text:
U - Fix CSS linter errors: data.specifications errors

The linter will check that pages correctly include this ingredient.
As per the spec for the linter, there are two specific errors that the linter raises here.

"data.specifications/expected-heading" is raised when the page doesn't have an H2 "Specifications". Sometimes this is just because the section is called "Specification".
"data.specifications/expected-macro" is raised when the section does not include the specification link via a call to the {{SpecName}} macro, or the exact text "Not part of any standard.".

Currently we have 45 "data.specifications/expected-heading" errors and 35 "data.specifications/expected-macro" errors. They are listed in the spreadsheet, all together in the "data.specifications" tab.
A substantial chunk of these seem to be nonstandard features, where the fix is just to make sure the text is exactly "Not part of any standard.". For the remainder we'll want to add spec URLs to SpecData.json, so {{SpecName}} can look it up.
Acceptance criteria

[x] There are zero errors reported by the linter for the "data.specifications" ingredient, when run against https://developer.mozilla.org/en-US/docs/Web/CSS

This is now done.

repo: mdn/sprints


text:
Add names to child DVGeos

Purpose
This PR changes how DVGeo class tracks its children. Old implementation just appended the children to a list, which is then indexed in order. The current implementation saves the child DVGeometries in the self.children dictionary. The keys of the dictionary are the names of each child DVGeo. This makes the code a lot more readable since each child DVGeo is referenced by its name.
The old functionality is maintained, and unless users were accessing the child DVGeometries in a hacky way by indexing the old list, everything should work fine. Some output names might be different, but we can also fix this behavior. The names of the added pointsets will be the same if users don't provide a name for the child DVGeo.
I will apply a similar set of changes to the mphys wrapper once #193 is merged.
Expected time until merged
2 weeks
Type of change

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (non-backwards-compatible fix or feature)
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no API changes)
[ ] Documentation update
[ ] Maintenance update
[ ] Other (please describe)

Testing

Checklist

[ ] I have run flake8 and black to make sure the Python code adheres to PEP-8 and is consistently formatted
[ ] I have formatted the Fortran code with fprettify or C/C++ code with clang-format as applicable
[ ] I have run unit and regression tests which pass locally with my changes
[ ] I have added new tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation

Should we change the approach here to rely on that name attribute?

Yes, there is a name attribute in the BaseDVGeo class so everything inheriting from that has access to it, I think it makes sense to use that since it's already there.

source: gharchive/pull-request

authors: anilyil hajdik

repo: mdolab/pygeo

license_type: permissive

license_source: github-api


text:
Match a list of known adapter sequences

A fast strategy would be to break adapter sequences into kmers, and then classify previously counted kmers into "possible adapter" kmers.

The list from Trimmomatic is probably good: timflutre/trimmomatic/adapters

Illumina's PDF says I can redistribute the sequences with a copyright notice.
Oligonucleotide sequences © 2007-2013 Illumina, Inc. All rights reserved. Derivative works created by Illumina customers are authorized for use with Illumina instruments and products only. All other uses are strictly prohibited.

source: gharchive/issue

license: mit

license_source: bigquery


text:
feat: support for highlighting JSX evaluated expressions

In JSX, you can include JS expressions within tags, like:
{doSomething(‘a’, 7)}

This PR adds syntax highlighting for those expressions.
Limitations
It will still highlight JS that isn’t valid to include in a JSX evaluated expression (eg. a class definition), which as far as I can tell is a limitation of how embedded languages work in TextMate syntax highlighting definitions.

In its current state, this PR fails linting:
yarn run v1.22.15
$ /workspaces/vscode-mdx-1/node_modules/.bin/lint-staged
✔ Preparing lint-staged...
❯ Running tasks for staged files...
  ❯ .lintstagedrc.js — 2 files
    ↓ *.{*sh,env,env.*,gql,ini,properties,rb,css,less,sass,scss,styl,stylus,svelte,vue} — no files [SKIPPED]
    ↓ .!(browserslistrc|nvm)rc — no files [SKIPPED]
    ↓ Dockerfile — no files [SKIPPED]
    ❯ *.{cjs,cts,js,json,jsonc,json5,jsx,html,md,mdx,mjs,mts,pug,svelte,toml,ts,tsx,vue,yaml,yml} — 2 files
      ✖ eslint --cache -f friendly --fix [FAILED]
↓ Skipped because of errors from tasks. [SKIPPED]
✔ Reverting to original state because of errors...
✔ Cleaning up temporary files...

✖ eslint --cache -f friendly --fix:

  ✘  http://eslint.org/docs/rules/

     Parsing error: Could not parse expression with acorn: Expecting Unicode escape sequence \uXXXX

     test/fixture.mdx:28:5
     26 | Lorem ipsum dolor sit _amet_, consectetur adipiscing elit. Ut ac lobortis velit.
     27 |
   > 28 | {3 \* 7}
        |     ^
     29 |

✘ 1 problem (1 error, 0 warnings)

Errors:
  1  http://eslint.org/docs/rules/null
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I could change the text case to avoid this, but that seems dodgy. Does anyone have any pointers on how to fix this? I’m a bit lost on how the linting config works for this repo.

Your changes have been released in version 1.1.0. Thanks again! :heart:

authors: KeyboardSounds remcohaszing

repo: mdx-js/vscode-mdx

license: MIT


text:
What version of node/npm?

Hi, im trying to get rid of my first meanjs application. Im using the yo generator and when the generator starts to build the application it always fail. I tried with node 7.1 and npm 3.9. What should i use for get successful start configuration ?

Depends on the version of the generator. If your using the latest generator, I recommend using Node 4. I don't think Node 7 is officially supported by this project yet.

Thank for your reply @codydaig, if i dont use the generator what version of Node its supported?

@mycodeself I'm running Node v6.6.0 and haven't encountered any issues with this project. Node 7 isn't fully supported yet, so you might run into issues. If you manage to get this project working with Node 7, would you report back on what issues you encountered, and how you solved them?

@mycodeself Feel free to reopen if there's additional questions around this, otherwise i'm closing for now and considering it resolved.

authors: codydaig mleanos mycodeself

repo: meanjs/mean


text:
add snapshot repo envs

Add Elasticsearch snapshot repo env variables to deploy.sh

PS, we're adding a mediacloud-test-elasticsearch-snapshots repo to the dev deployment stage, since Elasticsearch Snapshot API does not allow a blank/None repository name, required for elastic-conf. Tracking issue here #290

@philbudne any further concerns on this?

repo: mediacloud/story-indexer


text:
Add priorityClassName to manager container

Help the scheduler to understand the pod's priority versus other pods to be scheduled.
Related links:

Pod Priority in Kubernetes - https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority
priorityClassName in OpenShift - https://docs.openshift.com/container-platform/latest/nodes/pods/nodes-pods-priority.html
Three priorityClassName conventions -  https://github.com/openshift/enhancements/blob/master/CONVENTIONS.md#priority-classes

/test 4.13-openshift-e2e

Hmm looking at the 3 Three priorityClassName conventions I'm not entirely sure whether  system-node-critical or  system-cluster-critical is more appropriate here.
As far as I see the only difference is that the latter one can be OOMKilled, which IIUC shouldn't happen as long as it's not using more memory than declared.

Am I getting it right ?
Any particular reason for choosing  system-cluster-critical over system-node-critical  ?

we should discuss this more, tbh I doubt that system-cluster-critical or system-node-critical should be used by non core OCP components.
/hold

Am I getting it right ?

👍🏻

Any particular reason for choosing system-cluster-critical over system-node-critical ?

Consistency with the other operators, since they use system-cluster-critical.
In the last team meeting we have discussed about this topic and AFAIU using system-cluster-critical, as the other operators use, is the less strict priorityClassName out of the two common Kubernetes PriorityClasses and it suits FAR.

authors: mshitrit razo7 slintes


text:
Very disruptive flash when in dark mode and opening new tab

Firefox 87.0

I think it's caused by the css transition
transition: background-color 0.3s ease-in-out;
I'll find a way to fix it

authors: jamesSampica medyo


text:
Skype - "Browser not supported"

Describe the bug
Skype shows:
Browser not supported
Use Microsoft Edge or Google Chrome to access Skype for Web (Preview) experience.
Alternatively, download Skype on your desktop computer.
To Reproduce
Steps to reproduce the behavior:

Create a Skype service.

Expected behavior
Skype to work.
Screenshots
https://i.imgur.com/Nl5jNuV.png
Desktop (please complete the following information):
Windows 7. My default browser is Firefox, where I notice Skype Web has the same error. However Franz has ordinarily shown up as Chrome.
"Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Franz/5.0.0-beta.18 Chrome/59.0.3071.115 Electron/1.8.4 Safari/537.36"
Additional context
Issue started today.

Experiencing the same issue with 5.0.0-beta.18

Experiencing the same issue with 5.0.0-beta.18.
Updating to 5.0.0.-beta.24 has resolved the issue.

Thanks, this fixed the issue for me :)

I'm on OS X Mojave 10.14.3 and not getting the option to upgrade from 5.0.0.-beta.18 to beta.24
I did not have beta updates enabled so not sure how I ended up with this version, but checking for an upgrade isn't working.

