Create/drop policies

What do you think about adding support for policies and row level security?

I just came up with a macro in case someone else needs it:

    Blueprint::macro('policy', function (
      string $policy,
      array $options = [],
    ) {
      /** @var \Illuminate\Database\Schema\Blueprint $this */
      $prefix = $this->prefix;
      $table = $this->table;

      $command = $this->addCommand(
        'policy',
        compact('prefix', 'table', 'policy', 'options')
      );
    });

    PostgresGrammar::macro('compilePolicy', function (
      Blueprint $blueprint,
      Fluent $command
    ) {
      /** @var \Illuminate\Database\Schema\Grammars\PostgresGrammar $this */
      $prefix = $command->prefix;
      $table = $command->table;
      $policy = $command->policy;
      $options = $command->options;

      $modifiers = [];
      foreach ($options as $key => $value) {
          $modifiers[] = match (true) {
              'as' === $key => "as {$value}",
              'for' === $key => "for {$value}",
              'to' === $key => "to {$value}",
              'using' === $key => "using ({$value})",
              'check' === $key => "with check ({$value})",
              default => throw_if(true, message: "Unknown option '{$key}'."),
          };
      }
      $sqlModifiers = implode(' ', $modifiers);

      return [
        sprintf('CREATE POLICY %s ON %s%s %s', $policy, $prefix, $table, $sqlModifiers),
      ];
    });

And then similar for drop:
    Blueprint::macro('dropPolicy', function (
      string $policy,
    ) {
      /** @var \Illuminate\Database\Schema\Blueprint $this */
      $prefix = $this->prefix;
      $table = $this->table;

      $command = $this->addCommand(
        'dropPolicy',
        compact('prefix', 'table', 'policy')
      );
    });

    PostgresGrammar::macro('compileDropPolicy', function (
      Blueprint $blueprint,
      Fluent $command
    ) {
      /** @var \Illuminate\Database\Schema\Grammars\PostgresGrammar $this */
      $prefix = $command->prefix;
      $table = $command->table;
      $policy = $command->policy;

      return [
        sprintf('DROP POLICY IF EXISTS %s ON %s%s', $policy, $prefix, $table),
      ];
    });

Maybe we can incorporate it in this library as well 😊

I am planning to support RLS, but I don't know yet what the API will look like. I am unsure whether I want to make it look like the SQL syntax or some higher-level API. Also working with RLS within Laravel is not that easy so I am thinking about whether some helpers need to be added to make development easier - and make it a risk-free approach.


⚠ Digital Ocean - https://status.digitalocean.com/ has degraded performance

In 15590d8, Digital Ocean - https://status.digitalocean.com/ (https://status.digitalocean.com/api/v2/status.json) experienced degraded performance:

HTTP code: 200
Response time: 187 ms

Resolved: Digital Ocean - https://status.digitalocean.com/ performance has improved in 21fee8f.


[Internal] Client encryption: Add code to set isClientEncrypted based on property passed in

Description
Use https://github.com/Azure/azure-cosmos-dotnet-v3/pull/1489 to pass info about whether an item is client encrypted to the service.
Changes to invoke this from the Encryption package will be updated to https://github.com/Azure/azure-cosmos-dotnet-v3/pull/1430 once the SDK package with current PR is available to consume.
We send information to the service via this property on write requests with client encryption that indicate that the item is client encrypted. This allows the server to restrict operations such as sproc-based-update or patch on such items that may lead to undefined behavior (for example, if a property with the same path as what is already part of the encrypted payload is added, then upon decryption, we have two plaintext values for the same path and choosing the wrong one may give the impression of a lost update).
Type of change

[ ] New feature (non-breaking change which adds functionality)

Closing since there has been no update for over 30 days. Please re-open if necessary.

Closing since there has been no update for over 30 days. Please re-open if necessary.


Remove various deprecated utilities, methods and classes.

This PR removes:

customer.forms.SetPasswordForm
customer.forms.PasswordChangeForm
views.decorators.staff_member_required
UserAddress.num_orders

I thought about this some more and am now wondering whether we should remove SetPasswordForm and PasswordChangeForm, even though they are copies of the corresponding Django forms. Removing them means it would not longer be possible to customise them through dynamic loading. Maybe it's better just to leave them there?

It is easy enough to override the view or application. I think the better argument for keeping them would be consistency.


Create package template for Node tools

Details
The packages of Node tools installed using npm look very similar and a new template could be added to our create_package script and to our issue template. Current node tools examples:

malware-jail.vm
pkg-unpacker.vm

New tool we could add to test the template:

https://github.com/ben-sb/obfuscator-io-deobfuscator

We should start by adding a function helper

Function helper added, still missing modifying the script, template and CI (GH action to create the package).

I have just realised that we do not need to download the zip to install obfuscator-io-deobfuscator, it is enough with running: npm install -g obfuscator-io-deobfuscator, tracked this in https://github.com/mandiant/VM-Packages/issues/1005


Make EditText selectable when view attached to window

It's been detected that RN's TextInput components within the list, that are shown offscreen when the list is first loaded, do not allow their text to be selected.
Background
On the technical side, apparently the problem with RN’s TextInput should be fixed in this commit https://github.com/facebook/react-native/commit/89340f1620295c7ca6baecccc6b6d3befdf45cdb but we can see it still happens, and for some reason while this code exists for TextView, this modification is not on EditText anymore (see current RN master https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/views/textinput/ReactEditText.java)
(EDIT: the code has been reverted super shortly after in https://github.com/facebook/react-native/commit/862136a398decff8ad5d4509ca51bd6b893ff851#diff-457fd2ba359cc6fbb0c471516e279696, with the apparent intention to get it back in but never did).
As a workaround, this PR makes sure any EditText that's within a list row view hierarchy gets set to selectable if focusable when it gets attached to the window (that is, when it's about to become visible and hence actionable).
To test:
Before:

run the app
observe the word hello in the TextInput  is selectable in the first few rows being shown
scroll the list down (1 screen down is enough, as the problem happens with items that are not visible on first load)
now place the cursor on the TextInput of any of these items and try selecting text. Observe it's not possible.

After:
Repeat the steps above and observe all TextInput is selectable.

I think this PR is probably too old by now to consider. WDYT about closing it @mzorz ?

Closing


Set individual environment variables for build

pack allows setting build-time environment variables via a file, but not
as individual values on the cli. This PR adds the ability to set one (or
more) environment variables directly as cli switches.
The same semantics are preserved from --env-file where a value can be
forwarded from the current environment if a variable name is specified
without a value. The new flags can be used to augment or override
specific values from a file.
The BuildFlags struct now includes an Env field in addition to EnvFile.
The BuildConfig struct EnvFile field has been renamed to Env for
consistency as the field contains the parsed values and not a file.
Refs buildpack/roadmap#25

A little background context.
riff currently uses a riff.toml file to pass configuration to function buildpacks. This file is generated based on values provided to the riff cli. Since this config file is not actually part of the project, it's awkward to write a file to the filesystem, do some work and then remove that file. It would be nicer to specify this config as environment variables.

Merged master and fixed a conflict with build config changes.
cc @ekcasey

@scothis I was under the impression that riff was importing github.com/buildpack/pack as a library using the pack.Build(...) function to run builds. In which case, I would imagine the correct solution for this problem is to add a map of env vars as a  param to pack.Build. In that case riff should be able to construct that map as desired (no file required).
Is riff shelling out to the pack cli? I am not opposed to supporting a --env flag but to better enable library consumers it's important to us to know where users are integrating. In the near future we plan to make everything except a deliberately exposed library internal and thus not importable.

@ekcasey yes, riff embeds pack rather than shelling out. On its own, this PR is not enough to fully solve riff's needs, but it provides a large step towards scratching that itch. I'll open another PR that takes a baby step towards creating a programatic API that exposes the same capabilities.
This PR is updated to resolve conflicts.

@scothis Thanks for the explanation. If we think cli users will value having a --env flag in addition to an --env-file, flag this is a good step. I think the only thing missing here is acceptance test coverage. If we are exposing a new flag we should add coverage in acceptance/acceptance_test.go, just like we do with --env-file.

@ekcasey added an acceptance test and manually verified that all the tests are actually passing


Help troubleshooting, script is not affecting iFrames on our site

Hi, not sure if this is best place to ask for help but I'm trying to figure out why lazysizes is not working for us at https://razzball.com. Trying to get the carousel slider at the top to lazy load but it appears that all iframes in the carousel are loading at page load.
We have:

Installed the script in the js folder
Loaded the script in functions.php
Put "" in the site header
Added the class="lazyload" tag in the iFrame code after the src.

We're using the Brid.TV iframe player and the Slide Anything slider plugin with pop up windows; appears that SA does not see the lazy loading, wanted to see if anyone had any ideas or a workaround!
Thanks!

You have to change the src attribute to data-src.

I think that might've done it, thank you! Will check our bandwidth stats tomorrow to confirm, but slide is loading much faster now.


Change zone parsing to accept non-trailing newline

So, basically what this change does is not make the zone parser require a newline to delimit the record. I'm ok with it. I don't particulary like the static variable, but the parser isn't thread-safe anyway, so I'd be fine with this getting merged. @wcawijngaards, @wtoorop, any comments?

I do not see any issues with it, if that works for non-newline-ended files, that is nice.

@TCY16, can you update the changelog too? After that, I think we can go ahead and merge this.

@TCY16, Changelog?


chore(deps): regenerate package-lock.json

Intent

Fix dependencies installation for sasjs-tests.

Implementation

Regenerated package-lock.json using Node v16.13.0 and npm 8.1.0.

Checks
No PR (that involves a non-trivial code change) should be merged, unless all items below are confirmed!  If an urgent fix is needed - use a tar file.

[x] All sasjs-cli unit tests are passing (npm test).
[ ] All sasjs-tests are passing (instructions available here).
[ ] Data Controller builds and is functional on both SAS 9 and Viya

npm i didn't work


Add nbt interact method

It adds a method to get a cardinal data tag, where we can add/read stuff from an item, also, item mods is updated to use it, and some missing attributes and elements have been added in item mods (can place on, can destroy and show flags)

merged


Dockerfile: add ca-certificates

PR #1073 removed ca-certificates  from  the runtime image. However, it is still required.
screenshot:

I have read the CLA Document and I hereby sign the CLA

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.08%) to 31.594%

Totals

Change from base Build<PHONE_NUMBER>:
-0.08%

Covered Lines:
13031

Relevant Lines:
14791

💛  - Coveralls


Change tooltip placement to auto (SCRD-7643)

prevents the "tooltip flash" on certain pages. Does mean that tooltip placement is now dynamic and will not default to the same position for everything, but seems a reasonable tradeoff.

LGTM


batch: Execute root fragment task in frontend.

