Genesis v1.5.7 not uploading deps in pipeline correctly

Used latest genesis to update a bosh-release via a pipeline and ran into another regression.
Will debug it later on.
bosh should be update to 259 but 256.2 is being uploaded, and other releases are being downgraded :-S.
Output:
Deploying to BOSH director a5d90271-bb7e-4ffb-b14b-5807fe33f194

Target set to 'acf-global-proto-bosh'
Deployment set to '/tmp/build/028a4217/out/git/acf-global/alpha/manifests/.deploy.yml'
Acting as user 'admin' on 'acf-global-proto-bosh'
Checking whether release bosh/259 already exists...NO
Using remote release 'https://bosh.io/d/github.com/cloudfoundry/bosh?v=256.2'

Director task 3648
  Started downloading remote release > Downloading remote release. Done (00:00:20)

  Started verifying remote release > Verifying remote release. Done (00:00:00)

  Started extracting release > Extracting release. Done (00:00:01)

  Started verifying manifest > Verifying manifest. Done (00:00:00)

  Started resolving package dependencies > Resolving package dependencies. Done (00:00:00)

  Started processing 13 existing packages > Processing 13 existing packages. Done (00:00:00)

  Started processing 8 existing jobs > Processing 8 existing jobs. Done (00:00:00)

  Started release has been created > bosh/256.2. Done (00:00:00)

Task 3648 done

Started		2016-11-03 08:15:20 UTC
Finished	2016-11-03 08:15:41 UTC
Duration	00:00:21

Release uploaded
Acting as user 'admin' on 'acf-global-proto-bosh'
Checking whether release bosh-aws-cpi/60 already exists...YES
Acting as user 'admin' on 'acf-global-proto-bosh'
Checking whether release shield/6.3.6 already exists...YES
Acting as user 'admin' on deployment 'acf-global-alpha-bosh' on 'acf-global-proto-bosh'
Getting deployment properties from director...

Detecting deployment changes
----------------------------
resource_pools:
- name: bosh
  stemcell:
    sha1: 95ecc2709ac62f21d0a1c6cac023585c3919b825
    url: https://bosh.io/d/stemcells/bosh-aws-xen-hvm-ubuntu-trusty-go_agent?v=3263.8
releases:
- name: bosh
  version: '256.2'
  version: '259'
- name: bosh-aws-cpi
  sha1: 8e40a9ff892204007889037f094a1b0d23777058
  sha1: 3a5988bd2b6e951995fe030c75b07c5b922e2d59
  url: https://bosh.io/d/github.com/cloudfoundry-incubator/bosh-aws-cpi-release?v=60
  url: https://bosh.io/d/github.com/cloudfoundry-incubator/bosh-aws-cpi-release?v=53
- name: shield
  sha1: de6e56e8a10c7f07cc6464b1b5239562c4ce47cb
  sha1: 1918606e3fba5351470985e8d641a2ebe7e85912
  url: https://bosh.io/d/github.com/starkandwayne/shield-boshrelease?v=6.3.6
  url: https://bosh.io/d/github.com/starkandwayne/shield-boshrelease?v=6.2.1

Deploying
---------

Director task 3649
  Started preparing deployment > Preparing deployment. Failed: Release version 'bosh/259' doesn't exist (00:00:00)

Error 30006: Release version 'bosh/259' doesn't exist

Task 3649 error

For a more detailed error report, run: bosh task 3649 --debug

I thought latest was 1.5.6?

I released with the fix from #91 this morning to roll it out to client. It was working fine till we tried to update a release.

Answer is to
rm global/releases/**/{url,sha1}

then things work as expected.


How to visualize my registration results?

Hello,author! I have met with difficulties. When I take python src/train_egnn.py, I get a model_epoch_500.pth file in checkpoints. But I do not know how to use the two PCD point clouds I collected for registration, whether it is possible to use the data set provided by the project training, and then their own collection of two points cloud registration and visualization results？I hope to get your answer, thank you very much.

You can use the prediction pose, to convert into homogeneous transform matrix, and apply the transform to the source scan point cloud, as the prediction is from source scan to target, then visualized the transformed scans and target scans together in open3d with different colors, a visualize sample script "viz-pointcloud-reg" is provided under tools folder.

Now train and eval are merged into a single script, just follow the evaluation part, and set "mode" to "test" once your training is done with saved checkpoint. Yes the training loss is actually composed of three part, with rank regularizer loss dominant, so 1.3 is relatively small, but indeed you need to better plot the loss curve offline with train and val loss, like exporting the terminal logs into a txt file. Our original version is planned to be merged with tensorboard for better loss viz, but due to some local env conflict, it is not enabled, sorry for that, so just plot the loss offline by using matplotlib.

If u want to use the pre-trained model directly on your own point cloud scan pair registration, I recommend to check your point cloud scenario, whether it is close to 3DMatch indoor or KITTI outdoor scenes, if not, there may be some data gap for pre-trained and your own data. If your data is similar to large scene room dataset, like Scannet, then please replace the pointnet descriptor extraction encoder with the public  pointTransformerV2 or V3 api, then training the following equi-layers and registration layers only to learn the new equi-feature from large room scan data, otherwise you have to train the whole model from descriptor extraction, to equi-gnn, until to the regression decoder all together on your own data, so the data volume has to be considered as well to match the model capacity.

Great work！Thanks a lot！


bugfix: Freezes free-draw interactions after missed event

PointerCancelEvent was a unhandled PointerEvent, which invalidates the previous input, if already active. There is no PointerUpEvent afterwards. This prevents all future draw events until app restart / PainterController reload.

Facing the same or related to the issue after editing images  and kept the app in background for few minutes and tried to edit using free -draw it was not working the editor was freezed

Facing the same or replate after editing images  and the app in background for few minutes and tried to edit using free -draw it was not working the editor was freezed


Add import button to map list empty state

We have an import button on the map list page when there are maps present. We should also add a Import Map button to the empty state of the page.
AC:

There is an Import Map button on the empty state of the map list page that starts the process of importing a map.

@jfrankl I'm thinking we put the button underneath. Something like "or" with the button underneath. Thoughts?


Reconnect not working

When I mount a drive, disconnect cable for a while, and reconnect it back, the remote drives remain to seem empty until I remount them.
At best, there should be automatic reconnect ability.

it shoud be better now, test it


Cache device keys after generating them

Before they were only cached after signup.
Moved the caching to DeviceWrap, which is responsible
for generating device keys.
r? @maxtaco
cc @malgorithms

👍


No metrics for some of the chassis states

Recently we started using ipmi_exporter and found out that there is no metrics for Drive Fault and Cooling/fan fault states

System Power                        : on
Power overload                      : false
Interlock                           : inactive
Power fault                         : false
Power control fault                 : false
Power restore policy                : Restore
Last Power Event                    : unknown
Chassis intrusion                   : inactive
Front panel lockout                 : inactive
Drive Fault                         : false
Cooling/fan fault                   : false
Chassis Identify state              : off
Power off button                    : enabled
Reset button                        : enabled
Diagnostic Interrupt button         : enabled
Standby button                      : enabled
Power off button disable            : unallowed
Reset button disable                : unallowed
Diagnostic interrupt button disable : unallowed
Standby button disable              : unallowed

Thanks for the patch!


Mkl bf16

Existing Sample Changes
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes Issue#
External Dependencies
List any external dependencies created as a result of this change.
Type of change
Please delete options that are not relevant. Add a 'X' to the one that is applicable.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Implement fixes for ONSAM Jiras

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Command Line
[ ] oneapi-cli
[ ] Visual Studio
[ ] Eclipse IDE
[ ] VSCode
[ ] When compiling the compliler flag "-Wall -Wformat-security -Werror=format-security" was used

Delete this line and everything below if this is not a PR for a new code sample
Delete this line and all above it if this PR is for a new code sample
Adding a New Sample(s)
Description
Please include a description of the sample
Checklist
Administrative

[ ] Review sample design with the appropriate Domain Expert:
[ ] If you have any new dependencies/binaries, inform the oneAPI Code Samples Project Manager

Code Development

[ ] Implement coding guidelines and ensure code quality. see wiki for details
[ ] Adhere to readme template
[ ] Enforce format via clang-format config file
[ ] Adhere to sample.json specification. https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-specification
[ ] Ensure/create CI test configurations for sample (ciTests field) https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-ci-test-object
[ ] Run jsonlint on sample.json to verify json syntax. www.jsonlint.com

Security and Legal

[ ] OSPDT Approval (see Project Manager for assistance)
[ ] Compile using the following compiler flags and fix any warnings, the falgs are: "/Wall -Wformat-security -Werror=format-security"
[ ] Bandit Scans (Python only)
[ ] Virus scan

Review

[ ] Review DPC++ code with Paul Peterseon. (GitHub User: pmpeter1)
[ ] Review readme with Tom Lenth(@tomlenth) and/or Project Manager
[ ] Tested using Dev Cloud when applicable

@mayurpandeyin Can you make the updates based on @petercad's comments? Also, please resolve the conflict in
Libraries/oneMKL/matrix_mul_mkl/makefile
Once you have done that, I will try build and run the sample and approve.

@mayurpandeyin There's a conflict with Libraries/oneMKL/matrix_mul_mkl/makefile. Can you resolve that?
Also, dpcpp is deprecated. I think you will want to use icx-cl in the Makefile.

@mayurpandeyin I'm going to close this issue out. We've made some changes to the existing matrix_mul_mkl sample. There was a request to modify the sample to have both a fp32 and fp64 variant of matrix_mul_mkl. If you want to add an example for bf16, I would suggest you to submit a new PR based off of the development branch.


RFP - emusak-ui

Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts with 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL : https://github.com/CapitaineJSparrow/emusak-ui
Direct download URL for the software / installer : https://github.com/CapitaineJSparrow/emusak-ui/releases/download/v1.0.108/emusak-1.0.108.Setup.exe
Software summary / short description:  This is a tool which allows you to download saves or mods for Nintendo Switch emulators using a compatible Emusak backend

@soredake I can't find a package for this. Can you confirm what the URL is / what it was called?

@pauby this software is discontinued and will stop working soon


move_lower and move_higher not working returning nil

Hi,
I am using Rails 3.2.6 application with  acts_as_list(0.1.6)  gem included in my Gemfile.
I have the code as follows
class Product < ActiveRecord::Base
  attr_accessible :name, :price
  has_many :product_stores
  has_many :stores, :through => :product_stores, :order => 'product_stores.position'
end

class ProductStore < ActiveRecord::Base
  attr_accessible :position, :product_id, :store_id
  default_scope :order => 'position'

  belongs_to :store
  belongs_to :product

  acts_as_list :scope => :product
end

class Store < ActiveRecord::Base
  attr_accessible :description, :name
  has_many :product_stores
  has_many :products, :through => :product_stores, :order => 'product_stores.position'
end

