Kill Wordpress website

Once my Hugo website is fully functional and has an alias for each post in Wordpress, kill Wordpress website

fix aliases so no page/post from Wordpress site ends up as a 404
migrate all images to Imgur
get rid of \[
take screenshots of the old website before killing it

June 25, 2018

691 results: fvcproductions.files.wordpress.com
31 results: \[

Archive - Blog

https://fvcproductions.wordpress.com/blog/archive/

This is the only component left, all other pages have been aliased.
To-Do

[] https://fvcproductions.wordpress.com/2015/11/13/hrdevfest-talk/
[] https://fvcproductions.wordpress.com/2015/10/21/my-designlab-experience/
[] https://fvcproductions.wordpress.com/2015/08/30/fullstack-academy-reflections/
[] https://fvcproductions.wordpress.com/2015/08/20/readme-template-for-github/
[] https://fvcproductions.wordpress.com/2015/08/19/one-week-left-of-fullstack/
[] https://fvcproductions.wordpress.com/2015/08/05/web-dev-and-web-design-slides-fullstack-academy/
[] https://fvcproductions.wordpress.com/2015/07/25/fullstack-academy-week-6-review-week/
[] https://fvcproductions.wordpress.com/2015/07/11/fullstack-academy-week-5/
[] https://fvcproductions.wordpress.com/2015/07/03/fullstack-academy-week-4/
[] https://fvcproductions.wordpress.com/2015/06/26/fullstack-academy-week-3/
[] https://fvcproductions.wordpress.com/2015/06/20/fullstack-academy-week-2/
[] https://fvcproductions.wordpress.com/2015/06/13/first-week-at-fullstack-academy/
[] https://fvcproductions.wordpress.com/2015/06/04/fullstack-foundations-goldman-sachs/
[] https://fvcproductions.wordpress.com/2015/05/20/then-what-shall-we-code-for/
[] https://fvcproductions.wordpress.com/2015/05/20/bootcamp-me-attempting-to-crowd-source/
[] https://fvcproductions.wordpress.com/2015/05/17/fullstack-foundations-week-1/
[] https://fvcproductions.wordpress.com/2015/04/26/damehood-through-hollow-knight/
[] https://fvcproductions.wordpress.com/2015/04/23/ai-movies/
[] https://fvcproductions.wordpress.com/2015/04/20/full-of-them/
[] https://fvcproductions.wordpress.com/2015/04/18/sort-detective-solution/
[] https://fvcproductions.wordpress.com/2015/04/13/reset-launchpad-with-sorty/
[] https://fvcproductions.wordpress.com/2015/04/13/what-to-do-week-negative-8/
[] https://fvcproductions.wordpress.com/2015/04/11/auschwitz-a-doctors-eyewitness-account/
[] https://fvcproductions.wordpress.com/2015/04/08/lease-template/
[] https://fvcproductions.wordpress.com/2015/03/29/change-your-icons-yosemite/
[] https://fvcproductions.wordpress.com/2015/03/28/my-top-3-productivity-apps/
[] https://fvcproductions.wordpress.com/2015/03/12/jeopardy-template/
[] https://fvcproductions.wordpress.com/2015/02/24/that-tapia-conference/
[] https://fvcproductions.wordpress.com/2015/02/20/brief-thoughts-best-bootcamps-switchup/
[] https://fvcproductions.wordpress.com/2015/02/15/ted-2023/
[] https://fvcproductions.wordpress.com/2015/02/11/itunes-music-february-2015/
[] https://fvcproductions.wordpress.com/2015/02/01/adding-awesome-websites-to-your-chrome-app-launcher/
[] https://fvcproductions.wordpress.com/2015/01/30/adventures-with-aaai-2015/
[] https://fvcproductions.wordpress.com/2015/01/14/interview-maker-square/
[] https://fvcproductions.wordpress.com/2015/01/06/interview-coding-dojo/
[] https://fvcproductions.wordpress.com/2015/01/06/interview-devleague/
[] https://fvcproductions.wordpress.com/2015/01/06/interview-coding-house/
[] https://fvcproductions.wordpress.com/2015/01/06/interview-with-designation/
[] https://fvcproductions.wordpress.com/2015/01/05/interview-hack-reactor/
[] https://fvcproductions.wordpress.com/2015/01/05/prepare-for-coding-bootcamps/
[] https://fvcproductions.wordpress.com/2014/12/29/aaai-2015-month-left/
[] https://fvcproductions.wordpress.com/2014/12/29/memorable-experiences-in-gaming/
[] https://fvcproductions.wordpress.com/2014/12/28/analysis-of-my-scribd-top-5-hits/
[] https://fvcproductions.wordpress.com/2014/12/28/interview-fullstack-academy/
[] https://fvcproductions.wordpress.com/2014/12/27/a-short-operation-tips-tricks-4-coding-bootcamps/
[] https://fvcproductions.wordpress.com/2014/12/27/im-a-noob-when-it-comes-to-programming-where-to-now/
[] https://fvcproductions.wordpress.com/2014/12/23/first-meetup-first-impressions/
[] https://fvcproductions.wordpress.com/2014/12/23/analysis-of-the-25-highest-rated-companies-hiring-interns-in-2014-by-glassdoor/
[] https://fvcproductions.wordpress.com/2014/12/23/week-20/" style="display:
[] https://fvcproductions.wordpress.com/2014/12/20/50-lines-for-50-crimes/
[] https://fvcproductions.wordpress.com/2014/12/17/inkling-1-1/
[] https://fvcproductions.wordpress.com/2014/12/03/binary-trees-recursion/
[] https://fvcproductions.wordpress.com/2014/11/10/magnifying-the-bootcamp-research-experience/
[] https://fvcproductions.wordpress.com/2014/11/10/linked-lists-study-guide/
[] https://fvcproductions.wordpress.com/2014/10/20/midterm-melodrama-data-structures-with-java/
[] https://fvcproductions.wordpress.com/2014/10/17/coding-interview-tips-and-tricks/
[] https://fvcproductions.wordpress.com/2014/10/17/ti-89-tricks-for-calculus/
[] https://fvcproductions.wordpress.com/2014/10/17/long-lighthearted-lists/
[] https://fvcproductions.wordpress.com/2014/09/22/limbo-review/
[] https://fvcproductions.wordpress.com/2014/09/10/giving-back/
[] https://fvcproductions.wordpress.com/2014/09/04/answer-potc-parchment-riddle/
[] https://fvcproductions.wordpress.com/2014/09/03/new-html-signature/
[] https://fvcproductions.wordpress.com/2014/08/09/the-how-tos-when-it-comes-to-java-array/
[] https://fvcproductions.wordpress.com/2014/08/08/the-day-after-calculus-ended/
[] https://fvcproductions.wordpress.com/2014/07/20/answer-to-potc-logic-riddle/
[] https://fvcproductions.wordpress.com/2014/06/21/the-interconnectedness-of-social-networking-sites-and-us/
[] https://fvcproductions.wordpress.com/2014/05/12/speech-robotics-in-the-workforce/
[] https://fvcproductions.wordpress.com/2014/05/06/integrating-school-emails-airmail/
[] https://fvcproductions.wordpress.com/2014/05/02/a-review-of-dont-starve/

http://localhost:3000/about/feedback/ --> should be images from Imgur
fvcproductions.files.wordpress --> remove all instances of this

#49 is part of this

Update

[x] https://fvcproductions.wordpress.com/2015/11/13/hrdevfest-talk/
[x] https://fvcproductions.wordpress.com/2015/10/21/my-designlab-experience/
[x] https://fvcproductions.wordpress.com/2015/08/30/fullstack-academy-reflections/
[x] https://fvcproductions.wordpress.com/2015/08/20/readme-template-for-github/
[x] https://fvcproductions.wordpress.com/2015/08/19/one-week-left-of-fullstack/
[x] https://fvcproductions.wordpress.com/2015/08/05/web-dev-and-web-design-slides-fullstack-academy/
[x] https://fvcproductions.wordpress.com/2015/07/25/fullstack-academy-week-6-review-week/
[x] https://fvcproductions.wordpress.com/2015/07/11/fullstack-academy-week-5/
[x] https://fvcproductions.wordpress.com/2015/07/03/fullstack-academy-week-4/
[x] https://fvcproductions.wordpress.com/2015/06/26/fullstack-academy-week-3/
[x] https://fvcproductions.wordpress.com/2015/06/20/fullstack-academy-week-2/
[x] https://fvcproductions.wordpress.com/2015/06/13/first-week-at-fullstack-academy/
[x] https://fvcproductions.wordpress.com/2015/06/04/fullstack-foundations-goldman-sachs/
[x] https://fvcproductions.wordpress.com/2015/05/20/then-what-shall-we-code-for/
[x] https://fvcproductions.wordpress.com/2015/05/20/bootcamp-me-attempting-to-crowd-source/
[x] https://fvcproductions.wordpress.com/2015/05/17/fullstack-foundations-week-1/
[x] https://fvcproductions.wordpress.com/2015/04/26/damehood-through-hollow-knight/
[x] https://fvcproductions.wordpress.com/2015/04/23/ai-movies/
[x] https://fvcproductions.wordpress.com/2015/04/20/full-of-them/
[x] https://fvcproductions.wordpress.com/2015/04/18/sort-detective-solution/
[x] https://fvcproductions.wordpress.com/2015/04/13/reset-launchpad-with-sorty/
[x] https://fvcproductions.wordpress.com/2015/04/13/what-to-do-week-negative-8/
[x] https://fvcproductions.wordpress.com/2015/04/11/auschwitz-a-doctors-eyewitness-account/
[x] https://fvcproductions.wordpress.com/2015/04/08/lease-template/
[x] https://fvcproductions.wordpress.com/2015/03/29/change-your-icons-yosemite/
[x] https://fvcproductions.wordpress.com/2015/03/28/my-top-3-productivity-apps/
[x] https://fvcproductions.wordpress.com/2015/03/12/jeopardy-template/
[x] https://fvcproductions.wordpress.com/2015/02/24/that-tapia-conference/
[x] https://fvcproductions.wordpress.com/2015/02/20/brief-thoughts-best-bootcamps-switchup/
[x] https://fvcproductions.wordpress.com/2015/02/15/ted-2023/
[x] https://fvcproductions.wordpress.com/2015/02/11/itunes-music-february-2015/
[x] https://fvcproductions.wordpress.com/2015/02/01/adding-awesome-websites-to-your-chrome-app-launcher/
[] https://fvcproductions.wordpress.com/2015/01/30/adventures-with-aaai-2015/
[] https://fvcproductions.wordpress.com/2015/01/14/interview-maker-square/
[] https://fvcproductions.wordpress.com/2015/01/06/interview-coding-dojo/
[] https://fvcproductions.wordpress.com/2015/01/06/interview-devleague/
[] https://fvcproductions.wordpress.com/2015/01/06/interview-coding-house/
[] https://fvcproductions.wordpress.com/2015/01/06/interview-with-designation/
[] https://fvcproductions.wordpress.com/2015/01/05/interview-hack-reactor/
[] https://fvcproductions.wordpress.com/2015/01/05/prepare-for-coding-bootcamps/
[] https://fvcproductions.wordpress.com/2014/12/29/aaai-2015-month-left/
[] https://fvcproductions.wordpress.com/2014/12/29/memorable-experiences-in-gaming/
[] https://fvcproductions.wordpress.com/2014/12/28/analysis-of-my-scribd-top-5-hits/
[] https://fvcproductions.wordpress.com/2014/12/28/interview-fullstack-academy/
[] https://fvcproductions.wordpress.com/2014/12/27/a-short-operation-tips-tricks-4-coding-bootcamps/
[] https://fvcproductions.wordpress.com/2014/12/27/im-a-noob-when-it-comes-to-programming-where-to-now/
[] https://fvcproductions.wordpress.com/2014/12/23/first-meetup-first-impressions/
[] https://fvcproductions.wordpress.com/2014/12/23/analysis-of-the-25-highest-rated-companies-hiring-interns-in-2014-by-glassdoor/
[] https://fvcproductions.wordpress.com/2014/12/23/week-20/" style="display:
[] https://fvcproductions.wordpress.com/2014/12/20/50-lines-for-50-crimes/
[] https://fvcproductions.wordpress.com/2014/12/17/inkling-1-1/
[] https://fvcproductions.wordpress.com/2014/12/03/binary-trees-recursion/
[] https://fvcproductions.wordpress.com/2014/11/10/magnifying-the-bootcamp-research-experience/
[] https://fvcproductions.wordpress.com/2014/11/10/linked-lists-study-guide/
[] https://fvcproductions.wordpress.com/2014/10/20/midterm-melodrama-data-structures-with-java/
[] https://fvcproductions.wordpress.com/2014/10/17/coding-interview-tips-and-tricks/
[] https://fvcproductions.wordpress.com/2014/10/17/ti-89-tricks-for-calculus/
[] https://fvcproductions.wordpress.com/2014/10/17/long-lighthearted-lists/
[] https://fvcproductions.wordpress.com/2014/09/22/limbo-review/
[] https://fvcproductions.wordpress.com/2014/09/10/giving-back/
[] https://fvcproductions.wordpress.com/2014/09/04/answer-potc-parchment-riddle/
[] https://fvcproductions.wordpress.com/2014/09/03/new-html-signature/
[] https://fvcproductions.wordpress.com/2014/08/09/the-how-tos-when-it-comes-to-java-array/
[] https://fvcproductions.wordpress.com/2014/08/08/the-day-after-calculus-ended/
[] https://fvcproductions.wordpress.com/2014/07/20/answer-to-potc-logic-riddle/
[] https://fvcproductions.wordpress.com/2014/06/21/the-interconnectedness-of-social-networking-sites-and-us/
[] https://fvcproductions.wordpress.com/2014/05/12/speech-robotics-in-the-workforce/
[] https://fvcproductions.wordpress.com/2014/05/06/integrating-school-emails-airmail/
[] https://fvcproductions.wordpress.com/2014/05/02/a-review-of-dont-starve/

Migrate photos to Google Photos now.
Still need to take screenshots of old website.


Sign: [y/N]: after first signed tx, this message doesn't react on N

Environment information

OS: macOS
Python Version: x.x.x
ape and plugin versions: 0.2.1

$ ape --version
0.2.1

$ ape plugins list
ape-infura 0.2.0
ape-vyper 0.2.0
ape-etherscan 0.2.0

Contents of your ape-config.yaml (NOTE: do not post anything private like RPC urls or secrets!):

$ cat ape-config.yaml
contracts_folder: contracts

What went wrong?
Well, I use APE on testnet to generate a bunch of data for my web interface. With old version (I'm not sure what exactly version I have, maybe 1.5 or maybe 1.6) I ran with command ape run deploy_testing --network ethereum:rinkeby:infura I signed the first tx:
Sign:  [y/N]: y
Enter passphrase to unlock 'trader03' []:
Leave 'trader03' unlocked? [y/N]: y

After that I just leave unlocked account and wait when script will done.
Well, I decided to rewrite some test from Brownie to APE and check how it will going. I installed ape-hardhat through PyCharm Python Interpreter. As I understood APE updated too automatically.
If the script has:
    owner = accounts.load("trader03")
    owner.set_autosign(True)

I hasn't any problems. But if delete these strings and continue to Sign Tx with hands when the next message appear:
Sign: [y/N]:

it will react only positive, so if I type y,Y,n,N, or tap on ENTER, the result will be always Yes.
How to reproduce:
token: https://github.com/vyperlang/vyper/blob/master/examples/tokens/ERC20.vy
deploy_testing.py:
from ape import project
from ape import accounts

class InitToken(object):

    def load_accs(self, type):
        acc = accounts.load("trader03")

        if type > 0:
          acc.set_autosign(True)

        return acc1

    def create_token(self, name, symbol, decimals, supply,  owner):
        token = owner.deploy(project.Token, name, symbol, decimals, supply)
        return token

    def token_approve(self, token, receiver, amount, sender):
        return token.approve(receiver, int(amount), sender=sender)

random_addr = 0xDf032Bc4B9dC2782Bb09352007D4C57B75160B15
### works fine with set_autosign
deploy = InitToken()

main_account = deploy.load_accs(1)
main_token = start_deploy.create_token("NAME", "SMBL", main_account)
deploy.token_approve(main_token, random_addr, 1e18, main_account)

### check Sing Tx without set_autosign and type N
deploy = InitToken()
main_account = deploy.load_accs(0)
main_token = start_deploy.create_token("NAME", "SMBL", main_account)
deploy.token_approve(main_token, random_addr, 1e18, main_account)
deploy.token_approve(main_token, random_addr, 1e18, main_account)
deploy.token_approve(main_token, random_addr, 1e18, main_account)

NOTE: First tx I signed and leave account open.
Sign:  [y/N]: y
Enter passphrase to unlock 'trader03' []:
Leave 'trader03' unlocked? [y/N]: y

if account is locked, then everything works fine.
Please include information like:

what command you ran
the code that caused the failure (see this link for help with formatting code)
full output of the error you received

How can it be fixed?
Fill this in if you have ideas on how the bug could be fixed.

it will react only positive, so if I type y,Y,n,N, or tap on ENTER, the result will be always Yes.

I could use some information on the issue, as I was not able to reproduce this!
I modified your example some to get it to run and then things behaved as expected. e.g. when I select N, it does not leave the account unlocked.
Here is a simpler attempt at reproducing, but things seem to work (the account remains locked when selecting No):
(kong) ➜  ape-demo-project git:(main) ✗ ape console --network ethereum:mainnet-fork
INFO: Starting 'Hardhat node' process.

In [1]: account = accounts.load("test0")

In [2]: project.FundMe.deploy(sender=account)
DynamicFeeTransaction:
  chainId: 31337
  from: 0x1e59ce931B4CFea3fe4B875411e280e173cB7A9C
  gas: 411810
  nonce: 0
  value: 0
  data: 0x608060...0d0033
  type: 0x02
  maxFeePerGas:<PHONE_NUMBER>9
  maxPriorityFeePerGas: 0

Sign:  [y/N]: y
Enter passphrase to unlock 'test0' []:
Leave 'test0' unlocked? [y/N]: N
INFO: Confirmed 0x87061ff1113ac465da2396d0b03bfa3c430b43928897c2fbd1f5c436638acd3f (gas_used=411810)
SUCCESS: Contract 'FundMe' deployed to: 0x274b028b03A250cA03644E6c578D81f019eE1323
Out[2]: <FundMe 0x274b028b03A250cA03644E6c578D81f019eE1323>

In [3]: project.FundMe.deploy(sender=account)
DynamicFeeTransaction:
  chainId: 31337
  from: 0x1e59ce931B4CFea3fe4B875411e280e173cB7A9C
  gas: 411810
  nonce: 1
  value: 0
  data: 0x608060...0d0033
  type: 0x02
  maxFeePerGas: 0
  maxPriorityFeePerGas: 0

Sign:  [y/N]: y
Enter passphrase to unlock 'test0' []:
Leave 'test0' unlocked? [y/N]: N
INFO: Confirmed 0xe464e24a3aad0aafb1528a873347c98becc77c347f08964ff68d3c3034b7b384 (gas_used=411810)
SUCCESS: Contract 'FundMe' deployed to: 0xBcF7FFFD8B256Ec51a36782a52D0c34f6474D951
Out[3]: <FundMe 0xBcF7FFFD8B256Ec51a36782a52D0c34f6474D951>

In [4]:

@SwapOperator if you could please add more context that will help unblock us!

@SwapOperator if you could please add more context that will help unblock us!
sorry I was busy these days.
I made the small video

https://user-images.githubusercontent.com/93691214/166560611-a7849402-cce7-4a63-bdc1-66cf22c74979.mov

@SwapOperator It is strange, because when I do the same thing in your video, I get:
Sign:  [y/N]: n
ERROR: (SignatureError) The transaction was not signed.

I still need more info!
Perhaps send me your pip freeze output as well as Python version and your exact script (just to repro, not anything private).
 I receive the same result.

@SwapOperator Are you able to share the contents of deploy_mainnet.py ?

@SwapOperator Are you able to share the contents of deploy_mainnet.py ?

I send you an  invite to my repo. :) enjoy

Ah! I was able to reproduce! When I install the ape-ethersan plugin, I have this problem.
Strange!

I was able to reproduce!

I was able to reproduce!

ape-etherscan as I understood? :)

ape-etherscan as I understood? :)

