Properly add /nix/ and /nix/store/ first the the tarball

Motivation for this change
In https://github.com/NixOS/nixpkgs/pull/58431 the authors ensured that
the resulting layer.tar would always list
/nix/
/nix/store/
first to fully comply to the tar spec. Various refactorings later it is only
ensured to create /nix/ but NOT /nix/store anymore. Instead tar transformed
them to /nix/nix and /nix/nix/store.
To verify the change works I built several images, tested them on Docker and some very picky proprietary software working with Docker images.
Things done

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

[ ] NixOS
[x] 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.

We should not hardcode /nix/store. Instead, use builtins.storeDir for portability.

I agree. But I think that is a bigger sweep as we hard code and assume /nix/store in several places in the docker builder. I suggest to get this patch in to fix the issue at hand and tackle the rewrite to builtins.storeDir in the next patch.


Release v0.3

Description
We prepare to release v0.3 at the end of Aug. Here is the feature list:

Release multi-language client. Include Java, Rust and Python.
Support static cluster mode. And keep pushing toward a full-featured dynamic distributed version (related project: Distributed CeresDB).
Extend supported SQLs (tag: A-SQL).
Implement the hybrid storage format. And support reading from two formats.

Feel free to suggest or discuss other features you would like to add :heart:

Will ceresdb support multiple data sources? e.g. read records from mysql's REDO log and structure them into ceresdb's data structure storage

Will ceresdb support multiple data sources?

This sounds like data ingest, are you meaning bulk load?

yes, which means that ceresdb can import data from other existing commercial database files. I don't know much about this, so i not sure the terminology.

This might cover three scenarios. Let's narrow our discussion:

For offline data migration, our persistent format is relatively straightforward -- only a few metadata and data in the parquet format, all stored in OSS. We can achieve this in a few ways. And for some common formats like CSV or standard parquet generated in other systems, we can also support them directly.
Online data ingesting, on the other hand, would be a little more complicated. Maybe we need to add support for consuming data from streaming systems like Kafka, Flink, Pulsar or others. They have splendid ecosystems. By supporting them we can easily be integrated into various systems as a downstream warehouse.
The last one is querying from other databases. This may be a little off-topic but let me mention it as well. CeresDB is only a query frontend in this situation. In some cases I can imagine there are other projects that can do this. So I'll assign a low priority to this.

Offline migrating implementations are different case by case. We can support needed upstream on demand. Online ingesting also has a few candidating upstream, but I believe there is a common pattern among them. We can choose one to support at first if we decide to work on this. It can take a lot of effort and we need to discuss it further.

Thanks for the summary @waynexia . I will give some additional comments on these scenarios.

For data migration or data initialization from external data source, there could be some tools. But as far as I know, demands of this scenario is not so frequent. This feature can be implemented as an independent binary, like tools in mysql ecosystem. We can discuss this feature later.
Online data ingestion, this is a much more complex topic. If we start working on this, we should consider latency, consistency, transformation and other aspects in real-time computing. These requirements are commonly implemented using stream-computing framework like Apache Flink. So, in my opinion, the CeresDB project will be more focusing on core features of time-series database its own.
For the scenario: querying from other databases, there is a better choice, presto. So, we will not work on this direction.


Memory allocation problem

I consitently seem to be getting problems with memory allocation on Windows. I tried to change value of MYBMALLOC_BLOCK_SIZE from 5000 to smaller or higher, to see how memory fragmentation is affecting the allocation, but for some reason I get the same memory block size problem with a message:
Error: mymalloc: failed to allocate 3576400 bytes
It does not matter how long the input WAVE file is.
Below is my sample JCONF file:
-input file
-filelist Models\test.dbl
-htkconf Models\wav_config
-h Models\PLPL-v4.2.am
-hlist Models\PLPL-v4.2.phn
-d Models\PLPL-v4.2.lm
-v Models\PLPL-v4.2.dct
-b 2000
-lmp 12 -4
-lmp2 12 -4
-walign
-fallback1pass
-multipath
-iwsp
-norealtime
-iwcd1 max
-spmodel sp
-spsegment
-gprune none
-no_ccd
-sepnum 150
-b2 360
-n 40
-s 2000
-m 8000
-lookuprange 5
-sb 80
-forcedict

I guess it is not a problem of memory fragment, maybe other memory leak.  Could you determine where it occurs by debugger?  For example, using GNU debugger:
% make distclean
% CFLAGS=-g ./configure  (or env CFLAGS=-g ./configure)
% make
% gdb ./julius/julius
% run [command line arguments]

When stopped by error, type frame to see from where the crashed mymalloc() was called.
Or could you show me the error log?

The bug is caused by Julius not being able to find a segment and it constantly allocates more and more memory, until it runs out. I played a lot with Julius over the years and one of the changes I made was to increase the value of MAXSPEECHLEN from 320000 to 32000000. However I managed to get around the bug by adding option -cutsilence, which forces the Julius to cut segments based on silence detection. This has improved not only decoding speed but also WER from around 11.5% to around 11%. I suppose for the time being I will close the bug, as there is a workaround available.


Offline mode still greyed out after downloading all game files.

I have downloaded all latest game files on wifi and still cannot enable offline mode.

Check to make sure all of the files actually downloaded (there should be a "game" folder inside of the "resources" folder in the app). If the app is installed in somewhere like Program Files, the app might also have permission issues extracting the files, in which case running the app as Admin should allow that to work.

Hi! I had closed the menu in the top corner which allowed me to switch between online and offline mode...and don't know how to get it back...can you pls help

Hi! I had closed the menu in the top corner which allowed me to switch between online and offline mode...and don't know how to get it back...can you pls help

Press alt.

Thx
On Sun, 23 Jun, 2024, 3:03 am gameboi4784, @.***> wrote:

Closed #105 https://github.com/Admiral-Billy/Pokerogue-App/issues/105
as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/Admiral-Billy/Pokerogue-App/issues/105#event-13251798504,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASS7I2CZGZQQCDN6QANQVCTZIXURDAVCNFSM6AAAAABJU6ZWQOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTGI2TCNZZHA2TANA
.
You are receiving this because you commented.Message ID:
@.***>


Circuit equivalence in the presence of diagonal gates before measure

Hi,
It seems that two circuits which are different by a diagonal gate just before the measurements will be interpreted as non-equivalent by QCEC checker? Say, two circuits like:
qc1:
X q[0];
measure q[0] -> c[0];
and qc2:
X q[0];
Z q[0];
measure q[0] -> c[0];
The two circuits above implement different unitaries, however the measurement results will be the same.
Is it possible to implement such a functionality (equivalence checker in the presence of diagonal gates before measure gates)?
E.g. Qiskit has a RemoveDiagnoalBeforeMeasure subroutine as a part of transpiler.

JKQ QCEC now supports an (optional) optimization pass removeDiagonalGatesBeforeMeasure which can be used to eliminate diagonal gates before measurements. It can be enabled

in Python by passing removeDiagonalGatesBeforeMeasure=True to verify(...)
in the command-line executable by passing the flag --removeDiagonalGatesBeforeMeasure.

Note that there may still be some bugs. Let me know if you encounter any!

Great, thanks!


Code is not working with calling gpaw

After<PHONE_NUMBER>b0504a8571fcf8b46aa6118656251f or somewhere near, code is not working anymore with calling gpaw as:
gpaw -P5 python gpawsolve.py -o -c config.py -i inputfile.cif

but working with:
python gpawsolve.py -o -c config.py -i inputfile.cif

Ok. We can not parse more than one argument under gpaw command. I do not know why. However, with the 6e38e0ebac4284e2c0eeecbf832ef25d0c28883f commit, we can use the code with MPI with the commands:
For AMD CPUs or using Intel CPUs without hyperthreading: (Example CPU is intel here, 4 cores or 8 threads)
$ mpirun -n 4 python gpawsolve.py
For using all threads provided by Intel Hyperthreading technology:
$ mpirun --use-hwthread-cpus -n 8 python gpawsolve.py
We need to change readme and usage page in website accordingly @beyzalisesivdin .


Add etl2pcapng note to MMA deprecation notice

Docs Build status updates of commit ddf94e5:
:warning: Validation status: warnings

File
Status
Preview URL
Details

documentation/blog/MS-WININTBLOGLP/dd98b93c-0a75-4eb0-b92e-e760c502394f.md
:warning:Warning

Details

documentation/blog/MS-WININTBLOGLP/dd98b93c-0a75-4eb0-b92e-e760c502394f.md

[Warning] Author openspecs-office cannot be recognized in GitHub.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Thanks for the addition!


Teach AutoBench how to accept multiple benchmarks

It's handy to be able to run multiple benchmarks at once without having to specify all of them and doesn't require that substantial of a refactor.

Looks good.


included venv activation for python scripts

New PR for the venv activation problem adressed in https://github.com/MiczFlor/RPi-Jukebox-RFID/pull/2144
This implements the ideas from https://github.com/MiczFlor/RPi-Jukebox-RFID/pull/2144#discussion_r1421836778

have "proxy" shell scripts that handle the venv activation and setup the needed working dir, to be run from any relativ path.
better accessability of the scripts for the user, e.g. group with alike scripts like installation or tools
run_*.py scripts can't be moved right now, as the module imports are not accessable from sub dirs, so they have to stay in the root folder. This could be a future addition (possible solution https://stackoverflow.com/a/50194143)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.09%) to 38.384%

Files with Coverage Reduction
New Missed Lines
%

src/jukebox/components/gpio/gpioz/core/input_devices.py
1
62.73%

Totals

Change from base Build<PHONE_NUMBER>:
-0.09%

Covered Lines:
418

Relevant Lines:
1089

💛  - Coveralls

Would it be a problem, if a user manually activates a venv and then runs a sh script, which also activates the venv?

Would it be a problem, if a user manually activates a venv and then runs a sh script, which also activates the venv?

Nope, tested multiple activations and couldn't see a sideeffect. The installations process does the same with the RFID Reader setup script.

Looks good. In another iteration, a way to abstract the repetition of the individual bash files could be to build a single installer script with an argument.
$ run.sh rpc_tool
$ run.sh publicity_sniffer
$ run.sh register_rfid_reader

This could then prepare again for Whiptail 🙃

Thought about that too 😁👍

I will run some final test over this, otherwise ready to merge.

Edit: Do we then need the motd message at all (#2225)?

Not for the reason of informing about the venv, but I truly believe we should keep this! 🚀
##################################################
   ___  __ ______  _  __________ ____   __  _  _
  / _ \/ // / __ \/ |/ /  _/ __/(  _ \ /  \( \/ )
 / ___/ _  / /_/ /    // // _/   ) _ ((  O ))  (
/_/  /_//_/\____/_/|_/___/____/ (____/ \__/(_/\_)

            Welcome to your Phoniebox
##################################################

👍 i will update the Message to only have the banner :)

