Update README.md

I added the instructions to Readme, that allows people to clone and open the project in a browser

makes sense!


Create dark button style for 'main page' main section navigation

As per mock up:

I think this is fixed in #72


SystemDiagnosticsDebugDiagnosticBase should check the method name before calling GetSymbolInfo

GetSymbolInfo is a (relatively) expensive call that appeared while investigating #732. We should check the text name of the method being invoked before calling GetSymbolInfo to filter out the vast majority of calls.

Grabbed


fix: upgrade jxboot-helmfile-resources

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jstrachan: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
722026c66897e6b0e373ed982dee12931d8afd68
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/retest

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
722026c66897e6b0e373ed982dee12931d8afd68
link
/test gsm

vault
722026c66897e6b0e373ed982dee12931d8afd68
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/test vault


0.74.1 - http component start failed with cors_allowed_origins configed

Home Assistant release with the issue:
0.74.1
Last working Home Assistant release (if known):
0.74.0
Operating environment (Hass.io/Docker/Windows/etc.):
Component/platform:
https://www.home-assistant.io/components/http/
Description of problem:
http start failed
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
http:
  api_password: some_password
  cors_allowed_origins:
    - https://google.com
    - https://home-assistant.io

Traceback (if applicable):
2018-07-24 20:02:02 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/components/http/__init__.py", line 132, in start_server
    await server.start()
  File "/usr/src/app/homeassistant/components/http/__init__.py", line 284, in start
    await self.app.startup()
  File "/usr/local/lib/python3.6/site-packages/aiohttp/web_app.py", line 278, in startup
    await self.on_startup.send(self)
  File "/usr/local/lib/python3.6/site-packages/aiohttp/signals.py", line 35, in send
    await receiver(*args, **kwargs)
  File "/usr/src/app/homeassistant/components/http/cors.py", line 53, in cors_startup
    cors.add(route)
  File "/usr/local/lib/python3.6/site-packages/aiohttp_cors/cors_config.py", line 263, in add
    return self._cors_impl.add(routing_entity, config)
  File "/usr/local/lib/python3.6/site-packages/aiohttp_cors/cors_config.py", line 137, in add
    routing_entity, parsed_config)
  File "/usr/local/lib/python3.6/site-packages/aiohttp_cors/urldispatcher_router_adapter.py", line 240, in set_config_for_routing_entity
    resource))
ValueError: CORS is already configured for <PlainResource  /auth/token> resource.

