[DI] Start Catalog frontend packages migration

Hey, I just made a Pull Request!
Start the Catalog plugin migration to the declarative integration format.

[!Important]
Skipping entity pages in the initial attempt. Mostly sidebar items, index page, and filter extensions.

Know limitations

The Catalog table will not be configurable initially, but we are open to suggestions about what could be configurable;
The CatalogEntityPage will be migrated in a follow-up pull request.

Usage example

[!Note]
This is experimental, documentation will be updated in a follow-up pull request.

Only one step is required to start using the Catalog plugin in Backstage, which is to install the @backstage/plugin-catalog package in a Backstage app that supports declarative integration (e.g.,  app-next).
yarn add @backstage/plugin-catalog

The experimental Catalog plugin comes with a default implementation for the CatalogApi and StarredEntitiesApi; also includes a default CatalogIndexPage as well a few Catalog*Filter extensions. All of this is configurable via app-config.yaml file, for example:
# app-config.yaml
app:
  experimental:
    packages: 'all' # ✨

  extensions:
   # customize catalog index page path
    - catalog:
         config:
           path: '/entities'
   # customize catalog sidebar item label
    - catalog.nav.index:
        config:
          label: 'Entities'
    # disable default catalog entity tag filter
    - catalog.filter.entity.tag: false
    # define initial catalog entity kind filter
    - catalog.filter.entity.kind:
        config:
          initialFilter: 'api'

Local Testing:
First, install the branch dependencies and start both frontend and backend declarative applications:
# Installing branch dependencies
yarn install

# Starting the backend application
cd packages/backend-next
yarn start

# Starting the frontend application
cd packages/app-next
yarn start

Finally, navigate to http://locahost:3000 and click on the Catalog sidebar item:
https://github.com/backstage/backstage/assets/6290749/809baa65-b3e5-40bd-9c02-701098fb66c9
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

For @backstage/catalog-maintainers, please excuse us running all over your lawn 😅. We're using a couple of different plugins to aid us in the design of the new declarative integration system. We'll most likely take a stab at entity pages in not too long too, let us know if you want to be involved in that early or would rather wait for the DI system to be more finished, with docs etc.

oof a conflict got in!


Create devcontainer.json

This is basically the default dev container configuration, AFAIK. Did you need this to get something else working?


Updates for week of 22 July

Mergeup and other changes.
Instead of resolving conflicts in the merge commit, this PR:

reverts downstream patches which conflict and patches which rely on them
merges upstream without conflicts
cherry-picks the conflicting patches again, with conflicts resolved in the cherry picks

I've collapsed the multi-image patches a bit more and also marked them [nrf noup] instead of fromlist or toup since upstream has rejected this approach.
Build tested only at this point, along with an mcuboot mergeup (https://github.com/NordicPlayground/fw-nrfconnect-mcuboot/pull/47) and some other nrf changes (https://github.com/NordicPlayground/fw-nrfconnect-nrf/pull/1003).

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 17 committers have signed the CLA.:white_check_mark: hakonfam:white_check_mark: oyvindronningstad:x: carlescufi:x: arnop2:x: jimparis:x: andrewboie:x: pabigot:x: erwango:x: mbolivar:x: galak:x: ulfalizer:x: pavlohamov:x: gbakke:x: Rallare:x: rlubos:x: SebastianBoe:x: sigvartmhYou have signed the CLA already but the status is still pending? Let us recheck it.

Will the upmerge revert helper from the ncs-tools work fine with all these reverts and cherry-picked commits (there will be a lot of commits with duplicated titles in the tree)? I remember we've already had an issue with duplicated commit title, @carlescufi submitted a "hack" fix for that: https://github.com/NordicPlayground/ncs-tools/commit/4c964df0c84260816565b84377b4edb5e525a6e6.

Note that there is an issue with 5c97ecda6b69d6ff8e95a8a17918e61f6f694c49 which seems to break all samples with LTE_AUTO_INIT_AND_CONNECT. That is not related to this upmerge, just putting it here in case someone else finds the issue.

Will the upmerge revert helper from the ncs-tools work fine with all these reverts and cherry-picked commits (there will be a lot of commits with duplicated titles in the tree)? I remember we've already had an issue with duplicated commit title, @carlescufi submitted a "hack" fix for that: NordicPlayground/ncs-tools@4c964df.

I have some fixes in my fork that solve all these problems and will submit them as a separate PR.


Please provide some examples for BigQuery

Could you please provide some life examples about creating tables and sending queries to BigQuery service? Seems like all available in Internet are out of date, and missing something.

I can do some basic examples.
@ianbarber is it ok if I add examples in "examples/Service/Bigquery"... (thus mimicking the structure of the client library) ?

Of course, Thank You!
16 sty 2015 16:11 "Gabriel PREDA"<EMAIL_ADDRESS>napisał(a):

I can do some basic examples.
@ianbarber https://github.com/ianbarber is it ok if I add examples in
"examples/Service/Bigquery"... (thus mimicking the structure of the client
library) ?
—
Reply to this email directly or view it on GitHub
https://github.com/google/google-api-php-client/issues/453#issuecomment-70266709
.

Thanks @eRadical - we don't generally include service specific examples with the library, but if you put up your own repo of examples that would be great. If you have an example that demonstrate some generic functionality which is not otherwise covered, then do feel free to contribute that though!

@ianbarber  I started a repo as you said at https://github.com/eRadical/google-api-php-client-examples
I'll be happy to merge pull request that will enrich it.
I know I've digged into the API myself for an AppEngine & BigQuery application... maybe it will be of help.


BITMAKER-2100 estela-web: Implement "In Projects/Scheduled Jobs"

Description
estela-web: Implement "In Projects/Scheduled Jobs" mockup
Issue
https://tasks.bitmaker.dev/issues/2100
Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] My code follows the style guidelines of this project.
[x] I have made corresponding changes to the documentation.
[x] New and existing tests pass locally with my changes.
[x] If this change is a core feature, I have added thorough tests.
[x] If this change affects or depends on the behavior of other estela repositories, I have created pull requests with the relevant changes in the affected repositories. Please, refer to our official documentation.
[x] I understand that my pull request may be closed if it becomes obvious or I did not perform all of the steps above.

@Adriana618 Could you review this PR pls
https://tasks.bitmaker.dev/issues/2100

@Adriana618 The PR #101 add role field on ProjectList component. And this PR is about styling ProjectCronjobList component, algo Cronjob Create component. Are very different

Rebase with main branch


Dashboard Query Builder is slow to pick fields if an index has > 1000 fields

We need to consider implementing virtual scrolling to reduce the number of dom elements, e.g. https://dev.to/adamklein/build-your-own-virtual-scroll-part-i-11ib.
Also the field picker control needs to change to use the back-end quick filter code to be consistent with the other filter boxes in stroom.  Also, the term value suggest drop down needs to change to use the SelectionPopup instead of SuggestBox.


Too many caches?

With 3 OSs and 2 Rust versions, we create 6 caches per run. A single cache can get as large as 1 GB :astonished: https://github.com/o2sh/onefetch/actions/caches
With a 10GB limit, where older caches get evicted, this means that just 1 or 2 PRs can start evicting caches for the main branch. Basically, I don't think the caches are living long enough to be effective.
Perhaps we should only try to use caches for stable Rust? This should result in less turnover, so that hopefully some caches will live long enough to be useful.

Somehow related:

by switching to Swatinem/rust-cache for caching the build artifacts, it reduced the cache size for one CI run by a couple of hundreds MB -> https://github.com/o2sh/onefetch/actions/caches
I also noticed that we were missing a cache step in the coverage job: fixed in bad6516, resulting in ~4 minutes saved when caching is found.

Perhaps we should only try to use caches for stable Rust? This should result in less turnover, so that hopefully some caches will live long enough to be useful.

We could do smth like that, especially considering the fact that a "nightly" cache has a "reuse lifespan" of 1 day maximum.
With my recent changes, we're at cache size of 4,720MB per CI run - assuming no cache reuse - which is below the 10GB limit.
So we should be able to hit the cache quite often - on stable - as long as we don't touch the Cargo.lock OFC.

With my recent changes, we're at cache size of 4,720MB per CI run - assuming no cache reuse - which is below the 10GB limit.

That's a huge difference! Times like these I wish GitHub had a :astonished: comment reaction :laughing:

@o2sh I think caching is pretty good now. Should we close the issue, or were you thinking of implementing any other optimizations?


Upgrade to latest version of Firebase

Upgraded to 2.3.1 for Firebase and 1.1.3 for Firebase Angular


[Bug] This is not a chat model and thus not supported in the v1/chat/completions endpoint

{
"error": {
"message": "This is not a chat model and thus not supported in the v1/chat/completions endpoint. Did you mean to use v1/completions?",
"type": "invalid_request_error",
"param": "model",
"code": null
}
}
I haven't set any BASE_URL, and even if I set the BASE_URL to https://api.openai.com/, I still have this issue.
I have tried changing the API key, but it doesn't help.

10:32Listening on port 3000 url: http://deployment-643caf56c6718ce2cdaee0e6-9747f4f8-n2cnw:3000
10:40[Auth] allowed hashed codes:  []
10:40[Auth] got access code: null
10:40[Auth] hashed access code: d41d8cd98f00b204e9800998ecf8427e
10:40[User IP]  <IP_ADDRESS>
10:40[Time]  4/17/2023, 2:40:46 AM
10:40[Auth] set system token
10:40[Proxy]  v1/chat/completions
10:40[Base Url] https://api.openai.com
10:40[Stream] error  {
10:40  "error": {
10:40    "message": "This is not a chat model and thus not supported in the v1/chat/completions endpoint. Did you mean to use v1/completions?",
10:40    "type": "invalid_request_error",
10:40    "param": "model",
10:40    "code": null
10:40  }
10:40}
10:40
10:40[Auth] allowed hashed codes:  []
10:40[Auth] got access code: null
10:40[Auth] hashed access code: d41d8cd98f00b204e9800998ecf8427e
10:40[User IP]  <IP_ADDRESS>
10:40[Time]  4/17/2023, 2:40:47 AM
10:40[Auth] set system token
10:40[Proxy]  v1/chat/completions
10:40[Base Url] https://api.openai.com
10:40[OpenAI]  ReadableStream { locked: false, state: 'readable', supportsBYOB: false } TypeError: RequestInit: duplex option is required when sending a body.
10:40    at Object.fetch (node:internal/deps/undici/undici:11457:11)
10:40    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
10:41[Auth] allowed hashed codes:  []
10:41[Auth] got access code: null
10:41[Auth] hashed access code: d41d8cd98f00b204e9800998ecf8427e
10:41[User IP]  <IP_ADDRESS>
10:41[Time]  4/17/2023, 2:41:33 AM
10:41[Auth] set system token
10:41[Proxy]  v1/chat/completions
10:41[Base Url] https://api.openai.com
10:41[Stream] error  {
10:41  "error": {
10:41    "message": "This is not a chat model and thus not supported in the v1/chat/completions endpoint. Did you mean to use v1/completions?",
10:41    "type": "invalid_request_error",
10:41    "param": "model",
10:41    "code": null
10:41  }
10:41}
10:41
10:41[Auth] allowed hashed codes:  []
10:41[Auth] got access code: null
10:41[Auth] hashed access code: d41d8cd98f00b204e9800998ecf8427e
10:41[User IP]  <IP_ADDRESS>
10:41[Time]  4/17/2023, 2:41:33 AM
10:41[Auth] set system token
10:41[Proxy]  v1/chat/completions
10:41[Base Url] https://api.openai.com
10:41[OpenAI]  ReadableStream { locked: false, state: 'readable', supportsBYOB: false } TypeError: RequestInit: duplex option is required when sending a body.
10:41    at Object.fetch (node:internal/deps/undici/undici:11457:11)
10:41    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Any screenshots of browser console / network log?

