Import replaced same events from other calender

Duplicates should only be replaced when they are in the same calender

This is the intended behaviour given the presence of a UID, assuming the 'Keep UIDs' setting is enabled. UIDs are intended to ensure the events are uniquely represented.
I agree that this may be counter-intuitive or undesirable given how some people use multiple calendars currently. I will add an option to make UUIDs unique globally and default it to off.


Adding DialogMaxWidthTestCase to a test suite

The test fails on travis but not on my Windows machine! It seems that travis and my machine are using different fonts to display the dialog title which results in different dialog widths when the width can freely follow the width of the title.

I closed it, as the test as been added in the test suite in this commit : 4a75ce0


Replace todo.md by real page

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
If a user follow a todo link, the sidebar is closed because the todo.md page has no category.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

What is the expected behavior?
If we create an empty page, using the todo layout (like for loadflow, the menu is open and the corresponding item is selected

What is the motivation / use case for changing the behavior?
Make the navigation easier

Please tell us about your environment:

PowSyBl Version: ...
OS Version: ...

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, spectrum, etc)

(if a question doesn't apply, you can delete it)

Not relevant since the sidebar doesn't exist anymore


git secrets fix

Description
Git secrets was failing locally to catch failed patterns within our test databases. Interestingly, I had setup and installed git-secrets manually using brew. This failed to capture the sql database secret warnings, but would catch fake keys, such as AKIAIOSFODNN7EXAMPLES, which led me to believe that it was working as expected.
Uninstalling locally with brew uninstall git-secrets and then reinstalling using the UI script npm run install-git-secrets seemed to fix the local issue, and caused git secrets --scan to start picking up the expected results.
If you aren't sure if git secrets is working locally, I'd suggest scanning one of the database files, such as test/smoke_test_db.sql while the line  test/smoke_test_db.sql:.*public.databasechangelog isn't in .gitallowed. If your scan passes, git secrets may be broken.
Issue
A link to a github issue or SEAB- ticket (using that as a prefix)
Please make sure that you've checked the following before submitting your pull request. Thanks!

[ ] Check that your code compiles by running npm run build
[ ] If this is the first time you're submitting a PR or even if you just need a refresher, consider reviewing our style guide
[ ] Do not bypass Angular sanitization (bypassSecurityTrustHtml, etc.), or justify why you need to do so
[ ] If displaying markdown, use the markdown-wrapper component, which does extra sanitization
[ ] Do not use cookies, although this may change in the future
[ ] Run npm audit and ensure you are not introducing new vulnerabilities
[ ] Do due diligence on new 3rd party libraries, checking for CVEs
[ ] Don't allow user-uploaded images to be served from the Dockstore domain

npm run install-git-secrets works for me, as in it correctly flags the DB dumps. My previous setup didn't flag the DBs (which was manually downloading with brew install git-secrets and a subsequent git secrets --install). I'm not sure why this is the case, but the two SQL database dumps should have been added to .gitallowed when they were initially commit, but they seem to have skated by unseen. This PR adds them to .gitallowed so git secrets --scan no longer reports them, as they are false positives.
It seems our CI scanning may not be catching git secrets issues, similar to the local issue that I had? Not certain, I think @garyluu was taking a look?

Ah, I see. I think the idea is to scan new commits, not scour the past for existing secrets.
If I'm understanding right, I don't think you should do this PR. If you add a new token to the test database, we would want it scanned and you would need to explicitly approve/ignore it. ideally and probably always you will add a fake secret, but you could accidentally add a real secret, and the hook should force you to double check.

I noticed we had secrets issues because I was making unrelated commits and somehow git secrets complained about the two files and wouldn't let me commit

I noticed we had secrets issues because I was making unrelated commits and somehow git secrets complained about the two files and wouldn't let me commit

If I'm understanding this correctly, we have two main ways we can implement git secrets:

Only scan new commits
Scan the entire commit tree

And we have local installments of git secrets that behave differently:

Some only scan new file changes
Some scan the entire commit tree

No strong opinions from me, I think both approaches are reasonable, but is there a purpose to .gitallowed if we are only scanning the latest changes? If a new change is caught by git secrets, you'd presumably skip verification for the offending commit and it would never be scanned again (unless modified somewhere down the line), correct?

Going to close this PR and suggest we keep the current git-secrets functionality pattern. Feel free to reopen if anyone disagrees.


getNewMatches seems to be malfunctioning

It seems to be an error when i try to get new matches
new_matches = session.getNewMatches(quickload=True)
Getting not-interacted-with, NEW MATCHES
[>-----------------------------] 0% of the new matches handled.openchat 2:Message: no such element: Unable to locate element: {"method":"xpath","selector":"//a[@href="/app/messages/my-likes"]"}
(Session info: chrome=87.0.4280.141)
(Driver info: chromedriver=87.0.4280.88 (89e2380a3e36c3464b5dd1302349b1382549290d-refs/branch-heads/4280@{#1761}),platform=Windows NT 10.0.18363 x86_64)

Corrected adding the following statement on line 59 of match helper:

Corrected adding the following statement on line 59 of match helper:

Hi @bashback,
Thanks for noticing bugs and helping to fix them!
I changed line 59 of match_helper as you suggested, so it should work again in the newest update.
Have a nice day!
Fred

Hi @bashback,
Thanks for noticing bugs and helping to fix them!
I changed line 59 of match_helper as you suggested, so it should work again in the newest update.
Have a nice day!
Fred


On running "sudo ./build_ubuntu.sh" command I am getting error

On running "sudo ./build_ubuntu.sh" command I am getting error.
 They have been ignored, or old ones used instead.
WARNING: apt does not have a stable CLI interface yet. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
Package build-essential is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'build-essential' has no installation candidate
The command '/bin/sh -c apt update && apt install -y build-essential       && npm i && npm i --only=dev       && npm run build       && npm prune       && apt remove -y build-essential' returned a non-zero code: 100
Creating network "build-blockchain-insurance-app_default" with the default driver
Pulling insurance-ca (insurance-ca:)...
ERROR: The image for the service you're trying to recreate has been removed. If you continue, volume data could be lost. Consider backing up your data before continuing.
Continue with the new image? [yN]y
Pulling insurance-ca (insurance-ca:)...
ERROR: pull access denied for insurance-ca, repository does not exist or may require 'docker login'
anant@anant-VirtualBox:~/build-blockchain-insurance-app$
Please help me to resolve it.

docker login?

I am also facing the same error even after docker login

@Gurpret7 What's the host OS you are using?

Ubuntu 18 on VM

I have this working on Ubuntu 18 bare metal. Will check on a VM. I am assuming network is configured correctly since you could get the code.

@Gurpret7 OK just tested on Ubuntu 18.04 LTS VM. No issues. Let me know if you need anything in specific.

@subbaraok Thanks for your response & time.
while running the code, I m getting error
ERROR: pull access denied for insurance-ca, repository does not exist or may require 'docker login'
It worked for you fine. That sounds great!!
But why I m getting the error? if you can share any input. That would be appreciated.

@Gurpret7 please make sure to login to docker using "docker login" command. This step is immediately after cloning the repo.

You have error:
W: Failed to fetch http://deb.debian.org/debian/dists/jessie/InRelease
W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/InRelease
...
Are you working behind corporate proxy. If this is the case, do the following:
Use this alias to create a docker-build command with proxy settings (chnage your_proxy:your_port with your corporate proxy seting):
Step 1:
cat << EOF >> ~/.bashrc
export HTTP_PROXY=http://your_proxy:your_port
export HTTPS_PROXY=http://your_proxy:your_port
EOF
Then source the new bashrc:
. ~/.bashrc
Step 2:
Edit file docker-images.sh and add proxy parameters in lines "docker build ..." as:
docker build --build-arg http_proxy=http://your_proxy:your_port --build-arg https_proxy=http://your_proxy:your_port -t orderer:latest orderer/
docker build --build-arg http_proxy=http://your_proxy:your_port --build-arg https_proxy=http://your_proxy:your_port -t insurance-peer:latest insurancePeer/
docker build --build-arg http_proxy=http://your_proxy:your_port --build-arg https_proxy=http://your_proxy:your_port -t police-peer:latest policePeer/
docker build --build-arg http_proxy=http://your_proxy:your_port --build-arg https_proxy=http://your_proxy:your_port -t shop-peer:latest shopPeer/
docker build --build-arg http_proxy=http://your_proxy:your_port --build-arg https_proxy=http://your_proxy:your_port -t repairshop-peer:latest repairShopPeer/
docker build --build-arg http_proxy=http://your_proxy:your_port --build-arg https_proxy=http://your_proxy:your_port -t web:latest web/
docker build --build-arg http_proxy=http://your_proxy:your_port --build-arg https_proxy=http://your_proxy:your_port -t insurance-ca:latest insuranceCA/
docker build --build-arg http_proxy=http://your_proxy:your_port --build-arg https_proxy=http://your_proxy:your_port -t police-ca:latest policeCA/
docker build --build-arg http_proxy=http://your_proxy:your_port --build-arg https_proxy=http://your_proxy:your_port -t shop-ca:latest shopCA/
docker build --build-arg http_proxy=http://your_proxy:your_port --build-arg https_proxy=http://your_proxy:your_port -t repairshop-ca:latest repairShopCA/

i have the similar error when running sudo ./build_ubuntu.sh
i'm running on Ubuntu 18.04
`Step 9/11 : RUN apt update && apt install -y build-essential       && npm i && npm i --only=dev       && npm run build       && npm prune       && apt remove -y build-essential
---> Running in a5da58b543ba
WARNING: apt does not have a stable CLI interface yet. Use with caution in scripts.

Building dependency tree...
Reading state information...
All packages are up to date.
 They have been ignored, or old ones used instead.
WARNING: apt does not have a stable CLI interface yet. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
Package build-essential is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'build-essential' has no installation candidate
The command '/bin/sh -c apt update && apt install -y build-essential       && npm i && npm i --only=dev       && npm run build       && npm prune       && apt remove -y build-essential' returned a non-zero code: 100
Pulling shop-ca (shop-ca:latest)...
Traceback (most recent call last):
File "/usr/bin/docker-compose", line 11, in
load_entry_point('docker-compose==1.17.1', 'console_scripts', 'docker-compose')()
File "/usr/lib/python2.7/dist-packages/compose/cli/main.py", line 68, in main
command()
File "/usr/lib/python2.7/dist-packages/compose/cli/main.py", line 121, in perform_command
handler(command, command_options)
File "/usr/lib/python2.7/dist-packages/compose/cli/main.py", line 952, in up
start=not no_start
File "/usr/lib/python2.7/dist-packages/compose/project.py", line 431, in up
svc.ensure_image_exists(do_build=do_build)
File "/usr/lib/python2.7/dist-packages/compose/service.py", line 312, in ensure_image_exists
self.pull()
File "/usr/lib/python2.7/dist-packages/compose/service.py", line 1029, in pull
output = self.client.pull(repo, tag=tag, stream=True)
File "/usr/lib/python2.7/dist-packages/docker/api/image.py", line 381, in pull
header = auth.get_config_header(self, registry)
File "/usr/lib/python2.7/dist-packages/docker/auth.py", line 50, in get_config_header
authcfg = resolve_authconfig(client._auth_configs, registry)
File "/usr/lib/python2.7/dist-packages/docker/auth.py", line 97, in resolve_authconfig
authconfig, registry, store_name
File "/usr/lib/python2.7/dist-packages/docker/auth.py", line 142, in _resolve_authconfig_credstore
'Credentials store error: {0}'.format(repr(e))
docker.errors.DockerException: Credentials store error: StoreError('Credentials store docker-credential-secretservice exited with "Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached".',)`

I solved problem with step 9/11 by following this:
https://development.robinwinslow.uk/2016/06/23/fix-docker-networking-dns/

follow steps from issue 58


Ignore attribute changes in automation trigger from/to

Description:
This changes from/to filters on automation triggers to only consider actual state changes, not attribute updates. The change only makes a difference if just one of from/to is specified.
Using state as an alias of to is deprecated because it is ambiguous and redundant.
These changes were agreed upon in #7556.
Related issue (if applicable): fixes #6299 #7556
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#2665
Example entry for configuration.yaml (if applicable):
This example no longer arms the alarm when GPS coordinates are updated while the device is home:
automation:
  - alias: ‘Arm alarm when leaving home'
    trigger:
      - platform: state
        entity_id: device_tracker.amelchio
        from: ‘home’

Checklist:
If user exposed functionality or configuration variables are added/changed:

[X] Documentation added/updated in home-assistant.github.io

If the code does not interact with devices:

[X] Local tests with tox run successfully.
[X] Tests have been added to verify that the new code works.

I have added a test and updated the documentation. I am happy with this now but would appreciate a review from @armills.
(Note: it turned out that for without to is already forbidden.)


Add frontend flag -swift-concurrency={off|limited|on}

Replace -warn-concurrency with a more granular option
-swift-concurrency=, where the developer can select one of three
different "modes":

off disables Sendable checking for most cases. (This is the Swift
5.5 and Swift 5.6 behavior.)
limited enables Sendable checking within code that has adopted
Swift concurrency. (This is currently the default behavior.)
on enables Sendable and other concurrency checking throughout
the module. (This is equivalent to -warn-concurrency now).

There is currently no distinction between off and limited. That
will come soon.
Implements the flag part of rdar://91930849.
@DougGregor
DougGregor committed 6 hours ago
7a724c4

@swift-ci please smoke test

@DougGregor
https://github.com/apple/swift/pull/42445/files#diff-2ac349a051866d6b796d097a12719ea56da1b59e7b74bd8dc7c25e0c46636341R689
Doug, is it fair to say that this is an extremely breaking change? Thousands of lines of code will no longer compile due to the increase of strictness, and I suspect there's no way to override the flag anymore?


Improve channel selection UI

I'm thinking something in the header could work.

Done enough for now, but obviously the widget will have to change if the list gets larger or configurable.


[BUG] Default poll mode doesn't work for single vote

No matter which of the two options you choose, the default mode for a poll in the dialog is always multiple vote.

Fixed in v1.0.2
Please update the module and if something is still not working as expected, please let me know


Make sure that participants can generate certificates

Students are reporting that they are unable to generate certificates after completion of the course. Thank you!

Thank you for this and sorry for the delay. This has been resolved!


dupl things two switch/case clauses are the same when they differ in variable type creation

Consider this go code:
switch raw.VersionField {
// v1.Version and v2.Version are just strings aliases.
case v1.Version:
	dec := json.NewDecoder(bytes.NewReader(b))
	dec.UseNumber()
	var m v1.QueueMessage
	// some more code
case v2.Version:
	dec := json.NewDecoder(bytes.NewReader(b))
	dec.UseNumber()
	var m v2.QueueMessage
	// some more code, similar to the previous clause.
}

Running dupl on this returns:
duplicate of ./api.go:119-150 (dupl) // Lines belong to the second clase
duplicate of ./api.go:87-118 (dupl)  // Lines belong to the first clause

There are two issues here:

These two cases aren't the same, and differ by the var m v1.QueueMessage line.
Presuming that they are the same, they're linking each other in the error message. I guess the link should be one way, from the duplicate (the second clause, the with v2) to the first.

This is just an issue related to the method dupl uses for clone detection. It's a "false positive" match. The algorithm works only with token types, not their values. From certain angle I would say it is a duplicate because if both cases are that similar, their behaviour could be probably abstracted to an interface.
Ad 2. issue: I think it works as expected. You can check #2 where we have discussed the desired output format.
Did I miss something?

actually, this switch case is for initializing different structs which implement the same interface, so there isn't any further abstraction i can do in this case. if you say this is a FP than ok, but I think the chance for FPs should be mentioned in the README or something.

it also means i should unfortunately take this tool with a grain of salt, since not all comments are TP :\

That's just the way it is. You are right it should be more emphasized in README. It only contains one sentence about it (It ignores values of AST nodes, it cares just about the types.) so far. The reason is English is my second language. So I find it quite uncomfortable to write long passages of text.
dupl is a tool, it is not a source of truth. It should provide a user information about possible clones that would have been otherwise missed by the user.

Yeah, dupl is not a tool whose output can be run in CI and non-zero output can be considered a failure, the way, for example, vet is. It's more like golint, its output are hints, some of which may be helpful, some others may be noise.
On another note, in your original code, couldn't you factor out:
dec := json.NewDecoder(bytes.NewReader(b))
dec.UseNumber()

It seems that part is duplicated without necessity. It case it happens to lead to more readable, better code to factor it out, then dupl has been helpful even in this relatively false positive-y case.

I agree, and maybe you should quote from here in the README.

thanks for the quick response :)
hurray for awesome maintainers :+1:

You're welcome :-)


uORB change to avoid c struct inheritance

Also adds support for multiple topic pub/sub.

Thanks! I presume you have seen the travis fail?

Yeah, trying to get the chunks of the lpe pull request separated.

In master now.


[Bug] Long Query parameter value prevents editing

Overview

Insomnia Version: 5.2.0
Operating System:  MacOS 10.11.4
Summary:  Query parameter with long value prevents editing due to large url preview window and no scrolling

How To Reproduce

Create new request
Add a single query parameter with a very long value
You can no longer add any more query parameters or edit the just added one because the url preview window takes up the entire space and cannot be scrolled down

hi @reevesm, thanks for the report. Can you attach a screenshot of the problem?

I assume this is what you mean? Here's a screenshot of a fix I just implemented:

Yes, sorry I didn't get the screenshot to you yet. Looks like your solution solves the problem. Thanks for the quick turnaround.

Insomnia Version: 5.16.2
Operating System: Windows 7 Professional x64

This bug seems to occur also in the 5.16.2 version.

@murame please post a new issue with more details at to what your problem is


Rip out reference logic

Many thanks to contributing to nf-core/rnaseq!
To ensure that your build passes, please make sure your pull request is to the dev branch rather than to master. Thank you!
Please fill in the appropriate checklist below (delete whatever is not relevant). These are the most common things requested on pull requests (PRs).
PR checklist

[ ] PR is to dev rather than master
[ ] This comment contains a description of changes (with reason)
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If necessary, also make a PR on the nf-core/rnaseq branch on the nf-core/test-datasets repo
[ ] Ensure the test suite passes (nextflow run . -profile test,docker).
[ ] Make sure your code lints (nf-core lint .).
[ ] Documentation in docs is updated
[ ] CHANGELOG.md is updated
[ ] README.md is updated

Learn more about contributing: https://github.com/nf-core/rnaseq/tree/master/.github/CONTRIBUTING.md

Ok. Seeing as this is all going to be changed with DSL2 again anyway I will merge so I can create the dsl2 branch and start working on this 👍


Yukon Address Source

The current address source for Yukon that is listed is https://mapservices.gov.yk.ca/arcgis/rest/services/GeoYukon/GY_LandTenure/MapServer/42. According to personal correspondence the data provider, the following url should be the one that is used: https://open.yukon.ca/data/datasets/civic-address-point Data is available as an Esri shapefile, xml, kmz of fgdb. Licence for the data is here: https://open.yukon.ca/open-government-licence-yukon

Updated the data at https://github.com/openaddresses/openaddresses/pull/7563


I got ECONNREFUSED problem

One of power outlets works with TuyaOutlet plugin, but they doesn’t work with tuya-powerstrip.
I’ve gotten the device ID, IP address and local key.
Could you tell me what is wrong?
I got this error log.
[2018-6-10 16:47:30] [Tuya Powerstrip - ライト２] connect ECONNREFUSED <IP_ADDRESS>:6668
[2018-6-10 16:47:30] [Tuya Powerstrip - ライト１] connect ECONNREFUSED <IP_ADDRESS>:6668
[2018-6-10 16:47:30] [Tuya Powerstrip - ライト６] connect ECONNREFUSED <IP_ADDRESS>:6668
[2018-6-10 16:47:30] [Tuya Powerstrip - ライト５] connect ECONNREFUSED <IP_ADDRESS>:6668
[2018-6-10 16:47:30] [Tuya Powerstrip - ライト４] connect ECONNREFUSED <IP_ADDRESS>:6668
[2018-6-10 16:47:30] [Tuya Powerstrip - ライト３] connect ECONNREFUSED <IP_ADDRESS>:6668
here is my config.json
"accessories": [
{
  "accessory": "TuyaOutlet",
  "name": "Tuya Outlet221",
  "devId": "01205862dc4a341ac124",
  "localKey": "a0f0c285dc88041b"
},

{
    "accessory": "TuyaPowerStrip",
    "name": "ライト１",
    "description" : "Tuya Power Strip Outlet 1",
    "ip": "<IP_ADDRESS>",
    "devId": "01205862dc4a341ac124",
    "localKey": "a0f0c285dc88041b",
    "dps" : 1,
    "apiMinTimeout" : 100,
    "apiMaxTimeout" : 1000,
    "apiRetries": 1,
    "apiDebug" : false,
    "refreshInterval" : 120,
    "debugPrefix" : "~~~!~~~ ",
    "debug" : false,
    "deviceEnabled" : true    },

{
    "accessory": "TuyaPowerStrip",
    "name": "ライト２",
    "description" : "Tuya Power Strip Outlet 2",
    "ip": "<IP_ADDRESS>",
    "devId": "01205862dc4a341ac124",
    "localKey": "a0f0c285dc88041b",
    "dps" : 2,
    "apiMinTimeout" : 100,
    "apiMaxTimeout" : 1000,
    "apiRetries": 1,
    "apiDebug" : false,
    "refreshInterval" : 120,
    "debugPrefix" : "~~~!~~~ ",
    "debug" : false,
    "deviceEnabled" : true
},

{
    "accessory": "TuyaPowerStrip",
    "name": "ライト３",
    "description" : "Tuya Power Strip Outlet 3",
    "ip": "<IP_ADDRESS>",
    "devId": "01205862dc4a341ac124",
    "localKey": "a0f0c285dc88041b",
    "dps" : 3,
    "apiMinTimeout" : 100,
    "apiMaxTimeout" : 1000,
    "apiRetries": 1,
    "apiDebug" : false,
    "refreshInterval" : 120,
    "debugPrefix" : "~~~!~~~ ",
    "debug" : false,
    "deviceEnabled" : true
},

{
    "accessory": "TuyaPowerStrip",
    "name": "ライト４",
    "description" : "Tuya Power Strip Outlet 4",
    "ip": "<IP_ADDRESS>",
    "devId": "01205862dc4a341ac124",
    "localKey": "a0f0c285dc88041b",
    "dps" : 4,
    "apiMinTimeout" : 100,
    "apiMaxTimeout" : 1000,
    "apiRetries": 1,
    "apiDebug" : false,
    "refreshInterval" : 120,
    "debugPrefix" : "~~~!~~~ ",
    "debug" : false,
    "deviceEnabled" : true
},

{
    "accessory": "TuyaPowerStrip",
    "name": "ライト５",
    "description" : "Tuya Power Strip Outlet 3",
    "ip": "<IP_ADDRESS>",
    "devId": "01205862dc4a341ac124",
    "localKey": "a0f0c285dc88041b",
    "dps" : 5,
    "apiMinTimeout" : 100,
    "apiMaxTimeout" : 1000,
    "apiRetries": 1,
    "apiDebug" : false,
    "refreshInterval" : 120,
    "debugPrefix" : "~~~!~~~ ",
    "debug" : false,
    "deviceEnabled" : true
},

{
    "accessory": "TuyaPowerStrip",
    "name": "ライト６",
    "description" : "Tuya Power Strip Outlet 3",
    "ip": "<IP_ADDRESS>",
    "devId": "01205862dc4a341ac124",
    "localKey": "a0f0c285dc88041b",
    "dps" : 6,
    "apiMinTimeout" : 100,
    "apiMaxTimeout" : 1000,
    "apiRetries": 1,
    "apiDebug" : false,
    "refreshInterval" : 120,
    "debugPrefix" : "~~~!~~~ ",
    "debug" : false,
    "deviceEnabled" : true
}]

}

Is <IP_ADDRESS> your LAN IP for the tuya device? Also, are you certain no apps are running in the background on any device that controls these devices?  It only allows 1 connection from the lan to the device.

Thank you for your comment.
Yes,  <IP_ADDRESS> is my LAN IP for the tuya device.

I bought this wifi power strip and use it via Jinvoo Smart.
Wifi Power Strip: Geekbes / Jinvoo
https://www.ebay.com/p/WiFi-Smart-Power-Strip-Compatible-With-Alexa-Geekbes-Multi-plug-Timer-Outlets-4/7011116648
iPhone App: Jinoo Smart
https://itunes.apple.com/us/app/jinvoo-smart/id1182632835?mt=8
This app shows device’s IP address and I also check it on terminal.
tomoMac:~ tomo719$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=255 time=0.403 ms
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=255 time=0.329 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=255 time=0.333 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=255 time=0.351 ms
As your advice, I turn off the app but it doesn’t works.
I also reset the pairing of my device then I got this messages.
[2018-6-11 08:15:36] [Tuya Powerstrip - ライト２] connect ECONNREFUSED <IP_ADDRESS>:6668
[2018-6-11 08:15:36] [Tuya Powerstrip - ライト６] connect ECONNREFUSED <IP_ADDRESS>:6668
(node:8139) UnhandledPromiseRejectionWarning: Error: resolveIds() timed out. Is the device ID correct and is the device powered on?
at timeout (/Users/tomo719/.nodebrew/node/v10.3.0/lib/node_modules/homebridge-tuya-outlet/node_modules/tuyapi/index.js:121:11)
at Timeout.setTimeout (/Users/tomo719/.nodebrew/node/v10.3.0/lib/node_modules/homebridge-tuya-outlet/node_modules/p-timeout/index.js:19:13)
at ontimeout (timers.js:427:11)
at tryOnTimeout (timers.js:289:5)
at listOnTimeout (timers.js:252:5)
at Timer.processTimers (timers.js:212:10)
(node:8139) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:8139) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Can I use homebridge-tuya-powerstrip plugin without LAN IP for the tuya device?
With TuyaOutlet plugin, I checked my device working without LAN IP, but it allows only single outlet.

I'm so sorry, my device IP was wrong and after I correct that it was completely resolved!
Thank you so much :D


Add abstract function for null information

Reporter: Fiona La / @lafiona
Note: This issue was originally created as ARROW-12346. Please see the migration documentation for further details.

Marking this as resolved.
A public Valid property, which represents the null values in an Arrow array, was added to the arrow.array.Array classes in #35655.
Example:

>> a = arrow.array(uint64([1, 2, 3]), Valid=[true, false, true])

a =

[
  1,
  null,
  3
]

>> a.Valid

ans =

  3x1 logical array

   1
   0
   1


[SMALLFIX]Fix the logging message in ExecuteShellCollectInfoCommand

What changes are proposed in this pull request?
Fix Alluxio/new-contributor-tasks#633
Fix the logging message in ExecuteShellCollectInfoCommand.
Why are the changes needed?
Improve logging format.
Does this PR introduce any user facing changes?
No.

thanks Rianico for the improvement!

alluxio-bot,merge this please

alluxio-bot, merge this please


Powershell integrated console crashes when running Az cmdlets

Create ps1 script using Az cmdlet, e.g Get-AzKeyVaultSecret, and run the script from the integrated terminal.  Observe the console dies.


Upload functional tests step 1

replaced autonomous_setup.php by the corresponding include files from functional test folders
removed the overlaps between tools.inc and MsCommon.inc (likewise for pdo_tools.inc)
no longer create and drop temporary databases in some testsl; use test databases instead
create test tables as temporary ones if possible; if not, drop them after the tests

Coverage decreased (-19.5%) to 42.471% when pulling c6060e97665975e386146d388b02ce832d7a777d on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage decreased (-18.7%) to 43.325% when pulling 8e81dfa09d4d0b1aa184c6a05b3a01b8445cb97d on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage decreased (-18.7%) to 43.325% when pulling 554d2d9d3e3a28db36fe855014a227a86f07c5ab on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage decreased (-20.2%) to 41.749% when pulling f4aed36552bfbbb200adef0ce2731cac1b621384 on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage decreased (-0.08%) to 61.91% when pulling cc656ec1970681b07179a462e6ead4d7447fad68 on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage decreased (-20.3%) to 41.706% when pulling 00e4e90190784afcc5b36ed16fe5dfc85981f439 on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage decreased (-20.3%) to 41.706% when pulling 32f0f530b8d957dfc06612fd968f2d39a438d9dc on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage decreased (-20.3%) to 41.706% when pulling 02108069a28ac10fb1c1e3d5e5b63d1a804abd40 on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage decreased (-0.1%) to 61.867% when pulling 31cb487a3cccb48d55f0df5ca8399ebc12bbc2a7 on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage decreased (-0.1%) to 61.867% when pulling<PHONE_NUMBER>5fd3585a924b65d73afd22d183b4b2 on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage increased (+1.8%) to 63.844% when pulling 03ea90d3efa255cc12c55e4fbe7357ee9339cdd6 on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage decreased (-20.4%) to 41.628% when pulling 5740dc94ed4db646739b68ffc29f1bdc74ae4ab8 on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage increased (+2.7%) to 64.646% when pulling 16f43cc5664144eaeb23af577135ab5238b8a7db on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage increased (+2.9%) to 64.918% when pulling bafb9df0b07d0240dcfd43c46cea67132a04cdee on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage increased (+3.3%) to 65.316% when pulling d06938642d362a959b63501c3bd0f6b8dc627c70 on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage increased (+3.2%) to 65.244% when pulling c235f9cf6d91018a139892b17e69d38d3ec87f0f on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage increased (+4.03%) to 66.026% when pulling 8cca99a281918ace9e50e572d7268715a9fe7fe2 on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage increased (+4.4%) to 66.378% when pulling 2bebcd5718b7751c86141432ab91da8f3af27ca8 on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage increased (+5.4%) to 67.407% when pulling b21de0093d57c04dab242252122da47dd0044c50 on yitam:functional-tests into fb3663bca4370af8bf7e24039b26d5d632332e42 on Microsoft:dev.

Coverage increased (+5.6%) to 67.788% when pulling 78c0f6f4e689f48eca8ca4057ffc82687f58ece2 on yitam:functional-tests into ce6337709bd3c6180a007e188065992fbce7d44d on Microsoft:dev.

Coverage increased (+5.6%) to 67.745% when pulling 2fcff55432462193f1f7e06ef660f96f10f6d162 on yitam:functional-tests into ce6337709bd3c6180a007e188065992fbce7d44d on Microsoft:dev.

Coverage increased (+5.2%) to 67.402% when pulling a6ce2be894fdd4a64d07d681ab2585c11490de32 on yitam:functional-tests into ce6337709bd3c6180a007e188065992fbce7d44d on Microsoft:dev.

Coverage increased (+5.6%) to 67.745% when pulling 025dfdc2d964a954fe8948745bb4788980107f57 on yitam:functional-tests into ce6337709bd3c6180a007e188065992fbce7d44d on Microsoft:dev.


Hotfix for get()

HTTPService.get() was not returning JSON in some cases. This is now fixed.

Checks failed because Destiny API is currently down for maintenance.


fs.smbfs.SMBFS init fails due to share list request

The host I work with refuses to list the shares, so fs.smbfs.SMBFS init fails because it asks for said list (in https://github.com/althonos/fs.smbfs/blob/master/fs/smbfs/smbfs.py#L276)
Does fs.smbfs.SMBFS have to request the share list upon init? I know the name of the share I am interested in, so this request unnecessarily breaks functionality for me.

I don't think it does, I'm trying a patch that doesn't scan shares unless absolutely required. If that works, I'll push a new release. (sorry about the delay).


BulkInsertOrUpdateAsync is throwing exception in version 3.1.1

Unable to cast object of type 'System.Data.SqlClient.SqlConnection' to type 'Microsoft.Data.SqlClient.SqlConnection'.

My code was System.Data.SqlClient in DbContext


Add an option in plugin set up to customize the title ID regex/patterns

I want this too! I will be looking at it today.

Closed with #21.


Not able to search/click on any item after moving to other tab.

From<EMAIL_ADDRESS>on April 15, 2011 11:07:33
What steps will reproduce the problem? 1.Launch the favorites tab.
2.Click on the "Contact4" and check the contact details and go back.
3.Now launch the Contacts tab.
4)Now click On "Contact4" What is the expected output? What do you see instead? Should be able to click on contact.
Actual:
Not able to do any operations on the activity except the hardware key simulations.
1)Click, search operations are not happening.
2)only Hardware keys simulations are happening. What version of the product are you using? On what operating system? Android2.3 and Robotium 2.2 Please provide any additional information below.
Attachment: Issue.rar
Original issue: http://code.google.com/p/robotium/issues/detail?id=101

