fix

🛠 Fixes Issue (Number)
fix#1054
Closes #issue_number

👨💻 Changes proposed

✅ Check List (Check all the applicable boxes)

[x] You have linked this PR to the correct issue.
[x] My code doesn't break any part of the project (Zero Octave-Javascript-Projects).
[x] This PR does not contain plagiarized content.
[x] My Addition/Changes works properly and matches the overall repo pattern.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

Here  Solved the bug #1054


Image normalization causing test_model test failure

Hello! I ran into the issue while trying to run the test_model function on the exported model.
I want to discuss if the following behavior is a conscious choice or more of an oversight.
Sorry in advance for the long explanation 😄
I am trying to export and test the model from an external library (N2V).
I have a sample input image with a large mean and std. I normalize it, run the model and then denormalize the model output. The processing portion of my model rdf looks like this:
inputs:
- axes: byxc
  data_range: [-.inf, .inf]
  data_type: float32
  name: input0
  preprocessing:
  - kwargs:
      axes: yx
      mean: [32473.281]
      mode: fixed
      std: [18754.428]
    name: zero_mean_unit_variance
  shape: [1, 64, 64, 1]
outputs:
- axes: byxc
  data_range: [-.inf, .inf]
  data_type: float32
  name: output0
  postprocessing:
  - kwargs:
      axes: yx
      gain: [18754.428]
      offset: [32473.281]
    name: scale_linear
  shape: [1, 64, 64, 1]

After running test_model function on the exported model, the last test fails with the following error:
{
  'name': 'reproduce test outputs from test inputs (bioimageio.core 0.5.9)',
  'status': 'failed',
  'error': 'Output and expected output disagree:\n \nArrays are not almost equal to 4 decimals\n\nMismatched elements: 416 [/](https://vscode-remote+ssh-002dremote-002bvdi.vscode-resource.vscode-cdn.net/) 4096 (10.2%)\nMax absolute difference: 0.00048828\nMax relative difference: 2.5800531e-07\n x: array([[[[3405.0159],\n         [3877.9998],\n         [1644.0879],...\n y: array([[[[3405.0159],\n         [3877.9995],\n         [1644.0879],...',
  'traceback': None
}

After some investigation, I believe I was able to localize the issue - there is a slight difference between how the image is being handled in zero_mean_unit_variance vs my code.
When mean and std values are validated from the model rdf, it is done essentially in this way:
mean = np.array(float(mean_string)), which yields a float64 value.
After running zero_mean_unit_variance with this value on a float32 input, it becomes float64.
The problem with this behavior is that in my code, and probably many other users' code, the input value will stay the same type - float32 from the beginning to the end of the inference pipeline (although images with this large of the mean are probably rarer) If the mean and std values are large the resulting difference after normalization and denormalization between the output of my pipeline and bioimage core becomes big enough to fail the test.
So potential solutions could be one of the:

ensuring that mean and std values are fixed to the same dtype as the data_type in the model rdf in the bioimage core
making it clear somewhere in the documentation that the user should be careful with how he handles normalization in his own code

Here is the sample code to reproduce the issue. If you pass input and output tensors as type np.float32 the test will fail. If you uncomment the conversion of input and output to np.float64 the test will pass.
import os

import numpy as np
from tensorflow import keras
from tensorflow.keras import layers

from bioimageio.core.build_spec.build_model import build_model
from bioimageio.core import load_resource_description
from bioimageio.core.resource_tests import test_model

os.makedirs("my-model", exist_ok=True)

model = keras.Sequential([
    layers.Conv2D(1, kernel_size=1, activation=None, input_shape=(64, 64, 1), padding='same')
])
model.save('my-model/weights.hd5', save_format='h5')

X = np.random.rand(1, 64, 64, 1).astype(np.float32)
# X = np.random.rand(1, 64, 64, 1).astype(np.float64)

# multiplying by 5000 to make X mean and std values large
X *= 5000
np.save("my-model/test-input.npy", X)

mean = X.mean().item()
std = X.std().item()
eps = 1e-6
X = (X - mean) / (std + eps)

output = model.predict(X)
# output = output.astype(np.float64)
output = output * std + mean
np.save("my-model/test-output.npy", output)

with open("my-model/doc.md", "w") as f:
    f.write("# My First Model\n")

build_model(
    weight_uri="my-model/weights.hd5",
    weight_type="keras_hdf5",
    test_inputs=["my-model/test-input.npy"],
    test_outputs=["my-model/test-output.npy"],
    input_axes=["byxc"],
    output_axes=["byxc"],
    output_path="my-model/model.zip",
    name="MyFirstModel",
    description="a fancy new model",
    authors=[{"name": "Gizmo"}],
    license="CC-BY-4.0",
    documentation="my-model/doc.md",
    tags=["nucleus-segmentation"],
    cite=[{"text": "Gizmo et al.", "doi": "doi:10.1002/xyzacab123"}],
    preprocessing=[[
        {
            'kwargs': {
                'axes': 'yx',
                'mean': [mean],
                'mode': 'fixed',
                'std': [std]
            },
            'name': 'zero_mean_unit_variance'
        }
    ]],
    postprocessing=[[
        {
            'kwargs': {
                'axes': 'yx',
                'offset': [mean],
                'gain': [std]
            },
            'name': 'scale_linear'
        }
    ]]
)

my_model = load_resource_description("my-model/model.zip")
test_model(my_model)

Versions:
bioimageio_spec_version: 0.4.9
bioimageio_core_version: 0.5.9

Hi @veegalinova,
thanks for the clear description of the issue! I don't have time right now to think about how to cleanly solve this, but just wanted to let you know that we have a workaround: it is possible to set the precision for the test in test_model via the --decimal parameter. Setting this e.g. to 2 (default is 4), will probably fix the test. You can also add something to the config in the rdf so that this is respected by the CI. (I am not quite sure about the details anymore, @FynnBe should know more).
(T)

Are the --decimal and config (CI-wise) documented somewhere on https://bioimage.io/docs/#/? I couldn't find it there, but also might have missed it.


[MM-42906] - License receives invalid date in the console when license expiration check runs

Summary
This PR ensures the EnterpriseEditionLeftPanel component uses an unsanitized license to display information about the license
Ticket Link
MM-42906
Release Note
NONE

/e2e-test

The command /e2e-test requires all PR checks to pass.

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/190342

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/190373

/update-branch

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/190389

I'm pretty sure the /e2e-test runs here are failing because they are running against the MM-42906 server branch, which is out of date and was already merged separately into master over there. I'm checking with the other SDETs on this.

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/190492

@AGMETEOR Test still failed. The build is not picking up the latest update (I made) on your server's MM-42906 branch. Maybe check with Release team on what's going on. Not sure if it requires the branch to be submitted as PR. If such server branch is not required, could it be deleted so that this PR will build against master of server and enterprise?

Hmm, okay, I just saw this PR - https://github.com/mattermost/mattermost-server/pull/20035 - and it's already closed. Hope you don't mind but while I'm here, I'll go ahead and reopen that PR for the purpose of seeing the build, then eventually close and delete the remote server branch.

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/190515

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/190528

This should be good now - https://automation-dashboard.vercel.app/cycles/44472e7a-14ce-4232-89c6-63c1bfb8bfd2, but I'll be pushing another empty commit so that it will pick up the new server PR (empty, on master, https://github.com/mattermost/mattermost-server/pull/20132) instead of the old PR (https://github.com/mattermost/mattermost-server/pull/20035).

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/190545


[SPARK-47102][SQL][COLLATION] Add COLLATION_ENABLED config flag

What changes were proposed in this pull request?
This PR adds COLLATION_ENABLED config to SQLConf and introduces new error class COLLATION_SUPPORT_NOT_ENABLED to appropriately report error on usage of feature under development.
Why are the changes needed?
We want to make collations configurable on this flag. These changes disable usage of collate and collation functions, along with any COLLATE syntax when the flag is set to false. By default, the flag is set to false.
Does this PR introduce any user-facing change?
Yes. It introduces new error along with an appropriate message.
How was this patch tested?
./build/mvn -Dtest=none -DwildcardSuites=org.apache.spark.sql.errors.QueryCompilationErrorsSuite test
./build/mvn -Dtest=none -DwildcardSuites=org.apache.spark.sql.catalyst.expressions.CollationExpressionSuite test
./build/mvn -Dtest=none -DwildcardSuites=org.apache.spark.sql.CollationSuite test

Was this patch authored or co-authored using generative AI tooling?
No.

Current SQLConf.COLLATION_ENABLED cannot be used to prevent errors of invalid collation name in TypeContext. How should I proceed with this? In my view, if customer sends a query with word COLLATE, but invalid string literal, I would expect to get back error Collation not supported before getting error of Invalid Collation name. I investigated this and am pretty sure SQLConf is not the right way to go if we want to include this config for this error. @cloud-fan @MaxGekk

@mihailom-db The test failure is related to your changes:
[info]   Cause: org.scalatest.exceptions.TestFailedException: Function 'collate', Expression class 'org.apache.spark.sql.catalyst.expressions.CollateExpressionBuilder' "...ql.collation.enabled[	]true" did not equal "...ql.collation.enabled[ ]true"

Please, fix it.

+1, LGTM. Merging to master.
Thank you, @mihailom-db and @cloud-fan @dbatomic @mkaravel for review.


Add example for normal scrollview

Added more examples along with a master->detail navigation here https://github.com/kmagiera/react-native-gesture-handler/commit/c0c3ea1c97cccd77775cb950f8bc575e7e6e792e
But thanks anyways


Can't get SIWE to work with brave during development

I ran into an issue doing some QA testing of our site while using the Brave browser.  If I run a localhost dev network and app, I can't sign-in.  I'm getting the following error:
http://localhost:8080
We've rejected this request because this site is requesting that you use a different domain (https://localhost:8080)

Note that The brave browser thinks the site is requesting that I use https, when the site is using http.  If I change the domain property of the SIWE object to the fully qualified origin, the Brave wallet will sign the message but the backend will not verify the message.
To debug I tried using some of the apps in this repo, but they don't seem to work with Brave either.
To reproduce start up the quickstart 03_complete_app, and try to sign-in with Brave.
fwiw: everything works as expected on a public https domain.

If the issue is really with the domain field, it means that the Brave wallet is somehow adding a default scheme but the scheme is optional. Maybe they do it for security purposes but it is a deviation from the specs.
As for why the backend is not successfully verifying the message, I suspect it's because it's using an older version of the siwe library, which doesn't have support for the optional scheme. A PR would be welcome to update it. (If you do update it, please note that scheme is its own field and shouldn't be part of domain)

@sbihel Thanks for the response.
I'll bump the siwe version and see if that works, regardless I will work on a PR once I find a fix.


UserCategory parameter is missing in the SDK for User object

Hey guyz,
I was checking the MangoPay API documentation this morning about the new TermsAndConditionsAccepted parameter, and I discovered another new parameter ( UserCategory ) that is currently missing from the SDK.
Cheers,

Fixed with #558 so we can close this issue :)


I have created the local_server branch (not sure if I did it right), any reviews and constructive criticism is welcome.

I think Shawn said we're not going to use databases for this project so you can probably get rid of the database and model directories. And I guess if we're trying to only push what's necessary maybe delete the v1 directories as well because we have version control with GitHub (althought I'm not sure about that one, maybe it is good practice to keep track of versions but you'd probably wanna ask Shawn about that).
The main.py looks good