page-942ba0084af85765.js:1 [Config] got config from server Object
Fetch event handler is recognized as no-op. No-op fetch handler may bring overhead during navigation. Consider removing the handler if possible.
serviceWorkerRegister.js:4 ServiceWorker registration successful with scope:  https://dsj-gpt.zeabur.app/
serviceWorker.js:4 ServiceWorker activated.
page-942ba0084af85765.js:1 [User Input]  [{…}]
page-942ba0084af85765.js:1 [Request]  {messages: Array(1), stream: true, model: 'gpt-3.5-turbo', temperature: 1, presence_penalty: 0}messages: [{…}]model: "gpt-3.5-turbo"presence_penalty: 0stream: truetemperature: 1[[Prototype]]: Objectconstructor: ƒ Object()hasOwnProperty: ƒ hasOwnProperty()isPrototypeOf: ƒ isPrototypeOf()propertyIsEnumerable: ƒ propertyIsEnumerable()length: 1name: "propertyIsEnumerable"arguments: (...)caller: (...)[[Prototype]]: ƒ ()[[Scopes]]: Scopes[0]toLocaleString: ƒ toLocaleString()toString: ƒ toString()valueOf: ƒ valueOf()length: 0name: "valueOf"arguments: (...)caller: (...)[[Prototype]]: ƒ ()[[Scopes]]: Scopes[0]defineGetter: ƒ defineGetter()defineSetter: ƒ defineSetter()lookupGetter: ƒ lookupGetter()lookupSetter: ƒ lookupSetter()proto: (...)get proto: ƒ proto()set proto: ƒ proto()
page-942ba0084af85765.js:1 [Chat History]  (3) [{…}, {…}, {…}] 251 1000
page-942ba0084af85765.js:1
    POST https://dsj-gpt.zeabur.app/api/openai?_vercel_no_cache=1 500

暂时没有收到同类型报错，zeabur 平台是个小公司做的，建议用 vercel。

暂时没有收到同类型报错，zeabur 平台是个小公司做的，建议用 vercel。

及时我使用vercel进行部署，仍有相同问题

建议提供一下浏览器控制台 log，看一下请求是否正确。
当你部署到 vercel 的时候，不要设置任何 BASE_URL 或者 PROXY_URL，仅设置 OPENAI_API_KEY 和 CODE，再确认是否有问题。

如图，只设置了APIKEY

建议提供一下浏览器控制台 log，看一下请求是否正确。
当你部署到 vercel 的时候，不要设置任何 BASE_URL 或者 PROXY_URL，仅设置 OPENAI_API_KEY 和 CODE，再确认是否有问题。

请问这个问题解决了吗？

免费试用账号用不了 gpt-3.5.

同样的问题


Racing condition between Selenium Server and ChromeDriver

Main issue: ChromeDriver won't delete it's scoped_dir****_***** folders from Windows's Temporary files.
It was supposed to be fixed a few times already., but I am still struggling with this, when I am using selenium-server version 3.6.0 (and a few versions before this one too) with ChromeDriver 2.33 on a Windows 7 x64 virtual machine. The directories just keep piling up (each around 5MB) and after a day or two it slows down the system. I saw this issue mentioned with Firefox's driver too.
As much as I can see, sometimes when a browser closes a scoped_dir folder gets deleted, but most of the time it won't. I tried to use a ps1 script to manually delete the files (source, mentioned here), but It just cannot delete them until I shutdown selenium-server. For me, It looks like Chrome and selenium-server keep each other from deleting the files.
Please tell me, what information should I share to help this issue resolved.
Until then:

I am using Java 1.8 to connect to the server
I start the selenium server with simply calling java -jar selenium-server.jar
My test cases require lot's of browser starting and stopping, but I close them every time with a driver.quit() in a try-catch-finally structure.
I tried using driver.close() before calling driver.quit(), but it just crashed with an already closed driver exception.

Hi @SzabKel, sorry but this isn't the bug tracker for Selenium; this is just a composer package for PHP projects to download the Selenium JAR.
I think (but not 100% sure) the right place for your issue is over at https://github.com/SeleniumHQ/selenium/issues
Thanks!


Gracefully Handle System-Level Failures/Restarts

If there's a "system"-level error, like if the k8s pod dies, a scanner instance should restart (from scratch). ArgoCD is built to do this, however, the DB logical schema will need to be updated to handle restarts.
Likewise, if there's an application-level error, like the scanner server breaks, we don't (necessarily) want a restart. More investigation is needed to differentiate what errors are restart-worthy.

This is no longer a design requirement. It is the responsibility of the user to re-request scans.


On "Request funds" view history date shows NaN

Also proposed a change upstream: https://github.com/austintgriffith/burner-wallet/pull/158

via #60


cannot allocate memory in static TLS block

