hash.verification test failure on ppc64/s390x

Firstly, I had to modify the CMakeLists.txt to remove the -march=native before the C++14 check which would fail on ppc64(le)/s390x.
Secondly, I get this test error in hash.verification on ppc64 and s390x. I'm guessing this is because of some little-endian assumption somewhere:
/builddir/build/BUILD/xtl-0.4.4/test/test_xhash.cpp:157: Failure
      Expected: actual
      Which is:<PHONE_NUMBER>
To be equal to: res
      Which is: 520960004

Thanks for the report. Indeed there seems to be an endianess issue.

Could perhaps some of these warnings be relevant?
In file included from /builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:15:
/builddir/build/BUILD/xtl-0.4.13/include/xtl/xhash.hpp: In function 'std::size_t xtl::detail::murmur_hash(const void*, std::size_t, std::size_t) [with long unsigned int N = 4; std::size_t = long unsigned int]':
/builddir/build/BUILD/xtl-0.4.13/include/xtl/xhash.hpp:68:33: warning: conversion to 'std::size_t' {aka 'long unsigned int'} from 'int' may change the sign of the result [-Wsign-conversion]
                 hash ^= data[2] << 16;
                         ~~~~~~~~^~~~~
/builddir/build/BUILD/xtl-0.4.13/include/xtl/xhash.hpp:70:33: warning: conversion to 'std::size_t' {aka 'long unsigned int'} from 'int' may change the sign of the result [-Wsign-conversion]
                 hash ^= data[1] << 8;
                         ~~~~~~~~^~~~
/builddir/build/BUILD/xtl-0.4.13/include/xtl/xhash.hpp: In function 'std::size_t xtl::detail::murmur_hash(const void*, std::size_t, std::size_t) [with long unsigned int N = 8; std::size_t = long unsigned int]':
/builddir/build/BUILD/xtl-0.4.13/include/xtl/xhash.hpp:105:48: warning: unsigned conversion from 'int' to 'std::size_t' {aka 'long unsigned int'} changes value from '-8' to '18446744073709551608' [-Wsign-conversion]
             const char* end = data + (length & ~0x7);
                                                ^~~~
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp: In function 'void xtl::rand_p(void*, int)':
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:60:34: warning: conversion to 'uint32_t' {aka 'unsigned int'} from 'int' may change the sign of the result [-Wsign-conversion]
             blocks[0] = std::rand();
                         ~~~~~~~~~^~
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp: In function 'void xtl::flipbit(void*, int, uint32_t)':
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:75:24: warning: conversion to 'int' from 'uint32_t' {aka 'unsigned int'} may change the sign of the result [-Wsign-conversion]
         int byte = bit >> 3;
                    ~~~~^~~~
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:79:21: warning: conversion from 'int' to 'uint8_t' {aka 'unsigned char'} may change value [-Wconversion]
             b[byte] ^= (1 << bit);
             ~~~~~~~~^~~~~~~~~~~~~
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp: In instantiation of 'uint32_t xtl::verification_test(F, int) [with F = long unsigned int (*)(const void*, long unsigned int, long unsigned int); uint32_t = unsigned int]':
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:155:77:   required from here
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:29:42: warning: conversion to 'size_t' {aka 'long unsigned int'} from 'int' may change the sign of the result [-Wsign-conversion]
         std::memset(hashes, 0, hashbytes * 256);
                                ~~~~~~~~~~^~~~~
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:30:29: warning: conversion to 'size_t' {aka 'long unsigned int'} from 'int' may change the sign of the result [-Wsign-conversion]
         std::memset(res, 0, hashbytes);
                             ^~~~~~~~~
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:37:56: warning: conversion to 'std::size_t' {aka 'long unsigned int'} from 'int' may change the sign of the result [-Wsign-conversion]
             *reinterpret_cast<std::size_t*>(hashes + i * hashbytes) = f(key,i,256-i);
                                                      ~~^~~~~~~~~~~
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:41:66: warning: conversion to 'long unsigned int' from 'int' may change the sign of the result [-Wsign-conversion]
         *reinterpret_cast<std::size_t*>(res) = f(hashes,hashbytes*256,0);
                                                         ~~~~~~~~~^~~~
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:45:80: warning: conversion to 'uint32_t' {aka 'unsigned int'} from 'int' may change the sign of the result [-Wsign-conversion]
         uint32_t verification = (res[0] << 0) | (res[1] << 8) | (res[2] << 16) | (res[3] << 24);
                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp: In instantiation of 'bool xtl::sanity_test(F, int) [with F = long unsigned int (*)(const void*, long unsigned int, long unsigned int)]':
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:162:9:   required from here
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:112:43: warning: conversion to 'size_t' {aka 'long unsigned int'} from 'int' may change the sign of the result [-Wsign-conversion]
                     std::memcpy(key2,key1,len);
                                           ^~~
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:114:69: warning: conversion to 'long unsigned int' from 'int' may change the sign of the result [-Wsign-conversion]
                     *reinterpret_cast<std::size_t*>(hash1) = f(key1,len,0);
                                                                     ^~~
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:119:42: warning: conversion to 'uint32_t' {aka 'unsigned int'} from 'int' may change the sign of the result [-Wsign-conversion]
                         flipbit(key2,len,bit);
                                          ^~~
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:120:73: warning: conversion to 'long unsigned int' from 'int' may change the sign of the result [-Wsign-conversion]
                         *reinterpret_cast<std::size_t*>(hash2) = f(key2,len,0);
                                                                         ^~~
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:122:52: warning: conversion to 'size_t' {aka 'long unsigned int'} from 'int' may change the sign of the result [-Wsign-conversion]
                         if(std::memcmp(hash1,hash2,hashbytes) == 0)
                                                    ^~~~~~~~~
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:127:42: warning: conversion to 'uint32_t' {aka 'unsigned int'} from 'int' may change the sign of the result [-Wsign-conversion]
                         flipbit(key2,len,bit);
                                          ^~~
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:128:73: warning: conversion to 'long unsigned int' from 'int' may change the sign of the result [-Wsign-conversion]
                         *reinterpret_cast<std::size_t*>(hash2) = f(key2,len,0);
                                                                         ^~~
/builddir/build/BUILD/xtl-0.4.13/test/test_xhash.cpp:130:52: warning: conversion to 'size_t' {aka 'long unsigned int'} from 'int' may change the sign of the result [-Wsign-conversion]
                         if(std::memcmp(hash1,hash2,hashbytes) != 0)
                                                    ^~~~~~~~~

Actually, seems to be a limitation of MurmurHash2.

It may be possible to use the MurmurHash3 implementation by Shane Day that's used in the R digest package, or maybe xxHash, which both claim to be more portable.

@QuLogic thanks. Indeed, MurmurHash3 gives the same results regardless of the architecture.
However, for our use of murmurhash2, we don't really need it to give the same results on all machines, and modifying the test to check for the expected result on big endian architecture should be sufficient.


Polymer 2.0

Any plans of a polymer 2.0 element that uses this?
https://github.com/SortableJS/polymer-sortablejs
https://github.com/bmwalters/polymer-sortablejs/tree/2.0-preview
These ones simply does not work for polymer 2.0

You can try my fork
$ bower install myfrom/polymer-sortablejs#master
It works fine except on phones. I'm looking into it.


Add-Content and Out-File -Append can fail quietly, seemingly connected to cross-thread concurrency

Note:

I don't know what other cmdlets are affected. Update: at least Out-File -Append is affected too.

A common use case where the problem can surface is in the context of ForEach-Object -Parallel (while the use of Add-Content in parallel threads requires explicit synchronization, neglecting to do so should at least report the  failure to write.)

Steps to reproduce
$tempFile = New-TemporaryFile
Write-Verbose -vb "Waiting for an Add-Content call to fail..."
$Error.Clear()
while ($true) {
  Remove-Item -ea Ignore $tempFile
  # Let multiple threads try to update Add-Content simultaneously.
  1..100 | ForEach-Object -Parallel { Add-Content $using:tempFile -Value $_ -ErrorAction Stop; if (-not $?) { Write-Warning $_.ToString() } }
  # On occasion, the file ends up with fewer than 100 lines.
  $countWritten = (Get-Content $tempFile).Count
  if ($countWritten -ne 100) {
    Write-Verbose -vb "$countWritten lines were written."
    # If fewer lines were written, an error should have been reported.
    $Error.Count | Should -BeGreaterOrEqual 1
  }
}
Remove-Item $tempFile

Expected behavior
The tests should run indefinitely, because the Add-Content calls should either all succeed or those that fail should report an error.
Actual behavior
A test eventually (may take a while) fails, because an Add-Content calls fails silently; e.g.:
VERBOSE: 99 lines were written.
InvalidResult:
Line |
  13 | $Error.Count | Should -BeGreaterOrEqual 1
     | Expected the actual value to be greater than or equal to 1, but got 0.

Environment data

PowerShell Core 7.2.0-preview.1

@mklement0 Can you catch errors in ForEach-Object -Parallel scriptblock? Maybe add Get-Error?

I think really Get-Content does not fail. It write all values in the file but we have a race condition sometimes - some values are overwritten by subsequent ones.

It's definitely a race condition.
Some failure of Add-Content is involved and two possible reasons come to mind:

The write operation fails, but the failure isn't reported.
File content is cached (which seems unlikely) and on writing there's a failure to recognize that the file has been modified by another thread.

Either way, a fix is required.

Also note that the problem may not be cmdlet-specific, because Out-File -Append is affected too.

I doubt we can fix this since too many things in PowerShell are not thread-safe.
Perhaps the best option is to write this in the documentation if it is not already there.
@PaulHigin Could you please share your thoughts?

Yes, PowerShell cmdlets are not and were never intended to be multi-threaded safe.  Users must beware of using cmdlets in multiple threads, whether via foreach -parallel or PowerShell API.  Same as with any non-multi-threaded-safe .NET object.

Agreed in general, @PaulHigin, but while race conditions on in-memory data (e.g., a non-concurrent collection) cannot be prevented, we are talking about concurrent file access here.
And it seems to me that failure to update a file being written to by someone else should be reported as such - the current, quiet failure is insidious. (Note that this is different from expecting the concurrency to be managed automatically - that is indeed not the goal here.)

Are you sure it's actually failing to write? It could be successfully writing input of similar length to the same offset in the file.

