Please do not use init functions in library code

When updating container-device-interface from 0.3.0 to 0.3.1 we see a over 500 KB binary size increase in podman, https://github.com/containers/podman/pull/13610
However podman uses only small parts of the code in pkg/cdi, such size increase does not seem reasonable to me. Podman does not use any new logic.
Unless I am overlooking something the problem seems to be caused by https://github.com/container-orchestrated-devices/container-device-interface/pull/54
The use of init functions has two major problems:

First, it always runs on program startup so this slow each podman command down, even when most code paths will never even call CDI.

Second, it adds a lot unnecessary binary size because it calls code that way never be used otherwise by the library user. This is made worse by the fact that the PR started to embed the json spec into the binary.

I don't have enough knowledge about how this library is used to suggest a good fix.

Thanks for bringing this to our attention @Luap99.
@klihub could you have a look at this?

@elezar @Luap99 I'll take a look at getting rid of it.

Thanks for the quick fix.


⚠ Moon has degraded performance

In 8d51cb9, Moon (http://moon.sb) experienced degraded performance:

HTTP code: 200
Response time: 6348 ms

Resolved: Moon performance has improved in b53bdae.


Remove binary from git repo

I try not to have binaries in git, which this project currently has. You can remove it (and add a c++ .gitignore), and when you make a release you can manually upload the result of make (and change the link in the homewbrew formula to the uploaded binary) to the release.

Thank u jake ur an absolute babe and I love when you open issues on my repos ❤

Thank u jake ur an absolute babe and I love when you open issues on my repos ❤


fix(avatar): image always covers circle area

Fixes #480

just fyi, object-fit not supported in IE.  Experience there now will be a stretched image.

if that is an issue we can always explore background image and background size

Not an issue in my mind.  At least not yet...


Make goldenFileComparator a field instead of a trivial property

Removes an unnecessary abstraction.

test-exempt: trivial refactor with no semantic change


add search results provided by google

when you google something about date, time, currency, weather, google will provide the answer for you, like
'what time is it?'
'usd eur'
what do you think about adding this kind of results?

+1 !
Instead of links you should return a result object that has a links attribute plus other attributes.
Other things you could expose on this object:

The page URL
Page number
Search term
Scrapped Google response
Cheerio Object
Response HTML
The next callback

I think this would simplify the API and make it more extensible without breaking compatibility.
Of course this one change isn't backwards compatible and would require a major version bump.
You could make it backwards-compatible if the callback's length is 3 but that might be too hacky.
If you don't want to implement this scraping, I think you should at least change the response to an object like I describe and provide the cheerio object in it to allow custom scraping.

#38 proposes a response object, the scrapped result on this issue could be added to it. I actually need it, I can do it on my side once cheerio is exposed but I could add it to this module just as well


Uncaught Error: The Specified Module could not be found.

When I package my electron app with asar settings, this error displayed when the app starts.
Expected Behavior

Package the electron app with asar and iohook still run.
Current Behavior

When I Package the electron app with asar to false, the Iohook still working. But when the asar set to true, the iohook could not be found.
The following error displayed:

Uncaught Error: The specified module could not be found.
\?\C:\Users\Username\AppData\Local\Temp\452039c0-693f-4caf-99a7-393dc8f16557.tmp.node
at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:172:20)
at Object.Module._extensions..node (module.js:598:18)
at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:186:18)
at Module.load (module.js:503:32)
at tryModuleLoad (module.js:466:12)
at Function.Module._load (module.js:458:3)
at Module.require (module.js:513:17)
at require (internal/module.js:11:18)
at Object. (C:\Users\Username\Documents\TESTAPP\SOURCE CODE\release-builds\hirebrostimetracker-win32-x64\resources\app.asar\node_modules\iohook\index.js:17:21)
at Object. (C:\Users\Username\Documents\TESTAPP\SOURCE CODE\release-builds\hirebrostimetracker-win32-x64\resources\app.asar\node_modules\iohook\index.js:189:3)

Is there another way build package with asar and iohook?
Possible Solution

Don't have yet any solution
Steps to Reproduce (for bugs)

Build Package of Electron App using Electron Packager.
Set Asar to true.
Open App then in the console logs shows the error.

Context

I want to compile all the resources of my electron app
Your Environment

Version used: 1.8.4
Environment name and version (e.g. Chrome 39, node.js 5.4): Node.js v8.9.4
Operating System and version (desktop or mobile): Windows x64 and MacOS High Sierra
Link to your project: private repo

Hi there, We're happy to help :) Could you please edit your ticket to fit in our template ? It helps us diagnose your problem.

@Djiit  Ok sir, I updated again the issue thanks

Does the packaging without ASAR work ?
Did you put the correct ABI version in your package.json ?

@Djiit yes I input the correct ABI version in package.json, my applications works when the asar set to false.

Could you give us a link to your project OR a minimal project reproducing your error ? My main project using iohook is packaged in ASAR mode by electron-builder and everything is working great so far.

Hi there,
I'm closing this as this is old now. Feel free to ping me here if you have any further informations.

@pihey12
Maybe this help:
https://github.com/wilix-team/iohook/issues/160

Hello, exactly same problem here. Please provide some solution to this.

@Djiit The same problem

@vahagnsargsian try to update Visual C++ https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads. It should help

is this problem fixed? I'm still facing this in some client PCs using windows 10, not all but some of them

Me too, still the same problem on some Windows 10 PCs

I have too this problem on some Windows 10 PCs

still having same problem on some windows pc-s, now with electron 9 and iohook 0.6.6
its just giving "Specified module not found", trying to find iohook node which is there...

Typically when asar is set to true, native node modules like iohook must be excluded from the asar via the "asar": {"unpack": ...} build setting. Did you include that in your package.json?

Just add msvcp140.dll and vcruntime140.dll to your app root. If you use electron-builder use "extraFiles"
"extraFiles": [       {         "from": "dir-with-your-dlls",         "filter": [           "*.dll"         ] }


Moving to GitHub has broken the staging scripts for the Core-Model

Instead of storing .prj and .sln files in source control, the Core-Model relies on a series of .lua scripts, .bat and .txt files to download the current third-party libraries and generate the .prj and .sln files. These scripts have google-code repository urls hard-coded into them. Since the source code has been moved, the scripts no longer work and will only become less usable when google code goes offline.
Unless we have a resource to update these scripts, we may want to store the libraries with the core-model project and reference them directly. The library version have been static thus far. We can also store .sln and .prj files to avoid having to use the scripts.
Also open to other suggestions ...

I found that the scripts were broken due to a folder that was not migrated from SVN to GitHub. I added this folder to GitHub and the scripts work. This is a temporary solution as the LSML downloads still reside on GoogleCode. GitHub doesn't offer a distribution mechanism similar to GoogleCode downloads. GoogleCode recommends moving the downloads to Google Drive which could work but there is still work to be done. The scripts have some checksum and security elements that don't appear to be compatible with Google Drive. I'm not a fan of moving the downloads into source control because the repository is already quite large and syncs take a while.

LSML downloads have been moved into the core-model. This includes GDAL. Scripts have been modified to use these new locations to help stage scripts.
This Issue is complete and can be closed.


Help

Hello sir，this is an excellent project, thank you for your paper.
I'm not smart enough to know your code particularly well. Could you please give me a more detailed explanation? Thank you so much!
Best wish,
Chris

If I understand you correctly, we binary classify the dataset and the classification feature is thecategorical attribute, i.e. we are classifying based on the CATEGORICAL attributes. So what are the numeric attributes used for?

Hi Chris,
I hope I understood your question correctly.
In case the label is not provided we pick a categorical attribute as a label. The numeric attributes are part of the regular training set, together with other categorical attributes. The selection of the label is specific to your use case and is not mandatory, the model can also be trained without a label (unconditional training/sampling). However, to measure the Utility of the model, we need labels. Hope that helps.
Best regards,
Timur

Closing due to inactivity


Finding adjacent voxels in 2d or 3d space

Fixed the index ordering: (x, y[, z]).

Needs another fix.


[Feature] Hyperband and Successive Halving Hyperparameter optimization

Hi there!
Hyperband has shown the ability to do state of the art hyperparameter optimization. I implemented it with skopt dimensions.
Here is a gist if you are interested in incorporating the algorithm: https://gist.github.com/Deepblue129/2c5fae9daf0529ed589018c6353c9f7b
Thanks!

Thanks for this!
Question to others: should we grow scikit-optimize beyond sequential model based optimisers?

IMHO I am fine with going beyond SMBO, as long as we see that it is better than alternatives in being able

to minimize (very) expensive and noisy black-box functions.

:)
So this should go on my reading todo list:
http://proceedings.mlr.press/v51/jamieson16.pdf
Thanks @Deepblue129 for bringing this up!
IMHO before integrating this it would be good to do the clean up of the library, as was discussed somewhere a bit earlier, with a thought in mind that the algorithms like the one referenced here might be integrated.

Haven't had a chance to read the paper but i will surely do.

Question to others: should we grow scikit-optimize beyond sequential model based optimisers?

I think we should, provided that a) any new algorithm can be used together with the existing interfaces (i.e. we can stick to the main API, including future adaptions, and avoid too many special cases) and b) it has a use case and / or differs at least in some aspect from the other optimizers.

From a quick read of hyperband it seems like it relies on a smart idea of not training each model to completion, but stopping earlier and using that as an estimate for "full performance". This means it is specific to ML models (or black box functions that can be "resumed"/can be evaluated partially).
We should spend a bit of time thinking about how to fit this into the API.

