"Plan contains a non-contiguous sequence of pre-deployment migrations"

I'm using the django-syzygy library and encountered an issue.
Let's say I'm doing 2 unrelated migrations; each one generates 2 migrations: pre and post.
When trying to apply both pre migrations with ./manage.py migrate --pre-deploy I get the error:
CommandError: Plan contains a non-contiguous sequence of pre-deployment migrations.
Is that expected? How can I overcome this issue?
I'm using:
python 3.10.11
django==4.1
django-mysql==4.9.0
django-syzygy==0.1.0a10

Very hard to tell without your set of migrations. You normally get this error message when trying to combine pre and pre-post migrations that depend on each other but there was a bug in 0.1.0a11 that didn't account for some installed app order cases that was fixed in 30b348b5ebc5caae1b2c0af8ed9ade22c4fa2d91.
Can you retry with 0.1.0a11?

Hi,
Thanks for the answer.
I upgraded the django-syzygy package to 0.1.0a11, and tried again.
For example, I added a new field to a table, and then added another field to the same table.
Here are the 4 migration files that was created:
0363_migration
# Generated by Django 4.1 on 2023-05-17 12:40

from django.db import migrations, models
import syzygy.operations

class Migration(migrations.Migration):

    dependencies = [
    ]

    operations = [
        syzygy.operations.AddField(
            model_name='mymodel',
            name='my_new_field1',
            field=models.CharField(max_length=200, null=True),
        ),
    ]

0364_migration
# Generated by Django 4.1 on 2023-05-17 12:40

from django.db import migrations, models
import syzygy.operations

class Migration(migrations.Migration):

    dependencies = [
        ('dialogflow', '0363_migration'),
    ]

    operations = [
        syzygy.operations.PostAddField(
            model_name='mymodel',
            name='my_new_field1',
            field=models.CharField(max_length=200, null=True),
        ),
    ]

0365_migration
# Generated by Django 4.1 on 2023-05-17 12:41

from django.db import migrations, models
import syzygy.operations

class Migration(migrations.Migration):

    dependencies = [
        ('dialogflow', '0364_migration'),
    ]

    operations = [
        syzygy.operations.AddField(
            model_name='typeformsurvey',
            name='my_new_field2',
            field=models.CharField(max_length=200, null=True),
        ),
    ]

0366_migration
# Generated by Django 4.1 on 2023-05-17 12:41

from django.db import migrations, models
import syzygy.operations

class Migration(migrations.Migration):

    dependencies = [
        ('dialogflow', '0365_migration'),
    ]

    operations = [
        syzygy.operations.PostAddField(
            model_name='mymodel',
            name='my_new_field2',
            field=models.CharField(max_length=200, null=True),
        ),
    ]

When running ./manage.py migrate --pre-deploy I still get the error CommandError: Plan contains a non-contiguous sequence of pre-deployment migrations.
Since we don't have full CI/CD, many migrations that was created by several developers should run once a week, so cases like this are going to happen a lot. How can I overcome this?

I don't think you understand the purpose of this tool, it is meant to be used in a CD pipeline where changes are shipped incrementally and deployed in a way that pre-deployment and post-deploment changes are shipped with the deployment that depend on them.
From what I can see here the tool is doing exactly what it was designed for, it's telling you that it cannot deploy all migrations it has detected to be required to run pre-deployment (0363 and 0365) because 0364 must be run after a deployment completes.


vagrant-completion 1.8.1

I just merged #121 that updates it to 1.8.4; thank you anyway @Jerzerak! 😃


Verify that the schema contains necessary directives (#9).

graphql-core already validates that the schema contains the directives used in the query via the known_directives validation rule. I've added a test to verify this behavior, but I may have misinterpreted the issue (#9): do we wish to verify that the schema contains all the directives, or solely the ones used within the query?

Coverage remained the same at 93.717% when pulling 1537660c2271f0b67eaa7bca2b068e6cd56b4be8 on benlongo:validate-schema into 9eb7f04d90aa1579ee14cbfd92e59b7ac7c81af2 on kensho-technologies:master.

Hey @benlongo -- thanks for grabbing this issue, and apologies that I didn't write it more clearly.
If a user is using the compiler to compile GraphQL queries, we expect that their schema contains all directives the compiler needs to do its job, regardless of whether a particular query uses them or not. In addition to GraphQL's existing "any directive used in a query must have been present in the schema" rule, we want a rule that says "the directives present in the schema are exactly the directives the compiler wants".
So that would mean that the incomplete_schema in your test should raise errors for any passed query, since the schema doesn't contain the @output directive and therefore the user is using the compiler incorrectly.
Does that make sense?

Yeah that makes sense. I suspected this was the desired behavior but didn't want to proceed further until it was confirmed. I'll take a first pass at it later today, thanks!

Thank you!

Coverage remained the same at 93.714% when pulling 6f8c7fa1e186ba7b89352428fe3101a6a9b551e0 on benlongo:validate-schema into a36ac0969468dbe4e5dea3236fa5664bd996924b on kensho-technologies:master.

Hey @benlongo, are you still working on this PR or would you like me to take it over?

Hey @obi1kenobi,
Sorry I have not had the time to finish this up. There is a slight annoyance in determining if the directives defined in the schema are a superset of the ones we require because their equality methods check the descriptions. There is likely an elegant workaround that doesn't dig into the graphql internals.
I will probably be unable to work on this for the next couple of weeks so you are welcome to take it over.

@jssandh2 feel free to take this over.


Introduce Pull Request Reviewers

Introduces a generated set of code owners to ensure a good contribution experience.
For more details/timelines (internal): go/codeowners

@confluentinc/csid-reviewers, @confluentinc/csid-contributors, @confluentinc/csid-admins please take action to review and merge this pull request.
For more details/timelines see: go/codeowners
Note: This pull request and subsequent comments are automatically generated

@confluentinc/csid-contributors, @confluentinc/csid-admins, @confluentinc/csid-reviewers please take action to review and merge this pull request.
For more details/timelines see: go/codeowners
Note: This pull request and subsequent comments are automatically generated


Can't npm publish :(

npm doesn't let me publish
» npm publish
npm http request PUT https://registry.npmjs.org/aegir
npm http 403 https://registry.npmjs.org/aegir
npm ERR! publish Failed PUT 403
npm ERR! Darwin 15.4.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "publish"
npm ERR! node v4.3.2
npm ERR! npm  v3.8.7
npm ERR! code E403

npm ERR! you do not have permission to publish "aegir". Are you logged in as the correct user? : aegir

Although it lists me as an owner https://www.npmjs.com/package/aegir

Should be fixed, try again

+<EMAIL_ADDRESS>done :) What was it?


CrossGeolocator does not prompt for Location permission

Please take a moment to fill out the following (change to preview to check or place x in []) and remove all unused areas
This is a

[x] Bug

Which plugin does this impact:

[x] Geolocator

Bug
Version Number of Plugin: 3.0.4
Device Tested On: LG K8 (K350)
Simulator Tested On: N/A
Expected Behavior
Location permission should be prompted for
Actual Behavior
Location permission is not prompted for
Steps to reproduce the Behavior
Create instance of GeoLocator and call StartListeningAsync

I will add this in the future, checkout using the Permission Plugin until then.

This issue was moved to jamesmontemagno/GeolocatorPlugin#2


Flake?: TestSSHAuthSockPathHandling

Seeing this test fail in #8442 but it doesn't seem related.
Example:

https://dagger.cloud/dagger/traces/592be290e8f8cba6b3aca5baf50ae88b?span=005d3cee7b94ac88

Error: module at source dir "" doesn't exist or is invalid

Looks like this test was added in https://github.com/dagger/dagger/pull/8365
cc @grouville

Probably a flake, I've been tracking another one last week 🙏 Hope it's not blocking the PR

Confirming race, keeping a look at it

Found the fix, unsure about the implications:
When running this script, we can basically get the flake right away, in less than 10 iterations:
#!/bin/bash

log_file="test_results.log"
max_iterations=10

echo "Starting test loop. Results will be logged to $log_file" | tee -a "$log_file"

for i in $(seq 1 $max_iterations); do
    echo "Iteration $i of $max_iterations" | tee -a "$log_file"
    echo "----------------------------------------" | tee -a "$log_file"

    go test -race -count=1 ./core/integration -run "TestModule/TestSSHAuthSockPathHandling" -v

    exit_code=${PIPESTATUS[0]}
    echo "Exit code: $exit_code" | tee -a "$log_file"
    echo "----------------------------------------" | tee -a "$log_file"

    if [ $exit_code -ne 0 ]; then
        echo "Test failed with exit code $exit_code. Stopping the loop." | tee -a "$log_file"
        exit $exit_code
    fi

    echo "" | tee -a "$log_file"
done

echo "All iterations completed successfully." | tee -a "$log_file"