Currently the root fragment of mpp query is executed in compute node. It would be better to move it to frontend to reduce schedule and pull data latency.

There are two cases:

the root fragment is simply a single distribution exchange operator. It will be scheduled at the frontend.
the root fragment has other non-exchange operators. I think we may still schedule them at the compute nodes.

Totally agree. By the way, the plan generated by optimizers should always satisfies

Either, it has a singleton fragment on the top e.g. in the cases of Global Agg/TopN
Or, it has a singleton exchange on the top to gather data together

For 2, there are two cases:

2.1 No table scan, for example select 1+ 2
2.2 Singleton table scan, for example select * from t where a = 1 and a is a key of t.

Obviously 2.1 can be scheduled on frontend, while 2.2 can't.
For 2.2 I would suggest to add a singleton exchange on top of table scan so that all three cases can be executed in same way, and we don't need to maintain another code branch for execution.

For 2.2 I would suggest to add a singleton exchange on top of table scan so that all three cases can be executed in same way, and we don't need to maintain another code branch for execution.

+1, but we already had one.
dev=> explain select l_orderkey,l_linenumber from lineitem where l_orderkey = 10;
                               QUERY PLAN
------------------------------------------------------------------------
 BatchExchange { order: [], dist: Single }
   BatchFilter { predicate: ($0 = 10:Int32) }
     BatchScan { table: lineitem, columns: [l_orderkey, l_linenumber] }
(3 rows)


synonym request "breakdown"

"breakdown" is currently an exact synonym of "catalytic process.
This makes the Europe PMC text miners flag every instance of "breakdown" as "catalytic process.
I'd like to edit this  synonym to be "breakdown of substance", make it related, or remove it altogether.

This may be a tangent here, but breakdown should include spontaneous reactions that proceed without enzyme-mediated catalysis, like a number of physiologically important steps in eicosanoid metabolism, so will your edit fix the root problem?

I guess that makes it even broader.
Is it a useful synonym? I can only see it being useful if it is in the context of a specific compound, so "x compound" would be useful, but  "catabolic process" is a high-level grouping term anyway.
(@pgaudet  not, don't worry I don't intend to do this for every problem synonym for text mining but this one has been bugging me for a couple of years when I have reviewed because it's a straightforward fox to remove a lot of obvious nonsense, and I don't think a curator would miss this label)

Would "breakdown of substance" (or breakdown of molecule) be enough to avoid it being picked up by text mining tools?

I think so because they stopped doing partial string matches (or appeared to, but if not I will raise that issue again when I cheat with Europe PMC)

Sounds good, then go ahead and change it.

@ValWood I assume you meant 'catabolic process' , not catalytic process.


Issue: Timeout Error When Running Super Stream Example on RabbitMQ 3.11

Describe the bug
Hi,
I've set up RabbitMQ with the following command:
docker run -d --name rabbitmq -p 5552:5552 -p 15672:15672 -e RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS='-rabbitmq_stream advertised_host localhost -rabbit loopback_users "none"' rabbitmq:3.11.7-management
Additionally, I enabled the stream management plugin:
docker exec rabbitmq rabbitmq-plugins enable rabbitmq_stream_management
I’m attempting to run the super stream producer example from the repository:
examples/super_stream/producer/super_stream_producer.go
However, I keep encountering this error:
Super stream example - partitions
Connecting to RabbitMQ streaming ...
2024/09/25 10:08:27 [error] - timeout 10000 ns - waiting Code, operation: Command not handled 29, - invoices
timeout 10000 ms - waiting Code, operation: Command not handled 29, - invoices

Interestingly, the example works as expected when I upgrade RabbitMQ to version 3.13.
Am I missing any specific configuration for RabbitMQ 3.11, or is something else?
Thank you in advance for your help!

Additional context
No response

You need RabbitMQ 3.13.0 to create and delete the super-stream via client API
I added a check here: https://github.com/rabbitmq/rabbitmq-stream-go-client/pull/355

Before RabbitMQ 3.13.0, you need to use the command line tool to create a super stream.
3.11.x is an old version. I would suggest updating the server :)!


Enhancement: Automatically install bootstrap Go version (go1.4)

Automatically install the boostrap version of Go (go1.4) on behalf of the user, to make the setup process easier.

Duplicate of #204


chore: add issue template for feature requests

What this PR changes/adds
Adds an issue template for feature requests and provides a link to blank issues.
Why it does that
To make people's lives easier.
Linked Issue(s)
Closes #841
Checklist

[x] added relevant details to the changelog? (skip with label no-changelog)
[x] linked GitHub project? (see the section on the right-hand side -->)

Codecov Report

Merging #854 (83d8426) into main (b18a897) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main     #854   +/-   ##
=========================================
  Coverage     59.95%   59.95%
+ Complexity     2237     2236    -1
=========================================
  Files           600      600
  Lines         12992    12992
  Branches        907      907
=========================================
  Hits           7790     7790
  Misses         4777     4777
  Partials        425      425

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 b18a897...83d8426. Read the comment docs.


Allow re-balancing through an API

We need to be able to re-balance our channels.
Not sure what the best approach is but we will need this in the future.

I suggest we create an invoice with an outbound and an inbound routing hint. Shouldn't be too complicated.

I suggest we create and pay an invoice with an outbound and an inbound routing hint. Shouldn't be too complicated.

I've implemented it this way but keep getting "no route found" errors when paying the invoice. Are we sure that this is how it should work?

It looks like this is currently not possible as constructing a route to ourselves is not allowed:
https://github.com/lightningdevkit/rust-lightning/blob/ec928d55b480254f2ce3457a5c219ed115fdf9ef/lightning/src/routing/router.rs#L1498-L1500

Draft can be found here: https://github.com/get10101/10101/compare/feat/rebalance?expand=1

Unassigning myself from this and seeking help from LDK-team


ECONNRESET not triggering error event on connection

The following error is being thrown when our database fails over to a backup instance. Our first attempt to handle the error was to listen for error on each connection. However, this particular error is not being emitted on the connection, so our listener is never being invoked for us to handle.
Unfortunately, we're stuck on 2.0.1 (because we're stuck on a fork of Sequelize 1.6.0-beta4). Does anyone have any guidance on why this exception is being thrown and not emitted on the connection object?
Error: read ECONNRESET
    at errnoException (net.js:905:11)
    at TCP.onread (net.js:559:19)
    --------------------
    at Protocol._enqueue (/opt/apps/shutterstock-absinthe/deployment/node_modules/mysql/lib/protocol/Protocol.js:110:26)
    at Connection.query (/opt/apps/shutterstock-absinthe/deployment/node_modules/mysql/lib/Connection.js:148:25)
    at module.exports.Query.run (/opt/apps/shutterstock-absinthe/deployment/node_modules/sequelize/lib/dialects/mysql/query.js:26:17)
    at module.exports.execQueueItem (/opt/apps/shutterstock-absinthe/deployment/node_modules/sequelize/lib/dialects/mysql/connector-manager.js:226:21)
    at /opt/apps/shutterstock-absinthe/deployment/node_modules/sequelize/lib/dialects/mysql/connector-manager.js:180:25
    at adjustCallback (/opt/apps/shutterstock-absinthe/deployment/node_modules/sequelize/node_modules/generic-pool/lib/generic-pool.js:187:7)
    at dispense (/opt/apps/shutterstock-absinthe/deployment/node_modules/sequelize/node_modules/generic-pool/lib/generic-pool.js:211:9)
    at Object.me.acquire (/opt/apps/shutterstock-absinthe/deployment/node_modules/sequelize/node_modules/generic-pool/lib/generic-pool.js:260:5)
    at module.exports.enqueue (/opt/apps/shutterstock-absinthe/deployment/node_modules/sequelize/lib/dialects/mysql/connector-manager.js:171:19)
    at module.exports.ConnectorManager.query (/opt/apps/shutterstock-absinthe/deployment/node_modules/sequelize/lib/dialects/mysql/connector-manager.js:69:15)
    at module.exports.Sequelize.query (/opt/apps/shutterstock-absinthe/deployment/node_modules/sequelize/lib/sequelize.js:149:34)
    at null.fct (/opt/apps/shutterstock-absinthe/deployment/node_modules/sequelize/lib/query-interface.js:256:38)
    at null._onTimeout (/opt/apps/shutterstock-absinthe/deployment/node_modules/sequelize/lib/emitters/custom-event-emitter.js:15:16)
    at Timer.listOnTimeout [as ontimeout] (timers.js:112:15)

Hi! This is just how this module works, unfortunately: when the error occurs during a command (.query in the case of that stack trace), we do not emit the error on the connection, but rather only as the err to the callback function in your .query call.
We could potentially add support to also emit the error on the connection if you have a listener attached, but that won't help you, since you'd have to upgrade the mysql module.

My first attempt was to use the validate callback on the pool. Sequelize is using generic-pool, which has a validate hook that can declare a connection dead before it's acquired from the pool. However, the validate method must be synchronous and I believe connection.ping() is about the only way to truly validate the connection.
Right now I'm looking into monkey-patching the connection's query method to emit any error event on the connection as well.


What is the plan of Enarx release?

From enarx created by xiaonan-INTC: enarx/enarx#922
Hi, dear Enarx developers and maintainers,
Will Enarx plan to have some release versions or candidates or even tags (like v1.0, etc.) with kernel patch, source code, binaries, installation packages, test cases, documentation, etc.?
We want to do some development on Enarx with Intel SGX, but we saw Enarx updates and changes very frequently, and no stable and mature production for development and validation.
Thanks a lot!

@xiaonan-INTC
Our strategy is to have four components:

keepldr
wasmldr
keepmgr
client

Of these four, the most difficult to build is the keepldr. The good news is that we (just today) split it out of the https://github.com/enarx/enarx repo into the https://github.com/enarx/enarx-keepldr repo. The reason for this move is that we are preparing for an alpha release (without attestation).
We also have proofs-of-concept for the other components which we hope to merge into their own repos in the coming weeks. The easiest way to get things going today is to build enarx-keepldr. Apart from installing a few dependencies and the musl target, this should be pretty straightforward (as of today).
Does this answer your question?
cc @MikeCamel

Sorry to reopen this issue, @npmccallum
Another question, does Enarx alpha release have crate to support Intel SGX? And are there any SGX related test cases?

@xiaonan-INTC - we definitely plan to support SGX as part of the wasmldr crate.

@xiaonan-INTC
Our strategy is to have four components:

keepldr
wasmldr
keepmgr
client

Of these four, the most difficult to build is the keepldr. The good news is that we (just today) split it out of the https://github.com/enarx/enarx repo into the https://github.com/enarx/enarx-keepldr repo. The reason for this move is that we are preparing for an alpha release (without attestation).
We also have proofs-of-concept for the other components which we hope to merge into their own repos in the coming weeks. The easiest way to get things going today is to build enarx-keepldr. Apart from installing a few dependencies and the musl target, this should be pretty straightforward (as of today).
Does this answer your question?
cc @MikeCamel