Ah, no, that was a false hypothesis. The real reason is that I had an issue with the contract I was using to try and re-pro.

ape-etherscan as I understood? :)

Ah, no, that was a false hypothesis. The real reason is that I had an issue with the contract I was using to try and re-pro.

Did you try with different contracts or script structure?

Did you try with different contracts or script structure?

I was able to repro! Just wasn't because of ape-etherscan as I had thought


Need older article access from the main page

Need better way than search to navigate to older articles

Fixed! there is a link at the bottom of the front page.


Lumen 5.6 undefined method boot

Larastan Version: 0.4.0
--level used: default

Description
php artisan code:analyses

returns
Call to undefined method Laravel\Lumen\Application::boot()
Steps to reproduce
Install lumen 5.6
php composer create-project --prefer-dist laravel/lumen:v5.6.0 lumen5.6

Install larastan latest
php composer require --dev nunomaduro/larastan

Update bootstrap/app.php uncomment line 80
$app->register(App\Providers\AppServiceProvider::class);

Update AppServiceProvider register method
public function register()
{
    $this->app->register(\NunoMaduro\Larastan\LarastanServiceProvider::class);
    $this->app->instance('path.storage', app()->basePath().DIRECTORY_SEPARATOR.'storage');
    $this->app->instance('path.config', app()->basePath().DIRECTORY_SEPARATOR.'config');
}

