iPad connection to Mac running dnscrypt-proxy

I have set up dnscrypt-proxy to run on my iMac (10.13.4) using Cloudflare servers. I have installed dnscrypt-proxy as a service and everything works as expected.
However, when I plug in my iPad Pro 10.5 (iOS 11.3) to the iMac, the iPad loses internet connectivity. On the iPad, the wireless indicator on the status bar disappears. Settings show that the iPad is still connected to WIFI, but Safari, etc no long have internet connectivity. If I run Airport Utility on the iPad while connected to the iMac, it finds and communicates with an Apple Time Capsule which is on the network, so wifi is working, it is just internet connectivity that is gone. Also, the usb connection between the iMac and the iPad works properly.
Can anyone explain this and/or suggest a fix?

Huh? I've never heard of that before. I recommend to look at Apple Support, Alternatively you can reset the network settings in the iPad: Settings>General>Reset (it's at the very bottom)> Reset Network Settings note this will wipe any remembered WiFi passwords so you need to re-enter them.

Typically the Router will have dhcp which will give any connected device the recommended DNS servers to connect to. By using dnscrypt-proxy your iMac is using it's own DNS settings which does not impact the rest of the network. When the iPad is connected to the iMac, the iPad would still use it's own DNS settings and wifi, so I don't know how dnscrypt-proxy would have an impact.

On https://discussions.apple.com/thread/2746307 there is a mention of Internet sharing, make sure that it's off:


Carousel dots

Added less opaque black color to carousel dots that are not active.

Just as a general rule of thumb for PRs
try to keep strictly related to the Github Issue as possible (unless the issue is just that big).
I think this has changes about the progress bar, Instagram etc. which make it hard to merge.

Merged in https://github.com/AdvisorySG/dawn-advisory-theme/commit/cb9aab63d5588da5220b3cab1114703e7fe1449c.


Fix nested error reporting

Fixes #441

@bluebill1049, is there anything else you'd like to address on this PR?

I am quite busy at the moment, but I will find some time to review it properly in the following days. thanks for the help <3

The problem is that there is no easy way to fix or monkey patch this other than maintaining a fork. Also, this is a real feature bug for those who use the all criteria.

I was having the same error on my application and I can confirm this PR solves the issue. Is there something missing so we can have this in a future release of resolvers?

@georgekaran , this is a terrible but functional workaround for the issue:
import {ValidationError} from "yup";
import {yupResolver as baseResolver} from "@hookform/resolvers/yup";
import BaseSchema from "yup/lib/schema";

/**
 * Workaround for https://github.com/react-hook-form/resolvers/issues/441
 */

function fixErrorNesting(errors: Record<string, any>): Record<string, any> | any[] {
  const fieldErrors: Record<string, any> = {};

  for (const [key, value] of Object.entries(errors)) {
    if (typeof value !== 'object' || value === null) {
      fieldErrors[key] = value;

      continue;
    }

    if (Array.isArray(value)) {
      fieldErrors[key] = value.map(fixErrorNesting);

      continue;
    }

    if (!('0' in value)) {
      fieldErrors[key] = fixErrorNesting(value);

      continue;
    }

    const copy = {...value}
    const list = [];

    let index = 0;

    while (index in copy) {
      list.push(fixErrorNesting(copy[index]));
      delete copy[index];
      index++;
    }

    Object.assign(list, copy);

    fieldErrors[key] = list;
  }

  return fieldErrors;
}

export const yupResolver: typeof baseResolver = (schema, schemaOptions = {}, resolverOptions = {}) => {
  const schemaClone = (schema as any).clone() as BaseSchema;

  const validate = schemaClone.validate.bind(schemaClone);
  const validateSync = schemaClone.validateSync.bind(schemaClone);

  function fixError<T>(error: T): T {
    if (error instanceof ValidationError) {
      error.inner.sort((left, right) => {
        if (left.path === right.path) {
          return 0;
        }

        return (left.path ?? '') > (right.path ?? '') ? 1 : -1
      });
    }

    return error;
  }

  schemaClone.validate = async (...args) => {
    try {
      return await validate(...args);
    } catch (error) {
      throw fixError(error);
    }
  };

  schemaClone.validateSync = (...args) => {
    try {
      return validateSync(...args);
    } catch (error) {
      throw fixError(error);
    }
  };

  const resolver = baseResolver(schemaClone as typeof schema, schemaOptions, resolverOptions);

  return async (values, context, options) => {
      const result = await resolver(values, context, options);

      return {
        ...result,
        errors: fixErrorNesting(result.errors) as typeof result.errors,
      }
  };
};

It should definitely be fixed.

Thanks @marcospassos it worked like a charm, but it should definitely be shipped native 😕


[iOS] Twitter Authorize Gives Error

I did every step on readme. I get this error
Possible Unhandled Promise Rejection (id: 0):
Cannot read property 'configureProvider' of undefined
TypeError: Cannot read property 'configureProvider' of undefined

I'm getting this same error using facebook on iOS

It looks like it's working for me now after I re-built the debug config scheme in XCode and re-ran on simulator

Did you link react-native-oauth to your project?

@cihancil and @smkhalsa ^^


Updated phpdoc return type for getExceptionName

getExceptionName can return null, as described in phpdoc.

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Tests pass?

Fixed issues

Thanks!


Pytest version conflict at installing project dependencies

The following command generates an error caused by pytest==3.4.0 pinned on requeriments.dev.txt.
$ pip install -r requirements.dev.txt --use-feature=2020-resolver

ERROR: Cannot install pytest==3.4.0, pytest-cache 1.0, pytest-cov 2.5.1 and pytest-flask 0.15.0 because these package versions have conflicting dependencies.
The conflict is caused by:
The user requested pytest==3.4.0
pytest-cache 1.0 depends on pytest>=2.2
pytest-cov 2.5.1 depends on pytest>=2.6.0
pytest-flask 0.15.0 depends on pytest>=3.6
To fix this you could try to:

loosen the range of package versions you've specified
remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies

Just removing the pytest version from requirements.dev.txt for getting the latest version may solve the problem, as done on .travis.yml that runs pip install --upgrade pytest.

Thanks for reporting this.
Related to #95.

I did a pull request that fix this specific pytest problem. Please, check it.


Bugfix/fbp 201 boundary events wrong behavior

Fixes #201

Codecov Report

Merging #279 (77222db) into master (1b44b1e) will increase coverage by 0.09%.
The diff coverage is 80.00%.

:exclamation: Current head 77222db differs from pull request most recent head 913f78a. Consider uploading reports for the commit 913f78a to get more accurate results

@@             Coverage Diff              @@
##             master     #279      +/-   ##
============================================
+ Coverage     62.01%   62.11%   +0.09%
- Complexity     1276     1281       +5
============================================
  Files           185      185
  Lines          6090     6103      +13
  Branches        819      822       +3
============================================
+ Hits           3777     3791      +14
+ Misses         2049     2047       -2
- Partials        264      265       +1

Flag
Coverage Δ

