Add flag.Value for physic units

Add Set() to all unit.
Doc Set examples for all units.
Fix speed unit constant km/h.
Add tests for all setters.
Add simple decimal atod and dtoi helpers.
This is "functional" outline for flag.Value interface implementation.
There are some outstanding items including some "floaty" unit conversion complications such as Fahrenheit to mK. There probably should be some checks for how much loss of precision on unit conversion there is. SI units get maximum resolution as the SI prefix and exponent are combined when it is still in decimal form, however this is not the case when going from pico/nano/micro SI units to imperial units as they are int64 at that stage. I'm not sure on a clean way to fix this yet.
Thoughts?

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6cccd47). Click here to learn what that means.
The diff coverage is 97.42%.

@@            Coverage Diff            @@
##             master     #306   +/-   ##
=========================================
  Coverage          ?   71.33%
=========================================
  Files             ?       98
  Lines             ?     8749
  Branches          ?        0
=========================================
  Hits              ?     6241
  Misses            ?     2349
  Partials          ?      159

Impacted Files
Coverage Δ

conn/physic/units.go
98.47% <97.42%> (ø)

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 6cccd47...9db822a. Read the comment docs.

There are some outstanding items including some "floaty" unit conversion complications such as Fahrenheit to mK. There probably should be some checks for how much loss of precision on unit conversion there is. SI units get maximum resolution as the SI prefix and exponent are combined when it is still in decimal form, however this is not the case when going from pico/nano/micro SI units to imperial units as they are int64 at that stage. I'm not sure on a clean way to fix this yet.
Thoughts?

Often people uses float64 and then shrug off precision loss. Floating points values are also lossy, it's just that users can abstract away the pain.
I'm not super concerned about loosing a tad of precision for example when using Fahrenheit, as users using this unit are certainly not looking for µF precision, or they'd use a real unit. As long as the loss is within 0.001% or so.

gohci

Thanks heaps for the review. lots of good ideas in there. I'll split along the lines requested.

I'll fix this PR once #309 goes through.

Working on the unit rounding on conversions.

This still has problems with prefixed on units that start with the same letter as SI prefixes.
Doing them case by case is going to get fiddly and hard to reason about.
eg: "MMile", I believe that should be valid, not that anyone I know ever uses Mega miles.
The format should be Quantity|Prefix|Unit.

Its not as bad as I thought it might be even with the conditional rounding: If it is readable enough I will proceed with the other physic.units that have multiple units.
const (
	maxMiles  int64 = (maxInt64 - 500) / (int64(Mile) / 1000000) // ~Max/1609344
	maxYards  int64 = (maxInt64 - 5000) / (int64(Yard) / 100000) // ~Max/9144
	maxFeet   int64 = (maxInt64 - 5000) / (int64(Foot) / 100000) // ~Max/3048
	maxInches int64 = (maxInt64 - 5000) / (int64(Inch) / 100000) // ~Max/254
)

// Set sets the Distance to the value represented by s. Units can be provided in
// are miles, metres, feet, inches and yards with optional SI prefixes.
func (d *Distance) Set(s string) error {
	// Only default base metric unit has full range all other units are limited,
	// as any conversion calculations must fit inside a int64. Conversion math
	// should be ordered so as to maintain as much fidelity as possible.
	dec, n, err := atod(s)
	if err != nil {
		return err
	}
	prefix := prefix(none)
	if !(n == len(s)) {
		var n1 int
		prefix, n1 = parseSIPrefix([]rune(s[n:])[0])
		// Check for units that could be confused with prefixes.
		if prefix != none {
			switch strings.ToLower(s[n:]) {
			case "mile", "metre", "miles", "metres", "m":
				prefix = none
			}
		}
		if prefix != none {
			n += n1
		}
	}
	v, err := dtoi(dec, int(prefix-nano))
	if err != nil {
		return err
	}
	switch strings.ToLower(s[n:]) {
	case "mile", "miles":
		if v > maxMiles || v < -maxMiles {
			return &parseError{err: errors.New("too big use metric")}
		}
		if v >= 0 {
			*d = (Distance)((v*1609344 + 500) / 1000)
		} else {
			*d = (Distance)((v*1609344 - 500) / 1000)
		}
	case "yard", "yards":

		if v > maxYards || v < -maxYards {
			return &parseError{err: errors.New("too big use metric")}
		}
		if v >= 0 {
			*d = (Distance)((v*9144 + 5000) / 10000)
		} else {
			*d = (Distance)((v*9144 - 5000) / 10000)
		}
	case "foot", "feet", "ft":
		if v > maxFeet || v < -maxFeet {
			return &parseError{err: errors.New("too big use metric")}
		}
		if v >= 0 {
			*d = (Distance)((v*3048 + 5000) / 10000)
		} else {
			*d = (Distance)((v*3048 - 5000) / 10000)
		}
	case "in", "inch", "inches":
		if v > maxInches || v < -maxInches {
			return &parseError{err: errors.New("too big use metric")}
		}
		if v >= 0 {
			*d = (Distance)((v*254 + 5000) / 10000)
		} else {
			*d = (Distance)((v*254 - 5000) / 10000)
		}
	case "m", "metre", "metres":
		*d = (Distance)(v)
	default:
		return errNotUnits("m, Metre, Mile, Inch, Foot or Yard")
	}
	return nil
}

splitting.

I'm closing this PR and will just split the other units into there own PR as it too big all at once.


abort from configure if thread support isn't found

Ensure that not finding a working pthreads library causes the build
to fail (rather than continue and produce more cryptic errors later
on).
Also ensure that the pthreads header is included in sources which
call pthreads APIs.
Signed-off-by: Andre McCurdy<EMAIL_ADDRESS>

Codecov Report

Merging #19 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #19   +/-   ##
=======================================
  Coverage   64.87%   64.87%
=======================================
  Files          16       16
  Lines        4871     4871
  Branches      430      430
=======================================
  Hits         3160     3160
  Misses       1518     1518
  Partials      193      193

Impacted Files
Coverage Δ

source/broadband/webpa_parameter.c
65.78% <ø> (ø)
:arrow_up:

source/broadband/webpa_internal.c
41.34% <ø> (ø)
:arrow_up:

source/broadband/webpa_notification.c
23.74% <ø> (ø)
:arrow_up:

source/app/libpd.c
42.85% <ø> (ø)
: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 b5c36c8...e6804a9. Read the comment docs.


Handle RuntimeErrors in Command.process_collection