After a few iterations / isolations on my side, it seems that the root cause is the fact that the tests do run in parallel from the SAME client. Moving the client inside each of the test running in parallel does remove the flake:
func (ModuleSuite) TestSSHAuthSockPathHandling(ctx context.Context, t *testctx.T) {
	repoURL := "git@gitlab.com:dagger-modules/private/test/more/dagger-test-modules-private.git"

	t.Run("SSH auth with home expansion and symlink", func(ctx context.Context, t *testctx.T) {
		c := connect(ctx, t)
		mountedSocket, cleanup := mountedPrivateRepoSocket(c, t)
		defer cleanup()
})

	t.Run("SSH auth from different relative paths", func(ctx context.Context, t *testctx.T) {
		c := connect(ctx, t)
		mountedSocket, cleanup := mountedPrivateRepoSocket(c, t)
		defer cleanup()
})

A bit confused on the implications of that statement


Full Path

I am on the latest version.
Right now the images are being uploaded as following:

Could you please let me know how to upload images with

I also looked at your different issues and it seems that I have to edit script.blade.php or lfm.js bt I cannot find those files.
Thank you.

Do you set your domain in .env file? APP_URL=https://domain.com

Do you set your domain in .env file? APP_URL=https://domain.com

did that..still not working

We also need a way to configure domains for multi-tenant apps, root-relative file paths would be great to have.

is it anyone can find this solutions with tinymce full url path?

solutions ???

I have the same problem. Have you found a solution?

Still problem. Its possible to select by config setting to choose full path or relative?

Sorry for late reply.
Full urls are returned by default.
However, if you need relative urls, example code for getting relative urls, and explanations about why the full urls are returned can be found in https://github.com/UniSharp/laravel-filemanager/issues/1233 .


Iterating for the same 1st password !

It is working for me but the problem is it is trying only one password from the list the first password .
And when i put the real password of  my testing account in the list it checked for that password however it doesn't showed any success message .

same here

same

same here

same here

is there any solution for it?


Add cli support for running benchmark with custom dataset

I've added CLI support for running benchmark with custom dataset. Currently, I've only added and tested the support for pgvectorhnsw and pgvectorivfflat.

/assign @xuanyang-cn


Disable lock and group buttons when selected item is not CanvasItem

An idea of fix https://github.com/godotengine/godot/issues/88939 , should be merged after https://github.com/godotengine/godot/pull/89132 is merged.
The origin problem lies in the fact that ParallaxBackground is not a CanvasItem so the code did not do anything special to it, I guess if this need to be fixed, we can either hide the button or make it disable.
This pr disables lock and group buttons when there's not any selected CanvasItem.

So what about Node3Ds?

I've rebased the code onto master, and added back _update_lock_and_group_button in _draw_viewport, to support update the lock button immediately after click it instead of next selection_changed.

When you click non-CanvasItem node, the lock button opens:
https://github.com/godotengine/godot/assets/2223172/6e8f495a-b66e-446b-a2fb-8a9769258ee3
It's inconsistent with empty selection, which is closed, and also suggests that non-CanvasItems are "locked". Probably worth fixing.

Thanks!


[Bug] $Shape can be assigned to ?Field

type Field1 = {
  a1: string,
  b1: string
};

function f(field1?: $Shape<Field1>) {
  const foo: ?Field1 = field1; // This is unsound. Not every `$Shape<Field1>` is a `?Field1`
}

type Field2 = {|
  a2: string,
  b2: string
|};

function f(field2?: $Shape<Field2>) {
  // Can also happen with exact fields, but only after a `null | undefined` check
  if (field2) {
    const foo: Field2 = field2; // This is unsound. Not every truthy `$Shape<Field2>` is a `Field2`
  }
}

Repro
Flow version: 0.98.1 (and lower, even 0.59.x)
Expected behavior
Flow should print an error for the lines marked with // This is unsound, since not every $Shape<Field1> is a ?Field1 (e.g. { a1: '' } is a $Shape<Field1>, but not a ?Field1).
Actual behavior
No errors are thrown

Duplicate of #7566, #7316, #5702, #6039, #6796.
AFAIK this is an unsound "feature" and not a bug. Or at least that's how it has always worked, the other issues haven't really gained much traction, and there's quite a bit of code that depends on its current behaviour.
A safe alternative to $Shape would be something like
type Partial<T> = {...{...T}}

Also $Rest<T, {}>

Duplicate of #7316


A-2-3-4-5 is too strong !

If A-2-3-4-5 is possible, it will be evaluated as better straight then 2-3-4-5-6 or 3-4-5-6-7
It should not !

Done !


PhantomJS crashed during casperJS script

Which version of PhantomJS are you using? Tip: run phantomjs --version.
2.1.1

What steps will reproduce the problem?

Run my script

Wait

Which operating system are you using?
Linux Ubuntu Trusty

Did you use binary PhantomJS or did you compile it from source?
Bin

Please provide any additional information below.
I have a huge URL list (300 url). I use eachthen and thenopen to open all url and evaluate some data.
When i use my script with 1-10 url it is run well, but when i use 50+ url casperjs randomly stops (sometimes it can get through all url).
I can think to overflow or something similar error.

[info] [phantom] Step anonymous 538/5213: done in 358139ms.
PhantomJS has crashed. Please read the bug reporting guide at
<http://phantomjs.org/bug-reporting.html> and file a bug report.
Segmentation fault (core dumped)

I'm trying to release some resources (delete screenshots, url list store and read from file not from variable etc..), it can run more times but it still crashes.
How can i see full bugreport?

Please follow the link in the error message to output the crash logs: http://phantomjs.org/bug-reporting.html
How many URLs are you loading at the same time? How long are you waiting after each URL to load a new one?


zoom: updated version of zoom on x86_64-linux to <IP_ADDRESS>40

Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I wrote this patch that updates to <IP_ADDRESS>40 and adds Linux screen sharing support on wayland. Should I make another PR for it or you want to cherry-pick?
diff --git a/pkgs/applications/networking/instant-messengers/zoom-us/default.nix b/pkgs/applications/networking/instant-messengers/zoom-us/default.nix
index 65c7942b5b3..1d73939b287 100644
--- a/pkgs/applications/networking/instant-messengers/zoom-us/default.nix
+++ b/pkgs/applications/networking/instant-messengers/zoom-us/default.nix
@@ -1,6 +1,7 @@
 { stdenv
 , lib
 , fetchurl
+, pipewire
 , makeWrapper
 , xar
 , cpio
@@ -46,7 +47,7 @@ let
   version = {
     aarch64-darwin = "<IP_ADDRESS>23";
     x86_64-linux = "<IP_ADDRESS>23";
-    x86_64-linux = "<IP_ADDRESS>45";
+    x86_64-linux = "<IP_ADDRESS>40";
    }.${system} or throwSystem;

   srcs = {
@@ -60,7 +61,7 @@ let
     };
     x86_64-linux = fetchurl {
       url = "https://zoom.us/client/${version}/zoom_x86_64.pkg.tar.xz";
-      sha256 = "9gspydrGaEjzAM0nK1u0XNm07HTupJ2wnPxCFWy+Nts=";
+      sha256 = "sha256-ruw6ZKZo4spY9H8yQmMYKJKRi0ZNXf1+BlhLqdPazIw=";
     };
   };

@@ -76,6 +77,7 @@ let
     expat
     libdrm
     libGL
+    pipewire
     fontconfig
     freetype
     gtk3

I wrote this patch that updates to <IP_ADDRESS>40 and adds Linux screen sharing support on wayland. Should I make another PR for it or you want to cherry-pick?
diff --git a/pkgs/applications/networking/instant-messengers/zoom-us/default.nix b/pkgs/applications/networking/instant-messengers/zoom-us/default.nix
index 65c7942b5b3..1d73939b287 100644
--- a/pkgs/applications/networking/instant-messengers/zoom-us/default.nix
+++ b/pkgs/applications/networking/instant-messengers/zoom-us/default.nix
@@ -1,6 +1,7 @@
 { stdenv
 , lib
 , fetchurl
+, pipewire
 , makeWrapper
 , xar
 , cpio
@@ -46,7 +47,7 @@ let
   version = {
     aarch64-darwin = "<IP_ADDRESS>23";
     x86_64-linux = "<IP_ADDRESS>23";
-    x86_64-linux = "<IP_ADDRESS>45";
+    x86_64-linux = "<IP_ADDRESS>40";
    }.${system} or throwSystem;

   srcs = {
@@ -60,7 +61,7 @@ let
     };
     x86_64-linux = fetchurl {
       url = "https://zoom.us/client/${version}/zoom_x86_64.pkg.tar.xz";
-      sha256 = "9gspydrGaEjzAM0nK1u0XNm07HTupJ2wnPxCFWy+Nts=";
+      sha256 = "sha256-ruw6ZKZo4spY9H8yQmMYKJKRi0ZNXf1+BlhLqdPazIw=";
     };
   };

@@ -76,6 +77,7 @@ let
     expat
     libdrm
     libGL
+    pipewire
     fontconfig
     freetype
     gtk3

Either is fine by me, maybe it is just simpler for you to make a PR? Then I can close this one. Does it already work for you btw? It still gives me an error about os support, since it reads the os name from /etc/os-release

It works for me if I explicitely edit ~/.config/zoomus.conf to say enableWaylandShare=true

Can you do screen sharing on say, https://meet.webconf.ch/ ?

Can you do screen sharing on say, https://meet.webconf.ch/ ?

Screen sharing works fine if I use zoom on XWayland or in the browser. The issue with zoom wayland at this moment for me is that it still complains about the os. It is as if it does not honor the ~/.config/zoomus.conf

It may very well* make a difference. I would try setting
XDG_CURRENT_DESKTOP="GNOME" and see if that's better.
*: https://github.com/flathub/us.zoom.Zoom/blob/master/zoom.sh#L21
On Thu, Jun 23 2022 at 02:15:21 -07:00:00, Yuri A. Martinez Falcão
@.***> wrote:

Can you do screen sharing on say, https://meet.webconf.ch/ ?

Screen sharing works fine if I use zoom on XWayland or in the
browser. The issue with zoom wayland at this moment for me is that
it still complains about the os. It is as if it does not honor the
~/.config/zoomus.conf

It might be good to say that I'm on sway, not on Gnome, do you think
that it might make a difference?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID:
@.***>

It may very well* make a difference. I would try setting XDG_CURRENT_DESKTOP="GNOME" and see if that's better. : https://github.com/flathub/us.zoom.Zoom/blob/master/zoom.sh#L21
…
On Thu, Jun 23 2022 at 02:15:21 -07:00:00, Yuri A. Martinez Falcão @.> wrote: >> Can you do screen sharing on say, https://meet.webconf.ch/ ? >> > Screen sharing works fine if I use zoom on XWayland or in the > browser. The issue with zoom wayland at this moment for me is that > it still complains about the os. It is as if it does not honor the > ~/.config/zoomus.conf > It might be good to say that I'm on sway, not on Gnome, do you think that it might make a difference? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.*>

That was it! You sir just fixed my zoom screen sharing woes!

I'd like this PR to be merged with #178597 .

I just merged from that zoom darwin PR

Does anyone else experience a crash when trying to share their screen? Sharing my log here:
ZoomLauncher started.
Zoom path is: /nix/store/5aigasm0j0kzykwa35yqahinf3l46214-zoom-<IP_ADDRESS>40/opt/zoom
cmd line:
Start subprocess: /nix/store/5aigasm0j0kzykwa35yqahinf3l46214-zoom-<IP_ADDRESS>40/opt/zoom/zoom sucessfully,  process pid: 23987
No PulseAudio daemon running, or not running as session daemon.
                             Class      App      Lib Possible Culprit Flags
                resip::Connection      648      648
                      resip::Data       36       36
                 resip::DnsResult     1080     1080
                   resip::Headers        1        1
          resip::MsgHeaderScanner       40       40
                resip::SipMessage     5208     5208
         resip::TransportSelector      864      864
                     resip::Tuple      128      128
              resip::UdpTransport     1144     1144
          resip::GenericIPAddress       28       28

zoom started.
No PulseAudio daemon running, or not running as session daemon.
No PulseAudio daemon running, or not running as session daemon.
                                                        Class    Class        App    App        Lib   Possible Culprit FlagsLib
  Possible Culprit Flags
                            resip:: Connection  resip::Connection     648       648     648       648

                                         resip:: Data  resip::      36Data        36      36
      36
                              resip:: DnsResult  resip::    1080DnsResult      1080    1080
    1080
                                   resip:: Headersresip:: Headers       1         1       1         1

                  resip:: MsgHeaderScannerresip:: MsgHeaderScanner      40        40      40        40

                              resip:: SipMessageresip:: SipMessage    5208      5208    5208      5208

                resip:: TransportSelectorresip:: TransportSelector     864       864     864       864

                                        resip:: Tupleresip:: Tuple     128       128     128       128

                          resip:: UdpTransportresip:: UdpTransport    1144      1144    1144      1144

                 resip:: GenericIPAddress  resip::      28GenericIPAddress        28      28
      28

zoom started.
zoom started.
Client: Breakpad is using Single Client Mode! client fd = -1
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
QApplication: invalid style override passed, ignoring it.
    Available styles: Windows, Fusion
No PulseAudio daemon running, or not running as session daemon.
[CZPClientLogMgr::LogClientEnvironment] [MacAddr: DC:FB:48:7A:62:69][client: Linux][OS:  NixOS 22.11 Raccoon x64][Hardware: CPU Core:4 Frenquency:1.8 G Memory size:15823MB CPU Brand:Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz GPU Brand:][Req ID: ]
                             Class      App      Lib Possible Culprit Flags
                resip::Connection      648      648
                      resip::Data       36       36
                 resip::DnsResult     1080     1080
                   resip::Headers        1        1
          resip::MsgHeaderScanner       40       40
                resip::SipMessage     5208     5208
         resip::TransportSelector      864      864
                     resip::Tuple      128      128
              resip::UdpTransport     1144     1144
          resip::GenericIPAddress       28       28

Linux Client Version is 5.11.0 (3540)
QSG_RENDER_LOOP is
XDG_CURRENT_DESKTOP = GNOME;   GDMSESSION = gnome;   XDG_SESSION_TYPE = wayland
zoom started.
Graphics Card Info:: 00:02.0 VGA compatible controller: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] (rev 02)
Zoom package arch is 64bit, runing OS arch is x86_64
Using Wayland-EGL
qt.scenegraph.general: threaded render loop
qt.scenegraph.general: Using sg animation driver
qt.scenegraph.general: Animation Driver: using vsync: 16.67 ms
Using the 'xdg-shell' shell integration
xkbcommon: ERROR: couldn't find a Compose file for locale "en_IL.UTF-8" (mapped to "en_IL.UTF-8")
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.scenegraph.general: Using sg animation driver
qt.scenegraph.general: Animation Driver: using vsync: 16.67 ms
qt.scenegraph.general: texture atlas dimensions: 1024x512
qt.scenegraph.general: R/G/B/A Buffers:   8 8 8 8
qt.scenegraph.general: Depth Buffer:      24
qt.scenegraph.general: Stencil Buffer:    8
qt.scenegraph.general: Samples:           0
qt.scenegraph.general: GL_VENDOR:         Intel
qt.scenegraph.general: GL_RENDERER:       Mesa Intel(R) UHD Graphics 620 (WHL GT2)
qt.scenegraph.general: GL_VERSION:        4.6 (Compatibility Profile) Mesa 22.0.4
qt.scenegraph.general: GL_EXTENSIONS:    GL_3DFX_texture_compression_FXT1 GL_AMD_conservative_depth GL_AMD_depth_clamp_separate GL_AMD_draw_buffers_blend GL_AMD_multi_draw_indirect GL_AMD_performance_monitor GL_AMD_pinned_memory GL_AMD_query_buffer_object GL_AMD_seamless_cubemap_per_texture GL_AMD_shader_stencil_export GL_AMD_shader_trinary_minmax GL_AMD_texture_texture4 GL_AMD_vertex_shader_layer GL_AMD_vertex_shader_viewport_index GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_APPLE_packed_pixels GL_ARB_ES2_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility GL_ARB_ES3_compatibility GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_conservative_depth GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_elements_base_vertex GL_ARB_draw_indirect GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_fragment_shader_interlock GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_polygon_offset_clamp GL_ARB_post_depth_coverage GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_stencil_export GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shader_viewport_layer_array GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_spirv_extensions GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_filter_anisotropic GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_blend_equation_separate GL_ATI_draw_buffers GL_ATI_fragment_shader GL_ATI_separate_stencil GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_EXT_EGL_image_storage GL_EXT_EGL_sync GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_copy_texture GL_EXT_demote_to_helper_invocation GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_memory_object GL_EXT_memory_object_fd GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_semaphore GL_EXT_semaphore_fd GL_EXT_separate_specular_color GL_EXT_shader_framebuffer_fetch GL_EXT_shader_framebuffer_fetch_non_coherent GL_EXT_shader_integer_mix GL_EXT_shader_samples_identical GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_subtexture GL_EXT_texture GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod_bias GL_EXT_texture_object GL_EXT_texture_rectangle GL_EXT_texture_sRGB GL_EXT_texture_sRGB_R8 GL_EXT_texture_sRGB_decode GL_EXT_texture_shadow_lod GL_EXT_texture_shared_exponent GL_EXT_texture_snorm GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_IBM_multimode_draw_arrays GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_INGR_blend_func_separate GL_INTEL_blackhole_render GL_INTEL_performance_query GL_INTEL_shader_atomic_float_minmax GL_INTEL_shader_integer_functions2 GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent GL_KHR_context_flush_control GL_KHR_debug GL_KHR_no_error GL_KHR_parallel_shader_compile GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_KHR_texture_compression_astc_ldr GL_KHR_texture_compression_astc_sliced_3d GL_MESA_framebuffer_flip_y GL_MESA_pack_invert GL_MESA_shader_integer_functions GL_MESA_texture_signed_rgba GL_MESA_window_pos GL_NV_blend_square GL_NV_compute_shader_derivatives GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_clamp GL_NV_fog_distance GL_NV_fragment_shader_interlock GL_NV_half_float GL_NV_light_max_exponent GL_NV_packed_depth_stencil GL_NV_primitive_restart GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_env_combine4 GL_NV_texture_rectangle GL_OES_EGL_image GL_OES_read_format GL_S3_s3tc GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_SUN_multi_draw_arrays
qt.scenegraph.general: Max Texture Size: 16384
qt.scenegraph.general: Debug context:    false
AppIconMgr::systemDesktopName log Desktop Name: gnome
Error: Send error, 22 Invalid argument
Error: Send error, 22 Invalid argument
Error: Send error, 22 Invalid argument
Unsupported modifier, resource creation failed.
XXX: resource creation failed
qt.scenegraph.general: Using sg animation driver
qt.scenegraph.general: Animation Driver: using vsync: 16.67 ms
qt.scenegraph.general: texture atlas dimensions: 2048x1024
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.scenegraph.general: Using sg animation driver
qt.scenegraph.general: Animation Driver: using vsync: 16.67 ms
qt.scenegraph.general: texture atlas dimensions: 2048x1024
qt.scenegraph.general: Using sg animation driver
qt.scenegraph.general: Animation Driver: using vsync: 16.67 ms
qt.scenegraph.general: texture atlas dimensions: 512x512
Unsupported modifier, resource creation failed.
XXX: resource creation failed
qt.scenegraph.general: Using sg animation driver
qt.scenegraph.general: Animation Driver: using vsync: 16.67 ms
qt.scenegraph.general: texture atlas dimensions: 512x512
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.scenegraph.general: Using sg animation driver
qt.scenegraph.general: Animation Driver: using vsync: 16.67 ms
Unsupported modifier, resource creation failed.
XXX: resource creation failed
qt.scenegraph.general: texture atlas dimensions: 1024x1024
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
This plugin does not support setting window opacity
No PulseAudio daemon running, or not running as session daemon.
zoom was exited due to a handled signal: 7
ZoomLauncher exit.