Laravel code where the issue was found
On vendor/nunomaduro/larastan/bootstrap.php line 29
if we comment the $app->boot() line the command works
if ($app instanceof \Illuminate\Contracts\Foundation\Application) {
    $app->make(\Illuminate\Contracts\Console\Kernel::class)->bootstrap();
} elseif ($app instanceof \Laravel\Lumen\Application) {
    $app->boot();
}

Am i missing something?
I think the boot method was never actually working (lumen v5.1) on Laravel\Lumen\Application now days it is not even present.
Cheers!

boot method was added to \Laravel\Lumen\Application at version 5.7.0 So it's normal to have this error at 5.6.0
I'm not sure if we want to support Lumen 5.6 @nunomaduro what do you think? Should we support Lumen 5.6 ?

No. Just drop Lumen 5.6 and bump illuminate components to min 5.7.


fix: remove eval-based createNamedFn

Close #749

there was no way to turn off the bad implementation, causing a CSP violation every time.
try..catch is quite expensive, defeating the point of using an "optimized" version.

Looks like this is harder than I expect.
There's an ES6 way to create dynamically named function on SO: https://stackoverflow.com/questions/9479046/is-there-any-non-eval-way-to-create-a-function-with-a-runtime-determined-name
However, CSP existed from years before, and this isn't a complete fix.
We can also completely throw away the patched name, sacrificing debugging experience.

This has been fixed in https://github.com/angular/zone.js/pull/748/files#diff-f5e084bcb7c43d977d56c3b791bbca2dR570,I think that is better solution.

Looks super cool, feel free to close mine if it resolves the problem.

@ishitatsuyuki , thanks for posting the issue, you may close this PR and leave the issue #752.


Fetch view resource bundle in main thread for thread safety

Addresses #3558, see Maksym's last comment.

@christibbs  Nit: I would suggest adding a comment to getViewResourceBundle mentioning that it must be called from the main queue. An assertion or a warning message can be added as well. Since we would like to take the fix into M54, I would suggest to do it in a separate PR to avoid extra time for one more round of tests on Travis.


Removes vendor directory

@dwillist let's get https://github.com/paketo-community/bundle-install/pull/8 merged first


Automatically set regressionwindow-wanted for bugs that are regressions but don't have a regression range

Instead of having triagers do this manually, we could partially automate it.
We already have a way to detect bugs that are regressions (bugbug).
We could probably train an additional classifier to detect regression bugs that have no regression range.

Other than setting "regressionwindow-wanted", it would also add a comment explaining to the reporter what is needed (and maybe pointing them to mozregression).

@sylvestre was suggesting on IRC that this could be too noisy, and maybe we could do this only when we also have steps to reproduce.

Another possibility is to be more noisy with some people and less noisy with other.
E.g. by bug reporting experience.
For people who have only reported few bugs, we might ask for a regression range for bugs that are regressions.
For people who have reported many bugs, we assume they usually know what they are doing and only ask for a regression range when the bug is a regression and there are steps to reproduce.

#397 is doing it for bugs which have the hasSTR flag.


[Test](count on index) add statistics check for unique table #42982

cherry pick from #42982

run buildall


download_public -> public_download

After testing this new functionality; realized that:

public_download is a better name than download_public
405 will not show the reason in the browser which will be misleading; thus changing to 200

Codecov Report

Merging #2917 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #2917   +/-   ##
=======================================
  Coverage   95.29%   95.29%
=======================================
  Files          73       73
  Lines       13997    13997
=======================================
  Hits        13339    13339
  Misses        658      658

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 f7d6df2...283dce7. Read the comment docs.

Now, after the latest changes, the error in the website are:

and wget:
--2019-07-09 13:01:52--  https://qiita-rc.ucsd.edu/download_public/
Resolving qiita-rc.ucsd.edu (qiita-rc.ucsd.edu)... <IP_ADDRESS>
Connecting to qiita-rc.ucsd.edu (qiita-rc.ucsd.edu)|<IP_ADDRESS>|:443... connected.
WARNING: cannot verify qiita-rc.ucsd.edu's certificate, issued by ‘emailAddress=jdereus@ucsd.edu,CN=qiita-rc.ucsd.edu,O=UCSD,L=La Jollaq,ST=California,C=US’:
  Self-signed certificate encountered.
HTTP request sent, awaiting response... 405 You need to specify both data (the data type you want to download - raw/biom) and study_id
2019-07-09 13:01:52 ERROR 405: You need to specify both data (the data type you want to download - raw/biom) and study_id.


BC Farsi: Legal system and Immigration-For more legal information

There are 8 issues in this topic.

Blue arrow points out to the word "mailto" that should be removed.

Red and yellow arrows point out to the mixed up order of words. The english words should be at the beginning of the sentences.

Green arrow points out to the word " نجمن "  which should be " انجمن " it missed the letter " ا "

The word "mailto" should be removed.

Red arrow points out to the mixed up order of words. The english words should be at the beginning of the sentences.

Blue arrow points out to a small space needed here to separate between the two paragraphs.
Red arrow points out to the mixed up order of words. The english words should be at the beginning of the sentences.

See screenshot from the guide.

My solution puts the bolded phrases on their own line. Otherwise the english words will always be in the wrong spot described above

A few comments:

Not sure I'm a fan of bringing the EN text on to its own line, but maybe it's the least bad solution for when an RTL paragraph starts with an EN word.
All fixes seem to be right, just waiting for Meaad to confirm one thing, then I can close this

Item number 3 above, see green arrow, has not been fixed.


Model collections

A  common scenario in modelling is that we have a large number of similar/related single neuron models. Each model needs to have a separate representation in the KG, as they can be used individually, and may have different validation reference data, etc. However, we don't want to flood the KG Search results with hundreds of such models, rather the user should retrieve a model collection, with links to the individual component models.
Currently we achieve this by keeping the individual models in the Model Catalog, and releasing a uniminds ModelInstance to represent the collection.
This is a hack, and for openMINDS / KG v3 I'd like to do things more cleanly.
What I propose is to use the "hasSupplementVersion" property of ModelVersion to hold the links from the ModelVersion representing the collection to the list of component single neuron models.
The question remains: how to hide the individual component models in the KG Search? If this is the only use case for "hasSupplementVersion", then I guess the KG UI logic could exclude models which are "supplements" to another from the search results, or have a checkbox to allow the option of including such models. An alternative approach would be to add a ModelCollection schema to openMINDS.

@olinux @lzehl what do you think?

Dear @apdavison this is an important use case and similar than for datasets (although with much larger collections, I suppose). We received multiple requests by users and reviewers to "hide" versions in the KG Search and only present them on direct request.
I had something like the following in mind for this, but did not yet fully discuss this with @olinux or the development team (I think it matches what you suggest, but maybe not completely?):

the KG Search visualizes dominantly only the conceptual research products (Dataset, Model, Software, MetaDataModel)
the research product versions are listed there according to their relation:

supplementing versions together (with a "download all" option, because they supplement each other to provide the full research product)
alternative versions listed next to each other (maybe stating the  major difference between them, e.g. contentType of data)
sequential versions listed in order (latest at the top/coming first)

individual research versions should be still represented in the KG Search but only on direct request through the conceptual research product

If this would not work for your use case could you maybe give a more concrete example?
I like the checkbox you suggested for defining for the supplement versions how they are displayed.
@olinux your thoughts on this?

@lzehl This is close to the model collection use case; the main difference is that each of the component single neuron models has both a Model and at least one ModelVersion, so we would still need to be able to hide (or group) the Model products in the KG Search.

@apdavison I think I do not understand the structure of this completely...  Let me ask a couple of questions (to see where I might have the wrong assumption):

There is a main Model with a set of ModelVersions?
These main ModelVersions are defined by some code, but that code integrates also various other (sub)Models and all their versions or actually one version for each of these (sub)Models?
Can those (sub)Models be used independently of the main Model or not? Meaning should they be also used by other main Models?

@lzehl Let me try to restate the problem:

There is a collection of related/similar Models. Each Model has at least one ModelVersion.
The size of the collection is somewhere between 10 and 1000.
Each Model can be used independently.

The problem is that because there are so many they would dominate the KG Search results, so we would like a single entry per collection in the results, which gives access to all the Models/ModelVersions in the collection. (Note that we have several such collections).
Possible solutions:
1. add a ModelCollection and ModelCollectionVersion schema to openMINDS
In this scenario, it should be easy to exclude the members of the collection from the search results, but then we are adding yet another schema to openMINDS.
2. create a Model (with one or more associated ModelVersions) to represent the collection.
In this scenario, the logic to exclude the members of the collection from the search results becomes more complex, but the advantage is we're reusing existing schemas.

Thanks for explaining again @apdavison. Here my thoughts:
Normally I would say that for grouping related models typically a Project should be used. But that of course does not solve the problem that you do not want to flood the KG Search Results.
For solution 1: I still have some question here: why is there a ModelCollectionVersion needed? would it be not sufficient to group all Models (and with that all their versions) into one collection? Is there any other metadata you would like to capture for a modelCollection, besides using it to group related Models?
For solution 2: Assuming there is only one Collection and no CollectionVersion needed. I would maybe redefine the ResearchProduct / ResearchProductVersion schemas by moving the "hasSupplementVersion" to the ResearchProduct (that would work for datasets as well, and I suppose for software too @jagru20 ?). I would then define one Model for the whole collection and define for each related model one ModelVersion and list in hasSupplementVersion. I would leave the hasVersions in the Model blank. For each version of the related models I would again define ModelVersions and connect those via hasNewVersion/hasAlternativeVersion with the corresponding ones in hasSupplementVersion. Note: the "hasSupplementVersion" could also be renamed to something else if needed.

why is there a ModelCollectionVersion needed? would it be not sufficient to group all Models (and with that all their versions) into one collection?

for example, more models might be added to the collection.

@apdavison I see.
That case could be covered in solution 2 over a Project then: Each ModelCollectionVersion would be one Model (rest is the same as stated above) and these Models are grouped into a Project.
Would that work?
Solution 3 (similar to 2 but a different angle): Leave schemas as they are, but add an optional property "isPartOfCollection" to a ResearchProduct that can link to another ResearchProduct of the same type, in your case a Model. The referenced Model(s) (entered in "isPartOfCollection") represent(s) the CollectionVersion(s) which can be grouped into one Project. Each Model that has listed another Model in  "isPartOfCollection" does not need to be directly visualized in the KG Search (including their ModelVersions), only the once that are referenced in "isPartOfCollection" are grouped in a Project.

