Add metadata to Dead lettered Messages

Problem
Messages that fail to be delivered are Dead lettered without any modification, leaving the system/user with no easy way to know why they ended up there. A knative recommendation for this is to add some extra fields in this case that adds that missing info:
https://knative.dev/docs/eventing/event-delivery/#configuring-channel-event-delivery
Persona:
Users
Exit Criteria
Deadlettered messages now have metadata on why they ended up in the DLQ

[ ] Implement DLQ metadata for the Broker
[ ] Implement DLQ metadata for the Source

Is there any update on this other than it is scheduled for the "next" release?

Yes @andrewwebber We are finally getting this into Knative RabbitMQ!
We had some issues since is not well supported yet in RabbitMQ but we ended up implementing a solution here meanwhile!


flutter master  branch - error G09587AA0: Struct 'Utf8' is empty. Empty structs are undefined behavior

the depended plugins ffi-0.1.3 and win32-1.7.4+1 seem broken on flutter master branch, flutter/flutter#76485
Launching lib\main.dart on Windows in debug mode...
/C:/Users/micross/AppData/Local/Pub/Cache/hosted/mirrors.tuna.tsinghua.edu.cn%2547dart-pub/ffi-0.1.3/lib/src/utf8.dart(23,7): error G09587AA0: Struct 'Utf8' is empty. Empty structs are undefined behavior. [E:\workspace\peiyin\build\windows\flutter\flutter_assemble.vcxproj]
/C:/Users/micross/AppData/Local/Pub/Cache/hosted/mirrors.tuna.tsinghua.edu.cn%2547dart-pub/ffi-0.1.3/lib/src/utf16.dart(16,7): error G09587AA0: Struct 'Utf16' is empty. Empty structs are undefined behavior. [E:\workspace\peiyin\build\windows\flutter\flutter_assemble.vcxproj]
/C:/Users/micross/AppData/Local/Pub/Cache/hosted/mirrors.tuna.tsinghua.edu.cn%2547dart-pub/win32-1.7.4+1/lib/src/structs.dart(1111,7): error G09587AA0: Struct 'ENUMLOGFONTEX' is empty. Empty structs are undefined behavior. [E:\workspace\peiyin\build\windows\flutter\flutter_assemble.vcxproj]
/C:/Users/micross/AppData/Local/Pub/Cache/hosted/mirrors.tuna.tsinghua.edu.cn%2547dart-pub/win32-1.7.4+1/lib/src/structs.dart(2835,7): error G09587AA0: Struct 'BLUETOOTH_PIN_INFO' is empty. Empty structs are undefined behavior. [E:\workspace\peiyin\build\windows\flutter\flutter_assemble.vcxproj]
/C:/Users/micross/AppData/Local/Pub/Cache/hosted/mirrors.tuna.tsinghua.edu.cn%2547dart-pub/win32-1.7.4+1/lib/src/structs.dart(2960,7): error G09587AA0: Struct 'EXCEPINFO' is empty. Empty structs are undefined behavior. [E:\workspace\peiyin\build\windows\flutter\flutter_assemble.vcxproj]
/C:/Users/micross/AppData/Local/Pub/Cache/hosted/mirrors.tuna.tsinghua.edu.cn%2547dart-pub/win32-1.7.4+1/lib/src/structs.dart(2966,7): error G09587AA0: Struct 'PROPERTYKEY' is empty. Empty structs are undefined behavior. [E:\workspace\peiyin\build\windows\flutter\flutter_assemble.vcxproj]
/C:/Users/micross/AppData/Local/Pub/Cache/hosted/mirrors.tuna.tsinghua.edu.cn%2547dart-pub/win32-1.7.4+1/lib/src/structs.dart(2973,7): error G09587AA0: Struct 'PROPVARIANT' is empty. Empty structs are undefined behavior. [E:\workspace\peiyin\build\windows\flutter\flutter_assemble.vcxproj]
/C:/Users/micross/AppData/Local/Pub/Cache/hosted/mirrors.tuna.tsinghua.edu.cn%2547dart-pub/win32-1.7.4+1/lib/src/structs.dart(2978,7): error G09587AA0: Struct 'SAFEARRAY' is empty. Empty structs are undefined behavior. [E:\workspace\peiyin\build\windows\flutter\flutter_assemble.vcxproj]
/C:/Users/micross/AppData/Local/Pub/Cache/hosted/mirrors.tuna.tsinghua.edu.cn%2547dart-pub/win32-1.7.4+1/lib/src/structs.dart(2985,7): error G09587AA0: Struct 'CLSID' is empty. Empty structs are undefined behavior. [E:\workspace\peiyin\build\windows\flutter\flutter_assemble.vcxproj]
/C:/Users/micross/AppData/Local/Pub/Cache/hosted/mirrors.tuna.tsinghua.edu.cn%2547dart-pub/win32-1.7.4+1/lib/src/structs.dart(2992,7): error G09587AA0: Struct 'STATSTG' is empty. Empty structs are undefined behavior. [E:\workspace\peiyin\build\windows\flutter\flutter_assemble.vcxproj]
/C:/Users/micross/AppData/Local/Pub/Cache/hosted/mirrors.tuna.tsinghua.edu.cn%2547dart-pub/win32-1.7.4+1/lib/src/structs.dart(2999,7): error G09587AA0: Struct 'NLM_SIMULATED_PROFILE_INFO' is empty. Empty structs are undefined behavior. [E:\workspace\peiyin\build\windows\flutter\flutter_assemble.vcxproj]
/C:/Users/micross/AppData/Local/Pub/Cache/hosted/mirrors.tuna.tsinghua.edu.cn%2547dart-pub/ffi-0.1.3/lib/src/allocation.dart(47,33): error G733AAF94: Expected type 'T' to be a valid and instantiated subtype of 'NativeType'. [E:\workspace\peiyin\build\windows\flutter\flutter_assemble.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(238,5): error MSB8066: “E:\workspace\peiyin\build\windows\CMakeFiles\7c00e294f53b2c18e279f5a7262d1203\flutter_windows.dll.rule;E:\workspace\peiyin\build\windows\CMakeFiles\1641237fcbf9c44140010e4124d17fea\flutter_assemble.rule”的自定义生成已退 出，代码为 1。 [E:\workspace\peiyin\build\windows\flutter\flutter_assemble.vcxproj]
Building Windows application...
Exception: Build process failed.

This is an issue with Flutter, not much I can do on my side:
https://stackoverflow.com/questions/65912637/how-can-i-fix-this-error-struct-utf8-is-empty-support-for-empty-structs-is-d

update package:ffi to version 1.0.0  and package:win32 to preview version 2.0.0 may help.

What is your Flutter version?

I've just published 0.0.6
Please try it and let me know how that works.

it works now, thank you.
Flutter 1.27.0-5.0.pre.112 • channel master • https://github.com/flutter/flutter.git
Framework • revision 90c66f5db3 (2 hours ago) • 2021-02-22 18:21:03 -0800
Engine • revision 07afcf7d0f
Tools • Dart 2.13.0 (build 2.13.0-52.0.dev)


Support external/pre-provisioned authoritative cluster DNS

What does this PR do?

Document how to use fully external DNS servers w/o provisioning
dns servers group with Heat.

Document how to use a mixed servers setup for dynamic records
updates mathing public or private views.

Allow custom public key names for OSP10 dns service compatibility.
The osp-dns configures the named service with the fixed key_name
'update-key'. Add optional key_name for the external_nsupdate_keys
public section to allow custom key names.

How should this be manually tested?
Fully external DNS server:

Deploy s DNS server (f.e. by this guide) and populate an inventory file (e.g. inventory/external_dns.yaml) with its nsupdate data
Run provision openstack with app nodes count of 1 and dns nodes count of 0, and add
<EMAIL_ADDRESS>for the ansible-playbook commands used
Finish e2e (it shall pass)
Run provision openstack with app nodes count of 2 and dns nodes count of 0 and add
<EMAIL_ADDRESS>for the ansible-playbook commands used
Finish e2e (it shall pass)
Check if all app nodes' FQDNs are resolvable via your external DNS

Mixed instack/external DNS:

Deploy s DNS server (f.e. by this guide) and populate an inventory file (e.g.
inventory/external_dns.yaml) external_nsupdate_keys.public with the required server, key,
algorithm data.
Run provision openstack with app nodes count of 1 and dns nodes count of 1, and add
<EMAIL_ADDRESS>for the ansible-playbook commands used
Finish e2e (it shall pass)
Run provision openstack with app nodes count of 2 and dns nodes count of 1 and add
<EMAIL_ADDRESS>for the ansible-playbook commands used
Finish e2e (it shall pass)
Check if:

app nodes' public FQDNs are resolvable via your external DNS (run nslookup or dig against the public
DNS server public IP)
the private DNS server is used for a private view (run nslookup or dig from a cluster node to verify
this).

Is there a relevant Issue open for this?
Provide a link to any open issues that describe the problem you are solving.
Who would you like to review this?
cc: @tomassedovic @oybed PTAL

One question to both of you @bogdando and @oybed while we're thinking about external DNS.
Do you think it would be worthwhile to add support for servers that don't have multiple views? The one I'm testing this against doesn't so I had to create two of them. We would have to add e.g. a hostname suffix to the private entries and configure openshift-ansible accordingly, or something.
FWIW this is what the Red Hat reference architectures do (different names for public/private resolution).

Yes
The azure has a internal name server
And servers have internal and external names
In customer I see also multiple domains as well for applications
To the point there needs to be a microservice dns to facilitate
Sent from my iPhone

On 25 Aug 2017, at 6:03 PM, Tomas Sedovic<EMAIL_ADDRESS>wrote:
One question to both of you @bogdando and @oybed while we're thinking about external DNS.
Do you think it would be worthwhile to add support for servers that don't have multiple views? The one I'm testing this against doesn't so I had to create two of them. We would have to add e.g. a hostname suffix to the private entries and configure openshift-ansible accordingly, or something.
FWIW this is what the Red Hat reference architectures do (different names for public/private resolution).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@tomassedovic addressed the @oybed comments.
wrt a single view DNS servers and different FQDNs for priv/pub access, I believe we should switch the default DNS stack to Designate as soon as we can do that. I see no need to go (and maintain) offroad solutions but those that OpenStack DNSaaS proposes. Let's please create a separate feature request as well.

Yeah sorry if I was unclear. I meant it as a separate RFE/PR. We can merge this one when the end/end CI passes.

@tomassedovic supporting an internal and external set of hostnames is possible and it can all be driven by the playbooks. However, as-is, and what I have done in these cases where the DNS server doesn't support views, is to stand up 2 DNS servers (potentially with different ACLs) and hence one will serve the internal aspect and the other the external. With that approach, the playbooks will work as-is without any special handling/changes needed.

@oybed yeah that (2 servers) is what I've done so far. And yeah, good point on this being possible through the playbooks alone. I forgot about that.


