Configuration.defaultDependencies not run when only dependency is a platform

When adding a platform as a dependency to a configuration, defaultDependencies does not run, even if it is the only dependency.
Expected Behavior

Since a platform can only define constraints, not actual dependencies, it should not prevent defaultDependencies from running.
Current Behavior

When the only dependency is a platform, Configuration.defaultDependencies is not run.
Context

In a project using the jacoco plugin, a construct like this attempting to apply a platform to all configurations in a project
configurations.configureEach {
  dependencies.add(configuration.name, platform(project(":platform")))
}

The project fails to run tests with this error message
> Task :project:test FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':project:test'.
> Expected configuration ':project:jacocoAgent' to contain exactly one file, however, it contains no files.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Perhaps applying a platform to all configurations like that is not a good pattern (open to suggestions). However, applying a platform to jacoco configurations to manage their versions along with all other versions in a platform, as opposed to having to set the version in the jacoco extension, seems like a valid use case.
Even if this is not considered a valid use case, the error message is too confusing to understand the relationship to the problem (adding platforms to the jacoco configuration isn't supported). In that case, I'd recommend updating the Jacoco plugin to understand this case and provide a better error message or behavior, possibly using withDependencies.
Steps to Reproduce

https://github.com/anuraaga/gradle-platform-default-dependencies
./gradlew test jacocoTestReport
Your Environment

Gradle 6.0-rc-2, Windows, Java 13 (zulu)

I have to disagree with the initial reasoning. :)
In Gradle, a platform dependency is a dependency as every other dependency. The platform() only decides what to pick from the thing you depend on. With variant-aware dependency management each component can have multiple variants. platform() only says that we want to pick a platform variant. In theory, the targeted component can have both platform and library variants. And a java-platform can also have dependencies with allowDependencies().
For the concrete use case:
Adding the dependency to jacocoorg.jacoco:org.jacoco.agent (without version) should fix the problem - jacocoAgent("jacocoorg.jacoco:org.jacoco.agent").

I understand those semantics for platform dependencies, which does make sense. But it makes me feel that in such a case, defaultDependencies loses a lot of it's purpose - what is a good pattern for it with the presence of platforms? As you say, "The platform() only decides what to pick from the thing you depend on" so it seems it should still run when there are only platforms, to give a chance to decide the things you depend on.
Also, I did use adding the dependencies like you mentioned as a workaround (before really understanding what was going on). At some point of version upgrades or something, I ended up with a jacoco error of "configuration resolved to two files" :( I'm still not sure why that happened but assumed my workaround was bad in the first place and finally looked at the jacoco code to see defaultDependencies and thought it is a bad interaction with it and platform.
Anyways, my 2c and additional observation of having a weird issue with that workaround. Either way I'd be happy enough if Jacoco plugin gave a less cryptic error :)

"configuration resolved to two files"

Would be interesting to know what the other file was there. Maybe this is something that could be improved in how this is done in JaCoCo. There is a PR attempting to improve things here already (#11148) and maybe this can be taken into account if we better understand the problem. We can certainly think about improving the error message.

defaultDependencies loses a lot of its purpose - what is a good pattern for it with the presence of platforms?

In my mind the usage for defaultDependencies is limited to very specific use cases already. The moment a decision is made to use the defaults is before Gradle knows what the declared dependencies will resolve to.
My recommendation would be to not rely on defaultDependencies at all. There are other options to add a "default" like the one you expected here.
I.e. the JaCoCo plugin could fall back to the default if an error occurs after resolution.
Or you can use Configuration.withDependencies {}, where you can also add "defaults" after inspecting what was declared. There is no "one-fit-all" solution here in my opinion.

I agree with the reasoning and that there seem to be very few use cases for defaultDependencies. So does it make sense to rename this issue to focus on jacoco - Jacoco plugin should fall back to defaults if user provided dependencies don't resolve to jacoco?

Yes. Please rename the issue @anuraaga.


Add DriveToCenterStage

Define a set of pose2ds (currentPose - get from chassis, final pose - at the center stage, second to last pose in front of the center stage 1 meter away.  Based on current pose, add a couple of poses to go past the stage.   May need sets for each color.
call std::vector< frc::Translation2d > PathPlannerPath::bezierFromPoses( std::vector< frc::Pose2d > poses |) to calculate bezier points.
construct a pathplannerpath using these bezier points  PathPlannerPath::PathPlannerPath ( td::vector< frc::Translation2d >bezierPoints, PathConstraints constraints, GoalEndState goalEndState, bool reversed = false)

See https://pathplanner.dev/pplib-create-a-path-on-the-fly.html for an example

Get a trajectory from the path similar to DrivePathPlanner    auto trajectory = path->getTrajectory(speed, pose.Rotation()); utilizing the current speed and pose from the chassis
Update ChassisMovement with this information
Call SwerveChassis->Drive method with the chassismovement

Leverage DragonDriveTargetFinder::GetInstance()->GetPose and DragonDriveTargetFinder::SetCorrection methods


fix delete integration step

  clickDeleteIntegration(integrationName: string, rootElement: ElementFinder): P<any> {
    log.info(`clicking delete link for integration ${integrationName}`);
    log.info(`root element ${rootElement}`);

    const parentElement = rootElement.all(by.className('integration')).filter(function(elem, index) {
      return elem.element(by.className('name')).getText().then(function(text) {
        return text === integrationName;
      });
    });

    parentElement.first().element(by.id('dropdownKebabRight9')).click();
    this.rootElement.element(by.linkText('Delete')).click();
    return this.rootElement.element(by.buttonText('Delete')).click();
  }

find better place than app.po.ts
may crash cucumber

 ✔ And Integration "One step integration" is present in integrations list
2017-07-10 13:51:29,698 INFO [root] clicking delete link for integration One step integration
2017-07-10 13:51:29,699 INFO [root] root element [object Object]
[13:51:31] E/launcher - Index out of bound. Trying to access element at index: 0, but there are only 0 elements that match locator By(css selector, .integration)
[13:51:31] E/launcher - NoSuchElementError: Index out of bound. Trying to access element at index: 0, but there are only 0 elements that match locator By(css selector, .integration)
    at WebDriverError (/home/jludvice/devel/redhat/ipaas/syndesis-e2e-tests/node_modules/selenium-webdriver/lib/error.js:27:5)
    at NoSuchElementError (/home/jludvice/devel/redhat/ipaas/syndesis-e2e-tests/node_modules/selenium-webdriver/lib/error.js:168:5)
    at selenium_webdriver_1.promise.all.then (/home/jludvice/devel/redhat/ipaas/syndesis-e2e-tests/node_modules/protractor/lib/element.ts:287:17)
    at ManagedPromise.invokeCallback_ (/home/jludvice/devel/redhat/ipaas/syndesis-e2e-tests/node_modules/selenium-webdriver/lib/promise.js:1366:14)
    at TaskQueue.execute_ (/home/jludvice/devel/redhat/ipaas/syndesis-e2e-tests/node_modules/selenium-webdriver/lib/promise.js:2970:14)
    at TaskQueue.executeNext_ (/home/jludvice/devel/redhat/ipaas/syndesis-e2e-tests/node_modules/selenium-webdriver/lib/promise.js:2953:27)
    at asyncRun (/home/jludvice/devel/redhat/ipaas/syndesis-e2e-tests/node_modules/selenium-webdriver/lib/promise.js:2813:27)
    at /home/jludvice/devel/redhat/ipaas/syndesis-e2e-tests/node_modules/selenium-webdriver/lib/promise.js:676:7
    at process._tickCallback (internal/process/next_tick.js:109:7)Error
    at ElementArrayFinder.applyAction_ (/home/jludvice/devel/redhat/ipaas/syndesis-e2e-tests/node_modules/protractor/lib/element.ts:482:23)
    at ElementArrayFinder.(anonymous function) [as click] (/home/jludvice/devel/redhat/ipaas/syndesis-e2e-tests/node_modules/protractor/lib/element.ts:96:21)
    at ElementFinder.(anonymous function) [as click] (/home/jludvice/devel/redhat/ipaas/syndesis-e2e-tests/node_modules/protractor/lib/element.ts:873:14)
    at AppPage.clickDeleteIntegration (/home/jludvice/devel/redhat/ipaas/syndesis-e2e-tests/e2e/app.po.ts:155:65)
    at IntegrationSteps.deleteIntegration (/home/jludvice/devel/redhat/ipaas/syndesis-e2e-tests/e2e/integrations/integration.steps.ts:61:27)
    at World.bindingFunc (/home/jludvice/devel/redhat/ipaas/syndesis-e2e-tests/node_modules/cucumber-tsflow/src/BindingDecorator.ts:145:85)
[13:51:31] E/launcher - Process exited with error code 199
error Command failed with exit code 199.

@lvydra looks like developers changed integration editor -> Add a Step button changed  behavior and on click it displays some popup messages...

@lvydra any progress on this issue?

I've fixed the main issue via https://github.com/syndesisio/syndesis-e2e-tests/commit/e8fa83fc15113f764ab0f50be4075f1b6156b929. If you guys (@jludvice @lvydra) still feel that it can be further improved pls go ahead. I'm gonna close it for now.

I suspect
parentElement.first().element(by.id('dropdownKebabRight9')).click();
to be a cause of potential falling.
I got some solution for it already.


feat(forge): commit state between invariant runs

Motivation
Closes #3005.
Solution
Do not drop the executor between runs, but rather use the same executor.

This is incredibly slow though @mattsse — do you think there's another way to do this? If not, we probably shouldn't do this because of performance regressions.

Hey @mds1 looping you in here too—This is a direct fix for #3005 but introduces serious performance regressions, and i'm unsure if we have another way of doing this. I'd say we should hold off of merging this

Hmm, can you help me understand why this has such a big performance regression? We already commit state for all non-test contracts, so it seems surprising that committing state for the test contract would cause this

@mds1 @mattsse nevermind about performance regressions—something was affecting my environment and made builds super slow. Just moved to my new laptop and this is fine.
Just tested doing foundryup from this branch commit and the performance difference seems completely negligible. I think we can merge this in! Just a sanity test, can you test this branch @mds1 ?

nevermind about performance regressions—something was affecting my environment and made builds super slow. Just moved to my new laptop and this is fine.

Oh awesome, that's great news!
Definitely can test, cc @lucas-manuel @PaulRBerg to sanity test also :)

Closing, this is not the correct solution to #3005 — i'll followup with the proper fix


excluded paths: server functions not found

Server function not found after insert it on excluded paths
now the server functions are successfully excluded but also removed from REGISTERED_SERVER_FUNCTIONS this leads to the fact that handle_server_fns no longer works over the excluded functions, is it possible to exclude them only from automatic path generation?
To Reproduce
Steps to reproduce the behavior:
    let routes = generate_route_list_with_exclusions(
        {
            let options = leptos_options.clone();
            move || shell(options.clone())
        },
        Some(vec!["/api/my_server_functions".into()]),
    );

    Router::new().leptos_routes(&leptos_options, routes, {
            let options = leptos_options.clone();
            move || shell(options.clone())
        }) .route(
            "/api/my_server_functions",
            post(handle_server_fn)
        )

Could not find a server function at the route /api/my_server_functions.

It's likely that either
 1. The API prefix you specify in the `#[server]` macro doesn't match the prefix at which your server function handler is mounted, or
2. You are on a platform that doesn't support automatic server function registration and you need to call ServerFn::register_explicit() on the server function type, somewhere in your `main` function.

Expected behavior
handle_server_fns should be able to find the function so that it can be handled with axum together with the route and the layer

Duplicate of #3150.

Fixed by #3176


Create a contact info block

Add links to social networks (LinkedIn, Facebook, Instagram), phone number, email, Telegram username, etc.

created contact info block about myself


Adjust when strip-olytics-params.js middleware should redirect & clean url.

When no IdentityX context  is set, but there is an incoming oly_enc_id it now set the olytics cookie without forcing redirect.  It will now only redirect when there is an incoming Id conflict.  Meaning there is already an idX user context present that doesn't match the incoming request oly_enc_id.  Basically remove it and reload the page with the already set idX user context.

 Encrypted ID is being passed to Alchemer form


[ZT] WARP firewall additions

applies review feedback to #12509 and #14507

@ranbel I think this part is not covered yet. Can you adding this part as well?
Tunnel latency check through `icmpv4` probe to `<IP_ADDRESS>/24` WARP endpoint, is performed by WARP statistics service.


[List] Improve hover/select/focus UI display

[ ] I have followed (at least) the PR section of the contributing guide.

Closes #5186
Related to #19343

@joshwooding What's missing from the pull request?

@joshwooding What's missing from the pull request?

Nothing :) Had something I wanted to double-check but it was fine.

The logic looks really close to what we have on Pagination and TreeView. I think that we can scale it to all the other components now :)