thanks a lot @npmccallum , very expect Enarx alpha release, :)

@xiaonan-INTC You can see an example of an SGX test run here: https://github.com/enarx/enarx-keepldr/runs/1095551646?check_suite_focus=true

@xiaonan-INTC Yes. You can checkout enarx-keepldr and run ENARX_BACKEND=sgx cargo test. That will force it to run the tests on SGX.

@xiaonan-INTC Yes. You can checkout enarx-keepldr and run ENARX_BACKEND=sgx cargo test. That will force it to run the tests on SGX.

Thanks a lot @npmccallum
But I tried your command line and got the same error as issue 10.

Dear @npmccallum
Sorry to trouble,
What is the progress of Enarx re-structing and when do you paln to release alpha?
And will Enarx have an entry of building and running with readme since it will be split into 4 components?


Remove core-js polyfills

Automatically including polyfills can lead to a number of issues:

An application may already be polyfilling some features - leading to duplication/bloat.
An application may only be supporing browsers which support a particular feature, making the polyfill unnecessary weight.
An application may inadvertently rely on polyfill brought in by a library - and then be confused about why the feature no longer works after removing the library.

Another alternative might be to provide both a build with the polyfills and a build without them (which would require the application to provide and manage the polyfills).
Thanks!

I haven't investigated enough, but I am seeing the polyfills cause problems with a project we have using ImmutableJS on some browsers including IE11. I would say this is even more serious than the original suggestion.

We are in the process of deprecating, then removing polyfills from Helmet.  Should address this and #111

Fixed in<EMAIL_ADDRESS>

Thanks very much, this is great!


Poor write performanc on 1G interface

Setup
Tow consuming nodes are connect via 1G interface through switch, which then connected to longhorn nodes via 20G(aggregated) interface.
We have verifed that consuming nodes are able to perform stable 100MB/s connections to longhorn nodes.  However, when perform FIO on longhorn backed volumes, the performmance look unexpectedly bad. Only sequre read looks acceptable. Below is our test report:
Sequence Read：
fio -filename=/dev/vda -direct=1 -iodepth 1 -thread -rw=read -ioengine=psync -bs=16k -size=2G -numjobs=10 -runtime=60 -group_reporting -name=lhtest

Result：
Jobs: 10 (f=10): [R(10)][100.0%][r=47.0MiB/s,w=0KiB/s][r=3009,w=0 IOPS][eta 00m:00s]
lhtest: (groupid=0, jobs=10): err= 0: pid=26614: Mon Sep 21 17:36:41 2020
   read: IOPS=8663, BW=135MiB/s (142MB/s)(8125MiB/60019msec)
    clat (usec): min=87, max=1515.4k, avg=1149.51, stdev=16354.33
     lat (usec): min=88, max=1515.4k, avg=1150.31, stdev=16354.33
    clat percentiles (usec):
     |  1.00th=[    100],  5.00th=[    108], 10.00th=[    113],
     | 20.00th=[    118], 30.00th=[    123], 40.00th=[    127],
     | 50.00th=[    141], 60.00th=[    151], 70.00th=[    206],
     | 80.00th=[    709], 90.00th=[   1336], 95.00th=[   2278],
     | 99.00th=[  16712], 99.50th=[  21103], 99.90th=[  62129],
     | 99.95th=[ 123208], 99.99th=[1082131]
   bw (  KiB/s): min=   31, max=146016, per=11.04%, avg=15303.88, stdev=29146.40, samples=1087
   iops        : min=    1, max= 9126, avg=956.46, stdev=1821.66, samples=1087
  lat (usec)   : 100=0.92%, 250=70.03%, 500=3.97%, 750=5.92%, 1000=5.60%
  lat (msec)   : 2=7.92%, 4=1.80%, 10=2.09%, 20=1.22%, 50=0.40%
  lat (msec)   : 100=0.08%, 250=0.03%, 500=0.01%, 750=0.01%, 1000=0.01%
  cpu          : usr=0.39%, sys=2.03%, ctx=520008, majf=0, minf=54
  IO depths    : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     issued rwts: total=519988,0,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=1

Run status group 0 (all jobs):
   READ: bw=135MiB/s (142MB/s), 135MiB/s-135MiB/s (142MB/s-142MB/s), io=8125MiB (8519MB), run=60019-60019msec

Disk stats (read/write):
  vda: ios=518537/0, merge=447/0, ticks=582700/0, in_queue=584438, util=99.74%

Sequence Write：
fio -filename=/dev/vda -direct=1 -iodepth 1 -thread -rw=write -ioengine=psync -bs=16k -size=2G -numjobs=10 -runtime=60 -group_reporting -name=lhtest

Result：
Jobs: 10 (f=10): [W(10)][100.0%][r=0KiB/s,w=2530KiB/s][r=0,w=158 IOPS][eta 00m:00s]
lhtest: (groupid=0, jobs=10): err= 0: pid=26635: Mon Sep 21 17:38:12 2020
  write: IOPS=170, BW=2732KiB/s (2797kB/s)(160MiB/60057msec)
    clat (msec): min=4, max=171, avg=58.54, stdev= 8.60
     lat (msec): min=4, max=171, avg=58.54, stdev= 8.60
    clat percentiles (msec):
     |  1.00th=[   57],  5.00th=[   57], 10.00th=[   57], 20.00th=[   57],
     | 30.00th=[   58], 40.00th=[   58], 50.00th=[   58], 60.00th=[   58],
     | 70.00th=[   58], 80.00th=[   58], 90.00th=[   58], 95.00th=[   64],
     | 99.00th=[   97], 99.50th=[  109], 99.90th=[  171], 99.95th=[  171],
     | 99.99th=[  171]
   bw (  KiB/s): min=  192, max=  288, per=10.00%, avg=273.08, stdev=19.18, samples=1200
   iops        : min=   12, max=   18, avg=16.98, stdev= 1.24, samples=1200
  lat (msec)   : 10=0.02%, 20=0.02%, 50=0.05%, 100=99.07%, 250=0.84%
  cpu          : usr=0.02%, sys=0.07%, ctx=10267, majf=0, minf=14
  IO depths    : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     issued rwts: total=0,10254,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=1

Run status group 0 (all jobs):
  WRITE: bw=2732KiB/s (2797kB/s), 2732KiB/s-2732KiB/s (2797kB/s-2797kB/s), io=160MiB (168MB), run=60057-60057msec

Disk stats (read/write):
  vda: ios=40/10230, merge=0/0, ticks=48/598637, in_queue=591717, util=98.82%

Random Write：
fio -filename=/dev/vda -direct=1 -iodepth 1 -thread -rw=randwrite -ioengine=psync -bs=16k -size=2G -numjobs=10 -runtime=60 -group_reporting -name=lhtest

Result：
Jobs: 10 (f=10): [w(10)][100.0%][r=0KiB/s,w=2642KiB/s][r=0,w=165 IOPS][eta 00m:00s]
lhtest: (groupid=0, jobs=10): err= 0: pid=26669: Mon Sep 21 17:39:30 2020
  write: IOPS=163, BW=2619KiB/s (2682kB/s)(154MiB/60059msec)
    clat (msec): min=8, max=259, avg=61.06, stdev=13.08
     lat (msec): min=8, max=259, avg=61.06, stdev=13.08
    clat percentiles (msec):
     |  1.00th=[   45],  5.00th=[   52], 10.00th=[   54], 20.00th=[   56],
     | 30.00th=[   60], 40.00th=[   60], 50.00th=[   61], 60.00th=[   61],
     | 70.00th=[   61], 80.00th=[   66], 90.00th=[   67], 95.00th=[   72],
     | 99.00th=[   95], 99.50th=[  182], 99.90th=[  218], 99.95th=[  236],
     | 99.99th=[  259]
   bw (  KiB/s): min=  128, max=  320, per=10.00%, avg=261.83, stdev=25.76, samples=1200
   iops        : min=    8, max=   20, avg=16.30, stdev= 1.64, samples=1200
  lat (msec)   : 10=0.06%, 20=0.26%, 50=3.62%, 100=95.19%, 250=0.84%
  lat (msec)   : 500=0.02%
  cpu          : usr=0.01%, sys=0.07%, ctx=9850, majf=0, minf=11
  IO depths    : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     issued rwts: total=0,9831,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=1

Run status group 0 (all jobs):
  WRITE: bw=2619KiB/s (2682kB/s), 2619KiB/s-2619KiB/s (2682kB/s-2682kB/s), io=154MiB (161MB), run=60059-60059msec

Disk stats (read/write):
  vda: ios=0/9809, merge=0/3, ticks=0/598869, in_queue=588247, util=98.11%

Mix Random READ/Write：
fio -filename=/dev/vda -direct=1 -iodepth 1 -thread -rw=randrw -rwmixread=70 -ioengine=psync -bs=16k -size=2G -numjobs=10 -runtime=60 -group_reporting -name=lhtest

result：
Jobs: 10 (f=10): [m(10)][100.0%][r=3795KiB/s,w=1873KiB/s][r=237,w=117 IOPS][eta 00m:00s]
lhtest: (groupid=0, jobs=10): err= 0: pid=26693: Mon Sep 21 17:40:46 2020
   read: IOPS=253, BW=4058KiB/s (4155kB/s)(238MiB/60041msec)
    clat (usec): min=251, max=161389, avg=20886.03, stdev=13782.05
     lat (usec): min=252, max=161390, avg=20886.97, stdev=13782.03
    clat percentiles (msec):
     |  1.00th=[    3],  5.00th=[    4], 10.00th=[    6], 20.00th=[    9],
     | 30.00th=[   12], 40.00th=[   16], 50.00th=[   20], 60.00th=[   24],
     | 70.00th=[   27], 80.00th=[   32], 90.00th=[   38], 95.00th=[   43],
     | 99.00th=[   56], 99.50th=[   67], 99.90th=[  134], 99.95th=[  142],
     | 99.99th=[  157]
   bw (  KiB/s): min=  127, max=  896, per=10.00%, avg=405.86, stdev=116.77, samples=1200
   iops        : min=    7, max=   56, avg=25.30, stdev= 7.31, samples=1200
  write: IOPS=110, BW=1773KiB/s (1816kB/s)(104MiB/60041msec)
    clat (msec): min=2, max=179, avg=42.37, stdev=14.24
     lat (msec): min=2, max=179, avg=42.37, stdev=14.24
    clat percentiles (msec):
     |  1.00th=[   16],  5.00th=[   24], 10.00th=[   27], 20.00th=[   32],
     | 30.00th=[   36], 40.00th=[   38], 50.00th=[   42], 60.00th=[   44],
     | 70.00th=[   48], 80.00th=[   53], 90.00th=[   59], 95.00th=[   65],
     | 99.00th=[   87], 99.50th=[  102], 99.90th=[  159], 99.95th=[  163],
     | 99.99th=[  180]
   bw (  KiB/s): min=   32, max=  384, per=10.00%, avg=177.26, stdev=55.86, samples=1200
   iops        : min=    2, max=   24, avg=11.01, stdev= 3.50, samples=1200
  lat (usec)   : 500=0.06%, 750=0.04%
  lat (msec)   : 2=0.51%, 4=3.98%, 10=14.38%, 20=17.14%, 50=55.75%
  lat (msec)   : 100=7.81%, 250=0.32%
  cpu          : usr=0.03%, sys=0.14%, ctx=21888, majf=0, minf=7
  IO depths    : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     issued rwts: total=15228,6655,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=1