With this condition that updates are broken and a fresh installation is needed, should we add this already to v3.5.0?

... should we add this already to v3.5.0?

Aligned!

Last fix included. Good to go, if nothing left.

Merge it!


⚠ Spryr has degraded performance

In ccf370c, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3285 ms

Resolved: Spryr performance has improved in 54a8844 after 11 minutes.


[Broken] Call preventDefault() on keydown (GH-3)

https://github.com/satoshinm/NetCraft/issues/3 Keyboard controls interact with web page (ex: space = pages down), need to block/capture these events

Abandoned in favor of https://github.com/satoshinm/NetCraft/pull/29


pH measured in mV

A pH sensor can output in millivolts (mV) - this is now encountered in Cape Cod. TADA does list both VOLTS and MV in the characteristic validation table for PH, but marks both as REJECTED. From what I can see 0 mV == pH 7.0. Need a good function for this, considering:
pH = 7 - mV/57.14
New function would go in convert module, convert.SiO2_to_NTU() is very similar.

This originally came up in Cape Cod demo code block ~47:

pH, this time looking at a report
df = harmonize.harmonize(df, 'pH', report=True)
On inspection these results are all from OrganizationIdentifier==WTGHA. Of their pH results (n=8218) most are in None units (as expected), rather than mV (n=2193). This suggests the same results are added in both units. Although that doesn't mean their conversion is necessary, it should provide a good set of tests.
Some initial results show the function working as expected (e.g., "MonitoringLocationIdentifier"=="WTGHA-M41" & "ActivityStartDate"=="2013-09-12" has -64.9 mV and 8.1). However, those results that are in mV range from -1856.0 to 227.8. Looking at pH where "ResultMeasureValue"=="-1856", it occurs at WTGHA-S33 on 2014-05-20, and the result in expected units (None) is 7.22. Looking at a less extreme negative still out of range (-305) occurs at WTGHA-M41 on 2012-06-06, and the result in expected units is 7.82. For positive results, 227.8 occurred at WTGHA-P4 on 2022-03-08,  and the result in expected units was 7.9 (vs 3.01). These results have some other differences (much more recent, includes start time, result as float instead of str). Overall, not a lot of confidence in our formula.


Add timezone setting

Currently concierge runs on an AWS server by default configured for UTC time. This makes the script bumper run at 5 pm our time instead of midnight. Which isn't a big deal, but our Slackbot will also be running on the same server and it'd be nice to post things in the morning in a timely manner.
This will set the correct timezone inside the Docker container. Since we're using a stripped down version of Linux (alpine) we need to install tzdata for timezones to work.
@ggetz

Thanks for the pull request @OmarShehata!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:sparkles: :sparkles: :sparkles:I'm the Cesium Concierge and I'm here to test things. :sparkles: :sparkles: :sparkles:

@OmarShehata UTC is pretty standard. Can we just convert our time to UTC and set the config accordingly?

I thought about that, but I feel like it's an unnecessary complication we have to deal with every time we set up any timed task  with our bot, compared to the convenience of thinking relative to our timezone.
I think this way automatically accounts for daylight savings too.

Ok, let's give it a test,


audit log H appears truncated

Hi,
I'm not sure if this is a bug, but I've been looking for hours and I can't find similar errors, in my fresh installation of modsecurity on nginx it seems that logs that part H is truncated. Missing fields: Action, Stopwatch, Stopwatch2, Response-Body-Transformed, Producer, Server, Engine-Mode (compared to modsecurity with apache logs)
Current config:
Ubuntu 22.04.5 LTS, nginx/1.18.0, modsecurity-v3.0.13, modsecurity-nginx-v1.0.3, crs 4.8.0
nginx log part H

example expected result

thank you

Hi @ag-luca,
the second format is used by only Apache with mod_security2 module. libmodsecurity3 does not contain that format at all.

libmodsecurity3 does not contain the same log format as modsecurity2 part H. Thanks @airween

libmodsecurity3 does not contain the same log format as modsecurity2 part H. Thanks @airween


Uncaught exception 'ReflectionException' with message 'Class bugsnag does not exist'

Upgrading Laravel 5.0.x to 5.1, when running composer update I get the following
  [RuntimeException]
  Error Output: PHP Fatal error:  Uncaught exception 'ReflectionException' with message 'Class bugsnag does not exist' in C:\Users\Jesse\Documents\Projects\cw5\vendor\laravel\framework\sr
  c\Illuminate\Container\Container.php:765
  Stack trace:
  #0 C:\Users\Jesse\Documents\Projects\cw5\vendor\laravel\framework\src\Illuminate\Container\Container.php(765): ReflectionClass->__construct('bugsnag')
  #1 C:\Users\Jesse\Documents\Projects\cw5\vendor\laravel\framework\src\Illuminate\Container\Container.php(645): Illuminate\Container\Container->build('bugsnag', Array)
  #2 C:\Users\Jesse\Documents\Projects\cw5\vendor\laravel\framework\src\Illuminate\Foundation\Application.php(651): Illuminate\Container\Container->make('bugsnag', Array)
  #3 C:\Users\Jesse\Documents\Projects\cw5\vendor\laravel\framework\src\Illuminate\Container\Container.php(1220): Illuminate\Foundation\Application->make('bugsnag')
  #4 C:\Users\Jesse\Documents\Projects\cw5\vendor\bugsnag\bugsnag-laravel\src\Bugsnag\BugsnagLaravel\BugsnagExceptionHandler.php(25): Illuminate\Container\Container->off in C:\Users\Jesse
  \Documents\Projects\cw5\vendor\laravel\framework\src\Illuminate\Container\Container.php on line 765
  PHP Fatal error:  Uncaught exception 'ReflectionException' with message 'Class bugsnag does not exist' in C:\Users\Jesse\Documents\Projects\cw5\vendor\laravel\framework\src\Illuminate\C
  ontainer\Container.php:765
  Stack trace:
  #0 C:\Users\Jesse\Documents\Projects\cw5\vendor\laravel\framework\src\Illuminate\Container\Container.php(765): ReflectionClass->__construct('bugsnag')
  #1 C:\Users\Jesse\Documents\Projects\cw5\vendor\laravel\framework\src\Illuminate\Container\Container.php(645): Illuminate\Container\Container->build('bugsnag', Array)
  #2 C:\Users\Jesse\Documents\Projects\cw5\vendor\laravel\framework\src\Illuminate\Foundation\Application.php(651): Illuminate\Container\Container->make('bugsnag', Array)
  #3 C:\Users\Jesse\Documents\Projects\cw5\vendor\laravel\framework\src\Illuminate\Container\Container.php(1220): Illuminate\Foundation\Application->make('bugsnag')
  #4 C:\Users\Jesse\Documents\Projects\cw5\vendor\bugsnag\bugsnag-laravel\src\Bugsnag\BugsnagLaravel\BugsnagExceptionHandler.php(25): Illuminate\Container\Container->off in C:\Users\Jesse
  \Documents\Projects\cw5\vendor\laravel\framework\src\Illuminate\Container\Container.php on line 765

Everything is where it needs to be, (service provider, facade).

Hi @Kryptonit3, would you mind sharing your composer.json file so I can try to recreate the issue?

I've had the same issue in my deployment before. It was resolved by setting the vendor directory writable. I was now doing an upgrade to Laravel 5.1 and seems like I get the same error locally. It does not matter if I run this as admin rights. I am using Windows 7 if it makes any difference.
$ php artisan clear-compiled
PHP Fatal error:  Uncaught exception 'ReflectionException' with message 'Class bugsnag does not exist' in C:\Users\lasleh\Dropbox\Development\schilling-rest\vendor\laravel\framework\src\Illuminate\Container\Container.php:736
Stack trace:
#0 C:\Users\lasleh\Dropbox\Development\schilling-rest\vendor\laravel\framework\src\Illuminate\Container\Container.php(736): ReflectionClass->__construct('bugsnag')
#1 C:\Users\lasleh\Dropbox\Development\schilling-rest\vendor\laravel\framework\src\Illuminate\Container\Container.php(626): Illuminate\Container\Container->build('bugsnag', Array)
#2 C:\Users\lasleh\Dropbox\Development\schilling-rest\vendor\laravel\framework\src\Illuminate\Foundation\Application.php(642): Illuminate\Container\Container->make('bugsnag', Array)
#3 C:\Users\lasleh\Dropbox\Development\schilling-rest\vendor\laravel\framework\src\Illuminate\Foundation\helpers.php(53): Illuminate\Foundation\Application->make('bugsnag', Array)
#4 C:\Users\lasleh\Dropbox\Development\schilling-rest\vendor\bugsnag\bugsnag-laravel\src\Bugsnag\B in C:\Users\lasleh\Dropbox\Development\schilling-rest\vendor\laravel\framework\src\Illuminate\Container\Container.php on line 736
PHP Fatal error:  Uncaught exception 'ReflectionException' with message 'Class bugsnag does not exist' in C:\Users\lasleh\Dropbox\Development\schilling-rest\vendor\laravel\framework\src\Illuminate\Container\Container.php:736
Stack trace:
#0 C:\Users\lasleh\Dropbox\Development\schilling-rest\vendor\laravel\framework\src\Illuminate\Container\Container.php(736): ReflectionClass->__construct('bugsnag')
#1 C:\Users\lasleh\Dropbox\Development\schilling-rest\vendor\laravel\framework\src\Illuminate\Container\Container.php(626): Illuminate\Container\Container->build('bugsnag', Array)
#2 C:\Users\lasleh\Dropbox\Development\schilling-rest\vendor\laravel\framework\src\Illuminate\Foundation\Application.php(642): Illuminate\Container\Container->make('bugsnag', Array)
#3 C:\Users\lasleh\Dropbox\Development\schilling-rest\vendor\laravel\framework\src\Illuminate\Foundation\helpers.php(53): Illuminate\Foundation\Application->make('bugsnag', Array)
#4 C:\Users\lasleh\Dropbox\Development\schilling-rest\vendor\bugsnag\bugsnag-laravel\src\Bugsnag\B in C:\Users\lasleh\Dropbox\Development\schilling-rest\vendor\laravel\framework\src\Illuminate\Container\Container.php on line 736