Do we want to add a combination of focusedVisible + hover?

From what I recall during the initial implementation of the states styles, we made simplifications in order to reduce simplify overrides and the overall logic. Probably too much. Later on, we realized that it was important to differentiate the opacity style of "focus visible" vs. "hover" because they had significant different use cases (with focus visible, you need more contrast than a hover. But at the same time, focus visible is too much contrast for a hover)
Regarding the combinatory of the two states. Does the added complexity worth it?

Regarding the combinatory of the two states. Does the added complexity worth it?

Probably not. My point was, to me it was not clear why we would combine some states and not others, and where is this documented and how can we make sure it will be consistent across the components. On the other hand if I know that I always need to combine state, then we could be more confident that the consistency will be kept.
Combination of opacity does not have to be the answer for this, but it would be useful, at least for me if we have some form of documentation or guide on how do we combine states. Or if we don't combine all of them, than maybe it would be better to directly define in the theme the combinations that we support instead of doing calculation sometimes, but not always.
Anyway all this is probably just for my clarification and should not block this PR if the colors used now are by design.


@conda-forge-admin, please add user @hmaarrfk

    @conda-forge-admin, please add user @hmaarrfk

Originally posted by @hmaarrfk in https://github.com/conda-forge/nss-feedstock/issues/59#issuecomment-1331698713

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @hmaarrfk in conda-forge/nss-feedstock#62.


Is the project still alive?

Sorry for asking this, but is this awesome project still alive?
Thanks!

This does not work since the update to create-react-app 2

Sorry, @anonimusprogramus for the late response. Although it's not actively being developed, I'm still maintaining. Thank you.


Update submodule to fix linux basion deployment

Update submodule to the latest commit to fix linux bastion deployment. Tested in IAD and deployment succeeded.

I got an error while deploying the template from AWS official partner site page where the bastion didn't deploy and cloudformation error read it as : ec2 didn't receive signal. Did you receive the same error ?
I will try using your branch too for deploying if this works
Any other help would be appreciated too


[CONTRIB] Dockerfile and Splunk Support

Hi!
I learned of Twint awhile ago, and wanted to play around with it.  However, since I am very heavily into Docker these days, I couldn't find a Dockerized version, so I decided to make one:
https://github.com/dmuth/splunk-twint
You can run the Dockerized version of Twint right from the command line as follows:
bash <(curl -s https://raw.githubusercontent.com/dmuth/twint-splunk/master/twint) -u dmuth --year 2020 --since 2019-01-01
Along the way, I discovered that the Pandas module, which I wasn't using when calling Twint from the command line, was adding minutes to my build time.  So I tried programmatically removing references to Pandas from the code when building the Docker container, and much to my surprise, it worked!  This reduces the build time on my older iMac from approximately 15 minutes to 30 seconds.  :-)
But wait, there's a more!  I'm a big time user of Splunk at my day job (enterprise logging/analytics), and seeing that Splunk has a free license for up to 500 MB/day of data, I also use it out of the office as my analytics tool of choice.  So I decided to build a Splunk app to ingest and visualize tweets downloaded with Twint.  That app is also included with my Dockerized version of Twint.
Let me know what you think--and if you'd like to borrow my Dockerfiles, feel free!  I also found a bug along the way, but I will report that in a separate issue. :-)
Best,
-- Doug

We could create a repository for this, sounds good to you? I'd give you write-rights so that you can push, edit, etc. anytime

Hmm, so like a separate repo under https://github.com/twintproject?  Sure, why not?  If we could get twint-splunk as the name, that would be great, and I could push future work there.
Thanks!
-- Doug

I created the repo named as you suggested and added you as collaborator with write rights, you should get a notification soon!

Alright, looks like I have access to https://github.com/twintproject/twint-splunk now.
Since it's under your organization, do you have any guidelines (technical or otherwise) for how you'd like to see stuff pushed there?  I was planning on starting with pushing a copy of my current repo, and see if GitHub will let me copy future commits/branches from https://github.com/dmuth/splunk-twint over to https://github.com/twintproject/twint-splunk as well.
Also, once it's up, I was going to mention it on my Twitter feed as well as write something up on my blog, unless you had other plans?  If so, please let me know!
Thanks,
-- Doug

As of now there are not guidelines to follow, the only requests that I'd like to make are:

comments about code/instructions/declarations are welcome but not a must
"pythonic" code is welcome, so that people can integrate it easily with other tools
feel free to provide a short guide/documentation so that I'll add it to the wiki

Feel free to create a post on your blog and to give me the link so that I'll add it to our README
About moving the code, you can add twint-splunk as remote of your local splunk-twint and then push to it (twint-splunk). Otherwise you can just copy and paste the code, remember to not copy the .git directory. Those are just my suggestions, feel free to do as you may prefer!

Okay, code has been uploaded to https://github.com/twintproject/twint-splunk
Most of the code is shell, and I did my best to ensure it was documented.
Let me know if you think the README is sufficient, if not I can work on it.  I'll write a blog post in a week or two, as I have a few unrelated things to clear off my plate first. :-)
-- Doug

At a first glance it's amazing! I hope to try it out this weekend!
Please join osint.team (with either Twitter or Github account) so that you can easily collect feedback from the OSINT community.


Upgrade logs-elasticsearch version

I'd like to merge and deploy this tomorrow morning.
Before merging

[ ] Disable Puppet on all logs-elasticsearch machines

:+1: go merge

Going to close this for now, we probably need to take more care with it.


Signature verification failed

when i start tor browser it gives signature verification failed and generate
Error code:GENERIC_VERIFY_FAIL

Same error with latest git version

@Rohitashriyuga @blackPantherOS what's your gnupg version?
You can use the command below to check.
$ dpkg -l gnupg gnupg2

I'm having the same issue pointed out by @blackPantherOS. For me, the output of dpkg -1 gnupg gnupg2 is :
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                    Version          Architecture     Description
+++-=======================-================-================-===================================================
ii  gnupg                   2.2.10-1~bpo9+1  all              GNU privacy guard - a free PGP replacement
ii  gnupg2                  2.1.18-8~deb9u2  all              GNU privacy guard - a free PGP replacement (dummy t

@rogers0, I failed to download the tor browser using both the backports and experimental version. As such, I currently have the latest version available here installed (though it fails as well):
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                Version      Architecture Description
+++-===================-============-============-===========================================================
ii  torbrowser-launcher 0.3.0-1      all          A program to help you securely download and run Tor Browser

Sorry that I'm late.. I'm very busy , so tested with:
GnuPG version is: 1.4.21  and GnuPG2 version is: 2.1.18 working fine
after upgrade to:
GnuPG version is: 1.4.23  and GnuPG2 version is: 2.2.10 won't work anymore.
The problem source is the GnuPG2  2.2.10 but all gpg2 test passed was after build

@rogers0 :
> gpg --homedir ~/.local/share/torbrowser/gnupg_homedir --recv-keys EF6E286DDA85EA2A4BA7DE684E2C6E8793298290
gpg: WARNING: unsafe permissions on homedir '/home/user/.local/share/torbrowser/gnupg_homedir'
gpg: connecting dirmngr at '/run/user/1000/gnupg/d.dniezwd1guds6p6c6uwjr6bf/S.dirmngr' failed: IPC connect call failed
gpg: keyserver receive failed: No dirmngr

@hThoreau this log shows the problem is gnupg, not torbrowser-launch
I recommend you to remove ~/.local/share/torbrowser/gnupg_homedir and try to start torbrowser-launch again.

@rogers0 That worked. Though now I'm getting a blank screen when launching the Tor browser. 0_o

Run this command in the terminal :
gpg --homedir "$HOME/.local/share/torbrowser/gnupg_homedir/" --refresh-keys --keyserver pool.sks-keyservers.net
and then try to install the TOR Browser.

Running rm -r ~/.config/torbrowser ~/.cache/torbrowser ~/.local/share/torbrowser before trying to reinstall has solved my problem. :smile:


QuantumLeap integration with OrionCB and IoTagent-LoRaWAN

Describe the bug
I'm not sure if this is a bug or I am doing something wrong.
To Reproduce
Steps to reproduce the behavior:

First I've posted a device in the IoTagent-LoRaWAN and apparently is receiving the payload as you can see in the picture

However I'm gettin that "level":"error","message":"Could not cast message to NGSI" error message in the logs despite all containers are working as expected. Also I'm not sure how OrionCB, IoTagent-LoRaWAN and QuantumLeap interact between them; according to their docs I have to create a subscription in order to OrionCB notifies QuantumLeap to store the information in CrateDB but ... Should not I first create an entity attached to the IoTagent-LoRaWAN device that I've previously created?

Expected behavior
POST request to  http://localhost:8668/v2/subscribe?orionUrl=http://localhost:1026/v2&quantumleapUrl=http://localhost:8668/v2 returns a 200 OK code (?)
Environment (please complete the following information):

FIWARE GenericEnablers are running over docker
I'm using Postman and Curl to do HTTP requests
QuantumLeap version is 0.5.0; OrionCB version is 2.4.0-next and IoTagent-LoRaWAN version is 2.10.0-next

Additional context
I'll provide in followin answers if necessary
Sorry if this is not the right place to ask this kind of things but I did also a question in StackOverflow but I'm not sure this will be answered

Well, apparently it was my fault and the docker-compose.yml file was not deploying properly mongodb and orioncb so they cannot connect between them. However, ... now I'm able to create an entity through a POST request to the IoTagent-LoRaWAN when I create a device, also I'm able to create the subscription sending this body in another POST request to orioncb
{
  "description": "A subscription to get info about LORA-N-0",
  "subject": {
    "entities": [
      {
        "id": "LORA-N-0",
        "type": "LoraDevice"
      }
    ],
    "condition": {
      "attrs": [
        "analog_in_1"
      ]
    }
  },
  "notification": {
    "http": {
      "url": "http://quantumleap:8668/v2/notify"
    },
    "attrs": [
      "analog_in_1"
    ],
    "metadata": ["dateCreated", "dateModified"]
  },
  "throttling": 5
}

As you can see in the picture the subscription is apparently created correctly

However ... also as you can see in the picture ... QuantumLeap is throwing the following exception with its corresponding traceback
quantumleap_1  | INFO:reporter.reporter:Received payload: {'id': 'LORA-N-0', 'type': 'LoraDevice', 'analog_in_1': {'type': 'Number', 'value': 96.64, 'metadata': {'dateCreated': {'type': 'DateTime', 'value': '2020-06-25T08:36:55.00Z'}, 'dateModified': {'type': 'DateTime', 'value': '2020-06-25T09:21:41.00Z'}}}}
quantumleap_1  | INFO:geocoding.geocoding:Cannot add location to entity (type: "LoraDevice", id: "LORA-N-0"), missing "address" attribute.
quantumleap_1  | [2020-06-25 09:21:41,652] ERROR in app: Exception on /v2/notify [POST]
quantumleap_1  | Traceback (most recent call last):
quantumleap_1  |   File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1982, in wsgi_app
quantumleap_1  |     response = self.full_dispatch_request()
quantumleap_1  |   File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1614, in full_dispatch_request
quantumleap_1  |     rv = self.handle_user_exception(e)
quantumleap_1  |   File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1517, in handle_user_exception
quantumleap_1  |     reraise(exc_type, exc_value, tb)
quantumleap_1  |   File "/usr/local/lib/python3.6/site-packages/flask/_compat.py", line 33, in reraise
quantumleap_1  |     raise value
quantumleap_1  |   File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1612, in full_dispatch_request
quantumleap_1  |     rv = self.dispatch_request()
quantumleap_1  |   File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1598, in dispatch_request
quantumleap_1  |     return self.view_functions[rule.endpoint](**req.view_args)
quantumleap_1  |   File "/usr/local/lib/python3.6/site-packages/connexion/decorators/decorator.py", line 73, in wrapper
quantumleap_1  |     response = function(request)
quantumleap_1  |   File "/usr/local/lib/python3.6/site-packages/connexion/decorators/uri_parsing.py", line 117, in wrapper
quantumleap_1  |     response = function(request)
quantumleap_1  |   File "/usr/local/lib/python3.6/site-packages/connexion/decorators/validation.py", line 163, in wrapper
quantumleap_1  |     response = function(request)
quantumleap_1  |   File "/usr/local/lib/python3.6/site-packages/connexion/decorators/validation.py", line 336, in wrapper
quantumleap_1  |     return function(request)
quantumleap_1  |   File "/usr/local/lib/python3.6/site-packages/connexion/decorators/decorator.py", line 44, in wrapper
quantumleap_1  |     response = function(request)
quantumleap_1  |   File "/usr/local/lib/python3.6/site-packages/connexion/decorators/parameter.py", line 207, in wrapper
quantumleap_1  |     return function(**kwargs)
quantumleap_1  |   File "/src/ngsi-timeseries-api/src/reporter/reporter.py", line 179, in notify
quantumleap_1  |     trans.insert([payload], fiware_s, fiware_sp)
quantumleap_1  |   File "/src/ngsi-timeseries-api/src/translators/crate.py", line 183, in insert
quantumleap_1  |     fiware_servicepath)
quantumleap_1  |   File "/src/ngsi-timeseries-api/src/translators/crate.py", line 260, in _insert_entities_of_type
quantumleap_1  |     self._update_metadata_table(table_name, original_attrs)
quantumleap_1  |   File "/src/ngsi-timeseries-api/src/translators/crate.py", line 352, in _update_metadata_table
quantumleap_1  |     self.cursor.execute(stmt, (table_name, persisted_metadata))
quantumleap_1  |   File "/usr/local/lib/python3.6/site-packages/crate/client/cursor.py", line 54, in execute
quantumleap_1  |     bulk_parameters)
quantumleap_1  |   File "/usr/local/lib/python3.6/site-packages/crate/client/http.py", line 328, in sql
quantumleap_1  |     content = self._json_request('POST', self.path, data=data)
quantumleap_1  |   File "/usr/local/lib/python3.6/site-packages/crate/client/http.py", line 448, in _json_request
quantumleap_1  |     _raise_for_status(response)
quantumleap_1  |   File "/usr/local/lib/python3.6/site-packages/crate/client/http.py", line 187, in _raise_for_status
quantumleap_1  |     error_trace=error_trace)
quantumleap_1  | crate.client.exceptions.ProgrammingError: SQLActionException[SQLParseException: line 1:72: no viable alternative at input 'on duplicate']
quantumleap_1  | <IP_ADDRESS> - - [25/Jun/2020 09:21:41] "POST /v2/notify HTTP/1.1" 500 -
quantumleap_1  | INFO:werkzeug:<IP_ADDRESS> - - [25/Jun/2020 09:21:41] "POST /v2/notify HTTP/1.1" 500 -

