python3.12.5 安装paddlex模块报错

Checklist:

查找历史相关issue寻求解答
翻阅FAQ常见问题汇总和答疑
确认bug是否在新版本里还未修复
翻阅PaddleX API文档说明

描述问题
Installing build dependencies ... error                                                                                error: subprocess-exited-with-error                                                                                × pip subprocess to install build dependencies did not run successfully.                                               │ exit code: 1                                                                                ╰─> [100 lines of output]                                                                                Ignoring numpy: markers 'python_version == "3.6" and platform_system != "AIX" and platform_python_implementation == "CPython"' don't match your environment                                                                                Ignoring numpy: markers 'python_version == "3.6" and platform_system != "AIX" and platform_python_implementation != "CPython"' don't match your environment                                                                                Ignoring numpy: markers 'python_version == "3.7" and platform_system != "AIX"' don't match your environment             Ignoring numpy: markers 'python_version == "3.6" and platform_system == "AIX"' don't match your environment             Ignoring numpy: markers 'python_version == "3.7" and platform_system == "AIX"' don't match your environment             Ignoring numpy: markers 'python_version >= "3.8" and platform_system == "AIX"' don't match your environment             Collecting setuptools                                                                                Downloading setuptools-75.1.0-py3-none-any.whl.metadata (6.9 kB)                                                      Collecting wheel                                                                                Downloading wheel-0.44.0-py3-none-any.whl.metadata (2.3 kB)                                                           Collecting Cython>=0.28.5                                                                                Using cached Cython-3.0.11-cp312-cp312-win_amd64.whl.metadata (3.2 kB)                                                Collecting numpy==1.17.3                                                                                Downloading numpy-1.17.3.zip (6.4 MB)                                                                                ---------------------------------------- 6.4/6.4 MB 12.2 MB/s eta 0:00:00                                            Preparing metadata (setup.py): started                                                                                Preparing metadata (setup.py): finished with status 'done'                                                            Collecting scipy>=0.19.1                                                                                Downloading scipy-1.14.1-cp312-cp312-win_amd64.whl.metadata (60 kB)                                                   INFO: pip is looking at multiple versions of scipy to determine which version is compatible with other requirements. This could take a while.                                                                                Downloading scipy-1.14.0-cp312-cp312-win_amd64.whl.metadata (60 kB)                                                     Downloading scipy-1.13.1-cp312-cp312-win_amd64.whl.metadata (60 kB)                                                     Downloading scipy-1.13.0-cp312-cp312-win_amd64.whl.metadata (60 kB)                                                     Downloading scipy-1.12.0-cp312-cp312-win_amd64.whl.metadata (60 kB)                                                     Downloading scipy-1.11.4-cp312-cp312-win_amd64.whl.metadata (60 kB)                                                     Downloading scipy-1.11.3-cp312-cp312-win_amd64.whl.metadata (60 kB)                                                     Downloading scipy-1.11.2-cp312-cp312-win_amd64.whl.metadata (59 kB)                                                   INFO: pip is still looking at multiple versions of scipy to determine which version is compatible with other requirements. This could take a while.                                                                                Downloading scipy-1.11.1.tar.gz (56.0 MB)                                                                                --------------------------------------- 56.0/56.0 MB 13.9 MB/s eta 0:00:00                                           Installing build dependencies: started                                                                                Installing build dependencies: finished with status 'done'                                                              Getting requirements to build wheel: started                                                                            Getting requirements to build wheel: finished with status 'done'                                                        Installing backend dependencies: started                                                                                Installing backend dependencies: finished with status 'done'                                                            Preparing metadata (pyproject.toml): started                                                                            Preparing metadata (pyproject.toml): still running...                                                                   Preparing metadata (pyproject.toml): finished with status 'error'                                                       error: subprocess-exited-with-error                                                                                Preparing metadata (pyproject.toml) did not run successfully.                                                           exit code: 1                                                                                [44 lines of output]                                                                                + meson setup C:\Users\Remy\AppData\Local\Temp\pip-install-98cve3yd\scipy_a86da955f38d4a06bf818d4d4f216afa C:\Users\Remy\AppData\Local\Temp\pip-install-98cve3yd\scipy_a86da955f38d4a06bf818d4d4f216afa.mesonpy-8d3929_e\build -Dbuildtype=release -Db_ndebug=if-release -Db_vscrt=md --native-file=C:\Users\Remy\AppData\Local\Temp\pip-install-98cve3yd\scipy_a86da955f38d4a06bf818d4d4f216afa.mesonpy-8d3929_e\build\meson-python-native-file.ini                                          The Meson build system                                                                                Version: 1.5.2                                                                                Source dir: C:\Users\Remy\AppData\Local\Temp\pip-install-98cve3yd\scipy_a86da955f38d4a06bf818d4d4f216afa                Build dir: C:\Users\Remy\AppData\Local\Temp\pip-install-98cve3yd\scipy_a86da955f38d4a06bf818d4d4f216afa.mesonpy-8d3929_e\build                                                                                Build type: native build                                                                                Project name: SciPy                                                                                Project version: 1.11.1                                                                                C compiler for the host machine: gcc (gcc 8.1.0 "gcc (x86_64-posix-seh-rev0, Built by MinGW-W64 project) 8.1.0")                                                                                C linker for the host machine: gcc ld.bfd 2.30                                                                          C++ compiler for the host machine: c++ (gcc 8.1.0 "c++ (x86_64-posix-seh-rev0, Built by MinGW-W64 project) 8.1.0")                                                                                C++ linker for the host machine: c++ ld.bfd 2.30                                                                        Cython compiler for the host machine: cython (cython 0.29.37)                                                           Host machine cpu family: x86_64                                                                                Host machine cpu: x86_64                                                                                Program python found: YES (C:\Users\Remy\AppData\Local\Programs\Python\Python312\python.exe)                            Run-time dependency python found: YES 3.12                                                                              Program cython found: YES (C:\Users\Remy\AppData\Local\Temp\pip-build-env-4jm84h11\overlay\Scripts\cython.EXE)          Compiler for C supports arguments -Wno-unused-but-set-variable: YES                                                     Compiler for C supports arguments -Wno-unused-function: YES                                                             Compiler for C supports arguments -Wno-conversion: YES                                                                  Compiler for C supports arguments -Wno-misleading-indentation: YES                                                      Library m found: YES                                                                                Fortran compiler for the host machine: gfortran (gcc 8.1.0 "GNU Fortran (x86_64-posix-seh-rev0, Built by MinGW-W64 project) 8.1.0")                                                                                Fortran linker for the host machine: gfortran ld.bfd 2.30                                                               Compiler for Fortran supports arguments -Wno-conversion: YES                                                            Checking if "-Wl,--version-script" : links: YES                                                                         Program pythran found: YES (C:\Users\Remy\AppData\Local\Temp\pip-build-env-4jm84h11\overlay\Scripts\pythran.EXE)                                                                                Did not find pkg-config by name 'pkg-config'                                                                            Found pkg-config: NO                                                                                Found CMake: D:\SowftWare\cmake-3.18.2-win64-x64\bin\cmake.EXE (3.18.2)                                                 WARNING: CMake Toolchain: Failed to determine CMake compilers state                                                     Run-time dependency xsimd found: NO (tried pkgconfig and cmake)                                                         Run-time dependency threads found: YES                                                                                Library npymath found: YES                                                                                Library npyrandom found: YES                                                                                pybind11-config found: YES (C:\Users\Remy\AppData\Local\Temp\pip-build-env-4jm84h11\overlay\Scripts\pybind11-config.EXE) 2.10.4                                                                                Run-time dependency pybind11 found: YES 2.10.4                                                                          Run-time dependency openblas found: NO (tried pkgconfig and cmake)                                                      Run-time dependency openblas found: NO (tried cmake)                                                                                ....\scipy\meson.build:159:9: ERROR: Dependency lookup for OpenBLAS with method 'pkgconfig' failed: Pkg-config for machine host machine not found. Giving up.                                                                                A full log can be found at C:\Users\Remy\AppData\Local\Temp\pip-install-98cve3yd\scipy_a86da955f38d4a06bf818d4d4f216afa.mesonpy-8d3929_e\build\meson-logs\meson-log.txt                                                                        [end of output]                                                                                note: This error originates from a subprocess, and is likely not a problem with pip.                                  error: metadata-generation-failed                                                                                Encountered error while generating package metadata.                                                                                See above for output.                                                                                note: This is an issue with the package mentioned above, not pip.                                                       hint: See above for details.                                                                                [end of output]                                                                                note: This error originates from a subprocess, and is likely not a problem with pip.                                  error: subprocess-exited-with-error                                                                                × pip subprocess to install build dependencies did not run successfully.                                               │ exit code: 1                                                                                ╰─> See above for output.                                                                                note: This error originates from a subprocess, and is likely not a problem with pip.
复现