I deleted the database and model folders. I'll wait for @zeitgeistf to confirm whether we need to delete the v1 directories.

One comment related to the "title" of this PR.
Let's keep both PR title and commit comment as concise as possible, only describe what's related to the change, no need to add pronoun and extra comments (commit messages in this PR looks fine)
So for the title, we can shorten it to just "FastAPI basic server setup" or anything along this time

I deleted the database and model folders. I'll wait for @zeitgeistf to confirm whether we need to delete the v1 directories.

Versioning in the code or API router is used for larger projects with fast development and iteration, this is to prevent existing user experiencing breaking change when API is updated with new feature or modofications.
For our case, since we are the caller, and the API is fairly straightforward, we can remove v1 from the path to keep everything clean and simple

I did a bit of restructuring based on the file structure that Eddie created and some advice that Shawn gave me.

removed the local_server directory that was encapsulating everything
removed the v1 folders
added a utils folder
moved the routes from main.py

switched to an architecture that uses routers, basically instead of having decorators that define routes right above controller functions, there's a separate router (api/router.py) that creates the routes and connects them with an endpoint function (stored in controllers), and then the router is added to the app in main.py.


Make $model for getType() optional

Most often the serializer knows about the type, a $model would just be a stub here

I made the pull-request just from github. The problem arised is the one, I have in my code now. Basically, my serializers need to take the $model parameter for the getType() method. Although the parameter is completely useless in my case, I'd rather have it optional, than to call $serializer->getType(null).

I don't understand, where are you calling $serializer->getType(null)? You shouldn't need to call that directly, the Resource class does it for you. I can't see any rationale behind this. Also, this PR completely breaks the library/tests.

I do use my serializers from other locations as well. Basically, my models do have a static getSerializer() method. E.g. I do: Model::getSerializer()->getType(null). Also they implement some more interfaces.

I will retouch this PR to finish what I started. Would like to get this into the next release. Please ping me, if the next releases nears on nothing has been done here.

The problem is that theoretically, if someone implements the getType method in their serializer, it may rely on the $model being passed through and not being null. e.g.
public function getType($model) {
    return $model->type;
}

In this case, having a default value for the $model parameter doesn't make sense.
If passing in null is such an annoyance for you, can you implement something like a Model::getSerializerType() method which hides it?


VS 2015 error when opening DesktopBridgeDemoStep solutions

Got error when loading Step 1:
"Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- UWPPackager, "E:\work\GitHub\DesktopBridgeToUWP-Samples\Samples\JourneyAcrossTheBridge\DesktopBridgeDemo - Step1\UWPPackager\UWPPackager.vsdproj"
No changes required
These projects can be opened in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without changing them.
- MyDesktopApp, "E:\work\GitHub\DesktopBridgeToUWP-Samples\Samples\JourneyAcrossTheBridge\DesktopBridgeDemo - Step1\MyDesktopApp\MyDesktopApp.csproj"
- DesktopBridgeDemoStep1, "E:\work\GitHub\DesktopBridgeToUWP-Samples\Samples\JourneyAcrossTheBridge\DesktopBridgeDemo - Step1\DesktopBridgeDemoStep1.sln"
Trying Step 4 I get:
E:\work\GitHub\DesktopBridgeToUWP-Samples\Samples\JourneyAcrossTheBridge\DesktopBridgeDemo - Step4\BackgroundTasks\BackgroundTasks.csproj : error  : The imported project "C:\Program Files (x86)\MSBuild\Microsoft\WindowsXaml\v15.0\Microsoft.Windows.UI.Xaml.CSharp.targets" was not found. Confirm that the path in the  declaration is correct, and that the file exists on disk.  E:\work\GitHub\DesktopBridgeToUWP-Samples\Samples\JourneyAcrossTheBridge\DesktopBridgeDemo - Step4\BackgroundTasks\BackgroundTasks.csproj
E:\work\GitHub\DesktopBridgeToUWP-Samples\Samples\JourneyAcrossTheBridge\DesktopBridgeDemo - Step4\MyUWPApp\MyUWPApp.csproj : error  : The imported project "C:\Program Files (x86)\MSBuild\Microsoft\WindowsXaml\v15.0\Microsoft.Windows.UI.Xaml.CSharp.targets" was not found. Confirm that the path in the  declaration is correct, and that the file exists on disk.  E:\work\GitHub\DesktopBridgeToUWP-Samples\Samples\JourneyAcrossTheBridge\DesktopBridgeDemo - Step4\MyUWPApp\MyUWPApp.csproj
E:\work\GitHub\DesktopBridgeToUWP-Samples\Samples\JourneyAcrossTheBridge\DesktopBridgeDemo - Step4\BackgroundTasks\BackgroundTasks.csproj : error  : The imported project "C:\Program Files (x86)\MSBuild\Microsoft\WindowsXaml\v15.0\Microsoft.Windows.UI.Xaml.CSharp.targets" was not found. Confirm that the path in the  declaration is correct, and that the file exists on disk.  E:\work\GitHub\DesktopBridgeToUWP-Samples\Samples\JourneyAcrossTheBridge\DesktopBridgeDemo - Step4\BackgroundTasks\BackgroundTasks.csproj

check your solution file and see if VS 2015 changed the project template type.  The standard is
FAE04EC0-301F-11D3-BF4B-00C04F79EFBC
but the bridge projects use a template type of:
F365BE41E-7993-430D-A5E6-1381A54BC077
In my experience VS 2015 will let you open the project and modify files, but it will change the template type in the solution.  You have to use VS 15 Preview 2 or greater to actually debug deploy, since that is what the project template VSIX  supports.
Did you follow these steps?
https://msdn.microsoft.com/en-us/windows/uwp/porting/desktop-to-uwp-deploy-and-debug?f=255&MSPPError=-2147217396

I already hat the suspicion that VS 15 has to be used. But in the Readme of Desktop app bridge to UWP Samples only Visual Studio 2015 if given as requirement.
When using VS 15 Preview 4 and changing Versions in MyUWPApp.csproj to 10.0.14393.0  it worked now for me.


Update CDK and TF "vs" pages to include Automation API

Now that we've launched Automation API (https://www.pulumi.com/blog/automation-api/) we should update our comparison guides to highlight Pulumi's strengths in end to end software-driven automation support.

Fixed via #1304.


Build failed.

Build failed.
"C:\src\DarkHelp\build\DarkHelp.sln" (Build target) (1) ->
"C:\src\DarkHelp\build\ALL_BUILD.vcxproj.metaproj" (default target) (2) ->
"C:\src\DarkHelp\build\src-cam\DarkHelp_cam.vcxproj.metaproj" (default target) (3) ->
"C:\src\DarkHelp\build\src-lib\dh.vcxproj.metaproj" (default target) (4) ->
"C:\src\DarkHelp\build\src-lib\dh.vcxproj" (default target) (23) ->
(ClCompile target) ->
C:\src\DarkHelp\src-lib\DarkHelpNN.cpp(1619,22): error C2039: 'create_yolo_heatmaps': not a member of 'Darknet' [C:\src\DarkHelp\build\src-lib\dh.vcxproj]
C:\src\DarkHelp\src-lib\DarkHelpNN.cpp(1619,22): error C3861: 'create_yolo_heatmaps': identifier not found [C:\src\DarkHelp\build\src-lib\dh.vcxproj]
C:\src\DarkHelp\src-lib\DarkHelpNN.cpp(1636,17): error C2039: 'create_yolo_heatmaps': not a member of 'Darknet' [C:\src\DarkHelp\build\src-lib\dh.vcxproj]
C:\src\DarkHelp\src-lib\DarkHelpNN.cpp(1636,17): error C3861: 'create_yolo_heatmaps': identifier not found [C:\src\DarkHelp\build\src-lib\dh.vcxproj]
C:\src\DarkHelp\src-lib\DarkHelpNN.cpp(1636,3): error C2593: 'operator =' is ambiguous [C:\src\DarkHelp\build\src-lib\dh.vcxproj]
0 warnings
5 errors

My guess is you're using an old version of Darknet/YOLO which doesn't support heatmaps.  Please run darknet --version and post the version you are using.

My guess is you're using an old version of Darknet/YOLO which doesn't support heatmaps. Please run darknet --version and post the version you are using.