Here is also my docker-compose.yml Is it maybe the QuantumLeap version? :thinking:

Hello @WyRe, thank you for getting in touch.

POST request to
http://localhost:8668/v2/subscribe?orionUrl=http://localhost:1026/v2&quantumleapUrl=http://localhost:8668/v2
returns a 200 OK code (?)

As you noted, the problem there was that in your initial setup QuantumLeap wouldn't be able to reach Orion on localhost since Orion was in the Docker network. If you'd like to access QuantumLeap and Orion from your localhost too, you could try setting up a Docker compose bridge network, see e.g. https://github.com/smartsdk/ngsi-timeseries-api/blob/master/src/reporter/tests/docker-compose.yml.

Here is also my docker-compose.yml Is it maybe the QuantumLeap version?

Most likely yes. The version you have in your Docker compose (0.5) doesn't work with the latest Crate---the crate image points to version 4.1 which isn't supported by QuantumLeap 0.5. Try changing your Docker compose like so
quantumleap:
    image: smartsdk/quantumleap:0.7.5
...
crate:
    image: crate:3.3.5
...

Hope this helps.

@c0c0n3 oh no, thank to you! Now it's apparently working :smile:
fiware-iot-agent | time=2020-06-25T10:05:58.790Z | lvl=DEBUG | corr=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | trans=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | op=IoTAgentNGSI.NGSIService | srv=atosioe | subsrv=/lorattn | msg=error {"name":"DEVICE_GROUP_NOT_FOUND","message":"Couldn\t find device group","code":404} in get group device | comp=IoTAgent
fiware-iot-agent | time=2020-06-25T10:05:58.791Z | lvl=DEBUG | corr=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | trans=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | op=IoTAgentNGSI.NGSIService | srv=atosioe | subsrv=/lorattn | msg=typeInformation {"id":"node_0","type":"LoraDevice","name":"LORA-N-0","service":"atosioe","subservice":"/lorattn","active":[{"object_id":"analog_in_1","name":"analog_in_1","type":"Number"}],"timezone":"Europe/Madrid","internalAttributes":{"lorawan":{"application_server":{"host":"eu.thethings.network","username":"dendrometer","password":"ttn-account-v2.173lH8wwDiIRC8E2JgM9ScXyuNRlPpMefpazS0TIhnU","provider":"TTN"},"dev_eui":"00EC51D264A6F8FD","app_eui":"70B3D57ED0030B5D","application_id":"dendrometer","application_key":"7AF6B9A29EAF893F66C0F4360BA8DD5B"}},"internalId":null,"subscriptions":[],"creationDate":1593079329781} | comp=IoTAgent
fiware-iot-agent | time=2020-06-25T10:05:58.791Z | lvl=DEBUG | corr=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | trans=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | op=IoTAgentNGSI.NGSIService | srv=atosioe | subsrv=/lorattn | msg=typeInformation: {"id":"node_0","type":"LoraDevice","name":"LORA-N-0","service":"atosioe","subservice":"/lorattn","active":[{"object_id":"analog_in_1","name":"analog_in_1","type":"Number"}],"timezone":"Europe/Madrid","internalAttributes":{"lorawan":{"application_server":{"host":"eu.thethings.network","username":"dendrometer","password":"ttn-account-v2.173lH8wwDiIRC8E2JgM9ScXyuNRlPpMefpazS0TIhnU","provider":"TTN"},"dev_eui":"00EC51D264A6F8FD","app_eui":"70B3D57ED0030B5D","application_id":"dendrometer","application_key":"7AF6B9A29EAF893F66C0F4360BA8DD5B"}},"internalId":null,"subscriptions":[],"creationDate":1593079329781} | comp=IoTAgent
fiware-iot-agent | time=2020-06-25T10:05:58.792Z | lvl=DEBUG | corr=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | trans=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | op=IoTAgentNGSI.NGSIService | srv=atosioe | subsrv=/lorattn | msg=Updating device value in the Context Broker at [http://orion:1026/v2/entities/LORA-N-0/attrs?type=LoraDevice] | comp=IoTAgent
fiware-iot-agent | time=2020-06-25T10:05:58.792Z | lvl=DEBUG | corr=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | trans=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | op=IoTAgentNGSI.NGSIService | srv=atosioe | subsrv=/lorattn | msg=Using the following request:
fiware-iot-agent | {
fiware-iot-agent |     "url": "http://orion:1026/v2/entities/LORA-N-0/attrs?type=LoraDevice",
fiware-iot-agent |     "method": "POST",
fiware-iot-agent |     "headers": {
fiware-iot-agent |         "fiware-service": "atosioe",
fiware-iot-agent |         "fiware-servicepath": "/lorattn"
fiware-iot-agent |     },
fiware-iot-agent |     "json": {
fiware-iot-agent |         "analog_in_1": {
fiware-iot-agent |             "type": "Number",
fiware-iot-agent |             "value": 96.64,
fiware-iot-agent |             "metadata": {
fiware-iot-agent |                 "TimeInstant": {
fiware-iot-agent |                     "type": "DateTime",
fiware-iot-agent |                     "value": "2020-06-25T12:05:58.791+02:00"
fiware-iot-agent |                 }
fiware-iot-agent |             }
fiware-iot-agent |         },
fiware-iot-agent |         "TimeInstant": {
fiware-iot-agent |             "type": "DateTime",
fiware-iot-agent |             "value": "2020-06-25T12:05:58.791+02:00"
fiware-iot-agent |         }
fiware-iot-agent |     }
fiware-iot-agent | }
fiware-iot-agent |  | comp=IoTAgent
fiware-iot-agent | time=2020-06-25T10:05:58.801Z | lvl=DEBUG | corr=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | trans=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | op=IoTAgentNGSI.NGSIService | srv=atosioe | subsrv=/lorattn | msg=Received the following response from the CB: Value updated successfully
fiware-iot-agent |  | comp=IoTAgent
fiware-iot-agent | {"timestamp":"2020-06-25T10:05:58.801Z","level":"info","message":"Observations sent to CB successfully for device "}
fiware-iot-agent | {"timestamp":"2020-06-25T10:07:03.458Z","level":"info","message":"New message in topic"}
fiware-iot-agent | {"timestamp":"2020-06-25T10:07:03.459Z","level":"info","message":"IOTA provisioned devices:"}
fiware-iot-agent | {"timestamp":"2020-06-25T10:07:03.460Z","level":"info","message":"Decoding CaynneLPP message:AQIlwA=="}
fiware-iot-agent | time=2020-06-25T10:07:03.460Z | lvl=DEBUG | corr=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | trans=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | op=IoTAgentNGSI.NGSIService | srv=atosioe | subsrv=/lorattn | msg=executeWithDeviceInfo entityName LORA-N-0 type LoraDevice apikey  attributes [{"name":"analog_in_1","type":"Number","value":96.64}] deviceInformation {"id":"node_0","type":"LoraDevice","name":"LORA-N-0","service":"atosioe","subservice":"/lorattn","active":[{"object_id":"analog_in_1","name":"analog_in_1","type":"Number"}],"timezone":"Europe/Madrid","internalAttributes":{"lorawan":{"application_server":{"host":"eu.thethings.network","username":"dendrometer","password":"ttn-account-v2.173lH8wwDiIRC8E2JgM9ScXyuNRlPpMefpazS0TIhnU","provider":"TTN"},"dev_eui":"00EC51D264A6F8FD","app_eui":"70B3D57ED0030B5D","application_id":"dendrometer","application_key":"7AF6B9A29EAF893F66C0F4360BA8DD5B"}},"internalId":null,"subscriptions":[],"creationDate":1593079329781} | comp=IoTAgent
fiware-iot-agent | time=2020-06-25T10:07:03.461Z | lvl=DEBUG | corr=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | trans=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | op=IoTAgentNGSI.NGSIService | srv=atosioe | subsrv=/lorattn | msg=error {"name":"DEVICE_GROUP_NOT_FOUND","message":"Couldn\t find device group","code":404} in get group device | comp=IoTAgent
fiware-iot-agent | time=2020-06-25T10:07:03.461Z | lvl=DEBUG | corr=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | trans=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | op=IoTAgentNGSI.NGSIService | srv=atosioe | subsrv=/lorattn | msg=typeInformation {"id":"node_0","type":"LoraDevice","name":"LORA-N-0","service":"atosioe","subservice":"/lorattn","active":[{"object_id":"analog_in_1","name":"analog_in_1","type":"Number"}],"timezone":"Europe/Madrid","internalAttributes":{"lorawan":{"application_server":{"host":"eu.thethings.network","username":"dendrometer","password":"ttn-account-v2.173lH8wwDiIRC8E2JgM9ScXyuNRlPpMefpazS0TIhnU","provider":"TTN"},"dev_eui":"00EC51D264A6F8FD","app_eui":"70B3D57ED0030B5D","application_id":"dendrometer","application_key":"7AF6B9A29EAF893F66C0F4360BA8DD5B"}},"internalId":null,"subscriptions":[],"creationDate":1593079329781} | comp=IoTAgent
fiware-iot-agent | time=2020-06-25T10:07:03.468Z | lvl=DEBUG | corr=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | trans=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | op=IoTAgentNGSI.NGSIService | srv=atosioe | subsrv=/lorattn | msg=typeInformation: {"id":"node_0","type":"LoraDevice","name":"LORA-N-0","service":"atosioe","subservice":"/lorattn","active":[{"object_id":"analog_in_1","name":"analog_in_1","type":"Number"}],"timezone":"Europe/Madrid","internalAttributes":{"lorawan":{"application_server":{"host":"eu.thethings.network","username":"dendrometer","password":"ttn-account-v2.173lH8wwDiIRC8E2JgM9ScXyuNRlPpMefpazS0TIhnU","provider":"TTN"},"dev_eui":"00EC51D264A6F8FD","app_eui":"70B3D57ED0030B5D","application_id":"dendrometer","application_key":"7AF6B9A29EAF893F66C0F4360BA8DD5B"}},"internalId":null,"subscriptions":[],"creationDate":1593079329781} | comp=IoTAgent
fiware-iot-agent | time=2020-06-25T10:07:03.470Z | lvl=DEBUG | corr=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | trans=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | op=IoTAgentNGSI.NGSIService | srv=atosioe | subsrv=/lorattn | msg=Updating device value in the Context Broker at [http://orion:1026/v2/entities/LORA-N-0/attrs?type=LoraDevice] | comp=IoTAgent
fiware-iot-agent | time=2020-06-25T10:07:03.470Z | lvl=DEBUG | corr=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | trans=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | op=IoTAgentNGSI.NGSIService | srv=atosioe | subsrv=/lorattn | msg=Using the following request:
fiware-iot-agent | {
fiware-iot-agent |     "url": "http://orion:1026/v2/entities/LORA-N-0/attrs?type=LoraDevice",
fiware-iot-agent |     "method": "POST",
fiware-iot-agent |     "headers": {
fiware-iot-agent |         "fiware-service": "atosioe",
fiware-iot-agent |         "fiware-servicepath": "/lorattn"
fiware-iot-agent |     },
fiware-iot-agent |     "json": {
fiware-iot-agent |         "analog_in_1": {
fiware-iot-agent |             "type": "Number",
fiware-iot-agent |             "value": 96.64,
fiware-iot-agent |             "metadata": {
fiware-iot-agent |                 "TimeInstant": {
fiware-iot-agent |                     "type": "DateTime",
fiware-iot-agent |                     "value": "2020-06-25T12:07:03.469+02:00"
fiware-iot-agent |                 }
fiware-iot-agent |             }
fiware-iot-agent |         },
fiware-iot-agent |         "TimeInstant": {
fiware-iot-agent |             "type": "DateTime",
fiware-iot-agent |             "value": "2020-06-25T12:07:03.469+02:00"
fiware-iot-agent |         }
fiware-iot-agent |     }
fiware-iot-agent | }
fiware-iot-agent |  | comp=IoTAgent
fiware-orion   | time=Thursday 25 Jun 10:07:03 2020.475Z | lvl=INFO | corr=9e10fc36-b6cb-11ea-9471-0242ac1a0005 | trans=1593079220-399-00000000014 | from=<IP_ADDRESS> | srv=atosioe | subsrv=/lorattn | comp=Orion | op=logMsg.h[1844]:lmTransactionStart | msg=Starting transaction from <IP_ADDRESS>:50330/v2/entities/LORA-N-0/attrs
fiware-orion   | time=Thursday 25 Jun 10:07:03 2020.476Z | lvl=INFO | corr=9e10fc36-b6cb-11ea-9471-0242ac1a0005 | trans=1593079220-399-00000000014 | from=<IP_ADDRESS> | srv=atosioe | subsrv=/lorattn | comp=Orion | op=rest.cpp[874]:servicePathSplit | msg=Service Path 0: '/lorattn'
fiware-orion   | time=Thursday 25 Jun 10:07:03 2020.477Z | lvl=INFO | corr=9e10fc36-b6cb-11ea-9471-0242ac1a0005 | trans=1593079220-399-00000000014 | from=<IP_ADDRESS> | srv=atosioe | subsrv=/lorattn | comp=Orion | op=connectionOperations.cpp[244]:collectionCount | msg=Database Operation Successful (count: { _id.id: "LORA-N-0", _id.type: "LoraDevice", _id.servicePath: "/lorattn" })
fiware-orion   | time=Thursday 25 Jun 10:07:03 2020.478Z | lvl=INFO | corr=9e10fc36-b6cb-11ea-9471-0242ac1a0005 | trans=1593079220-399-00000000014 | from=<IP_ADDRESS> | srv=atosioe | subsrv=/lorattn | comp=Orion | op=connectionOperations.cpp[94]:collectionQuery | msg=Database Operation Successful (query: { _id.id: "LORA-N-0", _id.type: "LoraDevice", _id.servicePath: "/lorattn" })
fiware-orion   | time=Thursday 25 Jun 10:07:03 2020.479Z | lvl=INFO | corr=9e10fc36-b6cb-11ea-9471-0242ac1a0005 | trans=1593079220-399-00000000014 | from=<IP_ADDRESS> | srv=atosioe | subsrv=/lorattn | comp=Orion | op=connectionOperations.cpp[454]:collectionUpdate | msg=Database Operation Successful (update: <{ _id.id: "LORA-N-0", _id.type: "LoraDevice", _id.servicePath: "/lorattn" }, { $set: { attrs.analog_in_1: { value: 96.64, type: "Number", md: { TimeInstant: { type: "DateTime", value:<PHONE_NUMBER>.0 } }, mdNames: [ "TimeInstant" ], creDate:<PHONE_NUMBER>, modDate:<PHONE_NUMBER> }, attrs.TimeInstant: { value:<PHONE_NUMBER>.0, type: "DateTime", mdNames: [], creDate:<PHONE_NUMBER>, modDate:<PHONE_NUMBER> }, modDate:<PHONE_NUMBER>, lastCorrelator: "9e10fc36-b6cb-11ea-9471-0242ac1a0005" }, $unset: { location: 1, expDate: 1 } }>)
fiware-orion   | time=Thursday 25 Jun 10:07:03 2020.480Z | lvl=INFO | corr=9e10fc36-b6cb-11ea-9471-0242ac1a0005 | trans=1593079220-399-00000000015 | from=<IP_ADDRESS> | srv=atosioe | subsrv=/lorattn | comp=Orion | op=logMsg.h[1844]:lmTransactionStart | msg=Starting transaction to http://quantumleap:8668/v2/notify
fiware-orion   | time=Thursday 25 Jun 10:07:03 2020.480Z | lvl=INFO | corr=9e10fc36-b6cb-11ea-9471-0242ac1a0005 | trans=1593079220-399-00000000014 | from=<IP_ADDRESS> | srv=atosioe | subsrv=/lorattn | comp=Orion | op=logMsg.h[1874]:lmTransactionEnd | msg=Transaction ended
fiware-orion   | time=Thursday 25 Jun 10:07:03 2020.481Z | lvl=INFO | corr=9e10fc36-b6cb-11ea-9471-0242ac1a0005 | trans=1593079220-399-00000000015 | from=<IP_ADDRESS> | srv=atosioe | subsrv=/lorattn | comp=Orion | op=httpRequestSend.cpp[550]:httpRequestSendWithCurl | msg=Sending message 5 to HTTP server: sending message of 586 bytes to HTTP server
fiware-iot-agent | time=2020-06-25T10:07:03.481Z | lvl=DEBUG | corr=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | trans=c80c1c8b-d05c-4ad5-b865-0ae7b58aa319 | op=IoTAgentNGSI.NGSIService | srv=atosioe | subsrv=/lorattn | msg=Received the following response from the CB: Value updated successfully
fiware-iot-agent |  | comp=IoTAgent
fiware-iot-agent | {"timestamp":"2020-06-25T10:07:03.481Z","level":"info","message":"Observations sent to CB successfully for device "}
quantumleap_1  | INFO:reporter.reporter:Received payload: [{'id': 'LORA-N-0', 'type': 'LoraDevice', 'analog_in_1': {'type': 'Number', 'value': 96.64, 'metadata': {'dateCreated': {'type': 'DateTime', 'value': '2020-06-25T10:02:08.00Z'}, 'dateModified': {'type': 'DateTime', 'value': '2020-06-25T10:07:03.00Z'}}}}]
quantumleap_1  | INFO:geocoding.geocoding:Cannot add location to entity (type: "LoraDevice", id: "LORA-N-0"), missing "address" attribute.
quantumleap_1  | INFO:translators.factory:Env variable QL_CONFIG not set, using default value of:
quantumleap_1  | INFO:translators.factory:no config file specified, using defaults.
quantumleap_1  | INFO:translators.factory:Backend selected for tenant 'atosioe' is: crate
quantumleap_1  | INFO:reporter.reporter:Notification successfully processed
quantumleap_1  | <IP_ADDRESS> - - [25/Jun/2020 10:07:03] "POST /v2/notify HTTP/1.1" 200 -
quantumleap_1  | INFO:werkzeug:<IP_ADDRESS> - - [25/Jun/2020 10:07:03] "POST /v2/notify HTTP/1.1" 200 -
fiware-orion   | time=Thursday 25 Jun 10:07:03 2020.605Z | lvl=INFO | corr=9e10fc36-b6cb-11ea-9471-0242ac1a0005 | trans=1593079220-399-00000000015 | from=<IP_ADDRESS> | srv=atosioe | subsrv=/lorattn | comp=Orion | op=httpRequestSend.cpp[570]:httpRequestSendWithCurl | msg=Notification Successfully Sent to http://quantumleap:8668/v2/notify
fiware-orion   | time=Thursday 25 Jun 10:07:03 2020.606Z | lvl=INFO | corr=9e10fc36-b6cb-11ea-9471-0242ac1a0005 | trans=1593079220-399-00000000015 | from=<IP_ADDRESS> | srv=atosioe | subsrv=/lorattn | comp=Orion | op=httpRequestSend.cpp[579]:httpRequestSendWithCurl | msg=Notification response OK, http code: 200
fiware-orion   | time=Thursday 25 Jun 10:07:03 2020.606Z | lvl=INFO | corr=9e10fc36-b6cb-11ea-9471-0242ac1a0005 | trans=1593079220-399-00000000015 | from=<IP_ADDRESS> | srv=atosioe | subsrv=/lorattn | comp=Orion | op=logMsg.h[1874]:lmTransactionEnd | msg=Transaction ended

And here in Crate I can also see details of my device like analog_in_1

However, ... I was reading the docs about grafana and I was wondering ... Should I use crate:4200 for the host when I configure the data source in Grafana? Because I think it should be localhost:4200 :thinking: I guess I could TIAS
Thank you so much again and I'm closing this because the initial problem is apparently solved :wink:

@c0c0n3 Do you recommend me to use your docker-compose.yml?

Do you recommend me to use your docker-compose.yml

That's just a test file but I suppose you could use it as a starting point :-)

Should I use crate:4200 for the host when I configure the data source in Grafana?
Now Grafana cannot reach CrateDB

Yes, if you're using a Docker compose network, then the Crate container should be reachable using the crate host---as long as crate is also the service name in your Docker compose, if my memory serves me well. Did you try using crate:4200 when setting up the Grafana data source, like you suggested? It should work as far as I can tell since your Crate service exposes port 4200?

Thank you so much, @c0c0n3 it's all working apparently but ... I'd like if you don't mind to ask you a few more things,

Why apparently CrateDB exposes the port 5432 despite I didn't indicated such thing in the docker-compose.yml?

Also ... Which generic enabler does need the redis database and what for? Is it QuantumLeap? It is not theoretically using CrateDB?

Thank you again! :smile:

Why apparently CrateDB exposes the port 5432 despite I didn't indicated such thing in the docker-compose.yml?

Um, not sure. Probably because of this?
https://github.com/crate/docker-crate/blob/master/Dockerfile#L60
(Latest Docker file, haven't checked v3.3.5 but I bet you it's the same :-)

need the redis database and what for? Is it QuantumLeap?

Yes, that's correct. QuantumLeap uses Redis to cache geo-location data. On receiving a notification QL tries to pin down the geo-coords if they're not explicitly specified in the NGSI entity payload. To do that, QL makes a rather expensive call to OpenStreetMap. To reduce latency then, OSM's response gets cached in Redis so that future notifications of the same entity won't have to pay the price twice.

It is not theoretically using CrateDB?

No, while QL could use a CrateDB table as a cache, we found that Redis is much faster both when adding and retrieving entries from the cache.

Thank you again!

Pleasure! :-)


Use correct user name form

@hakonhall please merge if tests pass :)