I'm on Linux (Ubuntu 16.04) and I'm also stuck with 5.0.0-beta.18 (and no skype :-( )

when will this come to stable?

There might be a manual workaround like this https://github.com/meetfranz/franz/issues/1347#issuecomment-475107222 I guess. Any clue about this? I don't have any User Agent settings in ~/.config/Franz/recipes/skype/index.js =(

@anewtonlevey @tkreque Could you guys please show the contents of ~/.config/Franz/recipes/skype/index.js on your system?

Here is mine
"use strict";

module.exports = Franz => Franz;

Oh, I see. This means that default Franz User Agent has been updated in betas to align with new Skype and Slack requirements...

Browser not Supported ..... dude, it i so, so, so BORING !

same problem here since today. I'm using current 5.0.1-beta.1 on Ubuntu 18.10

Same problem, i've updated the index on skype recipe and reloaded Franz, but it still not working.

@ yermulnik replacing chrome version ain't enough - just use the complete Microsoft Edge User agent:
module.exports = Franz => class Skype extends Franz {   overrideUserAgent() {     return "Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10136";   } };

New release is coming ?

@q4z1 That worked, Kai! Thanks a bunch.

@q4z1 worked for me, too! thanks a lot

Hmm, wondering if this is related but after fixing Franz I've got all of my Skype chats outdated: it shows no new messages since ~1 month ago. Anyone experiencing this as well?

Hmm, wondering if this is related but after fixing Franz I've got all of my Skype chats outdated: it shows no new messages since ~1 month ago. Anyone experiencing this as well?

the same here. Ubuntu 18.10, Franz 5.0.0

@yermulnik: replacing chrome version ain't enough - better use the complete Microsoft Edge User agent:
module.exports = Franz => class Skype extends Franz { overrideUserAgent() { return "Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10136"; } };

Nice, it works !

@yermulnik: replacing chrome version ain't enough - better use the complete Microsoft Edge User agent:
module.exports = Franz => class Skype extends Franz { overrideUserAgent() { return "Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10136"; } };

Thank you for the quick patch! It worked for me as well in OpenSUSE Leap 15.0, Franz 5.0.0.
Just to clarify, you should edit the file ~/.config/Franz/recipes/skype/index.js and replace the module.exports line by the one provided here. Guess you guys are more into Franz than me but I had to look for it :(

Hmm, wondering if this is related but after fixing Franz I've got all of my Skype chats outdated: it shows no new messages since ~1 month ago. Anyone experiencing this as well?

Same here. OpenSUSE Leap 15.0, Franz 5.0.0.

Hmm, wondering if this is related but after fixing Franz I've got all of my Skype chats outdated: it shows no new messages since ~1 month ago. Anyone experiencing this as well?

I stumbled upon Franz last night because my web.skype didn't work anymore with Chrome & Chromium on Linux Mint 19 - same error with the "compatible browser". My skype chatlog on my "new" Franz setup  is up2date though. Maybe try to completely remove and re-install the service?

Hmm, wondering if this is related but after fixing Franz I've got all of my Skype chats outdated: it shows no new messages since ~1 month ago. Anyone experiencing this as well?

I stumbled upon Franz last night because my web.skype didn't work anymore with Chrome & Chromium on Linux Mint 19 - same error with the "compatible browser". My skype chatlog on my "new" Franz setup is up2date though. Maybe try to completely remove and re-install the service?

That worked for me :dancer:

What is user agent using is v5.0.1 for skype?

@q4z1 "Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10136" this user agent is not working in mac os

My recipes/skype/index.js looks like this, and I get just a blank page:
"use strict";

module.exports = Franz => class Messenger extends Franz {
  overrideUserAgent() {
    return window.navigator.userAgent.replace(/(Franz|Electron)([^\s]+\s)/g, '');
  }

};

Looks like that approach is no longer working.
The agent override using Edge (as suggested above) at least gets Skype start loading, but in the end also shows a blank screen. I even tried to use an up-to-date agent string from an actual Edge on a Windows desktop, but no change, still broken:
module.exports = Franz => class Skype extends Franz {
  overrideUserAgent() {
    return "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Edge/18.18362";
  }
};

Any hints on how to get that working again?

@bittner: This is usually a temporrary issue with skype. Try using the latest chrome or chromium User-Agent.
Regards.

authors: anewtonlevey bittner ccccyes cristianrcv find-evil gmauro kikislater leasti mitelg pnenov premkolindala q4z1 tkreque tymik vdaele yermulnik

repo: meetfranz/franz


text:
Tried to add Yandex Mail but it doesn't show up on Franz

Hello, i have downloaded and added the Yandex Mail recipe under the AppData/Roaming/Franz/recipes folder. Then i restarted the Franz but it didn't show up. Can you help me with this situation?
Service
Yandex Mail
Link to your repository
https://github.com/mskonovalov/franz-yandex-mail-recipe

@utkudagli  FYI, recipe folder path should be: ~/Library/Application Support/Franz/recipes/dev/yandex.
Official documentation: https://github.com/meetfranz/plugins/blob/master/docs/integration.md

authors: ansidev utkudagli

repo: meetfranz/plugins


text:
cannot import name '_jpegpy' from 'lib.data_preprocess.utils.jpegpy'

Hi，I have a question.can you help me, please?

You can refer to the following closed Issues.
"How do I generate so files"

repo: megvii-research/CADDM


text:
Some questions on "Implicit Identity Leakage"

Thank you for the new insight in deepfake detection!
I have some questions for fully understanding the "Implicit Identity Leakage".
The FF++ real dataset has 1000 videos, and the author split them into 720, 140, 140 for train, val and test.
Taking the training set as an example, the fake videos used for training are generated by forging each other within the training set.
Therefore, on FF++, the face identity information of the training set and the test set do not overlap.
So if the network has learned a lot of features related to face identity, the in-dataset test AUC on FF++ dataset will also lead to a decrease because these face identities have not been seen during training.

"Implicit Identity Leakage" means that the binary classifier captures identity information during the training phase. But it does not mean that the classifier makes judgments only based on such identity information, it also utilizes the specific artifact feature learned from specific manipulation methods. During the in-dataset evaluation, the testing set is generated by the same manipulation method and contains the same specific artifact as the training set. The classifier achieves high performance by indicating such artifacts. However, when testing the model on cross-dataset evaluation, The classifier can not detect novel artifact features in the new testing set, it misuses the identity information to make false judgments.
For more details please see Section 3 and Section 5 of the paper "Implicit Identity Leakage: The Stumbling Block to Improving Deepfake Detection Generalization".

Thank you for the new insight in deepfake detection!
I have some questions for running the training code. When compiling the Makefile file, it shows that there is no jpeglib.h file

authors: LOOKCC Nku-cs-dsc liuxuannan


text:
Support for python 3.10?

Thanks again for maintaining a very useful library that is often used for SAML SSO.
I noticed when installing xmlsec on CPython 3.10 that a wheel is not available:
Installed /opt/hostedtoolcache/Python/3.10.2/x64/lib/python3.10/site-packages/python3_saml-1.14.0-py3.10.egg
Reading http://github.com/mehcode/python-xmlsec/tarball/master
Searching for xmlsec>=1.3.12
Reading https://pypi.org/simple/xmlsec/
Downloading https://files.pythonhosted.org/packages/70/d7/83ac0d43bb92333c8ba3d9be97b85d1b[285]
...
Best match: xmlsec 1.3.12
Processing xmlsec-1.3.12.tar.gz
Writing /tmp/easy_install-bey4yd1m/xmlsec-1.3.12/setup.cfg
Running xmlsec-1.3.12/setup.py -q bdist_egg --dist-dir /tmp/easy_install-bey4yd1m/xmlsec-1.3.12/egg-dist-tmp-umgx26l1
WARNING: The wheel package is not available.
WARNING: The wheel package is not available.
WARNING: The wheel package is not available.

I understand that only 3.5 to 3.9 is supported. Are there plans to support for 3.10?

I second this. For my project I only use >=3.10.
Because of the missing wheel, it is tried to create one locally upon installation (xmlsec is no direct dependency for me). The wheel creation crashes (on windows) because "stdio.h" is missing, which in itself is a whole 'nother issue, I know.

I 3rd it 😂 or any advice on workarounds / self-compilation etc.

Depends on linux it was pretty easy to self-compile. On windows I was not able to get it to work.
So if you are on linux I may be able to help you.

Thanks, but I'm on Windows

Hi there 👋 wonderful codebase maintainers. Just letting you know I am still really looking forward to 3.10 support on this. ❤

This is blocking my project from upgrading to 3.10 as there are no windows py310 binaries in the latest release

Please upgrade for 3.10!
we have a project with 3 major components and in one of them, xmlsec is the only library out of 35 that prohibits the upgrade of our platform to 3.10!

Would really love support for >=3.10! I have a hard requirement to use 3.10 at work, and would really love to be able to use xmlsec on a project.

Hi all, I've uploaded windows wheels including 3.10 ones with the release of 1.3.13.

Can confirm! Thanks for that!

authors: Cielquan astrochun daveisagit hoefling kostasmarkakis mick88 swolfe2

repo: mehcode/python-xmlsec


text:
Draw overlay for both 2D and 3D birefringence acquisitions

Resolves #263

@talonchandler This naive solution does leave the GUI window unresponsive after reconstruction finished on the Automaton computer. Not sure if it is because of this though.

Codecov Report

Merging #270 (867b5b7) into main (f84f09d) will not change coverage.
The diff coverage is 0.00%.

@@          Coverage Diff          @@
##            main    #270   +/-   ##
=====================================
  Coverage   4.38%   4.38%
=====================================
  Files         22      22
  Lines       4970    4970
=====================================
  Hits         218     218
  Misses      4752    4752

Impacted Files
Coverage Δ

recOrder/plugin/main_widget.py
0.00% <0.00%> (ø)

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

Now the GUI does not freeze, but there's a delay before 3D overlay can be updated. On a local computer with high single-thread CPU performance, a 21512512 volume (from demo MM camera) takes < 1s; with Xeon Silver @2.4GHz we typically have on microscope computers, a 2120482048 volume will take 5~10s to be rendered.

authors: codecov-commenter ziw-liu

repo: mehta-lab/recOrder


text:
Bors and bumps

When merging bump at the start of the week bors raises the following error:
{{:badmatch,
  {:error, :push, 422,
   "{\"message\":\"At least 1 approving review is required by reviewers with write access.\",\"documentation_url\":\"https://docs.github.com/articles/about-protected-branches\"}"}},

Is this something that we want? Something that can be changed?

What don't you want in this behavior?
Why do you try to merge an unapproved PR?

Merge an un-approved PR is an administrator privilege and should not be done in most cases. Bors can be launched by a write-access contributor. So, if Bors could apply changes that only an admin contrib could, it would be a HUGE problem 🙂

My bad

authors: bidoubiwa curquiza

repo: meilisearch/integration-guides


text:
Add strapi plugin to readme and create plugin sections

Naming based upon:

bors merge

Oops, no bors


text:
Support for custom csv delimiter

Pull Request
Related issue
Fixes #292
What does this PR do?

Adds csvDelimiter parameter to addDocumentsCsv, addDocumentsCsvInBatches, updateDocumentsCsv, updateDocumentsCsvInBatches
Adds tests

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

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

Thank you so much for contributing to Meilisearch!
cc @brunoocasali

bors merge

authors: ahmednfwela brunoocasali

repo: meilisearch/meilisearch-dart


text:
Update version for the next release (v0.5.1)

Changes:

#119
#116
#118
#113

All the changes related to release v0.5.1 were merged into v0.5.0, I spotted a problem that prevented releasing a new release with the same tag. Since the v0.5.0 wasn't completed released, I removed the tag from the remote and regenerated it again. Now containing, of course, all the PR's merged for the v0.5.1.

repo: meilisearch/meilisearch-rails


text:
CI failing on release-v1.9.0

A lot of our CIs are failing on release-v1.9.0 (and on main, but less urgent)
https://github.com/meilisearch/meilisearch/actions/runs/9543257463

Due to the new release of rust

Fiiiiiixed
https://github.com/meilisearch/meilisearch/actions/runs/9549769580

repo: meilisearch/meilisearch


text:
[QUESTION] mobile offline geocoding

I hope it is OK to ask question here.
I am investigating the possibility of using Milli for offline mobile geocoding
The idea is this :

compile Milli for android and wrap.it through jni
generate a pre indexed database of geocoding doxuments

Presented like this it seems doable. But there are some questions and would love to have the team opinion befaure rushing into this:

i saw some numbers of 20mb memory usage with already indexed database. is that correct?
wondering about the size the database would be. is there any comparison we can do between the json representation of the database and the database itself in terms of size?
I know you have some Geo functions. could it handle filtering in a bbox ?
does that seem like a good fit to you?

Thanks for that amazing project

Hey @farfromrefug,

generate a pre indexed database of geocoding doxuments

What do you mean by pre-indexed? Is this something that milli will need to index or as it been already indexed by milli, and you are taking a snapshot (i.e. a copy of the already indexed file), here?

i saw some numbers of 20mb memory usage with already indexed database. is that correct?

Milli is entirely based on LMDB, which is a memory-mapped key-value store. Memory mapping is a technology that let the OS choose between loading pages from the disk in memory based on the available amount of memory and the usage of the pages. The memory usage that you could see is either the Rust program itself when functioning or the virtual memory usage (due to the memory mapping). In short: the OS can use the whole memory if it evaluates that it is more performant to do so but it will automatically release it if other programs need it.

wondering about the size the database would be. is there any comparison we can do between the json representation of the database and the database itself in terms of size?

It is, unfortunately, very hard to evaluate the amount of disk space that will be used by the engine, you can probably do some tests and graph with your own data.

I know you have some Geo functions. could it handle filtering in a bbox ?

I don't think so, you should look at the documentation, but I think this is something that we wanted to implement at some point. You can use the product repository to ask for specific features.

does that seem like a good fit to you?

A good fit for doing searches without calling the HTTP server? Yeah, but keep in mind that it hasn't been developed for such use cases and therefore the documentation of this library is not very good. Milli is the core of Meilisearch and is kind of hidden inside.

@Kerollmops First thank you for taking the time to answer me.

What do you mean by pre-indexed? Is this something that milli will need to index or as it been already indexed by milli, and you are taking a snapshot (i.e. a copy of the already indexed file), here?

yes i am talking about a snapshot that i would prepare in advance and then push on the phone. The idea is for milli to have everything ready.

A good fit for doing searches without calling the HTTP server? Yeah, but keep in mind that it hasn't been developed for such use cases and therefore the documentation of this library is not very good. Milli is the core of Meilisearch and is kind of hidden inside.

Yes the idea is to have something running as a lib and thus without an http server. Which is why i looked at milli directly. I know documentation is not "made for this" and i understand i would have to dig and test for myself.
This is also the reason i asked here first before going deep into it.
I think i l close this issue as you answered my questions. Though i might be asking a few more questions in the future if i have a go at this ;)
Thanks again

authors: Kerollmops farfromrefug

repo: meilisearch/milli


text:
Accessibility: make pressing the "enter" key, validate the admin key modal

When providing the admin key in the modal

Pressing on the enter key does not validate the input.
For accessibility purposes we should maybe trigger the ok when pressing on enter
Browser: Chrome Version 103.0.5060.53 (Official Build) (arm64)

Hi
I wanted to try this issue.
Can you please assign it to me?
Thanks

Thanks for your interest in this project 🔥 You are definitely more than welcome to open a PR for this!
We prefer not assigning people to our issues because sometimes people ask to be assigned and never come back, which discourages the real volunteers contributors from opening a PR to fix this issue.
We will accept and merge the first PR that fixes correctly and well implements the issue following our contributing guidelines.
We are looking forward to reviewing your PR 😊

authors: bidoubiwa nooras

repo: meilisearch/mini-dashboard


text:
Indexing NDJSONs

The goal of this PR is to specify NDJSON indexing.

I've updated this specification regarding similar points from @Kerollmops review on CSV file support.

repo: meilisearch/specifications


text:
[bug] Unable to install modules

Describe the bug
On a comfyUI portable install. I get this issue after installing with comfyUI manager.
I've tried manually installing tensorflow and it bugs comfyUI to the point I had to set up a fresh install. could use a hand.
Reproduction
No response
Expected behavior
Load all nodes. when installed using comfyUI manager.
Platform and versions
Windows, ComfyUI Portable.

Console output
[comfy_mtb] | STATUS -> Some nodes failed to load:
        Failed to import module faceswap because ModuleNotFoundError: No module named 'onnx.onnx_cpp2py_export.defs'; 'onnx.onnx_cpp2py_export' is not a package
        Failed to import module image_interpolation because ModuleNotFoundError: No module named 'tensorflow'

Additional context
Been having major issues with mtb installs, some of the features would be very useful for things im doing with tutorials and animation.

Hi,
On windows in order to have GPU support I use an older version of tensorflow since they dropped GPU support on native windows.
This leads to quite a few issues that I try to patch in the install but it's obviously not enough (a lot of issues are about this)
In your case though (the onnx error) I think it might be the python version (for now mtb is only working with 3.10.X and I'm working on 3.11 support).
If you can confirm your python version it would be useful

Python 3.10.9

If it helps, I get this error when installing (same python version as @Ferniclestix)
ERROR: Could not install packages due to an OSError: [WinError 5] Access is denied: 'C:\\Users\\xxx\\ComfyUI_windows_portable\\python_embeded\\Lib\\site-packages\\onnxruntime\\capi\\onnxruntime_providers_shared.dll'
 Consider using the `--user` option or check the permissions.

Also a duplicate of #83 I guess

same trouble...

Some clue as commented here on this related issue https://github.com/melMass/comfy_mtb/issues/83

Thanks, interesting.
I think there are two distinct issues here. The one @roop03988 linked to seems to indeed be related to the OPs issue, but @rcoedo your case is a bit different, it took me time to understand but my install script is trying to be smarter than needed and spawn threads... windows and pip don't like that and the file lock result in the issue you are seeing, I will have a fix for that this week

Hi,
The problematic nodes are removed in the next version, more precisely they are optional, you can learn more about it in the readme where I link to alternatives: https://github.com/melMass/comfy_mtb#optional-nodes

authors: Ferniclestix ffdown melMass rcoedo roop03988


text:
StrokedTextView not found

Hey there, I was interested in using your library but it doesn't seem to be working. I can't add it to an xml layout, it can't be found for some reason. I tried:
<com.melih.strokedtextview.StrokedTextView
            android:id="@+id/strokedTextView"
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:text="@string/text1"
            app:strokeColor="@color/colorPrimaryDark"
            app:strokeThickness="3dp"/>

Some more error details for you:
 Caused by: android.view.InflateException: Binary XML file line #63: Binary XML file line #63: Error inflating class com.melih.strokedtextview.StrokedTextView
     Caused by: android.view.InflateException: Binary XML file line #63: Error inflating class com.melih.strokedtextview.StrokedTextView
     Caused by: java.lang.ClassNotFoundException: Didn't find class "com.melih.strokedtextview.StrokedTextView"

repo: melihaksoy/StrokedTextView


text:
App freezes when we go back from the screen which uses this library

Is this a bug report, a feature request, or a question?
(Bug report)

Have you followed the required steps before opening a bug report?
(Check the step you've followed - put an x character between the square brackets ([]).)

[x] I have read the guidelines regarding bug report.
[x] I have reviewed the documentation in its entirety, including the dedicated documentations :books:.
[x] I have searched for existing issues and made sure that the problem hasn't already been reported.
[x] I am using the latest plugin version.
[x] I am following the issue template closely in order to produce a useful bug report.

Have you made sure that it wasn't a React Native bug?
(yes.)

Is the bug specific to iOS or Android? Or can it be reproduced on both platforms?
(The bug specific to iOS and iOS versions: 14.3)
Is the bug reproductible in a production environment (not a debug one)?
(Reproduce on both.)

Environment

Environment:
React: 17.0.2
React native: 0.65.1
react-native-snap-carousel: ^3.9.1
"@react-navigation/bottom-tabs": "^6.0.7",
"@react-navigation/native": "^6.0.4",
"@react-navigation/stack": "^6.0.9",
Target Platform:
iOS (14.3)
Expected Behavior

(The app should not freeze when going back to the tab screens)
Actual Behavior

(The app is freezing when going back from the screen which uses this library to the tab screens, when we remove this library app is working fine)
Reproducible Demo
I think it do not need the reproducible link

Steps to Reproduce

(Write your steps so that anyone can reproduce the issue in the Snack demo you provided.)

Create a StackNavigator, inside create 2 screens 1 having tabNavigator the initial route and second will be a screen which uses this library.
When we go back from second screen which uses this library it goes back but freezes the application.
When we remove library it works fine.

A quick workaround I found is to reset the stack on navigating back.

@zuhairnaqi Sorry, please allow me to advertise for my open source library! ~
I think this library react-native-reanimated-carousel will solve your problem. It is a high performance and very simple component, complete with React-Native reanimated 2

repo: meliorence/react-native-snap-carousel


text:
Document compensation framework

Migrated from GitLab: https://gitlab.com/meltano/handbook/-/issues/21
Originally created by @DouweM on 2021-11-12 23:29:46

Benchmark: OptionImpact, All US or SF, Enterprise, Seed Funding Only or "< 10 people", 75th percentile
Factors for regions: Europe: 0.7, Latin America: 0.5 (with room for exceptions for e.g. Switzerland)
https://gitlab.com/meltano/administration/-/issues/3
https://gitlab.com/meltano-admin/hiring/-/issues/16#note_629081859

View 8 previous comments from the original issue on GitLab

repo: meltano/handbook


text:
bug: property-level aliases/renaming doesn't appear to work

Meltano Version
3.0.0
Python Version
3.10
Bug scope
CLI (options, error messages, logging, etc.)
Operating System
Linux - 20.04
Description
Multiple core docs specify that properties can be renamed with mappers:

The meltano mappers guide documentation indicates, in the Property (Column) Level, section, that Aliasing: properties can be renamed in the resulting stream e.g. altering a column name from id -> customer_id
The Meltano SDK stream_maps documentation, in the Property-Level Mapping Applications section, indicate that stream_maps support Property-level aliasing: properties can be renamed in the resulting stream.

However, in v3.0.0, either this no longer works or all documentation that provides examples have been lost, as I searched through the docs as well as the source code for both the SDK and the meltano-map-transform plugin.
For example, for a config file that looks like :
...
  mappers:
  - name: meltano-map-transformer
    variant: meltano
    pip_url: git+https://github.com/MeltanoLabs/meltano-map-transform.git
    mappings:
    - name: lower-case-schema
      config:
        stream_maps:
          {STREAM_NAME}:
            __alias__: {new-table-name}
            {COLUMN-PROPERTY}:
              __alias__: {new-property-name}
...

The stream/table name is renamed but the property/column is not. There is a partial work around to make a copy of the column and then delete the old column.
      config:
        stream_maps:
          {STREAM_NAME}:
            __alias__: {new-table-name}
            {new-property-name}: {COLUMN-PROPERTY}
            {COLUMN-PROPERTY}: __NULL__

Sorry if this isn't quite a "bug" or if issues with the mapper  belong somewhere else - it was not clear where communication / contribution streams are or go (and Slack is unfortunately blocked at my workplace).
Code
...
  mappers:
  - name: meltano-map-transformer
    variant: meltano
    pip_url: git+https://github.com/MeltanoLabs/meltano-map-transform.git
    mappings:
    - name: lower-case-schema
      config:
        stream_maps:
          {STREAM_NAME}:
            __alias__: {new-table-name}
            {COLUMN-PROPERTY}:
              __alias__: {new-property-name}
...

Hi @kcphila! Thanks for logging.
This format, with nested column properties is not actually supported
  mappers:
  - name: meltano-map-transformer
    variant: meltano
    pip_url: git+https://github.com/MeltanoLabs/meltano-map-transform.git
    mappings:
    - name: lower-case-schema
      config:
        stream_maps:
          {STREAM_NAME}:
            __alias__: {new-table-name}
            {COLUMN-PROPERTY}:
              __alias__: {new-property-name}

so I'm curious if you found an example like it in the docs, or whether you were following similar patterns for other Meltano settings.

There is a partial work around to make a copy of the column and then delete the old column.

Is the workaround not good enough for your use case? If so, what are you missing that's not supported by the "copy and delete" approach?

This format, with nested column properties is not actually supported

Hi @edgarrmondragon,
Thanks for the quick response.
There weren't code examples of the nested column format (aside from some "this would be nice" in feature requests), but the two main mapper doc pages both list changing property names as an existing feature of mappers (meltano mappers guide documentation and Meltano SDK stream_maps documentation). So, if property renaming isn't actually an existing (or soon to be coming) feature, it should be removed from the docs.
The copy/delete is doable (especially since it looks like __else__: __NULL__ will clear out the original column names) - but the real need is to be able to handle renames/reformats of the property schema in bulk - Is there some other way to do inline property/schema changes? The meltano/singer Oracle tap pulls in all uppercase, and so what I'm really looking to do as a starting point is something like (and it does seem like it would require a special key to refer to the stream metadata definition):
      config:
        stream_maps:
          {STREAM_NAME}:
            __meta__[col['name'].lower()]: col

There weren't code examples of the nested column format (aside from some "this would be nice" in feature requests), but the two main mapper doc pages both list changing property names as an existing feature of mappers (meltano mappers guide documentation and Meltano SDK stream_maps documentation). So, if property renaming isn't actually an existing (or soon to be coming) feature, it should be removed from the docs.

I'm just encountering this myself, too. Property-level aliasing is listed as a feature, but I don't see how it can be configured. I am using the "copy and delete" approach to make things work.

authors: edgarrmondragon kcphila kinghuang

repo: meltano/meltano


text:
mission 1: learn how to control robot (move, turn)

Goal is to learn how to move and turn the robot to reach a fixed goal. Eg, use the cliff walking level to move and turn and reach the diamond. Also to check that Malmo is working properly.

Create template src file for attendees to edit.

done see src/movement.py

repo: melvinzhang/ai-python-course


text:
Kiosk will not build

Describe the bug
I'm trying to build the Kiosk UI as documented at https://membermatters.org/en/latest/GETTING_STARTED.html#kiosk-mode.
To Reproduce
$ cd membermatters/
$ git clone git@github.com:membermatters/MemberMatters.git src
$ cd src/
$ cd frontend/
$ npm install
$ npm run build
$ API_BASE_URL=http://localhost:8000 npm run build:electron

> frontend@3.0.0 build:electron
> quasar build -m electron

 .d88888b.
d88P" "Y88b
888     888
888     888 888  888  8888b.  .d8888b   8888b.  888d888
888     888 888  888     "88b 88K          "88b 888P"
888 Y8b 888 888  888 .d888888 "Y8888b. .d888888 888
Y88b.Y8b88P Y88b 888 888  888      X88 888  888 888
 "Y888888"   "Y88888 "Y888888  88888P' "Y888888 888
       Y8b

 Build mode................ electron
 Pkg quasar................ v2.6.6
 Pkg @quasar/app-webpack... v3.5.1
 Pkg webpack............... v5
 Debugging................. no
 Publishing................ no

 Configured browser support (>= 84.95% of global marketshare):
 · Chrome for Android >= 100
 · Firefox for Android >= 99
 · Android >= 100
 · Chrome >= 91
 · Edge >= 97
 · Firefox >= 90
 · iOS >= 14.0-14.4
 · Opera >= 79
 · Safari >= 14.1

 App • Chaining "Renderer" Webpack config
 App • Extending "Renderer" Webpack config
 App • Cleaned build artifact: "/home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/dist/electron"
 App •  WAIT  • Compiling of "Preload" in progress...
 App •  WAIT  • Compiling of "Main" in progress...
 App •  WAIT  • Compiling of "Renderer" in progress...
(node:82995) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/node_modules/vuex/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show where the warning was created)
 App •  DONE  • "Preload" compiled with errors • 296ms

 App •  ERROR  •  Preload

Module not found: Can't resolve imported dependency "/home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/src-electron/electron-preload"
Did you forget to install it? You can run: yarn add /home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/src-electron/electron-preload

 App •  COMPILATION FAILED  • Please check the log above for details.

 • Compiling:
 ├── Preload  ███████████████████  92% sealing asset processing TerserPlugin
 ├── Main     ███████████████████  92% sealing asset processing copy-webpack-plugin
 └── Renderer ███                  10% building 0/1 entries 0/0 dependencies 0/0 modules

$ node:internal/process/promises:279
            triggerUncaughtException(err, true /* fromPromise */);
            ^

RpcIpcMessagePortClosedError: Cannot send the message - the message port has been closed for the process 83017.
    at /home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:47:47
    at processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: undefined,
  signal: undefined
}
node:internal/process/promises:279
            triggerUncaughtException(err, true /* fromPromise */);
            ^

RpcIpcMessagePortClosedError: Cannot send the message - the message port has been closed for the process 83011.
    at /home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:47:47
    at processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: undefined,
  signal: undefined
}

Expected behavior
I expect the node/electron Kiosk UI to build.
Screenshots
Desktop (please complete the following information):

OS: Ubuntu
Browser Chrome
Version

Additional context
Ubuntu 22.04
npm 8.5.0
nodejs 16.14.2

We haven't used the kiosk version for over a year now, so it's been a little neglected. I can take a look over the next few days and see what's broken. Looks like it's a dependency issue so hopefully not too big a deal!

That's fair enough, appreciate the insight.
Tbh, the kiosk just looked like something cool to add to the platform, we're quite a way away from needing it for any other reason than tracking how often people attend as we only have one room and so if someone's in the space we can probably see them!
Would be great to be able to play with it though if it is as simple as a dep update.

OK, so I found some more time to play with this and if I create the file frontend/src/electron-preload.js without any content, and then re-run it complains again:
 App •  DONE  • "Main" compiled with errors • 1671ms

 App •  ERROR  •  Main

Module not found: Can't resolve imported dependency "/home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/src-electron/electron-main"
Did you forget to install it? You can run: yarn add /home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/src-electron/electron-main

 App •  COMPILATION FAILED  • Please check the log above for details.

So I symlink src-electron/main-process/electron-main.js to src-electron/electron-main.js, and uncommment the preload line, and now I get the following:
npm --trace run build:electron

> frontend@3.2.0 build:electron
> quasar build -m electron

 .d88888b.
d88P" "Y88b
888     888
888     888 888  888  8888b.  .d8888b   8888b.  888d888
888     888 888  888     "88b 88K          "88b 888P"
888 Y8b 888 888  888 .d888888 "Y8888b. .d888888 888
Y88b.Y8b88P Y88b 888 888  888      X88 888  888 888
 "Y888888"   "Y88888 "Y888888  88888P' "Y888888 888
       Y8b

 Build mode................ electron
 Pkg quasar................ v2.8.3
 Pkg @quasar/app-webpack... v3.6.0
 Pkg webpack............... v5
 Debugging................. no
 Publishing................ no

 Configured browser support (>= 86.52% of global marketshare):
 · Chrome for Android >= 105
 · Firefox for Android >= 104
 · Android >= 105
 · Chrome >= 96
 · Edge >= 102
 · Firefox >= 95
 · iOS >= 15.2-15.3
 · Opera >= 87
 · Safari >= 15.2-15.3

 App • Chaining "Renderer" Webpack config
 App • Extending "Renderer" Webpack config
 App • Cleaned build artifact: "/home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/dist/electron"
 App •  WAIT  • Compiling of "Preload" in progress...
 App •  WAIT  • Compiling of "Main" in progress...
 App •  WAIT  • Compiling of "Renderer" in progress...
(node:26696) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/node_modules/vuex/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show where the warning was created)
 App •  DONE  • "Preload" compiled with success • 2291ms
 App •  DONE  • "Main" compiled with success • 4915ms
 App •  DONE  • "Renderer" compiled with errors • 31686ms

 App •  ERROR  •  Renderer  in ./node_modules/@quasar/extras/animate/fadeIn.css

