⚠ Bofrost.be has degraded performance

In e68df1c, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1017 ms

Resolved: Bofrost.be performance has improved in ed1baa6.


:0: error: unable to load standard library for target 'x86_64-unknown-windows-msvc'

I'm using Windows 10 2004. I have downloaded everything for Visual Studio 2019. I already had Visual Studio 2017 but since 2019 was recommended so I went with downloading it separately
I installed CMake 3.17.1 on Windows & it worked. Checked Command-Line after that
I then followed the steps of copy-pasting
set SDKROOT=%SystemDrive%\Library\Developer\Platforms\Windows.platform\Developer\SDKs\Windows.sdk
copy "%SDKROOT%\usr\share\ucrt.modulemap" "%UniversalCRTSdkDir%\Include\%UCRTVersion%\ucrt\module.modulemap"
copy "%SDKROOT%\usr\share\visualc.modulemap" "%VCToolsInstallDir%\include\module.modulemap"
copy "%SDKROOT%\usr\share\visualc.apinotes" "%VCToolsInstallDir%\include\visualc.apinotes"
copy "%SDKROOT%\usr\share\winsdk.modulemap" "%UniversalCRTSdkDir%\Include\%UCRTVersion%\um\module.modulemap"

everything in 2019 cmd visual studio tools....whatever mentioned using admin permissions but I get this error when I compiled my swift code
<unknown>:0: error: unable to load standard library for target 'x86_64-unknown-windows-msvc'

Can anyone suggest to me what went wrong?

compiling works like this
set SDKROOT=%SystemDrive%/Library/Developer/Platforms/Windows.platform/Developer/SDKs/Windows.sdk
swiftc -sdk %SDKROOT% -I %SDKROOT%\usr\lib\swift -L %SDKROOT%\usr\lib\swift\windows -emit-executable test.swift -o test.exe

Thanks for sharing your solution, I had the same problem!

I'm using Windows 10 2004. I have downloaded everything for Visual Studio 2019. I already had Visual Studio 2017 but since 2019 was recommended so I went with downloading it separately
I installed CMake 3.17.1 on Windows & it worked. Checked Command-Line after that
I then followed the steps of copy-pasting
set SDKROOT=%SystemDrive%\Library\Developer\Platforms\Windows.platform\Developer\SDKs\Windows.sdk
copy "%SDKROOT%\usr\share\ucrt.modulemap" "%UniversalCRTSdkDir%\Include\%UCRTVersion%\ucrt\module.modulemap"
copy "%SDKROOT%\usr\share\visualc.modulemap" "%VCToolsInstallDir%\include\module.modulemap"
copy "%SDKROOT%\usr\share\visualc.apinotes" "%VCToolsInstallDir%\include\visualc.apinotes"
copy "%SDKROOT%\usr\share\winsdk.modulemap" "%UniversalCRTSdkDir%\Include\%UCRTVersion%\um\module.modulemap"

everything in 2019 cmd visual studio tools....whatever mentioned using admin permissions but I get this error when I compiled my swift code
<unknown>:0: error: unable to load standard library for target 'x86_64-unknown-windows-msvc'

Can anyone suggest to me what went wrong?

@AbhimanyuAryan
Me too getting the same error can you help out with what you do to get rid out of it.


Adding optional service_check_rw parameter to check for read-only filesystem

What does this PR do?
This PR adds read-write/read-only service check for disk.py which notifies if any of the disks are in read-only state.
Motivation
We need this functionality in our production environment in addition to standard disk metrics in order to catch any of the disks falling back to read-only mode.
Review checklist

[x] PR has a meaningful title or PR has the no-changelog label attached
[x] Feature or bugfix has tests
[x] Git history is clean
[x] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo

Additional Notes
The test for this change passes our local testing environment replicated from TravisCI configuration

Hi @zippolyte I've updated PR according to your comments, let me know if anything else has to be modified.


Advanced RAG

deprecates usage of retriever for AI Services and adds retrievalAugmentor instead
adds a new integration test module for testing RAG-related stuff
updates RAG-related samples to use a retrievalAugmentor
updates the docs a little, but there's probably no point in repeating all details about advanced RAG strategies when they are in Langchain4j docs and examples?!

Fixes https://github.com/quarkiverse/quarkus-langchain4j/issues/332

CC @langchain4j

Very nice @jmartisk!
@cescoffier @langchain4j could you please have a look at the docs and examples?
Thanks

@jmartisk why aren't we using contentRetrieval as well ?

I opened this issue, wondering if should be closed then https://github.com/quarkiverse/quarkus-langchain4j/issues/326

@karesti Retrieval augmentors typically contain content retrievers (among other things) so I think it's not necessary to also support standalone content retrievers. Or should we? I'm not sure

Hmm, OK, given that langchain4j's AI service implementation also supports specifying a standalone content retriever (and it wraps it into a retrieval augmentor automatically) I think we can add that on our side too. I'll look into it

@jmartisk I have a work in progress locally that replaces simply retrieval by content retrieval (deprecating retrieval)

@jmartisk https://github.com/karesti/quarkus-langchain4j/tree/content-retrieval

