Weird highlight results with non-ascii

Describe the bug
Meilisearch is giving weird results compared to algolia and typesense.
To be honest I don't know if the software is built to behave in this way, or the language I use is unsupported. I wanted to report this in any case. I there is a settings toggle for it to become strict, I'd like to know. I also uploaded the data to http://search.staging.academicpositions.com/ for you to try. (Not sure who owns the website though.)
To Reproduce
Steps to reproduce the behavior:

Go to meillisearch dashboard
Search for "Müəllimlərin İşə Qəbulu - Təsviri İncəsənət" or "Təsviri İncəsənət"
See the weird results

Expected behavior
Should show correct results as algolia and typesense.
Screenshots
Check out the video where I explain the results. Don't forget to enable audio.
https://user-images.githubusercontent.com/15037839/152649267-56b590cf-7093-457d-a167-339e4983fa61.mp4
if you want, here is youtube link https://www.youtube.com/watch?v=kumI6XbjnUA
Meilisearch version: v0.22.0, v0.25.2

With ascii-only it seems more correct, but I still would like to get single result in both cases
(Make sure to enable audio)
https://user-images.githubusercontent.com/15037839/152649679-2c330ace-5477-425d-be2a-6ab069d28a7c.mov

Hey @OrkhanAlikhanov,
Thank you very much for your issue and detailed explanation!
This bug seems to be highly related to the default Meilisearch tokenizer, Algolia uses a Unicode segmentation algorithm, and Typesense, IIRC, uses a basic split by whitespace system. We use a custom algorithm and it seems like it is the source of the issue here.
However, we plan to improve the tokenizer we use and we will probably expose a Unicode segmentation system too. @ManyTheFish plan to work on this for future releases. We will also expose parameters to disable the remove-words-at-the-end-of-the-query for when there are not enough documents to fulfill the 20 results.

Hey! Thank you for the detailed answer. How can one contribute to this. Is it easy to update tokenizer function or? Any directions if I want to mess around to workaround this issue?

I put this issue in v0.28.0. The new tokenizer might be fix this, nothing sure, we need to test once the first RC is done

Hello @curquiza, after some tests I'm confident that the new tokenizer will fix this issue. 😄

So this issue will be fixed when https://github.com/meilisearch/meilisearch/issues/2375 will be fixed 🚀


Function field fixes

Recent fixes to allowing you to reset the values of fields, caused issues with function fields. This was because previously those fields set the value of a property to it's default. Now we just pass the default value to the fields rather than mutating the value (see https://github.com/maputnik/editor/pull/563/files#diff-b98b1ae2788532d29e7217366330abaaL68). This resulted in the values being undefined when transitioning to 'function fields', causing the spec validator to throw an error.
This PR adds a new method findDefaultFromSpec which uses the default from the spec, else it falls back to a set of generic defaults (some properties don't have defaults).
I've also fixed enum to use the <EnumInput /> again, which was previously defined in <SelectInput/>

I'm not sure which issue this PR fixes exactly, but there is still an issue, e.g. click on the "Turn property into function ..." button of Allow overlap:

Nice find, fixed in latest commit
Demo: https://1731-84182601-gh.circle-artifacts.com/0/artifacts/build/index.html#0.35/0/0

Thanks @orangemug, looks good now.

Thanks, merging


QI Core Value Set and Code System Query Issue

Qi core data elements to spreadsheet tooling is missing value set and code systems for race and ethnicity.
These elements are must support under the QI Core patient profile- http://hl7.org/fhir/us/qicore/STU4.1.1/StructureDefinition-qicore-patient.html but were not in the last output from the tooling.

The data elements code does not go through the extensions in the elements and add them to the results. If those code systems and value sets are wanted the code needs to be refactored in QICoreElementsToSpreadsheet.java to loop through the extensions. Their format is "Patient.extension:ethnicity".
I wrote this coded and would be happy to take this on. If that is desired.

PR for this: https://github.com/cqframework/cqf-tooling/pull/531


Enable SingleFile Trimmed Publishing

We can shrink the size of the test-proxy executable by setting two additional configuration items in the csproj.

[ ] <PublishTrimmed>true</PublishTrimmed>
[ ] <PublishSingleFile>true</PublishSingleFile>

However, breaks some of the assumptions that we've been safe to make so far. Mostly around reflection and how we offer the metadata for available customizations via Info/Available. Specifically, GetExecutingAssembly() actually works differently for single package publishing as far as I can tell.
On top of that, we also need to ensure that none of our parsing is broken by the fact that we are adding trimming of the DLL to the build process.
When producing a standalone executable for win-x64, the trimmed exe is 90MB versus the normal 160MB, so it's quite an appreciable improvement.
This issue covers enabling these and ensuring functionality remains stable.

Closing this. If the 50MB download becomes a problem we will revisit.


Neodigm Enchanted CTA | After some time the ambient animations take over the entire page

This only exists on the landing page / TSK due to its implementation code. It looks like when any soda pop opens the N55_CTA_RND_TOUCH value being set to 800. This is too fast for the revert function to set the CTA back to its original state. This is most conspicuous on pages that have the widget carousel due to the high number of subscribing CTA elements.
Steps to Reproduce: Go to any widget page on TSK and open then close the contact soda pop.

This is fixed in v3.1. The Touch logic now cleans up after itself, forcing the whole collection of CTA to a stage of no ambient animation . While this is not an absolute fix, it is a compromise between having only one ambient animation and having then fire in rapid succession. The experience is much improved.


Feature/application

Coverage increased (+0.6%) to 73.544% when pulling 6a539dabd77e5a30cd4c0666ca6eb6054695744d on feature/application into 781bfca63785e67a32f4f5ded750e24531369f18 on master.


Parallelize I/O operations

Overview
Currently, vcztools view loads data from Zarr and writes the VCF output sequentially. These operations can be done in parallel. This pull request uses multi-threading to parallelize reading from Zarr and writing the VCF output.
I am opening this pull request as a draft because I think additional changes are likely needed.
Approach
The sequential implementation has the following form:
def vcztools_view():
    for chunk in chunks:
        handle_chunk(chunk)

def handle_chunk(chunk):
    load_dataset1()
    load_dataset2()
    write_output()

Here is the form of this pull request's multi-threading approach:
def vcztools_view():
    with ThreadPoolExecutor() as executor:
        preceding_future = None
        for chunk in chunks:
            future = executor.submit(handle_chunk, chunk, preceding_future)
            wait(preceding_future)
            preceding_future = future

def handle_chunk(chunk, preceding_future):
    load_dataset1()
    load_dataset2()
    wait(preceding_future)
    write_output()

This approach allows at most two threads to run concurrently and requires the preceding thread to finish before the current thread can start writing.
Testing
I added a multi-chunk dataset for unit testing. The dataset is a 100 variants by 100 samples subset of the chromosome 22 performance testing data. The variant and sample chunk sizes are each 10. Having a multi-chunk dataset should help us detect concurrent-programming errors such as not writing the output in the correct order.
Results
The results are disappointing so far. There is practically no improvement over the sequential implementation's results in #94.
bcftools view data/chr22.vcf.gz
1.67GiB 0:00:10 [ 162MiB/s] [                             <=>                                                                                ]

real    0m10.533s
user    0m10.142s
sys     0m0.481s

vcztools view data/chr22.vcz
1.67GiB 0:00:24 [70.1MiB/s] [                                                                <=>                                                                      ]

real    0m24.411s
user    0m23.836s
sys     0m4.271s

Profiling
Interestingly, the the profiling results show most of the time being spent on acquire.
         815373 function calls (794975 primitive calls) in 23.215 seconds

   Ordered by: internal time

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
      104   22.278    0.214   22.278    0.214 {method 'acquire' of '_thread.lock' objects}
      115    0.385    0.003    0.388    0.003 {built-in method _imp.create_dynamic}
      772    0.085    0.000    0.085    0.000 {method 'read' of '_io.BufferedReader' objects}
   115/77    0.064    0.001    0.137    0.002 {built-in method _imp.exec_dynamic}
      654    0.039    0.000    0.039    0.000 {built-in method marshal.loads}
      656    0.020    0.000    0.020    0.000 {built-in method io.open_code}
     3155    0.012    0.000    0.012    0.000 {method 'sub' of 're.Pattern' objects}

References

#94
Zarr parallel computing and synchronization
Python threading
PEP 703

Describes the challenges of parallel programming in Python.

Apple's threading guide

I looked at this since I am using an Apple M1 device.

Python C-API

Describes how to release the global interpreter lock in C extension code.

I suspect that moving the variant-wise encoding for-loop to the VCZ encoder library will help.
https://github.com/sgkit-dev/vcztools/blob/d152af13abb51da276b6e4603aa4ec3764d560e8/vcztools/vcf_writer.py#L397-L406
This way the C extension can release the GIL for all of the lines rather than acquiring and releasing for every line.

I pushed the for-loop down to the C extension, and now I am seeing the hoped-for results:
bcftools view data/chr22.vcf.gz
1.67GiB 0:00:10 [ 162MiB/s] [                             <=>                                                                                ]

real    0m10.525s
user    0m10.173s
sys     0m0.468s

vcztools view data/chr22.vcz
1.67GiB 0:00:17 [95.7MiB/s] [                                             <=>                                                                                ]

real    0m17.874s
user    0m23.969s
sys     0m3.347s

To get this prototype working, I used puts to print the output from C. However, vcztools does not always write to the standard output, and I am thinking about the best way to write the output from the C extension. Some of Python's I/O objects do not have file descriptors associated with them. For example, the test cases appear to use a TextIO object that raises an exception when fileno() is called.
References

C stdio
io module
File Objects C API

In the latest commit, the encode_all method uses fputs and fputc to write the output to the output file descriptor. In Python land, if the output I/O object has a file descriptor, then Python passes it to encode_all. If not, such as in the test cases, then Python creates a pipe for encode_all to write to and copies the pipe data to the output I/O object.
With this approach, all the test cases pass locally and the performance is still improved.
I am not sure why the GitHub checks are failing. They seem to be unrelated to this pull request's changes.

I am not sure why the GitHub checks are failing. They seem to be unrelated to this pull request's changes.

Sorry @Will-Tyler that's my fault! The changes in #95 caused ruff to change Optional[X] to X | None since that is allowed in Python 3.10 (see https://docs.astral.sh/ruff/rules/non-pep604-annotation/).
You should be able to rebase and run pre-commit run -v --all-files to get ruff to update your changes. (You may need to pip install pre-commit first.)

Very nice @Will-Tyler! I'm nervous about the C code writing directly to the FD though, there's a lot that can go wrong here and we'd need to work quite a bit harder to make things air tight (e.g., there's no error checking at the moment, so if a write fails it's silent). What you can and can't do while holding Py_BEGIN_ALLOW_THREADS etc is also very subtle, and it definitely pays to keep things as simple as possible.
What I had in mind was to write multiple lines at once to a buffer, and then flush these buffers out in-order to the output in Python. So, you could have something like this:

Zarr decode thread: decodes variants chunks, and pushed onto a queue
VCF encode thread(s): encodes numpy array(s) slice to VCF, returning buffer and pushing onto a priority queue (tagged by the chunk and slice index)
IO Write thread - consumes encoded VCF buffers in order, writing to output

This is quite a bit more complicated that what you have here as you'd need to set up some Queues etc to keep the threads fed , but I think it would perform quite well ultimately. We wouldn't need to go to the full thing initially though, and I think just writing the output to a pre-supplied buffer from C would be a good start.
So, rather than writing one line, we write a range of lines. Also, let's just raise an exception from C if the buffer size is too small rather and do the doubling in Python than trying to do the adaptive updates in C.
Keeping things as simple as possible in C is really important here. There's no point in trying to optimise the corner cases (i.e, you've supplied a buffer size that's too small) - do the important nominal case thing fast in C, and leave everything else to Python.
So, for this first PR, let's use your current architecture, but write the full chunk to a string that we return to Python rather than doing the IO in C. Does this sound OK?

I think that to get the most from parallelism, the extension module should do as much work as possible with the GIL released. If I understand correctly, you are proposing to encode multiple lines to a single buffer and raise an exception from C if the buffer is too small. I'm concerned that if the number of lines is too small, then the module will acquire the GIL too frequently and if the number of lines is too large, then vcztools might redo a lot of work whenever the buffer is too small. And if Python does the I/O, that is less parallelism because the I/O thread would need the lock although simply printing does not seem to be a top time consumer.

What you can and can't do while holding Py_BEGIN_ALLOW_THREADS etc is also very subtle.

This is true. I believe my current implementation is thread-safe. The raw memory interface my implementation uses are documented as thread-safe.

There's a lot that can go wrong here and we'd need to work quite a bit harder to make things air tight (e.g., there's no error checking at the moment, so if a write fails it's silent).

I feel like I am missing something but it seems overall simpler and more efficient to use C's standard I/O API and add error handling rather than share buffers between threads and C and Python.

The buffer won't be too small very often (we'll make the default much bigger, and make better guesses) so we don't need to worry about that. By writing multiple lines to at once, we can do a significant chunk of work with the GIL released. The difference between doing file IO in C and Python is negligible if you're writing a lot of text at a time, so there's no point in doing the IO in C unless you have to. It's easy to get stuff like this to work initially, but it's very hard to get it it fully air-tight and any minor efficiency you gain by doing stuff directly in C is bought at a high cost in subtle and difficult to track down bugs later on (I have war stories!).
I'm happy to pick this up and take it the last few steps, but I do want to take the C-level IO out before merging. You can just take out the encode_all method and not worry about the performance for now.