C:\Program Files\Darknet\bin>darknet --version
Darknet V3 "Jazz" v3.0-174-ga1e62b61
CUDA runtime version 12060 (v12.6), driver version 12070 (v12.7)
cuDNN version 12060 (v9.6.0), use of half-size floats is ENABLED
=> 0: NVIDIA GeForce RTX 3090 [#8.6], 24.0 GiB
OpenCV v4.10.0, Windows 11 Pro

I made a mistake the other day.  Everything is working correctly as far as I can tell:

From your post, you are running v3.0-174 from Oct 31.  This is prior to support for heatmaps, which was added in November and December.  Please make sure you are using the most recent version of both Darknet and DarkHelp.

@huniz86 Any update?  Can this be closed?

@huniz86 Any update? Can this be closed?

Sorry for the late reply.
This issue has been resolved, so I will close it.
Thank you.


stress: remove Schedule() since data races are fixed

Codecov Report

Merging #273 into master will increase coverage by 0.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #273      +/-   ##
==========================================
+ Coverage   99.01%   99.13%   +0.11%
==========================================
  Files          70       49      -21
  Lines        3058     2196     -862
==========================================
- Hits         3028     2177     -851
+ Misses         16       10       -6
+ Partials       14        9       -5

Flag
Coverage Δ

#dot
99.13% <ø> (+0.11%)
:arrow_up:

#dot_changes
100% <ø> (ø)
:arrow_up:

#dot_changes_diff
100% <ø> (ø)
:arrow_up:

#dot_changes_run
100% <ø> (ø)
:arrow_up:

#dot_changes_table
100% <ø> (ø)
:arrow_up:

#dot_changes_types
100% <ø> (ø)
:arrow_up:

#dot_example
100% <ø> (ø)
:arrow_up:

#dot_ops
97.87% <ø> (ø)
:arrow_up:

#dot_ops_bolt
97.67% <ø> (ø)
:arrow_up:

#dot_ops_nw
97.97% <ø> (ø)
:arrow_up:

#dot_ops_pg
97.45% <ø> (ø)
:arrow_up:

#dot_refs
100% <ø> (ø)
:arrow_up:

#dot_streams
98.73% <ø> (-0.3%)
:arrow_down:

#dot_streams_undo
?

#dot_test_seqtest
?

#dot_x_dotc
?

#dot_x_fold
?

#dot_x_heap
?

#dot_x_rt
?

#dot_x_ui_collab
?

#dot_x_ui_dom
?

#dot_x_ui_html
?

#dot_x_ui_input
?

Impacted Files
Coverage Δ

streams/scheduler.go
100% <ø> (ø)
:arrow_up:

x/ui/collab/keyboard.go

x/dotc/slices.go

x/dotc/unions.go

streams/undo/stream.go

x/ui/html/events.go

x/dotc/struct.go

x/ui/html/html.go

x/dotc/union.go

x/dotc/structs.go

... and 12 more

Continue to review full report at Codecov.

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


Adds more characters to the PUA range

Trying to move more characters to the PUA range, adding chars from https://bugzilla.mozilla.org/attachment.cgi?id=8412717&action=diff#a/gfx/thebes/gfxPlatformFontList.cpp_sec1.
Total count of problematic codes now is 2718 (PUA can hold 6400)

/botio-windows preview

/botio test

/botio makeref

Looks good, thank you for the patch!
@yurydelendik Since I don't have a Mac; can you please go through and close the relevant bugs (if they were fixed by this patch)?

[ ] #5540.
[ ] https://bugzilla.mozilla.org/show_bug.cgi?id=1151216.
[ ] https://bugzilla.mozilla.org/show_bug.cgi?id=1175943.

https://bugzilla.mozilla.org/show_bug.cgi?id=1026437 looks fixed now for me using preview

https://bug1151216.bugzilla.mozilla.org/attachment.cgi?id=8588312 is fixed

https://bugzilla.mozilla.org/show_bug.cgi?id=1175943 fixed as well.
good work @yurydelendik


bug: Wagmi createClient error 500, when using lineaTestnet

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
0.12.12
Current Behavior
when i remove lineaTestnet, then its working fine
import { lineaTestnet, arbitrumGoerli } from 'wagmi/chains';

 const { chains, provider, webSocketProvider } = configureChains(
    [lineaTestnet, arbitrumGoerli],
    [
      infuraProvider({ apiKey: process.env.NEXT_PUBLIC_INFURA_API_KEY }),
      publicProvider(),
    ],
  );

Expected Behavior
Should be able to connect linea testnet via infura

Steps To Reproduce
import { lineaTestnet, arbitrumGoerli } from 'wagmi/chains';

 const { chains, provider, webSocketProvider } = configureChains(
    [lineaTestnet, arbitrumGoerli],
    [
      infuraProvider({ apiKey: process.env.NEXT_PUBLIC_INFURA_API_KEY }),
      publicProvider(),
    ],
  );

    const connectors = connectorsForWallets([
    {
      groupName: 'Recommended',
      wallets: [
        injectedWallet({ chains }),
        rainbowWallet({
          chains,
          projectId: process.env.NEXT_PUBLIC_INFURA_PROJECT_ID,
        }),
        metaMaskWallet({
          chains,
          projectId: process.env.NEXT_PUBLIC_INFURA_PROJECT_ID,
        }),
        coinbaseWallet({ chains, appName: 'test' }),
        walletConnectWallet({
          chains,
          projectId: process.env.NEXT_PUBLIC_INFURA_PROJECT_ID,
        }),
      ],
    },
  ]);
  const wagmiClient = createClient({
    autoConnect: true,
    connectors,
    provider,
    webSocketProvider,
  });

Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
No response
Anything else?
tested to replace
     readonly infura: {
            readonly http: readonly ["https://consensys-zkevm-goerli-prealpha.infura.io/v3"];
            readonly webSocket: readonly ["wss://consensys-zkevm-goerli-prealpha.infura.io/ws/v3"];
        };
with

 rpcUrls: {
    infura: {
      http: ['https://linea-goerli.infura.io/v3'],
      webSocket: ['wss://linea-goerli.infura.io/v3'],
    },

but still getting same error,
I tested infura rpc url https://linea-goerli.infura.io/v3 is working to get ethBalance

Check out jsonRpcProvider. Linea isn't configured in ethers InfuraProvider.


Hover for anchors is hard to see on dark mode

Interesting - this was fixed in https://github.com/microsoft/TypeScript-Website/pull/459 but didn't go all the way to h5


CORE-20229: Make AssertWithRetryArgs.command lateinit

Make command a lateinit var. Simplifies the implementation by removing the need for null checks.

build e2e

build e2e


Just a question

Hey love this thanks for making it.
Just wondering if you've encountered this at all: https://github.com/mas-cli/mas/issues/336
I want to use your library for an app that's only iOS so won't affect me personally but as I'd seen it thought I'd mention it just in case.
Thanks again!

@shaps80 I did not encounter such, but I do know that the JSON can be updated quicker than the App Store in some cases. I might build a 24 hours delay before notifying about an update to encounter for this

Right makes sense. In some cases the user's app may even auto-update in that time. Nice one, thanks for coming back to me 👍🏻


Piece Configuration and Coupling

In our current PoC, all of the pieces are independent with no coupling or configuration whatsoever. Imminently, we will need to design and implement a system for configuring pieces which will also allow coupling them together by passing information such as verifiers or data types from one piece to another.
The most obvious use cases are coupling to the money piece so that all transactions can pay a tip and get prioritized appropriately. Similarly, many pieces will need a notion of money to take a security deposit for various piece-specific actions or otherwise provide economic incentives.
In talking with @coax1d, our best idea so far is to use a configuration trait system inspired by FRAME's, although we hope to keep it simpler either by design or just by convention. In such a system, any Verifier that needs configuration can be generic over a type that is bounded by its configuration trait. Foe example:
pub trait VotingConfig {
  type Money: Money;
  const deposit_amount: u128;
}
pub struct VotingVerifier<Config: VotingConfig> {
  // --snip--
}

In the snippet above we see that this pattern is nearly identical to FRAME's but is made simpler by a few soft conventions:

Only verifiers that actually need configuration take the config type parameter.
We call it Config instead of just T
We use associated constants rather than the Get trait.

None of these would be enforced, and developers who want to could still do it the FRAME way, but we should encourage only doing so when there is a good reason so as to keep Tuxedo code as simple and readable as possible.
The design may be shifted entirely.

Also in the original post made by @JoshOrndorff Verifier is now replace with ConstraintChecker
See #45 for more details

This has been done for a little while. It is demonstrated well in our dex tutorial. We ended up with a config trait system like FRAME's, as expected.
It is demonstrated well in our dex tutorial in the section about titles Generic parameters and DexConfig


Adding openthread API for Energy Scan operation

This is needed for #433.

LGTM :+1:

LGTM.

LGTM 👍


fix: fixed http library to properly set API header with organization …

[ ] Ready for review
[ ] Linked to Jira ticket

What does this PR do?
fix: fixed http library to properly set API header with organization name
Currently, we don't set a header with organization name for getAnalysis call.
These changes are all internal and don't affect public API
Where should the reviewer start?
How should this be manually tested?
Any background context you want to provide?
Screenshots
Additional questions

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Delete / application/json

Hi,
First of all very nice work, I love your module.
As I love it, I used it a lot :) and find something strange:
On the same object I use both PUT and DELETE actions.
With PUT my HTTP header Content-Type is set to "application/json" which is ok
but with DELETE Content-Type is set to "text/plain".
I don't understand why DELETE should be a text/plain as it's called on a js object.
My server accept only application/json content-type and I wanna be sure that's normal behavior before to create custom deletes ?
Thanks

But content will be send inside a delete request (1.4.0) So it would be good to have application/json as content type


Add links

Updated the code by Adding links to help center section for user notification
Fixes: https://github.com/zulip/zulip/issues/30562
Fix issue code:30568

@SamarthKoli welcome! Neither of these commits seem to have any content.
Take some time to learn Git a bit better and review our contributing guidelines before making a next PR.


Theory Macro should accept docstrings

In order to document a module created by a macro, you need to put the docs after the thing you document.
@theory ThClass begin
  Ob::TYPE ⊣ []
end

@doc """    ThClass

A Class is just a Set that doesn't worry about foundations.

""" ThClass

But it would be nice to do:
@theory """    ThClass

A Class is just a Set that doesn't worry about foundations.

""" ThClass begin
  Ob::TYPE ⊣ []
end

or
@theory ThClass
@doc """    ThClass

A Class is just a Set that doesn't worry about foundations.

""" begin
  Ob::TYPE ⊣ []
end

or something like that.

This should and I assume will work like it already does it Catlab:
"""    ThClass

A Class is just a Set that doesn't worry about foundations.

"""
@theory ThClass begin
  Ob::TYPE ⊣ []
end


Revert "adjust tests to changes from TSC"

Reverts apple/swift-package-manager#3008
Seeing failure in CI:
https://ci.swift.org/job/oss-swift-pr-test/13664/console
22:55:23 [36/48] Compiling PackageLoadingPerformanceTests ManifestLoadingTests.swift
22:55:23 /Users/buildnode/jenkins/workspace/oss-swift-pr-test/swiftpm/Tests/PackageLoadingPerformanceTests/ManifestLoadingTests.swift:21:13: error: cannot find 'testWithTemporaryDirectory' in scope
22:55:23         try testWithTemporaryDirectory { tmpdir in
22:55:23             ^~~~~~~~~~~~~~~~~~~~~~~~~~
22:55:23 error: fatalError

@swift-ci test

@swift-ci smoke test

cc: @tomerd

I dont think we need to revert #3008, instead we need to merge #3009
cc @abertelrud

Sounds good, closed this PR and we should merge 3009 to unblock Swift pull request testing.


Dump actual diffs in "decoders" and "parser" in embulk-guess-csv_verify

embulk-guess-csv-verify (#1415) originally dumped only different key names, without actual diffs, in order to avoid logging confidential information (e.g. AWS access token) unintentionally.
But, actual diffs are really helpful to investigate. This PR is to dump actual diffs of decoders and parser sections because those sections should not have any confidential information.

should not have any confidential information

Does it mean they CANNOT have such information, or is it still possible?

Thanks for your comment.

Does it mean they CANNOT have such information, or is it still possible?
At least for the default guess, decoders, and parsers we have -- bzip2, gzip, json and csv, they cannot have. If a user adds their own special ones in their configuration, it can have.

But, I don't think It's a problem because :

This embulk-guess-csv_verify is really a special plugin only for verifycation purpose (not to be bundled with the Embulk executable package). OSS Embulk users should use it at their own risk.
It does not sound very natural to use confidential information in "decoding" and "parsing", not about accessing to a storage like S3, SFTP, ...
(Just for ourselves) we plan to use it in our own service, but we only have known guess, decoders, and parsers. They have no concerns about confidential information.

Thank you, it makes sense to me. I'd include a comment "Make sure no credentials are included" anyway, but I don't think it's a blocker.

Thanks! Reasonable suggestion.
I pondered where to comment, but decided to note that in the RubyGem's "description" part. (To be available in https://rubygems.org/gems/embulk-guess-csv_verify)

@dmikurube I'd probably add it to dumping messages.


⚠ Avatar API Endpoint has degraded performance

In 223dded, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 5108 ms

Resolved: Avatar API Endpoint performance has improved in 7de8e55 after 21 minutes.


scale dynotype up/down

Eg in low periods scale down to hobby and scale up when  needed

Im thinking it could be based on the total rpm?

I wouldn't be able to use this because we configure our unicorn and resque process pools to run on a given class of hardware, although I suppose we could detect the dyno class and set parallelism dynamically on boot.
I don't have a clear vision of how the logic (and config) for this would interact with the simple "N users per dyno" or "M rpms per dyno" we use now. I guess we would need to define a 'users per dyno' value for each dyno class, but then defining the boundary of when you scale up to the next class vs adding more 1X dynos would be hard to fathom.
I think what I'm saying is that this is too complicated and doesn't answer a real need for us at Harry's, but I could see it being really useful for a site with very low average traffic that is highly burstable. A pull request would definitely be considered.


Confusing reporting of "(-w/2)"

With
% cat Delme.hs
module Foo where
foo p = case p of
  A -> 0
  B w -> -w
  C w -> (-w/2)

I get
% hlint Delme.hs
Delme.hs:2:9: Warning: Redundant bracket
Found:
  case p of
      A -> 0
      B w -> -w
      C w -> (-(w / 2))
Why not:
  case p of
      A -> 0
      B w -> -w
      C w -> -(w / 2)

1 suggestion

Note that it claims it found the text (-(w/2)) when it is actually (-w/2). This is not a particularly serious issue, but I thought I'd note it here. If I change the line to use -(w/2) then hlint accepts it.
I am using
% hlint --version
HLint v1.8.57, (C) Neil Mitchell 2006-2014

This has been fixed with haskell-src-exts <IP_ADDRESS> (probably got fixed before that, but I've only just retested).


currentSlide undefined on mount with carousel later snapping into place

Describe the bug
I have a carousel which is created from a list of objects (which only stores 2 strings) stored via pinia state management. When loading the page the carousel is in-between slides and after about a second or so it snaps to the correct modelValue. I've tried setting the modelValue to a static integer but the carousel still initializes in-between slides and snaps back.
When printing onMount the modelValue is set correctly but the currentSlide is undefined. Additionally I've confirmed my pinia objects are correct and non-null.
Thanks for any help 😄!
To Reproduce
<Carousel
	:itemsToShow="3"
	:wrapAround="true"
	:transition="500"
	:modelValue="piniaStore.initialSlide"
	ref="myCarousel"
	@slide-start="handleSlide"
>
	<Slide v-for="(option, index) in piniaStore.options" :key="option">
            <div class="carousel__item">
	            <h1 > {{ option.name }}  </h1>
            </div>
	</Slide>
</Carousel>

.carousel__slide {
	padding: 5;
}
.carousel__viewport {
	perspective: 2000px;
}
.carousel__track {
	transform-style: preserve-3d;
}
.carousel__slide--sliding {
	transition: 0.5s;
}
.carousel__slide {
	opacity: 0.9;
	transform: rotateY(-20deg) scale(var(--filter-other-scale));
}
.carousel__slide--active ~ .carousel__slide {
	transform: rotateY(20deg) scale(var(--filter-other-scale));
}
.carousel__slide--prev {
	opacity: var(--filter-other-opacity);
	transform: rotateY(-10deg) scale(var(--filter-other-scale));
}
.carousel__slide.carousel__slide--next {
	opacity: var(--filter-other-opacity);
	transform: rotateY(10deg) scale(var(--filter-other-scale));
}
.carousel__slide--active {
	opacity: 1;
	transform: rotateY(0) scale(1);
}

// pinia values on mount for example
// piniaStore.options = [{name: "option 1", date: "date 1"}, {name: "option 2", date: "date 2"}, etc.];
// piniaStore.initialSlide = 0;

Expected behavior
The carousel will be initialized with the first slide being the one set as modelValue and currentSlide will be set to be equal to modelValue
Desktop (please complete the following information):

OS: Windows
Browser: chrome
Version: 127.0.6533.100

Hi! Thanks for reporting the issue. I tried reproducing the behavior you described using a similar setup, but it seems to work as expected in this live example: Live Example on StackBlitz. The carousel initializes correctly with the first slide matching the modelValue, and there’s no snapping issue.
You might want to check:
1.	If your piniaStore is fully populated before the carousel renders. Using a v-if to ensure data is ready can help.
2.	If there are any asynchronous operations or reactivity mismatches in your setup causing delays.
Let me know if the issue persists even with the adjustments from this example, and I’d be happy to assist further!
Cheers! 😄


Rename .env.template to .env.example

Could you rename it please & resubmit to vercel.com/templates? Thanks!

sure thing


[Bug]: Display msgbox info not working in Gui

Apache Hop version?
2.7.0 (2023-11-17 12.19.09)
Java version?
11
Operating system
Windows
What happened?
When using Display msgbox info in workflow it will not display a popup.
Issue Priority
Priority: 2
Issue Component
Component: Transforms

Bug confirmed, GuiFactory not yet implemented


D&D Dice - show individual rolles

There are times in D&D when you need to know what each die did separately, not just the sum of all the dice.
So, I need to show the individual numbers somewhere.  It can be small and plain in the corner, perhaps. But still.
NOTE: The player may roll a dozen dice. If so... displaying each die separately might look ugly.  Perhaps they need to be in a column, not a row.

Naw, I'm not doing that.


chore: rename dictionary set and set add

I opened this pr instead of restoring file/class names in this previous pr.

Renamed dictionary and set operations names except DictionaryRemoveField, DictionaryRemoveFields,SetRemoveElement, and SetRemoveElements since they were already named that way.

Closes #39

@cprice404 @malandis
I'm not sure what is going on, but it again says I renamed files and classes names in a wrong way...
Am I missing something here regarding how to rename files/classes???

I think the renames are a false positive because the file contents are so similar.

ugh, that's annoying.  thanks Erika.


Bugfix: Inspector alignment on gateways

Blocked until test are fixed
Changes

Inspectors for all gateways are consistent
Added default names for event-based gateway & inclusive gateway

Video Capture
https://drive.google.com/open?id=1y1LLJ1u-1iTYRMY0MnujkY-Q836kVmyn
Inclusive Gateway Inspector - stand-alone modeler

Inclusive Gateway Inspector - spark modeler

Parallel Gateway Inspector - stand-alone modeler

Parallel Gateway Inspector - spark modeler

Fixes #375, #374

@velkymx can this be merged?

This is not correct. Gateways have different configurations depending on the type of gateway. The bug is about the UI not being consistent not about the content itself. The input boxes were different sizes.

@velkymx the input boxes for inclusive gateway were different sizes because the wider ones were not inside of the accordion. They are now inside of the accordion in this PR


settings

Issue type
[X ] Feature request
[ ] Bug report
[ ] Documentation

Environment

Python version:
Peering Manager version:

Description
Allow users to see the system settings, and edit them.

I don't want settings required to be exposed on a view.
Settings (configuration) are critical for Peering Manager and might need to restart the python workers if changed. So we will only support settings to be edited in the proper file.


Add missing options to JSON decoding config

Hello,
this PR adds expand_keys, document_id and ignore_decoding_error options for JSON decoding.
For completeness I've added ignore_decoding_error to templates/prospector.yml.erb, as this option was already available before version 7. The other two were added in 7.5 and 7.11 respectively, so I've added those to templates/input.yml.erb only.
These options exist with the same names in the ndjson-Parser for filestream inputs. While this PR does not fix #323, it shouldn't cause any additional issues in that regard, either.
If this makes it into a release soon, I'd be super happy, but no worries if not.
Cheers,
antiz

Thanks for submitting this - I just pushed this to the forge as v4.14.0.


Rider extension or rosylan analyser version?

I use rider 2023.3.6 due to new versions of rider leaking memory, is it possible to get this for it?

We don't have a rider extension unfortunately, but you can use this as a CLI tool to run on your binaries.

aww that's too bad. maybe sometime in the future you can port it to a rosylan analyzer


⚠ Bofrost.fr has degraded performance

In b76bbe8, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 885 ms

Resolved: Bofrost.fr performance has improved in bfeda8a after 6 minutes.


fix(core,scripts): Disable Circom optimizations

This seems to work better for some scenarios. Also delete old script.

we don't compile circuits in mopro anymore


wrong error - batch transcription failed with The recordings URI contains invalid data.

Describe the bug
wrong error message - in case that original file is stereo and IsDiarizationEnabled = true batch transcription is failed with error
The recordings URI contains invalid data.
To Reproduce
Steps to reproduce the behavior:
1.using default example https://github.com/Azure-Samples/cognitive-services-speech-sdk/tree/31abbe1e4b6e3a0bc7d60a72fd3802cb928654dc/samples/batch/csharp example
2.file https://batchrecordingstorage.file.core.windows.net/fileshare/rcd_2b6297790426000d_220c10de.tmp_stereo.wav?sp=rl&st=2021-12-05T17:00:12Z&se=2023-01-06T17:00:00Z&sv=2020-08-04&sig=zOFNnP1LZ9hyv2sx5Go6v8Lc3cnCoqimys6tM%2BWppho%3D&sr=f
Expected behavior
return actual error that file should be in mono format
Version of the Cognitive Services Speech SDK
v3
Platform, Operating System, and Programming Language

OS: Windows
Hardware - x64
Programming language: C#

Additional context
The recordings URI contains invalid data.

Thanks for reporting the issue. We will investigate.

I looked into the issue. Yes, the error message "The recordings URI contains invalid data" that is returned in the GET transcription response is not very clear for your case. Currently, as workaround, you can check the report.json file for detailed error messages for each audio in your request. You can get the location of report.json file via GET transcription files (https://eastus2.dev.cognitive.microsoft.com/docs/services/speech-to-text-api-v3-0/operations/GetTranscriptionFiles). In the report.json, the status of each audio of your request as well possible error messages are listed. For example, you will get the following error messages for your sample audio:
{
"successfulTranscriptionsCount": 0,
"failedTranscriptionsCount": 1,
"details": [
{
"source": "https://batchrecordingstorage.file.core.windows.net/fileshare/rcd_2b6297790426000d_220c10de.tmp_stereo.wav?sp=rl&st=2021-12-05T17:00:12Z&se=2023-01-06T17:00:00Z&sv=2020-08-04&sig=zOFNnP1LZ9hyv2sx5Go6v8Lc3cnCoqimys6tM%2BWppho%3D&sr=f",
"status": "Failed",
"errorMessage": "Reason BadChannelConfiguration, Details: Stereo audio is not supported when using diarization. (JobId 511bef28-38c3-4184-90ee-2d6924581da9).",
"errorKind": "BadChannelConfiguration"
}
]
}
I will forward your request for better error message to the team and we will provide a better error message in a future version.
Thanks,
Zhou

I am closing the issue. Please raise a new one if you have any questions.


Update an Iteration

Description
As a user, I can update an iteration for a space and change title and start and end dates.
Functional Acceptance Criteria

The user can select an iteration from a list of all iterations of the current space. The list order is undefined for this story.
The user can update an iteration from a dialog that opens when an iteration is selected from the list.
The user can change the title (alphanumeric value), the start date (date) and the end date (date).
It is not possible to update an iteration with an empty title.

Non-functional Acceptance Criteria

The "list/update iteration" view is easily accessible from anywhere in the system UI.

Dependencies

Userstory #409
Userstory #411
Userstory #412

Logic tied to the current date is generally not worth the effort. I should be able to set the start date to a date preceding today. Let's say I forgot to create an iteration for this month -- why are you having the system deny me creating it? A warning that I can turn off may be okay, but this shouldn't be a hard-coded rule. [e.g. QuickBooks warns me when I make accounting entries which are more than 6 months old -- just to be sure I didn't type the year wrong. But it does let me put these entries into the system.]

@qodfathr ok, updated the story.

Will there be a history/audit trail for updates made to the start/end dates?

Would this be part of the larger log/audit file?... I am not sure if this
would be something the user would want to see as part of the experience?...
On Mon, Oct 31, 2016 at 2:41 PM, Len DiMaggio<EMAIL_ADDRESS>wrote:

Will there be a history/audit trail for updates made to the start/end
dates?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/almighty/almighty-core/issues/410#issuecomment-257382239,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwqxexbPksgNBHqD6sP4NQInHanLQcks5q5jZDgaJpZM4Kid37
.

While I'm in favor of auditing almost everything, auditing changes to iteration dates strikes me as something that almost no one would care about. (Yes, I can come up with some use cases. But I believe they very rarely happen.) If we can capture this data, let's do so, but let's not work on any UX around it until we've got more data on usage (how often does it happen) and need (someone wants to review the data).

+1 on not auditing the Iteration dates right now.
On Wed, Nov 2, 2016 at 8:58 AM, Todd Mancini<EMAIL_ADDRESS>wrote:

While I'm in favor of auditing almost everything, auditing changes to
iteration dates strikes me as something that almost no one would care
about. (Yes, I can come up with some use cases. But I believe they very
rarely happen.) If we can capture this data, let's do so, but let's not
work on any UX around it until we've got more data on usage (how often does
it happen) and need (someone wants to review the data).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/almighty/almighty-core/issues/410#issuecomment-257856743,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwq29HNlnFhB33ZcDD1aufzIc0VGEmks5q6IjpgaJpZM4Kid37
.

@Mgranfie @qodfathr yes, not part here, because this has a much bigger scope. Logging/auditing is an epic of its own. There were talks in Westford about being able to roll the system back to any point in time, etc..this is much bigger than what can be done in this story.

@michaelkleinhenz right, a 'true, 100% rollback' would need something like this. Maybe a 'mostly true, 99% rollback' will suffice. :) Thanks for the reminder on this subtlety.

Important addition: we might need some way to select or view an iteration from a list of iterations. How are they ordered in that list? What iterations are displayed there? This is needed in the story.

Michael,
In the current designs we have a list of iterations, right now they are
listed by date, start date being the identifier.
Let me know if this makes sense.
Thanks,
Monica
On Tue, Nov 8, 2016 at 8:41 AM, Michael Kleinhenz<EMAIL_ADDRESS>wrote:

Important addition: we might need some way to select or view an iteration
from a list of iterations. How are they ordered in that list? What
iterations are displayed there? This is needed in the story.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/almighty/almighty-core/issues/410#issuecomment-259138912,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwq2x7Ete65n8Lcb9hfYtSyhkQMOQRks5q8HwmgaJpZM4Kid37
.

Since date are optionals sorting by date does not make sense IMO.
It should be an ordered sequenced list.

Proposing to go for alphabetical, until and even if we have dates...
On Tue, Nov 8, 2016 at 8:52 AM, Max Rydahl Andersen <
<EMAIL_ADDRESS>wrote:

Since date are optionals sorting by date does not make sense IMO.
It should be an ordered sequenced list.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/almighty/almighty-core/issues/410#issuecomment-259141516,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwq4zWkwsHcWQW4Y7-DAdtwHf4Zafkks5q8H67gaJpZM4Kid37
.

As alphabetical would only be a temporary solution until we defined something better, can't we just go for "unsorted" for now? Thats what we've done on the worklist..just leaving out any sorting and display the items as they are in the data(base).

Iterations are ordered. It is a list of data (actually, it's hierarchical -- remember, iteration is a path data type) -- and lists are, by definition, ordered (otherwise we'd call them a bag).
So if I type in
Iteration 1
Iteration B
Iteration III
then that's the order of the iterations. This is super-critical for the UX to have any degree of sanity.
As a lower priority feature, I should be able to drag/drop reorder and reparent them.
e.g.
Release 1
Sprint 1
Sprint 2
Release 2
Sprint X
Sprint Y
I should be able to drag Sprint X to somewhere else, such as:
Release 1
Sprint 1
Sprint 2
Sprint X
Release 2
Sprint Y

Todd,
Based on your examples, are we limiting the names of the Iterations and
Sprints to "Iteration #", "Sprint #" and "Release #" then?
This as a requirement. These are auto generated with a numeric appendage?
Thanks,
Monica
On Wed, Nov 9, 2016 at 11:15 AM, Todd Mancini<EMAIL_ADDRESS>wrote:

Iterations are ordered. It is a list of data (actually, it's
hierarchical -- remember, iteration is a path data type) -- and lists are,
by definition, ordered (otherwise we'd call them a bag).
So if I type in
Iteration 1
Iteration B
Iteration III
then that's the order of the iterations. This is super-critical for the UX
to have any degree of sanity.
As a lower priority feature, I should be able to drag/drop reorder and
reparent them.
e.g.
Release 1
Sprint 1
Sprint 2
Release 2
Sprint X
Sprint Y
I should be able to drag Sprint X to somewhere else, such as:
Release 1
Sprint 1
Sprint 2
Sprint X
Release 2
Sprint Y
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/almighty/almighty-core/issues/410#issuecomment-259454074,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwq-F0lHwB_hetEh_afHIjveNMARA4ks5q8fGRgaJpZM4Kid37
.

@Mgranfie No, they can have any name you want. No autogeneration of any kind. (Although we should consider some auto generation for the future. Often I will want "Sprint n, Sprint n+1, Sprint n+2..." auto generated for some value of n, likely also with dates (e.g., "every two weeks starting with jan 12, 2017").
But that's not for today. We can discuss in January.
The initial development methodology selection should be able to prepopulate the project with a list of initial recommended iterations. (e.g., the Scrum methodology might give you "Sprint 1," "Sprint 2," ... "Sprint 6" as a reasonable start. The user can then modify or delete these, of course.)

@joshuawilson @aslakknutsen @maxandersen @michaelkleinhenz  Wireframes for iterations: https://redhat.invisionapp.com/share/KA9CAYL7M

This issue was moved to fabric8io/fabric8-planner#647


WASM & Cloudflare Workers Support

Description of the feature
Support & Examples for WASM & Cloudflare Workers https://blog.cloudflare.com/workers-rust-sdk/
Code example (if possible)
It can be done the same way as lambda integration.

Since Cloudflare Workers are based on V8, maybe it won't be easy, but I'll try it later.


Format support in IDEs

I think it would be great to have a general syntax highlighting direction. As a naive user I don't know what format to choose in VSCode. This could be solved by giving a general syntax highlighting direction in the README or create a plugin for mainstream IDEs.
I assume that there is an existing format that is fundamentally compatible.

Not all people use VSCode, this maintainer for instance doesn't.  But patches from end users are of course welcome.


Search bar redirects to v3 docs instead of searching v2 docs.

Chrome Version 99.0.4844.51 (Official Build) (x86_64) Mac 11.6.1
https://user-images.githubusercontent.com/885196/158220367-87334c89-db01-4953-88f2-e11ff84a078f.mov

Hi there! This is a huge problem for me, I'm maintaining a library written in Vue2. Perusing the documentation often requires finding the same page, multiple times, until I find it the way that won't forward me. Any chance we can get auto-forwarding turned off, or have a larger window to opt-out before auto-forwarding?

Same issue as well, search is basically useless atm :/


Unable to add any new clients in recent versions (2.0+)

Describe the bug
New clients fail to install and work. Example client yaml:
$ cat client-test.yaml
apiVersion: vpn.example.com/v1alpha1
kind: WireguardPeer
metadata:
  name: test
  namespace: radnimax-vpn
spec:
  wireguardRef: "radnimax-vpn"

To Reproduce
Steps to reproduce the behavior:

apply new client yaml: kubectl apply -f client-test.yaml
run command to get peer information: kubectl -n radnimax-vpn get wireguardpeer test --template={{.status.config}} | bash
Note the following error is returned instead of the peer configuration:

bash: line 1: syntax error near unexpected token `newline'
bash: line 1: `<no value>'
Note: without piping to bash, the return is simply "<no value>"

Expected behavior
Should receive proper config info, which still happens with the existing clients already set up.
Additional context
Existing client configs are able to be retrieved.  It is only any new ones that are added now, that are not able to be retrieved.

This is still a problem on v2.0.26.

Hello,
What does kubectl -n radnimax-vpn get wireguardpeer test --template={{.status.config}}  return?

Hello,
What does kubectl -n radnimax-vpn get wireguardpeer test --template={{.status.config}}  return?

It just returns no value:
$ kubectl -n radnimax-vpn get wireguardpeer test --template={{.status.config}}

what about  kubectl -n radnimax-vpn describe wireguardpeer test

what about  kubectl -n radnimax-vpn describe wireguardpeer test

Sorry for the delay, been busy. Here is the result:
[xamindar@hp2530p-xam wireguard-operator]$ kubectl -n radnimax-vpn describe wireguardpeer test Name:         test Namespace:    radnimax-vpn Labels:       <none> Annotations:  <none> API Version:  vpn.example.com/v1alpha1 Kind:         WireguardPeer Metadata:   Creation Timestamp:  2024-04-20T06:31:52Z   Generation:          1   Resource Version:    381408287   UID:                 4f9de045-988d-493c-aad8-a5de4861aae7 Spec:   Wireguard Ref:  radnimax-vpn Events:           <none> [xamindar@hp2530p-xam wireguard-operator]$
I have tome to troubleshoot it now but I think I will just blow it away and redeploy it at this point.

Alright, so I removed it and my vpn "server/client" configs and redeployed. Now it isn't working at all. Applied release v2.0.30, then my server config in its own namespace just as I originally did. The only difference is updating the apiVersion to vpn.wireguard-operator.io/v1alpha1 as it's now listed on the readme page.
Now when I apply the client config, I just get nothing:
[xamindar@hp2530p-xam wireguard-operator]$ cat client-test.yaml  apiVersion: vpn.wireguard-operator.io/v1alpha1 kind: WireguardPeer metadata:   name: test   namespace: radnimax-vpn spec:   wireguardRef: "radnimax-vpn" [xamindar@hp2530p-xam wireguard-operator]$ kubectl apply -f client-test.yaml wireguardpeer.vpn.wireguard-operator.io/test created [xamindar@hp2530p-xam wireguard-operator]$ kubectl -n radnimax-vpn get wireguardpeer test --template={{.status.config}} Error from server (NotFound): the server could not find the requested resource (get wireguardpeers.vpn.example.com test) [xamindar@hp2530p-xam wireguard-operator]$

Hello,
I'm having the same issue, for me waiting did not solve it, I executed the commands as per the readme only adding the namespace to the wireguard resources, this is the state:

I tried with version 2.1.0 and 2.2.0 and same issue on both

Issue was a forever pending LoadBalancer Service type. changed server config to use NodePort and it solved the issue:
kind: Wireguard
metadata:
  name: "my-cool-vpn"
  namespace: wg-vpn
spec:
  serviceType: NodePort
  mtu: "1280"
  port: 30836


xss - Reflected Cross Site Scripting issue

How to reproduce

Navigate to the below URL.
http://wysibb.com/demo/
Click on “Insert image” button.
Enter this below payload in input field and click on “Save” button.
https://test.github.com/test/?">.jpg
Now Again click on "save” button.
Observe that an alert box is displayed in the browser which proves Reflected
Cross Site Scripting.

https://test.github.com/test/?"><iMg src=N onerror=alert(document.cookie)>.jpg

this is the code
.replace(/\</g,"<").replace(/\>/g,">").replace(/\{/g,"{").replace(/\}/g,"}");
but where to put it :)

To turn this into an actual XSS attack, you have to make the server accept and publish your bbcode ; so I'm not sure where WysiBB is concerned by this issue. Isn't the server-side parser + conversion to HTML that must be secure enough to detect such attacks? Unless you want to trick a user into copy/pasting your image link in the editor (but then you could also trick him into pasting javascript code in the browser console...)

https://test.github.com/test/?">.jpg

https://test.github.com/test/?">.jpg
https://test.github.com/test/?">.jpg


When is the next planned release?

I have noticed that turbo issue, when validation errors are not displayed in "set password" form, is fixed with: https://github.com/scambra/devise_invitable/commit/87228c1feefa0fea1d74f82fe7867111fddc7f91
This is great and is exactly what we need for our app!
Currently we are requiring devise_invitable via git in the gemfile and would like to move to regular releases.
When the next release is planned?
There is really no rush and I have set up a github notification for this. I just think that this will be very relevant for other stacks with this gem and hotwire.
Thanks for creating and maintaining this gem!

2.0.8 released

Amazing! Thanks a lot for such a quick response and release.


Change USK key type

A) I have the ATEM Television Studio HD and the ATEM Mini Pro and on both I can't change the
Inputs for the Down-Stream-Keyer.
For the Upstream-Keyer it works - on both devices.
B) Talking over the Upstream-Keyer, it would be very helpful if I could change the Keyer Funktion
(Luma, Chroma, Pattern, DVE)
For some Cases I have to change between the
Host-Camera 'Chroma-Keyer' and a PiP for the Presenter and the PowerPoint.
As a workaround I run first a Macro on the switcher to switch between the two.
I see if you implement Point B, wishes to change the PiP Size and Position will follow ;)
ATEM MiniPro 8.4, ATEM TSHD 8.1.1, Companion 2.1.0

+1 for that! I ended up doing it with macros.

On 9 20, 2020, at 1:42 PM, X21de<EMAIL_ADDRESS>wrote:
A) I have the ATEM Television Studio HD and the ATEM Mini Pro and on both I can't change the
Inputs for the Down-Stream-Keyer.
For the Upstream-Keyer it works - on both devices.
B) Talking over the Upstream-Keyer, it would be very helpful if I could change the Keyer Funktion
(Luma, Chroma, Pattern, DVE)
For some Cases I have to change between the
Host-Camera 'Chroma-Keyer' and a PiP for the Presenter and the PowerPoint.
As a workaround I run first a Macro on the switcher to switch between the two.
I see if you implement Point B, wishes to change the PiP Size and Position will follow ;)
ATEM MiniPro 8.4, ATEM TSHD 8.1.1, Companion 2.1.0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-bmd-atem/issues/82, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4KT65TVWP2VRQSNTGQVLDSGZLJTANCNFSM4RTZ6ZOA.