unittests
62.11% <80.00%> (+0.09%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ender/elements/shapes/AnyShapeNestableIconShape.kt
77.50% <57.14%> (-4.32%)
:arrow_down:

...ore/render/elements/edges/BaseEdgeRenderElement.kt
70.83% <100.00%> (+0.41%)
:arrow_up:

.../core/render/elements/shapes/ShapeRenderElement.kt
83.93% <100.00%> (+2.55%)
:arrow_up:

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 1b44b1e...913f78a. Read the comment docs.


Kubelet blows away manual changes to mirror pods

I found my fluentd pods (mirror pods) that were created by kubelet.  I made a manual change to one of them (changed the image).  I updated the pod successfully.  Kubelet immediately destroyed my changes.
As per conversation with @dchen1107, we should probably respect the changes made through the apiserver or else maybe block them?  Proposal was to save the hash of the file into an annotation.  Upon reading a mirror pod in apiserver that does not match the disk, check the hash - if it matches, assume the user changed it in the API.  If it doesn't match, blow it away and use the file.  Something like that...

My preference would be to just block changes to mirror pods. The kubelet isn't going to rewrite the manifest file on the node (or from the manifest URL) and it seems like that is the canonical source for the pod. If you want to have mutable pod definitions, you should create them through the apiserver in the first place. For the fluentd pods, we should move them out of the manifest and into a daemon controller (once the daemon controller supports updates).

I agree with @roberthbailey. Allowing changes to mirror pods through the apiserver can certainly become a source of confusion. For example, if user made different changes to the manifest file and the pod through apiserver, kubelet would be left to resolve the conflicts, which should really be apiserver's job. It'd also be hard for user to debug which pod is running on the node given that apiserver always accepts the update to the pod. In addition, there may be potential "regression" of pods when kubelet restarts, in which case it will likely to start the pod based on the manifest file before getting updates from the apiserver.
IMO, there should be one source of truth for a single pod. Given that we need to support standalone kubelets (when there is no apiserver or apiserver is temporarily unavailable), kubelet should respect the manifest files. Daemon controller seems more suitable for other use cases.
(FWIW, initially we wanted to make mirror pods read-only, or at least make it clear at the api level that it's a mirror pod, but the proposal was rejected).

Lowering the priority since the future of static/mirror pod is unclear (may be deprecated) for use cases beyond non-master components.

Let's close this one and discuss how to proceed in #16627


Feature request: Mattermost reporter

Mattermost is a popular open-source, self-hosting capable alternative to Slack. It would be highly appreciated if you could look into creating a reporter for that platform.
If you decide to implement it I would definitely be willing to test and provide feedback.

Hello,
The Mattermost integration is now available with the reportHTTP module. This is currently deployed in dev. Please, provide me with feedback. In particular we could describe a specific set of templates for mattermost.

Hi Massimo,
great, having a general webhook mechanism is certainly the most flexible approach. I will give it a try and report back.

So I finally came around to testing the reporter module and as far as I tested it works flawlessly.
The config we're using it with:
# Report to Mattermost channel
reports:
  - file: reportHTTP
    channels:
      - hijack
      - newprefix
      - visibility
      - path
      - misconfiguration
    params:
      templates:
        default: '
  {"attachments": [
  {"fields": [ {"title": "Prefix:", "value": "${prefix}", "short": "false"},
  {"title": "Expected from:", "value": "AS ${asn}", "short": "true"},
  {"title": "Seen from:", "value": "AS ${neworigin}", "short": "true"},
  {"title": "Since:", "value": "${earliest}", "short": "true"},
  {"title": "Details:", "value": "[BGPlay](${bgplay})", "short": "true"},
  {"title": "Event description":, "value": "${summary}"} ],
  "text": "#bgpalerter #${type}", "color": "#ffffff"}]}'
        visibility: '
  {"attachments": [
  {"fields": [ {"title": "Prefix:", "value": "${prefix}", "short": "false"},
  {"title": "Originating from:", "value": "AS ${asn}", "short": "true"},
  {"title": "Since:", "value": "${earliest}", "short": "true"},
  {"title": "Details:", "value": "[BGPlay](${bgplay})", "short": "true"},
  {"title": "Event description", "value": "${summary}"} ],
  "text": "#bgpalerter #${type}", "color": "#ffffff"}]}'
      isTemplateJSON: true
      headers:
      showPaths: 0 # Amount of AS_PATHs to report in the alert
      hooks:
        default: WEBHOOK_URL

which results in messages like these

Adding additional properties or modifying field descriptions can be easily done by adapting the fields array.

Hi @fstolba,
This is great!
I'm going to create a documentation page dedicated to mattermost and provide the template you wrote.
Ciao,
Massimo

Glad I could be of help. Thanks again @massimocandela for implementing this feature, it helps integrate BGPalerter much more seamlessly with our other tools.

Hi @fstolba, I added this here: https://github.com/nttgin/BGPalerter/blob/dev/docs/report-http.md#mattermost Thanks


DF Chat Enhancements: Simple Calendar Timestamps error

When using the "Use Simple Calendar for Chat Timestamps" option, the feature works fine until the page is reloaded, at which point the hour, month, and day are all off (hour is two hours ahead, month goes back 1 month, day jumps forward 2 weeks). Have no idea why it happens, and another reload sometimes fixes the problem, but the display is so erratic that it essentially makes the feature unusable.
Tested on PF2e system version 4.6.8, Foundry v10 build 291

This remains an issue using PF2e 4.11.2, v10.291.


Fix osds parsing regex

Osds parsing regex didn't return a match when the location contained a dot. (such as fqdn do)

Thanks for the change Guillaume. I have one nit though. Since now, microceph snap supports outputting the disk list command in json, using regex seems a bit overkill. Also, the tabular output format may change in future. May I suggest to use json output instead?

I'm using microceph             0+git.0819c49  817    reef/stable         canonical✓  held and the command does not have json format.
List servers in the cluster

Usage:
  microceph disk list [flags]

Global Flags:
  -d, --debug       Show all debug messages
  -h, --help        Print help
      --state-dir   Path to store state information
  -v, --verbose     Show all information messages
      --version     Print version number

@gboutry given that disk list json is still a few days away from being available in stable, is this change still relevant ? If that's the case i'll merge it..

It's still relevant :)


SendRawTransaction's interface has changed

Hello,
One more bug:
                {
                    {"hexstring", RPCArg::Type::STR_HEX, RPCArg::Optional::NO, "The hex string of the raw transaction"},
                    {"maxfeerate", RPCArg::Type::AMOUNT, /* default */ FormatMoney(DEFAULT_MAX_RAW_TX_FEE_RATE.GetFeePerK()),
                        "Reject transactions whose fee rate is higher than the specified value, expressed in " + CURRENCY_UNIT +
                            "/kB.\nSet to 0 to accept any fee rate.\n"},
                },

^ for sendrawtransaction, the second parameter used to mean "allow high fees" by setting it to "true", it now needs to be set to an amount.

This is supposed to be handled here:
	// Starting from bitcoind v0.19.0, the MaxFeeRate field should be used.
	case BitcoindPost19:
		// Using a 0 MaxFeeRate is interpreted as a maximum fee rate not
		// being enforced by bitcoind.
		var maxFeeRate int32
		if !allowHighFees {
			maxFeeRate = defaultMaxFeeRate
		}
		cmd = btcjson.NewBitcoindSendRawTransactionCmd(txHex, maxFeeRate)

but for some reason it doesn't

Ok it's because this:
// parseBitcoindVersion parses the bitcoind version from its string
// representation.
func parseBitcoindVersion(version string) BackendVersion {
	// Trim the version of its prefix and suffix to determine the
	// appropriate version number.
	version = strings.TrimPrefix(
		strings.TrimSuffix(version, bitcoindVersionSuffix),
		bitcoindVersionPrefix,
	)
	switch {
	case version < bitcoind19Str:
		return BitcoindPre19
	default:
		return BitcoindPost19
	}
}

is using wrong values to trim the prefix.
The node sends out /LitecoinCore:0.21.2
But the prefix expects bitcoindVersionPrefix = "/Satoshi:"

I suggest replacing with something like this:
// parseBitcoindVersion parses the bitcoind version from its string
// representation.
func parseBitcoindVersion(version string) BackendVersion {
	// Trim the version of its prefix and suffix to determine the
	// appropriate version number.
	// find the first ":" and trim everything before that
	var i int
	for i = 0; i < len(version)-1; i++ {
		if version[i] == ':' {
			break
		}
	}
	version = version[i+1:]
	switch {
	case version < bitcoind19Str:
		return BitcoindPre19
	default:
		return BitcoindPost19
	}
}

Can you open a PR with this change please?

If it's ok with you, absolutely yes

fixed with #20


Update instruction for Patch command

#603
Summary
The origin statements might misleading the usage of patch.
Promote to modify the instruction.
Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG
[x] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[x] I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

Sorry, my fault.


Add PiYArray?

First, thanks for this incredible library and for such thorough, readable docs.
Many computer vision applications use only greyscale input. Extracting the Y plane out of PiYUVArray is wasteful, though, since it's a fair amount of work to construct the YUV array in the first place.
In just a few minutes, I cobbled together a PiYArray implementation that mimics PiYUVArray but never constructs the color planes. I'm not doing much other work (yet), but it almost doubled my framerate.
PiYArray is easy to build, but I think it might be of broad enough to use to warrant being included. If you'd like to see it included, I'd be happy to send a pull request.

Sounds like a good idea. Can you provide the patch via a pull request ?

This would be very useful as applications often approximate image intensity using the Y component.

On Tue, 01 Mar 2016 05:28:52 -0800
Russ<EMAIL_ADDRESS>wrote:

This would be very useful as applications often approximate image intensity using the Y component.

I wonder if it would not be better to have a unic container which would have:

rgv_array
yuv_array
y_array
raw_array (?)
properties, all of them lazy evaluated and memoized as rgb_array for the YUV-container.

I'd rather keep the current separate class structure, but API decisions are better kept in one hand, so I'll defer to your preferences. Let me know what they are, and I'll pull together a PR, although it may take a week or three.

In case you decide you want to move forward without me on this (if I am too slow), here's an out-of-tree, doc-less code snippet:
class PiYArray(picamera.array.PiArrayOutput):

	def flush(self):
		super(PiYArray, self).flush()
		resolution = self.size or self.camera.resolution
		fwidth, fheight = picamera.array.raw_resolution(resolution)
		y_len = fwidth * fheight
		uv_len = (fwidth // 2) * (fheight // 2)
		data = self.getvalue()
		if len(data) != (y_len + 2 * uv_len):
			width, height = resolution
			raise PiCameraValueError('Incorrect buffer length for resolution %dx%d' % (width, height))
		self.array = np.frombuffer(data[:y_len], dtype=np.uint8)
		self.array.shape = (fheight, fwidth)

Before anybody puts any significant time into this, I'd have a quick look at what's coming up in 1.11 (which I've finally made some progress on - if I can close off #218 next week I'm planning to go for a release shortly after). Specifically, have a look at the "capture to buffer" functionality (#241) and how it can be used to capture just the Y plane with minimal overhead (see the end of the YUV recipe).
I suspect the new capture-to-buffer is going to make the various Pi*Stream classes fairly redundant (though the analysis classes covering unencoded video will still be useful). Obviously I'll leave 'em around for backward compatibility but I don't see much use for them when you can capture straight into a numpy array.

Argh - sorry 1.11's taking so long - nearly there though, and in more good news for people wanting to capture for analysis the new code is a lot faster at doing RGB/BGR captures under certain circumstances too (depends on what pipeline's being constructed though).

1.11 implemented the capture to buffer functionality as detailed above (including the ability to capture "just the Y values"). If people still want a PiYArray, do feel free to re-open this (or post a pull-request); I'm happy to add something like that for the sake of completeness, but I think capture to buffer is probably quicker and easier.


Querying information on Windows drives produces an error if the drive is not ready.

On windows, The method BrFileSelector>>createTable throws errors when querying information (size, date) from drives that exist but that may not be ready, such as a SD card reader or a CD drive without media.
The solution to this problem is to test if the drive exists before getting this data.
Change this line:
https://github.com/feenkcom/Brick/blob/b5709dad04ea18ce94ed9cd9bdf08c8b66f10897/src/Brick/BrFileSelector.class.st#L182
to
ifFalse: [ eachItem exists ifTrue: [ eachItem humanReadableSize] ifFalse: [ '-' ]])].
Similarly, the modified date column:
https://github.com/feenkcom/Brick/blob/b5709dad04ea18ce94ed9cd9bdf08c8b66f10897/src/Brick/BrFileSelector.class.st#L187
Change to:
aLabel text:
				 (eachItem exists
				 	ifTrue:  [String
								streamContents: [ :s |
									eachItem creationTime printYMDOn: s.
									s nextPut: Character space.
							    	eachItem creationTime printHMSOn: s ]]
					ifFalse: ['-']) ].

With this change, the git tool can open folders in other drives without issues.
Here E: and F: are empty drives that triggered the error on my computer.

Catching FileException is a nice solution.


mold: wrap so it can find system libraries

Description of changes
Move mold to become mold-unwrapped, add a wrapped version as mold.
Currently mold mostly works, but the moment users start to
need to link system libraries they get linking errors.
It's been reported on github:
Re #242816
and on user forums, e.g.:
https://discourse.nixos.org/t/using-mold-as-linker-prevents-libraries-from-being-found
I've been using the script provided by roosemberth on discourse.nixos.org
and it works, so I wonder if we could fixing it once and for all.
I bet this approach has some problems, but in my experience the
fastest way to get something done right is to do it incorrectly and
publish it on the Internet, so here it is.
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