Run status group 0 (all jobs):
   READ: bw=4058KiB/s (4155kB/s), 4058KiB/s-4058KiB/s (4155kB/s-4155kB/s), io=238MiB (249MB), run=60041-60041msec
  WRITE: bw=1773KiB/s (1816kB/s), 1773KiB/s-1773KiB/s (1816kB/s-1816kB/s), io=104MiB (109MB), run=60041-60041msec

Disk stats (read/write):
  vda: ios=15193/6650, merge=0/2, ticks=316823/281939, in_queue=592356, util=98.75%

You're limiting -iodepth 1 to one, which means all the operations must wait for the previous operation to be done before continue. It's normally used for the latency test only.
You can try with iodepth 32 or 64 again.

I tried to modify it to 32, and the test rate was still very low, and the results were as follows:
# fio -filename=/dev/vdb -direct=1 -iodepth 32 -thread -rw=randwrite -ioengine=psync -bs=16k -size=2G -numjobs=10 -runtime=60 -group_reporting -name=lhtest
lhtest: (g=0): rw=randwrite, bs=(R) 16.0KiB-16.0KiB, (W) 16.0KiB-16.0KiB, (T) 16.0KiB-16.0KiB, ioengine=psync, iodepth=32
...
fio-3.7
Starting 10 threads
^Cbs: 10 (f=10): [w(10)][50.0%][r=0KiB/s,w=880KiB/s][r=0,w=55 IOPS][eta 00m:30s]
fio: terminating on signal 2

lhtest: (groupid=0, jobs=10): err= 0: pid=3985: Wed Sep 23 03:43:08 2020
  write: IOPS=67, BW=1085KiB/s (1111kB/s)(32.4MiB/30532msec)
    clat (msec): min=16, max=440, avg=147.10, stdev=50.08
     lat (msec): min=16, max=440, avg=147.10, stdev=50.08
    clat percentiles (msec):
     |  1.00th=[   26],  5.00th=[   57], 10.00th=[   96], 20.00th=[  126],
     | 30.00th=[  132], 40.00th=[  138], 50.00th=[  144], 60.00th=[  148],
     | 70.00th=[  159], 80.00th=[  167], 90.00th=[  207], 95.00th=[  243],
     | 99.00th=[  292], 99.50th=[  368], 99.90th=[  426], 99.95th=[  435],
     | 99.99th=[  443]
   bw (  KiB/s): min=   63, max=  160, per=9.98%, avg=108.28, stdev=19.92, samples=603
   iops        : min=    3, max=   10, avg= 6.64, stdev= 1.30, samples=603
  lat (msec)   : 20=0.19%, 50=4.06%, 100=6.37%, 250=85.13%, 500=4.25%
  cpu          : usr=0.02%, sys=0.04%, ctx=2082, majf=0, minf=0
  IO depths    : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     issued rwts: total=0,2071,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=32

Run status group 0 (all jobs):
  WRITE: bw=1085KiB/s (1111kB/s), 1085KiB/s-1085KiB/s (1111kB/s-1111kB/s), io=32.4MiB (33.9MB), run=30532-30532msec

Disk stats (read/write):
  vdb: ios=50/2061, merge=0/0, ticks=98/302991, in_queue=302049, util=7.25%

It's weird that iodepth is still one in the result you posted
IO depths    : 1=100.0%

Oh, your ioengine ispsync. It seems it can only write/read once IO at a time. You should use ioengine=libaio, which can issue multiple IOs at the same time.

I modified it to ioengine=libaio, the test results are still not ideal, the following is the test results:
# fio -filename=/dev/vdb -direct=1 -iodepth 32 -thread -rw=randwrite -ioengine=libaio -bs=16k -size=2G -numjobs=10 -runtime=60 -group_reporting -name=lhtest
lhtest: (g=0): rw=randwrite, bs=(R) 16.0KiB-16.0KiB, (W) 16.0KiB-16.0KiB, (T) 16.0KiB-16.0KiB, ioengine=libaio, iodepth=32
...
fio-3.7
Starting 10 threads
Jobs: 10 (f=10): [w(10)][0.3%][r=0KiB/s,w=0KiB/s][r=0,w=0 IOPS][eta 06h:05m:53s]
lhtest: (groupid=0, jobs=10): err= 0: pid=3245: Wed Sep 23 21:51:28 2020
  write: IOPS=68, BW=1096KiB/s (1122kB/s)(68.0MiB/64453msec)
    slat (usec): min=5, max=4087.1k, avg=36185.06, stdev=248781.02
    clat (msec): min=25, max=13031, avg=4622.70, stdev=1627.69
     lat (msec): min=25, max=13031, avg=4658.88, stdev=1654.86
    clat percentiles (msec):
     |  1.00th=[  701],  5.00th=[ 2089], 10.00th=[ 2735], 20.00th=[ 3339],
     | 30.00th=[ 3876], 40.00th=[ 4279], 50.00th=[ 4597], 60.00th=[ 4866],
     | 70.00th=[ 5067], 80.00th=[ 5671], 90.00th=[ 6879], 95.00th=[ 7550],
     | 99.00th=[ 9194], 99.50th=[ 9866], 99.90th=[10805], 99.95th=[11073],
     | 99.99th=[13087]
   bw (  KiB/s): min=   31, max=  992, per=15.29%, avg=167.45, stdev=148.62, samples=784
   iops        : min=    1, max=   62, avg=10.37, stdev= 9.31, samples=784
  lat (msec)   : 50=0.05%, 100=0.07%, 250=0.23%, 500=0.39%, 750=0.36%
  lat (msec)   : 1000=0.41%
  cpu          : usr=0.01%, sys=0.03%, ctx=2986, majf=0, minf=10
  IO depths    : 1=0.2%, 2=0.5%, 4=0.9%, 8=1.8%, 16=3.6%, 32=93.0%, >=64=0.0%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=99.8%, 8=0.0%, 16=0.0%, 32=0.2%, 64=0.0%, >=64=0.0%
     issued rwts: total=0,4415,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=32

Run status group 0 (all jobs):
  WRITE: bw=1096KiB/s (1122kB/s), 1096KiB/s-1096KiB/s (1122kB/s-1122kB/s), io=68.0MiB (72.3MB), run=64453-64453msec

Disk stats (read/write):
  vdb: ios=241/4406, merge=0/0, ticks=24/18557225, in_queue=18555015, util=5.57%

What's your underlying disk? SSD/NVMe? What's the performance of them?
Also, for your reference, here is the command I used for benchmark:
fio --name=writefile --size=3G --filename=/dev/xxxx --nrfiles=1 --direct=1 --sync=0 --randrepeat=0 --refill_buffers --end_fsync=1 --iodepth=64 --ioengine=libaio --rw=write --bs=4k

Also, you can take a look at our performance report for v1.0.x here

The hard drive I'm using is the SATA mechanical hard drive, which can read and write between 400 and 500M. This is the rate at which I tested with the benchmark command:
fio-3.7
Starting 1 process
Jobs: 1 (f=1): [W(1)][100.0%][r=0KiB/s,w=6022KiB/s][r=0,w=94 IOPS][eta 00m:00s]
writefile: (groupid=0, jobs=1): err= 0: pid=17124: Thu Sep 24 14:43:34 2020
  write: IOPS=93, BW=5988KiB/s (6132kB/s)(3072MiB/525297msec)
    slat (usec): min=5, max=554, avg=38.17, stdev=27.61
    clat (msec): min=31, max=1651, avg=683.82, stdev=205.17
     lat (msec): min=31, max=1651, avg=683.86, stdev=205.17
    clat percentiles (msec):
     |  1.00th=[  146],  5.00th=[  405], 10.00th=[  498], 20.00th=[  550],
     | 30.00th=[  592], 40.00th=[  625], 50.00th=[  659], 60.00th=[  693],
     | 70.00th=[  735], 80.00th=[  793], 90.00th=[  944], 95.00th=[ 1099],
     | 99.00th=[ 1318], 99.50th=[ 1385], 99.90th=[ 1485], 99.95th=[ 1502],
     | 99.99th=[ 1586]
   bw (  KiB/s): min=  128, max=17664, per=100.00%, avg=6213.94, stdev=2427.36, samples=1011
   iops        : min=    2, max=  276, avg=97.02, stdev=37.94, samples=1011
  lat (msec)   : 50=0.01%, 100=0.47%, 250=1.95%, 500=8.22%, 750=62.61%
  lat (msec)   : 1000=18.76%
  cpu          : usr=0.43%, sys=0.45%, ctx=22007, majf=0, minf=34
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=99.9%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0%
     issued rwts: total=0,49152,0,1 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=64

Run status group 0 (all jobs):
  WRITE: bw=5988KiB/s (6132kB/s), 5988KiB/s-5988KiB/s (6132kB/s-6132kB/s), io=3072MiB (3221MB), run=525297-525297msec

Disk stats (read/write):
  vdb: ios=44/49153, merge=0/0, ticks=93/33566466, in_queue=33566482, util=100.00%

Per your benchmark result for disk, the spinning disk you have can only have IOPS of 93 and bandwidth around 6MB/s for the write. That explains why Longhorn gets such low performance in your setup. It's almost impossible to get higher write performance compared to your hardware drive since the storage system still has to write the data to the disk.

I see, thank you.

I will close this issue for now. Feel free to raise a new issue you have more questions.


sane-backends: install hwdb file

copied from debian https://jff.email/cgit/sane-backends.git/tree/debian/rules#n140
see #176412
Description of changes

Things done

Built on platform(s)

[ ] 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

[ ] Fits CONTRIBUTING.md.

This fixes the problem for me, thank you


Bugs of the dataset

when running training:
fid = stack.enter_context(open(os_fspath(file), "rb"))
FileNotFoundError: [Errno 2] No such file or directory: HADAR_database/Scene1/HeatCubes/S_EnvObj_L_0002.npy