(fixes #15)

Coverage decreased (-3.6%) to 84.404% when pulling ad1ae270f90178be85920c4b3fe673796af0c9e0 on process_collection into c9d31f17f3132c090f4ccc76d1cb8aa0f155daab on master.


Fixing hypre solver memory access

Some bad combinations of views/subviews were causing runtime errors in many cases. This fixes those and makes it cleaner for when we will use GPU-enabled HYPRE.
@kwitaechong This should fix the bug you have been seeing.

Codecov Report

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

@@            Coverage Diff             @@
##           master      #28      +/-   ##
==========================================
+ Coverage   84.26%   84.32%   +0.05%
==========================================
  Files          32       32
  Lines        5632     5653      +21
==========================================
+ Hits         4746     4767      +21
  Misses        886      886

Flag
Coverage Δ

#mpicc
84.32% <100.00%> (+0.05%)
: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 0feb57c...900e8e9. Read the comment docs.

Codecov Report

Merging #28 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #28      +/-   ##
==========================================
+ Coverage   84.26%   84.32%   +0.05%
==========================================
  Files          32       32
  Lines        5632     5653      +21
==========================================
+ Hits         4746     4767      +21
  Misses        886      886

Flag
Coverage Δ

#mpicc
84.32% <100%> (+0.05%)
:arrow_up:

Impacted Files
Coverage Δ

src/Cajita_HypreStructuredSolver.hpp
62.5% <100%> (+1.77%)
: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 0feb57c...900e8e9. Read the comment docs.


While running the infer.py file for the custom video summarization I am getting an error

Loading DSNet model ...
Preprocessing source video ...
#ERROR
THCudaCheck FAIL file=/pytorch/aten/src/THC/THCGeneral.cpp line=383 error=11 : invalid argument
Predicting summary ...
Writing summary video ...

It seems to be a CUDA error. I google this error and find this issue https://github.com/pytorch/pytorch/issues/15797. Does it help you?

Yes, I saw that issue but for me running the infer.py script again helped to resolve the error
Thanks for helping


Error when using @RouteScope in components

I have a component annotated with @RouteScope and when I try to init the app in the test, I get the error:
Caused by: java.lang.IllegalStateException: No WebApplicationContext found: no ContextLoaderListener registered?
	at org.springframework.web.context.support.WebApplicationContextUtils.getRequiredWebApplicationContext(WebApplicationContextUtils.java:85)
	at com.vaadin.flow.spring.scopes.VaadinRouteScope$RouteBeanStore.getContext(VaadinRouteScope.java:372)

This is the code in my test class:
  private static final Routes routes = new Routes().autoDiscoverViews("the.package");

  @Autowired
  private ApplicationContext ctx;

  @BeforeEach
  public void mockVaadin() {
    final Function0<UI> uiFactory = UI::new;
    final SpringServlet servlet = new MockSpringServlet(routes, ctx, uiFactory);
    MockVaadin.setup(uiFactory, servlet);
  }

To fix this error, I've changed the mockVaadin() function to:
  @BeforeEach
  public void mockVaadin() {
    final Function0<UI> uiFactory = UI::new;
    final SpringServlet servlet = new MockSpringServlet(routes, ctx, uiFactory);
    MockVaadin.setup(uiFactory, servlet);
    servlet.getServletContext()
        .setAttribute(WebApplicationContext.ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE, ctx);
  }

I think we should do this setup somewhere in karibu. My first idea is to add the code that sets the WebAplicationContext inside MockVaadin.setup. What do you think?

Hi Bruno, thanks for letting me know! Actually this should have been performed in MockSpringServlet.init() at line 58, which should have been called by MockVaadin.setup() at line 88. I've tried to debug Karibu internal tests and the init() function seems to be called; however in your case for some reason it's not called. Could you please try to debug through MockVaadin.setup() a bit, to see what's going on?

Hi Martin, I will try with karibu-testing 1.3.18 and check if it still happening. If it is, I will debug and see what I can come up with.

In 1.3.18 the WebApplicationContext is being, I see this was added in 1.3.13: https://github.com/mvysny/karibu-testing/commit/fd2bd453eb698ec289c60c91426078edc1bc396d. With version 1.3.18 I get another error. I will try to debug it and I will open another ticket if I find it isn't anything specific to my code.


depthai_demo.py fails with exception and told me to report to developers

Running depthai_demo.py with face-detection-retail-0004 for 12 shaves throws exception and tells me to report to developers.
Setup

Microsoft Windows [Version 10.0.19044.1348]
depthai repo at main currently d51f032df0a100f2879ca7318da333fb779cb6ec
python 3.9.5 64-bit

Repro

Follow instructions from https://docs.luxonis.com/en/latest/pages/tutorials/first_steps/#setup
activate the venv
Run python depthai_demo.py
see the default model run correctly
change model to face-detection-retail-0004
click apply restart
restart depthai_demo.py if the app completely exits
change model to face-detection-retail-0004 again if the app exited
see face model working
change shaves to 12
click apply restart
restart depthai_demo.py if the app completely exits
change model to face-detection-retail-0004 again if the app exited
click apply restart
download happens in background... then...

Result
App throws exception. Tells me to report to developers.
Windows dialog also appears.

(venv) C:\njs\depthai>python depthai_demo.py
Using depthai module from:  C:\njs\depthai\venv\lib\site-packages\depthai.cp39-win_amd64.pyd
Depthai version installed:  <IP_ADDRESS>
Setting up demo...
Available devices:
[0] 14442C10C1A1C6D200 [X_LINK_UNBOOTED]
USB Connection speed: UsbSpeed.SUPER
Stopping demo...
=== TOTAL FPS ===
[color]: 28.2
[nnInput]: 23.7
[depthRaw]: 24.9
[depth]: 24.9
[left]: 27.0
[rectifiedLeft]: 23.6
Setting up demo...
[right]: 26.4
Available devices:
[rectifiedRight]: 24.6
[nn]: 23.6
[0] 14442C10C1A1C6D200 [X_LINK_UNBOOTED]
USB Connection speed: UsbSpeed.SUPER
Downloading C:\Users\dale\.cache\blobconverter\face-detection-retail-0004_openvino_2021.4_12shave.blob...
[==================================================]
Done
[14442C10C1A1C6D200] [15.506] [SpatialDetectionNetwork(14)] [warning] Network compiled for 12 shaves, maximum available 13, compiling for 6 shaves likely will yield in better performance
[14442C10C1A1C6D200] [15.680] [system] [critical] Fatal error. Please report to developers. Log: 'ResourceLocker' '162'
Stopping demo...
=== TOTAL FPS ===
[color]: 30.5
[left]: 0.0
[right]: 0.0
  File "C:\njs\depthai\depthai_demo.py", line 548, in run
    self.instance.run_all(self.conf)
  File "C:\njs\depthai\depthai_demo.py", line 61, in run_all
    self.run()
  File "C:\njs\depthai\depthai_demo.py", line 256, in run
    self.loop()
  File "C:\njs\depthai\depthai_demo.py", line 283, in loop
    self._pv.prepareFrames(callback=self.onNewFrame)
  File "c:\njs\depthai\depthai_sdk\src\depthai_sdk\managers\preview_manager.py", line 113, in prepareFrames
    packet = queue.tryGet()
Communication exception - possible device error/misconfiguration. Original message 'Couldn't read data from stream: 'color' (X_LINK_ERROR)'

Log
log_system_information.zip
Expected
No errors and 12 shaves being used.

Thanks for the report!
The issue is related to the allocation of 2 inference threads here:
https://github.com/luxonis/depthai/blob/766ebed/depthai_sdk/src/depthai_sdk/managers/nnet_manager.py#L164
Looks like it tries to allocate 2x the number of shaves the model is compiled with.
Changing it to 1 in the code, it would work with up to 13 shaves (limited by this config with cameras, depth, spatial position calculation).
But in fact, having 2x threads (with one NCE - neural compute engine per thread) and max 6 shaves per thread, if probably performs better than a single thread with more shaves.
@VanDavv Maybe we could make it more clear in the GUI, specifying this as number of shaves per thread, and have also the number of threads configurable.
CC also @szabi-luxonis on the firmware falling back to a single thread (with a warning) for this case.

The issue is not related to the above-mentioned number of threads, it's an internal resource allocation issue in firmware. Will issue a fix.

🤪What you said @alex-luxonis 😉
I have much to learn about the onboard capabilities of OAK: NN, hardware threads, shaves, etc. Not only the tech, but the "feel" of the tech. This demo py looks like an excellent place to experiment and learn -- hence -- me trying different shave counts to see how it affects NN fps, latency, or "feel".
The demo GUI did caution me that it probably runs better with 6 shaves. 🙉
Is your fuzz testing in place? Randomly choosing config options and then run and see what breaks. Good opportunity for automation. a few rand(), a run(), and watch for smoke. 😂

That's true, we need to improve the testing...

The issue is not related to the above-mentioned number of threads, it's an internal resource allocation issue in firmware when setRuntimeModeSwitch is enabled.

Ok, so the number of NN threads just indirectly affected the initial allocation for StereoDepth. I tried just with: 1x13 working, 2x6(default) working, 2x7 failing, 3x4 working, 3x5 failing.

@diablodale this is fixed in latest main.

Verified fixed with main f54806f894f940ffbd34ac9d55f157e3eb568f18
thanks!


Makefile: rewrite that make build is stable

make build now creates all needed directories
and files only if needed
please check if you can use this or parts of it
you can also keep devel-uninstall if you want it, but as a common practice, please also add clean
(e.g. devel-uninstall: clean if you want to keep it )

"Parent" pull-request was already merged - this is obsolete now


Realtime for replays not working

Hi,
I was trying to set coordinator->SetRealtime(true); and then launching a replay. The replay loads but it gets stuck on the first game loop, or rather before that. OnGameStart() gets called and also ends. But OnStep() never gets called. When I pause the execution it seems that it waiting here.
Looking at issue #167 it seems that it already worked at one point.
Regards

Hi, is there any update to this? Further than just "getting stuck" - it seems that sending realtime: true (from the proto side of things) in the RequestStartReplay is simply ignored / starts the game in step mode.

Hi, any update on this? It was apparently fixed in #167, but it isn't working


Fix worker can't figure out owner of a job

The patch fixes uncaught exception RuntimeError:
I could not figure out the owner of the requested job.
Please pass --owner .
Worker dies with unhandled exception in run_with_watchdog
if it can't figure out owner of a job, which it tries
to kill when job runs longer then given limit of time.
Signed-off-by: Kyr Shatskyy<EMAIL_ADDRESS>

Can one of the admins verify this patch?

ok to test


Adjusted api calls to use string numbers

@DavidVorick You said Sia master had merged something that changed number returns from API to strings? I don't see that on the Sia repo

Is this PR working with the recent 'siad'? I'm pretty sure the code changed at some point. Perhaps in Luke's 85 commit PR?

Luke's PR seemed to not change anything about the host api that would change the UI, correct me if I'm wrong.
The renter no longer has a 'Repairing' field to its file list, that's alright I responded to that in my renting branch


feat: update golang-github-openzipkin-zipkin-go to 0.1.5+git20190103.2fd7f4a

Zipkin tracer library for go
Issue: https://github.com/linuxdeepin/developer-center/issues/3965
Log: update repo

/test all


Update Composer dependencies (2022-05-26-00-05)

Visual regression test passed!
View the visual regression test report


Correction for raw affiliation PHIM Plant Health Institute, Univ Montpellier, INRAE, CIRAD, Institut Agro, 34398 Montpellier, France

Correction needed for raw affiliation PHIM Plant Health Institute, Univ Montpellier, INRAE, CIRAD, Institut Agro, 34398 Montpellier, France
raw_affiliation_name: PHIM Plant Health Institute, Univ Montpellier, INRAE, CIRAD, Institut Agro, 34398 Montpellier, France
new_rors: 05kpkpg04;051escj72;03fkrcm40;03rnk6m14;003vg9w96;05y5s3h28
previous_rors: 05kpkpg04;051escj72;03fkrcm40;03rnk6m14;003vg9w96
works_examples: W4221046387
contact: 33c58ee361b29c499c2a0636f236f4e3:73e05021d43a03bf8e566e52c3b893a921f2 @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-18. The new affiliations should be visible within the next 7 days.


Conver commands to a dockerfile to image

We currently have a lot of commands to run the app. Can we convert them to a Docker file then image?
git clone git@github.com:v-limo/reservations.git &&
cd reservations &&
cd Reservations.Api &&
dotnet build &&
dotnet ef migrations add InitialMigration &&
cd .. &&
docker compose -f "docker-compose.yml" up -d --build &&
open http://localhost:5165/swagger/index.html &&
cd Reservations.Api &&
dotnet ef database update

Fix this by using SQlite on the main branch. now we have one docker image that run both the database and the api


System Time - impossible to see the country/city when changing Time Zone

When changing time zone it will show very little information as you can see in this picture:

I don't know if it has something to do with the incompatible of 19.19 with older webmin?

Thanks.


fix: prevent top level package from getting accidentally published

the top level package is only a lerna wrapper, it isn't intented to be
released to npm.
See: https://docs.npmjs.com/files/package.json#private

thx for noticing that, I had it as such previously and was messing w/ just trying to get it published today.


Testing with high-resolution images

Hi,
I'm trying to test on the Tanks and Temples dataset. The command is as follows:
export scene=Family
python test.py --dense_folder /path/to/tankandtemples/intermediate/$scene --regularization '3DCNNs' --max_w 1920 --max_h 1056 --max_d 256 --interval_scale 1.0 --pretrained_model_ckpt_path /path/to/tf_model_dtu --ckpt_step 150000

I tested on GPU with 24GB of memory, but the program could not run due to memory consumption.
How do I test on the Tanks and Temples dataset using the same conditions as in the paper?

I think the regularization using 3DCNNs consumes a lot of memory due to its 3D convolution. So, it could have the problem with high-resolution images.
I am not sure about the true parameters used for the evaluation in the paper, I think the first step to resolve the problem is to try --max_w 1152 --max_h 864 --max_d 192 --interval_scale 1.6 which can largely save the memory. As far as I tested, the program consumed all 11 GB of my GTX 1080 Ti but worked properly when being run with those parameters.
Also, I noticed that you should specify --interval_scale 0.8 when you specify --max_d 256.
Hope it helps.

It shouldn't be... I was using a V100 GPU (16GB) on google ml platform to do the experiments.
But also I found tensorflow GPU usage is somewhat unpredictable when using different GPUs...


ci: Fix bentobox-sim build not properly taking advantage of Docker Layer caching

Fixes: #12
Fixes bentobox-sim build not properly taking advantage of Docker Layer caching by:

Adds project makefile target  dep-sim  that does pulls in build dependencies without building.
Split out depdendency fetching sim/CMakeLists.txt  into dependencies.cmake.
dependencies.cmake is a standalone CMakeList.txt that can be used to fetch dependencies only.
Since the dependencies are pulled in before the source code is copied in the Dockerfile, this should allow them to cached even while Sim's source code changes.

LGTM :+1:

LGTM :+1:


Windows + Anaconda = Won't show process + Bulk Related Question

Just to be clear, I'm not a programmer but I've noticed that compare to other repos I tried on my local machine while testing your awesome repo.
Usually when processing (anything) it shows on Anaconda Prompt (or any console using) either progress bar with percentage and some information while it's "cooking" but in this one it won't show anything on windows and anaconda at least.
So when I run for example:
backgroundremover -i ./_SOURCE_/image.jpg -o ./_RESULT_/output.png
It will show the blinking underscore  _
and it works but no indication how much time it takes, or any info that could be helpful while it's processing.
So either I'm doing something wrong, or it's just not in the code for now on windows at least?
If it's not there yet, will you please consider to add this process status, it sure give some indication such as time estimate or how long it runs and the percentage of each task (image, multiple images or video when it will work on windows of course).

Another question: (multiple images / bulk)
Please consider that I'm not a programmer so I don't know how to mess with the code.
Is there a parameter I can add when I run "backgroundremover " so it will run ALL images on my input directory?
If not, will you consider to add such parameter? (could be cool for both multiple images, and videos) instead of testing one by one.
Thanks ahead for replying, keep up the good work! 👍

The bulk was a request in issue https://github.com/nadermx/backgroundremover/issues/22, they put a piece of code there to do that while I work on the native path upload currently

The bulk was a request in issue #22, they put a piece of code there to do that while I work on the native path upload currently

Thanks for the quick reply, I tried that.. but couldn't make it to work I'm not a programmer and it was confusing me... maybe if later on you'll add it as extra parameter it will be much easier to use even for newbies like me. :)

I hope you can read what I asked about the Process status and share if there are any planse,
BTW - I'm willing to help testing any Windows + Anaconda so feel free to message me if you like to test new improvements or experiments in general.
I hope you can improve the processing as it's blindly waiting without have no indication at all.
I'm curious if it does work for Linux but not for Windows / Anaconda (yet).

Try the new version, should work on windows pip install --upgrade backgroundremover


Testing (cargo test, uses docker-compose file that I've placed into tests/postgres.yml)

Spelling (typos)

Clippy (cargo clippy)

I have not included the coverage check at this point, and also not the cargo-deny check (due to lack of a deny.toml).
Besides that:

Fixes some spelling errors, caught by typos (which is awesome btw, I did not know it before)
Some tests are failing and I don't know how to fix them yet (should not be too hard).

fixed them on main!


Added ImageResizer resources.dlls to the MSI installer required for localization (dev/imageResizer)

Summary of the Pull Request
This PR adds the resources.dll files for each language in the MSI installer. For example the Imageresizer.resources.dll for french is stored in modules\fr\ImageResizer.resources.dll as this is the location recognized by the C# executable. A similar step will have to be done for FancyZonesEditor when it is translated (@crutkas note this would be needed later on for #199 for any C# projects. ImageResizer already has almost all the strings translated).

This PR also changes the ImageResizer registry entries to HKCU so that they are installed per user instead of per machine.

PR Checklist

[X] Applies to #53
[X] CLA signed. If not, go over here and sign the CLA

Validation Steps Performed
Build Release x64 of PowerToys and PowerToysSetup and install using MSI.
After verifying the ImageResizer works by right-clicking an image in file explorer, switch the OS language to another language in this list (ar;bg;ca;cs;de;es;eu-ES;fr;he;hu;it;nb-NO;nl;pl;pt-BR;ru;sk;tr;zh-Hans) and sign out and back in. ImageResizer should now show the translated UI.

Is this the only possible way to support localization? It seems it will become unmanageable very quickly.

@crutkas
sure, I added a comment to the issue.

xaml based. :)


BUG: Comments Box does not get displayed in FrontEnd

For any unknown reasons, the comments will not be displayed. This really needs to be fixed before launch.

done.


CSS + SCSS configuration

I load both .css and .scss as
{                     test: /\.scss$/,                     loader: ExtractTextPlugin.extract("style-loader", "css-loader!sass-loader"),                     include: paths,                 },
                {                     test: /\.css$/,                     loader: ExtractTextPlugin.extract("style-loader", "css-loader"),                     include: paths                 },             ]
