Some questions about the code

About interpolation update on X
https://github.com/argenycw/ILA-DA/blob/c7df8ddaad3063d4ae4a722e42f4ee935fa4d4ea/attack.py#L246

x_adv_if is obtained by adversarial image without data augmentation. It is inconsistent with the others. According to the paper, I think x_adv_mid and x_mid also should not use data aug?

About attack on cifar10

https://github.com/argenycw/ILA-DA/blob/c7df8ddaad3063d4ae4a722e42f4ee935fa4d4ea/attack_cifar.py#L219
the rev_update seems always be False.
Is this technique not effective on CIFAR10 dataset?

Thank you for the questions.

About interpolation update on X
x_adv_if is computed from img, which is obtained from the last image update (i.e. $x''$)

https://github.com/argenycw/ILA-DA/blob/c7df8ddaad3063d4ae4a722e42f4ee935fa4d4ea/attack.py#L236-L237
In Algorithm 1, we can see $\lambda$ is computed after an effective update of $x''$. Here $\Delta~y_l''$ no longer takes the input $x''$ (which is from the last iteration), but the newly updated $x''$. Since attack interpolation aims to strengthen $x'$ (attack_img), it is performed AFTER the update of $img$. The variable name x_adv_if means "if we update the attack, what are the intermediate features?" (Not a good name though I admit)

In short, img does not indicate the augmented version of $x''$, but the updated version (via backprop) of $x''$ in the same iteration.

About attack on cifar10
The whole line should be removed. That should be an error that we "conveniently" added when we conducted the study internally. The effectiveness of reverse update in CIFAR-10 is similar to that of ImageNet, where usually w/ is better but occasionally wo/ can be better.
Sorry for the confusion. We will commit and push a new version soon.

In Algorithm 1, when calculating $\delta y''_l$, the data augmentation shold be applied to $x''$. But the data augmentation proess  seems missed? In other words, the intermediate features are obtained by $T_z(x'')$ not $x''$
https://github.com/argenycw/ILA-DA/blob/c7df8ddaad3063d4ae4a722e42f4ee935fa4d4ea/attack.py#L248

I see what you mean. After updating $x''$, you suggest applying another augmentation to form $T(x'')$ before using it to compute the norm in the feature space. This can promote both the alignments in the image space and the feature space.
Indeed the original attack interpolation only focuses on using the updated $x''$, without further data augmentation. I believe your suggestion would make better coherence between the data augmentation and attack interpolation.
In terms of implementation, we can first define a new augmentation, by changing the original line 219-220
https://github.com/argenycw/ILA-DA/blob/c7df8ddaad3063d4ae4a722e42f4ee935fa4d4ea/attack.py#L219-L220
into
t_aug = T.Compose([op])
x_aug = sum(w * t_aug(x_combined) if i == aug_id else w for i, (w, op) in enumerate(zip(gp, aug_list)))

then we change
https://github.com/argenycw/ILA-DA/blob/c7df8ddaad3063d4ae4a722e42f4ee935fa4d4ea/attack.py#L246
into
x_adv_if = ila_forw_by_models(model, model_type, t_aug(img), ila_layer)

Thank you for pointing out the potential improvements. In short, the result reported in the paper is the current version but I do agree your suggestion makes more sense and will potentially improve the attack. To let the readers reproduce the reported results, I might not change the master branch in a short period of time. But it will definitely be adapted in future updates.

okay, thanks for your reply!


Unable to count committers from some repos on Bitbucket - report incomplete because of undefined author.user object

While trying to build a report of our entire Bitbucket workspace I encounter this bug on some repos, rendering the report incomplete.
{
    "error": {
        "message": "Cannot read properties of undefined (reading 'nickname')",
        "stack": "TypeError: Cannot read properties of undefined (reading 'nickname')\n
         at BitbucketRunner.aggregateCommitContributors (/home/portfolio/.nvm/versions/node/v20.12.0/lib/node_modules/@paloaltonetworks/redshirts/dist/vcs/bitbucket/bitbucket-runner.js:18:39)\n
         at BitbucketRunner.processRepo (/home/portfolio/.nvm/versions/node/v20.12.0/lib/node_modules/@paloaltonetworks/redshirts/dist/common/base-runner.js:72:22)\n
         at async Task.task (/home/portfolio/.nvm/versions/node/v20.12.0/lib/node_modules/@paloaltonetworks/redshirts/dist/common/base-runner.js:45:25)"
    }
}

From what I can tell there is a problem with this block:
            const newCommit = {
                username: author.user.nickname,
                email: email || author.raw,
                commitDate: date,
            };

It seems you're referencing the nickname property, but author.user is undefined, leading to this exception. Catching this error and outputting author.raw to the debug log seems wise, and possibly adding a list of unrecognized/ignored authors to the output in some way would be helpful.
Application details:
2024-06-07T08:02:57.090Z [debug]: Environment details:
2024-06-07T08:02:57.092Z [debug]: Redshirts version: 0.6.0
2024-06-07T08:02:57.092Z [debug]: Node version: v20.12.0
2024-06-07T08:02:57.092Z [debug]: OS: Linux - linux - 5.15.0-107-generic
2024-06-07T08:02:57.092Z [debug]: CPU arch: x64
2024-06-07T08:02:57.092Z [debug]: Command args:
/home/portfolio/.nvm/versions/node/v20.12.0/bin/node
/home/portfolio/.nvm/versions/node/v20.12.0/bin/redshirts

For reference, one of the git commit author lines in question that most likely triggered this bug had just this value in it: FluxCD <>
So there was no email to extract.

@mikeurbanski1 @kartikp10 I noticed it's a while since there was any movement in this repo. Just hoping this bug won't be lost in the void, since it's being used to count our credit usage in Prisma Cloud. It's quite hard for us to reduce the usage when we don't know which of our developers are counted double because they don't consistently use a single email for their commit author value.


Card header 1px width error.

Windows 10
Google Chrome 71
https://codepen.io/anon/pen/aXYYQK
1px flickering between header and border while resizing window - I think it's rounding issue

Don't think there's anything we can do here—the browser is misrendering on a half pixel or so, creating the visible gap you're seeing. No good way around that unless we're redoing how we build the component, which isn't likely to happy. Sorry!


Fixes #5 deprecated methods

Fixes issue described in #5
Fixes error:

DeprecationError: Deprecated on 2023-09-11: `stub.app` is deprecated: use e.g. `stub.obj` instead of `stub.app.obj`
        if you need to access objects on the running app.

Thanks!!


Corrected to not erroneously mention email as being required.

Email field isn't required.

Merged in 841a87785a78cc37362a66856025bae2f7ba633c. Thanks!


Incompatible with TrajectoryOptimization