I've run the prepare_data.py, but Scene11 seems lost files:
Scene11/GroundTruth/eMap/eMap_L_0001.mat


feat(scanner): Expose the RepositoryConfiguration to the scanner

In a future commit, the FossID scanner will use the Excludes contained in the configuration to generate ignore rules for the scan.

@fviernau : Another idea could be to expose the Excludes only for PackageScannerWrappers.
Thus, we can make clear that PathScannerWrappers  are independent from excludes.


[duro_gps_driver] Updated type names to latest libsbp.

Starts to address #33.  Still need to migrate sbp_register_callback but I am missing where is in the update.

@tonybaltovski thanks, i will check how it works as soon as I have the chance to work with the GPS


add ibaction, iboutlet, and createproperty snippets

I create my IBActions and Outlets in code alot so I've been using these snippets. I am also a C#.NET developer so I have grown accustomed to "prop" and "propfull" snippets that create properties.
I am a novice iOS developer so let me know if you think these are too pedestrian for your repo and I'll maintain my own.
I also have not contributed to other repos before so let me know of any rules or conventions I've broken and feel free to send anything back for edits. :)
Thanks,

So I guess step one of contributing is Read the README. :) I just changed my changes to the format you requested.

Thanks for the contribution!


Added '+' and '-' arithmetic operators. (EDIT: fixed errors)

I made them consistent with Ruby's Time class '+' and '-' operators I believe.
+ method allows addition to a DatelessTime object with a Numeric only (seconds), and returns a DatelessTime object.
- method allows subtraction from a DatelessTime object from a Numeric (seconds) and returns a DatelessTime object, or from another DatelessTime object, which returns a Float representing the difference in time in seconds.
I used your calculate_seconds_since_midnight method in both methods to quickly convert to seconds.
I wrote a few tests in the comparable_tests file showing the use.

@tompave Not sure if you're still keeping up with this project, but I'm using this in my personal project and needed this functionality, so I added it and thought I would go ahead and put in a pull request since it was already done.

Hi, thanks for the pull request!
I'm really sorry for the late reply, I didn't get any notification until you mentioned me.
I've not been using this for a while, but I'm happy to accept PRs and release a new version.

I've left a few comments on the diff.
A more general comment is that the two new methods should check for out-of-bounds situations and do something about it.
The easiest thing would be to raise a DatelessTime::TimeOutOfRangeError exception if they end up with negative seconds or with more seconds than there are in one day.
Another approach would be to wrap-around the day so that, for example, 23:50 + 22 minutes would result in 00:12,  and 01:30 - 3 hours would be 22:30. I'm still not too sure about this, because while interesting it clashes with the time-range validations applied when initializing new objects.

Gotcha, I'll look into it all and try to change some things! Appreciate the feedback.

@tompave Updated some things! Let me know what you think. Also commented a few things on some of your comments regarding Ruby's built in Time method's behavior.

Sorry for the late reply and thanks for the PR. I'll release a new version on Rubygems later today. :-)


Travis CI build falied on commits

Why do I keep getting The Travis CI build failed when I have updated the file as per contributin guidelines?
Please have a look at PR#631 & let me know how I can fix it, so that I can contribute.

Looking at your PR changes I can already see that your additions are not in alphabetical order (which can be confirmed by reading the log that Travis CI provides).


cryptomb: support ECDSA

Signed-off-by: Xie Zhihao<EMAIL_ADDRESS>Commit Message: cryptomb: support ECDSA
Additional Description: The CryptoMB private key provider only supports RSA at the time, the patch adds ECDSA support to it.
Risk Level: Low (as contrib extension)
Testing: Unit and integration tests
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: Requires AVX512 or equivalent CPU instruction set

/retest


'configure.exe' is not recognized as an internal or external command, operable program or batch file.

PhantomJS 2.1.1 build fails on Windows (with MSVC 11.0) with the following error:
Executing in G:\Sources\phantomjs: git submodule init
Executing in G:\Sources\phantomjs: git submodule update --init
configuring Qt Base, please wait...
Executing in G:\Sources\phantomjs\src\qt\qtbase: G:\Sources\phantomjs\src\qt\qtbase\configure.bat -static -opensource -confirm-license -prefix G:\Sources\phantomjs\src\qt\qtbase -qt-zlib -qt-libpng -qt-libjpeg -qt-pcre -nomake examples -nomake tools -nomake tests -no-qml-debug -no-dbus -no-opengl -no-audio-backend -D QT_NO_GRAPHICSVIEW -D QT_NO_GRAPHICSEFFECT -D QT_NO_STYLESHEET -D QT_NO_STYLE_CDE -D QT_NO_STYLE_CLEANLOOKS -D QT_NO_STYLE_MOTIF -D QT_NO_STYLE_PLASTIQUE -D QT_NO_PRINTPREVIEWDIALOG -mp -static-runtime -no-cetest -no-angle -icu -openssl -openssl-linked -I G:\Sources\phantomjs\src\qt\3rdparty\libicu\include -I G:\Sources\phantomjs\src\qt\3rdparty\libxml\include -I G:\Sources\phantomjs\src\qt\3rdparty\openssl\include -I G:\Sources\phantomjs\src\qt\3rdparty\zlib\include -L G:\Sources\phantomjs\src\qt\3rdparty\libicu\lib -L G:\Sources\phantomjs\src\qt\3rdparty\libxml\lib -L G:\Sources\phantomjs\src\qt\3rdparty\openssl\lib -L G:\Sources\phantomjs\src\qt\3rdparty\zlib\lib -release
Please wait while bootstrapping configure ...
<srcbase> = G:/Sources/phantomjs/src/qt/qtbase
<outbase> = G:/Sources/phantomjs/src/qt/qtbase
The system cannot find the file specified.

Microsoft (R) Program Maintenance Utility Version 11.00.50727.1
Copyright (C) Microsoft Corporation.  All rights reserved.

'configure.exe' is not recognized as an internal or external command,
operable program or batch file.
building Qt Base, please wait...
Executing in G:\Sources\phantomjs\src\qt\qtbase: nmake /NOLOGO
NMAKE : fatal error U1064: MAKEFILE not found and no target specified
Stop.

ERROR: Failed to build PhantomJS! Building Qt Base failed.

I installed Python, Perl (ActivePerl) and Ruby as per documentation and used python build.py from a Visual Studio 2012 command prompt.

Nevermind, I was able to proceed with the build after cloning the repo again and building from scratch. It seems that some files had not been deleted despite running git clean -xfd ..


add benchmark

resolve #2

Coverage remained the same at 100.0% when pulling 3adb9d76e955785b9fd4ce675947752c2c293125 on feature/add_benchmark into 885c1b1f4466bf7b24f61f9b64f0f01f6273280f on master.

Coverage remained the same at 100.0% when pulling a88378c512c583a1dbbdfcd9c5201e72b205117d on feature/add_benchmark into 885c1b1f4466bf7b24f61f9b64f0f01f6273280f on master.


Create demo DNN-Events pipeline-part as a template for many

Could be events or something

Working on it...but simply as a app any way you want it

Won't do. There is a large complexity with parameter matching (if the parameter should come from Query, from Module etc.) which is hard to pre-configure without the content-types etc. Close for now.


copilot chat in vscode: "certificate has expired"

My organization gave me a Copilot seat today.  When I try to use Copilot chat in VSCode, it tells me certificate has expired.
Copilot code completion seems to be working, though.
I've read suggestions that maybe my system time is off, but NTP time synchronization is forced on by my organization.  It's using time.apple.com as the NTP server.
I can use Copilot chat from Github Codespaces.  I can use it from PyCharm (JetBrains IDE), so I know I have a license.
I can access api.githubcopilot.com from desktop browsers and curl / wget in my terminal.  I don't seem to be having DNS resolution issues.
I think I've included the relevant logs.

Copilot Chat Extension Version: 0.17.1
VS Code Version: 1.91.1 (Universal)
OS Version: MacOS 14.6
Logs:

Copilot collect diagnostics

## Copilot

- Version: 1.219.0
- Build: prod
- Editor: vscode/1.91.1

## Environment

- http_proxy: n/a
- https_proxy: n/a
- no_proxy: n/a
- SSL_CERT_FILE: n/a
- SSL_CERT_DIR: n/a
- OPENSSL_CONF: n/a

## Feature Flags

- Send Restricted Telemetry: disabled
- Chat: enabled

## Node setup

- Number of root certificates: 141
- Operating system: Darwin
- Operating system version: 23.6.0
- Operating system architecture: arm64
- NODE_OPTIONS: n/a
- NODE_EXTRA_CA_CERTS: n/a
- NODE_TLS_REJECT_UNAUTHORIZED: n/a
- tls default min version: TLSv1.2
- tls default max version: TLSv1.3

## Network Configuration

- Proxy host: n/a
- Proxy port: n/a
- Kerberos SPN: n/a
- Reject unauthorized: disabled
- Fetcher: HelixFetcher

## Reachability

- github.com: HTTP 200
- api.github.com: HTTP 200
- proxy.business.githubcopilot.com: HTTP 200
- api.business.githubcopilot.com: HTTP 200
- default.exp-tas.com: HTTP 200

## VS Code Configuration

- HTTP proxy:
- HTTP proxy authentication: n/a
- Proxy Strict SSL: true
- Extension HTTP proxy support: override

## Extensions

- Is `win-ca` installed?: false
- Is `mac-ca` installed?: false

## Authentication

- GitHub username: lhoekenga

Copilot chat diagnostics

## GitHub Copilot Chat

- Extension Version: 0.17.1 (prod)
- VS Code: vscode/1.91.1
- OS: Mac

## Network