Now when i apply PurifyCss plugin, it does not include any style from any of .scss files. (works as expected for .css files). When i remove purify plugin, styles from .scss files are loaded.

check #55

You'll need to configure the resolveExtensions config.
    new PurifyCSSPlugin({
      basePath: path.join(__dirname, 'portal', 'js'),
      resolveExtensions: ['.html', '.js'],
      paths: [
        'app/**/*.js',
        'tpl/**/*.html',
      ],
    }),

Closing in favor of #55.


any-nix-shell: init at 1.1.0

Motivation for this change
This adds fish and zsh support for both nix run and nix-shell. More supported shells can be added in the future.
Supersedes #46630 as this is version 1.1.0
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Fits CONTRIBUTING.md.

@grahamcofborg any-nix-shell

@GrahamcOfBorg build any-nix-shell

Success on aarch64-linux (full log)
Attempted: any-nix-shell
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/m0f347mldvgh93frg60gbryq6rz754lb-any-nix-shell-1.1.0
strip is /nix/store/428gs2z4b8f9byvghzlpbjwjb3a7jwxx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/m0f347mldvgh93frg60gbryq6rz754lb-any-nix-shell-1.1.0/bin
patching script interpreter paths in /nix/store/m0f347mldvgh93frg60gbryq6rz754lb-any-nix-shell-1.1.0
/nix/store/m0f347mldvgh93frg60gbryq6rz754lb-any-nix-shell-1.1.0/bin/.any-nix-shell-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/017xymp5i03qzigafnfx7sgf6602gmzq-bash-4.4-p23/bin/sh"
/nix/store/m0f347mldvgh93frg60gbryq6rz754lb-any-nix-shell-1.1.0/bin/nix-shell-info: interpreter directive changed from "/bin/sh" to "/nix/store/017xymp5i03qzigafnfx7sgf6602gmzq-bash-4.4-p23/bin/sh"
/nix/store/m0f347mldvgh93frg60gbryq6rz754lb-any-nix-shell-1.1.0/bin/.any-nix-shell-wrapper: interpreter directive changed from "/bin/sh" to "/nix/store/017xymp5i03qzigafnfx7sgf6602gmzq-bash-4.4-p23/bin/sh"
/nix/store/m0f347mldvgh93frg60gbryq6rz754lb-any-nix-shell-1.1.0/bin/.any-nix-run-wrapper: interpreter directive changed from "/bin/sh" to "/nix/store/017xymp5i03qzigafnfx7sgf6602gmzq-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/m0f347mldvgh93frg60gbryq6rz754lb-any-nix-shell-1.1.0...
/nix/store/m0f347mldvgh93frg60gbryq6rz754lb-any-nix-shell-1.1.0

Success on x86_64-darwin (full log)
Attempted: any-nix-shell
Partial log (click to expand)
installing
post-installation fixup
strip is /nix/store/9xjkb4xz0b5lmizij9ppxy7lkxdxhx6b-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/fwnjppny28ryfql8rmg4746x47jg5z94-any-nix-shell-1.1.0/bin
patching script interpreter paths in /nix/store/fwnjppny28ryfql8rmg4746x47jg5z94-any-nix-shell-1.1.0
/nix/store/fwnjppny28ryfql8rmg4746x47jg5z94-any-nix-shell-1.1.0/bin/.any-nix-run-wrapper: interpreter directive changed from "/bin/sh" to "/nix/store/f2lp21azk4w88f17zgf4mji64agb18ga-bash-4.4-p23/bin/sh"
/nix/store/fwnjppny28ryfql8rmg4746x47jg5z94-any-nix-shell-1.1.0/bin/.any-nix-shell-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/f2lp21azk4w88f17zgf4mji64agb18ga-bash-4.4-p23/bin/sh"
/nix/store/fwnjppny28ryfql8rmg4746x47jg5z94-any-nix-shell-1.1.0/bin/.any-nix-shell-wrapper: interpreter directive changed from "/bin/sh" to "/nix/store/f2lp21azk4w88f17zgf4mji64agb18ga-bash-4.4-p23/bin/sh"
/nix/store/fwnjppny28ryfql8rmg4746x47jg5z94-any-nix-shell-1.1.0/bin/nix-shell-info: interpreter directive changed from "/bin/sh" to "/nix/store/f2lp21azk4w88f17zgf4mji64agb18ga-bash-4.4-p23/bin/sh"
/nix/store/fwnjppny28ryfql8rmg4746x47jg5z94-any-nix-shell-1.1.0


added matomo upgrade instructions

Added instructions on how to recreate the matomo volume in order to update to a new version of Matomo
Purpose / why
Upgrading from buildkit 1.x to 2.x requires updating matomo
What changes were made?
instructions added
Verification

Create a site using TAG 1.0.10
Set Matomo to track site visits so that you get some data in your Matomo database
upgrade to TAG 2.0.10
Follow these instructions to update Matomo to 4.15.1
Check that site data is still available and that new site visits are tracked

Interested Parties
https://github.com/Islandora-Devops/isle-dc/issues/356

@Islandora/documentation
@Islandora/committers

Checklist
Pull-request Reviewer
Pull-request reviewer should ensure the following:

[ ] Does this PR link to related issues?
[ ] Does the proposed documentation align with the Islandora Documentation Style Guide?
[ ] Are the changes accurate, useful, free of typos, etc?

Person Merging
The person merging should ensure the following:

[ ] Does mkdocs still build successfully? (This is indicated by TravisCI passing. To test locally, and see warnings, see How To Build Documentation.)
[ ] If pages are renamed or removed, have all internal links to those pages been fixed?
[ ] If pages are added, have they been linked to or placed in the menu?
[ ] Did the PR receive at least one approval from a committer, and all issues raised have been addressed?

These instructions may cause a loss of installed plugins, as possibly other customizations. I think more investigation is required.
Looks like the recommended way is to update through the web UI, so maybe we should document that instead.
https://github.com/matomo-org/docker/issues/248


Removing two dead links

Hey @sbilly,
just removing two dead links here.
Cheers!

please do some search before you delete dead link


Refactor: adding flutter linter rules

Description:
The addition of linter rules to our Flutter project to ensure code quality and maintainability. Linter rules can help us catch potential issues early in the development process and maintain a consistent coding style.
Tips for the issue:

Research and identify a set of Flutter-specific linting rules that align with best practices and our project's goals.
Configure the selected linter rules in our project, ensuring they are compatible with our current codebase.
Improve the overall code quality and maintainability of our Flutter project.

To do:

[ ] Ask us to assign the issue
[ ] Once the issue is assigned, you can start working on it
[ ] Create a PR

Resources:

dart/linter-rules
package/flutter-lints

Note:
The task is assigned to contributors on a first-come, first-serve basis, and the contributor has to report progress every 3 days to ensure active development on the tasks.

@dk-a-dev
Please assign this issue to me.

@RitwikSingh28 ye sure it's assigned, please stick to the note mentioned


Cannot get plugin to use Http instead of Https

Hi
The company I work for is using a firewall, with a self-signed certificate, which decrypts and reencrypts all https traffic between us and the internet, which (among other things) breaks the download of Android SDK updates via https.
I've tried setting the system property android.preferHttp to 'y' in gradle.properties (and in the Windows environment variables) but the sdk-manager-plugin tries to download via https anyway.
I can read the system property by manually calling "println java.lang.System.getProperty('android.preferHttp')" in a Gradle task.
How do I supply the system properties to the sdk manager plugin so that it doesn't use https?
TIA

It appears that when the the code was merged together (in https://github.com/JakeWharton/sdk-manager-plugin/pull/21) the part about the https property wasn't added (only the proxy part made it to master).
Is it possible to have it re-added again?


LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20211205163431594 to main

LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20211205163431594 to main with localized lcls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 41.696%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
27272

Relevant Lines:
59354

💛  - Coveralls


About the additional computation for sigma

can you explain these codes in lines 48-49 that do not appear in the paper, thank you.
especially why do pow computation with exponent 3?
sigma = torch.sigmoid(sigma * 5) + 1e-5
sigma = torch.pow(3, sigma) - 1

Same question.


docs: Create initial biolatency guide

This PR implements a simple guide about the biolatency gadget. It could be still improved by using additional flags of the stress tool and when we will have the possibility to use the different options that the BCC biolatency script offers.
Fixes #309

Some minor comments. I'm not sure about the spelling of I/O's. Should it be just 'I/O'?

Or I/Os?

@mauriciovasquezbernal @alban I modified it to "I/O operations" or simply "I/O" where "operations" can be omitted.
In addition, I also added the reference to the BCC documentation.


Literature Research for modeling tools

[ ] read paper of Ross Brown about modeling in virtual reality
[ ] do research about other modeling tools (e.g., gryphon paper) or summarize what you already have done (see google doc of tool research)
[ ] write short related work section about results and motivate why we implement a tool

I assume this to be obsolete [close]


Improve lint

Currently we have a 12% for go lint.
I suggest to make multiple PR by files to improve this and to raise the percent higher.

And since I also added it to the drone CI run the tests are also failing because of that ;)

@xinity do you want this one? otherwise I can take care of it :)

I think this is resolved via #12 & #13


colllection: add open source forem software collection

Close https://github.com/pingcap/ossinsight/issues/552

https://ossinsight.io/collections/open-source-forem-software


pull request for e2e test at 12/07/2016 14:56:02

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Update SwipableCarouselView.js

In the latest version of the react-swipeable-views package a few features have been moved to the react-swipeable-views-utils package instead

Seems like react-swipeable-views package just needs an update to 0.10.7 to include the utils package.
https://github.com/oliviertassinari/react-swipeable-views/blob/master/packages/react-swipeable-views/package.json#L27

Indeed, @saschb2b. So let's merge this and update react-swipeable-views then. :+1:


NumericBox should support BigDecimal by default

I tried to pass the code to checkStyleForJava extension. Link: https://github.com/DwcJava/engine/tree/issue%2361

According to the docs , BBjInputN supports only floats.
https://documentation.basis.cloud/BASISHelp/WebHelp/bbjobjects/Window/bbjinputn/bbjinputn_setvalue.htm

Update: The implementation will support Double, the client component cannot handle BigDecimal at the moment


Dockerhub tags out of date

FYI it looks like the tags for this are out of date, which seems to have been causing me troubles.
https://hub.docker.com/r/jfloff/alpine-python/tags
E.g. the latest tag is 10 months old, seemingly using an old Dockerfile (for Alpine 3.7).

IIRC I've removed the tags for recent/latest and replaced them with the specific tag versions. That is, instead of jfloff/alpine-python:latest try jfloff/alpine-python:3.6

Hey! I just realized how dumb I was and how little knowledge of Travis I have 🤦♂
I just updated the latest, latest-slim, and latest-onbuild! Feel free to check them out ;)


Verticacrossman patch 3

Variosu changes to readme, configuration.md and example1 in both examples and cmd dirs re fix for timeseries issue

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Sample Data: document, update scripts to validate, update tests

Pull Request
This Pull Request composes the necessary documentation and tests to develop, validate, and navigate TIDES data samples.
Documentation:

Documents sample data structure in samples/README.md (which then is added to the /samples page of documentation)
Documents available samples in samples.md (which becomes the /samples page of the documentation)
Documents the structure of a tides data package using a macro which reads tides-datapackage-profile
Updates CONTRIBUTING.md documentation

Code:

Adds a very lightweight script in samples/template/scripts/create_template_files.py which updates the template files based on the fields in the various table schemas. note: this isn't run automagically anywhere b/c I think this wasn't a universally desired feature
2 Add validation script /bin/validate-datapackage: validate a datapackage and its contents based on profile/spec specified in the datapackage, a local spec, or a remote spec based on its github reference.
Add validation script /bin/validate-datapackage-to-profile:  validate a datapackage file to the tides datapackage profile   based on profile/spec specified in the datapackage, a local spec, or a remote spec based on its github reference.
Splits tests/test_all into three scripts that we may want to use with different behaviors:

test_local_spec  validates the local spec, documentation, and code
test_samples_to_canonical validates the local samples to the canonical spec and
test_samples_to_local validates local samples to local spec

Spec:

Updates tides-datapackage-profile table schemas to be a string location to be consistent with most other profiles rather than an object.
Updates tides-datapackage-profile examples to make it easier to use in documentation.
Removes table-schema.json b/c I don't think we needed it

Replaces https://github.com/TIDES-transit/TIDES/pull/100 which was mistakenly from a fork...

[x] Pull-requests must address an existing issue
[x] Update relevant documentation.

By contributing to this project, all contributors certify to the Developer Certificate of Origin in CONTRIBUTING.md.

