RTAB-Map support in Autoware for SLAM

Feature request
Description
Taken from the first sentence of http://introlab.github.io/rtabmap:

RTAB-Map (Real-Time Appearance-Based Mapping) is a RGB-D, Stereo and Lidar Graph-Based SLAM approach based on an incremental appearance-based loop closure detector.

RTAB-Map works with multiple input sensors (odometry, stereo, RGB-D and LiDAR), works also with single input sensor, and output pose, occupancy maps (2D and 3D) and the pointcloud.
But most importantly, it is able to do large scale loop closure.
From their JFR paper (J Field Robotics. 2019;36:416–446), here is a comparison of ROS-compatible approaches (note NDT is missing)

and this is the general architecture:

It has large area loop closure. Check this video:
https://www.youtube.com/watch?v=qpTS7kg9J3A
in particular from 9:17 where it closes correctly the loop.
https://youtu.be/qpTS7kg9J3A?t=557
Implementation considerations
RTAB-Map is already on ROS farm (http://wiki.ros.org/rtabmap_ros) however it has never being tested on Autoware and not for a vehicle.
Alternatives
NDT but has to be largely modified to support Graph SLAM, that is a work on progress but will not be ready for 1.12. And even if NDT supported graph SLAM, RTAB-Map is superior for it works with several sensors.
Additional information
Several field tests will be performed to make sure RTAB-Map performs as well as NDT for mapping and that it can be used for localization.

Hi, finally is that planned to integrate RTAB-map in autoware new versions?
And possibly replace NDT for mapping and localization tasks?
Actually, is there any comparison available between these two methods?


[QUESTION] How can I install longhorn storage on dedicated node drives e.g. /dev/sdb

Question
Like the title says, I did not yet find in the documentation a example, where I can install longhorn on a list of devices available on my nodes (e.g. /dev/sdb) that are formatted, have no file-system and are not mounted
Preferably I would like to install longhorn with a setting like this:
nodes:
- name: node1
  devices:
    - /dev/sdb
- name: node2
  devices:
    - /dev/sdb
- name: node3
  devices:
    - /dev/sdb
    - /dev/sdc
- node4
  devices:
    - /dev/sdb
    - /dev/sdc
    - /dev/sde

Or in a simpler version if all nodes have the same disk device.
devices: /dev/sdb
nodes:
- node1
- node2
...

Is something like this already possible?

Hi, had you checked the doc yet?

Hi, yes and I did not find an answer to my question...
1) To add a new disk for a node, head to the Node tab, select one of the nodes, and select Edit Disks in the dropdown menu.
I do not want to use a UI to configure this post-installation
2) If you don’t want to use the original mount path of a disk on the node, you can use mount --bind to create an alternative/alias path for the disk, then use it with Longhorn
My disks are not mounted. This presumes they are mounted and a file-system already created on them. This is possible, but not what I want (even though I can still do it that way)
My question is if it is possible to use devices directly without them having to be prepared in advance?

No, you must format and mount the disk before Longhorn can it.

Ah ok. Was hoping it could use devices directly like OpenEBS or Rook/Ceph do
Then this could also be a feature request :)


After update, server connection not triggering Ray()

Describe the bug
I connect to my staging and prod servers on Ray. Then trigger a ray() event on the server, nothing pops up. On local it isn't a problem.
To see Ray working, I created a new command called ray:test
public function handle()
    {
        ray('Is it working');
        return 0;
    }

When I run it locally, it works.

I then push to Git and deploy the exact code to my staging server. In Ray I add the staging server credentials and connect with no issues. When I trigger ray:test on the staging server, nothing appears. It used to work on older releases and seems to be happening after the latest update.
Versions
2.0.1
spatie/backtrace                     1.2.1   A better backtrace
spatie/laravel-ray                   1.29.4  Easily debug Laravel apps
spatie/macroable                     2.0.0   A trait to dynamically add methods to a class
spatie/ray                           1.34.1  Debug with Ray to fix problems faster
PHP version:
8.0.x
Expected behavior
Expected to see a new Ray window that is connected to my server when triggering a ray() event
Desktop (please complete the following information):

MacOS: 12.3.1
Version 21E258
Apple M1 Max

I have the same problem


jetson_stats as well as jetson-fan-ctl

I have jetson_stats on my machine and it has a service that controls when jetson_clocks is run... Will jetson-fan-ctl upset that given the config files has a MAX_PERF value which causes jetson_clocks to be run?

Hi,
if you control jetson_clocks in another program, I'd recommend setting MAX_PERF to 0 and just let your other program handle it.
The MAX_PERF flag only runs jetson_clocks once at boot time.
If you disable MAX_PERF, then automagic-fan will only control the fan speeds.
Your other program would probably just override the one-off value set by automagic-fan, but if you want to be safe, then just disable MAX_PERF and let your other program handle clock speeds.
Hope this helps!

Thanks @Pyrestone. That’s what I was thinking so have set to 0.
I just notice that the power setting on the Xavier is dropped back to the bottom setting every. One and then and I’m trying to work out why.
Anyway great stuff on the fan control!!   ;-)


Fix web3 dependency

Web3 dependency should be >= and not ==

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.457%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2257

Relevant Lines:
2523

💛  - Coveralls


Store topographies in flexible backend

User Story
As provider of the web service we want to store all the topography data in order to be able to do machine learning on it or publish the data someday.
As researcher I want to collect my topography data at one place in order to (re)perform calculations on different topographies easily.
As provider we want to be able to switch the backend later in order not to be dependent on one provider (e.g. SciServer).
Acceptance Criteria

a user can upload his topographies, logout, login again later and see details on already uploaded data
we as provider have the possiblity to use all topography data uploaded by the users
the backend is used via a common interface so that it could be theoretically exchanged

The first supported backend is the local filesystem. It should be possible to extend the application later by saving the data in the sciserver infrastructure (volumes).
Should the user be able to switch backend systems? How are the files moved then?
Some more description work needed here.

I think this is out of scope now that we are starting to work with distribution of Data directly from S3 with presigned keys.


Remove formatting by default

While cross compiling (in particular to duckdb-wasm) linter does fail, so having some kind of escape hatch would be nice.
It also seems to me that it's somehow wasteful to iterate those check on every build. Would it make sense to have either them turned off by default (both for this and for the underlying library)?
Would it be possible to have this turned off by default ? Or alternatively having ENABLE_LINTING set to TRUE (so keeping same behaviour) but at least it becomes possible to opt-out?
Thanks!

I have a slightly modified version of this in #86, could you take a look at whether that works as well? It preserves the option to run automatic code formatting but keeps it off by default.


Move multiple types of out HeadLogic

