Xbox 360 like launcher for android/pc [suggestion]

Read the title

Weren't there one already? I found some tutorial here at XDA-Developers using a non X360 dedicated launcher. as for PC, IDK.
Aside from that, I don't know if I'm able to incorporate X360's Home Screen (Menu? Dashboard?) into to this very launcher since the XMB Styles were all shares same code as most have same look and functionality.
I might create a new repository for X360's if you can give me some reference, but I can't promise when will I start the project and when will it stable enough for release, or even would I really start it or not. and making one for PC (Windows specifically) is a bit too complicated, so I will skip it probably.
And If you look around this repository, I'm not even that active updating lately.
Also, for my entire life, I haven't seen the real X360 Home Screen, it's variants (like PS3/PSP XMB Screens), how it's behaviour and how it should feel when you navigate through it's menus, as I never own one before.

Well if you have time ill refrence this dashboard ill love to see it on android https://youtu.be/olTeUQbIjoU

Anyway, I'll move this issue to a discussion instead since this is not an issue regarding this app.


make stress,execprog,fuzzer ERROR

During in stage6, I execute "python3 Main.py fuzz" .
The system log reminds me that
make: *** [Makefile:161: execprog] Error 1
make: *** Waiting for unfinished tasks....
make: *** [Makefile:185: stress] Error 1
make: *** [Makefile:158: fuzzer] Error 1
I need assistance in resolving this issue
Thanks!

Sorry. We haven't encountered this error. Can you provide more information about the make error?

I found  someone encountered the same problem as me, you can refer to the following link for details
https://stackoverflow.com/questions/78242292/compile-syzkaller-fuzzer-failed-without-any-error-or-warning


add readme & rules in spanish

I've in the need to share this repository/package with my coworkers and few people of which some of them does not speak English. And I though would be nice to make this contribution. So this repo could reach by more people in Spanish spoken community.
I appreciate any feedback.
Thanks

YES! This is so excellent! I'm so stoked to merge this, as well as any other language translations that people want to submit.
Thanks @falmar!

👍 Now live on standardjs.com

OK, I made a small update to standard-www and now the alternate languages are live on standardjs.com The site nav is still in english though :/

Oh I see... Thanks for accepting @feross ... I'll probably give it a review again to find and fix any typo or grammar mistakes.
@Flet I just took a peek into standard-www. I never used the markdown-styles but is it possible or easy to change the nav bar according to the language or would that require a huge refactor for it?

Oh I just noticed that we're missing a link to the Spanish translation in RULES.md. I'll send a PR.

@falmar it shouldn't be too difficult. I think there might be a more efficient way of dealing with multiple languages that makes adding new languages easier...
Maybe have each one as a sub directory like http://standardjs.com/esla/index.html
It may be easier to accomplish this if we rework the /docs directory to have a directory for each language instead (and we could include a nav file in the native language as well).
Something like:
└── docs
    ├── esla
    │   ├── README.md
    │   └── RULES.md
    └── pbtr
        ├── README.md
        └── RULES.md

...we could also update the site generation to automatically build the links to each translation. This could be good if @feross wants to make a wider call for translations.. we could add them quickly to the site by just rebuilding.

@Flet I don't think it's too bad to maintain the inline links manually for now, especially since we're only linking back to the English version from the translations. As for the navigation links, I'm happy to do whatever you think is best.

I just tweeted about how we're looking for more translations! https://twitter.com/feross/status/822568452330291201


Difference between uploading vs done status

What is the difference between the two statuses? I am uploading video files to S3 and it uploads super fast but will take long from 100% of uploading to receiving headers_received status.
I just need some clarification for UX purposes!
Thank you for this wonderful component.

I am uploading a video file to the server, and the progress bar goes pretty quickly but it's not the correct progress bar because it hasn't been sent to the server yet.

@danielbyun I agree this is an issue... I am not a project owner here, but I'd love to fix this if I find the time.

@danielbyun have you find any solution for that???

I just found a workaround for it - I upload it, then if it at any point fails or the user cancels (by checking the status) I call the server again and delete the file that was uploaded to the cloud.
I hope that helps, and I hope that the documentation for this component can be improved!
This is a great component and I found it very useful.


Updating reference don't work anymore

As described in the Docs under @floating-ui/react it should be possible to update the reference with
 useLayoutEffect(() => {
    reference(referenceElement);
  }, [reference, referenceElement]);

