set $select, $orderby and #expand as comma-separated values

See related issue #21.

@Behnam-Emamian I approved the changes. But, maybe we should update some test cases. Don't worry, i will update them if have.


Mobile menu

In this branch

added JS file
updated CSS
updated HTML
added JavaScript linter

removed Microverse logo from README file
removed unnecessary comments from HTML and CSS file

Used the correct background color
Used the correct font weight on the links and the cancel button
Added the missing blur effect on the background
Added the functionality when a user clicks on any link, it takes them to part of a section of the portfolio


Add null check to olLayer before checking its name (setVectorLayerEvents)

I came upon a case where I could get a TypeError error while checking against the layer name of the olLayer if the object was null (rapidly updating system).
The current code could allow an openlayers.layers event to be dispatched when the feature was not part of the layer (since null will pass angular.isDefined() with a true value).  I updated the return value to undefined to prevent the event from being fired (please disregard this pull request if the current behavior is intentional).

@trojandj Merged and released v0.0.9. Thx again :+1:


Fix refresher specs

Looks good. This challenge is a poor imitation of the ruby koans. Check those out when you get a chance too. Its a great resource though ive only finished about 60-70% of them myself.
http://rubykoans.com/


New Tab Redirect affects behavior of Bookmark Bar visibility

Summary
With NTR extension disabled, opening a new tab always results in the Bookmark Bar becoming visible on the new page, regardless of whether it had been visble or hidden on the originating page. (TTBOMR, this has been native Linux-Chromium behavior for several years.)
With NTR enabled, opening a new tab seems to just duplicate the state of the Bookmark Bar from the originating page: If the Bookmark Bar was visble on the originating page, then it is also visible on the new page that appears when NTR is invoked. If the Bookmark Bar was hidden on the originating page, then it remains hidden on the newly opened tab page.
Steps to reproduce
With NTR enabled:

Open arbitrary URL
If Bookmark Bar is visible, type ctrl-shft-B to hide it.
Type ctrl-T to invoke NTR and bring up new tab page
Observe new tab page does not show Bookmark Bar.

With NTR disabled, steps are the same as above, except observation (4) is that the Bookmark Bar is always shown.
Comments
The native behavior fits well with my typical workflow, because  with high probability, opening a new tab is almost always followed by opening a bookmark from the Bookmark Bar. Although ctrl-shft-B can be used to force the Bookmark Bar to appear, it's extra keystrokes that I'd prefer to avoid.
I did research this for an hour or so before reporting it here, looking thru the github issues and googling at large  but was surprised not to find any similar reports This usually means that the problem is on my end, perhaps some pecularity in my setup, or an error or misunderstanding on my part in the Chromium version/options, or NTR options, or how they may interact.
So the first question is simply: Can anyone reproduce this?
Second: If it is reproducible and acknowledged to be a behavior change due to NTR, can an option possibly be implemented to allow choosing between native and "clone Bookmark Bar" behavior?
Thanks!
Version info

O/S: Arch Linux, x86_64
Ungoogled Chromium, 84.0.4147.105, from Arch Linux repo.
New Tab Redrect V3.1.5, installed from CRX file downloaded from WebStore.
NTR options and permissions page screenshots attached. (NOTE: Toggling
the "management" permission to "approve" has no effect on the issue.)

@ahmogit the bookmark bar you're seeing when NTR is disable is a bookmark bar built into the default new tab page and not the "real" bookmarks bar. This isn't an issue with NTR. It is expected behavior in Chrome that the bookmark bar stays hidden when you open a new tab while hidden, and stays visible when you open a new tab while visible.

Hi Jim, thanks for your response. But I'm not sure I understand it. Can you explain a little further?
Here's what I don't get:
You say that there is a bookmark bar that is "built in" to the default new-tab page, and you talk about it as though it is distinct from the "real" bookmark bar.  But when NTR is disabled, the bookmark bar that appears when a new tab is opened is identical in all visible respects to the current state of the "real" bookmark bar (i.e. as customized and maintained by me via the Bookmark Manager). So I don't understand why you're referring to that as "built in". That phrase usuallly means something  roughly synonymous with "default" or "standard". But what actually appears is not some sort of default or standarized bookmark bar; it is identical to the current state of my "bookmark bar" folder as displayed in the Bookmark Manager.
I just checked this again now, to be sure I'm not mis-reporting the default (non-NTR) behavior.  It does appear to be correct as stated above (and in the original ticket post).
Also, in the last sentence of your response, you say:
It is expected behavior in Chrome that the bookmark bar stays hidden when you open a new tab while hidden, and stays visible when you open a new tab while visible.
But with NTR disabled, that is not what is observed. What is observed is that "the" bookmark bar becomes visible, regardless of its visibility state on the originating page. That is the behavior that I am requesting to be implemented in NTR, if possible.
Sorry if I'm being obtuse on all this, I'm not trying to give you a hard time. Just want to understand more clearly what is going on.
Thanks!


Update glam version requirement from 0.27.0 to 0.28.0

I'm mainly pushing this change so we can unblock the following PR in bevy repo: https://github.com/bevyengine/bevy/pull/13792.
From the only issue filed in this repo I understand this is sub-par but it would be great to have this incorporated and a new version to be cut after it to be able to move the beforementioned update forward.
Checks and tests are passing locally FWIW.

Howdy! This looks good to me, I'll get this merged. As for the mint proposal, I've been pretty busy recently unfortunately, so I think that will take much longer to get done. I want to revisit this project and improve its api, and other things, but since it's working really well right now, the urgency to do so isn't there.

Alright, 13.0.0 is out on crates.io now :)
https://crates.io/crates/hexasphere

@OptimisticPeach that was fast, thanks a lot!!!


[error]docker: invalid reference format: repository name must be lowercase

python3 run_finder-mf metadata.csv \  -g bin.masked.fasta \ -out_dir /finder_out/ \ -gm /home/soft/GeneMark-ESETEP.4.69/ \  -gml /home/soft/GeneMark-ESETEP.4.69/gm_key_64 \  -om PLANTS \  -n 30
It downloads the docker image successfully and then throws following error-
Status: Downloaded newer image for sagnikbanerjee15/finder:1.1.0 docker.io/sagnikbanerjee15/finder:1.1.0 **docker: invalid reference format: repository name must be lowercase.**

Hello @ShailNair,
Thank you very much for your interest in finder. The command you executed looks correct (except that there should be a space between finder and -mf. I think that a typo here). Could you please try 'docker pull sagnikbanerjee15/finder:1.1.0'?
Thanks.

Hi, it was typing error here (for the missing space).
So, I pulled the docker image successfully
REPOSITORY                          TAG                 IMAGE ID                  CREATED             SIZE
sagnikbanerjee15/finder      1.1.0               50d4e3095f25        2 months ago        6.47GB
and when I run the above command python3 run_finder .........
I get the same error saying
docker: invalid reference format: repository name must be lowercase


refactor(v2): improve markup and styling on search page

Motivation

Use breadcrumbs from Infima
Use more semantic markup
Remove unnecessary styles and elements

Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Preview.

Before
After

Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

👍


Create SomeImpact Solution

I created a separate folder in the beginning folder , so I hope this is ok

I created a separate folder in the beginning folder , so I hope this is ok

Improper file name


Implement aggregate grouping

My use case is that I have multiple instances of various apps deployed to a single machine and monitored by a single sensu-client.
It's not possible to have duplicate check definitions with the same name so I've include a unique identifier in each check name, e.g: fooapp-id-check_for_process. When I add aggregate: true to my metadata, this results in the checks being written to separate buckets and not being aggregated properly.
This change allows you to specify an array of virtual check names to aggregate: enabling you to group checks into different (and multiple) buckets.
This builds upon the current effect of the aggregate: parameter and won't break existing check configs.

I've changed the implementation slightly as my initial attempt didn't take into account how the request scheduler works.
If :aggregate is set to a String then the check is assumed to be part of the specified group. Checks in an aggregate group are batched together and issued with the same :issued timestamp. A check can only belong to one group.
Existing behaviour is unaffected.

Exactly what I need. I also suggested to use subscription as tag : https://github.com/sensu/sensu/issues/766
Thanks for your work, I hope it will be merged

Waiting for feedback from @portertech on this :)

As discussed w/ @roobert, the future of the aggregate is unclear. We may need to split the functionality into two separate primitives/endpoints, to keep things well defined/clear.

Hello, any news about this feature ?

Any new on this ? Thanks

Looking into how to stop notifications based on groups of several different checks. For example if ~50% of any group of checks (one group per node, one group per service, one group per rack and one per datacenter) is down no notifications would be sent for that group. Being able to easily specify multiple aggregates would make this simple to implement.

Would love to have this, please!

A proposal for "aggregates 2.0" has been published as a comment on issue #1218. Barring any objections, this proposal will be implemented in Sensu 0.24 and will resolve this PR.

The release/0.26 branch includes "Aggregates 2.0" and supports multiple aggregates per check :+1: Thank you all for your ideas and input! Closing this pull request.


fix(links): fixes links in electron build

links in electron build now open in the default browser
fixes #81

:tada: This PR is included in version 1.5.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


409 conflict with own couchdb

Hi there,
I've just tried to use my own couchdb instance and the couchapp is installed correctly AFAICT, however when syncing I get a popup 409 document update conflict and the POST shows

Inspecting the payload it shows that it's containing a revision number which according to the CouchDB documentation, shouldn't be including in the initial POST to create a document.

This also happens after I try creating a New Document.
Strangely, if I do this with the smileupps.com default couch it doesn't set the _rev

If I then POST the initial document manually (removing the _rev) then subsequent saves work.

This fork https://github.com/dtu-compute/dtu-enote-stackedit have been modified to have working https and credentials for couchdb. The fork is not indented for general purpose, but the couchdb fixes are.