ModuleBuildError: Module build failed (from ./node_modules/css-loader/dist/cjs.js):
    ValidationError: Invalid options object. CSS Loader has been initialized using an options object that does not match the API schema.
     - options.url should be one of these:
       boolean | object { filter? }
       -> Allows to enables/disables `url()`/`image-set()` functions handling.
       -> Read more at https://github.com/webpack-contrib/css-loader#url
       Details:
        * options.url should be a boolean.
        * options.url should be an object:
          object { filter? }

    - validate.js:105 validate
      [frontend]/[schema-utils]/dist/validate.js:105:11

    - NormalModule.js:585 Object.getOptions
      [frontend]/[webpack]/lib/NormalModule.js:585:19

 App •  COMPILATION FAILED  • Please check the log above for details.

Just coming back to this and wondering if you had a chance to look at it?
I'm seeing the same error still when following the commands to build at https://membermatters.org/en/latest/GETTING_STARTED.html#kiosk-mode
If I just run npm run build, then I get a long list of errors starting with:
App •  WAIT  • Compiling of "UI" in progress...
 App •  DONE  • "UI" compiled with errors • 114180ms

 App •  ERROR  •  UI  in src/components/Account/RegistrationCard.vue:179:14

TS2339: Property 'loggedIn' does not exist on type '{ name: string; mixins: { methods: { validateEmail(email: string): boolean; validateNotEmpty(value: string): boolean; validatePassword(value: string): boolean; validateMatchingField(current: string, newField: string): boolean; validateFutureDate(date: string): boolean; validateFutureTime(time: string): boolean; vali...'.
    177 |   },
    178 |   mounted() {
  > 179 |     if (this.loggedIn) this.$router.push({ name: "dashboard" });
        |              ^^^^^^^^
    180 |   },
    181 |   computed: {
    182 |     ...mapGetters("profile", ["loggedIn"]),

This isn't massively urgent, but it would be nice to get this up and running so we can have it on a small screen attached to a Pi or similar by the door.

As mentioned on Discord, the build issue should be fixed now. However, the kiosk mode hasn't been thought about in several years so you may find problems with it, if you do, please open a GitHub issue. 🙂

authors: jabelone proffalken

repo: membermatters/MemberMatters


text:
Path to improving extstore's defaults

Extstore shouldn't be compile gated anymore. This would simplify the code by cutting out ifdef's. There're a few things holding me back..

[x] A performance comparison, since it adds some branches to hot paths. (this can be made neutral via changes to the way add_iov() is used)
Note: changes staged in next fix this! lots of branches removed from the hot paths.
[ ] A better answer to the memory allocation hurdles.

To the second point: TL;DR: small normal items and small item HDR's take up space in the same slab classes/LRU's. Small items can't/won't be flushed to disk. This has some side effects:

workloads with mixed small/large items, with zero-expiry, will end up with low/no memory for larger items, causing aggressive flushing in extstore.
unexpiring small items can cause HDR's to be evicted when there's plenty of extstore disk space free.
The RAM-cache of large objects will shrink over time, increasing disk pressure for writes and reads.

These are non-obvious to a user and may be surprising. Hopefully this issue can be a discussion but I won't be surprised if it's just me talking to myself for a month again :)
Ideas:

Raise aggressiveness of disk flushing... People often run extstore with almost no RAM cache regardless.
Add a slab-balancer-algorithm cap for small vs large items. Default in the range of 50-90% small?
Find some way of separating the HDR's into a different LRU? We've already used up the possible four, but HOT|WARM could repurpose here.
Use LRU crawler to sort or prioritize HDR vs non-HDR objects.
The above options could be used to prioritize HDR objects when extstore has a lot of empty space. We should allow memory space to small items if extstore is like 90% full anyway.
Any other ideas? :(

Most of these requires making a decision on the importance of a small item vs a HDR item, which is impossible to do generically. For extstore's case the "most generic" we can go is ensuring some space is reserved for large objects so the system doesn't thrash; with perhaps an option allowing for "prioritize using memory to fill extstore" vs "treat all objects equally".
The fewer options/twiddles and better defaults the.. better.

Honestly after the performance fixes I'd rather just build it in by default by leave it marked experimental. Then we can incrementally improve the memory situation.

note to self: check if it would be crazy for the extstore code to issue flushes inline with the eviction code, or wake and temporarily block on the bg thread where possible.
the code is mainly tuned to "never degrade set performance" but the flush performance is generally a write to RAM anyway, so it might make a better default to at least try so long as the performance drop isn't huge.
On a quick look it might not be too bad...

The storage bg thread just loops through the slab classes and if too few free chunks exist, flushes until we're back above threshhold. It calls storage_write()
storage_write() pulls the tail item, checks if it's valid to throw out (not a HDR item, age is above item_age, etc), then alloc's a HDR item and chucks it.
normal set-with-eviction has a retry loop built in because when I re-wrote the LRU there was no longer a way of directly reusing freed memory. There is a mechanism for that now (LRU_PULL_ITEM_RETURN) which can be expanded a bit.
Caveat: storage_write() fails while the write buffer is full and flushing to disk. For a while I had multiple write buffers but the code was awful and buggy. Might need to either revisit this or figure out how to at least have two write buffers so they can be swapped.

So on the cost of slightly increasing the inline set latency we could have the BG thread try to maintain some free space, but bottoming out just force-flushes and directly reclaims memory.
This would alleviate a lot of the holes in the flushing algorithm that currently require careful tuning.

Lets put this together for a potential general simplification:

hoist the page mover logic slightly: for each chunk to be tested, move function must be called with a free chunk to swap one piece of memory into if necessary.
caller page mover thread uses item_allocish() to get the free memory. Manages if necessary: retries if chunk was within page to move, retries or sleeps if tail locked, etc.
page mover function uses this free memory to swap an item if necessary, removing the _nomem case entirely.

next:

main item_allocish() logic can flush to extstore directly if necessary.
beware of causing a looped alloc!
extstore needs multiple (at least two) wbuf's per bucket so one can be flushed to disk while another is written to.
main allocish() flushing directly covers sets as well.

then for the automove algorithm:

The only goal of the mover algorithm now is to keep the global memory pool above a desired threshold. Currently it tries to maintain the global pool + a free chunk ratio per slab class.
If it is below the threshold, pick the highest non-HDR slab class with the most memory allocated and move a page.
This may still need a special case for the highest slab class (chunked items): need enough memory to hold at least two items of -I size.
Most of the free chunk balancing code can be deleted.
BG extstore flush thread removed?

Pros:

Re-arranges the "RAM buffer" used to avoid early evictions from free slab memory chunks across N classes to the size of the extstore write buffer.
Removes the ramp-up time necessary from the background thread. (going from idle to full throttle needs a few seconds of RAM buffer)
The time to swap and flush an extstore write buffer is dependent on the speed of the storage device vs various background threads which may be asleep.
Can maybe remove the storage flush thread entirely.

Cons:

Is still, at a high level, just moving the RAM buffers around. Fast enough bursts of writes will cause evictions unless wbuf is properly sized. Sizing wbuf requires a restart!
Set time will increase, as a lot more work will be guaranteed to be done inline with sets vs currently done on BG threads.
Might have to use a wide lock while writing to a particular write buffer, else ensure items are aligned to 8 bytes within the wbuf?

The set latency could be amortized slightly by having the lru_maintainer_thread() attempt to keep a couple chunks free per high slab class. Rather than have an entire thread for the extstore flushing still.
Notes:

any remote chance wbufs could be replace with bipbuffers? I assume finding an item stored in a bipbuffer would be nontrivial.
this might make a further change to separate HDR memory from main memory cleaner.

Feel like there's still a super corner case: All memory full, burst of writes bottoms out the spare pool buffer, then extstore needs some memory to allocate headers from.
Solution is more complicated though; maybe two spare page pools. Or, past the minimum spare pool, only small/HDR objects can cause memory to pull from the global pool. That should work actually. Else there's no point to flush-on-evict without some kind of spare memory for HDR objects.

Thought/refinement... if there's a clean way to decide during a SET on a high slab class that memory is low, it could evict->flush instead of pull from slabber. That avoids pushing on the global page pool and combined with the recent slab mover changes could work pretty well.
it might even be possible to do a decent pass at this with a single extstore write buffer; if the buffer is flushing to disk fall back to slab allocator temporarily. Then multiple write buffers fixes that/etc.
Still a series of not super quick changes. I'd first go for fixing the nomem case by having the mover require a free chunk passed into it. That's one of the last really dumb corner cases I've left in the system.

More thoughts:

Since extstore headers are marked by ITEM_HDR bit and only allocated in specific places, I could use a different or novel memory allocator for them.
A lot of the SET reliability problems could be amortized by allowing sets to queue when memory fills.

To explain: If a user tries to throw the same 1mb item into cache from 1,000 clients at the same time, we need 1 gigabyte of memory for all of the data uploads, then they just get rejected one by one after the first one succeeds.
Thus, if we bottom out of memory or otherwise cap "in-flight memory buffers", the sets can be thrown into a side queue (using the same queue system we use for extstore/proxy). As memory frees we pull from that set queue and read data from sockets/etc.
With this we can reliably accept sets by blocking them until resources become available, but not hang the worker threads so they're free to handles reads or process/queue other writes.

Note:
re-summarize the top post and delete comments. Since posting this some stuff was fixed (flush aggressiveness).
Current thinking:
First step: rewire page-mover to avoid nomem case by only moving forward with free memory chunk already in hand.

also make global page pool freeratio runtime tunable

Second step: when global pool is too low, broadcast to workers to switch to immediately pushing to extstore on all high class allocations.

balancer handles moving memory back to global pool by taking from the "most pages used" high slab class. That then re-distributes to low classes.
requires double extstore write buffers so one can be flushing while we write to another.
removes extstore flush thread to free us from all of its timing/polling/throughput weirdness.

Third step: reduce extstore item_hdr memory overhead from 12 bytes to 8 (tracked in another issue)

requires a handful of internal changes

Fourth step: dedicated slabber and LRU's for item header memory.

During above cleanups the slabber is cleaned of globals and turned into an object.
If extstore is enabled we create a dedicated slabber for item headers, with the max class size being very low so classes are very close together and memory overhead is very low.
make global page pool be external to the slabber (some tertiary service) (or something like this)
allow balancing pages of memory between the slabber instances, with % caps. IE: up to 90% in small item memory and then evict from those LRU's instead.
runtime tunables for the % split.

This would hopefully be minimal tunables and solve the issue of being unable to flush tiny items to extstore because they co-exist with item headers.

repo: memcached/memcached


text:
How to specify region?

Describe the bug
I'm getting the following error
Error: Error creating Secret: googleapi: Error 400: Constraint constraints/gcp.resourceLocations violated for [orgpolicy:projects/<redacted>] attempting to create a secret in [global]. For more information, see https://cloud.google.com/resource-manager/docs/organization-policy/defining-locations.
│ Details:
│ [
│   {
│     "@type": "type.googleapis.com/google.rpc.PreconditionFailure",
│     "violations": [
│       {
│         "description": "Constraint constraints/gcp.resourceLocations violated for [orgpolicy:projects/<redacted>] attempting to create a secret in [global]. For more information, see https://cloud.google.com/resource-manager/docs/organization-policy/defining-locations.",
│         "subject": "orgpolicy:projects/<redacted>",
│         "type": "constraints/gcp.resourceLocations"
│       }
│     ]
│   }
│ ]

Environment
Please execute these commands and add the output to this issue.
terraform version
terraform providers

terraform version
Terraform v1.1.0
on windows_amd64
+ provider registry.terraform.io/hashicorp/archive v2.2.0
+ provider registry.terraform.io/hashicorp/google v3.90.1

Your version of Terraform is out of date! The latest version
is 1.1.9. You can update by downloading from https://www.terraform.io/downloads.html

terraform providers

Providers required by configuration:
.
├── provider[registry.terraform.io/hashicorp/google]
├── module.sync_contacts
│   ├── provider[registry.terraform.io/hashicorp/google]
│   └── provider[registry.terraform.io/hashicorp/archive]
├── module.sync_leads
│   ├── provider[registry.terraform.io/hashicorp/google]
│   └── provider[registry.terraform.io/hashicorp/archive]
├── module.ids_accounts
│   ├── provider[registry.terraform.io/hashicorp/google]
│   └── provider[registry.terraform.io/hashicorp/archive]
├── module.ids_contacts
│   ├── provider[registry.terraform.io/hashicorp/google]
│   └── provider[registry.terraform.io/hashicorp/archive]
├── module.ids_leads
│   ├── provider[registry.terraform.io/hashicorp/google]
│   └── provider[registry.terraform.io/hashicorp/archive]
├── module.mc-creds
│   └── provider[registry.terraform.io/hashicorp/google] >= 3.44.0
├── module.sap-creds
│   └── provider[registry.terraform.io/hashicorp/google] >= 3.44.0
└── module.sync_accounts
    ├── provider[registry.terraform.io/hashicorp/google]
    └── provider[registry.terraform.io/hashicorp/archive]

Providers required by state:

    provider[registry.terraform.io/hashicorp/google]

    provider[registry.terraform.io/hashicorp/archive]

Reproducing the issue
Try creating a secret using the default config in a project with constraints on location
module "<redacted>" {
  source               = "memes/secret-manager/google"
  version              = "1.0.5"
  project_id          = var.project
  id                      = "<redacted>-${var.stage}"
  secret                = "placeholder"
}

Additional context
How can I specify which region I want to provision the secret in? With a default config, it looks like it's using global

I tried adding
replication_locations = ["${var.location}"]

as suggested here https://registry.terraform.io/modules/memes/secret-manager/google/latest/examples/user-managed-replication
and instead get
Error: Missing required argument
│
│   with module.<redacted>.google_secret_manager_secret.secret,
│   on .terraform\modules\<redacted>\main.tf line 15, in resource "google_secret_manager_secret" "secret":
│   15:   replication {
│
│ The argument "replication.0.user_managed.0.replicas.0.customer_managed_encryption.0.kms_key_name" is required, but no definition was found.

I made this go away by manually editing my modules to remove this line from this libraries main.tf file
            customer_managed_encryption {
              kms_key_name = contains(keys(var.replication_keys), replicas.value) ? var.replication_keys[replicas.value] : null
            }

Hello @brno32  - thanks for reporting this bug. The CMEK declaration should be dynamic and conditional on a replication_keys value existing for the location. At the same time, support for global CMEK should be present too for users wanting automatic (global) replication, and use of a CMEK.

Thanks kindly! I forked and was trying to open a PR to fix it myself, but I'm brand new to terraform and couldn't figure out how to get the dynamic block right haha

Release v1.1.1 has been pushed to Terraform registry and should fix this issue. Please let me know if there are any problems.

Thanks so much

repo: memes/terraform-google-secret-manager


text:
Update volterra provider constraints

The module is currently pinned to use an old Volterra provider; update to latest and fix-up any changes.

Not stale

Not stale

repo: memes/terraform-google-volterra


text:
Extend phpDocumentor support

Extend StructurePhpdoc with @property-write and @property-read
https://www.phpdoc.org/docs/latest/references/phpdoc/tags/property-write.html
https://www.phpdoc.org/docs/latest/references/phpdoc/tags/property-read.html

Hi @ahoendgen, thanks for your feature request. I currently haven't got the time to implement it, but you're welcome to submit a Pull Request: I'd gladly review it, merge it and then tag a new release version.

Hy @gnugat
currently i´m using 2.0 due php 7.1 support so i will create this in version-2 branch when i found time for this
maybe i have the time to do some more points from your roadmap in memio/model readme (in have eyes on extract Import (use statement) from FullyQualifiedName))

That sounds great! :+1:

authors: ahoendgen gnugat

repo: memio/memio


text:
🛑 Kérwá is down

In efacb68, Kérwá (https://kerwa.ucr.ac.cr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Kérwá is back up in 76aeae3 after 8 minutes.

repo: memoemg/howyoudoing


text:
🛑 Kérwá is down

In be02c4a, Kérwá (https://kerwa.ucr.ac.cr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Kérwá is back up in 05c652e after 8 minutes.


text:
🛑 Portal de Revistas is down

In 4c24018, Portal de Revistas (https://revistas.ucr.ac.cr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Portal de Revistas is back up in 7c8837f after 8 minutes.


text:
Add MENDER_EXTRA_PARTS_SIZES_MB description

Documentation corresponding to https://github.com/mendersoftware/meta-mender/pull/1005

Hi @coreycothrum
Just the signoff missing it seems :)

Superseded by #1031.

authors: coreycothrum kacf oleorhagen

repo: mendersoftware/mender-docs


text:
Update 7.23.md with a typo-fix, and putting "we fixed" in the fixes

Expended vs Expanded
"We fixed" suggests a bug fix, which can of course be considered as an improvement, but better fits in the fixes section
A new activity type in nanoflows counts as a new feature to me

@meertens do you work for Mendix?

@Adam-Dupaski No. I work at eMagiz and am one of the Mendix experts. At eMagiz, we are usually one of the early adopters of new Mendix versions, and tend to read all the release notes. As someone who writes release notes as well, I thought you'd appreciate the feedback in this form.

@meertens I see. Thanks for the feedback, you raise some interesting questions. But besides the typo, nothing here should be changed. The "list operation" note is considered an improvement by the dev team who built that, so our policy is to go with their categorization. And for the "we fixed" improvements, these aren't fixing tickets, that's why we rely on dev team categorization and list them as improvements. The typo will be fixed. Cheers.

authors: Adam-Dupaski meertens

repo: mendix/docs


text:
Add Custom Settings to SAP Environments Runtime tab

See MCDEP-1073

@katarzyna-koltun-mx Runtime and Deployment overlap example

Approved over Slack.

authors: Adam-Dupaski MarkvanMents


text:
Update business-events.md

Better usecase

Hi @TimvanSteenbergen , thanks for the update, it is indeed clearer. I changed the wording a bit to match our style guidelines and will merge shortly.

authors: TimvanSteenbergen johannahemminger


text:
[Snyk] Upgrade @fortawesome/fontawesome-free from 6.2.0 to 6.4.2

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @fortawesome/fontawesome-free from 6.2.0 to 6.4.2.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 4 versions ahead of your current version.
The recommended version was released 2 months ago, on 2023-08-02.

Release notes

Package name: @fortawesome/fontawesome-free

6.4.2 - 2023-08-02Change log available at https://fontawesome.com/docs/changelog/

6.4.0 - 2023-03-27Change log available at https://fontawesome.com/docs/changelog/

6.3.0 - 2023-02-07Change log available at https://fontawesome.com/docs/changelog/

6.2.1 - 2022-11-15Change log available at https://fontawesome.com/docs/changelog/

6.2.0 - 2022-08-30Change log available at https://fontawesome.com/docs/changelog/

    from @fortawesome/fontawesome-free GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Builds successfully and looks OK on local build. Merging.

authors: MarkvanMents hnejra


text:
Unable to get provider com.mercadopago.android.px.internal.di.PxCheckoutInitProvider

Aplicacion HelloWorld.
Compila.
Corre en emulalor y explota con el siguiente error:
java.lang.RuntimeException: Unable to get provider com.mercadopago.android.px.internal.di.PxCheckoutInitProvider: java.lang.ClassNotFoundException: Didn't find class "com.mercadopago.android.px.internal.di.PxCheckoutInitProvider"
log:
2021-07-08 09:50:55.521 14270-14270/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.example.myapplication, PID: 14270
java.lang.RuntimeException: Unable to get provider com.mercadopago.android.px.internal.di.PxCheckoutInitProvider: java.lang.ClassNotFoundException: Didn't find class "com.mercadopago.android.px.internal.di.PxCheckoutInitProvider" on path: DexPathList[[zip file "/data/app/com.example.myapplication-XmZpYSkgC-b4-asnSe4imQ==/base.apk"],nativeLibraryDirectories=[/data/app/com.example.myapplication-XmZpYSkgC-b4-asnSe4imQ==/lib/x86, /data/app/com.example.myapplication-XmZpYSkgC-b4-asnSe4imQ==/base.apk!/lib/x86, /system/lib, /vendor/lib]]
at android.app.ActivityThread.installProvider(ActivityThread.java:6288)
at android.app.ActivityThread.installContentProviders(ActivityThread.java:5851)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5772)
at android.app.ActivityThread.-wrap1(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1661)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6541)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:767)
`import com.mercadopago.android.px.core.MercadoPagoCheckout;
public class MainActivity extends AppCompatActivity {
@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_main);
    Toolbar toolbar = findViewById(R.id.toolbar);
    setSupportActionBar(toolbar);

    FloatingActionButton fab = findViewById(R.id.fab);
    fab.setOnClickListener(new View.OnClickListener() {
        @Override
        public void onClick(View view) {

            new MercadoPagoCheckout.Builder("xxxxxxxxxxxxxxxxxxxxxxx", "yyyyyyyyyyyyyyyyyyyy")
                    .build()
                    .startPayment(MainActivity.this , 123);
        }
    });
}

`

