Doubt with residual parameters calculation

I have a doubt on how you calculate the residual Helmholtz energy, specifically the first derivative with the reduced density.
According to the GERG-2008 paper the polinomial term should be:

In your code, around line 555:
for(let k = 1; k <= kpol[i]; k++){
          ndt = x[i] * delp[doik[i][k]] * taup[i][k];
          ndtd = ndt * doik[i][k];
          ar[0][1] = ar[0][1] + ndtd;

For what I understood, taup[i][k] equals to n_{oi,k} * tau ^ t_{oi,k}. So each term of the derivative is calculated like:
delta^d_{oi,j} * n_{oi,k} * tau ^ t_{oi,k} * d_{oi,j}
When the term of the paper is:
delta^(d_{oi,j}-1) * n_{oi,k} * tau ^ t_{oi,k} * d_{oi,j}
I'm sure your code work, since I've tested a bit of it and reached good results, could you tell me what I'm reading wrongly?
(I'm trying to make my own implementation on Python and Fortran and not getting the expected results)
Thank you for your time!

It's possible that you have the same mistake i had. Let me know if i'm right.
Let me use uppercase letters for DELTA = d/dr and lowercase for the partial derivative operator = delta.
When you first look at the meaning of the output in the comments. It seems like a[0][1] is delta aij/ delta DELTA. But if you look at it again you will notice that is DELTA * delta aij/ delta DELTA. That cancel out the -1 in the exponent.
//Outputs;
// ar(0,0) - Residual Helmholtz energy (dimensionless, =a/RT)
// ar(0,1) -     delta*partial  (ar)/partial(delta)
// ar(0,2) -   delta^2*partial^2(ar)/partial(delta)^2
// ar(0,3) -   delta^3*partial^3(ar)/partial(delta)^3
// ar(1,0) -       tau*partial  (ar)/partial(tau)
// ar(1,1) - tau*delta*partial^2(ar)/partial(tau)/partial(delta)
// ar(2,0) -     tau^2*partial^2(ar)/partial(tau)^2

PS:
I'm aware of two implementation in FORTRAN
https://github.com/n-centrix/ISO20765-Part2
https://github.com/usnistgov/AGA8/tree/master/AGA8CODE/FORTRAN (From NIST - Ian Bell and Eric Lemmon)
I'm not aware of any implementation on python. Looking forward to see it.

Thanks for the quick response!
Ohh, now I understand, thanks for the clarification! Is there any reason you do it this way besides avoiding using the "-1"?

When you run CalculateDensity. This routine is inside the loop of the Newton Raphson method.
I understand that Eric tried to avoid expensive computations inside the loop.

Sadly, the original version was on VBA. Where you can't upload to memory for more than one determination. (You could use a matrix formula but is not very comfortable). So this effort got diluted.

I've tried to replace this with a binary search (more robust but less effective). But low improvements were found.


Allow application-specific information in Handler Execution Exceptions

When using AxonServer and an exception is thrown from an @CommandHandler or @QueryHandler, this exception gets translated to a generic exception in the dispatching component. While this generic exception does contain information about the root cause of the exception, it does not provide this in a format that can be used to base decisions on.
Therefore, the APIs should allow handlers to provide additional details that get transported to the client (using the message serializer). This object should be available on the CommandExecutionException, as well as the QueryExecutionException.
A Command/Query Handler can throw an exception that has the Command/Query ExecutionException in the cause-chain (or have an interceptor wrap it on its behalf) in order to provide these details.

This great but it makes the domain (Exception) dependent on Axon (via extending HandlerExecutionException).. How else could domain exceptions be handled without depending on Axon?

In @abuijze last description on the issue is stated that you could leverage a Handler/Dispatch Interceptor solution to wrap exceptions thrown from your Domain Model. Doing this, you are ensured that your domain does not have to extend the HandlerExecutionException directly. You'd then instead introduces this layer once the exception transitions out side of your domain.
I would argue it is more pragmatic to extend the exception directly, but I understand the desire to decouple the framework logic from your domain logic. For Message Intercepting specifics I suggest to read this Reference Guide page.

@smcvb That's for the reply! I went over this approach earlier but wasn't able to figure out how to register a CommandHandlerInterceptor that executes after the command has been executed and an exception is thrown... Would appreciate a sample code of how this would look like.

Also, I think the doc for 4.2 needs to be updated because the handle method of MessageHandlerInterceptor takes two parameters not three.

Ok. Figured it out

public class AxonCommandHandlerInterceptor implements MessageHandlerInterceptor<CommandMessage<?>> {

  @Override
  public Object handle(UnitOfWork<? extends CommandMessage<?>> unitOfWork, InterceptorChain interceptorChain) throws Exception {
    unitOfWork.afterCommit((u) ->
      u.getExecutionResult()
      .getResult()
      .optionalExceptionResult()
      .ifPresent( (Throwable i) -> {
        // Handle Domain Exception
      })
    );
    return interceptorChain.proceed();
  }

Thanks for sharing your solution with others here @pyjac.
I do have a question regarding this though:

Also, I think the doc for 4.2 needs to be updated because the handle method of MessageHandlerInterceptor takes two parameters not three.

If I check the Reference Guide repository I cannot find any reference of a 3 parameter implementation of the MessageHandlerInterceptor. Would you mind specifying where you have seen this issue instead of just stating it? Ideally, an issue on the Ref.Guides repo would help us and other users greatly on that part for any issues you'd create.


SignIn fetch userInfo.

Thanks for the pull request! Could you give us a bit more context on this change?

Of course. Just like the + (RACSignal *)signInToServerUsingWebBrowser:(OCTServer *)server scopes:(OCTClientAuthorizationScopes)scopes method dose in OCTClient. Once the user login success using the browser, I have been able to obtain the userInfo. So I don't need to send a separate request to fetch the userInfo.

@leichunfeng Ah, I see, thanks!
@octokit/octokit-objc Any thoughts here? This makes sense to me.

Replacing rawLogin with login isn't correct in the general case. The raw login should be the username you provide for authentication, while login is the “canonical” username for the GitHub APIs.
In the case of LDAP authentication, rawLogin may contain special LDAP characters that GitHub doesn't support, so it should only be used for the auth flow. login would be the normalized version of that, and could be passed to GitHub APIs that accept usernames.

I have fixed the problem about the assignment of rawLogin.
But the already exists method + (RACSignal *)signInToServerUsingWebBrowser:(OCTServer *)server scopes:(OCTClientAuthorizationScopes)scopes in OCTClient had the same problem and may be can not using the same way to fix it.

assigning to @jspahrsummers since he has a better understanding of rawLogin problems.

But the already exists method + (RACSignal *)signInToServerUsingWebBrowser:(OCTServer *)server scopes:(OCTClientAuthorizationScopes)scopes in OCTClient had the same problem and may be can not using the same way to fix it.

That method doesn't accept a raw login, since the user signs in through the website. In fact, there's no possible rawLogin for that flow—we can only keep the username given to us by the GitHub API.

I have fixed the problem about the assignment of rawLogin.

Hmm, I'm still a bit confused about this code. What problem is fixed by this newest revision?

Replacing rawLogin with login isn't correct in the general case. The raw login should be the username you provide for authentication, while login is the “canonical” username for the GitHub APIs.

So I replace the previous has problem code if (user.rawLogin == nil) userDict[@keypath(user.rawLogin)] = user.login; with userDict[@keypath(user.rawLogin)] = client.user.rawLogin;. Because I can retrieve the username which the user input just is the rawLogin when the user using the native login flow to log in.

Sorry for not being clear.
My question is: what error or bug does this fix? Is there a behavior that occurs before this pull request that is now different after this change?

Nothing. I just add a chaining operation fetchUserInfo.

Of course. Just like the + (RACSignal *)signInToServerUsingWebBrowser:(OCTServer *)server scopes:(OCTClientAuthorizationScopes)scopes method dose in OCTClient. Once the user login success using the browser, I have been able to obtain the userInfo. So I don't need to send a separate request to fetch the userInfo.

Ah, I see.
Since not everyone may want to make that request (for example, because they don't need the data), it doesn't seem like the library should automatically do it. :confused:
Thanks for the pull request, though! :sparkles:


Add support for reproducible builds

Adds support for reproducible builds as required by the .NET Foundation project requirements: https://github.com/dotnet-foundation/projects#eligibility-criteria under the Code subsection.

Please open a issue discussing what this is and follow the PR template.

You havent discussed with any maintainers.

I am a maintainer of RxUI, thanks!

You haven't been involved in the splat project for over 3 years. Nor any rxui project other than refit. No discussion just come bulling in with a PR then using dnf policy as a excuse that doesn't even have a hard requirement on this package

The dependency is from the Foundation itself as the easiest "one click" way of getting things working. It can also be done in other ways too. There's no risk on that package, it's not third party, it's first party.
I never stopped being a maintainer, just stepped back to focus on other things. This is a small build-time enhancement that improves the security of the package; there's not much discussion required for this.

@clairernovotny a few things regarding this...

I recognize that this is a valuable improvement for developers consuming the library. To the best of my knowledge Prism and other libraries I write already follow these standards for that very reason. However, it is really inappropriate for the Foundation to impose and then expect member projects to follow such guidelines when the Foundation takes no active steps in discussing things with the maintainers of the member projects.

 I am fully aware of your history with Rx and many other libraries in the .NET ecosystem. I am also aware of various reasons that you would have had to step back from an active role. That being said, being a maintainer is about more than having access to a repo or what you have done in years past. In your absence, others within the community like @glennawatson & @RLittlesII have stepped up as the projects active maintainers. I find your comments here to be highly disrespectful of both Glenn and Rodney for you to assume that you are entitled to do whatever you would like with a project when you do not operate as part of a team, and properly communicate with the active maintainers of the project. Neither your role within the .NET Foundation or your past work on the project entitles you to bypass the projects current maintainers.

Given that you are not an active maintainer of this project, in the future please show this and all other .NET Foundation member project maintainers the respect of following their guidelines in opening an issue when required. Alternatively please show the respect the maintainers deserve, and that you are a team player by having the proper dialog with the projects active maintainers first.

Let's not #yolo merge things without discussion, even if they seem like good ideas. Splat is used by too many people to do stuff like that.

I will point out that the discussion on this PR feels like a Code of Conduct violation.
We have a template for Issues and Pull Requests that link to "How to Contribute".
We ask that issues be opened, and a discussion started to foster a healthy community inside the ReactiveUI project.
When presented with that constructive feedback, the response was less than professional.  There is no acceptance of the responsibility for the actions demonstrated.  No care was given to what is best for other project maintainers, let alone the overall community.  No apology to those affected by our mistakes.

Wow great conversation! Let's lock it to contributors just for a laugh and not because someone just unhelpfully sent 27.3k Looky-Loos over to drop their $0.02 on my repo

(to be 100% clear, if you're a contributer and want to write more, please do!)


Support for OSBA and p-MySQL

Hi @bingosummer , Can you help review it?

LGTM.
CC @zhongyi-zhang and @norshtein, who are actively working on OSBA.

Hi @davewalter ,
Could you help merge this PR?
Thanks

Hi @HDYA,

Could you help merge this PR?
Thanks

Sorry for the delay (vacation). I'm afraid that I am no longer on the Diego Persistence team. @paulcwarren or @DennisDenuto should be able to help with this.
Regards,
Dave

Thanks @davewalter

cc /@cloudfoundry/cf-diego-persistence


Advertise the VK_EXT_robustness2 extension.

We only support the robustImageAccess2 feature for now. Metal's
guarantees around out-of-bounds accesses to textures give us this for
free. nullDescriptor should also be possible to implement, but it
needs testing. Null image descriptors will probably just work, but null
buffer pointers probably not. We may need help, either from SPIRV-Cross
or a pass in SPIRV-Tools. robustBufferAccess2 definitely needs an
assist from SPIRV-Tools. All three are useful for Direct3D compatibility
layers (DXVK, wined3d).

When is that (what I assume is a) race condition in Travis going to get fixed?

When is that (what I assume is a) race condition in Travis going to get fixed?

I talked to James (Khronos webmaster) about that a little while ago...and he indicated I'll need to reach out to Travis with a complaint. I just haven't got around to it yet.

Hi @billhollings and @cdavis5e! Hope all is well.
Is there an issue open for building support for the nullDescriptor and robustBufferAccess2 features of the VK_EXT_robustness2 extension? Would love to follow the progress on them.

Hi @billhollings and @cdavis5e! Hope all is well.
Is there an issue open for building support for the nullDescriptor and robustBufferAccess2 features of the VK_EXT_robustness2 extension? Would love to follow the progress on them.

Hi @billhollings! Updating this because I just realized this is a pull request rather than an open issue. I guess I meant to ask if there is already a branch to tackle the implementation of nullDescriptor and robustBufferAccess?

Hi @billhollings and @cdavis5e! Hope all is well.
Is there an issue open for building support for the nullDescriptor and robustBufferAccess2 features of the VK_EXT_robustness2 extension? Would love to follow the progress on them.

Hi @billhollings! Updating this because I just realized this is a pull request rather than an issue. I guess I meant to ask if there is already a branch to tackle the implementation of nullDescriptor and robustBufferAccess?

Since I wrote my commit message, I looked into it, and I'm afraid it's more complicated than what I wrote. The problem is for robustBufferAccess2--and actually, the original robustBufferAccess as well--is that it also applies to buffers we can't easily bounds-check from a shader, like the vertex attribute and index buffers. We'll need help from Metal for that.
nullDescriptors, meanwhile, won't fly with Metal validation--having nil shader resources that are used isn't permitted. We'll need help from Metal here, too.

Since I wrote my commit message, I looked into it, and I'm afraid it's more complicated than what I wrote. The problem is for robustBufferAccess2--and actually, the original robustBufferAccess as well--is that it also applies to buffers we can't easily bounds-check from a shader, like the vertex attribute and index buffers. We'll need help from Metal for that.
nullDescriptors, meanwhile, won't fly with Metal validation--having nil shader resources that are used isn't permitted. We'll need help from Metal here, too.

@cdavis5e woops, totally meant to tag you instead of Bill. But thanks for the reply! Hopefully Metal/Apple will indeed help.


Setup release v0.0.26 [phab:D1150]

Created by zarko at 2016-11-11 21:44:32:

fromberger accepted this revision at 2016-11-11 21:47:44

zarko closed via commit c39b3ffd9e7e6a40a6883d91263c068d989294c8 at 2016-11-11 22:00:24


Weak test revisions

This PR revises our Weak tests...
The Weak module depends on the state of the GC.
As such, we have to be extra careful to start from "as clean a starting point as possible".
Just having run sequential tests pollutes the heap state - so better run a Gc.full_major () initially - and a cheaper Gc.minor () in between attempts.
Secondly, the PR switches away from strings to more easy-to-shrink int64s.
Finally I think running Lin tests of Weak is misguided, as I don't think it makes sense to perform a fragile GC-dependent parallel run and compare its outputs against more fragile GC-dependent sequential runs.
Parallel Weak STM tests however work well as stress tests - we previously caught run-time bugs that way (e.g., #181)
Hopefully this will solve #299.
I can see a 5.2 s390x run even completed within the timelimit with this: :tada:
https://ocaml-multicoretests.ci.dev:8100/job/2023-06-09/150708-ci-ocluster-build-44e4ee

The shadowing is handled in 9b85211.
I've also gone for removing the Lin tests entirely as I don't see us needing them in the future.
We may have to disable the parallel src/weak/stm_tests_hashset test on Windows bytecode where it doesn't seem to consistently trigger.

CI summary for 720028c

a failure to trigger a parallel weak/stm_tests_hashset on Windows bytecode 5.1.0~alpha2
a timeout due to excessive Lin Ephemeron shrinking on Cygwin part 1 5.1.0~alpha2
a timeout due to excessive Lin Out_channel shrinking on Windows bytecode trunk 5.2
a timeout due to threadomain livelock on Windows 5.1.0~alpha2 and on Windows trunk 5.2 #203
a timeout due to a on domain_spawntree with Atomic on Windows trunk 5.2 #354
a timeout due to long-running int ref STM and Thread tests (several 1500+ secs) on Cygwin part 2 trunk 5.2
a failure to trigger a Lin Out_channel test on Linux arm64 5.1 #360

Modulo the first one, none of this is related to this PR.

Small suggestion for the last commit: rather than disabling the warning globally, it can be disabled only where it might trigger, it’s easier to understand why it is required.
@@ -41,6 +41,7 @@ struct

   module Int64 =
   struct
+    [@@@warning "-unused-value-declaration"]
     (* support Int64.hash added in 5.1 *)
     external seeded_hash_param :
       int -> int -> int -> 'a -> int = "caml_hash" [@@noalloc]

CI summary for the latest run:

1 Windows bytecode 5.1.0~alpha2 threadomain timeout and 1 crash - with a new variant #203
1 Windows bytecode trunk 5.2 unexpected Thread Queue counterexample #363
2 timeouts on Cygwin part 1 5.1 and 1 Linux s390x 5.1 due to several (primary Lin) tests taking 1000+ seconds
1 macOS arm64 5.2 failure to trigger STM int ref test parallel asymmetric #364

I'll go ahead and merge.


[#noissue] Optimize druid plugin.

@Xylus PTAL...

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@724143e). Click here to learn what that means.
The diff coverage is 20%.

@@           Coverage Diff            @@
##             master   #4814   +/-   ##
========================================
  Coverage          ?   40.8%
========================================
  Files             ?    2590
  Lines             ?   78734
  Branches          ?   10663
========================================
  Hits              ?   32131
  Misses            ?   43622
  Partials          ?    2981

Impacted Files
Coverage Δ

.../pinpoint/plugin/druid/DruidDataSourceMonitor.java
65.21% <20%> (ø)

Continue to review full report at Codecov.

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

DruidDataSource.getUrl()
DruidDataSource.getActiveCount()
DruidDataSource.getMaxActive()
These methods have existed since the original version of the Druid.
So. I think remove the reflection from interceptors.


Method-based Routing not work

Describe the bug
Method-based Routing not work.
To Reproduce
Steps to reproduce the behavior:
Apply this yaml context:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: test-ambassdor-method-get
  labels:
    app: test-ambassdor-method-get
spec:
  replicas: 1
  selector:
    matchLabels:
      app: test-ambassdor-method-get
  template:
    metadata:
      labels:
        app: test-ambassdor-method-get
    spec:
      containers:
      - name: app
        image: registry.cn-shanghai.aliyuncs.com/loulan-public/ambassdor-method:v2
        ports:
        - containerPort: 8080
        command: ["/workspace/app"]
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: test-ambassdor-method-post
  labels:
    app: test-ambassdor-method-post
spec:
  replicas: 1
  selector:
    matchLabels:
      app: test-ambassdor-method-post
  template:
    metadata:
      labels:
        app: test-ambassdor-method-post
    spec:
      containers:
      - name: app
        image: registry.cn-shanghai.aliyuncs.com/loulan-public/ambassdor-method:v2
        ports:
        - containerPort: 8080
        command: ["/workspace/app"]
---
apiVersion: v1
kind: Service
metadata:
  name: test-ambassdor-method-get
spec:
  selector:
    app: test-ambassdor-method-get
  ports:
    - protocol: TCP
      port: 80
      targetPort: 8080
---
apiVersion: v1
kind: Service
metadata:
  name: test-ambassdor-method-post
spec:
  selector:
    app: test-ambassdor-method-post
  ports:
    - protocol: TCP
      port: 80
      targetPort: 8080
---
#apiVersion: getambassador.io/v2.  I am try v2 version, but it also do not work.
apiVersion: getambassador.io/v3alpha1
kind: Mapping
metadata:
  name: test-ambassdor-method-get
spec:
  prefix: /ambassdor-method
  service: test-ambassdor-method-get.default
  method: GET
  host_redirect: true
  method_regex: true
  hostname: "*"
---
#apiVersion: getambassador.io/v2
apiVersion: getambassador.io/v3alpha1
kind: Mapping
metadata:
  name: test-ambassdor-method-post
spec:
  prefix: /ambassdor-method
  hostname: "*"
  service: test-ambassdor-method-post.default
  method: POST
  host_redirect: true
  method_regex: true

Run this command;
[root@cluster1-master mapping]# curl  -X POST LB-IP/ambassdor-method
{"message":"This is GET server, from test-ambassdor-method-get-5d659c9fcf-sgbrh"}

Expected behavior
A clear and concise description of what you expected to happen.
[root@cluster1-master mapping]# curl  -X POST LB-IP/ambassdor-method
{"message":"This is POST server, from test-ambassdor-method-post-5d659c9fcf-sgbrh"}

Versions (please complete the following information):

Ambassador: 7.2.0
Helm chart: 2.1.0
K8s Version:

Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.1", GitCommit:"86ec240af8cbd1b60bcc4c03c20da9b98005b92e", GitTreeState:"clean", BuildDate:"2021-12-16T11:41:01Z", GoVersion:"go1.17.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.1", GitCommit:"86ec240af8cbd1b60bcc4c03c20da9b98005b92e", GitTreeState:"clean", BuildDate:"2021-12-16T11:34:54Z", GoVersion:"go1.17.5", Compiler:"gc", Platform:"linux/amd64"}

Additional context
Add any other context about the problem here.

This was fixed in Emissary-ingresss 2.1.2, which is now available.


Content for Pytorch library

Added content on Pytorch  library.
Completed Introduction to Pytorch page.
Closes https://github.com/thecuriousteam/PyLibLog/issues/223


Adaptor error on satellite-sea-surface-temperature

From https://cds2-dev.copernicus-climate.eu/datasets/satellite-sea-surface-temperature?tab=download any retrieve ends with this exception:
File "/opt/conda/lib/python3.10/site-packages/distributed/worker.py", line 3016, in apply_function_simple
    result = function(*args, **kwargs)
  File "/src/cads-worker/cads_worker/worker.py", line 36, in submit_workflow
    result = cacholote.cacheable(adaptor.retrieve)(request=request)
  File "/src/cacholote/cacholote/cache.py", line 85, in wrapper
    result = func(*args, **kwargs)
  File "/src/cads-adaptors/cads_adaptors/adaptors/url.py", line 28, in retrieve
  File "/src/cads-adaptors/cads_adaptors/tools/url_tools.py", line 40, in try_download
  File "/opt/conda/lib/python3.10/site-packages/multiurl/downloader.py", line 111, in download
  File "/opt/conda/lib/python3.10/site-packages/multiurl/base.py", line 119, in download
  File "/opt/conda/lib/python3.10/site-packages/multiurl/ftp.py", line 46, in estimate_size
  File "/opt/conda/lib/python3.10/ftplib.py", line 625, in cwd
    return self.voidcmd(cmd)
  File "/opt/conda/lib/python3.10/ftplib.py", line 286, in voidcmd
    return self.voidresp()
  File "/opt/conda/lib/python3.10/ftplib.py", line 259, in voidresp
    resp = self.getresp()
  File "/opt/conda/lib/python3.10/ftplib.py", line 254, in getresp
    raise error_perm(resp)
ftplib.error_perm: 550 /neodc/esacci/sst/data/CDR_v2/AVHRR07/L3C/v2.1/1982/02/02: No such file or directory

Hi @keul ,
I think you posted the wrong URL, I'm going to assume you meant this one:
https://cds2-dev.copernicus-climate.eu/datasets/satellite-sea-surface-temperature?tab=overview
Could you also provide the request you made as I think there are a lot of different options on this page.
Eddy

hmmm, it seems to be using the wrong pattern... And I think it may be a fundamental difference to how the old and new URL adaptor works. Maybe it's something simple like first pattern matched vs last pattern matched, needs further investigation

Uops sorry. Yes, it was https://cds2-dev.copernicus-climate.eu/datasets/satellite-sea-surface-temperature?tab=download

Okay, they are multi-layered problems here, both related to the ftp source type
The first one is easier to solve, the Exception for handling unfound files is only for http. It needs to be more generic, the solution I implemented on our develop stack is a bare exception which I think is possibly the best way. We raise our own excpeption if we don't find any files anyway, so I think it's fine.
The second problem is that we fail to download even legitimate ftp files with multiurl with the following error message:
error_perm: 550 SIZE not allowed in ASCII mode
This I will look into more when I get chance, unless you beat me to it ;-)

This is a problematic ftp URL: ftp://anon-ftp.ceda.ac.uk/neodc/esacci/sst/data/CDR_v2/ATSR/L3C/v2.1/AATSR/2005/03/14/20050314120000-ESACCI-L3C_GHRSST-SSTskin-AATSR-CDR2.1_day-v02.0-fv01.0.nc
And the error message is reproducable locally with the code snippet:
import multiurl url="ftp://anon-ftp.ceda.ac.uk/neodc/esacci/sst/data/CDR_v2/ATSR/L3C/v2.1/AATSR/2005/03/14/20050314120000-ESACCI-L3C_GHRSST-SSTskin-AATSR-CDR2.1_day-v02.0-fv01.0.nc" path="neodc/esacci/sst/data/CDR_v2/ATSR/L3C/v2.1/AATSR/2005/03/14/20050314120000-ESACCI-L3C_GHRSST-SSTskin-AATSR-CDR2.1_day-v02.0-fv01.0.nc" multiurl.download(url, path)


⚠ ClamAV has degraded performance

In f8919b7, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 206 ms

Resolved: ClamAV performance has improved in 36d599c after 10 minutes.


Add withEnvironment and withModifiedEnvironment

From https://hackage.haskell.org/package/mockery-0.3.5/docs/Test-Mockery-Environment.html
I had to use quite frequently and they are not big but uses bracket to recover the original env
Not sure if they follow:

Most of the functions have trivial implementations. If a beginner couldn't write the function, it probably doesn't belong here.

They depends on Prelude funcions (i think base-compat can be replaced with base, given the bounds here)

Sounds like a suitable inclusion for extra - patch welcome!

Sounds like a suitable inclusion for extra - patch welcome!


Return, dishonored Return, and/or contested dishonored Return Entries are in the same batch.

Return, dishonored Return, and/or contested dishonored Return Entries are in the same batch.

Dishonored Return and Contested Dishonored Return entries need to be supported
 EntryDetail.Category
CategoryDishonoredReturn
CategoryDishonoredReturnContested

Rule-wise, the three different kind of returns would not be in the same batch since they flow in different directions.

Thanks for the insight @chuckiebluestar ! With 300+ pages of the nacha specification I still get confused.

Wade: Thanks for responding. I'm a business-side ACH geek with a little
coding knowledge, and I would like to get involved with this project.
On Fri, Jun 15, 2018 at 10:58 AM, Wade Arnold<EMAIL_ADDRESS>wrote:

Thanks for the insight @chuckiebluestar
https://github.com/chuckiebluestar ! With 300+ pages of the nacha
specification I still get confused.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/moov-io/ach/issues/59#issuecomment-397665999, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHRUnyG-PmhCSKBiclrrSiHAT9hZ2ZAPks5t89migaJpZM4LjO3d
.

@chuckiebluestar that would be phenomenal! The project has the opposite problem. We are programmers trying to figure out ACH! Our current goal is to make the most complete open source implementation of an ACH reader/writer. Phase two is adding CSV/JSON parsing from the command line and REStful interface to the library so that other languages can leverage the solution. If we can make it that far then we want to make a ach origination platform that would be more inline with a Stripe style interface that abstracts the ach details.
We ♡ business-side


Forked mode by default

Hi!
I'd like to run pytest in forked mode by default, could you add an ini option?
Upd. Nevermind, I just found out addopts

Indeed. :+1:
(In those situations feel free to close the issue, thanks)


Get a error when use deepspeed training with torch.compile

@tohtana  Hello, I am training a model use deepspeed and huggingface trainer.
I want to use the torch.compile character and fellow
https://github.com/microsoft/Megatron-DeepSpeed/tree/tohtana/enable_compile/examples_deepspeed/compile
to set my deepspeed config file.
Then I get error like

And here is my ds_report info
DeepSpeed C++/CUDA extension op report
--------------------------------------------------
NOTE: Ops not installed will be just-in-time (JIT) compiled at
      runtime if needed. Op compatibility means that your system
      meet the required dependencies to JIT install the op.
--------------------------------------------------
JIT compiled ops requires ninja
ninja .................. [OKAY]
--------------------------------------------------
op name ................ installed .. compatible
--------------------------------------------------
 [WARNING]  async_io requires the dev libaio .so object and headers but these were not found.
 [WARNING]  async_io: please install the libaio-dev package with apt
 [WARNING]  If libaio is already installed (perhaps from source), try setting the CFLAGS and LDFLAGS environment variables to where it can be found.
async_io ............... [NO] ....... [NO]
fused_adam ............. [NO] ....... [OKAY]
cpu_adam ............... [NO] ....... [OKAY]
cpu_adagrad ............ [NO] ....... [OKAY]
cpu_lion ............... [NO] ....... [OKAY]
 [WARNING]  Please specify the CUTLASS repo directory as environment variable $CUTLASS_PATH
evoformer_attn ......... [NO] ....... [NO]
fp_quantizer ........... [NO] ....... [OKAY]
fused_lamb ............. [NO] ....... [OKAY]
fused_lion ............. [NO] ....... [OKAY]
inference_core_ops ..... [NO] ....... [OKAY]
cutlass_ops ............ [NO] ....... [OKAY]
transformer_inference .. [NO] ....... [OKAY]
quantizer .............. [NO] ....... [OKAY]
ragged_device_ops ...... [NO] ....... [OKAY]
ragged_ops ............. [NO] ....... [OKAY]
random_ltd ............. [NO] ....... [OKAY]
 [WARNING]  sparse_attn requires a torch version >= 1.5 and < 2.0 but detected 2.3
 [WARNING]  using untested triton version (2.3.0), only 1.0.0 is known to be compatible
sparse_attn ............ [NO] ....... [NO]
spatial_inference ...... [NO] ....... [OKAY]
transformer ............ [NO] ....... [OKAY]
stochastic_transformer . [NO] ....... [OKAY]
--------------------------------------------------
DeepSpeed general environment info:
torch install path ...............
torch version .................... 2.3.0+cu121
deepspeed install path ...........
deepspeed info ................... 0.14.2, unknown, unknown
torch cuda version ............... 12.1
torch hip version ................ None
nvcc version ..................... 12.1
deepspeed wheel compiled w. ...... torch 2.3, cuda 12.1

can you help me to figure out the problem? Thanks!

I have found the problem.  It looks that config should be
"compile": {
"enable": true,
"backend": "inductor"
},
instead of
"compile": {
"disable": false,
"backend": "inductor"
}
for my deespeed version


Added Permission for BackgroundRefresh

Hi @eikebartels , sorry for the delay :)
Thank you for your PR, I was about to merge it but I found this in the doc:

If your app relies on being launched into the background to perform tasks, you can use the value of this property to determine if doing so is possible and to warn the user if it is not. Do not warn the user if the value of this property is set to restricted; a restricted user does not have the ability to enable multitasking for the app.
source

Because Permission only has a denied status, we can't know if the property was denied or restricted and thus,  we won't be able to handle it accordingly to Apple's guideline.
I might add a restricted status in the future though, and I will ping you here when it's done.
Thanks again!


TupleRecord type?

The shared tuples array is described as:

Type
Name
Description

TupleRecord
sharedTuples[sharedTupleCount]
Array of tuple records shared across all glyph variation data tables.

What is the TupleRecord type? I can't see it defined anywhere. Should this be Tuple?

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

ID: 446bcdab-0883-6d30-b5ed-0d04262ff820
Version Independent ID: cdf10ecc-926a-a992-fb71-67213ea8113f
Content: gvar — Glyph Variations Table (OpenType 1.8.4) - Typography
Content Source: typographydocs/opentype/spec/gvar.md
Product: typography
GitHub Login: @PeterCon
Microsoft Alias: alib

Addressed in OpenType 1.9. Closing.


Message not sent

Sometimes the message didn't saved in firebase. sendMessageWithText return Done, but in firebase, the message doesn't exist. Some of them were saved to firebase a minute later, but some of them didn't. I thought it was because something wrong and sign out, but I did try login again, but still didn't send out.

Have you made any modifications to the SDK. For example, adding your own Firebase details? Also, is there any kind of error message in the console? Finally, which country are you based in? How good is your internet connection?

Hi, I do add my own firebase info. I didn't get any error message. After some debugging, I find out that it cause that user is not online. I did make some modifications to adapt to my custom login, what I did is when user login to my server, I also auto login to firebase. When user open a chat room, I open up ChatSDKChatActivity directly.
Intent intent =new Intent(context, ChatSDKChatActivity.class);
From firebase, I can see sometimes once open up ChatSDKChatActivity, user "online" become true (it's working) and other time stay false (that when message will not send out). I see a lot of online checking in other activity, such as enableCheckOnlineOnResumed. I wonder it's because in the ChatSDKMainActivity, it push user online, but mine go to the ChatSDKChatActivity directly.
Map<String, Object> data = AbstractNetworkAdapter.getMap(
                        new String[]{BDefines.Prefs.LoginTypeKey, BDefines.Prefs.LoginEmailKey, BDefines.Prefs.LoginPasswordKey},
                        BDefines.BAccountType.Password, email, FIRE_BASE_PASSWORD);

                BNetworkManager.sharedManager().getNetworkAdapter()
                        .authenticateWithMap(data).done(new DoneCallback<Object>() {
                    @Override
                    public void onDone(Object o) {
                        BUser currentUser = BNetworkManager.sharedManager().getNetworkAdapter().currentUserModel();
                        Log.e("user firebase id", currentUser.getEntityID());

                        // 2. update user name
                        currentUser.setMetaName(userBean.getName());
                        BNetworkManager.sharedManager().getNetworkAdapter().pushUser();

                    }
                }).fail(new FailCallback<BError>() {
                    @Override
                    public void onFail(BError bError) {
                        Log.e("error", "fire base login error " + bError.message);
                    }
                });

It seem like it's not connected to firebase in ChatSDKBaseActivity, goOnline or userGoOnline isn't working, I have to logout and relogin.
public void goOnline() {
DatabaseReference.goOnline();
    setUserOnline();
}

@Override
protected void onStart() {
super.onStart();
getNetworkAdapter().setUserOnline();
}
@Override
protected void onStop() {
    super.onStop();
    getNetworkAdapter().setUserOffline();
}

help me some for my issues

I find that the problem is in login, neither success or error shown in logcat, not sure why.
            ```

Map<String, Object> data = AbstractNetworkAdapter.getMap(
new String[]{BDefines.Prefs.LoginTypeKey, BDefines.Prefs.LoginEmailKey, BDefines.Prefs.LoginPasswordKey},
BDefines.BAccountType.Password, email, FIRE_BASE_PASSWORD);
            BNetworkManager.sharedManager().getNetworkAdapter()
                    .authenticateWithMap(data).done(new DoneCallback<Object>() {
                @Override
                public void onDone(Object o) {
                    BUser currentUser = BNetworkManager.sharedManager().getNetworkAdapter().currentUserModel();
                    Log.e("error", "firebase login success user firebase id " + currentUser.getEntityID());
                }
            }).fail(new FailCallback<BError>() {
                @Override
                public void onFail(BError bError) {
                    Log.e("error", "firebase login error " + bError.message);
                }
            });

This needs to be re-tested in v4.0 and reopened if necessary.


Support pre/post install hook directories

Indirectly fixes #25
This change allows users to mount a pre-install and/or post-install directory. Inside these directories users can place .sh scripts which will all be executed either before or after the install step. These directories give users the flexibility to create their own derived docker images with all the customization they may need to reproduce a working custom game server.
Some use cases I have:

Setting up a minecraft image that includes all the plugins and custom settings I want, and pinning the MC version so I decide when to upgrade it.
Setting up a gmod server with custom assets, fastdl and mods
Looking to do something similar to gmod with 7DaysToDie

I have an example repo setup to show how this could be used, https://github.com/joshhsoj1902/docker-linuxgsm-example

A couple shortcomings I've noticed playing with this:

If one of the hooks directories exists, but is empty the startup will fail saying it didn't find anything matching *.sh
If the pre-install hook creates the /data/serverfiles directory, the entrypoint-user.sh will skip the autoinstall and will do an update instead. For minecraft this means the Eula doesn't get accepted.

https://github.com/GameServerManagers/LinuxGSM/pull/4299 is likely a better option for this feature.
@dgibbs64 and I had a discussion about this https://discord.com/channels/127498813903601664/1080548263977046078/1159224633376120882
I'm going to leave this PR open for now because anyone who wants to create their own Dockerfiles supporting hooks can do so by making similar changes to the most up-to-date entrypoint-user.sh and creating a file that looks like something like this:
FROM gameservermanagers/gameserver:gmod

ADD entrypoint-user.sh /app/entrypoint-user.sh


Maintenance of the protobuf-embedded-c project

I think we need to determine if there are any plans to maintain this project in the future. This issue is mainly directed at @nvpopa as he is the only contributor identifed by github to have an account here.
Vlad, as I understand, the project was developed as part of the E-Energy-Grid demonstrator. Do you still work in the embedded industry?
My interest in this library (or Nanopb) is due to my need to have some protocol between a data gathering microcontroller and an embeded system used to process (and store that data).
I plan to evaluate both projects and direct my efforts at one that suits me best.
I know that some may hate me for this but I am CCing everybody who have cloned this repo on github before with 2 questions:

have you used this library at all?
do you still have a use case for it that motivated you to fork this project?

CC @mikevoyt, @simonAndre, @benmargolin, @AlexanderSkvortsov, @bumpy-b, @locomuco, @RohanBenkar, @ctiller, @bitmorse, @yossi-k

I forked this library because I was evaluating it for a use-case similar to
yours.
I haven't got the chance to use it yet, and quite frankly I don't think I
ever will.
From: Andrew Berezovskyi<EMAIL_ADDRESS>Sent: Thursday, September 24, 2015 17:03
To: berezovskyi/protobuf-embedded-c <
<EMAIL_ADDRESS>Cc: Yossi Konstantinovsky<EMAIL_ADDRESS>Subject: [protobuf-embedded-c] Maintenance of the protobuf-embedded-c
project (#56)
I think we need to determine if there are any plans to maintain this
project in the future. This issue is mainly directed at @nvpopa
https://github.com/nvpopa as he is the only contributor identifed by
github to have an account here.
Vlad, as I understand, the project was developed as part of the
E-Energy-Grid demonstrator. Do you still work in the embedded industry?
My interest in this library (or Nanopb https://github.com/nanopb/nanopb)
is due to my need to have some protocol between a data gathering
microcontroller and an embeded system used to process (and store that data).
I plan to evaluate both projects and direct my efforts at one that suits me
best.
I know that some may hate me for this but I am CCing everybody who have
cloned this repo on github before with 2 questions:

have you used this library at all?
do you still have a use case for it that motivated you to fork this
project?

CC @mikevoyt https://github.com/mikevoyt, @simonAndre
https://github.com/simonAndre, @benmargolin
https://github.com/benmargolin, @AlexanderSkvortsov
https://github.com/AlexanderSkvortsov, @bumpy-b
https://github.com/bumpy-b, @locomuco https://github.com/locomuco,
@RohanBenkar https://github.com/RohanBenkar, @ctiller
https://github.com/ctiller, @bitmorse https://github.com/bitmorse,
@yossi-k https://github.com/yossi-k
—
Reply to this email directly or view it on GitHub
https://github.com/berezovskyi/protobuf-embedded-c/issues/56.

@yossi-k thanks for a prompt reply. Feel free to unsubscribe from the notifications if you don't have any interest in this project any longer.

We used it at my previous company on a prototype we were developing.  It worked fined, but I left a few months ago, and I believe they switched to a different protobuf implementation since.

@mikevoyt Thanks Mike, do you happen to know if that implementation was Nanopb?

Not sure what they moved to, sorry...
-mike
On Sat, Sep 26, 2015 at 2:12 AM, Andrew Berezovskyi <
<EMAIL_ADDRESS>wrote:

@mikevoyt https://github.com/mikevoyt Thanks Mike, do you happen to
know if that implementation was Nanopb?
—
Reply to this email directly or view it on GitHub
https://github.com/berezovskyi/protobuf-embedded-c/issues/56#issuecomment-143414197
.

@berezovskyi
Hi, I just started working on this, so while trying to build the project in eclipse I am facing some issue. Can you help me with it?
Error:
eclipse can not resolve class such as ProtoLexer, ProtoParser etc.
Can you suggest me what could have gone wrong in my setup? I know it is very less information, so let me know if you want any further information.
Thank you

@abhilashdeshmukh hi, sounds like you have some ANTLR problems. I do not have much time to debug this now, but seems like there are extra ANTRL requirements: https://github.com/berezovskyi/protobuf-embedded-c#development-environment

Will be closing the repo


Stateful variants of functions

Currently, map, filter etc must be stateless, otherwise the returned builder can't be reused. We might consider adding stateful versions of them, ie, where the function is provided by a Supplier. This would then allow you to create things like a ProcessorBuilder<ByteBuffer, CharSequence> for decoding bytes into characters, that could be applied to many graphs, without having to create a new ProcessorBuilder each time.
We might also consider making the spi provide this, even if we don't offer it in the api, so that it can be added in future. The filter stage already allows stateful filtering, which is how drop and dropWhile are implemented.
We could also have a general stateful stage constructor in the API, which is a Supplier<Graph>, that gets supplied when the graph is built. This wouldn't need support in the spi.

Are you suggesting to create StatefulMap and StateFilter?

Probably not - though it does depend on how much we want the SPI to cover. It could be achieved by simply making Map have a Supplier<Function<A, B>>, rather than a Function<A, B>. Then, the existing map method in the API would just pass its stateless map function to the Map returned by a stateless supplier, while a new statefulMap API would accept a supplier.
The Filter stage SPI is already stateful, so nothing needs to be changed in the SPI there, the only thing that might change is what APIs we offer.


PHP Google Protobuf lib - Error occurred during parsing: Unexpected wire type.

Here's my step to catch this issue:

Install google/analytics-data + google/protobuf libraries (by Composer)
Everything still good when using google-data-api.
Deploy the project (with vendor folder - we're not run composer install when project is running build) to server.
Catch "Error occurred during parsing: Unexpected wire type." when using google/analytics-data

So I've found 1 solution to fixed, that is remove the google/protobuf in vendor and reinstall. But It's not inappropriate with my case (build without running composer install).
So do you have any other solution for this? Thanks for your help.

Hello @duypham1412 ! Thank you for reporting this. It seems like an issue in the php protobuf implementation (see https://github.com/protocolbuffers/protobuf). If you can provide more information (step-by-step to reproduce - what method are you calling? can you provide a stack trace?) we can open a ticket there and hopefully get it looked at.
As for removing the google/protobuf library, this does not seem like it should work (unless your autoloading is mixed up, and you are loading a different protobuf library somewhere else), as that is a required dependency for this library. There's also the protobuf c-extension, but that would take precedence over the google/protobuf composer library if you had that installed.
One thing you could try is to install the protobuf c-extension (pecl install protobuf). But in general, if removing the library in vendor works for you, I think there's something broken / wrong with your installation / autoloading.

@duypham1412 Please feel free to re-open this PR is the above solution didn't work for you.


fix(docs): Fixing some visual issues with the docs

:tada: This PR is included in version 1.24.1 :tada:
Your semantic-release bot :package::rocket:


Completion of error handling

Would you like to add more error handling for return values from functions like the following?

dup2 ⇒ main
printf ⇒ print_help

If they indeed cause problems, I will fix them.

I suggest to avoid ignorance of return values a bit more.
Would you like to detect every error situation as early as possible?

I will add an assert for dup2. For printf it looks overkill.
For functions which fails frequently(such as socket related) I did add a lot of error handling codes.

I would generally prefer a safe condition check there instead of a macro call with code which can be supressed.

Though I currently dont suppress assert(since they didnt show noticeable performance difference), maybe its a good idea to define a custom assert for the codes which should never be suppressed.

Are you interested to apply aspect-oriented software development?
Would you like to encapsulate error detection and corresponding exception handling as a reusable aspect in your software?

Looks interesting but a bit pedantic😂


Allow to use external tables in dynamic menu entries

Especially useful with config-tables plugin. 😃

Thank you, makes sense!


clear a date?

@jkuri
<ng2-datepicker [(ngModel)]="end_date">
how does one clear the date after it has been selected via Apply button?

Did you ever find out how to do it?

I did get thro' with a incomplete solution which was ugly, so I switched over to md-input-container. But you can try something like
end_date.date = new DateModel();

Yeah I did that too. I just want to make sure that the previous DateModel object gets disposed of correctly, but I'll take make sure of that later. Thank you!

this is now resolved with "clear" button in the ui. please check 1.6.0 version. thanks.

@jkuri, is the clear function still exist in the latest version? i try nom install the latest version seems there is no clear button..

@jkuri, the clear button does not exist on the new version?

this is now resolved with "clear" button in the ui. please check 1.6.0 version. thanks.

I'm using ^3.1.1 version... How can I use this "clear" button?


Upgrade to Humble

Part of https://github.com/osrf/buoy_sim/issues/81

This is open for review. There are outstanding warnings to be fixed upstream:

[ ] Import order errors with Humble, @quarkytale , I think we need to release https://github.com/ros2/rosidl_python/pull/173 for Humble.
[ ] DeprecationWarning: SelectableGroups, which is known upstream: https://github.com/ament/ament_cmake/issues/382

Ouch I think we'll need to split this package (https://github.com/ros2/ros2_documentation/pull/2882):
Calling rosidl_generate_interfaces and ament_python_install_package in the same CMake project does not work.
See this Github issue for more info. It is best practice to instead
separate out the message generation into a separate package.

We're getting the import order errors with Humble, @quarkytale , I think we need to release https://github.com/ros2/rosidl_python/pull/173 for Humble.

We're getting warnings like this, which is known upstream: https://github.com/ament/ament_cmake/issues/382
2022-08-29T21:20:34.0172029Z =============================== warnings summary ===============================
2022-08-29T21:20:34.0191249Z test/test_flake8.py::test_flake8
2022-08-29T21:20:34.0198098Z test/test_flake8.py::test_flake8
2022-08-29T21:20:34.0205103Z   /usr/lib/python3/dist-packages/flake8/plugins/manager.py:261: DeprecationWarning: SelectableGroups dict interface is deprecated. Use select.
2022-08-29T21:20:34.0211404Z     eps = importlib_metadata.entry_points().get(self.namespace, ())
2022-08-29T21:20:34.0217052Z
2022-08-29T21:20:34.0222950Z -- Docs: https://docs.pytest.org/en/stable/warnings.html
2022-08-29T21:20:34.0237341Z test/test_pep257.py .                                                    [100%]
2022-08-29T21:20:34.0243053Z ------- generated xml file: /github/home/ws/build/buoy_api_py/pytest.xml -------
2022-08-29T21:20:34.0248659Z ======================== 3 passed, 2 warnings in 0.61s =========================
2022-08-29T21:20:34.1087909Z --- stderr: buoy_api_py

Sorry just saw this now, will look into forward porting rosidl-python!

Humble backport PR #183

To be followed up on another PR


Bug 2039665: Fix entrypoint CA bundle permission issues

This is a fix related to #883 , the base image ubi8/nodejs-16-minimal already contains a /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem which has restrictive permissions, because this was the first CA cert copied, it caused subsequent CA additions to the bundle to fail during entrypoint startup.
This PR addresses this issue and also reorders by priority the creation of the NODE_EXTRA_CA_CERTS bundle. At any given time there are 2 CA certificates needed on this bundle: Kube API CA, Service Serving Signer CA, optionally also Custom Ingress CA can be added.
When a Custom Ingress cert has been detected by operator on the cluster , this will inject the trusted-ca configmap with the ca-bundle.crt and mount it in /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem which will override the nodejs-16-minimal file location.

What is the content of /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem? Does it contain the same certificates as /var/run/.../ca.crt ? If yes, this will duplicate the CAs in the final bundle.

@fabiendupont The base image .pem does not include ca.crt , just a bunch of default certs , see below  :
sh-4.4$ openssl crl2pkcs7 -nocrl -certfile /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem | openssl pkcs7 -print_certs -text -noout | grep 'Subject:'
        Subject: CN=ACCVRAIZ1, OU=PKIACCV, O=ACCV, C=ES
        Subject: C=ES, O=FNMT-RCM, OU=AC RAIZ FNMT-RCM
        Subject: C=ES, O=FNMT-RCM, OU=Ceres/organizationIdentifier=VATES-Q2826004J, CN=AC RAIZ FNMT-RCM SERVIDORES SEGUROS
        Subject: serialNumber=G63287510, C=ES, O=ANF Autoridad de Certificacion, OU=ANF CA Raiz, CN=ANF Secure Server Root CA
        Subject: C=IT, L=Milan, O=Actalis S.p.A./03358520967, CN=Actalis Authentication Root CA
        Subject: C=US, O=AffirmTrust, CN=AffirmTrust Commercial
        Subject: C=US, O=AffirmTrust, CN=AffirmTrust Networking
        Subject: C=US, O=AffirmTrust, CN=AffirmTrust Premium
        Subject: C=US, O=AffirmTrust, CN=AffirmTrust Premium ECC
        Subject: C=US, O=Amazon, CN=Amazon Root CA 1
        Subject: C=US, O=Amazon, CN=Amazon Root CA 2
        Subject: C=US, O=Amazon, CN=Amazon Root CA 3
        Subject: C=US, O=Amazon, CN=Amazon Root CA 4
        Subject: CN=Atos TrustedRoot 2011, O=Atos, C=DE
        Subject: C=ES, CN=Autoridad de Certificacion Firmaprofesional CIF A62634068
        Subject: C=IE, O=Baltimore, OU=CyberTrust, CN=Baltimore CyberTrust Root
        Subject: C=NO, O=Buypass AS-983163327, CN=Buypass Class 2 Root CA
        Subject: C=NO, O=Buypass AS-983163327, CN=Buypass Class 3 Root CA
        Subject: C=SK, L=Bratislava, O=Disig a.s., CN=CA Disig Root R2
        Subject: C=CN, O=China Financial Certification Authority, CN=CFCA EV ROOT
        Subject: C=GB, ST=Greater Manchester, L=Salford, O=COMODO CA Limited, CN=COMODO Certification Authority
        Subject: C=GB, ST=Greater Manchester, L=Salford, O=COMODO CA Limited, CN=COMODO ECC Certification Authority
        Subject: C=GB, ST=Greater Manchester, L=Salford, O=COMODO CA Limited, CN=COMODO RSA Certification Authority
        Subject: C=FR, O=Dhimyotis, CN=Certigna
        Subject: C=FR, O=Dhimyotis, OU=0002<PHONE_NUMBER>0036, CN=Certigna Root CA
        Subject: C=PL, O=Asseco Data Systems S.A., OU=Certum Certification Authority, CN=Certum EC-384 CA
        Subject: C=PL, O=Unizeto Technologies S.A., OU=Certum Certification Authority, CN=Certum Trusted Network CA
        Subject: C=PL, O=Unizeto Technologies S.A., OU=Certum Certification Authority, CN=Certum Trusted Network CA 2
        Subject: C=PL, O=Asseco Data Systems S.A., OU=Certum Certification Authority, CN=Certum Trusted Root CA
        Subject: C=GB, ST=Greater Manchester, L=Salford, O=Comodo CA Limited, CN=AAA Certificate Services
        Subject: O=Cybertrust, Inc, CN=Cybertrust Global Root
        Subject: C=DE, O=D-Trust GmbH, CN=D-TRUST Root Class 3 CA 2 2009
        Subject: C=DE, O=D-Trust GmbH, CN=D-TRUST Root Class 3 CA 2 EV 2009
        Subject: O=Digital Signature Trust Co., CN=DST Root CA X3
        Subject: C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert Assured ID Root CA
        Subject: C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert Assured ID Root G2
        Subject: C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert Assured ID Root G3
        Subject: C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert Global Root CA
        Subject: C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert Global Root G2
        Subject: C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert Global Root G3
        Subject: C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert High Assurance EV Root CA
        Subject: C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert Trusted Root G4
        Subject: C=TR, L=Ankara, O=E-Tu\xC4\x9Fra EBG Bili\xC5\x9Fim Teknolojileri ve Hizmetleri A.\xC5\x9E., OU=E-Tugra Sertifikasyon Merkezi, CN=E-Tugra Certification Authority
        Subject: C=ES, O=Agencia Catalana de Certificacio (NIF Q-0801176-I), OU=Serveis Publics de Certificacio, OU=Vegeu https://www.catcert.net/verarrel (c)03, OU=Jerarquia Entitats de Certificacio Catalanes, CN=EC-ACC
        Subject: O=Entrust.net, OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.), OU=(c) 1999 Entrust.net Limited, CN=Entrust.net Certification Authority (2048)
        Subject: C=US, O=Entrust, Inc., OU=www.entrust.net/CPS is incorporated by reference, OU=(c) 2006 Entrust, Inc., CN=Entrust Root Certification Authority
        Subject: C=US, O=Entrust, Inc., OU=See www.entrust.net/legal-terms, OU=(c) 2012 Entrust, Inc. - for authorized use only, CN=Entrust Root Certification Authority - EC1
        Subject: C=US, O=Entrust, Inc., OU=See www.entrust.net/legal-terms, OU=(c) 2009 Entrust, Inc. - for authorized use only, CN=Entrust Root Certification Authority - G2
        Subject: C=US, O=Entrust, Inc., OU=See www.entrust.net/legal-terms, OU=(c) 2015 Entrust, Inc. - for authorized use only, CN=Entrust Root Certification Authority - G4
        Subject: C=CN, O=GUANG DONG CERTIFICATE AUTHORITY CO.,LTD., CN=GDCA TrustAUTH R5 ROOT
        Subject: C=AT, O=e-commerce monitoring GmbH, CN=GLOBALTRUST 2020
        Subject: C=US, O=Google Trust Services LLC, CN=GTS Root R1
        Subject: C=US, O=Google Trust Services LLC, CN=GTS Root R2
        Subject: C=US, O=Google Trust Services LLC, CN=GTS Root R3
        Subject: C=US, O=Google Trust Services LLC, CN=GTS Root R4
        Subject: OU=GlobalSign ECC Root CA - R4, O=GlobalSign, CN=GlobalSign
        Subject: OU=GlobalSign ECC Root CA - R5, O=GlobalSign, CN=GlobalSign
        Subject: C=BE, O=GlobalSign nv-sa, OU=Root CA, CN=GlobalSign Root CA
        Subject: OU=GlobalSign Root CA - R2, O=GlobalSign, CN=GlobalSign
        Subject: OU=GlobalSign Root CA - R3, O=GlobalSign, CN=GlobalSign
        Subject: OU=GlobalSign Root CA - R6, O=GlobalSign, CN=GlobalSign
        Subject: C=BE, O=GlobalSign nv-sa, CN=GlobalSign Root E46
        Subject: C=BE, O=GlobalSign nv-sa, CN=GlobalSign Root R46
        Subject: C=US, O=The Go Daddy Group, Inc., OU=Go Daddy Class 2 Certification Authority
        Subject: C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2
        Subject: C=GR, L=Athens, O=Hellenic Academic and Research Institutions Cert. Authority, CN=Hellenic Academic and Research Institutions ECC RootCA 2015
        Subject: C=GR, O=Hellenic Academic and Research Institutions Cert. Authority, CN=Hellenic Academic and Research Institutions RootCA 2011
        Subject: C=GR, L=Athens, O=Hellenic Academic and Research Institutions Cert. Authority, CN=Hellenic Academic and Research Institutions RootCA 2015
        Subject: C=HK, O=Hongkong Post, CN=Hongkong Post Root CA 1
        Subject: C=HK, ST=Hong Kong, L=Hong Kong, O=Hongkong Post, CN=Hongkong Post Root CA 3
        Subject: C=US, O=Internet Security Research Group, CN=ISRG Root X1
        Subject: C=US, O=IdenTrust, CN=IdenTrust Commercial Root CA 1
        Subject: C=US, O=IdenTrust, CN=IdenTrust Public Sector Root CA 1
        Subject: C=ES, O=IZENPE S.A., CN=Izenpe.com
        Subject: C=HU, L=Budapest, O=Microsec Ltd., CN=Microsec e-Szigno Root CA<EMAIL_ADDRESS>        Subject: C=US, O=Microsoft Corporation, CN=Microsoft ECC Root Certificate Authority 2017
        Subject: C=US, O=Microsoft Corporation, CN=Microsoft RSA Root Certificate Authority 2017
        Subject: C=KR, O=NAVER BUSINESS PLATFORM Corp., CN=NAVER Global Root Certification Authority
        Subject: C=HU, L=Budapest, O=NetLock Kft., OU=Tan\xC3\xBAs\xC3\xADtv\xC3\xA1nykiad\xC3\xB3k (Certification Services), CN=NetLock Arany (Class Gold) F\xC5\x91tan\xC3\xBAs\xC3\xADtv\xC3\xA1ny
        Subject: C=US, O=Network Solutions L.L.C., CN=Network Solutions Certificate Authority
        Subject: C=CH, O=WISeKey, OU=OISTE Foundation Endorsed, CN=OISTE WISeKey Global Root GB CA
        Subject: C=CH, O=WISeKey, OU=OISTE Foundation Endorsed, CN=OISTE WISeKey Global Root GC CA
        Subject: C=BM, O=QuoVadis Limited, CN=QuoVadis Root CA 1 G3
        Subject: C=BM, O=QuoVadis Limited, CN=QuoVadis Root CA 2
        Subject: C=BM, O=QuoVadis Limited, CN=QuoVadis Root CA 2 G3
        Subject: C=BM, O=QuoVadis Limited, CN=QuoVadis Root CA 3
        Subject: C=BM, O=QuoVadis Limited, CN=QuoVadis Root CA 3 G3
        Subject: C=US, ST=Texas, L=Houston, O=SSL Corporation, CN=SSL.com EV Root Certification Authority ECC
        Subject: C=US, ST=Texas, L=Houston, O=SSL Corporation, CN=SSL.com EV Root Certification Authority RSA R2
        Subject: C=US, ST=Texas, L=Houston, O=SSL Corporation, CN=SSL.com Root Certification Authority ECC
        Subject: C=US, ST=Texas, L=Houston, O=SSL Corporation, CN=SSL.com Root Certification Authority RSA
        Subject: C=PL, O=Krajowa Izba Rozliczeniowa S.A., CN=SZAFIR ROOT CA2
        Subject: C=JP, O=Japan Certification Services, Inc., CN=SecureSign RootCA11
        Subject: C=US, O=SecureTrust Corporation, CN=SecureTrust CA
        Subject: C=US, O=SecureTrust Corporation, CN=Secure Global CA
        Subject: C=JP, O=SECOM Trust Systems CO.,LTD., OU=Security Communication RootCA2
        Subject: C=JP, O=SECOM Trust.net, OU=Security Communication RootCA1
        Subject: C=NL, O=Staat der Nederlanden, CN=Staat der Nederlanden EV Root CA
        Subject: C=US, O=Starfield Technologies, Inc., OU=Starfield Class 2 Certification Authority
        Subject: C=US, ST=Arizona, L=Scottsdale, O=Starfield Technologies, Inc., CN=Starfield Root Certificate Authority - G2
        Subject: C=US, ST=Arizona, L=Scottsdale, O=Starfield Technologies, Inc., CN=Starfield Services Root Certificate Authority - G2
        Subject: C=CH, O=SwissSign AG, CN=SwissSign Gold CA - G2
        Subject: C=CH, O=SwissSign AG, CN=SwissSign Silver CA - G2
        Subject: C=DE, O=T-Systems Enterprise Services GmbH, OU=T-Systems Trust Center, CN=T-TeleSec GlobalRoot Class 2
        Subject: C=DE, O=T-Systems Enterprise Services GmbH, OU=T-Systems Trust Center, CN=T-TeleSec GlobalRoot Class 3
        Subject: C=TR, L=Gebze - Kocaeli, O=Turkiye Bilimsel ve Teknolojik Arastirma Kurumu - TUBITAK, OU=Kamu Sertifikasyon Merkezi - Kamu SM, CN=TUBITAK Kamu SM SSL Kok Sertifikasi - Surum 1
        Subject: C=TW, O=TAIWAN-CA, OU=Root CA, CN=TWCA Global Root CA
        Subject: C=TW, O=TAIWAN-CA, OU=Root CA, CN=TWCA Root Certification Authority
        Subject: O=TeliaSonera, CN=TeliaSonera Root CA v1
        Subject: C=PA, ST=Panama, L=Panama City, O=TrustCor Systems S. de R.L., OU=TrustCor Certificate Authority, CN=TrustCor ECA-1
        Subject: C=PA, ST=Panama, L=Panama City, O=TrustCor Systems S. de R.L., OU=TrustCor Certificate Authority, CN=TrustCor RootCert CA-1
        Subject: C=PA, ST=Panama, L=Panama City, O=TrustCor Systems S. de R.L., OU=TrustCor Certificate Authority, CN=TrustCor RootCert CA-2
        Subject: C=US, ST=Illinois, L=Chicago, O=Trustwave Holdings, Inc., CN=Trustwave Global Certification Authority
        Subject: C=US, ST=Illinois, L=Chicago, O=Trustwave Holdings, Inc., CN=Trustwave Global ECC P256 Certification Authority
        Subject: C=US, ST=Illinois, L=Chicago, O=Trustwave Holdings, Inc., CN=Trustwave Global ECC P384 Certification Authority
        Subject: C=CN, O=UniTrust, CN=UCA Extended Validation Root
        Subject: C=CN, O=UniTrust, CN=UCA Global G2 Root
        Subject: C=US, ST=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust ECC Certification Authority
        Subject: C=US, ST=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust RSA Certification Authority
        Subject: C=US, OU=www.xrampsecurity.com, O=XRamp Security Services Inc, CN=XRamp Global Certification Authority
        Subject: C=RO, O=certSIGN, OU=certSIGN ROOT CA
        Subject: C=RO, O=CERTSIGN SA, OU=certSIGN ROOT CA G2
        Subject: C=HU, L=Budapest, O=Microsec Ltd./organizationIdentifier=VATHU-23584497, CN=e-Szigno Root CA 2017
        Subject: C=TW, O=Chunghwa Telecom Co., Ltd., OU=ePKI Root Certification Authority
        Subject: C=US, OU=emSign PKI, O=eMudhra Inc, CN=emSign ECC Root CA - C3
        Subject: C=IN, OU=emSign PKI, O=eMudhra Technologies Limited, CN=emSign ECC Root CA - G3
        Subject: C=US, OU=emSign PKI, O=eMudhra Inc, CN=emSign Root CA - C1
        Subject: C=IN, OU=emSign PKI, O=eMudhra Technologies Limited, CN=emSign Root CA - G1

Here is the kube api server CA :
openssl crl2pkcs7 -nocrl -certfile /opt/app-root/src/ca.crt | openssl pkcs7 -print_certs -text -noout | grep 'Subject:' | grep kube-apiserver
        Subject: OU=openshift, CN=kube-apiserver-lb-signer
        Subject: OU=openshift, CN=kube-apiserver-localhost-signer
        Subject: OU=openshift, CN=kube-apiserver-service-network-signer
        Subject: CN=openshift-kube-apiserver-operator_localhost-recovery-serving-signer@1641235272
sh-4.4$


Headers in Tonals page

Please confirm if I'm reading the Tonals page properly.
Since it's a mix of tabular and cross-tabular data structure, it would be easier to parse this if my understanding of this page is proper.
One set consists of the following under PROPULSION tonal type

Cruise Plant
Boost Plant
Reduction Ratio
Max TRPM
Shaft x Blade
MTBF
BHP
Av Temp
Max SRPM

One set under LIMITED DATA tonal type

Drive
Mode
Shaft x Blade
R:R
BHP
Av Temp (Guide)

One set under POWER RELATED tonal type

Source
Ratio/Freq
Harmonics
Remarks

One set under SIGNATURE & CHARACTERISTICS tonal type

Acoustic Signature
Unique classifiers
Aural

Also, please throw some light on how to read Commonly Detected Sources.
Also, can these attributes be expected to be in the original data as is?

Okay, let me get started just with proper Tonals then: "Source, Ratio/Freq, Harmonics and Remarks".
Could you also look into the other two questions that I have?
Also, please throw some light on how to read Commonly Detected Sources.

Also, can these attributes be expected to be in the original data as is? Meaning can these attributes be hard coded?

Also, please throw some light on how to read Commonly Detected Sources.

Rows of tonals, each with their preceding tonal-type. They tend to start with propulsion data, but the order of the others is less preditable.

Also, can these attributes be expected to be in the original data as is? Meaning can these attributes be hard coded?

The table headers can be hard-coded. The tonal-types cannot be.  I may have some work to provide increased consistency across the tonal types, but this will be easier to understand once we have processing for it.

Do you want any tests here, @IanMayo?
Say, don't  read any tonals without Commonly Detected Sources.

Say, don't read any tonals without Commonly Detected Sources.

For now, I'd like that to be reported as a discrepancy.  That will let me check that there aren't any subtle mis-spellings.
I'll try to think of other instances of doing that, as they arise.

Okay

I think we're past this now @rnllv
Our mock data demonstrates the above patterns. Well, it should ;-)
Can we close it?

Closing this as this issue has been outdated by recent changes.


python: open README.rst with utf-8 encoding

This would ensure pulumi-gcp can be installed using python3-pip

Closing this as this has been fixed in our new upstream pulumi-terraform-bridge project


This has happened twice now since yesterday, and each time it was resolved by deleting my .atom/storage directory.
Any thoughts on first troubleshooting steps?

Actually going to close this in favor of #8849 since maxbrunsfeld just assigned himself to that issue.


ORCORC-271: Improve HAS_PRE_1970/HAS_POST_2038 code

Change in HAS_POST_2038 shows the bug in osx/clang build:
/Users/travis/build/apache/orc/tools/test/TestMatch.cc:149: Failure
Expected: expectedLine
Which is: "{"time": "2038-05-05 12:34:56.1", "date": "2038-12-25"}"
To be equal to: line
Which is: "{"time": "2038-05-05 11:34:56.1", "date": "2038-12-25"}"
wrong output at row 0

Your HAS_POST_2038 doesn't do the correct test.
The point of the HAS_POST_2038 isn't that gmtime fails, it is that the timezone information continues in 2038. MacOS is the last hold out using the old 32 bit timezone files.
So the current test uses Americas/Los_Angeles and checks to see if daylight savings happens in 2038. Your test for HAS_POST_2038 erroneously passes on MacOS.

'Simplify HAS_POST_2038 check' commit is reverted.


Hang on multiple fast requests for short-term lease

Run the below command multiple times in quick succession to reproduce this.
curl -d '{"max_time":1}' -XPOST <IP_ADDRESS>/lease

This seems to happen only when there are no more clusters left...

Haven't been able to reproduce in the past week. Closing for now

Reopening because this is reoccuring

This hasn't been reproduced in a while, but the claimer hasn't been in production for much of that time. Leaving open and moving to RC1

Closing as the claimer is now integrated with our e2e tests (which I consider "in production") and we haven't seen the issue. My guess is the hang was occurring because either the Kubernetes API or the GKE API was latent.


Use postcss.config.js when present

Issue: #2455
What I did

Add find-up to dependencies to search for the nearest postcss.config.js
Use the nearest postcss.config.js to determine postcss-loader options if present, maintain previous defaults if not.

How to test

Use local storybook core against a test repository using a postcss config with an option not present in the default set (such as postcss-import).

Is this testable with Jest or Chromatic screenshots? Only if a custom serializer renders all styles.
Does this need a new example in the kitchen sink apps?
No.
Does this need an update to the documentation?
Yes. Describe that custom postcss.config.js should be handled just like custom babel configurations. Just wanted to ensure this is the correct direction before I add any changes.
If your answer is yes to any of these, please make sure to include it in your PR.
For maintainers only: Please tag your pull request with at least one of the following:
["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

Gonna wait on #4405 before I move forward.
The only work left to be done will be to integrate with those changes + provide an example + update docs 👍
I'm prepared to make the moves at any moment in my work day.

Suggested spot for documentation:
A section after https://storybook.js.org/configurations/custom-babel-config/ called "other common custom configurations" to leave room for how postcss.config.js gets consumed and - eventually - how .browserlistrc gets consumed

@ndelangen thoughts on deleting this branch PR and starting from the new API changes?

Gonna take another stab at this in a different PR since direction has changed a bit


USHIFT-362: Fix microshift executable location in the devenv docs

Follow-up on #931
Closes USHIFT-362

/hold
until https://github.com/openshift/release/pull/32076 merges.

/lgtm

/hold cancel
as https://github.com/openshift/release/pull/32076 merged.
/retest

/lgtm

/retest

/retest

/retest-required

/retest


Support for Apple Silicon

The App is not compiled for Apple Silicon or as universal binary for macOS. It only works with Rosetta 2

Latest release doesn't even open on Apple Silicon
Non-fatal error enumerating at <private>, continuing: Error Domain=NSCocoaErrorDomain Code=260 "The file “PlugIns” couldn’t be opened because there is no such file." UserInfo={NSURL=PlugIns/ -- file:///Applications/Podman%20Desktop%20Companion.app/Contents/, NSFilePath=/Applications/Podman Desktop Companion.app/Contents/PlugIns, NSUnderlyingError=0x13dd38a10 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}

Can you try this https://github.com/iongion/podman-desktop-companion/releases/download/4.0.3-rc.2/podman-desktop-companion-arm64-4.0.3-rc.2.dmg

Released 4.0.3-rc.3 that should include Apple cpu support - see the homepage https://iongion.github.io/podman-desktop-companion or directly https://github.com/iongion/podman-desktop-companion/releases/download/4.0.3-rc.3/podman-desktop-companion-arm64-4.0.3-rc.3.dmg

Closing this for now, feel free to re-open, I was able to build for Apple CPU, but don't have a device to test, I assume it should be ok.

Sorry I was on vacation. The build works just fine, thanks!


Structural suggestion SDG12.a

SDG: 12
Target & Phrase: 12.a phrases 1 and 2
Suggestion: Could the capacity phrases be streamlined, for simplicity? If the two elements in phrase 2 are merged (i.e. either develop OR ... or infrastructures OR..., rather than AND), then there are only a few terms missing in phrase 1 that would need to be added -
"technical", "scientific", "R&D", "innovation", "cleantech". The only term that doesn't really work in this new structure is "energy transitions", but this should be added to the power terms anyway I think.
Reason: Simplifies - we can cut a NEAR, and use the same term list twice.
"capacity", "infrastructure", "technolog", "facilities", "tools",
"research", "knowledge", "skills", "competenc", "expertise", "technical", "scientific", "R&D", "innovation", "cleantech",
"expenditure", "investing", "investment", "financ", "spending",
"funding", "funder", "financial support", "financial resources",
"incentive", "subsidy", "subsidies", "subsidis", "subsidiz",
"development spending", "international aid", "development aid", "foreign aid", "international assistance", "development assistance", "foreign assistance",
"communication", "campaign",
"cooperation", "collaboration", "network", "support", "partnership",
"policy", "policies", "empower", "strateg", "program", "intervention",
"awareness", "knowledge", "disseminat", "educat", "awareness", "training"

It is also possible that "power station$" OR... in phrase 2 could be used alone, without the near phrase to different energy types (as it is so specific already)

Duplicate issue, #92


PostgreSQL 11 support

pipelinedb-postgresql-11

waiting for that.... ;-)

PipelineDB now supports PostgreSQL 11. Binaries will be released shortly.

https://github.com/pipelinedb/pipelinedb/releases/tag/1.0.0-5


terraform/install: support build_on_remote

Remove the trusted user requirement for --build-on-remote by using --store instead of --builders
This is very useful for cross architecture deploys especially without any remote builders configured

@mergify queue

@mergify queue


Error 502

just reporting vgmdb.info is down. error 502 bad gateway.

Thanks for the notice! I restarted it and it looks to be working now.


No images rendered in release APK

I tried this library for an Android app and it rendered svg icons just fine for the debug build.
Then i tried to create a release apk, but it gave me an error 'filename must end with xml or png.'
So I used "android.disableResourceValidation=true" in gradle.properties, and the error messages were gone.
However, when i run my app, I don't see any svg icons, just a blank area.

Same issue as #10.
Can you try what is suggested in this comment?

Hello,
Getting the same issue, I'm using the gradle version 3.4.0.
using code "android.disableResourceValidation=true" error is gone but when you create the assemple release it throws an error.
Please look into it.
Thanks

This is may be because of https urls, if you are using http links it won't render and same for local svg files , which is considered as local http for source inside webview.
May be a chance to try


does torchscale functionalities can impove  modeling generality and capability in case of Session-Based Recommendation system

i am currently working Session-Based Recommendation system problem, indeed this topic in NLP so quite under progress of improvement, and most of technics used to tackle that problem are Matrix Factorization or GNN recently invidia realized a library TransfomerSRC4,
i would like to ask if there's a way to use TorchScale functionalities to address the problem Session-Based Recommendation or not yet

Actually, I am not familiar with recommendation models. If Transformers4Rec adopts the standard Transformer architecture as its backbone, I think it's possible to replace the backbone with TorchScale to enjoy the functionalities we have.


Nobunaga's Ambition: Souzou Sengoku Risshiden [PCSH00291]

App summary

App name: Nobunaga's Ambition: Souzou Sengoku Risshiden
App serial: PCSH00291
App version: 1.01

Vita3K summary

Version: v0.1.5
Build number: 2697
Commit hash: https://github.com/vita3k/vita3k/commit/1becdabd
CPU backend: Dynarmic

Test environment summary

Tested by: gymzatan
OS: Windows 11
CPU: AMD Ryzen 7 5800H
GPU: AMD Radeon(TM) Graphics
RAM: 16 GB

Issues
Game crashes without booting.
Screenshots

Log
vita3k.log
Recommended labels

Nothing
crash

Vita3K summary

Version: v0.1.6
Build number: 2840
Commit hash: https://github.com/vita3k/vita3k/commit/4a2c6582
CPU backend: Dynarmic

Test environment summary

Tested by: othmanead
OS: Windows 11
CPU: Intel i5-10300H
GPU: RTX 3060 mobile
RAM: 16 GB

Issue:
Game crashes when trying to go ingame
Screenshots:

Log
vita3k.log
Recommended labels

Menu
Crash

as of https://github.com/Vita3K/Vita3K/commit/22ea4f03d2c8c516159596b3b42c097406b7fe95, the game now can go ingame. Playable if you have a powerful computer. Sometimes the audio crackles after dialogue is finished.
Screenshots

Log
vita3k.log
Recommended Labels

Playable


gosund UP111 - 3 out of 4 successfully flashed

Did you have issues getting a device to flash?
Please be sure to include your device name, model, and firmware version as well as your logs!
Bought a 4pk Gosund UP111 from Amazon.  First three flashed fine.  Last one refused to flash
new client on port 443 from <IP_ADDRESS>:30868
ID: 0242416f68626d64366147393149465231d573656cd946df0ed77a2c37017f92f063cf2b90d615212bf4b6e3439851a749
PSK: 50a5c7431467e9b9eabbcbbb72305018ad3f91c578113460eac84e34e19ebcb5
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
Am I truly unlucky at getting one with a new psk or a change in chip in a box of 4?
smarthack-web.log
smarthack-psk.log
smarthack-wifi.log
smarthack-mqtt.log
smarthack-udp.log

Sounds like you got lucky, not unlucky, as I just purchased a set of four Gosund WP3's and most if not all are on the new PSK (haven't checked them all yet). See here for more info: https://github.com/ct-Open-Source/tuya-convert/issues/483

Indeed, whether you consider it unlucky that one was blocked, or lucky that three worked, it looks like this is the case.
I'd prefer to see the glass half full. Or in this case three quarters.
The fourth is probably still flashable the old fashion way, over serial wire.

Indeed, whether you consider it unlucky that one was blocked, or lucky that three worked, it looks like this is the case.
I'd prefer to see the glass half full. Or in this case three quarters.
The fourth is probably still flashable the old fashion way, over serial wire.


feat: listing export

Pull Request Template
Issue Overview
This PR addresses #1525

[x] This change addresses the issue in full
[ ] This change addresses only certain aspects of the issue
[ ] This change is a dependency for another issue
[ ] This change has a dependency from another issue

Description
This PR adds a new endpoint "listings/csv" which generates two CSVs: one capturing listing data and one unit data. When an admin clicks export, these two CSVs are then zipped together and downloaded as one .zip file. This PR also includes sucess and error messaging along with tests to ensure that behavior.
Column Info: https://docs.google.com/spreadsheets/d/1RrYNnkAdG4QPyVBC8yG1svqPaLt0V4qVQMzQgHUEIjY/edit#gid=0
How Can This Be Tested/Reviewed?
This can be tested by running this locally and clicking the Export to CSV button after signing in on the partners side. You can also go to chrome's throttler and set it to offline and then click the button to test the error messaging.
Checklist:

[x] My code follows the style guidelines of this project
[ ] I have added QA notes to the issue with applicable URLs
[x] I have performed a self-review of my own code
[ ] I have reviewed the changes in a desktop view
[ ] I have reviewed the changes in a mobile view
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have assigned reviewers
[x] I have run yarn generate:client and/or created a migration if I made backend changes that require them
[ ] I have exported any new pieces added to ui-components
[ ] My commit message(s) is/are polished, and any breaking changes are indicated in the message and are well-described
[ ] Commits made across packages purposefully have the same commit message/version change, else are separated into different commits

Reviewer Notes:
Steps to review a PR:

Read and understand the issue, and ensure the author has added QA notes
Review the code itself from a style point of view
Pull the changes down locally and test that the acceptance criteria is met
Also review the acceptance criteria on the Netlify deploy preview (noting that these do not yet include any backend changes made in the PR)
Either explicitly ask a clarifying question, request changes, or approve the PR if there are small remaining changes but the PR is otherwise good to go

On Merge:
If you have one commit and message, squash. If you need each message to be applied, rebase and merge.

One more visual note - looks like the success toast is not aligned with the content. This update to that alert should do the trick:
<div className="flex z-50 flex-col items-center justify-end">             <SiteAlert               dismissable               timeout={5000}               alertMessage={{ message: t("listings.exportSuccess"), type: "success" }}               sticky               className={"mr-0"}             />           </div>

Thank you for the detailed review @emilyjablonski 🗻  I believe I have addressed all of the comments above with the exception of the toast piece since we decided to maintain alignment with the User Export. Let me know what you think!


Improve testerina Documentation

We need to do the $subject. Some key information is missing in the ReadME file

This was fixed in the testerina rewrite.


Clicking relayer logs leaves the scrollbar halfway up

What's your CLI version?
0.83.7
Description & steps to reproduce
https://www.loom.com/share/2a6ba22a3f2e42af91ef4fcfcd37690c
Means the user has to manually scroll to the bottom or click the scroll-to-bottom button whenever they view the logs.
My guess is this appears when there are a lot of logs
Desired behavior
When clicking the logs, the scrollbar is already at the bottom
What is the severity of this bug?
Painful; this is causing significant friction in my workflow.

Same thing is happening on the Starlark output:
https://www.loom.com/share/6d692e4a352e4b90a878fa2353d9572e @ 0:15

FWIW it doesn't seem to be happening on the service logs anymore

Service logs redesign with new scroll should've fixed this


Chakra is broken

...and I don't think at this point it's worth fixing.
📦 jsvu v2.1.0 — the JavaScript engine Version Updater 📦
✔ Read OS from config: linux64
✔ Read engines from config: chakra
❯ Finding the latest Chakra version…
✖ RequestError: getaddrinfo ENOTFOUND chakratestx.file.core.windows.net

Fixed probably in https://github.com/CanadaHonk/jsvu/commit/7ce8e8474328f7716a5852c90922edf058ff1efd + https://github.com/CanadaHonk/jsvu/commit/be2ccb8d8516c645dd9f9b547fb0d1ec2f0969e9


Correct way of storing values between calls

I am trying to test an API which requires a JWT token as the authorization mechanism.
The flow is the following:

Call endpoint to login -> JWT from body
Call endpoint to get user -> Get JWT from last request and place it in headers

The current logic I am doing is the following one:

Make first request and store it in the Notepad

Given(/(.*) signs in/, (actorName: string) =>
  actorCalled(actorName).attemptsTo(
    Send.a(
      PostRequest
        .to('/url')
        .with({
          account: {
            email: 'whatever',
            password: 1234
          }
        })
    ),
    Ensure.that(LastResponse.status(), equals(201)),
    TakeNote.of(LastResponse.body())
  )
);

Extract JWT token from latest request and reuse it in the next request

Given(/(.*) post something in API/, async (actorName: string) => {
  const actor = actorCalled(actorName);
  const bearer = (await Note.of(LastResponse.body()).answeredBy(actor)).auth.access_token;

  return actor.attemptsTo(
    Send.a(
      PostRequest
        .to('/user')
        .with({
          test: 1234
        })
        .using({
          headers: {
            Authorization: `Bearer ${bearer}`
          }
        })
    ),
    Ensure.that(LastResponse.status(), equals(201))
  )
});

This is working just fine, but I am not sure if it is the proper way of doing so as here I am forcing the extraction of the bearer token from a previous request using  const bearer = (await Note.of(LastResponse.body()).answeredBy(actor)).auth.access_token;.
The problem here is that if in the step number 2 I also need to store something in the Notepad for usage in another API call, how should I retrieve again the bearer token if I override it with LastResponse.body()? Should it be stored in a variable or a class like an Ability to remember the JWT token?
Thanks!

Hey @AlexRex, check out this example and look at Question#map to extract the access token from a response body.
Hope this helps!
Jan


Repo guidelines vs Organisation guidelines?

It seems as though, while certain repos have guidelines specific to the repo (e.g., in 'Playground' try to break things), there are also guidelines that may be common across repos (e.g., our open-course philosophy and our thoughts on outside collaboration #31).

Is there a standard way to set guidelines for a whole organisation?
If not, what's our best course of action to avoid redundancy yet make clear our organisation's guidelines?

One solution could be to have 'Syllabus' as the main guide and link to it where necessary. In such a case the contributing.md of each repo would simply build on top of Syllabus/contributing.md

The same question could be applied to Code_of_Conduct as  I imagine we want to have the same code of conduct across all projects. In addition to using the Syllabus as the main guide, we could also have an entire repo for contributing guidelines or code of conduct. (This is how I did my Code of Conduct for Coding Train.
I think a good start is your suggestion, use Syllabus/CONTRIBUTING.md as the main guidelines and have CONTRIBUTING.md in other repos point back to it along with specific info about particular repos.

I'll leave this open for a little bit longer, but noting here that this is in progress in #33!

I'm going to close this as resolved now that we have guidelines and code of conducts throughout the various repos. Of course we can open new issues and continue the discussion as needed!


Android NfcV transceive doesn't work, iOS works

Hello,
I'm having issues reading NFCV(ISO15693) tag with android. iOS transceive works fine, but android always fails - ` ex transceive fail - Tag was lost.)
Android:
      const tech =  NfcTech.NfcV;

      const resp = await NfcManager.requestTechnology(tech, {
          alertMessage: 'Ready to do some custom NfcV cmd!'
      });

      const resp1 = await NfcManager.transceive([0x20,0x20,0,0,0,0,0,0,0,0,0]);

      console.warn(resp1);

iOS:
    const tech = NfcTech.Iso15693IOS;
    const handler = NfcManager.getIso15693HandlerIOS();

    await NfcManager.requestTechnology(tech, {
      alertMessage: 'Ready to scan the tag',
    });

    const blockBytes: Array<number> = await handler.readSingleBlock({
      flags: Nfc15693RequestFlagIOS.HighDataRate,
      blockNumber,
    });

There is no documentation on android part how the NFCV technology api should be used. What am I doing wrong?

Turns out the proper way to read NfcV on android is:
    await NfcManager.requestTechnology(NfcTech.NfcV, {
      alertMessage: 'Ready to write some NFC tags!'
    });

    let tag = await NfcManager.getTag();
    const idBytes = tag.id
      .split(/(..)/g)
      .filter(s => s);
    idBytes.forEach((val, i, a) => a[i] = parseInt(val, 16));

    let res = await NfcManager.transceive([32,32,...idBytes,0]); // 32 - read and high speed flags, then follows tag id and last byte is the byte address you want to read

I think this will be quite useful as an example.

@lukebars it's awesome that you figure it out! Since its definitely helpful to others, would you mind put it into example and make a PR?

@whitedogg13 sure, I'll raise a PR in a day or two


Add simple translate

Add https://translate.google.com/manager/website/ to get simple + quick translations for people who don't happen to read English.
Should check these two check boxes
Automatically display translation banner to users speaking languages other than the language of your page.
Your page contains content in multiple languages.

Moved to CH


Extract output format to a class structure and add CLI parameter

add CLI format parameter with currently only one option (default)
implement default format as class
refactor rendering and optimise relative path & fatal handling
only sort lints if the output format requires this (future JSON format does not need this)

I intend to create another PR with the Dart JSON output as follow up, but splitting this in a separate PR for easier review.
No test changes, output stays the same for now.

I added the JSON output format to this PR. With the class separation it is pretty clean and should be fine to review.

Overall LGTM, with some minor API/readability issues

Should be good to go

Great, thanks!


lexer: whitespace between operators

Issue
Something like true && !false will lex to ((Token.NAME, "true"), (Token.OPERATOR, "&&!"), (Token.NAME, "false")).
&&! is a not a valid operator.
Solution
Don't ignore whitespace between operators.

fixed in 4da35c3


Rate_5_model fails due to autodiff issue

the rand(Binomial(n, sampledval)) calls fail as Binomial can't accept autodiff tracker types.

Also applied to GLMM1_model

also lotka_volterra and one_comp_mm_elim_abs


Use node 20

Use node20
Fixes #3

Hi @ishworkh any thoughts about merging this in? I'm continually getting warnings in my GitHub actions because of this. Pretty soon I'm going to have to figure out a different solution.

Hi @ishworkh any thoughts about merging this in? I'm continually getting warnings in my GitHub actions because of this. Pretty soon I'm going to have to figure out a different solution.

Hi, thanks for the PR here too. As with "-download" action, I have already implemented the fix in a different PR (which has been released). Therefore I think we can safely close this PR. Any objections ? :)

Sounds good to me!


XML namespace

Hello,
Are you still using this package?
I was trying to use it with ETS 5 and discovered that exists a new schema "http://knx.org/xml/project/20", the version 2.0 of the XML schema.
Do you intend to update the repo? Does it exist other framework for go with this same propose ?
I could try to help updating to include the new schema
Regards,
Vitor

I do not intend to update this repository for schema version 2.0.
If you chose to fit this package to the new version, I would gladly review a PR.

I do not intend to update this repository for schema version 2.0.
If you chose to fit this package to the new version, I would gladly review a PR.


Not working using Scriptify instead of Scriptish.

It would be a nice to have, but not necessary.

The addon seems to dislike installing scripts from github - as well as my 1 enormous line of css.


PageList.Mvc Namespace missing in <IP_ADDRESS>-beta

I experienced the same behavior installing the beta as was described here: https://github.com/ernado-x/X.PagedList/issues/8
After the NuGet install the X.PagedList.Mvc .dll was no longer referenced in my project, the PagedList.Mvc namespace was compl As previously mentioned, the .dll did exist in a net45 directory and manually adding the reference addressed the issue. Perhaps the nuget bundling is the culprit?

I update packge: https://www.nuget.org/packages/X.PagedList.Mvc/
Please check new version.


Legacy Transition Code for Logs

What's New?

Fix a bug where legacy format logs from FBOS cause a crash in the UI.

Coverage increased (+0.005%) to 89.944% when pulling ca0cde6f846ad191cc22dbfe463c6cff4fcdd838 on RickCarlino:logs_part_iii into 93ff7ee770f025571a049e7f07789cd36241a7d2 on FarmBot:staging.


A FacilityMatch is not created when all pending matches are rejected

Overview
When all pending matches for a FacilityListItem are rejected, a new Facility is created, however a FacilityMatch row is not being created, resulting in the contributor not appearing on the facility detail page.
Expected Behavior
The facility detail page for a facility created after rejecting all pending matches displays the name of the contributor.
The tests are updated to verify that this works.
Actual Behavior
The facility detail page for a facility created after rejecting all pending matches does not show the name of the contributor.
Steps to Reproduce
NOTE: These specific steps depend on #248 and  #253

./scripts/manage resetdb
Register an account
Upload  src/django/api/management/commands/facility_lists/13.csv
Fully process the CSV

./scripts/manage batch_process --list-id 15 --action parse
./scripts/manage batch_process --list-id 15 --action geocode
./scripts/manage batch_process --list-id 15 --action match

Browse the list http://localhost:6543/lists/15?page=1&rowsPerPage=100
Reject the "Workfield Knitwears" match and confirm the rejection
Click the "Workfield Knitwears" link to browse the facility detail page

Demo

I updated the issue to include a line about having a test to verify that the code works.


Test failures do not display accurate test line numbers in stack trace

Expected behaviour
The line number in a test file referenced when a test fails is correct
Actual behaviour
The line number reported is incorrect, a virtual line number generated from Babel
Steps to reproduce the behaviour

Go to https://github.com/karma-runner/karma/blob/e36ba6c1d4cad4fc321f3376129b329fe663068d/test/unit/browser.spec.js#L30
Change .to.equal(fullName) to .to.equal(fullName) + '1'
Observe the line number reported

This likely is a simple configuration problem with Babel or one of the grunt plugins

I tried to replicate this but couldn't. Your change didn't throw an error so I changed it to this:
.to.equal(fullName + '1')
And then it gave me the correct line number (30):
at Context.<anonymous> (test/unit/browser.spec.js:30:33)
I'm on the latest commit in the master branch, running npm test

I was able to replicate this on os x with node v6.9.2 - it also incorrectly tells me the test failed on line 32 but the actual failure line is 30.


bump leaflet, esri leaflet, geocoder

i went on a bit of a tangent trying to debug ArcGIS/arcgis-for-developers#3178
fixed

changed default basemap to Topographic
esri-leaflet and esri-leaflet-geocoder bumped to 1.x
moved the above, and geotrigger-js from git submodules to devDependencies
moved basemap control on top of geosearch so suggestions would stop obscuring the other control
updated doc and changelog
fixed package.json license tag to prevent npm install nag

q's

i'm just assuming npm dependencies are nicer than submodules.  happy to retool if i'm wrong.
the geotrigger-editor.css got updated on its own.  i assume its because a newer version of one of the css build tools does its thing a touch differently.
calling grunt dev doesn't actually watch and rebuild when changes are made in src/.  (i didn't do anything about that).
calling grunt build works fine, but throws a warning about the code in geotrigger-js.  (i didnt do anything about that either).
.png resources aren't loaded in the example/default/ (i didn't do anything about that either)

my sincere apologies, and best of luck

what's there to apologize for friend?

mistakes made long ago

as per @paulcpederson and my conversation:

moved everything possible to CDN and got rid of both submodules and npm dependencies
bumped grunt-contrib-uglify to actually get the build working
caught a broken relative path in the CSS (this fixed the /examples/
admitted that i don't have enough knowledge or interest to debug whats wrong with the proxy sample
bumped the changelog, as i think merging this definitely warrants tagging a release.

after everyone's happy, i'll port into the developer site.


libs/libc/arm: use builtin routines instead of aliases of __aeabi_mem*

Summary
libs/libc/arm: use builtin routines instead of aliases of __aeabi_mem*
Signed-off-by: chao an<EMAIL_ADDRESS>Impact
N/A
Testing
armclang/clang/gcc

@xiaoxiang781216 do you recall why it was originally added? Was it because we used no-builtin flag?

@xiaoxiang781216 do you recall why it was originally added?

Sorry, I can't remember why add these functions:(. But since these functions block armclang LTO link, we can remove these functions first, and watch any bad feedback. Anyway, it's always be good to prefer the implementation provided by compiler.

Was it because we used no-builtin flag?

https://github.com/apache/incubator-nuttx/pull/5971 is related to no-builtin, not __aeabi_memxxx.

Since this change simply remove built-in functions implemented on ARM, Let's ignore macOS false alarm.


Add cars next to the City Hall

I added cars next to the City Hall as following.

good work !!
Thank you !!