0.14.0 was the last version where this was working. 0.15.0 and above just set the refence once and never update it again. I am using virtual elements (https://floating-ui.com/docs/virtual-elements#usage) to set the position of the floating popup to the mouse cursors click position. With >0.15.0 the Popup is stuck on its first position.

Do you have a CodeSandbox reproduction? Are you using state to store the external element, or a plain ref?

Okay, I see you're using virtual elements, the new positionReference callback ref will allow for that instead.
It was meant to be backwards-compatible but it seems the old technique no longer handles updating properly.

So instead of the reference, we should use positionReference now?

Going forward yes, as it was possible for the old technique to be overwritten if the reference element's ref callback was unstable between renders, e.g. in other component libs which you don't control. So it's more reliable. However, the old way should continue to work which the PR should fix.

Thanks for explaining how to fix it. In the meantime I've had to override this dependency in another dependency because this is a breaking change, but minor version bumps should not include breaking changes so npm is installing 1.1.x and my dependency is expecting things to still work the way they did in 1.0.x.
"overrides": {
    "some-other-dependency": {
      "@floating-ui/core": "1.0.1",
      "@floating-ui/dom": "1.0.1",
      "@floating-ui/react-dom": "1.0.0"
    }
  },

You don't have @floating-ui/react installed, where it's in v0 and minor changes are considered potentially breaking.
So your issue must be different, what problem are you facing?

@akinnee I've merged the PR which closed this issue because it affects @floating-ui/react not @floating-ui/react-dom which you seem to be using, but you can open a new issue with a reproduction using the dependency causing the issue.
To give more context, there were two changes made from v1.0.1 to 1.1.0 and v1.1.1:

In v1.1.0, the layout effect that caused an update when placement, middleware, or strategy changed was removed as it was redundant. The callback ref now changes during render, which causes React to call it with null and then with the new node again, which causes an update anyway. This shouldn't cause a bug unless there's an edge case not being considered.
In v1.1.1, the callback refs now check if the current node stored in the ref is different from the one being invoked with the callback ref, and only then perform a new update. Again, this shouldn't cause an issue in theory because React always calls it with null before the next node, and if it's a different node, the !== check handles it also.

So if you try out overrides with v1.1.0 vs. v1.1.1 of @floating-ui/react-dom, it can help identify if it was the layout effect being removed, vs. the guard check causing the issue. And even then, it seems like the dependency itself likely isn't using autoUpdate and was relying on flaky re-renders to cause updates, which also affected https://github.com/floating-ui/floating-ui/issues/2086#issuecomment-1369891879.

@atomiks Thanks for the additional info. Followup issue here, but it sounds like you can mark it resolved. https://github.com/floating-ui/floating-ui/issues/2096


external-dns: Add trailing '.' to txt-prefix

This is an improvement/fix to #343, to achieve the originally stated
goal.  external-dns prepends exactly the txt-prefix to created TXT
metadata records, so the . separator needs to be added explicitly.

bors r=sameersbn


rapidfuzz requires cmake during build

Building wheel for cryptography (pyproject.toml): started
      Building wheel for cryptography (pyproject.toml): finished with status 'error'
      error: subprocess-exited-with-error

      × Building wheel for cryptography (pyproject.toml) did not run successfully.
      │ exit code: 1
      ╰─> [174 lines of output]
          /tmp/pip-build-env-lb11ank8/overlay/lib/python3.11/site-packages/setuptools/config/pyprojecttoml.py:66: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*.
            config = read_configuration(filepath, True, ignore_option_errors, dist)
          running bdist_wheel
          running build
          running build_py
          creating build
          creating build/lib.linux-x86_64-cpython-311
          creating build/lib.linux-x86_64-cpython-311/cryptography
          copying src/cryptography/__init__.py -> build/lib.linux-x86_64-cpython-311/cryptography
          copying src/cryptography/fernet.py -> build/lib.linux-x86_64-cpython-311/cryptography
          copying src/cryptography/exceptions.py -> build/lib.linux-x86_64-cpython-311/cryptography
          copying src/cryptography/__about__.py -> build/lib.linux-x86_64-cpython-311/cryptography
          copying src/cryptography/utils.py -> build/lib.linux-x86_64-cpython-311/cryptography
          creating build/lib.linux-x86_64-cpython-311/cryptography/x509
          copying src/cryptography/x509/__init__.py -> build/lib.linux-x86_64-cpython-311/cryptography/x509
          copying src/cryptography/x509/name.py -> build/lib.linux-x86_64-cpython-311/cryptography/x509
          copying src/cryptography/x509/general_name.py -> build/lib.linux-x86_64-cpython-311/cryptography/x509
          copying src/cryptography/x509/certificate_transparency.py -> build/lib.linux-x86_64-cpython-311/cryptography/x509
          copying src/cryptography/x509/ocsp.py -> build/lib.linux-x86_64-cpython-311/cryptography/x509
          copying src/cryptography/x509/oid.py -> build/lib.linux-x86_64-cpython-311/cryptography/x509
          copying src/cryptography/x509/base.py -> build/lib.linux-x86_64-cpython-311/cryptography/x509
          copying src/cryptography/x509/extensions.py -> build/lib.linux-x86_64-cpython-311/cryptography/x509
          creating build/lib.linux-x86_64-cpython-311/cryptography/hazmat
          copying src/cryptography/hazmat/__init__.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat
          copying src/cryptography/hazmat/_oid.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat
          creating build/lib.linux-x86_64-cpython-311/cryptography/hazmat/backends
          copying src/cryptography/hazmat/backends/__init__.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/backends
          creating build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings
          copying src/cryptography/hazmat/bindings/__init__.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings
          creating build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives
          copying src/cryptography/hazmat/primitives/__init__.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives
          copying src/cryptography/hazmat/primitives/poly1305.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives
          copying src/cryptography/hazmat/primitives/_cipheralgorithm.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives
          copying src/cryptography/hazmat/primitives/hashes.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives
          copying src/cryptography/hazmat/primitives/padding.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives
          copying src/cryptography/hazmat/primitives/cmac.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives
          copying src/cryptography/hazmat/primitives/_asymmetric.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives
          copying src/cryptography/hazmat/primitives/hmac.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives
          copying src/cryptography/hazmat/primitives/keywrap.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives
          copying src/cryptography/hazmat/primitives/constant_time.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives
          copying src/cryptography/hazmat/primitives/_serialization.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives
          creating build/lib.linux-x86_64-cpython-311/cryptography/hazmat/backends/openssl
          copying src/cryptography/hazmat/backends/openssl/__init__.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/backends/openssl
          copying src/cryptography/hazmat/backends/openssl/ec.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/backends/openssl
          copying src/cryptography/hazmat/backends/openssl/aead.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/backends/openssl
          copying src/cryptography/hazmat/backends/openssl/decode_asn1.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/backends/openssl
          copying src/cryptography/hazmat/backends/openssl/rsa.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/backends/openssl
          copying src/cryptography/hazmat/backends/openssl/cmac.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/backends/openssl
          copying src/cryptography/hazmat/backends/openssl/ciphers.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/backends/openssl
          copying src/cryptography/hazmat/backends/openssl/utils.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/backends/openssl
          copying src/cryptography/hazmat/backends/openssl/backend.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/backends/openssl
          creating build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/openssl
          copying src/cryptography/hazmat/bindings/openssl/__init__.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/openssl
          copying src/cryptography/hazmat/bindings/openssl/_conditional.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/openssl
          copying src/cryptography/hazmat/bindings/openssl/binding.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/openssl
          creating build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/asymmetric
          copying src/cryptography/hazmat/primitives/asymmetric/__init__.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/asymmetric
          copying src/cryptography/hazmat/primitives/asymmetric/ec.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/asymmetric
          copying src/cryptography/hazmat/primitives/asymmetric/ed25519.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/asymmetric
          copying src/cryptography/hazmat/primitives/asymmetric/dsa.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/asymmetric
          copying src/cryptography/hazmat/primitives/asymmetric/x25519.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/asymmetric
          copying src/cryptography/hazmat/primitives/asymmetric/padding.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/asymmetric
          copying src/cryptography/hazmat/primitives/asymmetric/ed448.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/asymmetric
          copying src/cryptography/hazmat/primitives/asymmetric/dh.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/asymmetric
          copying src/cryptography/hazmat/primitives/asymmetric/rsa.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/asymmetric
          copying src/cryptography/hazmat/primitives/asymmetric/x448.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/asymmetric
          copying src/cryptography/hazmat/primitives/asymmetric/types.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/asymmetric
          copying src/cryptography/hazmat/primitives/asymmetric/utils.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/asymmetric
          creating build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/serialization
          copying src/cryptography/hazmat/primitives/serialization/__init__.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/serialization
          copying src/cryptography/hazmat/primitives/serialization/pkcs7.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/serialization
          copying src/cryptography/hazmat/primitives/serialization/base.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/serialization
          copying src/cryptography/hazmat/primitives/serialization/ssh.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/serialization
          copying src/cryptography/hazmat/primitives/serialization/pkcs12.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/serialization
          creating build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/ciphers
          copying src/cryptography/hazmat/primitives/ciphers/__init__.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/ciphers
          copying src/cryptography/hazmat/primitives/ciphers/aead.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/ciphers
          copying src/cryptography/hazmat/primitives/ciphers/base.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/ciphers
          copying src/cryptography/hazmat/primitives/ciphers/algorithms.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/ciphers
          copying src/cryptography/hazmat/primitives/ciphers/modes.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/ciphers
          creating build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/kdf
          copying src/cryptography/hazmat/primitives/kdf/__init__.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/kdf
          copying src/cryptography/hazmat/primitives/kdf/pbkdf2.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/kdf
          copying src/cryptography/hazmat/primitives/kdf/kbkdf.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/kdf
          copying src/cryptography/hazmat/primitives/kdf/concatkdf.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/kdf
          copying src/cryptography/hazmat/primitives/kdf/hkdf.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/kdf
          copying src/cryptography/hazmat/primitives/kdf/x963kdf.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/kdf
          copying src/cryptography/hazmat/primitives/kdf/scrypt.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/kdf
          creating build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/twofactor
          copying src/cryptography/hazmat/primitives/twofactor/__init__.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/twofactor
          copying src/cryptography/hazmat/primitives/twofactor/totp.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/twofactor
          copying src/cryptography/hazmat/primitives/twofactor/hotp.py -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/primitives/twofactor
          running egg_info
          writing src/cryptography.egg-info/PKG-INFO
          writing dependency_links to src/cryptography.egg-info/dependency_links.txt
          writing requirements to src/cryptography.egg-info/requires.txt
          writing top-level names to src/cryptography.egg-info/top_level.txt
          reading manifest file 'src/cryptography.egg-info/SOURCES.txt'
          reading manifest template 'MANIFEST.in'
          warning: no files found matching '*.c' under directory 'src/_cffi_src'
          warning: no files found matching '*.h' under directory 'src/_cffi_src'
          no previously-included directories found matching 'docs/_build'
          warning: no previously-included files found matching 'vectors'
          warning: no previously-included files matching '*' found under directory 'vectors'
          warning: no previously-included files found matching 'src/rust/target'
          warning: no previously-included files matching '*' found under directory 'src/rust/target'
          warning: no previously-included files matching '*' found under directory '.github'
          warning: no previously-included files found matching 'release.py'
          warning: no previously-included files found matching '.readthedocs.yml'
          warning: no previously-included files found matching 'ci-constraints-requirements.txt'
          warning: no previously-included files found matching 'mypy.ini'
          adding license file 'LICENSE'
          adding license file 'LICENSE.APACHE'
          adding license file 'LICENSE.BSD'
          writing manifest file 'src/cryptography.egg-info/SOURCES.txt'
          copying src/cryptography/py.typed -> build/lib.linux-x86_64-cpython-311/cryptography
          creating build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust
          copying src/cryptography/hazmat/bindings/_rust/__init__.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust
          copying src/cryptography/hazmat/bindings/_rust/_openssl.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust
          copying src/cryptography/hazmat/bindings/_rust/asn1.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust
          copying src/cryptography/hazmat/bindings/_rust/exceptions.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust
          copying src/cryptography/hazmat/bindings/_rust/ocsp.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust
          copying src/cryptography/hazmat/bindings/_rust/pkcs7.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust
          copying src/cryptography/hazmat/bindings/_rust/x509.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust
          creating build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl
          copying src/cryptography/hazmat/bindings/_rust/openssl/__init__.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl
          copying src/cryptography/hazmat/bindings/_rust/openssl/dh.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl
          copying src/cryptography/hazmat/bindings/_rust/openssl/dsa.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl
          copying src/cryptography/hazmat/bindings/_rust/openssl/ed25519.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl
          copying src/cryptography/hazmat/bindings/_rust/openssl/ed448.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl
          copying src/cryptography/hazmat/bindings/_rust/openssl/hashes.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl
          copying src/cryptography/hazmat/bindings/_rust/openssl/hmac.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl
          copying src/cryptography/hazmat/bindings/_rust/openssl/kdf.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl
          copying src/cryptography/hazmat/bindings/_rust/openssl/poly1305.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl
          copying src/cryptography/hazmat/bindings/_rust/openssl/x25519.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl
          copying src/cryptography/hazmat/bindings/_rust/openssl/x448.pyi -> build/lib.linux-x86_64-cpython-311/cryptography/hazmat/bindings/_rust/openssl
          warning: build_py: byte-compiling is disabled, skipping.

          running build_ext
          running build_rust

              =============================DEBUG ASSISTANCE=============================
              If you are seeing a compilation error please try the following steps to
              successfully install cryptography:
              1) Upgrade to the latest pip and try again. This will fix errors for most
                 users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip
              2) Read https://cryptography.io/en/latest/installation/ for specific
                 instructions for your platform.
              3) Check our frequently asked questions for more information:
                 https://cryptography.io/en/latest/faq/
              4) Ensure you have a recent Rust toolchain installed:
                 https://cryptography.io/en/latest/installation/#rust

              Python: 3.11.4
              platform: Linux-5.15.0-1039-azure-x86_64-with-glibc2.35
              pip: n/a
              setuptools: 67.8.0
              setuptools_rust: 1.6.0
              rustc: n/a
              =============================DEBUG ASSISTANCE=============================

          error: can't find Rust compiler

          If you are using an outdated pip version, it is possible a prebuilt wheel is available for this package but pip is not able to install from it. Installing from the wheel would avoid the need for a Rust compiler.

          To update pip, run:

              pip install --upgrade pip

          and then retry package installation.

          If you did intend to build this package from source, try installing a Rust compiler from your system package manager and ensure it is on the PATH during installation. Alternatively, rustup (available at [https://rustup.rs)](https://rustup.rs%29/) is the recommended way to download and update the Rust compiler toolchain.

          This package requires Rust >=1.56.0.
          [end of output]

  # Required by "cryptography" during its build on Linux.
  on_linux do
    depends_on "rust" => :build
  end


Not working for iOS

overflow:hidden does not work on Mobile Safari as expected - it does not prevent scrolling.
The only way to prevent a scroll - is to prevent touch event.

Added a note to the README in a426e8c03524ace7936eb7eab26461369d514705


Found a bug in Chrome

Found a bug where sites wouldn't load in chrome (Cuttent (23rd september 2021) version) and eventually crash the tab. I restarted my PC, deinstalled chrome, reinstalled chrome and then tried to systematically disable my extensions one by one and when I disabled this one the sites would suddenly load again, so I suspect that is a bug of this browser extension

I am having the same issue. As of a few days ago, some particular websites will hang while this extension is enabled. Issue occurs every time on specific URLs but never occurs on others.
Chrome reports a "RESULT_CODE_HUNG" error. Typical troubleshooting steps for this error (restarting chrome, deleting browser cache) do not work.


Support for Intelino Smart Train

Hello,
I have a hard time connecting to Intelino Smart Train.
martin@bono:~$ scratch_link
2021-12-24 21:06:48,682 Certificate is ready in FireFox NSS DB: /home/martin/.mozilla/firefox/qk78wey4.Default User
2021-12-24 21:06:48,689 Certificate is ready in FireFox NSS DB: /home/martin/.mozilla/firefox/qk78wey4.Default User
2021-12-24 21:06:48,703 Certificate is ready in FireFox NSS DB: /home/martin/.mozilla/firefox/qk78wey4.Default User/chrome_debugger_profile
2021-12-24 21:06:48,712 Certificate is ready in FireFox NSS DB: /home/martin/.mozilla/firefox/qb752b1e.ff75
2021-12-24 21:06:48,719 Certificate is ready in FireFox NSS DB: /home/martin/.mozilla/firefox/u16lwrru.default
2021-12-24 21:06:48,727 Certificate is ready in FireFox NSS DB: /home/martin/.mozilla/firefox/fq9mqhp8.Martin
2021-12-24 21:06:48,974 Certificate is ready in FireFox NSS DB: /home/martin/.mozilla/firefox/no8dwo1j.Default User
2021-12-24 21:06:48,983 Certificate is ready in FireFox NSS DB: /home/martin/.mozilla/firefox/jmegri7g.p1
2021-12-24 21:06:48,991 Certificate is ready in FireFox NSS DB: /home/martin/.mozilla/firefox/ya14x5g6.temp
2021-12-24 21:06:48,999 Certificate is ready for Chrome
2021-12-24 21:06:49,016 Started scratch-link
2021-12-24 21:06:56,467 Start session for web socket path: /scratch/ble
2021-12-24 21:07:06,878 Can not scan BLE devices. Check BLE controller.

martin@bono:~$ bluetoothctl
Agent registered
[CHG] Controller 40:74:E0:9F:B6:B2 Pairable: yes
[bluetooth]# devices
Device 00:A0:50:B6:45:0E intelino J-1
Device 50:81:D8:01:8A:13 Sony PLAYSTATION(R)3 Controller
Device 98:D3:31:FB:14:F7 HC-06
Device 30:21:03:00:04:85 Creative T100
Device 20:1B:88:14:AD:70 Mi True Wireless EBs Basic 2
Device 34:88:5D:3F:5D:38 Bluetooth Mouse M557
Device 00:1B:FB:C3:8C:64 Sony PLAYSTATION(R)3 Controller
Device 20:01:08:00:A9:32 Escape 220
Device 74:51:BA:ED:0C:A5 Mi Phone
[bluetooth]# connect 00:A0:50:B6:45:0E
Attempting to connect to 00:A0:50:B6:45:0E
[CHG] Device 00:A0:50:B6:45:0E Connected: yes
Connection successful
[NEW] Primary Service (Handle 0x8746)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service000a
	00001801-0000-1000-8000-00805f9b34fb
	Generic Attribute Profile
[NEW] Characteristic (Handle 0x75eb)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service000a/char000b
	00002a05-0000-1000-8000-00805f9b34fb
	Service Changed
[NEW] Descriptor (Handle 0xf360)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service000a/char000b/desc000d
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[NEW] Primary Service (Handle 0x80f0)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service000e
	0000180a-0000-1000-8000-00805f9b34fb
	Device Information
[NEW] Characteristic (Handle 0x75eb)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service000e/char000f
	00002a24-0000-1000-8000-00805f9b34fb
	Model Number String
[NEW] Characteristic (Handle 0x75eb)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service000e/char0011
	00002a25-0000-1000-8000-00805f9b34fb
	Serial Number String
[NEW] Characteristic (Handle 0x75eb)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service000e/char0013
	00002a26-0000-1000-8000-00805f9b34fb
	Firmware Revision String
[NEW] Primary Service (Handle 0x80f0)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service0015
	0000180f-0000-1000-8000-00805f9b34fb
	Battery Service
[NEW] Characteristic (Handle 0x75eb)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service0015/char0016
	00002a19-0000-1000-8000-00805f9b34fb
	Battery Level
[NEW] Descriptor (Handle 0x7360)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service0015/char0016/desc0018
	00002904-0000-1000-8000-00805f9b34fb
	Characteristic Format
[NEW] Descriptor (Handle 0x7360)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service0015/char0016/desc0019
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[NEW] Primary Service (Handle 0x80f0)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service001a
	00060000-f8ce-11e4-abf4-0002a5d5c51b
	Vendor specific
[NEW] Characteristic (Handle 0x75eb)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service001a/char001b
	00060001-f8ce-11e4-abf4-0002a5d5c51b
	Vendor specific
[NEW] Descriptor (Handle 0x76a0)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service001a/char001b/desc001d
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[NEW] Descriptor (Handle 0x76a0)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service001a/char001b/desc001e
	00002901-0000-1000-8000-00805f9b34fb
	Characteristic User Description
[NEW] Primary Service (Handle 0x80f0)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service001f
	43dfd9e9-17e5-4860-803d-9df8999b0d7a
	Vendor specific
[NEW] Characteristic (Handle 0x75eb)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service001f/char0020
	40c540d0-344c-4d0d-a1da-9cc260b82d43
	Vendor specific
[NEW] Descriptor (Handle 0x77a0)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service001f/char0020/desc0022
	00002901-0000-1000-8000-00805f9b34fb
	Characteristic User Description
[NEW] Primary Service (Handle 0x80f0)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service0023
	4dad4922-5c86-4ba7-a2e1-0f240537bd08
	Vendor specific
[NEW] Characteristic (Handle 0x75eb)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service0023/char0024
	a4b80869-a84c-4160-a3e0-72fa58ff480e
	Vendor specific
[NEW] Descriptor (Handle 0x7aa0)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service0023/char0024/desc0026
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[NEW] Descriptor (Handle 0x7aa0)
	/org/bluez/hci0/dev_00_A0_50_B6_45_0E/service0023/char0024/desc0027
	00002901-0000-1000-8000-00805f9b34fb
	Characteristic User Description
[CHG] Device 00:A0:50:B6:45:0E ServicesResolved: yes

Pairing doesn't work. Probably the train is not pairable.
[bluetooth]# pair 00:A0:50:B6:45:0E
Attempting to pair with 00:A0:50:B6:45:0E
[CHG] Device 00:A0:50:B6:45:0E Connected: yes
Failed to pair: org.bluez.Error.AuthenticationFailed
[CHG] Device 00:A0:50:B6:45:0E Connected: no

Using https://scratch.intelino.com/
I can connect to the device

I replaced deviceName = dev.getValueText(0x08) with deviceName = dev.getValueText(0x09) and the device was found. Unfortunately the device disconnects shortly after it is connected.

Attaching output of scratch_link -d: debug.log.gz

Hi @zdila  Thank you for sharing the issues.
It is great that you found that dev.getValueText(0x09) make pyscrlink connect to Intelino Smart Train. I will improve the pyscrlink code to try out both dev.getValueText(0x09) and dev.getValueText(0x08.
Regarding the disconnection, I checked the debug.log. Connection was established, and notification start was requested to the device, and some data write were made to the device. After that It looks like that the Scarch for Intelino Smart Train disconnects the connection to pyscrlink. Here I quote a part of debug.log. The line "scratch closed session" means that something is happening in the scratch side.
2021-12-25 12:17:27,618 start to notify
2021-12-25 12:17:27,618 in handle loop
2021-12-25 12:17:27,618 start recv_request
2021-12-25 12:17:27,618 scratch closed session
2021-12-25 12:17:27,618 received 1005 (no status code [internal]); then sent 1005 (no status code [internal])
2021-12-25 12:17:27,618 BLE session disconnected
2021-12-25 12:17:27,618 BLE session connected=0
2021-12-25 12:17:27,618 all BLE sessions disconnected
2021-12-25 12:17:27,618 disconnect from the BLE peripheral: intelino J-1

In the log, I did not find any notification message from the device. So my mere guess is that scratch for Intelino Smart Train timed out to wait for notifications from the device.
At this moment, I can not think of further way to investigate this issue. I wanted to take a look in the code of scratch for Intelino Smart Train, but I can not find it on the net...

Thanks for your reply. I've managed to create a dump of websocket communication from working scratch-link on MacOS. Will it help? It contains all messages from connecting to the train till I manual disconnection. When connected, train sends many messages (probably its status, like current speed or what color did it just scan.
intelino.txt.gz

WS dump when using pyscrlink: pyscrlink-ws-dump.json.gz

It looks like pyscrlink is not receiving characteristics change (or not sending them via WS). I tried following steps using nRF Connect Android app:

connect to the device
write b7 02 07 0a to service 43dfd9e9-17e5-4860-803d-9df8999b0d7a , characteristic 40c540d0-344c-4d0d-a1da-9cc260b82d43
subscribe to indications on service 4dad4922-5c86-4ba7-a2e1-0f240537bd08 , characteristic a4b80869-a84c-4160-a3e0-72fa58ff480e
send 07 00  to service 43dfd9e9-17e5-4860-803d-9df8999b0d7a , characteristic 40c540d0-344c-4d0d-a1da-9cc260b82d43
send 41 01 01  to service 43dfd9e9-17e5-4860-803d-9df8999b0d7a , characteristic 40c540d0-344c-4d0d-a1da-9cc260b82d43

then I started recording and saw many notifications on characteristic a4b80869-a84c-4160-a3e0-72fa58ff480e with bytes b7 12 03 00 00 ff 01 00 00 00 00 01 03 00 00 06 10 42 00 00. This part is missing in pyscrlink WS communication and could be the cause of disconenction

Meanwhile I've written Scratch Link for Linux and Intelino smart train in nodejs: https://github.com/zdila/intelino-smart-train-scratch-link-linux

Meanwhile I've written Scratch Link for Linux and Intelino smart train in nodejs: https://github.com/zdila/intelino-smart-train-scratch-link-linux

@zdila It's great that your wrote nodejs version of scratch-link :) I'm interested in your node js code. Is it working good for your device? If so, that's a good step forward.
Thank you for sharing the wireshark and nRF Connect logs. They helped me to have the wider view. From the pyscrlink logs, pyscrlink received the write and the notification subscribe requests from Scratch and handled them. However, there is no notification from the device. My current guess is that notification subscribe handling by pyscrlink is not correct (there could be a possibility that layers below pyscrlink is not working correctly, but if your nodejs version is working good, this is not the case).
Still I need some more time to think about the notification subscription handling.

I have spent some time about BLE Characteristic and notification. And learned that CCCD (Client Characteristic Configuration Descriptor) is the key to enable notification. Current pyscrlink assumes that CCCD comes just after the Characteristic Value declaration, but the spec warns that we should not assumes such an order. If this assumption in pyscrlink is wrong for the Intelino Smart Train, it could be the cause of the no notification from the device.
I made a commit 2d489321d07a to dev branch to avoid the assumption in pyscrlink. Now pyscrlink looks up the CCCD to enable notification. I wish this fix the issue with Intelino Smart Train.
@zdila If you have time to afford, please try the dev branch tip.

I tried the dev branch with your commit but unfortunatley the problem is thill there.
Yes, my Node.js version works fine with my Intelino train.

@zdlia Thank you for the quick update. It is my sorrow the problem is still there. At this moment, I have no further idea about the trouble cause. I will remove Intelino statements from the README of pyscrlink.
Anyway, it is good that your node.js version is available for other Intelino users.

Just a comment after looking into your node.js implementation. Oh, it uses DBus interface to communicate with bluetooth side. It's simple and looks stable. Hmm, that could be an option for pyscrlink future improvement.

Yes. There are other Node.js bluetooth alternatives like https://github.com/noble/noble (seems to be multiplatform but I got errors installing it as it failed compiling some native code) or https://github.com/chrvadala/node-ble (also uses D-Bus but it hides for example API for setting BT scanning filter), but using D-Bus directly (https://github.com/dbusjs/node-dbus-next library) it wasn't difficult to utilize BLE on my own :-).
BTW my scratch-link is also faster in finding a device for some reason (it finds it immediately if it is powered on, whereas for pyscrlink it takes couple of seconds). Also pyscrlink is using some loop for getting events which east CPU (in my case it eats  100% of a single core if it fails to connect). I think it is a problem of PyBluez design.

Thank you. The bluetooth libraries situation in Node.js sounds similar as that in Python. There are multiple bluetooth and BLE support libraries. Some of them are old, and not so stable. I has been thinking which bluetooth/BLE library could be the better, but that D-Bus approach sounds the best, at this moment.
Also thank you for sharing your experience on the device finding speed and CPU consumption.  Unfortunately (or fortunately), I have not yet observed them. Will keep them in my mind.

Hello, i'm using pyscrlink on Linux (Ubuntu 20.04) to connect WeDo 2.0 and EV3 Devices. Is it possible to try the Node.js verzion?

@markakis-sch I think it would be more suitable to discuss it at https://github.com/zdila/intelino-smart-train-scratch-link-linux/issues. Node.js version currently ignores bluetooth filter and is hardcoded with intelino string, but it is east to try it with different hardcoded name. Also it doesn't support getServices or getCharacteristics methods as intelino doesn't use them. But I can try to imlement them and you could try (I don't have the hardware). Or maybe your device doesn't use those methods as well.

I have made https://github.com/zdila/scratch-link-ble-linux/ ready for other BLE devices, but had no chance to test it with anything but Intelino smart train.

Yep it would be good to create an issue in scratch-link-ble-linux for the discussion.
My two cents on WeDo and EV3: WeDo is a BLE device, then it's worth trying with scratch-link-ble-linux. On the other hand, Lego EV3 is not a BLE device, but a BT device. Scratch-link-ble-linux looks dedicated to BLE devices at this moment, so EV3 will not work. To support EV3, some more work will be required for scratch-link-ble-linux to support BT Peripheral Protocol.

BTW https://github.com/intelino-code/intelino-trainlib-async-py uses https://github.com/hbldh/bleak

Oh, then bleak can be another choice, in place of bluepy. Bleak looks newer and more active than bluepy. Will think about it :)

BTW my scratch-link is also faster in finding a device for some reason (it finds it immediately if it is powered on, whereas for pyscrlink it takes couple of seconds). Also pyscrlink is using some loop for getting events which east CPU (in my case it eats 100% of a single core if it fails to connect). I think it is a problem of PyBluez design.

I confirm that finding a device (i used a WeDo 2.0) is much slower with pyscrlink than with scratch-link-ble-linux.


Add #1956 to changelog

https://github.com/ruby-grape/grape/pull/1956#issuecomment-632891506

Tacked this to https://github.com/ruby-grape/grape/pull/2060, fixing the build.


Add 3dep-seamless example notebook

PDF version here: 3dep-seamless-example.pdf

I'll push a fix for the linting issue with a few other changes.

Ok, sorry about that -- working on setting up linting in notebooks meow.

working on setting up linting

Ah, that's my bad - I should have given you a heads up on that.
If you install pre-commit, running pre-commit run --all-files will get you set up locally.

Updated some of the wording, linked to the entry in our datacatlog, using stackstac to load into xarray, and updated the plotting slightly.
Thanks @gadomski!


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 12:12:29 on 2023.08.18
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 1, errors out: 0
Original problem ID: 85069
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=85069

Problem has been resolved in 15m 0s at 12:27:29 on 2023.08.18
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 85069


TF_CUDA_VERSION and TF_CUDNN_VERSION can be too specific

If you run ./configure and provide your own TF_CUDA_VERSION and TF_CUDNN_VERSION, you will get an error message if your version is too specific.
For example, setting TF_CUDA_VERSION=7.5.18 will result in an error when nvcc reports a version 7.5. If you set TF_CUDNN_VERSION=5.1.3, you get an error because cudnn.h reports version 5.
I think in previous versions of TensorFlow this didn't happen, and it's only a minor annoyance, but it would be nice to fix this.

Please take a look @gunan. Thanks!

This is still an issue.  @gunan  agreed we can take a look.  I also find this frustrating.  Unless you are doing different version locally it is easier to say nothing and it will compile from the default folders.  If you have multiple versions you will want to point to the correct folder.

@gunan , any updates?


Improve CZ translation

naive translation via DeepL free account
!!! need to be checked before merge to main repo !!!
todo:

[ ] fix nonsense like Trenovat VS Vlak (EN Train)
[ ] should & be replaced by ... a ... in CZ

find someone to check each record


Automated cherry pick of #3465: Remove stale ClusterIP routes after Antrea restart

Fix #3131
Signed-off-by: Hongliang Liu<EMAIL_ADDRESS>

Codecov Report

Merging #3565 (33fe9c5) into release-1.6 (7a79389) will decrease coverage by 21.47%.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           release-1.6    #3565       +/-   ##
================================================
- Coverage        62.89%   41.42%   -21.48%
================================================
  Files              278      324       +46
  Lines            27828    40492    +12664
================================================
- Hits             17503    16773      -730
- Misses            8463    22148    +13685
+ Partials          1862     1571      -291

Flag
Coverage Δ

integration-tests
38.16% <ø> (?)

kind-e2e-tests
?

unit-tests
43.39% <ø> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.


DEV-14421 - Fixes a bug where hbase configuration did not upload to s3

https://datatamr.atlassian.net/browse/DEV-14421

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update the language service plugin docs

Added notes/changed wording for a few pitfalls I fell in while going
through this guide, as well as updated the proxy code to be simpler and
avoid an assertion to ‘any’

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: calebegg sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Sent off CLA via email (since I'm not allowed to use the automated one)

LGTM; merge pending CLA

I emailed CLA to<EMAIL_ADDRESS>yesterday. Not sure what happens next, or what kind of timeline to expect.

I though you just login with your github id and sign it electronically.

Google has a modified CLA we have to sign and email instead, for some
reason.
On Fri, Dec 1, 2017 at 2:31 AM Mohamed Hegazy<EMAIL_ADDRESS>wrote:

I though you just login with your github id and sign it electronically.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/TypeScript-wiki/pull/161#issuecomment-348422726,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAvySD8HBJHUdQfzYOvALbDK5cRFvnfkks5s76tqgaJpZM4QsdPT
.

aah.. i think we have a blanket one with Google. I think we should be fine.

It's not a blanket one, at least, not according to our docs. But I pinged the thread where I emailed the scan, and it seems to have gone through this time (the CLA bot is happy).

I got it today from our legal team. thanks!


RFC: simp to detect, report and ignore inherently looping rewrite rules

Motivation
The simplifier is not very helpful when giving a non-terminating simp set:
variable (P : Nat → Prop)
/--
error: tactic 'simp' failed, nested error:
maximum recursion depth has been reached
use `set_option maxRecDepth <num>` to increase limit
use `set_option diagnostics true` to get diagnostic information
-/
#guard_msgs in
example (a b c : Nat) : P (a + b + c) := by simp [Nat.add_assoc, (Nat.add_assoc _ _ _).symm]

inductive Tree (α : Type) where | node : α → List (Tree α) → Tree α
def Tree.children : Tree α → List (Tree α) | .node _ ts => ts
def Tree.size (t : Tree α) := 1 + Nat.sum (t.children.attach.map (fun ⟨c,_⟩  => c.size))
decreasing_by simp_wf; cases t; simp_all [Tree.children]; decreasing_trivial

/--
error: tactic 'simp' failed, nested error:
maximum recursion depth has been reached
use `set_option maxRecDepth <num>` to increase limit
use `set_option diagnostics true` to get diagnostic information
-/
#guard_msgs in
example (t : Tree α) : 0 < t.size := by simp [Tree.size]

The simplifier only says that it ran too far, but gives very little help for debugging this. The newish set_option diagnostics true can help, but still needs careful investigation – if lemma foo is the bad looping one, but in each step some innocent other lemmas are used a few times, foo will appear rather low on the list.
I assume that users face this not uncommonly in the two situations outlined above:

adding a lemma to the simp call that goes against the current simp-set (e.g. Nat.assoc)
using simp [f] with a recursive funciton f whose equational lemma is inherently looping.

Goal
Instead of the unspecific error message above I’d like simp to

Recognize such “inherently looping” rewrite rules before applying them.
If recognized as such, ignore the rule, but still make progress elsewhere.
Print a helpful warning that some rules were ignored.
In particular: indicate exactly the set of looping lemmas, so that users see right away where they have to look. Maybe suggest using rw instead for better control.

Of course not all kinds of simp loops can be prevented, but many common and “obvious” ones can.
Proposal
My idea for how to address this is based on the observation that a good™ simp lemma likely has it's RHS in simp-normal form, because what’s the point in not. But in the two examples above, the bad™ rules do not have their RHS in simp-normal form!
So the idea is that simp would, before applying a lemma ∀ x, lhs[x] = rhs[x] to an occurrence lhs[e], first simplify rhs[x] in the abstract, i.e. before instantiating x, to rhs'[x], and then continue with rhs'[x].
If simplifying the abstract rhs[x] already fails (by hitting the recursion limit), we conclude that this is not a good rule for simp to apply, report it, and ignore it from now on.
Even better: We don’t even have to hit the recursion limit. As we simplify the rule’s RHS with other rules we do the same thing; simplify these rules’s RHS first. If we keep track of the stack of rules which we are currently simplifying we can abort as soon as we look at a rule that we looked at before, as we just ran into a circle, and can very precisely report the set of looping rules.
Notes

This subsumes the (simpler) check “does this rule apply in it's own RHS“, which would catch the above Tree.size issue, but wouldn’t be good enough in the presence of mutual recursion.

I’d apply this check lazily, i.e. only when just about to apply a simp rule, to avoid unnecessary work and to treat the simp arguments similar to the theorems added with the simp attribute. So simp [looping_theorem] would not complain until looping_theorem would actually be applied. One could also consider checking all the explicit simp arguments.

Sometimes such a bad rule could still be usefully applied to concrete terms.
Consider the rewrite system if b then a else b = if foo b then a else b, foo true = false and if false then a else b = b. The first rule is looping and would be reported, even though (with buttom-up simp applications), and can actually resolve if true then a else b.
I’m not sure how often of that appears in practice, and whether it even should be supported.

If we do want this, then some override syntax (simp [!foo] or so) that disables the check might be useful.

It may be helpful to run this check also eagerly upon attribute [simp] foo, with regard to the current default simp set, to give an early warning.
But this check should not replace the check in the actual simp run, as then we likely have a different simp set.

If we have rules whose RHS is expensive to simplify (large, or very far from a normal form), then it may be useful to cache that, so that the rule can be applied many times without paying that cost again. In some obscure cases this might even speed up the simplifier compared to now.
(Or maybe the existing simp cache will reliably remember rhs[x] → rhs'[x] and provide this caching just fine?)

This is not expected to catch all kind of simp loops, but the remaining simp loops are then due to concrete terms, not due to rewrite rule sets that are inherently looping.

If the user writes simp [foo], then this is (almost) like simp [foo.eq_1, foo.eq_2, …]. Not sure what to say here when foo.eq_1 is good and foo.eq_2 loops; this may need some careful error message wording.

Community Feedback
(None yet)
Impact
Add :+1: to issues you consider important. If others benefit from the changes in this proposal being added, please ask them to add :+1: to it.

"and then continue with rhs'[x]." should be rhs'[e].
This would be nice. :-)


Add document placeholder

@viktor-yakubiv What do you think about this Facebook like loading animation instead of spinner? Also, I was thinking about moving LoadingBar to design as we use it here and in dashboard.

Sure, it looks nice. I wanted to add loading classes to the design but was busy with the dashboard recently. Let's schedule this for the next 2 weeks 🙂


Throw error if manifest.json isn't found

To avoid issues like https://github.com/fregante/chrome-webstore-upload-cli/issues/63#issuecomment-1239785761

It's hard here because it just receives a zip. I'll open an issue on the cli package


Getting this job was abandoned error message while building on macOS-13 vs. macOS-12

Description
I am getting intermittently every time i ran the pipeline a job was abandoned error from different agents:
This job was abandoned. We have detected that logs from the agent may have not finished uploading. We have included our in-memory record of all log lines uploaded before we lost contact with the agent: Starting: Run automation tests
This same error doesn't happen when using macOS-12.
Error:

Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[X] macOS 13
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
https://identitydivision.visualstudio.com/IDDP/_build/results?buildId=1138769&view=results
Is it regression?
No
Expected behavior
To run successfully without job was abandoned error
Actual behavior
As you see in the image, the task is not even complete and is around 45 mins through..
This issue has been preventing us from switching our automation tests to use macOS-13. This pipeline run multiple stages in parallel out of which every time it is running a consistent random-stage error message is displayed and the error is causing the stage to fail. This never happens with macOS-12. Pipeline view of stages here:

We'd like to have a resolution or suggestion on how to fix this issue?
Repro steps
Run the listed pipeline

It is a duplicate of #7754


Only enable exporters on live - ONLY merge if throttling is happening

This just in case we face some throttling

This hasn't been a problem for almost two months so I am closing this.


implement poet k2pow

Description
spec: https://community.spacemesh.io/t/proof-of-work-and-post-proof-generation/361

the spec as of now is not ready for implementation. the communication btwn poets and nodes need to be specified.

@countvonzero I think it's far too unspecified to consider it for implementation. It could even end with NOT being poet side k2pow.

maybe lets close this for now? the research thread on the forum is still open. we can track it there.


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 168 ms

Resolved: ClamAV performance has improved in 6112aa9.


Open a few different xcorr simultaneously

Is it possible to open two xcorr views, each showing plots for different subsets of units? Selection of units across two xcorr views currently appears to be locked together, so that if the units selected in one view change, the selected units also change in the other xcorr view, too. I understand how this locking is useful across different types of views; however, I might be misunderstanding why it is useful / why it must be this way when two of the same view are open. Thanks for any thoughts on this!

Thanks for raising this (as well as the number of other great issues you've been bringing up over the last couple days).
Fortunately, this one is already supported--if you pull up the cross-correlogram view, above the unit selection list on the left you'll see a little slider labeled 'lock selection.' When it's deactived (the default), the selection state will be synced with the global selection state (used on the units table, autocorrelograms, etc. etc.)
However, once you have a selection for your xcorr, activating 'lock selection' will keep that selection constant. It will no longer sync to the global state, and you won't be able to alter it in the widget either (so stray clicks won't change your locked view).

If you unlock the selection, it'll then automatically sync back to the global state and resume following changes made in other views.

Got it - makes sense and seems to work smoothly! Thanks.


Fixed Bug where last file in the lcov parse would not get added to the list.

Noticed this bug while working with the library. I've added a test case and fixed the issue

@sguiheux tagging ya so you can see this let me know if you need any more changes!


runtime error

I start the server with pm2
it will crash sometime.
pm2 list show status is errored
I check the err-log. it's like this.
/root/test-webhook/node_modules/gitlabhook/gitlabhook.js:113
    '%i': lastCommit.id,
                    ^
TypeError: Cannot read property 'id' of undefined

I added a check of existens.


Returning distance field?

Is there any way to get a distance field with this project? The distance filter works but it doesn't seem to return what the actual distance is. I can do something like qs.annotate(distance=Distance('point', point)) but then I imagine I'm running the distance calculation twice.

I think the best way - now - is simply not using DistanceToPointFilter and do the query by hand just as you mentioned (using annotate).

can anyone post here what will be the query for this and how we can get distance filed in return ?

This would be like the Distance function example in the django docs. That produces something like ST_Distance from postgis.

It gives error "Please provide a geometry attribute with a defined SRID."
lnglat = self.request.query_params.get('lnglat', None)
distance_from_point = {'mi': distance_miles}
queryset.filter(lnglat__distance_lte=(lnglat, measure.D(**distance_from_point))).annotate(
distance=Distance('lnglat', lnglat))

This is relevant as not everyone uses the same srid
https://en.m.wikipedia.org/wiki/Spatial_reference_system#Identifier
I'll think more about and try to suggest something.
I'm using srid 4326, and you should set in the Point instance you are using
the appropriate srid for your scenario.
On Fri, Sep 16, 2016, 2:24 AM codalprashant<EMAIL_ADDRESS>wrote:

It gives error "Please provide a geometry attribute with a defined SRID."
lnglat = self.request.query_params.get('lnglat', None)
distance_from_point = {'mi': distance_miles}
queryset.filter(lnglat__distance_lte=(lnglat,
measure.D(**distance_from_point))).annotate(
distance=Distance('lnglat', lnglat))
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/djangonauts/django-rest-framework-gis/issues/114#issuecomment-247535547,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIqSCp-qLnXZUTv_hS3QkouKRVsAalAks5qqkQ-gaJpZM4JXWWu
.

@paulosuzart I ended up doing this myself like this:
queryset = queryset.filter(point__distance_lte=(point, distance))
queryset = queryset.annotate(dist=Distance('point', point))
# Sort it too
queryset = queryset.order_by('dist')

I'm not sure if this is the most efficient way. It has acceptable performance for several thousand locations.

I have no idea. If this is a question regarding usage, I would suggest to ask on stackoverflow and keep using this place for bugs and patches only.


Persistence Management: persistent store for cached XML-data

HDFS?
Population procedures

persistence with XML file store implemented. Other persistence plugins are planed for next releases


⚠ Mobitopup has degraded performance

In 96e9a04, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 11429 ms

Resolved: Mobitopup performance has improved in 7503d2e.


Project Mass Scoping

Need to figure out additional models

Suspension
Brakes
Talk to Brown on 1/31

Scoped Remainder of PM simulation. Going to rock with constant acceleration for braking and suspension model will come from SS cornerning model


Update meta.yaml

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] 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)
[x] Ensured the license file is being packaged.

This PR adds two maintainers shimwell and RemDelaporteMathurin (which is the new user name for RemiTheWarrior)

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Invalid noarch value python >=3.6. Should be one of python, generic.

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.

@conda-forge-admin

@conda-forge-admin, please rerender


Come up with a GitHub-centric way to track structured data "across" events

The issue template is great, and provides an easy way to submit a prospective event with a number of different fields.
However, it's not currently possible to see a "birds eye" view of links across events, to compare, for example, their CFP deadlines, short of clicking into X different issues and doing this manually.
Requirements:

We want something GitHub-oriented that's transparent + open to everyone
It's in some kind of structured / tabular format

Ideas:

Markdown table?
Google Sheet managed by OpenSSF that we export as a CSV?
other?

Workflow suggestion from @edodusi and @Cheukting

Keep issue template as a way to suggest events. (easily editable, just write some text)
(Have some kind of approval process?)
Have either a manual process or automation for moving to a read-only Google spreadsheet, owned by OpenSSF committee, where further massaging / analysis can be done

A possibility for keeping the information in Github would be to use a project to collect the event issues that have been submitted. Issue data and any custom field data for each issue are displayed tabularly for a bird's eye view across the submitted events. It looks to be possible to add automation to issues/projects using workflows and actions.

Great idea! That sounds like an excellent use of the next two relatively meeting-free weeks for someone... perhaps even me. ;)