Safe solution was to mark cmdlets which is a thread-safe and allow in ForEach-Object -Parallel only such cmdlets. But in any case we can not make the ForEach-Object -Parallel fully thread-safe.
As for Add-Cmdlet, it has thick wrapper code and I guess it's not so easy to do it thread-safe.

That's possible, @SeeminglyScience, but that is still a failure to synchronize access to a file for writing, which is something that should be addressed in general, irrespective of cross-thread use, as it also applies cross-process.
Therefore, @iSazonov, this isn't about thread safety per se. It's about not allowing any other entity - whether thread or process - write access to a file while it is being written to.

Not sure if I should create a separate issue for this--seemed similar enough to the main issue.
Redirection/Writing to file fails in ForEach block within function
I'm a relative beginner, so might be a basic error--that said, *this same function worked earlier, and worked on WindowsPowerShell (5.1)
function makeDirective([string]$directiveFile, $files) {

        if (Test-Path $directiveFile) {
            throw "File $directiveFile Exists"
        }
        ForEach ($file in $files) {
            "file $($file.Name)" >> $directiveFile
        }
}

# Files is obviously not empty
$files = Get-ChildItem <file_pattern>

makeDirective 'manifest.txt' $files

No errors, no warnings--but no file is outputted.
The same redirection line in the function works when I type it into a shell, or as a line in a script.
I'm using Version 7.1.4

That would likely be a completely separate issue. FWIW I tried your function on 7.2.0-preview9 and it works as expected. I would guess something else is going on in your case, though I don't know what exactly.

Now .Net 6.0 has get new thread-safe file IO API.
https://devblogs.microsoft.com/dotnet/file-io-improvements-in-dotnet-6/#thread-safe-file-io
but I doubt that we will be able to use this.


Order by Relations not work

Bug description
Order by Relations not work in version 2.21.2
How to reproduce
My code:
prisma.product.findMany({
    orderBy: {
         analytics: {
             id: 'acs'
         }
      }
})

Type '{ analytics: {}; }' is not assignable to type 'Enumerable<ProductOrderByInput>'.
  Object literal may only specify known properties, and 'analytics' does not exist in type 'Enumerable<ProductOrderByInput>'

Expected behavior
No response
Prisma information
model Product {
  id               Int            @id @default(autoincrement())
  analytics       Analytic[]    @relation("fk_product_analytic")
  @@map("products")
}

model Analytic {
  id                        Int                   @id @default(autoincrement())
  product_id                Int
  product                   Product               @relation("fk_product_analytic", fields: [product_id], references: [id])

  @@map(name:"product_analytics")
}

Environment & setup

Node: 14.16.0

Prisma Version
2.21.2

Does this work in a more recent version of Prisma?

Hi @NguyenKyThinh94,
Not sure if you’ve already managed to get around your issue (or if this will be helpful to anyone else reading this) but I was also seeing this error in v2.30.3.
In my situation, when I actually ran my app the order by relation was working but I was seeing the above type error. To get rid of the error I just cast my object to the expected type and it seemed to be happy enough with it.
So in your example, something along the lines of:
const orderBy = { analytics: { id: ‘acs’ } } as ProductOrderByInput
prisma.product.findMany({ orderBy })

Thanks

instead of using orm, i wrote SQL query !!
Many thanks for supports

I'm able to order by relations in v3.14
Not sure if trying to order by 'acs' instead of the correct 'asc' has anything to do with the issue.
    const cyProjects = await db.projects.findMany({
        select: {
          ProjectNumber: true,
          ProjectName: true,
          Clients: {
            select: {
              ClientName: true,
              ClientId: true,
            },
          },
        },
        where: {
          ProjectNumber: { startsWith: '22' },
        },
        orderBy: {
          Clients: { ClientId: 'asc' },
        },
      })

Please try this again with the latest version of Prisma. This preview feature has been stabilized since the version that you using. @NguyenKyThinh94

There are a few things in this issue...
First, please upgrade to the latest Prisma version (4.3.1 currently) to use the feature.
Second, the only ordering you can do from a many side of the relation is by _count, so this would work:
await prisma.product.findMany({
  orderBy: {
    analytics: {
      _count: "asc",
    },
  },
});

Which translates to the following SQL:
SELECT "public"."products"."id"
FROM "public"."products"
         LEFT JOIN (SELECT "public"."product_analytics"."product_id", COUNT(*) AS "orderby_aggregator"
                    FROM "public"."product_analytics"
                    WHERE 1 = 1
                    GROUP BY "public"."product_analytics"."product_id") AS "orderby_0_Analytic"
                   ON ("public"."products"."id" = "orderby_0_Analytic"."product_id")
WHERE 1 = 1
ORDER BY COALESCE("orderby_0_Analytic"."orderby_aggregator", $1) ASC
OFFSET $2

But you can't really order by a specific column from the many side, that only works from the one side:
await prisma.analytic.findMany({
  orderBy: {
    product: {
      id: "asc",
    },
  },
});

And this translates to the following SQL:
SELECT "public"."product_analytics"."id", "public"."product_analytics"."product_id"
FROM "public"."product_analytics"
         LEFT JOIN "public"."products" AS "orderby_0_Product"
                   ON ("public"."product_analytics"."product_id" = "orderby_0_Product"."id")
WHERE 1 = 1
ORDER BY "orderby_0_Product"."id" ASC
OFFSET $1

So, from the many side, the parent can have more than one children. There would not really be a good way to order the parents by the ids of more than one children. From the one side, there can be at most one parent. Now we have a way to order by a column of this parent.

Hello @pimeys ,
So, how do you make this select work below in Prisma?
SELECT ch.* FROM challenges ch
JOIN user_challenges uc
ON uc.challenge_id = ch.id
WHERE uc.user_id = '************'
AND uc.completed = true
AND uc.is_current = true
ORDER BY uc.end_date DESC

My model looks like this (reduced).
model Challenge {
...
user_challenges                     UserChallenges[]
...
}
model UserChallenges {
...
user_id                 String                                  @db.Uuid
completed           Boolean                               @default(false)
is_current            Boolean                               @default(true)
end_date             DateTime?                           @db.Timestamptz(6)
challenge            Challenge                            @relation(fields: [challenge_id], references: [id])
...
}

And this here doesn't really work.
const challengesFound = await prisma.challenge.findMany({
  where: {
    user_challenges: {
      some: {
        user_id,
        completed: true,
        is_current: true,
      },
    },
  },
  orderBy: {
    user_challenges: {
      end_date: 'desc',
    },
  },
});

But look, I'm restricting so that there's only one result of the JOIN. Is it really not an alternative? (Just doing the raw query)

@fabriciosautner I believe you can do it reverse though user_challenges making it distinct by challengeId and ordering it, then selecting the challenge from user_challenges and returning the values in a map
const result = await prisma.user_challenges.findMany({
  // In order to only get one `challenge` per `user_challenges`
  distinct: 'challengeId',

  // order the `user_challenges.end_date` by desc
  orderBy: {
    end_date: 'desc',
  },

  // includes the `challenge` in the query
  select: {
    challenge: true,
  },

  // your query
  where: {
    user_id,
    completed: true,
    is_current: true,
  },
});

const challengesFound = result.map(r => r.challenge)


R4i Gold 3DS no longer sold

atleast on nds-card that is, but i think a small note should just reflect that to people. much thank

From what I can tell, the r4i Gold 3DS RTS is still being sold, yet it is hidden on nds-card, meaning that you can still buy it through the link found in the guide, which is: http://www.nds-card.com/ProShow.asp?ProID=149
That's the only way (from what I can tell) in order to get access to its product page, which allows you to buy it.

even if you get access to the product page, i have heard that they just ship the "plus" variant of the card instead which is preflashed


Make the lifetime in Scope<'env> invariant

Fixes #225
I made sure that the provided example does not compile anymore.

I'll merge this early and do a minor version jump because it's a rather serious issue.
bors r+


helm upgrade fails if deployment strategy type changes

Output of helm version:
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"clean", BuildDate:"2018-10-24T06:54:59Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
Minikube
If I have a deployment template like:
kind: Deployment
apiVersion: apps/v1beta2
metadata:
  name: prometheus-server
spec:
  replicas: 1

  strategy:
    type: RollingUpdate

  template:
    spec:
      containers:
      - name: server
        image: prom/prometheus:v2.2.1

And replace type: RollingUpdate with type: Recreate, the helm upgrade will fail:
Error: UPGRADE FAILED: Deployment.apps "prometheus-server" is invalid: spec.strategy.rollingUpdate: Forbidden: may not be specified when strategy `type` is 'Recreate'

If I use kubectl apply -f, it works fine.

Workaround is to set rollingUpdate: null.

Where do you set this?

@dannybitgo
  strategy:
    type: RollingUpdate
    rollingUpdate: null

@jsravn Thank you

helm upgrade --install is expected to be idempotent. This is another case when it will fail.

Do you observe this behaviour with helm 3? The 3-way merge patch strategy should solve this design issue.

@bacongobbler We're still on 2.x. Is 3.x a drop-in replacement for 2.x, in terms of using the same YAML templating syntax and the same CLI parameters?

@Nowaker It is pretty much backward compatible with chart format and CLI. Have a look at Helm docs on changes and Helm 3 blog for more details.

@hickeyma Thanks for your guidance, will take a look!

closing as inactive.

It's still an issue on helm 3 though.

Can you demonstrate?


Every picture has wrong colours on IOS 17

Tested on "1.2.0-beta01", "1.1.8"
Image type does not matter.
Image name modifiers: (_orig) are added
On IOS 16.4 everything works fine.

same problem, and ios doesnot see .svg files

same problem, and ios doesnot see .svg files

have same problem now, did you succeed to solve it?

I have a very small project, I migrated it to moko-resources in 1 day

Fixed in https://github.com/Skeptick/libres/releases/tag/1.2.0


Replace read_byte with gets

This commit changes byte_delimiter to string_delimiter.
(1) For now, string_delimiter is defined as a Char. Since gets supports
strings as delimiters, in the future this could become a String for even
more flexibility.
(2) If any backward compatibility should be preserved, please make another
commit to add it.
(3) All specs pass, except this one (unrelated to this PR):
Failures:

  1) Crystalizer::YAML Slice(UInt8) serializes
     Failure/Error: Crystalizer::YAML.serialize(object).should eq string

       Expected: "--- !!binary 'YWJj\n\n  '\n"
            got: "--- !!binary 'YWJj\n\n'\n"

     # spec/yaml_spec.cr:7

Finished in 6.66 milliseconds
128 examples, 1 failures, 0 errors, 0 pending