From<EMAIL_ADDRESS>on April 17, 2011 22:17:59
Thanks for this. Do you get any error when using the click methods? If you do for(TextView textView : solo.getCurrentTextViews()) Log.d("Robotium", "text: " +  textView.getText()); Do you see any of the text views that are displayed in that tab?

From<EMAIL_ADDRESS>on April 18, 2011 04:02:10
I do not get any error but robotium cannot proceed forward. I queried like this and i got the listView refrence to scroll
for(ListView lView : solo.getCurrentlistViews)
It has given me the correct lisview and quried the count by using lView.getCount() - This also has given me the correct count.
Only the hardware key functionalities is working and the robotium searchText and clickOntext is not working.I am able to scroll but using this.sendkeys(KeyEvent.KEYCODE_DPAD_DOWN) but if the textview is available also the not able to give proper result.

From<EMAIL_ADDRESS>on April 18, 2011 05:25:10
Would it be possible for you to send me this application?

From<EMAIL_ADDRESS>on April 18, 2011 06:22:41
No i cant send as it is against policy you can verify this on the base google contacts application.

From<EMAIL_ADDRESS>on April 20, 2011 03:27:27
So the problem is that it does not scroll? searchText() will still find something if it shown in the first screen?

From<EMAIL_ADDRESS>on April 20, 2011 08:47:02
yes if the item is visible it returns true and does not but clickOntext does not able to click on that text item if it is visible and also can't scroll.