[x] ClientInput -> Hydra.ClientInput
[x] Snapshot -> Hydra.Snapshot
[x] ServerOutput -> Hydra.ServerOutput
[x] HydraMessage -> Hydra.Network.Message (and renamed to just Message, required Heartbeat's Message to be named differently and I picked Data)
[x] OnChainTx -> Hydra.Chain
[x] Introduce a ChainComponent and refactor Hydra.Chain.ZeroMQ into this pattern as withMockChain

I would have done something like:

move types like ClientInput -> Hydra.HeadLogic.ClientInput
reexport the types from Hydra.HeadLogic module.

This reduces the impact of this change as no imports need to be updated, while still reducing the footprint of HeadLogic and improving its readability.


How does Flutter jump to Android native Activity?

How does Flutter jump to Android native Activity?

@gionchat
Your question indicate you want to know how that process work and not necessarily a bug or feature request for which this repo is mainly for. Please see https://flutter.dev/community for resources.
You may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


enhancement: return 404 when identity verification does not exist

The type of this PR is: Enhancement

This PR solves PLATFORM-4165
Description

This is a followup to https://github.com/artsy/force/pull/10263. After removing this logic and the wrong-owner component I introduced a regression and so now when requesting an identity verification that does not exist the client throws a 500 internal server error whereas before we rendered a wrong-owner component.
To address this regression I thought it would be good to return a 404 when an identity verification is not found.
Before https://github.com/artsy/force/pull/10263:

Now:

@damassi i've tried a few different ways to write a test for this state but haven't been able to nail it down. I thought it would be good to cover this state here. I tried the following thinking that if response comes back null, it would hit that condition but that doesn't seem to work.
      it("returns a 404 when the identity verification is not found", async () => {
        const env = setupTestEnv()
        const page = await env.buildPage({
          mockData: deepMerge(IdentityVerificationAppQueryResponseFixture, {
            identityVerification: null,
          }),
        })

        expect(page.text()).toContain("404")
      })

A simpler way to test this would be to assert that the page throws an error. Try this:
expect(async () => {
  await env.buildPage({
    mockData: deepMerge(IdentityVerificationAppQueryResponseFixture, {
    identityVerification: null,
  }),
}).toThrow()


Revert back to the previous Sass path

We’ve had multiple reports of failure importing Bourbon, specifically within Rails apps:
Failure/Error: @import "bourbon";

     ActionView::Template::Error:
       File to import not found or unreadable: bourbon.
       Load paths:
         /home/ubuntu/bungalow/vendor/bundle/ruby/2.3.0/gems/babel-source-5.8.35/lib
         /home/ubuntu/bungalow/app/assets/images
         /home/ubuntu/bungalow/app/assets/javascripts
         /home/ubuntu/bungalow/app/assets/stylesheets
         /home/ubuntu/bungalow/vendor/assets/javascripts
         /home/ubuntu/bungalow/vendor/assets/stylesheets
         /home/ubuntu/bungalow/vendor/bundle/ruby/2.3.0/gems/normalize-rails-3.0.3/vendor/assets/stylesheets
         /home/ubuntu/bungalow/vendor/bundle/ruby/2.3.0/gems/jquery-rails-4.1.1/vendor/assets/javascripts
         /home/ubuntu/bungalow/vendor/bundle/ruby/2.3.0/gems/bourbon-5.0.0.beta.4/core/home/ubuntu/bungalow/vendor/bundle/ruby/2.3.0/gems/bourbon-5.0.0.beta.4/core

Related: https://github.com/thoughtbot/suspenders/issues/727

Looks good!

:+1:


X-Pack License not installing, only getting trial license

Module version: 6.3.3
Puppet version: 5.5.8
OS and version: CentOS 7.6
ES Version: 5.6.14

Bug description
X-Pack License is not installing.
Here is the relevant puppet code:
  include elasticsearch
  include java

        elasticsearch::instance { $instance_name:
          ensure => present,
          config => $config_hash,
        }

Here is the relevant hieradata: (partially obfuscated)
elasticsearch::license:
  uid: 41bXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
  type: platinum
  issue_date_in_millis:<PHONE_NUMBER>000 # May 31, 2018
  expiry_date_in_millis:<PHONE_NUMBER>999 # June 6, 2019
  max_nodes: 10
  issued_to: A Company
  issuer: Magdalena Kowalska
  signature: >
    (censored)
  start_date_in_millis:<PHONE_NUMBER>000

I can see it in the catalog on the server /opt/puppetlabs/puppet/cache/client_data/catalog/$(hostname}.json
It is populated correctly, so I do not think that it is related to the hieradata or puppet code.
Here is  an excerpt of jq . (catalogfile):
    {
      "type": "Elasticsearch_license",
      "title": "xpack",
      "tags": [
        "elasticsearch_license",
        "xpack",
        "class",
        "elasticsearch::license",
        "elasticsearch",
        "license",
        "profile::elasticsearch",
        "profile",
        "role::elasticsearch",
        "role",
        "node",
        "default"
      ],
      "file": "/etc/puppetlabs/code/environments/des_qa/modules/elasticsearch/manifests/license.pp",
      "line": 90,
      "exported": false,
      "parameters": {
        "ensure": "present",
        "content": {
          "uid": "41bXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
          "type": "platinum",
          "issue_date_in_millis":<PHONE_NUMBER>000,
          "expiry_date_in_millis":<PHONE_NUMBER>999,
          "max_nodes": 10,
          "issued_to": "A Company",
          "issuer": "Magdalena Kowalska",
          "signature": "AAAAA(censored)\n",
          "start_date_in_millis":<PHONE_NUMBER>000
        },
        "protocol": "https",
        "host": "sea1l2dcesa01.company.corp",
        "port": 9200,
        "timeout": 30,
        "username": "elastic",
        "password": "changeme",
        "ca_file": "/etc/pki/elastic/ca/ca.crt",
        "validate_tls": true,
        "provider": "xpack"
      }
    }

I have added some Puppet.debug statements into the xpack.rb in the only method (process_body) and it appears to show the trial license in there, so I am pretty sure it is getting the license.
As I have mentioned elsewhere, we are getting the following warning, but I do not think it is relevant either:
Warning: Found multiple default providers for elasticsearch_license: shield, xpack; using shield

Puppet debug output:
Debug: Executing: '/bin/systemctl is-active elasticsearch-es-01.service'
Debug: Executing: '/bin/systemctl is-enabled elasticsearch-es-01.service'
Debug: Connected to the ES instance in 0.000395336 seconds.
Debug: Prefetching xpack resources for elasticsearch_license
Debug: xpack - process_body - body: {
  "license" : {
    "status" : "active",
    "uid" : "9ec2d3c9-5e01-45b0-b4ef-8b3701281ec1",
    "type" : "trial",
    "issue_date" : "2019-03-18T23:55:03.415Z",
    "issue_date_in_millis" :<PHONE_NUMBER>415,
    "expiry_date" : "2019-04-17T23:55:03.415Z",
    "expiry_date_in_millis" :<PHONE_NUMBER>415,
    "max_nodes" : 1000,
    "issued_to" : "des_qa",
    "issuer" : "elasticsearch",
    "start_date_in_millis" : -1
  }
}

Debug: elastic_rest - results: [{:name=>"xpack", :ensure=>:present, :content=>{"license"=>{"status"=>"active", "uid"=>"9ec2d3c9-5e01-45b0-b4ef-8b3701281ec1", "type"=>"trial", "issue_date"=>"2019-03-18T23:55:03.415Z", "issue_date_in_millis"=>1552953303415, "expiry_date"=>"2019-04-17T23:55:03.415Z", "expiry_date_in_millis"=>1555545303415, "max_nodes"=>1000, "issued_to"=>"des_qa", "issuer"=>"elasticsearch", "start_date_in_millis"=>-1}}, :provider=>:xpack}]

I have to assume that something is breaking where it is comparing the values, but I have no idea where that is happening. Not really an expert on types/providers. :)
NOTE: We did previously add debug statements to print the URI and response in "rest" but did not see any attempt to POST the corrected license details.
Any assistance is appreciated.

The only thing I have noticed that is somewhat out of place would be the \n at the end of the signature. I used eyaml encrypt -f which got the newline at the end. However, I would think, that if there was an error comparing the values or installing the new license, I would see something about it.  (shrug)

I'm having the same issue.
The hash is correct and elasticsearch_license is reporting content changed however it doesn't actually apply. It will report change on every subsequent run.
Notice: /Stage[main]/Elasticsearch::License/Elasticsearch_license[xpack]/content: content changed {
  'license' => {
    'status' => 'active',
    'uid' => '038e1b29-50c3-4442-9cee-e7bdaad4b06d',
    'type' => 'basic',
    'issue_date' => '2019-11-06T11:33:07.213Z',
    'issue_date_in_millis' =><PHONE_NUMBER>213,
    'max_nodes' => 1000,
    'issued_to' => 'strata_logs',
    'issuer' => 'elasticsearch',
    'start_date_in_millis' => -1
  }
} to {"license"=>{"uid"=>"0e18ca57-193d-45e7-a265-f0e5c3044a45", "type"=>"platinum", "issue_date_in_millis"=>1520294400000, "expiry_date_in_millis"=>1554076799999, "max_nodes"=>120, "issued_to"=>"some company", "issuer"=>"Magdalena Kowalska", "signature"=>"[redacted]", "start_date_in_millis"=>1520294400000}}

Here is the hash:
elasticsearch::license:
  license:
    uid: 0e18ca57-193d-45e7-a265-f0e5c3044a45
    type: platinum
    issue_date_in_millis:<PHONE_NUMBER>000
    expiry_date_in_millis:<PHONE_NUMBER>999
    max_nodes: 120,
    issued_to: 'some company'
    issuer: 'Magdalena Kowalska'
    signature: REDACTED
    start_date_in_millis:<PHONE_NUMBER>000

I noticed the API endpoint in the provider was set to /_xpack/license. Since I'm using Elasticsearch 7.4, the documentation uses /_license instead. I've tried both and still receive the same issue.

@TJM I think your hash is incorrect, it should be:
elasticsearch::license:
  license:
    uid: 41bXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
    type: platinum
    issue_date_in_millis:<PHONE_NUMBER>000 # May 31, 2018
    expiry_date_in_millis:<PHONE_NUMBER>999 # June 6, 2019
    max_nodes: 10
    issued_to: A Company
    issuer: Magdalena Kowalska
    signature: (censored)
    start_date_in_millis:<PHONE_NUMBER>000

Hmmm, THANKS!
That extra license level seems a bit unnecessary, but that would certainly explain why it is not finding the license or attempting to compare/install. I think, if I can find the time and can figure out where to do it, I will make it so that it accepts the license hash at the root of the license parameter instead of $license = license => { (the actual license) }.
~tommy

I agree it does seem unncessary but it's required because it's in the license.json file.
From the readme:

The license parameter will accept either a Puppet hash representation of the license file json or a plain json string that will be parsed into a native Puppet hash.

I was having difficulties but it turns out my license has expired >_< whoops.

I was having difficulties but it turns out my license has expired >_< whoops.

Perhaps if they would use a reasonable date format, instead of milliseconds since Jan 1, 1970, it would be easier to detect that :)
That was partially the reason why I chose to convert our license to yaml format, to make it more readable. Also the only portion that needed encrypted was the signature. I am giving up and just eyaml-ing the entire json license string this time :)

Apologies for the confusion here folks, but I'm glad you were able to pinpoint the problem!


[Bug Report] Select option's list is not closing on click when set to multiple and filterable

Element UI version
2.3.7
OS/Browsers version
Windows 7 / Chrome 66.0.3359.139
Vue version
2.5.11
Reproduction Link
https://codepen.io/akki-jat/pen/GdEYyG
Steps to reproduce
Open it then try to close it by clicking on select element
What is Expected?
Select option's list should be closed
What is actually happening?
Select option's list is not closing

Hey @Leopoldthecoder, what about this, is it suppose to work like that?

I think you should remove the property of filterable or change another version,version on 2.3.9 fixed this problem

@Leopoldthecoder  dalao close this problem

Hi @leslieSie, I need the filter functionality and this issue is not solved either in 2.3.9 or 2.4.0.
In new version, on pc it is closed only first time and second time it does not close & on mobile it even not closes first time

The problem is that if you want filterable, there will be an input where you type things. Clicking on select's text area will focus the input, thus preventing dropdown from closing (because the component is expecting user to input something).
Suppose dropdown is closed as you requested, imagine the scenario where user is selecting inputted text with mouse, which triggers click thus closes the dropdown. I doubt this is an appropriate behavior for user-interaction.
If you do really need to do so, you can listen on native click event on select, then modify select's internal state.

The arrow (caret) implementation seems buggy now. I suppose you are talking about clicking that button fails to close dropdown?

Hi @wacky6, I also thought that,
But in example on website, it is working fine.
Take a look
http://element.eleme.io/#/en-US/component/select#option-filtering

Well, in your case multiple is also used. My guess would be multiple somehow interferes with caret's click handler.

Yes, you are right @wacky6.


isDraggingOver is not set to False on cardDrop

Describe the bug
When draggable is set to true and you drag a card from lane A to lane B the lane B is extended 100px down during the drag event, but it doesn't get reduced 100px when you drop the card there.
In the code the lanes "isDraggingOver" prop is set to true on "onDragEnter" and to false on "onDragLeave" but since we drop the card in the lane, the "onDragLeave" event is never triggered and the extra 100px lane height sticks around.
I guess a fix would be to set "isDraggingOver" to false also on "onDrop" event?
Screenshots

This should be fixed 2.1.0


Merge prTesting_201909241328 branch to master branch

Docs Build status updates of commit cdfa9ae:
:warning: Validation status: warnings

File
Status
Preview URL
Details

split/updateTestRef.md
:warning:Warning

Details

split/updateTestRef.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.
[Warning] Missing attribute: title. Add a title string to show in search engine results.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Data model

Summary
Be sure to reference the ERD diagram from the sneak peek if you have any questions about table or column names or data relationships.

Create a new app. Give it a meaningful name.
Initialize your project with Git.
Make sure that your project has Postgres database set up.
Build your project schema.

Create and run the necessary migration files.
Table and column names should match the ERD diagram.

note: photo for users table should be a link to an image

Foreign keys should be included.
All columns that are foreign keys should have a corresponding index.

@brytebee @elisha2kyakpo1 Thank you for all of your reviews.

Note: All optional & required changes have been implemented.


Tree: add location for most nodes

This closes #732 (although some node types do not have locations yet e.g. array and struct initializers)
As expected this increases memory usage but there's not much of a performance hit (numbers are for parsing zig2.c which is 161,279,661 bytes)
Before
  measurement          mean ± σ            min … max           outliers         delta
  wall_time          9.54s  ± 9.92ms    9.53s  … 9.55s           0 ( 0%)        0%
  peak_rss           1.61GB ± 28.8KB    1.61GB … 1.61GB          0 ( 0%)        0%
  cpu_cycles         36.9G  ± 40.2M     36.8G  … 36.9G           0 ( 0%)        0%
  instructions       78.6G  ± 70.2      78.6G  … 78.6G           0 ( 0%)        0%
  cache_references   93.3M  ±  399K     92.9M  … 93.7M           0 ( 0%)        0%
  cache_misses       43.9M  ±  187K     43.6M  … 44.0M           0 ( 0%)        0%
  branch_misses       327M  ±  345K      327M  …  327M           0 ( 0%)        0%