User Settings:
```json
  "github.copilot.advanced": {
    "debug.useElectronFetcher": false,
    "debug.useNodeFetcher": false
  }

DNS Lookup api.githubcopilot.com: <IP_ADDRESS>

Fetching https://api.githubcopilot.com/_ping:
- Electron Fetcher: HTTP 200
- Node Fetcher: HTTP 200
- Helix Fetcher (configured): HTTP 200

Network Proxy Test: Test Network Connection

Note: Make sure to replace all sensitive information with dummy values before sharing this output.

VS Code 1.91.1 (f1e16e1e6214d7c44d078b1f0607b2388f29d729)
Network Proxy Test 0.0.12
darwin 23.6.0 arm64

Settings:
- http.proxy:
- http.proxyAuthorization: null
- http.proxyStrictSSL: true
- http.proxySupport: override
- http.systemCertificates: true

Environment variables:

Sending GET request to https://api.githubcopilot.com/_ping...
vscode-proxy-agent: DIRECT
Received response:
- Status: 200 OK
Certificate chain:
- Subject: *.githubcopilot.com (GitHub, Inc.)
  Subject alt: DNS:*.githubcopilot.com, DNS:githubcopilot.com
  Validity: Aug 16 00:00:00 2023 GMT - Aug 16 23:59:59 2024 GMT
  Fingerprint: 54:59:1F:F1:6B:26:2F:B0:BC:68:70:BE:9F:E9:06:B3:37:7A:8A:9D
- Subject: DigiCert Global G2 TLS RSA SHA256 2020 CA1 (DigiCert Inc)
  Validity: Mar 30 00:00:00 2021 GMT - Mar 29 23:59:59 2031 GMT
  Fingerprint: 1B:51:1A:BE:AD:59:C6:CE:20:70:77:C0:BF:0E:00:43:B1:38:26:12
- Subject: DigiCert Global Root G2 (DigiCert Inc)
  Validity: Aug  1 12:00:00 2013 GMT - Jan 15 12:00:00 2038 GMT
  Fingerprint: DF:3C:24:F9:BF:D6:66:76:1B:26:80:73:FE:06:D1:CC:8D:4F:82:A4
  Self-signed
Local root certificates:
- Subject: C=US O=DigiCert Inc OU=www.digicert.com CN=DigiCert Global Root G2 (built-in)
  Validity: Aug  1 12:00:00 2013 GMT - Jan 15 12:00:00 2038 GMT
  Fingerprint: DF:3C:24:F9:BF:D6:66:76:1B:26:80:73:FE:06:D1:CC:8D:4F:82:A4
  Issuer: C=US O=DigiCert Inc OU=www.digicert.com CN=DigiCert Global Root G2

Sending GET request to https://api.githubcopilot.com/_ping using fetch API...
Received response:
- Status: 200

Steps to Reproduce:

open chat window, "/explain something"
"Certficate has expired"

I tried it again today, and it's working.  Weird.

I tried it again today, and it's working. Weird.

and I am having this issue again. Once in a while copilot broke and I have no idea why.... This is really annoying for a paid product.

I'm having the same problem.

Same.

Reopening because other people are running into it..

Copilot collect diagnostics
## Copilot

- Version: 1.220.0
- Build: prod
- Editor: vscode/1.92.0

## Environment

- http_proxy: n/a
- https_proxy: n/a
- no_proxy: n/a
- SSL_CERT_FILE: n/a
- SSL_CERT_DIR: n/a
- OPENSSL_CONF: n/a

## Feature Flags

- Send Restricted Telemetry: disabled
- Chat: enabled

## Node setup

- Number of root certificates: 147
- Operating system: Darwin
- Operating system version: 23.6.0
- Operating system architecture: arm64
- NODE_OPTIONS: n/a
- NODE_EXTRA_CA_CERTS: n/a
- NODE_TLS_REJECT_UNAUTHORIZED: n/a
- tls default min version: TLSv1.2
- tls default max version: TLSv1.3

## Network Configuration

- Proxy host: n/a
- Proxy port: n/a
- Kerberos SPN: n/a
- Reject unauthorized: disabled
- Fetcher: HelixFetcher

## Reachability

- github.com: HTTP 200
- api.github.com: HTTP 200
- copilot-proxy.githubusercontent.com: HTTP 200
- api.githubcopilot.com: HTTP 200
- default.exp-tas.com: HTTP 200

## VS Code Configuration

- HTTP proxy:
- HTTP proxy authentication: n/a
- Proxy Strict SSL: true
- Extension HTTP proxy support: override

## Extensions

- Is `win-ca` installed?: false
- Is `mac-ca` installed?: false

## Authentication

- GitHub username: lhoekenga

Copliot Chat Diagnostics
## GitHub Copilot Chat

- Extension Version: 0.18.1 (prod)
- VS Code: vscode/1.92.0
- OS: Mac

## Network

User Settings:
```json
  "github.copilot.advanced": {
    "debug.useElectronFetcher": false,
    "debug.useNodeFetcher": false
  }

Connecting to https://api.github.com:

DNS Lookup: <IP_ADDRESS>
Electron Fetcher: HTTP 200
Node Fetcher: HTTP 200
Helix Fetcher (configured): HTTP 200

Connecting to https://api.githubcopilot.com/_ping:

DNS Lookup: <IP_ADDRESS>
Electron Fetcher: HTTP 200
Node Fetcher: HTTP 200
Helix Fetcher (configured): Error: certificate has expired

Documentation
In corporate networks: Troubleshooting firewall settings for GitHub Copilot.

### Network Proxy Test: Test Network Connection

Note: Make sure to replace all sensitive information with dummy values before sharing this output.
VS Code 1.92.0 (b1c0a14de1414fcdaa400695b4db1c0799bc3124)
Network Proxy Test 0.0.12
darwin 23.6.0 arm64
Settings:

http.proxy:
http.proxyAuthorization: null
http.proxyStrictSSL: true
http.proxySupport: override
http.systemCertificates: true

Environment variables:
Sending GET request to https://api.githubcopilot.com/_ping...
vscode-proxy-agent: DIRECT
Received response:

Status: 200 OK
Certificate chain:
Subject: .githubcopilot.com
Subject alt: DNS:.githubcopilot.com, DNS:githubcopilot.com
Validity: Aug  1 00:00:00 2024 GMT - Aug  1 23:59:59 2025 GMT
Fingerprint: 8D:C4:7D:28:E8:BF:72:45:F8:F8:C1:40:90:93:7F:09:EC:6B:3D:6F
Subject: Sectigo RSA Domain Validation Secure Server CA (Sectigo Limited)
Validity: Nov  2 00:00:00 2018 GMT - Dec 31 23:59:59 2030 GMT
Fingerprint: 33:E4:E8:08:07:20:4C:2B:61:82:A3:A1:4B:59:1A:CD:25:B5:F0:DB
Subject: USERTrust RSA Certification Authority (The USERTRUST Network)
Validity: Mar 12 00:00:00 2019 GMT - Dec 31 23:59:59 2028 GMT
Fingerprint: D8:9E:3B:D4:3D:5D:90:9B:47:A1:89:77:AA:9D:5C:E3:6C:EE:18:4C
Subject: AAA Certificate Services (Comodo CA Limited)
Validity: Jan  1 00:00:00 2004 GMT - Dec 31 23:59:59 2028 GMT
Fingerprint: D1:EB:23:A4:6D:17:D6:8F:D9:25:64:C2:F1:F1:60:17:64:D8:E3:49
Self-signed
Local root certificates:
Subject: C=GB ST=Greater Manchester L=Salford O=Comodo CA Limited CN=AAA Certificate Services (built-in and OS)
Validity: Jan  1 00:00:00 2004 GMT - Dec 31 23:59:59 2028 GMT
Fingerprint: D1:EB:23:A4:6D:17:D6:8F:D9:25:64:C2:F1:F1:60:17:64:D8:E3:49
Issuer: C=GB ST=Greater Manchester L=Salford O=Comodo CA Limited CN=AAA Certificate Services

Sending GET request to https://api.githubcopilot.com/_ping using fetch API...
Received response:

Status: 200

Yes I am encountering the same error.

Also having this issue.

Completely wiping VSCode from my computer and deleting it's preferences, and then reinstalling everything seems to have fixed it.    Not exactly convenient.

Also having this issue

So i looked a bit more into this and it seems the SSL cert used by api.github.com and api.githubcopilot.com has expired.
Both Node Fetcher and Helix Fetcher showing certificate has expired.

Installing Copilot v17.2 worked for me. v19 is acting up.
I'm running VSC Insiders Version: 1.93.0-insider (Universal) btw!

I am having this issue this morning.  Went down a hole trying to make sure my sntp is working; my time is synched.