Merging, as this is a fix.

👍


feat: Stage all hunks in a range.

Fixes #176.
This changes the stage_hunk and reset_hunk functions such that they accept a range. When given a range they will stage / reset all hunks that intersect with the given range.
Examples:

lua:

require"gitsigns".stage_hunk() -- stage the hunk at the cursor
require"gitsigns".stage_hunk({3, 45}) -- stage all hunks in a specific range
require"gitsigns".stage_hunk({vim.fn.line("."), vim.fn.line("v")}) -- stage everything in visual selection

vim command:

:Gitsigns stage_hunk
:3,45Gitsigns stage_hunk
:'<,'>Gitsigns stage_hunk

The reset_hunk variants have the same syntax.

@lewis6991 sorry I left this for so long, got busy with other things. This seems to work quite well now. Both range staging and resetting works, as well as stage undo. I also added some visual mode mappings for stage_hunk and reset_hunk.
There was a bug in create_patch that I had to fix to get this to work correctly. When creating a patch for multiple hunks the block header generated by that function did not consider changes made by previous hunks. This was causing patches to be applied incorrectly when staging multiple hunks.

@lewis6991 Can we merge this, or is it blocked by something?

The change has a merge conflict that needs resolving. Rebase on main then we can merge.

Also squash your commits.