I tried using the installer, after a long time i got the following stacktrace and the installation stopped.
ImportError: /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "manage.py", line 11, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
    utility.execute()
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/django/core/management/__init__.py", line 377, in execute
    django.setup()
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/django/__init__.py", line 24, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/django/apps/registry.py", line 114, in populate
    app_config.import_models()
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/django/apps/config.py", line 211, in import_models
    self.models_module = import_module(models_module_name)
  File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 848, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/usr/lib/librephotos/backend/api/models/__init__.py", line 1, in <module>
    from api.models.album_auto import AlbumAuto
  File "/usr/lib/librephotos/backend/api/models/album_auto.py", line 6, in <module>
    from api.models.photo import Photo
  File "/usr/lib/librephotos/backend/api/models/photo.py", line 22, in <module>
    from api.thumbnails import (
  File "/usr/lib/librephotos/backend/api/thumbnails.py", line 4, in <module>
    import pyvips
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/pyvips/__init__.py", line 71, in <module>
    vips_lib = ffi.dlopen(_vips_libname)
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/cffi/api.py", line 150, in dlopen
    lib, function_cache = _make_ffi_library(self, name, flags)
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/cffi/api.py", line 832, in _make_ffi_library
    backendlib = _load_backend_lib(backend, libname, flags)
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/cffi/api.py", line 827, in _load_backend_lib
    raise OSError(msg)
OSError: cannot load library 'libvips.so.42': /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block.  Additionally, ctypes.util.find_library() did not manage to locate a library called 'libvips.so.42'
/usr/lib/librephotos/.local/lib/python3.8/site-packages/torchvision/io/image.py:11: UserWarning: Failed to load image Python extension:
  warn(f"Failed to load image Python extension: {e}")
Traceback (most recent call last):
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/pyvips/__init__.py", line 19, in <module>
    import _libvips
ImportError: /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "manage.py", line 11, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
    utility.execute()
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/django/core/management/__init__.py", line 377, in execute
    django.setup()
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/django/__init__.py", line 24, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/django/apps/registry.py", line 114, in populate
    app_config.import_models()
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/django/apps/config.py", line 211, in import_models
    self.models_module = import_module(models_module_name)
  File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 848, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/usr/lib/librephotos/backend/api/models/__init__.py", line 1, in <module>
    from api.models.album_auto import AlbumAuto
  File "/usr/lib/librephotos/backend/api/models/album_auto.py", line 6, in <module>
    from api.models.photo import Photo
  File "/usr/lib/librephotos/backend/api/models/photo.py", line 22, in <module>
    from api.thumbnails import (
  File "/usr/lib/librephotos/backend/api/thumbnails.py", line 4, in <module>
    import pyvips
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/pyvips/__init__.py", line 71, in <module>
    vips_lib = ffi.dlopen(_vips_libname)
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/cffi/api.py", line 150, in dlopen
    lib, function_cache = _make_ffi_library(self, name, flags)
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/cffi/api.py", line 832, in _make_ffi_library
    backendlib = _load_backend_lib(backend, libname, flags)
  File "/usr/lib/librephotos/.local/lib/python3.8/site-packages/cffi/api.py", line 827, in _load_backend_lib
    raise OSError(msg)
OSError: cannot load library 'libvips.so.42': /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block.  Additionally, ctypes.util.find_library() did not manage to locate a library called 'libvips.so.42'

Trying to run the install script again stops at this point
+ which vips
/usr/local/bin/vips
+ echo 'VIPS allready found on the system'
VIPS allready found on the system
+ echo 'Sometimes older vips can cause problems.'
Sometimes older vips can cause problems.
+ read -t 5 -p 'If librephotos-backend not starting, try to uninstall vips and recompile again'
If librephotos-backend not starting, try to uninstall vips and recompile again

librephotos-linux is for amd64 architecture.
For ARM please look Discord:
https://discord.com/channels/784619049208250388/794163017071722527
@derneuere this can be closed. I have updated compatibility info and added CPU architecture. No more misleads :)

The discord link is invalid. Is there an arm version of the install script available or do I have to run the docker container?

Discord librephotos
I recommend to cleanup system


no license

Hello,
May we know the license for the repo? GitHub also encourages us to have a license for public repo (under "Licensing a repository - GitHub Docs"). We would like to highlight this as a transparency concern.
The following are from GitHub Docs.
· "If you're creating an open source project, we strongly encourage you to include an open source license."
· "If you publish your source code in a public repository on GitHub Enterprise Server, other users of your GitHub Enterprise Server instance have the right to view and fork your repository."
· "Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you'll need to license it so that others are free to use, change, and distribute the software."
Regards, Software Ethics Researcher.

Hi,
Thank you very much for the warning. I have already added the license to
the repos that didn't have it.
Best regards.
https://www.youtube.com/c/MouredevApps https://www.twitch.tv/mouredev
https://twitter.com/MoureDev https://instagram.com/mouredev*
@.**> https://github.com/mouredev
https://www.linkedin.com/in/braismoure
https://apps.apple.com/es/developer/brais-moure/id896842097
https://play.google.com/store/apps/dev?id=8530023128495175247&hl=es&gl=US
Brais Moure
MoureDev Founder | Freelance full-stack developer
www.mouredev.com https://mouredev.com/
@.*** @.**>
AVISO DE CONFIDENCIALIDAD.
Este correo y la información contenida o adjunta al mismo es privada y
confidencial y va dirigida exclusivamente a su destinatario. MoureDev
informa a quien pueda haber recibido este correo por error que contiene
información confidencial cuyo uso, copia, reproducción o distribución está
expresamente prohibida. Si no es Vd. el destinatario del mismo y recibe
este correo por error, le rogamos lo ponga en conocimiento del emisor y
proceda a su eliminación sin copiarlo, imprimirlo o utilizarlo de ningún
modo.
CONFIDENTIALITY WARNING.
This message and the information contained in or attached to it are private
and confidential and intended exclusively for the addressee. MoureDev informs
to whom it may receive it in error that it contains privileged information
and its use, copy, reproduction or distribution is prohibited. If you are
not an intended recipient of this E-mail, please notify the sender, delete
it and do not read, act upon, print, disclose, copy, retain or redistribute
any portion of this E-mail.
El mar, 14 jun 2022 a las 8:49, Software Ethics Researcher (<
@.***>) escribió:

Hello,
May we know the license for the repo? GitHub also encourages us to have a
license for public repo (under "Licensing a repository - GitHub Docs"). We
would like to highlight this as a transparency concern.
The following are from GitHub Docs.
· "If you're creating an open source project, we strongly encourage you to
include an open source license."
· "If you publish your source code in a public repository on GitHub
Enterprise Server, other users of your GitHub Enterprise Server instance
have the right to view and fork your repository."
· "Public repositories on GitHub are often used to share open source
software. For your repository to truly be open source, you'll need to
license it so that others are free to use, change, and distribute the
software."
Regards, Software Ethics Researcher.
—
Reply to this email directly, view it on GitHub
https://github.com/mouredev/Weekly-Challenge-2022-Swift/issues/206, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AECA7SWUUQ5YSPUVYUWTXJTVPATPTANCNFSM5YWRLVPA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


DSA 4.3.3 Anagram Pattern Search

Description
Give an introduction and explain the working of an algorithm for searching all anagrams of a pattern in a given text.
Task

[ ] Documentation
[ ] Audio
[ ] Video

Note

While requesting the issue to be assigned, please mention your NAME & BATCH NUMBER.
Kindly refer to Issue Guidelines.
In case you see that the issue has already been assigned, try to request for a different task within the same issue.
Changes should be made inside the DSA/directory & DSA branch.
Name of the file should be same as the issue.
This issue is only for 'GWOC' contributors of 'DSA' Domain.

/assign documentation

/Assign Documentation

/assign documentation

/assign documentation


Invalid barcode on IOS iphone

Test QR:
https://www.google.com/chart?chs=200x200&chld=M|0&cht=qr&chl=otpauth://totp/PCBPC:maremkulov@vpndev.siteg.ru?secret=SQXENQOIOTTSN5VK6ZR6HAEMGY======&issuer=PCBPC

Even when I try to add the secret key manually:

At the same time in the android version everything works as it should. I think the problem is that the secret key has the characters: ======

What tool or website generated this QR code?
Yeah that trailing "=====" is odd.


Add unit/integration testing for @opencensus/web-instrumentation-zone

Add unit testing for OnPageInteraction class.
Integration testing on InteractionTracker which creates fake interaction in other to test all kind of supported tasks (e.g. setTimeout, Promise, HTTP requests).

Additionally, there are some changes little changes:

Change InteractionTracker as Singleton as there will be only one InteractionTracker instance always.
(Fix) Reset currentEventTracingZone when the interaction has finished before it is reset automatically.
Register a initial SpanEventListener in the Tracing (for this case the NOOP_EXPORTER) as this is helpful for testing.
Stop tracking periodic tasks (setInterval) as they might never stop and interaction wouldn't be stable.

Codecov Report

Merging #104 into master will decrease coverage by 0.28%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           master   #104      +/-   ##
========================================
- Coverage   96.29%    96%   -0.29%
========================================
  Files          26     28       +2
  Lines         647    827     +180
  Branches       83    124      +41
========================================
+ Hits          623    794     +171
- Misses         24     33       +9

Impacted Files
Coverage Δ

src/on-page-interaction.ts
100% <0%> (ø)

src/interaction-tracker.ts
93.54% <0%> (ø)

src/trace/model/tracing.ts
100% <0%> (+4.54%)
:arrow_up:

Continue to review full report at Codecov.

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


Try importing dbg from bcalm, bifrost, and others in addition to megahit & spades

https://github.com/GATB/bcalm
conda install -c conda-forge -c bioconda bcalm
https://github.com/pmelsted/bifrost
conda -c bioconda bifrost

These have been evaluated - they're good to retain for benchmarking in future work


[CI]: Add basic CI pipeline for automated testing

Contact details
No response
Tell us what you want to do with CI in this project
No CI pipeline exists for basic testing and feature release

Done


Redundant conformance to SecureStorableResultType?

I'm seeing the following warning in Swift 3.0, Xcode 9:

Hey @abhishekbanthia, #179 was merged fixed this issue.

Great. Closing.


ENH: Create a Calibrations class for eyetracking data

Reference issue
I forgot to open a ticket before creating a PR (apologies!):
This PR is based on my discussions with @larsoner and @britta-wstnr regarding my current GSoC project. For the first week, the goal was to extend functionality to reading and storing some meta-information from eye-tracking recordings, that will be needed for work down the line in this GSoC project.
What does this implement/fix?
This PR creates a Calibration class that sublcasses OrderedDict.
Minimally Working Example:
fname = mne.datasets.testing.datapath() / "eyetrack" / "test_eyelink.asc"
calibrations = mne.io.read_eyelink_calibration(fname,
                                               screen_size=(.531, .298),
                                               screen_distance=.065,
                                               screen_resolution=(1920, 1080))

print(calibrations[0])  # show info for the left eye Calibration
Calibration |
  onset: 0 seconds
  model: HV13
  eye: left
  average error: 0.3 degrees
  max error: 0.9 degrees
  screen size: (0.531, 0.298) meters
  screen distance: 0.065 meters
  screen resolution: (1920, 1080) pixels

print(calibrations[1])  # show info for the right eye Calibration
Calibration |
  onset: 0 seconds
  model: HV13
  eye: right
  average error: 0.31 degrees
  max error: 0.52 degrees
  screen size: (0.531, 0.298) meters
  screen distance: 0.065 meters
  screen resolution: (1920, 1080) pixels

calibrations[0].plot()

Additional information
A couple of notes:

EDITED: I refactored the code so that if the EyeLink session was recorded in binocular mode, 2 Calibration instances are returned for each "calibration" that was collected during the session. See commit #48a946c

screen_size, screen_distance, and screen_resolution are not available in the ASCII files but can be optionally provided by the user.

This draft from the WIP eye-tracking BIDS specificaton was used to guide some of the decisions regarding the fields to include by default in the Calibration class.

TODOS:

[ ] Fix failing tests

[ ] increase codecov of the changes introduce in this PR

[ ] move mne.io.eyelink.calibration to mne.preprocessing.eyetrack.calibration, since the Calibrations class is not specific to eyelink.

[x] create a plot method for the Calibration class.

Great, @scott-huberty ! Let me know once this is ready to be tested on additional data.

Some small stuff my gaze tripped upon when looking at the PR - will do a more thorough review after tests pass 🙂

Thanks! since I made quite a bit of changes locally, I just made your suggested changes locally on top of my changes, (instead of comitting them here and rebasing). See the commit with title FIX: Incorporated Britta's suggested changes

Maintenance note: After some refactoring and adding a plot method, I edited my initial message at the top to reflect this. I've included an example of the calibration plot, there.

The plot looks great, it could be nice to have the average and max error written in a corner.

The plot looks great, it could be nice to have the average and max error written in a corner.

Good idea. I'll give it a shot!

I would nest the from ...preprocessing.eyetracking.calibration import Calibration in whatever function actually needs the Calibration class

I would nest the from ...preprocessing.eyetracking.calibration import Calibration in whatever function actually needs the Calibration class

That did it, thanks!

It seems like inherited methods are being built by sphinx autosumary: here is the Calibration doc page
And this is triggering some sphinx warnings during the build.
In mne/doc/preprocessing.rst we specify :no-inherited-members:, but this doesn't seem to solve the problem:
:py:mod:`mne.preprocessing.eyetracking`:

.. currentmodule:: mne.preprocessing.eyetracking

.. automodule:: mne.preprocessing.eyetracking
   :no-members:
   :no-inherited-members:

.. autosummary::
   :toctree: generated/

   Calibration
   set_channel_types_eyetrack

@larsoner / @britta-wstnr do you have any idea of what I'm doing wrong here?

... and also "a shallow copy of od"
The short explanation is that warnings in doc build are treated as errors. So if you search "warning" in the circle log you'll see these. And we can ignore them.
For the copy one it would actually be better to override the method using a deep copy like we do for Info and other objects that subclass __dict__. Basically in MNE there is an expectation that .copy() operates like a deep copy so we should probably continue that behavior here

... and also "a shallow copy of od"
The short explanation is that warnings in doc build are treated as errors. So if you search "warning" in the circle log you'll see these. And we can ignore them.
For the copy one it would actually be better to override the method using a deep copy like we do for Info and other objects that subclass __dict__. Basically in MNE there is an expectation that .copy() operates like a deep copy so we should probably continue that behavior here

Ok! Adding those phrases to conf.py and I will over ride the copy method.
What do you think we should do about the warning triggered by the move_to_end inherited method?:
WARNING: [numpydoc] Validation warnings while processing docstring for 'mne.preprocessing.eyetracking.Calibration.move_to_end':
  GL02: Closing quotes should be placed in the line after the last text in the docstring (do not close the quotes in the same line as the text, or leave a blank line between the last text and the quotes)
  PR01: Parameters {'key', 'last'} not documented

There should be a similar ignore somewhere for numpydoc. Take a look in conf.py and see if it's in there, if you can't find anything quickly I can look

I thought I found what I needed in numpy_doc_show_inherited_class_members, which I set to False:
numpydoc_show_inherited_class_members = {
    "mne.SourceSpaces": False,
    "mne.Forward": False,
    "mne.preprocessing.eyetracking.Calibration": False,
}

But the warning is still raised, and the documentation is still clearly being built for inherited methods
the search continues...

For no inherited members see how we document the Forward class in doc/, you need to change the autosummary template that gets used

https://github.com/mne-tools/mne-python/blob/main/doc/forward.rst?plain=1#L7

For no inherited members see how we document the Forward class in doc/, you need to change the autosummary template that gets used

Thanks!
Almost there.. There's a failure in the M1 tests and I am trying to figure out if it is specific to my PR:
mne.viz.backends.tests.test_abstract.test_widget_abstraction_pyvistaqt[pyvistaqt]

mne/viz/backends/tests/test_abstract.py:119: in test_widget_abstraction_pyvistaqt
    _do_widget_tests(backend)
mne/viz/backends/tests/test_abstract.py:28: in _do_widget_tests
    window = backend._AppWindow()
mne/viz/backends/_qt.py:707: in __init__
    _MNEMainWindow.__init__(self, size=size)
mne/viz/backends/_qt.py:698: in __init__
    MainWindow.__init__(self, parent=parent, title=title, size=size)
/opt/homebrew/lib/python3.10/site-packages/pyvistaqt/window.py:23: in __init__
    QMainWindow.__init__(self, parent=parent)
E   TypeError: _Widget.__init__() got an unexpected keyword argument 'parent'

No you can ignore that, I'll fix it tomorrow

Alright @larsoner @britta-wstnr  I think this is ready for review!
I'll open a ticket tomorrow for the next preprocessing function I'd like to work on. This work isn't a necessary pre-requisite for it so I won't be blocked, i.e no rush, feel free to review this when you have the time.
Here are the Built docs for:

read_eyelink_calibration
Calibration class

Here is the codecov report
I updated my message at the top with figures generated from the updated plot method.

Great @scott-huberty ! I'll give it a try no my EyeLink data as well and report back! 🙂

Ignore the pre CI failure there's a fix in https://github.com/mne-tools/mne-python/pull/11724

I gave this a try on my own data and it works like a charm! Will the Calibration object (with its info on screen_size etc) mesh with the raw EyeLink data at some point? Or am I missing that?

I gave this a try on my own data and it works like a charm!

Awesome! 🙂

Will the Calibration object (with its info on screen_size etc) mesh with the raw EyeLink data at some point? Or am I missing that?

Yeah I think the idea is for it to be used with a function like:
mne.preprocessing.eyetracking.convert_units(raw, calibrations[0])
where screen_size / screen_resolution / screen_distance will be used to convert pixel-on-screen data to visual-degrees (on screen), or vice-versa.
I think the last piece of information we need for that function is the unit ( and reference?) of the data in RawEyelink, so that we know what the unit is in and if we can convert it?
So, in the case that the RawEyelink eyegaze samples are in pixels:
The SampleCoordinateSystem would be 'pixel-on-screen', and the SampleCoordinateUnit would be 'pixel' (according to this draft of an eye-tracking BIDS standard). With that information, we could convert the pixel-on-screen data to visual degrees.
We talked about adding a new FIFF specification for this information, but I wanted to see how the Calibration class shaped up first, to confirm that we want to add a FIFF speicfication for this and store it in the Raw object?

We talked about adding a new FIFF specification for this information, but I wanted to see how the Calibration class shaped up first, to confirm that we want to add a FIFF speicfication for this and store it in the Raw object?

Maybe I'm missing something but if we say the data are in FIFF.FIFF_UNIT_PX what more do we need? Doesn't this mean they're pixels-on-screen and whatever info is in Calibration can get you directly to visual degrees? I'm not clear on the use case that requires more FIFF constants here

After discussing with @larsoner and @britta-wstnr during office hours today, Eric is right that there is already aFIFF.FIFF_UNIT_PX (that I somehow forgot about!), so we don't need to add another FIFF specification.
per @britta-wstnr 's point, For simplicity, we'll allow the to-be-develoepd conversion function to accept screen_size/screen_distance/screen_resolution directly. This will be done in a future PR.
We also decided that for this PR we should add a demonstration of loading a calibration in the current eye-tracking tutorial, and i'm going to look again at the Calibration['points'] array to see if it can be split into separate dict keys so that it is easier to initialize/extend to future readers for other manufacturers. I'll add these as TODOS to the top of this message.

@larsoner / @britta-wstnr sorry for the flurry of commits yesterday, I'm still working out some kinks in my local environment to make sure I can build the doc and run the test suite locally, but I mostly have figured it out.
I think I am happy with this PR. Let me know what you think about the design / code and if you need me to make any further changes!
Here is the updated eye-tracking tutorial. I've added a bit about loading the calibration, at the beginning of the tutorial. I think this should give you a good idea of the API and design without having to load a file yourself.
Here is the documentation for the Calibration class.
Here is the documentation for read_eyelink_calibration
Here is the codecov report. If I'm not mistaken It looks like the mne/preprocessing/eyetrackingcalibration.py file I added is covered 88% and themne/io/eyelink/_utils.py file I added is covered 96%.

How about using the existing BAD_ACQ_SKIP annot?

I agree that's a better idea but I'm kicking myself for not thinking of this when we wrote it -_-
This function was written just  before 1.4 I think so changing it would be an API change I think? So I'll let you all advise on that.

This function was written just before 1.4 I think so changing it would be an API change I think? So I'll let you all advise on that.

I consider it a bugfix so I'd say go ahead
Let me know when it's done and I'll look!

This function was written just before 1.4 I think so changing it would be an API change I think? So I'll let you all advise on that.

I consider it a bugfix so I'd say go ahead
Let me know when it's done and I'll look!

Done!
Thanks for the tip, @mscheltienne !

Looks like a great start! Got partway through and think I'm at a good stopping spot -- let me know what you think of my ideas and I'll keep looking after any additional changes (tests and tutorial might need to be updated)

Thanks @larsoner! I integrated your suggestions in 6ede0af and updated the docs / tests to reflect the changes.
It looks like the CI's are good. Let me know when you've had a chance to continue your review

Just FYI The Test windows 3.10 CI is returning an error "no matching distribution found for pandas" during the pip install action.
Not sure if that's a fluke, Let me know if you want me to re-trigger the CI's.

Just one last idea then we can merge @scott-huberty !

I think I need to update the docstring to scrub any mention of "will be zero if calibration was before recording start". Plus looks like there is some style complaint. push a commit in a moment.

@larsoner assuming the tests will run as smoothly here as the did locally, this is ready for your review again. Note that as discussed I added an axes kwarg to the plot method and removed he origin kwarg.

Yay for merging @scott-huberty ! 🎉


Biomes O Plenty's Bayou underwater fog color is very odd.

Title. Happens with/without other mods. Other swamp-like biomes may also have weird colors, but I have not tested.

Thanks, should be fixed in 1.14.4.


7 feat ackermann to motec

Added can interface
Description
Issue # 7
Node to translate stamped ackermann drive msg to CAN msg
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Will be tested by simulating various scenarios that may occur. Also test that works in docker.

[ ] simulate unsuccessful msg
[ ] simulate sys crash
[ ] simulate successful msg

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

For more information about the timmer you should look at the minimal publisher on https://docs.ros.org/en/humble/Tutorials/Beginner-Client-Libraries/Writing-A-Simple-Py-Publisher-And-Subscriber.html
As well as this node is going to be a client of the can publishing service and not the service its self so look at the minimal client on https://docs.ros.org/en/humble/Tutorials/Beginner-Client-Libraries/Writing-A-Simple-Py-Service-And-Client.html

should also rename file

btw for dignostics you want to read this https://github.com/ros/diagnostics

for dealing with the tests you should just call the function with diffrent types of messages and such as one where you have a negitive for the steering angle and such or one where all the values are greater then 255. Have another test that spins up the node and then publishes to the topic and see if it gets a responsice.


I18n fr

Is your feature request related to a problem? Please describe.
An I18n fr section
Describe the solution you'd like
An I18n fr section
Describe alternatives you've considered
An I18n fr section
Additional context
An I18n fr section

See https://contribute.freecodecamp.org/#/how-to-translate-files


Start adding brask

More items for Brask:
- Breaks into song
- Talks to his dear departed brother, Thrask Hellbeard
- Uses Vicious Mockery

•	Makes a joke that none of the other group members react to right away

https://deploy-preview-1--critshow-bingo.netlify.app/


Stop reading .babelrc files.

If a .babelrc file is present, it is being read, and the settings merged with the ones we specify for tests. We don't want that.
Reference:
http://babeljs.io/docs/usage/options/

I still need to write a test for this. I can get to it later today.

I still need to write a test for this. I can get to it later today.

@jamestalmage It's already tested in Babel I assume, but sure, if you want.

@jamestalmage It's already tested in Babel I assume, but sure, if you want.

FWIW, using this branch fixed the issue I was having. Thanks again @jamestalmage.

FWIW, using this branch fixed the issue I was having. Thanks again @jamestalmage.

It's already tested in Babel I assume

Yeah, but I could have sworn I already addressed this once before, adding a regression test ensures we don't accidentally drop it.
Test added.

It's already tested in Babel I assume

Yeah, but I could have sworn I already addressed this once before, adding a regression test ensures we don't accidentally drop it.
Test added.

Wait, @jamestalmage, @sindresorhus: Why wouldn't we want this? (Sorry if I missed some earlier conversation).

Why wouldn't we want this?

Because it prevents them from using a .babelrc file for instrumenting their production code with different settings from the tests. We don't currently support people modifying the transforms applied to their tests (and if we ever do, it almost certainly won't be via a .babelrc file).