Failed examples:

crystal spec spec/yaml_spec.cr:157 # Crystalizer::YAML Slice(UInt8) serialize

But this happens in my case always (not related to this PR) on all Crystal versions I tried (0.35 and up).

Yes it already happened in the past to me this kind of YAML issue, it is due to the libyaml version and/or the Crystal version.


Specify Domain for COMBINED_PEM

Hi Kereis :-)
    environment:
      DOMAIN: example.com,example.org,example.net,hello.example.in
      COMBINED_PEM: my_concatted_file.pem

Could you add the ability to Specify for which domain the cert-dumper creates a combined pem?
I have multiple domains for different usecases and services, where i share the certificates.
All except one of them uses a key and cert and only one (3cx) needs a combined certificate :-)
Need the same certificates for an ssl offloading instead of an sni proxy.
And yes, the workaround is to simply spin up a second cert-dumper instance.
So whatever you say, if a second cert-dumper instance is "The way to go", like if you planned that for such situations, then i'll do a second one.
If not and you can implent that feature, would be great either.
Thank for you work btw, cert-dumper works great!
But i do have a second question, somewhat when traefik regenerates certificates, cert-dumper doesn't dump the new ones.
Or at least not in a reasonable timeframe, like 1h.
But dumps instantly if i restart the container.
Do i miss there sth or is the timeframe longer?
Cheers

Hi @Ramalama2,
thank you very much for your feedback. :) I'm glad this tool helps you.

Could you add the ability to Specify for which domain the cert-dumper creates a combined pem?

Depends. Currently, the container should simply created combined PEM files for all domains. Does it matter that each domain's certificate and key are additionally combined, next to their original file?

And yes, the workaround is to simply spin up a second cert-dumper instance.

You could do that until then. If you don't need the restart functionalities of the image, you can also use the alpine version. Its size is much smaller than the default one with Docker in it.

But i do have a second question, somewhat when traefik regenerates certificates, cert-dumper doesn't dump the new ones.
Or at least not in a reasonable timeframe, like 1h.
But dumps instantly if i restart the container.
Do i miss there sth or is the timeframe longer?

I'm sorry, I haven't noticed that behaviour before. The dump script that lies within the image waits for any changes to your specified acme.json, and acts accordingly.
https://github.com/kereis/traefik-certs-dumper/blob/cc8fdeb437e31664ffb6490959b3dc121360f15a/bin/dump.sh#L441
It might be related to inotifywait, however I'm not sure.
Hope I could help you out!
Cheers

Hi @Ramalama2,
thank you very much for your feedback. :) I'm glad this tool helps you.

Could you add the ability to Specify for which domain the cert-dumper creates a combined pem?

Depends. Currently, the container should simply created combined PEM files for all domains. Does it matter that each domain's certificate and key are additionally combined, next to their original file?

And yes, the workaround is to simply spin up a second cert-dumper instance.

You could do that until then. If you don't need the restart functionalities of the image, you can also use the alpine version. Its size is much smaller than the default one with Docker in it.

But i do have a second question, somewhat when traefik regenerates certificates, cert-dumper doesn't dump the new ones.
Or at least not in a reasonable timeframe, like 1h.
But dumps instantly if i restart the container.
Do i miss there sth or is the timeframe longer?

I'm sorry, I haven't noticed that behaviour before. The dump script that lies within the image waits for any changes to your specified acme.json, and acts accordingly.
https://github.com/kereis/traefik-certs-dumper/blob/cc8fdeb437e31664ffb6490959b3dc121360f15a/bin/dump.sh#L441
It might be related to inotifywait, however I'm not sure.
Hope I could help you out!
Cheers

Jesus kereis, didn't thought that you're so nice :-)
About alpine and second container, thats exactly what im doing now and it works perfectly exactly as i wanted.
Otherwise big docker containers like debian/ubuntu based, doesn't take any additional space here anyway, no matter how much i spin up, thanks to zfs deduplication.
Just memory, but that's why im using alpine 😂
What i mean is anyway, spinning up multiple cert-dumper containers is actually in my mind a great solution, you can name them simply like your domains etc and they consume anyway almost no ressources.
About the second thing, if you could give me a bit time, till traefik regenerates the certificates, i could confirm or "deconfirm", if cert dumper dumps new certs on the certstorefile change. And how long it takes.
However something like inotify should actually react or execute your dumping script instantly.
Thing is, im not sure if i did something. In short if im the error or intofy 😂
That's why i need a bit time.
Otherwise i could simply edit with nano the certstore and delete the cert, then restart traefik. Should actually be the same as if traefik renews, but to be sure, ill wait a bit till traefik does it.
Especially because there is no one else reporting this issue.
Cheers and thank you!

Hey,
I'm going to close this issue for now.
Btw, about the issue you wrote regarding the certdumper not dumping certificates renewed by Traefik: Maybe this could be the same issue? https://github.com/kereis/traefik-certs-dumper/issues/130
Cheers!

Hey,
I'm going to close this issue for now. Btw, about the issue you wrote regarding the certdumper not dumping certificates renewed by Traefik: Maybe this could be the same issue? #130
Cheers!

Hey @kereis , im sorry for the late reply 🤦
Im not sure if this "bug" even exists. But im gonna check it tomorrow "triggering recreation" on traefik.
Just camed back from the holidays 🙈
I will reply in the other thread you mentioned then tomorrow.
Cheers ✌


Cache key length must be greater than zero.

./vendor/bin/composer-license-checker report --show-packages errors with "Cache key length must be greater than zero".
If it helps, the output until it failed was:
Looking up Apache-2.0 ...
Looking up MIT ...
Looking up  ...

One of our dependencies has "none" as the license name. It's actually an internal one, so I'll get that resolved. For your project, I guess you just need to handle that possibility.
This is what it looks like when a dependency has no license:
  15 => Dominikb\ComposerLicenseChecker\Dependency^ {#154
    -name: "***redacted***"
    -version: "dev-develop - none"
    -licenses: array:1 [
      0 => ""
    ]
  }

This then gets pushed into the array of dependencies in \Dominikb\ComposerLicenseChecker\ReportCommand::groupDependenciesByLicense as $grouped[""] => array
The license field is option, but recommended. https://getcomposer.org/doc/04-schema.md#license
This does feel more like we're misusing your tool, so feel free to close of course, but maybe it is also a good idea to handle this edge case as the license field is optional.


New Feature

The option to select which heaters are managed. I do not have a heated chamber and the gcode throws an error every time the plugin works.

Having the same issue here. Would love a configuration to disable heated chamber codes.


Fix constants.python_pgo_flag()

As constants._get_sys_config_params() returns a list (item 0 is for PY_CFLAGS and item 1 is for PY_CFLAGS_NODIST), constants.python_pgo_flag() always returns False. This MR fixes the bug by using " ".join() and it can now detect -fprofile-use.

Hi Julien,
This repo is marked as read-only. However, it is merged as of https://github.com/blackfireio/python-sdk/commit/a7e238aa21ab7782ee8c4fc1f02b39492ad3ff4a including your commit information.
Thanks :)

Hi Sümer,
Is there another repo where I should have posted this PR ?
Thanks :)


Removed Chow

The website is no longer online and the last commit to Github was in Dec 2016. The company is not currently active.
Chow - https://justchow.com | Bangalore, India | Food | - https://github.com/just-chow?language=haskell

Thanks for the update.


Image Displays in Preview But Not in the Android Emulator view

I'm doing the Kotin course at https://developer.android.com/codelabs/basic-android-kotlin-compose-composables-practice-problems?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-1-pathway-3%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-composables-practice-problems#4.
The "Compose Article" exercise displayed its image without an issue, but not the "Task Manager" exercise.  I copied your exact "Task Manager" code into Anroid Studio and ran the code.  The @Composable Preview showed the image and the text, but the Android emulators I chose showed only the text but not the image.  Any idea why?

Drop this issue.  I bumbled through it.

Close


ISPN-5436 Fix ClientClusterEventsTest random failures

The cause for the failures is the switch from REPL to DIST that happened in ISPN-5429.
When using DIST, keys associated with servers are needed to provide stronger guarantees and hence the tests have been amended to do so.
The failover test has been separated into another class to make it easy to run independently.
Previous random failures have been noticed in ClientClusterEventsTest, but these might be gone with this switch.

Looks good to me.

Maybe @wburns should have a look too.

Seems fine to me as well, just have the one question.

CI had 2 spotless runs already. A 3rd one is in progress. I believe this can be merged @wburns.

Pulling ...

Integrated in master and 7.2.x. Thanks @galderz !

Thanks @galderz & @anistor ! :+1:


Fix #1: type errors in Deno.

Seems like an easy enough fix? 🤞

Will this work if we add these lines of code directly to the mod.ts (Deno entrypoint) file?


Stop reloading after reconnect

Problem:
The server is started before webpack emits the initial changes and
built files are written to disk, causing the installed extension,
which is trying to reconnect, to reload without having files to load.
This caused an error in the extension, where it needs to be removed
and installed again.
Solution:
We stop reloading after reconnect. This shouldn't cause problems because
the server emits a reload signal after the files are initially built,
so even if there are any changes made to the code while the server was
not available, they will still be reloaded automatically.
Assumption:
Restarting the server is the only plausible scenario where connection
might be lost and changes are made to the code.
Fixes #51

After some testing I found out that the extension needs to reload after reconnect, otherwise it doesn't receive any of the reload messages. Therefore I'm closing this PR in favor of https://github.com/rubenspgcavalcante/webpack-extension-reloader/pull/60


App Not working with Vaadin 23.0.9

I keep getting a blank page with [object, Object] in it.
The error is: Type error cannot read properties of null (reading 'shadowRoot')
It seems that no example is working with Vaadin 23 and version 5.1.0. I've tried 14 with version 4.0.0 and everything is fine. I've tried Vaadin 22 (4.0.0) and everything worked as expected.
Thanks

Hello. I tested version 5.1.0 in a Vaadin 23.0.9 application and it works okay (see applayouttest.zip). If you're using Spring, please make sure you add com.flowingcode to the vaadin.whitelisted-packages property in your application.properties file.
Also we advice to run mvn vaadin:dance between every vaadin version change so node modules dependencies are update correctly.

Hello!
Thanks for the reply. Yes I've put com.flowingcode into the whitelisted-packages. I've tried with a brand new vaadin 23 install (todo demo). I will give your test a try later and let you know
Thanks for your time