re: crash, it sounds like you may be missing pulseaudio support. In
case it's not that I fear NixOS couldn't do much about it since it's
proprietary software.

re: crash, it sounds like you may be missing pulseaudio support.

I don't set pulseaudioSupport = false; when I call the derivation if that's what you mean. Do you take any action to enable pulseaudio support?

For the record, I don't think screen sharing has ever worked for me, so I don't vetoe this PR. I still wish to get screen sharing not crash it though.

@Maverickzero the Darwin release had a bug fix, could you merge again from whiteley:zoom.us-darwin-<IP_ADDRESS>23 please? Thanks!

Hi Whiteley, I just pulled again from your branch with the updates, thanks for the headsup!


Yum broken when RPM from this requirement with underscores.

Please never use underscores in python-packages names.
PEP-008 conatins

Python packages should also have short, all-lowercase names, although the use of underscores is discouraged.

We have a really problem. When our build system convert all dependencies to RPM (using FPM) yum is broken. We are can't use this package in our projects.

@mosquito thanks for spotting this, I didn't know that part of PEP8.
This is indeed contradict with PEP8 advices, but this is how (at least some) packages in aiohttp_* already named (e.g. aiohttp_admin, aiohttp_session).
@asvetlov we can raise discussion about renaming them or distributing both with underscore and hyphen versions (some of aiohttp packages indeed called with hyphen: aiohttp-riak, aiohttp-jrpc).
We are not only one who used underscore in packages names and underscores are disallowed in package names in RedHat based and Debian based distros, so FPM at least tries to replace underscores with hyphen: https://github.com/jordansissel/fpm/issues/65 , but looks like there are bugs in FPM with that: https://github.com/jordansissel/fpm/issues/1201 , https://github.com/jordansissel/fpm/issues/1016
Bottom line: at this point this is a bug of FPM (so in order to use aiohttp_cors with FPM you need to fix FPM), but also we should consider renaming aiohttp_* to aiohttp-* to line up with PEP8.

Actually you should see how PyPi and PIP works. When you try to fetch packages which contains underscores in names PYPI will return redirect.
$ curl -I 'https://pypi.python.org/simple/aiohttp_cors/'
HTTP/1.1 301 Moved Permanently
Location: /simple/aiohttp-cors
...

$ curl -I 'https://pypi.python.org/simple/aiohttp-cors/'
HTTP/1.1 200 OK
Server: nginx/1.10.1
Content-Type: text/html; charset=utf-8
Content-Length: 1864
Date: Thu, 20 Oct 2016 10:22:42 GMT
...