The change has a merge conflict that needs resolving.

Strange. Github showed no conflicts on my end. But I have rebased now.

Also squash your commits.

You can choose to squash when you merge. Should be available from the dropdown on the merge button unless you have explicitly disabled it for this repo.

Many thanks.

You can choose to squash when you merge. Should be available from the dropdown on the merge button unless you have explicitly disabled it for this repo.

You can choose to "squash and merge" or "rebase and merge". I want both so I have "rebase and merge" set as default. Basically I just want to avoid introducing merge commits into the history.

Ah, so "squash and merge" may introduce additional merge commits? Didn't know that, thanks.

Well, I don't know if it does tbh, but since there is no rebase I'd imagine it would.


build fail on cordova platform add android

cordova platform add android
Using cordova-fetch for<EMAIL_ADDRESS>Adding android project...
Creating Cordova project for the Android platform:
        Path: platforms\android
        Package: com.foxdebug.acodefree
        Name: Acode
        Activity: MainActivity
        Android target: android-33
Subproject Path: CordovaLib
Subproject Path: app
Android project created with<EMAIL_ADDRESS>Installing "admob-plus-cordova" for android
Subproject Path: CordovaLib
Subproject Path: app
Installing "cordova-plugin-consent" for android
Subproject Path: CordovaLib
Subproject Path: app
ENOENT: no such file or directory, open 'C:\Users\user\Documents\workplace\acode编译\Acode\platforms\android\app\src\main\java\org\apache\cordova\file\FileUtils.java'

#741

https://github.com/apache/cordova-android/issues/1660#issuecomment-1713891728

apache/cordova-android#1660 (comment)

Have you managed to build the acode app now with this possible solution?

apache/cordova-android#1660 (comment)

Have you managed to build the acode app now with this possible solution?

after change
-        <hook type="before_prepare" src="hooks/modify-java-files.js" />
+        <hook type="after_prepare" src="hooks/modify-java-files.js" />

this problem seems fixed.
After install Gradle and set ANDROID_SDK_ROOT and ANDROID_HOME, I get
=============================================================
==== Changed provider to com.foxdebug.acodefree.provider ====
=============================================================

Checking Java JDK and Android SDK versions
ANDROID_SDK_ROOT=C:\Users\13588\scoop\apps\android-sdk\current\platform-tools (recommended setting)
ANDROID_HOME=C:\Users\13588\scoop\apps\android-sdk\current (DEPRECATED)
Using Android SDK: C:\Users\13588\scoop\apps\android-sdk\current\platform-tools
The "path" argument must be of type string. Received undefined
Done in 31.99s.

I had the same issue which was fixed by running cordova prepare before yarn build

Use yarn setup to setup the project.


Some TextEdit selection improvements

One of the improvements is that it allows using pointer and shift selection together. Scrolling with mouse wheel does not longer end the selection process (closes #1190)
Changed the way shift+click selection works when changing from forward to backwards (and vice versa). It works similarly to shift selection (this is how most editors work).
This video shows the main differences (before,  after).

I am not sure if I used selection.shiftclick_left as it was intended. I see it was set to false if the click+shift selection was backwards and true if it was forward. Did I misinterpret it?
Also selection.selecting_text is no longer being read. I deleted the only condition that was using it.

Nice! :+1:

The last commit fixes vertical scroll when dragging the mouse, as requested in #2739. The sensitivity may be a bit too high, but I guess that can be changed if needed.
The only missing part is that it won't scroll if the mouse is idle, unlike most editors. Nothing annoying, but may be good to introduce.

The PR is working quite fine, thanks!
As you said having scrolling also on idle could be a nice addition, but the current PR is already a great enhancement.
The only little issue left IMO is that it starts scrolling down when you approach the last line of the TextEdit, but does not scroll up when you approach the first line of the TextEdit. To get it scrolling up, you actually have to go a bit further up, something like 20-30 px above the TextEdit area.

Top margin was being truncated, should be fine now.

Works great :)


Export usage requirements

Exported CMake Config may carry imported targets:
$<LINK_ONLY:cjson>
$<LINK_ONLY:ZLIB::ZLIB>
ZLIB::ZLIB

These must be resolved when the config is used.
Exported pc files did't carry these usage requirements at all.

@freerdp-bot test


VT HL7 message failures

Helpdesk has reviewed HL7 file from CDC Prime all patient info appears in code. However user is receiving "PATIENT_RESULT[0].PATIENT.PID.PatientAddress[0].StateOrProvince" Description="Field value not found in validation table"/>" Error on the attached messages.
Andrew Gross<EMAIL_ADDRESS>

These were received from simple report with the patient state = "NA". They were routed to VT based on the ordering facility state which was sent as VT.
@TaneaY @sliu1000 Can you work with SimpleReport to find out how "NA" could be sent in the patient state field?

@TaneaY , Please create a SimpleReport Escalation ticket .

Escalated to SimpleReport engineering. Awaiting response

SimpleReport engineering responded : "After further investigation the reason why patients states would be NA is when their state is not USA.
Specifically in this case, the patient's countries are TON."

