Segmentation fault in testzfp while testing 4D array of doubles on MacOS 10.15

After building zfp using GNU make on MacOS 10.15, I ran testzfp and see the following error message:
"testing 4D array of doubles
Segmentation fault: 11"

That's curious.  Which version/branch of zfp?  Using what compiler?  Can you please include the outputs of make and testzfp?

Version: 0.5.5
Compiler: AppleClang <IP_ADDRESS>00033
make output:
$ make
Scanning dependencies of target zfp
[  2%] Building C object src/CMakeFiles/zfp.dir/zfp.c.o
[  5%] Building C object src/CMakeFiles/zfp.dir/bitstream.c.o
[  7%] Building C object src/CMakeFiles/zfp.dir/encode1f.c.o
[ 10%] Building C object src/CMakeFiles/zfp.dir/encode1d.c.o
[ 12%] Building C object src/CMakeFiles/zfp.dir/encode1i.c.o
[ 15%] Building C object src/CMakeFiles/zfp.dir/encode1l.c.o
[ 17%] Building C object src/CMakeFiles/zfp.dir/decode1f.c.o
[ 20%] Building C object src/CMakeFiles/zfp.dir/decode1d.c.o
[ 23%] Building C object src/CMakeFiles/zfp.dir/decode1i.c.o
[ 25%] Building C object src/CMakeFiles/zfp.dir/decode1l.c.o
[ 28%] Building C object src/CMakeFiles/zfp.dir/encode2f.c.o
[ 30%] Building C object src/CMakeFiles/zfp.dir/encode2d.c.o
[ 33%] Building C object src/CMakeFiles/zfp.dir/encode2i.c.o
[ 35%] Building C object src/CMakeFiles/zfp.dir/encode2l.c.o
[ 38%] Building C object src/CMakeFiles/zfp.dir/decode2f.c.o
[ 41%] Building C object src/CMakeFiles/zfp.dir/decode2d.c.o
[ 43%] Building C object src/CMakeFiles/zfp.dir/decode2i.c.o
[ 46%] Building C object src/CMakeFiles/zfp.dir/decode2l.c.o
[ 48%] Building C object src/CMakeFiles/zfp.dir/encode3f.c.o
[ 51%] Building C object src/CMakeFiles/zfp.dir/encode3d.c.o
[ 53%] Building C object src/CMakeFiles/zfp.dir/encode3i.c.o
[ 56%] Building C object src/CMakeFiles/zfp.dir/encode3l.c.o
[ 58%] Building C object src/CMakeFiles/zfp.dir/decode3f.c.o
[ 61%] Building C object src/CMakeFiles/zfp.dir/decode3d.c.o
[ 64%] Building C object src/CMakeFiles/zfp.dir/decode3i.c.o
[ 66%] Building C object src/CMakeFiles/zfp.dir/decode3l.c.o
[ 69%] Building C object src/CMakeFiles/zfp.dir/encode4f.c.o
[ 71%] Building C object src/CMakeFiles/zfp.dir/encode4d.c.o
[ 74%] Building C object src/CMakeFiles/zfp.dir/encode4i.c.o
[ 76%] Building C object src/CMakeFiles/zfp.dir/encode4l.c.o
[ 79%] Building C object src/CMakeFiles/zfp.dir/decode4f.c.o
[ 82%] Building C object src/CMakeFiles/zfp.dir/decode4d.c.o
[ 84%] Building C object src/CMakeFiles/zfp.dir/decode4i.c.o
[ 87%] Building C object src/CMakeFiles/zfp.dir/decode4l.c.o
[ 89%] Linking C shared library ../lib/libzfp.dylib
[ 89%] Built target zfp
Scanning dependencies of target zfpcmd
[ 92%] Building C object utils/CMakeFiles/zfpcmd.dir/zfp.c.o
[ 94%] Linking C executable ../bin/zfp
[ 94%] Built target zfpcmd
Scanning dependencies of target testzfp
[ 97%] Building CXX object tests/CMakeFiles/testzfp.dir/testzfp.cpp.o
[100%] Linking CXX executable ../bin/testzfp
[100%] Built target testzfp

testzfp output:
$ ./testzfp
zfp version 0.5.5 (May 5, 2019)
library version 85
CODEC version 5
data model LP64

testing 1D array of floats
  compress:   rate= 2                                                    OK
  decompress: rate= 2 1.626e+01 <= 1.627e+01                             OK
  compress:   rate= 8                                                    OK
  decompress: rate= 8 8.276e-02 <= 8.277e-02                             OK
  compress:   rate=32                                                    OK
  decompress: rate=32 0.000e+00 <= 0.000e+00                             OK
  compress:   precision= 4 ratio=  7.474                                 OK
  decompress: precision= 4                                               OK
  compress:   precision= 8 ratio=  4.995                                 OK
  decompress: precision= 8                                               OK
  compress:   precision=16 ratio=  2.589                                 OK
  decompress: precision=16                                               OK
  compress:   tolerance=9.766e-04 ratio=  2.589                          OK
  decompress: tolerance=9.766e-04 3.662e-04 <= 9.766e-04                 OK
  compress:   tolerance=2.384e-07 ratio=  1.372                          OK
  decompress: tolerance=2.384e-07 0.000e+00 <= 2.384e-07                 OK
  compress:   tolerance=0.000e+00 ratio=  1.194                          OK
  decompress: tolerance=0.000e+00 0.000e+00 <= 0.000e+00                 OK
  compress:   reversible ratio=  2.253                                   OK
  decompress: reversible                                                 OK
  construct:  4.578e-05 <= 4.578e-05                                     OK
  update:     2.155e-02 ~ 2.155e-02                                      OK

testing 1D array of doubles
  compress:   rate= 3                                                    OK
  decompress: rate= 3 1.626e+01 <= 1.627e+01                             OK
  compress:   rate= 4                                                    OK
  decompress: rate= 4 1.600e+01 <= 1.601e+01                             OK
  compress:   rate=16                                                    OK
  decompress: rate=16 1.831e-04 <= 1.832e-04                             OK
  compress:   rate=64                                                    OK
  decompress: rate=64 0.000e+00 <= 0.000e+00                             OK
  compress:   precision= 8 ratio=  8.943                                 OK
  decompress: precision= 8                                               OK
  compress:   precision=16 ratio=  4.882                                 OK
  decompress: precision=16                                               OK
  compress:   precision=32 ratio=  2.323                                 OK
  decompress: precision=32                                               OK
  compress:   tolerance=9.766e-04 ratio=  4.882                          OK
  decompress: tolerance=9.766e-04 3.662e-04 <= 9.766e-04                 OK
  compress:   tolerance=4.441e-16 ratio=  1.266                          OK
  decompress: tolerance=4.441e-16 0.000e+00 <= 4.441e-16                 OK
  compress:   tolerance=0.000e+00 ratio=  1.127                          OK
  decompress: tolerance=0.000e+00 0.000e+00 <= 0.000e+00                 OK
  compress:   reversible ratio=  4.210                                   OK
  decompress: reversible                                                 OK
  construct:  1.831e-04 <= 1.832e-04                                     OK
  update:     2.155e-02 ~ 2.155e-02                                      OK

testing 2D array of floats
  compress:   rate= 2                                                    OK
  decompress: rate= 2 1.500e+00 <= 1.500e+00                             OK
  compress:   rate= 8                                                    OK
  decompress: rate= 8 3.662e-03 <= 3.663e-03                             OK
  compress:   rate=32                                                    OK
  decompress: rate=32 0.000e+00 <= 0.000e+00                             OK
  compress:   precision= 4 ratio= 27.676                                 OK
  decompress: precision= 4                                               OK
  compress:   precision= 8 ratio= 12.337                                 OK
  decompress: precision= 8                                               OK
  compress:   precision=16 ratio=  3.737                                 OK
  decompress: precision=16                                               OK
  compress:   tolerance=9.766e-04 ratio=  3.319                          OK
  decompress: tolerance=9.766e-04 3.395e-04 <= 9.766e-04                 OK
  compress:   tolerance=2.384e-07 ratio=  1.481                          OK
  decompress: tolerance=2.384e-07 0.000e+00 <= 2.384e-07                 OK
  compress:   tolerance=0.000e+00 ratio=  1.309                          OK
  decompress: tolerance=0.000e+00 0.000e+00 <= 0.000e+00                 OK
  compress:   reversible ratio=  3.210                                   OK
  decompress: reversible                                                 OK
  construct:  7.629e-06 <= 7.630e-06                                     OK
  update:     3.755e-01 ~ 3.755e-01                                      OK

testing 2D array of doubles
  compress:   rate= 1                                                    OK
  decompress: rate= 1 2.376e+01 <= 2.376e+01                             OK
  compress:   rate= 4                                                    OK
  decompress: rate= 4 1.797e-01 <= 1.797e-01                             OK
  compress:   rate=16                                                    OK
  decompress: rate=16 8.583e-06 <= 8.584e-06                             OK
  compress:   rate=64                                                    OK
  decompress: rate=64 0.000e+00 <= 0.000e+00                             OK
  compress:   precision= 8 ratio= 23.011                                 OK
  decompress: precision= 8                                               OK
  compress:   precision=16 ratio=  7.314                                 OK
  decompress: precision=16                                               OK
  compress:   precision=32 ratio=  2.597                                 OK
  decompress: precision=32                                               OK
  compress:   tolerance=9.766e-04 ratio=  6.512                          OK
  decompress: tolerance=9.766e-04 3.395e-04 <= 9.766e-04                 OK
  compress:   tolerance=4.441e-16 ratio=  1.260                          OK
  decompress: tolerance=4.441e-16 0.000e+00 <= 4.441e-16                 OK
  compress:   tolerance=0.000e+00 ratio=  1.131                          OK
  decompress: tolerance=0.000e+00 0.000e+00 <= 0.000e+00                 OK
  compress:   reversible ratio=  6.263                                   OK
  decompress: reversible                                                 OK
  construct:  8.583e-06 <= 8.584e-06                                     OK
  update:     3.756e-01 ~ 3.755e-01                                      OK

testing 3D array of floats
  compress:   rate= 2                                                    OK
  decompress: rate= 2 1.500e+00 <= 1.500e+00                             OK
  compress:   rate= 8                                                    OK
  decompress: rate= 8 9.583e-03 <= 9.583e-03                             OK
  compress:   rate=32                                                    OK
  decompress: rate=32 0.000e+00 <= 0.000e+00                             OK
  compress:   precision= 4 ratio=107.789                                 OK
  decompress: precision= 4                                               OK
  compress:   precision= 8 ratio= 15.754                                 OK
  decompress: precision= 8                                               OK
  compress:   precision=16 ratio=  3.562                                 OK
  decompress: precision=16                                               OK
  compress:   tolerance=9.766e-04 ratio=  2.684                          OK
  decompress: tolerance=9.766e-04 2.203e-04 <= 9.766e-04                 OK
  compress:   tolerance=2.384e-07 ratio=  1.394                          OK
  decompress: tolerance=2.384e-07 0.000e+00 <= 2.384e-07                 OK
  compress:   tolerance=0.000e+00 ratio=  1.282                          OK
  decompress: tolerance=0.000e+00 0.000e+00 <= 0.000e+00                 OK
  compress:   reversible ratio=  2.688                                   OK
  decompress: reversible                                                 OK
  construct:  3.147e-05 <= 3.148e-05                                     OK
  update:     1.846e+00 ~ 1.846e+00                                      OK

