add setdiff(::Interval, ::AbstractVector)

julia> ((1..2) \ 1.5)
(1.0..1.5 (closed–open)) ∪ (1.5..2.0 (open–closed))

julia> ((1..2) \ [1.5])
(1.0..2.0) \ [1.5]

We could do:
setdiffdomain(d1::Interval, d2::AbstractVector) =
    isempty(d2) ? d1 : setdiffdomain(d1 \ first(d2), d2[2:end])

But that is going to be horribly type-unsafe, and the complexity of the result depends on the length of the vector.
It would work though:
julia> (0.0..10.0) \ (2:6)
(0.0..2.0 (closed–open)) ∪ D₁

D₁ = (2.0..3.0 (open)) ∪ ((3.0..4.0 (open)) ∪ D₂)
D₂ = (4.0..5.0 (open)) ∪ ((5.0..6.0 (open)) ∪ (6.0..10.0 (open–closed)))

julia> typeof(ans)
UnionDomain{Float64, Tuple{Interval{:closed, :open, Float64}, UnionDomain{Float64, Tuple{OpenInterval{Float64}, UnionDomain{Float64, Tuple{OpenInterval{Float64}, UnionDomain{Float64, Tuple{OpenInterval{Float64}, UnionDomain{Float64, Tuple{OpenInterval{Float64}, Interval{:open, :closed, Float64}}}}}}}}}}}

But that type is not looking good. The result seems to be nested, that could probably be avoided.
In contrast currently:
julia> (0.0..10.0) \ (2:6)
(0.0..10.0) \ [2.0, 3.0, 4.0, 5.0, 6.0]

julia> typeof(ans)
SetdiffDomain{Float64, Tuple{ClosedInterval{Float64}, Vector{Float64}}}

It could make a UnionDomain{Float64,<:Vector} though this won't be type-stable because of the mixed open-closed intervals (there is the possibility of making an AbstractInterval whose clopenness is not part of the type). Though I agree leaving it as a SetdiffDomain is arguably cleaner.
Though perhaps (1..2) \ 1.5 should also be left as a SetdiffDomain?

I guess that would be more consistent. I think I'm using that elsewhere though, I'd have to check.
In the meantime I changed the example above so it becomes:
julia> (0.0..10.0) \ (2:6)
(0.0..10.0) \ 2.0:1.0:6.0

i.e., updating the eltype of a range now preserves the range (this is pending the resolution of https://github.com/JuliaLang/julia/issues/27138).

One year later and we still have:
julia> ((1..2) \ 1.5)
(1.0..1.5 (closed–open)) ∪ (1.5..2.0 (open–closed))

julia> ((1..2) \ [1.5])
(1.0..2.0) \ [1.5]

It is near impossible to avoid type instabilities when doing arithmetics with domains. I no longer worry about that, it just shouldn't be part of a time-critical code path. I do use the first kind of behaviour (subtracting a point). That means anybody can implement subtracting an array simply by iterating. So I'm inclined to leave it as is and close the issue.


Change latest event timestamp behaviour in search

Search has been changed as described in the last bit of this comment in #150.
Simply: latest visit should always be used for search unless no visits exist for a page (only then bookmark is used).
Make sure to remove all existing data before trying this branch.

All seems to be behaving as intended without any obvious bugs in the short time we've had to play with it. Merging in as we need to move on.
@mukeshkharita, you may want to rebase your branch from #150 on latest master. Main conflicts should be with PageResultItem: move your existing event handlers to src/overview/container.js, like handleTrashBtnClick, and no more hacky displayType - each result should have a derived hasBookmark flag now. Others should be straightforward, but of course feel free to send a message if any uncertainties :)


Upload haddocks

This addresses #10 .
I do not currently have a project in which I need to do a release and I don‘t wanna spam hackage without reason. So if anyone where to test this branch, I‘d be grateful.

Thanks for the contribution! I'll also test it the next time I release, but if someone beats me to it, let me know.

I have actually done a release with it today using cabal <IP_ADDRESS>. Worked fine!


Set up AppVeyor

Need to make sure that the cli doesn't break on Windows.

Would do that, need flowtype organisation access though.

Hi, Current version is not working on windows:
C:\dev\bugsnag-sourcemaps>flow-typed install -f 0.30<EMAIL_ADDRESS>C:\Users\szarouski\AppData\Roaming\npm\node_modules\flow-typed\dist\commands\run
Tests.js:45
      throw new Error("Unsupported os.type()! " + _node.os.type());
      ^

Error: Unsupported os.type()! Windows_NT
    at C:\Users\szarouski\AppData\Roaming\npm\node_modules\flow-typed\dist\comma
nds\runTests.js:45:13
    at Object.<anonymous> (C:\Users\szarouski\AppData\Roaming\npm\node_modules\f
low-typed\dist\commands\runTests.js:47:2)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\Users\szarouski\AppData\Roaming\npm\node_modules\f
low-typed\dist\cli.js:22:17)

Should I create a new issue or this thread is good enough?
Thank you.

@szarouski: I pushed a fix for this yesterday, but haven't published it yet: https://github.com/flowtype/flow-typed/commit/567032eb631e873d457bf5ffe51b99c02a44e9b6
Will do this very soon: I'm trying to get a few more PRs merged before publishing the next beta release.


Used this branch to do incremental fixes to get our Heroku working.

Bringing incremental Heroku auth fixes to main branch.

Reviewed and merged.


[R] Setup Travis Test

See reference of xgboost repo https://github.com/dmlc/xgboost
Because R-travis requires sudo. Let us only do it on OSX(I know this sounds strange:), where we have the sudo right. Current linux build uses container build that disables sudo

@hetong007 Let us know if you could help. Since you setup the travis for xgboost

related to #457

Oh should've seen this issue earlier. Yes there must be a sudo during linux build. Is it that if we enable sudo then some other builds could fail?

If sudo is disabled, then travis uses container based build, which caches the data and make things faster.
Unfortunately we cannot partially enable sudo, and I guess OSX test should be sufficient for most cases(usually OSX is the place to fail easier)

Got it. Yeah let's stick with just OSX for now.


feat: add RollingManifestWriter

Hi, this is in regards to #596 and still WIP.
The RollingManifestWriter implementation closely follows the java implementation.
It takes in a generator that produces ManifestWriter objects and rolls over to a new one once either the number of rows appended or the file size in bytes exceeds the target value.
It's not finished as of yet, I am still trying to find a good way to access the current file from the underlying reader. I tried to obtain that information from the ManifestWriter._writer.output_stream object, but that is write-only.
Any pointers on how to access the current file size of the manifest writer would help me a lot:)

I believe in the Java implementation we have a concept of a PositionOutputStream which is used to keep track of bytes written to each file with a position/counter. What we can do here is extend the current OutputFile, and OutputStream implementations to account for this and roll each based on that position.
For instance, the ManifestWriter can use the AvroFileAppender which calls it's length() method to determine the size. But this length method is calling the storedLength() method in PositionOutputStream.
https://github.com/apache/iceberg/blob/866021d7d34f274349ce7de1f29d113395e7f28c/core/src/main/java/org/apache/iceberg/avro/AvroFileAppender.java#L83

Sounds good, I will have a look at the implementation and make a suggestion. Thank you!

Hi, I finally had some time to continue working on this.
Based on your suggestions @geruh I added a tell method to the OutputStream protocol that returns the number of bytes written to the stream.
I then added __len__ to the AvroOutputFile which calls out to either OutputFile or OutputStream to get the number of bytes written, depending on whether the stream is closed or not.
Finally I extended ManifestWriter with a __len__ method that calls AvroOutputFile.
I initially tried to extend OutputStream with __len__ until I realized that both FileIO implementations fsspec and pyarrow offer OutputStream implementations that implement the tell method while neither supports __len__.
If we wanted to go with __len__ instead of simply using tell we might have to implement custom FsspecOutputStream and PyarrowOutputStream classes that implement __len__. This might well be the cleaner approach but introduce a bit more abstraction.
What do you think?

@Fokko Thanks for taking a look! Sorry about the formatting, should be fixed now:)


Add policy and policy_std columns to the aws_glue_catalog_database table

Add the column policy and policy_std to the table which will include the information pertaining to the Glue Data Catalog resource policy for access control.

We need to raise an issue to get policy related to the resource using resource arn as the data is not coming.

AWS has replicated the issue, now it's pending with them, lets work on an alternative else we mark this blocked [CASE<PHONE_NUMBER>] Glue - get-resource-policy resource CLI outcome

The API and CLI for get-resource-policy are not returning any results for the glue database resource.


failed to load config from vite.config.js error when starting dev server

Describe the bug
Failed to load config from vite.config.js error when starting dev server.
I did see #59 but an error persists.
Reproduction
npm init vite@latest vite-svelte-test --template svelte

cd vite-svelte-test
npm install
npm run dev

Logs
failed to load config from /Users/sfm17/software/personal/vite-svelte-test/vite.config.js
error when starting dev server:
file:///Users/sfm17/software/personal/vite-svelte-test/node_modules/@sveltejs/vite-plugin-svelte/dist/index.js:800
import { diff_match_patch, DIFF_DELETE, DIFF_INSERT } from "diff-match-patch";
                           ^^^^^^^^^^^
SyntaxError: The requested module 'diff-match-patch' is expected to be of type CommonJS, which does not support named exports. CommonJS modules can be imported by importing the default export.
For example:
import pkg from 'diff-match-patch';
const { diff_match_patch, DIFF_DELETE, DIFF_INSERT } = pkg;
    at ModuleJob._instantiate (internal/modules/esm/module_job.js:97:21)
    at async ModuleJob.run (internal/modules/esm/module_job.js:135:5)
    at async Loader.import (internal/modules/esm/loader.js:178:24)
    at async loadConfigFromFile (/Users/sfm17/software/personal/vite-svelte-test/node_modules/vite/dist/node/chunks/dep-11db14da.js:75342:31)
    at async resolveConfig (/Users/sfm17/software/personal/vite-svelte-test/node_modules/vite/dist/node/chunks/dep-11db14da.js:74965:28)
    at async createServer (/Users/sfm17/software/personal/vite-svelte-test/node_modules/vite/dist/node/chunks/dep-11db14da.js:73483:20)
    at async CAC.<anonymous> (/Users/sfm17/software/personal/vite-svelte-test/node_modules/vite/dist/node/cli.js:13959:24)

