[Question] When testing integration tests, it won't work. Does anyone have a similar problem?

Question
I ran  shenyu-admin 、 shenyu-bootstrap 、  shenyu-example-http locally .
I want to test SentinelPluginTest in shenyu-integrated-test-http
Whenever I hit test,

shenyu-bootstrap always gives the following error
2022-03-11 17:05:35 [shenyu-netty-kqueue-5] ERROR org.apache.shenyu.web.handler.GlobalErrorHandler -
[7565afcc] Resolved [ResponseStatusException: 403 FORBIDDEN "The key is not correct."] for HTTP POST /shenyu/plugin/saveOrUpdate

2022-03-11 17:05:35 [shenyu-netty-kqueue-5] WARN  org.apache.shenyu.common.utils.JsonUtils -
write to json string error: org.apache.shenyu.plugin.api.result.DefaultShenyuEntity@5917d0c4
com.fasterxml.jackson.databind.exc.InvalidDefinitionException: Direct self-reference leading to
cycle (through reference chain: org.apache.shenyu.plugin.api.result.DefaultShenyuEntity["data"]-
>org.springframework.web.server.ResponseStatusException["mostSpecificCause"])
	at com.fasterxml.jackson.databind.exc.InvalidDefinitionEx

Can anyone help reproduce or resolve this issue? thank you very much

for some unknown reasons.
The startup project needs to be in an idea window. The above problem will not occur.


Fix strange error when content of heredoc looks like heredoc

Why did you change the argument names of functions such as skipwhite()?
The reason a local variable is used is that this way the original string
can be inspected in a debugger.  In general, function arguments should
not be changed inside a function.
I do not like using "<<" directly after ":lua", ":ruby", etc., without
whitespace.  I do not think this was ever possible, and I see no good
reason to start supporting it now.  The functionality is the same, the
command is less readable.  I rather encourage users to write commands in
a readable way, by separating arguments with whitespace.
--
Back off man, I'm a scientist.
-- Peter, Ghostbusters
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Oh wait, some of the is still applicable.

I've update this PR to only keep changes related to :let.

AppVeyor seems to have some Internet connection problems.


v5.2.0 not working for mobile devices

Initialized with default configuration:
var myScroll = new IScroll('#wrapper', {});
Strange things I saw during debugging:
style="touch-action: none;" on wrapper element
If I pass eventPassthrough: true to options, scroll works

Sorry, it was my error.


theme download should store checksums of each individually downloaded file for faster comparisson

Is your feature request related to a problem? Please describe.
This is related to #801 (theme download gets stuck at 97%).
The issue is that theme download never reaches 100%.
Describe the solution you'd like
I noticed that in the newer versions of themekit, themekit smartly compares local and remote files,
making it much faster on subsequent runs.
I'd love to be able to use this feature.
Describe alternatives you've considered
I've considered using v1.0.2, but v1.0.2 downloads all files every time I run theme download.

I am sorry, is this an issue or is this just you trying to add to an already existing issue?

To me this seemed like a separate issue.
I don't know the internals of themekit, but what I noticed recently is that newer versions of themekit somehow magically remember which files are the same and don't need to be downloaded again.
Running theme download twice on v1.0.2 will run the full theme download twice.
Running theme download twice on v1.1.2 will run the full theme download once and will just download couple of files the second time.
Is this related to theme download stalls at 96%? I don't think so.
Please also notice that this is a feature request, and not a bug report.

This is directly related to that functionality, and the functionality already exists and is implemented.

@tanema from my experience using themekit, this is what seems to happen after you run theme download:

The files are downloaded in parallel
Once all of the files are downloaded, the checksums are stored

The workflow I'm suggesting is:

The files are downloaded in parallel
As each file is downloaded, its checksum is stored immediately.

Perhaps I don't fully understand how this works, especially since I don't see any local changes if theme download successfully finishes (I have no clue where/how the checksums are stored). This would partially fix the other issue, as subsequent theme downloads might actually pass as they will download less files. The main issue of #801 will still not be addressed (initial download).

Themekit does not store anything other than files. Themekit needs a file on the filesystem to check the content of.


[Question] Model with mutltiple relations of same type

Hey folks,
Nvm i figured it out myself, issuer and debtor shouldn't be an Model instance. Ticket can be closed
i'm currently having problems creating an record that has two relations of the same type.
These are the models i defined.
@Table({tableName: 'debt'})
export class Debt extends Model<Debt> {

    @Default(DataType.UUIDV4)
    @Column(DataType.UUID)
    debtId: string;

    @AllowNull(false)
    @Column(DataType.FLOAT)
    amount: number;

    @BelongsTo(() => User, {foreignKey: 'issuerId', as: 'issuer'})
    issuer: User;

    @BelongsTo(() => User, {foreignKey: 'debtorId', as: 'debtor'})
    debtor: User;

    @ForeignKey(() => User)
    @Column(DataType.BIGINT)
    issuerId: string;

    @ForeignKey(() => User)
    @Column(DataType.BIGINT)
    debtorId: string;
}

@Table({tableName : 'bb_user'})
export class User extends Model<User> {

    @PrimaryKey
    @AutoIncrement
    @Column(DataType.BIGINT)
    id: string;

    @Default(DataType.UUIDV4)
    @Column(DataType.UUID)
    userId: string;

    @Column(DataType.STRING)
    userName: string;

    @BelongsTo(() => LoginInformation, 'loginInformationId')
    login: LoginInformation

    @ForeignKey(() => LoginInformation)
    @Column(DataType.BIGINT)
    loginInformationId: string;

    @HasMany(() => Debt)
    debt: Debt[];
}

In a test i've been trying to create records of it, but couldn't get it to work. When omitting the user/debtor save it wouldn't save the User instances and thus leaving the ForeignKeys blank.
When i'd save the instances before calling save on the Debt model it correctly creates the user records and then again when calling Debt.save it would try to create the User again with the same PrimaryKey thus violating the Unqiue constraint. Does anyone know what is going wrong here ?
    it('should find all debts by issuer', async () => {
        const user = new User({userName: 'Rico'});
        const debtor = new User({userName: 'Whatever'});

        // await user.save();
        // await debtor.save();

        const debt: Debt =  new Debt({
            amount: 5000.0,
            issuer: user,
            debtor: debtor,
        }, {include: [{
            model: User,
            association: Debt.issuer,
            as: 'issuer'
        },
        {
            model: User,
            as: 'debtor'
        }]});
        await debt.save();

        console.log(await debtRepository.findByIssuer(user.userId));
    });

Hey @RykoL, since you solved your issue by yourself, can you provide your solution here and close this issue by you own? :)

Sure the solution was just as easy as replacing
const user = new User({userName: 'Rico'});
const debtor = new User({userName: 'Whatever'});

with
const user = ({userName: 'Rico'});
const debtor = ({userName: 'Whatever'});


Specify config file or project location in CLI

Describe the problem
I would like to be able to specify where svelte.config.js (or the target folder) is located when you have multiple apps based on a common lib.
Describe the proposed solution
Have a CLI option for the config file location such as
svelte-kit dev --config my/path/to/svelte.config.js

Or
Have a CLI option for the folder location, which will also handle all generated folders locations
svelte-kit dev --folder my/path/to/folder/

Alternatives considered
I currently use the following architecture:
myRoot/
    lib/
    subProject-1/
        package.json
        svelte.config.js
    subProject-2/
        package.json
        svelte.config.js
    package.json
    svelte.config.js

which is not ideal to maintain, due to duplicate config/dependencies.
Importance
would make my life easier
Additional Information
No response