@webchick such a great idea. Do you wanna have a go at this? Let me know how can I help


Implement date_diff('millisecond', x, y)

Can I take it?

Yep, got for it :)

My pull request is not listed, should I create new one?


Changes to support rotor & DLC integration with WEIS

These changes allow WEIS to automatically call RAFT and execute the rotor analysis with the DLC case structure.  Some changes should definitely be reviewed by the RAFT team.  I would also recommend activating a CI around a set of unit and regression tests to ensure the interoperability doesn't lapse.

I don't know enough about the WEIS integration to say that anything is out of place so looks good to me!


Named internal links after normal links are mangled

Example. The following tiddler:

This is a test tiddler that features an [[internal link]] followed by another [[different link]] and then by a [[third one|named link]], then by some random text that really doesn't matter at all. If we throw a named link here [[like this|another named link]] it's fine, but a named link after a [[normal link]] will be ruined. This tiddler gets mangled by the regular expressions.

... is, when processed, mangled, producing the following output:

This is a test tiddler that features an [internal link]] followed by another [different link](#different%20link) and then by a [third one](named link), then by some random text that really doesn't matter at all. If we throw a named link here [like this](another named link) it's fine, but a named link after a [[normal link](#third%20one%5D%28named%20link%29%2C%20then%20by%20some%20random%20text%20that%20really%20doesn%27t%20matter%20at%20all.%20If%20we%20throw%20a%20named%20link%20here%20%5Blike%20this%5D%28another%20named%20link%29%20it%27s%20fine%2C%20but%20a%20named%20link%20after%20a%20%5B%5Bnormal%20link) will be ruined. This tiddler gets mangled by the regular expressions.

The cause is a missing \] in the named internal link regex. PR coming right up.