您是否已经正常运行我们提供的教程？
否

环境

请提供您使用的PaddlePaddle和PaddleX的版本号
3.0.1b
请提供您使用的操作系统信息，如Linux/Windows/MacOS
win10
请问您使用的Python版本是？
python3.12.5
请问您使用的CUDA/cuDNN的版本号是？
cpu

hi，您好，目前在未支持Python3.12，我们会在下一个版本支持，请使用首页推荐的Python版本（Python3.8,Python3.9,Python3.10）

你都3.12了，我3.11都没支持呢。 3.11都出来2年了。哈哈哈哈

3.11 的加速没支持，其他还是正常的。

paddle本身是支持3.12的，paddlex集成了非常多的不同类型的模型，不同的模型的依赖的第三方库比较多，现在的问题是第三方的库有一些不支持python3.12，我们会逐步协同这些库支持

The issue has no response for a long time and will be closed. You can reopen or new another issue if are still confused.

From Bot


Add a Gitter chat badge to README.md

hortonworks/registry now has a Chat Room on Gitter
@harshach has just created a chat room. You can visit it here: https://gitter.im/registry-users/Lobby.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

+1 also


Receiving Install Error when attempting to load system.json

Receiving the following error message when attempting to install the system.json from the link:
https://github.com/Pjb518/FoundryVTT-Level-Up-Official/releases/download/0.1.0/system.json
Installation failed: the "path" argument must be of type string. Received undefined.

Using Foundry Version: Version 9 - Build 242 - Stable

Yep, same

@Nehtanoj @Shadoghast If you look at the heading of that dialog window, you're attempting to install a world.


Error: spawn yarn ENOENT

I get this error when attempting to install with npx create-fullstack-react-app my-app. Has not happened with other npx installations
events.js:291
      throw er; // Unhandled 'error' event
      ^

Error: spawn yarn ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:268:19)
    at onErrorNT (internal/child_process.js:468:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:274:12)
    at onErrorNT (internal/child_process.js:468:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn yarn',
  path: 'yarn',
  spawnargs: [ 'install' ]
}

Hey @rodrigojmr, it looks to me that you're having some kind of problem with yarn?
Error: spawn yarn ENOENT

I have no problems installing other projects with npx or using yarn. Many of the other examples of this error I find are often in development, , or missing C:\Windows\system32 in system PATH variables, which I already have. I've only found this issue in trying to install this project.


Bug: As of Obsidian 1.4.0, FrontMatterCache no longer has position

Steps to reproduce:

Use const metadata = App.metadataCache.getFileCache(file) to get file metadata
Refer to metadata.frontmatter, which has the type FrontMatterCache
FrontMatterCache inherits from CacheItem, which has a non-nullable position field of type Pos
However, metadata.frontmatter does not have a position field

https://github.com/obsidianmd/obsidian-api/blob/master/obsidian.d.ts#L1518
This breaks my plugin, Novel Word Count, which checks for null on frontmatter but not on frontmatter.position.
EDIT: I was firefighting because the plugin crashed for my users, but now I see in the release notes that FrontMatterCache isn't supposed to inherit from CacheItem anymore. Is there another way to get the start and end position of frontmatter? My users don't like frontmatter being included in their word and page count.

Awesome, thank you for the reply. I see why that's necessary. Very glad to see there's a painless way to update.

You'll likely want to use a fallback for older versions of obsidian for a while cache.frontmatterPosition || cache.frontmatter?.position

Yeah, that's what I ended up doing. :+1: thanks!


build: improved prepare.sh

assure we use bash strict mode
avoid shallow errors on full clones
make script bit more idempotent

Signed-off-by: Sorin Sbarnea<EMAIL_ADDRESS>

/ok-to-test

LGTM

LGTM but definitely want a head nod from @baude or @mheon.  Happy green test buttons.

/approve

/lgtm