From<EMAIL_ADDRESS>on April 21, 2011 00:36:57
The problem is that I am not able to write test cases for the pre-installed Contacts application. It is one of those pre-installed that can not be resigned and then replaced. So I am not able to reproduce this issue, consequently I can not figure out what the problem might be...

From<EMAIL_ADDRESS>on April 21, 2011 10:45:40
Status: WontFix


feat: highlight nav item in onPageNav ToC

Motivation
Highlight nav item in onPageNav ToC when scrolling  #1024
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Local Testing.
Before Changes - https://www.loom.com/share/956ba8b3696a41ba841d38fa5197ab20
After Changes - https://www.loom.com/share/68b57bf4af47400ab9abbdd1b8cbd3f6
Related PRs
#1024

Sorry but I’m not in favor of this PR.
First, it can be easily added by the user as a script. Katex did it (i can argue that the code is similar too) https://github.com/KaTeX/KaTeX/blob/master/website/static/js/scrollspy.js
Second, we are working on v2 and this means we have to port it back to v2. With such limited manpower (nobody is working on docusaurus full-time), its just going to delay v2 even more.
Third, new feature can come with a new bug. And eventually if bug arise, the maintainer will be the one having to fix it.
I think we need to make a clear stance that we are less likely to accept new feature as we are working on v2. Unless there is a high demand on it.
I really appreciate you taking your time to send this PR. I wish the effort was sent towards v2 instead