To help anyone with a tl;dr on the algorithm:
"The idea successive halving is remarkably simple. We first try out N hyperparameter settings for some fixed amount of time T. Then, we keep the N/2 best performing algorithms and run for time 2T. Repeating this procedure log2(M) times, we end up with N/M configurations run for MT time."
[http://www.argmin.net/2016/06/23/hyperband/]
Hyperband is built on top of successive halving.

Maybe a good way forward is to add a new HyperbandSearchCV next to BayesSearchCV. That way we avoid having to figure out what to do when people try and use hyperband on functions that can't be frozen/resumed.

Hyperband paper on arxiv: https://arxiv.org/abs/1603.06560 (relation to http://proceedings.mlr.press/v51/jamieson16.pdf ??)
Recent follow up paper combining SMBO with hyperband and claiming better performance: https://arxiv.org/abs/1801.01596

Hyperband would be indeed a great addition; specially for speeding up search for neural nets


paragraph transformation in source twice

on Line #27 it has another paragraph transformation. Is this purposeful or just oversight? I'm doing some general cleanup and wondering if I'm missing something by removing this?
Thanks!

@groteworld
It is simply an oversight, nothing purposeful. I have been keeping this cleanup for next update, but there is nothing in general I can provide as next update. I have tried to avoid introducing any unintended complexity keeping the library flexible as much as possible, which have so far been the initial goal.
However, Thanks for looking into it and letting me know.  :heart:


DRILL-5717: change some date time test cases with specific timezone or Local

Some date time test cases is US Local .This will cause developers from other areas to fail. Fix is to specify the explicit Local to the test cases.

Some tests from TestDateFunctions, TestDateConversions and TestConstantFolding classes also fails with some other locales (I checked it for zh_TW locale).
I think they should also be fixed in the border of this PR.
Are there any other tests that depend on the locale?

Yes, thanks for the notice ,have noticed those cases before ,the work is in process.some of that will be part of this PR. Others like sql_to_timestamp function need to discuss whether it should have a Local parameter or not set the specific UTC timezone when get the date.

update points :

remove commons-codec dependency for 1.4 vs 1.10 conflict
fix to_date , to_timestamp ,to_time ,sql_to_date ,sql_to_timestamp, sql_to_time function

@vvysotskyi sorry for the late update as have passed a busy week.
update points:

move out the pom update
recover the date related templates and update the related test cases by specify specific timezone and Local.

@vvysotskyi  please review the update ones

@vvysotskyi has updated the mentioned parts. These 4ea36c3, caa8b78 two links has been deeply thought about . I think they can't be solved using the same approach at current PR. They are too old to lost some function definitions like casttimestamptz . VectorUtil.appendVectorAccessibleContent 's date format does not retain time zone part.  So I suggest they should be kept there or removed.

@vvysotskyi thanks for your patient review . As you pointed out  , the timezone would not take effect when test cases run in parallel. I also tried the mock strategy. It will also fail in parallel. So I moved out that part of code to a new class called TestCastFunctionsSpecTZCases by specifying the timezone before the cluster starts up. It would be clear to the codes.

@vvysotskyi, can you take a look at the revisions and see if it looks OK?

@weijietong which problems did you have when tried to mock System.getProperty() method?
As the example of nice mock of this method, you may use this test. Also besides the timezone, property with locale should be mocked.

@vvysotskyi  the problem with mocking strategy is that when I run the test case just with the single method testToDateForTimeStamp it will pass. but when I run the whole test cases of the TestCastFunctions  , the included testToDateForTimeStamp method will fail.

@weijietong thanks for the explanation of your problem. I was able to reproduce it, but also I found working solution. This mock works correctly. The problem appears when unit test is run with other tests: DateTimeZone class contains static field cDefault which is used to receive timezone in testToDateForTimeStamp() and in other tests. When timezone does not set to this field, but method getDefault() is called, value is taken from System.getProperty().
When the first test that calls this method does not have a mock, it sets a real value of timezone from System.getProperty(). Therefore our test uses a unmocked value from cDefault.
So lets mock DateTimeZone.getDefault() method:
    new MockUp<DateTimeZone>() {
      @Mock
      public DateTimeZone getDefault() {
        return DateTimeZone.UTC;
      }
    };

@vvysotskyi thanks for your hard work, I have rewritten the corresponding method. But I have not rewritten the other Locate related cases. Since mockup is a white box testing , I payed some tedious work to explore the possible invocation path, maybe the same as you. I think current Local solution is also acceptable.

@vvysotskyi  thanks for your help! have done, please review.

@vvysotskyi any more advice ?

applied the review comments

done

@weijietong, thanks for the pull request, +1

+1, LGTM.


Init commit of 'The Methodology of Service Mesh Performance'

Signed-off-by: Huang Xin<EMAIL_ADDRESS>Description
This PR created the markdown file docs/pages/dashboard/methodology.md described "The methodology of Service Mesh Performance", which didn't contained any HTML, CSS and JS.
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

New layout added.


[CI] Fixing GitHub actions outputs deprecated syntax

About this PR
Current output syntax used in github actions is deprecated. This addresses https://github.com/bytecodealliance/wasm-micro-runtime/issues/1639.
Signed-off-by: Andrés Felipe Barco Santa<EMAIL_ADDRESS>

Hey @lum1n0us! Just letting you know about this PR given that you are the author of https://github.com/bytecodealliance/wasm-micro-runtime/issues/1639
For reference: https://github.com/bytecodealliance/wasm-micro-runtime/pull/1641


ENTSWM-192: Update prod boosters to Swarm 7.0.0.CR2 (next)

Do you want this merged Heiko? Or is still a WiP?


Cannot use NgsRevealModule Module in Angular 16

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

OS and Version?

Versions
MacOS Big Sur 11.6
Angular CLI: 16.1.1
Node: 18.13.0
Package Manager: npm 8.19.3
OS: darwin x64
Angular: 16.1.2
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Package                                          Version
@angular-devkit/architect            0.1601.1
@angular-devkit/build-angular    16.1.1
@angular-devkit/core                   16.1.1
@angular-devkit/schematics       16.1.1
@angular/cli                                   16.1.1
@schematics/angular                   16.1.1
rxjs                                                  7.8.1
typescript                                      5.1.3
Repro steps

npm install --save scrollreveal
npm install --save ngx-scrollreveal
In angular.json add this line
"scripts": [
"node_modules/scrollreveal/dist/scrollreveal.js"
]
Add in your feature Module.
import { NgsRevealModule } from 'ngx-scrollreveal';
...
imports: [NgsRevealModule]

Run the app:

ng serve

The log given by the failure
Error: src/app/app.module.ts:15:5 - error NG6002: 'NgsRevealModule' does not appear to be an NgModule class.
NgsRevealModule,
   ~~~~~~~~~~~~~~~

node_modules/ngx-scrollreveal/ngs-reveal.module.d.ts:6:22
export declare class NgsRevealModule {
                       ~~~~~~~~~~~~~~~
This likely means that the library (ngx-scrollreveal) which declares NgsRevealModule is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

From Angular 15 I get this when compiling.
Generating browser application bundles (phase: setup)...Processing legacy "View Engine" libraries:

ngx-scrollreveal [es2015/esm2015] (git://github.com/tinesoft/ngx-scrollreveal.git)
Encourage the library authors to publish an Ivy distribution.

As per the documentation, it shoud work for Angular 6+. However, it doesn't. My Angular is 17. It throws exactly the same error.

@turboaux @niamat-bakhshi anyone know what the complexity is with supporting Ivy so we can push a PR?


delete unused github action

this doesn't work, and we have unit tests running on prow
xref: #56

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_oci-proxy/57/pull-oci-proxy-test/1517213117421981696 unit tests here

/lgtm


Freshly created collection does not get pre-selected for Item insertion

Create top-level Community "Community 1"
It gets displayed in view mode
Pick option to create new Collection
Community "Community 1" is preselected in "new Collection" Community selector : "search.resourceid:047eb94a-d0d0-41bd-b761-6643d6d253ef"
Pick "Community 1" and add "Collection 1"
Collection "Collection 1" is displayed in view mode
Pick option to add new Item
New Item dialog does not preselect the "Collection 1" in collection picker

Expected - the collection, which is currently open in DSpace  (view or edit modes) should be pre-selected in collection picker.

The estimate for this ticket is included in my estimate for #843

Thanks. I've added a 0 hour estimate to this ticket, as it will be solved by #843


I need your help with implementing your config folder on Ubantu

stion" tag.
On Ubantu, I downloaded a lot of dependencies from your Dockfile. Execute runtest. I want to know if this builds successfully
If successful, why only one Cpp file was generated

What is your expectation and how is the result different from those expectations? What commands did you run?

I want to reference it in Qt as a server up and down function

The CMake script for finding the ZooKeeper server classpath generates a CPP file per ZooKeeper library version, so it looks like it is working as intended. I'm not sure what you expect to happen here.


Let the choice to pick other frontends

Is this modular enough to be able to write "extensions" to pick the fontend you want (Vue.js, React.js, etc...) ?

This is actually one of the first points on the roadmap. Currently, Crana only supports React out of the box. But since everything regarding configuration is encapsulated into the package, the current version doesn't offer such a possibility yet. I am working on an extension system which allows to modify/extend every configuration aspect of Crana. Those extensions could either be "installed" via an npm package or manually set up per project. The next minor release of Crana will contain a system like that, and truly go into the direction of "CReate A Node Application". What do you think?

can you detailly explain how to run the crana project.


fix(sender): start senders after answer is received

a race exists where rtp can arrive at the remote client before they have handled the sdp. this delays sending the rtp until the sfu has received an answer from the remote client

Lgtm!


Finalize selection of co-chairs, due to open role

@beekemarie has decided to remain involved with the DEI-SIG but will be stepping down from the co-chair role-
To fill the co-chair role, @Perelmuter posted in the minutes for the March DEI SIG that the call for co-chairs was open, and that interested individuals should respond or contact her directly.
This issue can be closed when the selection of co-chair(s) is complete.

Thanks for resharing @PaulaPaul - we are looking to resolve this tomorrow April 3rd -As shared on March 18th, Individuals interested in the vacant Co-Chair position should contact me at<EMAIL_ADDRESS>noting their background and ability to contribute.
Before putting themselves forward, It is important that individuals understand the time commitment and accountability requirements of the role.  The Co-Chair role is operational akin to COO responsibilities: Here is a description of the OSR SIG Leadership responsibilities as an example.  In addition to meeting planning and execution, it is expected that co-chairs will co-share preparation of the agenda/minutes/action items from the call as the SIG needs to be self-sustaining. In addition, the Co-Chairs will need to monitor and be responsive to the standard communications channels (Slack and GitHub, or others as determined by the Chair and Co-Chairs), and communicate their availability on standard channels when they are time constrained or out of office.
It is important that there is clarity on role differentiation and shared responsibility to ensure that the SIGs are run effectively and can become self-sustaining.    If more than one candidate emerges, we may consider adding more than two co-chairs.
A clarification WRT to Co-Chair Selection from FINOS Executive Director Gabriele Columbro - As the DEI SIG expands its remit, we are open to multiple co-chairs.  We would ideally like to see co-chairs selected by the SIG based on their stated contributions, experience  and ability to dedicate time to co-chair responsibilities. Elections are time-consuming to administer so ideally we would look to gain consensus on co-chairs with complimentary contributions on the next SIG call taking place on April 3rd.
Furthermore, exciting  opportunities for important issues are listed under 'to-do' here: https://github.com/orgs/finos/projects/94/views/1 -  we would be excited to see volunteers step forward for these roles to spearhead and take forward!

Hello All -- I hope you're all well.
My name is Sérgio Bettencourt and I have been actively involved in the DEI SIG for the past year representing Citi.
Following conversation with Rimma, I am submitting myself as candidate for Co-Chair of the SIG.
Though my background is primarily aligned to Financial Services and Technology, I have a strong history in both Human Capital and Diversity, Equity and Inclusion spaces and I am passionate about building and motivating communities toward addressing issues of greatest impact.
With respect to experience, I have spent most of my career involved in some leadership capacity across organizations aligned toward improving the experience of individuals of diverse communities, most recently within Citi as a Co-Chair of an internal global strategy focusing on addressing opportunity gaps for Black/Latinx professionals and their allies. In this role I am responsible for internal programming aligned to building community, resource retention, professional development, and organizing flagship events such as an annual conference and heritage aligned development and networking events. The experience has been one of the highlights of my career and has fundamentally change my experience of work and how I see myself as a professional.
Please be sure to reach out to me should you have any questions and I hope I can count on your support.
I look forward to working with each of you as we move forward.
Thank you.
Sérgio

Sérgio Bettencourt and @PaulaPaul were selected as co-chairs on the DEI SIG call, April 3rd :)


chef access to os package info mangled > 12.8.1

Description
Omnibus install using latest 12.9 started throwing errors on unchanged cookbooks. Github link to original issue thought to be in the cookbook https://github.com/dev-sec/chef-os-hardening/issues/112
Chef Version
chef-solo: 12.9.38
ohai: 8.14.0
Platform Versions
OS image: Amazon Linux AMI release 2015.09 (ami-f0091d91)
OS Image: Centos 6.7
Replication Case
Include os-hardening cookbook in your chef run with 12.9.x client install.
Client Output
chef-solo log: https://gist.github.com/rljohnsn/36cdf0e8525f5113a56afd8a69c85cfc
ohai output: https://gist.github.com/rljohnsn/8cd4b428e73c3d465376b072183787ba

You need to be a bit clearer about what you're seeing in ohai output and what you are expecting.  Your ohai output looks fine to me, so what do I need to be looking at?
AFAIK, we added the packages plugin to ohai sometime around 12.8.1 timeframe, but we were supposed to be adding it disabled:
https://github.com/chef/ohai/pull/717
If you are expecting a different format,then its likely that you were pulling in a custom plugin that was not in core which the new core plugin overrode.  We also might have a bug since the new core plugin was supposed to be disabled by default.  On the other hand, we're going to make the core plugin enabled by default and it'd be better to migrate to using it anyway.

This is also an ohai issue and should really get opened against https://github.com/chef/ohai/issues/new

Yeah this is solidly a bug in the cookbook:
https://github.com/dev-sec/chef-os-hardening/pull/88


Add meta information from admin-panel to config-sil.json

Signed-off-by: Cornelius Claussen<EMAIL_ADDRESS>

Outdated, will be recreated at some point in time


Feature/demos

Just saw there are some files I need to remove that reference my local machine, don't merge yet.

ok should be good now


[WIP][do-not-merge]Add training nb

Depends on #74, please ensure that PR is merged before adding this.
This PR adds

train / infer notebook
config files for model fine tuning using FARM

Closes #11

@chauhankaranraj Can we close this now? I guess since we moved to the inference pipeline we didn't really get back to this.

Hm I believe this (wip) addresses #11, which is a part of the epic #120. So maybe we can keep it open for now, and push updates here when we get back to the training side of things?

@chauhankaranraj: Closed this PR.

In response to this:

Closing this PR as it's replaced by #155
/close

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


Unary NE implementaion

op : ElemwiseUnary/ELEMWISE_UNARY_NE
ARCH: GS, WHB0

#7234 Merged (TTNN implementation removed)


Is it possible to use WinRT XAML controls in WinUI 3?

I know the XAML Islands, but these existing docs are all about Win32, WinForm and WPF. How to use custom and 3rd party WinRT (UWP) XAML controls in WinUI3?

Components targeting the UWP platform (System Xaml) like Windows Community Toolkit are not compatible with WinUI3 by default. Windows Community Toolkit and many of our other partners have produced compatible versions.
WinUI3 does not support islands to WinUI2.
@MikeHillberg to double check

@marb2000 FYI

Thanks for your reply. I have two problems here.

I've made a lot of custom controls over the past decade, based on C++/CX and PPL. The Windows App SDK only supports C++/WinRT, so rewriting them will take a lot of work. And I also have some 3rd party controls, not WinUI2. Is there a way to keep using these controls? Or will it be supported in the future?
It seems that WinUI3 Composition can't be used with MediaPlayerSurface?


isInternetReachable returns false even internet is connected or when the application is running in the background, then moving through different wifi areas, when it is reconnected, it still says that there is no connection

Environment

Platforms

Versions

Android: 9
iOS:
react-native-netinfo: 6.0.0
react-native: 0.64.0
react: 17.0.1

Description

Reproducible Demo

We have the exact same issue I think. If I open the simulator on my mac before I go to home from work, and open the computer the next day the screen is stuck at the no-internet phase. The hook returns isInternetReachable: false and I also tried calling fetch() (the simulator was still connected to Metro), which also returns no internet state.

@hermanbanken I'm running the app on a real device

@phucph1998 have you read the related issues here with their threads?
It appears the android system just provides unreliable information in this area, and no one yet has dedicated sufficient resources to make the information returned here reliable. That could be you though! If this is important for your business, dig in and fix it, it will be a service to humanity for sure.
In the meantime you may like to use the explicit / imperative force refresh methods added here recently along with the ability to specify your own connectivity check method, and retry failed network requests after forcing a network connectivity re-check and seeing it's online.
This is essentially duplicate of the other threads, I will close it


CDC #16 - User defined fields

This pull request fixes an issue that was occurring when only searching against user defined fields. If the query provided to the apply_user_defined_sort method was including all records, oring the query with the user-defined-fields query was always returning all results. A check has been added to merge the query if that is the case.
Additionally this pull request also updates the user_defined JSON field to store the keys as uuid values, instead of the user-entered text label. There are also migrations to convert existing values.

@camdendotlol - Would you mind reviewing this if you have a second? Specifically the part about updating the JSON keys to use uuid values instead of the label. There will also be an accompanying PR in the react-components repo to update the front-end, which I'll add you to as well.


Add auto-backup

Implements #62

Again — should have created a separate PR for creating constants for the ConfigType

Looks like the move to the src folder broke this one. Once it's rebased I'll take a look

Rebased.

This implementation does not include the max_backups setting discussed in https://github.com/bndw/pick/issues/62. What are your thoughts on including that in this PR?

It's not easy. We would either need to parse all backup file names and sort them by date, or simply sort by os.FileInfo.ModTime(). I don't like both ways.
Until I figured out a better way, this PR should be merged ASAP.
I will work on the max_backup feature this weekend.

Implemented max_backups.

Updated, rebased & merge target changed.
I decided to put the backup configuration to [storage.backup] as it's clearly related to storage.
Also it's not as simple to move it to the main config ([backup])

LGTM


Create changelog page

This PR tackles #57. I am providing screenshots of the design
The content in the page is generated via an array in /src/constants/changelogArchive.ts. I have left a JSDocs comment in there that explains how to work with it. This means that for every version release, all we have to do is simply update that array and this will be reflected in the page.
I have also made the page responsive. The current mobile design centers the Features/Fixes/Deprecated headings and aligns the bullet points to the left. In the screenshots above, I have also showcased a potential design where the headings are left-aligned as well for better symmetry, so I would appreciate feedback on which design is preferred
This PR also updates the navigation Buy/Search/Trade tabs bar to include a link to the main about page (which doesn't exist currently). With that said, I think it should receive some refactoring since it could potentially use the tabs component provided by MUI rather than use the current custom implementation and I remember even encountering cases where none of the links are selected (though I would need to investigate the steps for reproduction). It would be more appropriate to tackle this in a separate PR and I will likely open an issue regarding this at a later point and then fix it myself.
Let me know if there are any issues
edit: the page can be accessed on /about/changelog

Good job
You can remove the v0.9 version because it was just a filler
I personally think the way it is now is good. On bigger screens, we have the version to the left and the rest of the content in the middle. On smaller screens everything is in the same column, which looks good. Definitely needs to be left-aligned, though!
Feel free to rework the nav to be a MUI component, I also think this is a good change (in this PR or in another one)

Removed 0.9.0. Nav update will likely be in another PR (might be better to queue it for 1.2 since I will be focusing my attention to page implementation for 1.1), will open an issue for myself once I figure out the steps to reproduce the bug I mentioned.

3. Definitely needs to be left-aligned, though!
Just to clarify, do  you mean that the headings must be aligned to the left (aka start from the same line as the bullet points) or that the container itself needs to be aligned to the left

Just to clarify, do you mean that the headings must be aligned to the left (aka start from the same line as the bullet points) or that the container itself needs to be aligned to the left?

In my opinion, in mobile view, the headings aligned to the left (same line as bullet points) looks better.

done and this should be ready for merging


What am I doing wrong - I always get errors and req.body.password is undefined

router.post('/register', [
    check('name', 'Name is required').exists(),
    check('email', 'Email is required, and must be an email')
        .isEmail()
        .custom((val) => {
            // find the user by email
            console.log(val);
            return true;
        }),
    check('username', 'Username is required').exists(),
    check('password', 'Passwords must be at least 5 characters and container one number')
        .isLength({ min: 5 })
        .matches(/\d/),
    check('password2', 'Passwords do not patch')
        .exists()
        .custom((val, { req }) => {
            console.log(val, req.body.password);
            return val === req.body.password;
        }),
], (req, res) => {
    const { name, username, email, password, password2 } = req.body;
    console.log({ name, username, email, password, password2 });
const errors = validationResult(req);
    if (!errors.isEmpty()) {
        console.log('we got errors');
        const obj = { errors: errors.mapped() };
        console.log(obj);
        return res.render('register', obj);
    }

    console.log('no errors');
    return res.status(200);
}

In the password 2 custom val and req.body.password are all empty, but when I console log the fields they are all there. Every value is coming back undefined.
All the examples show app.post(...) is that the problem? I am using express.Router()

This doesn't seem right; how are you defining the body parser middleware?
Anywhere a middleware is accepted in express, express-validator should work just fine.
As a last resort, if we don't solve this quick enough, you could try migrating your code to the legacy API temporarily.

ping @jefflindholm - are you still tracking this?

Hi @jefflindholm, I went to your profile and saw you uploaded the app you're building with express-validator.
I checked the code where you are doing validations. Your example is different from the one in there!
Please see this SO question, as it must be pretty similar to what you're experiencing:
https://stackoverflow.com/questions/46046254/new-express-validator-syntax-validate-form-processed-by-multer

I will take a look I had to travel this week unexpectedly so did not have
time to look
On Fri, Sep 29, 2017 at 8:41 PM, Gustavo Henke<EMAIL_ADDRESS>wrote:

Closed #436 https://github.com/ctavan/express-validator/issues/436.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ctavan/express-validator/issues/436#event-1272570187,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAI52_kkJeZ5c_KibTJoQAIuJqZzINstks5snY5WgaJpZM4PjRwb
.


cannot send verify email ...

Describe the bug
SMTP login should use special authorization code instead of QQ password when sending verification mail...
see:
http://service.mail.qq.com/cgi-bin/help?subtype=1&&id=28&&no=1001256
To Reproduce
Steps to reproduce the behavior:

Go to 'setting'
Click on 'SEND EMAIL'
See error

Expected behavior
Failed to authenticate on SMTP server with username<EMAIL_ADDRESS>using 1 possible authenticators. Authenticator LOGIN returned Expected response code 235 but got code "535", with message "535 Error: ��ʹ����Ȩ���¼�������뿴: http://service.mail.qq.com/cgi-bin/help?subtype=1&&id=28&&no=1001256 "..

This is a known issue related to QQ Mail's policy, we are not intended to fix that right now because we are going to using third-party mailing services in the future.


Upgrade for Vaadin 18+

The component is not working for Vaadin 18+

When clicking on a single row, it seems to select all rows from the bottom up to the selected row.

Any plans to add Vaadin 18+ compatibility in the near future?

I'll try to update the component for Vaadin 23.

It's updated to Vaadin 23 (version 2.0.0) and will be updated to Vaadin 24 soon.
I'm closing this one since Vaadin 18 is outdated


Taking too long to run!

A user commented on a long run time for BreaKmer, below is the correspondence:
The algorithm has been running for more than 48 hours and have still not finished processing the data. So, I was wondering if you can offer some insights about what are the more time consuming steps in the process and how to speeding them up.
Dataset: Target panel of about 10 genes with mean coverage ~700x
PC: 16 GB memory ram

I have questions about this as well.  I would like to run this genome-wide, but I've been running it on a single chromosome as a test for only rearrangements and translocations for over 72 hours on a cluster node with 28GB RAM. Can BreaKmer be run over a whole genome and how?

First, I apologize but BreaKmer was not designed to scale for whole-genome analysis. How are you running it on a single chromosome, just using the genes on that chromosome as targets? I can imagine that the target reference files would take quite a long time to prepare for this. Nonetheless, I don't have any current strategies for the current version to be able to tackle a whole-genome analysis. Future versions may be able to handle it.
I suggest you check out WHAM, developed by Zev Kronenberg. He has developed a nice SV analysis program that is able to handle WGS data.

Ok, that's what I needed to know.  I can see how I would use this in targeted analysis but I was asked to run it across a whole genome.  Thank you very much for your response.


Dev

Q
A

Bug fix?
no - yes?

New feature?
no - yes?

New sample?
no - yes?

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
Please describe the changes in this PR. Sample description or details around bugs which are being fixed.
Guidance
You can delete this section when you are submitting the pull request.

Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to Dev branch.

Hi @krunaljani, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

Seems like a mistake in PR submission, so closing.


Update s3.go to enable content-md5

Per #49
If my understanding is correct, the MiniO library actually does most of the heavy-lifting for you so all that should be needed is setting the putObjectOptions.SendContentMd5  flag and the MinIO library will automagically do the rest for you, which makes enabling this enhancement pretty easy.
I have worked on the assumption that the desired default behaviour is to enable sending Content-MD5 since doing so has significant benefits (upload integrity) and minimal downsides (on modern processors calculating MD5 should not be a demanding task).  But I have attempted to add a way for people to disable sending it if they feel they need to.
N.B. I am not overly familiar with the simpleblob codebase so its possible I might have missed another section of code that needs to be "touched" but as I understand everything calls doStore() in the end.

LGTM. Thank you for this :)
I'll make a v0.2.6 release now. You can open a PR for lightningstream with the upgrade so you have full credits!


How to target linked/nested template to a different resource group?

The page contains the statement:

If the linked or nested template targets a different resource group, that deployment uses incremental mode.

However, there is no guidance here or in any other pages I could browse to actually tell me how I can make a linked/nested template target a different resource group. A link to such guidance here would be very helpful.

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

ID: 06ebdf4d-7dda-0449-d8cb-441535dd2e32
Version Independent ID: 171ad1a9-f6bf-4646-6bd3-3a52b64126ba
Content: Link templates for deployment - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/linked-templates.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

Thanks for bringing this to our attention. We will investigate it further and update you shortly.

The article will be updated later today.
#please-close


Reformatting whole repo with Black

Description

We are adapting black formatter and this is an urgent PR for reformatting of whole repo.
Type of change

[ ] Bug-fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[X] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Final checklist:

[X] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

This looks good to me, but a couple questions

Do we want to also format the _vispy folder as at some point we might want to merge that code back in and smaller diffs will be easier?
Do we want to format the vendored folder in colormaps as isn't there some stuff we've taken from other places there that we might want to keep the same?
Does this PR also add a test to check if the repo has been formatted correctly or is that planned in a followup PR? I think I'd rather see it in this PR too if possible as then we know we won't accidentally start breaking our formatting, but I'm open.

Would be great for @kne42 and @jni to weigh in and then we can move forward

I would say:

yes, also this should be refactored into a compat folder
no, we want easier diffs if this is really just copy/pasted from matplotlib
it shouldn't be too difficult to add but i dont think it should go in this PR since it has such a large diff

Thanks @kne42, I'll let @jni weigh in on vendored as he made that folder.
If @AhmetCanSolak can be ready to make a follow up PR that adds a test for compliance with black -S that would be great, as then we can get both of those in

I think we should add that format check to CI in a separate PR.
for vendored i am open to both, let's see what @jni will say.

Thanks @jni @sofroniewn @kne42 . As far as i understand we are good to merge if i take reformatting on vendored back. Will do and merge today.

sounds good to me @AhmetCanSolak

ah, i totally forgot about the upstream case, thanks @jni for reminding me!
with that in mind i think that both vendored and _vispy (and maybe even util.event) should be ignored

Hello @AhmetCanSolak! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file examples/add_image.py:

Line 14:80: E501 line too long (86 > 79 characters)

In the file examples/add_pyramid.py:

Line 17:80: E501 line too long (84 > 79 characters)

In the file examples/set_theme.py:

Line 12:80: E501 line too long (87 > 79 characters)

In the file examples/shapes_to_labels.py:

Line 97:80: E501 line too long (81 > 79 characters)

In the file examples/to_svg.py:

Line 98:80: E501 line too long (81 > 79 characters)

In the file napari/__init__.py:

Line 6:80: E501 line too long (82 > 79 characters)

In the file napari/_version.py:

Line 71:80: E501 line too long (86 > 79 characters)
Line 123:57: E203 whitespace before ':'
Line 193:27: E203 whitespace before ':'
Line 210:36: E203 whitespace before ':'
Line 244:80: E501 line too long (87 > 79 characters)
Line 296:80: E501 line too long (88 > 79 characters)
Line 310:57: E203 whitespace before ':'
Line 321:80: E501 line too long (84 > 79 characters)
Line 518:80: E501 line too long (82 > 79 characters)

In the file napari/components/_dims/model.py:

Line 46:80: E501 line too long (88 > 79 characters)
Line 58:80: E501 line too long (86 > 79 characters)
Line 169:80: E501 line too long (83 > 79 characters)
Line 176:80: E501 line too long (83 > 79 characters)

In the file napari/components/_dims/view.py:

Line 197:80: E501 line too long (86 > 79 characters)
Line 230:80: E501 line too long (88 > 79 characters)

In the file napari/components/_layers_list/model.py:

Line 46:80: E501 line too long (80 > 79 characters)

In the file napari/components/_layers_list/view/main.py:

Line 45:80: E501 line too long (88 > 79 characters)
Line 74:80: E501 line too long (88 > 79 characters)
Line 144:80: E501 line too long (82 > 79 characters)

In the file napari/components/_viewer/model.py:

Line 114:80: E501 line too long (82 > 79 characters)
Line 251:80: E501 line too long (84 > 79 characters)

In the file napari/components/_viewer/view/main.py:

Line 132:80: E501 line too long (84 > 79 characters)
Line 177:80: E501 line too long (86 > 79 characters)

In the file napari/components/_window/view.py:

Line 76:80: E501 line too long (85 > 79 characters)

In the file napari/layers/_base_layer/_visual_wrapper.py:

Line 43:80: E501 line too long (88 > 79 characters)
Line 93:80: E501 line too long (86 > 79 characters)

In the file napari/layers/_base_layer/model.py:

Line 122:43: E203 whitespace before ':'
Line 369:80: E501 line too long (84 > 79 characters)

In the file napari/layers/_base_layer/view/properties.py:

Line 84:80: E501 line too long (82 > 79 characters)
Line 94:80: E501 line too long (81 > 79 characters)
Line 186:80: E501 line too long (85 > 79 characters)

In the file napari/layers/_image_layer/model.py:

Line 66:80: E501 line too long (80 > 79 characters)
Line 273:80: E501 line too long (82 > 79 characters)
Line 461:80: E501 line too long (84 > 79 characters)

In the file napari/layers/_image_layer/view/properties.py:

Line 20:80: E501 line too long (85 > 79 characters)
Line 29:80: E501 line too long (87 > 79 characters)
Line 35:80: E501 line too long (83 > 79 characters)

In the file napari/layers/_labels_layer/model.py:

Line 49:80: E501 line too long (88 > 79 characters)
Line 114:80: E501 line too long (86 > 79 characters)
Line 389:80: E501 line too long (81 > 79 characters)
Line 446:80: E501 line too long (83 > 79 characters)
Line 447:80: E501 line too long (83 > 79 characters)
Line 476:80: E501 line too long (85 > 79 characters)
Line 500:80: E501 line too long (83 > 79 characters)
Line 561:80: E501 line too long (84 > 79 characters)
Line 615:80: E501 line too long (82 > 79 characters)

In the file napari/layers/_labels_layer/view/controls.py:

Line 2:80: E501 line too long (83 > 79 characters)
Line 17:80: E501 line too long (82 > 79 characters)
Line 18:80: E501 line too long (82 > 79 characters)
Line 104:80: E501 line too long (82 > 79 characters)

In the file napari/layers/_labels_layer/view/properties.py:

Line 2:80: E501 line too long (87 > 79 characters)
Line 27:80: E501 line too long (83 > 79 characters)
Line 56:80: E501 line too long (80 > 79 characters)
Line 67:80: E501 line too long (80 > 79 characters)
Line 73:80: E501 line too long (83 > 79 characters)

In the file napari/layers/_markers_layer/model.py:

Line 366:80: E501 line too long (81 > 79 characters)
Line 410:80: E501 line too long (80 > 79 characters)

In the file napari/layers/_markers_layer/view/properties.py:

Line 42:80: E501 line too long (82 > 79 characters)
Line 49:80: E501 line too long (80 > 79 characters)
Line 56:80: E501 line too long (82 > 79 characters)
Line 63:80: E501 line too long (80 > 79 characters)
Line 69:80: E501 line too long (80 > 79 characters)
Line 82:80: E501 line too long (83 > 79 characters)
Line 116:80: E501 line too long (88 > 79 characters)

In the file napari/layers/_pyramid_layer/model.py:

Line 113:80: E501 line too long (81 > 79 characters)
Line 115:80: E501 line too long (88 > 79 characters)
Line 158:80: E501 line too long (86 > 79 characters)
Line 212:80: E501 line too long (82 > 79 characters)

In the file napari/layers/_shapes_layer/model.py:

Line 260:80: E501 line too long (80 > 79 characters)
Line 337:80: E501 line too long (86 > 79 characters)
Line 360:80: E501 line too long (80 > 79 characters)
Line 368:80: E501 line too long (80 > 79 characters)
Line 383:80: E501 line too long (85 > 79 characters)
Line 425:80: E501 line too long (86 > 79 characters)
Line 438:80: E501 line too long (84 > 79 characters)
Line 445:80: E501 line too long (87 > 79 characters)
Line 574:80: E501 line too long (88 > 79 characters)
Line 628:80: E501 line too long (81 > 79 characters)
Line 631:80: E501 line too long (87 > 79 characters)
Line 661:80: E501 line too long (86 > 79 characters)
Line 806:80: E501 line too long (82 > 79 characters)
Line 937:80: E501 line too long (87 > 79 characters)
Line 1006:80: E501 line too long (88 > 79 characters)
Line 1053:80: E501 line too long (87 > 79 characters)
Line 1082:80: E501 line too long (88 > 79 characters)
Line 1103:80: E501 line too long (84 > 79 characters)
Line 1114:80: E501 line too long (81 > 79 characters)
Line 1127:80: E501 line too long (86 > 79 characters)
Line 1141:80: E501 line too long (81 > 79 characters)
Line 1244:80: E501 line too long (83 > 79 characters)
Line 1311:80: E501 line too long (88 > 79 characters)
Line 1331:80: E501 line too long (84 > 79 characters)
Line 1335:80: E501 line too long (82 > 79 characters)
Line 1341:80: E501 line too long (81 > 79 characters)
Line 1464:80: E501 line too long (83 > 79 characters)
Line 1551:80: E501 line too long (83 > 79 characters)
Line 1556:80: E501 line too long (85 > 79 characters)

In the file napari/layers/_shapes_layer/shape_list.py:

Line 99:80: E501 line too long (80 > 79 characters)
Line 110:80: E501 line too long (87 > 79 characters)
Line 113:80: E501 line too long (81 > 79 characters)
Line 138:80: E501 line too long (87 > 79 characters)
Line 141:80: E501 line too long (81 > 79 characters)
Line 198:80: E501 line too long (87 > 79 characters)
Line 254:80: E501 line too long (87 > 79 characters)
Line 483:80: E501 line too long (80 > 79 characters)
Line 487:80: E501 line too long (80 > 79 characters)
Line 494:80: E501 line too long (88 > 79 characters)
Line 629:80: E501 line too long (85 > 79 characters)

In the file napari/layers/_shapes_layer/shape_util.py:

Line 329:80: E501 line too long (81 > 79 characters)
Line 330:80: E501 line too long (85 > 79 characters)
Line 502:80: E501 line too long (87 > 79 characters)
Line 584:80: E501 line too long (85 > 79 characters)
Line 624:24: E203 whitespace before ':'
Line 648:80: E501 line too long (83 > 79 characters)
Line 751:23: E203 whitespace before ':'
Line 751:43: E203 whitespace before ':'

In the file napari/layers/_shapes_layer/shapes/ellipse.py:

Line 100:80: E501 line too long (83 > 79 characters)

In the file napari/layers/_shapes_layer/shapes/rectangle.py:

Line 139:80: E501 line too long (80 > 79 characters)

In the file napari/layers/_shapes_layer/shapes/shape.py:

Line 253:80: E501 line too long (83 > 79 characters)

In the file napari/layers/_shapes_layer/view/controls.py:

Line 1:80: E501 line too long (87 > 79 characters)
Line 13:80: E501 line too long (86 > 79 characters)
Line 26:80: E501 line too long (82 > 79 characters)
Line 27:80: E501 line too long (82 > 79 characters)

In the file napari/layers/_shapes_layer/view/properties.py:

Line 28:80: E501 line too long (80 > 79 characters)
Line 38:80: E501 line too long (82 > 79 characters)
Line 46:80: E501 line too long (80 > 79 characters)
Line 53:80: E501 line too long (82 > 79 characters)
Line 61:80: E501 line too long (80 > 79 characters)

In the file napari/layers/_vectors_layer/model.py:

Line 44:80: E501 line too long (88 > 79 characters)
Line 193:80: E501 line too long (88 > 79 characters)
Line 197:80: E501 line too long (88 > 79 characters)
Line 201:80: E501 line too long (88 > 79 characters)
Line 205:80: E501 line too long (88 > 79 characters)
Line 290:25: E203 whitespace before ':'
Line 290:46: E203 whitespace before ':'
Line 290:60: E203 whitespace before ':'
Line 290:80: E501 line too long (84 > 79 characters)
Line 290:81: E203 whitespace before ':'
Line 340:80: E501 line too long (81 > 79 characters)
Line 468:80: E501 line too long (83 > 79 characters)

In the file napari/layers/_vectors_layer/view/properties.py:

Line 2:80: E501 line too long (83 > 79 characters)
Line 50:80: E501 line too long (85 > 79 characters)
Line 61:80: E501 line too long (80 > 79 characters)

In the file napari/util/colormaps/colormaps.py:

Line 8:80: E501 line too long (87 > 79 characters)
Line 15:80: E501 line too long (83 > 79 characters)
Line 197:80: E501 line too long (83 > 79 characters)

In the file napari/util/event.py:

Line 308:80: E501 line too long (86 > 79 characters)
Line 382:80: E501 line too long (85 > 79 characters)
Line 407:80: E501 line too long (80 > 79 characters)
Line 414:80: E501 line too long (83 > 79 characters)
Line 447:80: E501 line too long (84 > 79 characters)
Line 771:80: E501 line too long (86 > 79 characters)
Line 779:80: E501 line too long (81 > 79 characters)

In the file napari/util/list/_model.py:

Line 30:80: E501 line too long (84 > 79 characters)
Line 39:80: E501 line too long (87 > 79 characters)

In the file napari/util/list/_typed.py:

Line 45:80: E501 line too long (81 > 79 characters)

In the file napari/util/misc.py:

Line 13:80: E501 line too long (84 > 79 characters)

In the file setup.py:

Line 56:80: E501 line too long (84 > 79 characters)
Line 60:80: E501 line too long (84 > 79 characters)

In the file test_examples.py:

Line 21:38: E203 whitespace before ':'

In the file versioneer.py:

Line 391:80: E501 line too long (86 > 79 characters)
Line 1007:27: E203 whitespace before ':'
Line 1024:36: E203 whitespace before ':'
Line 1058:80: E501 line too long (87 > 79 characters)
Line 1110:80: E501 line too long (88 > 79 characters)
Line 1124:57: E203 whitespace before ':'
Line 1135:80: E501 line too long (84 > 79 characters)
Line 1198:57: E203 whitespace before ':'
Line 1242:80: E501 line too long (81 > 79 characters)
Line 1246:80: E501 line too long (87 > 79 characters)
Line 1256:80: E501 line too long (85 > 79 characters)
Line 1601:80: E501 line too long (88 > 79 characters)
Line 1764:80: E501 line too long (82 > 79 characters)


The node is not opt-in to EigenDA yet!

After upgrading to the latest version, I see the following message in my logs of operator!
The node has successfully started. Note it's not opt-in to EigenDA yet (it's not receiving or validating data in EigenDA). To register, please follow the EigenDA operator guide section in docs.eigenlayer.xyz caller=node.go:183

I ran ./run.sh opt-in before docker compose up -d and received successfully opt-in the EigenDA, for operator ID: ***!

I don't think so you are running the updated version v0.2.0 yet. this log message is for older version - https://github.com/Layr-Labs/eigenda/commit/ee891cad9a5a93e4206aa078e8eaf147db30fedf

I am running the latest version! My operator also returns signatures, but at the top of the logs file, I see the mentioned warning message!

Hmm this is strange. The logs is from old binary. Since you are validating blobs, you are good. but I will take a note and see what is going on.

 I am truly grateful for your support!
After I realized that the operator had been ejected from AVS (that was unexpected because everything was under control and the operator was returning signatures using v0.2.0) I restarted everything again. Now, I see the correct logs from the latest binary. (Commit: ee891ca...fedf)
The node has successfully started. Note: if it's not opted in on https://goerli.eigenlayer.xyz/avs/eigenda, then please follow the EigenDA operator guide section in docs.eigenlayer.xyz to register caller=logging.go:65
Anyway, IDK why my operator has been ejected despite returning the correct logs and hashes! I have pieces of evidence to prove that!

Thank you! I don't know what happened with logs. Maybe docker had some glitch. I don't see you anymore in our non-signer list so you are good - could be an oversight on our side. I am closing this issue for now. Feel free to create new one with any other issues.


ZFS Graph Driver incompatible with user namespace support

Description of problem:
I have been looking at moving to using ZFS as a storage backend and am preparing to deploy user id namespacing to my production servers. Naturally I decided to run an experiment on using these awesome features together. No :game_die:. In IRC @estesp suggested I reference him as he'd likely be the one to fix it. The only remotely related issue I could find was #12648.
docker version:
Client:
 Version:      1.10.0-dev
 API version:  1.23
 Go version:   go1.5.3
 Git commit:   69c381c
 Built:        Mon Feb  1 18:12:12 2016
 OS/Arch:      linux/amd64
 Experimental: true

Server:
 Version:      1.10.0-dev
 API version:  1.23
 Go version:   go1.5.3
 Git commit:   69c381c
 Built:        Mon Feb  1 18:12:12 2016
 OS/Arch:      linux/amd64
 Experimental: true

docker info:
root@localhost:/vagrant# docker version
Client:
 Version:      1.10.0-dev
 API version:  1.23
 Go version:   go1.5.3
 Git commit:   69c381c
 Built:        Mon Feb  1 18:12:12 2016
 OS/Arch:      linux/amd64
 Experimental: true

Server:
 Version:      1.10.0-dev
 API version:  1.23
 Go version:   go1.5.3
 Git commit:   69c381c
 Built:        Mon Feb  1 18:12:12 2016
 OS/Arch:      linux/amd64
 Experimental: true
root@localhost:/vagrant# docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.10.0-dev
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: zfs
 Dirs: 2
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 3.16.0-30-generic
Operating System: Ubuntu 14.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.955 GiB
Name: localhost
ID: MCCO:LDLI:4CKJ:5CS5:KOW4:HBTZ:IJFE:YO3N:YQ4J:ZDFM:4YW4:L6AV
WARNING: No swap limit support
Experimental: true

uname -a
Linux localhost 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Environment details
Ubuntu 14.04 Virtualbox environment with one additional disk created.
Steps to reproduce:
To reproduce, I used vagrant to create a brand new environment on ubuntu 14.04. Then I ran the following:

# Install and configure ZFS as per https://docs.docker.com/engine/userguide/storagedriver/zfs-driver/
sudo -i
apt-get update
apt-get upgrade -y
apt-get install -y software-properties-common
add-apt-repository ppa:zfs-native/stable
apt-get update
apt-get install -y ubuntu-zfs
modprobe zfs
lsmod | grep zfs # This just validates zfs is up and running, of course.
zpool create -f zpool-docker /dev/sdb # Obviously YMMV depending on how you're attaching the disk
zfs list # Verify it exists
zfs create -o mountpoint=/var/lib/docker zpool-docker/docker
sudo zfs list -t all # Verify we see our volume and mount point

Install docker experimental as per https://github.com/docker/docker/tree/master/experimental
Unfortunately the documented approach didn't work for me (curl -sSL https://experimental.docker.com/ | sh), it seems the key server no longer can find this key.
Instead I ran:
echo 'deb [arch=amd64] https://apt.dockerproject.org/repo ubuntu-trusty experimental' > /etc/apt/sources.list.d/docker.list
curl https://apt.dockerproject.org/gpg > /tmp/docker.key
apt-key add /tmp/docker.key
apt-get update
apt-get install docker-engine -y
docker version
docker info
docker run hello-world

Here the documentation indicates that the zfs graph driver should be automagically selected, no dice - it knows we're backed by ZFS but picks aufs anyways.
root@localhost:~# sudo docker info
Containers: 1
Images: 2
Server Version: 1.9.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: zfs
 Dirs: 4
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.16.0-30-generic
Operating System: Ubuntu 14.04.2 LTS
CPUs: 1
Total Memory: 1.955 GiB
Name: localhost
ID: TZTE:CQEN:R5AL:HBLS:5KPC:L6CI:SDHV:NNLW:L6U7:PA6Y:YLSM:E57A
WARNING: No swap limit support

So, I add this to `/etc/default/docker:
DOCKER_OPTS="--storage-driver=zfs"

and I restart docker with service docker restart.
Now we've got a functional ZFS backend.
root@localhost:~# docker info
Containers: 0
Images: 0
Server Version: 1.9.1
Storage Driver: zfs
 Zpool: zpool-docker
 Zpool Health: ONLINE
 Parent Dataset: zpool-docker/docker
 Space Used By Parent: 160768
 Space Available:<PHONE_NUMBER>
 Parent Quota: no
 Compression: off
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.16.0-30-generic
Operating System: Ubuntu 14.04.2 LTS
CPUs: 1
Total Memory: 1.955 GiB
Name: localhost
ID: TZTE:CQEN:R5AL:HBLS:5KPC:L6CI:SDHV:NNLW:L6U7:PA6Y:YLSM:E57A
WARNING: No swap limit support

Now we're functional and I can pull and run docker images:
root@localhost:~# sudo docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
b901d36b6f2f: Pull complete
0a6ba66e537a: Pull complete
Digest: sha256:8be990ef2aeb16dbcb9271ddfe2610fa6658d13f6dfb8bc72074cc1ca36966a7
Status: Downloaded newer image for hello-world:latest

Hello from Docker.
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker Hub account:
 https://hub.docker.com

For more examples and ideas, visit:
 https://docs.docker.com/userguide/

Now, I edit /etc/default/docker again and and update DOCKER_OPTS to be:
DOCKER_OPTS="--storage-driver=zfs --userns-remap=default"

Now I restart docker service docker restart.
Now trying to run anything in docker results in:
root@localhost:~# docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 1.10.0-dev
Storage Driver: zfs
 Zpool: zpool-docker
 Zpool Health: ONLINE
 Parent Dataset: zpool-docker/docker
 Space Used By Parent: 98816
 Space Available:<PHONE_NUMBER>
 Parent Quota: no
 Compression: off
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 3.16.0-30-generic
Operating System: Ubuntu 14.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.955 GiB
Name: localhost
ID: TZTE:CQEN:R5AL:HBLS:5KPC:L6CI:SDHV:NNLW:L6U7:PA6Y:YLSM:E57A
WARNING: No swap limit support
Experimental: true

root@localhost:~# sudo docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
03f4658f8b78: Pull complete
a3ed95caeb02: Pull complete
Digest: sha256:8be990ef2aeb16dbcb9271ddfe2610fa6658d13f6dfb8bc72074cc1ca36966a7
Status: Downloaded newer image for hello-world:latest
Timestamp: 2016-02-02 15:33:24.916003924 -0800 PST
Code: System error

Message: can't create pivot_root dir , error mkdir /var/lib/docker/165536.165536/zfs/graph/08111af5be598b934a672bdd26f544d43909bb68c1f2916f8138a706715ebbef/.pivot_root492998315: permission denied

Frames:
---
0: setupRootfs
Package: github.com/opencontainers/runc/libcontainer
File: rootfs_linux.go@69
---
1: Init
Package: github.com/opencontainers/runc/libcontainer.(*linuxStandardInit)
File: standard_init_linux.go@57
---
2: StartInitialization
Package: github.com/opencontainers/runc/libcontainer.(*LinuxFactory)
File: factory_linux.go@240
---
3: initializer
Package: github.com/docker/docker/daemon/execdriver/native
File: init.go@35
---
4: Init
Package: github.com/docker/docker/pkg/reexec
File: reexec.go@26
---
5: main
Package: main
File: docker.go@18
---
6: main
Package: runtime
File: proc.go@111
---
7: goexit
Package: runtime
File: asm_amd64.s@1721
docker: Error response from daemon: Container command could not be invoked.

If I edit /etc/defaults/docker and set opts back to DOCKER_OPTS="--storage-driver=zfs" and re-run the hello-world image I get:
root@localhost:/etc/default# docker run hello-world

Hello from Docker.
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker Hub account:
 https://hub.docker.com

For more examples and ideas, visit:
 https://docs.docker.com/userguide/

Thanks for the bug report. The bug is fairly straightforward--even though the mapping of file ownership based on the user namespace map is happening when the layers are pulled from a registry, the root directory that they are placed in still has root:root ownership.  In other storage drivers this directory would be created with the remapped root ownership, but in ZFS, this (I believe) is created via calls to ZFS, and I'm trying to figure out how to fix it properly. If I use mount on a simple single-layer image by pulling it (e.g. docker pull alpine), finding it's zpool name, and mounting it manually, I can change the ownership of that root directory, and then that particular image works fine:
root@dev1404:/# zfs list -t all
NAME                                                                                USED  AVAIL  REFER  MOUNTPOINT
zpool-docker                                                                          5.37M   443M    19K  /zpool-docker
zpool-docker/docker                                                                   5.23M   443M   196K  /var/lib/docker.zfs
zpool-docker/docker/e859e33a39acd29d232f5e4ff1c7534e1204967f27b4c99031450fd3633f1240  5.04M   443M  5.04M  legacy
root@dev1404:/# mkdir /tmp/alpine
root@dev1404:/# mount -t zfs zpool-docker/docker/e859e33a39acd29d232f5e4ff1c7534e1204967f27b4c99031450fd3633f1240 /tmp/alpine/
root@dev1404:/# cd /tmp/alpine/
root@dev1404:/tmp/alpine# ls -al
total 35
drwxr-xr-x 17 root   root      18 Feb  5 13:22 .
drwxrwxrwt  8 root   root   16384 Feb  5 13:52 ..
drwxr-xr-x  2<PHONE_NUMBER>72    81 Jan 16 21:35 bin
drwxr-xr-x  4<PHONE_NUMBER>72     4 Jan 16 21:35 dev
...
root@dev1404:/tmp/alpine# chown 231072:231072 .
root@dev1404:/tmp/alpine# ls -al
total 35
drwxr-xr-x 17<PHONE_NUMBER>72    18 Feb  5 13:22 .
drwxrwxrwt  8 root   root   16384 Feb  5 13:52 ..
drwxr-xr-x  2<PHONE_NUMBER>72    81 Jan 16 21:35 bin
drwxr-xr-x  4<PHONE_NUMBER>72     4 Jan 16 21:35 dev
...
root@dev1404:/tmp/alpine# cd
root@dev1404:~# umount /tmp/alpine

Now that I've fixed the root dir to be owned with the remapped root uid:gid, I can run the alpine image  without error:
estesp@dev1404:~$ docker run -ti --rm alpine /bin/sh
/ # ls -al
total 20
drwxr-xr-x   17 root     root            20 Feb  5 18:52 .
drwxr-xr-x   17 root     root            20 Feb  5 18:52 ..
-rwxr-xr-x    1 root     root             0 Feb  5 18:52 .dockerenv
-rwxr-xr-x    1 root     root             0 Feb  5 18:52 .dockerinit
drwxr-xr-x    2 root     root            81 Jan 17 02:35 bin
drwxr-xr-x    5 root     root           380 Feb  5 18:52 dev
...

Seems like the fix can be done in the ZFS storage driver, but still digging..

I've figured out a way to fix it, although I wish there was a way to set the root dir ownership up at file creation time..


CSP --> BQM not returning valid transformation

The following map coloring does not work
HALF CANADA 4 COLORS
import dwavebinarycsp
from dwave.system.samplers import DWaveSampler
from dwave.system.composites import EmbeddingComposite
import operator
provinces = ['AB', 'BC', 'NT', 'SK', 'YT']
neighbors = [('AB', 'BC'), ('AB', 'NT'), ('AB', 'SK'), ('BC', 'NT'), ('BC', 'YT'), ('NT', 'SK'), ('NT', 'YT')]
one_color_configurations = {(0, 0, 0, 1), (0, 0, 1, 0), (0, 1, 0, 0), (1, 0, 0, 0)}
csp = dwavebinarycsp.ConstraintSatisfactionProblem(dwavebinarycsp.BINARY)
for province in provinces:
vars = [province+'0', province+'1', province+'2', province+'3']
csp.add_constraint(one_color_configurations, vars)
for neighbor in neighbors:
v, u = neighbor
for i in range(4):
var = [v+str(i), u+str(i)]
csp.add_constraint(operator.ne, var)
bqm = dwavebinarycsp.stitch(csp)
sampler = EmbeddingComposite(DWaveSampler())
response = sampler.sample(bqm, chain_strength=3, num_reads=1000)

An issue of problem construction.
for neighbor in neighbors:
    for i in range(4):
        var = [v+str(i), u+str(i)]
        csp.add_constraint([(0, 0), (0, 1), (1, 0)], var)


Clear is not working

The "Clear TwinColGrid" button is not working in the demo. Taking a look to the code, nothing special is being done, so probably the clear() method is broken.

I'm closing this issue because the feature works as expected in the demo.


Introduce an imports.jl file

Instead of overloading functions with syntax like LinearAlgebra.tr, it may be nice to use import LinearAlgebra: tr and then put all of the imports in a single imports.jl file (analogous to the exports.jl file).

This has been implemented by #511.


not showing all docker containers

Rancher Version:
1.2.0
Docker Version:
1.11.2
OS and where are the hosts located? (cloud, bare metal, etc):
CoreOS
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Just Rancher with mysql backend
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Clean installation, deleted the /var/lib/rancher and /var/lib/docker
Results:
Not showing all containers
Expected:
Showing all containers
I install the agent on the same server as Rancher and used the public 'internet' IP. With docker-compose I install some extra service, the containers are starting, but they are not visible in Rancher.

Same problem here... was ok before Rancher 1.2

I think we are the only one which have that, since the rest is not responding ;-). I will try v1.2.0-rc1 tonight to see if this will be changed. It would be great if it's working so I can see my stacks and attach haproxy on this from the Rancher interface. So other readers, please help us !!

Still the same with the 1.2.0-rc1 candidate. I notice that their are also r_ containers. Is there an easy way to detect the containers between Rancher and Docker, or to delete the cache?

+1

Same problem here! Docker Images started via compose are not detected by rancher at all.

Downgraded to previous version... and now it's ok!

I tested with master and found agent is doing reporting the status for those containers. Wondering if it is a bug in cattle somewhere else.

Is it possible to try this with an old agent and see if there is a difference? It's mostly with containers which are created with docker-compose.

@dcnl1980 happy to try downgrading agent, would it be possible to downgrade agent without downgrading rancher?
I did see a flicker of a container in the ui and then it went away again.

+1
Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) x86_64 GNU/Linux
Docker version 1.13.1, build 092cba3 - also not working on previous docker version ~1.13.0
Containers started with two docker-compose files..
CATTLE_RANCHER_SERVER_VERSION=v1.4.0
CATTLE_CATTLE_VERSION=v0.176.8
CATTLE_RANCHER_COMPOSE_VERSION=v0.12.2
....

@MartinBucko @tbohnen @dcnl1980 @juocal @fprieur are you all on rancher 1.2.X or have any of you seen this in 1.3/1.4
Also, if you could post a full docker-compose/rancher-compose for a service that is falling victim to this bug or otherwise give more detailed steps to reproduce, that would be helpful.

@sangeethah The fix is in master now.

Tested with rancher server build from master.
Created containers using  docker-compose up command with the following docker-compose.yml
version: '2'
services:
  web:
    image: nginx
    depends_on:
      - db
      - redis
  redis:
    image: redis
  db:
    image: postgres

nginx/redis/postgres containers from this host get synced to rancher-server as standalone containers on this host.
Changes made to these containers from host (stop/start/delete) are reflected correctly on the rancher-server.
Changes made to these containers from rancher-server UI (stop/start/delete) are reflected correctly on the host.

@sangeethah
Verified with rancher/agent:v1.5.0-rc4 and rancher/agent:v1.2.1
Works now! Thanks!


As an admin user, I want to be able to delete, pause, rotate and deprecate API keys and applications.

This refers to admin users of PORTERS, i.e. users who have created an account on PORTERS and fully control this account within the bounds of being a "user" of PORTERS.

create, delete, and rotate is done. App deletion is still needed. Probably done tomorrow.


Added update kwarg to open() and openEx().

The FTD2XX class has update kwarg that should be available when using the open() and openEx() functions.

Thanks @krister-ts . Looks good. May be add documentation in the docstring about the new update parameter?

Thanks @krister-ts . Looks good. May be add documentation in the docstring about the new update parameter?

Sorry I didn't get to this for quite some time. Today is a holiday, so I had a couple minutes to add in something to those docstrings.


Wordle Game

Wordle Game using HTML, CSS, JavaScript
About in brief
I want to make a Wordle game using HTML, CSS and JAVASCRIPT  in which you have to guess the word as per the hints hai guidance
Happy Hacking

Please Assign this to me


Settings screen is blank on 0.65

Microsoft PowerToys version
0.65.0
Installation method
WinGet
Running as admin
Yes
Area(s) with issue?
Welcome / PowerToys Tour window
Steps to reproduce

as the picture, open the app and you can see  the problem.
✔ Expected Behavior
there should be words or characters in the window
❌ Actual Behavior
there is no words in the app, but the button in the window can be interacted
Other Software
No response

/reportbug

PowerToysReport_2022-12-29-09-08-58.zip

I have submitted the zip file

Thanks!

@Pyramind-RJ Can you try installing WinUI 3 Gallery from MS Store app and check if it works correctly. Checking if this is PowerToys or framework related issue..
/needinfo

Also, are you using some of the listed apps: H24, MSI Afterburner, RivaTuner Statistics Server or HW64 ?

Also, are you using some of the listed apps: H24, MSI Afterburner, RivaTuner Statistics Server or HW64 ?
i don't have

@Pyramind-RJ Can you try installing WinUI 3 Gallery from MS Store app and check if it works correctly. Checking if this is PowerToys or framework related issue..
/needinfo

it doesn't works too.

Something is shimming into WinUI apps it looks like
do you use an app called trustview?
do you have a nVidia card?

/needinfo

Something is shimming into WinUI apps it looks like
do you use an app called trustview? do you have a nVidia card?

i don't have trustview or nVidia card

@Pyramind-RJ Is this issue still present with the latest PowerToys v0.67?

i'm trying to update it

The problem is still there

The problem is still remain.

@Pyramind-RJ there is an app that could be injecting something in. I think we’ll need a dump of the settings app shared to move forward. I’ll send instructions on Monday.

/dup https://github.com/microsoft/PowerToys/issues/29340


How to convert tgnet to newSession via QrCode  ?

Can you add function for converting tgnet to tdata via QrCode how new Session ?

This is not really related to conversion between session formats but more related to creating online session from QR code
You can definetely use other resources to create a web session from QR code and after that you can extract auth key, user id and dc id and use them to create a mobile session with AndroidTelePorter.
But the exact feature you are asking for will not be implemented


test coverage for fix service call

It has a minimal internal function test in analysis_server_test.dart
I agree that it should have a test being driven via common_server as well.


[Fix #11697] Fix Lint/Syntax behavior when using --only option

Fixes #11697.
This PR fixes Lint/Syntax behavior when --only is not given the cop name. The cop must always be executed.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Thanks!


Commit 386382b18caab6a3a8a111fa8e24875dca27b0aa is kicking my ass on Python 3

Hi,
Today our automated builds started failing because 2.11.0 was pulled and 386382b18caab6a3a8a111fa8e24875dca27b0aa causes a request's body to be a bytes object in Python 3 but a str in Python 2.7, which is breaking both my code and https://github.com/seanbrant/requests-wsgi-adapter:
https://gist.github.com/alexntt/b181b562852c6850a83269b7401d3bef
Can this be made a bit more "backwards-compatible"?
Cheers,
Álex

Bytes and str are the same type. In fact, bytes aliases to str on Python 2.6. For that reason, it would seem like the code to work around this problem is simple: if not isinstance(bytes, request.body): request.body.encode('utf-8')
Indeed, I'd like to point out that this has worked around a bug in requests-wsgi-adapter: specifically, if provided a unicode string containing code points outside U+0000 to U+007F then the content-length would have been incorrect. Because we're now providing bytes to you, this error cannot occur. This change was introduced for exactly this reason.

I've patched the library I depend on and our project so this is no longer an issue, thank you


Add Option::value synonym for get_Some_0

I've now gotten a bit more experience with both the rust-y and Dafny styles of using Option in spec contexts, and I've found good evidence that the Dafny approach of test-and-dereference is more readable.
Consider these two examples in match style:
       &&& match *self.prior_rec {
            Some(rec) => {
                &&& rec.wf()
                &&& rec.message_seq.can_concat(self.message_seq)
            }
            None => true
       }

            ||| match *self.prior_rec { Some(rec) => rec.valid(boundary_lsn), _ => false }

Compare them to the more direct translation from the test-and-reference style:
        &&& self.prior_rec.is_Some() ==> {
            &&& self.prior_rec.value().wf()
            &&& self.prior_rec.value().message_seq.can_concat(self.message_seq)
            }

            ||| self.prior_rec.is_Some() && self.prior_rec.value().valid(boundary_lsn)

Now it's easy to see that the first example was an implication and the second was a conjunct. In the match style, that boolean relationship is encoded in the default arm of the match, making it much more subtle.
We can write this today with get_Some_0(), but heavens is that cumbersome to read. To claw back a little parsimony, this PR proposes adding a value() synonym to pervasive Option to improve readability of the test-and-dereference style.

We've had discussions about general syntax for these cases, which I think we should still pursue, but I'm not against adding something like .value() for the time being.
I think we can name this spec_unwrap (for the reasons @jaybosamiya mentioned), and make it auto-spec to spec_unwrap, like for Vec::Len https://github.com/verus-lang/verus/blob/main/source/pervasive/vec.rs#L103-L110
That way you get to unwrap in both spec and exec code. It should probably also be #[verifier(inline)].

Oh I somehow completely missed the #[verifier(when_used_as_spec(...)]; that actually already makes things a lot cleaner than I had initially thought. This isn't exposed in the docs example but probably should. Opened a discussion about it: https://github.com/verus-lang/verus/discussions/434

@utaal: adding something like .value() for the time being. ... I think we can name this spec_unwrap
Should I take this as "also approved"?

Yes, but please first rename to spec_unwrap, add when_used_as_spec to unwrap, and add #[verifier(inline)]. Let me know if I can help with those, or if something's unclear.


User Authentication: Request Authorization

Resolves #14
Changes

Added authorization token to API requests made by fetchRequest() in the frontend
Modified firebase-admin set up in backend/src/firebase-admin.ts
Implemented validateUser() in backend/src/middleware/validation.ts. This is the middleware that checks to see if a user making the API request is authenticated.
Implemented validateHousingLocator() in backend/src/middleware/validation.ts. This is the middleware that checks to see if a user making the API request is a housing locator.

Testing

validateUser(): I logged in with my Google account and was able to reach the end of the validator. At the end of the validator, I logged the user info to console.
validateHousingLocator(): I added this to the validateWith variable at the end of validation.ts and got a frontend response when trying to log in with my Google account that I wasn't a Housing Locator, I would get an error response in the frontend.  When I manually change the isHousingLocator field through compass, I would not get the same error as before.

Confirmation of Change

See "Testing" to see see how I tested the changes.

When resolving merge requests with the main branch, I chose the options that were on the main branch. With the exception of firebase-admin.ts in the backend.

At the top of backend/src/middleware/validation.ts, I attempted to resolve the no-unsafe-member-access error with an explicit type, but I ran into issues when working with the typings of the asyncHandler from the wrapper file.

At the top of backend/src/middleware/validation.ts, I attempted to resolve the no-unsafe-member-access error with an explicit type, but I ran into issues when working with the typings of the asyncHandler from the wrapper file.

Yeah, this is a little tricky. You should be able to resolve that by adding a type declaration file to extend the existing Express Request type. Follow the first answer from here: https://stackoverflow.com/questions/65848442/property-user-does-not-exist-on-type-requestparamsdictionary-any-any-pars
Putting something like this in the index.d.ts file should work:
import { User } from "@/models/user";

declare global {
  namespace Express {
    interface Request {
      currentUser: User;
    }
  }
}

You might get a warning about using a type instead of an interface, but you can ignore this.


made the nav bar

Description
Please include a summary of the changes and the related issue. Include relevant motivation and context.
Fixes #147
Type of change
Please delete options that are not relevant.

[ ] New feature (non-breaking change)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so that they can be reproduced.

[ ] Test A
[ ] Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules

Please merge it under the hacktoberfest label


Building Haystac Database

Hey there,
so got to run Haystac via installing it with pip in a virtual python environment and also in a conda environment. In both environments I tried to create databases as depicted in the manual but It doesn't seem to work. So maybe you can help me and provide a solution.
When I use Conda I get the following error:
Updating job index_all_accessions.
Updating job entrez_db_list.
Updating job randomise_db_order.
[Thu Jun 17 12:31:09 2021]
Error in rule entrez_pick_sequences:
    jobid: 1
    output: /data110/misterx/software2/klebsiella/entrez/entrez-selected-seqs.tsv

Traceback (most recent call last):
  File "/data110/misterx/software2/test/lib/python3.6/site-packages/snakemake/executors/__init__.py", line 575, in _callback
    callback(job)
  File "/data110/misterx/software2/test/lib/python3.6/site-packages/snakemake/scheduler.py", line 544, in _proceed
    job, update_dynamic=update_dynamic
  File "/data110/misterx/software2/test/lib/python3.6/site-packages/snakemake/dag.py", line 1348, in finish
    updated_dag = self.update_checkpoint_dependencies(jobs)
  File "/data110/misterx/software2/test/lib/python3.6/site-packages/snakemake/dag.py", line 1312, in update_checkpoint_dependencies
    self.postprocess()
  File "/data110/misterx/software2/test/lib/python3.6/site-packages/snakemake/dag.py", line 1193, in postprocess
    self.cleanup()
  File "/data110/misterx/software2/test/lib/python3.6/site-packages/snakemake/dag.py", line 258, in cleanup
    del self.depending[dep][job]
KeyError: entrez_taxa_query
Removing output files of failed job entrez_pick_sequences since they might be corrupted:
/data110/misterx/software2/klebsiella/entrez/entrez-selected-seqs.tsv
Trying to restart job 1.

[Thu Jun 17 12:31:09 2021]
Job 1: Selecting the longest sequence per taxon in the entrez query.
Downstream jobs will be updated after completion.

[Thu Jun 17 12:31:11 2021]
Finished job 1.
3 of 5 steps (60%) done
Complete log: /data110/misterx/software2/.snakemake/log/2021-06-17T123038.153429.snakemake.log

This run I did with the following command but I also tried with the Y.pestis one from the manual and it throws the same error.
haystac database --mode build --query '"Klebsiella pneumoniae"[Organism] AND "complete genome"[All Fields] AND refseq[filter]' --output /data110/jsusat_side_projects/software2/klebsiella
And If I try to build a database in the python3 virtual environment where I installed Haystac with pip the error message looks like this:
`/bin/bash: bgzip: command not found
/bin/bash: bgzip: command not found
/bin/bash: bgzip: command not found
/bin/bash: bgzip: command not found
/bin/bash: bgzip: command not found
/bin/bash: bgzip: command not found
/bin/bash: bgzip: command not found
/bin/bash: bgzip: command not found
haystac: error: Unable to download assembly ftp://ftp.ncbi.nlm.nih.gov/genomes/all/GCF/003/798/225/GCF_003798225.1_ASM379822v1/GCF_003798225.1_ASM379822v1_genomic.fna.gz
None
/bin/bash: bgzip: command not found
/bin/bash: bgzip: command not found
haystac: error: Unable to download assembly ftp://ftp.ncbi.nlm.nih.gov/genomes/all/GCF/005/937/895/GCF_005937895.2_ASM593789v2/GCF_005937895.2_ASM593789v2_genomic.fna.gz
None
/bin/bash: bgzip: command not found
/bin/bash: bgzip: command not found
haystac: error: Unable to download assembly ftp://ftp.ncbi.nlm.nih.gov/genomes/all/GCF/000/834/455/GCF_000834455.1_ASM83445v1/GCF_000834455.1_ASM83445v1_genomic.fna.gz
None
[Thu Jun 17 13:11:45 2021]
Error in rule entrez_download_sequence:
    jobid: 22
    output: /data110/misterx/software2/virtual_env_haystack_cache/ncbi/Yersinia_rohdei/NZ_CP009787.1.fasta.gz

RuleException:
CalledProcessError in line 66 of /data110/misterx/software2/python3_haystac_virtualenv/lib/python3.7/site-packages/haystac/workflow/rules/entrez.smk:
Command 'set -euo pipefail;  /data110/misterx/software2/python3_haystac_virtualenv/bin/python3 /data110/misterx/software2/.snakemake/scripts/tmpif9vq4lr.entrez_download_sequence.py' returned non-zero exit status 1.
  File "/data110/misterx/software2/python3_haystac_virtualenv/lib/python3.7/site-packages/snakemake/executors/__init__.py", line 2352, in run_wrapper
  File "/data110/misterx/software2/python3_haystac_virtualenv/lib/python3.7/site-packages/haystac/workflow/rules/entrez.smk", line 66, in __rule_entrez_download_sequence
  File "/data110/misterx/software2/python3_haystac_virtualenv/lib/python3.7/site-packages/snakemake/executors/__init__.py", line 569, in _callback
  File "/opt/sw/python/3.7.4/lib/python3.7/concurrent/futures/thread.py", line 57, in run
  File "/data110/misterx/software2/python3_haystac_virtualenv/lib/python3.7/site-packages/snakemake/executors/__init__.py", line 555, in cached_or_run
  File "/data110/misterx/software2/python3_haystac_virtualenv/lib/python3.7/site-packages/snakemake/executors/__init__.py", line 2364, in run_wrapper
Removing output files of failed job entrez_download_sequence since they might be corrupted:
/data110/misterx/software2/virtual_env_haystack_cache/ncbi/Yersinia_rohdei/NZ_CP009787.1.fasta.gz
Trying to restart job 22.

[Thu Jun 17 13:11:45 2021]
Job 22: Downloading accession NZ_CP009787.1 for taxon Yersinia_rohdei.

[Thu Jun 17 13:11:45 2021]
Error in rule entrez_download_sequence:
    jobid: 20
    output: /data110/misterx/software2/virtual_env_haystack_cache/ncbi/Yersinia_pestis/NZ_CP033699.1.fasta.gz
`

I see the bgzip error which is also pretty odd as I installed bgzip in the virtualenv. But is the other problem where it states that it is unable to download the assembly linked to that? Or is it there for another reason? This error was generated with the following command:
haystac database --mode build --query '"Yersinia"[Organism] AND "complete genome"[All Fields]' --output yersinia_example
Maybe you can help me and provide some guidance :)
Thanks in advance,
Julian

Hello Julian,
I hope you are doing great !
Your first error was caused by the fact that we were not pinning the correct version of snakemake in our conda recipe. Not sure about the following ones though.
Would it possible for you to follow the updated instructions from our documentation and install the latest version of haystac from github (after cloning please install the package with pip), and let me know if you still face the same issues ? Of course I'll keep looking into the error messages you got in the meantime.
Apologies for this inconvenience and thank you for your patience !
Best,
Antony

Hey there and thanks for the answer, unfortunately I still cant get haystac to run. Neither with the updated instructions that I found here (https://github.com/antonisdim/haystac/blob/master/docs/installation.rst) nor with with pip and a python3 virtual environment again. But maybe I am doing something generally wrong. Do you also have an updated document on how to install with pip?
Cheers and all the best,
Julian

Hello Julian,
I hope you are doing great and I am really sorry for the delayed response !
I have uploaded an executable on my personal conda channel. Could you please install haystac in a fresh conda environment with the following command:
mamba install -c antonisdim haystac
Please make sure you are also using the latest version of conda.
Please let me know how it goes and thank you for your patience !
Best,
Antony


Allow inspection of PackingPlan

Developers should be able to do a dry run, or something similar to inspect the output of the packing plan with a given packing strategy via stdout before deploying the topology.

:+1: This does make sense

internal people said it would be good to have this feature. cc @kramasamy

We might need to extend this a bit - for example, with multiple packing algorithms, the resource consumption might differ. it might be good to list the resources required for each packing algorithm as well?

I would suggest that the user could configure a different packing algorithm
to see it's output, or pass a non-default packing class as another optional
arg.
On Thu, Aug 4, 2016 at 12:03 PM, Karthik Ramasamy<EMAIL_ADDRESS>wrote:

We might need to extend this a bit - for example, with multiple packing
algorithms, the resource consumption might differ. it might be good to list
the resources required for each packing algorithm as well?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/twitter/heron/issues/948#issuecomment-237651288, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AABczttzSzfATrqfT6_Mrad_F-585nUgks5qcjd5gaJpZM4I4sE0
.


Routing: Finding route block events loop

Finding the route blocks the event loop, this expensive compute needs to be offloaded elsewhere in such a way that subsequent requests can be processed.

Fixed in https://github.com/MBradbury/iot-trust-task-alloc/commit/05e4c6b6f514d7028a6bac398dbff8e56c25c702


component values!

Thanks for sharing your rather impressive body of work so far, I was looking at using your switch layout in a module, but i noticed theres no values for the components. could you add the values to the kicad files, or upload a bom so I can do it myself?
Keen to see what else you have in store so please keep updating
Cheers

Will do but it takes time ^^


"Run Task" does not load tsconfig from subfolder the first time

VSCode Version: Code - Insiders 1.15.0-insider (f39385b8326671dc6389f21f8c2e2f6afdb352a1, 2017-08-01T05:10:12.703Z)
OS Version: Linux x64 4.4.0-59-generic
Extensions: none

Testing #31232
Steps to Reproduce:

Open new window and add folder containing one subfolder
Run Task: only one tsconfig appears when there should be two

Run Task a second time: both tsconfigs appear

This is also true for Run Build Task

Thanks. I believe this is a duplicate of #31820
Should be fixed in master


mcrypt deprecated in PHP7.0 & mcrypt_encrypt throws warning PHP5.6

mcrypt deprecated in PHP7.0 - Used in Cana/Crypt.php
Also, mcrypt_encrypt() throws the warning 'Key of size 5 not supported by this algorithm. Only keys of size 24 supported' with >=PHP5.6 (only checked PHP5.6 and PHP7.0)
EDIT - mcrypt_encrypt error thrown by settings in include/config/config.xml

indeed it is deprecated natively. however the phpseclib/mcrypt_compat that should be installed by composer should fix this.
as for the key size, just make sure the key length matches the 24 length requirement.