fix: removes cluster-role role as it should be already in charms

The cluster-role ClusterRole is something that should be handled by charms, not by this operator.

Are there corresponding PRs to add the cluster role to the charms? How's this cluster-role being used right now? Do we not need a cluster role with access to all those crds?

Re @agathanatasha, the cluster-role ClusterRoles are for the charm workloads themselves (not the users), and are deployed in their respective charm.  Those would be the ClusterRoles that are created in a podspec call creating the workload, or maybe as part of that charm's manifest


Use docker provider and preview channel

Same approach as in blog post here: https://blog.docker.com/2017/09/docker-windows-server-1709/
We're now publishing EE preview builds in a separate channel. These builds have support for all the new Windows Insider goodness like improved ingress networking, LCOW and named pipe mounting.

cc @PatrickLang

Can we sync on this in ~2 weeks? We should talk strategy to get the OneGet providers converged and figure out the future direction. cc @taylorb-microsoft

@PatrickLang the referenced page in particular contains instructions to install Docker CE for use with Insider builds, which is problematic. This PR changes the page to use EE Preview, which matches our blog posts and addresses the CE reference. So we'd like to push it through.
Then when we're ready we can have the separate conversation on converging our mutual EE on WS2016/1709 docs.

@PatrickLang see comment above. What needs to happen to get this merged?

The one hesitation I have is that we found it handy on a few occasions to implement workarounds for insider related issues without risking mainline production...

@taylorb-microsoft yes, but you did that by creating a parallel provider instead of handling the workarounds in one provider codebase. With @johnstep's changes, we can handle this stuff per-channel. For example:
Install-Package -Name Docker -ProviderName DockerProvider -RequiredVersion preview

... will do the LCOW monkey business setup.
As the next preview/insider cycle rolls around, we'd be happy to work with you to handle that in the installer

I feel like we'll be able to resolve this PR more easily if we're clear on how it fits with the broader story we're telling about Docker versioning for Windows users.
Here's my understanding of that story, just to make sure we're all on the same page...

Today, we have a total of four channels of Docker versions:

Docker CE & Docker CE "Edge"
Docker EE & Docker EE "Preview"

In light of those versions, here's the versioning "story" we're telling Windows/Docker customers:

Use Docker CE on Windows 10 for stable developer scenarios
Use Docker CE Edge on Windows 10 to play with all of the latest/greatest Docker features, which may not yet be stable
Use Docker EE with Windows Server 2016 for enterprise production scenarios
Use Docker EE Preview with Windows Server 2016 to POC latest Docker features which are not yet supported in production

In parallel to this context, we have our download/install story for Docker on Windows. It's:

For Docker CE, download either the stable or edge version of Docker, which comes with a UI, here
For Docker EE, use PowerShell to install Docker on Windows Server 2016

And this--the workflow for installing Docker EE through powershell--is where we get to this thread's discussion:

In general, users need to be aware of two steps for installing Docker through PowerShell:
(1) Installing a module
(2) Actually installing Docker EE

And, if I'm correct, here we're trying to sort out our story for (1). Today there are two modules:
The DockerProvider module:  Install-Module DockerProvider

--> This is the way to get the latest version provided by Docker

The DockerMsftProvider module: Install-Module -Name DockerMsftProvider -Repository PSGallery -Force

--> This is the way to get the latest version of Docker that has been validated by Microsoft  (so, it's the latest version that we're able to support)

So, with the above in mind--I think the goal of this PR fits into our larger goal of making sure this story is clear to our users.
Do we understand our overall strategy for achieving that? If so, it should be easy for us to reflect that in our docs. If not, would you like me to come up with a quick recommendation on how we could word this in our docs (again, based on the above)? Would that help this move forward and solve the broader issue of making sure our users aren't confused about versioning?

@kallie-b good summary. a couple points relative to this PR:
1 - The DockerProvider module was created to support LCOW. It is the only provider capable of installing EE Preview builds today.
2 - This PR is specifically concerned with fixing the instructions for installing Docker on Windows Server Insider builds. EE Preview is the only build for use with Server Insider builds. The page currently says to install Docker CE 17.06, which is absolutely wrong.
I agree providing a better overall story is important. Can you open a separate issue?

Yes, absolutely. Here's the new PR: https://github.com/MicrosoftDocs/Virtualization-Documentation/issues/663
@enderb-ms, as I know Taylor has tapped him to jump in here :)

Hi, please see my pull request #666 . My I idea would be after reading your comments to make those kinds of changes to Windows Server Quick Start. After that page has been fixed. Remove the whole Windows Insider Quick Start. Rewrite it under Windows Server Quick Start. Starting from "Install Base Container Image" and merge it with Step 2. Also update "About Windows Containers" and move some text there.

This is an old pull request that did not get merged in time - and now has conflicts.


Custom id not set when inserting data

Hi,
When I define a model with custom uuid id attribute like this:
class User extends Model {
  static fields() {
    return {
      id: this.attr(() => uuid())
      name: this.attr(''),
      email: this.attr('')
    }
  }
}

And then insert new data into the store:
User.insertOrUpdate({
  data: {
    name: "John Doe",
    email<EMAIL_ADDRESS>  }
}).then(result => {
  const idOnInsert = result.users[0].id
  console.log('result', result)

  /*
  users: Array[1]
    0: User
    $id: "_no_key_1"
    id: "ab2ac650-00d6-11ea-b6ef-f116801352a9"
    name: "John Doe"
    email<EMAIL_ADDRESS>  */

  console.log(`User with id: ${idOnInsert}`, User.find(idOnInsert))
  /*
  User with id: ab2ac650-00d6-11ea-b6ef-f116801352a9
  null
  */
})

The custom id attribute(uuid in this case) is simply not set.
As you can see the $id attribute on the User is "_no_key_1" after the user is inserted. However, the id attribute is correct and that is the generated uuid.
Right now, I work around this issue by instantiating the model first data = new User(user) and then inserting into the store User.insertOrUpdate({ data }).
This is rather inconvenient for example when loading data from the API with the axios plugin.
Here's the repro sandbox: https://codesandbox.io/s/vuex-orm-uuid-bug-wmmjc
Thanks a lot for looking into this!

Oh yeah, this is true. This is happening because the callback within this.attr is called after the $id is set. We should be fixing this.

@kiaking this is resolved with id: this.uid(() => uuid())?