I like this addition! Feels very natural to have the highlighting follow scrolling.
I agree with @yangshun in favor of the browser's default behavior. I'd say smooth scroll on header clicks is at most an opt-in.
Checked a few non-Docusaurus doc sites on this issue:

Doc site
Highlight follows scroll
Smooth scroll to header clicks

ReactJS
No
No

VueJS
Yes
Yes

Docz
Yes
No

Google Web
Yes
No

Thank you all for the great feedback. @endiliey If this PR gets merged then I can certainly work on sending a PR that replicates this behavior in v2 also.

I'm going to let yall decide. My humble request and only complain is that we have to port this to v2 first before merging it. Not a good idea to see it in v1 but not in v2.
This was unexpected as well because there seems to be no discussion regarding this and suddenly the PR came out

Thank you all for the great feedback. @endiliey If this PR gets merged then I can certainly work on sending a PR that replicates this behavior in v2 also.

Oh cool, that'll be awesome then. Then my only complain is pretty much gone

@yangshun I've removed smooth scroll from this PR. Let me know if a separate PR for that would make sense : )

Working on it. Will submit a PR soon 🙋♂


ARM下shadow-tls启动失败

日志
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
thread '' panicked at 'unable to build monoio runtime: Os { code: 12, kind: OutOfMemory, message: "Out of memory" }', src/main.rs:46:18
thread '' panicked at 'unable to build monoio runtime: Os { code: 12, kind: OutOfMemory, message: "Out of memory" }', src/main.rs:46:18
2022-08-29T12:55:36.810718Z  INFO shadow_tls: Started with parallelism 4
thread 'thread '' panicked at '' panicked at 'unable to build monoio runtime: Os { code: 12, kind: OutOfMemory, message: "Out of memory" }unable to build monoio runtime: Os { code: 12, kind: OutOfMemory, message: "Out of memory" }', ', src/main.rssrc/main.rs::4646::1818

mac or linux?

mac or linux?

#31~20.04.1-Ubuntu SMP Wed Jan 26 14:20:52 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux

Try to adjust io-uring related settings according to monoio doc.

Recently I updated the monoio runtime, you can try to set env MONOIO_FORCE_LEGACY_DRIVER=1 to use legacy driver if you cannot make the io_uring work.

不活跃 issue 我这边先关掉了，如果未接决可以 reopen


Dns

This PR adds the DNS server docker file. This server is configured to point femr.net at the hostname of the laptop. To use, users should follow[ these instructions] (https://docs.google.com/document/d/1opcGO7SUYSOtQPjx1CUQ2PdLrzKxleHNVE4bLMBpUkE/edit?usp=sharing) to configure the router to use the DNS server that has also been changed.

lgtm!


Finishing evalSpanTimer always before return

Finishing evalSpanTimer before returning on errors cases.
Before this change, this span were not Finished on errors cases.

LGTM. Can you be consistent with the blank lines?

Done! thanks!

thank you :)

Thanks!! :D


Add option to disable header auto inclusion

Hi,
as the title of the issue suggest, I would like to disable the auto-header-inclusion feature.
Basically, this is because I have a complex setup and auto-include almost always fails, or adds useless headers (already included by other headers). Maybe there is room to improve the auto-inclusion, but I really do not use this feature, also in other languages.
Maybe, there could be three values for the option:

disable: turn off
enable: turn on as is currently working
popup: turn on but before adding the header, ask to the user

Regards

Flag --header-insertion=never disable auto-insert, but keep suggestion to include missing headers

Hi,
thank you for the reply.
I am actually aiming for an option in the configuration file.
For what I see there is no section in the config file for passing "extra command line options". Correct?
To me it seems that in general whatever we can specify via command line should also be possible to configure
via config file.
Regards

For what I see there is no section in the config file for passing "extra command line options". Correct?

Correct, there is not.

To me it seems that in general whatever we can specify via command line should also be possible to configure via config file.

I think that's worth filing a separate issue (or even better, Discussion) about.

Hi,
ok, I have open a discussion:
https://github.com/clangd/clangd/discussions/1782
Regards


⚠ GitLab Server has degraded performance

In 7f156d8, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 7103 ms

Resolved: GitLab Server performance has improved in 14bff2f.


add a low-level library for manipulating memory mappings, protection and locking

 Issue by thestinger
Saturday Sep 06, 2014 at 18:13 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/17047
This issue was labelled with: A-libs, I-enhancement in the Rust repository

Rust should expose a portable implementation of the mmap, mprotect and mlock functionality (VirtualAlloc, VirtualProtect, VirtualLock on Windows). The current support for memory mapped files is very lacking. The low-level support should be exposed via unsafe functions, and then a new high-level wrapper can be written on top of it.

First platform specific versions of these things should be written in the relative platform specific sys modules. Once they're both written, then we can improve the cross platform API.

Any update on this?

The current status is to just use https://github.com/danburkert/memmap-rs

FWIW, we found memmap-rs to be near-impossible to use safely for our usage, and thus we wrote https://github.com/standard-ai/shmem -- though it's not published on crates.io yet because we noticed the name was taken at the time of open-sourcing it and haven't taken the time to (most importantly) find a new name, change its name and publish it yet. If you're interested in it, feel free to leave a message on its issue tracker.
Maybe the API we chose might be to consider for such a concern, in addition to the API memmap-rs chose?


Refactor walreceiver

Share decoded record handling code between walreceiver and restore_local_repo.

The changes from &PageCache to &Arc<PageCache> seem unnecessary. Other than that, looks good to me.

Before that we had &Arc<PageCache> in walreceiver and &PageCache in restore_local_repo.
Is there a way to cast these types to each other that would be better?


Handle situation where cloud-init script fails

Currently job gets stuck in the ready state.
Example error:
[   83.175465] cloud-init[1302]: E: Failed to fetch http://ceph.clouds.archive.ubuntu.com/ubuntu/pool/universe/p/pigz/pigz_2.3.1-2_amd64.deb  Connection failed [IP: <IP_ADDRESS> 80]
[   83.177429] cloud-init[1302]: E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
[   83.179689] cloud-init[1302]: Failed to start docker.service: Unit docker.service not found.

In this case the startd never starts.