11 dias

repo: mercadopago/px-android


text:
resolve snrefs for child items

for issue #368, current solution is to resolve snrefs based on current variant context before trying to access it. To get the correct result, the snrefs of child items  should be resolved when calling its parent's _resolve_snrefs. So I add code to do the work for some missing items

 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.

repo: mercedes-benz/odxtools


text:
"upcoming"

The word "upcoming" appears multiple times. is misspelled

corrected on dashboard

repo: mercerbe/SocialRent


text:
miot CLI works at most time, but sometime failed with ERROR  user ack timeout.

  miot CLI works at most time, but sometime failed with `ERROR  user ack timeout`.

I execute 4 commands in one shot: turn off, get status, turn on, get status.
Compared with miot and miiocli, miiocli almost never failed, but miot almost failed at the third command every time.
miot send $GATEWAY_IP --token $GATEWAY_TOKEN set_properties "[{\"did\":\"$DEVICE_ID\",\"value\":false,\"siid\":2,\"piid\":1}]"
miot send $GATEWAY_IP --token $GATEWAY_TOKEN get_properties "[{\"did\":\"$DEVICE_ID\",\"siid\":2,\"piid\":1}]"
miot send $GATEWAY_IP --token $GATEWAY_TOKEN set_properties "[{\"did\":\"$DEVICE_ID\",\"value\":true,\"siid\":2,\"piid\":1}]"
miot send $GATEWAY_IP --token $GATEWAY_TOKEN get_properties "[{\"did\":\"$DEVICE_ID\",\"siid\":2,\"piid\":1}]"