@e-lo, this PR includes the first commit of these samples, tides-datapackage-profile.json, and validation of those samples using the new profile. Since the validation process relies on the contents of samples/template/TIDES/datapackage.json, which points to raw files on the main branch, testing was failing on tides-datapackage-profile.json, which doesn't yet exist on that branch. During testing, I pointed the data package file to this branch rather than the main branch to work through other issues and ensure that validation will work once merged.
After working around a ton of issues related to JSON parsing between different steps in the validation workflow, I kicked off two runs of validation (one with errors and one without) to show that that the GitHub workflow works on both - prior to the JSON parsing changes, the validation step and/or the comment publishing step would fail to complete on any non-passing data (for multiple reasons that probably aren't worth going into here).
I changed the ref in that file to point to this branch in order to show that validation could pass, but after we merge this we'll need to point the URLs referenced in samples/template/TIDES/datapackage.json back to main instead of the branch references that were used for testing this new validation step.
Other than that follow-up task at merge time, this looks ready to me!


Support CARGO_TARGET_DIR env var

Hi,
I have CARGO_TARGET_DIR env set in my shell, and have to manually disable it while building or working with anchor.
And it's a little hard to always remember to unset the variable.
This PR will support using target dir that is defined in CARGO_TARGET_DIR if available or fallback to local target directory.
It is not fully done, i need your opinion about where should we move types, idl and deploy folder.
As it's used in typescript tests and we don't want to store deploy keys and types of project into global cargo target dir.
I suggest we use another directory inside anchor project for artifacts.

Ok, so instead of compiling to target/ it just compiles to a different directory. I don't know if it's worth the effort to support this. It looks like a lot of changes and you're the first person to complain about this I think.

Yeah, it need a lot of changes, but it mostly is because anchor is storing all of it's artifacts in target directory, which is a cargo related folder.
I'm almost convinced that it's not worth the effort.
But if we want to do this, maybe we should put artifacts in another folder, so we can change cargo target dir easily.
I know this change will be a breaking one and all of the projects depending on Anchor have to modify a lot of their script and files.
So it's your call, i can do the changes.

As you say it's a heavily breaking change. It's really unfortunate that it
messes with your cargo setup but I just don't know if that's enough to
justify such a big change. Hopefully next time around if anchor gets a big
rewrite we can make sure to only put cargo artefacts in the target
directory and make a separate anchor folder for that other stuff.
On Thu, Feb 23, 2023, 4:24 PM Kaveh @.***> wrote:

Yeah, it need a lot of changes, but it mostly is because anchor is storing
all of it's artifacts in target directory, which is a cargo related
folder.
I'm almost convinced that it's not worth the effort.
But if we want to do this, maybe we should put artifacts in another
folder, so we can change cargo target dir easily.
I know this change will be a breaking one and all of the projects
depending on Anchor have to modify a lot of their script and files.
So it's your call, i can do the changes.
—
Reply to this email directly, view it on GitHub
https://github.com/coral-xyz/anchor/pull/2402#issuecomment-1442067465,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADAHMGFX447QRGEZB3WNIGLWY6FLLANCNFSM6AAAAAAVDIQJAE
.
You are receiving this because you commented.Message ID:
@.***>

Yup, good idea.
And thank you.


Cannot do anything with mini player

Once I have the mini player in use, I can no longer do anything with it, as in I can't bring back the main screen to change album/playlist etc. The 'maximise' icon (or whatever it is called) that used to appear at the bottom-right of the mini player window no longer appears. My hotkeys still work, though, and I can still use the system tray icon menu, but that only allows me to do certain things. What I have to do now if I want to listen to something else is quit the app from the system tray icon and then re-open the app. I would say I have only noticed this in the last two months or so.

This has been fixed in master.  If you are on linux you will need to update manually.


Devices do not show in home app

Describe Your Problem:

Hello! I just installed this plugin, and I cannot get it to show anywhere in home app. It shows in the home ridge log that it found both the 3 button raise lower and two button remotes, but does not show anywhere in home app
Logs:
Show the Homebridge logs here, remove any sensitive information.

Plugin Config:
Show your Homebridge config.json here, remove any sensitive information.

Screenshots:

Environment:

Plugin Version: 1.5.3
Homebridge Version: 1.5.0
Node.js Version: 16.18.0
NPM Version:
Operating System: raspbian

are you running an iOS beta?

I was able to find the toggle to create the child bridge and it works now!  Thanks!


pybind11_json_vendor: 0.2.1-1 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository pybind11_json_vendor to 0.2.1-1:

upstream repository: https://github.com/open-rmf/pybind11_json_vendor
release repository: https://github.com/ros2-gbp/pybind11_json_vendor-release.git
distro file: humble/distribution.yaml
bloom version: 0.11.2
previous version for package: 0.2.0-1

Holding for humble sync


[Major] Button focus update & related components

Fix #990 and #991.

And also:

File Input styles updated to fit the new styling.
Toggle Group styles are updated to fit the new styling. Also, the component changes its background-color from #fafafa to transparent.

Thanks for everything @aweell, enjoy your next chapter! 🙂


Query's to the db not returning anithing.

I am finding:
warning: process /usr/lib/postfix/sbin/smtpd pid 21353 exit status 1
Feb 16 11:31:12 mail postfix/master[21178]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling
in the logs
From what i can tell none of the query's are answering from then db.
Connection is fine but if i run the query from mysql interface i get the Empty set:
Database changed
MariaDB [mum]> SELECT 1 AS found FROM mailboxes INNER JOIN domains ON mailboxes.domain_id = domains.id WHERE mailboxes.local_part = '%u' AND domains.domain = '%d' AND domains.active = 1 AND mailboxes.active = 1 LIMIT 1;
Empty set (0.000 sec)
Is there something i missed in install?
Install is on updated ubuntu 20.04 php7.4 mariadb 10.3

When you tried to manually query your database, did you replace the Postfix placeholders %u and %d with actual values?
I have a MariaDB server running with version 10.3.27 and, at least for me, the query works as expected:
MariaDB [mum]> SELECT 1 AS found FROM mailboxes INNER JOIN domains ON mailboxes.domain_id = domains.id WHERE mailboxes.local_part = 'user' AND domains.domain = 'example.com' AND domains.active = 1 AND mailboxes.active = 1 LIMIT 1;
+-------+
| found |
+-------+
|     1 |
+-------+
1 row in set (0.001 sec)

If Postfix cannot get answers from the database, try increasing the debug log level in /etc/postfix/master.cf, see Postfix Debug Docs.
    smtp      inet  n       -       n       -       -       smtpd -v

Please check if you ...

... can execute the query with correct values for %u and %d in your SQL console
... have users in your table at all, if the query does not work
... increase the log level for Postfix and post the relevant log messages.

Closing due to inactivity


Compare dedicated sandbox node vs attached to an existing node as a script

Explain that you can run the scripts in a dedicated sandbox node or attached to an existing node like any other script and preface the recommendation of using a sandbox mode.
A single "Comparison" section would help us quickly understand why you want one style over the other.

Makes sense

I added information about dedicated sandboxes: http://localhost:3000/docs/godot/sandbox#dedicated-sandbox-nodes


Allow cross-origin access to API

I am making the LD map use your API, which will ensure that users get a consistent view of their comment status on both UIs.
However, when I try and fetch from api.php I get a COR error:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://feedback.ld.intricati.com/api.php?action=eventsummary&event=undefined. (Reason: CORS header 'Access-Control-Allow-Origin' missing).

The preferred solution is to emit the header.
An alternative solution is to support JSONP, e.g. via an optional callback parameter.
thx

(I think I can solve this by running my own caching server)

We could certainly open things up with CORS headers or JSONP support, no problem for me.
Now I've been thinking, if we're considering the long term, your map will probably outlive the FF site, so it might not be viable for LD37+ to rely on our API. It's your call though, I don't know how hard it would be to change the code one way or another.

I just added a 'Access-Control-Allow-Origin: *' header. I'm not a CORS expert but I assume it will suffice? Les live website is up to date if you want to try it.

Works a charm!  Thousand thanks :)


wscat Sends different GET Header through Proxy

I'm calling wscat against two different ports:
Simple node.js WebSocket Server:
wscat --connect ws://uri:8000
NGINX Proxy:
wscat --connect ws://uri:80
tcpdump shows the following:
The header in the GET to the node server includes:
Connection: Upgrade
Upgrade: websocket

The header in the GET to the NGINX server only has:
Connection: keep-alive

Why would this happen?

I don't know, the request is always the same: https://github.com/websockets/ws/blob/cb1c893ce94f3d800cd6e4166e6640bda24d74ab/lib/WebSocket.js#L636.

I finally figured out that my companies firewall was stripping out the Upgrade on port 80 and only port 80.  FML...
Thanks.


Work in progress: Parallel Benchmark

Namo, on all the plot labels, could you add a name that reflects:

split_rows, split_columns, split_nonzeros
static split or dynamic with grain size
output memory strategy (scratchspace, atomics, or mutex) if needed

so we would have, e.g., split_rows_static, split_columns_dynamic_50_atomicelement
i think this would help me understand the plots better

Try thread pinning to see if it improves performance on lanka. https://carstenbauer.github.io/ThreadPinning.jl/stable/examples/ex_pinning_julia_threads/

Let's also benchmark against taco and maybe mkl.


Safari: show() must be triggered by user activation.

Launching the Payment Request from via a hash change raises the following error in Safari:
SecurityError: show() must be triggered by user activation.