@cuebit In fact yes, that should work! Id will be generated when instantiating the model so both $id and id should have the same value when using this.uid() 👍
@petertoth Canyon check the above method and see if everything works correctly?

@kiaking Looking at some closed issues I believe uid attribute was designed with this in mind. I have tested this and works perfectly.
Would be keen to get @petertoth’a feedback before closing.

Yes I can confirm it works as expected now. Thanks for looking into it!

Niiiice 👍


[fpga] Update slice to work with 32kB ROM

The 32kB ROM configuration uses 4-bit RAM cells which were previously  not supported by the slice scripts. This commit adds the following changes:

Update the Vivado rom.mmi generation script to support 4bit wide address ranges.
Update the gen_vivado_mem_image.py to support swapping of byte nibbles. This is needed in order to match the expected bit order in the updatemem command.

Closes lowrisc/opentitan#8716.

Thanks for fixing this @moidx ! This looks good to me. I assume you successfully tested this on the FPGA, right?

Yep. Tested manually :).


Feature Request: fuse-like mount on Windows

Output of restic version
restic 0.9.2 compiled with go1.11 on linux/amd64
What should restic do differently? Which functionality do you think we should add?
Support mount command on Windows.
What are you trying to do?
Mounting a backup repository on Windows. I'm working on a proof of concept and wanted to discuss the design as soon as possible. At the moment, I use dokany, which allows to create a virtual file system on Windows.
The drawbacks of using dokany:

requires a driver to be installed
requires CGO to compile the go bindings

Given these drawbacks, would you still be keen to have this in restic core? Or should I implement this as a separate program instead? The advantage of having it in restic core would be that code between the fuse and dokany implementation could be shared.
Did restic help you or made you happy in any way?
I'm just starting to use restic and want to migrate my whole backup system to it. However, having a better Windows integration is a must in order to be usable for regular users.

A drawback of implementing this as an external tool is that the repository must be opened multiple times as there is no client/server model in restic where it would respond to queries on stdin or something.
So for an external tool to work, it must call restic many times and gather information. Also, I did not find a way to query the contents of snapshots partially (say by path without recursing into subdirectories). For huge snapshots, it might take really long to fetch their directory listing, although not the entire hierarchy would be needed at one time (only when the directory is actually opened).

After further discussion with @fd0, we decided that on Windows, we'd rather support a WebDAV and a native http interface (#485, #60), because we don't want to integrate a CGO dependency into restic.
If restic gains the internal http interface, then an external application could easily use this to provide a dokan mount on Windows.


Perform compression before rsync

So that we can more easily substitute a non-executable target like S3, etc.

 Archive to S3 and decommission server


VisualShader problem with UI

Godot version:
3.1
OS/device including version:
win10, gt1030
Issue description:
In create node menu via right-click, there are no items to scroll through. You can scroll only with the mouse wheel, which is not available to me.

Please add any buttons for scrolling. For example:

A mouse click does not process the layer, a click is made on any node from the stack.

And in general, in Godot, working with the viewport (3d / 2d - view) takes place through the mouse wheel, which not available for many people. Please do as in Blender the "emulate middle mouse button" mode.

#26164 will fix it


Need more info on how to make current() reactive

I'm super new to Meteor and I'm struggling to complete even a simple task...
I want to add an "active" class to a react component if the current route matches a certain condition. This works on page load but when the route changes the class doesn't update - it's not reactive.
From the docs it looks like I need to use Tracker to make it reactive but I have no idea how to put that together with react meteor data/createContainer so my component re-renders when the path updates.
Any ideas?

Solution: https://forums.meteor.com/t/reactively-set-active-class-react-depending-on-which-flowrouter-route-is-active/22441/3


WFCORE-1908 Metric attribute is not writable.

https://issues.jboss.org/browse/WFCORE-1908
METRIC is read-only attribute https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/java/org/jboss/as/controller/registry/AttributeAccess.java#L44

@soul2zimate could you open a corresponding PR issue for EAP7 please?

@jfdenise could you approve it please?

I think this master branch is for EAP 7.1.0 GA.

@soul2zimate you're right. sorry about that

Thank you for this fix. If that is not too complex to test, could we have a simple unit test to cover it?
JF.

Thanks for review, a simple test is added to cover this issue.

Hi @soul2zimate, thank you very much for the changes. That is good to merge.
Thanks.
JF


[Feature Request] switching animation of'el-tabs/el-tab-pane'content

Existing Component
是
Component Name
el-tabs/el-tab-pane
Description
Suggested 'el-tabs/el-tab-pane' to increase the switching animation of the content area
建议'el-tabs/el-tab-pane'组件增加内容区域的切换动画

Sorry, we have no plan to support this.


Remove hardcoded trust_domain and retrieve it from xDS server pushed

add trust_domain field in Workload and retrieve it from server pushed

@PlatformLC: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Some "protocols" should always be enabled

e.g.

collaborate
file_contents
scoring
unlock

We'll have to go through them one-by-one and decide if they should be default later.
This would mean we don't have to change .ok files for the autograder, and we'd have less bugs releasing assignments

Closed in #278


Dispose singleton instances at container disposal

fix #145, @micdenny please review.

great, thanks!

@mauroservienti bump the version, so I can merge it

@mauroservienti you will have to rebase, because I've merged #207

@micdenny rebased and bumped.

thank you!


Library - add publishing event to LO

PMC example: https://lux-front-sbx.collections.yale.edu/view/text/96d4e28a-decd-4d03-8f12-15d0ae05305d
e.g. record ID<PHONE_NUMBER>
<year>2018</year>
YUL example: https://lux-front-sbx.collections.yale.edu/view/text/5b6afc6d-16c8-4685-9663-3b7412de441f
Recipe from YUL: https://linked-art.library.yale.edu/node/67abd2f7-5011-49fd-b8b5-e1da1795ed0e
"used_for": [
{
"type": "Activity",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300054686",
"type": "Type",
"_label": "Publishing"
}
],
"took_place_at": [
{
"id": "https://linked-art.library.yale.edu/node/3fed51e1-9dac-426a-b975-1a491742c882",
"type": "Place",
"_label": "Scotland"
}
],
"timespan": {
"type": "TimeSpan",
"identified_by": [
{
"type": "Name",
"content": "2018",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300404669",
"type": "Type",
"_label": "Display Title"
}
]
}
],
"begin_of_the_begin": "2018-01-01T00:00:00",
"end_of_the_end": "2018-12-31T23:59:59"
}
}