Adding --config is possible but adds some complexity (see https://github.com/sveltejs/kit/issues/2973#issuecomment-1107863837). My recommendation would be to re-export a shared config, so that you don't duplicate stuff (but also have the ability to extend individual configs where necessary, which wouldn't be possible with --config ../shared/config.js):
import config from '../../svelte.config.mjs';
export default config;

Since this is very similar to #2973, I'll close it in favour of that


Unable to read the IISLOGs

Selected IISLOG in Data, even after a day unable to collect the IISLOG

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

ID: de204b3b-563a-0a65-8f5a-456cc8335585
Version Independent ID: 6b5c30b8-ae3b-12c0-6fd8-9a3d826795cd
Content: IIS logs in Azure Log Analytics
Content Source: articles/log-analytics/log-analytics-data-sources-iis-logs.md
Service: log-analytics
Product: unspecified
GitHub Login: @bwren
Microsoft Alias: bwren

@BharathMannem Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@BharathMannem Not sure this is a doc issue.  What kind of agents are you expecting data from?  Are you getting other data from the agents?

#in-progress

Thanks for your feedback, i corrected it myself, i am getting the data now.

@BharathMannem Can you please let us know what was the issue?
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


DW-109 - Fix , CHAPI default timeout is 1m for UnMount workflow which…

Bug : DW-109
Isssue : CHAPI client is getting timedout when multiple unmount are requested at the same time .
Fix : The default timeout values in 1m which is less , increasing the default timeout to 5m .
Signed-off-by: vidhut-kumar-singh<EMAIL_ADDRESS>

flexvolume dockerclient already has 5 minute timeout , does that not suffice ? If this is changed it impacts the dockerclient timeout too

Sorry didn't understand your comment, this is related to docker unmount workflow and it is failing constantly on Windows . As I can see the default timeout for chapclient is 5m for Mount wokflow however we have 1m timeout for Unmount workflow which is less and, causing unmount workflow issues on Windows.

The same unmount workflow is triggered from flexvolume too if both have 5 minutes timeout it would always timeout if this takes up the entire 5 minutes .
Can you debug further why the unmount takes so long.? We have throttling in unmount workflow controlled by defaultChannelCapacity so we don't process more requests than that.
Some pointers could be duplicate mountID from previous requests which weren't cleaned up because of which mountConflictDelay gets triggered in container provider

The same unmount workflow is triggered from flexvolume too if both have 5 minutes timeout it would always timeout if this takes up the entire 5 minutes .
Can you debug further why the unmount takes so long.? We have throttling in unmount workflow controlled by defaultChannelCapacity so we don't process more requests than that.
Some pointers could be duplicate mountID from previous requests which weren't cleaned up because of which mountConflictDelay gets triggered in container provider

The defaultChannelCapacity is 30 where here we are running unmount of 10 mountpoints . So ,chanellCapacity is not an issue here also there is no stale mount point as all are unique and run first time.
How flexvolume is impacted here since even if we add 5m timeout to CHAPI in unmount workflow?, the total timeout still would be 5m so it doesn't matter. Here we are adding timeout to CHAPI call only  whch is internally invoked during docker unmount workflow.
I think this change would not have any adverse impact even to linux workflow.

10 unmounts take more than a minute ? Are the requests blocking somewhere ? Unmounts should be fairly quick
Also, Since the code is common for Linux and Windows the timeout impacts both. We have tested ~100 unmounts with current values and didn't face issues as throttling with channels helped. Changing this could impact our scale testing.

10 unmounts take more than a minute ? Are the requests blocking somewhere ? Unmounts should be fairly quick
Also, Since the code is common for Linux and Windows the timeout impacts both. We have tested ~100 unmounts with current values and didn't face issues as throttling with channels helped. Changing this could impact our scale testing.

Please don't compare this with Linux as on Windows things are different. Also this is just a timeout value which we are increasing for CHAPI, if on Linux it CHAPI responds fast it will not have any impact anyway.

Sorry, accidentaly closed this pull request. Reopened.

Change the code so that it doesn't have any effect on linux plugin .

Thanks


twinx and datacursor

How can I use the datacursor in case of a twinx statement ?
ax1  = fig.add_subplot(111)
ax2 = ax1.twinx()
ax1.plot(dv[:,1],sr[:,1],label=r'$f_1(x)$')
x = dv[:,1]
y = sr[:,1]
tck = splrep(x, y)
yp = splev(x,tck,der=1)
ax2.plot(x,yp,c='r',label=r'$\frac{\partial f_1}{\partial x}$')
ax1.set_ylabel(r'Fundamental eigenfrequency $f_1$ [Hz]')
ax1.set_xlabel(r'Position $x$')
ax1.grid()
ax2.set_ylabel('Sensitivity')
ax2.legend(loc=0)
c1=datacursor(axes=ax1,formatter='x={x:0.0f}\ny={y:0.2f}'.format,draggable=True,display="multiple")
c2=datacursor(axes=ax2,formatter='x={x:0.0f}\ny={y:0.2f}'.format,draggable=True,display="multiple")
plt.show()

Thanks for the very useful module.
The twin axes workaround only seems to work correctly if the two sets of axes have the same scale/limits, which sort of defeats the purpose:

import numpy as np
from mpldatacursor import datacursor

t = np.linspace(0, 10, 200)
x = np.cos(t)
y = np.sin(t)

plt.close('all')
f = plt.figure()
ax = f.gca()
ax.plot(t, 3 * x)
ax2 = ax.twinx()
ax2.plot(t, 10 * y, 'r')

cursor = datacursor(axes=f.get_axes(), hover=True)

matplotlib 1.4.3
mpldatacursor installed with pip via GitHub 5 days ago

@wilywampa - Thanks for catching that! (and my apologies for my delay in replying)
I've pushed a fix for the problem.  Let me know if it does/doesn't work for you.
Thanks again for the bug report (and your other recent ones, as well)!

That fixed it. Thanks!


fetcher.py crashes unexpected

Have other experienced unexpected crashes of fetcher.py?

My SECRETS.txt contained new lines at the end. After removing them it started working.

@JacobValdemar  this solved here: https://github.com/defaultnamehere/zzzzz/issues/38, you can delete your issue


expose slack api to accept slack event instead of consuming events

First test whether multiple instance consuming has problem (repeated consuming), if yes, fix it via exposing api for slack to access. Otherwise it's ok.

According to my test, as long as the event is acked, it will only be notified once, so it's actually scalable, no repeat processing problems when scaling out.


Refactor: Changes in Types and Decorators

Any usage is removed in the app.
Used concat instead of spreading for handlers concatenation.

I have made changes @aaydin-tr. Could you check them again? I have taken back any for the Function target and i have wrapped it with custom type for now. Because previous definition creates an usage error while trying to use them in the app.

Also pls resolve changes


Test app build on Windows CI

:eyes:

So the app build is failing on CI with
eheap_alloc: Cannot allocate<PHONE_NUMBER>2148144504 bytes of memory (of type "heap").

I believe it originates here:
https://github.com/livebook-dev/livebook/blob/82dac5686114dee9b69742b9604937a3f0708293/app_builder/lib/app_builder/utils.ex#L26
and replacing it with the following helps:
shell!(~s/unzip "#{path}" -d "#{tmp_dir}"/)

I managed to reproduce the error on OTP 25.0-rc3 with this script, see the CI error. The erl_crash.dump is available here.

@josevalim it would make sense to report it upstream, is this enough information/reproduction?
@wojtekmach we will run into the same error if we want to build the app on CI, so for the time being we may need to depend on unzip, or use something more lightweight than ImageMagic :thinking:

Yes, please report this as a bug upstream!
I would also move to something simpler. This looks like a good option: https://github.com/npocmaka/batch.scripts/blob/master/hybrids/jscript/imageProcessing/scale.bat (found in this thread) /cc @wojtekmach

Reported in https://github.com/erlang/otp/issues/5913.

I removed automatic ImageMagick installation in #1201. So either the user already has rmagick.exe in PATH or they'd need to give us a file with the target extension, .ico. Otherwise, they get an error.

btw, I noticed some test failures on OTP 25. Would you mind looking into them?

Perfect, thanks for fixing the build :)

btw, I noticed some test failures on OTP 25. Would you mind looking into them?

Sure, likely some completion failures not accounting for new functions/modules :)


[operator] Align to create-rbac-permission flag deprecation

Ensure SERVICE_ACCOUNT_NAME env variable is set in pods to align with the deprecation of the create-rbac-permission flag
Addressing functionality issues with k8sattributes.

Closes: #1224


Batch Normalization renorm with tensorflow_hub

Hi,
I have observed an issue in Tensorflow hub and batch normalization. It seems that I cannot have a batch normalization layer with renorm in a module. Consider the following short script:
import tensorflow as tf
import tensorflow_hub as hub

def myfunc():
    input = tf.placeholder(tf.float32, [5, 10])
    output = tf.layers.batch_normalization(input, renorm = True)

    outputs = dict(default=output)
    inputs = dict(input_txt=input)
    hub.add_signature(inputs=inputs, outputs=outputs)

g_spec = hub.create_module_spec(myfunc)

which gives me the following error:

Traceback (most recent call last):
File "..../codes/5/test.py", line 16, in
g_spec = hub.create_module_spec(myfunc)
File "/usr/local/lib/python3.5/dist-packages/tensorflow_hub/native_module.py", line 189, in create_module_spec
if err: raise ValueError(err)
ValueError: A state-holding node x of a module's graph (e.g., a Variable op) must not be subject to a tf.colocate_with(y) constraint unless y is also a state-holding node.
Details: node 'batch_normalization/renorm_mean_weight' has op 'VarHandleOp', which counts as state-holding, but Operation.colocation_groups() == [b'loc:@batch_normalization/Read/ReadVariableOp'].

The problem does NOT exist with renorm=False.
Is there anything that I am missing? I have not found a similar problem on Stackoverflow.

Thank you for the convenient repro. I think if you try running this code
against tf-nightly it should work (see example below). TF is loosening
co-location constraints which I think might address this issue.
Python 3.5.2 (default, Nov 12 2018, 13:43:14)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.

import tensorflow as tf
import tensorflow_hub as hub
def myfunc():
...   input = tf.placeholder(tf.float32, [5, 10])
...   output = tf.layers.batch_normalization(input, renorm = True)
...   outputs = dict(default=output)
...   inputs = dict(input_txt=input)
...   hub.add_signature(inputs=inputs, outputs=outputs)
...
g_spec = hub.create_module_spec(myfunc)
WARNING: Logging before flag parsing goes to stderr.
W0226 09:13:14.521587<PHONE_NUMBER>30688 deprecation.py:323] From :3:
batch_normalization (from tensorflow.python.layers.normalization) is
deprecated and will be removed in a future version.
Instructions for updating:
Use keras.layers.batch_normalization instead.
W0226 09:13:14.575267<PHONE_NUMBER>30688 deprecation.py:323] From
/home/akhorlin/.local/lib/python3.5/site-packages/tensorflow_hub/saved_model_lib.py:109:
build_tensor_info (from tensorflow.python.saved_model.utils_impl) is
deprecated and will be removed in a future version.
Instructions for updating:
This function will only be available through the v1 compatibility library
as tf.compat.v1.saved_model.utils.build_tensor_info or
tf.compat.v1.saved_model.build_tensor_info.
print(tf.version)
1.13.0-dev20190226

On Fri, Feb 22, 2019 at 12:22 AM amirmazaheri1990<EMAIL_ADDRESS>wrote:

Hi,
I have observed an issue in Tensorflow hub and batch normalization. It
seems that I cannot have a batch normalization layer with renorm in a
module. Consider the following short script:
import tensorflow as tf
import tensorflow_hub as hub
def myfunc():
input = tf.placeholder(tf.float32, [5, 10])
output = tf.layers.batch_normalization(input, renorm = True)
outputs = dict(default=output)
inputs = dict(input_txt=input)
hub.add_signature(inputs=inputs, outputs=outputs)

