Docker container does not build

I'm on MacOS M1, so make start defaulted to the Docker setup. It ran fine for a while and then failed on this step:
 => ERROR [pdf-document-layout-analysis 30/30] RUN python src/download_models.py 37.7s:
The error itself is this:
[+] Running 0/1undError: [Errno 2] No such file or directory: '/app/models/layoutlm-base-uncased/.huggingface/.gitignore.lock'
 ⠧ Service pdf-document-layout-analysis  Building                                                                                497.7s
failed to solve: process "/bin/sh -c python src/download_models.py" did not complete successfully: exit code: 1

The full stack trace is this:
 > [pdf-document-layout-analysis 30/30] RUN python src/download_models.py:
0.677 2024-12-25 15:22:10,221 [INFO] Downloading doclaynet model
1.320 2024-12-25 15:22:10,865 [INFO] Downloaded 0%
5.252 2024-12-25 15:22:14,798 [INFO] Downloaded 20%
8.953 2024-12-25 15:22:18,497 [INFO] Downloaded 40%
12.34 2024-12-25 15:22:21,885 [INFO] Downloaded 60%
15.70 2024-12-25 15:22:25,242 [INFO] Downloaded 80%
19.48 2024-12-25 15:22:29,023 [INFO] Downloaded 100%
19.49 2024-12-25 15:22:29,035 [INFO] Embedding model is being downloaded
19.80 /app/.venv/lib/python3.11/site-packages/huggingface_hub/file_download.py:1194: UserWarning: `local_dir_use_symlinks` parameter is deprecated and will be ignored. The process to download files to a local folder has been updated and do not rely on symlinks anymore. You only need to pass a destination folder as`local_dir`.
19.80 For more details, check out https://huggingface.co/docs/huggingface_hub/main/en/guides/download#download-files-to-local-folder.
19.80   warnings.warn(
Fetching 11 files:  27%|██▋       | 3/11 [00:00<00:00, 15.29it/s]
37.11 Traceback (most recent call last):
37.11   File "/app/src/download_models.py", line 64, in <module>
37.11     download_models("doclaynet")
37.11   File "/app/src/download_models.py", line 60, in download_models
37.11     download_embedding_model()
37.11   File "/app/src/download_models.py", line 35, in download_embedding_model
37.11     snapshot_download(repo_id="microsoft/layoutlm-base-uncased", local_dir=model_path, local_dir_use_symlinks=False)
37.11   File "/app/.venv/lib/python3.11/site-packages/huggingface_hub/utils/_validators.py", line 114, in _inner_fn
37.11     return fn(*args, **kwargs)
37.11            ^^^^^^^^^^^^^^^^^^^
37.11   File "/app/.venv/lib/python3.11/site-packages/huggingface_hub/_snapshot_download.py", line 294, in snapshot_download
37.11     thread_map(
37.11   File "/app/.venv/lib/python3.11/site-packages/tqdm/contrib/concurrent.py", line 69, in thread_map
37.12     return _executor_map(ThreadPoolExecutor, fn, *iterables, **tqdm_kwargs)
37.12            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
37.12   File "/app/.venv/lib/python3.11/site-packages/tqdm/contrib/concurrent.py", line 51, in _executor_map
37.12     return list(tqdm_class(ex.map(fn, *iterables, chunksize=chunksize), **kwargs))
37.12            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
37.12   File "/app/.venv/lib/python3.11/site-packages/tqdm/std.py", line 1181, in __iter__
37.12     for obj in iterable:
37.12   File "/opt/conda/lib/python3.11/concurrent/futures/_base.py", line 619, in result_iterator
37.12     yield _result_or_cancel(fs.pop())
37.12           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
37.12   File "/opt/conda/lib/python3.11/concurrent/futures/_base.py", line 317, in _result_or_cancel
37.12     return fut.result(timeout)
37.12            ^^^^^^^^^^^^^^^^^^^
37.12   File "/opt/conda/lib/python3.11/concurrent/futures/_base.py", line 449, in result
37.12     return self.__get_result()
37.12            ^^^^^^^^^^^^^^^^^^^
37.12   File "/opt/conda/lib/python3.11/concurrent/futures/_base.py", line 401, in __get_result
37.12     raise self._exception
37.12   File "/opt/conda/lib/python3.11/concurrent/futures/thread.py", line 58, in run
37.12     result = self.fn(*self.args, **self.kwargs)
37.12              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
37.12   File "/app/.venv/lib/python3.11/site-packages/huggingface_hub/_snapshot_download.py", line 268, in _inner_hf_hub_download
37.12     return hf_hub_download(
37.12            ^^^^^^^^^^^^^^^^
37.12   File "/app/.venv/lib/python3.11/site-packages/huggingface_hub/utils/_validators.py", line 114, in _inner_fn
37.12     return fn(*args, **kwargs)
37.12            ^^^^^^^^^^^^^^^^^^^
37.12   File "/app/.venv/lib/python3.11/site-packages/huggingface_hub/file_download.py", line 1202, in hf_hub_download
37.12     return _hf_hub_download_to_local_dir(
37.12            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
37.12   File "/app/.venv/lib/python3.11/site-packages/huggingface_hub/file_download.py", line 1406, in _hf_hub_download_to_local_dir
37.12     paths = get_local_download_paths(local_dir=local_dir, filename=filename)
37.12             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
37.12   File "/app/.venv/lib/python3.11/site-packages/huggingface_hub/_local_folder.py", line 138, in get_local_download_paths
37.12     metadata_path = _huggingface_dir(local_dir) / "download" / f"{sanitized_filename}.metadata"
37.12                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
37.12   File "/app/.venv/lib/python3.11/site-packages/huggingface_hub/_local_folder.py", line 223, in _huggingface_dir
37.12     with WeakFileLock(gitignore_lock):
37.12   File "/opt/conda/lib/python3.11/contextlib.py", line 137, in __enter__
37.12     return next(self.gen)
37.12            ^^^^^^^^^^^^^^
37.12   File "/app/.venv/lib/python3.11/site-packages/huggingface_hub/utils/_fixes.py", line 84, in WeakFileLock
37.12     lock.acquire()
37.12   File "/app/.venv/lib/python3.11/site-packages/filelock/_api.py", line 332, in acquire
37.12     self._acquire()
37.12   File "/app/.venv/lib/python3.11/site-packages/filelock/_unix.py", line 42, in _acquire
37.12     fd = os.open(self.lock_file, open_flags, self._context.mode)

Would appreciate any guidance in getting this to run!

I'm pretty confused, it could be that this issue is regarding the document-layout-analysis repo: https://github.com/huridocs/pdf-document-layout-analysis?
Please try it again.
The issue may be due to temporary unavailability of the model's cloud server. Some Mac M1 users are successfully using the document layout analysis service.
Let us know if it continues to fail.
Have a good day.

Ah yes, it's related to the other repo. Apologies, I must have been on the wrong tab when opening the issue. I'll give it another try.
Closing this issue, will re-open in correct repo if issue persists.
Thanks!


MatchColor works only with RegexGroups, but RegexGroups now forces the use of 'token'

MatchColor cannot be used anymore

Not sure what I did last night, but work fine now.


replace_joypad_input_at_index exhibits unexpected behavior on switching from JOYPAD A

Describe the bug
On calling replace_joypad_input_at_index on an index not yet defined for an action that responds to JOYPAD A, will replace JOYPAD A with the new event instead of adding it to the correct index
Affected version

Input Helper version: 4.3.3
Godot version: 4.2.2

To Reproduce
Steps to reproduce the behavior:

Consider the case in which an action has the inputs [JOYPAD A]
If we call replace_joypad_input_at_index with the action Y at the index 1, the replacing action will be set as JOYPAD A by default, and the final input list will be [JOYPAD Y]

Expected behavior
The input list associated with the action should be [JOYPAD A, JOYPAD Y]. Intead, Y replaced A
Proposed solution
This happens due to the following line @ replace_joypad_input_at_index. On creating a new InputEventJoypadButton, the button_index is set to 0 by default, which is the key for the A button, instead of an invalid button, as it should be.
var replacing_input = InputEventJoypadButton.new() if (inputs.is_empty() or inputs.size() <= index)
This can be fixed by replacing this line with the following, which correctly defines the replacing_input as an invalid one
var replacing_input
if inputs.is_empty() or inputs.size() <= index:
  replacing_input = InputEventJoypadButton.new()
  replacing_input.button_index = JOY_BUTTON_INVALID
else:
  replacing_input = inputs[index]

Hey, I hope that's fine. I opened a PR that implements this proposed solution #37

Thanks 👍


virtualbox-modules is marked as broken

Describe the bug
NixOS 20.09 fails to build when configured as a VirtualBox host. The error message is:
Package ‘virtualbox-modules-6.1.16-5.9.11’ in /nix/store/n1l85sxys8yqackp207pj6ra7vmsrga9-nixos-20.09.2122.2fbcd0b9df9/nixos/pkgs/os-specific/linux/virtualbox/default.nix:20 is marked as broken, refusing to evaluate.

To Reproduce
Using the latest 20.09, add these lines to configuration.nix:
  virtualisation.virtualbox.host = {
      enable = true;
      enableExtensionPack = true;
  };
  users.extraGroups.vboxusers.members = [ "my-username" ];

Then run sudo nixos-rebuild switch.
Expected behavior
The rebuild should succeed, installing VirtualBox.
Additional context
This was working before I upgraded to 20.09. I can't track down where the package is marked as broken. It isn't in pkgs/os-specific/linux/virtualbox/default.nix, or in pkgs/applications/virtualization/virtualbox/. Once I set allowBroken = true; it compiles and runs fine, so it doesn't really seem to be broken.
Notify maintainers

@svanderburg, @ma27, @flokli, @domenkozar.
Metadata
λ ~/ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.9.11, NixOS, 20.09.2101.2335e7354f8 (Nightingale)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.9`
 - channels(root): `"nixos-20.09.2122.2fbcd0b9df9, nixos-unstable-21.03pre255600.24eb3f87fc6"`
 - channels(my-username): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

This seems to be a duplicate of issue https://github.com/NixOS/nixpkgs/issues/101823, which was fixed by PR https://github.com/NixOS/nixpkgs/pull/101493. I'd also appreciate a backport of the fix to 20.09.

I am also seeing the same problem and I am not even using the extension pack, so the issue seems to be different from #101823.

Seeing the same problem; not using extension pack.  Can we hope for a backport?

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/virtualbox-nixos-channel-20-09-failed-nixos-20-09-2152-e34208e1003/10381/2

Seeing the same problem; not using extension pack. Can we hope for a backport?

Need to be merged: https://github.com/NixOS/nixpkgs/pull/107421

Seeing the same problem; not using extension pack. Can we hope for a backport?

Need to be merged: https://github.com/NixOS/nixpkgs/pull/107421


Update slick-greeter preference

Had to switch back to slick-greeter due to #23, need to add these customization. Look at adding customization in /etc/lightdm/lightdm.conf.d instead of editing glib-schema.

Changes made. Will commit once other changes have been completed.


itest upgrade-charm retains rule files

This PR updates the existing integration test to make sure alert rules that were forwarded before an upgrade are still there after an upgrade.
Currently the itest fails because rule files are indeed not persisted across upgrade.
Crossref: OPENG-402

Following in this issue


Move part of AutoHOOT.jl to ITensorAutoHOOT

Also Get CI working.
Note that since AutoHOOT.jl depends on the Python library, currently it cannot be registered to be a general library, thus the previous CI workflow doesn't work (julia-buildpkg and julia-runtest will fail). I rewrite most parts in CI to get it working.
I also removed the docs workflow, can add that back later.

Overall looks good.
My main suggestions would be to:

Make use of #5 once that is merged and remove the lower level @adjoint definitions in favor of those definitions.
Change over the higher level @adjoint definitions like the adjoint of vjps with overloads of ChainRulesCore.rrule, and replace the Zygote dependency with a ChainRulesCore dependency. I don't think you are actually using Zygote for anything in this module besides defining rules, right? It seems like Zygote is only actually used in the tests.

@mtfishman please let me know if you have other comments on this PR

Looks good to me, feel free to merge.


There are no commands defined in the "deploy:mode" namespace.

Existing Magento 2.3.3 project
Configuring composer authentication for docker containers.................... ✔
Turning on developer mode.................................................... ✘
There are no commands defined in the "deploy:mode" namespace.

Due existing env.php in project


RSL4

Really good progress, however we need to get the tests passing now as opposed to moving on and leaving more TODO / FIXME items in the list.

Needs #122.

Thanks, looks very good, few small comments, but :+1:

Needs #122.

Rebased

Ok, have the comments been addressed?  Hard to tell as old history is gone, if so, I think we should merge. @tcard do you agree?

Yes, all comments addressed.

@tcard please merge if you are happy then

Aside from @tcard's feedback, looks good

LGTM


new Branding for the SDK!

Nah not worth the undoing work after april fools is over.

Well is just drag'n'drop on the folder (which you can do right on the web browser) plus 2 click to merge... but I understand if you prefer to spend your time in more productive stuff ;)

I know that I'm not really experienced in git but as far as I know undoing
stuff with git is quite a mess.

If you merge my pr and tag the release, I'll make another PR that brings the monkey back. Deal? ;)

That's up to darkchaos/mefisto. I don't have push permissions for this repo.
But yeah that would be ok IMO.

The binary would still be in the repository forevery, still I kinda must resist clicking the merge button XD

Not only merge, but also tag release... otherwise it is pointless.

The poll is going strong:
https://hub.jmonkeyengine.org/t/ummm-what-just-happened-to-system-administrator-of-this-website/35517/28?u=pesegato

Looks good to me 🦄   :+1:  :+1:  :+1:
✔ Official Management Seal of Approval

Hopefull this won't deter the merge; however I'll be AFK over the weekend and won't be able to PR the monkey... but hey, let's give the pony a weekend... :monkey_face:

No worries @Pesegato I think I have the monkey image on my fork. I can make the PR.

Just to note that: I was working the whole 1st so I couldn't react to this :(
Git/CVS is built that way you can easily revert anything which has been done. So you can just undo the PR again (which is what those systems are for).
This has been done by Dokthar already


Explorer is hiding

Issue Type: Bug
Explorer is hiding

Click  on search in left menu
Now observe that file explorer is hidden

VS Code version: Code 1.29.1 (bc24f98b5f70467bc689abf41cc5550ca637088e, 2018-11-15T19:13:36.375Z)
OS version: Windows_NT x64 10.0.16299

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz (8 x 2712)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.82GB (6.74GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (5)

Extension
Author (truncated)
Version

simple-react-snippets
bur
1.2.2

prettier-vscode
esb
1.7.2

debugger-for-chrome
msj
4.11.1

vscode-icons
rob
7.28.0

ayu
tea
0.17.0

the explore menu is not appearing once we clear the text in the search box. So now if i want to open any other file form the explorer i can't do it.  I have manually go to view section and have to enable explorer once again , and this will be issue for end user


Have pairing info include more stuff

Company info
Dates
Project name

This appears to have been done. Could use a better layout though, since the grid row setup doesn't work well for paired data displaying.


Updated keyboard shortcuts

Updating keyboard shortcuts based on the information provided in the portal.

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

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

@gmantri : Thanks for your contribution to the Azure documentation! The author, @flanakin, has been notified to review your proposed change.

Can you change "web apps" to "App Service" and "Browse" to "More services"? The latter is wrong in the portal, so I'll update that.

Hi @gmantri - Please see the comment from @flanakin.  Please advise whether this request for change should remain open.  Thanks

#please-close The keyboard shortcut topic has been updated since this was submitted. Thanks for the submission @gmantri.


[5.4] - Validate 'date' with 'milliseconds' (not 'microseconds')

Laravel Version: 5.4.23
PHP Version: 7.0.19
Database Driver & Version: MySQL 5.6

Description:
I'm trying to validate an input date field that contains milliseconds; something like this:
2017-03-20 23:48:52.243.
but it doesn't work.
Steps To Reproduce:
$validator = Validator::make($myArray, [
    'mytime' => 'date_format:"Y-m-d H:i:s.v"|required'
]);

Please, note that I need to validate milliseconds (v) and not microseconds (u). The v option was implemented on PHP7.0 (http://php.net/manual/en/function.date.php).

I didn't see any failing tests for this bug report so I wrote one: https://github.com/laravel/framework/pull/19460
Please provide guidance if I made any mistakes on contributing with this PR as I'm a newb to the process.
Thanks!

Hi
Thank you for your support.
I provided a Test that fails for me:
use Tests\TestCase;
use Illuminate\Foundation\Testing\WithoutMiddleware;
use Illuminate\Foundation\Testing\DatabaseMigrations;
use Illuminate\Foundation\Testing\DatabaseTransactions;
use Illuminate\Support\Facades\Validator;

class MyValidatorTest extends TestCase
{
    public function testValidateMicroseconds()
    {
        // Set input params
        $myArray = [
            'x' => '2016-06-22 16:52:06.321321',
        ];

        // Validate microseconds
        $validator = Validator::make($myArray, [
            'x' => 'date_format:Y-m-d H:i:s.u',
        ]);
        $this->assertTrue($validator->passes());
    }

    public function testValidateMilliseconds()
    {
        // Set input params
        $myArray = [
            'y' => '2016-06-22 16:52:06.321'
        ];

        // Validate milliseconds
        $validator = Validator::make($myArray, [
            'y' => 'date_format:Y-m-d H:i:s.v',
        ]);
        $this->assertTrue($validator->passes());
    }
}

As you can see, I validating microseconds and milliseconds; the "microseconds" pass the test but the "milliseconds" fails:
PHPUnit 5.7.20 by Sebastian Bergmann and contributors.

Runtime:       PHP 7.0.19
Configuration: /Users/valentino/Desktop/gitwork/group__caravel/dante/phpunit.xml

.F                                                                  2 / 2 (100%)

Time: 84 ms, Memory: 10.00MB

There was 1 failure:

1) App\Api\V1\Tests\MyValidatorTest::testValidateMilliseconds
Failed asserting that false is true.

/Users/valentino/Desktop/gitwork/group__caravel/dante/app/Api/V1/Tests/Eventdb/MyValidatorTest.php:38

FAILURES!
Tests: 2, Assertions: 2, Failures: 1.

Any idea?

Looking at the code I found in \Illuminate\Validation\Concerns\ValidatesAttributes.php
      /**
       * Validate that an attribute matches a date format.
       *
       * @param  string  $attribute
       * @param  mixed   $value
       * @param  array   $parameters
       * @return bool
       */
      protected function validateDateFormat($attribute, $value, $parameters)
      {
          $this->requireParameterCount(1, $parameters, 'date_format');

          if (! is_string($value) && ! is_numeric($value)) {
              return false;
          }

          $date = DateTime::createFromFormat($parameters[0], $value);

          return $date && $date->format($parameters[0]) == $value;
      }

As you can see the date_format validation uses DateTime::createFromFormat to validate the date.
In the php documentation (http://php.net/manual/en/datetime.createfromformat.php) you can see that this method does not accepts the v parameter like the date() function.

Hey guys, I managed to modify the method to use a combination of the date() method (which supports v/milliseconds) and the DateTime object to get it passing for v/milliseconds (perhaps a bit hacky?):
protected function validateDateFormat($attribute, $value, $parameters)
{
    $this->requireParameterCount(1, $parameters, 'date_format');

    if (! is_string($value) && ! is_numeric($value)) {
        return false;
    }

    // create date string with given format
    $dateString = date($parameters[0], strtotime($value));

     // create DateTime object with $dateString var
    $date = new DateTime($dateString);

    // DateTime->format() method outputs the result of 'v'
    return $date && $date->format($parameters[0]) == $value;
}

See the following code to see how this works:
>>> $dateString = date('Y-m-d H:i:s.v', strtotime('2000-01-01 00:00:00.000'));
=> "2000-01-01 00:00:00.000"
>>> $date = new DateTime($dateString);
=> DateTime {#809
     +"date": "2000-01-01 00:00:00.000000",
     +"timezone_type": 3,
     +"timezone": "UTC",
   }
>>> $date->format('Y-m-d H:i:s.v')
=> "2000-01-01 00:00:00.000"

However, this breaks three other tests which I believe are related to timezone. If I have understood things correctly this is because the date() method appears to rely on the timezone set at the beginning of the test: date_default_timezone_set('UTC');, rather than what the timezone was passed into the test. E.g. Instead of Atlantic/Azores it will return UTC.
The three failing tests are as follows:
// e - Timezone identifier
$v = new Validator($trans, ['x' => '2000-01-01T00:00:00Atlantic/Azores'], ['x' => 'date_format:Y-m-d\TH:i:se']);
$this->assertTrue($v->passes());

// T - Timezone abbreviation
$v = new Validator($trans, ['x' => '2000-01-01T00:00:00Z'], ['x' => 'date_format:Y-m-d\TH:i:sT']);
$this->assertTrue($v->passes());

// P - Difference to Greenwich time (GMT) with colon between hours and minutes
$v = new Validator($trans, ['x' => '2000-01-01T00:00:00+00:30'], ['x' => 'date_format:Y-m-d\TH:i:sP']);
$this->assertTrue($v->passes());

The only way I can think to get it passing right now is to check if the format string has a v in it and to use the original logic if it doesn't and then to alternatively use the logic I have written above if it does. Again, a bit hacky, but it gets the tests passing.
protected function validateDateFormat($attribute, $value, $parameters)
{
    $this->requireParameterCount(1, $parameters, 'date_format');

    if (! is_string($value) && ! is_numeric($value)) {
        return false;
    }

    if (!preg_match('/v/', $parameters[0])) {
        $date = DateTime::createFromFormat($parameters[0], $value);
    } else {
        $dateString = date($parameters[0], strtotime($value));
        $date = new DateTime($dateString);
    }

    return $date && $date->format($parameters[0]) == $value;
}

Any thoughts on this?
Another thought I had was that v/millisecond is only supported in PHP 7.0, so I'm guessing it would need to be added to Laravel 5.5 which I've read will require PHP 7.0? - https://laravel-news.com/laravel-5-5-php-7-0

Closing and moving the discussion to the opened PR.


Update stub-builder.ts to support falsy overrides

The current override logic checks if an override property exists by using falsy logic to check its value, so if an override defined with a value of false or 0, the override will instead be mocked.
Using the in operator checks if the property exists rather than checking the value of the property, allowing these overrides

thank you @darcyrush !


Add "token" parameter in $webhookExists

Featuring Type
Function
So, what is it about?
I think there should be an optional "token" parameter in $webhookExists. So like $webhookExists[id;token]. This allows us to see if a certain webhook exists in a channel which can be helpful for people who uses webhooks for logging. Sorry if I'm wrong but I think client.fetchWebhook has an optional "token" parameter.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

No, this can be merged.


Add styling to the network timeline

Related to #162
Offering this up. The end goal is a more readable network feed.
I can simplify or change as needed per direction.

Hey Jeff, thanks for this! I don't really know where we're headed yet re: the overall site styling, but I'll take this as at least a temporary measure since the current state of that page is pretty rough. I'll try to find some time to make the actual functionality a bit more useful too-- I need to filter out the extra noise that the URLs related to Mastodon @-mentions are causing.

Agreed. This is a temporary measure, until a CSS guru comes along and works their magic. 🪄 😄


Fallback to dump all nodes instead of error on /ast/100000 when id is not exists

Before

After

Closes https://github.com/rectorphp/getrector-com/issues/2223

All checks have passed 🎉 @TomasVotruba I am merging it ;)


[Documentation] Which Jenkins Staging jobs need to be saved / removed

Here is a list of all of the jobs on the Jenkins staging system, lets figure out if we need them or not

[ ] Single-Node-CDK-run
[ ] fetch_build_pipelines_Sai
[ ] fetch_bundles
[ ] Integ-test-demo
[ ] opensearch_bundle_integtest
[ ] perf-tests

[X] Save 1.0.0-maven-build-job
[X] Save 1.0.0-maven-sign-and-release
[X] Save bundle-build
[x] Save bwc-test
[x] Save integ-test
[x] Save perf-test
[x] Save perf_test_owais - Has sample script to run perf test
[x] Save random_test
[x] Save test-orchestration-pipeline

[x] Remove bundle-build-inline-test
[X] Remove bundle-build-petern
[x] Remove bundle_pipeliness_1.0.1
[x] Remove sample-cmd-testings
[x] Remove Test-handalm
[x] Remove test-job-1
[x] Remove test-pipeline
[x] Removetest-release-pipeline

Still have some outstanding jobs, need to circle back with the team members to update


Today is 2015.10.30,but cron error is "Month '1' is limited to '29' days"

Today is 2015.10.28,but cron error is "Month '1' is limited to '29' days",
My cron string is 38 11 10 30 * * .
I don't know why,when I use this string " 38 11 10 30  9  * ",it works fine;
My cron : 1.0.9

You can just do this 38 11 10 29,30 * *.... from crontab
Because 1 is February with 29 days doing it like that works for both i guess

The month ranges from 0 to 11, so month 1 would be February

Closing due to age. Can create a new ticket if it comes up again.


Provide thread monitor create task feature

Please answer these questions before submitting pull request

Why submit this pull request?

[ ] Bug fix

[x] New feature provided

[ ] Improve performance

Related issues
#4104

New feature or improvement

Follow step one, create and query thread monitor task according to graphql

Codecov Report

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

@@           Coverage Diff           @@
##           master    #4145   +/-   ##
=======================================
  Coverage   26.96%   26.96%
=======================================
  Files        1155     1155
  Lines       25325    25325
  Branches     3667     3667
=======================================
  Hits         6830     6830
  Misses      17888    17888
  Partials      607      607

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 a6d73f4...de7ca7d. Read the comment docs.

This is for step 1?

The e2e tests are keeping failure, we need to figure out why first.

This is for step 1?

Yes, this is for task creation and query.

I have a suggestion for e2e-profile . I think we should add ThreadMonitorTask toe2e-cluster e2e-mysql e2e-single-service instead of adding a new e2e.

I have a suggestion for e2e-profile . I think we should add ThreadMonitorTask toe2e-cluster e2e-mysql e2e-single-service instead of adding a new e2e.

At present, it's only graphql in OAP to add query test, but the interaction in sniffer will be integrated later. I think it's better to use a new E2E

@kezhenxu94 I can't find anything related to the e2e failure in the log, even no error logs from OAP. Could you check why? Or do we miss some logs?

@kezhenxu94 I can't find anything related to the e2e failure in the log, even no error logs from OAP. Could you check why? Or do we miss some logs?

The failures of the E2E tests are due to the missing update of the submodule (protocol), thus missing the newly-added file query-protocol/profile.graphqls, @mrproliu please update the submodule in this PR

The failure should be discoverable and reproducible in your local machine, if you make sure that your codes are the same with the remote repo @mrproliu

@kezhenxu94 He sent me this directly, that is why I asked.

The failure should be discoverable and reproducible in your local machine, if you make sure that your codes are the same with the remote repo @mrproliu

OK, I have submitted it.

Oh, you didn't update the submodule, strange, why log can't show this?

Oh, you didn't update the submodule, strange, why log can't show this?

The failure is due to timeout and the e2e-container is killed by the plugin, so we have no chance to cat the logs

The failure is due to timeout and the e2e-container is killed by the plugin, so we have no chance to cat the logs

So, if we face the OAP bootstrap issue, then this error shows up without the logs. Could I make this as a conclusion of a possible case? Could we make this a part of e2e test faq?

I have a suggestion for e2e-profile . I think we should add ThreadMonitorTask toe2e-cluster e2e-mysql e2e-single-service instead of adding a new e2e.

At present, it's only graphql in OAP to add query test, but the interaction in sniffer will be integrated later. I think it's better to use a new E2E

But es and mysql is not covered,  need to be added? @wu-sheng @kezhenxu94

So, if we face the OAP bootstrap issue, then this error shows up without the logs. Could I make this as a conclusion of a possible case?

Yes I agree.
Because bootstrap failure should be always stable to reproduce, and should be discovered when establishing a new E2E case, my assumption is that the contributor should verify locally, and guaranteed the codes are all pushed to remote repo, unlike this case :)

Could we make this a part of e2e test faq?

Sure, or maybe as an important note to contribute new E2E cases

Sure, or maybe as an important note to contribute new E2E cases

Could you submit a separated PR about this?

Before the further change, please make sure we have consistent name. Let's remove thread monitor in all names, only keep profile in name, including Graphql protocol. They are used randomly.


Moving Social Activities Framework from kie-uberfire-extensions to ub…

Depends on https://github.com/uberfire/uberfire/pull/603

Jenkins retest this.

@psiroky fyi, you might like this too ;). Getting closer to removing this repo.


PronotePy API Error : pronotepy.exceptions.PronoteAPIError: Your IP address is suspended.

Hello,
I recently decided to make a WhatsApp bot that gets my class' homework and send it to our group. The problem is that it gives me this error : pronotepy.exceptions.PronoteAPIError: Your IP address is suspended.. I do not know why. My used code is below:
import requests
import pronotepy
from pronotepy.ent import ac_poitiers

# creating the client and passing the occitanie_montpellier function to automatically get cookies from ENT
client = pronotepy.Client('https://HIDING_MY_SCHOOL'S_ID.index-education.net/pronote/eleve.html',
                          username='HIDING_MY_USERNAME',
                          password='HIDING_MY_PASSWORD',
                          ent=ac_poitiers)

if client.logged_in: # check if client successfully logged in
    # get the all the periods (may return multiple types like trimesters and semesters but it doesn't really matter
    # the api will get it anyway)
    nom_utilisateur = client.info.name # get users name
    print(f'Logged in as {nom_utilisateur}')

    today = datetime.date.today() # store today's date using datetime built-in library
    homework = client.homework(today) # get list of homework for today and later

    for hw in homework: # iterate through the list
        print(f"({hw.subject.name}): {hw.description}") # print the homework's subject, title and description

else:
    print("Failed to log in")

I would like to get help. Thanks.
P-S : I removed the WhatsApp part, my username, password and school id from this script.

I guess your bot just did too much requests in a certain period of time, so your ip is now suspended by pronote, try to login normally via browser and see if you can login (from the same device where your code is hosted) to see if it works or not, if it doesnt, then you can't do anything about it other that using a vpn or changing the host (it may be ip banned later if you continue doing that much requests)

Yeah, but my bot just comes, get the homework, prints it and dip out, so why would it send that much requests?

How often (i.e. at which frequency) does it run?

Like, twice a week? And I haven't touched it in a month because it's not fully functionnal... The WhatsApp part is functionnal, but because or this, it doesn't.

Okay if its only twice a week it is weird, i can't really help you here, good luck !

Can you try connecting with another IP (i.e. from another wifi network, through a VPN or after rebooting your router if you have a dynamic public IP) to see if the issue persists? Do you still have access to pronote through a web browser?

I kinda don't want to test it because:
Other WiFi network : My computer is on ethernet and doesn't have any WiFi card.
VPN : I don't want to install one just for this
Rebooting router : Don't have dynamic public IP


allow svg element

In this PR I have added a test case for the SVG element to prevent the element from lowercased and same for the attributes.

Thanks for doing this! Small comments.


Inconsistent Defaults

If you try installing the simple_form gem without running the simple_form:install generator, the default behavior will be different than when running the simple_form:install generator. I assume this is because a wrapper is provided in the generated config file that behaves differently that the defaults. Why is this inconsistent?
This can be frustrating when installing the gem and adjusting the CSS in the forms, then halfway through deciding to run the install generator. Then all of the sudden the CSS is broken because the markup is completely different.
IMO, the simple_form:install generator should be the same as the default behavior.

I see. I have the same consideration about this issue. We keep the default wrapper different of the generated because this can make the tests easier.
I'll fix this issue now.
Thanks to reporting

@ryanb Yeah, I completely agree there is some inconsistence between SimpleForm's defaults and the generated template. Some of the configs currently in SimpleForm's defaults are there to maintain compatibility with older versions, while in a new app we recommend running the generator to get most of the new stuff setup correctly.
Anyway, we should probably review this to keep things more consistent. Thanks for reporting.

I agree having these settings in the generated config is good so you are able to change the defaults in future versions while keeping backwards compatability, but I do think it's important for the defaults to match the generated config (unless passing additional options such as --bootstrap).
As for backward compatibility, changing the major version number (2.0) seems like the opportune time to break backwards compatibility. Perhaps too late now though?

Maybe the best option is for us to warn the user if he tries to use simple form without running the simple_form:install generator. We could do this by storing if SimpleForm.configure was called and using a Rails' after_initialize callback to warn the user.


Use per-service 'test:' github label instead of default 'test:shakedown' each time

At the moment, each successive test run hides the result of prior runs in github

Great idea! I'm seeing it as test:test:<fwk> though.

Oh whoops, fixed


[Crash]: GPU process exited unexpectedly: exit_code=134

Before you file a crash report

[X] I have checked the issue tracker and have not found an issue that matches the one I'm filing.
[X] This issue doesn't reproduce on web browsers (such as in Chrome). If it does, issue reports go to the Mattermost Server repository.
[X] I have read the contribution guidelines.

Mattermost Desktop Version
5.5.1
Operating System
Ubuntu 23.10
Mattermost Server Version
9.0.1
What type of crash did you experience?
Won't launch. Nothing happens with desktop launcher, below is the log from terminal
Crash report details
[xavier@imladris ~]$ Applications/mattermost-desktop/mattermost-desktop
15:30:37.274 › Logger Log level set to: info
15:30:37.385 › Logger Log level set to: warn
15:30:37.392 › [App.Initialize] Current working directory is /home/xavier, changing into /home/xavier/Applications/mattermost-desktop
15:30:37.560 › [i18nManager] Failed to set new language en-US
15:30:37.561 › [i18nManager] Failed to set new language US
*** stack smashing detected ***: terminated
[3758262:1106/153037.604432:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018
[3758262:1106/153037.786974:ERROR:gpu_process_host.cc(957)] GPU process exited unexpectedly: exit_code=134
15:30:37.787 › [App.App] "child-process-gone" The child process has crashed. Details:  { type: 'GPU', reason: 'crashed', exitCode: 134, serviceName: 'GPU' }
*** stack smashing detected ***: terminated
[3758262:1106/153038.066292:ERROR:gpu_process_host.cc(957)] GPU process exited unexpectedly: exit_code=134
15:30:38.066 › [App.App] "child-process-gone" The child process has crashed. Details:  { type: 'GPU', reason: 'crashed', exitCode: 134, serviceName: 'GPU' }
*** stack smashing detected ***: terminated
[3758262:1106/153038.338450:ERROR:gpu_process_host.cc(957)] GPU process exited unexpectedly: exit_code=134
15:30:38.339 › [App.App] "child-process-gone" The child process has crashed. Details:  { type: 'GPU', reason: 'crashed', exitCode: 134, serviceName: 'GPU' }
*** stack smashing detected ***: terminated
[3758262:1106/153038.630566:ERROR:gpu_process_host.cc(957)] GPU process exited unexpectedly: exit_code=134
15:30:38.631 › [App.App] "child-process-gone" The child process has crashed. Details:  { type: 'GPU', reason: 'crashed', exitCode: 134, serviceName: 'GPU' }
*** stack smashing detected ***: terminated
[3758262:1106/153038.867587:ERROR:gpu_process_host.cc(957)] GPU process exited unexpectedly: exit_code=134
15:30:38.868 › [App.App] "child-process-gone" The child process has crashed. Details:  { type: 'GPU', reason: 'crashed', exitCode: 134, serviceName: 'GPU' }
*** stack smashing detected ***: terminated
[3758262:1106/153039.138666:ERROR:gpu_process_host.cc(957)] GPU process exited unexpectedly: exit_code=134
15:30:39.139 › [App.App] "child-process-gone" The child process has crashed. Details:  { type: 'GPU', reason: 'crashed', exitCode: 134, serviceName: 'GPU' }
*** stack smashing detected ***: terminated
[3758262:1106/153039.368969:ERROR:gpu_process_host.cc(957)] GPU process exited unexpectedly: exit_code=134
15:30:39.369 › [App.App] "child-process-gone" The child process has crashed. Details:  { type: 'GPU', reason: 'crashed', exitCode: 134, serviceName: 'GPU' }
*** stack smashing detected ***: terminated
[3758262:1106/153039.611732:ERROR:gpu_process_host.cc(957)] GPU process exited unexpectedly: exit_code=134
15:30:39.611 › [App.App] "child-process-gone" The child process has crashed. Details:  { type: 'GPU', reason: 'crashed', exitCode: 134, serviceName: 'GPU' }
*** stack smashing detected ***: terminated
[3758262:1106/153039.834672:ERROR:gpu_process_host.cc(957)] GPU process exited unexpectedly: exit_code=134
[3758262:1106/153039.834704:FATAL:gpu_data_manager_impl_private.cc(431)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap (core dumped)

Log Output
No response
Additional Information
No response

@xavier8854 This looks like an internal Chromium engine error. Does this reproduce consistently for you? Have you tried a different server such as community.mattermost.com?

Hi @devinbinnie sorry for the delay
It reproduces consistently, even with --no-sandbox option
Since Mattermost won't launch, I cannot tru another server
Regards,
Xavier

@xavier8854 Sounds like there could be an issue with your GPU/driver? If you're able to turn off GPU acceleration (you can find the option in ~/.config/Mattermost/config.json) that might also help.

@xavier8854 Is this still an issue for you?

Hi,
I switched to Browser a few months ago, but gave a try to 5.9.0-linux-x64 application. The problem is fixed.
Thanks,
Xavier

Hi,
I switched to Browser a few months ago, but gave a try to
5.9.0-linux-x64 application. The problem is fixed.
Thanks,
Xavier
Le 27/09/2024 18:47, Devin Binnie a écrit :

@xavier8854 https://github.com/xavier8854 Is this still an issue for
you?
—
Reply to this email directly, view it on GitHub
https://github.com/mattermost/desktop/issues/2903#issuecomment-2379684386,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZCXILZ6AGCQLPBSGBWHRTZYWD3HAVCNFSM6AAAAABO7QWSDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZZGY4DIMZYGY.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Xavier @.***>
2 rue des Patureaux
54460 AINGERAY / FRANCE
Tél  +33 6 71 17 29 07
Dom  +33 9 51 00 37 63

Great, thanks for letting me now :)
Closing.


Medium.com blogposts are not shown after deployment

Acknowledge the following

[x] I carefully read and followed the Getting Started guide.
[x] I read through FAQ and searched through the past issues, none of which addressed my issue.
[x] The issue I am raising is a potential bug in al-folio and not just a usage question.  [For usage questions, please post in the Discussions instead of raising an issue.]

Describe the bug
I've provided the _config.yaml with my medium.com account RSS and when I run the jekyl locally I have my posts shown on the blog page. But after deployment my Blog page is empty.
Expected behavior
My blog posts from Medium are being shown after deployment.
Screenshots
If applicable, add screenshots to help explain your problem.
System (please complete the following information):

Browser (and its version) Yandex Browser
Jekyll version [e.g. 3.8.7]
Ruby version [e.g. 2.6.5]

Additional context
Add any other context about the problem here.

thanks for reporting this issue. it looks like the blog page is generated correctly in the gh-pages branch (https://github.com/bestasoff/bestasoff.github.io/tree/gh-pages), so I suspect the settings for github pages are misconfigured. please make sure you followed this step:

Finally, in the Settings of your repository, in the Pages section, set the branch to gh-pages (NOT to master).

@alshedivat Thank you for your response! I'll check it put ASAP.


Why there is no support for ipad

Hi ,
Can you give me a reason why there is no support for ipad
And whats with veecontrolpicker.bundle not loader
Thanks and Regards

v1 now support iPad


Extended lint applied

@RWOverdijk

re:
then(updated => { response = updated; })
      @RWOverdijk
RWOverdijk 3 hours ago
Mhm. I kind of get it, but it's convenient here. So by rule, it should then be an assignment followed by a return?
Either way, I think we can lose the curly braces, and the semicolon?

how?

Allow return statements can be done later, wouldn't break current linting so no rush.


how to make sure handlebars.js template complete, beacuse I want to use highlight.js

how to make sure handlebars.js template complete, beacuse I want to use highlight.js

I'm not sure what you are asking here. Can you provide more details?

I solved it ,because I can't make sure the template was compiled and render complete,so that when I use highlight is not available, I can't find any function (for example callback) to make sure  render complete, I use window.load solve it; so sorry for my english

Closing as it sounds like this is up and running.


unloadAll() doesnt work

this.store.unloadAll();

Error while processing route: orders Cannot read property 'typeKey' of undefined TypeError: Cannot read property 'typeKey' of undefined
I then tried to unload each model type individually:
this.store.unloadAll('order-item');

This doesn't produce an error but it also doesn't work. Any ideas for workarounds?

Not really. For TypeError: Cannot read property 'typeKey' of undefined, can you follow the execution until you find the line that's causing this?

https://github.com/kurko/ember-localstorage-adapter/issues/125 is related. I'm closing this. If you think it's a separate issue, please reopen.


Counts incorrect when fluo restarted in middle of stress test

On a 12 node ec2 cluster I ran stress test loading 1 million integers via M/R and then 3 million w/ load transactions.  While the workers were processing the 3 million I restarted fluo twice using fluo yarn stop and fluo yarn start.  After the workers had processed all notification I compared the counts from fluo and M/R.  The counts differed.
[ec2-user@leader1 fluo-stress]$ ./bin/print.sh 2>/dev/null
Total at root : 3991977
Nodes Scanned : 15259
[ec2-user@leader1 fluo-stress]$
[ec2-user@leader1 fluo-stress]$
[ec2-user@leader1 fluo-stress]$ grep UNIQ logs/unique.err
                UNIQUE=3992004

Using the technique described in a comment on fluo-io/fluo-stress#7 I compared the fluo generated tree with a M/R generated tree.  Below are some of the problems I found, but not all of the problems.  Seems locks were just left.
There was a problem at level 6 with the count for<PHONE_NUMBER>aa0000.  Saw the following at levels 7 and 8.
root@instance16 fluo> grep<PHONE_NUMBER>aa4f
07:s1o9:08:0000000021aa4f00 count:wait [] 14099658-LOCK    08:0iv6:08:0000000021aa4f4d count wait  $
07:s1o9:08:0000000021aa4f00 count:wait [] 14099658-DATA    1
08:0iv6:08:0000000021aa4f4d count:seen [] 14099658-LOCK    08:0iv6:08:0000000021aa4f4d count wait  $
08:0iv6:08:0000000021aa4f4d count:seen [] 14099658-DATA    1
08:0iv6:08:0000000021aa4f4d count:wait [] 6874041-TX_DONE
08:0iv6:08:0000000021aa4f4d count:wait [] 14101136-WRITE    14099658 TRUNCATION PRIMARY
08:0iv6:08:0000000021aa4f4d count:wait [] 6874041-WRITE    6872050 TRUNCATION PRIMARY
08:0iv6:08:0000000021aa4f4d count:wait [] 6872050-DATA    1

The count for<PHONE_NUMBER>fe0000 at level 6 was 270.  It was supposed to be 271, found the following problem.
root@instance16 fluo> grep<PHONE_NUMBER>fec3
07:0lan:08:0000000011fec300 count:wait [] 14099649-LOCK    08:0ilh:08:0000000011fec323 count wait  $
07:0lan:08:0000000011fec300 count:wait [] 14099649-DATA    1
08:0ilh:08:0000000011fec323 count:seen [] 14099649-LOCK    08:0ilh:08:0000000011fec323 count wait  $
08:0ilh:08:0000000011fec323 count:seen [] 14099649-DATA    1
08:0ilh:08:0000000011fec323 count:wait [] 7815895-TX_DONE
08:0ilh:08:0000000011fec323 count:wait [] 14101134-WRITE    14099649 TRUNCATION PRIMARY
08:0ilh:08:0000000011fec323 count:wait [] 7815895-WRITE    7813650 TRUNCATION PRIMARY
08:0ilh:08:0000000011fec323 count:wait [] 7813650-DATA    1

At level 6<PHONE_NUMBER>1f0000 was 253 instead of 254.  Found the following problems at level 7 and 8.
root@instance16 fluo> grep -np<PHONE_NUMBER>1f32
08:have:08:00000000231f321a count:seen [] 9555339-WRITE    9554544 TRUNCATION
08:have:08:00000000231f321a count:seen [] 9554544-DATA    1
08:have:08:00000000231f321a count:wait [] 9555339-TX_DONE
08:have:08:00000000231f321a count:wait [] 3777912-TX_DONE
08:have:08:00000000231f321a count:wait [] 9555339-WRITE    9554544 TRUNCATION PRIMARY
08:have:08:00000000231f321a count:wait [] 3777912-WRITE    3776950 TRUNCATION PRIMARY
08:have:08:00000000231f321a count:wait [] 3776950-DATA    1
07:5g59:08:00000000231f3200 count:seen [] 13339534-WRITE    13339363 TRUNCATION
07:5g59:08:00000000231f3200 count:seen [] 13339363-DATA    2
07:5g59:08:00000000231f3200 count:wait [] 13339534-TX_DONE
07:5g59:08:00000000231f3200 count:wait [] 13339534-WRITE    13339363 TRUNCATION PRIMARY
07:5g59:08:00000000231f3200 count:wait [] 14099648-LOCK    08:0ild:08:00000000231f32a7 count wait  WRITE NOT_DELETE NOT_TRIGGER l
07:5g59:08:00000000231f3200 count:wait [] 14099648-DATA    1
08:ogzn:08:00000000231f32c8 count:seen [] 9604411-WRITE    9603694 TRUNCATION
08:ogzn:08:00000000231f32c8 count:seen [] 9603694-DATA    1
08:ogzn:08:00000000231f32c8 count:wait [] 9604411-TX_DONE
08:ogzn:08:00000000231f32c8 count:wait [] 3581402-TX_DONE
08:ogzn:08:00000000231f32c8 count:wait [] 9604411-WRITE    9603694 TRUNCATION PRIMARY
08:ogzn:08:00000000231f32c8 count:wait [] 3581402-WRITE    3580467 TRUNCATION PRIMARY
08:ogzn:08:00000000231f32c8 count:wait [] 3580467-DATA    1
08:0ild:08:00000000231f32a7 count:seen [] 14099648-LOCK    08:0ild:08:00000000231f32a7 count wait  WRITE NOT_DELETE TRIGGER l
08:0ild:08:00000000231f32a7 count:seen [] 14099648-DATA    1
08:0ild:08:00000000231f32a7 count:wait [] 7033621-TX_DONE
08:0ild:08:00000000231f32a7 count:wait [] 14101124-WRITE    14099648 TRUNCATION PRIMARY
08:0ild:08:00000000231f32a7 count:wait [] 7033621-WRITE    7027699 TRUNCATION PRIMARY
08:0ild:08:00000000231f32a7 count:wait [] 7027699-DATA    1

The table had no notifications.  Maybe the notifications for these were prematurely deleted?

I noticed in the three cases above that the primary column has successfully committed.   The locks were left on other columns in the transaction.  For one of those I tried scanning the two locked columns.
fluo scan -r 08:0iv6:08:0000000021aa4f4d
08:0iv6:08:0000000021aa4f4d count seen 	1
fluo scan -r 07:s1o9:08:0000000021aa4f00
07:s1o9:08:0000000021aa4f00 count wait 	1

Then I looked for notifications and scanning the columns had caused one to be created.
root@instance16 fluo> scan -c ntfy
07:s1o9:08:0000000021aa4f00 ntfy:countwait [] 14101136-

Eventually the node at level 6 its count corrected from 233 to 234.  First wait was set and then seen was updated.
[ec2-user@leader1 ~]$ fluo scan -p 06 | grep<PHONE_NUMBER>aa0000
06:0ajr:08:0000000021aa0000 count seen 	233
06:0ajr:08:0000000021aa0000 count wait 	1

A bit of time between these.
[ec2-user@leader1 ~]$ fluo scan -p 06 | grep<PHONE_NUMBER>aa0000
06:0ajr:08:0000000021aa0000 count seen 	234

Based on this I tried scanning the entire table to clean up all locks.
fluo scan > /dev/null

This caused a lot of notifications to be created.  Eventually the counts came out correct!
[ec2-user@leader1 fluo-stress]$ ./bin/print.sh 2>/dev/null
Total at root : 3992004
Nodes Scanned : 15259

I looked into how this currently works and found the following.

regular notifications are deleted when the trigger column is committed using the startTs.  In the same mutation the ACK is written.
regular notifications are written when an observed column is committed using the commitTs
weak notifications are written after all locks were written but before primary column is committed.  Its dones using commitTs
weak notifications are deleted before any locks are written (this is really really bad, notification could be completely lost w/o doing any work)

The trigger column is always chosen as the primary column.  So basically when the primary column is committed the notification is deleted.  If the worker dies after this then there will be no notification to recreate the transaction.

I am thinking that regular and weak notifications should only be deleted after the transaction is completed.  For weak notifications this may result in the transaction running multiple times, but thats ok.  For regular notifications, if a process dies after committing but before deleting the notification then the ACK should prevent it from running again.  In the case where there is an ACK, would need to delete the notification.


Grant minimal permissions to workflows

Suggestion
🔍 Search Terms
token permissions, permissions
✅ Viability Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
I'd like to suggest that TypeScript reduce the permissions granted to GitHub workflows. This is recommended by the OpenSSF Scorecard (added in #52103).
By default, GitHub grants workflows full write-all permissions, which makes the project vulnerable to supply-chain attacks.
Minimizing permissions can be done by:

adding top-level permissions to the workflows themselves; and/or
changing the repo settings so that workflows run with read-only permissions.

I'm sending out a PR along with this issue setting the top-level permissions if you wish to follow this track.
If you instead prefer to change the repo settings:

Open the repository settings
Go to Actions > General
Under "Workflow permissions", set them to "Read repository contents and packages permissions"

There are a few workflows that require elevated permissions. Specifically, those that automatically commit to the repository will require content: write. If the default repo setting is changed, these workflows will need to be updated to declare this elevated permission.
📃 Motivating Example
The current write-all permissions mean that, if any workflow dependency gets taken over by a malicious actor, a malicious version could be released to manipulate the TypeScript repository's contents or to exfiltrate secrets and credentials.
Disclaimer
My name is Pedro and I'm working with Google and the OpenSSF to improve the supply-chain security of the open-source ecosystem.

Done, thanks!


Installer does not remember selection

If you install IronPython with pip and go to Apps & Features -> IronPython 2.7.9 -> Modify -> Change pip will be marked as not installed. A consequence of this is if you do a Repair then pip will be removed from the system.

Also using Change to try to readd pip doesn't seem to work.

I decided to remove the modify and repair options from the installer.


Rename question_formats.description column

The description column on question_formats is very misleading.
We should rename this to something along the lines of "data_url".
@xsrust @briri thoughts?

@xsrust @briri Do you think this task is work doing just now? Would be a good opportunity for @johnpinto1 to become more familiar with Rails migrations and the Schema.rb file

@briri and @xsrust is still still relevant?

I'm not sure. What do you think @xsrust? The column is blank in my DB. Maybe we can just remove it unless we think we will add an admin screen to enable/disable format types in the future as we continue to add new maDMP question types like 'Ethics' or the 'Re3data repo lookup'

We've got this used for the RDA Metadata-standards question-type, it holds the external URL we pull from to populate the question.
I like the suggestion of renaming to data_url and using for these API type integrations.


Turn off discovery when icc == false

This patch is to fix an issue which unveiled during design review of #17230: libnetwork built-in host discovery should not kick in when daemon icc flag is false

LGTM

LGTM


Discrepancy between NumPy's ShapeLike and ours

I think NumPy's ShapeLike is this:
from typing import Sequence, Tuple, Union, SupportsIndex

_Shape = Tuple[int, ...]

# Anything that can be coerced to a shape tuple
_ShapeLike = Union[SupportsIndex, Sequence[SupportsIndex]]

Is our ShapeLike truly a subset of theirs? Would our use of ShapeLike actually allow their definition?  We don't need to adapt to that kind of detail, but we should be aware of the consequences.

Technically our types are subsets of NumPy's types -- good enough.


Update Bitwarden repository url

This fixes #365
However note unfortunately the new combined Bitwarden client repository doesn't always tag the latest releases for reach client as "latest" so the full releases feed is used. This has the unfortunate side-effect of returning not just the current release but all releases and assets that match the filters in the manifest.
One of the "correct" solutions to this would be refactoring Get-GitHubRepoRelease to accept a filter for VersionTag and filter on the "desktop-" prefix and stop returning output when the version changes.
I haven't done this as:

From a quick search OpenJDK is also "broken" in this way returning multiple versions
There are many ways to refactor Get-GitHubRepoRelease and didn't want to start making decisions about this unilaterally without discussion

I don't want to make changes to Get-GitHubRepoRelease for one app. It does currently expect that the repo has the available binaries on the latest release.
This URL is available which might be able to be used to grab the latest version and installer: https://vault.bitwarden.com/download/?app=desktop&platform=windows. This resolves to a pretty messy URL though - https://objects.githubusercontent.com/github-production-release-asset-2e65be/53538899/7d83e8b2-55d7-451b-90ad-b173c46c245a?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220807%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220807T141735Z&X-Amz-Expires=300&X-Amz-Signature=eb01a30df174dd1ffb60bbf57b1af12b0c6d08db5bbf3eb98fd58bdb1f940e4e&X-Amz-SignedHeaders=host&actor_id=8227455&key_id=0&repo_id=53538899&response-content-disposition=attachment%3B%20filename%3DBitwarden-Installer-2022.6.2.exe&response-content-type=application%2Foctet-stream

Another approach might be to see what the app does and how it determines available updates.

Completely understand about Get-GitHubRepoRelease which is why I didn't even get started. Though even with it expecting binaries on the latest release it still "works" in the current form with the new repository and the the /releases rather than /releases/latest it just returns additional older versions assets as well like the OpenJDK package...
That all said a bit of digging has revealed: https://artifacts.bitwarden.com/desktop/latest.yml
The download URLs appear to relative e.g https://artifacts.bitwarden.com/desktop/Bitwarden-Installer-2022.6.2.exe seems to work. The only downside to this appears to be the loss of the "portable" version that was in the GitHub assets. Though I suppose you could get the latest version from https://artifacts.bitwarden.com/desktop/latest.yml and then feed that into the GitHub api as a release tag e.g https://api.github.com/repos/bitwarden/clients/releases/tags/desktop-v2022.6.2
For simplicities sake I have update this PR with the less convoluted option though if you think we should go for the above two stage approach using both the latest.yml  and GitHub happy to change things further.

Also apologies for the horrifically hacky "parsing" of the YAML given I was only after the version number it seemed inappropriate to load a whole YAML parsing package to do something a RegEx could (but perhaps shouldn't :D) do
As an FYI the UserAgent seems to be required else there is a 403 forbidden error.

🤦♂ Seems Bitwarden look up their own repo to find the latest version: https://github.com/bitwarden/clients/blob/bc639688e84c1a997019194312e9c4a8a826479d/libs/node/src/cli/commands/update.command.ts

For the non CLI clients they appear to use electron-updater and this config lead to the latest.yml:
https://github.com/bitwarden/clients/blob/master/apps/desktop/electron-builder.json#L26


User story 1

"as a user who has prepaid"
fix user.
should you use who prepaid instead of who has prepaid. cause it's already done and finish.

fixed


clientv3: wait for ConnectNotify before sending RPCs

With slow CPU, gRPC can lag behind with RPCs being sent before
calling 'Up', returning 'no address available' on the first try.
Fix https://github.com/coreos/etcd/issues/8581 and many other test failures since https://github.com/coreos/etcd/pull/8545.
Full explanation coming...

@xiang90 @fanminshi
Health balancer in https://github.com/coreos/etcd/pull/8545 adds a method balancer.next to force endpoint switch, by notifying empty grpc.Address and draining all current connections in gRPC. But gRPC routine after notify is asynchronous with balancer.next(). It is possible, in slow machine, that:

RPC is sent before connection has been established via balancer.Up
gRPC returns error no address available
clientv3 newRetryWrapper calls balancer.next()
Address is pinned before balancer.next() has been completed
balancer.next() triggers gRPC to drain all connections (including pinned ones)
RPC errors with grpc: the connection is drained
clientv3 newRetryWrapper receives error grpc: the connection is closing, exiting

This happens because balancer.next() is called before the first connection has been established, and then gRPC routine drains all connections while clientv3 balancer pins the address.
This patch makes sure the connection is ready before sending RPC. And returns grpc.ErrClientConnClosing on <-context.Context.Done() to keep the old behavior: RPC with canceled or deadline exceeded context returns gRPC error code codes.FailedPrecondition, and clientv3.toErr translates this error into grpc.ErrClientConnClosing https://github.com/coreos/etcd/blob/master/clientv3/client.go#L498-L520. Accordingly, updates tests to match grpc.ErrClientConnClosing and context.DeadlineExceeded. context.DeadlineExceeded would be returned if CPU or network is fast at establishing initial connection but times out while processing RPCs.

i feel we should not mix deadline exceed and clientclosing error together.

@xiang90 PTAL. Context errors and client closing errors are mixed only for grpc-proxy tests.

lgtm

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b6b4898). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master    #8601   +/-   ##
=========================================
  Coverage          ?   75.81%
=========================================
  Files             ?      358
  Lines             ?    29368
  Branches          ?        0
=========================================
  Hits              ?    22265
  Misses            ?     5546
  Partials          ?     1557

Impacted Files
Coverage Δ

clientv3/retry.go
61.57% <100%> (ø)

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 b6b4898...6368159. Read the comment docs.


KOGITO-2148 Adjustments for nightly pipeline

https://issues.redhat.com/browse/KOGITO-2148
To be able to run both pipelines in parallel for some time, I just copied Jenkinsfile.deploy to Jenkinsfile.deploy.new and removed triggers and notifications (as that will be part of the nightly pipeline).
Jenkinsfile.deploy is still used by currrent deploy pipeline.
That Jenkinsfile.deploy.new file will be called by kogito.nightly.
Once the nightly pipeline is stable on master, there will be a new PR to replace Jenkinsfile.deploy by Jenkinsfile.deploy.new and the current deploy pipeline will be deleted in favor of the new nightly pipeline.
Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Pull Request title is properly formatted: KOGITO-XYZ Subject
[ ] Pull Request title contains the target branch if not targeting master: [0.9.x] KOGITO-XYZ Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains link to any dependent or related Pull Request
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket

Changed so that it works for a regular pipeline instead of multibranch

@radtriste so we're going to need to setup the job manually for each branch then?

@cristianonicolai nope we won't need. We will have only one job (branch to build is a parameter).
This job is meant to be called by the kogito-nightly which will know which branch to use and has the nightly / daily trigger.
But you can still execute that job here manually and give the correct branch as parameter if needed.

I just added the deployment of examples as this one is mandatory for s2i builds to happen currently ...
For more information, see https://issues.redhat.com/browse/KOGITO-2342

@cristianonicolai @sutaakar @MarianMacik can you have a final look ?
The job itself is quite stable: https://rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/KIE/job/kogito/job/kogito-runtimes-deploy/

@radtriste looks good. Just wondering if emails to Zulip would be sent from here or parent/caller job?

This should be sent from parent.
But I could add a param to do it if enabled (in case we want to launch the job in standalone mode)

@radtriste np, just wanted to make sure we were not missing it.


feat: Update page templates

to use Article component
resolves #62

@TeddTech Please test this for any issues by running the dev script and navigating to all the pages to make sure that the expected content is there. Also please check the spelling of the page file names.

Thank you for catching that. Weird the linter usually catches when a used custom tag isn't listed in the components method.


fix: make dark style of navbar properly

Fixes bugs reported in the comment https://github.com/facebook/docusaurus/issues/3937#issuecomment-931261658

Before
After

thanks 👍


localStorage

Currently it says "up to 5MB is safe to use", that is not correct. Thanks to Chrome (and a few other browsers), only 2.5MB can be relied on.
See http://dev-test.nemikor.com/web-storage/support-test/ and related Chromium issue: http://code.google.com/p/chromium/issues/detail?id=58985#c15
An alternative wrapper library is Amplify.js Store: http://amplifyjs.com/api/store/ - that falls back to globalStorage and userData, instead of cookies (ugh). Recommending to use cookies as a fallback sounds like a really bad idea.
That sessionStorage project seems to also be rather odd. Using window.name along with "secure" cookies? Really?

Thank you for the reference to the Chromium bug, I tried to find that. I'll accept the pull request in Issue 75 (#75).
Cheers!


Spell Previews

Show a important spell information when hovering over a spell in the Player sheet.

Blocked on #6 because the strange design prevents the popup from covering the other spell boxes


Parallelize generate-packages and create-search-index

Also includes not-needed packages in the source index.

Sorry, merged the other PRs and somehow created a conflict here. :+1:


Retrieving call count to easily make assertions on call count

currently, the expect/3 api only performs call assertion at the end of the test case. However, there are situations where it is ideal to make call assertions throughout the test case (e.g. that api calls are made correctly, args are correct, etc), much like how :meck exposes a few functions to make call assertions easier.
Are there plans for such an API? I can dig into this and raise a PR if so.

Would verify! do what you are describing https://hexdocs.pm/mimic/Mimic.html?#verify!/1 ?


Can't rerun existing completed taskruns

Expected Behavior
There can be some fields that can automatically delete taskruns or completed pods if necessary.
If you don't want to delete existing succeeded taskruns, please allow me to rerun the same name of taskrun, like kubectl apply which can configure the same Deployment and the pod will rerun.
Actual Behavior
At present, when a taskrun is succeeded and the related pod is completed, they have not been deleted and cannot be re-run.
Sure, there's other way to delete taskrun and pod, such as kubectl delete, but there may be so many existing completed taskruns to rerun. To do so, first , i have to delete the exising taskruns and pods, then rerun. Even if I only delete related pod, I can't rerun taskRun.
Steps to Reproduce the Problem

When pod is completed, i rerun "kubectl apply -f taskrun.yaml", pod cannot rerun.
Delete pod but not related taskrun, apply taskrun.yaml, pod also cannot rerun.
Delete taskrun(of course, pod will be deleted), apply taskrun.yaml, pod can rerun.
Maybe PipelineRun is same with taskRun.

@vdemeester Would Pipeline or Operator like to design some fields used in yaml which means that succeeded taskruns can be deleted automatically after ttl time , or they can be deleted in batches?

see add taskrun_expired and pipelinerun_expired for deleting taskRuns or pipelineRuns automatically


[8.x] Added a method to the Macroable trait that removes all configured macros.

This pull request adds a static flushMacros method to the Macroable trait that removes all the configured macros.
The primary use of this method is in a unit testing environment. When running multiple test cases that add static macros in the same process, there can be side-effects between test cases caused by the use of static members.
When combined with either the --random-order flag to PHPUnit or parallelized testing, these side effects can cause intermittent failures, as tests may or may not pass depending on the order / process they are ran in and the result of the side effects.
Ideally each unit test case is ran in a sanitized environment to ensure the developer is testing exactly what they intended to test, and aren't relying on any aspects setup outside of the current test case.
I was unsure as to whether the framework should enforce the running of flushMacros on contained Macroable classes, or whether the developer should handle this manually so i haven't done that.
Also enforcing that macros are always flushed is a not fully backwards-compatible change, whereas adding a method to allow developers to handle it themselves is.
Thanks for your time.

rebased the branch because i noticed i had my work email set in git and not my noreply github one, whoops!


feat: 2024 05 25 - [merged]

Merges feat-2024-05-25 -> development
#27 #28

added 20m of time spent

added 1 commit
249b9cba - fix: add static files path to urls
Compare with previous version

mentioned in commit 249b9cbab9e8f917e0e1ecd97fbcc5300c1c832f

added 1 commit
f36400db - feat(setting): Enable super admin to set ALL software as global
Compare with previous version

mentioned in commit 900412b31706fbba0040139dd5a04b76aeb32af2

mentioned in commit 3128daee2aef580781ddf523f5b1190ea5150b96

mentioned in commit f36400dbb98d305e1ec54f62493f7f2cff0359b1

added 1 commit
3128daee - feat(setting): Enable super admin to set ALL software as global
Compare with previous version

added 2 commits
900412b3 - refactor(context_processor): relocate as baseee7977fe - feat(user): Add user settings panel
Compare with previous version

mentioned in commit ee7977fe4a5e78844e8652c313af49eda901bdad

added 1 commit
2034a57b - feat(setting): Enable super admin to set ALL software as global
Compare with previous version

mentioned in commit 2034a57b5ce7c1c7bdd9367ec88d0a9f8927706a

mentioned in commit 51dd9fb19e1f5ff0b150d004803baaa4623cbe65

mentioned in commit 433c69adfbdc274910d83e5334e4b6cdf3cfd3db

mentioned in commit e66e9b8dca740ffe411b74c8f50c53c732acef2f

added 1 commit
395f24f2 - feat: Add management command software
Compare with previous version

added 1 commit
3481350b - feat: Add management command software
Compare with previous version

added 1 commit
51dd9fb1 - feat: Add management command software
Compare with previous version

mentioned in commit af809183c81213b3941ac2dec971e0fc322c3bc9

mentioned in commit 3481350bf21dca366bfb33a630e0d8494412d93d

added 1 commit
433c69ad - feat: Add management command software
Compare with previous version

mentioned in commit 395f24f22c5418eed99d59659b7c60726c2ade53

mentioned in commit 7f4a036a32630599ef95bbe801d24e6204c61fcf

mentioned in commit 62c0bb77fe5134669e77b198acc02c28ea073696

mentioned in commit 7f3bf95b4627be434732b1045120e59fcae21cf3

mentioned in commit 9f5e5d25ec574caa0aeec91c5763f7f64c8b11c2

mentioned in commit 4c002bc259062fc4926deda8a943d165496c8a25

mentioned in commit abbd6a49d64fc24eb2c27191b594e8cefdb9042b

mentioned in commit b2f7c831551469445d091cd176ab6f210ec862e1

added 9 commits
abbd6a49 - feat(device): Populate initial organization value from user default organization7f4a036a - fix(device): OS form trying to add last inventory date when empty62c0bb77 - feat(itam): Populate initial organization value from user default organization...9f5e5d25 - feat(itam): Populate initial organization value from user default organization...7f3bf95b - feat(api): Populate initial organization value from user default organization inventory90f95672 - feat(itam): Populate initial organization value from user default organization...4c002bc2 - feat(itam): Populate initial organization value from user default organization...e66e9b8d - feat(itam): Populate initial organization value from user default organization...af809183 - chore: set if device has no type, return '-' for listview
Compare with previous version

mentioned in commit 90f95672aa71c0a5358238f491949fb356503ff3

mentioned in commit 96777f1beadb24328b3d90061220b6632b1bc575

added 11h 50m of time spent

mentioned in commit 668e871e4fd52abb20426b8dafa988c423d3d3a7

added 2 commits
b2f7c831 - feat(base): Add delete icon to content header668e871e - refactor(itam): relocation item delete from list to inside device
Compare with previous version


Support CICP

Would it be possible to add CICP support while this feature is 'only' part of the Working Draft?
https://www.w3.org/TR/png-3/#cICP-chunk

Given the dominant prior art (or posterior art?) of other formats choosing that triple for color space representations, yes, certainly. Should be simple to add? Similar to icc it'd be better not to delete any of the chunk decodings but simply offer it as an alternative.

I think there is one major conceptual question for me: What to do with color-matrix values other than RGB (0 iirc).
I guess, at least at image-rs level it's required to transform to RGB to fit into the current DynamicImage logic? So it would have to apply the specified matrix transform. However, would we change the CICP field in this case? Theoretically, those questions already apply for AVIF already, but since it's currently limited to 8bit in images-rs anyways, it does not seem to be practically relevant.
On the other hand, GTK will happily apply the color-matrix values on the raw data and might even pass the original texture through if it's the right format for the compositor/monitor. So there might be arguments for having the raw option available. However, I think it is not that's not that performance relevant for still images.

I wouldn't worry about the transformation into rgb in image. The png crate returns the raw color components and image's DynamicImage is about as wrong as it is currently when ignoring the chunk. More importantly, the Transformation options should get a bit of scrutiny. Is expanding 0xab to 0xabab the right transform for all OETFs?  Not fully but then again it's still in the intended interval so maybe good enough.
In the midterm we're also moving image to preserving the raw color values for as long as possible, and only collecting the metadata of intended transforms. Then these can be composed with the output transform and applied by either the compositor, the monitor, or manually. This is more correct and more performant.

What to do with color-matrix values other than RGB (0 iirc).

And to answer that concretely: I'd return it in an enum and maybe add methods to resolve those enum variants into XYZ primaries. Or not if there's any open questions, it can also be done at a later point.

IIRC at the moment the spec says that matrix coefficients should be 0. I believe (unless something changed in the meantime) that Chrome will refuse to interpret anything else.
OTOH the spec says that the full-range flag can be 0 too, but Chrome doesn't support that (~and if it were up to me, it never will~), and I don't see why one would ever want to do video-range RGB anyway in 2023...
Implementation of cicp in the JXL PNG en/decoder: https://github.com/libjxl/libjxl/blob/main/lib/extras/enc/apng.cc#L161 https://github.com/libjxl/libjxl/blob/main/lib/extras/dec/apng.cc#L89
In Chrome: https://chromium-review.googlesource.com/c/chromium/src/+/3705739

I think that this just got implemented: https://github.com/image-rs/image-png/pull/529


channel.generateSignedTransaction is not a function in e2eUtils.js is not a function?

Hi all,
I could not pass the below test while having failure report on channel.generateSignedTransaction. Can anyone please share any clue on the root cause?
Thanks,
MJ
mjjeon@swarm06:~/caliper$ sudo node benchmark/simple/main.js -c config-file.yaml
[sudo] password for mjjeon:
info: [bench-flow.js]: ####### Caliper Test #######
info: [bench-flow.js]: Executing command: docker-compose -f network/fabric-v1.1/2org1peergoleveldb/dCreating orderer.example.com ... done
Creating network "2org1peergoleveldb_default" with the default driver
Creating peer0.org2.example.com ... done
Creating orderer.example.com ...
Creating ca.org2.example.com ...
Creating peer0.org1.example.com ...
Creating peer0.org2.example.com ...
info: [create-channel.js]: Creating mychannel...
info: [create-channel.js]: Created mychannel successfully
info: [create-channel.js]: Sleeping 5s...
info: [join-channel.js]: Joining channels...
info: [join-channel.js]: Joining mychannel...
info: [join-channel.js]: Successfully joined peerOrg1's peers to mychannel
info: [join-channel.js]: Successfully joined peerOrg2's peers to mychannel
info: [join-channel.js]: Successfully joined mychannel
info: [install-chaincode.js]: Installing chaincodes...
info: [packager/Node.js]: packaging Node from /home/mjjeon/caliper/src/contract/fabric/marbles-norichquery/node
info: [packager/Node.js]: packaging Node from /home/mjjeon/caliper/src/contract/fabric/marbles-norichquery/node
info: [install-chaincode.js]: Installed chaincode marbles successfully in all peers
info: [packager/Node.js]: packaging Node from /home/mjjeon/caliper/src/contract/fabric/simple/node
info: [packager/Node.js]: packaging Node from /home/mjjeon/caliper/src/contract/fabric/simple/node
info: [install-chaincode.js]: Installed chaincode simple successfully in all peers
info: [instantiate-chaincode.js]: Instantiating chaincodes...
info: [e2eUtils.js]: The chaincode instantiate transaction was valid.
info: [instantiate-chaincode.js]: Instantiated chaincode marbles successfully
info: [e2eUtils.js]: The chaincode instantiate transaction was valid.
info: [instantiate-chaincode.js]: Instantiated chaincode simple successfully
info: [instantiate-chaincode.js]: Sleeping 5s...
info: [bench-flow.js]: Started monitor successfully
info: [bench-flow.js]: ####### Testing 'open' #######
info: [bench-flow.js]: ------ Prepare(file-write) waiting ------
error: [e2eUtils.js]: Failed to send transaction error: TypeError: channel.generateSignedTransaction is not a function
error: [e2eUtils.js]: Failed to send transaction error: TypeError: channel.generateSignedTransaction is not a function
error: [e2eUtils.js]: Failed to send transaction error: TypeError: channel.generateSignedTransaction is not a function
error: [e2eUtils.js]: Failed to send transaction error: TypeError: channel.generateSignedTransaction is not a function
error: [e2eUtils.js]: Failed to send transaction error: TypeError: channel.generateSignedTransaction is not a function

Can you check the version of fabric-client and fabric-ca-client that have been installed?

@jmj119 this file mode only supports fabric v1.1 and fabric v1.2.  When using this file mode, please rename the file src/adapters/fabric/ChannelSignedTransaction.js  with Channel.js  and then replace
the original file node_modules/fabric-client/lib/Channel.js with the new file Channel.js. Please note that it would be better to backup your original file Channel.js.

Since Fabric client does not support the function generateSignedTransaction/sendSignedTransaction in the versions 1.1 and 1.2.

@feihujiang Copying the file works! Thanks all for the comments and help!


v9 leave within useTransition misses unit when interpolating from unit-less 0

🐛 Bug Report
Here's my code:
const OuterLayout = () => {
  const [show, setShow] = React.useState(false);
  const transitions = useTransition(show, null, {
    unique: true,
    from: {opacity: 0, transform: "translate3d(0,70%,0)"},
    initial: {opacity: 1, transform: "translate3d(0,0,0)"},
    enter: {opacity: 1, transform: "translate3d(0,0,0)"},
    leave: {opacity: 0, transform: "translate3d(0,50%,0)"},
  });
  return (

      {transitions.map(
        ({item, key, props}) =>
          (item && console.log("0", props.transform.calc(0), "1", props.transform.calc(1))) ||
          (item && (
            <animated.div key={key} style={props} > + </animated.div>
          ))
      )}

  );
};

the accompanying console.log looks like this
"0" "translate3d(0,0,0)" "1" "translate3d(0,0,0)"
"0" "translate3d(0,0,0)" "1" "translate3d(0,50,0)"
"0" "translate3d(0,0,0)" "1" "translate3d(0,50,0)"

as you can see, the 50 misses its unit. And thus it doesn't get animated. Note that it only happens on the first transition.

react-spring 9.0.0-beta.31 (but also on latest v8)
react v16.9.0

Ah, I just found out that this can be fixed by adding the corresponding unit to the 0 in initial i.e. translate3d(0,0%,0).

I think for avoid this kind of issues juste use only number on from/enter/leave/initial values and use interpolation on render.
Example:
const OuterLayout = () => {
  const [show, setShow] = React.useState(false);
  const transitions = useTransition(show, null, {
    unique: true,
    from: {opacity: 0, transform: 70},
    initial: {opacity: 1, transform: 0},
    enter: {opacity: 1, transform: 0},
    leave: {opacity: 0, transform: 50},
  });
  return (

      {transitions.map(
        ({item, key, props}) =>
          (item && console.log("0", props.transform.calc(0), "1", props.transform.calc(1))) ||
          (item && (
            <animated.div key={key} style={{
              opacity: props.opacity,
              transform: props.transform.interpolate(v => `translate3d(0,${v}%,0)`)
            }} > + </animated.div>
          ))
      )}

  );
};

Thanks, it's good to know that there are work arounds, but I still feel like this is a bug that might affect and confuse quite some people, especially since adding a unit to a transition starting from 0 seems to works with enter but not with initial.

especially since adding a unit to a transition starting from 0 seems to works with enter but not with initial.

Please provide a sandbox that demonstrates this claim. Thanks!

repro is here: https://codesandbox.io/s/elegant-platform-1xu4s
check out the console.logs and note that the transform won't be correctly applied when clicking the button for the first time.

Fixed in #809
You can try it today: npm install<EMAIL_ADDRESS>Here's your example with the required changes:
import React from 'react'
import { useTransition, a } from 'react-spring'

const Demo = () => {
  const [state, set] = React.useState(1)
  const transition = useTransition(state, {
    from: { opacity: 0, transform: 'translate3d(0,70%,0)' },
    initial: { opacity: 1, transform: 'translate3d(0,0%,0)' },
    enter: { opacity: 1, transform: 'translate3d(0,0%,0)' },
    leave: { opacity: 0, transform: 'translate3d(0,50%,0)' }
  })
  return (

        <button onClick={() => set(state => state + 1)}>click</button>

        {transition((props, item) => (
		  item % 2 > 0 && +
		))}

  )
}

export default Demo


Graph banner lost

On Obsidian Version 1.7.7 (Installer 1.5.3) the plugin doesn't appear anymore... The graph banner frame doesn't show-up!
Anyone has the same issue?
Thanks.

Thank you for your bug report!
Could you tell me about your environment?
The banner grash is displayed correctly on my PC (Windows11) and iPhone (iOS18).
Please try to reload Obsidian or open new note after closing all notes.

This is really strange :-)
I can confirm that banner graph is displayed correctly on my iPhone (iOS 18.1.1)
I can confirm that banner graph is NOT displayed at all on my iPad (iPadOS 18.1.1)
I can confirm that banner graph is NOT displayed at all on my MacBook (Sequoia 15.1)
I closed all notes, reload Obsidian, restarted the OS.
This bug came with new version of Obsidian...

Another behavior I noticed and that could maybe help to understand what’s going on.
On iOS and iPadOS (I didn’t try yet for MAsOS) for some notes, the graph banner is displayed in edit mode bit disappear when you switch in preview mode. You can do that several times.
I tried with the “Time” option values : 1000, 5000, 100, 500, always the same behaviour.
Thanks


Build timeout for extremely large doc set

Details
Hi gang,
I have a gigantic REST API doc set that is hitting the build time limit (and probably the space limit as well) and failing. Does anyone have any suggestions for a workaround? I'm only going to have to build this doc set once, as it's not part of an actively developed project; we just need to be able to consult it for support purposes.
If this issue is for a specific project or build, include the following:

Project: linerate-api
Build #: 3989765; Build #3992486

Thanks!

In the default RTD theme, you can click the green version tag in the bottom left corner to show links to downloadable HTML, PDF and ePub versions.
As far as I know these are generated by default for everything that they host.

Project looks to be removed, so can't provide much guidance. We can look into bumping up the allowed limits if nothing else.

@agjohnson - thanks for looking, my apologies for not updating this thread earlier. I hid the project because I didn't want to confuse our customers. I tried building it locally with sphinx and it took a few hours, so I think I'm just not going to be able to use read the docs for this project (sob!).

Yeah, that's a long time to be blocking the community queue. We can provide more resources on our base plans on readthedocs.com, so especially if this is a commercial project, I'd consider a plan there.


Add New Features and Enhance TensorFlow ConstOp Tests

Overview
This pull request introduces several new features to the TensorFlow constant operation tests, enhancing the coverage and robustness of the tests. Key additions include tests for complex numbers, boolean values, large tensors, mixed data types, and range values.
New Features

Complex Numbers: Added a test case to check the creation of tensors with complex numbers.
Boolean Values: Added a test case to verify the creation of tensors with boolean values.
Large Tensor: Added a test case to create and verify a large tensor.
Mixed Data Types: Added a test case to check behavior with mixed data types (should fail).
Range Values: Added a test case to create tensors from a range of values.

Detailed Changes

Complex Numbers: Ensured support for complex number tensors and verified with appropriate tests.
Boolean Values: Verified the creation of boolean value tensors.
Large Tensor: Tested the creation and validation of a large tensor to ensure performance and correctness.
Mixed Data Types: Checked the behavior of tensors with mixed data types to ensure appropriate error handling.
Range Values: Created tensors from a range of values to validate correct tensor generation.

Impact
These enhancements improve the test coverage for TensorFlow's constant operations, ensuring more robust and comprehensive validation of tensor creation and handling.
Testing
Tested the code with various constant definitions and inputs to ensure functionality remains intact. Verified that error handling works as expected for invalid inputs and mixed data types.
Notes

Ensure all dependencies are up-to-date to avoid compatibility issues.
Review the added test cases to ensure they align with the intended usage and edge cases.

Please review the changes and let me know if there are any questions or further modifications needed.

Hi @sanowl Can you please sign CLA? Thank you!

Hi @sanowl Can you please sign CLA? Thank you!

Hi @sanowl, Can you please sign CLA? Thank you!

Hi @sanowl, Can you please sign CLA? Thank you!

Hi @sanowl I'm going to go ahead and close this PR, because it seems to have stalled. If you're still interested in pursing this (and responding to my comments), please feel free to reopen. Thank you for your contribution!


Unable to change default calendar view

Hi all,
First of all, I would like to thank you all for you GREAT job done in this project.
I have a question/bug because I've tried to change the default calendar view to "month" as indicated in issue https://github.com/fguillot/kanboard/issues/683 but nothing works.
Do I need to change anything else? Is it working for you?
Thank you so much.
Best regards,
Carlos.

If you change the Javascript don't forget to rebuild assets: https://github.com/fguillot/kanboard/blob/master/docs/assets.markdown


Custom metrics

Nice work on this. I like the direction that you are headed. I'll be honest, I have not looked too deeply into the code base yet, but have you put any thought into providing some sort of an API to providing custom metrics?
For example, it would be nice if I had some sort of a decorator, or something that would allow me to report back a custom metric on a particular endpoint. In particular, I am thinking about a way to report to prometheus the number of live sessions and websocket connections are open.

@ahopkins
sanic_prometheus uses prometheus_clitn, so you can just add custom mertic in every part of you code and it will be automatically exposed.
Try, for exampe, this snippet.

Beautiful. Thank you.


Not working for Stellaris

Continuing this issue here since the upstream repo got archived.
@clamor-s @rednatnas I just tested the latest creamlinux release on Stellaris 3.7.4 with up to date DLCs and it appeared to work fine (the game launched, the DLCs loaded and I could start a campaign). So it appears it was an outdated DLC files issue all along. Please test when you can and see if it works for you.

Yes, I do have red triangles but the DLCs nevertheless work in-game. If you have Discord, you can send me a friend request (anticitizen#0067). Otherwise send me a message at the e-mail on my github profile page

@anticitizn @rednatnas I can confirm that issue was in dlc.

It's confirmed then that outdated DLC files are the culprit.

It's confirmed then that outdated DLC files are the culprit.

Thanks I'll try that out!

@rednatnas I just saw this issue. Am I understanding correctly that Stellaris works fine on creamlinux 1.3 even with outdated DLC files?

@rednatnas I just saw this issue. Am I understanding correctly that Stellaris 3.7.3 works fine on creamlinux 1.3 even with outdated DLC files?

yeah, that's right


Dart and analyzer treat name conflict in the different ways

Dart SDK version: 2.14.4 (stable) (Wed Oct 13 11:11:32 2021 +0200) on "windows_x64"
The following source code example should throw compile errors:
    class C {
      int s1 = 1;
      int s2 = 1;

      static set s1(var value) => throw "Should not reach here";
      static String s2() => throw "Should not reach here";
    }

    main() {}

It throws 2 compile errors with analyzer and 3 compile errors + 1 warning with dart.
So is this a correct result or both tools should produce the same?
There are two kinds of conflicts here, because two instance variables implicitly induce a getter and a setter, so we have the conflict specified in 'Class Member Conflicts' as well as a regular name clash.
Analyzer reports the 'Class Member Conflicts' error, and it seems reasonable to omit the plain name clashes. Sample output is:
    Analyzing test.dart...
      error - Class 'C' can't define static member 's1' and have instance member 'C.s1' with the same name. - test.dart:5:14 - conflicting_static_and_instance
      error - Class 'C' can't define static member 's2' and have instance member 'C.s2' with the same name. - test.dart:6:17 - conflicting_static_and_instance
    2 errors found.

With dart we get the plain name clash, and not the 'Class Member Conflicts' error for s1. For s2, this is again the plain name clash, although via the implicitly induced members. Sample output is:
    test.dart:6:17: Error: 's2' is already declared in this scope.
      static String s2() => throw "Should not reach here";
                    ^^
    test.dart:3:7: Context: Previous declaration of 's2'.
      int s2 = 1;
          ^^
    test.dart:5:14: Error: Conflicts with the implicit setter of the field 's1'.
      static set s1(var value) => throw "Should not reach here";
                 ^
    test.dart:2:7: Error: Conflicts with setter 's1'.
      int s1 = 1;
          ^

The question might be whether we expect the number of errors reported to be specified.
In this case we have a direct name clash because the instance variable declaration named s1 implicitly induces two declarations named s1 and s1=, and the static setter declaration has name s1=. At the same time, we have an error because the interface of C includes member signatures named s1 and s1=, and we have a static member s1=. The former error occurs because the instance variable is declared in C, but the latter error would also have occurred if the instance variable had been inherited. Those two errors are specified in different locations in the specification (here and here).

The front end seems to be more informative than the analyzer because it points out both declarations that are conflicting.
It's not internally consistent, though, since it uses Context for one and Error for another.

The presentation could be improved to make this more clear, but the front end isn't reporting two diagnostics. It's reporting a single diagnostic (labeled as 'Error') and one context message (labeled as 'Context'). A context message is additional information that is associated with, and provides context for the user to understand, a diagnostic.
In my opinion, it would be better if the context message were indented under the diagnostic in order to make the relationship more clear. It would also be better to not print 'Context' at all, and especially not in a way that makes it look like another level of severity.
But I agree, the analyzer really ought to also provide a context message in this case so that it's easier for users to locate the other declaration that's causing a conflict.

But it may seem overly formalistic to require that both of these errors are reported, because they're "about the same name clash" for anyone who isn't spending their time writing language tests. ;-)

In my mind it's less about being "formalistic" and more about providing the best UX possible. Rather than look at it in terms of how many places the code is violating the specification, I think we want to look at it in terms of how many things the user needs to change in order to bring the code into compliance with the specification. If an instance and static member conflict, then there's really only one problem that needs to be fixed (with several possible ways that the user might choose to fix it).

Do we have a partial order among all compile-time errors such that we can gather a set of errors that apply at a given location, and then just report the most "informative" one?

No. I'm not actually convinced that (a) we could come up with a partial order or (b) that if we did that it would be the case that the diagnostics that ought to be removed would always be reported at the same location as the "informative" one. It would be nice, though, if we could automate some of the process of eliminating follow-on diagnostics.

eliminating follow-on diagnostics

I'm not quite sure what that means, but I wasn't thinking about error propagation (that is, var x = 1 + true; is an error, and now print(x); could be an error, too). We very likely want to avoid reporting propagated errors, but they would be related by a chain of cause-and-effect, so there's no need for an ordering on the error messages themselves, we just suppress the emission of each cause-and-effect path immediately after one step, and that probably typically done by using a special InvalidType which doesn't cause errors when used, no matter how.
I was thinking about errors that arise independently at the same location (that probably needs to be at overlapping or nested char offset ranges). For instance, if an instance member has both a name clash and an incorrect-override error.
Do we generally want to report all of those, or just the one that has the highest priority in some sense?
And if we generally want to report all of them, why wouldn't we report both the plain name clash and the 'Class Member Conflicts' error in the original example in this issue?

The way I think of it (which might not be right) is that the spec describes two static errors because it needs to do so in order to be complete. But from a user's point of view there's only one problem: the name can't be used for both an instance member and a static member in the same class. The number of diagnostics should equal the number of problems, not the number of places in the spec where a static error is described.

I'm not quite sure what that means ...

I think of a follow-on diagnostic as a diagnostic for a problem that wouldn't exist if some different problem were fixed. But after thinking about this more, I don't think it's relevant because the probably isn't the kind of situation you were thinking about.

I was thinking about errors that arise independently at the same location ... For instance, if an instance member has both a name clash and an incorrect-override error.
Do we generally want to report all of those, or just the one that has the highest priority in some sense?

That's a little harder. If the user solves the name clash by renaming the instance member, then maybe there was only one problem. But if the user solves the name clash by renaming the static member, then it appears that there were two problems. Because we don't know which situation we're in we don't have enough information to make a perfect choice.
I suspect that we generally opt to report both diagnostics at that point, but there's no compelling reason that I can think of to do so.