# Output
 INFO  Connecting to device at  192.168.x.x
 INFO  Device found! Sending command: set_properties [{"did":"xxx","value":false,"siid":2,"piid":1}]
(Protocol) Call 192.168.x.x: set_properties - [{"did":"xxx","value":false,"siid":2,"piid":1}] - {"retries":1,"timeout":5000}
 SUCCESS  Response from device -> [{"did":"xxx","siid":2,"piid":1,"code":1,"ts":1665230823,"ret":0}]
 INFO  Connecting to device at  192.168.x.x
 INFO  Device found! Sending command: get_properties [{"did":"xxx","siid":2,"piid":1}]
(Protocol) Call 192.168.x.x: get_properties - [{"did":"xxx","siid":2,"piid":1}] - {"retries":1,"timeout":5000}
 SUCCESS  Response from device -> [{"did":"xxx","siid":2,"piid":1,"value":false,"code":0,"ts":1665230827,"ret":0}]
 INFO  Connecting to device at  192.168.x.x
 INFO  Device found! Sending command: set_properties [{"did":"xxx","value":true,"siid":2,"piid":1}]
(Protocol) Call 192.168.x.x: set_properties - [{"did":"xxx","value":true,"siid":2,"piid":1}] - {"retries":1,"timeout":5000}
 ERROR  user ack timeout
 INFO  Connecting to device at  192.168.x.x
 INFO  Device found! Sending command: get_properties [{"did":"xxx","siid":2,"piid":1}]