Someone else posted this earlier, but I can't find it now. It worked for me:
View > Show Expired Certificates
Sort the login keychain by expire date
Look for a set of 3 certificates (AddTrust and USERTRUST and one other) that had expired May 30, 2020 (the expired ones you need to remove may be something else)
Delete those certificates```

This worked for me! Thank you

Someone else posted this earlier, but I can't find it now. It worked for me:
Open up Keychain Access
View > Show Expired Certificates
Sort the login keychain by expire date
Look for a set of 3 certificates (AddTrust and USERTRUST and one other) that had expired May 30, 2020 (the expired ones you need to remove may be something else)
Delete those certificates

is there an equivalent for vscode?

Someone else posted this earlier, but I can't find it now. It worked for me:
Open up Keychain Access
View > Show Expired Certificates
Sort the login keychain by expire date
Look for a set of 3 certificates (AddTrust and USERTRUST and one other) that had expired May 30, 2020 (the expired ones you need to remove may be something else)
Delete those certificates

is there an equivalent for vscode?

I used this to fix VSCode.

Someone else posted this earlier, but I can't find it now. It worked for me:
Open up Keychain Access
View > Show Expired Certificates
Sort the login keychain by expire date
Look for a set of 3 certificates (AddTrust and USERTRUST and one other) that had expired May 30, 2020 (the expired ones you need to remove may be something else)
Delete those certificates

is there an equivalent for vscode?

I used this to fix VSCode.

On windows I mean. Sorry for the confusion.

Someone else posted this earlier, but I can't find it now. It worked for me:
Open up Keychain Access
View > Show Expired Certificates
Sort the login keychain by expire date
Look for a set of 3 certificates (AddTrust and USERTRUST and one other) that had expired May 30, 2020 (the expired ones you need to remove may be something else)
Delete those certificates

is there an equivalent for vscode?

I used this to fix VSCode.

On windows I mean. Sorry for the confusion.

no problem! I'm sorry, I haven't seen a solution for Windows.

Thanks, this prob wont work for me cause i dont have total control of my laptop. My org does -_-

Someone else posted this earlier, but I can't find it now. It worked for me:
Open up Keychain Access
View > Show Expired Certificates
Sort the login keychain by expire date
Look for a set of 3 certificates (AddTrust and USERTRUST and one other) that had expired May 30, 2020 (the expired ones you need to remove may be something else)
Delete those certificates

This worked for me. Thank you! For anyone wondering this relevant to Mac OS. Make sure you are looking in the login keychain tab.

In windows:
Press Win + R to open the Run dialog.
Right-Click on Certificates-Current User and click "Find Certificates"
search for "addtrust"
In my case, there were 4 certificates with expiration dates were 30.05.2020
Delete all 4 and restart vscode.

Is there any solution for Linux OS for the same problem?

Didn't work for me on macOS. Still having this issue:
2024-08-09 12:23:18.071 [error] ZV: certificate has expired
    at Yde (/Users/qashto/.vscode-insiders/extensions/github.copilot-chat-0.19.2024080801/dist/extension.js:21:29516)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at NUe (/Users/qashto/.vscode-insiders/extensions/github.copilot-chat-0.19.2024080801/dist/extension.js:21:31538)
    at CI.fetch (/Users/qashto/.vscode-insiders/extensions/github.copilot-chat-0.19.2024080801/dist/extension.js:751:2373)
    at Jm._fetchModels (/Users/qashto/.vscode-insiders/extensions/github.copilot-chat-0.19.2024080801/dist/extension.js:1449:16231)

same issue for me. I worked couple days before.

In windows: Press Win + R to open the Run dialog. Type certmgr.msc and press Enter. This opens the Certificate Manager. Right-Click on Certificates-Current User and click "Find Certificates" search for "addtrust" In my case, there were 4 certificates with expiration dates 30.05.2020 Delete all 4 and restart vscode.

shoot. I got access denied :( What a pain.

Could you please try the following setting and reload VS Code:
"github.copilot.advanced": {
    "debug.useElectronFetcher": true
}

I have reviewed our code and for the HelixFetcher we are not filtering out expired certificates when reading them from the OS.

This is now fixed and will be part of the upcoming 0.18.2 release.

I am still getting this error. Extremely annoying for a paid product
024-08-20 21:03:12.571 [info] [certificates] Removed 3 expired certificates 2024-08-20 21:03:14.205 [error] [auth] auth: FetchError:
....
ts:58:9) {   type: 'system',   _name: 'FetchError',   code: 'ETIMEDOUT',   errno: undefined,   erroredSysCall: undefined

I am already logged in to Github copilot, still its not showing me the chat section and asking that I should sign in and when I am trying to that the sign in button is not working

@Khan-Kaleem Continuing in https://github.com/microsoft/vscode-copilot-release/issues/1494. Thanks.

In windows: Press Win + R to open the Run dialog. Type certmgr.msc and press Enter. This opens the Certificate Manager. Right-Click on Certificates-Current User and click "Find Certificates" search for "addtrust" In my case, there were 4 certificates with expiration dates 30.05.2020 Delete all 4 and restart vscode.

This did not work for me


[BUG]  Issue with Graph Rendering in Gremlin Queries on JupyterLab

I am encountering an issue where my Gremlin queries do not render as graphs. I'm unsure if this is related to the Graph Notebook widget, but it does not seem to be functioning as expected in my environment. I am running JupyterLab via JupyterHub, which is deployed on Kubernetes.
Here are the details of my environment:

OS: Linux SMP Debian 5.10.223-1 (2024-08-10) x86_64 x86_64 x86_64 GNU/Linux
Browser: Google Chrome
Graph Notebook Version: 4.5.2
Graph Database & Version: JanusGraph 1.0.0
Python Version: 3.9.13

I have attached relevant screenshots at the end for your reference. I would greatly appreciate your guidance on resolving this issue.
Here's the relevant screenshots

Thank you so much for your time and support!

Hi @amansharif, thank you for submitting an issue!
I tried manually installed your Jupyter package versions a Python 3.9.19 environment with graph-notebook. This resulted in an extensions warning when launching JupyterLab:
3c22fb5e1f47:graph-notebook chnmch$ python -m graph_notebook.start_jupyterlab --jupyter-dir ~/notebook/destination/dir
[W 2024-09-20 20:57:49.213 ServerApp] jupyter_server_terminals | error adding extension (enabled: True): Jupyter Server Terminals requires Jupyter Server 2.0+
    Traceback (most recent call last):
      File "/Users/chnmch/.pyenv/versions/3.9.13/envs/test-3.9.13/lib/python3.9/site-packages/jupyter_server/extension/manager.py", line 320, in add_extension
        ...
    RuntimeError: Jupyter Server Terminals requires Jupyter Server 2.0+

Installing both JupyterLab 3 and graph-notebook fresh in a different Python 3.9.19 env did not did not give me any issues. For comparison, this was the resulting Jupyter packages list:
3c22fb5e1f47:graph-notebook chnmch$ jupyter --version
Selected Jupyter core packages...
IPython          : 8.10.0
ipykernel        : 5.3.4
ipywidgets       : 7.7.2
jupyter_client   : 7.4.9
jupyter_core     : 5.7.2
jupyter_server   : 2.14.2
jupyterlab       : 3.6.8
nbclient         : 0.7.3
nbconvert        : 7.2.8
nbformat         : 5.10.4
notebook         : 6.5.7
qtconsole        : 5.6.0
traitlets        : 5.14.3

It looks like some of the older Jupyter dependencies in your environment may be preventing the widgets extensions from loading properly. Please try upgrading to the latest versions supported by Python 3.9 and JupyterLab 3, and see if it helps.

Closing due to 30 days of inactivity - please re-open if there are further updates.


Merging SAIL Optimizations

This merge has proven to be very difficult because the SAIL branch diverged before some major rewrites of the modeling code. Will re-write these optimizations into the current code as an alternative and where applicable.


Upgrade to halo2 -> halo2_proofs

Scheduling
This task must be done as part of:

#2982

Motivation

The halo2 crate is being refactored, we may need to adjust how we use it.
Designs

Try:
halo2 = { package = "halo2_proofs", version = "=0.1.0-beta.2" }

"and then you only need to focus on the API changes, not renaming the imports everywhere."
Make sure that the orchard crate is updated and working accordingly, if needed.
Related Work

See also the changelog for `halo2_proofs 0.1.0-beta.2 for all of the API changes relevant to this upgrade.

Schedule note
This task must be done as part of:

#2982

#2982 moved sprints, but this linked task didn't.
Should we close this ticket, and move its details into #2982?


chore: bdd-sbhg-1585594968 to 0.0.1

chore: Promote bdd-sbhg-1585594968 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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


LocationUpdatesForegroundService · launching activity from notification creates another instance of MainActivity

Title is self-explanatory: if you press Launch Activity from the notification, and you were in MainActivity, then, another instance of MainActivity will be created. To confirm, follow the steps before and press back.

I believed when you set up the notification.
You just have to put PendingIntent.FLAG_UPDATE_CURRENT so that another instance of MainActivity will not be created if already exist


Updated GriptapeCloudKnowledgeBaseClient.query() to optionally return raw query responses from the Knowledge Base

@cjkindel are you planning on doing the Vector Store Driver work on this PR? Otherwise I think we should close since there should be no changes to GriptapeCloudKnowledgeBaseClient


Drop support for Python 2

Actions required:

[ ] Include a note in 2.6 release notes announcing that it will be the last version to support Python 2
[ ] Remove as much Python 2 specific code as possible
[ ] Remove Python 2 environment tests from tox configuration

Here's the pip installs for wagtailmenus from PyPI for the last month (via pypinfo --percent --pip --markdown wagtailmenus pyversion), showing no Python 2.6 and quite low 2.7 numbers, especially compared to 3.x, which is over 91%.

python_version
percent
download_count

3.5
46.6%
346

3.6
39.2%
291

2.7
8.6%
64

3.4
5.4%
40

3.7
0.1%
1

3.3
0.1%
1

@hugovk Thanks for sharing. It hadn't occurred to me check download figures, but that's good to know. With Django 2.0 out already and Wagtail 2.0 not far away, it just seems like the right time. They've already made the big/impactful decisions, so most developers in this space will be moving over to py3 soon if they haven't already. I'm mostly just excited about using the tidier 'super()' throughout :)

Things will be much easier with just Python 3.4+!
Make sure to use python_requires in setup.py, which can be added already.
https://stackoverflow.com/a/44660547/724176

Thanks, that's super helpful.

Hey. May I know when 2.7 is going to be release? We would like to bump django/wagtail to 2.0 and wagtailmenus are the only dependency which is stopping as from that. And it seems that both tickets from 2.7 milestone are done.
Thanks!

Hi @hnykda,
2.7 will be released very soon (in the next few days). If you don't want to wait, you include the github repo as a branch for now (master branch), and that should work.

Hey. Thanks. Yeah, we know we can install from github, I was just curious when the next release is going to come.


isExe only returns true when everyone has execute on the binary.

Command returns not found when everyone doesn't have execute
eg:
-rwxr-x--- 1 root webapps     463 Dec 13 12:18 compass
$ node node_modules/.bin/which compass
not found: compass
$ chmod 755 compass
$ node node_modules/.bin/which compass
/usr/local/bin/compass

version: 1.0.5
os: debian wheezy

This works fine for me.  Are you perhaps not in the webapps group, or not the root user?


LL-1888 debounce clicks on navigations push

as mentioned in #1146
we should prevent double click navigation pushs
best solution yet is to debounce them.
Type
Bug Fix
Context
LL-1888
Parts of the app affected / Test plan
Accounts tokens links and sub operations aswell

cc @Arnaud97234 @nabil-brn


Reality and New Update

Hi guys,
I have 2 question:
1.When new update release?
2.Can u add reality protocol to npanel?
Thank's a lot.

Hi,
1- im trying to release it as soon as possible, but  things have gone out of my controll mostly but im trying to manage the situation and clean things up..
2-ofcourse, I will defientaly add vless with (tcp,reality) transports right after i release the currently pormised  update, but i probably don't bring the entrie xray-core , ill try to fit the vless protocol to trojan-go core style as a custom protocol stack, for a very high chance
it

Thanks fore your support & reply.

Hi, any news from new version?

Npanel is dead bro

Npanel is dead bro

Why are saying that?

Npanel is dead bro

Why are saying that?

you see now. why im saying "Npanel is dead"


verible.flist doesn't work with coc.nvim

vim9 with coc.nvim
configure

          "verible": {
              "command": "verible-verilog-ls",
              "filetypes": ["systemverilog", "verilog"],
              "settings": {
                  "verilog-trace-parser": "true"
              }
          }

export VERIBLE_LOGTHRESHOLD=0

I didn't see any special log in CocInfo.
go-to-definition works if the defination in the same file. It doesn't work if it's in other file.
So verible.filelist doesn't work here.

Just checking, the name is verible.filelist, not veriable.filelist.
There are two environment variables that might help VERIBLE_LOGTHRESHOLD=0 and also VERIBLE_VLOG_DETAIL=1 which expands more detail. Maybe that helps to see what is going on ?

@hzeller  sorry, it's my typo. I use verible.filelist in my real environment. I tried VERIBLE_LOGTHRESHOLD=0 and VERIBLE_VLOG_DETAIL=1. but it doesn't output any information in CocInfo. I will check the usage of coc.nvim.

To verify logging, do you see at least any output ? At least something like the following should be emitted
Verible Verilog Language Server built at v0.0-3033-gd35d72e0
... then potentially more logging

