Add Onboarding docs for info gateway

IMPORTANT: Where possible all PRs must be linked to a Github issue
Fixes #2851
Engineer Checklist

[ ] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[ ] I have added any strings visible on UI components to the strings.xml file
[ ] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[ ] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[ ] I have built and run the FHIRCore app to verify my change fixes the issue and/or does not break the app
[ ] I have checked that this PR does NOT introduce breaking changes that require an update to Content and/or Configs? If it does add a sample here or a link to exactly what changes need to be made to the content.

Code Reviewer Checklist

[ ] I have verified Unit tests have been written for any new feature(s) and edge cases
[ ] I have verified any strings visible on UI components are in the strings.xml file
[ ] I have verifed the CHANGELOG.md file has any notable changes to the codebase
[ ] I have verified the solution has been implemented in a configurable and generic way for reuseable components
[ ] I have built and run the FHIRCore app to verify the change fixes the issue and/or does not break the app

note that I consolidated this all into the ENGINEERING > Backend section cc @rowo

@sharon2719 for any previous references to the gateway and it's deployment, we need to align it with the new documentation here.

@sharon2719 for any previous references to the gateway and it's deployment, we need to align it with the new documentation here.

Thanks @ndegwamartin I will make the changes to the docs with the relevant urls

this looks great! I think that's exactly what I would have suggested


Poor camera quality when passing in C++

Hi everyone,
I've successfully made my ARTemplate project in C++ (woohoo...) But since the camera is blurred and it became much more difficult to track an image. The weird thing is I have a better quality if I use BP.
Does someone know where to or how to configure that ?
Best regards,
Alexandre

That is really wired. C++/Blueprint shouldn't affect the background image rendering. Did you do anything different to render the camera image in your c++ project?

Nope just the same pipeline for starting ARCore session than in the AgmentedImage project. But i've started it from blank c++ project so maybe I've missed a parameter where I can choose the resolution of the camera or set autofocus... That doesn't remind you a parameter ?
Thanks for  the reply btw.

Do you mind send me a project to reproduce the issue? There is no camera resolution configuration yet in GoogleARCore Unreal plugin. It is a fixed 1920x1080 resolution for camera texture right now.

It seems to be more like a focus problem. But yes how can I send it to you ?

@alexandreMarie Can you upload it to a Google drive and share the link here?

https://drive.google.com/file/d/1I0H7cDtQOUE1hZ7EREDJFw7x-uICesLI/view?usp=sharing

The brighter and blurred one is from the CPP project and the darker is from the BP project.
But for now I will let this thread on stand by because my client want this to turn on tablet. And I will have to move to ARKit to use iPad. :/

@alexandreMarie Looking at the screenshot, it looks like your CPP project has mobile HDR turned on in project settings. The camera texture is rendered in linear color space when mobile HDR is on so you will have to tonemap the frame output to gamma space. We recommend to turn off mobile HDR in general unless there is a specific use case in your app.

Thanks @bopangzz ! It was that :)


File Upload

How to do image file upload ??
{id: 'imagefile',type: 'file',name:'imagefile'}
and
$.ajax({                         url : "/admin/submit",                         type: "POST",                        contentType: false,                        cache: false,                        processData:false,                        data : new FormData(this.swalForm),                         success: function(data, textStatus, jqXHR)

i have this problem and have you ever solved it ?

ok，i have looked the code and found out swal-forms doesn't deal with this situation . you can  go to   function toValuableAttrs  to add some codes to solve it  in its source code in swal-forms.js

Could you please make a pull request with your changes? :)


[HUDI-6088] Do not set the optmistic concurrency mode when MDT is ena…

…bled
Change Logs
Follows HUDI-5887, this is the tweak in Flink side.
Impact
none
Risk level (write none, low medium or high below)
none
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

CI passed: https://dev.azure.com/apache-hudi-ci-org/apache-hudi-ci/_build/results?buildId=16412&view=results


Extension API to access and manage Debug Configurations

I'd like to request an API for extension developers to use in order to retrieve, modify, and add debug configurations to launch.json.
Benefits:

reduce the risk of data corruption when extensions directly write to the file (for example: writing an invalid structure)
encapsulate handling whether or not the file exists in the workspace
encapsulate file content concerns such as existing formatting/comments

It's not quite the same thing, but are you aware of the DebugConfigurationProvider API?

@Gama11 absolutely -- the nuance with DebugConfigurationProvider is that provideDebugConfigurations only kicks in when populating a launch.json file from scratch. There are times when an extension would want to add more entries into an existing launch.json, for example when users add more entrypoints into a workspace.

This is mostly covered by #88230.

I like the proposal in #88230 .
I'm unclear if that proposal provides users with a way to see and insert new debug configurations that a DebugConfigurationProvider detects after launch.json has been populated.
If that is (or can be) accommodated in the 88230, this is great. If not, this feature request would allow extensions to surface suitable gestures to users, which in turn can update launch.json.

As part of #88230 it has become possible to add a dynamic launch config to the launch.json by clicking in the gear button on the right hand side of the QuickPick menu:


Critical specialization effect for the crossbow and pick are missing in the en.json

From remaster pg.283

Picks too

There is no note created for those.


"Update Forum Thread" not working as expected

I am not sure how everyone else is updating their shop, but to make any updates on mine, I need to select/deselect a stash tab from left every time for the forum code to be updated. Am I missing something? Shouldn't "Update Forum Thread" automatically include any recent price changes I made?

The "Update Forum Thread" button only posts what's in the text area to the forum. I'll look at making a change so that it updates the text first.


[Menu] Static values

Right now the menu widget reacts on the result set to provide only the most meaningful facet values for the given search. However in the case of an editorial website, this can be out of the current practice of those websites where the menu is generally static.
What about adding an option or provide a new widget that would fetch the facet values during the init and use those values to always display options that may not be returned from the search?

I think an option staticValues would be the easiest to use, but might some extra complexity to the implementation, or would it be a simple one-time if?

Do we want to:

be able to provide manual values to a widget like menu?
example:

menu({
  items: [{label: 'Oranges', value: 'orange'}]
})

Will then be the only values being displayed, and the counts would be also filled by reading the API.

add an option to express "even if count for this a facet value is 0, I want to keep it"

Are those two options in the scope/context of what you proposed?
About 1. We had the requirement/feature idea by @Shipow at some point to be able to just create a menu with predefined items where the order would just stick to this. But if we have other ways of answering 1. (for example, with transformItems in react-instantsearch), then we are fine I guess :)

After discussing with @rayrutjes he seems to have a pretty solid implementation (without InstantSearch.js). His menu fetches first "all the values" with a request using search for facet values. There are no subsequent updates but we could imagine doing a rendering to display the counts. The order is based on the count (most used facet value first).
That could be the target behavior.

We now explain all these solutions in the documentation section "Modify the list of items in widgets". They mostly leverage the transformItems option introduced in 2.10.0.
I'll close this issue – if you feel like this doesn't fully answer your needs for a specific use case, feel free to open a new issue.


Implement API specs via cornice_swagger

Implemented generation of JSON-formatted API specs using cornice_swagger. The specs can be generated by sending a GET request to the backend, as  /-/api_doc. The output can be pretty-parsed at  parsed through an online JSON parser, or  , or using any online JSON parser.
Closes #308
NOTE: These commits require the cornice_swagger import (use pip3 cornice_swagger) & addition of hub_api_version in the development.ini file, and a *cornice>=2.0.0 (preferably 2.3.0) & cornice-swagger to be added in required installations (in /senic-hub/setup.py).
TODO: (In subsequent commits)
[1]. Add Schemas for some PUT requests & responses to GET requests.
[2]. Discuss on whether to continue using online parser for JSON specs, or run a node server to access the SwaggerUI pretty-parsed webpage for the same.

The swaggerUI parser looks something like this:

The SwaggerUI parser looks something like :+1:

This is a very good start, I think we need to make sure that upgrading the version of cornice doesn't have unintended consequences.
In addition each endpoint should provide an example output.
@tomster we talked about having a development spin of the senicos image, perhaps we could include node + swagger just in that build?

@kelada : I have added the fixes required post-upgrading the cornice version. I'll watch out for any other consequences. I guess I've covered all the attributes where cornice is being used.

@kelada regarding the consequences of upgrading cornice, i think we should be good, since we do have tests. sticking to the older version was just pure stasis, there's no hard reason to not upgrade. in fact, this is a good occasion to finally upgrade :)
for development i think it's fine to run nodejs to generate live swagger views but i'm against shipping the product with a running instance of nodejs
this also means that it's easy to add npm etc. for the development build by not adding it as a recipe on the yocto level but simply adding it to the development playbook which needs to be applied after booting the image anyway


[Feature] Add ability to disable emphasis/highlight functionality of tooltip axis trigger

What problem does this feature solve?
It would be really helpful to be able to render the tooltip axis trigger (e.g. a line or a cross) while disabling the highlight/emphasis functionality it triggers on the underlying series. This would probably be a configuration option for tooltip or tooltip.axisPointer.
I created a very simple example where you can see the behavior based on one of the line chart examples.
https://codesandbox.io/s/line-chart-tooltip-highlight-issue-ob1ob0?file=/index.js
When you have a line chart with multiple series, the axis trigger tends to highlight all the series, which is often unhelpful and can be really confusing to users.

If you focus very specifically on a line in this use case, you get a single focus. This behavior is fine.

If you set tooltip.trigger to none, you get more helpful highlight behavior where nothing is highlighted when you're outside a series, but you lose the visual assistance of the axis pointer tracking line to orient yourself within the chart.

A single series is highlighted when you are hovered over it, so that behavior is the same.

I tried a few different combinations of series, tooltip, and axis pointer configuration options to see if I could generate what I wanted with the current functionality, but I could not find a way. It seems like it's currently possible to disable highlight behavior entirely and disable the tooltip axis pointer. I'm hoping for the ability to have only series-level highlight functionality while rendering an axis pointer.
What does the proposed API look like?
This would probably be a configuration option for tooltip and/or tooltip.axisPointer. I do not have strong feelings about the name of the option to trigger this behavior. I see a silent option on some other parts of the API, so maybe having tooltip.axisPointer.silent: true could trigger "render but do not highlight" behavior, but I'm not sure if that would break other tooltip functionality (e.g. showing the tooltip on hover). Maybe a more specific emphasisTrigger or something like that would be more helpful. I'm open to whatever API approach folks with more experience with the internals of the library feel is best.
It looks like the implementation change would probably go hereabouts in the code. https://github.com/apache/echarts/blob/f5bb3b0c81f9843f73f57a0b01a35488f7795dd6/src/component/axisPointer/axisTrigger.ts#L447-L495