This currently triggered by (https://github.com/google-developer-training/pwa-ecommerce-demo/blob/master/project/app/scripts/modules/cart-view.js#L37):
this._checkoutBtn.addEventListener('click', this._goToPayment.bind(this));

and (https://github.com/google-developer-training/pwa-ecommerce-demo/blob/master/project/app/scripts/modules/cart-view.js#L78):
_goToPayment() {
    pushLocationHash('pay');
}

Here's what's happening:

Chrome sees the click and sets a flag that lets PaymentRequest::show run (which is why I was able to push the hash and let the next screen take it.)
Safari expects you to show the payment screen from the event handler.

This is why e-commerce sites have ApplePay buttons on the "cart" page rather than on "payments". The vendor-specific payment modes essentially take the place of the checkout screen.
I want to have a chat with our Payments and UX people before making any changes, but you can do this in the meantime:

Add an ApplePay button, and Google Wallet, and so on.
Change the checkout button to "Pay with credit card" and move it next to the other payment methods.
Move the PaymentRequest trigger into that checkout handler.
Add a regular link to bring up the checkout screen.

It's almost an anti-pattern setting up payment this way, but it's also what everybody seems to be doing. I'll keep you posted if we come up with a better answer.
Thanks for reporting this,
Sarah


Unable to generate libtensorflowlite_flex_jni.so

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
2.10.0
Custom code
Yes
OS platform and distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
I am working with soong build system. I have created a text based classification model and saved it as ".tflite" with select_tf_ops. Now, I am generating a ".apk" file using Android.bp only which is responsible for doing my classification task. I can push it on my target and it should classify. But I am getting below error.
--------- beginning of crash
10-23 11:33:25.970  4445  4445 E AndroidRuntime: FATAL EXCEPTION: main
10-23 11:33:25.970  4445  4445 E AndroidRuntime: Process: com.test.classifier, PID: 4445
10-23 11:33:25.970  4445  4445 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: library "libtensorflowlite_flex_jni.so" not found
10-23 11:33:25.970  4445  4445 E AndroidRuntime: 	at java.lang.Runtime.loadLibrary0(Runtime.java:1077)
10-23 11:33:25.970  4445  4445 E AndroidRuntime: 	at java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-23 11:33:25.970  4445  4445 E AndroidRuntime: 	at java.lang.System.loadLibrary(System.java:1661)
10-23 11:33:25.970  4445  4445 E AndroidRuntime: 	at org.tensorflow.lite.flex.FlexDelegate.(FlexDelegate.java:61)
10-23 11:33:25.970  4445  4445 E AndroidRuntime: 	at java.lang.Class.classForName(Native Method)
10-23 11:33:25.970  4445  4445 E AndroidRuntime: 	at java.lang.Class.forName(Class.java:454)
10-23 11:33:25.970  4445  4445 E AndroidRuntime: 	at java.lang.Class.forName(Class.java:379)
10-23 11:33:25.970  4445  4445 E AndroidRuntime: 	at org.tensorflow.lite.NativeInterpreterWrapper.maybeCreateFlexDelegate(NativeInterpreterWrapper.java:548)
10-23 11:33:25.970  4445  4445 E AndroidRuntime: 	at org.tensorflow.lite.NativeInterpreterWrapper.applyDelegates(NativeInterpreterWrapper.java:510)
10-23 11:33:25.970  4445  4445 E AndroidRuntime: 	at org.tensorflow.lite.NativeInterpreterWrapper.init(NativeInterpreterWrapper.java:88)
10-23 11:33:25.970  4445  4445 E AndroidRuntime: 	at org.tensorflow.lite.NativeInterpreterWrapper.(NativeInterpreterWrapper.java:66)
10-23 11:33:25.970  4445  4445 E AndroidRuntime: 	at org.tensorflow.lite.NativeInterpreterWrapperExperimental.(NativeInterpreterWrapperExperimental.java:44)
10-23 11:33:25.970  4445  4445 E AndroidRuntime: 	at org.tensorflow.lite.Interpreter.(Interpreter.java:228)
10-23 11:33:25.970  4445  4445 E AndroidRuntime: 	at org.tensorflow.lite.Interpreter.(Interpreter.java:212)
Standalone code to reproduce the issue
Added below code in /tensorflow/lite/java/Android.bp

 srcs: [
         ":tflite_flex_delegate_java",
         ":tflite_nnapi_delegate_java",
         "src/main/java/org/tensorflow/lite/annotations/*.java",
         "src/main/java/org/tensorflow/lite/*.java",
     ]

Used below code for saving the model:
converter = tf.lite.TFLiteConverter.from_keras_model(model)
converter.allow_custom_ops=True
converter.target_spec.supported_ops = [
  tf.lite.OpsSet.TFLITE_BUILTINS, # enable TensorFlow Lite ops.
  tf.lite.OpsSet.SELECT_TF_OPS # enable TensorFlow ops.
]

Relevant log output
No response

Hi @pkgoogle
Please look into the issue
Thank You

Hi @prerna1124, can you ensure you are following all the directions on this page? https://www.tensorflow.org/lite/android/development, specifically please be sure you have these abiFilters: https://www.tensorflow.org/lite/android/development#lite_lib, if you can share your gradle file or if possible, your entire project we can also take a look. Thanks for your help.


feat: function array_group_by

Description
A function to group data rows by values defined by indexes. The function supports the "dot syntax". Optionally it can include empty values (where empty($value) === true) and puts them under key ''.
The depth of return result equals count($indexes).
Example:
$data = [
    [
        'id'    => 1,
        'item'  => 'ball',
        'color' => 'blue',
    ],
    [
        'id'    => 2,
        'item'  => 'book',
        'color' => 'red',
    ],
    [
        'id'   => 3,
        'item' => 'bird',
        'age'  => 5,
    ],
    [
        'id'    => 4,
        'item'  => 'jeans',
        'color' => 'blue',
    ],
];

$result = array_group_by($data, ['color'], true);

Returns following result
$result = [
    'blue' => [
        [
            'id'    => 1,
            'item'  => 'ball',
            'color' => 'blue',
        ],
        [
            'id'    => 4,
            'item'  => 'jeans',
            'color' => 'blue',
        ],
    ],
    'red' => [
        [
            'id'    => 2,
            'item'  => 'book',
            'color' => 'red',
        ],
    ],
    '' => [
        [
            'id'   => 3,
            'item' => 'bird',
            'age'  => 5,
        ],
    ],
];

Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[ ] Conforms to style guide

Please fix the PHPStan error:
Error: Offset mixed on array{} in isset() does not exist.
 ------ ----------------------------------------------------
  Line   system/Helpers/array_helper.php
 ------ ----------------------------------------------------
  256    Offset mixed on array{} in isset() does not exist.
 ------ ----------------------------------------------------

https://github.com/codeigniter4/CodeIgniter4/actions/runs/4706875155/jobs/8348394968?pr=7438

------ -----------------------------------------------------------------
  Line   system/Helpers/array_helper.php
 ------ -----------------------------------------------------------------
  260    Call to function array_key_exists() with mixed and array{} will
         always evaluate to false.
 ------ -----------------------------------------------------------------

I tried different assignments, incl. string only, but i still get the same error that the function always evaluates to false. But this function call is important for the code to work. Any suggestions?

@rumpfc
Can you remove the references? It is difficult to understand.

Please run: $ composer cs-fix

@rumpfc Can you remove the references? It is difficult to understand.

The references are absolutely necessary. Each iteration of $indexes goes one level deeper into the nested $result. So $currentLevel assigns itself the reference of the subarray.

I checked the behavior. It seems you are correct, and the PHPStan error seems to be false positive.
If you cannot rewrite easily or if the rewrite code will be more complicated, I suggest you suppress the PHPStan error.

Can you add test case for dot array syntax?

Can you add test case for dot array syntax?

They are already included. See the final yield of both data providers in ArrayHelperTest.

Oh, I missed that. Thank you.

The recursive approach satisfies both rector and phpstan, but I feel like it requires more memory. TIme performance should be the same.

My quick benchmark on macOS shows recursive is slower, but the memory usage are the same.
memory usage: 114232
recursive: 0.8359
reference: 0.6689
    public function test()
    {
        $iterator = new \CodeIgniter\Debug\Iterator();

        $memory_base = memory_get_usage();

        $iterator->add('array_group_by', static function () {
            $indexes = ['gender', 'hr.department'];
            $data = [
                [
                    'id'         => 1,
                    'first_name' => 'Urbano',
                    'gender'     => null,
                    'hr'         => [
                        'country'    => 'Canada',
                        'department' => 'Engineering',
                    ],
                ],
                [
                    'id'         => 2,
                    'first_name' => 'Case',
                    'gender'     => 'Male',
                    'hr'         => [
                        'country'    => null,
                        'department' => 'Marketing',
                    ],
                ],
                [
                    'id'         => 3,
                    'first_name' => 'Emera',
                    'gender'     => 'Female',
                    'hr'         => [
                        'country'    => 'France',
                        'department' => 'Engineering',
                    ],
                ],
                [
                    'id'         => 4,
                    'first_name' => 'Richy',
                    'gender'     => null,
                    'hr'         => [
                        'country'    => null,
                        'department' => 'Sales',
                    ],
                ],
                [
                    'id'         => 5,
                    'first_name' => 'Mandy',
                    'gender'     => null,
                    'hr'         => [
                        'country'    => 'France',
                        'department' => 'Sales',
                    ],
                ],
                [
                    'id'         => 6,
                    'first_name' => 'Risa',
                    'gender'     => 'Female',
                    'hr'         => [
                        'country'    => null,
                        'department' => 'Engineering',
                    ],
                ],
                [
                    'id'         => 7,
                    'first_name' => 'Alfred',
                    'gender'     => 'Male',
                    'hr'         => [
                        'country'    => 'France',
                        'department' => 'Engineering',
                    ],
                ],
                [
                    'id'         => 8,
                    'first_name' => 'Tabby',
                    'gender'     => 'Male',
                    'hr'         => [
                        'country'    => 'France',
                        'department' => 'Marketing',
                    ],
                ],
                [
                    'id'         => 9,
                    'first_name' => 'Ario',
                    'gender'     => 'Male',
                    'hr'         => [
                        'country'    => null,
                        'department' => 'Sales',
                    ],
                ],
                [
                    'id'         => 10,
                    'first_name' => 'Somerset',
                    'gender'     => 'Male',
                    'hr'         => [
                        'country'    => 'Germany',
                        'department' => 'Marketing',
                    ],
                ],
            ];
            $actual = array_group_by($data, $indexes, true);
        });

        $htmlTable = $iterator->run(3000);

        echo memory_get_peak_usage() - $memory_base;
        echo $htmlTable; exit;
    }

My quick benchmark on macOS shows recursive is slower, but the memory usage are the same.

Win 11

@datamweb It is meaningless unless both (reference and recursive) results are compared in the same environment.

@kenjis thanks, Can you suggest a link or reference for a better understanding of this issue?

@rumpfc Please add this to the changelog to make people aware of this feature.
https://github.com/codeigniter4/CodeIgniter4/blob/4.4/user_guide_src/source/changelogs/v4.4.0.rst#helpers-and-functions

@datamweb What is this issue?
If we are talking about benchmarks, it means that they are meaningless unless we compare the results of running them in the same environment. The faster the machine, the faster the results.
What we are discussing now in this GitHub issue is whether reference or recursive code is better on
readability, performance.
For me, recursion seems to be a little slower, but it's not that different, so recursion is fine.
The PHPStan error is a bug in PHPStan; PHPStan does not seem to understand that references change values.

Thanks, but there is "Others" section.
Please move to "Helpers and Functions", and use :php:func: to link to the function page.
--- a/user_guide_src/source/changelogs/v4.4.0.rst
+++ b/user_guide_src/source/changelogs/v4.4.0.rst
@@ -87,6 +87,9 @@ Libraries
 Helpers and Functions
 =====================

+- **Array:** Added :php:func:`array_group_by()` helper function to group data
+  values together. Supports dot-notation syntax.
+
 Others
 ======

@@ -103,7 +106,6 @@ Others
 - **Request:** Added ``IncomingRequest::setValidLocales()`` method to set valid locales.
 - **Table:** Added ``Table::setSyncRowsWithHeading()`` method to synchronize row columns with headings. See :ref:`table-sync-rows-with-headings` for details.
 - **Error Handling:** Now you can use :ref:`custom-exception-handlers`.
-- **Array:** Added ``array_group_by()`` helper function to group data values together. Supports dot-notation syntax.

 Message Changes
 ***************


Added filter in equipeverycharacter to filter out heros that are not "isAlive"

Did not test, but have an issue when a hero dies in battle - they still exist in your party and I have not found a programmatic way to remove them.  This should at least prevent them from being equipped and stealing my loot.


feat(docker): change base_image to ros:humble-ros-core-jammy

Description
This PR changes base_image of the Dockerfile from ros:humble-ros-base-jammy to ros:humble-ros-core-jammy to decrease the image size.
Tests performed
https://github.com/autowarefoundation/autoware/actions/runs/9359817720
Effects on system behavior

Not applicable.
Interface changes

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@youtalk san, could you also test the autoware.universe build and test ci with an image generated with this action? If it passes, we can merge.

Due to the autoware.universe CI faiure, I first closed this PR.
https://github.com/autowarefoundation/autoware.universe/actions/runs/9376436454/job/25816364727


hey

Hey bro , thanks for wonderful work.
please add http://www.hotstar.com/ , https://einthusan.tv/ and http://www.tamilserials.tv/
and youtube if possible, it  is easy to download music and videos with you download options, thanks for it.

hotstar and eintusan have their dedicated and working addons already. So won't look into that yet.
Youtube is a Kodi official addon, so won't work on that either
Will take a look at tamilserials site

hi,
Any problem with Deccan Delight, after the update.  All files disappeared.

Hey Bro please add http://tamilrage.com
Hotstar and Einthusan addons not working. can you add the sites too please?
Thank you!


feature: uv activate

It would be really cool, if uv had an activate feature, that would make activating an environement easier:
uv activate
to activate the default ´venv´ environment or
uv activate venv2
to activate a venv with another name instead of having to write the long
source .venv/bin/activate

👋 this is a duplicate of https://github.com/astral-sh/uv/issues/1910, I'll be closing this issue in favor of that one.

👋 this is a duplicate of https://github.com/astral-sh/uv/issues/1910, I'll be closing this issue in favor of that one.

Sorry. Searched for it before posting but was apparently not good at searching.
Thanks


Comply with the did-resolution spec

There is a did-resolution spec: https://w3c-ccg.github.io/did-resolution
Main thing this would involve is that there should be a new function, dereference which should return:

DID Document
DID Resolution Metadata
DID Document Metadata

Right, thank you for raising this issue.
There is much work to be done to become conformant to that spec, even for the existing resolve method.

I guess this will be solved by #150

right.. there's some cleanup that needs to happen to support that breaking change


Upgrade to Flyway 4.0

No regression - unit tests from this change run without error

Coverage decreased (-0.05%) to 83.757% when pulling e53621e505d96c142d53dc2415d1f2782bd1c564 on klaus-sap:develop into 30a6b3186f82c0446ac3510619a7b963212b16f2 on cloudfoundry:develop.


the integration status changes to a configuration error

Hello,
after entering the data to the carelink account - the integration status changes to a configuration error. The log shows that the integration has connected to the account because you can see DEBUG (MainThread) [custom_components.carelink] Finished fetching carelink data in 26.615 seconds (success: True). I have installed HA core 2022.6.2.
Please let me know what I can do to make the integration work.

trouble resolved. update ha:)

Ah yes, I should update the readme to note that I only testen with version 2022.12.0 and later. That's when I made this integration.


[core] Add exports field and build proper ES modules

Builds "true" ES modules alongside CommonJS output.
Summary of changes

ESM build output is placed under /build/esm
CommonJS build output is placed under /build/cjs
Per-component package.json files were removed
The exports field was added to the package
The typesVersion field was added to package.json for compatibility with older tsconfig settings
Type definitions are built per target - the CJS one with module: "nodenext", the other one with module: "esnext".
Are The Types Wrong CLI is executed on CI to check if no issues with the package are introduced.

Type definitions
To verify if different methods of module resolution in TypeScript can resolve the exported types, the Are The Types Wrong (ATTW) tool was used. Its reports led to building the type definitions per build output (to avoid errors like False CJS and False ESM.
Another reported issue was the inability to resolve types under the node10 module resolution when the exports field is used. While we don't support Node 10, Typescript uses this resolution strategy by default (see https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/docs/problems/NoResolution.md#false-positive-unsupported-file-extension).
To work around this, I introduced the typesVersions field in package.json, as described in https://github.com/andrewbranch/example-subpath-exports-ts-compat/tree/main/examples/node_modules/types-versions-wildcards.
Testing
I created a repo to test the package with different bundlers and plain Node.js: https://github.com/michaldudak/base-ui-bundler-tests. There is an issue with running a Node.js app in ESM mode due to Base UI dependency on @mui/utils. The utils package does not currently conform to the ESM spec and cannot be used without a bundler this way.
As we're planning to move away from it and define our utilities locally, this won't be a problem for long.

This is built on top of https://github.com/mui/base-ui/pull/812

Superseded by #821


Asus FX506IV: Fan starts working after few seconds of turning off

If I turn off fans, after few seconds they start to continue working as usual.
It doesn't override fan control when I set it to off. Only for few seconds.
It will be very useful to force silence when I have weak load like browsing, movies etc.

The problem doesn't appears on command line version of program. Only in GUI.

there is no "turn off fans" function
when you uncheck the turn on checkbox, it disables the fan test mode, which seems to trigger a reset of the fan state, which is why it looks like the fan has been turned off for a few seconds
anyway, you should achieve what you need in latest commit using option mentioned in #3


Vendor<EMAIL_ADDRESS>

Release note:

`github.com/gardener/gardener` dependency is now updated to `v1.19.1`.

/unhold


Stable release of Go generated protos

Anyone writing a Go application that wishes to use Envoy protos will need a stable release of this repo.  In case you are not aware, proto definitions cannot be generated independently by libraries, since multiple versions of the generated code for a single message that make their way into the same binary will cause a panic at init time.  And without a stability guarantee, use of this repo as the official source of the protos is risky.  Please create a stable v1.x release of this repo ASAP.  Thank you.
Related to https://github.com/cncf/udpa/issues/42 and https://github.com/envoyproxy/go-control-plane/issues/391.
cc @htuch

@dfawley what do we need to do to make this "stable"? Is it just a release tag that is v1.0.0? I'm not sure why Go doesn't work with < v1.0.0 here, but we can probably do a v1.0.0 and iterate.
https://github.com/cncf/xds is now live and the canonical xDS-WG repo.

@dfawley what do we need to do to make this "stable"? Is it just a release tag that is v1.0.0?

Yes, exactly!

I'm not sure why Go doesn't work with < v1.0.0 here, but we can probably do a v1.0.0 and iterate.

Everything technically works fine without a v1 release.  This is purely symbolic -- releasing v1 is a signal that the APIs are stable, and that the owners will not break backward compatibility.

not sure if i follow entirely - but im wondering if a release is created should it not be the version number of the api - ie v3.x

nm - ignore me - this is xds version not envoy's api version

Exactly.  This repo can be at v1 and could eventually have envoy/xds v4-v7 protos in it as well as v3.

@markdroth @mattklein123 @lizan are you happy with cutting v1 from this repo? If so I can push the button.

Assuming that we're really treating this just as a checkpoint tag for build-dependency purposes, I think this is fine.  Before we would do any sort of really public release, I'd want to finish renaming the protos in the udpa tree to the xds tree.  But that seems like not an issue here, so let's not block on it.

I don't have a strong opinion either, as long as per @markdroth we aren't locking ourselves into anything we can't change. If it's an arbitrary point in time for "reasons" that's fine with me.

My understanding is that tagging v1 means we are not going to make any semver incompatible changes. If we do, we would need to release as v2 (or v3, v4, etc..) which has impacts on consumers: https://blog.golang.org/v2-go-modules.
So the ask here is not just tagging it as v1, but also committing to semver backwards compatibility

If we're really committing to not making any backward-incompatible changes at this point, then I would like to see us move the protos from the udpa tree to the xds tree before tagging v1.

Technically Go wouldn't care about the protos themselves being moved, but that would affect the generated code.  If the generated code moves from its current location, you will break our users.  We currently depend upon:
github.com/cncf/udpa/go/udpa/data/orca/v1
github.com/cncf/udpa/go/udpa/type/v1

@markdroth the APIs are already subject to https://github.com/envoyproxy/envoy/blob/main/api/API_VERSIONING.md.
At the very least, https://github.com/cncf/udpa/blob/main/udpa/type/v1/typed_struct.proto can't be moved in a breaking way.
Annotations can be debated, and ORCA we can probably break as nobody is using it in production as far as anyone knows..

At minimum, it seems like we should copy the protos in the udpa tree into the xds tree and tell people to start using those, even if the ones in the udpa tree need to stick around for backward-compatibility.
It would be nice if there was a reasonable way to maybe have the ones in the udpa tree be auto-generated from the ones in the xds tree, so that we have only one copy to maintain.

While no one may be using ORCA in production, grpc-go uses the generated protos in several places.  C and Java also use ORCA, but they generate their own protos so there is less concern about breakage being caused by a (re)move.  Should we remove all our code that depends upon it?

No, we shouldn't remove the code that uses ORCA -- we are going to need that functionality.  But once we have the protos in the new locations, we should update our code to use those new locations.

We can copy them to a new location here and update our existing code to reference it.  Do we ever need to delete the old generated code (within a year or two)?  If not, I think we'll be fine with that.

(Sorry, hit the wrong button.)
Doug, if we copy them to a new location before we tag v1, and we update our current code to use v1 and use the new locations, then why would it matter if we later remove the old locations?  Or are you concerned about other users that may be using the old locations?

If someone is using an old release of gRPC-Go that references the deleted things, their build can break when those things are removed if:

we delete the whole UDPA repo, or
they reference (directly or indirectly via another dependency) the UDPA repo at a commit after we delete those files.  This can be mitigated by making generated code depend upon an updated version of gRPC when we delete them.

When you say "the UDPA repo", I assume you actually mean cncf/xds.
I don't think we should be worried about deleting the whole repo.  I don't think we're going to plan to do that, and if we were, tagging a v1 in the repo probably wouldn't help anyway. :)
Since the second case you mentioned can be mitigated, it sounds like there's no real problem here?

Since the second case you mentioned can be mitigated, it sounds like there's no real problem here?

If we do things right we should be okay for ORCA, but we will need to coordinate things carefully.  I don't think we can move the typed struct proto to xds unless it's done in a major envoy version bump, as @htuch was implying.

Yeah, we can't move at least typed struct, so we can't kill this udpa tree until the next major version bump. ORCA can move. The only discretionary thing is annotations. I think it's safe to just change them in Envoy, in particular if we maintain the same extension IDs, but my intuition is sometimes broken when it comes to the complexities around backwards breaking changes across things like proto language bindings.
Anyway, I don't feel super strongly one way or the other. @markdroth I think you get to set the plan here as long as we don't break typed struct.

Friendly ping @markdroth. What should we do before declaring 1.0? :)