@karesti Ok then I guess I can just leave it to you and you'll send a follow-up PR :)
Please consider whether we should have the bean providing the content retriever as a Supplier<ContentRetriever> instead of just ContentRetriever, because the typical usage is, just like with RetrievalAugmentor, to create a configured instance of a class that implements ContentRetriever. I see that in your code, you basically have to "wrap" an instance of the actual retriever inside a custom object that also implements it (https://github.com/karesti/quarkus-langchain4j/commit/ad7df344f73c13526bba6d7de79d3b06e6e7768d#diff-0e4e6053292ca1aed882a051f674e71ee8f249a33278838fd6a404f528872210R17) which is a bit clumsy IMO, maybe it should follow the same pattern that I have for Supplier<RetrievalAugmentor> here. But let's have @cescoffier and @langchain4j tell us their opinion

@jmartisk my branch is very simple now since I was just doing the deprecate code replacement. I'll follow the standard

Merging, we can certainly improve with this in


Show log output when running individual tests

In #1083 @sechkova dug into the current logging behaviour and documented that

Executing the tests by aggregate_tests.py buffers the output on a successful run.
Executing a test "by hand", the logging output remains hidden until an error occurs.

IMNSHO we should only buffer individual tests run by hand when the -b command-line option is passed.

I'd prefer that the test log level was easily modifiable (like V=DEBUG python3 test_updater.py) so the default could be practically silent but tricky issues were easy to debug.

That would also be fine, so long as we can toggle easily.

2. Executing a test "by hand", the logging output remains hidden until an error occurs.

This is untrue AFAICT: the output is same on error or no error (in an error case there might be more high level output of course, but same logger levels get printed). We do not initialize logging at all when tests are run individually: It think the default is to only print WARNING and above.
We could initialize the logging based on a env variable in each if __name__ == '__main__': ... but I would expect this was an issue where python folks would have a Best Practice?

I'll open another issue on logging in general but leaving an example that should work right now here:
if __name__ == '__main__':
  verbose = '-v' in sys.argv or '--verbose' in sys.argv
  loglevel = logging.DEBUG if verbose else logging.CRITICAL
  logging.basicConfig(level=loglevel)
  tuf.log.set_log_level(loglevel)

  unittest.main()

Notes:

this is only for running test files manually: it does not and should not affect test runners. They set their own logging policies
this slightly abuses unittest CLI: '--verbose' is actually unittest argument which we're now using as well
had to set default level to CRITICAL since we currently log so much on ERROR
tuf.log.set_log_level() seems to work against me as a library user. I've already set my root logger level so should not need anything else (and could do logging.getLogger('tuf').setLevel() if I wanted more control) but tuf forces me to call tuf.log.set_log_level() because there is a default that is not logging.NOTSET


Add ability to specify host/port for Snowflake connection

Description
Add ability to specify host/port for Snowflake connection.
Motivation: At LocalStack, we have recently started building a Snowflake emulator that allows running SF queries entirely on the local machine: https://blog.localstack.cloud/2024-05-22-introducing-localstack-for-snowflake/ . As part of a sample application we're building, we have an Apache Airflow DAG that uses Cosmos (and DBT) to connect to the local Snowflake emulator running on localhost. Here is a link to the sample app: https://github.com/localstack-samples/localstack-snowflake-samples/pull/12
Currently, we're hardcoding this integration in the user DAG file itself, see here:
...
from cosmos.profiles.snowflake.user_pass import SnowflakeUserPasswordProfileMapping
...
SnowflakeUserPasswordProfileMapping.airflow_param_mapping["host"] = "extra.host"
SnowflakeUserPasswordProfileMapping.airflow_param_mapping["port"] = "extra.port"
...

It would be awesome if this integration was provided by Cosmos out of the box! Looking forward to getting your feedback..
TODO: Please let me know where is the best place to add a description to these new attributes, happy to add a short note in the docs! Thanks 🙌
Checklist

[ ] I have made corresponding changes to the documentation (if required)
[ ] I have added tests that prove my fix is effective or that my feature works

TODO: Please let me know where is the best place to add a description to these new attributes, happy to add a short note in the docs! Thanks 🙌

We generate profile docs with automation

https://github.com/astronomer/astronomer-cosmos/blob/main/docs/generate_mappings.py


Entities: Adding the build entity

The build entity in ManageIQ representing the BuildConfig from Openshift.
Signed-off-by: Erez Freiberger<EMAIL_ADDRESS>

@simon3z please review.

@enoodle it seems that some information are missing:
https://github.com/openshift/origin/blob/v1.1/pkg/build/api/v1/types.go#L24-L50
ServiceAccount, Source, Output, Resources, CompletionDeadlineSeconds seem interesting enough to collect.
For the rest, @moolitayer @zeari please review.

Overall OK but missing a few things:

ServiceAccount, Source, Output, Resources, CompletionDeadlineSeconds seem interesting enough to collect.

In this patch I would collect anything that doesn't require another new entity.

This needs tests. They probably should be in spec/models/manageiq/providers/kubernetes/container_manager/refresh_parser_spec.rb
since making a new VCR for each in spec/models/manageiq/providers/openshift/container_manager/refresher_spec.rb is too much.

The Travis failure looks legit.

@zeari As we discussed, The Travis problem will be fixed after a new version of openshift_client is available and we will know the new version number to update the GemFile.
I added ServiceAccount, Source, Output, CompletionDeadlineSeconds but still have Resources to parse but I had some trouble with their definition. so far I added all but the Output values to the DB.
@moolitayer would you like to review too?

@enoodle as discussed there should be an increment of the openshift_client gem in this patch[1],
you can mark this as wip until such version is made (using @miq-bot add_label wip)
[1] https://github.com/ManageIQ/manageiq/blob/master/gems/pending/Gemfile

to add the new entities also update the list at:
https://github.com/ManageIQ/manageiq/blob/master/app/models/manageiq/providers/openshift/container_manager/refresher.rb

@miq-bot add_label wip

Overall direction is good (I didn't go into details), please @moolitayer @zeari review. Thanks!

@enoodle can you split out the UI side of this PR? Thanks.

@simon3z Split, The UI is in #6084

At first sight this looks in a good state. @moolitayer @zeari @dkorn @alongoldboim can you review?

Aside from styling errors I think this is ok.

@miq-bot remove_label wip

@miq-bot add_label wip

@miq-bot add_label wip

@enoodle why is this a WIP? What is missing?

@simon3z I want to add a relation to container_image

@simon3z I want to add a relation to container_image

if you address that in another PR, would this be ready now?

@simon3z yes

Then this LGTM :+1: cc @chessbyte ready for merge.
@enoodle please remove the wip label and address the container_image relationship in another PR.

@miq-bot remove_label wip

@simon3z good call separating out UI to another PR ... much easier to look at this in isolation :smile:


Postgres Kubernetes Helm chart fails with Envoy...

Running a Postgres Helm chart on an Istio enabled cluster is failing, due to failing health probes.
Istio version info:
Version: 0.2.12
GitRevision: 998e0e00d375688bcb2af042fc81a60ce5264009
GitBranch: release-0.2
Operating System: OSX 10.13.1 (high sierra)
Minikube Version: 0.24.1
Helm Version: 2.7.2
Repro Steps:
o Using minikube on OSX
o Enable istio on minikube per installation steps

kubectl create -f istio.yaml -f istio-initializer.yaml
o Init Helm
helm init
o Install the Postgresql chart
helm install --name pg stable/postgresql --version 0.8.4

Actual
The postgresql pod is getting decorated correctly with an envoy but remains in 1/2 ready state.
Looking at the events on the postgresql pod, health probs are failing.
Both readiness/liveliness default probes on the Postgres chart issue the shell command pg_isready

sh -c - exec pg_isready --host $POD_IP
a.b.c.d:5432 - no response
which fails with istio installed. Guessing http 1.0 issue??

Expected
The postgres Helm chart runs correctly in an Istio enabled cluster
Not sure if there is a way to tell Istio NOT to decorate a given service?
Outcome
My Istio enabled cluster fails since the db pod is not considered healthy hence dependent services fail as well.

Getting the same type of issue, consulted https://istio.io/docs/setup/kubernetes/sidecar-injection.html and still not sure what is going on.

Not sure if there is a way to tell Istio NOT to decorate a given service?

You can opt-out of having the proxy automatically injected by adding the following annotation to the pod template spec in your deployment.
annotations:
    sidecar.istio.io/inject: "false"

Can we add a blacklist (if auto-inject is enabled by default) and whitelist (if auto-inject is off by default) ? In some cases users can't edit the template - for example if they install with helm, or
from a repository (kubectl apply http:...).

{black,white}listing is already supported. First, you can scope when the webhook is invoked using the NamespaceSelector in the webhook registration. Second, you can further refine opt-in / opt-out behavior within those namespaces using the policy field in the injection ConfigMap. See https://istio.io/docs/setup/kubernetes/sidecar-injection.html#understanding-what-happened for details.

I added the annotation like:
template:
   metadata:
       annotations:
           sidecar.istio.io/inject: "false"

but it seems to still be injecting?
In my deployment yaml I see:
   "template": {
      "metadata": {
        "creationTimestamp": null,
        "labels": {
          "app": "dev-db-postgresql"
        },
        "annotations": {
          "sidecar.istio.io/inject": "false",
          "sidecar.istio.io/status": "injected-version-0.2.6"
        }

and the probes are still failing?

Just tested it using Istio 0.7.1 (with auto-injection webhook), the postgresql chart (0.8.4) does indeed fail with Failed create pod sandbox. error.
Adding sidecar.istio.io/inject: "false" to template.metadata.annotations in the postgres deployment chart fixed the problem for me.

I have the same issue on docker for mac, any idea why it fails ?

Facing also this issue with 0.7.1


Too many detections in a image

I tried to evaluate the network weights/ssd300_mAP_77.43_v2.pth
python eval.py
And here is what I got:

What puzzles me is that, there are too many predicted boxes? Isn't it?
I think there should be only two boxes:

Box for predicting the person.

Box for predicting the dog.

And I got these predicted boxes by the following modifications:
At def test_net of eval.py,
        ...
        for j in range(1, detections.size(1)):
        ...
                for k in range(boxes.shape[0]):
                point_left_up = (int(boxes[k, 0]), int(boxes[k, 1]))
                point_right_down = (int(boxes[k, 2]), int(boxes[k, 3]))
                cv2.rectangle(img_original, point_left_up, point_right_down, (0, 0, 255), 1)
                cv2.imwrite('test/test.png', img_original, [int(cv2.IMWRITE_PNG_COMPRESSION), 0])

Is there a mistake in my modification?
Or is this the performance of the network?

Here is what I did, but I’m not sure if it’s correct and the best.
I found that when the network is used for testing, it has a specific mode.
class SSD(nn.Module):
    def __init__(self, phase, size, base, extras, head, num_classes):
        ...
        if phase == 'test':
            self.softmax = nn.Softmax(dim=-1)
            self.detect = Detect()

And at layers\functions\detection.py, class Detect(Function):

"""At test time, Detect is the final layer of SSD.  Decode location preds,
apply non-maximum suppression to location predictions based on conf
scores and threshold to a top_k number of output predictions for both
confidence score and locations.
"""

So, at eval.py, def test_net(save_folder, net, cuda, dataset, transform, top_k, im_size=300, thresh=0.05):,
we can get

scores = dets[:, 0].cpu().numpy() # predicted values in descending order
boxes = dets[:, 1:] # corresponding coordinate information

Then in order to get the most accurate prediction, we can do:
if args.only_best_pred:
    num_draw_box = 1
else:
    num_draw_box = boxes.shape[0]
for k in range(num_draw_box):
    point_left_up = (int(boxes[k, 0]), int(boxes[k, 1]))
    point_right_down = (int(boxes[k, 2]), int(boxes[k, 3]))
    cv2.rectangle(img_original, point_left_up, point_right_down, (0, 0, 255), 1)

Then below is what I got:

Maybe we can set a threshold to draw more accurate prediction boxes.

Set a threshold to draw more accurate prediction boxes.
for k in range(num_draw_box):
    if args.pred_threshold < scores[k]:
        point_left_up = (int(boxes[k, 0]), int(boxes[k, 1]))
        point_right_down = (int(boxes[k, 2]), int(boxes[k, 3]))
        cv2.rectangle(img_original, point_left_up, point_right_down, (0, 0, 255), 1)


XCOM not working!!!!!

There is a problem with file names length:
here the output:
Save additional energies in file? (Y/N):
At line 86 of file xcom.f (unit = 7, file = '/Users/admin/Documents/workspace/OASYS-Develop/1.0.beta/XOPPY/orangecontrib/xoppy/util/datMDATX3.005')
the file name is limited to 100 characters.

I recompiled. Only in Mac. try this binary:
https://github.com/lucarebuffi/xoppy_external_codes/blob/master/bin/darwin/xcom
I cannot check, my installation has a shorter path


Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
 Continuing.
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:10:43 Adding launcheruserconfig.conf path to /opt/dynatrace/gateway/launcher/dynatracegateway.ini.
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:10:43 Updating property (/var/lib/dynatrace/gateway/config/config.properties:[collector]:seedServerUrl)
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:10:44 Adding tenantUUID to (/var/lib/dynatrace/gateway/config/instance.properties) with the value from TENANT.
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:10:44 Adding tenantToken to (/var/lib/dynatrace/gateway/config/instance.properties) with the value from TENANT_TOKEN.
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:10:44 Updating property (/var/lib/dynatrace/gateway/config/config.properties:[directories]:packagesDir)
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:10:44 Updating property (/var/lib/dynatrace/gateway/config/config.properties:[directories]:tenantDataDir)
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:10:44 Updating property (/var/lib/dynatrace/gateway/config/custom.properties:[synthetic]:synthetic_enabled)
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:10:44 Updating property (/var/lib/dynatrace/gateway/config/custom.properties:[synthetic]:synthetic_browser_monitors_enabled)
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:10:44 Browser monitors module disabled
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:10:44 Autobackup not found. No settings to preserve
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:10:44 Checking access to folders...
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:10:44 Starting Dynatrace Gateway...
aws_instance.dynatraceactivegate: Still creating... (1m50s elapsed)
aws_instance.dynatraceactivegate: Still creating... (2m1s elapsed)
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:11:05 Checking if Dynatrace Gateway is running ...
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:11:05 Dynatrace Gateway is running.
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:11:05 Successfully connected to server https://.live.dynatrace.com:443/communication
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:11:05 Starting Dynatrace ActiveGate AutoUpdater...
aws_instance.dynatraceactivegate: Still creating... (2m11s elapsed)
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:11:10 Checking if Dynatrace ActiveGate AutoUpdater is running ...
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:11:10 Dynatrace ActiveGate AutoUpdater is running.
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:11:10 Cleaning autobackup...
aws_instance.dynatraceactivegate (remote-exec): 05/04 07:11:10 Installation finished successfully.
aws_instance.dynatraceactivegate: Provisioning with 'file'...
aws_instance.dynatraceactivegate: Provisioning with 'remote-exec'...
aws_instance.dynatraceactivegate (remote-exec): Connecting to remote host via SSH...
aws_instance.dynatraceactivegate (remote-exec):   Host: 54.*******
aws_instance.dynatraceactivegate (remote-exec):   User: ubuntu
aws_instance.dynatraceactivegate (remote-exec):   Password: false
aws_instance.dynatraceactivegate (remote-exec):   Private key: true
aws_instance.dynatraceactivegate (remote-exec):   SSH Agent: false
aws_instance.dynatraceactivegate (remote-exec):   Checking Host Key: false
aws_instance.dynatraceactivegate: Still creating... (2m21s elapsed)
aws_instance.dynatraceactivegate (remote-exec): Connected!
aws_instance.dynatraceactivegate (remote-exec): dynatracegateway: unrecognized service
Error: Error applying plan:
1 error(s) occurred:

aws_instance.dynatraceactivegate: error executing "/tmp/terraform_463252123.sh": Process exited with status 1

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Thanks for raising this issue! looks like forcestop doesn't work with systemd. I've updated the instance.tf to have proper functioning commands.


Fix bug regarding TAO (tail array optimization) when using nested com…

…pound types.
This fixes a bug regarding tail optimized compound types.

@pavel-kirienko allthough tail optimization (TAO) will be removed, this is a bug in the current version of the libcanard dsdl compiler.


Hide "drag and drop" prompt on small screens

While it might be possible to use drag and drop on certain mobile phones, we can't know for sure.
I also imagine that even if it's possible, it's rather hard to do on such a small screen.
So it is likely better to just hide the prompt for these devices.
Note on tablets: I believe most if not all tablets should support drag and drop. Can't say for certain, though at least the most common mobile browsers (chrome for android, safari for ios) offer support according to caniuse.
Closes #859

Unfortunately I don't think screen size is a good enough indicator for drag'n'drop support. Too many false negatives and positives false positives. I would suspect that a combination of the media queries pointer and hover would result in fewer errors. It also seems like the "Modernizr" library has a way to check for drag'n'drop support?
Have you looked into alternatives for detecting drag'n'drop support? I'd say if there is nothing considerably better than the screen width appraoch, I would just always show the text and close #859 that way. That would be better than having a bad guess at it.

I looked for alternatives but apparently not exhaustively. Looking around some more, it seems that your suggestion might work. My latest push combines the suggested media query (to check device capabilites) with the check that modernizr appears to be using (to check browser support). We should test this deployment with browserstack to see how this works on different devices (...browserstack local wasn't working just now).

Closed with https://github.com/elan-ev/tobira/issues/859#issuecomment-1779043613


PanResponder velocity return error values on Android.

React-native version 0.27.0
relate to https://github.com/facebook/react-native/commit/f2c1868b56bdfc8b0d6f448733848eafed2cd440 this commit.
The touch event timestamp returns nanoseconds.
But PanResponder didn't update expectedly, it calculates velocity using millisecond yet.
It causes lots of issue, such as Navigator gesture not response as expectedly.

I ran into this and had to roll back to 0.26

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/panresponder-velocity-return-error-values-on-android
Product Pains has been very useful in highlighting the top bugs and feature requests:
https://productpains.com/product/react-native?tab=top
Also, if this issue is a bug, please consider sending a pull request with a fix.

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain thumbmunkeys.com has exceeded the max emails per hour (71/60 (118%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from filter01.reliabledns.org ([<IP_ADDRESS>]:56487)
by en02-ams.stablehost.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.87)
(envelope-from<EMAIL_ADDRESS>id 1bzswO-0004Wm-NH
for<EMAIL_ADDRESS>Thu, 27 Oct 2016 22:14:29 +0000
Received: from github-smtp2-ext7.iad.github.net ([<IP_ADDRESS>] helo=github-smtp2a-ext-cp1-prd.iad.github.net)
by filter01.reliabledns.org with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.86)
(envelope-from<EMAIL_ADDRESS>id 1bzswN-00015o-0H
for<EMAIL_ADDRESS>Thu, 27 Oct 2016 15:14:28 -0700
Date: Thu, 27 Oct 2016 15:14:02 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2014; t=1477606466;
bh=HnFI26j1796el/URF8m6EmxHbJPcRUU9RFbV/zEMwDQ=;
h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=VuzBVo+hbzzQPkn6yLxzaIlo6m+IPBvFbfYoqBuhap4/IdqvfIfXqmWeel/EqyxpI
vOciqgI67nz4hayN/LDkwFi5j4fOJBSoA1FyT7LujIGzewDbEb9fkwjpU+31LRejrL
OkkjVdiGKBfvuW2Fs6F31PosLQY/+Aa2y3Eh6ThE=
From: Martin Konicek<EMAIL_ADDRESS>Reply-To: facebook/react-native<EMAIL_ADDRESS>To: facebook/react-native<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [facebook/react-native] PanResponder velocity return error values
on Android. (#8238)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_58127c2ab8f64_78323fecfdea32b82917a6";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mkonicek
X-GitHub-Recipient: bunnyboy1
List-ID: facebook/react-native <react-native.facebook.github.com>
List-Archive: https://github.com/facebook/react-native
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/ARoNgw4e7GDavmcsxZhN5JDVSh_5sfl3ks5q4SIqgaJpZM4I5jFR
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>Received-SPF: pass (filter01.reliabledns.org: domain of github.com designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS><EMAIL_ADDRESS>helo=github-smtp2a-ext-cp1-prd.iad.github.net;
X-SPF-Result: filter01.reliabledns.org: domain of github.com designates <IP_ADDRESS> as permitted sender
Authentication-Results: filter01.reliabledns.org; dmarc=pass header.from=github.com
X-Filter-ID: s0sct1PQhAABKnZB5plbIamwIYzgudGL4tMY9zS3pea7KY6rzXjgC+rgKYUjsj8D0JuF70A4EJMc
Wn6O/bsgoWSYW6KbZfj8apx6ohl75uX35Caz8bqM3i8tzwcg+lnkZzoX7PhhDs80mBQKIGWwu/Ku
scxs0Lj66ws3lVlgoDJwJVSL6KLw+g28lkb31HyS94pE1Cssu3RLQ0/o4r6NbA8zp1yYIFRkRN8y
Bn+CxV3PHBxbnbbNfXfDEALY1mKivRa9GUEaFQ1z9OvylRfhGJz3A1ed2ITkOuMtrwds5D7K3wOa
hktxrld16n2/ku5KJq/4FZbX1lzD9O+fyiIjB8wTNR/tjjZvmBdM/4lPZO2sASVdHfbtk3LlI8pB
wr4jGeKz8vlEl/GSEiCnxc6Ard0BaVp3jhK5GOBJIv+LCtD+V9//iYPXcUPDr8DL9oJhN0JkcMmQ
sV7j9toT40ga/GYzx2Zgyhf3OXiddZgacWc1/+H6OHgtV1bmxcq0CB3pmrFpDzdgJQc/rZDiOC7K
RpZxGk3X7U/CrpemaTYEqjR6fyHrrsngmi97syQy+4L3p7+eg7tptOUU98CNo4IBbK0jiD6XqsJZ
tjQxlyCdsezJow6Hi0pxrFS5O4yOAY8o6W0BvTIC60F9LNR/0kDSJQ==
X-Report-Abuse-To<EMAIL_ADDRESS>Authentication-Results: reliabledns.org; spf=pass<EMAIL_ADDRESS>Authentication-Results: reliabledns.org; dkim=pass header.i=github.com
X-SpamExperts-Class: ham
X-SpamExperts-Evidence: dnswl/se-reputation (trusted ham)
X-Recommended-Action: accept
X-Spam-Status: No, score=1.1
X-Spam-Score: 11
X-Spam-Bar: +
X-Ham-Report: Spam detection software, running on the system "en02-ams.stablehost.com",
has NOT identified this incoming email as spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
root@localhost for details.
Content preview:  Closed #8238. -- You are receiving this because you are subscribed
to this thread. Reply to this email directly or view it on GitHub: https://github.com/facebook/react-native/issues/8238#event-839326317
[...]
Content analysis details:   (1.1 points, 5.0 required)
pts rule name              description

-0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at http://www.dnswl.org/, no
trust
[<IP_ADDRESS> listed in list.dnswl.org]
1.5 SPF_SOFTFAIL           SPF: sender does not match SPF record (softfail)
1.6 HTML_IMAGE_ONLY_24     BODY: HTML: images with 2000-2400 bytes of words
-1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
[score: 0.0001]
0.0 HTML_MESSAGE           BODY: HTML included in message
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
domain
0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
X-Spam-Flag: NO
----==_mimepart_58127c2ab8f64_78323fecfdea32b82917a6
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #8238.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/facebook/react-native/issues/8238#event-839326317
----==_mimepart_58127c2ab8f64_78323fecfdea32b82917a6
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #8238.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_58127c2ab8f64_78323fecfdea32b82917a6--

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain thumbmunkeys.com has exceeded the max emails per hour (74/60 (123%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from filter03.reliabledns.org ([<IP_ADDRESS>]:46834)
by en02-ams.stablehost.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.87)
(envelope-from<EMAIL_ADDRESS>id 1bzsx0-0004lg-5l
for<EMAIL_ADDRESS>Thu, 27 Oct 2016 22:15:08 +0000
Received: from github-smtp2-ext3.iad.github.net ([<IP_ADDRESS>] helo=github-smtp2b-ext-cp1-prd.iad.github.net)
by filter03.reliabledns.org with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.86)
(envelope-from<EMAIL_ADDRESS>id 1bzswz-00047L-D2
for<EMAIL_ADDRESS>Thu, 27 Oct 2016 15:15:06 -0700
Date: Thu, 27 Oct 2016 15:14:06 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2014; t=1477606505;
bh=q8+RwZhhrbkBfxcXZUMznr3AC3/v3U/u0acSvz2OPgE=;
h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=Bd9gVmp+ZVn/2pa2oyj9rmbkvXBnvODXXdSsY7cxZ//T+IGBBuWJA41sf5d6OUusT
FWh8xxQG5bcd4goNo8CywSg1CrEZsppd2NfXAYXHOy95wv/xUkWYqt+9CEU08CU+pQ
Yk49LIYlRUst8kQQVvO8xiIUjwlETukYhgffpFM0=
From: Martin Konicek<EMAIL_ADDRESS>Reply-To: facebook/react-native<EMAIL_ADDRESS>To: facebook/react-native<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [facebook/react-native] PanResponder velocity return error values
on Android. (#8238)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_58127c2e88f57_2dd63f99805952a022122e";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mkonicek
X-GitHub-Recipient: bunnyboy1
List-ID: facebook/react-native <react-native.facebook.github.com>
List-Archive: https://github.com/facebook/react-native
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/ARoNg3xcaVYRh08t5Yx9wfhFHpkhyRQrks5q4SIugaJpZM4I5jFR
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>Received-SPF: pass (filter03.reliabledns.org: domain of github.com designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS><EMAIL_ADDRESS>helo=github-smtp2b-ext-cp1-prd.iad.github.net;
X-SPF-Result: filter03.reliabledns.org: domain of github.com designates <IP_ADDRESS> as permitted sender
Authentication-Results: filter03.reliabledns.org; dmarc=pass header.from=github.com
X-Filter-ID: s0sct1PQhAABKnZB5plbIamwIYzgudGL4tMY9zS3pea7KY6rzXjgC+rgKYUjsj8D0JuF70A4EJMc
Wn6O/bsgoWSYW6KbZfj8apx6ohl75uX35Caz8bqM3i8tzwcg+lnkZzoX7PhhDs80mBQKIGWwu/ZE
jF4Pov/vsc2Cwocc9pJwJVSL6KLw+g28lkb31HyS94pE1Cssu3RLQ0/o4r6NbA8zp1yYIFRkRN8y
Bn+CxV1doqf3SsUlPh0rekbLE9fodFQ3wF8RRcNI4veBCAWmOJz3A1ed2ITkOuMtrwds5D4lTQ4T
s4pbWtZ3YR/lXG1VJq/4FZbX1lzD9O+fyiIjB8wTNR/tjjZvmBdM/4lPZO2sASVdHfbtk3LlI8pB
wr4jGeKz8vlEl/GSEiCnxc6Ard0BaVp3jhK5GOBJIv+LCtDC+P7wO5Dn5esh4VR+ptzHN0JkcMmQ
sV7j9toT40ga/GYzx2Zgyhf3OXiddZgacWc1/+H6OHgtV1bmxcq0CB3pmrFpDzdgJQc/rZDiOC7K
RpZxGk3X7U/CrpemaTYEqjTUmURjlDc0k2fuHA8w+LTop7+eg7tptOUU98CNo4IBbK0jiD6XqsJZ
tjQxlyCdsewOr32jdvPLa/TCfXr5TU2T209TOOJMB2SW4wvj3us5pA==
X-Report-Abuse-To<EMAIL_ADDRESS>Authentication-Results: reliabledns.org; spf=pass<EMAIL_ADDRESS>Authentication-Results: reliabledns.org; dkim=pass header.i=github.com
X-SpamExperts-Class: ham
X-SpamExperts-Evidence: dnswl/se-reputation (trusted ham)
X-Recommended-Action: accept
X-Spam-Status: No, score=0.0
X-Spam-Score: 0
X-Spam-Bar: /
X-Ham-Report: Spam detection software, running on the system "en02-ams.stablehost.com",
has NOT identified this incoming email as spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
root@localhost for details.
Content preview:  Hi there! This issue is being closed because it has been inactive
for a while. But don't worry, it will live on with ProductPains! Check out
its new home: https://productpains.com/post/react-native/panresponder-velocity-return-error-values-on-android
[...]
Content analysis details:   (0.0 points, 5.0 required)
pts rule name              description

-0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at http://www.dnswl.org/, no
trust
[<IP_ADDRESS> listed in list.dnswl.org]
0.5 RCVD_IN_SORBS_SPAM     RBL: SORBS: sender is a spam source
[<IP_ADDRESS> listed in dnsbl.sorbs.net]
1.5 SPF_SOFTFAIL           SPF: sender does not match SPF record (softfail)
-1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
0.0 HTML_MESSAGE           BODY: HTML included in message
0.0 HTML_IMAGE_ONLY_32     BODY: HTML: images with 2800-3200 bytes of words
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
domain
0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
X-Spam-Flag: NO
----==_mimepart_58127c2e88f57_2dd63f99805952a022122e
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/panresponder-velocity-return-error-values-on-android
Product Pains has been very useful in highlighting the top bugs and feature requests:
https://productpains.com/product/react-native?tab=top
Also, if this issue is a bug, please consider sending a pull request with a fix.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/facebook/react-native/issues/8238#issuecomment-256784818
----==_mimepart_58127c2e88f57_2dd63f99805952a022122e
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Hi there! This issue is being closed because it has been inactive for =
a while.
But don't worry, it will live on with ProductPains! Check out its new =
home: https://productpains.com/post/re=
act-native/panresponder-velocity-return-error-values-on-android
Product Pains has been very useful in highlighting the top bugs and fe=
ature requests:
https=
://productpains.com/product/react-native?tab=3Dtop
Also, if this issue is a bug, please consider sending a pull r=
equest with a fix.
&m=
dash;You are receiving this because you are subscribed to this thre=
ad.Reply to this email directly, view it on GitHub, or mute the thread.=

=
----==_mimepart_58127c2e88f57_2dd63f99805952a022122e--


Fix nodebalancer config create

Closes #1980

Coverage remained the same at 80.257% when pulling 7e55f179406990eaf0cb747059114243884def94 on eatonphil:fix-nodebalancer-config-create into 3bb17b15abd678a592aea0376411ca57441d7d63 on linode:release.

Coverage remained the same at 80.257% when pulling 7e55f179406990eaf0cb747059114243884def94 on eatonphil:fix-nodebalancer-config-create into 3bb17b15abd678a592aea0376411ca57441d7d63 on linode:release.

thank you!


[GSSoC'23] Guess the Gender By entering the name

Describe the project you want to add with tech stack

Front end project
Created using HTML, CSS and JS
Sending request using API key

Expected behavior

Using API key, data will tell the status of gender of the entered name
Responsive towards the mobile devices
Responsive User interface with effective color gradients

Screenshots (optional)

Additional context (optional )

Useful when to find the number of males of females in the large dataset just by entering the name of the person

@pranjay-poddar @MohitGupta121 @Saurabh-kumar09 Sirs, please assign this project to work on the API key and give a valuable contribution under GSSoC'23 program
Please /assign


rust-1.72.0 changes

I like to use the current stable for better errors. rustfmt has learned to format let irrefutable = $expr else { ... }; blocks, which causes a reformatting every time.
Also there's nagging on the root workspace resolver not being defined. Picking the later one should not be an issue, as far as I know, we don't use these features yet, nor should we. Later is most likely what people will expect.

You will probably also have to adjust the rust-toolchain file, like in #4550 and #4718.

The point is to make the future compatible changes. Switching to newer rust will require the build changes as well, I just want to get these out of the way before. Out of github, we need to decide what to do with the diverging anyhow::bail! usage, which is quite plenty.

There is nothing to decide with the anyhow::bail! usage, clippy had just flagged a strange usage for it (method only diverged), fixed in: 4f4fe35.
This completes all of the changes for 1.72.0 so we could next start the image upgrade and after that finally bump the rust-toolchain.


[beta] "ES6: Use Destructuring Assignment with Arrays": challenge seed contains part of description

Challenge  use-destructuring-assignment-with-arrays  http://beta.freecodecamp.com/en/challenges/es6/use-destructuring-assignment-with-arrays  has an issue. User Agent is: Mozilla/5.0  X11; Ubuntu; Linux x86_64; rv:51.0  Gecko/20100101 Firefox/51.0 .
Challenge seed contains part of challenge description, possibly instead of the proper part of code:
let a   8, b   6; // change code below this line // change code above this line blockquote>const  a, b     1, 2, 3, 4, 5, 7 ; br>console.log a, b ; // 1, 2 /blockquote> The variable a assumes first value, and b takes the second value from the array. You can also destructure in a way, that you can pick up values from any other array index position. You simply have to use commas  , . Instructions. Use destructuring to swap the variables a, b. Swapping is an operation, after which, a gets the value stored in b, and b receives the value stored in a

I'll fix this.


AWS Chime is Giving Meeting ended when CreateAttendeeAsync

Please let me know if there is a better place to report Chime issues.
Expected Behavior
when trying to call CreateAttendeeAsync User should add-in that meeting.
 This occurs when I am attempting to add  user in meeting.
Steps to Reproduce (for bugs)
Create a Meeting, CreateAttendee for Joining Call,
Your Environment
AWSSDK.Chime <IP_ADDRESS>

Hi @koni-a,
Good afternoon.
I was trying to reproduce the issue invoking CreateAttendeeAsync() after creating a meeting. Calls to CreateAttendeeAsync() work fine for me. Please share the Amazon Chime service configuration, sample code and logs in order to further troubleshoot the issue. In case this is no longer an issue, please confirm it could be closed.
Thanks,
Ashish

Hi Ashish,
I am using .Net Core to aws chime sdk,
Example :
I Created a meeting Request today, I am trying to access tomorrow to join the meeting that it is throwing error. i will repo to my github i will share with you.

Sorry for the delay here i am attaching the code repo
Repo : https://github.com/koni-a/AWSChime
gave the access to your id "ashishdhingra"
Can you please add Client ID and Client Secret Key in WeatherForecastController.cs
Below are the endpoints
Create Meeting :
Method: Get
Url: http://localhost:51468/weatherforecast/create
Join Attendee :
Method: Get
Url: http://localhost:51468/weatherforecast/my/{meetingId}/{Name}
try to join Meeting after 15 Min
Below are the error message :
Amazon.Chime.Model.NotFoundException: Meeting  not found
---> Amazon.Runtime.Internal.HttpErrorResponseException: Exception of type 'Amazon.Runtime.Internal.HttpErrorResponseException' was thrown.
at Amazon.Runtime.HttpWebRequestMessage.GetResponseAsync(CancellationToken cancellationToken)
at Amazon.Runtime.Internal.HttpHandler1.InvokeAsync[T](IExecutionContext executionContext)    at Amazon.Runtime.Internal.Unmarshaller.InvokeAsync[T](IExecutionContext executionContext)    at Amazon.Runtime.Internal.ErrorHandler.InvokeAsync[T](IExecutionContext executionContext)    --- End of inner exception stack trace ---    at Amazon.Runtime.Internal.HttpErrorResponseExceptionHandler.HandleException(IExecutionContext executionContext, HttpErrorResponseException exception)    at Amazon.Runtime.Internal.ExceptionHandler1.Handle(IExecutionContext executionContext, Exception exception)
at Amazon.Runtime.Internal.ErrorHandler.ProcessException(IExecutionContext executionContext, Exception exception)
at Amazon.Runtime.Internal.ErrorHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.CallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.EndpointDiscoveryHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.EndpointDiscoveryHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.CredentialsRetriever.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.RetryHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.RetryHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.CallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.CallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.ErrorCallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.MetricsHandler.InvokeAsync[T](IExecutionContext executionContext)
at ChimeVideoAPI.Controllers.WeatherForecastController.JoinMeeting(String meetingId, String name) in C:\MyWork\ChimeVideoAPI\ChimeVideoAPI\Controllers\WeatherForecastController.cs:line 81
at lambda_method(Closure , Object )
at Microsoft.Extensions.Internal.ObjectMethodExecutorAwaitable.Awaiter.GetResult()
at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.AwaitableObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask`1 actionResultValueTask)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|19_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
at Microsoft.AspNetCore.Routing.EndpointMiddleware.g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)
HEADERS
Accept: /
Accept-Encoding: gzip, deflate, br
Connection: keep-alive
Host: localhost:51468
User-Agent: PostmanRuntime/7.26.5
Postman-Token: 6739d2c3-6007-41c9-8d44-5b328eefbd95

Hi @koni-a,
Good afternoon.
I was going through backlog and came across this issue. As per your reproduction steps, the attendee tries to join the meeting after 15 minutes and then Meeting not found exception is thrown. As per documentation at Creating meetings with the Amazon Chime SDK, a meeting automatically ends after a period of inactivity, such as the following:

No audio connections are present in the meeting for more than five minutes.
Less than two audio connections are present in the meeting for more than 30 minutes.
Screen share viewer connections are inactive for more than 30 minutes.
The meeting time exceeds 24 hours.

In your scenario, since there are no audio connections are present in the meeting for more than five minutes, the meeting might have ended automatically.
Hope this provides possible reasoning.
Thanks,
Ashish


Documentation quick start scaffold not working for me

when trying to use the application via docker-compose I can't create the minimum structure for jwt
Command:
 docker-compose exec prest prestd migrate up auth --url "postgres://prest:prest@postgres:5432/prest?sslmode=disable&sslcert=&sslkey=&sslrootcert="

Console messages:
2023/01/31 21:16:37 [warning] file './prest.toml' not found, falling back to default settings
2023/01/31 21:16:37 [warning] read env config error: Config File "prest" Not Found in "[/app]"
2023/01/31 21:16:37 [warning]
You are using v1 of prestd configs, please migrate to v2.

v1 will be deprecated soon.

View more at https://docs.prestd.com/prestd/deployment/server-configuration
pq: syntax error at or near "%"Error: pq: syntax error at or near "%"
Usage:
  prestd migrate up auth [flags]

Flags:
  -h, --help   help for auth

Global Flags:
      --path string   Migrations directory
      --url string    Database driver url (default "postgres://prest:prest@postgres:5432/prest?sslmode=disable&sslcert=&sslkey=&sslrootcert=")

pq: syntax error at or near "%"

I'm going to do a simple test, I don't want to make several configurations in files and etc.
Docker compose file:
version: "3"
services:
  postgres:
    image: postgres
    volumes:
      - "./data/postgres:/var/lib/postgresql/data"
    environment:
      - POSTGRES_USER=prest
      - POSTGRES_DB=prest
      - POSTGRES_PASSWORD=prest
    ports:
      - "5432:5432"
    healthcheck:
      test: ["CMD-SHELL", "pg_isready", "-U", "prest"]
      interval: 30s
      retries: 3
  prest:
    # use latest build - analyze the risk of using this version in production
    image: prest/prest:v1
    links:
      - "postgres:postgres"
    environment:
      - PREST_DEBUG=true
      - PREST_AUTH_ENABLED=false
      - PREST_PG_HOST=postgres
      - PREST_PG_USER=prest
      - PREST_PG_PASS=prest
      - PREST_PG_DATABASE=prest
      - PREST_PG_PORT=5432
      - PREST_SSL_MODE=disable
      - PREST_CACHE_ENABLED=false
      - PREST_CACHE=false
    depends_on:
      postgres:
        condition: service_healthy
    ports:
      - "3000:3000"

I have same issue on Ubuntu 22.04, but donot have this issue on WSL2.

Update: v1.1 workable.

@bulayee v1.1 is the docker image tag?

Now it worked for me. But I needed to change the docker image version.
I following this tutorial https://docs.prestd.com/prestd/docs/#test-using-docker
the only difference is after downloading the docker-compose.yml file, I change the prest image version of  image: prest/prest for image: prest/prest:v1.1. And I changed the image version before starting de stack, that is the second instruction of this tutorial docker-compose up.
With this simple configuration it Worked!!

@arxdsilva we might have a problem on the current image, then =/

@vmesel    If I try with prest/prest:latest the command docker-compose exec prest prestd migrate up auth does not work. But I think that if create prest_users manually will work.  Is possible that the problem is only on the migrate up auth command

I try with docker on Windows only (docker desktop)

leaving recorded the conversation I had in private with @alisonjr

he managed to follow the tutorial with version v1.1 (generated 1 year ago), is there any bug from there to here
we need to revise the tutorial for the new version

tried locally, so from the error It seams to be related to the one I had here: https://github.com/prest/prest/issues/767
So it is probably also related to https://github.com/prest/prest/pull/762, will have a look at them.

tried locally, so from the error It seams to be related to the one I had here: #767
So it is probably also related to #762, will have a look at them.

@arxdsilva were you able to look at this problem?

@avelino I've created a branch to work on this but havent solved yet, will open a PR to fix the problems that I already found.

@alisonjr could you help us by testing the "dev" version of the docker image and see if it works, working we generated release with this hotfix

@avelino I already tested locally, as I stated in the PR, this issue still isnt fixed but I've addressed related errors that were found while trying to fix this.

@arxdsilva generate new version pls

@alisonjr @bulayee please verify that it was fixed in v1.2.3, this was just merged.


Non Existing Directories and Non Existing Artifacts respond with 404 -  #418 / #419 / #420

Pull looks fine by me :) Thanks @sanket407 !

Hi @sanket407 and thanks for your PR! Looks great but you should not print the java.lang.IllegalArgumentException: Illegal character as @fuss86 has suggested in his comment earlier (https://github.com/strongbox/strongbox/pull/463#discussion_r159052950). You should only print a message because we already have too much logging info:
getLogger().debug("Cannot resolve invalid path " + path);

I'd actually say -- print nothing at all. We have tons and tons of debugging output. While developing the code, it's fine to have a line there that prints it out, but, to be honest, there will be many cases where people try to resolve an artifact and it's simply not there. These are all perfectly legal cases. If we keep printing these exceptions, or even one-liners all the time, the logs will eventually produce a lot of unnecessary noise...

@carlspring  ok ! I will just keep a comment in its place ! Just for further reference !

Okay, that sounds good to me.
Let me know when it could be merged. :)

Its done !

Thanks, @sanket407 !


dpaez/promise support

This PR adds promise support for level methods used by this lib.
This should fix https://github.com/hypermodules/level-auto-index/issues/30
:v:

Awesome! Will check it out today. Module was written before promise support was added to the level stack but it’s great to catch up finally.

Looks good.  I think next steps would be to add promise support to the hooks.  Open to this but I don't have the bandwidth to work on it quite yet.

https://github.com/hypermodules/level-hookdown/releases/tag/v3.1.0 🎉


[Deprecate] Remove old FW version test

New code for testing the Software versioning is in. This old test are now failing on the CT. Need to remove.

Shall we park this to Sweta?


fix docstring typos

Changes so minor I almost want to apologize. Stumbled on whilst going through code, seemed worth fixing, even just for aesthetic/OCD reasons :)

Feels way out of proportion to name me as a contributor for changing three characters. If this is a subtle attempt to try to guilt me into making an actual contribution, it may be working :)

Haha I feel seen 😄 though beyond this being a not so subtle attempt to incentivize / lure one-off contributors to contribute more regularly, I really like the idea to also acknowledge contributions that go beyond writing code & implementing full features. And then it's somewhat difficult to make a cutoff, so my decision rule at the moment is that "everything that is merged or leads to a code change" qualifies =)


replace class with struct on models

technical improvement:

replaced class with structs(apple doc)
removed custom inits as structs provide them out of the box
removed CodingKeys on Instruction as it is not needed

Thank you for contribution 💪🏼


Layout.split is not stable; returns different dimensions depending on how often it is called

Describe the bug
Calling Layout.split does not have predictable results.
To Reproduce
    use std::error::Error;
    use std::io::{stdout, Write};
    use tui::Terminal;
    use tui::{
        backend::{Backend, CrosstermBackend},
        layout::{Constraint, Layout, Rect},
        style::{Color, Style},
        text::{Span, Spans},
        widgets::{Block, Borders, Paragraph},
        Frame,
    };
    use crossterm::{
        event::EnableMouseCapture,
        execute,
        terminal::{enable_raw_mode, EnterAlternateScreen},
    };
    fn main() {
        build();
    }

    pub fn build() -> Result<Terminal<CrosstermBackend<std::io::Stdout>>, Box<dyn Error>> {
        // Initial setup
        enable_raw_mode()?;
        let mut stdout = stdout();
        execute!(stdout, EnterAlternateScreen, EnableMouseCapture);
        let backend = CrosstermBackend::new(stdout);
        let mut terminal = Terminal::new(backend).unwrap();
        terminal.draw(|f| draw_initial(f))?;
        loop {}
        // return Ok(terminal);
    }

    pub fn draw_initial<B: Backend>(f: &mut Frame<B>) {
        let size = f.size();
        let chunks = Layout::default()
            .constraints([Constraint::Min(2), Constraint::Min(2)].as_ref())
            .split(Rect {
                x: 0,
                y: 0,
                width: size.width,
                height: size.height - 3,
            });
        let text = "I\nam\na\ncontent\nline";
        let content = Paragraph::new(Spans::from(Span::styled(
            text,
            Style::default().fg(Color::Red),
        )));
        f.render_widget(content, chunks[0]);
        let text2 = "command line";
        let content2 = Paragraph::new(Spans::from(Span::styled(
            text2,
            Style::default().fg(Color::Red),
        )))
        .block(
            Block::default()
                .borders(Borders::TOP)
                .title("──Command Line"),
        );
        f.render_widget(content2, chunks[1]);
        println!("{:?}", chunks);
    }

Expected behavior
The same layout is always generated.
Screenshots
The layout is different sometimes (third pane). The darker gray lines are the pane separators in tmux.

Same problem in 4 separate iTerm 2 windows; the second terminal is rendered differently:

Desktop (please complete the following information):

OS: MacOS 11.0.1 (20B29)
Terminal Emulator: iTerm2, Alacritty
Font: Fira Code
Crate version: tui = { version = "0.13", default-features = false, features = ['crossterm'] }
Backend: crossterm = "0.18"

This crate uses cassowary-rs to find a layout solving the provided constraints. When the constraints are ambiguous or multiple solutions can satisfy them, the crate documentation suggest that:

for efficiency reasons this is picked nondeterministically

In your case, both layouts are actually valid solutions to your constraints, so I would advise you to use more precise constraints. At some point we may replace the underlying layout system but this is definitely not a priority at the moment :).


derive: Upgrade syn/quote/proc_macro dependencies to 1.0

Codecov Report

Merging #413 into master will increase coverage by 0.06%.
The diff coverage is 14.28%.

@@            Coverage Diff             @@
##           master     #413      +/-   ##
==========================================
+ Coverage   85.71%   85.77%   +0.06%
==========================================
  Files         110      110
  Lines       15825    15787      -38
==========================================
- Hits        13564    13541      -23
+ Misses       2261     2246      -15

Impacted Files
Coverage Δ

juniper_codegen/src/derive_enum.rs
0% <ø> (ø)
:arrow_up:

juniper_codegen/src/impl_object.rs
0% <0%> (ø)
:arrow_up:

juniper_codegen/src/derive_input_object.rs
0% <0%> (ø)
:arrow_up:

juniper_codegen/src/derive_scalar_value.rs
0% <0%> (ø)
:arrow_up:

juniper_codegen/src/util.rs
31.51% <28%> (+0.75%)
:arrow_up:

juniper/src/lib.rs
83.87% <0%> (-3.23%)
:arrow_down:

juniper/src/types/utilities.rs
90.47% <0%> (-2.39%)
:arrow_down:

juniper/src/value/mod.rs
85.58% <0%> (-1.81%)
:arrow_down:

juniper/src/ast.rs
81.06% <0%> (-0.9%)
:arrow_down:

juniper/src/types/base.rs
90.41% <0%> (-0.6%)
:arrow_down:

... and 14 more

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 752584f...e86da97. Read the comment docs.

Codecov Report

Merging #413 into master will increase coverage by 0.06%.
The diff coverage is 14.28%.

@@            Coverage Diff             @@
##           master     #413      +/-   ##
==========================================
+ Coverage   85.71%   85.77%   +0.06%
==========================================
  Files         110      110
  Lines       15825    15787      -38
==========================================
- Hits        13564    13541      -23
+ Misses       2261     2246      -15

Impacted Files
Coverage Δ

juniper_codegen/src/derive_enum.rs
0% <ø> (ø)
:arrow_up:

juniper_codegen/src/impl_object.rs
0% <0%> (ø)
:arrow_up:

juniper_codegen/src/derive_input_object.rs
0% <0%> (ø)
:arrow_up:

juniper_codegen/src/derive_scalar_value.rs
0% <0%> (ø)
:arrow_up:

juniper_codegen/src/util.rs
31.51% <28%> (+0.75%)
:arrow_up:

juniper/src/lib.rs
83.87% <0%> (-3.23%)
:arrow_down:

juniper/src/types/utilities.rs
90.47% <0%> (-2.39%)
:arrow_down:

juniper/src/value/mod.rs
85.58% <0%> (-1.81%)
:arrow_down:

juniper/src/ast.rs
81.06% <0%> (-0.9%)
:arrow_down:

juniper/src/types/base.rs
90.41% <0%> (-0.6%)
:arrow_down:

... and 14 more

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 752584f...e86da97. Read the comment docs.


Why do all object keys for className overlayClassName object prop need to be required?

Summary:
#536 introduced a specification for the className and overlayClassName props when passed as objects. I am interested in knowing whether or not all keys on the prop object need to be required. I would prefer to not be required to implement all three keys all the time (unless there is some a11y gain or the removal of some subtle bug).
Steps to reproduce:

Create a <ReactModal> and supply it an overlayClassName prop as an object, but exclude one of the three possible object keys (i.e. base, afterOpen, beforeClose)

Upon the modal render, you should see a prop warning in your console

Expected behavior:
No proptypes warning for missing object keys.
Link to example of issue:
I made a codepen that shows the warning, but I'm not really sure it's necessary. It's obvious by the code that the proptype warning will occur.

Yeah, there is room to improve this particular function ModalPortal.js#L268. The way it's implemented requires the same shape as in line ModalPortal.js#L272.

Looking at the code now, currently it works like this:
<Modal className={{
    base: "mymodal",
    afterOpen: "mymodal_after-open",
    beforeClose: "mymodal_before-close"
}}>

This will render to className="mymodal mymodal_after-open".
Not sure if afterOpen and beforeClose should be only the suffix part of the class, like:
<Modal className={{
    base: "mymodal",
    afterOpen: "_after-open",
    beforeClose: "_before-close"
}}>

This will give the same result as the first example, ${base}${afterOpen} and ${base}+${beforeClose}.

@indiesquidge any thoughts?

@diasbruno, after digging back into the necessity of having every key be required on the className and overlayClassName props as objects, it seems like there are a number of ways in which we can allow the keys to be optional. Looking back through this library's history, it seems the reason the keys were made required was because a missing key resulted in a class name of undefined being added to the element. If that is indeed the only reason they were added, it seems like we could get around that in a number of ways.
Potential Solution 1
Check if the key exists, and if it doesn't exist, only include base. (We could either leave base as a required key, or just default it to an empty string within this function.)
  buildClassName = (which, additional) => {
    const classNames =
      typeof additional === "object"
        ? additional
        : {
            base: CLASS_NAMES[which],
            afterOpen: `${CLASS_NAMES[which]}--after-open`,
            beforeClose: `${CLASS_NAMES[which]}--before-close`
          };
    let className = classNames.base;
    if (this.state.afterOpen) {
-     className = `${className} ${classNames.afterOpen}`;
+     className = classNames.afterOpen
+       ? `${className} ${classNames.afterOpen}`
+       : className;
    }
    if (this.state.beforeClose) {
-     className = `${className} ${classNames.beforeClose}`;
+     className = classNames.beforeClose
+       ? `${className} ${classNames.beforeClose}`
+       : className;
    }
    return typeof additional === "string" && additional
      ? `${className} ${additional}`
      : className;
  };

Potential Solution 2
Just render an empty string if the key is missing. This is less code, but the downside is that the full class name for the opened/closed states becomes customBaseClass  with that extra space there on the end. I don't see that as a huge issue, but it could be perceived as strange.
  buildClassName = (which, additional) => {
    const classNames =
      typeof additional === "object"
        ? additional
        : {
            base: CLASS_NAMES[which],
            afterOpen: `${CLASS_NAMES[which]}--after-open`,
            beforeClose: `${CLASS_NAMES[which]}--before-close`
          };
    let className = classNames.base;
    if (this.state.afterOpen) {
-     className = `${className} ${classNames.afterOpen}`;
+     className = `${className} ${classNames.afterOpen || ""}`;
    }
    if (this.state.beforeClose) {
-     className = `${className} ${classNames.beforeClose}`;
+     className = `${className} ${classNames.beforeClose || ""}`;
    }
    return typeof additional === "string" && additional
      ? `${className} ${additional}`
      : className;
  };

There are probably many ways to get around adding an undefined class name. If that is the reason the keys were made required, I'd be more than happy to implement an internal solution around it with some tests. If there are other reasons for making the keys required, I'd love to know about them so that I can contemplate a solution with more context.

You are right about the 'missing the default'. This problem could be fixed by merging with some default object like:
const defaultNames = {
  base: CLASS_NAMES[which],
  afterOpen: `${CLASS_NAMES[which]}--after-open`,
  beforeClose: `${CLASS_NAMES[which]}--before-close`
};
typeof additional === "object"
  ? Object.assign({}, defaultNames, additional) <--
  : default;

Maybe this function need to be refactored since it can do unnecessary work depending on the type of additional.


Issue with /docs/tutorials/kubernetes-basics/update-interactive/

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
In the last paragraph of the Step 3, it says that "We see that the deployment is using a stable version of the app (v1). The Rollback was successful.", while the stable version currently running is v2
Proposed Solution:
Change v1 into v2 in the last paragraph of the Step 3
Page to Update:
http://kubernetes.io/docs/tutorials/kubernetes-basics/update-interactive/

Duplicate issue; same as #1697, https://github.com/kubernetes/kubernetes.github.io/issues/1697#event-918036436


forcing scripts to install into /bin for consistency.

Connects to ament/ament_lint#13

connects to: ament/ament_lint#13

trying to link correctly.

lgtm

also runs for me

Great!


Refactor argparser

I've fixed several features of argparser.py in this pr.

help message wasn`t actually helping
fix order of sentences and split args of function to multi lines for readability

    // I think it is better
    training            train the network
    prediction          make prediction from trained network

　   // these are obvious
    param_search        see `param_search -h`
    sym_func            see `sym_func -h`
    phonon              see `phonon -h`

Please try git --help for examples.
Thank you.

Yeah, I know that. But the stdout happens sequentially with the progress.

The scripts are now implemented.
$ hdnnpy vasp2xyz

$ hdnnpy merge-xyz


metadata refresh exclude myself.

Pull Request Test Coverage Report for Build 11002

10 of 15 (66.67%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.007%) to 57.602%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-orchestration/sharding-orchestration-core/sharding-orchestration-core-metadatacenter/src/main/java/org/apache/shardingsphere/orchestration/core/metadatacenter/event/MetaDataIgnoredEvent.java
0
1
0.0%

sharding-orchestration/sharding-orchestration-core/sharding-orchestration-core-metadatacenter/src/main/java/org/apache/shardingsphere/orchestration/core/metadatacenter/listener/MetaDataChangedListener.java
2
3
66.67%

sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/schema/impl/ShardingSchema.java
0
1
0.0%

sharding-orchestration/sharding-orchestration-core/sharding-orchestration-core-metadatacenter/src/main/java/org/apache/shardingsphere/orchestration/core/metadatacenter/threadlocal/MetadataRefreshThreadLocal.java
8
10
80.0%

Totals

Change from base Build 10999:
0.007%

Covered Lines:
11821

Relevant Lines:
20522

💛  - Coveralls

This pr is invalid, cause of the new event does not take effect with original event.

Codecov Report

Merging #5165 into master will decrease coverage by 0.07%.
The diff coverage is 53.33%.

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


Support promotion config affected.groups.exclude

We can use something like this to reduce thousands of metadata clean-up jobs.
[promote]
affected.groups.exclude=^build-\d+
The build-# groups are just temp build groups and we can just skip the meta clean-ups.

Will we need this in place before we cut 2.0.0?

I'd like to but not necessary.
If I can get the reboot thing resolved, I'd roll out this pr very quickly. The reboot issue (nos-2424) a bit tricker than I thought.

@jdcasey I get it done - global filter for affected-by groups. The filter is added to the most basic AbstractIndyFunctionalTest and all ftests are happy with that. Pls review it and let me know if I miss anything. I thought it is quite safe but not sure if it will impact any edge cases.


Validate config file version when importing

Description
We could update the version of the config file in the future in a way that would break compatibility. This would result in preset import from older clients from the new config file format failing in unexpected ways.
I think it's important for MVP to validate a file version when reading a config file. We also need to write this version to the file when we generate it. Config import should fail with a recognizable error if the user tries to import a config file that is newer than what the client is able to import.
We could just use an integer for the config file version and increment it for any change that would cause an older client to not be able to import it.
We could alternatively have a {MAJOR}.{MINOR} file version, with minor changes being additions to the format that are ignored by older clients without errors. In this case the version validation can not throw an error for larger minor versions, but it could display a warning.
Tasks

[ ] Update the config file generation code to write a file version to the zip archive
[ ] Update the config import code to check the file version is known before trying to import it, and throw an error if not.

this was done when https://github.com/digidem/mapeo-core-next/pull/721 was merged


fix: access exposed properties from wrapper

this is work in progress from a stream - adding here to prevent it from being lost

@danielroe Do you have plans to continue working on this PR?

Thanks for the reminder! I will indeed, but if you want to pick it up before I do, I would certainly be grateful. 🙏

I'm not sure if I can solve this issue. 😢
In your example it is possible to access objects via
expect(component.vm.$.exposed.someRef.value).toBe('thing')

but no proxy is created for it.
Looks like a problem with suspend #vuejs/core/issues/7346


Unity version

This project looks very promising and I wonder if you could make a unity project version?

Hey there
Thank you for your interest
What do you mean by a unity project version?
This library targets .NET standard 1.0 which i believe is compatible with unity? https://docs.microsoft.com/en-us/dotnet/standard/net-standard

Hey there
Thank you for your interest
What do you mean by a unity project version?
This library targets .NET standard 1.0 which i believe is compatible with unity? https://docs.microsoft.com/en-us/dotnet/standard/net-standard

Hey there
Thank you for your interest
What do you mean by a unity project version?
This library targets .NET standard 1.0 which i believe is compatible with unity? https://docs.microsoft.com/en-us/dotnet/standard/net-standard

Hey there
Thank you for your interest
What do you mean by a unity project version?
This library targets .NET standard 1.0 which i believe is compatible with unity? https://docs.microsoft.com/en-us/dotnet/standard/net-standard

It works, yeah but It wouldn't be integrated with unity, without unity components and a scene.
What I mean is that for example using unity Update and Time to depended on frame rate, using Transform for position and rotation values.

It works, yeah but It wouldn't be integrated with unity, without unity components and a scene.
What I mean is that for example using unity Update and Time to depended on frame rate, using Transform for position and rotation values.

Quite frankly I'm not very familiar with Unity  :(
One of the main aim of this project is to be decoupled from any third party library. So if unity support is added it should be as an extension of this library.
I'm currently not in a position to be able to look into it. However if you have some solution and would like to submit a PR, I'd be happy to check it out :)

Quite frankly I'm not very familiar with Unity  :(
One of the main aim of this project is to be decoupled from any third party library. So if unity support is added it should be as an extension of this library.
I'm currently not in a position to be able to look into it. However if you have some solution and would like to submit a PR, I'd be happy to check it out :)

Hey thats great, I'll look into it 👍

Hey thats great, I'll look into it 👍


Clear search results when clearing search results as reported on issue #113

Added a new component as I needed to hookup redux to clear the search results and navigate back, this PR will solve #113 I think.

nice job @dan1d, contributing to both the app and android!
@akinwale please review at your earliest convenience.


loss is nan

your example was right, but when batch_size was 128, loss was nan,  actually it occur error on 36,37th line in circleloss.py.

One example in the code is a tensor with a batch size of 128, and the result is not nan, so did you use the 'cos' method to calculate the similarity?

your example was right, but when batch_size was 128, loss was nan, actually it occur error on 36,37th line in circleloss.py.

One example in the code is a tensor with a batch size of 128, and the result is not nan, so did you use the 'cos' method to calculate the similarity?

yes.

@qianjinhao
You may use soft_plus and logsumexp instead.
https://github.com/TinyZeaMays/CircleLoss/blob/d002ecd0c7e395f6e39bf8a2a96fd05b83afa93f/circle_loss.py#L37

@qianjinhao
You may use soft_plus and logsumexp instead.
https://github.com/TinyZeaMays/CircleLoss/blob/d002ecd0c7e395f6e39bf8a2a96fd05b83afa93f/circle_loss.py#L37

@qianjinhao
You may use soft_plus and logsumexp instead.
https://github.com/TinyZeaMays/CircleLoss/blob/d002ecd0c7e395f6e39bf8a2a96fd05b83afa93f/circle_loss.py#L37

Thanks for the reminder. Have you tested the difference between the two implementations?

@qianjinhao
You may use soft_plus and logsumexp instead.
https://github.com/TinyZeaMays/CircleLoss/blob/d002ecd0c7e395f6e39bf8a2a96fd05b83afa93f/circle_loss.py#L37

Can you tell me what is the difference between your implement and @qianjinhao 's implement. Cause I think it's true formula for circle loss


Added initial option to key generate command

Sometimes key:generate command is used in deploy scripts, which runs more than one time (each merge, for example). On production environment you dont need to set/overwrite application key each deploy.
Added option --initial to key:generate command allows to not set/overwrite application key if it already set.

I think the "key:generate" command shouldn't be in a deploy script that runs on every merge.
It's like having the "db:seed" command in the deploy script but it should only execute on the first deployment.
It's probably better to have a provision script that you execute when setting up a project.


add relnotes for July patch release

Deploy preview for modest-edison-79d82e ready!
Built with commit 57611c3813691afbebd278e31431733a26511f41
https://deploy-preview-7117--modest-edison-79d82e.netlify.com


env!("OUT_DIR") macro

Hello,
This PR is related to the #1964.
@matklad pls give a hint on how do we search for the OUT_DIR in the workspace given that we have a target_path from cargo metadata and can use that.

"look at what Cargo does, and do the same"

Highly relevant:
https://github.com/rust-lang/cargo/blob/b03182a8ff0117ffa1c426119ae2b5a418776bbd/src/cargo/core/compiler/context/compilation_files.rs#L216-L220
https://github.com/rust-lang/cargo/blob/b03182a8ff0117ffa1c426119ae2b5a418776bbd/src/cargo/core/compiler/context/compilation_files.rs#L197-L204
https://github.com/rust-lang/cargo/blob/b03182a8ff0117ffa1c426119ae2b5a418776bbd/src/cargo/core/compiler/context/compilation_files.rs#L164-L170

    /// Returns the "OUT_DIR" directory for running a build script.
    /// `/path/to/target/{debug,release}/build/PKG-HASH/out`
    pub fn build_script_out_dir(&self, unit: &Unit<'a>) -> PathBuf {
        self.build_script_run_dir(unit).join("out")
    }

    /// Returns the directory where a compiled build script is stored.
    /// `/path/to/target/{debug,release}/build/PKG-HASH`
    pub fn build_script_dir(&self, unit: &Unit<'a>) -> PathBuf {
        assert!(unit.target.is_custom_build());
        assert!(!unit.mode.is_run_custom_build());
        let dir = self.pkg_dir(unit);
        self.layout(CompileKind::Host).build().join(dir)
    }

    pub fn pkg_dir(&self, unit: &Unit<'a>) -> String {
        let name = unit.pkg.package_id().name();
        match self.metas[unit] {
            Some(ref meta) => format!("{}-{}", name, meta),
            None => format!("{}-{}", name, self.target_short_hash(unit)),
        }
    }

cargo metadata's target_directory is just the path to the %workspace/target directory, so it seems the only way to get OUT_DIR would be to guess the package meta disambiguator 😞
If nightly cargo is used, cargo +nightly build -Z unstable-options --build-plan outputs a huge JSON blob that includes
{ "invocations": [
  ..,
  { "package_name": "this-package",
    "target_kind": [ "custom-build" ],
    "compile_mode": "run-custom-build",
    "env": { "OUT_DIR": "/absolute/path/to/target/debug/build/this-package-hash/out" }
  },
  ..
}

This is present even if the build is fresh and would not be rerun, but does seem to make the build stale and queue a new full rebuild 😞
I think the "best" option would to be adding OUT_DIR to the cargo metadata information, if the package meta is set at that point. cc https://github.com/rust-lang/cargo/issues/7546

Also related: intellij-rust's implementation of env("OUT_DIR"): https://github.com/intellij-rust/intellij-rust/pull/4542
They use cargo build --build-plan.

@eupn are you still interested in this patch? I'd be happy to continue to implement it.

@edwin0cheng go ahead!

Current status:
OUT_DIR for a given build script is reported in the build script's build-script-executed message. https://github.com/rust-lang/cargo/pull/7622
Here's IntelliJ Rust's (currently off-by-default) support for OUT_DIR: https://github.com/intellij-rust/intellij-rust/pull/4734 (unless they've done more recently, ofc).

@CAD97
Yeah, and the current status of RA part :
We have implemented basic include and concat eager builtin macro. So this is the final puzzle for supporting `include!(concat!(env!(“OUT_DIR”), “xxx.rs”))!!

Another update :
#3549 is landed ! Although it didn't implement fetching OUT_DIR from cargo check yet, but I think it works functionally.
I will close this PR now and feel free to reopen it if needed.
Thanks @eupn.


It is not possible to suppress the use of regular expression for files

🚀 Feature Proposal
It would be useful for me to have a flag to suppress the use of regular expression for files.
Motivation
I would like to run one single file, mostly for debugging reasons. But as soon as the filename exists is some other filename the tests takes longer than needed.
Example
Lets assume we have the following two files:
Repository.integration.test
EntityRepository.integration.test

I would like to run Repository.integration.test but at the moment with jest Repository.integration.test both files are executed. A flag like the following would be useful for my use case:
jest Repository.integration.test --noRegEx

Add a full path to that file then, it will work. We're not gonna add new flags for such a use case.

I'd recommend just running jest /Repository.integration.test, there's usually some simple tricks that'll allow you to be more precise with the regex


Cannot run on mac osx El Capitain

Traceback (most recent call last):
File "/usr/local/bin/vncdo", line 9, in
load_entry_point('vncdotool==0.10.0', 'console_scripts', 'vncdo')()
File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 357, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 2394, in load_entry_point
return ep.load()
File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 2108, in load
entry = import(self.module_name, globals(),globals(), ['name'])
File "/Library/Python/2.7/site-packages/vncdotool/command.py", line 18, in
from twisted.internet import reactor, protocol
File "/Library/Python/2.7/site-packages/twisted/internet/reactor.py", line 38, in
from twisted.internet import default
File "/Library/Python/2.7/site-packages/twisted/internet/default.py", line 56, in
install = _getInstallFunction(platform)
File "/Library/Python/2.7/site-packages/twisted/internet/default.py", line 50, in _getInstallFunction
from twisted.internet.selectreactor import install
File "/Library/Python/2.7/site-packages/twisted/internet/selectreactor.py", line 18, in
from twisted.internet import posixbase
File "/Library/Python/2.7/site-packages/twisted/internet/posixbase.py", line 18, in
from twisted.internet import error, udp, tcp
File "/Library/Python/2.7/site-packages/twisted/internet/tcp.py", line 28, in
from twisted.internet._newtls import (
File "/Library/Python/2.7/site-packages/twisted/internet/_newtls.py", line 21, in
from twisted.protocols.tls import TLSMemoryBIOFactory, TLSMemoryBIOProtocol
File "/Library/Python/2.7/site-packages/twisted/protocols/tls.py", line 63, in
from twisted.internet._sslverify import _setAcceptableProtocols
File "/Library/Python/2.7/site-packages/twisted/internet/_sslverify.py", line 38, in
TLSVersion.TLSv1_1: SSL.OP_NO_TLSv1_1,
AttributeError: 'module' object has no attribute 'OP_NO_TLSv1_1'
Thank you!

Looks like versionitis of some type between Twisted, Python and the libssl being used. Perhaps using virtualenv would help narrow down the problem.

Hi, I would do whatever to help, I am not very experienced with virtualenv.
Pe 10 apr. 2017, la 05:51, Marc Sibson<EMAIL_ADDRESS>a scris:

Looks like versionitis of some type between Twisted, Python and the libssl being used. Perhaps using virtualenv would help narrow down the problem.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Android: Staging env file under releaseStaging with Code Push

On android, I have a two 3 env files:
.env -> for debug/local
.env.staging -> for staging environment
.env.production -> for production environment
The difference between the staging and production as basically the end points they use, but I can't get the react-native-config to read the staging file.
I also have 3 build type:

debug
release
releaseStaging

I'm using code push with different keys for release and releaseStaging variants.
Here is what I have in my build.gradle file for envConfigFiles:
project.ext.envConfigFiles = [
    releaseStaging : ".env.staging",
    release: ".env.production",
    anycustombuildlowercase: ".env",
]

When I build/run the app using variant releaseStaging
react-native run-android --variant=releaseStaging

I expect to use .env.staging file but it's using .env.production.
I think the issue is in dotenv.gradle file were we are looking at the flavour of the build and matching releaseStaging with release

I guess you're missing releaseStaging section in android/app/build.gradle
    buildTypes {
        debug {
            applicationIdSuffix ".debug"
            // Note: CodePush updates should not be tested in Debug mode as they are overriden by the RN packager. However, because CodePush checks for updates in all modes, we must supply a key.
            buildConfigField "String", "CODEPUSH_KEY", '""'
        }
        releaseStaging {
            minifyEnabled enableProguardInReleaseBuilds
            signingConfig signingConfigs.releaseStaging
            buildConfigField "String", "CODEPUSH_KEY", '"staging_key_here"'
        }
        release {
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
            buildConfigField "String", "CODEPUSH_KEY", '"production_key_here"'
        }
..

I was running in to the same issue. I tried the above and it didn't work. What eventually worked for me was changing
project.ext.envConfigFiles = [
    ...
    releaseStaging : ".env.staging",
    ...
]

To
project.ext.envConfigFiles = [
    ...
    stagingrelease : ".env.staging",
    ...
]

Then adding stagingrelease under buildtypes and running react-native run-android --variant=stagingrelease. They put emphasis on making all custom builds all lowercase. Not sure why it matters but using stagingrelease vs releaseStaging fixed it for me.

:+1:! @connercms solution above should work.
I think we compare variants in lowercase because depending on how you invoke Gradle the  names could be mixed up. We can probably enhance how we extract the variant to avoid this issue in 1st place, but not too familiar with Gradle to know 😬

@pedro any best practice?

Yeah react source expects the release token in the built variant or hilarity ensues:
def devEnabled = !targetName.toLowerCase().contains("release")
if (Os.isFamily(Os.FAMILY_WINDOWS)) {
    commandLine("cmd", "/c", *nodeExecutableAndArgs, "node_modules/react-native/local-cli/cli.js", "bundle", "--platform", "android", "--dev", "${devEnabled}",
            "--reset-cache", "--entry-file", entryFile, "--bundle-output", jsBundleFile, "--assets-dest", resourcesDir, *extraPackagerArgs)
} else {
    commandLine(*nodeExecutableAndArgs, "node_modules/react-native/local-cli/cli.js", "bundle", "--platform", "android", "--dev", "${devEnabled}",
            "--reset-cache", "--entry-file", entryFile, "--bundle-output", jsBundleFile, "--assets-dest", resourcesDir, *extraPackagerArgs)
}

So make sure you have the "release" token at the end of each custom variant.

Regarding @kodayashi comment, this is not entirely true anymore. React Native now has another option to toggle the release variant.
To use it, you must declare a project.ext.react at the top of your android/app/build.gradle file. An example usage looks like this:
project.ext.react = [
    ...

    // Staging build example
    devDisabledInStaging: true,
]

Notice the "Staging" suffix. It needs to match you build type.

project.ext.envConfigFiles = [
    debug : ".env.debug",
    release : ".env.release",
    releasestaging : ".env.staging"
]

To
project.ext.envConfigFiles = [
    debug : ".env.debug",
    releasestaging : ".env.staging",
    release : ".env.release"
]

just switch order of release and releasestaging
(releasestaging must be lowercase)


Query: GO:0036167 phenotypic switching in response to host

Hi @jlewsmith
The term GO:0036167 phenotypic switching in response to host specifically mentions Candida, "A reversible switch of a cell from one phenotype to another that occurs upon infection of a host or host cell. For example, Candida albicans switches from a unicellular form to an invasive multicellular filamentous form upon infection of host tissue. Phenotypic switching begins with changes in cell morphology and altered gene expression patterns and ends when the morphology of a population of cells has reverted back to the default state, accompanied by altered expression patterns.", but has no annotations.
Are there genes specifically involved in that process that can be annotated? Or is this using the same mechanism as the more general 'GO:0036166 phenotypic switching' , but other organisms can trigger the process?
Thanks, Pascale

Hi Pascale,
I think GO:0036167 phenotypic switching in response to host is more specific than it needs to be, seeing as the switching in response to host is largely restricted to Candida albicans. Other spp. are not obligate pathogens. GO:0036166 phenotypic switching is sufficient and obviously what we've been using to annotate. I think we could obsolete the former.
Best,
Jodi


Attempt at a pawn bar

Can't figure out the following:

How to make the colonists grayscale (drew on a red square just to distinguish - see image)
How to hook into the click/selection stuff. Just can't get any of it to trigger correctly.
How to show the selection indicator around the box.

Chucking this progress up if anyone wants to continue with it.
In the screenshot, the rightmost stored pawn is an enemy to show only colonists appearing in the bar.

Look at https://steamcommunity.com/sharedfiles/filedetails/?id=3019111152&searchtext=colony+bar to investigate integration.


Please add me to the organization.

What would you like to share?
I want to join EddieHubCommunity
Additional information
No response

Hey, @maskmanlucifer. We have an issue template for that. The bot will automatically invite you to the GitHub organization. Click here and choose the option below.

@schmelto, can you close this issue, please? Thanks. 🙂


[9.x] Add firstOrTap() Eloquent methods

Description
This PR adds a firstOrTap($closure, $attributes = []) method on the Eloquent Builder, BelongsToMany relation, HasManyThrough relation, and the HasOneOrMany relation.
When no existing model is found, a new instance is provided to the callback.
An optional array of attributes can be supplied in the second parameter as where clauses, which will pre-populate the new model instance's attributes if no model is found.
Purpose
These methods provide convenient encapsulation of logic that may obscure some of the outer logic.
Example
$user = User::where('...')->firstOrTap(function (User $User) {
    $user->fill(['...'])->save();
});

$meta = $book->metadata()->where('key', 'author')->firstOrTap(function (Metadata $meta) {
    $meta->fill(['key' => 'author', 'name' => 'John Doe'])->save();
});

Is so easy as, no?
$user = User::where('...')->firstOr(fn () => User::create($data));

Or using the firstOrCreate method.


[TableCell] Add align property to replace numeric.

This is mainly to gain the ability to center contents of a cell.
Referencing: https://github.com/mui-org/material-ui/issues/9117
I agree with an align key to replace numeric. We can have numeric override the align key if we want to retain backwards compatibility - or be a value for align: "left", "center", "right", "numeric"
I think this feature is still worth adding in. (14 upvotes on closed issue) I also agree that multiple boolean keys competing for priority doesn't make sense if we don't intend to be able use them at the same time.

@tendermario Thank you for raising your voice, I'm moving the discussion to #9117.


Why  marginLeft is invalid value when use Toggle component?

Problem description
Using Tgoogle compoent and config some style. the chrome console warn :
NaN is an invalid value for the marginLeft css style property. Check the render method of Paper
Steps to reproduce
const toggle = {
    toggle: {marginTop: '10px'},
    trackStyle: {height: '4px', width: '20px', marginTop: '6px', marginLeft: '0'},
    thumbStyle: {height: '10px', width: '10px', marginTop: '6px', marginLeft: '2px'},
    iconStyle: {width: '15px'},
    labelStyle: {color: 'rgba(120,120,120,0.7)'},
    rippleStyle: {height: '10px', marginTop: '10px'}
};

 <Toggle
     style={toggle.toggle}
     trackStyle={toggle.trackStyle}
     thumbStyle={toggle.thumbStyle}
     iconStyle={toggle.iconStyle}
     labelStyle={toggle.labelStyle}
     rippleStyle={toggle.rippleStyle}
  />

Versions

Material-UI: 0.15.2
React: 15.2.1
Browser:  52.0.2743.116 (64-bit)

By using chrome console react tool, I found

Toggle component contains Papar component,
the marginLeft always be null, even I config it still null, contrasting with with marginTop.
THX.

The bug is created by the following line I think: https://github.com/callemall/material-ui/blob/master/src/Toggle/Toggle.js#L210
The marginLeft is calculated according to the width of the thumbStyles.
Since your thumbStyles.width value is 10px (which is not a number), it results into 0 - '10px' which results into NaN.
The marginLeft can not be set via the actual property marginLeft but I think if you provide a numeric value of 10 to width the error will disappear.
Let me know if this resolves your issue.

We have been porting the component on the v1-beta branch. We reimplemented it from the ground-up. While we haven't tested it, I think that the issue is most likely fixed on that branch. Hence, I'm closing it.
Still, we will accept PR fixes until v1-beta takes over the master branch.


Linux Build isn't Solving

After building ethminer on Arch Linux with CUDA8, running the miner doesn't solve or submit any solutions to the specified pools, but there are no error messages.  I'm using the latest 370.28 drivers with two GTX 1070's.  It doesn't matter if I use CUDA or OpenCL, although OpenCL is slightly slower.  I've tried the Windows binary with the exact same switches and everything is fine.  Any ideas?

I can confirm the issue.
Up-to-date Archlinux, x86_64, up-to-date master, Dual AMD7950.
Stratum or eth-proxy.

I had the same problem some time ago. Upgraded my system in the beginning of October
and ethminer stopped to find solutions. After downgrading no problems.
Recently tried to find out the culprit and it seems to be related to crypto++: version 5.6.3-1 works,
with 5.6.4 and 5.6.5 no solutions.

Between 5.6.3 and 5.6.4 the sha3 implementation which is used in ethminer
was changed to fips 202 spec (some padding changes, see commit 844daf0e of cryptopp).
This implementation is not the one used for keccak and the ethminer does not work.

Experienced the same issue, and resolved it after manually installing https://archive.archlinux.org/repos/2016/04/30/extra/os/x86_64/crypto%2B%2B-5.6.3-1-x86_64.pkg.tar.xz

That worked for me.  How do I prevent a package from upgrading in Arch?  Are there plans to fix this in the future?


Simplify BitUtils methods

Couldn't help it. All tests still pass.

@grkvlt can you respond to @neykov's question "can you confirm signed vs unsigned shift", and then good to merge.

thanks @grkvlt, merging.


Ruby reimplementation and pushing limits

Based on tests written for my javascript explorations, i rewrote my solutions in ruby.
You can try it with ruby test2.rb "ruby csa2.rb" and ruby test3.rb "ruby csa3.rb"

ruby bench.rb "ruby csa2.rb"
Loading top stations
… done

Starting the application
… done

Loading the data
… done

Starting the benchmark
csa2.rb:135:in `compute': undefined method `<<' for nil:NilClass (NoMethodError)
	from csa2.rb:170:in `main'
	from csa2.rb:175:in `<main>'
bench.rb:11:in `consume_answer': undefined method `strip' for nil:NilClass (NoMethodError)
	from bench.rb:39:in `block in <main>'
	from bench.rb:37:in `each'
	from bench.rb:37:in `<main>'


IPCMessageWriter and IPCMessageWriter not available anymore

With the new version vscode-languageserver v7, both IPCMessageWriter and IPCMessageReader aren't available anymore. This is needed to create a connection over process.stdin and process.stdout. What's the workflow to do this with the new version?

@carmenberndt this is a breaking change caused by the split into common, node and browser. As document in the Readme (https://github.com/microsoft/vscode-languageserver-node/blob/master/README.md) you now need to import node specific API separately. The default import only imports the common API. The IPCMessageWriter and IPCMessageWriter are in vscode-jsonrpc\node or 'vscode-languageserver/node' if you develop a server.