text:
Specify code style guide

The contributing guide does not specify any code style. the obvious "respect pep 8" is easy, but...
What format do we prefer for docstrings? This SO post has some samples: https://stackoverflow.com/a/24385103/1819160.
I kind of like Google's style because it is more readable as-is, and it is supported by Sphinx so docs are the same once rendered. https://www.sphinx-doc.org/en/master/usage/extensions/example_google.html#example-google
Please drop your 0.02 so the contributing guide can be updated.

Google's style is ok with me, let me drop the link, I think it would be helpful for the future:

https://google.github.io/styleguide/pyguide.html

authors: oscarmlage telenieko

repo: oscarmlage/django-cruds-adminlte


text:
about section

WHAT DOES THIS PR DO?

Adds in a new frontend component
Adds about section.

HOW TO TEST THIS PR:

I added a new package, so  'run gh pr checkout 27'  'npm install'  'npm run dev'
Scroll to bottom of page. Check if all information is up to date.

ADDITIONAL NOTES:
No styling to this component at this time.  Will add styles on next PR.

@davidzhangnyc @JefZheng also please verify that the Navbar component works as expected with the new About component.

source: gharchive/pull-request

repo: oslabs-beta/Kubiquity

license: MIT

license_type: permissive

license_source: github-api


text:
area.id() is different then the actual relation id

https://www.openstreetmap.org/relation/161993 - this is the relation id for "Utah" the state.
First I create a filter for the planet extract:
osmium::TagsFilter filter{false};
filter.add_rule(true, "boundary", "administrative");

Then on finding each admin boundary I check and save the id and geometry... finding the ID as:
area.id()
but this is the wrong integer.
Utah is saved as ID: 323987. Which isn't even a boundary relation in osm.
Is there a separate function for the original relation id?
Thanks!

doing some research in the code itself, looks like the function I was looking for was:
area.orig_id()

source: gharchive/issue

repo: osmcode/libosmium


text:
Pin to libosmium release for binary builds

Our travis script (and therefore binary packages) always pull from latest master libosmium. How about we start pulling from a tagged version?

https://github.com/osmcode/node-osmium/blob/master/.travis.yml#L61

/cc @joto

I have updated the release instructions in https://github.com/osmcode/osmium-suite/blob/master/make_releases.md . We'll do it on the next release.

This is now done for travis and appveyor.

authors: joto springmeyer

repo: osmcode/node-osmium


text:
Using node cache to quickly find roads?

I'm looking for an efficient (as possible) way to find ways that contain a given node. I started by just using a SimpleHandler to walk all of the pbf and make a cache that maps nodes to ways, but can https://github.com/osmcode/pyosmium/blob/master/examples/use_nodecache.py be used to make this more efficient?

NodeLocationsForWays is the reverse of what you need. Skimming through the libosmium code I found ObjectRelations which, as far as I understand, may create the node to way index.
Though I don't see this exposed in pyosmium.

OK, cool, then I'll just walk all the ways.
Should I walk the relations too to find the names, or do ways always have a name?

Depends on what names you plan to find. If you're looking for street names then usually they are on way level.

This needs indeed the osmium::index::MultiMap because a node may be in multiple ways. That class is not yet exposed to pyosmium. It would be interesting to have though together with the ObjectRelations handler.

authors: lonvia retorquere wiktorn

repo: osmcode/pyosmium

license_source: bigquery


text:
feature/#1346 - new ScaleDiskOverlay class

A demo can be found in the "More Samples / Data / Marker" demo.
New class:

ScaleDiskOverlay: displays a disk of a given radius (distance) around a GeoPoint

Impacts:

GeoConstants: added enum UnitOfMeasure; gently refactored
ScaleBarOverlay: refactored the display of scale text, in order to be reused in ScaleDiskOverlay
strings.xml: created format_distance_only_% and format_distance_value_unit
SampleMarker: added a ScaleDiskOverlay for each POI

i like it, good work

repo: osmdroid/osmdroid


text:
Watch for fuel tanks and other industrial infrastructure

Something to look for when we import and validate. Some things like this object https://www.openstreetmap.org/way/408511408 are tagged with building=industrial, and they should probably have the tag man_made=storage_tank as well.
See http://wiki.openstreetmap.org/wiki/Tag:man_made%3Dstorage_tank, which suggests that it's acceptable to leave the building tag, too.
@imagico spotted this on the mailing list.

Good catch. Any way to check automatically for round features and flag them for tagging as tanks, silos or smokestacks?

Maybe catching round things could be done after the fact using Mapbox QA tiles?

We can definitely catch round buildings, but automatic tagging maybe risky.  What we can do is find all these round buildings and have a micro-task to do manual review by mappers.

My idea was mainly to supplement these with a fixme tag to indicate the default tags are likely insufficient.  Not every round structure in an industrial area is a storage tank.
The industrial areas are fairly concentrated so it might already be sufficient if those who take on these parts plan enough time to work this out by hand - ideally do some research in what kind of product/process is done there and tag accordingly (i.e. also content=* etc.)  In general with just buildings mapping of industrial facilities will never achieve any reasonable level of completeness in comparison to residential or commercial areas - there are so many different mappable structures there and buildings are just one of them.

@imagico, I like adding fixme for building=industrial.  I can run that for the rest of the imported data.  For the already imported data, we can ask validators to work on this specific task.

FWIW, last week, I did a bunch of the import tiles around the refineries (lots of tanks), and I manually changed building=industrial to man_made=storage_tank - at least, I did it for most of them.  It's a quick and easy thing to do.

authors: almccon bdiscoe imagico maning talllguy

repo: osmlab/labuildings


text:
update FET token IBC denom

new channel open after the fetchhub-3 migration to fetchhub-4

Thanks @Galadrin ! I have make new PR for frontier assetlist : https://github.com/osmosis-labs/assetlists/pull/139
We can switch on that, goin to close this one :)

authors: Galadrin IbrarMakaveli

repo: osmosis-labs/assetlists


text:
fix: data race related to last commit info; flush pruning heights as soon as changed

Context

Fixed data race related to last commit height concurrently written in Commit(...) and read in Query(...) and LastCommitID()
flush prune heights every time these are changed to avoid losing them if one of the commits fails

Related to: https://github.com/osmosis-labs/cosmos-sdk/issues/149

flush commit id and version atomically with updating rs.lastCommitInfo

Left some extra comments in code
Risks

This change introduced performance overhead due to synchronization in exchange for safety

closing in favor of #184

closing in support of #184

repo: osmosis-labs/cosmos-sdk


text:
Queries should return an error if the data at the requested height is not available

Background
Queries with --height on pruned state return the default values. Example:
❯ osmosisd query bank total --denom uosmo --height 5977650
amount: "0"
denom: uosmo

Suggested Design
Check if the IAVL and see if the version is stored. If it isn't, return an error.
Acceptance Criteria

Queries on pruned state return errors instead of defaults

Yeah this was a known tech debt that we need to come back to to fix in the sdk side.
From a brief investigation, I wonder why this is happening, where this error should be caught and returned as stated in
https://github.com/cosmos/cosmos-sdk/blob/main/baseapp/abci.go#L634-L641

Ah it's from how we handle CacheMultiStore, assigning myself for this issue for further investigation

This has been fixed

authors: ValarDragon mattverse nicolaslara

repo: osmosis-labs/osmosis


text:
Applying the x/farm logic to x/gamm module

I was hoping to apply the x/farm module to the x/gamm module as well. Currently, the x/gamm fee distribution mechanism accumulates the swap fees then gives the fee to the user upon claiming in proportion to the shares owned, so technically an LP who deposited later has some advantages if other users don’t claim their portion of the rewards as often. Therefore, I believe the F1 fee distribution mechanism is more reasonable so we should apply to the x/gamm module as well. Also, since there is no way to distribute the exit fee and the F1 distribution module will allow this as well.
However, this brings up another issue since each LP tokens have a different amount of fee reward accumulated, so unlocked LP tokens are technically not fungible with each other unless there is additional logic to stake the shares. Perhaps staking the share token upon minting by default could solve this. But the bigger issue that I see is that when the pool’s share tokens are staked to the pool, the lockup module isn’t able to be used. One option is to change the lockup module’s architecture, as going with the current implementation will force users to choose whether to receive the pool rewards or the Osmo farming rewards.
Pros:

Fee distribution is more equitable
Exit fee distribution can happen

Cons:

Requires a stake/unstake feature to be added to the pool shares
Need to come up with a different mechanism to distribute the exit fee
Not compatible with the current lockup module

Question:  Why not just add SwapFees into the pool, rather than distributed as rewards?  This way we don't need F1 or anything like that.  Just need to keep track of LP tokens and total shares.
This works as long as the token being distributed is part of the pool (which SwapFee tokens should be).
The place where this is a problem is when the token to be distributed (such as OSM liquidity rewards) is different to what's in the pools.  But I think for this, we don't need to have a continuous distribution.  That can be done in an epochized way, where it iterates over all recipients, but only like once a day or week or something.
I think this will remove a lot of this complexity

Question:  Why not just add SwapFees into the pool, rather than distributed as rewards?  This way we don't need F1 or anything like that.  Just need to keep track of LP tokens and total shares.
This works as long as the token being distributed is part of the pool (which SwapFee tokens should be).
The place where this is a problem is when the token to be distributed (such as OSM liquidity rewards) is different to what's in the pools.  But I think for this, we don't need to have a continuous distribution.  That can be done in an epochized way, where it iterates over all recipients, but only like once a day or week or something.
I think this will remove a lot of this complexity

Currently Balancer & Uniswap only calculate and distribute the fee upon withdrawal according to the portion of shares owned. The issue I see is that if I had 100 ATOM worth of fees to receive, and if someone deposits the same amount of liquidity right before I withdraw my swap fee gets cut in half even though I have been providing liquidity for longer.
However, I guess since this isn’t seen as a major issue on the Ethereum AMMs this may not be as big of an issue as I am thinking.
And like you’ve mentioned, the exit fee is paid in the share tokens which isn’t supported in the current implementation. However, since it seems like Balancer, even though has the exit fee but is fixed to a 0% value–so I’m okay with not prioritizing implementation for the exit fee.

Currently Balancer & Uniswap only calculate and distribute the fee upon withdrawal according to the portion of shares owned. The issue I see is that if I had 100 ATOM worth of fees to receive, and if someone deposits the same amount of liquidity right before I withdraw my swap fee gets cut in half even though I have been providing liquidity for longer.
However, I guess since this isn’t seen as a major issue on the Ethereum AMMs this may not be as big of an issue as I am thinking.
And like you’ve mentioned, the exit fee is paid in the share tokens which isn’t supported in the current implementation. However, since it seems like Balancer, even though has the exit fee but is fixed to a 0% value–so I’m okay with not prioritizing implementation for the exit fee.

And like you’ve mentioned, the exit fee is paid in the share tokens which isn’t supported in the current implementation.

So it seems the simplest solution would be to fix this, right?

Closing this due to switch to using x/incentives module.


text:
feat: allow sending denoms with URL encoding

Enable querying token factory with URL encoded token denom, that way LCD can be queried without failing due the following error:
{
  "code": 12,
  "message": "Not Implemented",
  "details": []
}

This will not cause issues because denoms aren't allowed to have % which will no create any collisions
LCD Query;

CLI Query:

based on: https://github.com/terra-money/core/pull/207

@emidev98 Thanks for the PR! Can you fix the lint please? 🙏

Hello @mattverse, for some reason the lint command does not work in my local. Could you run the linter please? Codewoners can push to the branch. Thanks!

@emidev98 Happy to merge this once lint is fixed!

