Add parameters to define sensor priorities

As discussed in the dev call on 14.11.2018 with @dagar and @davids5
Issue we want to solve
A developer or experienced user should be able to easily choose which instance of gyro/accel/mag should be used as the primary instance. Some flight controllers have vibration isolated and hard-mounted sensors at the same time and therefore we should allow the user to chose which sensor to use primarily.
Suggestion
We could add parameters for each sensor instance that define the priority of that sensor. Initially, those parameters could be set to reflect the current priority scheme. However, one would be able to change priorities via those parameters.
Example:
CAL_GYRO0_PRIO: ...
CAL_GYRO1_PRIO:...

Would the priority set (and reset) during calibration?


add toc in readme.md for better navigation

Added a table of contents in readme to navigate things better.

@adarsh-jha-dev - thanks for your contribution!   👍


Fix hardcoded AF_INET for IPv6 address handling

Providing fix for hardcoded AF_INET argument in parseIP function call for "destinations". This leads to issues with IPv6 addresses thus they handled as IPv4.
This patch provides a solution equivalent as its is used for "services":
https://github.com/herrwagner/libnetwork/blob/217bc0e7296b474afb5318b609dee673e819a00e/ipvs/netlink.go#L323-L334

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "2289-fix-ipv6-hardcode" git@github.com:herrwagner/libnetwork.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.


Modify copy fsaverage

[ ] extract inner skull surface as surf-file for visualisation
[ ] decimate inner_skull BEM: why 10242 points?!
[ ] copy mri/T1.mgz to allow volumetric visualisation too

Not even WIP yet! Excuse me...

I also almost changed "can not" to "cannot", too :)
Might be worth waiting for #4971 to land to avoid merge conflicts


Iteration order of VDom::nodes

In what order does VDom::nodes() iterate through all tags of VDom? I think ordering has to be specified in document.

I've just published a new release that specifies the order of the nodes in VDom::nodes().
Given the following HTML:

    Hello
    World