testing 3D array of doubles
  compress:   rate= 1                                                    OK
  decompress: rate= 1 5.210e+00 <= 5.210e+00                             OK
  compress:   rate= 4                                                    OK
  decompress: rate= 4 2.002e-01 <= 2.002e-01                             OK
  compress:   rate=16                                                    OK
  decompress: rate=16 3.338e-05 <= 3.338e-05                             OK
  compress:   rate=64                                                    OK
  decompress: rate=64 0.000e+00 <= 0.000e+00                             OK
  compress:   precision= 8 ratio= 30.797                                 OK
  decompress: precision= 8                                               OK
  compress:   precision=16 ratio=  7.087                                 OK
  decompress: precision=16                                               OK
  compress:   precision=32 ratio=  2.558                                 OK
  decompress: precision=32                                               OK
  compress:   tolerance=9.766e-04 ratio=  5.347                          OK
  decompress: tolerance=9.766e-04 2.201e-04 <= 9.766e-04                 OK
  compress:   tolerance=4.441e-16 ratio=  1.208                          OK
  decompress: tolerance=4.441e-16 0.000e+00 <= 4.441e-16                 OK
  compress:   tolerance=0.000e+00 ratio=  1.122                          OK
  decompress: tolerance=0.000e+00 0.000e+00 <= 0.000e+00                 OK
  compress:   reversible ratio=  5.347                                   OK
  decompress: reversible                                                 OK
  construct:  3.338e-05 <= 3.338e-05                                     OK
  update:     1.846e+00 ~ 1.846e+00                                      OK

testing 4D array of floats
  compress:   rate= 2                                                    OK
  decompress: rate= 2 1.372e+01 <= 1.373e+01                             OK
  compress:   rate= 8                                                    OK
  decompress: rate= 8 6.632e-01 <= 6.633e-01                             OK
  compress:   rate=32                                                    OK
  decompress: rate=32 0.000e+00 <= 0.000e+00                             OK
  compress:   precision= 4 ratio=256.000                                 OK
  decompress: precision= 4                                               OK
  compress:   precision= 8 ratio=  9.309                                 OK
  decompress: precision= 8                                               OK
  compress:   precision=16 ratio=  2.798                                 OK
  decompress: precision=16                                               OK
  compress:   tolerance=9.766e-04 ratio=  1.736                          OK
  decompress: tolerance=9.766e-04 1.359e-04 <= 9.766e-04                 OK
  compress:   tolerance=2.384e-07 ratio=  1.166                          OK
  decompress: tolerance=2.384e-07 0.000e+00 <= 2.384e-07                 OK
  compress:   tolerance=0.000e+00 ratio=  1.166                          OK
  decompress: tolerance=0.000e+00 0.000e+00 <= 0.000e+00                 OK
  compress:   reversible ratio=  2.387                                   OK
  decompress: reversible                                                 OK

testing 4D array of doubles
Segmentation fault: 11

Thank you.  Did you download zfp as a tar ball or using git?  In case of the latter, I assume from the make output that you're on the master branch, but please confirm.  Since you're building with CMake, it would be useful to see its output also.  Which options did you pass to CMake?  In short, can you please give me the sequence of steps you performed so we can attempt to reproduce the issue?
Using Apple clang version 12.0.0 and cmake version 3.13.4, I cannot reproduce this issue on the master branch.  What does otool -L bin/testzfp say?  Have you tried running testzfp with valgrind?

I download zfp-0.5.5 as ZIP archive
Then my next steps:
$ unzip zfp-0.5.5.zip
$ cd zfp-0.5.5
$ mkdir build
$ cd build/
$ cmake ..
-- The C compiler identification is AppleClang <IP_ADDRESS>00033
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00033
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Compiling with C standard: 99
-- Compiling with C++ standard: 98
-- Could NOT find OpenMP_C (missing: OpenMP_C_FLAGS OpenMP_C_LIB_NAMES)
-- Could NOT find OpenMP (missing: OpenMP_C_FOUND C)
-- Performing Test HAVE_MATH
-- Performing Test HAVE_MATH - Success
-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/test/zfp-0.5.5/build
$ make
$ cd bin/
$ ./testzfp

otool output:
$ otool -L testzfp
testzfp:
        @rpath/libzfp.0.dylib (compatibility version 0.0.0, current version 0.5.5)
        /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 800.6.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1281.0.0)

Unfortunately, now we don't have valgrind on this machine. But we can try to install it and I'll provide the logs later.

Using the same steps (but with a different clang), I cannot reproduce the issue.  Hopefully valgrind will give us some clues.

Another suggestion is to build zfp in debug mode (cmake -DCMAKE_BUILD_TYPE=Debug ..) and run testzfp through a debugger to give us some idea of where the fault occurs.

$ lldb ./bin/testzfp
(lldb) target create "./bin/testzfp"
Current executable set to '/tmp/zfp-0.5.5/build/bin/testzfp' (x86_64).
(lldb) run
error: process exited with status -1 (Error 1)

I'm not familiar with the lldb target create command.  You should be able to just build with cmake -DCMAKE_BUILD_TYPE=Debug .. and then execute run in lldb.  It's of course possible that the issue does not occur when building in debug mode, which appears to be the case, though I'm confused why there's no output.  Do you still observe the seg fault when just running from the command line?

@esosnina Was this issue resolved?  We were unfortunately not able to reproduce the issue on our end or in our Travis CI tests for macOS, so I am unsure how to proceed.  If this is no longer an issue for you, then I'd like to go ahead and close it.

Sorry for delay, our MacOS systems were upgraded and the issue isn't reproduced now. So I'll close it, thank you!


Add Spanish translation of the Standard criteria

Includes:

[x] Index
[x] Readers guide
[x] Glossary
[x] CONTRIBUTING
[x] GOVERNANCE
[x] CHANGELOG
[x] AUTHORS
[x] print.htlm
[x] Criteria:

[x] _template.md
[x] Bundle policy and code
[x] Code in the open
[x] Continuous integration
[x] Document maturity
[x] Document objectives
[x] Document
[x] Index
[x] Make contributions easy
[x] Use open licenses
[x] Use open standards
[x] Open to contributions
[x] Require review
[x] Reusable and portable codebases
[x] Coherent style
[x] Understandable English first
[x] Version control and history

View rendered es/criterios/_plantilla.md
View rendered es/criterios/codigo-en-abierto.md
View rendered es/criterios/documentacion-madurez-codigo.md
View rendered es/criterios/integracion-continua.md

Nice work! The bulk is clearly done. There are a few more files needed in order for us to be able to generate a completely Spanish pdf. I have listed them in the readme under Files to translate.

Hi there! I gave this draft translations a read, as requested by @ericherman.
I think the main thing he wanted me to check was the "universality" of the Spanish and I have to say it is really, really good :) It is generally very neutral and I haven't seen any regional discrepancies, except perhaps some minor things, such as the article/gender used for certain english words (e.g. "la codebase" vs. "el codebase") but it is not something that would hurt readability of understanding of the concepts.
Also, it is very nice to include the original english word with the disjunction (o) when the translation is not very used and the english word can help clarify (e.g. "revisores o reviewers").
The translation of the requirement level words (MUST, SHOULD, MAY, etc.) is great and makes a lot of sense.
So, overall, IMHO there is nothing to be improved or fixed about the translation to Spanish.
That said, I did spot some errors while scanning through the text, but not in translation, they are either typos, or parts left in English by mistake, that will get fixed when doing a thorough read. The only case I think is worth mentioning because it could be hard to spot is https://github.com/publiccodenet/community-translations-standard/pull/3/files#diff-b017d8b25cc1272719652c26167ce14c5e30f8af7770100fccd6e57171e8ba20R11 where instead of "PUEDE" it should be "PODRIA" as the original in English is SHOULD.
I hope this helps :)

Thank you so much for your input @maurosr ! Applying some of the changes now!


Make eql? behare like ==.

Quoting Object#eql?

For objects of class Object, eql? is synonymous with ==. Subclasses normally continue this tradition by aliasing eql? to their overridden == method

Rha, must fix this wrong remote, sorry for the noise again!


Vuex mutations not showing in dev tools

Version
4.1.4
Browser and OS info
Chrome 68.0.3440.75, Windows 10 1803
Steps to reproduce
Created a new project using the Vue CLI (webpack).
Installed Vuex.
Created a basic store. Added one property (array) and a mutation to alter it.
Committed a mutation, store does update (when logged), but the mutation doesn't show in dev tools.
I took screenshots of each step, which can be viewed here:
https://imgur.com/a/66ZCeSp
What is expected?
The mutation should show in dev tools. I know it used to, seems to have been a very recent update somewhere that has stopped this from working.
What is actually happening?
The mutation isn't showing in dev tools.

Be sure to check my screenshots here: https://imgur.com/a/66ZCeSp

You need to record the mutations:

Oh man, I didn't even think of this because it had always just been on. Thanks, I must have turned it off by accident somehow.

Jesus christ, I almost go crazy because of this

Another common thing I run into is something throwing an error. Sometimes I will have my vue devtools open without the console and wonder why my mutations aren't showing up. Check your console!

For me, not is showing when changing the route. My devtools doesn't can to show up anything, like it had lost the state completely, or get the state unregistered.


ThisType is invalid when using object spread on generic object

Bug Report

🔎 Search Terms

ThisType Object Spread Generic
🕗 Version & Regression Information

I was unable to test this on prior versions because I was not using this feature previously

⏯ Playground Link

Playground link with relevant code
💻 Code

function createObject<D extends {}>(def: D & ThisType<D>) { /* some code */ }

const namableObject = { name: '' };
// ThisType will be wrongly typed when using object spread
const spreadObject = createObject({
  ...namableObject,
  get thisName() {
    return this.name; // <-- Property 'name' does not exists on type '{}'
  },
});
// Correctly typed otherwise
const fullObject = createObject({
  name: '',
  get thisName() {
    return this.name;
  },
});

🙁 Actual behavior
The generic type is broken when the given object value contains a spread object.
🙂 Expected behavior
The generic type should contain the spreaded object properties as those are finally included into the result object.
Comment
This may be related to #26412 and other issues like this one but I didn't found a workarround to get a ThisType correctly typed.

