No option to add secondary IPs

I have a VM with 49 (yes!) secondary IP configurations/addresses that is being replicated with ASR.
Step 3 in the article shows "0 out of 3..." and a couple of buttons. However, for my VM, I do not see either of those things. It just says "No Secondary IP is configured".
Why is it not picking up the secondary IP addresses on this VM?

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

ID: 917708b7-cd1b-b914-ebf1-91cff016f49e
Version Independent ID: 30bbdc40-eecf-5fb3-9943-0f7a7e1d44b3
Content: Configure failover of multiple IP addresses with Azure Site Recovery - Azure Site Recovery
Content Source: articles/site-recovery/concepts-multiple-ip-address-failover.md
Service: site-recovery
GitHub Login: @rishjai-msft
Microsoft Alias: rishjai

@ChrisSommers Thank you for your post. Could you please share the screenshot of the UI where it shows "No Secondary IP is configured"?

Here you go:
@.***
This shows that the VM “vmlivesapp01” has multiple secondary IP addresses:
@.***
Thanks
Chris
From: SadiqhAhmed-MSFT @.>
Sent: 15 December 2021 14:04
To: MicrosoftDocs/azure-docs @.>
Cc: ChrisSommers @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] No option to add secondary IPs (Issue #85313)
@ChrisSommershttps://github.com/ChrisSommers Thank you for your post. Could you please share the screenshot of the UI where it shows "No Secondary IP is configured"?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/85313#issuecomment-994821108, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AISBLG6HSICNT27AELGNU7DURCN4JANCNFSM5KDTCHBA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@ChrisSommers Am afraid to say, we need to debug this issue to further understand the root cause and help you with solution. That said, I highly recommend you reach out to Azure technical support team by raising a support request. The ticket enables you to work closely with the support engineers and get a quick resolution to your issue.
Here is the link - https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request to create support case.

@ChrisSommers Could you let me know the following?

When was the VM protected with Site Recovery?
Did you add the IP Configs AFTER protecting with Site Recovery, or BEFORE?

Rishabh
That was a good shout – they were added after the VM was protected.
I have now disabled replication and re-enabled it. However, the VM has been stuck like this for several hours now:
@.***
So it looks like something has stalled in the background.
Many thanks
Chris
From: Rishabh Jain<EMAIL_ADDRESS>Sent: 16 December 2021 06:33
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: ChrisSommers<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] No option to add secondary IPs (Issue #85313)
@ChrisSommershttps://github.com/ChrisSommers Could you let me know the following?

When was the VM protected with Site Recovery?
Did you add the IP Configs AFTER protecting with Site Recovery, or BEFORE?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/85313#issuecomment-995480758, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AISBLGZCPHWQGUFLDW3AI5DURGBZFANCNFSM5KDTCHBA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


"Select" MixedRealityInputAction does not raise the "OnGestureStarted"

Describe the bug
When implementing the IMixedRealityGestureHandler interface, four (4) functions:

OnGestureStarted
OnGestureUpdated
OnGestureCompleted
OnGestureCanceled

I'm trying to catch the exact moment the "Select" action is started. All other input actions (hold, manipulation and navigation) are triggered, only "select" action doesn't raise the "OnGestureStarted".
To reproduce
Steps to reproduce the behavior:

Write a C# script that implements the IMixedRealityGestureHandler interface
Attach the script to a GameObject
Run the scene
Debug on the "OnGestureStarted" function

Expected behavior
When I start the "Select" action, "OnGestureStarted" should be called.
Your Setup (please complete the following information)

Unity Version [e.g. 2018.4.12f1]
MRTK Version [e.g. v2.1.0]

When I start the "Select" action, "OnGestureStarted" should be called.

I think at the moment, it only fires OnGestureCompleted. Would you expect a started event and immediate completed event, since a tap doesn't really have a time length component to it?


App needs to be updated to continue syncing with Health Connect

Hi,
I have run the project in the emulator with the following specs:
Android 14 ("UpsideDownCake") | x86_64
It run successfully but it hit the following pop up to mentioned that the app needs to be updated to continue syncing with Health Connect.

Please advise if there is any solution for this.
Thanks.

Hi, any update on this issue? Please let me know if there is any further information needed from my side.

@jackvintedge
Hello.
First of all, the Health Connect has been updated in Android 14.
From Android 14, it is included in Android system, and not a separate app anymore.
Currently, HealthStack is compatible with Android 13 and are trying to provide compatibility with Android 14 as well.
You can refer to the guide below, and we'll appreciate if you contribute :)

https://support.google.com/android/answer/14119325?hl=en
https://developer.android.com/health-and-fitness/guides/health-connect/develop/get-started?hl=en

🚫 Issue closed. Thank you for the contribution.


SMP now stable in x86_64

Statman was too small with only 2 pages, and the all the cores couldn't share the same stack

This did not trigger due to Couldn't obtain mergeable status. I will try and trigger this test again.
Jenkins test please


Settle message spontaneously on receive mode first

spec : http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#type-receiver-settle-mode
in mode first, the receiver must spontaneously settle all incoming transfers.
This was not implemented before because the receiver was not waiting for dispositions, and so the bug wasn't visible.

this fixed the servicebus test as expected :


Update hdinsight-faq.md

Improved the edge node FAQ

@ashishthaps1 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@hrasheed-msft: I'm sorry - only the author of this article, @Ramakoni1, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


example about doing OCR use CNN+RNN

I see some papers about doing OCR without segmentation using CNN and LSTM.
Does mxnet support such work?

I don't think we have an example for this. But you can definitely do it with mxnet. The speech and RNN examples are good references

Thanks!

@xlvector
Have you succeeded in achieving CNN + LSTM + CTC code?
or just achieve example warpctc?
recently I am studying cnn + lstm + ctc joint-training, but I have met some problem, did you make it successfully?

You can see examples under /examples/warpctc/

        This example does not use cnn to extract features as lstm's input，so when the captcha have rotate or some change it wont recognize success，do u plan to add cnn to this example？
        在2016年07月20日 15:17，Xiang Liang 写道:You can see examples under /examples/warpctc/

—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.

@sinmaystar @xlvector Do you gays make some progress with cnn+rnn+ctc?

example/warpctc  @sosong   You need to use an old version of warpctc from https://github.com/baidu-research/warp-ctc with version 5bfb46e83bcb338a09fbf875cb0b02bc39746b36

@xlvector Does warp-ctc plugin support bucketing? I implemented cnn-bi_lstm-ctc with buckets in order to fit variable input image length, but I find it all the outputs of final layer remain same during training, however it will converge if I resized all images to fixed length and only use one bucket.
So I guess warp-ctc may not be compatible with bucketing.


Got Error when refresh the page

/usr/lib/node_modules/redis-commander/lib/routes/home.js:40
reducedConfig.default_connections.forEach(function(item) {
^
TypeError: Cannot read property 'forEach' of undefined
at /usr/lib/node_modules/redis-commander/lib/routes/home.js:40:41
at /usr/lib/node_modules/redis-commander/lib/util.js:140:5
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:525:3)

have the same issue

have the same issue

redis-commander --redis-host=<IP_ADDRESS>
set the hostname it will work fine

FWIW I'm hitting the same problem, even after specifying the --redist-host flag.
It looks like @sseide is working on this however? Is there a way I can ensure that reducedConfig.default_connections is initialized by setting a different combination of flags? i.e. would using a configuration file workaround this issue?

latest version (github + docker) after merge yesterday will not crash anymore with this error.
For the web client it does not matter if there is a connection_defaults object contained or not as the web client only checks for the UI related properties like "sidebarWidth" and so on. If there are some more problems related to this just ping me - i will fix it as soon as possible.
Currently i do an more complete rewrite of the configuration stuff to make it easier to add new config params with semi-automatic env var support for docker.

Problem remain the same still it crashes and i see the same error
On Wed, 12 Dec 2018 at 2:51 PM, sseide<EMAIL_ADDRESS>wrote:

latest version (github + docker) after merge yesterday will not crash
anymore with this error.
For the web client it does not matter if there is a connection_defaults
object contained or not as the web client only checks for the UI related
properties like "sidebarWidth" and so on. If there are some more problems
related to this just ping me - i will fix it as soon as possible.
Currently i do an more complete rewrite of the configuration stuff to make
it easier to add new config params with semi-automatic env var support for
docker.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/joeferner/redis-commander/issues/322#issuecomment-446527320,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AiOfYsoBKkCLmaZwAbrSSAOA0ESewNF8ks5u4NGKgaJpZM4ZM1Nf
.

--
Regards,
[image: VentureDive]
Faisal Ali
Software Engineer
PK: +923433016854

@faisalmaqsood786 how do you run redis-commander? gitlab checkout? docker? npm?
If docker - do you have deleted the old image to really fetch the new one?

I use with  npm even i uninstall  and install it again but same issue
On Wed, Dec 12, 2018 at 3:03 PM sseide<EMAIL_ADDRESS>wrote:

@faisalmaqsood786 https://github.com/faisalmaqsood786 how do you run
redis-commander? gitlab checkout? docker? npm?
If docker - do you have deleted the old image to really fetch the new one?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/joeferner/redis-commander/issues/322#issuecomment-446531240,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AiOfYrXG059JeruP73YyITUpiMg4mn1mks5u4NSAgaJpZM4ZM1Nf
.

--
Regards,
[image: VentureDive]
Faisal Ali
Software Engineer
PK: +923433016854

npm version has no update right now. NPM version is only seldom updated by Joe Ferner. Fix only contained inside dockerhub images and gitlab. Docker images are automatically rebuild on commit.

Alright ,
Thanks for the update.
On Wed, Dec 12, 2018 at 1:40 PM sseide<EMAIL_ADDRESS>wrote:

npm version has no update right now. NPM version is only seldom updated by
Joe Ferner. Fix only contained inside dockerhub images and gitlab. Docker
images are automatically rebuild on commit.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/joeferner/redis-commander/issues/322#issuecomment-446542162,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AiOfYiH2ogTRQhqeLPLt6WZjCslUeu80ks5u4N00gaJpZM4ZM1Nf
.

--
Regards,
[image: VentureDive]
Faisal Ali
Software Engineer
PK: +923433016854

@chrsmith @zheeeng Someone of you not using npm as installation source? Does the problem remains somehow or is it fixed for you? Feedback welcome.

@sschueller I'm using the docker image. Any command execution leads to site crash.

@zheeeng do you updated the docker image? Than please post the exact stacktrace of the crash.
Thanks

I tried the latest image and problem solved. Thx!

@sseide I'm using the npm installation, and the problem still exists:
>>> npm list -g |grep redis-commander
├─┬<EMAIL_ADDRESS>

@joeferner  - Hi, I have installed redis-commander v0.6.7. I am getting below error when launching redis-commander. Please suggest.
$ redis-commander
Using scan instead of keys
No Save: false
C:\Users\Shilpi Gupta\AppData\Roaming\npm\node_modules\redis-commander\lib\app.js:86
return require.resolve(module).match(/.*/node_modules/[^/]+//)[0];
^
TypeError: Cannot read property '0' of null
at modulesPath (C:\Users\Shilpi Gupta\AppData\Roaming\npm\node_modules\redis-commander\lib\app.js:86:68)
at module.exports (C:\Users\Shilpi Gupta\AppData\Roaming\npm\node_modules\redis-commander\lib\app.js:132:59)
at startWebApp (C:\Users\Shilpi Gupta\AppData\Roaming\npm\node_modules\redis-commander\bin\redis-commander.js:567:21)
at C:\Users\Shilpi Gupta\AppData\Roaming\npm\node_modules\redis-commander\bin\redis-commander.js:489:12
at startDefaultConnections (C:\Users\Shilpi Gupta\AppData\Roaming\npm\node_modules\redis-commander\bin\redis-commander.js:515:10)
at startAllConnections (C:\Users\Shilpi Gupta\AppData\Roaming\npm\node_modules\redis-commander\bin\redis-commander.js:483:3)
at Object. (C:\Users\Shilpi Gupta\AppData\Roaming\npm\node_modules\redis-commander\bin\redis-commander.js:293:5)
at Module._compile (internal/modules/cjs/loader.js:956:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:973:10)
at Module.load (internal/modules/cjs/loader.js:812:32)

suggestion: do NOT hijack other issues clearly not related to your problems
suggestion: read open issues if there are problems similiar to yours
suggestion: when other issue found (hint: carefully read #388) apply solutions from there.


Support for multiple webpack configurations

What problem does this feature solve?
For my application, I need support for color schemes. I have solved this by using scss file with variables that gets imported wherever there's a need for color. E.g. variables.ThemeA.scss and variables.ThemeB.scss are color schemes supported.  Then it's just a matter of linking to one or another at runtime.
Before vue-cli, this was resolved using webpack support for multiple configurations (https://webpack.js.org/configuration/configuration-types/#exporting-multiple-configurations). After vue-cli this can't be solved as vue.config.js works only with a single configuration.
Current workaround is doing this in package.json:
"buildThemes": "set VUE_THEME=ThemeA && vue-cli-service build && set VUE_THEME=ThemeB && vue-cli-service build --no-clean",
And then using that environment variable in vue.config.js configureWebpack() method.
What does the proposed API look like?
Support for returning an array in configureWebpack method in vue.config.js
configureWebpack: config => {
       // code that alters config1 and config2 based on config argument...
       return [config1, config2]
}

It should be possible to implement this in a functional way as a plugin in userland.
I'm not sure that we should add this to the Core build process since I'm afraid it would take a pretty big refactoring to get it into the build process en par with the other options, in my eyes.

I had the same need in a  real world project. What I did is tweak the webpack configuration into multiple configs after it is resolved by vue cli. It's simple but a bit hacky.
I have extracted my usage into a plugin in case anyone needs: vue-cli-plugin-multi-compiler.
More details can be found in that repo.

I have exactly the same need, trying to transpile my test files, each of them requires individual webpack entry (to be standalone). Previously I've solved that by using multiple Webpack configs, but now I'm puzzled. Going to try the @jkzing plugin.

@jkzing 's plugin works great. However, as mentioned here https://github.com/jkzing/vue-cli-plugin-multi-compiler/issues/1, the serve command of vue-cli assumes webpack config is an object.
If that is the only place where such assumption is made (the plugin works fine in production build), then its not such a big change to sources. @LinusBorg Please consider adding this feature, or, can you give recommendations how to implement it in userland for development builds?

Just adding my two cents here to say that I'm trying to use webpack to bundle my server-side code into server.js and have it serve up my client. It would be nice to have webpack do this, but that is made considerably more difficult by the fact that a lot of the webpack code is abstracted away into vue-cli-service.

still no luck about @vue/cli's serve supporting multiple configuration?

I've been trying using multiple config using serve, hacking around serve to make the default returns an array. "single config can be an array of length 1" i thought.
but there are several implications in vue-loader checking for config, looking for appropriate loader. as i don't know the strategy behind this and can't find documents justifying for such... i guess we have not choice but to say "it's impossible to do so ; it's a limitation of @vue/cli"


Issue with serialization of type names

Note: for support questions, please ask on StackOverflow: https://stackoverflow.com/questions/tagged/Akavache . This repository's issues are reserved for feature requests and bug reports.
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Depending on the structure of your classes, you may end up serializing types to Sqlite as base classes rather than the actual runtime type.  This caused a problem for me in particular when using the GetAllObjects method, which wasn't returning anything.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
Run this to see the different between using typeof (compile time) vs GetType (runtime):
http://csharppad.com/gist/b19be0194baf19f2202f88ad6f46580e
What is the expected behavior?
I would expect my objects to be serialized as their actual type rather than boxed type.
What is the motivation / use case for changing the behavior?
I think this would make for more consistent serialization / de-serialization of objects.
Which versions of Akavache, and which platform / OS are affected by this issue? Did this work in previous versions of Akavache? Please also test with the latest stable and snapshot (https://www.myget.org/feed/Akavache/package/nuget/Akavache) versions.
I believe that prior versions of Akavache will have been affected.  Only tested on Windows / UWP.
Other information (e.g. stacktraces, related issues, suggestions how to fix)
Replace use of typeof with GetType.  I would submit a pull request but I don't have all the prerequisites installed to run Akavache anymore.  I was helping a former colleague diagnose an issue and thought it might be worth raising as an issue.  I also understand you may have other reasons for doing this and didn't want to presume that what I think is a solution is actually a solution :).
Workaround
A workaround is to cast an object (if the reference comes from a base class) to the actual type before calling AddObject but this isn't entirely intuitive.

Hi @natwallbank, If I understand your problem correctly, I just faced similar issue. I changed the namespace of my object and it is not deserializing/serializing anymore. Is that what you mean simply?

Hi @EmilAlipiev, not exactly, no. I'd probably expect that if the full name of the serialised type changed then existing serialised data may no longer be compatible.
The issue I had is that my reference to an object was declared as its interface for reuse/generic reasons, so calling AddObject serialised it using that type. I think it would be better if AddObject serialised as the actual runtime type, as when I wanted to de-stress serialise all objects of a specific derived type, it didn't work. It is possible to cast the object to is derived type first but it's a pain to have to remember to do that.


NPE on benchmar

Could be ARM/JDK11 specific, Debian 64-bit with OpenJDK 11.05.
mvn clean install of the rdf-testsuite yields
Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (enforce-bytecode-version) on project rdf4j-benchmark: Execution enforce-bytecode-version of goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce failed.: NullPointerException
See also #1148

Fixed by cleaning .m2 local cache


Unable to reset model instance attribute

Before we start: I have made a very small git repo with seed data and two REST endpoints to test this issue here: https://github.com/juanpasolano/sails-nested-test
So I have 3 models: Appointment which has many procedure which has one to one procedureItem.
Since there is not nested population in sails I am getting procedures with procedureItem by hand using something like:
Appointment.find(1).exec(function(err, appointments){
			if(err) return res.negotiate(err);
			async.eachSeries(appointments, function(appointment, cb){
				Procedure.find({appointment: appointment.id}).populate('procedureItem').exec(function(errP, procedures){
					if(errP) return cb(errP);
					appointment.procedures = procedures;
					appointment.proceduress = procedures;
					cb()
				})
			}, function(errE){
				if(errE) return cb(errE);
				res.ok(appointments)

So the issue is when I want to replace the proceduresattribute with the new array procedures (which has the nested depth i need), but if you hit the endpoint, there is no procedure attribute available.
As a test I have attached the same new procedures array to proceduress (double s) attribute and this one gets properly set.
I have tried using the .toObject() method with no luck.
Have tried sails 0.10.5 and 0.11.0 with no luck.

Hi @juanpasolano - did you find a resolution or answer for this problem?

Not a proper solution, more like a workaround.
I had to get the appointments and do a foreach and clone each item using _.clone() and push them to a new array. And then everything worked.
Are you having the same issue?
Have a look at this stackoverflow question i made. Upvote it to get more people to see it.

@juanpasolano it's not a bug, but it's also not the easiest thing to wrap your head around.  I posted on your SO question, hope that helps!

Thanks for the answer
I did try toObject() and it didn't work. I have and endpoint doing that in the demo.


Intermittent 503 Service Unavailable when using host based ingress with Rancher ingress controller

Rancher versions:
rancher/server:v1.6.7
rancher/agent:v0.6.6
Infrastructure Stack versions:
healthcheck:v0.3.1
ipsec:rancher/net:v0.11.7
network-services:rancher/network-manager:v0.7.7, rancher/metadata:v0.9.3
scheduler:rancher/k8s:v1.7.7-rancher1
kubernetes (if applicable):rancher/k8s:v1.7.7-rancher1
Docker version: (docker version,docker info preferred)
1.12.6
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
CentOS Linux 7 (Core), 3.10.0-693.2.2.el7.x86_64
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
VMware
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
HA Rancher with external mysql DB
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Kubernetes
Steps to Reproduce:

Deploy any service inside kubernetes cluster
Create an ingress using host path and use annotation: io.rancher.scheduler.global: "true" . This also creates an rancher ingress lb in the Rancher UI.
Browse the host path in any browser, and intermittently instead of loading the kubernetes service, we get 503 Service Unavailable - No server is available to handle this request.
If you refresh the browser multiple times (between 3 to 12 times), the service will load.
This happens will all the ingress that I create in the cluster
Results:
Expected result is to not have 503 Service unavailable error and load the service everytime you browse for that hostname.

I have recently updated rancher server to v1.6.10, but I am still getting this error.

They spawn new haproxy instance for every new ingress resource. It is totally killing all the idea of ingress. It have to be one  haproxy instance with virtualhosts inside. Every new ingress resource added should just update this haproxy instance without adding new one.
Rancher v1.6.14 still spawns new haproxy instance on every ingress resource added. It leads to port conflicts and 503 all the way.

Thanks for your report!
With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.
If you think we should keep this issue open, please let me know.


[DO-NOT-MERGE] trigger CI

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

To solve the stability of sql-others, hive-others and tpcds?

I'm only targeting to sql-others as I see almost consistent failure in sql-others, though I had to touch some code here to trigger test run. Are you investigating the same?

Seems like TPC-DS consistently fails too most likely because of out-of-memory. I worked around this by splitting the queries to run but .. it'd be great if we can find a way to fix this up. I'll likely take a look too around early next week.

Made a PR for TPC-DS https://github.com/apache/spark/pull/37270

sbt.ForkMain 34895 failed with exit code 137
2022-07-24T06:25:51.5368193Z [warn] In the last 5506 seconds, 21.985 (0.4%) were spent in GC. [Heap: 2.99GB free of 3.62GB, max 3.62GB] Consider increasing the JVM heap using `-Xmx` or try a different collector, e.g. `-XX:+UseG1GC`, for better performance.

Sorry for the late reply,  I found that before GA task was killed, there would be logs like the one above, can we try to increase -Xmx?
In addition, can we get the content of dmesg?

cc @Yikun too FYI

https://github.com/apache/spark/blob/72b55ccf8327c00e173ab6130fdb428ad0d5aacc/project/SparkBuild.scala#L1194-L1199
I change the 2 -Xmx4g in SparkBuild.scala to -Xmx3200m and add -XX:+UseG1GC options, but still found logs as follows:
sbt.ForkMain 42403 failed with exit code 137
2022-07-26T05:27:04.8785522Z [warn] In the last 3341 seconds, 19.769 (0.6%) were spent in GC. [Heap: 3.28GB free of 3.99GB, max 3.99GB] Consider increasing the JVM heap using `-Xmx` or try a different collector, e.g. `-XX:+UseG1GC`, for better performance.
2022-07-26T05:27:06.9932313Z [error] (hive / Test / test) sbt.TestsFailedException: Tests unsuccessful
2022-07-26T05:27:07.0186283Z [error] Total time: 3343 s (55:43), completed Jul 26, 2022 5:27:07 AM
2022-07-26T05:27:07.7573628Z [error] running /home/runner/work/spark/spark/build/sbt -Phadoop-3 -Phive -Dtest.include.tags=org.apache.spark.tags.SlowHiveTest hive/test ; received return code 1

The max heap size still 4GB,  it doesn't seem understandable,

Sorry for late reply, I'm busy in some local meeting recent days.

In addition, can we get the content of dmesg?

@LuciferYang  We can add a separate step like:
- name: Print debug info
  if: failure()
  run: |
    # print demsg info

Sorry for late reply, I'm busy in some local meeting recent days.

In addition, can we get the content of dmesg?

@LuciferYang We can add a separate step like:
- name: Print debug info
  if: failure()
  run: |
    # print demsg info

Thanks for your reply, I have tested,  the account executing GA should not have permission to execute demsg and  GA test should already stability now :)

Let me close this one. I believe all are fixed now.


generate a usage table from schema alone

detects relevant columns

Implemented with generate_and_populate_template in project.Makefile's local/usage_template.tsv target


improving connecting and reconnecting

closes #452 and #497

Could you add a test for NiListItem? The poor component feels so lonely down there with its 50% ;D


[WIP] Implement functional testing on Windows (part of #67)

Why close?

`

Just got some thought and wanted to test it.
BTW, can you add the AppVeyor webhook, please? It's Windows CI, free for opensource repos.
URL:
https://ci.appveyor.com/api/github/webhook?id=xdacywoetdk7s7bt
Content Type:
application/x-www-form-urlencoded
Which events would you like to trigger this webhook?

[x] Pull Request
[x] Push

Please, ping once I'll be in the office. Also, AFAIR @churkin also has permissions to do this

done

Wow, thanks guys, it's awesome! :+1:


[v2.0] RNN: use rnn_params

Description
Use only one parameter for rnn_layer in stead of multiple parameters to improve performance.
Checklist
Essentials

[x] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage
[x] Code is well-documented

Changes

[x] Fused rnn parameter to only one parameter
[x] Add rnn parameter split function in gluon.utils to help users split rnn_param into weight and bias in different layers.

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@mxnet-bot run ci [centos-gpu, unix-gpu]


Support additional transitive resolver strategies

Following on from tweet thread https://twitter.com/BlythMeister/status/1177225164859346945
Whereby some package maintainers (including Microsoft) don't put max version constraints on packages.
Proposed solution is to add 3 new "max" strategies

max-major - same as max now, max will be depricated
max-minor - take the max, but don't go up a major version.
max-patch - take the max, but don't go up a minor version

This means you could use max-minor and take new versions as they are released, but not expose yourself to a breaking transitive dependency.
Therefore helping to resolve issues like this: https://github.com/aspnet/Extensions/issues/2405
This issue it for the discussion of this idea (rather than using Twitter)

In cases where a maximum version has been specified as part of the dependency, this will be observed, even if it's bigger that the chosen "max" strategy.
This logic for limited max will only apply when the package publisher has not specified what the maximum is.
Based on the strategy chosen, it will automatically add the maximum version based on the strategy.
Whereby max/max-major will add nothing.
max-minor will add a < X+1 where X is the current major version.
max-patch will add <X.Y+1 whereby X is the current major version and Y is the current minor version.

One thing to consider are prereleases: Technically 2.0.0-alpha < 2.0.0 therefore you still get 2.0.0-alpha based on a package depending on ">= 1.0.0" when prereleases are allowed for that particular package

I think I've drastically over simplified this in my head....abort...abort...abort. 🤣

Don’t give up I’m happy to help / answer questions (at least for the parts I understand myself).
Also there is low risk to break too much because there is a good test coverage.
Basically:

We decide what we want
Add some unit tests
make sure we get the stuff green again with trial and error :D

I actually think half my issue is...I don't know what I want 🤣
The max approach has been perfect for me for years.
Now, I have an example where is doesn't work....which is part triggered by 1 package having a max version and another not (both from Microsoft)
So, if I don't use max version...I will end up downgrading things that have been working.
But if I use max version, this 1 thing doesn't work.

We have long been talking about using a private curated nuget feed...maybe that is another solution for me....and then have my bot auto update things I trust (like fake) but then manual process to update things like aspnetcore


Add clear message when topic creation fails

[ ] Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
I changed to display the error message returned from the backend.
Is there anything you'd like reviewers to focus on?
It's my first pull request on this project so I'm happy If you give me a feedback.
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[ ] No need to
[x] Manually - tried to create a topic twice
[ ] Unit checks
[ ] Integration checks
[ ] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[ ] My changes generate no new warnings (e.g. Sonar is happy)
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged

Check out Contributing and Code of Conduct
A picture of a cute animal (not mandatory but encouraged)
Topic creation when fails display 'Schema '

Now is displaying the error returned from the backend:

@Corlobin hey, thanks for your contribution!


Simpler func for SimpleObjectPool

Summarise the changes this Pull Request makes.
Simpler func for SimpleObjectPool
For the SimpleObjectPool constructor:

The constructor func can be Func<T>, we don't use the other param at all
the constructor func is IMHO a more important param than an initial size, so should come first
initial size has a default of zero

Please include a reference to a GitHub issue if appropriate.

todo in a later PR:  SimpleObjectPool<T> is only ever used as a SimpleObjectPool<Socket> - is the generic necessary?
ConnectedSocketPool is a wrapper of SimpleObjectPool<Socket>, which means that each operation is forwarded, incurring a tiny extra delay. Fold these classes together?

And yes you're right, the generic is also redundant now too.

I plan to make a later PR to fold SimpleObjectPool into ConnectedSocketPool as this is the only place where it is used. It will be simpler, and might remove some small run-time overhead - the indirection might or might not be optimised out.
As far as I know, there is no suitable generic pool class in the framework, as we are already doing something very close to this example


feat: Verification using email (FE)

[x] Develop verification dashboard screen
[x] Develop routes for verification using connections, verification using email and verification using bulk
[x] Develop schema list screen
[x] Develop cred def list
[ ] Develop attributes list screen
[ ] Develop support multiple email Id's screen to create proof request screen
[ ] Develop stepper on all pages, to check the progress of the verification process
[ ] Develop payload for Indy and Jsonld type flow
[ ] Test complete flow for Indy and Jsonld flow

This task is on hold because of other priority tasks

This task is completed.


Embed component references in runtime response?

Describe the feature
Ever since the isograph talk at GraphQL Conf, I've been trying to figure out if we would want to do something similar for Houdini's responses. So here's the general idea:
+page.gql
query UserInfo {
  viewer {
    ...UserAvatar @component
  }
}

+page.tsx
export default ({ UserInfo }: PageProps) {
  return (

      <UserInfo.viewer.UserAvatar size={10} />

  )
}

UserAvatar.tsx
type Props = {
  user: graphql<`{
      ... on User {
        firstName
      }
  }`>
}

export default ({ user }: Props) {
  return (

      {user.firstName}

  )
}

This leans even harder into Houdini tightly integrating into your bundler and that feels really good. Also every file has a distinct purpose without any kind of boilerplate to wire everything up and that feels even better.
pros:

no component import
no type import for the component prop
never have to deal with your prop being different than what you get back from useFragment
never have to import the type to define your prop (the graphql function would have properly overloaded signatures)
it's driven by graphql and still spec compliant (we'd generate the actual UserAvatar fragment so ide's could pick it up)

neutral:

fragment names don't have to be unique but component names do (or uniquely tagged)
We could even support named exports with an argument

the big hurdle for the fragment API is how to identify that a given fragment corresponds to a given prop (so the runtime can thread the reference through). Without typescript to give us a way to express it, the only thing I could think of is to rely on comments but that always feels so hacky to me. But, just for completeness, it could look something like:
const userInfo = graphql(`{
  ... on User {
        firstName
      }
}`)

export default ({ /* houdini: userInfo */ user  }) {
  return (

      {user.firstName}

  )
}

Criticality
None

A variation of this is to let fragments exist as a field on a type. something like:
UserAvatar.tsx
type Props = {
  user: graphql<`{
      ... on User @componentField(field: "Avatar") {  # infer "User" from inline fragment
        firstName
      }
  }`>
}

export default ({ user }: Props) {
  return (

      {user.firstName}

  )
}

+page.gql
query UserInfo {
  viewer {
    Avatar  # <- does not actually exist in the schema but we would generate type extensions
  }
}

+page.tsx
export default ({ UserInfo }: PageProps) {
  return (

      <UserInfo.viewer.Avatar size={10} />

  )
}

This forces the unique-ness into a slightly easier shape to swallow but at the cost of potentially conflicting with the schema (although that's easy to work around with casing)
Also, @componentField might be the answer for the vanilla javascript approach:
graphql(`{
      ... on User @componentField(type: "User", field: "Avatar", prop: "user") {
        firstName
      }
}`)

export default ({ user  }) {
  return (

      {user.firstName}

  )
}

I've start the work in #1176 and have a working demo for the simplest case 🚀

This looks so good. 🎉 🎉 🎉 🎉  I love it. Really clever to use ... on User instead of a (needlessly named) fragment on User. I don't foresee any issues with the design at the moment.
Type inference

I think that since you're explicitly defining props, you will correctly get TypeScript inference for e.g. the size prop. Correct?
Does the Prop type that the user sees exclude the user prop?

Compilation Errors

What if there are multiple @componentField annotations in the same props? Does Houdini fail gracefully in that case?
What if you have a legitimate need to pass a second fragment down (e.g. a fragment on viewer for the logged in user's name, and also a specific Foo). If only one of those is a @componentField, will this continue to work?
Are field-level merge conflicts reported in a sane way? (I think so... __componentField__User_Avatar is self-documenting)

Interactions with other directives

How would @arguments be passed to Avatar?
How do you add @defer etc to Avatar's fragment definition?
Is there any directive for which it maybe makes sense to apply it to Avatar, but also the fragment? e.g. @include... is there the possibility that you want to include the Avatar but not fetch the fragment; and is that case fully covered by ... on User @include { in Avatar. (It probably is!)
Are there any directives that are on fragment definitions, but not on inline fragments, that you want to support, other than @arguments? At Meta, there are "@fb_owner" (or something) directives that fall on fragment definitions, for example.

Neighboring Avatars:

I am not confident in Relay's behavior here, but it should refuse to compile something like

... on User {
  foo # a string
}
... on NotUser {
  foo # an int
}

If the foo's types don't align, at least if the inline fragments are being combined into a single object (i.e. we're not generating a discriminated union.). Do we have enough info to ensure that
... on User {
  Avatar
}
... on NotUser {
  Avatar
}

Will generate a coherent type? (I don't know Houdini's behavior here.)
Misc

Do aliases work?
Does suspense work as expected, i.e. the component (and not the parent) suspends?
Does @required work as expected? Do error boundaries?
What about infinite recursion, both direct (Avatar -> Avatar) and indirect (Avatar -> Foo -> Avatar)?
Will a VSCode extension suggest the auto-generated fragment? Is it accessible?

Wow thanks for taking the time to type all of that up!! It might be best to move this to discord where we can give each topic a thread but we'll see how far we can get here.

you will correctly get TypeScript inference for e.g. the size prop. Correct?
Does the Prop type that the user sees exclude the user prop?

The type generation still hasn't been added yet but since its totally "faked" (driven by a generated argument passed as a generic arg, not actually inferred from some value) i was planning on just tweaking the support for scalars to handle the Component scalar specially and leaving behind a function that omits the prop name and returns the same value as the passed component.

What if there are multiple @componentField annotations in the same props? Does Houdini fail gracefully in that case?

Right now, it checks for overlaps between all componentFields and the schema to ensure every field only has one canonical definition. The tests for that live here.

What if you have a legitimate need to pass a second fragment down

I think this is a perfect use-case for the ol' useFragment

How would @arguments be passed to Avatar?

Current thinking is that I will translate them to arguments on the field. Ie,
... on User @componentField(field: "Avatar") @arguments(size: { type: "Int"}) {

}

becomes
type User {
    Avatar(size: Int)
}

How do you add @defer etc to Avatar's fragment definition?

defer isn't supported at all in the framework so I think we punt on this for now. I imagine it would be able to be applied to the field and be treated as if it was applied to the fragment. They might not be semantically equivalent in all APIs but i'm not sure what else we could do 🤔

Equivalence between field and fragments re directives

So this was one of the reasons I wanted to keep the feature hidden behind a feature flag for a bit. I was just going to start by leaving directives in place at start and see if that works for people in the wild.

Neighboring Avatars

This is a good question. If we did want to prevent it, we could generate different scalars for every parent type but I'm not sure its a problem. From a type def generation point, it won't be an issue - every concrete member type of a union is generated independently so we can generate different field types even tho they're the same graphql type.

Do component aliases work?

Hadn't considered that! adding it to the task list now 👍  I think it's definitely something that should be supported.

What happens if the component alias conflicts...

If i'm following the situation correctly, i think it wouldn't validate just like normal graphql fields but I could be mistaken.

Does suspense work as expected

Right now, suspense is mostly driven by the page/layout components (so that the loading states compose correctly). I'm still working on the fragment part of the suspense story but haven't gotten to it. I was working on it in the time up to graphqlconf and then got distracted by your talk in the best way possible 😅

Does @required work as expected

The @required implementation predates our react support and svelte lacks an error boundary so there are no actions yet but its definitely something i want to add. I'm not sure it really make sense on a component field tho - just like it doesn't make sense for a fragment to have a null value.

What about infinite recursion

Since the fields are sugar for fragments I dont think this would pass validation

Will a VSCode extension suggest the auto-generated fragment? Is it accessible?

It won't see the __componentField__ fragments but that's by design. It will see the Avatar field since we already generate extensions that get picked up by the lsp.


BAEL-86: Unclosed Input Stream

I caught an unclosed input stream in the multipart file uploader that should be manually closed: https://github.com/eugenp/tutorials/blob/master/spring-dispatcher-servlet/src/main/java/com/baeldung/springdispatcherservlet/controller/MultipartController.java
This should also be updated in: http://www.baeldung.com/spring-dispatcherservlet

https://github.com/eugenp/tutorials/pull/3629

Hey @Thoughtscript  Thanks :) Merged and updated the article.

Hey @lor6 - thank you!


feat(pd): integrate pd-dist into hugegraph & add core tests, client tests, and REST tests for PD

subtask of https://github.com/apache/incubator-hugegraph/issues/2265

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

Project coverage is 41.70%.  Consider uploading reports for the commit 943c1db to get more accurate results

Additional details and impacted files
@@              Coverage Diff              @@
##             master    #2532       +/-   ##
=============================================
- Coverage     57.14%   41.70%   -15.45%
+ Complexity      827      272      -555
=============================================
  Files           608      608
  Lines         49415    49415
  Branches       6645     6645
=============================================
- Hits          28238    20607     -7631
- Misses        18361    26478     +8117
+ Partials       2816     2330      -486

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


Platform warnings should be skipped when using bundler/inline

I noticed that when using bundler/inline, I get the usual platform warnings for dependencies not meant for my platform:
The dependency activerecord-jdbcsqlite3-adapter (~> 51.0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for java. To add those platforms to the bundle, run `bundle lock --add-platform java`.
The dependency jruby-openssl (~> 0.10.1) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for java. To add those platforms to the bundle, run `bundle lock --add-platform java`.

However, since in the case of bundler/inline there's no lock file, I think these messages should be avoided?

We should still notify the user of unused platform gems, but adjust the message to not include bundle lock instructions

So what would be the solution for those cases? I don't like unresolvable warnings.

I'm not sure, does this message go away if the user sets platform: [:java] in the gem entry?


fix: avoid throwing an exception if the current selection no longer makes sense when initializing ySyncPlugin

Fixes https://github.com/yjs/y-prosemirror/issues/170.

Awesome PR!

Precise bug report
Reproducible code
Working fix that even uses lib0.math instead of Math.

It took me just a few minutes and saved me a lot of time. Thanks!!
Will merge, and release now. There should be a new release with a fix in a few minutes.


All matches on submitting license text show as "close"

If you enter a new license submittal with any text, it will show a green dialog box with the message "Close match found".  It should have an message that it does not match.
This may have been introduced with the recent PR for fixing the one word match fix https://github.com/spdx/spdx-license-matcher/pull/1

Added a more detailed issue for the UI: #211

Resolved with spdx/spdx-license-matcher#8


Does View Components Areas?

I have View Components, which are related to a specific Area only. It seems the View Component can not resolve views under paths like: "\Areas\Admin\Views\Shared\Components\Navigation"
Are the Areas supported?

I have View Components, which are related to a specific Area only.

This is not possible, view components and areas are unrelated features.  Putting [Area(...)] on a view component class has no meaning.
View lookup from view components uses the same set of search paths as the rest of the system, but with Components\Navigation appended. If the controller handling the current request is in the Admin area, then \Areas\Admin\Views\Shared\Components\Navigation will be part of the search paths.
My recommendation is, by default put views for a view component in Views\Shared\Components\<Name>. Use the more specific paths if you want to override how a component is styled for a certain part of your site.
The exception message you get when a view isn't found should include the paths are were tried, if it's still unclear I'd suggest experimenting with controllers in your Admin area and outside your area to see the difference.

Also a dup of https://github.com/aspnet/Mvc/issues/2640, which might have some further context and info.


[lain-box] permission denied

cd lain-box
vagrent up && vagrant ssh
lain update
lain config show
IOError: [Errno 13] Permission denied: '/usr/lib/python2.7/site-packages/protobuf-3.0.0b3-py2.7.egg/EGG-INFO/requires.txt'

sudo lain prepare
vagrant@lain goal]$ sudo lain prepare
>>> Generating prepare image...
>>> found shared prepare image at local.
>>> pushing image registry.lain.local/goal:prepare-0-1464172607 ...
The push refers to a repository [registry.lain.local/goal]
ab52d764c58e: Preparing
bc385ce46add: Preparing
5f70bf18a086: Preparing
841b2281a3bc: Preparing
8f01a53880b9: Preparing
Error: Status 405 trying to push repository goal: "\r\n<title>405 Not Allowed</title>\r\n\r\n
405 Not Allowed
\r\n
nginx\r\n\r\n\r\n"
>>> FAILED: docker push registry.lain.local/goal:prepare-0-1464172607
>>> Done lain prepare.

This was caused by a permission in protobuf tarball releases. For now it could be worked around by issuing these commands:
sudo rm -r /usr/lib/python2.7/site-packages/{protobuf*,lain*}
sudo pip install git+https://github.com/laincloud/entry.git
sudo pip install git+https://github.com/laincloud/lain-sdk.git
sudo pip install git+https://github.com/laincloud/lain-cli.git

An updated version of lain-box would be uploaded to Vagrant Cloud in a few hours.


Unmet dependencies with @vue2vis/network

Hi vue2vis team,
I am following this README to setup a NuxtJs project with @vue2vis/network. However I am getting the following unmet dependencies:

@egjs/hammerjs;
keycharm;
uuid;
vis-util/esnext/esm/vis-util.js;

Am I missing some step?
Reproduction
Install @vue2vis/network with:
yarn add @vue2vis/network vis-data moment

And create the following NuxtJs plugin to import the component:
import Vue from "vue";
import Network from "@vue2vis/network";

Vue.component("network", Network);

CodeSandbox example here:

https://codesandbox.io/s/vue2vis-network-build-error-j42h5?file=/plugins/vue2vis-network.js

Build Output
Here is the output of the dependencies not satisfied:
ERROR  Failed to compile with 4 errors               friendly-errors 09:39:41

These dependencies were not found:                    friendly-errors 09:39:41
                                                      friendly-errors 09:39:41
* @egjs/hammerjs in ./node_modules/vis-network/esnext/esm/vis-network.js
* keycharm in ./node_modules/vis-network/esnext/esm/vis-network.js
* uuid in ./node_modules/vis-network/esnext/esm/vis-network.js
* vis-util/esnext/esm/vis-util.js in ./node_modules/vis-network/esnext/esm/vis-network.js
                                                      friendly-errors 09:39:41
To install them, you can run: npm install --save @egjs/hammerjs keycharm uuid vis-util/esnext/esm/vis-util.js

Same problem for me with Timeline.

Same problem.


Too many reference sequences

This is strobealign 0.13.0-25-g3a97f6b-dirty
Time reading reference: 163.97 s
Reference size: 94366.30 Mbp (23452997 contigs; largest: 8.40 Mbp)
strobealign: Too many reference sequences. Current maximum is 8388607

@marcelm at what point did we reduce the nr of references? Is it that the 1 extra bit for MCS already got integrated in main in this version?  Previously we had 2^24=16M.
We should move the 8 offset bits to the hash value to allow 2^32 refs. Either we could put them in the unused top N bits of the hash, or we could put them in the lowest bit to allow later for distinguishing seeds with different lengths.
Copy of discussion in https://github.com/ksahlin/strobealign/issues/421

@yangzuokun Did you modify your copy of strobealign? When I use the same commit of strobealign as yours on an artificial reference with as many contigs as yours, I get:
This is strobealign 0.13.0-25-g3a97f6b
Time reading reference: 18.91 s
Reference size: 93.81 Mbp (23452997 contigs; largest: 0.00 Mbp)
strobealign: Too many reference sequences. Current maximum is 16777215

In strobealign 0.13.0, the maximum number of contigs is still $2^{24}-1$.

@marcelm at what point did we reduce the nr of references? Is it that the 1 extra bit for MCS already got integrated in main in this version?

Yes, that’s already in main and also in strobealign 0.14.0. So the maximum number of references is now $2^{23}-1$.
@yangzuokun I’ll close this soon; please follow the discussion in #421 instead.


Unhelpful error messages

Host operating system: output of uname -a
Linux  5.4.0-113-generic #127-Ubuntu SMP Wed May 18 14:30:56 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
flexlm_exporter version: output of flexlm_exporter --version

flexlm_exporter, version  (branch: , revision: )
  build user:
  build date:
  go version:       go1.19
  platform:         linux/amd64

Are you running flexlm_exporter in Docker?
No, running from systemd
What did you do that produced an error?
Can't seem to track down the event that cause the error, but for some reason it just stopped collecting data
What did you expect to see?
Expect status to yield no error messages or an error message that I can decipher
What did you see instead?
Nov 08 16:58:39 <host> level=error ts=2022-11-09T00:58:39.439Z caller=collector.go:173 lmstat="collector failed after:" 0.034567787=:
Nov 08 16:58:56 <host> level=error ts=2022-11-09T00:58:56.257Z caller=collector.go:173 lmstat="collector failed after:" 0.052950418=:
Nov 08 16:59:05 <host> level=error ts=2022-11-09T00:59:05.402Z caller=collector.go:173 lmstat="collector failed after:" 0.03479707=:
Nov 08 16:59:26 <host> level=error ts=2022-11-09T00:59:26.242Z caller=collector.go:173 lmstat="collector failed after:" 0.037066827=:
Nov 08 16:59:39 <host> level=error ts=2022-11-09T00:59:39.457Z caller=collector.go:173 lmstat="collector failed after:" 0.053389431=:
Nov 08 16:59:56 <host> level=error ts=2022-11-09T00:59:56.237Z caller=collector.go:173 lmstat="collector failed after:" 0.032255147=:
Nov 08 17:00:05 <host> level=error ts=2022-11-09T01:00:05.410Z caller=collector.go:173 lmstat="collector failed after:" 0.043314177=:
Nov 08 17:00:26 <host> level=error ts=2022-11-09T01:00:26.242Z caller=collector.go:173 lmstat="collector failed after:" 0.036626192=:
Nov 08 17:00:39 <host> level=error ts=2022-11-09T01:00:39.465Z caller=collector.go:173 lmstat="collector failed after:" 0.061041044=:
Nov 08 17:00:56 <host> level=error ts=2022-11-09T01:00:56.259Z caller=collector.go:173 lmstat="collector failed after:" 0.05391561=:

Update, this only errored due to running in sudo context. Ran it as a user and it worked

@abhinavDhulipala thanks for the update


parse android sdk ?

Hello
i face this issue in android sdk :
Logout function not clearing ParseUser currentUser in Android ?
Regards

This sounds like an issue in the android SDK. Please open an issue on that repo.


Update puppeteer to version 23.4.0

In #18771 we found that updating Puppeteer from version 23.3.0 to 23.4.0 caused new test failures. This is also reproducible locally. The logs from the bots can be found at http://<IP_ADDRESS>:8877/f9b8d1c303f789c/output.txt (Windows) and http://<IP_ADDRESS>:8877/902fcf449da1c69/output.txt (Linux). Version 23.3.1 doesn't have this issue locally, so we need to investigate what changed between 23.3.1 and 23.4.0 that causes some tests to fail and/or harden the tests against (intermittent) failure.

I have compared the Puppeteer 23.3.1 release with the Puppeteer 23.4.0 release and found the following commits: https://github.com/puppeteer/puppeteer/compare/puppeteer-v23.3.1...puppeteer-v23.4.0. There isn't really much interesting in there other than the Chrome update, and in http://<IP_ADDRESS>:8877/f9b8d1c303f789c/output.txt I noticed that the failures are (mostly) in Chrome. However, I think the problems in Chrome might point to pre-existing issues in the tests themselves that only surface now.

Unrelated to pdf.js but I am also getting unusual errors from 23.4 relative to 23.3. Basic things like not being able to connect to the server for the first few tests.

The issue exists in Puppeteer 23.5.0 too. The following logs contain the failures for me locally when running the integration tests against that version:

Puppeteer 23.5.0 integration test logs
Failures:
1) FreeText Editor Freetext must stay focused after having been moved must keep the focus
  Message:
    In chrome: Expected 0 to equal 1.
  Stack:
        at <Jasmine>
        at file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/test/integration/freetext_editor_spec.mjs:2326:14
        at async Promise.all (index 1)
        at async UserContext.<anonymous> (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/test/integration/freetext_editor_spec.mjs:2250:7)

2) Highlight Editor Highlight with the keyboard must check that some text has been highlighted
  Message:
    ProtocolError: Waiting for selector `#pdfjs_internal_editor_0` failed: Runtime.callFunctionOn timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.
  Stack:
        at <instance_members_initializer> (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:89:14)
        at new Callback (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:93:16)
        at CallbackRegistry.create (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:19:26)
        at Connection._rawSend (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/Connection.js:86:26)
        at CdpCDPSession.send (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/CDPSession.js:63:33)
        at #evaluate (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/ExecutionContext.js:355:50)
        at ExecutionContext.evaluateHandle (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/ExecutionContext.js:322:36)
        at IsolatedWorld.evaluateHandle (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/IsolatedWorld.js:86:30)
        at CdpJSHandle.evaluateHandle (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/api/JSHandle.js:147:37)
        at WaitTask.rerun (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/WaitTask.js:100:47)

3) Highlight Editor Highlight and caret browsing must check that selection is correctly highlighted on arrow down key pressed
  Message:
    ProtocolError: Waiting for selector `#pdfjs_internal_editor_0` failed: Runtime.callFunctionOn timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.
  Stack:
        at <instance_members_initializer> (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:89:14)
        at new Callback (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:93:16)
        at CallbackRegistry.create (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:19:26)
        at Connection._rawSend (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/Connection.js:86:26)
        at CdpCDPSession.send (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/CDPSession.js:63:33)
        at #evaluate (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/ExecutionContext.js:355:50)
        at ExecutionContext.evaluateHandle (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/ExecutionContext.js:322:36)
        at IsolatedWorld.evaluateHandle (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/IsolatedWorld.js:86:30)
        at CdpJSHandle.evaluateHandle (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/api/JSHandle.js:147:37)
        at WaitTask.rerun (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/WaitTask.js:100:47)

4) Highlight Editor Use a toolbar overlapping an other highlight must check that the toolbar is usable
  Message:
    ProtocolError: Waiting for selector `#pdfjs_internal_editor_0` failed: Runtime.callFunctionOn timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.
  Stack:
        at <instance_members_initializer> (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:89:14)
        at new Callback (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:93:16)
        at CallbackRegistry.create (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:19:26)
        at Connection._rawSend (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/Connection.js:86:26)
        at CdpCDPSession.send (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/CDPSession.js:63:33)
        at #evaluate (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/ExecutionContext.js:355:50)
        at ExecutionContext.evaluateHandle (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/ExecutionContext.js:322:36)
        at IsolatedWorld.evaluateHandle (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/IsolatedWorld.js:86:30)
        at CdpJSHandle.evaluateHandle (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/api/JSHandle.js:147:37)
        at WaitTask.rerun (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/WaitTask.js:100:47)

5) Ink Editor Basic operations must draw, undo/redo and check that the editor don't move
  Message:
    In chrome: Expected 420 to equal 121.
  Stack:
        at <Jasmine>
        at file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/test/integration/ink_editor_spec.mjs:133:14
        at async Promise.all (index 1)
        at async UserContext.<anonymous> (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/test/integration/ink_editor_spec.mjs:103:7)
  Message:
    In chrome: Expected 331 to equal 32.
  Stack:
        at <Jasmine>
        at file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/test/integration/ink_editor_spec.mjs:137:14
        at async Promise.all (index 1)
        at async UserContext.<anonymous> (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/test/integration/ink_editor_spec.mjs:103:7)

6) Interaction in issue15092.pdf must check that a value is correctly updated on a field and its siblings
  Message:
    ProtocolError: Runtime.callFunctionOn timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.
  Stack:
        at <instance_members_initializer> (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:89:14)
        at new Callback (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:93:16)
        at CallbackRegistry.create (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:19:26)
        at Connection._rawSend (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/Connection.js:86:26)
        at CdpCDPSession.send (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/CDPSession.js:63:33)
        at #evaluate (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/ExecutionContext.js:355:50)
        at ExecutionContext.evaluateHandle (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/ExecutionContext.js:322:36)
        at IsolatedWorld.evaluateHandle (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/IsolatedWorld.js:86:30)
        at CdpJSHandle.evaluateHandle (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/api/JSHandle.js:147:37)
        at WaitTask.rerun (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/WaitTask.js:100:47)

7) Interaction in bug1802888.pdf must check field value is treated by default as a number
  Message:
    In chrome: Expected '479' to equal '579'.
  Stack:
        at <Jasmine>
        at file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/test/integration/scripting_spec.mjs:1596:58
        at async Promise.all (index 1)
        at async UserContext.<anonymous> (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/test/integration/scripting_spec.mjs:1580:7)

8) Interaction Textfield with a zip code starting with 0 must check the zip code is correctly formatted
  Message:
    ProtocolError: Runtime.callFunctionOn timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.
  Stack:
        at <instance_members_initializer> (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:89:14)
        at new Callback (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:93:16)
        at CallbackRegistry.create (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:19:26)
        at Connection._rawSend (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/Connection.js:86:26)
        at CdpCDPSession.send (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/CDPSession.js:63:33)
        at #evaluate (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/ExecutionContext.js:355:50)
        at ExecutionContext.evaluate (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/ExecutionContext.js:270:36)
        at IsolatedWorld.evaluate (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/IsolatedWorld.js:97:30)
        at CdpJSHandle.evaluate (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/api/JSHandle.js:139:37)
        at awaitPromise (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/test/integration/test_utils.mjs:129:18)

9) Stamp Editor Basic operations must load a SVG, delete it and undo
  Message:
    ProtocolError: Runtime.callFunctionOn timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.
  Stack:
        at <instance_members_initializer> (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:89:14)
        at new Callback (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:93:16)
        at CallbackRegistry.create (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:19:26)
        at Connection._rawSend (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/Connection.js:86:26)
        at CdpCDPSession.send (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/CDPSession.js:63:33)
        at #evaluate (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/ExecutionContext.js:355:50)
        at ExecutionContext.evaluateHandle (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/ExecutionContext.js:322:36)
        at IsolatedWorld.evaluateHandle (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/IsolatedWorld.js:86:30)
        at CdpJSHandle.evaluateHandle (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/api/JSHandle.js:147:37)
        at WaitTask.rerun (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/WaitTask.js:100:47)

10) Text layer Text selection using mouse doesn't jump when hovering on an empty area in a single page
  Message:
    In chrome:
        Expected '' to roughly match 'code sequences, records
        them, and compiles them to fast native code. We call suc'.
  Stack:
        at <Jasmine>
        at file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/test/integration/text_layer_spec.mjs:138:18
        at async Promise.all (index 1)
        at async UserContext.<anonymous> (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/test/integration/text_layer_spec.mjs:116:11

If PR #19064 is merged I think we're down to two categories of issues I see locally with the newer versions of Puppeteer:

The Stamp Editor Basic operations must load a SVG, delete it and undo integration test, which fails pretty consistently locally and also on the bots sometimes already. This might actually be an issue in the editor code, which I have explained further in https://github.com/mozilla/pdf.js/issues/18396#issuecomment-2453547269 but don't actually know a good fix for yet.
The three highlight editor integration tests from https://github.com/mozilla/pdf.js/issues/18773#issuecomment-2395112248, which fail consistently locally but not (or barely) on the bots. This might also be an issue in the editor code or the tests that the new Puppeteer version merely surfaced: the editor never actually shows up after making the selection. I have had some luck with reproducing this by following the exact steps from the test in the viewer too, but I'm not sure on the root cause or fix here too.

The stamp editor issue is fixed by #19069, so only the highlight editor ones seem to remain.

The highlight editor issues are (at least partially) fixed by #19111.


Fix link to dacapo-bench.org in README

Thanks Stefan.   The problem was actually with the domain registration (something went wrong when that one was re-registered, apparently).   It was fixed, so no need to change the URL.


new exercise - series

[no important files changed]

it seems to be triggered because I edited the test file of another exercise, if you look at the changes I edited a simple comment line, there is no problem

it seems to be triggered because I edited the test file of another exercise, if you look at the changes I edited a simple comment line, there is no problem

Just to be clear what the above message means. If this PR is merged, the fact that a test file was updated would mean all of its solutions would have to be rerun in the test runner. Whilst the track is currently not yet live, this doesn't yet matter, but it will be important once it is live. The fact that it is "just a comment" is not something we can detect, so we'd have to rerun the solutions. However, you, the maintainer, can identify that it is "just a comment", in which case rerunning the tests wouldn't change any outcome. If this is true, you should add the [no important files changed] text to the commit message (you can add it when you get the commit text after pressing on Squash and merge).
See https://exercism.org/docs/building/tracks#h-avoiding-triggering-unnecessary-test-runs for more information.

it seems to be triggered because I edited the test file of another exercise, if you look at the changes I edited a simple comment line, there is no problem

Just to be clear what the above message means. If this PR is merged, the fact that a test file was updated would mean all of its solutions would have to be rerun in the test runner. Whilst the track is currently not yet live, this doesn't yet matter, but it will be important once it is live. The fact that it is "just a comment" is not something we can detect, so we'd have to rerun the solutions. However, you, the maintainer, can identify that it is "just a comment", in which case rerunning the tests wouldn't change any outcome. If this is true, you should add the [no important files changed] text to the commit message (you can add it when you get the commit text after pressing on Squash and merge).
See https://exercism.org/docs/building/tracks#h-avoiding-triggering-unnecessary-test-runs for more information.

Thanks you so much, I got it.


Rename start/stop to resume/suspend

Rename start/stop to resume/suspend to match what GCD and Cocoa are doing.
Affects:
HTTPServing protocol
HTTPServer class
PoCSocketSimpleServer

This PR would be blocked by #81
@carlbrown any thoughts?

I agree with @helje5 - #81 should happen first, and if it doesn't happen, this shouldn't, either.

ok I mistyped - I meant to say I agree that this PR is blocked by #81 for it to make sense.
Assuming #81 goes through, what are your thoughts on the renaming? @carlbrown

I think we need to consider what we want the lifecycle to be, and whether following Dispatch is the right approach for a server.
Dispatch queues have the following:

init: creates the queue, enabling work to be added, but is suspended.
resume: starts processing work on the queue
suspend: stops processing work on the queue
deallocate: shutdown the queue, running a finaliser function if provided

which I'm not convinced makes necessarily sense for a server. To be
I think the following are the likely possible events in the lifecycle:

init: creates the server and starts it to accept and process work
suspend: continues to accept work but doesn't process
resume: resumes from suspend
stop: stops the server, shuts down the port
start: starts the server, opens the port
shutdown: completely shutdown and destroy the server

Which of these do we think makes sense to have?
On a separate note, today if you call start() and then stop() immediately it results in a crash so we can't simply rename start/stop to resume/suspend.

When suggesting resume, I wasn't thinking of Dispatch, but of URLSessionTask's resume() method. Due to this Cocoa devs are familiar with that pattern (setup everything, then call resume to invoke it). I don't think resume/suspend is actually used a lot w/ Dispatch.
BTW: this uses cancel for stop/abort. Sounds reasonable to me too.
I also thought about this, but I'm against starting actual work in init. Quite often you want to wire up more stuff (make sure database connections are up, etc) before actually kicking of the stack. init should just configure the server.
Also keep in mind that the server might be running on a device, so you need to suspend/resume it when going to the background (which btw could assign new kernel assigned ports when going foreground again!).
P.S.: I don't get the thing about the start-stop crash, what does it have to do w/ the naming? start+stop shouldn't crash, neither should resume+suspend :->

P.S.: I don't get the thing about the start-stop crash, what does it have to do w/ the naming? start+stop shouldn't crash, neither should resume+suspend :->

It was an aside that really says that if we added a test as part of the PR for stop/start (or suspend/resume naming of the current APIs) it would crash - so theres more work to do than just naming.
Would this be the set that we'd ideally want?

init: sets up the server only
suspend: continues to accept work but doesn't process
resume: resumes from suspend, starts the server if not already started.
cancel: completely shutdown and destroy the server

I'm wondering whether we need some extra support for iOS back/foreground handling (you need to close the listen sockets and reopen them when going back to foreground). Or would we want the dev to restart the server from scratch? But then all connections would always die.
I guess it could also be automatic by listening to the notifications (but then you loose control when that happens, which might be important to the app).

@seabaylea I don't understand what continues to accept work but doesn't process means. Has the server started at this time? Is it listening and accepting connections?
Additional question is, do the following lifecycle make sense?

init
start
stop
start
stop
shutdown

Once we clarify the lifecycle of the server, we will make sure we have appropriate tests for them.

Btw if the lifecycle of the server has not been decided on, I can open a new issue to track that. Thoughts @carlbrown @seabaylea @helje5 ?

I think this could evolve into the issue tracking the lifecycle. (and the names would be just a result of this)

I don't understand what continues to accept work but doesn't process means

The socket would still be open, bound and listening, but not calling accept(). That will work until the kernel listen queue is full. I'm not entirely sure whether that is useful or not.
For iOS, apps really need to close when going bg and completely reopen listen socks when going fg (unless you have special VoIP like blessing, in that mode the kernel will ensure the listen sockets stay alive - which may or may not be another thing we would want to support).

Going to defer this one and see if it's still needed after #96

We still need to decide on lifecycle and naming, I'd reopen this one. #96 doesn't change much on the surface of the API (apart from the queue argument).

Opened #98 to track the discussions about server lifecycle.


Nicely handle missing user in collaborations

It is possible to have a collaboration in a repository which refers to a no-longer
existing user. This causes the repository transfer to fail with an unusual error.
This PR makes repo.getCollaborators() nicely handle the missing user by ghosting
the collaboration but also adds consistency check. It also adds an
Access consistency check.
Fix #17044
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

Codecov Report

Merging #17049 (38a2183) into main (45ebcb0) will increase coverage by 0.02%.
The diff coverage is 3.38%.

@@            Coverage Diff             @@
##             main   #17049      +/-   ##
==========================================
+ Coverage   45.22%   45.24%   +0.02%
==========================================
  Files         766      766
  Lines       86716    86650      -66
==========================================
- Hits        39217    39209       -8
+ Misses      41148    41087      -61
- Partials     6351     6354       +3

Impacted Files
Coverage Δ

models/access.go
70.55% <0.00%> (-0.80%)
:arrow_down:

models/repo_transfer.go
42.25% <0.00%> (-1.23%)
:arrow_down:

modules/doctor/dbconsistency.go
6.83% <0.00%> (+2.81%)
:arrow_up:

models/repo_collaboration.go
56.20% <36.36%> (-2.42%)
:arrow_down:

models/gpg_key_common.go
59.67% <0.00%> (-4.84%)
:arrow_down:

modules/queue/queue_channel.go
91.66% <0.00%> (-3.34%)
:arrow_down:

modules/process/manager.go
72.83% <0.00%> (-2.47%)
:arrow_down:

modules/queue/workerpool.go
47.32% <0.00%> (-1.15%)
:arrow_down:

models/repo_list.go
77.64% <0.00%> (-0.79%)
:arrow_down:

services/pull/pull.go
41.78% <0.00%> (-0.41%)
:arrow_down:

... and 2 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 45ebcb0...38a2183. Read the comment docs.


Expose anchoredDigestRegexp outside of the reference package

Export anchoredDigestRegexp in the reference package and allow users of the package not to reanchor the DigestRegexp.

Commented in PR


Adds grunt-assemble plugin to devDependencies

Adding this dependency to the package.json allows the grunt task "assemble" to succeed. Currently (following the contribution guide), It fails when running grunt preview and other commands.
Issue #744

Great, thanks! I must have missed the --save-dev flag on the recent stack update :-(


Filter out sources that do not match the shard database/retention policy

If you use a statement like this:
SELECT value FROM one..cpu, two..cpu

It will access both the one and two databases as if you had selected
the cpu measurement twice for both of them. Updated the tsdb.Shard
create iterator function to filter out any sources that do not apply to
that shard so this duplication doesn't happen.
Fixes #6701.

:+1:


Feat: Add places

Can you add places as well currently game always drops us to random road it would be fun if game gives hs famous place or something like that

Custom maps are now added! Check out some famous place maps:
https://www.worldguessr.com/map/famous-places
https://www.worldguessr.com/map/popular-places


Add freedownloadmanager version 5.1.38

Close #1598

Fixed manifest
{
    "version": "5.1.38",
    "description": "Powerful modern download accelerator and organizer for Windows and Mac.",
    "homepage": "https://www.freedownloadmanager.org/",
    "license": "Freeware",
    "architecture": {
        "64bit": {
            "url": "https://dn3.freedownloadmanager.org/5/5.1-latest/fdm5_x64_setup.exe",
            "hash": "0c05843c56eb0411d1baf2ab5d82207ecbad3fcbb7f7cb8eede1b4b43946bd6d"
        },
        "32bit": {
            "url": "https://dn3.freedownloadmanager.org/5/5.1-latest/fdm5_x86_setup.exe",
            "hash": "69cca0d59a37fefe70fe0f8308cb063215bc2687b2305c996cb216141e516f16"
        }
    },
    "installer": {
        "script": [
            "& (Get-HelperPath 'innounp') -x -d\"$dir\" \"$dir\\$fname\" -y | Out-Null",
            "Move-Item \"$dir\\{app}\\*\" \"$dir\" | Out-Null",
            "Move-Item \"$dir\\{code_CefInstallDir}\\*\" \"$dir\" | Out-Null",
            "@('install_script.iss', '{app}', '{code_CefInstallDir}') | ForEach-Object {",
            "    Remove-Item \"$dir\\$_\" -Recurse",
            "}"
        ]
    },
    "shortcuts": [
        [
            "fdm.exe",
            "Free Download Manager"
        ]
    ],
    "checkver": "FDM ([\\d.]+) for Windows 10",
    "autoupdate": {
        "architecture": {
            "64bit": {
                "url": "https://dn3.freedownloadmanager.org/$majorVersion/$majorVersion.$minorVersion-latest/fdm$majorVersion_x64_setup.exe"
            },
            "32bit": {
                "url": "https://dn3.freedownloadmanager.org/$majorVersion/$majorVersion.$minorVersion-latest/fdm$majorVersion_x86_setup.exe"
            }
        }
    }
}

Get-HelperPath is not merged into master yet, will do after https://github.com/lukesampson/scoop/pull/3449 being merged.

@h404bi see https://github.com/lukesampson/scoop-extras/issues/2150


Chore/update nx (Angular 13.x)

Description

References

#0000

https://github.com/Energinet-DataHub/greenforce-frontend/blob/669b0beb1a4956ab6e41e7e65cbc76cb467a5b7a/libs/dh/metering-point/feature-overview/src/lib/dh-metering-point-overview.component.spec.ts#L93-L103
@LayZeeDK This test fails with Class constructor ComponentStore cannot be invoked without 'new' error pointing to local-router-component-store.ts file. Do you have an idea what might be causing it?

Did we provide the local component store in the component tree? Otherwise, try the GlobalRouterStore, it has a root provider.

Did we provide the local component store in the component tree? Otherwise, try the GlobalRouterStore, it has a root provider.

@LayZeeDK Yes the component store is provided directly inside of the component

I'll look into it tomorrow unless we have sprint planning.

@frontend-specialisten We're already behind 😀 https://blog.nrwl.io/redesigned-starter-page-storybook-6-4-eslint-8-and-more-in-nx-13-3-5507d7378360

@frontend-specialisten We're already behind 😀 https://blog.nrwl.io/redesigned-starter-page-storybook-6-4-eslint-8-and-more-in-nx-13-3-5507d7378360

@dzhavat I will run the migrations again 😅


TypeError: Cannot read property 'rendered' of null (v3)

I have a fairly simple component that renders another component, its navigation. I have test in place to test whether it has been rendered inside. I'm using Jest and Enzyme v3.
  it('renders navigation', () => {
    const component = mount(
      <Calendar />
    );

    const navigation = component.find('.react-calendar__navigation');

    expect(navigation.length).toBe(1);
  });

Interestingly, this test passed without any issues on my computer. However, on Travis CI, I got the following error:
TypeError: Cannot read property 'rendered' of null

  at Object.getNode (node_modules/enzyme-adapter-react-16/build/ReactSixteenAdapter.js:233:69)
  at new ReactWrapper (node_modules/enzyme/build/ReactWrapper.js:100:33)
  at mount (node_modules/enzyme/build/mount.js:19:10)
  at Object.<anonymous> (src/__tests__/Calendar.jsx:13:39)
      at Promise (<anonymous>)
      at <anonymous>
  at process._tickCallback (internal/process/next_tick.js:188:7)

The code worked fine on Enzyme 2.9.1. Do you have any hints on what I could be doing wrong?

My bad, for some reason React stayed at 15.6.1 causing this error.

Lol... Had the same thing happen. This issue made me check my package.json and feel shame. Quickly after the shame faded, my tests were working again though. Thanks!

Same shame..  so sad


[WM-2427] Remove ability for Cromwell appTypes to be deleted

Jira Ticket: https://broadworkbench.atlassian.net/browse/WM-2427

Summary of changes:

What

Removing Cromwell app types from being displayed on the Clusters page

Why

Currently, deleting a Cromwell app type will put a workspace into an error state. To avoid users from deleting these apps and erroring their workspace, we want to stop a user from being able to delete, but still show them information regarding their apps.

Testing strategy

[x] Unit tests

Before:

After:

Do I understand correctly that the only way to delete cromwell app types on either cloud is through deleting the workspace?

That's my understanding. I'm not totally clear about the fine details, but since reconnecting to a previously running app state is not supported, manually deleting from the clusters page throws the associated workspace into a weird state.

Great, thanks for cleaning this up! One small nit about removing a TODO you addressed.
Eventually, I would like to see canDeleteResource call canDeleteApp so the call site doesn't need to choose which function to call, but I don't feel super strongly about doing that this iteration since you've already left the code in a much better place than when you started

I agree with your point. I think the goal is for canDeleteApp to be temporary. Once there is handling of deleting Cromwell-type apps, canDeleteResource should be the only decider for all resource types.


[WIP] Drop templatizer dependency

It will fix #91. I am still working on it, please do not merge.

I've squashed all valuable stuff from this branch into 6d5343fe403b203bf044c7aff1ca077d0c3361f5. This branch have no use now.


Initialize extension and completion provider for typescriptreact

Description
Initialize extensions and completion provider for typescript react (*.tsx) files.

Perfect @asvetliakov
Thanks!
Just one thing: would you mind to add this change to the CHANGELOG?
I'm not really around this weekend, so I can click merge afterwards :-)
Cheers and thanks for the contribution!

@buehler Sure, done


Dockerhub seems not using --no-cache to autobuild the updated code

I checked the logs. it seems the auto-builds all using caches.

Oh, I find the option to build without caches. I will close this issue then.


PARTIAL TAGALOG TRANSLATION FOR dictionary.md

Hi.
Please consider my partial translation for dictionary.md file which translated into Tagalog words dictionary_FIL.md file.
Thank you.

I already completed the Tagalog Translation on this file. See in the Filipino Translations Branch.


Data Link cannot work

Hello,
When I click the data link, it can't show the page. I wonder where can download the datasets, please.
Sorry for disturbing you.

I (probably) found the corresponding project page a few minutes ago.
And I downloaded the data from the below page. I hope this helps you, thanks.
http://www.josephdegol.com/pages/TagSfM_ECCV18.html

I (probably) found the corresponding project page a few minutes ago. And I downloaded the data from the below page. I hope this helps you, thanks.
http://www.josephdegol.com/pages/TagSfM_ECCV18.html

Thank you so much!!!
It works!


Rawtypes and unchecked conversions

In version 0.4.5, it generates code along these lines:
public static final class MoshiJsonAdapter extends JsonAdapter<TextViewerCfg> {
  private final JsonAdapter<String> syntaxAdapter;
  public MoshiJsonAdapter(Moshi moshi) {
    // warning: unchecked conversion
    this.syntaxAdapter = adapter(moshi, String.class);
  }
  // warning: rawtype
  private JsonAdapter adapter(Moshi moshi, Type adapterType) {
    return moshi.adapter(adapterType);
  }
...

These compile warnings are fixed by this:
private <T> JsonAdapter<T> adapter(Moshi moshi, Type adapterType) {

Open to a PR fixing this?

Please do!


Cannot find csrf

i was able to submit code without this error and now suddenly i am getting the msg of (cannot find csrf)

Same here, get any solution now?

Same, I can't even login...

Cannot find csrf
this is serious and need attention


[BUG] - Selecting some packages when creating an env reloads the page

Describe the bug

open the new green UI at /
click on + to create environment
+Add package -> type “anaconda”
Page reloads

Repros every time.
I think I've seen this with some other packages as well.
Expected behavior
Package is added.
OR: if this package causes problems, it shouldn't be listed.
How to Reproduce the problem?
See above.
Output
No response
Versions and dependencies used.
229f3ac1e56d6dce5890dffebc9c2d0c26dacabf
Anything else?
No response

Just to note, I couldn't reproduce this on the conda-store running on nebari.quansight.dev. I'm not certain what versions are currently being used there.


I have a issue of syntax with Aqueduct and Postgres. And I didn't find the solution.

aqueduct db upgrade --connect postgres://read:read@localhost:5432/reads
-- Aqueduct CLI Version: 3.2.1
-- Aqueduct project version: 3.2.1
-- Updating to version 1 on new database...
PostgreSQL connecting, read@localhost:5432/reads.
Initializating database...
CREATE TABLE _aqueduct_version_pgsql (versionNumber INT NOT NULL UNIQUE,dateOfUpgrade TIMESTAMP NOT NULL)
Applying migration version 1...
CREATE TABLE _Read (id BIGSERIAL PRIMARY KEY,title TEXT NOT NULL UNIQUE,author TEXT NOT NULL,year INT NOT NULL)
Seeding data from migration version 1...
*** There was an issue. Reason: syntax error at end of input. Table: null Column: null

Hi @lucasellery
you might want to open the issue on aqueduct's github.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you


Change path for windows setup

The documentation could save several lines by using %appdata% instead of C:\Users\username\AppData\Roaming

Opening so I don't forget this when I update readmes in a week or two.

For review at https://github.com/lbryio/lbrycrd/tree/depends_build_all

merged to master now


Custom Attribute Mapping example does not work for Custom Attributes added to Azure Active Directory Schema and other fields

The custom attribute sync mentioned in example on this page does not sync

employeeHireDate (this is a custom field in source but already present in Azure Active Directory attributes list by default)
Custom Fields added to Azure Active Directory schema (by enforcing AAD Schema Editor to true) and mapped with custom attributes in Source
Multi Valued Custom Fields added to Azure Active Directory schema (by enforcing AAD Schema Editor to true) and mapped with custom attributes in Source)

It throws the following error in Provisioning Logs. There are no issues with field name. It doesn't contain special characters and uses Title Case.
MyCustomFieldName is not a valid propertyName. This operation was retried 0 times. It will be retried again after this date
employeeHireDate gets synced/populated only if the value contains the Time part. "2021-05-01T00:00:00-05:00" gets synced but "2021-05-01" does not get synced.

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

ID: a59dad83-c2cb-fc27-bfa0-2dbf91303166
Version Independent ID: a9a1c464-5de2-e955-dbd1-3f5418c9f293
Content: Extend API-driven provisioning to sync custom attributes - Microsoft Entra ID
Content Source: docs/identity/app-provisioning/inbound-provisioning-api-custom-attributes.md
Service: active-directory
Sub-service: app-provisioning
GitHub Login: @kenwith
Microsoft Alias: kenwith

@MithunChopda
Thanks for your feedback! We will investigate and update as appropriate.

Hi @MithunChopda
The error message you provided suggests that the custom attribute name you are using is not valid. Here are some guidelines to follow when creating custom attribute names:

Custom attribute names must be unique within the directory.
Custom attribute names must start with a letter and can only contain letters, numbers, and underscores.
Custom attribute names cannot exceed 64 characters in length.
Custom attribute names are case-insensitive.

Please make sure that your custom attribute name follows these guidelines.
Regarding the issue with the employeeHireDate attribute, it appears that the attribute is only being synced when the value contains the time part. This behavior is expected because the employeeHireDate attribute in Azure Active Directory is of type "DateTimeOffset", which requires a time component. If the value being synced does not contain a time component, it will not be synced.
To resolve this issue, you can update the value being synced to include a time component. Alternatively, you can change the data type of the employeeHireDate attribute in Azure Active Directory to "Date", which does not require a time component. However, please note that changing the data type of an attribute in Azure Active Directory can have unintended consequences and should be done with caution.
I hope this information helps you resolve the issue. If you have any further questions or concerns, please let me know.

Thanks @ManoharLakkoju-MSFT
The custom attribute name is not invalid.
There are more issues here. The inbound API driven provisioning job works when the same custom field is added using Graph API.
Is there a way to find list of default attibutes and its schema?
Another issue is with Sponsors attribute. This attribute too doesn't get synchronized using bulk upload.

@MithunChopda
I'd recommend working closer with our support team via an [Azure support request] (https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request). Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.
[Teams Q&A forum] (https://docs.microsoft.com/en-us/answers/topics/46488/office-teams-windows-itpro.html) for technical questions about the configuration and administration of Microsoft Teams on Windows.
[Microsoft Teams Community forum] (https://answers.microsoft.com/en-us/msteams/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1)
Thank you for your time and patience throughout this issue.


new starter

react-admin-starter
move into gitlab
+api +deployment +idp +dev-setup

See https://github.com/vivid-planet/comet-admin-starter/pull/36#issuecomment-756144635

See https://github.com/vivid-planet/comet-admin-starter/pull/36#issuecomment-756144635