Here is my composer.json.
{
	"name": "laravel/laravel",
	"description": "The Laravel Framework.",
	"keywords": ["framework", "laravel"],
	"license": "MIT",
	"type": "project",
	"require": {
		"laravel/framework": "5.1.*",
		"league/fractal": "0.12.*@dev",
		"zircote/swagger-php": "2.*@dev",
		"guzzlehttp/guzzle": "~5.0",
		"predis/predis": "~1.0",
		"fale/isbn": "2.0.0",
		"cartalyst/sentry": "dev-feature/laravel-5",
		"lasselehtinen/elvis": "2.0.2",
		"venturecraft/revisionable": "1.*",
		"league/csv": "~7.0",
		"ezyang/htmlpurifier": "~4.6",
		"pda/pheanstalk": "~3.0",
		"bugsnag/bugsnag-laravel": "1.*",
		"morrislaptop/laravel-queue-clear": "~1.0"
	},
	"require-dev": {
		"behat/behat": "~3.0",
		"phpunit/phpunit": "~4.0",
		"phpspec/phpspec": "~2.1"
	},
	"autoload": {
		"classmap": [
			"database",
			"app/Traits"
		],
		"psr-4": {
			"SchillingRest\\": "app/"
		}
	},
	"autoload-dev": {
		"classmap": []
	},
	"scripts": {
		"post-install-cmd": [
			"php artisan clear-compiled",
			"php artisan optimize"
		],
		"post-update-cmd": [
			"php artisan clear-compiled",
			"php artisan optimize"
		],
		"post-create-project-cmd": [
			"php -r \"copy('.env.example', '.env');\"",
			"php artisan key:generate"
		]
	},
	"config": {
		"preferred-install": "dist"
	}
}

Same issue for me - composer.json:
{
  "name": "laravel/laravel",
    "description": "The Laravel Framework.",
    "keywords": ["framework", "laravel"],
    "license": "MIT",
    "type": "project",
    "require": {
      "php": ">=5.5.9",
      "laravel/framework": "^5.1",
      "illuminate/html": "~5.0",
      "jenssegers/mongodb": "dev-master",
      "predis/predis": "~1.0",
      "maatwebsite/excel": "^2.0",
      "barryvdh/laravel-debugbar": "^2.0",
      "guzzlehttp/guzzle": "^5.1",
      "bugsnag/bugsnag-laravel": "^1.0"
    },
    "require-dev": {
      "phpunit/phpunit": "~4.0",
      "phpspec/phpspec": "~2.1"
    },
    "autoload": {
      "classmap": [
        "database"
        ],
      "psr-4": {
        "aaaaaa\\": "app/"
      }
    },
    "autoload-dev": {
      "classmap": [
        "tests/TestCase.php"
        ]
    },
    "scripts": {
      "post-install-cmd": [
        "php artisan clear-compiled",
        "php artisan optimize"
        ],
      "post-update-cmd": [
        "php artisan clear-compiled",
        "php artisan optimize"
        ],
      "post-create-project-cmd": [
        "php -r \"copy('.env.example', '.env');\"",
        "php artisan key:generate"
        ]
    },
    "config": {
      "preferred-install": "dist"
    }
}

I got the same error, but what I did is something like this:

update composer.json
run composer update
receive that error

Then I followed instructions from http://laravel.com/docs/5.1/upgrade#upgrade-5.1.0 and did the following:

Update bootstrap/autoload.php
Create bootstrap/cache Directory
run composer update
no errors

$ composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Generating autoload files
Generating optimized class loader

@Gavrisimo that did the trick, thanks!

For what it's worth, this issue happened to me because the bootstrap/cache directory was not writable by the webserver. Thanks to @Gavrisimo for the tip.