System Info
System:
    OS: macOS 11.4
    CPU: (8) x64 Intel(R) Core(TM) i7-8569U CPU @ 2.80GHz
    Memory: 1.44 GB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.4.0 - /usr/local/bin/node
    npm: 6.14.4 - /usr/local/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 91.0.4472.164
    Firefox: 88.0.1
    Firefox Developer Edition: 91.0
    Safari: 14.1.1
  npmPackages:
    @sveltejs/vite-plugin-svelte: ^1.0.0-next.11 => 1.0.0-next.13
    svelte: ^3.37.0 => 3.38.3
    vite: ^2.4.2 => 2.4.2

Severity
blocking all usage of vite-plugin-svelte

Can't reproduce with the steps provided.
I notice that you are using an outdated version of node 14 (14.4.0). Please update it and try again.
vite-plugin-svelte requires "node": "^12.20 || ^14.13.1 || >= 16"
If it still fails and you did any modification to the template after creating it, please provide a repository with them.

That was it! Thanks and sorry for the inconvience!

how to check systeminfo on windows project，please


(PUP-7559) Pass correct mode when lookup SELinux default context

Originally when the file did not exist we simply passed the
mode as zero causing the file type bits not to be set which
means matchpathcon(3) won't lookup the type based on the
correct type.
This changes so that we set the file type bits in the mode_t
passed down to the SELinux libraries based on the resource
ensure set to present, file, directory or link on the File
resource.
This fixes [1] and can be observed for SELinux file contexts
that modifies files in top directory but only for symlinks for
example this [2] httpd file context change.
The patch is backward compatible and does not break the API
for the methods in the Puppet::Util::SELinux module.
[1] https://tickets.puppetlabs.com/browse/PUP-7559
[2] https://github.com/fedora-selinux/selinux-policy-contrib/pull/366/commits/43318bf3e6415ea323952529afd4d3b49a8a040e

Can one of the admins verify this patch?

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

sed s/matchpatchcon/matchpathcon/g

sed s/matchpatchcon/matchpathcon/g in commit msg

ping

@joshcooper do you have a second?

Hi @tobias-urdin, thanks for your contribution! I'll take a look at this tomorrow.

Any update? :)

ping @joshcooper

Thank you for your contribution @tobias-urdin! I've added a commit to your PR and retargeted 6.x in https://github.com/puppetlabs/puppet/pull/8570. I'm going to close this one in favor of that, but know that we will still recognize you as the author/contributor. Thanks again!


rviz2 on Windows exits immediately with error "missing package manifest"

I have installed prebuild ROS2 release on Windows by following the instructions on https://index.ros.org/doc/ros2/Installation/Foxy/Windows-Install-Binary, using ros2-foxy-20200710-windows-release-amd64.zip from https://github.com/ros2/ros2/releases/download/release-foxy-20200710. The examples from https://github.com/ros2/examples work nice.
Unfortunately, rviz2 or ros2 run rviz2 rviz2 exit immediately after start with the following error message:
[INFO] [1596608900.452275300] [rviz2]: Stereo is NOT SUPPORTED
[INFO] [1596608900.459010700] [rviz2]: OpenGl version: 3.3 (GLSL 3.3)
[INFO] [1596608900.900045700] [rviz2]: Stereo is NOT SUPPORTED
[ERROR] [1596608900.957963000] [pluginlib.ClassLoader]: Could not find package manifest (neither package.xml or deprecated manifest.xml) at same directory level as the plugin XML file c:\dev\ros2_foxy/share/rviz_default_plugins/plugins_description.xml. Plugins will likely not be exported properly.
)

But the file c:\dev\ros2_foxy\share\rviz_default_plugins\package.xml exists, is readable and looks okay to me. Changing slashes or drives in environment variable AMENT_PREFIX_PATH doesn't help either. Any ideas how to fix this?
Many thanks.

rviz2 works fine after installing ros2 on Windows 10 following https://ms-iot.github.io/ROSOnWindows/GettingStarted/SetupRos2.html:
Install chocolatey, run cmd as admin and enter
choco --version
choco upgrade all -y
choco source add -n=ros-win -s="https://aka.ms/ros/public" --priority=1
choco upgrade ros-foxy-desktop -y --execution-timeout=0 --pre

Problem solved. Nice package!


Rails.application.config.active_record.belongs_to_required_by_default…

… is set to true for new Rails 5 app as mentioned in https://github.com/volmer/bootsy/issues/243.
http://blog.bigbinary.com/2016/02/15/rails-5-makes-belong-to-association-required-by-default.html

The dummy app in specs/dummy is working fine without that option. Is there anything missing in it?

Perhaps initiliazers/new_framework_defaults.rb. ?

@volmer, yes, because the dummy app does not have initiliazers/new_framework_defaults.rb and the Rails.application.config.active_record.belongs_to_required_by_default = true setting, so it is fine. However, all new Rails 5 app will have that setting set to true by default. So I think it would be better to either set the belongs_to as optional: true or give some guideline in README.md to tell people to set belongs_to_required_by_default to false.

yes, because the dummy app does not have initiliazers/new_framework_defaults.rb and the Rails.application.config.active_record.belongs_to_required_by_default = true setting

So do you mind adding the file to the dummy app then?

@volmer, added.

Thanks for contributing!


Expand scenarios covered by default arguments for environments

Problem
We are proposing to determine appropriate default arguments for node --eval, Electron, and ES6.
Using require.main to determine --eval (or REPL) gives false positive for ES6 main program.
Related: #5 #18
Solution

detect node --eval directly by checking options passed to node (-e, --eval)
no need to detect REPL because no user arguments from CLI?
test for bundled Electron app (using same approach as Yargs and Commander)
fallback to usual process.argv.slice(2)

If the proposed process.mainArgs was available, it would cover the  --eval and REPL cases.
Related PRs for Electron argument processing:

https://github.com/tj/commander.js/pull/1172/files
https://github.com/yargs/yargs/pull/1554/files

And for historical interest, the addition of defaultApp to work-around the variant behaviour:

https://github.com/electron/electron/issues/4690#issuecomment-217435222

To Do

tests (might wait for feedback on PR before rolling tests)

Example
% node -e 'console.log(require(".").parseArgs())' 1 --foo 2 3
{
  args: { foo: true },
  values: { foo: [ undefined ] },
  positionals: [ '1', '2', '3' ]
}

 % node es6.mjs --foo 1 2 3
{
  args: { foo: true },
  values: { foo: [ undefined ] },
  positionals: [ '1', '2', '3' ]
}

Just spotted node -p in a comment. I had a feeling I was missing another special mode!
https://github.com/nodejs/node/pull/35015#discussion_r491625849

node -pe is critical

Added -p and --print. e.g.
% node --print 'require (".").parseArgs()' first second
{ args: {}, values: {}, positionals: [ 'first', 'second' ] }

Added tests, refactored code to be an explicit placeholder for process.mainArgs, describe Election as an example rather than as intended for inclusion.


JVM Crash when calling dispose() on an OrthogonalTiledMapRenderer

Please ensure you have given all the following requested information in your report.
Issue details
When I try and close my game using the following code:
 @Override         public boolean keyDown(int keycode) {             if (keycode == Input.Keys.ESCAPE) {                 GameScreen.this.dispose();                 Gdx.app.exit();             } return false; }
I get the following error:
`#
#  A fatal error has been detected by the Java Runtime Environment
# SIGSEGV (0xb) at pc=0x00007fdffccb434d, pid=1606, tid=0x00007fdfbf6fd700
#
# JRE version: OpenJDK Runtime Environment (8.0_112-b06) (build 1.8.0_112-release-b06)
# Java VM: OpenJDK 64-Bit Server VM (25.112-b06 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libc.so.6+0x7c34d]
Process finished with exit code 134 (interrupted by signal 6: SIGABRT)`
This does not happen if I simply close the game window and, from commenting out lines of code in the various dispose() methods, appears to be a result of a call to dispose() on OrthogonalTiledMapRenderer.
I have tried multiple JVMs including the one built in to Android Studio (openjdk 8), Openjdk8 - the latest version and the Oracle 8 jdk.  It appears on all of them - suggesting that it isn't a jvm bug.
Reproduction steps/code
It appears to happen if you call dispose() on an OrthogonalTiledMapRenderer - although it presumably requires a similar system to mine.
Version of LibGDX and/or relevant dependencies
1.9.6
Stacktrace
Provided above.  I tried to get it to create an error log, but failed.
Please select the affected platforms

[ ] Android
[ ] iOS (robovm)
[ ] iOS (MOE)
[ ] HTML/GWT
[ ] Windows
[X] Linux
[ ] MacOS

You are probably disposing twice as Gdx.app.exit() will close the app and propagate exit calls to the application listeners.  If you are still having the issue, please reopen with steps to reproduce and full compilable example code as requested by the issue template.

I'm confident I'm not calling dispose() twice as I have log messages in all the relevant dispose methods and they only get logged when I call them explicitly as outlined above.
That said, I don't have any more details on how to reproduce it than I've given - I can't even reproduce it in another project, so I suppose I'll have to leave this closed and figure something else out.

Full jvm crash log would also help.

and I've spent ages trying to generate one, but it never seems to work.  I've added
-XX:ErrorFile=/home/paul/hs_err_pid<pid>.log
to the org.gradle.jvmargs in gradle.properties, but that doesn't appear to make any difference...

I have googled the last line of the error message:

Process finished with exit code 134 (interrupted by signal 6: SIGABRT)`

and was able to find this: https://groups.google.com/d/msg/comp.lang.java.machine/OibTSkLJ-bY/7Gi-nsMgyZwJ
which says:

Signal number 6 is probably SIGABRT, which most often means
that some piece of code in the process deliberately called the libc abort()
function, e.g. many implementations of the assert() macro.
Does your application contain any native code (accessed through JNI) that
might use assert(), abort() or SIGABRT?  If not, then perhaps you're
tickling an assertion failure (i.e. bug) somewhere in the JDK's native code.

I'm not calling any native code, but, obviously, LWJGL does - so, perhaps, it's a bug there.

Hi, yes LibGDX is made of native and java code so it's usual to have that kind of error when something wrong happens in native code.
Anyway, your problem seams to be related to a "dispose twice". When you call dispose on the renderer, it just dispose its own batch. Maybe this batch is already disposed. Do you use it's own batch somewhere else in your code ? do you override/extends the renderer in some way ?
To not flood issue tracker, let's continue this subject on libGDX forum since it seams to be a bug in your code.


Pick 3563 into release v1.33

Description
Cherry-pick: #3563

For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.14 out of 15 committers have signed the CLA.:white_check_mark: electricjesus:white_check_mark: asincu:white_check_mark: Josh-Tigera:white_check_mark: bartolini:white_check_mark: danudey:white_check_mark: Behnam-Shobiri:white_check_mark: tmjd:white_check_mark: dimitri-nicolo:white_check_mark: nelljerram:white_check_mark: sridhartigera:white_check_mark: caseydavenport:white_check_mark: rene-dekker:white_check_mark: mazdakn:white_check_mark: song-jiang:x: Mike StephenMike Stephen seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Page No Longer Available in Current Version of Business Central.

It appears that Production BOM is no longer accessible from the search box, or by expanding the "Role Explorer" page.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 116dcd57-f002-5963-71e6-da6db354ec07
Version Independent ID: 50141a0e-bc99-4f41-8838-e17611181f76
Content: How to Create Production BOMs - Business Central
Content Source: business-central/production-how-to-create-production-boms.md
Service: dynamics365-business-central
GitHub Login: @SorenGP
Microsoft Alias: edupont

Hello,
Thank you for your feedback. Since your question is not about the Help, we suggest that you contact technical support. For more information, see Report a Problem. Note that the availability of production BOMs may rely on your license type and/or your permissions.


[FEATURE] Add support for hi-res / medium images to image gallery

Is your feature request related to a problem? Please describe.
The issue is that as of now, the image can only be fetched in small/large, however, even when using plugin_dis, when we do store the images in hi-res in Salesforce, they are not renderer on the PDP.
Describe the solution you'd like
Either allow to directly ask for this size on ImageGallery and ProductView
Describe alternatives you've considered
Have something that make the function findImageGroupBy able to find images from other resolution using plugin_dis

Hi @Valpich
Thank you for reaching out to us. Your requests sounds totally valid, fortunately we are working on the ProductTile component in the upcoming sprints, I'll create a ticket for this work and try to get it on our board for you.
Ben

Great, thanks a lot 🙏


The AppConfig.plist is missing

Hello,
the file is missing in your project. Could you please provide it ?

Hey 👋🏼
You'll need to obtain a free secret key from here
Then you can add the file as below to the root 👍
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>secret</key>
	<string>_YOUR SECRET KEY_</string>
</dict>
</plist>

Thank a lot !


TypeError: Cannot read property 'removeChild' of null

Thanks for this project!
I'm seeing this error when I navigate away from a page that makes use of ScriptTag:
TypeError: Cannot read property 'removeChild' of null

Looks like it's coming from the removeNode method here.
Pretty new to React so I may be doing something wrong.
Thanks!

Either you're doing something wrong, or your using new version of React that is causing problems (the React API is constantly evolving). The tests are passing, but not using the latest version of React.
Without your code to look at I can't be of any more help. You can open a new issue if you want to post some code, be sure to explain if the error is happening on the client or server.
Alternatively, fork this repo then update the React version and run the tests to see if its a React version problem.


Release v0.4.0 checklist

[x] Remove dev0 from the version in __init__.py __version__

[x] Make a release commit: git commit -m 'RLS: v0.2.0'

[x] Push the RLS commit git push upstream master

[x] Make a GitHub release

[x] Call the release the current version, e.g. v0.2.0 and pin it to master
[x] This will trigger this github action job. Ensure that it completes in the actions tab
After a few minutes, confirm that the PyPI version is updated
[x] If it's a minor/major versoin bump, add some simple release notes.
If you wish, use [github-activity to generate a changelog](https://github.com/choldgraf/github-activity, eg github-activity pandas-dev/pydata-sphinx-theme --since v0.2.2 --until v0.3.0).

[x] Bump the __init__.py __version__ and add dev0 to it. e.g.: v0.2.1dev0.

Closes #238

https://github.com/pandas-dev/pydata-sphinx-theme/releases/tag/v0.4.0


postcss Unocss inoperative

import esbuild from 'esbuild';
import { sassPlugin } from 'esbuild-sass-plugin';
import postcss from 'postcss';
import postcssUnocss from '@unocss/postcss';
sassPlugin({
async transform(source) {
const { css } = await postcss([
...postcssPlugins,
postcssUnocss({
content: ['src/**/*.{js,ts,jsx,tsx,vue}'],
}),
]).process(source);
return css;
},
}),
// unocss Not transferred correctly
@unocss;.qt-button-group{width:100%;background-color:#fff}

I am sorry but I can't look into 3rd party postcss plugin issues... unless, have you checked what is returned in css ?
just a console log before the return css is enough to see whether your call to postcss yields the results you expect.
I guess if there's an issue is with the call to post css...in any case this is beyond the scope of this plugin


[TIMEBOX] Figure out how we are building the UI

Find a framework to build the UI from currently it is using Next.js but look around and see if there are other things we can use to refresh and boostrap the app.

We are using nextjs

Boo


Interface updates

This issue is a log of the interface updates which will be made between version 0.1 -> 0.2.

[ ] .data -> .values to obtain underlying array data
[ ] object arrays -> tuple of strings for PdgArray.name attribute
[ ] scrap the .from_numpy classmethods, automatically handle conversions behind the scenes

Duplicate #67 supersedes this, closing.


Feat/internal/server/error tests

Ticket Link

Related Links

Description

Steps to Reproduce / Test

Request

Response

Codecov Report

Merging #68 (b4aea8d) into master (b04e02d) will increase coverage by 6.00%.
The diff coverage is 87.50%.

:exclamation: Current head b4aea8d differs from pull request most recent head 06a737d. Consider uploading reports for the commit 06a737d to get more accurate results

@@            Coverage Diff             @@
##           master      #68      +/-   ##
==========================================
+ Coverage   66.37%   72.37%   +6.00%
==========================================
  Files          19       19
  Lines         675      666       -9
==========================================
+ Hits          448      482      +34
+ Misses        206      159      -47
- Partials       21       25       +4

Impacted Files
Coverage Δ

internal/server/error.go
79.06% <87.50%> (+79.06%)
: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 b04e02d...06a737d. Read the comment docs.


WIP: Sync

Allow sync between nodes.

[x] save log entries to IPFS
[x] broadcast head
[x] listen to remote head broadcasts
[x] merge remote logs

Addresses #1

What's blocking this from moving forward / what is there still to do? I could see this project pairing really nicely with PouchDB.

I presumed it was the case that PouchDB would work with anything that implemented the abstract-leveldown interface, and thus were this to entirely do so things would just magically work. It’s not clear what additionally if anything would need to be done after the interface is implemented.
IMO IPFS backed DBs could be incredibly useful for making offline-capable apps that sync user data between web/desktop/mobile/backup. Much more attractive alternative to the CouchDB one user:one db concept.
I think there is also work being done to do a PouchDB OrbitDB adapter, but I think that is also super WIP status.

PouchDB doesn't do syncing at the level-down layer though. PouchDB is using level as the storage abstraction, it maps a syncable data model on top of that.
If you try to do syncing at the level layer with this you're asking for conflicts if both peers are accepting writes. This would work fine for read-only replicas but BadThings™ will happen if you're writing to two databases on top of this that have their own syncing semantics.

Much more attractive alternative to the CouchDB one user:one db concept.

Totally agree, that's one of the reasons I'm working in the IPFS/IPLD space instead of the Couch space nowadays :)
But, the CouchDB repo model is critical to how it does replication. There's work happening in CouchDB 3.0 to create "view based sync points" but it's still problematic because you have to know the data profile you want to sync for each user/device beforehand.
The nice thing about the IPLD data model is that you have a merkle graph and can pull whatever you need out of it dynamically and re-sync any parts of that graph in the future against another root node. If you start trying to map the Document/Repo model on top of this, and then start syncing it around with PouchDB, you'll lose that dynamic syncing profile.
In case you're worried I don't know what I'm talking about, I added CommonJS modules to CouchDB, I started the PouchDB project, and I've written a CouchDB compatible datastore directly on top of LevelUp ;)

If you try to do syncing at the level layer with this you're asking for conflicts if both peers are accepting writes. This would work fine for read-only replicas but BadThings™ will happen if you're writing to two databases on top of this that have their own syncing semantics.

I can see how real-time syncing would be an issue. I was actually thinking about this to solve the use case of allowing a user to store arbitrary data, and then to sync up from another device later, such that there's only ever one device writing at a time. Basically a load+save model w/out proper real-time syncing capabilities that's really only suitable for single-user use.

The nice thing about the IPLD data model is that you have a merkle graph and can pull whatever you need out of it dynamically and re-sync any parts of that graph in the future against another root node. If you start trying to map the Document/Repo model on top of this, and then start syncing it around with PouchDB, you'll lose that dynamic syncing profile.

I'm aware; IPFS/IPLD are remarkable, and I'm definitely eager to build w/ that data model. You have the right idea in working in that space! If you have any resources/projects that build off of this data model that you can reference, that would be greatly appreciated. Thanks!


feat(dropdown): support use of button element in dropdown options

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix(io): IOBase constructor do not update the fields id, name & description

The classes extending IOBase were already updating those fields (except SerialBase). SerialBase was the only class missing this change.
These changes allow the user to use multiple Serial interface at the same time. It was impossible before, as Pi4J would throw IOAlreadyExistsException.
This commit "moves" the fixes for the similar issues in the SPI interface. It also moves the similar code found in the dependency classes in the IOBase.
Ref: #244, #257
Closes: #257

You may change your PR to be ready for pulling


Bluetooth does not show any devices that I can connect to.

Describe the bug
When I go to my Bluetooth Settings on macOS and want to connect to my Bluetooth Headphones, I cannot do that, because they don't show up. But on my phone they do.
Not even one device shows up, but there should be at least 3.
The laptop shows on my phone's Bluetooth page, and I can connect to it with my phone and it shows up.
But the problem is I can't connect to any device from the macOS.
Expected behavior
New Bluetooth devices show up in macOS Settings.
Screenshots

macOS Info:

OS: Big Sur
Version 11.5.2
Laptop Model: T450

Thanks for advice!

Hello,
I'm running with the same "problem" using the Big Sur.
if you try to disable the wifi, you will be able to find bluetooth devices.
I'm using the "Magic Keyboard" right now, using the T450 like a Mac mini.
But, only works with the wifi turned off.
Regards,

Thanks for your response, it works!
I consider this issue as closed.
sob., 6 lis 2021, 21:46 użytkownik Lucas Oliveira @.***>
napisał:

Hello,
I'm running with the same "problem" using the Big Sur.
if you try to disable the wifi, you will be able to find bluetooth devices.
I'm using the "Magic Keyboard" right now, using the T450 like a Mac mini.
But, only works with the wifi turned off.
Regards,
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/racka98/Lenovo-Thinkpad-T450-T450s-Hackintosh-Guide-Opencore/issues/69#issuecomment-962507690,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALBGZP5CQUKM4HFJKUE2QSDUKWHZXANCNFSM5HP6HTJQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Add style choices as option or config file

I find the dot chart is sometimes better for analysing issues- its a bit like an x-ray view when there are outliers; where a line graph will draw a line to something and can give a wrong impression of peaks a few stray dots is often clearer and better context. Which leads to the path of choosing chart styles. Whether this can be passed as a config file so someone can set up their favourite colour schemes etc or whether we just have a few basic switches we can chat about.

agreed. we have the infrastructure layed out for putting options in the config file. following the example of the output graph size should be pretty straightforward

6f80aaf
We can discuss adding this as command line option as well if the config file way is not sufficient.
I would just pass a config with '--config dots.yml' where i have that setup ...


nf4_detach missing args error when calling fully_shard on latest nightly

Hi, I am seeing the error TypeError: nf4_detach() missing 1 required positional argument: 'args' when running torchtune's QLoRA FSDP2 recipe on the latest ao nightlies. Full stack trace
Repro:
tune download meta-llama/Llama-2-7b-hf --output-dir /tmp/Llama-2-7b-hf --hf-token <HF_TOKEN>
tune run --nnodes 1 --nproc_per_node 4 lora_finetune_fsdp2 --config llama2/7B_qlora enable_activation_checkpointing=False

Looks like it's happening when we try to call fully_shard on a TransformerDecoderLayer. When I downgrade to e.g. the 6/8 nightly things seem to work.

This might have been caused by #360 - cc @jerryzh168
@weifengpy did we ever end up merging some sanity tests in ao to detect these kinds of breakages cause relying purely on ao for testing seems less than ideal?

good catch! @ebsmothers
@msaroufim you are right. I will also check FSDP e2e in TorchAO just like how we do it in TorchTune

This might have been caused by #360 - cc @jerryzh168 @weifengpy did we ever end up merging some sanity tests in ao to detect these kinds of breakages cause relying purely on tune for testing seems less than ideal?

@weifengpy can we close this issue now?

@weifengpy can we close this issue now?

Yes, we can close it as it's landed


Cannot import 'detrex._C', therefore 'MultiScaleDeformableAttention' is not available. detrex is not compiled successfully, please build following the instructions!

I followed the installation procedure. And even performed export CUDA_HOME=path/to/cuda as mentioned for this particular error and still im getting the same error.
Please find the complete runtime log below for installing the build,
No CUDA runtime is found, using CUDA_HOME='/share/apps1/cuda-11.8'
Building wheel detrex-0.3.0
running install
/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!
    ********************************************************************************
    Please avoid running ``setup.py`` directly.
    Instead, use pypa/build, pypa/installer or other
    standards-based tools.

    See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
    ********************************************************************************

!!
self.initialize_options()
/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/setuptools/_distutils/cmd.py:66: EasyInstallDeprecationWarning: easy_install command is deprecated.
!!
    ********************************************************************************
    Please avoid running ``setup.py`` and ``easy_install``.
    Instead, use pypa/build, pypa/installer or other
    standards-based tools.

    See https://github.com/pypa/setuptools/issues/917 for details.
    ********************************************************************************

!!
self.initialize_options()
running bdist_egg
running egg_info
writing detrex.egg-info/PKG-INFO
writing dependency_links to detrex.egg-info/dependency_links.txt
writing requirements to detrex.egg-info/requires.txt
writing top-level names to detrex.egg-info/top_level.txt
reading manifest file 'detrex.egg-info/SOURCES.txt'
adding license file 'LICENSE'
writing manifest file 'detrex.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
creating build
creating build/lib
creating build/lib/detrex
copying detrex/version.py -> build/lib/detrex
copying detrex/init.py -> build/lib/detrex
creating build/lib/demo
copying demo/predictors.py -> build/lib/demo
copying demo/demo.py -> build/lib/demo
copying demo/init.py -> build/lib/demo
copying demo/mot_demo.py -> build/lib/demo
copying demo/mot_predictors.py -> build/lib/demo
creating build/lib/tools
copying tools/visualize_json_results.py -> build/lib/tools
copying tools/benchmark.py -> build/lib/tools
copying tools/init.py -> build/lib/tools
copying tools/analyze_model.py -> build/lib/tools
copying tools/hydra_train_net.py -> build/lib/tools
copying tools/visualize_data.py -> build/lib/tools
copying tools/train_net.py -> build/lib/tools
creating build/lib/detrex/data
copying detrex/data/detr_dataset_mapper.py -> build/lib/detrex/data
copying detrex/data/init.py -> build/lib/detrex/data
creating build/lib/detrex/utils
copying detrex/utils/misc.py -> build/lib/detrex/utils
copying detrex/utils/init.py -> build/lib/detrex/utils
copying detrex/utils/events.py -> build/lib/detrex/utils
copying detrex/utils/dist.py -> build/lib/detrex/utils
creating build/lib/detrex/modeling
copying detrex/modeling/init.py -> build/lib/detrex/modeling
copying detrex/modeling/ema.py -> build/lib/detrex/modeling
creating build/lib/detrex/checkpoint
copying detrex/checkpoint/c2_model_loading.py -> build/lib/detrex/checkpoint
copying detrex/checkpoint/detection_checkpoint.py -> build/lib/detrex/checkpoint
copying detrex/checkpoint/init.py -> build/lib/detrex/checkpoint
creating build/lib/detrex/layers
copying detrex/layers/conv.py -> build/lib/detrex/layers
copying detrex/layers/multi_scale_deform_attn.py -> build/lib/detrex/layers
copying detrex/layers/transformer.py -> build/lib/detrex/layers
copying detrex/layers/dcn_v3.py -> build/lib/detrex/layers
copying detrex/layers/init.py -> build/lib/detrex/layers
copying detrex/layers/box_ops.py -> build/lib/detrex/layers
copying detrex/layers/attention.py -> build/lib/detrex/layers
copying detrex/layers/shape_spec.py -> build/lib/detrex/layers
copying detrex/layers/denoising.py -> build/lib/detrex/layers
copying detrex/layers/position_embedding.py -> build/lib/detrex/layers
copying detrex/layers/mlp.py -> build/lib/detrex/layers
copying detrex/layers/layer_norm.py -> build/lib/detrex/layers
creating build/lib/detrex/config
copying detrex/config/config.py -> build/lib/detrex/config
copying detrex/config/init.py -> build/lib/detrex/config
creating build/lib/detrex/data/dataset_mappers
copying detrex/data/dataset_mappers/mask_former_semantic_dataset_mapper.py -> build/lib/detrex/data/dataset_mappers
copying detrex/data/dataset_mappers/mask_former_instance_dataset_mapper.py -> build/lib/detrex/data/dataset_mappers
copying detrex/data/dataset_mappers/mask_former_panoptic_dataset_mapper.py -> build/lib/detrex/data/dataset_mappers
copying detrex/data/dataset_mappers/init.py -> build/lib/detrex/data/dataset_mappers
copying detrex/data/dataset_mappers/coco_panoptic_new_baseline_dataset_mapper.py -> build/lib/detrex/data/dataset_mappers
copying detrex/data/dataset_mappers/coco_instance_new_baseline_dataset_mapper.py -> build/lib/detrex/data/dataset_mappers
creating build/lib/detrex/data/transforms
copying detrex/data/transforms/init.py -> build/lib/detrex/data/transforms
copying detrex/data/transforms/color_augmentation.py -> build/lib/detrex/data/transforms
creating build/lib/detrex/data/datasets
copying detrex/data/datasets/register_ade20k_instance.py -> build/lib/detrex/data/datasets
copying detrex/data/datasets/register_mapillary_vistas.py -> build/lib/detrex/data/datasets
copying detrex/data/datasets/register_coco_panoptic_annos_semseg.py -> build/lib/detrex/data/datasets
copying detrex/data/datasets/register_coco_stuff_10k.py -> build/lib/detrex/data/datasets
copying detrex/data/datasets/init.py -> build/lib/detrex/data/datasets
copying detrex/data/datasets/register_mapillary_vistas_panoptic.py -> build/lib/detrex/data/datasets
copying detrex/data/datasets/register_ade20k_panoptic.py -> build/lib/detrex/data/datasets
copying detrex/data/datasets/register_ade20k_full.py -> build/lib/detrex/data/datasets
creating build/lib/detrex/modeling/criterion
copying detrex/modeling/criterion/criterion.py -> build/lib/detrex/modeling/criterion
copying detrex/modeling/criterion/init.py -> build/lib/detrex/modeling/criterion
copying detrex/modeling/criterion/base_criterion.py -> build/lib/detrex/modeling/criterion
creating build/lib/detrex/modeling/matcher
copying detrex/modeling/matcher/matcher.py -> build/lib/detrex/modeling/matcher
copying detrex/modeling/matcher/modified_matcher.py -> build/lib/detrex/modeling/matcher
copying detrex/modeling/matcher/init.py -> build/lib/detrex/modeling/matcher
copying detrex/modeling/matcher/match_cost.py -> build/lib/detrex/modeling/matcher
creating build/lib/detrex/modeling/losses
copying detrex/modeling/losses/init.py -> build/lib/detrex/modeling/losses
copying detrex/modeling/losses/smooth_l1_loss.py -> build/lib/detrex/modeling/losses
copying detrex/modeling/losses/utils.py -> build/lib/detrex/modeling/losses
copying detrex/modeling/losses/dice_loss.py -> build/lib/detrex/modeling/losses
copying detrex/modeling/losses/cross_entropy_loss.py -> build/lib/detrex/modeling/losses
copying detrex/modeling/losses/focal_loss.py -> build/lib/detrex/modeling/losses
copying detrex/modeling/losses/giou_loss.py -> build/lib/detrex/modeling/losses
creating build/lib/detrex/modeling/neck
copying detrex/modeling/neck/init.py -> build/lib/detrex/modeling/neck
copying detrex/modeling/neck/channel_mapper.py -> build/lib/detrex/modeling/neck
creating build/lib/detrex/modeling/backbone
copying detrex/modeling/backbone/torchvision_backbone.py -> build/lib/detrex/modeling/backbone
copying detrex/modeling/backbone/resnet.py -> build/lib/detrex/modeling/backbone
copying detrex/modeling/backbone/eva.py -> build/lib/detrex/modeling/backbone
copying detrex/modeling/backbone/eva_02.py -> build/lib/detrex/modeling/backbone
copying detrex/modeling/backbone/focalnet.py -> build/lib/detrex/modeling/backbone
copying detrex/modeling/backbone/utils.py -> build/lib/detrex/modeling/backbone
copying detrex/modeling/backbone/convnext.py -> build/lib/detrex/modeling/backbone
copying detrex/modeling/backbone/timm_backbone.py -> build/lib/detrex/modeling/backbone
copying detrex/modeling/backbone/init.py -> build/lib/detrex/modeling/backbone
copying detrex/modeling/backbone/internimage.py -> build/lib/detrex/modeling/backbone
copying detrex/modeling/backbone/eva_02_utils.py -> build/lib/detrex/modeling/backbone
copying detrex/modeling/backbone/torchvision_resnet.py -> build/lib/detrex/modeling/backbone
creating build/lib/detrex/config/configs
creating build/lib/detrex/config/configs/common
copying detrex/config/configs/common/train.py -> build/lib/detrex/config/configs/common
copying detrex/config/configs/common/coco_schedule.py -> build/lib/detrex/config/configs/common
copying detrex/config/configs/common/optim.py -> build/lib/detrex/config/configs/common
copying detrex/config/configs/common/common_schedule.py -> build/lib/detrex/config/configs/common
creating build/lib/detrex/config/configs/common/data
copying detrex/config/configs/common/data/coco_detr.py -> build/lib/detrex/config/configs/common/data
copying detrex/config/configs/common/data/constants.py -> build/lib/detrex/config/configs/common/data
copying detrex/config/configs/common/data/coco.py -> build/lib/detrex/config/configs/common/data
copying detrex/config/configs/common/data/custom.py -> build/lib/detrex/config/configs/common/data
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/demo
copying build/lib/demo/demo.py -> build/bdist.linux-x86_64/egg/demo
copying build/lib/demo/mot_predictors.py -> build/bdist.linux-x86_64/egg/demo
copying build/lib/demo/predictors.py -> build/bdist.linux-x86_64/egg/demo
copying build/lib/demo/init.py -> build/bdist.linux-x86_64/egg/demo
copying build/lib/demo/mot_demo.py -> build/bdist.linux-x86_64/egg/demo
creating build/bdist.linux-x86_64/egg/detrex
creating build/bdist.linux-x86_64/egg/detrex/utils
copying build/lib/detrex/utils/dist.py -> build/bdist.linux-x86_64/egg/detrex/utils
copying build/lib/detrex/utils/events.py -> build/bdist.linux-x86_64/egg/detrex/utils
copying build/lib/detrex/utils/init.py -> build/bdist.linux-x86_64/egg/detrex/utils
copying build/lib/detrex/utils/misc.py -> build/bdist.linux-x86_64/egg/detrex/utils
creating build/bdist.linux-x86_64/egg/detrex/data
creating build/bdist.linux-x86_64/egg/detrex/data/dataset_mappers
copying build/lib/detrex/data/dataset_mappers/coco_instance_new_baseline_dataset_mapper.py -> build/bdist.linux-x86_64/egg/detrex/data/dataset_mappers
copying build/lib/detrex/data/dataset_mappers/init.py -> build/bdist.linux-x86_64/egg/detrex/data/dataset_mappers
copying build/lib/detrex/data/dataset_mappers/coco_panoptic_new_baseline_dataset_mapper.py -> build/bdist.linux-x86_64/egg/detrex/data/dataset_mappers
copying build/lib/detrex/data/dataset_mappers/mask_former_semantic_dataset_mapper.py -> build/bdist.linux-x86_64/egg/detrex/data/dataset_mappers
copying build/lib/detrex/data/dataset_mappers/mask_former_instance_dataset_mapper.py -> build/bdist.linux-x86_64/egg/detrex/data/dataset_mappers
copying build/lib/detrex/data/dataset_mappers/mask_former_panoptic_dataset_mapper.py -> build/bdist.linux-x86_64/egg/detrex/data/dataset_mappers
creating build/bdist.linux-x86_64/egg/detrex/data/transforms
copying build/lib/detrex/data/transforms/color_augmentation.py -> build/bdist.linux-x86_64/egg/detrex/data/transforms
copying build/lib/detrex/data/transforms/init.py -> build/bdist.linux-x86_64/egg/detrex/data/transforms
copying build/lib/detrex/data/init.py -> build/bdist.linux-x86_64/egg/detrex/data
copying build/lib/detrex/data/detr_dataset_mapper.py -> build/bdist.linux-x86_64/egg/detrex/data
creating build/bdist.linux-x86_64/egg/detrex/data/datasets
copying build/lib/detrex/data/datasets/register_coco_stuff_10k.py -> build/bdist.linux-x86_64/egg/detrex/data/datasets
copying build/lib/detrex/data/datasets/register_coco_panoptic_annos_semseg.py -> build/bdist.linux-x86_64/egg/detrex/data/datasets
copying build/lib/detrex/data/datasets/register_ade20k_instance.py -> build/bdist.linux-x86_64/egg/detrex/data/datasets
copying build/lib/detrex/data/datasets/register_mapillary_vistas.py -> build/bdist.linux-x86_64/egg/detrex/data/datasets
copying build/lib/detrex/data/datasets/register_mapillary_vistas_panoptic.py -> build/bdist.linux-x86_64/egg/detrex/data/datasets
copying build/lib/detrex/data/datasets/init.py -> build/bdist.linux-x86_64/egg/detrex/data/datasets
copying build/lib/detrex/data/datasets/register_ade20k_panoptic.py -> build/bdist.linux-x86_64/egg/detrex/data/datasets
copying build/lib/detrex/data/datasets/register_ade20k_full.py -> build/bdist.linux-x86_64/egg/detrex/data/datasets
copying build/lib/detrex/init.py -> build/bdist.linux-x86_64/egg/detrex
creating build/bdist.linux-x86_64/egg/detrex/layers
copying build/lib/detrex/layers/layer_norm.py -> build/bdist.linux-x86_64/egg/detrex/layers
copying build/lib/detrex/layers/mlp.py -> build/bdist.linux-x86_64/egg/detrex/layers
copying build/lib/detrex/layers/attention.py -> build/bdist.linux-x86_64/egg/detrex/layers
copying build/lib/detrex/layers/denoising.py -> build/bdist.linux-x86_64/egg/detrex/layers
copying build/lib/detrex/layers/shape_spec.py -> build/bdist.linux-x86_64/egg/detrex/layers
copying build/lib/detrex/layers/position_embedding.py -> build/bdist.linux-x86_64/egg/detrex/layers
copying build/lib/detrex/layers/multi_scale_deform_attn.py -> build/bdist.linux-x86_64/egg/detrex/layers
copying build/lib/detrex/layers/box_ops.py -> build/bdist.linux-x86_64/egg/detrex/layers
copying build/lib/detrex/layers/transformer.py -> build/bdist.linux-x86_64/egg/detrex/layers
copying build/lib/detrex/layers/conv.py -> build/bdist.linux-x86_64/egg/detrex/layers
copying build/lib/detrex/layers/dcn_v3.py -> build/bdist.linux-x86_64/egg/detrex/layers
copying build/lib/detrex/layers/init.py -> build/bdist.linux-x86_64/egg/detrex/layers
creating build/bdist.linux-x86_64/egg/detrex/config
creating build/bdist.linux-x86_64/egg/detrex/config/configs
creating build/bdist.linux-x86_64/egg/detrex/config/configs/common
creating build/bdist.linux-x86_64/egg/detrex/config/configs/common/data
copying build/lib/detrex/config/configs/common/data/constants.py -> build/bdist.linux-x86_64/egg/detrex/config/configs/common/data
copying build/lib/detrex/config/configs/common/data/coco_detr.py -> build/bdist.linux-x86_64/egg/detrex/config/configs/common/data
copying build/lib/detrex/config/configs/common/data/coco.py -> build/bdist.linux-x86_64/egg/detrex/config/configs/common/data
copying build/lib/detrex/config/configs/common/data/custom.py -> build/bdist.linux-x86_64/egg/detrex/config/configs/common/data
copying build/lib/detrex/config/configs/common/optim.py -> build/bdist.linux-x86_64/egg/detrex/config/configs/common
copying build/lib/detrex/config/configs/common/common_schedule.py -> build/bdist.linux-x86_64/egg/detrex/config/configs/common
copying build/lib/detrex/config/configs/common/coco_schedule.py -> build/bdist.linux-x86_64/egg/detrex/config/configs/common
copying build/lib/detrex/config/configs/common/train.py -> build/bdist.linux-x86_64/egg/detrex/config/configs/common
copying build/lib/detrex/config/init.py -> build/bdist.linux-x86_64/egg/detrex/config
copying build/lib/detrex/config/config.py -> build/bdist.linux-x86_64/egg/detrex/config
creating build/bdist.linux-x86_64/egg/detrex/checkpoint
copying build/lib/detrex/checkpoint/c2_model_loading.py -> build/bdist.linux-x86_64/egg/detrex/checkpoint
copying build/lib/detrex/checkpoint/detection_checkpoint.py -> build/bdist.linux-x86_64/egg/detrex/checkpoint
copying build/lib/detrex/checkpoint/init.py -> build/bdist.linux-x86_64/egg/detrex/checkpoint
creating build/bdist.linux-x86_64/egg/detrex/modeling
creating build/bdist.linux-x86_64/egg/detrex/modeling/neck
copying build/lib/detrex/modeling/neck/init.py -> build/bdist.linux-x86_64/egg/detrex/modeling/neck
copying build/lib/detrex/modeling/neck/channel_mapper.py -> build/bdist.linux-x86_64/egg/detrex/modeling/neck
creating build/bdist.linux-x86_64/egg/detrex/modeling/matcher
copying build/lib/detrex/modeling/matcher/match_cost.py -> build/bdist.linux-x86_64/egg/detrex/modeling/matcher
copying build/lib/detrex/modeling/matcher/modified_matcher.py -> build/bdist.linux-x86_64/egg/detrex/modeling/matcher
copying build/lib/detrex/modeling/matcher/matcher.py -> build/bdist.linux-x86_64/egg/detrex/modeling/matcher
copying build/lib/detrex/modeling/matcher/init.py -> build/bdist.linux-x86_64/egg/detrex/modeling/matcher
creating build/bdist.linux-x86_64/egg/detrex/modeling/backbone
copying build/lib/detrex/modeling/backbone/eva_02.py -> build/bdist.linux-x86_64/egg/detrex/modeling/backbone
copying build/lib/detrex/modeling/backbone/utils.py -> build/bdist.linux-x86_64/egg/detrex/modeling/backbone
copying build/lib/detrex/modeling/backbone/init.py -> build/bdist.linux-x86_64/egg/detrex/modeling/backbone
copying build/lib/detrex/modeling/backbone/convnext.py -> build/bdist.linux-x86_64/egg/detrex/modeling/backbone
copying build/lib/detrex/modeling/backbone/torchvision_resnet.py -> build/bdist.linux-x86_64/egg/detrex/modeling/backbone
copying build/lib/detrex/modeling/backbone/resnet.py -> build/bdist.linux-x86_64/egg/detrex/modeling/backbone
copying build/lib/detrex/modeling/backbone/internimage.py -> build/bdist.linux-x86_64/egg/detrex/modeling/backbone
copying build/lib/detrex/modeling/backbone/eva_02_utils.py -> build/bdist.linux-x86_64/egg/detrex/modeling/backbone
copying build/lib/detrex/modeling/backbone/timm_backbone.py -> build/bdist.linux-x86_64/egg/detrex/modeling/backbone
copying build/lib/detrex/modeling/backbone/focalnet.py -> build/bdist.linux-x86_64/egg/detrex/modeling/backbone
copying build/lib/detrex/modeling/backbone/eva.py -> build/bdist.linux-x86_64/egg/detrex/modeling/backbone
copying build/lib/detrex/modeling/backbone/torchvision_backbone.py -> build/bdist.linux-x86_64/egg/detrex/modeling/backbone
creating build/bdist.linux-x86_64/egg/detrex/modeling/criterion
copying build/lib/detrex/modeling/criterion/criterion.py -> build/bdist.linux-x86_64/egg/detrex/modeling/criterion
copying build/lib/detrex/modeling/criterion/init.py -> build/bdist.linux-x86_64/egg/detrex/modeling/criterion
copying build/lib/detrex/modeling/criterion/base_criterion.py -> build/bdist.linux-x86_64/egg/detrex/modeling/criterion
copying build/lib/detrex/modeling/init.py -> build/bdist.linux-x86_64/egg/detrex/modeling
copying build/lib/detrex/modeling/ema.py -> build/bdist.linux-x86_64/egg/detrex/modeling
creating build/bdist.linux-x86_64/egg/detrex/modeling/losses
copying build/lib/detrex/modeling/losses/smooth_l1_loss.py -> build/bdist.linux-x86_64/egg/detrex/modeling/losses
copying build/lib/detrex/modeling/losses/cross_entropy_loss.py -> build/bdist.linux-x86_64/egg/detrex/modeling/losses
copying build/lib/detrex/modeling/losses/init.py -> build/bdist.linux-x86_64/egg/detrex/modeling/losses
copying build/lib/detrex/modeling/losses/focal_loss.py -> build/bdist.linux-x86_64/egg/detrex/modeling/losses
copying build/lib/detrex/modeling/losses/utils.py -> build/bdist.linux-x86_64/egg/detrex/modeling/losses
copying build/lib/detrex/modeling/losses/giou_loss.py -> build/bdist.linux-x86_64/egg/detrex/modeling/losses
copying build/lib/detrex/modeling/losses/dice_loss.py -> build/bdist.linux-x86_64/egg/detrex/modeling/losses
copying build/lib/detrex/version.py -> build/bdist.linux-x86_64/egg/detrex
creating build/bdist.linux-x86_64/egg/tools
copying build/lib/tools/visualize_json_results.py -> build/bdist.linux-x86_64/egg/tools
copying build/lib/tools/train_net.py -> build/bdist.linux-x86_64/egg/tools
copying build/lib/tools/visualize_data.py -> build/bdist.linux-x86_64/egg/tools
copying build/lib/tools/benchmark.py -> build/bdist.linux-x86_64/egg/tools
copying build/lib/tools/hydra_train_net.py -> build/bdist.linux-x86_64/egg/tools
copying build/lib/tools/analyze_model.py -> build/bdist.linux-x86_64/egg/tools
copying build/lib/tools/init.py -> build/bdist.linux-x86_64/egg/tools
byte-compiling build/bdist.linux-x86_64/egg/demo/demo.py to demo.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/demo/mot_predictors.py to mot_predictors.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/demo/predictors.py to predictors.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/demo/init.py to init.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/demo/mot_demo.py to mot_demo.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/utils/dist.py to dist.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/utils/events.py to events.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/utils/init.py to init.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/utils/misc.py to misc.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/dataset_mappers/coco_instance_new_baseline_dataset_mapper.py to coco_instance_new_baseline_dataset_mapper.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/dataset_mappers/init.py to init.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/dataset_mappers/coco_panoptic_new_baseline_dataset_mapper.py to coco_panoptic_new_baseline_dataset_mapper.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/dataset_mappers/mask_former_semantic_dataset_mapper.py to mask_former_semantic_dataset_mapper.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/dataset_mappers/mask_former_instance_dataset_mapper.py to mask_former_instance_dataset_mapper.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/dataset_mappers/mask_former_panoptic_dataset_mapper.py to mask_former_panoptic_dataset_mapper.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/transforms/color_augmentation.py to color_augmentation.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/transforms/init.py to init.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/init.py to init.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/detr_dataset_mapper.py to detr_dataset_mapper.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/datasets/register_coco_stuff_10k.py to register_coco_stuff_10k.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/datasets/register_coco_panoptic_annos_semseg.py to register_coco_panoptic_annos_semseg.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/datasets/register_ade20k_instance.py to register_ade20k_instance.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/datasets/register_mapillary_vistas.py to register_mapillary_vistas.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/datasets/register_mapillary_vistas_panoptic.py to register_mapillary_vistas_panoptic.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/datasets/init.py to init.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/datasets/register_ade20k_panoptic.py to register_ade20k_panoptic.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/data/datasets/register_ade20k_full.py to register_ade20k_full.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/init.py to init.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/layers/layer_norm.py to layer_norm.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/layers/mlp.py to mlp.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/layers/attention.py to attention.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/layers/denoising.py to denoising.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/layers/shape_spec.py to shape_spec.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/layers/position_embedding.py to position_embedding.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/layers/multi_scale_deform_attn.py to multi_scale_deform_attn.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/layers/box_ops.py to box_ops.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/layers/transformer.py to transformer.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/layers/conv.py to conv.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/layers/dcn_v3.py to dcn_v3.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/layers/init.py to init.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/config/configs/common/data/constants.py to constants.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/config/configs/common/data/coco_detr.py to coco_detr.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/config/configs/common/data/coco.py to coco.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/config/configs/common/data/custom.py to custom.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/config/configs/common/optim.py to optim.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/config/configs/common/common_schedule.py to common_schedule.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/config/configs/common/coco_schedule.py to coco_schedule.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/config/configs/common/train.py to train.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/config/init.py to init.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/config/config.py to config.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/checkpoint/c2_model_loading.py to c2_model_loading.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/checkpoint/detection_checkpoint.py to detection_checkpoint.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/checkpoint/init.py to init.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/neck/init.py to init.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/neck/channel_mapper.py to channel_mapper.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/matcher/match_cost.py to match_cost.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/matcher/modified_matcher.py to modified_matcher.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/matcher/matcher.py to matcher.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/matcher/init.py to init.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/backbone/eva_02.py to eva_02.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/backbone/utils.py to utils.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/backbone/init.py to init.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/backbone/convnext.py to convnext.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/backbone/torchvision_resnet.py to torchvision_resnet.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/backbone/resnet.py to resnet.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/backbone/internimage.py to internimage.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/backbone/eva_02_utils.py to eva_02_utils.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/backbone/timm_backbone.py to timm_backbone.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/backbone/focalnet.py to focalnet.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/backbone/eva.py to eva.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/backbone/torchvision_backbone.py to torchvision_backbone.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/criterion/criterion.py to criterion.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/criterion/init.py to init.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/criterion/base_criterion.py to base_criterion.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/init.py to init.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/ema.py to ema.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/losses/smooth_l1_loss.py to smooth_l1_loss.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/losses/cross_entropy_loss.py to cross_entropy_loss.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/losses/init.py to init.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/losses/focal_loss.py to focal_loss.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/losses/utils.py to utils.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/losses/giou_loss.py to giou_loss.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/modeling/losses/dice_loss.py to dice_loss.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/detrex/version.py to version.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/tools/visualize_json_results.py to visualize_json_results.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/tools/train_net.py to train_net.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/tools/visualize_data.py to visualize_data.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/tools/benchmark.py to benchmark.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/tools/hydra_train_net.py to hydra_train_net.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/tools/analyze_model.py to analyze_model.cpython-39.pyc
byte-compiling build/bdist.linux-x86_64/egg/tools/init.py to init.cpython-39.pyc
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying detrex.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying detrex.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying detrex.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying detrex.egg-info/requires.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying detrex.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
zip_safe flag not set; analyzing archive contents...
tools.pycache.hydra_train_net.cpython-39: module references file
tools.pycache.train_net.cpython-39: module references file
creating 'dist/detrex-0.3.0-py3.9.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing detrex-0.3.0-py3.9.egg
creating /home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/detrex-0.3.0-py3.9.egg
Extracting detrex-0.3.0-py3.9.egg to /home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages
Removing detrex 0.3.0 from easy-install.pth file
Adding detrex 0.3.0 to easy-install.pth file
detected new path '/home/mu480317/Object_Detectors/detrex'
Installed /home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/detrex-0.3.0-py3.9.egg
Processing dependencies for detrex==0.3.0
Traceback (most recent call last):
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/pkg_resources/init.py", line 3109, in _dep_map
return self.__dep_map
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/pkg_resources/init.py", line 2902, in getattr
raise AttributeError(attr)
AttributeError: _DistInfoDistribution__dep_map
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/requirements.py", line 35, in init
parsed = _parse_requirement(requirement_string)
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/_parser.py", line 64, in parse_requirement
return _parse_requirement(Tokenizer(source, rules=DEFAULT_RULES))
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/_parser.py", line 82, in _parse_requirement
url, specifier, marker = _parse_requirement_details(tokenizer)
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/_parser.py", line 120, in _parse_requirement_details
specifier = _parse_specifier(tokenizer)
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/_parser.py", line 216, in _parse_specifier
parsed_specifiers = _parse_version_many(tokenizer)
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/_parser.py", line 231, in _parse_version_many
tokenizer.raise_syntax_error(
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/_tokenizer.py", line 165, in raise_syntax_error
raise ParserSyntaxError(
pkg_resources.extern.packaging._tokenizer.ParserSyntaxError: .* suffix can only be used with == or != operators
PyYAML (>=5.1.*)
~~~~~~^
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/mu480317/Object_Detectors/detrex/setup.py", line 217, in
setup(
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/setuptools/init.py", line 107, in setup
return distutils.core.setup(*attrs)
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 185, in setup
return run_commands(dist)
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
dist.run_commands()
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
self.run_command(cmd)
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/setuptools/dist.py", line 1234, in run_command
super().run_command(command)
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
cmd_obj.run()
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/setuptools/command/install.py", line 80, in run
self.do_egg_install()
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/setuptools/command/install.py", line 137, in do_egg_install
cmd.run(show_deprecation=False)
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/setuptools/command/easy_install.py", line 416, in run
self.easy_install(spec, not self.no_deps)
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/setuptools/command/easy_install.py", line 658, in easy_install
return self.install_item(None, spec, tmpdir, deps, True)
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/setuptools/command/easy_install.py", line 705, in install_item
self.process_distribution(spec, dist, deps)
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/setuptools/command/easy_install.py", line 750, in process_distribution
distros = WorkingSet([]).resolve(
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/pkg_resources/init.py", line 834, in resolve
new_requirements = dist.requires(req.extras)[::-1]
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/pkg_resources/init.py", line 2822, in requires
dm = self._dep_map
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/pkg_resources/init.py", line 3111, in _dep_map
self.__dep_map = self._compute_dependencies()
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/pkg_resources/init.py", line 3121, in _compute_dependencies
reqs.extend(parse_requirements(req))
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/pkg_resources/init.py", line 3174, in init
super(Requirement, self).init(requirement_string)
File "/home/mu480317/.conda/envs/detrex/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/requirements.py", line 37, in init
raise InvalidRequirement(str(e)) from e
pkg_resources.extern.packaging.requirements.InvalidRequirement: . suffix can only be used with == or != operators
PyYAML (>=5.1.*)
~~~~~~^
My Environment :
Python 3.9
Cuda 11.8
env - detrex
Please help me solve this issue.

Hello! You can try:

Remove the build dir if you've already installed detrex (even if it is failed)
Export the CUDA_HOME environment settings by export CUDA_HOME=path/to/cuda
Reinstall detrex by cd detrex; pip install -e .


express server support

supporting express server so, that it is easier to use node-soap in an existing express server without affecting other routes.
It supports middleware for body parsing like body-parser as well.
Please see the tests included in commit.

Coverage increased (+0.2%) to 92.696% when pulling c4490ddeecad9549a2035890e3a86e0dff2d143c on prasunsultania:master into 59aa639fe9ccc2f20faab63de2fdff5ada433242 on vpulim:master.

Looks good to me.  I'd like @herom to weigh in as well.

@jsdevel / @herom Any update on this ? We want to use this feature in our ongoing project.

Coverage increased (+0.2%) to 92.692% when pulling 952c7a06c622205a8b542c47c3d0eceb5004d5c3 on prasunsultania:master into 59aa639fe9ccc2f20faab63de2fdff5ada433242 on vpulim:master.

@herom have made recommended changes. Please review.

Thanks a ton @prasunsultania - LGTM :+1:
One last thing: could you please open a PR and update our README.md so that we have it documented, that soap is able to handle an express server instance as well? :smile_cat:

I will open a separate PR after updating docs.


Add API calls to provide write buffer metrics

Somehow I forgot to expose the api calls in a previous PR. This fixes this.
Add the following api calls

/api/instance-buffered-write-metrics-raw/:seconds
/api/instance-buffered-write-metrics-aggregated/:seconds

[x] contributed code is using same conventions as original code
[x] code is formatted via gofmt (please avoid goimports)
[x] code is built via ./build.sh
[x] code is tested via go test ./go/...

I can't figure out the right way to push a missing commit I pushed to my tree to get it here so going to open a new pull. Need to figure out this workflow better.


duplicate key entry

I'm facing an issue where I have duplicate entries in my table with identical (composite) keys:
schema.cds
entity CardReceiverAllocation {
    key receiver_ID         : UUID;
    key card_ID             : Integer;
    key timestamp           : Timestamp default $now; // this column was added later on
        receiver            : Association to one Receiver
                                  on receiver.ID = receiver_ID;
        card                : Association to one Card
                                  on card.cardID = card_ID;
        depositStatus       : Association to one CardDepositStatus;
        creatingUserEmail   : String(64);
        isCurrentAllocation : Boolean default false;
}

entity Card {
    key cardID      : Integer;
        isLost      : Boolean default false;
        pickupSlot  : Association to one PickupSlot;
        receiverAllocations : Association to many CardReceiverAllocation on
            cardID = receiverAllocations.card_ID;
        // [...]
}

entity Receiver : cuid {
    firstName                : String(128);
    lastName                 : String(128);
    registrationDate         : Timestamp @cds.on.insert : $now;
    cardAllocations           : Association to many CardReceiverAllocation
                                   on  ID     = cardAllocations.receiver_ID;
    isBlocked                : Boolean default false;
    // [...]
}

aspect cuid {
    key ID : UUID;
}

The issue occurs in the CardReceiverAllocation table with the composite key of { receiver_ID, card_ID, timestamp } where the timestamp was added since multiple entries with same receiver and card are possible (a kind of history). When the timestamp column got added it was populated with default timestamp now.
The problem is that we now have multiple rows with exact same key in the database (unique constraint violation):

You can see that even the metadata uri is identical
Any idea on how to resolve this and why the unique constraint is not preventing this?

Hi there.
I guess that should be the columns names, the following associations at CardReceiverAllocation will automatically create two columns named “receiver_ID“ and “card_ID“ at database table CardReceiverAllocation :
        receiver            : Association to one Receiver
                                  on receiver.ID = receiver_ID;
        card                : Association to one Card
                                  on card.cardID = card_ID;

But since you also create key columns with the same name, that surely is causing some problem. If the main purpose is to create some sort of log table, you can try to create the table with only one key... (GUID), like this:
entity CardReceiverAllocation {
    key ID              : UUID;
    timestamp           : Timestamp default $now; // this column was added later on
    receiver            : Association to one Receiver;
    card                : Association to one Card;
    depositStatus       : Association to one CardDepositStatus;
    creatingUserEmail   : String(64);
    isCurrentAllocation : Boolean default false;
}

entity Card {
    key cardID      : Integer;
        isLost      : Boolean default false;
        pickupSlot  : Association to one PickupSlot;
        receiverAllocations : Association to many CardReceiverAllocation on
            receiverAllocations.card = $self;
        // [...]
}

entity Receiver : cuid {
    firstName                : String(128);
    lastName                 : String(128);
    registrationDate         : Timestamp @cds.on.insert : $now;
    cardAllocations           : Association to many CardReceiverAllocation
                                   on  cardAllocations.receiver = $self;
    isBlocked                : Boolean default false;
    // [...]
}

Is higly improbably that you get duplicate GUID’s at CardReceiverAllocation, unless you create millions of entries in small time interval, only in this case would be necessary to promote timestamp to key.
Cheers.
Rafael Yegros.

Hi Rafael
First of all thank you for your quick answer!
I thought specifiyng the association with on receiver.ID = receiver_ID counts as a "unmanaged association" which will not automatically create the _ID fields as we specify the foreign key ourselves. Or am I misunderstanding something? See explanation here: https://cap.cloud.sap/docs/guides/domain-modeling#managed-1-associations

Since we added the timestamp column later on when the CardReceiverAllocation table already had data and we wanted the timestamp field as part of the key all the existing rows got the timestamp (default $now) in a short timeframe. In the database we actually have over 1300 entries with the exact same timestamp from when we populated the colum and it got filled with the default $now. Maybe because the $now gets translated to an exact timestamp before inserting? Or the Database just being so quick? But wouldn't this throw a unique constraint violation if that resulted in rows with duplicate GUID's?


Mapping from entity to types

Thank you for curating and releasing this dataset. I was trying to use the types.json mapping but I am not sure how I can map entities to their types using the dataset. Any suggestions?

Hi @ameyagodbole, thanks for your interest! In the data/types/ directory, there should be a file called entity2types.json, which maps each entity ID to a list of entity types (which are also Wikidata entity IDs). The README also gives information on the structure. Let me know if you have questions.

I was looking under en and missed the parent directory.
Sorry for the redundant question. Thanks


refactor(api, robot-server): Refactor ProtocolRunner per protocol type

Overview
Closes RSS-200.
create an abstract interface for ProtocolRunner and implement per JsonRunner PythonAndLegacyRunner and LiveRunner.
Also fixes a bug that was causing live http runs to finish executing the run after the first command.
Test Plan

Upload python 2.14, json v6, legacy python protocols and make sure you're able to analyze protocols, run LPC and run protocols. Check that:

all runs are created correctly
can be started, paused and stopped
run results are correct

(Optional)Test a LiveRunner: Start an empty run and post protocol-intent commands. Make sure all commands are run successfully. Also test pausing and stopping the protocol.

Changelog

Refactor ProtocolRunner to be an abstract and implement per JsonRunner PythonAndLegacyRunner and LiveRunner.
create_simulating_runner is now constructed per file type.
Change ProtocolAnalyzer to create on the fly the simulating runner instead of injecting it.
Changed tests that were using an empty run.

Review requests

I (Sanniti) have tested the changes on the dev server but it's important to test on a real robot (ot2/ot3 either works) since run flow control actions can't be tested on the dev server.
We have talked about how having a runner that can allow execution of batch commands could be useful for future features. I agree that it would be useful but the way the engine & run is architected currently, it would need a more detailed change to the architecture (more importantly, careful testing) than is strictly necessary for run split. So I have not attempted to do that in this PR. We will be able to make that change in the future when the feature is on the roadmap.
Currently we are setting run_started_at (also in the run response) when there is a play action. with this change we will no longer set this value for setup commands/post commands. this is the only real noticeable change -> might want to check with UI folks. they should use createdAt instead for this case.

Risk assessment
Medium-high. need to make sure nothing is effected from the refactor for all protocol types and for posting commands/runs with no protocol.

Tested on an OT-2 with json, python, legacy protocols. tested with live protocol commands. works as expected.

Totally agree with the changes added. Makes sense to move common implementations to the abstract. Thank you for fixing this @sanni-t


(read desc) added homepage 3d particle ring effect

pls compare it with the last added background and merge if you like this one.
this looks more like a portal which is the main purpose of the website to be one for historical places

It looks amazing !

Please mention the issue number so that I can assign the correct labels on your PR


Implement support for square and circle annotations

The commit descriptions provide more information about the individual changes.

/botio-linux preview

/botio-linux preview

/botio test

Does somebody have time to review this patch? It will make it easier to implement more annotation types and it is the first step towards supporting annotations without appearance streams (since the invisible annotations that we draw over the canvas can also be made visible and styled in case of missing appearance streams more easily with this approach).

I have updated the patches to resolve conflicts and to convert the code to ES6 syntax after the recent introduction of ES6 syntax for the annotation layer.

Thank you for the review! I incorporated all the improvements you mentioned and verified that everything still works.

/botio-linux preview

/botio test

/botio makeref


Added wcmuse support to handle multi field panel values

Could not create branch feature/multi-field-panel-wcmuse-support. Could you please create it and redirect the PR?

@murilodag not sure I understand what you mean about the branch. It seems like this should be merged to master and feature/6.2-compatibility. Is there a reason we should create a separate branch (and what would happen to that branch)?

@justinedelson , I read in some contributing guide for this repository to merge new features to a feature/new-feature-name. I think it would be fine going master and feature/6.2-compatibility.

@murilodag that is referring to a branch in your fork.

@justinedelson Thank you. Cancelling this PR to open a new correct one.

oh you don't need to do that.

but in the future, it makes things easier for you to manage.


🐛 BUG: kv commands do not roundtrip binary data correctly

What version of Wrangler are you using?
2.0.12
What operating system are you using?
Mac
Describe the Bug
Regression compared to wrangler1, raised by customers in discord. Even if https://github.com/cloudflare/wrangler2/pull/1255 fixes puts, it looks like reads don't work correctly.
bash-3.2$ dd if=/dev/urandom of=/tmp/random-binary bs=1 count=4096
4096+0 records in
4096+0 records out
4096 bytes (4.1 kB, 4.0 KiB) copied, 0.031555 s, 130 kB/s
bash-3.2$ wrangler1 kv:key put --binding="NEWKV" "a-random-key" "/tmp/random-binary" --path
✨  Success
bash-3.2$ wrangler1 kv:key get --binding="NEWKV" "a-random-key" > /tmp/random-binary-roundtrip
bash-3.2$ wrangler2 kv:key get --binding="NEWKV" "a-random-key" > /tmp/random-binary-roundtrip2
bash-3.2$ md5sum /tmp/random-binary
35f2320ed7c5c8ad4fd8056c6773c365  /tmp/random-binary
bash-3.2$ md5sum /tmp/random-binary-roundtrip
35f2320ed7c5c8ad4fd8056c6773c365  /tmp/random-binary-roundtrip
bash-3.2$ md5sum /tmp/random-binary-roundtrip2
2c8bb93dd8bd9c3a22e0158195365bda  /tmp/random-binary-roundtrip2

Thank you for reporting! We should fix this

We've currently reverted https://github.com/cloudflare/wrangler2/pull/1255 and will land it back as soon as we have a fix for kv:key read as well. Thank you for reporting this!


Update Finnish localization

Per discussion in Discord #translations &runAnimFramework currently drops one of the two %3% placeholders. It'll need to be rephrased with a workaround if this does not work.

I've tested the above change and found, that there is no problem at all. If the message anchor includes %1%, %2% and %3%, then those three placeholders must be present within the translations as well. However, if %3% is used twice within the original sentence, but only once within the translation, that works as well .. as long as %3% is present at all.


[doc] Filter is optional in Dd.listCollections

Updated the documentation of the listCollections in the Db class. The filter argument is optional

@jlord this will need a port to 3.0.0


gotk create source git does not create secret for ssh

I'm using following gotk (version 0.1.8, macos) command to create a git source with ssh for a private github repo;
gotk create source git reponame \
<EMAIL_ADDRESS>\
  --branch=master \
  --interval=30s \
  --export

But it somehow gotk does not recognise, that the scheme is ssh and hence doesn't trigger the creation of a deploy key.
The output is:
---
apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: GitRepository
metadata:
  name: k8s-home
  namespace: gotk-system
spec:
  interval: 30s
  ref:
    branch: master
  url<EMAIL_ADDRESS>
I looked at the sources, but can't figure out why it isn't triggered https://github.com/fluxcd/toolkit/blob/main/cmd/gotk/create_source_git.go#L188

When using export we don't generate secrets, as that means storing the secret in clear in your repo. If you want to do that, then run gotk create source git without --export then do:
gotk export source git reponame --with-credentials > source.yaml

thx. Still not sure I understand the flow here.
Why not doing the same for bot cases, with --export and without? Just add the option --with-credentials if one wants the credentials exported?
Currently I understand I have two options to persist the source in the fleet repo:
gotk create source git reponame \
<EMAIL_ADDRESS>\
  --branch=master \
  --interval=30s
gotk export source git reponame > ./dev-cluster/reponame.yaml

or alternatively:
opensssl ...
kubectl create secret --name reponame_secret ...
gotk create source git reponame \
<EMAIL_ADDRESS>\
  --branch=master \
  --interval=30s  \
 --secret-ref=reponame_secret  \
 --export > ./dev-cluster/reponame.yaml

sorry I'm new with the toolkit and may misunderstand the flow. :/


Pre-allocated constraint buffer is full. Increase njmax above 1000.

Hi, thanks for your excellent work. When I run command to train R3M on kitchen_sdoor_open-v3 environment, it works fine at the beginning, but at a certain iteration it throws an error:
>>> python hydra_launcher.py hydra/launcher=local hydra/output=local env=kitchen_sdoor_open-v3 camera=left_cap2 pixel_based=true embedding=resnet50 num_demos=5 env_kwargs.load_path=r3m bc_kwargs.finetune=false bc_kwargs.save_logs=true proprio=9 seed=125 job_name=kitchen_sdoor_open-v3_left-cap2

...
Step 3955
Step 3962
Step 3969
Step 3976
Step 3983
Step 3990
Step 3997
Evaluating
Error executing job with overrides: ['env=kitchen_sdoor_open-v3', 'camera=left_cap2', 'pixel_based=true', 'embedding=resnet50', 'num_demos=5', 'env_kwargs.load_path=r3m', 'bc_kwargs.finetune=false', 'bc_kwargs.save_logs=true', 'proprio=9', 'seed=125', 'job_name=kitchen_sdoor_open-v3_left-cap2']
An error occurred during Hydra's exception formatting:
AssertionError()
Traceback (most recent call last):
  File "/home/tiger/.local/lib/python3.7/site-packages/hydra/_internal/utils.py", line 252, in run_and_report
    assert mdl is not None
AssertionError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "hydra_launcher.py", line 42, in <module>
    configure_jobs()
  File "/home/tiger/.local/lib/python3.7/site-packages/hydra/main.py", line 52, in decorated_main
    config_name=config_name,
  File "/home/tiger/.local/lib/python3.7/site-packages/hydra/_internal/utils.py", line 378, in _run_hydra
    lambda: hydra.run(
  File "/home/tiger/.local/lib/python3.7/site-packages/hydra/_internal/utils.py", line 294, in run_and_report
    raise ex
  File "/home/tiger/.local/lib/python3.7/site-packages/hydra/_internal/utils.py", line 211, in run_and_report
    return func()
  File "/home/tiger/.local/lib/python3.7/site-packages/hydra/_internal/utils.py", line 381, in <lambda>
    overrides=args.overrides,
  File "/home/tiger/.local/lib/python3.7/site-packages/hydra/_internal/hydra.py", line 111, in run
    _ = ret.return_value
  File "/home/tiger/.local/lib/python3.7/site-packages/hydra/core/utils.py", line 233, in return_value
    raise self._return_value
  File "/home/tiger/.local/lib/python3.7/site-packages/hydra/core/utils.py", line 160, in run_job
    ret.return_value = task_function(task_cfg)
  File "hydra_launcher.py", line 38, in configure_jobs
    bc_train_loop(job_data)
  File "/opt/tiger/Robotics/r3m/evaluation/r3meval/core/train_loop.py", line 151, in bc_train_loop
    env_kwargs=env_kwargs)
  File "/opt/tiger/Robotics/r3m/evaluation/r3meval/utils/sampling.py", line 172, in sample_paths
    return do_rollout(**input_dict)
  File "/opt/tiger/Robotics/r3m/evaluation/r3meval/utils/sampling.py", line 95, in do_rollout
    o = env.reset()
  File "/opt/tiger/Robotics/r3m/evaluation/r3meval/utils/gym_env.py", line 91, in reset
    return self.env.reset()
  File "/home/tiger/.local/lib/python3.7/site-packages/gym/core.py", line 311, in reset
    return self.observation(self.env.reset(**kwargs))
  File "/home/tiger/.local/lib/python3.7/site-packages/gym/core.py", line 311, in reset
    return self.observation(self.env.reset(**kwargs))
  File "/home/tiger/.local/lib/python3.7/site-packages/gym/wrappers/time_limit.py", line 26, in reset
    return self.env.reset(**kwargs)
  File "/home/tiger/.local/lib/python3.7/site-packages/gym/wrappers/order_enforcing.py", line 18, in reset
    return self.env.reset(**kwargs)
  File "/opt/tiger/Robotics/lib/mj_envs/mj_envs/envs/relay_kitchen/kitchen_multitask_v2.py", line 335, in reset
    self.sim.step()
  File "mjsim.pyx", line 126, in mujoco_py.cymj.MjSim.step
  File "cymj.pyx", line 156, in mujoco_py.cymj.wrap_mujoco_warning.__exit__
  File "cymj.pyx", line 77, in mujoco_py.cymj.c_warning_callback
  File "/home/tiger/.local/lib/python3.7/site-packages/mujoco_py/builder.py", line 354, in user_warning_raise_exception
    raise MujocoException(warn + 'Increase njmax in mujoco XML')
mujoco_py.builder.MujocoException: Pre-allocated constraint buffer is full. Increase njmax above 1000. Time = 4.0040.Increase njmax in mujoco XML

I guess it may be caused by the buffer constrain of Mujoco. I have found parameter njmax related files under the fold ~/.mujoco/mujoco200/model, but I have no idea which file should be modified. Do you have any advice?

I have found the Franka Kitchen related xml file under the fold mj_envs/mj_envs/envs/relay_kitchen/assets. Increasing njmax and nconmax in line 9 can solve the problem.