The publishing event is there, but the issue is that the year is missing.

So perhaps addressed with resolution of https://github.com/digirati-co-uk/pmc-lux/issues/18

The year is present in here though?
https://lux-front-sbx.collections.yale.edu/data/text/96d4e28a-decd-4d03-8f12-15d0ae05305d
  "used_for": [
    {
      "type": "Activity",
      "_label": "Publishing",
      "timespan": {
        "type": "TimeSpan",
        "_label": "2018",
        "end_of_the_end": "2018-12-31T23:59:59Z",
        "begin_of_the_begin": "2018-01-01T00:00:00Z",
        "_seconds_since_epoch_begin_of_the_begin":<PHONE_NUMBER>,
        "_seconds_since_epoch_end_of_the_end":<PHONE_NUMBER>
      },
      "classified_as": [
        {
          "id": "https://lux-front-sbx.collections.yale.edu/data/concept/8f7f85dd-8517-476a-a7bc-1d8b53e08404",
          "type": "Type",
          "_label": "Publishing",
          "equivalent": [
            {
              "id": "http://vocab.getty.edu/aat/300054686",
              "type": "Type",
              "_label": "Publishing"
            }
          ]
        }
      ],
      "took_place_at": [
        {
          "id": "https://lux-front-sbx.collections.yale.edu/data/place/6aeb72d0-11c3-4f93-9126-cce175dc695e",
          "type": "Place",
          "_label": "Edinburgh"
        }
      ],
      "carried_out_by": [
        {
          "id": "https://lux-front-sbx.collections.yale.edu/data/group/637a5a48-35d3-41b1-8264-9720efd14b1c",
          "type": "Group",
          "_label": "Edinburgh University Press"
        }
      ]
    }
  ],

https://github.com/tomcrane/linked-art-net/commit/4f3ef0c6000624a6e72635df8bc1fd874df25dfd


Should check-asm unit tests check intermediate assembly instead of final assembly?

Checking intermediate assembly before register allocation and before labels are realized is easier and more robust. For example, I'm trying to write asm unit tests for https://github.com/FuelLabs/sway/pull/3523, but I can't really test jump offsets. If I was testing the intermediate assembly instead, I would have access to the jump labels and I would be able to write more robust tests (using regex for those labels etc.). Besides, what we really want to test here, I think, is that the assembly builder is correct. The rest of the flow can really only be tested in E2E tests for the most part.

Yep, sounds fair.
I would like to re-label the different stages some more.  I already have done this a bit in the asm_generation by having AbstractProgram, AllocatedProgram and FinalProgram.
And so there's #2907 which would print these different stages and we could therefore add them as inputs to the tests.  We may also want to check against the ASM before we optimise it further (the AbstractProgram) as well as the register-allocated but still abstracted-code-flow ASM (the AllocatedProgram) as you suggest above, or the final ASM as we do now.


fix: add cdn to pwa cache

:tada: This PR is included in version 3.1.141 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Resume should be opened in new tab

While clicking the Resume in the Navigation bar the Resume file should open in new tab

Would You like to work on this issue yourself?

Yes

Assigning it you then.

Closing this.


Update SARIF repot template

Remove character 'v' from start of version string.
Update rule name according to .Type value.
Update rule id format, remove severity from id to convert to sarif level.
Update result location Uri points to file.
Add base Uri id.
Remove region property for now.

This looks good to me. Just one note, I had a branch named sarif_fixes where I was planning to store these changes. That way, we can PR the entire thing upstream when we're ready. Thanks for helping with this.

hi @nathanstocking, I started working on your branch and later found I cannot push to remote due to permission issue, so I created my own branch. Please let me know if you'd like move the changes to your branch (need setup my access first).
I already created the PR merging from my branch to upstream @ https://github.com/aquasecurity/trivy/pull/935


Fixes #296 -- Ensure test users have an email address.

This was required due to a change in Django's development branch (django/django#88586314).

Coverage remained the same at 100.0% when pulling 9e435f3f9e55f88beec5033baa1b8a4ec9aeaf17 on jambonsw:django-master-fix into aaa4516d4b455f79fa0fe9f6626b34d1e67e2abe on pinax:master.

Closing; I didn't see #297.


Missing file names

All the MP3 files generated by the downloader are named _.mp3

And the logs show:
WARNING: Assuming --restrict-filenames since file system encoding cannot encode all characters. Set the LC_ALL environment variable to fix this.
WARNING: Unable to extract video title


Submodule issues when using FMRIPREP workflows in your own nipype pipline

Hello all,
Not sure if this is the correct forum to post this but I wanted to use the phase difference fieldmap workflow from FMRIPREP to prepare my fieldmaps without using the whole of FMRIPREP (I have high resolution patial brain data and therefore I do my own preprocessing). This is an issue because when I import the workflow via this command from fmriprep.workflows.fieldmap.phdiff import init_phdiff_wf and set it to run I get the following error:
  File "BIDSSEvsGEPhaseAnalysis.py", line 339, in <module>
    metaflow_exec_graph = metaflow.run(plugin='MultiProc', plugin_args = {'n_procs' : 14})
  File "/cfmm/home/ostanle2/.virtualenvs/nipype3.6/lib/python3.6/site-packages/nipype/pipeline/engine/workflows.py", line 592, in run
    execgraph = generate_expanded_graph(deepcopy(flatgraph))
  File "/cfmm/home/ostanle2/.virtualenvs/nipype3.6/lib/python3.6/site-packages/nipype/pipeline/engine/utils.py", line 937, in generate_expanded_graph
    graph_in = _remove_nonjoin_identity_nodes(graph_in, keep_iterables=True)
  File "/cfmm/home/ostanle2/.virtualenvs/nipype3.6/lib/python3.6/site-packages/nipype/pipeline/engine/utils.py", line 813, in _remove_nonjoin_identity_nodes
    for node in _identity_nodes(graph, not keep_iterables):
  File "/cfmm/home/ostanle2/.virtualenvs/nipype3.6/lib/python3.6/site-packages/nipype/pipeline/engine/utils.py", line 829, in _identity_nodes
    print(isinstance(node.interface, IdentityInterface))
AttributeError: 'Workflow' object has no attribute 'interface'