A) This is a known issue in 2.1.0 and is fixed in the 2.1.1 beta builds.
B) Yeah, this is not implemented yet

This is implemented and will be in the betas shortly


How to use OmniDB behind a proxy web server with Apache 2.4?

Hi everybody,
I’m struggling with implementing the OmniDB server behind a Apache 2.4 Webserver in a proxy configuration. Can somebody please deliver the needed httpd.conf code for it? The websocket proxying is breaking my neck. I’m using the newest release 2.16. I would like also to host it under the /omnidb endpoint. I’m using Ubuntu Linux. OmniDB is installed on a different server as the mentioned Apache Webserver.
Thank you kindly in advance!

Hi @TigerIcecold,
We are in the process of writing a fully updated doc, which will include these steps.
This part of the doc explains how OmniDB's ports work, and how to deploy with nginx:
https://omnidb.org/en/documentation-en/19-deploying-omnidb-server
We are documenting the steps to use with Apache too, but it is not ready.

I would like also to host it under the /omnidb endpoint.

Latest release (2.16.0) came with a new feature that allows to configure custom url paths, exactly
what you are looking for:
https://github.com/OmniDB/OmniDB/blob/master/OmniDB/omnidb.conf
The parameter path is used for that. If you have the following settings:
listening_address    = <IP_ADDRESS>
listening_port       = 8000
path = omnidb
you should access omnidb with the URL: http://<IP_ADDRESS>:8000/omnidb
The file omnidb.conf created once you run OmniDB for the first time. If you are running OmniDB as a service, using the service configured with the package's installation, OmniDB will use the file in /etc/omnidb.conf. If you running OmniDB manually, it will be created in ~/.omnidb/omnidb-server/omnidb.conf (home directory of the user running OmniDB).
Let me briefly explain how OmniDB's ports work:

listening_port: The port used to access OmniDB itself
websocket_port: Port used to serve OmniDB's websocket client connections
external_websocket_port: Port that will be used by the client's browser to connect to the websocket server.

With a custom path it should be much simpler to configure Apache and Nginx. If you have the following settings:
listening_address = <IP_ADDRESS>
listening_port = 8000
websocket_port = 25482
external_websocket_port = 443
path = omnidb
And you are accessing OmniDB with a secure connection, then you should configure Apache so that:

requests to domain/omnidb (port 443) are redirected to <IP_ADDRESS>:8000.
requests to domain/omnidb/ws and domain/omnidb/wss (443) are redirected to <IP_ADDRESS>:25482. Apache may require special config to proxy websocket requests.

Once doc is ready, I'll update this issue and close it.
Rafael.

Hi @rafaelthca,
thank you for your very detailed explanation and your hints for the correct configuration! I have now found an Apache 2.4 configuration, that seems to work!
This is my omnidb.conf config:
listening_address = <IP_ADDRESS>
listening_port = 8000
websocket_port = 25482
external_websocket_port = 80
path = omnidb

listening_address = <IP_ADDRESS> --> because my apache is an other VM (I know, I could enter here also the IP of that VM - that was for testing purposes).
external_websocket_port = 80 (my testing Apache VM is currently without SSL)
And here is my Ubuntu Apache 000-default.conf config:
<VirtualHost *:80>
	ServerName localhost
	ProxyRequests		Off
	ProxyVia		Off
	ProxyPreserveHost	On
	RewriteEngine		On

	<Proxy *>
		Require all granted
	</Proxy>

	ProxyPass	 "/omnidb/ws"	"ws://<IP_ADDRESS>:25482/omnidb/ws"
	ProxyPass	 "/omnidb/wss"	"wss://<IP_ADDRESS>:25482/omnidb/wss"

	ProxyPass	 /omnidb http://<IP_ADDRESS>:8000/omnidb
	ProxyPassReverse /omnidb http://<IP_ADDRESS>:8000/omnidb

	ProxyPass	 / ajp://<IP_ADDRESS>:8009/
	ProxyPassReverse / ajp://<IP_ADDRESS>:8009/

	ErrorLog  /var/log/apache2/ajp.error.log
	CustomLog /var/log/apache2/ajp.log combined