It's a design limitation. At the point when you call this.name the compiler has no idea what type this is except that it extends {}, because at that point the type is not yet fully defined.

I'm not immediately convinced this one isn't fixable-in-principle. The non-spread case works and there isn't a circularity, so I don't see any blockers to it working.

Hi,
Thanks for your quick answers. I agree with @RyanCavanaugh, I dont see anything blocking here.
Yes, the namableObject could be overwritten, but the type of the currently constructing ThisType should style be inferrable IMO.

@RyanCavanaugh, I don't know at all how Typescript works internally. I can make a PR for this if needed but I'll need some guidance.

It's very unlikely the fix here is approachable by someone not already quite familiar with the TypeScript codebase. It's definitely hard enough that I can't offer any concrete guidance on where to start.

OK no problem. I'll wait for any update on this and notify this issue in my package for now. Thanks a lot for those explanation and triage.


Cursor hover color change

Hey @QAZIMAAZARSHAD I want to work on this issue

@SayanSaha01 another similar issue is already open. See issue number https://github.com/QAZIMAAZARSHAD/Movie-Streaming-Website/issues/33.
These effects and features will be dealt with in that issue.


Fix-#363 'type should be enum'

Pull Request
Related issue
Fixes #363
What does this PR do?
Makes the type variable an enum and all the cases are made as per the issue description.

...

PR checklist
Please check if your PR fulfills the following requirements:

[• ] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
[• ] Have you read the contributing guidelines?
[• ] Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

@brunoocasali can you please guide me what do I have to do in order to fix the other two failing tests.
Thank you!!

Thank you! @brunoocasali this will help me a lot!
I will fix these as soon as possible!
Thank you!

I also had some doubts while fixing typing issues as you mentioned in the IndexesResults.swift file.  So I want to test it locally first.

Hii @brunoocasali I'm sorry I was away for some time. I've made some changes, how can I test and get the messages on my local before raising a PR. ? Thank you!!

Hi @Dishant10 good to see you here!
You can follow the instructions written here:
https://github.com/meilisearch/meilisearch-swift/blob/main/CONTRIBUTING.md#development-workflow

Closing due to inactivity!


⚠ Fortnite has degraded performance

In ce744a4, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1610 ms

Resolved: Fortnite performance has improved in 09d01c9.


cephfs static pv, rootPath is ignored by cephfs csi

I followed this doc to create static cephfs pv.
I have created following pv and pvc:
apiVersion: v1
kind: PersistentVolume
metadata:
  name: test
spec:
  accessModes:
  - ReadWriteMany
  capacity:
    storage: 1Gi
  csi:
    driver: rook-ceph.cephfs.csi.ceph.com
    fsType: ext4
    nodeStageSecretRef:
      name: rook-csi-cephfs-node
      namespace: rook-ceph
    volumeAttributes:
      "clusterID": "rook-ceph"
      "fsName": "myfs"
      "staticVolume": "true"
      "rootPath": /volumes/testGroup/testSubVolume
    volumeHandle: cephfs-static-pv
  volumeMode: Filesystem
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: test
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 1Gi
  # volumeName tying this PCV to a specific PV
  volumeName: test

Then I created a pod to consume the volume. When I list mounts then I could see the expected path was not mounted.
root@test-pre-prov:/# mount -l
<IP_ADDRESS>:6789,<IP_ADDRESS>:6789,<IP_ADDRESS>:6789:/volumes/csi/csi-vol-334530b7-a0e5-11ea-856f-0a580ae94188 on /mnt/data type ceph (rw,relatime,name=csi-cephfs-node,secret=<hidden>,acl,mds_namespace=myfs)

I was expecting the path /volumes/testGroup/testSubVolume has to be mounted.
Note: I am using rook-ceph.cephfs.csi.ceph.com csi driver, however in doc it is cephfs.csi.ceph.com.
Environment details

Image/version of Ceph CSI driver : quay.io/cephcsi/cephcsi:v1.2.2
Helm chart version :
Kernel version : 5.3.0-1020-gcp
Mounter used for mounting PVC (for cephfs its fuse or kernel. for rbd its
krbd or rbd-nbd) :
Kubernetes cluster version : v1.15.3
Ceph cluster version : v1.2.7

Ceph plugin logs attached
cephplugin.log

@agarwal-mudit can you please take a look at it?

Its working for me:
root@csicephfs-preprov-demo-pod:/# mount -l
ceph-fuse on /mudit type fuse.ceph-fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)

Have attached pvc/pv/pod definition, only difference is that I am using rook-ceph secret but that has nothing to do with mount failure.
And my cephfs plugin has similar logs as I have pasted earlier:
I0530 04:14:43.894807       1 util.go:48] ID: 2604 Req-ID: preprov-pv-cephfs-01 cephfs: EXEC mount [-o bind,_netdev /var/lib/kubelet/plugins/kuber
netes.io/csi/pv/preprov-pv-cephfs-01/globalmount /var/lib/kubelet/pods/8684edfd-ca91-4932-ae7c-4115a032da6b/volumes/kubernetes.io~csi/preprov-pv-c
ephfs-01/mount]
I0530 04:14:44.048884       1 nodeserver.go:212] ID: 2604 Req-ID: preprov-pv-cephfs-01 cephfs: successfully bind-mounted volume preprov-pv-cephfs-01 to /var/lib/kubelet/pods/8684edfd-ca91-4932-ae7c-4115a032da6b/volumes/kubernetes.io~csi/preprov-pv-cephfs-01/mount

static-pv.txt

Yes @agarwal-mudit I was trying dynamic and static both on the same setup.
I destroyed the cluster and brought back a new one. Now I am not able to reproduce the issue.
However, I got another issue with static PV, now mount is failing.
Describe of pod is showing following events:
  Type     Reason                  Age                From                     Message
  ----     ------                  ----               ----                     -------
  Warning  FailedScheduling        39s (x2 over 39s)  default-scheduler        persistentvolumeclaim "test" not found
  Warning  FailedScheduling        28s (x2 over 38s)  default-scheduler        pod has unbound immediate PersistentVolumeClaims (repeated 3 times)
  Normal   Scheduled               24s                default-scheduler        Successfully assigned default/test-pre-prov to sbr-2
  Normal   SuccessfulAttachVolume  24s                attachdetach-controller  AttachVolume.Attach succeeded for volume "test"
  Warning  FailedMount             7s (x5 over 16s)   kubelet, sbr-2           MountVolume.MountDevice failed for volume "test" : rpc error: code = Internal desc = failed to get user credentials from node stage secrets: missing ID field 'userID' in secrets

I edited the secret rook-csi-cephfs-node(this secret is provided in PV's nodeStageSecretRef field) as following:
Original:
apiVersion: v1
data:
  adminID: Y3NpLWNlcGhmcy1ub2Rl
  adminKey: QVFCTHZkaGVDT25PRmhBQTQrRzdEUWwzdzB0UERaVjFrMDhBdHc9PQ==
kind: Secret

Edited:
apiVersion: v1
data:
  adminID: Y3NpLWNlcGhmcy1ub2Rl
  adminKey: QVFCTHZkaGVDT25PRmhBQTQrRzdEUWwzdzB0UERaVjFrMDhBdHc9PQ==
  userID: Y3NpLWNlcGhmcy1ub2Rl
  userKey: QVFCTHZkaGVDT25PRmhBQTQrRzdEUWwzdzB0UERaVjFrMDhBdHc9PQ==
kind: Secret

After edit, it worked. I also tried with new secret, created with admin creds, and It worked too.
So, the issue missing ID field 'userID' in secrets is a known issue or I am the one who is facing this?

That's a known thing, static CephFS PV works with userID not adminID, ite mentioned here
However, you can create your own secret with userID/userKey and reference it in PV definition or edit rook-csi-cephfs-node (as you mentioned in last post) and use that.

closing this one as it's not an issue


search: search results items are not shown

Describe the bug
The search page is not rendering results (probably due to a missing template or similar).
Steps to Reproduce
Follow the quick start
Screenshots (if applicable)
Note, that the number of results shows 1, but there's no data show:

Oops I duplicated it in https://github.com/inveniosoftware/invenio-search-ui/issues/110 my bad. Closing that one.


Matching context with new lines in the regex doesn't work

Inside the latest Ack2 repository I search for this:
 $ ack "current\ndirectory.*then"
 249:Search for PATTERN in each source file in the tree from the current
 directory on down. If any files or directories are specified, then

But if I search the same with the context:
 $ ack -A2 "current\ndirectory.*then"
 $

I don't see anything. This is because the way ack parse files. It does parse the file iterating lines when context is enabled and the whole file else. No exception is handled here. This is a bug.

This is definitely a bug; both in the inconsistency in operation between two modes that should be consistent, but also in your first example.  Ack is line-based (see Can I do multi-line regexes? in the FAQ), but we read the file into a single chunk sometimes for optimization purposes.

Ok, this is fixed in dev now.  Thanks for the report!


select for update got an error

What happened:
when I write sql "select sth for update" and use QueryContext func.Why I use QueryContext(not ExecContext) because I want to
get the rows:

I got error:

What you expected to happen:
execute normally
How to reproduce it (as minimally and precisely as possible):
sql and func like my code
Anything else we need to know?:
the reason maybe in seata-go, it QueryContext and then ExecContext, so the mysql conn is something wrong
this is the QueryContext code:

and then :after exec the business func (showed upon) in line 178, it exec line:185

and this conn cant use twice(watching in mysql has been set to true, and haven't set to false after queryContext complete)

In mysql driver QueryContext func haven't finish the mc unless err != nil(it's diff with ExecContext func)

I change the code swap the business func and exec in select_for_update_executor.go
and the QueryContext func can use with in an Tx

assign me please


Include collective name in Action Required emails

I have a recurring expense for the SustainOSS collective. I get an email every month, asking me to upload the receipt for the expense. Due to Gmail filters, I never see this email, as I receive all emails for Open Source Collective.
I would like to filter the email to ensure it does show up in my actual inbox, so that I see it. However, the only way to do is to filter for the name of the expense, and not the name of the collective, as it is not included in the emails.
Proposed fix
Change the title of the email, or the text, to include the name of the collective where the notification is coming from.
Screenshot

As a quick fix I could suggest;

A card attached to FIRESIDE PODCASTING was charged $51.00 and we need the responsible admin to input additional
information. This expense was submitted to Agora Collective....

Also reported in https://github.com/opencollective/opencollective/issues/4312#issuecomment-1241805983

The email in the screenshot looks plain wrong to me.
Seems to me the "A card attached to" was meant to be the collective.name?

That would make more sense. May be an easy fix, then.


Swagger

Add swagger generation.  Let's see if travis works.

Yay travis.  Alright.  This is the last generator and now the three naughty packages.


TSC Meeting (11 June 2024)

June 2024 @StackStorm/tsc 1 hour meeting:

Tuesday, 11 June 2024, 9:30 AM US Pacific / 6:30 PM EU CEST
See https://github.com/StackStorm/community/issues/33 for the schedule and how to join
TLDR; Jitsi link: https://meet.jit.si/StackStormTSC

Attendees
Present

Carlos nzlosh
Scott jk464
Julius B

Absent

AJ guzzijones
Ankur Singh rush-skills
Bradley Bishop bishopbm1
Dmitri Zimine dzimine
Jacob Floyd cognifloyd
Khushboo khushboobhatia01
Marcel Weinberg winem (unable to attend)
Mick McGrath mickmcgrath13
Tomaz Muraus Kami
W Chan m4dcoder
Mark Mercado mamercad (unable to attend)
Amanda McGuinness amanda11 (unable to attend)

Meeting Agenda
Progress status

StackStorm v3.9.0 https://github.com/orgs/StackStorm/projects/31
Support for Python3.10 https://github.com/StackStorm/st2/pull/6157
Support for MongoDB 5, 6, 7
Eventlet Retirement https://github.com/StackStorm/st2/issues/6128
StackStorm Exchange - Pack compatibility with Python3.9/3.10/3.11
Pants
stackstorm.com revamp https://github.com/StackStorm/community/issues/132

Progress status

StackStorm v3.9.0 https://github.com/orgs/StackStorm/projects/31

Support for Python3.10 https://github.com/StackStorm/st2/pull/6157

nzlosh hasn't had much free time to work on py3.10 and will try to pickup the work this month.

Support for MongoDB 5, 6, 7

No update.

Eventlet Retirement https://github.com/StackStorm/st2/issues/6128

Julius B might be able investigate the effort required to switch to either gevent or asyncio.
A code jam was suggested as a possible way to create a collaborative environment for large tasks
like eventlet retirement.  nzlosh will look at how Coding Jams are run and see if it's possible to run trail to get feedback.

StackStorm Exchange - Pack compatibility with Python3.9/3.10/3.11

No update.

Pants

No update.

stackstorm.com revamp https://github.com/StackStorm/community/issues/132

Scott jk464 has been working on stackstorm helm.


Fix the bug of cache function in get_json method.

The BUG is:
The cache object cache the value for the first call. Then the
succedent call get the same value in the first time, no matter
what are the arguments.
This PR fixed this BUG
Link to https://github.com/pallets/flask/issues/2651

BTW: This is my first PR on github. If have any problem in this PR, please tell me in detail. Thx  :-）

Thanks for contributing!
This seems suboptimal in the case where it's still valid JSON even though silent was passed, which is hopefully the most common case. Either parsing will succeed and both cached values will be the same, or parsing will fail and the cached value for silent will always be None.

@davidism  Thx for your advice, which makes my thought more clear.
I refined the code now. :-)

