[v1.31.1] Change dependency config in awsagentprovider

Issue #, if available:
fixed https://github.com/aws-observability/aws-otel-java-instrumentation/issues/648, https://github.com/aws-observability/aws-otel-java-instrumentation/issues/644 in v1.31.x.
Description of changes:
In this PR, we changed the dependency configuration of io.opentelemetry:opentelemetry-exporter-otlp from implementation to compileOnly.
The high cardinality issue was caused by introducing this dependency as implementation which causes classpath conflict during the runtime.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (0e49186) 49.96% compared to head (1fc22a4) 49.96%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                Coverage Diff                 @@
##             release/v1.31.x     #653   +/-   ##
==================================================
  Coverage              49.96%   49.96%
  Complexity               264      264
==================================================
  Files                     39       39
  Lines                   1297     1297
  Branches                 145      145
==================================================
  Hits                     648      648
  Misses                   617      617
  Partials                  32       32

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Synology

Hello
Do you think it's possible to install it on docker on synology ?

yes it work

Do you know how to get it work with homebridge docker on Synology?


Version file does not support line ending (.node-version)

Text files often have a line-ending. Depending on the editor, it may be difficult for the user to tell if there is a line-ending or not, or possibly the editor may add one automatically.
It looks like from my limited testing that nvm-rust does not allow the version file to have a trailing line-ending:
% hexdump -C .node-version
00000000  31 30 2e 31 32 2e 30 0a                           |10.12.0.|
00000008
% nvm install
Failed to parse .node-version: '10.12.0
'
Error: You did not pass a version and we did not find any version files (package.json#engines, .nvmrc) in the current directory.

(Full disclosure. I am not a user of nvm-rust! I took a look because I am interested in application support for .node-version: https://github.com/shadowspawn/node-version-usage)

Thank you for the report!


[RFE] provisioning-v2 custom node cleanup on node deletion

Is your feature request related to a problem? Please describe.
In provisioning-v2, a custom node that is deleted from a cluster is not properly cleaned up. In the case of a controlplane node, this can lead to unexpected behavior (and etcd/worker nodes going into a perpetual NotReady state until either the deleted node is shut down or removed from the cluster. Additionally, in the case of non-etcd nodes, it is possible to have a custom node that was deleted and rebooted rejoin the cluster if rke2-server/rke2-agent/k3s or k3s-agent is started on it, as it will re-register into the cluster.
We need to provide the ability to clean up custom nodes from a cluster when they are deleted. We do not specifically have to worry about machine provisioned infrastructure as in most cases, that infrastructure is deleted on machine deletion.
Describe the solution you'd like
Add the ability to deliver an uninstall plan to a deleted custom node. This can be done through the rancher-system-agent, through the use of a finalizer on the machine object that triggers off deletion logic. I am thinking we can implement a pre-delete hook that has custom logic implemented to perform deletion of the custom node.
This functionality should also be able to be disabled.
Note that there are caveats and edge cases to this, and it is important to try and minimize the potential for accidental data loss. For example, certain cloud-providers may delete the node object if the node is offline, which could accidentally trigger machine deletion logic on our end via the nodesyncer.
Describe alternatives you've considered
Release note and/or workaround documentation
Additional context
The specific issue that I encountered that spawned this RFE is here: https://github.com/rancher/rke2/issues/4060

We are using Rancher to manage custom clusters in AWS using auto scaling groups vs the rancher machine pools following the guide here.
After cluster-autoscaler scales up the nodes and then scales back down the old nodes are now still in the Rancher UI with a Nodenotfound error.  We'd have to use ASG lifecycle hooks with a lambda but it'd be nice if this could be handled via rancher-system-agent

We still have the issue in 2.8.3, @snasovich have you plan to fix it in 2.8.4 ?


Added Git and GitHub Commands in md format (Corrected)

I previously made a separate folder for cheat sheets by mistake and also the .md file was not working properly.
But now I have fixed these issues.
Now I have added this file in already existing cheat sheet folder and the file is also working fine.
Please check it out.

I previously made a separate folder for cheat sheets by mistake and also the .md file was not working properly. But now I have fixed these issues. Now I have added this file in already existing cheat sheet folder and the file is also working fine. Please check it out.

nice👍


Address clang-tidy-10 warnings

We can wait for #296 and then rebase here before merging, of course.


Build/test docs in CI as an external target

The ultimate product of the docs build is the website, which builds from the envoy repo as an external target
Due to issues with rules_python namespacing this means that the website can break despite no issues being detected in our CI
The better test of the docs build would be to checkout the website repo and build docs from there

cc @missBerg website build was broken in recent rules_python update - im fixing in https://github.com/envoyproxy/envoy/pull/36914 - but ci should detect this


Feature request: add background to widget

A translucent background will improve the readability of the widget laying on a color-rich wallpaper.

It's good too to to drop some slight shadows. For example:

Great! But what I actually meant a borderless, colourless and translucent background like this image:

Of course, it would be quite perfect if you can implement text shadows.

Thanks for the advice. I will try.


Status bar could not be hidden for full screen ad on IOS devices

2.0.1
When I use Interstatial ads on iOS devices I receive this warning in debug console.(No problems with ads showing)
Status bar could not be hidden for full screen ad. Ensure that your app is configured to allow full screen ads to control the status bar. For example, consider whether you need to set the childViewControllerForStatusBarHidden property on your ad's rootViewController.
I wasn't able find out where can I implement the hide status bar functionality. Can you help?

I ran into this issue and this cleared the error for me:
import 'package:flutter/services.dart';
hide status bar:
SystemChrome.setEnabledSystemUIMode(       SystemUiMode.manual,       overlays: <SystemUiOverlay>[],     );
show status bar (after ad is closed by user):
SystemChrome.setEnabledSystemUIMode(       SystemUiMode.manual,       overlays: SystemUiOverlay.values,     );

Hi @zumatrahia
Please see Stricter enforcement of status bar controls.

Starting from version 9.0.0, when you present full screen format ads, your app should ensure that the ads are able to control the presentation of the status bar. You will see an error message in the logs if you fail to do so.

Depending on the specific layout of view controllers in your app, you may not need to make any changes to ensure this, but in some cases, you may need to set your parent view controller's modalPresentationCapturesStatusBarAppearance property.

However, I also don't see a workaround or guideline for this. Labeling this issue for further insights from the team.

I ran into this issue and this cleared the error for me: import 'package:flutter/services.dart'; hide status bar: SystemChrome.setEnabledSystemUIMode( SystemUiMode.manual, overlays: <SystemUiOverlay>[], ); show status bar (after ad is closed by user): SystemChrome.setEnabledSystemUIMode( SystemUiMode.manual, overlays: SystemUiOverlay.values, );

It works thank you

@JoeArmani @zumatrahia How do you restore the status bar when the ad is close?
I tried but it doesn't work. I'm not sure how. Here's my code:
              SystemChrome.setEnabledSystemUIMode(SystemUiMode.manual, overlays: []);
              await _showInterstitialAd();
              SystemChrome.setEnabledSystemUIMode(SystemUiMode.manual, overlays: SystemUiOverlay.values);
              print('Ad has been displayed');

Even when I await the _showInterstialAd function, the line 'Ad has been displayed' always finished before the ad finished. Meaning somehow the async function showInterstialAd doesn't wait at all.
Here's the code of _showInterstitialAd():
  Future<void> _showInterstitialAd() async {
    if (_interstitialAd != null) {
      _interstitialAd!.fullScreenContentCallback = FullScreenContentCallback(
        onAdDismissedFullScreenContent: (InterstitialAd ad) {
          ad.dispose();
          _loadInterstitialAd();
        },
        onAdFailedToShowFullScreenContent: (InterstitialAd ad, AdError error) {
          ad.dispose();
          _loadInterstitialAd();
        },
      );
      await _interstitialAd!.show();
    }
  }

@minhdanh SystemChrome.setEnabledSystemUIMode() is asynchronous, use await SystemChrome.setEnabledSystemUIMode() to make sure the bars are actually hidden before the ad is displayed.

I ran into this issue and this cleared the error for me: import 'package:flutter/services.dart'; hide status bar: SystemChrome.setEnabledSystemUIMode( SystemUiMode.manual, overlays: <SystemUiOverlay>[], ); show status bar (after ad is closed by user): SystemChrome.setEnabledSystemUIMode( SystemUiMode.manual, overlays: SystemUiOverlay.values, );

Thanks for the Solution. YOu saved my time


Upgrade OLM between releases

Feature Request
Is your feature request related to a problem? Please describe.
OLM itself is installed by applying the manifests in the latest release to a cluster via kubectl apply. However, for a long running cluster that expects to pull in newer versions of OLM over time, there is no clear path between releases. How do you install a newer version of OLM without first uninstalling it? In the trivial case, you could just reapply the new manifests and pull in their updates, but in some cases (ex a manifest that has been removed
Describe the solution you'd like
An explicit upgrade script (similar to install.sh) but that compares the current version on cluster to the new version being applied that is aware of how to upgrade from one version to the next. Potentially, if there are issues upgrading between those versions, an error message stating why along with next steps beyond that.

With the advent of operator-framework/rukpak -- and it's counterpart, deppy -- I think we should package OLM as a "plain bundle", and use rukpak to handle its upgrades. @kevinrizza wdyt?
cc @timflannagan @perdasilva

@njhale The only problem with packaging OLM as a plain bundle is that rukpak's plain provisioner has the current limitation where Bundles that contain both the CRD definitions and instances of those CRDs as CRs results in an ordering problem due to our usage of helm under-the-hood. See https://github.com/operator-framework/rukpak/issues/131 for more information.
That said, it's definitely possible to package OLM as two different Bundle resources:

CRD definitions
Application + custom resource instances

With the introduction of embedded Bundles, we'd need to create two BundleInstances to instantiate OLM, which seems like overkill right now?

I can upgrade OLM
# You should run this command the first time without --force-conflicts to check if you have any conflicts.
# If you have some conflicts, it is better to analyse them.
kubectl apply -f ./crds.yaml --server-side=true --force-conflicts

# check that all CRDs were installed properly.
kubectl wait --for=condition=Established -f ./crds.yaml

# OLM operators will be updated here and restarted.
kubectl apply -f ./olm.yaml

What potential issues can I have in this case?

@hedgss Since this is manually applying manifests this can cause issues if we rename or restructure the manifest files that are part of an OLM release. But to be honest we haven't done that so far as I can remember.
The other scenario is that within olm.yaml we do change the structure in which OLM is deployed, i.e. when adding new controllers or removing older ones. Again, not a likely scenario at the moment and not something we would do without a major version bump of OLM. But if you want to be extra sure, you can essentially kubectl apply delete -f ./olm.yaml with the previous olm.yaml and kubectl apply... the new one for a clean removal and install of the new version. The CRDs should never be deleted and should always be safe to be updated by applying the crd.yaml.


Update config_flow tests

Proposed change

Update config_flow tests
Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (which adds functionality)
[ ] Breaking change (fix/feature causing existing functionality to break)
[x] Code quality improvements to existing code or addition of tests
[ ] Documentation update
[ ] Adds a new shipper
[ ] Update existing shipper

Additional information

This PR is related to issue: n/a

Just a tests update, no changes to the integration itself.

You good to go on these even though it failed two of the checks?

Ya, the labeler and HACS validation just freaking out.


DoublePressModifier always triggered?

I have the following autogen:
      <autogen>
        __DoublePressModifier__
        KeyCode::A, ModifierFlag::OPEN_APPS,
        KeyCode::VK_OPEN_URL_APP_Firefox,
        __{ KeyCode::VK_OPEN_URL_APP_Firefox, KeyCode::ESCAPE, KeyCode::VK_WAIT_10MS, KeyCode::A, KeyCode::VK_WAIT_10MS, KeyCode::SPACE, }__
      </autogen>

My problem is that the latter keycode sequence is always triggered, despite the fact that I press A only once. Why might this happen? How do I begin to debug this problem?
I want a single tap of a+openapps modifier to open firefox, and a x2 + openapps modifier to run the latter keycode sequence.

You have to use experimental feature: Option::KEYTOKEY_TIMEOUT.
(No docs, No stable specifications)
Please upgrade to v10.6.18 and use this autogens.
    <block>
      <lastpressedphysicalkey_only>KeyCode::A</lastpressedphysicalkey_only>
      <elapsedtimesincelastpressed_lessthan>Millisecond::RawValue::300</elapsedtimesincelastpressed_lessthan>
      <autogen>
        __KeyToKey__
        KeyCode::A, ModifierFlag::OPEN_APPS,
        KeyCode::VK_OPEN_URL_APP_Firefox,
        KeyCode::ESCAPE,
        KeyCode::VK_WAIT_10MS,
        KeyCode::A,
        KeyCode::VK_WAIT_10MS,
        KeyCode::SPACE,
      </autogen>
    </block>

    <autogen>
      __KeyToKey__
      KeyCode::A, ModifierFlag::OPEN_APPS,
      KeyCode::VK_NONE,

      Option::KEYTOKEY_TIMEOUT,
      KeyCode::VK_OPEN_URL_APP_Firefox,

      Option::KEYTOKEY_TIMEOUT_CANCELED_BY,
      KeyCode::A,
      KeyCode::VK_NONE,
    </autogen>

How to upgrade to the latest beta version:
https://pqrs.org/osx/karabiner/document.html#check-for-updates

I've changed Option::KEYTOKEY_TIMEOUT to Option::KEYTOKEY_DELAYED_ACTION and
introduced more simple forms:
    <autogen>
      __KeyToKey__
      KeyCode::A, ModifierFlag::OPEN_APPS,
      KeyCode::VK_NONE,

      Option::KEYTOKEY_DELAYED_ACTION,
      KeyCode::VK_OPEN_URL_APP_Firefox,

      Option::KEYTOKEY_DELAYED_ACTION_CANCELED_BY,
      KeyCode::A,
      KeyCode::VK_OPEN_URL_APP_Firefox,
      KeyCode::ESCAPE,
      KeyCode::VK_WAIT_10MS,
      KeyCode::A,
      KeyCode::VK_WAIT_10MS,
      KeyCode::SPACE,
      KeyCode::VK_KEYTOKEY_DELAYED_ACTION_DROP_EVENT,
    </autogen>

Thanks!


Room badge does not update when the other user self-signed a device

Have a DM with a verify user
-> The DM has a green badge in Riot-iOS
The other user signs in on a new device but does not verify it
-> The DM has a red badge in Riot-iOS
The other user verifies the new device on their side
-> The DM still has a red badge in Riot-iOS (NOK)

Note that the user is green in the room member screen (OK):

Clear cache fixes it.

The opposite it also true. If the other users was green, we still see them green after they add a non verified device.


Support inline fragments for diffing + remove Node refetching code

TODO:

[x] Update CHANGELOG.md with your change
[x] Make sure all of the significant new logic is covered by tests
[x] Rebase your changes on master so that they can be merged easily
[x] Make sure all tests and linter rules pass

Fixes https://github.com/apollostack/apollo-client/issues/147

Note: To properly evaluate fragments, we need __typename. We can probably fake it for now, but it would be good to have #27 to make this feature work much better.

@jbaxleyiii just wanted to get a sanity check from you - this PR removes a bunch of code around refetching individual nodes that we weren't actually using in the public API at all. If we put it back, it should be as a diffing plugin a la #26
Also, I left some of the old tests in a commented file, should I do that or just delete stuff altogether?

Deleted the commented code, we can always get it later if we want it.

@stubailo what is the goal of removing the node fetching? I thought this was being used because we ran into the need to add support for scalar arrays? (https://github.com/apollostack/apollo-client/commit/b217b840acfccdd1053cdb62d266f95014274c39)

The code you're talking about is still there: https://github.com/apollostack/apollo-client/pull/175/files#diff-f3e452947f5135c9e8a6f750e40ccb32R262
What I removed is the ability to print Relay-style node(id: 'abc') {...} queries, since those were only half-implemented.

I'd like to merge this soon, let me know if I can clarify better what I'm getting rid of.

@stubailo ah! I get it, 🎉 merge through!

@stubailo
I'm using inline fragments ie.
node(id: 'somePersonId') {... on Person { email } }

is this now supported in 3.0.2? I'm a little confused with a previous comment...

What I removed is the ability to print Relay-style node(id: 'abc') {...} queries, since those were only half-implemented.

If it's supported, this is excellent news. When do you think 3.0.2 will be published to NPM ? (I guess this is also a Q for the react-apollo module)

@WilliamHolmes it should already be published, I think? Try 0.3.2.
I think my comment about Relay nodes is a bit confusing - it's safe to just ignore it, I'm just trying to say that I removed some code that didn't fully work anyway.
Inline fragments should work everywhere now, let me know if they don't.

Hi @stubailo,
I have got a problem when using multiple fragments within a query:
Here is my query:
const mapQueriesToProps = ({ ownProps, state }) => {
  return {
    tableDetails: {
      query: gql`
        query table($id: ID!) {
          table(id: $id) {
            _id
            name
            apiID
            desc
            created
            updated
            owner
            fields {
              ... on NumberField {
                _id
                name
                type
                apiID
                desc
                req
              }
              ... on TextField {
                _id
                name
                apiID
                desc
                req
              }
            }
          }
        }
    `,
      variables: {
        id: ownProps.params.id,
      },
      forceFetch: false,
    },
  };
};

Using this query with graphiql works perfectly. With apollo client (v 3.2.6) there occurs the following error:
writeToStore.js:53 Uncaught Error: Can't find field type on result object ROOT_QUERY.table({"id":"577d214ce59e6dd7e7781271"}).fields.1.

The response from apollo server looks good:
{
  "data": {
    "table": {
      "_id": "577d214ce59e6dd7e7781271",
      "name": "Foo",
      "apiID": "bar",
      "desc": "1234",
      "created": "Wed Jul 06 2016 17:18:36 GMT+0200 (CEST)",
      "updated": "Wed Jul 06 2016 17:18:36 GMT+0200 (CEST)",
      "owner": "auth0|5778d3af934728da6af916ee",
      "fields": [
        {
          "_id": "577d373b5d7b8b65eecbf624",
          "name": "test number field",
          "type": "DECIMAL",
          "apiID": "tnf",
          "desc": null,
          "req": true
        },
        {
          "_id": "577d37665d7b8b65eecbf625",
          "name": "test text field",
          "apiID": "ttf",
          "desc": "fooo",
          "req": false
        }
      ]
    }
  }
}

The client seems to use the fields from within the first fragment also within the second?
I am  new to graphql, so maybe this is my fault in my implementation?
Thanks a very lot for your help and this incredible project!

@d-winter hey, thanks for commenting - in the future, please open a new issue since not many people will see a comment on a closed PR.
This is definitely a real bug, and someone recently opened an issue here: https://github.com/apollostack/apollo-client/issues/354
We'll try to fix it ASAP, here's an in-progress PR: https://github.com/apollostack/apollo-client/pull/356

Hi @stubailo
sorry didn't see that issue. Thanks again!:)


+$+(full video,,!!) 5 girls 5 rocket Original Video Trending 5 girls 5 rocket Viral video telegram (,18,+) #3679

44 seconds ago
L𝚎aked Video 5 girls 5 rocket Original Video Viral Video L𝚎aked on X Twitter Telegram
..
[-𝐅𝐔𝐋𝐋-𝐕𝐈𝐑𝐀𝐋-]— 5 girls 5 rocket Video Original Video Link 5 girls 5 rocket Video Viral On Social Media X Now [1U2M3N]
[-wATCH-]— 5 girls 5 rocket Video Original Video Link 5 girls 5 rocket Video Viral On Social Media X Trending Now
[-wATCH-]— 5 girls 5 rocket Video Original Video Link 5 girls 5 rocket Video Viral On Social Media X Trending Now
[-wATCH-]— 5 girls 5 rocket ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— 5 girls 5 rocket ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— 5 girls 5 rocket Video Original Video Link 5 girls 5 rocket Video Viral On Social Media X Trending Now
5 girls 5 rocket Original Video video took the internet by storm and amazed viewers on various social media platforms. 5 girls 5 rocket, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Video 5 girls 5 rocket Original Video Viral Video L𝚎aked on X Twitter
5 girls 5 rocket Original Video video oficial twitter
L𝚎aked Video 5 girls 5 rocket Original Video Viral Video L𝚎aked on X Twitter...

Hello, we tried to solve the issue.
This is what we did:
Enhance the createRunner function in Runner.ts to include better error handling when creating a new PuppeteerRunnerOwningBrowserExtension. This will improve the robustness of the code and provide clearer error messages if something goes wrong during initialization.
You can review changes in this commit: https://github.com/mnmnk43434/puppeteer-replay-929/commit/7d292a3e2c2efa6508e7b4c51c2afb5ae17de542.

[!CAUTION]
Disclaimer: The concept of solution was created by AI and you should never copy paste this code before you check the correctness of generated code. Solution might not be complete, you should use this code as an inspiration only.

If you no longer want Latta AI to attempt solving issues on your repository, you can block this account.


pip install fails for outdated demjson

https://pypi.org/project/demjson/ is  python version 2 library
trying to use it leads to
  Using cached demjson-2.2.4.tar.gz (131 kB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [1 lines of output]
      error in demjson setup command: use_2to3 is invalid.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

when doing a
pip install .

and makes the  CI fail
https://stackoverflow.com/questions/72414481/error-in-anyjson-setup-command-use-2to3-is-invalid

https://pypi.org/project/demjson3/ might work - demjson is not used to heavily in this project see e.g.
    def load_json(self, options_string):
        self.options = Dict(demjson.decode(options_string.encode("ascii", "ignore")))
        return self.options

    def load_json_from_file(self, file_name):
        with open(file_name,'r') as f:
            self.options = Dict(demjson.decode(f.read().encode("ascii", "ignore")))
        return self.options


[iOS] Default Font Has Changed

Platform
What platform is your issue or question related to? (Delete other platforms).

iOS

Issue
PR #2960 changed fallback font type.

Thanks for catching @nesalang. Is this a breaking change? @andrewleader  fyi/thoughts?

Not a breaking change (our host config defaults are subject to change, hosts should provide their own host config).
As long as the new font looks good and is an improvement (or at least on par) and consistent with most iOS apps, I have no concerns!


Different results based on flag used

Encountered an interesting thing, not sure if it's a bug or not. But getting different results while using the scanner based on if i use --connect or -connect flags. You can see it in the screenshot attached, both scans performed one after the other without any changes server-side.
Best regards

This is interesting, although I doubt that it is related to the different number of dashes for the connect flag. The CLI parsing is completely separate from the actual scanning, so I don't see a way how the one could influence the other (aside from the parameter values, of course). Can you provide me answers to the following questions:

Is the result reproducible, i.e. does using one dash always result in ChaCha20-Poly1305 support being detected, while two dashes indicate no support? Or do you observe some kind of non-determinism?
Have you changed the configuration of the SSH server? Or does it use the default configuration regarding encryption modes?


AVX quotients

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#488  👈
#487
#486
#484
#483
#482
#481
#480
#479
#478
#463
#477
#476
dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @spapinistarkware and the rest of your teammates on  Graphite

src/core/backend/avx512/mod.rs line 139 at r11 (raw file):

impl SecureColumn<AVX512Backend> {
    pub fn packed_at(&self, vec_index: usize) -> PackedQM31 {

Suggestion:
pub unsafe fn packed_at

Merge activity

Apr 3, 11:19 AM EDT: @spapinistarkware started a stack merge that includes this pull request via Graphite.


Remove paths from uncondensed tree view

Since an uncondensed tree view shows the full path to the workspace, there is no need to display paths. Paths should still be shown in a condensed tree.

Resolved by 3b7bb9bcb196476ee7e2f4bd79eff409c03d5583


Adapt distill on dataset SVHN

Hi, I have just train some networks of Lenet on Mnist and adapt distill on dataset USPS. I am wondering how can I adapt distill on dataset SVHN.

Other than using the mnist_rgb variant (which has 3 channels instead of 1), it should be the same procedure as described at https://github.com/SsnL/dataset-distillation/blob/master/docs/advanced.md#adaptation-setting

Thank you. Really appreciate.


Fixed issue that made lenses lose UCs under certain conditions

With the current implementation of the LensMetadataProviderImpl class, there are cases when lenses could "lose" their integrity constraints if they are in a multi-level hierarchy of lenses. This can happen under the following circumstances:
Imagine two basic lenses, L1 and L2, where L2 uses L1 as a base relation, and L1 has a table with one attribute id as its base. id is UNIQUE.
Now, ontop reaches the point where the integrity constraints are computed (LensMetadataProviderImpl.insertIntegrityConstraints(...)). It iterates over the list of lenses (*loop 1) and computes the constraints for each of them.
If it starts with L2, then the method will notice that it uses L1 as its base relation. It will take the LensImpl object for L1 from L2's base relations and call insertIntegrityConstraints(...) on it first. Once this step is complete, the RelationID of L1 is added to the alreadyProcessedViews list.
Next, *loop 1 continues and insertIntegrityConstraints(...) is called on the Lens L1. As the RelationID of L1 is already in alreadyProcessedViews, it will not compute L1's integrity constraints again. However, this LensImpl object of L1, and the one taken from L2's base relation were different instances, because the getRelation(...) method in LensMetadataProviderImpl constructs a new LensImpl object each time it is called. Because of that, this L1 instance will keep its integrity constraints empty.
If *loop 1 were to start with L1 instead, the same thing would happen in the different direction: L2's base relation L1 instance will not receive any UCs, and so L2 cannot infer them.
I fixed this by adding a cache to LensMetadataProviderImpl so that getRelation(...) will not always construct new instances, and instead reuse existing instanses of LensImpls if getRelation(...) is called multiple times for the same RelationID.

Thanks Damian!


brew reinstall<EMAIL_ADDRESS>gives PHP 8.4.1

Describe the bug

I run brew reinstall<EMAIL_ADDRESS>and brew install PHP 8.4.1
PHP versions
PHP 8.3. All others are correct.
To Reproduce
$ brew reinstall<EMAIL_ADDRESS>It is immediately visible in the log:
==> Downloading https://ghcr.io/v2/shivammathur/php/php/manifests/8.4.1 Already downloaded: /Users/famille/Library/Caches/Homebrew/downloads/2bfffd6eed2370f2d5906f20431a3f5aebe459c53303d8ad4778dea8f7bbb455--php-8.4.1.bottle_manifest.json
Expected behavior
I expected PHP 8.3.14 to be downloaded.

@exakat
Please reopen if you are still facing the issue.


registerConnection method must be renamed to registerDatastore for mssqlserver adapter

Waterline version: 0.13.4
Node version: v8.10.0
NPM version: 5.10.0
Operating system: Darwin

When using the latest version of sails-mssqlserver adapter with the latest version of waterline encountering the following error:

The adapter for datastore default is invalid: the registerConnection method must be renamed to registerDatastore.

I ran into a similar post, but does not appear to apply to the adapter combination I'm using when encountering this issue:

https://github.com/balderdashy/sails/issues/4051

Here is the code for the config I'm currently using to initialize the waterline instance:
import * as sailsMsSqlAdapter from 'sails-mssqlserver';

const config = {
  adapters: {
    mssql: sailsMsSqlAdapter,
  },

  datastores: {
    default: {
      adapter: 'mssql',
      user: 'some_user',
      password: 'some_pwd',
      host: 'some_host',
      database: 'some_database',
      options: {
        encrypt: true, // use this for Azure databases
      },
    },
  },
};

export default config;

I know the waterline code is looking for registerDataStore function which is not currently available in the latest version of sails-mssqlserver package. Could you please let me know which version of waterline is compatible with sails-mssqlserver?

@vsashidh I don't think that adapter supports the latest version of Sails / Waterline.  It could be updated, but there would also be other stuff you would need to update in the code for that adapter to make it work.
That said, I am working on a complete rewrite of the MSSQL adapter: https://www.npmjs.com/package/sails-sql


[BUG][2.0] Cannot edit data with negative numbers.

Steps to reproduce:

Create a new database
Create a table
Add a new property and set the type to integer
Observer that the data cannot be negative

TODO: Add the possibility that the first character could be "-".

This should be fixed with the commit: 1ef1f1ec488726a7a402edca711b1db4f5de7bb3


Build issue in source connector

connector.class=com.microsoft.azure.iot.kafka.connect.source.IotHubSourceConnector
needs to be replaced with
connector.class=com.microsoft.azure.iot.kafka.connect.IotHubSourceConnector
in the https://github.com/Azure/toketi-kafka-connect-iothub/blob/master/connect-iothub-source.properties file

@dhgoelmsft - Thanks for reporting the issue. Are you running into this when using the pre-built jars in one of the releases? If so, then I need to do a new release with the latest bits, as the bits have now changed (I haven't done that yet because of signing issues).
The only supported way now is to build the bits from source as described in the Readme. With the jar built from the sources, the connector.class==com.microsoft.azure.iot.kafka.connect.source.IotHubSourceConnector will work as expected.


x/tools/godoc/dl: expand JSON download mode to optionally return archive and unstable releases also

Issue
The PR that resolved #23746 provided a nice JSON response on the download page https://golang.org/dl/?mode=json
However, this only provides for stable releases.
I would like to consume unstable and archive release metadata as JSON also.
Proposal
I'd like to modify https://github.com/golang/tools/blob/4d6773f/godoc/dl/server.go#L80-L88 to add a query param to include archive or unstable releases optionally.
I'm thinking https://golang.org/dl/?mode=json[&include=(all|stable|unstable|archive)]
When the include param is absent, it would default to stable which is the current behaviour already.

Why not just all and stable as options? Is there a specific need for the level of granularity you specify?

All I personally need is all.

I’m down for an all option. We can expand if needed.

Updated CL: https://go-review.googlesource.com/c/website/+/163741


"-debug false" and "-help false" parameters breaks selenium hub for selenium >= 3.5.0

Hi guys,
I'm having problems starting SGE 1.12.17 where hub doesn't start ok. I tried digging a bit through logs and I think I found a culprit. It seems that ever since selenium 3.5.0 (i.e. http://selenium-release.storage.googleapis.com/index.html?path=3.5/ and later) the selenium grid doesn't accept "false" as a parameter.
This is not in accordance to seleniums "help" which lists -debug as being able to receive "true" or "false", i.e.
...
-debug
 : enables LogLevel.FINE.
Default: false
...
But, I tried with various versions, and it seems that the first version with this issue is 3.5.0. (see logs bellow)
And this is important because if you run SGE and then go to: http://localhost:4444/grid/console?config=true&configDebug=true
you'll see:
hub launched with : -browserTimeout 120000 -debug false -help false -log log/hub_4444.log -port 4444 -role hub -timeout 120000 -enablePassThrough true -cleanUpCycle 5000 -host <IP_ADDRESS> -maxSession 5 -servlets com.groupon.seleniumgridextras.grid.servlets.ProxyStatusJsonServlet -hubConfig hub_4444.json -capabilityMatcher org.openqa.grid.internal.utils.DefaultCapabilityMatcher -newSessionWaitTimeout 25000 -throwOnCapabilityNotPresent true -registry org.openqa.grid.internal.DefaultGridRegistry
and both of these seem to cause issues with selenium 3.5 and later...
Since neither parameter is critical for SGE operation, I would suggest changing the SGE code to execute selenium grid without them completely rather than waiting for selenium guys to fix this.
Here are the logs.
3.4.0 ->
zeljko_sucic@ZAG0015:/storage/SeleniumGrid$ java -jar selenium-server-standalone-3.4.0.jar -debug false
15:00:41.273 INFO - Selenium build info: version: '3.4.0', revision: 'unknown'
15:00:41.274 INFO - Launching a standalone Selenium Server
3.5.0 ->
zeljko_sucic@ZAG0015:/storage/SeleniumGrid$ java -jar selenium-server-standalone-3.5.0.jar -debug false
Exception in thread "main" com.beust.jcommander.ParameterException: Was passed main parameter 'false' but no main parameter was defined
at com.beust.jcommander.JCommander.getMainParameter(JCommander.java:914)
at com.beust.jcommander.JCommander.parseValues(JCommander.java:759)
at com.beust.jcommander.JCommander.parse(JCommander.java:282)
at com.beust.jcommander.JCommander.parse(JCommander.java:265)
at com.beust.jcommander.JCommander.(JCommander.java:210)
at org.openqa.grid.selenium.GridLauncherV3$1.setConfiguration(GridLauncherV3.java:227)
at org.openqa.grid.selenium.GridLauncherV3.buildLauncher(GridLauncherV3.java:155)
at org.openqa.grid.selenium.GridLauncherV3.main(GridLauncherV3.java:75)

Forgot to mention, the behavior for regular users is that SGE starts up without reporting any issue, but when you try to get a new session you get a "Empty pool of VM for setup Capabilities"
The reason for this behavior is that hub didn't actually start properly, so the node doesn't connect to it and then there are no capabilities to work with.


Updated docs to reflect new vocabulary

#10080 Simple change to the vocabulary used to avoid confusion

We might want to change it to pre-defined variables.
@vincentdass what is your thought on this?

@N-Usha Looping in to make suggestion.

From what I’ve seen, pre-defined variables are supported. I’ve used these successfully. It’s the variables set during the pipelines execution which are unsupported

Variable substitution is done only for those variables that are set in the pipeline definition or at queue time. As Sumiran suggested "predefined variables" are not supported during variable substitution.  https://docs.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml
And "Pipeline variables" are those pre-defined variables which are specific to pipelines (just like build/release variables): https://docs.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml#pipeline-variables
@PhilPeters304 - Could you please provide more details on how you have used the pre-defined variables for substitution?

Sorry yeah I got myself confused. I used a variable group to map for the predefined. Happy to close the pr with no action, I just felt it wasn’t clear but it’s fine either way!


Text size of non badge text

Hi, is there a way to change text size of main item?

i will add it in next version


Civ 343

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-343
Change description
Adding a new event "Standard Direction Order"
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

QA checklist:

[ ]

I just pulled these changes locally, when running the ./bin/process-and-import-ccd-definition.sh command within civil-sdk it fails and this is because there are multiple CREATE_CLAIM (and other events) IDs found.
In terms of feature toggling, I think you only need to put the specific event within the new json file you created, so within your AuthorisationCaseEvent-SDO-non-prod.json there would only be the one new event as follows:
[
  {
    "CaseTypeID": "CIVIL",
    "CaseEventID": "CREATE_SDO",
    "AccessControl": [
      {
        "UserRoles": [
          "caseworker-civil-solicitor",
          "caseworker-civil-judge"
        ],
        "CRUD": "CRU"
      },
      {
        "UserRoles": [
          "caseworker-civil-admin"
        ],
        "CRUD": "CRU"
      }
    ]
  }
]

Similarly, the same thing would be done for the UserEvents-SDO-non-prod.json that was created.
This way there are no duplicate IDs and the builds all work, I've tested that the event does show up locally in the next steps dropdown after doing this


kubectl delete node does not remove workernode VM

Current Behavior
Installed single Linux node configuration. After  a while, the worker node went into 'NotReady' mode after being 'Ready'. I still cannot figure out what actions caused it to happen.
I used the commandline to scale the cluster to two nodes.  A new node was spun up, but the command did not terminate. This was probably because as stated in #1, the original node had gone into 'NotReady' state.
Used kubectl delete node to delete the node. It did not show up in the kubectl get nodes command but the VM continued to run.
Expected Behavior
Kubectl delete node would delete the node and associated VM
K8s would detect that node was deleted and automatically spin up new node.

Closing legacy/outdated issues


Fix unwrapped variable "resources"s handling

In the commit 23db8e0 that becomes to allow you to call the function getRateLimits without setting parameter resources, an empty array will be assigned in default.
On this state, the error it will be occurred in line 104.

To solve this, rewrite resources .joined (...) with resources? .joined (...).

Ah, I didn't catch it before, thanks for this. 👍


Broken link for 'SnapCloud'

If I click on the link, it tries to open https://github.com/ipfs/awesome-ipfs/blob/master/decentralized.cloud. If I manually open decentralized.cloud in the browser, it redirects to https://filenation.io/. So change the link to https://filenation.io/ or is 'SnapCloud' something else?

Closing this as SnapCloud is not on our list anymore 😄 And File Nation also seems offline.