Are there any blockers before releasing v1?

Here's my proposal:

In the xds directory, create a duplicate copy of everything under the udpa directory.
Everywhere in xDS where we use something from the udpa directory, change it to use the corresponding type from the xds directory instead, with whatever backward-compatibility is required.  For annotations, hopefully we can just change them directly to use the new ones without keeping the old ones.  For TypedStruct, change both Envoy and gRPC to handle both udpa.type.v1.TypedStruct and xds.type.v1.TypedStruct.  For ORCA, hopefully we can just change the code that exists in gRPC to use the new location.
In the udpa directory, remove anything that does not actually need to remain there to avoid API breakage.  For anything that does need to remain, mark it as deprecated and add very visible comments indicating that any new code should use the copy in the xds directory instead.  (Ideally, the only thing we should need to keep here is TypedStruct, but if we also wind up needing to keep the ORCA protos for some reason, we can live with that.)
Tag v1.

Thoughts...?

@markdroth sounds like a plan to me. Since we never reference TypedStruct directly, we just need to update code, I think we can break annotations for things like deprecation etc.

It occurs to me that we probably won't be able to actually completely remove udpa.type.v1.TypedStruct, since there are probably control planes already using it, and clients will need to continue to support it for a while.  I suspect that will have to stick around for a while, although we can mark it as deprecated.