</VirtualHost>

And now the websocket port is successfully forwarded!

THANK YOU!!!

Hi @rafaelthca,
now I have an other issue. As long as I use HTTP only without SSL on my front web server, everything works fine:

But as soon as I activate SSL, the websocket port can't be reached!
The first attempt goes to the correct URL with the correct endpoint, but the calls gets an HTTP500 Error:

And the second attempt goes to the website URL, but with the internal websocket port, which is behind a firewall and not reachable from the outside. Again: The same works without SSL perfectly fine!

Apache Proxy config is like this (different IPs, but everithing elese is same):
	ProxyPass	 "/omnidb/ws"	"ws://<IP_ADDRESS>:25482/omnidb/ws"
	ProxyPass	 "/omnidb/wss"	"wss://<IP_ADDRESS>:25482/omnidb/wss"

	ProxyPass	 /omnidb http://<IP_ADDRESS>:8000/omnidb
	ProxyPassReverse /omnidb http://<IP_ADDRESS>:8000/omnidb

These mods are activated specifically for OmniDB proxying:
sudo a2enmod proxy
sudo a2enmod proxy_http
sudo a2enmod proxy_wstunnel

I'm hosting all this in a cloud, which can be compared with AWS.
What could be the reason?
Again: HTTP/80 works fine, HTTPS/443: WebSocket Port HTTP500 :(
Thank you kindly an advance for your help!

Addition to yesterday's issue:
Now the first attemtp seems to work fine: HTTP 200 response. But the second WSS attemt goes to a port, that is closed in the internet. Is that probably a bug? HTTPS is being handles completely by the front end web server. A end-to-end encryption from the OmniDB side is not necessary in that case, right?

So, the current issue is: Why is OmniDB trying to access a closed port? This port is only opened to the web server internally, but not to the outside network.

Hi,
I'm currently traveling and using cellphone, so apologies for not being able give a more complete response, will do so as soon as possible.
When OmniDB fails to connect using the configured external websocket port, it tries to connect to the internal one. The question is why the external attempt is failing.
When using OmniDB behind apache or nginx with ssl the recommendation is that you setup certificates on apache/nginx and configure OmniDB to not use SSL. Is that what you did? Perhaps there is an additional configuration missing on apache.
I'll take a look.

Here is the config I use with nginx:
server {
    listen 443 ssl;
    listen [::]:443 ssl;
    include snippets/ssl-omnidb.org.conf;
    include snippets/ssl-params.conf;
    server_name cloud.omnidb.org, <IP_ADDRESS>;
    client_max_body_size 75M;
    proxy_read_timeout 86400s;
    proxy_send_timeout 86400s;

    location /omnidb/wss {
      proxy_pass http://<IP_ADDRESS>:25890;
      proxy_set_header   X-Real-IP $remote_addr;
      proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header   X-Forwarded-Ssl https;
      proxy_set_header   X-Forwarded-Proto https;
      proxy_set_header   X-Forwarded-Port 443;
      proxy_set_header   Host $host;
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection "upgrade";
    }

    location / {
      proxy_pass http://<IP_ADDRESS>:10551;
      proxy_set_header   X-Real-IP $remote_addr;
      proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header   X-Forwarded-Ssl https;
      proxy_set_header   X-Forwarded-Proto https;
      proxy_set_header   X-Forwarded-Port 443;
      proxy_set_header   Host $host;
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection "upgrade";
    }
}

And omnidb.conf:
[webserver]
listening_address = <IP_ADDRESS>
listening_port = 10551
path = omnidb
websocket_port = 25890
external_websocket_port = 443
is_ssl = False

I will try with apache once I have time.
Rafael.

Another thing, can you try with chrome?

@rafaelthca
Thank you for you response! It is very kind of you, that you answer even while travelling =)
This is my OmniDB Conf file:
# OmniDB Server configuration file

[webserver]

# What address the webserver listens to, <IP_ADDRESS> listens to all addresses bound to the machine
listening_address    = <IP_ADDRESS>

# Webserver port, if port is in use another random port will be selected
listening_port       = 8000

# Websocket port, if port is in use another random port will be selected
websocket_port       = 25482

# External Websocket port, use this parameter if OmniDB isn't directly visible by the client
external_websocket_port = 443

# Security parameters
# is_ssl = True requires ssl_certificate_file and ssl_key_file parameters
# This is highly recommended to protect information
is_ssl               = False
ssl_certificate_file = /path/to/cert_file
ssl_key_file         = /path/to/key_file

# Trusted origins, use this parameter if OmniDB is configured with SSL and is being accessed by another domain
csrf_trusted_origins = origin1,origin2,origin3

# Url path to access OmniDB, default is empty
path = omnidb

[queryserver]

# Max number of threads that can used by each advanced object search request
thread_pool_max_workers = 2

# Number of seconds between each prompt password request. Default: 30 minutes
pwd_timeout_total = 1800