I have position(integer) column in the product_stores table . But the move_lower and move_higher functions does not work  returning nil and the product is not moved to any position without updating the position. e.g
ruby-1.9.2-p290 :008 > store.product_stores.where(:product_id => 2).first.move_lower
  ProductStore Load (0.2ms)  SELECT `product_stores`.* FROM `product_stores` WHERE `product_stores`.`store_id` = 1 AND `product_stores`.`product_id` = 2 LIMIT 1
  ProductStore Load (0.3ms)  SELECT `product_stores`.* FROM `product_stores` WHERE (`product_stores`.`product_id` = 2 AND position = 2) ORDER BY position LIMIT 1
 => nil
ruby-1.9.2-p290 :009 >

Hw to resolve it ?

I had a Category hierarchy in my app and had the same problem with null position values. I solved it by adding this method to the migration that created the position column:
  update_position_recursively(Category.roots)

  def update_position_recursively(categories)
    categories.each_with_index do |cat, idx|
      cat.update_attribute(:position, idx)
      update_position(cat.subcategories) unless cat.subcategories.empty?
    end
  end

This is assuming Category.roots would return all roots and that I have has_many :subcategories ... in my Category class

I fixed this problem by making a rake task (as DB updates generally shouldn't be done in migrations). See: https://stackoverflow.com/a/15531843/380607


update readme.md

I have added basic step of starting up with python.

The grammar needs to be fixed.


fix: add rafif rabbani

resolves #1417
Checklist for profile addition

[x] Name the PR fix: add <your-username>.
[x] You've added file named your-username.json in the profiles directory.
[x] You've linked the PR to the correct issue.

Other additions/changes

[x] Changes made in this PR are mentioned below
[] Search previous suggestions before making a new one, as yours may be a duplicate.
[x] I acknowledge that all my contributions will be made under the project's license.
[x] I've read the contributing guidelines

This PR adds/fixes

Notes

Closing PR due to inactivity. Feel free to raise a new one.


Do we need consistent reads of etcd?

I am looking and looking at the code for pkg/registry/service/ipallocator/controller/repair.go, and I am having a hard time proving to myself that it is correct.
We have etcd configured to read in 'weakly consistent' mode.  As @smarterclayton and @lavalamp  previously explained to me (thanks!) that is not a problem, because any writes are done as a CAS with the version.  We might see stale data, and derive stale data from that, but we won't ever be able to write stale data.
However, I am worried that I can construct what appears to be possible etcd-partition states that an inconsistent read won't catch.  I'm basing this on this issue https://github.com/coreos/etcd/issues/741, in particular that raft/etcd allows a node to believe itself the leader while another leader has been elected.
For example, support I have one service, s1, with one IP at t0: <IP_ADDRESS>  Then I change s1's IP at t1: <IP_ADDRESS>.  So our IP allocation map should go from (<IP_ADDRESS>) -> (<IP_ADDRESS>)
But suppose we had a partition event in etcd just before t1.  At t0, node 1 believes itself to be the leader.    Node 1 still believes itself to be the leader at t1 (though its days are numbered), and will answer inconsistent reads.  But Node 1 has not seen s1's change from <IP_ADDRESS> -> <IP_ADDRESS>.
Now, at t2 the repair process does the following:
Reads the services from node 1: { s1=(<IP_ADDRESS>) }
Reads the node map from node 2: { (<IP_ADDRESS>) }
Builds a new node map: { (<IP_ADDRESS>) }
Writes the new node map back to node 2: { (<IP_ADDRESS>) }
And now (<IP_ADDRESS>) can be re-allocated to another service, despite the fact that s1 has it allocated.
Moreover, I think that not only can this happen with a double-leader partition, but it can happen simply if node 1 is lagging (no partitions behind the leader) when go-etcd is doing weakly consistent reads.
In short, I think we need etcd do consistent reads.  And then we also need to do further checks to detect partitions: I think the partition scenario could be caught because the node map in node would be newer than the newest service.
Is this in fact possible?  Or is there some etcd/versioning mechanism I am missing?

On May 14, 2015, at 8:23 PM, Justin Santa Barbara<EMAIL_ADDRESS>wrote:
I am looking and looking at the code for pkg/registry/service/ipallocator/controller/repair.go, and I am having a hard time proving to myself that it is correct.
We have etcd configured to read in 'weakly consistent' mode. As @smarterclayton and @lavalamp previously explained to me (thanks!) that is not a problem, because any writes are done as a CAS with the version. We might see stale data, and derive stale data from that, but we won't ever be able to write stale data.
However, I am worried that I can construct what appears to be possible etcd-partition states that an inconsistent read won't catch. I'm basing this on this issue coreos/etcd#741, in particular that raft/etcd allows a node to believe itself the leader while another leader has been elected.
For example, support I have one service, s1, with one IP at t0: <IP_ADDRESS> Then I change s1's IP at t1: <IP_ADDRESS>. So our IP allocation map should go from (<IP_ADDRESS>) -> (<IP_ADDRESS>)

You can't change a services ip?

But suppose we had a partition event in etcd just before t1. At t0, node 1 believes itself to be the leader.  Node 1 still believes itself to be the leader at t1 (though its days are numbered), and will answer inconsistent reads. But Node 1 has not seen s1's change from <IP_ADDRESS> -> <IP_ADDRESS>.
Now, at t2 the repair process does the following:
Reads the services from node 1: { s1=(<IP_ADDRESS>) }
Reads the node map from node 2: { (<IP_ADDRESS>) }
Builds a new node map: { (<IP_ADDRESS>) }
Writes the new node map back to node 2: { (<IP_ADDRESS>) }
And now (<IP_ADDRESS>) can be re-allocated to another service, despite the fact that s1 has it allocated.
Moreover, I think that not only can this happen with a double-leader partition, but it can happen simply if node 1 is lagging (no partitions behind the leader) when go-etcd is doing weakly consistent reads.
In short, I think we need etcd do consistent reads. And then we also need to do further checks to detect partitions: I think the partition scenario could be caught because the node map in node would be newer than the newest service.
Is this in fact possible? Or is there some etcd/versioning mechanism I am missing?

I believe repair must compare the resource versions in order to guarantee that the service list is newer than the read map (or ask for a consistent read).  That's a simple test.  I'm not aware of a partition scenario where a new term can be committed in the absence of a restore from backup.
I believe allocations are the only resource that require two resources to achieve their guarantee.  If sharded, the allocation maps have to be per shard anyway.  Trying to think of what other resources fall under this constraint.

—
Reply to this email directly or view it on GitHub.

Allocation is safe because set addition is a crdt safe operation.  Removal is not safe and so requires linearization read-read-write in order so as to make forward progress.

True, IP allocations can't change - poor example I chose there :-)  But:

I think the same applies if we delete service 1=(<IP_ADDRESS>) and create service 2=(<IP_ADDRESS>)
I think we want an approach that works across all domains - I'm working on publicPorts

I get really nervous when we start layering on checks in response to counter-examples; I just worry that there's always another counter-example that hasn't been suggested yet.
Another problem: if we assign a portal IP, but then fail to update the service list, then the version of the portal map will be truly ahead of the highest version in the service list.  I don't know how we differentiate that case from a stale read of the service list.

On May 14, 2015, at 10:45 PM, Justin Santa Barbara<EMAIL_ADDRESS>wrote:
True, IP allocations can't change - poor example I chose there :-) But:

I think the same applies if we delete service 1=(<IP_ADDRESS>) and create service 2=(<IP_ADDRESS>)
I think we want an approach that works across all domains - I'm working on publicPorts

I get really nervous when we start layering on checks in response to counter-examples; I just worry that there's always another counter-example that hasn't been suggested yet.
Another problem: if we assign a portal IP, but then fail to update the service list, then the version of the portal map will be truly ahead of the highest version in the service list. I don't know how we differentiate that case from a stale read of the service list.

We may not have to.  We can either wait and retry the read, or require allocations to miss two repair intervals before being reclaimed (or a unit multiple of that).  That controls reclamation with an upper bound on the time an allocation can precede a service.
The allocator controller reduces the risk of that occurring because it is level driven.  In general, the easier assumption to relax is that service ips never change, and that users are allowed to request portal ips.
Appreciate the review.

—
Reply to this email directly or view it on GitHub.

Alternatively, assuming multi object write in etcd3, we combine write and allocation.  But timeframe on that is further out.

On Thu, May 14, 2015 at 5:50 PM, Clayton Coleman
<EMAIL_ADDRESS>wrote:

On May 14, 2015, at 8:23 PM, Justin Santa Barbara<EMAIL_ADDRESS>wrote:

For example, support I have one service, s1, with one IP at t0: <IP_ADDRESS> Then I change s1's IP at t1: <IP_ADDRESS>. So our IP allocation map should go from (<IP_ADDRESS>) -> (<IP_ADDRESS>)

You can't change a services ip?

You could change the port, though, unless we have a general rule that
any instance of this pattern must be immutable

I believe repair must compare the resource versions in order to guarantee that the service list is newer than the read map (or ask for a consistent read). That's a simple test.

Do we set ResourceVersion for a list to the highest of any member of
the list?  Empirically, when I get a list I always see metadata
empty - no selfLink, no resourceVersion.  Should we be populating it?
Or should we get rid of it?

/subscribe

On May 14, 2015, at 11:51 PM, Tim Hockin<EMAIL_ADDRESS>wrote:
On Thu, May 14, 2015 at 5:50 PM, Clayton Coleman
<EMAIL_ADDRESS>wrote:

On May 14, 2015, at 8:23 PM, Justin Santa Barbara<EMAIL_ADDRESS>wrote:

For example, support I have one service, s1, with one IP at t0: <IP_ADDRESS> Then I change s1's IP at t1: <IP_ADDRESS>. So our IP allocation map should go from (<IP_ADDRESS>) -> (<IP_ADDRESS>)

You can't change a services ip?

You could change the port, though, unless we have a general rule that
any instance of this pattern must be immutable

I believe repair must compare the resource versions in order to guarantee that the service list is newer than the read map (or ask for a consistent read). That's a simple test.

Do we set ResourceVersion for a list to the highest of any member of
the list?

It's the current etcd committed term so it's "now" according to the etcd server you're talking to.

Empirically, when I get a list I always see metadata
empty - no selfLink, no resourceVersion.

Get from server or via kubectl get?

Should we be populating it?

Used to be

Or should we get rid of it?
—
Reply to this email directly or view it on GitHub.

On May 14, 2015, at 11:51 PM, Tim Hockin<EMAIL_ADDRESS>wrote:
On Thu, May 14, 2015 at 5:50 PM, Clayton Coleman
<EMAIL_ADDRESS>wrote:

On May 14, 2015, at 8:23 PM, Justin Santa Barbara<EMAIL_ADDRESS>wrote:

For example, support I have one service, s1, with one IP at t0: <IP_ADDRESS> Then I change s1's IP at t1: <IP_ADDRESS>. So our IP allocation map should go from (<IP_ADDRESS>) -> (<IP_ADDRESS>)

You can't change a services ip?

You could change the port, though, unless we have a general rule that
any instance of this pattern must be immutable

I believe repair must compare the resource versions in order to guarantee that the service list is newer than the read map (or ask for a consistent read). That's a simple test.

Also, we can compare two things.  The current etcd index on the read should be > than the read index of the map, AND at least one service modified index should be > the map modified index.  If the latter condition is not true we don't know whether the service succeeded (and we didn't observe it), failed, or is delayed arbitrarily.  Only in that case must we read again with a wait.