(Protocol) Call 192.168.x.x: get_properties - [{"did":"xxx","siid":2,"piid":1}] - {"retries":1,"timeout":5000}
 SUCCESS  Response from device -> [{"did":"xxx","siid":2,"piid":1,"value":false,"code":0,"ts":1665230831,"ret":0}]

And I switch the first and the third command, still failed at the third command.
Update:
I see miiocli's retry_count=3, timeout=5, so I add --retries 3 for miot, still failed.
Here's the data captured from wireshark:
miiocli:
--> {"id": 2, "method": "get_properties", "params": [{"did": "1044213155", "siid": 2, "piid": 1}]}
<-- {"id":2,"error":{"code":-9999,"message":"user ack timeout"},"exe_time":4004}
--> {"id": 3, "method": "get_properties", "params": [{"did": "1044213155", "siid": 2, "piid": 1}]}
<-- {"id":3,"result":[{"did":"1044213155","siid":2,"piid":1,"value":false,"code":0,"ts":1665232063,"ret":0}],"exe_time":12}

miot:
--> {"method":"set_properties","params":[{"did":"1044213155","value":true,"siid":2,"piid":1}],"id":1}
<-- {"id":1,"error":{"code":-9999,"message":"user ack timeout"},"exe_time":4005}

Seems miot retry not correctly working.
Originally posted by @0x5e in https://github.com/merdok/homebridge-miot/discussions/348#discussioncomment-3828503

@0x5e
do you have any tips on how to cause the "user ack timeout"? I cannot trigger them on any of my devices, and having them to trigger would make it easier to debug this issue.

@0x5e
do you have any tips on how to cause the "user ack timeout"? I cannot trigger them on any of my devices, and having them to trigger would make it easier to debug this issue.

If I send command to the mesh device too frequently, It will cause this error. For example, copy 4 commands together and paste to the shell, and enter, then usually failed at the third command...

The thing is that I do not have any mesh devices😅
So I need a reliable way to reproduce it without that.
Other then that, if you have coding knowledge and time, could you try to have a look? The code should be in the protocol file.

OK, just give me some time to read the code, I will try.

thanks 👍

repo: merdok/homebridge-miot


text:
mescroll-uni 上下反复滚动 scrollTop直接变为0

1.3.7

touchendEvent  获取的滚动条me.getScrollTop()高度为0  暂时改成了ins.$vm.wxsProp.scrollTop
暂不知原因

repo: mescroll/mescroll


text:
Changed cloud native catalog logo color

Signed-off-by: Rohith Raju rohithraju488@gmail.com
Description
Changed the logo color back to charcoal
This PR fixes #
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

@leecalcote a quick one 😄


text:
[Docs] Compatibility Matrix: Proper sorting by Kubernetes versions (descending)

Current State
The Kubernetes version column is not sorting correctly on the Compatibility Matrix page.

Desired State
The compatibility table should be sorted in descending order of Kubernetes version #.

Contributor Guides and Handbook

📚 Instructions for contributing to documentation

Meshery documentation site and source

🛠 Meshery Build & Release Strategy
🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Hello @lee I think I know how to fix this

I guess we can try it with the sort_by filter instead of group_by.  The sort_by filter will sort the items in a collection based on a specified key.

I guess we can try it with the sort_by filter instead of group_by. The sort_by filter will sort the items in a collection based on a specified key.

Here's the PR associated these changes #6923

authors: Abiey2579 leecalcote rudrakshkarpe

repo: meshery/meshery


text:
[mesheryctl] Fixing docker/k8s conflict incase of platform docker

Signed-off-by: Piyush Singariya piyushsingariya@gmail.com
Description
This PR marks checks on kubernetes in case of platform docker for mesheryctl system update
This PR fixes #
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Codecov Report

Merging #3490 (1beaa99) into master (9ca8378) will decrease coverage by 1.81%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #3490      +/-   ##
==========================================
- Coverage   12.33%   10.51%   -1.82%
==========================================
  Files          37       37
  Lines        3186     3194       +8
==========================================
- Hits          393      336      -57
- Misses       2710     2791      +81
+ Partials       83       67      -16

Flag
Coverage Δ

gointegrationtests
?

unittests
10.51% <0.00%> (-0.03%)
:arrow_down:

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

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/system/update.go
1.13% <0.00%> (-0.12%)
:arrow_down:

mesheryctl/internal/cli/root/system/check.go
1.49% <0.00%> (-21.35%)
:arrow_down:

Continue to review full report at Codecov.

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

authors: codecov-commenter piyushsingariya


text:
[GraphQL] Added Token to Req context

Signed-off-by: dhruv0000 patel.4@iitj.ac.in
Description
GraphQL resolvers should reuse the methods defined in provider interface. To do that, they need access to the token. This PR:

Addes the token to the req context (which resolver and handler both can access).
Updates GetResults method of provider interface as an example on how to make the methods generic for GraphQL to use.

Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

@bariqhibat ^^

In context of the Making GraphQL Solid plan, where does this land us?

In context of the Making GraphQL Solid plan, where does this land us?

On track. The Provider interface needs to become more generic in order for it to be used by both resolvers and handlers. This is just an example on how to do it.


text:
Fix the incorrect link

Notes for Reviewers
This PR fixes #7125
Fixed the incorrect link
Signed commits

[x] Yes, I signed my commits.

🚀 Preview for commit 2a2ca4af5a6f4bd58f22103d62e997fe3424d87d at: https://63f3da1499219333179d4beb--meshery-docs-preview.netlify.app


text:
Filter Package Error Wrappers

Notes for Reviewers
This PR fixes #8204
About
Creating Error Wrappers and implementing them in different filter code files when returning error messages , using Meshkit errors Syntax
Signed commits

[x] Yes, I signed my commits.

Please do make sure that short Description, Long Description, Probable Cause and Remediation all are filled. And also return the probable cause and Remediation for error. Also my suggestion would start error codes from 3000 so there isn't any duplicacy

Alright, should probable cause not contain the error message itself , like i mean err.Error()

@abdullah1308 , @suhail34 , @leecalcote
From these commits i made today ,I decided to create a new package ctlerrors mesheryctl/internal/cli/root/ctlerrors/errors.go  that will be used for defining error functions or wrappers that will be called within different mesheryctl files and packages for returning errors , I didn't succeed calling them from the root package
mesheryctl/internal/cli/root/errors.go  which is the parent package and its against golang's rule for package import .
So the remaining files  which i pushed , i just redefined and called the ctlerrors for each specific function when returning an error

@Philip-21  Let's discuss this on the Meshery Dev call. Please add this as an agenda item in the meeting minutes if you would. :)

changes will still have to be made before merging

Final review pending https://github.com/meshery/meshery/pull/8238

Merge conflict.

Please resolve all comments that have been addressed (with info on how they were addressed), @Philip-21

Please resolve all comments that have been addressed (with info on how they were addressed), @Philip-21

@leecalcote do you mean i should add additional info to the error functions ?

@leecalcote adjustments have been made, i have sorted out the conflicts

🚀 Preview for commit 160ca8eec6ad90e38c039a86a1d07564ce7fd5bf at: https://64e75f5430c27908e81d8998--meshery-docs-preview.netlify.app

🚀 Preview for commit 0f06e238b4b8a88d57639f2bd2a6ec2c17ed1218 at: https://64e767549bd1710f243f896c--meshery-docs-preview.netlify.app

Too many conflicts


text:
Handling executables (scripts from the Python POV) that link to distribution libraries

I don't think auditwheel fixes the binary dependencies for wheel scripts, we should confirm that. If it does not, we should put them in platlib and add a wrapper that just calls them in the scripts directory.
The issue here is that we do not know the final location of the .libs folder so we cannot set the path to point there. By placing them in platlib, we can set the rpath to $ORIGIN/../.libs.

The issue here is that we do not know the final location of the .libs folder

Why isn't it staying at pkgname/.libs (every package I'm aware of has it there, and I thought it was an auditwheel thing - but could be multibuild doing it)? Or do you need an absolute path somewhere?

Yes, but we need to set the rpath of the binary to path of the .libs folder, which we do not know.  It would be either absolute, which we do not know, or relative (using $ORIGIN), which we also not know if we place the binary in the scripts folder.

Or does auditwheel relocate the binary itself? This is what I need to check, and the reason for this issue. I was under the impression it didn't, but am not sure.

I haven't had much time to look into this so I just put my thoughts down here for future reference.

Or does auditwheel relocate the binary itself?

I thought it did, but I'm not 100% sure.

So, auditwheel does try to do something, but it's incorrect.
$ cd tests/packages/library
$ python -m build -nxw
* Building wheel...
! Using Meson to generate the project metadata (no `project` section in pyproject.toml)
+ meson setup --prefix=/usr /home/anubis/git/mesonpy/tests/packages/library /tmp/mesonpy-8ucf00vy/build
The Meson build system
Version: 0.59.99
Source dir: /home/anubis/git/mesonpy/tests/packages/library
Build dir: /tmp/mesonpy-8ucf00vy/build
Build type: native build
Project name: library
Project version: 1.0.0
C compiler for the host machine: ccache cc (gcc 11.1.0 "cc (GCC) 11.1.0")
C linker for the host machine: cc ld.bfd 2.36.1
Host machine cpu family: x86_64
Host machine cpu: x86_64
Build targets in project: 2