g_spec = hub.create_module_spec(myfunc)
which gives me the following error:
Traceback (most recent call last):
File "..../codes/5/test.py", line 16, in
g_spec = hub.create_module_spec(myfunc)
File
"/usr/local/lib/python3.5/dist-packages/tensorflow_hub/native_module.py",
line 189, in create_module_spec
if err: raise ValueError(err)
ValueError: A state-holding node x of a module's graph (e.g., a Variable
op) must not be subject to a tf.colocate_with(y) constraint unless y is
also a state-holding node.
Details: node 'batch_normalization/renorm_mean_weight' has op
'VarHandleOp', which counts as state-holding, but
Operation.colocation_groups() == [b'loc:@batch_normalization
/Read/ReadVariableOp'].
The problem does NOT exist with renorm=False.
Is there anything that I am missing? I have not found a similar problem on
Stackoverflow.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/hub/issues/238, or mute the thread
https://github.com/notifications/unsubscribe-auth/AbunTJbgQ5TCRpZ2vVVcDhd6iFiHh11-ks5vPyozgaJpZM4bIiQ0
.


+noframe, -fitVids

closes #409

Shall I delete this PR? As to make it work, other critical changes will be needed.

@pankajpatel I wouldn't delete it. We can leave it open but put a "[HOLD]" tag in the title. Maybe someone wants to pick it up from here...

@AileenCGN sounds good. Though if I can get few answers to the above question regarding classes and styles, maybe I can finish it.

.kg-card-markdown is part of the editor output so you won't see it in the theme templates. I'll put this PR on my list to pull down and evaluate, I'm sure there will be a fix available for FF

@thomasvaeth this PR has solution related to that; reframe.js does so with JS & CSS and noframe.js does so with CSS
noframe.js was not working properly on Firefox, whereas reframe.js works fine


Not able to change machine status to 'Active'

Hi, I am not able to make a machine 'active' in docker-machine. Ran 'eval $(sudo docker-machine env eris)' command. But it does not affect the status. I am using 0.8.2 version. Is there an issue?

Thanks for the issue -- you shouldn't be using sudo with docker-machine! Execute commands as a normal user, I think this is due to eval $(sudo docker-machine env) getting the environment variables set as sathish, whereas ls is invoked as the superuser.


As an app developer, pack rebase automatically determines a run image using the available mirrors

Acceptance Criteria
Given
When I run pack build my-image
Then I new version of the run image is available on all mirrors
Scenario 1
When I run pack rebase my-image (without --run-image)
Then The run image under my-image is replaced with a run image from the appropriate source
Scenario 2
When I run pack rebase my-image --run-image custom/image
Then The run image under my-image is replaced with custom/image
Notes

Mirror selection for the run image should use the same order as pack build. This means the run-image and run-image-mirrors from the builder used during pack build must be encoded in the generated OCI image on each pack build.
Update pack README to describe new model
buildpack/pack#90 covers updating --no-pull to work when only a local image is available
As with pack build --publish, pack rebase --publish should work when the run image is not available at the target registry. This means that if a suitable run image is not available on the registry, then select the canonical image.
Remove pack *-stack commands

Implementation Notes

Pack CLI should select run image from list of mirrors
pack create-builder should add a file (similar to order.toml) that also contains the run image mirror metadata (that is also available as a LABEL on the image). The file path should have a default value, but also be overridable using an arg or env var (like order.toml).
CNB_MIRRORS_PATH / -mirrors / /buildpacks/mirrors.toml

Added acceptance criteria and notes.

After a team discussion, we want to change this feature to have the following behavior:
Build

If the run-image used during build is not from the local config then include the run-image name as a label in the resulting app image.
If the run-image used during build is from the local config then do not include the run-image name as a label in the resulting app image.

Rebase

If the app image does have a run-image name in a label, use that for the rebase (Scenario 1).
If the app image does not have a run-image name in a label, require the user to specify a run-image with the --run-image flag (Scenario 2).

Waiting on approval of https://github.com/buildpack/lifecycle/pull/90
pack changes on branch run_images_during_rebase to get merged after the above PR is merged

I think the desired end state we would like to get to is the following
pack create-builder
When the builder.toml has the following contents
[stack]
id = "com.example.stack"
build-image = "example/build"
run-image = "example/run"
run-image-mirrors = ["registry.example.com/exmaple/run", "other.example.com/other/run"]

Then the builder is created with a label io.buildpacks.builder.metadata with the following value
"{"runImage":{"image":"example/run","mirrors":["registry.example.com/exmaple/run", "other.example.com/other/run"]}"

And the following file is added to the builder image at path /buildpacks/mirrors.toml.
And the following environment variable is set on the builder image CNB_MIRRORS_PATH=/buildpacks/mirrors.toml
lifecycle/exporter
scenario 1 (default)
When exporter is called w/o the -runImage flag
Then the exporter selects the right run image from the mirrors.toml file at CNB_MIRRORS_PATH
And all the of the mirrors from the mirrors.toml file are add to the io.buildpacks.run-image.metadata label
"{"runImage":{"image":"example/run","mirrors":["registry.example.com/exmaple/run", "other.example.com/other/run"]}"

scenario 2 (runImage)
When exporter is called with the -runImage
Then it uses the provided run-image as the base image for the exported app
And the mirrors from mirrors.toml are added to a label as described above
**The value passed to -runImage does not end up in a label
scenarios 3 & 4 (-mirrors)
When exporter is called with -mirrors=/some/path/mirrors.toml
Then It behaves as described in scenarios 1 & 2 but the mirrors.toml found at /some/path/mirrors.toml is used instead of the file found at CNB_MIRRORS_PATH
pack rebase
pack rebase selects the correct run image from the io.buildpacks.run-image.metadata label
Comments
I am comfortable with us doing some subset of this functionality now but I think the interim behavior the subset to conform to the same interface (lifecycle flag, label names, value names within the labels), requiring only additive changes in the future.

With the above the changes, we should revert the change that added the label flag to the exporter.

mirrors.toml
image = "string"
mirrors = ["string"]

We broke out the exporter selecting the run-image into buildpack/roadmap#58
We also made some last minute changes to the schema of metadata labels and files
on the builder image:

we created a stack.toml file with the following schema

[run-image]
  image = "string"
  mirrors = ["string", "string"]

we added the stack image to the io.buildpacks.builder.metadata label

{"stack":{"runImage": {"image": "string", "mirrors": ["string", "string"]}}}

on the app image:
we added the stack info to theio.buildpacks.lifecycle.metadata label
{"stack":{"runImage": {"image": "string", "mirrors": ["string", "string"]}}}

Leaving this as unaccepted because I want to test more edge cases, but it looks good enough to release in v0.1.0.


F #2161 Skip loopback IP on vxlan tep

Hi Jan,
This gives me the following ruby error:
Thu Nov 15 14:15:14 2018 [Z0][VMM][D]: Message received: LOG I 50 /var/tmp/one/vnm/vxlan/vxlan.rb:100:in block in get_interface_first_ip': undefined method starts_with?' for #<MatchData "    inet <IP_ADDRESS>" 1:"<IP_ADDRESS>"> (NoMethodError)

Oops, thanks for the catch. I fixed this typo locally but pushed the wrong one, anyway should be fine now.

Hmm, still fails for me:
Thu Nov 15 15:55:27 2018 [Z0][VMM][D]: Message received: LOG I 50 /var/tmp/one/vnm/vxlan/vxlan.rb:100:in block in get_interface_first_ip': undefined method start_with?' for #<MatchData "    inet <IP_ADDRESS>" 1:"<IP_ADDRESS>"> (NoMethodError)

Really not my day today, should be fine now.


Victor VosMottor: Watch digital vcard

Victor VosMottor requests the watch of the watch_keyword digital vcard. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

digital vcard has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Not sure this is much improvement over a simple watch on that domain.

Rejected by Mast in Charcoal HQ. Reason: 'Insufficient justification, moderate risk of FP.'


Work around pytube/Youtube integration issue

Youtube changes broke pytube again. There is already a fix queued up for a regex in the pytube MRs. Apply that fix.

This is all set.


improv: Update README.md

Clarified python focus and added cross-reference to Java.
Issue #, if available:
n/a
Description of changes:

Clarified that the repo is focused on Python and added a cross-reference to the Java implementation.
Checklist

[ ] Meet tenets criteria
[ ] Update tests
[ ] Update docs
[ ] PR title follows conventional commit semantics

Breaking change checklist

RFC issue #:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks for the change, Brad :)


Osx nswindow refactor part3

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

You can test this PR using the following package version. 0.10.999-cibuild0020269-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0020271-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0020273-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0020284-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0020287-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0020292-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0020314-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]


Introduce a specific exception for shadow-flow

Is your feature request related to a problem? Please describe.
Let's assume a new flow server is unavailable, then a web-client throws java.net.ConnectException. And in usage, we can't distinguish where this exception happened and who throws it. But we would like to know in order to exclude or ignore for example, otherwise, it affects the whole response and behavior of a service. We expect seamless integration for shadow flow.
In order to reproduce shutdown your shadow-flow server.
There is an exception stack trace.
[instance=MyService] Failed to run the shadow flow
java.net.ConnectException: Connection refused
	at java.base/sun.nio.ch.Net.pollConnect(Native Method)
	at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:672)
	at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:946)
	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:337)
	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:776)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Thread.java:833)
Wrapped by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: localhost/<IP_ADDRESS>:8101
Wrapped by: org.springframework.web.reactive.function.client.WebClientRequestException: Connection refused: localhost/<IP_ADDRESS>:8101
	at org.springframework.web.reactive.function.client.ExchangeFunctions$DefaultExchangeFunction.lambda$wrapException$9(ExchangeFunctions.java:136)
	Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException:
Error has been observed at the following site(s):
	*__checkpoint ⇢ Request to POST null [DefaultWebClient]

Describe the solution you'd like
Introduce a specific exception for a new flow.

It's irrelevant. Shadow Flow doesn't propagate exceptions


Create certificate failed in SBS2012 (all authorization result: valid)