I need to think this more through...
@apdavison could you let me know in which use case a collection version is really needed (e.g., should they always get a DOI?) I understood first that the feature you're missing is mainly for visualizing purposes and not because that this structure is needed for referencing. I'm just asking again because the versioning makes this problem much more difficult to solve cleanly...

Yes, the collection needs to be citable. It is less important that the individual members be citable.
If we add the property "isPartOfCollection" to ResearchProductVersion rather than to ResearchProduct, I think that solves the versioning problem. Then any ResearchProductVersion which for which "isPartOfCollection" is not empty should be "hidden", and any ResearchProduct for which all its versions are hidden should also be hidden.

@apdavison sorry for all the spams on that issue today. Would the previous sketch of the model satisfy your use case?
I'm not yet sure how to solve / define the list of supplements for each collection version in that case. This might have to be it's own schema eventually which is maybe even connected to the ResearchProduct as main collection again.

@lzehl any possibility you could share the diagram with me in an editable form? then I can show what I have in mind

@apdavison Of course, I'll send you an email.

Hi all, I am not sure if I can give much input to the discussion, but to answer the question on the location of hasSupplementVersion: I am not sure if that property makes Sense in the researchProduct because it would mean, that one software entity can link to a softwareVersion. In my opinion, this possibility should be - for software - located at researchProductVersion, as it is theoretically possible that different versions of the same software have different supplementVersions (i.e. the former components).
However, if hasSupplementVersion needs to be moved, it might be sensible to amend softwareVersion such that it holds a property "hasComponents" which also would be a bit more straightforward for software.

@jagru20 yes. I thought that you might mention the "hasComponents". Let's wait for @apdavison feedback on the sketch. Please continue following this discussion so that we can solve this issue for all research products sufficiently (considering all adoption of the concept of an additional grouping for the research products and/or research product versions).

@apdavison looks good I think. The ResearchProducts on the right side and the ResearchProductVersions of the different model versions in the middle should not show up in the KG Search, correct?
Some points / questions:

Could we rename "isSupplementedBy" to "hasComponents"? (cf. comment by @jagru20 and next point)
For datasets with cohort releases (first 20 subjects, second 30 subjects, third 50 subjects, -> total 100 subjects) I would like to still have the "isSupplementVersionOf" option (or something similar in name, could be also dataset specific if there is no need for models and software) between ResearchProductVersions. Or do you have a better idea?
We would still need to have a tag on the ResearchProducts and ResearchProductVersions that identifies them for not showing up in the KG Search, correct?

yes (or we could invert the connection, have "isComponentOf")
makes sense to me
that's a question for @olinux. In principle the query could exclude items that are in a "hasComponents" list (or which have an "isComponentOf" link)
no, I don't think so

Hi,
Here are my thoughts about this: I see the point in having a structure like this - we should make sure though that it's well understood what it describes for both, the producer of the structure and the consumer. Therefore I would suggest to call a ResearchProduct(Version) a "composite" when it consists of multiple other ResearchProduct(Version)s which should be documented explicitly as part of the openMINDS documentation. Please object if you have a better term for this.
IMHO, we should (as discussed above):

replace "isSupplementedBy" with "hasComponents" (although technically equivalent, I would keep the direction of the connection from the higher to the lower level since it might make since it feels more natural to describe this top-down and might simplify the way multi-reuse can be displayed - but this is a subjective feeling and I could live with the inverse too).
"hasComponents" can exist on both "ResearchProduct" and "ResearchProductVersion" although "ResearchProduct" can only point to another "ResearchProduct" whilst a "ResearchProductVersion" can point to another "ResearchProduct" or a "ResearchProductVersion" (this is mostly to relax the requirement to be too specific about the version of a dependent resource e.g. of software components). For the cohorts (if I understood it correctly), I'm wondering if we shouldn't represent each cohort as an individual "ResearchProduct" which can be grouped by this composite mechanism (so the individual cohorts can be versioned themselves e.g. if there have been some internal changes / improvements / formatting ...)
We need to define if we want to make it explicit every time that a "ResearchProduct" is a component of another "ResearchComponent" (by specifying it in the "hasComponents" link) or if we want to infer this (e.g. by defining that "ResearchProduct A" automatically becomes a component of "ResearchProduct B" as soon as one of its versions is connected to a version of "B").

If we do want to infer it, we need to decide if we want to "materialize" this inferred link (e.g. by having automated scripts adding the links for those cases) or if we want to leave it to the client to do the appropriate interpretation.
If we don't want to infer it, we might want to think about having an automation pipeline suggesting the link to be added by the user.

The KG Search would present "cards" / entry points for root-level ResearchProducts only (which are not components themselves) and integrate the information of the components within this view similar to versions (the actual design has still to be designed). Here, we also need to answer the question if we want to handle composites of composites or if we restrict this (at least on the interpretation level) for a single composite layer only.
We should have a discussion about DOIs for these kind of structures: Should components of a bigger components get their own conceptional and/or version DOIs?

Based on @apdavison example structure and @olinux comments I'd like you to have a look at the following drawing

I picked up the following aspects from the suggested approaches:

ResearchProduct can ReasearchProductVersion both have the property "hasCompenents"

for ResearchProduct this property can connect to other ResearchProducts
for ResearchProductVersion this property can connect to other ResearchProductVersions

ResearchProduct in addition can have the property "hasVersions" which can connect to ResearchProductVersions
a ResearchProductVersion in addition can state if it "isNewVersionOf" or "isAlternativeVersionOf" another ResearchProductVersion of the same ResearchProduct (if grouped under "hasVersions")
within the system it should be possible to "hide" ResearchProducts which reflect the conceptual component / cohort and ResearchProductVersions that reflect the versioned component /cohort

Although quite complex in structure this seems to be the most consistent way of capturing such cases in the graph database.
USE CASE ONE: Model collections (@apdavison does this still fit?)
USE CASE TWO: Datasets consisting of different subject cohort releases (@UlrikeS91 could you double check if that fits as well?)
USE CASE THREE: Software with different components (@jagru20 would that fit?)

Hi Lyuba,
It does with the minor additional comment that imho "ResearchProductVersions" should be able to point to both, "ResearchProduct" and "ResearchProductVersion" by the "hasComponent" since it would be quite tough to represent (and maintain) the dependency graphs of Software if you can only connect versions with each other. This is especially true if you're thinking about widely used libraries which would need the tracking of all potentially used versions - unless we decide that we register major versions only -> what do you think @jagru20 ?

@olinux & @jagru20 for "hasComponents" to be honest it does not really makes sense to me to allow pointing from a version to a concept. Would it not be sufficient to allow "only" the registration of the conceptual collection (white shade) with it's Research Product components (gray shaded) in the above depicted metadata model? (Meaning for such a case the colored versions could be left out.

@lzehl this is actually not the same use-case:
What I had in mind for software was that you're registering your software - let's say "Knowledge Graph" with its version "v3" -> now "Knowledge Graph v3" depends on a component called "ArangoDB". So what I would do is to register "ArangoDB" as another Software. There's plenty of different versions for ArangoDB and the "Knowledge Graph" is trying to upgrade regularly to them.
The question is now which granularity you would like to track. You could state:

"Knowledge Graph v3 has the component ArangoDB"
"Knowledge Graph v3 has the component ArangoDB 3.x"
"Knowledge Graph v3 has the component ArangoDB 3.6.11"

The first is obviously the most generic but also the one which needs the least maintenance. Here, you would need to point to the "concept" for "ArangoDB" which is version independent.
The second is the most practical if we want to improve granularity to a version level (and therefore disallow to link ResearchProductVersions to ResearchProduct) since at least the metadata wouldn't need to be updated for every minor version -> nevertheless, if we decide to migrate to ArangoDB 4 (which is possible without changing the Knowledge Graph version number since it's an internal dependency), our meta-data entry would need to be updated though. Here the question appears who is actually doing it and how the software team is going to be notified about the upgrade.
The third approach would only be realistic if we would automatically ingest dependency trees (based on the existing mechanisms like Maven / Gradle / npm / ... ) which - imho - is not the purpose of openMINDS. It would definitively not be possible to manage it.

@olinux thanks for providing this hands-on example. It helps a lot to organize my thoughts better.
I think the key point for software is that there we are talking about dependencies of a software product which has frequent sub-releases that might not all be captured in the KG. The components in such a software were (most likely) not build to serve that software but were produced as independent products, similar to the models in a collection. The difference to the model collection: all software dependencies are needed in order for the main software to work while in a model collection a single model could also be left out without affecting the overall functionality of the model collection (in most cases I guess).
My question here is clearly: should software dependencies on that level be really captured within the graph database or is it not sufficient or even better to document such dependencies within the software repository in the versioned specific software specifications? That does not mean that we may want to capture the dependencies directly in a few cases, but for those I still would think the coarse level you suggest would be sufficient.
I'm asking this for two reasons: on the one hand that level of detail seems to me more on tier-3 level or even beyond (since changes might happen frequently) on the other hand I think we do not aim to register all software out there within the KG in order to cover all possible dependencies of all software products. From your comment above I think you argue in the same direction, correct?
What could be done for software to "outsource" this issue is to allow to point to a "dependency file" for a specific registered software version and to better capture that the repository link of a software product does point to the overall repository and not necessarily the registered version (e.g. the official release of that version).
@jagru20 & @olinux let me know what you think.

As far as I understood, the purpose of the current components attribute in software was not to capture all possible dependencies of a software, but rather to yield to other neuroscience-related software that this software uses as a component to function. What we considered as neuroscience-related until now is software, that either already is part of the KG or is to be integrated into it (i.e., no commonly known libraries or services, but other specialized software or libraries).
I am not totally sure, but I think this is also a question about what information we want to deliver in defining another software as a component. Do we want to

just want to give a hint to software, that is related to the software the user is just looking at or
map neurocience-related dependencies?

In the first case, the first of @olinux granularity examples is totally sufficient IMO.
In the second case, in my understanding, the SoftwareProductVersion should carry the information, on which version of its component it relies (like the green shade in the drawing). Unfortunately, I don't know enough about software development to be able to assess when such a dependency can change without the version number having to change, and have so far assumed that examples like @olinux's above don't happen. But in that case I would refer to the softwareProduct, in the sense that it could theoretically be the latest version. However, I don't think that would really help as it is to unspecific.
Maybe @bweyers could briefly explain the initial intention behind the Components entry?

