Consistently getting "Specify which project file to use..."

After installing and attempting to run,  I'm consistently getting...
"Specify which project file to use because this 'D:\ATLASSVN\Common\source\Utilities\Utilities' contains more than one project file."
My command line is: dotnet migrate-2019 wizard "Utilities.csproj"
The directory actually only contains one .csproj file.   I've attached my .csproj file and a screenshot of my command window.
If there anything I'm obviously doing wrong?
Utilities.csproj.zip

Your directory is called Utilities.csproj? I would need to test but why
does your folder have an extension :)
Not saying we shouldn't fix that but it seems weird
On Wed, Sep 18, 2019, 16:27 threadz<EMAIL_ADDRESS>wrote:

After installing and attempting to run, I'm consistently getting...
"Specify which project file to use because this
'D:\ATLASSVN\Common\source\Utilities\Utilities' contains more than one
project file."
My command line is: dotnet migrate-2019 wizard "Utilities.csproj"
The directory actually only contains one .csproj file. I've attached my
.csproj file and a screenshot of my command window.
If there anything I'm obviously doing wrong?
Utilities.csproj.zip
https://github.com/hvanbakel/CsprojToVs2017/files/3628713/Utilities.csproj.zip
[image: 2019-09-19 11_12_24-Common- Microsoft Visual Studio
(Administrator)]
https://user-images.githubusercontent.com/5687119/65193459-54f5ef80-dacf-11e9-8d3c-6dffd1bd709b.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hvanbakel/CsprojToVs2017/issues/265?email_source=notifications&email_token=AA7QKPDLBPFRDZCRBK2TUXTQKK2PJA5CNFSM4IYEWUNKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HMIXPMQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA7QKPHXB4ZOZ2VI3FX6S5TQKK2PJANCNFSM4IYEWUNA
.

No. Project file in the Utilities directory is called Utilities.csproj.  I was referencing the project file directly from the command line.
It's a .NET Framework 4 class library.
Seemed a weird error message to me too.

@threadz It's strange, to the point of being weird.

There is currently no such string in this project. It's not the message of dotnet-migrate-2019.

Even if there were, the wizard should list all ambiguous variants (in case there are less than 5).

What is your version of project2015to2017.migrate2019.tool (dotnet tool list -g)?

Try turning on extreme log verbosity. dotnet migrate-2019 -v diag wizard "Utilities.csproj"

Try specifying ".\Utilities.csproj" or full path. Try not specifying anything, it should pick that file, since it's the only project/solution file in the current working directory.

Wow, that is odd then.  Here's the screenshot from the CMD window with your suggestions...

Apparently this error is also run when running dotnet ef
https://github.com/aspnet/EntityFrameworkCore/issues/11315


Please define outside collaborators in code

Hi there
We have a process to manage github collaborators in code: https://github.com/ministryofjustice/github-collaborators
Please follow the procedure described there to grant @ibrechin access to this repository.
If you have any questions, please post in #ask-operations-engineering on Slack.
If the outside collaborator is not needed, close this issue, they have already been removed from this repository.

@NickWalt01 he's already listed there:
https://github.com/ministryofjustice/github-collaborators/blob/main/terraform/bankline-direct-parser.tf
as it's not expired yet, is there anything you still want me to do?

Automation error: adding user back in manually


CUDA ZFP produces 0 for arrays beyond a size

We have this weird issue wherein if we compress and decompress an array bigger that 512^3, the resulting decompressed data is part filled with complete zeros (0.0e+0). In one of the machine where we ran, it exactly produces this behavior from 513^3 (float) onwards array, whereas on another machine, it starts breaking somewhere beyond 512^3 but not exactly at 513^3. For reproducibility sake, I compressed and uncompressed a float array of size 768 x 768 x 768 (also reproducible with 1024 x 1024 x 1024). I filled the array with exponential function as in examples/simple.c and also with a cosine wave function, source being at z = 0. The behavior of decompressed data containing zeros is exactly the same. I have attached the snapshot at the mid (x - z, y normal) plane for serial as well as cuda run for you to look at how the zeros show up in the case of CUDA_ZFP. In the case of cosine wave, I have highlighted the points on the slice where value == 0. with magenta color, since the neighboring points are of very small value compared to the wave source, making the visibility difficult.

You can reproduce the same result and behavior with the help of this gist which contains the high level C APIs as prescribed in the examples/simple.c: https://gist.github.com/data-panda/1f164852fbdadc7364f5cdf8a82ab065.
Compile: icc -O3 -fopenmp simple_0bug_reproducer.c -lm -lzfp
Tested this with zfp release 0.5.5 and current branch develop. In both the cases, I reproduce the same behavior.
I am not sure if the ISSUE https://github.com/LLNL/zfp/issues/105 and this has the same root cause but I am far from the 4GB limit. The uncompressed file size when written to disk is ~1.8GB.
Am I missing something here?

I can reproduce this issue using CUDA 10.1 and both icc 19.0 and gcc 4.9.  This issue probably is not related to #105 for 768^3 grids, but possibly for 1024^3 since 1024^3 * sizeof(float) = 4 GB.  Portions of the code that use signed ints would be limited to 2 GB.
We are aware that the CUDA implementation is not as robust for very large data sets and will be looking at weeding out bugs over the coming weeks.
In the meantime, the only quick fix I can suggest is to break the array into smaller pieces (whose dimensions are multiples of 4) and to compress them separately.  One way to achieve this without explicitly having to reorganize the data is to use zfp's striding mechanism.

Thanks @lindstro. If I move from 768 to 1024, the band of zeros increase (?). it seems like anything beyond a certain data size is being decompressed as zeros (or compressed as zeros). In the case of 1024, if everything is zero then i suspect I am seeing the same behavior as mentioned in #105 . Will update!

I cannot think of a good reason why we're seeing this behavior.  It's also unclear whether the issue is in the compressor or decompressor (or both), e.g., does the compressed output match what the serial implementation outputs?
It is somewhat telling that this appears to occur only along one axis (the z-axis, AFAICT, which should be the most slowly various one).  This suggests that the compressed stream is somehow being truncated.  What if you halve the rate to 4 bits/value?  I can investigate this further myself when I have more time, but it won't be until later this week.

Something else that occurred to me: zfp does not only need to address array elements (via indices) and bytes (via pointers), but also bits (via bit offsets into the compressed stream).  The largest 32-bit signed bit offset is 2^31 - 1.  For a data set of size 768^3 at a rate of 8 bits/value, you can address only (2^31 - 1) / 768^2 * 8 ~ 455 out of 768 slices, which judging by your visualizations appears to agree closely with where the data is cut off.  The bit offset should be a 64-bit unsigned quantity, but I've seen places in the CUDA code where 32-bit ints are (incorrectly) used.
This gives a plausible explanation for the behavior you're observing, and I'm guessing the problem will go away if you change the rate to 4 bits/value for the 768^3 data set.  I'll see if I can confirm this and will keep you posted.

I can confirm my suspicions.  First, using checksums I've verified that the compressed data matches between the serial and CUDA backends (for 768^3 arrays), so the issue is primarily with the decompressor, not compressor.  Also, decompression fails when the rate is above 2^31 / 768^3 ~ 4.74 (e.g., a rate of 4.5 works fine but 4.75 does not).
It appears this line is to blame.  Here (block_idx * maxbits) is the bit offset, which is computed as a 32-bit int.  Adding a cast makes your example work.  There's a similar missing cast in the BlockWriter that causes issues with larger arrays.
I've pushed a (temporary) fix to develop.  Please confirm that it addresses your issue.
Note that this addresses the bit offset issue only.  There are potentially other issues with addressing elements and/or bytes that might occur for larger arrays, though I confirmed that arrays up to 1200^3 now work.  As I said, we'll be looking at these issues over the coming weeks.

@lindstro i had already did the hashums on the compressed file and was sure the error was in decompression. Thanks for confirming the same. I will checkout he bugfix that you pushed to develop and confirm if it works for me.

works for (512 --> 1250]. Tried 1300^3 but hit the malloc limits on the system resulting in segfault. So I think this fix works.

Great for finding that one!

@data-panda Can I close this issue?


Dimensions of captured Bitmap are limited to a device screen size

Hello, I am using this test to screenshot test some composables
abstract class ScreenshotTest {

    @get:Rule
    val rule = ActivityScenarioForComposableRule(
        config = ComposableConfigItem(
            displaySize = NORMAL,
            orientation = PORTRAIT,
        )
    )

    protected fun snapshotComposable(
        name: String,
        composable: @Composable () -> Unit
    ) {
        rule.activityScenario
            .onActivity { activity ->
                activity.setContent {
                    composable()
               }
            }
        rule.activity
            .waitForComposeView()
            .captureToBitmap()
            .get()
            .writeToTestStorage(name)
    }
}

and I've noticed that if the rendered view is higher than the screen height it's cut. Is there any way to get a bitmap of the whole view regardless of the device size? I've tried to play with displaySize property of a ComposableConfigItem but it's only scaling the image not solving the issue. Is it even something your library can affect?
Thanks for the input :)

Ok so I rewrote my test like this, without using your library,
abstract class ScreenshotTest {

    @get:Rule
    val rule = createComposeRule()

    protected fun snapshotComposable(
        name: String,
        composable: @Composable () -> Unit
    ) {
        rule.setContent {
                composable()
        }
        rule.onAllNodes(isRoot())
            .onFirst()
            .captureToImage()
            .asAndroidBitmap()
            .writeToTestStorage(name)
    }
}

and it's still the same :(

Hi @davidbilik !
I'm afraid that is because you are using captureToBitmap() or captureToImage()
Those methods limit the bitmap to the window size i.e what is visible on the screen.
However, this library provides view.drawToBitmap(), which uses Canvas, which should allow you to take screenshots that outsize the screen window.
e.g.
abstract class ScreenshotTest {

    @get:Rule
    val rule = ActivityScenarioForComposableRule(
        config = ComposableConfigItem(
            orientation = PORTRAIT,
        )
    )

