QT Creator Setup

Hello,
I have noticed on your slides titled "Open-TEE – A Virtual Trusted Execution Environment" it shows screenshots of the project code running in QT Creator. I'm trying to get it to run in QT Creator, is there any documentation I'm missing somewhere for this?
If not could I get some help in setting this up or links that might help me do so?
Cheers,
Jorden

Hi Jorden,
After a full repo sync of the Open-TEE directory. I just run:
Open-TEE $ qtcreator project.qbs &
Then bottom left of the qtcreator window select the project you want to run
to be  opentee-engine.
Then you need to edit your /etc/opentee.conf file to have something similar
to the following:
$ cat /etc/opentee.conf
[PATHS]
ta_dir_path =
/home/brian/code/ccpp/build-project-Desktop-Debug/qtc_Desktop_7bb86f62-debug/TAs
core_lib_path =
/home/brian/code/ccpp/build-project-Desktop-Debug/qtc_Desktop_7bb86f62-debug
opentee_bin =
/home/brian/code/ccpp/build-project-Desktop-Debug/qtc_Desktop_7bb86f62-debug/opentee-engine
#ta_dir_path = /home/brian/code/ccpp/Open-TEE/gcc-debug/TAs
#core_lib_path = /home/brian/code/ccpp/Open-TEE/gcc-debug
#opentee_bin = /home/brian/code/ccpp/Open-TEE/gcc-debug/opentee-engine
subprocess_manager = libManagerApi.so
subprocess_launcher = libLauncherApi.so
As you can see the first 3 entries need to point towards the build path
where creator is dumping the output.
Then when you run the project it should run just fine. We have seen a
problem with newer versions of QtCreator not following the child process
after the fork, we have yet to determine the cause. I encountered the
similar problem with another project the other day, but I have not had time
to resolve it yet. Older versions worked just fine.
Br,
Brian
On Tue, Oct 6, 2015 at 2:04 PM, Jorden Whitefield<EMAIL_ADDRESS>wrote:

Hello,
I have noticed on your slides titled "Open-TEE – A Virtual Trusted
Execution Environment" it shows screenshots of the project code running in
QT Creator. I'm trying to get it to run in QT Creator, is there any
documentation I'm missing somewhere for this?
If not could I get some help in setting this up or links that might help
me do so?
Cheers,
Jorden
—
Reply to this email directly or view it on GitHub
https://github.com/Open-TEE/project/issues/11.

If the Qt Creator is not parsing the Qbs project: In QT Creator: Help ->
About Plugins -> Select QbsProjectManager box
At least at older version this was not a default setting..
-Tanel
2015-10-06 14:15 GMT+03:00 Brian McGillion<EMAIL_ADDRESS>
Hi Jorden,
After a full repo sync of the Open-TEE directory. I just run:
Open-TEE $ qtcreator project.qbs &
Then bottom left of the qtcreator window select the project you want to run
to be opentee-engine.
Then you need to edit your /etc/opentee.conf file to have something similar
to the following:
$ cat /etc/opentee.conf
[PATHS]
ta_dir_path =
/home/brian/code/ccpp/build-project-Desktop-Debug/qtc_Desktop_7bb86f62-debug/TAs
core_lib_path =
/home/brian/code/ccpp/build-project-Desktop-Debug/qtc_Desktop_7bb86f62-debug
opentee_bin =
/home/brian/code/ccpp/build-project-Desktop-Debug/qtc_Desktop_7bb86f62-debug/opentee-engine
#ta_dir_path = /home/brian/code/ccpp/Open-TEE/gcc-debug/TAs
#core_lib_path = /home/brian/code/ccpp/Open-TEE/gcc-debug
#opentee_bin = /home/brian/code/ccpp/Open-TEE/gcc-debug/opentee-engine
subprocess_manager = libManagerApi.so
subprocess_launcher = libLauncherApi.so
As you can see the first 3 entries need to point towards the build path
where creator is dumping the output.
Then when you run the project it should run just fine. We have seen a
problem with newer versions of QtCreator not following the child process
after the fork, we have yet to determine the cause. I encountered the
similar problem with another project the other day, but I have not had time
to resolve it yet. Older versions worked just fine.
Br,
Brian
On Tue, Oct 6, 2015 at 2:04 PM, Jorden Whitefield <
<EMAIL_ADDRESS>wrote:

Hello,
I have noticed on your slides titled "Open-TEE – A Virtual Trusted
Execution Environment" it shows screenshots of the project code running
in
QT Creator. I'm trying to get it to run in QT Creator, is there any
documentation I'm missing somewhere for this?
If not could I get some help in setting this up or links that might help
me do so?
Cheers,
Jorden
—
Reply to this email directly or view it on GitHub
https://github.com/Open-TEE/project/issues/11.

—
Reply to this email directly or view it on GitHub
https://github.com/Open-TEE/project/issues/11#issuecomment-145824794.

Thank you both very much for your speedy responses.
@brianmcgillion I am trying the method you described but when parsing the qbs project file it gives me the following error:
/home/jorden/Android/Open-TEE/project/qbs/modules/OpenSSL/OpenSSL.qbs:3: error: Items of type 'Module' cannot contain items of type 'Probe'.
I also assume it is for this reason that I don't get the choice to run the opentee-engine. Sorry I'm a newbie to QT Creator and well TEE's in general. Really excited to get started in using and understanding TEE's.
Thanks for your time.

What version of QtCreator are you running there ?
On Tue, Oct 6, 2015 at 2:35 PM, Jorden Whitefield<EMAIL_ADDRESS>wrote:

Thank you both very much for your speedy responses.
@brianmcgillion https://github.com/brianmcgillion I am trying the
method you described but when parsing the qbs project file it gives me the
following error:
/home/jorden/Android/Open-TEE/project/qbs/modules/OpenSSL/OpenSSL.qbs:3:
error: Items of type 'Module' cannot contain items of type 'Probe'.
I also assume it is for this reason that I don't get the choice to run the
opentee-engine. Sorry I'm a newbie to QT Creator and well TEE's in general.
Really excited to get started in using and understanding TEE's.
Thanks for your time.
[image: screenshot from 2015-10-06 12 31 26]
https://cloud.githubusercontent.com/assets/1949133/10307364/3a25b7f6-6c26-11e5-9515-b14c8171dc94.png
—
Reply to this email directly or view it on GitHub
https://github.com/Open-TEE/project/issues/11#issuecomment-145828836.

QT Creator 3.1.1
QBS 1.5.0

There has been quite heavy development with qbs recently, and especially
the one bundled with qtcreator, so I would suggest that you take the latest
stable qtcreator which is at version 3.5:
http://www.qt.io/download-open-source/
On Tue, Oct 6, 2015 at 2:41 PM, Jorden Whitefield<EMAIL_ADDRESS>wrote:

QT Creator 3.1.1
QBS 1.5.0
—
Reply to this email directly or view it on GitHub
https://github.com/Open-TEE/project/issues/11#issuecomment-145831077.

Hello Brian,
Thank you so much this has solved the problem and I can now build it in QtCreator.


Rename project

We've decided that the HAPI server and the HAPI adapters for LaTiS are separable and probably belong in different repositories.
This repository is for the HAPI server, so we will rename it hapi-server and change the package names so hapi is the top-level name. We'll want to also update the description and README to reflect the new focus, namely a HAPI server implemented using LaTiS.
When we begin work on the adapters we'll do that as a subproject in the main LaTiS repository.

I feel a little uncomfortable with using hapi-server as the project name and using hapi as the top-level package name.
We want to be clear that this is a generic HAPI server and not tied to us or our data in any particular way, but it is a specific HAPI server developed at LASP, not the HAPI server.
I don't know what to call the project, but I could imagine using lasp.hapi as the package.

I went ahead and changed the repo description.

Per an offline discussion:

rename the repository to hapi-server

it can always be renamed to something even more appropriate/specific later
implementations of specs are often given names (e.g. Hyrax, ERDDAP), but we want to stick with the HAPI branding for now

make latis.hapi the package


Delete redundant .coffeelintignore file

Description of the Change
This is a janitorial PR to delete an unused .coffeelintignore manifest that's sitting in the package's root directory.
There is no specs/fixtures directory, so this file is contributing absolutely nothing.

Happy to do whatever I can to purge the memory of CoffeeScript from the world.

@mnquintana Asking you since you were the one who standardized the Coffeelint rules across Atom.  Are you ok with this file being removed, as it's highly unlikely the language repos will ever get fixture files?

@50Wliu I believe you've asked him before.

Oh yeah, go for it 👍

I'll try to remember this time :P.


Rock Paper Scissor

#This is a code for Rock paper scissor game using the random function.

Please provide meaningful variable names in Pattern making of numbers


Pomodoro stop issue #window

I am using the version v7.3.333 on Windows.
In perferences, I open Pomodoro Timer for 25mins, when 25mins is over, Toggl will popup a tips, but it start a new record in the same time, So I click the contiune or create new, it is the same effect.
I don't know is this is a problem? I used an app call "SwipeTimer" on my android device, it also has a option to set how minutes after will alert me. But it will not start a new record.
I just want when the Pomodoro over, the button in pop window do this:

continue: keep the lastest record and go on
create new: if set Promdoro Breat Time, enter breat Time record, otherwise, it record the lastest Promodoro record, and record a new base current time.

Hi,
You are using a development version of the app. Latest stable release is 7.3.326. We are adding Pomodoro Break functionality that tracks breaks right after Pomodoro time ends. Pomodoro Break can be disabled from settings. If Pomodoro Break is not enabled no time entry is started at Pomodoro time end.
This is still in development so there can be bugs with the functionality.

In v7.3.326, it doesn't have the Pomodoro Break option, but when the Promodoro done, it also auto start a new record, whenever I click continue or create new...
I think when the Pomodoro done, Toggl should not immediately over current record and auto record a new one.
Hope Pomodoro will soon integration with Toggl, I am just using Toggl a week, but deep love it :)

Hi

continue: keep the lastest record and go on
To make the same entry continue you have to select "Save duration only" from the web app.
Go to https://toggl.com/app/profile

Then app will no create new entry and will continue tracking the same that was tracking before Pomodoro time ended.

Got it.
I have select "Save duration only", But there is another issuse:
When Pomodoro done, I click continue, Toggle tips me pomodoro done again.
I think its a bug,  Toggl use current recorded total time compare with Pomodoro Time, right?

Yes, There seems to be issue with continuing entry that has a duration larger than Pomodoro Timer. I'll work on a fix.
Thank you for your feedback.

duplicate of #1984


Debug tests written in Typescript

Is it possible?

Yes, I do it with a custom launch Jon - should really build that into here
On May 25, 2017 21:12, "Cesar Varela"<EMAIL_ADDRESS>wrote:

Is it possible?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/orta/vscode-jest/issues/115, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAC_jhZl6E_OEhjtldjce6cHNCsP3550ks5r9eCtgaJpZM4Nm1Y-
.

Can you share it with me?

I'm on a phone, vheck artsy/emission
On May 26, 2017 16:47, "Cesar Varela"<EMAIL_ADDRESS>wrote:

Can you share it with me?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/orta/vscode-jest/issues/115#issuecomment-304317570,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAC_jh9TR0zHu4EiHasNrj7Ni318Yh7kks5r9vQTgaJpZM4Nm1Y-
.

I'm closing this since now we moved to plain ol' js


Null reference exception using dump --format json on DRM protected file