@jamestalmage: Ok, but as a user of AVA, having AVA transpile my tests with babel, yet not follow my .babelrc, while recommending the babel require hook for test helper files (which does follow my .babelrc) is incredibly confusing. Like really confusing.

While recommending the babel require hook for test helper files.

We will support compiling helpers soon (https://github.com/sindresorhus/ava/pull/177 was an early attempt). Once #390 is merged, I will work on that.

@jamestalmage Looks good to me. Just merge when you've fixed the merge conflict ;)

@jamestalmage, @sindresorhus: I would like to say that I really think that if we're going to block .babelrc (I don't think we should). Then we should prioritize allowing additional babel config, because being forced to use diffrent babel settings for tests and production code is really bad.

We are already doing that. Without this change, our babel settings from caching-precompiler/test-worker are being merged with their .babelrc, and the user has no recourse to change that.
If users really want power-assert, and stage-2 constructs for their production code then they should list that explicitly in their .babelrc.

because being forced to use diffrent babel settings for tests and production code is really bad.

I don't think that's true at all, in fact I think the opposite. If your production code requires Babel, then you need to include a build step as part of npm publish to transpile your code to ES5 so it is easily consumed on npm. A build step necessitates a complete.babelrc for your production code, not one that relies on some plugins your test runner automagically merges (Especially since AVA should be a dev-dependency which would not be deployed with your production code). A complete .babelrc also clearly documents what code constructs can be used in production.

