Filter permission issue

Trying to set up linux print server, connected to Lexmark S405 by USB.
Cannot print test page - error log lists this as issue: Permission denied on starting filter.
I [30/Jul/2019:22:16:48 +0200] [Job 18] Started filter /usr/local/lexmark/v3/bin/printfilter (PID 15377)
I [30/Jul/2019:22:16:48 +0200] [Job 18] Started backend /usr/lib/cups/backend/dnssd (PID 15378)
D [30/Jul/2019:22:16:48 +0200] [Job 18] PID 15377 (/usr/local/lexmark/v3/bin/printfilter) stopped with status 113 (Permission denied)

Sorry if this is the wrong place to go for this.
Install details:
cups:
  Installed: 2.2.7-1ubuntu2.6

System details: uname -a
Linux legasov 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Attached here is my PPD for this printer, got it from manufacturer, extracted from their install deb package:
lxS300-S400-ppd.zip
Thank you

For me this looks like a problem of a third-party printer driver (from Lexmark).
Is the executable bit of the file
/usr/local/lexmark/v3/bin/printfilter

set?
I do not see any problem in the cups-filters package here.

Sorry, i didn't know where else to look for help - been trying the docs
extensively.
Yes, permissions seem to be set according to docs (no group write, owner
and group execute).
Could you point me in the right direction?
Thanks Till
On Wed, 31 Jul 2019 at 15:55, Till Kamppeter<EMAIL_ADDRESS>wrote:

Closed #137 https://github.com/OpenPrinting/cups-filters/issues/137.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OpenPrinting/cups-filters/issues/137?email_source=notifications&email_token=ADACLHMTBBQPY4NZSAP3J5TQCGKTPA5CNFSM4IIAA732YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSZTHZ6A#event-2523299064,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADACLHO2BMBBJATI7XGTHY3QCGKTPANCNFSM4IIAA73Q
.

--
Duncan Cosser - (+27)848009957

I don't know if @lumotroph ever found their answer, but I will leave this here for posterity's sake:
First make sure that  /usr/local/lexmark/v3/bin/printfilter has the correct permissions, user, and group:
sudo chmod 755 /usr/local/lexmark/v3/bin/printfilter
sudo chown root:bin /usr/local/lexmark/v3/bin/printfilter