Additional information:
I've updated to the latest Docker Image 0.74.1, but after the update HA wasn't working anymore (Frontende couldn't be reached. After a roll-back to 0.74.0 it was fine again.
Not so critical to me, but I though I share it here.

In 0.74.1, we auto loaded auth component with http component cause this issue. I can reproduce it.

Version 0.74.0 is the last build which is working for me, if I update to the latest build, I get a HTTP 502 bad gateway error. What changed since v 0.74.0 in terms of that?


remove border of qrcode image

toDataURL produce a image with a black border in Android and a white border in iOS, and this will make the image cannot be recognized by qrcode scanner. so I removed it.

Thanks. I just forgot why I add the +2 adjustment in the first place lol.


AKI EoD profile is different than live

General information
Project issue is for:
(Server)
The actual EoD from live is a quite different than AKI.
The ammo is exact the same but in the base of the start items is different.
The equipped inventory is the same as before.

Attachments

EoD_Inventory_Bear.png (1973 KiB)
EoD_Inventory_USEC.png (2147 KiB)

Originally written by ShadowXtrex

Are these screenshots from live?

Originally written by chomp

Are these screenshots from live?

Yes! from my profile and a friend
here is a streamer who show the initial stash from 1 wipe day too https://youtu.be/12LpGZ6pWWU?t=189
If you need something more please tell me

Originally written by ShadowXtrex

Would it be possible to dump these profiles from live?

Originally written by chomp

Would it be possible to dump these profiles from live?

Tell me how

Originally written by ShadowXtrex

Updated Bear EoD profile to match live: https://dev.sp-tarkov.com/SPT-AKI/Server/commit/6d2c17596bbc3f78469a00a39ae5c309e86a2f08
Only USEC left to update

Originally written by chomp

Updated USEC profile: https://dev.sp-tarkov.com/SPT-AKI/Server/commit/f73802ec1792cf8537be961142073eca5e0a4494

Originally written by chomp


Please allow loadbalancer SKU to be set via an annotation instead of only cloud_config

Currently the only way to set this is by setting the cloud_config to have the sku set to standard. I'd like to be able to set this as an annotation instead of globally only.

I'm afraid this is not possible now, because a virtual machine (with one network interface) on Azure could only be added to one public LB and one private LB.


Remove app proxy env

/e2e

Codecov Report

Merging #154 (ac898c0) into main (fb9b42c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #154   +/-   ##
=======================================
  Coverage   25.13%   25.13%
=======================================
  Files           1        1
  Lines         187      187
=======================================
  Hits           47       47
  Misses        134      134
  Partials        6        6

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 fb9b42c...ac898c0. Read the comment docs.


Hand tracking blocking plane

In the Oculus Interaction SDK there is the function to stop the ghost hand mesh passing through the mesh of buttons and UI using the surface plane. Is there a way to implement this for Avatars hands too?

There is! The Avatars in this project are using a body tracking class that forwards the hands/controllers from OVRInput. What you want is to use a body tracking class that forwards the SyntheticHands from ISDK.
For reference, that's how the rig is set up in Decommissioned. You can see the body tracking classes here.
The feature you're referring to specifically is called Touch Limiting. It's not currently used in Decommissioned, but if you add the HandPokeInteractorVisual component to the rig, it should work.

Excellent thanks I will try this out


ghost:3-alpine No create user "flow" on first launch

Hi,
When I'n running the ghost:3-alpine container I would expect that the first time I'm entering the site, I have the option to create a user.... but I don't. And I also don't see any button / link / etc. to login (I don't know if a default user is created)....
See below:

docker-compose.yml
container startup log
the page Im getting.

What am I doing wrong?
Sander
  blog:
    image: ghost:3-alpine
    container_name: blog
    restart: unless-stopped
    ports:
      - 8888:2368
    networks:
      - docker
    volumes:
      - ghost:/var/lib/ghost/content
    environment:
      - url=http://super:8888/
      - database__client=mysql
      - database__connection__host=mariadb
      - database__connection__user=ghost
      - database__connection__password=${ROOT_PASSWORD}
      - database__connection__database=ghost

[2020-01-15 08:16:58] INFO Creating table: posts
[2020-01-15 08:16:59] INFO Creating table: posts_meta
[2020-01-15 08:16:59] INFO Creating table: users
[2020-01-15 08:16:59] INFO Creating table: posts_authors
[2020-01-15 08:17:00] INFO Creating table: roles
[2020-01-15 08:17:00] INFO Creating table: roles_users
[2020-01-15 08:17:00] INFO Creating table: permissions
[2020-01-15 08:17:00] INFO Creating table: permissions_users
[2020-01-15 08:17:01] INFO Creating table: permissions_roles
[2020-01-15 08:17:01] INFO Creating table: permissions_apps
[2020-01-15 08:17:01] INFO Creating table: settings
[2020-01-15 08:17:01] INFO Creating table: tags
[2020-01-15 08:17:01] INFO Creating table: posts_tags
[2020-01-15 08:17:02] INFO Creating table: apps
[2020-01-15 08:17:02] INFO Creating table: app_settings
[2020-01-15 08:17:02] INFO Creating table: app_fields
[2020-01-15 08:17:03] INFO Creating table: invites
[2020-01-15 08:17:03] INFO Creating table: brute
[2020-01-15 08:17:03] INFO Creating table: webhooks
[2020-01-15 08:17:03] INFO Creating table: sessions
[2020-01-15 08:17:03] INFO Creating table: integrations
[2020-01-15 08:17:04] INFO Creating table: api_keys
[2020-01-15 08:17:04] INFO Creating table: mobiledoc_revisions
[2020-01-15 08:17:04] INFO Creating table: members
[2020-01-15 08:17:04] INFO Creating table: members_stripe_customers
[2020-01-15 08:17:05] INFO Creating table: members_stripe_customers_subscriptions
[2020-01-15 08:17:05] INFO Creating table: actions
[2020-01-15 08:17:05] INFO Creating table: emails
[2020-01-15 08:17:05] INFO Model: Tag
[2020-01-15 08:17:05] INFO Model: Role
[2020-01-15 08:17:05] INFO Model: Permission
[2020-01-15 08:17:05] INFO Model: User
[2020-01-15 08:17:06] INFO Model: Post
[2020-01-15 08:17:06] INFO Model: Integration
[2020-01-15 08:17:06] INFO Relation: Role to Permission
[2020-01-15 08:17:06] INFO Relation: Post to Tag
[2020-01-15 08:17:06] INFO Relation: User to Role
[2020-01-15 08:17:08] INFO Ghost is running in production...
[2020-01-15 08:17:08] INFO Your site is now available on http://super:8888/
[2020-01-15 08:17:08] INFO Ctrl+C to shut down
[2020-01-15 08:17:08] INFO Ghost boot 11.075s
[2020-01-15 08:17:25] INFO "GET /" 200 450ms
[2020-01-15 08:17:25] INFO "GET /assets/built/screen.css?v=a3f7360902" 200 13ms
[2020-01-15 08:17:25] INFO "GET /assets/built/casper.js?v=a3f7360902" 200 3ms
[2020-01-15 08:17:25] INFO "GET /favicon.ico" 200 4ms

where was it? I arrived here via search but I'm still looking for it, too...

By default the Ghost admin page is at /ghost

Please refer the ghost docs. It's not related to this docker image.

Thanks to all. Confirmed that I am not going crazy. Ghost will not kick you to the admin account creation screen if the domain set in your url environment variable is not reachable.
In my case, that is configured in docker-compose.


Activated geocoder api extension install for new users

Last part to enable geocoder api install to all the users where are created

@rafatower check this out

after-the-fact-okay


Typescript type error?

First of all thanks for this nice library, it's filling an important gap in the JS world.
When using typescript I'm getting the following error, any idea? It seems an issue with the grouped column parameter.
         groupBy('day', [
            summarize({ total_cost: mean('total_cost'),
                        total_revenue: mean('total_revenue'),
                        margin: mean('margin') })
         ]))

No overload matches this call.
  The last overload gave the following error.
    Argument of type 'string' is not assignable to parameter of type 'GK<object>'.ts(2769)
tidy.d.ts(1006, 18): The last overload is declared here.
```

The types are pretty finicky, if you can come up with any great solutions I'd be happy to use them. My suggestion would be to try switching to groupBy(['day'] and see if that helps the type inference. If not, you may find groupBy(['day'], [summarize...], {}) helps the type inference. You may also be able to do it via the generics but it's a bit of a doozy


Mojave layout anomalies when toggling Hide Library

When toggling Hide Library while using Mojave layout there are 2 noticeable anomalies:

Top nav bar is see through where the Library bar once was:

Playbar remains at the default position thus leaves a wide space where the library bar once was:

Is ur Cider up to date? I do not have this problem on newest Cider and iTheme.

Just manually reinstalled both, can confirm issue has been resolved. Thanks for your time.


Updating MeetingDetail and MeetingParticipantDetail

Adding superscript of 2 for meeting detail and meeting participantdetail

@markjjo

@cebulnes PR merged. Thanks for doing this in a PR.


python3Packages.pytest-cid: 1.1.1 -> 1.1.2

Description of changes
https://github.com/ntninja/pytest-cid/releases/tag/v1.1.2
This version bump doesn't really change anything: https://github.com/ntninja/pytest-cid/compare/v1.1.1...v1.1.2
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 254782 run on x86_64-linux 1

4 packages built:

python310Packages.pytest-cid
python310Packages.pytest-cid.dist
python311Packages.pytest-cid
python311Packages.pytest-cid.dist


Also parse .uavcan files with explicit version number

I'm not really a python developer, hope i managed to not mess up these small changes to bad.

For the API part I assume that the correct thing to do was to add a version field to CompondType. My assumption is mainly based on CompoundType also containing the default_dtid, I've not done much research how the parser is actually used except for the test.py script in the dsdl repo.
I dont like the _full_typename_version_and_dtid_from_filename method name. Fortunately it's a private method, but perhaps parse_filename or something in that direction would be better?
I've verified that if two versions of the same message exists the list returned by parse_namespace will have two element with the same name. When they are printed they are indistinguishable, is that a problem?

Another thing i just realized. How do we handle version numbers in normalized definitions? I assume they should be added?

How do we handle version numbers in normalized definitions? I assume they should be added?

Yes.

The point about normalized definitions is no longer valid as they will be removed with the protocol update. That's good :)
The point about the _full_typename_version_and_dtid_from_filename method name still stand. However, If a better name is found It should be easy enough to fix later.

I've been incredibly busy the last two weeks and will be for a couple more days. I will hopefully have a bit more time next week.


Flaky standalone_2/io/process_run_test test failure on iso-stress bot

Log:
[/b/s/w/ir/cache/builder/sdk/runtime/tests/concurrency/../../../tests/standalone_2/io/process_run_test.dart] finished
[/b/s/w/ir/cache/builder/sdk/runtime/tests/concurrency/../../../tests/standalone_2/io/process_run_test.dart] finished
[/b/s/w/ir/cache/builder/sdk/runtime/tests/concurrency/../../../tests/standalone_2/io/process_run_test.dart] finished
[/b/s/w/ir/cache/builder/sdk/runtime/tests/concurrency/../../../tests/standalone_2/io/process_run_test.dart] finished
Spawning tests in isolates resulted in the following errors:
------------------------------------------------------------
[/b/s/w/ir/cache/builder/sdk/runtime/tests/concurrency/../../../tests/standalone_2/io/process_run_test.dart] error: [Expect.fail('System should find process_run_test executable (ProcessException: Text file busy
  Command: /b/s/w/ityr17vl2e/process_run_testXNVBVK/path with space/process_run_test )'), #0      Expect._fail (package:expect/expect.dart:742:5)
#1      Expect.fail (package:expect/expect.dart:310:5)
#2      testProcessPathWithSpace (file:///b/s/w/ir/cache/builder/sdk/tests/standalone_2/io/process_run_test.dart:54:12)
#3      main (file:///b/s/w/ir/cache/builder/sdk/tests/standalone_2/io/process_run_test.dart:63:3)
#4      wrapper3238.<anonymous closure> (file:///b/s/w/ir/cache/builder/sdk/runtime/tests/concurrency/generated_stress_test.dart:58452:14)
#5      _rootRun (dart:async/zone.dart:1426:13)
#6      _CustomZone.run (dart:async/zone.dart:1328:19)
#7      _runZoned (dart:async/zone.dart:1861:10)
#8      runZoned (dart:async/zone.dart:1783:10)
#9      wrapper3238 (file:///b/s/w/ir/cache/builder/sdk/runtime/tests/concurrency/generated_stress_test.dart:58451:3)
#10     _delayEntrypointInvocation.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:300:17)
#11     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:192:12)
]
------------------------------------------------------------
-> Setting exitCode to 255

https://logs.chromium.org/logs/dart/buildbucket/cr-buildbucket/8824432375318156721/+/u/Run_Isolate_Stress_Tests_shard_1/task_stdout_stderr:_Run_Isolate_Stress_Tests_shard_1
/cc @aam @mkustermann

Today I've looked at this a bit deeper. What happens it that multiple isolates run this process_run_test.dart code which makes a temporary directory, copies the process_test binary into it and runs it.
My first thought is that the random number generator will cause collisions in the temporary directory names, thereby making two isolates run in the same temp dir which would race on running & deleting that executable. Though it doesn't "seem" like this is happening.
The root cause is that the subprocess (after fork()ing) calls execvp and gets ETXTBSY. There's a special mention about this in the manpage:
The behavior of execlp() and execvp() when errors occur while attempting to execute the file is historic practice, but has not traditionally been documented and is not specified by the POSIX  standard.
BSD (and possibly other systems) do an automatic sleep and retry if ETXTBSY is encountered.
Linux treats it as a hard error and returns immediately.

So we're observing the Linux treats it as a hard error situation.
Though I have been so far unable to identify what other thread / process may have the very same binary opened in write mode. It is written once (with a File.copySync()) and not touched until the exec().
In any case - this is dart:io related so I'm going to exclude this test from the iso-stress builder.


Scalable Conveyor Assemblies

Overview
This PR adds four assemblies and their scripts.

BeltConveyorAssembly
RollerConveyorAssembly
CurvedBeltConveyorAssembly
CurvedRollerConveyorAssembly

And also some bugfixes for Rollers, ConveyorLeg grabs, and LegBars.
Assemblies can be scaled in the editor to expand without distorting their parts. Optionally, leg stands and side guards can be generated via configuration in the inspector.
Properties for conveyor parts are editable in the assemblies' inspector. Changes are forwarded to the appropriate parts.
Scaling Behavior
Scaling the assembly will never alter the apparent scale or rotation of its parts, except the length of conveyors, the length of side guards, and the height of leg stands.
All direct children of the assembly have an apparent scale locked to 1. Technically, their scale is locked to the inverse of the whole assembly's.
Scaling always happens from the origin of the assembly.
Scaling can affect the position of children, but not grandchildren.
X-Axis
Scaling the x-axis will adjust the length of the assembly, which will be equal to the x-scale in meters. This doesn't include any overhang caused by the ends of the conveyor and its side guards.
If the conveyor is rotated around it's z-axis, it will extend to reach the length of the whole assembly, but scaling will not change its angle. (See the Conveyor Angle property.)
Scaling a curved assembly's x-axis will also scale it's z-axis. Curved conveyors will always have an x-scale and z-scale the same as the assembly's and they can't be rotated.
Y-Axis
Scaling the y-axis will adjust the height of the assembly. For the assemblies provided, each unit of y-scale is equal to 2 meters of height from the origin to the midpoint of the conveyor. This ratio will change if the leg stands or conveyors are positioned manually. (In fact, one could reposition the parts to create a 1:1 ratio, but leg stands can't support a 1m-high conveyor.)
Z-Axis
Scaling the z-axis will adjust the width of the conveyor, the position of side guards, and the width of leg stands. The z-scale of the conveyor equals the z-scale of the assembly.
Z-scale is locked to x-scale for curved assemblies and can't be directly adjusted.
Scaling Properties

Automatic Length - Disable to allow adjusting conveyor parts independently of assembly x-scale

Rotation and Translation Behavior
Rotation and translation have default behavior at the assembly level.
Conveyor Rotation
The conveyor line can be rotated around the z-axis independently of the rest of the assembly. You can use editable children to do this or the option below. They stay in sync.
Property

Conveyor Angle - Adjust the angle of the conveyor line. (Straight assemblies only.)

Side Guards Generation
Side Guards Properties

Left Side - Generate side guards on the left side of the assembly (negative Z direction).
Right Side - Generate side guards on the right side of the assembly (positive Z direction).
Gaps - A list of gaps to place between the generated side guards.

Gap Position - Center of the gap in meters from the center of the Conveyors node.
Gap Width - Size of the gap in meters.
Gap Side - Whether to place the gap on the Left, Right, or Both sides.

Model Scene - Which model to use for the generated side guards.

Leg Stand Generation
Leg stands will auto-generate beneath the conveyor by default. They can also be manually placed by the user. All leg stands auto-scale their height to reach the conveyor line.
Auto Leg Stands Properties

Floor Offset - Distance in meters to raise the floor plane for generated leg stands. Default is assembly origin.

Interval-Generated Legs

Enabled - Auto-generate leg stands along the whole conveyor line at fixed intervals starting at the assembly origin.
Interval - The separation distance in meters or degrees depending on assembly shape.
Offset - Shift the generation starting point from the origin. Signed distance in meters. (Straight assemblies only.)

End Legs
A pair of legs, one on each end of the conveyor line.

Front Leg - Place a fixed leg stand at one end of the conveyor line.
Rear Leg - Place a fixed leg stand at the other end of the conveyor line.

Placement Margins

Ends Margin - The distance from the ends of the belt to keep free of all leg stands.
End Legs Margin - Prevent generated leg stands from appearing within this distance to a fixed leg.

Model
These options are about the specific leg stand model to use. It's assumed that all leg stands for an assembly are the same.

Grabs Offset - The distance from the end of a leg to the clamp of the leg stand grab.
Scene - Which scene to instance for generated legs.

Manually Placed Leg Stands
Users can also place additional leg stands manually if they enable "Editable Children" and make them children of the LegStands node. Manually placed leg stands will snap into place beneath the conveyor, allowing adjustment.
Leg Stand Placement and Coverage Details
Any leg stand that's a child of child LegStands will be automatically snapped and rotated under the conveyor line and extended to reach it. Manually placed leg stands are free to move on the conveyors' xy-plane and rotate around their z-axis. For curved conveyors, this "plane" is actually a cylinder and no z-axis rotation is possible.
All leg stands, even automatic ones, can have their y-position adjusted.
For the purposes of leg stands, the conveyor line is defined as child Conveyors's x-axis from the leading-most edge of all conveyor children to the trailing-most edge of them. So, if any gaps exist, they will get unnecessary leg stands.
When a leg stand can't reach the conveyors due to a bad position or angle, auto-generated leg stands are deleted and manually placed ones are hidden.
Interval-aligned leg stands start at the LegStands child's origin. That means that users can translate LegStands along its x and y-axes to adjust the start point. For curved conveyors, it would make sense to allow rotating LegStands around its y-axis, but this isn't implemented now.
Assembly Scene Structure
Any node can be the child of an assembly, but certain node names will be treated specially and are expected to be type Node3D if they exist. All direct children regardless of name have an automatic inverse scale applied that cancels the effect of the whole assembly's scale, but prevents manual scaling by the user.
Conveyors
This node contains the conveyor to be scaled and defines the plane to which leg stands should reach. All conveyor and side guard children of this node will have special scaling applied by default. Despite the name, using more than one conveyor is discouraged. For multiple conveyors arranged in a line, leg stand generation will work, but conveyor auto-scaling should be turned off.
For expected behavior, align and position all child conveyors on the local x-axis.
Anything attached to the conveyor's center line can go here.
Supported manual transformations for straight assemblies:

Translation along X and Y
Rotation around Z (synced with Conveyor Angle property)

Supported manual transformations for curved assemblies:

Translation along Y

LeftSide and RightSide
These nodes are meant for side guards and anything else you'd like to attach to the side of a conveyor. The position of each node follows Conveyors so that they will always be a fixed distance (one side guard width) from the side of the conveyor.
Side guard children will be auto-scaled to the conveyor's full length by default, so more than one on each side is discouraged unless auto scaling is turned off.
Curved assemblies use the LeftSide for their side guard model and lock the both sides to the Conveyors transform.
Supported manual transformations:

None

LegStands
This node contains all manually placed leg stands to be scaled and all auto-generated leg stands. Leg stand behavior is detailed later.
Supported manual transformations on straight assemblies:

Translation along X (synced with Interval Legs Offset property)
Translation along Y (synced with Floor Offset property)

Supported manual transformations on curved assemblies:

Translation along Y (synced with Floor Offset property)
Rotation around Y (logical, but not implemented)

Explanation of the Inverse Scaling approach
The conveyors, side guards, and legs stretch in an ugly way if scaled indirectly, such as by the transforms of their parents.
There are two ways to deal with it:

Update the parts so that they use their global scale to manage their appearance instead of their local one.
Place the parts inside container nodes that have an inverse scale applied, then scale the parts directly.

I ended up developing the latter solution. That meant I had to capture the scaling input and reapply it to the parts manually.

Thanks!


Update for contribution instructions

Updated the boilerplate files: README and CONTRIBUTING guides. Added a code of conduct file linking to Facebook's.

Made modifications as there was an existing code of conduct already added.


Add a "community" page with maintainer info

End-user friendly description of the problem this fixes or functionality that this introduces

[ ] Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below

This PR adds a somewhat more organized "community" page, and importantly adds information about how we nominate maintainers

Give a summary of what the PR does, explaining any non-trivial design decisions
The maintainer policy is just a draft/RFP. I'd like maintainers to comment if you can!

Link of any specific issues this addresses
We did not have a clear policy about how maintainers are nominated, but this will fix that.

To run this PR locally, use the following command:
docker run -it --rm   -p 3000:3000   -v /var/run/docker.sock:/var/run/docker.sock   --add-host host.docker.internal:host-gateway   -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:96d82db-nikolaik   --name openhands-app-96d82db   docker.all-hands.dev/all-hands-ai/openhands:96d82db

Thank you for this! To summarize quickly the underlying issue here:
I think building a startup on this project has been and continues to be a great idea, and I know it is and may still be a little tricky at times to mix and match the concerns of the company with the open source project. This isn't just a matter of license, it is also something to do with attempting to maintain a genuinely community-driven development process where all contributors, whether affiliated with All Hands or elsewhere, operate under the same expectations.
This maintainer nomination policy gets it right, and I really  appreciate the care and thought that went into crafting it.

Thank you @enyst ! And thanks for your help and feedback in drafting it.


HDDS-7175. Timed out tests missing from bundle

What changes were proposed in this pull request?
Timed out tests are now missing from CI bundles:

HDDS-3078 added timed out tests to CI check bundles
SUREFIRE-1728 changed the output of Surefire plugin
Ozone upgraded to the version with changed output in HDDS-6095

Example timeout missing from summary.
This PR tweaks the search string used to check for timeouts in output.
https://issues.apache.org/jira/browse/HDDS-7175
How was this patch tested?
Old Surefire version:
$ curl -LOSs https://raw.githubusercontent.com/adoroszlai/ozone-build-results/master/2022/01/14/12529/it-ozone/output.log

$ grep 'in the fork' output.log
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M1:test (default-test) on project ozone-integration-test: There was a timeout or other error in the fork -> [Help 1]

$ bash hadoop-ozone/dev-support/checks/_mvn_unit_report.sh
org.apache.hadoop.ozone.om.TestAddRemoveOzoneManager

New Surefire version:
$ curl -LOSs https://raw.githubusercontent.com/adoroszlai/ozone-build-results/master/2022/08/22/16839/it-hdds/output.log

$ grep 'in the fork' output.log
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) on project ozone-integration-test: There was a timeout in the fork -> [Help 1]

$ bash hadoop-ozone/dev-support/checks/_mvn_unit_report.sh
org.apache.hadoop.hdds.upgrade.TestScmHAFinalization

Thanks @ayushtkn, @kerneltime for the review.


Luck Perm GUI

Suggest: I know exist the plugin LuckPerms in GUI! , but would not it be great to create an official gui as good or better than UltraPermissions (It have a better GUI in the moment)?

Please see #619 for my opinions on this topic.
:)


Downloading issue

Not able to download the ud-851 exercise repository. Error comes while downloading

Same.

What is the error?


resetpersistence isn't working

It wasn't like this until a few versions ago, something must have happened between the last 3-4 releases.
I don't know much, might be related to refactor or just some other small thing,
I tested it in version 1.10.3, 5 and now latest version 6, the result is the same.
[error] Failed reading masterserver response: got fastify error response
[error] {"error":{"enum":"NO_GAMESERVER_RESPONSE","msg":"Couldn't reach game server: failed to connect to auth port: request timed out"},"request_id":"cdr6bv13ngom5el9f77g","success":false}

[error] Reached max ms server registration attempts.

Sometimes not a response at all.
The command itself doesn't work at all, but script_ui seterrorhandler(void function() {}) was working, I had 3 other people tested to see if the problem was specific to me and confirmed that it worked, but now the script doesn't work anymore either.

This issue can now be closed, thanks to 1.10.7

Huh, we didn't change anything in v1.10.7 that addresses this? ^^

Well, yeah I read the update notes and didn't see anything related to this, but somehow it does work now. Maybe we can ask others to test it too.

Huh, we didn't change anything in v1.10.7 that addresses this? ^^

Well, yeah I read the update notes and didn't see anything related to this, but somehow it does work now. Maybe we can ask others to test it too.

It seems that there are still people having problems with this.


chore: bump reth; breaking changes

bump reth and fix a few breaking changes of the ext trait + types

@mattsse Great stuff. Thanks a lot🙏


Sidebar doesn't load on mobile devices

Options sidebar on the homepage doesn't load on mobile devices

Closing - No longer valid as a brand-new site was deployed (https://botkube.io) as a part of #80 🙂


WIP: Use native epoll transport on Linux

Summary of the changes / Why this improves CrateDB
Checklist

[ ] User relevant changes are recorded in CHANGES.txt
[ ] Touched code is covered by tests
[ ] Documentation has been updated if necessary
[ ] CLA is signed
[ ] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

Ran some benchmarks and I didn't see a clear improvement. Since we'd have to introduce some dynamic loading or different distributions for windows I'm closing this.


Can't change phy_mode to 1

When I try to change the phy_mode 802.11n to 802.11b it resets itself and I lose connection. I both tried telnet and serial port.

Maybe your uplink AP doesn't support 11b any more? There is no good reason to use it, if you have 11g or 11n.

Maybe your uplink AP doesn't support 11b any more? There is no good reason to use it, if you have 11g or 11n.

I'm using a old router and it seems it supports it. I just wanted to change it to increase TX and RX performance.

I'm using a old router and it seems it supports it. I just wanted to change it to increase TX and RX performance.

turn off ap mode before change the phy_mode seems work


Add documentation

Tests(#1) and CI(#2) are good, but actually telling people what this thing even does is kinda important.

Think the new readme is great so believe this can be closed!


MyBatis TransactionalCacheManager problem

When secondary caching(Redis) and transactions are opened, TransactionalCacheManager commits because entries ToAddOnCommit PutObject reads pojo's attribute method to obtain caches of other objects, which may result in ConcurrentModificationException of transactional Caches, with the following exceptions：

Whether use iterator instead of for loop in the commit method of TransactionalCacheManager。
like this:
public void commit() {
        Iterator it= this.transactionalCaches.values().iterator();

        while(it.hasNext()) {
            TransactionalCache txCache = (TransactionalCache)it.next();
            txCache.commit();
        }

    }

Hi @huangqinghe ,
I'm sorry, but I couldn't follow your explanation.
Please consider providing a repro like these.
And please paste text instead of an image whenever possible.

No reply.


Add refactored configurator

create controller directory to host all workflow related functionalities
(configurator, reporter, k8s-client functions, etc.)
add refactored configurator
part of effort for #48 (2nd layer API)

This change is

/hold

/assign @gaocegege

/lgtm

/approve


Full website

Building the Full Website
In this Step of The Project we've implemented the followings

Add Footer ✅
Add Header ✅
Add Home Page ✅
Add Quote Page ✅
Add Calculator Page ✅
Add and Optimize Styles ✅
Implement React Router for Navigation ✅
Add and use Pictures in building the website  ✅

thanks @vickymarz


Splatoony UI Update

First of all, thanks for making this tool! It's really good and will come handy when I eventually use it properly.
I've made some visual changes to enhance the experience and make it mimic more of Splatoon 2's splatiness of a user Interface.
Dialogs - Before

Dialogs - After

In addition:

The dropdown for selecting a language is less like Bootstrap's default.

Styling has been added to scrollbars for WebKit-based browsers (i.e. Chrome/Safari)

PS. I noticed I was working on ver 1.1.1, but the loadout.ink website is on ver 1.1.2. :confused:
Hope you like it! :smile:

Booyah! :smiley:
I'd be happy with that -- you can call me @lah7, or my full name (whichever seems to fit best), linking to my GitHub page. :+1:

holy


[BUG]Unable to load addon script from path: 'res://addons/dreadpon.spatial_gardener/plugin.gd'.

Godot v3.4.2.stable.mono.oficial [45eaa2daf]
OS: Ubuntu 18.04
godot_spatial_gardener_demo_v1.0.0-stable.zip
godot_spatial_gardener_demo_v1.0.0-stable.zip
"0.1.0 (3283e07), etc."
Unable to load addon script from path: 'res://addons/dreadpon.spatial_gardener/plugin.gd'. This might be due to a code error in that script.
Disabling the addon at 'res://addons/dreadpon.spatial_gardener/plugin.cfg' to prevent further errors.

Does the editor tell anything else? Or perhaps the console mentions the specific line where the error occurs? Does restarting the editor affect this issue somehow?

well, that is strange, i closed godot and opened again, and the bug was still there, but then, i deleted the file and extracted the zip again, and now it seems to be working fine...
so... sorry but im having trouble reproducing the bug on the first time i tried to extract it (on the file extracting program) , so maybe the problem isnt related to your code?
im not sure.
i will close the issue for now, hopefully no one will face it again.


Missing: Could you add Overwatch 2, thank you!

Could you please add Overwatch 2, thank you!

I have added the game(s) you requested in the most recent release: https://github.com/hobby-grade/Nintendo-Switch-Discord-Status/releases/tag/v1.1.3
Thank you for checking out the project, reach out if you have any more suggestions!


refactor

It seems the Monitor wrapper doesn't like the env being reset() when it is not done during evaluations:
Episode #1 return: 19.0		 episode length: 2806
Traceback (most recent call last):
  File "RL_plus_script.py", line 265, in <module>
    main()
  File "RL_plus_script.py", line 261, in main
    test()
  File "RL_plus_script.py", line 227, in test
    obs = env.reset()
  File "/home/karolis/Desktop/MineRL_2021/tmp/venv/lib/python3.7/site-packages/gym/wrappers/monitor.py", line 37, in reset
    self._before_reset()
  File "/home/karolis/Desktop/MineRL_2021/tmp/venv/lib/python3.7/site-packages/gym/wrappers/monitor.py", line 177, in _before_reset
    self.stats_recorder.before_reset()
  File "/home/karolis/Desktop/MineRL_2021/tmp/venv/lib/python3.7/site-packages/gym/wrappers/monitoring/stats_recorder.py", line 68, in before_reset
    raise error.Error("Tried to reset environment which is not done. While the monitor is active for {}, you cannot call reset() unless the episode is over.".format(self.env_id))
gym.error.Error: Tried to reset environment which is not done. While the monitor is active for MineRLObtainDiamond-v0, you cannot call reset() unless the episode is over.

Any ideas for a clean fix to this?

Monitor wrapper should have "allow_early_reset" flag for that.

Monitor wrapper should have "allow_early_reset" flag for that.

That would not change anything, right? Because env1 does not call the Monitor's step to record the video. Also, gym.wrappers.Monitor does not appear to have the allow_early_reset flag, thought it has a write_upon_reset flag, but I don't think it's gonna fix the issue.

Looking good to me, just need to iron out the one odd part of the code. That should also fix this monitor issue :)


WRN-9482 : [Sandstone] QA Sampler: Migrate storybook/addon-knobs to addon-controls

Enact-DCO-1.0-Signed-off-by: SJ RO<EMAIL_ADDRESS>Checklist

[x] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
Migrate addon-knobs to addon-controls in sampler, qa-sampler
Resolution
Migrate addon-knobs to addon-controls in sampler, qa-sampler
Additional Considerations
Links
WRN-9482
Comments

 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.

LGTM


Pull request for setting version on jaeger binaries

Which problem is this PR solving?

Short description of the changes

Can you please provide more details on the motivation behind this PR:

What specific problem is this trying to solve.
What is the final outcome of this change, e.g. what the windows explorer properties would look like for the jaeger exe.
How do you plan to manage version updates for each new release?
How can/should we incorporate this into our release process?

Yeah, this PR is not usable as is. Judging by the file names, this may have something to do with some of these tools:

https://pkg.go.dev/github.com/hallazzang/syso
https://github.com/tc-hib/go-winres
https://github.com/akavel/rsrc

But the files are supposed to be generated at build time, not checked in. What we would need instead:

a Makefile target to generate those files
if the tool is a Go program, it needs to be installed like the other build-time tools we install
It needs to use proper Jaeger icon
the config JSON needs to be filled out as appropriate for Jaeger project.
I am not clear if this will automatically use git tags for versions, or if we need to generate a different config file during build time where those values are populated (instead of <IP_ADDRESS>)

closing as there was no follow-up, feel free to reopen if comments are addressed


Fix typo

@bradfitz : Thanks for your contribution! The author(s) have been notified to review your proposed change.


GitHub output for CITATION.cff with 'preferred-citation'

When CITATION.cff has a 'preferred-citation', the DOI is absent in the output produced by GitHub.
Example: https://github.com/fgnievinski/mphw/blob/main/CITATION.cff

A. R. Fagundes, M., Mendonça-Tinti, I., L. Iescheck, A., M. Akos, D., & Geremia-Nievinski, F. An open-source low-cost sensor for SNR-based GNSS reflectometry: design and long-term validation towards sea-level altimetry. GPS Solutions, 25(), 73

The publisher's "cite this article" text reads:

Fagundes, M.A.R., Mendonça-Tinti, I., Iescheck, A.L. et al. An open-source low-cost sensor for SNR-based GNSS reflectometry: design and long-term validation towards sea-level altimetry. GPS Solut 25, 73 (2021). https://doi.org/10.1007/s10291-021-01087-1

Besides the major issue above (DOI missing), a related minor issue is the presentation of journal issue numbers: when it's absent, it should not produce empty parentheses "()" next to the volume number.
Related issues:

https://github.com/citation-file-format/citation-file-format/issues/343

if I set "preferred citation", the BibTeX generated by GitHub does not seem to include most of the data entered

https://github.com/ropensci/cffr/issues/7

indeed, I wasn't aware it's possible to use doi without identifiers; now my example is fixed.
except for the journal issue number, please let me know if it should be split in a new ticket.

except for the journal issue number, please let me know if it should be split in a new ticket.

Good with me either way, whatever @hainesr thinks is most convenient

Let's just leave this issue open and I'll have a look at this as soon as possible.

Right, I'm looking at this now. One thing I've also noticed in the comparison of the two outputs above is the apparent mangling of the authors' initials:
A. R. Fagundes, M.

Where you'd expect:
Fagundes, M.A.R.

It turns out that in the CFF file the middle initials have been specified in the name-particle field, which is for things like 'von' or 'van der' rather than initials. @fgnievinski, was this how the CFF was generated by cffinit? If so I think that's a bug in cffinit.

Hi @arfon, with this and #105 now fixed it might be a good time for a bump of the version GitHub uses. Do you need me to cut a release?

:+1: will do. I'll look at getting this deployed early next week.

@fgnievinski, was this how the CFF was generated by cffinit? If so I think that's a bug in cffinit.

I've split this in a separate issue:
https://github.com/citation-file-format/citation-file-format/issues/373


Parallel iterators cause huge (~30x) slowdown in Callgrind.

I have a few, small parallel iterators in my program to do very expensive operations in parallel. Everything is fine when I run it standalone, but when I try to profile it in Callgrind, it runs spectacularly slowly, with rayon eating up 97% of my execution time according to the profiling output. When I switch to stdlib iterators, it runs about 30 times faster. I included the callgrind output (Use KCachegrind for human-readable viewing), but the biggest offending functions are:

rayon::thread_pool::WorkedThread::steal_work (43%)
std::panicking::try::do_call (25%)
pthread_mutex_lock (11%)
std::panicking::panicking (10%)

It also only uses one core when running in Callgrind.
I'm not sure if this is normal or to be expected in Callgrind, but I'd really like to able to properly profile this program. I can provide more info if anyone is interested.
callgrind.out.txt

Valgrind in general is not great with threading - see here: http://valgrind.org/docs/manual/manual-core.html#manual-core.pthreads
Personally, I use perf for profiling rayon.

I'm inclined to close this issue, since it seems like it's not really a rayon problem per se. @MortenLohne feel free to re-open or comment if you disagree. Hopefully perf works for you!

FWIW, valgrind --fair-sched=yes does seem to do a little better here, but it's still not great.


Docs - note when partitioning using concatenated dimensions

OTBO community Slack https://the-asf.slack.com/archives/CJ8D1JTB8/p1595434977062400

Note of caution when doing single_dim with concatenated dimensions.
Links to subheadings for each partitioning type
Slight wording changes

This PR has:

[x] been self-reviewed.
[ ] been tested in a test Druid cluster.

@techdocsmith

@techdocsmith I have merged our proposals – switched up the grammar and added some links, too.


Dashboard within accordion rendering as a stack

copied from PAL tracking issue
Occuring in APM  here: http://mahi-docker09.swg.usma.ibm.com:3000/#/assetDetail?ids=1588
The dashboard is automatically adjusting itself on the screen when rendering.
1: The dashboard inside of the Predictions accordion (and any other accordion) do not properly render when opened.  On screen re-size, they "snap" into the proper position.

2: The dashboard causes a horizontal scroll on the screen. When you re-size the browser, the horizontal scroll disappears.

Here's a CRA that demonstrates the dashboard overflow issue.  In short this is caused because of page animations.  ie, we want to show a little bump when you navigate to the page.  The dashboard never updates itself based on available space so it overflows.  When you build this app, it starts on a main page, just click the dashboard on the side menu to show the dashboard view with an overflow.
dashboard-overflow.zip

@stuckless that is what I needed.

This should be applied to the container and it allows DashboardGid to calculate properly. The only other way is to force trigger a render but then you would lose the animation in.

Closing issue since there is no component change. @stuckless please feel free to reopen if necessary.


Embedding WebAssembly in Javascript code

💡 Feature description
I wish wasm-pack could do something like this.
The feature is almost the same as doing wasm-pack build --target nodejs except, instead of doing
const path = require('path').join(__dirname, 'xxx_bg.wasm');
const bytes = require('fs').readFileSync(path);

do
// convert wasm file into base64 and embed it
const base64Wasm = "AGFzbQEAAAABBwFgAn9/AX8DAgEABwcBA2FkZAAACgkBBwAgACABags=";
const bytes = base64Decode(base64Wasm);

This is very helpful because I dont have to worry about .wasm file in both nodejs and web.

so you proposing essentially --target inline and base64 encoded inline wasm loading?

@sassman that's the gist of it, at least from my perspective. It offers a nice "one-file" solution to incorporate wasm into a webpage.

I've been searching something like this for days. Has anyone done this with binding any canvas functions?

Would love to have this!

+1, I've been doing this by hand and would love a build system that does it automatically.

Hey @jmole, how did you do this by hand?


cant connect to servers

Describe the bug
cant connect to proxies
To Reproduce
Steps to reproduce the behavior:

Go to 'idk'
Click on 'idk'
See error

Expected behavior
wont let you connect
Logs
Attach logs (app, node, supervisor) to the issue. Where to find the logs: https://github.com/mysteriumnetwork/mysterium-vpn-desktop#logs
Screenshots

Desktop (please complete the following information):

OS: [e.g. Windows 11]
App Version idk

Additional context
Add any other context about the problem here.

I have same problem


what about the way for the data stream of apollo ?

Hello, Excuse me. when the apollo is running, the camera 、lidar and others device will gather data to keep the car is normal operation. So I want to know, The camera、lidar and others device need to gather how much data ? and how does the data flow ?For example from the description on the bus device, or from the kernel, rtos, apollo. and what is the standard of camera、lidar and others device ? such as How many frames per second per camera？How much data does the laser radar produce per second?
Best regards！Thank you!

call apollo...

@breakisx
a late reply!

such as How many frames per second per camera？How much data does the laser radar produce per second?

It depends on the camera, usually 30Hz, radar are usually 100Hz, and lidar 10hz


TypeError: Cannot read property 'withRootViewBackgroundColor' of undefined

Summary
When building using eas on iOS the following message appears before the start of iOS build =>
TypeError: Cannot read property 'withRootViewBackgroundColor' of undefined
Expected behavior : iOS build should start
Actual behavior : iOS build canceled
Environment
EAS CLI 0.38.0 environment info:
System:
OS: macOS 12.0.1
Shell: 5.8 - /bin/zsh
Binaries:
Node: 12.18.1 - ~/.nvm/versions/node/v12.18.1/bin/node
Yarn: 1.22.17 - ~/.nvm/versions/node/v12.18.1/bin/yarn
npm: 6.14.5 - ~/.nvm/versions/node/v12.18.1/bin/npm
Utilities:
Git: 2.34.0 - /opt/homebrew/bin/git
npmPackages:
expo: ^43.0.0 => 43.0.3
expo-cli: ^4.13.0 => 4.13.0
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
Error output
TypeError: Cannot read property 'withRootViewBackgroundColor' of undefined
Reproducible demo or steps to reproduce from a blank project
Run eas build -p ios

Hi @yonitou,
I can't reproduce the issue. Could you try reinstalling eas-cli?

Just did and same error :/
I downgraded back to 0.37 and it now works perfectly.
Maybe, to reproduce, you can try having the same app.config.ts structure that we have ?
import { ExpoConfig, ConfigContext } from "@expo/config";
import "dotenv/config";

const BUILD_NUMBER = "400";
const BUILD_VERSION = "4.0.0";

const BUNDLE_ID = "com.XXX.YYY";

export default ({ config }: ConfigContext): ExpoConfig => ({
	...config,
	extra: {
		build: BUILD_NUMBER,
		version: BUILD_VERSION,
		baseURL: process.env.BASE_URL,
	},
	name: "XXX",
	slug: "XXX",
	owner: "XXX",
	privacy: "public",
	platforms: ["ios", "android", "web"],
	version: BUILD_VERSION,
	orientation: "portrait",
	icon: "./assets/icon.png",
	plugins: ["./lib/withSimulatorExcludedArchitecture.ts", "sentry-expo"],
	splash: {
		image: "./assets/splash.png",
		resizeMode: "cover",
		backgroundColor: "#2C6465",
	},
	updates: {
		fallbackToCacheTimeout: 0,
	},
	assetBundlePatterns: ["**/*"],
	hooks: {
		postPublish: [
			{
				file: "sentry-expo/upload-sourcemaps",
				config: {
					organization: "XXX",
					project: "XXX",
					authToken: "XXX",
				},
			},
		],
	},
	ios: {
		buildNumber: BUILD_NUMBER,
		supportsTablet: true,
		bundleIdentifier: BUNDLE_ID,
		infoPlist: {
			NSCameraUsageDescription:
				"XXXX",
			NSLocationAlwaysUsageDescription:
				"XXXX",
			NSLocationWhenInUseUsageDescription:
				"XXXX",
			NSLocationAlwaysAndWhenInUseUsageDescription:
				"XXXX",
			UIBackgroundModes: ["location", "fetch"],
		},
		config: {
			googleMapsApiKey: process.env.GOOGLE_MAPS_API_KEY,
		},
	},
	androidStatusBar: {
		hidden: false,
		translucent: true,
		barStyle: "dark-content",
		backgroundColor: "#FFFFFF",
	},
	notification: {
		icon: "./assets/icon.png",
		color: "#67dee1",
	},
	android: {
		package: BUNDLE_ID,
		versionCode: parseInt(BUILD_NUMBER, 10),
		googleServicesFile: "./google-services.json",
		config: {
			googleMaps: {
				apiKey: process.env.GOOGLE_MAPS_API_KEY,
			},
		},
		useNextNotificationsApi: true,
		permissions: [
			"CAMERA",
			"NOTIFICATIONS",
			"READ_EXTERNAL_STORAGE",
			"USE_FINGERPRINT",
			"VIBRATE",
			"WAKE_LOCK",
			"WRITE_EXTERNAL_STORAGE",
			"ACCESS_FINE_LOCATION",
			"ACCESS_COARSE_LOCATION",
			"com.anddoes.launcher.permission.UPDATE_COUNT",
			"com.android.launcher.permission.INSTALL_SHORTCUT",
			"com.google.android.c2dm.permission.RECEIVE",
			"com.google.android.gms.permission.ACTIVITY_RECOGNITION",
			"com.google.android.providers.gsf.permission.READ_GSERVICES",
			"com.htc.launcher.permission.READ_SETTINGS",
			"com.htc.launcher.permission.UPDATE_SHORTCUT",
			"com.majeur.launcher.permission.UPDATE_BADGE",
			"com.sec.android.provider.badge.permission.READ",
			"com.sec.android.provider.badge.permission.WRITE",
			"com.sonyericsson.home.permission.BROADCAST_BADGE",
		],
	},
});

Your app config looks good at first glance.
We just released a new version of eas-cli (0.38.1) that includes @expo/* deps upgrade. Can you check if it works for you?

Same issue here using plugins. I have eas-cli 0.38.1 too... @dsokal

@sean-m-oleary - this is likely an issue with using yarn to install eas-cli globally. run yarn global remove eas-cli && npm i -g eas-cli

Closing because of the inactivity.


Migrate package to Swift 4, remove support for Swift 3

This also modifies the package dependencies to use a slightly upgraded HypertextApplicationLanguage, but we can remove that if https://github.com/noppoMan/HypertextApplicationLanguage/pull/1 gets merged.

@noppoMan How do you feel about bumping the version of Swift to 4.1? I think there are a few good improvements here, and we'll need it for #28 and #15 🙏

@Yasumoto lgtm. I think Yuki was working on this for the parent sdk as well.
@noppoMan i will go ahead and merge this tomorrow morning if no objections
https://github.com/noppoMan/aws-sdk-swift/pull/75

Sweet! Sounds like I could lend a hand on some build issue there, I’ll take a look tomorrow (I’m in Dublin, so it’s UTC for me) 👍

@Yasumoto ok, what comes to mind is whether this warrants a version bump... since there is impact on the parent sdk, which still claims support for 3.x
Perhaps we should update the parent first?


Make requirements stand out more in setup.py

Jan-Willem commented that he could not easily find where to update the
requirements in setup.py. Now it should stand out more.

:+1:


Version: '5.5.41-0ubuntu<IP_ADDRESS>'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
150303 12:25:44 [Note] /usr/sbin/mysqld: Normal shutdown
150303 12:25:44 [Note] Event Scheduler: Purging the queue. 0 events
150303 12:25:46 [Warning] /usr/sbin/mysqld: Forcing close of thread 61  user: 'nova'
150303 12:25:46 [Warning] /usr/sbin/mysqld: Forcing close of thread 59  user: 'nova'
150303 12:25:46 [Warning] /usr/sbin/mysqld: Forcing close of thread 56  user: 'keystone'
150303 12:25:46 [Warning] /usr/sbin/mysqld: Forcing close of thread 55  user: 'keystone'
150303 12:25:46 [Warning] /usr/sbin/mysqld: Forcing close of thread 52  user: 'cinder'
150303 12:25:46  InnoDB: Starting shutdown...
150303 12:25:47  InnoDB: Waiting for 162 pages to be flushed
150303 12:25:48  InnoDB: Shutdown completed; log sequence number 6294563
150303 12:25:48 [Note] /usr/sbin/mysqld: Shutdown complete
150303 12:25:48 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150303 12:25:48 [Note] Plugin 'FEDERATED' is disabled.
150303 12:25:48 InnoDB: The InnoDB memory heap is disabled
150303 12:25:48 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150303 12:25:48 InnoDB: Compressed tables use zlib 1.2.8
150303 12:25:48 InnoDB: Using Linux native AIO
150303 12:25:48 InnoDB: Initializing buffer pool, size = 128.0M
150303 12:25:48 InnoDB: Completed initialization of buffer pool
150303 12:25:48 InnoDB: highest supported file format is Barracuda.
150303 12:25:48  InnoDB: Waiting for the background threads to start
150303 12:25:49 InnoDB: 5.5.41 started; log sequence number 6294563
150303 12:25:49 [Note] Server hostname (bind-address): '<IP_ADDRESS>'; port: 3306
150303 12:25:49 [Note]   - '<IP_ADDRESS>' resolves to '<IP_ADDRESS>';
150303 12:25:49 [Note] Server socket created on IP: '<IP_ADDRESS>'.
150303 12:25:49 [Note] Event Scheduler: Loaded 0 events
150303 12:25:49 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.41-0ubuntu<IP_ADDRESS>'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)

Mar  3 12:25:38 vagrant-ubuntu-trusty-64 ansible-command: Invoked with executable=None shell=True args=/opt/image_upload.sh && touch image_upload_completed removes=None creates=image_upload_completed chdir=None
Mar  3 12:25:44 vagrant-ubuntu-trusty-64 ansible-service: Invoked with name=mysql pattern=None enabled=None state=restarted sleep=None arguments= runlevel=default

Was this error thrown by Ansible? I had the same errors too, which was due to the glance image create/upload action before 9292 being brought up. I added a line in Ansible to prevent uploading until port is up. Don't know if this is the case.

9292 was up. glance api worked. from the first log, it was db that was down.
second comment is mysql.log, third is syslog.

I encountered "mysqldb has gone away" errors too, but failed re-produce it. Did your commit fix the issue? Would you be able to locate the bug?

i suspect db restart was notified and executed at the end, immediately after glance role was finished.
syslog shows that the db was restarted by ansible on purpose, not by accident. weird that you couldn't reproduce it.
my commit won't fix this issue. i only saw in db role task there was a db restart, somehow it got executed in the end as well.

This is because "notify" commands will be and will only be executed during end of each play run and direct commands for actions will be executed immediately, and I think I placed both "notify" and "shell" for mysql db restart, which is probably why db has this problem.
I will look into it.

the problem is that glance image-create from remote source is an async action, and after it returned true, restart mysql will be executed, which is required as it subscribes to my.cnf.
we could download cirros image, and create image from the file instead of url, also there had better be a delay after glance image-create.

There is a "wait_for: port=9292 delay=5" in the action before running image upload. I am adding another delay in the sh script.

That won't do it. It is the db restart after asynchronous image create causing the issue.
I have fix it by creating from local file, which is synchronous.
Best regards!
Jerry

On Mar 5, 2015, at 2:49 AM, Xicheng Chang<EMAIL_ADDRESS>wrote:
There is a "wait_for: port=9292 delay=5" in the action before running image upload. I am adding another delay in the sh script.
—
Reply to this email directly or view it on GitHub.

OK I may revert that change I made to image_upload.sh later, it would only sleep for 10 sec before uploading. I ran a test earlier today and still it complained that "No Valid host was found", but this time it's different that I traversed all nova logs but found no errors. Could you help look at that, too?

I have faced same issue and i tried to upload image from file/ISo format but that also not worked and status shown was killed


Analyze existing ring-attention implementations

Please create a little markdown report about your findings.

lhao499/ring-attention/bpt
lucidrains/ring-attention-pytorch

Get some feeling for the impls:

easy to setup and run on our dev machine (e.g. with nvidia gpus)?
perf, gpu-utilization & memory usage (e.g. very high-level with nvtop)

I'll close this is favor of a new one to compare the two impls by lucidrains & zhuzilin.


Help needed for installation

Thank you for your great project.I want to use your code to build low power sensor network for home automation using 10-15 esp8266 devices as sender devices and Raspberry pi zero as receiver or gateway to internet. Right now I am using adhoc network to exchange 2 way data between 2 ESP8266 devices but it takes about 200 milliseconds to exchange 6 bytes of data. As I read on your hackaday project your solution is very fast. I have put my raspberry pi in monitor mode using https://re4son-kernel.com/download/re4son-kernel-current/ but I am confused about my next steps to use your code.
Can you please provide brief howto steps ? I do not know which code from this repo I have to use for sender ESP8266 ?  Also what I need to do on raspberry pi ?
Please help me.
Thanks.

Hello,
I think a good start is to use this simple code, on the pi:
https://github.com/thomasfla/Linux-ESPNOW/blob/master/ESPNOW_lib/src/main.cpp
this will echo each espnow packet received by the pi.
You could also run wireshark on the pi to check that you receive the espnow packet. It's a simple and usefull graphical tool.
I never ran this code on the pi, I would be interested to have your feedback!
On the esp side, you could have a look at this simple code:
https://github.com/thomasfla/Linux-ESPNOW/blob/master/ESP8266_Echo/ESP8266_Echo.ino
My advice would be to modify it to only send data, in a first time. You could remove the 'send' call in the receive callback and put it in the main loop with a reasonable delay.

I tried to compile your code to raspberry pi and I get following error message:
/tmp/ccKgaZCh.o: In function `callback(unsigned char*, unsigned char*, int)':
espnow.cpp:(.text+0x68): undefined reference to `ESPNOW_manager::send()'
/tmp/ccKgaZCh.o: In function `main':
espnow.cpp:(.text+0x118): undefined reference to `ESPNOW_manager::set_filter(unsigned char*, unsigned char*)'
espnow.cpp:(.text+0x12c): undefined reference to `ESPNOW_manager::set_recv_callback(void (*)(unsigned char*, unsigned char*, int))'
espnow.cpp:(.text+0x13c): undefined reference to `ESPNOW_manager::start()'
/tmp/ccKgaZCh.o: In function `ESPNOW_manager::ESPNOW_manager(char*, unsigned char, unsigned short, unsigned char*, unsigned char*, bool)':
espnow.cpp:(.text._ZN14ESPNOW_managerC2EPchtPhS1_b[_ZN14ESPNOW_managerC5EPchtPhS1_b]+0x38): undefined reference to `ESPNOW_manager::set_interface(char*)'
espnow.cpp:(.text._ZN14ESPNOW_managerC2EPchtPhS1_b[_ZN14ESPNOW_managerC5EPchtPhS1_b]+0x8c): undefined reference to `ESPNOW_manager::set_filter(unsigned char*, unsigned char*)'
espnow.cpp:(.text._ZN14ESPNOW_managerC2EPchtPhS1_b[_ZN14ESPNOW_managerC5EPchtPhS1_b]+0xa0): undefined reference to `ESPNOW_manager::set_filter(unsigned char*, unsigned char*)'
/tmp/ccKgaZCh.o: In function `ESPNOW_manager::set_channel(unsigned short)':
espnow.cpp:(.text._ZN14ESPNOW_manager11set_channelEt[_ZN14ESPNOW_manager11set_channelEt]+0x28): undefined reference to `ESPNOW_packet::set_channel(unsigned short)'
/tmp/ccKgaZCh.o: In function `ESPNOW_manager::set_datarate(unsigned char)':
espnow.cpp:(.text._ZN14ESPNOW_manager12set_datarateEh[_ZN14ESPNOW_manager12set_datarateEh]+0x28): undefined reference to `ESPNOW_packet::set_datarate(unsigned char)'
/tmp/ccKgaZCh.o: In function `ESPNOW_manager::set_src_mac(unsigned char*)':
espnow.cpp:(.text._ZN14ESPNOW_manager11set_src_macEPh[_ZN14ESPNOW_manager11set_src_macEPh]+0x20): undefined reference to `ESPNOW_packet::set_src_mac(unsigned char*)'
/tmp/ccKgaZCh.o: In function `ESPNOW_manager::set_dst_mac(unsigned char*)':
espnow.cpp:(.text._ZN14ESPNOW_manager11set_dst_macEPh[_ZN14ESPNOW_manager11set_dst_macEPh]+0x20): undefined reference to `ESPNOW_packet::set_dst_mac(unsigned char*)'
collect2: error: ld returned 1 exit status````

Thanks

For anyone else seeing this, you need to compile the program with the included Makefile (it contains compile instructions basically).
From the project home directory, cd into /ESPNOW_lib and then just execute make in the terminal. A new directory - bin will be generated as a sibling to the src directory.

For anyone else seeing this, you need to compile the program with the included Makefile (it contains compile instructions basically).
From the project home directory, cd into /ESPNOW_lib and then just execute make in the terminal. A new directory - bin will be generated as a sibling to the src directory.


Get test suite to pass with Python 3

Main changes:

Bump TestCmd.py and TestCommon.py from SCons
Un-wrapping long line
de-lint for E9,F8
disable some CLI flags I didn't like (opt out of checks, run in parallel)
implement environment cache to speedup ninja on Windows

These issues on Python 2 only are worth paying attention to:

https://travis-ci.com/refack/GYP/jobs/178702474#L226

The issue is that on Python 3, variables that are defined inside a comprehension are scoped only to that comprehension so there are not side effects but that scope leaks outside the comprehension in Python 2 so you might want to find unique variable names.

These issues on Python 2 only are worth paying attention to:

travis-ci.com/refack/GYP/jobs/178702474#L226

Ack. Fixed.
I want to expand https://github.com/refack/GYP/blob/9acfe76809586c952ce952eeec5a3f6445b0cc49/.flake8#L3
incrementally, to get maximum benefit from static analysis.

This should be ready to land.
Any review will be much appreciated (big change set, so even partial review will be great).

Travis CI: Do we want the macOS test to run in allow_failures mode for now or do you know how to fix?

Travis CI: Do we want the macOS test to run in allow_failures mode for now or do you know how to fix?

I'm not sure why it regressed.
Should be green now (skipping this test on Travis)


Link provided by Paper doesn't work

When I do the /timings report command, paper gives me a link but the link doesn't exist

I'm on Paper 1.6.1-136
Plugins (25): ActionHealth*, AuthMe, BannerMaker, Chunkmaster, DeadChest, dynmap*, Essentials, EssentialsAntiBuild, EssentialsChat, EssentialsProtect, EssentialsSpawn, ImageOnMap, LuckPerms, LWC, LWCTrust, OpenInv, PlugMan, ProtocolLib, SetHomes*, SinglePlayerSleep, SkinsRestorer, Timber, Vault, WorldEdit, WorldGuard

Replace /d= with /?id=, your control panel is janky and screwing up the output

On 20 Aug 2020, at 22:13, jsebtessier<EMAIL_ADDRESS>wrote:
When I do the /timings report command, paper gives me a link but the link doesn't exist
https://user-images.githubusercontent.com/26907216/90822829-05352f00-e303-11ea-8130-47315fe3fc8c.png
https://user-images.githubusercontent.com/26907216/90822863-1120f100-e303-11ea-9c51-c00b21d78913.png
I'm on Paper 1.6.1-136
Plugins (25): ActionHealth*, AuthMe, BannerMaker, Chunkmaster, DeadChest, dynmap*, Essentials, EssentialsAntiBuild, EssentialsChat, EssentialsProtect, EssentialsSpawn, ImageOnMap, LuckPerms, LWC, LWCTrust, OpenInv, PlugMan, ProtocolLib, SetHomes*, SinglePlayerSleep, SkinsRestorer, Timber, Vault, WorldEdit, WorldGuard
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/aikar/timings/issues/102, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJMAZD7MNH6SAH7D6GNE5LSBWGYXANCNFSM4QGSKTKA.


support for multiple download urls

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm requesting a feature unrelated to a specific site
[X] I've looked through the README
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
I tried to assign an array of strings to url of formats in the extractor, but it won't work.
It seems that currently the url field only accepts a single string?
What I was trying is to enable the downloader to have some backup urls so if the first one failed or too slow, the downloader would use next one in the array.
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

I don't understand what you are trying to do or what have already tried.
Please try to rephrase what it is that you are trying to achieve.
Show a log, or, at the very least, show the example commands/code you have tried.

I believe what they are asking for is #1986, but for other sites

I believe what they are asking for is #1986, but for other sites

Yes, that's what I mean. And the fallback_url approach would also work for me.
Right now I have only investigated the extractor part, but not the downloader part yet.
Please kindly notify me when the downloader is ready for mutiple fallback urls.

Oh and the issue is well described in #1986. Maybe closed as dup?

For now, you can return the different URLs as different formats so user can choose b/w them with -f or use --check-formats to skip any broken ones

closing as dup


Arduino serial integration

Now the web interface is able to read from the arduino serial via USB.
By using AP_command.py it is also possible to control the AP from the command line without breaking the web interface.

Approved


add --rename-tag

This could be quite useful, I think.  In written material, I always seem to find that an initial tag name starts to feel awkward as time progresses. Often a detailed initial tag starts to feel longer than it needs to be.  But, just as often, a short initial tag proves to be ambiguous.
When I do this, I'll also make the test suite check it.  I'm adding too many things, testing only by hand, and that's a recipe for problems down the road.

Hm, in doing local tests, I noticed three problems with python.

WARNING: Error parsing dependencies of arabic-reshaper: Expected matching RIGHT_PARENTHESIS for LEFT_PARENTHESIS, after version specifier
fonttools (>=3.0<4.0) ; (python_version < "3") and extra == 'with-fonttools'
~~~~~~^

Installing collected packages: diary
...
DEPRECATION: Configuring installation scheme with distutils config files is deprecated and will no longer work in the near future. If you are using a Homebrew or Linuxbrew Python, please see discussion at https://github.com/Homebrew/homebrew-core/issues/76621

Something about datetime is deprecated in the sqlite3 interface, but when I search for that on the web, I don't find any solutions.

I don't recall seeing number 3 with nota, but I guess I haven't built it for a couple of years.  The python ecosystem doesn't seem to be as professional as the R ecosystem.


Scripts not permitted to use staticMethod

Hello,
I got error during running pipeline
Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods
How to fix this issue fr jenkinsfile-runer ?

Whitelist the method. E.g. via JCasC once https://github.com/jenkinsci/script-security-plugin/pull/219 is done
Install the Permissive Script Security Plugin and disable sandbox (not recommended)

I’ve installed plugin, but I can’t figure it out how to enable it because there is no file jenkins.xml.
The plugin is disabled after installation. It can be enabled providing -Dpermissive-script-security.enabled=true property to Jenkins master JVM. Since 0.3, value no_security is supported to permit not whitelisted signatures without any logging. Note that this is not secure at all

It can be enabled providing -Dpermissive-script-security.enabled=true property to Jenkins master JVM

You need to pass a system property

It can be enabled providing -Dpermissive-script-security.enabled=true property to Jenkins master JVM

You need to pass a system property

I am sorry, but I don't know how to do it, because jenkinsfile-runner execute Jenkins...so How to do it ?

Could you shed some light on passing JVM params to Jenkins master or whitelisting methods?
I'm having the same problem.

We keep running into this, but seems like it only happening when we use Container folders.
I can't say I understand the suggested fixes (especially this -> 2. Install the Permissive Script Security Plugin and disable sandbox (not recommended) ), I'm very new to Jenkins.

@uridium , @ReddyKilowatt:
first install Permissive Script Security Plugin
after build jenkinsfile-runner by mvn edit( or create copy and edit new one) file app\target\appassembler\bin\jenkinsfile-runner (or jenkinsfile-runner.bat for Windows).
Then add parameter  -Dpermissive-script-security.enabled=true do line which start with %JAVACMD% %JAVA_OPTS%  .

https://github.com/jenkinsci/jenkinsfile-runner/pull/26 has been released in 1.0-beta-7 (Changelog is coming soon). With this update you can use the --no-sandbox flag to disable sandboxing in Jenkinsfile Runner without complex solutions.
Closing this ticket, please feel free to reopen if anything left to be done here


Added coverall configuration

@bshaffer
Hi, I'm adding coveralls configuration. Can you take a look?
FYI, here is a coverage report for this PR:
https://coveralls.io/builds/4349893
Thanks!

Cool, thanks man!


Persistent table : wrong redirection in case of multiple CRUD for same entity

Bug report
This is a really edge case, but still ^^
When having multiple CRUD pointing to the same entity, and persistant tables, the JS redirects to the first view whose list url has been saved in localstorage.
What I did:
Define 2 CRUDs with the same $crud->entity_name_plural, with different access roles.
Some user might change access roles during a session, and access the 2 CRUDs one at the time
What I expected to happen:
The user can access each CRUD normally
What happened:
The user can access the first CRUD, but is redirect when accessing the second one.
Due to list entry filter persistance (https://github.com/Laravel-Backpack/CRUD/pull/1702), when accessing the second CRUD, and as the localstorage key for storing persistant filter list is the entity_name_plural, the user is redirected to the first CRUD. In my case, if the user also changed roles, he ends up getting a 403.
What I've already tried to fix it:

Turning off Persistant storage of one of the CRUD.
--> but that's a loss of a really cool feature!

Changing the localstorage key with the slugified route seems to do the job.
Something like this made it work, but hasn't been tested thoroughly :

in  CRUD/src/resources/views/inc/datatables_logic.blade.php line 12-15

var saved_list_url = localStorage.getItem('{{ $crud->entity_name_plural }}_list_url');
if (saved_list_url && saved_list_url!=window.location.href) {
    window.location.href = localStorage.getItem('{{ $crud->entity_name_plural }}_list_url');
}

changed by

var saved_list_url = localStorage.getItem('{{ str_slug($crud->getRoute()) }}_list_url');
if (saved_list_url && saved_list_url!=window.location.href) {
    window.location.href = localStorage.getItem('{{ str_slug($crud->getRoute()) }}_list_url');
}

in  CRUD/src/resources/views/inc/datatables_logic.blade.php line 42
localStorage.setItem('{{ $crud->entity_name_plural }}_list_url', new_url);
changed by
localStorage.setItem('{{ str_slug($crud->getRoute()) }}_list_url', new_url);
Backpack, Laravel, PHP, DB version:
3.5, 5.7, 7.1, 5.7

Wow - indeed a niche problem but I'm very happy you've provided a solution. Thank you @7ute let's move the conversation inside the PR - which I'm merging now.
Thanks again, cheers!


OT spans should be reported using the sdk span type

Spans are currently reported in generic form.  Using the SDK will allow for better handling, processing and presentation.

Also, this PR expands on the test suite a bit.


Multiple additional fans?

This might be more of a question than a bug/problem... most like me not knowing how this works more... and first of all, thank you for all his great work!! This is exactly what I was about to build, did a quick search and saw you had already done it!!
I have a creality k1 max with a bunch of fans... there's the MCU, hotend electronics fan, hotend parts fan, an aux part cooler on the side, and a chamber fan in the back... I see all of those fans in my fluidd dashboard, but I'm not sure how to configure the collector to grab all of it. Is there a way to have get those additional metrics?

I'm actually going to close this, I found what I was looking for.
For anyone wondering, the values I was looking for could be found in the klipper_output_pin_value metrics. The fans and LED brightness are all there reported in values of 0 to 1, 0 being off, 1 being 100%. I'm assuming this is the PWM duty cycle of those pins... I'll eventually hook it up to my oscilloscope and measure it directly to be sure, but from the flicker I get from the builtin camera when the LED is set to anything other than 100%, I'm pretty sure that's the case!


Pagination options - infoFn shows incorrect data. totalPage parameter is always undefined.

Issue Type (delete the irrelevant ones)

[x] Bug

Specs
What version are you using?
2.21.10
What browser?
Chrome Version 90.0.4430.212 (Official Build) (64-bit)
Expected Behavior
What did you expect to happen?
The parameter - totalPage in the info-fn pagination options should return valid value.
Actual Behavior
What actually happened?
The parameter - totalPage is returning undefined.
Steps to Reproduce the Problem
I am trying to implement my own function to layout pagination information.
Steps :

Run the app using the basic example from getting started documentation.
Set your own page labels and pagination info function under the pagination-options.
Add the following line in pagination-options of your app, so that you use totalPage paramter :

infoFn: (params) =>
`Showing ${params.firstRecordOnPage} to ${params.lastRecordOnPage} of page ${params.currentPage} out of ${params.totalPage} pages. Total Records: ${params.totalRecords}`,

jsfiddle
If you provide a jsfiddle reproducing the issue, it'll be addressed much faster.
you can use this as base
https://jsfiddle.net/mkx60gp7/

use ${params.totalPages} instead of ${params.totalPage}
it works


feat: transactions/fees endpoint

Adds the transaction/fees endpoint.

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Refactor
[ ] Performance
[ ] Tests
[ ] Build
[ ] Documentation
[ ] Code style update
[ ] Continuous Integration
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Does this PR release a new version?

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the develop branch, not the master branch
[x] All tests are passing
[x] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Thanks for submitting this pull request! A maintainer will review this in the next few days and explicitly select labels so you know what's going on.
If no reviewer appears after a week, a reminder will be sent out.

Looks good to me

A contributor has approved this PR. A maintainer will merge this PR shortly. If it shouldn't be merged yet, please leave a comment saying so and we'll wait.
Thank you for your contribution!

@faustbrian
This looks good to go 👍
Thank you, @dated


v3

By now, only one issue is missing to fix. When you don't have the separated code tab visible, then when you come back to the tab the file is being deleted. The file should only get deleted when you close the file.

Now, the principal issue is that if you undo a change from the original tab, then the selection will increase considerably in each undo.

Issues founded so far:

[ ] If you close the original file while the separated code is open, and then you start writing on the original file, then the original file will open again, but this time you cannot edit on the original file, it's like locked.
[ ] An increase of several lines after undo on original file.
[ ] Saving is being triggered automatically on the original file if you write fast enough, it should only be trigger if you save the separated code.


[FLINK-12619][StateBackend]Support TERMINATE/SUSPEND Job with Checkpoint

What is the purpose of the change
Inspired by the idea of FLINK-11458, we propose to support terminate/suspend a job with checkpoint. This improvement cooperates with incremental and external checkpoint features, that if checkpoint is retained and this feature is configured, we will trigger a checkpoint before the job stops. It could accelarate job recovery a lot since:

No source rewinding required any more.
It's much faster than taking a savepoint since incremental checkpoint is enabled.

Please note that conceptually savepoints is different from checkpoint in a similar way that backups are different from recovery logs in traditional database systems. So we suggest using this feature only for job recovery, while stick with FLINK-11458 for the upgrading/cross-cluster-job-migration/state-backend-switch cases.
The current commit does not include rest API(will do this by follow up issue  FLINK-12733.
Verifying this change
This change added tests and can be verified as follows:

CliFrontendStopTest.java#{stopWithCheckpoint, testStopWithCheckpointWithMaxWM, testStopWithCheckpointAndSavepoint}
CheckpointPropertiesTest.java#testSyncCheckpoint
CheckpointTypeTest.java #testOrdinalsAreConstant
PendingCheckpointTest.java #testSyncCheckpointCannotBeSubsumed
CheckpointSerializationTest.java
EventSerializerTest.java #testIsEvent
SynchronousCheckpointITCase.java
SynchronousCheckpointTest.java

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (JavaDocs)
@aljoscha @StefanRRichter

From a first glance I agree with @carp84's comments that we should prevent code duplication as much as possible. Regarding CANCEL-WITH-SAVEPOINT, I don't think we need to worry about this one since STOP-WITH-SAVEPOINT is meant to replace this in the long run. We only left this in for now to now break the REST API/CLI.

thanks for your reviews @carp84 @aljoscha  will address all your comments.

We should of course wait until the discussion on https://issues.apache.org/jira/browse/FLINK-12619 has converged.

Since we reached a consensus after some nice and constructive discussion with @aljoscha , let's resume the review here. Please do necessary rebase and refactor to prepare a new PR @klion26 , thanks.

@aljoscha @carp84 I've rebased the master and addressed the comments, please have another look when you're free, thanks.

Seems the failed test is related, I'll fix it.

Have fixed the failed test.
I think we may add a configure autoCheckpoint (whether to trigger a checkpoint when canceling a job), and when canceling a job, we'll do a checkpoint automatically if the  autoCheckpoint is true. what do you think @aljoscha

@klion26 I would suggest to keep autoCheckpoint to a separate Jira issue and PR. And focus this PR on purely the stop-with-checkpoint functionality.

@aljoscha thanks for the reply, will create a separate Jira issue to that.
close and reopen the pr for trigger another Travis test.

Seems Travis build is broken now(all builds failed), I'll retrigger another build when Travis build is ok.

Seems Travis build is ok now, close and reopen to trigger another build.

What if the checkpoint is timeout, the task will block all the time?

Hi, @yumengz5  what do you mean "task will block all the time?", would you mind explain it more?

In my opinion, If the checkpoint is timeout,  this checkpoint will be discarded. But the checkpoint coordinator would handle such abortion as usual and assume that the Flink job continues running. In fact, it looks like "running", but it doesn't process any records. In sync-checkpoint case, every task will be blocked after triggering the checkpoint. Unlocking only happens either when the task is cancelled or when the corresponding checkpoint is acknowledged. I guess stop-with-savepoint may have the same issue. I'm not sure it will truly happen.

I'm not sure I fully follow what you mean, in the following, I'm trying to answer your question. Please correct me if I'm not understanding right.

If you mean "the sync checkpoint/savepoint" is timeout, then the pendingCheckpoint will be abort, and the onCompletionPromis will complete with an exception, the job exit.
Currently, when stopping a job, the task will not exit, if you want the task exit, could use cancel instead of stop

The onCompletionPromis does complete with an exception, if the pendingCheckpoint has been abort, but the job will not exit and its tasks will not resume to execute because you don't notify the syncLatch. For second part, I don't want the tasks to exit. I just want them to unblock and resume to execute.

Currently, Flink doesn't' notify task about the expired checkpoint now, FLINK-8871 will fix it. After FLINK-8871 has been fixed, we can do better here.
Thanks for your comments.


CSS SHIZLEZ

Hai I need the following Views cleaned up:
Auth/*
form/* - Align the boxes properly
shows/show -> Fixed up the People section
emails/*
---Please re-english them, format them a little, shove our logo in there.
Admin/applications/* - I think they might need a lot of work
Admin/useredit
Admin/users
Admin/show/*

What needs to be done for the clean up of auth/?

The lay of the login / registration pages isn't aligned

Clean up for back-end interfaces (including #10) has been pushed back to release v0.3 since it's not a major change


Add zloss

Anything we can do to get this merged? We want to polish the OLMoE release, and it would be nice if we could just take a dependency on your version instead of @Muennighoff's.

@Muennighoff can you resolve merge conflicts and make sure tests are passing?
CC: @josejg  for review

I believe the current implementation will consume extra memory even when z-loss weight is zero. Even though the tensors are small, I always worry about keeping stuff around messing with the mem allocator. When we tested this, we had the zloss tensors separate from the LBL loss using a separate global variable and helper methods, which wouldn't save the logits if the zloss is disabled.

I'm also not fan of changing the Router and Experts API (returns and arguments) since that is not backwards compatible. In our implementation, the z-loss was handled entirely in router.py, which prevented this.

Similar for changing the API of batched_load_balancing_loss which now returns a tuple instead of a value, not backwards compatible. With our implementation the separate function prevents this.

Lastly, we did not observe any meaningful improvements when enabling router zloss, so I would keep it at a default of 0 instead of 1e-3 to prevent the computation in the default case and for backwards compatibility. I see Figure 11 in the OLMoE paper reports stability improvements but I guess the training settings are different.

Here's our implementation for reference - https://github.com/databricks/megablocks/compare/main...josejg/zloss . The main difference is that the modeling code is responsible for doing clear_router_zloss and batched_router_zloss in the corresponding places.
@mvpatel2000  Wdyt?
@Muennighoff could you refactor the PR to address these comments? We can also merge our implementation giving you credit in the PR if that's easier.

oh just merge yours 👍

Sg, tracking it here - https://github.com/databricks/megablocks/pull/151

Closing in favor of https://github.com/databricks/megablocks/pull/151
@Muennighoff  @dirkgr  please feel free to comment on other PR if you need any related changes or you can open a github issue :)


mailbox-server implementation

i thought on this a little bit and i like the idea for a simple k/v store since it's minimal and very fast.
the part i'm not grasping is if we implement a deletion period of x-days do we introduce theoretical duplicate addresses somewhere or perhaps duplicate patients?
e.g:

john catches a bug
john has an address on the backend
john recovers after x time
john's information no longer needs to persist
john goes to live a long life
john 6 weeks later gets infected with a new pathogen
john's address was deleted

would we consider it a new case, thus a new address?
also out of context a bit, if i'm thinking what you may be thinking this would be a good time to discuss async and time-delayed messaging.
edit: ok i read the mixer design spec, so this would likely cover async/time-delay
@JonathanLogan @frankbraun

The addresses on the server are only for receiving messages, hence, if john recovers he sends his recovery status to his contacts. in the meantime, he collects new contacts. he then gets sick again and only contacts those collected in the timeframe before his new test.


Differentiate prerequisite and event issue15

Problem:
Need distinction between what is a prerequisite for a program and an event of a program
This PR fixes issue #15
Solution:
Added programId to event:
In the programevent model there is a column for programId add that column inside of the event model. This way it is clear what event belongs to which program.
Made Table called preqForProgram:
There was no way to tell if an event was required for a program. The preqForProgram contains two fields programId and eventId. The programevent model was renamed preqForProgram after transferring the programId column.
Created a program called training:
The training program contains many events and some of those events are prereqs for multiple other programs. We created  Training program (in test data), added multiple events to it, and assigned those events as prereqs for other programs.
We also refactored the code in /app/logic/events.py and added preqForProgram model migrate_db.sh .
Test:
Run ./reset_database.sh test and check the database to see if preqForProgram is added and column_id is added to event table. prgramEvent should no longer exist.
Run tests again and they all should pass.

The whole reason we created ProgramEvent is that there are events that are in more than one program, meaning program_id in Event doesn't work.
You need to remove that part of these changes.

Training is not a separate program. Programs are specific CELTS initiatives. Events within a program can be classified as a training. I thought we said that isRequiredForProgram indicated a training?
If we want to make that clearer we can have other boolean flags. Like, we could do isTraining, or isPrerequisite, or isRequired. But creating new tables doesn't give us additional functionality that we need.

@Sandesh-L @sreynit02
Any update on this PR?

@Sandesh-L @sreynit02
Any update on this PR?

Sorry, I accidentally closed the PR by accident.


Add notifications table to the admin app

Description
In order to more easily debug which notification emails are sent to whom, we needed a way to view them in the admin app.
Reviewer Notes
You may notice that I've introduced a more generic service object (using interface{} as its secret sauce) that allows fetching lists of records for any table. I've made use of it here for fetching notifications and, for the sake of example, replaced the office user list fetcher. Clear, consistent patterns have emerged across our service objects and I'd like to save on some boilerplate, so I'll be trying to trim more fat in the same way in forthcoming PRs. Let me know what you think!
Setup

make server_run
make client_run
Log into the admin app and click on Notifcations in the sidebar

Code Review Verification Steps

[x] Request review from a member of a different team.
[ ] Have the Pivotal acceptance criteria been met for this change?

References

Jira story for this change

@lynzt and @donaldthai I've addressed your comments. Thanks for the thorough review!


Release 0.2.1

See #44. I can't build the 0.2.0 release from crates.io. The PR represents the state of the repo when I published a 0.2.1 release.
I started by publishing a 0.2.1-alpha release. The alpha release was needed to put us in a good state to build and release 0.2.1. While stepping through the 0.2.1 release, I wrote some notes on how I did the release. I put the notes at docs/RELEASE.md.
Show that both crates build when referenced from crates.io:
RAL:
cd /tmp
cargo new --lib test-ral
cd test-ral
echo 'imxrt-ral = { "version" = "=0.2.1", features = ["imxrt1062"] }' >> Cargo.toml
cargo build

HAL:
cd /tmp
cargo new --lib test-hal
cd test-hal
echo 'imxrt-hal = { "version" = "=0.2.1", features = ["imxrt1062"] }' >> Cargo.toml
cargo build

0.2.1 release works in the teensy4-rs project. I didn't supply a tag. But, the actual release occurred at 28c995a.

A change to a markdown file (3a55171d5fe0b55585be67c165f2940bfa8be211) broke the build... 😮

Nevermind, I tried harder, re-ran the jobs, and they all pass now 😛I'll keep an eye on that.

I might have introduced CI flakiness by removing the RAL's Cargo.toml file. Here's the first batch of jobs that failed on 3a55171. Does the cache not include the auto-generated Cargo.toml file? Let me know what you think; I'm happy to revert a95bf24 if we need.


Invisible button with "back" behavior

Is this a bug report?
Yes

Have you read the Installation Instructions?
Yes
Environment

react-native: "0.55.4"
react: "16.4.1"
react-native-maps: "0.21.0"
react-navigation: "2.13.0"
Steps to Reproduce

Create a regular stack navigator using react-navigation
Create a MaterialTopBar navigator within another screen
Include a MapView within a random tab
Click on the left top of the map, you'll be moved back

Expected Behavior

Render a very basic map, nothing else.
Actual Behavior
It seems to place an invisible button, that when pressed, moves back to the previous activity. I'm using react-navigation, but it doesn't show up when rendering another view instead of the map. Switching around the tabs doesn't work either, as it just makes the button show up on the map on another tab.

Reproducible Demo

I'm unable to properly get this running on https://snack.expo.io (getting errors and the device is very unresponsive), so I'm pasting the part of the code I'm having issues with here. I stripped all my own logic, that is further not needed to reproduce the steps.
import React, { Component } from "react";
import { View, StyleSheet } from "react-native";
import PropTypes from "prop-types";
import MapView from "react-native-maps";

class MapScreen extends Component {
	constructor(props) {
		super(props);
	}

	calculateDelta(latitude, longitude, zoom) {
		const oneDegreeOfLatitudeInMeters = 111.32 * 1000;
		const latitudeDelta = zoom / oneDegreeOfLatitudeInMeters;
		const longitudeDelta = zoom / (oneDegreeOfLatitudeInMeters * Math.cos(latitude * (Math.PI / 180)));

		return {
			latitude,
			longitude,
			latitudeDelta,
			longitudeDelta
		};
	}

	render() {
		return (
			<View style={{ ...StyleSheet.absoluteFillObject, justifyContent: "flex-end", alignItems: "center" }}>
				<MapView
					style={{ ...StyleSheet.absoluteFillObject }}
					ref={ref => { this.map = ref; }}
					initialRegion={this.calculateDelta(51.43581846832452, 5.475311279296875, 4000)} />
			</View>
		);
	}
}

export default MapScreen;

Try a lower version of the navigator, like 2.12.1

Resolved it by removing react-native-elements and react-native-vector-icons package which is used in the header.

@vbhv19 I have neither of these modules installed. I can't see them anywhere in my node_modules folder either.


Hcall and Qcall implementation update

Use shared memory for message exchange, ensure all the data in the message and the the data pointed by the pointer in the message are allocated in the shared memory.

Can you please fix the indentation, e.g., on unsafe{} blocks?

Can you please fix the indentation, e.g., on unsafe{} blocks?

I'd suggest we add a rustfmt specs for this codebase for consistent (and most importantly, automated) coding style.

Can you please fix the indentation, e.g., on unsafe{} blocks?
Could you give me a more detailed example? How would you like me to fix these unsafe blocks for indentation?