I'm using listening_address = <IP_ADDRESS> because my webservers are different machines and I'm using multiple webservers to test different configurations. I'm not using OmniDB and Apache on the same VM/machine.
Also I've checked this setting: is_ssl = False And my websocket experience with OmniDB is the following:
When I'm accessing OmniDB over the webserver over Port 80, then OmniDB tries to access its websocket over the ws:// instance.
But when I'm accessing OmniDB over the webserver over Port 443 (SSL), then OmniDB tries to use the wss:// instance to access its websocket.
Again: The omnidb.conf SSL setting is set like this: is_ssl = False
So I believe, that OmniDB ignores the is_ssl = False setting here, and as soon as the external weserver works with SSL, OmniDB tries to access the websocket over wss://
That's my experience here. Parhaps I'm wrong, but that's what I've seen. It is also possible, that my Apache is still not configured optimal, but then again: Why is OmniDB trying to use wss:// even if the is_ssl setting is set to False as soon, as I use SSL on my web server? (Which is a different machine!)
(In the meantime I'll experiment with the rewrite conditions on my Apache. My issue is, I'm unfortunately not very experienced with the apache proxying options)

Hi @rafaelthca
I think, I have found a better and a more stable solution for my issue:
With the help of the rewrite engine of the Apache webserver the websocket is proxied correctly with the HTTP response 101 (switching protocols). Thanks for that valuable hint!
Here is my Apache code snippet for OmniDB proxy config:
LoadModule rewrite_module modules/mod_rewrite.so

RewriteEngine     On

RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteCond %{HTTP:Connection} upgrade [NC]
RewriteRule .* "ws://<IP_ADDRESS>:25482%{REQUEST_URI}" [P]

ProxyPass        /omnidb http://<IP_ADDRESS>:8000/omnidb
ProxyPassReverse /omnidb http://<IP_ADDRESS>:8000/omnidb

This config is better, because here the request header is used to enforce to route the websocket requests to the websocket interface!
This works with HTTP and HTTPS on the web servers equally! Interesting is, that evene with this config the HTTPS web servers are routing the requests to wss:// - but here it works correctly with HTTP 101 response! Oo
I'll test that the next days and if I'll get issues with that I'll report :)
For now: THANKS AGAIN!!!


Use string_rtl gem.

Coverage remained the same at 100.0% when pulling 100ff30705e14c4cf9e12dec4184823b2bae3a6d on string_rtl_gem into ffb862ec38b5cdc646a2e8b2264e5408c37fda58 on master.


Error should always contain the video

The returned error should always contain the video object... this can be desired in the case of a fallback behaviour, when the direct video streaming is not available, but the app wants to show the thumb, title etc and probably open a webview

Can you pls marge?

Unfortunately, this doesn't fit with how the library works.

What do you mean by that?

Yup, but the AVPlayerViewController is recommended in favour of the old deprecated MP classes


x509: add ASN1_STRING_set() check result

Fixes #21492
Function v2i_issuer_sign_tool() (crypto\x509\v3_ist.c) uses function ASN1_STRING_set() to set the ASN1 string, but the result of ASN1_STRING_set() execution is not checked, although it may fail.
Added ASN1_STRING_set() check result.

This pull request is ready to merge

Merge, thanks for the contribution.


verifyIdToken does not seems to work

Describe the bug
When I pass wrong token like "aaa" for verifyIdToken method, I expected it to cause error but it seems it does not causes error. Instead of causing error, verifyIdToken seems to return infomration as follows:
 {
    id: null,
    email: null,
    emailVerified: false,
    phoneNumber: null,
    displayName: null,
    photoURL: null,
    claims: {},
    getIdToken: [Function (anonymous)],
    clientInitialized: false,
    firebaseUser: null,
    signOut: [Function (anonymous)],
    serialize: [Function: serialize]
  }

Versions
next-firebase-auth version: 1.0.0-canary.8
Firebase JS SDK: ^9.6.1
Next.js: 12.0.7
To Reproduce
Steps to reproduce the behavior:

run this example: https://github.com/gladly-team/next-firebase-auth/blob/main/example/pages/api/example.js#L20
pass wrong token like "aaa" and see it not to cause error.

Expected behavior
causes error to be able to catch properly when not authed.
Thanks.

This is expected behavior. See this config property for handling errors:
https://github.com/gladly-team/next-firebase-auth#onverifytokenerror


Red Headband - "'why I couldn't draw from the draw pile' if the draw pile was empty" will happen? If yes, fix description

Yes, it will happen.


Fix BigQueryInsertJobOperatorAsync bug

Sync version has changed and removed _job_id in operator which was used in our repo,
Code has been moved to hooks with certain changes.
Implement the code change needed for it in our repo

closes #470

Let's test in astro cloud after merging this.

We should also be able to test this locally with the latest version of the provider.


Dencun readiness - pin Lighthouse image tag in base Docker Compose setup

Small tweak to the Docker Compose file, pinning Lighthouse to version 5.0.0. The upstream Lighthouse Docker hub repo does not update the latest tag whenever new images are pushed, thus the Docker Compose yaml (implicitly pulling latest due to missing a pin) pulls a very old version of Lighthouse.
All lighthouse beacon nodes need to be updated to a minimum of 5.0.0 to be compatible with the upcoming Dencun release.
More info here: https://github.com/sigp/lighthouse/releases/tag/v5.0.0. TL;DR:

All Lighthouse Beacon Nodes and Validator Clients must be upgraded to a v5.x.x release to ensure they follow the correct chain.

As it's my first PR to this repo, keeping it very light. We've modified these base Docker Compose files in other ways internally, but this seems like a critical fix that should be included as a sane default in the base files before the imminent Dencun upgrade.

This PR definitely would work as described, just wanted to clarify before approving though- @zakisaad what image do you get when you pull down sigp/lighthouse:latest? You mentioned its very old but I'm seeing a new latest tag pushed at the exact same time at the 5.0.0-modern tag, if their latest on dockerhub is incorrect then we can give the lighthouse folks a heads up on that.

Hey @rswanson - I've just checked and you're right, the latest tag is indeed up to date (i.e. pulls down v5.0.0). It may have been that the latest tag went stale and wasn't updated on one of our previously configured machines.

Looks like a (related/variant?) of this issue hit Blast (L2) today as Dencun rolled out: https://twitter.com/Blast_L2/status/1767924021872455902
Their fix: https://github.com/blast-io/deployment/commit/66daab7abcf2d254166bf55731fd3d48fb8cf375
This is an option (:latest + always pull), but I feel that pinning specific versions is probably more prudent for stability. Backward incompatible changes/regressions could have unfavourable effects on a Reth node if a resync is required (downtime for x period).

Small tweak to the Docker Compose file, pinning Lighthouse to version 5.0.0. The upstream Lighthouse Docker hub repo does not update the latest tag whenever new images are pushed, thus the Docker Compose yaml (implicitly pulling latest due to missing a pin) pulls a very old version of Lighthouse.
All lighthouse beacon nodes need to be updated to a minimum of 5.0.0 to be compatible with the upcoming Dencun release.
More info here: https://github.com/sigp/lighthouse/releases/tag/v5.0.0. TL;DR:

All Lighthouse Beacon Nodes and Validator Clients must be upgraded to a v5.x.x release to ensure they follow the correct chain.

As it's my first PR to this repo, keeping it very light. We've modified these base Docker Compose files in other ways internally, but this seems like a critical fix that should be included as a sane default in the base files before the imminent Dencun upgrade.

Thanks to your issue, and it really helps a lot.


Don't use the .NET out byref marshaling for the return buffer parameter for DllImports

I think this is an artifact from before trampolines were created to hide return buffer semantics for static imports. (It was brought over from the prototype in c79bb2bc009e6f450460f14c4b227e7c0d0bbc68) There's no reason to use an out byref here since the trampoline is generated code and there's no sense in making it friendly.
The .NET Runtime is not smart enough to use a simple pointer in its place, so doing this is causing it to generate and call an unnecessary IL stub which has a (very very minor) negative performance impact.

The performance impact is quantified in AresBenchmarks.Interop.SimpleCall (which is not published but is reproduced below), with the following results:

BenchmarkDotNet=v0.12.1, OS=Windows 10.0.19043
Intel Core i7-4770 CPU 3.40GHz (Haswell), 1 CPU, 8 logical and 4 physical cores
.NET Core SDK=6.0.100-preview.5.21302.13
  [Host]     : .NET Core 5.0.7 (CoreCLR 5.0.721.25508, CoreFX 5.0.721.25508), X64 RyuJIT
  DefaultJob : .NET Core 5.0.7 (CoreCLR 5.0.721.25508, CoreFX 5.0.721.25508), X64 RyuJIT

Method
Mean
Error
StdDev
Code Size
Gen 0
Gen 1
Gen 2
Allocated

Unsafe
6.744 ns
0.1656 ns
0.1626 ns
147 B
-
-
-
-

UnsafeNoGC
1.855 ns
0.0517 ns
0.0458 ns
50 B
-
-
-
-

OutRef
8.713 ns
0.1850 ns
0.1640 ns
28 B
-
-
-
-

OutRefNoGC
3.136 ns
0.0963 ns
0.1442 ns
28 B
-
-
-
-

More details: (Click to expand)

SimpleCall.cs
using BenchmarkDotNet.Attributes;
using System.Runtime.InteropServices;

namespace AresBenchmarks.Interop
{
    public unsafe class SimpleCall
    {
        private const string DllName = "AresBenchmarks.Native.dll";
        private const string EntryPoint = "WriteOut";

        [DllImport(DllName, EntryPoint = EntryPoint, ExactSpelling = true)]
        private static extern void WriteOut_Unsafe(int* x);

        [DllImport(DllName, EntryPoint = EntryPoint, ExactSpelling = true)]
        private static extern void WriteOut_OutRef(out int x);

        [SuppressGCTransition]
        [DllImport(DllName, EntryPoint = EntryPoint, ExactSpelling = true)]
        private static extern void WriteOut_UnsafeNoGC(int* x);

        [SuppressGCTransition]
        [DllImport(DllName, EntryPoint = EntryPoint, ExactSpelling = true)]
        private static extern void WriteOut_OutRefNoGC(out int x);

        [Benchmark]
        public int Unsafe()
        {
            int result;
            WriteOut_Unsafe(&result);
            return result;
        }

        [Benchmark]
        public int UnsafeNoGC()
        {
            int result;
            WriteOut_UnsafeNoGC(&result);
            return result;
        }

        [Benchmark]
        public int OutRef()
        {
            int result;
            WriteOut_OutRef(out result);
            return result;
        }

        [Benchmark]
        public int OutRefNoGC()
        {
            int result;
            WriteOut_OutRefNoGC(out result);
            return result;
        }
    }
}

AresBenchmarks.cpp
extern"C" __declspec(dllexport) void WriteOut(int* x)
{
    *x = 3226;
}

Disassembly Report
.NET Core 5.0.7 (CoreCLR 5.0.721.25508, CoreFX 5.0.721.25508), X64 RyuJIT
; AresBenchmarks.Interop.SimpleCall.Unsafe()
       push      rbp
       push      r15
       push      r14
       push      r13
       push      r12
       push      rdi
       push      rsi
       push      rbx
       sub       rsp,78
       lea       rbp,[rsp+0B0]
       lea       rcx,[rbp+0FF80]
       mov       rdx,r10
       call      CORINFO_HELP_INIT_PINVOKE_FRAME
       mov       rsi,rax
       mov       rcx,rsp
       mov       [rbp+0FFA0],rcx
       mov       rcx,rbp
       mov       [rbp+0FFB0],rcx