@jamestalmage: That's not what I meant. Here's my situation: I use the babel-require hook, with babel-preset-es2015, and babel-preset-stage-0 in my .babelrc. I'd like for AVA to use that. Otherwise there's stuff I can do in my code but not in my tests. On top of that, the babel-runtime thing means that I can't use bluebird, which is extremely annoying. So I think that the best course of action would be to make AVA smart enough to detect a competing .babelrc, and if it exists, use that (+ power-assert), instead of it's own config..

On top of that, the babel-runtime thing means that I can't use bluebird

Why not?

detect a competing .babelrc, and if it exists, use that (+ power-assert), instead of it's own config...

I don't like that idea. I am certainly open to the idea of allowing users to customize the test transpiler as they see fit. (If you hunt back into the early 100's you'll find half a dozen PR's where I explore the idea). Doing it automatically isn't a good idea, users should have to be explicit about it.

@jamestalmage: your can't use bluebird because it overrides 'Promise' anywhere it finds it, regardless of scope.
Why would it ever be a bad thing for babel to read babel configuration?
What I've personally done for a project that i started yesterday was to transpile it with babel ahead of time.
So while I think that es2015 support is a cool idea, I think that has having a '--no-babel' flag for more complex projects. might be a good idea. (And, you know, being able to babel config would be great too).
Thoughts?

it overrides 'Promise' anywhere it finds it, regardless of scope.

Well that's annoying.
As for the rest of it:

I am certainly open to the idea of allowing users to customize the test transpiler as they see fit ... [but] users should have to be explicit about it.

it overrides 'Promise' anywhere it finds it, regardless of scope.

Well that's annoying.

It's also not true:
// foo.js
import Promise from 'bluebird'
import test from '../../'

Promise.longStackTraces();

test(async t => {
	await Promise.resolve('foo');
});

// transpiled foo.js
'use strict';

var _regenerator = require('babel-runtime/regenerator');

var _regenerator2 = _interopRequireDefault(_regenerator);

var _asyncToGenerator2 = require('babel-runtime/helpers/asyncToGenerator');

var _asyncToGenerator3 = _interopRequireDefault(_asyncToGenerator2);

var _bluebird = require('bluebird');

var _bluebird2 = _interopRequireDefault(_bluebird);

var _ = require('../../');

var _2 = _interopRequireDefault(_);

function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { default: obj }; }

_bluebird2.default.longStackTraces();

(0, _2.default)((function () {
	var _this = this;

	var ref = (0, _asyncToGenerator3.default)(_regenerator2.default.mark(function _callee(t) {
		return _regenerator2.default.wrap(function _callee$(_context) {
			while (1) {
				switch (_context.prev = _context.next) {
					case 0:
						_context.next = 2;
						return _bluebird2.default.resolve('foo');

					case 2:
					case 'end':
						return _context.stop();
				}
			}
		}, _callee, _this);
	}));
	return function (_x) {
		return ref.apply(this, arguments);
	};
})());

@jamestalmage: Weird... It didn't work for me, and according to the maintainers, it shouldn't. I still disagree that AVA shouldn't read the config automatically, but it's not that big of a deal if we document it.
@sindresorhus: Thoughts on a --no-babel option as a hold over till we allow customizing babel config?

Thoughts on a --no-babel option

For what purpose exactly?

@sindresorhus: Until we can modify babel config, I pre-compile my code with babel. Running the transpiled code through babel again doesn't make any sense (This can come with a warning like If you use --no-babel, you must use the power assert babel plugin!).

This can come with a warning.

Or not. We already handle assertions that are not enhanced by the plugin (throws, doesNotThrow).
Personally, I would rather just wait until we figure out configurable transforms instead of adding a feature we intend to replace.
@ariporad - Would the ability to include stage-1 and/or stage-0 satisfy your needs? I am thinking something like a --stage=0 flag.

@jamestalmage: Not really. I also use babel-preset-features, although I guess loosing that wouldn't be the end of the world. But really I think the solution is to allow custom babel config.

@jamestalmage I agree with @ariporad -- it's unintuitive that if my lib code is using babel-preset-stage-[<2] and/or other custom plugins (e.g. I use one to extend import syntax), then I can't use these features in my test code.
Personally, I think the --require flag should disable the Babel hook in favor of the user-provided register hook, but something like a --no-babel option would work too.
More generally, consider this: AVA works well for the (increasingly less common) case of packages written in ES5 with no transpilation step (since you get to write your tests using modern syntax "for free"). However, I'd argue that it drops the ball for the (increasingly more common) case where library code is transpiled anyway: now, despite you having set up tooling to use the syntax you want in lib code, you have to write your tests in a predetermined (and typically strictly smaller) subset of new syntax, which is surprising and frustrating.

I've never said we won't allow configuration of how your tests get transpiled, that's a feature I think is worthwhile. Just that it's not going to automatically happen because you have a .babelrc file present.
I'm not sure what's "most common"/"typical", though I am sure ES2015 use is on the rise. I do find it hard to believe that stage-1/0 constructs are in high demand, especially for use in production code. That seems like a risky plan.
However we solve configurable transpiling, I want it to be able to participate in the caching-main thread-precompiler stuff we just added that has given us a huge performance boosts.

@jamestalmage: Think about it like this: AVA says that it invokes babel for you. If you've explicitly said that you want babel to do X, it would be confusing when AVA's babel doesn't.
Since this seems to be a matter of opinion, why don't we just do a poll?

@ariporad I disagree that it would be confusing, because of the docs outlining AVA's approach to ES2015 that say:

AVA comes with builtin support for ES2015 through Babel 6. Just write your tests in ES2015. No extra setup needed. You can use any Babel version in your project. We use our own bundled Babel with the es2015 and stage-2 presets.

Of course I'm a bit biased towards this because this PR solved the issue I was having with conflicting .babelrc settings breaking the test execution. Even so, I think it's better that AVA's set up is completely independent of my project because it's one less thing to worry about (say I'm porting older Mocha tests from a Babel 5.x project one day, and starting a brand new project the next - the syntax for my tests hasn't changed so I can write my tests first for both projects and not have to rethink structure/syntax/language features/etc). I also think it's better to test production code with esnext features that are more mature & less prone to inconsistent behaviour, for sanity's sake.
A healthy compromise IMHO would be an --ignore-my-babelrc option that defaulted to true and could be configured via the command line or package.json. Something along those lines (with perhaps a snappier name) I would love to see for the day when I would like to use more advanced Babel settings.

@sindresorhus: what are your thoughts on having AVA's babel automatically ignore the explicit babel configuration that users have set. (In my mind, this seems absolutely crazy and the wrong thing to do).
And since this seems to be a debated topic, would everyone be open to a poll of AVA users on what they'd prefer?

This is a really weird breaking change. I am using AVA to test some react (jsx yeah) and now I just cannot (=> I cannot upgrade to 0.10 and I am stuck with 0.9 until there is a solution).
Are you aware that babel have an option to specify config depending on the NODE_ENV variable?
Because it seems that the thing that should be used here: http://babeljs.io/docs/usage/babelrc/#env-option (make sense in the use case of @JaKXz).
AVA should use babelrc by default, otherwise UX is like superweird.

@MoOx - as stated elsewhere. The problem is that without this, the configs end up getting merged with the one AVA automatically creates(which is not always what you want). Specifically, I would generally prefer only to ship production code with fully ratified language constructs (i.e. only the es2015 preset), whereas I'm perfectly comfortable using "beta" language features in my tests.
We are working on a --no-babel option which will allow you to disable AVA's babel processing entirely, and let you do your own thing.

Are you aware that babel have an option to specify config depending on the NODE_ENV variable

I wasn't until just a few hours ago, and my thought was similar to yours. My question now is: Is there a way to specify an environment on a per-file basis via the API?

the configs end up getting merged with the one AVA automatically creates(which is not always what you want).

Is there something uncommon that AVA need?

Is there a way to specify an environment on a per-file basis via the API?

No idea. But maybe process.env.BABEL_ENV/NODE_ENV can be adjusted during the runtime (because babel read from that)?

AVA automatically includes stage-2, which is pretty beta stuff. Also, AVA adds a transform required for power-assert which you definitely don't want instrumenting your production code.

Let's continue further discussion in #448.


[Next] Fields nested within repeater are not localizable

Field specifications in the repeater options object do not appear to use the localize flag. I tried two versions:
{
  "fields": [
    {
      "type": "set",
      "options": {
        "fields": [
          {
            "type": "text",
            "name": "key"
          },
          {
            "type": "text",
            "localize": true,
            "name": "value"
          }
        ]
      }
    }
  ]
}

{
  "fields": [
    {
      "type": "set",
      "localize": true,
      "options": {
        "fields": [
          {
            "type": "text",
            "name": "key"
          },
          {
            "type": "text",
            "name": "value"
          }
        ]
      }
    }
  ]
}

Neither of these swapped the content out when changing languages.
Note: this is different (subtly so) than localizing the repeater field itself (which DOES currently work). Use case for this feature: say I have a "dictionary" repeater field that I want to localize into different languages. I add three words to the repeater and fill in English values. With the localize flag set on the repeater, when I switch to German I have an empty slate - if I want to translate the same words I added in English, I have to add them over again. In this particular case, it would be better if I could instead add the localize flag to the field within the repeater: it would keep the fields I had previously added when I switch languages, but would allow me to swap the values only.

this is one use/edge case, but it is a pretty complicated topic. as you described there is a possible way to handle it. for now, there are more important issues to solve ;-)

Agreed! I hope you don't mind me leaving issues like this around - reminders for later

Sure, suggestions are always welcome 👍

Just like to +1 this for a use case like this: Building a localizeable "Page" entry where a page consists of a few fixed fields (title, route etc) plus a "Content" repeater with all the content blocks for that page. Again, if the entire Content is localized, the editor needs to add all the blocks to the page for each language, instead of just translating the fields that need localization.

That is pretty much exactly what I need it for! It is already a really
great setup but that extra piece would make data entry so much better
On Wed, Sep 21, 2016, 10:53 PM Jesper We<EMAIL_ADDRESS>wrote:

Just like to +1 this for a use case like this: Building a localizeable
"Page" entry where a page consists of a few fixed fields (title, route etc)
plus a "Content" repeater with all the content blocks for that page. Again,
if the entire Content is localized, the editor needs to add all the blocks
to the page for each language, instead of just translating the fields that
need localization.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/COCOPi/cockpit/issues/453#issuecomment-248818622, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFhG2BTL3NiVBE74ms0H87M4yNjyTqC7ks5qshfwgaJpZM4J-Vdj
.