@apdavison , @olinux , @jagru20 , @UlrikeS91 , @skoehnen , @bweyers
I've made the following changes now (within the PR #168):

All individual ResearchProduct schemas (Dataset, Model, MetaDataModel, Software) have now a property "hasComponent" that can link to another ResearchProduct of the same type.
All individual ResearchProductVersion schemas (DatasetVersion, ModelVersion, MetaDataModelVersion, SoftwareVersion) have now a property "hasComponent" that can link to another ResearchProductVersion of the same type.
The property "hasSupplementVersion" does not exist anymore in the individual ResearchProductVersion schemas.
The property "hasAlternativeVersion" was changed to "isAlternativeVersionOf" in all individual ResearchProductVersion schemas.

All properties discussed above are of course not required.

this issue seems to be solved for now therefore I close it. Let see if it will hold up in the use cases


Update node-version-manager extension

Description

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

but failing on ci

@AndresMorelos how and when do we merge?

@LeOndaz we need to wait for someone from raycast team


Mc param update

@DanielJMaher , This is pretty straight forward.

You got Conflicts, sir! @FBRTMaka


Link Lists are borked!

Link lists are exhibiting a show-stopping bug whereby they don't display at all.

I believe this was resolved by e6a0fd7cf8b3ad290fedfe22036879ad9b46ab12, but it's a little hard to test.

Looks to me like the issue persists. When I load the edge list in the first screenshot below into MicrobeTRACE, I get a network without any edges connecting nodes (see second screenshot):


Changed km/h to m/s and corrected formatting in the README

Short Description:
Fixed wrong unit in README under Advance Config.
Fixes:

km/h to m/s
Added size of 1 step
added a space

The config uses km/h!
Calculate it!

@Ryurem btw, one of your pictures didn't upload.

60 meter in 10 seconds.
20km/h = 5,5 m/s
5.5 * 10 = 55.
@Ryurem you seem to be correct.


Online server to validate comments?

Not an issue on the actual format, but related:
If we want folks to use this more widely then having an online server that validates the format (either as a file upload or a cut and paste) would likely be helpful rather than requiring everyone to install locally.

If it gets traction, definitely. Ideally it'd run in-browser.

I had a quick look at running it in pyodide using Pyscript. It seems possible, but would require some refactoring so we don't pull in libraries like requests for validation.

OK, I've got a page up at:
https://mnot.github.io/ietf-comments/
It's pretty barebones but functional; I'll likely add to it and adjust over the next few days. Feedback much appreciated.
Also, pyscript and pyodide are very early software, but it works in the browsers I've tested.


Clean up dependencies

Closes #183
Create a server extra that installs Voilà and ASE.
Remove unused dependencies: App Mode, JupyterLab, NumPy.
Update README accordingly and ensure the CLI returns a non-zero code and a helpful message on how to make it work if Voilà is not installed.

Missing:

[ ] Tests

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@38a6b24). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop     #184   +/-   ##
==========================================
  Coverage           ?   35.82%
==========================================
  Files              ?       17
  Lines              ?     2127
  Branches           ?        0
==========================================
  Hits               ?      762
  Misses             ?     1365
  Partials           ?        0

Flag
Coverage Δ

#optimade-client
35.82% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 38a6b24...fb72d56. Read the comment docs.


Fixes ownership of a tmp directory propagated to container

tmt then tries to enter this directory when running tests, but cannot do so because of the original permissions u=rwx,go=.
This was a subtle test issue spoiling wrapping up of #1521.

I'm not sure about this change. Why should be user expected to have their working directory (plan) readable by container user? Shouldn't it be tmt's job to map tmt's user to container properly (/me found --uidmap)?
It could be OK to merge to unblock #1521 (as that has higher priority than custom users for container) but IMO it should be fixed.

@lukaszachy well, the file was created by the user with u+gw - mktemp. Why should tmt try to work around the permissions here if the user requested to run as nobody? It looks to me a user problem, more like a tmt problem.

I'm not sure about this change. Why should be user expected to have their working directory (plan) rwx for container user? Shouldn't it be tmt's job to map tmt's user to container properly (/me found --uidmap)?

I'm not sure here. You might be right, but the whole test setup might be also something to improve. Adding --uidmap sounds tempting, yet it's not something I'm versed in, and I'd rather not dive into it right now.

It could be OK to merge to unblock #1521 (as that has higher priority than custom users for container) but IMO it should be fixed.

Maybe an issue for follow-up investigation & improvement?

--uuidmap could even require elevated privileges to work as @lukaszachy wants:
https://docs.podman.io/en/latest/markdown/podman-run.1.html#uidmap-container-uid-from-uid-amount
But I am personally not convinced this is something we would like to do. Feels to me security problem, I created a file as me, I can only access it, run container as somebody else, and expect the access to work? Does not sound good to me.

Filed https://github.com/teemtee/tmt/issues/1663 for a future investigator.

@lukaszachy well, the file was created by the user with u+gw - mktemp. Why should tmt try to work around the permissions here if the user requested to run as nobody? It looks to me a user problem, more like a tmt problem.

This isn't user's problem. User created some directory, called tmt init there. It is 'tmt' who binds directory with invalid permissions to the container.
Just run tmt init in any new directory, execute tmt run pro -h container --user nobody login finish and while in the container try to eg. touch $TMT_PLAN_DATA/this. You will get permission denied. Does it look like user's fault? I'd argue that no.

Agree with @happz and @thrix that tmt should not unexpectedly/randomly change permissions of existing files or directories, this could present a security issue. If needed, let's file a separate issue and discuss the uidmap approach or other options.

I'm not saying that tmt should change permissions of existing files. tmt just needs to make sure that workdir it exposes  is writeable for the container.

Just run tmt init in any new directory, execute tmt run pro -h container --user nobody login finish and while in the container try to eg. touch $TMT_PLAN_DATA/this. You will get permission denied. Does it look like user's fault? I'd argue that no.

I understand you reasoning. On the other hand, the default container provision setup with root as the user works nicely read/write. If you explicitly select nobody you should know what you are doing. And I see valid use cases for this, for example execute tests which do not need to write any data to disk. The following example works correctly even with nobody:
mkdir /tmp/test
cd /tmp/test
tmt init --template mini
tmt run --all provision --how container --user nobody

Well, tmt is not installed so... yes, the test will fail with an error.

I understand the reasoning however - we mention in docs to use TMT_*_DATA to store output, we don't say anything that it might be not writable.
If this was about provision -h connect --user and tmt will be able to connect but wont be able to write anything to workdir wouldn't it be a bug? Why is container --user different? The implementation how workdir gets from/to SUT is an implementation detail.


ViewComponentAttributeBag behaviour is incorrect

Laravel Version: 7.0.8
PHP Version: 7.4.0
Database Driver & Version: n/a

Description:
I believe the behaviour of the View Component $attributes->merge() is incorrect.   Blade Components are top down.  When a view declares a component on the page and specifies an attribute, if the component has a default attribute of the same name, in the current implemenation only the default value will be used.
The docs state:

Sometimes you may need to specify default values for attributes or merge additional values into some of the component's attributes.

My interpretation (and the ViewComponentAttributeBag makes extensive use of the name 'defaults') is that a component can specify a default but the page declaring the component can override the default.  Currently this is not the case.  I believe the intention of this API is to have a similar behaviour to Vue.
Steps To Reproduce:
<?php
use Illuminate\View\ComponentAttributeBag;

// this is akin to <x-my-component width="600" />
$bag = new ComponentAttributeBag(['width' => '600']);

// this is akin to {{ $attributes->merge('width' => '100%']) }}
dump($bag->merge(['width' => '100%']))

Result:
Illuminate\View\ComponentAttributeBag {#1623
  #attributes: array:1 [
    "width" => "100%"
  ]
}

Suggestions

I can quicky create a PR to change the behaviour.

But maybe the naming of the method merge() is misleading?  Would defaults() be more appropriate ?  I appreciate that the method is in fact merging the special case of class attributes.

Thoughts?

I agree the that <x-my-component> should override default attributes. Naming is tricky, especially since merge() is what we have now...
Probably unrelated, but I'll mention it here anyway: When looking up how "boolean attributes" (disabled, checked etc) are handled I run into an issue where the output differs when using $attributes and $attributes->merge() (Note that nothing is merged in). This test illustrates that:
public function testAttributeBag()
{
    $bag = new ComponentAttributeBag(['test' => true]);

    $this->assertSame('test="test"', (string) $bag); // Fails, actual output: test
    $this->assertSame('test="test"', (string) $bag->merge());

    $bag = new ComponentAttributeBag(['test' => false]);

    $this->assertSame('', (string) $bag); // Fails, actual output: test=""
    $this->assertSame('', (string) $bag->merge());
}

The result when using $attributes->merge() is actually pretty neat, but might be unintentional. It means that <x-input :checked="false"> renders as <input> and <x-input :checked="true"> renders as <input checked="checked"> with this blade template:
<input $attributes->merge()>

Might indicate that attributes should have a bigger overhaul than just the handling of defaults?

(Copied from the PR) This is a better illustration of the merge issue.
With a component that defines some default attributes:

merge(['width' => '600', 'class' => 'mb-4']) }}>
  ...

If the component is used like this
<x-my-table width="100%" class="mt-2" />

We would expect the rendered template to be:

  ...

But the current implementation renders:

>
  ...


ARROW-1364: [C++] IPC support machinery for record batch roundtrips to GPU device memory

This additionally does a few things:

Change libarrow_gpu to use CUDA driver API instead of runtime API
Adds code for exporting buffers using CUDA IPC on Linux, but this is not yet tested

cc @m1mc @asuhan @seibert @sklam
This patch enables writing record batches to GPU device memory with code like:
std::shared_ptr<CudaBuffer> device_serialized;
ASSERT_OK(arrow::gpu::SerializeRecordBatch(*batch, context_.get(),
                                           &device_serialized));

You can also do zero-copy read from device memory:
Status ReadRecordBatch(const std::shared_ptr<Schema>& schema,
                       const std::shared_ptr<CudaBuffer>& buffer,
                       MemoryPool* pool, std::shared_ptr<RecordBatch>* out);

The returned record batch in this case will have device pointers in its buffers.
We'll need to do a tiny bit of work so that libarrow_gpu can "attach" to existing CUcontext created by others, but I wanted to get this reviewed and merged first.
Additionally, we have the new functions for schema serialization:
Status SerializeSchema(const Schema& schema, MemoryPool* pool,
                       std::shared_ptr<Buffer>* out);

Status ReadSchema(io::InputStream* stream, std::shared_ptr<Schema>* out);

Thanks, this is very exciting!

Thanks. I will resolve the outstanding issues around shared CUDA contexts in the course of making a PR into MapD to simplify their Arrow serialization code