Do we set ResourceVersion for a list to the highest of any member of
the list? Empirically, when I get a list I always see metadata
empty - no selfLink, no resourceVersion. Should we be populating it?
Or should we get rid of it?
—
Reply to this email directly or view it on GitHub.

I've opened an issue with etcd to see if they can provide some input.
But, I think we might be OK, even without consistent reads, if we do the following procedure (which is I think what @smarterclayton suggested):

We read the key we are going to update, and note the current etcd raft index (the raft index, not the key lastModified)
We read all the "input" keys, and if we ever see a raft index < the index in step 1, we abort / retry.  We may have out-of-date reads, but we are seeing a consistent sequence in time (a linearizable view).
We then do a CAS write on the first key, comparing against the value/lastModified in step 1

The write in #3 will only succeed if the key has not changed and was up to date.  (This is what we have today)
But we also know that we saw a linearizable view of the world.  So we only have to deal with concurrent mutations, which the current logic deals with by always writing to the bitmap key whenever any service changes, thus invalidating the CAS.
In step 2, if we do multiple reads, I do not know whether we have to restart if we see any out-of-sequence indexes, or can just compare to step 1.  My guess is that in general we do, but in this particular case because we always update the bitmap key we're OK.
In other words, I think we can get linearized reads simply by observing the etcd server index and making sure it is monotonic.  But this is what I have asked the etcd folk to confirm.

----- Original Message -----

I've opened an issue with etcd to see if they can provide some input.
But, I think we might be OK, even without consistent reads, if we do the
following procedure (which is I think what @smarterclayton suggested):

We read the key we are going to update, and note the current etcd raft
index (the raft index, not the key lastModified)
We read all the "input" keys, and if we ever see a raft index < the index
in step 1, we abort / retry.  We may have out-of-date reads, but we are
seeing a consistent sequence in time (a linearizable view).
We then do a CAS write on the first key, comparing against the
value/lastModified in step 1

The write in #3 will only succeed if the key has not changed and was up to
date.  (This is what we have today)
But we also know that we saw a linearizable view of the world.  So we only
have to deal with concurrent mutations, which the current logic deals with
by always writing to the bitmap key whenever any service changes, thus
invalidating the CAS.
In step 2, if we do multiple reads, I do not know whether we have to restart
if we see any out-of-sequence indexes, or can just compare to step 1.  My
guess is that in general we do, but in this particular case because we
always update the bitmap key we're OK.
In other words, I think we can get linearized reads simply by observing the
etcd server index and making sure it is monotonic.  But this is what I have
asked the etcd folk to confirm.

Your description matches what expect etcd to view - we have to linearize allocation map -> service list -> CAS on allocation map.  At least one service must be at or above the etcd index of the allocation map.

Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/issues/8295#issuecomment-102431681

On Fri, May 15, 2015 at 6:01 AM, Clayton Coleman
<EMAIL_ADDRESS>wrote:

Get from server or via kubectl get?