Issue description
Create certificate failed
But following Files could be found in "C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org" :
1,4,5,6,7-chain.pem
1,4,5,6,7-crt.der
1,4,5,6,7-crt.pem
ca-1,4,5,6,7-crt.der
ca-1,4,5,6,7-crt.pem
1,4,5,6,7-csr.pem
1,4,5,6,7-gen-csr.json
1,4,5,6,7-gen-key.json
1,4,5,6,7-key.pem
Steps to reproduce
PS C:\Windows\system32> C:\Users\Public\Downloads\letsencrypt-win-simple.v<IP_ADDRESS>\letsencrypt.exe
[DBUG] Options: Options {BaseUri="https://acme-v01.api.letsencrypt.org/", Test=False, Verbose=False, Renew=False, ForceRenewal=False, Plugin=null, SiteId=null,
ExcludeBindings=null, HideHttps=False, ManualHost=null, ManualTargetIsIIS=False, Validation=null, ValidationMode="http-01", WebRoot=null, ValidationSiteId=null
, Warmup=False, UserName=null, Password=null, AzureTenantId=null, AzureClientId=null, AzureSecret=null, AzureSubscriptionId=null, AzureResourceGroupName=null, D
nsCreateScript=null, DnsDeleteScript=null, KeepExisting=False, CentralSslStore=null, CertificateStore=null, Installation=[], InstallationSiteId=null, SSLPort=44
3, Script=null, ScriptParameters=null, CloseOnFinish=False, NoTaskScheduler=False, UseDefaultTaskUser=False, Cancel=False, AcceptTos=False, EmailAddress=null}
[DBUG] Config folder: C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org
[INFO] Let's Encrypt Windows Simple (LEWS)
[INFO] Software version 198.4.6605.15190 (RELEASE)
[INFO] IIS version 7.5
[INFO] ACME Server https://acme-v01.api.letsencrypt.org/
[INFO] Please report issues at https://github.com/Lone-Coder/letsencrypt-win-simple
[DBUG] Renewal period: 55
N: Create new certificate
M: Create new certificate with advanced options
L: List scheduled renewals
R: Renew scheduled
S: Renew specific
A: Renew all
V: Revoke certificate
C: Cancel scheduled renewal
X: Cancel all scheduled renewals
Q: Quit
Please choose from the menu: m
[INFO] Running in Advanced mode
1: Single binding of an IIS site
2: SAN certificate for all bindings of an IIS site
3: SAN certificate for all bindings of multiple IIS sites
4: Manually input host names
C: Cancel
Which kind of certificate would you like to create?: 3
[DBUG] Scanning IIS sites
[INFO] No valid hosts found for SBS SharePoint.
[INFO] No valid hosts found for SharePoint Central Administration v4.
[INFO] No valid hosts found for SharePoint Web Services.
[INFO] No valid hosts found for WSUS-Verwaltung.
1312694709: Companyweb (1 bindings) [@C:\inetpub\wwwroot\wss\VirtualDirectories\Companyweb80]
1: Default Web Site (4 bindings) [@C:\inetpub\wwwroot]
7: Mangaard.de (1 bindings) [@C:\Web-Hosting\www.mangaard.de]
2: SBS Client Deployment Applications (2 bindings) [@C:\Program Files\Windows Small Business Server\Bin\webapp\ClientDeployment]
6: www.magneticpower.de (3 bindings) [@C:\Web-Hosting\www.magneticpower.de]
4: www.Mangaard.ch (3 bindings) [@C:\Web-Hosting\www.Mangaard.ch]
5: www.Mangaard-Physio.de (3 bindings) [@C:\Web-Hosting\www.Mangaard-Physio.de]
Enter a comma separated list of site IDs, or 'S' to run for all sites: 1,4,5,6,7

mangaard-informatik.de
www.mangaard-informatik.de
remote.mangaard-informatik.de
mail.mangaard-informatik.de
www.mangaard.ch
mangaard.ch
mail.mangaard.ch
www.mangaard-physio.de
mangaard-physio.de
mail.mangaard-physio.de
www.magneticpower.de
magneticpower.de
mail.magneticpower.de
mangaard.de

Press enter to include all listed hosts, or type a comma-separated lists of exclusions:
[INFO] Plugin IISSites generated target [IISSites] 1,4,5,6,7 [14 bindings - mangaard-informatik.de, ...]
1: [dns-01] Azure DNS
2: [dns-01] Run external program/script to create and update records
3: [http-01] Create temporary application in IIS
4: [http-01] Save file on local (network) path
5: [http-01] Upload verification file to FTP(S) server
6: [http-01] Self-host verification files (recommended)
7: [http-01] Upload verification file to WebDav path
C: Cancel
How would you like to validate this certificate?: 6
1: Create or update IIS bindings
2: Run external script
3: Do not run any installation steps
C: Cancel
Which installer should run for the certificate?: 3
[DBUG] Scanning IIS sites
[DBUG] Loading signer from C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org\Signer
[DBUG] Getting AcmeServerDirectory
[DBUG] Send GET request to https://acme-v01.api.letsencrypt.org/directory
[DBUG] Loading registration from C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org\Registration
[INFO] Authorize identifier: mangaard-informatik.de
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Cached authorization result: valid
[INFO] Authorize identifier: www.mangaard-informatik.de
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Cached authorization result: valid
[INFO] Authorize identifier: remote.mangaard-informatik.de
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Cached authorization result: valid
[INFO] Authorize identifier: mail.mangaard-informatik.de
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Cached authorization result: valid
[INFO] Authorize identifier: mangaard.de
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Cached authorization result: valid
[INFO] Authorize identifier: www.magneticpower.de
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Cached authorization result: valid
[INFO] Authorize identifier: magneticpower.de
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Cached authorization result: valid
[INFO] Authorize identifier: mail.magneticpower.de
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Cached authorization result: valid
[INFO] Authorize identifier: www.mangaard.ch
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Cached authorization result: valid
[INFO] Authorize identifier: mangaard.ch
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Cached authorization result: valid
[INFO] Authorize identifier: mail.mangaard.ch
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Cached authorization result: valid
[INFO] Authorize identifier: www.mangaard-physio.de
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Cached authorization result: valid
[INFO] Authorize identifier: mangaard-physio.de
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Cached authorization result: valid
[INFO] Authorize identifier: mail.mangaard-physio.de
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Cached authorization result: valid
[DBUG] Certificate folder: C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org
[DBUG] Certificate store: My
[DBUG] RSAKeyBits: 2048
[INFO] Requesting certificate 1,4,5,6,7 2018.2.10 5:41:52
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-cert
[INFO] Saving certificate to C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org
[EROR] Create certificate failed
N: Create new certificate
M: Create new certificate with advanced options
L: List scheduled renewals
R: Renew scheduled
S: Renew specific
A: Renew all
V: Revoke certificate
C: Cancel scheduled renewal
X: Cancel all scheduled renewals
Q: Quit
Please choose from the menu:
Client version: letsencrypt-win-simple.v<IP_ADDRESS>
Windows version: Small Business Server 2011 Standard
Relevant part of log file:
what am I dooing wrong?
Using the Client "Certify The Web" I get all the Certificates installed, but this is not useable in IIS 7.5 - he I Need a SAN Certificate.

Looking at the source code and your log, this seems to fail during the conversion of the private key to the Microsoft RSA SChannel Cryptographic Provider, which may not be installed or disabled on your system. We might be able to diagnose that with more certainty if you post a log with --verbose.
I haven't encountered this problem before, but I'll make sure to add better error handling and a fallback to the default provider in the next release of LEWS. Thanks for reporting this bug!

Thanks for the answer,
"Microsoft RSA SChannel Cryptographic Provider" is installed and enabled - see copy of Result in Powershell:
PS C:\Users\Public\Downloads\letsencrypt-win-simple.v<IP_ADDRESS>\scripts> Get-CSP
Name                                                                                Type

Microsoft Base Cryptographic Provider v1.0                                                           RSA Full (Signature and Key Exchange)
Microsoft Base DSS and Diffie-Hellman Cryptographic Provider                                         DSS Signature with Diffie-Hellman Key Exchange
Microsoft Base DSS Cryptographic Provider                                                            DSS Signature
Microsoft Base Smart Card Crypto Provider                                                            RSA Full (Signature and Key Exchange)
Microsoft DH SChannel Cryptographic Provider                                                         Diffie-Hellman SChannel
Microsoft Enhanced Cryptographic Provider v1.0                                                       RSA Full (Signature and Key Exchange)
Microsoft Enhanced DSS and Diffie-Hellman Cryptographic Provider                                     DSS Signature with Diffie-Hellman Key Exchange
Microsoft Enhanced RSA and AES Cryptographic Provider                                                RSA Full and AES
Microsoft RSA SChannel Cryptographic Provider                                                        RSA SChannel
Microsoft Strong Cryptographic Provider                                                              RSA Full (Signature and Key Exchange)
Maybee Process is interferred throuh installed Certsrv.
Log with --verbose
PS C:\Windows\system32> C:\Users\Public\Downloads\letsencrypt-win-simple.v<IP_ADDRESS>\letsencrypt.exe --test --verbose
[DBUG] Options: Options {BaseUri="https://acme-v01.api.letsencrypt.org/", Test=True, Verbose=True, Renew=False, ForceRenewal=False, Plugin=null, SiteId=null, ExcludeBindings=null, HideHttps=False, ManualHost=null,
ManualTargetIsIIS=False, Validation=null, ValidationMode="http-01", WebRoot=null, ValidationSiteId=null, Warmup=False, UserName=null, Password=null, AzureTenantId=null, AzureClientId=null, AzureSecret=null, AzureSub
scriptionId=null, AzureResourceGroupName=null, DnsCreateScript=null, DnsDeleteScript=null, KeepExisting=False, CentralSslStore=null, CertificateStore=null, Installation=[], InstallationSiteId=null, SSLPort=443, Scri
pt=null, ScriptParameters=null, CloseOnFinish=False, NoTaskScheduler=False, UseDefaultTaskUser=False, Cancel=False, AcceptTos=False, EmailAddress=null}
[DBUG] Test parameter set: https://acme-staging.api.letsencrypt.org/
[DBUG] Config folder: C:\ProgramData\letsencrypt-win-simple\httpsacme-staging.api.letsencrypt.org
[INFO] Let's Encrypt Windows Simple (LEWS)
[INFO] Software version 198.4.6605.15190 (RELEASE)
[INFO] IIS version 7.5
[INFO] ACME Server https://acme-staging.api.letsencrypt.org/
[INFO] Please report issues at https://github.com/Lone-Coder/letsencrypt-win-simple
[DBUG] Renewal period: 55
N: Create new certificate
M: Create new certificate with advanced options
L: List scheduled renewals
R: Renew scheduled
S: Renew specific
A: Renew all
V: Revoke certificate
C: Cancel scheduled renewal
X: Cancel all scheduled renewals
Q: Quit
Please choose from the menu: n
[INFO] Running in Simple mode
1: Single binding of an IIS site
2: SAN certificate for all bindings of an IIS site
3: SAN certificate for all bindings of multiple IIS sites
4: Manually input host names
C: Cancel
Which kind of certificate would you like to create?: 3
[DBUG] Scanning IIS sites
[INFO] No valid hosts found for SBS SharePoint.
[INFO] No valid hosts found for SharePoint Central Administration v4.
[INFO] No valid hosts found for SharePoint Web Services.
[INFO] No valid hosts found for WSUS-Verwaltung.
1312694709: Companyweb (1 bindings) [@C:\inetpub\wwwroot\wss\VirtualDirectories\Companyweb80]
1: Default Web Site (4 bindings) [@C:\inetpub\wwwroot]
7: Mangaard.de (1 bindings) [@C:\Web-Hosting\www.mangaard.de]
2: SBS Client Deployment Applications (2 bindings) [@C:\Program Files\Windows Small Business Server\Bin\webapp\ClientDeployment]
6: www.magneticpower.de (3 bindings) [@C:\Web-Hosting\www.magneticpower.de]
4: www.Mangaard.ch (3 bindings) [@C:\Web-Hosting\www.Mangaard.ch]
5: www.Mangaard-Physio.de (3 bindings) [@C:\Web-Hosting\www.Mangaard-Physio.de]
Enter a comma separated list of site IDs, or 'S' to run for all sites: 1,4,5,6,7