Thank you very much for your help and the great addon. Seems that the problem was with the vaadin:dance. Didn't know about it.
Thanks!!!


Updates to help texts

This is just a cleaned up version of #4468 to make things easier to review
closes #4018
(thanks @1ec5 👍 )

Translators are going to experience a bit of inconvenience updating their translations in Transifex this time around, but future updates will go a lot more smoothly than before. I think we should blast out a message to translators that they can take a look at the iD source code if they’re missing translation memory.

Yes!  As soon as this merges, I'll announce to everyone that we need help with translations.  I'm not anticipating a need to release a new version of iD for a little while (maybe mid December?), so that will give everyone time to work on it.

Happy to say I just merged this 👍   This will make it so much easier to maintain and translate the help texts.
Thanks @manfredbrandl and @1ec5 for your help with this.. I will make some announcements to request translation help.


fix(generators): no module by default

Short description of what this resolves:
By default, generate will make a NgModule by default, Since we do not ship lazy loading by default, we should not generate this right now.
Changes proposed in this pull request:

setincludeNgModule to false for now.

@mhartington,
Thanks!
Thanks,
Dan

Why? :(
Is there some flag to turn it on?
ionic g page MyPage -ng

any update on how to generate a page including the module file?
didn't find it in any doc :/

nothing right now. Im working on this currently.

ok thanks for the info ;)


Can't change settings of mirrored local file repo

Gitea version (or commit ref): 1.12.2
Git version: n/a
Operating system: Linux
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
Trying to change the settings on a mirror from a local file repo causes an error "The provided url is invalid. Only http(s):// or git:// locations can be mirrored from.".
From looking at the Gitea sources, it seems the interpretation of the repo URL is implemented quite differently between the New Migration page and the Settings page. But because the New Migration screen lets you create a mirror, the interpretation should be the same.
Screenshots
Snippets from the Settings page:

Still an issue

Still an issue


Annotate HLG with line of user code that created each layer

Computations on the scheduler currently capture the user code that called compute, for diagnostic purposes. This often misses the important part though, if the code that called compute and the code that actually generated the graph are in different places/functions/Jupyter notebook cells.
What might be more useful would be to track which line of user code created each layer in the HLG. This could be used for all sorts of purposes to help users better understand what's going on:

Showing a "line-profiler-style" flamegraph about what lines of user code are contributing the most to runtime or memory use; see https://github.com/dask/community/issues/301#issuecomment-1398668675.
Mapping errors in tasks back to the line of user code that created the task
"Query-plan-style" visualization of the HLG, showing progress, parallelism, and (a snippet of) the line of user code running?

Open question whether we'd want to capture:

just the line number and file
partial stack trace (line number and file of prev N frames)
full stack trace
any of the above, but also with the actual text of the code

xref https://github.com/dask/dask/issues/7933

I would be super happy with just the line number, it would help our dashboard look clearer over at Coiled


Past Papers Project: Independent practice quizzes for learners

Summary
Independent practice quizzes, (as we will refer to them here, but aka past papers and practice quizzes) are pre-loaded quizzes that have been imported to Kolibri using content-integration scripts or via Studio.
In Kolibri:

Device admin can import and export channel quizzes
Coaches will be able to assign channel quizzes to their learners as quizzes and in lessons, and view reports
Learners can then access and search for the channel quizzes in channel topics or see them assigned in their classes, as well as view their own reports and retry quizzes

Dev Deliverables

WHL file installer with past papers functionality (possibly contained in beta release for Kolibri 0.16)
Documentation of the new past papers functionality for the Kolibri Learning Platform
Separate ricecooker class for channel-based quizzes.

Resources

Overview of project - slides
Designs - Figma file
Gherkin stories - Notion
Strings - Ditto
2020 designs for the feature - slides
2021 designs for retry behavior and reports - slides
Tech spec in detail - Notion

All issues completed!


support for native amp

Fixes #1336
Fixes #1337
@mcarilli  mind taking a look?
Issue 1
We have a slight issue with the DP API...
MyModel(nn.Module):
    ...
    @autocast()
    def forward(self, input):
       ...

# Alternatively
MyModel(nn.Module):
    ...
    def forward(self, input):
        with autocast():
            ...

@ethanwharris suggested a way around this which we have in the PR
original_fwd = model.forward
model.forward = autocast()(model.forward)

# train and stuff
# ...

model.forward = original_fwd

Issue 2
How do we save the state of the scaling factor to resume training?
@mcarilli

since which version is amp in pytorch native?

1.6. but we don’t need to explicitly check. we can test the properties as i did

How do we save the state of the scaling factor to resume training?

scaler.state_dict
scaler.load_state_dict

@Borda these tests are failing bc amp is not installed... did we remove amp?

@Borda these tests are failing bc amp is not installed... did we remove amp?

probably, unfortunately, it happened here with Horovoed https://github.com/PyTorchLightning/pytorch-lightning/pull/1529#issuecomment-618068439


Stuck installation

Hi
I am on m1 macbook pro and I try to install Torch Studio but it gets stuck every time
I just click on "install (recommended)" and wait for hours but nothing happened
And the log file has the same text.

me too

My guess is that conda is stuck in an infinite loop when parsing package dependencies.  I solved the problem by installing in groups:
cd ~/TorchStudio/python/bin/conda
./conda install nomkl pytorch torchvision torchaudio -c pytorch -c conda-forge -c anaconda
./conda install datasets scipy pandas -c pytorch -c conda-forge -c anaconda
./conda install matplotlib-base python-graphviz paramiko -c pytorch -c conda-forge -c anaconda

@wzh1994 thanks for the tip. Not sure why conda got stuck though.
NB: note that on mac, due to MKL being incompatible with M1 CPUs, I had to specify a specific version of torch and mkl (as seen in the screenshot).

@wzh1994 Thank you very much
Your solution solved my problem 🙏🌸🌺


New to ModEngine2

Hi: Im new to using the software and upon downloading your latest release I cannot find the executable or the place to place mods.
Any resources I can watch or read to help better?

Retracting my request for help b/c nobody answered.


reduce wait time on yahoo for repeated ISIN numbers

add a local file or cache to save the found isin numbers to speed up conversion
cache only stays for the current run, file stays across runs
what do you think @dickwolff ?

Great suggestion. I have a cache of sorts in the current service but that does not work across multiple runs. Will look into that for sure!

There was an issue with the TypSxcript Map not being correctly processed and saved in cache. This is now resolved.
However there are now issues with retrieving symbols that are linked to the current "old" DEGIRO converter. This has to do with the way the current converter works with parsing records, and conflicting currencies. When #18  is merged, these issues should be resolved I believe.

I have made the final changes to the cache in #22 , which should work now :-)


Add dynamic list templates

Does this solve the issue? https://github.com/symbiote/silverstripe-dynamiclists/releases/tag/2.0.9

Yep!


:arrow_right: Migrate core package 'about' into ./packages

Description of the Change
This PR migrates the core about package into atom/atom.  See issue #17832 for more information.

I'm guessing we can also delete PULL_REQUEST_TEMPLATE.md, ISSUE_TEMPLATE.md, package-lock.json, .travis.yml, and appveyor.yml.

Should these repo specific files be being migrated?

.travis.yml
ISSUE_TEMPLATE.md
PULL_REQUEST_TEMPLATE.md
appveyor.yml

The package specs should be being run as part of Atom's own CI builds now, never mind the fact that they are now in a different repo, so the CI configurations are completely useless. The GitHub repo files are also pointless now as they are superseded by the Atom ones.

Yes, they can be removed, I'll do that before merging.

Added a README.md with details about core package locations.  This will be updated for future package migrations.

Gonna go ahead and get this merged so that I can move forward on finishing the migration of this package.  Please let me know if there's anything else you'd like for me to address and I'll be happy to do it in another PR tomorrow!

📈 💥


Add Prototype Pseudocode

Can this go in its own file? The qeo_ndis header is meant to contain NDIS definitions for QEO.

It could, but it's going to get deleted eventually anyways, so why does it matter?

This seems like it belongs in markdown; the point of this header file is to take the code snippets in the QEO markdown file and produce something an actual compiler will accept. Why would we prefer putting non-compiling, commented-out pseudo code into the compiler-readable header file rather than a human-readable markdown file, which also provides the opportunity for description between code blocks?

I don't want to be super nit-picky, but why is the markdown file in the include directory?
I guess I'm just a bit lost: what is the intent of this pseudo code? Is this meant to be a non-normative extension of the QEO spec, sample code, or something driver developers actually include in their projects?


FAT-141: Implement API Karate tests - PART 2 (improvments)

Jira: https://issues.folio.org/browse/FAT-141
PURPOSE
Cause the environment modules process files slower than locally it is required to give more time to the system for uploading a file.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: IlliaDaliek:x: Bohdan SuprunBohdan Suprun seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


NC 2020 missing major cities

Hey, thanks for this great repository!
Just created a GitHub action that compiles all CDS geojson files into one. One peculiar thing is the 2020 NC data is missing major cities like Raleigh and Greensboro. Wanted to know if that was intentionally left out? You can take a look here: https://github.com/Andrew-Chen-Wang/district-autoupdate/blob/checking-if-geojson-worked/districts.geojson

nvm; faulty code


Few Changes

The user has identified a few changes in the document that has been added where applicable.
Problem:https://github.com/MicrosoftDocs/windows-itpro-docs/issues/6276

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.


added code to create a releasable rebar3/relx otp application

Hi -- I recently had need to migrate a slim-release Nitrogen codebase to one that would work with rebar3 and relx.  While the process was fresh in my mind (and because I never want to have to do that by hand again!) I whomped up some code that can be used to make it all work.  This pull request represents that work.
I don't really expect that this is a PR that's ready for prime time; however, if you see utility in this I'm more than happy to tweak it some to make it more production ready, e.g., figuring out how to manage plugins and HTTP servers other than Cowboy.  If this isn't a direction you want to head in, I fully understand.
Thanks for providing Nitrogen ... it really is a pleasure to use!

Very cool! I was definitely planning to migrate to rebar3 and relx, and
this looks like a great jumpstart point.
I'm on a business trip at the moment, but I'll try to take a look at this
and play around with it a bit this coming week.
I like what you're doing with the config handler - that's definitely
something that's been irritating me for a while.
My gut is telling me that due to the fundamentality of changing from
rebar2/reltool to rebar3/relx, and that it almost necessitates breaking
backwards compatibility, that this will be the nugget of and foundation of
what will become Nitrogen 3.0.
Thanks again, I'm really looking forward to diving into this and plunking
around.
Great work!
-Jesse
On Fri, Jul 31, 2015 at 2:04 PM, Kevin Montuori<EMAIL_ADDRESS>wrote:

Hi -- I recently had need to migrate a slim-release Nitrogen codebase to
one that would work with rebar3 and relx. While the process was fresh in my
mind (and because I never want to have to do that by hand again!) I whomped
up some code that can be used to make it all work. This pull request
represents that work.
I don't really expect that this is a PR that's ready for prime time;
however, if you see utility in this I'm more than happy to tweak it some to
make it more production ready, e.g., figuring out how to manage plugins and
HTTP servers other than Cowboy. If this isn't a direction you want to head
in, I fully understand.
Thanks for providing Nitrogen ... it really is a pleasure to use!

--
Jesse Gumm
Owner, Sigma Star Systems
414.940.4866 || sigma-star.com || @jessegumm

Can you please add Anton to this mailing list?
His email is<EMAIL_ADDRESS>Best regards,
Georges Landry
Mobile: +86 186 2102 2149
Skype contact: georges_landry
Sent from my iPhone

On Aug 1, 2015, at 7:44 PM, Jesse Gumm<EMAIL_ADDRESS>wrote:
Very cool! I was definitely planning to migrate to rebar3 and relx, and
this looks like a great jumpstart point.
I'm on a business trip at the moment, but I'll try to take a look at this
and play around with it a bit this coming week.
I like what you're doing with the config handler - that's definitely
something that's been irritating me for a while.
My gut is telling me that due to the fundamentality of changing from
rebar2/reltool to rebar3/relx, and that it almost necessitates breaking
backwards compatibility, that this will be the nugget of and foundation of
what will become Nitrogen 3.0.
Thanks again, I'm really looking forward to diving into this and plunking
around.
Great work!
-Jesse
On Fri, Jul 31, 2015 at 2:04 PM, Kevin Montuori<EMAIL_ADDRESS>wrote:

Hi -- I recently had need to migrate a slim-release Nitrogen codebase to
one that would work with rebar3 and relx. While the process was fresh in my
mind (and because I never want to have to do that by hand again!) I whomped
up some code that can be used to make it all work. This pull request
represents that work.
I don't really expect that this is a PR that's ready for prime time;
however, if you see utility in this I'm more than happy to tweak it some to
make it more production ready, e.g., figuring out how to manage plugins and
HTTP servers other than Cowboy. If this isn't a direction you want to head
in, I fully understand.
Thanks for providing Nitrogen ... it really is a pleasure to use!

--
Jesse Gumm
Owner, Sigma Star Systems
414.940.4866 || sigma-star.com || @jessegumm
—
Reply to this email directly or view it on GitHub.

cc @T0ha

Hi Kevin,
I'm working with this, but having a few issues with the perl script. I suspect it's because of different CPAN modules on our respective machines (that's why, when I do write perl for Nitrogen, I try to keep it as vanilla as possible without using modules).
Any chance you'd have some time to update the new script to be a little more portable?

"jg" == Jesse Gumm<EMAIL_ADDRESS>writes:

jg> I'm working with this, but having a few issues with the perl
jg> script. I suspect it's because of different CPAN modules on our
jg> respective machines (that's why, when I do write perl for
jg> Nitrogen, I try to keep it as vanilla as possible without using
jg> modules).

Ah!  I should really have run up a VM to test that.  Oops.
jg> Any chance you'd have some time to update the `new` script to be
jg> a little more portable?

Yep.  Next week though: this week's vacation!

Of course! No rush. Get your vacation on!
What environment did you originally develop it with?
-Jesse
On Tue, Aug 11, 2015 at 7:17 PM, Kevin Montuori<EMAIL_ADDRESS>wrote:

"jg" == Jesse Gumm<EMAIL_ADDRESS>writes:

jg> I'm working with this, but having a few issues with the perl
jg> script. I suspect it's because of different CPAN modules on our
jg> respective machines (that's why, when I do write perl for
jg> Nitrogen, I try to keep it as vanilla as possible without using
jg> modules).
Ah! I should really have run up a VM to test that. Oops.
jg> Any chance you'd have some time to update the new script to be
jg> a little more portable?
Yep. Next week though: this week's vacation!
—
Reply to this email directly or view it on GitHub
https://github.com/nitrogen/nitrogen/pull/92#issuecomment-130118033.

--
Jesse Gumm
Owner, Sigma Star Systems
414.940.4866 || sigma-star.com || @jessegumm

"jg" == Jesse Gumm<EMAIL_ADDRESS>writes:

jg> What environment did you originally develop it with?
OS X (Erlang 17.x, Perl 5.18) but I do a ton of Perl work so there are
good odds that I'm using some lib that's not part of the core (or has
maybe been removed from the core in later Perl versions).

Cool. Yeah, I can tell you're quite a bit more proficient with Perl than I
am :)
On Tue, Aug 11, 2015 at 7:35 PM, Kevin Montuori<EMAIL_ADDRESS>wrote:

"jg" == Jesse Gumm<EMAIL_ADDRESS>writes:

jg> What environment did you originally develop it with?
OS X (Erlang 17.x, Perl 5.18) but I do a ton of Perl work so there are
good odds that I'm using some lib that's not part of the core (or has
maybe been removed from the core in later Perl versions).
—
Reply to this email directly or view it on GitHub
https://github.com/nitrogen/nitrogen/pull/92#issuecomment-130121410.

--
Jesse Gumm
Owner, Sigma Star Systems
414.940.4866 || sigma-star.com || @jessegumm

Hi Jesse --  Sorry for the very long delay in responding.  In the course of doing some new work I migrated from rebar to rebar3 and the code I'd submitted in this PR seemed less than exciting after that.  I do have a rebar3 template for Nitrogen though (albeit limited to the features I need).  If you're interested my code is here: https://github.com/kevinmontuori/nitrogen-template .  Thanks again for all the work you've put into Nitrogen!

Thanks Kevin,
I've starred it and will give it a closer look when I begin the process to officially migrating Nitrogen to rebar3. Thanks. For now, I'll leave this PR open, even though it probably won't be merged in its current form. But it'll serve as a reference along with your template.
Thanks!


[Doc] Server MP final review

Apply changes from https://github.com/oracle/helidon/pull/4545 review
Signed-off-by: tvallin<EMAIL_ADDRESS>

@tvallin - is this ready for me to approve or did you need a technical review? I can approve if needed.

Sure you can approve it, there is no technical stuff involved. Thank you !


Failed to start tunnel

SST version: 3.3.29
My AWS keys expired while I was running sst dev command. I killed the process to set them again but now the tunnel doesn't start. I have run sst refresh before sst dev but it doesn't seem to help

Log at .sst/log/tunnel_PanelsVPC.log
time=2024-11-27T12:18:27.965+01:00 level=INFO msg="starting tunnel" subnet=“*******" host=******** port=22
time=2024-11-27T12:18:27.965+01:00 level=INFO msg="running command" command="[ifconfig utun69 destroy]"
time=2024-11-27T12:18:27.971+01:00 level=ERROR msg="failed to execute command" command="[ifconfig utun69 destroy]" error="exit status 1"
time=2024-11-27T12:18:27.971+01:00 level=INFO msg="creating interface" name=utun69 os=darwin
time=2024-11-27T12:18:27.976+01:00 level=INFO msg="running command" command="[ifconfig utun69 ********* ********* netmask ********* up]"
time=2024-11-27T12:18:27.984+01:00 level=INFO msg="running command" command="[route add -net ********* -interface utun69]"
time=2024-11-27T12:18:27.989+01:00 level=INFO msg="running command" command="[route add -net ********* -interface utun69]"
time=2024-11-27T12:18:27.993+01:00 level=INFO msg="running command" command="[route add -net ********* -interface utun69]"
time=2024-11-27T12:18:27.997+01:00 level=INFO msg="running command" command="[route add -net ********* -interface utun69]"
time=2024-11-27T12:18:28.002+01:00 level=INFO msg="tunnel started"
time=2024-11-27T12:18:28.007+01:00 level=ERROR msg="failed to start tunnel" error="dial tcp *********: connect: connection refused"
time=2024-11-27T12:18:28.012+01:00 level=INFO msg="running command" command="[ifconfig utun69 destroy]"
time=2024-11-27T12:18:28.018+01:00 level=ERROR msg="failed to execute command" command="[ifconfig utun69 destroy]" error="exit status 1"

We'll take a look.
 Was the deploy taking too long?

My company uses the AWS Access Portal to manage different accounts as environments. But the AWS environment variables expire really quickly. I was using the dev command, but I noticed that the keys had already expired (because the NextJS application no longer shows CSS styles when this happens, I’m not sure why). I stopped the dev process using Ctrl-C, and after re-assigning the environment variables, I got the error I reported. By the way, I tried changing the Wi-Fi network because I had issues in the past when I was running the tunnel while connected to a VPN. I connected to my mobile hotspot, and the problem was solved. After a few minutes, I reconnected to the office Wi-Fi network, and it worked again.

rebooting the computer helps


[7.x] Publish stubs

Adding the following stubs to the files that will be published when running php artisan stub:publish

mail.stub
markdown-mail.stub
markdown.stub
notification.stub
markdown-notification.stub
channel.stub
view-component.stub
event.stub
listener.stub
listener-duck.stub
listener-queued.stub
listener-queued-duck.stub
exception.stub
exception-render.stub
exception-render-report.stub
exception-report.stub

I only want to publish that people may actually have a reason to customize.

@taylorotwell are there any specific files you would make customizable? I can make new PR for that

Hello, @taylorotwell I hope you are feeling well.
Since a while ago I was going to make a PR about this, but until now I was searching, in case someone had already done it and I found this PR, but I see that they closed it.
In my case the reason of being able to customize these files is to obtain another type of structure that I use and that I like a lot to have a better code reader, example of a component:
class Select extends Component {

    /**
     * Create a new component instance.
     *
     * @return void
     */
    public function __construct(
        public array $options,
        public string $selected = '',
        public string $name = '',
        public ?string $label = null,
        public string $colClass = '',
        public bool $error = false,
    ) {}

    public function isSelected( $option ): bool {
        return $option === $this->selected;
    }

    /**
     * Get the view / contents that represent the component.
     *
     * @return \Illuminate\Contracts\View\View|\Closure|string
     */
    public function render() {
        return view( 'components.form.select' );
    }

}