This error can be traced back to the networkx topological_sort not exanding the fmriprep workflow since it is imported as a niworkflow.nipype object and not a nipype object. I think this is caused by the fact that the fmriprep workflow uses the niworkflow submodule of nipype and not the version I have installed on my machine.
What is the correct way to connect an FMRIPREP workflow to another nipype workflow which isn't based in niworkflows? Usually the nipype version is specified by a requirments.txt file and so both objects would use the same nipype version. Should I be modifying the FMRIPREP workflow to use the system version of nipype?
Thank you,
Olivia

So one possibility here is for us to move back to using nipype as a dependency, rather than a submodule. We've made a concerted effort to increase the frequency of nipype's release schedule, the lack of which was the primary problem that led to this solution, and we've now had four on-time monthly releases.
In the meantime, the only other ways to work are to either pull the fmriprep sub-workflow out and re-build it based on native nipype interfaces, or to import all of your nipype components from niworkflows.nipype.
@oesteban @chrisfilo How do we feel about reverting to official nipype releases? It will mean that any hot-fix niworkflows releases that happen between upstream releases need to temporarily house the entire fix in niworkflows. But I think that's a pretty small price to pay for compatibility, when we're on a <1 month cycle.

Thanks for the speedy reply! For now I'll rebuild it on native nipype and I'll keep an eye on this thread so I can revert back if you guys decide to use nipype as a dependency again.

I'm all in with official nipype

+1
On Wed, May 16, 2018, 1:57 PM Oscar Esteban<EMAIL_ADDRESS>wrote:

I'm all in with official nipype
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/niworkflows/issues/239#issuecomment-389628888,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOkp94cYhXIxtacrHzqpPJbCCC8-Vszks5tzHazgaJpZM4UBoGG
.

Sounds good. As there have been some fixes that we depend on since 1.0.3, I propose we switch back (#241) when 1.0.4 is released.

Hi @ostanley. Niworkflows 0.4.0+ interfaces will be usable with standard nipype installations, as will fMRIPrep 1.1.0+, which should be available in ~2 hours.


Modify formatter for project

I checked "Never join lines" and unchecked "Remove blank lines" in comments section.

Codecov Report

Merging #1042 into dev will decrease coverage by 0.47%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #1042      +/-   ##
============================================
- Coverage     51.26%   50.79%   -0.48%
+ Complexity     3005     2969      -36
============================================
  Files           120      120
  Lines         28001    28001
  Branches       4686     4686
============================================
- Hits          14354    14222     -132
- Misses        11489    11631     +142
+ Partials       2158     2148      -10

Flag
Coverage Δ
Complexity Δ

#JDBC42
50.35% <ø> (-0.08%)
2925 <ø> (-8)

#JDBC43
50.72% <ø> (+0.06%)
2966 <ø> (+8)
:arrow_up:

Impacted Files
Coverage Δ
Complexity Δ

...osoft/sqlserver/jdbc/dataclassification/Label.java
0% <0%> (-100%)
0% <0%> (-3%)

...ver/jdbc/dataclassification/ColumnSensitivity.java
0% <0%> (-100%)
0% <0%> (-2%)

...erver/jdbc/dataclassification/InformationType.java
0% <0%> (-100%)
0% <0%> (-3%)

...r/jdbc/dataclassification/SensitivityProperty.java
0% <0%> (-100%)
0% <0%> (-3%)

.../dataclassification/SensitivityClassification.java
0% <0%> (-75%)
0% <0%> (-2%)

...erverColumnEncryptionCertificateStoreProvider.java
0% <0%> (-36%)
0% <0%> (-3%)

...va/com/microsoft/sqlserver/jdbc/StreamColumns.java
54.91% <0%> (-31.15%)
22% <0%> (-9%)

...om/microsoft/sqlserver/jdbc/ReaderInputStream.java
43.95% <0%> (-3.3%)
15% <0%> (ø)

...om/microsoft/sqlserver/jdbc/SimpleInputStream.java
55.97% <0%> (-1.5%)
15% <0%> (-1%)

.../microsoft/sqlserver/jdbc/SQLServerConnection.java
47.26% <0%> (-1.06%)
367% <0%> (-8%)

... and 7 more

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 9f78a13...4764cae. Read the comment docs.

We have an alternative. Closing as not needed.


.git folder parser alternative without external dependencies

This PR replace the dependency to src-d/go-git using a custom .git folder parser without any external dependencies.

Can we include some tests?

Can we include some tests?

I'll try, it's hard because reads the .git folder, but I guess I can do some tests of the regexes in use, at least...

Can we include some tests?

Done @drodriguezhdez

Checked with go-ethereum.
It seems branch is not being sending:
https://app.scope.dev/dashboard/b774c8da-2494-4ede-8d2f-b0321ff3cd7c/f9775d86-9c81-43d9-a28c-3f3cb60f30b4/default/explore/inspect/fe9cb4954f12ec9709d448d6f274c7088322eb60/00000000-0000-0000-70b3-e3e4509d0ff2/trace?spanId=00000000-0000-0000-0713-8c606cc58d21

Checked with go-ethereum.
It seems branch is not being sending:
https://app.scope.dev/dashboard/b774c8da-2494-4ede-8d2f-b0321ff3cd7c/f9775d86-9c81-43d9-a28c-3f3cb60f30b4/default/explore/inspect/fe9cb4954f12ec9709d448d6f274c7088322eb60/00000000-0000-0000-70b3-e3e4509d0ff2/trace?spanId=00000000-0000-0000-0713-8c606cc58d21

Done, the branch = HEAD when a detached commit is being used was missing.

Tested in local, with repos no containers, and with repos inside containers.
https://app.scope.dev/dashboard/b774c8da-2494-4ede-8d2f-b0321ff3cd7c/400412c1-517f-4f94-8291-7cc167d92ca4/default/explore/inspect/93645c357bde143c6275b6119fd255a8e8071287/00000000-0000-0000-69b2-30adb11f0355/trace?spanId=00000000-0000-0000-480d-57aa489125bb
Approved


Update docs to reflect breaking change in v0.16.0

Problem
There was a breaking change introduced in v0.16.0 where the waitForConnectedPeer function was replaced with waitForRemotePeer. The example code has been updated but not the documentation.
Solution
Update the documentation to reflect this new change.
Notes

js-waku version: v0.16.0

Fixed with #35


Update anything.js

added things for multiply,divide,subtract and add

This repo is really fun. @Rabrennie thank you for everything anything.

No problem @kotAPI . I'm glad you like it and thanks for your contributions


Wrong link generation of some URLs

Gitea version (or commit ref): Current master: f1d2f16b544ef5ef66a45d0a8859d133c46979a4
Git version: Not relevant
Operating system: Not relevant
Can you reproduce the bug at https://try.gitea.io:

[x] Yes (provide example URL)
[ ] No
[ ] Not relevant

Description
Take as example these links:
https://foo.bar.com/post/2017/03/16

https://foo.bar.com/post/2017/03/16/index.html

https://foo.bar.com/post/2017.03.16

They're not Gitea/GitHub issues, but Gitea thinks it is. Screenshot:

try.gitea.io link: https://try.gitea.io/andreynering/issue-test/issues/1

There's also the slight annoyance where just typing #1337 becomes a broken link since it's not a valid issue/PR-number 😅

FIxed by https://github.com/go-gitea/gitea/pull/2292


[Request]:

App to request
Axis Bank Mobile Banking
App Store link
https://apps.apple.com/in/app/axis-bank-mobile-banking/id699582556
App version
6.9
Jailbreak
Odyssera1n, Checkra1n
Bypass tried

[X] A-Bypass
[X] Liberty Lite (Beta)
[X] Hestia
[X] Shadow
[ ] HideJB
[ ] iHide
[X] KernBypass (iOS 12.0 - 14.2)
[X] vnodebypass
[X] Disabling tweak injection with Choicy or libhooker-configurator

Which bypass worked?
So far no known jailbreak bypasses for this app!
Checklist before submission

[X] The app is missing from the table, or bypasses are not working anymore.
[X] I have checked through all open issues and none matched my app.
[X] I have tried at least one bypass before submission.

#2 (forget to close)


Use context

During the extraction of the code from the dashboard huge performance degradation was introduced on purpose. A reminder of the reasons:

the lib shouldn't depend on redux
the lib should be compatible with dashboard (react v15.6.1)
react <16.3.0 didn't have official context support

This PR fix it but requires new react.
Benchmarking of mouse moving over the same nodes with 6x CPU throttling:
Master. Average event takes ~630ms. When I move the mouse faster, react cancels events and doesn't rerender the tree at all:

This PR. Average event takes ~200ms:

Without CPU throttling in this branch, I don't feel any lag anymore.
P.S. But 200ms is way too much even for weak CPU. We will need to improve performance further later.

That's quite an improvement. Out of curiosity, did you benchmark updating to the new react version, before using context?

I have tested it on the with source code editor example. And for examples, we use react 16.3.2 from the start.
Anyway, the performance boost isn't related to react version but how we render the tree. Before we were updating all the tree because uast props is changing on every event. Now we update only changed nodes. The same results are achievable by using redux or old version of context (which wasn't stable/documented but used by redux and many other libs for years).