    protected fun snapshotComposable(
        name: String,
        composable: @Composable () -> Unit
    ) {
        rule.activityScenario
            .onActivity { activity ->
                activity.setContent {
                    composable()
               }
            }
        rule.activity
            .waitForComposeView()
            .drawToBitmap() // this is the key
            .writeToTestStorage(name)
    }
}

The only disadvantage of that method, is that elevation elements (like shadows) are not drawn.
Alternatively, you could use
@get:Rule
    val rule = ActivityScenarioForComposableRule(
       // make the composable smaller,
       // to see whether it fits in the window,
       // without sacrificing elevation
        config = ComposableConfigItem(
             displaySize = SMALL,
        )
    )

Warning: the library also provides view.drawToBitmapWithElevation(), but that uses PixelCopy, which limits the screenshot to the window size :(
let me know if that helped :)

Hey Sergio, thanks for you answer :) I've tried to rewrite my test to this
protected fun snapshotComposable(
        name: String,
        composable: @Composable () -> Unit
    ) {
        rule.activityScenario
            .onActivity { activity ->
                activity.setContent {
                      composable()
                }
            }
        rule.activity
            .waitForComposeView()
            .drawToBitmap()
            .writeToTestStorage(name)
    }

and it's still limited to a screen size 🤔 But maybe i did something wrong because you've said

However, this library provides view.drawToBitmap(), which uses Canvas

and I did not find this method in your library, I've used the one from core-ktx.

@davidbilik
Although it seems it is not related to this lib, could you share the problematic composable?
I could take a look at it and might find a solution to the problem

@davidbilik
I'll close this issue seems it does not seem to be related to this lib


[Discussion] Add Blog to Documentation

I think it would be useful to add a blog-like page to the docs with rxjs related blogs.
I see 2 possible solutions for this:

Like angular.io we could link to a medium account.
pro:
-  it is a well known blog platform with a lot of features like comments
- not that much work to setup
con:
- not that flexible for using code
- share account details
- I don't know if it is possible to add a review process before an article is published

We could add a new site to the docs, where we reference pages which could be inside the docs_app or across the internet.
pro:
- more or less easy to prepare
- kinda flexible with code and other stuff
- easy to find content to start with
- review could be done easily via github
cons:
- no(not easily) blog-like features like comments
- linked pages could be remove and therefore we reference a dead page or the content changes in a way not compliant to the rxjs code of  conduct.

Any opinions or other solutions?

@JWO719 is there any way that we can make use of https://github.com/ReactiveX/reactivex.github.io ?

Could you please elaborate what you have in mind, I actually don't get it

Seeing that it used Jekyll to create the site, I thought we could look over the structure of how the content is being delivered. Once that is done, it could have a section devoted strictly towards RxJS content. One of the pros that this checks off is the use of code reviews for any content that would be added. I think it is very flexible yet also know that it is not the docs site right now.
Throwing out ideas as they come to me.

I think we can do pretty much the same with dgeni what we are currently using. Therefore I don't see a benefit in using jekyll, or maybe I just don't get it. Theoretically authors could just file a pr with an md in the content folder and this would generate an html page in it. Then we would have the content, but I don't think that many authors will do that. Maybe it would rather be an option for rxjs contributors to use that way. But I'd still prefer a json file with the references. Something like:
[{
  "title": "some awesome title",
  "author": "some awesome author",
  "level": "beginner",
  "link": "....",
  "tags": ["rxjs", "testing", "dunno", ....],
  "releasedAt": "some date"
}]

Those have to be added manually, but I think it would be pretty straightforward to do so and also we could provide search and filter functions easily. Having a component which loads and renders this json file would come with easy unit tests and so on...

Sure this sounds like a good path to take. I don't know much about dgeni. My only recommendation is that this would be an iterative process. With what we are discussing right now, it could be a longer process of getting external resources available for people. Having one markdown file like I had in the proposed PR could be a good start and could incorporate the same properties that you are showing in your example above. I would consider it to be a phase 1 and phase 2 pipeline of deliverables.

Oh yeah that's totally fine for me. Good suggestions

@JWO719 cool. I will structure the content based on the JSON format that you have given above in a regular markdown style file. Then while a more thorough external reference is being created, this file can be updated so we have that information to port into the 2nd phase.

With the merge of the external resources, this can be closed IMHO.


Change to Docker instructions

Added command to change ownership of /srv/zulip to user zulip, otherwise the provision script is not allowed to continue

I cleaned up the commit message and merged, thanks @emilio-aburto!

I just realized that I used chmod instead of chown! Oh crap, can you correct this instead of sending another PR?

Sure, but can you test this a bit more carefully first?  I suspect the /bin/bash is also unnecessary, now that I'm reading this more closely.


NIFI-6610 Disconnected Relationship support of Connect WebSocket processor in Nifi

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
We are using Connect WebSocket processor to connect to a WebSocket server.
As part of the requirement, when the WebSocket server closes the connection, we need to do retry mechanism.
Current connect WebSocket processor does not have disconnected relationship that indicates jetty @OnWebSocketClose callback.
This is required, so that in case of the disconnected relationship we can do the retry mechanism
Enables Disconnected Relationship support functionality; fixes bug NIFI-6610.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message? Yes

[ ] Does your PR title start with NIFI-6610 where 6610 is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
Yes

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?
Yes

[ ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder? Yes
[ ] Have you written or updated unit tests to verify your changes? Yes
[ ] Have you verified that the full build is successful on both JDK 8 and JDK 11? Yes
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0? N/A
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties? Yes

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered? Yes

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

waiting for the review to be done

could some one please review my code ?


cmd/bosun: check for template before using

I merged this because it needs to go out, but I'd appreciate a review anyways. Thanks.

Looks fine. That function will be deleted with #868 anyway.


feat: add xata example

This PR adds an example to use Remix with Xata as its data layer

Thank you very much for the suggestions and feedback! And sorry it took me so long to address them 🙇♂
I believe I have now addressed everything!


[case]fixmove rest cases from p2 to p0 and fix iceberg version issue for 2.1 (#37898)

bp: #37898

run buildall


What difference btw Block-nerf and Mega-nerf

Hi,
I am wondering that what is the difference between Block-nerf and Mega-nerf?
Thanks and regards,
Hung

We are benchmarking the two algorithms and supporting all the datasets. At that time, one can clearly observe the difference.
You may refer to the Mega-nerf's authors' post: https://github.com/cmusatyalab/mega-nerf/issues/23

Thank you, sjtuytc.
Did you mean that this work is for benchmarking the two algorithms? If right, I got your work now. Because I see that the title is BlockNerf for Pytorch, I think this is the code for Block-nerf.
Thank you for your clarification.
Cheers.

Sure, the ultimate goal should be the large-scale neural radiance fileds. But Block-NeRF is easy to search and remember so we keep this name. This repo is not restricted to the original Block-NeRF algorithm but is heading towards a system such as Detectron2.

Thank you Sjtuytc.

I close this issue temporally and please re-open if the above solution does not address your problem.


fake storage class

How can i fake storage GCS, in unittest i use:
Storage::fake('gcs');
but:
$browser->fake(Storage::class, 'gcs')
seems not to work!

I've been trying to look into this but I switched to using alpine linux with docker some time ago and I can't get dusk tests to run in there, so I can't reproduce your problem yet. I'll get back to you when I can reproduce it!

After some time digging into the problem, I found the reason why this is not working. And that is because the Storage facade uses the FilesystemManager, which contains a reference to the Application instance and that cannot be serialized (among other things, because it has Closures). You can learn more about this in the "How does it work?" section of the readme in this repo.
I've been working on a fix for this, but the current implementation only works for the first test, and subsequent tests fail. I still have to find why is that happening. On the meantime, it should work if you set the processIsolation option for your phpunit tests to true.

Oh ok... I understand! I wait for a fix.... thanks for a great work!

@lucabecchetti I just released a couple of version (compatible with dusk 4 and 5) fixing this, let me know if it works for you!

Thanks! I’ll try it next week!

@NoelDeMartin it works like a charm! Thanks!


Microsoft Edge support added

Hello @vitorgalvao, I think it is a good idea to add support for Microsoft Edge.

Thank you for the submission. It is a good idea, but it’s in the wrong place and incomplete (edge variants missing). I’ll update the Workflow soon, and all the others that use this.
Appreciate the nudge about the missing browser support.


Registration process 'hangs' when user is already signed in to Github

When a user clicks 'register with Github' and is already signed in to github, the server returns a 500 error.

Reported by @ccsr

+1 this is still an issue. Should we at least hide that button for now as it is broken?

Ping @bajiat. Should we prioritize this bug?

My suggestion is to remove the feature (button) and reprioritize to later.

@jykae took a quick look and suspects that we are still using boilerplate
code for Github signin/signup. Would this be fixed by using accounts-github
instead? Info can be found from the Meteor guide. If yes, then I would
prioritize this.
2016-09-28 14:58 GMT+03:00 Philippe Luickx<EMAIL_ADDRESS>
My suggestion is to remove the feature (button) and reprioritize to later.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apinf/platform/issues/422#issuecomment-250146547, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALFnlJH3tAmbysAlyFHB2rlo4DLoiwsVks5qulZRgaJpZM4F2cVn
.

--
Taija Björklund
p. 040 5177 969
<EMAIL_ADDRESS>www.linkedin.com/in/taijabjorklund

We also need to find out if Apika needs Github authentication. Ping @kyyberi

Self-assigned. Purpose is to check the workload for remaining sprint on Monday and then make a decision on whether we would be able to fix or hide.

Here is info on login packages from Meteor guide, if that helps: https://guide.meteor.com/accounts.html#supported-login-services

@bajiat @brylie
Our implementation of Github does not completely follow guidelines: http://docs.meteor.com/api/accounts.html#service-configuration
Our login hook seems to try login manually with Github API:
https://github.com/apinf/platform/blob/develop/users/server/accounts_hooks.js#L38
Suggested way in guidelines to do login is to use loginWithGithub function, that uses saved service configuration. Service configuration is saved & updated right way.
I can successfully register & login with Github locally with development version.
Issue verified at least in nightly.

@bajiat @brylie ROOT_URL env variable had typo in nightly.apinf.io, missing "h". thanks @shaliko for quick fix.
Verified to work with @Laura-Sampo after change.

@philippeluickx Can you also verify that you are able to register using Githubm authentication?

All good now!

Cool. @bajiat @jykae can we close this issue?

I am fine to close.


MERGE DEVELOP CHANGES TO MAIN

Current changes in (develop) branch are ready to merge, after revision

LGTM


[bug] no popup selector on 12.4

Bug in 12.4 (insider):

There is no popup selector when using @.
After typing @today and hitting enter, it still replaces @today with [[2021-05-26]]
After typing @tomorrow and hitting enter, I get today's link: [[2021-05-26]]

I'm not sure why, but it works today.   Weird.


funding channel waiting event will timeout

➜  ~ lampo-cli --network testnet fundchannel --node_id 030b686a163aa2bba03cebb8bab7778fac251536498141df0a436d688352d426f6 --amount 500000 --public false
{
  "code": -1,
  "message": "timed out waiting on receive operation",
  "data": null
}

An error happened but we were not able to catch it, and we timeout

Blocked by https://github.com/vincenzopalazzo/lampo.rs/issues/237
We should use the event a little bit better there to notify the caller


We have.win2016 server, still.findout how to connect to docker machine
Any glue?
On Oct 9, 2016 14:54, "Mano Marks"<EMAIL_ADDRESS>wrote:

Definitely planned!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/docker/labs/issues/69#issuecomment-252471251, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AANT-soujq0vamzh57HIyRWc8Tx6nia0ks5qyJ3HgaJpZM4KRwFo
.

Update on this, we don't yet have a way to provision Windows hosts in Docker Machine. So this will have to wait until this is possible.


Risk - merge without review - Test daily risk

⚠ Pre Checklist

Please complete ALL items in this checklist, and remove before submitting

[ ] I have read through the Contributing Documentation.
[ ] I have added relevant tests.
[ ] I have added relevant documentation.
[ ] I will add labels to the PR, such as pr-type/bug-fix, pr-type/feature-development, etc.

Summary
What does this PR do?
Does this close any open issues?
Closes xx
Screenshots
Include any relevant screenshots here.
Other Information
Any other information that is important to this PR.

Sorry, it was supposed to be conducted in my forked repo.


Issues with async code

Hi Everyone,
I'm battling with an issue where I receive the following error when running an acceptance test on my registration code:
Error: Uncaught Error: Assertion Failed: You have turned on testing mode, which disabled the run-loop's autorun. You will need to wrap any code with asynchronous side-effects in a run
Here's my test:
import {
  describe,
  it,
  beforeEach,
  afterEach
}
from 'mocha';
import {
  expect
}
from 'chai';
import sinon from 'sinon';
import Ember from 'ember';
import startApp from '../helpers/start-app';
import config from '../../config/environment';

describe('Acceptance: Registration', function() {
  var application;
  var server;

  ///////////////////////////////////////////////////
  /// Setup
  ///////////////////////////////////////////////////

  beforeEach(function() {

    // start the ember application
    application = startApp();

    // invalidate session if it exists
    invalidateSession();

    // create a fake server to intercept ajax requests
    server = sinon.fakeServer.create();
    server.respondImmediately = true;

    // simulate successful login
    server.respondWith('POST',
      config.APP.API_URL + '/auth/login', loginSuccessResponse());

    // simulate successful registration
    server.respondWith('POST',
      config.APP.API_URL + '/auth/register', registerSuccessResponse());
    });

  afterEach(function() {

    // restore an alterations to the login endpoint
    server.restore();

    // tear down the application
    Ember.run(application, 'destroy');

  });

  ///////////////////////////////////////////////////
  /// Tests
  ///////////////////////////////////////////////////

  it('can register with valid information', function(done) {

    visit('/signup');
    fillIn('#businessName', 'test');
    fillIn('#firstName', 'test');
    fillIn('#lastName', 'test');
    fillIn('#email', 'test@test.com');
    fillIn('#password', 'q1w2e3r4');
    click('#submit');

    andThen(function() {
      expect(currentRouteName()).to.equal('login');
      done();
    });
  });

And finally, here's the code that's running in the controller that's causing the hiccup:
signup: function() {
  const _this = this;
  const flashMessages = Ember.get(this, 'flashMessages');

  // clear leftover flash messages
  flashMessages.clearMessages();

  // perform validation on the form
  this.validate().then(function() {

    // create the business record
    var business = _this.store.createRecord('business', {
      'name': _this.get('businessName')
    });

    // create the businessAccount record
    var businessAccount = _this.store.createRecord('businessAccount', {});

    // register the user
    Ember.$.post('/auth/register', {
      businessName: _this.get('businessName'),
      firstName: _this.get('firstName'),
      lastName: _this.get('lastName'),
      email: _this.get('email'),
      password: _this.get('password')
    }).done(function(response) {
      flashMessages.success('Thanks for signing up! Check your email for a link to verify your account.');
      _this.transitionToRoute('login');
    }).fail(function(error) {
      flashMessages.warning(error);
    }); // register()

  }).catch(function() {
    // display any errors returned by the client-side validator
    var errors = _this.get('errors');
    for (var e in errors) {
      if (errors.hasOwnProperty(e) && errors[e].length > 0) {
        flashMessages.warning(errors[e]);
      }
    }
  }); // validate()
}

I realize that the call to Ember.$.post is asynchronous, but it was my understanding that the Ember test helpers, such as click() were of the asynchronous sort and andThen() would wait until any async operations have been completed.
Regardless, I'm pulling my hair out a bit and would appreciate any help before it's all gone :)
Thanks in advance :+1:
Best,
James

You need to do what it's telling you to do :trollface: .
But really, this issue would happen in ember-qunit, too. You're going to need to wrap any code with async effects in Ember.run.
A cursory look at your code shows a few places you'll need to use an Ember.run:

The createRecord
The jQuery.post

To do this correctly, put it in an Ember.run like this:

Ember.run(this, function() {
    Ember.$.post('/auth/register', {
      businessName: _this.get('businessName'),
      firstName: _this.get('firstName'),
      lastName: _this.get('lastName'),
      email: _this.get('email'),
      password: _this.get('password')
    }).done(function(response) {
      flashMessages.success('Thanks for signing up! Check your email for a link to verify your account.');
      _this.transitionToRoute('login');
    }).fail(function(error) {
      flashMessages.warning(error);
    });
});

Thanks for the help, @blimmer! It turns out that this isn't a ember-mocha issue at all. Instead, it appears that Ember doesn't know about jQuery promises. Therefore I needed to either wrap my jQuery call in a promise or wrap the calls in then() with Ember.run().


Kibana 6.x (6.3.0) support

Hello,
is there any plans to make this plugin works with latest kibana version?
Thanks for a great plugin.

hear hear

+1

Do we have support for this in 6.3.0?

We skipped loads of releases and went directly to 7.4.2:
https://github.com/ommsolutions/kibana_ext_metrics_vis/releases/tag/7.4.2
It's unlikely that there will be a version 6.x release.


more details needed

Where does this current data come from? Is it coming from https://www.akamai.com/products/mpulse-real-user-monitoring  - the site / documentation is really thin on this.
Please explain more how is the current data collected.

Hi @matti !
The Datasets section of the documentation lists where each dataset is coming from: https://rumarchive.com/datasets/
In particular, for mPulse: https://rumarchive.com/datasets/#akamai-mpulse-rum
The Methodology section should also describe how the data is collected, aggregated and shared: https://rumarchive.com/docs/methodology/
Please let me know if you need any other specifics

We can re-open if you have any further questions.


OSError: exception: access violation reading 0x0000000000000000

Please note
If you are reporting an installation or module import issue, please note that
this project only accepts reports about problems with packages downloaded from
the Python Package Index. Conda users should take issues to one of the
following trackers:

https://github.com/ContinuumIO/anaconda-issues/issues
https://github.com/conda-forge/shapely-feedstock

Expected behavior and actual behavior.
(For example: the area of my geometry is 1.417 when it should be 1.414.)
Steps to reproduce the problem.
(For example, a script with required data)
Operating system
(For example, Mac OS X 10.12.3)
Shapely version and provenance
(For example, 1.6b4 installed from PyPI using pip)
c = fiona.open(shp_path)    #打开路网数据
coord_feature_dict = {}
geom_list = []
for feature in c:
geometry = feature['geometry']
geom = shape(geometry)
geom_list.append(geom)
coord_key = geom.coords[0] + geom.coords[-1]
assert(coord_key not in coord_feature_dict)
coord_feature_dict[coord_key] = feature
Traceback (most recent call last):
File "C:/Users/guanhuizhen/Desktop/map-match-master/get_od_path.py", line 161, in
road_rtree, coord_feature_dict = get_road_rtree('./shp/input/connected_road.shp')
File "C:/Users/guanhuizhen/Desktop/map-match-master/get_od_path.py", line 47, in get_road_rtree
coord_key = geom.coords[0] + geom.coords[-1]  #首末点
File "D:\software\anaconda\lib\site-packages\shapely\geometry\base.py", line 322, in _get_coords
if self.is_empty:
File "D:\software\anaconda\lib\site-packages\shapely\geometry\base.py", line 643, in is_empty
return (self._geom is None) or bool(self.impl'is_empty')
File "D:\software\anaconda\lib\site-packages\shapely\predicates.py", line 25, in call
return self.fn(this._geom)
OSError: exception: access violation reading 0x0000000000000000

I think this is very likely to be either of 1) a problem with your conda environment or 2) a problem with a particular feature geometry. I can't help with #1.
Can you share the value of geometry when the exception occurs?

This is value of ###geometry  :{'type': 'LineString', 'coordinates': [(818021.4062999999, 2496252.202299999),<PHONE_NUMBER>999998, 2496258.6306)]}.
I have no idea of this error .Can you help me ? Thanks a lot.

I just try upgrade the versions of shapely,then i solve this problem.

@skyfully thanks for following up! I'm happy that the problem is solved.

Updating shapely worked for me too.


feat(NumberTheory/LSeries/*): add material on convergence

This continues a series of PRs on L-series.
Here we add ArithmeticFunction.LSeriesHasSum (in NumberTheory.LSeries.Basic) and ArithmeticFunction.abscissaOfAbsConv (in a new file NumberTheory.LSeries.Convergence), together with some results about these notions.
See here on Zulip.

bors r+


fix typo in bevy_ecs/README.md

Objective
Fixes #3866
Solution
Fix comment in bevy_ecs/README.md

bors r+

thanks!


DST Weirdness on Timeline - Day Planner 0.15.3

Describe the bug
It was 12:46pm when I took this screenshot. The timeline is showing the time as being around 1:46pm. I set a task for right now and the task instead assigned itself for 11:46.
Everywhere else on obsidian, the time is reporting properly. I'm using Windows 10 and my time and date automatically updates. I'm using 24 hour time format in Windows if that makes any difference.
To Reproduce
Steps to reproduce the behavior:

Restart obsidian after Daylight Savings Time has ended
Open timeline view and notice that the yellow line is in the wrong place
Create a task for current time
Task is on timeline an hour too soon

Expected behavior
I expected a task created for right now to show at the current time. I also expected the yellow line that's supposed to signify what time it is currently to show the current time.
Screenshots

In the community plugin settings, the time shows correctly (screenshot taken at 12:53pm)

Additional context
Add any other context about the problem here.

I am also experiencing this issue on v0.15.3

Does not appear to be affecting any days after Sunday, Nov 5th.

Also experiencing something similar, reposting comment on #215 https://github.com/ivan-lednev/obsidian-day-planner/issues/215#issuecomment-2395262261 :

Some states in Australia observe Daylight Saving, and today the clock moved forward an hour. All was working fine until today, when I woke up to my timeline looking like this:

See how the current time indicator line and the gutter to the left is correct (it's currently 1pm) but the task is put an hour ahead at 2pm, even though you can see on the task it's marked for 1pm.
Restarted the app multiple times thinking maybe there were some quirks with how the plugin syncs its timezone, but unfortunately the problem is still there.

This kept troubling me until I restarted Obsidian. Maybe the timeline is set up at plugin initialisation and things go wrong if DST is changed while Obsidian is running?


2014-2015 emojis (http://www.unicode.org/emoji/charts/full-emoji-list.html)

Support for new emojis.

Cool! Thank you!

Thanks!
Enough for a new release?

Probably! Need to get test suite and CI updated onto newer versions of Ruby. Thanks!

@mwunsch have you gotten a chance to do the updates you needed before tagging a new release? the speed improvements in master vs 0.4.1 are significant :+1:


[BUG] Lambda based Youtube video transcript download seems to be blocked

Describe the bug
Filling out this field will help us investigate the issue efficiently. Providing detailed information allows us to set the appropriate priority. We appreciate your cooperation.
A clear and concise description of what the bug is.
Creating a new Bot including a knowledge base from Youtube transcriptions fails. Error in Frontend: "Failed to detect language: Could not retrieve a transcript for the video https://www.youtube.com/watch?v=Pv0cfsastFs"
This error message is misleading, because what seems to go wrong is not language detection specifically, but the whole transcript API seems to be not usable.
It took me quite some research to have good evidence that AWS owned IP addresses are (currently) blocked from Youtube transcription download. This applies at least to Lambda functions and Cloud9. Tested in us-east-1, eu-central-1 and ap-northeast-1.
To Reproduce
Filling out this field will help us investigate the issue efficiently. Providing detailed information allows us to set the appropriate priority. We appreciate your cooperation.
Steps to reproduce the behavior:

Create a new Bot, adding any arbitrary Youtube URL as part of the knowledge base. After the sync phase is done, it will show you the related error.

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Error situation on the Bot overview list:

The problem is caused by youtube-transcript-api library. Issues:

https://github.com/jdepoix/youtube-transcript-api/issues/293
https://github.com/jdepoix/youtube-transcript-api/issues/303

We may remove the youtube feature in the future for KB integration. Thank you for your understanding.


Character won't mantle when inside a collision sphere

I'm currently trying to mantle over a simple rock. If the character isn't within a collision sphere, the mantling works. However, if it is within the sphere collision, it's not mantling.
Here is a screenshot of whatMs happening.

Here is my sphere collision setting:

I've made some progress. It seems like the Object Type must not be either:

WorldStatic
WorldDynamic
Destructible

The others will work.
I'm not sure if it's normal, it's the first time I have to tweak these. Is it a bug?

Not a bug, because you can tweak it
Settings->Mantling.MantlingTraceObjectTypes

Thanks for pointing that out! I'll need to dive deeper into these settings. You guys really thought about everything!


Keep the count of the inner nested microformats

If the count == 0, there are no nested microformats and then use the implied name.

sorry I missed this when it first came in 😕 Closing PR, as this got handled (in a slightly different way) in 906e843bd1e2790bdcae7c46460f1a32ffbe720c


Clientv3: Watches stop working permanently after Close()

I'm experiencing what I'm pretty sure must be some sort of strange etcd bug. I've tried with both current git master, as well as a commit right after https://github.com/coreos/etcd/issues/5495 was fixed.
What happens:
I startup one server, and a client that connects to it. It runs some watches. Then I startup a second client and connect it to the first server. It then runs some watches too. Then I startup a second server and have it join the cluster. At this point I'd like for client two to also know about the new endpoint (server 2). This would be nice natively as #5491, but in the meantime let's emulate it. I then run a Close() on client 2's connection, and then try and Connect again.
It seems that whenever I do a Close() it causes all existing watches to go crazy. They report events repeatedly, but in particular:

response.Canceled == false
response.Err() == nil
response.Header.Revision == 0

The last one is particularly mysterious! Unfortunately, they continue to spawn events, and this never ends. Fine, however, even after the new Connect() happens they still spawn these empty events...
If anyone could recommend some things to try or has seen something similar, I'd appreciate the help.
It's also worth pointing out that this issue is probably a blocker for: https://github.com/coreos/etcd/issues/5491 which I am encountering by attempting to emulate that feature.

Actually please hold off on investigating, I think this might be related to re-using of a context... I'm investigating. If anyone has information related to that sort of thing and how it might manifest itself, please let me know. Thanks!

@purpleidea Close() on what? Watcher.Close() and Client.Close() will close all associated watch channels (that response data looks like it's reading from a closed channel).

AFAICT, this bug was due to a mistake on my part:
The issue: if you use a certain context (call it ctx) and then you Close() and then You Connect a brand new connection, but reuse ctx for the Watch, then it causes this error. It's probably worth mentioning this somewhere if you think it's useful information. It wasn't obvious to me anyhow.
Sorry for the noise, hopefully this is useful info.


Fix version string for nightly build

Followup to PR #12. Embarrassingly I must have somehow got lost in the various Azure builds, and didn't notice that I used an invalid version string for conda recipes. This PR updates the version string for the nightly builds to satisfy both conda and setuptools requirements:

conda: cannot include dashes
setuptools: must adhere to PEP 440

I went with X.X.X.devYYYYMMDD, but I'm open to other options that satisfy the requirements. Note that X.X.X corresponds to the latest version in the conda recipe. It's possible to instead use the current version string in the upstream Git repo, but I'm trying to avoid prematurely optimizing this nightly build pipeline.
Here are the relevant Azure logs from my fork:

builds on branch "nightly-build"
build log that passed before I opened this PR - note the use of the version string 1.2.1.dev20230417
build log (currently running) from squash commit

I confirmed it's passing now: https://dev.azure.com/TileDB-Inc/CI/_build/results?buildId=31601&view=results


fix detection of redis loading the dataset

we just discovered that the reconnect implemented in #149 does not work properly: the exception message has a \r\n at the end. so calling equals always returns false and hence the workers will terminate.
the fix is to call startsWith instead.

Coverage remained the same at 70.823% when pulling 8fe0606aae9f80248c49ab65369812f4923a14e7 on uberall:fix-loading-dataset-message into b55a7c821534faf0083881974e566bc4bc588e11 on gresrun:master.


Update for testssh.sh 2.8

Hi, it looks like testssl.sh 2.8 was released a few days ago: https://github.com/drwetter/testssl.sh/releases
Any plans to update this docker image to support the latest release?
David

Thanks. I missed the release. I had been checking periodically. I'd like to support the new release. I haven't looked into it yet, but I'm hoping it is an easy update to make. Thanks again.

On Dec 1, 2016, at 12:31 PM, David Green<EMAIL_ADDRESS>wrote:
Hi, it looks like testssl.sh 2.8 was released a few days ago: https://github.com/drwetter/testssl.sh/releases
Any plans to update this docker image to support the latest release?
David
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I've completed the update. Please let me know if you encounter any issues.

Great, thanks!

@MatthewVance running this we're seeing Fatal error: No IPv4 address for "myhostname" available which looks like issue #1 - any ideas?

@greensopinion can you provide more detail? What command were you trying to run? Were you scanning an internal or external DNS name? I did a quick check and the latest version appeared to work when I scanned an Internet address. However, I got a similar error when trying to scan a FQDN on my LAN. I believe this was because the DNS config of my Docker instance wasn't using my internal DNS server.

@MatthewVance we're using the following Dockerfile:
FROM mvance/testssl:2.8rc3

RUN apt-get update && \
    apt-get install -y \
        netcat && \
    apt-get clean && \
    rm -rf /var/lib/apt/lists/*

ADD testssl-wait.sh /testssl-wait.sh

ENTRYPOINT ["/testssl-wait.sh"]

the testssl-wait.sh looks like this:
#!/bin/bash

set -e

if [ $# -ne 2 ]
  then
    echo "usage: testsssl-wait.sh <hostname> <port>\n (got $# arguments: $*)" && exit -1
fi

TESTSSL_HOSTNAME=$1
TESTSSL_PORT=$2

echo -e "Waiting for availability of $TESTSSL_HOSTNAME:$TESTSSL_PORT"
while ! nc -w 1 -z $TESTSSL_HOSTNAME $TESTSSL_PORT; do
  sleep 2;
  echo "."
done
echo "$TESTSSL_HOSTNAME:$TESTSSL_PORT available"

testssl.sh --color 0  $TESTSSL_HOSTNAME:$TESTSSL_PORT | tee testssl.out

if $(grep -i "Fatal error" testssl.out); then
    grep -i "Fatal error" testssl.out && exit -1
fi

TESTSSL_RESULT=$(grep -i "(NOT ok)" testssl.out | wc -l)
if [ "$TESTSSL_RESULT" -ne "0" ]; then
    echo "Failed with $TESTSSL_RESULT violations:" && grep -i "(NOT ok)" testssl.out && exit -1
fi

The Docker container is brought up in a docker-compose environment with the other container being an HTTP webserver (Tomcat actually).  Here's the docker-compose.yml:
platform:
  image: docker.van.tasktop.com/thewebserver
  ports:
   - 8443
testssl:
  container_name: testssl
  image: docker.van.tasktop.com/testssl
  links:
   - platform
  command: platform 8443

Interesting. I'm not sure what it would be, if not a local DNS issue given what happened when I tested it. I ran it with with something more like sudo docker run -t --rm matthewvance/testssl:2.8rc3 --protocols example.com. You might also look into the other Docker repo for this at https://github.com/jumanjihouse/docker-testssl to see if it works. You may need to revise the code to use the latest release.

in case anyone else is interested, we solved this problem by declaring the docker-compose version number as 2.1 at the top of the docker-compose.yml:
version: '2.1'

services:
  platform:
    image: docker.van.tasktop.com/thewebserver
    ports:
     - 8443
  testssl:
    container_name: testssl
    image: docker.van.tasktop.com/testssl
    links:
     - platform
    command: platform 8443

Thanks for the update and tip.


Website: Some Spanish translations are missing

🐛 Bug Report
Some Spanish translations are missing
To Reproduce
Navigate to the Spanish version of the website.
Link to repl or repo (highly encouraged)
https://jestjs.io/es-ES/

https://jestjs.io/docs/es-ES/getting-started.html

Edited: Other translations are also failing. Is this a bug or is it that the translation are missing ?. I would have checked myself but I don't have crowdin API key and secret.

Good point. Looks like mixed English & Spanish. By the way, you can support the translation here: https://crowdin.com/project/jest/es-ES#
via CrowdIn ⭐

I think it gets mixed whenever we update the docs? The translations are 100% from the community on crowdin, so if you see anything in English it'd be a great help if you could translate it.


Show FreeRTOS Queues

Convert view to panels. Add panels for queues and semaphores/mutexes. Resolves #41
Some example shots:

Any update on this amazing feature ? :)

Guys maintainig this great repo are busy most probably. We have to wait :)

@hwmland Thanks for contributing and sorry for the delay.
Changes look good in general. Happy to see the introduction of the panels in FreeRTOS.
Will need to test this change with different RTOS implementations.


Web site expired?

"BUY THIS DOMAIN
The domain markdownj.org may be for sale by its owner!"

+1

Wow, it got bought by someone.

what a smart japanese


Python3 cant print unicode

Not quite sure the logistics behind this but attempting to print a string with Japanese characters (or anything utf-8/Unicode isn't working.
# Yes this string looks ugly, but just shows all of the things ive tried
print(str(u"カタカナ")).encode('utf-8')

This throws a..
UnicodeEncodeError: `ascii` codec cant encode characters in positions 0-3: ordinal not in range

Any known fixes?

Woops..

@jakeoid I suppose you can't convert unicode to ascii without being specific in python 3 -> str(u"カタカナ") - maybe close this - it isn't a bitter bug in any case.

BitBar spawns a shell without locale variables.  Python 3 inherits the shell encoding and in the absence of one, it defaults to ASCII.  It will attempt to encode stdout in the default encoding before emission because.... reasons.  The easiest thing to do is to prepend a UTF-8 locale inside the shebang:
#!/usr/bin/env LC_ALL=en_US.UTF-8 /usr/local/bin/python3

print('カタカナ')


Feature Request - data-table - specify date format in column declaration

This repository's issues are reserved for feature requests and bug reports.
Do you want to request a feature or report a bug?
Feature
Feature Request
Would it be possible to add the functionality to specify a date format when declaring columns for the data-table component?
I'm thinking something along the lines of:
columns: ITdDataTableColumn[] = [
    { name: 'startDate', label: 'Start Date', date: true, format: 'yyyy/mm/dd' },
  ];

This would then result in the column cell values being piped to the specified date format.
Apologies if this functionality is already possible through the API, I did notice there is a format field already available but I can't figure out what it does.

Hey @agpreynolds
So the format property does exactly what you want to do, it passes in the value and you return the value that you want displayed for that column.
columns: ITdDataTableColumn[] = [
    { name: 'startDate', label: 'Start Date', date: true, format: (value) => { return formatToSomething(value)} },
  ];

The reason we did it this way is to have the data-table agnostic of formats, and have devs provide their own formatting implementation.

We are gonna add more examples to show how you can leverage fully the data-table + more enhancements for beta.3 😄

Ahh I see, thanks for clearing that up

It's cool you have this implemented and this issue should be closed.  Also this is easily doable using a pipe, and therefore reusable in your project, if the excess code becomes burdensome.

yup, closing this since you can use the format property or a template cell.


huddles: Fix search bug and extract huddle_data

Feel free to squash the first two commits.

This is great, merged, thanks @showell!


File name is same always

Once the image is compressed, the file name is not the same  as of the actual image instead it keeps repeating and storing the image with the same file name.

Hello @diveshlunker thanks for your feedback, Please check the new release(2.2.4) solves covers this issue


feat: annotate OpenAPI spec with operation types and auth requirements

fix: skip internal operations during OAS generation
feat: annotate OAS operations with type and authentication requirements

@fiam good work! Are you addressing filtering internal operations in this PR or another?

@fiam good work! Are you addressing filtering internal operations in this PR or another?

It's fixed in this PR too https://github.com/wundergraph/wundergraph/pull/728/files#diff-7751c31c1535d5b56c9d9545aed171e638b6d5c48a5cf5820896492f1985a328R280


Added optional days argument to clean command

based on: #484
docs: https://github.com/spatie/docs.spatie.be/pull/392

There is a test failing. Seems unrelated to this PR though.

@freekmurze it's fixed by #498

@freekmurze could you release this? The changelog doesn't match with the real releases. So I don't know which one is right.

https://github.com/spatie/laravel-activitylog/releases/tag/3.5.0


Error: Roles do not match in cross cluster search for version 1.12.0

Hello everyone,
We have detected the following behavior:
In Open Distro version 1.11.0 the roles of a coordinating environment matched the roles of the remote environments, being possible that a user of the coordinating environment could perform cross searches while his role was present in the remote environment. Example:
Coordinating cluster:

user: mike
role: custom_admin

Remote cluster:

role: custom_admin

In this case, Mike can access from the coordinating cluster to the remote cluster as the role is the same in both clusters.
In Open Distro version 1.12.0 this does not work. Having the same configuration:
Coordinating cluster:

user: mike
role: custom_admin

Remote cluster:

role: custom_admin

We have found that works by matching per user:
Coordinating cluster:

user: mike
role: custom_admin

Remote cluster:

user: mike
role: custom_admin_2

Amazingly, this works. In this case, Mike can access the remote cluster because the user is matched. Note that the password does not matter and the role that applies is remote(role: custom_admin_2).
We have also verified that the following configuration is valid:
Coordinating cluster:

user: mike; backend_role -> coordinating_admin_custom

Remote cluster:

role: custom_admin; backend_role -> coordinating_admin_custom

If we assign to a user of the coordinating cluster a backend_role (something that cannot be done from the security interface in Kibana) that also exists in the desired role of the remote cluster, it works.
We have not found anything in the documentation or in the changelog of version 1.12.0 that explains this behavior, so it seems to be an error.
Regards

Any update on this?

Permission evaluation happens local to the cluster based on the roles associated with the user.
For cross cluster requests, user(with backendroles obtained from authentication backend) is passed in the request from local cluster to the remote cluster and
the remote cluster gets all the roles associated with this user (locally) and evaluates the permissions.
In the above case,
Case 1 - With just cusotom_admin role and no user at remote cluster
the behavior observed in 1.12 is valid. I tried to reproduce the behavior observed in 1.11 and the request failed with security exception. (which is valid behavior and same as 1.12)
At co-ordintating cluster

Created a user testadmin
Created and asssociated indices_all permissions to same_role in co-ordinating cluster
same_role is mapped to testadmin in co-ordinating cluster

At remote cluster

Created and associated indices_all permissions to same_role in remote cluster
(No testadmin user here)

Case 2 - With same user but different roles - This is valid behavior and from above issue description as well, there is no regression in 1.11 and 1.12.

Here, based on the user plugin gets all the roles associated locally (in the remote cluster) and if these roles have sufficient privileges the request goes through.

Case 3 - With backend roles same in both cluster - a valid behavior and from above issue description as well, there is no regression in 1.11 and 1.12.

Here, based on the user in the request and the associated backend roles, the plugin(at remote) gets the roles mapping to the backend roles. if these roles have sufficient privileges the request goes through.

Let me know, If I am missing anything to reproduce case 1

Hi @saikaranam-amazon
I am facing the same problem as @SitoRBJ. This works on Open Distro 1.11 version, but fails in Open Distro 1.12.
Steps to reproduce case 1 (cross-cluster search in 1.11 version)

Configure remote cluster
Both, the coordinating and the remote cluster use the following images:

Elasticsearch image: amazon/opendistro-for-elasticsearch:1.11.0
Kibana image: amazon/opendistro-for-elasticsearch-kibana:1.11.0

Create index patterns of remote clusters in the coordinating one

This step can be performed without any issues in Open Distro 1.11 version, however, in 1.12 one it seems to be bugged.
Cannot create Index Patterns of remote clusters [Open Distro 1.12]. I hope you can work on it soon.

Create an user in the coordinating cluster

I created the user William in the coordinating cluster and mapped it to the all_access role. The user William does not exist in the remote cluster.

Coordinating cluster:

user: William
role: all_access

Remote cluster:

role: all_access

Go to discover

Cross-cluster searches can be performed correctly. However, in Open Distro 1.12 version when using this same configuration, we got a Forbidden error. If this is the expected behavior, why has it not been included in the changelog?

Tried to reproduce the behavior using 1.11 clusters as mentioned in the previous comment.
I was unable to search the index patterns from co-ordinating cluster (same behavior as 1.12)
@SitoRBJ @Phandora

Were there any backend roles associated with the users that are shared between the two clusters?
Could you verify your cluster security configuration with the setup used below?

Images used:

amazon/opendistro-for-elasticsearch:1.11.0
amazon/opendistro-for-elasticsearch-kibana:1.11.0

Setup:

Remote cluster

Single ES node and Kibana node
Security

User: testadmin1 mapped to all_access role

Coordinating cluster

Single ES node
Security

only role all_access is present (and no testadmin1 present)

Screenshots:
testadmin1 role mapping to all_access

Index pattern search with testadmin1

Index pattern search with admin

Hi @saikaranam-amazon
My environment configuration may have not been detailed enough. I have two environments, both of them, with a single ES node and a Kibana node.

Images used:

amazon/opendistro-for-elasticsearch:1.11.0
amazon/opendistro-for-elasticsearch-kibana:1.11.0

However, one of these environments has been configured as a remote cluster in the other environment, so it can be accessed from its own kibana and from the coordinating cluster's kibana.

Coordinating cluster
Remote cluster

single ES node: 1.11.0 version
single ES node: 1.11.0 version

Kibana node: 1.11.0 version
Kibana node: 1.11.0 version

User: testadmin1 (mapped to all_access role)
User: the testadmin1 user does not exists

Role: all_access
Role: all_access

The all_access role exits in both environments, but the testadmin1 user only exists in the coordinating one.

Coordinating cluster security configuration

Users:

Roles:

Remote cluster security configuration

Users:

Roles:

When accessing from the coordinating cluster's kibana using the testadmin1 it works without any issues since the all_access role exists in both clusters:

Creating index pattern for the remote cluster in the coordinating cluster's kibana (This index pattern is just an example to explain the issue):

Accessing discover:

However, it fails in 1.12 version. It is also related to the issue: https://github.com/opendistro-for-elasticsearch/security-kibana-plugin/issues/688

Any update on this?

This issue seems to be also related: https://discuss.opendistrocommunity.dev/t/cross-cluster-search-with-secured-clusters/5162.
They said it fails on 1.12.0, 1.13.0 and 1.13.1 🤕

Hi,
This issue is currently impacting our production deployments. Did you get a chance to review it?
Thanks.

Hi!
It keeps failing on 1.13.2 version. Any update on this?
regards

We've received reports of this being fixed in 1.13.2. @Phandora if this is not resolved for you, could you please provide additional repro details to help us troubleshoot?
Additionally, we strongly recommend migrating to OpenSearch as that is where we are fixing security issues and others moving forward. Thanks!


Feature request: get available GPU memory

Please add an API to get available memory from the GPU.
When tf.Session() starts, it shows the free memory.

I've implemented this as a user-op available here:  https://github.com/yaroslavvb/memory_probe_ops

@zheng-xq, do you want to bring this in to being a  first-class op?

That seems like a good idea. Feel free to send a PR! We can start with tf.contrib, and migrate to tf core later.

@yaroslavvb would you like to contribute your custom op to tensorflow/contrib?

@gunan done in https://github.com/tensorflow/tensorflow/pull/13107


email alerts for new answers

The research team have requested to be emailed when new answers are submitted to the database by users.

tested on test server and working as expected


Provide a VM Service / DDS API for evaluating expressions based on their location

Consider the following code:
var aaa = 1;

f() {
  var aaa = 2;
  debugger();
}

If I stop at debugger() and hover over aaa on the first line, I will see a value of 2 because we always just evaluate the expression in the current frame. It would be nice if we could provide a location and ask for an evaluation at a given location, which automatically handles selecting the right frame based on the hover location.
It would even be nice if we didn't need to provide an expression at all, but just a location, since VS Code often expands to something that is not valid (an API for "evaluate whatever expression is at [location]"), which causes issues for evaluating expressions in parens (see https://github.com/Dart-Code/Dart-Code/issues/5362).
There's some more discussion about this in https://github.com/Dart-Code/Dart-Code/issues/5362
cc @bkonyi @derekxu16

Not sure if the VM or CFE will be able to reliably figure out the expression to evaluate based on the location information. Ideally the IDE is in the best position to figure out the correct expression to evaluate.

Ah, maybe in that case we need to delegate this to the language server. There's a VS Code API for that, but it's not yet supported in LSP (https://github.com/microsoft/language-server-protocol/issues/1596). I thought since we might want to send the location to the debugger anyway (for https://github.com/dart-lang/sdk/issues/59737) it could do both together. Probably we'd need both though (https://github.com/dart-lang/sdk/issues/59737 to handle scoping, and the EvaluatableExpressions in LSP to handle getting the right expression for a location).
(Feel free to close this if you don't think it belongs here - I'm not familiar with the capabilities and you only said "not sure" :) )

Sorry, I got confused while writing the above. I thought there were two issues for:

using the location to get the expression
using the location to get the scope/frame correct

But actually, it was just this one issue. So if we can't use the location to get the correct expression here, this issue should remain open about using the location for the correct scope/frame :-)


feat: chain-adapters getAddress() get addresses from unchained

Description

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk

Testing

Engineering

Operations

Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #5336

PR #5392   👈

This comment was auto-generated by Graphite.


Private Channels not displaying on Dimensional Transceivers

While using <IP_ADDRESS>3 I am not able to see ( on the available list ) or create new Private channels.  The dimensionalTransceiver.json file is in world/enderio and has all the expected channels listed.
I have 15 channels listed in the file and from above it shows all of them saving.
My UUID matches between login and the json file.
I see a lot of channels saved on server load:
[10:46:37] [pool-7-thread-1/INFO] [EnderIO]: ServerChannelRegister: Dimensional Transceiver data saved to /home/minecraft/./world/enderio/dimensionalTransceiver.json
[10:46:37] [pool-7-thread-1/INFO] [EnderIO]: ServerChannelRegister: Dimensional Transceiver data saved to /home/minecraft/./world/enderio/dimensionalTransceiver.json
[10:46:37] [pool-7-thread-1/INFO] [EnderIO]: ServerChannelRegister: Dimensional Transceiver data saved to /home/minecraft/./world/enderio/dimensionalTransceiver.json
[10:46:37] [pool-7-thread-1/INFO] [EnderIO]: ServerChannelRegister: Dimensional Transceiver data saved to /home/minecraft/./world/enderio/dimensionalTransceiver.json
[10:46:37] [pool-7-thread-1/INFO] [EnderIO]: ServerChannelRegister: Dimensional Transceiver data saved to /home/minecraft/./world/enderio/dimensionalTransceiver.json
[10:46:37] [pool-7-thread-1/INFO] [EnderIO]: ServerChannelRegister: Dimensional Transceiver data saved to /home/minecraft/./world/enderio/dimensionalTransceiver.json
[10:46:37] [pool-7-thread-1/INFO] [EnderIO]: ServerChannelRegister: Dimensional Transceiver data saved to /home/minecraft/./world/enderio/dimensionalTransceiver.json
[10:46:37] [pool-7-thread-1/INFO] [EnderIO]: ServerChannelRegister: Dimensional Transceiver data saved to /home/minecraft/./world/enderio/dimensionalTransceiver.json
[10:46:37] [pool-7-thread-1/INFO] [EnderIO]: ServerChannelRegister: Dimensional Transceiver data saved to /home/minecraft/./world/enderio/dimensionalTransceiver.json
[10:46:37] [pool-7-thread-1/INFO] [EnderIO]: ServerChannelRegister: Dimensional Transceiver data saved to /home/minecraft/./world/enderio/dimensionalTransceiver.json
[10:46:37] [pool-7-thread-1/INFO] [EnderIO]: ServerChannelRegister: Dimensional Transceiver data saved to /home/minecraft/./world/enderio/dimensionalTransceiver.json
[10:46:37] [pool-7-thread-1/INFO] [EnderIO]: ServerChannelRegister: Dimensional Transceiver data saved to /home/minecraft/./world/enderio/dimensionalTransceiver.json
[10:46:37] [pool-7-thread-1/INFO] [EnderIO]: ServerChannelRegister: Dimensional Transceiver data saved to /home/minecraft/./world/enderio/dimensionalTransceiver.json
[10:46:37] [pool-7-thread-1/INFO] [EnderIO]: ServerChannelRegister: Dimensional Transceiver data saved to /home/minecraft/./world/enderio/dimensionalTransceiver.json
[10:46:37] [pool-7-thread-1/INFO] [EnderIO]: ServerChannelRegister: Dimensional Transceiver data saved to /home/minecraft/./world/enderio/dimensionalTransceiver.json

Not sure what other information may be helpful.

Could you screenshot the private channels GUI? What do you mean by "can't create" private channels?

@tterrag1098 here are the images with some basic descriptions at each step:
http://imgur.com/a/OTXZ9
Here is what was added to world/enderio/dimensionalTransceivers after Image 1:
{
    "name": "Private Test",
    "type": 1
  },

@tterrag1098 I tried updating my client and server to <IP_ADDRESS>8 and the inability to create private channels (process to replicate documented in the imgur images) or access existing private channels (also documented in the imgur images) is still non-functional.  Is there more information I can provide that may help narrow this down?

tl;dr: I had this very problem on a server. I tested in single player for this post and I no longer have this problem.
I seem to have been having the same issue, though I'm playing on a server and don't have immediate access to logs. Client and server are using version <IP_ADDRESS>5 beta.
Dimensional Transceivers using private channels as of 1 or 2 weeks ago are still using them. (I don't know what might have changed at that time. No mods were updated between when I started using the Dimensional Transceivers without a problem and now.)
I do not see these in the Available list, but I do see them in the Send or Receive lists in the GUI wherever they existed before.
If I try to create a private channel, it shows up in the available list without the lock icon beside the name.
There were no public channels prior to this that would have persisted. (I'm the first to get into these on the server and kept all my usage on private channels.)
This affects power and item tabs. I assume it affects all tabs, but I used no others prior to this problem beginning.
The server has gone through several scheduled restarts since I noticed the issue.
I tested in single player and discovered that I do not have the issue there, Though I did not have an existing single player world with dimensional anchors, the issue that I was unable to create new private channels or see existing private channels was not present.
After testing in single player I returned to the server world and do not have the problem. I can see the previously existing private channels and I can create new channels that are private.
I have screenshots that I'll compile into an album on imgur if that would help.

Had the problem again as soon as I had to start a new instance. Again fixed by opening a single player world. I didn't even have to do anything like opening the Dimensional Transceiver GUI.

So from what I'm reading, this only occurs on servers, not in singleplayer?

I haven't had the issue in single player, but I haven't played single
player with dimensional transceivers extensively.
On Fri, Jun 12, 2015, 2:32 PM tterrag1098<EMAIL_ADDRESS>wrote:

So from what I'm reading, this only occurs on servers, not in singleplayer?
—
Reply to this email directly or view it on GitHub
https://github.com/SleepyTrousers/EnderIO/issues/2367#issuecomment-111595510
.

@tterrag1098 I just tested <IP_ADDRESS>0 on a server and private channels still do not seem to be created.  This is a brand new world so I cannot see if the other private channels show up.

I cannot reproduce this whatsoever. Tested on a local server.

I downloaded my server and ran it locally, was able to reproduce the locked icon next to private channel not being there.
I removed all mods except EnderCore, Ender IO, and ForgeEssentials Server, still not seeing the lock indicating it's a private channel.
Here is what I had during the minimal test:
Forge Version: forge-1.7.10-<IP_ADDRESS>1-1.7.10-universal
Server Startup Script: java -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -Xmx2048M -Xms2048M -jar forge-1.7.10-<IP_ADDRESS>1-1.7.10-universal.jar
Brand new world
Mods: EnderCore-1.7.10-.0.1.12_alpha, EnderIO-1.7.10-<IP_ADDRESS>0_beta, and forgeessentials-1.7.10-1.4.0-beta8-server
Configs: All default.  I deleted the config folder before starting the server to ensure no prior data would taint the test.
Here are images from the minimal test world: http://imgur.com/a/C4TUI
Are there any other data, tests, setups, etc, I can try to help you reproduce this?

So, this only happens if you have no singleplayer worlds created on that client?

Also, could you please try without FE? That is not needed for testing this, and it contains a lot of hacky stuff.

Going to list out my whole process hoping it helps identify the steps I took to reproduce this.  And after doing this run of tests, I have to agree that not having a singleplayer world may be part of the problem.

Using Technic Launcher, I deleted the Vanilla install of MC I had.
Verified that the modpack was deleted out of .technic/modpack.
Installed version 1.7.10 of Vanilla.
Added in the forge-1.7.10-<IP_ADDRESS>1-1.7.10-universal jar as modpack.jar in the bin folder
Added  EnderCore-1.7.10-.0.1.12_alpha, and EnderIO-1.7.10-<IP_ADDRESS>0_beta to the mod folder
Installed a fresh Forge server, added in the same two Ender* mods.
Once in game I went creative, put down a creative capacitor bank and a dimensional receiver.
Added a private channel, verifying the lock was selected.
No lock was shown on the right hand side.
Verified the usernamecache.json was not in the vanilla modpack folder.
Added the backup usernamecache.json from last night and relaunched vanilla.
Original Private channel still showing as Public, however, new Private channel had the lock as expected.

So it's a username<->UUID issue. Interesting. Will investigate later.

In testing, the above commit fixes the issue, however I'm unsure of the effects that change will have elsewhere. Time will tell, it's really hard to test such things by myself.

Do you have a compiled list of features?  My friends and I can go through them all server side to test them out for you.

@Drethic The most important thing I need to be tested on servers is the Dimensional Transceiver. Make sure there are no new issues from this change.

One player on my server is currently seeing this issue, running <IP_ADDRESS>4.
Does that include that commit?
Of note, the player in question has changed his in-game name previously, and this problem appeared after upgrading to that release.

Have him open a new creative world and access a dimensional anchor (gui).
Then try again on the server. Please report back if the problem remains or
not after that. (For my own curiosity, as this worked around the issue for
me, having had no name changes.)
On Tue, Sep 22, 2015, 8:19 PM Svein Ove Aas<EMAIL_ADDRESS>wrote:

One player on my server is currently seeing this issue, running <IP_ADDRESS>4.
Does that include that commit?
Of note, the player in question has changed his in-game name previously,
and this problem appeared after upgrading to that release.
—
Reply to this email directly or view it on GitHub
https://github.com/SleepyTrousers/EnderIO/issues/2367#issuecomment-142467481
.

That fixed it.

Yes, the problem is that the GUI on the dim trans uses the clientside username->UUID map (the usernamecache.json in the root MC folder). It needs to be changed to either request the UUID from mojang, or use the server data.
Opening a creative world creates the usernamecache.json for your client, so then it works.


request: support pathlib objects

Currently telfhash doesn't support pathlib objects https://docs.python.org/3/library/pathlib.html and gives an error:
>>> import telfhash
>>> import pathlib
>>> a = pathlib.Path('/bin/ls')
>>> type(a)
<class 'pathlib.PosixPath'>
>>> telfhash.telfhash(a)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/nix/store/g4a5izmyv29k6jibzmwa9a8yv2gyj1nw-python3-3.9.6-env/lib/python3.9/site-packages/telfhash/telfhash.py", line 487, in telfhash
    files_list += expand_filepath(path, recursive=recursive)
  File "/nix/store/g4a5izmyv29k6jibzmwa9a8yv2gyj1nw-python3-3.9.6-env/lib/python3.9/site-packages/telfhash/telfhash.py", line 353, in expand_filepath
    for filepath in glob.glob(input_filepath):
  File "/nix/store/81lwy2hfqj4c1943b1x8a0qsivjhdhw9-python3-3.9.6/lib/python3.9/glob.py", line 22, in glob
    return list(iglob(pathname, recursive=recursive))
  File "/nix/store/81lwy2hfqj4c1943b1x8a0qsivjhdhw9-python3-3.9.6/lib/python3.9/glob.py", line 44, in _iglob
    if not has_magic(pathname):
  File "/nix/store/81lwy2hfqj4c1943b1x8a0qsivjhdhw9-python3-3.9.6/lib/python3.9/glob.py", line 156, in has_magic
    match = magic_check.search(s)
TypeError: expected string or bytes-like object

It would be nice if pathlib could be supported in the future.

Thanks for your suggestion. I'll take a look.


Audit use of assert! and debug_assert! for bloat

assert! can cause an unexpected amount of code bloat that takes time to compile and fills up binary space to never ever be executed. See what its impact is on tikv.
A good way to start would be to simply convert all asserts to debug_asserts and benchmark, see if it's worth pursuing. Consider doing the same with tikv's raft and prometheus dependencies.
If it seems worth pursing then decide on a case-by-case basis which have the biggest impact and can be converted.
https://github.com/dtolnay/cargo-expand can probably help.

I don't think this is worth doing.


Enhance Ops Extension documentation

Add more details about the internals of the traffic ops extensions. Includes example of how to configure cron to run the extension scripts.

Thanks!


Add a message in the Target Namespace dropdown that you can type to create a new namespace

Resolves #395 (https://bugzilla.redhat.com/show_bug.cgi?id=1918069)
This places all the namespace Select options in a SelectGroup so that we can place a non-clickable header above them reading "Type to search or to create a new namespace".

When you start typing, the "Create" option appears alongside any existing namespaces that partially match what you've typed.

Note: because we have limited control over the implementation details of the PatternFly Select component's isCreatable mode, this group header cannot be applied to the dynamic "Create ___" option that appears. So if you type something that does not partially match any existing namespaces, the only thing that appears is the "Create ____" option (the new header disappears). There's not much I can do about that at this time.

Converting to draft pending @vconzola's review

Converting to draft pending @vconzola's review

This one's ready now @gildub (and https://github.com/konveyor/forklift-ui/pull/398)

This one's ready now @gildub (and https://github.com/konveyor/forklift-ui/pull/398)


Added first version of settings v2

https://github.com/DozerMapper/dozer/issues/463

First draft of giving the user control on how they want to set certain settings.
CC @orange-buffalo

@garethahealy, thanks a lot, looks very nice to me!


Unable to sign up on Speaker Registration Form.

Describe the bug
Unable to sign up on Speaker Registration Form.
To Reproduce
Steps to reproduce the behavior:

Open Developer Tools
Go to 'http://localhost:3000'
Click on 'SignUp'
Fill Out Form
Post Error in console log

Expected behavior
Successful SignUp
Screenshots
If applicable, add screenshots to help explain your problem.

take a screenshot

http://localhost:3000/#/SignUp

System Info (please complete the following information):

Device: [e.g. Macbook Pro, iPhone6]
OS: [e.g. iOS, Android]
Browser: [e.g. chrome, firefox]
Version: [e.g. 22]

Additional context
Post Error in console log upon form submission. Although object seems to be passing through
Screenshot: https://screencast.com/t/NyNl5KLT

Part of this problem is not having a db connected to the project. Once you set up a local db, if you sign up as a speaker, it will successfully  add the speaker request to the db and it will show up in the admin dash under meetups. However, the talkSubmit action found in src/components/SignUp/SignUpActions.js will still throw two errors
xhr.js:178 POST http://localhost:3000/api/talks/talkSubmit net::ERR_EMPTY_RESPONSE
createError.js:16 Uncaught (in promise) Error: Network Error     at e.exports (createError.js:16)     at XMLHttpRequest.m.onerror (xhr.js:87)


powerdns: 4.1.2 -> 4.1.3

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/powerdns/versions.
These checks were done:

built on NixOS
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/pdns_control passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/pdnsutil passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/zone2sql passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/zone2json passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/dnsgram passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/dnsreplay passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/dnsscan passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/dnsscope passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/dnswasher passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/dumresp passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/pdns_notify passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/nproxy passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/nsec3dig passed the binary check.
Warning: no invocation of /nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/saxfr had a zero exit code or showed the expected version
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/stubquery passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/ixplore passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/sdig passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/calidns passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/dnsbulktest passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/dnstcpbench passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/zone2ldap passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/dnspcap2protobuf passed the binary check.
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin/pdns_server passed the binary check.
22 of 23 passed binary check by having a zero exit code.
20 of 23 passed binary check by having the new version present in output.
found 4.1.3 with grep in /nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3
directory tree listing: https://gist.github.com/4e2a99ca3fe4bbb630b7cbd39e96db37
du listing: https://gist.github.com/9722c4085ca5ddbe661816db86a84a6f

meta.description for powerdns is: '"Authoritative DNS server"'.
cc @mic92 for testing.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: powerdns
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: powerdns
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: powerdns
Partial log (click to expand)
shrinking /nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/lib/pdns/libremotebackend.so
shrinking /nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/lib/pdns/librandombackend.so
shrinking /nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/sbin/pdns_server
gzipping man pages under /nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/share/man/
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/lib  /nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin  /nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/sbin
patching script interpreter paths in /nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3
checking for references to /build in /nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3...
moving /nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/sbin/* to /nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3/bin
/nix/store/yacb209ny3gi3p0bg2n4hamp39b9dqxi-powerdns-4.1.3


Field: slots.default() should be called in render

Overview of the problem
Oruga version: 0.8.5
Vuejs version: 3.4.21
OS/Browser: Windows 10 / Chrome
Description
When using the OField component, I get the following warning:
[Vue warn]: Slot "default" invoked outside of the render function: this will not track dependencies used in the slot. Invoke the slot function inside the render function instead.

This is causing issues with trying to use a bound value for the message and variant properties to show validation errors.
Steps to reproduce
Here's an example component:
<script setup>
import { ref } from 'vue'

const variant = ref(null)
const message = ref(null)

function onClick() {
  variant.value = 'danger'
  message.value = 'This is an error'
}
</script>

<template>
  <o-field
    label="Input"
    horizontal
    :variant="variant"
    :message="message">
    <o-input :maxlength="200" />
  </o-field>

  <o-button @click="onClick">
    Click Me!
  </o-button>
</template>

Expected behavior
When clicking the button, the message should appear below the input and the variant should be applied.
Actual behavior
The warning appears in the console as soon as the component is rendered.
The message appears, and the variant icon appears in the field. But the message text and field border are not getting updated with the variant styling.
If setting variant to a static string value, then the UI appears as you would expect.

I had the same problem and had prepared an environment for inspection.
https://stackblitz.com/edit/vitejs-vite-spyfnj

The unchanged variant class was an unknown bug, thanks for spotting this. (see #834)
The "Vue warning" is a known issue that occurs when moving from the option api to the composition api. The `addons' feature of the OField component needs to check the default slot children. This is done by creating the slot from the template in a function.
https://github.com/oruga-ui/oruga/blob/9693d7c63246eb0d6fab791f272b6d9574dab253/packages/oruga/src/components/field/Field.vue#L202
This was a working behaviour in the options api. However, it is not a good implementation for the composition api.
I think the template of OField needs to be refactored and changed so that a template ref can be used instead to fix this.


Adapt Python generator to Roc

I copied Python's bin/generate_tests.py script and its dependencies (bin/data.py, config/generator_macros.j2, and requirements-generator.txt), and I adapted it to Roc.
To use:

Create a .meta/template.j2 file.
Run bin/generate_tests.py

This will generate the <slug>-test.roc file for each exercise. See bin/generate_tests.py --help for more options.
I also added a template.j2 file for the two existing exercises (hello-world and leap) and regenerated the test scripts.
Now that we have a roc-test-runner and generator script, and a couple working exercises, we can start adding new exercises quickly! 😊

Thanks Erik ☺


merge package from arlac77/npm-package-template

.travis.yml

chore(travis): add node versions -10
chore(travis): remove<EMAIL_ADDRESS>from notifications.email

Coverage remained the same at 83.951% when pulling 1f6b83ad306e00c65ed6ef4c55ac8fcf1724f204 on template-sync-1 into 2e0fe99525dc5035e86820cfade0700215923188 on master.


Add support for custom date format

Adds the option "@nord_tmux_date_format" that allows for customizing the date format shown in the status content.

Closes: #60
Related: #24

Hi @andersevenrud :wave:, thanks for your contribution :+1:
I'll try to test and review the changes this weekend.

Great, thanks! :)

Neat :) Thanks for looking into this so quickly.


Generating error for other language dataset

Please check. it generates the following error for other language dataset
File "train.py", line 158, in
x_batch, y_batch = zip(*batch)
ValueError: need more than 0 values to unpack

It seems like there are errors in your code that created the batch. Would need more details.

I am using your code only i just changed the dataset. (Instead of your english i am using some other language)

running your code in python 2.7. Because of this problem, i am getting error. Could you please tell us how to correct this

If you changed the dataset you also need to change the dataset loading code. I don't think this is a problem with the code in the repository, but rather a problem with your Python code. So I'd recommend posting it on Stackoverflow instead of here and get help here.


(GH-117) Support specifying minimum package version

As discussed in #117 here is support for specifying a minimum allowed version. Test-TargetResource returns true if the installed package version is greater or equal to that specified. This helps when user are given permission to update to the latest version of apps not yet specified in DSC.
Originally I had intended to include a MaxmimumVersion also but on reflection I don't have a use case for this so its probably better to not include it for no reason.
One caveat that i welcome feedback on is that when using MinimumVersion the test is carried out on [System.Version] objects as opposed to strings for the Version parameter. This could be confusing but I didn't want to alter the behaviors of Version as it is an existing feature. Let me know if you have any concerns about this.

Fixed the tests so I think this is ready to merge. I actually updated the script analyzer tests to emit a warning with some information on what issues script analyzer found to make it easier to spot. Im happy to remove this change if it is unwelcome though.
I think this is ready from my point of view. @pauby Let me know your thoughts

Apologies for leaving this to collect dust. I'll keep an eye out and await your feedback

Awesome work! Thanks for your contribution (and patience)!


Issue sharing to devices

Google Support suggested I move to Connector from the old GCP Service app.  To reduce user downtime I installed Connector while the service app was running, everything seemed ok, users could still print, the new Connector was syncing printers to the cloud.  I migrated all my device shared printers off the service app and to the Connector app.  After waiting the recommended 24 hours I found the printers were not showing up on the devices.  I called support and tried isolating some devices, put them in their own OU with no restriction or forced apps, removed firewall settings on the server side so it had full access, still had the same issue.  I downgraded from version 1.16 (https) to 1.13 (http) still had the same issue.  Finally gave up and uninstalled connector and reinstalled GCP Service, which was working prior to the connector install, it is now having the same issue as connector.  Support does not seems to have any more ideas on how to fix this issue and my users are not able to print.

Sharing the printers to devices is not directly related to the connector/service you are using. A few things to check:

make sure the user you are logging into the connector with is at least a delegated admin with Chrome rights in your admin console so that the user can share the printer with your devices via admin.google.com.

As support said, sharing to the devices can sometimes take 24 hours to show on all devices, sharing directly with users or groups should be quicker so if that's an option I'd recommend it.

If you still have issues please re-open or start a new support case and post the case number here, I'll see if I can get the right eyes on the issue.

Closing this for now as it's not a connector-specific issue but again, if you re-open the case, you should still be able to post the case # here.

The user I am using for sharing printers is a super admin on the Google
side and domain admin on the Active Directory side.
Normally printers show up vary quickly within a minute of adding them,
regardless I waited all weekend and they still are not showing up.
Support does not want to open another case number and are not familiar with
you or the github site, my existing numbers are 15522973 and 15486890.
My contact info on the case is<EMAIL_ADDRESS>Thank you
On Mon, Apr 16, 2018, 9:03 AM Jay Lee<EMAIL_ADDRESS>wrote:

Sharing the printers to devices is not directly related to the
connector/service you are using. A few things to check:

make sure the user you are logging into the connector with is at least
a delegated admin with Chrome rights in your admin console so that the user
can share the printer with your devices via admin.google.com.
2.
As support said, sharing to the devices can sometimes take 24 hours to
show on all devices, sharing directly with users or groups should be
quicker so if that's an option I'd recommend it.
3.
If you still have issues please re-open or start a new support case
and post the case number here, I'll see if I can get the right eyes on the
issue.
Closing this for now as it's not a connector-specific issue but again, if
you re-open the case, you should still be able to post the case # here.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/cloud-print-connector/issues/410#issuecomment-381657436,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AgqWiY5A9PNsC_fJUK1c8bMJW6WADPNvks5tpMDZgaJpZM4TWzJ5
.

Thanks, I've followed up on the case.


Add some solvers!

SAT/SMT: https://planet.racket-lang.org/package-source/ianj/smt-solver.plt/1/1/planet-docs/smt-solver/An_SMT-solver_for_Racket.html#(def._((planet.smt-solve..rkt.(ianj._smt-solver..plt._1._0)._smt-solver)._smt-solve))
Systems of equations: https://docs.racket-lang.org/math/matrix_solve.html

old, but I'm guessing not too difficult to un-bitrot..
https://github.com/sid0/z3.rkt
from the paper http://www.cse.iitk.ac.in/users/karkare/pubs/icsews13formalise-id1-p-16138-preprint.pdf
'course, it'd be nice to run/maintain z3 in-process, now that it's licensed much more permissively.


Update readme with the current 0.3.3 installation guide.

Please answer these questions before submitting a bug report.
What version of OpenTelemetry are you using?
0.3.3
What version of Node are you using?
12.14.1
What did you do?
If possible, provide a recipe for reproducing the error.
tried to follow readme here https://www.npmjs.com/package/@opentelemetry/plugin-ioredis to instantiate trackers
What did you expect to see?
success
What did you see instead?
failure because the right modules were not exported from the typescript packages.
The docs should match waht is listed here.
https://github.com/open-telemetry/opentelemetry-js/tree/master/packages/opentelemetry-node
Additional context
Add any other context about the problem here.

I am closing this issue, as I believe it has been addressed in 0.4.0 release. Please add a comment if that is not the case.