Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

The problem
Not sure if I am missing something here but I get a "Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble" message after being redirected back to Home Assistant when signing into Miele. Have tried with different versions and on a different browser but that did not help.

Version of miele integration having the issue?
v0.1.17
Version of Home Assistant Core having the issue?
2023.11.1
Anything in the logs that might be useful for us?
2023-11-10 00:35:39.665 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 31, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 148, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 63, in with_admin
    return await func(self, request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 170, in get
    return await super().get(request, flow_id)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 96, in get
    result = await self._flow_mgr.async_configure(flow_id)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 293, in async_configure
    result = await self._async_handle_step(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 389, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 315, in async_step_creation
    token = await self.flow_impl.async_resolve_external_data(
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 172, in async_resolve_external_data
    return await self._token_request(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 209, in _token_request
    resp.raise_for_status()
  File "/usr/local/lib/python3.11/site-packages/aiohttp/client_reqrep.py", line 1005, in raise_for_status
    raise ClientResponseError(
aiohttp.client_exceptions.ClientResponseError: 401, message='Unauthorized', url=URL('https://api.mcs3.miele.com/thirdparty/token')
2023-11-10 00:35:55.732 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 31, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 148, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 63, in with_admin
    return await func(self, request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 170, in get
    return await super().get(request, flow_id)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 96, in get
    result = await self._flow_mgr.async_configure(flow_id)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 293, in async_configure
    result = await self._async_handle_step(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 389, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 315, in async_step_creation
    token = await self.flow_impl.async_resolve_external_data(
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 172, in async_resolve_external_data
    return await self._token_request(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 209, in _token_request
    resp.raise_for_status()
  File "/usr/local/lib/python3.11/site-packages/aiohttp/client_reqrep.py", line 1005, in raise_for_status
    raise ClientResponseError(
aiohttp.client_exceptions.ClientResponseError: 401, message='Unauthorized', url=URL('https://api.mcs3.miele.com/thirdparty/token')
2023-11-10 00:36:11.957 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 31, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 148, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 63, in with_admin
    return await func(self, request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 170, in get
    return await super().get(request, flow_id)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 96, in get
    result = await self._flow_mgr.async_configure(flow_id)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 293, in async_configure
    result = await self._async_handle_step(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 389, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 315, in async_step_creation
    token = await self.flow_impl.async_resolve_external_data(
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 172, in async_resolve_external_data
    return await self._token_request(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 209, in _token_request
    resp.raise_for_status()
  File "/usr/local/lib/python3.11/site-packages/aiohttp/client_reqrep.py", line 1005, in raise_for_status
    raise ClientResponseError(
aiohttp.client_exceptions.ClientResponseError: 401, message='Unauthorized', url=URL('https://api.mcs3.miele.com/thirdparty/token')
2023-11-10 00:37:47.028 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 31, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 148, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 63, in with_admin
    return await func(self, request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 170, in get
    return await super().get(request, flow_id)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 96, in get
    result = await self._flow_mgr.async_configure(flow_id)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 293, in async_configure
    result = await self._async_handle_step(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 389, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 315, in async_step_creation
    token = await self.flow_impl.async_resolve_external_data(
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 172, in async_resolve_external_data
    return await self._token_request(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 209, in _token_request
    resp.raise_for_status()
  File "/usr/local/lib/python3.11/site-packages/aiohttp/client_reqrep.py", line 1005, in raise_for_status
    raise ClientResponseError(
aiohttp.client_exceptions.ClientResponseError: 401, message='Unauthorized', url=URL('https://api.mcs3.miele.com/thirdparty/token')

Additional information
No response

I have a few questions trying to understand what is going on here:

Has it worked before? or is this your first attempt till install the integration?
The UI says Error 500, can you find a 500 error in home Assistant log?
The log says error 401. That indicates an authorization error. Something is wrong with your login credentials, the redirect back to HA - or something else. You can verify your credentials at https://www.miele.com/developer/swagger-ui/

Just logged into swagger (browser autofilled my info) and everything worked fine, devices returned and all.
This is the first time I have tried it on HA but have uninstalled and reinstalled multiple times (restarting HA in-between). For extra context my instance is running on proxmox LXC. (No complicated VLAN setups or anything like that).
When I press configure, it does not ask for my client id or secret, is that normal? Strangely enough the 401 error is the only error showing in the logs, not a 500.

Just logged into swagger (browser autofilled my info) and everything worked fine, devices returned and all.
This is the first time I have tried it on HA but have uninstalled and reinstalled multiple times (restarting HA in-between). For extra context my instance is running on proxmox LXC. (No complicated VLAN setups or anything like that).

I have no experience of running in LXC. However, I have lots of experience of installing as a HAOS VM on Proxmox with no problems at all. It could be that the redirect URL suggested by HA is wrong in your context.

When I press configure, it does not ask for my client id or secret, is that normal? Strangely enough the 401 error is the only error showing in the logs, not a 500.

Client ID and secret are often retained deep in HA even after uninstall of the integration. Look here https://github.com/astrandb/miele/discussions/247 how to remove the credentials to make a fresh install.
A detailed description of a successful installation can be found here https://github.com/astrandb/miele/discussions/366

All working now after resetting the credentials. Must have been a typo with the name. Thank you for the help!
Might be worth making a note of this error in the docs as it is pretty undescriptive.

Might be worth making a note of this error in the docs as it is pretty undescriptive.

These errors are caught and handled in oauth2 helpers in Home Assistant and this integration is not really involved. However, I have seen that the same undescriptive error messages are popping up in official integrations also. There is work going on to correct and extend the oauth2 error handling and I expect that we will se much more descriptive errors in next release of HA


Features that represent biological signals

Hi,
I’m  interested in the part that you have investigated the biological relevance of extracted latent features. However, I have not been bale to figure where you find the dimensions that are say most important in distinguishing patients' sex. It appears that this is feature 82. Is this feature 82 (out of 100) in the latent space of VAEs with one hidden layer, or two hidden layer? I’m guessing it’s the latter, which is why I was looking into tybalt_twohidden.ipynb. However, here only weights for all samples are extracted based on multiplying the weights of the two hidden layers. So the question I was hoping you can help me with is in the vae with two hidden layer, how the latent feature(s) that distinguishes patients's sex is identified as 82?

Hi @ZohrehShams - thanks for your interest in our project! I will answer your questions below.

Is this feature 82 (out of 100) in the latent space of VAEs with one hidden layer, or two hidden layer?

The model with one hidden layer. This is the model presented in the PSB paper.

how the latent feature(s) that distinguishes patients's sex is identified as 82?

I used a brute force approach for this particular case - this shiny app (also documented in the paper) helped https://gregway.shinyapps.io/pancan_plotter/
Brute force is not satisfying and is not scalable. We also developed this method which may also be of interest.

Thanks very much for your reply and the clarification. Then in tybalt_two hidden is it possible to extract gene's weight for specific targets (gender = male)? As it stands now the count_high_weight_genes which is based on extracted weights, does the counting for all samples. Thanks very much.


okhttp fails to build when complies with Java version 1.6 for android

Set JAVA_HOME to use jdk1.6 and run "mvn compile" on the latest master branch, then get the following build errors.  This is an issue since this makes okhttp unable to build for android apps where jdk1.6 is required.
[INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ okhttp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 44 source files to /Users/leehwa/Programming/ThirdParty/okhttp/okhttp/target/classes
[INFO] -------------------------------------------------------------
[WARNING] COMPILATION WARNING :
[INFO] -------------------------------------------------------------
[WARNING] Note: Some input files use or override a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[INFO] 2 warnings
[INFO] -------------------------------------------------------------
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /Users/leehwa/Programming/ThirdParty/okhttp/okhttp/src/main/java/com/squareup/okhttp/internal/http/HttpsURLConnectionImpl.java:[304,3] method does not override or implement a method from a supertype
[ERROR] /Users/leehwa/Programming/ThirdParty/okhttp/okhttp/src/main/java/com/squareup/okhttp/internal/http/HttpsURLConnectionImpl.java:[309,20] cannot find symbol
symbol  : method getContentLengthLong()
location: class com.squareup.okhttp.internal.http.HttpURLConnectionImpl
[ERROR] /Users/leehwa/Programming/ThirdParty/okhttp/okhttp/src/main/java/com/squareup/okhttp/internal/http/HttpsURLConnectionImpl.java:[308,3] method does not override or implement a method from a supertype
[ERROR] /Users/leehwa/Programming/ThirdParty/okhttp/okhttp/src/main/java/com/squareup/okhttp/internal/http/HttpsURLConnectionImpl.java:[313,20] cannot find symbol
symbol  : method getHeaderFieldLong(java.lang.String,long)
location: class com.squareup.okhttp.internal.http.HttpURLConnectionImpl
[ERROR] /Users/leehwa/Programming/ThirdParty/okhttp/okhttp/src/main/java/com/squareup/okhttp/internal/http/HttpsURLConnectionImpl.java:[312,3] method does not override or implement a method from a supertype
[INFO] 5 errors
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] OkHttp (Parent) ................................... SUCCESS [5.224s]
[INFO] OkHttp SPDY and HTTP/2.0 internals ................ SUCCESS [10.657s]
[INFO] MockWebServer ..................................... SUCCESS [2.771s]
[INFO] OkHttp ............................................ FAILURE [0.401s]
[INFO] OkHttp Apache HttpClient .......................... SKIPPED
[INFO] OkCurl ............................................ SKIPPED
[INFO] Samples (Parent) .................................. SKIPPED
[INFO] Sample: Guide ..................................... SKIPPED
[INFO] Sample: Simple Client ............................. SKIPPED
[INFO] Sample: Static Server ............................. SKIPPED
[INFO] Benchmarks ........................................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 19.676s
[INFO] Finished at: Thu Feb 13 13:16:06 PST 2014
[INFO] Final Memory: 14M/81M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.0:compile (default-compile) on project okhttp: Compilation failure: Compilation failure:
[ERROR] /Users/leehwa/Programming/ThirdParty/okhttp/okhttp/src/main/java/com/squareup/okhttp/internal/http/HttpsURLConnectionImpl.java:[304,3] method does not override or implement a method from a supertype
[ERROR] /Users/leehwa/Programming/ThirdParty/okhttp/okhttp/src/main/java/com/squareup/okhttp/internal/http/HttpsURLConnectionImpl.java:[309,20] cannot find symbol
[ERROR] symbol  : method getContentLengthLong()
[ERROR] location: class com.squareup.okhttp.internal.http.HttpURLConnectionImpl
[ERROR] /Users/leehwa/Programming/ThirdParty/okhttp/okhttp/src/main/java/com/squareup/okhttp/internal/http/HttpsURLConnectionImpl.java:[308,3] method does not override or implement a method from a supertype
[ERROR] /Users/leehwa/Programming/ThirdParty/okhttp/okhttp/src/main/java/com/squareup/okhttp/internal/http/HttpsURLConnectionImpl.java:[313,20] cannot find symbol
[ERROR] symbol  : method getHeaderFieldLong(java.lang.String,long)
[ERROR] location: class com.squareup.okhttp.internal.http.HttpURLConnectionImpl
[ERROR] /Users/leehwa/Programming/ThirdParty/okhttp/okhttp/src/main/java/com/squareup/okhttp/internal/http/HttpsURLConnectionImpl.java:[312,3] method does not override or implement a method from a supertype
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :okhttp

Hi @monteiz I forked the okhttp to support Java 6 https://github.com/Nextpeer/okhttp
Take a look if it still bugs you.

Thanks @ItamarM but at the moment I do not use okhttp.
Cheers

I also required a java 1.6 build of okhttp but I needed an updated one for v2.3 so I forked @ItamarM again to bring the repo up to date with square
Furthermore, I had to fork directly from square/okio to generate a java 1.6 friendly build of okio (1.3.0) required by okhttp.
https://github.com/bluebery/okhttp
https://github.com/bluebery/okio

The Building wiki page says

Runtime compatibility with Java 6 is enforced as part of the build to ensure compliance with Android and older versions of the JVM.

so Java 6 is supported in runtime, right? But the [home page] says:

OkHttp supports Android 2.3 and above. For Java, the minimum requirement is 1.7.

which one is correct?

We require Java 7 or Android 2.3. The building page is out of date.

@bluebery I cloned your two repos and opened them up in IntelliJ. When I went to build the whole project after importing it, many of the files still failed to build. It turns out that the okhttp/okhttp part of the library will build fine for Java 1.6, however many of the other modules will not, due to the diamond operator. It may be worth clearing this up in your README.md so others don't waste time, or completely bypass your repo if all they need is the okhttp/okhttp module to be Java 1.6 compatible. I plan to submit a PR with many of the other modules fixed up with the Java 1.6 compatible use of the diamond operator.
I also wanted to drop this note here for anyone else looking for a Java 1.6 compliant version of this library (or just a part of it) as I was.

@cameron-gagnon good work. Sorry I didn't maintained my forked repo.


Importing a private AKS cluster results in the registration tab being absent in the cluster details view

Rancher Server Setup

Rancher version: v2.6-head https://github.com/rancher/rancher/commit/e35d32feea3ff9511d972b87f14a4f66b194db39
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE2

Proxy/Cert Details:

Information about the Cluster

Kubernetes version: v1.23.5
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): Imported AKS

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom) Standard

If custom, define the set of permissions:

Describe the bug

When importing a private AKS cluster into Rancher, you are able to register the cluster as expected. What is unexpected is that when you look into the cluster details, there is no registration tab. See below:

Whether you create a private AKS cluster via the Azure UI or use the az cli, the above result is the same. One point to consider is that the cluster agent uses the cattle service account in Rancher to authenticate for redeploy on a private cluster. However....the cattle service account and the secret autogenerated for it were not created in Rancher.
Additionally, I was able to verify this behavior in v2.6.5 as well, so this is not a direct regression from the last release per say.
To Reproduce

Create a private AKS cluster using either the az cli or directly in the Azure marketplace.

Versions v1.23.5 and v1.22.6 both showed this behavior.
Network policy that is chosen will not matter, issue happens regardless if you choose None or specify a CNI.

Setup Rancher v2.6-head and navigate to the UI in a browser.
Create a standard user and login to Rancher as that newly-created user.
In Cluster Management, import an existing cluster and choose AKS.
Fill out the prompted information and import the previously created private AKS cluster.
As it is being created, click the cluster and you should NOT see the registration tab.

Result
The registration tab is not present when importing an existing private AKS cluster.
Expected Result

The registration tab should be present when importing an existing private AKS cluster.

Related to https://github.com/rancher/dashboard/issues/4545 (though that's EKS)

We have some rules that we use to conditionally render the registration tab so we might need to revisit those to understand what needs to change. As it stands now, I don't have enough information to make an informed decision about why the Registration tab might not be showing and what we would need to modify in order to correctly show it. Here's the rundown of the logic for rendering the registration tab:
If there is no cluster token
  Don't render the Registration Tab

If the cluster is Imported
  If management is ready
    Don't render the Registration Tab
  Else
    Render the Registration Tab

If the cluster is custom
  Render the Registration Tab

If none of the conditions above
  Don't Render the Registration Tab

This change came in about a year ago, in response to #3337. But the only requirement that I can glean from the change is the we shouldn't show the Registration tab when the cluster is "Ready".
https://github.com/rancher/dashboard/pull/3381/files
@gaktive @markusewalker

@kwwii to review the flow around this section and @jordojordo to take this over from @rak-phillip. This may address https://github.com/rancher/dashboard/issues/6112 but TBD.

Following a discussion with @kwwii, we decided it would make sense to modify this conditional here to show the registration tab depending on some arbitrary condition like status: Unknown, type: Pending.
After some investigation, I found that there is no way to know if an imported cluster is using a private endpoint unless the cluster agent has connected, which it cannot do if not provided the private endpoint (naturally).
We should add a banner warning the user of using the registration command more than once, for example:

"When importing a cluster with a private API server endpoint - it will need to be registered the first time in order to complete the import. Running the command a second time will cause serious issues."

With that in place we should also have a button to show the registration commands to acknowledge that the user has seen the warning.

@jordojordo What serious issues would be caused by running the import command a second time? There are some valid uses cases when a downstream cluster's agent workload was accidentally modified and the best way to recover or repair is to re-run the import to repair configuration, deployment, pods, etc. Is the "serious issues" warning needed or warranted?

@richard-cox Can you explain the issues that arose for you when running this command after the cluster had already been imported?
Does anyone know if there a difference in behavior when running this command again after import in AKS vs EKS clusters? (There are similar issues open for both types)

Thought about this last night, and i had it the other way around. I'd brought up a new rancher and imported an existing cluster that was connected to a previous rancher. The cluster had references to system/default projects from the old rancher and thus namespaces weren't grouped correctly in the project/namespace list.

In that case, we can always show the Registration tab with the information and add a warning that they should not import a cluster which has already been connected to another instance of Rancher as it will lead to data corruption (or something like that).

There's also concern that the registration command can be inadvertently run on a different cluster, breaking the current cluster.

Once the cluster is imported it's useless and also a bit dangerous to show the Registration command. User then may run the command by mistake on different cluster which would probably broke the current imported cluster.

@gaktive @jordojordo circling back to this issue to verify this is on track for v2.6.7? Thanks!

@markusewalker The pr (#6226) that will resolve this is waiting on a re-review, will keep you posted on the progress.

Thought about this last night, and i had it the other way around. I'd brought up a new rancher and imported an existing cluster that was connected to a previous rancher. The cluster had references to system/default projects from the old rancher and thus namespaces weren't grouped correctly in the project/namespace list.

Is this still the case with recent versions of Rancher?

@tuupola The action in that specific quote is an unsupported process. I think there is a flow to clean the cluster first to then re-import it, though haven't tried it in a while https://ranchermanager.docs.rancher.com/faq/rancher-is-no-longer-needed#what-if-i-dont-want-rancher-anymore

The solution is create a NameSpace cattle-fleet-system if you don´t have the resource in your Cluster


Add polars and tidypolars support for pipedag

Checklist

[x] Added a CHANGELOG.rst entry

Merging without review to release 0.2.4


Align Conference Names in data/ccfFullUrl.js Entries with Semantic Scholar

Some conference names listed in the cl-paper-venue field on Semantic Scholar may slightly differ from those currently in the data/ccfFullUrl.js. I have duplicated these entries using the names as they appear on Semantic Scholar. There may be additional conferences with similar discrepancies

谢谢 @EulerianMoe 的指正！
我在想，如果跟着 SemanticScholar 的会议显示而改变期刊/会议的名称可能不是最好的解决办法，如果能有 URL 等更稳定的标识是不是更好？
我正在考虑 #86 中的方法。
谢谢 @EulerianMoe ！


GCST change for PMID: 33230300 (submission id:60c366fa53729000012f79f7)

The following GCST should be changed:
GCST90292471 change back to GCST012378
GCST90292472 change back to GCST012377
GCST90292473 change back to GCST012376
This is an old paper (2021) where these 3 studies without sumstats were submitted by the curation app, and the rest of the studies with sumstats were submitted through the deposition app. The submission was unpublished to add more studies (without sumstats), and the GCST for these 3 studies was changed and needs to be changed back to the original ones.

@sajo-ebi It is not imported to the curation app.

can this ticket be closed @Santhi1901 ?

yes, this can be closed. It is completed.


fix struct  nested reflection

With pull requests:

Open your pull request against main
Your pull request should have no more than two commits, if not you should squash them.
You should pass all tests by go test -v ./... at the project root path in local.
It should pass all tests in the available continuous integration systems such as GitHub Actions.
You should add/modify tests to cover your proposed code changes.
If your pull request contains a new feature, please document it on the README.

#38 这个问题只解决了一层嵌套
现在修改代码，通过递归方式，解决多层嵌套的问题

With pull requests:

Open your pull request against main
Your pull request should have no more than two commits, if not you should squash them.
You should pass all tests by go test -v ./... at the project root path in local.
It should pass all tests in the available continuous integration systems such as GitHub Actions.
You should add/modify tests to cover your proposed code changes.
If your pull request contains a new feature, please document it on the README.

#38 这个问题只解决了一层嵌套 现在修改代码，通过递归方式，解决多层嵌套的问题

good！

@aixj1984  请在评论下面回复这句话哈

I have read the ClDocument and ! hereby sign the CLA

I have read the CLA Document and I hereby sign the CLA


CLOUDSTACK-9074: Support shared networking in NiciraNVP Plugin

JIRA TICKET:
https://issues.apache.org/jira/browse/CLOUDSTACK-9074
Design Document:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Support+shared+networking+in+NiciraNVP+Plugin

LGTM, based on a set of tests that I run on this branch (which I rebased myself first). Screenshot is from an experimental Jenkins job (that runs the same tests I did manually until now).
These test may not cover your change, all they do is show you didn't break them. Someone else needs to review the code.

Thanks @remibergsma !

@nvazquez Ai, there is a conflict now. Could you please have a look?

@remibergsma thanks Remi, I rebased to master branch and resolved a few conflicts

@miguelaferreira @wilderrodrigues Can one of you review this? Once done, I can run the integration tests again.Thanks!

@nvazquez I've just read through you code and I made some comments that I would be happy to discuss with you.
Nice to see effort being put in unit testing the PR.

@miguelaferreira thanks for reviewing! Sure, would be great to discuss them

@miguelaferreira besides fixing these issues and writing marvin test, what else would be needed to include this feature in version 4.7? Would it be possible, or could be included in later versions?

@nvazquez I have one more request for you, and (if you agree, of course) that should be the end of it on a code level. With the marvin test then this would be ready for 4.7, but be aware that feature freeze is planned for December 7, so we need to work fast.
However, if we do not make that deadline we can always include this feature in 4.8 (as you have probably seen, we are releaseing more often these days :smile:)
I have to say I've never really liked reviewing code for other people, but it has been a pleasure to do it with you :+1:.

Thanks @miguelaferreira I really appreciate that! Thanks a lot for your help!
I'll try to make it before the deadline. I'm not that into Python but I'll do my best with Marvin tests

I'm working on adding a new test case to the test file we already have, but unfortunately I don't know how to cover your change. What I do know is how marvin works, and how a test case should look like, so please do ping me (here, or by mail) so that we can setup a chat somewhere and I'll be happy to help you.

Sure, I couldn't find you mail address, mine is in my profile

@nvazquez @miguelaferreira Hi Guys, do you think you can finish this PR on Monday so we can include it in 4.7? Would be nice :-) Let me know if you need help.

Hi @remibergsma @miguelaferreira
I've been working in marvin test file to cover this new features, those are test03 y test04 in test/integration/smoke/test_nicira_controller.py
I attach my test results:
$ cat /tmp/MarvinLogs/test_nicira_controller_1Z39R8/results.txt
test_01_nicira_controller (integration.smoke.test_nicira_controller.TestNiciraContoller) ... === TestName: test_01_nicira_controller | Status : SUCCESS ===
ok
Nicira clusters will redirect clients (in this case ACS) to the master node. ... === TestName: test_02_nicira_controller_redirect | Status : SUCCESS ===
ok
Shared Networks Support ... === TestName: test_03_nicira_shared_networks_numerical_vlanid | Status : SUCCESS ===
ok
# Shared Networks Support ... === TestName: test_04_nicira_shared_networks_lrouter_uuid_vlan_id | Status : SUCCESS ===
ok

----------------------------------------------------------------------
Ran 4 tests in 1415.297s

OK

I'm finishing my own test, and will test this PR asap.

@nvazquez I've been able to verify that the existing tests did not break with your PR, however I can't seem to get an NSX configuration for running the two additional test you added.
Here's my network config:
start IP = <IP_ADDRESS>
end IP   = <IP_ADDRESS>
netmask  = <IP_ADDRESS>
gateway  = <IP_ADDRESS>

The VLAN config
VLAN            = 50
VLAN_UUID = 2eea1553-837e-4a3e-bfbb-872c4cb2a49a

The VLAN_UUID is the UUID of a LRouter I've created in NSX. That LRouter is connected to an LSwitch.
The pictures bellow show the LRouter and LSwitch.

If you could help me fix my config, I'll test your PR today.

Since you are testing L3 connectivity existing switch patch to router shouldn't overlap an ip range used by the new subnet. Cidr #1 should work fine . You might also try disconnect existing switch from router to see if test passes. For test #4 we tested we lrouter patched over to l3 gateway without existing switch . For test# 3 you need to have l2 gateway to match the one specified for nvp device. The issue we observed was if any of the test fail for any reason the cleanup on nsx side doesn't work so a manual cleanup might require to remove existing router port left over from previous tests that has overlapping cidr

@serg38 I will use CIDR 1 and disconnect the switch from the router, to se if that works. I haven't' seen any think left behind after testing. That is, the clean up seems to be working fine for me.

Guys, I cannot build a cloud from this branch any more. The build itself works, but the database deployment gives an SQL error: Can't DROP 'logicalrouter_uuid'; check that column/key exists
Details:
[INFO] --- exec-maven-plugin:1.2.1:java (create-schema) @ cloud-developer ---
log4j:WARN No appenders could be found for logger (org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
========> WARNING: Provided file does not exist: /data/git/cs1/cloudstack/developer/../utils/conf/db.properties.override
========> WARNING: Provided file does not exist: /data/git/cs1/cloudstack/developer/developer-prefill.sql.override
========> Initializing database=cloud with host=localhost port=3306 username=cloud password=cloud
============> Running query: drop database if exists `cloud`
============> Running query: create database `cloud`
============> Running query: GRANT ALL ON cloud.* to 'cloud'@`localhost` identified by 'cloud'
============> Running query: GRANT ALL ON cloud.* to 'cloud'@`%` identified by 'cloud'
========> Initializing database=cloud_usage with host=localhost port=3306 username=cloud password=cloud
============> Running query: drop database if exists `cloud_usage`
============> Running query: create database `cloud_usage`
============> Running query: GRANT ALL ON cloud_usage.* to 'cloud'@`localhost` identified by 'cloud'
============> Running query: GRANT ALL ON cloud_usage.* to 'cloud'@`%` identified by 'cloud'
========> Processing SQL file at /data/git/cs1/cloudstack/developer/target/db/create-schema.sql
========> Processing SQL file at /data/git/cs1/cloudstack/developer/target/db/create-schema-premium.sql
========> Processing SQL file at /data/git/cs1/cloudstack/developer/target/db/templates.sql
========> Processing SQL file at /data/git/cs1/cloudstack/developer/developer-prefill.sql
========> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[WARNING]
java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
        at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script: /data/git/cs1/cloudstack/developer/target/db/db/schema-410to420-cleanup.sql
        at com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:290)
        at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:425)
        at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:474)
        at com.cloud.upgrade.DatabaseCreator.main(DatabaseCreator.java:217)
        ... 6 more
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Can't DROP 'logicalrouter_uuid'; check that column/key exists
        at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:185)
        at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
        at com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:281)
        ... 9 more
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 19.639s (Wall Clock)
[INFO] Finished at: Sun Dec 06 09:07:53 GMT 2015
[INFO] Final Memory: 43M/259M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:java (create-schema) on project cloud-developer: An exception occured while executing the Java class. null: InvocationTargetException: Unable to execute upgrade script: /data/git/cs1/cloudstack/developer/target/db/db/schema-410to420-cleanup.sql: Can't DROP 'logicalrouter_uuid'; check that column/key exists -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Not sure if it is related. Tried cleaning everything (VMs, git repo, storage) but same result.

This index comes from schema-40to410.sql:
CREATE TABLE cloud.nicira_nvp_router_map (
id bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id',
logicalrouter_uuid varchar(255) NOT NULL UNIQUE COMMENT 'nicira uuid of logical router',
network_id bigint unsigned NOT NULL UNIQUE COMMENT 'cloudstack id of the network',
PRIMARY KEY (id),
CONSTRAINT fk_nicira_nvp_router_map__network_id FOREIGN KEY (network_id) REFERENCES networks(id) ON DELETE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
There might be variation how UNIQUE attribute is enforced in different versions of MySQL.
In 5.5 it generate unique index  logicalrouter_uuid
To take it out the correct statement is
ALTER TABLE cloud.nicira_nvp_router_map
DROP INDEX logicalrouter_uuid ;
Can you check if schema-40to410.sql got applied in your environment? What version of MySQL do you use?
The drop index logicalrouter_uuid should come from schema-470to471.sql (or later upgrade script)but not from schema-410to420-cleanup.sql.
From:  Remi Bergsma<EMAIL_ADDRESS>Reply-To:  apache/cloudstack<EMAIL_ADDRESS>Date:  Sunday, December 6, 2015 at 11:59 AM
To:  apache/cloudstack<EMAIL_ADDRESS>Cc:  Sergey Levitskiy<EMAIL_ADDRESS>Subject:  Re: [cloudstack] CLOUDSTACK-9074: Support shared networking in NiciraNVP Plugin (#1094)
Guys, I cannot build a cloud from this branch any more. The build itself works, but the database deployment gives an SQL error: Can't DROP 'logicalrouter_uuid'; check that column/key exists
Details:
[INFO] --- exec-maven-plugin:1.2.1:java (create-schema) @ cloud-developer ---
log4j:WARN No appenders could be found for logger (org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
========> WARNING: Provided file does not exist: /data/git/cs1/cloudstack/developer/../utils/conf/db.properties.override
========> WARNING: Provided file does not exist: /data/git/cs1/cloudstack/developer/developer-prefill.sql.override
========> Initializing database=cloud with host=localhost port=3306 username=cloud password=cloud
============> Running query: drop database if exists cloud
============> Running query: create database cloud
============> Running query: GRANT ALL ON cloud.* to 'cloud'@localhost identified by 'cloud'
============> Running query: GRANT ALL ON cloud.* to 'cloud'@% identified by 'cloud'
========> Initializing database=cloud_usage with host=localhost port=3306 username=cloud password=cloud
============> Running query: drop database if exists cloud_usage
============> Running query: create database cloud_usage
============> Running query: GRANT ALL ON cloud_usage.* to 'cloud'@localhost identified by 'cloud'
============> Running query: GRANT ALL ON cloud_usage.* to 'cloud'@% identified by 'cloud'
========> Processing SQL file at /data/git/cs1/cloudstack/developer/target/db/create-schema.sql
========> Processing SQL file at /data/git/cs1/cloudstack/developer/target/db/create-schema-premium.sql
========> Processing SQL file at /data/git/cs1/cloudstack/developer/target/db/templates.sql
========> Processing SQL file at /data/git/cs1/cloudstack/developer/developer-prefill.sql
========> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[WARNING]
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script: /data/git/cs1/cloudstack/developer/target/db/db/schema-410to420-cleanup.sql
at com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:290)
at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:425)
at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:474)
at com.cloud.upgrade.DatabaseCreator.main(DatabaseCreator.java:217)
... 6 more
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Can't DROP 'logicalrouter_uuid'; check that column/key exists
at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:185)
at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
at com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:281)
... 9 more
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 19.639s (Wall Clock)
[INFO] Finished at: Sun Dec 06 09:07:53 GMT 2015
[INFO] Final Memory: 43M/259M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:java (create-schema) on project cloud-developer: An exception occured while executing the Java class. null: InvocationTargetException: Unable to execute upgrade script: /data/git/cs1/cloudstack/developer/target/db/db/schema-410to420-cleanup.sql: Can't DROP 'logicalrouter_uuid'; check that column/key exists -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Not sure if it is related. Tried cleaning everything (VMs, git repo, storage) but same result.
—
Reply to this email directly or view it on GitHub.

@remibergsma my mistake, I meant to modify schema-460to470.sql and schema-461to470.sql but not setup/db/db/schema-410to420-cleanup.sql as I did.
I'll push some other changes and also fix this.

@nvazquez OK, check! No problem. Just let me know when you're ready and I'll run some more tests.

ping @remibergsma would be great to test this new functionalities

@miguelaferreira configuration needed is very complicated, I could not be able to include it on test/integration/plugins/test_nicira_controller.py, tests added assume that configuration is ok.
I attach 2 documents that could help you with transport zone and L2 Gateway configuration:
NSX-MH-DesignGuidev4.2_Final.pdf
NSX-User-Guide-4.2.2.pdf
Please let me know if you need help with this

@nvazquez I suggested to add the config to the test itself, but I gave it some more thought and I agree with you that the test should just assume the config is in place.
Thanks for the documents, but it is still a lot to digest. What about step-wise instructions on what to create and in which order?

Assuming everything else is ready e.g. service controllers, transport zone, management server, STT tunnels in-between then to create L2 gateway (page 89 of the User guide):

Create new gateway transport node
1.1. Download and install either OVA or ISO for your hypervisor (available on Vmware site). You need at least 2 separate vSwitches. If tunneling traffic follows a different path, then 3 interface might be needed for the appliance
1.2 Login with admin/admin
1.3 Configure
set hostname
add network dns-server
add network ntp-server 0.pool.ntp.org
set network interface breth1 ip config static     .it could be breth0 in some cases and in some cases more than one bridge
add switch manager
1.4. Obtain gateway certificate
show switch certificate
1.5 Add gateway node to NSX
Transport Node->Add->Gateway->Display Name->Admin Status Enabled->Security Credentials - Certificate. Paste from section 1.4->Connection->Add->STT->IP of the bridge used for tunneling traffic
1.6. Create L2 Gateway Service and publish it on created Gateway transport node

Thanks for the instructions @serg38
I will attempt to reproduce this early this week.

I've tested this PR with the additional commits that I've requested to be merged here.
My environment:

Management Server
2 KVM hypervisors
3 NSX controllers
1 NSX Service Node
2 NSX Gateways
1 NSX Manager

NSX setup:

1 transport zone (with service node, hypervisors and gateways configured in it)
1 L2 Gateway service (connected to a NSX Gateway VM)
1 L3 Gateway service (connected to a NSX Gateway VM)
1 LRouter connected to the L# Gateway service

Same marvin configuration used for deploying DC and running tests.
Tests:
nosetests --with-marvin --marvin-config=/data/shared/marvin/mct-zone1-kvm1-kvm2-NVP-2.cfg -s -a tags=advanced,required_hardware=true test/integration/plugins/test_nicira_controller.py
(...)
test_01_nicira_controller (test_nicira_controller.TestNiciraContoller) ... === TestName: test_01_nicira_controller | Status : SUCCESS ===
ok
Nicira clusters will redirect clients (in this case ACS) to the master node. ... === TestName: test_02_nicira_controller_redirect | Status : SUCCESS ===
ok
test_03_nicira_tunnel_guest_network (test_nicira_controller.TestNiciraContoller) ... === TestName: test_03_nicira_tunnel_guest_network | Status : SUCCESS ===
ok
Shared Networks Support ... === TestName: test_04_nicira_shared_networks_numerical_vlanid | Status : SUCCESS ===
ok
Shared Networks Support ... === TestName: test_05_nicira_shared_networks_lrouter_uuid_vlan_id | Status : SUCCESS ===
ok

----------------------------------------------------------------------
Ran 5 tests in 1961.460s

OK

@nvazquez if you can reproduce the same test results in your environment, then I think we have tested this PR thoroughly.

@DaanHoogland I can't figure out why the rats build is failing. Can you please help us?

@miguelaferreira the report says api/src/com/cloud/network/guru/NetworkGuruAdditionalFunctions.java doesn't contain a known license

Nice work guys!
@nvazquez This will be merged to master, which is now at 4.8.0-SNAPSHOT. Can you please rebase with master, and move your SQL change to schema-471to480.sql (https://github.com/apache/cloudstack/blob/master/setup/db/db/schema-471to480.sql).
@miguelaferreira Can you conclude your review with a LGTY?

LGTM!

@remibergsma Thanks a lot Remi! I rebased with master, moved sql to 4.8.0 schema and pushed it again.
@miguelaferreira Thanks a lot for your help and your effort testing this features!
Merry Chistmas guys

@DaanHoogland Jenkins failed due to this (missing artifact). Any hint on the cause?
Archiving artifacts
ERROR: No artifacts found that match the file pattern "target/rat.txt". Configuration error?
ERROR: ?target/rat.txt? doesn?t match anything: ?target? exists but not ?target/rat.txt?
Build step 'Archive the artifacts' changed build result to FAILURE
Skipping Cobertura coverage report as build was not UNSTABLE or better ...
Publishing Clover coverage report...
No Clover report will be published due to a Build Failure
Putting comment on the pull request
Finished: FAILURE

@remibergsma (and others) I will continue to look at this. It has kind of a long and irregular round trip sorry for the inconvenience.

btw the reason is that rat.txt was deleted if it succeeded by the next build step (mvn clean)

@nvazquez If you open/close this PR it should build again at builds.a.o. The job should now be fully functional.

@DaanHoogland Done

hm, that didn't work, strange it worked for me. another option would be to force push. If you feel the extra run is needed you can try that. This looks like a well tested and reviewed PR however. I doubt if the extra run will give us any information we don't have yet.

@DaanHoogland I see that all checks have passed, what is it failing?

@nvazquez the job has not rerun, but as far ad I can see it is alright.

@DaanHoogland @remibergsma (cc @nvazquez) can we merge this PR before master drifts away again?

@miguelaferreira I see no issues so LGTM (no integration tests done!)

Hi @nvazquez, when we run this in production weird stuff started to happen. This happened with VPCs that have a private gateway attached. It seemed to get confused and plugged nics in the wrong lswitches. We had to revert this change and it worked fine again. Before digging deeper, did you ever succeed creating a private gateway with this code base?

Hi @remibergsma no, I didn't try VPC. I meant to adjust shared network handling, technically any isolated stuff including VPC would be affected. But I can help you examining this code, if you need any help please let me know


Updating record with multiple new values

Is there way of updating record with multiple values?
Example:
class User
  scheme do
    field :name, String
    field :age, Int32
  end
end

params = { name: "Crecto", age: 3 }

user = Crecto::Repo.get(User, 1)
user.update(params) # --- how to do it?
Crecto::Repo.update(user)

Currently there is no shortcut method for updating from json, unless there is some helper thats a part of JSON.mapping that i'm not aware of

JSON.mapping is fairly simple, it only creates getters, setters, instance variables and initializer.
I think JSON.mapping should also create two methods attributes : Hash, which is same as to_query_hash, and attributes=(attrs : Hash) that works like initializer.

Is this still something that's being considered? If so, I'd like to be able to pass a params object or pass naked attributes:
u = User.new
params = { name: "tester", age: 21 }
u.update(params)
u.update(name: "tester", age: 21)

Crystal allows splatting NamedTuples, so if the bare attributes version is implemented, I think the explicit params object could be pretty simple:
def update(params : NamedTuple)
  update(**params)
end

I have another branch where I have added a couple of small features to support another related project where I have implemented an update_from_hash method.
In this case though its expecting a hash of Hash(String, String) type (which comes from HTTP::Params#to_s).  I might be able to extend this to allow for a more generic hash argument, and probably an overloaded method for NamedTuple

Nice! That certainly seems like the more common use case. Any idea of when that might get merged?

Later tonight probably.  I have a couple of tweaks on my computer at home that I haven't pushed yet, but I think its ready to be merged.

closed by #91


fix url

What:
Fixed the url of browsertime.

Why:
Wrong url.

How:

Checklist:

[ ] Documentation
[ ] Tests
[ ] Ready to be merged

Thanks @makotot !


[All frameworks] Execute correct detection of disconnected or connected mode

Description / Motivation

Use JSS_MODE env variable to check are we working in disconnected/connected mode
Move JSS_MODE constants from sitecore-jss-nextjs to sitecore-jss and add for each framework package.
Angular enabled proxy for each mode, now I enabled it only for disconnected.
Get rid of bootstrap:connected

Testing Details

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation update (non-breaking change; modified files are limited to the /docs directory)

Also, the change in constants is technically a breaking change for the Next.js sample. We should probably list this in the release notes.


Is project still alive?

Is project still alive? There is no any commit after September 21

apparently edcarrol is on some travels around the world - the project is not dead ;)

Still alive, things have just been very busy. Aiming to be more on top of things in the coming weeks however.


0.21.0 (remove webpack 1 support)

It's time.
This will make things easy to fix #984.

I will also take some time to update babel latest to babel preset env


Break script & return exit code on failure

Fix #28
Off-topic
I'm not familiar with shell scripting, may I ask you why you don't create a function debug like say.
I've done this locally in another branch, I find it quite more readable. Any caveats ?

Thank you @emri99 for this, I've integreated the PR in forked script


[FEATURE]: Add option to set Accept: application/x-protobuf header

Describe the solution you'd like
Auckland Transport's realtime API returns JSON data by default, but does return Protobuf if the Accept header is set to application/x-protobuf. Add an option to set this header if required by the data source.
Describe alternatives you've considered
Looking at Auckland Transport's documentation, this header is the only way to get Protobuf data, and getting realtime data without it is not possible. I've tried adding a .pb extension to the URL in case this somehow worked, but just resulted in a 404.
Additional context
Static GTFS data source: https://gtfs.at.govt.nz/gtfs.zip
Realtime API data requires an API key. The URLs I've been using (with the key in the header):
https://api.at.govt.nz/realtime/legacy/tripupdates
https://api.at.govt.nz/realtime/legacy/vehiclelocations
https://api.at.govt.nz/realtime/legacy/servicealerts

try <IP_ADDRESS>, as I donot have local/static data I only tested with the service call and that collects the correct format

Too many things to work on and only limited testing ... typo fixed  in <IP_ADDRESS>

Thanks @vingerha, no more errors and debug data suggests the API can now be contacted. 😄
I'm just getting a dash in the realtime attributes, but it's also possible that I've misconfigured something else, so will keep digging on this.

Do try the service call so you can see the readable data too
On 8 Apr 2024, at 09:33, Alex Burgess @.***> wrote:

Thanks @vingerhahttps://github.com/vingerha, no more errors and debug data suggests the API can now be contacted. 😄
I'm just getting a dash in the realtime attributes, but it's also possible that I've misconfigured something else, so will keep digging on this.
—
Reply to this email directly, view it on GitHubhttps://github.com/vingerha/gtfs2/issues/49#issuecomment-2042053634, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKREVY35DJDYNCQ5KNQA2GLY4JB3NAVCNFSM6AAAAABF27B3W6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBSGA2TGNRTGQ.
You are receiving this because you were mentioned.Message ID: @.***>


[GPU] Layering Materials not fully working.

So this is how image looks when u just render it with simple single node material..

This is where bug starts as u can see we no longer see the metal material it is just the 2nd material. this is rendered on GPU

And this is the correct render done on CPU

so this is file that u can render in 30 sec and it shows the issiue.. it autimaticly renders 1 render on CPU and 1 on GPU and shows both next to each other.
bug.zip

This is a duplicate of #307. So it is known limitation.
Both Mix and GlossyCoatting (all materials that can reference other materials) supports only directly plugged bump mapping, they will ignore the bump mapping of all sub-nodes.
As simple workaround, you can just plug the bump map directly in GlossyCoatting node, instead of the metal sub-node, and it will work on GPU too:

@Theverat , until when #307 is not fixed, we could add a warning in BlendLuxCore if someone use bump mapping on a glossycoatting/mix sub-node.

This is a duplicate of #307.

This is a duplicate of #307. So it is known limitation.
Both Mix and GlossyCoatting (all materials that can reference other materials) supports only directly plugged bump mapping, they will ignore the bump mapping of all sub-nodes.
As simple workaround, you can just plug the bump map directly in GlossyCoatting node, instead of the metal sub-node, and it will work on GPU too:

@Theverat , until when #307 is not fixed, we could add a warning in BlendLuxCore if someone use bump mapping on a glossycoatting/mix sub-node.

no this is not the workaround!!! as u can see the both shaders have bump map.. the base.. and the clearcoat... have bump in such situation! with is tottaly not the effect u want..

Check the latest news on issue #307.


[Flowershow] Documentation updates

User story
As a user, I want to be able to find comprehensive and up-to-date documentation of a given feature.
⚠ This is especially needed after the switch from contentlayer to our @flowershow/markdowndb package.
Acceptance

[ ] all docs pages are up-to-date
[ ] every feature has a doc page
[ ] every doc page is listed on the docs/index.md page

Tasks

[ ] docs/config page has a full list of all available config options with a short description (if not super clear)
[ ] blog tutorial and doc page are up-to-date
[ ] custom layouts tutorial and doc page are up-to-date

@olayway i would definitely consider markdowndb is Flowershow v2-alpha or something. We could even have 2 sites e.g. v1.flowershow.app that runs v1 branch (we could branch v1) and a v2 which is main ... (cf how tailwind etc does it). However, this could be overkill given where we are in terms of usage etc atm.


Missing Textures from glTF

VulkanglTFModel is not presenting specularGlossiness and diffuse textures.

Can you elaborate? Is this something that's missing or is this a bug?

It's missing. void vkglTF::Model::loadMaterials(tinygltf::Model &gltfModel) is not populating material.specularGlossinessTexture and material.diffuseTexture fields.

yeah, that sample isn't supposed to be a full fledged glTF renderer. If you're looking for a more complete glTF sample, please take a look at https://github.com/SaschaWillems/Vulkan-glTF-PBR/.


fix(ui): crash when trying to save remote node updates

Description:
Fix crash when trying to update remote wallet settings in the launchpad

How Has This Been Tested?
Manually

Types of changes:
Bugfix

Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage decreased (-0.007%) to 22.882% when pulling ac4936a341918cf75986117b52d7c3338d8908e8 on korhaliv:fix/wallet-save into 4214cd2eab96644a74ba8d3c00c58bc72607065c on LN-Zap:next.


urlscan: 1.0.3 -> 1.0.6

Diff: https://github.com/firecat53/urlscan/compare/refs/tags/1.0.3...1.0.6
Changelog: https://github.com/firecat53/urlscan/releases/tag/1.0.6

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 362202

x86_64-linux

:white_check_mark: 2 packages built:

urlscan
urlscan.dist


bucket.upload doesn't retry failed resumable requests

Environment details

OS: any
Node.js version: any
npm version: any
@google-cloud/storage version: 4.6.0

Steps to reproduce

Use bucket.upload with a file size over the RESUMABLE_THRESHOLD  to upload
If /home/.config is not writable the upload fails

Do the same steps but with file.createWriteStream and a file stream and the upload works.
From looking at the code, bucket.upload sets options.resumable and that means the retry check in file.createWriteStream doesn't work.
Note I discovered this issue by trying a resumable upload on Cloud Run which doesn't allow writing to /home/.config which doesn't seem right!

Looking at this again - a simple fix would be only to set options.resumable to false for bucket.upload if the file is smaller than the threshold. Then if the file is over the threshold, file.createWriteStream will automatically default to trying a resumable upload first.
@bcoe is this a acceptable solution - happy to do a PR if it is?


Make it possible to decode a url containing an encodeURIComponent encode...

...d % symbol
We've been having problems with params that have been encoded as URI parts with encodeURIComponent. For example:
'http://foo.com/bar/'+encodeURIComponent('foo%/bar')
Somewhere in the router decodeURI is getting called on the URI, then it's throwing a URIError in  _extractParameters when decodeURIComponent is getting called on an already decoded % character.
This patch fixes our app by falling back on regex substitutions of URI separators not already decoded by decodeURI when a URIError is thrown. It is still necessary to perform replacements of characters decodeURI does not catch.
Confusingly, the unit test doesn't seem to call decodeURI on the url with the checkURL call, so I've left decodeURIComponent in place rather than avoiding it completely. It would break other tests to remove it and I'm not confident I know all the code paths that call _extractParameters.
Signed-off-by: Pete Setchell<EMAIL_ADDRESS>

Have you seen this?
https://github.com/jashkenas/backbone/pull/3434
Does it address your problem?


Fingerprint in bulk

Restructure manager so that it has three separate queues. The OG queue, a fingerprinting queue, and an uploading queue.
All three queues run independently. The OG queue parses the replays on background threads, and puts the results on the fingerprinting queue.
The fingerprinting queue checks the fingerprinting API in bulk, marks duplicates as such, and puts non-duplicates on the upload queue.
The upload queue uploads the file.
Tested to a limited amount, as I don't have an environment set up for a local API, and a limited amount of replays available.
Intended to fix https://github.com/hotsapi/Hotsapi.Uploader/issues/17

This looks really good and the review is definitely knowledgable and way over my head :)
Do either of you have a means of testing? It would be great to be able to incorporate some tests into the repo itself, or at least docs on how to set that up. I do almost no desktop dev so sorry fi that's a silly question.

Yes I forgot to say I just reviewed the code here, I haven't actually tested it, so someone else probably should test it locally

I meant more like is there way to make a docker instance that can build this and then try uploading some sample replay files, something that we could pipeline.

All pull requests are supposed to be built by our CI, but it is broken after project transfer to a separate org. Testing could be done via uploading to a local hotsapi instance. I'll try to look into it more closely soon.

@MGatner Yeah you definitely can set up test cases for desktop C# software
I'm a lazy, selfish developer, so I don't like to write test cases :) I like it when other people write them though
In this case, if my review comments actually are issues, I don't think they would have been caught in tests anyway, which is part of why I'm lazy

Integration with the data services is pretty tight, which makes this hard to unit test. To make it testable, the backend needs to be factored out and injected: uploader has to be abstracted to an interface, passed as a mock service, and become a constructor parameter of manager.
It's a lot of work, and arguably worth it (and arguably not), but maybe not in the scope of this PR.

re:testibility, I opened https://github.com/hotsapi/Hotsapi.Uploader/issues/57 to track that.

This is looking great.

@MGatner I think it's ready!

I didn't have a local API client, so my own testing has been rather limited - up until my uploads were done, after that I had dupes. A little more trying it out would be good.

rebased on top of #62

Looking into the validation failure

Made sure that uploads are uploaded in order, by holding the concurrent uploads that younger, to make sure the older ones complete first.

rebased on master, dropping the commits shared with #62

Hmmm why is it closed?

I started it on a big batch and there were two issues.

Max concurrent uploads weren't respected
UI freezes during upload

Fixing the concurrent uploads issue also fixed the UI freezes (so I suspect that was a resource contention issue), so I'm re-opening.

We can just mark it as WIP in title while working on it

It should be good now though


v1.6 backports 2019-12-12

#9643 -- Add missing words to spelling_wordlist (@ungureanuvladvictor)
#9743 -- fqdn: Support setting tofqdns-min-ttl to 0 (@raybejjani)

Once this PR is merged, you can update the PR labels via:
$ for pr in 9643 9743; do contrib/backporting/set-labels.py $pr done 1.6; done

This change is

never-tell-me-the-odds

@jrajahalme I finally managed to understand what's going on. The version of viper we have on master and 1.6 happen to have a bug were IsSet always returns true. This seems to cause IPs to not show up in the checks for the failing tests. Given that the original motivation for backporting this was to supports the --tofqdns-min-ttl 0 usecase, but it turned out to not be in-use, I'd say let's skip the backport for now. It isn't critical for any known user (and otherwise unlikely to occur).
See https://github.com/cilium/cilium/pull/9796 for the fix on master.

Dropped #9743

never-tell-me-the-odds


Fix for materials / textures with too long names not importing.

Some textures have names longer than 63 characters (i.e. fx_channelholdduckplushietalkquestionlargeracesnotwai_channel_4690956.png). Blender is unable to properly deal with these on its own, as it will either:

Cut them at 63 characters (i.e. when trying to add something to a collection like bpy.data.images; fx_channelholdduckplushietalkquestionlargeracesnotwai_channel_4)
Cut the last 4 characters and replace them with a counter (i.e. when creating a new material; fx_channelholdduckplushietalkquestionlargeracesnotwai_chann.001)

This PR solves the parsing bit by offloading the materials array to csv files that are loaded when needed and the creation of materials bit by truncating the name.
Feedback & other ways to solve this are very welcome!

This has been resolved by hashing oversized material names


added beta7 coreclr sample

added beta7 coreclr sample :smile:
ties it into the aspnet docker CI build https://github.com/aspnet/aspnet-docker/pull/84

Hi @jchannon, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

is the only diff the dockerfile?

yup
On 9 September 2015 at 09:10, Ahmet Alp Balkan<EMAIL_ADDRESS>wrote:

is the only diff the dockerfile?
—
Reply to this email directly or view it on GitHub
https://github.com/aspnet/Home/pull/891#issuecomment-138819234.

Then you can probably symlink all the other files. I'm no big fan of duplicating things just because we need this folder structure in docker image CI.
Actually we may even rewrite the CI scripts over there to replace the image name in the dockerfile here.

Yup makes sense. Want me to symlink to beta 7 for now?

I'll let repo owners decide. Maintaining symlinks on Windows might be a pain :-)

@jchannon, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;

Closing because this is no longer needed. Thanks!


QFileSystemViewer has error when a selected wad is removed

Need to look into best usage of filesystemviewer
inotify_add_watch("/home/karlpet/.wadlauncher/wads/f-f01-s2") failed: "No such file or directory"

wontfix, not our problem.


I want to get the candidate column information of Fcitx5

I want to set the transparency of the candidate bar of Fcitx5 separately, but I can't get its title and other information. What should I do to get its title and other information?
I am not good at English,so I translated it

try these
windowrule=opacity 0.6 override 0.6 override,^(fcitx)$

this will match the candidates for xwayland applications

for wayland applications, classes would get disappeared, and I'm not sure whether if it's possible to match against initialClass

try these
windowrule=opacity 0.6 override 0.6 override,^(fcitx)$

this will match the candidates for xwayland applications

Thank you for your help! Have a nice day!


MockClient for Demo or Frontend Contributors

For the demo site or someone who wants to contribute to the frontend part, it is not necessary to set up different kinds of real cloud integrations. It is better to have a mock client that returns some fake cost data in this case.

Both mock clients for cost data and business metrics have been implemented (#56 and #58) so I am closing this issue.


mirador.sh install

GitHub Issue: (https://github.com/Islandora-CLAW/CLAW/issues/645)
What does this Pull Request do?
Downloads and installs mirador drupal module, and library dependencies
What's new?
would give users an option to install mirador with a vagrant provision

Added scripts/mirador.sh
*you must add a line; to your Vagrantfile to enable this script

Could this change impact execution of existing code?
Gads I hope not...

How should this be tested?

To Test that the Pull Request does what is intended.
add:
config.vm.provision :shell, :path => "./scripts/mirador.sh", :args => home_dir
to the pre-penultimate (3rd to last) line of Vagrantfile

Additional Notes:
You must enable the module yourself. bc I couldn't figure out permissions.. 👎
Interested parties
@Islandora-CLAW/committers @whikloj

thanks for all the feedback. and for putting up with my noob. I'll get on these changes. thanks!

@flummingbird Not to dogpile more feedback on ya, but commenting in those lines at the top of your bash script should make the $DRUSH_CMD variable available for you to use.  The . "$HOME_DIR"/islandora/configs/variables bit loads those variables so they're available for use. We have to make them available that way because each script in the Vagrantfile is sandboxed and is totally unaware of environment variables.

@flummingbird you don't need to close this. I'd prefer if you worked through it, much of this is our particular vagrant setup that you are (perhaps) not as familiar with as we are. But there are tricks in there that could help you...and by extension help us.

Especially as I just got Mirador to work. However it doesn't seem to work as a tiling service rather it is serving a single (or sequence) of static images.
But its a start.


Better handling of adaptive card attachments with text

Issue
As a bot developer, I'm trying to send an adaptive card with a text message.
Currently, sending an adaptive card with text runs into the following issues:

Issue 1: Teams sends the text and adaptive card attachment as two separate activities. If the adaptive card has a submit button, and the desire is to update the existing card when the user submits. The ReplyToId only contains the card, and not the text. The text message cannot be updated or deleted without having this tracked separately as conversation state.
Issue 2: Chat feeds will only present the last message sent, which will just say "Bot send a card"

Issue 3: If you use TeamsNotifyUser to enable notifications, the Notifications feed present both the text and card separately, which results in noise:

Expectation
The text message should help describe the card for the notification feed, chat feed. The most ideal is if the message is presented in the same activity as the card. The notification and chat feed should display the text instead of "Send a card", or the "card" icon.
Sample to reproduce
Message json:
{
  "type": "message",
  "attachmentLayout": "list",
  "text": "Hello World Message",
  "inputHint": "acceptingInput",
  "attachments": [
    {
      "contentType": "application/vnd.microsoft.card.adaptive",
      "content": {
        "type": "AdaptiveCard",
        "version": "1.2",
        "body": [
          {
            "type": "TextBlock",
            "text": "Hello, World!"
          }
        ]
      }
    }
  ],
  "entities": []
}

@weikanglim , This is current behavior and we don't have any plans as of now regarding the change in adaptive card.


Add ObservedGeneration to status (conditions)

Is your feature request related to a problem?
Identifying whether a controller is working correctly is currently not easy (neither 100% accurate) when looking at the ResourceSynced status field:

Patterns: For people coming with some Kubernetes operational knowledge, not having ObservedGeneration could impact troubleshooting and documented procedures best practices gained from using other controllers/operators.
Failures: If the controller is not running/keeps crashing after a successful initial ResourceSynced the operator cannot easily see whether the resource actually has synced based on the set Generation in the metadata - because ResourceSynced might be stale.

In https://github.com/aws-controllers-k8s/community/issues/1133#issuecomment-1020218494 reasons were given why ObservedGeneration might have issues, e.g. when dealing with multiple controllers. IMHO this is not accurate and against the Kubernetes convention of using ObservedGeneration in Kubernetes resources:

Guidelines writing Kubernetes controllers: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-api-machinery/controllers.md
Standardize Conditions: https://github.com/kubernetes/enhancements/blob/0ffd37f8925d8a9af7ce7a7409007db8285a30b1/keps/sig-api-machinery/1623-standardize-conditions/README.md
"The recommendation to have observedGeneration in conditions only began a year or two ago, people have to update their CRDs and controllers. We probably haven't done enough to publicize this. (Daniel Smith SIG API Machinery)": https://kubernetes.slack.com/archives/C0EG7JC6T/p1666625916236369?thread_ts=1666371350.588619&cid=C0EG7JC6T

Also, currently I don't see any multi-writer implementation in ACK or related projects using ACK (to my knowledge). But even if that's a scenario (very likely in the future), Server-Side Apply (SSA) and related techniques in the API server are meant to address multi-writer scenarios, also for updating individual conditions:

Unfortunately we don't have a standard way for multiple controllers to work together on status other than conditions (Daniel Smith SIG API Machinery)

Describe the solution you'd like
Follow Kubernetes standardized conditions convention.
Describe alternatives you've considered
Keep as is.

@jaypipes @A-Hilaly putting this out for discussion

Guidelines writing Kubernetes controllers: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-api-machinery/controllers.md
@embano1 note that the above doc does not refer to ObservedGeneration in a Condition but rather in the Status struct iself.

I still have concerns about an ObservedGeneration field in our Condition structs, for the same reasons I gave in the comment on #1133. Adding it would mean we could never move to a multi-writer architecture and could only ever use a single-writer architecture (i.e. the leader-elected architecture that upstream Kubernetes controllers all have).
Also, all Conditions on all ACK resources are entirely cleared for every resource at the beginning of reconciliation:
https://github.com/aws-controllers-k8s/runtime/blob/da127a61ebce56b3bfcff331ba161bd5215484a9/pkg/runtime/reconciler.go#L227
The reason for this is because a Condition represents a state transition during that particular reconcile. So, all Conditions are guaranteed to always be the freshest representation of a resource's latest state transition. I guess I could see some use in debugging crashing controllers by adding an ObservedGeneration to a Condition, but frankly, that generation is output in all log lines in the controller's logs anyway, along with a timestamp, so it's relatively straightforward to diagnose state transition issues simply by looking at the log.
That said, if this is something a bunch of folks want (@A-Hilaly @RedbackThomson @jljaco) then I will back off and relent :) It should not be difficult to add support for this into our standard Condition handling.

@embano1 note that the above doc does not refer to ObservedGeneration in a Condition but rather in the Status struct iself.

Reason I mentioned this doc (in addition to the more specific links in the original post) was to point out that setting ObservedGeneration is a recommended pattern (and has evolved over time, see other links).

Adding it would mean we could never move to a multi-writer architecture and could only ever use a single-writer architecture (i.e. the leader-elected architecture that upstream Kubernetes controllers all have).

I don't think so. See what Daniel Smith responded (quoting from above):

Unfortunately we don't have a standard way for multiple controllers to work together on status other than conditions (Daniel Smith SIG API Machinery)

IMHO setting status conditions does not prevent a controller authors from multi-writer scenarios. Leader-election is a special case and not truly multi-writer due to the fencing mechanisms at play (only one writer at all times) unless the controller is violating leader election primitives (i.e. bug).
In fact, I'd argue that status conditions actually provide the means to have multiple controllers cooperate (in addition to the advancements with server-side apply).

Also, all Conditions on all ACK resources are entirely cleared for every resource at the beginning of reconciliation:
https://github.com/aws-controllers-k8s/runtime/blob/da127a61ebce56b3bfcff331ba161bd5215484a9/pkg/runtime/reconciler.go#L227
The reason for this is because a Condition represents a state transition during that particular reconcile. So, all Conditions are guaranteed to always be the freshest representation of a resource's latest state transition. I guess I could see some use in debugging crashing controllers by adding an ObservedGeneration to a Condition, but frankly, that generation is output in all log lines in the controller's logs anyway, along with a timestamp, so it's relatively straightforward to diagnose state transition issues simply by looking at the log.

I don't see any issue with the existing "clearing" logic: that is exactly the way status is designed for and inline with the API conventions, i.e. being stateless (though we've seen users bending the rules here).
Setting ObservedGeneration is also a "stateless" operation and does not violate this principle (otherwise all controllers would be broken).
Regarding debugging: instead of looking at the various controller logs, an operator/developer can clearly see whether the controller is actively reconciling by inspecting the Kubernetes resource, e.g. kubectl get .... Note that if central logging is configured (which is very common), this is even more beneficial by tracking object state transitions and controller logs in a central logging system (e.g. ElasticSearch or CloudWatch) and using timestamps to reason about issues.
I just checked the code as I'm happy to implement this. But it's pretty deep in the runtime and there's likely edge cases that I am not thinking about all the code paths to touch to add ObservedGeneration to all status fields for all Synced/Terminal cases (not sure if controller authors can even influence/overwrite this behavior on a case by case basis...).

Regarding debugging: instead of looking at the various controller logs, an operator/developer can clearly see whether the controller is actively reconciling by inspecting the Kubernetes resource

I would echo this point. In my case I have a different controller provisioning an ACK Bucket. It needs to first create or update the Bucket and once that is complete, do further processing. Without some way to know that syncing is complete, it is forced try and save when the last sync was and check that the bucket has a ResourceSynced transition time that is newer than that. This gets particularly painful when there are scenarios where my controller will need to reconcile loop.
I don't know of ObservedGeneration is the right solution, but some way to know that a sync is underway would be extremely useful.

Like I mentioned, if this is something we all want, I'm happy to walk a contributor through the process of adding this functionality to the ACK runtime. :)

/remove-lifecycle stale

@jaypipes

Adding it would mean we could never move to a multi-writer architecture and could only ever use a single-writer architecture (i.e. the leader-elected architecture that upstream Kubernetes controllers all have).

Are you referring to a future architecture where the whole status object would be reset and rewritten by multiple writers, or where various fields are 'owned' by various controllers? In the former scenario, if the whole status is rewritten a single observedGeneration on the status would suffice since you wouldn't be able to partially read the previous status. In the latter scenario, this is where having a different condition per controller would come into play, with each of them having their own observedGeneration field.
We're looking for this functionality as well to be able to guarantee the resource is indeed sync'd when we are looking at it from another non-ACK controller, and not to cause race conditions where we update the resource and read it again before the controller has time to observe and react to the change.

Regarding debugging: instead of looking at the various controller logs, an operator/developer can clearly see whether the controller is actively reconciling by inspecting the Kubernetes resource

I would echo this point. In my case I have a different controller provisioning an ACK Bucket. It needs to first create or update the Bucket and once that is complete, do further processing. Without some way to know that syncing is underway or complete, it is forced try and save when the last sync was and check that the bucket has a ResourceSynced transition time that is newer than that. This gets particularly painful when there are scenarios where my controller will need to reconcile loop. Or when it is not clear whether there is an actual diff on the update for the Bucket, so it doesn't know if it needs to wait.

Hi @AlistairBurrowes sorry for the late response. The way to determine if an ACK resource is completely synced is to check whether there is a Condition of type ACK.ResourceSynced with a ConditionStatus of True. What this means is that the last time the reconciler ran for that resource, the controller was able to determine that the desired state of the resource matched the latest observed state of the resource.
Whenever there is a Condition of type ACK.ResourceSynced with a ConditionStatus of False that means the last time the reconciler ran for that resource, the controller was able to determine that the desired state of the resource did NOT match the latest observed state of the resource.
If there is a Condition of type ACK.Terminal with a ConditionStatus of True on such a resource, that means the resource will never have a Condition of type ACK.ResourceSynced with a ConditionStatus of True unless the user modifies something about the resource's Spec.

I don't know if ObservedGeneration is the right solution, but some way to know that a sync is underway would be extremely useful.

Also, all Conditions on all ACK resources are entirely cleared for every resource at the beginning of reconciliation

Unless I am missing something, this does not appear to be true. If I update a Bucket there is no change until it has synced and there is a new transition time for ResourceSynced. There is no update where the conditions are cleared. (Using kubectl get bucket --watch -o yaml)

Sorry, this is referring to the ACK runtime's behaviour of deleting all Condition objects in a CR's Status at the start of each reconciliation loop. We don't actually Patch that condition-resetting change back to the Kubernetes API server but rather recalculate the CR's Conditions at the start of each reconcile loop.


XSL stylesheet for XML reports

Let's generate XSL stylesheet for all reports and make sure they all have links to it.

Job gh:yegor256/jpeek#10 assigned to @yegor256, please go ahead (policy).

Manual assignment of issues is discouraged, see par.19: -5 points just awarded to @yegor256, total is +4085.

Oops! Job gh:yegor256/jpeek#10 is already assigned to @yegor256, sorry.

Bug was reported: +15 points just awarded to @yegor256, total is +4100.

@rultor release, tag is 0.3

@rultor release, tag is 0.3

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.3

@yegor256 Done! FYI, the full log is here (took me 11min)

Job gh:yegor256/jpeek#10 is now out of scope.

Order was successfully finished: +30 points just awarded to @yegor256, total is +4305.

Oops! There is no order for job gh:yegor256/jpeek#10.

Oops! Job gh:yegor256/jpeek#10 is not in scope.


tools: cherry-pick vc image convert tools

Coverage remained the same at 81.042% when pulling 96bcabc9e83087e03509d5454113a63e2900ab6b on aravuri/vc_utils into d206d14431d001fbe76c144c2fa46e39d587ef39 on master.


Inner selection from inside a pair jumps to next pair even with cover_or_next

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md
[X] I have updated 'mini.nvim' to latest version

Module(s)
mini.ai
Description
I am experiencing a bug with the mini.ai plugin. When the cursor is inside a pair of quotes and I try to select the text in that pair (viq) , the plugin jumps to the next pair of quotes and select its content. This also happens with the other types of pairs (brackets, etc.), and sometimes with the "around" version (vaq).
The search method is correctly set to cover_or_next.
Neovim version
0.9.2
Steps to reproduce

nvim -nu minimal.lua
Open a file (Typescript here) and type const list = ["abc", "def"]
Position the cursor on "a" and run viq

Expected behavior
I expect the string abc to be selected.
Actual behavior
The string def is actually selected.

Thanks for the issue.
I can not reproduce and pretty sure everything works correctly here. Can you still reproduce with minimal config (ideally only with 'mini.ai' enabled)?
Here are the possible causes of your behavior:

When it comes to quotes, they are balanced. So in this example it would select def if cursor is on comma.
When target selection contains single character and cursor is on it, applying i textobject would trigger "consecutive application" (as target region is already already selected after v) and try to select other region.
When there are both multiline covering region and target region on same line, the latter will be selected.
Having conflicting set of mappings. What does xmap i show? It should not have iq (or other combinations with which you have problems).

Closing as I really doubt that this basic feature does not work because of 'mini.ai'. If you are indeed able to reproduce with only 'mini.ai', please let me know.

Thanks for the quick reply!
I finally found the problem: I had the v key remapped to incremental selection (with nvim-treesitter/nvim-treesitter-textobjects). When I changed this keymap, it fixed the issue.


Database.sql

sir, where i can find database file ?
i am developing attendance for my school with Codeigniter 3
i use zkteco mini ac plus for attendance machine

Kindly email me on<EMAIL_ADDRESS>Will guide you

Hope too hear and assist you soon