After
  measurement          mean ± σ            min … max           outliers         delta
  wall_time          9.63s  ± 40.2ms    9.60s  … 9.67s           0 ( 0%)          +  1.0% ±  0.7%
  peak_rss           1.74GB ± 59.1KB    1.74GB … 1.74GB          0 ( 0%)        💩+  7.8% ±  0.0%
  cpu_cycles         37.0G  ±  167M     36.9G  … 37.2G           0 ( 0%)          +  0.5% ±  0.7%
  instructions       78.7G  ±  101      78.7G  … 78.7G           0 ( 0%)          +  0.2% ±  0.0%
  cache_references   97.1M  ±  808K     96.4M  … 98.0M           0 ( 0%)        💩+  4.1% ±  1.5%
  cache_misses       46.7M  ±  328K     46.4M  … 47.1M           0 ( 0%)        💩+  6.4% ±  1.4%
  branch_misses       327M  ±  599K      326M  …  327M           0 ( 0%)          -  0.1% ±  0.3%

Looks like we're massively faster than GCC with similar memory usage, and about 40% faster than clang at the cost of 44% higher memory usage. The only caveat is that I'm not sure if those 2 are doing more work than we are for -fsyntax-only
Benchmark 1 (3 runs): clang-18 -fsyntax-only -I/home/ehaas/source/zig/lib /home/ehaas/source/zig/build/zig2.c
  measurement          mean ± σ            min … max           outliers         delta
  wall_time          16.2s  ± 41.8ms    16.2s  … 16.3s           0 ( 0%)        0%
  peak_rss           1.20GB ± 81.3KB    1.20GB … 1.20GB          0 ( 0%)        0%
  cpu_cycles         66.5G  ±  174M     66.3G  … 66.6G           0 ( 0%)        0%
  instructions       99.9G  ±  177M     99.8G  …  100G           0 ( 0%)        0%
  cache_references    418M  ± 8.74M      408M  …  424M           0 ( 0%)        0%
  cache_misses       36.9M  ±  188K     36.7M  … 37.1M           0 ( 0%)        0%
  branch_misses       126M  ±  454K      126M  …  127M           0 ( 0%)        0%
Benchmark 2 (3 runs): /home/ehaas/source/arocc/zig-out/bin/arocc-node-locs -fsyntax-only -I/usr/lib/gcc/x86_64-linux-gnu/10/include -I/home/ehaas/source/zig/lib /home/ehaas/source/zig/build/zig2.c
  measurement          mean ± σ            min … max           outliers         delta
  wall_time          9.58s  ± 38.5ms    9.55s  … 9.62s           0 ( 0%)        ⚡- 40.9% ±  0.6%
  peak_rss           1.74GB ± 17.1KB    1.74GB … 1.74GB          0 ( 0%)        💩+ 44.3% ±  0.0%
  cpu_cycles         37.0G  ± 39.1M     36.9G  … 37.0G           0 ( 0%)        ⚡- 44.4% ±  0.4%
  instructions       78.7G  ± 10.4K     78.7G  … 78.7G           0 ( 0%)        ⚡- 21.2% ±  0.3%
  cache_references   97.5M  ±  524K     97.2M  … 98.1M           0 ( 0%)        ⚡- 76.7% ±  3.4%
  cache_misses       46.5M  ±  159K     46.3M  … 46.6M           0 ( 0%)        💩+ 25.8% ±  1.1%
  branch_misses       327M  ±  116K      327M  …  327M           0 ( 0%)        💩+158.4% ±  0.6%

Benchmark 1 (3 runs): gcc-13 -fsyntax-only -I/home/ehaas/source/zig/lib /home/ehaas/source/zig/build/zig2.c
  measurement          mean ± σ            min … max           outliers         delta
  wall_time          92.0s  ±  281ms    91.7s  … 92.3s           0 ( 0%)        0%
  peak_rss           1.75GB ±  116KB    1.75GB … 1.75GB          0 ( 0%)        0%
  cpu_cycles          349G  ± 1.21G      348G  …  350G           0 ( 0%)        0%
  instructions       75.0G  ±  103M     75.0G  … 75.2G           0 ( 0%)        0%
  cache_references   6.65G  ± 14.8M     6.64G  … 6.67G           0 ( 0%)        0%
  cache_misses       3.87G  ± 35.7M     3.84G  … 3.91G           0 ( 0%)        0%
  branch_misses       129M  ±  185K      129M  …  130M           0 ( 0%)        0%
Benchmark 2 (3 runs): /home/ehaas/source/arocc/zig-out/bin/arocc-node-locs -fsyntax-only -I/usr/lib/gcc/x86_64-linux-gnu/10/include -I/home/ehaas/source/zig/lib /home/ehaas/source/zig/build/zig2.c
  measurement          mean ± σ            min … max           outliers         delta
  wall_time          10.7s  ±  250ms    10.4s  … 10.9s           0 ( 0%)        ⚡- 88.4% ±  0.7%
  peak_rss           1.74GB ± 49.5KB    1.74GB … 1.74GB          0 ( 0%)          -  0.7% ±  0.0%
  cpu_cycles         37.1G  ± 83.0M     37.0G  … 37.2G           0 ( 0%)        ⚡- 89.4% ±  0.6%
  instructions       78.7G  ±  413      78.7G  … 78.7G           0 ( 0%)        💩+  4.9% ±  0.2%
  cache_references   97.6M  ± 2.19M     95.4M  … 99.8M           0 ( 0%)        ⚡- 98.5% ±  0.4%
  cache_misses       46.1M  ±  152K     45.9M  … 46.2M           0 ( 0%)        ⚡- 98.8% ±  1.5%
  branch_misses       327M  ±  104K      326M  …  327M           0 ( 0%)        💩+152.5% ±  0.3%


drop the bounceback effect

in a material world, we accelerate than decelerate. we don't run the stop sign, reverse, run it again by a lesser amount, then reverse into the correct position.
<3

Hello. Thanks for a correct comment. ICVP based on inspired design which bring best of them.
You can change interpolator to your own. Thanks.

Awesome!


missing config.yaml

"The config.yaml file, located at ~/petals_server_installer/main_ui/, stores various configurations." suggests that there should be a config file in the main_ui folder, but there isn't a file with that name.

I see ... it gets created at launch. Is there a way to connect to or even manage a private petals swarm?

Hi there. It should be possible to do that. I just didn't have the time to do it :)
You can contribute to this project if you want by updating the code to allow connecting to a private network.
I don't have much time these days to do it myself. But maybe I will, If I have time.


Support filtering out specification projects

In the old landscape, it was possible to filter using extra metadata
e.g., https://landscape.cncf.io/?specification=true
Would filter out projects that were specifications that had
extra:
specification: true
In the metadata.
Can the new landscape support this @tegioz

Done: https://landscape.cncf.io/?specification=true (the filter is also accessible from the UI)
Closed by #509

Thank you!
On Wed, Feb 21, 2024 at 11:01 AM Sergio Castaño Arteaga <
@.***> wrote:

Done: https://landscape.cncf.io/?specification=true (the filter is also
accessible from the UI)
Closed by #509 https://github.com/cncf/landscape2/pull/509
—
Reply to this email directly, view it on GitHub
https://github.com/cncf/landscape2/issues/505#issuecomment-1956289236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAPSIKLMSLQKBXSEZCGJKLYUXAWDAVCNFSM6AAAAABDRJWBG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJWGI4DSMRTGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Cheers,
Chris Aniszczyk
https://aniszczyk.org


12 workaround

Not fully complete, unable to get all of the text white. Don't merge until I figured this out.

well that was an incredibly sad amount of effort

feel free to revert when actual implementation is here


Configure fcm for shared repositories

resolution_fixed   |    by<EMAIL_ADDRESS>
Follow instructions at https://code.metoffice.gov.uk/trac/home/wiki/FAQ#HowdoIconfiguretheFCMkeywords

Issue migrated from trac:154 at 2024-01-31 17:39:35 +1100

<EMAIL_ADDRESS>changed status from accepted to closed

<EMAIL_ADDRESS>changed status from new to accepted

<EMAIL_ADDRESS>changed owner from `` to saw562

<EMAIL_ADDRESS>changed resolution from `` to fixed


removed DGZ from leveraged_etf_list

Removed DGZ from leveraged ETF list per the discussion on this thread:
https://www.quantopian.com/posts/dgz-a-leveraged-etf#561440cf8c09fa5208000096

@jfkirk Could you take a look at this one?

This list is meant to be point in time. We should not be mutating files in place. We would need to create new remove entry instead of deleting the add. @fawce, can you confirm that I have translated your intent correctly.

@llllllllll is correct - this should be a new delete file.

wait does this mean I should be making a new date folder with today's date, having a blank add file and then a delete file with DGZ?

Need to hold off on merging this one. I get the functionality of the date files but we need to decide what we want in terms of retroactively removing it or removing it from today-onward.

@llllllllll Changed it to a point-in-time deletion today, can you check that it looks ok?

Hey, I was looking this over but I think I need to talk to fawce quick to answer some questions  I have around the security lists

@llllllllll @jmccorriston @fawce what's the status on this?

I think it's blocked on a dicussion between @llllllllll and @fawce

@jmccorriston @llllllllll what should we do about this?

No clue, I just know that DGZ shouldn't be on the list. @llllllllll ?

Moved to https://github.com/quantopian/zipline/pull/1434.


CircularDependencyError with Custom User Model app

Issue Summary
I'm new to Wagtail, and wanted to START a project (I say START meaning before makemigrations or migrate):

Without the "home" app
With an app called "base"
The base app contains a Custom User Model
The base app also contains a Home(Page) model
The base app User model is the project's user model (obvious, but thought I'd clarify)

But after running migrate (after makemigrations) I get this big ugly error:
Traceback (most recent call last):
  File "manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "C:\Users\zackp\.virtualenvs\wagtail_training_3-TmuBvXmb\lib\site-packages\django\core\management\__init__.py", line 401, in execute_from_command_line
    utility.execute()
  File "C:\Users\zackp\.virtualenvs\wagtail_training_3-TmuBvXmb\lib\site-packages\django\core\management\__init__.py", line 395, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "C:\Users\zackp\.virtualenvs\wagtail_training_3-TmuBvXmb\lib\site-packages\django\core\management\base.py", line 330, in run_from_argv
    self.execute(*args, **cmd_options)
  File "C:\Users\zackp\.virtualenvs\wagtail_training_3-TmuBvXmb\lib\site-packages\django\core\management\base.py", line 371, in execute
    output = self.handle(*args, **options)
  File "C:\Users\zackp\.virtualenvs\wagtail_training_3-TmuBvXmb\lib\site-packages\django\core\management\base.py", line 85, in wrapped
    res = handle_func(*args, **kwargs)
  File "C:\Users\zackp\.virtualenvs\wagtail_training_3-TmuBvXmb\lib\site-packages\django\core\management\commands\migrate.py", line 92, in handle
    executor = MigrationExecutor(connection, self.migration_progress_callback)
  File "C:\Users\zackp\.virtualenvs\wagtail_training_3-TmuBvXmb\lib\site-packages\django\db\migrations\executor.py", line 18, in __init__
    self.loader = MigrationLoader(self.connection)
  File "C:\Users\zackp\.virtualenvs\wagtail_training_3-TmuBvXmb\lib\site-packages\django\db\migrations\loader.py", line 53, in __init__
    self.build_graph()
  File "C:\Users\zackp\.virtualenvs\wagtail_training_3-TmuBvXmb\lib\site-packages\django\db\migrations\loader.py", line 282, in build_graph
    self.graph.ensure_not_cyclic()
  File "C:\Users\zackp\.virtualenvs\wagtail_training_3-TmuBvXmb\lib\site-packages\django\db\migrations\graph.py", line 274, in ensure_not_cyclic
    raise CircularDependencyError(", ".join("%s.%s" % n for n in cycle))