Who can help me to review the code.
I am waiting for a response.
@davidism


(notepadplusplus) Uninstaller isn't silent for notepadplusplus.install

After the uninstall script has finished executing, the uninstaller pops up and needs to be manually clicked through.

could you please provide some more details as I'm unable to reproduce this on my end.
what OS and architecture do you run?
was it 64bit or 32bit version of notepad++ you had installed?
Do the script any output, or warnings?


Release/extensions

This PR fixes #

@microsoft-github-policy-service agree company="Microsoft"

@RamyaR29 You have to remove the > from your response


Primary Election Losers still showing

Candidates who lose in the primary election are still showing in the list. For example, in Washington State 8, only Patty Murray and Chris Vance should show for Senate, and for House, only Dave Reichert & Tony Ventrella should show. For Oregon, only 3 should show for Senate, only 2 should show.

yea, those candidates are the outdated data in the original db. I will add an extra column indicate the candidate source then @terry77228 might need to adjust the front end code a bit.

Not sure how the candidate source will solve this issue. We need to show only those who won the primary election, that have the green checkmark next to their name in ballotpedia.

Add field in the DB to show if candidate is a winner of the primary.

Mark, Can you improve the scrappy readme so a new user can understand it. Also perhaps mention it in the STARTHERE.md. Thanks


Cmake failure when attempting to compile against CGAL

I am getting the following ecbuild/cmake error when trying to compile ATLAS against CGAL (via -DENABLE_TESSELATION=ON):
CMake Error at CMakeLists.txt:141 (set_target_properties):   set_target_properties can not be used on an ALIAS target.
Cmake version 3.13.4, CGAL version 5.0, ATLAS develop.  My ecbuild command contains -DCgal_DIR=/path/to/cgal/install/lib64/CGAL/cmake, I have looked at the trace and it seems to be correctly finding the CGALConfig.cmake file and its friends.
Line 141 of CMakeLists.txt is
     set_target_properties( CGAL::CGAL PROPERTIES INTERFACE_COMPILE_OPTIONS "" )
I can work around this by removing lines from ATLAS's CMakeLists.txt files:
line 141 of CMakeLists.txt
lines 234-237 of src/atlas/CMakeLists.txt
but I guess this is not the desired solution.

It seems that replacing CGAL::CGAL with plain CGAL in CMakeLists.txt fixes the issue.  This is consistent with the error message, and this documentation:
https://cmake.org/cmake/help/v3.9/command/add_library.html#alias-libraries
which both say that what is being done currently is invalid.  There is a reference in the code comments to an ECMWF ATLAS Jira ticket 193 which I guess would be:
https://jira.ecmwf.int/browse/ATLAS-193
but I don't have permission to view it.

is this fixed by https://github.com/JCSDA-internal/jedi-stack/pull/70 ?

The modifications to the dependencies file help fix the problem.


v1.32.4 version bump

Backstage release v1.32.4 has been published, this Pull Request contains the changes to upgrade to this new release
Please review the changelog before approving, there may be manual changes needed to enable new features:

Changelog: v1.32.4
Upgrade Helper: From 1.33.0-next.0 to 1.32.4

Created by Version Bump<PHONE_NUMBER>7

Closing, we want to stay on the next release line, looks like the logic version bump automation needs a fix


Offer a base set of app data

So, for example, someone could install Tweetbot without having to find the proper name and pkgutil ID strings.
How should this be exposed to the user? Recipes? Resources? Both?
Maybe Tweetbot can be installed with either:
include_recipe 'mac-app-store::tweetbot'

or:
mac_app_store_app 'tweetbot'

Left some examples in the README and going with individual app cookbooks for now--some of these apps also have Windows and/or Linux versions.


Setup native-x to occupy requested slot

It appears Native-X was set up for this site at some point but nothing was actually declaring an index to put them anywhere, this puts it as the first card in all load-more sections for both landing and content pages. Should this need to get moved up a level to only be on section landings let me know.

 Verify NativeX ad placement on site.

@Shinsina - I'm closing this one for now, at least until such time we have direction from the group.

 Verify NativeX ad placement on site.


Chrome loads incorrect source when using auto sizes

When using auto sizes the source image loaded is inconsistent in Chrome Version 48.0.2564.103.
Works fine in Firefox and Safari.

On page load sometimes the incorrect source (too large) is loaded. This occurs more often on smaller sizes but sometimes the same source is applied to all images.
On resizing the window every image is changed to the largest source.

See my codepen:
http://codepen.io/anon/pen/LGXGJx
Please compare results between Chrome and Firefox/Safari

I think this is a duplicate of this:
https://github.com/aFarkas/lazysizes/issues/133
please close if you think so too or explain why not.

Yes It might be that Chrome caches and reuses the first image, however even disabling cache in devtools I get strange results which are not consistent like in Firefox or Safari. I'll do some tests with only unique images in various sizes to see  how it behaves and post the results here.

I updated the pen with unique sources and now it seems to work. When I open it in a incognito window in small viewport it loads the smaller versions. You could easily be tricked by the algorithms of Chrome. :) Closing.


merge from template-kronos-app

package.json

chore(deps): add ^12.0.1 remove ^12.0.0 (devDependencies.@semantic-release/release-notes-generator)

:tada: This PR is included in version 1.11.0 :tada:
The release is available on:

npm package (@latest dist-tag)
v1.11.0
GitHub release

Your semantic-release bot :package::rocket:


Expose function evaluation from KLLVM bindings

Blocked on https://github.com/runtimeverification/llvm-backend/issues/943

https://github.com/runtimeverification/k/pull/4242


GraphQL as a swift package manager

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

I am creating some projects which have a common platform. and I am using the common swift package manager for business logic.
Now with GraphQL, I need to move my business logic from


agent: use regorus instead of opa

Implement Agent Policy using the regorus crate instead of the OPA daemon.
The OPA daemon will be removed from the Guest rootfs in a future PR.
Fixes: #9388

Conformance run: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=558485&view=results

Conformance run: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=558485&view=results

Thanks for helping with this!