I hope they will rethink the publication of the other Stubs.
Best regards.


inference_demo.py issue, detailed install instructions of tested platform?

I'm getting errors after installing it, see below. Can you describe on what platform you develop and test lcp-physics, which versions of all relevant packages (Linux distro, mac, windows etc), python3 version (anaconda?) etc.
demo.py seems to work (but sim runs pretty slow), but python inference_demo.py gives an error:
erwincoumans-macbookpro2:demos erwincoumans$ python inference_demo.py
  10 / 11  30.0Traceback (most recent call last):
  File "inference_demo.py", line 248, in <module>
    inference_demo(screen)
  File "inference_demo.py", line 49, in inference_demo
    grad = c.mass.grad.data
AttributeError: 'NoneType' object has no attribute 'data'

(python and pip are an alias to python3 and pip3)

conda install pytorch torchvision -c pytorch
pip install pygame
python setup.py develop
cd demos
python demo.py

erwincoumans-macbookpro2:demos erwincoumans$ python inference_demo.py
  10 / 11  30.0Traceback (most recent call last):
  File "inference_demo.py", line 248, in <module>
    inference_demo(screen)
  File "inference_demo.py", line 49, in inference_demo
    grad = c.mass.grad.data
AttributeError: 'NoneType' object has no attribute 'data'

I had introduced a small bug on the inference script, should be fixed right now. (Currently testing here.)

Regarding demo running slowly, for simple examples like that, most of that is simply because the pygame display is not really optimized, if you run with no display (python demo.py -nd or setting screen=None in the run_world code) it should run much faster than real time. On top of that, especially for more complex examples, the solver is still running on dense matrices, so we're currently working on speeding that up taking advantage of the sparsity in the formulation.

Thanks for the quick reply, performance makes sense now. After updating, the error is as follows:
[torch.DoubleTensor of size 1]

Traceback (most recent call last):
  File "inference_demo.py", line 247, in <module>
    inference_demo(screen)
  File "inference_demo.py", line 71, in inference_demo
    rec = Recorder(DT, screen)
  File "/Users/erwincoumans/dev/lcp-physics/lcp_physics/physics/utils.py", line 58, in __init__
    os.mkdir(path)
FileNotFoundError: [Errno 2] No such file or directory: 'videos/frames'

Fixed. Strange that it passed the tests, I'll check on that.


Improve idp deletion error scenario for user defined federated authenticator

Task issue:

https://github.com/wso2/product-is/issues/21216

The existing implementation deletes the associated action first and then deletes the Identity Provider (IDP) from the database. If an error occurs while deleting the IDP, a rollback mechanism adds the action back. However, the newly added action does not retain the original ID, causing inconsistencies.
To address this, we are changing the implementation to delete the IDP from the database first, followed by deleting the associated action. However, if an error occurs during the deletion of the action, it will result in a stale action remaining in the system. Added a warn for that.

PRs:

https://github.com/wso2/carbon-identity-framework/pull/6178


Header serializer interface change

@smccauliff This patch shows what I suggests for the HeaderSerializer interface change. Can you merge to your patch if you think it makes sense? Thanks.

@becketqin Thanks for the patch for my patch.


Creating the database to contribute to the project

Hi guys, I cloned the repo but had a problem creating the database with bin/setup because the part of the setup that does it is commented (as the database.yml.sample doesnt exist anymore, I guess).
How should people create the database? I used the database.yml.ci but if this was the intention we could make it clear in the bin/setup :)

Same thing about the secrets.yml. And I also needed to set the secret_key on devise's initializer.
Can we make it explicit or try to automatize it on bin/setup?

Actually bin/setup was created automatically by the scripts for the migration to Rails 4.2, and it hasn't been changed since then. It is not useful in its current state.
Currently running the app involves creating by hand some files:

datababase.yml (database.yml.ci can be copied, it will use sqlite which may be enough for some setups)
secrets.yml (secrets_ci.yml can be copied, then rake secret can be run to get keys to replace the secret_key_base and devise_secret_key placeholders in the production section)

This should absolutely be automated to some extent. Also some wiki pages should be written to help people who want to self-host and prefer using a RDBMD different from sqlite. I will get around to it eventually, but of course PRs are welcome.


the fontawesome is on version

i can used the fontawesome 6  for example
fas fa-docker
i used   fab fa-docker


tests: Remove deprecated SHA1PasswordHasher

SHA1PasswordHasher will be removed in Django 5.1. MD5PasswordHasher will remain for the purpose of speeding up tests.