in favor of 'istanbul report' over wrapper

Is there any specific reason for keeping istanbul-combine? For what I can see the results are the same.

Hey @probot-stale[bot], I appreciate you care about this. I don't know if this has changed in master but I really think it's an improvement. Could you advice how can I get more attention?

thanks @stale, this is no longer relevant


VM: Implement support for constants being evaluated by front end

This is the tracker issue for implementing support in the VM for constants being evaluated by the front end

[ ] Implement support in JIT mode
[ ] The bytecode compiler currently implements constant expression evaluation, with CFE doing it that becomes redundant
[ ] The AOT pipeline implements constant expression evaluation as a kernel to kernel transformation, with CFE doing it that becomes redundant

Language tracking issue: https://github.com/dart-lang/language/issues/60
Frontend implementation tracking issue: https://github.com/dart-lang/sdk/issues/35079

/cc @aartbik @alexmarkov who should own this issue?

I marked us both as owner for now. Alex probably wants to do the bytecode side. I can help with the other stuff after consulting with Alex.

Any updates on this issue?

I am not aware of blocking VM work. For JIT, we could eagerly evaluate the constants in the constant table (which becomes larger) to reduce compile-time. For AOT, I don't think anything is not working, and removing code would be just a cleanup. I let Alex comment on bytecode status.

I think this issue can be taken off from the 2.3 milestone list, it is more for clean up work to remove the redundant constant expressions evaluation code from the AOT and bytecode paths once CFE has solid support for constant expressions evaluation.

Lazy constant reading has been submitted. Items and ideas to follow up on:
(1) by setting the raw-bytes array and hash map from the start, we may be able to completely avoid the "pending" and "delayed" data structures; we should be evaluate every constant when needed first
(2) by peeking into pragma's we may avoid the cyclic detector altogether
(3) removed unused code and data structures when this stabilizes

Approved fails to follow-up on:
| vm-kernel-precomp-obfuscate-linux-release-x64 | language_2/const_inference_test | RuntimeError |