Err we need to ensure we didn't introduce any serialization ambiguity here. We should be safe as long as:

URL escape only works with replacing input with a %
Chain denoms can't have % characters.

I feel uncomfortable relying on that first assumption in such a load bearing way though. Could we instead just do a find replace of %2F with /

Thanks @mattverse I have been very busy this days and didn't paid attention to some PRs.
I hope this helps you! 🥂

@ValarDragon Feel free to give secondary review for the change, planning to merge this by EOW!

@emidev98 Definitely does save alot of people's lives :) Thanks so much for the PR :)

authors: ValarDragon emidev98 mattverse


text:
Invokes wrong 'tsc' on windows with multiple tsc versions

On my windows, i have several TypeScript installations manually or automatically(by Visual Studio) installed. I have also installed nodejs global module 'tsc' (typescript).
Problem is when you have tsc.exe in "c:\Program Files (x86)\Microsoft SDKs\TypeScript\1.5\tsc.exe"  together with nodejs global module 'tsc' your gulp task _build will invoke tsc.exe (from program files) not nodejs version 'tsc'.
For fix, change: exec('tsc') to  exec('tsc.cmd') within file gulpfile.js.

This got me too. Thanks @psulek!

Thanks for the reporting it guys. I'm not a Windows user and therefore have no way of discovering such very OS-specific bugs. I'm working on the next release currently and will incorporate fix for this in it.

This is fixed in the latest release - v1.0.0. The generator now installs TypeScript as local dev dependency and the gulp prepends node_modules/.bin to process.env.PATH thereby ensuring the local tsc is always used.

authors: ospatil psulek rumit91

repo: ospatil/generator-node-typescript

license: mit


text:
Unable to initialize rmf_fleet_adapter

Hi everyone. Does anyone what are the possible causes that results in not initializing rmf_fleet_adapter? I am able to execute the launch file and opened up Gazebo and RViz but it shows the following results below,
[ERROR] [full_control-17]: process has died [pid 21663, exit code -11, cmd '/hom/rmf_demos_ws/install/rmf_fleet_adapter/lib/rmf_fleet_adapter/full_control --ros-args -r __node:=deliveryRobot_fleet_adapter --params-file /tmp/launch_params_0egknyqn --params-file /tmp/launch_params_wmc47pt3 --params-file /tmp/launch_params_i9ovtjzf --params-file /tmp/launch_params_e4mqcpom --params-file /tmp/launch_params_ega3xqll --params-file /tmp/launch_params_q45ajgjg --params-file /tmp/launch_params_7bi_6n2s --params-file /tmp/launch_params_kmsrl3f3 --params-file /tmp/launch_params_zrhi1zlf --params-file /tmp/launch_params_9mud_zqv --params-file /tmp/launch_params_0uvxclok --params-file /tmp/launch_params_n_1_ygsq --params-file /tmp/launch_params_oyi3qjz0 --params-file /tmp/launch_params_oj85aiqr --params-file /tmp/launch_params_2wgtqgj_ --params-file /tmp/launch_params_sndybptp --params-file /tmp/launch_params_z6dwyxny --params-file /tmp/launch_params_p_db5xje --params-file /tmp/launch_params_b2skfg4t --params-file /tmp/launch_params_gdejt6wl --params-file /tmp/launch_params_6j65k5vz --params-file /tmp/launch_params_u3vunadu --params-file /tmp/launch_params_zcyw14xf --params-file /tmp/launch_params_i77ptpgq --params-file /tmp/launch_params_zz8ro5i4 --params-file /tmp/launch_params_rs3huvud --params-file /tmp/launch_params_2fni1w3y --params-file /tmp/launch_params_9nf7r3s1'].
[ERROR] [full_control-15]: process has died [pid 21656, exit code -11, cmd '/home/rmf_demos_ws/install/rmf_fleet_adapter/lib/rmf_fleet_adapter/full_control --ros-args -r __node:=tinyRobot_fleet_adapter --params-file /tmp/launch_params_ryg_3m77 --params-file /tmp/launch_params_7mcf94k_ --params-file /tmp/launch_params_i_v4xw9c --params-file /tmp/launch_params_tp59exre --params-file /tmp/launch_params_ly4alid6 --params-file /tmp/launch_params_fk651h4w --params-file /tmp/launch_params_n2d1o9na --params-file /tmp/launch_params_pna8ioh4 --params-file /tmp/launch_params_imie_g5z --params-file /tmp/launch_params_8407eodh --params-file /tmp/launch_params_p1a58gje --params-file /tmp/launch_params_wa2rk5qi --params-file /tmp/launch_params_fnm1goyz --params-file /tmp/launch_params_nstcdjuz --params-file /tmp/launch_params_oefq2_kw --params-file /tmp/launch_params_z_xifcbb --params-file /tmp/launch_params___9hca8u --params-file /tmp/launch_params__c6g30lt --params-file /tmp/launch_params_kd8rb9en --params-file /tmp/launch_params_ad1qrcyh --params-file /tmp/launch_params__0xzwrxr --params-file /tmp/launch_params_3w33cchz --params-file /tmp/launch_params_2_vxas1m --params-file /tmp/launch_params_of9vzngw --params-file /tmp/launch_params_ckug_orm --params-file /tmp/launch_params_4ak9si7y --params-file /tmp/launch_params_piwvg7b7 --params-file /tmp/launch_params_dw9tfshp'].

Without knowing what you're trying to launch or how you're trying to launch it, we can't really guess at what might be wrong.
Please provide the following details:

What system you're running on (e.g. Ubuntu 20.04)
What branch of each repo you're using
What command you are passing into the terminal to perform the launch

Without knowing what you're trying to launch or how you're trying to launch it, we can't really guess at what might be wrong.
Please provide the following details:

What system you're running on (e.g. Ubuntu 20.04)
What branch of each repo you're using
What command you are passing into the terminal to perform the launch

Without knowing what you're trying to launch or how you're trying to launch it, we can't really guess at what might be wrong.
Please provide the following details:
* What system you're running on (e.g. Ubuntu 20.04)

* What branch of each repo you're using

* What command you are passing into the terminal to perform the launch

System running on Ubuntu 20.04
Command used is ros2 launch demos test_building.launch.xml
I have drawn a map from traffic editor and generated both the map and navigation.

Without knowing what you're trying to launch or how you're trying to launch it, we can't really guess at what might be wrong.
Please provide the following details:
* What system you're running on (e.g. Ubuntu 20.04)

* What branch of each repo you're using

* What command you are passing into the terminal to perform the launch

System running on Ubuntu 20.04
Command used is ros2 launch demos test_building.launch.xml
I have drawn a map from traffic editor and generated both the map and navigation.

I assume test_building.launch.xml is a launch file that you wrote yourself. In that case, would you be able to share it with us? There still isn't much we can conclude without knowing what the launch file contains.

I assume test_building.launch.xml is a launch file that you wrote yourself. In that case, would you be able to share it with us? There still isn't much we can conclude without knowing what the launch file contains.

I assume test_building.launch.xml is a launch file that you wrote yourself. In that case, would you be able to share it with us? There still isn't much we can conclude without knowing what the launch file contains.

Hi there. My apologies as I am still new in this. Please find the codes below,
<?xml version='1.0' ?>

<launch>
  <arg name="use_ignition" default="0"/>
  <arg name="gazebo_version" default="11"/>

  <!-- Common launch -->
  <include file="$(find-pkg-share demos)/common.launch.xml">
    <arg name="use_sim_time" value="true"/>
    <arg name="viz_config_file" value ="$(find-pkg-share demos)/include/test_building/test_building.rviz"/>
    <arg name="config_file" value="$(find-pkg-share rmf_demo_maps)/test_building/test_building_1.building.yaml"/>
  </include>

  <!-- Simulation launch -->
  <include file="$(find-pkg-share demos)/simulation.launch.xml">
    <arg name="map_name" value="test_building" />
    <arg name="use_ignition" value="$(var use_ignition)" />
    <arg name="gazebo_version" value="$(var gazebo_version)" />
  </include>

<!-- TinyRobot fleet adapter and robot state aggregator needed for the TinyRobot slotcar_plugin -->
  <group>
    <let name="fleet_name" value="tinyRobot"/>
    <include file="$(find-pkg-share demos)/include/adapters/tinyRobot_adapter.launch.xml">
      <arg name="fleet_name" value="$(var fleet_name)"/>
      <arg name="use_sim_time" value="$(var use_sim_time)"/>
      <arg name="nav_graph_file" value="$(find-pkg-share rmf_demo_maps)/maps/test_building/nav_graphs/0.yaml" />
    </include>
    <include file="$(find-pkg-share rmf_fleet_adapter)/robot_state_aggregator.launch.xml">
      <arg name="robot_prefix" value="tinyRobot"/>
      <arg name="fleet_name" value="$(var fleet_name)"/>
      <arg name="use_sim_time" value="true"/>
    </include>
  </group>

<!-- DeliveryRobot fleet adapter and robot state aggregator needed for DeliveryRobot slotcar_plugin -->
  <group>
    <let name="fleet_name" value="deliveryRobot"/>
    <include file="$(find-pkg-share demos)/include/adapters/deliveryRobot_adapter.launch.xml">
      <arg name="fleet_name" value="$(var fleet_name)"/>
      <arg name="use_sim_time" value="$(var use_sim_time)"/>
      <arg name="nav_graph_file" value="$(find-pkg-share rmf_demo_maps)/maps/test_building/nav_graphs/1.yaml" />
    </include>
    <include file="$(find-pkg-share rmf_fleet_adapter)/robot_state_aggregator.launch.xml">
      <arg name="robot_prefix" value="deliveryRobot"/>
      <arg name="fleet_name" value="$(var fleet_name)"/>
      <arg name="use_sim_time" value="true"/>
    </include>
  </group>

</launch>

The codes are copied from the other reference file (hotel.launch.xml)
I have named both robots according to the screenshots shown below,

I assume test_building.launch.xml is a launch file that you wrote yourself. In that case, would you be able to share it with us? There still isn't much we can conclude without knowing what the launch file contains.

Hi there. My apologies as I am still new in this. Please find the codes below,
<?xml version='1.0' ?>

<launch>
  <arg name="use_ignition" default="0"/>
  <arg name="gazebo_version" default="11"/>

  <!-- Common launch -->
  <include file="$(find-pkg-share demos)/common.launch.xml">
    <arg name="use_sim_time" value="true"/>
    <arg name="viz_config_file" value ="$(find-pkg-share demos)/include/test_building/test_building.rviz"/>
    <arg name="config_file" value="$(find-pkg-share rmf_demo_maps)/test_building/test_building_1.building.yaml"/>
  </include>

  <!-- Simulation launch -->
  <include file="$(find-pkg-share demos)/simulation.launch.xml">
    <arg name="map_name" value="test_building" />
    <arg name="use_ignition" value="$(var use_ignition)" />
    <arg name="gazebo_version" value="$(var gazebo_version)" />
  </include>

<!-- TinyRobot fleet adapter and robot state aggregator needed for the TinyRobot slotcar_plugin -->
  <group>
    <let name="fleet_name" value="tinyRobot"/>
    <include file="$(find-pkg-share demos)/include/adapters/tinyRobot_adapter.launch.xml">
      <arg name="fleet_name" value="$(var fleet_name)"/>
      <arg name="use_sim_time" value="$(var use_sim_time)"/>
      <arg name="nav_graph_file" value="$(find-pkg-share rmf_demo_maps)/maps/test_building/nav_graphs/0.yaml" />
    </include>
    <include file="$(find-pkg-share rmf_fleet_adapter)/robot_state_aggregator.launch.xml">
      <arg name="robot_prefix" value="tinyRobot"/>
      <arg name="fleet_name" value="$(var fleet_name)"/>
      <arg name="use_sim_time" value="true"/>
    </include>
  </group>