[feature] Validate model directory for the given format

Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
We should validate the model.
Ref https://github.com/caicloud/ormb/pull/10#discussion_r429014208
/cc @codeflitting

/priority p2

At the same time, ORMB UI needs to visualize the model directory structure

At the same time, ORMB UI needs to visualize the model directory structure

I think it is a separate feature, will open a new issue for it.

https://github.com/caicloud/ormb/issues/42

/assign @simon-cj I think we also need it when uploading models in dashboard.

/assign @simon-cj I think we also need it when uploading models in dashboard.

validate model directory when uploading models in dashboard, I think it should be in the model registry， not in ormb， WDYT

Yeah, I think so. But we also need to validate the model in ormb side. WDYT

I am not understant this issue, can you describe it

When users run ormb save, we need to validate that the model is qualified.

SGTM, I will do it


refmt not idempotent for optional tuple

I have the reason code
switch !prevEl {
    | None => prevEl := currEl
    | Some (prevInner, prevOuter) =>
      print_endline "asd"
    }

Which becomes the following ocaml code with refmt -parse re -print ml
let _ =
  match !prevEl with
  | None  -> prevEl := currEl
  | ((Some ((prevInner,prevOuter)))[@explicit_arity ]) -> print_endline "asd"

Which becomes this when formatting back to reason
switch !prevEl {
| None => prevEl := currEl
| Some prevInner prevOuter => print_endline "asd"
};

This is wrong because Some is now taking 2 arguments instead of a 1 argument being a tuple.

Fixed in master


port hobbes to OSX

This adjusts various parts of the code so that it can also build on OSX.  In the process, I also fixed the bug where the std::string type didn't lift correctly (which has affected a couple of other platforms as well).
This change still leaves open the issue of supporting C++ class coercions on OSX because it seems that clang doesn't expose the same information that gcc does (at least in the clang build on my Mac).
Also readline seems to be a little buggy on OSX so the "hi" shell doesn't show the prompt consistently or support the line edit history correctly.
But at least the hobbes compiler works, all tests (except class coercion tests) pass, structured logging over shared memory works via storage.H and lightweight networking via net.H also works.

Hi, Kalani,
I tried all LLVM versions available on mac as below:
$ brew search llvm
llvm ✔<EMAIL_ADDRESS>✔<EMAIL_ADDRESS>✔<EMAIL_ADDRESS>✔

all failed with:

CMake Error at /usr/local/opt/llvm@3.8/lib/llvm-3.8/share/llvm/cmake/LLVM-Config.cmake:203 (message):
Library `jit' not found in list of llvm libraries.

You may want to specify what exact environment is needed to have this build/test properly?

I hit a similar issue when I was moving between different LLVM builds on OSX.  I am not sure what the best way is to select components here -- if I select "all" then I think I can get it to work across different LLVM versions but then it's going to link against too many things.
FWIW, I did all of my testing with llvm-3.5 as selected by the MacPorts package manager.

I tried llvm37 (homebrew) + link all,  i can build it successfully, but cores when i running "hi".

My tests here were only with LLVM 3.5.  I will take a look at 3.7, see if there's anything I can do to sort out the component selection between different versions.  If anybody has ideas about that, I'd love to know -- else I may put the question to one of the LLVM lists.

It looks like this is an issue with LLVM, there doesn't seem to be a consistent way to select components for a JIT between 3.5-4: https://github.com/RPCS3/rpcs3/issues/1070
I think that we might need to add some analysis to our cmake file to select different components depending on which version of LLVM is selected.

Updated PR, cmake will pull all LLVM components -- this is more than we need but it's not clear to me how to select just what's necessary between LLVM versions, hopefully the linker can sort this out.
Also I reproduced the crash with LLVM 3.7 on OSX.  It was an issue with some logic in jitcc specific to 3.7+ versions of LLVM.  It looks like "hi" works with these changes.

Now I saw this with llvm3.7:
In file included from /Users/huangbaiyan/work/hobbes/lib/hobbes/eval/func.H:6:
/Users/huangbaiyan/work/hobbes/lib/hobbes/lang/tylift.H:195:10: error: redefinition of 'hobbes::lift<std::string, true>'
  struct lift< std::string, true > { static MonoTypePtr type(typedb&) { return OpaquePtr::make("std::string", sizeof(std::string), true); }  };

Here is what I used to build:
export<EMAIL_ADDRESS>cmake .
make
make install

Bad merge, fixed now.

I fixed another problem that I noticed with the LLVM 3.7 issue pointed out by libow.

(PS: It seems that my OS system readline library is a little wonky, echoes the prompt the wrong way.  I had to update it.)

If no one else is having this problem than feel free to ignore this comment but this project doesn't build with xcode's clang. Specifically there is a complaint about clock_gettime which seems to be related to https://stackoverflow.com/questions/5167269/clock-gettime-alternative-in-mac-os-x
jonathanbarrios@lasalle [19:40:55] [~/hobbes] [port-to-OSX *]
-> % make
Scanning dependencies of target hobbes
[  0%] Building CXX object CMakeFiles/hobbes.dir/lib/hobbes/boot/gen/boot.C.o
[  1%] Building CXX object CMakeFiles/hobbes.dir/lib/hobbes/db/bindings.C.o
[  1%] Building CXX object CMakeFiles/hobbes.dir/lib/hobbes/db/file.C.o
[  2%] Building CXX object CMakeFiles/hobbes.dir/lib/hobbes/db/series.C.o
In file included from /Users/jonathanbarrios/hobbes/lib/hobbes/db/series.C:2:
In file included from /Users/jonathanbarrios/hobbes/lib/hobbes/db/series.H:12:
/Users/jonathanbarrios/hobbes/lib/hobbes/util/perf.H:15:21: error: use of undeclared identifier 'CLOCK_MONOTONIC'
  if (clock_gettime(CLOCK_MONOTONIC, &ts) == 0) {
                    ^
/Users/jonathanbarrios/hobbes/lib/hobbes/util/perf.H:25:21: error: use of undeclared identifier 'CLOCK_REALTIME'
  if (clock_gettime(CLOCK_REALTIME, &ts) == 0) {
                    ^
2 errors generated.
make[2]: *** [CMakeFiles/hobbes.dir/lib/hobbes/db/series.C.o] Error 1
make[1]: *** [CMakeFiles/hobbes.dir/all] Error 2
make: *** [all] Error 2

@jeb2239 I wonder if this could be an issue with older XCode/clang installs?
My cmake-generated make files seem to decide on using this compiler from my local system (macOS Sierra 10.12.5):
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -> clang
Do you know what OS/XCode version you're using?

That must be it. I was using capitain.
Sent from my Motorola XT1650 using FastHub

I uninstall my XCODE, and set CC to export<EMAIL_ADDRESS>but still got the same error as jeb2239 above.

Could this be a brew vs macports issue?
Sent from my Motorola XT1650 using FastHub

I'm using clang with, I think, a recent version of XCode.  This clock_gettime code isn't really that important so I would rather not have it block anybody.  If you stub the tick/time functions to just return 0, are you able to make progress or are there other compile errors?

There are a few other errors after comment out the tick/time error:
/Users/huangbaiyan/Dev/work/hobbes/lib/hobbes/util/autorelease.H:16:12: warning: reference to stack memory associated with local variable 'rs' returned [-Wreturn-stack-address]
    return rs;
           ^~
/Users/huangbaiyan/Dev/work/hobbes/lib/hobbes/util/autorelease.H:37:7: error: thread-local storage is not supported for the current target
      thread_local Vals vs;

What is the difference between using clang installed and clang from Xcode?

Baiyan, what version of clang are you using?  I haven't seen those complaints about thread_local before, and the warning referencing the return of a stack address is on a thread_local var too (just double-checked).

I am using this version:
$<EMAIL_ADDRESS>--version
clang version 3.7.1 (tags/RELEASE_371/final)
Target: x86_64-apple-darwin14.5.0
Thread model: posix

and my build is started with:
export<EMAIL_ADDRESS>export<EMAIL_ADDRESS>cmake .
make

My llvm is installed using homebrew

I previously was installing LLVM with ports but also used brew to get LLVM 3.7 and fix the issue that libow hit with 3.7.
I seem to be picking up this version of clang with my XCode install:
$ /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ --version
Apple LLVM version 8.1.0 (clang-802.0.42)
Target: x86_64-apple-darwin16.6.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

I am not sure whether hobbes can compile with clang 3.7.  That's probably another porting effort, but the complaints about thread_local scare me.  :)

@baiyanhuang pls try osx10.12+ and xcode8.3 toolchain


Some implementation hints and questions

Hi.  It seems I can’t add inline comments to README.rst, as github renders it to HTML instead of showing the source, so here are comments.  I am a Python core developer in charge of distutils, BTW.

Myppy is a set of tools for building and managing a portable python environment.
The end result is something similar in spirit to portable python_ but can
be built for a variety of different platforms.

You should also compare it to virtualenv.

Currently targeted build environments are linux-i686 and OSX.

Why only i686?

Scripts installed by easy_install and pip embed the absolute path to the
interpreter in the shebang line; they should be replaced by a loader stub
that finds python at runtime.

This is controllable with the --executable option of the build_scripts command.

distutils and sysconfig embed the absolute library paths as they were at
build time, meaning you can't properly build C-extensions if you move the
environment around.  They should be patched in a simlar way to virtualenv.

This may be changed in Python itself, as we want to support virtualenv-like functionality in the interpreter for 3.3.

Why, everything that something like portable python_ is good for, but on
Linux or OSX instead of Windows!  Use it as a convenient portable scripting or
testing environment, or to run multiple python versions side-by-side.

Is it also useful to put a Python on a USB stick and use it anywhere?

On 09/10/11 19:57, Éric Araujo wrote:

Hi.  It seems I can’t add inline comments to README.rst, as github renders it to HTML instead
of showing the source, so here are comments.  I am a Python core developer in charge of distutils, BTW.

Thanks Éric.  I lurk on python-dev so I recognised your name.

Myppy is a set of tools for building and managing a portable python environment.
The end result is something similar in spirit to portable python_ but can
be built for a variety of different platforms.

You should also compare it to virtualenv.

A good suggestion, although the comparison will probably be more about
how they are different than how they are similar.

Currently targeted build environments are linux-i686 and OSX.

Why only i686?

It's all I've needed, and all I have set up for testing at the moment.
I don't see why the build tools couldn't be made to work on other
architectures, I just haven't tried it.
The OSX scripts build fat binaries though, so it's not limited to i686
in that case.

Scripts installed by easy_install and pip embed the absolute path to the
interpreter in the shebang line; they should be replaced by a loader stub
that finds python at runtime.

This is controllable with the --executable option of the build_scripts command.

Ah, interesting.  Thanks for pointing it out, I will investigate.

distutils and sysconfig embed the absolute library paths as they were at
build time, meaning you can't properly build C-extensions if you move the
environment around.  They should be patched in a simlar way to virtualenv.

This may be changed in Python itself, as we want to support virtualenv-like functionality in the interpreter for 3.3.

Nice.  Is there an open bug for it at this stage?  Or is it just in
planning on python-dev?

Why, everything that something like portable python_ is good for, but on
Linux or OSX instead of Windows!  Use it as a convenient portable scripting or
testing environment, or to run multiple python versions side-by-side.

Is it also useful to put a Python on a USB stick and use it anywhere?

Yes - assuming the above-mentioned issues with absolute paths can be fixed.
Unfortunately I don't have much time to devote to the project at the
moment.  Cloudmatrix as a business venture is pretty much dead from lack
of funding, and I don't need myppy for any of my existing projects at
the moment, so it's relegated to hobby status.
I do hope to keep pushing it forward but it's going to be slow going.
Cheers,
Ryan

A good suggestion, although the comparison will probably be more about
how they are different than how they are similar.
Good.
Why only i686?

It's all I've needed, and all I have set up for testing at the moment.
Okay, I’ll try to run it on my x64_86 Debian machine.
This may be changed in Python itself, as we want to support virtualenv-like functionality in the interpreter for 3.3.

Nice. Is there an open bug for it at this stage? Or is it just in planning on python-dev?
There have been a number of threads on distutils-sig and python-dev.  A PEP will be written.  There is a repository (https://bitbucket.org/vinay.sajip/pythonv) but no bug report.
Is it also useful to put a Python on a USB stick and use it anywhere?

Yes - assuming the above-mentioned issues with absolute paths can be fixed.
Great feature.  Tell me if you need help with that bug then!
Unfortunately I don't have much time to devote to the project at the moment. Cloudmatrix as a business venture is pretty
much dead from lack of funding, and I don't need myppy for any of my existing projects at the moment, so it's relegated
to hobby status.
I understand that, I contribute to Python on my free time.

The quotes were borked but hopefully my reply is still readable.


Look-and-feel, and UI features, of the entities

particularly narrative elements and items of evidence).
As a general background point, as I ponder these things, I'm increasingly inclined to think we should strive to create first a simple-as-possible (or nearly so) base version, which would be fairly "vanilla" in appearance and functionality.  As an example of what I mean by this, consider the issue of whether the basic entities should have, or be built around, icons. There are of course various pros and cons. One of the cons is that it can be very hard to find suitable icons. I've searched a lot for something that seemed to work for "event" or "narrative element", but haven't found anything that seems to work. A minimalist version of the app would sidestep this issue - maybe icons are needed and can be introduced further down the road, but in version 0.1, we do without them.

Narrative elements, and items of evidence, are (basically) just text boxes, with a label and (optionally) body text.
They are distinguished in various ways: rounded corners vs r-angle corners, coloured background vs plain white, no border vs border - and of course by general location, and the kinds of connections they have.

Focusing just on narrative elements for the moment: these are "fine-tuned" in various ways taking advantage of standard draw.io options. Formatting:

grey fill
rounded corners
content is just a single rich-text field, first line is H3 style, body is normal style (but it may work much better to have a more complex shape with two distinct text fields)
Spacing (margins) is -5pt at top, 10pt on left and right

Functionality/interaction:

The shape auto-resizes in height to accommodate the amount of text it contains; width is manually changeable.


[requirement] VPN disconnection protection

Hello, I think the softether client should add the function of VPN disconnection protection. When the VPN is disconnected or reconnected, the application is prohibited from accessing the Internet.
**SoftEther version: latst version
Component: [Client]
Operating system: [Windows,]
Architecture: [64 bit]

I think this is similar to #1634

Closing in favor of #1634


Add gentx for Borsh

Please make sure your node is up and running now. Join #validators on Discord for help: https://discord.gg/QeJWCrE.


[INLONG-2448] [SDK] upgrade httpclient to secure version

Fixes #2448
Motivation
use secure library
Modifications
pom change
Verifying this change

[X] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

Codecov Report

Merging #2449 (3b9d597) into master (4d236f7) will increase coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #2449      +/-   ##
============================================
+ Coverage     12.53%   12.55%   +0.02%
- Complexity     1218     1222       +4
============================================
  Files           420      420
  Lines         36255    36255
  Branches       5674     5674
============================================
+ Hits           4545     4553       +8
+ Misses        30901    30893       -8
  Partials        809      809

Impacted Files
Coverage Δ

.../tubemq/corebase/policies/FlowCtrlRuleHandler.java
34.51% <0.00%> (+0.44%)
:arrow_up:

.../inlong/tubemq/corebase/policies/FlowCtrlItem.java
40.00% <0.00%> (+1.11%)
:arrow_up:

.../producer/qltystats/DefaultBrokerRcvQltyStats.java
45.31% <0.00%> (+1.17%)
:arrow_up:

.../client/producer/qltystats/BrokerStatsItemSet.java
72.09% <0.00%> (+4.65%)
: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 4d236f7...3b9d597. Read the comment docs.


Improve errors from frame.waitFor* methods

closes #394

Done @Meir017

@Meir017 could you take a look at the latest commit?

Done @Meir017


Defib requires armor to be off to use + medical Locale fixes

About the PR
some medical locale now respects pronouns
defib can only be used if armor is off
Why / Balance
CM13 parity
fixes defib not having RMC battery
Technical details

Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog
:cl:

tweak: Defibrillating someone now requires their armor to be off.

requested changes done


Name

Give this tool and repo a name

[ ] Update package.json
[ ] Add repository field

{
  "repository": {
    "type": "git",
    "url": "https://github.com/luanorlandi/gaming-bot-sdk/"
  }
}

Possible names related to robots in games:

LegionJS
GladosJS
ClaptrapJS

Ended up with gladosjs:
https://www.npmjs.com/org/gladosjs/


Fixed issue for loading/unloading an additive scene multiple times. I…

Fixed issue for loading/unloading an additive scene multiple times. I've added an example scene which you can enable in the build settings "Master Scene". The example shows how to properly load and unload additive scenes in a network enviroment. You should call Network NetworkManager.Instance.UnloadSceneAdditive(sceneName / sceneIndex). I use this a lot in my game for world streaming so hopefully will also be useful for someone else (Pulled from my custom version of Forge)

Before this commit the actual behaviour was
[Actual Behaviour]

Connect to server which changes the active scene
Clients connect to server
You load in the additive scene (2 and 3 can be in either order)
You unload the additive scene (The client does recieve a command to destory the scene)
You load the additive scene (Error the ArgumentException: An element with the same key already exists in the dictionary.)

[New Behaviour]

Connect to server which changes the active scene
Clients connect to server
You load in the additive scene (2 and 3 can be in either order)
You unload the additive scene using NetworkManager.Instance.UnloadSceneAdditive, which informs the client to unload the scene aswell as properly disposing of the network objects from the
dictionary in the NetWorker
Go back to step 3 - All should work

Looks fine to me and @tommohawkaction said he did test it in a non-custom version of Forge.
Only thing being the merge conflicts

Yes all raw Forge. Mentioned this is our private chat, there is an example scene called MasterScene which you can enable in the build settings to see this in action

Please make sure to use the correct branch for your changes to not get merge conflicts.

Please make sure to use the correct branch for your changes to not get merge conflicts.

Apologies, are we able to discard most of them except the EditorBuildSettings

you need to fix your setup. You are using your fork's master branch instead of develop as it is mentioned on the wiki under contributions.
I personally would have created a feature branch from my fork's develop branch and used that instead of adding changes straight to the fork's master/develop branches
Makes it easier to deal with changes from upstream.


fix: use user as owner of files generated by nasher instead of root

Currently files generated by nasher in docker are generated as root. So files which are generated by nasher are owned by root:root. This forces users to change the permissions of the files with sudo/root permissions. This is bad practice for CI/CD pipelines where the files should be owned by the user that started the docker container. This change fixes this problem.

Sorry, I missed this when you made the PR.
Is there a benefit to doing it this way versus using --user $(id -u):$(id -g) in the docker run command?

Passing user id and group id to docker does not work with the current Dockerfile. The tools installed within are installed as root currently, so they are not available to the user that calls docker. You will get something like:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"nasher\": executable file not found in $PATH": unknown.
If using docker without specifying a user and a group the created module.mod file is owned by root as well. It's the weird docker user thing where the id inside the docker container is the user outside the docker container.
For example: If using github actions to deploy your nwn module with docker you currently have the problem, that the files are deleted and newly generated. The created module.mod file has root permissions so i would need to create a script with sticky bit, which is bad as well.
My pull request is not exactly great as well though, as the user has to have uid 1001 for it to work correctly.

@urothis, do you have any  opinions or insight on this?

This looks like a good idea,
Although I would recommend passing the UID in with an ARG with a default value. To support any other odd usage someone might wanna do.


Remove custom job factory

I couldn't quite figure out what the goal of the custom JobFactory was. It's been around for ages, it looks like. 7+ years. Maybe there was some data missing on the IJobExecutionContext back in the day? I don't know.
Either way, instead of using the MassTransitJobFactory to create an instance of the type, and all the complexity that comes with it, I think it makes sense to just get the data from the job execution context. It's there. I left most of the logic exactly the same. Merge the maps (by hand, though that's another question, Quartz documentation says using the MergedMap on IJobDetail is preferred). Added a class to hold the properties, which get populated using the property read/writer thing.
So, now, at least for my application, I can use the default AutofacJobFactory that creates the ScheduledMessageJob from the container on it's own. Since IBus is there, it works nicely.

I doubt I'll accept it anytime soon, I don't have time to verify backwards compatibility, etc.

Relevant Discussion on integration with MS DI

I removed the job factory from v8, thanks for the idea!


Some more documentation on getting started would be helpful

The docs show how to get started in nativescript but don't cover getting Tesseract installed for Android or iOS.
It would be really helpful (for newbs like me at least) to have maybe some links or a simple list of how we can get Tesseract installed, what dependencies this module requires etc.
For example, I am using Mint 18 with Tesseract installed from the package manager, but I am getting a "TypeError: Cannot read property 'tesseract' of undefined" error when trying to scan an image. I assume this is because the Tesseract libs are not installed for Android, but I am finding it quite hard to track down how to install this (most of the tutorials online invoilve using Eclipse, Android Studio etc etc).
Hope that makes some sense?

Just an update, in the end it appeared Tesseract was installed correctly, but running tns run didn't pull down all dependencies.
Running tns build however sorted the issue.

@mlewis-everley can you please explain how can i set up this in a project?


Address R CMD check notes related to DESCRIPTION formatting

Umlaute are problematic
The "description" field may not start with the package name

the dplyr stuff is actually gone so perhaps that can be reflected? otherwise fine with me


Deprecation Warning

FastAPI: 0.105.0
fastapi-mqtt 2.1.1
 /usr/local/lib/python3.11/site-packages/fastapi_mqtt/fastmqtt.py:235: DeprecationWarning:
          on_event is deprecated, use lifespan event handlers instead.

          Read more about it in the
          [FastAPI docs for Lifespan Events](https://fastapi.tiangolo.com/advanced/events/).

    @app.on_event("shutdown")

Hi @ftapajos, you should use a lifespan, as indicated in the warning, and use the await fast_mqtt.mqtt_startup() and await fast_mqtt.mqtt_shutdown() methods, instead of the old fast_mqtt.init_app(app) method 👌
An example of that is already in one of the included examples (examples/ws_app/app.py) --> https://github.com/sabuhish/fastapi-mqtt/blob/d4da8acdf1d6fe06a646cb616582abe06ae16a54/examples/ws_app/app.py#L27-L35
Both methods are valid, but the lifespan is preferred 👍


c-c c-p (projectile-mode-map) conflicts with org mode's outline-previous-visible-heading

https://github.com/purcell/emacs.d/blob/a97dc5a44242f7f78c70335a9532bc657ea0a8d8/lisp/init-projectile.el#L12
the projectile readme suggests c-c p rather than c-c c-p. perhaps this would be a better option?

Makes sense - done, thanks.


How do I make a type that can be two or more different types

I need to validate a field that can be either number or string, like zod has or() for example
It is also not quite clear how to use the default value for validation.

use union([string(), number()])


Url resolution & menu bugs

Added url resolution on paste (based on #10).
Fill free to change anything (names, filenames...), just wanted to add the basic functionality open to possible refactoring.

Resolved conflicts (was really hard for some reason)

@MaanooAk probably because I just introduced eslint 😬 sorry

#41 should close after this.

Last commits removes the template[1].submenu[7].submenu = ... with fixed indexes (which has already caused enough problems).

Fixing the validation errors now...

Nice, thank you for that. I haven't gotten the url resolution regex to work, perhaps we could leverage another library that has solved this problem such as https://github.com/ogt/valid-url?

Wait, you mean it doesn't work for you?
(note: it has to be one line starting with http:// or https://)
Try copy this http://maanoo.com/projects/data.json and git to the app select all -> paste.

I see, yeah that was the issue. Thanks for cleaning up the validation errors! I'm down to merge this for now. We can improve it over time.


RunOptions.FULL_TRACE produce wrong timestamps

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):Ubuntu 16.04
TensorFlow installed from (source or binary):binary
TensorFlow version (use command below):v1.9.0-0-g25c197e023 1.9.0
Python version: 3.6
Bazel version (if compiling from source):n/a
GCC/Compiler version (if compiling from source):n/a
CUDA/cuDNN version:9.0.176/7.1.1
GPU model and memory:P100 16G (can reproduce on other GPU model as well)
Exact command to reproduce: see below

#!/usr/bin/env python
# -*- coding: utf-8 -*-

import sys
import os
import tqdm
from datetime import datetime
import tensorflow as tf
from tensorflow.python.client import timeline

def build():
    image = tf.random_normal(shape=[64,32,32,3], dtype=tf.float32)
    label = tf.random_uniform(shape=[64], maxval=10, dtype=tf.int32)
    l = tf.transpose(image, [0, 3, 1, 2])
    for k in range(1, 100):
        l = tf.layers.conv2d(l, 16, 3, data_format='channels_first',
                name='conv{}'.format(k), padding='SAME')
    l = tf.reduce_mean(l, [2, 3])

    logits = tf.layers.dense(l, 10, name='linear')
    cost = tf.nn.sparse_softmax_cross_entropy_with_logits(logits=logits, labels=label)
    cost = tf.reduce_mean(cost, name='cross_entropy_loss')
    return cost

if __name__ == '__main__':
    with tf.device('/gpu:0'):
        cost1 = build()
    with tf.device('/gpu:1'), tf.variable_scope(tf.get_variable_scope(), reuse=True):
        cost2 = build()
    cost = cost1 + cost2
    opt = tf.train.GradientDescentOptimizer(0.1)
    train_op = opt.minimize(cost)

    def write_tracing(idx, metadata):
        tl = timeline.Timeline(step_stats=metadata.step_stats)
        fname = os.path.join(
            '.', 'chrome-trace-{}.json'.format(idx))
        with open(fname, 'w') as f:
            f.write(tl.generate_chrome_trace_format(
                show_dataflow=True, show_memory=True))

    config = tf.ConfigProto()
    config.allow_soft_placement = True
    with tf.Session(config=config) as sess:
        sess.run(tf.global_variables_initializer())
        opt = tf.RunOptions()
        opt.trace_level = tf.RunOptions.FULL_TRACE

        for k in tqdm.trange(100):
            meta = tf.RunMetadata()
            sess.run(train_op, options=opt, run_metadata=meta)

            write_tracing(k, meta)

            for devst in meta.step_stats.dev_stats:
                for ns in devst.node_stats:
                    micro = timestamp = ns.all_start_micros // 1000000
                    timestamp = datetime.fromtimestamp(timestamp)
                    diff = timestamp - datetime.now()
                    if diff.days > 100:
                        print(k, micro, timestamp)
                        #import IPython as IP; IP.embed()
                        #sys.exit()

The code above trains a CNN on two GPUs with FULL_TRACE enabled. The returned profiling information contains correct timestamps, but sometimes contains timestamps that are many years in the future. It prints the following output:
...
13<PHONE_NUMBER>3 2554-07-21 16:34:33
13<PHONE_NUMBER>3 2554-07-21 16:34:33
13<PHONE_NUMBER>3 2554-07-21 16:34:33
13<PHONE_NUMBER>3 2554-07-21 16:34:33
13<PHONE_NUMBER>3 2554-07-21 16:34:33
13<PHONE_NUMBER>3 2554-07-21 16:34:33
13<PHONE_NUMBER>3 2554-07-21 16:34:33
13<PHONE_NUMBER>3 2554-07-21 16:34:33
13<PHONE_NUMBER>3 2554-07-21 16:34:33
13<PHONE_NUMBER>3 2554-07-21 16:34:33
13<PHONE_NUMBER>3 2554-07-21 16:34:33
...

The issue was originally reported at https://github.com/tensorpack/tensorpack/issues/819.
The issue is more likely to happen after running about 50 steps.
The issue seems to disappear when training on one GPU, or training a small model.

Nagging Assignee @angersson: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@zheng-xq Can you have a look at this? Seems possibly GPU-related.

@zheng-xq @tensorflowbutler  @ppwwyyxx
It seems like a problem in calling the cupti func:
tensorflow\core\platform\default\gpu\cupti_wrapper.cc
CuptiWrapper::ActivityGetNextRecord -> cuptiActivityGetNextRecord
As the cupti-api reference mentioned, the reason is lack of device memory,is there anyway to resolve this problem?
Or am I miss anything?
Look forward to your reply.
It will return 0 timestamp on some CUPTI_ACTIVITY_KIND_CONCURRENT_KERNEL kernels in my testing.
LOG:
2018-08-21 11:37:10.099749: W tensorflow/core/platform/default/device_tracer.cc:583] ActivityCallback kernel->start:0 kernel->end:0 kernel->deviceId:0 kernel->streamId:13 kernel->correlationId:8928781
2018-08-21 11:37:10.099759: W tensorflow/core/platform/default/device_tracer.cc:583] ActivityCallback kernel->start:0 kernel->end:0 kernel->deviceId:0 kernel->streamId:13 kernel->correlationId:8928789
Cupti func reference:
https://www.cs.rit.edu/~ark/cuda/doc/html/cupti/group__CUPTI__ACTIVITY__API.html
Inputs the previous record returned by cuptiActivityGetNextRecord and returns the next activity record from the buffer. If input value is NULL, returns the first activity record in the buffer. Records of kind CUPTI_ACTIVITY_KIND_CONCURRENT_KERNEL may contain invalid (0) timestamps, indicating that no timing information could be collected for lack of device memory.

Nagging Assignee @zheng-xq: It has been 15 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @zheng-xq: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ymodak: It has been 45 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

CC @nluehr
This looks like an issue with CUPTI. Nathan, could you help us triage this issue?
Thanks in advance!

I can reproduce this on CUDA 9.0, but it appears to be fixed in CUDA 10.0.

Thanks Nathan for the quick update. Closing this issue.


Additional capabilities to compile.py

Summary

Additional capabilities to compile.py

If a join (not online) references a group_by that has a backfill_start_date set, group_by will be materialized
If a join (not online) references a group_by that is online, group_by will be materialized

PR contains other minor doc and code fixes
Why / Goal

Above capabilities help keep the python configurations the JSON materialized files in sync
Test Plan

[x] Added Unit Tests
[ ] Covered by existing CI
[ ] Integration tested

Checklist

[ ] Documentation update

Reviewers
@pengyu-hou @hzding621 @donghanz @yuli-han @pkundurthy

@hzding621 addressed comments


Provide virtuality on the host_info endpoint.

MAAS currently collects whether or not a machine is running in a container or is a virtual machine using systemd-detect-virt during commissioning. If this information is made available via the LXD API MAAS will be able to display this information for LXD Pods.
Note: Running systemd-detect-virt shows lxc whenever running in a Snap. LXD should only show true if the host operating system is running in a container or virtual machine.

I'm not really sure why you care. For pods you already know their types through the LXD API.
So I guess it's about saving you one command during commissioning which I guess is ok.
I think we'll fold that into #7189 though.


Update the arcgis to 2.4.0

At the moment ArcGIS package is set to 2.3.1, we need to update it to 2.4.0, however there are changes to WebMap APIs that need to be updated in the code.

I have now updated the code base to support 2.4.0 but the new build itself is not well documented. There is just one issue re the cover that needs to be updated.


type role Ref nominal

Fixes #110

Do you know if these casting functions will be broken by this role annotation? To be clear, I think this is the right approach and I can fix them if necessary.

They will not break. A type role affects only what can be coerced with Data.Coerce (built-in class)


customize GOOS/GOARCH/etc

It would be nice to be override GOOS/GOARCH/etc variables when trying to understand non-portable code. Unfortunately, this can't be done via go-guru-command, because it gets shell quoted into a single argument.
I was able to get the effect I needed by changing (list go-guru-command ...) in go-guru-command to (list "env" "GOOS=openbsd" go-guru-command ...).

You can simply set the environment variables via M-x setenv and it'll work for all tools (gocode, godef, guru, ...)

Interesting, that seems like it should work. I'll reopen if not. Thanks!


Here is my step trying to reproduce CTRL，I want to know is there any wrong ？

          Here is my step trying to reproduce CTRL，I want to know is there any wrong ？

especially step2，and Is the config file ‘fsd_base_vehicle.yaml’ correct?
1.prepare waymo data(I only use part of waymo dataset)
1.1 use my python script to generate train.txt val.txt test.txt and idx2timestamp.pkl idx2contextname.pkl
Then cp train.txt val.txt test.txt to ./data/waymo/kitti_format/ImageSets/
cp idx2timestamp.pkl idx2contextname.pkl to ./data/waymo/kitti_format/
1.2 python tools/create_data.py --dataset waymo --root-path ./data/waymo/ --out-dir ./data/waymo/ --workers 128 --extra-tag waymo

Step 1: Generate train_gt.bin once for all. (waymo bin format).
python ./tools/ctrl/generate_train_gt_bin.py
generate file 'train_gt.bin'

python ./tools/ctrl/extract_poses.py
Generate file context2timestamp.pkl and pose.pkl

Step 2: Use ImmortalTracker to generate tracking results in training split (bin file format)
modify file ego_info.py and time_stamp.py like this:

Modify file waymo_convert_detection.sh like this:

then:
bash preparedata/waymo/waymo_preparedata.sh ~/dataset/waymo/waymo_format/
generate files like this :

bash preparedata/waymo/waymo_convert_detection.sh ~/dataset/waymo/waymo_format/train_gt.bin CTRL_FSD_TTA
Generate files like this:
In data/waymo/training/detection/CTRL_FSD_TTA/dets:

Modify file run_mot.sh like this:

Then:
bash run_mot.sh
generate file like this:

Step 3: Generate track input for training
modify file ‘fsd_base_vehicle.yaml’ like this: pred.bin was generated in step 2.

python ./tools/ctrl/generate_track_input.py ./tools/ctrl/data_configs/fsd_base_vehicle.yaml --process 1
generate files like this:

Step 4: Assign candidates GT tracks
python ./tools/ctrl/generate_candidates.py ./tools/ctrl/data_configs/fsd_base_vehicle.yaml --process 1

Step 5: Begin training
bash tools/dist_train.sh configs/ctrl/ctrl_veh_24e.py 1 --no-validate
Originally posted by @20210726 in https://github.com/tusen-ai/SST/issues/132#issuecomment-1688148061

Thanks for your interesting and detailed post. I will check once I am free.

@Abyssaledge @20210726
Hi, I follow the guide from the link,
I met the error when I train the model.
ries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
Traceback (most recent call last):
  File "/opt/conda/envs/sst/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/opt/conda/envs/sst/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/root/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/adapter/../../debugpy/launcher/../../debugpy/__main__.py", line 39, in <module>
    cli.main()
  File "/root/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/adapter/../../debugpy/launcher/../../debugpy/../debugpy/server/cli.py", line 430, in main
    run()
  File "/root/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/adapter/../../debugpy/launcher/../../debugpy/../debugpy/server/cli.py", line 284, in run_file
    runpy.run_path(target, run_name="__main__")
  File "/root/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_runpy.py", line 321, in run_path
    return _run_module_code(code, init_globals, run_name,
  File "/root/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_runpy.py", line 135, in _run_module_code
    _run_code(code, mod_globals, init_globals,
  File "/root/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_runpy.py", line 124, in _run_code
    exec(code, run_globals)
  File "/SHFP12/xiaoquan.wang/01_bev/SST/tools/train_track.py", line 231, in <module>
    main()
  File "/SHFP12/xiaoquan.wang/01_bev/SST/tools/train_track.py", line 221, in main
    train_model(
  File "/defaultShare/SHFP12/xiaoquan.wang/01_bev/SST/mmdet3d/apis/train.py", line 41, in train_model
    train_detector(
  File "/opt/conda/envs/sst/lib/python3.8/site-packages/mmdet/apis/train.py", line 170, in train_detector
    runner.run(data_loaders, cfg.workflow)
  File "/opt/conda/envs/sst/lib/python3.8/site-packages/mmcv/runner/epoch_based_runner.py", line 127, in run
    epoch_runner(data_loaders[i], **kwargs)
  File "/opt/conda/envs/sst/lib/python3.8/site-packages/mmcv/runner/epoch_based_runner.py", line 47, in train
    for i, data_batch in enumerate(self.data_loader):
  File "/opt/conda/envs/sst/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 517, in __next__
    data = self._next_data()
  File "/opt/conda/envs/sst/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1199, in _next_data
    return self._process_data(data)
  File "/opt/conda/envs/sst/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1225, in _process_data
    data.reraise()
  File "/opt/conda/envs/sst/lib/python3.8/site-packages/torch/_utils.py", line 429, in reraise
    raise self.exc_type(msg)
AssertionError: Caught AssertionError in DataLoader worker process 0.
Original Traceback (most recent call last):
  File "/opt/conda/envs/sst/lib/python3.8/site-packages/torch/utils/data/_utils/worker.py", line 202, in _worker_loop
    data = fetcher.fetch(index)
  File "/opt/conda/envs/sst/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 44, in fetch
    data = [self.dataset[idx] for idx in possibly_batched_index]
  File "/opt/conda/envs/sst/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 44, in <listcomp>
    data = [self.dataset[idx] for idx in possibly_batched_index]
  File "/opt/conda/envs/sst/lib/python3.8/site-packages/mmdet/datasets/dataset_wrappers.py", line 151, in __getitem__
    return self.dataset[idx % self._ori_len]
  File "/defaultShare/SHFP12/xiaoquan.wang/01_bev/SST/mmdet3d/datasets/waymo_tracklet_dataset.py", line 284, in __getitem__
    data = self.prepare_train_data(idx)
  File "/defaultShare/SHFP12/xiaoquan.wang/01_bev/SST/mmdet3d/datasets/waymo_tracklet_dataset.py", line 218, in prepare_train_data
    example = transform(example)
  File "/defaultShare/SHFP12/xiaoquan.wang/01_bev/SST/mmdet3d/datasets/pipelines/tracklet_pipelines.py", line 156, in __call__
    assert len(points_list) == len(tracklet) == len(pose_list)
AssertionError

This is my script.
DIR=ctrl
CONFIG=ctrl_veh_24e_demo
WORK=work_dirs
bash tools/dist_train.sh configs/$DIR/$CONFIG.py 4 --work-dir ./$WORK/$CONFIG/ --no-validate

@20210726  Greate introduction! The only thing I concern is the train_gt.bin in step2, which should be replaced with xxx.bin from our own detector when converting format for mot.

@20210726 Truly sorry for the late reply. I quickly go through your introduction. The pipeline is basically right, but one point need to be modified:
If you are generating the training data, you do not need the max_time_since_update: 10 in the tracking config, which will retain many boxes in the generated xx.bin file and is likely to lead to and oversize error of bin file.
max_time_since_update: 10 should be only adopted in generating training data.
Many thanks to all of you for the discussions!!!  @rockywind @SakuraRiven @20210726

@Abyssaledge  Are there some mistakes? 《If you are generating the training data, you do not need the xxx》《xxx should be only adopted in generating training data》

@SakuraRiven  The introduction above uses tracking config immortal_for_ctrl_keep_10.yaml to generate training data. This config enables max_time_since_update: 10, which means we will keep adding virtual boxes (at most 10) if the tractor loses an object. This is not wrong but it may lead to too many boxes in the training set, greatly slowing the processing.
Thus I recommend disabling max_time_since_update: 10 (set it to 0) when generating the training data.

If you are generating the training data, you do not need the max_time_since_update: 10 in the tracking config, which will retain many boxes in the generated xx.bin file and is likely to lead to and oversize error of bin file.
max_time_since_update: 10 should be only adopted in generating training data.

I see. So here should be "max_time_since_update: 10 should be only adopted in generating val and test data"?

@Abyssaledge  Another question. Do we have to perform extend_tracks.py for the training data generation? Considering that the tracklet anno in training set does not contain the first 10 frame, maybe it is not necessary?

No, you do not need extend_tracks.py for training. @SakuraRiven
Btw, if you use max_time_since_update > 0 or extend_tracks.py, please remember to remove the empty predictions. Otherwise, there might be some false positives, especially for pedestrian and cyclist.

Thanks for your interesting and detailed post. I will check once I am free.

Hi, thanks for your great work!
I have a question when I tried to reproduce the result. I followed steps to generated predicted tracks input in step 3. And in step 4, I used train_gt.bin to assign bbox to the predicted track. But seems like the predicted track from previous steps was already with ego motion, but the object position in train_gt.bin not. So the assignment results was weird (very low Average candidates per trk and very high Tracklet FP rate). I am wondering how to add ego motion into train_gt.bin so that the assignment could be correct or I did something wrong?
Thanks in advance!

Which version and slice of waymo data ,and i will reproduce ctrl result by your pipeline@20210726


Add"---cmd-opts" / "---dump-opts" for mysql and postgres

Add new tests for new args
Add tests for addtitional_opts in cmd and dump runners for mysql and postgres
update docs

Closes #38

To solve #38 this would need to also propagate into the normal execute/db_execute statements, since the concern was about SSL parameters. TODO.


DELETE /calendar/periods/{servicePointId}/period/{periodId}

Current: https://s3.amazonaws.com/foliodocs/api/mod-calendar/calendar.html

[x] Type out requests
[x] Handle requests
[x] Produce valid response
[x] Unit tests
[x] Integration tests

Forgot to tag but 987819f4384c8b261b5ce5a67cf21064e4ee250f added unit tests to complete this issue.


build: change example config to suit serverless platforms

Summary
Because we will only run the VSL core worker on Railway and Zeabur, we should provide the correct default configuration file:

Remove unused Arweave.
Use the official RSSHub endpoint.

Checklist

[x] The commit message follows Angular Contributing guidelines;
[x] Tests for the changes have been added (for bug fixes / features);

Does this PR introduce a breaking change?

[ ] Yes
[x] No

The current default configuration is https://github.com/RSS3-Network/Node/blob/develop/deploy/sample/config.sample.yaml


feat: implement get_pendingTransactions

Add support for eth_pendingTransactions with reference to https://github.com/moonbeam-foundation/moonbeam/issues/2184

Hi @virajbhartiya
Please, also add a typescript test. You can find an example: https://github.com/polkadot-evm/frontier/blob/master/ts-tests/tests/test-fee-history.ts


Add ValidateOption() API

Add ValidateOption() API which validates that all command line options are either SCons specified or specified by AddOption calls. It will error out if there are any unknown options.
Resolves Issue #4187
Contributor Checklist:

[x] I have created a new test or updated the unit tests to cover the new/changed functionality.
[x] I have updated CHANGES.txt (and read the README.rst)
[x] I have updated the appropriate documentation

There are AddOption calls in tool initialization. How will this interact with them?

There are AddOption calls in tool initialization. How will this interact with them?

Not sure how that's different from any other AddOption()?
If you call ValidateOptions() and you haven't yet specified an option which is on the command line you'll get an error.
Thus the requirement that you do all your AddOption()'s before callign ValidateOptions()

There are AddOption calls in tool initialization. How will this interact with them?

Not sure how that's different from any other AddOption()? If you call ValidateOptions() and you haven't yet specified an option which is on the command line you'll get an error. Thus the requirement that you do all your AddOption()'s before callign ValidateOptions()

The (conceptual, maybe not "real") difference is that AddOption hidden in a tool isn't necessarily something the user is aware of, so they go ahead and call the validator, and then tool initialization maybe happens later, and then their command line (using an option like --install-sandbox, or --disable-ninja) fails the validation?  I guess then you go back and change where you call the validator, so it's just a step in iteratively setting up your build and not a disaster...

Ahh. IC. I'll add some more language to docs.

After thinking about this, I believe the docs need to explain why you'd want to do this. After all, SCons already complains on bad options, so without reading the description in issue #4187 it's unlikely to be clear why this is needed. It's to provide a hook to be able to "fail fast" and have a chance to say something contextually appropriate rather than just that it's an unknown option, or get lost in some external configure check - most build systems won't need this, I assume.

Took another run at reorging the docs with some guidance from @mwichmann


(MINOR) New ingredient support and c2pa file formats

Adds support for many new formats
add ingredient_paths to support ingredients as files or JSON
Updates to README and schema
Add simple ingredient report
injects c2patool claim_generator

Codecov Report

Merging #111 (8ba2668) into main (e228213) will increase coverage by 2.30%.
The diff coverage is 68.29%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #111      +/-   ##
==========================================
+ Coverage   75.07%   77.38%   +2.30%
==========================================
  Files           3        3
  Lines         325      367      +42
==========================================
+ Hits          244      284      +40
- Misses         81       83       +2

Impacted Files
Coverage Δ

src/main.rs
74.45% <68.29%> (+3.55%)
:arrow_up:

... and 1 file with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


construct evm circuit test inputs from geth trace

still need to wait for https://github.com/gakonst/ethers-rs/pull/693 publicly released, as the same reason described in https://github.com/appliedzkp/zkevm-circuits/pull/226#issuecomment-994111114

still need to wait for gakonst/ethers-rs#693 publicly released, as the same reason described in appliedzkp#226 (comment)

We decided to import the ethers-rs dependency via git to use the latest commit from master to avoid waiting for a new release.  This change was applied in https://github.com/appliedzkp/zkevm-circuits/pull/226 which is already merged.  Could you please rebase against main to apply this change?  This should fix the github actions failures related to the yanked crate.


RTC-337

https://membraneframework.atlassian.net/browse/RTC-337?atlOrigin=eyJpIjoiZjRkNTEzMDliNmEwNDhkNDk5YWIxNzhkMzhmODQ2MWQiLCJwIjoiaiJ9

One more thing: we should edit /README.md, /engine/README.md (add mix test.file), and the moduledoc in /engine/lib/membrane_rtc_engine/engine.ex (section about Endpoints)

And as we discussed, let's include H264 and Opus parsers inside File endpoint


Export missing for @egjs/vue3-view360

Description
I recently tried to use @egjs/vue3-view360 to display an equirectangular panorama and found out that, after installing the latest version and running my vue3 application, it returns a console warning saying a couple exports are missing on ´@egjs/view360´:

getValidProps
generateCanvasKey

Steps to check or reproduce
Once @egjs/vue3-view360 is installed, run npm run serve to start your vue application and you should get the following warnings:
 warning  in<EMAIL_ADDRESS>"export 'generateCanvasKey' was not found in '@egjs/view360'
 warning  in<EMAIL_ADDRESS>"export 'getValidProps' was not found in '@egjs/view360'
 warning  in (webpack)/buildin/global.js

I also navigated to the node_modules egjs files and found this on<EMAIL_ADDRESS>

Hello @si7o!
It looks like there was a mistake setting the correct dependency version in vue3-view360.
I've just updated its version to 3.0.1 to fix this issue, please try that :)

It works now. Thank you for fixing it so fast :)


test-branch/execute-job/wrong-commit-sha-on-pr/03d82615-ff81-4f89-8fb6-b1d90b1a9943

PR for testing 244ad8c58a7c61e69ecc0d10e4badd88277c783c

/canonical/self-hosted-runners/run-workflows 931ad21dd9ace68aaa0a7d341e94de96ad93fa6b


Can't install Brunel

When i tried to install brunel using "[sudo] pip install brunel" it comes back with "Command "python setup.py egg_info" failed with error code 1".
Could someone please advise on what to do?
Thank you!!

Hello.  What version of python are you running?  Also what is your OS?


parseZone() seems to have unexpected handling of ambiguous input

Describe the bug
Based on the documentation:

moment.utc(...) is utc mode. Ambiguous input is assumed to be UTC. Unambiguous input is adjusted to UTC.
moment.parseZone() keep the input zone passed in. Ambiguous input is assumed to be UTC.

Since for ambiguous input the wording is exactly the same, I assumed they would produce the exact same result. For example I expect this line of code to return true:
moment.utc('1900-01-01').isSame(moment.parseZone('1900-01-01'));

However, when running this line of code with system / browser timezone set to Asia/Shanghai, Asia/Kolkata, Europe/Moscow, or perhaps many other ones, the result would be false.
Also noting that more modern time like 2000-01-01 doesn't have this issue.
This looks like a bug to me, since the documentation indicates the result should be agnostic to local timezone. If this is not a bug, I would appreciate any help to understand the reason, and perhaps have the quirk documented somewhere.
To Reproduce
Run moment.utc('1900-01-01').isSame(moment.parseZone('1900-01-01')); when local timezone is Asia/Shanghai. You can either change OS timezone or use Chrome dev tools to override.

Expected behavior
This line moment.utc('1900-01-01').isSame(moment.parseZone('1900-01-01'));  should return true, in other words, moment.utc and moment.parseZone should have the same output when input is offset-ambiguous.
Screenshots

Desktop (please complete the following information):

OS: Mac
Browser: Chrome
Version: Version 117.0.5938.149 (Official Build) (arm64)

Smartphone (please complete the following information if applicable):
I didn't test on mobile.
Moment-specific environment

The time zone setting of the machine the code is running on: Asia/Shanghai
The time and date at which the code was run: now
Other libraries in use (TypeScript, Immutable.js, etc): N/A, I can repro on momentjs.com in Chrome console

Please run the following code in your environment and include the output:
console.log((new Date()).toString())
console.log((new Date()).toLocaleString())
console.log((new Date()).getTimezoneOffset())
console.log(navigator.userAgent)
console.log(moment.version)

Fri Oct 13 2023 01:59:51 GMT+0800 (中国标准时间)
2023/10/13 01:59:51
-480
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
2.29.4

Additional context
N/A

If you are running the code in Asia example I am running in INDIA, moment.js will use the Asia/Kolkata timezone. Therefore, the moment.parseZone() function will parse the date string 1900-01-01 in Asia/Kolkata time, which will create a Moment object that represents the date and time 1900-01-01 05:30:00 UTC.
he moment.utc() function will create a new Moment object in UTC time, which will create a Moment object that represents the date and time 1900-01-01 00:00:00 UTC.
so the output would be false

Thanks @shridhar2656. What your experiment shows is that parseZone will parse ambiguous inputs in local timezone, that contradicts with the documentation:

The doc was updated in 2020 specifically to change from mentioning local mode to UTC: https://github.com/moment/momentjs.com/commit/af673359476388d94cd36807d157a525037ccfc6.


Improve log readability PR1

@varunsh-coder I will be putting in multiple PRs regarding this, the changes in this are the safe ones. I have made some other changes as well that need to be tested, so I will add that in the next PR

@arjundashrath can you please create the PR in the rcbranch?


Add dictionary support for C data interface

Which issue does this PR close?

Closes #1397.
Rationale for this change

Currently the Rust implementation of C data interface doesn't support dictionary type yet, which is necessary if we want to pass data between Rust and other languages such as Java/C++.
What changes are included in this PR?

Added dictionary support in Rust FFI.
Added roundtrip tests within Rust (i.e., Rust -> Rust -> Rust)
Added roundtrip tests between Python and Rust

I kept the DictionaryArray untouched so the dictionary (i.e., values) is still stored as the only child of the ArrayData it is associated to.
Are there any user-facing changes?
Yes, now we can use C data interface with dictionary type. No API change.

Codecov Report

Merging #1407 (b86a377) into master (1fbe618) will increase coverage by 0.02%.
The diff coverage is 80.95%.

@@            Coverage Diff             @@
##           master    #1407      +/-   ##
==========================================
+ Coverage   83.13%   83.16%   +0.02%
==========================================
  Files         182      182
  Lines       53321    53382      +61
==========================================
+ Hits        44330    44394      +64
+ Misses       8991     8988       -3

Impacted Files
Coverage Δ

arrow/src/datatypes/ffi.rs
73.65% <68.75%> (+2.80%)
:arrow_up:

arrow/src/ffi.rs
85.71% <90.19%> (+1.09%)
:arrow_up:

arrow/src/array/ffi.rs
100.00% <100.00%> (ø)

arrow/src/datatypes/field.rs
53.79% <0.00%> (-0.31%)
:arrow_down:

parquet_derive/src/parquet_field.rs
65.98% <0.00%> (-0.23%)
:arrow_down:

arrow/src/array/array_binary.rs
93.28% <0.00%> (+0.05%)
:arrow_up:

arrow/src/array/transform/mod.rs
86.43% <0.00%> (+0.11%)
:arrow_up:

arrow/src/array/equal/mod.rs
93.24% <0.00%> (+0.33%)
: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 1fbe618...b86a377. Read the comment docs.

cc @alamb @jorgecarleitao @kszucs could you help to review this? thanks!

We should also be able to pass is_ordered flag via the C data interface, but it appears that property is not supported in the Rust implementation yet (perhaps it should be part of DataType::Dictionary).

Yea, I will review this PR. Thanks @alamb @sunchao

Yes, now we can use C data interface with dictionary type. No API change.

FFI_ArrowSchema.try_new is a public function, so I wonder this should be an API change?

Thanks @jorgecarleitao @alamb @viirya ! I've addressed your comments. Let me know if you have more feedback. Otherwise I'll merge this tonight.

Merged, thanks!


how to use with cocoapods?

Cocoapods sets its own config file Pods-Pairs.debug, so we can't use the custom UnitiyConfig.xcconfig, so i think we have to change UnitiyConfig to extend   Pods-Pairs.debug but i have no clue how to do that. Any advice?

Try marge Pods-Pairs.debug to UnitiyConfig.xcconfig.

this seems to work:
#include "Pods/Target Support Files/Pods-Pairs/Pods-Pairs.debug.xcconfig"

Hey,
I think I am having the same issue. My react native project is using cocoapods and when I change the config to UnityConfig.xcconfig I am getting this error:
diff: /Podfile.lock: No such file or directory
diff: /Manifest.lock: No such file or directory
error: The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation.

Any idea how to fix this ?

@macrozone : Where did you add this #include line ?
Thanks


Previous.current is confusing

Describe the feature in detail (code, mocks, or screenshots encouraged)
previous.current suggests that it's the current value, not the retained one. While at first it doesn't really make sense as the current value can be read from the original store, it's still a viable source of confusion as one might think it's exposed for debugging purposes (e.g. debugging reactivity problems with complex nested objects).
I recommend changing it to previous.value.  While other alternatives like .retained, .old, or even .previous might seem more descriptive at first, we have to consider that in most cases the Previous instance is not named previous, but something else. Try to use the property name with some possible object names: previousCursorPosition.value, oldSelectedItem.value, previousInputContent.value
What type of pull request would this be?
Enhancement
Provide relevant links or additional information.
No response

Thanks for opening this issue!
The decision to use .current is part of a broader pattern across Svelte's APIs, where .current consistently represents "the current value of this thing at this moment in time." This pattern appears in other Svelte utilities like reactive window values (innerWidth.current, scrollY.current), MediaQuery, and more.
While I understand that .value might feel more intuitive in isolation, changing it would create an inconsistency with related APIs. When using this utility, I've found it helpful to use variable names that make the intent clear, for example:
const prevCount = new Previous(() => count)
const prevValue = new Previous(() => value)

This way the variable name itself communicates that we're dealing with a previous value, while the .current accessor remains consistent with Svelte's other APIs.
For these reasons, we'll keep the existing .current convention.


Add example for array and composite type columns

Adds examples to the information added in #501.

Cool, I like it :)


[Ok] Add resolveDns

Hi, I need resolveDns function.
Where should I add my test, can my test depend on a real external DNS server, or should the DNS ser er should be mock ?
how can I start the tests ?

 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.

@UrielCh thanks! I think using a real one is fine for now.

The commands to use to run the tests for all workspaces are:
# npm install
npm i  --ignore-scripts
# build
npm run --silent build --workspaces
# test
npm run --silent test --workspaces

To format and lint:
deno fmt
deno lint

I will add contributing instructions.

fmt + lint done

I'm not sure that my test has been executed.

I create a src/deno/stable/functions/resolveDns.test.ts
because I found a
I create a src/deno/stable/functions/run.test.ts
but none src/deno/stable/functions/run.test.ts is not called by your test command.
I also see that src/deno/stable/functions/run.test.ts use Deno.test and import file dependent with .js extension.
so can you tell me where and how to execute my test file.

@UrielCh sorry, this repository is not fresh in my memory. It looks like ./packages/shim-deno/tools/run_tests.js reads from ./packages/shim-deno/tools/working_test_files.txt so I believe you just need to add the test file path to that txt file.

test enable with extra doc.
Ready to merge.

Please can you merge my PR?
I need it to convert and publish my first deno project.


[DO NOT MERGE] Add a new assisted digital satisfaction survey

This survey is specifically about help with fees and we only want to show
it on certain done pages.  For now this is a bit experimental, so we don't
want to add it to the documents themselves as a toggle selectable in
publisher.  We've left it as a hardcoded list in
lib/assisted_digital_satisfaction_survey.rb.
Note that the backend for this is handled by the feedback app (see https://github.com/alphagov/feedback/pull/179 and https://github.com/alphagov/feedback/pull/189 and https://github.com/alphagov/feedback/pull/190 - all of these should be merged and deployed before this is).
Trello: https://trello.com/c/kZCX6dGB/53-assisted-digital-support-on-done-page-survey

Flagged as DNM because we should deploy the feedback PR first, otherwise folk might get routing errors.

Is this still needed?

Yup, getting product review on integration - hopefully deploying soon!

New commits added to reflect feedback on original survey.

This is ready to go as we have go-ahead from the depts using the services, and all dependant PRs on other services are merged, but we can't merge it until after the election.

Removed DNM as we're finally ready to ship this thing!


Tooltip for feature on map WPF

Is there a way to add tooltip to the features displayed on the map instead of label?
WPF provides an event for mouse enter which can be used to display tooltip. But, the argument of the event handler doesn't provide the GetMapInfo() function as provided by the mouse click event arguments in WPF.

Perhaps you could take a look at Callout, otherwise you have to create something like this yourself by call GetMapInfo on move move.


Fix deprecation and bump dependencies

It seems that there's an issue with production build. May be same cause as described here https://dev.clojure.org/jira/browse/CLJS-2392

Sorry, cant merge this with a broken build.

Could you also please rebase this on top of current master? Commit 5471d25 should be after latest merge commit that is on master.

Sounds like a plan, good luck! :)
On Sun, Apr 8, 2018, 14:49 Alex<EMAIL_ADDRESS>wrote:

@Alexx-G commented on this pull request.
In project.clj
https://github.com/Gonzih/cljs-electron/pull/19#discussion_r179957267:

@@ -3,13 +3,13 @@
:url "https://opensource.org/licenses/MIT"}
:source-paths ["src"]
:description "A hello world application for electron"

:dependencies [[org.clojure/clojure "1.8.0"]

            [org.clojure/clojurescript "1.9.542"]

            [figwheel "0.5.10"]

:dependencies [[org.clojure/clojure "1.9.0"]

            [org.clojure/clojurescript "1.10.238"]

It works with 1.9.542, I'm gonna try to find the root cause. It would be
nice to get it working with 1.10.x since it improved build time
significantly.
If it's a regression of 1.10.x, I'll downgrade cljs.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Gonzih/cljs-electron/pull/19#discussion_r179957267,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQQI6PIeOdZGw47V6rvMRV355MNgJiRks5tmlvRgaJpZM4TLijr
.

As I could see from the build error could it be due to drop of support for JDK 7 in the latest binary release ? Issue : https://github.com/google/closure-compiler/issues/2672 . I am still confused over why OracleJDK 7 succeeds though. Feel free to ignore this if I am wrong.

Oh yeah, that might be related. Ugh in that case removing Java 7 from travis.yml might make sense.

I've left only oraclejdk8 in travis config.
Also, I've had to use additional externs files for node's process and some closure compiler warning (as somebody recommended in slack).
It works fine for me with both dev and release builds.

I've pushed another commit which disabled process-shim and allowed to drop node process extern file.
I didn't know about this option which caused the issue with js/process, https://clojurescript.org/reference/compiler-options#process-shim

Thanks


refactor: refactor tests to maintain a single naming convention

Resolves #480

@pwilson77
thank you for the PR

This is totally my fault but I meant to refactor test names with low dashes like testConstructor_ShouldRevert_WhenBurnFeeIsHigh. Could you please refactor code with low dashes?
Pls merge the development branch (there is a fix for CI build there)
Pls fix the conflicts

oh alright will make those fixes

Hi @rndquu  could u review I made the changes but the same CI checks keeps failing

Hi @rndquu could u review I made the changes but the same CI checks keeps failing

Hi, thank you for the update, I will check it today

@rndquu I just told CI to re-run please recheck soon!

@pwilson77

Pls merge the latest updated from the development branch
Some of the tests are failing because of a string mismatch, ex: https://github.com/ubiquity/ubiquity-dollar/pull/532/files#diff-827ff987b6797b6cac2dfa68cd5920a68c648799d2cb37e5582ceb4a0379d156L31 => Credit NFT manager  vs CreditNFT manager
When test starts with testFail then it is expected to revert (this is a special forge syntax  https://book.getfoundry.sh/forge/writing-tests). When you rename, for example testFailWithdraw to testWithdraw, then testWithdraw is gonna fail because it is not expected to revert but reverts nevetheless. Simply put you may omit renaming tests that start with testFail, we're in the process of getting rid of all of them.

Oh ok , making those changes

Hi @rndquu, the CI checks have passed now, could u check the PR

We just renamed NFT to Nft in our codebase (camelCase) once you do that this can auto-merge.

We just renamed NFT to Nft in our codebase (camelCase for variables, functions, and file names) once you do that this can auto-merge.

This is not described in the original issue so I guess we can skip this requirement for now. I can do it later.
Overall the PR looks good so @pwilson77 pls fix the conflicts so that this PR could be merged.

Ok fixing the conflicts then

Hi @rndquu, fixed the conflicts and I had to do the renaming because I had CI errors, could u merge I am not sure why the auto-merge didn't work

@pavlovcik seems fine to me, ready to be merged


[Rotate] Non-mutating variants for rotating APIs

This is an implementation of non-mutating variant for rotate(toStartAt:) and rotate(subrange:toStartAt:)
that are rotated(toStartAt:) and rotated(subrange:toStartAt:) respectively that results in a RotatedCollection view.
The useful aspects of such API is that when preserving the original collection, the mutating version requires a copy. Also, when base conforms to RandomAccessCollection calling rotated is O(1) time and elements at each position are also computed in constant time.
Couple of other points to note:

Rotate.md documentation was updated with new variants. Not sure if was worth a new file both for implementation or docs. So opted to keep everything together.
Tests to ensure that both mutating and non-mutating variants produce the same result.
There is also a point worth discussing together with this, that is #165, if that is a useful API modification and if both PRs are useful additions we can land together.

Let me know what you think @natecook1000 @timvermeulen @lorentey
Checklist

[x] I've added at least one test that validates that my change is working, if appropriate
[x] I've followed the code style of the rest of the project
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary

A quick bench about difference in perf for a single all elements iteration just out of curiosity
var benchmark = Benchmark(title: "Rotated Algorithm")
let inputGenerator: (Int) -> [Int] = { size in
  return (0..<size).map { $0 }
}
benchmark.registerInputGenerator(inputGenerator)

benchmark.add(
  title: "In place rotation 25%",
  input: [Int].self
) { input in
  var mInput = input
  let count = mInput.count / 4 // 25% rotation
  return { timer in
    mInput.rotate(toStartAt: count)
    for value in mInput {
      blackHole(value)
    }
  }
}

benchmark.add(
  title: "Rotated View 25%",
  input: [Int].self
) { input in
  let count = input.count / 4 // 25% rotation
  return { timer in
    for value in input.rotated(toStartAt: count) {
      blackHole(value)
    }
  }
}

benchmark.main()


Edit Elevator preset

Remove wrong field "maxweight" which is used for "legal access restriction for vehicles that exceed the specified actual weight".
The tag maxweight is well described on Wiki and there is no mention about using it for elevators.
https://wiki.openstreetmap.org/wiki/Key:maxweight

@maro-21 Thanks, but just because the wiki doesn't mention a usage doesn't mean it's wrong. I see elevators as part of the accessible routing network. Many even support vehicles. Elevators always have a legal maximum weight posted in them, at least in the US, which is akin to a max weight sign along the highway.
Let us know if this is causing problems for data consumers, but otherwise I'm certain this is fine.

But we can't use the same tag for two different things.
As you can see on the screenshot, the description and image doesn't fit to elevator maximum weight.
You previously said that there should be community consensus to add or remove something from iD preset.
If there was consensus, there would be mention on the Wiki.

But we can't use the same tag for two different things.

This actually happens all the time. A few examples are ele, height, width, access, and lit, which encode the same information on all kinds of different types of features.
The wiki also says "a number of navigable structures may be tagged with a weight restriction", and then gives examples such as railways, helipads, roller coasters, and zip-lines in addition to roads. An elevator is a navigable structure too.

As you can see on the screenshot, the description and image doesn't fit to elevator maximum weight.

I'd recommend updating these and the wiki page to reflect broader usage patterns.

If there was consensus, there would be mention on the Wiki.

Unfortunately, we can't make this assumption about the wiki. It's written be a small number of volunteers and is often outdated or incomplete.

You previously said that there should be community consensus to add or remove something from iD preset.

Community consensus is just one of the factors, but yes, if there is actually controversy here then I'm happy to change this until it's sorted out. But I don't see evidence of controversy.


feat(dp): Regular Expression Matching

Coverage remained the same at 100.0% when pulling fec4289aec7c9ef6e587c06de2545fc2729188df on regular-expression-matching into 9c02452efdf1bdd9cdfdb1b1f1938e9b97a69aa9 on master.


Page class _context is public

Now that _parent is a thing of the past, we will see many extensions break. Namely subscribing to initaliseAdminPageHead and using:
$page = $context['parent']->Page;

This should go into the 2.3 migration guide as being changed to:
$page = Administration::instance()->Page;

Since the delegate no longer contains the page as it is globally available via the above accessor.
However there is still a need to access a page's "context" which is currently done via:
$page->_context
The naming of this suggests to me it should really be private but having migrated from PHP4 where private did not exist, this member is now erroneously public. Now, the information within _context can be obtained by calling:
Administration::instance()->getPageCallback()

(Not sure why it is called "callback". Callback from where?) However, we found some time ago that calling this without first checking the type of the (instanceof contentPublish) would throw an error:
Cannot request a page callback without first specifying the page.

We never got to the bottom of this.
So my issues are:

The change to this delegate is missing from the migration guide (loads of extensions use it, so it should be explicit)
Should $_context be public, or should we get grabbing context via getPageCallback() instead?

The change to this delegate is missing from the migration guide (loads of extensions use it, so it should be explicit)

It was mentioned in the Removed section, but I've updated it to be more helpful

Should $_context be public, or should we get grabbing context via getPageCallback() instead?

The naming convention suggests it should have an accessor (Frontend::Page()->_param is another culprit).
That error arises because the Administration instance might not have a Page attached to it (to be honest, I'm not sure why this would be the case, I don't recall that issue). However in the documentation is also states that you can pass the URL to the getPageCallback() as a string:
* @param string $page
*  The full path (including the domain) of the Symphony backend page

Anyway, I'll add accessors, and note the deprecation of accessing these properties directly.

Awesome, thanks. Just need to add these into the changelog and migration guide before closing :-)

Done and done.


Increase default IO timeout submitted to NVMe devices

What this PR does / why we need it:
For EC2 m5/c5 families, EBS volumes are exposed as NVMe block devices.
If there's a delay for AWS EBS to respond, we can reach NVMe IO timeout.
When this happens, the disk is re-mounted as read-only. The default is 30 seconds.
AWS recommends to set it as high as possible. The newest Amazon Linux has this configured too.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html#timeout-nvme-ebs-volumes
For the kernel version, the highest value is 255.
Which issue(s) this PR fixes:
https://github.com/kubernetes/kops/issues/5694
Release note:
Increase nvme io timeout to better support EC2 c5/m5 instances.

@kubernetes/kube-deploy-reviewers

/assign justinsb


Fix some minor bugs related to 1-wavelength Rainbow objects.

The changes include:

A simple wrapper for .get_integrated_lightcurve() to produce a wavelength-integrated light curve as a 1-wavelength Rainbow.
Use wavelength edges to improve .imshow extents. Now it can handle 1-wavelength Rainbows.

@catrionamurray , this fixes a few of the bugs we saw with dealing with single-wavelength Rainbow objects. They should now behave pretty similarly to normal ones. Doing so actually fixed some subtle bugs that I hadn't noticed in how imshow works!


[DO-NOT-MERGE][SPARK-33913][SPARK-33921][BUILD] Upgrade kafka to 2.7.0 and Upgrade Scala version to 2.12.12

What changes were proposed in this pull request?

This patch proposes to upgrade Kafka version to 2.7.0 and Scala 2.12 patch version to 2.12.12.
Why are the changes needed?

To catch up with latest Kafka bug fix and features: https://downloads.apache.org/kafka/2.7.0/RELEASE_NOTES.html
To catch up with bug fix and improvement of latest Scala 2.12 patch.
https://github.com/scala/scala/releases/tag/v2.12.11
https://github.com/scala/scala/releases/tag/v2.12.12

Performance improvements in the collections library, the compiler
Fix memory leak in runtime reflection's TypeTag caches
Fix some toX methods that could expose the underlying mutability of a ListBuffer-generated collection
ASM was upgraded to 7.3.1, allowing the optimizer to run on JDK 13+

Does this PR introduce any user-facing change?

No
How was this patch tested?

Unit test.

Test build #133412 has started for PR 30939 at commit 670ec1d.

Test build #133412 has finished for PR 30939 at commit 670ec1d.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/133412/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38003/

Test build #133413 has started for PR 30939 at commit 2443950.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38004/

Test build #133413 has finished for PR 30939 at commit 2443950.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/133413/

Yea, it's the same issue as https://github.com/embeddedkafka/embedded-kafka/issues/202. We need to bump Scala patch version to match Kafka's.

Created #30940 for upgrading Scala 2.12 patch version.

Hi, @viirya . Sorry, but, are you sure about Scala 2.12.12?
I commented on your original Scala 2.12.12 PR, too.
* [#30940 (comment)](https://github.com/apache/spark/pull/30940#issuecomment-751581096)

Yea, I just saw it. If we don't want Scala 2.12.12, seems we cannot upgrade Kafka 2.7.0 too: https://github.com/apache/spark/pull/30940#issuecomment-751583360.

I'm going to see Jenkins test to verify it, although I already experimented locally.

No, @viirya . We detected the issues six month ago and made a Spark-side adaptation via SPARK-32436 on July 2020.
Please see the discussion here for the technical details and Scala side bug IDs. AFAIK, the bug is in Scala 2.12.12 and we are waiting for 2.12.13 .

https://github.com/apache/spark/pull/29231

cc @srowen and @mridulm who were together on the original PR for Scala 2.12.12 bug fix.

No, @viirya . You may not notice the bug, because we detected the issues six month ago and made a Spark-side adaptation via SPARK-32436 on July 2020.
Please see the discussion here for the technical details and Scala side bug IDs. AFAIK, the bug is in Scala 2.12.12 and we are waiting for 2.12.13 .
* #29231

I'm reading https://github.com/scala/bug/issues/12096. I understood Scala 2.12.12 was skipped now. I just meant if we cannot upgrade to Scala 2.12.12, then upgrading Kafka 2.7.0 is blocked by it.
Then we may also wait for next Kafka version which uses Scala 2.12.13 (if there is).

In short, the Scala compiler had a critical bug.

scala/bug#12096
scala/bug#12002

Got it, @viirya . For testing purpose, there is no problem.

Test build #133425 has started for PR 30939 at commit 91a6ccd.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38016/

Right, I think we'd just have to skip this for now.

Test build #133425 has finished for PR 30939 at commit 91a6ccd.

This patch fails from timeout after a configured wait of 500m.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/133425/

Thanks for discussion.

FYI, we adjusted the optimizer configs for Kafka to avoid the exact Scala patch version dependency issue: https://github.com/apache/kafka/pull/10174
It will be part of Kafka 2.8.0.

Thank you, @ijuma .


bump and publish version 0.0.1

Cleaned up README.md, added standard dual license, and setup the version and tags to publish 0.0.1

That dual license setup is starting to become standard practice in some OSS communities such as Rust and most of PLN/IPFS libraries. The reasoning stems (in some part) from issues with patent granting. The general description (stolen from the internet somewhere) is:
Requiring both MIT and Apache 2.0 as inbound licenses for contributions means that anyone making a contribution is providing the Apache 2.0 patent grant. And then having MIT and Apache 2.0 as outbound licenses means our libraries provide widespread compatibility with all sorts of other FOSS licenses, including GPLv2. Actually, we could just scrap the two and use something like https://opensource.org/licenses/BSDplusPatent instead, which looks quite good.
For further reference, here's an issue from the IPFS community that reflects the thinking around the dual licensing setup: https://github.com/ipfs/js-ipfs/issues/2624.

cool, thanks for the brain dump. sounds good to me.

Should we switch the license here before publishing?

I think what you did looks good
On Nov 8, 2022, 5:11 PM -0800, Joe Wagner @.***>, wrote:

Should we switch the license here before publishing?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because your review was requested.Message ID: @.***>


Port to Spark 1.3.0

I would very much like to use the new DataFrame work so I'm attempting to build this for Spark 1.3.0
I'll be happy to submit a Pull Request once I get it building.
Currently getting the following error:
[info] Compiling 2 Scala sources to /Users/antony/home/src/spark/spark-redshift/target/scala-2.10/classes...
[error] /Users/antony/home/src/spark/spark-redshift/src/main/scala/com/databricks/examples/redshift/input/RedshiftInputFormat.scala:109: value attr is not a member of String
[error]         field.name.attr.cast(field.dataType).as(Symbol(field.name))
[error]                    ^

The types seem to have moved around some in the change from 1.2 to 1.3.0.  It looks to me the like the type of field.name is String in both 1.2 and 1.3.0, so I am guessing there's some kind of implicit conversion that was visible in 1.2 that's disappeared or moved in 1.3.0.  If anyone can offer a comment on where to look to understand what field.name.attr was doing or suggest how to resolve, I'll do the legwork to try and fix.

try wrap it with col
i.e.
import org.apache.spark.sql.functions.col

col(field.name).cast(field.dataType).as(field.name)

Great, thanks Reynold!  That was it.  Pull request is here:  https://github.com/databricks/spark-redshift/pull/7
Let me know if you'd like me to make any changes to the PR.

PR was merged.


Polygonal shape with active "elevation" and vector drawable

<de.hdodenhof.circleimageview.CircleImageView
        android:id="@+id/select"
        android:layout_width="56dp"
        android:layout_height="56dp"
        android:layout_gravity="center"
        android:src="@drawable/ic_check_circle_24dp"
        android:elevation="8dp"/>

When elevation 0 or image not vector - shape is round.

As stated in the FAQ vector drawables shouldn't be used with CircleImageView - it's a bit of a surprise it works at all. Not sure where the octagon come from though, but if it works with a non-vector drawable, it's out-of-scope of this library.

@hdodenhof It works with a non-vector drawable. It is a pity that vector images are not officially supported. I had no performance issues when using vector icons with CircleImageView .