text:
Health check race condition fix

/claim #773
Health Check System Improvements
Summary of Changes

Enhanced useHealthCheck hook with debounced functionality and proper cleanup
Added loading states for dialog operations
Improved error handling and type safety
Implemented proper event handling for settings updates
Added request cancellation for stale health checks

Key Files Modified

lib/hooks/use-health-check.tsx
components/screenpipe-status.tsx
components/settings.tsx

Purpose
Address intermittent button functionality issues and improve reliability of health check system by:

Preventing race conditions in health status polling
Adding proper request cancellation
Implementing debounced health checks for performance
Separating concerns between health checks and UI operations
Improving error handling and user feedback

Implementation Details
Health Check Hook Improvements
export function useHealthCheck(): HealthCheckHook {
  // Added proper type definitions
  // Implemented abort controller for request cancellation
  // Added debounced fetch functionality
  // Improved error handling with type guards
}

Loading State Management

Separated health check loading from UI operation loading
Added visual feedback during loading states
Implemented proper cleanup to prevent memory leaks

Settings Integration

Added event-based communication for settings updates
Implemented debounced health checks to prevent unnecessary API calls
Improved type safety with proper interfaces

Technical Rationale

Request Cancellation: Used AbortController to prevent stale requests from affecting UI state
Debouncing: Implemented to reduce server load during rapid state changes
Type Safety: Added proper interfaces and type guards to catch potential issues at compile time
State Management: Separated concerns between health checks and UI operations for better maintainability
Event System: Used custom events for better decoupling between components

how to reproduce error and test? @screwyforcepush

does not fix the issue, still cant click things

not sure what this PR is doing/solving

@louis030195 When I was trying to debug the UI elements not working. I noticed some console errors in the logs that came from server request failing. Turns out there was a race condition in the code. It may not help the UI elements not work but I thought to fix it anyway for stability.

@screwyforcepush can you solve coflict and will merge

@screwyforcepush can you solve coflict and will merge

bump

repo: mediar-ai/screenpipe


text:
Add empty selector validation

We allow control plane fencing now, but strongly discourage using the same NHC config for control plane and worker nodes. On the other hand we allow the node selector to be empty, which results in selecting ALL nodes. That does not make sense. So disallow empty selectors.
For backwards compatibilty, we will still process existing NHCs with empty selectors
ECOPROJECT-1220

/retest

/retest

/retest

/retest

/lgtm
Giving a chance to get more feedbacks, feel free to unhold
/hold

/hold cancel
/retest

source: gharchive/pull-request

authors: clobrano slintes

license_type: permissive

license_source: github-api


text:
Problem displaying "similarity" attribute from QuickUMLS in DocConsumer

DocConsumer for some reason does not display the "similarity" attribute correctly when added to the ent attributes.  The attached screen shot shows a doc from which I can print the QuickUMLS attributes directly, but when run through DocConsumer, all the attributes except "similarity" print correctly.  The error suggests an expectation that "similarity" is a function instead of the float that the attribute is in actuality.

I think the reason for this is that the way the DocConsumer works is it first checks if there is a native spaCy attribute with the specified name, and if there isn't it looks for a custom attribute. In this case, ent.similarity is already defined by spaCy as a method, so that's what the DocConsumer grabs and puts here.
I think the simplest solution would be to give your attribute a different name which is distinct from spaCy's native attributes, something like ent._.span_similarity

@abchapman93 I believe this similarity is a part of QuickUMLS. It’s the similarity of the match compared to the text of the CUI. So it was an oversight on our part to not rename the attribute when we updated/added QuickUMLS

Ah, I see. Well since QuickUMLS is kind of a third-party library, I still think the simplest solution would be to register a new attribute that just returns this value, something like:
from spacy.tokens import Span; Span.set_extension("quickumls_similarity", getter=lambda x:x._.similarity)

source: gharchive/issue

authors: RonWilkinson abchapman93 turbosheep

repo: medspacy/medspacy

license: MIT


text:
Deploy NextJs Storefront using Docker Run

Hello folks,
The  Nextjs uses SSG for most pages and we need a backend server running in build time. So how we can build an image and can use it in both development and production environments. They have different backend server URL  and we only know about the backend server at run time, when we run docker run -e NEXT_PUBLIC_MEDUSA_BACKEND_URL=backend-dev.host.com or docker run -e NEXT_PUBLIC_MEDUSA_BACKEND_URL=backend-prod.host.com

Link in Discord channel: https://discord.com/channels/876835651130097704/1106152560143900724

Hi @quang-ng,
We don't use Docker ourselves and can't offer you support on this question. Hope you will be able to figure it out, but I will close the issue, as it is outside the scope of this project.