Are there any plans to add this feature? Did anybody find a workaround for it?

@mcapu There is no "workaround" really. What we do is I help my editors by manually copying one language to the other in MongoDB when they create new complex pages :-P

Yeah I haven't found anything better than what @JesperWe suggests, unfortunately.

Actually, now that I think about it, having a UI command to do that copy (Copy the Content from one language to another) would be rather nice... ;-)


feat: Added support for php with test cases

feat: Added support for php with test cases
/claim #48

Summary by CodeRabbit

New Features

Added comprehensive support for the PHP language, including syntax highlighting, grammar, and parser bindings.
Introduced PHP code snippet tests for various language constructs and transformations.
Implemented support for PHP patterns in the PatternsDirectory.
PHP language now supported in language identification and matching patterns within the project.

Documentation

Updated documentation and build configurations to include PHP language support details.

Tests

Added unit tests for PHP language parsing and functionality verification.

Hey @digital-phoenix
I see you've also thrown your hat in the ring ⚔.
Perhaps you didn't see it but @morgante posted this comment 2 days ago on another PR:

There are a few conflicts now too, but this looks close to ready.

Once I saw that, it didn't make sense (for me at least) to continue working on my PR since they'd only be paying out one bounty. At that point, the only thing left was for @morgante to assign the issue to the author of that PR.
Grit is definitely one of the more exciting COSS projects to join Algora and I'm hoping there's plenty of work like this to go round.


adaptiveavgpool

I see the code,it seems support the adaptiveavgpool,but,when I use it,like:
Self.avgpool =  nn.AdaptiveAvgPool2d(1)
Y=self.avgpool(x).view(b,c)
It doesn’t work.and the error is type error None has type Nonetype,but expected one of bytes,Unicode
My env is pytorch 1.2,python 3.6
Can you give some suggestion,how can I fix it?

hi , @riskeverything
i meet the same problem. Have you solved it?
If you had solved it could you share your solution？
Thanks！


react/destructuring-assignment: Enforce destructuring props at function parameter

I want an option to enforce props destructuring happens in function parameter.
Bad:
function Foo(props) {
  const {a} = props
  return <>{a}</>
}

Good:
function Foo({ a }) {
  return <>{a}</>
}

This can be implemented as an option for react/destructuring-assignment. It only affects function components. It does not affect class components.

Seems reasonable, as long as it doesn’t warn when there’s a second reference of the props object.

Ah perfect, I've been looking for a rule like this. Has this been released yet? (I think the answer is 'no')

No, it hasn't.


Restrict available methods on App from Plugin::Build()

What problem does this solve or what need does it fill?
When implementing a Plugin, a user has some footgun available:

calling App::run(), would result in an early launch of the app, handled by plugin, resulting in a partly initialized app to run. On discord a user had this problem and it was not so trivial to track. See final fix there: https://github.com/Sheepyhead/prepare_two_die/commit/3586bcdd532f17bf6b853b3b7d5c763c7b902938#diff-b1a35a68f14e696205874893c07fd24fdb88882b47c23cc0e0c80a30c7d53759L29

What solution would you like?
Ordered from my personal preferred to less preferred:
If there are no uses to run an App from a Plugin::Build, a user shouldn't be able to, we could either:

pass ownership to App::run(self), the same way run_once works, so we couldn't call that from Plugin::Build because we have a &mut App.
Leverage the type system to avoid having App::run() and other footguns being available within the Plugin::Build() function body.

If there exists reasons (I'm curious to hear about them) to indeed run an app from a plugin, we could either:

Do the above, but provide another function like build_advanced allowing such rare behaviour ?
Add a warning when starting the app from a non-conventional place, offering a way to suppress those ?
Use tooling akin to ReportExecutionOrderAmbiguities to offer advanced diagnostics.

pass ownership to App::run(self), the same way run_once works, so we couldn't call that from Plugin::Build because we have a &mut App.

This would make it impossible to do either App::new().add_plugin(Foo).run() or let mut app = App::new(); app.add_plugin(Foo); app.run(); as either add_plugin accepts and returns the app by value in which case app.add_plugin(Foo); doesn't work, or it accepts and returns app by mutable reference in which case .run() doesn't work.
Maybe App could have a private field indicating if it is in the middle of an .add_plugin() operation and panic on .run() in that case?

Indeed we would lose function chaining, see diff on 3d_scene example:

Your comment might be interpreted as that solution would NOT work, but I'm positive that the code I linked works with App::run() taking ownership of app.
That said, I fully agree that losing function chaining is very suboptimal so I'll try to implement your suggestion :+1: .


fix: removed deprecated _get_val_from_obj

In 2.0 Django deprecated _get_val_from_obj[1] and should be replaced with value_from_object
[1]: See https://code.djangoproject.com/ticket/24716

Fixed in #1980


[CSE-228] Add TotalAda endpoint

Please don't merge this PR as it is untested yet.

To review both points from @Martoon-00 :

If we have bridge for explorer, then I guess that Mirco is not ok here :/ Bridge will truncate number to double. @akegalj Is that true?

atm we don't use it in the bridge. We are just exposing backend endpoint for  other to use this value.

I believe that there is a function which checks that coin is in bounds, smth like integerToCoin

yes, there is integerToCoin already here https://github.com/input-output-hk/cardano-sl/blob/master/core/Pos/Core/Coin.hs#L82 which does all the checks @Pastafarianist made with his validateUtxoSum.
As both of these are safe - they can be fixed later. Lets continue with merging this and fixing those minor points later. Issue to fix them here https://issues.serokell.io/issue/CSM-470

@Martoon-00 could you approve as both of the points seems minor and there is an issue to track them https://issues.serokell.io/issue/CSM-470

Yes, CCoin represents integer number. Adas are measured in floating number with 6 digits after point, so Micro is used instead of Coin

:confused:
So:

maxCoinVal =<PHONE_NUMBER>0000000 - lovelaces, CCoin
maxCoinVal =<PHONE_NUMBER>0.000000 - Micro = Ada

So why not newtype CAda = CAda ... with either Text or something suitable for PS and return that?
If we return Micro, we have to manually define the PS side (conversions).

@akegalj Just said that there is no purescript for explorer

@Martoon-00 He said "no bridge" because he was thinking about wallet "bridge".
There is a "bridge" for explorer.

@Martoon-00 Sorry for the confusion. This is starting to sound more like an architectural discussion (patterns anyone?) than anything else.
There are two bridges, each bridge is for a separate frontend:

wallet
explorer

@akegalj Can you confirm we need a client representation for explorer - the "bridge" from Haskell to Purescript?

Can you confirm we need a client representation for explorer - the "bridge" from Haskell to Purescript?

@ksaric yes. Do we use Micro or this endpoint in the Explorer anywhere atm @ksaric ?

Do we use Micro or this endpoint in the Explorer anywhere atm

@akegalj No, we can create the suggested newtype CAda to represent this.

Also, we can create the suggested newtype CAda to represent this.

@ksaric yes, lets do this when this will be needed in UI. It is not needed right now.
I just checked how Micro is serialized and it gives scientific notation.
curl -v http://localhost:8100/api/supply/ada
*   Trying ::1...
* TCP_NODELAY set
* connect to ::1 port 8100 failed: Connection refused
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to localhost (<IP_ADDRESS>) port 8100 (#0)
> GET /api/supply/ada HTTP/1.1
> Host: localhost:8100
> User-Agent: curl/7.55.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Transfer-Encoding: chunked
< Date: Wed, 27 Sep 2017 12:04:26 GMT
< Server: Warp/3.2.13
< Content-Type: application/json;charset=utf-8
<
* Connection #0 to host localhost left intact
{"Right":4.499998899998801e10}

This looks ok to me.
Thoughts @Pastafarianist @ksaric @Martoon-00 ?

@dcoutts good to go?

I've opened #1664 (it needs immediate attention) and we'll be merging cardano-sl-1.0 to master, so I'm closing this one.

Tested here https://issues.serokell.io/issue/CSE-228#comment=96-7725

Changed base to cardano-sl-1.0 and reopened as it has been tested.

Closing due too cherry picked PR https://github.com/input-output-hk/cardano-sl/pull/1679


Progressbar issues with import_librivox.py

I ran into a sequence of issues using import_librivox.py

progressbar uses maxval not maxvalue
2)progressbar uses widgets not widget
C:\Users\dlevinth\machine_learning\deepspeech2>diff import_librivox.py import_librivox_orig.py
33,34c33
<   #with progressbar.ProgressBar(max_value=7, widget=progressbar.AdaptiveETA) as bar:
<   with progressbar.ProgressBar(maxval=7, widgets=progressbar.AdaptiveETA) as bar:
but then I ran into the following which I am unclear on how to resolve
levinth@moxli001:~/OpenSeq2Seq$ python3.6 scripts/import_librivox.py data/librispeech
Downloading Librivox data set (55GB) into data/librispeech if not already present...
Traceback (most recent call last):
File "scripts/import_librivox.py", line 190, in
_download_and_preprocess_data(sys.argv[1])
File "scripts/import_librivox.py", line 34, in _download_and_preprocess_data
with progressbar.ProgressBar(maxval=7, widgets=progressbar.AdaptiveETA) as bar:
File "/usr/local/lib/python3.6/site-packages/progressbar/progressbar.py", line 120, in init
self._update_widgets()
File "/usr/local/lib/python3.6/site-packages/progressbar/progressbar.py", line 240, in _update_widgets
for w in self.widgets)
TypeError: 'ABCMeta' object is not iterable

this is on ubuntu16.04.5 with python3.6 built from source in /usr/src with sudo

I followed the installation instructions
and installed the following missing packages
sudo pip3.6 install progressbar
sudo apt-get install sox libsox-dev libsox-fmt-all
sudo pip3.6 install sox
should I remove progressbar and install tqdm instead?
On Tue, Dec 11, 2018 at 10:32 AM Vitaly Lavrukhin<EMAIL_ADDRESS>wrote:

It looks like a mismatch in different progressbar versions. I switched to
tqdm package. Please try the latest master branch.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NVIDIA/OpenSeq2Seq/issues/308#issuecomment-446310674,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIUuTwMH4uxlt7_KXd_rFoDUr47Znivrks5u3_pNgaJpZM4ZMLYh
.

Sure. We don't use progressbar now. All required Python packages should be in requirements.txt.

thanks for replacing progressbar with tqdm
did the trick..
On Tue, Dec 11, 2018 at 11:36 AM Vitaly Lavrukhin<EMAIL_ADDRESS>wrote:

Sure. We don't use progressbar now. All required Python packages should
be in requirements.txt.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NVIDIA/OpenSeq2Seq/issues/308#issuecomment-446332974,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIUuT6fjxe6Z9R5EbYYIZ0invlQDG0h0ks5u4AkmgaJpZM4ZMLYh
.