I only see this from coc.nvim. I think I need to find the method to open logging in coc.nvim
2023-03-09T23:21:16.897 INFO (pid:20760) [services] - LanguageClient verible state change: stopped => starting
2023-03-09T23:21:17.707 INFO (pid:20760) [language-client-index] - Language server "languageserver.verible" started with 20792
2023-03-09T23:21:17.730 INFO (pid:20760) [attach] - receive notification: jumpDefinition []
2023-03-09T23:21:17.776 ERROR (pid:20760) [attach] - Error on notification jumpDefinition Error: definition provider not found for current buffer, your language server doesn't support it.
 at Handler.checkProvider (/home/harriszh/.vim/plugged/coc.nvim/build/index.js:83057:17)
 at LocationsHandler.request (/home/harriszh/.vim/plugged/coc.nvim/ build/index.js:79316:22)
at processTicksAndRejections (node:internal/process/task_queues:965)
at async LocationsHandler.gotoDefinition (/home/harriszh/.vim/plugged/coc.nvim/build/index.js:79358:26)
at async Plugin.cocAction (/home/harriszh/.vim/plugged/coc.nvim/build/index.js:83362:16)
at async EventEmitter.<anonymous> (/home/harriszh/.vim/plugged/coc. nvim/build/index.js:83472:15)

I found the method to debug lsp in coc.nvim.
:CocCommand workspace.showOutput will output the log from lsp.
Then I got the error msg and found out the issue.
My code is in one git reposity.
I put verible.filelist in the exact verilog code (<git_root_dir>/src/v). but verible try to find the verible.filelist in the root directory(<git_root_dir>).
After copying verible.filelist into <git_root_dir>,  it works.

Yay.
Yes, editors themselve attempt to find the root of the project and will report it to the language server which then tries to find the file list there. Only if we don't get a file list from the editor, we fall back to backwards search from the location.
We probably need to document that better.


How to set/override hover background to transparent?

Hi there,
setting the background color of a hover window from e.g. lsp.buf.hover works, when I use this setting:
require("nightfox").setup({
  groups = {
    carbonfox = {
	NormalFloat = { link = "DiffAdd" },
        -- NormalFloat = { bg = "#73daca" }, -- this works as well
    },
  },
  options = {
    transparent = true,
    ...
  },
})
vim.cmd("colorscheme carbonfox")
...

What I can't get to work is a transparent background like e.g. telescope or neotree etc.
For instance, linking to Normal does not work. That would have been, what I expected to be neccessary, is this correct?
Changes to NormalFloat effect the look of telescope as I would expect them to by the way. What am I missing here?
I'm not sure, if this is an issue of me being too dump to set things up correctly, or maybe something in my config messes with the transparency setting...
This is what it looks like without modification:

...using some setting takes effect:

What I would like to achive, the same style as in telescope:

Have you tried to get the background to NONE?
require("nightfox").setup({
  options = {
    transparent = true,
  },
  groups = {
    all = {
      NormalFloat = { bg = "NONE" },
    },
  },
})


⚠ Bofrost.be has degraded performance

In 2afbbaf, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2203 ms

Resolved: Bofrost.be performance has improved in fefa71d.


MAPC/24.2.0

URL for testing:

https://stage--dme-partners--adobecom.hlx.page/

Codecov Report
Attention: Patch coverage is 81.02894% with 472 lines in your changes missing coverage. Please review.

Please upload report for BASE (main@3df599d). Learn more about missing BASE report.

Files
Patch %
Lines

edsdme/components/PartnerCards.js
60.18%
338 Missing :warning:

edsdme/blocks/announcements/AnnouncementsCards.js
62.28%
89 Missing :warning:

edsdme/scripts/utils.js
68.25%
40 Missing :warning:

edsdme/components/NewsCard.js
92.42%
5 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #22   +/-   ##
=======================================
  Coverage        ?   81.73%
=======================================
  Files           ?        7
  Lines           ?     2606
  Branches        ?        0
=======================================
  Hits            ?     2130
  Misses          ?      476
  Partials        ?        0

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


Qt 6 version used to build Cast Android

I am trying to use Cast Android 10.0.0 from a Qt 6 app.
For now the issue is that an UnsatisfiedLinkError occurs when instantiating Cast:  libcast_android.so references native symbols that can not be found.
The same issue occurs with Qt 6.4.0, 6.3.2 and 6.2.4.
What is the exact Qt version used to build Cast library?
Thank you,
David

Qt 6.3.2 was the one.

@julien-l Is there any plan to remove Qt dependency from the Android build?

No plan to remove Qt dependencies (this would be ideal but not feasible).
The cast package (AAR file) now embeds all the necessary dependencies, or at least it should, maybe one is missing. Can you copy the error messages? Or provide a minimal application to reproduce the problem?

There is no missing dependency but in the case of integrating into a Qt based Android app, there are conflicts, and a constraint regarding the Qt SDK version used. Qt SDK 6.3.2 is the only one able to load cast shared object.
Another issue is that after instantiating Cast, the Qt app UI doesn't refresh anymore. If Cast is instantiated from an another thread than the main one, the following log appears:
WARNING: QApplication was not created in the main() thread.

If there are 2 QCoreApplication instances in the app, this may explain the UI refresh issue.
Here is a test project: https://github.com/daudrain/TestQtAndroidWithClariusCast

Hi @julien-l ,
Have you been able to look at this issue?
Thx

No update yet sorry.

Hi @julien-l ,
I did update the Qt Android test project with the 10.1.1 release.
So far the situation is the same, the UI is not responsive after instantiating Cast.
Is there any workaround on your side such as testing if there is already a QCoreApplication available?
Thank you,
David

Hi the clarius app version 10.2.3 was just released and includes this fix, no need to wait for 10.3.0. This version does not required a firmware update. Current cast library should be compatible.

Hi @julien-l ,
10.2.3 doesn't seem available here yet.
I will try it out.
Thx

Published: https://github.com/clariusdev/cast/releases/tag/v10.2.3

@julien-l ,
I confirmed that Cast object can be instantiated and initialized using 10.2.3.
Note that 6.4.3 is the only Qt 6.4 that will work ok because the bug ABI broke for QJniObject::callVoidMethodV in 6.4  prevented previous version to be ABI compatible with 6.3. Fix has been applied to 6.5 and 6.6.


Improve dockerfile and add nodemon

Adds nodemon (auto restart app on file change) for local development and adds some Node/Docker best practices

What functionality does NODE_ENV toggle here?

What functionality does NODE_ENV toggle here?

Technically nothing. But its commonly used by packages as a basis of whether or not to run in dev mode. could be removed since we aren't really using it.

We can leave NODE_ENV, was just making sure I wasn't missing something.
Otherwise looks good, I'll merge later after I make a slight adjustment to the volume setup.

Had to revert this change as it prevented app from starting


Visual issue: Purple rubber band effect seen on first screen of on-boarding.

Purple rubber band effect seen on first screen of on-boarding.  Compare with screen 2.  See screen-recording, attached)
IMG_0017.TRIM.MOV.zip

@ahurworth Should be addressed in the next build.


Add services.yaml entry for new WeMo Humidifier platform service

Description:
Add an entry to services.yaml describing the wemo_set_humidity service offered by the new WeMo Humidifier platform
Related issue (if applicable): addition to #17996

I found another typo in fan/wemo.py, so I'm including that fix in this PR as well.

Can be merged when build passes.

Thanks again for the help, @MartinHjelmare. I created a new fork and am doing branching from the start this time. That should make rebasing actually work this time.


Deprecating Support Portal and created a Landing page

Removing the redirect for mawssupport.trafficmanager.net and created a landing page that helps customers find the Diagnostic tools easily.

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

We ended up backing this one out, and @puneetg1983 will change it to host image in CDN instead of embedded.


New version: Anchore.Grype version 0.85.0

Pull request has been created with komac v2.6.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Packages\Anchore.Grype__DefaultSource\grype.exe returned exit code: 1
Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Links\grype.exe returned exit code: 1

(Automated response - build 899.)


ListView.builder should let clients specify a divider

The ListView class should let clients specify a divider to be added between each Widget in the list. When all children are available ahead of time ListTile.divideTiles works, but there is no easy way to get the same effect with the ListView.builder interface aside from wrapping/decorating each built element.

Is there any progress on this? It seems really weird that there is no inbuilt way to do this.

When this issue is complete make sure to update the flutter tutorial here : https://flutter.io/get-started/codelab/
It uses a hack to add dividers so once this is complete it should use the built in API.

Have you tried https://docs.flutter.io/flutter/material/Divider-class.html?

Support for ListView separators was added here: https://github.com/flutter/flutter/pull/18619
@willlarche - maybe new ListView.separated() could be incorporated into a codelab update.

@HansMuller doesn't using ListView.separated with a Divider not follow the Material spec? It looks like ListView.separated adds a divider between each item. IIRC the Material spec mandated that the divider should be placed at the bottom of each item, on top of its padding.
The old spec says this ("Placement: Along the bottom edge of content tiles") but I guess the new spec website doesn't. Maybe it was changed?

The current spec isn't terribly strong on this point but it does include this:

Do.
Place a divider between rows with lots of content, such as those with three-line lists.

Most of the spec examples with dividers seem to put them (just) in between items.

@HansMuller  Am I misinterpreting the issue, or isn't ListView.separated incompatible with ListView.builder? Which is what the whole point of this issue, in which case it should not be closed with this argument!

I don't intend to add support for automatically including dividers for the general ListView.builder case.
@dguralnick - if ListView.separated didn't address your requirements, I'll be happy to reopen this issue.

@SUPERETDUPER @HansMuller

https://flutter.io/get-started/codelab/#step-4-create-an-infinite-scrolling-listview
The so called "hack" does not work if you generate a list with json or database because it will replaced odd index values with a divider instead of the actual element with a divider underneath it. It's hardly a solution. Why has this issue been closed exactly?

I hope we didn't refer to it as a "hack".
If you have a list of N database or JSON items then creating a ListView whose itemCount is N * 2 and doing the arithmetic to distinguish item indices from data indices in the item builder shouldn't be a problem.
The solution would be the same for an unbounded list. In either case the item index is the index of the list item - a divider or a data item - rather than the data item. The index of the data item is i ~/ 2.

@HansMuller
I think the issue should be reoppened and divider functionality should be added to ListView.builder.
A couple advantages to doing this

Make people less confused (ex. @JosephDunivan )
Define a best practice/standard (ex. decorate items or add a divider every second item)
Reduce amout of code the developer must write (and therefor the chance of bugs)
Make it feel less hackish

Being able to have dividers between items seems like a standard feature. There could be a simple boolean switch in the constructor.


Print debug information

we should add -i to curl to get the headers

Good idea.

we can split the "Install Koyeb CLI" step into two steps:

I agree, makes things clearer.

Also, it would be great to allow the action to be run more than once.

I added a step to check this before everything else, let me know if you would have done it differently.

I didn't try to run the action, but it looks good! Thanks a lot!