Actually, do eventually get deleted, but the user doesn't see a very useful error message:
    "status": "deleted",
    "statusReason": "",

Also it takes 30 minutes to be deleted. The rule used is:
(JobStatus == 1 && isUndefined(RouteName) && ProminenceInfrastructureState =?= "configured" && CurrentTime - ProminenceInfrastructureEnteredCurrentStatus > 1800)

Probably should reduce the 1800 to 600 and add a SYSTEM_PERIODIC_REMOVE_REASON.


Prepare vehicle hp, run ae-likes, and enable usage of certain REs in vehicles/hazards

Hardness uses data-property in case ae-likes touch it, but otherwise doesn't receive modifiers until we find something in the game that tweaks it. This doesn't make clumsy/enfeebled work for hazard strikes, since hazard strikes don't add {ability}-based selectors.
After this we can probably make rework speed, but anything more will require the ability to retrieve an abilities/effect's source actor (making collision dc match class dc, for example).

Conflicts!


vavr-jackson restoration

Vavr is not just the core. Vavr has a whole ecosystem and one of the components have not been receiving much love lately: https://github.com/vavr-io/vavr-jackson
If you want to contribute, but have no clue where to start, I'd focus on it first since it's been rotting for a while. Core vavr has received some love recently, and it's time for other crucial components to get some as well!

@pivovarit, not able to find any recent issues on the repo, you may add some labels on the problems and update, them so I can contribute there.

I closed a couple of them already - those that are still there can be picked up, for example: https://github.com/vavr-io/vavr-jackson/issues/149

Thank you @pivovarit, I'm grateful that you are revitalizing Vavr again. Can I help with the version/1.x branch of vavr-jackson? I am specifically interested in commit 27c4007, but I don't know what needs to be done to get it out there.

The version/1.x branch represents the next major release and is now in 'pre-alpha' state - so if you want to get something out in finite time, version/0.x is the way to go. I hope to release that as soon as possible.
So if this particular commit is relevant for 0.x, you need to pretty much recreate it and issue a new PR against version/0.x. Remember to reference the original commit


LoRa concentrator failed to start

Hi,
Since the production stopped, I printed my own PCB without no changes in the given schematics. When I test it, I still get "main: LoRa concentrator failed to start".
Am I missing something!?

Hi @kungfupizza  I am also trying to assemble my own board for rpi zero.
Can you help me regarding few component selection.
Im not finding OCX1 and OCX2 part numbers.
It will be great if you can tell me which parts number your using  or links to purchase for these two oscillators.
I can also help you in testing and resolving the issue.
You can find my entire list of BoM at :
https://octopart.com/bom-tool/LadeLROL
suggest any change if you think it can be made better.

You can enable the debug output from lora_gateway/libloragw/library.cfg
And see which component failed.


file: libpython3.a(start.cpp.o) has no symbols