But PyPi XML-RPC is "underscore sensitive". And you can't find this by pip search aiohttp-cors
When I developed my PyPI server this caused some difficulties (have to search twice).

@mosquito if PyPI/pip/setptools make such conversions, does it mean that we can just rename packages on PyPI to have hyphen instead of underscore, and nothing will break?
Does it mean, that currently all aiohttp_cors users can specify in their dependencies that they require aiohttp-cors and it will still download aiohttp_cors and everything will work?

Let's rename the package -- looks like it is safe and backward compatible operation

Fixed by c34202e


License

hi @ananjev-a-v ,
how about license for this library?

hi @faliqulamin ,
Thanks for your interest. I've chosen a BSD 3-Clause for this project, I think that's enough.


Won't show Vencord plugin context menu item icons

On hover or right click on a message, the items that were added by a Vencord plugin doesn't have icons
https://github.com/TakosThings/Fluent-Discord/assets/80098945/3adc747b-24d2-46dc-a9b8-6a5935391411

I found a fix for this with Vencord's QuickCSS. I recommend using FontForge or similar to find the characters you need from the font this theme uses
Here's what I put:
html[lang^=en-].theme-dark .wrapper_ef319f .button_ef319f[aria-label="Hide Attachments"]::before {
  content: "\ed1a";
}
html[lang^=en-].theme-dark .wrapper_ef319f .button_ef319f[aria-label="Show Attachments"]::before {
  content: "\f78d";
}

html[lang^=en-].theme-dark .wrapper_ef319f .button_ef319f[aria-label="View Raw (Left Click) / Copy Raw (Right Click)"]::before {
  content: "\e943";
}

html[lang^=en-].theme-dark .wrapper_ef319f .button_ef319f[aria-label="Translate"]::before {
  content: "\e8c1";
}


Enhancement: Add a feature to render LaTeX-formatted equations

Contact Details
<EMAIL_ADDRESS>What features would you like to see added?
Could you add a feature to render LaTeX-formatted equations? The equations generated by ChatGPT are difficult to understand. Thanks!
More details
Could you add a feature to render LaTeX-formatted equations? The equations generated by ChatGPT are difficult to understand. Thanks!
Which components are impacted by your request?
UI
Pictures
No response
Code of Conduct

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

Sure, this should be easy. Can you give me some examples of prompts I can use for testing?


Add LM trainer

@drugilsberg thanks for the review. I have addressed the majority of the requested changes. Some comments: the LICENCE file is already there in the main from the initial commit and there is no need to be added again. Python 3.11 is not supported at this point, but this can be addressed with a newer PR.

@drugilsberg thanks for the review. I have addressed the majority of the requested changes. Some comments: the LICENCE file is already there in the main from the initial commit and there is no need to be added again. Python 3.11 is not supported at this point, but this can be addressed with a newer PR.

great, sorry for the overlook but from the changes it wasn't apparent.


jenssegers / date set globale to country setting

Hi,
where can i change the folllowing setting globaly ?
use Jenssegers\Date\Date;

Date::setLocale('nl'); <--

in the Netherlands we work with a 24H clock instead of AM and PM

The date strings can be changed in the admin panel -> localisation -> languages
search for time_format and you'll see options starting with php. - they are backend/admin, and some that are moment. - they are front end.
Moment formatting:
https://momentjs.com/docs/#/displaying/
PHP date formats:
https://www.php.net/manual/en/datetime.format.php

The date strings can be changed in the admin panel -> localisation -> languages
search for time_format and you'll see options starting with php. - they are backend/admin, and some that are moment. - they are front end.
Moment formatting:
https://momentjs.com/docs/#/displaying/
PHP date formats:
https://www.php.net/manual/en/datetime.format.php

Nice Ryan Thanks !

Nice Ryan Thanks !


Update notebooks to use VirtualiZarr

This PR updates the notebooks in the foundations and generating references sections to use VirtualiZarr, excluding the GRIB2 notebook which will require a PR to VirtualiZarr with a GRIB reader.

@norlandrhagen do you think we should update the basics and NetCDF/GeoTIFF notebooks now or wait until the remaining features are available in VirtualiZarr (GRIB, appending)?

Hmm, I'm open to either. Maybe we wait to update until those are in virtualizarr? We could also add a coming soon note or something?


Source maps offsets investigations

We should verify source maps are exactly lining up according to https://github.com/jspm/jspm-cli/issues/1104.
@crisptrutski any chance you still have a link to that really good source map comparison tool you found online?

I am seeing a related issue using coffeescript...it appears that the source mappings generated by traceur map to the transpiled js rather than the original source file. So post bundling the mappings reference the intermediate javascript and not the original file. Then those mappings are sent back in the bundle sourcemap.
I threw everything here including beginning, intermediate and final sourcemaps. app.bundle.js and app.bundle.js.map demonstrate the problem. Maybe it helps:
https://gist.github.com/CPWeaver/cca2638fffd215557530

I am seeing a related issue using coffeescript... when the transpiled js is passed into traceur, the output sourcemap appears to reference the transpiled code, NOT the original coffee despite passing an input source map to traceur. If you use the traceur output against its inline sourceContents then it maps properly but if you use the same mappings against the original source it doesn't line up. I threw all the files including a bundle and map which demonstrate the issue below; hope it helps.
https://gist.github.com/CPWeaver/cca2638fffd215557530

@CPWeaver if you're using a precompilation step to compile CoffeeScript and not a SystemJS plugin, then that is a separate issue is being tracked in https://github.com/systemjs/systemjs/issues/638 and https://github.com/systemjs/builder/issues/297.

You're right that It does look like #297, but I am using the systemjs plugin and calling System.input directly on .coffee. I see that systemjs does have the correct sourcemapping from coffee in load.metadata.sourceMap when it invokes Traceur. For what it's worth.

@CPWeaver ok that is an issue then - do the CoffeeScript source maps work for you in the browser?

@guybedford I have used https://github.com/sokra/source-map-visualization or  https://github.com/lydell/source-map-visualize which is a CLI extension for the same thing.

@frankwallis awesome thanks, yes that was the one!

I've been using the sourcemap-validator library, especially as the visual tool sometimes refuses to load source maps that are not valid (as per the jspm issue with minification). I also wrote a helper script to wrap the library into an executable script.
As far as https://github.com/jspm/jspm-cli/issues/1104 is concerned, I think there is definitely an issue that is not offset related but more related to names mappings. It seems that names from the Traceur-compiled source are making it into the final names list, which of course is wrong. Disabling mangling (but still using minify) seems to result in correct source maps.
The error is also reproduceable with Babel as transpiler, although the resulting source maps and names list is slightly different (slightly better IIRC).
IIRC (sorry it was a few weeks ago I last looked into this), the transpiler sourcemap is making it to the Uglify step, but I noticed the transpiler source map didn't contain any names. I don't know if that's expected behaviour (technically no name was rewritten), but it may be part of the issue? It also didn't contain any sourcesContent (which is expected in the absence of --source-map-contents, although there was also an odd bug with passing -m --inject --source-map-contents options).
Assuming the correct sourcemaps were passed to uglify with all the necessary information (mappings, and names or sourcesContent), it's also possibly a bug in uglify itself, although that's quite hard to debug.

As a note, I swear it used to work in prior versions of jspm, but I'm not 100% sure of it anymore..

A few more notes:
Dumping the output file+map of the transpile step (at which point the map validates fine) and passing those manually to the uglify2 CLI results in the same final output+map, which the names problem. So it seems to point at either a bug in uglify2 with that input source+map combination, or else the Traceur (and Babel) sourcemap is not complete enough for uglify2 to do a good job.
I also tried with --hires-source-maps, which seems to generate a more fine-grained source map (more mappings), but that still doesn't seem to help the final result.
For the record I'm using this trivial source as test case:
function hello(world) {
    var abcde = 'var';
    console.log(abcde);
    return abcde + 'x';
}

hello('you');

export default hello;

@guybedford Yes, I confirmed this morning that when the app is served unbundled, source mapping in the "!transpiled" files work correctly in the browser. When the app is bundled I see the line offsets.

Having probably similar issue with typescript. I run "jspm bundle-sfx lib/main .../app.min.js --minify"  - map file has "sources" with scripts ONLY from jspm_packages folder (basically all scripts from config. None of script from lib folder are included. Any workaround on this? Do i have to somehow describe lib in config file? Currently specifying only defaultExtension for that folder.

@kpomka try using the TypeScript plugin at https://github.com/frankwallis/plugin-typescript instead for TypeScript support.

@guybedford thanks a lot, that helped!

Does it mean it's fixed?

@mihcall I investigated :) it turns out Traceur is screwing up input source maps so the best strategy here is to move to Babel for internal transformations over Traceur. This work is tracking in https://github.com/systemjs/builder/issues/489.

Thanks! I experienced this: https://github.com/jspm/jspm-cli/issues/1104 with Babel though :( Not sure how this discussion ended, I couldn't find an error myself using some tools you guys were mentioning in the issue, had to disable source maps "for now"

This lines up with what I suspected but I was over my head looking at traceur source code. Thanks for looking into it and we will look forward to the babel switch. :+1:

Originally I was able to reproduce the issues with incorrect sourcemaps both with Traceur and Babel. Will have to try re-running those tests with latest version of those and JSPM to check whether anything has improved.

I still experience sourcemap offsets while using systemjs-builder and the systemjs babel plugin directly (just vanilla ES6, no preprocessing step or TypeScript involved). Could somebody please confirm that this is still a somewhat "general" issue of systemjs-builder?
@crisptrutski @guybedford said you know an powerful sourcemap analyzing tool ... any chances you could tell us where to find it? :)

@gcnm-pgeil the source map testing tool is https://github.com/sokra/source-map-visualization. It works well with the --source-map-contents and --inline-source-maps options in jspm. I'm currently getting a substr of undefined error when using it though which may be the first hurdle in the jspm source map output! See also https://github.com/jspm/jspm-cli/issues/1729.


Update running-coreos/platforms/vmware/index.md