Followup to commit ac5161f4397eb6d984cdc27f56fba52f6a220af2 (#29620).

Sounds good, marked to merge once CI passes.


ZenDesk no longer picking up ticket title

Relevant integration (if any): ZenDesk
🐛 Describe the bug
When a user starts a timer in ZenDesk it now says "undefined" instead of the ticket title
Expected behaviour
Timer would show the ticket title on the timer description.
Other details or context
Intercom link
Screenshot included in Intercom 😊

User reports that the wrong ticket title,
Case reference

@LulzAugusto


Fix cte ordering (#924)

An attempt at fixing CTE ordering by changing storage from an OrderedDict mapping cte ID to its sql into a list of {'id': ..., 'sql': ...} dicts.
Note: this issue is not reproducible on Python 3.6+ due to how the semantics of the dict type changed. Python 2.7, or 3.5, will see it.

Yes, though it's not 100% reliable because you're at the mercy of a dict's random ordering properties, which will be different for every python run. I ran it several times against development and got it to fail.

And yes, it is ready for review!

Fixed #927


Challenge (Use the .env File) delete the property instead of setting it to undefined

Technically, if we are testing for a non-existing property we can't set process.env.MESSAGE_STYLE to undefined as that is implicitly converted to a string.

process.env
Assigning a property on process.env will implicitly convert the value to a string.

This means you can't use this logic
// process.env.MESSAGE_STYLE = 'uppercase'

let message = process.env.MESSAGE_STYLE ? {"message": "HELLO JSON"} : {"message": "Hello json"}

console.log(message) // { message: 'HELLO JSON' }

process.env.MESSAGE_STYLE = undefined;
console.log(typeof process.env.MESSAGE_STYLE) // string

message = process.env.MESSAGE_STYLE ? {"message": "HELLO JSON"} : {"message": "Hello json"}
console.log(message) // { message: 'HELLO JSON' }

But if you delete it, it works.
delete process.env.MESSAGE_STYLE
message = process.env.MESSAGE_STYLE ? {"message": "HELLO JSON"} : {"message": "Hello json"}
console.log(message) // { message: 'Hello json' }

The forum thread that made me open this issue:
https://forum.freecodecamp.org/t/use-the-end-file/498485

Challenge: https://www.freecodecamp.org/learn/back-end-development-and-apis/basic-node-and-express/use-the--env-file
Test: https://github.com/freeCodeCamp/fcc-express-bground-pkg/blob/master/index.js

Hmm, I think this warrants some further discussion.
I do agree that process.env.MESSAGE_STYLE = undefined; is an issue and should be fixed. However, I'm not sure that let message = process.env.MESSAGE_STYLE ? {"message": "HELLO JSON"} : {"message": "Hello json"} should be considered valid logic.
It seems like an anti-pattern to allow a truthiness check to pass a challenge that expects a specific value.

I'm not suggesting that using this type of logic is the correct way of checking (in the client code) for the presence of a value on an environment variable. You would normally look for the string value (e.g. 'development').
However, if you just consider the presence of the string value as a "Boolean" (i.e. it exists or not) you should be able to check for it as such. The only reason you can't is that we set it to a value that isn't actually a falsy value but a string value. Setting the environment variable to the string "undefined" is equivalent to setting it to any arbitrary string that isn't the string "uppercase".
I don't think setting the environment variable to the string "undefined" is in any way the correct thing to do. It's misleading and makes the test code look like it is doing something it isn't. Secondly, we are looking for the absence of the string value, and setting it to another string value just isn't the same.
I don't see an issue with the fix I propose, but if there is one I'd like to hear it.

Setting the environment variable to the string "undefined" is equivalent to setting it to any arbitrary string that isn't the string "uppercase".

Which is, IMHO, what we should do.

I don't think setting the environment variable to the string "undefined" is in any way the correct thing to do. It's misleading and makes the test code look like it is doing something it isn't.

I agree.

Secondly, we are looking for the absence of the string value, and setting it to another string value just isn't the same.

This is the bit I'm confused on. The challenge asks "transform the response object's message to uppercase if process.env.MESSAGE_STYLE equals uppercase", which to me means a specific equality check rather than a truthiness test.

Which is, IMHO, what we should do.

Why? I'm not sure I understand the logic here?

We check that the value is set to the expected string and that we get the expected response.

We remove the value and check that we get the expected response.

Why would setting the environment variable to some random string value be better than removing it?

Because it would prevent code like the one above from passing, without the ambiguity of setting it to undefined.

I still don't get it.
If you have an environment variable in your code that isn't being set then sure it wouldn't match the string you are looking for, but it also wouldn't be some random string value. It simply wouldn't be there. If the property was missing it would be undefined, if the value was missing it would be undefined. At no point in a real project would the absence of the property or value result in some random string being placed on it.
Removing the property seems to me to be what closest emulates a real-world senario.

I don't think we should change expected behavior to force code to conform with some idea of what is, or isn't an anti-pattern. That just doesn't seem like a good idea to me. If something would work in real-world code it should ideally work in an "emulated" setup. If we change the expected behavior that may result in misleading conclusions on the part of the student.
Again just to clarify, I do agree that the code in question isn't how you would want to write it. However, that still doesn't change the fact that it in fact should work.

What if, instead of a random string, we set it to a typo like UPERCASE? That would assert that their logic is in line with the challenge and emulate a real world scenario.

I just don't understand the point? Why is removing the property wrong when it clearly is what the intention of the original code is? The point of setting it to undefined is to emulate it not having a value. Why would that be a problem and how is setting the variable to some magic string behind the user's back not completely unexpected?
This environment variable is acting as a Boolean, it never is set to any other string value (by anyone other than us). It does not contain two possible values used for switching between responses. If it was we would have the client code set it to the two values uppercase and lowercase. Which would be fine with me, but it isn't how the challenge was implemented.

Anyway, if people think we should set it to some string value then I can update the code. I just don't agree with it that's all.
Sorry if it seems like I'm being argumentative. I'm just trying to understand the logic here.

In my experience, it has bitten me in the back many times, in recent months, assuming ENV_VAR=false did anything for a check of if (process.env.ENV_VAR).
That is, I need to constantly be reminded that environment variables are treated like that.

So, if the lesson instructions are:

transform the response object's message to uppercase if process.env.MESSAGE_STYLE equals uppercase

Then, regardless of what process.env.MESSAGE_STYLE is, it should result in the "object's message [being] uppercase"
That is, if process.env.MESSAGE_STYLE=foo or process.env.MESSAGE_STYLE=undefined, the object's message should not be uppercase.

Setting process.env.MESSAGE_STYLE to undefined is simply checking what happens when the value is anything other than uppercase. So far so good.
Setting it to any truthy value for this test is in my opinion wrong. We should give them expected values. The expected value when not set is undefined. What the user decides to do with the value is 100% up to the user.

if object.value === "uppercase" is true, value is "uppercase"
if object.value !== "uppercase" is true, value is ???
I'm not suggesting inferring the type is a good idea, but what if you had to guess?
A safe guess would be an "Any type" but that is just a cop-out.
You might say if the value was initialized to a string value, it should be a string. OK, but what if the value can be missing? That would make it an optional string, or string | undefined. This is an object property, if it or its value is missing it is undefined.
The user doesn't know what the value is when value !== "uppercase" but inferring a falsy value, while not a good idea, isn't that unreasonable either. Always receiving a truthy value seems unexpected to me based on the challenge setup.
The user is setting the value, we are emulating what happens if it is not the correct value, as such we can set it to anything to test. However, in doing so we are changing a user set value without the user knowing about it. Based on the challenge setup, having it always be a truthy string value is, in my opinion, unexpected.

I still do not see the problem with removing the property to test for object.value !== "uppercase"

if object.value === "uppercase" is true, value is "uppercase"
if object.value !== "uppercase" is true, value is ???

Then, in the /json GET route handler you created in the last challenge, transform the response object's message to uppercase if process.env.MESSAGE_STYLE equals uppercase. The response object should either be {"message": "Hello json"} or {"message": "HELLO JSON"}, depending on the MESSAGE_STYLE value.

Again, letting the user decide to ignore the value of the environment variable and instead use its truthiness is a fundamentally different exercise. I'm fine with that exercise existing, but that would require changing the instructions of this exercise.
I think having a challenge where the user has to check not only the existence but also the value of the environment variable is important. That is currently what the instructions require for this challenge.

Case MESSAGE_STYLE === "uppercase":

transform the response object's message to uppercase if process.env.MESSAGE_STYLE equals uppercase.

Case MESSAGE_STYLE !== "uppercase":

The response object should either be {"message": "Hello json"} or {"message": "HELLO JSON"}, depending on the MESSAGE_STYLE value.

Specifically, I'm focused on the words depending on the MESSAGE_STYLE value.
Absolutely nowhere have I mentioned the user code from the forum. I don't like their code, but I'm talking about the instructions as written.
If we instead changed the tests to ignore the value of the MESSAGE_STYLE, then the instructions should correspondingly change to depending upon if the MESSAGE_STYLE variable has been set and we should probably change the name of the environment variable to be consistent with its change into a boolean flag.

I don't care what we set it to when MESSAGE_STYLE !== "uppercase". I agree that alternative values are not currently in the speciation.
I do care that the exercise checks that the user understands they can the the value out of the environment variable and use it like any other value stored in a variable. Getting the exact value out is useful.
If we change then tests to remove the environment variable all together, then we don't know if the user understands that they have access to the value of the environment variable. But that's a very useful thing for them to know.

I don't care what we set it to when MESSAGE_STYLE !== "uppercase". I agree that alternative values are not currently in the speciation.

I mean that is the whole point of this issue though. So you are OK with it being undefined?
No one has posted a good reason why we shouldn't remove the property when testing the response for MESSAGE_STYLE !== "uppercase".
@nhcarrigan said because it allows for an anti-pattern.
I don't agree with us preventing users from creating code that uses anti-patterns. That is not our responsibility. The only responsibility we have here is to make sure we provide a trustworthy environment with expected behavior. Having the environment variable contain a value that the user didn't set is unexpected behavior.

I keep repeating a very good reason.
If we go with your proposed change, then the user can pass the challenge by only checking if the environment variable exists.
That means that we don't verify that the user understands how to get values out of environment variables.
Knowing how to get values out of environment variables is important.
Thus, removing the check that the user knows how to access the value (not just the fact that the variable was set) would be reducing the volume of knowledge required to pass the challenge.

If we go with your proposed change, then the user can pass the challenge by only checking if the environment variable exists.

But that is the expected behavior.

That means that we don't verify that the user understands how to get values out of environment variables.

We also do not know if they have a full understanding of JS and are leveraging it to write code the way they want to write code (good or bad).
If all we need to confirm is that they know how to set the environment variable and use it we can just have it in the response.
res.json({ message: "The message is " + environment_variable})
But we are not doing that. We are asking them to use the environment variable to make a logical branching decision. As such it does matter that the value contain expected values. And when a property value isn't set, it is undefined.

If we go with your proposed change, then the user can pass the challenge by only checking if the environment variable exists.

But that is the expected behavior.

Ok. Then we need to

remove all references to the value of the environment variable from the instructions

change  MESSAGE_STYLE to a name consistent with a  boolean flag

Remove the === "uppercase" information as irrelevant

Well, we definitely need to decide what this challenge is doing and what it is teaching because as it stands now that isn't even clear to me.
Again if we just want to check the env is set and used then why not just have the response with the env value?
On the other hand, if we want to teach how to use an env that can have more than one value, like what you have with "development" and "production", we should set it up as such with two different known values and have the user make a logical branching decision based on the known values.

I thought it was trying to teach accessing environment variable values. That seemed obvious to me from the instructions, but maybe not.
What I don't think is clear is the fact that the test suite has the ability to modify the environment at runtime, which has caused most of the confusion that I've seen on the forum.
I think both use cases (boolean flag or actual value) are important. I don't want to lose the second in an effort to reduce the confusion in the current instructions.

I think this should ideally have been two challenges. One that simply tests for setting and using an env value and then one that uses the env for making logical branching.
Or if combined as it is now, the two possible values should be fixed and the user should know the values.
if (env.value === 'uppercase') {
  res.json({ message: env.value.toUpperCase() })
} else if (env.value === 'LOWERCASE') {
  res.json({ message: env.value.toLowerCase() })
}

Two challenges would definately be better, but I thought we weren't adding challenges?
I agree that it would make more sense if there was more cases, though I like having a default behavior if particular values are not found. Currently we specify a) "uppercase"  and b) default. I'd be happy with a) "uppercase" b) "lowercase" and c) default.
I know we won't ever keep users from writing bad code. The only way to write good code is to write lots of bad code first. But I don't see that as a reason to make it easier to write bad code. In this case, the requirements currently specify that the user checks the value, so letting user code pass that doesn't do that would go beyond 'bad code' to me.

I still did not say that fixing this will let the user write bad code.
I agree that setting the string value "undefined" was probably not the intent.
But your proposed change to the tests would require a change to text of the challenge as well. Checking only if the value has been set is different from the text of the challenge.

process.env.MESSAGE_STYLE ? 'do something' : 'do something else'

This checks if the environment is set and ignores the value of the environment variable.

process.env.MESSAGE_STYLE === "uppercase" ? 'do something' : 'do something else'

This is fundamentally different behavior. It checks if the environment variable is set and what value it is set to.

I'm not trying to twist your words. I'm try to acknowledge that mistakes are important in learning, especially to you, without agreeing that we should write tests that knowingly let solutions pass that have semanticly different results from the requirements.

I see this as a bad assumption. I always assume bad input is a possibility. Letting the user ignore realty that more than just their code matters feels hand holdy to me.

The env from a user's perspective can not contain a string value they did not set, if it can, it should be made clear.

I agree that the user should be told that the environment variable can change.