A fix for the cyclic test crash is pending (see https://dart-review.googlesource.com/c/sdk/+/107000). As for the constant inference, the difference is right after canonicalize:
v16 <- Constant(#Closure: (Null) => Null from Function 'constFunction': static.) T{_Closure}
vs.
v16 <- Constant(#Closure: (dynamic) => dynamic from Function 'constFunction': static.) T{_Closure}

The canonicalize difference happens in LoadFieldInstr::Canonicalize() with the following code
   if (Evaluate(instance()->BoundConstant(), &result)) {
      if (result.IsSmi() || result.IsOld()) {
          return flow_graph->GetConstant(result);
      }
  }

with Evaluate() returning the different values
v15 <- Constant(#Instance of 'C<Null>') T{C}
Instance of 'C<Null>'
Closure: (Null) => Null from Function 'constFunction': static.

v15 <- Constant(#Instance of 'C<Null>') T{C}
Instance of 'C<Null>'
Closure: (dynamic) => dynamic from Function 'constFunction': static.

Fix for crash confirmed:
selected bot: vm-kernel-precomp-linux-debug-x64
The following tests are now succeeding:

BOT/CONFIG
TEST

vm-kernel-precomp-linux-debug-x64
language_2/cyclic_metadata_test/02

Fix for the failure is pending at https://dart-review.googlesource.com/c/sdk/+/107064

Confirmed fixes for all vm bots. Sample. below.
The following tests are now succeeding:

BOT/CONFIG
TEST

vm-kernel-precomp-linux-product-x64
language_2/const_inference_test

@a-siva any actionable items left for this?

I think there are no more known items, let me close it. If we find bugs we can open new issues for the failures.


Question about sp.load() command

Hello,
In tedlium3 train.py I see following lines
sp = spm.SentencePieceProcessor()
sp.load(params.bpe_model)

But on other I know that bpe_model is not passed to train.py. I would expect that the train.py script will fail. But actually it work. What am I missing?
Thanks,
AlexG.

I am sorry, there is default value
parser.add_argument(
    "--bpe-model",
    type=str,
    default="data/lang_bpe_500/bpe.model",
    help="Path to the BPE model",
)


If a member of an inner class has the same name as a variable in the outer class, the type of the outer variable is used for type-checking

Hi!  I noticed a bug in the new type-checking system.  It's easy to work around, but I figured it'd be good to know before 3.1 goes out.
Godot version:

Commit 2e877031369c35c918c014a7ae3688b6f555e5bd
The latest on the master branch.
OS/device including version:

Fujitsu Lifebook T734 with Windows 7 Professional, Service Pack 1.  All non-optional updates installed
Issue description:

With the new optional type-checking, there is incorrect behavior when a member of an inner class has the same name as a variable defined in the outer scope.  When the inner member is used in code, the parser incorrectly uses the type of the outer variable for type-checking.
Steps to reproduce:

Create a new script.  In that script, create an inner class with a typed member.

Create a variable with the same name as that typed member, but a different type

Create an instance of the inner class, and assign a value to its typed member.  This should cause a Parser Error, saying that there was a mismatched type.

Here's a full code sample that causes the error:
class Example:
	var s: String

var s: Dictionary

func test():
	var e :Example = Example.new()
	#The following line causes this error:
	#Parser Error: Assigned value type (String) doesn't match the variable's type (Dictionary).
	e.s = "string"

Minimal reproduction project:

The attached file also has some other behavior showing when the error does and doesn't occur.
project.zip

Further details:
This seems to only happen with variables defined in the outer-most scope of the script.  Local variables do not interfere with type-checking of inner class members, from my test.
If the instance of the inner class is not declared with its type, the error does not occur (no type-checking is done, as expected).


fix(error): avoid phpunit crash by triggering side-effect via count on testcase

@mfn this is a followup of https://github.com/sebastianbergmann/phpunit/issues/5866#issuecomment-2172429263
What do you think about the fix? I don't see any other option since we analyze the whole stacktrace.

Thank you @simPod and @mfn! Released with https://github.com/webonyx/graphql-php/releases/tag/v15.12.3.


Add pipeline format

Add pipeline type info.
Format pipeline's outputs by type info.

Codecov Report

Merging #372 (24ee27c) into main (e8d35bd) will increase coverage by 0.11%.
The diff coverage is 97.82%.

@@            Coverage Diff             @@
##             main     #372      +/-   ##
==========================================
+ Coverage   70.15%   70.26%   +0.11%
==========================================
  Files         223      224       +1
  Lines        8101     8135      +34
  Branches     1065     1069       +4
==========================================
+ Hits         5683     5716      +33
- Misses       2159     2160       +1
  Partials      259      259

Impacted Files
Coverage Δ

towhee/pipeline_format.py
96.15% <96.15%> (ø)

towhee/__init__.py
94.73% <100.00%> (-0.62%)
:arrow_down:

towhee/dag/graph_repr.py
38.20% <100.00%> (+2.90%)
:arrow_up:

towhee/engine/pipeline.py
80.00% <100.00%> (+1.62%)
:arrow_up:

towhee/tests/engine/test_engine.py
97.10% <100.00%> (ø)

towhee/tests/engine/test_graph_context.py
98.07% <100.00%> (ø)

towhee/tests/engine/test_pipeline.py
96.66% <100.00%> (+0.37%)
:arrow_up:

Continue to review full report at Codecov.

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

/lgtm


Add column has_manager to taxonomies table

type boolean

@barancw when you get the chance it would be helpful to add a flag has_manager to the taxonomies table
rails g migration AddHasManagerToTaxonomies has_manager:boolean
thanks

[ ] need to be added to category serializer too


Tweaked action descriptions

Current dependencies on/for this PR:

main

PR #142   👈

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: 🔄 Waiting for checks to pass
This pull request is currently waiting for CI and mergeability checks to pass before being merged.
This comment was auto-generated by Graphite.

Job Reference: yKnlmtOOFOAhqWzllqSL


"from ipynb.draw" should be "from draw_rna.ipynb.draw"

I think this issue refers to the example notebook. Note that the README.md also lacks the snippet where this should be shown, since there is an empty code block after "In brief:"


Update to v 1.24.0:

version and sha256 updated.
build number reset to 0.
skip rule updated.
dependencies updated.

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_21pbggeuew/clone/recipe/meta.yaml:32: python_build_tool_in_run: The python build tool packaging is in run depends
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_5cjj1be7w4/clone/recipe/meta.yaml:32: python_build_tool_in_run: The python build tool packaging is in run depends
Warnings were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_0andl4s8bo/clone/recipe/meta.yaml:26: remove_python_pinning: On arch specific packages, python deps should not be constrained.
WARNING: /tmp/abs_0andl4s8bo/clone/recipe/meta.yaml:33: python_build_tool_in_run: The python build tool packaging is in run depends
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_a7jcavwb5m/clone/recipe/meta.yaml:26: remove_python_pinning: On arch specific packages, python deps should not be constrained.
WARNING: /tmp/abs_a7jcavwb5m/clone/recipe/meta.yaml:33: python_build_tool_in_run: The python build tool packaging is in run depends
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_1c2mlnh56x/clone/recipe/meta.yaml:26: remove_python_pinning: On arch specific packages, python deps should not be constrained.
WARNING: /tmp/abs_1c2mlnh56x/clone/recipe/meta.yaml:33: python_build_tool_in_run: The python build tool packaging is in run depends
Errors were found


Plot=True referenced before assignment

When we call with "Plot=True" parameter, like this:
data_ = pd.read_csv('analytics_test.csv',                     index_col='timestamp',                     parse_dates=True,                     squeeze=True,                     date_parser=dparserfunc)
returns this error:
UnboundLocalError: local variable 'num_days_per_line' referenced before assignment
in anomaly_detect_ts.py file in 274. line:
...     if plot:         num_days_per_line         breaks         x_subset_week ...

Saw this as well

close this thanks for the fix by @hokiegeek2