I added useMoldLinker stdenv adapter to use mold https://github.com/NixOS/nixpkgs/blob/master/pkgs/stdenv/adapters.nix

I added useMoldLinker stdenv adapter to use mold 299a7bd

I'm not very versed with stdenv. I don't think it's very helpful for e.g. Rust users, that will just change the linker in .cargo/config.toml and expect it to work, just like on other Linuxes. Is there something I'm missing here?

Im worried about having multiple bintools in an environment because AFAIK there hasn't been a case like that before and so all the setup assume one bintools which contains all the utils

Im worried about having multiple bintools in an environment because AFAIK there hasn't been a case like that before and so all the setup assume one bintools which contains all the utils.

I don't understand the details here, but ...

I think we should start by having a explicit mold-wrapped and leaving mold unwrapped

... that's good enough for me. Better than copy&pasting some script between my flakes, and a simple solution for affected users, I guess.

@Artturin Done, hopefully I combined the both suggestions correctly.

Remember to look at the CI
drop or fixup and reword the unnecessary commit

Before merge let's create tests for wrapped mold and the mold adapter  in pkgs/test/
I will do it but you can take a shot at it too if you want

I will do it but you can take a shot at it too if you want

Please go ahead if you can. I'll be happy to review and learn something, but I have no idea how to start, and not a lot of time ATM.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/using-mold-as-linker-prevents-libraries-from-being-found/18530/7

Tests added


protect against null-path

Description
This PR...

Fixes: #8747

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Bug Severity

[ ] BLOCKER
[x] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?
This is not re-produced bug. The fix is fairly simple. I have no idea how to reproduce but it resulted in data loss in a production VM. I think the best we can do is test upgrades from different versions. and see if anything happens.

How did you try to break this feature and the system with this change?

@blueorangutan package

@blueorangutan package

@DaanHoogland a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✖ el7 ✖ el8 ✖ el9 ✖ debian ✖ suse15. SL-JID 9258

@blueorangutan package

@blueorangutan package

@DaanHoogland a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 9259

@blueorangutan test

@vishesh92 a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[SF] Trillian test result (tid-9837)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 38030 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr8915-t9837-kvm-centos7.zip
Smoke tests completed. 99 look OK, 2 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_02_deploy_vm_with_extraconfig_kvm
Error
1.18
test_deploy_vm_extra_config_data.py

test_03_update_vm_with_extraconfig_kvm
Error
1.19
test_deploy_vm_extra_config_data.py

test_02_deploy_vm_on_specific_cluster
Error
1.13
test_vm_deployment_planner.py

test_03_deploy_vm_on_specific_pod
Error
0.14
test_vm_deployment_planner.py

test_04_deploy_vm_on_host_override_pod_and_cluster
Error
1.16
test_vm_deployment_planner.py

test_05_deploy_vm_on_cluster_override_pod
Error
1.13
test_vm_deployment_planner.py

@blueorangutan package

@DaanHoogland a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 9271

@blueorangutan test alma9 vmware-70u3

@DaanHoogland a [SL] Trillian-Jenkins test job (alma9 mgmt + vmware-70u3) has been kicked to run smoke tests

[SF] Trillian Build Failed (tid-9844)

@blueorangutan test rocky8 vmware-70u3

[SF] Trillian test result (tid-9845)
Environment: vmware-70u3 (x2), Advanced Networking with Mgmt server r8
Total time taken: 40143 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr8915-t9845-vmware-70u3.zip
Smoke tests completed. 99 look OK, 2 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_04_deploy_vm_with_extraconfig_throws_exception_vmware
Error
1.20
test_deploy_vm_extra_config_data.py

test_05_deploy_vm_with_extraconfig_vmware
Error
0.19
test_deploy_vm_extra_config_data.py

test_02_deploy_vm_on_specific_cluster
Error
1.17
test_vm_deployment_planner.py

test_03_deploy_vm_on_specific_pod
Error
1.20
test_vm_deployment_planner.py

test_04_deploy_vm_on_host_override_pod_and_cluster
Error
1.21
test_vm_deployment_planner.py

test_05_deploy_vm_on_cluster_override_pod
Error
1.17
test_vm_deployment_planner.py

@blueorangutan package

@DaanHoogland a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 9286

@blueorangutan test alma9 vmware-70u3

@DaanHoogland a [SL] Trillian-Jenkins test job (alma9 mgmt + vmware-70u3) has been kicked to run smoke tests

[SF] Trillian test result (tid-9877)
Environment: vmware-70u3 (x2), Advanced Networking with Mgmt server a9
Total time taken: 46074 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr8915-t9877-vmware-70u3.zip
Smoke tests completed. 109 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_02_list_cpvm_vm
Failure
0.05
test_ssvm.py

test_04_cpvm_internals
Failure
0.07
test_ssvm.py

@rajujith any findings?


"Get bugs with only one or two words in the summary for the" ignore some words

Remove
Implement

Fixed in https://github.com/mozilla/relman-auto-nag/commit/764b70de9e9a101532a9ebc8f09349f3f62befad.


Support and test mypy 0.910, 0.920, and 0.921

Change Summary

Problem: We aren't testing mypy version compatibility, which makes it hard to know when we're making/breaking compatibility.
Solution: Add mypy version matrix to CI.
Related issue number

Link: https://github.com/samuelcolvin/pydantic/discussions/3538#discussioncomment-1867912
See-also: #3175
Checklist

[x] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[x] Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)
[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

please review

Thanks for this, I'm stealing some ideas for #3572.


Update team information and images

This pull request updates the team information and images to reflect the latest changes. Specifically, it updates the README.md and docs/AboutUs.md files, renames several image files and updates the corresponding references in the documentation, and adds new .md files for each team member.
Please review these changes and let me know if there are any issues or concerns. Thank you!

The names of the image files have not been renamed to our GitHub usernames and you might have missed out on Jun Kang's PPP file.
Other than those mentioned, the rest looks good. Thank you for helping us!

 Do remember to approve this PR if there is nothing more to add :)


API: Fetching the Uniform state

User Story
As a user
I want to be able to fetch the uniform state (for a project) using a dedicated endpoint
Details
Keptn Service/Integrations will register / unregister themselves using the endpoint implemented in #4041
Additionally, this endpoint shall support a GET operation to fetch the current uniform state.
This operation will mainly be used by the Keptn Bridge to fetch the data for its Uniform screen
Definition Of Done

[ ] Endpoint support GET operation for fetching the uniform state
[ ] Swagger documentation is updated
[ ] Integration test is available

Dependencies
#4041
#4033

Possible follow up: Implemtnation of keptn show uniform <project> in Keptn CLI


JDK metadata json binary_type is set to "debugimage" ?

This doesn't look right?
19:23:47      "binary_type": "debugimage",

https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-aix-ppc64-hotspot/947/console
Seems random, here's one set to jre:
https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk16u/job/jdk16u-linux-ppc64le-hotspot/52/console
One set to testimage:
https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk16u/job/jdk16u-linux-ppc64le-hotspot/46/console
Wondering if it relates to the last image uploaded...?

I think this is an aspect only of the Console printed metadata, so not a big deal, published binaries json is good.


[Refactor docs] emphasize simple reproducible build step

Provide immediate, easy-to-find access to streamlined reproducible build steps.
Refactor everything else out of the way.

All looks great! We now need the correct PowerShell command for the 'docker compose up'.

@Marc-Gee I'm away from my Windows machine. Any chance you can figure out the PowerShell command to finish this off?

ACK


Fixed component governance bugs for FileTransformV1, bumped version

Task name: FileTransformV1
Description: Fixed component governance bugs for FileTransformV1
Checklist:

[x] Task version was bumped - please check instruction how to do it
[ ] Checked that applied changes work as expected

/azp run

/azp run


Bug report share options is too generic

When I want to send a bug report I get the option of sending it via email, vector, dropbox, blah, etc etc. is it possible to restrict this to email clients?

The android fragmentation does not help us.
1- we use intent.ACTION_SEND_MULTIPLE action because SEND or SENDTO don't seem to support email attachments.
It also depends if the user has installed some clients which might support it.
SEND_MULTIPLE seems supported by all the android devices.
2- i tried to display the email clients first
__// list the intent which supports email
// it should avoid having lot of unexpected applications (like bluetooth...)
Intent emailIntent = new Intent(Intent.ACTION_SENDTO, Uri.fromParts("mailto"<EMAIL_ADDRESS>null));
emailIntent.putExtra(Intent.EXTRA_SUBJECT, "Mail subject");
List resolveInfos =    mContext.getPackageManager().queryIntentActivities(emailIntent, 0);
final List intents = new ArrayList<>();
for (ResolveInfo info : resolveInfos) {
                Intent intent = new Intent(Intent.ACTION_SEND_MULTIPLE);
                info.loadLabel(mContext.getPackageManager()), info.icon));
            }
            Intent chooser = Intent.createChooser(intents.get(intents.size() - 1), "...");
            chooser.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
            chooser.putExtra(Intent.EXTRA_INITIAL_INTENTS, intents.toArray(new Parcelable[]{}));
            mContext.startActivity(chooser);__

It seems working on a nexus 6 (android 5.1), but EXTRA_INITIAL_INTENTS is ignored on a Samsung S5.
EXTRA_INITIAL_INTENTS seems also buggy on Android 6

BugReport are now done with a dedicated screen. I close the issue


Write performance regression

Hi, I am seeing a regression in write performance ~0.5x after updating to the latest.
-require github.com/segmentio/parquet-go v0.0.0-20220330180547-542d8f0815f1
+require github.com/segmentio/parquet-go v0.0.0-20220426180755-25a20d16fa7f

Attaching some cpu profiles for 3 runs:

cpu.old.out - Baseline, parquet.Writer only, ~15s
cpu.new.out - Latest, parquet.Writer only, ~37s
cpu.buffer.out - Latest, both parquet.Writer and Buffer, ~32s
profiles.zip

On initial scan it looks like more time spent in parquet-go.clearValues and github.com/pierrec/lz4/v4/internal/lz4block.(*CompressorHC).CompressBlock

Thanks a lot of the report!

The calls to clearValues do seem to take more time than they should

The change on the LZ4 path may be due to a fix; parquet-go was mistakenly using the LZ4 stream format instead of the block format, which is required by the spec

I'm investigating, will get back to you if I find what's going on.
If you happen to have a dataset I can use or a Go benchmark to reproduce the regression, this would also be highly valuable.