CouchDB support has been dropped in the v5 (https://stackedit.io/app), at least for now.


workbox not working in dev

Vuetify-todo-pwa is a great project for me to learn PWA with Vue! Thx your project.
But when I run your project in dev, I found that workbox not working?
I tried to build the project and run the project in dist, workbox is work.
At the beginning, I thought that the reason is registerServiceWorker.js has a if (process.env.NODE_ENV === 'production'). I tried to remove it. But workbox still not working in dev.

Hi @MillionQW !
I'm very glad to know that my project is being useful to you! 😄
As I read in the official vuecli-plugin-pwa documentation

The service worker added with this plugin is only enabled in the production environment (e.g. only if you run npm run build or yarn build). Enabling service worker in a development mode is not a recommended practice, because it can lead to the situation when previously cached assets are used and the latest local changes are not included.
Instead, in the development mode the noopServiceWorker.js is included. This service worker file is effectively a 'no-op' that will reset any previous service worker registered for the same host:port combination.
If you need to test a service worker locally, build the application and run a simple HTTP-server from your build directory. It's recommended to use a browser incognito window to avoid complications with your browser cache.

Regards!


Add Chrome and Gecko WebDrivers

These are tools to automate browsers, and not actually drivers in the typical sense, so I think these should still go into the main repo.
After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if updating a cask:

[ ] If the sha256 changed but the version didn’t,
provide public confirmation by the developer: {{link}}

Additionally, if adding a new cask:

[x] Named the cask according to the token reference.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no open pull requests for the same cask.
[x] Checked the cask was not already refused in closed issues.
[x] Checked the cask is submitted to the correct repo.

Completely missed that these are available as Formulae.


Consider syncing changes from https://github.com/ieQu1/system_monitor

Hello,
We've made some significant performance optimizations in this application mostly to support systems with much larger number of processes.

Size of the delta record has been shrunk to reduce memory usage (now it only stores the pid, prev. reductions and memory, everything else is derived from the runtime data).
Postgres operations are batched
Data collection has been moved to a separate process to avoid blocking the server with requests for data
Simplified sampling algorithm
Improved postgres schema for application and function (non-BWC change)

Improvements:

"Very Important Processes": always collect metrics for a configurable list of registered processes
Added automatic tests

Hello,
I'm sorry for not getting back to you sooner. I've taken a quick look at your repo, and the changes look nice.
Let's start with the batching of Postgres operations (https://github.com/ieQu1/system_monitor/pull/9). Was there a problem with the buffer in system_mointor_pg?

Hello,
We tried running the original version in AWS and observed multiple instances of uncontrollable queue growth.
The issue boils down to network latency: in the original implementation the round trip time is added to each individual request, so time to insert N entries is (t_q + 2 t_n) * N where t_q is the time Postgres executes the actual query (it's miniscule) and t_n is network latency.
In the updated version the total time to insert N entries is just t_q * N + 2 t_n. This solved our issue.

I see the benefits of batching the Postgres requests and would like to merge that into our repo. When looking at the PR where you introduced Postgres batching, I noticed that you removed a buffer. The buffer was meant to hold some data when the Postgres connections didn't have a connection to Postgres.
The reason we introduced this was that we would got gaps in the system monitor data when the Postgres connection was down. These gaps occurred during network instabilities at our cloud provider, which is a time when system monitor data is extra valuable.
To this day, we have not noticed any problems with the buffer. Did you? Do you think we can include the buffering without removing the buffer?

Sorry, I misunderstood the question then. If I remember correct, we decided that it's better to lose some datapoints than to be OOM-killed when the queue grows (since it stores all the messages in RAM). We didn't run a separate test with queue and batching, it was all changed in a single commit.

I've started to sync the changes here: https://github.com/klarna-incubator/system_monitor/pull/20
Let me know what you think. I'll continue with the smaller delta record when I'm back at work.

P.S. If you want to revert the change that removed the queue, WDYT about using https://github.com/emqx/replayq instead? It can offload data to disk.

The intention is that the buffer should not grow indefinitely. It has a max size that can be configured using an app env. As we haven't seen any problems with the buffer, I will not spend time fixing it. If you want to make a PR to start using replayq, I'll look at it.
My intension is it

Thanks for highlighting the changes in your fork of this repo. I am interested in some of the other stuff you have changed, but I need more time to pick these things out of your repo.
In the future, would it be possible for you to pull request changes that you would like to get into this repo?


Use Node.js CLI to update env vars during start time

Another option for #414
to answer https://github.com/Visual-Regression-Tracker/frontend/pull/332

this should solve security issue https://github.com/Visual-Regression-Tracker/frontend/pull/197/files


Row-by-row model estimator for conditional probability of cell taking arbitrary value

In looking through the satellites demo, I would like to find satellites that are likely to be reconnaissance satellites that weren't labeled as such. My first attempt at this was:
estimate name, purpose, probability of purpose = "Reconnaissance" as prob_recon from satellites_cc

However, probability of purpose = "Reconnaissance" is a constant, because it estimates the probability under the distribution over a hypothetical next column. A version of this that is indexed by observed row, that estimates the probability under the conditional distribution of the cell given all of the other observed data in the row, would be helpful. Presumably this would have the form predictive probability of <column> = <value>, to keep in form with predictive probability of <column>.
Interestingly, predictive probability of <column> = <value> gives the same constant result as probability of <column> = <value>. Is this a bug?

Hm.  The existing metamodel interface exposes two functions, which correspond to the two things you didn't want: column_value_probability assumes a fresh row, and row_column_predictive_probability evaluates the probability of the value currently there, not a hypothetical one.  I am in the process of refactoring that interface to permit a generic logpdf_joint method that would enable your query, but some change in the surface language would still be required to enable you to ask that question in a query.

I think having access to the full capability of your logpdf_joint in BQL would feel empowering for me as a user: It would make me feel like I have access to the interface I (personally) am drawn to, which is the ability to sample from and evaluate probabilities under arbitrary conditional and marignal distributions derived from the full joint over the table and hypothetical rows. However, I haven't explored trying to compose these outputs into more complex objects using the tabular format.
For example, in the satellites demo, one problem I was hoping to tackle was creating a confusion matrix for a categorical column (Purpose) in which I sought to predict the Purpose from the other columns.

@axch, what's the status of that refactor. Has this been enabled by the committed foreign predictor interface? If so, what would be the associated language change?

Also, how is this related to #263? Would that want to use the same hypothetical?

Not by the foreign predictor interface per se, but by changes to the metamodel.  The desired metamodel changes are complete; the only thing standing in the way of this now would be to design and implement the surface syntax for it.  If you weren't about to disapparate, I would suggest that the implementing could make a nice intro-to-the-guts project for you, @gregory-marton .  Not sure how to make the decision on what the syntax should actually be, though.


Tree Explorer Focus vs. Current File Highlighting Confusing

Issue Type: Bug

Open a file by double-clicking on it in the explorer tree in the sidebar
Click back to the same file in the side bar to enable up + down keyboard navigation around the tree
Navigate to a different file with the same name (good example: index.js or readme.md, for projects with lots of those)
Focus in to the file that is open
Glance at the results in the explorer tree. Which file is currently open?

Actual Results:
The highlight style of the cursor indicator is almost exactly the same to the highlight style of the currently opened file. This makes it very difficult to distinguish which file is currently open, especially with a quick glance:

Expected Results:
The highlight style of the cursor indicator should be very different than the highlight style of the currently opened file and possible to be distinguished from a quick glance.
Keywords for search: workbench, list, sidebar, side bar
Similar: Microsoft/vscode#67697
cc @joaomoreno @isidorn @roblourens
VS Code version: Code 1.31.1 (1b8e8302e405050205e69b59abb3559592bb9e60, 2019-02-12T02:16:38.656Z)
OS version: Darwin x64 18.2.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6567U CPU @ 3.30GHz (4 x 3300)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
3, 2, 2

Memory (System)
16.00GB (0.07GB free)

Process Argv
-psn_0_577677

Screen Reader
no

VM
0%

Extensions (12)

Extension
Author (truncated)
Version

snapshot-tools
asv
0.2.2

vscode-eslint
dba
1.8.0

tslint
eg2
1.0.43

prettier-vscode
esb
1.8.1

wordcounter
kir
1.4.0

graphql-for-vscode
kum
1.13.0

rainbow-csv
mec
1.0.0

vsliveshare
ms-
0.3.1182

vscode-docker
Pet
0.5.2

mdx
sil
0.1.0

vscode-open-in-github
sys
1.12.0

vim
vsc
1.0.8

I would propose that a completely separate style should be developed for the "cursor" in the tree view, to make it visually distinct at a glance (don't know what the design language permits here, but potentially some kind of light arrow or something?)

Agreed, tracking this in https://github.com/Microsoft/vscode/issues/67697

Oh ok, then our issues did describe the same problem/solution pair.
@roblourens Do you think you could reword your description and maybe also title in #67697 to be more clear?
I read it three times, and was still unsure whether you were proposing a change to the style to make them distinct or whether you wanted to make the two styles exactly the same.

@roblourens, as per @isidorn's latest comment in #67876 (which has been closed as fixed), it appears that the visual style is not changing, making this not a duplicate of the other issue. Can we reopen this?
cc @isidorn @misolori

Sure. @misolori assigning to you as I am not passionate about this

We can dim list.inactiveFocusBackground a bit so it doesn't stand out as much:

Or we can also apply list.activeSelectionForeground to list.inactiveSelectionForeground:

@isidorn @joaomoreno @bpasero thoughts?

My personal feeling is that there is not much value in showing both the selected and focused items when the tree does not have focus. I think we never did that in the past, e.g. here is a video from the old tree times:

@bpasero this makes somehwhat sense and is probably the main cause of confusion. So I +1 it.

What was the main reason we added both focus and selection in the inactive state?

It's something the new tree added. So @joaomoreno would be the best to answer this one.

We used to have it in the old tree. We then made it the same in the list. Then it was removed from the old tree and left in the list. The new tree is based on the list. 🤷♂

Since we've already introduced this color token (and there are several themes that define this) do we just need to set the default to null in our color registry?
https://github.com/Microsoft/vscode/blob/2e173fabe821d06a60f532b90d6e5d95c0e09a9c/src/vs/platform/theme/common/colorRegistry.ts#L230

Thanks @misolori and everyone else!

I realize this is closed but, my $.02, the most frustrating part is the style priority. list.inactiveSelectionBackground should have a lower priority than list.inactiveFocusBackground, that way the inactive selection background can be set to something fairly muted and when it's focused by switching files a less-muted current file highlight will make it clear what's going on.
At the moment, the reverse is true which behaves like loosing the inactiveFocusBackground entirely when you happen to switch to the currently selected file...


blog: request validation

Signed-off-by: Navendu Pottekkat<EMAIL_ADDRESS>New blog post on using the request-validation plugin.
Please don't merge this PR after approval. I will merge it when we are ready to promote it.

@navendu-pottekkat Don't we want to publish it on the API7 website?

@Boburmirzo I think it is better here because it is very APISIX specific. I usually publish articles which have a more broader audience in the API7.ai website. Also it is good to keep publishing here IMO. Any strong reasons why we should publish on the other website?

@Boburmirzo I think it is better here because it is very APISIX specific. I usually publish articles which have a more broader audience in the other website. Also it is good to keep publishing here IMO. Any strong reasons why we should publish on the other website?

That makes sense! No, I do not have a strong reason. I remember the Growth team was pushing the idea of publishing a post first to the API7 blog. That's why I asked:)

@navendu-pottekkat The post is nice and quite easy to understand. I love that! Would you like to make a tutorial from it later on too?
Just I am thinking it will be quite useful content for the Tutorials section on the APISIX website:
https://apisix.apache.org/docs/apisix/tutorials/expose-api/

@navendu-pottekkat The post is nice and quite easy to understand. I love that! Would you like to make a tutorial from it later on too?
Just I am thinking it will be quite useful content for the Tutorials section on the APISIX website:
https://apisix.apache.org/docs/apisix/tutorials/expose-api/

I can make a video tutorial using your blog post if you allow me.

@Boburmirzo Yes to all. Please feel free.

I can modify it to fit into the tutorials section.

@yzeng25 I'm still waiting for an answer (or a change) to my last comment, which wasn't addressed. The content is good, but the question of why you should validate in the API Gateway needs to be answered in the introduction, not the conclusion, and with convincing arguments.
As it stands, I expect pushback - and with good reasons.


Created a pytest mark for broken tests

To mark tests that will currently fail due to the underlying code-base being broken, I've created the new pytest mark pytest.mark.broken, as opposed to manually skipping the test. This allows us to easily find and fix the broken tests in the future as the code base regains stability.
Use this at the top of a test module:
pytestmark = pytest.mark.broken

or as a decorator on a test function/test class:
@pytest.mark.broken

along with a comment as to why the test is currently broken.

Great, thanks @smite!


chore(nodebuilder/p2p)!: Upgrade arabica chain ID to arabica-4

Blocked on #1620

Codecov Report

Merging #1696 (94705c8) into main (d873e02) will decrease coverage by 0.12%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1696      +/-   ##
==========================================
- Coverage   55.14%   55.02%   -0.12%
==========================================
  Files         230      230
  Lines       15007    15007
==========================================
- Hits         8275     8258      -17
- Misses       5847     5865      +18
+ Partials      885      884       -1

Impacted Files
Coverage Δ

nodebuilder/p2p/network.go
100.00% <ø> (ø)

share/eds/byzantine/pb/share.pb.go
32.88% <0.00%> (-1.97%)
:arrow_down:

das/coordinator.go
86.76% <0.00%> (-1.48%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


chore(Algebra/Module/Equiv): clean and golf

Thank you @grunweg for your review.
I have merged master, so let's see if the checks succeed now. I don't believe the changes I've made could introduce any build errors...

Thank you @grunweg for you review! Fixed the problem.

Thanks! This looks good to me now, so let's
maintainer merge

Thanks!
bors merge


Obese male: Obj. file?

Thanks a lot for this repo!
Could you also add the raw obj file to the repo? I would like to add some other animations.
Not really an issue, but i dont know how else i could reach out to you...
Thanks in advance!

Hi, I'm sorry, I can see the model is not available anymore. Since it was a copyright material, I didn't have the permission to distribute it in its raw format and I don't have the original file anymore.
Overall, I see that now it's harder to get quality free 3d models.
But you can also use one the models included in the Mixamo library. This model I found searching for the other model looks good too.

Thanks for your answer @eh3rrera.
The obese guy perfectly fits the needs of my university project (therefore non-commercial and never released app)
I managed to transform the .dae file with blender to an .obj and add some other animations in Mixamo. But you are right, since its not publicly available anymore, we should not merge the .obj file into this repo. Thanks again for your efforts!

Great 👍


complete records change from last 1 day to last 30 days

complete records page should show records that have been ingested over the past month so users have more time to check what's been ingested

complete


simplify function_ref code by deducing noexcept-ness and remove branching for void return type

function_ref implementation can be simplified a bit by deducing noexcept-ness and removing unnecessary constexpr branch for void return type

also fixed clang compilation error due template template mismatch

Seems unsupported by MSVC

PS: which version of Clang were you testing?

I tried it with clang 17.0.6 and 16.0.6. 15 and lower has some errors (looked just now) will fix them tomorrow.
MSVC makes me sad.


support ndt error minimization?

Dear authors,
Thanks for sharing this excellent work to community!

I want to know whether drpm could be used in ndt-based error minimization pipeline lio slam system?

BTW, the rotation convention is hamilton or JPL? I see the pose update is left multiply with old pose.

If our rotation convention  is hamilton, is there a typo in equ 8? If rotation convention is JPL, i understand that is OK, we use local pertubation in JPL convention to calculate jacobian and to locally update (left multiply) with old pose to get new pose.

Thank you for the questions and the kind words.

The code can't be used as-is for NDT. It might be possible to extend the method to NDT. The key is to model spurious noise entering the Hessian. As far as I know, NDT uses covariance matrices instead of surface normals. One would need to model the spurious information induced by the covariance matrices.
The method can be used with either convention. Adjoint matrices can be used to relate left and right operations. The derivations in section II use left multiplications in line with ref [23]. In the implementation used for experimental evaluation, we express the Hessian and find the perturbation in the local LiDAR frame. The resulting perturbation can be used directly for right-side updates or be transformed for use in left-side updates via an appropriate adjoint transformation.
In (8) the negative sign stems from applying the transpose operator to the small-angle approximation of $\bar{R}_i$. $\bar{R}_i^T = Exp(\eta_i)^T \approx I + [\eta_i]_x^T = I - [\eta_i]_x$.

Thanks very much for your very kind and detailed reply, my problem is solved.


[Feature] add startAt property

is that possible to add startAt to
player.open( playList ,startAt: duration );

and to
player.jump( index ,startAt: duration );

Check Media class's constructor.


RestAPI

Hey guys,
whats about the RestAPI? Where is it? Can you implement it? Would be great..

Hey @klightspeed,
whats about the suggestion?


Oncoplot multi-hit color not visible on linux

Hi,
I am developing a shiny app that includes an Oncoplot as one of the outputs. When I am running the app on my windows pc, all works fine. I can change the color the way I want, but when I run the app via my Linux machine, I get this plot with blank color in the central oncoplot. More strange is that the color appears on the right sidebar and top one. I can't figure out why these colors are not shown on the oncoplot and in the legend.
The color variable I give to the oncoplot function is well-formatted as a list of strings with the correct names for each element corresponding to the mutation type.
I have tried with the maf example file, which produces the same error. Any ideas to fix that?

reproducible in this manner :
col = c(RColorBrewer::brewer.pal(3,"Paired"),"#D43F3AB2")
names(col)=c("mut_id","mut_int","poly","Multi_Hit")

cancer = c(RColorBrewer::brewer.pal(8,"Dark2"),RColorBrewer::brewer.pal(12,"Paired"),RColorBrewer::brewer.pal(3,"Accent"))
names(cancer)=unique(DEMOG_MUT$CANCER[!is.na(DEMOG_MUT$CANCER)
cancer_col = cancer[which(names(cancer)%in%new_clinical$Cancer)]
cancer_col = list(Cancer=cancer_col)

oncoplot(maf=laml,
               drawColBar = T,
               genes = genes_names,
               showTumorSampleBarcodes = T,
               clinicalFeatures = "Cancer",
               sampleOrder = nearest_rea$df$IPP,
               keepGeneOrder = T,
               showTitle = F,
               legendFontSize = 1.5,
               annotationFontSize = 1.5,
               SampleNamefontSize = 1.5,
               barcode_mar = 7,
               legend_height = 5,
               gene_mar = 9,
               colors = col
      )

Session info
> sessionInfo()
R version 3.5.1 (2018-07-02)
Platform: x86_64-redhat-linux-gnu (64-bit)
Running under: CentOS Linux 7 (Core)

Matrix products: default
BLAS/LAPACK: /usr/lib64/R/lib/libRblas.so

locale:
 [1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C
 [3] LC_TIME=en_US.UTF-8        LC_COLLATE=en_US.UTF-8
 [5] LC_MONETARY=en_US.UTF-8    LC_MESSAGES=en_US.UTF-8
 [7] LC_PAPER=en_US.UTF-8       LC_NAME=C
 [9] LC_ADDRESS=C               LC_TELEPHONE=C
[11] LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base

other attached packages:
 [1] maftools_2.6.05        data.table_1.14.2      umap_<IP_ADDRESS>
 [4] tidyr_0.8.3            stringr_1.4.0          shinyjs_2.1.0
 [7] shinycssloaders_0.2.0  openxlsx_4.1.1         gridExtra_2.3
[10] shinydashboard_0.7.1   htmltools_0.3.6        formattable_<IP_ADDRESS>00
[13] plotly_4.8.0           ggplot2_3.1.0          dplyr_<IP_ADDRESS>
[16] DT_0.5                 shiny_1.2.0

loaded via a namespace (and not attached):
 [1] reticulate_1.22    tidyselect_0.2.5   purrr_0.3.1        splines_3.5.1
 [5] lattice_0.20-38    colorspace_1.4-0   viridisLite_0.3.0  yaml_2.2.0
 [9] survival_2.43-3    rlang_0.4.11       R.oo_1.24.0        later_0.8.0
[13] pillar_1.3.1       R.utils_2.11.0     glue_1.3.0         withr_2.1.2
[17] RColorBrewer_1.1-2 lifecycle_1.0.0    plyr_1.8.4         munsell_0.5.0
[21] gtable_0.2.0       R.methodsS3_1.8.1  zip_2.2.0          htmlwidgets_1.3
[25] crosstalk_1.0.0    httpuv_<IP_ADDRESS>     Rcpp_1.0.0         xtable_1.8-3
[29] openssl_1.2.2      promises_1.0.1     scales_1.0.0       jsonlite_1.6
[33] mime_0.6           RSpectra_0.16-0    askpass_1.1        png_0.1-7
[37] digest_0.6.18      stringi_1.3.1      grid_3.5.1         tools_3.5.1
[41] magrittr_1.5       lazyeval_0.2.1     tibble_2.0.1       crayon_1.3.4
[45] pkgconfig_2.0.2    Matrix_1.2-15      assertthat_0.2.0   httr_1.4.0
[49] R6_2.4.0           compiler_3.5.1

Is it possible to try a new version of maftools to see how it works?
https://github.com/PoisonAlien/maftools/blob/d04f4704584377fe484179c09a6d587d2c29b7c0/DESCRIPTION#L4

I can't using github repo, I don't understand why !
ERROR: compilation failed for package 'maftools'
* removing 'C:/DATA/R.Apps/R-4.0.2-win/library/maftools'
* restoring previous 'C:/DATA/R.Apps/R-4.0.2-win/library/maftools'
Warning message:
In i.p(...) :
  installation of package ‘C:/Users/da/AppData/Local/Temp/RtmpWC3mbu/file4b44318a2a90/maftools_2.10.10.tar.gz’ had non-zero exit status

I mean on your Linux machine.
For Windows, you may need to restart the RStudio session before installing the maftools or you are lack of Rtools in windows.

I have install it on my linux machine now and I still have this bug.

> sessionInfo()
R version 3.5.1 (2018-07-02)
Platform: x86_64-redhat-linux-gnu (64-bit)
Running under: CentOS Linux 7 (Core)

Matrix products: default
BLAS/LAPACK: /usr/lib64/R/lib/libRblas.so

locale:
 [1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C
 [3] LC_TIME=en_US.UTF-8        LC_COLLATE=en_US.UTF-8
 [5] LC_MONETARY=en_US.UTF-8    LC_MESSAGES=en_US.UTF-8
 [7] LC_PAPER=en_US.UTF-8       LC_NAME=C
 [9] LC_ADDRESS=C               LC_TELEPHONE=C
[11] LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base

other attached packages:
 [1] maftools_2.10.0        data.table_1.14.2      umap_<IP_ADDRESS>
 [4] tidyr_0.8.3            stringr_1.4.0          shinyjs_2.1.0
 [7] shinycssloaders_0.2.0  openxlsx_4.1.1         gridExtra_2.3
[10] shinydashboard_0.7.1   htmltools_0.3.6        formattable_<IP_ADDRESS>00
[13] plotly_4.8.0           ggplot2_3.1.0          dplyr_<IP_ADDRESS>
[16] DT_0.5                 shiny_1.2.0

loaded via a namespace (and not attached):
 [1] reticulate_1.22    tidyselect_0.2.5   purrr_0.3.1        splines_3.5.1
 [5] lattice_0.20-38    colorspace_1.4-0   viridisLite_0.3.0  yaml_2.2.0
 [9] survival_2.43-3    rlang_0.4.11       R.oo_1.24.0        later_0.8.0
[13] pillar_1.3.1       R.utils_2.11.0     glue_1.3.0         withr_2.1.2
[17] RColorBrewer_1.1-2 lifecycle_1.0.0    plyr_1.8.4         munsell_0.5.0
[21] gtable_0.2.0       R.methodsS3_1.8.1  zip_2.2.0          htmlwidgets_1.3
[25] crosstalk_1.0.0    httpuv_<IP_ADDRESS>     Rcpp_1.0.0         xtable_1.8-3
[29] openssl_1.2.2      promises_1.0.1     scales_1.0.0       jsonlite_1.6
[33] mime_0.6           RSpectra_0.16-0    askpass_1.1        png_0.1-7
[37] digest_0.6.18      stringi_1.3.1      grid_3.5.1         tools_3.5.1
[41] magrittr_1.5       lazyeval_0.2.1     tibble_2.0.1       crayon_1.3.4
[45] pkgconfig_2.0.2    Matrix_1.2-15      assertthat_0.2.0   httr_1.4.0
[49] R6_2.4.0           compiler_3.5.1

Could you provide a reproducible and minimal example with maftools builtin dataset? If the bug is still existing, this would help check if the problem comes from the code. Also you can check result of capabilities() to see the supported graph devices on your linux.
library(maftools)

laml.maf = system.file("extdata", "tcga_laml.maf.gz", package = "maftools") #MAF file
laml.clin = system.file('extdata', 'tcga_laml_annot.tsv', package = 'maftools') #clinical data
laml = read.maf(maf = laml.maf, clinicalData = laml.clin)

Besides, for you oncoplot(), perhaps you can check col on the linux and your windows, and see if they are identical.

I'm sorry to have made you lose your time! I found my error, and it's nothing about oncoplot function. But a massive thanks for your quick answer!

@dancelestini you're welcome. Please also close this issue :).

I am glad you were able to fix it. It would also help if you can post what was the issue.
Thanks, @ShixiangWang as always.

Yes sorry, so my issue was that the names(col) was wrong so the oncoplot functions wasn't able anymore to show the corresponding colors to the variant_classification. Something strange happend when transfering the code in my linux machine and the names(col) has been converted to NA so it's explain the complex_event legend. By correcting the names(col) I solve the problem.
Thanks you both !


Automate the gathering and publishing of new toolchain versions

An attempt at automatically updating the toolchain version.
In short what this PR does:

Get the current RUST_VERSION from the Rakefile
I originally though of using some grep/regex magic to get this value, but thought: "Ruby knows best what it's looking for".
Get the latest release from rust-lang/rust (This is what github determines as "latest" - so there is some limitation there if patches for older versions are released)
IF the values are different:

update the value with sed magic in the file (Makes me second guess my "ruby knows best" comment above) and runs bundle exec rake toolchain:sync
Create[/Update] a PR to merge.

I've had some success running this action with act, however for some reason I'm getting a "Could not read from remote repository" when it tries to run git remote prune origin here: https://github.com/peter-evans/create-pull-request/blob/main/src/create-pull-request.ts#L138. (running with act -s GITHUB_TOKEN="$(gh auth token)" -j check-toolchain-version, have also tried a hardcoded PAT token, to no success).
I can confirm everything works up until the git pr/commit part of it, so that's all good. In theory the last PR part should "Just work", but it might be a wait and see on the next rust release. I fear having a dirty tree (only easy way to test this) is causing some issue somewhere.
Fixes: #192

@lopopolo Woo! https://github.com/b-n/gh-action-test/blob/main/.github/workflows/create-pr.yaml generates https://github.com/b-n/gh-action-test/pull/1 so the answer is yes - we can play with variables, and yes - it works. I added you as a contributor to that repo so you can press the play button here: https://github.com/b-n/gh-action-test/actions/workflows/create-pr.yaml (if you just want to see it working :sweat_smile:
I'll fix up this PR tomorrow at some point. The key takeaways:

It works
It supports variable interpolation
It does require some permissions on the action runner - I'll see if I can find the values in terraform and add to project-infrastructure if applicable.

w.r.t runner permissions: I can't find a terraform setting for this specific switch: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#preventing-github-actions-from-creating-or-approving-pull-requests.
Apparently it's possible to just us gh commands on github runners without having to use this particular setting (haven't tested). It seems a bit redundant though whether it's from a action or whether it's from your own gh scripting to restrict this functionality, so I'm not sure what's the best course.
The create-pull-request does use just the plain github api from what it looks. I do wonder whether providing a machine token to the token: attribute (e.g. a machine PAT token) would actually circumvent this setting. Is the one available for the artichoke org?

@lopopolo I have one tiny other little idea:

Even though not "needed", we can create a rust-toolchain.toml file in this repo.
In the rakefile, we read the current version from rust-toolchain.toml instead of inside the artichoke main repo: https://github.com/artichoke/artichoke/blob/trunk/Rakefile#L201
We read/update the value in rust-toolchain.toml via grep/sed.

Why? Because then we can use the exact same github action in this repo as we can in the main artichoke repo. Thoughts?

Sorry, another message - eventually I might try and commit a dependabot-core for rust-toolchain. Looks like an old issue is people wanting it a long time ago: https://github.com/dependabot/dependabot-core/issues/1758#issuecomment-834333421
Dependabot-core usage restricts the running of pre-post commit things, but there is apparently a way to bump commits on top of dependabot PRs, so that could be done for the toolchain:sync part: https://github.com/dependabot/dependabot-core/issues/1758#issuecomment-834333421 (This is a big TIL for me today - kinda cool :sweat_smile:)

w.r.t runner permissions: I can't find a terraform setting for this specific switch: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#preventing-github-actions-from-creating-or-approving-pull-requests.

at https://github.com/artichoke/docker-artichoke-nightly/settings/actions:

There's an org setting I can flip to enable us turning that on in this repo. Let me look to see if I can terraform this.

@lopopolo I have one tiny other little idea:

Even though not "needed", we can create a rust-toolchain.toml file in this repo.
In the rakefile, we read the current version from rust-toolchain.toml instead of inside the artichoke main repo: https://github.com/artichoke/artichoke/blob/trunk/Rakefile#L201
We read/update the value in rust-toolchain.toml via grep/sed.

Why? Because then we can use the exact same github action in this repo as we can in the main artichoke repo. Thoughts?
Could also make it a published action. e.g.
- uses: artichoke/rust-toolchain-dependabot
  with:
    toolchain_path: ./rust-toolchain.toml
    toolchain_syntax: toml
    pre_commit_command: "bundle exec rake toolchain:sync"

"A github action that will check and update the rust toolchain. You can provide your own command to update any other files prior to commiting"

this sounds pretty sweet and I'd be interested to experiment here. Let me know if you want me to set up a repo for you

@lopopolo I'll merge this one for now after incorporating the feedback. I'm sure the action will fail on the run unless those options are action perms are added.
Also, more than happy to give a generic action a go, so yes please to a repo!

I tweaked the setting and bumped the job. It worked!

https://github.com/artichoke/docker-artichoke-nightly/pull/198

It looks like PRs created with this workflow don't trigger github status checks to run on PRs: https://github.com/peter-evans/create-pull-request/issues/48
A workaround I've found is to close and then reopen the PR.


Add entrypoint for exercise information

Kind: feature
(Summary: as discussed with @yurug and @leunam217, this new entrypoint appeared to be necessary for the learn-ocaml.el-based student workflow)
This PR is ready, it subsumes and replaces #297.
To test it:
make
make opaminstall
learn-ocaml "--repo=$PWD/demo-repository" build serve
export TOKEN="…"
xdg-open "http://localhost:8080/description/demo#token=$TOKEN"

Hi @yurug, thanks for your feedback! I agree that a code-factorization is welcome here :)
I have to go away from my keyboard now (but I should be able to do it tonight or tomorrow Monday)

Dear @yurug

This PR seems fine but if you could do a pass to improve code factorization, it would be nice!

Done. Tested locally (just need to wait for the CI :)

Dear @yurug, this PR #326 was already ready, but for more clarity I've just "split" the last commit into several parts:

the commit ffe6040 deals with the refactoring you had requested in your review;
the commit dacffc5 performs a further small refactoring by modifying an interface (but which seems unused elsewhere), of course I can revert that commit if you disagree;
and the last two commits 26df32a and f737279 are just details (w.r.t. spaces/colon) entangled with an automatic update of translations/fr.po (thanks to make update-fr-translation, which needs the gettext package - and an editor such as emacs+https://melpa.org/#/po-mode)

Thank you @erikmd !


Ability to teleport player without teleport confirm

resolves #2220

I'd like to see the variable named (should)confirmTeleport rather than noConfirm, don't want to introduce double negatives into the api.
I also don't think this elegantly handles a situation where you teleport a player with confirmation and then immediately teleport a player without confirmation... it looks like it would override the confirmation it's waiting on and start showing the player's client position when it shouldn't.
I don't think noConfirm should not overwrite a valid pending teleport confirmation
player.teleport(pos1, confirm); // Player is frozen at their destination
player.teleport(pos2, noConfirm); // Player is no longer frozen at their destination and running around doing whatever without being teleported, even though their client has yet to confirm teleport 1.

I don't think noConfirm should not overwrite a valid pending teleport confirmation
It does not overwrite valid pending teleport confirmation. It sends a teleport with ID -1, and when receiving a response with ID -1, this response is simply ignored


Container image scan for application vulnerabilities

cdxgen 3.0.0 would support application SBoM generation from container images. dep-scan could be enhanced to support reporting application-specific vulnerabilities from this bom.
NOTE:
This is not the same as container image scanning that reports OS-specific vulnerabilities. If you're interested in that feature you can contact me to discuss some funding options.

v2.0.0 is released


Add Kinvolk logo to container

I am trying a new approach, so let's pause this for a sec.

We won't use this approach in the end. We have an alternative that won't need us to include Kinvolk's logo in the repo.
Thanks for the investigation though, that made clear what we needed to do.


Fix Babel interference with source project:

Avoid transpiling transform files to help surface errors.
Convert ES6 to ES5 to allow CLI to run under Node 0.12.x.
Pass options to all transforms.
Fix single transform option.

Pretty sure you could have written a codemod script to do this for you...


Cache persistence based on AsyncStorage

This PR adds a new approach for cache persistence based on AsyncStorage in React Native

I do not understand why you say it will not work, if the SWR instance is only generated once the cache is initialized, as long as it is not initialized SWRConfig will never be rendered.
It would be great if you have the opportunity to test this workaround, because on my side it works without any problem. @shuding

Hey guys @shuding @huozhi, do you have any update about this MR?
If you guys have any feedback, please let me know


Cannot load libcuda.so.1

FROM jrottenberg/ffmpeg:4.2-nvidia
ffmpeg version 4.2.2 Copyright (c) 2000-2019 the FFmpeg developers
built with gcc 7 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
configuration: --disable-debug --disable-doc --disable-ffplay --enable-shared --enable-avresample --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-gpl --enable-libass --enable-fontconfig --enable-libfreetype --enable-libvidstab --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libxcb --enable-libx265 --enable-libxvid --enable-libx264 --enable-nonfree --enable-openssl --enable-libfdk_aac --enable-postproc --enable-small --enable-version3 --enable-libbluray --enable-libzmq --extra-libs=-ldl --prefix=/opt/ffmpeg --enable-libopenjpeg --enable-libkvazaar --enable-libaom --extra-libs=-lpthread --enable-nvenc --enable-cuda --enable-cuvid --enable-libnpp --extra-cflags='-I/opt/ffmpeg/include -I/opt/ffmpeg/include/ffnvcodec -I/usr/local/cuda/include/' --extra-ldflags='-L/opt/ffmpeg/lib -L/usr/local/cuda/lib64 -L/usr/local/cuda/lib32/'
When i try to ffmpeg with -c:v h264_nvenc  i got thie problem. Strange, cause ffmpe built up with nvenc/cude/cuvid support. File exists in /usr/local/cuda-10.2/compat/libcuda.so.1
How to resolve issue?

Seems to be that problem related to that in composer no gpu was described
when i try to run
docker run --runtime=nvidia
docker run --gpus all
then it works.
But how to run service with that gpu enabled?

@kuznetcoff777 were you able to fix this?

@wobeng
https://docs.docker.com/compose/gpu-support/
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              count: all
              capabilities: [gpu]


Update docs skeleton and add index config docs.

Let's merge this PR before receiving PR from everyone.

thanks @PSeitz for your comments. I will report them when possible but I forgot to push all my commits I had locally :/


Fix panic in multi_node_sim

Closes https://github.com/spacemeshos/go-spacemesh/issues/2257
When the stdout of the PoET server is not read, the server hangs after some time, which causes a panic in multi_node_sim.
How to test this PR:

Add replace github.com/spacemeshos/poet => ../poet to go.mod in https://github.com/spacemeshos/go-spacemesh (assuming it's located in the adjacent directory)
Attempt to reproduce https://github.com/spacemeshos/go-spacemesh/issues/2257 following steps from the PR description
There should be no panic

Alternatively, perhaps reading and logging the poet output would be even better - up to you.

@noamnelke Thanks, I agree. The changes you suggested work fine.

Superseded by https://github.com/spacemeshos/go-spacemesh/pull/2290


Hey

Hey
Originally posted by @Carla6-7 in https://github.com/apache/superset/pull/17999#issuecomment-1011730428

Hey.


DOCS: Figure 2 not showing on readthedocs

Looking at
http://shapely.readthedocs.io/en/stable/manual.html#linearrings
there is no Figure 2 showing up for the LinearRing example.
Operating system
macOS 10.12.6, using Chrome 67

Actually, Figure 1 is the only one showing.


fix(graphql-transport-ws): ensure result message is processed before …

fix(graphql-transport-ws): ensure result message (next or error) is processed before complete message; do not close connection if keepalive is on

Hi!
Could you explain (on a higher level) what exactly this does, why it's needed/an improvement and document the change in behaviour with a test?
I don't fully understand it yet.

Hi!
Could you explain (on a higher level) what exactly this does, why it's needed/an improvement and document the change in behaviour with a test?
I don't fully understand it yet.

I'm using websocket connection not only for subscriptions, but also for single result operations.  This pr is to fix 2 bugs that occur for single-result operations.
this part of code in graph-transport-ws.dart causes race condition, if "complete" message is received shortly after "next" message, it's possible that "complete" message is processed before "next" message (because of this step final messageMap = await options.graphQLSocketMessageDecoder(msg);), which closes sink, but next message will still add data to sink, which causes process to hang, there is no error thrown
try {
    final messageMap = await options.graphQLSocketMessageDecoder(msg);
    message = parseMessage(messageMap!, options.parser);
  } catch (e, s) {
    throw WebSocketLinkParserException(
      // TODO: should not be ConnectionAck
      message: ConnectionAck(),
      originalException: e,
      originalStackTrace: s,
    );
  }

this part of code closes connection whenever there are no more operations in process, which is not desired, because I want to do a bunch of single-result operations before I do subscription
released.then((_) {
          if (locks == 0) {
            // and if no more locks are present, complete the connection
            ...
          }
  }
)

Thanks! I can see how awaiting the decoded message is problematic.
try {
    final messageMap = await options.graphQLSocketMessageDecoder(msg);
    message = parseMessage(messageMap!, options.parser);
  } catch (e, s) {
    throw WebSocketLinkParserException(
      // TODO: should not be ConnectionAck
      message: ConnectionAck(),
      originalException: e,
      originalStackTrace: s,
    );
  }

I observe the following:

The method signature returns a FutureOr
The default implementation is just a synchronous jsonDecode()

So, the  await is probably unnecessary for the vast majority of users
              final messageMapFutureOr =
                  options.graphQLSocketMessageDecoder(msg);
              final Map<String, dynamic>? messageMap;
              if (messageMapFutureOr is Future) {
                messageMap = await messageMapFutureOr;
              } else {
                messageMap = messageMapFutureOr;
              }

This would avoid this problem by processing the message synchronously, if possible.
But it would be a breaking change, so let's investigate on how to handle the path with a future:
            int waitTimeOut = 0;
            while (message is CompleteMessage &&
                nextOrErrorMsgWaitMap.containsKey(message.id)) {
              await Future.delayed(const Duration(milliseconds: 100));
              waitTimeOut++;
              // if next or error message is not arrived or processed in 60 seconds, break the loop
              if (waitTimeOut >= 600) {
                break;
              }
            }

This avoid the endless loop, but I would prefer a solution without polling.
How about making the
nextOrErrorMsgWaitMapa map Map<String, Completer<void>>?
Then we could just await the Completer instead of continuously polling for it.
And before removing the id, we'd call complete() on the existing completer.

this part of code closes connection whenever there are no more operations in process, which is not desired, because I want to do a bunch of single-result operations before I do subscription

Sounds reasonable.
Could you split this part up in a separate PR and add a test, which ensures that this behavior isn't get broken in a future update?
There are already similar tests in test/gql_websocket_link_test.dart. Based on your description, it could just be executing two queries sequentially and asserting the the same connection is used (if I understood the issue correctly)

I'll add tests in next couple of weeks, kinda tied up at the moment.
I can't make another pr for close connection fix because my app needs both of changes in the same repo to work

the new commit fix(graphql_transport_ws): completer error Future already completed fixes error
Bad state: Future already completed

For single-result operations, error message can complete future, but completer.complete() will be called after future is completed if caused by error, so need to check before call

We are needing similar things.  I'm wondering how this PR is coming?  Thanks for all your work on it!

very busy at the moment, I need at least 1 day to do tests, my estimation is November, you can point to my repo in the mean time
gql_websocket_link:
    git:
       url: https://github.com/agufagit/gql
       ref: master
       path: links/gql_websocket_link

If you have time to do tests, feel free to make a PR to my repo

tests are done

Thanks! LGTM


Add permissions system

Add a permissions system, with administrator roles.
See https://issues.dp.la/issues/8163
The specification was to add a class of view-only users (who can view unpublished sets, but not modify or create them), and a permissions system is necessary to achieve this.

@AudreyAltman: I've added some explanatory text that might clarify the roles.

When testing this in my local browser, I'm finding that I can't change an admin's role/status.    If I am logged in as a manager, access an admins#registrations#edit form for myself or any other admin, and try to change the role, it doesn't persist.

OK, I'll look into that!

@AudreyAltman that last commit oughta fix it.

@markbreedlove yep, that fixed it!
I think it would be good on the source_set, set, and guide views to hide links to functionality that isn't available to reviewers, but that seems out-of-scope for this ticket - I will make a new Redmine ticket to follow up on it.
All in all, this looks great.  I think it's ready to go.  Do you want to :squash: before I :merge:?

Oh yeah, I guess I overlooked some places where there are create-content links. Do the main navigational links at least get removed for you if you're a reviewer? (The links to "Administrators" and so forth?)

I will squash it if all's well with the nav links.

@markbreedlove yes, the navigational links accurately reflect what actions are available to all three roles.

OK, @AudreyAltman, should be good to go.

:rocket:


Change package name

The name FDM.jl makes the package un-discoverable.
Perhaps it could be changed to FiniteDifferences.jl or similar?

This is a great package that I wish I had discovered earlier. Not sure if I would have with the name changed, but it's possible. FDM.jl isn't very high up on DuckDuckGo results for Finite Differences Julia for instance (though Google performs better).

Very much pro-this. @iamed2 is this something that you would be happy to arrange?

This is done and transferred to https://github.com/JuliaDiff/FiniteDifferences.jl


TGraph not supported

While uproot4 supports TGraphAsymmErrors, it seems plain TGraph isn't supported.

"Support" in this case means, "has special high-level methods for easier access." All of the data can be accessed as all_members (dict) and member (method to access one).
TGraphAsymmErrors has these high-level methods because @kratsg had an idea about how he wanted to access TGraphAsymmErrors and implemented it (#240). The equivalent for TGraph would probably be very similar: a values property without the errors.
It's enough to add a submodule with the class name containing a class of the same name in uproot.behaviors, similar to
https://github.com/scikit-hep/uproot4/blob/main/uproot/behaviors/TGraphAsymmErrors.py
Since there are (to a first approximation) infinitely many classes in ROOT and the automated interpretation gets all of the private data members into all_members, I'd like to encourage users of Uproot to define how they want to access their favorite classes. That's why "uproot-methods" used to be a separate module (so that it could change more rapidly than the main codebase, and demonstrably didn't break core functioning), but keeping it as a separate module led to it getting ignored and out-of-date. So the methods/behaviors are part of the main Uproot codebase again, but I'd still like users of these classes to take an active part in shaping them.

I did implement being able to read memberwise versions of TGraph recently in #298 . I think until that point, it wasn't quite easy for one to be able to read it in. One could use the test file in scikit-hep to write a test for it. I'm guessing because it's a TGraph, you'd only want the x/y values and not much else?

In my case I'm actually reading a RooCurve. I'll work on a PR for this, the RooCurve could use some extra functions to disentangle the strange way RooFit plots histograms and errors on histograms.

Wait, are we talking about deserializing (to get an object at all) or accessing the object's methods in an easier way? Deserialization is a more significant effort (and @kratsg's work on memberwise deserialization is beyond what I'd expect most people to be able to do).
I thought we were talking about the fact that there's a TGraphAsymmErrors submodule in uproot.behaviors but not a TGraph.

I was talking about the behaviour. I can see that we have a filled all_members already.

Well, I believe up until that PR -- most TGraphs were not able to be read in since it seems a lot of them tend to be memberwise-serialized. Now that they can be read in, it shouldn't be too hard to add in the behavior. Just mostly explaining why the behavior never quite existed before for a common object.

Well, "most" depends on what kinds of ROOT files you tend to look at (i.e. the measure of your space). I remember that uproot-methods had a behavior defined for TGraph, indicating that Uproot 3 could access TGraphs, even though Uproot 3 didn't do any memberwise deserialization.
It was scikit-hep/uproot3-methods#7, added by @marinang. Looking at that now, I see that there's actually three classes, TGraph, TGraphErrors, and TGraphAsymmErrors. His implementation had a lot of methods for finding the maximum and such, though I'd rather have these objects have smaller interfaces that go straight to the library with all of that functionality now. That is, with a values method to get a NumPy array, things like the maximum can be computed in NumPy. There was also a matplotlib method; it wouldn't be bad to have something that immediately returns an "ax" to be mixed into a plot or implicitly drawn by Jupyter.
Actually, TGraph and TGraphErrors are the only two behaviors that haven't been reimplemented in Uproot 4 or are going to be in Vector. That set—histograms/profiles, graphs, TParameter, and 2D/3D/Lorentz vectors—are the ones that are desirable enough that they were requested again after the Uproot 3 → 4 transition. THnSparse is in the old uproot3-methods/classes directory, but it's just a placeholder (says "hello world") as an illustration of how to get started.

I've made a PR here with a draft implementation. No tests yet, I think those need to go in scikit-hep-testdata, right?

@beojan Thank you!
Any files that are needed as input to a test would have to go into scikit-hep-testdata/src/skhep_testdata/data, which has a normal PR/release process. If you have any files that you plan to use to test #350, you can make the PR now and I'll merge-and-deploy scikit-hep-testdata as soon as possible. It should be publicly sharable and not much larger than a megabyte. (The largest so far is 64 MB, but the median is 68 kB.)


Feature Request - Make possible to undo (redo) changes in code after VS Code's been restarted

VSCode Version: 1.21.0-ins
OS Version: win7x64

It would be great to undo (Ctrl+Z) and redo (Ctrl+Y) changes in the code we've done, after VS Code's been closed and restarted.
Is it hard to implement?

I strongly suggest not to add this feature for the following reasons:

Subsequent drawback: suppose you opened a new file, added some code/text and closed it. After some time, you opened the same file again, added some changes but found that your code/text became very messy/defective. You may need to return to the initial state when the file was last opened, but unfortunately if you keep pressing Ctrl+Z you will go beyond that state, since the undo scope will go beyond last file open. The more saved changes, the harder it will be to return to the initial state.
Hardly or infrequently needed because usually one closes the file when everything is done

I think it would be a very useful feature. I also don't think that the subsequent drawback as mentioned is really an issue, since if there is infinite ctrl+z there should be infinite redo (CTRL+Y) as well, allowing you to return to whatever state the file was opened.

Hardly or infrequently needed because usually one closes the file when everything is done

closing/opening a tab in vs-code is not perceived as closing/opening a file, it's just a tab which can be opened and closed for the same file many times. and the fact that closing a tab has side effects is not clear, and users have to learn that on their own after they lose their changes few times

but unfortunately if you keep pressing Ctrl+Z you will go beyond that state

Ctrl+Shift+Z will allow to go back and forth, so there is still an option to find correct changes. While currently there is no option at all, things just get lost.
this feature is absolutely needed since it's counterintuitive that Ctrl+Z history disappears when you for example Reload window, or even close a tab and open it back. I would even qualify this as a bug, not as a feature.

This is one of the things that are keeping me in vim.  I don't think the subsequent drawback mentioned above is a problem especially when you are using git or other vcs.

Undo/redo after file or tab closing, not VSCode reload or restart, is discussed in https://github.com/Microsoft/vscode/issues/7169 (@Ahmed-Hussein-Karam, @airato).

Full undo / redo would be amazing and should be off by default but supported by turning on a config flag.

Before VSCode, I used Atom.io for a short while. Of course I was After moving to VSC, the only thing I truly missed was this: https://atom.io/packages/persistent-undo.
This feature would be just amazing!

And any new news ?
Is that bug still there?

you will go beyond that state,

That's not a problem because in vim you see a visual indicator, basically [+] is removed, when you crossed that state.
I work with this setup in vim for ages and never had any problems. @octref, would be nice to see an update on this or somebody being assigned.

Is there an extension that will do this?  I'm not even sure what to search for.

Is there an extension that will do this? I'm not even sure what to search for.

I don't think so, it's a core feature

At least when we close a tab, the history should remain, similar to WebStorm. Not necessarily after reloading VSCode itself, but it's a great feature.

I think we can make persistent undo by modifying local-history and  and remap the undo and redo key.
We only need a brave hero to implement it

And that hero never came.

The undo history is now preserved when you close a tab. Not the case for restarting vscode entirely though.

Is anyone aware of a way / is there a way to disable the new undo stack behavior? A search of settings doesn't show anything obvious, and the update note doesn't list any settings.
While I certainly see why this would be useful, and desirable, it is also a major change in default behavior if there is no opt-out setting. Perhaps it's just me, but I frequently open a file, trying something, then discarding it by holding down CTRL/CMD + Z and expecting that to return the file state to where it was on open.
I accidentally undid committed changes today with the new behavior -- not the end of the world, and easily remedied once I realized what had happened, but slightly annoying.

@nodehead There is a seperate issue for the new undo mechanic: #7169, while this one is about preserving the changes after IDE restart.
Making the new mechanic configurable is also shortly discussed in that issue, and #94778 is the continuation. You'll probably want to participante in there.

friend I just want to undo the changes made with the file open. why did you request such a thing? he says back all the time. I want to come back to the last registered yield. going back to the last commit. Doesn't it have a setting?

Is it just me that finds "persistent undo" the weirdest thing ever? It's like expecting the bottom of the stairs to arrive in a block of flats on ten floors, but going down past that to the 20th and beyond!
As @nodehead said pretty well - this should be configurable. Several times I've undone committed changes which is just plain weird! I used Netbeans since forever (and heaps of standard text editors) the default is "sane": If you've closed a tab or a window, you closed the file. EOS.
If you want a config setting to enable that (and maybe I'm just too old, but I ask "why would you"?) then fine, but don't make it a default and/or provide a setting to control this so VSC behaves like a "standard" editor.
Thx team :-)

Re-pasting my question here because it is somewhat related. I need to prevent undos from persisting!
My extension (https://github.com/boltex/leointeg) uses file system api to implement custom 'editors' for my needs as indicated in the docunmentation here https://code.visualstudio.com/api/extension-guides/virtual-documents#file-system-api .
I need to  be able to 'block' or 'clear' undos when closing or switching from one of them to another.
It used to be that doing vscode.WorkspaceEdit "rename" operation would 'clear'/'block' all undos for the newly named document to traverse across the point where the document was renamed, but lately the newer versions of vscode tries to open a document with the old name when pressing ctrl+Z on a newly renamed document (in a custom filesystem)... Is there a way to disable that? Or a way to clear the undo stack for a given document URL? or for a filesystem scheme only in particular?
Thanks to anyone who can clarify 'undo stack' persistence behavior!

Is it just me that finds "persistent undo" the weirdest thing ever? It's like expecting the bottom of the stairs to arrive in a block of flats on ten floors, but going down past that to the 20th and beyond!

@phptek - FWIW persistent undo is "new" on the scale of it, at least 10 years old for vim. My comment in my above ticket, June 2019, suggests that persistent undo be off by default since it's a big change in behavior. vim's version is smart in that any non-vim change to the file, even metadata IIRC, resets the undo stack. So if you've pulled a new branch or even touched the file the undo is reset.

@nodehead For those of you who do not support this feature, thank you for explaining it is because you don't know how to use git checkout file-you-are-editing.js.
I'm disappointed that Microsoft continues to persist this design. At least expose the undo stack internals for someone to write a plugin for the option to make VSCode persist undo history between sessions.


bug in update.sh

in function check_version()
if wget form github failed, the script will still rm files. ( whcih happens frequently in China )
in line 8, only check the version not equal, does not check if the tmp exist or not.
should check if wget success or not, if failed, retry 3 times then exit with error code.
https://github.com/Phala-Network/solo-mining-scripts/blob/bd7d335454cbdde9e10476fce094801fe8e9927b/scripts/cn/update.sh#L8

We have fixed this issues. Thanks.


Support for large bot buckets

This pr adds support for correctly ratelimiting with both that have a
max_concurrency > 1
Depends on #5

Needs updated to latest trunk


makemigrations

I contacted you earlier this week about an issue I was facing with your system. Below is a screenshot of the issue

Kindly provide steps to reproduce, attach screenshots also.
The attached link appears to be broken.

when trying to makemigrations it also gave this error:
Traceback (most recent call last):
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/core/management/base.py", line 412, in run_from_argv
self.execute(*args, **cmd_options)
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/core/management/base.py", line 453, in execute
self.check()
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/core/management/base.py", line 485, in check
all_issues = checks.run_checks(
^^^^^^^^^^^^^^^^^^
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/core/checks/registry.py", line 88, in run_checks
new_errors = check(app_configs=app_configs, databases=databases)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/core/checks/templates.py", line 55, in check_for_template_tags_with_the_same_name
for conf in settings.TEMPLATES:
^^^^^^^^^^^^^^^^^^
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/conf/init.py", line 102, in getattr
self._setup(name)
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/conf/init.py", line 89, in _setup
self._wrapped = Settings(settings_module)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/conf/init.py", line 217, in init
mod = importlib.import_module(self.SETTINGS_MODULE)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 1204, in _gcd_import
File "", line 1176, in _find_and_load
File "", line 1140, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'settings'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/eddieosafo/e-voting-with-django/manage.py", line 23, in
main()
File "/Users/eddieosafo/e-voting-with-django/manage.py", line 19, in main
execute_from_command_line(sys.argv)
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/core/management/init.py", line 442, in execute_from_command_line
utility.execute()
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/core/management/init.py", line 436, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/core/management/base.py", line 425, in run_from_argv
connections.close_all()
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/utils/connection.py", line 84, in close_all
for conn in self.all(initialized_only=True):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/utils/connection.py", line 76, in all
return [
^
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/utils/connection.py", line 73, in iter
return iter(self.settings)
^^^^^^^^^^^^^
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/utils/functional.py", line 57, in get
res = instance.dict[self.name] = self.func(instance)
^^^^^^^^^^^^^^^^^^^
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/utils/connection.py", line 45, in settings
self._settings = self.configure_settings(self._settings)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/db/utils.py", line 148, in configure_settings
databases = super().configure_settings(databases)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/utils/connection.py", line 50, in configure_settings
settings = getattr(django_settings, self.settings_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/conf/init.py", line 102, in getattr
self._setup(name)
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/conf/init.py", line 89, in _setup
self._wrapped = Settings(settings_module)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/eddieosafo/e-voting-with-django/venv/lib/python3.11/site-packages/django/conf/init.py", line 217, in init
mod = importlib.import_module(self.SETTINGS_MODULE)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 1204, in _gcd_import
File "", line 1176, in _find_and_load
File "", line 1140, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'settings'

Kindly confirm the Django version you have installed.
Ensure all packages are installed and give it a try.
Let's know if you are having further issues.

I am still having this issue

Would it be possible for me to arrange an online meeting so you could help me resolve this issue

I have done that and uploaded it onto the git repository
On Tue, 1 Aug 2023, 11:32 am Job Sunday Owonubi, @.***>
wrote:

Kindly confirm the Django version you have installed.
Ensure all packages are installed and give it a try.
Let's know if you are having further issues.
—
Reply to this email directly, view it on GitHub
https://github.com/jobic10/e-voting-with-django/issues/15#issuecomment-1660130805,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATL6A2XEO24PDRO7J7U6DM3XTDSOFANCNFSM6AAAAAA23J4LN4
.
You are receiving this because you authored the thread.Message ID:
@.***>

pip install django_renderpdf
Kindly go through the closed issues on this repo.
I am sure you'll find solution.
Apologies for the stress 💘

Is there a way to run this without running the makemigrations command?
On Tue, 1 Aug 2023, 12:11 pm Job Sunday Owonubi, @.***>
wrote:

[image: Screenshot 2023-08-01 at 12 04 20 PM]
https://user-images.githubusercontent.com/81256554/257508414-b615335d-ba5c-43a9-a638-f72a921b5c13.png
pip install django_renderpdf
Kindly go through the closed issues on this repo.
I am sure you'll find solution.
Apologies for the stress 💘
—
Reply to this email directly, view it on GitHub
https://github.com/jobic10/e-voting-with-django/issues/15#issuecomment-1660189319,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATL6A2SOSALOU5N3N57KT3LXTDW7PANCNFSM6AAAAAA23J4LN4
.
You are receiving this because you authored the thread.Message ID:
@.***>

You'll need to migrate and runserver.
 Share it here, so others might find a fix when they experience similar thing.


Bug: Lexical Playground bug & Lexical internal logic bug in every lexical version

Lexical version: every version
Steps To Reproduce
https://github.com/facebook/lexical/assets/78121870/1ec772c8-4511-4d07-8e4b-e1cb685e59e0

select 20px in toolbar
click editor

Link to code example:

The current behavior

reset default fontSize

The expected behavior

keep current style

I found what makes bug.  onSelectionChange has below logic.
        if (
          currentTimeStamp < timeStamp + 200 &&
          anchor.offset === lastOffset &&
          anchor.key === lastKey
        ) {
          selection.format = lastFormat;
          selection.style = lastStyle;
      }

If conditional statement is true, It works expected. but currentTimeStamp < timeStamp + 200 is false.
What is the intention of this code??

https://github.com/facebook/lexical/pull/1989
You can use Git Blame to see the commit that introduced a diff, which can help you understand the intent.

@acywatson  thank you!
I have created a pull request. Could you please review my commit?


Remove install of custom toolchain on debian page

For additional context regarding gcc6 see https://github.com/mendersoftware/mender-convert/pull/78

Awesome!
Sorry to feature-creep, but could you do the same in the docker-mender-convert container? Probably not urgent but good for maintenance reasons.

This commit did remove it from the Dockerfile of the docker-mender-convert container.
So all is good

Ah, nice!
Once BeagleBone conversion works well inside docker container (WIP), we should probably update this doc to use it?

Once BeagleBone conversion works well inside docker container (WIP), we should probably update this doc to use it?

That should also work now with @apodogrocki latest changes. Today at least I did convert beagle images using the docker-mender-convert.

It is time to create a Mender Hub post for Beagle as well.

Yep and yep! Let's follow up on that once we can get around to it. It's been on my list for a while, and now seems like good timing to "clean" this up.

Should this be back-ported to 1.7?
The 1.7 docs are using version 1.0.0 of mender-convert so I would assume not unless we also update the version which includes the changes done.

No, as you mention mender-convert 1.0.0 was released with 1.7, so let's release 1.1.0 with 2.0 and make it available there. :)


Bump minimum TimescaleDB version to 2.6.1

Description
2.6.1 delivered fixes which allow the promscale extension to be
uninstalled.
Merge requirements
Please take into account the following non-code changes that you may need to make with your PR:

[x] CHANGELOG entry for user-facing changes
[ ] Updated the relevant documentation

Do we need any corresponding changes on the extension side to make? Maybe in the tests?


Dependencies prevent building apps with Vapor, Perfect, Kitura, etc.

Some of the aws-sdk-swift-core dependencies (Prorsum, I believe) are causing build issues when trying to build a Swift project with aws-sdk-swift and server-side frameworks such as Vapor, Perfect, Kitura, etc.  When building with Vapor, I see this error:

'HTTP' /Volumes/Untitled/SwiftDev/MyApp/.build/checkouts/http.git-9159899851620770205: error: multiple targets named 'Performance'

With Perfect, I get multiple error messages that look like this:

duplicate symbol _http_parser_pause in:
/Volumes/Untitled/SwiftDev/MyApp/.build/x86_64-apple-macosx10.10/debug/CHTTPParser.build/http_parser.c.o
/Volumes/Untitled/SwiftDev/MyApp/.build/x86_64-apple-macosx10.10/debug/PerfectCHTTPParser.build/http_parser.c.o
duplicate symbol _http_errno_name in:
/Volumes/Untitled/SwiftDev/MyApp/.build/x86_64-apple-macosx10.10/debug/CHTTPParser.build/http_parser.c.o
/Volumes/Untitled/SwiftDev/MyApp/.build/x86_64-apple-macosx10.10/debug/PerfectCHTTPParser.build/http_parser.c.o
ld: 4110 duplicate symbols for architecture x86_64
:0: error: link command failed with exit code 1 (use -v to see invocation)
error: terminated(1): /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-build-tool -f /Volumes/Untitled/SwiftDev/MyApp/.build/debug.yaml main output:

With Kitura, the error looks like this:

'CHTTPParser' /Volumes/Untitled/SwiftDev/MyApp/.build/checkouts/CHTTPParser.git-5348291456210268902: error: multiple targets named 'CHTTPParser'

These dependency issues effectively make it impossible to build server-side apps using these frameworks and aws-sdk-swift.

Hi @sdnakhla
There is a branch in development that will compile when added to a vapor project. It needs more testing if you could please try it and provide feedback for your use cases.
This version removes the Prorsum dependency and uses Swift-Nio (synchronous for now) to interface with aws services.
.package(url: "https://github.com/GetBlast/aws-sdk-swift-core.git", .branch("swift-nio"))

@sdnakhla that would be great thank you. I can make a branch of the dynamo module for you that sources core from the swift-nio version if that makes things easier for you?

@jonnymacs it should be easy enough for me to fork the DynamoDB repo and change the dependency to test.  I’ll let you know how it goes.

@sdnakhla were you ever to able test?
We have merged the upgrade to master and will tag v2 for release in the next week. Please let us know how it goes with your integration.

@sdnakhla I will close this issue. The sdk compiles with Vapor, and I would expect it to compile with kitura or perfect as well. Please open another issue if you have problems.


feat: make PhiAccrualFailureDetector configurable

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
This closes https://github.com/GreptimeTeam/greptimedb/issues/1738.
Although, PhiAccrualFailureDetector seems a deep internal struct. Perhaps we can evaluate if we want to config it in metasrv level.
Checklist

[ ]  I have written the necessary rustdoc comments.
[ ]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

@MichaelScofield @WenyXu @killme2008

@MichaelScofield Is there any pending task before this PR mergeable?

Left a comment, PTAL @tisonkun

@MichaelScofield Updated.


[Warp Launch Configuration] Unexpected behaviour, not launching configuration if it has custom title

Extension
https://www.raycast.com/joetannenbaum/warp-launch-configuration
Description
When selection an configuration from the list it takes name of file as title to lookup in warp

However a configuration can have different title, other than the file name:

Support for this pending
Steps To Reproduce
launch a configuration which has custom name

Current Behaviour
cannot find configuration in warp pallete
Expected Behaviour
launch configuration

Fix has been PR'ed: https://github.com/raycast/extensions/pull/5493

@raycastbot close this issue


Add Bgee to Expasy

In GitLab by @fbastian on Oct 29, 2015, 15:19
When we'll have a gene page and a search engine, we could add Bgee to Expasy.

In GitLab by @marcrr on Mar 14, 2016, 15:32
In a first step, do ugly adaptation of the autocompletion of gene search to display gene search results.
See with @smoretti for Sphinx and blacklisting of uninformative terms.

In GitLab by @vrechdelaval on May 1, 2019, 19:13
Bgee webapp, updated with the new gene search and page for expasy, is available for test at http://devbgee.unil.ch.
News will be updated later.
Currently, it requests rbioinfo for sphinx. I need to see with @smoretti how to have sphinx on devbgee and, for the production release, on bioinfo

In GitLab by @vrechdelaval on May 1, 2019, 19:14
assigned to @vrechdelaval

In GitLab by @vrechdelaval on May 21, 2019, 15:30
Released in production

In GitLab by @vrechdelaval on May 21, 2019, 15:30
closed


API for eduID app

This issue is imported from pivotal

API endpoints to publish next:

DELETE eduIdPerServiceProvider
UPDATE password (Peter Havekes - Feb 22, 2023)

https://github.com/OpenConext/OpenConext-myconext/commit/055e26be77a3bca04d5730f6174ac6d202f354ab (Okke Harsta - Feb 22, 2023)

API endpoints next up:

Download data
Delete account
/myconext/api/sp/service (delete serviceprovider) (Peter Havekes - Feb 23, 2023)

https://github.com/OpenConext/OpenConext-myconext/commit/5fb6766ab09609119d90481a8884a693fc74d428 (Okke Harsta - Feb 23, 2023)

Expose idps-metadata in mobile api

The APP needs to display the Displayname of the institution the account is linked to.
This can be done by:

Looking up the displayname of the IdP based upon the scope in idps-metadata.xml, and adding it to the linedaccounts object
expose an API-endpoint to allow fetching the list of IdP information from idps-metadata.xml (Peter Havekes - Mar 2, 2023)

https://github.com/OpenConext/OpenConext-myconext/commit/a4c965bd38d5be4eb54ed65dbfd1ccf32c39d7f6 (Okke Harsta - Mar 4, 2023)

https://login.test2.eduid.nl/myconext/api/mobile/swagger-ui/index.html#/user-controller/institutionNames (Okke Harsta - Mar 5, 2023)


UiTextfield border Style selected as none then there is no spacing between phone code and input phone number

Describe the bug
UiTextfield border Style selected as none then there is no spacing between phone code and input phone number.
To Reproduce
Steps to reproduce the behavior:

Go to Xcode Project and put UITextField on storyboard and set up border style none in IB or textfieldName.borderStyle = .none.
Add the FPN pods and run project.
see the error.

Expected behavior
It would be nice if there is space between phone code and phone number.
The issue arrises only when border style = none is selected.
Screenshots

Smartphone (please complete the following information):

Device: [Iphone 11 pro max]
OS: [e.g. iOS 13]
Version [e.g. 0.7.7]

FlagPhoneNumber (please complete the following information):

Version [e.g. 0.7.7]

Hey I had the same issue.. did this to fix it temp:
        textField.leftView?.translatesAutoresizingMaskIntoConstraints = false
        textField.leftView?.widthAnchor.constraint(equalToConstant: 110.0).isActive = true

apparently in iOS13 right/left views dimensions needs to be set via constraints.

Nope that didn't work for me @dustfire.

Temporarily fixed it by setting border style  to line and then hiding the borders using UIViews.

same


GraphQL override not working

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
7.6.26
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No.
Amplify Categories
storage, api
Amplify Commands
override, push
Describe the bug
The override file is not read as console logs are not printed to the screen during amplify push.
Expected behavior
Should read the override file and apply the overrides.
Reproduction steps

Create a graphQL API
Override the api
The override code:

import { AmplifyApiGraphQlResourceStackTemplate } from "@aws-amplify/cli-extensibility-helper";
import { ModelDirectiveStack } from "@aws-amplify/cli-extensibility-helper/lib/types/api/amplify-api-resource-stack-types";
import environment from "./overrideContext"; //? Generated from a pre-push hook

type Models =
  | "Task"
  | "Identity"
  | "User"
  | "Activity"
  | "Payment"
  | "Audit"
  | "Notification"
  | "Configuration";

export function override({ models }: AmplifyApiGraphQlResourceStackTemplate) {
  const { Task, Identity, User, Activity, Payment, Audit } = models as Partial<
    Record<Models, ModelDirectiveStack>
  >;

  if (environment === "usability") {
    prepareForExport(Task);
    prepareForExport(Identity);
    prepareForExport(User);
    prepareForExport(Activity);
    prepareForExport(Payment);
    prepareForExport(Audit);
  }
}

function prepareForExport(model?: ModelDirectiveStack) {
  if (model) {
    model.modelDDBTable.pointInTimeRecoverySpecification = {
      pointInTimeRecoveryEnabled: true,
    };
  }
}

GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information
No response

Hey @maxludovicohofer :wave: thanks for raising this! Unfortunately I was not able to reproduce by using a modified overrides file:
import { AmplifyApiGraphQlResourceStackTemplate } from '@aws-amplify/cli-extensibility-helper'
import { ModelDirectiveStack } from '@aws-amplify/cli-extensibility-helper/lib/types/api/amplify-api-resource-stack-types'
// import environment from './overrideContext' //? Generated from a pre-push hook

type Models = 'Todo'

export function override({ models }: AmplifyApiGraphQlResourceStackTemplate) {
  const { Todo } = models as Partial<Record<Models, ModelDirectiveStack>>

  // if (environment === 'usability') {
  prepareForExport(Todo)
  // }
}

function prepareForExport(model?: ModelDirectiveStack) {
  if (model) {
    model.modelDDBTable.pointInTimeRecoverySpecification = {
      pointInTimeRecoveryEnabled: true,
    }
  }
}

Can you confirm whether the environment check is working as expected?


clientv3: disable client side grpc log

Fix https://github.com/coreos/etcd/issues/4811.

I ran some simple code of put and get using clientv3 and confirmed that this disables grpc logs when I killed one of the members.
Before
2016/03/26 21:09:30 transport: http2Client.notifyError got notified that the client transport was broken EOF.
2016/03/26 21:09:31 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:2379: getsockopt: connection refused"; Reconnecting to "localhost:2379"
2016/03/26 21:09:32 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:2379: getsockopt: connection refused"; Reconnecting to "localhost:2379"
2016/03/26 21:09:32 grpc: Conn.transportMonitor exits due to: grpc: timed out trying to connect
2016/03/26 21:09:33 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:2379: getsockopt: connection refused"; Reconnecting to "localhost:2379"
2016/03/26 21:09:35 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:2379: getsockopt: connection refused"; Reconnecting to "localhost:2379"

After
[None]

@xiang90 Made the logger configurable. PTAL. Thanks.

@xiang90 Fixed up and added godoc. PTAL. Thanks!

lgtm

thanks


make onclose event cancelable

by returning true from onclose user supplied event, you can prevent close from occurring.
example
var foo_are_you_sure = function () {
    var sure = window.confirm("are you sure to close window?")
    if (!sure) {
        return true;
    }
}

new WinBox("Theme: Modern", {
    onclose: foo_are_you_sure
});

also, method close now supports option to force close without firing user supplied onclose.

Hello, thanks a lot for the contribution. There is an issue with your pull request. You have committed a lot of code style changes which was automatically applied by your editor auto style configuration. Please consider to just commit the changes you want to take. I would like to keep your name in the commit history, so I will merge your PR and apply the code style changes back, to keep the history clean.

Hi , thanks for the merge. I will try to keep the style next time.
On Sat, May 1, 2021 at 11:43 AM Thomas Wilkerling @.***>
wrote:

Merged #9 https://github.com/nextapps-de/winbox/pull/9 into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nextapps-de/winbox/pull/9#event-4673281131, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADZP6DUA5C5LHORD3HXKPQTTLO5LLANCNFSM434FQXBQ
.

I made some little changes in how to apply "force" state. This flag is now delegated to the assigned callback handler as a first parameter. This way the user is also able to apply additional logic when force closing a window.
https://github.com/nextapps-de/winbox#callbacks

Please allow me to note that there are 2 non related additions:

cancelable onclose -> which is fine
"force" close parameter or state -> which is a dubious design decision.
because it is up to the onclose callback to decide if the window shall
close or not anyway.