mangaard-informatik.de
www.mangaard-informatik.de
remote.mangaard-informatik.de
mail.mangaard-informatik.de
www.mangaard.ch
mangaard.ch
mail.mangaard.ch
www.mangaard-physio.de
mangaard-physio.de
mail.mangaard-physio.de
www.magneticpower.de
magneticpower.de
mail.magneticpower.de
mangaard.de

Press enter to include all listed hosts, or type a comma-separated lists of exclusions:
[INFO] Plugin IISSites generated target [IISSites] 1,4,5,6,7 [14 bindings - mangaard-informatik.de, ...]
[DBUG] Scanning IIS sites
[DBUG] Loading signer from C:\ProgramData\letsencrypt-win-simple\httpsacme-staging.api.letsencrypt.org\Signer
[DBUG] Getting AcmeServerDirectory
[DBUG] Send GET request to https://acme-staging.api.letsencrypt.org/directory
[DBUG] Loading registration from C:\ProgramData\letsencrypt-win-simple\httpsacme-staging.api.letsencrypt.org\Registration
[INFO] Authorize identifier: mangaard-informatik.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing mangaard-informatik.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://mangaard-informatik.de/.well-known/acme-challenge/h-rYk4Fg5TA8odc9MNitk8CtHfequNX0t4wC--JQN_Q
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/spkhOH-HsMUPVVqJFkSdrkkyl_RIed5WjBXICCz2E5E/92207937
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: www.mangaard-informatik.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing www.mangaard-informatik.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://www.mangaard-informatik.de/.well-known/acme-challenge/ueoxUUGYUpUqR7KZGJDXcM1yShAd3D6W_1cXhXI-0k8
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/EWX6mxP3HfX6-oFKwATNMENW8ZKjEHD3mcCzYclRtQQ/92208029
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: remote.mangaard-informatik.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing remote.mangaard-informatik.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://remote.mangaard-informatik.de/.well-known/acme-challenge/qCIEdevn_JbzreHr26s_kCLBgycoAYhAuPv1zXcb4KI
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/OPWcHTzD7qZ4OlaF4yYvx2R8KnWvUxI7SaZpbZTIVUc/92208924
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: mail.mangaard-informatik.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing mail.mangaard-informatik.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://mail.mangaard-informatik.de/.well-known/acme-challenge/0kflFUAv9CGRFQfqZs8mF7DoHSXlxqAm-uJyCywnDqU
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/vQq51Ccz7aJIUK_CaBIjfl3il86nX_xE7DB3kirW1Bc/92209054
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: mangaard.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing mangaard.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://mangaard.de/.well-known/acme-challenge/q8gkqNnM7tXxcmP6bplhyjO6VMYVsWOqFWHDlrlTxt8
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/3C7q3c74DlkuUcPoMgEIiOgqp288Nq9vhABoFQpb8B8/98124681
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: www.magneticpower.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing www.magneticpower.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://www.magneticpower.de/.well-known/acme-challenge/hdlFdxlkzFvwBk_a1aVHBUhHKmI2dIqCI2wMRoNjZ4c
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/lAabum5OEeEvCpHDFCuo-KbT5qcVGt6PKtPNjx6Y9R4/92209108
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: magneticpower.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing magneticpower.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://magneticpower.de/.well-known/acme-challenge/JDcr_A51x6-4Kl6_ceCphZOKnsqwdI2pCLhtTCy8c8E
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/rtzwlhTz4q-gUgJ14hmfpUfM4SCASrl2fqF6TxsrDRg/92391744
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: mail.magneticpower.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing mail.magneticpower.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://mail.magneticpower.de/.well-known/acme-challenge/MQaj2rcr8QICYqt7hDcVYs-V8z0RDN4Q8Se8-bHTbDE
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/OlnVSRbCOsWfJetfmB2nm3iKDbVJXGlOu2gnlzqeRsM/92391784
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: www.mangaard.ch
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing www.mangaard.ch using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://www.mangaard.ch/.well-known/acme-challenge/VYgj-T5NQgJ3xYWNKVBvFhDwwfXJ3lorzfkd8hDB_6c
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/z19g4ZgriBA-MxmfYpY2rs6o-qyd3llbcR_EnCsWeuE/92209150
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: mangaard.ch
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing mangaard.ch using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://mangaard.ch/.well-known/acme-challenge/IWV3qamjuMUxe5Ctu2ntVmmVhuZzPIbhVLIssUkalBY
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/vxeJUSwMsIx-Pmzns7-96fOYk9SMdGiA0XM6gNRtwXw/92391569
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: mail.mangaard.ch
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing mail.mangaard.ch using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://mail.mangaard.ch/.well-known/acme-challenge/WvGFkdJDEn_ci8iMhUHy0yM2xyUSOqL77_GLGeegcXc
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/-5wPZxRODAhoSZbRDC5dLTZi7B1Ciw-ozOj8744F2s8/92391602
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: www.mangaard-physio.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing www.mangaard-physio.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://www.mangaard-physio.de/.well-known/acme-challenge/UGgL_AwyJWgiWTLTQQFpB5j8hbvXCEwrj5S8NEMz9HA
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/_u8y6AzVLY0EoV5iNsqJJZDGmGXoGEcpaj0C4zNaP9E/92209191
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: mangaard-physio.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing mangaard-physio.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://mangaard-physio.de/.well-known/acme-challenge/f4aUk-1bHt01nGLHFYYwZvxJnMr9d75bbs0SsFAXqjg
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/subV1_lpPgtts8i35g1Sk6S2FQgBs-QYrhVfIP33yCg/92209214
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: mail.mangaard-physio.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing mail.mangaard-physio.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://mail.mangaard-physio.de/.well-known/acme-challenge/xoAQumc7sdr_pa5lS9UT4DYbXwqM3y9mVHJpNHuA-dk
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/XU6dN-UA1CfWoCCHYWGMNk3Tfbqk_1DqtFRkNavipc4/92209262
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[DBUG] Certificate folder: C:\ProgramData\letsencrypt-win-simple\httpsacme-staging.api.letsencrypt.org
[DBUG] Certificate store: My
[DBUG] RSAKeyBits: 2048
[INFO] Requesting certificate 1,4,5,6,7 2018.2.11 4:15:23
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-cert
[INFO] Saving certificate to C:\ProgramData\letsencrypt-win-simple\httpsacme-staging.api.letsencrypt.org
[EROR] Create certificate failed
N: Create new certificate
M: Create new certificate with advanced options
L: List scheduled renewals
R: Renew scheduled
S: Renew specific
A: Renew all
V: Revoke certificate
C: Cancel scheduled renewal
X: Cancel all scheduled renewals
Q: Quit
Please choose from the menu:

This is odd, the logger seems to be acting up. I don't see any of the [VERB] messages in your log. Also it shows a debug message which I don't see in my builds.
Would you mind trying this build to see if it gives you a proper error message?
letsencrypt.zip

After Unzipping your File and running it i bekame a Message about missing files.
I copied them from Version: <IP_ADDRESS>
and Ran your version.
Essensial is the Warning at the end:
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/sjuaYOIj7xezJas22lX1CbF4ftOK_OBMEOQEYl4docc/101105800
[DBUG] Refreshing authorization
[DBUG] Send GET request to https://acme-staging.api.letsencrypt.org/acme/authz/sjuaYOIj7xezJas22lX1CbF4ftOK_OBMEOQEYl4docc
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[DBUG] Certificate folder: C:\ProgramData\letsencrypt-win-simple\httpsacme-staging.api.letsencrypt.org
[DBUG] Certificate store: My
[DBUG] RSAKeyBits: 2048
[INFO] Requesting certificate 1,4,5,6,7 2018.2.13 12:39:56
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-cert
[INFO] Saving certificate to C:\ProgramData\letsencrypt-win-simple\httpsacme-staging.api.letsencrypt.org
[WARN] Error converting private key to Microsoft RSA SChannel Cryptographic Provider, which means it might not be usable for Exchange.
[DBUG] Set private key exportable
[--test] Do you want to install the certificate? (y/n): - no
The debug messages commes because of setting “” in the “letsencrypt.exe.config”
You find the complete Log in attached file.

Diese Nachricht wurde auf Viren überprüft.
This mail was checked for viruses.
Ce mail a été vérifié.