4 wheel math?

Has anyone done the code/math for 4 wheels?  Having the joystick interface on https://github.com/shaunuk/picar would be better.

Hi - sorry, I'm not sure exactly what you're asking, could you explain?
This project was inspired by shaunuk's, however this robot uses a 2 wheel differential drive so the joystick math is quite different to his. For a car with front wheels which can be angled, you could just map the angle of these wheels on to the x axis of the joystick, and the speed of the back motors on to the y axis.


Not Working with new version of Atom

Hey is not working anymore with the version 1.10.2 of Atom

Hi. I'll check this as soon as possible.

I guess it's again because of babel-language plugin

Thank you for the update but still not working for me. Gonna look if it's not from my side

Can you show me some code and list of your plugins?

It's ok now I just restart Atom after the update now it's working ;)


homepage example contains syntax error

I pasted this into the console on the homepage:
const styles = {
  color: lighten(0.2, '#000'),
  font-size: modularScale(1),
  [hiDPI(1.5)]: {
    font-size: modularScale(1.25)
  }
}

And, unsurprisingly, got
Uncaught SyntaxError: Unexpected token -
I assume it needs to be "font-size": ?

Yes, good call! PR welcome.

Sure, forthcoming

thanks @rattrayalex


Scan area is now too high and on top of Compare button

I used to have the scan area in the good position, but with recent updates, it's now on top of the screen.
Screenshot/Mockup/Before-After

Smartphone model

Device: Galaxy S8

Yes same as #1708 just in more extreme


Update vendors.md

typo

Hi, thanks for the contribution.
I'm quite busy right now, but I will merged it & publish soon.
Thanks again.

Has been implemented & published in version 0.11.7.
Thanks again.


[TextServer] Fix incorrect line breaks count for embedded objects (e.g. RTL tables).

Fixes regression from https://github.com/godotengine/godot/pull/67821

Thanks!


Turn off reupload_on_changes for Cirrus caches

Description
Cirrus caching is often failing with EOF errors when unarchiving the downloaded cache due to multiple tasks reuploading to Google Storage.  See https://github.com/cirruslabs/cirrus-ci-docs/issues/567#issuecomment-591706875.
@fkorotkov says:

I don't think it's freezable to try more than once. In your case it seems there is a race condition and Google Storage throws on read because some other tasks re-uploads a cache entry. Consider using https://github.com/cirruslabs/cirrus-ci-docs/pull/569

Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I signed the [CLA].
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

Skipping change detection for pub cache!
https://cirrus-ci.com/task/5963410898681856?command=Upload 'pub' cache#L0

By

modify fingerprint_script as well to not have collisions with currently running tasks

I meant that you can modify fingerprint_script so it has a different output and therefore a different key. The issue happens when other tasks are reuplaoding a cache entry that is being downloaded at the time. Once the change is landed, old PRs will still use the old logic (have the same fingerprint).

For example instead of echo $OS you can echo $CIRRUS_OS which will slightly change the output since an executed command line is also a part of a fingerprint.


1.15 Support

Crazy Crates fails to load in 1.15

Same, we need an update.

If you'd care to join the discord where you would see that THERE IS A NEW UPDATE THAT YOU COULD DOWNLOAD AND TEST IF YOU JUST WAITED FOR BADBONES TO UPDATE THEM!!!!  ITS NOT THAT HARD TO CLICK 3 BUTTONS TO JOIN A DISCORD SERVER.  jeez

The update is currently in the works and a build is available on the Jenkins. https://jenkins.badbones69.com/


Native TLS option fails on corporate laptop.

Previous versions, prior to 0.2.5 I think, worked on my corporate laptop that includes the Cisco Umbrella proxy. The current version 0.2.7 (and 0.2.6 and 0.2.5) appears to have broken support for native TLS, the --native-tls option does nothing. The issue is in the Windows environment. uv does still work on linux in WSL2 as long as I'm not connected to the corporate firewall.
~\junk on ☁  (us-east-1)
❯ uv --version
uv 0.2.7 (a241f148d 2024-06-05)

~\junk on ☁  (us-east-1)
❯ uv venv
Using Python 3.11.9 interpreter at: C:\Users\320159535\mambaforge\python.exe
Creating virtualenv at: .venv
Activate with: .venv\Scripts\activate

~\junk on ☁  (us-east-1)
❯ .venv\Scripts\activate

~\junk via 🐍 v3.11.9 (junk) on ☁  (us-east-1)
❯ uv pip install -v numpy
DEBUG Searching for Python interpreter in virtual environments
DEBUG Found CPython 3.11.9 at `C:\Users\320159535\junk\.venv\Scripts\python.exe` (active virtual environment)
DEBUG Using Python 3.11.9 environment at .venv\Scripts\python.exe
DEBUG Acquired lock for `.venv`
DEBUG At least one requirement is not satisfied: numpy
DEBUG Using registry request timeout of 30s
DEBUG Solving with installed Python version: 3.11.9
DEBUG Adding direct dependency: numpy*
DEBUG Found stale response for: https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/
DEBUG Sending revalidation request for: https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/
DEBUG Transient request failure for https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/, retrying: Request error: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: client error (Connect)
  Caused by: invalid peer certificate: UnknownIssuer
DEBUG Transient request failure for https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/, retrying: Request error: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: client error (Connect)
  Caused by: invalid peer certificate: UnknownIssuer
DEBUG Transient request failure for https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/, retrying: Request error: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: client error (Connect)
  Caused by: invalid peer certificate: UnknownIssuer
DEBUG Transient request failure for https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/, retrying: Request error: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: client error (Connect)
  Caused by: invalid peer certificate: UnknownIssuer
error: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: client error (Connect)
  Caused by: invalid peer certificate: UnknownIssuer

~\junk via 🐍 v3.11.9 (junk) on ☁  (us-east-1) took 4s
❯ uv pip install --native-tls -v numpy
DEBUG Searching for Python interpreter in virtual environments
DEBUG Found CPython 3.11.9 at `C:\Users\320159535\junk\.venv\Scripts\python.exe` (active virtual environment)
DEBUG Using Python 3.11.9 environment at .venv\Scripts\python.exe
DEBUG Acquired lock for `.venv`
DEBUG At least one requirement is not satisfied: numpy
DEBUG Using registry request timeout of 30s
DEBUG Solving with installed Python version: 3.11.9
DEBUG Adding direct dependency: numpy*
DEBUG Found stale response for: https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/
DEBUG Sending revalidation request for: https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/
DEBUG Transient request failure for https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/, retrying: Request error: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: client error (Connect)
  Caused by: invalid peer certificate: UnknownIssuer
DEBUG Transient request failure for https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/, retrying: Request error: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: client error (Connect)
  Caused by: invalid peer certificate: UnknownIssuer
DEBUG Transient request failure for https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/, retrying: Request error: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: client error (Connect)
  Caused by: invalid peer certificate: UnknownIssuer
DEBUG Transient request failure for https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/, retrying: Request error: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: client error (Connect)
  Caused by: invalid peer certificate: UnknownIssuer
error: error sending request for url (https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/)
  Caused by: client error (Connect)
  Caused by: invalid peer certificate: UnknownIssuer

Note that the environment variable UV_INDEX_URL is set to point to a JFrog pypi mirror that includes proprietary packages. I used to have the variable set for native TLS, but I removed it when it stopped working sometime around version 0.2.5 (it could have been an earlier version).

As far as I can tell, we didn't change anything here from 0.2.5 to 0.2.7. We did upgrade some dependencies. But native_tls is still being respected in the codebase. Can you please determine which version exactly this stopped working for you? There's no way for me to debug it since I don't have access to your environment or your index.

I will investigate further and report back.

Thanks.

Update: I was trying different versions and noted that uv self update is working again for 0.2.9. However, the peer certificate error still occurs when trying to do a pip install.
~\junk via 🐍 v3.11.9 (junk) on ☁  (us-east-1)
❯ uv self update                                                                                info: Checking for updates...                                                                                success: You're on the latest version of `uv` (v0.2.9).                                                                                ~\junk via �� v3.11.9 (junk) on ☁  (us-east-1)                                                                           ❯ powershell -c "irm https://github.com/astral-sh/uv/releases/download/0.2.8/uv-installer.ps1 | iex"                      Downloading uv 0.2.8 (x86_64-pc-windows-msvc)
Installing to C:\Users\320159535\.cargo\bin
  uv.exe
Everything's installed!

