Missing how to configure with an ARM template

Please include information about configuring an app configuration resource with an ARM template.

adding a feature flag with an arm template
adding a configuration value with an arm template
retrieving a connection string with an arm template

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

ID: 48545e6e-02ea-1a4a-c74a-82af6513a7f7
Version Independent ID: 916d7949-1a62-1d74-7cb5-1be816326ca7
Content: Tutorial for integrating with a continuous integration and delivery pipeline by using Azure App Configuration
Content Source: articles/azure-app-configuration/integrate-ci-cd-pipeline.md
Service: azure-app-configuration
GitHub Login: @yegu-ms
Microsoft Alias: yegu

@satls Thank you for the feedback!  We are investigating this and will get back to you shortly.

@satls Thanks for the feedback. We are working on this and will put up documentation when it's available. We will have the support of retrieving key-values as part of ARM template first and adding key-values via ARM template will be after.

@satls -- We are working on this request, as @zhenlan mentioned, and we'll have an update to our content shortly.  Thanks for your patience!  I'll close this Issue for now, but will return to this thread with a link to the new content when it has published.
#please-close

@jpconnock Is there an update on when this documentation will be published?

Where is the link to these ARM docs / examples?

Here is the document of an example of how to read key-values from App Configuration with ARM template. Particularly, please check out the usage of listKeyValue(...) API.
https://docs.microsoft.com/en-us/azure/azure-app-configuration/quickstart-resource-manager
The support for writing to App Configuration with ARM template is to be worked on, which is tracked in https://github.com/Azure/AppConfiguration/issues/268.


 It's difficult to find the cause of this problem from the log you pasted. I need to check what byte streams is passed to rtmp server.
 But sorry, could you paste the output of proxy?

in process right now ;)

About proxy, i got connection refused.
output:
2018/02/06 15:09:01 Listening: :1935
2018/02/06 15:09:01 Proxying: :1936
2018/02/06 15:09:04 tcpproxy: for incoming conn <IP_ADDRESS>:53189, error dialing ":1936": dial tcp :1936: getsockopt: connection refused

Did you run rtmp server at :1936 port?

 I'll analyze the output.
It may take a while, but please wait.

Sure, thank you so much!

add full log file
testlogfile.zip

Thank you. great job!

May I ask your email address ?

Sorry, no soliciting is allowed.

ok, understood.

Do you have any idea ?

Same problem here...


Bmc dump capture

THanks for this! I've merged it with some of my recent changes and pushed to master as of fa57c50e43b76e0f16d55b989dabfa24a349f9f3


v0.147.1

v0.147.1, 18 May 2021

Terraform: remove legacy terraform feature flag
Terraform: Clean up support for legacy terragrunt files
Hex: Fix version resolver specs
Update rubocop requirement from ~> 1.14.0 to ~> 1.15.0 in /common
Bump phpstan/phpstan from 0.12.85 to 0.12.88 in /composer/helpers/v1
Bump phpstan/phpstan from 0.12.85 to 0.12.88 in /composer/helpers/v2
build(deps-dev): bump eslint in /npm_and_yarn/helpers
build(deps-dev): bump prettier in /npm_and_yarn/helpers
build(deps): bump flake8 from 3.9.1 to 3.9.2 in /python/helpers
build(deps): bump @npmcli/arborist in /npm_and_yarn/helpers

I think we're backed up on CI because of the current incident https://www.githubstatus.com/


Feature/otp upload csv

Hi @nick-a-kitrum,
I minified the SVG file and rebased on develop. I'll merge the PR now.
Regarding the issue of the observations not appearing in the table, it seems it's because of the user ID. I added a comment in the task so Tiago and/or Dmytro can have a look: https://www.pivotaltracker.com/story/show/170696413


go test seems broken

go test fails:
lab@ubu20:~/devel/godux$ go test github.com/luisvinicius167/godux
# github.com/luisvinicius167/godux
src/github.com/luisvinicius167/godux/godux_test.go:7: store.Setstate undefined (type *Store has no field or method Setstate, but does have SetState)
src/github.com/luisvinicius167/godux/godux_test.go:15: store.Setstate undefined (type *Store has no field or method Setstate, but does have SetState)
FAIL    github.com/luisvinicius167/godux [build failed]
lab@ubu20:~/devel/godux$

@udhos fixed. :+1:

It keeps failing for me:
lab@ubu20:~/devel/godux$ ls -al
total 16
drwxrwxr-x  4 lab lab 4096 May 26 05:10 .
drwxrwxr-x 17 lab lab 4096 May 26 04:57 ..
drwxrwxr-x  3 lab lab 4096 May 26 05:10 pkg
drwxrwxr-x  3 lab lab 4096 May 26 05:10 src
lab@ubu20:~/devel/godux$ rm -rf *
lab@ubu20:~/devel/godux$ go get github.com/luisvinicius167/godux
lab@ubu20:~/devel/godux$ go test github.com/luisvinicius167/godux
# github.com/luisvinicius167/godux
src/github.com/luisvinicius167/godux/godux_test.go:7: store.Setstate undefined (type *Store has no field or method Setstate, but does have SetState)
src/github.com/luisvinicius167/godux/godux_test.go:15: store.Setstate undefined (type *Store has no field or method Setstate, but does have SetState)
FAIL    github.com/luisvinicius167/godux [build failed]
lab@ubu20:~/devel/godux$

Pass :+1: Try now!

Sim, agora o teste está rodando.
Eu tinha criado um pull request com o mesmo reparo:
https://github.com/luisvinicius167/godux/pull/3

Show de bola!


Cases API Deprecation Note

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[x] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

Should "deprecated": true be used instead?

although preview doesn't necessary apply to deprecation policy, add ARM review team to double confirm.


memory compression question

I have some questions when looking at the memory compression section, is the middle layer memory compressed here, or weight memory? How did you achieve such a high compression ratio.

It's the activation compression, no weight memory here.
When one activation tensor is consumed by all its consumers, its memory can be freed to the next layer's activation tensor.

So can it be interpreted as peak activation memory usage？

You can say it's the peak activation memory usage with dynamic activation allocation.

OK，I got you, thanks a lot !


f-cim-14191 into Develop

Added customerSLa in channel config for customer sla implementation'
Added   AGENT_SLA,CUSTOMER_SLA_STARTED,CUSTOMER_SLA_EXPIRED,CUSTOMER_SLA_STOPPED,
CUSTOMER_SLA,HOLD_TIMER and NO_RESPONSE_ENTITY for communication b/w C_manager and C_Monitor
For jira task:
http://project.expertflow.com:8080/secure/RapidBoard.jspa?rapidView=218&view=detail&selectedIssue=CIM-14005


Added Clean Code .NET

What does this PR do?
Add Resource
For resources
Description
Added "Clean Code .NET" book
Why is this valuable (or not)
Wasn't already available and is a good guide to clean code practices in .NET.
How do we know it's really free?
MIT license: https://github.com/thangchung/clean-code-dotnet/blob/master/LICENSE
For book lists, is it a book?
Checklist:

[x] Not a duplicate
[ ] Included author(s) if appropriate
[x] Lists are in alphabetical order
[ ] Needed indications added (PDF, access notes, under construction)

Thanks!


[RFR] Fix file field

Fix #597

@fzaninotto Tests are ok, fail is due to data that had been changed on the public demo...


Exceptions and Forward/Backward Flow Analysis

There is a serious problem with the way control-flow caused by exceptions is handled in the forward/backward dataflow analyses classes.  They don't handle it properly at all.
I think the solution is to make the exception blocks are more integral part of these analyses, so they automatically pass all possible flow over to the right places.

Forward Flow Analysis is now working correctly with them.

Backward Flow Analysis now done as well.


Multiple User Paths Displayed

Multiple user paths are show when only one user's path should be displayed.

Fixed in ed0e72dba8bb1cf6866d81ea15b7edb319f4583c.


Trouble with css

After deploy DEV , or PROD are missing images.
Fields are on left side on screen.

What exactly caused this? I'm doing a fresh install of this via the scatterp fork script and get the exact same thing.

this is not the place for issues on my fork...
you didnt follow the instructions please see the readme
its cause because you did not complete precompile:assets step

please visit https://gitter.im/peatio/peatio
for chat based direct help
and i will help you further there
for future tickets please post on my repo not here

Thanks, just saw this as an analog of my issue so posted here. Noted.


[Pipeline] create failed. jnlp connect timeout

** jnlp logs

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
Machine type (cloud/VM/metal) and specifications (CPU/memory):
Kubernetes version (use kubectl version):

rancher 2.2.8

Anyone can help me

I have the same problem
rancher 2.2.5

@zhoutaoo check Network Plugin

Let us know if this still needs to be investigated.


fix(api): Change the camera device based on system version

Overview
We updated the Linux Kernel recently which has changed the camera device from /dev/video0 to /dev/video2, so lets change it here. This pull request pertains to Opentrons/oe-core#140.
Closes: EXEC-354
Test Plan

[ ] Make sure we can take a picture via /camera/picture endpoint.

Changelog

set the camera device to /dev/video2 when taking a picture

Review requests
Risk assessment

curl -X POST --header "opentrons-version: 3" <IP_ADDRESS>:31950/camera/picture --output "picture1.jpg"


Datetime not working for dayValues attribute

Short description of the problem:
DateTime not working when the dayValues attribute is added
What behavior are you expecting?
Should show the Date picker with the specified days
When using the dayValues attribute in  something like this:
<ion-item>
       <ion-label>Date</ion-label>
       <ion-datetime monthValues="6,7,8" yearValues="2014,2015" dayValues="01,02,03,04,05,06" displayFormat="DD/MMM/YYYY" [(ngModel)]="myDate"></ion-datetime>
</ion-item>

i get the error as:

Cannot set property 'disabled' of undefined
at DateTime.validate (datetime.js:486)
at DateTime.open (datetime.js:350)
at DateTime._click (datetime.js:313)
ORIGINAL EXCEPTION: TypeError: Cannot set property 'disabled' of undefined
ORIGINAL STACKTRACE:
TypeError: Cannot set property 'disabled' of undefined
at DateTime.validate (http://localhost:8100/build/js/app.bundle.js:48564:48)
at DateTime.open (http://localhost:8100/build/js/app.bundle.js:48428:14)
at DateTime._click (http://localhost:8100/build/js/app.bundle.js:48391:14)
at DebugAppView.ViewAnalyticsRender0.handleclick_385_1 (AnalyticsRender.template.js:4870:36)
at http://localhost:8100/build/js/app.bundle.js:31774:24
at http://localhost:8100/build/js/app.bundle.js:41260:36
at http://localhost:8100/build/js/app.bundle.js:41330:111
at ZoneDelegate.invoke (http://localhost:8100/build/js/zone.js:323:29)
at Object.onInvoke (http://localhost:8100/build/js/app.bundle.js:36931:41)
at ZoneDelegate.invoke (http://localhost:8100/build/js/zone.js:322:35)
ERROR CONTEXT:
[object Object]Zone.runTask @ zone.js:260ZoneTask.invoke @ zone.js:423

Plunkr: http://plnkr.co/edit/RL5REAhfQdAoEdCjmLj3?p=preview
Which Ionic Version? 1.x or 2.x
2.0.0-beta.31
Plunker that shows an example of your issue
http://plnkr.co/edit/RL5REAhfQdAoEdCjmLj3?p=preview
Cordova CLI: 6.2.0
Gulp version:  CLI version 3.9.1
Gulp local:
Ionic CLI Version: 2.0.0-beta.31
Ionic App Lib Version: 2.0.0-beta.17
ios-deploy version: Not installed
ios-sim version: 5.0.8
OS: Mac OS X El Capitan
Node Version: v4.4.5
Xcode version: Xcode 7.3.1 Build version 7D1014

Any Updates on this?

Same issue here!

Same issue!

On RC3 is still not working, i cannot set dayValues:

Thanks for the issue and sorry for the wait! This will be fixed in the rc.5 release, but I also released a nightly version with the fix if you want to try it out sooner:
npm install --save<EMAIL_ADDRESS>


Add custom labels to prop_general

For the HFC tests, we take advantage of this to show how many A blocks and how
many B blocks we have, though I imagine it can come in handy in lots of other
places also.
I had accidentally left in a change to prop_general where we show the full chains always; this is not very useful for most tests.

No separate commits?

Some people get confused by them :roll_eyes:

bors merge


Rework actions

Phases
MP
MM
MB
MR
JM
Total

ETA
0
0
4
0
0
0

Developing
0
0
0
0
0
0

Review
0
0
0
0
0
0

Total
-
-
-
-
-
0

ETA est.

0

ETA cust.
-
-
-
-
-
0

Problem description
We need to speed up, parallelize and clean up github actions.

testing if open PR is breaking some jobs.

was not it, reopening


PLAYWRIGHT_MAX_CONTEXTS seams not works

I have set PLAYWRIGHT_MAX_CONTEXTS to 1
but when I start with to crawler it still open 2 browser instances.

class UrlCrawlerScript(Process):
    def __init__(self, spider, skus=None, proxy_provider="net_not"):
        Process.__init__(self)
        settings = get_project_settings()
        settings["TELNETCONSOLE_ENABLED"] = False
        settings["DOWNLOADER_MIDDLEWARES"] = {
            ScraperResponseMiddleware: 1000,
        }
        settings["DOWNLOAD_HANDLERS"] = {
            "https": "scrapy_playwright.handler.ScrapyPlaywrightDownloadHandler",
            "http": "scrapy_playwright.handler.ScrapyPlaywrightDownloadHandler",
        }
        settings["CONCURRENT_REQUESTS"] = 1
        settings["PLAYWRIGHT_MAX_CONTEXTS"] = 1
        settings["PLAYWRIGHT_MAX_PAGES_PER_CONTEXT"] = 1
        settings["CONCURRENT_ITEMS"] = 1
        settings["REACTOR_THREADPOOL_MAXSIZE"] = 1
        settings["ROBOTSTXT_OBEY"] = False
        settings["PLAYWRIGHT_BROWSER_TYPE"] = "firefox"
        settings["PLAYWRIGHT_LAUNCH_OPTIONS"] = {
            "headless": False,
        }

        settings[
            "TWISTED_REACTOR"
        ] = "twisted.internet.asyncioreactor.AsyncioSelectorReactor"

        self.skus = skus
        self.proxy_provider = proxy_provider
        self.crawler = CrawlerProcess(settings)
        self.spider = spider

    def run(self):

        scrapy.utils.reactor.install_reactor(
            "twisted.internet.asyncioreactor.AsyncioSelectorReactor"
        )
        is_asyncio_reactor_installed = (
            scrapy.utils.reactor.is_asyncio_reactor_installed()
        )
        print(f"Is asyncio reactor installed: {is_asyncio_reactor_installed}")

        from twisted.internet import reactor

        for sku in self.skus:
            proxy = utils_tasks.get_random_proxy(self.proxy_provider)
            self.crawler.crawl(
                self.spider, sku=sku, proxy_provider=self.proxy_provider, proxy=proxy
            )
        self.crawler.start()
crawler = UrlCrawlerScript(
    MouserSpyder, skus=processed_skus, proxy_provider=proxy_provider
)
crawler.start()
crawler.join()

Ok, thank you, I will try later

It works now


Added Horizontal Card Hover

Description
I've added a new CSS effect. It flips and shows information when the user hovers over it.

Type of change

[x] New feature (non-breaking change which adds functionality)

Explain the Testing instructions
Test Configuration:

Operating system: Tested on Mozilla Firefox and Google Chrome on Windows 10
Text-editors used: VS code

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@arpit456jain u can merge it


make it compile in elixir 1.10

HI,
This project is awesome, but it seems it can not be compiled in recent elixir versions. I tried to fix some compile error, still can't pass all tests, but now it's usable with elixir 1.10.
If more works need to be done about this PR, let me know. : )

@Ljzn Thanks a lot for that!


Modify AlaSQL to allow generate AST with other parsers (e.g. with Closure)

Some people want to write their queries with other query languages than SQL. E.g. query can ve written on Closure, it will generate AST, and AlaSQL will execute it.

I cant get my head around why that would be awesome. Maybe we could have some more words from the ones with the need.
Idea: If we make the module system where we can select flavour of SQL - will it be a parser module that generates a AST for the "engine" ? If so, we have a way of people extending with their own "parser" or how ever they want to create their selection interface.

Any inputs?


Added initial documentation for RedPen Server's REST API

Added some basic documentation for the REST API, including some example requests and responses, and some curl examples

Thank you very much for the excellent work!


"similar images" not clickable

When opening the details of a photos, some of them will have a "similar images" section near the bottom.
Expected behavior: clicking the image thumbnail will open the image
Current behavior, clicking the image thumbnail does nothing
Running docker on x86

Duplicate of #265 :)


Amplify init fails to resolve credential from profile in $AWS_CONFIG_FILE despite $AWS_SDK_LOAD_CONFIG=1

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.

previous issue, since closed, where people are invited to open new ones: https://github.com/aws-amplify/amplify-cli/issues/6882

[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
npm install -g @aws-amplify/cli@latest
If applicable, what version of Node.js are you using?
v12.22.12
Amplify CLI Version
10.4.0
What operating system are you using?
Ubuntu 20.04.2 LTS
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
Not applicable
Amplify Categories
Not applicable
Amplify Commands
init
Describe the bug

I do not use ~/.aws/config  in the standard location (I override it with AWS_CONFIG_FILE)
I do not use ~/.aws/credentials  at all (aws-vault does not require one)

Using aws-vault through credential_process in my non-standard located config file without a credentials file has been working for me in awscli v2 (and Intellij) for some time. So I expected it to be supported in Amplify CLI as well, especially since I export AWS_SDK_LOAD_CONFIG=1 (see reproduction). But it doesn't.
Expected behavior
I can't describe what to expect, since I never got past amplify init, it is the first time I use it, and I never ran it before.
First contact, so to speak:
I can tell you what I did not expect

Using default provider  awscloudformation
? Select the authentication method you want to use: AWS profile
AWS access credentials can not be found.  <<<< UNEXPECTED
? Setup new user (Y/n)                                 <<<< UNEXPECTED

Reproduction steps
1 .envrc
export AWS_REGION=eu-central-1
export AWS_DEFAULT_REGION=${AWS_REGION}
export AWS_CONFIG_FILE="/tmp/.aws/config.awsvault"
export AWS_VAULT_PROMPT=zenity
export AWS_PROFILE=awsvault-scrubbed-sandbox-admin
export AWS_SDK_LOAD_CONFIG=1
use asdf
layout node

/tmp/config.awsvault

[profile scrubbed-primary]
region=eu-central-1

[profile scrubbed-primary-admin]
source_profile=scrubbed-primary
role_arn=arn:aws:iam::PRIMARYACCOUNTID:role/scrubbed-primary-admin-role
mfa_serial=arn:aws:iam::PRIMARYACCOUNTID:mfa/scrubbed.primary.apiuser

[profile scrubbed-sandbox-admin]
source_profile = scrubbed-primary-admin
role_arn = arn:aws:iam::SANDBOXACCOUNTID:role/OrganizationAccountAccessRole

[profile awsvault-scrubbed-sandbox-admin]
credential_process = aws-vault exec -j  scrubbed-sandbox-admin

I'm using a jump account where an admin-role is assumed with an api user's credentials as long as an MFA token is provided.
From there, OrganizationAccountAccessRole in a target test account is assumed. This multihop is all taken care of by aws-vault.
3 direnv allow; amplify init use all the default answers, except for the default editor where I chose Intellij (this is irrelevant to the issue)
GraphQL schema(s)

# Put schemas below this line

Project Identifier
No response
Log output

$ strace -o strace.txt -f amplify init
$ tail -f strace.txt | grep -E '/\.aws'

Up to  Select the authentication method you want to use:
tail: strace.txt: file truncated
79159 access("/home/scrubbed/.aws/credentials", F_OK) = -1 ENOENT (No such file or directory)
79159 access("/home/scrubbed/.aws/config", F_OK) = -1 ENOENT (No such file or directory)
79159 openat(AT_FDCWD, "/home/scrubbed/.aws/credentials", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
79159 openat(AT_FDCWD, "/home/scrubbed/.aws/credentials", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
79159 access("/home/scrubbed/.aws/credentials", F_OK) = -1 ENOENT (No such file or directory)

Up to  AWS access credentials can not be found.
79159 access("/home/scrubbed/.aws/config", F_OK) = -1 ENOENT (No such file or directory)
79159 access("/home/scrubbed/.aws/config", F_OK) = -1 ENOENT (No such file or directory)

Additional information
My assessment is that AWS_CONFIG_FILE is not supported, even when AWS_SDK_LOAD_CONFIG=1.
Further, because amplify does not have a --debug flag, it is difficult to figure out what the tool is doing without resorting to strace.

Hey @lestephane, thank you for reaching out. Usage of AWS_CONFIG_FILE or AWS  to use a non standard location is currently not supported. Marking this as a feature request to align with AWS CLI(https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html)


wip: Clean up JS examples.

This is still early stages, mostly for @aero31aero to look at

@akashaviator I am closing this now, since we've now had a chance to discuss this approach, and I assume you've already grabbed my commits (and you can still do that after this is closed).


README: Documentation

The specs have quite a few examples, however, it would be a good idea to generate some documentation in the README that shows how to interact with the classes after they have been parsed.

:+1:


feat: manage job_token_scope allowlist

Will use python-gitlab to manage job_token_scope
closes #571

Full REST api for job_token_scope allowlists expected to be released in 16.10 (Mar 21st 2023), python-gitlab changes have been tested on the nightly build.
For development purposes this PR will be pointed at my fork/branch with the python-gitlab changes on

Will use: https://github.com/webfactory/ssh-agent?tab=readme-ov-file#usage to setup access to the python-gitlab fork

Need to add an SSH key into the workflow to pip install from the python-gitlab fork, so will set that all up within my fork and then merge main on there into here once proved and ideally once 16.10 released: https://github.com/TimKnight-DWP/gitlabform/pull/1


Bare year export

@njbart any opinion on year = 2021 vs year = {2012} for bibtex? Or date = 2021 for biblatex?
Support log ID:

Seems to be permitted. On bibtex: “For numerical values, curly braces and double quotes can be omitted” (http://tug.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf). WRT biblatex, all of the year-only date fields in https://github.com/plk/biblatex/blob/dev/bibtex/bib/biblatex/biblatex-examples.bib seem to be bare (unlike the date fields containing additional elements, though).
But what’s wrong with including the braces?

Nothing, mainly curious.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-25-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3646

Questions ?
Please refer to the Backport tool documentation


fix: storageincentives chain backend mock data race

Checklist

[x] I have read the coding guide.
[ ] My change requires a documentation update, and I have done it.
[ ] I have added tests to cover my changes.
[x] I have filled out the description and linked the related issues.

Description
Fixes storageincentives package chain backend mock datarace: https://github.com/ethersphere/bee/actions/runs/3603052071/jobs/6070762703

This change is

I suppose this issue was fixed in #3615?


CSP Tri 2 Review Ticket

Assigment
Points

N@tM
4/4

Observe Team project quality,  runs on cross domain, performs all evaluations without crashing.
1/1

Observe, Individual UI contains inputs that are validated for garbage, data cleaned (ie validate DOB or Password)
1/1

Observe, Individual UI contains actions for Create, Read,
1/1

Observe, Individual UI contains actions for Update, Delete (above requirement)
1/0

Individual code quality, review and observe comments in every function, class, or method reviewed.
1/1

BE review, observe if  Individual API handles error conditions (ie duplicate user id).
1/1

BE review,  observe if Individual API contains GET and POST methods
1/1

BE review, observe that Individual code contains database operations that support Create, Read
1/1

BE review, observe that Individual code contains database operations that support Update, Delete (above requirement)
1/0

Participation of Individuals, 75% of individuals completed college board requirements with a crossover score on each of 6 criteria.
1/1

Review Ticket / Presentation
0.5/0.5

Runtime Links
0.5/0.5

Technical Achievements, backend focus
0.5/0.5

Guides for Review (include Blog)
0/0.5

Video
0.5/0.5

GitHub analytics
0.5/0.5

Bonus, substitute and personal achievement for .5 more
0/0

Runtime links
Frontend
Backend
Technical Achievements
This is the code that I wrote to get class reviews. Originally, the code could only return the first class review posted by a user (as shown in user.showClassReview() in the commented out code). I used a for loop at the end to iterate through each entry

Video
Github analytics
Frontend
Backend

Assigment
Points
Comments

N@tM
4/4

Observe Team project quality,  runs on cross domain, performs all evaluations without crashing.
1/1

Observe, Individual UI contains inputs that are validated for garbage, data cleaned (ie validate DOB or Password)
1/1

Observe, Individual UI contains actions for Create, Read,
1/1

Observe, Individual UI contains actions for Update, Delete (above requirement)
1/0

Individual code quality, review and observe comments in every function, class, or method reviewed.
1/1

BE review, observe if  Individual API handles error conditions (ie duplicate user id).
1/1

BE review,  observe if Individual API contains GET and POST methods
1/1

BE review, observe that Individual code contains database operations that support Create, Read
1/1

BE review, observe that Individual code contains database operations that support Update, Delete (above requirement)
1/0

Participation of Individuals, 75% of individuals completed college board requirements with a crossover score on each of 6 criteria.
1/1

Review Ticket / Presentation
0.5/0.5

Runtime Links
0.5/0.5

Technical Achievements, backend focus
0.5/0.5

Guides for Review (include Blog)
0.5/0.5

Video
0.5/0.5

GitHub analytics
0.5/0.5

Keira


Deleted docs at cloudant.com are not replicated to device(deleted on device too)

my pull:
 Map<String, String> parameters = new HashMap<String, String>();
        parameters.put("doc_type", doc_type);
        PullFilter filter = new PullFilter("filters/getByDocType", parameters);
        Replicator replicator = ReplicatorBuilder.pull()
                .from(uri)
                .to(documentStore)
                .filter(filter)
                .withId(id).build();

my filter at cloudant:
function (doc, req) {
     if(doc.doc_type === req.query.doc_type) {
     return true;
  }

  return false;
}

i tried a workaround:

    if(doc.deleted) {
        return true;
    }

but no success, document at device are not deleted:

I/System.out: REV:{ id: aba05d7513d30f8c31d4af175ea657ad, rev: 1-82435da0a023e2e218549fb37dfdbce3, seq: 38, parent: -1, current: true, deleted false }

thru url: /mydb/aba05d7513d30f8c31d4af175ea657ad

{"error":"not_found","reason":"deleted"}

the only thing i can guess, is that the latest revision (deleted one) has no attr doc_type, so its not returned by the return( when doc_type = req.query.doc_type), thats why i tried with no success the workaround above
how can i handle this deleted docs and replicate even the deletion to the device?

@defaultbr it looks like you made a small mistake in the "workaround" for your filter, you need to use _deleted instead of deleted:
(using the animaldb database as an example)
{
  "_id": "_design/animal",
  "_rev": "3-bf2aa5336257f9e99f3dab823129392d",
  "filters": {
    "by_class": "function(doc, req) { if (doc._deleted == true) {return true;} if(doc.class && doc.class == req.query.class) { return true; } return false; }",
  }
}

Now I can set up a filter:
        PullFilter filter = new PullFilter("animal/by_class",
                CollectionFactory.MAP.of("class", "mammal"));

If I pull replicate, then delete a document, I can see the delete reflected in my database.
I agree that this is a work-around because you will end up replicating all deleted documents and not just the ones for the document type you want. But the problem is that once the document has been deleted, it has no body so you can't tell what the type is.

@defaultbr a colleague suggested another approach which is to write a "tombstone" document. You can perform a PUT on your couch/cloudant instance with the _deleted flag set:
{"_id": "foo", "_rev": "123-abc", "_deleted": true, "class": "mammal"}

In your case the tombstone would have "doc_type". The key is to include the field which your filter depends on.

I got it, i had another light:

Pull all docs by doc_type (or by_class you created above)

Pull all deleted docs by ids that i pass to the filter
-> query for non deleted docs inside the device
-> get all IDS:
-> pull from getDeletedFromIdsList(pass the list as parameter to the filter)

so filter will update the docs that i have and i will not take the unecessary files, ex: something deleted that i dont have, what do you think?
@tomblench  is there any way to REMOVE the doc from device(not delete), ex: take all tombstone and delete it to free some disk space? cuz i have a incremental database and i replicate the docs from today (i pass the date parameter to filter), but i must really remove the yesterday docs so i can have free disk space

Firstly, you are correct that you will run into problems using the document IDs as parameters to a filter. They are passed in the query part of the URL and you will soon run into the path length limit (I can't remember what is is off-hand for Cloudant but we have definitely seen other users run into similar issues).
Secondly, what you refer to as "REMOVE" is called purge in CouchDB parlance. You can see from the link that there lots of caveats associated with purging documents. Currently purging is not supported in sync-android. However, if you do a compact() after deleting a document then only minimal metadata about the revision history is retained - on the order of tens of bytes per revision. Whether this suffices for you will depend on your data model and the number of documents/revisions you expect to create and delete.

Solved this splitting the replicator in parts to avoid to explode get path limit


change model

Hi! friend，I need your help. When I try test.sh , I change the model from centerfusion modle to nuscens_3Ddetection_e140 model,like the picture:

But the result like this

,the error is too big,Is this a normal result?OR,  Is there any parameters that I need to change or add

Hi.
If you want to get the baseline CenterNet results you should run the CenterNet code. CenterFusion has many modifications and might not give you the correct CenterNet results even when modifying the test script options like what you've done.


The default value for maximum instance count is 20 if not specified.

The article stipulates that the default value for maximum instance count is 20 but from what I can see when creating an Application Gateway that this value is 10.

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

ID: faa5b8a2-11a1-6a2d-07cb-ffcf39643ed4
Version Independent ID: 298a134e-fb27-f16d-bff2-d43eb0f766fd
Content: Scaling and Zone-redundant Application Gateway v2
Content Source: articles/application-gateway/application-gateway-autoscaling-zone-redundant.md
Service: application-gateway
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

@dcc-spartan , thank you for your feedback. We'll review this and get back to you shortly!

@dcc-spartan , thank you for bringing this to our notice. You are right. The default value for maximum instance count shows 10 when autoscaling is selected. And this can be seen in the screenshot provided in the Application gateway creation tutorial.
Refer : https://learn.microsoft.com/en-us/azure/application-gateway/quick-create-portal#basics-tab

I've submitted a PR to update the doc with the correct maximum instance count i.e. 10 and the doc will reflect the changes soon.
We are closing this issue for now. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


ARROW-8843: [C++] Compare bitmaps in words

Unaligned bitmap comparision are currently processed bit-by-bit.
Comparing word-by-word in uint64 improves performance significantly.
Bechmark(comparing two identical bitmaps with 64K bits) jumps from
86M/s to 5.7G/s on my test machine.
NOTE: This patch may hurt performance if two bitmaps differ at the very
begining bits, as it always loads and compares 64 bits if possible. Bit
by bit comparison will notice the difference and return false earlier.
This should not be a problem in practice.

Before (apply only benchmark code)
BitmapEqualsWithoutOffset/8192                195 ns          195 ns      3618366 bytes_per_second=39.1055G/s
BitmapEqualsWithOffset/8192                 91272 ns        91235 ns         7673 bytes_per_second=85.6307M/s

After
BitmapEqualsWithoutOffset/8192                193 ns          193 ns      3635971 bytes_per_second=39.6261G/s
BitmapEqualsWithOffset/8192                  1332 ns         1331 ns       510343 bytes_per_second=5.73058G/s

NOTE: This patch may hurt performance if two bitmaps differ at the very
begining bits, as it always loads and compares 64 bits if possible. Bit
by bit comparison will notice the difference and return false earlier.
This should not be a problem in practice.

This should be negligible in practice. The processor still load in unit of words.

@cyb70289 Thank for this. For future reference, if you add a new benchmark, do it first as a seperate commit, and then add the improvement in a following (chronologically) second commit. You'll be able to check the difference with ursabot, e.g. ... benchmark [filter] <sha_of_first_commit>.


NYT Raw Data QA

This PR includes QA for NYT Data, because their data keeps changing 👍
Please Check

[ irrelevant] Are the JSON schemas updated?
[ irrelevant] Are the api docs updated?
[ they better!] Are tests passing?

@tashwoods I'd like to get to a world where the entire covid-data-model has zero dependencies on data outside the covid-data-public repo. Perhaps it is a bit fanciful but what do you think of putting QA checks on NYT data in covid-data-public? If you think covid-data-public has deviates from the nytimes/covid-19-data repo by even single number lets fix get to the bottom of why our copy is broken. Perhaps a release process for covid-data-public makes sense where we run checks on fetched data then bless a particular covid-data-public sha for use by the run done in covid-data-model.
I tried to list out the tradeoffs...
QA checks in covid-data-model:

don't need to change how NYT data is fetched
lets QA display reference particular API snapshot outputs
makes it easier of QA analysis to reuse code/tools used for other analysis in the model repo

QA checks in covid-data-public:

changing how NYT data is fetched is already queued https://trello.com/c/CUdt78CV/107-add-nyt-data-to-covid-data-public
helps to separate data changes (in data-public) from code changes (in data-model) which

makes running the model more deterministic
enables more caching of intermediate values for faster builds
provides a clean separation of concerns where someone can contribute to the data-public repo with little knowledge and no dependency on data-model

@TomGoBravo
That is an interesting idea, to only 'release' data for covid-data-model to use once it has passed checks within covid-data-public. This seems to make sense to me, as long as we don't end up stuck on an old version of the dataset, because all the new datasets differ 'too much.' I think we will have discuss this more with @igorkofman.
For now, this works and at least provides some easy debugging. But will still have to be added to run.sh so we can see the differences between api snapshots.
If people are cool with this merge, we could add
python check_nyt_raw_data.py
to run.sh

Replaced by https://github.com/covid-projections/covid-data-model/pull/436


DnssdServer ResponseTimeout

Sometime after 697cb48, thread FTDs are no longer able to resolve DNS of a hostname on the adjacent ethernet network successfully. To be clear, 697cb48 works fine, but the latest commit does not.
I have a Raspberry Pi 5 with RCP connected via SPI running a docker compose stack consisting of an otbr container and a mosquitto broker container, which are networked appropriately. The FTDs are commissioned via the otbr container and attempt to use otDnsClientResolveIp4Address to resolve the mosquitto service name so they can connect to MQTT. This has been working fine for a while.
After running a clean build of the otbr container recently, the FTDs can no longer find mosquitto:
ot-br-posix_main.log
The FTDs return errno 28 (ETIMEOUT) when trying to resolve DNS. Equivalent with ot dns resolve4 hostname.
I jumped back a couple months on ot-br-posix to the aforementioned commit in a new clean docker build and it works again as expected. This was the only change made.
ot-br-posix_697cb48.log
As expected, the FTDs can resolve the hostname.
Additional details:
Raspberry Pi 5, nrf52840DK RCP connected via SPI
FTDs are nrf52840DK running proprietary software, though the openthread CLI is sufficient to check the problem with ot dns resolve4 hostname
Network is:
FTD <---> Pi 5 [ OTBR Docker <--Docker VLAN--> Mosquitto Broker ]

Probably this is caused my previous PR: https://github.com/openthread/openthread/pull/10864.
If you build with OPENTHREAD_POSIX_CONFIG_UPSTREAM_DNS_BIND_TO_INFRA_NETIF set to 0 then it should have exactly the same behavior as the older code.
However, this issue is still worth digging into. Could you capture (using tcpdump or wireshark) the DNS packets on the Docker VLAN and check if the DNS queries were sent to the upstream?

Thanks for the response!
I tried setting OPENTHREAD_POSIX_CONFIG_UPSTREAM_DNS_BIND_TO_INFRA_NETIF to 0 by modifying my Dockerfile (copied from ot-br-posix and modified for SPI) to have:
ENV OTBR_OPTIONS=${OTBR_OPTIONS:-"-DOT_POSIX_RCP_SPI_BUS=ON -DOPENTHREAD_POSIX_CONFIG_UPSTREAM_DNS_BIND_TO_INFRA_NETIF=0"}

Building at latest ot-br-posix with that has no effect it would seem. I am still getting the DNS query timeouts. I'm not 100% sure I'm setting that flag right though.
The log is much the same as before:
ot-br-posix_issue2593_1.log
As I understand it, the dockerfile should also be setting the -B flag by way of INFRA_IF_NAME correct? I do have the following entries for all 3 of the logs provided so far (working and not working):
Nov 19 22:19:07 f6d3e1397017 otbr-agent: [NOTE]-AGENT---: Backbone interface: eth0
Nov 19 22:19:07 f6d3e1397017 otbr-agent[156]: [NOTE]-AGENT---: Running 0.3.0-thread-reference-20230710-471-gb4cfa2ffa25
Nov 19 22:19:07 f6d3e1397017 otbr-agent[156]: [NOTE]-AGENT---: Thread version: 1.4.0
Nov 19 22:19:07 f6d3e1397017 otbr-agent[156]: [NOTE]-AGENT---: Thread interface: wpan0
Nov 19 22:19:07 f6d3e1397017 otbr-agent[156]: [NOTE]-AGENT---: Radio URL: spinel+spi:///dev/spidev0.1?gpio-int-device=/dev/gpiochip0&gpio-int-line=20&gpio-reset-device=/dev/gpiochip0&gpio-reset-line=21&spi-speed=1000000
Nov 19 22:19:07 f6d3e1397017 otbr-agent[156]: [NOTE]-ILS-----: Infra link selected: eth0

I think adding -DOPENTHREAD_POSIX_CONFIG_UPSTREAM_DNS_BIND_TO_INFRA_NETIF=0 to OTBR_OPTIONS may not work as you expected, because OTBR_OPTIONS expects CMake options while OPENTHREAD_POSIX_CONFIG_UPSTREAM_DNS_BIND_TO_INFRA_NETIF is a C macro which is not visible to CMake.
Maybe you can try just changing this line to define it as zero.
This gives me lo, wpan0, eth0, and eth1 inside the container. eth0 should be the correct backbone interface to reach the MQTT container I'm running DNS queries for on my FTDs. The other network is my reverse proxy / ingress for the docker compose stack just so I can reach otbr web and the otbr REST API.

It seems correct to specify -B eth0 according to your topology and otbr-agent was configured correctly.
The issue is that when otbr-agent's UDP socket is bound to eth0, the DNS query failed to get transmitted to the DNS server. When it's not bound, it can reach the DNS server.
Suggestion:

Check the /etc/resolv.conf file for the IPv4 DNS server addresses, see if they are reachable using the eth0 network interface. E.g. ip route get <DNS server address> oif eth0. A possible case is that your container uses <IP_ADDRESS> as the DNS server so it's not accessible eth0.


When trying to Deoply to Heroku - the configuration of SendGrid add-on fails

Hi,
When pressing on "Deploy to Heroku" button, the process fails on the step of Configure environment with the message of:
"There was an issue setting up your app environment.
An error was encountered when contacting the add-on partner to create sendgrid:starter. Please try again later."
I got this message also when I try to attach the sendgrid add-on to another heroku app so I know this problem has nothing about you, but maybe you are familiar with this issue.
Thanks.

solved


Suggestion: Add additional information for commandline argument in documentation to show note about backslash needing to be escaped

There is a "Note" for this for the "Starting directory" property, but nothing noted for this issue for "commandline", which comes first in the documentation.
Listing a couple examples for commandline that use a full path may help this standout even better (along with using forward slash as an alternative).  Such as:
Examples:
"commandline": "C:\PSH7.1\pwsh.exe",
"commandline": "D:/PS7/pwsh.exe",
Love the product so far!

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

ID: cdc47554-5bdf-3c0b-b0aa-9cdf7dd1f552
Version Independent ID: d4f44877-99e8-4563-6b06-7b6f9bcd43bd
Content: Windows Terminal General Profile Settings
Content Source: TerminalDocs/customize-settings/profile-general.md
Product: dev-environment
Technology: windows-terminal
GitHub Login: @cinnamon-msft
Microsoft Alias: cinnamon

I was hesitant to even add the note for commandline, under the auspices of it’s JSON, that’s just the rules. Now we have two problems with it. 😄

NOw that we have the Settings UI, we are recommending that folks update their paths there which will handle this issue automatically. Thanks for filing this!


add --message-format short option

--message-format currently has the following options:
--message-format FMT         Error format: human, json [default: human]

I would like an additional option to be added: short. Other possible names:

brief
oneline

I've been programming in rust for the better part of a year now. The compiler has been my friend and mentor through this time, and a big part of that has been the fantastic human readable error messages. Thank you so much for them!
However, I have gotten much more familiar with the language and my common mistakes, so (often) no longer need error messages to be so long (sometimes they are longer than 10-15 lines!). Normally I just need the compiler to give the me the file, line/col number and name of te error and I can spot it myself very quickly.
For an experienced programmer, a shorter format would make finding errors much more ergonomic.
The following pipe does roughly what I want, although it would be nice if it was all on one line:
# cargo test |& rg "(error\[\w+\])|(^\s+--> \w+/\w+)" -N --color never
error[E0061]: this function takes 2 parameters but 3 parameters were supplied
   --> src/user/tests.rs:186:37
error[E0061]: this function takes 2 parameters but 3 parameters were supplied
   --> src/export.rs:133:51
error[E0061]: this function takes 2 parameters but 3 parameters were supplied
   --> src/export.rs:139:37
error[E0063]: missing field `revision` in initializer of `export::ArtifactData`
   --> src/export.rs:149:20

Thanks!

Thanks for the report! This may be best opened up over at rust-lang/rust though, as in general Cargo doesn't control the compiler's output of error messages.

I'm going to close this since https://github.com/rust-lang/rust/issues/42653 exists :)


Interpretation of Benchmark Outputs

Hi again Eric,
I was able to add my own network to your collection, and wanted to run two benchmarks: varying regression and varying networks. I'm having some trouble interpreting the outputs. From my understanding, the resulting perPert.parquet file for the varying regression benchmark should contain a 'regression_methods' column that's populated by each regression method specified in the respective experiment's metadata JSON. The 'regression_methods' column in the output I obtained is only populated by the last value of the list provided in the metadata JSON (which happens to be 'BayesianRidge'). I'm having the same issue for the varying networks benchmark. Am I misunderstanding the output? I've attached the regression benchmark's JSON. Thanks!
metadata.json

You're right -- that's not what I would expect either. Do you have stdout and stderr logged from that run? Could you also share the result of running tree on your output folder?

Hey, here are the files for the most recent regression I ran:
tree.txt
stdout.txt
err.txt
metadata.json

OK, this looks pretty good to me. All the predictions got saved, and they all got found and read back into memory for evaluation. The exceptions shown in stdout are safe to ignore and they just mean your output will have some 2d visualizations missing. The only downside to all this positivity -- I have no idea at all where the actual problem lies. Is evaluationsPerPert.parquet small enough that you could send it, or send me a dropbox/gdrive link to? My email is<EMAIL_ADDRESS>if that helps.

Thanks for your patience, and thanks for sending that file. I wrote this bug recently while working on new evaluation code related to timeseries and embryogenesis data. It should be fixed now in the development version. It also should not affect the version of the code released with our preprint.
You do not have to re-train all the models. If you reinstall pereggrn and run it again, by default pereggrn will re-run your evaluations based on the already-saved predictions.


DKMS module loaded but not present in lsmod

I know this is maybe not actively watched but, if anyone looked at this it would be very appreciated!
I think i built everything right, i can see the DKMS module setup, but its not loaded in lsmod?
# dkms status
nwfermi/<IP_ADDRESS>, 6.1.0-17-amd64, x86_64: installed
# lsmod |grep -i fermi
#

# lsusb | grep "Touch"
Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen

Thanks for reading!

Your device ID 1926:0003 is not listed in the driver so it's unsure if this driver will work for your model.
You can always try to duplicate line https://github.com/glorang/nwfermi/blob/master/usr/src/nwfermi-<IP_ADDRESS>/nw-fermi.c#L52 and change 0x0006 in 0x0003, rebuild, reinstall and check if it works or not.
This is presumably a HP TouchSmart ? Which model exactly ?

Wow! That was really quick, I appreciate you replying so fast.
It was pretty easy to change that line you mentioned, thanks! I rebuilt and everything but, it doesn't seem to work, lsmod |grep -i fermi is still empty and
$ strings /dev/nwfermi1
strings: '/dev/nwfermi1': No such file

still says nothing is there.

This is presumably a HP TouchSmart ? Which model exactly ?

Its a HP TouchSmart dx9000
Thanks again for the help!

$ strings /dev/nwfermi1   , if you are getting output as no such file,
try $ strings /dev/nwfermi2
if still doesnt's work , try  $ strings /dev/nwfermi0
if it still doesn't work , try $ strings /dev/nw-fermi

lsmod |grep -i fermi is still empty

This should not happen, did you perhaps change the nw-fermi.c file in your local git copy but then didn't copy it to /usr/src/nwfermi-<IP_ADDRESS>/ ?
Does modinfo nw_fermi | grep "v1926p0003" return anything ? If not you are still using an old driver.
You can always do a modprobe nw-fermi as well and check dmesg output


Faster byte-to-hex and other fun stuff

The main purpose of me looking into this was to add CodesInChaos's unsafe variant of his byte-to-hex lookup method that runs significantly faster than the safe version (on SmallText, this was 171.87 average ticks for unsafe compared to 235.47 ticks for lookup-per-byte... 105.9x vs 77.3x since the worst one that run was 18194.17 ticks).  While I was in there, I also added:

forced amortization of costs on the different byte-to-hex variants that would be amortized in practice, such as creating lookup tables.
dynamically generating the hex string table using some really fun LINQ, which seemed fair game because that's how _Lookup32 is generated.
super minor cleanups.

I also took a look at the other tests and added some thoughts of my own... it's all in the commit messages, but might as well point it out here:

since the casting stuff is literally just looking at different ways of reimplementing .OfType<T>(), I figured we might as well put .OfType<T>() in there to see how well it performs... turns out, better than some of the other ones here.
figured I'd add at least one in each LINQ-based test that does away with the projection operators and just does a simple loop.
fixing an oversight in the entire-sequence casting test that causes it to just test how quickly we can create the sequence, rather than anything that actually manipulates the sequence... this also meant dropping down the iteration count for the same reason I suspect you did it on the other similar test.
leveling the playing field for all of the casting tests by calling .Skip(0) on the list we return, as LINQ sometimes special-cases List<T> sources by doing different things that give anything that starts with .Select(x) or .Where(x) an unfair advantage over anything that doesn't.
calling the built-in SequenceEqual method for equality comparison on the entire-sequence casting test, instead of reimplementing it inefficiently.

I also tried improving the test for getting object properties by name, but by the time I was done, I discovered that I had just reimplemented FastMember, just in a less general-purpose way, so I backed off on that one.  It was super cool, but then again, so is FastMember...
Note that I had to make some changes to the project file to make it compile in my MonoDevelop environment... I backed them all out except for the couple of lines required to make unsafe blocks OK to use, but that means I wasn't able to directly test the code here.  Let me know if it doesn't build for you, or breaks for some other reason, and I'll try to help make it work for you.  I'd normally use Visual Studio Community, but that PC is out for repairs so I'm in an Arch Linux VirtualBox on a different PC (which is actually why I looked into your project at all... I'm incredibly bored... but this is like a tangent on another tangent, so I'll stop writing now).

Wow! Thanks for poking around at things. You've definitely found some tweaks that were long overdue. I'll give things a few runs in the next day or two to verify everything is working as expected, but this should definitely tighten things up.
Questions
One quick clarification, and it may just be from a lack of understanding on my part.

leveling the playing field for all of the casting tests by calling .Skip(0) on the list we return, as LINQ sometimes special-cases List sources by doing different things that give anything that starts with .Select(x) or .Where(x) an unfair advantage over anything that doesn't.

I hadn't heard about the special-case logic for certain lists, but I almost wonder if we should avoid the Skip(0) since the advantage would be relevant to any performance of the test here. If the special case would happen for people actually implementing this code, would that be a point in favor of allowing the advantage to happen?
Everything Else
I've never written a single line of unsafe code, so I'll have to defer to assuming it all works there.

since the casting stuff is literally just looking at different ways of reimplementing .OfType(), I figured we might as well put .OfType() in there to see how well it performs... turns out, better than some of the other ones here.

I don't know how I totally missed the existence of the OfType<T> LINQ method, but now that I know it performs well, it pretty much negates the need for any of the rest of the tests in that section. Good catch there!
That SelectMany is a really clean way to do the hex look-up table. I like it! I suppose there's something to be said for the unmistakable obviousness-of-intent of the full table, but I'll keep your version since the comment works well enough.

fixing an oversight in the entire-sequence casting test that causes it to just test how quickly we can create the sequence, rather than anything that actually manipulates the sequence... this also meant dropping down the iteration count for the same reason I suspect you did it on the other similar test.

Good catch on that one. As for the iteration count, it was definitely more about patience than anything. As much as I want to allow for evening out any anomalous results, I don't have all day.

calling the built-in SequenceEqual method for equality comparison on the entire-sequence casting test, instead of reimplementing it inefficiently.

Nicely done! That's an even better solution that my ancient comment was pointing toward.
I do have one question

Last line looks like it got cut off at the end there.
About the List<T> special-casing, you have a point, but it would make the results only be fully applicable to List<T>; not that it's my place to tell you what's right or wrong in your project, but given the choice for my own project, I'd rather pick the solution that has the best worst-case behavior, and let built-in optimizations sometimes push it faster, rather than picking the one that's tested with certain optimizations that may not apply, pushing the code slower if it gets called differently than the benchmark does it.
FYI, the difference is fairly small for List<T> vs an arbitrary IEnumerable<T> (it's a lot more significant for a T[]).  The relevant bits can be found in the implementation of these methods in the reference source, specifically lines 15-22, 38-45, and then the beasts on 61-389 that make it all happen.  Ignoring the one-time savings of not having to box the List<T>.Enumerator and a slightly simpler Dispose() method that probably JITs down to the same thing anyway, the biggest difference I can see here is that accessing MoveNext() and Current for the List<T> version is done with a CIL call instruction (because it's known at compile-time to be a struct) instead of the very slightly slower callvirt instruction that it has to do for the arbitrary IEnumerable<T> version.  The difference is very small and not even applicable in Mono for me to test it out (it just optimizes the T[] case), but since the difference between call and callvirt feels like it could be significant when compared to the other differences between some of the other things we see here, I felt it worth mentioning.
The unsafe code is directly copy-pasted from CodesInChaos's post that included the source for the current leader, in case that helps increase your confidence.

Sorry. That last line was a case of poor editing on my part. I'd moved the question up so you didn't have to wade through other minor responses and forgot to trim.
You've certainly convinced me on that optimization avoidance. I wasn't trying to forbid it, I just didn't realize it wasn't going to be universally applicable. After I give everything a new run today, I'll plan on giving it a merge.

@patridge: ping :-)

Thank you for the reminder. I ended up side-tracked that evening, and this PR sadly disappeared off my radar. Everything ran fine. Things shuffled only a little but there were gains across most of them. And of course, unsafe shot way to the top. After I merge, I'll update the main readme with a sample run.


changed entity types to reflect the Model Names, not the database tables

Coverage increased (+31.3%) to 98.723% when pulling 43fb0777057e65d913222828975b920c8d33fa7f on c-harris:master into b73bf56d20c42c951dff83d8a475c36ff5592fb6 on Algo-Web:master.

Coverage increased (+31.3%) to 98.722% when pulling daa49917396bd583f1fd8a452bf834a26ae89ca5 on c-harris:master into b73bf56d20c42c951dff83d8a475c36ff5592fb6 on Algo-Web:master.

Coverage remained the same at 98.722% when pulling dcf17444c6d5ac7e4aa3320acd20e070d0d8d83d on c-harris:master into 73f0ee5c724eb0ee9faeb1932b9ece5d961cd6d8 on Algo-Web:master.

Coverage remained the same at 98.722% when pulling dcf17444c6d5ac7e4aa3320acd20e070d0d8d83d on c-harris:master into 73f0ee5c724eb0ee9faeb1932b9ece5d961cd6d8 on Algo-Web:master.


Support signing and preparing declare transactions through Account

Currently, Declare transactions have to be manually prepared and signed. This flow should be improved to allow easy Declare preparation and signing through Account interface.

Partially blocked until #146 is resolved.

let's split into two


Thread Safety of EntitasCache

Hi,
We are using Entitas on a server and I am currently trying to start server instances in multiple threads, and I noticed that the class EntitasCache is not thread-safe, through the use of the static instance of ObjectCache. Are there any plans to fix this, for example by wrapping that instance inside a ThreadLocal? Are there other places where static instances are used, i.e. should I forget the idea of running different Context instances safely in different threads?
Thanks,
Wofgang

@wolfgang-wdw
If you spot areas that can be improved to better support multi threading I encourage you to make a PR. Unfortunately, I'm not working on a project that uses multiple threads atm, so my attempts to make Entitas safer would be based on artificial scenarios and probably incomplete.
But I'd be happy to exchange experience with you and make Entitas work better in you case!

related PR #919


self is not defined

See https://github.com/mozilla/localForage/blob/master/src/localforage.js#L424
call(typeof window !== 'undefined' ? window : self);

The self is undefined. Although I am uncertain what it is supposed to be. It looks like the passed in variable isn't used. The self might have been added in a pull request adding service worker support.
This error prevents localforage being upstream with webpack.
https://github.com/mozilla/localForage/commit/66ed3aeb261886c60f7805a1ccdbbb59d675eae0

Yes, this was added to support service & web workers.

This error prevents localforage being upstream with webpack.

What exactly is your error?
Because we are using webpack to bundle localforage's sources in v1.3 and never got any error!?!?

I see that webpack is used to bundle localforage itself, but then if you consume the localforage dist into another project that is also being bundled with webpack, then webpack throws a wobbly because it can't resolve self.
For example, in a project where localforage is installed via npm, import it your file, then bundle this. Webpack will go off and load the dist output.
import localforage from 'localforage';

As said in #470,

We have webpack repacking tests

What exactly is your error and what configuration do you use?

This is the exact error thrown by webpack when bundling it in with myproject that has a file with the import as mentioned above.
I'll look at the test (just grabbing 🍜lunch) and figure out why the test passes but this fails.
Cheers
/myproject/node_modules/localforage/dist/localforage.js:1161
        typeof window !== 'undefined' ? window : self
                                                 ^

ReferenceError: self is not defined
    at Object.exports.__esModule (/myproject/node_modules/localforage/dist/localforage.js:1161:50)
    at __webpack_require__ (/myproject/node_modules/localforage/dist/localforage.js:719:30)
    at exports.__esModule (/myproject/node_modules/localforage/dist/localforage.js:739:18)
    at /myproject/node_modules/localforage/dist/localforage.js:742:10
    at webpackUniversalModuleDefinition (/myproject/node_modules/localforage/dist/localforage.js:692:20)
    at Object.<anonymous> (/myproject/node_modules/localforage/dist/localforage.js:699:3)

I'm encountering the same error using import localforage from 'localforage'; + babel6. Did you find some solution?

Is there an error trace available? Are you targeting the /src/ files?

File is compiled (sucessfully) by babel:
import extend from 'lodash/object/extend';
import clone from 'lodash/lang/clone';
import localforage from 'localforage';
const log = console.log.bind(console);
log(localforage);
export default class FooBar {
}

With .babelrc

{
  "presets": ["es2015", "stage-0"]
}

But in my mocha unit tests:

import chai from 'chai';
const expect = chai.expect;
import FooBar from './../foobar.js';

describe('FooBar', () => {
  describe('#constructor()', () => {
    it('should properly merge options', () => {
      const analytics = new FooBar({foo: 'bar'});
      // assert.equal(analytics.opts, {foo: 'bar'});
      expect(analytics.opts).to.be.a('object');
      expect(analytics.opts.foo).to.eql('bar');
    });
  });
});

It fails right away with:
ReferenceError: self is not defined
    at Object.exports.__esModule (/Users/olivier/Projects/web-analytics/node_modules/localforage/dist/localforage.js:1157:51)
    at __webpack_require__ (/Users/olivier/Projects/web-analytics/node_modules/localforage/dist/localforage.js:719:30)
    at exports.__esModule (/Users/olivier/Projects/web-analytics/node_modules/localforage/dist/localforage.js:739:18)
    at /Users/olivier/Projects/web-analytics/node_modules/localforage/dist/localforage.js:742:10
    at webpackUniversalModuleDefinition (/Users/olivier/Projects/web-analytics/node_modules/localforage/dist/localforage.js:692:20)
    at Object.<anonymous> (/Users/olivier/Projects/web-analytics/node_modules/localforage/dist/localforage.js:699:3)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at Object.<anonymous> (/Users/olivier/Projects/web-analytics/dist/analytics.js:19:20)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at Object.<anonymous> (/Users/olivier/Projects/web-analytics/dist/test/analytics.spec.js:7:18)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at /Users/olivier/Projects/web-analytics/node_modules/mocha/lib/mocha.js:216:27
    at Array.forEach (native)
    at Mocha.loadFiles (/Users/olivier/Projects/web-analytics/node_modules/mocha/lib/mocha.js:213:14)
    at Mocha.run (/Users/olivier/Projects/web-analytics/node_modules/mocha/lib/mocha.js:453:10)
    at loadAndRun (/Users/olivier/Projects/web-analytics/node_modules/mocha/bin/_mocha:349:22)
    at rerun (/Users/olivier/Projects/web-analytics/node_modules/mocha/bin/_mocha:376:5)
    at /Users/olivier/Projects/web-analytics/node_modules/mocha/bin/_mocha:384:7
    at StatWatcher.<anonymous> (/Users/olivier/Projects/web-analytics/node_modules/mocha/lib/utils.js:173:9)
    at emitTwo (events.js:87:13)
    at StatWatcher.emit (events.js:172:7)
    at StatWatcher._handle.onchange (fs.js:1295:10)

I'm still not able to reproduce this... and the integration tests seem to
be passing !?!?
Can you test of #470 fixes your problem?
--
Thodoris Greasidis
Computer, Networking &
Communications Engineer

Juste merged the changed and rebuild. I do confirm that #470 does fix it.

@thgreasi Hi!
I am getting this same error with:
"localforage": "1.4.0"
"babel-cli": "^6.6.5",
"babel-core": "^6.7.0"
"mocha": "^2.4.5"

The command is ./node_modules/.bin/mocha --recursive --compilers js:babel-core/register
My .babelrc is:
{
  "presets": ["es2015"],
  "plugins": ["transform-flow-strip-types", "transform-object-rest-spread", "transform-class-properties"]
}

Stacktrace:
/Users/montogeek/project/node_modules/localforage/dist/localforage.js:1162
  })(typeof window !== 'undefined' ? window : self);
                                              ^

ReferenceError: self is not defined
    at Object.exports.__esModule (/Users/montogeek/project/node_modules/localforage/dist/localforage.js:1162:46)
    at __webpack_require__ (/Users/montogeek/project/node_modules/localforage/dist/localforage.js:719:30)
    at exports.__esModule (/Users/montogeek/project/node_modules/localforage/dist/localforage.js:739:18)
    at /Users/montogeek/project/node_modules/localforage/dist/localforage.js:742:10
    at webpackUniversalModuleDefinition (/Users/montogeek/project/node_modules/localforage/dist/localforage.js:692:20)
    at Object.<anonymous> (/Users/montogeek/project/node_modules/localforage/dist/localforage.js:699:3)
    at Module._compile (module.js:398:26)
    at Module._extensions..js (module.js:405:10)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/montogeek/project/node_modules/babel-register/lib/node.js:134:7)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Module.require (module.js:354:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (auth.js:3:1)
    at Module._compile (module.js:398:26)
    at loader (/Users/montogeek/project/node_modules/babel-register/lib/node.js:126:5)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/montogeek/project/node_modules/babel-register/lib/node.js:136:7)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Module.require (module.js:354:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (index.js:4:1)
    at Module._compile (module.js:398:26)
    at loader (/Users/montogeek/project/node_modules/babel-register/lib/node.js:126:5)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/montogeek/project/node_modules/babel-register/lib/node.js:136:7)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Module.require (module.js:354:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (currencies.js:2:1)
    at Module._compile (module.js:398:26)
    at loader (/Users/montogeek/project/node_modules/babel-register/lib/node.js:126:5)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/montogeek/project/node_modules/babel-register/lib/node.js:136:7)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Module.require (module.js:354:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (index.js:2:1)
    at Module._compile (module.js:398:26)
    at loader (/Users/montogeek/project/node_modules/babel-register/lib/node.js:126:5)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/montogeek/project/node_modules/babel-register/lib/node.js:136:7)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Module.require (module.js:354:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (index.js:5:1)
    at Module._compile (module.js:398:26)
    at loader (/Users/montogeek/project/node_modules/babel-register/lib/node.js:126:5)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/montogeek/project/node_modules/babel-register/lib/node.js:136:7)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Module.require (module.js:354:17)
    at require (internal/module.js:12:17)
    at /Users/montogeek/project/node_modules/mocha/lib/mocha.js:219:27
    at Array.forEach (native)
    at Mocha.loadFiles (/Users/montogeek/project/node_modules/mocha/lib/mocha.js:216:14)
    at Mocha.run (/Users/montogeek/project/node_modules/mocha/lib/mocha.js:468:10)
    at Object.<anonymous> (/Users/montogeek/project/node_modules/mocha/bin/_mocha:403:18)
    at Module._compile (module.js:398:26)
    at Object.Module._extensions..js (module.js:405:10)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Function.Module.runMain (module.js:430:10)
    at startup (node.js:141:18)
    at node.js:980:3

When running:
babel src --out-dir dist it compiles without problem

@montogeek I'm not sure if this change has been published as part of a npm release, but #538 has completely removed the aforementioned code.


Auto update sponsors

is this feasible?

yes feasible but id say its easier just to update the markup directly. They don't change very often.


Bug #3883: Attach disk doesn't check cluster compatibility.

Hi ! This is a fix for bug #3883. Any comments or review will be appreciated :).
http://dev.opennebula.org/issues/3883

merged in master, check 17f38ea37ef30b2571db5158a14bf39d61290adf. I've improved some of the previous checks.
THANKS!!!!!!


feat: add anoncreds interface

And use it in Issue Credential v2 and Present Proof v2.
This PR supersedes #2191. As compared to #2191, this PR includes the required changes to use revocation with the generic anoncreds interface. Additionally, I've cleaned up this branch quite a bit. We had some unsuccessful detours (led by me lol) that resulted in both a messy history and changes in places that didn't need changes in the end.
Due to the need to clean up history, the contributions of my collaborators have unfortunately been obscured. Thank you @burdettadam and @cjhowland for all of your work on this!
As discussed with @swcurran, the intent of this PR is to have it merged to a feature branch (as in not merged to main) and for work to continue on the feature branch. I will create a number of issues reflecting things we hadn't gotten to yet or explicitly set aside for later as well as calling out discoveries that warrant further discussion.
Here is a brief summary of the changes that are included in this PR:
Changes
Added AnonCreds Registry and plugin interface

This is a generic AnonCreds registry interface. It defines a registrar and resolver abstract base class which are to be implemented by plugins. The plugged in resolvers and registrars are then registered with the main registry interface which selects the appropriate resolver/registrar for a given identifier and operation.
Interface found in aries_cloudagent.anoncreds.registry
ABCs found in aries_cloudagent.anoncreds.base
Associated models for generic representations of schemas, cred defs, and revocation artifacts found in aries_cloudagent.anoncreds.models

Added default registry for "legacy indy"

Found in aries_cloudagent.anoncreds.default.legacy_indy
Uses the aries_cloudagent.ledger to send transactions to indy networks.
Does NOT support endorsement protocol flow.

Added stubs for did:web and did:indy

These reside alongside the legacy_indy registry but are just stubbed out for now.

Added AnonCreds Issuer, Verifier, and Holder interfaces

Found in aries_cloudagent.anoncreds.{issuer,verifier,holder}
These are very similar to but different from the original IndyIssuer, IndyVerifier and IndyHolder interfaces that existed previously.
The role of these interfaces has expanded slightly, especially for Issuer, to better abstract the details of credential artifact registration and creation when using the generic anoncreds interface.

Added AnonCreds Revocation interface

Found in aries_cloudagent.anoncreds.revocation
This is intended to replace several components: IssuerRevRegRecord, RevocationRegistry, and IndyRevocation.
The components it replaces remain in place until all responsibilities have been moved.
There was an unfortunate amount of conceptual overlap between these components. On top of this, their responsibilities were confused over time, resulting in models/records doing more than the probably should have.
Implements a create_credential method similar to AnonCredsIssuer.create_credential. The issuer version supports credentials for cred defs that do not support revocation. The revocation version supports credentials for cred defs that do support revocation. The separation results in a cleaner implementation on both sides and cleaner split in responsibilities.

Update Issue Credential v2 indy format handler to use AnonCreds interface

Generally only minor tweaks with the exception of a cleaned up issue_credential; previously, this method made calls directly to the ledger with Indy specific revocation details being handled at this layer. These details have been moved down the stack to AnonCredsRevocation.create_credential.

Update Present Proof v2 indy format handler to use AnonCreds interface

Generally minor tweaks.

Update Revocation Manager

This component bridges the gap between protocol records and IssuerCredRevRecords and AnonCreds details.
Updated revoke and publish methods to use the generic interface.
There remains some Indy-isms in update_rev_reg_revoked_state. I believe this can be translated to a more generic operation but I haven't had a chance to take a closer look at the revocation recovery pieces yet.

Added AnonCredsTailsServer and updated BaseTailsServer

In order to publish a tails file to the tails server, we have to take a different tactic due to when rev reg def ids are available and opportunities for invalid URL values to be in the rev reg def id. Now, we upload by hash instead of rev reg id.
We have a branch on our fork of indy tails server that implements the new endpoint: https://github.com/Indicio-tech/indy-tails-server/tree/fix/put-get-file-backwards-compat

Added Admin endpoints for AnonCreds operations
post /anoncreds/schema
get /anoncreds/schema/{schemaId}
get /anoncreds/schemas
post /anoncreds/credential-definition
get /anoncreds/credential-definition/{cred_def_id}
get /anoncreds/credential-definitions
post /anoncreds/revocation-registry-definition
post /anoncreds/revocation-list
put /anoncreds/registry/{rev_reg_id}/tails-file
put /anoncreds/registry/{rev_reg_id}/active
post /anoncreds/revoke
post /anoncreds/publish-revocations

These behave more or less as expected when compared to /schemas, /credential-definitions, /revocation/*, etc.
This is currently the only flow supported. Automated setup flow is in the works.

Updated BaseLedger to behave as needed for the legacy indy registry

The ledger implementation previously did some funky stuff with passed in IndyIssuer to both create and publish anoncreds artifacts. The responsibility of the ledger has been reduced to only publishing.
These changes were implemented destructively but don't have to be if we want to better support backwards compatibility of Indy specific components.
Some improvements were made to error handling to clean up the flow of some methods (see aries_cloudagent.ledger.error)

Updates to Dockerfiles, requirements, setup to add anoncreds dep

Currently pulling directly from git repo since no package is published to PyPI yet
Binary also pulled from github releases page

Notably missing changes

Issue Credential v1 and Present Proof v1 implementation has not been updated
Old endpoints are still present but are in various states of functional; these will either need to be deprecated or adapted
Removal of deprecated components like IssuerRevRegRecord; we need a migration plan here, too
There are some shortcomings in link secret handling as caused by the anoncreds library not accepting a memory view (see https://github.com/hyperledger/anoncreds-rs/issues/202#issuecomment-1581415680)
Additional rearranging of components like aries_cloudagent.ledger; several should be moved to somewhere in anoncreds.default.indy or similar
Models for portions of AnonCreds credentials are still defined in aries_cloudagent.indy -- moving these components was omitted for a cleaner set of changes in this PR (not moving these reduced the number of lines changed by half)
In general, backwards compatibility with previously created anoncreds objects. Holder and verifier roles are likely fine but Issuer will need a migration plan.
Updates to tests. Sorry :grimacing: -- we have been testing using an integration style test that calls the added admin API endpoints. I have not included these tests in this PR for the sake of cleanliness.
Automated setup of revocation artifacts -- I have some WIP but opted to hurry up and open this PR rather than wait for me to finish.
did:indy and did:web implementations

FYI - @usingtechnology
@dbluhm — thanks for the documentation!

@usingtechnology — once you have looked at #2233, jump to this to get to a point we can merge it into a dev branch?  We don’t have to worry right now about the tests passing. Don’t worry if you can’t do that today, and don’t let it interfere with your Friday.  I’ll work on a meeting for (hopefully) Monday so we can go over this and plan next steps.

i think we can merge and i can do those little touch ups.


Handle variables better, add comments and clean up code

https://github.com/Ostronkex/100-Days-of-Code-The-Complete-Python-Pro-Bootcamp-Solutions/blob/572a4ec17fb5bcc17ec0da5f499a8fdd1ebe7693/Day9/SilentAuction.py#L16-L26
Handle variables better, add comments and clean up the code.
Clear the screen properly instead of printing 100 empty lines

The method of clearing the screen by printing 100 empty lines was the method I was supposed to use according to the course. I'm certain I'll eventually learn of a better way to do this, I will return to this project then and also fix the variable handling.
The program works fine in the meantime.


Ask for a filename instead of a directory name when creating a file

When you create a file via the Remote-FTP context menu, the dialog says "Enter the path for the new folder".
The usage for the AddDialogs constructor is new AddDialog (initialPath, isFile).
The true for isFile was missing.

Manually


Unable to update information in ARG_000001 BCO

Describe the bug
Information in required fields is not saved after each update in ARG_000001 BCO.
To Reproduce

Go to 'IO Domain'
The updated file name and URI are not saved for 'Input Subdomain'

Expected behavior
The above updated information that are missing need to be shown in this BCO, in order to proceed to final completion.
Screenshots
Desktop (please complete the following information):

OS: MacOS
Browser  Safari

Additional context
N/A

Was not able to replicate issue


Pressing the home button in settings should go home

Is your feature request related to a problem? Please describe.
I often find myself pressing the home button when I'm in the settings screen, then being surprised that nothing happens.
Describe the solution you'd like
It would be nice if pressing the home button when in the setting screen went back to the home screen (i.e. dismissed the settings).
Describe alternatives you've considered
I'm aware of the "X" button but I nearly always press home first and so get interrupted.
Additional info
It's just a tweak that would make me happy.

I implemented this as part of my fork (https://github.com/jrpie/Launcher/), see ef16d70
Since many of the changes I made are a matter of taste (and this repo doesn't seem to be actively maintained any more) I decided not open a PR but just publish it as a separate app.


Added allowed words for rigged

TrumpScript needs to be able to say that the election was rigged!

Excellent addition.


Add DNS support for PWD instances

:bell: @marcosnils

It won't fail! It will return the first value, which is the entire string.
On Fri, Feb 17, 2017, 07:57 Marcos Nils<EMAIL_ADDRESS>wrote:

@marcosnils commented on this pull request.
In api.go
https://github.com/franela/play-with-docker/pull/94#discussion_r101733602
:

@@ -119,3 +130,29 @@ func main() {
}
log.Fatal(s.ListenAndServeTLS("", ""))
}

+func handleDnsRequest(w dns.ResponseWriter, r *dns.Msg) {

if len(r.Question) > 0 && strings.HasSuffix(r.Question[0].Name, ".play-with-docker.com.") && strings.HasPrefix(r.Question[0].Name, "ip") {

// this is something we know about and we should try to handle

question := r.Question[0].Name

domainChunks := strings.Split(question, ".")

tldChunks := strings.Split(strings.TrimPrefix(domainChunks[0], "ip"), "-")

Question: "-" might now always come right?. Remember that we can also
handle stuff like ip10_0_0_1.play-with-docker.com:8080 for which this
split will fail.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/franela/play-with-docker/pull/94#pullrequestreview-22471388,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIhp4wxsknJGoY2l-2_Jh0_nLOWfr5Iks5rdX0vgaJpZM4MDYtv
.

It won't fail! It will return the first value, which is the entire string.

right, I didn't see the split above. LGTM, we just need to fix the domain thing and we're good to go!.


Skip test_unwriteable when tests are run as root

root can always write to any directory, so this test will fail, incorrectly.

root can always write to any directory

Not strictly true, e.g. read only filesystems, and (I think) the immutable attribute would still prevent root writing. Permission wise, you're right.

Fair enough. I meant in terms of permissions, which is how this test attempts to disable writing.


Improvements for analyze_db tool

See #264, #265

[x] Open LMDBs as read-only
[x] Allow quick read for large databases
[x] Write tests
[x] Expose log like #222

Ready for merge. @gheinrich, any feedback?

That looks very good to me.

Ok great! I've rebased to master to ensure no conflicts came up with the recently merged PRs, and I've added notes to close issues #264 and #265 in the commit messages.
Merge at your convenience.


[Enhancement] DeltaLake supports reading metadata without stat generated by older versions

Why I'm doing:
What I'm doing:
The metdata generated by delta lake has no stat.
{"commitInfo":{"timestamp":1720172614781,"operation":"WRITE","operationParameters":{"mode":"Append","partitionBy":"[]"},"readVersion":0,"isBlindAppend":true,"operationMetrics":{"numFiles":"4","numOutputBytes":"2440","numOutputRows":"4"}}}
{"add":{"path":"part-00000-8bae0835-6d1e-441a-bb16-72512018f2c3-c000.snappy.parquet","partitionValues":{},"size":623,"modificationTime":1720172614000,"dataChange":true}}
{"add":{"path":"part-00001-0cf492f8-f661-497f-8e1b-696cb807db72-c000.snappy.parquet","partitionValues":{},"size":623,"modificationTime":1720172614000,"dataChange":true}}
{"add":{"path":"part-00002-15c565e6-319a-42a4-a622-a01a71d4398b-c000.snappy.parquet","partitionValues":{},"size":623,"modificationTime":1720172614000,"dataChange":true}}
{"add":{"path":"part-00003-8a267696-b2ea-42d4-aff6-0116dc2f5941-c000.snappy.parquet","partitionValues":{},"size":571,"modificationTime":1720172614000,"dataChange":true}}

What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.3
[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

@Mergifyio backport branch-3.3


Detect keywords Vs Identifiers ambiguity.

We have the strings of the keywords. either those strings are passed directly as strings
or as simple regExps which we can extract the string from.
So we can check if any pattern could match these keywords
And if so validate that the longer_alt property is used correctly.

I think this should be split up into several different validations.

Unreachable Token - e.g: an Identifier appearing before a keyword.

Missing longer_alt property - e.g:

a keyword appearing before an identifier.
An Integer Token appearing before a decimal Token (although we cannot easily detect this).

The missing longer_alt property can be automatically fixed in most cases simply by adding it.

If multiple longer_alt properties must be added than it is an error.
If the token already has a longer_alt property we should not validate it as we assume the user knows what they are doing.
It should also be possible to define the longer_alt property as Lexer.NA to explicitly
tell the Lexer to ignore this validation, thus providing backward compatible behavior.

detecting Missing longer_alt property requires more in depth regExp analysis.


GetOAuthContextCookie throws InvalidOperationException

Hi!
We are using IndetityServer together with Google's OAuth2 as identity provider.
From time to time, the /issue/hrd/oauth2callback will fail with "Sorry, an error occurred while processing your request." and won't let user in. Event viewer has the following message and stack trace recorded:
Exception type: InvalidOperationException
    Exception message: cookie
   at Thinktecture.IdentityServer.Protocols.WSFederation.HrdController.GetOAuthContextCookie()
   at Thinktecture.IdentityServer.Protocols.WSFederation.HrdController.<OAuthTokenCallback>d__6.MoveNext()

I checked the cookies, and indeed idsrvoauthcontext has the value of "." there.. so doesn't look right.
Is this a known issue? Is there any way to fix it?

I am currently experiencing what seems to be at least a very similar issue.  We can wire up facebook as an Identity Provider and login to to register Relying Parties using hrd, however when we try to do the same with our google credentials we get the 'Sorry, an error occurred while processing your request.' message.  Was there ever a resolution to the above mentioned using v2?


passing objects between a code chunk and an exercise

I need to be able to load data (from a csv in the www directory) in a code chunk and have the data object accessible within an exercise. More generally, however, I can't figure out how to make objects accessible in an exercise. Very simple example below (quotes taken out so code will show on github). Help much appreciated.
---
title: "Tutorial"
output: rtutor::tutorial
runtime: shiny_prerendered
---

[triple quote]{r setup, include=FALSE}
library(rtutor)
knitr::opts_chunk$set(echo = FALSE)
[triple quote]

[triple quote]{r loadData}

x <- c(1,2,3,4,5 / 6, 7, 8, 9, 10)

[triple quote]

[triple quote]{r view-data, exercise=TRUE, exercise.eval=TRUE}

[triple quote]

[triple quote]{r view-data-hint}
x
[triple quote]

I've been creating shared chunks to coordinate between the knitr part of the document and the environment in which the exercises are defined.

create a setup chunk to be used in the exercises, before where the corresponding content in the knitr'ed part of the document occurs.
In an ordinary chunk --- that is, not an exercise --- refer to the chunk in (1) using ref.label=.
In an exercise chunk, refer to the chunk in (1) using exercise.setup =.

This worked perfectly. Thank you!


ntr: abolished FYPO:0005528  + histone methylation PMID:26804021

PMID:26804021
Here we found that the subnuclear localization of Sgo2–green
fluorescent protein (GFP) always overlapped with the knobs
(Fig. 4a), and that the knobs were completely lost in sgo2D cells
(Fig. 4b,c).

and increased histine H3-K36 tri-methylation H3K36me3

do you mean "abolished subtelomeric chromatin knob formation"?
"abolished decreased subtelomeric chromatin knob formation" would make no sense, but that's what the ticket title asks for ;)

One of these exists already, so this is the other one :)

my point is that you implicitly asked for a term with the nonsense name "abolished decreased subtelomeric chromatin knob formation"

"abolished subtelomeric chromatin knob formation
or
"decreased subtelomeric chromatin knob formation
(I think decreased exists, if so it was abolished)

abolished subtelomeric chromatin knob formation FYPO:0006260
abolished histone H3-K36 trimethylation during vegetative growth FYPO:0006261
edit file: 940e4f1fa6e57fb20827e9f138daab9844811dfb
release: e1793b5c1b70775665337bfa8900d7d6df6a4c67

wanted
increased histone H3-K36 trimethylation during vegetative growth FYPO:0006261
;)

oh, so the title doesn't parse "abolished ( FYPO:0005528 + histone methylation )"?
;)

oops.

no worries, my "oops" too for only looking at the title
might get to it today but won't promise right now ...

increased histone H3-K36 trimethylation during vegetative growth FYPO:0006263
edit file: 2011bfe344cf4469ff367678286868a97ecad1a5
release: e0803a1a324831c9be326794ec4c7fc8f797804c


add hdf5 reporter/writer and dataset for torch.util.dataloader

This PR is still in progress and requires some test cases. However, you can test and use this hdf5 reporter if needed (@MartinKliemank).
Open issues:

[ ] Some metadata is already implemented in the initialization. Should we make this more flexible?

Hello @McBs! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file lettuce/datautils.py:

Line 9:1: E302 expected 2 blank lines, found 1
Line 10:80: E501 line too long (97 > 79 characters)
Line 17:80: E501 line too long (89 > 79 characters)
Line 18:80: E501 line too long (89 > 79 characters)
Line 39:80: E501 line too long (95 > 79 characters)
Line 57:21: E225 missing whitespace around operator
Line 58:80: E501 line too long (113 > 79 characters)
Line 68:1: E302 expected 2 blank lines, found 1
Line 69:80: E501 line too long (88 > 79 characters)
Line 78:80: E501 line too long (83 > 79 characters)
Line 80:80: E501 line too long (86 > 79 characters)
Line 91:80: E501 line too long (83 > 79 characters)
Line 96:80: E501 line too long (94 > 79 characters)
Line 120:80: E501 line too long (80 > 79 characters)

@McBs are you still planning on finishing this? Otherwise, I'll close this PR.

Yes, the PR is scheduled to be finished this month.


added iris dataset classification

Changes proposed
Adding Irish data classification.

Check List (Check all the applicable boxes)

[ x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ x] This PR does not contain plagiarized content.
[x ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Hey @SOUMOJIT-CHAKRABORTY please add readme of the project by describing about it !
and please remove that .DS Store file from the main file

okay

@Anubhavdevv  done

Please improve the readme with proper documentation and images attached for the reference


no idea what to say, but here you go

doesn't allow my game to start. Crashes at 100%. Ignore my crafttweaker scripts
log:
latest.log
Modlist:

forgot to add that i removed chocolate. Hence why you don't see it in the mod list

Debug log?

I've posted it above

No, you posted the latest log, not the debug log.

aight, i'll download it again and post it then

debug.log

What is "helium" and where is it from? At a wild guess that might be conflicting with chocolate.

It's not helium as I have tested the mod pack without helium and it still crashes
But here's the mod:
https://www.curseforge.com/minecraft/mc-mods/hydrogen-reforged


Box-sizing should be border-box by default.

That's an easy one to implement and it does make a lot of sense.

@rafaelcastrocouto It's not about this plugin. And we can't know where need to add this. So, not)

@rafaelcastrocouto, I was thinking about how to handle these situations, too. I have some options:

Inject 2 rules at the top of the stylesheet
* { box-sizing: inherit; }
:root { box-sizing: border-box; }

And possibly replace any box-sizing: initial declarations with box-sizing: border-box

Recommend a CSS library that does this for you already, like Sanitize.css

What do you think?

Since Sanitize does way more than adding box-sizing, I would go for the first one.
But I would only add the 2nd line :root { box-sizing: border-box; } and leave all other declarations unchanged.
That would make easier to control exceptions and avoid unnecessary !important.

@rafaelcastrocouto, do you mean * { box-sizing: border-box; }? Because :root { box-sizing: border-box; } won’t do anyone any good.

Yes, u r right ... my bad. :root will only apply to the <html> tag.

I’m going to ask if box-sizing should really have been inherit all along with border-box as an initial root value. If the answer is "no, it should have been box-sizing at an element level all along” then I’ll add this.

We have our answer. https://twitter.com/tabatkins/status/674325928843993088
No inheritance, therefore:
* { box-sizing: border-box; }

:+1:

Resolved by https://github.com/jonathantneal/postcss-time-machine/commit/509c79cd8ace39f21612da496079d1d83ec2d96f and published to npm! Thanks, @rafaelcastrocouto.


Name your decision forest models

I would like to be able to explicitly name my model. I've seen that the models have a name attribute but it does not appear to be possible to set this manually.
I've tried:
setattr(model, 'name', 'my_cool_model')

And:
tfdf.keras.RandomForestModel(name = 'my_cool_model')

The error indicates that the attribute name is already used. You can use another name e.g. model.model_name = 'my_cool_model' will work.
Alternatively, you can store this model in a new class e.g. ModelAndMetaData. This way, there is no risk to override an existing attribute and possibly perturbe the internal logic of the model.

Is this not a functionality gap as you can do this with the standard keras API?

You are right. I did not realize this was part of the Keras API :).
The change has been submitted, and it will be part of the next TF-DF release (v0.1.8).

Thank you :)

The change was published in TF-DF 0.1.8.


Bump the maven plugin version to work nice with Mac/Java 1.7

Had hard time running mvn package from shell on Mac (worked fine with Ubuntu).
The only thing that really helped was bumping maven plugin.
I am not sure it makes sense to push this to master, so feel free to reject the PR if you think it's dangerous.

Sorry for the delay. Did you test it with ubuntu?

Not sure, have no Ubuntu at hand. Can anyone try and verify?

Hi, @MatejBalantic, since it looks like no one with a linux box can test it, I'll merge it and if any linux user gets a problem with that in the future I hope a new issue will be opened :-)
Thanks!

I have been running it with Ubuntu 14.04 and have not noticed any issues


WORK ON LOCAL BUT NOT ONLINE ! What To Do

The package works fine when i'm on my local machine but as soon I upload it in my CPanel it show's this error.
FIRST PICTURE LOCAL WORKS FINE

SECOND ONE CPANEL

This error returns when there is a problem with your class namespace or the file doesn't exist.
Check out that you have this class with the correct namespace or maybe there is a problem with your composer to load the right namespcae.


Broken types for arrays of union types

The latest release update (version 1.8.1) introduced array types using the typical brackets-suffixed notation (${content}[]). However, the generator seems to produce faulty type definitions when the array is to contain a union of types or a union of enum values. That problem has not occured with previous versions using the Array<T> notation. An easy fix respecting the intentions of release 1.8.1 may be to put the content type inside parentheses to which the brackets-suffix can be applied.
Screenshots of the problem
Original Swagger definition:

Generated code: 1.8.1 generated type to the left, pre-1.8.1 generated type to the right

@jabrandes Hello! Thanks for the issue report!
I will fix it right now!

@js2me Thanks a lot! :smiley:

It should be fixed in release 1.8.2 🙂