Trying to extract the chapters from a DRM protected file and write to a file so I can write them back into the non-DRM protected version.  I can dump the chapters using the standard format, and manually edit this into a standard chapter format, but this is time consuming.
Trying this command so I can automate all files:
tone dump drmfilename.m4b --include-property chapters --format json > chapters.json
Then write back with this command:
tone tag nodrmfilename.m4b --meta-tone-json-file="chapters.json" --auto-import="tonejson"
When I try to dump the chapters with the json format I get a null reference exception.  Debugging the application, turns out that track.ChannelsArragement is null on these files.   So, the SerializeAsync method fails with the null reference exception on this line:
Channels = new { Count = track.ChannelsArrangement.NbChannels, Description = track.ChannelsArrangement.Description },
I tried it with this line commented out and I was able to write the file fine without the Channels info and the nodrm file kept its existing Channels info.
Great tool btw!

Hey thanks for this detailed report.

Trying to extract the chapters from a DRM protected file and write to a file so I can write them back into the non-DRM protected version.

Interesting approach :-)

When I try to dump the chapters with the json format I get a null reference exception. Debugging the application, turns out that track.ChannelsArragement is null on these files.

Ah I see, I did not know that this is even a possibility. Unfortunately, due to this exception it is not possible to workaround this issue by using tone.json format.
However, it would have been possible to use ffmetadata or ChptFmtNativeformat to overcome this, if there was a feature to auto-import / export and vice versa these :-/
 # no import possible
tone dump --format=ffmetadata 'audiobook.m4b' --include-property=chapters

# no export / dump possible
tone tag --auto-import=chapters 'audiobook.m4b'

So in a series of unfortunate events, I think you have to wait until this is fixed in the next release - I think I'll fix this pretty quick, but the next release will take some time.
Can you build a latest code version on your own?
Seems that I have to fix / add a few things here:

[ ] Handle the fact, that track properties, that can be null on encrypted files (most important)
[ ] Add possibility --auto-import=ffmetadata
[ ] Add possibility to dump --format=ChptFmtNative
[ ] Think over a nightly build for early adopters (the brave people)
[ ] (Maybe add a parameter --exclude-leaf='audio' to skip whole parts of the dump, when using json) => this is something I have to think about

Trying to extract the chapters from a DRM protected file and write to a file so I can write them back into the non-DRM protected version.

Interesting approach :-)

Well, it would have been better if I had found a utility that would just strip the encryption so I could play the audiobooks on non-iTunes players and not lose the chapters.  :-)

Can you build a latest code version on your own?

Yes, I was able to comment out the offending line, build and run from within Visual Studio.  I didn't spend a lot of time, but I would have to figure out how you created the portable exe version.

So in a series of unfortunate events, I think you have to wait until this is fixed in the next release - I think I'll fix this pretty quick, but the next release will take some time.

I'm not in a huge rush.  I can wait until you get it fixed, and then I'll work on updating my library.  This is a winter project anyways. :-)

I didn't spend a lot of time, but I would have to figure out how you created the portable exe version.

This is easy, take a look at https://github.com/sandreas/tone/blob/main/tone/build.sh (you have to adjust the runtime id) or simply fork and run ./release.sh 0.1.1, then github will do the rest for you.

I'm not in a huge rush. I can wait until you get it fixed, and then I'll work on updating my library. This is a winter project anyways. :-)

Great, then I can take the time to fix this and some other things. Thank you for the quick feedback.

Ok, should be fixed in the latest commits. You can now also use
tone dump --format=ChptFmtNative my-file.m4b

to get a chapters.txt only dump, which then can be used for --auto-import=chapters
I would really appreciate feedback if this fixes it for you.

Works like a charm!  Either format will do what I need!  Thanks for fixing it so quickly.


Feature proposal: ng add apollo-angular

Angular CLI 6.0 introduced a new command - ng add. It allows plugin authors to add an installation script to their npm packages. That script will be executed whenever someone installs the plugin with ng add my-plugin.
The script should be implemented as a schematic in order to be executed by the Angular CLI.
ng add apollo-angular
The initial setup of apollo-angular can be automated by enabling ng add. It should do the following:

Installs the apollo-angular plugin.
That happens automatically because the Angular CLI will execute npm install apollo-angular, whenever someone executes ng add apollo-angular.

Installs the other dependencies and add them to the project's package.json.(apollo-angular-link-http apollo-link apollo-client apollo-cache-inmemory graphql-tag graphql).

Adds an NgModule with an initial setup to the project.

// graphql.module.ts
import { NgModule } from '@angular/core';

import { ApolloModule, APOLLO_OPTIONS } from 'apollo-angular';
import { HttpLinkModule, HttpLink } from 'apollo-angular-link-http';
import { InMemoryCache } from 'apollo-cache-inmemory';

const uri = ''; // <-- add the URL of the GraphQL server here
export function createApollo(httpLink: HttpLink) {
  return {
    link: httpLink.create({ uri }),
    cache: new InMemoryCache(),
  };
}

@NgModule({
  exports: [
    ApolloModule,
    HttpLinkModule
  ],
  providers: [
    {
      provide: APOLLO_OPTIONS,
      useFactory: createApollo,
      deps: [HttpLink],
    },
  ],
})
export class GraphQLModule { }

Imports the GraphQLModule and HttpClientModule to the root NgModule.

// app.module.ts
import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { HttpClientModule } from '@angular/common/http';

import { AppComponent } from './app.component';
import { GraphQLModule } from './graphql.module';

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    HttpClientModule,
    GraphQLModule,
    BrowserModule
  ],
  providers: [],
  bootstrap: [AppComponent]
})
export class AppModule { }

With these changes done automatically, the project should be ready to use the apollo-angular plugin.
Please share any comments or suggestions :)

#779

"lib": [
"es6",
"dom",
"esnext"
],
fixed my issue. Thank you guys


Boolean value true is bolded in dynamic snippet when using some_field=true in query

(opening issue per discussion in the Vespa slack)
Describe the bug
Imagine a document which contains the word true, the word false, and the word baz.  And imagine the following yql:
select * from sources foodoc
where active=true
and default contains "baz" limit 2;

With that query, my dynamic snippet field with bolding works great, but both true and baz are bolded from the snippet source text.  I would have expected only baz to be bolded.  As a workaround, I can use !(active=false) and it works as expected (no bolding of false for instance).
Is this expected, or possibly a bug?
Expected behavior
My expectation would be the word true is not bolded, since it's a boolean value (active=true).
Screenshots
none
Environment (please complete the following information):
docker, single node on mac os or linux (happens on both)
Vespa version
7.585.20
Additional context
Per the discussion in slack, I've applied a filter annotation as a work around.  See the example below, which works great.  However, the discussion indicated the above is still possibly a bug, so I went ahead and opened this issue.
select * from sources foodoc
where ({filter:true}active=true)
and default contains "baz" limit 2;

Thanks for reporting this issue. This uncovered a fundamental bug in summary fields using dynamic or bolding, where query terms not searching the source field were still used during bolding calculation. This has been fixed in Vespa 8.117.40 (https://github.com/vespa-engine/vespa/pull/25768). More system tests added in https://github.com/vespa-engine/system-test/blob/master/tests/search/bolding/bolding_multiple_fields.rb.


feat: use new dedicated websocket server

@nicolasburtey / @krtk6160 ,
The web wallet code in the PR works with the dedicated websocket server locally and in my local dev charts environment but not in staging when I call authenticated subscriptions using cookies. I am not sure why?
To reproduce you can pull this code down and set these .envrc settings:
export NETWORK="signet"
export GRAPHQL_URL="https://api.staging.galoy.io/graphql"
export GRAPHQL_SUBSCRIPTION_URL="wss://ws.staging.galoy.io/graphql"
export GALOY_AUTH_ENDPOINT="https://api.staging.galoy.io/auth"

I get this error below, when testing an authenticated subscription to myUpdates:
{message: "Not Authenticated for subscription", locations: [{line: 2, column: 3}], path: ["myUpdates"],…}

Relevant honeycomb traces. https://ui.honeycomb.io/galoy/datasets/galoy-staging/result/ptskBRBGrgQ?tab=raw
Any ideas? I wonder if oathkeeper or nginx is not passing the cookies properly


vo-amrwbenc: init at 0.1.3

Motivation for this change
Adding new package for AMR-WB encoder/
Things done

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

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

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Do I need to find a way to test this on NixOS and/or macOS?

Works find on macOS for me. Can you add "platforms = stdenv.lib.platforms.unix;" to meta?

Done :)


WISE support setting separate fields

Currently wise design choices favor the ability to cache results which has lead to some big limitations, especially around IPs. For example with the current design it is not possible to set a different fields based on if an ip is src or dst.
For example if <IP_ADDRESS> is foo, <IP_ADDRESS> is bar, <IP_ADDRESS> is proxy with http traffic of <IP_ADDRESS> -> <IP_ADDRESS> and XFF=<IP_ADDRESS> wise might set the asset=foo,bar,proxy where really you might want asset.src=foo, asset.dst=bar,http.asset=proxy.
Two general approaches

Continue to send wise the ip lookups and capture remaps the fields.
<IP_ADDRESS>, wise returns asset=foo, capture remaps to asset.src=foo
<IP_ADDRESS>, wise returns asset=bar, capture remaps to asset.dst=bar
<IP_ADDRESS>, wise returns asset=proxy, capture remaps to http.asset=proxy

query wise with both the ip AND the field the ip was from
<IP_ADDRESS>;ip.src, wise returns asset.src=foo
<IP_ADDRESS>;ip.dst, wise returns asset.dst=bar
<IP_ADDRESS>;http.xffip wise returns http.asset=proxy

Pros:
1 - no change to wise
1 - fixes current wise sources
2 - super flexible and clear what is happening
Cons:
1 - can't have wise sources that only do ip lookups for some of the fields
1 - setting the results is a little slower/complex
2 - at least 2x queries to wise for ips since ip.src and ip.dst lookups are now different
2 - wise ip cache is 2x because 2x the queries/results
2 - all the sources have to be updated
I'm leaning towards solution (1) and fixing the limitations by allowing [wise-types] to support other ip queries AND passing the wise-type into the getIp callback (if full query is turned on)
[wise-types]
outersrc=kind:ip;outputip.src
outerdst=kind:ip;outputip.dst

I agree I think 1 is a good compromise that increases flexibility without the performance hit.
Also 1 is only really a problem if you have enrichment sources that have data for both ip.src and ip.dst or outerip.src and outerip.dst for example which duplicates the lookup if you're only having capture care about ip.dst for example. So as long as wise has a snappy return for null results this makes perfect sense to me.

This was completed in #2517 https://arkime.com/settings#custom-fields-remap


.sass media query won't precompile

Not sure if this is the right place.
Simple responsive.sass:
// Anything smaller than XS
@media(max-width:767px)

//Anything larget than SM
@media(min-width:768px)

// Anything smaller than MD
@media(max-width:991px)
  body
    padding-bottom: 566px

// Anyting larger than MD
@media(min-width:992px)

@media(min-width:1200px)

Running rake assets:precompile it complains:
Sass::SyntaxError: Invalid CSS after "...ax-width:767px)": expected "{", was ";"
  (in /Users/nitsujri/ruby/testproj/app/assets/stylesheets/application.sass)
(sass):12350

If I

Change the file to responsive.scss
Put the brackets in
Run precompile