~\junk via 🐍 v3.11.9 (junk) on ☁  (us-east-1) took 6s
❯ uv self update
info: Checking for updates...
error: error sending request for url (https://objects.githubusercontent.com/github-production-release-asset-2e65be/699532645/d12c4ef0-c66f-43d6-9cf9-40fc46e8205a?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=releaseassetproduction%2F20240606%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20240606T220805Z&X-Amz-Expires=300&X-Amz-Signature=ecdeab1b3afe738495483fae0276ce1bb1497d86d47b664fd57776c44467c488&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=699532645&response-content-disposition=attachment%3B%20filename%3Duv-installer.ps1&response-content-type=application%2Foctet-stream)
  Caused by: client error (Connect)
  Caused by: invalid peer certificate: UnknownIssuer

~\junk via 🐍 v3.11.9 (junk) on ☁  (us-east-1)
❯ powershell -c "irm https://github.com/astral-sh/uv/releases/download/0.2.9/uv-installer.ps1 | iex"
Downloading uv 0.2.9 (x86_64-pc-windows-msvc)
Installing to C:\Users\320159535\.cargo\bin
  uv.exe
Everything's installed!

~\junk via 🐍 v3.11.9 (junk) on ☁  (us-east-1) took 6s
❯ uv self update
info: Checking for updates...
success: You're on the latest version of `uv` (v0.2.9).

~\junk via 🐍 v3.11.9 (junk) on ☁  (us-east-1)
❯

For the previous several versions, I could not run uv self update, but now it runs without an error and without the --native-tls option. However, up pip install still fails with the same peer certificate error seen above for uv self update for 0.2.8.

So, 0.2.9 also works if my index source is pypi.org rather than our proprietary server. But it's not a real certificate issue on our server because uv is perfectly happy to accept those certificates if I run on the same machine using linux on WSL.
~/junk via 🐍 v3.12.3 (junk) on ☁  (us-east-1) took 9s
❯ uv --version
uv 0.2.9

~/junk via 🐍 v3.12.3 (junk) on ☁  (us-east-1)
❯ uv clean
Clearing cache at: /home/syrus/.cache/uv
Removed 938 files (65.0MiB)

~/junk via 🐍 v3.12.3 (junk) on ☁  (us-east-1)
❯ uv venv
Using Python 3.12.3 interpreter at: /home/syrus/mambaforge/bin/python3
Creating virtualenv at: .venv
Activate with: source .venv/bin/activate

~/junk via 🐍 v3.12.3 (junk) on ☁  (us-east-1)
❯ source .venv/bin/activate

~/junk via 🐍 v3.12.3 (junk) on ☁  (us-east-1)
❯ uv pip list

~/junk via 🐍 v3.12.3 (junk) on ☁  (us-east-1)
❯ uv pip install -v numpy
DEBUG Searching for Python interpreter in virtual environments
DEBUG Found CPython 3.12.3 at `/home/syrus/junk/.venv/bin/python3` (active virtual environment)
DEBUG Using Python 3.12.3 environment at .venv/bin/python3
DEBUG Acquired lock for `.venv`
DEBUG At least one requirement is not satisfied: numpy
DEBUG Using registry request timeout of 30s
DEBUG Solving with installed Python version: 3.12.3
DEBUG Adding direct dependency: numpy*
DEBUG No cache entry for: https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/
DEBUG Checking netrc for credentials for https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/
DEBUG Found credentials in netrc file for https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/simple/numpy/
DEBUG Searching for a compatible version of numpy (*)
DEBUG Selecting: numpy==1.26.4 (numpy-1.26.4-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl)
DEBUG No cache entry for: https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/packages/packages/0f/50/de23fde84e45f5c4fda2488c759b69990fd4512387a8632860f3ac9cd225/numpy-1.26.4-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl#sha256=675d61ffbfa78604709862923189bad94014bef562cc35cf61d3a07bba02a7ed
DEBUG Tried 2 versions: numpy 1, root 1
Resolved 1 package in 1.62s
DEBUG Identified uncached requirement: numpy==1.26.4
DEBUG No cache entry for: https://biotelemetry.jfrog.io/artifactory/api/pypi/pypi/packages/packages/0f/50/de23fde84e45f5c4fda2488c759b69990fd4512387a8632860f3ac9cd225/numpy-1.26.4-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl#sha256=675d61ffbfa78604709862923189bad94014bef562cc35cf61d3a07bba02a7ed
Downloaded 1 package in 7.27s
Installed 1 package in 9ms
 + numpy==1.26.4

~/junk via 🐍 v3.12.3 (junk) on ☁  (us-east-1) took 8s
❯

I'd recommend taking a look at these similar issues

https://github.com/astral-sh/uv/issues/1819
https://github.com/astral-sh/uv/issues/2020

The general theme here is that we don't actually implement certificate loading so we're unlikely to be able to help you. Here's a portion of one of my previous comments:

It may be worth seeing if there are any upstream rustls-native-certs issues that apply to your situation and confirm that your certificates are available through the schannel API.

You could also bisect the regression to a specific commit on uv, which would be very helpful for investigating the source of the issue.

I will try to identify a specific commit. Also, Schannel works fine for git-for-windows and for mamba-forge. I will take a look at the upstream rust-native-certs repo for related issues. Thank you!

@zanieb, this issue may be the culprit: https://github.com/rustls/rustls-native-certs/issues/22
Coupled with the upstream bug in loading the SSL certificate file (I also tried that), I seem to be blocked, but it looks like the upstream TLS package will resolve this in the long run. I will also try using the SSL certificate variable again. Because that may be needed.

Thank you so much for doing this investigation!

Bumping since the devs of rustls-native-certs don't plan to fix this in favor of using rustls-platform-verifier per rustls-native-certs#133

@gdebrun2 Can you open a new specific issue with a request instead of bumping?


Show faction perks accumulated for each faction

[ ] Show faction relation level
[ ] Show perks accumulated by the character over time.

I'm not sure this is in scope as it is not a D&D 5e rule. Factions are homebrew and while it might be useful, it requires a whole lot more of work. Standing is not a stable resource, you gain standing in a different way as it is not the consequence of a single activity. It doesn't quite fit in the resource system that i'm working on. We'll see if the app goes there.

[ ] Add a faction API
[ ] Add contacts to characters resources
[ ] Update resource delta to better handle double negatives (downtime produces neg contacts so that they get neg in the delta calc, sign should be an option in the Activities UI)
[ ] Update carousing to produce contact resources
[ ] Impacts hireling costs and lifestyle cost (if we ever go that route)

@FinchPhil mentionne aussi qu'un faction et un hireling vont peut-etre utiliser la meme mechanique au final.


FS-1123: Supermicro (SMC) BIOS config Get, Set and Reset support via SUM

What does this PR implement/change/remove?
BIOS config management support for Supermicro (SMC) platforms implemented as a wrapper over Supermicro Update Manager (SUM).

GetBiosConfiguration
SetBiosConfiguration
SetBiosConfigurationFromFile
ResetBiosConfiguration

Description for changelog/release notes
BIOS config management support for Supermicro (SMC) platforms.

Still need to complete some code here.

@splaspood is this ready for review? set reviewers in that case.


Create Example

Create example that predicts handwritten numbers, to show how to use the package.

Closed with #5


Disable ROSS output

A command-line argument, --no-ross-output or similar, that disables the pre-run (timestamp, ROSS revision) and post-run (statistics) ROSS output would be great to have. That way, it's much easier to handle sims that e.g., dump their own data to stdout. Typically (for me at least), the ROSS output is best for debugging/tuning the simulation under various scenarios - it doesn't need to hang around for the subsequent "production" runs.

Do you still want the start/ending simulation messages and progress messages?

Preferably not - ideally, with this option stdout would be completely unused by ROSS (with stderr being used for warning/error reporting).

hackathon - people want to post-process output via tw_output and piping. Suppressing ross output would be very helpful in this case.


Add open-ce tests for pyarrow

The current version of the Arrow recipe matches the official upstream conda recipe, which has a pyarrow-tests package. This package includes some extra tests to run at conda-build time that are not desired in the final package.
Change this recipe to remove the pyarrow-tests package and move the tests to our standard Open-CE test mechanism in the test/ directory.

Let's also move the import testing from the conda-build test section to the test/ directory as well so we can control wether or not they run (due to availability of GPUs and libcuda)


System unavailable: Wazuh - SIEM System

Please put the system name in the title of this issue.

Wazuh / Web Dashboard / Indexer Issue

Please describe the issue:

The Wazuh system has stopped showing alerts. This needs to be investigated and resolved.
Tasks:

[X] - Investigate and resolve initial problem - Indexer out of shards
[X] - Identify root cause - Hit 1000 shard limit.
[ ] - Implement solution - enable auto housekeeping, initial limit of 9 months data
[x] - Add missing data back into Wazuh indexes.

Indexer had run out of shards, have removed data from Oct, Nov, Dec 2023, so "only" have 9 months of data. Have noticed data for the last month has not been indexed correctly. Log files are still available on the Wazuh server, so will investigate re-indexing and adding this data. Real time alerts and monitoring are now in place.

Re ingesting log files in progress... details on how to achieve this are contained in this handy blog post, it'll likely take the weekend to complete.. https://wazuh.com/blog/recover-your-data-using-wazuh-alert-backups/

For future reference:
https://wazuh.com/blog/wazuh-index-management/
Get the python script from this blog post
https://wazuh.com/blog/recover-your-data-using-wazuh-alert-backups/
vi /usr/share/filebeat/module/wazuh/alerts/manifest.yml

Change This
module_version: 0.1
var:
 - name: paths
   default:
     - /var/ossec/logs/alerts/alerts.json
 - name: index_prefix
   default: wazuh-alerts-4.x-
input: config/alerts.yml
ingest_pipeline: ingest/pipeline.json

To This
module_version: 0.1
var:
 - name: paths
   default:
     - /var/ossec/logs/alerts/alerts.json
     - /tmp/recovery.json
 - name: index_prefix
   default: wazuh-alerts-4.x-
input: config/alerts.yml
ingest_pipeline: ingest/pipeline.json

Then restart filebeat ( and check its running... )
# systemctl restart filebeat
# filebeat test output
elasticsearch: https://<IP_ADDRESS>:9200...
 parse url... OK
 connection...
   parse host... OK
   dns lookup... OK
   addresses: <IP_ADDRESS>
   dial up... OK
 TLS...
   security: server's certificate chain verification is enabled
   handshake... OK
   TLS version: TLSv1.2
   dial up... OK
 talk to server... OK
 version: 7.10.2

Run The Restore Script
nohup ./recovery.py -eps 500 -min 2024-08-06T00:00:00 -max 2024-09-05T23:59:59 -o /tmp/recovery.json -log ./recovery.log -sz 2.5 &

Monitor progress using this..
cut -b 16-25 /tmp/recovery.json |sort |uniq -c

Use this in the indexes dev tools to check how many shards are in use..
GET /_cat/shards?v=true

Alert retention policy added as described here
https://documentation.wazuh.com/current/user-manual/wazuh-indexer/index-life-management.html
Currently set to 280days. Will be monitored and adjusted as required.


/react/redux/snowflake/src/snowflake.js: Unexpected token (120:6)

When i'm running from xcode i get following error.
{
    "type": "TransformError",
    "message": "SyntaxError /Users/jjonagam/react/redux/snowflake/src/snowflake.js: Unexpected token (120:6)",
    "snippet": "\u001b[0m    \u001b[36mvar\u001b[39m color \u001b[1m=\u001b[22m \u001b[36mthis\u001b[39m\u001b[1m.\u001b[22mprops\u001b[1m.\u001b[22mselected \u001b[1m?\u001b[22m \u001b[31m'#FF3366'\u001b[39m \u001b[1m:\u001b[22m \u001b[31m'#FFB3B3'\u001b[39m\u001b[1m;\u001b[22m\n    \u001b[36mreturn\u001b[39m \u001b[34m\u001b[1m(\u001b[22m\u001b[39m\n      \u001b[1m<\u001b[22mView style\u001b[1m=\u001b[22m\u001b[32m{\u001b[39m\u001b[32m{\u001b[39mflex\u001b[1m:\u001b[22m\u001b[35m1\u001b[39m\u001b[1m,\u001b[22m flexDirection\u001b[1m:\u001b[22m\u001b[31m'column'\u001b[39m\u001b[1m,\u001b[22m alignItems\u001b[1m:\u001b[22m\u001b[31m'center'\u001b[39m\u001b[1m,\u001b[22m alignSelf\u001b[1m:\u001b[22m\u001b[31m'center'\u001b[39m\u001b[32m}\u001b[39m\u001b[32m}\u001b[39m\u001b[1m>\u001b[22m\n        \u001b[1m<\u001b[22mIcon style\u001b[1m=\u001b[22m\u001b[32m{\u001b[39m\u001b[32m{\u001b[39mcolor\u001b[1m:\u001b[22m color\u001b[32m}\u001b[39m\u001b[32m}\u001b[39m name\u001b[1m=\u001b[22m\u001b[32m{\u001b[39m\u001b[36mthis\u001b[39m\u001b[1m.\u001b[22mprops\u001b[1m.\u001b[22miconName\u001b[32m}\u001b[39m size\u001b[1m=\u001b[22m\u001b[32m{\u001b[39m\u001b[35m30\u001b[39m\u001b[32m}\u001b[39m \u001b[1m/\u001b[22m\u001b[1m>\u001b[22m\n        \u001b[1m<\u001b[22mText style\u001b[1m=\u001b[22m\u001b[32m{\u001b[39m\u001b[32m{\u001b[39mcolor\u001b[1m:\u001b[22m color\u001b[32m}\u001b[39m\u001b[32m}\u001b[39m\u001b[1m>\u001b[22m\u001b[32m{\u001b[39m\u001b[36mthis\u001b[39m\u001b[1m.\u001b[22mprops\u001b[1m.\u001b[22mtitle\u001b[32m}\u001b[39m\u001b[1m<\u001b[22m\u001b[1m/\u001b[22mText\u001b[1m>\u001b[22m\n      \u001b[1m<\u001b[22m\u001b[1m/\u001b[22mView\u001b[1m>\u001b[22m\u001b[0m",
    "lineNumber": 120,
    "column": 6,
    "filename": "/Users/jjonagam/react/redux/snowflake/src/snowflake.js",
    "description": "/Users/jjonagam/react/redux/snowflake/src/snowflake.js: Unexpected token (120:6)",
    "errors": [{
        "description": "/Users/jjonagam/react/redux/snowflake/src/snowflake.js: Unexpected token (120:6)",
        "filename": "/Users/jjonagam/react/redux/snowflake/src/snowflake.js",
        "lineNumber": 120
    }]
}

Be sure to kill whatever terminal is already running -ie, make sure to run "react-native start" in the correct window.  I had this same thing happen and it was because after updating Snowflake locally, there was a previous packager running.  After killing that packager and restarting it, iOS ran fine.

Please help me...
64% 489/764[BABEL] Note: The code generator has deoptimised the styling of "C:/Users/khoahoang/Desktop/snowflake/node_modules/immutable/dist/immutable.js" as it exceeds the max of "100KB". 72% 549/764Error while persisting cache: SyntaxError C:/Users/khoahoang/Desktop/snowflake/src/snowflake.js: Unexpected token (120:6)

I'm not sure how to help w/ this.  I can't replicate it.

Out of the box, clean checkout, I see the same:
START> request:/index.ios.bundle?platform=ios&dev=true transforming [=========================               ] 62% 477/767[BABEL] Note: The code generator has deoptimised the styling of "/.../snowflake/node_modules/immutable/dist/immutable.js" as it exceeds the max of "100KB". transforming [=============================           ] 72% 555/767Error while persisting cache: SyntaxError /.../snowflake/node_modules/react-native/Libraries/CustomComponents/Navigator/Navigation/NavigationEventEmitter.js: Unexpected token (33:5)

I will look at this tomorrow - today I have to take a trip.

I am also seeing this same error.
I am also seeing the error src/components/FormButton.js: Unexpected token (47:6) on a fresh install when running from xcode.

I had this problem as well. If I'm not mistaken, just removing the .babelrc file fixed the persisting cache error. Before that, I also ran these lines, before removing the .babelrc file (just in case it matters, don't think it does):
react-native upgrade
npm install ---save react
react-native upgrade
./node_modules/react-native/packager/packager.sh start --reset-cache
mv .babelrc .orig.babelrc