The order would be: [div#a, div#b, span, "Hello", span, "World"].
(Prior to this release, the parser would insert the innermost children first, so the order used to look more like: ["Hello", "World", span, span, div#b, div#a])
Does this answer your question?

Closing due to inactivity. Feel free to reopen if there's still something that needs to be done here.


correct calc_rational_iv inputs with rate and dividend

after perusing the formulas in section 1 and 2 of the "Let's be rational" paper, it seems the formulas would use the undiscounted price (first paragraph of Section 1), and would use the forward price (formula 2.1 and variable naming in code).
Also took into account the continuous dividend q.
With these changes, calc_rational_iv now gives comparable results to the black_scholes crate for me.
Thank you to the contributors for the work you put in this crate! Loved that "let's be rational" is available in Rust! 🙏

Nice, thanks for your work on this.  I figured a conversion needed done there but have been too lazy to work on it.


two signalhubs not working?

Try using two signalhubs on two different domains (e.g., signalhub.mafintosh.com and signalhub.dat.land). The swarms seem to connect to each other briefly and then disconnect.

https://signalhub.dat.land/ has a broken HTTPS cert. Maybe that's the reason? Running signalhubs tests with two hubs does work for me. You could try https://signalhub.perguth.de:65300 as a second hub.


eml attachments encoding regression

I found out that my change wasn't enough #1106
Mail::Body.encoded calls get_best_encoding twice (correct transfer encoding should already be set for example in identify_and_set_transfer_encoding)
in my opinion, the encoding availability check shouldn't be called here.
the problem is in my case get_best_encoding('7bit') without available encodings always chooses base64 which is not compatible with eml file, but it encodes the content.
So as a result I have an eml attachment which claims to have
Content-Transfer-Encoding: 7bit (which is correct)
but in reality the content is encoded in base64 (which is forbidden), that makes the attachment unreadable

ping @jeremy
could you take a look? This is still broken in 2.7.0.

Hey all! When trying to send an email with "eml" attachment:
mail.attachments["original.eml"] = mailer_message.raw_message

I'm getting this exception when using mail 2.7.0:
NoMethodError: undefined method `can_transport?' for nil:NilClass
from /home/.../gems/mail-2.7.0/lib/mail/encodings/transfer_encoding.rb:49:in `block in renegotiate'

This used to work for mail < 2.7.0, and now only happens for "eml" attachments. Is this related to changes/fixes from this PR?

Hard to say, @saks. What's the rest of the backtrace? Could you paste in a complete example to reproduce?

Sure:
NoMethodError: undefined method `can_transport?' for nil:NilClass
    mail (2.7.0) lib/mail/encodings/transfer_encoding.rb:49:in `block in renegotiate'
    mail (2.7.0) lib/mail/encodings/transfer_encoding.rb:47:in `select'
    mail (2.7.0) lib/mail/encodings/transfer_encoding.rb:47:in `renegotiate'
    mail (2.7.0) lib/mail/encodings/transfer_encoding.rb:42:in `negotiate'
    mail (2.7.0) lib/mail/body.rb:143:in `negotiate_best_encoding'
    mail (2.7.0) lib/mail/body.rb:157:in `encoded'
    mail (2.7.0) lib/mail/message.rb:1833:in `encoded'
    mail (2.7.0) lib/mail/body.rb:153:in `block in encoded'
    mail (2.7.0) lib/mail/parts_list.rb:31:in `block in collect'
    /home/.../.rvm/rubies/ruby-2.3.5/lib/ruby/2.3.0/delegate.rb:341:in `each'
    /home/.../.rvm/rubies/ruby-2.3.5/lib/ruby/2.3.0/delegate.rb:341:in `block in delegating_block'
    mail (2.7.0) lib/mail/parts_list.rb:31:in `collect'
    mail (2.7.0) lib/mail/body.rb:153:in `encoded'
    mail (2.7.0) lib/mail/message.rb:1833:in `encoded'
    actionmailer (5.1.2) lib/action_mailer/base.rb:573:in `set_payload_for_mail'
    actionmailer (5.1.2) lib/action_mailer/base.rb:557:in `block in deliver_mail'
    activesupport (5.1.2) lib/active_support/notifications.rb:166:in `block in instrument'
    activesupport (5.1.2) lib/active_support/notifications/instrumenter.rb:21:in `instrument'
    activesupport (5.1.2) lib/active_support/notifications.rb:166:in `instrument'
    actionmailer (5.1.2) lib/action_mailer/base.rb:556:in `deliver_mail'
    mail (2.7.0) lib/mail/message.rb:260:in `deliver'
    /home/.../.rvm/rubies/ruby-2.3.5/lib/ruby/2.3.0/delegate.rb:83:in `method_missing'
    app/mailers/my_mailer.rb:109:in `send_my_email'

I can prepare PR with spec later on today if necessary.

@jeremy I rebased it against 2.7 branch

As this seems to be the only thing which is keeping version 2.7.1 from being complete and ready to build, is there anything I can help with to get this PR merged?

Backported to 2-7-stable @ dead487e02f592d9058fd07deedcde39b569d18d


[question] How to disable autoformatting

I honestly feel like I must be blind, but I really can't find the option.
How does one disable formatting on save automatically for this plugin?

Example in this issue: #81
      require("typescript-tools").setup {
        on_attach = function(client)
          client.server_capabilities.documentFormattingProvider = false
          client.server_capabilities.documentRangeFormattingProvider = false
        end,
      }

Will it disable only typescript-tools to manage lsp formatting?
I wan't to use https://github.com/stevearc/conform.nvim or prettier_d with none-ls instead of typescript-tools for formatting.


Kdd2018 workshop

Submit initial README with installation and setup instructions for the workshop.

Looking into why the CLA check failed.


ci: Make the cargo-deny job faster

Codecov Report

Merging #40 (4616d6d) into main (92c7b26) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #40   +/-   ##
=======================================
  Coverage   88.99%   88.99%
=======================================
  Files           7        7
  Lines         509      509
=======================================
  Hits          453      453
  Misses         56       56


Don't trigger create-microbosh from paas-cf

We don't (yet) want this pipeline to be triggered on every commit to
git. This is different to all the other pipelines and therefore causes
surprise.

works


[pt] Add translations for content/pt/docs/concepts/instrumentation/_index.md

Add localization for content/pt/docs/concepts/instrumentation/_index.md

@open-telemetry/docs-maintainers appreciate if someone can merge this PR


AMI doc needs step-by-step instructions

People can find this doc when looking for instructions; it should supply them or give a pointer to them.

There is a line in https://github.com/weaveworks/scope/blob/master/site/installing.md#installing-scope-on-amazon-ecs saying:

For step by step instructions on how to configure the stack, see: Install Weave to AWS with One-Click

however the link goes to https://www.weave.works/deploy-weave-aws-cloudformation-template/ which redirects to https://www.weave.works/docs/tutorials/kubernetes/launch-aws-cloudformation/ which is not about ECS

Looks like this is a much better page https://www.weave.works/docs/cloud/latest/install/ec2-no-kubernetes/

Updated to use that link in ca9351553c341ccb1e189a90f8127ba2000b8b11
but I still don't think that covers the original issue - there should be step-by-step instructions just for the AMI


2021-12-28 equity dashboard chart data update

Equity dashboard stats updates in this PR may be reviewed on staging - here.
After reviewing, if all looks well, approve and merge this Pull Request.
If there are issues with the data:

Note concerns or issues here by commenting on this PR
Work with Triston directly to resolve data issues
Alert the COVID19 site team in Slack (in the Equity page channel)

ran too early.


LocalFolder binaries are seeked in "\published"

Example:
crank.exe  --config C:\git\benchmarks\scenarios\plaintext.benchmarks.yml --application.source.project "" --application.source.repository "" --application.source.localFolder C:\git\benchmarks\src\Benchmarks\bin\Release\net7.0\win-x64\publish\app --application.executable Benchmarks.exe --scenario plaintext --profile aspnet-perf-win

Crank will try to execute "...\abcde\published" where the app is actually contained in "...\abcde".

I noticed recently, perhaps in my analysis, directories whose name contained published/published which smelled, but I didn't pursue that...

I think this issue is unrelated to the other issue, this is caused by empty strings not being forwarded correctly when it is a value of a dynamic argument.
On this line of code: https://github.com/dotnet/crank/blob/7114609ae6d36d50d8bbdf0dafc4035eebd9253a/src/Microsoft.Crank.Controller/Program.cs#L279-L282
When the arguments are being passed back in again, empty string arguments are not surrounded by quotes and so instead what happens is that --application.source.project "" --application.source.repository "" is being turned into --application.source.project --application.source.repository, so the project value is not set to empty and thus it thinks that the output is in the "published" directory.

/cc @trylek


ResinOS 2 images have no size shown

Oops, wrong project. Moved to the UI: https://github.com/resin-io/resin-ui/issues/633


pytest historic database does not hadles exception on UI if user creates a project with name of database already available in MySQL

Steps to reproduce:

Navigate to pytesthistoric (localhost:5000)
Click in getting started
Click on new project
Enter Name as test and description as test.
Click Create

Console Logs :

(1007, "Can't create database 'test'; database exists")

Good catch :), I have to look into it. Until fix requesting users to not add duplicates in Create Project page

That's cool Shiva !
I found this issue thinking of using this for demo (poc ) mindset where user tries to create projects by the name of "test".


Bugfix and performance improvements

Hi @mhart,
I found a bug in the library and got a bit carried away when fixing it, this PR contains the following (each in their own commit, so can be reviewed separately if needed)

Tests for common features
A bugfix (moving the SharedArrayBuffer inside the function call, because if it was not done, the function would always return the result of the first call)
Support for multiple arguments in async functions (with a test)
New argument for timeouts (with a test)
Use a single worker for a given async function (big performance improvement, see below)
Add a benchmark

Reusing the worker across calls is a significant performance improvement as you can see:
Load time
┌─────────┬────────────────────────┬───────────┬────────────────────┬──────────┬─────────┐
│ (index) │       Task Name        │  ops/sec  │ Average Time (ns)  │  Margin  │ Samples │
├─────────┼────────────────────────┼───────────┼────────────────────┼──────────┼─────────┤
│    0    │        'native'        │ '818 234' │ 1222.1439571458939 │ '±3.69%' │  81824  │
│    1    │     'sync-threads'     │ '927 568' │ 1078.087884336715  │ '±0.94%' │  92757  │
│    2    │ 'sync-threads (1.0.1)' │ '902 893' │ 1107.5497360136544 │ '±2.00%' │  90290  │
│    3    │       'synckit'        │ '958 314' │ 1043.4987350162614 │ '±2.21%' │  95832  │
└─────────┴────────────────────────┴───────────┴────────────────────┴──────────┴─────────┘
Execution time
┌─────────┬────────────────────────┬───────────┬────────────────────┬───────────┬─────────┐
│ (index) │       Task Name        │  ops/sec  │ Average Time (ns)  │  Margin   │ Samples │
├─────────┼────────────────────────┼───────────┼────────────────────┼───────────┼─────────┤
│    0    │        'native'        │ '127 639' │ 7834.536944837339  │ '±3.20%'  │  12764  │
│    1    │     'sync-threads'     │ '10 695'  │  93495.3008379255  │ '±7.74%'  │  1071   │
│    2    │ 'sync-threads (1.0.1)' │   '881'   │ 1134772.9650776037 │ '±49.95%' │   89    │
│    3    │       'synckit'        │  '1 789'  │<PHONE_NUMBER>989817  │ '±22.36%' │   179   │
└─────────┴────────────────────────┴───────────┴────────────────────┴───────────┴─────────┘
Total time
┌─────────┬────────────────────────┬──────────┬────────────────────┬───────────┬─────────┐
│ (index) │       Task Name        │ ops/sec  │ Average Time (ns)  │  Margin   │ Samples │
├─────────┼────────────────────────┼──────────┼────────────────────┼───────────┼─────────┤
│    0    │        'native'        │ '73 668' │ 13574.320538260483 │ '±10.58%' │  7367   │
│    1    │     'sync-threads'     │ '2 169'  │<PHONE_NUMBER>951494  │ '±7.17%'  │   217   │
│    2    │ 'sync-threads (1.0.1)' │ '1 228'  │<PHONE_NUMBER>413193  │ '±58.56%' │   123   │
│    3    │       'synckit'        │  '761'   │ 1313029.3481143904 │ '±41.65%' │   81    │
└─────────┴────────────────────────┴──────────┴────────────────────┴───────────┴─────────┘

These tests were run today on my own MacBook Air m2.
I did not push the test for sync-threads (1.0.1) as it's just to illustrate the point.

@onigoetz Thanks for showing me the impressive performance improvement! Do you think is there anything we can change to bring better performance for synckit? It is slower in your benchmark because:

It does a lot of extra things than sync-threads, for example
worker path resolution to determine whether it should be considered as commonjs or ESM instead
first-class TypeScript support
first-class yarn pnpm support
It does not use v8 for serialization/deserialization, maybe we can try this approach to improve synckit?

Hi, yes indeed it must be possible to bring these things to synckit as well.
The reason I am interested in bringing this PR to this package is the package size; sync-threads is 2-3kB, no dependencies. Whereas synckit is 1MB when installed with all its dependencies.

The reason I am interested in bringing this PR to this package is the package size; sync-threads is 2-3kB, no dependencies. Whereas synckit is 1MB when installed with all its dependencies.

Indeed, that's because what I mentioned above

It does a lot of extra things than sync-threads

It's much more powerful. And well maintained.
Do you think what can I do for speeding up for synckit, or a PR would be very appreciated.

It's much more powerful. And well maintained.

Indeed, I see that it covers a lot of edge cases. Great work there :)

I'm up for the challenge and would happily make a PR to synckit.
Though I have to admit that if possible I would also like to make a PR to remove @pkgr/utils because it brings a lot of dependencies.

Awesome, thanks for this @onigoetz ! As you can tell, I like my libraries nice and lean, so I'll take a while to go through the changes just to ensure it's not adding too much complexity – but your explanations of the changes sound totally reasonable, so it gets a +1 from me so far. Thanks again

Though I have to admit that if possible I would also like to make a PR to remove @pkgr/utils because it brings a lot of dependencies.

Sure, this can be done with a separate PR, or if you think that's the cause of performance impact, Feel free to combine them together.

@onigoetz After https://github.com/un-ts/synckit/releases/tag/v0.8.8, synckit is much more slimmer now! I tried to bundle it with esbuild --minify, the output file is about 6KB.

I made some more changes to this PR:

Use a single SharedArrayBuffer (this was a bug initially, but I found a way to get it to work fine)
Add an option to automatically grow the buffer if possible (it is a feature of Node.js 20)
Change the library to run benchmarks for a library that's more precise. also includes memory usage

The incredibly high memory usage of sync-threads 1.0.1 skewed the initial benchmark results, here are the updated numbers which run sync-threads 1.0.1 last to not consume all the memory before (as it would use disk swapping for memory operations, thus making them appear slower than they are)
[initial] Memory usage 58.671104MB (+58.671104MB)
Load time
[after native] Memory usage 97.222656MB (+38.551552MB)
[after sync-threads (PR #3)] Memory usage 90.60352MB (-6.619136MB)
[after synckit] Memory usage 116.588544MB (+25.985024MB)
[after synckit (PR #154)] Memory usage 123.748352MB (+7.159808MB)
[after sync-threads (1.0.1)] Memory usage 125.894656MB (+2.146304MB)

Fastest is native
┌─────────┬────────────────────────┬─────────────┬───────────┬─────────┐
│ (index) │       Task Name        │   ops/sec   │  Margin   │ Samples │
├─────────┼────────────────────────┼─────────────┼───────────┼─────────┤
│    0    │        'native'        │ '5,284,942' │ '± 0.19%' │   97    │
│    1    │       'synckit'        │ '5,033,051' │ '± 0.55%' │   96    │
│    2    │ 'sync-threads (PR #3)' │ '4,935,344' │ '± 0.28%' │   100   │
│    3    │  'synckit (PR #154)'   │ '4,927,874' │ '± 0.26%' │   99    │
│    4    │ 'sync-threads (1.0.1)' │ '4,628,793' │ '± 0.23%' │   97    │
└─────────┴────────────────────────┴─────────────┴───────────┴─────────┘
Execution time
[after native] Memory usage 136.23296MB (+10.338304MB)
[after sync-threads (PR #3)] Memory usage 159.82592MB (+23.59296MB)
[after synckit] Memory usage 204.111872MB (+44.285952MB)
[after synckit (PR #154)] Memory usage 233.783296MB (+29.671424MB)
[after sync-threads (1.0.1)] Memory usage 6784.581632MB (+6550.798336MB)

Fastest is native
┌─────────┬────────────────────────┬───────────┬────────────┬─────────┐
│ (index) │       Task Name        │  ops/sec  │   Margin   │ Samples │
├─────────┼────────────────────────┼───────────┼────────────┼─────────┤
│    0    │        'native'        │ '150,795' │ '± 0.30%'  │   100   │
│    1    │  'synckit (PR #154)'   │ '15,963'  │ '± 0.35%'  │   91    │
│    2    │ 'sync-threads (PR #3)' │ '15,672'  │ '± 0.29%'  │   96    │
│    3    │       'synckit'        │ '15,672'  │ '± 0.35%'  │   99    │
│    4    │ 'sync-threads (1.0.1)' │   '397'   │ '± 37.23%' │   11    │
└─────────┴────────────────────────┴───────────┴────────────┴─────────┘
Total time
[after native] Memory usage 5044.764672MB (-1739.81696MB)
[after sync-threads (PR #3)] Memory usage 3800.530944MB (-1244.233728MB)
[after synckit] Memory usage 3411.935232MB (-388.595712MB)
[after synckit (PR #154)] Memory usage 3412.164608MB (+0.229376MB)
[after sync-threads (1.0.1)] Memory usage 2892.824576MB (-519.340032MB)

Fastest is native
┌─────────┬────────────────────────┬──────────┬────────────┬─────────┐
│ (index) │       Task Name        │ ops/sec  │   Margin   │ Samples │
├─────────┼────────────────────────┼──────────┼────────────┼─────────┤
│    0    │        'native'        │ '42,395' │ '± 11.08%' │   53    │
│    1    │ 'sync-threads (PR #3)' │ '1,903'  │ '± 8.96%'  │   53    │
│    2    │  'synckit (PR #154)'   │ '1,414'  │ '± 8.92%'  │   57    │
│    3    │       'synckit'        │ '1,357'  │ '± 8.14%'  │   60    │
│    4    │ 'sync-threads (1.0.1)' │  '233'   │ '± 8.27%'  │   32    │
└─────────┴────────────────────────┴──────────┴────────────┴─────────┘

@onigoetz Awesome work again, and we can add benchmarks on CI like
https://github.com/un-ts/synckit/blob/68ae0604aeefd9514bb50d61afd9e04a8f7084be/.github/workflows/ci.yml#L41-L43
It would show different benchmark results on different platforms and node versions.
See also https://github.com/un-ts/synckit/actions/runs/7405983872/job/20149716081#step:6:8
┌───────────┬────────────┬──────────────┬───────────────────┬─────────────┬────────────────┬───────────┬────────────────┐
│  (index)  │  synckit   │ sync-threads │ perf sync-threads │   deasync   │  perf deasync  │  native   │  perf native   │
├───────────┼────────────┼──────────────┼───────────────────┼─────────────┼────────────────┼───────────┼────────────────┤
│ loadTime  │ '13.02ms'  │   '1.98ms'   │  '6.56x slower'   │  '1.72ms'   │ '7.58x slower' │ '22.53ms' │ '1.73x faster' │
│  runTime  │ '189.66ms' │ '22844.97ms' │ '120.45x faster'  │ '1593.37ms' │ '8.40x faster' │ '27.19ms' │ '6.97x slower' │
│ totalTime │ '202.68ms' │ '22846.96ms' │ '112.72x faster'  │ '1595.09ms' │ '7.87x faster' │ '49.72ms' │ '4.08x slower' │
└───────────┴────────────┴──────────────┴───────────────────┴─────────────┴────────────────┴───────────┴────────────────┘


[TypeSpec Validation] Add "specification/common-types" to triggers to validate all specs

Fixed by https://github.com/Azure/azure-rest-api-specs/pull/25945


Upgrade version of @compodoc/compodoc used

"Fix" for Unable to run storybook on M1 MacBook #6.
I say "fix" because relatively new to all of this, and I'm not sure if I've done a proper job 😄 I would appreciate any feedback 🙏

@jonniebigodes, just following up on this 😄

@ebh Sorry for the delayed response, but I've been working on some other parts of the documentation, and as such, this pr was left unattended. With that out of the way, I wanted to also let you know that I've updated the template to the latest Storybook package versions and also is now working with Angular 13, and with that, the issue is now solved. Tested it out on a couple of boxes with various versions of Node and it's working without this issue.
Hope you understand and have a great week.
Stay safe.

All good @jonniebigodes, thanks for getting back to me 😄


add title and description of project to home page

Make the navbar look good

Completed!

Created on figma then implemented


feat(protocol-designer): add ability to clear staging slots directly

Overview
This PR adds the ability to clear staging area slots directly by interacting with a column 4 slot.
In order to preserve the functionality where pressing "done" does NOT delete labware in a slot of the labware is the same labware when users opened the toolbox, i added a parameter to the handleClear function to conditionally clear existing labware.
closes RQA-3626
Test Plan and Hands on Testing
Mess around with the deck setup tools. Add staging areas, add adapters, labware, modules, etc. Clear the slot both from the toolbox and the slot overflow menu. Just generally try to break it.
Changelog

add ability to clear staging slots directly

Review requests
See test plan
Risk assessment
Low

if you zoom into the 3rd column staging area and press "clear", it incorrectly zooms out. we want it to stay zoomed in since the slot turns into a standard slot
https://github.com/user-attachments/assets/4f579214-bcb5-438a-83bd-cde1aa0bbd28

Also, labware in 4th column slot is incorrectly deleted
https://github.com/user-attachments/assets/4431af25-9ac1-4f8e-9576-63aab2a9a9e9

uh oh thanks @jerader ill fix

@jerader i think the second issue is not a regression, it's in edge currently. but i think i fixed it and this is desired behavior now?


hard to config on Ubuntu

Hi, I am new on all of these. when I run ./setup.sh on Ubuntu, it would not easy.
I have figured out that the apache user name is www-data, the apache2 is located at /etc/apache2, the apache config file is located at /etc/apache2/apache2.conf
But, I still can not make it work. if i open <IP_ADDRESS>/nodepoint      , i could only see a list of files in the nodepoint folder on browser.
i appreciate you sharing this project. I really need your help.
Thank you.

Check the troubleshooting section in the manual. If you're seeing a list of files then it's likely you do not have AllowOverride set in your Apache config, or it's set to None. Locate it and change it to All.

On Jun 7, 2016, at 01:33, leo yu<EMAIL_ADDRESS>wrote:
Hi, I am new on all of these. when I run ./setup.sh on Ubuntu, it would not easy.
I have figured out that the apache user name is www-data, the apache2 is located at /etc/apache2, the apache config file is located at /etc/apache2/apache2.conf
But, I still can not make it work. if i open <IP_ADDRESS>/nodepoint , i could only see a list of files in the nodepoint folder on browser.
i appreciate you sharing this project. I really need your help.
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

hi, I still can not make it work. AllowOverride is set as All in config. still just a list of files: http://<IP_ADDRESS>/nodepoint/

Your symlink should point to the www subfolder, not to nodepoint. Also make sure NodePoint has write access to the files:
chown -R www-data /path/to/nodepoint
This should be done by the setup script but somehow it didn't on your system.

On Jun 7, 2016, at 12:09, leo yu<EMAIL_ADDRESS>wrote:
hi, I still can not make it work. AllowOverride is set as All in config. still just a list of files: http://<IP_ADDRESS>/nodepoint/
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

i tried, i think i failed.
Could you provide some other ways to finish this step? such as download the source code and use node command to start the project?

Node runs JavaScript applets. That has nothing to do with this.
What failed? Can you run other CGIs on your server? Did you do the symlink?

i really do not know much. do you mind login into my server and help me figure it out? my email<EMAIL_ADDRESS>i will reply you my server info

I ran it on a brand new Ubuntu system and ran into just 2 issues. The Apache restart didn't go through since Apache has a different service name on Ubuntu versus RHEL/CentOS, and CGI is apparently not enabled by default over there. I modified the setup script to take care of these particularities. Please open a new issue with specific errors if you run into more problems.


Is there a list of supported plugins for G++?

Well, the title pretty much says everything.

We have a list, but nothing is on it. The original project has a list, and we haven't broken compatibility with any plugins, so you can use that.


Monitor and continue data ship from mysql database to es

Please post all product and debugging questions on our forum. Your questions will reach our wider community members there, and if we confirm that there is a bug, then we can open a new issue here.
For all general issues, please provide the following details for fast resolution:
bin/logstash -f logstash.cof
This command is doing job  but getting terminated and I have to run again. Please tell me if their is a way that can keep running this command so whenever data change in mysql can get updated to es automatically.

Version: logstash 6.4.0

Operating System: Ubantu

Config File (if you have sensitive info, please remove it):
input {
jdbc {
jdbc_connection_string => "jdbc:postgresql://localhost:5432/mydb"
jdbc_user => "postgres"
jdbc_validate_connection => true
jdbc_driver_library => "/path/to/postgresql-9.4-1201.jdbc41.jar"
jdbc_driver_class => "org.postgresql.Driver"
statement => "SELECT * from logstable"
}
}
output {
elasticsearch {
hosts => "<>"
index => "contacts"
document_type => "contact"
document_id => "%{iid}"
}
}

Sample Data:
NA

Steps to Reproduce:

run below cammand
bin/logstash -f logstash.cof
This command is doing job  but getting terminated and I have to run again. Please tell me if their is a way that can keep running this command so whenever data change in mysql can get updated to es automatically.

Use the schedule setting. The docs explain it well enough.
Closing. Please use the forum if you have further questions.


Prop className did not match when using createX

🐛 Bug Report
Prop className did not match. Server, When using I'm using createX
import styled, {
  createX,
  compose,
  space,
  backgroundColor,
} from '@xstyled/styled-components';

const x = createX(compose(space, backgroundColor));

const CustomBox = styled(x.div)`
  background: red;
  color: #fff;
`;

const Box = (props) => {
  return <CustomBox {...props} />;
};

export default Box;

To Reproduce
once you start editing code error will show in the console
https://github.com/ProxN/xstyled-custom-x

Will be solved in v3

Please reopen it if you have problem in v3.


Remove all controllable short options for CLI

Currently, the following options are supported by the CLI:
-V, --version              output the version number
--no-color                 disables color output
-b, --base-url <url>       specify base URL to use for all relative URLs in SVG
-f, --filename <filename>  specify filename the for PNG output when processing STDIN
--height <value>           specify height for PNG
--scale <value>            specify scale to apply to dimensions [1]
--width <value>            specify width for PNG
-h, --help                 output usage information

To be future-proof and avoid confusion when adding more options (see #14), we should remove all short options within our control. This includes the following:

-b
-f

These will still be accessible via their long options (i.e. --base-url and --filename respectively), however, the short options will no longer work.
Obviously, this will be a breaking change.

This change has been implemented in 81eed21 and will be included in the 0.3.0 release.


withDefault confuses props types

It seems withDefault partially modifies the Volar types of props, in particular it can narrow an any type in the parent.
To work around a bug in current Vue release, I have defined my data prop as any but it has a default value like so:
const props = withDefaults(
  defineProps<{ data?: any }>(),
  { data: () => [] },
);

Now if I hover props in TS, I can clearly see that the returned value still has { data: any }:

Yet, in templates Volar thinks it's data: never[] | undefined, which is clearly influenced by the default value []:

This is optional prop so it can be undefined in parent attr. It should be never[] in itself's template.

TS props.data and the type of component in template are in disagreement: one says any, the other never[] | undefined, so something is not coherent.
I would argue it's the latter that is wrong:
I declared data as any... or any | undefined if you wish but that's still basically any.
The default value must be assignment compatible with the base type, and it should remove undefined from the returned props, as there's a default now.
So it should be any | undefined minus the undefined -> just any.
And that actually works.
The component property should be just what I said in defineProps, regardless of the withDefault, since undefined is an acceptable binding -> it should stick to any | undefined... or just any as it's a special type.
From what I observe, the component property seems to be the type of withDefault or undefined. In this case, the type of [], aka never[], or undefined.
But that's narrowing the declared property type.
If I declare x?: A | B | C and give a default of B, the component property must not be B | undefined it should stick to A | B | C | undefined.

Thanks for the shared, but this is defineComponent behavior not volar.
const Component = defineComponent({
	props: {
		data: {
			type: {} as PropType<any>,
			required: false,
			default: () => [],
		}
	}
});
type Data = InstanceType<typeof Component>['$props']['data']; // never[] | undefined

ah sorry... I'm never sure if the typing problems come from Vue types or Volar 😞
I'm gonna move this issue to vue-next.

Never mind, thank you for being active. :)


As the blockchain platform provider,we need to provide users some sample blockchain applications

Fabric Chaincodes

[ ] erc721 @0xff-dev @Lanture1064
https://github.com/bestchains/fabric-builder-k8s/tree/main/samples

closed as we will track this in another repo
BTW... probably we will devlope a application store


Add automated testing using travis-ci.

Hopefully this means other contributions can be accepted more easily. See results for this build here https://travis-ci.org/Connorhd/double-bag-ftps/builds/365819663

Nice! @bnix any objection to merging this in?


Update Checker.java

With this change, the compiler will enforce catching of the checked exception. Without it, I find that it does not enforce this.

Codecov Report

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

@@            Coverage Diff            @@
##             master      #22   +/-   ##
=========================================
  Coverage     98.52%   98.52%
  Complexity       85       85
=========================================
  Files            12       12
  Lines           136      136
  Branches          1        1
=========================================
  Hits            134      134
  Misses            2        2

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/pl/touk/throwing/Checker.java
80% <ø> (ø)
3 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

Right, great idea! thanks :)

Thanks. My first ever pull request :-)
On 1 December 2017 at 13:19, Grzegorz Piwowarek<EMAIL_ADDRESS>wrote:

Right, great idea! thanks :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pivovarit/ThrowingFunction/pull/22#issuecomment-348492665,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFlLWwsGaqN03q2r-5xUORK7KtPm-WKTks5s7_zWgaJpZM4QyTqz
.


Dev15 build is broken

Due to change of C++ toolset version to 141 and b/c MSBuild binary is now copied locally.

https://github.com/Microsoft/RTVS/commit/6adedb75ca0a75415372055ac5d7392ace8c0d6f

Still have problems in C++
2016-09-13T21:32:06.3782208Z Build started 9/13/2016 2:32:06 PM.
2016-09-13T21:32:06.3938460Z Project "F:\A\_work\24\s\private\src\build.proj" on node 1 (Build target(s)).
2016-09-13T21:32:06.3938460Z Project "F:\A\_work\24\s\private\src\build.proj" (1) is building "F:\A\_work\24\s\public\src\build.proj" (2) on node 1 (Build target(s)).
2016-09-13T21:32:06.3938460Z Build:
2016-09-13T21:32:06.3938460Z   SolutionProperties: Configuration=release;Platform=any cpu;GenerateAssemblyVersionInfo=true;Year=2016;Date=0913;Time=1432;SolutionDir=F:\A\_work\24\s\public\src\;BinDirectory=F:\A\_work\24\s\bin\15.0\;ObjDirectory=F:\A\_work\24\s\obj\;LibDirectory=F:\A\_work\24\s\public\lib\;WIX=D:\Users\DLAB\.nuget\packages\VS.Tools.Wix\1.0.15100801\;WixToolPath=D:\Users\DLAB\.nuget\packages\VS.Tools.Wix\1.0.15100801\bin\sdk\;WixTargetsPath=D:\Users\DLAB\.nuget\packages\VS.Tools.Wix\1.0.15100801\bin\wix.targets;WixCATargetsPath=D:\Users\DLAB\.nuget\packages\VS.Tools.Wix\1.0.15100801\bin\sdk\wix.ca.targets
2016-09-13T21:32:06.3938460Z   SetupProperties: Configuration=release;Platform=x86;GenerateAssemblyVersionInfo=true;SuppressValidation=true;Year=2016;Date=0913;Time=1432;WIX=D:\Users\DLAB\.nuget\packages\VS.Tools.Wix\1.0.15100801\;BinDirectory=F:\A\_work\24\s\bin\15.0\;ObjDirectory=F:\A\_work\24\s\obj\;WixInstallPath=D:\Users\DLAB\.nuget\packages\VS.Tools.Wix\1.0.15100801\bin\;WixToolPath=D:\Users\DLAB\.nuget\packages\VS.Tools.Wix\1.0.15100801\bin\;WixSdkPath=D:\Users\DLAB\.nuget\packages\VS.Tools.Wix\1.0.15100801\bin\sdk\;WixTargetsPath=D:\Users\DLAB\.nuget\packages\VS.Tools.Wix\1.0.15100801\bin\wix.targets;WixCATargetsPath=D:\Users\DLAB\.nuget\packages\VS.Tools.Wix\1.0.15100801\bin\sdk\wix.ca.targets
2016-09-13T21:32:06.4250958Z Project "F:\A\_work\24\s\public\src\build.proj" (2) is building "F:\A\_work\24\s\public\src\R.sln" (3) on node 1 (Build target(s)).
2016-09-13T21:32:06.4250958Z ValidateSolutionConfiguration:
2016-09-13T21:32:06.4250958Z   Building solution configuration "release|any cpu".
2016-09-13T21:32:06.4250958Z ValidateProjects:
2016-09-13T21:32:06.4250958Z   The project "Setup" is not selected for building in solution configuration "Release|Any CPU".
2016-09-13T21:32:06.4250958Z   The project "SetupRHost" is not selected for building in solution configuration "Release|Any CPU".
2016-09-13T21:32:06.4250958Z   The project "SetupRemote" is not selected for building in solution configuration "Release|Any CPU".
2016-09-13T21:32:06.5188454Z The target "_ConvertPdbFiles" listed in a BeforeTargets attribute at "D:\Program Files (x86)\MSBuild\14.0\Microsoft.Common.targets\ImportAfter\Xamarin.Common.targets (34,37)" does not exist in the project, and will be ignored.
2016-09-13T21:32:06.5188454Z The target "_CollectPdbFiles" listed in an AfterTargets attribute at "D:\Program Files (x86)\MSBuild\14.0\Microsoft.Common.targets\ImportAfter\Xamarin.Common.targets (34,70)" does not exist in the project, and will be ignored.
2016-09-13T21:32:06.5188454Z The target "_CollectMdbFiles" listed in a BeforeTargets attribute at "D:\Program Files (x86)\MSBuild\14.0\Microsoft.Common.targets\ImportAfter\Xamarin.Common.targets (40,38)" does not exist in the project, and will be ignored.
2016-09-13T21:32:06.5188454Z The target "_CopyMdbFiles" listed in an AfterTargets attribute at "D:\Program Files (x86)\MSBuild\14.0\Microsoft.Common.targets\ImportAfter\Xamarin.Common.targets (40,71)" does not exist in the project, and will be ignored.
2016-09-13T21:32:06.5657235Z ##[error]D:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Platform.targets(57,5): Error MSB8020: The build tools for v141 (Platform Toolset = 'v141') cannot be found. To build using the v141 build tools, please install v141 build tools.  Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution".
2016-09-13T21:32:06.5657235Z Project "F:\A\_work\24\s\public\src\R.sln" (3) is building "F:\A\_work\24\s\public\src\Package\Impl\Microsoft.VisualStudio.R.Package.csproj.metaproj" (4) on node 1 (default targets).
2016-09-13T21:32:06.5657235Z Project "F:\A\_work\24\s\public\src\Package\Impl\Microsoft.VisualStudio.R.Package.csproj.metaproj" (4) is building "F:\A\_work\24\s\public\src\Host\Process\src\Microsoft.R.Host.vcxproj" (5) on node 1 (default targets).
2016-09-13T21:32:06.5657235Z D:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Platform.targets(57,5): error MSB8020: The build tools for v141 (Platform Toolset = 'v141') cannot be found. To build using the v141 build tools, please install v141 build tools.  Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution". [F:\A\_work\24\s\public\src\Host\Process\src\Microsoft.R.Host.vcxproj]
2016-09-13T21:32:06.5657235Z Done Building Project "F:\A\_work\24\s\public\src\Host\Process\src\Microsoft.R.Host.vcxproj" (default targets) -- FAILED.
2016-09-13T21:32:06.5657235Z Done Building Project "F:\A\_work\24\s\public\src\Package\Impl\Microsoft.VisualStudio.R.Package.csproj.metaproj" (default targets) -- FAILED.
2016-09-13T21:32:06.5657235Z Done Building Project "F:\A\_work\24\s\public\src\R.sln" (Build target(s)) -- FAILED.
2016-09-13T21:32:06.5657235Z Done Building Project "F:\A\_work\24\s\public\src\build.proj" (Build target(s)) -- FAILED.
2016-09-13T21:32:06.5657235Z Done Building Project "F:\A\_work\24\s\private\src\build.proj" (Build target(s)) -- FAILED.
2016-09-13T21:32:06.5657235Z Build FAILED.

The C++ toolset inside our host .vcxproj is set to v141 when building for Dev15:
  <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'" Label="Configuration">
    <ConfigurationType>Application</ConfigurationType>
    <UseDebugLibraries>true</UseDebugLibraries>
    <PlatformToolset Condition="'$(VisualStudioVersion)'=='14.0'">v140</PlatformToolset>
    <PlatformToolset Condition="'$(VisualStudioVersion)'=='15.0'">v141</PlatformToolset>
    <CharacterSet>Unicode</CharacterSet>
  </PropertyGroup>

Which is correct and builds fine locally. Preview 5 has 141 toolset. It looks like at the lab machine Dev15 is Preview 4.

2016-09-20T23:00:28.0490730Z ##[error]public\src\Package\Impl\Microsoft.VisualStudio.R.Package.csproj(1424,5): Error MSB4062: The "XamlRuleToCode" task could not be loaded from the assembly D:\Users\DLAB\.nuget\packages\\Microsoft.VisualStudio.ProjectSystem.SDK.Tools\15.0.183-pre\build\net451\Microsoft.VisualStudio.ProjectSystem.Sdk.Tasks.dll. Could not load file or assembly 'file:///D:\Users\DLAB\.nuget\packages\Microsoft.VisualStudio.ProjectSystem.SDK.Tools\15.0.183-pre\build\net451\Microsoft.VisualStudio.ProjectSystem.Sdk.Tasks.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.

Updated to Preview5 SDK, will see what happens in the lab

Preview5 changed C++ toolset to v141. Third party libraries are unaware of the new version just yet. This means we either have to build from sources or set up separate build for the host and continue using Dev14. There is an option in Dev15 to use old toolset, but it is not quite working yet.

https://github.com/Microsoft/RTVS/commit/c09a8152f250386e597505fe22aca019d7d46861

OK, this is working now


Interactive docstrings

With this PR, almost every tactic in library/init/meta/interactive has  a docstring. I added the missing ones, and revised the existing ones to make them more uniform. Comments and corrections are welcome.
The docstrings are duplicated verbatim in the reference manual: https://leanprover.github.io/reference/tactics.html. I will do my best to keep these synchronized.

@kha thanks for reviewing the PR.
@avigad I will merge after issues are fixed.

@Kha Thanks for the very careful review!
I implemented all the corrections, but there is one I am not sure about. The docstring for fapply now reads "Similar to the apply tactic, but does not reorder goals." If this is correct, you can merge. If not, let me know, and I will fix it.


Metrics: Keep default promhttp.Handler

coverage: 78.111% (-0.08%) from 78.193%
when pulling 2d8a9a58f2cc1f3dd62047926066583a1cbdaa9e on dissoupov
into cd394e5b01c8f1461df54a8be3cb6f29bebbf48d on main.


blinking cursor color

Is your feature request related to a problem? Please describe.
blinking cursor color is not very nice
Describe the solution you'd like
change blinking cursor color

Is there any way to do it ? Can I help somehow to add it in case it is not available?

In v4 the cursor colour can be customised via CSS using --jp-vim-cursor-color variable. By default it is set to #7e7:
https://github.com/jupyterlab-contrib/jupyterlab-vim/blob/2078dc0ad8be24225da67cac8bf954a8e31e66fc/style/base.css#L20-L22


drop support for Python 3.7

According to https://github.com/pytorch/pytorch/issues/80513#issuecomment-1396166181, core will drop support for 3.7 with the upcoming torch==2.0.0 release. We should do the same.
cc @seemethere

We have some failing 3.7 jobs that we have no influence over. They are generated here from https://github.com/pytorch/vision/blob/93df9a50885d0345e31bba691576c83d5cee7737/.github/workflows/build-wheels-linux.yml#L12. Thus, this PR is blocked by pytorch/test-infra#1416.

pytorch/test-infra#1416 was closed in favor of pytorch/test-infra#1475. IIUC, this was done since PyTorch core tests stable binaries as well: https://github.com/pytorch/test-infra/pull/1416#issuecomment-1402786799. I'm fairly certain we don't so we should be good to remove everywhere. cc @atalman and @malfet to be sure.

CI failures seem unrelated. I'll deal with them today.


Freeze bars

Adds Freeze bars for NPCs and Players.
If the target is frozen/immune this will be shown regardless of whether HP bars are shown.
The freeze bar displayed in a light blue color and immunity in orange.

Uses #574

I will update the timer tomorrow

I like the gifs

Closing as this is very old PR now and has a lot of merge conflicts, reopen if you want to re-implement it.


'Run selection/line in python interactive window' - not working for VS Code

Bug: Notebook Editor, Interactive Window, Editor cells
Steps to cause the bug to occur

Select code and run using Shift+Enter or 'Run selection/line in python interactive window' with right click.

Actual behavior

If one line is selected - it runs the code correctly.
If more than one line is selected - nothing happens.

Expected behavior
That the code will run.
Solution
Solution found at: https://stackoverflow.com/questions/59678010/vs-code-run-selection-line-in-python-interactive-window-not-working-at-all
Your Jupyter and/or Python environment
Please provide as much info as you readily know

Jupyter server running:                       Local
Extension version:                               2020.1.57204
VS Code version:                                1.41
Setting python.jediEnabled:               true | false
Python and/or Anaconda version:     3.7.4
OS:                                                     Windows
Virtual environment:                          virtualenv

Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer

Dupe of #9437


arch: riscv: add an option for empty spurious interrupt handler

Add the possibility to disable fault handling in spurious interrupt handler on RISCs and replacce it with an infinite loop.

Comliance checks fail because this PR references symbol CONFIG_NRFE, that was added in https://github.com/masz-nordic/zephyr/pull/1 , but is not rebased on it.


EMFILE error - too many open files

Version
5.0.8
Environment info
Node.js v18.8.0
Ubuntu 20.04

Steps to reproduce

Use the default configuration of Vue
run the Tasks/serve

What is expected?
localhost:8080 can be accessed
What is actually happening?
The log shows "serve ended with error code 1"

$ vue-cli-service serve --mode development --dashboard
INFO  Starting development server...
[3%] setup (watch run)
[9%] setup (compilation ExportsInfoApiPlugin)
node:internal/errors:484
ErrorCaptureStackTrace(err);
^
Error: EMFILE: too many open files, watch '/home/user/Programming/Vue-Tutorial/vue_test'
at FSWatcher. (node:internal/fs/watchers:244:19)
at Object.watch (node:fs:2315:34)
at createFsWatchInstance (/home/user/Programming/Vue-Tutorial/vue_test/node_modules/chokidar/lib/nodefs-handler.js:119:15)
at setFsWatchListener (/home/user/Programming/Vue-Tutorial/vue_test/node_modules/chokidar/lib/nodefs-handler.js:166:15)
at NodeFsHandler._watchWithNodeFs (/home/user/Programming/Vue-Tutorial/vue_test/node_modules/chokidar/lib/nodefs-handler.js:331:14)
at NodeFsHandler._handleDir (/home/user/Programming/Vue-Tutorial/vue_test/node_modules/chokidar/lib/nodefs-handler.js:567:19)
at NodeFsHandler._addToNodeFs (/home/user/Programming/Vue-Tutorial/vue_test/node_modules/chokidar/lib/nodefs-handler.js:617:27)
at async /home/user/Programming/Vue-Tutorial/vue_test/node_modules/chokidar/index.js:451:21
at async Promise.all (index 0)
Emitted 'error' event on FSWatcher instance at:
at FSWatcher._handleError (/home/user/Programming/Vue-Tutorial/vue_test/node_modules/chokidar/index.js:647:10)
at NodeFsHandler._addToNodeFs (/home/user/Programming/Vue-Tutorial/vue_test/node_modules/chokidar/lib/nodefs-handler.js:645:18)
at async /home/user/Programming/Vue-Tutorial/vue_test/node_modules/chokidar/index.js:451:21
at async Promise.all (index 0) {
errno: -24,
syscall: 'watch',
code: 'EMFILE',
path: '/home/user/Programming/Vue-Tutorial/vue_test',
filename: '/home/user/Programming/Vue-Tutorial/vue_test'
}
Node.js v18.8.0
[10%] building (0/0 modules)
Total task duration: 1.66s

no idea?

no idea?

hello, Is there any solution?

same error here


The README's description of test_page setup in browser needs improvement

When I setup testem to run my on my test-runner.html page in a browser, I had to include more files than what is described in the README. The only file that the README says to include is with /testem.js, but this file doesn't work in the browser because it begins with #!/usr/bin/env node. Instead of /testem/js, I had to include /public/testem-client.js, and, since I'm using Mocha, I had to include /public/mocha-adapter.js for testem-client's initTestFrameworkHooks method to run properly.
The only thing the README mentions is Next, the test page you use needs to have the adapter code installed on them, as specified in the next section. However, adapters aren't mentioned in the next section, and it isn't really explained. I think there should be specific instructions for including the testem-client.js with the appropriate adapter in the README.
I opened this issue to verify that this is an actual issue. Once I hear your thoughts on this, I'll create a pull request with the improvements I'd like to see in the README.

+1
I am struggling with the same issue.
@jonesnc Thanks for explaining your solution, this was helpful.
I also would love to see the docs updated


Revert "Create v1beta1 manifests for vsphere provider (#930)"

This reverts commit 1f90618c94d61efd8cdd985dffd2c9cd57146040.
Issue #, if available:
Description of changes:
This is causing issues with upgrades/scaling because the vsphere username and password is not accessible by the controller, so it is filling up the values as empty strings, causing the capv integration to break. Will need to move the secrets back to a separate step or retrieve those values through the controller, but because that would require some rework on these changes, I will revert this for now.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


This article is missing thumbnail in Browse experience

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

ID: cd458c97-751a-2ea5-af06-771defec74f6
Version Independent ID: 1a69b107-54d5-b910-c7ea-011edc380dd6
Content: Clinical insights with Microsoft Cloud for Healthcare - Azure Example Scenarios
Content Source: docs/example-scenario/mch-health/medical-data-insights.yml
Service: architecture-center
Sub-service: example-scenario
GitHub Login: @dsk-2015
Microsoft Alias: pnp

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 413309

Fixed now, thanks!

Thumbnail is present as of this date. Thanks for reporting the issue.


Some JSON configuration parameters are strings, but could be integers

The following options are strings in the JSON configuration and are interpreted as signed and unsigned integers:

job_limit_per_collection_indexing_operation (unsigned int)
minimum_delay_time (int)
maximum_delay_time (int)

We should probably just accept an integer in the JSON. Please investigate whether this is possible. In particular, make sure job_limit_per_collection_indexing_operation won't overflow or underflow.

Consider adding units to the names as well (e.g. minimum_delay_time_in_seconds?)

we'd have to make sure old/existing strings are also honored, but superseded by the new/correct configs.

Consider adding units to the names as well (e.g. minimum_delay_time_in_seconds?)

Unless we are still considering doing this?

Let's create a new issue for the renaming of config settings. That way, the PRs addressing this issue can be merged.

ok , I support that. Will make the new issue.

The following options are strings in the JSON configuration and are interpreted as signed and unsigned integers:

job_limit_per_collection_indexing_operation (unsigned int)
minimum_delay_time (int)
maximum_delay_time (int)

We should probably just accept an integer in the JSON. Please investigate whether this is possible. In particular, make sure job_limit_per_collection_indexing_operation won't overflow or underflow.

#114 is the new issue for this concern.

I have checked the boxes. Leaving to @d-w-moore to close if done.

Hmm, I don't seem to have a close option...

And what about now? :)

Yes, thanks! Closing....


Updating gh-pages documentation, syncing with README.md

@tariqislam Looks good! Thanks for syncing slate docs with Readme changes. :shipit:


Feature #10 display name

https://github.com/admin-shell-io/questions-and-answers/issues/10
Update Question "How is the relation between idShort, shortName and preferredName for a submodel element and the related concept description?"
Update question considering the introduction of displayName in V3.0RC01 of part 1.

The Task Force prefers to have two seperate answers: one for idShort and one for displayName.

The Task Force prefers to have two seperate answers: one for idShort and one for displayName.

Changes as agreed in Exmplary Modelling Meeting incorporated: ready to be merged into main branch from my point of view.


The PDF I generated cannot be edited by Adobe.

The pdf image I generated using jspdf has been reporting 110 errors when I opened it with Adobe.
I hope someone can give me a solution.

This issue is of no help to us if you don't describe what errors exactly Adobe reports. At least attach the PDF file so we can have a look at it ourselves.

When I create my report and export it as PDF I can open it in the web browser (Google Chrome) but if I try to open it in Acrobat Reader it says there is a Problem reading the document (110)
Reporte.pdf

@Amarok74 could be related to #2904


 I don't know if this is expected or not.
From my system...

The screenshots at http://mikebuss.com/2014/04/07/customizing-prezto/ make me think that I am expecting too much here!
Steps to Reproduce

Install zsh
Install prezto
prompt fire

Versions

Prezto commit:
b3c27bb
ZSH version:
5.3.1
OS information:
macOS 10.13.3 High Sierra

I just checked and it looks like the fire prompt is included with zsh itself and not as a part of prezto. We don't aim to override these prompts to add prezto features because, as you've noticed, some of them are (as you put it) a bit underwhelming. I'd recommend checking out some of the prompts we bundle with prezto:
agnoster
cloud
damoekri
giddie
kylewest
minimal
nicoulaj
paradox
peepcode
powerlevel9k
powerline
pure
skwp
smiley
sorin
steeef

There are a few additional themes in the prezto-contrib repo (including the one I'm using) if you don't find one in the main prezto that you like. My personal favorites from the main prezto repo are agnoster and sorin.
Thanks for filing the issue - I'm always happy to clear stuff like this up. If you have any questions about the supported prompts, definitely feel free to comment or file another issue here.

Thanks for the reply Belak, your explanation makes perfect sense. I've settled on steeef for the time being as being a cool mixture of uncomplicated but attractive form combined with a decent amount of useful functionality!

Update: I've found the Chauncey Garrett theme and now my terminal looks like this...
I think it looks quite neat embedded in VSCode's terminal window!


Finish Project

In this pull request I was able to :
-Get metric Data from API.
-Format Data in thunk to be easily used by the app.
-Create dynamic route that changes for each continent clicked.
-Implement searching tool to help users find their target easily.
-Add transitions and styling to meet the required template.
-Add tests .
-Change README to describe the project.

Just did, thanks for the feedback. I don't know why but it doesn't appear to be approved in my dashboard @MeqdamAlqudah

@yayoamigo, Your dashboard would be updated soon.

@yayoamigo, What does it show on your dashboard?

@yayoamigo, What does it show on your dashboard?

@yayoamigo, kindly check your dashboard now and let me know if it has changed with a screenshot of it as you did above. :pray:

@yayoamigo, kindly check your dashboard now and let me know if it has changed with a screenshot of it as you did above. :pray:

It works:) thanks

@yayoamigo, kindly check your dashboard now and let me know if it has changed with a screenshot of it as you did above. pray

It works:) thanks

Please, add the screenshot of it


Crash after write to service characteristic

I'm getting a crash on core 0 (the system core, not the one my code is running on) shortly after my other application writes to the NimBLE characteristic I've exposed. The crash happens every time.
This remains true even if I do not set any callback for the service characteristic. It does not happen unless I tell the other side to do a write to this characteristic.
If I do set a callback, usually the code in the onWrite() callback will finish running before it crashes. Occasionally it will not.
I can't debug on this one because I can't use a WROVER for this because I need the pins, and for some reason Espressif never released a properly debuggable WROOM development board to my knowledge.
I know writing to a characteristic usually doesn't crash because I do it elsewhere in my code (under a different runtime configuration) and it doesn't crash, but I can't figure out what the major difference is here.
This is a long shot, but what things could I be doing that would be causing a crash after the other app writes?
Guru Meditation Error: Core  0 panic'ed (StoreProhibited). Exception was unhandled.
Core 0 register dump:
PC      : 0x400d1d0e  PS      : 0x00060f30  A0      : 0x800d4929  A1      : 0x3ffc9ba0
A2      : 0x3ffca008  A3      : 0x3ffc9fc8  A4      : 0x3ffc9c84  A5      : 0x3ffc187c
A6      : 0x00000213  A7      : 0x00000000  A8      : 0x00000000  A9      : 0x00000000
A10     : 0x00000000  A11     : 0x00000430  A12     : 0xfeb70988  A13     : 0xfeb70988
A14     : 0x3ffc2af4  A15     : 0x00000000  SAR     : 0x0000001f  EXCCAUSE: 0x0000001d
EXCVADDR: 0x00000000  LBEG    : 0x400014fd  LEND    : 0x4000150d  LCOUNT  : 0xfffffff9

Hard to say without a decided backtrace but that core dump looks very much like something was trying to write to a nullptr.
The callbacks execute on core 0 if the originating source is from the BLE stack.

Thanks anyway. I figured you probably wouldn't be able to help here, but I am running out of ideas so I needed to ask at this point. I found when I remove both callbacks it works even though the server callbacks simply log - maybe logging from core 0 is doing it or something. I'm going to close this for now, based on the fact that when both callbacks are removed it's not crashing. I'm not sure why it's my callbacks, because they hardly do anything, but apparently it's my callbacks.


Restspectra Rendering is Very Slow

Would plyr::ldply be more efficient?

Here's what I've done. I'm not really sure if it's much quicker, it needs benchmarking on a half decent Linux machine that will do parallel computing.
# use plyr::ldply()
library(tidyverse)
library(itraxR)
library(microbenchmark)

read_function <- function(foldername, label, parameters = "CD166_19_(2020)_SETTINGS.dfl", datapos = 37, depthpos = 6){
  settings <- itrax_qspecsettings(parameters)
  channel_kev <- as.numeric(pull(settings[stringr::str_which(settings$key, pattern = "keV/channel"), "value"]))
  channel_offset <- as.numeric(pull(settings[stringr::str_which(settings$key, pattern = "energy offset"), "value"]))
  rm(settings)

  plyr::ldply(.data = unzip(zipfile = foldername, list = TRUE)$Name,
              .parallel = TRUE,
              .fun = function(x){itrax_spectra(unz(description = foldername, filename = x),
                                               plot = FALSE,
                                               datapos = datapos) %>%
                  as_tibble() %>%
                  mutate(position = read.table(unz(description = foldername, filename = x),
                                               skip = depthpos,
                                               nrows = 1,
                                               header = FALSE) %>%
                           pull("V2") %>%
                           round(digits = 2),
                         filename = str_split(x, pattern = "/") %>% sapply(., `[`, 2),
                         energy = (channel * channel_kev) + channel_offset,
                         label = label
                  )
              }
  )
}

spectral_join <- left_join(bind_rows(read_function(foldername = "CD166_19_S1/CD166_19_S1/XRF Data.zip", label = "S1"),
                                     read_function(foldername = "CD166_19_S2/CD166_19_S2/XRF Data.zip", label = "S2"),
                                     read_function(foldername = "CD166_19_S3/CD166_19_S3/XRF Data.zip", label = "S3")),
                           CD166_19_xrf %>%
                             select(depth, validity, filename, label) %>%
                             mutate(filename = filename %>%
                                      str_split(pattern = "\\\\") %>%
                                      sapply(., `[`, 7)),
                           by = c("filename", "label")
                           )

itrax_qspecsettings("CD166_19_(2020)_SETTINGS.dfl")[1,2]
channel_kev <- as.numeric(pull(settings[stringr::str_which(settings$key, pattern = "keV/channel"), "value"]))
channel_offset <- as.numeric(pull(settings[stringr::str_which(settings$key, pattern = "energy offset"), "value"]))
rm(settings)

spectral_join %>%
  ggplot(aes(x = energy, y = depth, fill = count)) +
  geom_raster() +
  scale_fill_gradient(name = "value",
                      trans = "pseudo_log",
                      low = "#132B43",
                      high = "#56B1F7",
                      labels = round) +
  scale_y_reverse() +
  ylab("position [mm]") +
  guides(fill = "none") +
  facet_grid(rows = vars(label),
             scales = "free_y",
             space = "free_y") +
  scale_x_continuous(name = "energy [k eV]",
                     sec.axis = sec_axis(trans = ~ (. / itrax_qspecsettings("CD166_19_(2020)_SETTINGS.dfl")[1,"value"]) - itrax_qspecsettings("CD166_19_(2020)_SETTINGS.dfl")[2,"value"],
                                         name = "channel [n]")
  )

It doesn't make a huge difference - 4.4 mins vs. 4.9 mins. Would be interesting to do some further benchmarking to see where the hold-up is, but for now, closed!


[UNDERTOW-1745] AccessLog must contain HTTP2 Upgrade requests too

https://issues.redhat.com/browse/UNDERTOW-1745

I already reviewed it @fl4via

thanks a lot, @ropalka !


So why pip install virtualenvwrapper is not enough?

Came here from Python Guide and don't get the problem that this package is trying to solve. Is there a log of command session that shows what is wrong with pip install virtualenvwrapper and right with this package?

The project description describes the goal pretty well — "One command to have a working virtualenv + virtualenvwrapper environment." If you're happy setting up your environment another way, then do that! :-)

@brainsik yea, but that command doesn't work on Windows, and it is not clear how that's different from pip install virtualenvwrapper.

Ah, sorry, this project doesn't currently support Windows.
It's quite different from pip install virtualenvwrapper since it's handling the case where there is no pip application. The idea is you can boot up a fresh *nix system, run the curl command, and start coding. No perquisites.

I thought that pip is installed with Python by default now, but perhaps it is only me. Still python is still needed for it to work, right?

pip only comes with recent versions of Python. All *nix systems ship with Python.

Ok. Now it is a little bit more clear than before.

But it could be explained in docs!
=)

Like sadly complicated could be a link to actual complicated session.

I added a "requirements" section at top (19a673dc783e6ff3dd3d951104043758498efc1a) before closing this. :-)
As for the "sadly complicated" part, I figured the list of different packages one might end up dealing with was scary enough. :-)


Smesher with many small proposals/rewards

Right now we let smeshers choose their own active sets and correspondingly their eligibility slots for proposals each epoch, which can result in a smesher submitting many proposals that each receive only a tiny reward. This appears to be happening with one smesher: 0x318cceb3df7174d42b582ffb4ccfd6ef6fbce4def8aee342c33e264ff78909f8
Example reward: https://explorer.spacemesh.io/rewards/6524347792abdc943072d99c
Coinbase: sm1qqqqqq8q9hxmhdqnktagjx7r65cf3vjfk79knvqnzy7yg
CC @dshulyak

we have minimal active weight parameter in the config to prevent such issue, we should raise it to known weight in current epoch. additionally there is pending issue of not rewarding atxs in hare that were received too late https://github.com/spacemeshos/go-spacemesh/issues/4942


Update software-restriction-policies.md

Clarify SRP is deprecated and should not be used.

@JasonGerend - Any chance we can get this clarification to SRP availability published soon?

@vinaypamnani-msft - Can you help get this PR unstuck?

#sign-off

@JasonGerend can you get this PR merged please?


feat: Extend connect-query-es to other Tanstack Query variants

Buf Slack link: https://bufbuild.slack.com/archives/CRZ680FUH/p1705412823808149
As discussed on Slack this issue shall track the initial addition of more than just the React variant of Tanstack Query. The v1 release already went ahead and decoupled the codegen from react but several more steps will be needed to fully implement compatibility with other variants. To quote @paul-sachs on the approach:

The first steps I’d recommend would be to create your own package that depends on connect-query and uses only the non-react specific apis (createConnectQueryKey and callUnaryMethod) and create your own version of useQuery based on that. As much as I think the apis are similar, I think the types (and use of suspense) are probably different. Once you figure out the common bits that your package needs, the first step for us would probably be to create a connect-query-core package that just exports those and we can work towards removing the unnecessary dependencies.

Quick update on this, I was able to test a very rough Svelte implementation and using stores and context works in a similar manner than the react implementation of connect-query-es works. Should I create a standalone package as reference first, e.g. as a repo under my name which you guys can then integrate with your own ideas or should I create a PR directly to this repo with my own try to integrate it?

Hey @MDr164, glad to hear it worked alright. I think the best way forward is to get your repo up and we can look to update our own repo to better support yours (by splitting out a core package). It may still make sense to integrate your repo back into this one eventually, but that depends on the amount of glue code.

Once that progresses a little further and everyone is happy with the state of the repo, we can go ahead and get the repo added to the connectrpc org so it's all equally discoverable. The specific process is here.

What is the status of this? We would like to participate as we use Svelte extensively and this might solve some boilerplate for us :)

I'll publish that PoC repo this week once I'm satisfied with amount of boilerplate aka keep it trimmed down a bit more. Side note: I built it around Svelte 4 so only with the Context and Store API

Hi, any news? Can we help?

Hi @MDr164 - would you like me to participate on this?

With V2 out (in RC) and the core package available, it should be pretty trivial to write adapters for different frameworks. Going to close this since there hasn't been any activity for a while.

I'll give it another shot. We redesigned large parts to use websockets instead for what I initially used connect-query so I never got around polishing up the hacky solution I had. But with the new core package I'll retry and see where that goes. :+1:


Limit behaviour and GLUE benchmark fixes

Replace islice with arrow_dataset select (bugfix)
Add type limit argument
Classification metrics require same target types (bugfix)
Tensor shape check to handle individual MNLI data failures

Tests params: --tasks cola,mnli,mnli_mismatched,mrpc,rte,qnli,qqp,stsb,sst,wnli --limit 500
Test evidence: (https://github.com/EleutherAI/lm_evaluation_harness/files/5613096/results.json.txt)

Can you explain why arrow_dataset is preferred to isslice?

Can you explain why arrow_dataset is preferred to isslice?

getDatasets() already returns an arrow_dataset object.  The problem is that the code that follows expects to be iterating through a DataSet not an islice.  So when it for instance addresses doc['label'] it fails

Great, thanks.


Start playing HLS without waiting for full segment download

Hello. I coded all my videos with ffmpeg option "-movflags faststart" (moov atom at the front of the file (Fast Start)). But when i start play the HLS m3u8 playlist, the video start playing only after segment fully downloaded ( https://i.imgur.com/tnrDwj3.png )
Is it possible not to wait for downloading full segment (when video has moov atom at the front of the file)?
Thank you!
P.s. sorry for my english

How many seconds are your segments duration ? maybe you could try reduce them, to decreased download duration of first fragment and therefore the playback start.

My fragments duration has 10 sec. Experimented with 5 sec, but in fullhd - downloading (starting time) is too long..
Is it possible to start playing without full segment downloading?


Microsoft.OperationalInsights/workspaces noisy properties Deletion

Describe the noise
Re-deploying the same workspaces resource always marks some of the properties for deletion
Resource type (i.e. Microsoft.Storage/storageAccounts)
Microsoft.OperationalInsights/workspaces
apiVersion (i.e. 2019-04-01)
2020-03-01-preview
Client (PowerShell, Azure CLI, or API)
Azure CLI 2.8.0
Relevant ARM Template code (we only need the resource object for the above resourceType and apiVersion, but if it's easier you can include the entire template
{
  "name": "myWorkspace",
  "type": "Microsoft.OperationalInsights/workspaces",
  "apiVersion": "2020-03-01-preview",
  "tags": {},
  "location": "northeurope",
  "properties": {
    "sku": {
      "name": "pergb2018"
    },
    "retentionInDays": "60"
  }
}

Expected response (i.e. "I expected no noise since the template has not been modified since the resources were deployed)
No noise as the template has not been modified
Current (noisy) response (either include a screenshot of the what-if output, or copy/paste the text)
~ Microsoft.OperationalInsights/workspaces/myWorkspace [2020-03-01-preview]
     - properties.createdDate:  "Wed, 01 Jul 2020 09:51:43 GMT"
     - properties.features:
         enableLogAccessUsingOnlyResourcePermissions: true
         legacy:                                      0
         searchVersion:                               1
     - properties.modifiedDate: "Wed, 08 Jul 2020 10:41:18 GMT"
     - properties.source:       "Azure"
     - properties.workspaceCapping:
         dailyQuotaGb: -1.0

[w32?]

This fix should be fully deployed.

@alex-frankel Just a small follow-up question regarding the fix/deployment. Are there any release/change logs when it comes to what-if fixes.
I've only seen the azure cli release notes here: https://github.com/MicrosoftDocs/azure-docs-cli/blob/master/docs-ref-conceptual/release-notes-azure-cli.md#tab/azure-cli but no new releases have been done there either.
(Using the newest azure cli I am still seeing this noise right now)

Latest noise reduction information is in #38
The what-if noise reduction is a service-side improvement, so it's not affected by what version of the CLI you are using (unless there is a CLI specific bug)
@fulder - are you seeing the exact same noise as before? It looks like this fix has not yet rolled out to the following regions:
UK South, Australia Southeast, Germany West Central, Canada East
So if you are hitting those regions, it's possible you will not see the fix. Otherwise @Xynoclafe can take a look.

@alex-frankel Thanks for the info!
I was running what-if with a template in North Europe region and still saw the exact same noise today.

I'll take another look at it.

@fulder @alex-frankel @Xynoclafe Sorry I think I made a mistake on the week number. The fix is actually in build w33 but not w32. It got deployed to Canary, but we'll have to wait for a few more days for it to hit other regions.

This fix should be deployed

I'm still seeing this issue in North Europe location today. :crying_cat_face:

@fulder thanks for reporting it. We found that some of the read-only properties are not declared in Swagger at all, so we need to make some additional changes on our side. The following noise should be fixed though:
- properties.workspaceCapping:
         dailyQuotaGb: -1.0

Is it still showing in your result?

- properties.workspaceCapping:
         dailyQuotaGb: -1.0

Is it still showing in your result?

This is not showing in my results anymore :) but the rest of the properties are still there.

- properties.workspaceCapping:
         dailyQuotaGb: -1.0

Is it still showing in your result?

This is not showing in my results anymore :) but the rest of the properties are still there.

I see. We just committed changes to fix the other properties. It will take another couple of weeks for them to be deployed. Sorry that we had to open this again :(

No problem :) One step closer to cleaning up this noise. Waiting for the deployment :+1:

[w40]

This fix should be deployed. Let us know if you are still seeing this issue.

Have verified I don't see this noise anymore. Works just fine. Thank you for this fix! :+1:


Auto Complete Menu doesn't appear in unsaved C/C++ file

VSCode Version:1.46.1
OS Version:Windows 10 x64

Problem
Whenever I work on a C/C++ file without saving it, autocomplete menu does not show any suggestions at all whereas it works if I work on a unsaved Python file..
If file is saved, it works fine in all types of files.
Suggestion
Make it work please !

Does this issue occur when all extensions are disabled?: Yes

/extcpp

/extC++
@JacksonKearl Maybe add /extcpp as an alias?

@gjsjohnmurray thanks, added extCpp. Case insensitivity probably makes sense in general so I'll add that with the next Action bump.


Fix Flake 8 linting

The bug that you found
Currently, All the python code fails flake 8 tests, It would be great if that could be fixed
Solution (Optional)
Run flake8 tests locally and fix the issues
Type of Issue

[ ] Code breaking bug
[ ] Documentation issue
[x] Other: Fix flake8 linting

Screenshot
Include any screenshots that can assist the person reviewing the PR.

The only ones that remain are line too long types:
backend/API/urls.py:8:80: E501 line too long (87 > 79 characters)
backend/API/urls.py:10:80: E501 line too long (82 > 79 characters)
backend/API/urls.py:11:80: E501 line too long (86 > 79 characters)
backend/API/urls.py:16:80: E501 line too long (90 > 79 characters)
backend/API/urls.py:17:80: E501 line too long (80 > 79 characters)
backend/API/urls.py:18:80: E501 line too long (80 > 79 characters)
backend/API/urls.py:20:80: E501 line too long (88 > 79 characters)
backend/API/urls.py:21:80: E501 line too long (104 > 79 characters)
backend/API/models.py:22:80: E501 line too long (97 > 79 characters)
backend/API/serializer.py:5:80: E501 line too long (110 > 79 characters)
backend/API/serializer.py:14:80: E501 line too long (91 > 79 characters)
backend/API/serializer.py:26:80: E501 line too long (82 > 79 characters)
backend/API/serializer.py:32:80: E501 line too long (80 > 79 characters)
backend/API/serializer.py:38:80: E501 line too long (81 > 79 characters)
backend/API/serializer.py:44:80: E501 line too long (96 > 79 characters)
backend/API/views.py:8:80: E501 line too long (90 > 79 characters)
backend/API/views.py:12:80: E501 line too long (89 > 79 characters)
backend/API/views.py:13:80: E501 line too long (87 > 79 characters)
backend/API/views.py:14:80: E501 line too long (121 > 79 characters)
backend/API/views.py:36:80: E501 line too long (93 > 79 characters)
backend/API/views.py:125:5: F841 local variable 'token' is assigned to but never used
backend/API/views.py:148:5: F841 local variable 'login' is assigned to but never used
backend/API/helper.py:7:80: E501 line too long (235 > 79 characters)
backend/API/helper.py:22:80: E501 line too long (84 > 79 characters)

Also, there are two unused variables in views.py so if you let me know I can remove them too! Thanks!

Hey @kishan3 I think you can comment them out for now, And also update the PR on how you performed flake 8 testing in your local


s390x architecture drone jobs

There might be issues with the specific commit this branch diverged from.    I will rebase and push to the pull request again.

@alandefreitas if this doesn't fail we should merge it

It does fail in the new architecture.

the tests try to link to coroutine, which doesn't work

(Peter)

Boost context supports s390 - will investigate.

@sdarwin it looks like boost.context needs you to explicitly add architecture=s390x for it to pick up the right assembly file. I could possibly hack something together, but I reckon it's better if you add that parameter the proper way.
https://github.com/boostorg/context/blob/5852b493554ba8be5459147abf226f57d6bfa74c/build/Jamfile.v2#L473

Oh, that's an issue in the build script of context - I'll create a PR.

@klemens-morgenstern nice work. Switching from clang-12 to clang-14 solved it. However the update to boostorg/context is still required, and they haven't merged it, so this pull request will still show errors.


Custom edges names

Summary 💡
Hello everyone, I'm new in Golang and I have started to use Ent framework.
Firstly, I have an existing database generated thanks Doctrine 2 for a web app and I want to code a service with Golang to implement this database.
So I have a specific field name in my database for a relation :  "table_1_id".
But Ent framework generate a name like this : "table_1_table_2"
I have search in the documentation and in git issue but I never found what I want to do.
Someone know how can I do that ?
Thank you in advance and have a good day.

Hey @FournyP, I think the edge.StorageKey should solve your problem here, right?
Please let me know if it does solve your problem and I can close this issue. Also, feel free to join our Slack channel.

Hey @a8m,
Exactly, edge.StorageKey solve the problem, thanks a lot for your answer
Have a good day


Improve zjquery error message when users uses tag as a selector.

See 2nd commit for more details. @showell FYI.

LGTM.  I will merge when the build passes, unless I forget.

Merged, thanks @amanagr!


[REQ] Evapotranspiration data source for Portugal

Evapotranspiration data for Portugal
https://api.ipma.pt/open-data/observation/climate/evapotranspiration/

thanks, added to the Wiki.


Stackfile interpolation breaks on foo-bar variables

Trying to use the following kind of variable name:
variables:
  web-path:
    type: string
    ....
services:
  wordpress:
    environment:
      KONTENA_LB_VIRTUAL_PATH: ${web-path}

Results in the following service configuration:
development/wordpress-red/wordpress:
  env:
    - KONTENA_LB_VIRTUAL_PATH=-path}

The variables should be validated to match the /\w+ used for interpolation, failing with an error otherwise.
Alternatively, the interpolation should be a bit smarter... leaving bits and pieces of the } hanging around looks ugly.

Something along the lines of /\$(\w|\{.+?\})/ might work better?

Perhaps /(\$\{?[^\s\]+}?)/

I would keep the (...|\{...\]}) structure to not leave unmatched braces.

Oh... and I still think this stack install/deploy should have just failed with an "no such variable 'web'" error :/


Fix formatting of changedSince date in CDC requests

The $formattedChangedSince sent with the CDC request placed the month (m) in the place of the minute (i).

@robmilward there will be a big release coming soon for PHP SDK. I have included the change on the release, however, the pull request cannot be merged now. Thanks for contribution.

Included. Thanks!


#105 Fix file paths to match package declarations

Commit 5839388 renamed org.moditect to org.kcctl throughout the whole
project, but the top level folder wasn't updated accordingly. Maven
build passes however many IDEs, including IntelliJ, would complain and
fail to compile with the following error:
"Package name 'org.kcctl.command' does not correspond to the file
path 'org.moditect.kcctl.command'."
Fixes #105

Whoops, good spot!

Applied, thx!


[MINOR] fix(gvfs): Extend sleep time in the testInternalCache unit test

What changes were proposed in this pull request?
Caffeine Cache's use of RemoveListener is not stable and may cause a single test to fail in some cases. Therefore, the waiting time in the single test is extended to ensure that the Cache is cleaned normally.

Hi @xloya can you please create an issue to track this?

Hi @xloya can you please create an issue to track this?

Done


Fix long name behavior

Ticket: []
Feature flag: n/a

Purpose

Summary of Changes

Screenshot(s)

Side Effects

QA Notes

@brianjgeiger PR updated. I've modified the FolderButton class so that it will show multi-line texts for long folder names. Might as well be consistent with the long file name behavior.


Add end-to-end tests

To catch stuff like client/server communication issues.
For example, while working on this, the tests would all pass, but then the client would panic decoding.

Implementation will probably involve firing up a client against a "mock server".

No longer a concern of Flux itself.


TN-2828-TN-2820-org-changes

v5 batch 12: https://jira.movember.com/browse/TN-2828
New org: https://jira.movember.com/browse/TN-2820

@ivan-c  I'll defer to you as to whether you want to bring this in Friday, or with Saturday's maintenance window.


Store timestamp in the log

Resolves #2731
So that the data can be accessed without needing the folder structure.

And then I have a question about L1045/1048:
let tier = this.format.toLowerCase().replace(/[^a-z0-9]+/g, '');

Shouldn't this just be toId(this.format)?

Can we remove some redundant data while we're at it?

A lot of fields in p1rating/p2rating are superfluous. The individual formatid's and entryids, for one.

That would be fine with me, but I'm not sure how to do it in a future-proofed way (say the colname in the db changes, then delete p1rating.formatid would throw an error, no?)

Or if you're worried about space, you could always just tackle #2733

You're cute when talking about languages you don't know.
There's not a single language for which it's impossible to delete a key from a map if you're not sure if the key exists. Every language at the very least has a "does this key exist?" function (except ObjC for some weird reason).
Anyway, delete p1rating.formatid won't throw if p1rating.formatid doesn't exist, it just silently fails.

@Zarel, as I said, I don't know how to do it in JS. I never said it wasn't possible to do it.
But let's identify the redundant keys:
That would be:

formatid
username (since it's encoded separately as p[n])
userid (since you can always toId(username)

And if we don't care about future-proofing, we can ditch

rpsigma
sigma

col1 (number of battles for the alt, even past the last reset) might be a useful, but seeing as how it's not documented, I'm fine with dropping it as well.
Does js have a "delete all" or do you just have to iterate?

Iterate.
I'm fine with all of the above, although keeping userid may be nice.


Describe different between tmLanguage in Visual Studio and Visual Studio Code

ITNOA
Many different between tmLanguage in Visual Studio and Visual Studio Code (for example supporting on firstLineMatch Why grammar does not highlight keyword ). I think it is very essential to describe all different in supporting features and concepts (for example I do not find that Visual Studio supported injection grammars or etc.)

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

ID: 02810ab3-cd5b-c837-b6b7-ab1090aa3577
Version Independent ID: b245aa2a-1fe8-5c7b-342b-ca9c7c0252c5
Content: Add editor support for other languages - Visual Studio (Windows)
Content Source: docs/ide/adding-visual-studio-editor-support-for-other-languages.md
Product: visual-studio-windows
Technology: vs-ide-general
GitHub Login: @TerryGLee
Microsoft Alias: tglee

@soroshsabz -- thank your for your feedback.  I have upvoted this tmlanguage issue:

https://developercommunity.visualstudio.com/t/Support-firstLineMatch-in-tmlanguage-for/10281813

It is impractical to describe every difference between Visual Studio and VS Code.
I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.

@WilliamAntonRohm I think every user need to know about all constraints about tmLanguage support in Visual Studio, for example some major feature like injection grammar or something else
@TerryGLee I think this issue is not close, but add comprehensive documentation about tmLanguage feature support by Visual Studio
thanks

@WilliamAntonRohm Do you can get me your note about my last note

I think every user need to know about all constraints about tmLanguage support in Visual Studio, for example some major feature like injection grammar or something else

and if you agree with me, please reopen this issue, and if you disagree with me, please give me your cause to better understant
I do not find any place to learn tmLanguage feature gap in Visual Studio and then I do not know how to write my own extension for supporting my new language
thanks

@soroshsabz -- thank you for your followup.  Your questions are outside the scope of our existing and planned documentation.  Please consider these resources:

Ask a question or find an answer on the Microsoft Q&A page for Visual Studio.
Report product issues to the engineering team via the Report a problem tool that appears both in the Visual Studio Installer and in the Visual Studio IDE.
Track product issues and engineering team responses in the Visual Studio Developer Community.

Thanks for response, but as I say before, Visual Studio 2022, does not support completely Syntax Highlight Guide, So I think Microsoft must writes document and describe the scope of support of TML


Connection error misleading

I encountered this error today while doing development work (see screenshot).
The filepath I was specifying for the source file was incorrect (one folder too many). The error that was returned had me confused for about five minutes until I figured this out out, particularly given that the very next command to list datasets in the Workspace showed the dataset I had just created.
It wasn't until I went into the the tower.nf GUI and saw the  Data field in an infinite spinning load attempt that I clued in where the problem lay.

Thanks for reporting.


Fix typo in FC status condition reason

Description
This pr fixes a typo in the ForeignCluster status condition reason

/test

/merge


flex-basis workaround

hello,
I'm making my grid system http://mosne.it/playground/mosne-flexbox/
and is working good! So first of all thank you!
I've found a workaround for supporting flex-basis: ie9 and ie10 need a specified width,
starting from ie11 it has to be max-width
.col-1-3{ flex: 0 0 33.333333333333%; max-width:33.333333333333%;}
.no-flexbox .col-1-3{ width:33.333333333333%;}.
I was wondering if it would be possible to integrate this in your polyfill walker
so i can make a smaller css. thank you

I am working on adding flex-basis support. The math was insane. Then I was swamped with work. I’m working on it this week.

flex-basis support has arrived in v2!


Error in elasticsearch filter of logstash: Failed to query elasticsearch for previous event.

Hello.
I have an index in kibana called poc1*, it contains fields of machineId and timestamp
I need to get from that index a maximum value of timestamp to a new index for each machineId (which is deviceId in sql).
It is working if I specify a certain machine (ma1). But when trying to join machineId to deviceId it fails with - Failed to query elasticsearch for previous event.
Any ideas? What am I doing wrong?

I think I need to ask a question on beats github.
Please close this question and ask on beats github.
https://github.com/elastic/beats

It's actually logstash

Ask the following
https://github.com/elastic/logstash

Please close

Moved to logstash


Windows Installer triggers Windows Install Warning (1.0.23)

Describe the bug
When running the installer, the "this might not be safe to run" image appears. (shown below)
To Reproduce
Steps to reproduce the behavior:

Go to https://github.com/benawad/dogehouse/releases/tag/v1.0.23
Download the installer EXE
Open it
See error

Expected behavior
No error was expected.
Screenshots

What device are you on?
Windows 10 Pro N (10.0.19042) Build 19042
Additional context
Might require to add a publisher certificate(?) somehow.

That was already mentioned in the docs, just click run anyway.

Duplicate of #1376


In-place scan and un-scan

Description
Adds new API for element-mutable collections that takes a closure that fuses element values and performs a scan (i.e. a progressive reduce) in-place.  The other new method performs the inverse operation, taking a closure that removes the contribution one element value plays on another.
Detailed Design
extension MutableCollection {
    /// Progressively replaces each element with the combination of its
    /// (post-mutation) predecessor and itself, using the given closure to
    /// generate the new values.
    public mutating func accumulate(via combine: (Element, Element) throws -> Element) rethrows

    /// Progressively replaces each element with the disassociation between its
    /// (pre-mutation) predecessor and itself, using the given closure to generate
    /// the new values.
    public mutating func disperse(via sever: (Element, Element) throws -> Element) rethrows
}

Documentation Plan
The methods, types, and the types' properties have block documents. There is also a guide file.
Test Plan
A test file is included.
Source Impact
It adds API.
Checklist

[x] I've added at least one test that validates that my change is working, if appropriate
[x] I've followed the code style of the rest of the project
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary

As has been discussed in this repo, a “scan” function is going to be named reductions, and there is active work in another PR to design and add that functionality.
In general, if you haven’t already, I recommend taking a look at the existing work and discussions that are ongoing. It’s helpful because you can get a sense of how to build on that work rather than duplicating it.

I used "scan" in the title because it's technically a term-of-art, so casuals reading the PR list would have more of an idea what's going on.
The PR with reductions returns a separate object for the results, while the functions here work in-place.  This adds a restriction that the seed/first-operand type for the closure must be the same as the element type.  I'm not sure the two could share code (without making a distinct result object and copying the results back in, of course).


Works popup window

Added JavaScript array to store all of the information for all projects. Implemented Js interaction, When the user clicks (or taps) the button to check project details, the popup with details about the project appears.

I was requesting if it could be possible we spend like 10min on zoom you
help me to know how I will implement project card on the right
On Thu, Sep 8, 2022 at 11:18 AM Shoira @.***> wrote:

@.**** commented on this pull request.
Hi team,
👍 This is good to make it this far, your project is really nice,
congratulations on the good work you have done so far.
First let me to point out:

Modal window works as expected ✔
You passed all the Linters! ✔
Data is retrieved dynamically ✔

Keep on coding, good job so far! 👏
There are some issues that you still need to work on to go to the next
project but you are almost there!
https://camo.githubusercontent.com/7a3175b24229512cc970aece8b2e2de8a06ce098a4f0ba2c4079f9a4f9152c29/68747470733a2f2f6d656469612e67697068792e636f6d2f6d656469612f644550476b6e5269456e6965632f67697068792e676966
Required Changes ♻

Please check the readme file, some sections look broken:

[image: Screenshot 2022-09-08 at 11 17 41]
https://user-images.githubusercontent.com/77038610/189072005-61a344c8-c7bb-443e-9b38-c038bab7d626.png
Check the comments under the review.
Cheers and Happy coding! 👏 👏 👏
Feel free to leave any questions or comments in the PR thread if something
is not 100% clear by mentioning my Github username.
Please, do not open a new Pull Request for re-reviews. You should use the
same Pull Request submitted for the first review, either valid or invalid
unless it is requested otherwise.
As described in the Code reviews limits policy
https://microverse.zendesk.com/hc/en-us/articles/1500004088561 you have a
limited number of reviews per project (check the exact number in your
Dashboard). If you think that the code review was not fair, you can request
a second opinion using this form https://airtable.com/shrQAqnBwek5a0O0s.
In index.html
https://github.com/tonnymuchui/Portfolio/pull/12#discussion_r965642734:

             onclick="window.location.href = 'https://github.com/tonnymuchui/Portfolio';"

           >

             See Project

           </button>

Multi-Post Stories

CANOPY

●   Back End Dev

●   2015

           Experimental content creation feature that allows users to add

           to an existing story over the course of a day without spamming

           their friends.

html

css

javaScript

         <button

           class="btn"

           onclick="window.location.href = 'https://github.com/tonnymuchui/Portfolio';"

         >

           See Project

         </button>

Facebook 360

CANOPY

●   Back End Dev

●   2015

           Exploring the future of media in Facebook's first Virtual

           Reality app; a place to discover and enjoy 360 photos and videos

           on Gear VR.

html

css

javaScript

         <button

           class="btn"

           onclick="window.location.href = 'https://github.com/tonnymuchui/Portfolio';"

         >

           See Project

         </button>

Uber Navigation

CANOPY

●   Back End Dev

●   2015

           A smart assistant to make driving more safe, efficient, and fun

           by unlocking your most expensive computer: your car.

html

css

javaScript

         <button

           class="btn"

           onclick="window.location.href = 'https://github.com/tonnymuchui/Portfolio';"

         >

           See Project

         </button>

After the recent changes, I can see that the structure of project
cards has been broken, please make sure that your layoput is same as
provided on Figma:

Your design Figma design
[image: Screenshot 2022-09-08 at 11 11 59]
https://user-images.githubusercontent.com/77038610/189070756-68f6605a-c1b4-44ce-9425-3773b2192960.png [image:
Screenshot 2022-09-08 at 11 10 16]
https://user-images.githubusercontent.com/77038610/189070347-814914e5-9f9b-4644-b607-d4309570c2b1.png
As you can see, project's text content should be on the left or on the
right depending on the flow. But in your case, it is always on the right
In js/script.js
https://github.com/tonnymuchui/Portfolio/pull/12#discussion_r965647042:

 'A daily selection of privately personalized reads; no accounts or sign-ups required.',

languages: ['html', 'css', 'javascript'],

},

+];

+const worksCard = cards.map(

(card, index) => `

+
+
+
+

${card.title}

Please add a little more space below the project title and date info:

Your design Figma design
[image: Screenshot 2022-09-08 at 11 15 43]
https://user-images.githubusercontent.com/77038610/189071607-c1af88f1-4053-4fd5-8d37-a892031628cd.png [image:
Screenshot 2022-09-08 at 11 15 26]
https://user-images.githubusercontent.com/77038610/189071539-83771dc8-b326-41bd-bafb-1d6bc1d1827d.png
—
Reply to this email directly, view it on GitHub
https://github.com/tonnymuchui/Portfolio/pull/12#pullrequestreview-1100288099,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJVSLTKHPSEST3DB3SIXPQLV5GOMDANCNFSM6AAAAAAQHM7KOM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Food Recipe Finder Project

I would like to add FoodRecipe Finder project . Please assign me under GSSOC'2024

@AmrutaJayanti Thank you for providing your insight but it is not required as of now