I just realised the regex actually expects this to be an external link, which breaks named internal links in additional ways.


ctags: no tags found for ***

@jtanx , I have tried this plugin, with ctags --tag-relative --extra=f -R generate the tags file, but mostly, it output ctags: no tags found for ***.
My environment is: Win7, ctags 5.8, vscode 1.12.1.

@armslave7 can you confirm that the tag you're interested in can be found in your tags file? For example, if I want to lookup CLARTG, in my tags file, I have a line that says
CLARTG	lapack-netlib/SRC/clartg.f	/^      SUBROUTINE CLARTG(/;"	s

@jtanx i can find the tag in the tags file(my tags file is .tags), and the case i used is also correct.
For example, i find the line
LDLT_1	E:\data\*.f90	/^SUBROUTINE  LDLT_1(/;"	subroutine	line:799

and i can goto the right line from other file where use CALL LDLT_1(***),
but for another one, like
AS_G    E:\data\*.f90	/^SUBROUTINE  AS_G(/;"	subroutine	line:295

it gives the information ctags: no tags found for ***.
It's confuse.

@jtanx I have tried for another project, and use ctags -R -f generates tags file, it works for every function. I checked the file, and the line read
asgl_p	.\asp_ap.f90	/^subroutine asgl_p(/;"	s

And i checked the previous project with problem,  also use ctags -R -f generates tags file, it still can't work. In the main directory there is .tags, and .tags1 file which ATOM generated. It's really confused me.
Meanwhile this plugin works well for my another project, it's efficient, and if it could provide a function for returning where i call Navigate to definition will be very good!
Thank you!

@armslave7 was this line copied directly from your tags file?
AS_G    E:\data\*.f90	/^SUBROUTINE  AS_G(/;"	subroutine	line:295

I notice between AS_G and E:\data\*.f90, there's 4 spaces instead of a tab character. The tab separation is very important, otherwise the line won't be parsed correctly.
As for providing a function to jump back to where you called Navigate to definition, vscode has an in-built function which I find good enough, called Go back/Go forward (the default key binding is Alt+Left/Alt+Right).

@jtanx yes, i copied from my tags file, i replaced the directory by *.
I found that it works well. I delete the tags generated by ATOM plugin, and regenerate the tags file, this plugin can work well, it may be the ATOM plugin use a different format which confused this plugin.
And what i want is go back to where i from. For example, from main.f90 with plugins i go to where AS_G defined maybe in fun.f90, when i finish my edit, i want go back to main.f90 where i from.
I know go back, it only help to go back to the last place.
Thank you very much, this already help me a lot.

@armslave7 I've implemented the jump back functionality; please upgrade to version 1.0.3 and give it a try. The default key binding is Alt+t. Thanks.

@jtanx I have tried this function, it works well, thank you very much!


fix: remove sanity checks as they might trigger false positives

When the reference being written is near the very start of the stable memory
it could be 6l (corresponding to MutBox).
Such is case is probably very rare (for realistic programs), but could be engineered.
This PR avoids the conflating of heap tag constants with absolute stable memory
offsets. For references the heap tag field has either been already changed to hold
the absolute offset (by write_alias), or has the StableSeen tag value as written by size_alias.
This is a preparation for #2790 (but also an independent fix).

I'm a bit confused about this patch. It seems like the assumption here is that for MutBox (and ObjInd, Array) should not be seen here as those would be turned into StableSeen in the previous pass, which is what we do in
https://github.com/dfinity/motoko/blob/423b0923eb6f609358778cd0072cc25bf097e475/src/codegen/compile.ml#L4320-L4326
So these assertions look correct to me.

However, as you mentioned on Slack, we should make sure that the value of StableSeen is not a valid offset to stable memory. I think the only way to make sure is by making it a value that is not a multiple of word size as objects are word aligned.

However, as you mentioned on Slack, we should make sure that the value of StableSeen is not a valid offset to stable memory.

I think that’s why it is (was) -1.
(And, to be precise, I think it’s not the offset into stable memory, but rather into the Candid serialization, which is itself 4 bytes into stable memory.)

I think the only way to make sure is by making it a value that is not a multiple of word size as objects are word aligned.

The offsets can be arbitrary bytes, as Candid serialization isn’t word-size. So a negative number is probably the safest.

Actually, what we write into the tag isn’t the offset into the candid date buffer either, but actually the absolute memory position of a position in the buffer. We get the offset using
          get_tag ^^ get_data_buf ^^ G.i (Binary (Wasm.Values.I32 I32Op.Sub)) ^^

So we’d have a problem if a pointer into that dynamically allocated data blob could be the same as these heap tags, which is not possible right now (they’ll always point to the stack).

I think that’s why it is (was) -1.
...
The offsets can be arbitrary bytes, as Candid serialization isn’t word-size. So a negative number is probably the safest.
...
what we write into the tag isn’t the offset into the candid date buffer either, but actually the absolute memory position of a position in the buffer

32-bit -1 is the same as<PHONE_NUMBER> which is a valid address (last location in 4 GiB address space). So I think the reason why this works is because that memory location cannot be used for a MutBox, ObjInd, or Array, as there won't be enough space for the rest of those objects after the header.

Ok you caught me, I admit I willingly disregarded the case that the candid data buffer extends to precisely the last byte in memory, and that a mutable object of size one byte ends up being out precisely there :-)
But I acknowledge that while extremely unlikely, it's not really nice to do it that way.
Which means that small numbers (that end up pointing to the stack area) are actually safer.

Yeah, now I think (went back and examined advance_data_buf) that the code is safe. The data buffer lives in the heap (memory 0x0 and at address > 0xFFFF) so any absolute address saved into the 32 bits will be distinct from MutBox, ObjInd, or Array's code. My error was that I thought that the addresses point into a different memory (e.g. stable memory).
Closing.

That said, the sanity checks should be only inserted for "debug instrumentation" as they will never trigger for a correct serialiser. Also they eat up cycles. And they will trip #2790, if it ever gets put into practice.


ldap search filters allow for any legal expression

Older implementation assumed all ldap filters end with "={0}" This newer implementation allows the user to craft any legal filter expression, including complex compound expressions, like (&(|(member={0})(member={1}))(objectclass=groupofnames))
Signed-off-by: Chuck Levesque<EMAIL_ADDRESS>

yes well thats cuz the changes have changed

Chuck Levesque | Cloudera
Principal Solutions Engineer
(M)<PHONE_NUMBER>

On Mar 9, 2023, at 1:16 PM, Webster Mudge @.***> wrote:
@clevesque https://github.com/clevesque - looks like you are including other upstream change into this PR. Can you review and resubmit only the LDAP search filter elements?
—
Reply to this email directly, view it on GitHub https://github.com/cloudera-labs/cloudera.cluster/pull/97#issuecomment-1462549594, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABUH2HKS6N7Q4GBTZFQ26TW3INBDANCNFSM6AAAAAASPVXEQY.
You are receiving this because you were mentioned.


Orientation.lockToPortrait() not locking view

Hey,
i do want to lock certain views to portrait mode, but when calling
Orientation.lockToPortrait();
in any of the methods, it does not lock at all, landscape mode still changes view behaviour
i tried:
componentWillMount()
componentDidMount()
Any suggestions on that?
( the xcode Project allows "Portrait", "Landscape Left", "Landscape Right" , since i do have some views that i want to allow in landscape)
Best,
Patrick

I have the same issue, Orientation.lockToPortrait() not locking at componentDidMount().
Orientation.addOrientationListener(() => Orientation.lockToPortrait()); is a bit weird as it did rotate the screen then rotate it back to Landscape, not an ideal solution.

@mickeyjc  I have the same issue on android. Orientation.lockToPortrait() not working at componentDidMount(), and throw a error :undefined is not an object(evaluating ‘Orientation.lockToportrait’)
How do I modify the Configuration in android？

Follow the Android part of the Configuration section on the project README.md, it mentions to add extra two lines to the MainActivity.java

@mickeyjc thanks your reponse . It could running that I make a mistake for no import a few pakerage on MainActivity.java
now，it is still the same error， but when I use  the demo of  ..\node_modules\react-native-orientation\demo\index.android.js running , throw the same error above.

I now got it running on ios. i somehow missed the "configure" section in this. sorry about that.

Yes I am not getting in IOS, but  fixed in android.

I followed the linking and configuring steps but I couldn't get it to work on iOS (didn't test in Android).
When I use toLockPortrait() or toLockLandscape() the screen starts at correct orientation, but if I rotate the device or cmd+left/cmd+right in the simulator the orientation changes, it's not really being locked.
Any suggestions?

I was just playing with this, it appears if you add any listeners with:
Orientation.addOrientationListener
It unlocks all the orientations

I still couldn't get it to work. I created this repo to show a simple example of my situation: https://github.com/soutot/react-native-orientation-test
Any suggestions?
Thanks in advance

this method call in componentWillMount
On Mar 29, 2017 11:13 PM, "Tiago Souto"<EMAIL_ADDRESS>wrote:

I still couldn't get it to work. I created this repo to show a simple
example of my situation: https://github.com/soutot/
react-native-orientation-test
Any suggestions?
Thanks in advance
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/yamill/react-native-orientation/issues/136#issuecomment-290167080,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATmTnNOX93F7arpOI3PIXwrJPB3u4VLlks5rqpg1gaJpZM4LaX-N
.

@lavarajallu I changed it, but it's still not locking

I will  give on some code after 10hrs okay
On Mar 29, 2017 11:26 PM, "Tiago Souto"<EMAIL_ADDRESS>wrote:

@lavarajallu https://github.com/lavarajallu I changed it, but it's
still not locking
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/yamill/react-native-orientation/issues/136#issuecomment-290170874,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATmTnA4Gur1rRJF22xDDR0miiwje4wVJks5rqps_gaJpZM4LaX-N
.

Dear Tiago Souto,
var Orientation = require('react-native-orientation');

follow this  when you want change or lock to portrait*

componentWillMount(){  if(this.props.sportName == 'Pro Football'){
Orientation.lockToLandscape();    this.setState({      HEIGHT:375,
WIDTH:667                })  }  else{   Orientation.lockToPortrait();
}  }  _orientationDidChange(orientation) {    if (orientation ==
'LANDSCAPE') {      //do something with landscape layout    } else {
Orientation.lockToLandscape();    }  }onBack(){
Orientation.lockToPortrait();       this.setState({        open:false
})  }
On Wed, Mar 29, 2017 at 11:29 PM, ALLU LAVARAJU<EMAIL_ADDRESS>wrote:

I will  give on some code after 10hrs okay
On Mar 29, 2017 11:26 PM, "Tiago Souto"<EMAIL_ADDRESS>wrote:

@lavarajallu https://github.com/lavarajallu I changed it, but it's
still not locking
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/yamill/react-native-orientation/issues/136#issuecomment-290170874,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATmTnA4Gur1rRJF22xDDR0miiwje4wVJks5rqps_gaJpZM4LaX-N
.

@lavarajallu I really appreciate your effort. I tried to run the following code and still getting the same scenario: the screen loads as landscape but when I rotate it (cmd + left), the whole content turns to portrait view.
componentWillMount() {
		Orientation.lockToLandscape();
	}

	_orientationDidChange(orientation) {
		if (orientation == 'LANDSCAPE') {
			Orientation.lockToLandscape();
		}
	} onBack() {
	 	Orientation.lockToPortrait();
	}

	render() {
		return(
			<View style={{ flex: 1, justifyContent: 'center', alignItems: 'center'}}>
				<Text>This is my content</Text>
			</View>
		);
	}

My package.json:
{
  "name": "teste",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "test": "jest"
  },
  "dependencies": {
    "react": "~15.4.1",
    "react-native": "^0.42.3",
    "react-native-orientation": "^1.17.0"
  },
  "devDependencies": {
    "babel-jest": "19.0.0",
    "babel-preset-react-native": "1.9.1",
    "jest": "19.0.2",
    "react-test-renderer": "~15.4.1"
  },
  "jest": {
    "preset": "react-native"
  }
}

I also tried with RN 39, no success.
Here's the demo:

Would you mind trying to run the code from my repo? I still don't know why it doesn't work. I even tried to create new blank projects to check if I followed the correct setup steps.
https://github.com/soutot/react-native-orientation-test
Thanks in advance

Hey,
Thank you everyone for the help! After an observation of @ibussieresI found that there was an error of RCTBridgeModule.h' file not found
I replaced it the import to this #import <React/RCTBridgeModule.h> and it seems to be working now!
Thank you very much!

Glad you got it working. You, should close the issue. Cheers !

@soutot Is this still working for you? I want to actually lock to Portrait Orientation.lockToPortrait() but it's still allowing to go landscape. Is this scenario doing the same for you? If not, how did you get it to work?
Thanks!

@larryranches Yes, it's working fine here. After npm install I opened this file node_modules/react-native-orientation/iOS/Orientation.h and replaced the import to #import <React/RCTBridgeModule.h> since it's the new syntax of RN. After this it worked perfectly here.
I created a repo with a simple example. Try cloning it and check if it works for you. If you have any issue, I'll try to help!
https://github.com/soutot/react-native-orientation-test

for me, after these fixes Orientation.lockToLandscape() works fine, but Orientation.lockToPortrait() still is not working...

@timCF that's odd. If landscape works portrait should works as well. I guess it might be something regarding your setup.
Try cloning my repo and setting up the lib. Check if it works for you.

@soutot
Thank you for your solution! It works for me!

Closing this for now as it works as expected

This does not work as expected. Orientation.h should be updated according to latest RN standard.

My imports in Orientation.h look like:
#import <Foundation/Foundation.h>
#import <UIKit/UIKit.h>
#if __has_include(<React/RCTBridgeModule.h>)
#import <React/RCTBridgeModule.h>
#else
#import "RCTBridgeModule.h"
#endif

and it's still not working on IOS, but on Android is working well. Any suggestions? Thanks a lot!

Update your environment, it seemed like it fixed itself in a later version of RN for me. Before the update this worked also as a workaround: "Orientation.addOrientationListener(() => Orientation.lockToPortrait());"

hey there, I have tried all the solutions mentioned, as I have encountered the same road blocks too, but none have helped me.
The project begins to compile but it ends up complaining further about missing files and can't get the library to build as part of the whole project, just to support orientations.
any other tips?

Still Orientation.lockToPortrait is not working. Any suggestions?

Make sure you have install Pods
cd ios && pod install
Use:
Orientation.lockToLandscape()
Orientation.lockToPortrait()
In AppDelegate.m
write before @end
- (UIInterfaceOrientationMask)application:(UIApplication *)application supportedInterfaceOrientationsForWindow:(UIWindow ``*)window {
    while ([[UIDevice currentDevice] isGeneratingDeviceOrientationNotifications]) {
        [[UIDevice currentDevice] endGeneratingDeviceOrientationNotifications];
    }
    return [Orientation getOrientation];
  }


Incorrect display with fast turn 180 degrees

I'm sorry for my English, I use Google translator.
With the rapid turn the device 180 degrees picture is displayed inverted, and the accelerometer is not working properly maintaining .When also obtained an inverted image. Tested on 4 devices.

Also reproduced on:

nVidia SHEILD - Android 5.0.1
Samsung Galaxy S3 - Android 4.4.2


[5.6] Support --allow-writing-to-package-directory as described in SE-0332 and --allow-writing-to-directory to allow arbitrary directories (#3972)

5.6 cherry-pick of https://github.com/apple/swift-package-manager/pull/3972

@swift-ci please test


Update scripts to generate ColorType.swift and GradientType.swift

Update FlatColorsTypeScript.swift and GradientsTypeScript.swift to generate ColorType.swift and GradientType.swift.

[ ] GradientsTypeScript.swift
[ ] FlatColorsTypeScript.swift

We can generate the code using #colorLiteral like #colorLiteral(red: 0.08235294118, green: 0.6980392157, blue: 0.5411764706, alpha: 1), then Xcode 8 can display the color in code editor like

I've got a working script for GradientsType but i think it could be improved slightly. Any ideas? @tbaranes @lastMove
https://gist.github.com/gkye/1bdc8ccf86099b26f6ef7204c487cfa7

@gkye LGTM, just a few of small suggestions about the method names.
func getColorLiteral(hexString: String) -> String
func JSON(from urlToRequest: String) -> Data
func parse(JSONData: Data) -> [[String: AnyObject]]?
I am not good at naming as well 😁, any feedback is welcome.


[Feature] Trigger savepoint automatically if the aligned snapshots in sources are created by savepoint

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
Related to #1635 and #1640
When there are ETL jobs and Paimon Tables associated upstream and downstream, the upstream job creates a tag through savepoint, and downstream jobs consume the tag data and align it, they could automatically trigger a savepoint instead of checkpoint. For example, there are tables TableA, TableB and TableC, Job1 processes data from TableA to TableB, Job2 processes TableB to TableC
TableA --> Job1 --> TableB --> Job2 --> TableC
When Job1 save a tag named tagB1 in TableB by savepoint, Job2 will trigger a savepoint for tagB1 and save a tag named tagC1.
When we need to resume the above data processing, we can create a new Job1' and Job2' from the above savenpoints and tags in TableB and TableC to incremental recover data processing. cc @liming30
Solution
No response
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

@JingsongLi What do you think of this issue?

I think we need to give a PIP to describe how to use savepoint and tag in Flink && Paimon to support correcting streaming data processing, WDYT? @JingsongLi @liming30

I think we need to give a PIP to describe how to use savepoint and tag in Flink && Paimon to support correcting streaming data processing, WDYT? @JingsongLi @liming30

@FangYongs Does this refer to branch features?  Should this be in the PIP documentation for the branch feature and implemented as a subtask?

@liming30 Not very relevant yet. I think we can create a PIP that clarifies the data backtracking process based on savepoint and tag, and then organize the features that need to be supported based on this process cc @schnappi17


db.json instead of content.json

Everything works fine, except it generates a db.json file instead of content.json. I have to manually change the file name after each hexo generate.

Thanks for report and sorry for late response!
This issue will be fixed soon.

Sorry, I just ran a simple test here. It's all right and content.json was generated normally.
Please don't reaname your db.json file! It is generated by Hexo itself and is an important framework file.
If your content.json wasn't generated, something is working bad.
Try this:
If you are running hexo server to develop or test your site, the content.json file will not be generated physically in the file system, but only virtually.
Just access your site url and add content.json to access the generated content. Like: http://localhost:4000/content.json
When you run hexo generate command to build your static site, the content.json file will be generated physically in the file system in your public folder root.

You are right, of course. I was using hexo server to develop locally and the search plugin couldn't find content.json. All I had to do was hexo generate. Thanks.


Thread getting Killed

Terminal Output:-
.
.
.
computing neighbors
computing neighbors
computing neighbors
finished: added to .uns['neighbors']
'distances', distances for each pair of neighbors
'connectivities', weighted adjacency matrix (0:01:47)
running Louvain clustering
using the "louvain" package of Traag (2017)
finished (0:00:01)
finished: added to .uns['neighbors']
'distances', distances for each pair of neighbors
'connectivities', weighted adjacency matrix (0:01:49)
running Louvain clustering
using the "louvain" package of Traag (2017)
finished: added to .uns['neighbors']
'distances', distances for each pair of neighbors
'connectivities', weighted adjacency matrix (0:01:49)
running Louvain clustering
finished (0:00:00)
using the "louvain" package of Traag (2017)
finished (0:00:00)
Killed

My code is running for some time. Eventually, I'm just getting a "thread killed" error message.
I'm running the following code:
import scanpy as sc
import pandas as pd
import numpy as np
import trajectorama
from anndata import AnnData
import matplotlib.pyplot as plt
plt.switch_backend('agg')
sc.settings.set_figure_params(scanpy=True, dpi=100, dpi_save=200, format='pdf')
sainath=sc.settings.figdir
sc.settings.verbosity = 3
sc.logging.print_versions()
result_file='./write/sainath.h5ad'
sc.settings.set_figure_params(dpi=100)
bdata = sc.read_h5ad("/home/vaibhav_agrawal51_va/mo_new_data_after_RV_6_improved.h5ad")
X = bdata.X
studies = list(bdata.obs.condition)
Xs_coexpr, sample_idxs = trajectorama.transform(
X, studies,
corr_cutoff=0.7,
corr_method='spearman',
cluster_method='louvain',
min_cluster_samples=500,
)
n_features = X.shape[1]
triu_idx = np.triu_indices(n_features) # Indices of upper triangle.
X_coexpr = np.concatenate([
Xs_coexpr[triu_idx].flatten() for Xs_coexpr in Xs_coexpr
])
Plot KNN graph in coexpression space.
adata = AnnData(X_coexpr)
sc.pp.neighbors(adata)
sc.tl.draw_graph(adata)
sc.pl.draw_graph(adata,save="trajectory")

Perhaps it's killed due to memory usage? Can you try using sparse matrices, e.g.,
import scipy.sparse
X_coexpr = scipy.sparse.csr_matrix(X_coexpr)


Create Shop campaign

refactor campaign creation flow to manage case for promote my shop
integrate with cs to create shop campaign.
TODO:
get campaign details
manage case while campaign is being created

Should we also feature the new button in the demo? Or do it in another PR?

Should we also feature the new button in the demo? Or do it in another PR?

it's already there

Please add a detailed description of the changes.

added


Fix typo in TimingPoints parser (?)

timing points with 2 elements exist, and they do work.
eg. https://osu.ppy.sh/b/256
This mainly fixes calls to GetMaxCombo on maps with these short timing points
All included Unit tests still pass.

Seems good, thanks!


 I could just host the script locally to ensure that it doesn't change but then I'd lose the benefits of CDN caching and also I don't really understand the intricacies of utterances to be sure that it'd work perfectly that way.
So what do you recommend?

Quick solution: you could generate the hash for https://utteranc.es/client.js using https://www.srihash.org
 <script src="https://utteranc.es/client.js"
         repo="jdanyow/utterances-demo"
         branch="master"
         issue-number="15"
         async
+        integrity="sha384-Xzvl+Tf9crKsJBG5htkEvAri2XbSYf2jsxOcpHtkZ3xRUJsDvSOdxl78utgsbf1h"
+        crossorigin="anonymous"
+        onerror="insertAdjacentHTML('afterend', 'Error loading utterances. If you are the site owner and have enabled SRI, verify the hash value for https://utteranc.es/client.js at https://www.srihash.org/')">
 </script>

Running example here: https://jsfiddle.net/jdanyow/8xjse6r1/ (edit the hash value to see the error behavior).
The trouble with this approach (as you know) is utterances will stop working on your site when an update is published that changes the client.js script. That script is not updated very often but indirect changes to things like the transpiler (typescript), bundler (parcel) or minifier (uglify) could cause the hash to change. I imagine this would happen quite often.
A proper solution would involve maintaining versioned builds so that folks wanting to use SRI could opt out of automatic updates. Eg <script src="https://utteranc.es/1.0.1/client.js" integrity="...." ....>. For that to work long term I'd need to manage backwards compat all the way down to the api. Doable but I'm not sure I want to take on the extra work at this time.
Another option would be to create a "release notification" issue that folks could subscribe to where I could give notice of upcoming hash changes. Site owners could subscribe and update their integrity attributes ahead of the release (multiple hashes separated by whitespace are permitted in the integrity attribute). This would ensure the upgrade experience is seamless.
All that said, it's probably pointless to use SRI with the current utterances architecture. The utterances widget is sandboxed in an iframe for a couple reasons: 1) prevent host page styles from breaking the widget and visa versa and 2) prevent the host page from accessing the user's github auth token. Unfortunately there's no way to specify an integrity attribute for iframes. Initially iframes were in the working draft of the SRI spec but they never made it to the final draft. I don't think it's worthwhile to check the integrity of https://utteranc.es/client.js if the first thing the script does is create an <iframe src="https://utteranc.es/utterances.html"> element which we cannot verify integrity on.
Does this make sense? Let me know if you have any questions/ideas to improve this.

@jdanyow Good point about the iframe. I was going to suggest hosting it locally as an alternative to versioned hosting, etc. Perhaps in that scenario you'd be able to verify the integrity of every local file using some kind of manifest? Here's a great writeup by CryptPad, who attempted to solve a similar issue.

@awnumar thanks for the link, this is interesting stuff. For now I think you could use the instructions in #42 to self-host and consider using utterances directly if we come up with a solution in the future.


OSX  cannot be found in default CPP Include Path /usr/include

VSCode Version: 1.0.0
OS Version: OSX 10.11.4

Steps to Reproduce:

Setup a C++ project in VS Code
include <fstream> in source

I see a green wavy line under include <fstream> with a lightbulb. When I click the lightbulb the c_cpp_properties.json file is opened.  I see that /usr/include is listed as the include path.  I can see that  is in this path (actually it's in /usr/include/c++/4.2.1/ ... but other C++ headers in the same folder seem to work ok... like  and )
What am I doing wrong?

We are very sorry to hear you are having issues with VS Code. Reading your description it seems that the issue originates from an extension and not VS Code itself. Thereby I will close this issue and kindly ask you to report this issue against the extension repository. Most extensions are on GitHub as well so it should be easy to file it against the extension.
Thanks for your feedback!


_tkinter.TclError: bitmap "images/iconbitmap.ico" not defined _____   Import "backend" could not be resolvedPylancereportMissingImports)

like the title says i have the following problems with tkinter_designer.py

import backend isnt working properlly (atleast vscode is having trouble)

if i try to run the script i get to following error message:

-->>>python3 tkinter_designer.py
Traceback (most recent call last):
  File "/home/shaco/Tkinter-Designer/tkinter_designer.py", line 55, in <module>
    window.iconbitmap("images/iconbitmap.ico")
  File "/usr/lib/python3.9/tkinter/__init__.py", line 2080, in wm_iconbitmap
    return self.tk.call('wm', 'iconbitmap', self._w, bitmap)
_tkinter.TclError: bitmap "images/iconbitmap.ico" not defined

For reference, how did you install the program? Using the Git command, or an executable?

Hey @Shaco74 ,

I don't use VSCode but what do you mean by 'Isnt working properly' ?
I was not able to reproduce this error both on windows and mac.

Excuse my inaccuracie please. It's my first time reporting something on GitHub.
So I am running the latest Ubuntu version (hippo)
I installed the program by cloning the git repo and installing the requirements (basically following the installation instructions)
By saying that VSCode isn't working properly I meant that VSCode is highlighting one specific line in the script. It highlights the 'import backend' line as a missing import error. (this could be a bug of VSCode or pylance because there is not an Error referring to this when running the python script from the terminal.)
Still there is this error comming up
_tkinter.TclError: bitmap "images/iconbitmap.ico" not defined
I am not too experienced with python. But I have this feeling that this error is related to the working directory the script is using. I saw that there were indeed lines which would change the os.dir
Hope I could help you out providing you this informations

I just tested Tkinter-Designer on my Windows machine, it works fine here..
Are there linux distros on which the software got tested on?

Sorry from us too @Shaco74 , Tkinter Designer was never tested on linux machines. I am currently looking for solutions for the problem you've mentioned.

Yeah i allready tired commenting out that line, but he catched another error which looked very similiar. I assum its just about relative and absolute paths which are causing the trouble here on linux

Can I know the other error ?

I am not currently on my linux mashine but I am preatty sure it was about
generate_btn_img = PhotoImage(file="./images/generate.png")
similiar error: not able to locate the file

Ohh I see. I'll look into it. Thanks for letting us know.

Looks like something an import of the os module and using os.path.join() would fix.

So i found out that the Scripts wasnt actually having trouble due to relative/absolute paths.
The problem was simply that Linux cant work with .ico files.
I opened up this pull request here:
https://github.com/ParthJadhav/Tkinter-Designer/pull/21

The same holds true for macOS, you can work around this issue in the meantime by commenting out line #55 in tkinter_designer.py
#window.iconbitmap("images/iconbitmap.ico")

Yes, Actually I discovered that issue on Mac too but not much alarming as Linux. And the solution is given by @Shaco74 in his pull request.
Instead of commenting it, we can use GIF. It works on Mac and @Shaco74 is testing it on Windows and Linux.

Fixed issue in the latest commit.

The same holds true for macOS, you can work around this issue in the meantime by commenting out line #55 in tkinter_designer.py
#window.iconbitmap("images/iconbitmap.ico")

THANKS!