Next step is to convey that information from SimpleReport to VT and ask them to propose a solution for these messages and similar messages that may arrive in the future with foreign patient addresses.

Message sent to submitter for proposed solution:
Hi Andrew,
After further investigation SimpleReport team was able to provide the reason why patients states would be NA is when their state is not in the USA.
Specifically in this case, the patient's countries are TON.
How would you like these these messages and similar messages that may arrive in the future with foreign patient addresses to be processed?
Thank you,
Tanea

@TaneaY If the state is NA how is that data being routed to VT? is it based on some other state?

Hi Sharon,
When Brick investigated he discovered that they were routed to VT based on the ordering facility state which was sent as VT from SR. Then, I escalated to SR engineers to find out why and they responded that it was because they were out of the country patient addresses. So far, VT has not responded as to how they would like future results like this filtered.
Thank you,
Tanea
The SimpleReport Support Team
Contact us at @.***
Support hours:  8:00 am through 9:00 pm Eastern time
Monday-Friday, excluding US public holidays

From: sliu1000 @.>
Sent: Monday, January 30, 2023 11:39 AM
To: CDCgov/prime-reportstream @.>
Cc: Young, Tanea (CDC/DDPHSS/OD/HITSSU) (CTR) @.>; Mention @.>
Subject: Re: [CDCgov/prime-reportstream] VT HL7 message failures (Issue #7922)
@TaneaYhttps://github.com/TaneaY If the state is NA how is that data being routed to VT? is it based on some other state?
—
Reply to this email directly, view it on GitHubhttps://github.com/CDCgov/prime-reportstream/issues/7922#issuecomment-1408957202, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZGEOOXS7SRDKNKTOSDCA5DWU7VFJANCNFSM6AAAAAATXHBRHQ.
You are receiving this because you were mentioned.Message ID: @.***>

@TaneaY I believe Vermont stated that they wanted to just leave that state field blank. But not sure if that's a required field for SimpleReport?

Hi Tanea,
ReportStream can filter out states with "NA", the question is if VT wants to receive international patient test results. We may need to find out if they do or do not.

Hi Sharon,
I see, apologies for the confusion. I have emailed VT to confirm if they would like to receive the international test results going forward.
Thank you,
Tanea
The SimpleReport Support Team
Contact us at @.***
Support hours:  8:00 am through 9:00 pm Eastern time
Monday-Friday, excluding US public holidays

From: sliu1000 @.>
Sent: Monday, January 30, 2023 2:24 PM
To: CDCgov/prime-reportstream @.>
Cc: Young, Tanea (CDC/DDPHSS/OD/HITSSU) (CTR) @.>; Mention @.>
Subject: Re: [CDCgov/prime-reportstream] VT HL7 message failures (Issue #7922)
Hi Tanea,
ReportStream can filter out states with "NA", the question is if VT wants to receive international patient test results. We may need to find out if they do or do not.
—
Reply to this email directly, view it on GitHubhttps://github.com/CDCgov/prime-reportstream/issues/7922#issuecomment-1409210258, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZGEOOXPFCZJXI63KUMQUC3WVAINTANCNFSM6AAAAAATXHBRHQ.
You are receiving this because you were mentioned.Message ID: @.***>

@TaneaY any update from VT?

No reply to the 1/30 follow-up to confirm if they want to filter the results from patients with addresses outside of the USA. Request for information resent 2/9.

From: LaFreda1 @.>
Sent: Thursday, February 9, 2023 1:14 PM
To: CDCgov/prime-reportstream @.>
Cc: Young, Tanea (CDC/DDPHSS/OD/HITSSU) (CTR) @.>; Mention @.>
Subject: Re: [CDCgov/prime-reportstream] VT HL7 message failures (Issue #7922)
@TaneaYhttps://github.com/TaneaY any update from VT?
—
Reply to this email directly, view it on GitHubhttps://github.com/CDCgov/prime-reportstream/issues/7922#issuecomment-1424620681, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZGEOOWGCHLTUPZ2MOQ4RQLWWUXZ7ANCNFSM6AAAAAATXHBRHQ.
You are receiving this because you were mentioned.Message ID: @.***>

Update from Sender:
Thank you for your assistance with this. Below is what I believe we would like our filter criteria to be, can you let me know if that is something that could be done?
Filter out OTC antigen covid results, excluding employee testing.
Thanks,
Andrew Gross, MPH | Health Data Administrator
Division of Health Statistics & Informatics
Vermont Department of Health
108 Cherry St, Burlington, VT 05402

update from user
Hi Juan,
Thank you for that info! I had recently inquired with ReportStream about filtering out at-home test results, as VDH no longer requires those results – I wonder if that filter has been implemented (though that hasn’t been confirmed with me)? If so, that might be the reason for the error?
Thanks,

@brick-green any updates on the filter? Has it been implemented?

linked to ticket # 7677

@LaFreda1 We can filter out Antigen results. But we do not have a way to distinguish employee testing. So we can't create the filter how VT is asking. We need to ask VT if they want to filter out all antigen results if there is another approach for filtering.

Follow-up to user sent.
Hello Andrew,
We received an update on your filter request. We can filter out Antigen results, but we do not have a way to distinguish employee testing.
Please advise if you want to filter out all antigen results or if there is another approach you would like to try.
Thank you,
Tanea


Fix #367 - Resize only works when you've first moved the divider

We never send a layout event to the iframe api when we do a resize.  This fixes it.

Perfect, I can implement the resize fix on thimble-side once merged.
r+

It should just work on the Thimble side, if you're listening for layout info.

It's not listening for that on resize - yet. But I have all the code needed and I can make a quick branch & pr.


Request to retag TKG for Oct 2024 release

https://github.com/adoptium/aqa-tests/pull/5524 is delivered into https://github.com/adoptium/aqa-tests/tree/v1.0.4-release. However, it has a dependent TKG change https://github.com/adoptium/TKG/pull/591. And this change is not in https://github.com/adoptium/TKG/releases/tag/v1.0.4.
For the Oct 2024 release, we request that TKG be tagged again. Assume it should be v<IP_ADDRESS>
@smlambert are you ok with it?
FYI @jasonkatonica @JasonFengJ9

Yes, v<IP_ADDRESS> is how this will need to be handled and then an update to the testenv.properties file in the v1.0.4-release branch of aqa-tests.  Will you take care of it @llxia ?

testenv.properties update: https://github.com/adoptium/aqa-tests/pull/5594

The change is delivered. This issue can be closed.


support for YouTube 4K Live stream?

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.12.01. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[X] I've verified and I assure that I'm running youtube-dl 2016.12.01

Before submitting an issue make sure you have:

[X] At least skimmed through README and most notably FAQ and BUGS sections
[X] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[X] Question
[ ] Other

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
E:\tools\tools>youtube-dl -v -F G0rBvROOLcs
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['-v', '-F', 'G0rBvROOLcs']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2016.12.01
[debug] Python version 3.4.4 - Windows-8.1-6.3.9600
[debug] exe versions: ffmpeg N-78268-g0ab25da, ffprobe N-78268-g0ab25da, rtmpdump 2.4
[debug] Proxy map: {}
[youtube] G0rBvROOLcs: Downloading webpage
[youtube] G0rBvROOLcs: Downloading video info webpage
[youtube] G0rBvROOLcs: Extracting video information
[youtube] G0rBvROOLcs: Downloading formats manifest
[youtube] G0rBvROOLcs: Downloading MPD manifest
[info] Available formats for G0rBvROOLcs:
format code  extension  resolution note
91           mp4        144p       HLS , h264, aac  @ 48k
92           mp4        240p       HLS , h264, aac  @ 48k
93           mp4        360p       HLS , h264, aac  @128k
94           mp4        480p       HLS , h264, aac  @128k
95           mp4        720p       HLS , h264, aac  @256k
96           mp4        1080p      HLS , h264, aac  @256k (best)
...
<end of log>

Single video: https://www.youtube.com/watch?v=G0rBvROOLcs

Description of your question, suggested solution and other information
YouTube added 4K as an option for live streaming. This DASH live stream is not recognized by youtube-dl > only the HLS live streams are displayed; Is it possible to record the 4K live stream?
The sample video is a continuous 4K live stream example.
Recording Youtube 4K videos works flawless, but live streams not yet.
un saludo, beatsmaster

Duplicate of #10787.


Use an optimized text search algorithm to find boost test keywords in source code

Leftover of #21:
Wouldn't it be better to use an optimized text search algorithm (e.g see discussion here http://programmers.stackexchange.com/questions/183725/which-string-search-algorithm-is-actually-the-fastest) instead of using normal regular expressions or string search?

We did some internal tests and implemented some of the mentioned algorithms in C#. Our benchmarks show that the String.Contains method is still faster than the custom algorithms or regular expressions for string searching.
Given the recent requests (#24), source code parsing should be made redundant for Boost Test 3 projects which should minimise the priority for this feature.

Ok we close this


Remove Contract Address QR code function

I found that the token address of a token can be found in the "My Wallet Address" screen by clicking on the Ethereum logo on the top right.
Making it possible to show a QR code of the contract address is a bad idea because then someone could scan and send tokens to the contract, instead of the intended recipient. The Ethereum logo could be accidentally pressed. Such tokens can then end up being stuck in there forever as usually token contracts aren't programmed with a custom function for withdrawing tokens.
Usually there's no reason to be sending tokens into a token contract.

Yep ok. This is actually in here for development purposes. Now that we can access it from the token info itself this can be removed.

There's currently no way to access that option, it's been deprecated, but that code should be removed too.


Research coefficient for networking of data leaving a data center

Context
Overview
Currently we take into account networking when calculating our carbon emissions. So far, we consider only traffic between data centers.
We would like to extend this to also include external traffic. To include this, we will need an appropriate coefficient to apply when converting usage to energy. This ticket handles the research involved in deciding on a coefficient.
Out of Scope:
Related issues/Dependencies:
Issue 307
Acceptance Criteria

[ ] There is a document with sources in the google drive [tbd where]
[ ] A coefficient has been chosen for external networking traffic
[ ] Rationale for number chosen is documented
[ ] Reach out to community members for additional research?

Tech Tasks

[ ] Run Changesets, bump any packages that have been updated/changed
[ ] Did you make changes to the client, api or cli package? If so, considering updating the create-app templates.

Tech Notes
Review Tasks

[ ] eg. specific QA details, update methodology, or update microsite

Hi,
Here are some suggestion coming from the literature for those coefficients :

Study on the carbon footprint of 1GB transferred on the RENATER network, in France, Marion Fischer, Françoise Berthoud and Al, 2021==> suitable for Intra-Region traffic

low traffic days on this network result in an energetic intensity of : 0.004 to 0.007 kWh/GB ==> suitable for Intra-Region
high traffic days result in an energetic intensity of : 0.002 to 0.004 kWh/GB ==> suitable for Intra-Region

Carbon Trust report, from Malmodin, Koomey and Masanet, 2021

1GB on the network of a network operator : between 0.15 and 0.075 in 2020 (kWh/GB?)
0.0065kWh/GB for core network only ==> suitable for Intra-Region (under-estimated according to impact factors data gurus I've discussed with)

Investigating the Inconsistencies among Energy and Energy Intensity Estimates of the Internet

0.02kWh/GB for core network ==> suitable for Intra-Region but higher than other coefficients so might suit Inter-Region
0.07kWh/GB for operator to customer network (including CPE) ==> suitable for Internet Traffic

The Carbon Trust report also introduces the power model which may allow to not compute energy consumed by network traffic only linearily and may be closer to the reality, but I'm not sure it could be used in this context (didn't take the time to see what would be missing).


[Task]: PoC: consolidate APIs for first page load time optimization

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks
No response

Results are documented here:
ref1
PR for PoC: https://github.com/appsmithorg/appsmith/pull/29578


integrate select, input, textarea with form wrapper

In GitLab by @01oseluiz on Feb 8, 2022, 11:11

unassigned @01oseluiz


GUIs are blank on Prism Launcher / Steam Deck in Game Mode

The "optional mods" and other UIs are completely blank in the steam deck's game mode under Prism Launcher.

Duplicate of https://github.com/packwiz/packwiz-installer/issues/33


Loan reminder emailer: [Was: Collection Manager Loan Manager Time Saving Task]

As a collection manager:
I want to track what loans are due, but do as little work as possible to remind people of their loans.
Once I enter the dates "Requested", "Sent", "Received", "Return Expected"; and contacts have email addresses, then I want TaxonWorks to create a list of Overdue loans. Then, I want to have TaxonWorks send reminders automatically, copying the collection manager, creating the emails from the content in each loan (e.g.:
{Hello from [collection manager],
Our records indicate that [Loan identifier] is now due. This loan contains [Loan Items]. Please contact [collection manager] to extend your loan, or return specimens to [address] as soon as possible.
Sincerely,
[Collection Manager]}

This might be two issues: one: CM task that deals with loans. two: email reminders for overdue loans.

This alread exists: tasks/loans/overdue/index


bugfix: numFmtHash's wrong hash-key makes too many  tags for …

…the same format in styles.xml

Too many number formats seems to makes the excel file unreadable.
https://support.microsoft.com/en-us/kb/213904

I was having the same problem. This fix worked great.
FYI if it helps here was the specific error I was getting when validating sheets with too much style:
Location of error: { 0}/x:worksheet[1]/x:sheetData[1]/x:row[4431]/x:c[11] Error description: The attribute 's' has invalid value '66473'. The MaxInclusive constraint failed. The value must be less than or equal to 65490.
So it looks like the max for xlsx is about 65490.

This is fantastic, thanks!

I think this fix is already part of master, @Youngbae-Jeon - can you confirm?

I have tested with the last commit on Aug 16, 2016 and found there are no more problems like this.
So I'm closing this pull request. Thank you.


environment problem

When I install the environment, I found a problem.
Gaussctrl relies on lang-sam, and lang-sam(text) relies on a specific version of sam-2. And then sam-2 upgrades nowadays. So we should install python=3.10 instead python=3.8 to comply sam-2. If we still using python=3.8, the installation will be incompatible.

And can you update the installation instructions? There are some small errors in there. Thank you for your great work!
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
nerfstudio 1.0.0 requires gsplat==<IP_ADDRESS>, but you have gsplat 0.1.3 which is incompatible.

Hi there, what is the error message?


Pasting citadels to structures module results in some results being deleted

https://i.imgur.com/Um81v9c.gif

Confirmed that this bug does not exist in Pathfinder v2.0

Tracked down the issue. Structures were being saved correctly into the 'structure' table, however the associated 'corporation_structure' record that is used to build the systemData was being overwritten on each iteration when looping over structures in the pasted data, resulting in only the last structure on the list being properly persisted to the DB.
I have solved by simply resetting the CorporationStructureModel instance when saving corporation structures (f343753f). I'm not sure if this is a good fix or a hacky one, but I know very little PHP, so unless anybody has a better solution I will include in the next release.


It breaks a fresh ember installation

Steps to reproduce:
ember new my-app
cd my-app
ember install ember-simple-auth
ember install ember-simple-auth-auth0
ember s

Navigate to localhost:4200, you will see the following error in the console:
vendor.js:62487 Uncaught SyntaxError: Unexpected identifier
app.js:1 Uncaught ReferenceError: define is not defined
    at app.js:1

vendor.js:62487:
	import Authentication from './authentication';

more lines from vendor.js:
/* 0 */
/***/ (function(module, exports, __webpack_require__) {

	module.exports = __webpack_require__(1);

/***/ }),
/* 1 */
/***/ (function(module, exports) {

	import Authentication from './authentication';
	import Management from './management';
	import WebAuth from './web-auth';
	import version from './version';

	export { Authentication, Management, WebAuth, version };

	export default {
	  Authentication: Authentication,
	  Management: Management,
	  WebAuth: WebAuth,
	  version: version
	};

/***/ })
/******/ ])
});

I've been using this library successfully in older ember projects, but now it breaks the new ember app. Tried on both ember v2.18.2 and v3.x.x

Update:
Added the following in "resolutions" in package.json
    "ember-simple-auth-auth0/auth0-lock": "11.0.1"
```

With this specific version of auth0-lock my app works.

This is not working for me on my brand new project running ember 3.3.0.
This is what i get when i try the "resolutions" approach.
warning Resolution field<EMAIL_ADDRESS>is incompatible with requested version<EMAIL_ADDRESS>I'm still getting
vendor.js:62503 Uncaught SyntaxError: Unexpected identifier
app.js:1 Uncaught ReferenceError: define is not defined
    at app.js:1

Heh. "define is not defined." That's the goofiest error message I've seen in a while. :P
Anyhow, it looks like something in webpack is goofing up on newer versions of auth0.js/lock. I'm not 100% sure what it is, but fortunately we just switched away from webpack in favor of ember-auto-import for pulling in the Auth0 dependencies, so I think this is already fixed on the develop branch.
I created a couple of test projects to verify:

Made a new app, installed ember-simple-auth and ember-simple-auth-auth0; it broke, just as described.
Made a 2nd new app, installed ember-simple-auth and https://github.com/auth0-community/ember-simple-auth-auth0.git#develop, and it works fine. Whew!

Just need to cut a new release with the fix, I suppose.

@XaserAcheron I can confirm that with develop branch it also works for me on a fresh installation.

Finally got 'round to releasing v4.1.0, so this should all be good now. Whew!


Unable to enable Windows Susbsystem Linux in the Enable Features dialog or through PS command

Hi
I am trying to install Microsoft Windows Subsystem Linux on Windows 10 Home (ver 10.0.16299.15)
For That I am trying to enable optional feature through "Programs and Features" dialog or running PS command
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
I am getting the following error message
Enable-WindowsOptionalFeature : One or several parent features are disabled so current feature can not be enabled.
At line:1 char:1
+ Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows- ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException
    + FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand

Also when I look at the feature list after the restart  in the Programs and Features, it is still disabled.
What might be a problem?
Thanks
Darius

Could people encountering this issue ensure that the trustedinstaller service is set to autostart?
SC config trustedinstaller start= auto

For me this was also caused by a different problem where a fresh Windows install wouldn't install the latest cumulative updates, getting in an infinite loop of requiring a restart for updates that wouldn't go through. The fix was reinstalling Windows.

Running PowerSheel "as Administrator" solved the problem for me

getting in an infinite loop of requiring a restart for updates that wouldn't go through

I hit that too in early January and a total wipe ended up being the only path to salvation, despite my considerable best efforts to solve it otherwise.

Running PowerShell "as Administrator" solved the problem for me

@dariuspranskus  can you confirm you were running an elevated Powershell? That was kind of taken as a given in this thread. I think you probably were, because I'd expect a different mode of failure if you weren't. But "solved the problem for me" (emphasis on definite article mine) loose end above needs tidying up. Running elevated will definitely solve a problem, but not necessarily your problem.

Hi
I had the same issue (the One or several parent features are disabled so current feature can not be enabled. one).
In my case it was that the Trusted Installer service wasn't up. I started it and set it to run automatically and than wait a cople of minutes and try again to activate the feature and then it works.
Hope it helps other people.

Same problem
PS C:\Windows\system32> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
Enable-WindowsOptionalFeature : One or several parent features are disabled so current feature can not be enabled.
At line:1 char:1

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows- ...

  + CategoryInfo          : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException
  + FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand

I turned the TrustedInstaller to Auto and restarted and everything. Just don't understand what does it want me to do!
If I try to turn on WSL via GUI it say finished doing requested changes and restarts. But when I check it again after restart, the box is unchecked!
Please help

Same problem, same error COMException.
OS: Windows 10 x64
Build: 16299

Same issue here, brand new machine.
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.16299 N/A Build 16299

Same issue again, I'm led to believe it's a problem with version 1709. Restarts do nothing, no system changes are saved, no updates going through. Any solutions? I've tried everything but the media creation tool, trying to avoid a fresh install.

Same issue here

The same issue with Windows 10 Home (1709) - 64

After applying the April update for Windows 10: https://support.microsoft.com/en-us/help/4093112 this issue was resolved for me.

The same issue. I tried installing the update recommended by stensson, but ended up in the "infinite loop of requiring a restart for updates" as described by Morthy

@tanjakantola Have you also tried starting Windows in recovery mode and choosing to repair the installation? I believe that fixed my infitite loop issue, together with 4093112. Can't remember all details on which sequence i did this though.

@Groumy , the trusted installer service set to up fixed the thing.
When typing "Enable-WindowsOptionalFeature -Online -FeatureName TelnetClient" (or whatever feature) I was having "Enable-WindowsOptionalFeature: Impossible de lire la clé du Registre de configuration" (Enable-WindowsOptionalFeature : Impossible to read Configuration regitry key).
Turning on and automatic start the "Programme d'instalaltion pour les module Windows" service which I think correspond in english to the Trusted installer has solved the problem.
@Groumy : you saved me...

@therealkenc Sorry for coming in so late to this, is "Running an elevated Powershell" different than running PS on an administrator account? Thanks!

I had the same problem as everyone else. My solution was disabling firewall / antivirus software before installing WSL from the PowerShell. The logs of the security software showed it was preventing a registry update from being completed at around the same time as running the install.

Giving @arnaudoisel kudos for February answer. My problem, too, was solved simply by running PowerShell as Administrator.

I am still running into this problem. I'm running PS as Administrator, and according to the graphical Windows feature installer, WSL is active. However, upon trying to start Ubuntu, I'm running into the familiar error message. I'm also positive I'm running a 64-bit Windows.

I'm assuming this is a different problem, but with similar symptoms. Can anyone help?

I also have the exact problem as @wvdschel commented. In addition, if I try to enable the windows feature 'Windows Subsystem for Linux' it shows the error code 0x70083701. I tried to resolve it using the Microsoft support threads. But they are of no help.

Same problem.

+1

Running power shell as admin solved the problem for me as well. Thank you!


Create common helper method to find best matching dns zone.

Based on bugfixed code from Route53, thanks to @rvdginste (see https://github.com/win-acme/win-acme/pull/1525), but the same problem was in most other DNS plugins. Which meant it was high time to create a common helper which will always have the latest logic.
Would appreciate testing/verification for the various plugins.
@rvdginste
@georg-jung (this one I'm most curious about, as the Cloudflare implementation didn't handle multiple result pages yet and only seemed to work for top-level domains, so the rewrite was a bit more drastic)
@albertofustinoni
@vidarw
@inkahootz

Actually I'm rather sure that the plugin did handle all this (100s of pages at CF + arbitrary deep subdomains) and I'm not sure if the new version doesn't make things worse:

Cloudflare has sites/zones. They are always .tld. If you have x.y.com, that might be a DNS record that is part of the zone y.com, but it is not a zone on it's own.
To get the relevant CF zone for the domain in question I took just the y.com part of every domain. If you gave a.b.c.d.e.y.com I'd have asked the CF api for y.com - that's the only way this works after all.
You're right, it didn't use paging. Because it asked the API directly for results filtered by the relevant name. Thus, the API would only ever return one or zero results.
The new version just does all the filtering that was handled by the CF API before on the client side. Either I don't understand it correctly (more read over it than in too great detail, don't have too much time currently) or the result is comparable but just requiring more wire transfers and http requests.

I’d be interested in how one can even register a sub domain as its own zone in Cloudflare: as far as I know they don’t allow you to do that.

So, in CF-sense, that best (and only) matching dns zone is always the top level DNS zone.

I’d be interested in how one can even register a sub domain as its own zone in Cloudflare: as far as I know they don’t allow you to do that

So in that sense Cloudflare is different from other mayor DNS providers that allow creation of zones for specific subdomains. Seems like a weird limitation because it prevents customers from dipping their toes in the water with some subsite(s) before fully committing, but as long as it remains like that this code change is not necessary so I will revert for the sake of stability. Thanks for the feedback!


Invalid/Erratic Transactions get committed to the BlockChain

Currently invalid or wrong invoke transactions get committed the blockchain.

Invalid transactions: tx referencing not deployed chaincode, calling chaincode without the correct credentials, calling a non-existent chaincode function...

Erratic transactions: tx that can't be executed because of any random execution error or because it can't be performed with current values of world state variables (for example if money transactions are asked but account has insufficient balance).

In the current BlockChain design, all this "bad" transactions are still committed to the BC (although they obviously don't modify the world state variables).
This raises several problems because ultimately, the client won't know if his transaction has been executed. For example: a user does a transaction of 5€ but he only has 3€ in his account. How can this user know that the transaction was wrong if it was committed anyway and the user can check that it is registered in the BC?
Here are two suggestions of what could be done (it should be thought thoroughly as it is a premature idea):

When executing transactions (that have been previously ordered) each node does not commit those transactions that are invalid or return an error of execution. This would work if it is assumed that execution output is the same in all nodes (assumption that current BlockChain implementation assumes)

Use Sieve consensus algorithm, which agrees on the output of transaction execution, if the transaction's execution output is an error or invalid discard transaction as it would be done if outputs do not match (I think this solution can be more easily implemented).

My first (rhetorical) question is: Why do you say that bad transactions don't modify the state variables? Where is this documented/specified? If a transaction does writes to the state and then exits with an error there is no specification of what happens or is supposed to happen. (Note, I'm griping about the lack of good specifications, not about your issue.)
I do disagree with one of your points, however. I would argue that any transaction that is accepted asynchronously (as they all are currently) must be registered in the Blockchain. If the INVOKE interface has given the client a UUID, then the client must be able to unequivocally determine that the transaction UUID has been executed or will never be executed, even if the execution resulted in a failure. Simply omitting the UUID if it fails creates more problems than it solves in my view, since this prohibits the client from getting absolute "closure" on the state of its transactions. If HyperLedger included an interface that would block until the final disposition of the transaction (error or committed) was known then it would be OK to drop, I think.

My understanding that if a validator node's chaincode returns an error on a transaction. The transaction will not being in the blockchain.

@bcbrock I agree with what you "asked". It is true that if it is decided that wrong transactions need to be removed then it must be ensured that the transaction hasn't modified any state variable. It is a crucial observation.
I also agree that if the client doesn't know what happens with his/her transaction he/she might think that something went wrong (e.g. network down) instead of being sure that the transaction was wrong (e.g. balance insufficient). In any case, the client currently doesn't have any way of knowing if his/her transaction was wrong as the client will always see the transaction committed.
In my opinion transactions should be discarded before assigning them a total order through consensus (2nd of my suggested solutions).

@bcbrock @mcr222 I would be more comfortable if all incoming transactions were logged in the blockchain for audit purposes. Good or bad, anything that is attempted is a transaction and worthy of knowing about. I am of course presuming that defence against various attacks such as (D)DOS is handled outside the fabric.

How would then any service on top of the blockchain know if their request (invoke transaction) was executed correctly? Many things can go wrong (reference a non-existent deploy tx, sending incorrect function parameters, parameters that the chaincode rejects...) and the transaction would still be registered as any other correct transaction.

@bcbrock: you're making two requirements -- want to clarify, b/c
they're different, and one of them -might- or might not be good to
have.
(1) [clearly necessary] When a client submits a tran to a peer, it
should also be able to (by default YES, can't imagine NO) create a
local subscription in the peer, for thay tran-id.  Eventually (barring
certain problems, read below) that tran comes thru in the log via
consensus, and is either successfully applied, or aborted.  At that
point, the local peer delivers a notifcation of this, to that
subscribed client.
The creation of such a subscription by a client must be possible
independently of the submission of a tran, so that a client can
subscribe to the result of a tran it has yet to submit, at many
peers. This would be used to implement "strong reads".
This is uncontroversial.
The only snag in the above, is that the network might "lose track of"
a tran, and it never comes thru in the log.  This is a distributed
system -- such things happen.  We can look into all the edge cases
where it might happen, but I'm a little dour that we can find all of
them.
A non-snag: if the client crashes (or the peer crashes) that
subscription will be gone, and this is an expected thing -- if your
connection to DB2 crashes, you can't find out whether that tran on
which you just typed "COMMIT" actually committed.
(2) [somewhat controversial] If we keep all trans (both committed and
aborted) in the blockchain, it could be quite large.  Also, does this
mean that even trans that fail basic (local) consistency checks should
be stored ("everywhere") in the blockchain?
Could be significant storage.  That said, the -implementation- of this
is uncontroversial.

@mcr222 - I think the simple answer to one of your concerns is to include a status field in the transaction records in the Blockchain that indicates whether the transaction succeeded or failed, or more specifically how it succeeded or failed.
@chetmurthy - I agree that haviing success/failure status come back in an event stream seems like an appealing idea. This notification is ephemeral however - if you blink you can miss it. If this is the only notification for failed transactions it would require the client applications to probably be even more robust that the server, which seems upside-down to me.
I don't think the idea of failed transactions taking up too much space would really be an issue in a permissioned blockchain. Clients are not going to be simply "trying stuff to see what works".  The peers can probably also do more to filter out obviously bogus transactions, like those that refer to non-existent chain codes, before returning a transaction ID (i.e., before officially accepting the transaction).
Or, let's say there is a rogue client. What is the the difference between the client sending 1,000,000 transactions that "work", are recorded in the chain but don't actually change the world state, vs. sending 1,000,000 that outright "fail"?

@bcbrock SGTM  I just wanted to be sure the question of size of data was considered-and-dismissed.  Assumed it'd go this way, and I sure support.

@bcbrock I agree that a status field would solve the issue of not knowing what happened with your transaction.

Related to PR #1719

@srderson #1719 was merged, can we close this?


Add weak cache to keep references to retained objects

The map table ensures the cache has a reference to an object still in memory, even if it has been evicted from the dictionary.

@jparise Sorry for the changes this morning, I had intended to open the PR against our branch so my colleagues could check through.  Clearly I missed a dropdown.  Updates have been made.
If you would like to reach out to me, I can be found using my first name @ the company I work for.

The date stuff looks great. I would accept that immediately as a solo PR.
The weak map bits look useful too, but I think we might want to include some unit test coverage for that new behavior.

There is also the issue of behavior on -removeAllObjects
I have not removed objects from the weak cache for this, since it is called for the app entering background and also memory warning.  Since the objects referenced by the weak cache are retained elsewhere, this won't removing them won't save memory.
A similar issue exists for -removeObjectAndExecuteBlocksForKey:.
The primary issue is that both these methods are exposed, so potentially there could be some confusion about expected behavior.

@garrettmoon is probably the best person to offer guidance on those issues.

Fixed failing unit tests. Primary issue came from objects remaining in the (new weak) cache when they were not deallocated, which is the desired behavior.  Added (admittedly only one) test coverage for weak cache.
Very happy to take other feedback/questions.

@jparise If you would like me to remove the NSDate change from this PR and submit it separately, please let me know.

@lukescholefield Yes, if you have a moment to do that, we can get that part merged straight away.

@lukescholefield Yes, if you have a moment to do that, we can get that part merged straight away.

Removed commit related to NSDate changes, which is now in a separate PR.  Rebased to latest version of master.  Sorry for the forced pushes, but I am trying to keep this in a conflict free state (and keep a tidy commit history).

This is an improvement I've been wanting to make! Thank you for taking the time to improve the project!
One thing that has been stopping me is how we can make this behavior optional (precisely because people will expect removeAllObjects to actually remove all objects). I feel like it's probably the correct default behavior, however, I'm concerned about making it such without a point release.
Can you think of a way to make this optional behavior? One way would be to not init the weakMap unless the cache were configured to use it? Then when we decide to roll out PINCache 3 we can init it by default?

I had a few options:

Make weak cache optional/configurable as you suggest.
Implement either force remove methods for flushing the weak cache too or add a parameter to the existing remove methods that controls if the weak cache is cleared (and provide convenience remove methods consistent with the current API).
Implement the weak cache and document the behavior (which is what I have done here, minus the documentation).
Modifying -setObject:forKey:withCost: to clear remove cached object when object == nil to provide a way for the user to flush individual objects out of the cache.

As I mentioned before (and you no doubt know), failing to remove the object from the weak cache doesn't really cost memory (aside from the references), so the only downside to the object sticking around is if the user wants to flush it for a specific reason. In this case I would rather push the burden onto the user not to check the cache, but that is a personal opinion, and would at least require documentation.
So I would still lean towards 3, as it results in the simplest API, but you are entirely valid with your concerns about including it in a point release. Implementing 4 would possibly be useful too.
The other option I had was to introduce it as an entirely entirely new layer of cache in addition to PINDiskCache and PINMemoryCache. If this is preferred it can easily be done, but I felt this change was more concise and logically consistent (since after all, it is just an additional type of memory cache).

Err, when I said NSHashTable's weakObjectsHashTable method I actually meant NSMapTable's strongToWeakObjectsMapTable.

I'll update the prior comments to be accurate.

@timonus Updated with check in 524440c
This should now be fine back to iOS 5.

@lukescholefield I think we should at the very least remove objects from the map table when removeObject is called from the API.

Hey @lukescholefield I know you're busy, so no pressure on this, but I'm going to close this until you're ready to update. Ping me when you are and I'll re-open.