E-Mail Disclaimer
Der Inhalt dieser E-Mail ist ausschliesslich fuer den bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte, dass jede Form der Kenntnisnahme, Veroeffentlichung, Vervielfaeltigung oder Weitergabe des Inhalts dieser E-Mail unzulaessig ist. Wir bitten Sie, sich in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen.
The information contained in this email is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any form of disclosure, reproduction, distribution or any action taken or refrained from in reliance on it, is prohibited and may be unlawful. Please notify the sender immediately.
L'information contenue dans cet email est prévue seulement pour le destinataire. L'Access à cet email par n'importe qui est autrement non autorisé. Si vous n'êtes pas le destinataire prévu, aucune forme de révélation, reproduction, distribution ou aucune mesure prise ou abstenue à dans la confiance là-dessus, est interdit et peut être illégal. Veuillez informer l'expéditeur immédiatement.

Von: Wouter Tinus<EMAIL_ADDRESS>Gesendet: Montag, 12. Februar 2018 18:41
An: Lone-Coder/letsencrypt-win-simple<EMAIL_ADDRESS>Cc: Mangaard-Informatik<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Betreff: Re: [Lone-Coder/letsencrypt-win-simple] Create certificate failed in SBS2012 (all authorization result: valid) (#741)
This is odd, the logger seems to be acting up. I don't see any of the [VERB] messages in your log. Also it shows a debug message which I don't see in my builds.
Would you mind trying this build to see if it gives you a proper error message?
letsencrypt.ziphttps://github.com/Lone-Coder/letsencrypt-win-simple/files/1717198/letsencrypt.zip
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Lone-Coder/letsencrypt-win-simple/issues/741#issuecomment-365001519, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATyjAjIVzUK_5ahwZMzZtZBkRmMJFGTtks5tUHefgaJpZM4SBA8m.
C:\inetpub\AdminScripts>C:\Users\Public\Downloads__Wouter_Tinus_Build_letsencrypt\letsencrypt.exe --test --verbose
[DBUG] Options: Options {BaseUri="https://acme-v01.api.letsencrypt.org/", Test=True, Verbose=True, Renew=False, ForceRenewal=False, Plugin=null, SiteId=null, ExcludeBindings=null, Hide
Https=False, ManualHost=null, ManualTargetIsIIS=False, Validation=null, ValidationMode="http-01", WebRoot=null, ValidationPort=null, ValidationSiteId=null, Warmup=False, UserName=null,
Password=null, AzureTenantId=null, AzureClientId=null, AzureSecret=null, AzureSubscriptionId=null, AzureResourceGroupName=null, DnsCreateScript=null, DnsDeleteScript=null, KeepExisting=
False, CentralSslStore=null, CertificateStore=null, Installation=[], InstallationSiteId=null, SSLPort=443, Script=null, ScriptParameters=null, CloseOnFinish=False, NoTaskScheduler=False
, UseDefaultTaskUser=False, Cancel=False, AcceptTos=False, EmailAddress=null}
[DBUG] Test parameter set: https://acme-staging.api.letsencrypt.org/
[DBUG] Config folder: C:\ProgramData\letsencrypt-win-simple\httpsacme-staging.api.letsencrypt.org
[INFO] Let's Encrypt Windows Simple (LEWS)
[INFO] Software version 198.4.6617.33472 (DEBUG)
[INFO] IIS version 7.5
[INFO] ACME Server https://acme-staging.api.letsencrypt.org/
[INFO] Please report issues at https://github.com/Lone-Coder/letsencrypt-win-simple
[DBUG] Renewal period: 55
N: Create new certificate
M: Create new certificate with advanced options
L: List scheduled renewals
R: Renew scheduled
S: Renew specific
A: Renew all
V: Revoke certificate
C: Cancel scheduled renewal
X: Cancel all scheduled renewals
Q: Quit
Please choose from the menu: m
[INFO] Running in Advanced mode
1: Single binding of an IIS site
2: SAN certificate for all bindings of an IIS site
3: SAN certificate for all bindings of multiple IIS sites
4: Manually input host names
C: Cancel
Which kind of certificate would you like to create?: 3
[DBUG] Scanning IIS sites
[INFO] No valid hosts found for SBS SharePoint.
[INFO] No valid hosts found for SharePoint Central Administration v4.
[INFO] No valid hosts found for SharePoint Web Services.
[INFO] No valid hosts found for WSUS-Verwaltung.
1312694709: Companyweb (1 bindings) [@C:\inetpub\wwwroot\wss\VirtualDirectories\Companyweb80]
1: Default Web Site (4 bindings) [@C:\inetpub\wwwroot]
7: Mangaard.de (1 bindings) [@C:\Web-Hosting\www.mangaard.de]
2: SBS Client Deployment Applications (2 bindings) [@C:\Program Files\Windows Small Business Server\Bin\webapp\ClientDeployment]
6: www.magneticpower.de (3 bindings) [@C:\Web-Hosting\www.magneticpower.de]
4: www.Mangaard.ch (3 bindings) [@C:\Web-Hosting\www.Mangaard.ch]
5: www.Mangaard-Physio.de (3 bindings) [@C:\Web-Hosting\www.Mangaard-Physio.de]
Enter a comma separated list of site IDs, or 'S' to run for all sites: 1,4,5,6,7

mangaard-informatik.de
www.mangaard-informatik.de
remote.mangaard-informatik.de
mail.mangaard-informatik.de
www.mangaard.ch
mangaard.ch
mail.mangaard.ch
www.mangaard-physio.de
mangaard-physio.de
mail.mangaard-physio.de
www.magneticpower.de
magneticpower.de
mail.magneticpower.de
mangaard.de

Press enter to include all listed hosts, or type a comma-separated lists of exclusions:
[INFO] Plugin IISSites generated target [IISSites] 1,4,5,6,7 [14 bindings - mangaard-informatik.de, ...]
1: [dns-01] Azure DNS
2: [dns-01] Run external program/script to create and update records
3: [http-01] Create temporary application in IIS
4: [http-01] Save file on local (network) path
5: [http-01] Upload verification file to FTP(S) server
6: [http-01] Self-host verification files (recommended)
7: [http-01] Upload verification file to WebDav path
C: Cancel
How would you like to validate this certificate?: 6
1: Create or update IIS bindings
2: Run external script
3: Do not run any installation steps
C: Cancel
Which installer should run for the certificate?: 3
[DBUG] Scanning IIS sites
[DBUG] Loading signer from C:\ProgramData\letsencrypt-win-simple\httpsacme-staging.api.letsencrypt.org\Signer
[DBUG] Getting AcmeServerDirectory
[DBUG] Send GET request to https://acme-staging.api.letsencrypt.org/directory
[DBUG] Loading registration from C:\ProgramData\letsencrypt-win-simple\httpsacme-staging.api.letsencrypt.org\Registration
[INFO] Authorize identifier: mangaard-informatik.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing mangaard-informatik.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://mangaard-informatik.de/.well-known/acme-challenge/pq3o2aVVKiWbG1EQXlJGvCZCHkalRnvU-Zg7JB89b-E
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/K1j9vAPnm9gVu77xC5P745uV9IZhsC4HUK4vrQLBiL4/101104206
[DBUG] Refreshing authorization
[DBUG] Send GET request to https://acme-staging.api.letsencrypt.org/acme/authz/K1j9vAPnm9gVu77xC5P745uV9IZhsC4HUK4vrQLBiL4
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: www.mangaard-informatik.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing www.mangaard-informatik.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://www.mangaard-informatik.de/.well-known/acme-challenge/-zR6fxEfRBgZDdYha3ldFDrL0UcqwUJpzNulYZ0Msvg
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/Igh8zikyuRnmyTPri0SNr1V-5sj30cWEkp4hI-qm-d0/101104906
[DBUG] Refreshing authorization
[DBUG] Send GET request to https://acme-staging.api.letsencrypt.org/acme/authz/Igh8zikyuRnmyTPri0SNr1V-5sj30cWEkp4hI-qm-d0
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: remote.mangaard-informatik.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing remote.mangaard-informatik.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://remote.mangaard-informatik.de/.well-known/acme-challenge/v9PG16GMJ12NIGwyPGFeiSRMC2bKzGlS9tGeTE3KXl8
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/jjqeLO1HdUrczJ1rb8tvytUn6F8WnJPfqEG1ecg0ZiI/101104938
[DBUG] Refreshing authorization
[DBUG] Send GET request to https://acme-staging.api.letsencrypt.org/acme/authz/jjqeLO1HdUrczJ1rb8tvytUn6F8WnJPfqEG1ecg0ZiI
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: mail.mangaard-informatik.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing mail.mangaard-informatik.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://mail.mangaard-informatik.de/.well-known/acme-challenge/HmgnCSz_o6RIWpqhUphsP3dubctxbi_PKDVMzdihz3g
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/6Jgq_D0Wns3P9AOAJB64GkhNOlAtgovyt4S20CHFDks/101104962
[DBUG] Refreshing authorization
[DBUG] Send GET request to https://acme-staging.api.letsencrypt.org/acme/authz/6Jgq_D0Wns3P9AOAJB64GkhNOlAtgovyt4S20CHFDks
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: mangaard.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing mangaard.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://mangaard.de/.well-known/acme-challenge/q8gkqNnM7tXxcmP6bplhyjO6VMYVsWOqFWHDlrlTxt8
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/3C7q3c74DlkuUcPoMgEIiOgqp288Nq9vhABoFQpb8B8/98124681
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: www.magneticpower.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing www.magneticpower.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://www.magneticpower.de/.well-known/acme-challenge/ToBezvdeDUkeg1ZBIO9pLDGWQ3xN_da_veWk8q2zm_U
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/IXLwOGVhqRBBajd_knS7Mp2xRc6XyxZyqhyknl-QxYM/101105009
[DBUG] Refreshing authorization
[DBUG] Send GET request to https://acme-staging.api.letsencrypt.org/acme/authz/IXLwOGVhqRBBajd_knS7Mp2xRc6XyxZyqhyknl-QxYM
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: magneticpower.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing magneticpower.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://magneticpower.de/.well-known/acme-challenge/msjEUxmMHnVQvbqD--FrCYAw2DGLKDupZzFY7iPWwh8
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/rEmM3w3djdyDRg-xHf1yDDV2VHI8vR7ZmF9duQjeP_8/101105049
[DBUG] Refreshing authorization
[DBUG] Send GET request to https://acme-staging.api.letsencrypt.org/acme/authz/rEmM3w3djdyDRg-xHf1yDDV2VHI8vR7ZmF9duQjeP_8
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: mail.magneticpower.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing mail.magneticpower.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://mail.magneticpower.de/.well-known/acme-challenge/7IGKz_CJae2K8MGG2ekdUm9RLcvEOaqXpU9dF4LzVM0
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/QiZu2HUTUDnYXUsmYkREi_5R-gxxXtPtF6H-lOCr2yA/101105513
[DBUG] Refreshing authorization
[DBUG] Send GET request to https://acme-staging.api.letsencrypt.org/acme/authz/QiZu2HUTUDnYXUsmYkREi_5R-gxxXtPtF6H-lOCr2yA
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: www.mangaard.ch
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing www.mangaard.ch using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://www.mangaard.ch/.well-known/acme-challenge/-fUDR0yRURm_NRcgRz7q_7uL5kx2mfyaO4An0-f2hr8
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/5lBqc4FUl0qm0dWlYalJ4AadIj39rfFSwLrzNccOjl8/101105544
[DBUG] Refreshing authorization
[DBUG] Send GET request to https://acme-staging.api.letsencrypt.org/acme/authz/5lBqc4FUl0qm0dWlYalJ4AadIj39rfFSwLrzNccOjl8
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: mangaard.ch
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing mangaard.ch using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://mangaard.ch/.well-known/acme-challenge/GZAKcLraTKw3XM5v2rJVRyOPtOFAJD_QWfPSfETkji8
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/QTxO0lzTPq90nDGrVYS5zFxxOigpawzErL16ffjtBYk/101105586
[DBUG] Refreshing authorization
[DBUG] Send GET request to https://acme-staging.api.letsencrypt.org/acme/authz/QTxO0lzTPq90nDGrVYS5zFxxOigpawzErL16ffjtBYk
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: mail.mangaard.ch
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing mail.mangaard.ch using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://mail.mangaard.ch/.well-known/acme-challenge/ekeZ4BsI-Geor1d5MtV8AWmgcgnOK-BnzZb3uea3W6Y
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/yxXlq5S0hSLNTJm4VnmP86haaz6hIwABnn9iJUOtZw8/101105673
[DBUG] Refreshing authorization
[DBUG] Send GET request to https://acme-staging.api.letsencrypt.org/acme/authz/yxXlq5S0hSLNTJm4VnmP86haaz6hIwABnn9iJUOtZw8
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: www.mangaard-physio.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing www.mangaard-physio.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://www.mangaard-physio.de/.well-known/acme-challenge/nuUQFQlmFIj9bH7-TWeDQiYl7FsTDpQqp8fRB9_Pj5Y
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/7LJFpP-NtpF5Qp8lFm4epH-wRU4m5rcHDrQGRYIegXg/101105731
[DBUG] Refreshing authorization
[DBUG] Send GET request to https://acme-staging.api.letsencrypt.org/acme/authz/7LJFpP-NtpF5Qp8lFm4epH-wRU4m5rcHDrQGRYIegXg
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: mangaard-physio.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing mangaard-physio.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://mangaard-physio.de/.well-known/acme-challenge/srdcIx1SU-nwi3w6R2jbKvMmWVY-laZZeJ5h83eZMw4
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/oHBMHD4D8A1_vhAIDGmp0tco5hHcs4h-pahEWBKp8ZE/101105767
[DBUG] Refreshing authorization
[DBUG] Send GET request to https://acme-staging.api.letsencrypt.org/acme/authz/oHBMHD4D8A1_vhAIDGmp0tco5hHcs4h-pahEWBKp8ZE
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[INFO] Authorize identifier: mail.mangaard-physio.de
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing mail.mangaard-physio.de using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://mail.mangaard-physio.de/.well-known/acme-challenge/IG8KB4bAy0m-FWd0Mndz_OsciCbZLgdt7QrS3nLBtgg
[--test] Try in default browser? (y/n): - yes
Press enter to continue...  [DBUG] Submitting answer
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/challenge/sjuaYOIj7xezJas22lX1CbF4ftOK_OBMEOQEYl4docc/101105800
[DBUG] Refreshing authorization
[DBUG] Send GET request to https://acme-staging.api.letsencrypt.org/acme/authz/sjuaYOIj7xezJas22lX1CbF4ftOK_OBMEOQEYl4docc
[INFO] Authorization result: valid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[DBUG] Certificate folder: C:\ProgramData\letsencrypt-win-simple\httpsacme-staging.api.letsencrypt.org
[DBUG] Certificate store: My
[DBUG] RSAKeyBits: 2048
[INFO] Requesting certificate 1,4,5,6,7 2018.2.13 12:39:56
[DBUG] Send POST request to https://acme-staging.api.letsencrypt.org/acme/new-cert
[INFO] Saving certificate to C:\ProgramData\letsencrypt-win-simple\httpsacme-staging.api.letsencrypt.org
[WARN] Error converting private key to Microsoft RSA SChannel Cryptographic Provider, which means it might not be usable for Exchange.
[DBUG] Set private key exportable
[--test] Do you want to install the certificate? (y/n): - no
N: Create new certificate
M: Create new certificate with advanced options
L: List scheduled renewals
R: Renew scheduled
S: Renew specific
A: Renew all
V: Revoke certificate
C: Cancel scheduled renewal
X: Cancel all scheduled renewals
Q: Quit
Please choose from the menu:

So the error is where I expected it to be, but at least it's handled with a warning now, instead of it being fatal. I recommend you to use that build until the next official release comes out.

First of all i would check if it is SBS2012 OR 2011...
The issuer ignored the warnings that .net framework 4.6.1 is NOT supported on a SBS an breaks many other stuff.
(and according to his mail signature, he seems to be a neighbor :-P )

The error is warned about but no longer fatal in the latest release.


msmtp: 1.8.19 -> 1.8.20

Description of changes

Bump msmtp version to 1.8.20.
This version supports the new allow_from_override configuration option.
I had to make a small change to the patch to get it to build, and I'm using this build to send mail successfully
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 177452 run on x86_64-linux 1

1 package built:

msmtp


Bug fix in Sagemaker plugin

TL;DR
Please replace this text with a description of what this PR accomplishes.
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[ ] Smoke tested
[x] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
How did you fix the bug, make the feature etc. Link to any design docs etc
Tracking Issue
https://github.com/lyft/flyte/issues/
Follow-up issue
NA
OR
https://github.com/lyft/flyte/issues/

🔨

Codecov Report

Merging #110 into master will decrease coverage by 0.05%.
The diff coverage is 20.00%.

@@            Coverage Diff             @@
##           master     #110      +/-   ##
==========================================
- Coverage   55.51%   55.45%   -0.06%
==========================================
  Files          99       99
  Lines        5910     5916       +6
==========================================
  Hits         3281     3281
- Misses       2318     2324       +6
  Partials      311      311

Impacted Files
Coverage Δ

go/tasks/plugins/k8s/sagemaker/config/config.go
0.00% <ø> (ø)

go/tasks/plugins/k8s/sagemaker/sagemaker.go
4.35% <0.00%> (-0.05%)
:arrow_down:

go/tasks/plugins/k8s/sagemaker/utils.go
49.67% <33.33%> (-0.66%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8dd7a24...870df76. Read the comment docs.

This PR is merged in order to fix an important bug in a timely manner. Extra unit tests are added but we haven't reached the coverage goal. Will try to reach the goal in a separate PR.


Investigate a way to eager load recommendable models in development

In test and production, models are automatically eager loaded when the application boots. This is good, as acts_as_recommendable appends the class's constant into the Recommendable.recommendable_classes array for use internally. In development, however, eager loading can cause too much slowdown in requests. This means that, in the development environment, these class constants have to be referenced manually before attempting to get recommendations. If possible, I need to find a way to either:

Eager load only models that act_as_recommendable and alter the Railtie accordingly
Figure out a better way to internally keep track of classes that act_as_recommendable

Just noting a possibility: require models that act_as_recommendable to be moved to a subdirectory of app/models... app/models/recommendable/*.rb and then eager load files in this directory in development or if app.config.cache_classes == false.
Dislike.

Fixed in 0.1.4


JavaScript Standard Style

[ ] Stick to the JavaScript Standard Style
[ ] Put this nice badge in the README.md.
[ ] Update our Style Guidelines.

Keep in mind that that guide enforces no semicolons, we should update ALL our code to be able to stick to it.

+1

We´ll enforce with houndci


Figure out how to best Integration Test the locale changes

Thanks for creating an issue! Please fill out this form so we can be sure to have all the information we need, and to minimize back and forth.

What are we trying to do?
Now that we are introducing another locale (Spanish) in #1526 and follow on work, figure out the best way to test this.

What feature or behavior is this required for?
Essentially just figuring out that all the Spanish translation work, stays good!

How could we solve this issue? (Not knowing is okay!)
In theory you could rerun all tests with the locale changed, but I'm not sure if that's correct.

Anything else?
Fuerza!

One option is relying on i18n keys.
I18n.t('key.for.something') can be used by both capybara helpers and matchers
For example
click_link 'Lock account'  -> click_link 'I18n.t("lock_account")'
assert_text 'Build your call list' -> assert_text 'I18n.t("build_call_list")'
of course the downside now is you have to change your tests whenever you I18n keys change.

I think I'd be good with the 'prove the locale switch works' method -- something like:
visit authenticated_root_path, params: { locale: 'es' }
assert has_content? 'Welcome to DARIA'
click_link 'Spanish mode'
refute has_content? 'Welcome to DARIA'
assert has_content? 'Bienvenidos a DARIA'

I don't think we need to exhaustively test every key, or key values. I'm mostly interested in 'when we smash the button the language switches'. But I am def open to hearing otherwise. @Kevin-Wei @DarthHater yr thoughts?

@colinxfleming I am 100% on board with that, not because it reduces work load, just because I think it is about as much as I think you SHOULD test. Keys can change quickly, it's really only important to test them if it's like mission critical that something says an exact thing.

I didn't mean that it is critical that every key is tested. What I'm recommending is a path forward for areas that have existing view tests that rely directly on text in the test that will be translated.
I also agree that keys should rarely change and its not necessarily a bad thing to add that kind of overhead. It could reveal to us where we are over-testing text on the view. Therefore we can remove those kinds of text validations. Only leaving the ones that @DarthHater said are "mission critical"

I'm not super concerned about this - i18n tools that @lomky adopted into our test suite make it so we don't have to be too scared of this, in my opinion. I'm closing unless @DarthHater or @Kevin-Wei have a strong opinion and/or a path to doing this.


Upgrade xml2js to v0.5.0

Consuming dependencies:

[x] https://www.npmjs.com/package/@azure/ms-rest-js (Updated to v2.6.6)
[ ] https://www.npmjs.com/package/@azure/core-http (update not available)
[x] https://www.npmjs.com/package/vsce  > Migrated to @vscode/vsce

[ ] https://www.npmjs.com/package/@vscode/vsce (update not available)

[x] https://www.npmjs.com/package/azure-storage > Migrated to @azure/storage-blob

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.005%) to 41.684%

Files with Coverage Reduction
New Missed Lines
%

extensions/sql-database-projects/src/common/httpClient.ts
1
66.18%

extensions/sql-database-projects/src/dialogs/publishDatabaseDialog.ts
2
50.74%

Totals

Change from base Build<PHONE_NUMBER>:
-0.005%

Covered Lines:
30348

Relevant Lines:
67407

💛  - Coveralls

Are you done making changes? If not, could you put this in a draft state until it's ready for review?


Support partial deserialization

Imagine there's a structure in Js, which I know partly, but some things of it are too dynamic to be mapped to types.
Let's say in js something would look like this:
{
    dynamicData: {  someData: "whatever" },
    staticData: { someOtherData: "any" }
}

From rust perspective I would like to look at it like this:

#[derive(Deserialize)]
struct MyStaticData {
    staticData: String
}

#[derive(Deserialize)]
struct MyData {
    dynamicData: JsValue,
    staticData: MyStaticData,
}

So in this example, structure of MyStaticData is known beforehand, but for field dynamicData we don't know how will it look like at compile time, and so we'd like to just keep there JsValue without changes (and if possible, without copying).
However this will not compile, because Deserialize trait required for from_value cannot be derived for structure with JsValue, because JsValue does not implement it.
I tried to implement it myself  by wrapping JsValue inside custom RawJsValue  like that :
struct RawJsValue {
    value: JsValue
}

impl<'de> Deserialize<'de> for RawJsValue {
...

However I'm not sure how exactly to implement Deserialize. I figure that if serde::Deserializer would be of type serde_wasm_bindgen::Deserializer , then it's just about rewrapping value, but I don't understand how to cast deserializer to that structure from generic type. Any ideas?

Unfortunately, this isn't possible with Serde. Due to abstraction it uses, the precise types used by specific deserializer - in this case JsValue - are lost in translation.
You can deserialize into a HashMap or custom enum if you know potential shape of your expected value, but you can't preserve JsValue itself.

For anyone coming here, this is possible now on Git main (soon to be released) via #40.


Get rid of Che Rest API sidecar

Che Theia already use k8s api to get everything needed so it's time to get rid of Che Rest API sidecar on DevWorkspace Operator level.

I have some related WIP changes I need to push to make this easier

Both PRs are merged, closing the issue.


college_2

Hello,
Thanks for the great work!
I might have missed this but I noticed "college_2" is used in a lot of prompt makers. What's the reason behind it?
Thanks!

Never mind I believe it's used for few-shot schema links.


Create Dockerfile for building a container image

I would like to help  @ps-89 , but as I am a beginner I dont know what exactly to do . can you give more proper directions and instructions

@ryuusama09 You can refer to https://dev.to/karanpratapsingh/dockerize-your-react-app-4j2e
We need to do something similar. Creating a Dockerfile for the project. Our project is react-based, and we need to expose port 3000 in the container.

@ryuusama09 Welcome to the project :)
You can refer to https://dev.to/karanpratapsingh/dockerize-your-react-app-4j2e
We need to do something similar. Creating a Dockerfile for the project. Our project is react-based, and we need to expose port 3000 in the container. If you have further questions, feel free to ask in this same thread.

yes , according to this creating a dockerfile is not an issue but what all to write in it , can you guide me ?

@ryuusama09
The first Dockerfile example given in the article is good enough for our project too.
FROM node:14-alpine AS development
ENV NODE_ENV development
# Add a work directory
WORKDIR /app
# Cache and Install dependencies
COPY package.json .
COPY yarn.lock .
RUN yarn install
# Copy app files
COPY . .
# Expose port
EXPOSE 3000
# Start the app
CMD [ "yarn", "start" ]

This is in a more readable way, what the first example in the article does i.e
Use the base node alpine image
set the working directory in the container
copy current code in the working directory
copy yarn.lock and package.json to the working directory
yarn install
expose 3000 port
run the yarn start command

If you can make this more efficient, that'd be great too. You can add steps in the readme too, for running the project via Docker.

@ps-89 If the issue is still up for grabs, I would like to take it on. I have prior exp with Docker so that should come in handy

Assigned it to you @imabhinavagarwal.


Support existing RabbitMQ Celery Broker

Celery - and Airflow - supports Redis and RabbitMQ as a broker.
http://docs.celeryproject.org/en/latest/getting-started/first-steps-with-celery.html#choosing-a-broker
https://airflow.apache.org/howto/executor/use-celery.html#scaling-out-with-celery
Currently, the airflow-operator only supports Redis as a broker.


error coming on latest sdk dependancies

Caused by: java.lang.RuntimeException: org.gradle.api.reflect.ObjectInstantiationException: Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl.
Hello,
I have updated my project to gradle 8.5.0 and and using your plugin in our project.
lastest flutter version and dart version.
andorid sdk 34-35.
Please update the version for latest releases.
Thank you.

@vikasyadav2184  please check with git url.

Hello,
can you confirm when you release the new version on "flutter package" of this.

@vikasyadav2184 hi, im getting new error on git
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':flutter_native_contact_picker:verifyReleaseResources'.

A failure occurred while executing com.android.build.gradle.tasks.VerifyLibraryResourcesTask$Action
Android resource linking failed
ERROR:/home/khaled/Workspace/AMRServer/Flutter-UserClient/build/flutter_native_contact_picker/intermediates/merged_res/release/values/values.xml:194: AAPT: error: resource android:attr/lStar not found.

@vikasyadav2184  @khaled-0  try to use prerelease version.

Duplicate #17


Build Test Runner

This issue is part of the migration to v3. You can read full details about the various changes here.
In Exercism v3, one of the biggest changes is that we'll automatically check if a submitted solution passes all the tests.
We'll check this via a new, track-specific tool: the Test Runner. Each test runner is track-specific. When a new solution is submitted, we run the track's test runner, which outputs a JSON file that describes the test results.
The test runner must be able to run the tests suites of both Concept Exercises and Practice Exercises. Depending on the test runner implementation, this could mean having to update the Practice Exercises to the format expected by the test runner.
Goal
Build a test runner for your track according to the spec.
If you are building a test runner from scratch, we have a starting guide and a generic test runner that can be used as the base for the new test runner.
If a test runner has already been built for this track, please check if it works on both Concept Exercises and Practice Exercises.
It can be very useful to check how other tracks have implemented their test runner.
Tracking
https://github.com/exercism/v3-launch/issues/4

Test runner has been built, still need to check that it works on Concept and Practice Exercises.

I think this issue can be closed as there is a working version of the test runner. Note that the test runner itself can be improved, but that does not preclude this issue from being closed as test runner improvements can be handled in the test runner repo.


Feature request: node api w/ option to pass in graphql inputs manually

Hi one of the great benefits of https://www.npmjs.com/package/gql2ts is that it provides a (documented) programable api. I have my graphql schema split into several *.graphql files and id like to pass this in and write out to a flowtypes.js file with a node.js script.

I think a programmatic API would be great, but your use case currently isn't a particularly good fit for apollo-codegen. It generates query-specific types, so you'll need queries in addition to the schema.
Do you generate types for the schema because you're using this for a server implementation?

@martijnwalraven yeah you're right, ive settled on using this tool for generating client side types and  then in each of my microservices that my graphql service is exporting i define the types first there and import them to my graphql project to be type safe server side.


Add support for scan history (aggregated and rebased w/master)

This pull request is the rebased version of the multiple pull requests related to adding support for --scan-history. I am submitting this PR just so that @andreaswittig and/or @jschucht can double check that the rebase with master looks ok.

:+1:
Thanks for your support, @mtdowling.

Thanks for contributing!


[DEFECT] GA scrambleMutators Error

Thank you for the defect report

[X] I am using the latest version of RAVEN.
[X] I have read the Wiki.
[X] I have created a minimum, reproducible example
that demonstrates the defect.

Defect Description
In GA, scrambleMutator with onePointCrossover or twoPointsCrossover options do not work.
Steps to Reproduce
Run
C:\Users<UserID>\projects\raven\doc\workshop\optimizer\GeneticAlgorithms\Inputs\1_GA_MaxwRep.xml with proper changes in  node in  node. In  node, the type should be "scrambleMutator."
Expected Behavior
It should not have an error.
Screenshots and Input Files
No response
OS
Windows
OS Version
No response
Dependency Manager
CONDA
For Change Control Board: Issue Review

[x] Is it tagged with a type: defect or task?
[x] Is it tagged with a priority: critical, normal or minor?
[x] If it will impact requirements or requirements tests, is it tagged with requirements?
[x] If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

[x] If the issue is a defect, is the defect fixed?
[x] If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[x] If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[x] If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[x] If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

Issue checklist is good.