Then (and this was the most cryptic part of the whole process) you need to add apparmor exceptions. If you take a look at dmesg you'll see something like:
[  358.513178] audit: type=1400 audit(1588983225.678:22): apparmor="DENIED" operation="exec" profile="/usr/sbin/cupsd" name="/usr/local/lexmark/v3/bin/printfilter" pid=4087 comm="cups-exec" requested_mask="x" denied_mask="x" fsuid=7 ouid=0
[  359.162327] audit: type=1400 audit(1588983226.326:23): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=3854 comm="cupsd" capability=12  capname="net_admin"
[  362.744441] audit: type=1400 audit(1588983229.910:24): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=3854 comm="cupsd" capability=12  capname="net_admin"
[  362.745297] audit: type=1400 audit(1588983229.910:25): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=3854 comm="cupsd" capability=12  capname="net_admin"
[  362.747397] audit: type=1400 audit(1588983229.914:26): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=3854 comm="cupsd" capability=12  capname="net_admin"
[  519.206652] audit: type=1400 audit(1588983386.373:27): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=4427 comm="apparmor_parser"
[  519.207028] audit: type=1400 audit(1588983386.373:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=4427 comm="apparmor_parser"
[  519.227903] audit: type=1400 audit(1588983386.397:29): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=4427 comm="apparmor_parser"
[  549.055658] audit: type=1400 audit(1588983416.226:30): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=4512 comm="cupsd" capability=12  capname="net_admin"

To get around this you need to add the following snipets to /etc/etc/apparmor.d/usr.sbin.cupsd:

Find the capabilities section and add capability net_admin, Pick a spot in the middle of the list (yes the comma is needed)
Find a section that starts off like:

# FIXME: no policy ATM for hplip and Brother drivers
  /usr/bin/hpijs Cx -> third_party,
  /usr/Brother/** Cx -> third_party,

right below that add:
  /usr/local/lexmark/** Cx -> third_party,
Again, the comma is required. Then load the new rules and restart cups:
sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.cupsd
sudo /etc/init.d/cups restart

Much thanks to the following links:
https://ubuntu.pl/forum/viewtopic.php?t=182694
https://askubuntu.com/questions/645636/apparmor-with-cupsd-denied-in-logs
https://wiki.ubuntu.com/DebuggingPrintingProblems#AppArmor_Protection_of_the_printing_system

Fantastic, Irvega, thank you so much for taking the time to share this.
On Sat, 09 May 2020 at 03:00, lrvega<EMAIL_ADDRESS>wrote:

I don't know if @lumotroph https://github.com/lumotroph ever found
their answer, but I will leave this here for posterity's sake:
First make sure that /usr/local/lexmark/v3/bin/printfilter has the
correct permissions, user, and group:
sudo chmod 755 /usr/local/lexmark/v3/bin/printfilter
sudo chown root:bin /usr/local/lexmark/v3/bin/printfilter
Then (and this was the most cryptic part of the whole process) you need to
add apparmor exceptions. If you take a look at dmesg you'll see something
like:
[  358.513178] audit: type=1400 audit(1588983225.678:22): apparmor="DENIED" operation="exec" profile="/usr/sbin/cupsd" name="/usr/local/lexmark/v3/bin/printfilter" pid=4087 comm="cups-exec" requested_mask="x" denied_mask="x" fsuid=7 ouid=0
[  359.162327] audit: type=1400 audit(1588983226.326:23): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=3854 comm="cupsd" capability=12  capname="net_admin"
[  362.744441] audit: type=1400 audit(1588983229.910:24): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=3854 comm="cupsd" capability=12  capname="net_admin"
[  362.745297] audit: type=1400 audit(1588983229.910:25): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=3854 comm="cupsd" capability=12  capname="net_admin"
[  362.747397] audit: type=1400 audit(1588983229.914:26): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=3854 comm="cupsd" capability=12  capname="net_admin"
[  519.206652] audit: type=1400 audit(1588983386.373:27): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=4427 comm="apparmor_parser"
[  519.207028] audit: type=1400 audit(1588983386.373:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=4427 comm="apparmor_parser"
[  519.227903] audit: type=1400 audit(1588983386.397:29): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=4427 comm="apparmor_parser"
[  549.055658] audit: type=1400 audit(1588983416.226:30): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=4512 comm="cupsd" capability=12  capname="net_admin"
To get around this you need to add the following snipets to
/etc/etc/apparmor.d/usr.sbin.cupsd:

Find the capabilities section and add capability net_admin, Pick a
spot in the middle of the list (yes the comma is needed)
Find a section that starts off like:

FIXME: no policy ATM for hplip and Brother drivers
/usr/bin/hpijs Cx -> third_party,
/usr/Brother/** Cx -> third_party,
right below that add:
/usr/local/lexmark/** Cx -> third_party,
Again, the comma is required. Then load the new rules and restart cups:
sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.cupsd
sudo /etc/init.d/cups restart
Much thanks to the following links:
https://ubuntu.pl/forum/viewtopic.php?t=182694
https://askubuntu.com/questions/645636/apparmor-with-cupsd-denied-in-logs
https://wiki.ubuntu.com/DebuggingPrintingProblems#AppArmor_Protection_of_the_printing_system
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OpenPrinting/cups-filters/issues/137#issuecomment-626079426,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADACLHPUSNHDAMFGFWMGTQTRQSTKNANCNFSM4IIAA73Q
.

--
Duncan Cosser - (+27)848009957


GLTF format is not formed after exporting CityGML file

Hello I am Fadel.
I am currently trying to visualize a dataset of shape file multipatch into Cesium using 3D web client.
I exported the shp multipatch to CityGML using fme. It was successfull.
After that I exported the GML into KML/GLTF using BBox option and with the tiling option was clicked. It was succesfull.
However when I try to call the data in the web browser, It only shows a blue line of border (which was Bbox) with no 3d model loaded in the box. I have tried to zoom in but I still found no model.

Then I checked the Console in the browser, There are warnings telling that this kind of ID model with .GLTF format is not found.
I checked the root directory and trace the ID. I found that the file with such ID only in .DAE format.
I tried to search any file with GLTF format in the TILES directory. I found none.
Please help me to resolve this issue.
Thank you.

Are you sure you checked the option "Create glTF model" on "Preferences -> KML/COLLADA/glTF Export -> General"?

Yeah I didnt check it. I just checked it and It is succesfull. Thank You 😃


Add finding destination MAC by IP in traceflow

Find the destination MAC in traceflow controller by destination IP via local cache.
Solved a TODO in traceflow. Testing accepted on local machine.

/test-all


Make REPL works always (even .js code in infinite loop)

Options

Process REPL in USB (UART?) interrupt handlers
Use a separate thread (dual-core)

Use Ctrl+C for break (It is policy of MicroPython)


Update default tsconfig.json options

Command
new, update
Description
It's been a while since we've looked at recent TypeScript configuration changes and refreshed the default Angular setup. We should review recent additions and changes to look for anything we want to enable in ng new as well as through ng update for existing apps.
Two options in particular which stand out:

moduleResolution: 'bundler' - This seems appropriate given our esbuild / Webpack usage.
allowSyntheticDefaultImports: true - I believe this is recommended by the TypeScript team.
esModuleInterop: true - This is highly recommended for our esbuild setup and maybe we should just make it the default.

We don't need to be specifically limited to these three options, but those are the immediate ones to consider.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response

In version 17, for new apps we now enable esModuleInterop, which also enables allowSyntheticDefaultImports.

Also, should downlevelIteration be set to false by default in year of 2023? Do we really need to to support <ES2015?

Also, should downlevelIteration be set to false by default in year of 2023? Do we really need to to support <ES2015?

Starting with Angular CLI 17.0.1 in new generated workspaces downlevelIteration is no longer set (see https://github.com/angular/angular-cli/commit/f7f62c9d6988e6801981592f56137cd02bfe2316).

Closing as this has been completed as part of version 18 where we added moduleResolution: 'bundler'


interrupting parsing leaves terminal unusable

if i cancel a long running "parsing" screen, the terminal is not reset, the cursor is invisible, arrow keys dont work anymore, typing is invisible, etc.  even doing a soft reset with ctrl-v esc c<enter> does not fix it.
would it be possible to reset the terminal after catching the ctrl-c?

Thanks for reporting this. Typing reset (even if you can't see what's being typed) should set the terminal back into its initial state, but let me take a look at this, it's probably not hitting endwin() after SIGINT.


class is not assignable to generic components (rfc436)

With "experimentalRfc436": true enabled, vue-tsc complains when adding a class to generic components, since version 1.4.4, and still with version 1.6.0. Version 1.4.3 works fine in this regard.
Please find a link to a reproduction repo and below the exact error message:
"Argument of type '{ class: string; }' is not assignable to parameter of type '{ foo?: string | undefined; } & VNodeProps'.
Object literal may only specify known properties, and 'class' does not exist in type '{ foo?: string | undefined; } & VNodeProps'."
In the reproduction repo, please see the two errors in component TheWelcome.vue (either with vscode extension or by running yarn type-check).

That was fast! ⚡


attribute the rendition of the GNU Bash icon I created for exercism.i…

…o to its original author (from exercism.io's ATTRIBUTION.md)
a step in fixing https://github.com/exercism/exercism.io/issues/3112.

Sweet, thanks so much, @catb0t!


Incorrect eta-reduction in presence of -XRankNTypes

HLint will suggest eta-reducing f a = id a to f = id.
However, in the presence of RankNTypes, eta-reduction doesn't always hold, and applying the hints can result in code that doesn't compile.
See:

https://stackoverflow.com/questions/16402942/how-can-eta-reduction-of-a-well-typed-function-result-in-a-type-error/16403298#16403298
https://stackoverflow.com/questions/19758828/eta-reduce-is-not-always-held-in-haskell

Thanks, yep, this is a known issue, but wasn't really covered in the limitations. I've added more notes, and the links from Stack Overflow: 85e8ecca189431cb4e6bb74615274579f66916a6

Eta-reduction can also be unsafe under linear types. E.g.
{-# LANGUAGE LinearTypes #-}

f :: Int %1 -> Int
f x = x

g :: (Int -> Int) -> Bool
g f = f 0 == f 1

main :: IO ()
main = print (g (\x -> f x)) -- cannot be reduced

Given how new linear types are, I think it's not quite ready to be added to the readme as an explicit limitation. Maybe once linear types are more popular it will be worth revisiting.


[qtbase] [qttools] windeployqt has been moved

In Qt 6.3, windeployqt has been moved from the qttools package into qtbase. Therefore, vcpkg's windeployqt.debug.bat no longer gets deployed, which breaks the example code given in #20101.

https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.3.0/release-note.md

indicates otherwise so that windeployqt is still in qttools. Maybe the issue is that the wrapper no longer works because the path querying has changed. (using qtpaths.exe now if I read that correctly.)

hmm ok release notes are inexact. It doesn't mention that change.

Please try #24445


Modals for CDS

Currently, I could not identify a place on chicago.gov where modal pop-up dialogs are used. The USWDS is not planning on including modals (https://github.com/uswds/uswds/issues/911).
If modals are implemented in a future version of CDS, consider the following resources on modal use and accessibility:
Is a modal right for your application? - Nielsen Norman Group
W3 modal accessibility considerations
Bootstrap modal accessibility considerations

Added 3 samples of modal in the CDS Reference page:
https://chicago.github.io/cds-reference/#modals


Add LOO capability

@goedman @dfish Mostly done, but there's a couple things --

If you guys know how to manipulate StructArrays, I'm having trouble getting the tests on lines 53+54 to run. I verified that they look good "By hand" but in the future it would be better for them to run automatically.
I definitely don't like that Loo currently returns a weirdly structured Dict. I'd much prefer some kind of table.
The Loo object needs some kind of nice-looking display method, possibly using PrettyTables.jl.
More documentation would be nice.

Also, there seems to be some kind of problem with running the tests on Github, even though they run fine locally.

I will look at the StructArray issue tomorrow. In the meantime, the error report seems to indicate that Coveralls failed to send a message. I don't know how to setup Coveralls. If Rob is not familiar, the easiest solution in the short term is to disable it.

@ParadaCarleton and @goedman
I think part of the problem with the tests is that the data structures are different between R and Julia. In addition, there seems to be  different information. This requires manually aligning data from the two sources. Here is the best I could do:
    # fails on pareto_k
    indices = [1,3,4]
    field_names = [:estimate,:p_eff,:pareto_k]
    for (i,f) in zip(indices,field_names)
         @test getproperty(jul_loo.pointwise, f) ≈ r_loo["pointwise"][:,i] rtol = .001
         @test getproperty(rel_eff_loo.pointwise, f) ≈ r_loo["pointwise"][:,i] rtol = .001
    end

    @test jul_loo.estimates["Score Est"] ≈  r_loo["estimates"][1] rtol = .001
    @test jul_loo.estimates["Parameters (Eff)"] ≈  r_loo["estimates"][2] rtol = .001
    @test rel_eff_loo.estimates["Score Est"] ≈  r_loo["estimates"][1] rtol = .001
    @test rel_eff_loo.estimates["Parameters (Eff)"] ≈  r_loo["estimates"][2] rtol = .001

The pointwise data fail on pareto_k. Those appear to be very different. :estimate and :p_eff pass. Since I am not familiar with the package and the details of LOO, I may have missed something. Please double check that I aligned the data properly.

@itsdfish @goedman I've fully added LOO capability. The answers look good on inspection; however, a couple of the tests are broken and should probably be double-checked before merge.

Hi @ParadaCarleton Thanks for all your work. I've been trying to figure out an issue in DiffEqBayes hence the silence from my side. But I'll go back to it asap. I had, probably on Monday, some trouble to compute a loo value which should be comparable to the WAIC.

I've gotten the tests to work now; the main problem is that the MCSE calculations are way off, 2 or 3 times the amount they should be, and I can't figure out what the MCSE calculations in the R package are doing at all.

Hi Carlos, do you see real advantages to have a Project.toml file (and the associated Manifest.toml) in the test directory?
I've mostly seen the specific test dependencies being included in the [extras] section of the main Project.toml but maybe my workflow is outdated. I have also several times been bitten by storing manifest.toml files in a package in the repo.
In the current format, how and where do you run the Package tests? Simply (with ParetoSmooth dev-ed):
cd(".julia/dev/ParetoSmooth")
]
activate .
instantiate
test

fails on my system with:
  [8e850ede] nghttp2_jll v1.41.0+1 `@stdlib/nghttp2_jll`
  [3f19e933] p7zip_jll v16.2.1+1 `@stdlib/p7zip_jll`
     Testing Running tests...
WARNING: Wrapping `Vararg` directly in UnionAll is deprecated (wrap the tuple instead).
ERROR: LoadError: ArgumentError: No file exists at given path: test/Example_Log_Likelihood_Array.RData

Hi Carlos, do you see real advantages to have a Project.toml file (and the associated Manifest.toml) in the test directory?
I've mostly seen the specific test dependencies being included in the [extras] section of the main Project.toml but maybe my workflow is outdated. I have also several times been bitten by storing manifest.toml files in a package in the repo.

Not sure; is there some other way to do it? It was set up automatically like this for me.

And yes, all the tests should be working apart from the MCSE test, since I haven't been able to get MCSE calculations to work.

I really like what you have done with AxisKeys.jl and the KeyedArray objects. Had to step over my aversion against AxisArrays.jl which I also found very user unfriendly.
Guess with the test stuff, I will just have to update my workflow notions. Most packages added the test dependencies to the main Project.jl. But I can see this is a good approach and I've seen something about being able to test selections of all tests.
I'll set some time aside to see if I understand what's going on with the MCSE calculation.

All tests are passing, so this looks good to go. MCSE gives somewhat different answers different from R (~ 30% RMSE), but they seem to be using a different algorithm from the one outlined in their paper; I've decided to just use the simpler algorithm in the paper for now.


Fix Issue when OE connection Disconnects on Notebook Close

Fixes #4383.
I spent a decent amount of time thinking about this problem, and came up with the following solution due to the following reasons:

We only currently connect using the ConnectionManagementService in SQL (for the purposes of IntelliSense) for all of the notebooks code, and for the Add new connection scenario in the Attach To
Any new connections from notebooks (besides Attach To [is there a way to include a purpose to simplify this code even more?]) should include the 'notebook' tag when generating the connection URI (we already do this today)
I don't want to create new connections when they aren't strictly necessary, and would much prefer pruning them instead of creating new ones

Therefore, when we're closing the notebook, we should only be disconnecting from connections that were created in the notebook, and those that were created in Attach To (since those won't be reused).

Totally agree on the tests; this is a great case to ensure that these various methods get called with the correct connections when thee notebook is closed.


Making Documentation Link work

The previous link was a 404... this is the fix.
Signed-off-by: Ken Sipe<EMAIL_ADDRESS>

Affects: <hygieia-docker-collector-version-number>.

Individual Agreement
Corporate Agreement

[x] I Have signed the CLA

 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.

CLA was signed... but just prior to PR


Supporting explicit resource management

For integration with https://github.com/tc39/proposal-explicit-resource-management it would be useful to define some explicit disposability of resources in JS using the Symbol.dispose function on the resource.
This Symbol.dispose functionality would only apply to currently valid own resources.
Disposing borrowed resources would be a noop, since the borrowed handle lifetime doesn't affect the underlying resource disposal.
For exported resources that are created within JS code itself, we would conversely need the ability to define the destructor, and we could use Symbol.dispose as that mechanism again, although this would indicate the underlying disposal that is run for JS-created resources as opposed to being the mediator of that disposal.
There are some edge cases with this kind of an integration - if you dispose of a JS resource using Symbol.dispose when that resource is JS-exported but currently owned by Wasm, then Wasm's own disposal would be a second dispose. But in a sense, the JS disposal would sit at a higher layer so that this doesn't seem like a huge gotcha to me, given that JS "owns" in the theoretical sense its own classes, since there is no concept of ownership in JS. Importantly within the Wasm-JS interactions the model remains well-defined. Alternatively we could do something fancy to avoid this like eg masking the Symbol.dispose function with a wrapper function, but we could always add that kind of support later I think.

Importantly, if Symbol.dispose is not called - the usual finalization registry disposal would still apply. That is Symbol.dispose for the imported own resources offers a way to eagerly dispose without relying on finalization. But GC finalization will still always be enabled as the fallback for all disposal.

I thought WIT didn't have a notion of destructors? Given you're writing a PR there clearly seems to be a way to figure this out. How do we know which methods to place inside symbol.dispose?

The component model defines the notion of a destructor for a component model resource. Note this is separate from the drop of a handle which doesn't necessarily call the destructor - it is only own drops that call the destructor. See eg the mention under resource.drop in https://github.com/WebAssembly/component-model/blob/main/design/mvp/Explainer.md#canonical-built-ins.

Landed in https://github.com/bytecodealliance/jco/pull/237.


Localized content/hi/zero-trust-architecture.md

Describe your changes

Localized content/hi/zero-trust-architecture.md to Hindi.

Trcking issue: #1354

Checklist before opening this PR (put x in the checkboxes)

[x] This PR does not contain plagiarism

don’t copy other people’s work unless you are quoting and contributing it to them.

[x] I have signed off on all commits

signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

review/ @Garima-Negi @anubha-v-ardhan

please review/ @anubha-v-ardhan

review/ @Garima-Negi @anubha-v-ardhan

Hi @shivam-sharma7  thank you for your PR.
I shall be reviewing in more depth tomorrow. Meanwhile can you fix the alignment of sentences? They need to be in a paragraph and not new sentence on new line. Thanx!

This PR is a duplicate; please see https://github.com/cncf/glossary/pull/1249#issuecomment-1409749859.

Hey @shivam-sharma7 as you can see that this particular topic is addressed in another PR, it will be great if you can try to take a different topic. Thanks for the PR tho!


View.LAYER_TYPE_HARDWARE cause SurfaceView becomes transparent in 5.0 devices

I faced a problem when content view with SurfaceView becomes transparent while sliding, just appear in 5.0 devices. (Samsung SM-P550 & Moto X Pro)
Finally I see a log output in logcat when issue coming:
V/SlidingMenu: changing layerType. hardware? true

This log output contains in SlidingMenu.java:
	@TargetApi(Build.VERSION_CODES.HONEYCOMB)
	public void manageLayers(float percentOpen) {
		if (Build.VERSION.SDK_INT < 11) return;

		boolean layer = percentOpen > 0.0f && percentOpen < 1.0f;
		final int layerType = layer ? View.LAYER_TYPE_HARDWARE : View.LAYER_TYPE_NONE;

		if (layerType != getContent().getLayerType()) {
			getHandler().post(new Runnable() {
				public void run() {
					Log.v(TAG, "changing layerType. hardware? " + (layerType == View.LAYER_TYPE_HARDWARE));
					getContent().setLayerType(layerType, null);
					getMenu().setLayerType(layerType, null);
					if (getSecondaryMenu() != null) {
						getSecondaryMenu().setLayerType(layerType, null);
					}
				}
			});
		}
	}

When sliding start, this code will call setLayerType(View.LAYER_TYPE_HARDWARE), and SurfaceView becomes transparent.
Why this will appear, and how to fix?

And I find a similar issue here: https://github.com/SimonVT/android-menudrawer/issues/13


VS2017 version throws an assembly version error

Everything was working great in VS2015. Then I upgraded to VS2017 and downloaded the uodated files. Now the "account/register" page is responding with the following error:
Could not load file or assembly 'System.Diagnostics.DiagnosticSource, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
According to information I can find online, it has something to do with System.Net.Http, but I have been unable to identify the root cause within accountgo.

Issue is resolved by adding nuget package System.Net.Http 4.3.1 to the accountgoweb project.


ci: make docs-check in CI takes forever sometimes.

Usually what we seen it's the liche taking ages to check links. We might want to disable this step or try something else ):

Help wanted!

E.g: https://github.com/thanos-io/thanos/pull/3059

Ok it's too annoying, I am disabling it for now ): See: https://github.com/thanos-io/thanos/issues/3060

Let's try to update it first: https://github.com/thanos-io/thanos/pull/3070


updating the submodule SAMBA

Updated SAMBA to the commit I want included in the v0.4 release.

@asemposki I tried the following:
git clone --recursive git@github.com:asemposki/bandframework.git
cd bandframework
pip install -r requirements.txt
pip install -e .
cd Tests
pytest
========================================== test session starts ==========================================
platform linux -- Python 3.10.12, pytest-7.4.2, pluggy-1.2.0
rootdir: /home/wild/oldcomp/repos/testing/bandframework/software/SAMBA
plugins: cov-5.0.0, dash-2.17.1, anyio-4.3.0
collected 15 items

test_GP_BMM.py ......                                                                             [ 40%]
test_LMM.py ......                                                                                [ 80%]
test_bivariate_BMM.py ...                                                                         [100%]

=========================================== warnings summary ============================================
../../../../../../../.local/lib/python3.10/site-packages/emcee/utils.py:23
../../../../../../../.local/lib/python3.10/site-packages/emcee/utils.py:23
  /home/wild/.local/lib/python3.10/site-packages/emcee/utils.py:23: DeprecationWarning: 'chain' is deprecated. Use 'get_chain()' instead.
    deprecation_warning(msg)

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
==================================== 15 passed, 2 warnings in 12.15s ====================================

So this seems to be working well.
Please check out the deprecation warning to consider addressing for future SAMBA development.


gradle setup

is this possible to have a gradle setup for us?

Sorry, I did not get what you mean by "gradle setup"? Can you explain in detail?

I think the problem is solved, no reply yet. I close it.

done!


fix permissions for stream_space and search_space

Not able to publish the pushed database from server #199

Looks good. Merging


HAGL & Pi Pico + ILI9341

Hi, thank you for the great job! I test version with SDL2 on my linux machine and I was impressed by the result. Now I wanted to try the Pi Pico version with a tft ILI9341 screen, I chose the cmake file : generic-ili9341-320x240.cmake, and nothing appears. I checked my wiring with a quick code in micropython and everything works. Is there a limitation due to the use of a mipi driver?

ILI9341 is a MIPI DVS chip so it is supported. I would double check the wiring. How does your MicroPython code look like?

Thank you for the feedback, my driver reference for micropython is https://github.com/rdagger/micropython-ili9341/blob/master/ili9341.py
MISO Pin not connected. And the setup
# Baud rate of 40000000 seems about the max
spi = SPI(1, baudrate=40000000, sck=Pin(10), mosi=Pin(11))
display = Display(spi, dc=Pin(8), cs=Pin(9), rst=Pin(12))
just the SPI bus a little slower .
I tried changing the speed in your driver, but without success.

Hello, yes backlight Pin is connected on Vcc. In boot screen is light and just after screen becomes blacks.
I compile in debug version to to view debug info
[main] 251588 total heap
[main] 251588 free heap
[HAGL HAL] Initialising single buffered display.
[HAGL HAL] Initialising SPI.
[HAGL HAL] Baudrate is set to 62500000.
[HAGL HAL] clk_peri 125000000.
[HAGL HAL] clk_sys 125000000.
[main] 251588 total heap
[main] 251588 free heap
[HAGL HAL] Initialising single buffered display.
[HAGL HAL] Initialising SPI.
[HAGL HAL] Baudrate is set to 31250000.
[HAGL HAL] clk_peri 125000000.
[HAGL HAL] clk_sys 125000000.
first try with default baud rate and second at same baud like in python code.

Sounds like backlight is on and then something turns it off? I don't know how your code looks like, but you could try with:
https://github.com/tuupola/pico_effects
You probably can just use the generic ILI9341 config, again assuming that the pins are correct.
https://github.com/tuupola/pico_effects/blob/master/CMakeLists.txt#L66
Also if you have 320x240 screen change PIXEL_SIZE to 2 or you will run out of memory. You could actually try this with your own test program too. Maybe you are running out of memory.
https://github.com/tuupola/pico_effects/blob/master/CMakeLists.txt#L52

Great!! I succeeded in getting your demo to work!
There's nothing like a grey, damp Sunday to spend some time coding and debugging.
You were right, I've rewired everything and it works.
Thanks again for your support and for taking the time to reply.

oups just I also had to set PIXEL_SIZE to 2 for it to work, as you asked me to do

Great :)


Attempting to call onMovePiece callback even when it isn't defined

In chessdiagram.js, the introduction 'allowMoves' was a good idea.
However, there should be an additional safeguard against the case where allowMoves is true, but onMovePiece is undefined.
I propose the following change to Chessdiagram.js, line 64:
_onMovePiece(pieceType, from, to) {
	if (this.props.allowMoves && this.props.onMovePiece) {
		this.props.onMovePiece(pieceType, from, to);
	}
}

fixed in f4e480c2617658e353c162f1cb8e67a0ffa98a14


Added code for  Sum of Root To Leaf Binary Numbers

Have you read the Contributing Guidelines on Pull Requests?
YES
Description
Sum of Root To Leaf Binary Numbers
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#6439

Made Changes Pls check


python310Packages.aioesphomeapi: 13.1.0 -> 13.2.0

Diff: https://github.com/esphome/aioesphomeapi/compare/refs/tags/v13.1.0...v13.2.0
Changelog: https://github.com/esphome/aioesphomeapi/releases/tag/v13.2.0
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 215899 run on x86_64-linux 1

31 packages built:

esphome
home-assistant-component-tests.airthings_ble
home-assistant-component-tests.aranet
home-assistant-component-tests.bluemaestro
home-assistant-component-tests.bluetooth_adapters
home-assistant-component-tests.bluetooth_le_tracker
home-assistant-component-tests.bthome
home-assistant-component-tests.esphome
home-assistant-component-tests.fjaraskupan
home-assistant-component-tests.govee_ble
home-assistant-component-tests.homekit_controller
home-assistant-component-tests.ibeacon
home-assistant-component-tests.inkbird
home-assistant-component-tests.kegtron
home-assistant-component-tests.keymitt_ble
home-assistant-component-tests.led_ble
home-assistant-component-tests.moat
home-assistant-component-tests.oralb
home-assistant-component-tests.qingping
home-assistant-component-tests.ruuvitag_ble
home-assistant-component-tests.sensorpro
home-assistant-component-tests.sensorpush
home-assistant-component-tests.snooz
home-assistant-component-tests.switchbot
home-assistant-component-tests.thermobeacon
home-assistant-component-tests.thermopro
home-assistant-component-tests.tilt_ble
home-assistant-component-tests.xiaomi_ble
home-assistant-component-tests.yalexs_ble
python310Packages.aioesphomeapi
python311Packages.aioesphomeapi


Remove unused define

Should have been removed in #40

Sharp eye. Please merge!

@fredj, do you really mean #40?

@elemoine sorry, it was https://github.com/camptocamp/ol3/pull/40


processing multiple Build Reports

The dbb-ucd-packaging.groovy script now has additional functionality to process multiple build reports into a single shiplist.

Closing this PR, while we merged our work via #114


Crashing Issue when extending from unexisting template

Issue
Torchbear crashes without giving a proper error message when it extends from a template that doesn't exist.
example in the linked repository
https://github.com/LuisReyes98/found-patterns-theme/tree/crashing_error_in_templeate_searching

Our updated plan:

Make the Include FrameType a condensed clone of the including template's frame stack
Make a fuction that creates an Include FrameType given an existing FrameStack
Start the included template's processor with an Origin Frame and an Include frame on top it

This makes include more powerful than the current one, more secure and less bug-prone than sharing the frame stack, but with a linear performance cost, so developer's will need to use it carefully.
this potentially has value https://github.com/Keats/tera/pull/321


Apply rename template to multiples

You might have a bunch of vacation requests for the same day, or a bunch of PR reports for the same day, but that day isn't the day that's reflected in the file.  Shift-select to apply?  Set a new replacement for those?


Run Language model on the entire dataset.

Currently the LM is being pretrained on a subset of the training data (5% I think). There are two bottlenecks:

Creating the masked data before pretraining (requires CPU only). The Fat Rome node is good for this. Also I can do chunking to ensure we create masked data for the entire dataset.
Loading the masked data and training using gpus.
- the gpu only gets one batch at a time. so gpus are fine.
- loading the entire data may not be feasible. we may need to use something like DASK library or see how chunking can work without significantly effecting efficiency due to huge I/O time

We have devised a somewhat different strategy involving a customIterableDataset where we use a generator to yield data from the disk and use HDF5 file for efficiency. More details in  #24
The customIterableDataset is working as expected, but the pipeline exhausts all memory on 480 GB GCN due to parallel processing and the process gets killed. I need to do some trial-and-error on Snellius to figure out the right balance between memory and time efficiency (i.e., # of processes and the chunk_size to run in parallel)

closing; the parallel processing for the pipeline is in #37 .


Redo medium.com/Qiskit banner image

What is the expected behavior?
At present, the medium.com/qiskit blog's banner image doesn't align with the rest of the Qiskit imagery, such as the imagery that appears on the QIskit website. I'd appreciate if some artists (Russell? Maybe we do a contest?) can give it a facelift.

Moving to Qiskit/Qiskit.org as per russell's request


fixing question 61 correct answer

Description:
Question 61 was missing a correct answer and this PR change holds adding the correct options.

@jakeherp
you are right, I checked at the chrome and it is like you said but FYI for node, it is not giving the same result


Incorrect pom.xml file. Issue with bamboo

Hello!
We are seeing a problem with our bamboo instances.
On each of them, we had a problem with hanging agents in the status 'idle' and 'pending'. Atlassian support has indicated that there is a problem with the atlassian-spring-scanner-annotation and the user-installed plugin. How the plugin-reason was indicated by Allure
Below is the Atlassian support response:
I have checked the code of these 2 Allure plugins as well and found the configuration related to the dependency atlassian-spring-scanner-annotation is configured as compile instead of provided. Please see the below for the same:
Allure-ee-bamboo :
<?xml version="1.0" encoding="UTF-8"?>

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">

    <modelVersion>4.0.0</modelVersion>
    <groupId>io.qameta.allure</groupId>
    <artifactId>allure-ee-bamboo</artifactId>
    <version>4.0.0</version>

    <organization>
        <name>Qameta Software</name>
        <url>https://github.com/qameta</url>
    </organization>

    <name>Allure EE for Bamboo</name>
    <description>This is the Allure EE plugin for Atlassian Bamboo.</description>
    <packaging>atlassian-plugin</packaging>
...
<dependency>
            <groupId>com.atlassian.plugin</groupId>
            <artifactId>atlassian-spring-scanner-annotation</artifactId>
            <version>${atlassian.spring.scanner.version}</version>
            <scope>compile</scope>
        </dependency>

Allure for Bamboo :
<?xml version="1.0" encoding="UTF-8"?>

<!--suppress VulnerableLibrariesLocal -->
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>io.qameta.allure</groupId>
    <artifactId>allure-bamboo</artifactId>
    <version>1.15.0</version>
    <name>Allure for Bamboo</name>
    <description>Allure reports right in deployment plans in Bamboo</description>
    <packaging>atlassian-plugin</packaging>
    <organization>
        <name>Allure Framework</name>
        <url>https://github.com/allure-framework</url>
    </organization>
....
 <dependency>
            <groupId>com.atlassian.plugin</groupId>
            <artifactId>atlassian-spring-scanner-annotation</artifactId>
            <version>${atlassian.spring.scanner.version}</version>
            <scope>compile</scope>
        </dependency>

The files above are the file pom.xml from jar file available on Atlassian marketplace.
Could you please help us with the  configuration for these plugins and fix it ?
Thanks!

So far the scope for atlassian-spring-scanner-annotation has always been set to compile even during the latest changes.
Just some more analysis into the pom.xml changes for versions around 1.15
The major rework in "Allure for Bamboo" 1.15 changed the atlassian.spring.scanner.version from 1.2.13 to 2.1.7
This change in atlassian.spring.scanner.version was also reverted back to 1.2.13 in version 1.16 wieder reverted.
A similar issue described in #288 mentioned that a downgrade to version 1.14 helped if you cannot upgrade or test newer version like 1.16.x

Try to use 1.19.1 version (without S.S)


subs-manager continuous improvements

any reasons ?

there are lot of meteor app used subs-manager, but a lot of open issues with it.
maybe we should stop using subs-manager , or try to improve current version together?


KOGITO-7842 - Provide WorkItemConfig without need for codegen

(tests) - kogito-apps job #857 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.downstream.kogito-apps/857/display/redirect
Test results:

PASSED: 1936
FAILED: 4

Those are the test failures:

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

(tests) - kogito-runtimes job #727 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.kogito-runtimes/727/display/redirect
See console log:

Console Logs
[2022-08-24T03:11:35.321Z] du: cannot access<EMAIL_ADDRESS>No such file or directory[2022-08-24T03:11:35.321Z] du: cannot access<EMAIL_ADDRESS>No such file or directory[2022-08-24T03:11:35.321Z] du: cannot access<EMAIL_ADDRESS>No such file or directory[2022-08-24T03:11:35.321Z] du: cannot access<EMAIL_ADDRESS>No such file or directory[2022-08-24T03:11:35.321Z] du: cannot access<EMAIL_ADDRESS>No such file or directory[2022-08-24T03:11:35.321Z] 1.8G	/home/jenkins/workspace[2022-08-24T03:11:35.321Z] 0	/home/jenkins/.pki[2022-08-24T03:11:35.321Z] 137M	/home/jenkins/tools[2022-08-24T03:11:35.321Z] 0	/home/jenkins/caches[2022-08-24T03:11:36.058Z] 644M	/home/jenkins/.npm[2022-08-24T03:11:36.058Z] 0	/home/jenkins/.yarn[2022-08-24T03:11:36.058Z] 40K	/home/jenkins/.java[2022-08-24T03:11:36.058Z] 34M	/home/jenkins/.jenkins[2022-08-24T03:11:36.058Z] 5.6G	/home/jenkins[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Install build-chain tool)Stage "Install build-chain tool" skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Build projects)Stage "Build projects" skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Sonar analysis)Stage "Sonar analysis" skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (check space after build)Stage "check space after build" skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh[2022-08-24T03:11:37.168Z] + wget --no-check-certificate -qO - https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.kogito-runtimes/727/api/json[Pipeline] readJSON[Pipeline] sh

(tests) - kogito-apps job #861 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.downstream.kogito-apps/861/display/redirect
Test results:

PASSED: 1939
FAILED: 4

Those are the test failures:

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

Jenkins rerun kogito-apps tests

Jenkins rerun kogito-runtimes tests

(tests) - kogito-apps job #862 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.downstream.kogito-apps/862/display/redirect
Test results:

PASSED: 1939
FAILED: 4

Those are the test failures:

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

(tests) - kogito-apps job #863 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.downstream.kogito-apps/863/display/redirect
Test results:

PASSED: 1939
FAILED: 4

Those are the test failures:

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

@fjtirado done, thanks

(tests) - kogito-apps job #866 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.downstream.kogito-apps/866/display/redirect
Test results:

PASSED: 1939
FAILED: 4

Those are the test failures:

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.

Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteBoundaryTimersOnTask
java.lang.AssertionError: 1 expectation failed.Expected status code <201> but was <500>.


[WFCORE-4686] Add a profile to add the log manager to the boot class path and add set the log manager for Eclipse OpenJ9.

https://issues.jboss.org/browse/WFCORE-4686
Also ignore the standalone script tests that check for GC logging. This could be a separate PR if desired.

OpenJ9 builds is https://ci.wildfly.org/viewLog.html?buildId=169985&

Core - Full Integration Build 9090 outcome was FAILURE using a merge of dcd30672fc7a3eb064ca69201ff85c08546da814
Summary: Tests failed: 1 (1 new), passed: 5486, ignored: 101 Build time: 02:41:55
Failed tests
org.jboss.as.test.clustering.cluster.web.persistence.CoarseDatabasePersistenceWebFailoverTestCase.test: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:69)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:58)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:52)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.establishTopology(AbstractWebFailoverTestCase.java:389)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:104)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:96)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.test(AbstractWebFailoverTestCase.java:87)
------- Stdout: -------
 [0m12:08:39,132 INFO  [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
 [0m [0m12:08:39,394 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
 [0m [0m12:08:39,404 INFO  [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
 [0m [0m12:08:39,520 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 18.0.0.Final-SNAPSHOT (WildFly Core 11.0.0.Beta1-SNAPSHOT) starting
 [0m [0m12:08:40,897 INFO  [org.wildfly.security] (ServerService Thread Pool -- 30) ELY00001: WildFly Elytron version 1.10.3.Final
 [0m [0m12:08:41,661 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m12:08:41,700 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 42) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m12:08:41,815 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 [0m [0m12:08:41,841 INFO  [org.xnio] (MSC service thread 1-7) XNIO version 3.7.3.Final
 [0m [0m12:08:41,847 INFO  [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.7.3.Final
 [0m [0m12:08:41,921 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 58) WFLYCLINF0001: Activating Infinispan subsystem.
 [0m [0m12:08:41,923 INFO  [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 5.0.15.Final
 [0m [0m12:08:41,950 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 49) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
 [0m [0m12:08:41,976 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 63) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 4.1.4
 [0m [0m12:08:41,951 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 66) WFLYJSF0007: Activated the following JSF Implementations: [main]
 [0m [0m12:08:41,986 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 57) WFLYIIOP0001: Activating IIOP Subsystem
 [0m [0m12:08:41,990 INFO  [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 73) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
 [0m [0m12:08:41,991 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 60) WFLYRS0016: RESTEasy version 3.9.0.Final
 [0m [0m12:08:42,000 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 59) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
 [0m [0m12:08:42,006 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
 [0m [0m12:08:42,023 INFO  [org.jboss.as.connector] (MSC service thread 1-3) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.17.Final)
 [0m [0m12:08:42,036 INFO  [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 70) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
 [0m [0m12:08:42,041 INFO  [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 71) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
 [0m [0m12:08:42,060 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 86) WFLYWS0002: Activating WebServices Extension
 [0m [33m12:08:42,070 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 84) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
 [0m [0m12:08:42,075 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 75) WFLYNAM0001: Activating Naming Subsystem
 [0m [0m12:08:42,120 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 81) WFLYSEC0002: Activating Security Subsystem
 [0m [0m12:08:42,145 INFO  [org.wildfly.extension.microprofile.metrics.smallrye] (ServerService Thread Pool -- 72) WFLYMETRICS0001: Activating Eclipse MicroProfile Metrics Subsystem
 [0m [0m12:08:42,153 INFO  [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=5.0.3.Final
 [0m [0m12:08:42,164 INFO  [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
 [0m [0m12:08:42,190 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
 [0m [0m12:08:42,153 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0003: Undertow 2.0.26.Final starting
 [0m [0m12:08:42,267 INFO  [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
 [0m [0m12:08:42,268 INFO  [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
 [0m [0m12:08:42,545 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 85) WFLYUT0014: Creating file handler for path '/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-3/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
 [0m [0m12:08:42,563 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0012: Started server default-server.
 [0m [0m12:08:42,567 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0018: Host default-host starting
 [0m [0m12:08:42,674 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTP listener default listening on [::1]:8280
 [0m [0m12:08:42,680 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow AJP listener ajp listening on [::1]:8209
 [0m [0m12:08:42,699 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 88) MODCLUSTER000001: Initializing mod_cluster version 1.4.1.Final
 [0m [0m12:08:42,734 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 88) MODCLUSTER000032: Listening to proxy advertisements on /<IP_ADDRESS>:23364
 [0m [0m12:08:42,791 INFO  [org.jboss.as.patching] (MSC service thread 1-2) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none

I'm gonna close this in favor of a new PR coming up which contains more fixes for Eclipse OpenJ9.


Contributor instructions

Per the JOSS standard, there should be some community guidelines regarding contribution, reporting issues, etc. The examples in the package are great, but I didn't find either a CONTRIBUTING.md or a doc page akin to this giving such instructions.
@DavidLapous Could you add one of the above to the repo, or show me where one already exists? It would help potential contributors immensely!
6773

There is a small section already at the end of the readme, and I've added templates for issues / feature requests in the commits 0e4878461ae0286efea39aa0f6e6325f9e8c61c7 and 2d7287612a494eb0ebfb922c1803a48187089d73.
You can check that by trying to open an issue. I'll add a contributing page in the documentation for the next release.

I've added a contributions page in the doc here. I still need to do a release to ensure that doc<->library are coherent, but this point should be fixed.

Thanks @DavidLapous! Looks good


Fix the issue with the quote character in a category name

If a category has a double quote character (") in the name it's impossible to see any products in this category or it's ascenders because the query to solr brokes.

Doesn't it need proper escaping for all special characters in this case?

@sasha0 you are 100% right. I changed it to the function that espaces all the special characters. thanks for pointing out.

Np. Thanks for the contribution.


[Overwatch] Lighting does not work on all heroes (beta v0.6.0b) L G810

There are 3 heroes that don't work with lighting. How would I be able to assist in creating them or making new lighting profiles for these missing heroes?
I also have a few heroes I would like to change the colors while I am at it. Like Soldier 76, the colors are too dark and maybe could opt for making red white and blue, or something of that nature.
I'm new to GitHub and don't fully grasp this site just yet. But would love to help any way I can.

Also, I'm new to GitHub and don't fully grasp this site just yet.


Update service throws error when offline

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.78.1
OS Version: macOS 13.2.1

Steps to Reproduce:

open VSCode(not the latest version so it can receive and try to download newer version)
close you mac(physically) to make it offline

You'll receive this error (just like this issue happened before: #61467):

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.78.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

You can't reproduce this error if using the latest version!!

This bug has been fixed in the latest release of VS Code Insiders!
@Saafo, you can help us out by commenting /verified if things are now working as expected.
If things still don't seem right, please ensure you're on version b9a77b3c7b43f229a430b28070250d55e5d14858 of Insiders (today's or later - you can use Help: About in the command palette to check), and leave a comment letting us know what isn't working as expected.
Happy Coding!

verified via code review

@joaomoreno  for snap this might still be an issue https://github.com/microsoft/vscode/blob/ce729a5a1a70d3a24fb8d7cba0232595b16b9a66/src/vs/platform/update/electron-main/updateService.snap.ts#L177


is this support azote ?

mainly x11 based system use feh as their background reserved,
may some unit on top of wayland already familiar with azote/oguri, is it supported by azote too ?

Hi. I'm not familiar with wayland (and so azote/oguri), do they have some command line tool to set wallpaper?


Incorrect metrics for ragged tensor as output

System information

OS Platform: Windows 10
TensorFlow installed from pip, version 2.5.0
Python version: 3.8

Describe the current behavior
The metrics for the ragged tensors are calculating incorrectly.
Standalone code to reproduce the issue
The model:
class dummy(tf.keras.Model):
    def __init__(self):
        super(dummy, self).__init__()

    def call(self, inputs):
        lens = tf.map_fn(lambda x: len(x), inputs, fn_output_signature=tf.int32, name='get_lengths')
        tensored_input = inputs.to_tensor(0, shape=[None, 10])
        x = Lambda(lambda x: tf.cast(x, dtype=tf.float32))(tensored_input)
        outputs = tf.RaggedTensor.from_tensor(x, lengths=lens)
        return outputs

Running:
x_dataset = tf.data.Dataset.from_tensor_slices( tf.ragged.constant([[0,0,0,0,0],[0],[0,0,0],[0,0,0,0]]))
y_dataset = tf.data.Dataset.from_tensor_slices( tf.ragged.constant([[1,1,1,1,1],[1],[1,1,1],[1,1,1,1]]))
tensor_dataset = tf.data.Dataset.zip((x_dataset, y_dataset))
# Create batches
batched_ds = tensor_dataset.batch(2, drop_remainder=True)

model = dummy()
model.compile(loss='binary_crossentropy',metrics=['accuracy'])
history = model.fit(batched_ds,epochs=2)

Result (history.history) - 100% accuracy despite clear dismatches.
{'loss': [15.424947738647461, 15.424947738647461], 'accuracy': [1.0, 1.0]}

@HannaLochOlszewska In order to expedite the trouble-shooting process, please provide a code snippet to reproduce the issue reported here. Thanks!

import tensorflow as tf
from tensorflow.keras.layers import Lambda

class dummy(tf.keras.Model):
    def __init__(self):
        super(dummy, self).__init__()

    def call(self, inputs):
        lens = tf.map_fn(lambda x: len(x), inputs, fn_output_signature=tf.int32, name='get_lengths')
        tensored_input = inputs.to_tensor(0, shape=[None, 10])
        x = Lambda(lambda x: tf.cast(x, dtype=tf.float32))(tensored_input)
        outputs = tf.RaggedTensor.from_tensor(x, lengths=lens)
        return outputs

x_dataset = tf.data.Dataset.from_tensor_slices( tf.ragged.constant([[0,0,0,0,0],[0],[0,0,0],[0,0,0,0]]))
y_dataset = tf.data.Dataset.from_tensor_slices( tf.ragged.constant([[1,1,1,1,1],[1],[1,1,1],[1,1,1,1]]))
tensor_dataset = tf.data.Dataset.zip((x_dataset, y_dataset))
# Create batches
batched_ds = tensor_dataset.batch(2, drop_remainder=True)

model = dummy()
model.compile(loss='binary_crossentropy',metrics=['accuracy'])
history = model.fit(batched_ds,epochs=2)
# Accuracy should be 0 here obviously and it's not
print(history.history)

@HannaLochOlszewska Could you please take a look on the link1 , link2 and let us know if it helps ? Thank you!

Hi @sushreebarsa, the links didn't help much. But I managed to find out that
model.compile(loss='binary_crossentropy',metrics=['accuracy']) yields incorrect accuracy results, while
model.compile(loss='binary_crossentropy',metrics=[tf.keras.metrics.Accuracy()]) seems to work fine.

@HannaLochOlszewska Thank you for the update! I also tried to reproduce the same in colab using TF v2.5, please find the gist here and confirm the same .Kindly move this issue to closed status if it is resolved for you ? Thanks!

Yes, indeed, it's resolved - thanks a lot for your assistance!
For the future reference - the problem was only in the accuracy metric that was passed, not ragged tensors at all, my bad.
According to tf.keras.Model.compile() documentation:

When you pass the strings 'accuracy' or 'acc', we convert this to one of tf.keras.metrics.BinaryAccuracy, tf.keras.metrics.CategoricalAccuracy, tf.keras.metrics.SparseCategoricalAccuracy based on the loss function used and the model output shape. We do a similar conversion for the strings 'crossentropy' and 'ce' as well.

@HannaLochOlszewska Glad that it worked for you .Could you please close this issue as it is resolved ?Thank you!


Some question for “thumb2” instruction

This is amazing work!
I have some question for you after I dig into the code.

https://github.com/mar-v-in/ArtHook/blob/master/lib/src/main/java/de/larma/arthook/instrs/Thumb2.java#45. why you use "ip" register for cmp?

https://github.com/mar-v-in/ArtHook/blob/master/lib/src/main/java/de/larma/arthook/instrs/Thumb2.java#47.   You annotation “bne next”， but I decode the “0x40, (byte) 0xf0, 0x09, (byte) 0x80,”  it was mean "bne 0x09". But 0x09 wasn't an instruction. Maybe I was made a mistake, Could you explain it more detail for me.  I know this “bne” shouldn't happen, but I still confused with this code！
Thank you very much!

As questtion 2, There was a mistake,  “0x40, (byte) 0xf0, 0x09, (byte) 0x80" it was mean "bne #16", so it will jump to next "TargetJump", am I right?

Question 1: We need to store the value to compare in a register. ip ("intra-procedural scratch register") is the only register that can be destroyed between method calls. Using ip means we don't need to backup the register, which is very fortunate as we can't guarantee that we can write to stack at this position without causing a stack corruption/overflow.
Question 2: Yes, your second comment is right about this statement. "next" is probably not perfect as comment.

Thank you！


libevent and nitcorn should expect to read binary data in HTTP requests

Currently, libevent converts every byte received within a packet to a UTF8 String. And nitcorn picks up these strings (with format errors or not) to reassemble them in a larger String.
Because of this, nitcorn servers cannot receive binary data.
libevent must be updated to read bytes and forward instances of Bytes in the callbacks to the users of the library. nitcorn HTTP parser services should expect bytes and offer services to access binary data.

As discussed, ping @R4PaSs


Allow update disabled prop at runtime

fix #118

please merge this!

@waynevanson Hi Wayne, can you review/merge and publish this changes? It's simple and straightforward fix to pretty common problem.

Please merge this, I ran on this problem today and looking for fix.
@i-akhmadullin btw thank for fix!

Please merge this, I ran on this problem today and looking for fix.
@i-akhmadullin btw thank for fix!

+1 Please merge @waynevanson

@waynevanson @andresin87 Please merge this. I need this fix.

@waynevanson is not answering for a long time. I wrote @cheton ancient main maintainer but he is not enrolled now. This project looks like its abandoned. Sorry @jishidaaaaa

@waynevanson wrote me an email indicating the current mantainer is @owen-m1

@jishidaaaaa i just start taking care of this project. We need to fix some problems with CI integration for publishing packages and I will review your fix then.


Ran out of storage, now unable to delete files

Describe the bug
I ran out of storage when I downloaded files, since then I cannot start a kernel. When I tried to delete the files I downloaded, I get "Delete Failed unhandled error". Is there a way to delete files?
Desktop (please complete the following information):

Windows OS
Firefox Browser

Hello,
This issue may be similar to https://github.com/aws/studio-lab-examples/issues/35#issuecomment-1001746976
Q. How are you deleting the files? Have you also deleted files from this location - /home/studio-lab-user/.local/share/Trash/files
The default behavior of jupyter is to move the deleted files to platform trash bin. You will find the deleted files in this location /home/studio-lab-user/.local/share/Trash/files . Deleting files in this location using rm will permanently delete them.
Can you try to delete the files from this location, and see if issue persists?

I right-clicked on a folder to delete it, then I get the above mentioned error. I cannot open any kernel due to storage issue, how do you suggest I delete files?

Are you able to access the terminal (File -> New -> Terminal)? If so you can use that to delete unwanted data using rm. Try running this command  rm -rf <path_to_directory>


Composer packaging?

Looks great! Any chance of re-working your code slightly to make incorporating it into Composer-managed projects easier? (i.e. composer.json file, namespacing and PSR-0 class names)?

Haven't forgotten about this but it's still on hold as it breaks WordPress (a significant number of our users) - hopefully they'll drop PHP 5.2 support soon and we can move with the times.

Any update on this? It would be very useful to be able to use composer and namespace this


Add to-do-list project

What does this PR do?
This PR is raised to implement the following features: 👍 :

[x] Add CRUD to the project.
[x] Use local storage to store data.
[x] Mark the tasks as finished and remove them in bulk 😀

Description of the tasks completed 👇

[x] Add the HTML for the structure.
[x] Add the CSS file for the styling.
[x] Add the JavaScript file for adding interactions.
[x] Use the linter tool that analyzes my source code to flag programming errors, bugs, stylistic errors, and suspicious constructs. 💯
[x] Use Flexbox a layout tool in CSS that helps you easily position HTML elements on the page.
[x] Check the accessibility of this project which means that websites, tools, and technologies are designed and developed so that people with disabilities ♿ can use them. For more information about Web accessibility Click here☺

How should it be tested
Clone the repository
git clone https://github.com/UbdaNam/Javascript-best-practice.git

Navigate to the folder
cd Javascript-best-practice

Checkout the branch
git checkout Add-to-do-list-project

Thanks for reviewing my PR 😊

Thank you again for reviewing my code 👍


Use DefaultAWSCredentialsProviderChain for AWSCredentialsProvider

This will attempt all of the methods known by the SDK to
authenticate.
See: http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/DefaultAWSCredentialsProviderChain.html

This PR looks to fix the issue I'm encountering here: https://github.com/llibra/embulk-output-s3/issues/9
On top of that it fixes an issue benjaminws and I were hitting with this plugin with IAM authentication on EC2 instances. Before this change, we kept getting the following error message despite having no env variables setup on the EC2 instance:
Error: com.amazonaws.AmazonClientException: Unable to load AWS credentials from environment variables (AWS_ACCESS_KEY_ID (or AWS_ACCESS_KEY) and AWS_SECRET_KEY (or AWS_SECRET_ACCESS_KEY))
Looking at the code for the AmazonS3Client, you can see that a different error message occurs if no environment variable is set.
As such, it looks like the check that the plugin is performing is incorrect and preventing the IAM authentication from occurring. With the above change, everything looks to work as expected by bring driven by DefaultAWSCredentialsProviderChain's fallback logic.

Thank you for your PR, @benjaminws.
I imported your code with a bit change.
See: http://docs.aws.amazon.com/AWSSdkDocsJava/latest/DeveloperGuide/credentials.html#loading-credentials

Right on! Thanks for the quick response! This will be helpful for us.


Change axis acceleration option

I wonder if it is possible to change axis acceleration, to make the confettis fall faster/slower, or even fall in a constant velocity. I think it would be great to manipulate the acceleration, specially on y axis.
Oh, and thanks for the great lib!

Hey @GBL147852, yeah I haven't exposed that api part of the library. It should be possible to easily manipulate that if I open that part up. I'll see what I can do about it

@GBL147852 I know it has been two years so I understand situation has changed and it isn't necessary anymore, though I made some changes and was wondering if it aligns with your suggestion.
I've implemented a way to disable and set a maxAcceleration value to control the behavior and endless acceleration of the particles. Is the example in the GIF what you meant?

Yeah! That's just how I meant. Great job! \o

I didn't expect a response so soon 😄 Thanks, then I'll do some more testing and publish it in the next release 👍

This is now available in the latest release (v1.2.2)


Bech32 encoding for connect string

As a separate matter, now that we have the federation id in there taking up most of the bytes it might make sense to explore bech32 encoding of the whole string. This would get rid of json special characters and be more compact for binary data too. If bech32 is serialized in upper case it only uses 5.5 bit per character (so only an overhead of 10% for binary data compared to 100% for hex encoding+special characters forcing binary encoding).

Originally posted by @elsirion in https://github.com/fedimint/fedimint/issues/1654#issuecomment-1426882261
See also  #614

Seems like the reduction is 242 -> 229 bytes for 10 peers, but I guess you get some error-correction too.


Return null file in Android 11 FileNotFoundException

UriUtils.getPath is returning null for content URI. You may need to follow this approach https://stackoverflow.com/a/60538917/5710872

This is a solution, but it is not recommended.


Deprecate auto mode from ModelCheckpoint and EarlyStopping

What does this PR do?

Fixes #4668
Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together? Otherwise, we ask you to create a separate PR for every change.
[x] Did you make sure to update the documentation with your changes?
[x] Did you write any new necessary tests?
[x] Did you verify new and existing tests pass locally with your changes?
[x] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In in short, see following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified; Bugfixes should be including in bug-fix release milestones (m.f.X) and features should be included in (m.X.b) releases.

Did you have fun?
Make sure you had fun coding 🙃

Hello @rohitgr7! Thanks for updating this PR.

In the file tests/test_deprecated.py:

Line 116:1: E305 expected 2 blank lines after class or function definition, found 0

@rohitgr7 did you do a full text search for mode=auto across the whole project?

yes @awaelchli

@williamFalcon this needs your approval.

@williamFalcon mind review?


Fix: properly get coords

Fix #55

It's not working with page scroll position😡
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAH


Microsoft.Build.Exceptions.InvalidProjectFileException: The imported project "/usr/lib/mono/xbuild/15.0/Microsoft.Common.props" was not found.

Issue Description
This problem occurs if I install dotnet from the Ubuntu 19.04 repositories.  If I instead install from the Microsoft site, the problem does not occur.  I don't know if this is an OmniSharp issue, or an Ubuntu packaging issue.  So I'll start here, and if the issue belongs to Ubuntu, please let me know and Ill take it there.
Steps to Reproduce
Install dotnet-sdk-2.2 from the 19.04 repo.  Then install Visual Studio Code from package code_1.36.1-1562627527_amd64.
IMPORTANT: After installing Visual Studio Code, start it up, and change the setting Omnisharp: Use Global Mono to "Never".
Set up GtkSharp with "dotnet new -i "GtkSharp.Template.CSharp"
Then create a GtkSharp app with "dotnet new gtkapp", and try to run it without debugging (or just build it from the terminal.)
Expected Behavior
App should build and run.
Actual Behavior
    Failed to load project file '/data/projects/dotnet/GtkApp/GtkApp.csproj'.

/data/projects/dotnet/GtkApp/GtkApp.csproj(1,1)
Microsoft.Build.Exceptions.InvalidProjectFileException: The imported project "/usr/lib/mono/xbuild/15.0/Microsoft.Common.props" was not found. Confirm that the path in the  declaration is correct, and that the file exists on disk.  /usr/share/dotnet/sdk/2.2.301/Sdks/Microsoft.NET.Sdk/Sdk/Sdk.props
Now, in Sdk.props, I see the following line for loading Microsoft.Common.props:
<Import Project="$(MSBuildExtensionsPath)$(MSBuildToolsVersion)\Microsoft.Common.props" />`
If I change this instead to:
<Import Project="/usr/share/dotnet/sdk/2.2.301/Current/Microsoft.Common.props" />
then everything builds and runs fine.  So, something is not setting the MSBuild environment variables correctly.  I'm not familiar wtih MSBuild, so I can't figure out where those are constructed.  Notice it is picking up the correct instance of Sdk.props from /usr/share/dotnet, but then attempting to load Microsoft.Common.props from /usr/lib/mono.  But it shouldn't be doing that, since I told Code to never use Global Mono.
Logs
OmniSharp log
    Failed to load project file '/data/projects/dotnet/GtkApp/GtkApp.csproj'.

/data/projects/dotnet/GtkApp/GtkApp.csproj(1,1)
Microsoft.Build.Exceptions.InvalidProjectFileException: The imported project "/usr/lib/mono/xbuild/15.0/Microsoft.Common.props" was not found. Confirm that the path in the  declaration is correct, and that the file exists on disk.  /usr/share/dotnet/sdk/2.2.301/Sdks/Microsoft.NET.Sdk/Sdk/Sdk.props
C# log
Post the output from Output-->C# here
Nothing
Environment information
VSCode version: 1.36.1
C# Extension: 1.20.0
Mono Information
        OmniSharp using built-in mono
Dotnet Information
.NET Core SDK (reflecting any global.json):
 Version:   2.2.301
 Commit:    70d6be0814
Runtime Environment:
OS Name:     ubuntu
OS Version:  19.04
OS Platform: Linux
RID:         ubuntu.19.04-x64
Base Path:   /usr/share/dotnet/sdk/2.2.301/
Host (useful for support):
Version: 2.2.6
Commit:  7dac9b1b51
.NET Core SDKs installed:
2.2.301 [/usr/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.2.6 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.2.6 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.2.6 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

csharp
ms-vscode
1.20.0

I am also experiencing the same issues. After I use this hotfix solution for the Sdk.props file, it fixes OmniSharp for my VSCode.
I have the same environment setup as the OP.

@Vulfox
I am having the same issue. What hotfix solution you are talking about?

@ar-tour , it is written in the OP's post under the "Actual Behavior" title. It mentions changing this file /usr/share/dotnet/sdk/2.2.301/Sdks/Microsoft.NET.Sdk/Sdk/Sdk.props by replacing the interpolated path to a hardcoded path.

I am having the same issue but on NixOS, where I cannot edit Sdk.props as it is installed on a read-only file system.

I'm having the same problem with .net core projects on NixOS.
I'm using nix-shell --pure and then running code .
shell.nix
with import <nixpkgs> {};

stdenv.mkDerivation {
  name = "my-environment";

  buildInputs = [
    pkgs.dotnet-sdk
    pkgs.vscode
    pkgs.mono
    pkgs.dotnetPackages.Nuget
  ];
}

I installed the latest mono (6.0.0) and told vscode to use the global mono and this was resolved

Editing the Sdk.props file for 2.2 worked for me, but the problem returned when I switched to 3.0, and editing the Sdk.props file no longer resolves it.
OS:  Ubuntu Mate 19.04 (Disco Dingo)
Kernel: 5.0.0-29
.NET Core: 3.0.100

@jfcarr I just started up my Ubuntu Mate 19.04 VM, and installed .Net Core 3.0 SDK using the Package Manager instructions from here: https://dotnet.microsoft.com/download/dotnet-core/3.0
The workaround mentioned here is no longer needed.  With 3.0, the app built and ran for me without having to modify any of the props files.  The SDK installed to /usr/share/dotnet/sdk/3.0.100/.

@guy-rouillier I installed it the same way, but the error occurs for me.  Perhaps a carry-over of the 2.2 issue, since I had it installed previously.

I also had 2.2 installed, and still do as a matter of fact.  Have you changed the TargetFramework to netcoreapp3.0?
<TargetFramework>netcoreapp3.0</TargetFramework>

If so, the 2.2 props settings should not come into play.

I got it working.  In addition to editing Sdk.props, I also had to set this environment variable:
export MSBuildSDKsPath=/usr/share/dotnet/sdk/3.0.100/Sdks

Things start working as soon as I move /usr/lib/mono/xbuild away from there, so apparently something within OmniSharp's msbuild still looks in the global paths, even if the bundled version is being used.

I have the same issue (macOS). If anyone needs a repro, it happens on https://github.com/felixfbecker/PowerGit.

I get a very similar issue with the following error when trying to load a .net core project within a Unity C# solution on OSX:
Microsoft.Build.Exceptions.InvalidProjectFileException: The imported project "/Library/Frameworks/Mono.framework/Versions/5.16.0/lib/mono/xbuild/Current/Microsoft.Common.props" was not found. Also, tried to find "Current/Microsoft.Common.props" in the fallback search path(s) for $(MSBuildExtensionsPath) - "/Library/Frameworks/Mono.framework/External/xbuild/" . These search paths are defined in "/Users/[username]/.vscode/extensions/ms-vscode.csharp-1.21.8/.omnisharp/1.34.8/omnisharp/OmniSharp.exe.config". Confirm that the path in the <Import> declaration is correct, and that the file exists on disk in one of the search paths.  /usr/local/share/dotnet/sdk/2.2.300/Sdks/Microsoft.NET.Sdk/Sdk/Sdk.props

Installing Mono on MacOS helped me as well.

My fix, add reference error:
Re: [GitHub Developer Support] - Microsoft.Common.Props not found -FIX
....vscode\extensions\ms-dotnettools.csharp-1.21.15.omnisharp\1.34.14.msbuild\Current\Microsoft.Common.Props
copy to
...\ProgramFiles\MSBuild\Current
JR

We've made lots of updates to the C# extension since this issue was filed. Please file a new issue if you're still experiencing this with updated logs.


js arrow function -> "Could not find function "fnName" in project."

trying to peek at an JS arrow function results in the warning "Could not find function "fnName" in project."
const foo = x => x*2
foo( 10 )

peeking at the foo call generates the warning

Thanks for reporting this. The current regex to find a JavaScript function is:
function\s+REPLACE\s*(|REPLACE\s*(=|:)\sfunction\s(|REPLACE\s*([=:])?\s*(?\s*(([,\s\w])?)?\s=>
That matches something like this:
REPLACE(() => {
this.foo = foo;
}, 1000);
It does not match a const function though. I'll look into improving it to match more. Are there any other examples that do not match that you've found? Thanks again.

the problem is not that the function is a constant, the problem apears to be the parentheses that may be left out if only 1 argument is used
const canBeFound = () => {}
const canNotBeFound = x => {}

I have not found any other mismatches sofar

Thanks for the detailed clarification. I'll work on fixing those cases. Keep me updated if you find anymore. Thanks again!

I have this issue too! thanks for working on this

const canNotBeFound = x => {}

This is a single specific rule Parentheses are optional when there's only one parameter.
I reckon it'll be easier to manage this with its own regex: REPLACE\s*([=:])?\s*\w+\s*=>

const canNotBeFound = ({x,y,z}) => {}
const canNotBeFound = ( ...args ) => {}

For the others, it is tricky. There are even more combinations than that!

var f = ([a, b] = [1, 2], {x: c} = {x: a + b}) => a + b + c;

I recommend for a more loose regex that will cater to any parameter and leave it to the programmer to write correct syntax.
propose regex to replace current es6:
REPLACE\s*([=:])?\s*\(?\s*\([^\(\)]*\)\s* =>

I haven't had a chance to look at this yet, but thank you for providing assistance. I'll let you know if it works!

@jonyeezs, the proposed regex still doesn't match const REPLACE = x => {}.
I'm trying out this regex:
REPLACE\s*([=:])?\s*\(?\s*\(?[^\(\)]*\)?\s*=>
Seems to work (I made the ( and ) matchers optional with a '?'). Can anyone confirm with more examples? Here's my regex link I'm using to test: https://regex101.com/r/qLNVaD/1

I proposed two regex in my previous comment. Both regex needs to be
implemented
The first is the case for a single argument (which is what is discussed).
The second is to cater all other permutation.
Hopefully my explanation in my previous post explain why I did that.
Which one were you using to test?
On Sat., 13 May 2017, 6:07 am DFreds<EMAIL_ADDRESS>wrote:

@jonyeezs https://github.com/jonyeezs, the proposed regex still doesn't
match const REPLACE = x => {}.
I'm trying out this regex:
REPLACE\s*([=:])?\s*(?\s*(?[^()])?\s=>
Seems to work (I made the ( and ) matchers optional with a '?'). Can
anyone confirm with more examples? Here's my regex link I'm using to test:
https://regex101.com/r/qLNVaD/1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/DFreds/code-peek-atom/issues/18#issuecomment-301173460,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKXAhnJICEaIbjH-Pjw4kbJ07CRsvx2Iks5r5LvpgaJpZM4L698U
.

I see. So I think it matches fine, but the issue is having it only show that function and nothing else. Currently, Code Peek handles only showing the specific function in the panel by either relying on brackets or tabs to know when the function declaration is complete.
I'm currently going through a refactor based on a suggestion to show the entire file but start at the currently peeked function. That is being worked on in #35 and reference issue  #32.
Therefore, I'm going to put this fix on hold until the WIP branch is complete.

Sounds good to me
On Sat., 13 May 2017, 9:38 am DFreds<EMAIL_ADDRESS>wrote:

I see. So I think it matches fine, but the issue is having it only show
that function and nothing else. Currently, Code Peek handles only showing
the specific function in the panel by either relying on brackets or tabs to
know when the function declaration is complete.
I'm currently going through a refactor based on a suggestion to show the
entire file but start at the currently peeked function. That is being
worked on in #35 https://github.com/DFreds/code-peek-atom/pull/35 and
reference issue #32 https://github.com/DFreds/code-peek-atom/issues/32.

Therefore, I'm going to put this fix on hold until the WIP branch is
complete.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/DFreds/code-peek-atom/issues/18#issuecomment-301208638,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKXAhhrRIWvS0e3-Fiaz46Pz2-CiBMkJks5r5O2FgaJpZM4L698U
.


Package URl
<EMAIL_ADDRESS>CPE
cpe:2.3:a:clojure:clojure:*:*:*:*:*:*:*:*
CVE
CVE-2017-20189
ODC Integration
None
ODC Version
9.0.9
Description
CVE-2017-20189 is a vulnerability in Clojure < 1.9. (Although 2017, the CVE was recently issued.) The maven package url for these dependencies is specifically pkg:maven/org.clojure/clojure@*. However this seems to be fuzzy-matching many other org.clojure projects and even projects that are merely written in Clojure.
So far I have seen the following packageUrls match:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
This is just what I found in a largish clojure application, so this is likely not a complete list.
I used the following suppression:
<suppress>
  <packageUrl regex="true">^pkg:maven/(?!org\.clojure/clojure@).*$</packageUrl>
  <cve>CVE-2017-20189</cve>
</suppress>

This seems to be enough for it to correctly narrow down to only org.clojure/clojure and then start looking at the version. It detects clojure 1.8 jars and ignores clojure 1.9 and above.
Another possibility might be this:
<suppress>
  <packageUrl regex="true">^pkg:maven/(?!org\.clojure/clojure@).*$</packageUrl>
  <cpe>cpe:/a:clojure:clojure</cpe>
</suppress>

However I don't know for sure whether cpe:/a:clojure:clojure is meant to include any other clojure-adjacent products besides the core clojure artifact itself.

@favila could you update the Package URI to a specific example instead of many so that we get this issue ready for maintainers to review?

@favila could you update the Package URI in the description to a specific example instead of many so that we get this issue ready for maintainers to review?

I was concerned that this would create an overly narrow suppression rule like above.
Note to maintainers: please do not regard the list of affected packages above as exhaustive. Potentially hundreds of packages that are merely written in Clojure are affected by this false positive.

@jeremylong how can I help move this forward?

@antonmos @favila It's now only awaiting a FP suppression publishing workflow to be triggered using another more straight-forward FP issue

Suppressions should now be active


how to change title bar color as you posted

What terminal emulator are you using @nicreals ? Try hyper or iTerm, both allow customizing title bars.
Our demo uses hyper terminal. See Troubleshooting.md#why-doesnt-my-prompt-look-like-the-preview for more information.

@nicreals feel free to reopen if you still have questions.


Add new ZoneScopeManager for web

If you have any suggestions, thoughts, things I should be aware of when implementing the new ZoneScopeManager that will support async operations please share it, thank you.

cc @mayurkale22 @draffensperger

I think we could base this loosely on the OpenCensus Web tracer that uses Zone.js.
Also, I think the core functionality of the scope manager should bring in Zone.js as a peerDependency, and call the package something like opentelemetry-scope-zone-peer-dep. The advantage of that is that for Angular apps that bring in Zone.js already, there are no issues around version skew or problems around bringing in the Zone.js library twice.
That said, for non-Angular apps (the majority!), we could have a more convenient package opentelemetry-scope-zone that just composes opentelemetry-scope-zone-peer-dep with the Zone.js package itself. We could clearly document which package to use when based on whether your app already includes the Zone.js dependency.
We did this for OpenCensus Web, see https://github.com/census-instrumentation/opencensus-web#using-as-npm-dependency-in-existing-js-build in the second bullet point.


Exception handling broken after adding Realm to project

Goals
To add Realm to a project (using CocoaPods) without breaking unit tests.
Expected Results
Adding Realm to the project (and doing nothing more) should not change the application or unit tests.
Actual Results
After adding Realm, the following warning shows up when compiling:
ld: warning: too many personality routines for compact unwind to encode
The app behaves normally, but there is an issue with some of our unit tests, specifically the ones that assert that exceptions are thrown. They all work on 64-bit simulators, but on 32-bit simulators (iPhone 4S, iPhone 5) exception handling is broken so any exception thrown during unit testing will cause a crash.
This Apple Developer Forums thread suggests that it may be a bug in the developer tools and that rebuilding any pre-built binaries with the latest tools may resolve the issue.
Steps to Reproduce
I attempted to reproduce the issue in isolation but was unable to do so. This answer suggests that the personality routine problem occurs when the binary has too many forms of exception handling, possibly having been linked from several other pre-built binaries. See the list of other installed CocoaPods in the project below to get an idea of what else is in our app.
Code Sample
I haven't yet been able to reproduce this in isolation and I can't expose my company's proprietary codebase where it is reproducible. If I am able to reproduce it I will upload the example.
Environment
Realm 0.92.4
Xcode 6.3.1
OSX 10.10.3
Built against iOS 8.3, targeting iOS 8.1 or later
Other installed pods:

Google Analytics ~> 3.0
Mixpanel ~> 2.6
HockeyApp ~> 3.0
Masonry ~> 0.6
ReactiveCocoa ~> 2.0
CocoaLumberjack ~> 1.0
Kiwi ~> 2.0 (for unit test target)

I should also mention that we have a rather large internal c++ library linked into the app, which is likely contributing to the variety of types of exception handling. That said, prior to adding Realm, we were not getting this warning.

@ndonald2 unfortunately, this is a limitation of the way C++ exception handling is done on Itanium-like CPUs. It uses something called a compact unwind table, which has an upper bound on the number of different exception paths it can handle in a single binary. This StackOverflow question has some good answers on why this is happening, but the long story short is that, on 32-bit iOS, there's a limitation on the amount of different exception code paths the linker can handle. Your hunch is likely correct, in that it's the combination of Realm and your internal C++ library that's putting things over the limit. Unfortunately, there's not really anything we can do about this -- its an underlying platform limitation.

Thanks for the info. It's worth noting that when I build in Xcode 6.2, this issue does not manifest at all, so it seems to be related to the current dev tools release, not some intrinsic limitation.
Is the static library distributed with the Realm Cocoapods release built in 6.3 or 6.2? The internal C++ library we are using is built with 6.3, but I could also try building it with 6.2 before linking in 6.3.
The dev forum post by the Apple dev support agent suggests that this will go away in the next Xcode 6.4 beta, so I may try that as well.

@tgoyne do you know with which version of Xcode CI is building the Core releases with?

The core OS X slave is running 10.9, so it's built with some pre-6.3 version. Compiler versions being tied to OS releases is wonderful.

I just verified that building our own c++ libs with Xcode 6.2 and then building the app and linking the lib with 6.3 does resolve the issue. Hopefully Xcode 6.4 will resolve the issue so that it no longer matters, but this solves my problem in the short term.
Thanks for you help!

Scratch that. Still broken for 32-bit.

There are no issues in Xcode 6.4 beta 4. So for now I guess it's a matter of patience - chances are we won't ship the app before 6.4 is released.

I'm closing this issue as the issue isn't specific to Realm and a fix is coming in a future version of Xcode.

Could you try building with 6.3 and https://static.realm.io/downloads/temp/core-xcode-6.3-0.89.4.zip in place of the automatically downloaded copy of the core library? It should be identical other than being built with Xcode 6.3, and if that does solve the problem it's worth spending the time upgrading the CI slave.

@tgoyne Nope, same issue with that library file. It's all Xcode's fault I'm afraid.