Found ninja-1.10.2 at /usr/bin/ninja
+ meson compile
[5/5] Linking target example
+ meson install --destdir /tmp/mesonpy-8ucf00vy/build
ninja: Entering directory `/tmp/mesonpy-8ucf00vy/build'
ninja: no work to do.
Installing libexample.so to /tmp/mesonpy-8ucf00vy/build/usr/lib
Installing example to /tmp/mesonpy-8ucf00vy/build/usr/bin
WARNING File could not be mapped to an equivalent wheel directory: /tmp/mesonpy-8ucf00vy/build/usr/lib/libexample.so ({libdir_shared}/libexample.so)
+ auditwheel repair -w /tmp/mesonpy-8ucf00vy/build/auditwheel-output /tmp/mesonpy-8ucf00vy/build/library-1.0.0-py3-none-linux_x86_64.whl
INFO:auditwheel.main_repair:Repairing library-1.0.0-py3-none-linux_x86_64.whl
INFO:auditwheel.wheeltools:Previous filename tags: linux_x86_64
INFO:auditwheel.wheeltools:New filename tags: manylinux_2_5_x86_64, manylinux1_x86_64
INFO:auditwheel.wheeltools:Previous WHEEL info tags: py3-none-linux_x86_64
INFO:auditwheel.wheeltools:New WHEEL info tags: py3-none-manylinux_2_5_x86_64, py3-none-manylinux1_x86_64
INFO:auditwheel.main_repair:
Fixed-up wheel written to /tmp/mesonpy-8ucf00vy/build/auditwheel-output/library-1.0.0-py3-none-manylinux_2_5_x86_64.manylinux1_x86_64.whl
Successfully built library-1.0.0-py3-none-manylinux_2_5_x86_64.manylinux1_x86_64.whl
$ unzip dist/*.whl -d wheel-contents
Archive:  dist/library-1.0.0-py3-none-manylinux_2_5_x86_64.manylinux1_x86_64.whl
   creating: wheel-contents/library.libs/
   creating: wheel-contents/library-1.0.0.data/
   creating: wheel-contents/library-1.0.0.dist-info/
  inflating: wheel-contents/library.libs/libexample-d5767f33.so
   creating: wheel-contents/library-1.0.0.data/scripts/
  inflating: wheel-contents/library-1.0.0.data/scripts/example
  inflating: wheel-contents/library-1.0.0.dist-info/RECORD
  inflating: wheel-contents/library-1.0.0.dist-info/WHEEL
  inflating: wheel-contents/library-1.0.0.dist-info/METADATA

$ readelf -d wheel-contents/library-1.0.0.data/scripts/example

Dynamic section at offset 0x6000 contains 28 entries:
  Tag        Type                         Name/Value
 0x000000000000000f (RPATH)              Library rpath: [$ORIGIN/:$ORIGIN/../../library.libs]
 0x0000000000000001 (NEEDED)             Shared library: [libexample-d5767f33.so]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
 0x000000000000000c (INIT)               0x1000
 0x000000000000000d (FINI)               0x11f8
 0x0000000000000019 (INIT_ARRAY)         0x3dc8
 0x000000000000001b (INIT_ARRAYSZ)       8 (bytes)
 0x000000000000001a (FINI_ARRAY)         0x3dd0
 0x000000000000001c (FINI_ARRAYSZ)       8 (bytes)
 0x000000006ffffef5 (GNU_HASH)           0x5178
 0x0000000000000005 (STRTAB)             0x6210
 0x0000000000000006 (SYMTAB)             0x50b8
 0x000000000000000a (STRSZ)              218 (bytes)
 0x000000000000000b (SYMENT)             24 (bytes)
 0x0000000000000015 (DEBUG)              0x0
 0x0000000000000003 (PLTGOT)             0x4000
 0x0000000000000002 (PLTRELSZ)           48 (bytes)
 0x0000000000000014 (PLTREL)             RELA
 0x0000000000000017 (JMPREL)             0x630
 0x0000000000000007 (RELA)               0x570
 0x0000000000000008 (RELASZ)             192 (bytes)
 0x0000000000000009 (RELAENT)            24 (bytes)
 0x000000006ffffffb (FLAGS_1)            Flags: PIE
 0x000000006ffffffe (VERNEED)            0x550
 0x000000006fffffff (VERNEEDNUM)         1
 0x000000006ffffff0 (VERSYM)             0x540
 0x000000006ffffff9 (RELACOUNT)          3
 0x0000000000000000 (NULL)               0x0

Ad you can see, the rpath is set to $ORIGIN/:$ORIGIN/../../library.libs, which is incorrect. There's no guarantee the library will be at $ORIGIN/../../library.libs ($ORIGIN here being the location of the binary itself), in fact, that does not even happen under a normal Python installation on Linux. The executable will go to /usr/bin/example, so the rpath points to /usr/library.libs.

We're no longer using auditwheel, and this issue isn't really a bug - more something very low prio that isn't supported right now. I am removing the "bug" label. Let's wait with doing anything here until a real-world use case comes along.

In case someone needs this - there's at least two ways of handling this scenario right now:

Statically linking libraries built within the project itself
Installing a thin .py wrapper script to the scripts directory and installing the actual executable in site-packages (where it can reliably use RPATHs)

repo: mesonbuild/meson-python


text:
Logstash framework uses 8080 port (file server)

https://github.com/mesos/logstash/blob/master/logstash-scheduler/src/main/java/org/apache/mesos/logstash/config/FrameworkConfig.java#L37
we are running logstash without docker on mesos+marathon.
when mesos tries to start logstash framework on any host, which has marathon running - logstash fails, because it tries to use 8080 port, which is already taken (by marathon).
example: marathons tells that logstash framework is running on 6053 port of slave-07:
[cloud-user@slave-07 ~]$ curl master-01:8080/v2/apps/logstash/ | jq .app.tasks
[
  {
    "id": "logstash.1f57736f-eaab-11e5-9fe4-0242cccd6336",
    "host": "slave-07.test.com",
    "ports": [
      6053
    ],

but there is nothing there:
[cloud-user@slave-07 ~]$ sudo netstat -tuplan | grep 6053
[cloud-user@slave-07 ~]$

while logstash framework is running on 8080 port.
[cloud-user@slave-07 ~]$ sudo netstat -tuplan | grep 8080
tcp6       0      0 :::8080                 :::*                    LISTEN      7620/java
[cloud-user@slave-07 ~]$ sudo ps waxu | grep 7620
root      7620  2.3  3.4 9247916 731364 ?      Ssl  12:40   0:14 java -jar logstash-mesos-scheduler.jar

Hi @AndriiOmelianenko. Thanks for pointing this out. Obviously the port should be configurable. Which it sort of is, except that executors won't obey it.
A quick fix would be to run the scheduler in Docker. (Or move Marathon to a different port…)
I will look into it as soon as possible.

@AndriiOmelianenko Do you want to try this PR to see if it solves your problem? You can now change the port with --server.port=n command line parameter or SERVER_PORT=n environment variable.

@mwl thanks.
Do you expect this to go to 0.10 release?

Yes

authors: AndriiOmelianenko mwl

repo: mesos/logstash


text:
Release v0.0.1

This PR introduces tagged semantic versioned releases and a CHANGELOG. Once the PR is merged, I'll tag the commit with two tags:

v0.0.1: mesos-go semantic version
mesos-0.24.0: mesos version compatibility

Fixes #167

@sttts: Made it clear that we support also support Mesos 0.23.0 in the CHANGELOG. I'll also find the place in the git history where we started supporting Mesos 0.23.0 and tag it accordingly.

To make it clear: Documentation of Mesos version support deprecation shall be done via the CHANGELOG.

lgtm

authors: sttts tsenart

repo: mesos/mesos-go


text:
gracefully handle master failover

fixes here include:

messenger does not abort upon transport errors
scheduler and executor observe network errors as indicators of disconnection
additional debugging flag for example scheduler
removed separate go-routine for message encoding
context.Context from sender (sched/exec driver) is preserved down to the transport level

fixes #155
fixes #160

connected to #155
connected to #160

mesos devs have confirmed that socket errors between executor and slave indicate "slave not running". this isn't bulletproof, especially if executor runs out of FDs. but it's how the native impl works


text:
WIP establish regular molecule tests

What problem does this PR solve?:
Currently only basic testing is done against a full image build. But changes in ansible are not covered by tests. This actually lead to customer facing issue.
Molecule was in a quite unmaintained state. To improve code quality its important to establish a test driven approach making changes to the ansible code in KIB.
This PR will establish automated molecule testing for all supported OSes by using AWS instances for testing.
We'll not cover provider specific code but focus on the supported Distributions
Action items:

[x] make sure ansible ( without the sysprep step ) is idempotent so while developing new features ansible could be run over and over again
[ ] ensure molecule works from within the devkit container
[ ] establish private AWS GH runner for this repository
[ ] add github actions to run the molecule suite whenever there are changes in /ansible
[ ] add github action to run special GPU related tests whenever the /ansible/roles/gpu has changes

Which issue(s) does this PR fix?:

no jira
Special notes for your reviewer:
This is branched off my latest changes about cloud-init due to those changes adding a molecule test.
Does this PR introduce a user-facing change?:

Hey @supershal @faiq I've took another look into this PR and rebased it.
It adds regular molecule test to improve ansible code quality as molecule does not only testing the run results but also doing linting of ansible.

repo: mesosphere/konvoy-image-builder


text:
network/cni support

The upcoming mesos 1.0.0 adds the network/cni isolator, see http://mesos.apache.org/documentation/cni/.
To support this, marathon have to manage the NetworkInfo.name , which is the cni network name.
a state from a mesos-agent running a mesos container with cni isolator
[...]
          "statuses": [
              {
                "state": "TASK_RUNNING",
                "timestamp": 1465547659.73453,
                "container_status": {
                  "network_infos": [
                    {
                      "ip_addresses": [
                        {
                          "protocol": "IPv4",
                          "ip_address": "10.135.10.2"
                        }
                      ],
                      "name": "mynet"
                    }
                  ]
                }
              }
            ],
            "container": {
              "type": "MESOS",
              "mesos": {
                "image": {
                  "type": "DOCKER",
                  "docker": {
                    "name": "debian:latest"
                  },
                  "cached": true
                }
              },
              "network_infos": [
                {
                  "name": "mynet"
                }
              ]
            }
          }
[...]

For the health checks, the state provide the container IP.
Does the network name should be part of the portsDefinition, merged with ip-per-task, ... ?
Does the heath check needs some rewrite for using this ip_address ?
I'd like to contribute but need some guidelines to be efficient.

fixed by #3974

repo: mesosphere/marathon