django.db.migrations.exceptions.CircularDependencyError: wagtailcore.0017_change_edit_page_permission_description, wagtailcore.0018_pagerevision_submitted_for_moderation_index, wagtailcore.0019_verbose_names_cleanup, wagtailcore.0020_add_index_on_page_first_published_at, wagtailcore.0021_capitalizeverbose, wagtailcore.0022_add_site_name, wagtailcore.0023_alter_page_revision_on_delete_behaviour, wagtailcore.0024_collection, wagtailcore.0025_collection_initial_data, wagtailcore.0026_group_collection_permission, wagtailcore.0027_fix_collection_path_collation, wagtailcore.0028_merge, wagtailcore.0029_unicode_slugfield_dj19, wagtailcore.0030_index_on_pagerevision_created_at, wagtailcore.0031_add_page_view_restriction_types, wagtailcore.0032_add_bulk_delete_page_permission, wagtailcore.0033_remove_golive_expiry_help_text, wagtailcore.0034_page_live_revision, wagtailcore.0035_page_last_published_at, wagtailcore.0036_populate_page_last_published_at, wagtailcore.0037_set_page_owner_editable, wagtailcore.0038_make_first_published_at_editable, wagtailcore.0039_collectionviewrestriction, wagtailcore.0040_page_draft_title, wagtailcore.0041_group_collection_permissions_verbose_name_plural, wagtailcore.0042_index_on_pagerevision_approved_go_live_at, wagtailcore.0043_lock_fields, wagtailcore.0044_add_unlock_grouppagepermission, wagtailcore.0045_assign_unlock_grouppagepermission, wagtailcore.0046_site_name_remove_null, wagtailcore.0047_add_workflow_models, wagtailcore.0048_add_default_workflows, wagtailcore.0049_taskstate_finished_by, wagtailcore.0050_workflow_rejected_to_needs_changes, wagtailcore.0051_taskstate_comment,
wagtailcore.0052_pagelogentry, wagtailcore.0053_locale_model, wagtailcore.0054_initial_locale, wagtailcore.0055_page_locale_fields, wagtailcore.0056_page_locale_fields_populate, wagtailcore.0057_page_locale_fields_notnull, wagtailcore.0058_page_alias_of, wagtailcore.0059_apply_collection_ordering, base.0001_initial, wagtailcore.0001_squashed_0016_change_page_url_path_to_text_field

Steps to Reproduce

Start a new project with wagtail start myproject
Delete the home app
Create a new app named "base"
Edit the base app models page like so (add a custom User model, then add a Wagtail page):

#base/models.py

from django.contrib.auth.models import AbstractUser, BaseUserManager
from django.db import models

from wagtail.core.models import Page

# Create your models here.

class UserManager(BaseUserManager):
    def create_user(self, email, first_name, last_name, password=None):
        if not email:
            raise ValueError('Users must have an email address')

        user = self.model(
            email=self.normalize_email(email),
            first_name=first_name,
            last_name=last_name,
        )

        user.set_password(password)
        user.save(using=self._db)
        return user

    def create_superuser(self, email, first_name, last_name, password=None):
        user = self.create_user(
            email=email,
            first_name=first_name,
            last_name=last_name,
            password=password
        )
        user.is_superuser = True
        user.is_staff = True
        user.save(using=self._db)
        return user

class User(AbstractUser):
    username = None
    email = models.EmailField(unique=True)

    USERNAME_FIELD ='email'
    REQUIRED_FIELDS = ['first_name', 'last_name']

    objects = UserManager()

    def __str__(self):
        return self.email

    @property
    def name(self):
        return f'{self.first_name} {self.last_name}'

# Home Page
class Home(Page):
    pass

In the myproject/settings/base.py file, update INSTALLED_APPS like so:

# myproject/settings/base.py
INSTALLED_APPS = [
    'base',
    'search',

    'modelcluster',
    'taggit',
    'django_extensions',

    'django.contrib.admin',
    'django.contrib.auth',
    'django.contrib.contenttypes',
    'django.contrib.sessions',
    'django.contrib.messages',
    'django.contrib.staticfiles',
]

Also in the myproject/settings/base.py file, add the custom Auth user model:

# myproject/settings/base.py

AUTH_USER_MODEL = 'base.User'

Run python manage.py makemigrations
Run python manage.py migrate

Then the error occurs.

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: yes

Technical details

Python version: 3.8.6
Django version: 3.1.3
Wagtail version: 2.11

Hi @ZackPlauche - thanks for the detailed report!
This is an expected consequence of how Django migrations behave. You can't create a custom user model in the same migration as a page model, because Wagtail's base Page model contains references to the user model, and so the migrations need to create the user model first, followed by Wagtail's base Page model, then your home page model. If you proceed as follows:

Delete the failing base.0001_initial migration
Comment out the definition of class Home(Page): in your models.py
Run python manage.py makemigrations
Uncomment the definition of class Home(Page):
Run python manage.py makemigrations again

then the dependencies will be set up correctly, and migrations should then complete successfully.

Hi @gasman, thanks for the reply!
That makes a lot of sense. Your explanation was clear as crystal.
Out of curiosity, and coming to this as a beginner, is this somewhere in the documentation? If not, I think it would be a valuable addition to the docs as a warning above in the "Custom User Models" section in the Advanced Topics / Customising Wagtail documentation:  https://docs.wagtail.io/en/v2.11/advanced_topics/customisation/custom_user_models.html
Currently it the layout is a bit confusing, as the heading above where the Custom User Model is created it says "Custom user forms example", instead of first just talking about the Custom User part.
I know that's where I looked (and I literally just went through the first 2 parts of the documentation 2 days ago haha) and it was confusing to me.
Here's what I think would help:


Commit "Merge remote-tracking branch 'upstream\master'"

Today after sync with Powershell/master I get local a commit  285f2bfbe216ee6ada27fbd161fe40fe26ab4f91 Merge remote-tracking branch 'upstream\master'
Is it ok? The name is strange and no link to PR.

Looks just like @steve forgot to rebase instead of merge :)
Unless a smarter git-wiz than me sees something wrong here, this should be okay to close.

Uh, my bad.


chore(main): release 0.6.1

:robot: I have created a release beep boop
0.6.1 (2023-08-04)
Miscellaneous