You can acheive this by using triggerTooltip: false (and you may want to take a look to into the trigger: "none")
https://codesandbox.io/s/stacked-area-chart-forked-emk9qt?file=/index.js
I still do agree we should have at least a "show" or "silent" to make this more dev friendly (I lost some hours to find a solution)

I gave that a try in a modified version of my original example, and I'm still seeing similar behavior. Am I doing something slightly wrong in here?
https://codesandbox.io/s/line-chart-tooltip-highlight-issue-trying-with-triggertooltip-false-56elon?file=/index.js

Taking a look at the code a little more, it looks like triggerTooltip only impacts the rendering of the tooltip itself inside axisTrigger, but not the call to the dispatchHighDownActually function, which triggers the highlighting. There's a bunch more complexity inside modelHelper.ts that uses triggerTooltip alongside a bunch of other values that I didn't dig into more deeply, so might be something in there isn't playing nicely?
https://github.com/apache/echarts/blob/f5bb3b0c81f9843f73f57a0b01a35488f7795dd6/src/component/axisPointer/axisTrigger.ts#L345-L347
https://github.com/apache/echarts/blob/f5bb3b0c81f9843f73f57a0b01a35488f7795dd6/src/component/axisPointer/axisTrigger.ts#L206

I don't see anything wrong on your last example, I tough you wanted to hide the tooltip but keep the highlight dashed line. But I probably misunderstood what you're trying to achieve.

I don't see anything wrong on your last example, I tough you wanted to hide the tooltip but keep the highlight dashed line. But I probably misunderstood what you're trying to achieve.

To clarify what I'm hoping to achieve is:

Show the axis pointer (i.e. the line that follows the mouse pointer to help orient the user).
Disable the axis pointer from triggering highlight/emphasis behavior.

I think our team has use cases for showing and not showing the tooltip alongside the above behavior.

EDIT: If you want to do the inverse, hide the highlight and still see the tooltip, then you need to change the width of the axisPointer: https://codesandbox.io/s/basic-line-chart-forked-lswt8t?file=/index.js

Making the axis pointer 0 width would make the axis pointer functionally invisible, so not quite what we're looking for.

FYI, I'm going to look into making a pull request for this feature.

I agree that this should be a useful feature. Glad to see that you made a pull request!


Fix Abseil build command

@pifon2a I've noticed the BUILD_COMMAND is broken. You're setting ABSL_BUILD_COMMAND, but using ABSEIL_BUILD_COMMAND (effectively empty). Somehow this doesn't confuse newer CMakes, but the one you install on Trusty gets confused and interprets this as a no-op build step. This causes the indigo pipeline in cartographer_ros to fail.
Use the cross-platform build command instead:
https://cmake.org/cmake/help/latest/module/ExternalProject.html#obtaining-project-properties (just above the linked paragraph)

@ojura You are the hero of the day. Thank you a lot!

 I did warn you, though :D https://github.com/googlecartographer/cartographer/pull/1301#issuecomment-406353293

@ojura yeah, cmake is weird.  :)

@wally-the-cartographer merge

Merge requested by authorized user pifon2a. Merge queue now has a length of 1.

@pifon2a also WDYT about throwing in a find_package(Abseil REQUIRED) into cartographer-config.cmake.in so Cartographer users don't have to it by themselves?


Plotting LineString

Hi,
I think there's a bug when setting a geopandas LineString column as the geometry column, and running gdf.plot_bokeh()
if the column name isn't 'geometry' we get an error 'geometry not in index'
only after i changes the column name to geometry I got the plot
actually I think this happens not just for LineString also for 'regular' Point..
gdf['return_point'] = [Point(xy) for xy in zip(gdf["return_lng"],gdf["return_lat"])] gdf['take_point'] = [Point(xy) for xy in zip(gdf["take_lng"],gdf["take_lat"])] gdf['line'] = [LineString(ab) for ab in zip (gdf["take_point"], gdf["return_point"])] gdf.set_geometry('line',inplace=True) gdf.crs = {'init' :'epsg:4326'} #gdf.plot_bokeh() test= gpd.GeoDataFrame(gdf,geometry='line') test.crs = {'init' :'epsg:4326'} test = test.rename(columns={'line': 'geometry'}).set_geometry('geometry') test.plot_bokeh()

Hi,
thanks for the bug report. Never considered the case that you wouldn't call your geometry column "geometry". Should be an easy fix, but I haven't got any time right now. Hope that I can fix that soon. Hope you can live with your workaround.
Best Patrik

Hi @BatchenE,
in the next release there will be a "geometry_column" parameter for plotting GeoDataFrames with geometry-columns of a different name than "geometry".
I would close this issue if this is okay for you.
Best Patrik


TVTouchable: Skip if findNodeHandle thrown error

Summary
I got the following error with component used TVTouchable on unmount.
ExceptionsManager.js:158 Error: Unable to find node on an unmounted component.
Changelog
[General] [Fixed] - Skip if findNodeHandle thrown error in TVTouchable
Test Plan
I'm upgrading react-native-tvos to 0.71 for a project, and it's working fine with this fix (by patch).

I've a minimum example for reproduce this issue.
const [showFirst, setShowFirst] = useState(true);
return (
  <>
    {showFirst && (
      <TouchableOpacity onPress={() => setShowFirst(!showFirst)}>
        <Text>First</Text>
      </TouchableOpacity>
    )}
    {!showFirst &&
      [0, 1, 2].map(key => (
        <TouchableOpacity
          key={String(key)}
          onPress={() => setShowFirst(!showFirst)}
        >
          <Text>Key {key}</Text>
        </TouchableOpacity>
      ))}
  </>
);

The issue will be caused on setShowFirst(!showFirst) with unmounting the 3 touchables. It doesn't happen when its number is less than 3.
After try to reproduce that, I think the main problem is some event issue from TVEventHandler, although I haven't had time to figure out clearly, I'll open a new issue for this.


Icons are not matching to android 13 default icon size

About this discussion
Looking at aosp 13 they have changed the size of icons instead of the regular android 12 this seems to not be changed this may or may not be related to lawnicons but it's supposed to make more sense looking at the previous versions of Lawnchair

As see in this image it can be seen like this using it in other launchers it is the same consistency is supposed to be applied

Seems to be lawnicons instead of the launcher if the developers could resize them it would be better


Add Bill of Material pom file to TracEE (resolves #115)

Looks good!

Still needs to be documented but thats something for the tracee.io site :)

LGTM

Btw. we need to reconsider how we release a bom if we start to version single modules independently.


Opening the selector from Visual-mode, I can not input text to filter values

Like a vim.lsp.buf.range_code_action(), some features may be called from the Visual-mode.
When I called them with this plugin from Visual-mode, keeping the mode, so I cannot input text to filter choices.

Should probably be fixed from telescope side :thinking:

We recently merged a PR that fixed opening telescope from visual mode.
Closing if it still doesnt work feel free to reopen :)


Info.plist Privacy Properties In iOS 10

Since iOS 10 we have to declare Usage Description keys in info.plist
<key>NSPhotoLibraryUsageDescription</key>
<string>Text</string>
<key>NSCameraUsageDescription</key>
<string>Text</string>
<key>NSCameraUsageDescription</key>
<string>Text</string>
<key> NSMicrophoneUsageDescription </key>
<string>Text</string>
NSPhotoLibraryUsageDescription
NSCameraUsageDescription
NSMicrophoneUsageDescription
I think this should be added to the README.md.

Will look at that. Thank you.

I've added this to the README, thanks for reporting.


Local LA Meetup Map ready!!!

Here is the page, with maps, with data in the maps:
@caseytherocket
@thebearingedge
@IanDCarroll

LGTM 👍


Feature Request: Allow Uint8 or ObjectURL blobs in deserialize filtered query

Was hoping to be able to place flatgeobuf into a webworker and provide range requests/filtered requests from arbitrary serialized geojson features.
However, the range request feature with spatial filter seems directly tied to the HTTP/request system.
Reviewing the code, it looks tightly coupled.
It seems like it should just be given an  interface that returns various slices of data from . Is it possible to make a cheap object interface that can be substituted for the <url> input.

Yeah I agree it would make sense to decouple it.