I trust your judgement and experience—I reverted some of the changes so that this pull request is mostly about setting up the parallel threads.


[FEATURE] - Blue Green Deployment Reference Implementation

Add a reference implementation for the blue green pattern, usually adopted to control the deployment of new cluster versions.
I would like to have a reference implementation integrated in the AKS Secure Baseline. The implementation is based on Terraform and is retro.compatible with the previous, enabling deployment also of a single cluster.

The Azure Mission-Critical Reference Implementation does a full working version of blue-green deployments, including the pipeline automation (which is the actual tricky part in this): https://github.com/Azure/Mission-Critical-Online

the idea is to provide blue green as generic pattern, that of course is also part of the mission critical workloads. Some users can be still interested in the blue green without implement a full mission critical architecture.

Indeed, and I don't mean that everybody needs to implement a full mission-critical architecture. People can also just take certain pieces of the reference implementation, like the blue-green deployment approach (and lots of them are).
I just wanted to give you a pointer to there, so you don't go and reinvent the wheel ;)


Initial Content Writup

Included Content
Summary of Content Added

Welcome Page
TL;DR - simple refence page
Git Overview
Installing Git
Common Commands
Creating a repository
Changes, Staging and Commits
Branches, Stashes and Tags
Merging
Rebasing
Configuring Git
GitHub Overview
Setup
Creating, Cloning and Uploading Remote Repositories
Push, Pull, Fetch
Forks
Template Repositories
Collaborating
Issues
Pull Requests
Milestones
Tags and Releases
Discussions
Licensing and OSS
A Sample Workflow

Still Todo

Wikis
GitHub Actions
GitHub Pages
GitHub Organisations

Looks amazing Tyler! Very user friendly and definitely invaluable as a reference to new GIT users.
I can think of relevant extension topics I can contribute with like GitHub actions, YAML syntax, CI/CD workflows and integrations with cloud services but no free time atm 😅

Add the desired topics as issues and you or someone else can add them later.


Accelerate estimate-memory not working.

System Info
- `Accelerate` version: 0.21.0
- Platform: macOS-14.5-arm64-arm-64bit
- Python version: 3.10.14
- Numpy version: 1.26.2
- PyTorch version (GPU?): 2.1.0 (False)
- PyTorch XPU available: False
- PyTorch NPU available: False
- System RAM: 16.00 GB
- `Accelerate` default config:
        Not found

Information

[X] The official example scripts
[ ] My own modified scripts

Tasks

[ ] One of the scripts in the examples/ folder of Accelerate or an officially supported no_trainer script in the examples folder of the transformers repo (such as run_no_trainer_glue.py)
[ ] My own task or dataset (give details below)

Reproduction
When running the accelerate cli to estimate the memory usage of a HuggingFace model according to the documentation a invalid command choice is being returned.
Command:
accelerate estimate-memory bert-base-cased
Error:
usage: accelerate  []
Accelerate CLI tool: error: argument {config,env,launch,tpu-config,test}: invalid choice: 'estimate-memory' (choose from 'config', 'env', 'launch', 'tpu-config', 'test')
Replication:
Execute mentioned command
Documentation Link:
https://huggingface.co/docs/accelerate/main/en/usage_guides/model_size_estimator
Expected behavior
Return a table representation of the dtypes and memory usage as described in the documentation.

You need to upgrade your accelerate version


bug(vite): ENOENT: no such file or directory, open '/__skip_vite/.nuxt/components/nuxt-error.vue'

Environment

Operating System: Linux (via Windows 11 WSL)
Node Version:     v16.19.0 (also tested Node 18)
Nuxt Version:     2.16.3
Nitro Version:    2.3.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      bridge, nitro, serverHandlers, devServerHandlers, devServer, typescript, buildModules
Runtime Modules:  -
Build Modules<EMAIL_ADDRESS>

Reproduction
https://github.com/AndreyYolkin/nuxt-bridge-skip-vite
https://codesandbox.io/p/sandbox/frosty-leftpad-cn0sgz
Run npm run dev or open the Sandbox link