Updated conformance run for image build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=558539&view=results
Previous one (https://dev.azure.com/mariner-org/mariner/_build/results?buildId=558518&view=results) triggered with the wrong m-a-p branch/ fork branch tag


no start line - RS256

Greetings.
I'm not sure if it's something I'm completely borking up, but I can't see another way to do it.
We use your library to send JWT's from our frontends to our backends out of paranoia - this is working great, php has no trouble decoding these.
I am now trying to use your library to accept a JWT from a different provider (encoded with go-jwt)
This is the public key
-----BEGIN PUBLIC KEY-----
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD0UJybPz2/GQAGh/Ri3rvsv60h
fYB3JzoZpWzKBPPXeHC/w7rnOSdOjeqLT4evgfRXjsld9Rx5GYXARiEicTl1l9DU
+P9xk0eptU/Cawz003/XT5tPX+uhmFcC3zIa3oUb/25Kq+IPeq1AUTK9PcJsohFk
pcgtuZvphRLKvFA8uQIDAQAB
-----END PUBLIC KEY-----

This is the token
eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE0NDQ2OTQxNzksImlhdCI6MTQ0NDY1MDk3OSwiaXAiOiIxNzIuMTYuMjAzLjEiLCJuYmYiOjE0NDQ2NTA5NzksInVzZXIiOiJzaGFubm9uLnd5bnRlciJ9.PLEe64xKFGpkwrX2OameIT6_xSpl5mW_BxFmI4sz20SS_jOaemWrwUBB4gMIUm9LwhxUWTAr5wdLMF30bDJLSfQamf2VeggGMzvjKMQdbJcOPzT6QPmuITAju7bn6WzLzEE5cThIXhOCEdNGKf1xDp9om9T8HVZ15nWpuwwvqwo

This is the output
{"payload":{"nbf":1444650979,"ip":"<IP_ADDRESS>","exp":1444694179,"user":"shannon.wynter","iat":1444650979},"reason":"no start line","raw_header":"eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9","valid":true,"header":{"alg":"RS256","typ":"JWT"},"signature":"PLEe64xKFGpkwrX2OameIT6_xSpl5mW_BxFmI4sz20SS_jOaemWrwUBB4gMIUm9LwhxUWTAr5wdLMF30bDJLSfQamf2VeggGMzvjKMQdbJcOPzT6QPmuITAju7bn6WzLzEE5cThIXhOCEdNGKf1xDp9om9T8HVZ15nWpuwwvqwo","verified":false,"raw_payload":"eyJleHAiOjE0NDQ2OTQxNzksImlhdCI6MTQ0NDY1MDk3OSwiaXAiOiIxNzIuMTYuMjAzLjEiLCJuYmYiOjE0NDQ2NTA5NzksInVzZXIiOiJzaGFubm9uLnd5bnRlciJ9"}```

And this is how I get that
local cookie_value = ngx.var.cookie_lda
if (cookie_value == nil) then
    ngx.exit(401)
else
    local public_key = [[-----BEGIN PUBLIC KEY-----
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD0UJybPz2/GQAGh/Ri3rvsv60h
fYB3JzoZpWzKBPPXeHC/w7rnOSdOjeqLT4evgfRXjsld9Rx5GYXARiEicTl1l9DU
+P9xk0eptU/Cawz003/XT5tPX+uhmFcC3zIa3oUb/25Kq+IPeq1AUTK9PcJsohFk
pcgtuZvphRLKvFA8uQIDAQAB
-----END PUBLIC KEY-----]]

    local jwt_obj = jwt:verify(public_key, cookie_value)
    ngx.log(ngx.ERR, cjson.encode(jwt_obj))
end

The debug tool at jwt.io says it's a verified signature but this library won't verify it saying "no start line"
Any help?

got this, i'll look at it in few hours.

Has it been resolved? I am getting the same reason "no start line". If I remove the start line of the key, I get "wrong tag"

For all the poor lost souls out there, who were brought up here by google search: no start line - in this case I needed a certificate file rather than a public key. Turn your public key in certificate and you are good to go!

For all the poor lost souls out there, who were brought up here by google search: no start line - in this case I needed a certificate file rather than a public key. Turn your public key in certificate and you are good to go!

thanks @tanica !

We knew this was a solution, but with other libraries (and indeed jwt.io) it's not a requirement.

Is there an example of how people here accomplished this? I have the same problem as @freman. I'd love to know how @tanica went about creating a certificate file from a public key. Also, how are you passing in that file to the verify function? Are you reading it with io.read and saving that to a variable? Thanks.

@tanica @swynter-ladbrokes  @SkyLothar  - I'm working with Nick, so just adding more to his question as we've found ourselves a bit up against the clock... we've tried all kinds of different openssl calls to try to generate a crt from a pem, but are seeing the same "no start line" error from openssl when we try that.  And we've been searching online for how-to's but can't seem to find anything that works for going from a public key to a cert.    We know we've at least got the pem generally right as we can use it to perform a working validity check in node.    We're also guessing that the requirement here is not that the key is read specifically from a file in the lua code, but rather the reference to a cert file has to do with how the data is converted... and that if we wanted (though not really desired) we could hardcode the resultant content of a cert into our lua module variable directly and it should still work.  Is that correct?  But the primary question is still specifically how can we covert our pem key to the necessary form that this module requires.  Thanks in advance for any help!!

So I created a shell script which I put these commands, because I needed some different types. Here is what I had:
#!/bin/bash
KEYNAME=$1
openssl genrsa -out $KEYNAME.pem 2048
openssl rsa -in $KEYNAME.pem -outform PEM -pubout -out $KEYNAME.pub
openssl pkcs8 -topk8 -inform PEM -outform DER -in $KEYNAME.pem -out $KEYNAME.pkcs8 -nocrypt
openssl rsa -in $KEYNAME.pem -pubout -outform DER -out $KEYNAME.pub.der
openssl req -new -days 3600 -key $KEYNAME.pem -out pubcert
RANDFILE=temp openssl x509 -req -in pubcert -signkey $KEYNAME.pem -out certificate
Good luck!

Is there any movement on this? Or has anyone been able to convert a PEM public key to a format accepted by this library?

Both tanica & atanasova users are me, I posted the reply with my work account. The shell script above should work! good luck!

@atanasova Thanks! That's a great script to create a new cert and all the associate assets and that will work well for testing.
However, unless I'm missing something, I don't think that solves the issue of converting an existing PEM to a certificate that can be used. I need to use a PEM public key I've been given. So either I need to convert it to a format that this library takes or I need to modify the library to accept the PEM.

unfortunately no, it won't work with PEM. You can use openssl to convert to Certificate. Unfortunately this is the only Lua lib I found that will validate RSA keys

i ran into this problem as well - luckily i had access to the private key and could generate a certificate.  I do think the library should accept a public key, though.  it looks like all it does with the certificate is get a public key from it: https://github.com/SkyLothar/lua-resty-jwt/blob/master/lib/resty/evp.lua.  so maybe the fix isn't too bad?

I've made some mods to make this work you are welcome to try.
https://github.com/theganyo/lua-resty-jwt
Just use as normal but pass in your public_key (PEM string):
local jwt_obj = jet:verify(public_key, jwt_token)
It has worked for me, but I haven't spent much time testing it.

@theganyo - I've pulled down your fork since I need to do some verification of the JWT using the PEM file. From what I have tested it seems to work.

@clwang Great! Thanks for verifying!


OpenSource or not? And Google where is inside?

Hi Devs and thanks for your contribute!
This is not a really issue question, we would like to know if "google-authenticator-libpam" is or isn't OpenSource (or if it contains proprietary code),
Wikipedia says:
Previous versions of the software were open-source but since 2013 releases are proprietary.[3]
Then, should be very interesting to know if "google-authenticator-libpam" contains calls to Google servers and therefore covert tracking systems.
Many thanks!

This repo, Google Authenticator LibPAM, is 100% open source, and there is no internal version or anything. In fact, this repo is ONLY distributed as source code, which is entirely open to read, to find any covert tracking. As the current maintainer I've stared at the code a lot, and not found any. (though I am employed by Google, and encourage you to look for yourself).
Linux distributions take the code from here, and compile it to release it as binary. But Google does (to my knowledge) not.
Sorry for the confusion. That statement on wikipedia applies only to the apps on phones/tablets, and not to anything in this repo.

This repo, Google Authenticator LibPAM, is 100% open source, and there is no internal version or anything. I[...]
I hope that clarifies.

Hi ThomasHabets and thanks for your reply,
anyway my doubt persist. Here you can see a call stack to Google system, with which it can get different types of information, as ip, time, and location for example, but surely much and much more..
if (encoderURL) {
    // Show a QR code.
    const char *encoder = "https://www.google.com/chart?chs=200x200&"
                          "chld=M|0&cht=qr&chl=";
    const char *encodedURL = urlEncode(url);

    *encoderURL = strcat(strcpy(malloc(strlen(encoder) +
                                       strlen(encodedURL) + 1),
                                encoder), encodedURL);
    free((void *)encodedURL);
  }

and here Google admits to have access to tocken:

`printf("Warning: pasting the following URL into your browser exposes the OTP secret to Google:\n  %s\n", encoderURL);`

What can you tell me about this?
And secondly, but still of a certain importance, why does the code still bear the name of Google?
Thanks in advance for all the answers you will give me.

As noted in the lines of code you quoted, it prints a URL that lets you optionally open the QR code in Google’s web QR code generator, and shows a clear warning alongside the URL about the impact of doing so.
If you don’t open the link in your browser, no traffic is sent to Google.
The code probably bears Google’s name because Google employees wrote it.

Ah yes. When you provision a new user that is done by showing a QR code, and scanning it in your app. Normally the QR code "image" is generated using libqrencode, to create an ASCIIART QR code in your terminal. That is done entirely on the local system.
Optionally, you can choose to generate the QR code image by using the Google charts API.
Personally, I never use that generated URL. And it's never used automatically. You have manually copy-paste that into a browser for any network activity to happen.
I'm not on the Google Charts team, nor can I speak for them about how their logs are used. I think this may be the ToS for Google Charts, and maybe the relevant section is 5b. But I'm not a lawyer, and am not in a position to speak for a lawyer, or Google, or to forbid, allow, or promise anything. And please don't read anything into that vagueness, other than the fact that I'm not a lawyer.
Note that "Google admits to have access to token" may be technically true (though one could debate the difference between "exposes" and "access"), it's also true that pasting that URL into your browser also gives access to the token to Firefox, AdBlocker, and any other extension you have that is allowed to look at URLs. Hopefully all of these only use the URL to provide the service of rendering the QR code, and don't log them anywhere. Hmm… actually your browser probably put it in the browser history. That's… actually a bit concerning.
Why still the name "Google" is a good question. It's mostly historical. Back when this code was on code.google.com it was all part of the same git repo called "Google Authenticator" that included apps for iPhone, Android, and Blackberry. When I moved it to github I split it into one for Android, one for the PAM module, and one for "other". This makes it easier to deal with pull requests and bug reports. Also they don't share code. And I only really wanted to maintain the PAM module, so am hoping someone will take more ownership of the other ones.
There's nothing Google-specific about the code in this repo. It's an open standard, that other applications also implement. The Google Charts API could just as well also have a link to some other web-based chart renderer, and I would accept a PR to provide alternatives. (though really one should generate the QR code locally by having libqrencode installed). It could be called "TOTP/HOTP PAM module". But it's had this name for longer than I've maintained it, and the name is used by Linux distributions and many other things, so I'd say the name ship has sailed.


Can't input numbers on mobile Safari

v2.2.31
Repro code: Pinput()
Visit webpage using Safari on iPhone, try to tap numbers, no input.

Yep, it works there. Our app is using Flutter stable 3.7.5. What was the demo page built with?

I've just pushed the update to the demo page and it's built with flutter 3.7.6

@Tkko Found the problem - the SelectionArea widget. Full repro:
void main() async {
  runApp(
    MaterialApp(
      home: SelectionArea(
        child: Scaffold(
          body: Pinput(),
        ),
      ),
    ),
  );
}

Wrapping Pinput() with SelectionContainer.disabled() to disable selection on it doesn't work either.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_4419e0f0-91e6-458e-950c-9d9e55c4ce36/pull/1 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target_4419e0f0-91e6-458e-950c-9d9e55c4ce36.git

Docs Build status updates of commit 552d3aa:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: RepositoryUnauthorizedWithSourceCommit] Git data access to 'https://github.com/opstest2/docs-archive-test-source' (branch: Release_Archive_main_2022-02-21-10-09-28) is not authorized.. It looks like this might be the first time user: v-alji submitted a pull request to this repo. Before user can run builds in a pull request, he/she can enable 'v-alji' GitHub account in Docs by visiting Docs Portal (https://ops.microsoft.com). After enabling his/her account (v-alji), close and then reopen this pull request to start another build.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Map based LSTM

Hi guys!
These baselines are really wonderful to start with Motion Forecasting. In my particular case, I am trying to include map information to the LSTM in order to compute multimodal predictions that are directed towards plausible lanes (computed using map_utils.py). However, I have not seen in the train function that the input to the encoder is influenced by the lanes:

But, on the other hand, in the infer_map function, you specify some CANDIDATE_CENTERLINES and modify the input of the encoder:

Do you use these map lanes only during inference or also while training?

Hi! The map is used during training as well. Instead of using all candidate centerlines, we use just the oracle centerline. The input features in the above "train" code are for a pre-selected oracle centerline. Refer the feature computation here for more details. Hope this makes sense.

then you train with just the oracle (the groundtruth centerline) and in the inference you do the same for each candidate, so all map information is not included for each iteration of the for loop, but only each candidate, right? And what happens if I want to predict k=6 trajectories (required for the leaderboard) but I have less than 6 candidates in front of me?
By the way, do you encode both the past and future information of the centerline or just the future?


Release 1.1.2 not working on uWSGI and gunicorn

Hi!
Thank you for sharing this package. It's really useful.
I've found a problem upgrading to the 1.1.2 release. Using runserver works great, but at least on uWSGI and gunicorn, it fails with the following error just after receiving the first chunk.
[2017-06-22 10:03:41,866] ERROR django.request-132 Internal Server Error: /api/chunked_upload/
Traceback (most recent call last):
  File "/home/juan/.virtualenvs/demo/lib/python3.5/site-packages/django/core/handlers/exception.py", line 42, in inner
    response = get_response(request)
  File "/home/juan/.virtualenvs/demo/lib/python3.5/site-packages/django/core/handlers/base.py", line 187, in _get_response
    response = self.process_exception_by_middleware(e, request)
  File "/home/juan/.virtualenvs/demo/lib/python3.5/site-packages/django/core/handlers/base.py", line 185, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/home/juan/.virtualenvs/demo/lib/python3.5/site-packages/django/views/generic/base.py", line 68, in view
    return self.dispatch(request, *args, **kwargs)
  File "/home/juan/.virtualenvs/demo/lib/python3.5/site-packages/django/views/generic/base.py", line 88, in dispatch
    return handler(request, *args, **kwargs)
  File "/home/juan/.virtualenvs/demo/lib/python3.5/site-packages/chunked_upload/views.py", line 93, in post
    return self._post(request, *args, **kwargs)
  File "/home/juan/.virtualenvs/demo/lib/python3.5/site-packages/chunked_upload/views.py", line 214, in _post
    chunked_upload.append_chunk(chunk, chunk_size=chunk_size, save=False)
  File "/home/juan/.virtualenvs/demo/lib/python3.5/site-packages/chunked_upload/models.py", line 69, in append_chunk
    self.file.write(chunk.read())
io.UnsupportedOperation: write

Same code with release 1.1.1 works as expected
I've tested it with  uWSGI-2.0.14 and gunicorn-19.7.1

Did you check the read/write permissions?

Yes. In the following code:
    def append_chunk(self, chunk, chunk_size=None, save=True):
        self.file.close()
        self.file.open(mode='ab')  # mode = append+binary

First line closes the file. But the second line opens the file in read mode, not in 'ab' mode, as requested.

Same issue, with 1.1.2 and using runserver:
 File "<path_to_virtualenv>/lib/python3.5/site-packages/chunked_upload/models.py", line 69, in append_chunk
    self.file.write(chunk.read())
io.UnsupportedOperation: write

I juste tested the 1.1.1 and it works.

Version 1.1.2 works with Django 1.11.0. Apparently it was due to this bug:

https://github.com/django/django/commit/ac1975b18b5a33234284bec86e5a5bb44a4af976

Thanks @kansch!
The problem was the Django version. Updating from 1.10 to 1.11 fixed the problem.


Files don't get recompiled if require-macro file changes

If i change my macros file, included via require-macros, the file does not properly get reapplied. For it to apply the changes, I currently need to make a minor change in the file I want to have recompiled.
Expected behaviour
Changing a macro causes all files that require-macro it to be recompiled

I think I've run into this before... I don't think I can solve it in a general sense without performing static analysis. I honestly can't think of a way that doesn't involve a huge amount of work. I currently rm -r ~/.config/nvim/lua when I perform my package updating / dotfile syncing which solves any of these inconsistency problems. I'll give it a little more thought.
Maybe I could make it so if you change a file ending in macros.fnl (which I already kinda treat as a special file) everything gets recompiled.
I should probably simplify things so if a file has changed I recompile everything, if nothing changed I do nothing 🤔 I think that's a better approach and fits the use case just fine tbh.

 By only compiling changed files I save maybe 2ms but incur weirdness like this. I think I'll check for any *.fnl changes in the dir, if there are any I'll recompile everything.

Yea, I'd argue just checking for any fennel files to change is more than enough. When I'm actively working on config it's reasonable to say "hey I'll tolerate the 2ms increase in startup time" :P And conditional partial recompilation is always a finnicky, difficult subject that's prone to breaking!
I agree with recompiling everything on change 👍🏻

It would only be 2ms if something has changed, is what I mean. So it's
really silly that I'm only compiling what changed when all the cost is in
loading the compiler. I'm completely guessing at times, but I want to
optimise the "nothing changed" case, the "something changed" branch can
afford to be a tiiiiny bit slower imo.
On Sun, 9 May 2021, 11:58 ElKowar, @.***> wrote:

Yea, I'd argue just checking for any fennel files to change is more than
enough. When I'm actively working on config it's reasonable to say "hey
I'll tolerate the 2ms increase in startup time" :P And conditional partial
recompilation is always a finnicky, difficult subject that's prone to
breaking!
I agree with recompiling everything on change 👍🏻
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Olical/aniseed/issues/41#issuecomment-835781313, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACM6XKG7GYXA26PBWWGKT3TMZTFFANCNFSM44N644UQ
.

yea exactly "something has changed" is only gonna happen while I'm actively working on my config - where it really doesn't matter. Fully agree here!

Should be fixed on develop 😄


cypress-configuration Depends on "Vulnerable" inflight Library

While working on a snyk vunability issue (https://security.snyk.io/vuln/SNYK-JS-INFLIGHT-6095116 ) I've gone through all our dependencies.
It sees like this package has a transitive dependency to inflight through the package glob.
Updating to the latest version of glob resolves this issue.
You might want to take a look at these issues as well while i resarched about this issue.
https://github.com/mochajs/mocha/issues/5148
https://github.com/karma-runner/karma/issues/3888
https://www.npmjs.com/package/inflight

The most recent version of @badeball/cypress-cucumber-preprocessor no longer depends on this package (ie. this repository). Hence, this repository will be archived and the package discontinued. Hence, closing, as I will not be making any changes to it.


[ARCTIC-1704][BUG] exclude hadoop-client-api

fixed #1704

Why are the changes needed?
Class conflict due to hadoop-client-api referenced by spark3.3
Brief change log
exclude hadoop-client-api
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before making a pull request

Documentation

Does this pull request introduces a new feature? (no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Thanks  for your contribution. BTW, Have you done any local testing after modifying the dependencies?


Add aliases for Tibea TW Z3 and CLA60 TW

Z2M publishes these different names, thus the aliases

Thanks. LGTM

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.739%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1926

Relevant Lines:
2300

💛  - Coveralls


Some replays still not loading (Unexpected type)

Description

I was following the previous issue (https://github.com/space-wizards/space-station-14/issues/30801) and trying to load replay after the fix was released and was mentioned in the previous issue. But I am still getting errors and the replay isn't loading or starting.  The error happens at least in this replay (62341). It was played 2024/08/11.
Reproduction

Start the Space Station 14 launcher, drag the replay zip normally.

Try to close errors either from the big red "Try load with.." button or from the corner close X-button. It gives the first errors here, but it seems to progress further with the load of the replay (see Screenshot 1 and Screenshot 2).
It proceeds to "Direct Connect" menu and after clicking the "Direct Connect" it tries to connect to the host, but fails (Screenshot 3).
After that it starts the 1/5 loading. It first throws some errors which have increasing id or coordinate numbers (Screenshot 4) so it looks like it is still progressing with the actual replay load process?
But when it gets to the 2/5 loading phase it seems to get "stuck" it looks like the loading process is looping from the start, passing 1/5 without errors and ending up to the same error in the phase 2/5 (Screenshot 5).

Screenshots

Screenshot 1:

Screenshot 2:

Screenshot 3:

Screenshot 4:

Screenshot 5:

Additional context

(https://github.com/space-wizards/space-station-14/issues/30801) <- might have fixed some replays? But it seems to me that some issues still exists while trying to load replays.

2024/08/11

The pr isn't going to fix old replays unless you manually backport a fix.


Fix etc0 description

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix_document_backend" git@github.com:skohar/swarm.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix_document_backend" git@github.com:skohar/swarm.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

LGTM @moxiegirl @SvenDowideit

Seems like this was fixed in the meantime in other docs update, closing this one but thanks for opening @skohar


BAU: log error in case of get-token failure but display generic 500 page

Change description
Previously we were displaying the error from Azure AD error back to the user (I guess for developer convenience but this is not best practice security wise) this changes it to log the error internally and display a generic 500 message

[ ] Unit tests and other appropriate tests added or updated
[ ] README and other documentation has been updated / added (if needed)
[x] Commit messages are meaningful and follow good commit message guidelines (e.g. "FS-XXXX: Add margin to nav items preventing overlapping of logo")

How to test
Make secret key invalid locally, 500 page should display and error should be logged in console.
Screenshots of UI changes (if applicable)

Maybe a test wouldn't hurt though.

@samuelhwilliams added a test in aa6e757


Support for llama-cpp-python server

Feature request
Currently llama-cpp-python provides server package which acts like a drop-in replacement for the OpenAI API.
Is there any specific langchain LLM class which supports the above server or do we need to alter the existing OpenAI class with a different openai_api_base ?
Motivation
I would like to have a dedicated machine or host which runs only the llama-cpp-python server wheres as the client which uses langchain should interact with just like we are doing with OpenAI.
Your contribution
I would like to contribute but before that I need to check if there's any solution already available.

@dosu-bot I don't want to use LlamaAPI  and the above mentioned LlamaCppEmbeddings class directly uses llama-cpp-python package not it's server. See, I don't want to include the model path anywhere in the codebase. Since I already have a server running with all the parameters defined.

@dosu-bot I don't want to use LlamaAPI and the above mentioned LlamaCppEmbeddings class directly uses llama-cpp-python package not it's server. See, I don't want to include the model path anywhere in the codebase. Since I already have a server running with all the parameters defined.

I have been modifying the openai class with my own api location. It works OK, but I have not been successful in creating embeddings, have you tried such a thing?

You should do a number of things:

Follow this guide. It explains how to modify the api_like_OAI.py file for the Llamacpp server example to strictly follow the same API like OpenAI:

Then you can fake OpenAI llm by replacing the address with your local address:
os.environ[
        "OPENAI_API_KEY"
    ] = "sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"  # can be anything
os.environ["OPENAI_API_BASE"] = "http://localhost:8081/v1"
os.environ["OPENAI_API_HOST"] = "http://localhost:8081"
# TODO make it using a proper subclassing for this specialized object
llm = OpenAI(
    model_name="text-davinci-003",  # can be anything indeed
    temperature=temperature,
    openai_api_base="http://localhost:8081/v1",
    max_tokens=max_new_tokens,
    top_p=top_p,
    model_kwargs=dict(
        openai_key="sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
        top_k=top_k,
    ),
    presence_penalty=0.0,
    n=1,
    best_of=1,
    batch_size=20,
    logit_bias={},
    streaming=True
)

Hi @CarloNicolini , I have my llama2-chat model running using llama-cpp-python[server] , using the above solutions , I just have to use the OpenAI class , and  it should work right ?

Hi @CarloNicolini , I have my llama2-chat model running using llama-cpp-python[server] , using the above solutions , I just have to use the OpenAI class , and it should work right ?

Yes it works but you need also to setup the OPENAI_API_KEY and OPENAI_API_HOST environment variables.

This worked for me
from langchain_openai import OpenAI
OpenAI(openai_api_base=os.environ.get("LLAMACPP_API_ENDPOINT", "http://localhost:8080/"), openai_api_key="hello.world")


fix(*): Fixes our use of deprecated functions

Also addresses several clippy lints across the tests and examples

thanks!


Clang on Windows: 't' cannot be thread local when declared 'dllexport'

Trying to use HIP-CPU on Windows using Clang results in a compiler error:
deps/hip-cpu/include\hip/../../src/include/hip/detail/runtime.hpp:180:55: error: 't' cannot be thread local when declared 'dllexport'
                static thread_local std::vector<Task> t;
                                                      ^

Note to "self": change hip/hip_defines.h from
#if defined(_WIN32)

to
#if defined(_WIN32) && (!defined(__clang__))

solves this issue. Likely a more sophisticated mechanism will be needed instead of this hotfix.

Should be fixed by https://github.com/ROCm-Developer-Tools/HIP-CPU/commit/e98cd3cc09b212d58e5fd4afaeb6e70f74638ab3. Thank you for reporting it.


GHA to create issue on new IANA release

fixes #169
not sure how you cut releases, but we could also create a PR which already changes the TZ_RELEASE file to reflect the latest release, which you can pull and push?

I tried it on this branch and it created this issue: https://github.com/nilsnolde/timezone-boundary-builder/issues/1


Teku documentation shows an option that may not be available for validator-client

Visit the below link and you will see a section for initial-state which is not even a valid option for validator-client
https://docs.teku.consensys.net/en/latest/Reference/CLI/Subcommands/Validator-Client/
teku validator-client --help in CLI does not show initial-state

Hi @gethwethreth,  `initial-state` shows up just under `h, --help` when using `teku validator-client --help`. I've attached the screen shot here.  Please let me know if you need any additional help.  Thanks!

Going to reopen this one. I'm not sure what version of Teku you're using but --initial-state isn't listed in help for the latest version of teku. I think it was mistakenly present in earlier versions though it was ignored.  If we have --eth1-deposit-contract-address listed we should remove it too as it falls into the same category.


⚠ Bofrost.es has degraded performance

In 0444f77, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1700 ms

Resolved: Bofrost.es performance has improved in befa500 after 6 minutes.


Table css is lost when printing

Hi,
I'm interested in using the data table. The only issue is that the table css is missing on print. Is it possible to include the table CSS on print?
Thanks,
Matt

It would be interesting to get experiment with that. I put this on my todo and will have a look when I have time to. Feel free to experiment yourself too meanwhile since the code is very easy and straightforward

There's a tiny tiny little overflow bug issue while rendering table on only Chrome, but so far the feature can be considered as implemented. It'll be available in the next release.


PN532 class using hardware SPI

Here is the code I have ...
import Adafruit_GPIO.SPI as SPI
import Adafruit_PN532 as PN532

# Configuration for Raspberry Pi hardware SPI:
#CS         = 8
CS         = 24
SPI_PORT   = 0
SPI_DEVICE = 0

# Create an instance of the PN532 class.
pn532 = PN532.PN532(cs=CS, spi=SPI.SpiDev(SPI_PORT, SPI_DEVICE))

# Call begin to initialize communication with the PN532.  Must be done before
# any other calls to the PN532!
pn532.begin()

and here is what gets returned ...
Traceback (most recent call last):
  File "readmifare.py", line 55, in <module>
    pn532.begin()
  File "build/bdist.linux-armv6l/egg/Adafruit_PN532/PN532.py", line 336, in begin
  File "build/bdist.linux-armv6l/egg/Adafruit_GPIO/GPIO.py", line 64, in set_low
  File "build/bdist.linux-armv6l/egg/Adafruit_GPIO/GPIO.py", line 194, in output
IOError: [Errno 22] Invalid argument

Please don't close issues ... when they are not closed

I run in to the same error.
How to setup this library with hardware SPI?

I am in the same situation.
Any ideas..?

Apologies in advance for the large wall of text, but the information about why this problem occurs and how to get around it seems to be a little scattered over the internet. Hopefully bringing my findings together will help some others progress with their projects.
Anyway, I came across this problem this weekend and have now managed to get it working (sort of). There's actually a number of ways to do it, some more elegant than others. The method I tried first and now have working is probably the less elegant, but it works...
Some background to the problem...
The RPi SoC has three hardware SPI modules in total, SPI0, SPI1, and SPI2. The latter two are two of the three auxiliary devices on the SoC. All this information can be found in the BCM2835 ARM Peripherals datasheet. While some models of the RPi use the BCM2836 and BCM2837, this document is (apparently) still correct for those devices.
The 'default' device, and the one you'll see listed if you do an ls /dev/spi* on a Pi with a standard setup is SPI0.... and this is where the problem lies. While there a quite a number of ways to setup this module, of the few things it can't do, LSBFIRST is one (check page 153 of the datasheet to see the available options of SPI0's control register). Therefore, assuming you're working with a Raspberry Pi with a standard setup, you can use the hardware SPI module, but you will have to handle the conversion to lsbfirst in software.
Manually bit-reversing every byte that's both sent and received isn't hard, but it can be costly time-wise. Personally, this whole exercise began by me wanting to learn Python and my impression so far is that it's great at handling data but awful at speed. Therefore, my solution was to hack the Python SPI module that interfaces to the kernel (py-spidev) because it's written in C. In there I ended up modifying SpiDev_writebytes, SpiDev_readbytes and SpiDev_xfer2 to use a LUT to reverse the bits if SPI_LSB_FIRST was set (honestly, it's nothing more than if(self->mode & SPI_LSB_FIRST) {buf[ii] = lsb_first_table[buf[ii] & 0xFF];} where  lsb_first_table is just a 256 byte table of bit-reversed bytes) since each of those functions already iterates through the entire rx/tx buffers anyway. I also commented out the call to set the mode in SpiDev_set_lsbfirst. This all works fine for our purpose here on an RPi, but clearly it's hacky and isn't a clean enough solution for a PR on spidev as it will probably break things for other platforms.
The second (and probably better) solution is to enable and use one of the two aux SPI modules on the Pi as both of these do support hardware LSBFIRST (see the control register tables on pages 22/23/24 of the datasheet). I haven't tried this yet, but I believe adding dtoverlay=spi1-3cs to /boot/config.txt should enable the second module. However, I believe for some RPi models there is then another problem. With the Pi3 (and therefore probably the Pi Zero W too), the bluetooth module uses UART0 and the default serial console is then pushed to UART1. UART1 is the third auxiliary device and shares some resources with SPI1 (and SPI2). Currently, enabling both at the same time causes a conflict and will crash your Pi. The two solutions are therefore to either disable bluetooth (by adding dtoverlay=pi3-disable-bt to /boot/config.txt) so that the console is configured on UART0 or to leave bluetooth enabled on UART0 and disable the console by removing console=serial0,115200 from /boot/cmdline.txt.
Anyway, I hope that helps a little...

Thank you for the contribution. I will continue testing ...

hiya - we've re-written this library to support circuitpython/python, i2c and uart as well! it now also supports hardware SPI using Adafruit_blinka circuitpython API
check it out here https://github.com/adafruit/Adafruit_CircuitPython_PN532


[Release-1.28] - Fix remaining corner cases in containerd certs.d support

Backport fix for Fix remaining corner cases in containerd certs.d support

#9341

Validated using k3s version v1.28.8-rc1+k3s1
Environment Details
Infrastructure
Cloud EC2 instance
Node(s) CPU architecture, OS, and Version:
Ubuntu 22.04
$ cat /etc/rancher/k3s/registries.yaml
---
mirrors:
  docker.io:
    endpoint:
      - https://registry.example.com
      - docker.io
  k8s.gcr.io:
    endpoint:
      - https://registry.example.com
      - k8s.gcr.io
configs:
  registry.example.com:
    auth:
      username: testusername
      password: testpassword
    tls:
      ca_file: /home/ubuntu/ca.pem

Steps to validate

Configure private registry
Create the registries.yaml with the last registry in the endpoint list as the default to /etc/rancher/k3s
Install k3s.
Validate certs.d//hosts.toml is generated

Results from reproducing the issue:
$ k3s -v
k3s version v1.28.7+k3s1 (051b14b2)
go version go1.21.7

$ sudo cat  /var/lib/rancher/k3s/agent/etc/containerd/certs.d/docker.io/hosts.toml
cat: /var/lib/rancher/k3s/agent/etc/containerd/certs.d/docker.io/hosts.toml: No such file or directory

Results from validating the issue:
$ k3s -v
k3s version v1.28.8-rc1+k3s1 (653dd61a)
go version go1.21.8

$ sudo cat  /var/lib/rancher/k3s/agent/etc/containerd/certs.d/k8s.gcr.io/hosts.toml
# File generated by k3s. DO NOT EDIT.

server = "https://k8s.gcr.io/v2"
capabilities = ["pull", "resolve", "push"]

[host."https://registry.example.com/v2"]
  capabilities = ["pull", "resolve"]
  ca = ["/home/ubuntu/ca.pem"]

$ sudo cat  /var/lib/rancher/k3s/agent/etc/containerd/certs.d/docker.io/hosts.toml
# File generated by k3s. DO NOT EDIT.

server = "https://registry-1.docker.io/v2"
capabilities = ["pull", "resolve", "push"]

[host."https://registry.example.com/v2"]
  capabilities = ["pull", "resolve"]
  ca = ["/home/ubuntu/ca.pem"]


Add support for Modular Event Bridge for Log Ingestion (single)

Change summary:

Added the module as an integration module since it is feature agnostic and can be used for shared integrations.
Added the respective tf files for single onboarding case
Added test example for event-bridge integration (single)

Testing:
Validated the changes with single onboarding of actual accounts on AWS.

I don't think delegated_admin needs to appear at all in the single account resources, as it should not affect what is provisioned here at all. It seems as though setting delegated_admin = true would break these single deploys.

Actually we expect the resources in this file to create stacksets for both - an account in single case & management account in org case i.e I was hoping to leverage the same stackset for both.  And in the org case, we don't want to create these stacksets if user provides delegated_admin instead of management account. Hence, we decided upon keeping the condition check.

I would suggest leaving it out for now and then gating all single account only resources with is_organizational once that is implemented.
One thing we can do to avoid confusion is, use this file for solely single case (removing delegated_admin & adding is_organizational). Create a copy of the same in organizational.tf file (but with delegated_admin check) when I push org changes. I'm leaning towards this. Thoughts?

cc: @haresh-suresh

You will need to rebase with main after my merge of the foundational modules

I don't think delegated_admin needs to appear at all in the single account resources, as it should not affect what is provisioned here at all. It seems as though setting delegated_admin = true would break these single deploys.

Actually we expect the resources in this file to create stacksets for both - an account in single case & management account in org case i.e I was hoping to leverage the same stackset for both. And in the org case, we don't want to create these stacksets if user provides delegated_admin instead of management account. Hence, we decided upon keeping the condition check.

I would suggest leaving it out for now and then gating all single account only resources with is_organizational once that is implemented.

One thing we can do to avoid confusion is, use this file for solely single case (removing delegated_admin & adding is_organizational). Create a copy of the same in organizational.tf file (but with delegated_admin check) when I push org changes. I'm leaning towards this. Thoughts?
cc: @haresh-suresh

We discussed this offline, and decided to keep the pattern to reuse resources in main.tf for both single and org. For single case, delegated admin is a noop and have removed its check from this PR. Once we introduce the org changes, will add the condition back since we want to reuse the same stackset code.


feat: support savers stablecoins

Description

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk

Testing

Engineering

Operations

Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #5206   👈

This comment was auto-generated by Graphite.

Tested by @MBMaria - one smolish obvious bug fixed in https://github.com/shapeshift/web/pull/5206/commits/da032b24ecd72b4737d80f9bf564b0d7d0288d37
Merging as this is way better than it is on develop, though three issues were spotted, which have overlap with current prod issues (i.e some of them are already on prod):

ETH deposits sometimes not confirming after Tx on-chain is confirmed, othertimes showing up as confirmed on the modal but - balance doesn't update
Miner fee value changes from confirm to status steps
Error-handling for "not enough fee" withdraws (possibly deposits as well). We currently don't gracefully handle smolish deposits and just error out without much more info there, and without letting the user try again


Try alternate CODEOWNERS layout

As per title, @slinkydeveloper says this fixed stuff for them!

/approve
/lgtm


Add Custom Animation to the Logo

Fixes Issue #108

Closes #108
Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
https://user-images.githubusercontent.com/58919161/201551639-494ce474-a954-4b0d-b254-f1b029e5d061.mp4
Note to reviewers

It's not a video file, nor a gif but an animated svg with data in a json file. This makes it scale without pixelation and saves on space.
The total size of the animated logo is 110kbs
The packages "react-lottie" and "@types/react-lottie" were installed to implement this.

Hello @akuya-ekorot, any progress on the requested changes for this?


Text cursor disappears automatically from Jupyter Notebook cell

Does this issue occur when all extensions are disabled?: Yes/No

Text cursor disappears automatically from Jupyter Notebook cell two seconds after not typing. The original reporter was using Remote, it could be a document update from the remote extension host which triggers the editor to refresh.

While Code on VS Code, below is the error occured
Open Azure ML Studio via VS Code desktop.
The issue is that mouse cursor in a cell disappears without touching any keyboard.
List of extensions insalled on Desktop VS Code


followup on scipy breaking

https://github.com/conda-forge/openblas-feedstock/pull/146

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Is the plan that we merge this and then see if scipy starts working again?

What is the best way to download and install a package built in this PR?

What is the best way to download and install a package built in this PR?

Needs the following in conda-forge.yml plus a rerender:
# TODO: remove after debug
azure:
  store_build_artifacts: true

Already done.

Sorry I didn't check this (was on a phone...), seems you're well on top of things. ;)

Once downloaded you can either:

upload to a personal channel and then pull down like usual with -c yourchannel

Note that you can use
conda install -c /path/to/where/you/unpacked/the/artefact openblas

if you download it directly.

Conclusion: as rgommers said, the errors are due to fortran updates (or more precisely, the automated updates in this PR).

Do we have any idea/intuition why a compiler upgrade would break this (well, aside from compiler regressions)...?


”Cracu Teiului”, ”Dobraia”, ”Dolina”, ”Gruni”, ”Hora Mare” are listed in the drop-down menu

Description:
When user writes ”Cracu Teiului”, ”Dobraia”, ”Dolina”, ”Gruni”, ”Hora Mare” the locations appear in the drop-down menu next to the comune and the county witch is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Cracu Teiului"

Expected results
The location appears in the drop-down menu as "Cracu Teiului, Caraș-Severin(Cornereva)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Dobraia"

Expected results
The location appears in the drop-down menu as "Dobraia, Caraș-Severin(Cornereva)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Dolina"

Expected results
The location appears in the drop-down menu as "Dolina, Caraș-Severin(Cornereva)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Write in the search bar "Gruni"

Expected results
The location appears in the drop-down menu as "Gruni, Caraș-Severin(Cornereva)".

Step 8
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 9
Write in the search bar "Hora Mare"

Expected results
The location appears in the drop-down menu as "Hora Mare, Caraș-Severin(Cornereva)".


chore(package): update npm-pkgbuild to version 5.1.0

:tada: This PR is included in version 5.0.50 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add profile photo for Chantell

Codecov Report
Base: 72.15% // Head: 72.15% // No change to project coverage :thumbsup:

Coverage data is based on head (c8d2a98) compared to base (6e6a5d9).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master       #7   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


visitArrayElement/visitOptionalExpression Error

Comment 확인부탁드립니다!
Current Visitor.js is:
visitArrayElement(e) {
    if (e && e.type === "SpreadElement") {
        return this.visitSpreadElement(e);
    }
    return this.visitOptionalExpression(e);
}

When it should be:
visitArrayElement(e) {
    if (e && e.type === "SpreadElement") {
        return this.visitSpreadElement(e);
    }
    if (e.expression) {
        e.expression = this.visitOptionalExpression(e.expression);
    }
    return e
}

OR
Current Visitor.js is:
visitOptionalExpression(e) {
    if (e) {
        return this.visitExpression(e);
    }
}

When it should be:
visitOptionalExpression(e) {
    if (e.expression) {
        e.expression = this.visitExpression(e.expression);
    }
    return e
}

Because:
Current Visitor class returns:
a = [
    ,
    ,
];

When it should be:
a = [
    a,
    b,
    c
];

Version
The version of @swc/core: 1.2.62

메인 개발자분이 한국분인것 같아 한국어로 댓글답니다!
visitArrayElement 또는 visitOptionalExpression 에 오류가 있어 맨 아래의 예제와 같이 array가 빈 상태로 반환됩니다.
어제 제가 이슈한 'props => properties' 버그도 그렇고 Visitor 클래스에 문제가 조금 많은것 같은데,
개발자님이 보셨을 때 SWC로 커스텀 플러그인을 만들기에는 아직 시기상조의 단계인지 궁금합니다.
사용자로부터 받은 스크립트에서 보안적 이슈들을 제거하고 서버에서 실행시켜주는 서비스에 느린 바벨 대신 사용하려는데,
아직은 불안정한 단계인가 싶어 조금 걱정이 되어 문의드립니다. 특히 보안이랑 관련된 사항이다보니 ㅜㅜ
답답한 바벨을 대체할 수 있는 빠른 트랜스 스크립터 개발에 힘써주시는 강동윤님께 정말 감사의 말씀드립니다!!

Core transforms are stabilized but the plugin system is not powerful enough.
Also, it's not well-tested, and I don't think improving my own plugin system worths it because I'm working on support for babel plugins. (It's almost done.)
With v2, swc will drop support of current plugin APIs and the only plugin API will be one of babel.

Core transforms are stabilized but the plugin system is not powerful enough.
Also, it's not well-tested, and I don't think improving my own plugin system worths it because I'm working on support for babel plugins. (It's almost done.)
With v2, swc will drop support of current plugin APIs and the only plugin API will be one of babel.

Oh my, that really is a great news.
So I am guessing the speed of transcriptors are mostly determined by parsing AST and restructuring part?
I'll be waiting for v2 then :), is it possible for you to give me an idea of when the v2 will be released?

So I am guessing the speed of transcriptors are mostly determined by parsing AST and restructuring part?

I expect babel plugins to be a bottleneck. Even if I call them from the background thread, all javascript code run within a thread. Although parsing is one of the slow parts, the task would be offloaded to a background thread.

is it possible for you to give me an idea of when the v2 will be released?

I'm sorry but I'm not sure about this at the moment. Estimating time is too hard.

However, I think this bug should be solved in v1. @EedoCelsius  will you contribute a PR for it?

I found that babel plugin compatibility would be much harder than I expected.
I'm also considering rust plugin api.
https://github.com/swc-project/swc/issues/1392#issuecomment-873521336

I'll fix the plugin api for now, as babel plugin compat requires more investigation.

Seems related: https://github.com/swc-project/swc/issues/1623


Add instructions for linting and formatting back to CONTRIBUTING.md

What needs to be changed?
As a contributor, I would like documentation for how to ensure my code is formatted properly before submitting PRs.
There used to be a section titled "Submitting a change" that documented the npm run test-and-fix command, which can catch issues recommends running npm run fix:format to fix them.
This information was removed in this PR, so I want to raise this issue before going ahead and adding it back, in case it was intentional and preferred not to be there.
I would like to add these back if there is no objection.
What is the name + path of the page that needs changed?
/CONTRIBUTING.md

Hi Jay! Thanks for filing this issue.
The missing info is here now: https://opentelemetry.io/docs/contributing/pr-checks/