It works as expected.

Are you able to make it work without Rails?

@rafaelfranca, I'm not sure how to do that. Could you point me? Gladly run the test.

Try:
gem install sass
sass responsive.sass

Ugh, I kept working on the project and the problem doesn't reproduce, of course. Thanks for the time and all that you do, @rafaelfranca.


Separate IHttpProxy and Transforms

IHttpProxy is getting much more attention/usage than most other parts of YARP. Long term we're interested in moving that component into ASP.NET Core. However, IHttpProxy also brings in the entire transforms infrastructure which it's not clear if people using IHttpProxy directly need, or if they could use a simplified model (e.g. callbacks).
It's going to be a pretty significant design change. It would require at least three callbacks for the different stages of the request:

Request creation (multiple steps)

Method, Version, url parts
HttpContent creation
Request headers (split across the request and the content)

Request trailers (future)
Response headers
Response trailers

I'm not sure how incremental the callback logic could be, or if each callback would have to duplicate all of the default logic it was replacing. In the simplest case the default logic runs first and then the transforms try to fix up the HttpRequestMessage afterwards, but this results in redundant work like dis-assembling and re-assembling the uri for every modification, or removing headers that you don't want forwarded, when it would have been better not to copy those headers in the first place.
I'll do some experiments and see what it would take to separate these two.

Significant API break, so needs to be in 1.0

@davidfowl here's a first draft I have working at the IHttpProxy layer:
    public record HttpTransforms
    {
        public static readonly HttpTransforms Empty = new HttpTransforms();

        /// <summary>
        /// Indicates if all request headers should be copied to the outgoing HttpRequestMessage before invoking
        /// OnRequest. Disable this if you want to manually control which headers are copied.
        /// Note this copy excludes certain protocol headers like HTTP/2 psuedo headers (":authority").
        /// </summary>
        public bool CopyRequestHeaders { get; init; } = true;

        /// <summary>
        /// Indicates if all response headers should be copied from the received HttpResponseMessage before invoking
        /// OnResponse. Disable this if you want to manually control which headers are copied.
        /// Note this copy excludes certain protocol headers like `Transfer-Encoding: chunked`.
        /// </summary>
        public bool CopyResponseHeaders { get; init; } = true;

        /// <summary>
        /// Indicates if all response trailers should be copied from the received HttpResponseMessage before invoking
        /// OnResponseTrailers. Disable this if you want to manually control which headers are copied.
        /// </summary>
        public bool CopyResponseTrailers { get; init; } = true;

        /// <summary>
        /// A callback that is invoked prior to sending the proxied request. All HttpRequestMessage fields are
        /// initialized except RequestUri, which will be initialized after the callback if no value is provided.
        /// The string parameter represents the destination URI prefix that should be used when constructing the RequestUri.
        /// The headers will be copied before the callback if CopyRequestHeaders is enabled.
        /// </summary>
        public Func<HttpContext, HttpRequestMessage, string, Task> OnRequest { get; init; }

        /// <summary>
        /// A callback that is invoked when the proxied response is received. The status code and reason phrase will be copied
        /// to the HttpContext.Response before the callback is invoked, but may still be modified there. The headers will be
        /// copied to HttpContext.Response.Headers before the callback if CopyResponseHeaders is enabled.
        /// </summary>
        public Func<HttpContext, HttpResponseMessage, Task> OnResponse { get; init; }

        /// <summary>
        /// A callback that is invoked after the response body to modify trailers, if supported. The trailers will be
        /// copied to the HttpContext.Response before the callback if CopyResponseTrailers is enabled.
        /// </summary>
        public Func<HttpContext, HttpResponseMessage, Task> OnResponseTrailers { get; init; }
    }

I'll see how well I can re-layer the other transform model on top.


How to find user base on an accessToken using findOne?

Just a question.
I want to find a user based on their access token.
Can you guide me how to do that?
Thanks

@nguyenhuutinh
is this what you are looking for? req.route.meta.user;
example - https://github.com/ngduc/node-rem/blob/master/src/api/controllers/user.controller.ts#L127


Remove tasers from arsenal tech

About the PR

Tasers are highly controversial and, though they are rare due to the cost of unlocking, when they are present in rounds they exacerbate the worst aspects of stun meta. Extremely hard to counter, they really just turn nukeops and revs rounds into a rush for arsenal so sec can play cleanup.
now that we have an alternative T3, i really don't mind cutting them.

Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

remove: Removed the Handheld Electrical Propulsion technology and its associated item, tasers, from research.

never thought I'd see the day where emogarbage argued for the removal of tasers

tier 3 x-ray cannons when

Why not just make tasers unable to penetrate a spacesuit? Scientists rarely unlock them anyway


Set outgouing interface

Hello,
I tried to implement useful feature - send packets from specific network interface.
This feature is platform specific (depend on syscall.BindToDevice).
Hoping I did it correctly. Test successfully passed on Linux OS.
Thanks!

Yes, I think problem in circleci environment because syscall return "socket: permission denied".
Maybe absent some Linux capabilities (example: CAP_NET_ADMIN).
utils_linux.go:52
func (c icmpConn) BindToDevice(ifName string) error {
if fd := getConnFD(c.c); fd >= 0 {
**		return syscall.BindToDevice(fd, ifName)*
}
return errors.New("bind to interface unsupported")
}

It may be possible to run the tests if we change from running in a Go docker image to a machine build. But we would have to script setting up Go inside the machine.
The other option is to make this not included in short test.

I have added a "-short" flag in Makefile and made a few changes in my Test (skip).
But circleci pipeline breakes in "goreleaser" stage (integrity check error).

Unfortunately I agree with @mem here - I don't think that poking around in the internals of other packages is something we should be doing in go-ping. I appreciate that this is really useful, but I think it's better proposed as a change request upstream to the icmp.PacketConn package itself.


gpu enabled node(s) not advertising nvidia.com/gpu resource

According to the cluster machine-set, we should have one node that is gpu-enabled, but none of the nodes show the standard nvidia.com/gpu resource to allow scheduling based on gpu resource
[eje@localhost ~]$ oc get node -o jsonpath="{range .items[*]}{..allocatable}{'\n'}{end}"

map[attachable-volumes-aws-ebs:25 cpu:7500m ephemeral-storage:114396791822 hugepages-1Gi:0 hugepages-2Mi:0 memory:30954864Ki pods:250]
map[attachable-volumes-aws-ebs:25 cpu:7500m ephemeral-storage:114396791822 hugepages-1Gi:0 hugepages-2Mi:0 memory:30954864Ki pods:250]
map[attachable-volumes-aws-ebs:25 cpu:15500m ephemeral-storage:114396791822 hugepages-1Gi:0 hugepages-2Mi:0 memory:30953132Ki pods:250]
map[attachable-volumes-aws-ebs:25 cpu:3500m ephemeral-storage:114396791822 hugepages-1Gi:0 hugepages-2Mi:0 memory:14784740Ki pods:250]
map[attachable-volumes-aws-ebs:39 cpu:3500m ephemeral-storage:114396791822 hugepages-1Gi:0 hugepages-2Mi:0 memory:61706180Ki pods:250]
map[attachable-volumes-aws-ebs:25 cpu:7500m ephemeral-storage:114396791822 hugepages-1Gi:0 hugepages-2Mi:0 memory:30954864Ki pods:250]
map[attachable-volumes-aws-ebs:25 cpu:3500m ephemeral-storage:114396791822 hugepages-1Gi:0 hugepages-2Mi:0 memory:14784740Ki pods:250]
map[attachable-volumes-aws-ebs:25 cpu:7500m ephemeral-storage:114396791822 hugepages-1Gi:0 hugepages-2Mi:0 memory:31298928Ki pods:250]
map[attachable-volumes-aws-ebs:25 cpu:7500m ephemeral-storage:114396791822 hugepages-1Gi:0 hugepages-2Mi:0 memory:30954864Ki pods:250]
map[attachable-volumes-aws-ebs:25 cpu:3500m ephemeral-storage:114396791822 hugepages-1Gi:0 hugepages-2Mi:0 memory:14784740Ki pods:250]

Can we please get this resolved (i.e., make a plan to have the cluster use the GPUs that are preferred in the zone that we are using)?
@dvizzini107

@MichaelTiemannOSC we have currently at least 3 nodes with enabled GPU's (older models) , we will increase this number to 4 . Plan is to see if we can use current GPU enabled nodes (p2 instances) for the tasks related to  COP26 presentation.  I believe that we were able to successfully deploy test notebook that uses gpu , next step is to adapt the actual pipeline to use these nodes  (@erikerlandson  correct me if I am wrong) .  Considering that to move to different availability zone we need to provision new OCP cluster it makes sense to do this transition post COP26 (to avoid disruptions and have solidified platform and configuration ) . I think that this issue can be closed at this point and track remaining tasks in separate tickets

This is fixed, and we have verified jupyter notebook can access the gpus


Command translation is broken

The command description in the extension info's "Feature Contributions" section is broken.

Hi @hyangah, thank you for reaching out.
The strings being shown (%python.command.....%) are what we use to localize our commands inside the extension, however the page you're seeing is managed by the marketplace, which doesn't seem to support nls-based localization yet: https://github.com/microsoft/vscode/issues/3289. Feel free to upvote https://github.com/microsoft/vscode/issues/3289 to help prioritize it.
Closing in favour of https://github.com/microsoft/vscode/issues/3289.
Thank you!


Don't add TEEC_TEST_LOAD_PATH into TA search paths

Description of changes
This is to supplement PR #103

By default, tee-supplicant prepends "/foo:/bar::/baz" into the TEEC_LOAD_PATH. Add a patch which removes that.
Export buildOpteeTaDevKit to make it easier to build TAs in other flakes

Testing
AGX devkit and NX devkit

For that patch you have, wouldn't we just need to remove the hardcoded #define TEEC_TEST_LOAD_PATH that optee has and that should suffice? It would make the patch much easier to maintain going forward. It looks like CFG_TEST_TA_PATH already defaults to off.

#132 exposes the built ta-dev-kit, let me know if this implementation would work for your use case.

For that patch you have, wouldn't we just need to remove the hardcoded #define TEEC_TEST_LOAD_PATH that optee has and that should suffice? It would make the patch much easier to maintain going forward. It looks like CFG_TEST_TA_PATH already defaults to off.