bad response :(

repo: medusajs/nextjs-starter-medusa


text:
Reorder

Not sure if this has been done but is there a feature for reordering a jobs individual components. EG. Tell it to engrave first then cut then do a raster... Also, can you merge 2 different engrave jobs, I simulated a design with an image to engrave and text to engrave (same settings but did the image completely then went back to the start to do the text)
Thanks

Yes. That feature already exists to reorder individual jobs or components. Just drag the operation (Raster, Image, Engrave, or Cut) up or down. Might make it easier if you collapse the drop-down triangles as you do those drag moves.
Not really sure what you mean about merging 2 different engrave jobs. You have have more than one engrave job in the same file. They can be made to run back to back which is exactly how it would function if you combined them. Alternatively; you could simply set those lines to the same color and they would open as a "combined" object when the file is loaded in MeerK40t.
Or did you mean load two files at the same time? That does work as well.

Hi, thanks for fast reply. I'm still getting used to this software, I've
used another piece for years so have some habits from that one... I've just
worked out the reordering. I was trying to do it from the job list pop up
box. Thanks
Also, I've just worked out what I was doing wrong with the jobs not doing
all of the details at once. Sorry for mithering. I learn best by messing
with stuff but after 2 hours gave up 😅😅 thanks for your help
On Thu, 24 Dec 2020, 13:43 Joseph Lane, notifications@github.com wrote:

Yes. That feature already exists to reorder individual jobs or components.
Just drag the operation (Raster, Image, Engrave, or Cut) up or down. Might
make it easier if you collapse the drop-down triangles as you do those drag
moves.
Not really sure what you mean about merging 2 different engrave jobs. You
have have more than one engrave job in the same file. They can be made to
run back to back which is exactly how it would function if you combined
them. Alternatively; you could simply set those lines to the same color and
they would open as a "combined" object when the file is loaded in MeerK40t.
Or did you mean load two files at the same time? That does work as well.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/meerk40t/meerk40t/issues/280#issuecomment-750886947,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASIDTCPBEJE4AOIN6JGW4ELSWNARNANCNFSM4VIGJT3A
.

It's not a bad idea though, if the settings between the two engrave operations are the same I don't see any trouble with moving everything from the one operation into the other operation. That stuff does, at some point, need an upgrade especially with regards to grouping objects together and moving multiple objects at the same time, or groups at the same time.  It wouldn't be too weird to do it that way. Or make trying to combine them like that create an arbitrary group with the operations as the leaf-nodes. I mean it would be into the 0.7.x series but certainly there's a few actions you could see with dragging operations into other operations that would make some logical sense.

😀 glad I've got you thinking 🤔 😂
On Thu, 24 Dec 2020, 17:34 David Olsen, notifications@github.com wrote:

It's not a bad idea though, if the settings between the two engrave
operations are the same I don't see any trouble with moving everything from
the one operation into the other operation. That stuff does, at some point,
need an upgrade especially with regards to grouping objects together and
moving multiple objects at the same time, or groups at the same time. It
wouldn't be too weird to do it that way. Or make trying to combine them
like that create an arbitrary group with the operations as the leaf-nodes.
I mean it would be into the 0.7.x series but certainly there's a few
actions you could see with dragging operations into other operations that
would make some logical sense.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/meerk40t/meerk40t/issues/280#issuecomment-750932779,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASIDTCNEI6VJNLQ4DBGOVJDSWN3RRANCNFSM4VIGJT3A
.


text:
Feature Request : Operations menu

The Operations menu is messy, and long, and only about half of it is really needed.
Suggestions:

Add a "Collapse All" option to shrink the list for moving operations around easier
Start with files and elements collapsed
Keep things collapsed after they are moved
Add a "group" option that will AUTOMATICALLY group things by functions, put all of the Raster stuff together, then the engraving, and finally the cut operations.
Option to have the menu start collapsed

The tree stuff is being worked on currently, since it suffers a series of defects. You're scratching the surface with your list. The work in 0.7.0 is mostly focused on making it dynamic and allowing grouping. So in theory if you load a file it will just modify the tree rather than needing to rebuild the whole thing, and allow it to build the icons dynamically in their own threads because that stuff is slow and causes serious optimization issues.

You can collapse that, you just can't tell. Click on it and hit the left arrow on your keyboard. Though any change to the tree will make it expand all again.
Files is going to be deprecated. They will be a custom group around elements. So elements -> file -> paths and you could easily access the sub elements.
Collapsing isn't something the current tree does well, collapsing things is damned near pointless since they will automatically expand again the next thing you tweak.
Grouping stuff is a primary need and part of the reason for the rewrite. There's also functional needs for grouping within the cutplanning. Grouping is also needed to move objects as groups. So if the object is a single thing it shouldn't all need selecting. It should select correctly.
Staying collapsed works, starting collapsed might not be useful except for some options like templates (groups of operations that should be switched on fly for different materials etc). It might be worthwhile to save whether the particular operations should be collapsed, but not as part of the startup, but rather as part of the saved file.

All good stuff...
#3, not staying collapsed... a bother, as I was trying to group things so
as to not have a cut in the middle, and it was a pain every time i did
something it insisted on expanding the {unrepeatable} list...  if a user
collapses it, it should STAY collapsed  until they expand it.
my $.02 anyway...
On Tue, Feb 9, 2021 at 5:49 PM tatarize notifications@github.com wrote:

The tree stuff is being worked on currently, since it suffers a series of
defects. You're scratching the surface with your list. The work in 0.7.0 is
mostly focused on making it dynamic and allowing grouping. So in theory if
you load a file it will just modify the tree rather than needing to rebuild
the whole thing, and allow it to build the icons dynamically in their own
threads because that stuff is slow and causes serious optimization issues.

You can collapse that, you just can't tell. Click on it and hit the
left arrow on your keyboard. Though any change to the tree will make it
expand all again.
Files is going to be deprecated. They will be a custom group around
elements. So elements -> file -> paths and you could easily access the sub
elements.
Collapsing isn't something the current tree does well, collapsing
things is damned near pointless since they will automatically expand again
the next thing you tweak.
Grouping stuff is a primary need and part of the reason for the
rewrite. There's also functional needs for grouping within the cutplanning.
Grouping is also needed to move objects as groups. So if the object is a
single thing it shouldn't all need selecting. It should select correctly.
Staying collapsed works, starting collapsed might not be useful
except for some options like templates (groups of operations that should be
switched on fly for different materials etc). It might be worthwhile to
save whether the particular operations should be collapsed, but not as part
of the startup, but rather as part of the saved file.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/meerk40t/meerk40t/issues/354#issuecomment-776296599,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFJ2GY4FFQNL2IJI6CI4CFTS6G3WVANCNFSM4XLZOYEA
.

--
Need a quick answer? Call our booking line at (301) 208-8289, or book your
inspection on our website 24/7.
Don't wait for a response as someone else may get the spot you want... call
Today!
Bob Sisson, ACI, BVI
Inspections by Bob, LLC
www.inspectionsbybob.com
bob@inspectionsbybob.com
MD Lic#29666; ASHI Member #212016

Tree stuff got finished.

authors: inspectionsbybob tatarize


text:
Impractical size divisions on "dynamic rulers"

See screenshot:

Seems like it would be more logical to have marks at rounded numbers (ie every x mm/cm)

Okay, fixed. And it doesn't interfere with anything so I'll be able to push it to the master branch in short order.

This is now live in 0.1.5

authors: dietervansteenwegen tatarize


text:
[NO-ISSUE] refactor/adapt update js client

Changed

Updated dependencies of the client lib
Switched from npm to pnpm
Removed usages of !

CI is failing because I've enabled it, but both are fixed in https://github.com/meetsmore/nittei/pull/9 and in https://github.com/meetsmore/nittei/pull/11. So no problem 👍

repo: meetsmore/nittei


text:
A Chinese version for README

Hi @xxx7xxxx, I noticed that you've already provided a very detailed and thoughtful README. May I contribute a Chinese version?

Sure, all contributions we will welcom

Thanks for your kind reply @zhao-kun , but I didn't notice that the Chinese version has already been provided in the content... Maybe I can contribute some translation for docs/*.md .

Thanks for your contribution, your PR has been merged.

authors: C-ld xxx7xxxx zhao-kun

repo: megaease/easemesh


text:
reconstructions default to input datasets scale

The output dataset's scale is wrong as it is read from the input here
Should the zyx scale be taken from the config file instead? Specifically, in the case of falcon datasets, the bug arises from here.

The easier fix is to update-scale-metadata before starting any processing.

Closely related to #457.
Our plan is to use the input dataset's scale metadata by default, and use the config file's metadata to override the input's scale metadata.
@edyoshikun will that design work for your use case?

authors: edyoshikun talonchandler

repo: mehta-lab/recOrder


text:
Example script saves to a single zarr

Fixes #296

This PR combines changes to the example scripts with changes to the CLI. I haven't tested the CLI changes yet.

My fault! Fixed now.


text:
Improve Test Logging by Removing a Noisy Message

Pull Request
What does this PR do?
Fixes #140

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

[x] Does this PR fix an existing issue?
[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!

@michael-rodriguez22 Thanks for your contribution! ❤
It is awesome to hear that is your first time contributing to open-source, and it is amazing to see that you choose us to start! Thanks a lot!

Hey, @michael-rodriguez22 do you have any questions about this? Can I help you with something?

I'm closing this PR since it should fix the conflicts now... Also, it should fix the linter issues, feel free to reopen!

repo: meilisearch/meilisearch-dart


text:
Remove the sync feature and use Arc everywhere by default

Pull Request
What does this PR do?
Fixes #250
PR checklist
Please check if your PR fulfills the following requirements:

[x] Does this PR fix an existing issue?
[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!

bors try

@irevoire, not an emergency but looks like there is an issue with the wasm-build CI

I rebased + fixed everything 👍

@bidoubiwa you can merge

authors: curquiza irevoire

repo: meilisearch/meilisearch-rust


text:
v0.28.0rc0 Cannot create tenant tokens with custom api keys

Describe the bug
Creating tokens is possible with the default keys (admin and search) but is not possible with any kind of custom API key.
The same custom api key was able to create a token in v0.27.0
To Reproduce
Steps to reproduce the behavior:

Create a custom API key with the master key

{
        expiresAt: null,
        description: 'Custom key',
        actions: ['search'],
        indexes: [UID],
      }

Create a jwt with any search rule
An error is thrown The provided API key is invalid.

Expected behavior
Should be working
Meilisearch version: [e.g. v0.20.0]
v0.28.0rc0

Thanks @bidoubiwa for the report!
We need to add tests for this! 🔥

We further tried it out and it does not work with the default API keys as well

Thank you @Kerollmops for investigating!!

authors: bidoubiwa curquiza

repo: meilisearch/meilisearch


text:
Would this work as a webassembly module?

To integrate this with browser/client/serverless javascript, as a developer, I want to find out if this could compile to web assembly. That would be interesting because you could import a search function in the browser or alongside node processes in serverless microservices and use MeiliSearch without needing to wait for network requests. That might be hella fast
How do you feel about web assembly?
https://developer.mozilla.org/en-US/docs/WebAssembly/Rust_to_wasm

I really hope this discussion is revived at some point. I feel like there is such a huge potential in running a lightweight search engine on the edge, utilizing some distributed KV storage.

Hello @janus-reith
You're right, the potential is huge, we are aware of this, but the work is huge as well :)
Making MeiliSearch work on lambda edge in an easy and open-sourced is really complex regarding the current codebase.
Most of the core team is currently focusing on adding the most important features we are missing, for instance, the High Availability. But be sure we are still working on it 🙂
FYI, the search on the edge needs several R&D phases on our side. The first phase is to integrate segments into milli -> you can follow the work on this issue.
But integrating segments is only the beginning, so it's not possible to give any ETA.

You're right, the potential is huge, we are aware of this, but the work is huge as well :)

Awesome to hear it's still on your radar! :)

Making MeiliSearch work on lambda edge in an easy and open-sourced is really complex regarding the current codebase.

Yeah I can imagine that there's quite some hurdles involved.
I have my eye on Cloudflare Workers and Deno Deploy, as well as any potentially emerging platforms built on a similar architecture. ^^
Maybe sometime in the future one wasm build could cover them all with some simple wrappers 🤞

Hello @nolotz
No, sorry we have not worked on this yet. It's not trivial to make meilisearch work on the edge, but it's still something we have as long term plan.

authors: bionicles curquiza janus-reith


text:
Batch tasks by total payload size instead of tasks count

Motivation

Improve indexing speed and avoid RAM consumption issues
Usage

Introduce a flag to batch by size instead of tasks count (as it's processed now)
@ManyTheFish @Kerollmops, TBD:

If experimental -> create product discussion
If not, create PRD and public API usage
And link it here

TODO

Reminders when modifying the Setting API

[ ] Ensure the new setting route is at least tested by the test_setting_routes macro
[ ] Ensure Analytics are fully implemented

[ ] /settings/my-new-setting configurated in the make_setting_routes macro
[ ] global /settings route configurated in the update_all function

[ ] Ensure the dump serializing is consistent with the /settings route serializing, e.g., enums case can be different (camelCase in route and PascalCase in the dump)

Special cases when adding a setting for an experimental feature

[ ] ⚠ API stability: The setting does not appear on the main settings route when the feature has never been enabled (e.g. mark it Unset when returned from the index in this situation. See an example)
[ ] The setting cannot be set when the feature is disabled, either by the main settings route or the subroute (see validate_settings function)
[ ] If possible, the setting is reset when the feature is disabled (hard if it requires reindexing)

Impacted teams
@meilisearch/docs-team @meilisearch/cloud-team

@curquiza
I would like to take a grab at the issue.
But I see that some discussions are needed. Is it possible for me to get involved in those discussions as it would help me get a better understanding and requirements for the issue

Hello @K-Kumar-01 this issue will be tackle by our internal team to ensure to meet deadline and internal requirements. But we appreciate your involvement.
Except if @meilisearch/engine-team knows exactly what we want to do, in this case, please explain the details in this issues 😊


text:
search result doesn't have scroll bar

Description
I set the maxSuggestions to 20, and when I search a key word that has many suggestions, the result display without scroll bar in the right and also miss the "powered by" logo. It seems the server return right results because when I zoom out the page to  50% or less, all results can been seen.
by the way, I use a community vuepress theme which version is 1.30.0.
Expected behavior
show the suggestion scroll bar when the page zoom 100%.
Current behavior
not showing yet.
Screenshots or Logs

Environment (please complete the following information):

OS: neon KDE Ubuntu 20.04
Meilisearch version: v0.29.0
vuepress-plugin-meilisearch version: v0.13.0
Browser: Chrome 108.0.5359.71 also Firefox 105.0
VuePress version: v1.9.7

config file

Hey @PPG007, thanks for raising this.
Unfortunately, not adding a scroll bar is on purpose. It clashes with the scrolling experience on the screen. I think you might tweak the CSS though to obtain what you want.

@bidoubiwa Thanks for your reply, I finally resolve this by using .vuepress/styles/index.styl.

repo: meilisearch/vuepress-plugin-meilisearch


text:
TestTableDetection.[35]: Expected one table and detected two

File us-009.pdf
New code is detecting more rulings that the old code.
New rulings:

Old rulings:

That's why is detecting 2 tables instead of 1, see images:
New:

Old:

I think it is ok to detect 2 tables, what should we do in this case?

That's an interesting side effect of the improvements in PDFBox 2.0: the old version missed some lines.
Also, we've run into this case before. Sometimes, the table detection algorithm picks up two "tables", one contained inside the other. Unfortunately, we haven't arrived to a decision on what to do. My guess is that we should build a tree of rectangles (using containedIn as the linkage criteria) and keep the outermost element. @jeremybmerrill any ideas?

I found the comparator in the NurminenDetectionAlgorithm and I made a fix the make the tests pass.
I'm not sure if this is the right solution, because this comparator doesn't ensure that the TreeSet keep the outermost table, this depends of the order of the tables that you send in the addAll:
tableSet.addAll(tableAreas);

authors: jazzido melisabok

repo: melisabok/tabula-java

license: mit

license_source: bigquery


text:
image.MetaData.HorizontalResolution is not correct, returns 1, and file properties shows 96

I'm using Veldrid.ImageSharp v4.1.1 from Nuget, and run the following code:
var fileStream = new FileStream("96Resolution.jpg", FileMode.Open);
IImageFormat format;
var image = Image.Load(fileStream, out format);
if (image.MetaData.HorizontalResolution < 72){ .... }
Here image.MetaData.HorizontalResolution is 1, but when I check the image properties, its resolution is 96 both vertically and horizontally. Another jpg file returns the correct resolution.
Just attached my test image.

Thanks

Hey @steven-gong, I'm not actually the developer of ImageSharp itself. Veldrid.ImageSharp is just an integration library that lets you create GPU textures from images loaded through ImageSharp. If there's a problem with loading image files, then you might want to go check the ImageSharp repo, or ask around the chat to see if anyone's seen the problem before.

Hi Eric,
Thanks, will post the issue there.
Steven
On 16 March 2018 at 17:35, Eric Mellino notifications@github.com wrote:

Hey @steven-gong https://github.com/steven-gong, I'm not actually the
developer of ImageSharp itself. Veldrid.ImageSharp is just an integration
library that lets you create GPU textures from images loaded through
ImageSharp. If there's a problem with loading image files, then you might
want to go check the ImageSharp repo
https://github.com/SixLabors/ImageSharp, or ask around the chat to see
if anyone's seen the problem before.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mellinoe/veldrid/issues/56#issuecomment-373601039,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AU-xBpbLtb_VCxdfAkit5Kk-g4BWpHxkks5te0EpgaJpZM4StOrt
.

authors: mellinoe steven-gong

repo: mellinoe/veldrid


text:
🛑 Siege Green SeAT is down

In 809f0d1, Siege Green SeAT (https://seat.siege-green.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Siege Green SeAT is back up in 8345d15 after 7 minutes.

repo: meloncafe/status-sggrn-upptime


text:
📁Docs: make importance of preprocessor setting more obvious in examples

First, thank you for what is already a great library.
But in writing my first component with it, I discovered a potential onboarding issue. After installing, I skipped straight to the example for the component I wanted to use and thought "Wow, that looks easy." And then proceeded to spin my wheels for quite some time trying to figure out why my radio buttons did absolutely nothing when I clicked them.
Eventually I figured out that I had to turn off the preprocessor switch in the lower left to see the code sample for my use case. To spare the next users who jump straight to the examples a similar frustration, perhaps something could be done to make the significance of that setting more prominent??

Thank you for the kind words 🧡
@AdrianGonz97 gave a good suggestion: Making the melt action throw an error when used in a non-pp environment, with a link to the PP docs. What do you think?

That would likely have helped. Though my ideal solution would probably be to place the preprocessor/non-preprocessor selector right next to the Tailwind/CSS selector. When I see a setting above the code like that, I know almost instantly that it affects that code sample. Had the selector been in that position, I might well have tried the right code the first time, and even if not, I probably would have found the issue quickly.

The issue is that we'd have to put the switch next to every code snippet, not only the component previews... But it's not a bad idea to be honest!

authors: TGlide harshbarger

repo: melt-ui/melt-ui


text:
Dagster as orchestrator

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2393
Originally created by @blarghmatey on 2020-10-26 21:34:52

Problem to solve
Add support for more orchestrators to improve the options for adoption of Meltano in a production context.
Target audience
Organizations and data teams that have already invested in an orchestrator other than Airflow.
Further details
I am considering setting up Meltano for use at my day job, and I currently use Dagster as my workflow
orchestrator so I was curious where in the code I should look to see about adding support for that integration. Also, if you have any pointers about sharp edges that I should avoid, or any upcoming change in the structure or roadmap of the project that would be helpful.
Proposal
I would like to be able to use Dagster as the orchestrator for executing my Meltano pipelines.
What does success look like, and how can we measure that?
Success looks like having a well defined integration with Dagster such that I can easily get up and running with Meltano as a component in a pipeline when I am already using the Dagster/Dagit service in my environment. The likely path is to add a plugin along the lines of what has been built for Great Expectations or DBT so that I can define a "Solid" that will execute a Meltano pipeline definition and provide detailed output that integrates with the existing logging infrastructure. If it is possible to use the Dagster table space as the metadata storage for Meltano for a tighter and simpler deployment, that would be a stretch goal to work toward.

View 23 previous comments from the original issue on GitLab

Hi guys,
how is the priority of this issue? It got moved up from January 2022 to July 2022.
It is the last missing piece for us to use Meltano fully.
Would love to see it in the next month.

Gagster is now live on the hub! 🎉
https://hub.meltano.com/utilities/dagster

For reference (since I didn't see the URL here nor in the Hub page): https://github.com/quantile-development/dagster-ext

authors: MeltyBot aaronsteers astrojuanlu ebnermic

repo: meltano/meltano


text:
Add goes-funky fork of singer-io/tap-shopify as new default variant

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2620
Originally created by @DouweM on 2021-03-02 23:45:22

All forks: https://github.com/singer-io/tap-shopify/network
Promising candidate: https://github.com/goes-funky/tap-shopify

View 10 previous comments from the original issue on GitLab


text:
pip cannot install a PyPI package that requires a non-PyPI package

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/359
Originally created by @mbergeron on 2019-02-05 20:59:06

After the v0.9.0 release @boleary tries to install it and was greeted with an unwelcome message:
(venv) ❯ pip install meltano
Collecting meltano
  Using cached https://files.pythonhosted.org/packages/f4/34/c56403bd041e07c0d3df218805379bce0daf0863b287df15de55ac599317/meltano-0.9.0.tar.gz
Packages installed from PyPI cannot depend on packages which are not also hosted on PyPI.
meltano depends on flask-security@ git+https://github.com/meltano/flask-security.git@v3.0.0/meltano.0.1.0

Even though you can install this package locally (i.e. if you download the tar.gz and pip install ..., it'll work) it seems pip doesn't support that when the package is hosted on PyPI.
Let's purge v0.9.0 from PyPI now and see what is our next step here.
Every time I come close to pip/PyPI it seems something breaks, should we move to 100% Docker?
/cc @jschatz1

View 8 previous comments from the original issue on GitLab


text:
Exploratory Sprint: Enable users to use Meltano with Jupyter Notebooks

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/539
Originally created by @dmor on 2019-03-20 14:51:04

We already produce tables and an analytics schema after ELT and transform, and it would technically work for us to connect this to a Jupyter Notebook.
This is a potential easy win for us.

[x]  @dmor Figure out if this is even possible
[x]  @iroussos make first draft of a simple tutorial to get set up
[x]  Look at the old Jupyter Hub setup
[ ]  Look for some generic tutorials we can copy
[ ]  Add this to our documentation

View 13 previous comments from the original issue on GitLab


text:
chore: Add libpq-dev to Meltano Docker image

Successful Docker publish workflow targetting the GitHub registry: https://github.com/meltano/meltano/actions/runs/2847838317
This increases the image size a negligible amount, and pulls in few libraries that we didn't already have.
It introduces 2 new security vulnerabilities, but I'm not sure which ones. GitHub doesn't seem to provide a way to diff the alerts between 2 branches.

Closing as stale.


text:
chore: Disable meltano compile command

Context:

https://github.com/meltano/meltano/issues/7306#issuecomment-1432086410

To avoid anyone depending on the manifest feature before we are confident that we can avoid making breaking changes to it, this PR disables the meltano compile command. Manifests can continue to be used internally, but once we allow users to generate them via the CLI, and depend on the data they contain, we will have to be careful about what we change.

Closing following a discussion with @aaronsteers. Another PR will be opened shortly to make it clear that the compile command is experimental.


text:
feat: import json module for stream maps, add tests

First draft.
Resolves:

#1502

Related to:

#1500

@edgarrmondragon - This is another PR I opened a while ago and wasn't high enough priority to push to delivery. I think I'll close for now, since it needs a tiny bit more work and I don't currently have capacity to get it completed. If anyone else wants to pick this up, they can use this as a starting point for resolving this one:

#1502

repo: meltano/sdk


text:
🛑 Kérwá is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Kérwá is back up in f50a9f7 after 7 minutes.

repo: memoemg/howyoudoing


text:
🛑 Kérwá is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Kérwá is back up in d89c5a8 after 7 minutes.


text:
🛑 Kérwá is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Kérwá is back up in 59e220a after 14 minutes.


text:
🛑 Kérwá is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Kérwá is back up in be4a1ae after 56 minutes.


text:
how to check is click position inside a shape or not?

Is there any function to check that click position inside a shape or not?
for example is a position inside a rounded rect or not? or any Idea to help me to achieve this functionality

Have you ever figured this out?

repo: memononen/nanovg

license: Zlib


text:
Build instructions added to README.md

There were no instructions on building the nanovg examples, and I'd never run across the premake tool before, so I added a quick tutorial.
I put the information at the top of the file -- I felt that this was a good place to put it since the demo is really slick, and would motivate people to learn the API below.

Excelent idea, would you mind updating the PR to give a bit more hints per platform? Here's what I did on another project: https://github.com/memononen/recastnavigation

authors: epitron memononen


text:
Use TryLock instead of RwLock/Mutex for uncontended locks

We use RwLock and Mutex in some places where we only use the .try_*() methods, as there's no actual contention, and we're doing it just for the borrow checker. However, RwLock and Mutex are fairly large and even their .try_*() methods are not small, so we should use a lightweight alternative like TryLock, whose only overhead is an AtomicBool and atomic swaps for locking and unlocking.

It seems like parking_lot::Mutex's .try_lock() is about as efficient as TryLock, so this isn't worth it anymore now that we're using parking_lot.


text:
Width in percentage on left column doesn't work as it should

Hi,
When setting the property: width in percentage under Left data source, I expect that the complete column becomes wider and not only the left column on the top row.
Also when i keep the value on 0, I expect that the text in the left column is visible. Now it just becomes invisible.

This is when the percentage is set to 25

This is when the percentage is set to 0

Fixed in version 2.2. New version is pending on the App Store or you can download the .mpk directly here on Github.

authors: Rvthof sebasvanderplaat

repo: mendix/GridSelector


text:
composer repositories 出现警告导致nginx 访问502

PHP 5.6
Loading composer repositories with package information
Installing dependencies from lock file
Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. Run update to update them.
  - Installing yiisoft/yii2-composer (2.0.3)
    Loading from cache

  - Installing bower-asset/jquery (2.1.4)
    Loading from cache

  - Installing bower-asset/jquery.inputmask (3.1.63)
    Loading from cache

  - Installing bower-asset/punycode (v1.3.2)
    Loading from cache

  - Installing bower-asset/yii2-pjax (v2.0.5)
    Loading from cache

  - Installing symfony/routing (v2.7.7)
    Loading from cache

  - Installing symfony/http-foundation (v2.7.7)
    Loading from cache

  - Installing evenement/evenement (v2.0.0)
    Loading from cache

  - Installing react/stream (v0.4.3)
    Loading from cache

  - Installing react/event-loop (v0.4.1)
    Loading from cache

  - Installing react/socket (v0.4.2)
    Loading from cache

  - Installing symfony/event-dispatcher (v2.7.7)
    Loading from cache

  - Installing guzzle/common (v3.9.2)
    Loading from cache

  - Installing guzzle/stream (v3.9.2)
    Loading from cache

  - Installing guzzle/parser (v3.9.2)
    Loading from cache

  - Installing guzzle/http (v3.9.2)
    Loading from cache

  - Installing cboden/ratchet (v0.3.3)
    Loading from cache

  - Installing cebe/markdown (1.1.0)
    Loading from cache

  - Installing ezyang/htmlpurifier (v4.6.0)
    Loading from cache

  - Installing yiisoft/yii2 (2.0.6)
    Loading from cache

  - Installing bower-asset/bootstrap (v3.3.5)
    Loading from cache

  - Installing yiisoft/yii2-bootstrap (2.0.5)
    Loading from cache

  - Installing swiftmailer/swiftmailer (v5.4.1)
    Loading from cache

  - Installing yiisoft/yii2-swiftmailer (2.0.4)
    Loading from cache

Package guzzle/common is abandoned, you should avoid using it. Use guzzle/guzzle instead.
Package guzzle/stream is abandoned, you should avoid using it. Use guzzle/guzzle instead.
Package guzzle/parser is abandoned, you should avoid using it. Use guzzle/guzzle instead.
Package guzzle/http is abandoned, you should avoid using it. Use guzzle/guzzle instead.

Generating optimized autoload files

拉取了两次均是这个警告

最近guzzle升级，甚至最低php要求5.5，也让我好头疼，警告没事，忽略吧

呐尼，难怪我找不到解决方案，一搜一大堆都是即将更新的消息
--
Sent with Airmail
发件人: huamanshu notifications@github.com
回复: meolu/walle-web reply@reply.github.com
日期: 2015年12月5日 at 14:44:49
到: meolu/walle-web walle-web@noreply.github.com
抄送: Tory 2pporg@gmail.com
邮件标题:  Re: [walle-web] composer repositories 出现警告导致nginx 访问502 (#71)
最近guzzle升级，甚至最低php要求5.5，也让我好头疼，警告没事，忽略吧
—
Reply to this email directly or view it on GitHub.

502的日志在哪里可以捕获？

502如果不是php超时，可以在php_errors里看到

额。路径呢~ 囧。我不会PHP，只是调研下帮公司选CI

加下我q吧，直接帮你解决

求联系方式。- -
--
Sent with Airmail
发件人: huamanshu notifications@github.com
回复: meolu/walle-web reply@reply.github.com
日期: 2015年12月6日 at 11:33:12
到: meolu/walle-web walle-web@noreply.github.com
抄送: Tory 2pporg@gmail.com
邮件标题:  Re: [walle-web] composer repositories 出现警告导致nginx 访问502 (#71)
加下我q吧，直接帮你解决
—
Reply to this email directly or view it on GitHub.

q：861459320

authors: meolu zzvv

repo: meolu/walle-web


text:
Humidifier reports 0 temperature and humidity when offline

I added my humidifier (deerma.humidifier.jsqs) to homebridge via this plugin.
The problem is, when the humidifier is offline, the plugin would still report 0°C temperature and 0% humidity to HomeKit.
I tried manually removing all “environment” stuff from the js file, the extra accessories in the following screenshot would be removed.

But the “Current Relative Humidity” attribute was still there (see below screenshot).

This is not a huge deal, but kind of annoying. Especially when you ask Siri, she would say the temperature ranges from 0 to something.  I only use the device in winter, so it’s offline most of time through the year.
Is it possible to avoid reporting data when the device is offline (maybe show it as no response), or completely disable the temperature and humidity sensors?
Thank you.

Oh, you are right! Not sure how i missed that, but indeed the temperature sensor and relative humidity sensor are always set to active and do not change to inactive when the device goes offline. Will adjust that in the next update!

Should be fixed in 1.2.0

@merdok Thanks for the quick fix. However, I’m still seeing the same issue after upgrading to 1.2.0.
Could you please take a look again? Following are the debug logs for my humidifier.
Initial logs when the device is connected.
[5/21/2022, 10:44:32 AM] [miot] [Bedroom Humidifier] Got device configuration, initializing device with name: Bedroom Humidifier
[5/21/2022, 10:44:32 AM] [miot] [Bedroom Humidifier] Model known: deerma.humidifier.jsqs!
[5/21/2022, 10:44:32 AM] [miot] [Bedroom Humidifier] Initializing device!
[5/21/2022, 10:44:32 AM] [miot] [Bedroom Humidifier] Creating device instance by model: deerma.humidifier.jsqs!
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Did not find device class! Trying to identify device from miot spec!
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Found cached miot spec for device: deerma.humidifier.jsqs
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Parsing miot spec!
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Using humidifier type and Humidifier description for device identification!
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Got device type Humidifier from spec!
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Found device type class at ../modules/humidifier/HumidifierDevice.js!
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Using module class for device type Humidifier, indentified by miot spec! Not all features might work!
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Initializing device services
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Device services: [
  "humidifier",
  "environment",
  "alarm",
  "indicator-light",
  "custom"
]
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Initializing device properties
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Device properties: [
  "humidifier:on",
  "humidifier:fault",
  "humidifier:fan-level",
  "humidifier:target-humidity",
  "environment:relative-humidity",
  "environment:temperature",
  "alarm:alarm",
  "indicator-light:on",
  "custom:water-shortage-fault",
  "custom:the-tank-filed",
  "custom:set-overwet-protect",
  "custom:other-sensors"
]
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Initializing device actions
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Device actions: [
  "custom:if-device-relative"
]
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Initializing device events
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Device events: [
  "custom:lack-of-water",
  "custom:bring-water-tank",
  "custom:overwet"
]
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Initial properties to monitor: [
  "humidifier:on",
  "humidifier:fault",
  "humidifier:fan-level",
  "humidifier:target-humidity",
  "custom:water-shortage-fault",
  "alarm:alarm",
  "indicator-light:on",
  "environment:temperature",
  "environment:relative-humidity"
]
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Successfully created a Humidifier device! It is a Unknown humidifier device.
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Found cached accessory for this device! Unregistering it first!
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Initializing accessory!
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Creating Humidifier accessory for device Bedroom Humidifier!
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Found accessory class at ../modules/humidifier/HumidifierAccessory.js!
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Accessory successfully initialized!
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Final properties to monitor: [
  "humidifier:on",
  "humidifier:fault",
  "humidifier:fan-level",
  "humidifier:target-humidity",
  "custom:water-shortage-fault",
  "alarm:alarm",
  "indicator-light:on",
  "environment:temperature",
  "environment:relative-humidity"
]
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Registering 1 accessories!
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Everything looks good! Initiating property polling!
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] (Protocol) Call 192.168.2.33: miIO.info - {"timeout":5000,"retries":3} - {}
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Device found: deerma.humidifier.jsqs
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Setting up miot device!
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Doing basic setup
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Device firmware: 2.1.3
[5/21/2022, 10:44:33 AM] [miot] [Bedroom Humidifier] Doing MiCloud setup
[5/21/2022, 10:44:35 AM] [miot] [Bedroom Humidifier] Got device info from MiCloud:
{
  "did": "455782265",
  "token": "…",
  "longitude": "0.0",
  "latitude": "0.0",
  "name": "…”,
  "pid": "0",
  "localip": "192.168.2.33",
  "mac": "B4:60:ED:5E:D7:8D",
  "ssid": "…",
  "bssid": "8C:DE:F9:E3:3C:2A",
  "parent_id": "",
  "parent_model": "",
  "show_mode": 1,
  "model": "deerma.humidifier.jsqs",
  "adminFlag": 1,
  "shareFlag": 0,
  "permitLevel": 16,
  "isOnline": true,
  "desc": "Device online ",
  "extra": {
    "isSetPincode": 0,
    "pincodeType": 0,
    "fw_version": "2.1.3",
    "needVerifyCode": 0,
    "isPasswordEncrypt": 0,
    "mcu_version": "0017"
  },
  "uid": …,
  "pd_id": 72559,
  "password": "",
  "p2p_id": "",
  "rssi": -37,
  "family_id": 0,
  "reset_flag": 0
}
[5/21/2022, 10:44:35 AM] [miot] [Bedroom Humidifier] Device setup finished! Miot device ready!
[5/21/2022, 10:44:35 AM] [miot] [Bedroom Humidifier] Connected to device: deerma.humidifier.jsqs
[5/21/2022, 10:44:35 AM] [miot] [Bedroom Humidifier] Doing initial property fetch.
[5/21/2022, 10:44:35 AM] [miot] [Bedroom Humidifier] Splitting properties into chunks. Number of chunks: 1. Chunk size: 14
[5/21/2022, 10:44:35 AM] [miot] [Bedroom Humidifier] (Protocol) Call 192.168.2.33: get_properties - [{"did":"455782265","siid":2,"piid":1},{"did":"455782265","siid":2,"piid":2},{"did":"455782265","siid":2,"piid":5},{"did":"455782265","siid":2,"piid":6},{"did":"455782265","siid":7,"piid":1},{"did":"455782265","siid":5,"piid":1},{"did":"455782265","siid":6,"piid":1},{"did":"455782265","siid":3,"piid":7},{"did":"455782265","siid":3,"piid":1}] - {}
[5/21/2022, 10:44:35 AM] [miot] [Bedroom Humidifier] Successfully saved device info!

Logs after the device disconnects.
5/21/2022, 10:54:04 AM] [miot] [Bedroom Humidifier] (Protocol) 192.168.2.33 <- Handshake timed out
[5/21/2022, 10:54:04 AM] [miot] [Bedroom Humidifier] (Protocol) 192.168.2.33 <- Reached maximum number of retries, giving up get_properties - [{"did":"455782265","siid":2,"piid":1},{"did":"455782265","siid":2,"piid":2},{"did":"455782265","siid":2,"piid":5},{"did":"455782265","siid":2,"piid":6},{"did":"455782265","siid":7,"piid":1},{"did":"455782265","siid":5,"piid":1},{"did":"455782265","siid":6,"piid":1},{"did":"455782265","siid":3,"piid":7},{"did":"455782265","siid":3,"piid":1}]
[5/21/2022, 10:54:04 AM] [miot] [Bedroom Humidifier] Poll failed 1 times!
[5/21/2022, 10:54:04 AM] [miot] [Bedroom Humidifier] Poll failed! Error: Error: Call to device timed out

Both the temperature and humidity sensor are now set to inactive when the device is not connected. Not sure how the Home app handles that...

Is it possible to set the entire humidifier device as inactive, not just
the sensors?
On Sat, May 21, 2022 at 15:18 Marcin @.***> wrote:

Both the temperature and humidity sensor are now set to inactive when the
device is not connected. Not sure how the Home app handles that...
—
Reply to this email directly, view it on GitHub
https://github.com/merdok/homebridge-miot/issues/264#issuecomment-1133553775,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAV76B7SQYSUMAB77KRTJL3VLCE2NANCNFSM5TWE2N3Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

Is it possible to set the entire humidifier device as inactive, not just the sensors?

If that’s not possible, maybe add an “enable” option to allow manually disable a device?

The device is also being already set as inactive when it is not connected. I am not sure why Siri would still pick them up even that they are inactive...

authors: merdok raulchen

repo: merdok/homebridge-miot


text:
fix: #619 Config-UI - Setup Delete Connection UX Workflow

Config-UI / Integrations / JIRA (Multi-source) / DELETE
Key Points

[x] Enable DELETE UX for multi-source Providers such as JIRA
[x] Add Delete Trigger to Provider Connections List View
[x] Add Delete Trigger to Configure Connection View
[x] Disable (hide) delete for single-source connections

Description
This PR adds support for deleting connections for providers that are flagged as "Multi-source", primarily JIRA at this moment. Single-source providers such as GitHub and Jenkins are unaffected by this change.
Does this close any open issues?
#619
Current Behavior
Users can add multiple connections for JIRA but are unable to remove them.
New Behavior
Users are able to DELETE a connection added to a multi-source provider such as JIRA.
Screenshots

LGTM

repo: merico-dev/lake


text:
Suggestion

NOT ISSUE REALY, JUST A SUGGESTION
Is it not better if a service creates and exposes its clients?
for example here https://github.com/merikbest/twitter-spring-reactjs/blob/microservice/chat-service/src/main/java/com/gmail/merikbest2015/feign/TweetClient.java
you are creating tweet client, but technically that should be created in the tweet service and uploaded to artifactory as part of every release. then other services to import is use them

Hi there,
JUST A SUGGESTION
By creating the tweet client inside the tweet service like you suggested could introduce a form of tight coupling or high coupling of dependency between services.
This would mean that changes in the Tweet service could potentially impact the Chat service, and vice versa.
In the context of microservices and software architecture, it's generally preferred to achieve loose coupling or low coupling.
** this is a suggestion **

You are not wrong but some times it is needed, like if you use service X most likely will try using their SDK too right?
Also service change should be backward compatible, it is not always possible but better to be.
// I said these based on my previous involvements with real-lworld microservices.

authors: Akinyemi-samuel amirmab

repo: merikbest/twitter-spring-reactjs


text:
Error when detecting changes

this is my docker info
Containers: 3  Running: 1  Paused: 0  Stopped: 2 Images: 21 Server Version: 17.12.0-ce Storage Driver: overlay2  Backing Filesystem: extfs  Supports d_type: true  Native Overlay Diff: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins:  Volume: local  Network: bridge host ipvlan macvlan null overlay  Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: 89623f28b87a6004d4b785663257362d1658a729 runc version: b2567b37d7b75eb4cf325b77297b140ea686ce8f init version: 949e6fa Security Options:  seccomp   Profile: default Kernel Version: 4.9.60-linuxkit-aufs Operating System: Docker for Windows OSType: linux Architecture: x86_64 CPUs: 2 Total Memory: 1.934GiB Name: linuxkit-00155d014d01 ID: ATPD:LEOL:LNRR:KEHA:NR6R:AVKN:LQR6:5XF5:W7VT:6HUP:GUS5:ONDU Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): true  File Descriptors: 29  Goroutines: 55  System Time: 2018-02-02T01:09:14.2428761Z  EventsListeners: 2 Registry: https://index.docker.io/v1/ Labels: Experimental: true Insecure Registries:  127.0.0.0/8 Live Restore Enabled: false
I'm running docker-volume-watcher
and when I change some file throws this exception
Exception in thread Thread-1: Traceback (most recent call last):   File "c:\users\XXX\appdata\local\programs\python\python36-32\lib\threading.py", line 916, in _bootstrap_inner     self.run()   File "c:\users\XXX\appdata\local\programs\python\python36-32\lib\site-packages\watchdog\observers\api.py", line 199, in run     self.dispatch_events(self.event_queue, self.timeout)   File "c:\users\XXX\appdata\local\programs\python\python36-32\lib\site-packages\watchdog\observers\api.py", line 368, in dispatch_events     handler.dispatch(event)   File "c:\users\XXX\appdata\local\programs\python\python36-32\lib\site-packages\watchdog\events.py", line 454, in dispatch     _method_map[event_type](event)   File "c:\users\XXX\appdata\local\programs\python\python36-32\lib\site-packages\docker_volume_watcher\container_notifier.py", line 49, in __change_handler     self.notify(absolute_path)   File "c:\users\XXX\appdata\local\programs\python\python36-32\lib\site-packages\docker_volume_watcher\container_notifier.py", line 66, in notify     permissions = permissions.decode('utf-8').strip() AttributeError: 'ExecResult' object has no attribute 'decode'
I'm unable to find anything related to this on docs and previous issues, so any help will be appreciated
thanks in advance

Hi @epgeroy,
thank you for reporting this issue. Looks like in the version 3.0.0 of docker python package (which was released by docker just yesterday) some incompatible changes to API were made.
As a temporary solution please try downgrading docker python package (this action will not downgrade docker itself):
pip install docker==2.7.0

Please let me know if this workaround helps. Meanwhile I will try to fix compatibility of docker-windows-volume-watcher with the new docker python package.

Thanks for the short reply, it works when downgrading docker package perfectly.
please let us know if there are any changes with this issue. Thanks again.

authors: epgeroy merofeev

repo: merofeev/docker-windows-volume-watcher


text:
Where is the ta_heap array being used?

I'm having an issue where a TA is running out of heap memory.
I've increased TA_DATA_SIZE, but this appears to have no effect.
Looking through the code, the ta_heap array is allocated in ta_static.rs and placed in bss.
However, I cannot find where ta_heap is being added to the memory pools (or even if the OPTEE memory pool implementation is being used by the rust allocator).
Where in the code is the ta_heap array being used?

I found the functions in user_ta_entry.c, but I do not see them getting called.
The main entry point for user_ta_entry.c , __utee_entry, is not getting called.
Do I need to somehow call __utee_entry in the create or open_session functions of my TA in order to get my ta_heap allocation added to the memory pools?

The entrypoint of a TA is __ta_entry:
https://github.com/OP-TEE/optee_os/blob/b4814b22dcf813691f1a6697e2013b0cbeb8dca3/ta/arch/arm/user_ta_header.c#L43
This entrypoint is specified by linker:
https://github.com/OP-TEE/optee_os/blob/b4814b22dcf813691f1a6697e2013b0cbeb8dca3/ta/arch/arm/link.mk#L29
So, I think it is already added to the memory pools when TA started.

Issue staled. I'm closing it. Feel free to reopen if you think it's still valid.

authors: dreemkiller mssun

repo: mesalock-linux/rust-optee-trustzone-sdk


text:
Move service's status to manager

In PR https://github.com/mesg-foundation/core/pull/904, the package manager has been introduced to manage the logic between service and container.
Continuation of conversation: https://github.com/mesg-foundation/core/pull/904#discussion_r277137119
Now that's the manager is managing all container related functions, the status of a service should not stay in the package service but should move to the package manager.
The service package should have only logic about the service's data and nothing more.
Basically, the file manager.go should only return struct define in its own package.
Please check the conversation first, and then tell if you are agree to move namespace to manager or leave it like this.

I can't quite agree with this one because manager.go is also depends on the service.Service, in this case we have to move it to manager as well. In that case, there is no reason for having both service & manager packages. because they should be merged into one. to me, service pkg is all about storing the data types for services and other useful stuff like validation, getters, errors, etc.

service.Service is passed as inputs of the functions in manager.
I'm speaking about the returned values of the manager's function.

to me, service pkg is all about storing the data types for service and useful stuff for service like validation, getters, errors types etc.

So why service should keep status when its logic is implemented in another package?

it's a logical decision. Manager is responsible with dealing with Service type and its siblings, not defining them. because Manager has nothing to do with service validation, task getter, event not found errors or etc. its just responsible for managing the service's container and providing logs, statuses, etc.

I see the manager package as the link between service and container.
Service should not have anything about container.
Container should not know anything about service.
Only manager knows both and define the logic and data structure that "connect" service with container.
What is the status of a service if service doesn't know anything about container?
Same for log.
Maybe manager is not the best name for the manager package as it's too generic and doesn't describe enough the goal of the package.
@antho1404 suggested "runner" in the PR https://github.com/mesg-foundation/core/pull/904. I kind of like it. Maybe with a bit more context: "serviceRunner".
@mesg-foundation/core  What do you think?

Container and Service should no know each other and yes only the manager knows both.
For now, we get the status based on the container information so service cannot do that and the manager should do it because it knows both.
For the name, I don't really like the name Manager, even serviceRunner is not ideal but still better. Moving this package into api (that controls all the logic) and calling it service would make sense.
This way it's an api package that manages the service that runs and we can call it instances or serviceInstances to start the next developments.
This for me makes a lot of sense and totally remove the dependency between the service package and the container. Also a good argument for that is that all the business logic is already fully delegated to this manager in the api meaning that this business logic is really related to the api

Moving this package into api (that controls all the logic) and calling it service would make sense.

Totally agree ;) but still let's keep it at a separate package like: api/service.

@antho1404 suggested "runner" in the PR #904. I kind of like it. Maybe with a bit more context: "serviceRunner".

👎 - runner sounds like js runner or task runner something like this. Manager tells the story. Docker container could be called runner because it runs the service but don't change the manager name (at least not for a runner).
The things you are talking about are in the https://github.com/mesg-foundation/core/pull/799/ ;) so yes and yes. The service shouldn't know anything about the container and vice versa and the Manager should be link between them

authors: NicolasMahe antho1404 ilgooz krhubert

repo: mesg-foundation/core


text:
[CI] Support Multi-platform Docker Images

Desired Behavior
Meshery users, particularly those running Docker Desktop can benefit from multi-platform images of Meshery Server.
Implementation
Refactor existing stable and edge build and release workflows to use docker-build-push actions. See https://github.com/meshery/meshery/blob/master/.github/workflows/build-and-release-dde.yml as an example.
Be aware of local binaries and their needs:

layer5/wrk2
layer5/nighthawk
layer5/kubeopenapi-json

Acceptance Tests

platform: linux/amd64,linux/arm64 should both be supported.2.

Contributor Guides and Resources

🛠 Meshery Build & Release Strategy
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

completed

repo: meshery/meshery-cilium


text:
add catalog links

Notes for Reviewers

This PR fixes #

Signed commits

[x] Yes, I signed my commits.

🚀 Preview for commit bf2c60c9c306c228b9ca88b755f6e8e2ca1c0afd at: https://673755637fe30d98ba0d960f--meshery-docs-preview.netlify.app

repo: meshery/meshery


text:
[WIP] Meshery perf helm

Description
This PR fixes #4895
The helm charts for meshery-perf have been added in both meshery and meshery-operator directories in /install/kubernetes/helm
Notes for Reviewers
This is a reasonably big PR where I my work primarily has been copying and pasting. I would need ideas on how to test my changes, to ensure the meshery-perf component runs as per expectations. I would need inputs from you folks on this @leecalcote @piyushsingariya @gyohuangxin @Aisuko
TO-DO's
Making changes to the README's in the meshery-perf children charts as well as meshery and meshery-operator charts
Signed commits

[ ] Yes, I signed my commits.

The templated approach makes deployments configurable for users who might want to change the law clear assigned port number for each deployed pod. It seems that the default values for the container parts aren't being supplied, though?
Port 10013/tcp needs to be reserved in the Meshery Docs. Please do PR the Docs to make this component-to-port assignment - https://docs.meshery.io/concepts/architecture

Sure @leecalcote it looks like I just need to create a new row for meshery-perf here https://github.com/meshery/meshery/blob/master/docs/pages/concepts/architecture/architecture.md#network-ports
Right?

Hey @navendu-pottekkat, @leecalcote, @gyohuangxin can you suggest some ways to test my changes out. They do pass the chart tests here, but still anything to reduce your reviewing load just let me know

Sure @leecalcote it looks like I just need to create a new row for meshery-perf here https://github.com/meshery/meshery/blob/master/docs/pages/concepts/architecture/architecture.md#network-ports
Right?

Spot on, yes. 👍

@hershd23 something to demo here for the meshery dev call? I'll put it on the agenda just in case😅


text:
fix release tag function to work with alphanumeric tags  w/signoff

Description
The old function only works for numeric values and sort them. This function sorts tags based on release time rather than tag number.
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

https://github.com/meshery/meshery/issues/11598

@Jougan-0 where did we land on this approach?

@Jougan-0 where did we land on this approach?

I was working solely on the migration and fixing bugs of the v1beta1 pr now that's done I'll head to this issue.

@Jougan-0 thank you. I'll put the k6 model to use immediately, when this is completed.

Was a decision arrived at in terms of when to incorporate consideration of release date vs. tag numbering?

Nope haven't been to discuss this needs a revisit later this week if we don't stuck on Kanvas.

repo: meshery/meshkit


text:
Add test cases for SocketUrlDetection

There is no test class in SocketUrlDetection.
So, I created SocketUrlDetectionTest class and I wrote the test cases.
Please check this pull request.
Thanks.

@erikdw Thank you for review.
I rewrote code based on your review.

modified constant name: PORT --> HOPEFULLY_UNUSED_PORT
chaged port 9999 --> 29999
added comment to isReachableFalse method

Please check again.

@fuji-151a : thanks for the great comments that make it very clear what is happening.

repo: mesos/storm


text:
Fixes #55 - moves chaos examplpe into a separate build.

Like suggested in #55, examples are moved into a separate build.

@aquamatthias Replacement for #56 PR.

@aquamatthias src2 is no more

Thanks! :100:

authors: alexanderweber aquamatthias

repo: mesosphere/chaos


text:
[INFINITY-1762] Resource Refinement

Includes resource refinement / consumption of statically reserved resources, but with the capability turned off, pending merge of Mesos bits.

retest this please

repo: mesosphere/dcos-commons


text:
Disallow tasks/volumes/secrets being set to null in the DefaultPodSpec

Make sure empty collections are returned in DefaultPodSpec if tasks/volumes/secrets are null

@mbdcos: Collections should not possible by null.  I missed tasks and have fixed it.

retest this please

These fixes were applied in: https://github.com/mesosphere/dcos-commons/pull/1164

authors: benclarkwood gabrielhartmann


text:
Add advertise-address flag to handle the scheduler being behind a NAT

In cases where the Docker daemon puts containers behind a NAT, the agent needs to use a different address to the address that is bound on to get the executor and related binaries. This change adds an 'advertise-address' flag that allow you to specify this.
I would have loved to call this flag address, and move the current address flag to bind-address or something, but I don't know how compatible that would be?

thanks for the PR, left some comments

Not 100% sure that's exactly what you wanted. Used the explicitAdvertise var to indicate if the advertiseAddress flag was ever set to anything different.

authors: bluepeppers jdef

repo: mesosphere/etcd-mesos


text:
Gradle build, Findbug and PMD fixes

This PR doesn't remove mvn.  It just adds gradle.  Both builds styles work currently.  There is a desire to have a multi-project build and this moves in that direction.   There are a number of checkstyle, findbugs and PMD fixes in this PR as well.   This has been rebased with the latest.
@elingg would love your review and merge.

I did NOT expect teamcity to have a preference for gradle :)   The build failed because of the gradle build.  The mvn package works.   It has been resolved.  I'll add in the findbugs and PMD when we work out all the issues that are still there.  (some can safely be ignored)

@kensipe, I'll take a look. Thanks for your contribution!

Thanks for the lovely clean up that the rest of us haven't had a chance to do @kensipe! I left a few comments and also still need to test this. Could you also rebase with master? @adam-mesos will also be taking a look.

@kensipe You should consider updating .travis.yml to run your gradle+findbugs+etc. build/tests.

@adam-mesos it already is :)  I discovered on accident.   It apparently doesn't require a .travis change.  Currently the yml configures the different JVMs to run.  openjdk + the oracle jvm.   I just checked and the last builds for this branch run the gradlew which is appropriate (and the reason I included it) with the "build" task... which runs the build + findbugs + PMD + checkstyle.

@elingg this is ready to go after updates based on reviews.  there are a couple points of debate with details above (I capture them here so it is easier to see all at once.

hadoopConfig vs hdfsConfig
name of HdfsFrameworkConfig class
//NOPMD comments

everything else I believe is resolved.

Where did the binary gradle/wrapper/gradle-wrapper.jar come from? Can we please check in source instead of binaries?

Looks like a great step in the right direction. I've got a few concerns, but they should be resolvable.

Although findbugs(?) seems to suggest removing RuntimeException throws, we cannot just log the error and return in every case. Unrecoverable errors must be propagated up the call chain.
I think you accidentally removed a mkdirs() call in NameNodeExecutor.
We should not be checking in a binary file, even a jar.
We'll need to test this on at least a few popular linux distros (and maybe OS X) before merging.

As for your previous concerns:

hadoopConfig vs hdfsConfig: I prefer frameworkConfig, or mesosFrameworkConfig.
HdfsFrameworkConfig sounds good, but you'll want to change HDFSConstants to HdfsConstants.
Fix the NOPMD errors, don't enable that rule, or at least restrict the PMD suppression to a single rule.

Thanks for the detailed review, @adam-mesos since I did not have time for a final review yet. Removing the name dir is certainly a bug. My main concern is testing your Implementation @kensipe. The current code is fairly stable and I don't want to introduce any bugs. I was planning on testing it before merge but it would be better if you do since I have higher priority work on this projects The reason is that code changes and features take higher priority right now than clean up and build improvements. Thanks again for the great work on clean up and the build.

@adam-mesos @elingg
adam,
I've fixed or responded to each of feedback you provided.  thanks for the focused review!
referring to the gradle-wrapper.jar.  While I agree with the spirit of your concern completely.  This is a special case.  The gradle-wrapper.jar is established when you execute gradle wrapper.   It is a bootstrap jar which downloads and runs the exact version of gradle this was tested to work with which is defined in gradle-wrapper.properties.   This is the most mature way of managing builds as it is NOT dependent on a specific pre-installed tool version (such as maven).   It also allows someone to bootstrap their entire environment.   I can provide some demos if that helps.
I think all issues are resolved... except for testing.  which leads to the question...
what constitutes a successful test?   and which hadoop distros would you like?
ken

@kensipe, could you also update the readme if needed, so the users can understand the build process:
We are planning on adding automated tests ASAP, but right now we manually test the framework on a cluster. Testing involves running it on a cluster as explained in the readme and trying several hadoop fs commands, also described in the readme. I also typically test the following failure scenarios by killing the executor process for each scenario:
Restarting Framework
JN Standalone
JN Colocated
2 JNS
Active NN
Standby NN
JN + NN Colocated
JN + NN Not Colocated
ZKFC
DN
2 DNS

I would like to use hadoop 2.5 to be consistent with Myriad.

Closing this PR as this was broken into smaller PRs, 2 are already merged into master.
This is no longer useful.

authors: adam-mesos elingg kensipe

repo: mesosphere/hdfs


text:
no matching offer for /group/app

System: ubuntu 14.04 LTS 64bit
Marathon Version: 0.8.1-1.0.171.ubuntu1404
Mesos Version: 0.21.1-1.1.ubuntu1404
An application is not deployed even though the cluster has enough resource. See the logs below.
May  4 11:19:31 head2 marathon[27492]: [2015-05-04 11:19:31,443] INFO No matching offer for /xxx-group/web (need cpus=0.5, mem=384.0,
 disk=0.0, ports=Vector(0)) : id {
May  4 11:19:31 head2 marathon[27492]:   value: "20150428-051346-1388575636-5050-26039-O833496"
May  4 11:19:31 head2 marathon[27492]: }
May  4 11:19:31 head2 marathon[27492]: framework_id {
May  4 11:19:31 head2 marathon[27492]:   value: "20141126-052351-1405352852-5050-32174-0000"
May  4 11:19:31 head2 marathon[27492]: }
May  4 11:19:31 head2 marathon[27492]: slave_id {
May  4 11:19:31 head2 marathon[27492]:   value: "20150419-123325-1405352852-5050-1561-S11"
May  4 11:19:31 head2 marathon[27492]: }
May  4 11:19:31 head2 marathon[27492]: hostname: "mesos-slave.example.com"
May  4 11:19:31 head2 marathon[27492]: resources {
May  4 11:19:31 head2 marathon[27492]:   name: "cpus"
May  4 11:19:31 head2 marathon[27492]:   type: SCALAR
May  4 11:19:31 head2 marathon[27492]:   scalar {
May  4 11:19:31 head2 marathon[27492]:     value: 0.5
May  4 11:19:31 head2 marathon[27492]:   }
May  4 11:19:31 head2 marathon[27492]:   role: "*"
May  4 11:19:31 head2 marathon[27492]: }
May  4 11:19:31 head2 marathon[27492]: resources {
May  4 11:19:31 head2 marathon[27492]:   name: "mem"
May  4 11:19:31 head2 marathon[27492]:   type: SCALAR
May  4 11:19:31 head2 marathon[27492]:   scalar {
May  4 11:19:31 head2 marathon[27492]:     value: 384.0
May  4 11:19:31 head2 marathon[27492]:   }
May  4 11:19:31 head2 marathon[27492]:   role: "*"
May  4 11:19:31 head2 marathon[27492]: }
May  4 11:19:31 head2 marathon[27492]: resources {
May  4 11:19:31 head2 marathon[27492]:   name: "ports"
May  4 11:19:31 head2 marathon[27492]:   type: RANGES
May  4 11:19:31 head2 marathon[27492]:   ranges {
May  4 11:19:31 head2 marathon[27492]:     range {
May  4 11:19:31 head2 marathon[27492]:       begin: 31178
May  4 11:19:31 head2 marathon[27492]:       end: 31178
May  4 11:19:31 head2 marathon[27492]:     }
May  4 11:19:31 head2 marathon[27492]:   }
May  4 11:19:31 head2 marathon[27492]:   role: "*"

For me the offer seems enough for the app, why does marathon consider it "no matching"? Or did I get it wrong somewhere? There were also several other similar offers being considered "no matching" in the log.

Is there any useful information in the log before your log excerpt that indicate what resources/constraints aren't satisfied?
If you specify just slightly less resources, does it work then? Not that it is a rounding issue or the like.

Is there any useful information in the log before your log excerpt that indicate what resources/constraints aren't satisfied?

No, I don't find any.

If you specify just slightly less resources, does it work then? Not that it is a rounding issue or the like.

There were other offers that's more than engough, e.g.
May  4 11:19:27 head2 marathon[27492]: [2015-05-04 11:19:27,441] INFO No matching offer for /group/app (need cpus=0.5, mem=384.0, disk=0.0, ports=Vector(0)) : id {
May  4 11:19:27 head2 marathon[27492]:   value: "20150428-051346-1388575636-5050-26039-O833490"
May  4 11:19:27 head2 marathon[27492]: }
May  4 11:19:27 head2 marathon[27492]: framework_id {
May  4 11:19:27 head2 marathon[27492]:   value: "20141126-052351-1405352852-5050-32174-0000"
May  4 11:19:27 head2 marathon[27492]: }
May  4 11:19:27 head2 marathon[27492]: slave_id {
May  4 11:19:27 head2 marathon[27492]:   value: "20150414-203931-1388575636-5050-26585-S14"
May  4 11:19:27 head2 marathon[27492]: }
May  4 11:19:27 head2 marathon[27492]: hostname: "some-slave.example.com"
May  4 11:19:27 head2 marathon[27492]: resources {
May  4 11:19:27 head2 marathon[27492]:   name: "cpus"
May  4 11:19:27 head2 marathon[27492]:   type: SCALAR
May  4 11:19:27 head2 marathon[27492]:   scalar {
May  4 11:19:27 head2 marathon[27492]:     value: 1.25
May  4 11:19:27 head2 marathon[27492]:   }
May  4 11:19:27 head2 marathon[27492]:   role: "*"
May  4 11:19:27 head2 marathon[27492]: }
May  4 11:19:27 head2 marathon[27492]: resources {
May  4 11:19:27 head2 marathon[27492]:   name: "mem"
May  4 11:19:27 head2 marathon[27492]:   type: SCALAR
May  4 11:19:27 head2 marathon[27492]:   scalar {
May  4 11:19:27 head2 marathon[27492]:     value: 6400.0
May  4 11:19:27 head2 marathon[27492]:   }
May  4 11:19:27 head2 marathon[27492]:   role: "*"
May  4 11:19:27 head2 marathon[27492]: }

So I think it's not because of rounding errors.

Hey @lins05 Can you provide the configuration of the mater and the slave as well as the definition of the application? Apparently it is not possible to say something on the logs that are provided.

We cannot proceed without more information...

authors: aquamatthias kolloch lins05

repo: mesosphere/marathon


text:
Kubernetes: add subcommand

Follow-up of https://github.com/mesosphere/multiverse/pull/23, now against version-1.x.
TODO:

[x] mesosphere/docs changes, bump version to v0.6.7
[ ] before clicking on merge: scripts/build.sh.

xref https://github.com/mesosphere/kubernetes/releases/tag/v1.0.6-v0.6.7

/cc @jdef @spacejam @karlkfi

@kensipe: can you take a look at the subcommand integration, i.e. command.json?

@sttts is this blocked on anything?

I think that my prior comment re: v0.6.6 not being changed everywhere to v0.6.7 still stands

@jdef had forgotten to push the last commit. PTAL

Did I say before we need a release checklist?

I've been roughly following this:

update version in package.json, config.json (docker image version) and
rebuild index.json using scripts/ tooling

create PR in mesosphere/mesosphere-docs w/ updated build #'s, link it to
the multiverse PR and mark it WIP until multiverse PR merges

once multiverse PR merges, merge the mesosphere-docs changes and wait for
staging rebuild to happen (usually within 1h); verify that your version
bump changes are good (manually walk through the steps in the entire doc)
then file a DOCS ticket in JIRA to request a merge from staging to prod
(link to the GH PR)

run and verify functionality of the k8s guestbook as a sanity check

On Mon, Nov 2, 2015 at 2:17 PM, Dr. Stefan Schimanski <
notifications@github.com> wrote:

Did I say before we need a release checklist?
—
Reply to this email directly or view it on GitHub
https://github.com/mesosphere/multiverse/pull/28#issuecomment-153129271.

Should we put that into an issue in k8sm with sub-tasks?

makes sense to me. GH issue w/ some checkboxes in the top-level desc w/
xref'd links where it applies
On Mon, Nov 2, 2015 at 2:43 PM, Dr. Stefan Schimanski <
notifications@github.com> wrote:

Should we put that into an issue in k8sm with sub-tasks?
—
Reply to this email directly or view it on GitHub
https://github.com/mesosphere/multiverse/pull/28#issuecomment-153136235.

we can create a template and then create a copy of that for each release. makes releases transparent.

Smoke tested on CCM dcos. Looks fine.

@kensipe this is ready for review PTAL

@stts, please have someone from your team review. @kensipe and our team are currently focused on the data agility reviews. Each team is responsible for reviewing their own submission. Thanks!

NAVER - http://www.naver.com/
keliong@naver.com 님께 보내신 메일 <Re: [multiverse] Kubernetes: add subcommand (#28)> 이 다음과 같은 이유로 전송 실패했습니다.

받는 사람이 회원님의 메일을 수신차단 하였습니다.

Thanks for the heads up! Will do.
On Tue, Nov 3, 2015 at 6:10 PM, Elizabeth Lingg notifications@github.com
wrote:

@stts https://github.com/stts, please have someone from your team
review. @kensipe https://github.com/kensipe and our team are currently
focused on the data agility reviews. Each team is responsible for reviewing
their own submission. Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/mesosphere/multiverse/pull/28#issuecomment-153517905.

@karlkfi want to give this a spin? If all looks good then we can merge.
On Tue, Nov 3, 2015 at 6:19 PM, James DeFelice james@mesosphere.io wrote:

Thanks for the heads up! Will do.
On Tue, Nov 3, 2015 at 6:10 PM, Elizabeth Lingg notifications@github.com
wrote:

@stts https://github.com/stts, please have someone from your team
review. @kensipe https://github.com/kensipe and our team are currently
focused on the data agility reviews. Each team is responsible for reviewing
their own submission. Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/mesosphere/multiverse/pull/28#issuecomment-153517905
.

LGTM
xref https://github.com/mesosphere/kubernetes-mesos/issues/600#issuecomment-154005208

:+1:
On Thu, Nov 5, 2015 at 4:52 AM, Sergiusz Urbaniak notifications@github.com
wrote:

Merged #28 https://github.com/mesosphere/multiverse/pull/28.
—
Reply to this email directly or view it on GitHub
https://github.com/mesosphere/multiverse/pull/28#event-455521374.

authors: elingg jdef s-urbaniak stts sttts

repo: mesosphere/multiverse


text:
Upgrade of Hadoop dependencies for 2.7 profile from 2.7.3 to 2.7.4

What changes were proposed in this pull request?
Resolves DCOS-45197

upgrade of Hadoop dependencies from 2.7.3 to 2.7.4 for Spark Hadoop 2.7 profile
fixes

CVE-2016-6811
CVE-2017-3166
CVE-2017-3162 (is available since 2.7.0, see release notes)

How were these changes tested?
Integration tests from mesosphere/spark-build
Release Notes

Hadoop dependencies upgraded for 2.7 build profile from 2.7.3 to 2.7.4 in order to fix org.apache.hadoop_hadoop-hdfs:2.6.5 vulnerabilities: CVE-2016-6811, CVE-2017-3162, CVE-2017-3166. org.apache.hadoop_hadoop-hdfs:2.6.5 is the last version in 2.6 line and doesn't contain fixes for given CVEs. It is recommended to use Spark with Hadoop 2.7 to avoid these vulnerabilities.

@samvantran I think it is safer to upgrade to the closest version with necessary fixes to minimize the amount of impact.

Makes sense

authors: akirillov samvantran

repo: mesosphere/spark


text:
fix (#minor); makerdao; fixed inaccurate TVL

This PR fixes inaccurate TVL/inputTokenBalance in maker markets, esp. ETH-A and ETH-B, as reported in #1695 . Basically, a refactoring I did to consolidate handlers causes liquidated collateral not removed from TVL. To fix this, I moved liquidatePosition call up to Cat.Bite() and Dog.Bark() when liquidation auction was first set up, from when liquidation auction ends (handleFlipEndAuction() and handleClipTakeBid()).
Deployment & validation (sync in progress)

test deployment: https://thegraph.com/hosted-service/subgraph/tnkrxyz/makerdao-ethereum?version=pending&selected=logs
validation dashboard: https://subgraphs.messari.io/subgraph?endpoint=https://api.thegraph.com/subgraphs/id/QmdWkF7LsHEq88hrMAMHdoCeNxLyzSqNZdd2qyHiCCpCXQ&tab=protocol

@tnkrxyz Was going to take a look at this, but looks like the deployment failed.

@tnkrxyz Was going to take a look at this, but looks like the deployment failed.

Fixed (hopefully) and redeployed.

looks like the syncing is failing

looks like the syncing is failing

Yup, a different issue. Fixed & restarted.

Issue resolved, thanks @tnkrxyz

@tnkrxyz deployment failed

thnks @tnkrxyz

@tnkrxyz @ishraq8 the protocol side revenue looks like there was an issue

repo: messari/subgraphs


text:
Libertinus Serif font missing

Compile a document with default font(which is Libertinus Serif under typst 0.12.0) generates wrong document. The font fallback to some random sans font.

It would be better to use typst-assets, instead of manually maintaining typst fonts in python/typst/fonts

Thanks for the advice @Coekjan, I've switch to use typst-kit instead.

authors: Coekjan ParaN3xus messense

repo: messense/typst-py


text:
git clone of repo fails, pip install lama-stack does not provide llama cli tool

Attempting to git clone this repo fails with no public read permission.
Doing a "pip install llama-stack" appears to work, but there is no llama cli tool afterwards.
So, this repo appears to be a nop, can't get anything to work at all.

I manually downloaded the repo and tried the manual install steps given in the README. This error is emitted:
ERROR: file:///home/bsenftner/meta/llama-stack-main/llama_stack does not appear to be a Python project: neither 'setup.py' nor 'pyproject.toml' found.

The README instructions are wrong, they say to run:
$CONDA_PREFIX/bin/pip install -e .
From the llama_stack directory, which is wrong, it should be run one directory above.

Yes, the directory to run pip install -e . is in the llama-stack directory, not llama-stack/llama_stack.

I installed in a venv and llama cli installed fine.

authors: bsenftner kvchitrapu yanxi0830

repo: meta-llama/llama-stack


text:
curl -X GET http://xxxx5000/alpha/models/list   return empty list

System Info
Collecting environment information...
PyTorch version: 2.1.2+cu118
Is debug build: False
CUDA used to build PyTorch: 11.8
ROCM used to build PyTorch: N/A
OS: Ubuntu 22.04.4 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: Could not collect
CMake version: version 3.19.3
Libc version: glibc-2.35
Python version: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (64-bit runtime)
Python platform: Linux-5.15.0-122-generic-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: 11.8.89
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration:
GPU 0: NVIDIA A100-SXM4-80GB
GPU 1: NVIDIA A100-SXM4-80GB
GPU 2: NVIDIA A100-SXM4-80GB
GPU 3: NVIDIA A100-SXM4-80GB
GPU 4: NVIDIA A100-SXM4-80GB
GPU 5: NVIDIA A100-SXM4-80GB
GPU 6: NVIDIA A100-SXM4-80GB
GPU 7: NVIDIA A100-SXM4-80GB
Nvidia driver version: 535.161.08
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.9.6
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.9.6
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.9.6
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.9.6
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.9.6
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.9.6
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.9.6
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Architecture:                         x86_64
CPU op-mode(s):                       32-bit, 64-bit
Address sizes:                        48 bits physical, 48 bits virtual
Byte Order:                           Little Endian
CPU(s):                               256
On-line CPU(s) list:                  0-255
Vendor ID:                            AuthenticAMD
Model name:                           AMD EPYC 7713 64-Core Processor
CPU family:                           25
Model:                                1
Thread(s) per core:                   2
Core(s) per socket:                   64
Socket(s):                            2
Stepping:                             1
Frequency boost:                      enabled
CPU max MHz:                          3720.7029
CPU min MHz:                          1500.0000
BogoMIPS:                             4000.37
Flags:                                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 invpcid_single hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 invpcid cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd amd_ppin arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold v_vmsave_vmload vgif v_spec_ctrl umip pku ospke vaes vpclmulqdq rdpid overflow_recov succor smca
Virtualization:                       AMD-V
L1d cache:                            4 MiB (128 instances)
L1i cache:                            4 MiB (128 instances)
L2 cache:                             64 MiB (128 instances)
L3 cache:                             512 MiB (16 instances)
NUMA node(s):                         2
NUMA node0 CPU(s):                    0-63,128-191
NUMA node1 CPU(s):                    64-127,192-255
Vulnerability Gather data sampling:   Not affected
Vulnerability Itlb multihit:          Not affected
Vulnerability L1tf:                   Not affected
Vulnerability Mds:                    Not affected
Vulnerability Meltdown:               Not affected
Vulnerability Mmio stale data:        Not affected
Vulnerability Reg file data sampling: Not affected
Vulnerability Retbleed:               Not affected
Vulnerability Spec rstack overflow:   Mitigation; safe RET
Vulnerability Spec store bypass:      Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:             Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:             Mitigation; Retpolines; IBPB conditional; IBRS_FW; STIBP always-on; RSB filling; PBRSB-eIBRS Not affected; BHI Not affected
Vulnerability Srbds:                  Not affected
Vulnerability Tsx async abort:        Not affected
Versions of relevant libraries:
[pip3] data-pipelines-pytorch==4.2.1
[pip3] numpy==1.23.5
[pip3] pytorch-ignite==0.5.0.post2
[pip3] pytorch-triton-rocm==2.3.1
[pip3] torch==2.1.2+cu118
[pip3] torchvision==0.16.2+cu118
[pip3] triton==2.1.0
Information

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

🐛 Describe the bug
llama stack run   .llama/distributions/llamastack-my-local-stack/my-local-stack-run.yaml
Error logs
INFO:     Application startup complete.
INFO:     Uvicorn running on http://['::', '0.0.0.0']:5000 (Press CTRL+C to quit)
INFO:     10.253.11.29:59248 - "GET /alpha/models/list HTTP/1.1" 200 OK
06:03:30.379 [START] /alpha/models/list
06:03:30.972 [END] /alpha/models/list [StatusCode.OK] (593.40ms)
INFO:     10.253.11.29:59298 - "GET /alpha/models/list HTTP/1.1" 200 OK
06:03:42.368 [START] /alpha/models/list
06:03:42.584 [END] /alpha/models/list [StatusCode.OK] (215.45ms)
Expected behavior
model name

I've been able to reproduce: https://github.com/aidando73/llama-stack-apps/pull/3/files#diff-1ebfaf6cb3592166b73835fa82333cb7109e7c624865c0039a7b22ff34aa27fa
Traceback (most recent call last):
  File "/Users/aidand/dev/llama-stack/llama_stack/distribution/server/server.py", line 158, in sse_generator
    async for item in event_gen:
  File "/Users/aidand/dev/llama-stack/llama_stack/providers/inline/agents/meta_reference/agents.py", line 153, in _create_agent_turn_streaming
    async for event in agent.create_and_execute_turn(request):
  File "/Users/aidand/dev/llama-stack/llama_stack/providers/inline/agents/meta_reference/agent_instance.py", line 179, in create_and_execute_turn
    async for chunk in self.run(
  File "/Users/aidand/dev/llama-stack/llama_stack/providers/inline/agents/meta_reference/agent_instance.py", line 250, in run
    async for res in self._run(
  File "/Users/aidand/dev/llama-stack/llama_stack/providers/inline/agents/meta_reference/agent_instance.py", line 568, in _run
    result_messages = await execute_tool_call_maybe(
  File "/Users/aidand/dev/llama-stack/llama_stack/providers/inline/agents/meta_reference/agent_instance.py", line 833, in execute_tool_call_maybe
    assert name in tools_dict, f"Tool {name} not found"
AssertionError: Tool code_interpreter not found
[INFO] role='assistant' content='' stop_reason=<StopReason.end_of_turn: 'end_of_turn'> tool_calls=[ToolCall(call_id='effb0bb7-ebb2-4baf-8a3a-941c99dc0cca', tool_name=<BuiltinTool.code_interpreter: 'code_interpreter'>, arguments={'code': 'import os\nfrom llama_index import LLaMAIndex\nfrom llama_index.finer_tuning import fine_tune_orma\n\n\n# Initialize the LLaMA index\nllama_index = LLaMAIndex()\n\n\ndef main():\n    # Load the pre-trained Llama model\n    model_name = "large"\n    model_path = os.path.join(llama_index.model_dir, f"{model_name}.pth")\n\n    # Fine-tune the loaded model on a custom dataset\n    fine_tune_orma(\n        model_path=model_path,\n        train_data_path="path/to/custom/train/data",\n        eval_data_path="path/to/custom/eval/data",\n        batch_size=32,\n        num_epochs=5,\n    )\n\n\nif __name__ == "__main__":\n    main()'})]

Let me look into it


text:
qtbase: Add a kde DISTRO_CONFIG

If trying to build KDE there are extra package config options required.
This patch adds a KDE DISTRO_CONFIG that enables the extra
PACKAGE_CONFIG options required.
Signed-off-by: Alistair Francis alistair.francis@wdc.com

I just pushed an update that fixes the commit message.


text:
Bumped testinfra to 1.16.0 due to testinfra bug.

This is a request to bump testinfra to 1.16.0 because they've fixed PATH issue that prevent using some modules (like sysctl) on Red Hat-type systems.
This change has passed all Tox tests (except some rubocop because I didn't installed it)

Thanks @camillehuot

repo: metacloud/molecule


text:
Update description about MetaDrive

What changes do you make in this PR?

Please describe why you create this PR

Checklist

[x] I have merged the latest main branch into current branch.
[x] I have run bash scripts/format.sh before merging.
Please use "squash and merge" mode.

Merge if that's OK

repo: metadriverse/metadrive


text:
WP.org-SVN/Release out of sync with GitHub repo

Hi guys,
I am mainly concerned with the WordPress Plugin and have some free time on my hands.
Why is the GitHub code "older" than the release version in the WP.org SVN?
Could you please push the changes to GitHub?

I have been doing the same the last few days, too!

repo: metafizzy/infinite-scroll


text:
added Simplified Chinese translation

I only added a text toggle button because I think the flag of China is not a good idea.  Maybe it will involve Chinese political issues.

 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.

authors: CLAassistant SkywalkerJi

repo: metaflow/apex-recoil


text:
🌱 fix distroless:nonroot pinning

Fix the way nonroot is part of the image pinning.

/test-centos-e2e-integration-main
/test-ubuntu-integration-main


text:
Ability to cancel individual AsyncControllers

I'd like to suggest having the ability to cancel AsyncControllers individually

You can cancel an individual AsyncController if you create it with an identifier.
val key = "key"
key.async { ... }
...
//to cancel
key.async.cancelAll()

authors: julianostarek tonilopezmr

repo: metalabdesign/AsyncAwait