[Documentation update]
The old link (https://developercenter.vmware.com/tool/ovf/3.5.0) pointed to a 404, changing to the tool's generic homepage (https://developercenter.vmware.com/tool/ovf/) which looks exactly the same as the previous link, but doesn't need to be updated every time VMWare pushs an update.

Thanks!


Error when app start

[ERROR] FATAL UNHANDLED EXCEPTION: Java.Lang.NullPointerException: Attempt to invoke virtual method 'void android.support.v7.widget.ContentFrameLayout.setId(int)' on a null object reference
at (wrapper dynamic-method) System.Object:a510dffd-64d3-4452-9492-7a3ba8518cd7 (intptr,intptr,intptr)
End of managed Java.Lang.NullPointerException stack trace ---
java.lang.NullPointerException: Attempt to invoke virtual method 'void android.support.v7.widget.ContentFrameLayout.setId(int)' on a null object reference

https://github.com/jamesmontemagno/MediaPlugin/issues/226
Fixed my issue.
Thanks

#226
Fixed my issue.
Thanks

@manonaga2188 what was the issue and how did you fix that?

#226
Fixed my issue.
Thanks

@manonaga2188 what was the issue and how did you fix that?

"delete bin and obj folders on Android project and rebuild it"
https://github.com/jamesmontemagno/MediaPlugin/issues/226#issuecomment-298005958

#226
fixed issue;
I moved file_paths to LayOut folder; and issue fixed


Register x.part-of.my.id

Requirements

[x] You have completed your website.
[x] The website is reachable.
[x] The CNAME record doesn't contain https:// or /.
[x] There is sufficient information at the owner field.

Description

Link to Website

x.part-of.my.id

I don't think we can merge this PR since we are not in the PSL (Public Suffix List) and if we merge this PR for you, people in the future might not be able to connect to it and then the list goes on. Ita better to get a different domain if you want to use Vercel.


Tkinter is an unnanounced but required dependency

brownie Version: 1.1.0
Python Version: 3.7.5
OS: linux

What was wrong?
$ brownie init
Traceback (most recent call last):
  File "/home/bryant/.pyenv/versions/plasma-cash/bin/brownie", line 5, in <module>
    from brownie._cli.__main__ import main
  File "/home/bryant/.pyenv/versions/3.7.5/envs/plasma-cash/lib/python3.7/site-packages/brownie/__init__.py", line 4, in <module>
    from brownie._gui import Gui
  File "/home/bryant/.pyenv/versions/3.7.5/envs/plasma-cash/lib/python3.7/site-packages/brownie/_gui/__init__.py", line 3, in <module>
    from .root import Root as Gui  # noqa: F401
  File "/home/bryant/.pyenv/versions/3.7.5/envs/plasma-cash/lib/python3.7/site-packages/brownie/_gui/root.py", line 4, in <module>
    import tkinter as tk
  File "/home/bryant/.pyenv/versions/3.7.5/lib/python3.7/tkinter/__init__.py", line 36, in <module>
    import _tkinter # If this fails your Python may not be configured for Tk
ModuleNotFoundError: No module named '_tkinter'

How can it be fixed?
This should be an optional feature. If detected, then the coverage system GUI should be available. If not, either disable it entirely or write to files/terminal for your viewing pleasure.

According to https://github.com/pyenv/pyenv/issues/94#issuecomment-31371552, just install tk-dev before compiling Python to get access to this missing package.

Thanks for letting me know!  I like the idea of only installing it if tkinter is detected.  Once https://github.com/iamdefinitelyahuman/brownie/issues/230 is implemented the GUI can become a sort of first-class plugin that's installed by default if the dependencies are there.

This one finally got things working for me, just leaving it here for reference.


ML node

Thank you for this excellent example, I have successfully used it to set up similarity search.
I am wondering how the pre-trained model in elasticsearch is utilized. I have an ML node in elastic cloud and I have imported the pre-trained model but I am unclear on if those things are necessary. I am already using sentence-transformers to extract image embeddings in my application - how is the model loaded into elasticsearch used?
If I can get rid of the ML node in elastic cloud, I can substantially reduce cost.

Hello @threewordphrase !
Thanks for your feedback. I am glad to see that you were able to successfully deploy the example.

how is the model loaded into elasticsearch used?

When you create a vector (image embedding) from your image, store it in Elasticsearch in an index; then you have your vector database of image embeddings.
When searching your images based on the generated vectors, you need a vector to search against them. In the case of this application, the "searching" vector is generated from the text query from the search bar. The vectorization of the text utilizes the NLP model loaded in Elasticsearch. This model can convert the search text to a vector and then use that vector as a "query term" for the vector database.
So, the model in Elasticsearch is used to convert the text to a vector for your search against images.
Having the model in Elasticsearch is very convenient because you do not need to utilize other infrastructure, and it uses Elasticsearch API for the _inference.
Note that the model to create image embeddings (from binary data to vector) and the model to generate vectors from your search text must be compatible (dimensions, type, learning content)
I hope this helps and if you want, you can read more on the topic in a miniseries I wrote. There are 3 parts.
1, 2 and 3
Feel free to let me know if you have more questions.

I am closing this one for now. If you have more questions, feel free to reopen.
Thanks


Maven central

Could you deploy your artifact to Maven central please.
It would be much more easier to use it, because u don't need to add additional repositories to your project.
Thank you.

Sorry, I won't do that. Deploying to maven central is a pain, that's why so many people are using JitPack by now.

Hi @ralfstuckert!
Nowadays JReleaser eases some of the pain related to Maven Central publication. If you would accepts some PRs, I'll gladly help out.


relates to #1920: update C* and DSE versions in the docker compose

What this PR does:
Updates docker compose in the v2.0.0 after #1926.
Which issue(s) this PR fixes:
Relates to #1920

Thank you @ivansenic -- I forgot this part wrt v2, C*/DSE updates.


documentDescribes property should be replaced with a DESCRIBES property

The SPDX 2.2 Ontology includes a property documentDescribes which has been replaced with the a DESCRIBES relationship between the Document and the Package in the 2.0 spec.
The upgrade facility should replace any documentDescribes property with the preferred relationship approach.

Based on issues in the SPDX spec - it looks like retaining the documentDescribes is a preferred approach.


Exit early when running on Windows + unsupported language

This introduces env var TRAVIS_WINDOWS_LANGS, which is a comma-separated list of language names that are allowed to run on Windows.

Tested: https://staging.travis-ci.com/BanzaiMan/com_testing/builds/232020


Incomplete Anomaly Score Log: Missing Value for 'msg' Field with Rule ID 980170

1. The problem I'm having:

Hello,
We don't have the value of the msg field in the anomaly score log wich have the rule id 980170.
this was already reported and fix in #684
2. Expected behavior :
We should have a log like this one.
{
  "level": "error",
  "ts":<PHONE_NUMBER>.7382822,
  "logger": "http.handlers.waf",
  "msg": "[client \"<IP_ADDRESS>\"] Coraza: Warning. Anomaly Scores: (Inbound Scores: blocking=25, detection=25, per_pl=15-0-0-10, threshold=1000) - (Outbound Scores: blocking=0, detection=0, per_pl=0-0-0-0, threshold=1000) - (SQLI=0, XSS=0, RFI=0, LFI= [file \"/ruleset/coreruleset/rules/RESPONSE-980-CORRELATION.conf\"] [line \"11046\"] [id \"980170\"] [rev \"\"] [msg \"Anomaly Scores: (Inbound Scores: blocking=25, detection=25, per_pl=15-0-0-10, threshold=1000) - (Outbound Scores: blocking=0, detection=0, per_pl=0-0-0-0, threshold=1000) - (SQLI=0, XSS=0, RFI=0, LFI=\"] [data \"\"] [severity \"emergency\"] [ver \"OWASP_CRS/4.0.0-rc1\"] [maturity \"0\"] [accuracy \"0\"] [tag \"reporting\"] [hostname \"\"] [uri \"/?foo=/etc/passwd&bar=/bin/sh\"] [unique_id \"DyldtRcMRMBWPrdM\"]\n"
}

3. Actual behavior - Error messages and/or full log output:

Actually the rule 980170 is trigerred but we have no msg.
{
    "level": "error",
    "ts":<PHONE_NUMBER>.5746813,
    "logger": "http.handlers.waf",
    "msg": "[client \"<IP_ADDRESS>\"] Coraza: Warning. Inbound Anomaly Score Exceeded (Total Score: 25) [file \"/ruleset/coreruleset/rules/REQUEST-949-BLOCKING-EVALUATION.conf\"] [line \"0\"] [id \"949110\"] [rev \"\"] [msg \"Inbound Anomaly Score Exceeded (Total Score: 25)\"] [data \"\"] [severity \"emergency\"] [ver \"OWASP_CRS/4.0.0-rc2\"] [maturity \"0\"] [accuracy \"0\"] [tag \"anomaly-evaluation\"] [hostname \"\"] [uri \"/?foo=/etc/passwd&bar=/bin/sh\"] [unique_id \"pzIBCQEecpuPBGDi\"]\n"
}

{
    "level": "error",
    "ts":<PHONE_NUMBER>.5751467,
    "logger": "http.handlers.waf",
    "msg": "[client \"<IP_ADDRESS>\"] Coraza: Warning.  [file \"/ruleset/coreruleset/rules/RESPONSE-980-CORRELATION.conf\"] [line \"0\"] [id \"980170\"] [rev \"\"] [msg \"\"] [data \"\"] [severity \"emergency\"] [ver \"OWASP_CRS/4.0.0-rc2\"] [maturity \"0\"] [accuracy \"0\"] [tag \"reporting\"] [hostname \"\"] [uri \"/?foo=/etc/passwd&bar=/bin/sh\"] [unique_id \"pzIBCQEecpuPBGDi\"]\n"
}

4. Caddy version:

v2.7.6 h1:w0NymbG2m9PcvKWsrXO6EEkY9Ru4FJK8uQbYcev1p3A=

5. How I installed and ran Caddy and Coraza:

a. System environment:

I'm using a raspeberrypi 4B
Linux srvone4all 5.4.0-1100-raspi #112-Ubuntu SMP PREEMPT Fri Nov 24 15:35:17 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

Docker version
Docker version 26.0.0, build 2ae903e

b.  My complete Caddy config:

{
	order coraza_waf first
	persist_config off
	log {
		level INFO
		output file /var/log/caddy/caddy.log
	}
	servers {
		timeouts {
			idle 10s
			read_body 1m
			read_header 10s
		}
		max_header_size 4KB
	}
}

# Default server block that will respond with a "Not found" message for all requests to port 443
:443 {
	log
	respond "Not found" 404
}
# Default server block that will respond with a "Not found" message for all requests to port 80
:80 {
	log
	respond "Not found" 404
}

{$DOMAIN} {
	log
	coraza_waf {
		directives `
		Include /ruleset/coraza.conf
		Include /ruleset/vaultwarden/crs-setup.conf
		Include /ruleset/coreruleset/rules/*.conf
		`
	}

	request_body {
		max_size 100MB
	}

	# Handle vaultwarden sends with file upload.
	@not-api not path /api/sends/*
	request_body @not-api {
		max_size 100KB
	}

	encode gzip
	tls {
			dns gandi {$GANDI_API_KEY}
	}

	# By default, Vaultwarden actually handle a lot Web Security Header and caching.
	header {
		Strict-Transport-Security "max-age=15768000;"
		Referrer-Policy "no-referrer"
		X-Robots-Tag "none"
	}

	@insecureadmin {
		not remote_ip <IP_ADDRESS>/24
		path /admin*
	}
	redir @insecureadmin /
	reverse_proxy vaultwarden:60278 {
		header_up X-Real-IP {remote_host}
	}
}

e. CRS version:
from crs-setup.conf: tx.crs_setup_version=400

Hey, apologies, I just took a look at this now. I'm quite confident you are facing the point 3. written in the PR you mentioned:

Just like phases 3 and phases 4, also for phase 5 I had to explicitly set SecDefaultAction "phase:5,log,auditlog,pass" (Related to https://github.com/corazawaf/coraza/issues/494). Rule 980170 does not have explicit log, therefore Coraza does not log its message without setting the default action also for this phase.

So something like the following should do the trick 🤞
	coraza_waf {
		directives `
		Include /ruleset/coraza.conf
		Include /ruleset/vaultwarden/crs-setup.conf
		SecDefaultAction "phase:5,log,auditlog,pass"
		Include /ruleset/coreruleset/rules/*.conf
		`
	}

Hello, sorry for the late reply, There is no more the issue :+1:
{
    "level": "error",
    "ts":<PHONE_NUMBER>.9216244,
    "logger": "http.handlers.waf",
    "msg": "[client \"<IP_ADDRESS>\"] Coraza: Access denied (phase 5). Anomaly Scores: (Inbound Scores: blocking=3, detection=3, per_pl=0-0-3-0, threshold=1000) - (Outbound Scores: blocking=0, detection=0, per_pl=0-0-0-0, threshold=1000) - (SQLI=3, XSS=0, RFI=0, LFI=0, R [file \"/ruleset/coreruleset/rules/RESPONSE-980-CORRELATION.conf\"]
        [line \"13679\"]
        [id \"980170\"]
        [rev \"\"]
        [msg \"Anomaly Scores: (Inbound Scores: blocking=3, detection=3, per_pl=0-0-3-0, threshold=1000) - (Outbound Scores: blocking=0, detection=0, per_pl=0-0-0-0, threshold=1000) - (SQLI=3, XSS=0, RFI=0, LFI=0, R\"]
        [data \"\"]
        [severity \"emergency\"]
        [ver \"OWASP_CRS/4.3.0\"]
        [maturity \"0\"]
        [accuracy \"0\"]
        [tag \"reporting\"]
        [tag \"OWASP_CRS\"]
        [hostname \"\"]
        [uri \"/notifications/hub?access_token=eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.eyJuYmYiOjE3MjYxNjk2OTksImV4cCI6MTcyNjE3Njg5OSwiaXNzIjoiaHR0cHM6Ly92YXVsdHdhcmRlbi5vbmU0YWxsLmljdXxsb2dpbiIsInN1YiI6IjYxZGRiOGQ4LWE1MDgtNGM5My1iZmUwLTAzZjE2MzU4OGNkMyIsInByZW1pdW0iOnRydWUsIm5hbWUiOiJCYXJub3V4IiwiZW1haWwiOiJiYmFybm91eEBnbWFpbC5jb20iLCJlbWFpbF92ZXJpZmllZCI6dHJ1ZSwic3N0YW1wIjoiYjM0NGMxODMtNjUyYS00MjZhLThhYjAtYTVhODgwMWZiZTY5IiwiZGV2aWNlIjoiNzVhOWMxNTctMjg1OS00YTE3LWExMzctNDBjNDlmODFhMGQ1Iiwic2NvcGUiOlsiYXBpIiwib2ZmbGluZV9hY2Nlc3MiXSwiYW1yIjpbIkFwcGxpY2F0aW9uIl19.a8QDqEPyvGvHPeiAlp4dNdfC2hMQHaP2tpeQ_vqCUCFYaL0_6tVhFj_T6UU7B_eyl7-IoLLtHKLVXi7UelSXJcq-RwN2Ad-PTBbKO9DcvJuLKMaN0u1NR3HxTeeW1u9llpgQyIDq9XxZ13mYVGjvOSiXGEryOMCXXIyu9p2H_Tj6u8S9yOhZf1d1eXOFq82cSGUBgKiMXZsItyoMzgRmjy9y9ULxODEZicO0_66K52uVjvuwtUFRI6PbId54KMtmdvAt-jC-VO1vLKNUjCwWdjWl4oXFML8HSFxFKvm1ZCktOj-l1d2ZFzWMDdKH80_GI_-Qsk7uIIHSK166l_rD_w\"]
        [unique_id \"clpuhxOGpwZLPcST\"]\n"
}


No maps

also makes it slightly easier to add ratcheting validation for these.

Still seeing 4 expected files with missing new lines at the end, if you care about that (I think it can lead to weird diffs in GitHub if not fixed and the file is edited in the future)

/lgtm


[FEAT]: Implement optional peerDependencies

Hi everyone,
I would like to implement optional peer dependencies to allow some hooks to have dependencies without having to install it globally. By example:

useDebounceCallback requires lodash.debounce
useCookie may requires js-cookie
Etc

If I only use useUnmount, by example,, I don't want to have either lodash.debounce or js-cookie in my bundle.
I tried to implement this in #443 using:
 "peerDependencies": {
     "lodash.debounce": "^4",
   },
   "peerDependenciesMeta": {
     "lodash.debounce": {
       "optional": true
     }
   },

But it does not work as expected as it requires lodash.debounce anyway, even if you're not importing useDebounce*** (like mentioned here: #458, #452, #453).
If someone knows how to fix this, it's more than welcome!

Tree-shaking looks to do the work... but bundlephobia tells us another story (2.12.0 added lodash.debounce)
<EMAIL_ADDRESS>

So, I looked into this matter and found some interesting behaviours.
Most modern bundlers like vite, webpack/turbopack bundles the entire package before hand to use in development.
There is a setting is Next.js/Webpack that can be used to stop this and import part of code during development but that is out of scope as the user need to manually change some config. And there is no simillar setting in vite.
 But the overhead of that overhead would be greater that having it as the way it is.
I don't know how bundlephobia works, but I am sure that all modern bundlers can treeshake every last byte of code that is not needed.
So if we even have one dependency per hook, it would be just a development overhead and no extra code would be present in the production build. So I think we can just keep the package as it is and don't bother about this.
If you have other concerns, I would be happy to help.

I also think that we can trust modern bundlers. Thanks for your work 👍


Add code review guidelines for changing running infrastructure

Writing and reviewing terraform code has different challenges than
reviewing other kinds of code. This is a draft attempt at
codifying how code review and merges work with terraform in our
repo, so we can make changes safely and quickly
closes https://github.com/2i2c-org/team-compass/issues/213

I requested reviews from some more team members, since my push changes and updates the wording a little bit. It would be good if at least one person could give this a 👍 and make sure that we haven't missed anything important.
Also I can't request a review from @yuvipanda since he's the author, but I would love if he could confirm that this PR still looks good to him w/ my changes :-)

many thanks for the review @consideRatio - changes accepted!
for others - let's leave this open for another 48 hours. If somebody else approves then I think we can just merge it in unless somebody objects.

LGTM

Not sure about the CI failure but content LGTM...

OK - we've got a few approves, and CI is now happy, and we've given it several days, so I'm gonna merge this one in! Thanks for all the feedback everybody :-)


Fail the response on exception in case of AudioPlayer request

Fixing #135

Coverage increased (+0.03%) to 98.371% when pulling 8ba63d9baf35c7cbe53015a729ee33554558b39c on fremail:fix-135 into 6bf28a8862c2e5f5f81188bb8bd33f9771960ffc on alexa-js:master.

Coverage increased (+0.03%) to 98.371% when pulling 8e377767d342c46829ff06bfd530f2d9dc9cbe3e on fremail:fix-135 into 6bf28a8862c2e5f5f81188bb8bd33f9771960ffc on alexa-js:master.

Coverage increased (+0.03%) to 98.371% when pulling 8e377767d342c46829ff06bfd530f2d9dc9cbe3e on fremail:fix-135 into 6bf28a8862c2e5f5f81188bb8bd33f9771960ffc on alexa-js:master.

Coverage increased (+0.03%) to 98.371% when pulling 8e377767d342c46829ff06bfd530f2d9dc9cbe3e on fremail:fix-135 into 6bf28a8862c2e5f5f81188bb8bd33f9771960ffc on alexa-js:master.

Coverage increased (+0.03%) to 98.371% when pulling 8e377767d342c46829ff06bfd530f2d9dc9cbe3e on fremail:fix-135 into 6bf28a8862c2e5f5f81188bb8bd33f9771960ffc on alexa-js:master.

Coverage increased (+0.03%) to 98.371% when pulling 8e377767d342c46829ff06bfd530f2d9dc9cbe3e on fremail:fix-135 into 6bf28a8862c2e5f5f81188bb8bd33f9771960ffc on alexa-js:master.

Coverage increased (+0.03%) to 98.371% when pulling 8e377767d342c46829ff06bfd530f2d9dc9cbe3e on fremail:fix-135 into 6bf28a8862c2e5f5f81188bb8bd33f9771960ffc on alexa-js:master.

Coverage increased (+0.03%) to 98.371% when pulling 8e377767d342c46829ff06bfd530f2d9dc9cbe3e on fremail:fix-135 into 6bf28a8862c2e5f5f81188bb8bd33f9771960ffc on alexa-js:master.

Merged, thanks.


WIP: Use dynamic symbol resolution for libmpi_caf on macOS

I'd like to get the CI system back up to parity with the old Travis-CI system. If I have time I'll add this to this PR, otherwise I'll change this from a draft to a real PR and just commit what's here.
Unfortunately mpi_caf.c now calls into libgfortran for the random seed
functionality.
It would be nice to avoid this if possible, but it's stateful so I
doubt that it would be possible.
Any code that links to the library should be Fortran code and/or pull in libgfortran.

coverage on master

Summary of changes
On macOS link the caf_mpi shared dylib so that symbols from libgfortran that are unresolved when building the library can be dynamically resolved at runtime (or when the executable is linked, perhaps?).
Rationale for changes
Recent changes broke OpenCoarrays on macOS. These changes were made to handle RNG seeding behavior and support make calls directly into libgfortran. Since this is stateful I doubt there is any way to avoid this, but if there is we should consider it. By default, macOS doesn't like unresolved symbols when creating shared/dynamic .dylib libraries, but you can tell the macOS linker to ignore undefined symbols and resolve them dynamically (at runtime or link time of the executable I presume). On linux the linker doesn't seem to care about creating shared libraries with undefined symbols which is why this issue didn't affect linux.
Additional info and certifications
This pull request (PR) is a:

[X] Bug fix
[ ] Feature addition
[ ] Other, Please describe:

I certify that

[X] I certify that:

I have reviewed and followed the contributing guidelines
I will wait at least 24 hours before self-approving the PR to give another
OpenCoarrays developer a chance to review my proposed code
I have not introduced errant white space (no trailing white space or white space errors may
be introduced)
I have added an explanation of what these changes do and why they should be included
I have checked to ensure there aren't other open Pull Requests for the same change
I have you written new tests for these changes
I have successfully tested these changes locally
I have commented any non-trivial, non-obvious code changes
The commits are logically atomic, self consistent and coherent
The commit messages follow best practices
Test coverage is maintained or increased after this is merged

Code coverage data

I don't know what else could be done, besides replicating the code from the gfortran library and thus creating a maintenance nightmare. So when this works, go for it!

Yes, I completely agree. Because it's stateful I don't think there's any other option.
It seems like there are a few small functions copied over from the single image implementation in libgfortran--I wonder if we should remove those, declare extern interfaces and pick them up from libgfortran so we're not duplicating and maintaining that code... Maybe a discussion for another time...


Point Broadcasting Redis to Event Machine Redis

This one took me a while to figure out why it was posting to the front end. It seems that calling Redis by itself doesn't call the callback set in streams and instead needs the EM connection.
1.) Switch to EM Redis Instance already established in ActionCable::Server::Base
2.) Put in a catch in case EM isn't started yet

Event Machine Redis not support sentinel connections - not scalability.
https://github.com/rails/actioncable/issues/99

https://github.com/livehelpnow/em-hiredis-sentinel
@badlamer Perhaps this gem could be merged into AC, or someone could PR it into em-hiredis?

@rushingfitness AC not working with this gem. Broadcasting better done through a redis-rb client.

Well if I go with the master branch, broadcasting doesn't even work at all with the redis-rb client.


create an option in core/merge_new_data to ignore invalid keys

Currently, merge_new_data(new_dataset) ignores keys that are in new_dataset but not in the existing self.dataset. We can make this optional and add those keys to self.dataset as new entries if a new argument 'ignore_invalid_keys=False'? + need to add more test cases for this

closed by #7


State variables.

Hello. As far as I understand, state is structured in some kind of substates. For example, in sample application there is async  HomePage reducer, which adds home  variable to state (in addition to global and route). In this  home  object only username is stored. When you are loading repositories,  you should load data and show spinner while loading (setting state.global.loading variable to true).
I understand, that loading variable should be global for whole application. Because of it, you need to get access in one reducer to both loading and userData.repositories variables . That is why you handle  LOAD_REPOS action on application level (in App/reducer not in HomePage/reducer). And that is why you have to keep HomePage specific info ( userData.repositories variable ) in state.global, not in state.home. Am I right?
If I am right, let us imagine, that I have some BlogPage container (generated by your generator), which adds  blogPage section in state. I need to retrieve list of blogs from API and show spinner while I am loading it. For that purpose I need something like this:
function blogPageReducer(state = initialState, action) {
  switch (action.type) {
    case LOAD_BLOGS:
          return  state.set('loading', true).
            setIn(['blogData'],['blogs'],false);
    case BLOGS_LOADED:
          return state.setIn(['blogData', 'blogs'], action.blogs)
                      .set('loading', false);
    default:
      return state;
  }
}

But as I understand, I can not do this, because I do not know, how to get access to state.global.loading variable from 'BlogPage/reducer'. Only  blogPage object is passed in reducer function. That is why I also need to handle LOAD_BLOGS in App/reducer and add my blogData object (with list of blogs) in state.global object. Is it normal? How can I get access to state.global.loading from 'BlogPage/reducer'?

I've been fiddling around with this too...was able to get access to state values via the store e.g.
store.getState().get('global').get('currentUser') // returns false by default, as per app's initial state
Not sure if this is best practice (I'm sure someone out there can tell us). So in your case if store isn't available, just import it.

@kunal-mandalia we don't have store from BlogPage/reducer? How can I get store object from BlogPage/reducer?

The missing piece here is that with Redux, you can react to an action with multiple reducers.
 The same goes for the BLOGS_LOADED action.
Hope that answers the question, let me know if you have any more!

Thank you.  It answers the question.  But you hold your repositories array in global variable of state?  For simplicity?

Yes, mostly for simplicity since this is a tiny example app!

Thank you Max.  Your template is cool.  I am. Net and Asp. Net developer,  who decided to learn something new,  and your template is awesome starting point

Thanks, great to hear! Let me know how you get along!

It is is rather unusual for me.  All this node and especially react stuff is some kind of chaos for me,  after structured and rather static .Net world.  Also I am confused with the leak of normal debug (like we do it in  Visual Studio).  But this is funny.  Maybe someday (I believe in it)  Asp.Net Core will become the best backend and with React will become a future of Web


Fix insertion/removal behavior

PR for issue #62

Looks like this just needs a small clippy fix?

I also squashed a few of the commits together

third time's the charm

woo!


Allow configure port for remote access

Hello.
Next scenario, I have elixir/phoenix app listen on http://localhost:4000 and dev server on http://localhost:4001
dev server running with --host <IP_ADDRESS> option allow get assets from remote machines in Lan Network
export default
  entry:
    app: ['./app.coffee', 'webpack-hot-middleware/client]

This work for app.js from any pc in network but return 404 in browser for /__webpack_hrm
It because GET to http://#{localhost or remote_ip}:4000 but http://#{localhost or remote_ip}:4001
Maybe add something like https://github.com/Fudoshiki/webpack-hot-middleware/commit/c784d8c8b79f7e5d05d1f986329fc72a6be6a22f or any othe solution

Solved
remote.coffee
host = 'http://' + window.location.hostname + ':4001'

__webpack_public_path__ = host
__webpack_require__.p = "#{host}/"

webpack.config.coffee
remote_hosts = '../webpack-dev-server/remote.coffee' remote_hmr = 'webpack-hot-middleware/client?dynamicPublicPath=true&path=__webpack_hmr'

entry:
  app: ['./app.coffee', remote_hosts, remote_hmr]

Looks like this still works with webpack 5.
Only difference for me was having both __webpack_public_path__  and __webpack_require__.p equal
`${host}/`


Regression: Empty "SQLTools Results" tab after executing query (SQLite)

Describe the bug
When I run a query, the results do not show in the "SQLTools Results" tab that comes up. It is a blank screen.
Downgrading to SQLTools 0.22.9 and restarting vscode (window reload doesn't work) fixes the issue.
To Reproduce
Steps to reproduce the behavior:

Execute any query

Expected behavior
Results to show in the opened tab
Screenshots

Desktop (please complete the following information):

SQLTools Version v0.22.10
VSCode Version: 1.47.0-insider (user setup)  2020-07-03T10:27:06.804Z
OS: Windows 10 20.04
Driver: SQLite
Database version: SQLite 3.31.1

I also see this issue with the Postgres Driver

Dup #639


Specifications Rework

A new specification language should be developed, with its own internal representation in BASIL. The ANSI/ISO C Specification Langage (ACSL) may serve as a useful reference point for this new specification language. The specifications should ideally be integrated into BASIL at the stage of the BASIL IR, rather than only being added in at the last stage when translation to Boogie happens as is currently the case.
To translate specifications into Boogie, a system that parses C types will be necessary, and the type information of parameters of C-level functions will need to be used to map C-level parameters to Boogie-level registers and stack locations in accordance with the ARM64 ABI. This is a complex task.
Specifying properties such as pointer freshness is likely to be useful and necessary, but we will need to determine what the scope of the specification language should be.
We of course want to maintain existing functionality around specifying security predicates for global variables, thread relies and guarantees, and function preconditions and postconditions.

Libclang is possibly a reasonable choice for parsing C types? I had a brief look at this a few weeks ago https://github.com/UQ-PAC/bil-to-boogie-translator/tree/libclang-funcdef-tool/scripts/libclang-type-info. Vercors and Frama-C may have better solutions since they're closer to our domain, but I haven't looked into them, I don't know if there's anything we can use. I think it's a valid question whether we want to have specifications embedded in the code itself; considering handling threads etc. I imagine writing specs might have to be some iterative process with the basil tool involved; e.g. asking it what thread IDs it found and then writing a spec about those threads.

map C-level parameters to Boogie-level registers and stack locations in accordance with the ARM64 ABI

relevant: https://github.com/ARM-software/abi-aa/blob/main/aapcs64/aapcs64.rst
This topic also relates to the MRA, we probably want to use the same set of heuristics for the a-loc candidate pass.

Libclang does seem worthy of further investigation there, it seems like it should do what we want but hard to say for sure without looking more closely at it.
Embedding specifications in the code itself is an even harder problem for us, as we then have to maintain the correspondence between everything throughout the compilation and lifting process, probably by making use of debug information. There has been some previous work looking into using the debug information and it doesn't really seem straight-forward at all as we don't have a good way of retrieving and making use of the debug information through the lifting process right now. It's probably something to look into further in the future but is really a separate task from this.
Yeah, that's the ABI document I was referring to. The relevant section there is 6.8 Parameter Passing.
What's the relevance to the MRA & what's the a-loc candidate pass?

What's the relevance to the MRA & what's the a-loc candidate pass?

Reconstructing the ABI involves identifying where parameters are placed in registers/the stack; we can use type information to give us region boundary candidates.

Ah, that makes sense.

A new specification language should be developed, with its own internal representation in BASIL. The ANSI/ISO C Specification Langage (ACSL) may serve as a useful reference point for this new specification language. The specifications should ideally be integrated into BASIL at the stage of the BASIL IR, rather than only being added in at the last stage when translation to Boogie happens as is currently the case.

This depends on the objectives we are trying to achieve here, and more information would be required to advise on the best solution. Moreover, what is the actual outcome we want to achieve, and what are we trying to solve?
If we want to use ACSL, a few ANTLR grammas are already out there that will aid in this. For example, https://github.com/maximmenshikov/acsl-grammar/blob/master/ACSL.g4 would be sufficient to parse ACSL specification you linked to.

To translate specifications into Boogie, a system that parses C types will be necessary, and the type information of parameters of C-level functions will need to be used to map C-level parameters to Boogie-level registers and stack locations in accordance with the ARM64 ABI. This is a complex task.

There are also C ANTLR grammas out there, which we could use to grab c types. An example would be: https://github.com/antlr/grammars-v4/blob/master/c/C.g4
However, mapping C types from an already compiled binary requires debugging information compiled into the binary. This can be done via objdump -Wi and gcc -g3.

Specifying properties such as pointer freshness is likely to be useful and necessary, but we will need to determine what the scope of the specification language should be.

This is the problem: without first understanding the objective and the problem we are trying to solve here, we are simply stabbing in the dark.

A major part of this issue is figuring out what the scope of the specification language should be. You will have to talk to Nick & Kirsten about this; I couldn't tell you exactly what is desired.
The basics are that we want to be able to specify pre- and post-conditions for C functions, and then translate these into Boogie so the C-level identifiers are translated to whatever they are at the level of the lifted machine code that is translated to Boogie. We also want to specify rely/guarantee predicates per-thread, and security predicates for global variables. There may be other desired functionality that I am unaware of. Determining what we want to be able to express in the pre/postconditions especially is a major part of this.
I don't know if we will want to use ACSL, a subset of it, something merely based upon it, or something else completely. There hasn't been any assessment made of how well it will map to our needs (or even exactly what our needs are), it's just a starting point for investigation.
Mapping the C-level values and types to the lifted machine code is a complex problem and there are many potential ways to do this, yes. We haven't really made any assessment of what the best way would be, what I described was merely one option that doesn't involve dealing with debug information. Do we want to rely on having debug information? Do we want to parse the C source for type information, or make the user specify type information in the specification files separately and not directly work with the C source at all? There are many, many questions like this that need to be answered that we have not really begun to answer, and part of the task here is to investigate and start to answer them.

To be put on the back burner for the time being.


Option to specify nightly version of Rust

Thanks!

@maksimryndin, going to make some small changes, I think some of the logic here if flipped. Afterwards, let me know if I misunderstood anything!


dubbo spi  IOC some case not work

[ ] I have searched the issues of this repository and believe that this is not a duplicate.
当你的接口只有一个实现类的时候，并且这个实现类被@Adaptive注解。那么你在另外一个类中，通过inject将无法注入成功这个类
When your interface has only one implementation class, and this implementation class is annotated with @Adaptive. Then you are in another class, you will not be able to successfully inject this class through inject

Environment

Dubbo version: latest
Operating System version: mac os
Java version: 1.8

Steps to reproduce this issue
Pls. provide [GitHub address] to reproduce this issue.
Expected Behavior
当你的接口只有一个实现类的时候，并且这个实现类被@Adaptive注解。那么你在另外一个类中，可以成功注入这个类。
When your interface has only one implementation class, and this implementation class is annotated with @Adaptive. Then you are in another class and can successfully inject this class.

Actual Behavior
当你的接口只有一个实现类的时候，并且这个实现类被@Adaptive注解。那么你在另外一个类中，无法成功注入这个类。
When your interface has only one implementation class, and this implementation class is annotated with @Adaptive. Then you are in another class and cannot successfully inject this class.
具体可以看demo类中的main方法。当Log只有一个实现类的时候，并且这个实现类被注解，getLog是null。当log有两个实现类的时候,可以注入成功，比如说Log2这个接口，就可以注入成功。
For details, see the main method in the demo class. When Log has only one implementation class, and this implementation class is annotated, getLog is null. When the log has two implementation classes, it can be injected successfully. For example, the Log2 interface can be injected successfully.
请看：(please see)
https://github.com/xixingya/dubbo-demo

https://github.com/apache/dubbo/pull/12792


Create index.html

Index.html file creates a structure for form.

Thanks for contributing to this project.


Changes to rubix_service inside rubix-rpm

Pull Request Test Coverage Report for Build 223

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

Files with Coverage Reduction
New Missed Lines
%

rubix-hadoop2/src/main/java/com/qubole/rubix/hadoop2/Hadoop2ClusterManagerV2.java
4
59.65%

Totals

Change from base Build 211:
-0.2%

Covered Lines:
578

Relevant Lines:
2470

💛  - Coveralls


[Bug Hunting] Steembottracker application - Bid History

Expected behavior
The Steembottracker is a bidding application build by @yabapmatt that provides a dynamic window for a user to buy votes from the bidding bots, displaying their Minimum Value, Suggested Bid and ROI like parameters. So that a user can bid on the voting power of a particular bot.
It's expected that when a user clicks on the User --> Bid History It should display the History of Bids made by the logged in user.
Actual behavior
Currently, the Bid History is not getting displayed at all irrespective of the waiting time.
How to reproduce

Open the https://steembottracker.com/ on Web Browser (Google Chrome is used here).
Login with a steemit user using steemconnect.
Navigate to User--> Bid History
Frame opens up but no data is displayed.

Browser:  Google Chrome/ Mozilla Firefox
Operating system: Windows 8.1

Recording Of The Bug

Posted on Utopian.io -  Rewarding Open Source Contributors

This has been fixed.


DeepL integration for automatic translations

This is now done:

Note that the free account was registered with my Rx Studio email address and verified via a company credit card.


[EMB-333] Add missing analytics events

Purpose
Send analytics events for page views and user actions that should have been tracked all along
Summary of Changes
New events:

Dashboard page:

Dashboard - Search projects

Quick files detail page:

Quick Files - Filter file browser
Quick Files - Delete file
Quick Files - Open delete modal
Quick Files - Close delete modal
Quick Files - Change view - edit
Quick Files - Change view - revision
Quick Files - Change view - view
Quick Files - Change view - view_edit
Quick Files - Save
Quick Files - Open file
Quick Files - Add tag
Quick Files - Remove tag
Quick Files - Search by tag
File version - Download
File version - Change version

Institutions landing page

Page view
Institutions - Search
Institutions - Next page
Institutions - Header - Read more
Institutions - Visit institution
Institutions - Footer - Contact us

Also I fixed a bug that got in the way of manual testing: Clicking an item's name in the file browser would trigger the open action twice (preventDefault is not the same as stopPropagation).
Side Effects / Testing Notes
I guess the best way to test would be checking the devtools network tab to see google analytics events being sent when you navigate to each page and take various actions.
Ticket
https://openscience.atlassian.net/browse/EMB-333
Reviewer Checklist

[ ] meets requirements
[ ] easy to understand
[ ] DRY
[ ] testable and includes test(s)
[ ] changes described in CHANGELOG.md

Pull Request Test Coverage Report for Build 1247

14 of 34 (41.18%)  changed or added relevant lines in 6 files are covered.
35 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-0.1%) to 59.428%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

app/dashboard/controller.ts
0
1
0.0%

app/institutions/route.ts
2
3
66.67%

app/institutions/controller.ts
3
5
60.0%

lib/osf-components/addon/components/file-list-item/component.ts
0
2
0.0%

app/guid-file/controller.ts
8
22
36.36%

Files with Coverage Reduction
New Missed Lines
%

app/institutions/route.ts
1
67.74%

lib/osf-components/addon/components/file-list-item/component.ts
2
74.0%

app/dashboard/controller.ts
2
41.35%

lib/osf-components/addon/components/file-version/component.ts
5
71.11%

app/institutions/controller.ts
8
52.46%

app/guid-file/controller.ts
17
40.97%

Totals

Change from base Build 1245:
-0.1%

Covered Lines:
2038

Relevant Lines:
3275

💛  - Coveralls


paths which contain '.' or '..'

I have found some strangeness when bfs encounters a folder that has '.' or '..' in its path.
For example I have these folders:
/tmp/Soundcloud/.ION./
/tmp/Soundcloud/.._Shok_../

They are empty. but when I run this:
yes | bfs -nohidden -type d -exec bfs -f {} -not -type d -exit 1 \; -prune -ok bfs -f {} -type d -delete \;

the folders aren't deleted

Those folders are hidden, so -nohidden filters them out


Various python fixes

Fixes found by deepsource.io

Needed for other CP's.
Cherry-picked to v9.0.x branch.


[Backport] k8s 1.27 support for rancher-vsphere-csi chart

Backport of https://github.com/rancher/rancher/issues/41793
This issue is to implement the chart changes & perform the testing required to upgrade to k8s 1.27. Please perform below steps.

[ ] Check whether the chart has any references to the below deprecated features of k8s 1.27. You can find information about deprecated APIs here on Kubernetes Deprecation guide.

storage.k8s.io/v1beta1 API version of CSIStorageCapacity

[ ] Update kube-version annotation in Chart.yaml. catalog.cattle.io/kube-version: '>= 1.23.0-0 < 1.28.0-0'

Note: If this is an upstream chart and if the upstream chart doesn't support k8s 1.27 then do not update the kube-version annotation or update the k8s version accordingly.

[ ] Perform below tests

Fresh install/uninstall/upgrade/downgrade of the charts on K8s 1.27 provisioned on Rancher. Test the chart functionality.
(Please refer to the https://github.com/rancher/rancher/issues/41395 to know what testing was done for k8s 1.26 upgrade for your chart)

Provision rancher on k8s 1.26 or lesser

Install chart on this cluster

Upgrade this cluster in rancher to k8s 1.27

Make sure the existing chart and the app is functional after cluster upgrade

@thatmidwesterncoder , need to introduce rancher-vsphere-csi to https://github.com/rancher/charts/tree/dev-v2.7.11 similar to https://github.com/rancher/charts/tree/release-v2.8/charts/rancher-vsphere-csi/103.0.0%2Bup3.0.2-rancher1 (but with 2.7.x versioning). See https://github.com/rancher/charts/pull/2956 for reference.

tested on 2.7.11-rc3:

deploy 1.26 cluster, install csi chart
upgrade to 1.27
upgrade chart to latest version -- pass

fresh install with chart on 1.27 -- pass


Ignore indices.data_stream as API is unstable (experimental)

Failing windows canary test should be fixed with #4558 as the prelease packages we used to depend moved out of the retention policy.