mac OS Sierra 10.12.6
./eosio_build.sh
.......
Requirement already up-to-date: pip in ./dist/lib/python3.6/site-packages
Collecting cython
Downloading https://pypi.tuna.tsinghua.edu.cn/packages/dd/1f/fbc379eeb53eedbff12d0623a154902c06ac6a386830cdc30d4ccb874453/Cython-0.28.1-cp36-cp36m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl (5.2MB)
100% |████████████████████████████████| 5.2MB 187kB/s
Installing collected packages: cython
Successfully installed cython-0.28.1
Scanning dependencies of target python3
[  4%] Building CXX object libraries/python/CMakeFiles/python3.dir/start.cpp.o
[  4%] Linking CXX static library libpython3.a
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: libpython3.a(start.cpp.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: libpython3.a(start.cpp.o) has no symbols
warning: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: warning for library: libpython3.a the table of contents is empty (no object file members in the library define global symbols)
[  4%] Built target python3
make: *** [all] Error 2
>>>>>>>>>>>>>>>>>>>> MAKE building EOSIO has exited with the above error.

"(start.cpp.o) has no symbols" was not the cause of errors, please use the following command to compile your source and upload compile.log to github.
./eosio_build.sh >compile.log 2>&1

complie.log

I try to install 'libffi' by brew:
➜  pyeos git:(master) ✗ brew install libffi
Updating Homebrew...
Warning: libffi 3.2.1 is already installed and up-to-date
To reinstall 3.2.1, run brew reinstall libffi

Please try:
brew link libffi
libffi will be removed from building as it's no need by pyeos

➜  pyeos git:(master) ✗ brew link libffi
Warning: libffi is keg-only and must be linked with --force
Note that doing so can interfere with building software.

Yes, try：
brew link —force libff

On Apr 13, 2018, at 9:12 PM, sindbad<EMAIL_ADDRESS>wrote:
➜ pyeos git:(master) ✗ brew link libffi
Warning: libffi is keg-only and must be linked with --force
Note that doing so can interfere with building software.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/learnforpractice/pyeos/issues/45#issuecomment-381130899, or mute the thread https://github.com/notifications/unsubscribe-auth/Ad6ZPpdu__4TwC90OEdF-1IMn8vMBoW9ks5toKRIgaJpZM4TTB9z.

pyeos git:(master) ✗ brew link --force libff
Error: No such keg: /usr/local/Cellar/libff

OK, I have submitted a patch to remove libffi from building, please update your source with the following command:
git pull
git submodule update --init --recursive
Good luck!

On Apr 13, 2018, at 9:16 PM, sindbad<EMAIL_ADDRESS>wrote:
pyeos git:(master) ✗ brew link --force libff
Error: No such keg: /usr/local/Cellar/libff
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/learnforpractice/pyeos/issues/45#issuecomment-381131863, or mute the thread https://github.com/notifications/unsubscribe-auth/Ad6ZPvQdJ8KgixqMR5ZDr8z-5L2JhdQBks5toKUrgaJpZM4TTB9z.


BUG: ENH: update spa_files to patch timezone bug

closes #168
get source and header in setup.py
replace "timezone" with "timezone" to fix the bug
also update readme
also remove a lot of extra whitespace and tabs

Signed-off-by: Mark Mikofski<EMAIL_ADDRESS>

okay, the user is forced to see the license and push a key to install now, here's what they see:
>python setup.py build_ext --inplace
# NOTICE

Copyright (c) 2008-2011 Alliance for Sustainable Energy, LLC, All Rights Reserved

The Solar Position Algorithm ("Software") is code in development prepared by
employees of the Alliance for Sustainable Energy, LLC, (hereinafter the
"Contractor"), under Contract No. DE-AC36-08GO28308 ("Contract") with the
U.S. Department of Energy (the "DOE"). The United States Government has been
granted for itself and others acting on its behalf a paid-up, non-exclusive,
irrevocable, worldwide license in the Software to reproduce, prepare
derivative works, and perform publicly and display publicly. Beginning five
(5) years after the date permission to assert copyright is obtained from the
DOE, and subject to any subsequent five (5) year renewals, the United States
Government is granted for itself and others acting on its behalf a paid-up,
non-exclusive, irrevocable, worldwide license in the Software to reproduce,
prepare derivative works, distribute copies to the public, perform publicly
and display publicly, and to permit others to do so. If the Contractor ceases
to make this computer software available, it may be obtained from DOE's
Office of Scientific and Technical Information's Energy Science and
Technology Software Center (ESTSC) at P.O. Box 1020, Oak Ridge, TN
37831-1020.  IN NO EVENT SHALL THE CONTRACTOR OR THE U.S. GOVERNMENT BE LIABLE
FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER,
INCLUDING BUT NOT LIMITED TO CLAIMS ASSOCIATED WITH THE LOSS OF DATA OR
PROFITS, WHICH MAY RESULT FROM AN ACTION IN CONTRACT, NEGLIGENCE OR OTHER
TORTIOUS CLAIM THAT ARISES OUT OF OR IN CONNECTION WITH THE ACCESS, USE OR
PERFORMANCE OF THIS SOFTWARE.

The Software is being provided for internal, noncommercial purposes only and
shall not be re-distributed. Please contact [Jean
<EMAIL_ADDRESS>in the NREL Commercialization and
Technology Transfer Office for information concerning a commercial license to
use the Software.

As a condition of using the Software in an application, the developer of the
application agrees to reference the use of the Software and make this Notice
readily accessible to any end-user in a Help|About screen or equivalent manner.

By continuing you accept the NREL LICENSE. Press any key ...

Then they have to press a key to continue.
running build_ext
building 'spa_py' extension
<some compiler stuff>
spa_py.c
<more compiler stuff>
spa.c
spa.c(535): warning C4244: 'return': conversion from 'double' to 'int', possible loss of data
spa.c(1072): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
<even more compiler stuff>
   Creating library build\temp.win-amd64-3.7\Release\spa_py.cp37-win_amd64.lib and object build\temp.win-amd64-3.7\Release\spa_py.cp37-win_amd64.exp
Generating code
Finished generating code

ok?

I'm not comfortable with the auto-download, I would be more comfortable with if we sought and received NREL's agreement that the auto-download satisfies their request for registration.  I don't think we should merge until we have their approval. I suspect they will not be pleased with the pvlib-python user name and will want individuals and organizations.
I'd be happy to contact NREL about this.
I appreciate and agree with the motivation to make the build convenient for users, especially with the timezone vs. time_zone behavior.

@cwhanse sounds good , FYI: I changed it so the user has to enter there name now

Thanks @mikofski. Can we do something similar for all of the fields?
print('Enter the following to accept the NREL LICENSE:')
VALUES['name'] = input('Name: ')
VALUES['country'] = input('Country: ')
VALUES['company'] = input('Company: ')
VALUES['software'] = input('Software (enter pvlib-python if not bundling with another application): ')

@wholmgren I responded to some of your comments that are hidden as outdata above I guess you saw them?

@mikofski confused about your comment above about the CI building it -- I don't think it is.

E   TypeError: spa_calc() takes at least 13 positional arguments (6 given)

spa_py.pyx:3: TypeError

confused about your comment above about the CI building it -- I don't think it is.

no I didn't mean it's building the spa-c files, I meant it is building pvlib-python without the spa-c files, which I think is what we would expect, right? and it is consistently building pvlib-python everytime AFAICT

In any case, it didn't work for me:

weird, same for me on linux, but seems to work on windows? is this a red herring? grrrrr

@cwhanse @mikofski I support asking NREL if the latest interface meets their requirements. Here's what it looked like after I pulled @mikofski's latest changes that require the user to enter all information:
$ python setup.py build_ext --inplace
# NOTICE

Copyright (c) 2008-2011 Alliance for Sustainable Energy, LLC, All Rights Reserved

The Solar Position Algorithm ("Software") is code in development prepared by
employees of the Alliance for Sustainable Energy, LLC, (hereinafter the
"Contractor"), under Contract No. DE-AC36-08GO28308 ("Contract") with the
U.S. Department of Energy (the "DOE"). The United States Government has been
granted for itself and others acting on its behalf a paid-up, non-exclusive,
irrevocable, worldwide license in the Software to reproduce, prepare
derivative works, and perform publicly and display publicly. Beginning five
(5) years after the date permission to assert copyright is obtained from the
DOE, and subject to any subsequent five (5) year renewals, the United States
Government is granted for itself and others acting on its behalf a paid-up,
non-exclusive, irrevocable, worldwide license in the Software to reproduce,
prepare derivative works, distribute copies to the public, perform publicly
and display publicly, and to permit others to do so. If the Contractor ceases
to make this computer software available, it may be obtained from DOE's
Office of Scientific and Technical Information's Energy Science and
Technology Software Center (ESTSC) at P.O. Box 1020, Oak Ridge, TN
37831-1020.  IN NO EVENT SHALL THE CONTRACTOR OR THE U.S. GOVERNMENT BE LIABLE
FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER,
INCLUDING BUT NOT LIMITED TO CLAIMS ASSOCIATED WITH THE LOSS OF DATA OR
PROFITS, WHICH MAY RESULT FROM AN ACTION IN CONTRACT, NEGLIGENCE OR OTHER
TORTIOUS CLAIM THAT ARISES OUT OF OR IN CONNECTION WITH THE ACCESS, USE OR
PERFORMANCE OF THIS SOFTWARE.

The Software is being provided for internal, noncommercial purposes only and
shall not be re-distributed. Please contact [Jean
<EMAIL_ADDRESS>in the NREL Commercialization and
Technology Transfer Office for information concerning a commercial license to
use the Software.

As a condition of using the Software in an application, the developer of the
application agrees to reference the use of the Software and make this Notice
readily accessible to any end-user in a Help|About screen or equivalent manner.

Enter the following information to accept the NREL LICENSE ...

Name: Will Holmgren
Company (or enter "Individual"): University of Arizona
Country: USA
Email (optional<EMAIL_ADDRESS>running build_ext
building 'spa_py' extension
gcc -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/Users/holmgren/miniconda3/envs/pvlibfx36/include -arch x86_64 -I/Users/holmgren/miniconda3/envs/pvlibfx36/include -arch x86_64 -I/Users/holmgren/git_repos/pvlib-python/pvlib/spa_c_files -I/Users/holmgren/miniconda3/envs/pvlibfx36/include/python3.6m -c spa_py.c -o build/temp.macosx-10.9-x86_64-3.6/spa_py.o
gcc -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/Users/holmgren/miniconda3/envs/pvlibfx36/include -arch x86_64 -I/Users/holmgren/miniconda3/envs/pvlibfx36/include -arch x86_64 -I/Users/holmgren/git_repos/pvlib-python/pvlib/spa_c_files -I/Users/holmgren/miniconda3/envs/pvlibfx36/include/python3.6m -c spa.c -o build/temp.macosx-10.9-x86_64-3.6/spa.o
gcc -bundle -undefined dynamic_lookup -Wl,-rpath,/Users/holmgren/miniconda3/envs/pvlibfx36/lib -L/Users/holmgren/miniconda3/envs/pvlibfx36/lib -headerpad_max_install_names -Wl,-rpath,/Users/holmgren/miniconda3/envs/pvlibfx36/lib -L/Users/holmgren/miniconda3/envs/pvlibfx36/lib -headerpad_max_install_names -arch x86_64 build/temp.macosx-10.9-x86_64-3.6/spa_py.o build/temp.macosx-10.9-x86_64-3.6/spa.o -L/Users/holmgren/miniconda3/envs/pvlibfx36/lib -o /Users/holmgren/git_repos/pvlib-python/pvlib/spa_c_files/spa_py.cpython-36m-darwin.so

no I didn't mean it's building the spa-c files, I meant it is building pvlib-python without the spa-c files, which I think is what we would expect, right? and it is consistently building pvlib-python everytime AFAICT

Great. Let's not add this to the CI.
No clue about the platform/test issues. Sorry.

No clue about the platform/test issues. Sorry.

It's "time_zone" now, not "timezone"!
pdb to the rescue!

OK, works now in linux too, thanks for catching that! I reverted the Python API in pvlib.solarposition.spa_c to continue to use timezone without the underscore, so it's only the cython version in pvlib.spa_c_files.spa_py.spa_calc that confusingly takes a timezone but outputs a time_zone, sorry!

See this explanation from the cython users google group - evidently , only a windows issue, and only since Python-3.5, pyconfig.h redefines timezone as a function.

I should probably leave, so I slightly revert the changes, and added spa_py.c back in after accidently deleting it, you might have you check your tests again, but make sure to purge your build folders, I had to on linux, it passes for me. I just thought it was better to have a consistent in/out api for spa_calc, even tho timezone isn't used that much.

This seems sub-optimal but not a must fix:
$ python setup.py build_ext --inplace
$ git diff
diff --git a/pvlib/spa_c_files/spa_py.c b/pvlib/spa_c_files/spa_py.c
index 378c34c..b711b0d 100644
--- a/pvlib/spa_c_files/spa_py.c
+++ b/pvlib/spa_c_files/spa_py.c
@@ -4,10 +4,10 @@
 {
     "distutils": {
         "depends": [
-            "spa.h"
+            "/Users/holmgren/git_repos/pvlib-python/pvlib/spa_c_files/spa.h"
         ],
         "include_dirs": [
-            "."
+            "/Users/holmgren/git_repos/pvlib-python/pvlib/spa_c_files"
         ],
         "name": "spa_py",
         "sources": [

I'm not a fan either, if rather drop the generated Cython, I can't think of a case where any user would use it

I think that's only showing up on your machine after you build on place and replace that spa_py.c file locally. It doesn't look that way on GitHub https://github.com/mikofski/pvlib-python/blob/fix_spa_c_files_timezone_compile_fail/pvlib/spa_c_files/spa_py.c

My objection is when I build the package it modifies a file that git tracks, so now I have a file that shows up under "not staged for commit" in my local repo. If I used this regularly it would be a problem for me because I use git commit -a all the time. But I don't, so I won't be a stickler about it. Maybe there is some difference between your platform and mine or maybe I'm not doing something right. In any case, if we're going to require cython to use spa_c then we could git rm spa_py.c as you suggested earlier and also add it to .gitignore and problem solved.

Sorry, I misunderstood, yes the same annoying thing happens to me too. I vote to git remove it and then git ignore as you suggest.

What do you think of the LGTM alerts? No big deal for this?

What do you think of the LGTM alerts? No big deal for this?

I thought about this, it's only a concern for Python-2, b/c in Python-3, input is always coerced to string, but in Python-2, it calls evil eval. But I think in this case it's okay, because:

the user probably should not try to build the spa-c files in Python-2. I don't know if the byte-strings will work without some compatibility fixes, and I don't have the patience for something that affects 1% of users
the user is using input on themselves, so if they happen to be using Python-2.7, and it magically works, and they happen to type rm -rf / as their name, then it's kind of their own fault

@mikofski @wholmgren am trading emails with NREL will let you know if/when they approve.

OK, I agree, I'll factor out the download code.
And by the way, it works fine in Python-2

I agree with the factoring at this point.

BTW: refactoring out the autodownload removes the input threat, which turns out it was real, b/c the setup.py byte-string patching does work on py2
Anyway, OK now?

Here's the old code for posterity:
from urllib import request, parse

SPA_C_URL = r'https://midcdmz.nrel.gov/apps/download.pl'
SPA_H_URL = r'https://midcdmz.nrel.gov/spa/spa.h'
VALUES = {'software': 'SPA'}
LICENSE = 'SPA_NOTICE.md'

with open(os.path.join(DIRNAME, LICENSE)) as f:
    print(f.read())

print('\nEnter the following information to accept the NREL LICENSE ...\n')
VALUES['name'] = input('Name: ')
VALUES['company'] = input('Company (or enter "Individual"): ')
VALUES['country'] = input('Country: ')
VALUES['email'] = input('Email (optional): ')
DATA = parse.urlencode(VALUES).encode('ascii')

# get spa.c
REQ = request.Request(SPA_C_URL, DATA)
with request.urlopen(REQ) as response:
    SPA_C = response.read()
# patch here ...

# get spa.h
with request.urlopen(SPA_H_URL) as response:
    SPA_H = response.read()
# patch here ...

Ready to go, I think a few inline comments would be wise to remind us why we change timezone

Thanks @mikofski and @cwhanse. I think the additional comments will helpful.

@wholmgren AFAIK I think this is ready whenever, just waiting for approval from @cwhanse

Closes #168


XRI3 migration step17 removing xr controller

Removed XRComponent from prefabs, for example:

Updated controllerless prefabs so that their Interactors now hold a reference to their parent XRControllerless controller GameObject in the ModeManagedRoot field.  For example:

Added IModeManagedInteractor implementation to GazeInteractor class.
Updated BasicInputTestsForControllerlessRig::ControllerlessRigSmokeTest to test against removed XRController component in prefabs.
Added missing logic in TapToPlace to properly register to stopping placement actions events.
Updated org.mixedrealitytoolkit.input/CHANGELOG.md

/azp run

@whebertML This PR replaces the old PR.  This was created because it was easier to just create a new one to incorporate the latest changes in the branch and re-start the XRComponent removal.  Your previous feedback has been attended in this new PR, thank you for your feedback btw.  If you have time, could you please take a look at this PR too?


[ForumsTeam] PowerShell Cmdlets missing for the Examples Section

PowerShell Cmdlets missing for the Examples Section

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azuresmps-4.0.0/Azure/Get-AzureDeploymentEvent.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

#sign-off Looks good to me


fixed cancel label

Fixes #2039
Changes
Changed label value in en-US for cancel key from "Delete" to "Cancel"
Summary of changes you made.

en-US.json

"cancel": "Delete"

Test plan
Explain how to test changes you made.

Login to busy.org
Go to wallet.
Click on Power Up\Power Down
Check the label of the white button.

Demo (optional)
Sreenshots (before & after) or video that show result of your work.
Before

After

We use crowdin for translations and we updated it there:
https://crowdin.com/project/busy/en


Add interceptor support to opentracing_instrumentation

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

btw -- py 2.7.14 is out :)


Allow specifying the tag after AAD in CCM mode

This change allows to pass the authentication tag after specifying the AAD in CCM mode. This is already true for the other two supported AEAD modes (GCM and OCB) and it seems appropriate to match the behavior.
GCM and OCB also support to set the tag at any point before the call to EVP_*Final, but this won't work for CCM due to a restriction imposed by section 2.6 of RFC3610: The tag must be set before actually decrypting data.
This commit also adds a test case for setting the tag after supplying plaintext length and AAD.

Checklist

[x] tests are added or updated

ping

Hello everyone,
in GCM and OCB mode, it is possible to set the authentication tag after
supplying AAD, but the CCM implementation does not allow that. This
isn't a problem for most applications, but in Node.js, we expose similar
APIs to interact with AEAD ciphers and these differences between cipher
modes within OpenSSL propagate to our users. Unless there is a reason
for the current behavior, I would prefer to change it.
I opened a PR about this five months ago
(https://github.com/openssl/openssl/pull/7243). It has received zero
attention and I am hoping the mailing list is a good way to change that.
Kind regards,
Tobias

(see https://mta.openssl.org/pipermail/openssl-users/2019-February/009881.html)

@mattcaswell Thank you for reviewing! I fixed the indentation issue, but I'll have to take a look at the documentation.
@blaufish Thank you for reviewing as well!

GCM and OCB also support to set the tag at any point before the call
to `EVP_*Final`, but this won't work for CCM due to a restriction
imposed by section 2.6 of RFC3610: The tag must be set before
actually decrypting data.

Does RFC3610 2.6 say anything specific on this subject?
Are you referring to this advice?
The recipient MUST verify the CBC-MAC before releasing any
information such as the plaintext.  If the CBC-MAC verification
fails, the receiver MUST destroy all information, except for the fact
that the CBC-MAC verification failed.

Yes, I am. I agree that the commit message might be a bit inaccurate there, I meant "releasying any information such as the plaintext" when I wrote "decrypting data".

It seems like good advice for any AEAD mode, and doesn't explicitly talk about in which order tag,aad,ciphertext is provided to aead-decrypt operations?
As per 2.2, before decryption can start:
* length(nonce)

* length(AAD)

* length(message)

These are needed due to CBC.MAC operations needs first block B_0 calculations.
As far as I know, there's nothing in the RFC about when tag needs to be provided, except that tag length must be known prior to decrypt finalising (releasing plaintext to caller).

That is correct, but the tag is required before providing the plaintext to the user, meaning it needs to be provided before decrypting data using EVP_CipherUpdate.

I think the EVP_EncryptInit man page could do with some update as part of this PR to clarify when exactly the tag can be set.

@mattcaswell I added a few lines to the documentation, I assume that's what this has been waiting for. Please take another look.

Ping @openssl for second review.

Pushed. Thanks.


included form validation using express-validator

Is it fully working?

yes from my side no issues. working as accepted


Issue539 fit2d

Motivations:

Update the fit2d routines, including plots to be operational for automated data treatment for XICS on WEST

Main changes:

tofu.spectro now contains:

_fit12d_dinput.py: contains routines fit1d_dinput() and fit2d_dinput() for data-pretreatment (before fitting), they will check all inputs (data, noise, constraints...) and format them into a unique dinput dict to be fed to the fitting routines.
These 2 routines must be called directly be the user.
_fit12d_funccostjac.py: contains routines for computing and return the functions that evaluate the cost function and the jacobian for the least-square fit problem. Called by inside machinery, not directly by the user.
_fit12d.py: contains routines fit1d() and fit2d(), called directly by the user, fed dinput.
These routines handle the fitting process itself, taking into account all constraints and data, for all time steps.
They return a dfit output dict.
_fit12d_dextract.py: contains routines fit1d_dextract() and fit2_dextract(), called directly by the user with dfit as an input.
These routines extract all relevant data from the fits and return them in a single output dict dextract.
_plot.py: contains routines:

plot_dinput1d(dinput=...) and plot_dinput2d(dinput=...) to  plot the input content
plot_fit1d(dfit1d=..., dextract=...) and plot_fit2d(dfit2d=..., dextract=...) to  plot the result of the fit and extracted data.
They produce one figure per time step (no interactivity yet) and the desired time step can be specified using indspect=...

There is a very large number of parameters that the user can set for each of these 3 steps, to optimize the input contraints, the fit convergence or the type of output required. But both for 1d and 2d fits, the general process is of the form (n=1 or 2):
import tofu as tf

# step 1: check and format input
dinput = tf.spectro.fitnd_dinput(data=..., ...)

# step 2: run the fit
dfit = tf.spectro.fitnd(dinput=dinput, ...)

# step 3: extract output
dextract = tf.spectro.fitnd_dextract(dfit=dfit, ...)

All these routines, for 1d and 2d fitting, are unit-tested and benchmarked.
Regarding the input pre-treatment:

The data has to be provided as a (nlamb, nphi) 2d array for 2d fits.
Any coordinate tranform (xi, xj) => (lamb, phi) has to be done before calling fit2d_dinput()
A minimum S/N ratio can be enforced (make sure data is provided in counts, not counts/s or counts/m2).
Binning can be done for 2d fits
a mask can be used
A series of sub-domains can be defined to restrict the fit to a chosen region
A dict of known spectral lines (rest wavelengths) must be provided (the shift from the rest wavelength is what will be fitted)

Regarding the fit hypothesis:

The background is an exponential with 2 free parameters (amplitude, rate)
All lines are gaussians, with 3 free parameters (amplitude, width, shift from rest wavelength)
All lines can be doubled with 2 free parameters (dratio, dshift), these 2 parameters are common to all lines
The 2d fit can be assumed to up-down symmetric
All lines parameters can be expressed as groups of linear functions of each-others, for example, for a total of N lines

n lines can share the same amplitude (or width, or shift), and N-n lines can each have their own amplitude (or width, or shift).
n lines can share the same width and shift, 2 lines can share the same amplitude with a linear relationship, N-n-2 lines can share the same width only
... al combinations are possible

For 2d fits, all free parameters (except line-doubling parameters) are decomposed vertically on a set of nbs bsplines, to ensure continuity of the solution. The fit is done simultaneously for the whole image.

Tips:

When in doubt, it is always worth check the dinput dict content,

Issues:

Fixes, in devel, issue #539

Example:
It would be too long to detail all steps, so in the following we make use of a pre-implemnted unit test that:

load realistic WEST data
load all relevant constraints (spectral lines dict, sub-domain definitions, data reshaping, binning, focus...)
calls fit2d_dinput() * calls fit2d()
calls fit2d_dextract()

And finally the 3 dictionarries dinput, dfit2d, dextract, which allows us to plot the input and the resuls using plot_dinput() and plot_fit2d()
In [1]: import tofu as tf

In [2]: test = tf.tests.tests04_spectro.test_01_fit12d.Test02_RealisticWESTCase()

In [3]: dinput, dfit2d, dextract, t = test.test00_load_dinput_dfit_dextract()
Loaded from:
    /home/didier/Documents/Projects/tofu/tofu/tests/tests04_spectro/test_data/TFG_CrystalBragg_ExpWEST_DgXICS_ArXVII_sh00000_Vers1.5.0.npz
/home/didier/Documents/Projects/tofu/tofu/spectro/_fit12d_dinput.py:868: UserWarning: binning[lamb] seems finer than the original!
	- estimated original step: 1.7772910669872196e-14
	- binning step: 1.775280898876403e-14
  => nb. of recommended steps: 444.5
  warnings.warn(msg)
/home/didier/Documents/Projects/tofu/tofu/spectro/_fit12d_dinput.py:982: RuntimeWarning: Mean of empty slice
  dataphi1d = np.nanmean(databin, axis=2)
/home/didier/Documents/Projects/tofu/tofu/spectro/_fit12d_dinput.py:983: RuntimeWarning: Mean of empty slice
  datalamb1d = np.nanmean(databin, axis=1) + np.nanstd(databin, axis=1)
/home/didier/anaconda3/lib/python3.7/site-packages/numpy/lib/nanfunctions.py:1665: RuntimeWarning: Degrees of freedom <= 0 for slice.
  keepdims=keepdims)
Spect      time (s)   cost       nfev       njev       msg
---------- ---------- ---------- ---------- ---------- ----------
2 / 2      1.87392    1.786e+06  6          6          `ftol` termination condition is satisfied.
The following variables seem to have saturated:
	amp ArXVII_w_Bruhns: 2 / 2
	width wxyzkj: 2 / 2
Total computation time:	4.09 s for 2 spectra (2.045 s per spectrum)

In [4]: dax = tf.spectro.plot_dinput2d(dinput=dinput)

In [5]: dax = tf.spectro.plot_fit2d(dfit2d=dfit2d, dextract=dextract)

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

In the file tofu/spectro/_fit12d_dextract.py:

Line 432:5: E303 too many blank lines (2)
Line 515:13: E122 continuation line missing indentation or outdented
Line 752:13: E122 continuation line missing indentation or outdented
Line 812:5: E303 too many blank lines (2)

In the file tofu/spectro/_fit12d_dinput.py:

Line 77:1: E303 too many blank lines (3)
Line 87:1: E302 expected 2 blank lines, found 3
Line 411:40: E225 missing whitespace around operator
Line 1018:11: E131 continuation line unaligned for hanging indent
Line 1235:5: E303 too many blank lines (2)
Line 2153:5: E303 too many blank lines (2)
Line 2181:9: E116 unexpected indentation (comment)
Line 2182:9: E116 unexpected indentation (comment)
Line 2183:9: E116 unexpected indentation (comment)
Line 2184:9: E116 unexpected indentation (comment)
Line 2189:9: E116 unexpected indentation (comment)
Line 2190:9: E116 unexpected indentation (comment)
Line 2191:9: E116 unexpected indentation (comment)
Line 2192:13: E116 unexpected indentation (comment)
Line 2193:13: E116 unexpected indentation (comment)
Line 2194:13: E116 unexpected indentation (comment)
Line 2195:13: E116 unexpected indentation (comment)
Line 2196:17: E116 unexpected indentation (comment)
Line 2197:13: E116 unexpected indentation (comment)
Line 2198:9: E116 unexpected indentation (comment)
Line 2199:9: E116 unexpected indentation (comment)
Line 2203:9: E116 unexpected indentation (comment)
Line 2204:9: E116 unexpected indentation (comment)
Line 2205:9: E116 unexpected indentation (comment)
Line 2206:9: E116 unexpected indentation (comment)
Line 2207:9: E116 unexpected indentation (comment)
Line 2213:9: E116 unexpected indentation (comment)
Line 2214:9: E116 unexpected indentation (comment)
Line 2215:9: E116 unexpected indentation (comment)
Line 2217:9: E116 unexpected indentation (comment)
Line 2218:13: E116 unexpected indentation (comment)
Line 2219:13: E116 unexpected indentation (comment)
Line 2220:9: E116 unexpected indentation (comment)
Line 2221:13: E116 unexpected indentation (comment)
Line 2222:13: E116 unexpected indentation (comment)
Line 2231:9: E116 unexpected indentation (comment)
Line 2232:9: E116 unexpected indentation (comment)
Line 2308:23: E702 multiple statements on one line (semicolon)
Line 2616:22: E225 missing whitespace around operator
Line 2972:80: E501 line too long (81 > 79 characters)
Line 2974:80: E501 line too long (81 > 79 characters)

In the file tofu/spectro/_plot.py:

Line 315:1: E302 expected 2 blank lines, found 1
Line 336:9: E117 over-indented (comment)
Line 338:9: E117 over-indented (comment)
Line 340:9: E117 over-indented (comment)
Line 342:9: E117 over-indented (comment)
Line 739:80: E501 line too long (83 > 79 characters)
Line 793:18: E131 continuation line unaligned for hanging indent
Line 1106:17: E116 unexpected indentation (comment)
Line 1107:17: E116 unexpected indentation (comment)

In the file tofu/tests/__init__.py:

Line 14:1: W391 blank line at end of file

In the file tofu/tests/tests00_root/__init__.py:

Line 4:1: E303 too many blank lines (3)

In the file tofu/tests/tests01_geom/test_03_core.py:

Line 679:38: E231 missing whitespace after ':'
Line 821:15: E225 missing whitespace around operator
Line 823:35: E231 missing whitespace after ','
Line 823:47: E231 missing whitespace after ','
Line 824:37: E231 missing whitespace after ','
Line 824:50: E231 missing whitespace after ','
Line 826:37: E231 missing whitespace after ','
Line 826:51: E231 missing whitespace after ','
Line 828:26: E231 missing whitespace after ','
Line 828:29: E231 missing whitespace after ','
Line 829:22: E231 missing whitespace after ','
Line 829:25: E231 missing whitespace after ','
Line 830:29: E231 missing whitespace after ','
Line 834:23: E225 missing whitespace around operator
Line 835:30: E231 missing whitespace after ','
Line 835:53: E231 missing whitespace after ','
Line 836:40: E231 missing whitespace after ','
Line 836:50: E231 missing whitespace after ','
Line 839:48: E231 missing whitespace after ','
Line 840:48: E231 missing whitespace after ','
Line 842:23: E225 missing whitespace around operator
Line 844:40: E231 missing whitespace after ','
Line 844:43: E231 missing whitespace after ','
Line 845:30: E231 missing whitespace after ','
Line 845:53: E231 missing whitespace after ','
Line 846:45: E231 missing whitespace after ','
Line 846:60: E231 missing whitespace after ','
Line 846:70: E231 missing whitespace after ','
Line 846:80: E501 line too long (81 > 79 characters)
Line 847:37: E231 missing whitespace after ','
Line 847:52: E231 missing whitespace after ','
Line 847:60: E231 missing whitespace after ','
Line 850:40: E231 missing whitespace after ','
Line 850:43: E231 missing whitespace after ','
Line 851:55: E231 missing whitespace after ','
Line 852:51: E231 missing whitespace after ','
Line 853:49: E231 missing whitespace after ','
Line 854:32: E228 missing whitespace around modulo operator
Line 858:33: E231 missing whitespace after ':'
Line 858:41: E231 missing whitespace after ':'

In the file tofu/tests/tests02_data/__init__.py:

Line 4:1: E303 too many blank lines (3)

In the file tofu/tests/tests03_openadas/__init__.py:

Line 4:1: E303 too many blank lines (3)

In the file tofu/tests/tests04_spectro/test_01_fit12d.py:

Line 616:70: W291 trailing whitespace
Line 797:80: E501 line too long (80 > 79 characters)

In the file tofu/tests/tests04_spectro/test_data/_spectral_constraints.py:

Line 68:17: E131 continuation line unaligned for hanging indent
Line 135:7: E261 at least two spaces before inline comment
Line 135:8: E262 inline comment should start with '# '
Line 173:9: E265 block comment should start with '# '
Line 200:20: E261 at least two spaces before inline comment
Line 200:21: E262 inline comment should start with '# '
Line 201:9: E131 continuation line unaligned for hanging indent

In the file tofu/tests/tests05_nist/__init__.py:

Line 4:1: E303 too many blank lines (3)

In the file tofu/tests/tests06_mesh/__init__.py:

Line 4:1: E303 too many blank lines (3)

In the file tofu/tests/tests07_inversions/__init__.py:

Line 4:1: E303 too many blank lines (3)

Opening issue #612 to adress the unit tests


feat: ibc validation logic

Description
closes: #312

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] added appropriate labels to the PR
[ ] targeted the correct branch
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Codecov Report
Attention: 28 lines in your changes are missing coverage. Please review.

Comparison is base (326eee2) 15.44% compared to head (faf4bdb) 15.42%.

Files
Patch %
Lines

x/gmp/keeper/keeper.go
0.00%
28 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #318      +/-   ##
==========================================
- Coverage   15.44%   15.42%   -0.02%
==========================================
  Files          78       78
  Lines       18942    18961      +19
==========================================
  Hits         2925     2925
- Misses      15868    15887      +19
  Partials      149      149

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


when optimization.moduleIds =  'named',  an absolute-path module identifier makes error in windows file system.

System Info
System:
OS: Windows 10 10.0.19045
CPU: (12) x64 AMD Ryzen 5 5600X 6-Core Processor
Memory: 16.10 GB / 31.93 GB
Binaries:
Node: 18.15.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 8.6.0 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Spartan (44.19041.1266.0), Chromium (112.0.1722.64)
Internet Explorer: 11.0.19041.1566
npmPackages:
@rspack/cli: latest => 0.1.9
Details
If you set optimization.moduleIds to be 'named', it is expected that bundled modules have identifiers that resemble the original file path.

If the module can be imported from a relative path, it works just fine. But if the module must be imported from an absolute path, (i.e. the module is imported from a different drive), the module identifier breaks in windows file system, because it uses \ instead of \\.

Webpack seems to handle it well, and I included a snapshot to show that.
(I imported a module named simple-demo-package from another drive, and compiled it with RsPack and WebPack, respectively.)

Reproduce link
https://github.com/aliveornot/rspack-module-id-bug
Reproduce Steps

Clone the repo into a drive.

clone the repo, into a windows machine that has at least two different drives. (let's say you cloned into d:/src/rspack-bug)

Make another project in a different drive.

Initialize another npm project somewhere like c:/src/rspack-bug-2
install simple-demo-package by yarn add simple-demo-package

Modify rspack.config.js accordingly.

open rspack.config.js in the cloned project from (1)
modify resolve.modules so that it imports from project initilized in (2)
run yarn build

Now, open ./dist/main.js and you can see the imported module name contains single-backslash. It's especially erroneous when the name of the package starts with u, because it makes the module identifier contain \u****, which is a unicode escape sequence.

should be fixed by #3220

Thanks a lot!

Oh I checked with somewhat more complicate repo which I'm actually working on, and the bug persists in some cases. Please take a look at #3306

@alexander-akait sorry to bother you again, do you know why webpack don't use normalize path when dealing with cross driver path?

if it is out of context，why cant we use path like ”../../../other-folder/lib.js”

You can, but loader should do it on own side when inject import() or plugins, i.e. contextify


[Feature Request] React Helmet Integration

Since things are changing quite a bit for React Router V6, I thought that suggesting a feature that would make React Helmet integration with React Router would be welcomed.
Indeed, in most case the page HTMl Header is defined on a route basis, route n.1 needs a specific title, route n.2 needs another specific title and so on). Since React and all these modern framework are all about making dev life easier, I was wondering whether adding custom properties to routes or passing the entire Helmet node would be possible?

This would be something you would build in another library. That could take in a route config that can read extra properties for react-helmet. We don't need to build anything into the library for that.


Disaster recovery with uni-directional replication

Since implementation of #116, uni-directional (optionally cyclic) replication networks are supported. The current implementation of disaster recovery, however, assumes a bi-directional replication between connected endpoints (see ReplicationEndpoint.recover() API docs). For example, given two event logs, A and B at different endpoints, disaster recovery of A requires

a replication connection from B to A to support metadata re-synchronization at B (recover metadata phase)
a replication connection from A to B to replicate events from B to A (recover events phase).

When having a replication connection only from A to B, the current disaster recovery implementation (introduced with #157) would not make progress, as A would never receive a ReplicationRead message from B. Disaster recovery at A should therefore skip the recover metadata phase if there's only a replication connection from A to B but no replication connection from B to A.

@volkerstampa I don't see this as high priority at the moment as most applications anyway have bi-directional replication links between endpoints.

In addition to the fact that A needs to know that the replication link from B to A is missing, A also needs to know if there are additional unidirectional replication links from C to A, as in that case C's replication metadata needs to be reset. As A is currently not aware of those it might be an option that in case of recovery an administrator has to list all of A's incoming replication links explicitly.

@volkerstampa is this now resolved with #308?

@volkerstampa I will anyway close this ticket for now as disaster recovery will be re-designed in context of #314. If you think this ticket is still valid, feel free to re-open.


Update baseline

Close #375

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
667 unchanged lines in 9 files lost coverage.
Overall coverage decreased (-5.7%) to 29.55%

Files with Coverage Reduction
New Missed Lines
%

src/Kendrick/KETransition.class.st
16
78.38%

src/Kendrick/KECompartmentName.class.st
25
0%

src/Kendrick/KEGillespieSimulator.class.st
39
0%

src/Kendrick/KEDeterministicSimulator.class.st
69
0%

src/Kendrick/KEDependentModelPart.class.st
75
0%

src/Kendrick/KEModelPart.class.st
75
33.11%

src/Kendrick/KESimulator.class.st
80
0%

src/Kendrick/KEModelPartTest.class.st
122
8.96%

src/Kendrick/KEDependentModelPartTest.class.st
166
16.16%

Totals

Change from base Build<PHONE_NUMBER>:
-5.7%

Covered Lines:
4038

Relevant Lines:
13665

💛  - Coveralls