Thanks, I forward to using this in our product.


chore: Migration from rstk to afrish

Related issues

resolve #78

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

19 of 25 (76.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.6%) to 88.84%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/lib.rs
5
8
62.5%

src/window/toolkit.rs
11
14
78.57%

Totals

Change from base Build<PHONE_NUMBER>3:
-0.6%

Covered Lines:
605

Relevant Lines:
681

💛  - Coveralls


fix: revert "fix: adjust java memory usage"

Reverts jeremylong/Open-Vulnerability-Project#224

@jeremylong shouldn't we just put it into quotes?

@okgolove thanks for noticing that was the problem.


Consider update of ng-dynamic-forms library to latest version

Problem Description
The submission form implementation in DS7 (and DS8) depends on the ng-dynamic-forms library. The current version of this library is 18 (released in mid of 2023). DS8 depends on version 16 (released in december 2022).
Note: There is / was some discussion about a replacement of the ng-dynamic-forms library in DS8. Some developers noted that this change would require a large amount of work. Perhaps it is easier to update the version of the ng-dynamic-forms library.

While I'm not against an upgrade, I think this doesn't "fix" the issues mentioned in #2216.  The issue is that @ng-dynamic-forms is not being well maintained (even now, it's not yet updated to Angular 17 support, which is what DSpace 8 uses).  So, this ticket could provide a way to temporarily improve ng-dynamic-forms by upgrading it. But, in the long term it's still better to find a way to migrate to Angular's own forms library.
So, I'll pull this over to the 9.0 board in case someone wants to work on this until we find a way to fix #2216.


Self defined PetscPreconditioner

Hi all,
I want to define a very general petsc user-defined preconditioner, which is just like this one. And I know I just need to solve several separate linear systems in sequence like this explanation. I also read about using Operator, but it's different if I use PetscParMatrix.
The below class SelfDefined_Preconditioner has some errors but I don't where and how to fix it.
class SelfDefined_Preconditioner: public PetscPreconditioner
{
private:
    PetscParMatrix &A, &B;
    PetscLinearSolver *ksp1, *ksp2;

public:
    SelfDefined_Preconditioner(MPI_Comm comm, const string& prefix, PetscParMatrix& A_, PetscParMatrix& B_)
            : PetscPreconditioner(comm, prefix), A(A_), B(B_)
    {
        ksp1 = new PetscLinearSolver(A, prefix);
        ksp2 = new PetscLinearSolver(B, prefix);
    }
    virtual ~SelfDefined_Preconditioner() { delete ksp1, ksp2; }

    virtual void SetOperator(const Operator& op) {} //avoid calling PetscPreconditioner::SetOperator()

    virtual void Mult(const Vector& b, Vector& x) const
    {
        Vector dummy(b.Size()); // Temporary Vector
        ksp1->Mult(b, dummy);
        ksp2->Mult(dummy, x);
    }
};

Thanks for any help in advance!

@stefanozampini or @jandrej, do you think you can help?

What exactly is not working? Can you provide the error message or provide a minimal failing example so that I can run and test the code?

I think what you need is a shell preconditioner. See https://github.com/mfem/mfem/blob/tds-mhd-dev/miniapps/mhd/imResistiveMHDOperatorp.hpp Take a look at how MyBlockSolver is defined and used.
You can take a look at imMHDp and play with it. Here is the instruction https://github.com/mfem/mfem/blob/tds-mhd-dev/miniapps/mhd/README.md

The below class SelfDefined_Preconditioner has some errors but I don't where and how to fix it.

What kind of errors? compilation errors? or issues at runtime? Or what else?
A note: using a linear solver as preconditioner for an outer  linear solver may cause troubles  if the inner solves do not lead to a linear operator (unless you use a flexible outer method) Is this the issue?

Thank you for your reply @jandrej , @tangqi , @stefanozampini .
Yes, @tangqi you are right I need a shell preconditioner. I will dig into MyBlockSolver in your project.
Sorry about MWC @jandrej and @stefanozampini. Below is an example code which is obtained from by simplifying mfem/examples/petsc/ex5p.cpp.
#include "mfem.hpp"
#include <iostream>

using namespace std;
using namespace mfem;

class SelfDefined_Preconditioner: public PetscPreconditioner
{
private:
    Operator &op1, &op2;
    PetscLinearSolver *ksp1, *ksp2;
    Array<int>& block_offsets;

public:
    SelfDefined_Preconditioner(MPI_Comm comm, Operator& op1_, Operator& op2_,
            const string& prefix, Array<int>& offsets)
            : PetscPreconditioner(comm, prefix), op1(op1_), op2(op2_), block_offsets(offsets)
    {
        height = op2.Height() + op2.Height();
        width = op1.Width() + op2.Width();
        ksp1 = new PetscLinearSolver(static_cast<PetscParMatrix&> (op1), "prec1_");
        ksp2 = new PetscLinearSolver(static_cast<PetscParMatrix&> (op2), "prec2_");
    }
    virtual ~SelfDefined_Preconditioner() {}

    virtual void SetOperator(const Operator& op) {} // avoid calling base class SetOperator()

    virtual void Mult(const Vector& b, Vector& x) const
    {
        // here divide Vector b into 2 sub Vector b1, b2, but how to do it?
//        Vector b1, b2;
//        Vector x1, x2;
//        ksp1->Mult(b1, x1);
//        ksp2->Mult(b2, x2);
        // here merge 2 sub Vector x1, x2 into x, but how to do it?
        x = b; // just for avoiding compiling failure
    }
};