Hey!
Just tried adding TrajectoryOptimization, building TrajectoryOptimization, and then adding RobotZoo. I ran into conflicting requirements:
(v1.3) pkg> add RobotZoo   Updating registry at ~/.julia/registries/General  Updating git-repohttps://github.com/JuliaRegistries/General.git`
Resolving package versions...
ERROR: Unsatisfiable requirements detected for package Rotations [6038ab10]:
Rotations [6038ab10] log:
├─possible versions are: [0.7.2, 0.8.0, 0.9.0-0.9.2, 0.10.0, 0.11.0-0.11.1, 0.12.0-0.12.1, 0.13.0, 1.0.0-1.0.1] or uninstalled
├─restricted by compatibility requirements with TrajectoryOptimization [c79d492b] to versions: 0.13.0
│ └─TrajectoryOptimization [c79d492b] log:
│   ├─possible versions are: [0.0.1, 0.1.0-0.1.2, 0.2.0] or uninstalled
│   └─restricted to versions 0.2.0 by an explicit requirement, leaving only versions 0.2.0
└─restricted by compatibility requirements with RobotZoo [74be38bb] to versions: 1.0.0-1.0.1 — no versions left
└─RobotZoo [74be38bb] log:
├─possible versions are: 0.1.0 or uninstalled
└─restricted to versions * by an explicit requirement, leaving only versions 0.1.0`
I'm running Julia 1.3 on Ubuntu 16.04.
Let me know if I can provide any additional information. Thanks!

Yes, not all the latest versions are fully registered yet. I just released the newest version of TrajOpt (0.3.0) this morning. RobotDynamics should be good to go, and ALTRO should be registered soon.


fix: Gitpod Remote Development Revamp

Describe the changes you have made in this PR -

Added Redis APT Repository to .gitpod.Dockerfile to use the latest redis version always
Update extensions of gitpod.yml to use open-vsx registry as Microsoft Terms & Policy does not allow to use their marketplace to fetch extensions outside of official VSCode. Detailed about this issue
Added VSIX files for ruby-rubocop-revived and vscode-rdbg as these two extensions are not published yet in open-vsx registry
Added vscode settings for use rvm as package manager [required by ruby debugger extension]

Overall Imporvement

Gitpod is fixed [previously failed due to lower version of redis]
Gitpod extensions are working
Ruby debugger working fine
Solargraph extension is working fine

Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

Added VSIX files for ruby-rubocop-revived and vscode-rdbg as these two extensions are not published yet in open-vsx registry

Could you create issues on the corresponding repositories to encourage them to publish to open vsix ? Skip them from this PR for now

Added VSIX files for ruby-rubocop-revived and vscode-rdbg as these two extensions are not published yet in open-vsx registry

Could you create issues on the corresponding repositories to encourage them to publish to open vsix ? Skip them from this PR for now

Yup, I am removing the extensions and will raise issues in the repositories.


Rework Norm to use associated type

This one builds on my previous PR, needed to make ncollide work in 1.0.0.beta4

No need to pull this in yet, it seems there's a whole lot more to it than just Norm.

Yes, ncollide requires you to use associated types almost everywhere they should be on nalgebra. You may want to get some inspiration from nalgebra's associated_types branch (which ICEs at the moment, and I could not manage to find exactly which piece of code causes this bug).

This is a very old PR and Norm now uses associated types, so I can close this.
Regarding other traits, it might be worth it to wait and see if we end up integrating brendanzab/algebra eventually.


New keyboard shortcut for new Group chat

cc @Beamanator
Details
OS specific shortcut using libs/getOperatingSystem
To open new group chat.
Command + shift + K for MacOS
Control + shift + K for Windows/Linux.
To not allow extra key modifiers being pressed
const extraModifiers = _.difference(['shift', 'control', 'alt', 'meta'], callback.modifiers);
And then return early if they're being pressed.
Subscribe K to open new group chat.
On subscribing the key K
KeyboardShortcut.subscribe('K', () => {
    Navigation.navigate(ROUTES.NEW_GROUP);
}, ['control', 'shift'], true);

Contains of eventCallbacks are shown below. Which is why I loop over it.

I also changed shortcut for search on Windows,
from Win + K to Control + K as per the discussion on Slack.
Fixed Issues

#3349
Tests / QA

Login

On Windows/ Linux, press Cltr + Shift + K to give focus to new group chat.
On MacOS, press Command + Shift + K to give focus to new group chat.

Tested On
Don't have a Mac to test Desktop app.

[x] Web Windows
[ ]  Web MacOS
[ ] Desktop

Not applicable (Mobile Web, iOS, Android)
Screenshots

Web

https://user-images.githubusercontent.com/29673073/123422380-caf18980-d5c6-11eb-8d13-a51ac4dd6fbc.mp4
Desktop

Don't have a mac :)

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging in version: 1.0.74-1🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Turn off automatic open for both dev server and storybook

Need to turn off auto browser functionality if inside docker
# --ci for storybook

Honestly, I have to restart storybook so often to clear the test file cache that I would love to kill this everywhere. As long as the final output on start prints the port when using localhost, I think we'd be fine.

should be easy to configure but yeah I can just make it always off.

Fixed here: https://github.com/pixeloven/pixeloven/pull/31


AlecAivazis/survey is archived

https://github.com/AlecAivazis/survey has been archived and won't received updates in the future.
It is used in https://github.com/cli/go-gh/blob/25db6b99518c88e03f71dbe9e58397c4cfb62caf/pkg/prompter/prompter.go#L10
It should probably be moved to another library.

Worth leaving this open since it's also relevant for extensions but this is tracked by https://github.com/cli/cli/issues/8084

--Pu/

[t](url)


Array of FileInfo objects back onSuccess of fileGroup upload

Currently, what's returned when uploading multiple files isn't actually a fileInfo object.  Instead, what's returned is a truncated object sort of based on what would be returned for single file uploads.
What would be useful, so that users don't have to separately retrieve the individual objects in order to do things like show a more robust preview option in javascript, is to return an array of fileInfo objects for each of the files in the group.  I suspect it's trivial to do this inside the react library itself as the network call to /group already returns this info.

Hi @thongly, thanks for the suggestion! Using the Dialog API, you can get an array of file objects from the widget and then get information about each object. Here's how you can do this
<Widget
    publicKey="demopublickey"
    onDialogOpen={(dialog) => {
      // fires when a user closes the widget's dialog (clicks Done)
      dialog.done(async (group) => {
        // get an array of file instances and fileInfo objects
        const fileInfos = await Promise.all(group.files());
        console.log(fileInfos);
      });
    }}
    multiple
  />

We'll definitely consider simplifying this in the new uploader we're working on.

yes thanks!  that's how i'm doing it in the meantime


Proposed 2.0.0-rc1

High-Level Overview of Change
The base branch is release because all releases (including betas) go in release.
Context of Change
When finalized, the next stable release of rippled is expected to be the last one for 2023. The major version is bumped due to:

General availability of api_version 2 (expected).

This api_version is not available yet (except in beta, requiring a configuration change), but it will be in the next release.

New server_definitions method.
Notable performance improvements in TPS (transactions per second).
XLS-38 sidechains support

This is a large change and adds significant new functionality to the protocol.

XLS-40 DID support
Lastly, lots of code has been refactored and changed since the previous major version bump.

Type of Change

[x] Release

In its current state, this branch has diverged from what has been merged to develop, and includes a PR that has since been withdrawn.

Also the PR https://github.com/XRPLF/rippled/pull/4775 which was approved and merged in develop , in this branch is missing its last commit

Closing in favor of https://github.com/XRPLF/rippled/pull/4810 (which has already been merged to release).


⚠ Secret Website 2 has degraded performance

In a6912fa, Secret Website 2 ($SECRET_WEBSITE_2) experienced degraded performance:

HTTP code: 200
Response time: 10520 ms

Resolved: Secret Website 2 performance has improved in ab94857.


[CT-2599] [Feature] childrens_parents depth

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
Currently the @ graph operator does not allow for depth control in any way and will always include all children of a model and their (the childrens) parents.
I would like to be able to specify the depth of the child selection in the same way the children/parent operators allow for depth specification.
example:
dbt ls -s 1@my_model would result in the selection of the models children up to depth 1 + all the parents of those children.
The same should be possible with a YAML selector definition
definition:
  method: fqn
  value: my_model
  childrens_parents: true
  children_depth: 1

Describe alternatives you've considered
I tried finding a workaround with complex yaml selector definitions but since we can't "layer" definitions (take all the 1 depth children of this model + then take all the 1 depth parents of all the models in the selection) I could not get it to work as I wanted.
Who will this benefit?
For our specific use case we want to run all seeds that are used in the tests of a specified model.
Currently we can achieve this with the @ operator and a resource-type filter but this also includes any seeds that are used in tests of any of the child models of the specified model, which are not necessary for us and increases run times.
Are you interested in contributing this feature?
sure, I haven't looked at the codebase structure but this feels like a good first issue.
Anything else?
Some extra context on where/why this would help us:
https://github.com/duneanalytics/spellbook/pull/3408#issuecomment-1562445109

We also ran into this one for exactly the same use case.  In our CICD we build all parents of changed_model and one level of child models.  This gives us a good indicator if anything has broken downstream without having to build all children which, when you're using snowflake and have 1500+ models can make your CICD pipeline both slow and expensive.
The workaround we'll likely employ is to introduce some code that queries graph.pickle or uses dbt list -s changed_model+1 first in order to get the child models and then using that data, run dbt like this:
i.e.
dbt build -s +changed_model+1 +child_1 +child_2 ... +child_n
So not impossible to workaround but ugly and may have problems when the command line args get very big

@0xRobin @whisperstream Thanks for the idea, and for weighing in!
I feel like getting the syntax right will be the trickiest bit by far. Should 1@changed_model mean:

first-order children, and all their parents
first-order parents, and all their children
first-order children + first-order parents
first-order children (and their first-order parents) + first-order parents (and their first-order children)
...

To @whisperstream's point, you can do this with a series of list commands, and more ergonomically if you're wrapping dbt-core's Python entry point (new in v1.5).
Although in CI, there should be no need to build all parents of changed_model if you're using --defer or clone (which will be new in v1.6!).

@jtcohen6 thanks for the additional info.
From my understanding @changed_model currently works as:

all children, and all their parents

Which could also be expressed as +(changed_model+) as some kind of nested graph selection. Ideally we could control both the children and the parent depth.
I think it's important here to follow the convention of having parent depth before the model and child depth after the model..
usage proposal:

@changed_model+ (equivalent as @changed_model)
all children, and all their parents
1@changed_model+ (equivalent as1@changed_model)
all children, and their first-order parents
@changed_model+1
first-order children, and all their parents
1@changed_model+1
first-order children, and their first-order parents

I think @0xRobin proposed syntax seems straight-forward and intuitive.

One thing I've never actually been sure about is the current implementation of @changed_model - "the parents of the children" - does "the parents" mean only first-order parents or all (great)(grand)parents? This could be clarified with a small change to the documentation.

I think it's important here to follow the convention of having parent depth before the model and child depth after the model..

Agree!
The order of operations for resolving the @ operator: first we select the children, and second we select their parents. So it is a bit like reading from right to left.
I'm on board with the syntax that @0xRobin is proposing. And to @foundinblank's point, there's an opportunity to freshen up our docs on @. I'll tag this one a good first issue.

Likely starting point: Add parents_depth and children_depth arguments to select_childrens_parents, and pass them in accordingly.
https://github.com/dbt-labs/dbt-core/blob/b78d23f68d6e9124b74c07e0b101bed00c4171ed/core/dbt/graph/graph.py#L55-L57
https://github.com/dbt-labs/dbt-core/blob/b78d23f68d6e9124b74c07e0b101bed00c4171ed/core/dbt/graph/selector.py#L101-L120
And add some more tests:

https://github.com/dbt-labs/dbt-core/blob/main/tests/unit/test_graph_selection.py
https://github.com/dbt-labs/dbt-core/blob/main/tests/functional/graph_selection/test_graph_selection.py

Is this by any chance related to using one of the unit testing packages?

Hi @graciegoheen, thanks for pointing out that interesting discussion. We're not using any external unit testing package. The tests we are running is a combination of seeds and a custom generic test to perform the seed equality test. Our problem arises from our setup where the seeds aren't being materialized in production and are only materialized in our slim CI when they are modified. This results in the seeds not being accessible in the slim CI when you later modify the model but not the seed.


router.isActive() does not work

The isActive() Method of the Router has some overloads. Unfortunatly only the overload isActive(url: UrlTree, exact: boolean) is supported by this addon.
The other overloads isActive(url: string | UrlTree, matchOptions: IsActiveMatchOptions) is not working when using this addon. To make matters worse the isActive(url: UrlTree, exact: boolean) signature has been deprecated in the Router API.
Could you please also provide an implementation for the other overloads of isActive()?

Hi, thanks for raising this. I will look into adding the missing overloads.

I released a canary version 1.9.2--canary.25.f96e573.0 with a fix for the issue. Let me know if it works now for you

@sonallux I released a canary version 1.9.2--canary.25.f96e573.0 with a fix for the issue. Let me know if it works now for you

@Jakob-em Thanks for the fix :+1:  It works perfectly and sorry for the late reply. I was busy with other things.


Don't crash when building lighting for a level with a Cesium3DTileset

Fixes #1180
UnrealLightmass.exe is a separate process run via Swarm when building lighting. As reported in #1180, it (always? usually?) crashes when we attempt to build lighting (Build -> Build Lighting Only) for a level that has a Cesium3DTileset in it. Unfortunately it's build without any debug symbols, so I had to build it myself to debug it.
Having done that, I learned that the problem is that every FStaticMeshLightingMesh pointed to the same FStaticMesh instance, which really couldn't be right. And I learned that that was happening because, on import, all the static mesh references had the same GUID (all zeros!). Ok, so the problem seemed to be back in the Unreal Editor on the export side.
So, I traced through the code that exported the lightmass data, and yep, it was writing a GUID of all zeros. It got that GUID from a property on the UStaticMesh called LightingGuid. So how is that property set? I searched for it in the UE source code, and saw that things like DatasmithStaticMeshImporter call SetLightingGuid on the static just before they called InitResources. I added the same to our code that creates the static mesh in CesiumGltfComponent, and the lightmass crash went away.
I'll spare everyone the rant about how ridiculous it is that we have to call some random undocumented method on every static mesh we create in order to prevent UE's static lighting baking system from crashing. 🤷

Thanks for the pull request @kring!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium for Unreal Samples works.

Thanks @kring , I confirmed this removes the crash when building lighting data. I'll merge once CI passes!

This page was helpful to me in learning how to debug the lightmass executable:
https://ikrima.dev/ue4guide/graphics-development/lightmass-lightmapping/debugging-lightmass/
The really short version is you can run lightmassdebug in the console, and then launch a light build normally, and Swarm will wait for you to start UnrealLightmass.exe manually rather than launching it itself. So you can run your debug version of it in the Visual Studio debugger, and it will pick up and execute the waiting job.
Just putting this here for possible future reference.


Doc: Re-organises NIC device type docs introducing section about network property

Adds explanation of network property.
Removes nictype prefix on each NIC device type section (to avoid confusion when a NIC can be specified using both nictype and `network).
Adds Managed column for bridged NIC type.
Re-formats additional info section at bottom.
Re-orders device order to match current master.
Adds "Selected by" section to each NIC type.
Removes unnecessary white space in columns.