Moves further device side error checks behind NO_SEATBELTS.

These (getVariable() for each message type) were all missing for some reason.

Tests have passed with and without seatbelts. It's a fairly trivial change so I will merge after CI.


Reorder clusterrole and clusterrolebinding

The template will create resources in order so the role needs to be created before the binding can use it

/hold
Putting a hold as the user that applies this role doesn't have the correct permissions


Server disconnected (code: 1006)

I got the container up fine, and MKVToolnix is running on the host machine, but I am getting the above error and my screen is basically blank when I access the web gui.
Any idea why this is happening?

Clearing the browser's cache usually fix this error.

I tried that and it didn't work.
I disabled host networking and re-created the container, and hey presto! It works now...


Spark | Update getting started tutorial

Summary

Updates to get started tutorial code and version used
Clarify where files created at build time reside.

Fixes #19668

Thanks @Youssef1313 and @adegeo for the review. I'll take a look and make the changes

@luisquintanilla ping

@adegeo other Ignite related work items took priority but planning to merge this week.

@luisquintanilla No rush! Just friendly ping 😄

Okay. I think this one's good to go. Whenever you get a chance @adegeo. Thank you! :)

@mamccrea can I please get a review on this when you get a chance. Thanks 🙂


Fixed props key was spread into JSX FitImage

Hi,
With the last version of react-native (0.75.4), the package display a warning for a deprecated code :
 ERROR  Warning: A props object containing a "key" prop is being spread into JSX:
  let props = {key: someKey, indicator: ..., style: ..., source: ..., accessible: ..., accessibilityLabel: ...};
  <FitImage {...props} />
React keys must be passed directly to JSX without using spread:
  let props = {indicator: ..., style: ..., source: ..., accessible: ..., accessibilityLabel: ...};
  <FitImage key={someKey} {...props} />

So I create this PR to fix it. As you can see, it’s really a light commit.
This PR work with last react-native version and previous one.
Do you think create a new npm patch 7.0.3 to add this modification ?
Thanks for reading.

Beat me to it, I was about to submit the same PR :)


Api 20130815

Update API, Add bunches of Table Operations, refactor integration tests

Merged in to let it go through CI, let me know if you see anything horrible stylistically BMac


Installation failed

Hello,
I wa trying to install the bundler to work with new posenet version from tensorflow but I get several errors:
npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated and is no longer maintained. Please use @rollup/plugin-commonjs.
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated<EMAIL_ADDRESS>This module has been deprecated and is no longer maintained. Please use @rollup/plugin-json.
npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated and is no longer maintained. Please use @rollup/plugin-node-resolve.
npm ERR! code 128
npm ERR! Command failed: git clone --depth=1 -q -b fde/max_target git://github.com/fde31/rollup.git C:\Users\dell\AppData\Roaming\npm-cache_cacache\tmp\git-clone-22fe93bb --config core.longpaths=true
npm ERR! warning: templates not found in C:\Users\dell\AppData\Local\Temp\pacote-git-template-tmp\git-clone-c3b24fe1
npm ERR! error: invalid path 'test/chunking-form/samples/sanitize-chunk-names/_expected/amd/_virtual:entry-1.js'
npm ERR! fatal: unable to checkout working tree
npm ERR! warning: Clone succeeded, but checkout failed.
npm ERR! You can inspect what was checked out with 'git status'
npm ERR! and retry with 'git restore --source=HEAD :/'
npm ERR!
npm ERR!
npm ERR!      C:\Users\dell\AppData\Roaming\npm-cache_logs\2020-02-28T15_31_25_802Z-debug.log
I am running on windows and tested the npm install inside max itslef

guess I'll need to take a pass on updating the dependencies. Thanks for the report.

Sorry, I accidentally duplicated that issue in your other repo. You can see the more detailed log file attached.
2020-03-23T12_03_25_026Z-debug.log


QR Code not scannable

Since a week I haven't been able to scan a new code. Worked fine previously, now I switched back from LineageOS to MIUI.

Hi, thanks for your feedback. What exactly is the issue? Which phone are you on and which app version?
Is it maybe #61 or #71 ?