int main(int argc, char *argv[])
{
    int num_procs, myid;
    MPI_Init(&argc, &argv);
    MPI_Comm_size(MPI_COMM_WORLD, &num_procs);
    MPI_Comm_rank(MPI_COMM_WORLD, &myid);

    const char *petscrc_file = "./petsc_opts";
    MFEMInitializePetsc(NULL, NULL, petscrc_file, NULL);

    Mesh *mesh = new Mesh(20, 20, Element::TRIANGLE, true, 1.0, 1.0);
    int dim = mesh->Dimension();

    ParMesh *pmesh = new ParMesh(MPI_COMM_WORLD, *mesh);
    delete mesh;

    FiniteElementCollection *hdiv_coll(new RT_FECollection(1, dim));
    FiniteElementCollection *l2_coll(new L2_FECollection(1, dim));

    ParFiniteElementSpace *R_space = new ParFiniteElementSpace(pmesh, hdiv_coll);
    ParFiniteElementSpace *W_space = new ParFiniteElementSpace(pmesh, l2_coll);

    Array<int> block_offsets(3);
    block_offsets[0] = 0;
    block_offsets[1] = R_space->GetVSize();
    block_offsets[2] = W_space->GetVSize();
    block_offsets.PartialSum();

    Array<int> block_trueOffsets(3);
    block_trueOffsets[0] = 0;
    block_trueOffsets[1] = R_space->TrueVSize();
    block_trueOffsets[2] = W_space->TrueVSize();
    block_trueOffsets.PartialSum();

    ConstantCoefficient one(1.0);
    Vector two_(dim);
    two_ = 2.0;
    VectorConstantCoefficient two(two_);

    // This example code solves a simple 2D mixed Darcy problem
    //          k*u + grad p = f
    //          -div u       = g
    // Assemble the finite element matrices for the Darcy operator
    //         D = [ M  B^T ]
    //             [ B   0  ]
    //         where:
    //         M = \int_\Omega k u_h \cdot v_h d\Omega   u_h, v_h \in R_h
    //         B   = -\int_\Omega \div u_h q_h d\Omega   u_h \in R_h, q_h \in W_h
    //
    // Construct the operators for preconditioner
    //         P = [ M    0 ]
    //             [ 0    S ],
    //         where:
    //         S  = \int_\Omega p_h q_h d\Omega   p_h, q_h \in W_h
    //
    ParLinearForm*        fForm(new ParLinearForm);
    ParLinearForm*        gForm(new ParLinearForm);

    ParBilinearForm*      mVarf(new ParBilinearForm(R_space));
    ParMixedBilinearForm* bVarf(new ParMixedBilinearForm(R_space, W_space));
    ParBilinearForm*      sVarf(new ParBilinearForm(W_space));

    BlockVector x(block_offsets), rhs(block_offsets);
    BlockVector trueX(block_trueOffsets), trueRhs(block_trueOffsets);

    PetscParMatrix *pM = NULL, *pB = NULL, *pBT = NULL, *pS = NULL;
    Operator::Type tid = Operator::PETSC_MATAIJ;
    OperatorHandle Mh(tid), Bh(tid), Sh(tid);

    fForm->Update(R_space, rhs.GetBlock(0), 0);
    fForm->AddDomainIntegrator(new VectorFEDomainLFIntegrator(two));
    fForm->Assemble();
    fForm->ParallelAssemble(trueRhs.GetBlock(0));

    gForm->Update(W_space, rhs.GetBlock(1), 0);
    gForm->AddDomainIntegrator(new DomainLFIntegrator(one));
    gForm->Assemble();
    gForm->ParallelAssemble(trueRhs.GetBlock(1));

    mVarf->AddDomainIntegrator(new VectorFEMassIntegrator);
    mVarf->Assemble();
    mVarf->Finalize();
    mVarf->ParallelAssemble(Mh);
    Mh.Get(pM);
    Mh.SetOperatorOwner(false);

    bVarf->AddDomainIntegrator(new VectorFEDivergenceIntegrator);
    bVarf->Assemble();
    bVarf->Finalize();
    bVarf->ParallelAssemble(Bh);
    Bh.Get(pB);
    Bh.SetOperatorOwner(false);

    sVarf->AddDomainIntegrator(new MassIntegrator);
    sVarf->Assemble();
    sVarf->Finalize();
    sVarf->ParallelAssemble(Sh);
    Sh.Get(pS);
    Sh.SetOperatorOwner(false);

    (*pB) *= -1;
    pBT = pB->Transpose();

    Operator *darcyOperator = NULL;
    {
        BlockOperator *tdarcyOp = new BlockOperator(block_trueOffsets);
        tdarcyOp->SetBlock(0,0,pM);
        tdarcyOp->SetBlock(0,1,pBT);
        tdarcyOp->SetBlock(1,0,pB);
        darcyOperator = new PetscParMatrix(pM->GetComm(),tdarcyOp, Operator::PETSC_MATAIJ);
        delete tdarcyOp;
    }

    SelfDefined_Preconditioner darcyPreconditioner(MPI_COMM_WORLD, *pM, *pS, "prec_", block_offsets);

    trueX = 0.0;
    {
        PetscLinearSolver *solver = new PetscLinearSolver(MPI_COMM_WORLD, "main_");
        solver->SetOperator(*darcyOperator);
        solver->SetPreconditioner(darcyPreconditioner);
        solver->SetPrintLevel(2);
        solver->Mult(trueRhs, trueX);
        delete solver;
    }

    // 17.
Without you telling us what you think is the issue (at least how it manifests itself, like an error at screen) is impossible to give you an answer

I run your example and got the error below, This is because PetscPreconditioner has a PC object inside (protected member of the PetscSolver class) that you should construct  properly. Since you are providing the action of the preconditioner, then you should inherit from mfem::Solver instead of mfem::PetscPreconditioner and everything will work

[szampini@localhost petsc]$ valgrind ./ex1p
[0]PETSC ERROR: --------------------- Error Message --------------------------------------------------------------
[0]PETSC ERROR: Object is in wrong state
[0]PETSC ERROR: Mat object's type is not set: Argument # 1
[0]PETSC ERROR: See https://www.mcs.anl.gov/petsc/documentation/faq.html for trouble shooting.
[0]PETSC ERROR: Petsc Development GIT revision: v3.12.1-170-gbf5b09bd8c  GIT Date: 2019-10-29 09:27:25 +0300
[0]PETSC ERROR: Unknown Name on a arch-debug named localhost.localdomain by szampini Tue Nov  5 17:06:50 2019
[0]PETSC ERROR: Configure options --DATAFILESPATH=/data/petscdatafiles --download-ctetgen --download-exodusii --download-glvis --download-hdf5 --download-hypre --download-metis --download-mfem-commit=b25280d --download-mfem=1 --download-ml --download-mumps --download-netcdf --download-p4est --download-parmetis --download-pnetcdf --download-ptscotch --download-revolve --download-suitesparse --download-superlu --download-superlu_dist --download-triangle --download-hpddm --download-slepc --with-blaslapack-dir=/home/szampini/intel/compilers_and_libraries_2019.5.281/linux/mkl --with-cxx-dialect=C++11 --with-fortran-bindings=0 --with-mkl_pardiso-dir=/home/szampini/intel/compilers_and_libraries_2019.5.281/linux/mkl --with-opengl --with-scalapack --with-valgrind --with-zlib CFLAGS="-Wall -g -O0" CXXFLAGS="-Wall -g -O0" FFLAGS="-g -O0" PETSC_ARCH=arch-debug
[0]PETSC ERROR: #1 MatHasOperation() line 10828 in /home/szampini/Devel/petsc/src/mat/interface/matrix.c
[0]PETSC ERROR: #2 PCGetDefaultType_Private() line 23 in /home/szampini/Devel/petsc/src/ksp/pc/interface/precon.c
[0]PETSC ERROR: #3 PCSetFromOptions() line 147 in /home/szampini/Devel/petsc/src/ksp/pc/interface/pcset.c
[0]PETSC ERROR: #4 KSPSetFromOptions() line 335 in /home/szampini/Devel/petsc/src/ksp/ksp/interface/itcl.c
[0]PETSC ERROR: #5 void mfem::PetscSolver::Customize(bool) const() line 2037 in /home/szampini/Devel/petsc/arch-debug/externalpackages/git.mfem/linalg/petsc.cpp

Thanks @stefanozampini .
It works. I should be careful about protected members when defining myself class next time.
Thanks all of you again.


Ignore a note that occurs right after \id marker

fixes https://github.com/sillsdev/serval/issues/393

This change is

Codecov Report
Attention: Patch coverage is 95.65217% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 67.32%. Comparing base (a19d577) to head (6cc0bc7).

Files
Patch %
Lines

src/SIL.Machine/Corpora/UsfmTokenizer.cs
93.75%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #203      +/-   ##
==========================================
+ Coverage   67.31%   67.32%   +0.01%
==========================================
  Files         441      441
  Lines       35001    35021      +20
  Branches     4695     4700       +5
==========================================
+ Hits        23560    23579      +19
  Misses      10352    10352
- Partials     1089     1090       +1

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


For the Thermostat presets delegate implementation we do not support deletion of presets.

This issue tracks adding support for cases where Presets have been removed as part of the write to the Presets attribute in the example app implementation

also address - https://github.com/project-chip/connectedhomeip/pull/34532/files#r1693633732


Docs/fix documentation generation

Description

Upgrade typedoc and the markdown plugin to the latest versions
Migrate the typedoc config to be compatible
Refactor the Polymesh class and its namespaces into api/client
Hide some types that shouldn't be exposed by the docs

These changes keep the doc generation from breaking and result in something acceptable, but not ideal. I created this task to discuss improvements
JIRA Link
https://polymath.atlassian.net/browse/DA-347
Checklist

[x] Updated the Readme.md (if required) ?

:tada: This PR is included in version 15.0.0-alpha.4 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 15.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 15.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix clone on filters

Signed-off-by: Ruturaj Mohite<EMAIL_ADDRESS>Description
PR Fixes failing clone on filters
Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

Handled by UI PR

It was not fixed. I need a coffee I think


Adding documentation of new features in IMAP extractor

Randomly selecting @ondrajodas to bring this to attention.

@davidesner  new default branch is main. Would it be possible to rebase this if PR is still valid? Thanks!

I rebased it

I rebase it again


ansible deployment

The idea is to be able to deploy and maintain a production instance with nexus as the starting point. This would allow support to reproduce issues based on the ansible scripts.

[ ] add a make deployment that uses a dedicated repository with ansible scripts

Is this still relevant?

Is this still relevant?

ping @butonic

ping @butonic

Seems to be fixed with our continuous deployed examples


Add .QCI to asset types.

The follow changes add .QCI to asset types to use as a naming convention for .QC files included within other files.
This is currently used in #148 .
This could also be used for sprites .QC files if needed.

@SamVanheer
#148 has been merged (see previous comment).


Checking PX4 messages at startup

Hello,
The compatibility of the PX4 messages are tested at startup but not their availability. I don't know to which extend it can be implemented but for now if one message if missing in the controller we get a throw when we ask for the last message for example with no previous warning. It would be nice to have a system to check that the required messages are really available on PX4 side at initialization.
If it exist already I doesn't work for vehicle_angular_velocity for example (did I miss something when I did the PR on this?)
Also the name of the topic in the throw would be a + :D

There's no check yet. My preferred approach is to have a mechanism to request a message at a given update rate. And this could then also return an error if it's not available.


Github icon in header leads to Nextra repository

The Github icon at the top-right of the page currently leads to https://github.com/shuding/nextra rather than to the SWR or SWR-site repository.

Thanks for reporting! Fixed now


potentially corrupted file

CNR-ISAC/ua_6hrPt_GLOBO_free_s20180125-r1i47p1f1_gr_20180125-20180310.nc
CNR-ISAC/ua_6hrPt_GLOBO_free_s20180125-r1i49p1f1_gr_20180125-20180310.nc
--
and
CNR-ISAC/ua_6hrPt_GLOBO_free_s20180125-r1i48p1f1_gr_20180125-20180310.nc
are significantly larger than earlier ensemble members, and my attempts to open these files failed.

I redownloaded these files, and the file size was more reasonable. Not sure what happened the first time....


[WIP] Implementing SRIOV

Implemented SRIOV funcitonality according to this doc
Still work in progress, needs to be tested

[ ]  Need to add a grub option to grub.cfg, e.g. enable_sriov, which would automatically include intel_iommu and add iommu=pt into the list of kernel command line parameters.
[ ] Write unit-tests
[ ] Come up with usage scenario
[ ] Write functional tests

[ ]   Need to add a grub option to grub.cfg, e.g. enable_sriov, which would automatically include intel_iommu and add iommu=pt into the list of kernel command line parameters.

Shouldn't we add that to the default kernel command line? Or do we think there is hardware where we do not want to enable it?

[ ]    Need to add a grub option to grub.cfg, e.g. enable_sriov, which would automatically include intel_iommu and add iommu=pt into the list of kernel command line parameters.

Shouldn't we add that to the default kernel command line? Or do we think there is hardware where we do not want to enable it?

@eriknordmark Well, for Intel platforms we need to enable VT-d, for AMD -- AMD-Vi and if we would want to run it on Arm it'll look differently. I'm not sure about intel_iommu or vt-d option in kernel, but if you mess up huge pages or cpu pinning in grub config, kernel will crash and it'll become an infinite boot.

Well, for Intel platforms we need to enable VT-d, for AMD -- AMD-Vi and if we would want to run it on Arm it'll look differently. I'm not sure about intel_iommu or vt-d option in kernel, but if you mess up huge pages or cpu pinning in grub config, kernel will crash and it'll become an infinite boot.

OK, I'm fine pulling in this PR (once the other issues are resolved) in a state which requires grub config to enable further testing. But later (before customers try it) I think we need to figure out some automatic way to do this which can't result in failures to boot.

After internal conversations with @milan-zededa and @eriknordmark SR-IOV implementation was changed. Now we do not store any mappings inside domainmgr.go rather creating appropriate IoBundle for each VF requested. For this to work Logicallabel field was added to differentiate VF IoBundles from PF IoBundles, and AddOrUpdateIoBundle was modified to be able differentiate VF from PF since they have same PhyLabel.

And I have a high-level question whether we should at least handle added VFs on a running system. Currently the VF processing seems to only be done when !Initialized i.e., at the startup of domainmgr. @milan-zededa what are you thoughts on handling additions or more general modifications?

Modifications to VF count require to un-assign all existing VFs, i.e. restart domains that already use them. For this reason we decided that the maximum number of VFs a particular device might need better be fixed and part of the device model.

@eriknordmark there were problems accessing account from which this PR was created. I created new one here. If it's possible, please archive this PR and use new one.

Closed in favor of #2828


refactor(multicast-spec): update multicast operator tests to use pipeable operators

Update multicast spec to use updated import sites and pipeable operators.
Ran into a typing issue in this test. Not sure if it would be considered a separate issue (or an issue at all really?) but would appreciate some input. With the following example:
const expected = [1, 2, 3, 4];

const connectable = of(1, 2, 3, 4).pipe(multicast((new Subject<number>())));

connectable.subscribe((x) => { expect(x).to.equal(expected.shift()); },
   (x) => {
      done(new Error('should not be called'));
    }, () => {
      done();
    });

connectable.connect();

I get a type error on the last line: [ts] Property 'connect' does not exist on type 'Observable<number>'
This looks to be because the pipe function return value is typed as Observable<number> when in this case we really need it to be ConnectableObservable<number>
To get around this I added
const connectable = of(1, 2, 3, 4).pipe(multicast((new Subject<number>()))) as ConnectableObservable<number>;

but this is verbose and also cheats the typings test at the end of the file (line 708) where it should infer the type.

Thanks again, @natmegs!


docker-compose version 2 service definiton breaks dnsdock

dnsdock is unable to register containers running inside the new network groups of docker-compose version 2.
Logs show the following (notice the <nil>):
2016/02/22 00:41:39 Added service: d90f35986816e301f2144ebc0ec97c159cc8da741ef34b3fb1ac9f65a3d26719 {name_foo_1 bar1 <nil> -1 []}

+1

+1

I had a look at how to solve this issue, it appears that dockerclient does not support it by default.
There is an update on my fork that solves this issue: https://github.com/tjamet/dnsdock/tree/networks however, I cannot do the pull request until dockerclient supports more recent API (PR: https://github.com/samalba/dockerclient/pull/234)
Maybe you can try the fix by running docker run <...> tjamet/dnsdock?

That looks good - hopefully dockerclient will accept the PR soon.
In the meantime does anyone know of a workaround?

@tjamet I use:
network_mode: "bridge"
for the services that should be available via dns.

@tjamet i tried your docker image, it does not correcly detect the ips of containers running inside a docker-compose network, i see just "nil".
@tjamet do you have any plans to solve this issue ?
Thanks a lot!

@paolomainardi I had the same problem and was able to fix that by applying this patch. https://github.com/duck1123/dnsdock/commit/bbf2279715e3aa3a0e4907bea6c82f4844bae06a
I'm not sure if it's the best solution, but it allowed me to specify dns aliases for services that only exist in a docker network. A proper solution would probably allow the user to specify which network adapter to use in cases like this.

Thanks @duck1123!
AFAIK a container can exisr just in a network, am wrong ?

@tonistiigi should we consider this project dead ? is there anything we can do to fix the docker networks compatibility ?

The answer is pretty obvious, it's time to look for an alternative.

Sorry for the late reply @paolomainardi
I also run docker-compose with networks and do not notice any problem
There are nil in logs but dig answers correctly with ..

currently this seems stalled by the samalba client.  Should we consider re-writing this to use the fsouza dockerclient base instead?  It's quite active in development.

@jnugh, adding network_mode: "bridge" works for me, thanks

Hi
I did some modification to remove dependencies to deprecated docker client lib.
I've replaced the samalba library by the official docker client one.
Tested on my environment with a compose file creating containers with networks (no nil ip address anymore).

I can confirm that aacebedo's fork works perfectly with docker-compose v2 ! I didn't find it on docker hub so I had to build it myself.

Thanks a lot @aacebedo can you build it on the docker hub ?

Hi !
You're welcome :)
I've pushed the image with the following tag on dockerhub:  aacebedo/dnsdock:1.12.1
A docker pull shall do the trick.
I do not have the ownership on the official repository so I am unable to push it as an official dnsdock release.
I hope the author will merge my PR and will update its image, as people has to change the name of the repo in their workflow with the current solution :(

it works for me.
I am surprised that the official image isn't set to rebuild on merge.

Travis can be configured to push automatically.
I'll check with @tonistiigi if I can push to my docker hub repo instead of his as he said he don't use the code anymore.

I'll check with @tonistiigi if I can push to my docker hub repo instead of his as he said he don't use the code anymore.

You can also configure hub.docker.com to build on each merge instead of letting Travis do it, which is quite easy. Maybe he could do that instead, so that the image name stays the same?

I've migrated on Rocker so hub.docker is not an option anymore

Maybe @tonistiigi could add you as a collaborator on hub.docker.com so that you can push the image manually ? That way the name of the image does not change…

Already did it but it still cannot erase or have a total control on the repo

Another solution would be embrace the name change and update the documentation to reflect the fact that aacebedo/dnsdock should be used because it is more maintained.

Yep I am going to ask him


bio/b_addr.c: resolve HP-UX compiler warnings.

The warning reads "[cast] may cause misaligned access". Even though
this can be application-supplied pointer, misaligned access shouldn't
happen, because structure type is "encoded" into data itself, and
application would customarily pass correctly aligned pointer. But
there is no harm in resolving the warning...

On related note there is #5742 pending for review. On another related note, with reference to the fact that this request targets 1.1.0, there will be remaining TLSProxy-related issues in 1.1.0, so one can wonder if it would be appropriate to backport some of recent TLSProxy changes. I'd prefer not to...

Am I right that this is induced by #5691? Are you interested in the full compile log? I would need to remove paths and host names, though. There are some more warnings throughout the code as well as a massive amount of "remarks".

Are you interested in the full compile log?

It's a trick question. From one hand yes, while on the other no. No, because it can be frustrating to sort out false positives. But sure, attach one to #5691... Note that I suggest to disregard some of test errors in 1.1.0, those in 70 range. This is admittedly controversial and can be challenged. My rationale is that since HP-UX users didn't step up so far, they might as well move straight to 1.1.1.

Since there is a chance that more modifications would be needed, I've added WIP, and postpone the commit. However, if other warnings turn out not worthy to address, I'm going to simply go forward with this one.


adapter-cloudflare-workers: platformProxy persist configuration example is wrong

Describe the bug
https://kit.svelte.dev/docs/adapter-cloudflare-workers says
svelte.config.js

import adapter from '@sveltejs/adapter-cloudflare-workers';

export default {
	kit: {
		adapter: adapter({
	  config: '<your-wrangler-name>.toml',
	  platformProxy: {
		persist: './your-custom-path'
	  }
	})
	}
};

https://developers.cloudflare.com/workers/wrangler/api/#syntax says
persist boolean | { path: string }

Indicates if and where to persist the bindings data. If not present or true, defaults to the same location used by Wrangler, so data can be shared between it and the caller. If false, no data is persisted to or read from the filesystem.

The doc example should be changed to persist: { path: './your-custom-path' }, or just persist: true.
Reproduction
n/a to docs
Logs
No response
System Info
n/a to docs

Severity
annoyance
Additional Information
No response

Nite: we should fix this for adapter-cloudflare docs as well https://kit.svelte.dev/docs/adapter-cloudflare#usage


"Special" color setting

Having some issues with wal.. I can't get it to generate background, foreground and cursor lines in the colors.Xresources file.
EDIT:
Please close/delete, lets put it down to sleep deprevation..

On another note, I seem to have the same issue as #138 also. I was too busy focusing on the special snippet.

@dylanaraps 👀


fix: remove duplicate file model_location_event and model_location_type

Remove LocationType

Remove LocationEvent

R17 Files

https://github.com/free5gc/openapi/blob/feat/r17/models/model_amf_location_location_type.go
https://github.com/free5gc/openapi/blob/feat/r17/models/model_amf_location_location_event.go


Add option to publish stubs

Laravel 7 introduced new Stub Customisation
by publishing there stubs to /stubs/
could publish  to /stubs/vendor/... similar to how views are published
https://github.com/laravel/framework/commit/db4e5d3a5186b41bb0e1742381cc19ddc4ea86d3#diff-67cd0e59d939a533a834a6f4b204843b

good idea!  Relies on #4, but should be relatively easy.
It's a shame that we can't hook into the publish:stubs command...

Yeah standard pattern would be something like vendor:publish —tag=stubs


Fix to set variables for non-interactive shells

Fix for issue at https://github.com/ThePrez/ServiceCommander-IBMi/issues/35
In a nutshell, bash is not properly detected when invoked from QP2SHELL (and likely others) unless -i is specified.

Oh for real? Was this all it was?

Oh for real? Was this all it was?

Let's not celebrate until the OP verifies it on the ServiceCommander issue! 😬

Well the problem here is now I've gotta go through the trouble of updating the version and publishing the rpm. Ugh. Will get to it as soon as I can. Probably this wekeend. I might not even have an IBM i to build the RPM on anymore, boo.
Has Matthew tested this?

Fixes https://github.com/ThePrez/ServiceCommander-IBMi/issues/35
Latest changes also fix up the bashrc file to set vars and path even for non-interactive shell. I have been able to recreate Matt's problem and verify that this fixes it. Matt has also made a similar edit to his .bashrc and it resolved.


nixos/ibus: add ibus portal if portals are enabled

Motivation for this change
Should fix https://github.com/NixOS/nixpkgs/issues/75120, haven't tested anything.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This does not change anything to #75120: without IBUS_USE_PORTAL there is a delay, with it there is no delay. Tested on XFCE+i3.

Yeah @jtojnar confirmed this. We should add the portal, though.


Adds bolt add and bolt workspace add commands

This is encompasses all the work from #27

adds yarn.add helper
adds symlinking helper
refactors install to use symlinking
adds tests for install

Its still a bit messy and theres some dupliacted code I'd like to clean up, but I wanna try to get this in and do any more refactors in the next drop (which would also add bolt workspaces add).
As an aside, the testing patterns I've been using have changed a fair bit over the course of all this, so I definitely want to refactor and align all that at some point.
The mock yarn.add command for instance is in three different forms in three different places. A single one that everything uses would be awesome.

[] refactor nested-workspaces-with-root-dependencies-installed tests to use package-with-external-deps-installed

Okay, had another look through and this seems pretty fine. I'm going to start work on the addDependenciesToPackage s function now.

I think we should enforce at the project level that you cannot add a workspace as a dependency.
path/to/project/ $ bolt add workspace-name # error
path/to/project/other-workspace/ $ bolt add workspace-name # success

Can you rebase?

I cant seem to push here after rebasing, so pushed to https://github.com/boltpkg/bolt/pull/36


Update glibc

Fixes

Description

Adds a temporary update for glibc for a security vulnerability fix, while waiting updated python and airflow images.
Testing Instructions

CI should pass. I also ran just recreate locally and ran a few DAGs and some smoke tests on the API.
Exec into the docker containers for the catalog webserver and upstream_db and run ldd --version. The glibc version should be 2.31-13+deb11u7. For the API and ingestion server it should be 2.36-9+deb12u3.
Checklist

[ ] My pull request has a descriptive title (not a vague title likeUpdate index.md).
[ ] My pull request targets the default branch of the repository (main) or a parent feature branch.
[ ] My commit messages follow best practices.
[ ] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible errors.
[ ] I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

It might be easy to forget to remove these pinned versions later so maybe an issue (blocked for now) to remove them

Good point. Created #3157 to track this


Updated the customization section.

Warning the user of a difference from the start section. Ref #306

HI @colsen1991
I'm sorry for the delay, I've updated the docs structure so there's conflicts, if you fix it I can merge! Thanks

@rafaelpimpa No worries :) We all have lives outside of GitHub, hehe. I'll get to it ASAP 👍

Should be all good(?)!

Thanks :)


⚠ Site ANTS has degraded performance

In b282f08, Site ANTS (https://ants.gouv.fr) experienced degraded performance:

HTTP code: 200
Response time: 8369 ms

Resolved: Site ANTS performance has improved in fdf2937.