'videosnap: Bad CPU type in executable' on Intel Core Duo 1.66ghz / 10.5.8

Hello. I've been using this happily on newer hardware, but I just inherited an older 2006 era Mac Mini running at 1.66ghz and on Mac OS X.5.8 (Leopard). As per the readme, this should be supported? The thing is, I get "videosnap: Bad CPU type in executable" when running videosnap -l
Any ideas?
Thank you for the awesome utility :)

Thanks for reporting, I'll take a look and why this might be and get back to you.  It is possible I had the wrong build settings selected last time I compiled.

Out of interest, what CPU are you running on that Mac, is it an Intel or PowerPC chip?
Select 'About this Mac' - from the top left apple menu, and look for the Processor details.  While I do support Leopard, VideoSnap doesn't support PowerPC based architectures.

It's a second-gen Intel chip :)

So the real problem here is that VideoSnap (right now) requires ARC (automatic reference counting).  This is available in 64 bit CPUs for OSX 10.5+ but not 32 bit, unless you have OSX 10.6+ (see the Xcode build output below)..

So this is why the currently binary is built for 64bit Architectures only (your Mac Mini Intel CPU is 32 bit).
So what i've done is create a new branch with a test release that has a universal (32/64bit) binary, but targeting 10.6+.
https://github.com/matthutchinson/videosnap/tree/cross-platform-compatible
Can you try it on your Mac Mini (with 10.5, Leopard) and see if you have any issues :question:
If you do you will probably have to update to 10.6 (Snow Leopard) for VideoSnap to work for you.
A better fix would be to fix VideoSnap to work without ARC, which unfortunately I do not have time to do right now (PR's are welcome!).

Unfortunately I get the same error on the recompiled binary on 10.5.
I've got a couple of GBs of RAM on the way from Amazon, and as soon as that gets here and I can pop it in, I'll upgrade to Snow Leopard and let you know if it works there.
I'm not much for Objective C, but I'll take a peek about the ARC maybe submit a PR, but I kinda doubt it :)
Thank you so very much for looking at this!
Cheers!

2GB of RAM installed, system upgraded to Snow Leopard, but the same error :(

Ok, a couple more things to try;
I've learned that Snow Leopard on Intel Core Duo, will boot into 32bit mode by default.
Can you run this and tell me what it gives you?
uname -m

For 64bit you'd see x86_64, and 32bit would show i386.  If you see i386 you can try the advice here to boot your mac with a 64 bit kernel.  However your mac mini may not support this.  But worth a shot.
I tried to reproduce the problem and installed 10.6.8 on a virtual machine, but since it uses a virtual CPU that matches my own hardware, everything works since its 64bit.  And I don't have any 32bit CPUs to test this out with.

Sorry for the delayed response.
My machine doesn't do 64bit, apparently :(
Thank you for putting so much effort into this, but I think my system is just too old, probably by a matter of months.

Hmm, i don't want to be beaten by this, so i'm not closing the issue just yet..  I have an idea to try another approach.  Will update here if I succeed.

  I tried building a universal binary, to include 32/64 bit but in doing so had to remove ARC which caused a bunch of issues leading to memory leak errors.
I tried an ARC bridge header but had no luck with that either. So basically I was unable to get the binary to run on my 10.6.8 OSX virtual machine (on 32bit Intel CPU).  The whole thing felt a bit like this;

I've decided to change the README to indicate that I only support 10.7+ (and hence x86_64 CPU's only)
For older machines and OSX i'd suggest you try the (very old) command line video capture tool wacaw.

I cannot properly express my gratitude for your efforts :) keep up the great work!
I did explored wacaw a bit (before I found videosnap even), and it works, but it necessitates transcoding pre-publishing, which complicates matters and seems to result in quality loss. I don't mind adding a bit of extra code house ffmpeg, but it's not the same. Videosnap is where it's at.


Sternberg task number of trials

Refactor the sternberg code to allow users to manually set the number of trials per block. Currently it is hard coded, and not even passed into the class constructor

Options should be settable in the task specific menu (https://github.com/sho-87/cognitive-battery/issues/9)

Add settings window option for block count and trial count

Sternberg block count is settable in Settings as of e1b39c14ff1581a5f27fe1189a1b470c6b475338


Reddit provider randomly fails with ?error=access_denied

I think there must be a timing issue since this is random. Any ideas where to look?
GET /account/reddit?state=j8fcm5g_BT7aO5CRx7gWBQkFr3OakrEPu7WtTCq7hFCEQX5ynW8VINsfuPZFiOvhJoX9Yj3UNtf6z-wzQ3U6mSqhd2RUWjxOTvfVxaN4wr4PmSzKolt7j_OBC_if0LdJUqkJ0TVkk4qcSMbEpLK8-Ki_9XYjeAARlHPdFASnmqEHo9R5FqqHyUCJqRAJ17vEl0tIMvg5AK1MS-W9i04__A&code=0zioxQrzVNITfmUMqVgpftGOxAE HTTP/1.1
Host: warmatch.us
Connection: keep-alive
Cache-Control: max-age=0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,/;q=0.8
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36
DNT: 1
Referer: https://ssl.reddit.com/
Accept-Encoding: gzip, deflate, sdch
Accept-Language: en-US,en;q=0.8
Cookie: ai_user=14BDF21C-9EB3-4A1E-B8D8-4F2BBD1CC546|2015-10-01T20:30:34.603Z; ARRAffinity=9cde55da3754cdedacdad8362abbb0b9ec45d456b3e242169c547ef7fc6c6159; ai_session=B252B4E8-1783-46CC-B95B-9FAB02B31D67|1446384318866|1446386528355; .AspNet.Correlation.Reddit=v9HY078XCAcxfSyhmoWLKev6gRpwVIqjBoFABjDJ5LA
HTTP/1.1 302 Found
Content-Length: 0
Location: /reddit?error=access_denied
Server: Microsoft-IIS/8.0
Set-Cookie: .AspNet.Correlation.Reddit=; path=/; expires=Thu, 01-Jan-1970 00:00:00 GMT
X-Powered-By: ASP.NET
Date: Sun, 01 Nov 2015 14:02:21 GMT

@jarrettv I would suggest running Fiddler while testing on your local machine and having a look at the traffic which in being sent between your computer and Reddit. You may get a better idea of the actual error message returned from Reddit by having a look at the responses they return.

@jerriep thanks, the data above was extracted using fiddler

If you say it is random I assume it is working most of the times, right?
In that case it may be an issue on the Reddit side. This happens from time to time, and I have experienced similar symptoms with both LinkedIn and Yahoo.
Can you try and reach out to the Reddit support team and find out whether there are any other know issues?
Also, have a look not just at the request / response you sent about, but also at some of the requests / responses preceding that one. Sometimes a clue may be hidden in there somewhere.

It seems like the first time I try it each day, it fails twice, then succeeds the third time. I'm going to add some additional logging to dig deeper. I'm also pulling the oauth code in locally so I can try debugging. Next step will be trying another provider to see if it is just a reddit problem.

Ok, I think i've narrowed down that the error occurs when requesting the token.
An error occurred while sending the request.The request was aborted: Could not create SSL/TLS secure channel.
System.Net.Http.HttpRequestException:
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (mscorlib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (mscorlib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (mscorlib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089)
at ClanLogs.Infra.Reddit.RedditAuthenticationHandler+d__7.MoveNext (ClanLogs.Web, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null)
Inner exception System.Net.WebException handled at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess:
at System.Net.HttpWebRequest.EndGetRequestStream (System, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089)
at System.Net.Http.HttpClientHandler.GetRequestStreamCallback (System.Net.Http, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a)

I've run into this issue every once and a while as well, mostly while using RedditSharp. My suspicion is that it's a server timeout/issue on Reddit's end that doesn't end gracefully and winds up being an error about establishing a connection to the server. At least that's what my gut says, I haven't been able to confirm it yet or reliably reproduce it

I've had a similar issues with oauth on twitter using tweetsharp. What fixed it for us was adding
ServicePointManager.Expect100Continue = true;

inside our application_start

Ok, I ended up building in retries and that fixed the problem. What a hack! Oh well. One day I'll get to the bottom of it.
Example retry code in RedditAuthenticationHandler
// keep trying to request token because some issue causes to not succeed until 3rd time
string token = null;
int retries = 0;
while (token == null && retries < 4)
{
tc.TrackTrace("5.Try requesting the token-" + retries);
try
{
var request = new HttpRequestMessage(HttpMethod.Post, TokenEndpoint);
request.Headers.Add("User-Agent", Options.UserAgent);
request.Content = new FormUrlEncodedContent(body);
                    var req = await httpClient.SendAsync(request);
                    if (req.IsSuccessStatusCode)
                    {
                        token = await req.Content.ReadAsStringAsync();
                        tc.TrackTrace("6.Request the token success");
                        break;
                    }
                }
                catch(Exception ex)
                {
                    tc.TrackException(ex);
                }
                await Task.Delay(400);
                retries++;
            }


Add shebang at top of burrito script

In order to ensure that this script is runnable when a user's shell is
not bash, this commit adds a shebang at the top of the script. It uses
whatever bash it can find in a user's path to avoid hard coding a path
to bash.

:+1: Thanks!


RN 0.57.5: cancel all subscriptions and asynchronous tasks in %s.%s', 'the componentWillUnmount method' in ModalBox

React Native 0.57.5
Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in %s.%s', 'the componentWillUnmount method' in ModalBox

same for me


Profunations

We blogger stut serfing from links dont secure of platine payings on credit cards!
My blog  << https://www.mhaim1.blogspot.com >> not so inside page chimical process wever forever.
Pay Laptop CORE i3.pdf

Pay Fax Machine.pdf
Resaver from out call from Israel not absolutly pounds recalls!


Re-organise docs for user perspectives

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 68.466%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
6998

Relevant Lines:
9690

💛  - Coveralls


add public folder to gitignore file

We shouldn't be checking in generated code.

Fixed with b9af6d20feb05f1965fe073236f87b4612068391.