Lost some config files in scripts folder ;(

Because I indicate the dnsforwarder in .gitignore, so the config files with that name has been ignore too.

Resolved by 07c8bc1b0c388058aba3e1f5e07835c028862bb3


chore(main): release 0.14.0

:robot: I have created a release beep boop
0.14.0 (2024-09-09)
Features

remove config and stas-config (61818ca)

Bug Fixes

add default on ct2_dir option (6073139)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.14.0
:sunflower:


Core implementation and auto-test of generic-reduction

This is core the implementation of the generic_reduction. The generic_reduction provides the functionality of generic tensor reduction similar to what provided by cudnnReduceTensor(), and it is based on the composable-kernel facility available with MIOpen. The core implementation include
four commits:

Tiny adding/changes to composable_kernel to support generic-reduction.
Kernel-layer implementation of generic-reduction, which includes the source of four kernels. kernel wrapper and some common helper functions.
Implementation of host-layer c++ interface (miopenReduceTensorDescriptor class) for generic-reduction.
Auto-test support (#>make check) for generic-reduction, which include an c++ file providing verifying testing of the generic-function function and also some host-layer helper functions.

Four reduction methods are implemented by the kernels which are called DirectThreadwise, DirectWarpwise, Blockwise, MultBlockwise. The selection of which reduction method is based on the specification of the reduction problem(the input tensor description and the dimensions to reduce). And the reduction process is hierarchical (at most two layers), where the first-call of MultiBlockwise reduction will be followed by one of the three other reduction methods as second-call.
The following are some important source files explained:

src/reducetensor.cpp -- the host c++ interfaces for generic_reduction, in which the host-side codes compile, cache, find and launch the kernels
src/kernels/composable_kernel/include/kernel_algorithms/gridwise_generic_reduction.hpp -- the top layer kernel, which does tensor transformation and call one of the four xy_to_x kernels to do 2d to 1d tensor reduction
src/kernels/composable_kernel/include/kernel_algorithms gridwise_generic_2d_reduction_.hpp -- the four xy_to_x kernels representing four different reduction methods respectively
src/kernels/composable_kernel/src/kernel_wrapper/gridwise_generic_reduction.cpp -- the "global" entry of the all kernels, in which the compiler definitions are received and tensor descriptors are created to represent the reduction task.
test/reduce_test.cpp -- the auto-tester called by "#make check". The verification is done by comparing the device-based reduction result with that of host-based one. Various reduction cases are covered.

Looks like there are some coding issues:
http://micimaster.amd.com/blue/organizations/jenkins/MLLibs%2FMIOpen/detail/PR-302/1/pipeline
Also, please merge the latest develop and resolve merge conflicts.

Looks like there are some coding issues:
http://micimaster.amd.com/blue/organizations/jenkins/MLLibs%2FMIOpen/detail/PR-302/1/pipeline
Also, please merge the latest develop and resolve merge conflicts.

Fix and Merged

@fronteer This PR contains changes from other branches. This is resulting in 50+ files and 8K+ lines being shown as changed.
Please close this PR and create a branch and PR that contains only your changes. You can checkout the latest develop and apply your changes on top of it.

@fronteer This PR contains changes from other branches. This is resulting in 50+ files and 8K+ lines being shown as changed.
Please close this PR and create a branch and PR that contains only your changes. You can checkout the latest develop and apply your changes on top of it.

I see,  so very often I have to resubmit the PR in order to absorb updates from the latest upstream branch?


do-backup action not working on focal and jammy

After working on and fixing this bug 1, the do-backup action was still not working on focal and jammy.
For focal, the charm was built and run on focal. This was the error 2 in the debug logs while testing on serverstack (openstack cloud).
These were the commands I used for testing:
$ j add-model test-jba
$ j deploy ./jba.charm
$ j config juju-backup-all exclude-controller-backup=true
$ j config juju-backup-all<EMAIL_ADDRESS><EMAIL_ADDRESS># DB to be backed up
$ j deploy postgresql
$ j run-action juju-backup-all/leader do-backup --wait

For jammy, the charm was built and run on jammy as well. Changes from this MR were implemented 3. This was the error 4 in the debug logs while testing on serverstack.
There was a similar bug 5 reported on the snap where the do-backup action was hanging and it was fixed as part of this commit 6. But the pinned commit of the snap j-b-a used by the charm (in requirements.txt) does not have this fix. Even after modifying the requirements.txt to use the latest snap commit, this is the error on jammy 7. I've also deployed and verified that the backup action on the latest j-b-a snap is functioning correctly.
While testing the backup action of the charm on an lxd cloud, the error messages in the debug logs don't come up but the backup action still hangs nonetheless.
Another bug that was raised recently 8 might have similar root cause to this one.

(by dashmage)
Some more observations after testing with jammy on serverstack.
The final exception thrown is an asyncio.TimeoutError.
The error traceback in the debug logs point to this line of code 1 as the source of the error.

with connect_controller(controller_name) as controller:

The connect_controller function comes from the snap library code (jujubackupall.utils) 2 and runs the following command on the libjuju controller object.

run_async(controller.connect(controller_name))

As part of this commit 3, the snap uses a customrun_async defined in jujubackupall/async_handlers.py4. Currently the pinned commit of the snap library used by the charm (in requirements.txt) does not have this fix and fails the backup action. But even after including the commit with this fix, the backup action still fails.


Doesn't work with the last version of mosquitto

docker-compose.yml file worked perfectly until 10 days ago. The lastest version of mosquitto container leads now to this error :
Error: Address not available  :  (https://github.com/eclipse/mosquitto/issues/2040) .
I had to use go back to eclipse-mosquitto:1.5 to make it work.
mosquitto:
image: eclipse-mosquitto:1.5
ports:
- 1883:1883

eclipse-mosquitto:2.0 has breaking changes: https://mosquitto.org/blog/2020/12/version-2-0-0-released/
In order to get this working with v2 you have to add the following settings to mosquitto.conf:
listener 1883
allow_anonymous true

I have fixed the version to :1.6 so that the issue is fixed for now. @GinterP would you like to make a pull-request, updating Mosquitto to v2 + adding the above config?

I have added a pull request: #40

I've merged #40 :+1:


Marketplace Coming Soon Page

Rather than taking the user to the dashboard, it would nice if we could direct them to a page similar to screenshot below when a user clicks on the marketplace link in the nav bar.

@dstraffon Any thoughts on using a more generic image rather than Duro Dogs here? I'm open either way... I think most projects would just remove the marketplace page at this point anyways since the functionality isn't there yet

good catch. think you're right that'll probably be removed by most, but still think it's smart to replace the DD logo with something more generic just to avoid confusion for users who might assume it is a "duro dog sample app" rather than asset layer based.
attaching an alternative option below


LLMaaJ implementation of MLCommons' simple-safety-tests

LLM-as-a-Judge implementation of MLCommons' simple-safety-tests
Signed-off-by: bnayahu<EMAIL_ADDRESS>

@OfirArviv can you please check the failed test? I think it relates to one of your changes.

@OfirArviv can you please check the failed test? I think it relates to one of your changes.

I'll fix the tests


perf: Unify XHR requests to fetch.

During my practice of how to use service-worker, I found that the XHR in this part seemed abrupt since all the other parts used fetch.

@googlebot I signed it!


Wrong audio format in ffmpeg export

there was this russian user in corrscope's server 3 months ago who reported a bug
and posted taskmgr screenshots, which are unusable because taskmgr truncates command lines
and they're no longer in the server, and i cannot reproduce the bug
if you ever see this, poke me to fix it


Mark case classes final

Co-authored-by: Andrea Magnorsky<EMAIL_ADDRESS>Adds the final modifier to case classes that are not already final or sealed abstract. Exceptions listed below:

TimedMatcher in /testing/src/main/scala/org/http4s/testing/RunTimedMatchers.scala
Anything under a src/test path

Adding the final or sealed abstract modifiers to the following case classes fails to compile, so these have also been excluded from this refactor:

/core/src/main/scala/org/http4s/parser/StrictTransportSecurityParser.scala:  private case class StrictTransportSecurityParser(override val input: ParserInput)
./examples/blaze/src/main/scala/com/example/http4s/blaze/demo/server/endpoints/JsonXmlHttpEndpoint.scala:  case class Person(name: String, age: Int)

Fixes #2074

Wonderful, thank you!  Do you happen to remember the nature of the compile errors on the others?  If not, I can reproduce easily enough.


[Question] Custom SDK doesn't show under 'Dependencies -> SDK' node in VS

Is this the correct behavior that a custom SDK, like NoTargets doesn't show under the Dependencies -> SDK node in Visual Studio?
Perhaps two points I see:

When using a custom SDK and define this like the project XML tag like

<Project Sdk="MyCompany.MyProduct.SDK/2018.1.0-preview3">
...

then we cannot display and update the SDK inside Visual Studio and the NuGet Package Manager. Both don't see and detect the custom SDK.

When using a custom SDK and define it with

...
<ItemGroup>
  <PackageReference Include="MyCompany.MyProduct.SDK" Version="2018.1.0-preview3" PrivateAssets="All" />
</ItemGroup>
...

then it be displayed and is updateable from NuGet Package Manager inside Visual Studio.

I think you should move this to https://github.com/dotnet/project-system/issues as that is the probably where the fix would go.  This repository only contains the actual SDKs and not the MSBuild or Visual Studio implementation of how they are used.

I'm closing this in favor of https://github.com/dotnet/project-system/issues/3463


[FEAT]logseq style flashcard

logseq style flashcard use #card tag and indentation to generate flashcards so it can keep the structure of the note more clear. Say if you review this in vscode, indentation can be a bit better than '?' or '??', i think. logseq falshcard style described here

It's an interesting format but it'd take quite some work to do. You'd need to extend the parser, essentially. If you want to try this, I'm happy to provide some guidance.

It's an interesting format but it'd take quite some work to do. The work itself is easy, just that there's much to do. You'd need to extend the parser, essentially. If you want to try this, I'm happy to provide some guidance.

Thanks, I've been tied up with my paper lately, I'll let you know when I got the time

Could this be implemented more easily by tagging headers? For example:
# Some big topic

## A smaller topic that I want to be also a flashcard #card

This will be the back of the card, and with it all the content in this subheading.

Including this

## This is not included in the previous card

Lorem ipsum

## A new card #card

...

With logseq being an outliner I think it makes it easy to structure it hierarchically anywhere. Within obsidian, the hierarchical primitive is the header, and I think respecting that removes a lot of complexity and makes things more organic.


Disable logging in with organization token

Hello 👋 This PR solves this issue #658. I looked into code to see where the user might login and where tokens are checked. I've seen three cases:

When the token in the folder is retrieved (when user doesn't give it)
When user logs in through CLI or notebook (_login)
When user passes the token directly (which are checked inside repository related functions that are used in places like mixins) like so:

        if token is None:

            token = self._validate_or_retrieve_token()

       elif isinstance(token, str):

          if token.startswith("api_org"):
              raise ValueError("You must use your personal account token for login.")
          elif not self._is_valid_token(token):
              if self._is_valid_token(name):
                  warnings.warn(
                      "`create_repo` now takes `token` as an optional positional argument. "
                     ....

We also check inside validate_or_retrieve token in case the token pulled is organization token.
So I added checks there and wrote tests for those three cases too.
cc: @osanseviero

I refactored & tested but will check if there's nits to do on Monday 🙂

I don't see anything else to refactor. I just have one question.
What is the reason behind this in upload_file? (below is initial version)
elif not self._is_valid_token(token):
 if self._is_valid_token(path_or_fileobj):

Do people pass tokens in paths or files? I refactored assuming that. (it didn't make much sense to me though) @osanseviero

What is the reason behind this in upload_file? (below is initial version)

I believe this is there only for backward compatibility. At some point the order of args were changed, and therefore this makes sure the older order is still accepted.

One could argue that the refactoring could or should have been a separate PR. But I'm glad this is done now.

Note that this PR reverts docstrings changes needed for the new documentation (e.g. using *optional*). You can see it in the diff


Release v0.5.1

What's Changed

FI-3097: Maintain checkbox label colors on error by @AlyssaWang in https://github.com/inferno-framework/inferno-core/pull/537
Fi 2962 execute outputters by @Shaumik-Ashraf in https://github.com/inferno-framework/inferno-core/pull/541
FI-3469: Use provided auth input options by @AlyssaWang in https://github.com/inferno-framework/inferno-core/pull/560
FI-3475: Unit testing improvements by @Jammjammjamm in https://github.com/inferno-framework/inferno-core/pull/559
FI-3023: Add default env vars and documentation to validator dockerfile by @dehall in https://github.com/inferno-framework/inferno-core/pull/562
Fix Inferno::Entities::TestSession docs by @Shaumik-Ashraf in https://github.com/inferno-framework/inferno-core/pull/563

Full Changelog: https://github.com/inferno-framework/inferno-core/compare/v0.5.0...v0.5.1

Update CHANGELOG.md

Thanks for the catch


clock_info: prepend swipe listener if possible

attempt to fix https://github.com/espruino/BangleApps/issues/3355

Thinking about this more, I suppose it's a good change to have since we want to be the first listener always, as when we don't have focus we're totally "transparent", if you will:
https://github.com/espruino/BangleApps/blob/b934653ff0c91fe649f9add2068de2fbb7e65d2d/apps/clock_info/lib.js#L256

Yes I think something like this should go in. I was thinking maybe wait a week as to not conflate some bug that might arise. But the risk feels small so we could also just go ahead.

Yeah I think we merge it, it's low risk

I'll merge this now then.


AAudio samples should close their audio stream on pause (and open on resume)

This sample has been deprecated/archived (check README for more information on newer samples related to this technology).
As recommended by GitHub, we are closing all issues and pull requests.


Does this has E2E cases?

It seems that all request are processed by sqlite by default ? (in src/network/postgres/postgres_network_commands.cpp)
Any way to use terrier itself to make the new comer be involved quickly ?

Removing sqlite is a WIP. See #634


Failing Request Test Draft

This is a draft of how failing request test support may be added in a way that will support failing requests for both server and client implementations.
This has a few issues & required cleanups, just want to see if we're directionally on the same page.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

CI is failing on some checkstyle issues: Import ordering, an unused import, missing copyright header and wrong copyright year, and line lengths exceeding 120 chars.

The idea of defining negative protocol tests are interesting, but do we have a use case in mind for them? I also think if we added them, it might be easier to add them to the existing traits.

yeah can close, I think adding a boolean to the existing traits is probably better.


Add style

#In this feature I added the following

Add styling files to match with the zipline design.
Add react-icons package to the project.
Remove existing default styling file  app.css from the project.
Update the README with the current progress of the project.

Status: Invalid 🔴
Hi @yosaddis 🙋♀,
While you made a great effort in this project, I can't review your code.
Invalid Code Review Request
You have submitted a project that has a README that is not professional. Here is a point to consider when documenting your README.

Kindly delete the live demo section if the application is not deployed. If project requirements say to deploy the project, the section should be restored and the link updated. There should not be any broken links in the README file.

Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers 🥂  and Happy coding!!! 👯
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Remember to tag me @KDlamini  in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.

Hi
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.

Invalid Code Review Request
You have submitted a project, that has unrelated texts on your README file. Kindly update the related area below with the correct project name.

Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


CC3XX: Add asym sign/verify and key generation entry points

Signing/Verification and key generation enabled in wrapper
Needs another patch in TF-M to include the
header files in the CC3XX file

Signed-off-by: Georgios Vasilakis<EMAIL_ADDRESS>

This is ready to merge. Will merge once I get the other patch in TF-M merged to avoid compilation issues.


nixos/paperless: fix start with latest systemd

Description of changes

After the last systemd update, paperless didn't start at all (see linked issue for details). I'm not sure whether this is the best approach, but imho it should be fixed, and then we can find the best solution.
fixes  #258823
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Also tested manually with postgresql.

Just to mention it, IMO ProtectSystem=true provides less isolation than TemporaryFileSystem=/, because it bind-mounts all kinds of paths and thus makes them visible to the service. For example all of /etc and /var/lib are now visible to paperless, before it could only see the things it actually needed.

The test passes for me. The changes look good but I'd like to ensure that we aren't breaking the optional redis support that previously had some unit configurations. Can you add that as another configuration within the same nixos test or add another?

Actually redis support is already tested: Redis is not optional, but necessary for the task queue. I added an additional test, tetsing that the optional postgres connection works.

Just to mention it, IMO ProtectSystem=true provides less isolation than TemporaryFileSystem=/, because it bind-mounts all kinds of paths and thus makes them visible to the service. For example all of /etc and /var/lib are now visible to paperless, before it could only see the things it actually needed.

I was also able to see the whole of the Nix store. Not just what it needed. The bind mounts we had might be less surface than what this option provides but IMO we should either invest in proper composable isolation for services or stick with the systemd facilities. Cargo-culting a list of options from one service to the next will continuously run into these kinds of issues. Permissions should be opt-in and not opt-out :(

Thanks for looking into this! Some fixups.

@ofBorg build paperless-ngx.tests


test_integration.py: A number of the tests were out of date, specifically those dealing wi…

…th DidlMusicTrack being a dictionary and not a an object.
Other small problems, like the queue being 0 based now where it wasn't before.  All tests run, All tests still test their original materials.
Comments and docstrings have been updated where appropriate.  Closes issue #342

Thanks


Optimize method saveDataURIAsFile

The method ipfsService.saveDataURIAsFile seems sub-optimal.
I haven't had time to test thoroughly on Node and Browser but we should be able to replace it with something that does not involve converting every single byte into an Uint8Array.
Something like this:
 async saveDataURIAsFile(dataURI) {
    let binary
    if (typeof Blob === 'undefined') {
      binary = new Buffer(dataURI.split(',')[1], 'base64')
    } else {
      const mimeString = dataURI
        .split(',')[0]
        .split(':')[1]
        .split(';')[0]
      const data = new Buffer(dataURI.split(',')[1], 'base64')
      binary = new Blob([data], {type: mimeString})
    }
    return await this.saveFile(binary)
  }

While doing that, we should add some unit test on the back-end for uploading Data URI.
Here is a snippet for creating a Data URI for an image:
      const imageBin = fs.readFileSync(imagePath)
      const imageBase64 = new Buffer(imageBin).toString('base64')
      const contentType = imagePath.endsWith('jpg')
        ? 'image/jpeg'
        : 'image/png'
      const medium = {
        url: `data:${contentType};base64,${imageBase64}`,
        contentType: contentType
      }

I tested my suggestion on both Node and Chrome browser. But I agree more testing on different type of browsers would make me feel more confident...
I'm actually not clear on why we need to use Blob on browser... Why not passing a Buffer to the saveFile() method in all cases ?

I think browsers don't have Buffer?


Update env_logger to mitigate RUSTSEC-2021-0145

This dependency update removes usage of the unmaintained and unsound atty crate.

Thanks! LGTM but could you also update http3_tests please? https://github.com/cloudflare/quiche/blob/master/tools/http3_test/Cargo.toml#L13, https://github.com/cloudflare/quiche/blob/master/tools/http3_test/tests/httpbin_tests.rs#L186 and https://github.com/cloudflare/quiche/blob/master/tools/http3_test/tests/httpbin_tests.rs#L208

Sure, no problem. I guess it didn't catch this because it was explicitly excluded from the workspace.

Great, thanks @PSUdaemon!


Redirect to non-www via JS

This is bad for SEO, but since SEO is not of our concern(*), we can just do the redirect in JS. This follows the pattern for the non-http-redirect right above.
(*) With Google Webmaster Tools it would also be possible to specify a primary domain to solve the duplicate content problem.
This solves https://github.com/mapbox/osmcha-frontend/issues/441
This script is based on https://stackoverflow.com/a/47281530

:clap: :clap: :clap: @tordans thank you for this idea :bow: . While serving redirects from the backend still seems to be a problem, to me, this seems like the best way forward. Will leave it to other folks to decide.
cc @willemarcel - I think this would be a good solution, if it seems okay to you.


Support common format geo point

Description
Currently, we only support geo point in the format of an object with a latitude and longitude, this PR aims to expand our support to all common formats that are described in OpenSearch doc.
Issues Resolved
#1432
Check List

[x] New functionality includes testing.

[x] All tests pass, including unit test, integration test and doctest

[x] New functionality has been documented.

[x] New functionality has javadoc added
[x] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@dai-chen you might be interested in this :) Could you please take a look when you get a chance?

The build failures contains low code test coverage: Execution failed for task ':opensearch:jacocoTestCoverageVerification'. Please run ./gradlew build in local and check the jacoco report file.

test

Seems the workflows were not triggered correctly. @bugmakerrrrrr Could u merge latest change from main and re-run test? (try to avoid force-push)

After rebasing the main branch, it appears that I have to perform a force push.

You can git merge latest upstream/main to your local dev branch then push to your origin/[dev branch].

Unit tests passed, fundamentally LGTM, @bugmakerrrrrr could you add a new IT similar to integ-test/src/test/java/org/opensearch/sql/sql/DateTimeFormatsIT.java?

@LantaoJin @dai-chen can we merge this?

@penghuo do you have a chance to review this?

@bugmakerrrrrr  could u help resolve conflict and submit backport PR to 2.x. https://github.com/opensearch-project/sql/pull/2801#issuecomment-2263318211

@bugmakerrrrrr could u help resolve conflict and submit backport PR to 2.x. #2801 (comment)

#2896


Browser tests aren't running in TeamCity CI

Our browser tests aren't running on every build in TeamCity. The tests just silently no-op if there are no suitable browsers, and some agents don't have the right browsers. We should:

Change the tests to fail loudly if no browsers are available when running on the CI
Install at least a browser on each TeamCity agent

Note: The tests are running on VSTS so we have some coverage.

This is fixed


Symbol’s value as variable is void: doom-neotree-folder-size

This is caused when installing doom-themes from Melpa with all-the-icons.
I had to set it manually
(use-package doom-themes
  :config
  (load-theme 'doom-one t)
  (require 'doom-neotree)
  (setq  doom-neotree-folder-size 120))

Aah, I derped hard and accidentally removed a variable declaration. I've fixed it in the latest push.

Thanks!

By the way, if you (or anyone) still has this problem, it can be fixed by adding (defvar doom-neotree-folder-size 1.1) to your emacs.d for the time being.

Yup, i set it (setq  doom-neotree-folder-size 120) but i didn't know it was a float value... I also think that 1.1 is a little too small, maybe 1.3 - 1.5 might work better.

Either float or integer will work actually (hadn't occurred to me!). Feel free to customize it though (that's what it's there for). I'm on a small 13' laptop so it seemed like a good default.
Would you mind showing me a screenshot of your settings? I've been worried about how it would look on other people's setups.

Sure... on 1.5 it looks like this:

Fantastic, good to know it came out well. Thanks!

Yup... however, my previous manual installation which i copied off your emacs.d had the folder icon color as blue. Could you please add an option to customize that? i can create a separate issue for this if needed.

Could you please add an option to customize that?
Certainly.

i can create a separate issue for this if needed.
Please do. It makes its easier for others to search for these things.


linked to site generates error

I click on the site linked to at the top of the repo "https://www.versionbot.com" in either google chrome or safari and I see a page for a few seconds then it is replaced with this text:
An error occurred loading this page's template. More information is available in the console.

Hey there @simbo1905 	This is a nasty bug introduced in React-static 7.2.0. For now, we've pinned the dependency to 7.1.0 and will upgrade when it's been resolved.
Thanks!


Add a JsonWrapperArrayWriter

Just like the XmlWrapperTagWriter, some use cases require the JSON output records to be wrapped in an array, like:
[
 {object1},
 {object2},
 {object3}
]

The idea is to provide a job listener that adds [ and ] around the JSON output records.
TODO: Add a sample on how to generate this kind of output ( marshaller + writer + arraywrapper).

This is not possible with the current design as there is no way to detect the last record and NOT write the last separator.
Here is a failed attempt to detect the last record (by adding a flag in the header):
attempt_to_detect_the_last_record.txt
And an implementation of JsonWrapperArrayWriter with a sample app:
sample_for_issue_328.txt
It produces something like:
[
 {object1},
 {object2},
 {object3},
]

which is invalid due to the last invalid separator.


Failure when creating superuser

While executing command
docker exec -it cvat bash -ic 'python3 ~/manage.py createsuperuser'
I get this error

Traceback (most recent call last):
File "/home/django/manage.py", line 21, in
execute_from_command_line(sys.argv)
File "/usr/local/lib/python3.5/dist-packages/django/core/management/init.py", line 381, in execute_from_command_line
utility.execute()
File "/usr/local/lib/python3.5/dist-packages/django/core/management/init.py", line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/local/lib/python3.5/dist-packages/django/core/management/base.py", line 323, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/local/lib/python3.5/dist-packages/django/contrib/auth/management/commands/createsuperuser.py", line 61, in execute
return super().execute(*args, **options)
File "/usr/local/lib/python3.5/dist-packages/django/core/management/base.py", line 361, in execute
self.check()
File "/usr/local/lib/python3.5/dist-packages/django/core/management/base.py", line 390, in check
include_deployment_checks=include_deployment_checks,
File "/usr/local/lib/python3.5/dist-packages/django/core/management/base.py", line 377, in _run_checks
return checks.run_checks(**kwargs)
File "/usr/local/lib/python3.5/dist-packages/django/core/checks/registry.py", line 72, in run_checks
new_errors = check(app_configs=app_configs)
File "/usr/local/lib/python3.5/dist-packages/django/core/checks/urls.py", line 40, in check_url_namespaces_unique
all_namespaces = _load_all_namespaces(resolver)
File "/usr/local/lib/python3.5/dist-packages/django/core/checks/urls.py", line 57, in _load_all_namespaces
url_patterns = getattr(resolver, 'url_patterns', [])
File "/usr/local/lib/python3.5/dist-packages/django/utils/functional.py", line 80, in get
res = instance.dict[self.name] = self.func(instance)
File "/usr/local/lib/python3.5/dist-packages/django/urls/resolvers.py", line 584, in url_patterns
patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
File "/usr/local/lib/python3.5/dist-packages/django/utils/functional.py", line 80, in get
res = instance.dict[self.name] = self.func(instance)
File "/usr/local/lib/python3.5/dist-packages/django/urls/resolvers.py", line 577, in urlconf_module
return import_module(self.urlconf_name)
File "/usr/lib/python3.5/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 986, in _gcd_import
File "", line 969, in _find_and_load
File "", line 958, in _find_and_load_unlocked
File "", line 673, in _load_unlocked
File "", line 665, in exec_module
File "", line 222, in _call_with_frames_removed
File "/home/django/cvat/urls.py", line 28, in
path('', include('cvat.apps.engine.urls')),
File "/usr/local/lib/python3.5/dist-packages/django/urls/conf.py", line 34, in include
urlconf_module = import_module(urlconf_module)
File "/usr/lib/python3.5/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 986, in _gcd_import
File "", line 969, in _find_and_load
File "", line 958, in _find_and_load_unlocked
File "", line 673, in _load_unlocked
File "", line 665, in exec_module
File "", line 222, in _call_with_frames_removed
File "/home/django/cvat/apps/engine/urls.py", line 7, in
from . import views
File "/home/django/cvat/apps/engine/views.py", line 50, in
import cvat.apps.dataset_manager.task as DatumaroTask
File "/home/django/cvat/apps/dataset_manager/task.py", line 24, in
from datumaro.components.project import Project, Environment
File "/home/django/datumaro/datumaro/components/project.py", line 8, in
import git
File "/usr/local/lib/python3.5/dist-packages/git/init.py", line 38, in
from git.exc import *                       # @NoMove @IgnorePep8
File "/usr/local/lib/python3.5/dist-packages/git/exc.py", line 9, in
from git.compat import UnicodeMixin, safe_decode, string_types
File "/usr/local/lib/python3.5/dist-packages/git/compat.py", line 16, in
from gitdb.utils.compat import (
ImportError: No module named 'gitdb.utils.compat'

Should be fixed by #1146

Thanks, I will give it a try

Nope, still not working

Traceback (most recent call last):

File "/usr/local/lib/python3.5/dist-packages/django/db/backends/base/base.py", line 217, in ensure_connection
self.connect()
File "/usr/local/lib/python3.5/dist-packages/django/db/backends/base/base.py", line 195, in connect
self.connection = self.get_new_connection(conn_params)
File "/usr/local/lib/python3.5/dist-packages/django/db/backends/postgresql/base.py", line 178, in get_new_connection
connection = Database.connect(**conn_params)
File "/usr/local/lib/python3.5/dist-packages/psycopg2/init.py", line 130, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
psycopg2.OperationalError: could not translate host name "cvat_db" to address: Temporary failure in name resolution
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/django/manage.py", line 21, in
execute_from_command_line(sys.argv)
File "/usr/local/lib/python3.5/dist-packages/django/core/management/init.py", line 381, in execute_from_command_line
utility.execute()
File "/usr/local/lib/python3.5/dist-packages/django/core/management/init.py", line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/local/lib/python3.5/dist-packages/django/core/management/base.py", line 323, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/local/lib/python3.5/dist-packages/django/contrib/auth/management/commands/createsuperuser.py", line 61, in execute
return super().execute(*args, **options)
File "/usr/local/lib/python3.5/dist-packages/django/core/management/base.py", line 363, in execute
self.check_migrations()
File "/usr/local/lib/python3.5/dist-packages/django/core/management/base.py", line 453, in check_migrations
executor = MigrationExecutor(connections[DEFAULT_DB_ALIAS])
File "/usr/local/lib/python3.5/dist-packages/django/db/migrations/executor.py", line 18, in init
self.loader = MigrationLoader(self.connection)
File "/usr/local/lib/python3.5/dist-packages/django/db/migrations/loader.py", line 49, in init
self.build_graph()
File "/usr/local/lib/python3.5/dist-packages/django/db/migrations/loader.py", line 212, in build_graph
self.applied_migrations = recorder.applied_migrations()
File "/usr/local/lib/python3.5/dist-packages/django/db/migrations/recorder.py", line 73, in applied_migrations
if self.has_table():
File "/usr/local/lib/python3.5/dist-packages/django/db/migrations/recorder.py", line 56, in has_table
return self.Migration._meta.db_table in self.connection.introspection.table_names(self.connection.cursor())
File "/usr/local/lib/python3.5/dist-packages/django/db/backends/base/base.py", line 256, in cursor
return self._cursor()
File "/usr/local/lib/python3.5/dist-packages/django/db/backends/base/base.py", line 233, in _cursor
self.ensure_connection()
File "/usr/local/lib/python3.5/dist-packages/django/db/backends/base/base.py", line 217, in ensure_connection
self.connect()
File "/usr/local/lib/python3.5/dist-packages/django/db/utils.py", line 89, in exit
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/usr/local/lib/python3.5/dist-packages/django/db/backends/base/base.py", line 217, in ensure_connection
self.connect()
File "/usr/local/lib/python3.5/dist-packages/django/db/backends/base/base.py", line 195, in connect
self.connection = self.get_new_connection(conn_params)
File "/usr/local/lib/python3.5/dist-packages/django/db/backends/postgresql/base.py", line 178, in get_new_connection
connection = Database.connect(**conn_params)
File "/usr/local/lib/python3.5/dist-packages/psycopg2/init.py", line 130, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
django.db.utils.OperationalError: could not translate host name "cvat_db" to address: Temporary failure in name resolution

+1, this does not seem to be resolved

@nicolocarissimi, looks like another issue, could you please attach output from docker ps -a?

@azhavoro, you are right, it's a different issue.
Here's the output from docker ps -a

CONTAINER ID        IMAGE                COMMAND                  CREATED             STATUS                              PORTS                              NAMES
3fd037835add        nginx                "nginx -g 'daemon of…"   16 hours ago        Up 16 hours                         <IP_ADDRESS>:7080->80/tcp               cvat_ui
0de971f3ca4c        cvat                 "/usr/bin/supervisord"   16 hours ago        Up 16 hours                         <IP_ADDRESS>:8080->8080/tcp, 8443/tcp   cvat
171ba6ce9f52        postgres:10-alpine   "docker-entrypoint.s…"   16 hours ago        Restarting (1) About a minute ago                                      cvat_db
12b04e0a3c33        redis:4.0-alpine     "docker-entrypoint.s…"   16 hours ago        Up 16 hours                         6379/tcp                           cvat_redis

It seems cvat_db keeps restarting.

Thanks, your issue is https://github.com/opencv/cvat/issues/1145, we will fix it soon.

Thanks, #1145 solved my problem. I'm closing this one.

I'm not sure if this is a separate issue or not, but I tried the 'trust' fix and it still didn't solve it. I get a similar error and my postgress container keeps restarting. Except for permission issues when looking at docker logs cvat_db
fixing permissions on existing directory /var/lib/postgresql/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default timezone ... UTC
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
running bootstrap script ... ok
sh: locale: not found
2021-08-06 18:18:11.318 UTC [32] WARNING:  no usable system locales were found
performing post-bootstrap initialization ... ok

PostgreSQL Database directory appears to contain a database; Skipping initialization

2021-08-06 18:18:12.884 UTC [1] FATAL:  data directory "/var/lib/postgresql/data" has wrong ownership
2021-08-06 18:18:12.884 UTC [1] HINT:  The server must be started by the user that owns the data directory.

It seems like when looking at other issues like here that it's an issue with mounting windows volumes. I assume that refers to NTFS volumes, and even though I'm running arch I have an NTFS volume mounted for my docker data-root. This might be the issue because as soon as I switched my data-root back to my ext4 drive it worked fine.


replace murmur hash with farmhash

Addresses #24
Not sure if more communication around this potentially being a breaking change is necessary

Also tests are failing on scalastyle https://travis-ci.org/spotify/ratatool/jobs/378916482#L565

Codecov Report

Merging #92 into master will increase coverage by 0.15%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##           master      #92      +/-   ##
==========================================
+ Coverage   70.48%   70.63%   +0.15%
==========================================
  Files          24       24
  Lines        1047     1049       +2
  Branches      125      123       -2
==========================================
+ Hits          738      741       +3
+ Misses        309      308       -1

Impacted Files
Coverage Δ

...ala/com/spotify/ratatool/samplers/BigSampler.scala
64.76% <83.33%> (+0.81%)
:arrow_up:

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 251ba4a...d02c8b9. Read the comment docs.


Use travis to publish to bintray

Taking inspiration from [1] and [2], this PR automates publishing to bintray from travis-ci. It works by publishing builds triggered by tags, allowing for the current jenkins bits to continue to work.
In order to trigger a release, push a tag eg pushing [3] resulted in [4], and [5]
It currently publishes a pretty sparse POM, and I'm sure there are lots of possible improvements, but this seemed like a reasonable start.
It's using my bintray creds to publish to the alphagov org on bintray. Shout if you want me to add a few more peoples bintray accounts to that org.
[1] http://bithacker.org/post/120996678805/publishing-artifacts-to-bintray-from-travis-ci
[2] https://github.com/bintray/bintray-examples/blob/master/gradle-bintray-plugin-examples/publications-example/build.gradle
[3] https://github.com/davidillsley/dropwizard-logstash/tree/1.0.0
[4] https://travis-ci.org/davidillsley/dropwizard-logstash/builds/210472908
[5] https://bintray.com/alphagov/maven-test/dropwizard-logstash/1.0.5-1.0.0

Looks good to me 👍

Looks good to me as well

@davidillsley I'd like you to add a few more accounts to that bintray org 😄

I admit this shout is a bit later than ideal...


npm linked modules resolve ProvidePlugin dependencies wrong

I have Project, which depends on a node module Dep. Dep uses fetch in its source code, but doesn't provide a polyfill. Project provides a polyfill for fetch like so:
  plugins: [
    new webpack.ProvidePlugin({
      fetch: 'isomorphic-fetch'
    })
  ]

I'm making changes to Dep, so I linked it in using npm link. Dep is now a symlink in my node_modules.
When I run a build webpack tries to resolve isomorphic-fetch from  Dep/node_modules instead of Project/node_modules, which throws an error because isomorphic-fetch doesn't exist there.
Webpack version: 1.13.0
Node version: 6.9.2
Temporary fix
I've added the following to my config to override the module resolution:
  resolve: {
    alias: {
      'isomorphic-fetch': path.join(__dirname, 'node_modules', 'isomorphic-fetch')
    }
  }

The provided module resolves relative to the injected file.
  plugins: [
    new webpack.ProvidePlugin({
      fetch: path.join(__dirname, 'node_modules', 'isomorphic-fetch')
    })
  ]

@sokra, how can I use your technique to connect to a specific javascript file in my node_modules directory?

Another solution is to use resolve.symlinks: false in your webpack config.
This prevents module resolution of symlinked packages from being relative to their actual location.


ovn-sbctl show returns empty output

I have ovn architecture running on the same node, just to be clear northbound DB and southbound DB, controller everything is running on the same node, now I think the problem can be

In my Architecture
or southbound DB configurations

Can you guys validate this architecture and Why I am getting output from northdb, but now southdb. attaching the outputs below

Don't know if this is valid still but I had an issue with the Open vSwitch configuration and thus ovn-controller wouldn't register itself as a Chassis with the SB DB. I fixed the OVS config and restarted ovn-controller and then it showed up in the SB DB. I was then able to provision a port to OVS and add the external-id so the SB DB would have a binding added on the right Chassis.


OSError: libcudart.so.7.5: cannot open shared object file: No such file or directory

I upgrade my nvidia drivers and cuda version;
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2016 NVIDIA Corporation
Built on Sun_Sep__4_22:14:01_CDT_2016
Cuda compilation tools, release 8.0, V8.0.44
When i finished all of it; i recompile the caffe and mxnet; the caffe work well,but the mxnet always remind me "OSError: libcudart.so.7.5: cannot open shared object file: No such file or directory", don't how to modify my configuration. Thank you;

export LD_LIBRARY_PATH=/path/to/cuda/lib

@piiswrong Thank you for your comments,my LD_LIBRARY_PATH is
echo $LD_LIBRARY_PATH
/usr/local/cuda-8.0/lib64/stubs:/usr/local/cuda-8.0/lib64;
my cuda version is 8.0,i'm confused about why the mxnet always remind me "cannot open shared object libcudart.so.7.5"?

Edit config.mk to make sure usecudapath point to cuda8.0 then rebuild
On Nov 14, 2016 9:29 PM, "xhniu"<EMAIL_ADDRESS>wrote:

@piiswrong https://github.com/piiswrong Thank you for your comments,my
LD_LIBRARY_PATH is
echo $LD_LIBRARY_PATH
/usr/local/cuda-8.0/lib64/stubs:/usr/local/cuda-8.0/lib64;
my cuda version is 8.0,i'm confused about why the mxnet always remind me
"cannot open shared object libcudart.so.7.5"?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dmlc/mxnet/issues/3829#issuecomment-260551276, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAiudIc7BJEtp5ES-7-bo3lcXhtqltarks5q-UNHgaJpZM4KyBWH
.

add the path to CUDA library to link and compile flag
if you have already add them to environment variable, leave it as NONE
USE_CUDA_PATH = /usr/local/cuda-8.0
My config.mk file /usr/local/cuda-8.0,i checked it again. There was no error when i rebuild the whole project. I'm not sure if there was any other configure file i should modify. Thank you. @piiswrong

@xhniu Have you solve your problem? I have a same problem. I edit config.mk to make sure usecudapath point to cuda8.0 then rebuild. But when I import mxnet in python, it still show error:
>>> import mxnet
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/congleng/work/deeplearning-tools/mxnet-cuda8/python/mxnet/__init__.py", line 7, in <module>
    from .base import MXNetError
  File "/home/congleng/work/deeplearning-tools/mxnet-cuda8/python/mxnet/base.py", line 46, in <module>
    _LIB = _load_lib()
  File "/home/congleng/work/deeplearning-tools/mxnet-cuda8/python/mxnet/base.py", line 38, in _load_lib
    lib = ctypes.CDLL(lib_path[0], ctypes.RTLD_GLOBAL)
  File "/home/congleng/local/anaconda2/lib/python2.7/ctypes/__init__.py", line 362, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: libcudart.so.7.5: cannot open shared object file: No such file or directory

why it always remind "cannot open shared object libcudart.so.7.5"?
@xhniu @piiswrong Can you give me some advices?
thank you in advance!

try pip install mxnet-cu80

@IvyGongoogle Have you solved your problem?

I was able to solve this issue by:
pip install mxnet-cu80
But the change I did - completely removed the mxnet git repo which I had downloaded. Seemed like that installation was over-riding the pip installation (NOTE that I was getting the same error as long as both were installed)

This issue is closed due to lack of activity in the last 90 days. Feel free to ping me to reopen if this is still an active issue. Thanks!
Also, do please check out our forum (and Chinese version) for general "how-to" questions.

@Alexander-flyer Hi, I have also encountered a similar problem here.
I'm using cuda-9.0, but mxnet keeps asking me to find libcudart.so.8.0.
Thought might be a problem with my opencv, can you tell me how you solved the problem?

conda install -c anaconda cudatoolkit==9.2 (I faced it with 9.2) solves it for me in an anaconda environment.
I am still trying to determine the reason.


swap resource group to a var and fix thumbprint typo

Signed-off-by: Robbie Page<EMAIL_ADDRESS>

@cephalin can you please do a test run on this script and let me know the outcome and i'll get it merged.

@rorpage Thanks for the contribution! We'll do some testing (all looks good, but always need to verify) and get this merged ASAP.

#sign-off @erickson-doug please merge.


Can't run pre-install on package if package is filtered out

Hello,
I have setup a filter so that any package with *.dev in the version is ignored by default.
While this works well in general, it has now made it impossible for me to build such a package if the package has unit tests running on pre-install, as it fails to resolve the environment for the tests.
Environment

OS windows
Rez version 2.104.9
Rez python version 3.7.9

To Reproduce

In config, add a filter to exclude dev packages package_filter = {'excludes': '*.dev'}
Setup a package, say test_rez_package and add tests meant to run on pre-install.
Set version to 1.0.0.dev
Attempt to build

Expected behavior
Package should build and run unit tests
Actual behavior
Build runs successfully, then tests try to kick in:
Running test: unit
----------------------------------

Resolving test environment: test_rez_package==1.0.0.dev pyest
17:32:20 ERROR    The test environment failed to resolve: Package could not be found:  test_rez_package==1.0.0.dev
[... Here are tests results saying how it all failed ...]
17:32:20 ERROR    PackageTestError: 1 tests failed; the installation has been cancelled

and the install directory gets deleted.
** Notes **
Is it actually a bug, or is it the filter doing its job? I'm unsure, but it sure is annoying.

I've done some thinking about this, and it might be tricky to to implement without changing any legacy behavior.
Instead, I might give a try to implement it as a new type of filter (to put in includes).
I don't know if there is a specific term used to describe requests with the '==' symbol, as described in the wiki:

package request
description
example versions within request

foo==2.0.0
Only version 2.0.0 exactly
foo-2.0.0

Assuming this is called an "exact" request, I would make a new filter exact_request(), which could be used to include packages if they match an exact request.
Assume the following filter:
package_filter = {
    'excludes': 'glob(*.beta)',
    'includes': 'exact_request()'
}

Assuming a package: foo, with versions foo-1.0.0 and foo-2.0.0.beta:

Running rez-env foo would resolve foo-1.0.0
Running rez-env foo-2.0.0.beta would give a resolve error
Running rez-env foo==2.0.0.beta would resolve to foo-2.0.0.beta

Someone could possibly add that in the excludes, which would exclude all exact requests, I don't know why they would, but they could.
In order to implement, the PackageFilter class would need some info about the request (an extra optional argument on the excludes() method?). It seems doable as only the solver ever calls the filter and it has a version_range available right there to pass to the the filter.
Any thoughts?

Another possible solution, in https://github.com/AcademySoftwareFoundation/rez/blob/master/src/rezplugins/build_process/local.py#L471,
do something like:
        package_filters = PackageFilterList.singleton
        package_filter.add_inclusion(variant.parent.as_exact_requirement())
        # run the tests, and raise an exception if any fail. This will abort
        # the install/release
        runner = PackageTestRunner(
            package_request=variant.parent.as_exact_requirement(),
            package_paths=package_paths,
            cumulative_test_results=self.all_test_results,
            stop_on_fail=True,
            verbose=1,
            package_filter=package_filter
        )

This should stay more localized to only the tests happening at build time, while not affecting other tests, closer to a bug fix than my previous comment which is more like a new feature.
The reason I did like the new filter in the previous comment is because I can also use it with rez-env in general for testing my packages.

The filter type you need already exists no?
https://github.com/AcademySoftwareFoundation/rez/blob/master/src/rez/package_filter.py#L450
.
Then:
package_filters = PackageFilterList.singleton.copy() # use copy don't

alter singleton!
package_filter.add_inclusion(RangeRule(variant.parent.as_exact_requirement
()))
...rest is the same...
On Tue, Sep 13, 2022 at 3:05 PM Erwan Leroy @.***>
wrote:

Another possible solution, in
https://github.com/AcademySoftwareFoundation/rez/blob/master/src/rezplugins/build_process/local.py#L471
,
do something like:
    package_filters = PackageFilterList.singleton
    package_filter.add_inclusion(variant.parent.as_exact_requirement())
    # run the tests, and raise an exception if any fail. This will abort
    # the install/release
    runner = PackageTestRunner(
        package_request=variant.parent.as_exact_requirement(),
        package_paths=package_paths,
        cumulative_test_results=self.all_test_results,
        stop_on_fail=True,
        verbose=1,
        package_filter=package_filter
    )

This should stay more localized to only the tests happening at build time,
while not affecting other tests, closer to a bug fix than my previous
comment which is more like a new feature.
The reason I did like the new filter in the previous comment is because I
can also use it with rez-env in general for testing my packages.
—
Reply to this email directly, view it on GitHub
https://github.com/AcademySoftwareFoundation/rez/issues/1374#issuecomment-1244902675,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMOUSRNATNHRN6HA4KS243V6ADRRANCNFSM6AAAAAAQIHW2JQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Yes indeed, this would work while editing the local build process, likely resolving the issue of aborted builds because of tests. (In short, direct fix to what I believe to be a bug)
My earlier idea about a different filter was sort of a new feature, which as far as I know doesn't currently exist. As I'm basing my development/alpha/beta workflow around filtered packages (because I never want them to resolve accidentally), right now I have to both explicitly request them, and add them to the inclusion list to resolve. With the new filter I was hoping to be able to ask "filter out all *.beta versions, unless explicitly requested", so that anywhere I could run "rez env my_package==0.0.1.beta" and it would resolve.

I don't think a new kind of filter is the way to go - having one that knows
about a ResolvedContext request seems a bit complex, but the main reason is
that such a filter would allow exact package requirements (as opposed to
user-defined requirements) to see dev versions too, and I don't think
that's right.
I have an alternative suggestion:

We add a new setting, default_no_filter_on_exact_request
We add analogous arg to ResolvedContext constructor, defaults to None (ie
inherit from setting)
If True, and package filter is not explicitly specified in
ResolvedContext constructor, then we use add_inclusion to add a
range-rule-inclusion for every exact request in the request list (ie we
make a copy of the default package filter, and add the inclusions there)

Benefits:

No new package filter impl
Backwards compatibility (new setting is False by default)
No chance of leaking into package requirements (which should always obey
the filter imo, exact requirement or not)
Explicitness (the filter stored into the rxt file will show that each
exact requirement has been explicitly allowed for all versions)

Thoughts?
On Thu, Sep 22, 2022 at 1:20 AM Erwan Leroy @.***>
wrote:

Yes indeed, this would work while editing the local build process, likely
resolving the issue of aborted builds because of tests. (In short, direct
fix to what I believe to be a bug)
My earlier idea about a different filter was sort of a new feature, which
as far as I know doesn't currently exist. As I'm basing my
development/alpha/beta workflow around filtered packages (because I never
want them to resolve accidentally), right now I have to both explicitly
request them, and add them to the inclusion list to resolve. With the new
filter I was hoping to be able to ask "filter out all *.beta versions,
unless explicitly requested", so that anywhere I could run "rez env
my_package==0.0.1.beta" and it would resolve.
—
Reply to this email directly, view it on GitHub
https://github.com/AcademySoftwareFoundation/rez/issues/1374#issuecomment-1253861957,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMOUSXFIMW43NKZRP3BFBLV7MRSDANCNFSM6AAAAAAQIHW2JQ
.
You are receiving this because you commented.Message ID:
@.***>

I don't think a new kind of filter is the way to go - having one that knows
about a ResolvedContext request seems a bit complex,
agreed, it also kind of breaks single responsibility principles
but the main reason is
that such a filter would allow exact package requirements (as opposed to
user-defined requirements) to see dev versions too, and I don't think
that's right.

You mean the requirements listed in package.py under requires or variant?
I think it would, but if somebody puts requires = ['foo==1.0.0.dev'] in their package.py, doesn't it mean they want that version to load?

I have an alternative suggestion:

We add a new setting, default_no_filter_on_exact_request
We add analogous arg to ResolvedContext constructor, defaults to None (ie
inherit from setting)
If True, and package filter is not explicitly specified in
ResolvedContext constructor, then we use add_inclusion to add a
range-rule-inclusion for every exact request in the request list (ie we
make a copy of the default package filter, and add the inclusions there)

Yes that was another thing that crossed my mind, but for some reason I thought adding a new filter would be less disruptive / controversial. Could you clarify this part: If True, and package filter is not explicitly specified in ResolvedContext constructor ?

Benefits:

No new package filter impl
yep
Backwards compatibility (new setting is False by default)
filter would also be backward compatible?
No chance of leaking into package requirements (which should always obey
the filter imo, exact requirement or not)
Wouldn't the setting still affect the requirements from a package? If I set the global setting to no filters on exact requests, and a package has it as an exact request, wouldn't it still resolve? I'm not sure I fully grasp the difference?
Explicitness (the filter stored into the rxt file will show that each
exact requirement has been explicitly allowed for all versions)
fair enough

Thoughts?

This would totally work for me, but just for the sake of conversation, I'm adding a con to this solution:

You wouldn't be able to do this type of filter:
package_filter:

excludes:

glob(*.beta)

excludes:

after(1429830188)
includes:

explicit_requirement()
(only allow explicit requirements for the timestamp filter, not the glob one)

Below.
On Fri, Sep 23, 2022 at 10:02 AM Erwan Leroy @.***>
wrote:

I don't think a new kind of filter is the way to go - having one that knows
about a ResolvedContext request seems a bit complex,
agreed, it also kind of breaks single responsibility principles
but the main reason is
that such a filter would allow exact package requirements (as opposed to
user-defined requirements) to see dev versions too, and I don't think
that's right.
You mean the requirements listed in package.py under requires or variant?
I think it would, but if somebody puts requires = ['foo==1.0.0.dev'] in
their package.py, doesn't it mean they want that version to load?

It probably does mean they want that, but it doesn't mean that I (being the
person creating my context) do. If I've filtered out dev packages, I don't
want them, unless I have requested one explicitly myself. As a user I want
a guarantee that my filter is respected, and if another package
requires something I don't want it to, I want my resolve to fail.

I have an alternative suggestion:

We add a new setting, default_no_filter_on_exact_request
We add analogous arg to ResolvedContext constructor, defaults to
None (ie
inherit from setting)
If True, and package filter is not explicitly specified in
ResolvedContext constructor, then we use add_inclusion to add a
range-rule-inclusion for every exact request in the request list (ie we
make a copy of the default package filter, and add the inclusions
there)

Yes that was another thing that crossed my mind, but for some reason I
thought adding a new filter would be less disruptive / controversial. Could
you clarify this part: If True, and package filter is not explicitly
specified in ResolvedContext constructor ?

If I call ResolvedContext(package_filter=...), that's explicit - I don't
think the package filter should be changed to allow your exact requests. If
it's not, and that new setting is True, I think it's reasonable to adapt
the filter as expected.

Benefits:

No new package filter impl
yep
Backwards compatibility (new setting is False by default)
filter would also be backward compatible?
No chance of leaking into package requirements (which should always
obey
the filter imo, exact requirement or not)
Wouldn't the setting still affect the requirements from a package? If
I set the global setting to no filters on exact requests, and a package has
it as an exact request, wouldn't it still resolve? I'm not sure I fully
grasp the difference?

Ah I should have made clearer, the default_no_filter_on_exact_request
setting would apply only to user requests, not package requests. I don't
know how to convey that without the setting name getting silly long.

Explicitness (the filter stored into the rxt file will show that each
exact requirement has been explicitly allowed for all versions)
fair enough

Thoughts?
This would totally work for me, but just for the sake of conversation, I'm
adding a con to this solution:

You wouldn't be able to do this type of filter:
package_filter:

excludes:

glob(*.beta)

excludes:

after(1429830188)
includes:

explicit_requirement()
(only allow explicit requirements for the timestamp filter,
not the glob one)

It's fine that this isn't supported imo - because exact=nofilter is only
supported in user requests, this is not an issue - you've either asked for
the exact dev version in your request, or you haven't. It's easy to reason
about.

—
Reply to this email directly, view it on GitHub
https://github.com/AcademySoftwareFoundation/rez/issues/1374#issuecomment-1255671261,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMOUSR4IANF4MHXHR6R733V7TXP3ANCNFSM6AAAAAAQIHW2JQ
.
You are receiving this because you commented.Message ID:
@.***>

Thanks for the clarifications, it does make more sense.
Would you agree that my original statement that a package being built and running its own tests should never get filtered out and that the current behaviour can be considered a bug?
The solution would then to do what you suggest, as well as setting the new ResolvedContext argument to True when running the pre-build tests?

I don't consider this a bug. That behavior was present before pre-install was introduced. If you have a dev package in your requires and simply run rez-test, it would be filtered out. It be a bug or not is up for debate I think but that's not important to this discussion. What's important is to focus on what should be the behavior and how we want to tackle that.

JC, I think Erwan is describing the case where the package itself (the one
getting its pre-install tests run) is a dev version - not that its
requirements are dev versions (which I agree should be filtered out).
In that specific case, I think this is a bug - it surely cannot be right
that the very package getting tested is getting filtered out of its own
test env.
On Fri, Sep 23, 2022 at 10:42 AM Jean-Christophe Morin <
@.***> wrote:

I don't consider this a bug. That behavior was present before pre-install
was introduced. If you have a dev package in your requires and simply run
rez-test, it would be filtered out. It be a bug or not is up for debate I
think but that's not important to this discussion. What's important is to
focus on what should be the behavior and how we want to tackle that.
—
Reply to this email directly, view it on GitHub
https://github.com/AcademySoftwareFoundation/rez/issues/1374#issuecomment-1255689540,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMOUSRL5NHGUVJZDOBL73LV7T4JHANCNFSM6AAAAAAQIHW2JQ
.
You are receiving this because you commented.Message ID:
@.***>

@JeanChristopheMorinPerso fair enough, I guess what I'm asking is should it always ignore the filter when running running on pre-install as it feels odd that you can't even finish the build if the package matches the conditions to be filtered out.
I think what I have in my 3rd post is very specific, and would only add the one package currently being built,  while setting no_filter_on_exact_request when running the pre-install tests might allow some others to also get resolved (if there are some other explicit requests for the test env).

I didn't follow the whole discussion, so sorry if I'm missing some details, but couldn't we just special case this instead of adding yet another setting?

We could yes - I brought up the setting because this has come up a few
times before (not necessarily in the context of test hooks).
I agree that simply fixing this issue directly is appropriate then. Erwan -
any reason we can't just update the filter with a range inclusion
specifically for this case?
Thx
A
On Fri, Sep 23, 2022 at 10:54 AM Jean-Christophe Morin <
@.***> wrote:

I didn't follow the whole discussion, so sorry if I'm missing some
details, but couldn't we just special case this instead of adding yet
another setting?
—
Reply to this email directly, view it on GitHub
https://github.com/AcademySoftwareFoundation/rez/issues/1374#issuecomment-1255695183,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMOUSUHFOUPBLWLOK2LK2LV7T5THANCNFSM6AAAAAAQIHW2JQ
.
You are receiving this because you commented.Message ID:
@.***>

What do you suggest?
I do like the new setting because it also stops me from having add an
include every time I want to resolve a dev package, although I guess that's
2 separate issues.

not able to build at all: critical and can be fixed specifically for that
case only
have the setting: quality of life, could be considered a new feature

On Thu, 22 Sep 2022, 19:59 allan johns, @.***> wrote:

We could yes - I brought up the setting because this has come up a few
times before (not necessarily in the context of test hooks).
I agree that simply fixing this issue directly is appropriate then. Erwan -
any reason we can't just update the filter with a range inclusion
specifically for this case?
Thx
A
On Fri, Sep 23, 2022 at 10:54 AM Jean-Christophe Morin <
@.***> wrote:

I didn't follow the whole discussion, so sorry if I'm missing some
details, but couldn't we just special case this instead of adding yet
another setting?
—
Reply to this email directly, view it on GitHub
<
https://github.com/AcademySoftwareFoundation/rez/issues/1374#issuecomment-1255695183
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAMOUSUHFOUPBLWLOK2LK2LV7T5THANCNFSM6AAAAAAQIHW2JQ
.
You are receiving this because you commented.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/AcademySoftwareFoundation/rez/issues/1374#issuecomment-1255751276,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJAV5BFI64MKSGBMKJGIV3V7UMKZANCNFSM6AAAAAAQIHW2JQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

I would fix specifically for this case - as you say, the setting is a
separate issue.
A
On Fri, Sep 23, 2022 at 1:33 PM Erwan Leroy @.***>
wrote:

What do you suggest?
I do like the new setting because it also stops me from having add an
include every time I want to resolve a dev package, although I guess that's
2 separate issues.

not able to build at all: critical and can be fixed specifically for that
case only
have the setting: quality of life, could be considered a new feature

On Thu, 22 Sep 2022, 19:59 allan johns, @.***> wrote:

We could yes - I brought up the setting because this has come up a few
times before (not necessarily in the context of test hooks).
I agree that simply fixing this issue directly is appropriate then.
Erwan -
any reason we can't just update the filter with a range inclusion
specifically for this case?
Thx
A
On Fri, Sep 23, 2022 at 10:54 AM Jean-Christophe Morin <
@.***> wrote:

I didn't follow the whole discussion, so sorry if I'm missing some
details, but couldn't we just special case this instead of adding yet
another setting?
—
Reply to this email directly, view it on GitHub
<

https://github.com/AcademySoftwareFoundation/rez/issues/1374#issuecomment-1255695183

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAMOUSUHFOUPBLWLOK2LK2LV7T5THANCNFSM6AAAAAAQIHW2JQ

.
You are receiving this because you commented.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
<
https://github.com/AcademySoftwareFoundation/rez/issues/1374#issuecomment-1255751276
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAJAV5BFI64MKSGBMKJGIV3V7UMKZANCNFSM6AAAAAAQIHW2JQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/AcademySoftwareFoundation/rez/issues/1374#issuecomment-1255766035,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMOUSQXQUW4I4VYOHSGEUTV7UQJBANCNFSM6AAAAAAQIHW2JQ
.
You are receiving this because you commented.Message ID:
@.***>


Update setup.py with latest details

Some minor corrections.
This library is no more just plain beta (so respective classifier got removed) + repo got moved to new location, so I updated url.
I don't know if we should touch author's email, I might assume in Pypi it plays a role of way to contact author (?), tho, I don't know if @toidi  is still reachable via it anymore. Even if we decide to change it, don't know what to put there.

Hey @dimon222 ,
Thanks for the update!
That email is no longer active. Feel free to remove/change it.

@lresende is there some CODAIT contact mailbox that we could plug there?

We don't have anything specific, but most of us have public e-mails on our profiles but we should always encourage communication via issues.

@lresende I see. I have done some reading, in our case we could utilize maintainer & maintainer_email. I've added myself there as last point of contact (but I would assume anyway most people will appear in this repo in "Issues")

@lresende got any update?


Allowing white-space characters in environment variables (#14)

@jalajmsft version change is not required?