Signed-off-by: Thomas Parrott<EMAIL_ADDRESS>

Testsuite passed

Testsuite passed


commit faq for amit

commit faq for amit
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?
commit faq for amit
If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Update free-courses-hi.md

What does this PR do?
Add resource(s)
For resources
Description
Full Compiler Design Tutorial
Why is this valuable (or not)?
Teaches Hindi speakers how to use a compiler design
How do we know it's really free?
It is a free Youtube video
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Done, sorry for the inconvenience.


comparison of Float with String failed (ArgumentError)

Not sure when this started happening, but I'm getting this error message when trying to check for content on the page:
click_on 'A link or button'
expect(page).to have_content 'whatever'

#> comparison of Float with String failed (ArgumentError)

It used to be that Capybara would provide a helpful error message including the content that was found on the page. I'm using Capybara/Cucumber/RSpec to test an Ember.js app so maybe there is a bug in this particular combination.

What driver are you using? and please post the stacktrace so we can see where the error is coming from

Mostly using capybara-webkit, but this happens when using selenium too. It usually happens when an element can't be found on the page. There is no stack trace other than my failing steps. My steps simply have things like fill_in fields or click_on links or expect(page).to have_content. The cause of the failure is that the AJAX request hasn't finished, and Capybara doesn't know to wait for those requests to finish. Normally, Capybara is smart enough to wait, but in this case, it's some sort of conflict with Ember.js's virtual DOM.

Without a stack trace or reproducible test case there's not much we can do about this

Closing -- if a stacktrace or reproducible test case is provided we can reopen

In case anyone else comes across this (my google search led me here), I experienced this issue. The cause for me was the following line:
https://github.com/jnicklas/capybara/blob/master/lib/capybara/node/base.rb#L90
raise e if (Capybara::Helpers.monotonic_time - start_time) >= seconds

It turned out I was loading the wait time from my environment setting:
Capybara.default_max_wait_time = ENV['DEFAULT_MAX_WAIT_TIME'] || 20

The issue is that in this example ENV['DEFAULT_MAX_WAIT_TIME'] will be a string and not a numeric type.
Capybara.default_max_wait_time = (ENV['DEFAULT_MAX_WAIT_TIME'] || 20).to_i

Solved things for me.


CI: kubernetes-e2e-net-conformance (ipv4) - NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client

CI failure

Link
PR (for main branch)
No artifacts

 • [FAILED] [567.806 seconds]
[sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client [It] should enforce policy based on PodSelector with MatchExpressions[Feature:NetworkPolicy]
test/e2e/network/netpol/network_legacy.go:270

[...]

  Jun 26 21:28:53.710: INFO: Running '/usr/local/bin/kubectl --server=https://<IP_ADDRESS>:33299/ --kubeconfig=/home/runner/work/cilium/cilium/_artifacts/kubeconfig.conf --namespace=network-policy-9493 logs client-a-t8xw7 --tail=100'
  Jun 26 21:28:54.425: INFO: stderr: ""
  Jun 26 21:28:54.425: INFO: stdout: "OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted\nOTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted\nOTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted\nOTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted\nOTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted\n"
  Jun 26 21:28:54.425: INFO:
  Last 100 log lines of client-a-t8xw7:
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted

[...]

  [FAILED] Pod client-a-t8xw7 should be able to connect to service svc-server, but was not able to connect.
  Pod logs:
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted

   Current NetworkPolicies:
  	[{{ } {allow-client-a-via-pod-selector-with-match-expressions  network-policy-9493  2ef78995-2adb-4d1a-b47f-680d7f12ab58 4884 1 2023-06-26 21:22:27 +0000 UTC <nil> <nil> map[] map[] [] [] [{e2e.test Update networking.k8s.io/v1 2023-06-26 21:22:27 +0000 UTC FieldsV1 {"f:spec":{"f:ingress":{},"f:podSelector":{},"f:policyTypes":{}}} }]} {{map[pod-name:server] []} [{[] [{&LabelSelector{MatchLabels:map[string]string{},MatchExpressions:[]LabelSelectorRequirement{LabelSelectorRequirement{Key:pod-name,Operator:In,Values:[client-a],},},} nil nil}]}] [] [Ingress]} {[]}}]

   Pods:
  	[Pod: client-a-t8xw7, Status: &PodStatus{Phase:Failed,Conditions:[]PodCondition{PodCondition{Type:Initialized,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:22:27 +0000 UTC,Reason:,Message:,},PodCondition{Type:Ready,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:23:34 +0000 UTC,Reason:PodFailed,Message:,},PodCondition{Type:ContainersReady,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:23:34 +0000 UTC,Reason:PodFailed,Message:,},PodCondition{Type:PodScheduled,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:22:27 +0000 UTC,Reason:,Message:,},},Message:,Reason:,HostIP:<IP_ADDRESS>,PodIP:<IP_ADDRESS>,StartTime:2023-06-26 21:22:27 +0000 UTC,ContainerStatuses:[]ContainerStatus{ContainerStatus{Name:client,State:ContainerState{Waiting:nil,Running:nil,Terminated:&ContainerStateTerminated{ExitCode:1,Signal:0,Reason:Error,Message:,StartedAt:2023-06-26 21:23:13 +0000 UTC,FinishedAt:2023-06-26 21:23:28 +0000 UTC,ContainerID:containerd://501b494b54394f568902a60f48548197856c65d477623d15863ddb2acff07cd1,},},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:false,RestartCount:0,Image:registry.k8s.io/e2e-test-images/agnhost:2.43,ImageID:registry.k8s.io/e2e-test-images/agnhost@sha256:16bbf38c463a4223d8cfe4da12bc61010b082a79b4bb003e2d3ba3ece5dd5f9e,ContainerID:containerd://501b494b54394f568902a60f48548197856c65d477623d15863ddb2acff07cd1,Started:*false,AllocatedResources:ResourceList{},Resources:nil,},},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{PodIP{IP:<IP_ADDRESS>,},},EphemeralContainerStatuses:[]ContainerStatus{},Resize:,}
   Pod: server-mrrgw, Status: &PodStatus{Phase:Running,Conditions:[]PodCondition{PodCondition{Type:Initialized,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:19:44 +0000 UTC,Reason:,Message:,},PodCondition{Type:Ready,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:28:50 +0000 UTC,Reason:,Message:,},PodCondition{Type:ContainersReady,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:28:50 +0000 UTC,Reason:,Message:,},PodCondition{Type:PodScheduled,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:19:44 +0000 UTC,Reason:,Message:,},},Message:,Reason:,HostIP:<IP_ADDRESS>,PodIP:<IP_ADDRESS>,StartTime:2023-06-26 21:19:44 +0000 UTC,ContainerStatuses:[]ContainerStatus{ContainerStatus{Name:server-container-80,State:ContainerState{Waiting:nil,Running:&ContainerStateRunning{StartedAt:2023-06-26 21:20:04 +0000 UTC,},Terminated:nil,},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:true,RestartCount:0,Image:registry.k8s.io/e2e-test-images/agnhost:2.43,ImageID:registry.k8s.io/e2e-test-images/agnhost@sha256:16bbf38c463a4223d8cfe4da12bc61010b082a79b4bb003e2d3ba3ece5dd5f9e,ContainerID:containerd://713781a6ea78e5cc9a867e3a4ea6fda8e468a71d38f01e41b26c26b9f707fe5f,Started:*true,AllocatedResources:ResourceList{},Resources:nil,},ContainerStatus{Name:server-container-81,State:ContainerState{Waiting:nil,Running:&ContainerStateRunning{StartedAt:2023-06-26 21:20:05 +0000 UTC,},Terminated:nil,},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:true,RestartCount:0,Image:registry.k8s.io/e2e-test-images/agnhost:2.43,ImageID:registry.k8s.io/e2e-test-images/agnhost@sha256:16bbf38c463a4223d8cfe4da12bc61010b082a79b4bb003e2d3ba3ece5dd5f9e,ContainerID:containerd://531731065ce48f4fe9fd20c90f237cf651b67a51b5a4caf05566701ae35315d3,Started:*true,AllocatedResources:ResourceList{},Resources:nil,},},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{PodIP{IP:<IP_ADDRESS>,},},EphemeralContainerStatuses:[]ContainerStatus{},Resize:,}
  ]

  In [It] at: test/e2e/network/netpol/network_legacy.go:1944 @ 06/26/23 21:28:54.834

[...]

• [FAILED] [455.502 seconds]
[sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client [BeforeEach] should enforce multiple ingress policies with ingress allow-all policy taking precedence [Feature:NetworkPolicy]
  [BeforeEach] test/e2e/network/netpol/network_legacy.go:78
  [It] test/e2e/network/netpol/network_legacy.go:1124

[...]

  Jun 26 21:35:22.624: INFO: Running '/usr/local/bin/kubectl --server=https://<IP_ADDRESS>:33299/ --kubeconfig=/home/runner/work/cilium/cilium/_artifacts/kubeconfig.conf --namespace=network-policy-9636 logs client-can-connect-80-h49f2 --tail=100'
  Jun 26 21:35:22.886: INFO: stderr: ""
  Jun 26 21:35:22.886: INFO: stdout: "OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted\nOTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted\nOTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted\nOTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted\nOTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted\n"

[...]

  [FAILED] Pod client-can-connect-80-h49f2 should be able to connect to service svc-server, but was not able to connect.
  Pod logs:
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted

   Current NetworkPolicies:
  	[]

   Pods:
  	[Pod: client-can-connect-80-h49f2, Status: &PodStatus{Phase:Failed,Conditions:[]PodCondition{PodCondition{Type:Initialized,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:29:28 +0000 UTC,Reason:,Message:,},PodCondition{Type:Ready,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:30:14 +0000 UTC,Reason:PodFailed,Message:,},PodCondition{Type:ContainersReady,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:30:14 +0000 UTC,Reason:PodFailed,Message:,},PodCondition{Type:PodScheduled,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:29:28 +0000 UTC,Reason:,Message:,},},Message:,Reason:,HostIP:<IP_ADDRESS>,PodIP:<IP_ADDRESS>,StartTime:2023-06-26 21:29:28 +0000 UTC,ContainerStatuses:[]ContainerStatus{ContainerStatus{Name:client,State:ContainerState{Waiting:nil,Running:nil,Terminated:&ContainerStateTerminated{ExitCode:1,Signal:0,Reason:Error,Message:,StartedAt:2023-06-26 21:29:57 +0000 UTC,FinishedAt:2023-06-26 21:30:09 +0000 UTC,ContainerID:containerd://bb1a4457b7856d64359a6be5e2f68ceb3742590cb4b12eee6e1eff9fa7373ce2,},},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:false,RestartCount:0,Image:registry.k8s.io/e2e-test-images/agnhost:2.43,ImageID:registry.k8s.io/e2e-test-images/agnhost@sha256:16bbf38c463a4223d8cfe4da12bc61010b082a79b4bb003e2d3ba3ece5dd5f9e,ContainerID:containerd://bb1a4457b7856d64359a6be5e2f68ceb3742590cb4b12eee6e1eff9fa7373ce2,Started:*false,AllocatedResources:ResourceList{},Resources:nil,},},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{PodIP{IP:<IP_ADDRESS>,},},EphemeralContainerStatuses:[]ContainerStatus{},Resize:,}
   Pod: server-ps6n4, Status: &PodStatus{Phase:Running,Conditions:[]PodCondition{PodCondition{Type:Initialized,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:28:00 +0000 UTC,Reason:,Message:,},PodCondition{Type:Ready,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:32:40 +0000 UTC,Reason:,Message:,},PodCondition{Type:ContainersReady,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:32:40 +0000 UTC,Reason:,Message:,},PodCondition{Type:PodScheduled,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:28:00 +0000 UTC,Reason:,Message:,},},Message:,Reason:,HostIP:<IP_ADDRESS>,PodIP:<IP_ADDRESS>,StartTime:2023-06-26 21:28:00 +0000 UTC,ContainerStatuses:[]ContainerStatus{ContainerStatus{Name:server-container-80,State:ContainerState{Waiting:nil,Running:&ContainerStateRunning{StartedAt:2023-06-26 21:28:32 +0000 UTC,},Terminated:nil,},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:true,RestartCount:0,Image:registry.k8s.io/e2e-test-images/agnhost:2.43,ImageID:registry.k8s.io/e2e-test-images/agnhost@sha256:16bbf38c463a4223d8cfe4da12bc61010b082a79b4bb003e2d3ba3ece5dd5f9e,ContainerID:containerd://b768adb731fba7a914a7238d017a5d0011e3e0a50f565118183643c16c6ea19e,Started:*true,AllocatedResources:ResourceList{},Resources:nil,},ContainerStatus{Name:server-container-81,State:ContainerState{Waiting:nil,Running:&ContainerStateRunning{StartedAt:2023-06-26 21:28:44 +0000 UTC,},Terminated:nil,},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:true,RestartCount:0,Image:registry.k8s.io/e2e-test-images/agnhost:2.43,ImageID:registry.k8s.io/e2e-test-images/agnhost@sha256:16bbf38c463a4223d8cfe4da12bc61010b082a79b4bb003e2d3ba3ece5dd5f9e,ContainerID:containerd://70c72f055299d3fe07fbee48ee59dea0ef34f6ee2e0ad65f2b585f120bbbadfe,Started:*true,AllocatedResources:ResourceList{},Resources:nil,},},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{PodIP{IP:<IP_ADDRESS>,},},EphemeralContainerStatuses:[]ContainerStatus{},Resize:,}
  ]

  In [BeforeEach] at: test/e2e/network/netpol/network_legacy.go:1944 @ 06/26/23 21:35:23.441

[...]

• [FAILED] [600.932 seconds]
[sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client [It] should enforce policy to allow traffic from pods within server namespace based on PodSelector [Feature:NetworkPolicy]
test/e2e/network/netpol/network_legacy.go:165

[...]

  Jun 26 21:35:07.683: INFO: Running '/usr/local/bin/kubectl --server=https://<IP_ADDRESS>:33299/ --kubeconfig=/home/runner/work/cilium/cilium/_artifacts/kubeconfig.conf --namespace=network-policy-414 logs client-a-g9cpl --tail=100'
  Jun 26 21:35:07.942: INFO: stderr: ""
  Jun 26 21:35:07.942: INFO: stdout: "OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted\nOTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted\nOTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted\nOTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted\nOTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted\n"

[...]

  [FAILED] Pod client-a-g9cpl should be able to connect to service svc-server, but was not able to connect.
  Pod logs:
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:80: connect: operation not permitted

   Current NetworkPolicies:
  	[]

   Pods:
  	[Pod: client-a-g9cpl, Status: &PodStatus{Phase:Failed,Conditions:[]PodCondition{PodCondition{Type:Initialized,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:28:42 +0000 UTC,Reason:,Message:,},PodCondition{Type:Ready,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:29:56 +0000 UTC,Reason:PodFailed,Message:,},PodCondition{Type:ContainersReady,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:29:56 +0000 UTC,Reason:PodFailed,Message:,},PodCondition{Type:PodScheduled,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:28:42 +0000 UTC,Reason:,Message:,},},Message:,Reason:,HostIP:<IP_ADDRESS>,PodIP:<IP_ADDRESS>,StartTime:2023-06-26 21:28:42 +0000 UTC,ContainerStatuses:[]ContainerStatus{ContainerStatus{Name:client,State:ContainerState{Waiting:nil,Running:nil,Terminated:&ContainerStateTerminated{ExitCode:1,Signal:0,Reason:Error,Message:,StartedAt:2023-06-26 21:29:40 +0000 UTC,FinishedAt:2023-06-26 21:29:49 +0000 UTC,ContainerID:containerd://07f8236cd4178b6e69daec11498e45ffb4df2567dd84752aa8cda77e91eb0510,},},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:false,RestartCount:0,Image:registry.k8s.io/e2e-test-images/agnhost:2.43,ImageID:registry.k8s.io/e2e-test-images/agnhost@sha256:16bbf38c463a4223d8cfe4da12bc61010b082a79b4bb003e2d3ba3ece5dd5f9e,ContainerID:containerd://07f8236cd4178b6e69daec11498e45ffb4df2567dd84752aa8cda77e91eb0510,Started:*false,AllocatedResources:ResourceList{},Resources:nil,},},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{PodIP{IP:<IP_ADDRESS>,},},EphemeralContainerStatuses:[]ContainerStatus{},Resize:,}
   Pod: server-mgl8c, Status: &PodStatus{Phase:Running,Conditions:[]PodCondition{PodCondition{Type:Initialized,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:25:40 +0000 UTC,Reason:,Message:,},PodCondition{Type:Ready,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:33:27 +0000 UTC,Reason:,Message:,},PodCondition{Type:ContainersReady,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:33:27 +0000 UTC,Reason:,Message:,},PodCondition{Type:PodScheduled,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:25:40 +0000 UTC,Reason:,Message:,},},Message:,Reason:,HostIP:<IP_ADDRESS>,PodIP:<IP_ADDRESS>,StartTime:2023-06-26 21:25:40 +0000 UTC,ContainerStatuses:[]ContainerStatus{ContainerStatus{Name:server-container-80,State:ContainerState{Waiting:nil,Running:&ContainerStateRunning{StartedAt:2023-06-26 21:26:17 +0000 UTC,},Terminated:nil,},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:true,RestartCount:0,Image:registry.k8s.io/e2e-test-images/agnhost:2.43,ImageID:registry.k8s.io/e2e-test-images/agnhost@sha256:16bbf38c463a4223d8cfe4da12bc61010b082a79b4bb003e2d3ba3ece5dd5f9e,ContainerID:containerd://e0f945732e286d307f2a4f3ed9e3e5735043cab2ce18cb24dc7f633a30fffad2,Started:*true,AllocatedResources:ResourceList{},Resources:nil,},ContainerStatus{Name:server-container-81,State:ContainerState{Waiting:nil,Running:&ContainerStateRunning{StartedAt:2023-06-26 21:26:31 +0000 UTC,},Terminated:nil,},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:true,RestartCount:0,Image:registry.k8s.io/e2e-test-images/agnhost:2.43,ImageID:registry.k8s.io/e2e-test-images/agnhost@sha256:16bbf38c463a4223d8cfe4da12bc61010b082a79b4bb003e2d3ba3ece5dd5f9e,ContainerID:containerd://099b71f4323bc6ac5e7e7f5f76f3b4094f0b9b2892821e307d95583d4b638254,Started:*true,AllocatedResources:ResourceList{},Resources:nil,},},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{PodIP{IP:<IP_ADDRESS>,},},EphemeralContainerStatuses:[]ContainerStatus{},Resize:,}
  ]

  In [It] at: test/e2e/network/netpol/network_legacy.go:1944 @ 06/26/23 21:35:08.751

[...]

 • [FAILED] [425.045 seconds]
[sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client [BeforeEach] should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
  [BeforeEach] test/e2e/network/netpol/network_legacy.go:78
  [It] test/e2e/network/netpol/network_legacy.go:100

[...]

  Jun 26 21:38:44.378: INFO: Running '/usr/local/bin/kubectl --server=https://<IP_ADDRESS>:33299/ --kubeconfig=/home/runner/work/cilium/cilium/_artifacts/kubeconfig.conf --namespace=network-policy-9450 logs client-can-connect-81-rkzvr --tail=100'
  Jun 26 21:38:44.558: INFO: stderr: ""
  Jun 26 21:38:44.558: INFO: stdout: "OTHER: dial tcp <IP_ADDRESS>:81: connect: operation not permitted\nOTHER: dial tcp <IP_ADDRESS>:81: connect: operation not permitted\nOTHER: dial tcp <IP_ADDRESS>:81: connect: operation not permitted\nOTHER: dial tcp <IP_ADDRESS>:81: connect: operation not permitted\nOTHER: dial tcp <IP_ADDRESS>:81: connect: operation not permitted\n"

[...]

  [FAILED] Pod client-can-connect-81-rkzvr should be able to connect to service svc-server, but was not able to connect.
  Pod logs:
  OTHER: dial tcp <IP_ADDRESS>:81: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:81: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:81: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:81: connect: operation not permitted
  OTHER: dial tcp <IP_ADDRESS>:81: connect: operation not permitted

   Current NetworkPolicies:
  	[]

   Pods:
  	[Pod: client-can-connect-81-rkzvr, Status: &PodStatus{Phase:Failed,Conditions:[]PodCondition{PodCondition{Type:Initialized,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:32:59 +0000 UTC,Reason:,Message:,},PodCondition{Type:Ready,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:33:35 +0000 UTC,Reason:PodFailed,Message:,},PodCondition{Type:ContainersReady,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:33:35 +0000 UTC,Reason:PodFailed,Message:,},PodCondition{Type:PodScheduled,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:32:59 +0000 UTC,Reason:,Message:,},},Message:,Reason:,HostIP:<IP_ADDRESS>,PodIP:<IP_ADDRESS>,StartTime:2023-06-26 21:32:59 +0000 UTC,ContainerStatuses:[]ContainerStatus{ContainerStatus{Name:client,State:ContainerState{Waiting:nil,Running:nil,Terminated:&ContainerStateTerminated{ExitCode:1,Signal:0,Reason:Error,Message:,StartedAt:2023-06-26 21:33:20 +0000 UTC,FinishedAt:2023-06-26 21:33:29 +0000 UTC,ContainerID:containerd://dd9b177ffce65e3e351474bde116a3d2d8c140546c62ccc6735ea4a795875da0,},},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:false,RestartCount:0,Image:registry.k8s.io/e2e-test-images/agnhost:2.43,ImageID:registry.k8s.io/e2e-test-images/agnhost@sha256:16bbf38c463a4223d8cfe4da12bc61010b082a79b4bb003e2d3ba3ece5dd5f9e,ContainerID:containerd://dd9b177ffce65e3e351474bde116a3d2d8c140546c62ccc6735ea4a795875da0,Started:*false,AllocatedResources:ResourceList{},Resources:nil,},},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{PodIP{IP:<IP_ADDRESS>,},},EphemeralContainerStatuses:[]ContainerStatus{},Resize:,}
   Pod: server-5dw4b, Status: &PodStatus{Phase:Running,Conditions:[]PodCondition{PodCondition{Type:Initialized,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:31:46 +0000 UTC,Reason:,Message:,},PodCondition{Type:Ready,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:35:12 +0000 UTC,Reason:,Message:,},PodCondition{Type:ContainersReady,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:35:12 +0000 UTC,Reason:,Message:,},PodCondition{Type:PodScheduled,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-06-26 21:31:46 +0000 UTC,Reason:,Message:,},},Message:,Reason:,HostIP:<IP_ADDRESS>,PodIP:<IP_ADDRESS>,StartTime:2023-06-26 21:31:46 +0000 UTC,ContainerStatuses:[]ContainerStatus{ContainerStatus{Name:server-container-80,State:ContainerState{Waiting:nil,Running:&ContainerStateRunning{StartedAt:2023-06-26 21:32:08 +0000 UTC,},Terminated:nil,},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:true,RestartCount:0,Image:registry.k8s.io/e2e-test-images/agnhost:2.43,ImageID:registry.k8s.io/e2e-test-images/agnhost@sha256:16bbf38c463a4223d8cfe4da12bc61010b082a79b4bb003e2d3ba3ece5dd5f9e,ContainerID:containerd://93807515023797eb507ef0344eaeacc25f519b2ca568e1496b74bfc568efb75d,Started:*true,AllocatedResources:ResourceList{},Resources:nil,},ContainerStatus{Name:server-container-81,State:ContainerState{Waiting:nil,Running:&ContainerStateRunning{StartedAt:2023-06-26 21:32:12 +0000 UTC,},Terminated:nil,},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:true,RestartCount:0,Image:registry.k8s.io/e2e-test-images/agnhost:2.43,ImageID:registry.k8s.io/e2e-test-images/agnhost@sha256:16bbf38c463a4223d8cfe4da12bc61010b082a79b4bb003e2d3ba3ece5dd5f9e,ContainerID:containerd://af75bc8489044fbf7bde32377f95adf9330bb9cac28c875b9abe09f9ef503937,Started:*true,AllocatedResources:ResourceList{},Resources:nil,},},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{PodIP{IP:<IP_ADDRESS>,},},EphemeralContainerStatuses:[]ContainerStatus{},Resize:,}
  ]

  In [BeforeEach] at: test/e2e/network/netpol/network_legacy.go:1944 @ 06/26/23 21:38:45.17

[...]

   In [BeforeEach] at: test/e2e/network/netpol/network_legacy.go:1944 @ 06/26/23 21:38:45.17
------------------------------
••••••••••••••••••

Summarizing 4 Failures:
  [FAIL] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client [It] should enforce policy based on PodSelector with MatchExpressions[Feature:NetworkPolicy]
  test/e2e/network/netpol/network_legacy.go:1944
  [FAIL] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client [BeforeEach] should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
  test/e2e/network/netpol/network_legacy.go:1944
  [FAIL] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client [It] should enforce policy to allow traffic from pods within server namespace based on PodSelector [Feature:NetworkPolicy]
  test/e2e/network/netpol/network_legacy.go:1944
  [FAIL] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client [BeforeEach] should enforce multiple ingress policies with ingress allow-all policy taking precedence [Feature:NetworkPolicy]
  test/e2e/network/netpol/network_legacy.go:1944

Ran 91 of 7207 Specs in 1964.800 seconds
FAIL! -- 87 Passed | 4 Failed | 0 Pending | 7116 Skipped

Discussion on Slack https://cilium.slack.com/archives/C7PE7V806/p1687790469836489

connect: operation not permitted

this is something strange since the operation is happening in the socket namespace?
@brb are network policies or something "influencing" somehow the network namespace of the containers?

are network policies or something "influencing" somehow the network namespace of the containers?

It should not. Why?

OTHER: dial tcp <IP_ADDRESS>:81: connect: operation not permitted

the failures are calls inside the network namespace, that seems like an EPERM trying to "connect" , that is socket level, but I'm speculating here,

Got another one: https://github.com/cilium/cilium/actions/runs/5446592740/jobs/9907557850

interestingly the other job for network policies have socketLB disable
https://github.com/cilium/cilium/blob/55a09e5957e3cdff7183eb4330e84fbbae0e4f46/.github/workflows/conformance-k8s-network-policies.yaml#L89


Can you use aframe-text-component with this

You wrote a cool text component, but I cant seem to get it to be wrapped since its not a primitive. Any suggestions on to how this would work?

I don't recommend using primitives with aframe-react, you can use the basic Entity building block. React already has component/wrapping logic.
<Entity text={{ text: 'hello' }}>
or maybe wrap it if you want like <Text/>
export default props => <Entity text={...props.text} material={...props.material}>

Because the whole premise of aframe-react is to expose the <Entity/> building block :)
Else you'd just use raw React

btw hoping to move that component into the aframe repo some time :)

So just for clarification, you are saying I should build my own  component instead of attempting to use your aframe-text-component? I'm just trying to render some text onto the canvas.

You can use the component. I recommend not using primitives like <a-cube> or <a-sphere> since React kind of solves creating components.
You can use the text component. Do <Entity text={{ ...textProps }}>

Kind of confusing because of the overloading name of components :/

Hmm getting Unknown component attribute: text. Maybe its just a require issue. Thanks for the clarification on primatives.

Np, happy to debug any code you have here.

Ah, your demo has
var textComponent = require('aframe-text-component');
AFrame.registerComponent('text', textComponent);```
 instead of

var textComponent = require('aframe-text-component').component;```


Create new landing page for the library and docs

Landing page for library created. Docs still need a nicer page, with links to examples, etc.


Hosted app broken

I keep getting this page every time I try to access the hosted app. Looking at the console, I cannot find any error that can help with the resolution of the problem.

Just noticed https://github.com/jpartemis/cwarp/issues/1 and I reckon it's the same issue. Perhaps writing somewhere in the README that the hosted version is unstable might help.


DOC-4572 v22.1.4 release notes

Addresses: DOC-4572

Cut v22.1.4 release notes for upcoming release.

releases/v22.1.md

This change is

Thanks, great feedback! Made all changes except DB Console: is under such heading already. Thank you for quick turnaround!!


Hide internal team members from assignable case workers

Changes in this PR

add internal field to agent
add caseworkers scope to agent
filter out internal team members on the case assignment page

 Hide internal team members from assignable case workers


Cant start mongo container with DATA_SAVE_PATH changed on docker-for-mac?

Info:

Docker version ($ docker --version): Docker version 17.03.1-ce, build c6d412e
Laradock commit ($ git rev-parse HEAD): 69ccd74d2e52a8a0dac88963f87b5c19e1e12a04
System info (Mac, PC, Linux): Mac
System info disto/version:

Issue:
After change DATA_SAVE_PATH from /tmp  to ../data,i can not start mongodb now?
And i use d4m-nfs to improve speed. All my file is under /Users/xxxx/xxx
$ cat ~/d4m-nfs/etc/d4m-nfs-mounts.txt
/Users:/Users

The error is:
$ docker-compose up --build mongo
Building mongo
Step 1/5 : FROM mongo:latest
 ---> 8b2eaf28bb84
Step 2/5 : MAINTAINER Mahmoud Zalt<EMAIL_ADDRESS> ---> Using cache
 ---> 2ecf2f12375c
Step 3/5 : VOLUME /data/db /data/configdb
 ---> Using cache
 ---> 219c8e62acb1
Step 4/5 : CMD mongod
 ---> Using cache
 ---> 5bb9f38f72da
Step 5/5 : EXPOSE 27017
 ---> Using cache
 ---> 11c1c7ffab41
Successfully built 11c1c7ffab41
Starting laradock_mongo_1
Attaching to laradock_mongo_1
mongo_1                | chown: changing ownership of '/data/db': Operation not permitted
laradock_mongo_1 exited with code 1

And i also tried and user:mongodb in docker-compose.yml mongo section
#1007
Error changed like this:
mongo_1                | about to fork child process, waiting until server is ready for connections.
mongo_1                | forked process: 12
mongo_1                | 2017-08-10T07:32:05.979+0000 I CONTROL  [main] ***** SERVER RESTARTED *****
mongo_1                | 2017-08-10T07:32:05.988+0000 I CONTROL  [initandlisten] MongoDB starting : pid=12 port=27017 dbpath=/data/db 64-bit host=8080635e0fe6
mongo_1                | 2017-08-10T07:32:05.988+0000 I CONTROL  [initandlisten] db version v3.4.3
mongo_1                | 2017-08-10T07:32:05.988+0000 I CONTROL  [initandlisten] git version: f07437fb5a6cca07c10bafa78365456eb1d6d5e1
mongo_1                | 2017-08-10T07:32:05.988+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1t  3 May 2016
mongo_1                | 2017-08-10T07:32:05.988+0000 I CONTROL  [initandlisten] allocator: tcmalloc
mongo_1                | 2017-08-10T07:32:05.988+0000 I CONTROL  [initandlisten] modules: none
mongo_1                | 2017-08-10T07:32:05.988+0000 I CONTROL  [initandlisten] build environment:
mongo_1                | 2017-08-10T07:32:05.988+0000 I CONTROL  [initandlisten]     distmod: debian81
mongo_1                | 2017-08-10T07:32:05.989+0000 I CONTROL  [initandlisten]     distarch: x86_64
mongo_1                | 2017-08-10T07:32:05.989+0000 I CONTROL  [initandlisten]     target_arch: x86_64
mongo_1                | 2017-08-10T07:32:05.989+0000 I CONTROL  [initandlisten] options: { net: { bindIp: "<IP_ADDRESS>", port: 27017, ssl: { mode: "disabled" } }, processManagement: { fork: true, pidFilePath: "/tmp/tmp.f41dXYo6FM" }, systemLog: { destination: "file", logAppend: true, path: "/proc/1/fd/1" } }
mongo_1                | 2017-08-10T07:32:06.009+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=487M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
mongo_1                | 2017-08-10T07:32:06.034+0000 E STORAGE  [initandlisten] WiredTiger error (1) [1502350326:34070][12:0x7f160de72cc0], connection: /data/db/WiredTiger.wt: handle-open: open: Operation not permitted
mongo_1                | 2017-08-10T07:32:06.039+0000 I -        [initandlisten] Assertion: 28595:1: Operation not permitted src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 267
mongo_1                | 2017-08-10T07:32:06.039+0000 I STORAGE  [initandlisten] exception in initAndListen: 28595 1: Operation not permitted, terminating
mongo_1                | 2017-08-10T07:32:06.039+0000 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
mongo_1                | 2017-08-10T07:32:06.040+0000 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-27017.sock
mongo_1                | 2017-08-10T07:32:06.040+0000 I NETWORK  [initandlisten] shutdown: going to flush diaglog...
mongo_1                | 2017-08-10T07:32:06.040+0000 I CONTROL  [initandlisten] now exiting
mongo_1                | 2017-08-10T07:32:06.040+0000 I CONTROL  [initandlisten] shutting down with code:100
mongo_1                | ERROR: child process failed, exited with error number 100
laradock_mongo_1 exited with code 100

It seems like a problem of d4m-nfs. when i dont use d4m-nfs,it is ok!

@NewbMiao How to revert d4m-nfs changes?

@k-zakhariy  try to change the preference of file sharing and restart docker


InvalidPayloadDataException when using Dependency Injection

Laravel version: v5.4.17
Package version: v1.2.0
I seem to be getting an InvalidPayloadDataException when resolving this package via the service container.
The error seems to be that the TrackingId and ProtocolVersion are not being merged in when the service is resolved. Taking a dump of the resulting Analytics instance it seems these options are missing. However, everything is working fine if I use the Facade.
This has really stumped me. I am using the Facade as a workaround, but I would prefer to inject the service where possible.
Any thoughts would be greatly appreciated.
Usage Example
<?php

namespace App\Http\Controllers;

use App\Http\Controllers\Controller;
use TheIconic\Tracking\GoogleAnalytics\Analytics;

class FooController extends Controller
{
    /**
     * Set up the controller.
     *
     * @param  \TheIconic\Tracking\GoogleAnalytics\Analytics  $analytics
     * @return void
     */
    public function __construct(Analytics $analytics)
    {
        // See below for result
        dd($analytics);
    }
}

Analytics instance
Analytics {#214 ▼
  #uriScheme: "http"
  #isAsyncRequest: false
  #endpoint: "://www.google-analytics.com/collect"
  #debugEndpoint: "://www.google-analytics.com/debug/collect"
  #isDebug: false
  #singleParameters: []
  #compoundParametersCollections: []
  #httpClient: null
  #availableParameters: array:90 [▼
    "ApplicationId" => "AppTracking\ApplicationId"
    "ApplicationInstallerId" => "AppTracking\ApplicationInstallerId"
    "ApplicationName" => "AppTracking\ApplicationName"
    "ApplicationVersion" => "AppTracking\ApplicationVersion"
    "ExperimentId" => "ContentExperiments\ExperimentId"
    "ExperimentVariant" => "ContentExperiments\ExperimentVariant"
    "ContentGroup" => "ContentGrouping\ContentGroup"
    "DocumentHostName" => "ContentInformation\DocumentHostName"
    "DocumentLocationUrl" => "ContentInformation\DocumentLocationUrl"
    "DocumentPath" => "ContentInformation\DocumentPath"
    "DocumentTitle" => "ContentInformation\DocumentTitle"
    "LinkId" => "ContentInformation\LinkId"
    "ScreenName" => "ContentInformation\ScreenName"
    "CustomDimension" => "CustomDimensionsMetrics\CustomDimension"
    "CustomMetric" => "CustomDimensionsMetrics\CustomMetric"
    "CurrencyCode" => "Ecommerce\CurrencyCode"
    "ItemCategory" => "Ecommerce\ItemCategory"
    "ItemCode" => "Ecommerce\ItemCode"
    "ItemName" => "Ecommerce\ItemName"
    "ItemPrice" => "Ecommerce\ItemPrice"
    "ItemQuantity" => "Ecommerce\ItemQuantity"
    "Affiliation" => "EnhancedEcommerce\Affiliation"
    "CheckoutStep" => "EnhancedEcommerce\CheckoutStep"
    "CheckoutStepOption" => "EnhancedEcommerce\CheckoutStepOption"
    "CouponCode" => "EnhancedEcommerce\CouponCode"
    "Product" => "EnhancedEcommerce\Product"
    "ProductAction" => "EnhancedEcommerce\ProductAction"
    "ProductActionList" => "EnhancedEcommerce\ProductActionList"
    "ProductCollection" => "EnhancedEcommerce\ProductCollection"
    "ProductImpression" => "EnhancedEcommerce\ProductImpression"
    "ProductImpressionCollection" => "EnhancedEcommerce\ProductImpressionCollection"
    "ProductImpressionListName" => "EnhancedEcommerce\ProductImpressionListName"
    "Promotion" => "EnhancedEcommerce\Promotion"
    "PromotionAction" => "EnhancedEcommerce\PromotionAction"
    "PromotionCollection" => "EnhancedEcommerce\PromotionCollection"
    "Revenue" => "EnhancedEcommerce\Revenue"
    "Shipping" => "EnhancedEcommerce\Shipping"
    "Tax" => "EnhancedEcommerce\Tax"
    "TransactionId" => "EnhancedEcommerce\TransactionId"
    "EventAction" => "Event\EventAction"
    "EventCategory" => "Event\EventCategory"
    "EventLabel" => "Event\EventLabel"
    "EventValue" => "Event\EventValue"
    "ExceptionDescription" => "Exceptions\ExceptionDescription"
    "IsExceptionFatal" => "Exceptions\IsExceptionFatal"
    "AnonymizeIp" => "General\AnonymizeIp"
    "CacheBuster" => "General\CacheBuster"
    "DataSource" => "General\DataSource"
    "ProtocolVersion" => "General\ProtocolVersion"
    "QueueTime" => "General\QueueTime"
    "TrackingId" => "General\TrackingId"
    "HitType" => "Hit\HitType"
    "NonInteractionHit" => "Hit\NonInteractionHit"
    "GeographicalOverride" => "Session\GeographicalOverride"
    "IpOverride" => "Session\IpOverride"
    "SessionControl" => "Session\SessionControl"
    "UserAgentOverride" => "Session\UserAgentOverride"
    "SocialAction" => "SocialInteractions\SocialAction"
    "SocialActionTarget" => "SocialInteractions\SocialActionTarget"
    "SocialNetwork" => "SocialInteractions\SocialNetwork"
    "DocumentEncoding" => "SystemInfo\DocumentEncoding"
    "FlashVersion" => "SystemInfo\FlashVersion"
    "JavaEnabled" => "SystemInfo\JavaEnabled"
    "ScreenColors" => "SystemInfo\ScreenColors"
    "ScreenResolution" => "SystemInfo\ScreenResolution"
    "UserLanguage" => "SystemInfo\UserLanguage"
    "ViewportSize" => "SystemInfo\ViewportSize"
    "ContentLoadTime" => "Timing\ContentLoadTime"
    "DnsTime" => "Timing\DnsTime"
    "DomInteractiveTime" => "Timing\DomInteractiveTime"
    "PageDownloadTime" => "Timing\PageDownloadTime"
    "PageLoadTime" => "Timing\PageLoadTime"
    "RedirectResponseTime" => "Timing\RedirectResponseTime"
    "ServerResponseTime" => "Timing\ServerResponseTime"
    "TcpConnectTime" => "Timing\TcpConnectTime"
    "UserTimingCategory" => "Timing\UserTimingCategory"
    "UserTimingLabel" => "Timing\UserTimingLabel"
    "UserTimingTime" => "Timing\UserTimingTime"
    "UserTimingVariableName" => "Timing\UserTimingVariableName"
    "CampaignContent" => "TrafficSources\CampaignContent"
    "CampaignId" => "TrafficSources\CampaignId"
    "CampaignKeyword" => "TrafficSources\CampaignKeyword"
    "CampaignMedium" => "TrafficSources\CampaignMedium"
    "CampaignName" => "TrafficSources\CampaignName"
    "CampaignSource" => "TrafficSources\CampaignSource"
    "DocumentReferrer" => "TrafficSources\DocumentReferrer"
    "GoogleAdwordsId" => "TrafficSources\GoogleAdwordsId"
    "GoogleDisplayAdsId" => "TrafficSources\GoogleDisplayAdsId"
    "ClientId" => "User\ClientId"
    "UserId" => "User\UserId"
  ]
}

Stack Trace
[2017-08-14 16:57:43] local.ERROR: TheIconic\Tracking\GoogleAnalytics\Exception\InvalidPayloadDataException: Minimum required parameters not met for payload data, the following must be set: ProtocolVersion, TrackingId and ClientId in /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/theiconic/php-ga-measurement-protocol/src/Analytics.php:568
Stack trace:
#0 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/theiconic/php-ga-measurement-protocol/src/Analytics.php(848): TheIconic\Tracking\GoogleAnalytics\Analytics->sendHit('sendEvent')
#1 /Users/b-argo/Dropbox/Projects/majic-lamp/app/Http/Controllers/Promotions/RedeemController.php(97): TheIconic\Tracking\GoogleAnalytics\Analytics->__call('sendEvent', Array)
#2 /Users/b-argo/Dropbox/Projects/majic-lamp/app/Http/Controllers/Promotions/RedeemController.php(77): Genii\Http\Controllers\Promotions\RedeemController->redirect(Object(Genii\Models\Promotions\Promotion))
#3 [internal function]: Genii\Http\Controllers\Promotions\RedeemController->handle(Object(Genii\Models\Promotions\Promotion))
#4 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Controller.php(55): call_user_func_array(Array, Array)
#5 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(44): Illuminate\Routing\Controller->callAction('handle', Array)
#6 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Route.php(203): Illuminate\Routing\ControllerDispatcher->dispatch(Object(Illuminate\Routing\Route), Object(Genii\Http\Controllers\Promotions\RedeemController), 'handle')
#7 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Route.php(160): Illuminate\Routing\Route->runController()
#8 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Router.php(559): Illuminate\Routing\Route->run()
#9 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(30): Illuminate\Routing\Router->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#10 /Users/b-argo/Dropbox/Projects/majic-lamp/app/Http/Middleware/HttpsProtocol.php(27): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#11 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Genii\Http\Middleware\HttpsProtocol->handle(Object(Illuminate\Http\Request), Object(Closure))
#12 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#13 /Users/b-argo/Dropbox/Projects/majic-lamp/app/Http/Middleware/Sandbox.php(48): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#14 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Genii\Http\Middleware\Sandbox->handle(Object(Illuminate\Http\Request), Object(Closure))
#15 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#16 /Users/b-argo/Dropbox/Projects/majic-lamp/app/Http/Middleware/Auth/Authenticate.php(82): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#17 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Genii\Http\Middleware\Auth\Authenticate->handle(Object(Illuminate\Http\Request), Object(Closure))
#18 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#19 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php(41): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#20 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Routing\Middleware\SubstituteBindings->handle(Object(Illuminate\Http\Request), Object(Closure))
#21 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#22 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/VerifyCsrfToken.php(65): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#23 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Foundation\Http\Middleware\VerifyCsrfToken->handle(Object(Illuminate\Http\Request), Object(Closure))
#24 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#25 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/View/Middleware/ShareErrorsFromSession.php(49): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#26 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\View\Middleware\ShareErrorsFromSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#27 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#28 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(64): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#29 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Session\Middleware\StartSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#30 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#31 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/AddQueuedCookiesToResponse.php(37): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#32 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse->handle(Object(Illuminate\Http\Request), Object(Closure))
#33 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#34 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php(59): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#35 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Cookie\Middleware\EncryptCookies->handle(Object(Illuminate\Http\Request), Object(Closure))
#36 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#37 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(102): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#38 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Router.php(561): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#39 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Router.php(520): Illuminate\Routing\Router->runRouteWithinStack(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request))
#40 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Router.php(498): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request))
#41 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(174): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request))
#42 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(30): Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}(Object(Illuminate\Http\Request))
#43 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(30): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#44 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))
#45 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#46 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(30): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#47 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))
#48 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#49 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php(27): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#50 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Foundation\Http\Middleware\ValidatePostSize->handle(Object(Illuminate\Http\Request), Object(Closure))
#51 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#52 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php(46): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#53 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode->handle(Object(Illuminate\Http\Request), Object(Closure))
#54 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#55 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(102): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#56 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(149): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#57 /Users/b-argo/Dropbox/Projects/majic-lamp/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(116): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
#58 /Users/b-argo/Dropbox/Projects/majic-lamp/public/index.php(51): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
#59 /Users/b-argo/.composer/vendor/laravel/valet/server.php(133): require('/Users/b-argo/D...')
#60 {main}

Sorry for the long delay. I just noticed this issue right now. It should be fixed in the latest release. Please update and test it. Thanks!

Confirmed, thanks for your help!


TLS support for gRPC Query server

Which problem is this PR solving?

Add TLS for gRPC Query server
Fixes #2248

Short description of the changes

Similar to collector TLS implementation. Made use of pkg/config/tlscfg and added new query options

TODO

Add docs for --query.grpc.tls.* options

Please see the build error:
vet: cmd/all-in-one/main.go:201:12: cannot initialize 1 variables with 2 values

Thanks for the review! I adjusted the code based on suggestions. For docs, i'll open a separate PR in documentation repo

@jan25 let me know if you'd like to increase unit test coverage in server.go

Yes, let me see to improve the coverage

I see two ways to improve coverage - One is to write TestCreateServer that just creates server instance with TLS enabled and tests for nil err. Other is to setup server with TLS, gRPC client and test a RPC call(which may need test certs and keys). Which one would you recommend?

It would be nice to have both, but looking at collector code we don't have tests for the client/server TLS. Let's at least add tests for the error cases (like invalid path to a cert file).
In the future we may consolidate starting the gRPC server into a shared package that can be tested for TLS.

Thanks, @jan25 🎉


Add support for IBM DB2

Looks that testcontainers provide first class support for it https://java.testcontainers.org/modules/databases/db2/ hense unit tests can be added seamlessly.

Will be released soon in the scope of 8.14.0


Update dom-helpers

Currently uses the older version, which leads to dom-helpers being included twice, when bundling react-virtualized with webpack and having dom-helpers 2.x and 3.x used.

Hi @danez,
Thank you for creating this PR.
Jumping a dependency from 2.x to 3.x is a questionable change without a major release.
I don't see a changelog on the dom-helpers lib unfortunately so I'm not sure if it would be safe enough to just relax the dependency to allow either 2.x or 3.x (eg "^2.4.0 || ^3.0.0")
@jquense would you have any suggestion by chance?

should be safe to upgrade. the "breaking" change in 2 -> 3 was around the import structure when importing all of dom-helpers, since RV just cherry-picks scrollbarSize , it shouldn't affect ya'll

Excellent. Thanks @jquense!
@danez let's go with a pattern that supports either version (eg "^2.4.0 || ^3.0.0") and leave it up to library users which they use. I don't want to yank the rug out from under anyone who may be relying on the 2.x import structure. It sounds like RV is safe to work with either though. 😁

Okay updated :)

Fantastic. Thanks to both of your for your help with this. 😄
I'll try to get a release out sometime within the next day or two.


remove the redundant alert when recasting the spell

Whenever the spell is castable and one of the spell icons is clicked, the following alert is skipped.
https://user-images.githubusercontent.com/85463994/194217166-52090fb8-432a-43a0-86be-d5a696b9383d.mp4
Fixes https://github.com/PortAGuy/thrall-helper/issues/5

was this issue fixed for you @call-me-maple or is it still happening?

was this issue fixed for you @call-me-maple or is it still happening?

It was fixed for a time but I don't think it's working at the moment.


docs(ngComponentRouter): add note about shims needed for IE

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
docs
What is the current behavior? (You can also link to an open issue here)
info about es6 shims is missing

LGTM


cube.with_spectral_unit gives KeyError: PhysicalType('frequency')

Following the examples on https://spectral-cube.readthedocs.io/en/latest/manipulating.html, when we run :
from astropy import units as u
cube2 = cube.with_spectral_unit(u.km / u.s, velocity_convention='radio')
we see the following error:

KeyError                                  Traceback (most recent call last)
Input In [42], in <cell line: 3>()
1 cube.spectral_axis
2 #cube2 = cube.with_spectral_unit(u.km / u.s)
----> 3 cube2 = cube.with_spectral_unit(u.km / u.s,velocity_convention='radio')
4 cube2.spectral_axis
File /opt/anaconda3/envs/CH/lib/python3.10/site-packages/spectral_cube/spectral_cube.py:1293, in BaseSpectralCube.with_spectral_unit(self, unit, velocity_convention, rest_value)
1269 def with_spectral_unit(self, unit, velocity_convention=None,
1270                        rest_value=None):
1271     """
1272     Returns a new Cube with a different Spectral Axis unit
1273
(...)
1291
1292     """
-> 1293     newwcs,newmeta = self._new_spectral_wcs(unit=unit,
1294                                             velocity_convention=velocity_convention,
1295                                             rest_value=rest_value)
1297     if self._mask is not None:
1298         newmask = self._mask.with_spectral_unit(unit,
1299                                                 velocity_convention=velocity_convention,
1300                                                 rest_value=rest_value)
File /opt/anaconda3/envs/CH/lib/python3.10/site-packages/spectral_cube/base_class.py:334, in SpectralAxisMixinClass._new_spectral_wcs(self, unit, velocity_convention, rest_value)
331     meta['Original Unit'] = self._wcs.wcs.cunit[self._wcs.wcs.spec]
332     meta['Original Type'] = self._wcs.wcs.ctype[self._wcs.wcs.spec]
--> 334 out_ctype = ctype_from_vconv(self._wcs.wcs.ctype[self._wcs.wcs.spec],
335                              unit,
336                              velocity_convention=velocity_convention)
338 newwcs = convert_spectral_axis(self._wcs, unit, out_ctype,
339                                rest_value=rest_value)
341 newwcs.wcs.set()
File /opt/anaconda3/envs/CH/lib/python3.10/site-packages/spectral_cube/spectral_axis.py:119, in determine_ctype_from_vconv(ctype, unit, velocity_convention)
117 else:
118     lin_cunit = LINEAR_CUNIT_DICT[ctype]
--> 119     in_physchar = PHYSICAL_TYPE_TO_CHAR[lin_cunit.physical_type]
121 if unit.physical_type == 'speed':
122     if velocity_convention is None and ctype[0] == 'V':
123         # Special case: velocity <-> velocity doesn't care about convention
KeyError: PhysicalType('frequency')
Any help is greatly appreciated!  This works fine on my own (older) version of Python with Spectral-cube, but we get this error on a student's newer version.

This looks like a duplicate of #709 and #747.  Could you report your spectral-cube and astropy versions?

Thanks for finding those related tickets, I didn't see them because they are "closed".  Should have looked!
Should we use  dev version of spectral cube?
Will look into the versions.  Thanks!

Which version of spectral-cube do you have now? spectral_cube.version.version?
The newest release is v0.6.0 and should have this issue fixed now.

spectral-cube v0.5.0, astropy v5.1, and astropy-healpix v0.6

I had the same issue, but the latest release V0.6.0 appears to have fixed it. Thank you very much!

Since the solution is to upgrade to v0.6, I'm closing this.


Change boolean to Boolean

Codecov Report

Merging #214 into master will decrease coverage by 0.02%.
The diff coverage is 33.33%.

@@             Coverage Diff              @@
##             master     #214      +/-   ##
============================================
- Coverage     31.69%   31.67%   -0.03%
  Complexity      355      355
============================================
  Files            46       46
  Lines          2988     2987       -1
  Branches        379      379
============================================
- Hits            947      946       -1
  Misses         1921     1921
  Partials        120      120

Impacted Files
Coverage Δ
Complexity Δ

.../redhat/red/build/finder/DistributionAnalyzer.java
67.02% <100%> (ø)
44 <7> (ø)
:arrow_down:

...rc/main/java/com/redhat/red/build/finder/Main.java
30.07% <25%> (-0.18%)
17 <4> (ø)

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 047374b...6d2ec07. Read the comment docs.


Add a command-line option to disable all caching

If one's experimenting with external libraries then both in-browser caches and in-node caching should be made disableable behind a switch.
Requested via twitter: https://twitter.com/Eric01/status/959532612384518144

I'm willing to submit a PR if someone can point me in the right direction. I've been hacking on the JS, and haven't found an easy way to disable caching that works.
Ideally I would like to delete a character, re-type the same character, and have the entire compilation repeated anew.

There's a button in the UI to re-submit (at the bottom right).
To disable the caching you'll need to do something like:

add a command-line option in app.js near the top of the file
pass it as a configuration option to the browser; add it to options around https://github.com/mattgodbolt/compiler-explorer/blob/master/app.js#L268
Server-side, use the config to indicate to lib/compilation-env.js that its cacheGet should always return undefined (or similar)
Browser-side use the config set in step 2 above to disable the cache in CompilerService (static/compiler-service.js)

So: I've added an EXTRA_ARG that disables all caching, server & client side. But as you might have guessed, this is not going to be used in the live site (For obvious reasons!) so locally, simply running make EXTRA_ARGS="--noCache" should do the trick.
:)


Hi there! When will 4.3.4 be available？#manual_legend.ipynb#

https://github.com/JetBrains/lets-plot/blob/master/docs/f-24e/manual_legend.ipynb.
It seems the layer parameter manual_key and layer_key function cannot be found in 4.3.3.

That's right, this feature is coming only in the next release in late July.


token: Remove flow declarations file

Problem
The flow declarations file module.flow.js is maintained by hand and cannot easily be checked in CI, leading to a bad experience for downstream developers whenever there's an issue.  The TypeScript declaration file should be enough for developers.
Solution
Remove the file and references to it.

Nevermind, this is still needed!


Twipsy tooltip with an unreachable link inside

I'm trying to use Twipsy as a hovering tooltip with a link inside the tooltip.
The problem is that when the mouse cursor leaves the element then the tooltip disappears and users can't reach the link inside the tooltip (take a look at the Demo (http://twitter.github.com/bootstrap/javascript.html#twipsy) and see that you can't put your mouse cursor on the twipsy black bubble as it disappear).
Please advise.

delayOut

That's not a solution but rather a bad hack, because if there is another twipsy element next to it then two tooltips may be visible at the same time, and one may cover the other.

There isn't a way to do this. Our tooltips weren't designed to have interactive content.
If you did want this, your best bet would be to roll a custom solution which houses the tooltip within the element which is being hovered, so that the mouseout event isn't fired.

Oh, too bad. Thanks for the answer Jacob.

Although Jacob is most certainly correct that it's a better idea to roll your own in this instance, I posted a hacky way to solve this issue on stack overflow.

Oh, actually in 2.0 you can do placement: "inside top" and it will insert the tipsy inside the element being hovered. You'll have to do some work with css from there to make sure it doesn't inherit styles, etc. Not sure if this will actually make it into the final 2.0 release.


Plans for Rustler precompiled?

Hey there! Any plans to add CI workflows w/ Rustler Precompiled? Would definitely help with deployment.

Definitely on the roadmap! Between rustler precompiled and precompiled libonnxruntime(s), I think there's a lot we can do to make deployment quicker and simpler. In the meantime, we're open to PRs too!


Cannot run the example

Hello !
I saw an article about Compoxure and I wanted to try it but I think it doesn't work when I run it.
I'm able to clone the repository, do an "npm install" and "npm run start" and I can see the messages :
"Example compoxure server on http://localhost:5000
Example backend server on http://localhost:5001"
But when I go to http://localhost:5000 as mentioned in the instructions, I see nothing but "Service http://localhost:5001/ responded with status code 504"
So I try to go on http://localhost:5001 and here I'm able to see something : a page with some examples showing the difference between original source template and the result proxied via Compoxure.
BUT ! The problem is there is no difference between the contents so I suppose Compoxure is not running (or not working).
When I read the logs, I have errors about "cache missing for key backend:/".
Did I miss something important ? (For information, i use node v6.9.5)
I'm sorry if my problem is stupid but I think the example is supposed to work without any additional configurations. Or am I totally wrong ?
Thank you in advance !

I am also hitting this issue.
Here is my stack trace:
LOG debug: OK http://localhost:5001/
STAT timing for backend_localhost.responseTime | 42
~/Development/compoxure/node_modules/compoxure/src/middleware/htmlparser.js:275
        host: req.get('host')
                  ^

TypeError: req.get is not a function
    at getParxerOpts (~/Development/compoxure/node_modules/compoxure/src/middleware/htmlparser.js:275:19)
    at ServerResponse.parse (~/Development/compoxure/node_modules/compoxure/src/middleware/htmlparser.js:332:14)
    at ~/Development/compoxure/node_modules/compoxure/src/middleware/proxy.js:175:17
    at ~/Development/compoxure/node_modules/compoxure/src/middleware/proxy.js:106:20
    at ~/Development/compoxure/node_modules/reliable-get/index.js:123:13
    at args.(anonymous function) (~/Development/compoxure/node_modules/async-deco/src/log.js:22:9)
    at args.(anonymous function) (~/Development/compoxure/node_modules/async-deco/src/fallback-cache.js:54:11)
    at args.(anonymous function) (~/Development/compoxure/node_modules/async-deco/src/cache.js:35:13)
    at Immediate.<anonymous> (~/Development/compoxure/node_modules/async-deco/src/dedupe.js:23:15)
    at runCallback (timers.js:576:20)
    at tryOnImmediate (timers.js:554:5)
    at processImmediate [as _immediateCallback] (timers.js:533:5)

Hello,
Same exact issue here.

I figured out why the example is failing in my comment above. Turns out the example is written to use the connect server, which uses the nodejs-native request objects. However, the call to req.get fails with this assumption. This is because .get is a method available on request objects returned from Express.js.
As such, it looks like the example is broken since the project does not look to support connect from what I can tell. I was able to get things working by writing a basic example with express.

Hi @strife25. I have not ran the example for a while but using Express instead of connect is correct. We run all pur microservices on Express 4. Can you submit a PR with tha fix for the example? If you hit another snag let me know and I'll try to help

@gabceb @strife25 I had the same issue today while doing an evaluation of Compoxure. Please look at #95 that fixes it. Special thanks to @strife25 for a hint about using Express.


Implements log_det functions for arma, blaze and eigen using cholesky decomposition

I have implemented the functions to compute log_determinant using cholesky decomposition inside matrix_ops.hpp and used the same in dmvnormal.hpp to avoid direct computation of determinant as it breaks (underflows) in case of large covariance matrices. Also I tested the consistency of the results with all the three matrix libraries.

Thanks for the PR. I'll switch out the inv cases myself.

Great. Thanks


Some tile highlighting doesn't work

As mentioned in a comment to a different issue, all boulders except copper don't appear. This also applies to Fungal Soil and possibly Ancient Gemstone Ore (or I just don't have any currently discovered, but it's possible that I do and it doesn't show up). Also I thought Rug didn't work, but it seems it's only the default colour that shows up, and all the other painted versions just aren't implemented at all (pretty please?).

I'll reply here, since I closed the other one already.
Map is working for me. You sure your map has more boulders? Try the example map to make sure. That one (as can be seen in the picture) has other boulders
Ancient Gemstone Ore seems to work as well:

You can also verify it in the example map.
Fungal soil might not be in the example map, since it was added in a later patch I think. So I'll have to check it out later.
And yeah, wanted to add all the tiles (that inlcudes the colored carpets) but I didn't get around to it yet, since I wasn't on the PC where I have the formatted list in over a week. I'll definitely do it tomorrow though 😬

Welp, it seems maybe I don't have any other boulders, actually? I don't know, I found a gold one and took a screenshot while standing next to it to be sure where it was, and that one shows up on the map tool. Weird, I was sure I've seen some others while running around. I'll have to check once I see one again.
As for the Fungal Soil:

as you can see, there are two bands of it in the right farm, not highlighted. I see you included Stone Moss, are any others also planned?

Huh. I might have messed up the RGB values by accident. Will check it out today.
I have the color values of all the things that show up in the minimap, so I should be able to add everything

Sorry for the delay! Had family visiting, so I had to take some time away from my pc.
Should be fixed now. Turns out the color picker I used had a +1 for the blue value (61 instead of 60).


Announce 6 July 2023 Jira outage

Announce 6 July 2023 Jira database upgrade
https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-25544 as coordinated from Mark Waite's account at the Linux Foundation.

I'm not sure if we want to merge this now or wait until we're much closer to the scheduled date.  Guidance from others?

I'm not sure if we want to merge this now or wait until we're much closer to the scheduled date. Guidance from others?

We could merge it now, setting the severity to "notice" and changing it to "down" once the update takes place.
That helps to raise awareness.

I'm not sure if we want to merge this now or wait until we're much closer to the scheduled date. Guidance from others?

We could merge it this week, setting the severity to "notice" and changing it to "down" once the update takes place.
That helps to raise awareness, by putting a pre-announcement in place, for ~7 business days before the incident takes place.
To raise even more awareness, a Jira admin could place an announcement banner directly on Jira itself, pointing to the status page.
I don't think everyone looks at status.j frequently, and an announcement directly on the service affected could help.