Describe the bug
In dev mode, Nuxt built-in files are not loading in a propper way, which causes ENOENT on server
Additional context
It remembers this issue: https://github.com/nuxt/bridge/issues/649
"Literally no one cares, but I get annoyed by anything" - magic string to attract attention)
Logs
ERROR  1:13:33 PM [vite] Internal server error: ENOENT: no such file or directory, open '/__skip_vite/.nuxt/components/nuxt-error.vue'                                                13:13:33
      at Object.openSync (node:fs:590:3)
      at Object.readFileSync (node:fs:458:35)
      at getDescriptor (file:///home/user/nuxt-bridge-app-spa/node_modules/@vitejs/plugin-vue2/dist/index.mjs:86:66)
      at Context.load (file:///home/user/nuxt-bridge-app-spa/node_modules/@vitejs/plugin-vue2/dist/index.mjs:1075:28)
      at Object.load (file:///home/user/nuxt-bridge-app-spa/node_modules/vite/dist/node/chunks/dep-79892de8.js:43360:46)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at async loadAndTransform (file:///home/user/nuxt-bridge-app-spa/node_modules/vite/dist/node/chunks/dep-79892de8.js:41038:24)

 ERROR  1:13:33 PM [vite] Internal server error: ENOENT: no such file or directory, open '/__skip_vite/.nuxt/components/nuxt-loading.vue'                                              13:13:33
      at Object.openSync (node:fs:590:3)
      at Object.readFileSync (node:fs:458:35)
      at getDescriptor (file:///home/user/nuxt-bridge-app-spa/node_modules/@vitejs/plugin-vue2/dist/index.mjs:86:66)
      at Context.load (file:///home/user/nuxt-bridge-app-spa/node_modules/@vitejs/plugin-vue2/dist/index.mjs:1075:28)
      at Object.load (file:///home/user/nuxt-bridge-app-spa/node_modules/vite/dist/node/chunks/dep-79892de8.js:43360:46)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at async loadAndTransform (file:///home/user/nuxt-bridge-app-spa/node_modules/vite/dist/node/chunks/dep-79892de8.js:41038:24)

Same issue here !

@danielroe Looks like this was broken in your PR #724, are there any plans to fix it?

For sure! Equally, you should feel free to submit a PR if you get to it before I do. 🙏

I didn't dive deeply but it's interesting for me, why it's working in Nuxt3. Also I'm curious about the origins of __skip_vite prefix 🫨

@danielroe I'm not familiar enough with the codebase however I did come up with a nasty workaround for the time being that others are free to use:
defineNuxtModule({
  meta: {
    name: 'SkipViteFix',
  },
  setup(_options, nuxt) {
    let cachedViteServer: ViteDevServer | null = null;
    nuxt.hook('vite:serverCreated', async (viteServer) => {
      cachedViteServer = viteServer;
    });
    nuxt.hook('server:devHandler', () => {
      const viteServer = cachedViteServer;
      if (!viteServer) {
        console.error('No vite dev server');
        return;
      }

      let insertionPoint = viteServer.middlewares.stack.findIndex(
        (m) =>
          m.handle instanceof Function &&
          m.handle.name === 'viteTransformMiddleware'
      );
      if (insertionPoint == -1) {
        console.error('Invalid middleware insertion point ' + insertionPoint);
        return;
      }
      viteServer.middlewares.stack.splice(insertionPoint, 0, {
        route: '',
        handle: (
          req: IncomingMessage & { _skip_transform?: boolean },
          _res: ServerResponse,
          next: (err?: any) => void
        ) => {
          // remove /__skip_vite/ from the URL
          if (req.url && req.url.includes('/__skip_vite/')) {
            const newUrl = req.url.replace('/__skip_vite/', '/');
            req.url = newUrl;
          }
          next();
        },
      });
    });
  },
})


Update ProximaGrpcSearchClient.java

fix bug, if WriteRequest.Row OperationType is WriteRequest.OperationType.DELETE, allow IndexValues is null.

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


Cannot add more classes to the  and  elements in the Pager

I want to add some CSS classes to the <ul> and <li> elements created by the pagination() function, but that seems to break the pager.
Here's how I initialize it.
var pagerContainer = $('div.pager-container');
pagerContainer.addClass('item-list');

pagerContainer.pagination({
  items: 20
  itemsOnPage: 2
  displayedPages: 8,
  prevText: '<',
  nextText: '>',
  currentPage: 1,
  onPageClick: function(pageNumber) {
    console.log("Selected page: " + pageNumber);
  },
  onInit: function() {
    pagerContainer.find('ul').addClass('pager');
  }
});

If I have the onInit() function like this, then nothing really happens. The pager class is not added to the <ul> element.
Instead, if I remove onInit() and add the class afterwards, then the <ul> element will have the pager class, but the <ul> itself will be deleted from the DOM when I click any link in the pager.
var pagerContainer = $('div.pager-container');
pagerContainer.addClass('item-list');

pagerContainer.pagination({
  items: 20
  itemsOnPage: 2
  displayedPages: 8,
  prevText: '<',
  nextText: '>',
  currentPage: 1,
  onPageClick: function(pageNumber) {
    console.log("Selected page: " + pageNumber);
  },
});

pagerContainer.find('ul').addClass('pager');

How do I add some simple classes to the <ul> and <li> without breaking the pager?

The issue was caused by the framework I'm using, which gave a special meaning to the pager class in the specific place I was using it. The pager was disappearing due to an AJAX reload of the entire content area.
This issue wasn't caused by simplePagination.js, closing it.


How to add my own image targets?

Hi , Thanks for your amazing Code!!
I was wondering how can i add my own image targets? i tested new image targets and add it to my own database in vuforia .. i add my image target (.dat, .xml) to image targets folder. but it says there's an error in loading it. so i think it's more than just adding it to the project.
Thanks in advance!!

@iMishaDev what was your solution?


No-ISSUE: cluster install timeout rename and doc updates for timeout

Rename the timeout config key for cluster install from clusterProvisioningTimeout to clusterInstallationTimeout to avoid confusion (since cluster provisioning refers to the process from hw provisioning to cluster configuration).
Add a brief description for timeout.

/lgtm
/approve


Create Changelog entries for 0.18.2

Related to issue ( https://github.com/dask/dask/issues/3789 ).

[ ] Tests added / passed
[ ] Passes flake8 dask

Just realized the date needs to be updated:
 0.18.2 / 2018-MM-DD
-------------------

Would you like to do that @jakirkham or should I?

Oops, sorry about that. I'll send a PR to fix it. Thanks for raising.

PR ( https://github.com/dask/dask/pull/3806 ) should fix that issue. Thanks Tom.


Should be able to import 'Web3Provider' type.

My Problem:
I want to pass the returned value of useProvider() hook as a parameter to a typescript function. But I cannot import its corresponding type (Web3Provider) from @web3-wallet/react.
Desired solution:
A simple type export would suffice. All types returned from currentWallet hooks shoud be exported, in general. It would be very helpful, and it is very simple to implement.
Note:
I tried
import type { Wallet } from '@web3-wallet/react'; type Web3Provider = ReturnType<Wallet['useProvider']>
but then I get Property 'provider' does not exist on type 'BaseProvider'. typescript warning, while provider property is there

hey @dipapazacharias, thanks for your feedbacks.

The Web3Provider is retrieve from the wallet asynchronously. The useProvider hook returns Web3Provider | undefined not Web3Provider. You function should probably also take Web3Provider | undefined as it's input not just Web3Provider.
Since you can use useProvider in any other hook, you may not need to pass Web3Provider as an parameter to your hooks. Instead, you can use useProvider directly in your hooks.
The Web3Provider and BaseProvider are both imported directly from the @ethersproject/providers package.


Schema in a file

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

Tests pass?
✔

Added console command cycle/schema/php [file] that can render ORM Schema as PHP code and save to file
Added [ru] documentation about Schema

TODO: translate docs into English

Thanks!


[Rendering] [Android] Adaptive Card in Task Module does not expand to fill available width

Copied bug from: https://github.com/microsoft/AdaptiveCards/issues/7039
Details from original post:
Target Platforms
Android
SDK Version
2.7.2
Application Name
Microsoft Teams
Problem Description
When rendering an adaptive card in a task module with a column width set to "stretch" the column does not stretch to fill the container. The same card renders fine on web, desktop, and iOS versions of Teams.
Screenshots

Card JSON
{
	"type": "AdaptiveCard",
	"body": [
        {
            "type": "ColumnSet",
            "columns": [
                {
                    "type": "Column",
                    "items": [
                        {
                            "type": "Image",
                            "style": "default",
                            "url": "https://pbs.twimg.com/profile_images/3647943215/d7f12830b3c17a5a9e4afcc370e3a37e_400x400.jpeg",
                            "size": "Small"
                        }
                    ],
                    "width": "auto"
                },
                {
                    "type": "Column",
                    "width": "stretch",
                    "verticalContentAlignment": "center",
                    "items": [
                        {
                            "type": "TextBlock",
                            "weight": "Bolder",
                            "text": "This column should stretch to fill the available space."
                        }
                    ]
                }
            ]
        }
	],
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "msteams": {
        "width": "Full"
    },
    "version": "1.4"
}

Sample Code Language
No response
Sample Code
No response---
Document Details
⚠ Do not edit this section.It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3fb4394d-25b1-8752-3996-fe3a2934732d
Version Independent ID: 6d391381-89d0-117c-27cc-00043bd26a36
Content: Cards reference - Teams
Content Source: msteams-platform/task-modules-and-cards/cards/cards-reference.md
Product: msteams
GitHub Login: @surbhigupta12
Microsoft Alias: surbhigupta12

@jrburek - We are looking into this I will get back to you soon.

@jrburek -We are unable to repro the issue. with image and text.It's working fine for us. Could you just check it once or share the repro steps so we can tried our end?

The issue is an adaptive card in a task module, so yes normal adaptive card works just fine.

Correct, I don't see this issue with adaptive cards posted as messages, only when they are used in the full screen task module.

@sayali-MSFT It seems that adaptive cards in task modules on Android need a leading TextBlock to go full width
ie this card works fine in a task module and the Input.Text is full width:
{
        "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
        "type": "AdaptiveCard",
        "version": "1.0",
        "body": [
              {
                "type": "TextBlock",
                "text": "Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum",
                "id": "text",
                "wrap": true
              },
              {
                "type": "Input.Text",
                "id": "inputText",
                "placeholder": "Some placeholder",
                "maxLength": 2000,
                "isMultiline": true,
                "isVisible": true
              },
              {
                "type": "ActionSet",
                "id": "actionSet",
                "actions": [
                  {
                    "type": "Action.ToggleVisibility",
                    "title": "Press me",
                    "targetElements": [ "text", "inputText" ]
                  }
                ]
              }
]}

But this card is too small and it is difficult to enter text:
{
        "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
        "type": "AdaptiveCard",
        "version": "1.0",
        "body": [
              {
                "type": "Input.Text",
                "id": "inputText",
                "placeholder": "Some placeholder",
                "maxLength": 2000,
                "isMultiline": true,
                "isVisible": true
              },
              {
                "type": "ActionSet",
                "id": "actionSet",
                "actions": [
                  {
                    "type": "Action.ToggleVisibility",
                    "title": "Press me",
                    "targetElements": [ "inputText" ]
                  }
                ]
              }
]}

@jrburek,@matthiasdilger- We are unable to repro the issue. We are tried with your given Adaptive json.
Android Teams Version:-1416/1.0.0
Android Version:-8.1.0

@sayali-MSFT The issue occurs for me on Android 12 (physical device) with Teams Android version 1416/<IP_ADDRESS>2223102/0201
I tried enabling/disabling the developer preview setting but it did no make a difference

I'm seeing similar behavior. The ColumnSet does seem to stretch to fill its container but its container doesn't appear to start full screen. If another element is added that forces a larger width (e.g. a TextBlock with enough text in it) then the ColumnSet stretches to accommodate. If no other element is present, or the additional elements are too small themselves, then the rendering is incorrect.
Is there some additional property on the Attachment or on the TaskModuleInfo that needs to be set to get the desired behavior? Below is the full response I send:
{     "task": {         "value": {             "title": "Android Test",             "card": {                 "contentType": "application/vnd.microsoft.card.adaptive",                 "content": {                     "type": "AdaptiveCard",                     "version": "1.4",                     "height": "auto",                     "body": [                         {                             "type": "Container",                             "items": [                                 {                                     "type": "ColumnSet",                                     "columns": [                                         {                                             "type": "Column",                                             "width": "auto",                                             "items": [                                                 {                                                     "type": "Image",                                                     "size": "small",                                                     "url": "https://pbs.twimg.com/profile_images/3647943215/d7f12830b3c17a5a9e4afcc370e3a37e_400x400.jpeg",                                                     "height": "auto"                                                 }                                             ],                                             "height": "auto"                                         },                                         {                                             "type": "Column",                                             "width": "stretch",                                             "items": [                                                 {                                                     "type": "TextBlock",                                                     "weight": "bolder",                                                     "text": "This column should stretch to fill the available space.",                                                     "height": "auto"                                                 }                                             ],                                             "verticalContentAlignment": "center",                                             "height": "auto"                                         }                                     ],                                     "height": "auto"                                 }                             ],                             "height": "auto"                         }                     ],                     "actions": [],                     "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",                     "msteams": {                         "width": "Full"                     }                 }             }         },         "type": "continue"     } }

@matthiasdilger,@jrburek -we are able to repro the issue with android version 11.We have raised bug for the same and concerned team is looking into it. We will inform you once we get any update.

@sayali-MSFT This issue has been fixed for me in the lastest Teams Android release. Thanks!


Are there different types for 'flame.type'?

Is it or could it be possible to add bookmarks as well with docker labels? like 'flame.type=bookmark' ?

Checking https://github.com/pawelmalak/flame/blob/0ec77c33bff1fea7a2b62e269a59f1e3a12516dd/controllers/apps/docker/useDocker.js#L89 type only needs to be defined and the value doesn't matter.

So.....no?

That's a no, correct.

Can we add bookmark at least? so flame.type=bookmark creates an entry in the bookmark table instead?


Dashboard URL redirecting to 0auth2 page

When I try opening up https://myvpsip:8080 as set in config.js
  DASHBOARD: {
    enabled: false, // enable or disable dashboard
    baseURL: "http://myvpsip:8080", // base url
    failureURL: "http://myvpsip:8080", // failure redirect url
    port: "8080", // port to run the bot on
  },

I go to authorisation page on 0auth2 and I added my bot to the server I wanted.
This is my redirection url: https://prnt.sc/RbcwUO7ci9jF
After that, I head over to https://myvpsip:8080 to login to dashboard but instead it keeps redirecting me to the 0auth2 page.

NodeJS version: 14x latest
Bot version: latest

I found someone had same problem but no solution for that issue.
https://github.com/saiteja-madha/discord-js-bot/issues/43

Seems like there was an error which is causing you to redirect back to login page since failureURL in config.js is same as baseURL. I have added loggers which can help find the exact cause
Check commit: 9b213a68c80a7b568e3425db325f1e23dfdb3473

@saiteja-madha :
One of the Errors, I've recieved from this the updated discord.js file is:
user_id[NUMBER_TYPE_COERCE]: Value "null" is not snowflake.
So It Looks like the the userID is returning null on the Authorization Process

Follow the steps in the docs and it should work. Alternatively, feel free to join our Discord server.


UWP games crashing

Godot version
3.5.2 Stable
System information
Windows 10 - Godot v3.5.2 Stable
Issue description
I tried exporting a simple game to UWP, just for testing purposes, but every time I try to run the game it shows the splash screen for a second, then crashes and closes. Same thing happens on my Xbox, when running it in development mode.
(Godot 3.5.2 stable)
Steps to reproduce
just export the game to UWP and run it.
video bellow:
https://github.com/godotengine/godot/assets/101520426/4ce9de30-0186-4dc6-886d-871b9b956692
Minimal reproduction project
N/A

The UWP port is known to be broken: https://github.com/godotengine/godot/issues/30558

Hi! It should work with a few workarounds. Try to follow these steps, they might help you:
https://www.rawrlab.com/blog/2023/07/24/how-to-play-your-godot-3-x-game-on-your-xbox/

Hi! It should work with a few workarounds. Try to follow these steps, they might help you: https://www.rawrlab.com/blog/2023/07/24/how-to-play-your-godot-3-x-game-on-your-xbox/

Thank you for your help. I tried this method before publishing the problem, but unfortunately the same thing happens.

Hi! It should work with a few workarounds. Try to follow these steps, they might help you: https://www.rawrlab.com/blog/2023/07/24/how-to-play-your-godot-3-x-game-on-your-xbox/

Thank you for your help. I tried this method before publishing the problem, but unfortunately the same thing happens.

I'd like to find out why is not working for you.
Ping me at Discord (@panreyes) and we'll find out why.


234 Modify the title of auto created PR [skip ci]

Fixes #234  .
Description
This PR modifies the pull requests title of auto created PR that used to update model_info.json.
Status
Ready
Please ensure all the checkboxes:

[x] Codeformat tests passed locally by running ./runtests.sh --codeformat.
[ ] In-line docstrings updated.
[ ] Update version and changelog in metadata.json if changing an existing bundle.
[ ] Please ensure the naming rules in config files meet our requirements (please refer to: CONTRIBUTING.md).
[ ] Ensure versions of packages such as monai, pytorch and numpy are correct in metadata.json.
[ ] Descriptions should be consistent with the content, such as eval_metrics of the provided weights and TorchScript modules.
[ ] Files larger than 25MB are excluded and replaced by providing download links in large_file.yml.
[ ] Avoid using path that contains personal information within config files (such as use /home/your_name/ for "bundle_root").

/build

/build

/build

/build


Add task page for troubleshooting CNI plugin-related errors

Troubleshooting CNI plugin-related errors.
Related to closed k/k issue https://github.com/kubernetes/kubernetes/issues/109686
Related to obsolete issue #33240

/assign @mikebrow

@sftim

/assign @sftim @nate-double-u

/retitle Add task page for roubleshooting CNI plugin-related errors

roubleshooting? There's too much conflict in the world already.
/retitle Add task page for troubleshooting CNI plugin-related errors

/assign @squeed

Thank you very much everyone! This was a great effort :)
/lgtm

Excellent work @rolfedh, especially considering the time pressure you were under. Thanks for coming through on this!

Thanks @chrisnegus! A huge thanks to @mikebrow and everyone who helped move this forward, @divya-mohan0209 @sftim @nate-double-u @bobfuru and others!


Error after upgrading to Nuxt 3.8.2: [ERROR] No matching export in<EMAIL_ADDRESS>for import "toPath"

Environment
Working directory: /home/stefano/Sviluppo/Personali/nuxt-storyblok-starter                                              12:05:18
Nuxt project info:                                                                                12:05:18

------------------------------
- Operating System: Linux
- Node Version:     v18.18.2
- Nuxt Version:     3.8.2
- CLI Version:      3.10.0
- Nitro Version:    2.8.0
- Package Manager<EMAIL_ADDRESS>- Builder:          -
- User Config:      css, modules, extends, runtimeConfig, image, storyblok, tailwindcss, veeValidate, gtm, app, build
- Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>- Build Modules:    -
------------------------------

Reproduction

Update from previous version to Nuxt 3.8.2 by using npx nuxi upgrade --force
Run pnpm dev, the following error occurs
pnpm generate then pnpm preview does not seem to report any obvious error

Describe the bug
Error output:
✘ [ERROR] No matching export in<EMAIL_ADDRESS>for import "toPath"

    node_modules/.pnpm/globby@14.0.0/node_modules/globby/ignore.js:8:8:
      8 │ import {toPath} from 'unicorn-magic';
        ╵         ~~~~~~

✘ [ERROR] No matching export in<EMAIL_ADDRESS>for import "toPath"

    node_modules/.pnpm/globby@14.0.0/node_modules/globby/index.js:7:8:
      7 │ import {toPath} from 'unicorn-magic';
        ╵         ~~~~~~

 ERROR  [unhandledRejection] Build failed with 2 errors:                                                                11:53:08
node_modules/.pnpm/globby@14.0.0/node_modules/globby/ignore.js:8:8: ERROR: No matching export in<EMAIL_ADDRESS>for import "toPath"
node_modules/.pnpm/globby@14.0.0/node_modules/globby/index.js:7:8: ERROR: No matching export in<EMAIL_ADDRESS>for import "toPath"

  node_modules/.pnpm/globby@14.0.0/node_modules/globby/ignore.js:8:8: ERROR: No matching export in<EMAIL_ADDRESS>for import "toPath"
  node_modules/.pnpm/globby@14.0.0/node_modules/globby/index.js:7:8: ERROR: No matching export in<EMAIL_ADDRESS>for import "toPath"
  at failureErrorWithLog (node_modules/.pnpm/esbuild@0.18.20/node_modules/esbuild/lib/main.js:1649:15)
  at node_modules/.pnpm/esbuild@0.18.20/node_modules/esbuild/lib/main.js:1058:25
  at node_modules/.pnpm/esbuild@0.18.20/node_modules/esbuild/lib/main.js:1525:9
  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Additional context
The error seems to originate in<EMAIL_ADDRESS>in my lockfile this version is used only by:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
<EMAIL_ADDRESS>is present in my lockfile only as a dependency of<EMAIL_ADDRESS>Logs
No response

We are having the same issue. I've been able to boil it down to the @storyblok/nuxt package.
And a reproduction:
https://stackblitz.com/~/github.com/jordypereira/nuxt-bug-globby-repro

i have the same issue with storyblok and nuxt

Ok, updating only with npx nuxi upgrade (without the --force flag) and not recreating the lockfile does not fire the issue.
I tried to install a clean copy of Nuxt, and the problem still does not happen.
I suspect that it may be related to some module that maybe has not yet been updated to the 3.8.2 stack, so I think that I will wait some days to see if newer versions will solve it.
As things stands right now, it does not seem to be a problem strictly related to Nuxt, but if it is not a problem I would leave this open for now for reference, and try to take care of it in a few days.

I think that the error occurs because of the nitro version 2.8.0 and I don’t quite understand how to downgrade to version 2.7, it seems that nuxt 3.4.0 - 3.8.2 now always comes with 2.8.0. But for our project i need at least nuxt 3.7.0 version 😔
i use storyblok and nuxt for production project and it very sad that i cant handle error with downgrade or any other stuff(

I found a quick solution
We need to downgrade nitro to 2.7 version... to do it - add following code into package.json
"overrides": {
"nitropack": "2.7.0"
}

'globby' was updated to v14.0.0 a couple weeks back, which introduced an import for 'toPath' from the author's 'unicorn-magic' package, which has one release and no export named toPath. Seems like an error by the author maybe?
Globby v13.2.2 does not have that import, so overriding or using resolutions to set globby to v13.2.2 for the time being worked for me:
In package.json:
"resolutions": {
    "globby": "13.2.2"
}

toPath is only exported in node environments<EMAIL_ADDRESS>The issue here is that the storyblok module was pulling the module/build-time code into the runtime context by adding it to vite.optimizeDeps.include.
I've raised https://github.com/storyblok/storyblok-nuxt/pull/662 which fixes the issue and should also speed up your dev server environment.
If anyone is experiencing this and isn't using @storyblok/nuxt, let me know. 🙏

@danielroe thanks for your PR to fix the module!

@danielroe Thanks for your help, much to learn!

Not at all! Your investigation was very helpful ❤

toPath is only exported in node environments<EMAIL_ADDRESS>The issue here is that the storyblok module was pulling the module/build-time code into the runtime context by adding it to vite.optimizeDeps.include.
I've raised storyblok/storyblok-nuxt#662 which fixes the issue and should also speed up your dev server environment.
If anyone is experiencing this and isn't using @storyblok/nuxt, let me know. 🙏

unfortunately, I am not using  @storyblok/nuxt, but have this problem in the build on the server. My package-lock.json does not have storyblok also. this also does not help(((: "overrides": { "nitropack": "2.7.0" }

https://github.com/sindresorhus/globby/issues/260

I have this issue when building with Nitro's cloudflare-pages preset. With node-server it's fine.
Here are my dependencies
"devDependencies": {
"@nuxt/devtools": "latest",
"@nuxtjs/tailwindcss": "^6.10.1",
"@tailwindcss/typography": "^0.5.10",
"nuxt": "^3.8.2",
"nuxt-security": "^1.0.0-rc.4",
"vue": "^3.3.8",
"vue-router": "^4.2.5"
},
"dependencies": {
"@nuxt/content": "^2.9.0",
"@radix-icons/vue": "^1.0.0",
"@vueuse/core": "^10.6.1",
"class-variance-authority": "^0.7.0",
"clsx": "^2.0.0",
"tailwind-merge": "^2.0.0",
"tailwindcss-animate": "^1.0.7"
},

I am using Nuxt 3.8.2 with nitro 2.8.0
Using also Prismic as headless.
The website is hosted on Vercel and works fine
However, when deploying to CloudFlare I get this issue
16:58:34.147 | [success] [nitro] Generated public dist
-- | --
16:58:34.185 | [info] [nitro] Building Nitro Server (preset: `cloudflare-pages`)
16:58:50.786 | [error] [nitro] RollupError: "toPath" is not exported by "node_modules/unicorn-magic/default.js", imported by "node_modules/globby/ignore.js".
16:58:50.787 |
16:58:50.787 |
16:58:50.787 | 6: import gitIgnore from 'ignore';
16:58:50.788 | 7: import slash from 'slash';
16:58:50.788 | 8: import {toPath} from 'unicorn-magic';
16:58:50.788 | ^
16:58:50.788 | 9: import {isNegativePattern} from './utilities.js';
16:58:50.789 | [error] "toPath" is not exported by "node_modules/unicorn-magic/default.js", imported by "node_modules/globby/ignore.js".
16:58:50.789 | at error (node_modules/nitropack/node_modules/rollup/dist/es/shared/parseAst.js:337:30)
16:58:50.789 | at Module.error (node_modules/nitropack/node_modules/rollup/dist/es/shared/node-entry.js:12728:16)
16:58:50.790 | at Module.traceVariable (node_modules/nitropack/node_modules/rollup/dist/es/shared/node-entry.js:13169:29)
16:58:50.790 | at ModuleScope.findVariable (node_modules/nitropack/node_modules/rollup/dist/es/shared/node-entry.js:11582:39)
16:58:50.790 | at ReturnValueScope.findVariable (node_modules/nitropack/node_modules/rollup/dist/es/shared/node-entry.js:5897:38)
16:58:50.790 | at FunctionBodyScope.findVariable (node_modules/nitropack/node_modules/rollup/dist/es/shared/node-entry.js:5897:38)
16:58:50.790 | at ReturnValueScope.findVariable (node_modules/nitropack/node_modules/rollup/dist/es/shared/node-entry.js:5897:38)
16:58:50.790 | at FunctionBodyScope.findVariable (node_modules/nitropack/node_modules/rollup/dist/es/shared/node-entry.js:5897:38)
16:58:50.791 | at Identifier.bind (node_modules/nitropack/node_modules/rollup/dist/es/shared/node-entry.js:7184:40)
16:58:50.791 | at CallExpression.bind (node_modules/nitropack/node_modules/rollup/dist/es/shared/node-entry.js:4625:23)
16:58:50.791 |
16:58:50.792 | [error] "toPath" is not exported by "node_modules/unicorn-magic/default.js", imported by "node_modules/globby/ignore.js".
16:58:50.899 | Failed: Error while executing user command. Exited with error code: 1
16:58:50.909 | Failed: build command exited with code: 1
16:58:51.901 | Failed: error occurred while running build command

If you can provide a reproduction, we can have a look 🙏

Hi @danielroe
Just to install nuxt clear project then try to build project for CF
NITRO_PRESET=cloudflare-pages nuxt build

Problem is globby updated to 14.0.0 and toPath not exported for non-node project
modules nuxt, nuxt/kit etc.. using globby 14.0.0 when i try downgrade version it can be fixed for nuxt but nuxt/kit install globby 14 =(
Refs:
https://github.com/sindresorhus/unicorn-magic/pull/1
https://github.com/sindresorhus/globby/issues/260

@danielroe Hi sorry so much:
Preview  https://stackblitz.com/edit/github-jfmbya?file=package.json
in terminal try please
NITRO_PRESET=cloudflare-pages nuxt build

I'm sorry!  I have find hot to resolve problem "nuxt-simple-sitemap": "^3.4.1", must be updated to "4.1.6"
so issue now is closed but will be better to have a more clear stacktrace to understand problem without remove module by module this stack said problem in globby with using in nuxt.

Thanks @boxexchanger for all your troubleshooting. For me, it was caused by nuxt-security and I had to downgrade from 1.0.0-rc.4 to 0.14.4

@imm That is caused by the fact that you have several different versions of globby installed but you haven't declared a dependency on globby in your package.json.

I'm getthing this error after ugrading nuxt 3.8.1 to nuxt 3.9.2
is there something i need to include in vite.optimizeDeps or is there a way to debug if i have a package that needs another version of a dependency?
X [ERROR] No matching export in "../../node_modules/unicorn-magic/default.js" for import "toPath"
    ../../node_modules/globby/ignore.js:8:8:
      8 │ import {toPath} from 'unicorn-magic';
        ╵         ~~~~~~
X [ERROR] No matching export in "../../node_modules/unicorn-magic/default.js" for import "toPath"
    ../../node_modules/globby/index.js:7:8:
      7 │ import {toPath} from 'unicorn-magic';
        ╵         ~~~~~~
 ERROR  [unhandledRejection] Build failed with 2 errors:
../../node_modules/globby/ignore.js:8:8: ERROR: No matching export in "../../node_modules/unicorn-magic/default.js" for import "toPath"
../../node_modules/globby/index.js:7:8: ERROR: No matching export in "../../node_modules/unicorn-magic/default.js" for import "toPath"
  ../../node_modules/globby/ignore.js:8:8: ERROR: No matching export in "../../node_modules/unicorn-magic/default.js" for import "toPath"
  ../../node_modules/globby/index.js:7:8: ERROR: No matching export in "../../node_modules/unicorn-magic/default.js" for import "toPath"
  at failureErrorWithLog (C:\LAIT\scanpipe-frontend-new\src\node_modules\esbuild\lib\main.js:1651:15)
  at C:\LAIT\scanpipe-frontend-new\src\node_modules\esbuild\lib\main.js:1059:25
  at C:\LAIT\scanpipe-frontend-new\src\node_modules\esbuild\lib\main.js:1527:9
  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

fixed this by adding "globby" to build.transpile.

I am also facing the same issue, super unclear to me where it comes from. Trying to figure out whats wrong here. Super complicated.

I encountered the same issue and migrated my module to Nuxt Layers. It wasn't that complicated and fits in my opinion much better into the embedding application. Perhaps this could be a fallback for some here.

Thank you for the quick answers, guys! In my case it became complicated as I (due to other reasons) did not update all my packages for a while and they are of course dependent to each other.
If someone has a similar issue

Make sure all imports are still relevant - remove packages that can be removed
Always commit before upgrading your packages, so you can revert your changes

In my case, the issue (pretty certain) came from '@vite-pwa/nuxt', but it was very hard to pinpoint and still im only 90% sure, not 100%, but after removing this package, the error disappeared.
I upgraded from nuxt3.4 and another error I got was due to the autoimports changing with pinia, instead of:
 modules: [
    ['@pinia/nuxt',
      { autoImports: ['defineStore', 'mapStores'] }
]

defineStore will be autoimported anyways so just register the autoimports as follows:
  imports: {
    presets: [
      {
        from: "pinia",
        imports: ["mapStores"]
      }
    ],
  },

Maybe it's relevant for someone, it was hard to find online by googling so, just for keywords sake: [mapStores issue nuxt pinia mapStores not defined]


Update the placeholder docstrings for meaningful ones

DESCRIPTION
Several parts of the code have dummy docstrings added as workaround to pass the static code checks. They must be replaced into meaningful code documentation, in preparation for a larger issue that will create the project documentation and AP reference.
TARGET

all *.py files

ACCEPTANCE CRITERIA

Code documentation is written using Google style docstrings.
No associated errors found during static code checks, and no placeholders are in place.

Commit was partial


Troubleshooting 3D model loading issues on iOS devices using Lock Mode

Loading 3D models from a URL on iOS devices has been found to fail due to Lockdown Mode.
This commit includes instructions to disable Lockdown Mode and restore app functionality.
Added instructions so users can temporarily disable this security feature.
Common issues found: 3D object is not displayed and there is no clear error output.

done,


Move migration/create to gii/migration

What steps will reproduce the problem?
I wanted to create a migration file from a template without an actual DB connection.
What is the expected result?
It should be possible to do so.
What do you get instead?
Access denied error (in my case) because the DB hasn't been set up yet.
While looking at the code I saw that the migration command ensures a DB-connection beforeAction, which is basically fine.
But this lead me to the question if it wouldn't make more sense to have a command like:
yii gii/migration

Where the code-generator would create the migration files.
Additional info

Q
A

Yii version
<IP_ADDRESS>

PHP version
7.2

Operating system
Linux

If such a change is made, surely only in 2.1

While we could use Gii for it, there are more operations with migrations: applying, checking history, reverting, moving current migration pointer. I think it's logically correct to keep these together with creating migration.

Just noticed that `generateMigrationSourceCode` needs the database connection when creating junction tables, missed that functionality, so it's fine.


Fallback to GLX_MESA_swap_control if GLX_EXT_swap_control isn't supported

Tested with Radeon RX 570 Series (POLARIS10, DRM 3.35.0, 5.4.33-3-lts, LLVM 10.0.0)

Thanks for the PR!
I should say that this construct is very hard to read. It took me good five minutes to understand how it works. I think that the following should work better:
#if GLX_EXT_swap_control
        if (glXSwapIntervalEXT != nullptr)
        {
            glXSwapIntervalEXT(display, wnd, SwapInterval);
        }
#elif GLX_MESA_swap_control
        if (glXSwapIntervalMESA != nullptr)
        {
            glXSwapIntervalMESA(SwapInterval);
        }
#endif

It does not check both extensions at run time, which I think is probably not necessary. Or is this you actual problem?  In this case I would suggest this way:
#if GLX_EXT_swap_control
        if (glXSwapIntervalEXT != nullptr)
        {
            glXSwapIntervalEXT(display, wnd, SwapInterval);
        }
#    if GLX_MESA_swap_control
        else if (glXSwapIntervalMESA != nullptr)
        {
            glXSwapIntervalMESA(SwapInterval);
        }
#    endif
#elif GLX_MESA_swap_control
        if (glXSwapIntervalMESA != nullptr)
        {
            glXSwapIntervalMESA(SwapInterval);
        }
#endif

Sometimes some code duplication may not be a bad thing

Both GLX_EXT_swap_control and GLX_MESA_swap_control are always enabled in glxew.h
The problem is runtime checking.


Muttering something about crypto ...

Added a section for SunOS/Solaris UNIX.
Added Mutt to all *nix systems (including OS X and Solaris).
Added Thunderbird to Solaris.
Inserted footnote for GPG with GPGME (it's usually optional,
depending on the software it's used with, it's definitely optional
with Mutt).
Not yet added a section for *BSD (esp. FreeBSD and OpenBSD), but
that would probably end up being largely similar to the GNU/Linux
options anyway (since GPG is dual licensed with the LGPL 2.1 and can
thus be incorporated into the BSDs safely, which is why it ships
with OS X by default too ... it's just usually a very old and
unmaintained version).

Great work, thanks!

You're welcome.


How To Avoid Reconversion Of Songs

I want to download the original file which spotify uses, I don't want the file to be reconverted which leads to Genertational loss

Well after looking through the code I found that setting the download format to vorbis/ogg will basically disable the conversion and simply copy the file avoiding reconversion. spotify converts their songs to aac(24,128,256) and vorbis(96,160,320) while the higher bitrates are for the premium users, the people using free accounts can download upto 160kbps vorbis


can not print msg with sender middleware?

my config like this :
var props= Actor.FromProducer(() => new MyActor()).WithSenderMiddleware(
next => async (c, target, envelope) =>
{
Console.WriteLine($"middleware 1 enter {c.Message.GetType()}:{c.Message}");
await next(c, target, envelope);
Console.WriteLine($"middleware 1 exit {c.Message.GetType()}:{c.Message}");
},
next => async (c, target, envelope) =>
{
Console.WriteLine($"middleware 2 enter {c.Message.GetType()}:{c.Message}");
await next(c, target, envelope);
Console.WriteLine($"middleware 2 exit {c.Message.GetType()}:{c.Message}");
});
var pid = Actor.SpawnNamed(props, "myparent");
when i use : pid.Tell("hello world!");
why not print the message?

Hello,
You've defined the sending middleware for the actor, it doesn't fire during receiving:
pid.Tell("hello world!");
The myparent actor receives a message, not sends.


Searching bootstrap.css.map freezes tag

The tag command freezes when I run it on bootstrap.css.map. I am running tag commit efa3eff1d39f23dcdfba90f013e9bac79d31421e and ag version 0.31.0 on Ubuntu 16.04. My shell is zsh 5.1.1. The problem disappears if I pipe to cat, i.e. tag foo bootstrap.css.map | cat.
Is there anything else I can do to help debug this problem?

Hmm, it seems like the root of the problem might be in vanilla ag. Try filing an issue there? Closing this issue for now because I think it's beyond my control.


I wish bigger window and bigger items

That's not an issue, only wish.
Hats, skins etc. are very small, that's why i don't see well how they look like. Increase window and everything in order to see better.

And something else. In editor i selected mouse and keyboard, In playerprefs i see 1 (that means mouse and keyboard) but in among us settings i see only mouse. So i have to select mouse and keyboard again in settings.


Onboarding to San Diego

Complete on boarding to the project to help get started with the ecosystem mapping.
Acceptance Criteria

[x] Review Augur demo guide
[x] Access to Augur database
[x] Review any existing work relevant to ecosystem mapping

We have access to the database and have looked at existing work. Are we good to close this? @hemajv 🙂


Show build status of master branch

Hey!
Thanks for making this, and for making it available.
I just noticed when I read about the project that the travis build status icon was red and failing, which came from the fact that the README links to the latest build, which might at a given time be a WIP branch with failing tests.
So, right now it is green again, but at least here is a very minor PR to make sure it always displays the master build status. Who knows, someone might loose confidence in a project based on a red build status :)
Thanks again, have a nice week!

:tada: I've been meaning to do this. Thanks, friend!


How to handle consent for early tests

When we present patients with the choice to participate in their app, should we be asking for permission to share their eligibility info with a network of safety-net providers, or with each provider individually? If a network, how should we handle the addition of new providers?

This seems like a great question for Danny. Let's make sure we bring it up in our discussion on Friday the 27th.

Update: We discussed HIPAA implications of our current non-client facing app, and it seems like the use of the app by clinics would fall under a BA agreement and general consent clauses about sharing patient info for billing and care coordination purposes. My current assumptions:

we probably don't need a consent form that is specific to our app, because we are currently covered by general consent forms used by clinics during intake.
We might need BA agreements with clinics (not sure about this)?
Given that some clinics provide behavioral health services, we may need to exclude content regarding behavioral health, because it requires more strict authorization steps. Or if we do include it, we would need to look at authorization steps for patients.

We will probably need to get the basic permission, waiver, contracts assigned for the patient, CHW, and the approved healthcare providers as well. I am not sure who should be the bearer or these contracts and such but we should outline these areas before we get too far along as they are vital for the data being collected and shared and making sure its protected, safe and controlled.

@andreasRVA Yes, we have a lawyer that specializes in HIPAA that we consulted about two weeks ago. We will talk with her again to clarify assumptions and possibly draft a privacy policy. Here's the relevant section in HIPAA that she pointed us to: https://www.law.cornell.edu/cfr/text/45/164.506

For record's sake and updating @andreasRVA, we've decided to continue production under the "umbrella consent" concept, where you will have access to all patients in the system if you are a standard user. It opens the door for more tiered user roles (#173) moving forward, and removes an unnecessary amount of friction for the users and patients that the app's sharing/consent process created.
We heard from Fairfax that they are running their app in under this umbrella process that allows for partners to be added and BAs to be updated annually (?) with newly added care providers between Inova and the county.
How do early consent forms change with this? What officially needs to be written for us to start testing?

[ ] Patient consent to the application – paper and app
[ ] Business agreement between all active partners (including the Richmond City Health Department) – paper
[ ] BA between CfA and the partnership – paper

UPDATE
We are in progress of getting BAA's signed between the city and the following partners to prepare for testing before the end of the fellowship:

[ ] Daily Planet
[ ] Access Now
[ ] Bon Secours Care-a-van
[ ] Richmond Center for High Blood Pressure
[ ] OAR
[ ] Resource Centers
[ ] Code for America

Patient consent form AND BAA have been approved on Code for America's end. They are attached here as PDFs.
RVA_PatientConsentv0.2.pdf
RVA_BAAv0.1.pdf

Sam
I think we should draft a review statement of the Patient Consent form to
be read to the patient to summarize the document. Something along the lines
of:
By signing this document you agree

That all information provided is accurate and truthful
Agree to share this information with the Richmond Community Health
Partners
And that the Richmond Community Health Partners are able to share this
information among themselves for the benefit of providing financial
screening for your access to their services
I can refuse and/or cancel this authorization to my provided information
at any time, and if I  refuse, I understand that this will have no impact
or effect on my access to the services provided by the RCH Partners.

Something along those lines should suffice. A way for the basic elements to
be outlined in a 5th grade equivalent language is important. Thoughts?
Andreas
On Mon, Oct 26, 2015 at 7:06 PM, Sam Matthews<EMAIL_ADDRESS>wrote:

Closed #1 https://github.com/codeforamerica/rva-screening/issues/1.
—
Reply to this email directly or view it on GitHub
https://github.com/codeforamerica/rva-screening/issues/1#event-446175774
.

--
Andreas D. Addison
Civic Innovator, City of Richmond
804.833.5898 c
twitter         @andreasrva
facebook     andreasrva
GovLoop     Andreas Addison
Skype         andreasRVA

I like it - does this go on to the actual document? Where do you think would work best?

I'm thinking this is part of the operational training for use in the field. Part of the on boarding process for new patients as read to them by the trained and qualified input coordinator from the RCH Partners.
Best,
Andreas D. Addison
Civic Innovator, City of Richmond
804.833.5898
Please excuse autocorrect typos as this was sent with my thumbs from my iPhone

On Oct 27, 2015, at 12:46 PM, Sam Matthews<EMAIL_ADDRESS>wrote:
I like it - does this go on to the actual document? Where do you think would work best?
—
Reply to this email directly or view it on GitHub.

I would recommend making the following changes to the BAA and MOU section:
The Richmond Community Health Partners network is initiated through a Business Associate Agreement (BAA) between the Richmond City Health District and Code for America that establishes the access and utilization of the QuickScreen application and ensures its compliance with HIPAA. The Richmond Community Health Partners are granted access to the application through the Memorandum of Understanding (MOU) drafted between the application owner ____ and each of the consenting partners. These documents assure that the data and information entered, stored and shared through the application is secure and safe and only accessible by approved, trained and qualified users.


Fix some broken links

Fix broken links discovered during macOS testing.

Do you think we should set up the redirect from the space-acres to space-acres-recommended @jim-counter?

Do you think we should set up the redirect from the space-acres to space-acres-recommended @jim-counter?

Sounds like a good idea. Can you add it to this PR?

Added

The last commit not broken link per-se, but fits into fixing broken stuff pr.


Update broken links in README.md

Updated broken links - these links look like they used to be in a repository called "ss-documentation" which is now called "doc" and the links have been updated accordingly.
Concisely (20 words or less) describe the issue
Please Link issue(s)
resolves #385
What tests have been done? Upload any model input files created for testing in a zip file, if possible.
None, updating the readme links
What tests/review still need to be done? Who can do it, and by when is it needed (ideally)?
Double check that links now work.
Has any new code been documented?
No need.
If not, please add documentation before submitting the Pull Request.

[ ] I have documented any new code added (or no new code was added)

is there an input change for users to Stock Synthesis?

[ ] Yes, there was an input change

If so, please provide an example of the new inputs needed.
[New example stock synthesis input goes here]

Check which is true. This PR requires:

[ ] no further changes to r4ss
[ ] no further changes to the manual
[ ] no further changes to SSI (the SS3 GUI)
[ ] no further changes to the stock synthesis change log (new features, bug reports)

Describe any changes in r4ss/SS3 manual/SSI that are needed (if not checked):
If changes are needed in the change log, please fill in the table here:

Action
Topics
Type

[fix, new, or revise]
[e.g., biology. Use issue label options.]
[input, output, and/or calc, or ALL]

Additional information (optional):

@Rick-Methot-NOAA could you provide the link to that because I'm not seeing that anywhere in the repository - I might just be missing it somehow.

@Rick-Methot-NOAA The README.md now goes to the SS3 Shiny helper app and the phrasing in the readme has been changed accordingly.


【Feature Request】adding“Push line/selection to another file and leaving block/section embed in current line”

This is an amazing plugin, with the core idea of Obsidian that when moving things or ideas, one should always remember to leave a link for connection. However, when using “Push line/selection to another file" the content is permanently lost in the current file unless you use the "Pull Line(s) from another file as block embeds" in the current file or go to the destination file and using the copy block embed to paste the embed link of the content you just pushed. This process is tedious and not very elegant. I wonder if you can add the function to "Push line/selection to another file and leaving block/section embed in current line"

I found this request is similar to #30


Add a controller argument to the storage checker function.

Most of the changes are just reindenting.
REVIEW NOTE: Please look at a diff that ignores whitespace changes.  It will be much smaller.

Fast-tracking platform-specific change with platform owner review.


1.9.0a1  breaks workaround for field_type_schema and nullable

release 1.9.0a1  breaks this work around completely:
.../inmanta/data/model.py", line 34, in <module>
    old_field_type_schema = pydantic.schema.field_type_schema
AttributeError: 'cython_function_or_method' object has no attribute 'field_type_schema'

Originally posted by @wouterdb in https://github.com/samuelcolvin/pydantic/issues/1270#issuecomment-997700804

I think this issue has the following root cause:

The pydantic/main.py file defines a function called schema
The pydantic/__init__.py file does the import from .main import *

As such the following import from pydantic import schema imports the function schema and not the package schema which also exists in the pydantic package.
Illustration:
(env) [arnaud@laptop]/tmp% pip install pydantic==1.8.2
...
Successfully installed pydantic-1.8.2
(env) [arnaud@laptop]/tmp% python
>>> from pydantic import schema
>>> print(schema)
<module 'pydantic.schema' from '/tmp/env/lib64/python3.6/site-packages/pydantic/schema.cpython-36m-x86_64-linux-gnu.so'>

(env) [arnaud@laptop]/tmp% pip install -U --pre pydantic
...
Successfully installed pydantic-1.9.0a1
(env) [arnaud@arnaud]/tmp% python
>>> from pydantic import schema
>>> print(schema)
<cyfunction schema at 0x7fec8df76d50>


Use RefCell to enforce aliasing rules

Currently pyo3 allows to break rust's aliasing guarantees, i.e. you can get two mutable references to the same object. This is not a big issue because you can only have those two references on the same thread, but this still needs to be fixed eventually. See this capter in wasm bindgen's guide for a good write-up on the why and how.

Another issue closely related to this is mutable Python native types where PyO3 returns references to the internal buffer, e.g.:
extern crate pyo3;
use pyo3::{prelude::*, wrap_pyfunction};

#[pyfunction]
fn sum_as_string() -> PyResult<()> {
    let gil = Python::acquire_gil();
    let py = gil.python();

    let byte_arr = pyo3::types::PyByteArray::new(py, &[1, 2, 3]);
    let byte_arr_data = byte_arr.data();
    println!("Pre mut: {:#?}", byte_arr_data);

    use pyo3::types::IntoPyDict;
    let d = [("byte_arr", byte_arr)].into_py_dict(py);
    py.run("byte_arr.clear()", None, Some(&d)).unwrap();

    println!("oh shit ...");
    println!("Post mut: {:#?}", byte_arr_data);

    Ok(())
}

/// This module is a python module implemented in Rust.
#[pymodule]
fn pyo3bug(py: Python, m: &PyModule) -> PyResult<()> {
    m.add_wrapped(wrap_pyfunction!(sum_as_string))?;

    Ok(())
}

Python 3.7.3 (default, Mar 30 2019, 03:37:43)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.4.0 -- An enhanced Interactive Python. Type '?' for help.

Post mut: [
    216,
    67,
    13,
]

I don't think this could be fixed using just a RefCell, could it? We would have to proxy the actual native type through something in our control to achieve this, which sounds like an unreasonable amount of complexity. Perhaps methods returning references into mutable Python objects should just be scrapped or replaced by visitor style APIs. Not really idiomatic, perhaps there is a better way.

Here's what rust_cpython does:
/// Gets the buffer memory as a slice.
///
/// This function succeeds if:
/// * the buffer format is compatible with `T`
/// * alignment and size of buffer elements is matching the expectations for type `T`
/// * the buffer is C-style contiguous
///
/// The returned slice uses type `Cell<T>` because it's theoretically possible for any call into the Python runtime
/// to modify the values in the slice.
pub fn as_slice<'a, T: Element>(
    &'a self,
    _py: Python<'a>,
) -> Option<&'a [ReadOnlyCell<T>]>;

/// Gets the buffer memory as a slice.
///
/// This function succeeds if:
/// * the buffer is not read-only
/// * the buffer format is compatible with `T`
/// * alignment and size of buffer elements is matching the expectations for type `T`
/// * the buffer is C-style contiguous
///
/// The returned slice uses type `Cell<T>` because it's theoretically possible for any call into the Python runtime
/// to modify the values in the slice.
pub fn as_mut_slice<'a, T: Element>(
    &'a self,
    _py: Python<'a>,
) -> Option<&'a [cell::Cell<T>]>

Given that all python objects happen to have a reference counter in them already, this is fairly easy to fix in the glue that exists between Python and Rust. Any attempt to downcast PyObject into &mut T should fail with some PyO3-specific exception if the reference count is not equal to 1.

Possibly.  I suspect that it would be impractical to use in practice.  A refcount of 1 is nigh unattainable in any sort of realistic scenario, especially in the context of calling Rust from Python.  Even something like:
def f0(x): return f1(x)
def f1(x): return f2(x)
def f2(x): return x

needs to produces additional references to x at each call level.
That said, I'm not certain what happens precisely when the interpreter calls methods and functions defined in extension modules.  I know that the self object given to these methods is a borrowed reference, as are objects returned by PyArg_ParseTuple; so it is theoretically possible that the compiler does not increment refcounts at these callsites.  (for methods, you'd also have to be careful to make sure a "bound method" object isn't created; e.g. f = x.method; f())

If we replaced the Python<'p> GIL marker with a reference &'p [mut] Python to a non-Cloneable type, we could safely allow operations like
impl PyByteArray {
    fn data<'p>(&'p self, py: &'p Python) -> &'p [u8];
    fn data<'p>(&'p self, py: &'p mut Python) -> &mut 'p [u8];
}

In other words,

Holding a shared reference to the GIL marker means that the state of the Python world is frozen and you can safely have shared references to data in the Python world.
Holding a unique reference to the GIL marker means that you can safely borrow data mutably from the Python world, but only once at a time.


Error installing from wheel

I'm using a Linux system with python 3.7 on GCP deep learning image for GPUs, here's the system info:
jkterry0@instance-3:~$ python3
Python 3.7.12 | packaged by conda-forge | (default, Oct 26 2021, 06:08:53)
[GCC 9.4.0] on linux

jkterry0@instance-3:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
jkterry0@instance-3:~$ pip -V
pip 22.0.3 from /opt/conda/lib/python3.7/site-packages/pip (python 3.7)
Codename:       buster

jkterry0@instance-3:~$ pip -V
pip 22.0.3 from /opt/conda/lib/python3.7/site-packages/pip (python 3.7)

However, when I try to install the corresponding wheel image this happens and I have absolutely no idea why:
jkterry0@instance-3:~$ pip install [https://github.com/deepmind/lab2d/releases/download/release_c](https://github.com/deepmind/lab2d/releases/download/release_candidate_2021-07-13/dmlab2d-1.0-cp37-cp37m-manylinux_2_31_x86_64.whl)
[andidate_2021-07-13/dmlab2d-1.0-cp37-cp37m-manylinux_2_31_x86_64.whl](https://github.com/deepmind/lab2d/releases/download/release_candidate_2021-07-13/dmlab2d-1.0-cp37-cp37m-manylinux_2_31_x86_64.whl)
ERROR: dmlab2d-1.0-cp37-cp37m-manylinux_2_31_x86_64.whl is not a supported wheel on this platfor
m.

What is your glibc version, out of curiosity?
You could also try and use the unversioned wheel that doesn't enforce any platform constraints.

glibc:
jkterry0@instance-3:~$ ldd --version
ldd (Debian GLIBC 2.28-10) 2.28
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.

Forgive my ignorance, but what would the full command to build and install the unversioned wheel from that be?

That might be the problem? The wheel seems to require glibc 2.31 (Not sure why! That's what Python says.)
The unversioned wheel is :dmlab2d_wheel_local, instead of :dmlab2d_wheel.
Oh wait, you're not building anything locally, you're just downloading this from our release page? Then yes, I suppose our wheels require glibc >= 2.31, sorry about that. We just use the current github runner to build them,

I suppose we should add some documentation on how to build the wheels, @charlesbeattie.
bazel build -c opt //dmlab2d:dmlab2d_wheel
bazel build -c opt //dmlab2d:dmlab2d_wheel_local

You use pip, and the resulting wheel file name should be printed ads the result of running bazel.


Code for data preprocessing

Thanks for the code again.
Would you also provide the code for data preprocessing? For example, how did you reformat the original H3.6m dataset and generate the .h5 files? How did you finetune the stack-hourglass model on H3.6m data?
That would be a great reference for manipulating other datasets. Thank you very much!

Hi @bearpaw!,
These are good questions. My goal is to make all the pipeline as transparent as possible, but I also want to keep the code simple so we've left some things out of this repository.

how did you reformat the original H3.6m dataset and generate the .h5 files?

The 3d data that we provide has no pre-processing other than the change from .cdt to .h5. You just have to download the 3d data in D3 Positions format, as available on the human 3.6m website.
Perhaps you are having trouble reading .cdt files? Matlab has a function to read .cdf files. Reading them in python is a little bit more of a pain... There's a package (spacepy) that's supposed to provide a cdf reader, but if I remember correctly if you pip install it, it will not work, and you will still have to download the C library that does the actual reading and link it to your LD_LIBRARY and INCLUDE paths.

How did you finetune the stack-hourglass model on H3.6m data?

That is a bit more tricky. The SH train code expects data to come nicely in image-2d pairs, with the mapping available via hdf5 files that you have to generate yourself (they provide some python scripts to do it, but there's lots of manual modifying going into it). That was actually mostly done by @rayat137, and I think it took him 2 or 3 days to get it completely right, but I don't think the scripts are close to being in a releasable state :S (@rayat137 can confirm).
It would be easy for me to either

Share the h5 files that we used for fine-tuning SH or
Share the fine-tuned SH detections.

Would any of those help?

Hi @una-dinosauria , thanks a lot for your comprehensive answer!
For the SH finetune part, it would be great if @rayat137 could release the code (then others are able to improve the code by creating pull request).
I think both 1. Share the h5 files that we used for fine-tuning SH; and 2. Share the fine-tuned SH detections. are very useful. The former one can help newbies like me to get familiar with the whole process, and allows us to use other network structures. The later one can help us reproduce the results quickly. Personally, I prefer the h5 files that you used for finetuning the SH model.
P.S. To make the repo clean, you may provide a link to Google Drive or Dropbox.

Here you can find the fine-tuned SH detections we used. You can replace them by the ones we provide by default and get slightly better results: https://slack-files.com/T3LNARA8Z-F5YB4D99P-814b9613cb

Here is the link for the h5 files that we used to fine-tune Stacked Hourglass: https://drive.google.com/file/d/0BxWzojlLp259MS1obTA2QkNheDg/view?usp=sharing. I think this should work almost out of the box for fine-tuning, as it contains all the 2d data-to-image mappings in SH format.
(If you get the code from https://github.com/anewell/pose-hg-train, this goes under data/).
You'll obviously also need the images too, which you should generate yourself from the videos using ffmpeg.
Here's a gist used to generate these h5 files: like I said, not close to being releasable; only hoping it will help understand the process: https://gist.github.com/una-dinosauria/382e488d557af2b07e89bdeddeab1379

@una-dinosauria These are very helpful resources! Thank you very much!


Feature/126 - AEM 6.4 Responsive Grid support

Here's an approach for resolving the responsive grid's grid_base.less file. This approach entails:

Updated code mainline to use the 6.4 responsive grid path (as this the correct long term path)
Adding the AEM 6.3 compatible grid.less file into an embedded AEM Package.
Adding a dependency on the OOTB AEM 6.3 package that deploys the new grid_base.less file; ie this dependency will only exist on 6.3 instances.

The major downside is the on 6.4 there will be an uninstalled package, blocked by package dependencies. Definitely open to other more elegant solutions.

Perhaps we could temporarily have this be an extra manual fix install as well and figure out if we can get product to fix for GA (big if) or figure out how to build different versions of the package using classifiers? Having the uninstalled package isn’t great looking

I don't think we should have an extra package that gets uploaded automatically. I think this should be a manual fix until we can figure something out on the product side. Maybe we can ask if the 6.4 location can be back-ported to 6.3 as part of a Service Pack?
A different approach would be to extract the grid LESS into its own client library and have two versions, one for 6.3, another for 6.4. The grid can the get included as part of the Template's page policy or could be embedded into the Theme client library. I like this approach because the Theme/policies will be project specific and each project can target based on the version AEM they are running? Still not ideal of course.

Disagree wrt to the manual fix - a manual fix implies that you need to apply it everytime you deploy an update to ASC (at least in one of the two case) which is not tenable/best-practice (imagine if you had to install an HF everytime you deployed your app?!).
The CL + Policy update has the sad side-effect of not being BC (its weird in that its leaking the bug pretty far out into runtime config).
The package approach above is effectively an automation of the manual-fix approach, which the unfortunate side effect of unsatisfied packages on 6.4.
IMO tenants we adhere to for this fix are:

(Easily) automatic and transparent-as-possible to consumers of ASC
Backward compatible
The AEM 6.4 approach is the "default" (since the approach in 6.4 is the long-term solution)

So, I guess let's wait to see if we can get a proper fix in the product.


Default settings

Is it possible to set the "Where separate prefix" value somehow to 2 as default?

Hi @mlostekk
Can't set default value now.
If it create a class that inherits PersistentStateComponent , it will be possible.
http://www.jetbrains.org/intellij/sdk/docs/basics/persisting_state_of_components.html
But, I can't use the time on maintenance. Sorry.
If possible, please send pull request. 🙏


Cycling envelopes

The feature you'd like
Loopable AD envelope with 'end of cycle' callbacks.
The envelope parameters can be modulated independently in realtime.
Any alternatives you've considered
Some complex combination of Signal and Gain nodes I figure.
Additional context
Buchla Dual Function Generator

Thanks for this suggestions @munozu
Since Web Audio envelopes are all scheduled, an onended callback of an envelope might come a little too late. By that i mean that if you if you wanted to do something in response to an envelope ending, the looseness of JS timing would make that difficult. Web Audio gets around this by scheduling everything using sample-accurate timing. If you wanted a second envelope to be triggered directly after the first one ends, you could use the scheduled timing to do that
const currentTime = Tone.now()
// the attack phase: 0->1 over the course of 0.1 seconds starting 'now'
signal.linearRampTo(1, 0.1, currentTime)
// the release of the envelope starts after the attack
signal.linearRampTo(0, 0.1, currentTime + 0.1)

// at this point you could schedule something else with this envelope time.
const envelopeEndTime = currentTime + 0.2

This also doesn't enable the attack/decay to modified in real time since they are scheduled ahead of time.
The way to achieve this would probably be a AudioWorklet if you had any interest in contributing this as a PR, these days i don't have much time to work on such a feature


MudDatePicker's PickerActions Breaks Date Selection

Bug type
Component
Component name
MudDatePicker
What happened?
When the PickerActions is specified in the Razor, the ability to select a date stops working.
This works
<MudDatePicker Label="Expiration Working"    MinDate="DateTime.Now.Date"    Required="false"    @bind-Date="ExpirationDate2"> </MudDatePicker>
This does not (it doesn't matter if there are child components within the PickerAction tag:
<MudDatePicker Label="Expiration Not Working"    MinDate="DateTime.Now.Date"    Required="false"    @bind-Date="ExpirationDate1">    <PickerActions>    </PickerActions> </MudDatePicker>
Expected behavior
You should continue to be able to select a date when the PickerActions is defined.
Reproduction link
https://try.mudblazor.com/snippet/mYGPFQGhrpNcISgu
Reproduction steps

Click on "Expiration Working"
Select a date (works).
Click on "Expiration Not Working"
Select a date (doesn't work).

Relevant log output
No response
Version (bug)
6.0.2
Version (working)
No response
What browsers are you seeing the problem on?
Firefox, Microsoft Edge
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I added " AutoClose="@true"" to your example and it works fine.
Behavior issue.  If you define PickerAction AutoClose defaults to False.
<MudDatePicker Label="Expiration Not Working"
   MinDate="DateTime.Now.Date"
   Required="false" AutoClose="@true"
   @bind-Date="ExpirationDate1">
   <PickerActions>
   </PickerActions>
</MudDatePicker>

See : https://try.mudblazor.com/snippet/QuGvlcmDBBKOkjEs


Adding an S3 backend

Hi,
I'm considering investing some time to add a backend for aws s3. I'm wondering a few things, first of all, is it worth it? This project seems mostly abandoned even though it is still linked to from electron documentations.
Secondly, javascript and node have moved on significantly in the last 7 years. I'm wondering if it would be acceptable to use newer language and node standard library features or if I should continue with this ES5 style of writing code.
There are also multiple vulnerabilities detected by npm audit which I would like to resolve since we are running nuts in a production environment.
Please let me know if there's anyone out there and what you think of my suggestion.

@willm I would be happy to see an S3 backend for my fork, https://github.com/dopry/pecans I'm also on the look out for additional maintainers.


Incorrect layout calculation results in empty month for vertical paging mode

I've done some debugging and the issue itself is in layoutAttributesForElementsInRect method.
There is calculations of the start and the end row for layout which is using fs_height and rely on integer division as we can see here:
NSInteger startRow = ({
                    NSInteger startSection = rect.origin.y/self.collectionView.fs_height;
                    CGFloat heightDelta = FSCalendarMod(CGRectGetMinY(rect), self.collectionView.fs_height)-self.sectionInsets.top;
                    heightDelta = MIN(MAX(0, heightDelta), self.collectionView.fs_height-self.sectionInsets.top);
                    NSInteger countDelta = FSCalendarFloor(heightDelta/self.estimatedItemSize.height);
                    NSInteger startRow = startSection*6 + countDelta;
                    startRow;
                });

If we add rounding to the method which is used here to obtain height like so, we will receive the correct result:
- (CGFloat)fs_height
{
    return round(CGRectGetHeight(self.frame));
}

Here is debug tracing of start and end indexes before and after this change, during swiping months:
Before:
height:260.333344 start:0 end:13
height:260.333344 start:91 end:104
height:260.333344 start:104 end:117
height:260.333344 start:117 end:130
height:260.333344 start:130 end:150
height:260.333344 start:150 end:157
height:260.333344 start:157 end:170
height:260.333344 start:170 end:183

After:
height:260.000000 start:0 end:13
height:260.000000 start:91 end:104
height:260.000000 start:104 end:118
height:260.000000 start:118 end:131
height:260.000000 start:131 end:144
height:260.000000 start:144 end:157
height:260.000000 start:157 end:170
height:260.000000 start:170 end:183

Most likely we can do this change, but the issue is that this method is widely used across this library and as there are no unit tests I not sure that we can do this without affecting anything.

Issue is still exist after https://github.com/WenchaoD/FSCalendar/commit/27bd907b08c3979928551265d54b301fa6d94073

@numen31337 Can you provide a sample project which reproduce the issue?

Here is the project with the issue, you need to scroll down to Jan 2018 to see the issue on the iPhone 5:
https://www.dropbox.com/s/apt6gp7v4rhm5ee/EmptyMonthIssue.zip?dl=0
And the video demonstration:
https://www.dropbox.com/s/xb4bktob6hlczdb/IssueVideo.mov?dl=0

Can you help try this commit in development branch?

Can't reproduce this issue on the development branch anymore.

Thanks.


Make it Wayland ready

Right now, AppImageUpdate won't run on a KDE Desktop that is configured to use Wayland (env var QT_QPA_PLATFORM set to wayland).
I don't know Qt too well, so I don't know which version started supporting Wayland, and if it's feasible to switch to that version, but when that env var is set to wayland, AppImageUpdate will silently fail to start. There are two solutions:

Compile it with a newer version that supports the wayland platform plugin;
Add export QT_QPA_PLATFORM=xcb to AppRun.

We're building against Qt 5.9.3 and could easily upgrade to Qt 5.10. The question is, would that "just fix" the issue? I presume we have to ship said wayland plugin simply, just like we do with xcb?
@probonopd did you have such issues before?

No, my assumption was that applications written for X continue to run under Wayland thanks to some compatibility layer.

QT_QPA_PLATFORM set to wayland

Never seen that. Is this the default configuration of any Linux desktop, as of today?

QT_QPA_PLATFORM was set to wayland as a default for a while in KDE. And applications not supporting that and instead failing silently was exactly the reason this default was reverted for now (which results in all KDE applications being run as xcb applications).

Good. I expect Wayland to be an option once the oldest still-supported distributions use Wayland, but not before. When shipping applications to users on unknown target systems, we need to always shoot for the "lowest common denominator".

Can you not just ship both the wayland and xcb plugins?

One could, but isn't shipping a wayland plugin kinda pointless when xcb works just as well, at least for the forseeable future (until xcb is no longer supported)?

Which would imo be a point for setting that variable to xcb.

@zilti the thing is, AppImageUpdate doesn't have an "AppRun script", it just uses a symlink to the main binary. That's the big advantage of tools like linuxdeploy: they make those scripts mostly obsolete.
There must be a better way than setting such a variable. Shipping the other plugin seems like a better idea, if it fixes the issue and won't increase the size significantly, as it would provide native integration without having to deal with xwayland and its bugs etc.

Ah, I see. Tbf even with linuxdeploy - it has been a big help though - I have not yet been able to go without at least a simple AppRun script, since the stuff I packaged so far all needed env vars.

That's perfectly fine, of course, we do it in some AppImages, too. But the "default way" shouldn't be adding scripts; if someone else wants to add some additional env var, things become complex to handle.
We already thought about allowing linuxdeploy plugins to create "hook/callback scripts" which are called by a "main" AppRun script (if available), which would mean we forcibly ship our own script and don't allow for completely custom scripts any more, but that's got more drawbacks than advantages (slower startup, additional complexity, not as obvious to packagers, ...).
We should continue the discussion in https://github.com/linuxdeploy/linuxdeploy-plugin-qt/. I'll open an issue there, and will reference this one. Hope you don't mind when I ping you there.

@zilti did you get a chance to run the latest version and see if it "just works" now?

I did! It does not work though... Here's what it does:
$ export QT_QPA_PLATFORM=wayland
$ ./AppImageUpdate-x86_64.AppImage
AppImageUpdate version 1-alpha (commit 6f2d028), build 400 built on 2019-02-07 22:44:08 UTC
Failed to load client buffer integration: wayland-egl

qt.qpa.wayland: No shell integration named "xdg-shell" found
qt.qpa.wayland: No shell integration named "xdg-shell-v6" found
qt.qpa.wayland: No shell integration named "wl-shell" found
qt.qpa.wayland: No shell integration named "ivi-shell" found
qt.qpa.wayland: Loading shell integration failed.
qt.qpa.wayland: Attempted to load the following shells ("xdg-shell", "xdg-shell-v6", "wl-shell", "ivi-shell")
Could not create a shell surface object.

Confirms my overall impression of Wayland, adding pain without much gain (for me). I'd say don't bother until we are forced to (= Xorg does not work anymore).

The amount of libraries that would have to be added is quite large, yeah. And the files aren't available from "any" Qt distribution, you need to install extra files, etc.
I think we should drop support for it from linuxdeploy-plugin-qt again, or make it optional at least.

We've dropped Wayland support in linuxdeploy-plugin-qt again. We won't be supporting Wayland natively in the forseeable future.


sql lab didn't select default database when open the first tab on superset

I setup these two parameters in superset_config.py
# The db id here results in selecting this one as a default in SQL Lab
DEFAULT_DB_ID = 7 # https://github.com/apache/incubator-superset/blob/master/superset/config.py#L512

# SQLLAB_DEFAULT_DBID
SQLLAB_DEFAULT_DBID = 7 # https://github.com/apache/incubator-superset/blob/master/superset/config.py#L521

I don't have any tabs, then I opened the first tab, superset didn't select the default database that I setup in superset_config.py
Is this the right way to setup default database? Or the code here didn't work? https://github.com/apache/incubator-superset/blob/master/superset-frontend/src/SqlLab/components/TabbedSqlEditors.jsx#L223

Hi @jiegzhan - please fill out all of the required information in the issue template to help the maintainers better assist you.