Thank you @TheTekton this resolved the errors for me

Just removing .babelrc saved my day, thanks @TheTekton

see https://github.com/bartonhammond/snowflake/releases/tag/0.0.13b


Backport PR #5480 to 17.x.x

This backports PR #5480 to 17.x.x. If not desired, feel free to close.

wtf?


camera's color data frame couldn't play in chrome57.0.2987.98 Linux x86

Seems this issue doesn't reproduce on my side.
I used Joule + R200 as server, and client used:

OS
Chrome Version
Result

Linux Ubuntu16.04
57.0.2987.98
PASS

Linux Ubuntu 16.04
56.0.2924.76
PASS

Window 7
55.0.2883.87
PASS

Windows 8.1
56.0.2924.87
PASS

Windows 8.1
58.0.3017.1
PASS

Windows 8.1
59.0.3043.0
PASS


Floating Label not visible when building app with expo.

I have a very simple component that uses floatingLabels and when I use expo start they appear properly. When I use expo build:android the labels do not appear at all.
Here is more details from a forum thread. Unfortunately the solution the person proposed did not work for me I also wanted to post this issue here because using an older version is not a solution, its a workaround.
http://discuss.nativebase.io/t/nativebase-form-is-not-visible-properly-in-release-build-apk-generated-with-gradlew-assemblerelease/1142/7

Did you check #2264 before creating this issue?

I did a while ago, but didn't think to check today. A new version will be available this week. Thank you for the link.


Spring Cloud Stream SSL authentication to Schema Registry- 401 unauthorized

I am trying to use Spring Cloud Stream (which is based on Spring Boot) application with Confluent Schema Registry. The authentication method is SSL and I am not able to pass the connection step for some reason. Either the configuration parameters are incorrect or I am hitting a bug. I would appreciate it if you could help me to realize how to resolve this issue.
spring:
  cloud:
    stream:
      bindings:
        input:
          destination: sensor-topic
      schemaRegistryClient:
        endpoint: https://[schema-registry-url]:[port]
      schema:
        avro:
          schema-locations: classpath:avro/sensor.avsc
server.port: 9999
spring.cloud.stream.kafka.streams.binder:
  brokers: https://[kafka-url]:[port]
  configuration:
    bootstrap.servers: SSL://[kafka-url]:[port]
    security.protocol: SSL
    ssl.truststore.location: client.truststore.jks
    ssl.truststore.password: secret
    ssl.keystore.type: PKCS12
    ssl.keystore.location: client.keystore.p12
    ssl.keystore.password: secret
    ssl.key.password: secret
    key.serializer: io.confluent.kafka.serializers.KafkaAvroSerializer
    value.serializer: io.confluent.kafka.serializers.KafkaAvroSerializer
    schema.registry.url: https://[schema-registry-url]:[port]
    basic.auth.credentials.source: USER_INFO
    basic.auth.user.info: [username]:[pass]