Hi, thank you for the quick response and for your otherwise great app! My phone is a
Xiaomi POCO F3 and i'm on MIUI 12.5.2 with no google play services. (Signature Spoofing is not up and running yet).
The App version is 1.7.2.
Before I was on LineageOS with some Signature Spoofing (some apps were spoofed some weren't) and on the same app version.
Unfortunately it is neither of the two issues. The QR code shows but it is not scannable from any phone, no matter if Multidevice enabled or disabled. I will look into whether it is my phone that is not capable of generating QR codes atm, (will try sharing a WiFi when I'm back home).

Started working 3 days ago. All good now!

interesting :D do you know what changed?

nope, no idea, did you release a new version?

no, still 1.7.2. I guess an android webview update oder wa web internal update fixed it - still strange.
Anyway, glad it works for you now!


styles

Issue Type (delete the irrelevant ones)

[x] Question ---- Canned styles not being applied.

Specs
"vue-good-table": "^2.16.3",
"vue": "latest",
"vue-template-compiler": "latest",
What browser?
firefox 65.0.1
Expected Behavior
Table to be styled
Actual Behavior
Table is not styled.
Steps to Reproduce the Problem
Just using vue-good-table in default mode.

hey @stevyrino! could you show me how you're importing it? did you import the styles?
https://xaksis.github.io/vue-good-table/guide/

Yes .... I wasn't importing the styles correctly ... cheers.


tvg: revise the binary version check

Replace the TVG header version information with auto-generated version info to prevent human-mistakes.
replace (in tvgFormat.h)
#define TVG_HEADER_VERSION "010000"       //Major 01, Minor 00, Micro 00
#define TVG_HEADER_VERSION_LENGTH 6

with (in config.h)
#define THORVG_VERSION_STRING "0.14.99"

@hermet is there a way we can get the THORVG_VERSION_STRING from ThorVG C bindings ?

@theashraf No APIs yet, Any use cases? Probably we can provide apis if the use-case makes sense.

@hermet Our use case involves avoiding hardcoding the Thorvg version in dotLottie-rs. Instead, it would be beneficial to pull this version directly from Thorvg itself as a single source of truth. This approach would ensure that the version is consistent across all our bindings, including dotLottie-android, iOS, and web. This way, users can easily identify which versions of dotLottie-rs and Thorvg they are currently using. Let me know your thoughts.
For example, in dotLottie-viewer, we currently display a Thorvg version that we need to update manually every time we update the Thorvg version. Sometimes, we miss updating it, which results in incorrect information being displayed to the user.

@theashraf please follow up this issue: https://github.com/thorvg/thorvg/issues/2543  thanks.


gt_prob question

Hello,
How is the gt_prob parameter in unary_from_labels() used in the original paper?

Hi and sorry for the very late answer! I am not the author of the original paper, and this wrapper was created much later than the original paper, so I'm not sure how to interpret your question.

Closing due to no clarification.


"Can't open file error" in Mojo::Asset::File

Recently upgraded from 4.26 to 6.15 (and now 6.16), suddenly getting lots of errors from uploads:
[2015/08/20 13:46:38] error: Can't open file "/tmp/mojo.tmp.096a27496a2b8632cada9bd978f822f2": No such file or directory

Even stranger, sometimes the errors look like this:
[2015/08/20 13:33:57] error: Can't open file "/tmp/mojo.tmp": No such file or directory

Since there are 2 Instances of this application running on two servers behind a load-balancer, I figured the load-balancer directed upload chunks to different servers and thus caused the problem. So I set MOJO_TMPDIR to a path on a shared NFS volume, hoping it would solve the problem, but unfortunately it didn't.
The culprit in my upload endpoint code is probably this:
  my $asset;
  if ($c->req->content->is_multipart) {
      $asset = $c->param('file')->asset;
  } else {
      $asset = $c->req->content->asset;
  }

  if (open(my $fh, ">>", $part_path)) {
      print $fh $asset->slurp;
      close($fh);
  }

I haven't been able to reproduce this in my development environment, so I can't provide a test case. It doesn't even always happen in production, only intermittently.
But from looking at the source of Mojo::Asset::File (https://github.com/kraih/mojo/blob/v6.16/lib/Mojo/Asset/File.pm#L27), shouldn't md5_sum() be appended to $base before the until-loop starts? That at least explains the different filenames I'm seeing.
Otherwise I'm at a loss here, any help would be greatly appreciated.

Are you sure you can write to /tmp as the user that the process is running as? Are you running the server with hypnotoad? Maybe you missed out on https://github.com/kraih/mojo/blob/master/Changes#L39
The md5_sum() logic is simply to ensure a unique file, if there is already a temp file existing.

Yes, I'm running hypnotoad and no, I didn't miss that change. The user has permissions to write to /tmp, in fact there are temporary files there:
-rw-r--r--  1 www www  334K Aug 20 15:13 mojo.tmp.ec248220e3554cb30c2e28f034ef63db

Also, since the error is "No such file" and not "Permission denied", I kinda doubt that's the problem :(

FYI: this was previously running under perl-5.16.3, I just upgraded to 5.22.0. Problem persists.

We need a test case for this, preferably in t/mojo/asset.t.

The slurp method got optimized a little recently, perhaps that caused it, but impossible to say until we are able to replicate the problem. https://github.com/kraih/mojo/commit/959157c767c93e777d32e1b778103adce5c8cd65#diff-4e1bdb34da448764c931ba03e53f8feeL130

As I said, haven't been able to reproduce this on my machine. Will give it another shot tomorrow, though.

I'm afraid then there is not much more we can do at the moment. Closing this issue for now, and will reopen it if there is new information.

I don't think the slurp optimizations are the cause, AFAICT we never reach that code.

FYI: I downgraded Mojo on one of the two machines to 4.67, no error in the last 15 minutes.

@prg: Try upgrading in steps. As in 4.90, 5.00, 5.xx, 6.00, ...

Already on it, currently running 5.00 and waiting for errors to occur.

So far everything >= 5.40 produced errors, everything <= 5.30 seemed fine (although that's harder to tell, but I waited for approx. 20 minutes every time which should be plenty).
Currently running 5.35, hopefully I'm closing in on this...

I just noticed something else:
I was running 5.31 for about 20 minutes without problems, and just as I started cpanm<EMAIL_ADDRESS>an error occured. I'm guessing something in the build process/tests is wiping MOJO_TMPDIR?

Perhaps you could git bisect around that time to see if you can pin it down
to a commit?
On Fri, Aug 21, 2015 at 7:04 AM Patrick Goldmann<EMAIL_ADDRESS>wrote:

I just noticed something else:
I was running 5.31 for about 20 minutes without problems, and just as I
started cpanm<EMAIL_ADDRESS>an error occured. I'm guessing something
in the build process/tests is wiping MOJO_TMPDIR?
—
Reply to this email directly or view it on GitHub
https://github.com/kraih/mojo/issues/833#issuecomment-133392366.

@jberger I'll try to make time for that.
Right now I'm back to running 5.30, when I downgraded once more from 5.32 to 5.31 (to verify it was OK) I got another error. Looking at the Changelog, this makes no sense to me at all.

Been running on 5.30 for an hour now without any incident.
Looking at https://github.com/kraih/mojo/compare/v5.30...v5.31, there have been some changes to Mojo::Asset::File. I'm guessing they are the problem.

"The culprit in my upload endpoint code is probably this" ... does that mean that it's not your actual code? Please paste more of your actual code.

The change I can see is that 0.30 use the filehandle, while 0.31 use the path... Maybe the file is somehow unlinked from the filesystem, but still accessible by the direct handle? Can you try to Change back the slurp() method, but leave everything else is in 0.31?
https://github.com/kraih/mojo/compare/v5.30...v5.31#diff-4e1bdb34da448764c931ba03e53f8feeR128
Also, did you say that the temp file is stored on nfs..?

It is my actual code, and the rest of it is probably irrelevant. Stuff like
  my $file_path = try { $c->_order->uploadPath($file_name) };
  ...
  my $part_path = "$file_path.part";

which I think doesn't help anyone in debugging this.
Initially I tried pointing MOJO_TMPDIR to a path on a NFS share, but since it was clear that this wasn't the problem I reverted that (defaulting to /tmp again).
Right now I have other issues to handle, I'll try to manually modify slurp() and/or do a git bisect when I have time.

That's literally the commit i pointed at earlier. https://github.com/kraih/mojo/commit/959157c767c93e777d32e1b778103adce5c8cd65#diff-4e1bdb34da448764c931ba03e53f8feeL130

And i assume this commit makes all problems go away. (still without tests!) https://github.com/kraih/mojo/commit/ec7920ea74e9fdb8316037316d3c08cf195a9e0b

Well, since you said recently, I figured you meant https://github.com/kraih/mojo/commit/683f4a23db4bd48ea09189d9fb83d95f4c620ce9 and https://github.com/kraih/mojo/commit/04732845a2b30d7e6d5e7f0d9064b58205dfa678. Surely my mistake that I didn't look more closely, but to be honest: you have an interesting definition of recently, seeing as https://github.com/kraih/mojo/commit/959157c767c93e777d32e1b778103adce5c8cd65 is from almost exactly one year ago.
And since you came up with the solution, I'm confident you'll be able to write tests for this :)

@prg Actually, i've been unable to find a test case. So odds are someone will break it again at some point.

@kraih how about:
diff --git a/t/mojo/asset.t b/t/mojo/asset.t
index 8b82fbe..b476a02 100644
--- a/t/mojo/asset.t
+++ b/t/mojo/asset.t
@@ -191,7 +191,9 @@ ok $asset->is_file, 'stored in file';
 $asset = $asset->add_chunk('lala');
 is $upgrade, 1, 'upgrade event was not emitted again';
 ok $asset->is_file, 'stored in file';
-is $asset->slurp,   'lalalalalala', 'right content';
+ok $asset->handle, 'got handle';
+unlink $asset->path;
+is $asset->slurp, 'lalalalalala', 'right even if file is removed';
 ok $asset->cleanup, 'file will be cleaned up';
 $asset = Mojo::Asset::Memory->new(max_memory_size => 5);
 $asset = $asset->add_chunk('lala');

Just wanted to confirm the problem is gone in 6.17, been running that since this morning.

Hi,
sorry i'm a newbie with Mojo, and i have a question related to this topic if you don't mind.
I see that Mojo is temporary storing the file uploaded into /tmp/mojo.tmp
What is going on if i run multiples workers with prefork and the service receive multiples upload simultaneously ? Does mojo use different tmp file names ?
Otherwise, a workaround is tu use slurp, but slurp is returning "more" than the file content posted
ie :
------WebKitFormBoundaryZthpSWxw9tWBTrTj
Content-Disposition: form-data; name="filepdf"; filename="msg.pdf"
Content-Type: application/octet-stream
...
Finally
Is there any way to only get the file content and only the file content ?
Many thx.

@akelwood please don't reuse closed issued for a different (if related question). It sounds to me like you should ask the mailing list or come chat with us on #mojo on irc.perl.org. http://mojolicious.org/perldoc#SUPPORT


Reduce memory usage

Hello
Thank you so much for audfprint, your implementation of audio recognition works much better and more accurately than others on Python. I experimented with different settings to achieve an excellent result, and to some extent I managed to find a middle ground, but noticed a very serious problem that others have no implementation - this is a huge use of memory, even with standard settings. From the very beginning I thought that the problem in gzip while saving and opening saved hashes, but as it turned out we really had a problem in pickle, I decided to replace it with HDF5 similar storage using the hickle library (which has an interfeis similar to pickle), but the problem still did not solve it. The use of memory in general when analyzing even 1mb file is approximately 1.5gb, which is very critical (I have Linux with 2.0 GB, Celeron)
What are your thoughts? Could it be better to use MySQL as in this project?

Do you mean RAM or Disk?  Gzip, HDF5 sound like solutions to the space
on-disk, but big disks are cheap.  I think the RAM usage is more often the
problem: the reference table is read into RAM in a space-inefficient (but
access speed-efficient) way; by default it occupies 400MB, which I hoped
would be OK in current machines.
The real problems I've observed are the dynamic memory using when matching
against large databases.  During matching, the program retrieves lists of
all the reference tracks implicated by each individual landmark extracted,
then filters to find the most promising reference items.  When the
reference database gets big, and when the reference items are large, you
can end up with a large portion of the reference items looking promising,
and so very large initial lists of tracks to check.  There's no simple fix
here, although shorter reference items can reduce the likelihood of pulling
in every item.
DAn.
On Thu, Jan 28, 2021 at 9:11 AM Zhymabek Roman<EMAIL_ADDRESS>wrote:

Hello
Thank you so much for audfprint, your implementation of audio recognition
works much better and more accurately than others on Python. I experimented
with different settings to achieve an excellent result, and to some extent
I managed to find a middle ground, but noticed a very serious problem that
others have no implementation - this is a huge use of memory, even with
standard settings. From the very beginning I thought that the problem in
gzip while saving and opening saved hashes, but as it turned out we really
had a problem in pickle, I decided to replace it with HDF5 similar storage
using the hickle https://github.com/telegraphic/hickle library (which
has an interfeis similar to pickle), but the problem still did not solve it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dpwe/audfprint/issues/81, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEGZUITPJF74UXLPT7WXVTS4FWCJANCNFSM4WXD6QIA
.

Do you mean RAM or Disk?  Gzip, HDF5 sound like solutions to the space
on-disk, but big disks are cheap.  I think the RAM usage is more often the
problem: the reference table is read into RAM in a space-inefficient (but
access speed-efficient) way; by default it occupies 400MB, which I hoped
would be OK in current machines.
The real problems I've observed are the dynamic memory using when matching
against large databases.  During matching, the program retrieves lists of
all the reference tracks implicated by each individual landmark extracted,
then filters to find the most promising reference items.  When the
reference database gets big, and when the reference items are large, you
can end up with a large portion of the reference items looking promising,
and so very large initial lists of tracks to check.  There's no simple fix
here, although shorter reference items can reduce the likelihood of pulling
in every item.
DAn.
On Thu, Jan 28, 2021 at 9:11 AM Zhymabek Roman<EMAIL_ADDRESS>wrote:

Hello
Thank you so much for audfprint, your implementation of audio recognition
works much better and more accurately than others on Python. I experimented
with different settings to achieve an excellent result, and to some extent
I managed to find a middle ground, but noticed a very serious problem that
others have no implementation - this is a huge use of memory, even with
standard settings. From the very beginning I thought that the problem in
gzip while saving and opening saved hashes, but as it turned out we really
had a problem in pickle, I decided to replace it with HDF5 similar storage
using the hickle https://github.com/telegraphic/hickle library (which
has an interfeis similar to pickle), but the problem still did not solve it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dpwe/audfprint/issues/81, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEGZUITPJF74UXLPT7WXVTS4FWCJANCNFSM4WXD6QIA
.

I'm sorry I haven't answered for so long.

Do you mean RAM or Disk?

I meant RAM. The files themselves in disk principle inside gzip weigh 1024 times less. I experimented with different methods of saving audio hashes table to a file, and did not achieve much result. The more audio hashes, the more audfprint takes memory during the recognizing. After looking at the code, I came to the conclusion that you need to transfer the mechanism for reading and saving audio hashes table. Now, alas, I'm busy finding time to try to implement what I'm thinking.


[dv/top_earlgrey] lc ctrl register access acquisition for JTAG failure when in SCRAP state

Signed-off-by: Dror Kabely<EMAIL_ADDRESS>This test tries to perform the following LC state transition: TEST_LOCKED1->SCRAP.
The transition completes successfully, then a hard reset is issued.
After finishing the reset, we try to check that we indeed changed into SCRAP by trying to acquire access for LC_CTRL registers for the JTAG TAP, then reading the LC_STATE register in order to compare the read value to SCRAP.
However, the test gets stuck at the acquisition of the LC_CTRL access stage post reset. (hw/top_earlgrey/dv/env/seq_lib/chip_sw_lc_ctrl_scrap_vseq.sv#65)

Thanks for pushing this to a draft PR, @dkabely-ot. Can you also add your changes in chip_sim_cfg.hjson so that I can check the configuration? I have hacked something together locally so that I can run and debug, but I just wanted to double check.

Alright, there are two reasons why this is currently failing:

behavior of READY bit and FSM in LC_CTRL, will be fixed by https://github.com/lowRISC/opentitan/pull/15962. You should then use wait_lc_initialized(.allow_err(1)); instead of wait_lc_ready(.allow_err(1)); if only reading status (and not performing a transition).
the strap sampling pulse from pwrmgr to pinmux is never asserted in SCRAP state, since the pwrmgr gets stuck waiting for the ROM checker to complete. this does not succeed successfully in SCRAP at the moment, since KMAC is not operational in SCRAP (on purpose!). this issue will be solved by https://github.com/lowRISC/opentitan/pull/15602 which rearranges the strap sampling sequence.

If you want to make progress while waiting for https://github.com/lowRISC/opentitan/pull/15962 to be merged, you can rebase  onto https://github.com/lowRISC/opentitan/pull/15962 and remove the associated commits later when pushing this again.

I believe we can close this now.