So, I just monkey patched the javascript library's fetch as follows:
//interceptFetch.js
globalThis.fetch = async (...args) => {
    const [url, fetchOpts] = args

    for (const [route, handler] of handlers) {
      if (route({ url, fetchOpts })) {
        const response = handler({ url, fetchOpts })
        return response
      }
    }

    return origFetch(...args)

import rangeParser from 'range-parser' // npm package
//handler...
    function appendToUint8Array(arr, data) {
      const newArray = new Uint8Array(arr.length + data.length)
      newArray.set(arr) // copy old data
      newArray.set(data, arr.length) // copy new data after end of old data
      return newArray
    }
   const fcFgb = ...data
    if (fetchOpts?.headers) {
      let chunks
      for (const header of Object.keys(fetchOpts.headers)) {
        if (header.toLowerCase() === 'range') {
          const parser = rangeParser(fcFgb.length, fetchOpts.headers[header])
          chunks = new Uint8Array()
          for (const { start, end } of parser) {
            const chunk = fcFgb.slice(start, end)
            chunks = appendToUint8Array(chunks, chunk)
            console.log('range', { start, end })
          }
        }
      }
      if (chunks) {
        fcFgb = chunks
      }
    }
    return new Response(fcFgb, {
      status: 200,
      headers: {
        'content-type': 'application/vnd.flatgeobuf',
      },
    })


Settings - Bot and Composer settings (Sang)

This has been reviewed and moved to Master Design Specs as well.
I think it may be the same as this?
https://github.com/microsoft/BotFramework-Composer/issues/2573

Yup same


Add toolchain prefix mappings for s390x

This adds prefix mappings for s390x to allow cross-compiles without having to define environment variables.  Should match other Linux platforms.

Thanks!


The Content-Length for the copy source is not specified.

I got this error when submitting a manifest in PR #172

I also got this error when submitting a manifest in PR #717

This appears to have been fixed #717 was merged. #172 seems to have a hash-mismatch.


Here is the Log part about the error (it repeats up to attempt 12):
Cloud SQL Proxy installation succeeded
About to run 'run_validation' with retries...
Metastore connection URL:	 jdbc:mysql://localhost:3306/hive_metastore
Metastore Connection Driver :	 com.mysql.jdbc.Driver
Metastore connection User:	 hive
Mon Sep 23 11:06:40 UTC 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Hive distribution version:	 2.3.0
Metastore schema version:	 2.3.0
schemaTool completed
[2019-09-23T11:06:44+0000]: Failed to bring up Cloud SQL Metastore
'run_validation' attempt 1 failed! Sleeping 1.

Since it worked last time at SDK 240.0.0 and stopped working on 263.0.0, what has changed and how to circumvent this issue?
If the solution is to pass the useSSL=false flag, how can I do it in the startupScript as I found no documentation within this Git repo?
PS.: Connecting to the metastore using Hive CLI works fine. Only issue is with Beeline CLI.
Thank you!

We recently released few fixes for services start up, please reopen if your issues persists.


cppguide: Clarify use of nonstandard extensions

Was reviewing as part of platform review today. Came across this section, and remembered we had some direct usages of stuff like __PRETTY_FUNCTION__.

This change is

In general, Drake will always have small niches of code that need to violate GSG.  It is a guide after all, not a judge jury and executioner all on its own.  I don't think we should try to upstream every practical caveat that we need to carve out back into the guide.  There will be a lot of them!
If someone used a compiler extension in a PR, we should certainly question it during review.  I think the current (main branch) guide text is sufficient for that purpose as it stands.  If you want to try to clarify it that's fine, but (as Sherm notes) it should definitely keep the spirit of what is here already -- that compiler extensions are broadly dispreferred.


Initial Theme Development

[ ] Initial Theme

[ ] focus on typography and structure of the content
[ ] create required templates to show the primary (text-based) content
[x] create required structure for SASS (5-1 pattern according to Simple SCSS playbook)

[x] close #27 (as of 4f9cb56d18ddabf9639b5260302ad240a69adec6)

TODO while developing

[ ] <blockquote> elements should have a visual style with a ::before pseudo-element. As of now, this element is clipped in Firefox (Ubuntu 22.04)

[x] Verify in Chrome (Win10): Result: No clipping in Chrome
[x] Verify in Edge (Win10): Result: No clipping
[x] Verify in Firefox (Win10): Result: No clipping
[ ] https://css-tricks.com/snippets/css/simple-and-nice-blockquote-styling/
[ ] it might be just a font issue; as of now, the ::before text is formatted with serif, which relies on the system font that is used for that keyword... (see #30)

[ ] Hyphenation in CSS (https://stackoverflow.com/a/49471381)
[ ] run todo from repository root!

font-stretch is not yet W3C Standard, so html5validator fails during CSS validation.
Add another ignore string to corresponding job.


Ability to return arrays from includes

It occurred to me today that it'd be handy to be able to return an array from an include, rather than explicitly ResourceAbstract.
Reasoning:
I have a model Booking, which has a transformer, returning essential data. If I needed some extra data returned, it'd be handy to be able to use something like includeExtraData, which simply returns an array of the extra data.
Does this sound sensible? Should this data always go in meta? or am I missing something completely? Either way, awesome package!

Depends what the data is but it sounds like it belongs to meta.

@leon13  the content if includeExtraData si actual data (like embeded data) or info about data (like pagination)?
For example JSOANPI format has a new key besides data and meta, named included. For example, your response might look like this:
{
   "data":[

   ],
   "includeded":[

   ],
   "meta":{
      "pagination":{

      }
   }
}

I agree with @jasonlewis in that this belongs in Meta.


Update version info in README.md

The README file says that v1.0 has been released, but later has
apparently obsolete text about how the software is pre-release and the
team is working towards a v1 release. This change edits that text to
remove the content about being a pre-release version.

thanks very much for correcting this :)


Update ci_arm Docker tag

Update ci_arm image to use tag tlcpack/ci-arm:20231013-060139-71caa19f9

Update ACL to 23.05 version

Tested at https://github.com/apache/tvm/pull/15930
cc @neildhickey @leandron @ashutosh-arm @tqchen @areusch

Thanks @Liam-Sturge @neildhickey


table formatting is slightly wack

The default styling doesn't paint borders around tables, which makes them slightly strange looking.

What I would really like I think is an option that makes formatting exactly like what GH does, if that's an easy thing to do (no idea).

:+1:


No more than 9 jobs starts

I listed 3 final drives and 3 temp drives 1tb each, so my setting were 144 total plots, 12 plots in parralel, delay 35min, RAM 4000, and 8 threads each(may be i dont need that much). The problem is that after the 8th queue was running for 1:35min no more queues were started, some time later i check and finally the 9th job has started. but now 12 hours has passed and the queues 10, 11, 12 are listed as running in "Jobs queues" but in Queued Plots they are not listed.

Sorry about this, I put the max number of runspaces at 10 during my testing, but meant to change to be dynamically assigned based on processor count. This will be fixed in the next release.

Please if you put a limitter (cpu ram etc) put also bypass button for it.
Waiting with hurry :=)

So theoretically if i spawn two jobs with 6 queues each it should work? or is it the total number of plots parallel that is limited?

I have fixed the hard coded limit on runspaces so you should not be limit to the number of queues you have. I am sorry that I missed that on initial release. I have also added some other features, and removed the limit on the RAM. Please open up a new issue is new problems arise from this release. I really changed more than I should in one release but there was a lot of feedback that I wanted to address.


added django 1.10 to travis matrix

@nemesisdesign I will send another PR to pass builds

@auvipy looking forward to it. Thanks.

@auvipy
Any progress on this?

@blueyed, if you want to help out, you may want to take a look at #120

@nemesisdesign
It is not clear to me what the problem is.
I thought @auvipy might have some insight, since I could imagine this being a problem with the test suite only.  It sounded like there was a plan about how to fix the build.

@blueyed yup you are right.


Add expiration property to authenticated user info

Questions
Q. How long should a user stay authenticated?
Q. Should the lifetime of a user's session be extended on each interaction?
Q. Should the lifetime be fixed, forcing the user to authenticate again?
Q. Should these facilities be configurable?

Partially implemented for Basic auth.
Need to consider OIDC and other auth schemes.
Need to implement logic that removes expired auth entries from process stash.

After some discussion, we've decided that this issue applies to Basic authentication only. OIDC and other schemes will be handled on an as-needed basis.

Q. How long should a user stay authenticated?

Basic authentication will last for a specific amount of time defined by the administrator. The value will be defined in the config file.

Q. Should the lifetime of a user's session be extended on each interaction?

No. Until that is a use-case for automatic extension, the lifetime of a session will be fixed.

Q. Should the lifetime be fixed, forcing the user to authenticate again?

Yes. An appropriate HTTP status code will be returned indicating that the user should authenticate again.

Q. Should these facilities be configurable?

As stated earlier, the behavior is controlled by the admin via the config file.

With that said, the current implementation satisfies all of these requirements. Therefore, this issue can be closed.


#2479 Switch to nats 0.8.0

Signed-off-by: Christian Kreuzberger<EMAIL_ADDRESS>Finally fix #2479 by switching to nats 0.8.0.
Apparently something has changed with the service-naming, hence I needed to add fullnameOverride.
Integration Tests: https://github.com/keptn/keptn/actions/runs/938419801

We ran into an issue when upgrading from an older version to this:
Error: Could not complete Keptn installation: Error when installing/upgrading Helm Chart keptn in namespace keptn: cannot patch "keptn-nats-cluster" with kind StatefulSet: StatefulSet.apps "keptn-nats-cluster" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', and 'updateStrategy' are forbidden


New type: plugin

As proposed in #21, plugin may be a nice software category we have not considered yet.

On Fri Sep 8, 2023 at 4:30 PM CEST, Daniel Garijo wrote:

As proposed in #21, plugin may be a nice software category we have not considered yet.

Agreed, something like SoftwarePlugin would make sense to include,
with a proper definition. It would be an extension/module to existing
software. We do have to make sure to clearly distinguish it from the
more generic SoftwareLibrary


interpreter planner refactor

Enhancement
background
Currently tiflash's interpreter is designed based on DAGQueryBlock.
DAGQueryBlock is designed to coprocess read, and it can handle simple queries well.
However, there is no way to handle the complex query of MPP, so the DAGQueryBlock tree is introduced, which is a compromise that makes the code more complicated and affects the subsequent iterative development.
We need to refactor the interpreter code in a plan visit way.
design
Therefore we introduce a new abstraction layer called PhysicalPlan to replace DAGQueryBlock.
It will be responsible for the processing of ExpressionAction and the generation of BlockInputStream.
We call this organization of code the planner.
DAGRequest (executor tree or executor array).
     |
     |
     v
physical plan <---+
     |            |
     |            | optimize
     |            |
     +------------+
     |
     |
     v
BlockInputStream

why planner
Most databases are designed based on planner.

Friendly for database developers to understand code.
We can improve tiflash with a general approach from the DB area, such as pipeline mode.

todo list

[x] public desgin doc

#4743

[x] Small refactoring of Interpreter before planner refactoring

#4118

[x] interpreter test framework

#4609

[x] planner refactory

[x] poc #4601
[x] Introduce PhysicalPlan/planner, add switch and set it to planner by default

https://github.com/pingcap/tiflash/pull/4820

[x] Replace all operators with PhysicalPlan

[x] common plans: projection/agg/filter/exchange_(sender/receiver)/limit/topn

https://github.com/pingcap/tiflash/pull/5143

[x] window function

https://github.com/pingcap/tiflash/pull/5363

[x] join

https://github.com/pingcap/tiflash/pull/5320

[x] table scan

https://github.com/pingcap/tiflash/pull/5335

[x] remove DAGQueryBlock
- https://github.com/pingcap/tiflash/pull/5381

[x] merge to master

feature branch: https://github.com/pingcap/tiflash/tree/planner_refactory
https://github.com/pingcap/tiflash/pull/5493
https://github.com/pingcap/tiflash/pull/5321

all merged.


Allow aligned_index to be None

Description
There was a bug previously that didn't actually allow aligned_index to be unset in the storage creation calls. This fixes that.

bors try


Accessing UI is deprecated. Call 'getErrorsMessages' on the instance directly.

After I updated to 2.7.2 it displays this message Accessing UI is deprecated. Call 'getErrorsMessages' on the instance directly. how can I fix it?
this is my code:
ParsleyUI.getErrorsMessages(Instance)

Instance.getErrorMessages...
Future questions on StackOverflow please.

this may helps: https://stackoverflow.com/questions/23008008/display-parsley-errors-in-bootstrap-tooltip

change ParsleyUI.getErrorsMessages(Instance)to Instance.getErrorsMessages(); could works, too!


feat(dateparser): Allow overriding of parsers.

Proof of concept for #6370.

This mostly LGTM, just needs a little cleanup.

@wesleycho how's that? I split the original test out into a few to better articulate the intent.

I think the test cases can be simplified - what is mainly of concern is whether you can grab the current parser (and thus the original one), and whether you can override the parser used. That way if a failure in the overriding is present, it is easily isolated by the tests.

So basically remove the "clears cached parsers when overridden" and we're good as it is implied in "can set a parser back to the original"?

The two specs should read
it('should get the current parser'
And
it('should override the parser'
Or something like that, and test those scenarios

Ok, simplified. I still think it's important to have a test for making sure that the parsers are cleared when a parser is overridden. Basically guarding against this line (https://github.com/dougludlow/bootstrap/blob/b02815b446ad03df6eeb8a7ac054b13d9669f579/src/dateparser/dateparser.js#L258) being removed. If they aren't cleared the overridden parser will not be used.

@wesleycho any other feedback here?

LGTM, going to schedule for 2.4.0


ARTEMIS-5055 AIO not detected in official Ubuntu Docker image

@jbertram should we redo the tag?

I figure we'll do another release pretty soon so I don't think that's necessary.


Protection One / Alarm.com now requires 2FA

@uvjustin - I used Protection One/Alarm.com as my security provider. I had the same issue noted in #21 for a few days but it resolved itself. I rebooted 2 days ago and now the 2FA issue has come back. I'm getting the following errors in my log.
ERROR (MainThread) [pyalarmdotcomajax.pyalarmdotcomajax] Unable to extract data from adt.com
ERROR (MainThread) [homeassistant.components.alarm_control_panel] Error while setting up alarmdotcom platform for alarm_control_panel
I know you fixed this for ADT users. Is there a way you do the same for Protection One users? Here's the site I log into https://www.alarm.com.
Thanks!

This issue is being worked on in #26. Please track the progress over there.


Replace specific "Nexus" mentions with more generic "artifact repository"

While ODS uses Nexus, there should not be Nexus-specific things in the build tasks, as the configuration of build tools like Gradle does not depend on which artifact repository is used. In those places we should talk about "artifact repository", not "Nexus". The same applies to the ConfigMap and Secret.
There is however Nexus-specific implementation in the Go client, and this is required. However, we could create an interface and make the other code use that interface instead.
FYI @oalyman as suggested by you

The start and finish tasks are tied to Nexus.
The build task extracted in https://github.com/opendevstack/ods-pipeline/pull/722 should be Nexus-agnostic, and those may choose to use a neutral name. However the central repo only works with Nexus right now, as it uses the Nexus API to discover artifacts.


can't install operator_sdk on win10: "cannot use syscall.NsecToFiletime" bug when doing "make install"

Bug Report

What did you do?
first of all, i installed make tool, go lang on my win10 pc.
i followed the official instructions from https://sdk.operatorframework.io/docs/installation/ (Compile and install from master)
git clone https://github.com/operator-framework/operator-sdk
cd operator-sdk
git checkout master
make install

i created the folder , git cloned into and tried the last step.
the last step did not work  and gave me this error:
go\pkg\mod\github.com\containerd\containerd@v1.4.11\archive\tar_windows.go:257:27: cannot use syscall.NsecToFiletime(createTime.UnixNano()) (value of type syscall.Filetime) as "golang.org/x/sys/windows".Filetime value in assignment

What did you expect to see?
i expected to have operator-sdk installed and to follow some utube tutorial and create my own operator from scratch

What did you see instead? Under which circumstances?
i see this error:
make install
go install -gcflags "all=-trimpath=C:/Users/erjan/Downloads/operator_k8s_sdk" -asmflags "all=-trimpath=C:/Users/erjan/Downloads/operator_k8s_sdk" -ldflags " -X 'github.com/operator-framework/operator-sdk/internal/version.Version=v1.31.0+git' -X 'github.com/operator-framework/operator-sdk/internal/version.GitVersion=v1.31.0-3-gd21ed649' -X 'github.com/operator-framework/operator-sdk/internal/version.GitCommit=d21ed6499ebfc8ecdb4508e1c2a2a0cfd2a151f3' -X 'github.com/operator-framework/operator-sdk/internal/version.KubernetesVersion=v1.26.0' -X 'github.com/operator-framework/operator-sdk/internal/version.ImageVersion=v1.31.0' "  ./cmd/# github.com/containerd/containerd/archive
..\..\..\go\pkg\mod\github.com\containerd\containerd@v1.4.11\archive\tar_windows.go:234:19: cannot use syscall.NsecToFiletime(hdr.AccessTime.UnixNano()) (value of type syscall.Filetime) as "golang.org/x/sys/windows".Filetime value in struct literal
..\..\..\go\pkg\mod\github.com\containerd\containerd@v1.4.11\archive\tar_windows.go:235:19: cannot use syscall.NsecToFiletime(hdr.ModTime.UnixNano()) (value of type syscall.Filetime) as "golang.org/x/sys/windows".Filetime value in struct literal
..\..\..\go\pkg\mod\github.com\containerd\containerd@v1.4.11\archive\tar_windows.go:236:19: cannot use syscall.NsecToFiletime(hdr.ChangeTime.UnixNano()) (value of type syscall.Filetime) as "golang.org/x/sys/windows".Filetime value in struct literal
..\..\..\go\pkg\mod\github.com\containerd\containerd@v1.4.11\archive\tar_windows.go:239:17: cannot use syscall.NsecToFiletime(hdr.ModTime.UnixNano()) (value of type syscall.Filetime) as "golang.org/x/sys/windows".Filetime value in struct literal
..\..\..\go\pkg\mod\github.com\containerd\containerd@v1.4.11\archive\tar_windows.go:257:27: cannot use syscall.NsecToFiletime(createTime.UnixNano()) (value of type syscall.Filetime) as "golang.org/x/sys/windows".Filetime value in assignment
make: *** [Makefile:75: install] Error 1

Environment
git bash,win10, 64bit,amd64
Kubernetes cluster type: minikube
$ go version (if language is Go)
go version go1.21.1 windows/amd64

@erjan we have a similar issue open: https://github.com/operator-framework/operator-sdk/issues/6586
We do not officially support or build binaries for windows. But we are open to receiving any help with contributions. I'll close this as a duplicate of #6586. But feel free to re-open if you feel otherwise. Thank you!


Add ember-alpha to try config.

Tests are passing (with the tweak to avoid using this.attrs in the acceptance test).
I have reported the issue that passing an action through a middle layer doesn't properly prevent mut-wrapping in this.attrs as was done in HTMLBars with a failing test in https://github.com/emberjs/ember.js/pull/13996.

OK, this is good to go and prevents errors when using with the alpha (due to the ACTION import).

@homu r+

:pushpin: Commit da10e1b has been approved by poteto

:zap: Test exempted - status


Update content from Sept 16 edits

See changes at: https://docs.google.com/document/d/1E_S4g8swsliJSNgMYkT9JRdm0GMzjrav/edit#

updated with the changes from the google doc as of now (in a separate branch): https://github.com/NASA-Openscapes/2021-Cloud-Hackathon/tree/2-updates @erinmr


Bump Go to 1.21.5

See https://go.dev/doc/devel/release#go1.21

go1.21.4 (released 2023-11-07) includes security fixes to the path/filepath package, as well as bug fixes to the linker, the runtime, the compiler, and the go/types, net/http, and runtime/cgo packages.
go1.21.5 (released 2023-12-05) includes security fixes to the go command, and the net/http and path/filepath packages, as well as bug fixes to the compiler, the go command, the runtime, and the crypto/rand, net, os, and syscall packages.

cert-manager is now built with Go 1.21.5

/kind feature
Testing
Before:
$ make vendor-go
curl --silent --show-error --fail --location --retry 10 --retry-connrefused https://go.dev/dl/go1.21.3.linux-amd64.tar.gz -o _bin/downloaded/tools/go-1.21.3-linux-amd64.tar.gz
rm -rf _bin/downloaded/tools/_go-1.21.3-linux-amd64/goroot
tar xzf _bin/downloaded/tools/go-1.21.3-linux-amd64.tar.gz -C _bin/downloaded/tools/_go-1.21.3-linux-amd64
mv _bin/downloaded/tools/_go-1.21.3-linux-amd64/go _bin/downloaded/tools/_go-1.21.3-linux-amd64/goroot
cd _bin/tools/ && ln -f -s ../downloaded/tools/_go-1.21.3-linux-amd64/goroot .
cd _bin/tools/ && ln -f -s ../downloaded/tools/_go-1.21.3-linux-amd64/goroot/bin/go .
rm _bin/downloaded/tools/go-1.21.3-linux-amd64.tar.gz

$ govulncheck --version
Go: go1.21.3
Scanner<EMAIL_ADDRESS>DB: https://vuln.go.dev
DB updated: 2023-12-11 15:30:30 +0000 UTC

No vulnerabilities found.

Share feedback at https://go.dev/s/govulncheck-feedback.

$ make go-workspace
go work init
go work use . ./cmd/acmesolver ./cmd/cainjector ./cmd/controller ./cmd/ctl ./cmd/webhook ./test/integration ./test/e2e

$ govulncheck ./...
Scanning your code and 1406 packages across 150 dependent modules for known vulnerabilities...

Vulnerability #1: GO-2023-2382
    Denial of service via chunk extensions in net/http
  More info: https://pkg.go.dev/vuln/GO-2023-2382
  Standard library
    Found in<EMAIL_ADDRESS>    Fixed in<EMAIL_ADDRESS>    Example traces found:
      #1: pkg/issuer/acme/dns/util/wait.go:258:25: util.httpDNSClient.Exchange calls ioutil.ReadAll, which eventually calls internal.chunkedReader.Read

Vulnerability #2: GO-2023-2186
    Incorrect detection of reserved device names on Windows in path/filepath
  More info: https://pkg.go.dev/vuln/GO-2023-2186
  Standard library
    Found in<EMAIL_ADDRESS>    Fixed in<EMAIL_ADDRESS>    Example traces found:
      #1: pkg/issuer/venafi/client/instrumentedvenaficlient.go:67:51: client.instrumentedConnector.RetrieveCertificate calls cloud.Connector.RetrieveCertificate, which eventually calls filepath.IsLocal

Vulnerability #3: GO-2023-2185
    Insecure parsing of Windows paths with a \??\ prefix in path/filepath
  More info: https://pkg.go.dev/vuln/GO-2023-2185
  Standard library
    Found in<EMAIL_ADDRESS>    Fixed in<EMAIL_ADDRESS>    Platforms: windows
    Example traces found:
      #1: test/apiserver/apiserver.go:44:24: apiserver.RunBareControlPlane calls envtest.Environment.Start, which eventually calls safefilepath.FromFS
      #2: test/apiserver/apiserver.go:44:24: apiserver.RunBareControlPlane calls envtest.Environment.Start, which eventually calls safefilepath.FromFS
      #3: pkg/controller/context.go:258:51: controller.NewContextFactory calls clientcmd.BuildConfigFromFlags, which eventually calls filepath.Abs
      #4: pkg/logs/logs.go:34:2: logs.init calls klog.init, which calls filepath.Base
      #5: test/acme/suite.go:94:40: acme.fixture.TestExtendedDeletingOneRecordRetainsOthers calls wait.PollUntilContextTimeout, which eventually calls filepath.Clean
      #6: pkg/util/configfile/configfile.go:53:43: configfile.configurationFSLoader.Load calls filepath.Dir
      #7: pkg/issuer/venafi/client/instrumentedvenaficlient.go:67:51: client.instrumentedConnector.RetrieveCertificate calls cloud.Connector.RetrieveCertificate, which eventually calls filepath.IsLocal
      #8: test/webhook/testwebhook.go:85:39: webhook.StartWebhookServer calls filepath.Join
      #9: pkg/acme/client/http.go:73:37: client.Transport.RoundTrip calls exec.roundTripper.RoundTrip, which eventually calls filepath.VolumeName
      #10: test/acme/util.go:50:26: acme.fixture.setupNamespace calls filepath.Walk
      #11: pkg/controller/context.go:258:51: controller.NewContextFactory calls clientcmd.BuildConfigFromFlags, which eventually calls filepath.Abs
      #12: pkg/logs/logs.go:34:2: logs.init calls klog.init, which calls filepath.Base
      #13: test/acme/suite.go:94:40: acme.fixture.TestExtendedDeletingOneRecordRetainsOthers calls wait.PollUntilContextTimeout, which eventually calls filepath.Clean
      #14: pkg/util/configfile/configfile.go:53:43: configfile.configurationFSLoader.Load calls filepath.Dir
      #15: pkg/issuer/venafi/client/instrumentedvenaficlient.go:67:51: client.instrumentedConnector.RetrieveCertificate calls cloud.Connector.RetrieveCertificate, which eventually calls filepath.IsLocal
      #16: test/webhook/testwebhook.go:85:39: webhook.StartWebhookServer calls filepath.Join
      #17: pkg/acme/client/http.go:73:37: client.Transport.RoundTrip calls exec.roundTripper.RoundTrip, which eventually calls filepath.VolumeName
      #18: test/acme/util.go:50:26: acme.fixture.setupNamespace calls filepath.Walk

Your code is affected by 3 vulnerabilities from the Go standard library.

Share feedback at https://go.dev/s/govulncheck-feedback.

After

$ make vendor-go
curl --silent --show-error --fail --location --retry 10 --retry-connrefused https://go.dev/dl/go1.21.5.linux-amd64.tar.gz -o _bin/downloaded/tools/go-1.21.5-linux-amd64.tar.gz
rm -rf _bin/downloaded/tools/_go-1.21.5-linux-amd64/goroot
tar xzf _bin/downloaded/tools/go-1.21.5-linux-amd64.tar.gz -C _bin/downloaded/tools/_go-1.21.5-linux-amd64
mv _bin/downloaded/tools/_go-1.21.5-linux-amd64/go _bin/downloaded/tools/_go-1.21.5-linux-amd64/goroot
cd _bin/tools/ && ln -f -s ../downloaded/tools/_go-1.21.5-linux-amd64/goroot .
cd _bin/tools/ && ln -f -s ../downloaded/tools/_go-1.21.5-linux-amd64/goroot/bin/go .
rm _bin/downloaded/tools/go-1.21.5-linux-amd64.tar.gz

$ govulncheck --version
Go: go1.21.5
Scanner<EMAIL_ADDRESS>DB: https://vuln.go.dev
DB updated: 2023-12-11 15:30:30 +0000 UTC

No vulnerabilities found.

Share feedback at https://go.dev/s/govulncheck-feedback.

$ govulncheck ./...
Scanning your code and 1406 packages across 150 dependent modules for known vulnerabilities...

No vulnerabilities found.

Share feedback at https://go.dev/s/govulncheck-feedback.

/approve
/lgtm

/kind cleanup


mempool corruption fixes for the v1.14 branch

This is a backport of #16966 and #16996 for the v1.14 branch (backport-v1.14).

@npitre could you rebase?

Something is quite amiss with this PR :(

Something is quite amiss with this PR :(

I have same impression. Maybe something went wrong in global replacement?

Ugh.  I tried removing myself and then got an error saying "15 reviewers max".

On Wed, 17 Jul 2019, Vinayak Kariappa Chettimada wrote:

@npitre could you rebase?

Rebase onto what?
It is currently based on v1.14-branch aka commit 03a52401c682.

@npitre:

Rebase onto what?

It is currently based on v1.14-branch aka commit 03a5240.

It seems that CI didn't run for this PR due to the initial "mis-branching". I'd suggest to rebase this on the current HEAD of v1.14-branch to re-trigger CI.

Ugh. I tried removing myself and then got an error saying "15 reviewers max". A bunch of others were removed:

I took freedom to further prune the reviewer list, based on my knowledge of who might work with such deep kernel issues. Apologies if I removed someone interested (you still should receive notifications about this issue and be in loop).

On Tue, 23 Jul 2019, Paul Sokolovsky wrote:

It is currently based on v1.14-branch aka commit 03a5240.

It seems that CI didn't run for this PR due to the initial "mis-branching". I'd suggest to rebase this on the current HEAD of v1.14-branch to re-trigger CI.

What is the commit for current HEAD of v1.14-branch at your end?
My latest fetch refreshed master and a few "backport" branches, but not
v1.14-branch. Hence it is still at commit 03a5240.

CI seems incredibly unhappy.
Attempting to fix this by doing a brand-new PR with the same patches: https://github.com/zephyrproject-rtos/zephyr/pull/17759

#17759 merged


ISSUE: Not counting FedEx email 'delivering tomorrow' in FedEx Delivering sensor

Describe the bug
My expectation of the "delivering" sensors is that it would count emails that state 'your package is being delivered tomorrow' or 'your package is scheduled for delivery tomorrow' as in transit packages at the least.  But I'm not seeing this behavior and instead counts only show up when something is being delivered TODAY.  Is my understanding incorrect or is this actually unexpected behavior?  I've included an example of a FedEx delivery that will be delivered tomorrow, though nothing is showing in my mail_fedex_delivering sensor.
Environment (please complete the following information):

OS: HassOS
Type of device: Ubuntu VM running in Virtual Box
Home Assistant version: 0.114.4
Hassio
Component version: 0.2.2-b25

Logs
No errors
Screenshots

Additional context
PlainText email provided, personal info redacted or altered
FedEx Shipment 9177448XXXXX_ Your package is scheduled for delivery tomorrow.txt

Nope, per the wiki only the current day's deliveries. You can review the search terms as well in the wiki.

Thanks, Chris.  I figured as much but wanted to be sure otherwise what's the point of me testing all these betas! LOL
Search terms table is a really nice addition to the docs!  Thanks for pointing me to it. And I appreciate the quick response!
(BTW, it says something that this is the first time in a while that I even found something worth asking about.  Betas have been pretty solid for me and development is coming along nicely. )


logical defs of movement: cilium & microtubule-based

Unexpected inference in gomodel:5f46c3b700004144
I made a small GO-CAM model in Noctua for Xenopus fam183b from a paper that covered both Xenopus and mouse, MGI were already curating the mouse stuff.
One of the annotations is for 'epithelial cilium movement involved in extracellular fluid movement [GO:0003351]'. The reasoner adds an inferred process of 'establishment of localization in cell [GO:0051649]'. This doesn't seem to be an obvious inference. I thought initially it might be because I said the process occurred in multiciliated cells but even when I removed that relationship the inference was still there.
Is this inference correct?

@vanaukenk @ukemi

The inference is correct based on all of the rules. But it points to a problem in the ontology.
'epithelial cilium movement involved in extracellular fluid movement'  is asserted to be a subclass of 'extracellular transport'.
'extracellular transport' is a subclass of 'transport'.
'transport' is a subclass of 'establishment of localization'.
The 'epithelial cilium movement involved in extracellular fluid movement'  in your model occurs_in some 'multiciliated epidermal cell'.
'multiciliated epidermal cell is a subclass of cell.
Therefore 'epithelial cilium movement involved in extracellular fluid movement' is a type of 'transport' that occurs in a cell.
Therefore it is a type of 'establishment of localization' that occurs_in a cell.
'establishment of localization in cell' is defined as 'establishment of localization' and ('occurs in' some cell).
Following this logic, if the 'epithelial cilium movement involved in extracellular fluid movement' occurs in a cell, then it is 'establishment of localization in cell'.
I would question whether 'epithelial cilium movement involved in extracellular fluid movement'  is a subclass of 'extracellular transport'. The 'involved in' phrasing of the term suggests that when it was created, the movement of the cilium was part_of 'extracellular transport'. This would be the easiest solution, but brings up some interesting issues about the spatial relations of transport. It would be fun to look at logically defining the term with nested expressions.
'epithelial cilium movement involved in extracellular fluid movement' = ('cilium movement' occurs_in some 'epithelial cell') and results_in_movement_of some (fluid? adjacent_to some 'epithelial cell'). Or a new cc term extracellular fluid?? I can't find fluid in an ontology. It would be nice to indicate the same instance of the epithelial cell.

Thanks for that detailed answer David. One small thing is that the inference persisted even when I removed the 'occurs in' relationship to the cell type.

Ah yes. I suspect that once the occurs_in is removed, the inference is because
'cilium' is a subclass of 'plasma membrane bound cell projection'.
'plasma membrane bound cell projection' is part of a 'cell'.
'cilium movement' results in movement of some 'cilium'.
@balhoff do you agree?

I'm hanging up on the occurs_in part. If a cilium protruding outwards from a cell beats and thereby sets up a flow of fluid in the extracellular space (e.g., to clear mucus from lung epithelia, or to set up a directional flow sensed by other cells in a developing embryo to establish left - right asymmetry), then even though a cell part is doing the agitating and definitely depends on things inside the cell to provide energy and leverage, the flow is happening entirely on the outside. Is there any mileage in this?

Yes. There is something funny about this and the way we represent it.

Drag Karen into the inside - outside discussion. She really understands the weedy details!

From: David Hill<EMAIL_ADDRESS>Sent: Tuesday, November 3, 2020 10:43 AM
To: geneontology/go-ontology
Cc: D'Eustachio, Peter; Comment
Subject: Re: [geneontology/go-ontology] Unexpected inference in gomodel:5f46c3b700004144 (#20258)
[EXTERNAL]
Yes. There is something funny about this and the way we represent it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_geneontology_go-2Dontology_issues_20258-23issuecomment-2D721208603&d=DwMCaQ&c=j5oPpO0eBH1iio48DtsedeElZfc04rx3ExJHeIIZuCs&r=2Sysx5329O--oOLYkHqNwFvpSt4Hk2pxc3MQOQUUTGQ&m=FFD67Q5b5hFUOZ6K9XWHQetk_9C_bG62VqQ0IV2FiD4&s=tK0VFfF3_SLRNzvAefBrmk7QjYmMBDt0H51Rbyb_Sjc&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ADBFYVZLTAM7S4BEDE5X3ILSOAQLNANCNFSM4TIM3SKQ&d=DwMCaQ&c=j5oPpO0eBH1iio48DtsedeElZfc04rx3ExJHeIIZuCs&r=2Sysx5329O--oOLYkHqNwFvpSt4Hk2pxc3MQOQUUTGQ&m=FFD67Q5b5hFUOZ6K9XWHQetk_9C_bG62VqQ0IV2FiD4&s=rVXIwAWDsAxaArhMKcsRDLh4Pk9khnhtTuBYl4qUygo&e=.

This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is proprietary, confidential, and exempt from disclosure under applicable law. Any unauthorized review, use, disclosure, or distribution is prohibited. If you have received this email in error please notify the sender by return email and delete the original message. Please note, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email.

@malcolmfisher103 , are you sure you refreshed after you deleted the occurs_in 'multiciliated epithelial cell'? I just tried it with @balhoff and we didn't see the inference.

@malcolmfisher103 , are you sure you refreshed after you deleted the occurs_in 'multiciliated epithelial cell'? I just tried it with @balhoff and we didn't see the inference.

@krchristie anything to add? An interesting discussion about cilia, where they are moving and location of the things that are a result of their movement. Perhaps bring this up on an ontology call?

Hi David, you are right I hadn't refreshed it, I think I expected the reasoner to update it when I saved the changes.

I'm kind of surprised it didn't when you saved. Weird.

Ah yes. I suspect that once the occurs_in is removed, the inference is because
'cilium' is a subclass of 'plasma membrane bound cell projection'.
'plasma membrane bound cell projection' is part of a 'cell'.
'cilium movement' results in movement of some 'cilium'.
@balhoff do you agree?

I think it is a tautology to say that cilium movement results in movement of itself, and probably not really what we want in GO.
Here are the logical definitions of cilium movement and microtubule-based movement
cilium movement (GO:0003341)
'movement of cell or subcellular component'
 and ('results in movement of' some cilium)
 and ('process has causal agent' some microtubule)

microtubule-based movement (GO:0007018)
'movement of cell or subcellular component'
 and ('process has causal agent' some microtubule)

I think that the logical definition of cilium movement should probably be changed to say that the cilium is the causal agent. I don't think it's correct to say that the microtubule is the causal agent of cilium movement anyway, as the MTs are present in non-motile cilia too. For cilia, the causal agent, or agents, would include the dynein arms. I'm wondering if it's really correct to say that the causal agent of microtubule-based movement is the MTs. It seems to me that the MTs are often the highway upon which motors move.
I'll make an ontology ticket about these logical defs.

@malcolmfisher103 - Regarding your model, it seems that you should be able to put the two GO terms in line with each other since we know that cilium assembly is upstream of cilium motility. Basically, whatever Fam183b.L is doing in the process of cilium assembly is upstream of epithelial cilium motility involved in extracellular fluid movement.

@krchristie I had been considering making cilium assembly upstream of the motility term, thanks for the advice.
I think David and Jim have identified the 'occurs in' relationship with the 'multiciliated epidermal cell' as the culprit for where the inference came from, with some issues with my interaction with Noctua being why it persisted. So is this an incorrect relationship that I should just remove? The cilium is definitely part of the cell but should I say the motility 'occurs in' the cell?

@krchristie I had been considering making cilium assembly upstream of the motility term, thanks for the advice.
I think David and Jim have identified the 'occurs in' relationship with the 'multiciliated epidermal cell' as the culprit for where the inference came from, with some issues with my interaction with Noctua being why it persisted. So is this an incorrect relationship that I should just remove? The cilium is definitely part of the cell but should I say the motility 'occurs in' the cell?

As a biologist, I think that the cilium movement is occurring within the cell since there are motors moving within the cilium that create the movement of the organelle as a whole and that movement is occurring within a part of the cell. However, due to its location on the external surface of the cell, the cilium is also moving through the extracellular region and the movement of extracellular fluid is definitely occurring outside of the cell. Many things about the cilium are tricky in the ontology. It isn't the first time we've had a hard time defining cilium terms in the ontology. I've added the editors-discussion tag so that we'll discuss this at an ontology editors' call.

The problem is the
GO:0003351    epithelial cilium movement involved in extracellular fluid movement
parent
GO:0099111    microtubule-based transport
movement is not always transport.
This parentage is wrong on a number of levels.
The fluid is being transported by the epithelia.
cillium movement is a microtuble based movement, but not a microtubule based transport
I guess this term would need an additional parent to describe the fluid movement

movement is not always transport.

was an understatement.
Movement and transport are different things, but often conflated in the ontology.
"movement is physical motion between points in space while transport is an act of transporting"
microtubules move things (i.e  as cillia), or  by pushing (the nucleus), or pulling (chromosomes apart). I don't think this is transport?
they are also part_of the process of transport, when they provide the tracks for vesicles and cargo to be moved (for instance components of the spindle pole body,  are transported along the spindle  microtubules towards the SPB). Lost chromsomes are pulled toward the spindle pole body during mitosis. I think this happens on 'depolymerizing mnicrotubules', so it might look a bit like transport, but it probably isn't.
I don't know if this helps to disambiguate?
At present we have
GO:0099111   microtubule-based transport
as part of transport, but not all microtubule based movement is transport.
I think you  might fix the problem here by moving
GO:0003351 epithelial cilium movement involved in extracellular fluid movement
to be a child of
GO:0007018   microtubule-based movement
instead of
GO:0099111   microtubule-based transport

Maybe the genera should be 'GO:0046907 intracellular transport'
rather than 'movement of cell or subcellular component'
(or another term - just 'movement of cell or subcellular component' is a strange grouping class.

11/9/20 - Discussion on ontology editors call

The logical definition of microtubule-based movement (GO:0007018) = 'movement of cell or subcellular component' and ('process has causal agent' some microtubule) is not sufficient. It also requires an additional causal agent of some type of microtubule motor.
In the logical definition of cilium movement (GO:0003341), it seems very odd that the genera is a term that is so broad: 'movement of cell or subcellular component'. @krchristie will look into what it should be.

Maybe the genera should be 'GO:0046907 intracellular transport'
rather than 'movement of cell or subcellular component'

I don't think that 'GO:0046907 intracellular transport' will work since the microtubule motors within the cilium don't transport anything; they just change the relative positions of the microtubules within the cilium resulting in cilium bending, aka movement.

(or another term - just 'movement of cell or subcellular component' is a strange grouping class.

Agreed!

Is that always true? I thought there were cases where there was transport of receptors along microtubules in the cilium so that they could be deposited in the cilium and the cilium would act as an antenna for the ligands.

Is that always true? I thought there were cases where there was transport of receptors along microtubules in the cilium so that they could be deposited in the cilium and the cilium would act as an antenna for the ligands.

Transport of receptors along MTs in the cilium occurs by IFT (intraflagellar transport) and is caused by movement of the IFT motors along ciliary MTs, so this is transport. This occurs in non-motile primary cilia for sure, and probably also in motile cilia, but I haven't seen much research characterizing signaling in motile cilia. IFT motors do not generate movement of cilia, though IFT is required upstream of ciiary movement because IFT is required to transport things into the cilium as part of assembly, so when IFT is broken, ciliary movement is generally also broken.
Ciliary movement is caused by the motors of the dynein arms, which are present in motile cilia, but not in non-motile ones. Movement of dynein arms does not transport anything, but shifts the relative connection points between two ciliary MTs such that bending of the cilium occurs.
I edited my previous comment to accurately specify the microtubule motors THAT MOVE the cilium rather than the the microtubule motors IN the cilium

microtubules move things (i.e as cillia), or by pushing (the nucleus), or pulling (chromosomes apart). I don't think this is transport?

MTs are often the scaffold along which a MT-motor may move along a MT to generate movement; this is how motile cilia move and a common mechanism of transport. However, MTs alone are often not sufficient for movement, e.g. non-motile cilia which have MTs, but no dynein arms with motors to shift the relative positioning of the MTs.
My recollection is that there are other types of microtubule mediated movement where the movement is generated by shortening or lengthening an anchored MT that has some cargo attached at other end. @ValWood - do you know if this is what is occurring in the examples you mentioned above for "pushing (the nucleus), or pulling (chromosomes apart)"?

I see that we already have this term: microtubule polymerization based movement (GO:0099098). But this term chromosome movement towards spindle pole (GO:0051305) is due to shortening rather than polymerization so it isn't a child of that term.
I think we're going to need some new grouping terms under microtubule movement. Here's some initial thoughts.
-- microtubule movement (GO:0007018)
--- term to group movement based on MT length change (GO:NEW)
---- microtubule depolymerization based movement (GO:NEW)
---- microtubule polymerization based movement (GO:0099098)
--- term to group movement based on movement of motor along MT (GO:NEW)
not sure whether existing term microtubule sliding is related to motors or not...
We may also need new child terms under microtubule-based transport to reflect the subgroupings I'm thinking about above.

Yes, for chromsome pulling apart microtubules depolymerize, and the DAM/DASH complex acts as a rachet, so this is the microtubule kinetochore attachment.
https://www.mdpi.com/1422-0067/20/24/6182/htm
This is 'microtubule-dependent movement', but it isn't transport (at least, I do not think anybody would describe chromosome segregation as a type of transport, but the chromosomes move apart).
Then there is this situation:
https://www.pombase.org/reference/PMID:31483748
microtubules-dependent processes also  provide the force to oscillate the nucleus at interphase (I don't think this is transport intuitively either).
There is also  the microtubule-based movement  with kinesins providing the force moving the SPBs apart  during spindle formation
https://www.pombase.org/reference/PMID:29167352
These processes are all microtubule-based movement, but not transport. I looked at these terms last night and they all seemed to make sense except for the one parentage I pointed out above.
I think this proposal  is making things more complicated. I wouldn't add any more grouping terms, I also wouldn't put depolymerization in the process terms since ideally these would be in the molecular function ontology. We have been trying to move these recently because we now more about microtubule  polymerases and the depolymerases. I would like to remove "microtubule polymerization based movement" and "microtubule sliding" from BP because these include  molecular functions in the processes and would require an exponential number of terms to make these work for all processes.
There are quite a few open tickets about this. Adding more processes which include  activities isn't going to help,  because there are so many mechanisms at play.
I still think you can resolve the current problem by removing
GO:0003351 epithelial cilium movement involved in extracellular fluid movement
parent
GO:0099111 microtubule-based transport
which is clearly wrong. Cillium movement isn't microtubule-based transport.

I updated the above comments, I think the depolymerization terms are OK but I'm sure there are now aspects of these processes, especially around chromosomes segregation, where we know a lot of the activities and the processes could be simplified to allow more modular annotation.
But I don't think it is simple to classify as polymerization or depolymerization based movement. A single process can combine a number of mechanisms and forces.

I requested some of these polymerization terms over the years when  we knew less about the processes.

I still think you can resolve the current problem by removing
GO:0003351 epithelial cilium movement involved in extracellular fluid movement
parent
GO:0099111 microtubule-based transport
which is clearly wrong. Cillium movement isn't microtubule-based transport.

It really isn't quite that simple.
This parentage is coming from reasoning based on the existing equivalence axiom of several terms including this term:
cilium movement (GO:0003341)
'movement of cell or subcellular component'
 and ('results in movement of' some cilium)
 and ('process has causal agent' some microtubule)

I've already commented about the fact that this equivalence axiom is not sufficient. Fixing this may require adding grouping terms under microtubule-based movement in order to make appropriate logical axioms for other terms.
Then this term, the one being used for annotation,
epithelial cilium movement involved in extracellular fluid movement (GO:0003351)
does not have an equivalence axiom, but does have these ASSERTED SubClass Of relationships:

cilium movement
extracellular transport [def = The transport of substances that occurs outside cells.]

and this INFERRED SubClass Of relationship:

microtubule-based transport

The ASSERTED relationships seem true to, but the INFERRED one is incorrect. To remove the inferred relationship, it is likely that we will have to fix the logic in microtubule-based movement, which I hope will make it possible for me to define this term with an equivalence axiom, rather than just with some directly asserted relationships.

OK got it.
I still think we should ask first whether "microtubule-based movement" is really a useful grouping term.
All of the children should have other parentage describing specific processes, and "microtubule-based movement" groups so many unrelated concepts (other than that they are microtubule-based)  it might not really be so useful (microtubule-based process would suffice).
Also, the persistance of the precomposed term-  I thought GO was  removing all of the precomposed  process terms with  "involved in" so the speciific term epithelial cilium movement involved in extracellular fluid movement (GO:0003351) presumably would go at some point?

I dont know very much about those processes, but it seems to me 'microtubule-based movement (GO:0007018)' is a good grouping term, and can include microtubule polymerization and depolymerization-based movements, but I am wary of creating too many grouping therms under that class - so I would NOT create those. In fact I suggest we go the other way sand obsolete 'microtubule polymerization based movement (GO:0099098) (has no direct annotations).
I suggest we dont create those:

--- term to group movement based on MT length change (GO:NEW)
The definition of 'microtubule-based movement (GO:0007018) already covers that: "A microtubule-based process that results in the movement of organelles, other microtubules, or other cellular components. Examples include motor-driven movement along microtubules and movement driven by polymerization or depolymerization of microtubules."

---- microtubule depolymerization based movement (GO:NEW)
--- term to group movement based on movement of motor along MT (GO:NEW)

Thanks, Pascale

I agree.  'microtubule-based movement (GO:0007018) is sufficient. The rest are mechanistic, so they now seem odd in BP.

The reason I'm suggesting these terms is that I think that they may be needed in order to make equivalence axioms that are both necessary and sufficient. For some of these types of MT-based movement, a MT motor that moves along the MT is required. I don't think that is true for the types of movement that are based on MT length change, i.e. polymerization or depolymerization. I don't want them as annotation terms, but as logical definitions that can be used in order to define other terms.

Let's see if we can do without, first ?


[BIA-674] Create a StaffSectionDim view in AMT Core

Added a new view in DS 2 and DS 3x.
Created testcases to validate rows and view instalation.

@jleiva-gap should the title of the PR be updated? Since this is for a SectionDim view and not StaffSectionDim?


Live HLS / DVR

Hello,
Is there a way to support dvr with live ? ( I mean rewind, because pause is working)

HLS is not optimal for live, there is a bit of lag that comes with it (up to 15 seconds) do you have the option to play your live stream via another method/format?

Thank you for your answer. We have to use HLS, in order to have the same stream on ios,android andwindows desktop. DVR is working great with mediaelement (don't know for the player) when the option is activated on the CDN ;)


selinux: update

This PR is a follow-up of https://github.com/flatcar/portage-stable/pull/339 and https://github.com/flatcar/coreos-overlay/pull/1993 - the idea is to "only" upgrade SELinux related software and to pull the new "selinux-container" policy, relabeling investigation could be done in a second time: at least, let's try to get the foundation.
The main change is a transition from virt to container policy (which solves some issues) while I did not want to fix all the SELinux AVC in this PR, I just patched the container policy to get Cilium working out of the box (because now, even in permissive mode, it was failing)

[x] Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update)
[x] Inspected CI output for image differences: /boot and /usr size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.
[x] CI: http://jenkins.infra.kinvolk.io:8080/job/container/job/packages_all_arches/2521/cldsv/

While it closes a certain number of issues, there is still some investigation to do on the others but from a first look it's just a matter of upstreaming some policies (example: https://github.com/SELinuxProject/refpolicy/pull/621)
Closes: https://github.com/flatcar/Flatcar/issues/479, https://github.com/flatcar/Flatcar/issues/891, https://github.com/flatcar/Flatcar/issues/696
Tested in the CI with: https://github.com/flatcar/mantle/pull/344
NOTE: All the kernel_t related patches have to be DROPPED once we support a fully labelled system.

@krnowak thanks for the review - addressed your comments except the nitpick as it seems we still need to pull anyway setools into the overlay? I don't think it's worth as we still need to maintain another downstream patch for policycoreutils.

Fair, we can tackle it when we will be able to move policycoreutils to portage-stable.

Finally, to answer your question:

Where is ssh selinux module defined? Should we add a dependency on sec-policy/selinux-dbus to the package that provides it?

I already asked myself, ssh module is part of the selinux-base-policy (https://gitweb.gentoo.org/repo/gentoo.git/tree/sec-policy/selinux-base-policy/selinux-base-policy-2.20221101-r4.ebuild#n30) so we can't really add a dependency for ssh in particular but we could add a dependency to selinux-base-policy to selinux-dbus but I fear of falling into a cyclic dependency.

Meh. selinux-dbus should be deprecated and dbus module moved to selinux-base-policy. Anyway, won't be blocking this PR on this kind of stuff, obviously.


WIP: Outline specification for using ansible roles

For now just rough draft of how roles could be specified. It seems
the ansible-galaxy command already supports fetching roles from
git repositories so the implementation should not be hard I guess.
https://galaxy.ansible.com/docs/using/installing.html

As discussed on the hacking session, here's the kick-off pull request for the role support in ansible prepare step. @thrix, @happz, @FrNecas, @lukaszachy, @pvalena, please have a look.

Another idea from the hacking session: instead of adding role or collections keywords to tmt, I think it would be more reasonable to provide ansible-galaxy requirements file instead, which supports both, it is more standard and also we should be better covered future-wise.
# Install requirements via ansible-galaxy and run given playbook
prepare:
    how: ansible
    requirements: ansible/requirements.yml
    playbook: ansible/playbooks/test.yml

@thrix that would work. Several remarks:

it precludes installing collections from RPMs because you can't specify them in requirements - probably that's not a big problem though and if you want it, I suppose you can list the RPM providing the desired collection as a RPM requirement elsewhere
it has the advantage of applying an arbitrary playbook, not just a role, but you then need to specify a standard for the hosts: entry in the playbook (as a bad example, STI did not tell you what to put there, so some people used localhost, some used all ... ).
one should be able to specify variables for the playbook run in order to be able to write generic playbooks (this applied to the original proposal using roles as well)
one should be prepared to the possibility of specifying a playbook relative to a collection (embedded in a collection) - https://docs.ansible.com/ansible/devel/user_guide/collections_using.html#using-a-playbook-from-a-collection - but his is supported only since Ansible 2.11, so I would say do not rely on it yet.

@thrix that would work. Several remarks:

it precludes installing collections from RPMs because you can't specify them in requirements - probably that's not a big problem though and if you want it, I suppose you can list the RPM providing the desired collection as an RPM requirement elsewhere

yep, that should not be a problem, we have for rpm requires a dedicated step

it has the advantage of applying an arbitrary playbook, not just a role, but you then need to specify a standard for the hosts: entry in the playbook (as a bad example, STI did not tell you what to put there, so some people used localhost, some used all ... ).

I guess that is just a documentation thing, I would expect users to use hosts: all for their playbooks ...

one should be able to specify variables for the playbook run to be able to write generic playbooks (this applied to the original proposal using roles as well)

+1 this is what I mentioned in the hacking session

one should be prepared for the possibility of specifying a playbook relative to a collection (embedded in a collection) - https://docs.ansible.com/ansible/devel/user_guide/collections_using.html#using-a-playbook-from-a-collection - but his is supported only since Ansible 2.11, so I would say do not rely on it yet.

right, but that is automatic, once we pass to ansible-playbook like my_namespace.my_collection.playbook1 it will just work (ansible 2.11+ will recognize it correctly)? i.e. nothing needed on the tmt side?


Add jsonschema.protocols.IValidator

I'm marking this as a draft. I wanted to share what I've got so far for #548, but I'm not certain that it's good to merge without checking in on typeshed to see what we should do there.

This is a Protocol implementation for type checking under mypy and other static analyzers. It uses the protocol class defined in py3.8+ and uses typing_extensions as a backport for py3.7
The documentation-only validator class has been replaced with the protocol, and docs are now driven via autoclass on the protocol.
Importantly, several documented methods of the class have been removed, as they were marked deprecated under jsonschema v3.0 and are no longer provided by the builtin validators.
Minor adjustments to the docs are made to repoint references at the new class definition.

Thanks! This looks very much in the right direction. The only "significantish" thing that occurs to me is perhaps it'd be nice to also now add verification that validators implement this protocol to CI -- I'm out of the loop on whether we need a pytype (or mypy) toxenv to do so but if you know, let me know. Basically any code appearing in the tests would be good to add before merging, to ensure the protocol correctly describes things.

To keep us on the same page, here's the typeshed issue I just opened to discuss getting this added there:
https://github.com/python/typeshed/issues/6564

it'd be nice to also now add verification that validators implement this protocol to CI

I very much agree. Because I marked it runtime_checkable, I should be able to write a test which asserts isinstance(validator_class(), jsonschema.protocols.Validator).
That won't check everything that a type checker cares about (limitations of runtime_checkable), but it's a good first step.

Doing more sophisticated mypy (or pytype or pyright) testing is possible, but it gets very messy (I'm happy to share details, maybe in a separate issue). Based on what I've seen doing it, and where I see jsonschema as being right now, I'd recommend against trying to do too much right now.
I'll look at setting up mypy on jsonschema itself, in a separate branch -- I think that will be necessary before we can think more about typing-related functionality. I don't want to force typing on anyone, but I'm happy to help try to make it useful here.

I very much agree. Because I marked it runtime_checkable, I should be able to write a test which asserts isinstance(validator_class(), jsonschema.protocols.Validator). That won't check everything that a type checker cares about (limitations of runtime_checkable), but it's a good first step.

Yes that was all I was hoping for but I see you sent the other PR for mypy which is also nice of you, will have a look. I'm not a huge fan overall you can imagine otherwise I'd have done so myself previously but I'm perfectly happy (and appreciative) with what you've done there so will likely merge both of these.

Thanks for the suggestions; it made updating that much easier!
I've done a rebase to get that pyc file out of the history (whoopsie), and I've marked this no longer a draft since I got a reply on typeshed that we should add this here first, and we'll get it into typeshed afterwards.
Let me add a few tests for isinstance checks, and hopefully this will be good to merge.
I'll revisit the mypy checking branch after this is in and do a rebase to make sure everything looks okay with both changes.

I've added the tests I wanted and gotten most of the build passing. I'm stuck on tox -e docs-linkcheck, which fails to find a link to jsonschema.protocols.Validator.iter_errors. I see an element in the dirhtml output which has that as its id, so I don't understand why it's failing.
I've fiddled with things a bit but couldn't get it to pass -- any help or feedback on how to make progress with that would be greatly appreciated.

Thanks! I'll have a look in the morning, Linkcheck failing  (but not others) would be odd, linkcheck should only fail (by itself) if it's an external link, but will have to have a look. Appreciated!

Ah of course, linkcheck is failing because of the README change, which relies on RTD rebuilding the docs. That's fine we can merge and it will fail the first time but pass afterwards.
Thanks again for sending the PR!


[ffmpeg] fails to detect soxr

Describe the bug
There is a soxr feature for ffmpeg, but this one fails to detect soxr and don't use it.
Environment

OS: Macos and Windows

To Reproduce
Steps to reproduce the behavior:

./vcpkg install ffmpeg[core,ffmpeg,ffprobe,mp3lame,vorbis,opus,soxr]
You can see that in tools/ there will be no soxr.dll and that ffmpeg.exe will not be compiled with soxr even through it was compiled with --enable-soxr

I suspect that the build script fails to find soxr.

Hi @abique
Thanks for posting this issue. Confirmed this should be a bug on ffmpeg.
@mcmtroffaes
I noticed the code in configure file:
enabled libsoxr           && require libsoxr soxr.h soxr_create -lsoxr -lm
And from build log, I found:
External libraries:
libsoxr                 mediafoundation         schannel

Since I'm not familiar with ffmpeg. I'm not sure where the problem is. Could you please help take a look?

Soxr makes no sense without swresample, so I believe you're simply missing it from your features. The ffmpeg build script is clever enough to work out not to build soxr unless swresample is specified. For reduced confusion, perhaps swresample could be listed as a build dependency in the port?
For the record, in case it helps, it passes my own regression tests, including a small test program that verifies that the soxr engine is available:
https://ci.appveyor.com/project/mcmtroffaes/ffmpeg-msvc-build/build/job/y57ij6ge8nvo9y2c#L290
https://github.com/mcmtroffaes/ffmpeg-msvc-build/blob/master/test/swresample/find_swr_engine.cpp


Fix NonPos

NonPos is not working correctly in the current master. This change fixes the problem.

Addresses #1263


--pretty should respect .editorconfig

As a suggestion, --pretty should respect .editorconfig for formatting, particularly in regards to indentation.
.editorconfig is a centralized place to configure encoding and formatting for all text files in a repo, so you don't have to separately configure tools.
Often, I will --pretty optimize files and then open them in Atom to make manual edits. Atom conveniently respects my established SVG formatting config but SVGO doesn't, resulting in inconsistent formatting.
A benefit to respecting the config, other members from the team can jump in and start optimizing without having to ask anyone about the formatting. I don't trust everyone to laboriously follow up SVGO optimizations with manual reformatting to conform to our standards.
Ideally there would also be formatting options for the CLI that would take precedent, like how ESLint works.

FYI, there is new option --indent added in 0.6.4 which allows to set number of spaces to --pretty.

Editorconfig look less popular these days. Wouldn't like to increase package size with editorconfig dependencies.


sync env in juicefs cluster mode

close #3247

Codecov Report
Base: 55.55% // Head: 55.39% // Decreases project coverage by -0.17% :warning:

Coverage data is based on head (5ce2d37) compared to base (ccbd646).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3254      +/-   ##
==========================================
- Coverage   55.55%   55.39%   -0.17%
==========================================
  Files         142      142
  Lines       33213    33335     +122
==========================================
+ Hits        18452    18466      +14
- Misses      12813    12918     +105
- Partials     1948     1951       +3

Impacted Files
Coverage Δ

pkg/sync/cluster.go
27.58% <0.00%> (-2.05%)
:arrow_down:

pkg/sync/config.go
0.00% <0.00%> (ø)

pkg/meta/openfile.go
84.72% <0.00%> (-7.06%)
:arrow_down:

pkg/meta/config.go
50.69% <0.00%> (-3.16%)
:arrow_down:

pkg/meta/tkv_mem.go
92.44% <0.00%> (-1.17%)
:arrow_down:

pkg/meta/tkv.go
70.82% <0.00%> (-0.71%)
:arrow_down:

pkg/meta/sql.go
58.70% <0.00%> (-0.22%)
:arrow_down:

pkg/meta/redis.go
66.15% <0.00%> (-0.10%)
:arrow_down:

cmd/gc.go
12.50% <0.00%> (+0.08%)
:arrow_up:

cmd/dump.go
78.66% <0.00%> (+0.28%)
:arrow_up:

... and 6 more

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Algorand: Update capacity when selecting a different node type

Description
Capacity for algorand nodes should be updated according to the node type. as seen in the video below the values doesn't change when you switch between node types and in comparison is the same flow from the old weblets where the capacity used to change with each node type.
Screencast from 12-06-23 13:21:39.webm

@mohamedamer453 What if the use wrote his own values and then he switched the network or type? why should we update the values in case the user decided he is going to set his custom ones?

I think mainly because the flow is firstly selecting the Network/Node type and based on that the user will add the needed resources, and i think it's a better flow to add the minimum acceptable resources instead of showing an error message while changing the node type.

Verified on Devnet, 9227221.
Values were updated.


convert canvas prepare to typescript

Description of change

Seemed simple enough.
Pre-Merge Checklist

[x] Lint process passed (npm run lint)
[x] Tests passed (npm run test)

Codecov Report

Merging #6657 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #6657   +/-   ##
=======================================
  Coverage   82.59%   82.59%
=======================================
  Files          35       35
  Lines        1724     1724
=======================================
  Hits         1424     1424
  Misses        300      300

Continue to review full report at Codecov.

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


⚠ Samsung has degraded performance

In 8f9cc55, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2054 ms

Resolved: Samsung performance has improved in 5e12a3c.


Revert bower angular dependency to 1.4.0

As discussed in https://github.com/bendrucker/angular-credit-cards/issues/49 also released a new version so that angular 1.3.x users can continue to benefit from this good work.

Could you git tag v2.3.5 && git push --tags after pulling this so that bower will pick up the latest version, thanks.

Not right either, please match the package.json. And please don't touch the package version itself.

Okay sure I reverted the package version, but aren't you going to add a 2.3.5 anyway since this is a pretty important fix to push out? You want that privilege for yourself eh :P

please match the package.json

You mean you want the devDependencies in package.json to also be downgraded to 1.3.0? Else I'm not sure what you mean.

This is the correct semver string: https://github.com/bendrucker/angular-credit-cards/blob/516df5ea8fb8604e1c34a0833a8a9566312896f7/package.json#L46
Using ~1.3.0 is equally wrong as ~1.4.0 because either way you're excluding compatible users. package.json is right, bower is wrong, but I never noticed because I don't use bower.

but aren't you going to add a 2.3.5 anyway

Sure, but you never bump versions in PRs. Standard OSS etiquette. Most people who maintain lots of packages have an automated release system and you adding that bump commit screws it up.

Perfect! Thanks for bearing with me. Gotta make sure this stuff makes everyone happy or it becomes a huge headache for me.

No problem, I don't really like bower either (really getting into jspm) but stuck with it on a conservative paid project.
If you could release a new version with this change I'd be really grateful, then our integration tests will work again.

Yup, on it now

All set, tag/npm published

Thanks, in your honour I shall officially name this day "Ben (I appreciate Robots) Drucker Day".

:tada:


Create a dashboard to configure the search & analytics

We already have a small web page that allows a user to search on the data they have indexed. The goal of this would be to go much further with a full dashboard. This dashboard could include the following features:

Create/delete indexes
Change settings
Manage keys
See the list of updates
Have a monitoring view

@qdequele is there a repo for this project?

Not yet. We are looking to hire an frontend developer expert and this feature is planned for the end of the year.

@qdequele seems good~I'm also interested on this so please share us when project is released as open source

Would it be interesting to have a simple interface to configure production environment (domain name, SSL, proxy...)?

Would it be interesting to have a simple interface to configure production environment (domain name, SSL/TLS, proxy/nginx...)?

It would indeed! But aren't we talking about something quite separate from the dashboard then? Basically the same as the WordPress config page, right?

@erlend-sh that's exactly what I had in mind!

@eskombro seems it is different concept with 'dashboard', but it also should be useful 👍

Started a dedicated issue for that here: https://github.com/meilisearch/MeiliSearch/issues/698

For monitoring, rather than building your own, I'd advise following the protocol of existing monitoring solutions (like prometheus) so that the development effort can be conserved to focus on the core :)

If you haven't heard of it, I recommend checking out Netdata, I finally played with it today and it is simply amazing. It's fast and light weight and supports tons of collectors and storage backends and even supports Prometheus if someone wanted to build that already that was mentioned then it could work for it too.
https://github.com/netdata/netdata

Hello,
I will close this issue in favor of our public roadmap.
I invite everyone interested in this feature to upvote it on the roadmap.


Changing streamable episode ordering

To fix this problem: https://jira.dev.bbc.co.uk/browse/PROGRAMMES-5737?focusedCommentId=3613303&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-3613303

@BPScott not keen on those sort of tests. Would that not be better as an automated test by the testers?

Test this please


Invitation to github

Name
TEJA
Discord Username (if applicable)
No response
Additional Context
To learn

To learn