Make error handling and validation consistent (#60) (06f6112)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/momentohq/client-sdk-elixir/releases/tag/v0.6.1 :sunflower:


number field client validation does not work correctly

What steps will reproduce the problem?
Create an active form with ->textInput(['type' => 'number') with number validation rule created for corresponding attribute. If non-numeric value is entered to the field, client validation passes.
What is the expected result?
Validation error shown.
What do you get instead?
Validation passes and no error is shown.
Additional info
It is due to empty value returned by https://github.com/yiisoft/yii2/blob/d43341a73ab9ab711c42b74c117e076275d9b8c0/framework/assets/yii.activeForm.js#L918 for non-numeric values. This empty value is then passed to https://github.com/yiisoft/yii2/blob/d43341a73ab9ab711c42b74c117e076275d9b8c0/framework/assets/yii.validation.js#L120 via https://github.com/yiisoft/yii2/blob/d43341a73ab9ab711c42b74c117e076275d9b8c0/framework/assets/yii.activeForm.js#L367-L367 and as empty value is a valid value, validation passes.

Q
A

Yii version
<IP_ADDRESS>

PHP version
8.1.18

Operating system
Fedora

@karelvasicek
You mean if you enter "aaa" into numeric field, it will not show error?
I have never seen that. On active forms it shows error in my project.
What value exactly did you fill in ?

@lubosdz

You mean if you enter "aaa" into numeric field, it will not show error?

Yes, correct. I've just installed fresh basic app, changed Name field in Contact form to <?= $form->field($model, 'name')->textInput(['autofocus' => true, 'type' => 'number']) ?>, removed the name attribute from required rule and added a new ['name', 'number'] rule. Client validation result is as follows:

What is your model validation rule for the attribute?
Did you add to rules e.g. [['name'], 'number'], ?
Validator to which you are pointing is related to model validation rule for number, not the input attribute type="number". Also I dont think that yii.validation.js supports HTML5 specific attributes like type="number" or type="email". It would also make no sense on client side only. I tested your scenario and adding rule ``[['name'], 'number']` worked fine for me.

@lubosdz

Did you add to rules e.g. [['name'], 'number'], ?

Yes, I wrote that in my comment. I wrote "...and added a new ['name', 'number'] rule".

is related to model validation rule for number

Yes, it is. As I wrote, I have number rule in rules().

Also I dont think that yii.validation.js supports HTML5 specific attributes like type="number" or type="email"

Could be. At least number field is not client-validated correctly. Should be HTML5 fields supported?

It would also make no sense on client side only

How did you mean that?

Why would client side validation make no sense? It improves UX significantly.
"Browser" validation is performed on form submission and Yii backend validation would be performed too, of course. But this is totally unrelated to this issue. This issue is about not working client side validation for number field. The field turns green even with invalid value.

I tested your scenario and adding rule ``[['name'], 'number']` worked fine for me.

What exactly did work fine for you?


Timeslices in Safari 13

Description
Briefly describe the issue.
On Mac OS X, Chrome, Edge, and Firefox works with Timeslices. Safari, instead of timeslices, uploads one whole clip.
Steps to reproduce
Explain in detail the exact steps necessary to reproduce the issue.
Record video with timeslice in player configuration.
 record: {
        maxLength: 900,
        debug: false,
        audio: false,
        timeSlice: 2000,
        videoMimeType: "video/mp4;codecs=H264",

Results
Expected
Please describe what you expected to see.
Video Timeslices
Actual
Please describe what actually happened.
on finishRecord, player.on('timestamp', function() uploads a single video clip.
Error output
If there are any errors at all, please include them here.
No errors in console
Additional Information
Please include any additional information necessary here. Including the following:
versions
videojs
what version of videojs does this occur with?
videojs 7.6
browsers
what browser(s) are affected? Make sure to test with all third-party browser extensions disabled.
Safari 13.1
OSes
what platforms (operating systems and devices) are affected?
Mac OS X 10.15.5

@taylerz can you try this RecordRTC demo in Safari and check if it works. If not, can you check the console and paste the output (or screenshot) here?
https://www.webrtc-experiment.com/RecordRTC/simple-demos/ondataavailable.html

@thijstriemstra The page does not work for Safari.
A single blob is recorded, similarly to my videojs recorder code. Moreover, the header title just above the recorder does not update automatically like it does for Chrome. The header title, which reads at initialization: "ondataavailable | get Intervals based blobs using RecordRTC" remains the same throughout the recording. At end of recording, Safari displays the title "Total blobs: 1 (Total size: 4.97 MB)"
On the other hand, in Chrome, the header title automatically updates for each blob. The title at the end of a test recording read: "Total blobs: 6 (Total size: 1.30 MB)"
Console output appears to be identical for both Safari and Chrome. I believe insufficient data is output to console showing the timesliced blobs.
It would appear the issue is with RecordRTC, not Videojs recorder. Thanks!

It would appear the issue is with RecordRTC, not Videojs recorder. Thanks!

Can you open a ticket there and link it here?

@thijstriemstra This issue is fixed in Safari Technology Preview 111, and presumably in Safari 14 when it's released this fall with Mac OS Big Sur.

thanks for the feedback @taylerz!


Add linux networking support

This patch is initial commit to introduce linux
networking support in krnlmon.
Title: Add linux networking support
Signed-off-by: nupuruttarwar<EMAIL_ADDRESS>

On the next commit, could you please correct the title in the top-level README.md file to the name of the repository on ipdk-io? I accidentally carried over the repository name from intel-sandbox. Thanks.

On the next commit, could you please correct the title in the top-level README.md file to the name of the repository on ipdk-io? I accidentally carried over the repository name from intel-sandbox. Thanks.

Sure, will do

LGTM.
Most of my comments are meant to be informative. The only point I consider important is that we must preserve copyright notices when we adapt existing intellectual property.
I have no objection if you want to wait until the next iteration to fix the copyright notices, especially if this you are doing little more than carrying over existing code from P4-OVS in this iteration.
Incidentally, if any of the new files were adapted from existing code, you should add their copyright notices back in.

Sure, let me check about licenses one more time with Namrata and from legal standpoint as well, will take care of license in next commit

Sure, let me check about licenses one more time with Namrata and from legal standpoint as well, will take care of license in next commit
I'm talking about copyright notices, not licenses. They both go into the module header, but they're two different things, governed by different sets of laws.

Intel policy says that when we modify an existing work, we add our copyright notice below the existing ones.
By omitting the existing copyright notice, we appear to be claiming sole authorship of a work of which we are not the sole author. That's at best tacky, and at worst a violation of copyright law. Intel has a bad reputation in the open source community. We need to be punctilious in our observance, partly to maintain public good will, and partly because respect for intellectual property is an Intel value.
Barefoot Networks was the author at the time the work was created. Even though they're part of Intel now, their original declaration of authorship still stands.

Sure, let me check about licenses one more time with Namrata and from legal standpoint as well, will take care of license in next commit

I'm talking about copyright notices, not licenses. They both go into the module header, but they're two different things, governed by different sets of laws.
Intel policy says that when we modify an existing work, we add our copyright notice below the existing ones.
By omitting the existing copyright notice, we appear to be claiming sole authorship of a work of which we are not the sole author. That's at best tacky, and at worst a violation of copyright law. Intel has a bad reputation in the open source community. We need to be punctilious in our observance, partly to maintain public good will, and partly because respect for intellectual property is an Intel value.
Barefoot Networks was the author at the time the work was created. Even though they're part of Intel now, their original declaration of authorship still stands.

I agree, will make the changes in the next commit


Tweak some colors and spacing for contrast and brand prominence

This was fun! Made a few small cosmetic tweaks.

Change gradient band to have 4 corners representing Microsoft colors
Change background to a dark blue and brighter blue-white with same saturation and hue as Microsoft's logo blue
Move content down a bit for some breathing room

Before:

After:

 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.:x: sandgraham sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Looking good! Sorry for the conflicts.

Oh, looks like someone already spiffed up the color band. I'll get rid of that part and push back up.

Awesome. Maybe you can add this to the work in #73 so we have a blue theme?


User status in the member list are wrong

App version : Android, 1.0.17
The member list(swiping left opens the menu to choose from) pop-up shows the users for the channel, but at times it shows the wrong status. Like the user on the web version is offline(gray), the app shows either orange or green(depends).
Also sometime it does not show the list and only showing total members count.

It some time update the status but after a while. Like opening that list for 5 times.

@mmarif4u Thanks for opening the issue, we're going to rewrite all the members list using a different API request, so I'm closing this issue but you can follow the progress here: #421.


Intermidiate Scene for Sceneloading to prevent chaching problems

Is your feature request related to a problem? Please describe.
When using NetworkingSceneManager, the old scene gets unloaded after the new scene finsihed loading. Thus, the start methods of the new scene might cache the wrong refrences (main.Camera for example) on the old scene jsut before it gets unloaded.
Currently you have take care and make sure that you don't accidently cache obejcts from the old scene
Describe the solution you'd like
A way of being sure that the old scene is unloaded, before the new start methods fire.
to quote "Petter" here for a possible solution:
"It would maybe be possible to first load a temporary scene[,] copy the networkedobjects over to the temporary scene[,] unload the old scene[,] load the new scene and copy them over from the temporary scene to the new scene.
The temporary scene could maybe be the dont destroy on load scene."
This would make it much more intuitive to use the NetworkingSceneManager.

:tada: This issue has been resolved in version 8.2.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Street lights turn off when the simulation enters night mode

CARLA version:0.9.11
Platform/OS:Linux
Problem you have experienced: When I added a new BP_StreetLight_doble to the map and ran dynamic_weather.py, I found that the street lights were not on at night. Is it because a certain logic is not turned on? How can I solve it, thank you!

@bernatx


feat: zip compression

Codecov Report

Merging #265 (f4129f5) into master (8a9bd7d) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #265      +/-   ##
==========================================
- Coverage   88.60%   88.58%   -0.03%
==========================================
  Files          40       40
  Lines        3810     3810
  Branches     1115     1115
==========================================
- Hits         3376     3375       -1
- Misses        400      401       +1
  Partials       34       34

Impacted Files
Coverage Δ

packages/cli-plugin-package/src/index.ts
86.40% <ø> (ø)

packages/cli-plugin-check/src/index.ts
93.96% <0.00%> (-0.27%)
:arrow_down:

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 8a9bd7d...f4129f5. Read the comment docs.


Access semver version properties in Gradle build file.

Hey!
How can I read the version properties?
Currently I'm loading them manually
val props = Properties().apply {
    load(file("version.properties").inputStream())
}

Is there an easy way to do it?

@Kerooker If your project is in Java or Kotlin, you can use the SemVer Annotation Processor to create a version class that is accessible programmatically within your project.
If you are trying to read the properties file in the Gradle build file, then what you suggested works.
I've never really thought about exposing the properties file content. Maybe as project extensions? Is that what you're looking for?

I have the need to embed the version to other gradle tasks, such as Google App Engine's release or for Android artifact creation.
I'm using the file approach, but I think that perhaps there should be a way to do it out-of-the-box. Something like
android {
     version = semver.version
     build = semver.major * 10000 + semver.minor * 100 + semver.patch
}

(This is actually pretty close to my use case)

And then we can remove user's trouble on fetching these to use in build.gradle

Have you tried?
version = project.version
That should work, if not try putting it in a doFirst block.
As far as your build calculation, I'd have to look into it. Providing read-only properties in Gradle is not very straight forward.

@Kerooker I've released 1.0.3-beta. It implements a set of semver extension properties. Look at the documentation for a complete list.
Your example should now work as-is. Give it a try and let me know if that works for you.

That's exactly what I wanted!
This works as expected

Implemented by e1891c47af347f38a899af465a9210c2428d6976

Thanks, will let you know ASAP 🙏

@mochadwi I have no idea if it'll work, but you could try:
versionName = ${-> semver.version}

It might work, let me know.

What's this is called in Gradle, is it Lambda argument? needs to find an alternative for build.gradle.kts (kotlin script)

@mochadwi It's a lazy instantiation of a GString. I don't think there's an equivalent in Kotlin, unfortunately.
Have you tried setting the version as a late variable? Might work, but I have my doubts.

Thanks for the reference, will update you later. Currently still AFK 🙏


Subset sum equal to k

Is your feature request related to a problem? Please describe.
Given an array A of size n and an integer K, return all subsets of A which sum to K.
Describe the solution you'd like
I want the solution to be using recursion.
Do you want to work on it
I would like to work on this issue and would be using the C++ language.

Hey, we want to add the most optimised solution to be added. Would be able to solve this using dp ?

I would like to code this in C++. I m a GSSOC'21 Partcipant .I will assure you that I will provide a most optimized code and
commented code with efficient time complexity.@tarun26091999 @dheerajkotwani @anubhavitis @dheerajkotwani @rudrakshi99 @plazzy99 @nakul-19 please assign this to me .
Regards
Madhvi .

Is your feature request related to a problem? Please describe.
Given an array A of size n and an integer K, return all subsets of A which sum to K.
Describe the solution you'd like
I want the solution to be using recursion.
Do you want to work on it
I would like to work on this issue and would be using the C++ language.

hey, plz reply if you would be able to solve via dp else assigning the issue to others.

@raksha009 isn't this issue same as #148

@raksha009 isn't this issue same as #148

Ohh yess, my bad. Thanks


Idempotency in extension creation

 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.

Signed.


adding codeql to besu to check for quality

PR description
Adding codeql scans to HLF Besu

This PR fixes the comparison of int <> long in loops
https://github.com/hyperledger/besu/pull/3777

Lists.emptyList() -> Collections.emptyList() https://github.com/hyperledger/besu/pull/3780

fix for "dereferenced object always null" error https://github.com/hyperledger/besu/pull/3788


Partition help content incorrect

The help content for the -Partition parameter is incorrect.

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

ID: c0b9f4db-305b-847a-1ab6-ad3b547a91f7
Version Independent ID: a626e689-b2ba-6a11-c17b-9f1fd0e565cd
Content: Get-ADUser (addsadministration)
Content Source: docset/windows/addsadministration/get-aduser.md
Product: w10
GitHub Login: @coreyp-at-msft
Microsoft Alias: coreyp

@officedocsbot unassign @e0i
@officedocsbot assign @yogkumgit

Hello @SeanQuinlan
Thanks for your feedback.
I created a pull request to correct the description of Partition parameter.
Many thanks


Add debug info for release.sh

Changes
To investigate https://knative.slack.com/archives/CA1DTGZ2N/p1619160369065000

/approve


Some beatmaps download without video

Beatmap: https://kitsu.moe/d/762823
It seems to be related directly to kitsu.moe. Perhaps this requires replacing the beatmap mirror, but which one to use instead?

This appears to be a geographical issue. In the US, it redirects to a host that downloads with the video (us.kitsu.moe), but in europe, it downloads without video (kitsu.moe).

@kionell Can you confirm that fix this works from your location?

Yep, it seems to be fixed now


Add native profile and document the it profile

Here are the few things I missed when creating the freemarker extension:

Specify -Pnative in build.yml:

run: mvn -B -Pnative formatter:validate verify --file pom.xml

Or at least document it in the readme if there are native tests.

Specify that there should be the following profile

    <profiles>
        <profile>
            <id>it</id>
            <activation>
                <property>
                    <name>performRelease</name>
                    <value>!true</value>
                </property>
            </activation>
            <modules>
                <module>integration-test</module>
            </modules>
        </profile>
    </profiles>

Unless it is included by the create-extension plugin.

And document that the integration-test module should not be listed in the module list.

Include the minimal test dependencies

        <!-- Minimal test dependencies to *-deployment artifacts for consistent build order -->
        <dependency>
            <groupId>io.quarkus</groupId>
            <artifactId>quarkus-XXX-deployment</artifactId>
            <version>${quarkus.version}</version>
            <type>pom</type>
            <scope>test</scope>
            <exclusions>
                <exclusion>
                    <groupId>*</groupId>
                    <artifactId>*</artifactId>
                </exclusion>
            </exclusions>
        </dependency>

wrong project


[WIP] Add switchboard for sender routing

Another prototype used for plugins

Moved to https://github.com/dmcgowan/libchan-hack


vscodium: 1.65.1 -> 1.65.2

Motivation for this change
Upgrades vscodium from 1.65.1 to 1.65.2
This PR was automatically generated by nixpkgs-upkeep.

CI workflow that created this PR.
Internal tag: a616c2ed93485de7590dbce9436874e0.

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@ofborg build vscodium
@ofborg test vscodium.xorg
@ofborg test vscodium.wayland


fixed yarn scheduler doc typos

This PR is trying to fix #1574
The change list is following:

fixed typos
add block code type

👍

@ashvina - can you please check?

Oops! CI tests are failed......
Is there anything we could do to make the gateway_looper_unittest passed?


ModifiersStatusKeeper.

Fix for https://github.com/ergoplatform/ergo/issues/342

Coverage remained the same at 46.671% when pulling 8dad52683f40fc3f4ba51afba8c9fc38039075a9 on i342 into 87376ceb71d857cf41eb6926180db87300badf92 on master.

Same as #281 but without guava cache. Please merge one of this 2 pull requests

@kushti Usage was added.
Status Received includes that it is in cache, this is written in comments to this class https://github.com/ScorexFoundation/Scorex/pull/280/files#diff-4743027b9f2f35bb4a0ffeb11cd7c2c1R78

@ceilican you notes were fixed, please make one more round of review


[Bug]: serverOptions isn't been exposed in StaticService class

Which Devopness module(s) are the source of the bug?
SDK-JS
SDK Version
2.115.0
Expected behavior
As a SDK user, i expected that the StaticService class should have a serverOptions property
What is actually happening?
StaticService doesn't have a serverOptions property
Reproduction link
https://github.com/devopness/devopness/blob/7344938b224e461ce488e0496890389dc59baeab/packages/sdks/javascript/src/services/StaticService.ts#L13C1-L25C2
Steps to reproduce

Instantiate DevopnessApiClient.

const devopnessApi = new DevopnessApiClient({ baseURL: BASE_URL })

Try access devopnessApi.static.serverOptions
See that serverOptions property doesn't exists

Additional details
No response

can i take this issue?

@vianaz sure thing!
Feel free to submit a pull request.
Please reference this issue on the PR description.

@jfoliveira PR merged :))
Should i close this issue? I don't see nothing about in CONTRIBUTING

@jfoliveira PR merged :)) Should i close this issue? In CONTRIBUTING says that auto close this issue, but this doesn't happens