;             WriteOut_Unsafe(&result);
;             ^^^^^^^^^^^^^^^^^^^^^^^^^
       lea       rcx,[rbp+0FFC0]
       mov       rax,offset MD_AresBenchmarks.Interop.SimpleCall.WriteOut_Unsafe(Int32*)
       mov       [rbp+0FF90],rax
       lea       rax,[M00_L00]
       mov       [rbp+0FFA8],rax
       lea       rax,[rbp+0FF80]
       mov       [rsi+10],rax
       mov       byte ptr [rsi+0C],0
       call      qword ptr [7FFBEE16A818]
M00_L00:
       mov       byte ptr [rsi+0C],1
       cmp       dword ptr [7FFBEE16C0CC],0
       je        short M00_L01
       call      qword ptr [7FFBEE16E368]
M00_L01:
       mov       rax,[rbp+0FF88]
       mov       [rsi+10],rax
;             return result;
;             ^^^^^^^^^^^^^^
       mov       eax,[rbp+0FFC0]
       lea       rsp,[rbp+0FFC8]
       pop       rbx
       pop       rsi
       pop       rdi
       pop       r12
       pop       r13
       pop       r14
       pop       r15
       pop       rbp
       ret
; Total bytes of code 147

.NET Core 5.0.7 (CoreCLR 5.0.721.25508, CoreFX 5.0.721.25508), X64 RyuJIT
; AresBenchmarks.Interop.SimpleCall.UnsafeNoGC()
       push      rbp
       sub       rsp,30
       lea       rbp,[rsp+30]
;             WriteOut_UnsafeNoGC(&result);
;             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
       lea       rcx,[rbp+0FFF8]
       call      00007FFBEDF58808
       mov       rax,7FFC4DDFC0CC
       cmp       dword ptr [rax],0
       jne       short M00_L01
;             return result;
;             ^^^^^^^^^^^^^^
M00_L00:
       mov       eax,[rbp+0FFF8]
       lea       rsp,[rbp]
       pop       rbp
       ret
M00_L01:
       call      CORINFO_HELP_POLL_GC
       jmp       short M00_L00
; Total bytes of code 50

.NET Core 5.0.7 (CoreCLR 5.0.721.25508, CoreFX 5.0.721.25508), X64 RyuJIT
; AresBenchmarks.Interop.SimpleCall.OutRef()
       push      rbp
       sub       rsp,30
       lea       rbp,[rsp+30]
;             WriteOut_OutRef(out result);
;             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
       lea       rcx,[rbp+0FFF8]
       call      AresBenchmarks.Interop.SimpleCall.WriteOut_OutRef(Int32 ByRef)
;             return result;
;             ^^^^^^^^^^^^^^
       mov       eax,[rbp+0FFF8]
       lea       rsp,[rbp]
       pop       rbp
       ret
; Total bytes of code 28

PInvoke method
AresBenchmarks.Interop.SimpleCall.WriteOut_OutRef(Int32 ByRef)
.NET Core 5.0.7 (CoreCLR 5.0.721.25508, CoreFX 5.0.721.25508), X64 RyuJIT
; AresBenchmarks.Interop.SimpleCall.OutRefNoGC()
       push      rbp
       sub       rsp,30
       lea       rbp,[rsp+30]
;             WriteOut_OutRefNoGC(out result);
;             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
       lea       rcx,[rbp+0FFF8]
       call      AresBenchmarks.Interop.SimpleCall.WriteOut_OutRefNoGC(Int32 ByRef)
;             return result;
;             ^^^^^^^^^^^^^^
       mov       eax,[rbp+0FFF8]
       lea       rsp,[rbp]
       pop       rbp
       ret
; Total bytes of code 28

PInvoke method
AresBenchmarks.Interop.SimpleCall.WriteOut_OutRefNoGC(Int32 ByRef)

The native portion of the benchmark was built using whatever CMake 3.18.4 does as default for release builds for Visual Studio 2019.

Turns out virtual methods used out byrefs at one point too, but I removed it while fixing https://github.com/InfectedLibraries/Biohazrd/issues/142 because it was painful and annoying in that context.


converting to python3

Apart from the few comments I made the code looks good. I'll manually test it later, but apart from testing this looks fine to merge.

Closed, we'll use #153. Thank you for your contribution.


As a cif user, I want to see the list of existing projects, so that I can find a project of interest

Description:
As a project coordinator, I want to be able to see the list of existing projects, so that I can find a project of interest.
The table filtering, sorting and pagination will be added in #64
The table components developed for CIIP should be reused (and adapted to move away from bootstrap)
Acceptance Criteria:
Given that I am logged in as a cif_internal or cif_admin user,
When I go to the /cif/projects page
Then I see a table displaying the existing projects
Given that a project was created
When it is displayed in the projects table
Then I can see the following project information:

Project Name
Project Operator's trade name
Project RFP Id
Project Status
List of assigned project managers (<lastName>, <firstName> with each manager on a separate line)
Total Funding Request
A button to view the project

Given that a project is displayed in the table
When I click on the button to view the project
Then I am redirected to a /cif/project/[projectRelayId] page
Given that a project is displayed in the table
When the project name, trade name, or project manager length exceeds Xpx (tbd)
Then it should wrap on a new line
Given that a project is displayed in the table
When the project status is displayed
Then it should have a fixed width
Development Checklist:

[x] Meets the DOD

Personas:

Program Development Team
Operations Team
Tech Team

Notes:

Current wireframe before CIF feedback:

Wireframe after CIF feedback:

Notes:

Top Right: User's logged in name from GAL with dropdown to Log out. Later versions perhaps could have a profile and preferences selection (TBD)

Bootstrap messaging above the list title, for system alerts. Potential use later on for user status messages (TBD).

Trade Name: Is an alias that the user can assign to the often much longer Legal Name Proponent.

RFP ID: Using same format as what CIF is currently using. Ideally, it could be less cryptic (ie. substituting 'EP' instead of '02' for the Stream. Seeing two letters for the Type would be useful as well).

Status: Bootstrap pill-badge. Options: In Progress, Measurement, Changes Requested. Options awaiting verification from CIF users.

Assigned: MVP is to show all name assigned. Future versions are hoping for showing just the items the logged in user is assigned to (Matthieu suggested a URL with applied filters could be bookmarked by users to jump to a filtered list)

View Attachment: Jumps to the Project Details > Attachments tab. A request was for a list of attachments that are sortable by date and kind.

View Notes: Jumps to the Project Details > Notes tab. MVP is that notes from emails and phone call outcomes requested to be recorded with a flag option to show on CIF Projects List so others will know to check the notes. Any user can remove the flag, signifying the issue has been dealt with. Nice to haves later on TBD.

Next Report Due: YYYY-MM-DD (Type). Each project has quarterly, annual and milestone dates. Request was for showing the next soonest date and its type.

Actions: Apply for actioning all filters. View for showing Default tab of a Project's details. Tabs still TBD from next co-design session.

Bottom of table on left: Pager to show number of items per page (10, 20 [default], 50, All).

Footer links TBD. Taken from CIIP for now.

Bottom Right: Help link similar to CIIP to redirect users to help documentation or contact CAS or GGIRCS team as appropriate.

I think we should also add a dropdown above the table to select the Reporting Year, as we have in CIIP. If devs are in agreement, I'll update the wireframe above to reflect that.

Hey team! Please add your planning poker estimate with ZenHub @dleard @pbastia

Adding applicable Personas to the ticket
Program Development Team - CIF Persona
Operations Team - Persona
Tech Team - CIF Persona

Thank you @matthieu-foucault ! This project lists looks great! I have a couple of questions:

Assigned To: is this the same as Project Manager or something different? When I created a new project and assigned a project manager, the "assigned to" displayed the J. Doeloremipsum, J. Doe".
Next Report Due: I don't believe we have this field accounted for in v1 for project creation (it doesn't look like it is in the wireframe either)?

Assigned To: Given that we will be updating the managers form soon, I opted to just hardcoding a value in the meantime. This will have to be fixed in #133, and could be renamed to "Project Managers"
Next Report Due: We can definitely remove that column given that we won't have that information in v1


tests: remove dependencies on unnecessary Invenio-* packages

It would make package release process easier.

[ ] move record_file_factory and file_download_ui to invenio_records_files (cc @lnielsen @nharraud @tiborsimko)

I don't see any issue with that.
It seems that the only change which this would require would be to change the config:
RECORDS_UI_ENDPOINTS = dict(
            recid=dict(
                # ...
                route='/records/<pid_value/files/<filename>',
                view_imp='invenio_files_rest.views.file_download_ui',
                record_class='invenio_records_files.api:Record',
            )
        )

Changed with
- view_imp='invenio_files_rest.views.file_download_ui',
+ view_imp='invenio_records_files.views.file_download_ui',

Do we need to keep record_file_factory at all? It seems that it is only used by file_download_ui .
In case somebody wants to use a different record_file_factory they can at the same time provide their own file UI endpoint as it means that there is probably not a 1 record -> 1 bucket relation anymore.

👍
Would make Files-REST more clean. @nharraud I would still keep record_file_factory (which is anyway already located in Records-Files).

@lnielsen I meant remove it from the ext.py file, not removing the function which is in invenio-records-files.

[ ] invenio-access - used in permissions.py - named tuple + flask_security.Permission when Invenio-Access is not installed
[ ] invenio-accounts easy to remove after Invenio-Access is out

@lnielsen after our discussion I believe this one can be closed, the removal of invenio-access is not easy or feasible.


Enable text selection on S3 buttons

Before:

After:

Thank you for this.
This is fine for now but I think the real solution would be to decouple the path from the button. We could show the path with a copy button, and next to it a button to open the path in the AWS console. It's ok, we can do this in a separate PR.

I consulted a customer's opinion, being able to copy text naturally is preferred over a separate button.
Also when we say path, what does it refer to? Is it the s3:// path or https:// path?


Independent Value Ranges for Positive and Negative Regions to Prevent Distortions

Hello, I believe the value ranges in the positive and negative regions of the chart should be independent of each other; otherwise, distortions occur. To explain this with a few examples:
For example, in this data, the values increase by 8, 8 and decrease by 8, 8. However, I want the values in the negative part of the chart to decrease by a different amount.
So, I want the chart to have 5 sections in the positive area and 2 sections in the negative area. I set the noOfSections prop to 5 and the noOfSectionsBelowXAxis prop to 2, but this causes my chart to look distorted.
For this reason, I believe the interval values in the positive and negative areas should be independent of each other.
My example :
<BarChart
height={160}
activeOpacity={0.9}
focusBarOnPress={true}
data={[
{ label: 'AAA', value: 30 },
{ label: 'BBB', value: 20 },
{ label: 'CCC', value: 10 },
{ label: 'DDD', value: -90 },
]}
adjustToWidth={true}
noOfSections={5}
noOfSectionsBelowXAxis={2}
autoShiftLabels
/>
  Screenshot

Hi @dogankablan 👋
Thanks for requesting this feature. This is now supported from version 1.4.15 onwards 🎉
We can now use the props-

negativeStepValue
negativeStepHeight
to independently control the value and height steps/sections in the Y axis for negative values.

Please use the latest version of the library.