Exception:
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'avroSchemaMessageConverter' defined in class path resource [org/springframework/cloud/stream/schema/avro/AvroMessageConverterAutoConfiguration.class]: Invocation of init method failed; nested exception is java.lang.RuntimeException: Failed to register subject sensor, server replied with status 401
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1778) ~[spring-beans-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:593) ~[spring-beans-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:515) ~[spring-beans-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:320) ~[spring-beans-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) ~[spring-beans-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:318) ~[spring-beans-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199) ~[spring-beans-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:277) ~[spring-beans-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.addCandidateEntry(DefaultListableBeanFactory.java:1463) ~[spring-beans-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.findAutowireCandidates(DefaultListableBeanFactory.java:1427) ~[spring-beans-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveMultipleBeans(DefaultListableBeanFactory.java:1318) ~[spring-beans-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1205) ~[spring-beans-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1167) ~[spring-beans-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:857) ~[spring-beans-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:760) ~[spring-beans-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	... 171 common frames omitted
Caused by: java.lang.RuntimeException: Failed to register subject sensor, server replied with status 401
	at org.springframework.cloud.stream.schema.client.ConfluentSchemaRegistryClient.register(ConfluentSchemaRegistryClient.java:99) ~[spring-cloud-stream-schema-2.2.0.BUILD-20190416.000801-103.jar:2.2.0.BUILD-SNAPSHOT]
	at org.springframework.cloud.stream.schema.avro.AvroSchemaRegistryClientMessageConverter.registerSchema(AvroSchemaRegistryClientMessageConverter.java:395) ~[spring-cloud-stream-schema-2.2.0.BUILD-20190416.000801-103.jar:2.2.0.BUILD-SNAPSHOT]
	at org.springframework.cloud.stream.schema.avro.AvroSchemaRegistryClientMessageConverter.lambda$afterPropertiesSet$3(AvroSchemaRegistryClientMessageConverter.java:253) ~[spring-cloud-stream-schema-2.2.0.BUILD-20190416.000801-103.jar:2.2.0.BUILD-SNAPSHOT]
	at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184) ~[na:1.8.0_191]
	at java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948) ~[na:1.8.0_191]
	at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580) ~[na:1.8.0_191]
	at java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:270) ~[na:1.8.0_191]
	at java.util.stream.ReferencePipeline$11$1.accept(ReferencePipeline.java:373) ~[na:1.8.0_191]
	at java.util.stream.DistinctOps$1$2.accept(DistinctOps.java:175) ~[na:1.8.0_191]
	at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) ~[na:1.8.0_191]
	at java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948) ~[na:1.8.0_191]
	at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) ~[na:1.8.0_191]
	at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) ~[na:1.8.0_191]
	at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) ~[na:1.8.0_191]
	at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) ~[na:1.8.0_191]
	at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[na:1.8.0_191]
	at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) ~[na:1.8.0_191]
	at org.springframework.cloud.stream.schema.avro.AvroSchemaRegistryClientMessageConverter.afterPropertiesSet(AvroSchemaRegistryClientMessageConverter.java:245) ~[spring-cloud-stream-schema-2.2.0.BUILD-20190416.000801-103.jar:2.2.0.BUILD-SNAPSHOT]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1837) ~[spring-beans-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1774) ~[spring-beans-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	... 185 common frames omitted
Caused by: org.springframework.web.client.HttpClientErrorException$Unauthorized: 401 Unauthorized
	at org.springframework.web.client.HttpClientErrorException.create(HttpClientErrorException.java:81) ~[spring-web-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:122) ~[spring-web-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:102) ~[spring-web-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.web.client.ResponseErrorHandler.handleError(ResponseErrorHandler.java:63) ~[spring-web-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.web.client.RestTemplate.handleResponse(RestTemplate.java:778) ~[spring-web-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:736) ~[spring-web-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:670) ~[spring-web-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:579) ~[spring-web-5.1.6.RELEASE.jar:5.1.6.RELEASE]
	at org.springframework.cloud.stream.schema.client.ConfluentSchemaRegistryClient.register(ConfluentSchemaRegistryClient.java:93) ~[spring-cloud-stream-schema-2.2.0.BUILD-20190416.000801-103.jar:2.2.0.BUILD-SNAPSHOT]
	... 204 common frames omitted

I have gone through more depth to understand what is going on. Please correct me if I am wrong, but it looks like being able to create an SSL connection with providing username and password have not been implemented in Spring Cloud Stream yet.
I could not find anything related to creating an SSL context in the following classes:
SchemaRegistryClientConfiguration
ConfluentSchemaRegistryClient
DefaultSchemaRegistryClient

That is correct. We need to do some work there on SSL side.

@olegz Any idea when that will be added?
I can see that one of the constructors accepts RestTemplate. I have tried to see if I can add the SSL context via the RestTemplate customization. It works fine at first, but when it reaches the part that wants to send the msg to Kafka it wants to validate the message with Schema Registry and for that, it uses Confluent Schema Registry client. Unfortunately, the confluent package does not have any details on the SSL setup for the schema registry client. Therefore, I have got stuck and cannot proceed further.

@mraliagha Unfortunately we had to push it to 2.3 which will be some time in August. We basically didn't have a chance to look into this for the upcoming release.
However, if you can help out and contribute something that works in a form of PR, we can help you polish it and merge. We are currently targeting 2.2 release Monday May 6.

@olegz I would submit a PR if I could manage to pass the issue that I am facing. I will do my best ...

@mraliagha I understand, but what I am also trying to say is do what you think is necessary to make it work. We'll help you to make it right. So if you feel like modifying any code, go for it we can polish it later.
Thank you for volunteering with this!

We have actually found a workaround for this, but just wondering if this is added to the code base.

@mraliagha This is not yet addressed. Do you mind sharing details about the workaround?

@sobychacko
Of course not. Please find it as follows. I think it might be useful to add it as an example or to the official document for the time being.
ConfluentSchemaRegistryClient  has a constructor that accepts a restTemplate object.
final KeyStore keyStore = KeyStore.getInstance("PKCS12");
        keyStore.load(new FileInputStream(
                new File(keystoreLocation)),
            keyStorePass.toCharArray());

        final KeyStore trustStore = KeyStore.getInstance("JKS");
        trustStore.load(new FileInputStream(
                new File(truststoreLocation)),
            trustStorePass.toCharArray());

        TrustStrategy acceptingTrustStrategy = (X509Certificate[] chain, String authType) -> true;

        SSLContext sslContext = SSLContextBuilder
            .create()
            .loadKeyMaterial(keyStore, keypass.toCharArray())
            .loadTrustMaterial(trustStore, acceptingTrustStrategy)
            .build();

        HttpClient httpClient = HttpClients.custom().setSSLContext(sslContext).build();
        ClientHttpRequestFactory requestFactory = new HttpComponentsClientHttpRequestFactory(
            httpClient);
        schemaRegistryClient = new ConfluentSchemaRegistryClient(
            new RestTemplate(requestFactory));

To make it work there are some extra configurations that should be passed in conjunction with this code as it looks like it goes beyond the scope of Spring Cloud Stream classes and looks into Spring-Kafka to find the required configurations.
spring:
  kafka:
    properties:
      basic.auth.credentials.source: USER_INFO
      basic.auth.user.info: ${Schema_Registry_Credentials}
      schema.registry.url: ${Schema_Registry_URL}


slickGoTo - Uncaught TypeError: undefined is not a function

Hi,
I am trying to realize a simple button with the "slickGoTo" method to slide to another slide, but all time I get the error "Uncaught TypeError: undefined is not a function".
Do you have an idea, where I am wrong?
Here my Fiddle: http://jsfiddle.net/N6wfG/99/

The way you call methods has changed. You now need to call slick first and pass it the name of the method you want to call, like this:
slider.slick('slickGoTo', 1)

Oh yeah, this works fine. Thanks for that!

Thanks you babe

Thank you @evalunamain

Why don't they changed it on the docs already? Geez.

just out of curiosity @evalunamain what was the reason for this change?

Thank you so much @evalunamain..
It's very help for me.. :+1:

i am getting  this error
uncaught TypeError: $(...).slick is not a function at interval ((index):807)
at this line
$('.single-item').slick('slickNext');
and also on this line
$('.single-item').slick('slickGoTo', goToThisIndex, false);

i am getting  this error
uncaught TypeError: $(...).slick is not a function at interval ((index):807)
at this line
$('.single-item').slick('slickNext');
and also on this line
$('.single-item').slick('slickGoTo', goToThisIndex, false);

I don't think this solution is working anymore
Try using
$('.slide').slick(             slidesToShow: 1,             centerMode: true,             variableWidth: true,             arrows: true, ).slick('slickGoTo', 1);
credit: https://stackoverflow.com/a/54787822


patch() triggers $beforeInsert

I have the following code:
  User
    .query()
    .patch(updateUser)
    .where('id', userId)
    .then(...)
    .catch(...)

and I have a $beforeInsert() function in the User model.
I notice that $beforeInsert() is called even though I am using patch() - shouldn't only $beforeUpdate() be called in this case

My bad. I called the wrong super()


bail out of rekey loop if our device is in the list

this usually indicates a rekey bug, such as broken TLF

r? @patrickxb

LGTM

Wait, one sec:

Do you need to call refresh with empty device list so they can close the window?

empty problem set


CORE-6287: Simulating signing service, verification

A key store is passed into each node which will generate a public key on request. Only RSA keys are generated, regardless of spec. The keys are made available for each member through the MemberLookup.
The signing service fakes signing by wrapping the clear data, PEM-encoded key and other parameters in a JSON wrapper.
The verification service parses the wrapper and checks the key, signature spec and clear data against the expected values.
No encryption is ever actually performed. A prominent warning has been added to the README.

Note we should always favour ECDSA, or EdDSA over RSA. RSA is not a good statement on our using current cryptography.

@mnesbit Deliberately used RSA to avoid the appearance of actually doing any cryptography (nothing is encrypted!), but I can change it for sure.


Model->save() not trowing an exception when insert fail

Laravel Version: 5.3.28
PHP Version: 7
Database Driver & Version: SQL Server 2008

Description:
When my insert fail (because the key is duplicated, for example) i've expected get an exception, but the execution stop like and "die". The server response is an error 500 but i cant catch the exception.
Steps To Reproduce:

Create a block try~catch.
load an model and try insert an register with duplicated key.

A QueryException is thrown successfully in this case, just tested. Please test on a fresh laravel installation and include more information in Steps To Reproduce on how I can replicate the issue on a fresh laravel installation.

Lol, i have a problem here. In fresh installation work fine. I'll investigate this case. I'm sorry for wasting your time.


Using a depreciated dependency |<EMAIL_ADDRESS>

"warning compile-sass ><EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial)."
Not a big deal for me, but thought I'd make it known incase no one noticed

Thank you for bringing it to my attention. I will update the dependencies and release a new version with them.


Fix code editor's ColorPicker issue

This commit fixes #63880

Fix an issue that caused editor replacing whole the line with color parameter on editing a color constant.
If the color constant does not exist, "Pick Color" is not shown in the context menu.

"Pick Color" is no longer shown in the context menu if  Color's parameter contains brackets such as Color((0),0,0) because this expression also caused the same problem.

I've tested this and it works great!

Needs rebase.

Thanks!


Revert "BoxedUint: improve efficiency of square (#382)"

This reverts commit cd9cdcecf9cd27fae48843905581b053c31952e0.
Benchmarks reveal this caused a performance regression to modpow. Reverting it yields the following improvement:
Montgomery arithmetic/modpow, BoxedUint^BoxedUint
                        time:   [76.362 µs 76.381 µs 76.403 µs]
                        change: [-72.846% -72.795% -72.747%] (p = 0.00 < 0.05)
                        Performance has improved.

Still need to investigate why this caused as much performance degradation as it did


Sb retry bdio upload

Retry IP bdio upload if it fails. (Earlier changes didn't account for the fact that an exception is thrown when there's a failure. With these changes it'll handle the exception case, or the no-exception case, in case integration-rest is changed in the future to not throw exceptions on failure.)

I'm surprised no tests needed to be updated with this change. Can we add some for this?

Great point. Now done.


Adding Timer

We should add a timer to the site.

Like this? http://a-g-f.github.io/metro-ui-jekyll/documentation/times.html
It should be customizable enough, I think.


Dynamically changing the IndicatorsControl color from the ViewModel

I want to change the color of the indicator according to the color of the item. If I try to use a value converter that returns cardview style, it doesn't even call the converter.
<controls:IndicatorsControl SelectedIndicatorStyle="{Binding Item, Converter={StaticResource itemToStyle}}"/>

But if I bind the backgroundcolor only like bellow, it works.
<controls:IndicatorsControl>
    <controls:IndicatorsControl.SelectedIndicatorStyle>
        <Style TargetType="controls:IndicatorsControl">
            <Setter Property="BackgroundColor"  Value="{Binding item, Converter={StaticResource itemToStyle}}" />
            <Setter Property="HeightRequest" Value="25" />
            <Setter Property="HeightRequest" Value="25" />
        </Style>
    </controls:IndicatorsControl.SelectedIndicatorStyle>
</controls:IndicatorsControl>

Well, let's investigate it)
Perhaps, you want to debug this view and check, why it doesn't work?)

I would be grateful so much, if you create small sample with reproduction.

Hi

Everything works fine for me (I tried from code)
Must be the same with xaml (try to clean/rebuild/delete bin/obj)
if you still have this issue, obligatory create sample with reproduction


NMS for multi-class prediction

Dear @uschmidt83,
Dear @maweigert,
I have trained multiple stardist model to detect objects.
These objects belong to overlapping classes.
Thus, i need to do an NMS on data from independent predictions.
I know how to get the details by:
labels, details = model.predict_instances...
and the the probabilities from:
coord, points, prob = details['coord'], details['points'], details['prob']
But it is not clear to me :
a) how to transform these into an image (with the probabilities being the pixel values)
b) what is the best way to make an NMS based on 3 pairs of label images & probabilities.
Do you have an example I might look at?
Thanks a lot & Kind regards
Tobias

Discussion via email, hence closed here.

Discussion via email, hence closed here.


Add og:image and og:title for Facebook sharing

Reference of meta tags that need to be added. At the minimum, we need to add the image and text.

https://developers.facebook.com/docs/sharing/webmasters/

You can use the sharing debugger to check if the image and text is getting displayed properly.

https://developers.facebook.com/tools/debug/

Tested on Facebook and LinkedIn. Looks fine on these platforms.
However, on Twitter, the thumbnail is not getting displayed.
Tested using the card validator: https://cards-dev.twitter.com/validator

Closing as this is done.


Dedicated function to parse gl version

I found that the GL version was not properly parsed.
It was returning 51, 48 for a string version 3.0.
Because the string was bytes and indexes was returning ordinal of char 3 and 0
This parsing issue was probably broken in python 3 since the beginning. Or it is a change in the behavior of PyOpenGL.
This PR create a dedicated function to return this version.
Changelog:

Fix GL version parsing

pytest-mock is missing in github actions config (same needs to be done as for appveyor)

It would be good to put that into 1.1.2 as well.


Feature.arklet v1 support initialized project

initialization of arklet project.
support http protocol installation, uninstall and other instructions.
support command mode extension instructions

wait to append api doc and unit test


Data sharing and re-use: Contact PRL to re-inquire about their harvesting development plans, how often they are harvesting, etc.

PRL messaging / meeting key points: https://docs.google.com/document/d/1c3OrJOZCf6RAJqki1TPb6xleHhKS8EJ4q4F_HISynKI/edit?usp=sharing

@christinklez moved to in-progress, got a draft message going -- putting forward some initial questions, also proposing a meeting

Draft message / discussion points: https://docs.google.com/document/d/1c3OrJOZCf6RAJqki1TPb6xleHhKS8EJ4q4F_HISynKI/edit?usp=sharing

Discussed that we would like to propose a meeting with PRL to strategize if there might be alternatives to OAI-PMH harvesting.
Also, here's this link: https://github.com/ucldc/oaiapp


LUIS datetime parsing issue

Version
4.0.7
Describe the bug
LUIS will return the start and end of time range:
"entities": [     {       "entity": "may 2nd to may 5th",       "type": "builtin.datetimeV2.daterange",       "startIndex": 0,       "endIndex": 17,       "resolution": {         "values": [           {             "timex": "(XXXX-05-02,XXXX-05-05,P3D)",             "type": "daterange",             "start": "2017-05-02",             "end": "2017-05-05"           },           {             "timex": "(XXXX-05-02,XXXX-05-05,P3D)",             "type": "daterange",             "start": "2018-05-02",             "end": "2018-05-05"           }         ]       }     }   ]
But BF SDK didn't return the start and end property. Is this by design?
Edit:
Also the date/time/datetime have the same issue:
"entities": [     {       "entity": "may 2nd",       "type": "builtin.datetimeV2.date",       "startIndex": 0,       "endIndex": 6,       "resolution": {         "values": [           {             "timex": "XXXX-05-02",             "type": "date",             "value": "2017-05-02"           },           {             "timex": "XXXX-05-02",             "type": "date",             "value": "2018-05-02"           }         ]       }     }   ]

This looks like a bug in the LUIS recognizer.
Those values are in the LUIS response and should be available as they are with the DateTimePrompt.
An alternative (and more flexible) solution is to base your program logic on the TIMEX array. The problem is TIMEX can be awkward to deal with directly. To work with TIMEX values it is best to use the TimexExpression value.
For the TimexExpression library see:
https://github.com/Microsoft/Recognizers-Text/tree/master/.NET/Microsoft.Recognizers.Text.DataTypes.TimexExpression
(Documentation and samples are behind here. But there are many illustrative unit tests.)
The package is published here:
https://www.nuget.org/packages/Microsoft.Recognizers.Text.DataTypes.TimexExpression/

We have also added a new sample showing TIMEX manipulation:
https://github.com/Microsoft/BotBuilder-Samples/tree/master/samples/csharp_dotnetcore/40.timex-resolution

The decision is that the missing fields in the results is "by design" and we think you should use the TIMEX library. If you can't easily create the missing fields you wanted in the result from the TIMEX values using the Timex Expression classes then open a bug on that.
Basically using the TIMEX library is going to lead to a much more robust implementation. There can be a lot of ambiguity even in the simplest of scenarios and working with the TIMEX is helpful.
Closing this issue now.


Debug why get_package returns different sets of pids than get_related_pids

Jesse mentioned this in Slack, here's an example he pasted:
get_related_pids(mn,"urn:uuid:0599306e-2ed9-4f5f-a5aa-f1f05e70cebe")
                                                  identifier                                                   documents1
             "urn:uuid:0599306e-2ed9-4f5f-a5aa-f1f05e70cebe"              "urn:uuid:0599306e-2ed9-4f5f-a5aa-f1f05e70cebe"
                                                  documents2                                                   documents3
"resource_map_urn:uuid:ff45529d-83d2-437b-bf62-3484ff4a5b4c" "resource_map_urn:uuid:3a731bb6-447a-4e61-95d8-3cb305eab60f"
                                                resourceMap1                                                 resourceMap2
"resource_map_urn:uuid:0599306e-2ed9-4f5f-a5aa-f1f05e70cebe" "resource_map_urn:uuid:cccda1ff-cac3-4dc2-8f35-90723622503f"
> get_package(mn,"urn:uuid:0599306e-2ed9-4f5f-a5aa-f1f05e70cebe")
$metadata
[1] "urn:uuid:0599306e-2ed9-4f5f-a5aa-f1f05e70cebe"

$resource_map
[1] "resource_map_urn:uuid:cccda1ff-cac3-4dc2-8f35-90723622503f"

$data
character(0)

$child_packages
[1] "resource_map_urn:uuid:ff45529d-83d2-437b-bf62-3484ff4a5b4c"
[2] "resource_map_urn:uuid:3a731bb6-447a-4e61-95d8-3cb305eab60f"

See what's going on.

get_related_pids was just returning the the identifier, resourceMap, and documents fields from the given PID's Solr document.
get_package does that, and more!
Should remove get_related_pids


Exclude project on windows

I have read the docs and edited my .wakatime.cfg to be like this
[settings]
api_key = XXXXXXX-XXXX-XXXX-XXXX-XXXXXX
exclude =C:\Users\informatic\JungleBird.Android
but waka time is still tracking that project. how to prevent waka from that?

Try this instead:
[settings]
api_key = XXXXXXX-XXXX-XXXX-XXXX-XXXXXX
exclude = [\\/]Users[\\/]informatic[\\/]JungleBird.Android

Since it's using POSIX regular expressions it needs backslashes escaped, and better to match both back and forward slash because both are accepted by WakaTime on Windows.


SQLMap API is NOT running Error

Preface - I tried following the troubleshooting steps in the other issue regarding the API not starting but it didn't solve it.
I'm on the latest version of Kali Linux VM using VirtualBox.  Latest version of BurpSuite Community Edition.
Jython version is jython-standalone-2.7.3.jar
When I try and start SQLMap API through burp it doesn't work, so I launch it through the CLI and (see screen shot below) it looks like it's run successfully but Burp still shows that the API is not running.
So far I've tried using python 3 and python 2, different ports and reinstalling burp all to no avail.
Greatly appreciate any help, thx.
Java Version:

SQL Map API Successfully running in CLI:

BurpSuite UI:

So if you manually start the API, the extension definitely WILL NOT show that it is running but it will WORK JUST FINE. You just have to manually set the scanner tab to point to the right IP and port.
I just downloaded the latest kali, did an apt update and apt upgrade, used the latest version of Burp and tracked this down.
This appears to be a bug in Jython 2.7.3 - I have been using 2.7.2. When I used the latest Jython (2.7.3) I had the same error but when I used 2.7.2 it worked.

Thanks for doing all of that troubleshooting.  I switched to jython 2.7.2 and still having the issues, this is the output I see.  There's nothing in the error logs or other logs from what I can tell, so just posting what I've found
I will try and get a fresh copy of kali and do all the steps you did but in the mean time maybe you see something from this output?

Did you unload/reload the extension with Burp pointing to Jython 2.7.2? If not, I am unsure how to recreate since I just today installed and updated the latest version of Kali (Kali-rolling 2022.4), the latest version of Burp (2022.9.6), the version of the extension in the BApp store (0.8.2), same version of Python (2.7.18), and used Jython 2.7.2 (I'm using the standalone Jython JAR file).
I'm using Burp Pro, but that shouldn't matter since that only changes extension output, not task creation.
The only other difference is Java version. I didn't bother to figure out installing JDK 11, I just went with what Kali had, which is OpenJDK 17.0.5.

Sounds like you got the API started with the extension, so this is a new problem? I don't see in the above where the API has been started, either way (if started manually) then this would be a whole separate problem.
If you go to the SQLiPy.py file for the extension and add "import traceback" underneath "import os" (around line #60), then add the following before the "print 'SQLMap task creation failed\n'" lines at #1560 and #1563:
print(traceback.format_exc())
It should give errors that will help resolve.

I just started with a fresh kali install, upgraded it etc just like you did earlier and now it's working.  Was able to get the UI to launch the API successfully, thanks for all your help!


Docs: Fix broken build due to PyYAML version

The version of PyYAML specified in the docs requirements file is invalid, and as such our docs builds have been failing. This fixes it.
How to test this PR
pip install -r requirements/docs.txt
mkdocs serve

Notes and todos
@willbarton I'm not sure what happened here. Your PR #8188 last updated this file and the checks all passed on your PR. Could the 6.0.livereload1 version of PyYAML have been published and then unpublished at some point? I can't seem to find any reference to this release at all.
Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)
[x] Code follows the standards laid out in the CFPB development guidelines

Huh. That's weird. It's possible that was a vim-user-error.