You apparently didn't follow the fourth step on Making Changes and submitting Pull Requests by adding the supported keyword in the PR's description. You can see the supported keywords in the documentation.
Perhaps a change to the Pull Request template could streamline this process?

Perhaps a change to the Pull Request template could streamline this process?

@brlipi yeah :)) In Pull Request template has something about Jira issue and i don't have access to Jira, maybe should be changed to some like:
## Issues resolved by this PR
<!-- Check list box of Issues completed by this PR -->

- [ ] Closes #ISSUE-NUMBER

What do you think?

Perhaps a change to the Pull Request template could streamline this process?

@brlipi yeah :)) In Pull Request template has something about Jira issue and i don't have access to Jira, maybe should be changed to some like:
## Issues resolved by this PR
<!-- Check list box of Issues completed by this PR -->

- [ ] Closes #ISSUE-NUMBER

What do you think?

@brlipi @vianaz
Changes applied in https://github.com/devopness/devopness/pull/827


Add missing diagnostic_updater dependency to system_monitor

Bug fix
Fixed bug
Add missing diagnostic_updater dependency to system_monitor
Fix applied
Added to package.xml and CMakeLists.txt

Any updates here? This fix seems trivial as per ROS1 practices.


About downstream task and DropPath

Thank you for your great ideas and work.
I have currently re-implemented RDNet Backbone with Tensorflow, and I am trying to apply it to Human Pose Estimation(HPE) as a downstream task and I am asking you because I have the following questions:

From what I understand after reading RDNet paper, RDNet backbone uses Stochastic Depth(DropPath), but RDNet's DenseBlock class only declares DropPath and doesn't seem to use it. Is this the part that was intended? If yes, please explain why you didn't use it.
As a downstream task, I am trying to train a model by applying RDNet to the HPE task, but I have confirmed that the model is not trained well. I have tried several times by modifying hyperparameters such as batch size, LR, etc., but the model is not trained well. As a curiosity about this, could the training be sensitive or not trained well when applying RDNet Backbone to the downstream task?
The conditions used in training are as follows:

Backbone: RDNet-Tiny (pretrained: X)
LR Scheduler: MultiStepLR
LR: 0.001 (also tried lower LR)
batch size: 64 (also tried 16, 32)
optimizer: Adam

한국어 버전(Korean Translation)
RDNet이라는 좋은 아이디어와 결과물을 공유 해주셔서 감사합니다.
현재 저는 RDNet Backbone을 Tensorflow로 재 구현하여, downstream task로 Human Pose Estimation(HPE)에 적용하고자 하는 상황 중에 궁금한 점이 생겨 아래의 질문들을 문의드립니다:

RDNet 논문을 이해하기로 RDNet Backbone은 Stochastic Depth(DropPath)를 사용하는 것으로 알고 있습니다. 하지만 RDNet의 DenseBlock 클래스에서 DropPath를 선언만 하고 사용하지 않는 것으로 보입니다. 이 부분이 의도된 것이 맞는 문의드립니다. 만약, 의도된 사항이 맞다면 그 이유도 설명 부탁드립니다.
downstream task로 RDNet Backbone을 HPE task에 적용하고자 시도한 결과, 모델의 학습이 잘 이루어지지 않음을 확인했습니다. batch size나 LR과 같은 hyperparamter도 수정하여 여러 번 시도 해봤지만 이 역시 학습이 잘 되지 않았습니다. 이에 대한 궁금증으로 RDNet Backbone을 downstream task에 적용할 경우, 학습이 민감해지거나(hyperparameter 등으로 인해), 학습이 잘 안될 수도 있을지 궁금합니다:
학습 때 적용한 조건들은 다음과 같습니다.

Backbone: RDNet-Tiny (pretrained: X)
LR Scheduler: MultiStepLR
LR: 0.001 (also tried lower LR)
batch size: 64 (also tried 16, 32)
optimizer: Adam

Sincerely appreciate your interest in our work!

During the process of creating the release-specific code, there was an instance of code omission. I sincerely apologize for this oversight. I will ensure that the necessary corrections are implemented and provide you with an update once completed. (cc @ogencoglu )

All the tables and figures reported in the paper (for downstream tasks) are based on experiments conducted using IN-1k pretrained weights. For RDNet, I empirically observe that its initial convergence is slower compared to other networks. This can be interpreted as a difficulty in effectively training the network in its early stages. When the pretrained argument is set to False and the network is trained on downstream tasks, this issue can persist. I believe that considering pretraining is important for RDNet, especially when the downstream data is limited and the training epochs are short.

The bug has been fixed. Please check it on release 0.1.2 !
Additionally, I plan to integrate RDNet into the timm package.
timm issue : https://github.com/huggingface/pytorch-image-models/issues/2241
I will re-train RDNet during this process and re-validate the code for any potential bugs.
Stay tuned for updates!

Thank you for checking and correcting the bug quickly!
I will close this issue.


Web golden flake

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket.appspot.com/8862086434858666720/+/steps/felt_test_chrome/0/stdout#L39178_0
Text:
00:03 +0: screenshot test reports failure
 00:03 +0 -1: screenshot test reports failure [E]
   Golden file smoke_test.png did not match the image generated by the test.
   (2.9188% of pixels were different. Maximum allowed rate is: 0.2800%).
   You can view the test report in your browser by opening:
   /b/s/w/ir/cache/builder/src/flutter/lib/web_ui/.dart_tool/test_results/smoke_test.report.html
   To update the golden file call matchGoldenFile('smoke_test.png', write: true).
   Golden file: /b/s/w/ir/cache/builder/src/flutter/lib/web_ui/.dart_tool/test_results/smoke_test.expected.png
   Actual file: /b/s/w/ir/cache/builder/src/flutter/lib/web_ui/.dart_tool/test_results/smoke_test.actual.png

Failed on presubmit
@nturgut @yjbanov

This has flaked 4 out of the last 13 builds on Mac Web Engine: https://ci.chromium.org/p/flutter/builders/prod/Mac Web Engine.
This is too flaky, so I am bumping this up to P1.