Actually this issue is present in the OP-TEE upstream (and not only NVIDIA's fork) and I opened an issue and PR there:
https://github.com/OP-TEE/optee_client/issues/357
https://github.com/OP-TEE/optee_client/pull/358

But yes you are right, the proper fix is much more bigger

Now I force-pushed a simplified version of this PR and the patch in it. Given that the #132 also gets merged the TA support is now convenient enough


Support for 'undelete' of storage containers

Is your feature request related to a problem? Please describe.
We are unable to 'undelete' storage containers using the Azure CLI. Expecting an option like az storage container undelete on the page with all the other container commands.
We can do this via the Azure browser UI - see here: https://raw.githubusercontent.com/dvasdekis/images/master/azure_container_undelete.png
Describe the solution you'd like
New command: az storage container undelete
Describe alternatives you've considered
Doing it via the UI - but we don't do things this way! Everything is programmatic here.
Additional context
Will be creating an issue in the Terraform provider to support this once it's enabled here.

storage

You can install cli extension storage-blob-preview by
az extension add -n storage-blob-preview

and then try
az storage container restore

az storage container restore

This works great, thank you, sorry I didn't see it!


Unable to build site locally

Experiencing the following errors trying to build the website locally:
Error: Error building site: "/home/cdaley/go/src/github.com/shipwright-io/website/content/en/blog/posts/2020-10-21-intro-shipwright-pt1/index.md:34:1": failed to extract shortcode: template for shortcode "imgproc" not found

Error: Error building site: "/home/cdaley/go/src/github.com/shipwright-io/website/content/en/_index.html:7:1": failed to extract shortcode: template for shortcode "blocks/cover" not found

Guess I had some weird path issues on my workstation.

cdaley@redhat [~/go/src/github.com/shipwright-io/website] (main)
$ hugo version
Hugo Static Site Generator v0.74.3-DA0437B4/extended linux/amd64 BuildDate: 2020-07-23T16:30:30Z
cdaley@redhat [~/go/src/github.com/shipwright-io/website] (main)
$ make build
rm -rf public/*
hugo -t docsy --minify
Total in 12 ms
Error: Error building site: "/home/cdaley/go/src/github.com/shipwright-io/website/content/en/_index.html:7:1": failed to extract shortcode: template for shortcode "blocks/cover" not found
make: *** [Makefile:7: build] Error 255

I did not, I will give it a try.
Where are the Docsy docs located?

Where are the Docsy docs located?

https://www.docsy.dev/docs/


[stable/hlf-peer] fix typo

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/ok-to-test

/approved

/lgtm


ROX-9802: Replace docker repositories with quay

Description
In order to remove docker hub images completely from the repository, references have been changed to point to the quay.io alternatives of the repositories.
The logic used to choose between stackrox-io and rhacs-eng is to keep anything that could be used by a community member in stackrox-io (i.e make targets, documentation) and anything used privately by CI in rhacs-eng, although they should be interchangeable so we might want to add some of the missing repos in stackrox-io and move on to use only that repository in a follow up PR.
Checklist

[x] Investigated and inspected CI test results
[ ] Updated documentation accordingly

Automated testing

[ ] Added unit tests
[ ] Added integration tests
[ ] Added regression tests

If any of these don't apply, please comment below.
Testing Performed
Every modified CI step needs to be tested using the proper labels in the PR.
Some make targets might need to be run manually.

The dockerized check failures step is expected to fail, everything else seems to be working correctly so I'm opening the PR up for review.


Option text (--option) same as background on Solarized Dark theme

Using Powershell, and the Solarized Dark theme, any text preceded by, and including a "-" is the same as the background color.  This is assumed to be due to the definition of "background" and "brightBlack" being identical -> #002B36

Environment
Win32NT             10.0.18362.0 Microsoft Windows NT 10.0.18362.0
Any other software?

# Steps to reproduce

<!-- A description of how to trigger this bug. -->

# Expected behavior

<!-- A description of what you're expecting, possibly containing screenshots or reference material. -->
Visible text, i.e. changing the Solarized Dark "brightBlack" definition to #777777 the text displays as expected
# Actual behavior

<!-- What's actually happening? -->
Text not visible

Yeah, the solution here is "we should not have shipped Solarized as a stock theme" moreso than "it is broken"


Elasticache : Unable to use cluster configuration endpoint

Hello @mrniko
We are using redisson version 3.18.0 on our production application and are using Elasticache in cluster mode.
As per the recommendation from AWS we need to use cluster configuration endpoint. However when we tested with the same it is not able to connect to the cluster. We see the below error when using the cluster configuration endpoint.
org.redisson.client.RedisException: MOVED redirection loop detected. Node rediss://<IP_ADDRESS>:6379 has further redirect to rediss://qaw01-appcontext-esse-s001-0001-002.qaw01-appcontext-esse-s001.gzreim.usw1.cache.amazonaws.com:6379
Can you please help to let us know if the cluster configuration endpoint is being supported or not. Please note that AWS documentation states that we should be using cluster configuration endpoint for connection.
https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/Endpoints.html

Can you please help to let us know if the cluster configuration endpoint is being supported or not

Yes, it's supported.
Can you share the logs with trace logging level for org.redisson package to understand the cause?

TraceLogsRedisson.txt
@mrniko  Attached trace logs for connection failure with cluster configuration endpoint

I don't see output from ClusterConnectionManager

@mrniko I am not sure what you mean exactly. Actually we use the below code to create a connection
Config config = new Config();
config.useClusterServers().addNodeAddress(redisNodes.toArray(new String[0]));
config.useClusterServers().setPassword(redisPassword);
Redisson.create(config);
Let me know if we need to explicitly use ClusterConnectionManager here

In this ClusterConnectionManager is used by Redisson, but I don't see any output in logs. Can you check if you set correctly trace logging level for all Redisson classes?

@mrniko I am attaching the logs again.
ClusterConfigTrace.log
Kindly let me know if this is sufficient.

Still don't see any output from ClusterConnectionManager

Fixed in https://github.com/redisson/redisson/issues/4656


Pressing enter when creating a repo doesn't do anything

Scenario
1- Try to create a repo and instead of pressing confirm.. press enter

2- The box will disappear and nothing will be done

Software Version
JumpScale
Core: v8.1.0-21-gd543c65
Portal: v8.1.0

JSCockpit
JSCockpit: 8.1.0rc2-2-g28c77ae

@john-kheir it closes the popup. I don't see how this is a bug.
Please explain or close?


Optimize and extend deployment unit tests.

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
Optimize and extend deployment unit tests.
Which issue(s) this PR fixes:

Prepare for #3555
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

/cc @mimowo

Resolved conflicts.

/lgtm

/cherry-pick release-0.9


Delete temporary parameter files in Azure Powershell

Azure Powershell compiles bicep files on disk before making any deployment (instead of storing it in memory like Azure CLI). These compiled files might contain user secrets that should be removed from disk after deployment.

Fixed with https://github.com/Azure/azure-powershell/pull/22728 - I switched over to using --stdout


运行起来后，不能create创建

（1）、git clone https://github.com/joeblau/gitignore.io.git
（2）、vapor build
（3）、vapor run  后，显示：
You might not have done a recursive clone to update your submodules:
git submodule update --init --recursive
No command supplied, defaulting to serve...
No preparations.
Server 'default' starting at <IP_ADDRESS>:8080
（4）、访问页面：
在文本框内输入python，no  create；
这是怎么回事呢？

There seems to be a bug if you follow these steps:

Enter Python
Press Create
Press back on the browser
Press Create again - (At this step nothing happens)

I'll figure out what's going on with this.

I follow the tutorial on github, the local environment, install the swift 4.0 framework, vapor 3.0 version;
OS： Ubuntu16.04
(1)、Git clone -- recursive<EMAIL_ADDRESS>joeblau/gitignore. IO.
（2）、Git showed no permission to connect, I try to download zip code file, and then,
（3）、 cd  gitignore. io/
（4）、execution
vapor builds
vapor run,
（5）、access to the web site, shows the ignore. io  page, just can't create ignore files;

Per the Package.swift file, the app works with vapor 1.5, not vapor 3.  I'm not sure if vapor 3.0 supports localization but I need that for some of my international users.
https://github.com/joeblau/gitignore.io/blob/master/Package.swift

How is vapor1.5 installed

swift package fetch

Hello, I have cloned gitignore from github to local, and I entered the gitignore.io folder and implemented the vapor build. Then I encountered these mistakes. What is the problem, please?
Vapor build
No. Build folder, fetch may take a while...
Fetching Dependencies [•]
Error: backgroundExecute(code: 1, Error: "warning: 'fetch' command is deprecated;Use 'resolve' instead\nerror: invalidAccess\n ', output: '

I've updated to vapor 3, can you try the clone build and run steps again please?

Please re-open this ticket if vapor 3 doesn't work.

thank you !  I have solved it


Fixes memory leaks and a crash on invalid BPG data

A crash occurs when trying to decode invalid data and deallocating
decoder in catch block.

Thank you for this GREAT PR!!

Could you please send me (or attach) the BPG image to reproduce the crash?

Hi,
Thank you for a great wrapper, it saved a lot of time for me :)
I'll make the changes you asked and I'll try to find an image data on which crashed occurs.
I've added the null check just for consistency (for example [NSKeyedUnarchiver unarchiveObjectWithData:nil] is also nonnull, but it still does not crash and return a nil value).

OK, I could reproduce the crash (it only occurs on release build), and still crashes after applying this patch. I'll fix it soon, so please fix only the memory leaks🙏

OK, I found how to reproduce; it only occurs on the release build😟
so, a sample image is not needed :+1:

I'll fix this on this branch.


Javascript runtime exited unexpectedly

Using the library as it is I ran into the titled error using the V8 runtime. I identified the source of the problem in the two payload definitions in the request header in the lines
https://github.com/tanaikech/DownloadLargeFilesByUrl/blob/8d55db02887755929700ed6cf92a9f35d4413ddf/DownloadLargeFilesByUrl.js#L376
and
https://github.com/tanaikech/DownloadLargeFilesByUrl/blob/8d55db02887755929700ed6cf92a9f35d4413ddf/DownloadLargeFilesByUrl.js#L435
Using the methods getBlob().getBytes() seems to cause this problem. Removing the two methods fixes the problem for me. Assigning an instance of the DriveApp File to the payload resolves its content and the request is submitted correctly.

Hello,
I'm experiencing the same exception as soon as joining process starts.
I don't think I have the opportunity to change library source code as stated in issue description, so I found another workaround for the problem - changing chunkSize to 26MB (27 262 976B). More than that causes JavaScript runtime error.


more filtering ideas

just going through interviews and a lot of ideas have come up regarding things people might want, so I wanted to compile them all somewhere for future consideration as features.
password reset links, financial info, order confirmations from amazon, etc. should not go through moderation - ppl want them immediately and don't want mods to see them. some of these are easy to detect if they always come from same domain/address, but others (like pw emails) are not.
option to have anyone you've replied to in the past automatically whitelisted
emails containing links to websites that look suspicious (we could probably find some api/library to check for this) should be flagged as such

closing because I've broken this down into more specific issues.


chore(roadmap): complete primary API

Checking off boxes

Current coverage is 100% (diff: 100%)

Merging #31 into master will not change coverage

@@           master   #31   diff @@
===================================
  Files           7     7
  Lines          93    93
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
  Hits           93    93
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update ace52c5...57b3807

:tada: @jdetle

:shipit:!

Looks like we're shipping 2.0.0. Time to release, build some prototypes against this, and inevitably make patch releases. :smile:


Add support for feature restore files from backup

Signed-off-by: pratiksha chavan<EMAIL_ADDRESS>Description
Add support for feature restore files from backup
Issues Resolved
None
Check List

[x] New functionality includes testing.

[x] All tests pass($ tox).

[x] New functionality has been documented in the README if applicable.

[x] New functionality has been thoroughly documented in the examples (please include helpful comments).
[x] New endpoints supported are updated in the endpoints-support.md file.

[x] Changes are documented in the CHANGELOG.

Updated the content-type to minimum version from were the API is supported

@svt-pchavan , please resolve the conflicts.


Generate plugin docs and publish to github.io pages

Is there some low-effort, repeatable way to do this, perhaps via a Maven plugin?

@gual Yeah, the maven-site-plugin generates static websites for maven projects. It can be tweaked with various reporting plugins. The maven-plugin-plugin is a particularly useful reporting plugin for generating sites for maven plugins. Once configured, you can generate the site with the built-in site lifecycle mvn site.
You can manually copy the generated static site's html from target/ to a gh-pages branch in the project. If the repository is properly configured in GitHub, that would cause the generated docs to be hosted at https://gaul.github.io/modernizer-maven-plugin/ (see https://pages.github.com/ for info on static site hosting on GitHub).
Instead of manually copying, publishing can be automated further by binding plugins to deploy phase of the site lifecycle so they automatically publish when you do mvn site-deploy. Several projects I host at https://github.com/revelc do this, if you want to see some example pom.xml files:

formatter-maven-plugin currently uses wagon-git and wagon-ssh to publish
(my preferred method): apilyzer-maven-plugin, zookeeper-maven-plugin and others skip the built-in deploy action of maven-site-plugin and instead use GitHub's own site-maven-plugin, which uses GitHub's API to directly upload the site to the gh-pages branch in the repository.

I use the maven-site-plugin to generate the site and maven-scm-publish-plugin to publish to a gh-pages branch; I've found this to be the most reliable way, also for very large, multimodule sites.
As an example see https://github.com/GeoDienstenCentrum/schemaspy-maven-plugin/blob/master/pom.xml
I can get you started with a PR if you like

@mprins I would appreciate a PR!  @ctubbsii gave some good background but I don't have the cycles to look into this myself.

So I've created the PR about 2 months ago, but so far no reaction


Dynamic executor import errors

This is mainly a revamp of the executor/launcher loading code. The main stuff (with description) is in ad9e42451f23e6d6a09070683a90011a9a679208, and I'll reproduce the text below.
There are some tests in fd56015ca0ec8c64188a8b67404468e6b9e660bd
Plugins are now loaded indirectly, using a descriptor class. This was
needed because one could not find details about, say, an executor (such
as name and version) if the executor file failed to import. However, a
minimal descriptor is virtually guaranteed to load, providing information
about the implementation that does not depend on that implementation being
able to load/import.
Also updated the way loading works. Previously, problems could occur when
implementations existed in multiple locations, because package traversal
in python is weird: despite correctly iterating over packages from
multiple locations, python only really references the first location
loaded and only allows imports from that location. The current
implementation works according to the following rules:

descriptors must be in the 'psij.executors' package, and the package can
be spread across multiple locations
implementations must exist in the same location as the descriptor; for
example, a descriptor in the system dist-packages can only be used to load
an implementation from the system dist-packages, not from a user directory.
if implementations exist in both the same location and another location
as a descriptor, only the one in the same location will be used
here, "location" means one directory in PYTHONPATH and/or sys.path.

And last, you can now run "python -m psij plugins" to get a detailed list
of what is loaded and from where.

A bit of a note on tests: 3 of the new tests require some directories to be added to PYTHONPATH before invoking pytest. This is done by ci_runner.py, which is always checked out from the main branch. So those tests will fail on this branch/PR until it's merged.

A bit of a note on tests: 3 of the new tests require some directories to be added to PYTHONPATH before invoking pytest. This is done by ci_runner.py, which is always checked out from the main branch. So those tests will fail on this branch/PR until it's merged.

this breaks the pytest command line in README-testing.md - maybe remove that entirely as make test is probably enough documentation

I've encountered this behaviour which is somewhere between awkardness and failure [...] path order [...]

I noticed this as I was adding the paths to ci_runner.

Where this is more a problem than an awkwardness is when I have installed psij into a conda environment, but want to add in more stuff using PYTHONPATH - for example, I installed psij in conda and tried out my pbspro executor as a separate module.

We cannot enforce/guarantee a particular order when this is used, so this is a problem.

[...]
This doesn't feel right to me.

I agree.

The closest I know of in the Python documentation is namespace packages, here: https://packaging.python.org/en/latest/guides/packaging-namespace-packages/#native-namespace-packages
which talks about doing things like omitting the top level init.py so as to make that package a "namespace package".
I don't have any practical experience with doing that, though.

Since I discovered the issue, I've been experimenting with that. It doesn't work, at least not the way things are structured now. The problem with namespace packages is that we do need psij to be a normal package with things done when it is loaded and that prevents us from using it as a namespace package.
What I will experiment with next is having a separate namespace package for descriptors and "mandating" separate packages for the executors themselves (e.g. psij-executor-xyz.xyz_executor.py.

I'm also unclear about what the package modularisation goals for the code that this PR deals with - eg what should end users be able to do (or not do) wrt separate installs of pieces?

This does try to address the separate install of pieces. However, the core loader has to be able to find the pieces, so they have to be in a more-or-less pre-determined "location".

What I will experiment with next is having a separate namespace package for descriptors and "mandating" separate packages for the executors themselves (e.g. psij-executor-xyz.xyz_executor.py.

b419aeedc4ebcb136df6570f1c24bba3492f6e80 adds the separate namespace package (psij-descriptors). It also contains a more detailed explanation of what and why. It appears to work in all situations I've tested.
There's also an earmark (d9028490337aa3180ef0e650957cdfe57fdf081a) which adds a branch-specific wrapper between ci_runner and pytest, so that some customization can be done on specific branches (since ci_runner is always used from the main branch).

ok, with separate psij-descriptors, my psij-in-conda, pbspro-in-PYTHONPATH test works, at least as far as getting jobs in the queue (looks like that system isn't actually running jobs at the moment...)
The directory tree so far looks like (though probably doesn't need the subdirectory structure so much now it's in its own top-level package)
./psijpbs/__init__.py
./psijpbs/executors/__init__.py
./psijpbs/executors/pbspro.py
./psijpbs/executors/batch/pbspro/pbspro.mustache
./psij-descriptors/pbspro_descriptor.py

@benclifford good to hear.
I think it's fine to leave the exact location of the executor implementation up to whoever is writing it.

@benclifford if you are OK with the various fixes and, seeing that there's likely no other reviewers, can you click the merge button?

I'll take a look today and merge if things check out, if you don't mind.

I'll take a look today and merge if things check out, if you don't mind.

Not at all. Thank you!


To fast logout

Hi, I have a project in .net 3.1 with Finbucke.MultiTenant 6.2.0.
When a user logs in he is automatically logged out in +- 1h but I want to keep the session for 12h or even longer. How can I achieve that?
My code for MultITenant configuration
 services.AddMultiTenant<TenantInfo>().WithHostStrategy()
.WithStore<MultitenantAzureStorageStore>(ServiceLifetime.Scoped) //my own implemented store
.WithPerTenantOptions<CookieAuthenticationOptions>((o, tenantInfo) =>
{
    o.Cookie.Name = "FC.SigninCookie." + tenantInfo.Name;
    o.ExpireTimeSpan = TimeSpan.FromHours(12);
    o.SlidingExpiration = true;
})
.WithPerTenantAuthentication();

What am I doing wrong?
Thanks for your help,
Cris

hi @szymczakk sorry for the slow reply
I'm not sure what would be causing it. If you check the browser dev mode what lifetime does it show for the auth cookie when it is first created?
I'm happy to take a closer look -- is there a repo I can access to see an example application where this is occurring?

Hi, not a problem,
I will prepare one later.
As a quick fix I deleted WithPerTenantAuthentication and it's working right now.

@szymczakk a few questions

are you using identity?
in your call to SignInAsync are you setting the IsPersistant property to true?

I suspect that WithPerTenantAuthentication conflicted with the prior call to WithPerTenantOptions -- something I need to investigate

Hi,
yes Im using Identity and Im setting it to true.
I will prepare test repo for you where you will be able to investigate it ;)
wt., 13 kwi 2021, 07:21 użytkownik Andrew White @.***>
napisał:

@szymczakk https://github.com/szymczakk a few questions

are you using identity?
in your call to SignInAsync are you setting the IsPersistant
property to true?

I suspect that WithPerTenantAuthentication conflicted with the prior call
to WithPerTenantOptions -- something I need to investigate
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Finbuckle/Finbuckle.MultiTenant/issues/415#issuecomment-818445286,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACBP3RVFC25COI5T6UXGPDLTIPIGFANCNFSM4Z6P2A5A
.

hi @szymczakk
Just following up here-- did you create a test repo? Sorry if I missed it

I had a similar problem and after some research found the issue.
When using the .WithPerTenantAuthentication() extension method, it breaks the Cookie Validation, triggered by the cookie validation timeout.
I set it like this:
services.Configure<SecurityStampValidatorOptions>(options =>
            {
                // This also refreshes the User Claims
                options.ValidationInterval = TimeSpan.FromSeconds(10);
            });

What this does is reloading the Claims for the user after the interval passed.
When you use the method .WithPerTenantAuthentication(), then it expects the User to have the Claim "tenant" with the value of your tenant id. If it does not have it, then the Principal will be rejected.
It works after the first SignIn, because at https://github.com/Finbuckle/Finbuckle.MultiTenant/blob/4c422b3965ff326f3232cfeb7091d44dbe1db006/src/Finbuckle.MultiTenant.AspNetCore/Extensions/MultiTenantBuilderExtensions.cs#L107 it get's set after signing in.
The problem is, that this event does not get triggered after the UserClaims have been loaded again.
To fix it you can add a custom UserClaimsPrincipalFactory. I had that anyway, because I needed to add custom Claims to the user.
public class UserClaimsFactory : Microsoft.AspNetCore.Identity.UserClaimsPrincipalFactory<Data.Set.User>
    {
        private readonly Common.Tenant _tenant;
        public UserClaimsFactory(UserManager<Data.Set.User> userManager, IOptions<IdentityOptions> optionsAccessor, Common.Tenant tenant) : base(userManager, optionsAccessor)
        {
            _tenant = tenant;
        }

        protected async override Task<ClaimsIdentity> GenerateClaimsAsync(User user)
        {
            var principal = await base.GenerateClaimsAsync(user);

            const string strTenantType = "__tenant__";
            if (_tenant != null)
                principal.AddClaim(new Claim(strTenantType, _tenant.Id));

            return principal;
        }
    }

and register it in the Startup.cs
services.AddScoped<IUserClaimsPrincipalFactory<MyUser>, UserClaimsFactory>();

After doing that the user always had the tenant claim and did not get rejected at https://github.com/Finbuckle/Finbuckle.MultiTenant/blob/4c422b3965ff326f3232cfeb7091d44dbe1db006/src/Finbuckle.MultiTenant.AspNetCore/Extensions/MultiTenantBuilderExtensions.cs#L90

@Nivalux thanks for the detailed response. I probably need a more robust method of setting the tenant claim -- probably via an IUserClaimsFactory that wraps around any preexisting user claims factory. Thanks!

Looking into this and working on a solution. I actually have a tenant claim in my Identity user model so I think it was preventing me from seeing the issue. Hope to have a release with this fix out soon.


Add ns randomizer for vault

To allow deploying both vault and vault-k8s in the same time using the Helm chart without still in use error.

PTAL when possible. @stormqueen1990 @mattmoor

PTAL when possible. @stormqueen1990 @mattmoor

done!


Add throttle support

@NROL39 why? I mean what this PR actually fixes/enhances

It adds throttling support, let's say you have a hundred users, your server has 100mbps bandwidth, at the moment what will happen is that you'll be sending data as fast as possible, choking the other connections (try downloading multiple large files at the same time, you'll notice some will be downloading at a fast rate while some will have much lower rate).
Basically, it's so you can divide resources between multiple clients without having clients interfere with each other's downloads

@NROL39 got it, but why not make build in (all pipes by default) with ability to change (bps). Now if user does not passes throttle to Files instance, this feature won't be used

That's right, I feel this should be an opt-in feature rather than an opt-out (although this is entirely up to you)

Better to have it enabled by default. But we need to specify default bps? Which value will be optimal?

Well, it depends on the server's bandwidth, average file size and concurrent user count, every project will have it's own optimal range which is why i think it should be opt-in.

Agree now.
And why this feature is not applied to 206 responce

There we go, 206 support added.

@NROL39 Thank you. I'll run tests, then merge and publish

Could you also add check @throttle, Match.oneOf Boolean, Number into constructor and update docs and in-code doc-block?


Fix full plant name not shown.

Basics

[x] I added a line to changelog.md
[x] The PR is rebased with current master.

[x] References to issues, e.g. close #X, are in the commit messages and changelog.
[ ] The buildserver is happy.

Checklist

[ ] I have installed and I am using pre-commit hooks
[ ] I fully described what my PR does in the documentation
[ ] I fixed all affected documentation
[ ] I fixed the introduction tour
[ ] I wrote migrations in a way that they are compatible with already present data
[ ] I fixed all affected decisions
[ ] I added automated tests or a manual test protocol
[ ] I added code comments, logging, and assertions as appropriate
[ ] I translated all strings visible to the user
[ ] I mentioned every code or binary not directly written or done by me in reuse syntax
[ ] I created left-over issues for things that are still to be done
[ ] Code is conforming to our Architecture
[ ] Code is conforming to our Guidelines
[ ] Code is consistent to our Design Decisions
[ ] Exceptions to any guidelines are documented

Review

[ ] I've tested the code
[ ] I've read through the whole code
[ ] I've read through the whole documentation
[ ] I've checked conformity to guidelines

@badnames when I rename the seeds, still the old (additional) names are shown. Is this a different issue? After complete reload the new names are fetched.

Might be because the query cache never gets updated. I'm looking into it.

jenkins build please

It is not stale anymore but there is still another problem:

user A puts a plant from a seed on the map X
user B looks at X

expected behavior: user B also sees the additional name (like user A).
actual behavior: user B doesn't see the additional name (unlike user A).

The problem at the moment is that seeds can only be accessed by the user who created them.

If you want I can fix this by sending the additional name alongside the seed id.
The other option would be to restructure our seeds/inventory endpoint such that users can access seeds other than their own.
Doing this in a secure manner would not be trivial.

If you want I can fix this by sending the additional name alongside the seed id.

Sounds good, doesn't that make sense anyway to get everything in a single endpoint request?

@markus2330 I think we should hold of on adding end to end tests for this feature until #869 is merged.
Otherwise I would have to reimplement a significant amount of its functionality.
That might lead to nasty merge conflicts down the road.

It is enough if you only manually write what should be tested.
Did you test already if a concurrent user correctly sees plants?

@badnames there are clippy problems. Looking forward to get this merged :heart:

Did you test already if a concurrent user correctly sees plants?

Yes and it should work now.

jenkins build please

Unfortunately, clippy is still not happy. I try to fix it in #1070 but I didn't understand what you wanted to do, so I maybe fixed it wrongly. Please always comment what the code should do, not about what you attempted to do but then decided otherwise.

Unfortunately, clippy is still not happy. I try to fix it in #1070 but I didn't understand what you wanted to do, so I maybe fixed it wrongly. Please always comment what the code should do, not about what you attempted to do but then decided otherwise.

All clippy errors have now been fixed.

Thx, unfortunately still buggy in concurrent use: if I have an additional listener on the plants*, the browser that does the action does not see the additional name (the browser that listened to the action, gets the correct name).

in a later test this was not even needed?

And then later it was not possible anymore to put seed plants anymore at all?
What is being planted also does not show the additional name?

Thx, unfortunately still buggy in concurrent use: if I have an additional listener on the plants*, the browser that does the action does not see the additional name (the browser that listened to the action, gets the correct name).
* in a later test this was not even needed?

And then later it was not possible anymore to put seed plants anymore at all?
What is being planted also does not show the additional name?

Thanks for reporting this bug.
I made sure that the additional name is added to the frontend store of the local browser.
Can you verify that this is no longer an issue?

Much better, still two minor bugs:

[ ] when changing the additional name (in inventory), and planting this plant, a concurrent viewer doesn't see the first plant planted (later planted plants are seen)
[ ] the planting mode window still doesn't show the additional name

the planting mode window still doesn't show the additional name

Does this only occur in conjunction with the first issue or does this always happen?
Because at the moment I can not replicate this locally:

I mean the little window in the bottom middle (not toolbar left bottom).

Sorry, I thought you ment the plant layers left toolbar.

So everything that was requested should hopefully now be implemented.
Big Disclaimer:
I am perfectly honest, I am not proud of this code as it is ugly, inefficient and insecure (altough, our entire action broadcasting system was not built with security in mind) but it should get the job done.
Initially (yes, I know I say this often) I did not expect that this fix would need that many changes so I did not see this coming.
Doing it properly would require some significant reworks of the action broadcasting system.
I will add the missing manual tests to our test protocol tomorrow and hopefully fix the broken e2e test, then we should be able to merge.

jenkins build please

@horenso @danielsteinkogler @absurd-turtle can you do a review here please?


Doesn't install via cabal

Hi, I'm extremely new to Haskell, (first cabal package I tried to install) so I might just be doing something wrong, but while miku installs, hack2-hander-snap-server does not.
https://gist.github.com/1324724
Hoping to try it out! thanks!

Thanks, fixed.
cabal update && cabal install hack2-hander-snap-server

That was fast. Thanks!


XEP-0163: Personal Eventing Protocol; Planned support/accepting PR?

Hi there,
I've been thinking about building an XMPP server in go for a while, and I just found yours. I haven't looked at the code yet (will do soon) but it looks good and active, so I was wondering if you have reached a point on the project where pull requests are welcome (API is more or less consolidated, etc).
Currently I'm really interested in PEP, as it is a hard requirement for OMEMO which is a feature I'd need for my XMPP service. What do you think? Can I give it a try? If you think it's worth it, I could use a few lines explaining the project structure, like if it is module-based, if there are hooks, and where should I place the PEP-related code.
Regards and thanks for your time!

Hi roobre
Of course! In fact PEP was originally included in my internal roadmap, cause OMEMO support is also one of the preferences for jackal (and would also like to enforce it, if possible). Feel free to PR it! Regarding code and architecture design, if you have any doubt, ask and I’ll try to shed some light on it.
Welcome onboard!


use this sdk in native platform

I want to integrated / embed this sdk into my existing native android/iOS app (not react native)
any example how to do that?

We don't have a native sdk for now. You can try using a hybrid model to embed ReactNative with native app.

I temporarily mark this as wontfix, please leave comments below if you have demands for native sdk (or  other languages) so we can adjust our priority.

Would love to see native android and ios support. Even better if you can support flutter as well

Same...
React Native is not possible, welcome Native SDK.
Do you have documentation with the APDU commands?


Can't build on Raspberry Pi 3

I get meson error while trying to build ashuffle 3.5.0 on RPI3 following step-by-step instructions.
Here is the meson log:
`Build started at 2020-06-08T18:40:01.583197
Main binary: /usr/bin/python3
Python system: Linux
The Meson build system
Version: 0.49.2
Source dir: /home/pi/ashuffle
Build dir: /home/pi/ashuffle/build
Build type: native build
Project name: ashuffle
Project version: undefined
Sanity testing C compiler: cc
Is cross compiler: False.
Sanity check compiler command line: cc /home/pi/ashuffle/build/meson-private/sanitycheckc.c -o /home/pi/ashuffle/build/meson-private/sanitycheckc.exe
Sanity check compile stdout:

Sanity check compile stderr:

Running test binary command: /home/pi/ashuffle/build/meson-private/sanitycheckc.exe
Native C compiler: cc (gcc 8.3.0 "cc (Raspbian 8.3.0-6+rpi1) 8.3.0")
Sanity testing C++ compiler: c++
Is cross compiler: False.
Sanity check compiler command line: c++ /home/pi/ashuffle/build/meson-private/sanitycheckcpp.cc -o /home/pi/ashuffle/build/meson-private/sanitycheckcpp.exe
Sanity check compile stdout:

Sanity check compile stderr:

Running test binary command: /home/pi/ashuffle/build/meson-private/sanitycheckcpp.exe
Native C++ compiler: c++ (gcc 8.3.0 "c++ (Raspbian 8.3.0-6+rpi1) 8.3.0")
Build machine cpu family: arm
Build machine cpu: armv7l
meson.build:25:2: ERROR:  Module "cmake" does not exist`

on Arch Linux, the instructions work for me on RPI B3 and B1 (armv6/7).

@ge-ps Thanks for including all this info in your report! As per https://github.com/joshkunz/ashuffle#dependencies, a Meson version of at least 0.54.0 is required to build ashuffle. Consider upgrading Meson from your package manager, or installing a newer version with pip.
Ideally, you could just use the binary distributions included with the release, instead of having to compile from source. Unfortunately, I overlooked that Raspberry Pi OS is 32-bit only, even though RPi 3+ are actually running 64-bit capable chips 😅. I've opened #66 to fix this oversight.


Multiple Type errors

There are multiple Type errors while compiling and flashing. Any idea how to fix?

@Jimmy106-e I'm currently building a whole new repository, build on the newest IDF and other needed software. You cna find it here: https://github.com/AchimPieters/esp32-homekit-demo. It is still in construction, but will soon be completed and then the ESP Camera is on my list.


Mine

Just trying to update with fixes... dont really know how this all works(prs)

just copy/pasted branch which means that there will be some updates that need to be done


Add frontend changes- Login page

Add login page.
Objective: Accept user details and redirect to index page.

Is handling sign-up also in the scope of this ticket?

Sign-up is needed too

Handled sign up functionality.


add nftType field to EntryRemoved event

Adds a field to the EntryRemoved event so that indexers can easily pick up what contract was impacted by the removal. Without this, indexers have to keep a mapping of collectionIdentifier -> type on their own so that when a removal event comes through, they know what type it belongs to

Tests failed here in github actions, but worked when i pulled it locally. Going ahead and merging it with that in mind.


4653: Permit :date_range filter param in DistributionsController#index

Resolves #4653
Description
This "unpermitted parameter" warning was logged because we were permitting other filter params but not the date_range param. This parameter is needed for date filtering, so I added it to the permitted params list.
Type of change
Minor change in logging.
How Has This Been Tested?
Added a spec to test permitted filter params.
And manually noticed that the "unpermitted_parameter" warning was no longer being logged.

Looks good from a functional pov -- Over to @dorner for technical comments

Looks good, thanks!


username unchecked?

hello,my medoo config 'username'  use empty or a 'hello' or any words,its still connected and can do select.
only password changed it went wrong. why is that? am i wrong?

I'm not sure. But it seems your database can be connected with any user without password.
You may check out your database configuration.


Battery calibration doesn't seem to work

What is the issue? (required)
The battery calibration CLI command doesn't fully charge the battery to 100%. Instead it stops at 83% and then disables the charging mechanism again.
What exactly did you do to produce the issue? (required)
Steps to reproduce the behavior:

Restarted the MacBook
Started the Battery App
Opened the Terminal
Entered battery calibrate
Waited.

Expected behavior (required)
The battery is getting discharged to 15%, then charges up to 100%. Waits for an hour and then it discharges down until 80% again.
Screenshots (optional)
None.
Error logs

Open for logs
```
07/04/24-12:28:03 - 🚨 Calibration process have been stopped
07/04/24-12:28:03 - Error: recover is not a valid setting for battery maintain. Please use a number between 0 and 100
07/04/24-12:28:37 - 🚨 Calibration process have been stopped
07/04/24-12:28:37 - 🚨 Calibration process have been stopped
07/04/24-12:28:37 - Not triggering discharge as it is not requested
07/04/24-12:28:37 - Not triggering discharge as it is not requested
07/04/24-12:28:37 - Charging to and maintaining at 80% from 22%
07/04/24-12:28:37 - Charging to and maintaining at 80% from 22%
07/04/24-12:29:06 - Starting calibration
07/04/24-12:29:06 - 🚨 Calibration process have been stopped
07/04/24-12:29:06 - Killing running maintain daemons & enabling charging as default state
07/04/24-12:29:06 - Disabling daemon at gui/501/com.battery.app
07/04/24-12:29:06 - Battery at 22% ((no remaining), 11.25V, smc charging enabled
07/04/24-12:29:06 - Discharging to 15% from 22%
07/04/24-12:29:06 - 🔽🪫 Enabling battery discharging
07/04/24-12:29:06 - Battery at 22% (target 15%)
07/04/24-12:30:06 - Battery at 22% (target 15%)
07/04/24-12:31:06 - Battery at 22% (target 15%)
07/04/24-12:32:06 - Battery at 22% (target 15%)
07/04/24-12:33:06 - Battery at 22% (target 15%)
07/04/24-12:34:06 - Battery at 22% (target 15%)
07/04/24-12:35:06 - Battery at 21% (target 15%)
07/04/24-12:36:06 - Battery at 21% (target 15%)
07/04/24-12:37:06 - Battery at 21% (target 15%)
07/04/24-12:38:06 - Battery at 21% (target 15%)
07/04/24-12:39:06 - Battery at 21% (target 15%)
07/04/24-12:40:06 - Battery at 21% (target 15%)
07/04/24-12:41:06 - Battery at 21% (target 15%)
07/04/24-12:42:06 - Battery at 21% (target 15%)
07/04/24-12:43:06 - Battery at 21% (target 15%)
07/04/24-12:44:06 - Battery at 21% (target 15%)
07/04/24-12:45:06 - Battery at 21% (target 15%)
07/04/24-12:46:06 - Battery at 20% (target 15%)
07/04/24-12:47:53 - Battery at 20% (target 15%)
07/04/24-12:48:53 - Battery at 20% (target 15%)
07/04/24-12:49:54 - Battery at 20% (target 15%)
07/04/24-12:50:54 - Battery at 20% (target 15%)
07/04/24-12:51:54 - Battery at 20% (target 15%)
07/04/24-12:52:54 - Battery at 20% (target 15%)
07/04/24-12:53:54 - Battery at 20% (target 15%)
07/04/24-12:54:54 - Battery at 20% (target 15%)
07/04/24-12:55:54 - Battery at 20% (target 15%)
07/04/24-12:56:54 - Battery at 19% (target 15%)
07/04/24-12:57:54 - Battery at 19% (target 15%)
07/04/24-12:58:54 - Battery at 19% (target 15%)
07/04/24-12:59:54 - Battery at 19% (target 15%)
07/04/24-13:00:54 - Battery at 19% (target 15%)
07/04/24-13:01:54 - Battery at 19% (target 15%)
07/04/24-13:02:54 - Battery at 19% (target 15%)
07/04/24-13:03:54 - Battery at 19% (target 15%)
07/04/24-13:04:54 - Battery at 19% (target 15%)
07/04/24-13:05:54 - Battery at 18% (target 15%)
07/04/24-13:06:54 - Battery at 18% (target 15%)
07/04/24-13:07:54 - Battery at 18% (target 15%)
07/04/24-13:08:54 - Battery at 18% (target 15%)
07/04/24-13:09:54 - Battery at 18% (target 15%)
07/04/24-13:10:55 - Battery at 18% (target 15%)
07/04/24-13:11:55 - Battery at 18% (target 15%)
07/04/24-13:12:55 - Battery at 17% (target 15%)
07/04/24-13:13:55 - Battery at 17% (target 15%)
07/04/24-13:14:55 - Battery at 17% (target 15%)
07/04/24-13:15:55 - Battery at 17% (target 15%)
07/04/24-13:16:55 - Battery at 17% (target 15%)
07/04/24-13:17:55 - Battery at 17% (target 15%)
07/04/24-13:18:55 - Battery at 17% (target 15%)
07/04/24-13:19:55 - Battery at 17% (target 15%)
07/04/24-13:20:55 - Battery at 16% (target 15%)
07/04/24-13:21:55 - Battery at 16% (target 15%)
07/04/24-13:22:55 - Battery at 16% (target 15%)
07/04/24-13:23:55 - Battery at 16% (target 15%)
07/04/24-13:24:55 - Battery at 16% (target 15%)
07/04/24-13:25:55 - 🔼🪫 Disabling battery discharging
07/04/24-13:25:55 - Disabling discharging: Charge above 15, disabling charging
07/04/24-13:25:55 - 🔌🪫 Disabling battery charging
07/04/24-13:25:55 - MagSafe LED function invoked
07/04/24-13:25:55 - 💡 Setting magsafe color to green
07/04/24-13:25:55 - setting LED to green
07/04/24-13:25:55 - Discharging completed at 15%
07/04/24-13:25:55 - checking if at 100%
07/04/24-13:26:26 - Charge below 80
07/04/24-13:26:26 - 🔌🔋 Enabling battery charging
07/04/24-13:26:26 - 🔼🪫 Disabling battery discharging
07/04/24-13:26:26 - MagSafe LED function invoked
07/04/24-13:26:26 - 💡 Setting magsafe color to orange
07/04/24-13:26:26 - setting LED to orange
07/04/24-13:30:55 - checking if at 100%
07/04/24-13:35:55 - checking if at 100%
07/04/24-13:40:56 - checking if at 100%
07/04/24-13:45:56 - checking if at 100%
07/04/24-13:50:56 - checking if at 100%
07/04/24-13:55:56 - checking if at 100%
07/04/24-14:00:56 - checking if at 100%
07/04/24-14:05:56 - checking if at 100%
07/04/24-14:10:56 - checking if at 100%
07/04/24-14:15:56 - checking if at 100%
07/04/24-14:20:56 - checking if at 100%
07/04/24-14:53:26 - checking if at 100%
07/04/24-15:29:56 - Charge above 80
07/04/24-15:29:56 - 🔌🪫 Disabling battery charging
07/04/24-15:29:56 - MagSafe LED function invoked
07/04/24-15:29:56 - 💡 Setting magsafe color to green
07/04/24-15:29:56 - setting LED to green
07/04/24-15:36:34 - Charge above 80
07/04/24-15:36:34 - MagSafe LED function invoked
07/04/24-15:36:34 - 💡 Setting magsafe color to green
07/04/24-15:36:34 - setting LED to green
07/04/24-15:37:01 - checking if at 100%
07/04/24-15:37:34 - Charge above 80
07/04/24-15:37:34 - MagSafe LED function invoked
07/04/24-15:37:34 - 💡 Setting magsafe color to green
07/04/24-15:37:34 - setting LED to green
07/04/24-15:54:49 - Charge above 80
07/04/24-15:54:49 - MagSafe LED function invoked
07/04/24-15:54:49 - 💡 Setting magsafe color to green
07/04/24-15:54:49 - setting LED to green
07/04/24-15:55:49 - Charge above 80
07/04/24-15:55:49 - MagSafe LED function invoked
07/04/24-15:55:49 - 💡 Setting magsafe color to green
07/04/24-15:55:49 - setting LED to green
07/04/24-15:56:50 - Charge above 80
07/04/24-15:56:50 - MagSafe LED function invoked
07/04/24-15:56:50 - 💡 Setting magsafe color to green
07/04/24-15:56:50 - setting LED to green
07/04/24-15:57:50 - Charge above 80
07/04/24-15:57:50 - MagSafe LED function invoked
07/04/24-15:57:50 - 💡 Setting magsafe color to green
07/04/24-15:57:50 - setting LED to green
07/04/24-15:58:16 - checking if at 100%
07/04/24-15:58:50 - Charge above 80
07/04/24-15:58:50 - MagSafe LED function invoked
07/04/24-15:58:50 - 💡 Setting magsafe color to green
07/04/24-15:58:50 - setting LED to green
07/04/24-15:59:50 - Charge above 80
07/04/24-15:59:50 - MagSafe LED function invoked
07/04/24-15:59:50 - 💡 Setting magsafe color to green
07/04/24-15:59:50 - setting LED to green
07/04/24-16:00:50 - Charge above 80
07/04/24-16:00:50 - MagSafe LED function invoked
07/04/24-16:00:50 - 💡 Setting magsafe color to green
07/04/24-16:00:50 - setting LED to green
07/04/24-16:01:50 - Charge above 80
07/04/24-16:01:50 - MagSafe LED function invoked
07/04/24-16:01:50 - 💡 Setting magsafe color to green
07/04/24-16:01:50 - setting LED to green
07/04/24-16:02:50 - Charge above 80
07/04/24-16:02:50 - MagSafe LED function invoked
07/04/24-16:02:50 - 💡 Setting magsafe color to green
07/04/24-16:02:50 - setting LED to green
07/04/24-16:03:16 - checking if at 100%
07/04/24-16:03:50 - Charge above 80
07/04/24-16:03:50 - MagSafe LED function invoked
07/04/24-16:03:50 - 💡 Setting magsafe color to green
07/04/24-16:03:50 - setting LED to green
07/04/24-16:04:50 - Charge above 80
07/04/24-16:04:50 - MagSafe LED function invoked
07/04/24-16:04:50 - 💡 Setting magsafe color to green
07/04/24-16:04:50 - setting LED to green
07/04/24-16:05:50 - Charge above 80
07/04/24-16:05:50 - MagSafe LED function invoked
07/04/24-16:05:50 - 💡 Setting magsafe color to green
07/04/24-16:05:50 - setting LED to green
07/04/24-16:06:50 - Charge above 80
07/04/24-16:06:50 - MagSafe LED function invoked
07/04/24-16:06:50 - 💡 Setting magsafe color to green
07/04/24-16:06:50 - setting LED to green
07/04/24-16:08:13 - 🚨 Calibration process have been stopped
07/04/24-16:08:13 - 🚨 Calibration process have been stopped
07/04/24-16:08:13 - Not triggering discharge as it is not requested
07/04/24-16:08:13 - Not triggering discharge as it is not requested
07/04/24-16:08:13 - Charging to and maintaining at 80% from 83%
07/04/24-16:08:13 - Charging to and maintaining at 80% from 83%
07/04/24-16:08:16 - checking if at 100%
```

Additional context (optional)
None.

For calibration you do not need to discharge, just charge to 100% within an hour.

Well I meant the calibration feature introduced with the new version.
This is supposed to discharge your battery down to 15%, then charging up to 100% and let it stay for an hour.
This is also inside the description of it.


Allow stdout for passing tests

Hey there!
I have a rare scenario where I would like to capture the logging output for a handful of successful tests, which ultimately end up being converted to JUnit Xml format. I tried --success-output final, but it has no effect for passing tests, presumably due to https://github.com/nextest-rs/nextest/blob/3a7a63739c99fb7757a2b382ea5c6b72d9599ef9/nextest-runner/src/reporter/aggregator.rs#L165
Could you possibly confirm whether this is indeed still on the TODO list and I am not missing something please? 🙂

Thanks for the feature request! This would be a great feature to add for sure. We could expose it as an option under the JUnit configuration.

Going to release support for new config options:
[profile.default.junit]
store-success-output = true  # false by default

and also as a per-test override:
[[profile.default.overrides]]
filter = 'test(my-tests)'
junit.store-success-output = true

so you can choose to do this for a subset of tests.

Planning to release this sometime this weekend.

whoops, this was released in cargo-nextest 0.9.49.


Add python alias on ec2 instance for gpu tests

Will merge it right away.
See e.g. https://github.com/huggingface/optimum/actions/runs/3434693610/jobs/5726266315

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


#27 jsinclude

Quite a big refactor of the javascript code: #27 .
Moved everything to the requirejs module system, hopefully improving (future) development ease and stability.
Really needs proper checking before we merge this one. It seems to be reaaally slow, but development_core suffers from the same thing it seems: zeeguu is just oddly late to respond to post request these days.

Had an interesting conversation with Johan, will close this request until I have been able to listen to him more on Monday

What's the outcome of the discussion?
On Mon, May 1, 2017 at 3:06 PM, Luc van den Brand<EMAIL_ADDRESS>wrote:

Reopened #53
https://github.com/mircealungu/Unified-Multilanguage-Reader/pull/53.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mircealungu/Unified-Multilanguage-Reader/pull/53#event-1063946183,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAcWh6E3wX526Neb9galifGq5RnpXinJks5r1djVgaJpZM4NMXS8
.

No longer using requireJS, as we found out that you can use native ES6 without browser compatibility problems. Martin and I had a small tutorial from him on Javascript Transpilers and converted our code accordingly.


Update docker-compose version for requests compatibility

I think this needs to be rebased to pass the CI. (it uses the outdated url to download fabric-bins)

@dexhunter Yes, but we need to rebase https://github.com/hyperledger/fabric-sdk-py/pull/12 as I do my branch to complete this PR, have you the rights to rebase https://github.com/hyperledger/fabric-sdk-py/pull/12 ?

I just asked the bot to rebase the branch. Let see if the test passes now

Besides, does @GuillaumeCisco approve this change?

I still have no idea why it always fails at first build. Is it caused by network or something else?


[v2] 404 for all hosts unless "localhost"

Any request sent to the gateway will return 404 unless the Host header is set to "localhost" even when the service has been configured with "testing.com".

The support is not in master yet.

The change was deployed and now config includes services.proxy.host with all hostnames to listen to.


[util] Add support for partial one-to-N connections.

This allows blocks such as edn connect to fewer than 4 modules at once
Signed-off-by: Timothy Chen<EMAIL_ADDRESS>

can you guys have a quick look?

closing this one since it's now part of #5107


[6.x] Add php serialize cast to castAttribute in Eloquent model

when cast an object attribute to a native PHP type, php object converted to stdClass.
i added serialize to castAttribute . with this cast when cast an object to a native PHP type, use original php class
for example:
class myModel extends Illuminate\Database\Eloquent\Model
{
     protected $casts = [
        'userObject' => 'object',
        'userSerializeObject' => 'serialize',
    ];
}
$model = new myModel();
$model->userObject               = new User();
$model->userSerializeObject = new User();
$model->save();

echo get_class($model->userObject) ; // stdClass
echo get_class($model->userSerializeObject) ; // User

Thanks, but that example you provided won't actually work. You can't serialize laravel models like that. Moreover, why would you want to?

Custom casts is available in 7.x.


Add rsyslog (Fixes #60)

The yum install and enable should be no-ops as rsyslog is already installed and enabled on the OS images we have on Oracle and Google.

LGTM, feel free to merge.


How to export GLB files through "SaveGLBToByteArray" method ?

Hi,
I want export glb files in a webgl project.  I tried method “SaveGLBToByteArray”，but nothing happened.
Can anyone point me at the steps to solve it please ?

Hi, by any chance did you get the solution to export gameobject from webgl?

Can you please test it with the latest version? When it's not working at all, can you please share some code snippets?


Canonicalize path before calling startsWith

Fixes Microsoft/vscode#52089 and #25279

What about test cases? Also, does this fix any of #25358 #24599 #25345 #25186?

I do agree with Daniel that we probably should err on adding more test coverage tho, considering this is used for paths in declaration emit now, too.

Also looks related to https://github.com/Microsoft/TypeScript/issues/25338

@sheetalkamat Do we have any existing case-insensitivity tests? I thought fourslash was case-insensitive but I can't reproduce the error in a fourslash test.

Figured out why fourslash test wasn't working, I needed to put a capitalized name before the importing directory.

@andy-ms can you also verify that this change fixes #25358 #24599 #25345 and #25186?

seems fixed on my pc@20180705

I'm running vscode 1.25.0 and typscript 2.9.2, still have this issue. Can anyone help? Thanks

install the typescript@next
set typescript tsdk to gloabl typescript lib, eg: /usr/local/lib/node_modules/typescript/lib

This is all cool, but angular cli does not allow to use the newest typescript. What should we do?

@smnbbrv Just install typescript globally with npm install -g typescript@next and point the editor to that.

@andy-ms thanks, it works!

for me installing @next did not work

solution for now was to only set VsCode to use workplace TS version. In my case that is the one installed with angular and it is 2.7.2

Maybe I say bullshit but if the typescript version is so crucial why don’t you guys just bundle it with vscode or at least give users some hint about mismatching typescript versions and the consequences of that? The way how it is done right now is so counter intuitive; it was properly working one version before, then it gets broken and the only way to fix this is using beta versions of typescript; that’s kinda... weird

The next version of VSCode should include the fix. VSCode insiders tomorrow should include the fix.
If you are on latest VSCode and want to try the fix out, you can find instructions on using a custom version of TS in your VSCode at: Using Newer TypeScript Versions.

@andy-ms  I just installed the latest insiders and am on TS 2.9.2 - you mentioned the new insiders should have the fix - should 2.9.2 + latest insiders be working? I'm still getting the same behavior as when I originally opened the issue.

:point_up: never mind, it does work when I update to @next. So for those dealing with this issue that aren't using insiders and tsnext, will they have to wait until 3.0.0 is shipping with VSCode?

@ratidzidziguri can you explain what you mean by using a "work-space" version?

@lucasklaassen or to anyone else looking: You can set your TS workspace version by following the steps here.

This last release of VS Code is so, so buggy.
Hope an upgrade is coming soon!
Does it make sense to allow people to revert after so many bugs were introduced?

You can always set your workspace version of TS to an older (or newer!) version of TS.

@ratidzidziguri can you explain what you mean by using a "work-space" version?

@lucasklaassen You can click on the right bottom toolbar of VS Code. Where you have the typescript version. From there you can choose the workspace version.

Is there any chance this can get into a patch release? This apparently fixes #52089? Which is a pretty bad regression, it's loss of functionality. Basically auto imports import the wrong file.
Thanks for all the hard work on this project. VS Code is awesome.


Fix/update dashboard data

This PR allows us to move away from Glitch totally and uses a MongoDB instead of the data.json file which was used previously.
When running locally, you must run npm run seed to populate the local db with the current production data.  This can also be used anytime you want to restore the local db to whatever is in the production db.
A cron job can be set up on dashboard-api/utils/update-db.js which will keep the MongoDB up to date.

@raisedadead This is a PR we will want to review and merge during our meeting.


Bug: Event is not included in the $cordovaKeyboard:show broadcast.

Should I add event to keyboardShowEvent() and $broadcast()?
https://github.com/driftyco/ng-cordova/blob/master/src/plugins/keyboard.js#L8
var keyboardShowEvent = function (event) {
  $rootScope.$evalAsync(function () {
    $rootScope.$broadcast('$cordovaKeyboard:show', event);
  });
};

When the keyboard opens, it does a $broadcast, but the original event object is not included.  So the listener can't get the information (like keyboard height) that is embedded in the event object.
I want to make sure this is correct before I submit a pull request.  Please let me know.

Anyone could comment on this?

Hi,
I am facing the same issue and was about to submit a bug :) I managed to fix the behavior by slightly updating your code. Since the only useful information is -at least in my case- the keyboardHeight, I do not forward the entire event (which would create an object with only one key: keyboardHeight), but only the keyboard height information:
var keyboardShowEvent = function (event) {
  $rootScope.$evalAsync(function () {
    $rootScope.$broadcast('$cordovaKeyboard:show', event.keyboardHeight);
  });
};


Create AddMultiWorkSheet.ps1

This example shows how to add multiple tabs within the same file.

@conradagramont Thanks for the example. This can be simplified. You don't need to do the -PassThru and  use Close-ExcelPackage. Just use  Export-Excel and on the last one use the -Show. If you can re-work that and commit it, should be able to merge it then.

Thanks for the for the feedback Doug!  I checked in the change.  It's cool to see that contributing my example actually helped me improve my own code!  Community coding at it's finest!!

Great! Do you have a Twitter handle I can use in the comments?

Twitter: @agramont


IBMBackend minor doc string fixes

Summary
Added blank lines before Returns: in some of the doc strings to avoid stuff like this:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2940

Relevant Lines:
6782

💛  - Coveralls


bower install | GutHub keeps asking for github username & password

I am struggling with this issue while installing bower install it keeps asking for github username and password everytime, does anyone has any idea or faces this issue ?
Error while installing -

It's because this repo/file doesn't exist anymore, probably.
On Fri, Oct 27, 2017 at 10:39 AM, GRawatCoder<EMAIL_ADDRESS>wrote:

I am struggling with this issue while installing bower install it keeps
asking for github username and password everytime, does anyone has any idea
or faces this issue ?
Error while installing -
[image: image]
https://user-images.githubusercontent.com/22786031/32095318-60d0efc4-bb20-11e7-883f-28f109efcf5b.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bower/bower/issues/2490, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAR2DZVx_AtS--I6fcbxpCcoSV6X16Zsks5swZbcgaJpZM4QIuUU
.

Thanks sheerun. I found owl carousel doesn't exist anymore ob bower.

how do i install owl-carousel now ? do you have any suggestion ?

maybe something like bower install OwlCarousel2/OwlCarousel2

updated the owl.carousel version mentioned in bower.json as ow.carousel 1.3.2 is not available on github repo which is why it keeps asking for github username and password.

I am getting the similar issue when I include blockUI in bower.json file. Git login popup is getting triggered and getting the following error message.
Error in plugin 'gulp-bower'
Message:
Failed to execute "git ls-remote --tags --heads https://github.com/ueqt/blockui.git", exit code of #128
Logon failed, use ctrl+c to cancel basic credential prompt.
bash: /dev/tty: No such device or address
error: failed to execute prompt script (exit code 1)
fatal: could not read Username for 'https://github.com/': Invalid argument
Details:
code: ECMDERR
details: Logon failed, use ctrl+c to cancel basic credential prompt.
bash: /dev/tty: No such device or address
error: failed to execute prompt script (exit code 1)
fatal: could not read Username for 'https://github.com/': Invalid argument
exitCode: 128
data: [object Object]