ClickOnce Remote name could not be resolved

Hi
I created azure container like this:
az container create --resource-group ***
--name *** --image indrek.azurecr.io/dynamics-nav:2018
--registry-login-server *** --registry-username ***
--registry-password ***
-os-type Windows
--ip-address public --cpu 2 --memory 4 --dns-name-label nav2018w1democurrent
--ports 443 7046 7048 7049 8080
--environment-variables ACCEPT_EULA=Y username=*** password=*** ClickOnce=Y
Azure Container Registry indrek.azurecr.io/dynamics-nav:2018 based for Microsft Nav repo Microsoft/dynamics-nav:2018
When i run ClickOne istallation  from my local laptop i got error file like this:
PLATFORM VERSION INFO
Windows 			: 10.0.16299.0 (Win32NT)
Common Language Runtime 	: 4.0.30319.42000
System.Deployment.dll 		: 4.7.2556.0 built by: NET471REL1
clr.dll 			: 4.7.2633.0 built by: NET471REL1LAST_C
dfdll.dll 			: 4.7.2556.0 built by: NET471REL1
dfshim.dll 			: 10.0.16299.15 (WinBuild.160101.0800)
SOURCES
Deployment url			: file:///C:/Users/indrekt/Downloads/Microsoft.Dynamics.Nav.Client%20(3).application
Deployment Provider url		: http://6f0fc16bb646:8080/NAV/Win/Deployment/Microsoft.Dynamics.Nav.Client.application
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of C:\Users\indrekt\Downloads\Microsoft.Dynamics.Nav.Client (3).application resulted in exception. Following failure messages were detected:
+ Downloading http://6f0fc16bb646:8080/NAV/Win/Deployment/Microsoft.Dynamics.Nav.Client.application did not succeed.
+ The remote name could not be resolved: '6f0fc16bb646'
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
* The manifest for this application does not have a signature. Signature validation will be ignored.
OPERATION PROGRESS STATUS
* [10.04.2018 22:41:00] : Activation of C:\Users\indrekt\Downloads\Microsoft.Dynamics.Nav.Client (3).application has started.
ERROR DETAILS
Following errors were detected during this operation.
* [10.04.2018 22:41:03] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
- Downloading http://6f0fc16bb646:8080/NAV/Win/Deployment/Microsoft.Dynamics.Nav.Client.application did not succeed.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState, X509Certificate2 clientCertificate)
at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirect(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.FollowDeploymentProviderUri(SubscriptionStore subStore, AssemblyManifest& deployment, Uri& sourceUri, TempFile& tempFile, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl, Uri& deploymentUri)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
--- Inner Exception ---
System.Net.WebException
- The remote name could not be resolved: '6f0fc16bb646'
- Source: System
- Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
On some reason it cant solve IP address because error pointing to host name 6f0fc16bb646 but my nav container have public IP.
Br,
Indrek

I think this happens when you use Google Chrome, not sure why.
Could you try Edge or IE?

Same
Error are bit of diferent:
PLATFORM VERSION INFO
Windows 			: 10.0.16299.0 (Win32NT)
Common Language Runtime 	: 4.0.30319.42000
System.Deployment.dll 		: 4.7.2556.0 built by: NET471REL1
clr.dll 			: 4.7.2633.0 built by: NET471REL1LAST_C
dfdll.dll 			: 4.7.2556.0 built by: NET471REL1
dfshim.dll 			: 10.0.16299.15 (WinBuild.160101.0800)
SOURCES
Deployment url			: http://<IP_ADDRESS>:8080/NAV/Win/Deployment/Microsoft.Dynamics.Nav.Client.application
Server		: Microsoft-IIS/10.0
X-Powered-By	: ASP.NET
Deployment Provider url		: http://6f0fc16bb646:8080/NAV/Win/Deployment/Microsoft.Dynamics.Nav.Client.application
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://<IP_ADDRESS>:8080/NAV/Win/Deployment/Microsoft.Dynamics.Nav.Client.application resulted in exception. Following failure messages were detected:
+ Downloading http://6f0fc16bb646:8080/NAV/Win/Deployment/Microsoft.Dynamics.Nav.Client.application did not succeed.
+ The remote name could not be resolved: '6f0fc16bb646'
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
* The manifest for this application does not have a signature. Signature validation will be ignored.
OPERATION PROGRESS STATUS
* [10.04.2018 23:11:24] : Activation of http://<IP_ADDRESS>:8080/NAV/Win/Deployment/Microsoft.Dynamics.Nav.Client.application has started.
ERROR DETAILS
Following errors were detected during this operation.
* [10.04.2018 23:11:26] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
- Downloading http://6f0fc16bb646:8080/NAV/Win/Deployment/Microsoft.Dynamics.Nav.Client.application did not succeed.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState, X509Certificate2 clientCertificate)
at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirect(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.FollowDeploymentProviderUri(SubscriptionStore subStore, AssemblyManifest& deployment, Uri& sourceUri, TempFile& tempFile, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl, Uri& deploymentUri)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
--- Inner Exception ---
System.Net.WebException
- The remote name could not be resolved: '6f0fc16bb646'
- Source: System
- Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Ok, I made last try with http://nav2018w1democurrent.westeurope.azurecontainer.io:8080/NAV still same result or you  think it should working when i am make a and cname record form my own domain against container itself? 👍

if that is your public dns name you should add an environment variable:
--environment-variables PublicDnsName=nav2018w1democurrent.westeurope.azurecontainer.io
that might do it.

Sir I would like to report:
Site: http://nav2018w1democurrent.westeurope.azurecontainer.io:8080/NAV/ is up and running and allowing ClickOnce installation with my favorite browser (Google Chrome :))
I would suggest you to update https://github.com/Microsoft/nav-docker/blob/master/HOWTO.md on section Adding ClickOnce deployment of the Windows Client. I feel it is useful to add some explanation about --environment-variables PublicDnsName.
Also it is good idea to add extra section about list of useful environment variables with short explanations.
Tank you for supporting!

Good to hear, thanks

i found that there are issue with C Side client with ClickOnce installation hosted by Azure Container Instance
When I try to run table directly from development environment then it points to containerized hostname   e.g: 94abb3c9a34a instead value of PublicDnsName. Just added Picture to more explain.
Can we somehow change that behavior when deploying NAV docker container to Azure Container Instance?

Using the publicdnsname in CSIDE will most of the time be wrong.
Most VMs etc. will not have a pen SQL port and as such it will fail.


[LANG-1662] Create methods on ReflectionToStringBuilder to reflect only select fields

As commented in JIRA issue LANG-1662  and the mailing list (here and here), the class ReflectionToStringBuilder has methods to exclude fields from toString; If we have an object with several fields and want to reflect only some, we have to list all the fields that we don't want to reflect and pass to excludeFieldNames, or use the ToStringBuilder and call the method append with the keys and values.
To exemplify what I mean:

In a case where we need to print only the fields a,  b, and e from the class UseCase, the current solution is:

       Example example = new UseCase.Example();
       example.setA("test");
       example.setB(1);
       example.setC(1.1);
       example.setD(true);
       example.setE(false);
       example.setF(false);
       example.setG(true);

       ToStringBuilder toStringBuilder = new ToStringBuilder(example,
       ToStringStyle.JSON_STYLE);
       toStringBuilder.append("a", example.getA());
       toStringBuilder.append("b", example.getB());
       toStringBuilder.append("e", example.isE());
       System.out.println(toStringBuilder.build());

With these changes, the solution would be:
       Example example = new UseCase.Example();
       example.setA("test");
       example.setB(1);
       example.setC(1.1);
       example.setD(true);
       example.setE(false);
       example.setF(false);
       example.setG(true);

       ReflectionToStringBuilder reflectionToStringBuilder = new ReflectionToStringBuilder(example, ToStringStyle.JSON_STYLE);
       reflectionToStringBuilder.setSelectedFieldNames("a", "b", "e");
       System.out.println(reflectionToStringBuilder.build());

Both ways would generate the result {"a":"test","b":1,"e":false}, but there are some negative points while using ToStringBuilder:

We instantiate the ToStringBuilder with the object, but it's meaningless to the situation, as we need to set every key/value;
We can put whatever we want as attribute name and value, therefore it's not related to the object we want to print;
It's verbose; The more attributes we want to print, the more calls to append we need;

With the proposed solution, one has only to pass the field names as a parameter to reflect it.

Could anyone review this PR?

I will review later in the week.

Thanks, @garydgregory.

Hello @GutoVeronezi
Thank you for your PR.
The name setSelectedFieldNames1 is confusing because it is not symmetric (for lack of a better word) with setExcludeFieldNames, I think it would be best as setIncludeFieldNameswhich then is a bit odd since ALL fields are included by default, so there should be _clear_ documentation that usingsetIncludeFieldNames` overrides this default behavior.
The following behavior should throw an IllegalStateException IMO:
       ReflectionToStringBuilder reflectionToStringBuilder = new ReflectionToStringBuilder(example, ToStringStyle.JSON_STYLE);
       reflectionToStringBuilder.setIncludedFieldNames("a", "b", "e");
       reflectionToStringBuilder.setExcludedFieldNames("a", "b", "e"); // throws IllegalStateException?
       System.out.println(reflectionToStringBuilder.build()); // throws IllegalStateException?

IOW what does it mean to set a field as both included and excluded, does the "last API call win" or, does the code simply throw an IllegalStateException  if the include and exclude set intersect?

Hi, @garydgregory,
Thanks for the review, I'll address the changes regarding the feature name (setSelectedFieldNames -> setIncludeFieldNames) as well the documentation of its use.

Regarding the intersection between included and excluded, I see it as a complement rather than an intersection;  The current behavior of this class, as you said, is to include all fields by default. If we have a class with fields a, b and c and instantiate and reflect it, both of them will be reflected. If we set them in the excluded field names, the reflection will return empty:
import org.apache.commons.lang3.builder.ReflectionToStringBuilder;
import org.apache.commons.lang3.builder.ToStringStyle;

public class Test {

    private String a;
    private String b;
    private String c;

    public Test(String a, String b, String c) {
        this.a = a;
        this.b = b;
        this.c = c;
    }

    public static void main(String[] args) {
        Test test = new Test("this is field 'a'", "this is field 'b'", "this is field 'c'");
        ReflectionToStringBuilder reflection = new ReflectionToStringBuilder(test, ToStringStyle.JSON_STYLE);
        System.out.println(String.format("Before excluding: %s", reflection.build()));

        reflection = new ReflectionToStringBuilder(test, ToStringStyle.JSON_STYLE); // Recreating the object because once builded it caches the result.
        reflection.setExcludeFieldNames("a", "b", "c");
        System.out.println(String.format("After excluding: %s", reflection.build()));
    }

Result:
Before excluding: {"a":"this is field 'a'","b":"this is field 'b'","c":"this is field 'c'"}
After excluding: {}

In this example we're creating a complement of excluded (fields a, b and c) regarding set included (the default fields a, b and c), which will result in an empty set, or, in other words, nothing to reflect. The behavior per se will be the same, however, with this proposal, we'll be able to override the included set. Therefore, I think instead of throwing an exception, we should add an explanation in the documentation about it and let the users decide how to handle it.
If this is proposal is not valid and we proceed with the exception proposal, which cases should we consider to throw it? included and excluded are equal or just by having one field of included in excluded should throw an exception?

Hi @GutoVeronezi
You did not answer my question. See my code example; it should be one of your unit tests. I do not know (yet) what would be reasonable as the behavior.
@kinow , any thoughts?

Hi, @kinow,
Thanks for the review.
I fixed the bug with the exception and added more unit tests. I couldn't think in many other situations to validate; therefore, if you think in other use cases, just let me know and I create the tests.
Best regards,
Daniel

Hi, can anyone else review this PR?
Best regards,
Daniel

Codecov Report

Merging #849 (1e8b9de) into master (1bf7d7e) will increase coverage by 0.00%.
The diff coverage is 94.73%.

@@            Coverage Diff            @@
##             master     #849   +/-   ##
=========================================
  Coverage     91.71%   91.72%
- Complexity     7408     7422   +14
=========================================
  Files           188      188
  Lines         15900    15928   +28
  Branches       2994     3000    +6
=========================================
+ Hits          14583    14610   +27
- Misses          725      726    +1
  Partials        592      592

Impacted Files
Coverage Δ

...mmons/lang3/builder/ReflectionToStringBuilder.java
91.96% <94.73%> (+0.56%)
:arrow_up:

...in/java/org/apache/commons/lang3/BooleanUtils.java
94.82% <0.00%> (+0.28%)
:arrow_up:

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 1bf7d7e...1e8b9de. Read the comment docs.

Applied PR and:

Added missing @since tags to new public and protected methods and
fields
Fixed Javadocs
Reuse own ArrayUtils API for validation
Move methods to AB order

@garydgregory, I have a question, why close the PR and push the changes as if they were yours instead of merging the PR? I know that you referenced my PR in the commit message and so on, but for anybody that looks at the git history, the credits are yours. If you think that changes/amendments were necessary, you could have asked, and I would haply apply them. However, this way seems a bit odd. At least, quite different from the other OpenSource interactions I have had so far. Is this a common practice here in the commons-lang community?

Hi @GutoVeronezi
I had a quick look via GitHub UI and it is not showing you as co-author. When a maintainer needs to perform changes during the merge, it is common practice here in Commons (also in other OSS projects), to squash/rebase/edit commits.
I think maybe @garydgregory was trying that but accidentally replaced authorship? Normally both original author & Commons maintainer appear as the authors of the commits. We can edit that commit's authorship & push-force if necessary, but let's wait for @garydgregory 's reply to confirm if that was really the case :+1:
Thanks!
Bruno

Hi, @kinow, thanks for the reply.
@garydgregory, it feels a bit weird for us here on the other side proposing things to contribute back to commons-lang and interacting with reviewers to see somebody "taking over the changes". If the PR is missing something or there is a better way to do something, I would expect the reviewers to point what can be improved, or at least it being merged with some changes/rebase and so on (as described by @kinow https://github.com/apache/commons-lang/pull/849#issuecomment-1175649542). This way of applying the changes (closing the PR and pushing it as yours, without co-authoring) discourages new contributors, because we do not receive the credit for all the work we did (neither in Git history nor in GitHub Insights).
Anyways, thanks for accepting my changes, I will now work on our side to use the new release of commons-lang as soon as it is released.


Missing config.py and user_config.py files

In most script are the following lines
import config
import user_config

The problem is there are no such files in the repo! So I don't know how to create them from scratch.
Could someone please share the correct files so I can try running "inference.py" on my computer? Thanks!

Did you get the files? @steve3nto

Are these files available?

I also meet the problem of the absence of the two files. Please help. @CF2220160244

Could someone share the config files? Thanks @JadTawil-theonly @ranandalon @xllau @CF2220160244 @steve3nto

after doing some research of the code, indeed these two files are the missing link for running inference.py
I would summarize the variables needed to fillin the blanks as below:
config.py:
working_dataset =
strided =
gpu_memory_fraction =
colors =
autoencoder = 'ResNet' # or 'SegNet'
user_config.py:
autoencoder = 'ResNet' #or 'SegNet'
May be we can use divide and conquer to reconstruct the above two files..... Anyone would like to give a try? Let me know if I can be of help. I think the most complicated one is colors and working_dataset. The others may be just a number.

it seems the inference.py is not distilled enough to just run on input images: for example, if you trace the code
input_img[ind], gt = dh.get_data(ind, 'val')
still asking for ground truth files which are not needed....
I modified inference.py to get rid of not needed files and generate my "guessing" config.py and user_config.py, then I am able to run through inference.py (not without hiccop though, but solveable). Good luck for whoever would like to try it.
You may download config files here: (warning: this is not from author and it's my pure guessing...)
mtl_config_files.zip


Class NumberFormatter not found after installation

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
1.5.1
Issue Description
I've installed the PHP intl extension and checked using
PHP -m

command, it is successfully installed but not working on my Ubuntu 20.04
Preconditions
OS: Ubuntu 20.04
PHP 8.1
Steps to reproduce
Just install fresh Bagisto and login to the admin dashboard
Expected Result
It should be login successfully
Actual Result
Getting error
Class NumberFormatter not found.
ss attached
Screenshots

Additional context
No response

Install Intl extension, refer to the following issues for more info
Duplicate of #6218, #6050, #4012


Update terms-of-use.md

Added a new url in the Q&A section since the endpoint will have updated URL. The old url: https://account.activedirectory.windowsazure.com will be removed later in Jan 2023 or once the deployment is completed.

Learn Build status updates of commit a9dd993:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/active-directory/conditional-access/terms-of-use.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


weex -v提示未安装

node -v
v8.11.1
npm -v
6.0.0

@JimmyKent Try to use npm@4 to install weex-toolkit or re-install your node environment, that seems your environment cause it.


[Bug] "Extra Chaos Damage" being displayed as "Converted Chaos Damage"

The Gain #% of Physical Damage as Extra Chaos Damage modifier is not displaying correctly on the "Calcs" screen. The actual damage calculation appears to be correct. The program appears to be incorrectly displaying Gain #% of Physical Damage as Extra Chaos Damage as #% of Physical Damage Converted to Chaos Damage.
Version: 1.3.18
Steps to reproduce:

Create a new build
Add Ming's Heart, Amethyst Ring as an equipped item
Add Shockwave Totem as an active skill

Observed behavior:
When hovering over the "Skill Hit Damage" row in the "Chaos" column of the "Skill Hit Damage" table, the pop-up tool-tip incorrectly states that 20% of our physical damage is being converted to chaos damage.  However, the damage appears to be calculated correctly. This can be seen by observing only the physical damage (231-429) and removing all equipped items. The physical damage value will not change, but the total skill hit damage will change.
This same behavior can be observed using any combination of Ming's Heart, Amethyst Ring and/or Obliteration, Demon's Horn.

This is not a bug. "Gain as X" and "Convert to X" are both types of damage conversion; they use exactly the same mechanics and calculation code, except that "Convert to X" also reduces the final damage total of the source type. Consequently, they are combined together under the "Conversion" heading, and in fact it's not possible to list them separately, as they are combined long before the hit damage calculation occurs (which is when the table in the breakdown is populated).
I do agree that it can be misleading, but it merely reflects the underlying mechanics of the damage calculations, and some understanding of those mechanics will always be necessary if you are to correctly interpret the output of the hit damage calculations (especially when conversions are involved).

After considering what you said and reading the wiki page carefully, I understand why you have chosen to represent the conversion in such a confusing manner. It is a shame that the terminology is so convoluted between "converted to" and "conversion to". Surely there must be a better way of representing the information! I mean, just look at this mess:
Initial physical damage (200)
-Converted to Chaos (50% of dmg)
-Added as Chaos (25% extra dmg)
-Total conversion to Chaos (75% of dmg)
Final Physical damage (100 dmg)
dispite "75%" conversion to chaos"
Initial Chaos damage (0 dmg)
Final Chaos damage (150 dmg)
-Converted from physical (100% of dmg)
dispite "75%" conversion to chaos.


Fix typo and return value in doc

https://github.com/elixir-ecto/ecto_sql/blob/5a2978918a81d584a2fa2d94abb77e4f96b808cc/integration_test/myxql/storage_test.exs#L198-L199
As the above code part shows the output should be a tuple in the doc.
Thank you for reviewing.

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


"Pull and redeploy" not redeploying (in certain cases)

I'm building an image like this with my acorn-cli pointing to my acorn.io account.
acorn build -t my_app
Then I deployed my app with this:
acorn run -s my-secrets:my-secrets -n my-app-pro --memory=2Gi
After that I can't seem to pull and redeploy. I will build again, but if I click "Pull and ReDeploy" on the acorn.io UI nothing happens. Same too for the acorn update --pull my-app-pro command.
It seems that on the run command there is an implicit push to an unspecified repo which is perhaps not happening when I use only build or update.
If I've deployed my app this way, is there a way to update the image without deleting and calling run again?

@randall-coding In your case , if you had deployed the app from the image  my_app (that you had built) , then building the image  my_app again and using acorn update --pull my-app-pro would result in the app being deployed with the new version of the image.

acorn build -t my_app
acorn run -s my-secrets:my-secrets -n my-app-pro my_app --memory=2Gi -> Deploy app withe image my_app
Make changes and build
acorn build -t my_app
 acorn update --pull my-app-pro

If the app was deployed using the current directory then you can use acorn run --update to update the app.

acorn run -s my-secrets:my-secrets -n my-app-pro --memory=2Gi
Make changes in the current directory
acorn run --update -s my-secrets:my-secrets -n my-app-pro --memory=2Gi  --> This will result in app being deployed with the latest changes made in step 2.


Compound het should look at VEP impact on canonical only, not highest impact across all transcripts

Why is that? It makes sense that we want to consider VEP impact of both variants in the compound het from the same transcript, but why would it need to be the canonical?

Agreed.

Seems we agree the current behavior is fine. I'm closing


Inconsistent operand order for logarithm to base x

Behavior of logarithm to base x
The first operand entered (or previous result) is the base, the second operator is the anti-logarithm (i.e. the number of which the logarithm is calculated).
e.g.: "16   base log   2" yields 0.25 instead of the expected value 4.

Behavior of similar operators
For exponentiation (xy) the first operand is the base and the second operand is the exponent.
For the n-th root (x1/y) the first operand is the radicand and the second operand is the index.

The behavior of the logarithm (logx(y)) is inconsistent to similar binary operators and also to the GUI, which shows logy(x). Furthermore this behavior does not allow to take the logarithm to base x of a previous result.

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

Good catch! We want to be consistent with other operators. With logy(x), the first operand should be x, and the second y, but it is currently flipped, as you describe.


Update plugins June 2024

List of updates.
Advanced Custom Fields PRO
Faust.js™
Microsoft Start
Pantheon Advanced Page Cache
SVG Block
WPGraphQL
Yoast SEO

Hey @brandonhundt this update has updates for WPGraphQL and Faust.js™ Maybe it will be good to make a test with the frontend before merging it.


Changes "Create" method to "PostTodoItem" method

Fixes #13727

The scaffolder creates PostTodoItem and we should too. See Examine the PostTodoItem create method

@mattielee Thank you for the PR. I don't understand the value of changing the method name. It could be that I'm overlooking something obvious. Can you please help me understand?

I agree with @scottaddie . If we were to rewrite this, PostTodoItem would be a better choice because it's consistent with the scaffolder. Let me know if you've got a good reason to accept this PR and we'll reopen/reconsider.


Improve https://docs.fedimint.org/

It's pretty bare right now.
We should:

[x] make it possible to customize the index page (@dpc) #4624
[ ] write a nice introduction what is it for, what to expect, with links to other materials, which are the main crates to look, what are the main binaries
[ ] add module level rustdoc comment to main crates
[ ] link to https://docs.fedimint.org/ from README via badge, and explicit link

After #4624 , the rest should be editing ./docs/rustdoc-index.md, *.rs files and linking things around.


Fix login page and redirect URL after signup

Feature

Change login and signup opacity
Fix google login button
Fix OAuth signup redirect

Solution

overwrite get_signup_redirect_url library function in adapter.py
change soem html in signup and login page

How to test?

go to login and register page. And try to sign up

Screen shot

Codecov Report

Merging #40 (e031758) into beta (dcfe5e8) will increase coverage by 3.00%.
The diff coverage is 36.36%.

@@            Coverage Diff             @@
##             beta      #40      +/-   ##
==========================================
+ Coverage   81.74%   84.74%   +3.00%
==========================================
  Files          17       18       +1
  Lines         378      577     +199
  Branches       26       42      +16
==========================================
+ Hits          309      489     +180
- Misses         51       80      +29
+ Partials       18        8      -10

Impacted Files
Coverage Δ

users/adapter.py
38.88% <36.36%> (-11.12%)
:arrow_down:

trip/admin.py
100.00% <0.00%> (ø)

threpose/settings.py
100.00% <0.00%> (ø)

trip/forms.py
100.00% <0.00%> (ø)

trip/models.py
83.67% <0.00%> (+0.34%)
:arrow_up:

trip/tests.py
91.72% <0.00%> (+5.23%)
:arrow_up:

trip/views.py
79.04% <0.00%> (+8.63%)
:arrow_up:

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 dcfe5e8...e031758. Read the comment docs.


copy current URL?

I might have missed it in the documentation, but is there a way to copy the current URL? Thanks

I'll add this feature in a release that should be out today or tomorrow. Thanks!

I've released Version 1.15, which contains this feature (mapped to y, y) and several bug fixes. It should be available on the Chrome web store shortly.


chore: release main

:robot: I have created a release beep boop
auto-instrumentations-node: 0.39.3
0.39.3 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

dependencies

@opentelemetry/instrumentation-amqplib bumped from ^0.33.1 to ^0.33.2
@opentelemetry/instrumentation-aws-lambda bumped from ^0.37.0 to ^0.37.1
@opentelemetry/instrumentation-aws-sdk bumped from ^0.36.0 to ^0.36.1
@opentelemetry/instrumentation-bunyan bumped from ^0.32.1 to ^0.32.2
@opentelemetry/instrumentation-cassandra-driver bumped from ^0.33.1 to ^0.33.2
@opentelemetry/instrumentation-connect bumped from ^0.32.1 to ^0.32.2
@opentelemetry/instrumentation-cucumber bumped from ^0.1.0 to ^0.1.1
@opentelemetry/instrumentation-dataloader bumped from ^0.5.1 to ^0.5.2
@opentelemetry/instrumentation-dns bumped from ^0.32.2 to ^0.32.3
@opentelemetry/instrumentation-express bumped from ^0.33.1 to ^0.33.2
@opentelemetry/instrumentation-fs bumped from ^0.8.1 to ^0.8.2
@opentelemetry/instrumentation-fastify bumped from ^0.32.2 to ^0.32.3
@opentelemetry/instrumentation-generic-pool bumped from ^0.32.2 to ^0.32.3
@opentelemetry/instrumentation-graphql bumped from ^0.35.1 to ^0.35.2
@opentelemetry/instrumentation-hapi bumped from ^0.33.0 to ^0.33.1
@opentelemetry/instrumentation-ioredis bumped from ^0.35.1 to ^0.35.2
@opentelemetry/instrumentation-knex bumped from ^0.32.1 to ^0.32.2
@opentelemetry/instrumentation-koa bumped from ^0.36.0 to ^0.36.1
@opentelemetry/instrumentation-lru-memoizer bumped from ^0.33.1 to ^0.33.2
@opentelemetry/instrumentation-memcached bumped from ^0.32.1 to ^0.32.2
@opentelemetry/instrumentation-mongodb bumped from ^0.37.0 to ^0.37.1
@opentelemetry/instrumentation-mongoose bumped from ^0.33.1 to ^0.33.2
@opentelemetry/instrumentation-mysql bumped from ^0.34.1 to ^0.34.2
@opentelemetry/instrumentation-mysql2 bumped from ^0.34.1 to ^0.34.2
@opentelemetry/instrumentation-nestjs-core bumped from ^0.33.1 to ^0.33.2
@opentelemetry/instrumentation-net bumped from ^0.32.1 to ^0.32.2
@opentelemetry/instrumentation-pg bumped from ^0.36.1 to ^0.36.2
@opentelemetry/instrumentation-pino bumped from ^0.34.1 to ^0.34.2
@opentelemetry/instrumentation-redis bumped from ^0.35.1 to ^0.35.2
@opentelemetry/instrumentation-redis-4 bumped from ^0.35.1 to ^0.35.2
@opentelemetry/instrumentation-restify bumped from ^0.34.0 to ^0.34.1
@opentelemetry/instrumentation-router bumped from ^0.33.1 to ^0.33.2
@opentelemetry/instrumentation-socket.io bumped from ^0.34.1 to ^0.34.2
@opentelemetry/instrumentation-tedious bumped from ^0.6.1 to ^0.6.2
@opentelemetry/instrumentation-winston bumped from ^0.32.1 to ^0.32.2
@opentelemetry/resource-detector-alibaba-cloud bumped from ^0.28.1 to ^0.28.2
@opentelemetry/resource-detector-aws bumped from ^1.3.1 to ^1.3.2
@opentelemetry/resource-detector-container bumped from ^0.3.1 to ^0.3.2
@opentelemetry/resource-detector-gcp bumped from ^0.29.1 to ^0.29.2

auto-instrumentations-web: 0.33.2
0.33.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

dependencies

@opentelemetry/instrumentation-document-load bumped from ^0.33.1 to ^0.33.2
@opentelemetry/instrumentation-user-interaction bumped from ^0.33.1 to ^0.33.2

contrib-test-utils: 0.34.2
0.34.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-amqplib: 0.33.2
0.33.2 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

instrumentation-aws-lambda: 0.37.1
0.37.1 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-aws-sdk: 0.36.1
0.36.1 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

dependencies

@opentelemetry/propagation-utils bumped from ^0.30.1 to ^0.30.2

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

instrumentation-bunyan: 0.32.2
0.32.2 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-cassandra-driver: 0.33.2
0.33.2 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

instrumentation-connect: 0.32.2
0.32.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-cucumber: 0.1.1
0.1.1 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-dataloader: 0.5.2
0.5.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-dns: 0.32.3
0.32.3 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-document-load: 0.33.2
0.33.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-express: 0.33.2
0.33.2 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-fastify: 0.32.3
0.32.3 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)
fastify: Use plugin name for middleware span name (#1680) (4503d3e)
instrumentation-fastify: add tav script (#1710) (52dd42d)
Removed deprecated properties usage in Fastify instrumentation (#1679) (d3328f8)

instrumentation-fs: 0.8.2
0.8.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-generic-pool: 0.32.3
0.32.3 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-graphql: 0.35.2
0.35.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-hapi: 0.33.1
0.33.1 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-ioredis: 0.35.2
0.35.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

instrumentation-knex: 0.32.2
0.32.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-koa: 0.36.1
0.36.1 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-long-task: 0.33.2
0.33.2 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-lru-memoizer: 0.33.2
0.33.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

instrumentation-memcached: 0.32.2
0.32.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

instrumentation-mongodb: 0.37.1
0.37.1 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

instrumentation-mongoose: 0.33.2
0.33.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

instrumentation-mysql: 0.34.2
0.34.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

instrumentation-mysql2: 0.34.2
0.34.2 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

instrumentation-nestjs-core: 0.33.2
0.33.2 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-net: 0.32.2
0.32.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-pg: 0.36.2
0.36.2 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

instrumentation-pino: 0.34.2
0.34.2 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-redis: 0.35.2
0.35.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

instrumentation-redis-4: 0.35.2
0.35.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

instrumentation-restify: 0.34.1
0.34.1 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-router: 0.33.2
0.33.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-socket.io: 0.34.2
0.34.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

instrumentation-tedious: 0.6.2
0.6.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

instrumentation-user-interaction: 0.33.2
0.33.2 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

instrumentation-winston: 0.32.2
0.32.2 (2023-10-10)
Bug Fixes

deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

@opentelemetry/propagation-utils: 0.30.2
Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

@opentelemetry/resource-detector-alibaba-cloud: 0.28.2
Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

@opentelemetry/resource-detector-aws: 1.3.2
Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

resource-detector-container: 0.3.2
0.3.2 (2023-10-10)
Bug Fixes

Update defect of of wrong resource attribute of "container.id" (#1682) (5675c49)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

resource-detector-gcp: 0.29.2
0.29.2 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

resource-detector-instana: 0.5.2
0.5.2 (2023-10-10)
Bug Fixes

deps: update all patch versions (#1687) (47301c0)
deps: update otel core experimental to v0.43.0 (#1676) (deb9aa4)
deps: update otel core experimental to v0.44.0 (#1725) (540a0d1)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.34.1 to ^0.34.2

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/resource-detector-aws-v1.3.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/resource-detector-gcp-v0.29.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/resource-detector-instana-v0.5.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/auto-instrumentations-node-v0.39.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/propagation-utils-v0.30.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/contrib-test-utils-v0.34.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-amqplib-v0.33.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-dataloader-v0.5.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-lru-memoizer-v0.33.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-mongoose-v0.33.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-socket.io-v0.34.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-aws-lambda-v0.37.1 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-bunyan-v0.32.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-cassandra-driver-v0.33.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-dns-v0.32.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-express-v0.33.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-fastify-v0.32.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-generic-pool-v0.32.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-hapi-v0.33.1 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-ioredis-v0.35.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-knex-v0.32.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-koa-v0.36.1 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-memcached-v0.32.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-mongodb-v0.37.1 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-mysql-v0.34.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-mysql2-v0.34.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-nestjs-core-v0.33.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-net-v0.32.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-pg-v0.36.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-pino-v0.34.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-redis-v0.35.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-redis-4-v0.35.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-restify-v0.34.1 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-router-v0.33.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-document-load-v0.33.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-user-interaction-v0.33.2 :sunflower:


Fetching doesnt work since 2 days

The bot has not fetched any news for 2 days (according to the log). Was there again a change in the Google News structure?

I have tested get_news() and search() function, it seems both are working properly. Probably you need to check your IP is not being blocked or challenged by Google with robot verification

The problem hasn't been solved yet, the news we got still empty @HurinHu would you please check again?
thanks a lot!

The problem hasn't been solved yet, the news we got still empty @HurinHu would you please check again?
thanks a lot!
I tried again with latest version, both functions are working fine.

@HurinHu  Thanks for update, I upgraded my package version to 1.6.10 and seems to be work but the URL is containning so many extra stuffs which we can access the URL properly, would you able to take a look?
Thanks so much


Remove unnecessary files from bower

Currently c3 bower component includes lots of unnecessary stuff like src, spec, examples and unrelated config files. This PR removes them.

@shuhei Fantastic! I figured the Bower package could use some optimisation!
PR looks good to me; feel free to merge at will, @masayuki0812! :+1: :shipit:

You're right. Thank you very much!!!

Thanks for merging!


Create convenience XRayRecorder initializer with EventLoop for XRayUDPEmitter

FYI, you may want to follow this pattern for EventLoopGroupProvider, we've been using it consistently in newer sswg libs.
https://github.com/swift-server/async-http-client/blob/c9a9bf061d713c91ee9974fa8a6afe413acfd0e9/Sources/AsyncHTTPClient/HTTPClient.swift#L737-L743
Example / docs https://github.com/swift-server/async-http-client/blob/9c1c62b183036884332c2cfa2a526b4fa59b9ffe/README.md#request-response-api

@ktoso
thank you for the references, I have seen it in a few places (in fact its already defined in UDPClient
) and will use it for consistency
having said that I think it would be very convenient if SwiftNIO defined it and promoted it in such way
currently different libraries implement (copy and paste) the same enum in different namespaces.
In my case I will need to create the enum twice (once in public XRayUDPEmitter and once in internal UDPClient) and map them  (will add inline comment to illustrate it when its implemented)


two refresh buttons when playwright and python extensions are enabled

Does the python button work for you?

In the linked issue, there is a now standard API for this which will be stable in our next release (<= 14 days from today)

Yeah, I am also seeing to Refresh buttons. If I press on it I am getting an error talking about pytests

Talking about getting an error message, I need to see the full-form of the message or I can't fix it!


minimal number of loops for pile-up analysis

Hi,
When I do the pile-up analysis on a loop file (about 177 loops), coolpuppy reports the following error:
"ValueError: No chromosomes are in common between the coordinate file/anchor and the cooler file. Are they in the same format, e.g. starting with "chr"? Alternatively, all regions might have been filtered by distance/size filters."
However, when I apply same parameters to another loop file with same format (about 509 loops), it's ok.
So I am wondering what's the minimal number of loops for pile-up analysis?
Looking forward to your helpful reply.
Qiang

Hi Qiang,
That's strange, this shouldn't happen! Could you share some more details? What do your files look like? Do you mind sharing them?

Hi Phlya,
Thanks for your kindly reply.
Here is my input loop file (bedpe):
1       28960000        28970000        1       29100000        29110000
2       171780000       171790000       2       172010000       172020000
2       196520000       196530000       2       196930000       196940000
2       219120000       219130000       2       219260000       219270000
2       231910000       231920000       2       232310000       232320000
2       242600000       242610000       2       242820000       242830000
3       11680000        11690000        3       11880000        11890000
3       12520000        12530000        3       12700000        12710000
3       13690000        13700000        3       13930000        13940000
3       13930000        13940000        3       14160000        14170000
And here is code for pile-up analysis:
coolpup.py hic.cool input_loop.bed --nshifts 10 --unbalanced --coverage_norm --mindist 100000 --outname output.txt
Best,
Qiang

Is it tab delimited? What are the chromosomes stored in the cooler you are working with?

Yes, it's tab delimited.
I think chromosome is not the point. Because another loop file has same format as previous one, and it uses the same cooler for pipe-up analysis.

By the way, all the loop file with row number around or less than 200 will raise this error.

OK, it shouldn't happen, and works for me with the latest version for any small number of loops using the latest version from GitHub - even with 20 loops, and even when no loops pass the distance filters, so I get an output with all zeros. Can you try the latest version please? This could have cause problems if some chromosomes had no loops in them, but it would have raised a different error...

OK, I will try the latest version of coolpuppy. Thanks for your kindly help!

How are you getting on? Did the new version fix your issue?

Sorry for my later reply. The new version solved my problem. Thank you!


Remove deprecated PP legacy_custom_rules

The legacy_custom_rules in iris.fileformats.rules were deprecated in v1.9 and made life unnecessarily difficult in #2059. As the functionality has served its deprecation period, let's just remove it for v1.10.

@bjlittle FYI it's just pesky timeout exceptions that are now stopping the tests from passing :unamused:

Hi @dkillick
what is the purpose of the file:
.idea/uiDesigner.xml
please?

@marqh that's a file for an IDE, which should not have been included in the commit. Frankly, I'm surprised it was; I'll get rid of it.

The legacy_custom_rules in iris.fileformats.rules were deprecated in v1.9 and made life unnecessarily difficult in #2059. As the functionality has served its deprecation period, let's just remove it for v1.10.

I think this may be a bit hasty.  There is user feedback regarding use of this feature which we are managing.
It may be less disruptive to remove this at a later version than 1.10.
I'm not sure about this, but I think we should consider it

@dkillick - I think we need to understand where this one is at. Do we need it for 2.0? Can we close this PR altogether? etc.
Would you mind providing a status update?

The legacy_custom_rules were actually removed in #2778... think this is done.


[SPARK-4452][SPARK-11293][Core][BRANCH-1.6] Shuffle data structures can starve others on the same thread for memory

What changes were proposed in this pull request?
This PR is for the branch-1.6 version of the commits PR #10024.
How was this patch tested?
unit tests

cc @davies @JoshRosen

Test build #58238 has started for PR 13027 at commit 42a8701.

Test build #58238 has finished for PR 13027 at commit 42a8701.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58238/
Test PASSed.

This PR includes the commit PR #13020 for the branch-1.6 version too.

This pr is great for us, solved some ExecutorLost problems for branch-1.6.
this includes the commit PR #13020 for the branch-1.6 version too?

ping @davies @JoshRosen

@davies , could you review this pr and merge it?

@lianhuiwang This is not a fix for bug or regression in 1.6, so we may not merge this into 1.6.
We could re-visit this if we plan to have another release for 1.6.

@davies  Thanks. Many people said they need it for 1.6 in issue, So I submit this PR.

@lianhuiwang This PR is useful, other people could easily patch it by themselves, thanks for it.

Test build #59141 has started for PR 13027 at commit 42a8701.

Test build #59141 has finished for PR 13027 at commit 42a8701.

This patch fails build dependency tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59141/
Test FAILed.

@davies  Why haven't we pulled this into branch 1.6?   can we upmerge and pull in so that if we do 1.6.3 its there?

@tgravescs For minor releases, we (the community) usually do not put much effort on the QA, it's risky to pull in large change (like this one) it. At least, I don't have enough confidence to merge this one. Sorry for that.


Filter "ClassDescriptor Failed to Learn" errors

Makes sense. I changed it to be more specific.

thanks!


investigate why reshape creates new tensors

Reported initially by @owulveryck

I'll give some explanation for the record:
The Op interface specifies a OverwritesInput() int  method.

// overwriteInput() is a method which states which input the output will be overwriting.
// This allows for some efficiency gains as the underlying arrays wouldn't have to be re-allocated.
// The method returns an int instead of a bool because potentially different operations may be allowed
// to overwrite certain inputs. For example, consider an operation to increment a value:
// the IncrementOp would be a unary operator, and assuming we would like to overwrite the input,
// the retVal of overwriteInput() will be 0 (inputs[0]).
// -1 is returned if overwriting of input is disallowed

The reshapeOp's overwriteInput() method returns 0, which means that the input of the operator can be modified:
https://github.com/gorgonia/gorgonia/blob/d84fc3e8c3f7051e07e9bca7e233d7c2caea3ac1/op_tensor.go#L1167
The Do(...) method of the reshape operator creates new value by cloning its input, which implies that the original data will not be modified:
https://github.com/gorgonia/gorgonia/blob/d84fc3e8c3f7051e07e9bca7e233d7c2caea3ac1/op_tensor.go#L1145
I don't understand if this a mistake or if there is something under the hood that impose this. In this case, we should, at least, document it.

I made a simple quick-and-dirty patch to test with a ShallowClone if the Value is a *tensor.Dense
diff --git a/op_tensor.go b/op_tensor.go
index ec582e9..15b8f0e 100644
--- a/op_tensor.go
+++ b/op_tensor.go
@@ -1142,9 +1142,19 @@ func (op reshapeOp) Do(vals ...Value) (Value, error) {
        }
        var val Value
        var err error
-       if val, err = CloneValue(vals[0]); err != nil {
-               return nil, errors.Wrapf(err, cloneFail, vals[0])
+       switch vals[0].(type) {
+       case tensor.Tensor:
+               if v, ok := vals[0].(*tensor.Dense); ok {
+                       val = v.ShallowClone()
+               } else {
+                       if val, err = CloneValue(vals[0]); err != nil {
+                               return nil, errors.Wrapf(err, cloneFail, vals[0])
+                       }
+               }
+       default:
+               return nil, errors.Errorf(nyiTypeFail, "reshape.Do", "Non tensor")
        }
+
        if !val.Shape().Eq(op.from) {
                return nil, errors.Errorf("Shape mismatch. Input shape is %v. Expected %v", val.Shape(), op.from)
        }

The tests are ok, and the bench I run on the tiny yolo v2 model with onnx are a lot better:
benchcmp /tmp/tinyyolo-master.bench /tmp/tinyyolo-new-reshape.bench
benchmark          old ns/op     new ns/op     delta
BenchmarkRun-4     960358292     957275056     -0.32%

benchmark          old allocs     new allocs     delta
BenchmarkRun-4     37528          37572          +0.12%

benchmark          old bytes     new bytes     delta
BenchmarkRun-4     343268306     179500499     -47.71%

I should test that this has no impact on the gradient computation, but I don't know how to do that.

This issue can  now be closed as @owulveryck had pushed through the changes


add is_crdt convenience fn

Convenience fun related to @seancribbs's comment on https://github.com/basho/yokozuna/pull/452#discussion-diff-24717256. If there's a better name for this fun, I'll update it accordingly :).

Looks good to me, although a unit test wouldn't hurt.

Yeah... I'm basically testing it for the use-case here, https://github.com/basho/yokozuna/pull/452/files#diff-a765b250cdc4d78ac1eef6cfddbbb280R508, but I'll add a unit test.

Thanks, I think a unit test here is needed. Just something simple, meck out riak_core_bucket and return buckets for all the datatypes, some datatype=nonsense, and some no datatype is exhaustive.

:+1: 9f17bcc

@borshop merge


Can't set bar-progress-empty to a single space

I tried bar-progress-empty = " ", but that didn't work. It just printed a bunch of raw " everywhere.

that's an easter egg.

:D
what if I'm ... allergic to, uh, egg protein?

hehe, I'll have a look

If it helps, I'm fairly sure I remember it working in 2.3.(8|9).

think I broke it with d34263d but now it should apply to all text labels


Image Resizer - Resize picture - Useless warning message about the .bak file

#873  ℹ Computer information

PowerToys version: 0.23.0
PowerToy Utility: Image Resizer
Running PowerToys as Admin: No
Windows build number: W10 19041.508

📝 Provide detailed reproduction steps (if any)

Right Click on a picture
Run "Resize Pictures"
Set options as following

Click "Resize"

✔ Expected result
The Image is resized
❌ Actual result
A warning message pop-up informing that the file (.bak.) is already used by a program.
I need to validate with "Retry" on this window. After that, the resize is done!

@Spb8Lighting I think that image was being used by another program before you retried it

@Spb8Lighting I think that image was being used by another program before you retried it

You're right, It is inside a "Dropbox" shared folder, and out of this shared folder, I don't get this warning message.


Instance: convert qemuCPU plus a few other simple templates

Convert qemuCPU which contains a fairly complex template logic, plus a few other very simple templates. After this one I will send a PR with the remaining templates.

This pull request didn't trigger Jenkins as its author isn't in the allow list.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"


[WIP] Adds default custom Head component

Includes the default custom Head component in Enhance starter projects.
Docs updated here: https://github.com/enhance-dev/enhance.dev/pull/140
Changes to arc-plugin-enhance forthcoming.

@kristoferjoseph Done! :)


Deprecate cupy.bool, cupy.int, cupy.float and cupy.complex

Resolve #4755

Rebased.

pfnCI, test this please.

Jenkins CI test (for commit 9dae95b863a4445ae3526197740458708d7bae17, target branch master) succeeded!


Run Istio control plane on VM

Describe the feature request
We need to get istio runninng on VM, in addition to k8s to break the viewpoint where folks had that istio is just for k8s.
In https://github.com/istio/istio/issues/13259, we described a desire to install istio from istioctl without reading docs.
While install from istioctl is nice, there is also a need for users to understand what binaries user needs to install if they choose to wire it up manually themselves with their existing system like Systemd or Chef or Ansible.  This WI is to track the binaries and manual steps.
Describe alternatives you've considered
There isn't much docs on this today from istio.io
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[x ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Additional context
Based on feedback from Istio steering meeting today with @kelseyhightower cc @louiscryan @dcberg @sven @oaktowner @ssuchter cc @rshriram @rvennam @geeknoid

think @costinm is working on this via Istiod :)


Add option to limit output id length

what

Adds a new optional variable max_id_length, that when set to a value greater than 0 will limit the length of ID output to given value.
The truncated ID is still disambiguated by suffixing the first 5 characters of the md5 hash of the full ID.
The full ID will still be available as a new output full_id.
The default value of max_id_length is 0, so that the change is not breaking any existing usages.

why

Many resources have a max allowed length of names, such as aws_lb and aws_alb_target_group (32 characters), aws_iam_role (64 characters). Setting the max_id_length variable ensures that the max length is never exceeded, no matter the number of included attributes.

references

Closes #93

@osterman Sorry to disagree with you, but since this is a new feature, anyone who wants to use it will have to make changes. Therefore, I think we should retain id as full-length ID and instead add 2 new fields, something like

limited_id_length_limit
limited_id

agree with @Nuru , no need to change the original id output since it's in use in hundreds of modules by thousands of people.
Let's make the new vars as @Nuru suggested - people who need the limited ID will just use the new output

@osterman Sorry to disagree with you, but since this is a new feature, anyone who wants to use it will have to make changes. Therefore, I think we should retain id as full-length ID and instead add 2 new fields, something like

limited_id_length_limit
limited_id

@Nuru No, this PR has no breaking behavior or require any changes in existing usages. The id field will always represent the full ID unless max_id_length has been specified.

@osterman Sorry to disagree with you, but since this is a new feature, anyone who wants to use it will have to make changes. Therefore, I think we should retain id as full-length ID and instead add 2 new fields, something like

limited_id_length_limit
limited_id

@Nuru @aknysh No, this PR has no breaking behavior or require any changes in existing usages. The id field will always represent the full ID unless max_id_length has been specified.

Then no need to change the original ID at all, and no need to change its logic because many people are using it now.
Let's create another output with all the truncation logic you are proposing.

I understand why would you want to be able to modify the original ID - to keep the caller code the same (using just the id).
We will have two ID outputs in any case:

The original unmodified ID and a truncated ID

or

The original truncated ID and the new unmodified ID

@Nuru @osterman which way would be better?

I understand why would you want to be able to modify the original ID - to keep the caller code the same (using just the id).
We will have two ID outputs in any case:

The original unmodified ID and a truncated ID

or

The original truncated ID and the new unmodified ID

@Nuru @osterman which way would be better?

Yes exactly, in my mind it was more intuitive to not have to use a different output just because you have set a length limit. If you do set the max_id_length, you would probably in most cases never actually need the full ID, but it's there as a second output just in case.

Ya the benefit with @tibbing approach is that it works seamlessly provided we add the max len input. Also since it defaults to zero, it has no effect unless the user overrides it. I like supporting the explicit outputs as well, but that doesn't work unless a module implements support for choosing the id. I think setting the max len should be used sparingly by end users as needed and this gives users an escape hatch when needed, that our modules currently do not provide.

/terraform-fmt

/rebuild-readme

/test all


Allow -s for --state when listing containers

The same is already possible for pods, so we now add the alias to
containers as well to streamline the CLI behavior.

/lgtm


[Recorder] Recording is not generated for a particular test

Request-responses are not being saved for this test
https://github.com/Azure/azure-sdk-for-js/blob/79505a16bd6fef572cb1afb1de75a097bc86e016/sdk/web-pubsub/web-pubsub/test/hubs.spec.ts#L146
@bterlson reported

Enabled more logs from nock to understand.. "nock" is not saving the request-response pair for the "check connection test", somehow the request is special.
Could not figure out yet on how the request is different to see where it goes wrong in nock to be able to provide a repro for them.

Migrated to new recorder, no longer a problem


/dev/kvm not found on OSX

Describe the Bug
Summary: I've installed the haxm kext on OSX, and the kernel module appears to be loaded, but /dev/kvm still does not exist.
Host Environment

HAXM version: 7.4.5
Host OS version: macOS 10.14.5
Host OS architecture: x86_64
Host CPU model: Intel Core i7
Host RAM size: 16GB
(Optional) Host computer model: MacBookPro15,1

Guest Environment
Trying to run ls /dev/kvm - ultimately to run an Android Emulator through https://github.com/google/android-emulator-container-scripts
Expected Behavior
I would expect /dev/kvm to exist
Diagnostic Information
I'm checking that the kernel extension is loaded by running
% kextstat | grep intel
  192    0 0xffffff7f8429a000 0x28000    0x28000    com.intel.kext.intelhaxm (7.5.4) E622291F-7B94-3EA7-B644-97F1AD6DF807 <8 6 5 3 1>

HAXM log:
 % log show --predicate 'sender == "intelhaxm"' --style syslog --last 5m
Filtering the log data using "sender == "intelhaxm""
Skipping info and debug messages, pass --info and/or --debug to include.
Timestamp                       (process)[PID]
2019-12-17 14:35:16.364229+0100  localhost kernel[0]: (intelhaxm) haxm_warning:
2019-12-17 14:35:16.364232+0100  localhost kernel[0]: (intelhaxm) -------- HAXM v7.5.4 End --------
2019-12-17 14:35:40.530580+0100  localhost kernel[0]: (intelhaxm) possible map ffffffffffffffff cpu_online_map fff
2019-12-17 14:35:40.530775+0100  localhost kernel[0]: (intelhaxm) haxm_warning:
2019-12-17 14:35:40.530777+0100  localhost kernel[0]: (intelhaxm) -------- HAXM v7.5.4 Start --------

Additional context
None

Hi @arthurdarcet , HAXM is different with KVM. I noticed that you installed the HAXM successfully on your Mac Host but searched another hypervisor KVM. You can try to use HAXM  for acceleration or install KVM separately.


Feature/dist config enhancements

When I committed again on the branch for #106 it seems to have become detached from that PR. Anyway, here's a modification that only adds a note about best practice of not committing credentials, (and also the docblock housekeeping).

Gah! I accidentally PR'd to master instead of develop, but I see they're in sync anyway, so probably doesn't matter.

I can live with this. I think it is not a bad idea to mention the credentials thing. If build passes I'l merge it.
And don't worry, most of the pull requests are made to master ;-)

Cool. BTW, 5.x is a great update. Much nicer configs. Thanks for creating this module.

Thank you for contributing


Chamferdis module reported an error

Is there any exception in the provided chamferdis module version 1.0.0? The error is pointing to this module
The following is the error message
“Traceback (most recent call last):
File "test.py", line 327, in
test(args)
File "test.py", line 283, in test
metrics["chamfer_distance"] += compute_chamfer_distance(pred_pcd, gt_pcd, device)
File "/home/gdyanfa1/tmh/tmh_lidar_occ/4d-occ-forecasting-main/utils/evaluation.py", line 207, in compute_chamfer_distance
cd_forward, cd_backward, CD_info = chamfer_distance(
File "/home/gdyanfa1/miniconda3/envs/tmh_lidar_occ/lib/python3.8/site-packages/torch/_tensor.py", line 607, in iter
raise TypeError('iteration over a 0-d tensor')
TypeError: iteration over a 0-d tensor”

You need to install the modified chamferdist package shipped from this repo, under utils/chamferdist.
You can use command like: $ ~/4d-occ-forecasting/utils/chamferdist# pip install .

sure，It needs to be solved by linking other libraries in a ”pip insatll ." way


chore(ci) dont enable the download cache when building xenial for arm

:tada: This PR is included in version 2.0.8 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Record screen produces video that appears black in Quicktime

Here's the command I ran on version 1.6:
scrcpy -m 1280 -r Desktop/some-file.mp4 -t
Here are the logs for my recording attempt:
/usr/local/Cellar/scrcpy/1.6/share/scr...shed. 1.2 MB/s (19464 bytes in 0.015s)
2019-01-30 17:30:33.950 scrcpy[21276:1317781] INFO: Enable show_touches
2019-01-30 17:30:34.673 scrcpy[21276:1317781] INFO: Initial texture: 720x1280
2019-01-30 17:30:41.662 scrcpy[21276:1317781] INFO: Disable show_touches

Here's the output of scrcpy --version:
scrcpy 1.6

dependencies:
 - SDL 2.0.9
 - libavcodec 58.35.100
 - libavformat 58.20.100
 - libavutil 56.22.100

OS: MacOS Mojave 10.14 (18A391)
While the command was running (until I clicked the close button on the window), the screen was displayed correctly on my computer, but the output file, results in black footage when viewed from Quicktime.

Fixed on dev.


⚠ Bofrost.at has degraded performance

In e0d814a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1464 ms

Resolved: Bofrost.at performance has improved in d74a4b9 after 6 minutes.


CORS

I'm trying to make a call to the Yelp API, but keep getting the following error:
XMLHttpRequest cannot load https://api.yelp.com/v2/search?term=food&location=new york. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access. The response had HTTP status code 400.
Any suggestions on how to work around this?

You need something like this:
http://enable-cors.org/server_expressjs.html
http://stackoverflow.com/questions/18310394/no-access-control-allow-origin-node-apache-port-issue

I think you rather want to proxy that API call through express @tadwhitaker . It is Yelp not having the necessary headers to you can not do much about that. But Node can be a proxy handling the request.
So:
var request = require('request');
app.get('/yelp', function (req, res) {
  request('/api.help.com....', function (error, response) {
    res.send(response.body); // Check request API, do not remember this
  })
});

Can any-body advice me the way of handling server changes, with no rerun the server manualy,
and working with routes on it, thanks a lot !!


polymer 2.0 typings

Please update the typings for polymer and webcomponents first. It opens up the door for easy polymer 2.0 typescript experimenting.
npm i -D @types/polymer

PS iron-component-page is completely broken but the /demo code that only needs polymer 2 is working.
https://github.com/gertcuykens/hello-world
web-component-tester is also working except how do you do getContentChildren(); in polymer 2?
      test('distributed children', function() {
        var els = myEl.getContentChildren();
        assert.equal(els.length, 0, 'no distributed nodes');
      });

getContentChildren(slctr) would be something like:
var slot = this.shadowRoot.querySelector(slctr || 'slot');
var nodes =  slot ? slot.assignedNodes({flatten: true}) : [];
return nodes.filter(function(n) {
        return (n.nodeType === Node.ELEMENT_NODE);
});

Of course, if you know the slot in advance, you don't need the first half, and you could boil it down to:
this.$.slotID.assignedNodes({flatten: true}).filter(function(n) {
        return (n.nodeType === Node.ELEMENT_NODE);
});

@arthurevans do you mind looking at https://github.com/gertcuykens/hello-world and see how far you get :D I am pulling at as many legs as I can at google and microsoft to get this typescript polymer thing working. Just want to make sure all issues are currently covered and are on its way to be implemented before next typescript release or polymer release. I want to prevent loosing time on things we could have figured out before 2.0 preview.

@arthurevans coming back to your shadowRoot example I think it might be differently then you expect?

Hi @gertcuykens. Seeing as I have never used Typescript or vscode in my life, I don't think I'm the best person to try this out for you. Sorry.
I don't know what you mean about shadowRoot. The responses in your console are exactly what I would expect. What did you expect?
The code snippets I gave you above are basically the shadow DOM v1 equivalent of what getContentChildren does in Polymer 1.x. I ran them in the console against a Polymer 2 project and they appeared to work fine.

Ok thanks never mind, It was just me wrong then expecting the slot innerhtml to be hello world :)

@gertcuykens Nope. That's why you need the assignedNodes() call. The nodes don't move, they're just rendered there.

@justinfagnani did you publish@types/polymer?
Now that we're getting closer to a release of 2.0, we should see how much of the Closure type annotations are handled by typescript and fill in the gaps.

Now that there's a release candidate out, is there any progress on this?
Currently I use Closure + Polymer 1 - but build times are fairly long and editor support is weak. I'd love to be able to use TS + Polymer 2, but I haven't had any luck setting up an environment with proper typing & compilation, and the Polymer2.0-typescript branch is quite out of date now.

I'm working on the declaration exporter tool and decorators over the next week.

Awesome! Having a good official typing solution for Polymer 2.0 is very exciting.

any progress on this? thanks

Eagerly awaiting this...any progress?

I'd also be very happy about some status update on this topic.

I would like very much to see comprehensive TypeScript support. The mechanism for generating types discussed here is very interesting: Consume Closure types in the source code, and generate TypeScript from there. Over in the Angular project, they are going the opposite direction, with a tool (which is coming along quite well) tsickle. It consumes TypeScript, and emits Closure types.
As I understand, neither type system is strictly a superset of the other, so there's some rough edges with either direction. But it is interesting to see these two sister projects (perhaps just a few buildings apart on the same campus, or perhaps around the world even though it's the same company) solving essentially the same problem from either direction.

TypeScript support is currently work in progress at https://github.com/polymer/polymer-decorators

@TimvdLippe to clarify, that's just TypeScript (and possibly Babel, if they end up being compatible) decorators. The typings will be generated by https://github.com/Polymer/gen-typescript-declarations and probably included in the core repo.


Introduce qimalloc as an allocator option

Closes #46.
So far it's a really dumb allocator. It simply tries to allocate enough wasm pages everytime the alloc method is called (i.e. pages are not filled with subsequent alloc calls). It also doesn't dealloc. I tested it with runevm+hera and it passes some tests.

Some notes:

The allocation algorithm is a rough translation of @poemm's C malloc
It's been only implemented for arch wasm32
I tried it with a few simple test cases, but not fully sure about correctness

From a rust developer PoV this code is probably an abomination :smile:

The C version of dumb malloc() is untested for edge cases and assumes things about LLVM compiler output.
The good news: dumb malloc() compiles to wasm in 15 bytes (or 60 bytes if the preprocessor flag GROWABLE_MEMORY is set to true). This mostly solves the problem of memory allocation in Ewasm -- no host system library is needed for malloc() since its size is nearly negligible.

Changed this to use the new crate: https://github.com/wasmx/qimalloc

Looks good to me, can't approve my own PR though :)

Release qimalloc so we can refer to a version and not just a random repo in this crate.


Science Pack Inventory Crafting Location

Mod source
Factorio Mod Portal
Which mod are you having an issue with?

[ ] pyalienlife
[ ] pyalternativeenergy
[X] pycoalprocessing
[ ] pyfusionenergy
[ ] pyhightech
[ ] pyindustry
[ ] pypetroleumhandling
[ ] pypostprocessing
[ ] pyrawores

Operating system

=Windows 10

What kind of issue is this?

[ ] Compatibility
[ ] Locale (names, descriptions, unknown keys)
[ ] Graphical
[ ] Crash
[ ] Progression
[ ] Balance
[ ] Pypostprocessing failure
[X] Other

What is the problem?
If I want to handcraft an Automation Science Pack or Logistic Science Pack, it is listed in the "Coal Processing" tab of my inventory.
If I want to set a building to craft an Automation Science Pack or Logistic Science Pack, it is listed in the "Coal Processing" tab of the filter.
However, If I want to place a shortcut on my bar for an Automation Science Pack, it is listed in the "Intermediate Products" tab of the filter.

Py Science Pack 1, Military Science Pack, and Py Science Pack 2 are always on the "Intermediate Products" tab.
Steps to reproduce
No response
Additional context
I am using the full Py suite, the latest release version.
Log file
No response

Fixed. Thanks for the report.


Dear kukdh1

Dear kukdh1,
My English is not good, sorry......
You write a program, "AokanaCGExtractor"
I download use "Microsoft Visual Studio Ultimate 2013" open, there will be many errors.
These errors may be set in my relationship with the environment.
"AokanaCGExtractor.exe files" you can provide it?
THX!

I added executable file in /Release directory.
Please check.

Dear kukdh1,
Thanks for your palindrome.
My English is not good, sorry......
You provide "exe file", "start button" after pressing,
Addition to the button name becomes "stop", no other reaction.
My OS is win7, the Japanese language.
'Aono Kanatano Four Rhythm(蒼の彼方のフォーリズム)' has to use to crack the program.
Will these factors will be affected?
This is a video my executed。
http://youtu.be/X49jAEND5Vk
Thank you!


Make POST action use body as default instead of query string

I have run into a problem recently creating large create_inbound_shipment_plan requests. When adding more than around 30 skus, I get a 400 Excon::Errors::BadRequest back from Amazon with no error message. Since I am not getting a 414 Excon::Errors::RequestURITooLong back, it isn't hitting the rescue case and retrying. As far as I can tell, this is only happening to me when the query string gets too long.
I decided that instead to be safer, I would make the POST with body action default when possible, instead of performing a retry after attempting to use the query string. I would be open to any improvements or suggestions you would have on my solution. Thanks!

:+1: It seems this is the most pragmatic thing to do after all.

Awesome, I appreciate the help. I look forward to the updated version in peddler!


fix(joinNetwork): make params required - properties and note

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 80.86%. Comparing base (d71e949) to head (5b78246).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #78   +/-   ##
=======================================
  Coverage   80.86%   80.86%
=======================================
  Files          19       19
  Lines         465      465
  Branches       94       87    -7
=======================================
  Hits          376      376
  Misses         89       89

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