Lowering back to P4. The original issue is due to Chrome process failing to start:
UnknownException (13): unknown error: Chrome failed to start: exited abnormally.
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /b/s/w/ir/cache/builder/src/flutter/lib/web_ui/.dart_tool/chrome/768968/chrome-linux/chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
  (Driver info: chromedriver=84.0.4147.30 (48b3e868b4cc0aa7e8149519690b6f6949e110a8-refs/branch-heads/4147@{#310}),platform=Linux 4.9.0-11-amd64 x86_64)

Updating the issue description

In some other test runners I added some protection against this, but I'm not sure if those fixes covered integration tests.

Well, more specifically I added handling of a flaky glibc bug: https://github.com/flutter/flutter/pull/67466. I'm not sure if this crash is due to the same bug.

I haven't seen this flake in a long time. Closing for now.


Implement Client SDK registration

Codecov Report
Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (104f711) 97.83% compared to head (1fa7efa) 96.84%.

Files
Patch %
Lines

src/api/cprclient.cpp
87.09%
4 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #21      +/-   ##
==========================================
- Coverage   97.83%   96.84%   -0.99%
==========================================
  Files          16       16
  Lines         277      317      +40
==========================================
+ Hits          271      307      +36
- Misses          6       10       +4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Feat: Simple profiler for BuiltinLogger

Maybe not so simple

Node 18 is missing Intl unit:
RangeError: Invalid unit argument for Intl.NumberFormat() 'microsecond'

What I found out during this work is that Ramda methods should rather be used once for making own functions only, not in loops.

I'm thinking that for the purposes of express-zod-api (for possible usage inside handlers that may happen to serve for multiple users async) it might be better to have not so simple profiler, but the one with references.


Re-introduce stable pipeline for torch-ort

This pull request reintroduces the stable pipelines for torch_ort. This stable pipeline should be run manually using the ADO link to the pipeline.
The differences between nightly and stable pipelines:

Nightly pipeline will be triggered every night as 12:00 AM. The stable pipeline will run only when manually triggered.
Nightly pipeline installs onnxruntime-training nightly package where as the stable pipeline installs the onnxruntime-training stable package when building the wheel.
Nightly pipeline will upload a wheel once on every run where as the stable pipeline will not upload the wheel file. Both pipelines will still publish the wheel file to the pipeline published artifacts.

Another way would be using templates and passing all the difference parameters for the template, such as dockerfile, boolean for the upload, requirements file, etc

I am actually doing that. The main pipelines are passing the parameters to the template and the template is the common execution path for the two pipelines.


fix: validate refund amount with amount_captured instead of amount

Type of Change

[x] Bugfix
[ ] New feature
[ ] Enhancement
[ ] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description

Refund amount was being validated with amount field in payment_attempt.
In fact it should be validated with amount_captured field in payment_intent.
Because refund can only be made with amount that has already being captured.
Additional Changes

[ ] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

How did you test it?

Manual
Partially captured payment

Refund with refund_amount greater than amount_recieved(amount_captured)

Refund with refund_amount less than amount_recieved.

Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed the submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

@hrithikesh026 Can you add the same cases in postman aswell


WIP: Fix Array defaults for struct.PyTreeNode

I've been working some on this and made a little progress at least: I'm fetching the default values for all jax.Arrays and setting a field with default_factory= lambda: default.
The problem is now that Python only remembers the last value for default from the loop, and thus will initialize all other Array attributes erroneously to this value.

@epignatelli The code now passes all tests. The solution can probably be made more elegant.
What's the best way to test/benchmark that no funny business occurs during compilation?
I tried running some scripts under test/performance, but they threw errors for me, e.g.,

TypeError: scan body function carry input and carry output must have the same pytree structure, but they differ:  The input carry component c.info is a <class 'dict'> with 0 child but the corresponding component of the carry output is a <class 'dict'> with 1 child, so the numbers of children do not match, with the symmetric difference of key sets: {'return'}.

when running python tests/performance/grid.py.


Update README description, repo description, and repo tags

Given that this org has expanded into other areas that also have Docker-related things, I think the emoji 🐳 should be changed to something like a toolbox 🧰
While we're at it, why not update the description to include a tag to the official @devcontainers org?
Here's my proposal:
Readme and repo description:
🧰 Feature addons for @devcontainers
Repo tags:
devcontainers devcontainer-feature
/assign @jcbhmr to change the readme
I will need @danielbraun89 to actually edit the repo's description and tags
Oh, and sidenote, if #284 gets merged, we'll want to add a website link to https://devcontainers-contrib.github.io/features

I'm trying to find out more about act-asdf but the automatically generated documentation is quite poor. I think it would be helpful if you could expand the documentation for newcomers.

@gromag You're absolutely right that documentation isn't very there at all. @danielbraun89 recently has transitioned (a few weeks ago) to a more complex system of creating features, and the documentation that I wrote before is now sorely out-of-date.
Here's a possible future readme:

And maybe we'll get some GitHub Pages website spun up to serve more in depth documentation about each feature! Follow progress on https://github.com/devcontainers-contrib/features/pull/291 and more discussion in https://github.com/devcontainers-contrib/features/discussions/290 for more talk about current pitfalls and friction points.

@gromag If you have any ideas for stuff that you want to see on a theoretical HTML GitHub Pages site, tell me! I want to know! So far my only idea for improvement is too add a link to create a new GitHub Issue.
You can track the future [id].php file that generates all this stuff here: https://github.com/jcbhmr/devcontainers-contrib-features/blob/main/docs/pages/[id].php

📬 @danielbraun89 Pls add tags/update description of repo:

Doubtful this will happen. Closing to focus on actual bugs.


Get rid of BaseModel for Volume model

there is a problem with root disks. Sometimes there are 2 actions in actionbar that appear for root disks (detach and delete), though they should be available only for data disks. This is a model problem, fixed in #630, but it is proposed to make a refactoring in this ticket (c) @ksendart


ModuleNotFoundError: No module named 'igt_res_gan'

Hi friends
I am getting this error when running controller_trainer.py : ModuleNotFoundError: No module named 'igt_res_gan'
I guess the authors might have forgotten to add igt_res_gan module.
please can anyone provide it or any help is highly appreciated.
README.md

hello, sorry for bothering you but I do need your help!
Have you ever solved the issue? Can you give me some help for finding the igt_res_gan?

Thanks a lot for your kind reply!
Can you please tell me where can I find "igt_res_gan"? Is that a repo posted on github? I have searched for it but I found nothing

@zhang373
I couldn't find it either. let me know if you find.

Thanks a lot!
I understand what you mean, I will have a try!


[UXP-20366] Addition of Overlay-0.37.0

Adding wrapper for overlay.
Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@deepthi-majji - Please add aliasing changes in utils/alias.js

@deepthi-majji - Please run yarn format:fix to fix formatting error in the PR.


Update lfortran to v 0.33.0

PS: We might need to rerun the CI once LFortran 0.33.0 is available at conda-forge.

LFortran v0.33.0 seems to be available at https://anaconda.org/conda-forge/lfortran/files, but conda is unable to install this version yet (I also checked this locally on my system).
@certik Do you know how much time it usually takes for conda to work with newer version once that version is uploaded at https://anaconda.org/conda-forge/lfortran/files?

Usually an hour or so. It's already available for me locally on Apple M1.


[LEAGUE LOADER]: ESPN Loader throwing 403

League Loader
ESPN
Summary
ESPN Loader is throwing 403 errors because ESPN changed threir supported endpoint. The espn_api that is used has fixed it's underlying implementation in version 0.36.0. It looks like dependabot is finding that there is a new version, but it isn't submitting a pull request to update it. Can we update it manually?
League Info
All leagues fail
Error Logs
ESPN returns a 403

Thank you @kylehild

Fixed in this release


Detail workflow for plugins that are not open source

So I create a plugin and it gets added to the main app. What if this plugin should not be open sourced? How do we I move it to an internal repo and stil use it in the main Backstage app?
This needs to be documented, and ideally supported in the CLI.

Should document this as a part of #287. The scaffolded app should be able to create it's own plugins.

Some of this now exists in the https://backstage.io/docs/plugins/ .
But I think specifically closure of this issue involves authoring the page here:
https://backstage.io/docs/plugins/publish-private

Still open for contributors, esp those who may be doing this already.

Some of this now exists in the https://backstage.io/docs/plugins/ .
But I think specifically closure of this issue involves authoring the page here:
https://backstage.io/docs/plugins/publish-private

Still open for contributors, esp those who may be doing this already.

Curious if this publish private page is intended to document just plugins that are published to a private repo and/or for custom plugins within an orgs backstage instances monorepo?

Curious if this publish private page is intended to document just plugins that are published to a private repo and/or for custom plugins within an orgs backstage instances monorepo?

Both, right? I think the dev experience should be fairly similar.

Both, right? I think the dev experience should be fairly similar.

Partially the same I would think. However, separate repos requires more setup and are more work to test from my experience. I don't think there is much of a difference between publishing open ba private in the latter. So probably makes sense to cover all scenarios and rename the docs page accordingly.

Partially the same I would think. However, separate repos requires more setup and are more work to test from my experience. I don't think there is much of a difference between publishing open ba private in the latter. So probably makes sense to cover all scenarios and rename the docs page accordingly.

Hey Team!
Is anything pending on this? I am sorting the good first issue backlog on age to see if I can help cleanup :smile:
Its not 100% clear to me whats still pending on this... Please let me know if I can help out?
Thanks!

@Parsifal-M thank you for doing that! 😁
To be honest this one doesn't seem vary actionable at this point, so going to close it. Glad if you want to have a look at a different one though!


[7.x] Introduced basic padding (both, left, right) methods to Str and Stringable…

Basically, this brings PHP's str_pad() into Laravel's Str and Stringable classes.  I looked quickly for such support in the code and the docs and couldn't find any.  Likewise, I couldn't find any previous PRs (accepted or rejected) that mentioned str_pad.
I added tests, but no documentation.  I don't mind updating the docs once I know it's likely to be accepted.  Hopefully that makes sense.
I explicitly provided the pad type argument when it matches the default.  I thought about removing it, but decided that being explicit might be the better choice after all.
Any feedback is welcome.
Thx.  🤓

@telkins can you also PR these to the docs? Thanks!

@telkins can you also PR these to the docs? Thanks!

@driesvints Only if I can get my hands on Blade UI Kit...right now...! 😜
Kidding...of course.  I'll try to get that done this weekend, if that's OK.
Thx.

I'll try to get that done this weekend, if that's OK.

@driesvints I just decided to try to get it out of the way right now.  Hope it's OK.
https://github.com/laravel/docs/pull/6283
Thx.


Pip installation problem

error in gym setup command: 'extras_require' must be a dictionary whose values are strings or lists of strings containing valid project/version requirement specifiers.

Hi, this is most likely the same pip/setuptools version issue described here.
pip install setuptools==65.5.0 pip==21  # gym 0.21 installation is broken with more recent versions
pip install wheel==0.38.0

should fix it.

I tried creating an up-to-date conda environment, cloned the rlrd repo and installed it with pip install -e ., but could not reproduce the issue, the installation went smoothly.
Setuptools is 68.2.2, pip is 23.3.1 and python is 3.10.14

I had the same issue and it was resolved by changing the gym version in the setup.py


Switch to built-in cilium ingress/gateway-api

See https://github.com/cilium/cilium/pull/30840. Just landed, so at least wait until a release picks it up.

https://docs.cilium.io/en/stable/network/servicemesh/ingress/


[control] add tasks to start/stop/configure HEV cleaning cycles

Adds the following tasks:

get_clean_cycle_status: Get the current cleaning cycle status from the target bulb
get_clean_default_config: Get the default HEV cleaning cycle configuration for the target bulb
set_clean_default_config: Set the default clean cycle configuration for a device
start_clean_cycle: Start a cleaning cycle on an HEV-capable bulb
stop_clean_cycle: Stop a cleaning cycle on an HEV-capable bulb

The reason for the draft PR is because I'm not happy with the tests and could use a nudges in the right direction on how best to test things like changing the default configuration or current status.
Signed-off-by: Avi Miller<EMAIL_ADDRESS>

I'll squash all the commits before I disable draft mode.

I've updated clean.py and tweaked the tests so they continue to pass. I'll look into the other stuff during the week.

While you were reviewing, I got this to work:
$ ./command clean/status
{
    "results": {
        "d073d56d6b63": {
            "active": "yes",
            "duration": 7200,
            "power": "off",
            "remaining": 7197
        },
        "d073d56e137b": {
            "active": "no",
            "duration": 600,
            "power": "off",
            "remaining": 0
        }
    }
}

My review of your review will be reviewed momentarily.

I'll squash it all up with a nice commit message when I'm done, but I thought I'd share my progress, so here's the result of today's efforts.

Style/nomenclature question: I've used clean in user-visible text but have been inconsistent with the name in the code. I'd prefer to stick with clean for classes, functions and variables too, but as the protocol and capabilities refers to hev, I though I'd just check that that was ok.

Goooooood question.
I'd say clean is better externally because it's the effect, whereas hev is appropriate internally cause it's the implementation.

I'd say clean is better externally because it's the effect, whereas hev is appropriate internally cause it's the implementation.

Yep, makes sense.

Next question: do you have a preference/standard for formatting the output? I'd prefer to output JSON but other similar tasks output non-structured text, so I went with that instead. I figure that JSON is more useful for integration and anyone using the lifx CLI is probably savvy enough to read it anyway.

cli actions is for humans and not overly suitable for machines :)

I'll humanize my output once everything actually works. :) I shall also ponder opening an ER for an --output global flag so that --output json becomes a thing. :)

Problem with an --output global is you'd have to make everything support it. To do that nicely I'd make it so that actions get an object they can use to do the different styles of output (would also mean nothing uses print anymore which would be nice). Discussion for another time lol.

I shall continue to cheat and just use my Interactor instance which returns all JSON all the time. 😛

yeah, tbf, json over http is for machine consumption :)

What's the right way to add a dependency to Photons?
I want to use humanize to make the duration output friendlier, ie. instead of Time left: 7209 seconds it becomes Time left: 1 hour, 59 minutes and 15 seconds

yeah, humanize is fine to add specifically to interactor. Add it here https://github.com/delfick/photons/blob/main/apps/interactor/setup.py#L15

I've squashed this down to two commits: one for Photons and the other for Interactor. Would appreciate another review as I've tweaked it in all sorts of places.

We are all going to ignore the fact that I had to push linting fixes for the task into the interactor commit.

hehe, awesome. will review when back home from sanity walk :)
On Wed, 21 Jul 2021, 1:37 pm Avi Miller, @.***> wrote:

We are all going to ignore the fact that I had to push linting fixes for
the task into the interactor commit.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/delfick/photons/pull/68#issuecomment-883861082, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA2V5O3EVDFSH63B3DKWNTTYY6IFANCNFSM5ARTFYRA
.

nah, it's better to set res_required to False for Sets and just rely on acks

10-4.

I haven't abandoned this, I just had a lot of life happening all at once. I've been using Photons to drive an HEV cycle on a nightly basis for two weeks now and it's great.  However, that anecdote doesn't qualify as "testing", and I would appreciate any guidance you may have to get me on the right track with what's missing.

not a competition, but I'd bet I've had more of the whole "life" thing get in the way hahahha
Umm, I think it was just tests right?
So tests for interactor and tests for the special objects that get information from the lights.

Yep, it's just the tests. And I haven't been able to get my head around how the special objects work or really an understanding of how mocking a bulb response actually tests the code.

For example, run git am --keep-non-patch *.patch on these https://gist.github.com/delfick/e15b8a65e8313e0953256f65e09e3fdd
and then implement for HEVConfigPlan (it's included and marked as skip)

also, in writing those tests, I'm not sure your transformation of last_power for HevStatusPlan makes sense

Thanks! I really appreciate the assist.

also, in writing those tests, I'm not sure your transformation of last_power for HevStatusPlan makes sense

I'm not sure my transformation makes sense either; it's the coding equivalent of a double negative. For some reason lost to time and my failing memory, I thought it would be a good idea to return whether or not the bulbs would be powered off at the end of the cycle. I think it was because I couldn't think of a short enough way of describing the "Power state to which the bulb will be set when the HEV cycle ends".
Anyhoo, the TL;DR is that I'll change it to return the power state to which the bulb will be set when the HEV cycle ends. 😂

:)

Thanks again for doing most of the work here. I've finished this off, added tests, and change duration parameters to be duration_s parameters.
And pushed to main.
https://github.com/delfick/photons/compare/def71bfecad68725d2beb32409d9b225128b7075...c54b5bc


IDL Doc Field

Adds a new, optional doc field to several of the IDL structs. The program module, instruction functions, and account structs are searched for inner doc comments (this is intended to minimize intrusion on existing programs, which likely use outer doc comments on those elements). IxArg and IdlField also will grab their associated doc comment.
The doc field is not included in the IDL JSON in cases when it parses to None.
Todo:

Someone already got close with adding a docs field to the AccountField, it just needs wiring up.
Considering a command-line flag to suppress inclusion of doc fields in anchor idl parse.

hey @ebrightfield I would like to get this into the next release. Do you have time to finish this or do you want me to take over?

We can include outer comments in the IDL too. But we should include a feature like tom did in his PR https://github.com/project-serum/anchor/pull/1546 I suggest we make this an anti-feature though. So it's enabled by default and the feature turns it off.
agree that a flag to supress docs in anchor idl parse would be good
Please also have a look at tom's PR regarding the tests

@paul-schaaf Awesome! I can knock it out tomorrow.
To reiterate, action items are:

include outer doc comments
put it behind an (anti-)feature flag
--no-docs flag in anchor idl parse
additional testing in the fashion of Tom's PR #1546

great!

To reiterate, action items are:

yup!
thanks! @ebrightfield

@paul-schaaf just took care of everything, or nearly. Unsure how best to automate testing the anchor idl parse --no-doc, and turning on/off the no_docs feature (they work when I manually test). The rest of the feature has accompanying Typescript tests in the same fashion as Tom's PR.
Also, took the liberty of skipping over the CHECK doc strings during parsing.

On second thought, I think we don't need the feature.
It seems like features are most useful if your code changes depending on whether your code would change depending on whether it's turned off or on. This isn't the case here, so I think that having a flag on the build command is good enough.

Also, took the liberty of skipping over the CHECK doc strings during parsing.

sounds good!

Okay, feature removed.
Any ideas on how best to automate test of anchor idl parse --no-doc?
Also, should --no-doc also be an option on anchor build?

Also, should --no-doc also be an option on anchor build?

yes that is what I meant by flag on build

Any ideas on how best to automate test of anchor idl parse --no-doc?

Manual testing is fine. Not critical if it doesn't work.

I think it would be easier to parse the idl doc field if it was an array of the lines instead of a space separated list
also pls move the tests into their own program inside the misc workspace and have them run as a separate test suite. Once you merge master and fix the conflicts, you'll be able to see 2 test suites in misc already that you can check out for how to do it

Okay, --no-doc added to build and publish commands. And doc fields are Option<Vec<String>> instead of Option<String> now.
After merging, I created a dedicated program for testing under tests/misc/programs/idl_doc, and I emulated the structure of the rest of the misc tests on master, although I am too much of a newbie with JS tooling and could not figure out how they're supposed to get executed.

what's the need for --no-doc for publish? I can see there's a call to build in the publish code but I think thats only used to check whether compilation succeeded

Ah, got it. Wasn't sure about that one. Just removed it from the publish command.

@ebrightfield anything else that youre about to push or can I merge now?

I'm satisfied, go for it.

thanks for the contribution!


Attribute error when meshing CadQuery solids

Hello, I'm working on introducing Stellarmesh as the primary open-source DAGMC modeling workflow for ParaStell. Firstly, I'd like to say that I appreciate the work done here to develop and maintain a freely available DAGMC faceting toolset. I know I'm not the only one with an interest in such capability. Thus far, the API has been a breeze to understand, so thank you for that as well.
Unfortunately, I'm running into the following AttributeError when I attempt to mesh my Geometry class object:
AttributeError: 'OCP.TopoDS.TopoDS_Solid' object has no attribute '_address'

The relevant code snippet is
geometry = stellarmesh.Geometry(solids, material_names)
mesh = stellarmesh.Mesh.from_geometry(
    geometry,
    min_mesh_size=20,
    max_mesh_size=50
)

where solids is a list of cadquery.occ_impl.shapes.Solid and cadquery.occ_impl.shapes.Compound objects and material_names is a list of corresponding strings. In case it's relevant, I've tried with just solid objects, converting the CadQuery compounds to solids, and received the same error. I've poked around in the CadQuery and OpenCASCADE documentation, trying to find an _address attribute referenced anywhere, without success. Does anyone here have a better idea of why this is occurring? For the record, I'm using CadQuery 2.4.0.
Thanks!

The code is failing on line 112 of mesh.py:
111    for s, m in zip(geometry.solids, geometry.material_names, strict=True):
112        dim_tags = gmsh.model.occ.import_shapes_native_pointer(s._address())

Hi @connoramoreno and thanks for reporting this. What version of OCP do you have installed? And did you install cadquery through pip or conda?
After digging a bit, I found this to be where the _address method originates from:
https://github.com/CadQuery/OCP/blob/544d7fd55b997dff26eb5b1009d17d97b42063b1/ocp.toml#L520-L524

Also noting that _address was added in OCP 7.7.1

Looks like I'm on OCP <IP_ADDRESS> (installed via conda alongside CadQuery)


Base font re-size

Reduces base font size from 19px to 16px (applies to text, labels)
Increases any font at 18px to 19px (standardise the sizing)
Decreases large headings from 36px to 30px
Decreases medium headings from 24px to 20px
You probably can't tell from the screenshot, but basically everything should be 16px unless it's a heading:

Nice! Jon will be happy :D


is there a healthcheck?

hey guys,
I am trying to set up this service locally and want to know if there is a health check for this service
Thanks,
Vignesh

Don't recall there is a health check since this is not really a REST
service.  Most of the time people wants to check the consumer offset lags
to see whether secor is working properly, there is a
ProgressMonitorMain.java which contains those kind of trackings, you can
take a look at that class.
On Thu, Jul 26, 2018 at 7:04 PM, vigneshsenapathy<EMAIL_ADDRESS>wrote:

hey guys,
I am trying to set up this service locally and want to know if there is a
health check for this service
Thanks,
Vignesh
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pinterest/secor/issues/443, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHCX_1rWYcP02C_XYWZn-MpyMT5ezOxxks5uKmctgaJpZM4ViwrT
.

What about using the Ostrich port?


Lawnicons as icon pack (cleanups)

This PR can be merged after https://github.com/LawnchairLauncher/lawnicons/pull/815 .

Since the main PR has been merged, please update this PR (fast-foward) before I merge it.