<!-- DeliveryRobot fleet adapter and robot state aggregator needed for DeliveryRobot slotcar_plugin -->
  <group>
    <let name="fleet_name" value="deliveryRobot"/>
    <include file="$(find-pkg-share demos)/include/adapters/deliveryRobot_adapter.launch.xml">
      <arg name="fleet_name" value="$(var fleet_name)"/>
      <arg name="use_sim_time" value="$(var use_sim_time)"/>
      <arg name="nav_graph_file" value="$(find-pkg-share rmf_demo_maps)/maps/test_building/nav_graphs/1.yaml" />
    </include>
    <include file="$(find-pkg-share rmf_fleet_adapter)/robot_state_aggregator.launch.xml">
      <arg name="robot_prefix" value="deliveryRobot"/>
      <arg name="fleet_name" value="$(var fleet_name)"/>
      <arg name="use_sim_time" value="true"/>
    </include>
  </group>

</launch>

The codes are copied from the other reference file (hotel.launch.xml)
I have named both robots according to the screenshots shown below,

I'm running into the same issue, code 11 means an invalid memory reference I'm assuming somewhere in full_control. I'm able to run the default office scenario, but as soon as I plug in custom files from traffic editor, this node crashes. Unlike the OP I'm using real robots (which aren't showing up in RViz although the map and traffic lanes are)
@mxgrey adding in some relevant info to add on to this issue:

sample message on /fleet_states (I'm not sure how to change the level_name in free_fleet so I changed everything to be the default...)

name: fetch
robots:
- name: fetch26
  model: robot_model
  task_id: ''
  seq: 0
  mode:
    mode: 0
    mode_request_id: 0
  battery_percent: 100.0
  location:
    t:
      sec: 1616633676
      nanosec: 857054821
    x: -0.09609447419643402
    y: -8.53885269165039
    yaw: -1.4772193431854248
    level_name: level_name
    index: 0
  path: []

My core + adapter launch file
My fleet adapter launch file
map directory

I'm assuming what's happening is that some field is empty or incorrect somewhere causing the full_control node to crash. Either way the error is quite cryptic and probably should be caught. Any pointers appreciated!

There is a PR here which addresses a known memory issue that could be triggered close to startup when trying to run a scenario that doesn't meet the fleet adapter's expectations. I suggest giving that a try.
I'll see if I can reproduce the issue on my end using the files that you've provided. Hopefully I'll have time to do that before the end of tomorrow.
As a meta remark, we're migrating over to the https://github/open-rmf organization, and the meta repo's discussion board is replacing this one.

Can confirm that's the issue. I know get the error message described in that PR now. Not sure which scenario is causing it though.
I think this can be closed.

Closed by open-rmf/rmf_ros2#13

authors: Achllle destkk mxgrey


text:
Disable crowd sim without failing

Previously, if MENGE_RESOURCE_PATH is not provided, the crowd_sim plugin will fail, resulted in failing to launch a demo world. Instead of failing, the minor change here is to disable crowd_sim if MENGE_RESOURCE_PATH is not provided.
With this, a subsequent pr will consist of an optional use_crowdsim arg (e.g.  XX.launch.xml use_crowdsim:=1 ) in the demo world launch files.

Can we also shortcut and early the Update functions if crowdsim is disabled? I don't see any check for it so I'm not sure what they would do


text:
integrate the updated arducopter code path with new failsafe logic

There's a branch being developed of arducopter with enhanced failsafe logic to match the zephyr logic.
It's still currently pending in a branch.

we're on top of the copter integration code now

repo: osrf/uctf


text:
how to find out that a peer has sent all the routes

in bgperf, it uses the count of how many prefixes received from a peer to know that a test has finished. When adding filter testing, just knowing the number of prefixes accepted isn't enough. It needs to know either the number of prefixes received before filters or the number of prefixes filtered, or that End-of-RIB has been sent. Is there anyway to get any of those things? with BIRD you can see the number of prefixes received and the number accepted. With FRRouting and OpenBGPD you can see when EOR has been sent.

The latest master sends eor messages.
Also you need the number of prefixes and accepted via the API, right?

Now the number of accepted routes are properly reported.

authors: fujita jopietsch

repo: osrg/rustybgp


text:
Add New Tools (Adno, Universal Viewer) and Update About Page Content

We need to enhance our toolset by adding two new tools and update the content on the About page.
Tasks:

Add New Tools:
Add two new tools, Adno and Universal Viewer, into the existing set of tools.
Reference information for the tools can be found in official websites:
Adno
Universal Viewer

Update About Page:
Add information about RERUM playground (what it does, why it is needed), JSON vs JSON LD and Manifests to the About section of the website.
Use the JSON vs. JSON-LD README for information of them.
For information about JSON Manifests (reference on what a manifest might look like), visit: IIIF Cookbook.

https://github.com/IIIF/awesome-iiif is a great list to research for other low-hanging fruit. Viewers and annotation tools are the things to look at.

authors: cubap jacksayshi

repo: oss-slu/rerum-playground


text:
Update OWASP item

Not sure if this can be merged w/o updating the Crunchbase page.
References:

https://en.wikipedia.org/wiki/OWASP
https://en.wikipedia.org/wiki/OWASP#cite_note-namechangetweet-7

Pre-submission checklist:
Please check each of these after submitting your pull request:

[ ] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[ ] Is your project closed source or, if it is open source, does your project have at least 250 GitHub stars?
[ ] Have you picked the single best (existing) category for your project?
[ ] Does it follow the other guidelines from the new entries section?
[ ] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[ ] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[ ] Does your project/product name match the text on the logo?
[ ] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~10 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

@arkid15r thank you for the update. However the landscape get autogenerated from LFX Organization Dashboard.
The Open Source Technology Improvement Fund administrators (Amir & Derek) can make changes to the org dashboard, linked below, and the change will pull through on the next automatic run.
https://myorg.lfx.dev/open-source-technology-improvement-fund-inc/users/access

repo: ossf/ossf-landscape


text:
Delivery DASH-support Hevc

描述(Description)

描述你遇到了什么问题(Please description your issue here)
reference v4.x support hevc(h.265) RTMP streaming #1721
hls is ok. but delivery dash can not work.（play with vlc Display black screen and the audio played ok）

SRS版本(Version): feature/h265
SRS的日志如下(Log):
log no error infos
SRS的配置如下(Config):
listen              1935;
max_connections     1000;
daemon              off;
srs_log_tank        console;
http_server {
enabled         on;
listen          8080;
dir             ./objs/nginx/html;
}
vhost defaultVhost {
http_remux {
enabled     on;
mount       [app]/[stream].flv;
}
hls {
enabled         on;
hls_vcodec      h265;
hls_path        ./objs/nginx/html;
hls_fragment    10;
hls_window      60;
}
dash {
enabled         on;
dash_fragment       30;
dash_update_period  150;
dash_timeshift      300;
dash_path           ./objs/nginx/html;
dash_mpd_file       [app]/[stream].mpd;
}
}
2.ffmpeg推流脚本如下：

#!/bin/sh
for((;;)); do
/workspace/hevc_ffmpeg/FFmpeg/ffmpeg -re -i ./localvideos/withaudioH265.mp4 -vcodec copy -acodec copy -f flv -y rtmp://10.72.55.67/live/livestream;
sleep 1;
done
testvideo:
链接：https://pan.baidu.com/s/1M-anNGOHN3HGfNk3_MGwEA
提取码：9b96
3.vlc 错误日志
mp4 info: Fragment sequence discontinuity detected 53638234 != 0
mp4 error: missing avcC
mp4 info: Fragment sequence discontinuity detected 53638234 != 0
main error: buffer deadlock prevented
4.dah.js(http://reference.dashif.org/dash.js/nightly/samples/dash-if-reference-player/index.html)错误:
MEDIA_ERR_SRC_NOT_SUPPORTED (CHUNK_DEMUXER_ERROR_APPEND_FAILED: Append: stream parsing failed. Data size=730 append_window_start=0 append_window_end=inf)
重现(Replay)
必现
期望行为(Expect)
VLC/hls.dash Play audio and video normally

i found mp4box in srs not supprt hvc1

找到另一个开源项目ZLMediaKit是支持ws+fmp4，正好复合我的需要。
正在熟悉，后期评估是否可以添加到srs。

HEVC暂时没有计划支持。

HEVC暂时没有计划支持。

Dup to #465

Dup to #465

repo: ossrs/srs


text:
采集RTSP协议视频流的时候如何强制使用tcp协议？

ffmpeg中的-rtsp_transport tcp 参数

在ffmpeg中使用下面的格式可以采集到，在SRS2.0中没找到对应的设置方法。主要是双引号如何加上，强制TCP的参数如何加上。
ffmpeg -rtsp_transport tcp -i "rtsp://admin:12345678@192.168.2.21:554/Streaming/Channels/501?transportmode=unicast" -vcodec copy -an -f flv rtmp://127.0.0.1:1935/live/mystream

RTSP还需要完善。

双引号只有命令行才有需要，实际上SRS fork进程是不用双引号的。

    ingest {
        enabled      on;
        input {
            type    stream;
            url     rtsp://admin:12345678@192.168.2.21:554/Streaming/Channels/501?transportmode=unicast;
        }
        ffmpeg      ./objs/ffmpeg/bin/ffmpeg;
        engine {
            enabled          on;
            prefile {
                rtsp_transport tcp;
            }
            vcodec copy;
            acodec copy;
            output          rtmp://127.0.0.1:[port]/live?vhost=[vhost]/livestream;
        }
    }

加了一个prefile，可以支持-i前面加rtsp_transport了。

生成的日志：
[2017-01-06 10:38:51.105][trace][9604][105] fored process, pid=9605, bin=./objs/ffmpeg/bin/ffmpeg, stdout=./objs/ffmpeg-ingest-__defaultVhost__-live-livestream.log, stderr=./objs/ffmpeg-ingest-__defaultVhost__-live-livestream.log, argv=./objs/ffmpeg/bin/ffmpeg -rtsp_transport tcp -i rtsp://admin:12345678@192.168.2.21:554/Streaming/Channels/501?transportmode=unicast -vcodec copy -acodec copy -f flv -y rtmp://127.0.0.1:1935/live?vhost=__defaultVhost__/livestream

注意是SRS3解决的。

authors: winlinvip yanest


text:
libsrtp2: fix compilation with GCC 10

Please refer the issue on the link https://github.com/openwrt/telephony/pull/546

Codecov Report

Merging #2397 (8c76fbd) into 4.0release (d526672) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           4.0release    #2397      +/-   ##
==============================================
- Coverage       38.73%   38.72%   -0.01%
==============================================
  Files             109      109
  Lines           39658    39658
==============================================
- Hits            15360    15359       -1
- Misses          24298    24299       +1

Impacted Files
Coverage Δ

trunk/src/protocol/srs_service_utility.cpp
72.43% <0.00%> (-0.55%)
: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 d526672...8c76fbd. Read the comment docs.

感谢贡献。 👍
看起来这个是srtp的代码问题，是否可以考虑也给srtp提个PR？

我不知道srtp的repo在哪..libsrtp看起來不像

Merged as https://github.com/ossrs/srs/commit/cc99226ed5e5334a49e4eb1223baa15fa43d0a87
👍 Thanks a lot @HungMingWu

authors: HungMingWu codecov-commenter winlinvip


text:
BugFix: Fix reserved bit value.

The MPEG-DASH receiver that we're using couldn't receive the stream that SRS ouputs.
The reason was that the value of the reserve bit of AVC sequence header was set to 0.
I fixed the reserved bit value to 1.

This is a great fix, and we can use both the documentation standards(ISO_IEC_14496-15-AVC-format-2012, page 16.) and FFmpeg's processing method as reference(ff_isom_write_avcc).

authors: KazuoHagihara chundonglinlin


text:
Pb fil d'ariane

https://search.google.com/search-console/r/breadcrumbs/drilldown?resource_id=sc-domain:osuny.org&item_key=ChkICRoEaXRlbSIPaXRlbUxpc3RFbGVtZW50EAMYDw&utm_source=wnc_10030322&utm_medium=gamma&utm_campaign=wnc_10030322&utm_content=msg_100058679&hl=fr

Ca va surtout dans le sens de ne pas laisser les enfants publiés dans des parents dépubliés, non ?
@pabois @SebouChu ?

@SebouChu @pabois @arnaudlevy est-ce corrigé côté admin ?

authors: alexisben arnaudlevy

repo: osunyorg/theme


text:
Integrate functions library

Use the central functions library from https://github.com/oszuidwest/bash-functions

Fixes https://github.com/oszuidwest/rpi-teksttv/issues/5

repo: oszuidwest/rpi-teksttv


text:
Jetsonnano + YOLOv5 could not work on python 3.6.9

Thanks for your useful repository!!
I met this type of error
"AssertionError: Python 3.7.0 required by YOLOv5, but Python 3.6.9 is currently installed"
How can I figure out ?
#I can read japanese.

I think your jetpack should be updated to 4.5 or higher.
Try it!

I had the similar issue. Try this: Run yolov5 on Jetson Nano

I updated to jetpack 4.5 today.
And, it didn't not work...
There was same issue
"AssertionError: Python 3.7.0 required by YOLOv5, but Python 3.6.9 is currently installed"

Ok, I'd like to confirm this weekend.

Thanks !!

recent commits at yolov5, https://github.com/ultralytics/yolov5/pull/3088, requires python3.7 or higher.
I'd like to fix this issue. thanks.

Thank you for your kindness !
Do you know which commit of yolov5 is suitable for jetpack 4.5 ?

@okome-git
before https://github.com/ultralytics/yolov5/pull/3088, I think 91547edec1a33121b3607e8c946e051514182b4f can be used, like this:
diff --git a/Dockerfile b/Dockerfile
index 3b46f20..8dfe8e4 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -19,5 +19,6 @@ RUN git clone --recursive https://github.com/skvark/opencv-python.git
 RUN python3 -m pip install --upgrade pip
 RUN cd opencv-python && python3 -m pip wheel . --verbose && find . -name "opencv_python*.whl" | xargs python3 -m pip install
 RUN git clone https://github.com/ultralytics/yolov5.git
+RUN git checkout 91547edec1a33121b3607e8c946e051514182b4f
 RUN cd yolov5 && python3 -m pip install -r requirements.txt
 WORKDIR /yolov5

It works !
Thank you!!

Hello, I have same issue "AssertionError: Python 3.7.0 required by YOLOv5, but Python 3.6.9 is currently installed". I installed jetpack 4.5.1. In my Jetson Nano, Python version default is 3.6.9 then I installed Python 3.7.5 and I point python3 to python3.7. So when I type "python3 --version", terminal show "python 3.7.5". But this problem still exists.
Can you help me?
Thank advance

Currently https://github.com/otamajakusi/dockerfile-yolov5-jetson/issues/8#issuecomment-846356393 is the only workaround for this issue.
Even if you install python3.7 on the docker environment, pytorch can not be worked.

I think you should set cd yolov5 before git checkout 91547edec1a33121b3607e8c946e051514182b4f.

@phongvu0403
It works using "git checkout 91547edec1a33121b3607e8c946e051514182b4f".
But I could not use my custom training weights, because of "_pickle.UnpicklingError" like below,
Namespace(agnostic_nms=False, augment=False, classes=None, conf_thres=0.25, device='', exist_ok=False, hide_conf=False, hide_labels=False, img_size=640, iou_thres=0.45, line_thickness=3, name='exp', nosave=False, project='runs/detect', save_conf=False, save_crop=False, save_txt=False, source='data/images', update=False, view_img=False, weights=['../yolov5_01/my_yolov5s.pt'])
YOLOv5 \U0001f680 v5.0-75-g91547ed torch 1.8.0 CUDA:0 (NVIDIA Tegra X1, 3964.1328125MB)
Traceback (most recent call last):
File "detect.py", line 181, in
detect(opt=opt)
File "detect.py", line 33, in detect
model = attempt_load(weights, map_location=device)  # load FP32 model
File "/yolov5/models/experimental.py", line 120, in attempt_load
ckpt = torch.load(w, map_location=map_location)  # load
File "/usr/local/lib/python3.6/dist-packages/torch/serialization.py", line 593, in load
return _legacy_load(opened_file, map_location, pickle_module, **pickle_load_args)
File "/usr/local/lib/python3.6/dist-packages/torch/serialization.py", line 762, in _legacy_load
magic_number = pickle_module.load(f, **pickle_load_args)
_pickle.UnpicklingError: invalid load key, '-'.

@okome-git
I modified the Dockerfile following the author's instructions. However, there is 1 error here:
Step 15/18 : RUN git clone https://github.com/ultralytics/yolov5.git
---> Running in 0fd30920640d
Cloning into 'yolov5'...
Removing intermediate container 0fd30920640d
---> e70d45f62147
Step 16/18 : RUN git checkout 91547edec1a33121b3607e8c946e051514182b4f
---> Running in 08ab50a200dc
fatal: not a git repository (or any of the parent directories): .git
The command '/bin/sh -c git checkout 91547edec1a33121b3607e8c946e051514182b4f' returned a non-zero code: 128
Can you help me fixed this problem?
Thank you!

workaround is add at c46325b7961f00ccf6624b5a61f795a92179c991
and default branch is changed to war-python36, since this is a workaround, not solution.
please fetch and change your branch to war-python36.

3c8e9465bc6b2dd170c9547be65bb316ac24803a supports python3.8 and default branch has been changed to main.
In this commit, pre-build pytorch binary is used, which was build with https://github.com/otamajakusi/dockerfile-pytorch-build-jetson repo.
thanks.

authors: okome-git otamajakusi phongvu0403 quicktwit


text:
gradio version incompatible

First of all, thank your project！
I suggest should give a requirement.txt,
when I download the face-editor in sd-webui and run, it show error : AttributeError: 'Dropdown' object has no attribute 'input',
so I clone this project and install the gradio==3.52 , the error is gone. But if i update the sd-webui's gradio(it's 3.23) to 3.52,other scripts will error.so, I hope have the requirements.txt or some others, and maybe the gradio can downgrade or other solution I don't know?Thanks your

oops, I upgrade my sdwebui to 1.4(before is 1.0),the lastest sd webui's gradio version is 3.23! It can work with sd-face-editor,!

repo: ototadana/sd-face-editor


text:
Create common language for serialization types and marks

I propose that we change the implementation to talk about type and mark serialization rather than MarkerDefinition and "custom serializer".
Perhaps we could find a common structure for these, as they all serialize/render into HTML.
Serializer
    -> TypeSerializer
         -> BlockSerializer
         -> ListSerializer
         -> ListItemSerializer
         -> ImageSerializer
         -> ....
    -> MarkerSerializer
        -> LinkSerializer
        -> StrongSerializer
        -> ....

That would match the upstream rendering pipelines somewhat more, although in a more OO-manner.

I had to do a quick refresher before starting #23, and thought it would be productive to quickly summarize my current understanding of the elements in the spec.
Types
The portable text spec indicates that there are only 2 primary types: block and span.
We have inferred a list type (because it's there), but it's not a recognized type as far as I can tell. There is also no listItem type, just a block with listItem specified (which is just one variation of block, right) - we definitely need extra serializers both of these here though.
From the upstream tests we have test 26 which uses the button type and several tests (e.g., 12) which uses the image type. As I understand it these are both custom types. This is extra confusing since the image type especially is so frequently used and is clearly built into sanity's own packages.
Mark definitions
A mark definition is something (anything?) referenced in a span's marks list. IIRC, the npm-package separates between
decorator and annotation mark definitions, which I'm not 100% clear on what the difference is, but we've mirrored the structure and now have the following lists
decorator marker definitions

em
strong
code
underline
strike-through

annotation marker definitions

link
comment

Styles
In addition to mark definitions we have styles, which define the outer tags of the block - this makes more sense if you remember that blocks are meant to represent chunks of text, and that the Portable Text spec sort of assumes that this is how you break down your content.
We do not support any custom styles at the moment.

authors: klette sondrelg

repo: otovo/python-sanity-html


text:
HW №1. Добавлены необходимые файлы для выполнения домашнего задания

Выполнено ДЗ №1

[ ] Основное ДЗ
[ ] Задание со *

В процессе сделано:

Пункт 1
Пункт 2

Как запустить проект:

Например, запустить команду X в директории Y

Как проверить работоспособность:

Например, перейти по ссылке http://localhost:8080

PR checklist:

[ ] Выставлен label с темой домашнего задания

Добрый день !Дз принято


text:
建议把普通圆角改为平滑圆角

PS：这个视频里面有讲平滑圆角
https://b23.tv/TD9kmG

（MIUI默认图标即平滑圆角）

这个背景具体绘制成什么样子，实际上模块很难控制。能够修改圆角也是桌面资源里本身提供了圆角参数。这种需求现在没时间也没能力实现，可以考虑自己做做试试。

repo: ouhoukyo/MIUIDock


text:
shell命令无法执行

按照说明文档安装启动成功。执行shell命令报错，信息如下：
INFO[2369] execute cmd start: [id: 9 cmd: ps aux | grep gocron]
INFO[2369] execute cmd end: [id: 9 cmd: ps aux | grep gocron err: ]
INFO[2817] execute cmd start: [id: 10 cmd: pwd]
INFO[2817] execute cmd end: [id: 10 cmd: pwd err: ]

错误是什么

错误是什么

刚调试了下    没报错  是没有输出执行完的output

感谢及时回复～

authors: LFasMike ouqiang

repo: ouqiang/gocron


text:
5 Column layout ?

I noticed that making a 5 column layout (full width), is impossible hard.
Bootstrap has the same issue and must be tweaked to support it.
https://stackoverflow.com/questions/10387740/five-equal-columns-in-twitter-bootstrap
One solution to this is to do like what pure-css does and implement multiple 5ths and 24ths based grids.
Maybe we could look into implementing something like this for beauter ?
Chris

Hello Chris,
Thank you for opening such an important and useful issue. Of course this is the power of open source, improving beauter together, I welcome your suggestion. Forming 5 and 7 columns layout would be a great pain indeed.
I saw how bootstrap and purecss have implemented their solution. Is having a custom grid generator plugin (just as purecss also provide) a nice idea, considering beauter as a CSS only framework? Coz this would add a lot of flexibility to the designer. (At the cost of JavaScript)
So Chris, what's your take on this issue? It would be nice of you to help us implementing such things properly for beauter 3.0 updates :)

Well, as you said I am not sure creating a grid generator is the way to go.
Maybe simply creating 5ths-Based Units and 24ths-Based Units column grid layouts ?
They could compliment the current 12 unit base grid.
Ex:
m1-5 to m5-5    => medium col 1 to 5 of a 5 column layout
m1-24  to m24-24 => medium col 1 to 24 of a 24 column layout
Any thoughts ?
Chris

I clearly got your idea for complementing the current 12 unit based grid with 5 and 24 based. But I am thinking about the possibilities and (difficulties) we can achieve on having JavaScript working behind. Not only for grids, but in general. Although I considered Beauter to be a vanilla CSS Initially, I believe hardly any site would exist without using JavaScript now a days. Specially concerned about size, there is a lot we can save and make things more DRY.
What's your opinion on Dynamic styling using JavaScript for keeping Beauter lighter and flexible?

Although beauter is pure css by source, it uses javascript for many of its elements like responsive navigations, alerts, modals etc. And creating them with pure CSS is a pain in neck with compatibility issues. Hence for full utilization of beauter, user always has to use javascript along side beauter css. Having a javascript generator would not that much of trouble.

I agree with @vyasnavneet adding some sort of basic JavaScript to implement standard features would be nice.
As for the dynamic grid system not too sure, we could maybe use css variables.
I found this medium article with a working prototype.
https://medium.com/@fionnachan/dynamic-number-of-rows-and-columns-with-css-grid-layout-and-css-variables-cb8e8381b6f2
But support for variables is not 100%
http://caniuse.com/#feat=css-variables
Maybe we can inspire ourselves with it an implement a js version if it is more flexible I am not sure.
Any thoughts ?
Chris

I found @chrisribe suggestion the best yet. We shall add new classes for new sizes. 5 columns or 7 or 24 etc.

JavaScript will add a render delay due to dynamic styling and this will not be convenient for many browsers.
CSS variables are still facing compatibility issues.
Using hacks like offsets etc (commonly used with bootstrap grid) is a bit complex, I don't consider it EASY for a beginner, considering beauter a simple framework.

Any thoughts ?

authors: chrisribe ramdeoshubham vyasnavneet

repo: outboxcraft/beauter


text:
新增直播相关接口

rt :-)

editXXXXX麻烦都改为 updateXXXX

authors: Abbotton overtrue

repo: overtrue/wechat


text:
SecStatusEngine should be "Off" in modsecurity.conf-recommended

Describe the bug
v2 states that
# NB: As of April 2022, there is no longer any advantage to turning this
# setting On, as there is no active receiver for the information.

and has the setting turned off for in https://github.com/owasp-modsecurity/ModSecurity/blob/705002be2ba23b01bd9c895a8d01ebd9fd141ceb/modsecurity.conf-recommended#L239
But v3 has it enabled in https://github.com/owasp-modsecurity/ModSecurity/blob/4e4f3291ad2f65df7b945d3fdc4ef67d6fcc631d/modsecurity.conf-recommended#L284.
Expected behavior
Both should be in sync, and turned off.

Thanks for pointing this out.

repo: owasp-modsecurity/ModSecurity


text:
bundle install vs rails6 fails vs camaleon-cms 2.4.6

ruby 2.6.3 or 2.6.4 vs rails6 (bundle install | bundle update) fails
Fetching gem metadata from https://rubygems.org/.........
Fetching gem metadata from https://rubygems.org/.
Resolving dependencies....
Bundler could not find compatible versions for gem "railties":
  In Gemfile:
    rails (~> 6.0.0) was resolved to 6.0.0, which depends on
      railties (= 6.0.0)

    sass-rails (~> 5) was resolved to 5.0.4, which depends on
      railties (>= 4.0.0, < 5.0)

    web-console (>= 3.3.0) was resolved to 4.0.1, which depends on
      railties (>= 6.0.0)

    webpacker (~> 4.0) was resolved to 4.0.7, which depends on
      railties (>= 4.2)

Bundler could not find compatible versions for gem "sass-rails":
  In Gemfile:
    sass-rails (~> 5)

    camaleon_cms (>= 2.4.6) was resolved to 2.4.6.6, which depends on
      sass-rails (<= 5.0.7)

even if gem update
  In Gemfile:
    sass-rails (~> 6)

    camaleon_cms (>= 2.4.6) was resolved to 2.4.6.6, which depends on
      sass-rails (<= 5.0.7)

+1 for also having this issue as well

in rails5 bundle update fixed that erorr but it used bundler -v 1.17.3,
but with rails6 i used bundler 2.0.2 and pre versions, neither helped(

Fixed. Please try again with the new version: 2.4.6.7
Enjoy!

thanx it works now


text:
Lock image size is hard-coded and square

Just wanted to start by saying thanks for i3lock-next! Definitely the fastest locker I've come across so far.
I was wondering if it'd be possible to make i3lock-next a little more flexible with regards to the lock image, specifically:

lookup lock image size directly in i3lock-next-helper.c
potentially adjust the ring size argument that's passed to i3lock-color

I've done step 1 already on my fork and can submit a PR if you're agreeable. Otherwise, I'm curious as to what your thoughts are.

I appreciate your kind words! I would love to implement both features, go ahead and submit a PR.

I rewrote the i3lock-next script in Python on the kcarbon-lookup_lock_image_size branch, let me know what you think.

I'm personally happier with scripting in Python and your branch/script looks good! I'm about to get on a plane though, so I didn't have a chance to test it out. This is where my ignorance comes up (aerospace background, not software), but how much slower is the Python script versus the bash script? I'd assume not enough to become perceptible to the user?

In my expert (read: definitely NOT expert) opinion, Python should be faster than Bash. Getting the image size with Python instead of with C could be slower but in my (very unscientific) testing it didn't seem slower.

authors: kylecarbon owenthewizard


text:
Fix missing info in operations list of etl dashboard

I noticed that the information in the operations list was incomplete.
To replicate the issue:

Tick “Select only grapher...”.
Select step “data://grapher/irena/2023-12-12/renewable_power_generation_costs”.
Click on "Add selected steps to the Operations list".
Click on "Add direct dependencies". A garden step is added to the operations list.
Click on "Add direct dependencies" of the garden step. The corresponding meadow step should appear, but instead, nothing happens.

If you repeat this without ticking on "Select only grapher...", the problem is solved, and you do see meadow as well.
So to perform operations, we need the full steps_df, not just the filtered version that is displayed.
That's why, in this PR, I define steps_df (as all the original data, used in operations), and steps_df_display (as the filtered data, used for the Steps table).

@lucasrodes I'll merge now since I wanted to present the dashboard this morning, but please have a look when you have some time, and let me know if you think there is a better solution.

repo: owid/etl


text:
feature(backport): Perform a once-off bulk backport of the full dataset

Add a couple of helper functions needed for bulk backport.

Needed to merge this because etl was failing after moving open numbers to its own channel.

No worries! I think the PR title was misnamed, given that this PR adds just the helpers, but the description made sense.

No worries! I think the PR title was misnamed, given that this PR adds just the helpers, but the description made sense.

True, I tend to use identical names for PRs belonging to the same issue, but this got out of hand a bit.

authors: Marigold larsyencken

repo: owid/owid-catalog-py


text:
Add photo facet

See https://learn.microsoft.com/en-us/graph/api/resources/photo?view=graph-rest-1.0 and https://learn.microsoft.com/en-us/graph/api/resources/driveitem?view=graph-rest-1.0 :shrug:

We can probably get all these properties (and much more) from tika. See:
map[string][]string{
	"Component 1":                               []string{"Y component: Quantization table 0, Sampling factors 2 horiz/2 vert"},
	"Component 2":                               []string{"Cb component: Quantization table 1, Sampling factors 1 horiz/1 vert"},
	"Component 3":                               []string{"Cr component: Quantization table 1, Sampling factors 1 horiz/1 vert"},
	"Compression Type":                          []string{"Baseline"},
	"Content-Type":                              []string{"image/jpeg"},
	"Content-Type-Parser-Override":              []string{"image/ocr-jpeg"},
	"Data Precision":                            []string{"8 bits"},
	"Exif IFD0:Bits Per Sample":                 []string{"8 8 8 bits/component/pixel"},
	"Exif IFD0:Date/Time":                       []string{"2019:08:13 18:42:18"},
	"Exif IFD0:Device Setting Description":      []string{"105 112 112 0"},
	"Exif IFD0:Image Height":                    []string{"2736 pixels"},
	"Exif IFD0:Image Width":                     []string{"3648 pixels"},
	"Exif IFD0:Make":                            []string{"HUAWEI"},
	"Exif IFD0:Model":                           []string{"VOG-L29"},
	"Exif IFD0:Orientation":                     []string{"Unknown (0)"},
	"Exif IFD0:Resolution Unit":                 []string{"Inch"},
	"Exif IFD0:Software":                        []string{"VOG-L29 9.1.0.178(C431E4R2P2)"},
	"Exif IFD0:X Resolution":                    []string{"72 dots per inch"},
	"Exif IFD0:Y Resolution":                    []string{"72 dots per inch"},
	"Exif IFD0:YCbCr Positioning":               []string{"Center of pixel array"},
	"Exif SubIFD:Aperture Value":                []string{"f/3.4"},
	"Exif SubIFD:Brightness Value":              []string{"0.0"},
	"Exif SubIFD:Color Space":                   []string{"sRGB"},
	"Exif SubIFD:Components Configuration":      []string{"YCbCr"},
	"Exif SubIFD:Compressed Bits Per Pixel":     []string{"0.95 bits/pixel"},
	"Exif SubIFD:Contrast":                      []string{"None"},
	"Exif SubIFD:Custom Rendered":               []string{"Custom process"},
	"Exif SubIFD:Date/Time Digitized":           []string{"2019:08:13 18:42:18"},
	"Exif SubIFD:Date/Time Original":            []string{"2019:08:13 18:42:18"},
	"Exif SubIFD:Digital Zoom Ratio":            []string{"1"},
	"Exif SubIFD:Document Name":                 []string{""},
	"Exif SubIFD:Exif Image Height":             []string{"2736 pixels"},
	"Exif SubIFD:Exif Image Width":              []string{"3648 pixels"},
	"Exif SubIFD:Exif Version":                  []string{"2.10"},
	"Exif SubIFD:Exposure Bias Value":           []string{"0 EV"},
	"Exif SubIFD:Exposure Mode":                 []string{"Auto exposure"},
	"Exif SubIFD:Exposure Program":              []string{"Program normal"},
	"Exif SubIFD:Exposure Time":                 []string{"16667/1000000 sec"},
	"Exif SubIFD:F-Number":                      []string{"f/3.4"},
	"Exif SubIFD:File Source":                   []string{"Digital Still Camera (DSC)"},
	"Exif SubIFD:Flash":                         []string{"Flash did not fire"},
	"Exif SubIFD:FlashPix Version":              []string{"1.00"},
	"Exif SubIFD:Focal Length":                  []string{"14.5 mm"},
	"Exif SubIFD:Focal Length 35":               []string{"1343 mm"},
	"Exif SubIFD:Gain Control":                  []string{"None"},
	"Exif SubIFD:ISO Speed Ratings":             []string{"100"},
	"Exif SubIFD:Makernote":                     []string{"65 70 95 67 0"},
	"Exif SubIFD:Max Aperture Value":            []string{"f/3.4"},
	"Exif SubIFD:Metering Mode":                 []string{"Multi-segment"},
	"Exif SubIFD:Saturation":                    []string{"None"},
	"Exif SubIFD:Scene Capture Type":            []string{"Standard"},
	"Exif SubIFD:Scene Type":                    []string{"Directly photographed image"},
	"Exif SubIFD:Sensing Method":                []string{"One-chip color area sensor"},
	"Exif SubIFD:Sharpness":                     []string{"None"},
	"Exif SubIFD:Shutter Speed Value":           []string{"1/999963864 sec"},
	"Exif SubIFD:Sub-Sec Time":                  []string{"086108"},
	"Exif SubIFD:Sub-Sec Time Digitized":        []string{"086108"},
	"Exif SubIFD:Sub-Sec Time Original":         []string{"086108"},
	"Exif SubIFD:Subject Distance Range":        []string{"Unknown"},
	"Exif SubIFD:White Balance":                 []string{"Other"},
	"Exif SubIFD:White Balance Mode":            []string{"Auto white balance"},
	"Exif Thumbnail:Compression":                []string{"JPEG (old-style)"},
	"Exif Thumbnail:Image Height":               []string{"384 pixels"},
	"Exif Thumbnail:Image Width":                []string{"512 pixels"},
	"Exif Thumbnail:Orientation":                []string{"Unknown (0)"},
	"Exif Thumbnail:Resolution Unit":            []string{"Inch"},
	"Exif Thumbnail:Thumbnail Length":           []string{"18598 bytes"},
	"Exif Thumbnail:Thumbnail Offset":           []string{"1586 bytes"},
	"Exif Thumbnail:X Resolution":               []string{"72 dots per inch"},
	"Exif Thumbnail:Y Resolution":               []string{"72 dots per inch"},
	"File Modified Date":                        []string{"Sun Oct 15 23:17:31 +00:00 2023"},
	"File Name":                                 []string{"apache-tika-5757958221908409679.tmp"},
	"File Size":                                 []string{"971393 bytes"},
	"GPS:GPS Altitude":                          []string{"0 metres"},
	"GPS:GPS Altitude Ref":                      []string{"Below sea level"},
	"GPS:GPS Date Stamp":                        []string{"2019:08:13"},
	"GPS:GPS Latitude":                          []string{"53° 4' 28.27\""},
	"GPS:GPS Latitude Ref":                      []string{"N"},
	"GPS:GPS Longitude":                         []string{"-6° 17' 26.88\""},
	"GPS:GPS Longitude Ref":                     []string{"W"},
	"GPS:GPS Processing Method":                 []string{"GPS"},
	"GPS:GPS Time-Stamp":                        []string{"17:42:17.000 UTC"},
	"GPS:GPS Version ID":                        []string{"2.200"},
	"Image Height":                              []string{"2736 pixels"},
	"Image Width":                               []string{"3648 pixels"},
	"Interoperability:Interoperability Index":   []string{"Recommended Exif Interoperability Rules (ExifR98)"},
	"Interoperability:Interoperability Version": []string{"1.00"},
	"Number of Components":                      []string{"3"},
	"Number of Tables":                          []string{"4 Huffman tables"},
	"Resolution Units":                          []string{"inch"},
	"Thumbnail Height Pixels":                   []string{"0"},
	"Thumbnail Width Pixels":                    []string{"0"},
	"Version":                                   []string{"1.1"},
	"X Resolution":                              []string{"96 dots"},
	"X-TIKA:Parsed-By": []string{"org.apache.tika.parser.DefaultParser",
		"org.apache.tika.parser.image.JpegParser",
		"org.apache.tika.parser.ocr.TesseractOCRParser"},
	"X-TIKA:Parsed-By-Full-Set": []string{"org.apache.tika.parser.DefaultParser",
		"org.apache.tika.parser.image.JpegParser",
		"org.apache.tika.parser.ocr.TesseractOCRParser"},
	"X-TIKA:content":           []string{"\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\noa\n\n\n\n"},
	"X-TIKA:content_handler":   []string{"ToTextContentHandler"},
	"X-TIKA:embedded_depth":    []string{"0"},
	"X-TIKA:parse_time_millis": []string{"399"},
	"Y Resolution":             []string{"96 dots"},
	"dcterms:created":          []string{"2019-08-13T18:42:18"},
	"dcterms:modified":         []string{"2019-08-13T18:42:18"},
	"exif:DateTimeOriginal":    []string{"2019-08-13T18:42:18"},
	"exif:ExposureTime":        []string{"0.016667"},
	"exif:FNumber":             []string{"3.4"},
	"exif:Flash":               []string{"false"},
	"exif:FocalLength":         []string{"14.46"},
	"exif:IsoSpeedRatings":     []string{"100"},
	"geo:lat":                  []string{"..."},
	"geo:long":                 []string{"..."},
	"tiff:BitsPerSample":       []string{"8"},
	"tiff:ImageLength":         []string{"2736"},
	"tiff:ImageWidth":          []string{"3648"},
	"tiff:Make":                []string{"HUAWEI"},
	"tiff:Model":               []string{"VOG-L29"},
	"tiff:Orientation":         []string{"0"},
	"tiff:ResolutionUnit":      []string{"Inch"},
	"tiff:Software":            []string{"VOG-L29 9.1.0.178(C431E4R2P2)"},
	"tiff:XResolution":         []string{"72.0"},
	"tiff:YResolution":         []string{"72.0"}
}

yes, AFAICT graph already reduced the photo related properties to the most relevant set.

Sure, wasn't suggesting that - just saying "hey we got this and more available"

authors: butonic dschmidt

repo: owncloud/libre-graph-api


text:
Disable the demo users by default

By default, the demo users are enabled,
I would propose by default to have:
      ACCOUNTS_DEMO_USERS_AND_GROUPS: false

and only if the developers want to have a testing environment could be enabled.
Otherwise, this could produce a security issue if someone forgets it.

Thanks carlos for pointing it out.
IMO we should solve this during build time. The locally self compiled binary should still have the demo users, and  the docker image and the official binary should set the value to false

To have a secure oCIS instance, there is more than deleting the demo users. I agree on having them disabled by default for released binaries as soon as were in Beta.
But we should also find a solution for the default secrets (https://owncloud.dev/ocis/deployment/#secure-an-ocis-instance), at least for the single process use case.

authors: cdamken micbar wkloucek

repo: owncloud/ocis


text:
Copying over TABs

Is your feature request related to a problem? Please describe.
I am in Chrome (Version 128.0.6613.120 (Offizieller Build) (64-Bit) - should be the latest version) and I want to copy a folder in oCIS and want to paste the folder in another TAB. But I do not get the option to paste it there.
A refresh of the second TAB also does not work.
Describe the solution you'd like
I would like to be able to copy the folder/file in one TAB and be able to insert it in another TAB. That way I can have both locations opened and I do not have to find my way to the second location.
Describe alternatives you've considered
I have no idea for a different alternative in web.
Additional context
I tried this on infinite on 05.09.2024 at 12:35 o'clock.

WHO is the requester of that FR?

authors: LisaHue micbar


text:
[tests-only][full-ci]Extended public link tests to have more checks

Description

Related Issue

Part of: https://github.com/owncloud/ocis/issues/4937

Motivation and Context

How Has This Been Tested?

locally
CI

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)
[ ] Technical debt
[x] Tests only (no source changes)

Checklist:

[ ] Code changes
[ ] Unit tests added
[x] Acceptance tests added
[ ] Documentation ticket raised:

Ported to master in PR #5335

authors: SwikritiT phil-davis


text:
add import/import-no-namespace

because there is typescript/no-namespace the import plugin needed another unique name.
We should remap them to the eslint-rule-name or wait for https://github.com/oxc-project/oxc/discussions/7242

it is fixed in the next version

repo: oxc-project/eslint-plugin-oxlint


text:
chore: release v2.0.0

🤖 New release

oxc_resolver: 1.11.0 -> 2.0.0

Changelog

2.0.0 - 2024-09-06
Added

give a specific error for matched alias not found (#238)

Fixed

fix .github/workflows/release-plz.yml

Other

set GH_TOKEN for "Bump package.json" in release-plz.yml
update package.json in release-plz.yml (#242)
apply semver_check to release-plz (#241)
(deps) update dependency rust to v1.81.0 (#239)
(deps) update crate-ci/typos action to v1.24.5
(deps) update crate-ci/typos action to v1.24.4
(deps) update crate-ci/typos action to v1.24.3
add esm / cjs condition_names to examples

This PR was generated with release-plz.

Should I add a non_exhaustive?
--- failure enum_variant_added: enum variant added on exhaustive enum ---

Description:
A publicly-visible enum without #[non_exhaustive] has a new variant.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#enum-variant-new
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.35.0/src/lints/enum_variant_added.ron

Failed in:
  variant ResolveError:MatchedAliasNotFound in /home/runner/work/oxc-resolver/oxc-resolver/src/error.rs:29
    Summary semver requires new major version: 1 major and 0 minor checks failed

I have to admit that the changelog doesn't say anything about what are the breaking changes, or if there are any, since we're shipping a major.
Any chance we can write something about it?

I have to admit that the changelog doesn't say anything about what are the breaking changes, or if there are any, since we're shipping a major.
Any chance we can write something about it?

Yes absolutely, I'm in the process of learning and applying cargo-semver-checks to this repo so I can use it in oxc in a few months.

authors: Boshen ematipico

repo: oxc-project/oxc-resolver


text:
refactor(syntax): ASCII tables static not const

A small nit: ASCII_CONTINUE is used in multiple places, so it's preferable that it's a static not a const so it only gets included in the binary once, rather than once for each usage.
Only makes a tiny difference on benchmarks (~0.1 ms), but change seems worthwhile anyway just to be more "good practice".

re graphite: did you setup the access token?

Argh! Maybe I didn't grant the right permissions on the access token. I'm not familiar with this stuff. I'll have to come back to this...

authors: Boshen overlookmotel

repo: oxc-project/oxc


text:
Question: Will Clarabel support box cone?

Hello there,
I am starting to benchmark Clarabel, and would like to know if support for box cone (to manage box constraints on variables more "natively" than with the positive cone) is something planned?
(Like SCS -> https://www.cvxgrp.org/scs/api/cones.html)
Cheers,
Roman

We do not directly support interval (i.e. box) constraints.   The reason is that the "box cone" isn't really a cone, and it's generally harder to deal with that constraint directly in an interior point solver than it is in a projection-based first order solver like SCS or OSQP.
I don't think it would make much difference to solve times anyway, since modelling such a constraint as a pair of one-sided bounds can be made about as a sparse as a single box constraint anyway.   Specifically, if you have a constraint like $\ell \le Ax \le u$ with some non-trivial $A$ matrix, then it would be better to remodel it as the set of constrants :
$$
\begin{aligned}
z &= Ax \
z &\le u \
-z &\le -\ell \
\end{aligned}
$$
rather than as :
$$
\begin{aligned}
Ax &\le u \
-Ax &\le -\ell \
\end{aligned}
$$
The reason being that in the second form you would have $A$ (possibly with many nonzeroes) appearing twice in the eventual linear system that is solved at every interior point iteration, whereas in the first case you would $A$ and then two additional block rows that only have a single entry each.   Given that we use a sparse linear solve internally those extra rows are unlikely to change the solve time by much.

The reason is that the "box cone" isn't really a cone

Why isn't the box cone really a cone? I think it is a cone, but I agree that IPMs won't be able to use it effectively though.

Wait, this is specifically about the box cone, if you see in the link to the SCS docs shared above the definition of the box cone is:

it's not just the box, it's the perspective of the indicator of the box. The box cone combined with the constraint that $t=1$ yields the standard box. Having a cone is useful for use in the homogeneous embedding solvers and fast infeasibility certification. However, I'm not sure how an IPM could use the box cone without losing the main benefit that the projection solvers enjoy, which is moving badly conditioned data into the projection step, but it might be possible.

Makes sense, although now that I think about it perhaps IPMs would be able to make use of the box cone. So maybe something to think about.

authors: bodono goulart-paul lequant40


text:
Inaccurate type declaration of Store#load

In node.d.ts I find
/**
* @param {string} data
* @param {any} options
* @param {any} base_iri
* @param {any} to_graph_name
*/
load(data: string, options: any, base_iri: any, to_graph_name: any): void;

However, the readme shows a different interface (my rendition of options, assuming Format is a union type of allowed values but could be a simple string)
load(data: string, options: {
  format: Format,
  base_iri?: string | NamedNode
  to_named_graph?: NamedNode | BlankNode | DefaultGraph
  unchecked?: boolean
  no_transaction?: boolean
})

Hey! The documentation exposes the new function arguments with a single data field and the options dictionnary whereas the code and auto generated type script definition is is still compatible with the old argument lists (data, type, base_iri, to_graph_name). I plan to drop the old argument list in a future release but kept them for now to ease transition

Would it be possible actually express that accurately, without using any and with possible function overloads? Are types generated?

They were auto generated in the latest apha release but #922 migrates to explicit types that removes all these any

Released as part of 0.4.0-alpha.8

authors: Tpt tpluscode

repo: oxigraph/oxigraph


text:
Fix rotations on bottom side, fix last item in BOM

I observed that the rotation of components on the bottom side is mirrored, i do not know whether this is a problem with JLC or with Eagle, but i fixed it in this ULP.
I also fixed a bug where the last item of the BOM was missing.
During my work the tabs were accidentally replaced with spaces, i can revert that if it bothers you.

Hey @jhbruhn thank you very much! I actually tested only the process with top components.
For the sake of tracking the changes, it'd be indeed nice to avoid a merge with tabs replacements. Since I wanted to kill the tabs since a while, what do you think if I fix them on master and you send me a new pull request with two commits, one per fix?
Thanks in advance!

Sounds good!

authors: jhbruhn oxullo

repo: oxullo/jlcpcb-eagle


text:
feat(s3-proxy): Add support for Pod Security Context settings

Provides the ability to use AWS IAM Roles for Service Accounts (IRSA) tokens

Hello, Thanks for that PR. CI is red but not because of your changes. I'm merging this. Release will be deployed soon.

authors: legopost oxyno-zeta


text:
Parser does not recognize @plugin

Hi I am using https://github.com/seanCodes/bootstrap-less-port
It gives me this error
Fatal error:  Uncaught Less_Exception_Chunk: ParseError: Unexpected input in _functions.less on line 5, column 1
| 3| // Utility mixins and functions for evalutating source code across our variables, maps, and mixins.
  | 4|
  | 5| @plugin "plugins/index";
  | 6| @plugin "plugins/map-get";

same issue

You have in About:

About
The code structure of less.php mirrors that of the official processor which helps us ensure compatibility and allows for easy maintenance.

Please note, there are a few unsupported LESS features:

Evaluation of JavaScript expressions within back-ticks (for obvious reasons).
Definition of custom functions.

So I guess, it can't be used.

authors: MikeYV bkrsmanovic hprasetyou


text:
Wrong post dates

Nevermind, I just realised the dates are manually specified.

I just added that for testing purposes. I will edit the post.

authors: WilliamDavidHarrison oyepriyansh

repo: oyepriyansh/DevTweet


text:
Exponential notation (e.g., 1e+140) is not parsed as a BigInt but as a double

Hi,
While trying to use json_bigint for learning about writing Flutter and dart apps I discovered the package doesn't recognize exponential notation for integers.
Using the example code as illustration,
String json =
    '{"sometext": "hello world!", "bignumber": 100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000}';

correctly parses bignumber as a BigInt, but
String json = '{"sometext": "hello world!", "bignumber": 1e+140}';
incorrectly parses bignumber as a double (just as convert does).
In my current use case I am pulling the number from an external website so have no direct control over when it decides to hand me an integer in integer notation or in exponential notation.
(Also, as a side note, the example code is missing the '}' closing character on the json declaration such that running the example code results in a runtime parsing error.)

So I'm thinking the issue is caused by Dart itself.
At a low level Dart appears to convert numbers like 1e+140 to doubles, automatically, with no apparent option to keep it from doing so. Worse, even trying to sidestep the problem by using BigInt.parse('1e+140') results in a FormatException as, apparently, BigInt, itself, doesn't handle exponential notation, at all.
I was originally fooled by the documentation on this because I saw that BigInt.parse('7.5', radix: 16) worked fine until I realized it worked fine because e is a hex value not an exponential indicator.
Not sure why BigInt was designed in such a strangely broken way but at least I understand what it is doing now. I'm too new to Dart to know how this is supposed to be handled but I can only assume most, if not all, pathways will end up with big exponential notation values getting converted to a double which, basically, just sort of breaks everything.
Hopefully there is an answer out there but the only answer, at the moment, that I can see here is if we altered the parsing code to convert things like 1e+140 to a canonical string, first, and then parsing that with BigInt.parse() from there. The bigger problem would be going the other way as I'm thinking there are probably many edge cases that would get in the way such that encodeJson(decodeJson('1e+140')) may not be 1e+140.

I think you're right about converting it to a canonical form. I'm gonna try doing that.
As for the errors in the example code, I've fixed that, thanks for point it out.

I played with it a little a couple days ago as a Dart learning exercise. The numberPrimitive petitparser matcher already captures the form correctly so I thought about separating it into an integer and exponential notation form (which might be a decent answer) and handling it there but instead started modifying the _numOrBigInt method.
Immediately ran into the first "interesting" design problems:
1 to what extent should a BigInt raised to the BigInt be supported?
2 should an arbitrary chaining of exponents be supported? (.i.e, X1^Y2...^Xn)?
3 should there be an upper limit to an allowed value?
4 would it just be easier to have an option to decode exponential notation numbers (or any numbers, actually) into strings instead of turning them into number?
The third one struck me as important lest some malicious, or prankster, number source present a googolplex raised to the googolplex (10^10^100)^(10^10^100) raised to the ... you get the idea. Since "arbitrary" would let someone do such things, especially if chaining was supported, it would a lame if there was no way to control or limit that behavior.
While pondering how one might handle such issues it occurred to me that the allowing BigInt values to just not be turned into numbers might also be an answer. The tutorial I was going through only used the values for presenting (which would work fine), not calculating, and, more importantly, the website that the code interacts with uses the numbers for returning random trivia about the number which led to this additional, possible, feature for the encodeJson encoder:
5 allow strings formatted as numbers to be encoded as numbers instead of strings.
This last part would help support the canonical and reversible portions of the parser.
I started down this path, wrote some tests, updated the example code (to also include using the EncoderSettings variable which the original defined but never used), and then went "but what does ozaner want to do? Maybe the vision is entirely different than anything I just laid out."
So I sort of just stopped until maybe I heard back or just became super interested in seeing some of these changes I was pondering actually work. I did fork it off to safely play with it so if there was anything you found interesting (really only the example code is current in the forked repo) then feel free to grab it or let me know and maybe I could learn how to submit patches on github and send it your way all official like and stuff).
Thanks for making and posting the code. It has been fun to play with and learn from. And it also introduced me to petitparser which, it just so happens, is exactly the library I was needing for another little project piece of Dart code I'm playing around with right now. So json_bigint has been a big hit for me!

Ok I released an updated version of the package as v2.0.0, that adds support for this. You can see the documentation on pub.dev, but what's relevant to this discussion is that it adds DecoderSettings.
By default, the decoder still treats any number written in exponential notation (e.g. 1.212e+3, 2e4, 3e-4, etc.) as doubles. However, when  treatExpAsIntWhenPossible (one of the new decoder settings) is set to true, it tries to parse these exponential numbers and determine if they would evaluate to integers. If so, it converts them to integers instead of doubles.
For example:

1e6 = 1000000 is an int so it becomes a BigInt.
-23000e-3 = -23 is an int so it becomes a BigInt.
2.312e2 = 231.2 is not an int so it becomes a double.
43e-2 = .42 is not an int so it becomes a double.

You can look at the source code if your interested, but basically I just made a custom regex expression that runs on the string should it fail to parse as a BigInt. Then I do some calculations to make sure it evaluates to an integer with no decimal part, and return it as a BigInt if so.
As for representing large numbers as Strings, this is possible and is the most common way of getting around the problem of decoding BigIntegers from JSON in a lot of languages. You can just encode integers as strings and convert them back to integers yourself.
For my use case though, I didn't want to have my output JSON include quotations around the numbers. This meant I needed to be able to truly serialize BigInts rather than just their string counterparts. This is ultimately is why I made this library.
Anyway thanks for using and experimenting with the library, I hope this update allows you to decode exponentials as BigInts. Assuming I didn't break anything. If it doesn't work as intended, you can just reopen the issue.

authors: ozaner thumdugger


text:
Unable to connect to CCU3

Describe Your Problem:

I setup the config and hombridge restarts and in the logs spit out the following:
Logs:

Homebridge Config:

Environment:

Hi @khwerhahn,
It looks like you're not running Homebridge, and this project is for the Homebridge UI.
If you'd like to swap to Homebridge, you can backup your HOOBS instance and restore it into Homebridge:
https://github.com/homebridge/homebridge-raspbian-image/wiki/How-To-Migrate-From-HOOBS-To-Homebridge
Otherwise, you will need to contact HOOBS support directly for any assistance.

authors: khwerhahn oznu

repo: oznu/homebridge-config-ui-x


text:
[BUG] Visual glitch with Tidy5e Sheet

Module Version:

Tidy5e Sheet: Version 0.8.16.
Character Actions List dnd5e: Version 6.0.2.

Describe the bug
Visual dealignment between range, hit/dc and damage fields and its list elements in the action menu inside the character sheet if using Tidy5e Sheet. Also the headers of the lists are a bit too broad and I don't know if that's the intention.
To Reproduce
Steps to reproduce the behavior:

Open the character sheet.
Go to the action section of the sheet.

Expected behavior
To have the range, hit/dc and damage fields align with its list elements.
Screenshots

Browser:
Desktop app.
Foundry Version:
Version 10, Build 291.
Game System:
DnD 5e. Version: 2.1.4.
Additional context
None at the moment.

I can corroborate that this issue also occurs ever since update .8.14 on Tidysheet. I've also noticed that I can no longer add spells onto the action's list as right clicking does not show an option to add it as seen below.

authors: OxTailSafu RaylaTheBrave


text:
Proposed additions to P4_16 spec: restrictions on use of stateful obj…

…ects

Created a PR at the suggestion of @mbudiu-vmw to make it easier for others to comment on particular lines, as compared to all of the text in a single comment on this issue: https://github.com/p4lang/p4-spec/issues/375
I have made changes due to some comments from @jnfoster to make it more explicit that parser loops are allowed, and we expect architectures to define mechanism for recirculating/cloning packets, but while a control or parser is executing, there can be no recursion "beneath" that on the stack.

Are we classifying this is a minor change that can be merged without a discussion on p4-design? It's certainly more than a typo correction.

authors: jafingerhut jnfoster


text:
Clarification on VERIFY_AND_SAVE & COMMIT

Clarification on VERIFY_AND_SAVE & COMMIT action for SetForwardingPipelineConfig()
Right now, it looks like these 2 have to go together, meaning COMMIT always refers to the previous VERIFY_AND_SAVE P4info. We are trying to come up with a solution to have the server apply the last previously applied and saved p4info (via VERIFY_AND_SAVE or VERIFY_AND_COMMIT or RECONCILE_AND_COMMIT) when a COMMIT action is specified and want to understand the motive behind the tight coupling to VERIFY_AND_SAVE.

Want to understand the reasoning behind the text in VERIFY_AND_SAVE - “any subsequent Read / Write requests must refer to fields in the new config.” Why does the subsequent write requests have to refer to a field which has not been applied yet ?

@smolkaj for vis.

So, for the second question, it think it's because o.w. this line from COMMIT definitely won't work: "The forwarding state in the target is updated by replaying the write requests to the target device since the last config was saved."
However, I think it's not completely clear what it would mean for the forwarding state to be updated here. It seems like it must be cleared first, then updated by replaying, because o.w. how do we know that the forwarding state is compatible with our p4info?

authors: jonathan-dilorenzo kishanps


text:
Correct imports to be compatible with Py3

Correct imports to be compatible with Py3.
This Pull Request trying to fix:
ImportError: attempted relative import with no known parent package

when using relative import with Python3, ex from . import packet

@antoninbas @Yi-Tseng I add an isort to the pipeline. An automatic code refactoring was also introduced, some of the imports are not necessary for the code, but maybe some users import, unnecessary imports.

Moving to draft I need to do some more tests...


text:
complete migration from Wordpress

the current blog is self-hosted with WordPress.
I want to migrate it to Gatsby+Makrdown. So that blog can be written using markdown.
I don't want to continue using WordPress but I need old blogs too.
It seems, this codebase, connect to wordpress and try to get all the data and then create pages. so, I think, It doesn't satisfy my purpose. Kindly help me to understand!

Hi,
This is a starter to keep using WordPress. The starter helps you to bring your current posts in WordPress to GraphQL and Gatsby. But the source of information will be WordPress yet.
If you want to use Markdown there are other starters to help you. I have never done it so, I think you should start copying your posts into Markdown files, but maybe I'm wrong.

this plugin       : WordPress --> GraphQL --> Gatsby
desired flow:  WordPress --> Markdown                   (plugin 1) - download
Markdown --> GraphQL --> Gatsby  (plugin 2)

Although it's a good approach to follow that flow, it was the first intention of this starter

authors: nsisodiya pablovila


text:
Downsample flag in pipelines

Add a downsample flag in pipelines for when user wants to experiment. Instead of running processing all the data whenever they update a pipeline, they can set a downsample factor. Saves cluster resources and improves the update pipeline <--> view results iteration cycle.

This may be obvious and our current sharding implementation already supports this: If the downsample factor doesn't change when a pipeline is updated, the input data should remain the same, not resampled each run or update.

This can be accomplished today w glob patterns. E.g. if at my root I have a bunch of images, I can specify a glob like 11*.tif to get a consistent subset.

authors: JoeyZwicker sjezewski

repo: pachyderm/pachyderm


text:
Update GPU docs

GPU docs should be updated to include information about:

deploying on GKE
resource limits
resource requests

I have notes I will integrate for GKE and AWS, and I have already updated the pix2pix example to work with the new limits: https://github.com/pachyderm/pachyderm/pull/2561.

Our docs for this seem pretty good to me: https://docs.pachyderm.io/en/latest/cookbook/gpus.html
They don't discuss deploying on specific providers, but we decided not to do that because it changes frequently and it's better to link to relevant docs than to document a moving target ourselves. They do talk about resource limits and requests.

authors: dwhitena jdoliner


text:
Use prettier to autoformat the circleci config and helm values files

This also adds a test to ensure that the files stay formatted correctly.

Thanks for taking a look.  After CI succeeds I'll merge, and backport to the 2.1 branch.  (I'm just going to copy the CI rules and .prettierrc.yml, and re-run prettier.  Not a strictly a backport, but a similar effect.)


text:
Let gh actions releaser create & push a tag for the apis/ submodule

Summary

Change Type

Check List Before Merging

[ ] This PR passes all pre-commit hook validations.
[ ] This PR is fully tested and regression tests are included.
[ ] Relevant documentation has been updated.

Additional Information

/retest

/retest

repo: package-operator/package-operator


text:
Configurable check names

This was brought up few times by our users to avoid having long check names such as testing-farm:OL8.7-x86_64-HVM-2023-03-07:tier1. The initial idea would be to be able to assign some aliases to the targets.

[ ] design the solution on what will be configurable (e.g. only the targets)
[ ] implement the configuration option(s)

I think this is covered by status_name_template.

repo: packit/packit-service


text:
Re-enable most of the tests in 'check_in_container'

7ff83b1e disabled most of the tests run by default, by mistake.
'check_in_container' should run the unit, integration and functional
tests by default.
Signed-off-by: Hunor Csomortáni csomh@redhat.com

regate

repo: packit/packit


text:
udp(bitwig-studio-deb): 4.1.2 -> 4.2

udp(bitwig-studio-deb): 4.1.2 -> 4.2

@Zahrun do you want to connect this pacscript with repology and thus use Pacup?

@Zahrun do you want to connect this pacscript with repology and thus use Pacup?

2 days have passed so I assume that's a no then.

@Henryws i386 error.

repo: pacstall/pacstall-programs


text:
Transaction not going through/stuck

I encountered a bug today when trying to Transfer some coins. I attempted to transfer from one of my Account to another Account on another node. The transaction initially appeared to go through, but after a long wait, nothing happened. Upon trying again, I received an "insufficient funds" error.
I checked pacviewer and found no record of the transaction. My node was synced at the time. After restarting the node, I try to send again, and I was able to successfully transfer the coins this time.
My suspicion is on:

Insufficient funds(not 100% sure as i didnt check exactly the decimals): I didn't have enough funds to cover the transaction fee, but the transaction still appeared to go through. This could indicate that transactions are not properly validated when the sender has insufficient funds. But somehoe it go through but not accepted by the chain, that is why it is stucked.

Rate limitation: The default rate limit for broadcasting transactions is 5 per second. If exceeded, messages might be consumed but not delivered. This could explain why the transaction was not registered on the chain.

Windows 10 Home 64bit
GUI v1.2.0
Thank you,

@aboka2k It sounds like your query would be best dealt with by the support team.
Please see the link below to our dedicated support line:
Support :Help Center
Note: Click on the live chat icon at the bottom corner of the page to start a conversation

We have implemented a rate limitation on broadcasting transactions.
By default, it is set to 5 transactions per second.
This means that if I receive more than 5 transactions per second, I will consume the messages myself but won't deliver them to others.
Here, you probably have more than 5 transactions per second: one is yours, and the other 4 are from others, like sortition, etc. Simply say in very random occasion transaction won't commit or commit too long.
One way to fix this issue is to check if we have sent the transaction; then we don't apply the rate limit. This approach is challenging, since we have no information at that level to identify the original sender of the transaction.

We have implemented a rate limitation on broadcasting transactions. By default, it is set to 5 transactions per second. This means that if I receive more than 5 transactions per second, I will consume the messages myself but won't deliver them to others.
Here, you probably have more than 5 transactions per second: one is yours, and the other 4 are from others, like sortition, etc. Simply say in very random occasion transaction won't commit or commit too long.
One way to fix this issue is to check if we have sent the transaction; then we don't apply the rate limit. This approach is challenging, since we have no information at that level to identify the original sender of the transaction.

Ok i think frist we need to try find out the real cause for this. And if its really bcoz of what you suggest here, will it be possible to  check if the transaction is from myself or external, or maybe it will wait for awhile and check if my trsaction has gone through, if not re-send? im not sure, since im not a dev or really understand how it works under the hood. Thanks.

One simple solution for this issue is to check the sender of the message. If it comes from self-ID, we can always propagate the message even if the rate limit is exceeded.

One simple solution for this issue is to check the sender of the message. If it comes from self-ID, we can always propagate the message even if the rate limit is exceeded.

Is this the more probable reason for this? Any chances it be due to insufficient fees?

I don't think so because the fee is checked at the time of sending the transaction. This issue appears when it seems like you've sent the transaction but it wasn't broadcasted.

I don't think so because the fee is checked at the time of sending the transaction. This issue appears when it seems like you've sent the transaction but it wasn't broadcasted.

Okay, cool. Hope it will be implemented soon. I'll update here if I find out anything new. Thank you.

@aboka2k Please check this issue in the next release. It should be fixed by #1408

repo: pactus-project/pactus


text:
show "login failed" message,  but puppet still work

18:31:24 ERR [PuppetPadlocal] login failed
(node:82001) UnhandledPromiseRejectionWarning: Error: SubRequestCancelError: sub request has been cancelled reason: 1,
at PuppetPadlocal.puppet.on.payload (/Users//Downloads/*****_test/node_modules/wechaty/src/wechaty.ts:440:32)
at PuppetPadlocal.emit (events.js:198:13)
at PuppetPadlocal.EventEmitter.emit (domain.js:448:20)
at _client.api.login.then.catch (/Users//Downloads/*****_test/node_modules/wechaty-puppet-padlocal/src/puppet-padlocal.ts:207:14)
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:82001) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:82001) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
on message: Message#Recalled[🗣Contact<微信团队>]
on message: Message#Recalled[🗣Contact<微信团队>]
on message: Message#Recalled[🗣Contact<微信团队>]
on message: Message#Recalled[🗣Contact<微信团队>]

fixed

authors: iyjian padlocal

repo: padlocal/wechaty-puppet-padlocal


text:
[Bug] After an assignment the value is displayed

After an assignment instruction the value is displayed. This should not happen.

During an execution of a cell code, the instructions are split into code snippets and send to JShell instance (if the snippets are not magics, but Java code).
The last command is aimed to behave like the python kernel, aka to display the value of the last command. The last command can be a method which returns void, which will display nothing. The last command could be a call to a method which returns something. The effect would be that the returned object will be displayed. Also, the command could be simply the name of a variable. In that case the value of the variable will be displayed.
The previous behavior aims to mimic the python kernels.
How it is decided if the result of the last instruction is displayed? The answer is that we allow display values only for specific subkind of snippets defined here: https://download.java.net/java/early_access/jdk23/docs/api/jdk.jshell/jdk/jshell/Snippet.SubKind.html
The problem is that when something like the following is executed: int[] x = new int[1]; x[0] = 3; the same subkind of snippet is considered by JShell TEMP_VAR_EXPRESSION_SUBKIND as it is for 10, for example. This creates a problem since while it is desirable to display the result for the last example, it is not desirable to do that for the first example.

I really don't know how this can be implemented properly. I will close it for now, but if anybody have any idea I am glad to reopen it.

repo: padreati/rapaio-jupyter-kernel


text:
Save drafts automatically

Problem
Hello everybody,
I wrote a huuuuuuuge blog post today. And my browser crashed. I did not save in between, because I'm a bit too stupid sometimes. It would be cool to have some kind of "autosaving" for drafts in sites and blog.
Technical Details

Pagekit version: 1.0.13
Webserver: Apache 2.4
Database: SQLite
PHP Version: 7.1.2

really cool feature

authors: SPQRInc erikperin

repo: pagekit/pagekit


text:
🛑 Open deur vzw is down

In 1d106c9, Open deur vzw (http://opendeurvzw.be) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Open deur vzw is back up in ae11bb3.

repo: pageon/uptime


text:
🛑 Ik geloof in vlaanderen is down

In cd23b11, Ik geloof in vlaanderen (https://ikgeloofinvlaanderen.be) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ik geloof in vlaanderen is back up in d82491e after 40 minutes.


text:
Update to go 1.16

Now that go 1.16 is available, let's upgrade the buildpack to use it

This is already covered in #174: https://github.com/paketo-buildpacks/bundle-install/pull/174/files#diff-33ef32bf6c23acb95f5902d7097b7a1d5128ca061167ec0716715b0b9eeaa5f6L3-R3. I'm gonna close this so we don't have to deal with merge conflicts there.

authors: fg-j ryanmoran

repo: paketo-buildpacks/bundle-install