kubectl - should there be a difference?
$ kubectl get pods -o json | head -5
{
    "kind": "List",
    "apiVersion": "v1beta3",
    "metadata": {},
    "items": [

Should we be populating it?

Used to be

Seems not any more.

On May 15, 2015, at 11:38 AM, Tim Hockin<EMAIL_ADDRESS>wrote:
On Fri, May 15, 2015 at 6:01 AM, Clayton Coleman
<EMAIL_ADDRESS>wrote:

Get from server or via kubectl get?

kubectl - should there be a difference?

It's a bug, there's special code to unify resource versions across multiple calls.

$ kubectl get pods -o json | head -5
{
"kind": "List",
"apiVersion": "v1beta3",
"metadata": {},
"items": [

Should we be populating it?

Used to be

Seems not any more.

Bug.  The rest API for each individual call returns it (note you have a List, not a PodList).

—
Reply to this email directly or view it on GitHub.

Do we set ResourceVersion for a list to the highest of any member of the list?

No, it is set to the global etcd index (which will be >= the highest member of the list). The highest member of the list might be too old to be in the watch window.
As for why you don't see it in kubectl output, that sounds like a kubectl bug. It's definitely there if you curl. (just tried it) In fact basically nothing would work if it weren't being set right.

On May 15, 2015, at 10:55 PM, Daniel Smith<EMAIL_ADDRESS>wrote:
Do we set ResourceVersion for a list to the highest of any member of the list?
No, it is set to the global etcd index (which will be >= the highest member of the list). The highest member of the list might be too old to be in the watch window.
As for why you don't see it in kubectl output, that sounds like a kubectl bug. It's definitely there if you curl. (just tried it) In fact basically nothing would work if it weren't being set right.

It's almost certainly the version merge code being wrong after recent changes to how we dealt with lists.  In fact, I kind of remember putting a todo in the code to fix it.

—
Reply to this email directly or view it on GitHub.

closing this issue b/c in v3 all reads are quorum reads, and original issue sited has been closed for a long time now.


Clicking on ref link leads to wrong location

Maybe "wrong location" is an exaggeration, but what I mean is that if you click on a link that says "Theorem 1" in Chrome, you are directed to the theorem body, while the header "Theorem 1" is not visible --- it's off the top of the screen.
Hence it's not clear that you have been directed to the right place unless you scroll up.

Yes, I have noticed that as well. It's actually because of the main topbar which has a white background and it's almost the same height as the title div of the directive.

Is there any way to fix it you can think of?

@najuzilu would it help to wrap the whole theorem in another div and set the id=target to get link to the top of a theorem? @AakashGfude may be able to help on the html side of things here.

I think the easiest way might be to control the scroll behaviour using javascript and provide a bit of an offset to the location scrolled.
If @najuzilu is not working on this, I can give this one a shot.

sounds good @najuzilu . I guess it will be a more generic solution.


Redis: Adding support for disabling Redis password

Added password.enabled flag to enable/disable Redis password.

I signed it!

Closing this as the password can be disabled by using a different redis image.


Linux It Works Just Bundle It

It Runs, you just gotta slap it in a deb file (not like anyone really needs much support its an API call to a GitHub Repo that edits markdown. Smart but not gonna require all that much)

Hi, I just found this app on Electron App Directory and I find this amazing, I'm using Fedora 30 now, and the app runs very good on Node 8 (it's probably time to update), I just have some trouble with nodegit, for Fedora you need install this:
sudo dnf install openssh-devel // For FEDORA, RHEL or CENTOS

And then you start all the compiling stuff from the README

Great! I'll love to see this on .deb and .rpm👍❤🙂

I managed to install it in Fedora and all the setup went just fine. However, the app is not working properly.

Developer tools are toggled by default at startup.
File > New note does not work at all. I have to use the + button close to Note.
Even though the commits appear to be happening, they are not being synced with the repository. Sometimes when I try to sync the application simply closes.
Besides, when I click to move a note to the Recycle Bin, nothing happens.

I thought of creating an issue but since it's not officially supported in Linux, maybe it is better sharing it here.

or don't, its on you guys but I don't use it and so there is no need to keep the issue open.


Swup, main element animation

The setup:
I want to setup my site with my own id names, so i have set up the containers data-containers="#base #nav"
The problem:
Now the swup animation does not work anymore. This is because the animation plugins also use an option on them to name the main element of the animation({{ mainElement: '#swup' }). See documentation.
https://swup.js.org/themes/fade-theme
https://github.com/swup/fade-theme/blob/master/src/index.js#L11
The solution
Add a data-main-element attribute so we can also setup the main elements for the animations.

https://github.com/symfony/ux/pull/20 should solve this issue.


Added a cache for TransactionAndMetadata objects

This PR adds a cache for TransactionAndMetadata objects. The backend of clio maintains a cache of the NUM_CACHED_LEDGERS most recently published ledgers' transactions. I am posting this now mainly for visibility.

I think it is safe to assume we are not going to be merging this so i'm closing it.


Add revision prefix to cycle test comp key

Please provide a description of this PR:
Followup to #38219
Just noticed that we missed adding the remote prefix ("^") to the revision key in the cycle test when the new comp function is used, so remote instances always look like local ones, missing several cases where an initial lock steal should occur.

@frankbu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ipv6_istio
d17e8c8890405892437500a9114901dd3d0c6917
link
true
/test integ-ipv6_istio

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

/test integ-ipv6_istio


Support for User-Defined Fonts

as i see it fit up to the current build, all controls are using ROBOTO Fonts by default. I was kind off hoping to use some other font like Segoe, Lucida, Arial, etc. wondering if this could be implemented in the upcoming or future builds. thanks

This is because Roboto is the font Google specifies in their Material Design Guidelines. The idea of MaterialSkin was to implement Material Design exactly as how Google describes it.
I would be okay with MaterialSkin supporting other fonts but the default one should be Roboto.

+1, when using Chinese chars it will become "SimSum" which is the default font in Windows XP, it have poor display effect, especially high dpi device. After Windows 7, MS is using "Microsoft Yahei" to solve it.


Is it possible to set MTG-FakeTLS behind NGINX?

Currently I have NGINX setup accepting connection from Cloudflare (with strict SSL setting). Setting MTG MTG_CLOAK_PORT as 9443, and make NGINX listening at 9443 does not work. I suspect It is due to Cloudflare SSL setting. May I know if I can reverse proxy the connection from Cloudflare to NGINX to MTG instead?
Thanks.

Yes, please see this instruction: https://github.com/freejohn123/mtproto-tls-server

As long as I investigate, it is not possible to use cloudflare. Cloudflare only proxy http/https stream, but mtproto is not.
Of course you can set mtg behind nginx. but the mechanism is not client -> http/https -> nginx -> mtg, it is client -> mtproto -> nginx with proxy protocol -> mtg. In this chain, nginx acts as a tcp load balance but not HTTP reverse proxy.
I also wanna set mtg behind cloudflare but current mtproto do not allow this. hope that mtproto would support HTTP or ws in the future.

I have a similar setup.
I have a VPS running caddy that I use to host my domain apex, and to use as a reverse_proxy for docker containers and other services. I'm behind cloudflare, but the acme_dns cloudflare caddy plugin is compiled and working properly.
I've been using mtg for a long time and it recently stopped working after I upgraded Ubuntu. Not right after, it took like a few days, which was really really weird...
But I took the opportunity to migrate to a docker container. It took me hours, but I eventually got it to work... And then it stopped... Nothing changed, it just stopped working after like an hour. Since then I've been completely and hopelessly lost getting it started again. I've tried direct ports and the docker container name, and nothing works.
I've additionally added a new A record for my subdomain and ensured it was pointed at my VPS over my wildcard. So I've tried with and without cloudflare, and nothing has worked. It's absolutely crazy.


[Bug] Drive enumeration in 54-check-optical-drive.sh

Current Behavior
SR_DEV and SG_DEV are picking out - as the device path given the following output from lsscsi:
[1:0:0:0] cd/dvd HL-DT-ST BD-RE WH14NS40 1.05 /dev/sr0 -

Expected Behavior
SR_DEV and SG_DEV assigned as /dev/sr0 given the lsscsi output:
[1:0:0:0] cd/dvd HL-DT-ST BD-RE WH14NS40 1.05 /dev/sr0 -

Steps To Reproduce
No response
Environment

OS: nixos
OS version: 24.05 and kernel 6.6.41
CPU: AMD Ryzen 7 5800X
Docker version: 24.0.9
Device model: WH14NS40
Browser/OS: firefox/nixos

Container creation
  virtualisation.oci-containers.containers = {
    makemkv = {
      image = "docker.io/jlesage/makemkv:latest";
      autoStart = true;
      ports = [ "5800:5800" ];
      volumes = [
        "/run/media/josiah/DATA/makemkv/config:/config:rw"
        "/run/media/josiah/DATA/makemkv:/storage:ro"
        "/run/media/josiah/DATA/makemkv/output:/output:rw"
      ];
      extraOptions = [
        "--device=/dev/disk/by-id/ata-HL-DT-ST_BD-RE_WH14NS40_KLPK7693753:/dev/sr0"
      ];
      environment = {
        "MAKEMKV_KEY" = "REDACTED";
        "APP_NICENESS" = "19";
        "AUTO_DISC_RIPPER_BD_MODE" = "mkv";
        "AUTO_DISC_RIPPER_FORCE_UNIQUE_OUTPUT_DIR" = "1";
        "AUTO_DISC_RIPPER" = "1";
        "AUTO_DISC_RIPPER_EJECT" = "1";
      };
    };
  };

Container log
[init        ] container is starting...
[cont-env    ] loading container environment variables...
[cont-env    ] APP_NAME: loading...
[cont-env    ] APP_VERSION: loading...
[cont-env    ] DISPLAY: executing...
[cont-env    ] DISPLAY: terminated successfully.
[cont-env    ] DISPLAY: loading...
[cont-env    ] DOCKER_IMAGE_PLATFORM: loading...
[cont-env    ] DOCKER_IMAGE_VERSION: loading...
[cont-env    ] GTK2_RC_FILES: executing...
[cont-env    ] GTK2_RC_FILES: terminated successfully.
[cont-env    ] GTK2_RC_FILES: loading...
[cont-env    ] GTK_THEME: executing...
[cont-env    ] GTK_THEME: terminated successfully.
[cont-env    ] GTK_THEME: loading...
[cont-env    ] HOME: loading...
[cont-env    ] QT_STYLE_OVERRIDE: executing...
[cont-env    ] QT_STYLE_OVERRIDE: terminated successfully.
[cont-env    ] QT_STYLE_OVERRIDE: loading...
[cont-env    ] SUP_GROUP_IDS_INTERNAL: executing...
[cont-env    ] SUP_GROUP_IDS_INTERNAL: terminated successfully.
[cont-env    ] SUP_GROUP_IDS_INTERNAL: loading...
[cont-env    ] TAKE_CONFIG_OWNERSHIP: loading...
[cont-env    ] XDG_CACHE_HOME: loading...
[cont-env    ] XDG_CONFIG_HOME: loading...
[cont-env    ] XDG_DATA_HOME: loading...
[cont-env    ] XDG_RUNTIME_DIR: loading...
[cont-env    ] XDG_STATE_HOME: loading...
[cont-env    ] container environment variables initialized.
[cont-secrets] loading container secrets...
[cont-secrets] container secrets loaded.
[cont-init   ] executing container initialization scripts...
[cont-init   ] 10-certs.sh: executing...
[cont-init   ] 10-certs.sh: terminated successfully.
[cont-init   ] 10-check-app-niceness.sh: executing...
[cont-init   ] 10-check-app-niceness.sh: terminated successfully.
[cont-init   ] 10-clean-logmonitor-states.sh: executing...
[cont-init   ] 10-clean-logmonitor-states.sh: terminated successfully.
[cont-init   ] 10-clean-tmp-dir.sh: executing...
[cont-init   ] 10-clean-tmp-dir.sh: terminated successfully.
[cont-init   ] 10-fontconfig-cache-dir.sh: executing...
[cont-init   ] 10-fontconfig-cache-dir.sh: terminated successfully.
[cont-init   ] 10-init-users.sh: executing...
[cont-init   ] 10-init-users.sh: terminated successfully.
[cont-init   ] 10-nginx.sh: executing...
[cont-init   ] 10-nginx.sh: terminated successfully.
[cont-init   ] 10-openbox.sh: executing...
[cont-init   ] 10-openbox.sh: terminated successfully.
[cont-init   ] 10-pkgs-mirror.sh: executing...
[cont-init   ] 10-pkgs-mirror.sh: terminated successfully.
[cont-init   ] 10-set-tmp-dir-perms.sh: executing...
[cont-init   ] 10-set-tmp-dir-perms.sh: terminated successfully.
[cont-init   ] 10-vnc-password.sh: executing...
[cont-init   ] 10-vnc-password.sh: terminated successfully.
[cont-init   ] 10-web-data.sh: executing...
[cont-init   ] 10-web-data.sh: terminated successfully.
[cont-init   ] 10-x11-unix.sh: executing...
[cont-init   ] 10-x11-unix.sh: terminated successfully.
[cont-init   ] 10-xdg-runtime-dir.sh: executing...
[cont-init   ] 10-xdg-runtime-dir.sh: terminated successfully.
[cont-init   ] 15-cjk-font.sh: executing...
[cont-init   ] 15-cjk-font.sh: terminated successfully.
[cont-init   ] 15-install-pkgs.sh: executing...
[cont-init   ] 15-install-pkgs.sh: terminated successfully.
[cont-init   ] 54-check-optical-drive.sh: executing...
[cont-init   ] 54-check-optical-drive.sh: looking for usable optical drives...
[cont-init   ] 54-check-optical-drive.sh: found optical drive [/dev/sr0, -], but it is not usable because:
[cont-init   ] 54-check-optical-drive.sh:   --> the host device - is not exposed to the container.
[cont-init   ] 54-check-optical-drive.sh: found optical drive [/dev/sr1, -], but it is not usable because:
[cont-init   ] 54-check-optical-drive.sh:   --> the host device - is not exposed to the container.
[cont-init   ] 54-check-optical-drive.sh: no usable optical drive found.
[cont-init   ] 54-check-optical-drive.sh: terminated successfully.
[cont-init   ] 55-makemkv.sh: executing...
[cont-init   ] 55-makemkv.sh: registration key already up-to-date.
[cont-init   ] 55-makemkv.sh: getting supported drives...
[cont-init   ] 55-makemkv.sh: terminated successfully.
[cont-init   ] 85-take-config-ownership.sh: executing...
[cont-init   ] 85-take-config-ownership.sh: terminated successfully.
[cont-init   ] 89-info.sh: executing...
    ╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮
    │                                                                      │
    │ Application:           MakeMKV                                       │
    │ Application Version:   1.17.7                                        │
    │ Docker Image Version:  24.06.1                                       │
    │ Docker Image Platform: linux/amd64                                   │
    │                                                                      │
    ╰――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╯
[cont-init   ] 89-info.sh: terminated successfully.
[cont-init   ] all container initialization scripts executed.
[init        ] giving control to process supervisor.
[supervisor  ] loading services...
[supervisor  ] loading service 'default'...
[supervisor  ] loading service 'logmonitor'...
[supervisor  ] service 'logmonitor' is disabled.
[supervisor  ] loading service 'logrotate'...
[supervisor  ] loading service 'app'...
[supervisor  ] loading service 'gui'...
[supervisor  ] loading service 'openbox'...
[supervisor  ] loading service 'xvnc'...
[supervisor  ] loading service 'certsmonitor'...
[supervisor  ] service 'certsmonitor' is disabled.
[supervisor  ] loading service 'nginx'...
[supervisor  ] loading service 'autodiscripper-11'...
[supervisor  ] service 'autodiscripper-11' is disabled.
[supervisor  ] loading service 'autodiscripper-0'...
[supervisor  ] service 'autodiscripper-0' is disabled.
[supervisor  ] loading service 'autodiscripper'...
[supervisor  ] service 'autodiscripper' is disabled.
[supervisor  ] loading service 'autodiscripper-1'...
[supervisor  ] service 'autodiscripper-1' is disabled.
[supervisor  ] loading service 'autodiscripper-2'...
[supervisor  ] service 'autodiscripper-2' is disabled.
[supervisor  ] loading service 'autodiscripper-3'...
[supervisor  ] service 'autodiscripper-3' is disabled.
[supervisor  ] loading service 'autodiscripper-4'...
[supervisor  ] service 'autodiscripper-4' is disabled.
[supervisor  ] loading service 'autodiscripper-9'...
[supervisor  ] service 'autodiscripper-9' is disabled.
[supervisor  ] loading service 'autodiscripper-7'...
[supervisor  ] service 'autodiscripper-7' is disabled.
[supervisor  ] loading service 'autodiscripper-13'...
[supervisor  ] service 'autodiscripper-13' is disabled.
[supervisor  ] loading service 'autodiscripper-6'...
[supervisor  ] service 'autodiscripper-6' is disabled.
[supervisor  ] loading service 'autodiscripper-8'...
[supervisor  ] service 'autodiscripper-8' is disabled.
[supervisor  ] loading service 'autodiscripper-15'...
[supervisor  ] service 'autodiscripper-15' is disabled.
[supervisor  ] loading service 'autodiscripper-14'...
[supervisor  ] service 'autodiscripper-14' is disabled.
[supervisor  ] loading service 'autodiscripper-5'...
[supervisor  ] service 'autodiscripper-5' is disabled.
[supervisor  ] loading service 'autodiscripper-10'...
[supervisor  ] service 'autodiscripper-10' is disabled.
[supervisor  ] loading service 'autodiscripper-12'...
[supervisor  ] service 'autodiscripper-12' is disabled.
[supervisor  ] all services loaded.
[supervisor  ] starting services...
[supervisor  ] starting service 'xvnc'...
[xvnc        ] Xvnc TigerVNC 1.13.1 - built Dec 21 2023 00:55:16
[xvnc        ] Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
[xvnc        ] See https://www.tigervnc.org for information on TigerVNC.
[xvnc        ] Underlying X server release 12014000
[xvnc        ] Tue Sep 17 21:07:29 2024
[xvnc        ]  vncext:      VNC extension running!
[xvnc        ]  vncext:      Listening for VNC connections on /tmp/vnc.sock (mode 0660)
[xvnc        ]  vncext:      Listening for VNC connections on all interface(s), port 5900
[xvnc        ]  vncext:      created VNC server for screen 0
[supervisor  ] starting service 'openbox'...
[supervisor  ] starting service 'nginx'...
[nginx       ] Listening for HTTP connections on port 5800.
[supervisor  ] starting service 'app'...
[supervisor  ] all services started.
[xvnc        ] Tue Sep 17 21:12:10 2024
[xvnc        ]  Connections: accepted: /tmp/vnc.sock
[xvnc        ]  SConnection: Client needs protocol version 3.8
[xvnc        ]  SConnection: Client requests security type None(1)
[xvnc        ]  VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
[xvnc        ]  VNCSConnST:  Client pixel format depth 24 (32bpp) little-endian bgr888
[xvnc        ]  ComparingUpdateTracker: 0 pixels in / 0 pixels out
[xvnc        ]  ComparingUpdateTracker: (1:-nan ratio)

Container inspect
No response
Anything else?
Proposed fix submitted in https://github.com/jlesage/docker-makemkv/pull/219

To my knowledge, without a /dev/sgX device, MakeMKV won't recognize the drive.
The log message could be enhanced, but basically the - means that there is no device.

Then perhaps there should be a more explicit error state if the sg mod isn't loaded.  If you agree should I close this out and create a feature req?


Long Edges end very far from Nodes

Hi,
First of all, visjs is impressive and it's great.
I have recently an issue with very long edges with arrows (> 150 000 point/pixel) : the edges are not ending on the nodes they are linked but they remain very far...

Any ideas on how to fix that ?
Thanks

Sure... Here you go :
https://codepen.io/jk-12345/pen/gOOXjPB

Thanks for the MWE.
After investigating it I found out that disabling smooth edges makes the problem disappear. So the problem will be in the smooth edge algorithms. They probably make some rough guesses that result in small imprecisions. You just streched them to noticeable size.
I'm not sure when I'll have the time to do something about it. There are already a few other things I'd like to do. If you're willing to supply a PR, and thank you very much if you do, the offending code will most likely reside in https://github.com/visjs/vis-network/tree/master/lib/network/modules/components/edges.


Vector3D class output invalid json schema.

For example, firstPerson/firstPersonBoneOffset、 it requires array in json schema,  But current outputted json data of vrm file is like {"x"=>0, "y"=>0.06, "z"=>0}

Thanks for the feedback.
I will fix the schema.


Update Code - Proof_Of_ContributionSnapshot4.md

Adding contributions taking place during Snapshot 4 for the Nedbuchadnezzar crew.

Weights adjusted.  Please resubmit PR based on amount noted in smart contract.  Moving forward, pull requests not approved by the last day of the month, will not be adjusted, but will be rejected and not considered until the following month.

Thanks for the feedback - adjusted weights and resubmitted via new pull request


Does not show CPU time in Ububtu 20.04

Ubuntu 20.04
Disks:
sda   38.2G  HDD

CPU: SHA256-hashing 500 MB
    CPU: bzip2-compressing 500 MB
    CPU: AES-encrypting 500 MB

ioping: seek rate
    min/avg/max/mdev = 102.7 us / 315.6 us / 19.9 ms / 252.1 us
ioping: sequential read speed
    generated 7.51 k requests in 5.00 s, 1.83 GiB, 1.50 k iops, 375.6 MiB/s

While in CentOS 7, 8
Disks:
sda  152.6G  HDD
sdb    100G  HDD

CPU: SHA256-hashing 500 MB
    2.062 seconds
CPU: bzip2-compressing 500 MB
    6.318 seconds
CPU: AES-encrypting 500 MB
    1.390 seconds

ioping: seek rate
    min/avg/max/mdev = 93.3 us / 363.1 us / 17.9 ms / 363.8 us
ioping: sequential read speed
    generated 5.03 k requests in 5.00 s, 1.23 GiB, 1.01 k iops, 251.7 MiB/s

I have the same problem when using zsh/sh, with bash it works fine.


bug:

Installation Information
n/a
Describe the bug
"Open GitHub to Report Cody Issue" goes to the wrong URL https://github.com/sourcegraph/sourcegraph/issues/new?template=jetbrains.md

Expected behavior
It should open https://github.com/sourcegraph/jetbrains/issues/new?assignees=&labels=bug%2Cteam%2Fjetbrains&projects=sourcegraph%2F381&template=bug_report.yml&title=bug%3A+
Additional context (logs, images, etc)
See above

good point, thanks


JUnit platform-compatible test descriptor API

JUnit platform has made us aware of additional concepts that we might want to add to our TestDescriptors, e.g. reporting entries and display names. We should think about ways to enhance our current TestDescriptor API to support these. A simple solution might be to just add them and accept that the descriptors are very JVM specific. Alternatively we could make them more generic and hierarchical to support other kinds of testing frameworks.

@oehme It might be worth reopening this issue because, if I understand the topic of this issue correctly, I believe Gradle doesn't yet support printing user-friendly display names for JUnit 5 parameterized tests and dynamic tests.
That being said, I haven't done a search for a separate issue that may already be tracking this, so if that's the case, feel free to ignore me.

Oh, never mind, I believe I found a related issue, which means this issue can remain closed https://github.com/gradle/gradle/issues/5975.


Modem clients don't send mail reliably

From @nzola

The Ethernet Lokole is very stable. It connects at the scheduled Sync time and transfers emails without fail.
The Modem Lokoles behaves the same way.
They don't transfer emails intermittently. Some mail sent to them get lost and never bounce back to the sender. sometimes mail send to them arrives after 24 hrs or couple of days. Sometimes the modem skip the scheduled Sync time. Manual Sync works well, but it does not always transfer emails

@nzola For one or more of the Lokole clients where you've seen the erratic sending behavior, could you send me all the files in the ~/lokole/logs directory?

On Sun, May 12, 2019 at 11:14 AM Clemens Wolff<EMAIL_ADDRESS>wrote:

@nzola https://github.com/nzola For one or more of the Lokole clients
where you've seen the erratic sending behavior, could you send me all the
files in the ~/lokole/logs directory?
—
You are receiving this because you were mentioned.

Watches established.
Setting up watches.
Watches established.
Setting up watches.
Watches established.
Setting up watches.
Watches established.
Setting up watches.
Watches established.
Setting up watches.
Watches established.
Setting up watches.
Watches established.
Setting up watches.
Watches established.
Setting up watches.
Watches established.
Setting up watches.
Watches established.
Setting up watches.
Watches established.
Setting up watches.
restarter.stderr.log

A different Lokole client logs:
On Sun, May 12, 2019 at 11:14 AM Clemens Wolff<EMAIL_ADDRESS>wrote:

@nzola https://github.com/nzola For one or more of the Lokole clients
where you've seen the erratic sending behavior, could you send me all the
files in the ~/lokole/logs directory?
—
You are receiving this because you were mentioned.

Watches established.
Setting up watches.
Watches established.
Setting up watches.
Watches established.
Setting up watches.
Watches established.
restarter.stderr.log (END)

Looks like the behavior happens when there's too much data to sync. A potential solution would be to offload the sync to a separate task runner like celery. Let me look into this a bit more.

Work-in-progress branch: celery-sync

ok Thanks
On Sun, May 12, 2019 at 4:37 PM Clemens Wolff<EMAIL_ADDRESS>wrote:

Looks like the behavior happens when there's too much data to sync. A
potential solution would be to offload the sync to a separate task runner
like celery. Let me look into this a bit more.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ascoderu/opwen-webapp/issues/169#issuecomment-491638690,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEH5MM7GI4FERLADZJAC6QLPVCS3ZANCNFSM4HMGDQTQ
.

@nzola I published a fix for this in version 0.2.0, please take a look and let me know what you think. Note that this will require a full clean re-install of the Lokole.

@nzola To provide some technical details on the changes: we used to run the sync as part of a request to the email app. If the sync takes a long time, the web server will cancel the request which leads the sync to fail. Now we instead run the sync in a separate worker process so the sync can take as much time as it needs.

Ok I will do a full clean install when I return home tonight and test. I
will let you know.
On Mon, May 13, 2019 at 7:27 PM Clemens Wolff<EMAIL_ADDRESS>wrote:

@nzola https://github.com/nzola I published a fix for this in version
0.2.0, please take a look and let me know what you think. Note that this
will require a full clean re-install of the Lokole.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ascoderu/opwen-webapp/issues/169?email_source=notifications&email_token=AEH5MM4YEVQIIS2EVXL2I6LPVIPQBA5CNFSM4HMGDQT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVKCO3Y#issuecomment-492054383,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEH5MM3QC7RXMW4GFH4NO3LPVIPQBANCNFSM4HMGDQTQ
.

Ok. this is great. Increasing the connection time might increase also data
charge for the the customer, but I think the most important is all messages
must transfer.
On Mon, May 13, 2019 at 7:28 PM Clemens Wolff<EMAIL_ADDRESS>wrote:

@nzola https://github.com/nzola To provide some technical details on
the changes: we used to run the sync as part of a request to the email app.
If the sync takes a long time, the web server will cancel the request which
leads the sync to fail. Now we instead run the sync in a separate worker
process so the sync can take as much time as it needs.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ascoderu/opwen-webapp/issues/169?email_source=notifications&email_token=AEH5MM7ASWKX33LCEOSEOC3PVIPVRA5CNFSM4HMGDQT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVKCRAI#issuecomment-492054657,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEH5MM3X3LZSRXUST2M2J5TPVIPVRANCNFSM4HMGDQTQ
.

@nzola The data charge shouldn't increase since we pay for bandwidth usage (megabytes), not time (minutes).

Oh yes. I had forgotten. Thanks!
On Mon, May 13, 2019 at 7:47 PM Clemens Wolff<EMAIL_ADDRESS>wrote:

@nzola https://github.com/nzola The data charge shouldn't increase
since we pay for bandwidth usage (megabytes), not time (minutes).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ascoderu/opwen-webapp/issues/169?email_source=notifications&email_token=AEH5MM3SYSEQNWU6NSIYXX3PVIR2PA5CNFSM4HMGDQT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVKDLOA#issuecomment-492058040,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEH5MM7ON3AL7W5S2OAVFVDPVIR2PANCNFSM4HMGDQTQ
.

@nzola Actually, please use version 0.2.1.


[Bug]: URL state not changed even login pop up is closed

🐛 Describe the bug:
When clicking the Write button on the website, a new popup opens, showing a different URL in the address bar. However, after closing the popup, the main website’s URL does not revert to its original state. Additionally, clicking the Write button does nothing
🔃 Steps To Reproduce:

Go to the website.
Click on the Write button to open a popup window.
Close the popup window and observe the URL on the main website.
Click the Write button again and notice the unintended repeated actions or duplicated behavior.

📃 Expected behavior:

The main website’s URL should reset to its original state when the popup is closed.
Clicking the Write button multiple times should not trigger duplicated or unintended actions.

📸 Screenshots:

Environment details:

Browser: (e.g., Chrome, Firefox, Safari)
Device: (e.g., Desktop, Mobile, Tablet)
Operating System: (e.g., Windows 11, macOS 13)

This will be addressed in the Auth flow migration and currently v2 apis are under progress which are a dependency currently.
Can close this issue


Graph Module Updates

The following assets have been updated to include Graph data ingestion of the "SignInLogs" query:

GraphAPI_data_ingestion.zip (pipeline for ingesting the new query, under pipelines/Extracts).
GraphAPI_py.ipynb (module notebook for processing the data from the new query).

Readmes have also been updated accordingly.

Added new Insights Activity test data


Skeleton behaviors don't validate (filters)

Describe the bug
Vanilla Behavior file for Skeleton doesn't validate as error-free. Could technically be an issue in the code, but I somehow doubt it. Its filters, so... yeah, nested nastiness to validate.
To Reproduce
Steps to reproduce the behavior:

Open VSCode with the plugin installed
Open the Skeleton behavior pack entity file

Expected behavior
No errors on vanilla entities
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):
Windows

This is apparently an old format of filters that is not really supported. I have thus decided to not add support for it. :)

This is apparently an old format of filters that is not really supported. I have thus decided to not add support for it. :)


chore: fix fmt warning.

Please open the P&R to develop branch.

@hantmac I can change the base branch to develop in current PR. Anyway I ceated new PR https://github.com/crawlab-team/crawlab/pull/330


update material community icons

is it possible to update the material community icons files?

I have the same request!
Some of the Icons I need are not present in the current version. Probably there were added after the last update.

Fixed in 4.3.0.

Material Community Icons is now v5.2.45 (At the time I write).
But current v6.6.0 is on Material Community Icons v3.6.95.
As release note said:

Update Material Community Icons to v3.6.95

@oblador Is it possible to update Material Community Icons to v5 for us?


Preliminary ESP32 port

This patch set adds preliminary support for ESP32, both as a SoC, and as a board.  I haven't compiled the documentation yet, but the individual commit messages contain much of what's necessary to build Zephyr for this board. I'm submitting this series now in order to gather feedback and raise awareness in the ESP32 community.
Most of the legwork for an Xtensa port has been made available in previous versions, so basic things such as threads, timers, and synchronization primitives are all working fine.  The philosophers sample is working as expected, for instance.
A lot of things are missing from the port, though, including I/O (no GPIO, I2C, SPI, analog I/O, PWM, etc) and connectivity (WiFi, BT, and BLE).   We're working on these, and I hope to have patches implementing some of them soon.  Connectivity is going to take more work, though.
OpenOCD should work fine (as long as you're using the fork from Espressif).

Rebased and fixed comments.


Feature/home page text

Changed the text of home page

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


conduwuit_git: switch remote to github

:fish: What?

Switches conduwuit_git remote to GitHub from GitLab

:fishing_pole_and_fish: Why?

Conduwuit development is done only on GitHub
GitLab, git.gay, Codeberg, sr.ht, etc are only mirrors that I manually push to, and have admittedly forgotten to push to for at most a few days
Our CI only works on GitHub until I can get a GitLab Runner setup (https://github.com/girlbossceo/conduwuit/issues/160)

:fish_cake: Pending

[ ] Complain with linter;
[ ] Remove some temporary fix;
[ ] Publishing to news' channel.

Thanks! :>


fix(requirements): add support for non resource url rules

Description

Adds support for NonResourceURL rules as CSV requirements
Adds CRD served version CSV requirement check

Fixes: ALM-755 and ALM-756

/assign @alecmerdler

Tested with this patch against olm master and it's working great :+1:

/retest

/test e2e-aws

/approve


fix: detection of zombie dind_add_host script

Summary
Update the make lambdas target so that it can correctly
identify zombie and reaped dind_add_host.sh script
processes so that they are restarted.
Prior to this change, a <defunct> dind_add_host.sh was
considered running.

tested and the base script is still working. i didn't run into the defunct dind issue but we can iterate if this still doesn't catch that scenario, so lets give it a try 🚀 ✅

I was seeing it on my end when the devcontainer was restarted after a reboot.
An easy way to test is to kill the dind_add_host.sh process, which will leave it in a <defunct> state (since docker events is the parent process) and then run make lambdas again.


docs(Prototypes): add example integration with redux-form

This PR adds new page with prototypes and integrations, other integrations will be added, too.

Codecov Report

Merging #3203 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3203   +/-   ##
=======================================
  Coverage   99.92%   99.92%
=======================================
  Files         169      169
  Lines        2790     2790
=======================================
  Hits         2788     2788
  Misses          2        2

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 0b34d9b...96d7586. Read the comment docs.

Released in<EMAIL_ADDRESS>


removed out of scope test data

Codecov Report

Merging #136 into master will increase coverage by 0.35%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #136      +/-   ##
==========================================
+ Coverage      87%   87.35%   +0.35%
==========================================
  Files          13       13
  Lines        1977     1977
  Branches      371      371
==========================================
+ Hits         1720     1727       +7
+ Misses        134      127       -7
  Partials      123      123

Impacted Files
Coverage Δ

wqio/viz.py
89.94% <0%> (+3.91%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4f43a09...9b99690. Read the comment docs.


[firebase_crashlytics] File names are incorrect on Android (still an issue?)

Pretty sure this is still an issue ...
https://github.com/FirebaseExtended/flutterfire/issues/80
If not, which version was it fixed in, or what needs to be done differently to prevent recording errors in .java files?
I'm using: firebase_crashlytics: ^2.0.6

Hi @carman247
Could you please try upgrading to the latest firebase_crashlytics: ^2.2.1?
Thank you

Hi @carman247
Could you please try upgrading to the latest firebase_crashlytics: ^2.2.1?
Thank you

Ok, will upgrade and report back

I've tested using 2.2.1 in release mode and still getting errors reported as java files instead of dart.

Seeing this as well. Since https://github.com/FirebaseExtended/flutterfire/issues/80 is locked this can be tracked here as a continuation.

@carman247, are you able to provide steps to reproduce this behaviour? Perhaps in the firebase_crashlytics/example project. I'm seeing dart file extensions in my crash reports.

The project I am working on is using
  firebase_core: ^1.6.0
  firebase_crashlytics: ^2.2.1

and one example I copy from crashlytics is (with some code change due to pnc)
Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: Null check operator used on a null value. Error thrown Instance of 'ErrorDescription'.
       at State.context(State.java:1095)
       at _EntryPage.initState.<fn>(initState.java:33)
       at Utils.afterBuild.<fn>(afterBuild.java:94)
       at SchedulerBinding._invokeFrameCallback(SchedulerBinding.java:1144)
       at SchedulerBinding.handleDrawFrame(SchedulerBinding.java:1090)
       at SchedulerBinding._handleDrawFrame(SchedulerBinding.java:998)

I have also updated my project from fabric to firebase .. I'll try and get some more information added today about how I am implementing crashlytics/firebase.
Could updating from fabric to crashlytics, and some lingering references be what's causing the problem?

Hi @russellwheatley,
Following your recommendation I tested the firebase_crashlytics/example.
Works on debug mode :

but NOT on release :

Debut mode show correct class and ligne number :

Release mode show correct line number but no class and replace 'dart' with 'java' (Other crash may differ more)

flutter doctor -v
[✓] Flutter (Channel stable, 2.5.2, on macOS 11.6 20G165 darwin-x64, locale en-GB)
    • Flutter version 2.5.2 at /Users/bounty1342/fvm/versions/stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 3595343e20 (30 hours ago), 2021-09-30 12:58:18 -0700
    • Engine revision 6ac856380f
    • Dart version 2.14.3

  firebase_crashlytics: ^2.2.2
  firebase_core: ^1.7.0

This is certainly why there is also issues with obfuscation.
This is a really annoying issue.

flutter build appbundle --release --obfuscate --split-debug-info=build/app/outputs/symbols
produce obfuscated code that Firebase can't handle:

Previous issue similar to this :
https://github.com/FirebaseExtended/flutterfire/pull/4407
Btw on @untp screenshot it also show java classes instead of dart:
https://github.com/FirebaseExtended/flutterfire/pull/4407#issuecomment-815945809
https://github.com/FirebaseExtended/flutterfire/pull/4407#issuecomment-815605757This PR explain why the .java behavior but it should be made clear on the docs as a warning. (People expect dart file and I was confuse to see those java...)
Finally, the PR regex dosent seem to match with this :
. #00 abs 0 virt<PHONE_NUMBER>1cb0af _kDartIsolateSnapshotInstructions+0xe660f (.java)
Hopefully i'm wrong, but it seems the previous PR was incomplete. Hope this help.
Regards

I reproduced the issue above where it worked in debug but not in release.
I used this simple code (and copied firebase_crashlytics/lib/src/utils.dart to project directory for testing getStackTraceElements):
import 'dart:async';
import 'dart:convert';

import 'package:firebase_core/firebase_core.dart';
import 'package:firebase_crashlytics/firebase_crashlytics.dart';
import 'package:flutter/material.dart';

import 'utils.dart';

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp();
  FirebaseCrashlytics.instance.recordError('Error object', StackTrace.current);
  print(jsonEncode(getStackTraceElements(StackTrace.current)));
}

Debug mode:

Release mode:

Obfuscated release mode:

Deobfuscation: #0      main (package:crashlytics_example/main.dart:13:71)
print(jsonEncode(getStackTraceElements(StackTrace.current))) output:
Debug mode: [{"file":"package:crashlytics_example/main.dart","line":"14","method":"main"}]
Release mode: [{"file":"package:crashlytics_example/main.dart","line":"14","method":"main"}]
Json encoded getStackTraceElements returns same output both in debug and release. So the problem is not caused from this package. It is probably in the backend.
Deobfuscation can be done with https://github.com/FirebaseExtended/flutterfire/issues/2644#issuecomment-746217634.
I also filed an issue to dart sdk (dart-lang/sdk#47357), so we can directly deobfuscate without editing any lines.

It hard to keep deobfuscing by hand for apps in production.
Is there any configuration that will prevent this issues or alternative setup ?
On top of it, every version produce a new set of error, and have to switch better symbols...
This make Crashlytics unfit for production app atm...

Any update on this?

@4ntoine - I'm still in communication. Will update when I have something to report.

Quick update - Firebase support was able to reproduce and will look to get this fixed. I was told to keep an eye out for future releases/release notes 👌

Hey folks, I haven't noticed anything in the release notes, but I believe this issue has now been resolved. Could someone please confirm that the correct file extension is now displayed in the Crashlytics console, please 🙏 ?

Still having the issue

This one should stay open.
@russellwheatley, can you check with Firebase support what's the exact status for this issue on their side ?
Thanks

@bounty1342 reopened. Firebase support said to keep an eye on release notes for changes in status. No changes so far I'm afraid.

Since version 2.9.0 this should not be an issue anymore:
FEAT: Send Flutter Build Id to Crashlytics to get --split-debug-info working

Please reopen if needed.


ProgressBar ShowProgressText not implemented in FluentTheme

I made a Window containing a ProgressBar. My application was using the FluentTheme (which is default for both application templates). I set the property 'ShowProgressText' to true. My progress bar was updating correctly, but no text showed up.
I was wondering why it wasn't working. Eventually I found out that the ControlTemplate was different for Default and Fluent theme:
Default theme (src/Avalonia.Themes.Default/ProgressBar.xaml)
<ControlTemplate>
  <Grid>
    <Border Background="{TemplateBinding Background}" BorderBrush="{TemplateBinding BorderBrush}" BorderThickness="{TemplateBinding BorderThickness}" CornerRadius="{TemplateBinding CornerRadius}">
      <Panel>
        <Border Name="PART_Indicator" Background="{TemplateBinding Foreground}" IsVisible="{Binding !IsIndeterminate, RelativeSource={RelativeSource TemplatedParent}}"/>
        <Border Name="PART_IndeterminateIndicator" Background="{TemplateBinding Foreground}" IsVisible="{Binding IsIndeterminate, RelativeSource={RelativeSource TemplatedParent}}"/>
      </Panel>
    </Border>
    <LayoutTransformControl HorizontalAlignment="Center" VerticalAlignment="Center" IsVisible="{Binding ShowProgressText, RelativeSource={RelativeSource TemplatedParent}}" Name="PART_LayoutTransformControl">
      <TextBlock Foreground="{DynamicResource ThemeForegroundBrush}" Text="{Binding Value, RelativeSource={RelativeSource TemplatedParent}, StringFormat={}{0:0}%}" />
    </LayoutTransformControl>
  </Grid>
</ControlTemplate>

Fluent Theme (src/Avalonia.Themes.Fluent/Controls/ProgressBar.xaml)
<ControlTemplate>
  <Border x:Name="ProgressBarRoot" ClipToBounds="True" Background="{TemplateBinding Background}" BorderBrush="{TemplateBinding BorderBrush}" BorderThickness="{TemplateBinding BorderThickness}" CornerRadius="{TemplateBinding CornerRadius}">
      <Panel>
        <Panel x:Name="DeterminateRoot">
          <Border CornerRadius="{TemplateBinding CornerRadius}" x:Name="PART_Indicator" Margin="{TemplateBinding Padding}" Background="{TemplateBinding Foreground}" />
        </Panel>
        <Panel x:Name="IndeterminateRoot">
          <Border x:Name="IndeterminateProgressBarIndicator" CornerRadius="{TemplateBinding CornerRadius}" Margin="{TemplateBinding Padding}" Background="{TemplateBinding Foreground}" />
          <Border x:Name="IndeterminateProgressBarIndicator2" CornerRadius="{TemplateBinding CornerRadius}" Margin="{TemplateBinding Padding}" Background="{TemplateBinding Foreground}" />
        </Panel>
      </Panel>
  </Border>
</ControlTemplate>

Is this a bug or am I misunderstanding something?

Could you describe how we can reproduce the bug?

I made a small application to demonstrate it AvaloniaProgressBar.zip
In app.xaml comment the following line
<FluentTheme Mode="Light"/>
and change it to
<StyleInclude Source="avares://Avalonia.Themes.Default/DefaultTheme.xaml"/>
As you can see, with the default theme the progressbar contains a '42%' text, with FluentTheme it doesn't

I think the Fluent Theme is actually correct for a few reasons:

Upstream WinUI has no percentage. Fluent is based on upstream
The text brush color can't simply be foreground. It needs to change so it is visible reguardless of progress percent.

If the desire is to add this, I think it should be easily disabled with new property rather than retemplating.
I do realize since default theme has this, it is undesirable to loose the functionality with Fluent. I would argue it shouldn't have been there to begin with though.

@robloo this ShowProgressText was old existing property used only on default theme. When we added Fluent one, this property apparently was ignored. So it worth to add it just for consistency of API.


refact(type): Callback

Pull Request Test Coverage Report for Build 1732

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 63.793%

Totals

Change from base Build 1728:
0.0%

Covered Lines:
101

Relevant Lines:
152

💛  - Coveralls


Add a "preferred mode" option to settings.

When playing a playlist if one video fails to play in embedded mode, the extension will load that and every next video in Youtube TV or Youtube website.
It would be nice to be able to select a preferred mode that the extension will try to force in every video of a playlist.

Once you're on YouTube TV, there's no going back. If you don't like YouTube TV, you can uncheck the option "Play video on YouTube TV if it cannot be embedded". Then when you're playing a playlist and one video fails, you can just skip it.


broadcastUpdatePlugin requires a response header to determine response difference

Library Affected:
workbox-broadcast-cache-update
Browser & Platform:
All
Issue or Feature Request Description:
The broadcastUpdatePlugin will check response headers to determine whether responses are the same. However there is no way to disable this check for when your server doesn't send usable response headers.
I expect this to disable the response header check.
      new workbox.broadcastUpdate.Plugin('api-updates', { headersToCheck: []})

However this code will just assume response are always the same: https://github.com/GoogleChrome/workbox/blob/master/packages/workbox-broadcast-cache-update/utils/responsesAreSame.mjs#L55
Possible solution:
if(!headersToCheck.length) {
  return false;
}

At the top of responsesAreSame

An alterative would be to make the change detection algorithm of this plugin pluggable. That way it doesn't have to rely on response headers if you don't want that.

We do offer a pluggable solution, via the cacheDidUpdate() callback that is fired whenever a cache is written to.
You can implement your own, arbitrarily complex logic inside of that callback, giving you control over both how to determine whether something's "changed" (checking headers, checking response bodies [assuming you clone() the responses first], etc.), as well as what you want to do if a change is detected. The recipe I linked to illustrates one possible custom implementation.
Given the flexibility offered by that custom callback, I don't believe that we would want to change the default behavior of the "official" workbox-broadcast-cache-update plugin, which is fundamentally just one possible, prepackaged cacheDidUpdate() callback implementation.


Add RTEMS TCP/UDP Support

With this PR, the DDS Client (and subsequently micro-ros) can build and run on RTEMS 5.
RTEMS is a Real Time Executive in use in multiple research and space exploration projects (satellites, rovers...).
This is the issue where I kept track of the progress.
https://github.com/micro-ROS/micro_ros_setup/issues/397
Today I managed to run a 1:1 copy of the ping-pong example with 50 Hz ping rate.
RTEMS support is enabled by defining UCLIENT_PLATFORM_RTEMS_BSD_NET.
Both TCP and UDP transports have been tested.

Build status:

Linux
Windows

Build status:

Linux
Windows

Build status:

Linux
Windows

Build status:

Linux
Windows

Thanks @roncapat, let's review it and we can merge it in develop branch

Build status:

Linux
Windows

Thank you so much! :100:

@roncapat we are really interested in your use case. Will you be interested in talking about the purpose / use cases / projects where RTEMS is going to be used along with micro-ROS in our monthly ROS 2 Embedded Working Group?

@pablogs9 of course I am.
Note that currently, this is a low-priority and personal contribution, but is meant to pave the way to internal usage (at Thales Alenia Space Italy, where I currently work) in some robotic testbenches. Let me know more about the meeting at<EMAIL_ADDRESS>(so that I can then reply with my corporate mail).


feat: custom busola extensions

Description
Changes proposed in this pull request:

added proxyHandler to backend (for accessing external APIs without CORS issues)
adjusted busola code to load custom html content and script provided by extension
added feature flag
added example for a custom extension

Related issue(s)
#3497

Definition of done

[x] The PR's title starts with one of the following prefixes:

feat: A new feature
fix: A bug fix
docs: Documentation only changes
refactor: A code change that neither fixes a bug nor adds a feature
test: Adding tests
chore: Maintainance changes to the build process or auxiliary tools, libraries, workflows, etc.

[x] Related issues are linked. To link internal trackers, use the issue IDs like backlog#4567
[x] Explain clearly why you created the PR and what changes it introduces
[x] All necessary steps are delivered, for example, tests, documentation, merging

LGTM

/override tide


Use kube-prometheus-stack signed OCI Helm chart

Changes:

Pull kube-prometheus-stack from oci://ghcr.io/prometheus-community/charts
Enable Cosign verification for the kube-prometheus-stack Helm release

_https://github.com/prometheus-community/helm-charts/pull/2631_


allowed-unsafe-sysctls not working in BootstrapArguments

What happened:
According to the Kubernetes 1.11 documentation
--allowed-unsafe-sysctls 'net.core.rmem_max'

should be a valid kubelet flag.
We're currently passing this into EKS via BootstrapArguments:
--kubelet-extra-args "--allowed-unsafe-sysctls 'net.core.rmem_max,net.core.netdev_max_backlog'"
and are using this k8s deployment
apiVersion: apps/v1beta2
kind: Deployment
...
spec:
...
  template:
    metadata:
...
      annotations:
        security.alpha.kubernetes.io/unsafe-sysctls: net.core.rmem_max=10485760,net.core.netdev_max_backlog=100000

But we don't see any effect when setting the properties:
sysctl: cannot stat /proc/sys/net/core/rmem_max: No such file or directory

What you expected to happen:
sysctl -w net.core.rmem_max=10485760 on the pod should work
How to reproduce it (as minimally and precisely as possible):
See above.
Anything else we need to know?:
Environment:

AWS Region: us-east-1
Instance Type(s): m5.xlarge
EKS Platform version (use aws eks describe-cluster --name <name> --query cluster.platformVersion): eks.1
Kubernetes version (use aws eks describe-cluster --name <name> --query cluster.version): 1.11
AMI Version: ami-0c24db5df6badc35a, also tried ami-0c5b63ec54dd3fc38
Kernel (e.g. uname -a): Linux ... 4.14.88-88.76.amzn2.x86_64 #1 SMP Mon Jan 7 18:43:26 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Do we have the same issue as i do, can you confirm. What did bootstrap.sh actually run on the box?
I put the example from a similar issue in my arg for cloudformation
--kubelet-extra-args '--node-labels=something=hello,somethingelse=bye --register-with-taints=taint1=true'

+ /etc/eks/bootstrap.sh metrictank --kubelet-extra-args ''\''--node-labels=something=hello,somethingelse=bye' '--register-with-taints=taint1=true'\'''
Cluster "kubernetes" set.

Which will only give you:
+ key=--kubelet-extra-args
+ case $key in
+ KUBELET_EXTRA_ARGS=''\''--node-labels=something=hello,somethingelse=bye'
+ shift
+ shift

We're having the same problem when calling bootstrap.sh with, for example:
/etc/eks/bootstrap.sh prod1 --kubelet-extra-args \   "--allowed-unsafe-sysctls 'net.*' \   --kube-reserved cpu=200m,memory=0.5Gi,ephemeral-storage=1Gi \   --system-reserved cpu=200m,memory=0.2Gi,ephemeral-storage=1Gi"
kubelet doesn't run with KUBELET_EXTRA_ARGS at all in this case.

We're seeing this not working, too:
/etc/eks/bootstrap.sh \
...
  --kubelet-extra-args "--allowed-unsafe-sysctls 'net.core.somaxconn'" \
...

The combination of quoting and working around the flapping kublet stuff I describe here got it going:
https://github.com/awslabs/amazon-eks-ami/issues/288#issuecomment-541375091
Though I guess on top of the stuff mentioned there we also had to get our pod security policies right to allow this particular sysctl.

Is there a finalized way that anyone was able to get net.core.rmem_max configured in a pod?

My understanding that the parameter net.core.rmem_max  should only applicable at host(node) level as it is option for Network core due to some parameters are not supported when trying to use namespace level sysctl to configure that. (This also has been mentioned in the doc [1] [2] Only namespaced sysctls are configurable via the pod securityContext within Kubernetes).
According to my testing(I was using amazon-eks-node-1.14-v20200122, ami-0bf3e2c598f50ba82, in us-east-1), to change this parameter, you have to use hostNetwork: true to let Pod to use host network instead of containerized network namespace. Then, run a privileged container to apply your own kernel configuration on the Node:

Option 1: Using sysctl to update net.core.rmem_max
Option 2: Update through filesystem echo '10485760' >  /proc/sys/net/core/rmem_max

But please note that it also will be applied to other applications/running Pods. The change parameter is host wide. You may have to land your Pods by Node label or else to ensure you are running application on worker nodes that with proper kernel parameters.
[1] https://github.com/kubernetes/kubernetes/issues/77546#issuecomment-506885448
[2] https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/#setting-sysctls-for-a-pod
Similar issues

https://groups.google.com/forum/#!topic/docker-dev/kFZdaIxoxbg
https://forums.docker.com/t/how-to-tune-kernel-properties-in-docker-images/25291

Just if somebody face same issue.
I was able to allow net.core.somaxconn changes with following

Args to bootstrap.sh (including some additional)

    --kubelet-extra-args \
        "--kube-reserved cpu=100m,memory=200Mi,ephemeral-storage=512Mi \
        --allowed-unsafe-sysctls=net.core.somaxconn \
        --cluster-dns=<IP_ADDRESS>"

Creating PodSecurityPolicy related doc

---
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
  name: sysctl
spec:
  allowPrivilegeEscalation: false
  allowedUnsafeSysctls:
  - net.core.somaxconn
  defaultAllowPrivilegeEscalation: false
  fsGroup:
    rule: RunAsAny
  runAsUser:
    rule: RunAsAny
  seLinux:
    rule: RunAsAny
  supplementalGroups:
    rule: RunAsAny
  volumes:
  - '*'
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: allow-sysctl
rules:
- apiGroups:
  - policy
  resourceNames:
  - sysctl
  resources:
  - podsecuritypolicies
  verbs:
  - '*'
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  creationTimestamp: "2020-09-03T10:17:28Z"
  name: allow-sysctl
  namespace: ${SOME_NAMESPACE}
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: allow-sysctl
subjects:
- apiGroup: rbac.authorization.k8s.io
  kind: Group
  name: system:serviceaccounts
  namespace: default

Hi All,
I am also facing same issue, I have created PodSecurityPolicy as @maksymivash suggested but still i am not able to set somaxconn through deployment
`---
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
name: sysctl
spec:
allowPrivilegeEscalation: false
allowedUnsafeSysctls:

net.core.somaxconn
defaultAllowPrivilegeEscalation: false
fsGroup:
rule: RunAsAny
runAsUser:
rule: RunAsAny
seLinux:
rule: RunAsAny
supplementalGroups:
rule: RunAsAny
volumes:
'*'

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: allow-sysctl
rules:

apiGroups:

policy
resourceNames:
sysctl
resources:
podsecuritypolicies
verbs:
'*'

apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: allow-sysctl
namespace: my-namespace
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: allow-sysctl
subjects:

apiGroup: rbac.authorization.k8s.io
kind: Group
name: system:serviceaccounts:my-namespace
`

and i have the below annotation in my deployment file, but still i am not able to get this working. Can someone help me out

seems to be resolved now.. instead of annotation setting the required syctl in the pod/deployments security context seems to be doing the job

I have the same problem with v1.18.9-eks-d1db3c :(  I tried even adding annotations..
Should we add this parameter while creating eks cluster?

PodSecurityPolicy

Per https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/#podsecuritypolicy it is deprecated in Kubernetes v1.25. Anyone knows any alternative to this?
Thanks.

Hacky solution
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: node-sysctls
  namespace: kube-system
  annotations:
    kubernetes.io/description: |
      This daemon set configures the kernel parameters required to optimize networking performance.
    kubernetes.io/psp: eks.privileged
spec:
  selector:
    matchLabels:
      name: node-sysctls
  template:
    metadata:
      labels:
        name: node-sysctls
    spec:
      volumes:
        - name: kube-api-access-5hrk8
          projected:
            sources:
              - serviceAccountToken:
                  expirationSeconds: 3607
                  path: token
              - configMap:
                  name: kube-root-ca.crt
                  items:
                    - key: ca.crt
                      path: ca.crt
              - downwardAPI:
                  items:
                    - path: namespace
                      fieldRef:
                        apiVersion: v1
                        fieldPath: metadata.namespace
            defaultMode: 420
      containers:
        - name: shell
          image: docker.io/alpine:3.13
          command:
            - nsenter
          args:
            - '-t'
            - '1'
            - '-m'
            - '-u'
            - '-i'
            - '-n'
            - bash
            - '--'
            - '-c'
            - |
              # We are in the host PID namespace, so we can see the host's /proc so we can set sysctls
              sysctl -w net.core.rmem_max=2500000

              echo "Set sysctls... sleeping"
              tail -f /dev/null
          resources:
            limits:
              cpu: 50m
              memory: 64Mi
            requests:
              cpu: 50m
              memory: 64Mi
          volumeMounts:
            - name: kube-api-access-5hrk8
              readOnly: true
              mountPath: /var/run/secrets/kubernetes.io/serviceaccount
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
          imagePullPolicy: IfNotPresent
          securityContext:
            privileged: true
      hostNetwork: true
      hostPID: true
      hostIPC: true
      terminationGracePeriodSeconds: 1
      tolerations:
        - operator: Exists


docs: added goreleaser to user list

Thanks for gitleaks, its amazing to have it in the pipeline so I can have some extra peace of mind!
Description:
adds goreleaser to the users.md list
Checklist:

[x] Does your PR pass tests?
[x] Have you written new tests for your changes?
[x] Have you lint your code locally prior to submission?

nioce!


node-keyboard doesn't work on Mac OS 10.13.3

I installed node-keyboard on Mac OS 10.13.3 but get below errors when typing anything on the terminal. I am using node v8.9.1, npm 5.5.1
node-keyboard>MIDI not detected. Disabling support.
fs.js:75
    throw new TypeError('"options" must be a string or an object, got ' +
    ^

TypeError: "options" must be a string or an object, got number instead.
    at getOptions (fs.js:75:11)
    at Object.fs.writeFile (fs.js:1261:13)
    at ReadFileContext.fs.readFile [as callback] (/Users/joey/.nvm/versions/node/v8.9.1/lib/node_modules/node-keyboard/lib/index.js:42:23)
    at FSReqWrap.readFileAfterOpen [as oncomplete] (fs.js:420:13)

Hi there. I just tried reinstalling on node 8.93. and npm 5.8.0 on Mac OS 10.13.4 with no issues (I had to remove all node_modules  and npm install again though as the node-gyp modules had to be rebuilt. Can you try removing node_modules and trying again? If that fails, can you try with the latest node and npm (I tried with those also and no issues).

That's correct. Let me try this later today and get back to you

Fixed in 3.9.3 and published. Thanks for reporting @zhaoyi0113!


Add fixtures for flashcache

Add an example set of fixtures for /proc/flashcache handling.
https://github.com/prometheus/procfs/issues/218
Signed-off-by: Ben Kochie<EMAIL_ADDRESS>

Not really planning to work on this.


Wrong year in changelog

The changeling currently has the most recent releases with the wrong year.

@bassrock Thanks. It updates.


creating snap files from another processing pipeline

I would like to process my scATAC data with snaptools and snapatac but, for several reasons, the BAM files I have are in a format which is different from the one required by snaptools (i.e. the cell barcode is not in the read name and it's a RG tag instead). In my BAM files, reads are already deduplicated at cell level (that is, the BAM flag is properly set). I already have counts over binned genome (at 5kb) in a scipy sparse matrix. What would be the best way to convert my matrices into snap format?

Hi there,
There are multiple entry point that you can generate the snap file. The easiest way is to convert the bam file to the format that required by sanptools. Here is the example:
https://github.com/r3fang/SnapATAC/wiki/FAQs#cellranger_output https://github.com/r3fang/SnapATAC/wiki/FAQs#cellranger_output
Best
-Rongxin

On Sep 10, 2019, at 7:50 AM, Davide Cittaro<EMAIL_ADDRESS>wrote:
I would like to process my scATAC data with snaptools and snapatac but, for several reasons, the BAM files I have are in a format which is different from the one required by snaptools (i.e. the cell barcode is not in the read name and it's a RG tag instead). In my BAM files, reads are already deduplicated at cell level (that is, the BAM flag is properly set). I already have counts over binned genome (at 5kb) in a scipy sparse matrix. What would be the best way to convert my matrices into snap format?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/r3fang/SnapTools/issues/16?email_source=notifications&email_token=ABT6GG6XBQ4UEI44PEX7BX3QI6X2ZA5CNFSM4IVIYAC2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HKPDH7Q, or mute the thread https://github.com/notifications/unsubscribe-auth/ABT6GG3WPPQPP5UVFHZY37LQI6X2ZANCNFSM4IVIYACQ.

Yes, I did that as it sounds the only way to go. Still I’d rather not use read-sorted bam (it wastes disk space and time in sorting, IMHO), my BAM files already have barcode names in their header and read groups, so the size of the resulting matrix is known from the start and reads are already D.E. duplicated at cell level.

Just commenting that this is how the new BioRad scATAC protocol works and it would be really great to see support for this in the future!


python310Packages.censys: 2.1.6 -> 2.1.6

Description of changes
https://github.com/censys/censys-python/releases/tag/v2.1.6

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

3 packages built:

python310Packages.censys
python39Packages.censys
theharvester


Git source: doublecheck logging of the source URL

The BitBucket documentation is suggesting to use the username and password in the git clone command here: https://support.atlassian.com/bitbucket-cloud/docs/use-oauth-on-bitbucket-cloud/#Cloning-a-repository-with-an-access-token.
Shipwright users might now take that URL and put it into .spec.source.url of a Build. This might work but we will likely then print the password because we print the command in https://github.com/shipwright-io/build/blob/4c5a50bd493e160d28ea428b4add134c391dea98/cmd/git/main.go#L423. We should make sure to mask this if we find our that a user is doing that.
Assuming credentials work when taken from a secret (see #1132), then we should discourage placing username and password in the URL in general in our docs.

Checking whether I can tackle that with #1176.


Issue #65  Add "Don't show this dialog next time" checkbox to plugin prompt

Addresses #65

I wrote an implementation for the PersistentStateComponent as suggested by @Foso and also added a Configurable where a plugin user would be able to configure their preferences from the plugin’s tab inside the IDE’s preferences window.

@pocmo Hi, any feedback on this?

When the setting is deselected, the Xml is still converted to Compose

@t-regbs Is this fixed in the latest version?

Oh, there's now also a PR with different implementation in #100.

yes that is fixed in the latest version

@pocmo Just checked out the other implementation and it looks good.
Only functional difference is I also added settings for showing the dialog and also turning on or off conversion to compose altogether in Preferences.

Thank you for your work! 👍 I rebased and landed your changes in #106. :)