Any test change needs a corresponding change in the challenge text.
I like the approach of adding another possible value. Suppose we wanted user code to behave like this (ignoring any bad code/good code discussion, which.... again... isn't my point with my objection to just changing the test)
app.get("/json", (req, res) => {
  let messageStyle = process.env.MESSAGE_STYLE;
  let message = "Hello json";
  if (messageStyle === "uppercase") {
    message = message.toUpperCase();
 } else if (messageStyle === "lowercase") {
    message = message.toLowerCase();
 }
res.json({ "message": message});
});

This makes the value meaningful and requires more interaction with the value.
We then would have 3 tests for the outcomes of the user code

MESSAGE_STYLE === "uppercase" -> return "HELLO JSON"

MESSAGE_STYLE === "lowercase" -> return "hello json"

All other cases -> return "Hello json"

Thank you, for all the discussion on this.
I think if anything more needs to be said on the matter, I suggest we take it to the contributor's channel on Chat.

I will be giving this a proper review, next week, and discussing as needed to come to a conclusion for resolution.

My suggestion is as on the comment I made on: https://github.com/freeCodeCamp/fcc-express-bground-pkg/pull/11

Nothing in the instructions here need to change. They are as clear as they need to be whereby:

If MESSAGE_STYLE is equal to the string uppercase, the response should be uppercased. For all other values (falsey or otherwise), the response should be unchanged.


Support Environment.MachineName in Linux builds

@jkotas I fixed the code according to your comments.

LGTM otherwise.


Update readme with weekly call and mailing list

This adds information for new participants to join the mailing list and
weekly meeting.
Signed-off-by: Michael Crosby<EMAIL_ADDRESS>

LGTM

lgtm

Paragraph formatting didn't match the new rule (#82).  It would be
nice to automate that check, since there will be a sizable
finger-breaking period while we get used to the new rule…


Organization configuration consistency

Short Abstract
Centrally manage the OpenFeature GitHub organization to improve configuration transparence and improve consistency.
Why
The OpenFeature project has over 30 repos in the GitHub organization. This brings a number of administrative challenges, leading to inconstancies across the org. These can range from minor annoyances like missing tags or social previews to more critical ones like missing branch protection and invalid user permissions. In order to address these challenges, we need a way a centralized way to manage and share these configurations across the entire org.
Functional Requirements

A central repo must be used to manage the following:
Social preview
Pull request using allow squash merging using PR title
Features (issues, projects)
Collaborates and teams
Teams and member roles (if a custom role is required)
Branch protection on main

Min number of approvals
DCO check before merging
Conversations must be resolved

Individual repos must be able to override the default org configuration.
GitHub Teams must be managed from a central repo

Non-Functional Requirements
The process for modifying org level config is well documented
Inconsistencies are identified but not modified unless approved by an org admin
E2E Acceptance Criteria
New repo
If a new repo is created, it enhances a set of standard options from the org configuration. Examples of these shared settings include branch protection, permissions, and merging strategies.
Update configuration on an existing repo
A configuration update on an existing repo should be possible via a pull request in a centralized management repo. For example, the users that have write permissions on a repo can be modified from a central config.
E2E Demo
An E2E demo should include a centralized configuration repo that contains the orgs current config. Changing a value via a PR should cause the impacted repos to be updated once the PR is merged.

Proposal: https://github.com/open-feature/community/issues/158


ARTEMIS-2359 Upgrade to Guava 24.1

CVE-2018-10237 guava: Unbounded memory allocation in AtomicDoubleArray
and CompoundOrdering classes allow remote attackers to cause a denial
of service.

can you rebase please?

rabased


Figure out how we will use audio features for robot interaction adaptation

This issue will be a place for discussion and collecting resources for using audio features for robot interaction adaptation

It is one goal of the project to use audio data from the participant reading various texts in some meaningful way to cause the robot to adapt the interaction. The first part of this is to understand what features we can sense and from there we can think about what we can adapt based on this information.
Sensing
Possible features

Their accuracy in speaking the words

Perhaps compare a transcription of them through Amazon Polly to the text they're reading
It will be hard to do this on a phoneme level outside of a transcription service because language is complex and it will likely be challenging to find a similar dataset

Their reading speed

We could find their reading rate in words per minute by starting and stoping the interaction - we could also see if they read most of the text by looking at the transcript of the recording

Their reading confidence

Measured by features like how shakey is their voice, etc.

Possible tools

openSmile

Adaptation
Possible ways of adapting the interaction

Giving simple performance feedback

For example, "You are reading 25% faster than last week."

Giving advice

For example, "Maybe you can try slowing down to make sure that you're reading clearly."

FYI @emilyxzhou


Added link to github repo

The main website says If you have any issues regarding this PPA package, create an issue here but it doesn't link anywhere. This request adds a link to the github repo for anyone to report bugs

Merged 898cecb7dc73f65086a7444ddb69f55c8f02164c
Thanks for the MR.


Hotfix for negative axes in unsqueeze op

This is a copy of #3705 to master

Already included in #3716


DoctrineAnnotationBracesFixer false positive

Fixes #5120

Coverage remained the same at 91.848% when pulling 3c461371abc1b6205de5e5c6bf4352c18d540316 on Leprechaunz:doctrine-annotation-braces-psalm into 919e0c6cdbd4fa7c76e69ca9e9701407b728a645 on FriendsOfPHP:2.18.

Thank you @Leprechaunz.


Do not process system Python 2 on macOS Monterey

Closes #17870

@karthiknadig Please let me know if there's a better spot for this check.

We should probably update isMacDefaultPythonPath and use that in the function above.


Add tests

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@bdbe671). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #14   +/-   ##
=========================================
  Coverage          ?   95.23%
=========================================
  Files             ?        6
  Lines             ?      189
  Branches          ?        0
=========================================
  Hits              ?      180
  Misses            ?        9
  Partials          ?        0

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 bdbe671...09489b9. Read the comment docs.


Revert "remove fixed deps"

Change
Reverts AcalaNetwork/bodhi.js#390
waffle examples will still have the deps warning without these locks :

with lock, no warnings: https://github.com/AcalaNetwork/bodhi.js/runs/6102942438?check_suite_focus=true
without lock, has warnings: https://github.com/AcalaNetwork/bodhi.js/runs/6104611253?check_suite_focus=true

This is because waffle examples rely on @acala-network/api which has outdated dependecies, so this warning should only affect waffle examples. I think it should be fine if we just leave it as is, and after @acala-network/api is updated the errors will go awao.
What do you think @ntduan ? Do you prefer keep the locks or remove them

I checked that the waffle examples, doesn't actually use @acala-network/api, so the dependencies can be removed.  Removing polkadot dependencies in the lock file can help us catch dependency problems. Until we can't solve the dependency problem, at that time we can use lock.


fix framerate update bug

fyi @antoinefalisse. Changing the event listener removed the check for available framerates. I changed this back and tested.

Thanks for fixing! Looks good on my end too.


update version number and authors

Codecov Report

Merging #26 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #26   +/-   ##
======================================
  Coverage    89.4%   89.4%
======================================
  Files          27      27
  Lines        1208    1208
======================================
  Hits         1080    1080
  Misses        128     128

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 8bc81c0...b1bcd1a. Read the comment docs.

Looks good, please merge it whenever you're ready.

By selecting "Squash and merge" from the green drop-down menu.


Fix missing import.

The WebDriver / WinAppDriver split put a WebDriver class extension in WinAppDriver.  Which I guess is fine if you build with SPM, but it is not fine if you build with CMake.
This is needed to build Arc test targets with CMake.


Multiarch

Thank you for your effort on all this.
I redesigned the Dockerfile a little so there is no need to change it based on the architecture.
Tested on amd64 and armv7
Trying to build it also in a container right now but failing, need to check why

The Dockerfile.build is now working just fine and you could probably push this to dockerhub with a github action, If you want I can prepare this

Hey, sorry for the late answer. I am quite busy at the moment.
Yes, it would be awesome if you could prepare the github action!

I am going to change the location of the jar file in https://github.com/ReverseEngineeringDE/SAIC-API-Documentation/pull/10 , since it doesn't belong into the git tree.
The jar will also be build by a github action. Currently it can be found in my fork here: https://github.com/tisoft/SAIC-API-Documentation/releases/download/latest/ismart-api-gateway-main-SNAPSHOT-full.jar

merged the PR.
Latest version is now always here: https://github.com/ReverseEngineeringDE/SAIC-API-Documentation/releases/download/latest/ismart-api-gateway-main-SNAPSHOT-full.jar


godot 3 (4?) headless server example

why rush to release anything here?
think about adding an example with a headless server build.
would need to, at a high level:

[ ] create new Dockerfile for creating a headless server client, export that to servers/headless-build similar to web build approach, could likely expand game/docker-compose.yml as well and just add another build client step
[ ] alter servers/docker-compose.yml to launch a container based on servers/headless-build/ - consider creating a servers/headless-build/Dockerfile just for this part, or figure out base cmd w/n docker-compose.yml if straight forward enough
[ ] create a demo / upgrade existing 2d-example demo to have (better) movement, and maybe a pew pew thing
[ ] server build would need to contain code for scaling game in headless client
[ ] nakama or servers/central/ would need to adjust Match code to talk to server and know if players can be added or not, program to work with a single instance w/ a configurable IP / port suppled via existing profile.omgd.headless.host or whatever var - think about scaling headless instances later w/ agones

Make work in a separate area first, then start migrating to omgd code examples.
Consider making this all "just work" by adding a - headless to the yml profile somewhere, if possible

depending on how well / easy / approachable this works, it may be the "standard" approach.
if so, consider renaming or dropping the omgd code godot3-nakama3/channel approach, or renaming it to be more specific sounding, or something. it'd be best used for situations where you wouldn't want to be headless - cost saving - or where the game would benefit from it (card games, maybe?).


<input> not picking up open sans

Describe the bug
<input> in https://github.com/pxblue/angular-design-patterns/pull/134 is not picking up open sans and appears to be using system defaults. All the other text fields, like those listed under "Forms & Validations" in that repo, rendered OK.
What is the expected behavior?
Should use Open Sans
Screenshots or links to minimum reproduction example
Here is what it looked like in Chrome, rendered as Arial

And here is what it looked like in Firefox, rendered as -apple-system

Environment
Mac Big Sur, chrome and Firefox. Fresh clone
Anything else to add?

Likely due to <input> used directly in the Angular code, instead of the Angular Material one


GAB Setup Step

Hi Rama,
Adding a step to go to Dual Write in Finance & Operations and using Apply Solution "Dynamics 365 GAB Dual Write Entity Maps" solution would make things clearer for people who are new to Dual Write.
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/dual-write/party-gab#setup-instructions
Thanks,
Venki

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

ID: 28c9f029-f84b-7ae9-b0a0-257a1cb70683
Version Independent ID: 7218e9bc-56df-da30-509e-1e9ac08ec6eb
Content: Party and global address book - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/data-entities/dual-write/party-gab.md
Service: dynamics-ax-applications
GitHub Login: @RamaKrishnamoorthy
Microsoft Alias: ramasri

@VenkiK, thanks for the feedback. @RamaKrishnamoorthy, please review.


Login to rosa cluster as cluster-admin. error: A server URL must be specified

We are trying to install ROSA with CP4D services. Terraform went into error with below logs. We are seeing below continue messages since long. This issue is intermittent. When we check into "installer-files/.cred" file, cluster API url was missing.
module.ocp.null_resource.configure_image_registry (local-exec):  Login to rosa cluster as cluster-admin
module.ocp.null_resource.configure_image_registry (local-exec): error: A server URL must be specified
module.ocp.null_resource.configure_image_registry: Still creating... [1m10s elapsed]
module.ocp.null_resource.configure_image_registry: Still creating... [1m20s elapsed]
module.ocp.null_resource.configure_image_registry: Still creating... [1m30s elapsed]
module.ocp.null_resource.configure_image_registry: Still creating... [1m40s elapsed]
module.ocp.null_resource.configure_image_registry: Still creating... [1m50s elapsed]
module.ocp.null_resource.configure_image_registry: Still creating... [2m0s elapsed]

This issue was also reported by AWS team while they were testing Data Governance and Privacy with IBM Data Fabric from marketplace.
https://aws.amazon.com/marketplace/pp/prodview-h6w2gbqgaihoa?sr=0-8&ref_=beagle&applicationId=AWSMPContessa


Addition of search bar in Projects section

Search bar is not present there by which the viewer have to scroll all the page.

This issue already exist.


cannot automatically next song

in my case cannot automatically next song,,, thank you

Hello, I suggest looking at the "UAMP" sample: https://github.com/googlesamples/android-UniversalMusicPlayer.
The UAMP sample contains a MediaBrowserService implementation that works with more Android features.
https://android-developers.googleblog.com/2018/06/a-new-universal-music-player.html
https://medium.com/androiddevelopers/making-the-uamp-sample-an-instant-app-30c3f0a050af