bring role configs to inventory

!!! Please hold on testing this until the dependencies get merged.
This PR depends on the following getting merged:

https://github.com/Islandora-Devops/ansible-role-alpaca/pull/7
https://github.com/Islandora-Devops/ansible-role-crayfish/pull/28

What does this Pull Request do?
This PR make some of the variables that need to be configured for multi sever deployment explicit in the inventory.
How should this be tested?

After the dependent PRs are merged, get this PR
Vagrant up
Sanity checks

Interested parties
@Islandora-Devops/committers

FWIW i'm testing all at once by updating my requirements.yml file to point to your forks for the alpaca and crayfish roles, and then I pulled in this PR.  I'll let you know how it goes.

@Natkeeran Tested, works great.  I sliced 1.0.1 versions for the alpaca and crayfish roles.  Want to update requirements.yml to point to those and I'll merge this in?

@dannylamb
I am wondering if I could use {{ hostvars[groups['tomcat'][0]].ansible_ssh_host }} variables:
Example:
https://github.com/Natkeeran/claw-playbook/commit/c747553387798c16f383debe3eaa135345db9fa4
This works.  It will put <IP_ADDRESS>.  The only issue is that we are only using the first machine in the inventory group.  However, that is equivalent to having localhost situation right now!

@dannylamb
Web server port should be a variable as well!

@Natkeeran You want to toss those in now or should I just merge?

@dannylamb
I'll make those changes now, test it and ping you.

@dannylamb
If you can test/merge this https://github.com/Islandora-Devops/ansible-role-blazegraph/pull/8, I can the requirements as well.
I am running into the following issue:
"The upload directory fedora://2019-07 for the file field field_media_image could not be created or is not accessible. A newly uploaded file could not be saved in this directory as a consequence, and the upload was canceled."
I am not sure if this related to this PR.  Going to try without these PRs.

@Natkeeran I'll give it a shot and report back.

I tested the blazegraph role along with the others and it all looks good.  I can't replicate the issue you're running into.  I uploaded an image and a video and all the viewers work, content is indexed in fedora and blazegraph.  Looks good to me.

I merged the blazegraph role.   Update requirements.yml and I'm happy to pull this in.

Thx @Natkeeran


code show in one line

CodeView codeView = (CodeView) findViewById(R.id.code_view);
    codeView.setVerticalFadingEdgeEnabled(true);
    codeView.highlightCode("java")
            .setColorTheme(ColorTheme.SOLARIZED_LIGHT)
            .setCodeContent(getString(R.string.code));

Does your code contains line break characters?

No
Does your code contains line break characters?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Softwee/codeview-android/issues/21#issuecomment-247554110,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUFFy9_QgjIKUgtiCQk21stsnPTdCOGaks5qql0DgaJpZM4J-tCc
.

You must add them, because text parser cannot understand where he should slice content on lines.


Systems Biology Gene Sets (Evidence)

@MichaelaEBI commented on Tue Mar 06 2018
Include Systems Biology-derived gene sets in the Open Targets platform under "Pathways & Systems Biology"

[x] Map out process to include Systems Biology gene sets
[ ] Generate sample data (JSON) from IBD Key Driver Gene Set paper
[ ] Identify and curate sample papers that identify key driver genes for various diseases
[ ] Validate and process sample JSON file using pipeline code
[ ] Define changes that need to be made throughout the platform

Issue moved to opentargets/platform #167 via ZenHub


Chrome Lighthouse Screening "best practices" penalty on image size

Hello!
I guess this is not a direct issue with this package, but I wanted to discuss it anyway.
Should I worry about lighthouse giving a penalty for using optimized images? I guess it has something to do with the aspect ratio of the screen. Does not chrome adjust for that automatically?
Example 1 - Use next-optimized-image:
Category "Best practices": penalty (< 100%)
Category "Performance": 100%
> Displays images with inappropriate size
Image natural dimensions should be proportional to the display size and the
pixel ratio to maximize image clarity.

Displayed size: 624 x 416
Actual size: 800 x 533
Expected size: 1248 x 832 --> 2x ratio

Example 2 - use a regular img with only one src (img with 2500px width):
Category "Best practices": 100%
Category "Performance": penalty (< 100%)
> Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time.

Any ideas of how to deal with this? Ignore lighthouse or is there a proper solution to it? :)

Hello @marteloge
I think the problem here is that the images don't have the expected sizes.
Let's say you have a div with a maximum width of 624px and you want to display an image within it. Optimally, the image should have exactly the same size. If it is bigger (e.g. 800px), it just wastes data. Additionally, you will want to also provide a 2x ratio image for retina displays. next-optimized-images does not resize your images automatically, you would actually have to specify it yourself which sizes you need (with the ?sizes query param) and specify different versions in the srcset attribute or a  tag.
But I'm currently working on the next major version of this plugin which is a complete rewrite and introduces many new features (currently available at the canary tag). One of those new features, the provided Img component, would solve your problem very easily. You can simply specify the sizes and densities you want and the plugin will generate everything for you (including fallbacks etc):
<Img src={MyImage} sizes={[624]} densities={[1, 2]} />

You could also add the webp prop to provide the image in WebP if the browser supports it or with the breakpoints attribute, you can provide different image sizes for desktop & mobile users.
So if you want, feel free to check out the canary version. It should already be quite stable, just a few features are missing before I'll publish it to the non-canary tag.

@cyrilwanner Thanks! Really appreciate your answer :)
I am using canary - always nice to test out the newest and to be able to help out testing. A great feature with densities! I am using a full-screen image and the size of the double density image is quite bigger so lighthouse starts complaining about the performance. I guess I should not worry too much about it. I think density is a great feature, especially on smaller images where size is smaller in general!

Ah sorry, I didn't get it that you are already on canary. Thank you for testing it, everyone using it helps getting it shipped sooner!
Is the page you are talking about public or the code open-source? I would still be interested to investigate the cause for that, it could also help others or maybe there is also a bug where next-optimized-images does not generate the correct size.

Thanks for reply! It is public - I tried out the density but did not get it to work. I have now removed the image so it is not testable at the moment (did remove it for design reasons - not because of the lighthouse score!). Whatever I did I got a penalty on one of the scores. This was a full-screen image. I am not sure if there is a problem with this package - maybe it is just the scores in Lighthouse that are too sensitive 🤷♀


Add console clearing functionality to procMon.py

two lines of code added just so that the terminal std output doest look cluttered and hard to understand.

The code works like a champ!, totally impressed!


attrs factory parameter gives "Fields without default values cannot appear after fields with default values" error

Language Server version: 2021.7.7
OS and version: Windows 10 21H1
Python version (& distribution if applicable, e.g. Anaconda): 3.9.6 64-bit
attrs version: 21.2.0

With the attrs module, and a class where a field with a factory parameter follows one with a default value, Pylance reports "Fields without default values cannot appear after fields with default values."
According to the documentation for attrs, the factory parameter is syntactic sugar for default=attr.Factory.  The two classes defined below are equivalent, but Pylance flags C1.field2 as having the error. (https://www.attrs.org/en/stable/examples.html#defaults)
Mypy 0.910 does not report any errors in this code.
from typing import Any

import attr

@attr.s(auto_attribs=True)
class C1:
    field1 : int = 0
    field2 : list[Any] = attr.ib(factory=list)

@attr.s(auto_attribs=True)
class C2:
    field1 : int = 0
    field2 : list[Any] = attr.ib(default=attr.Factory(list))

This is expected behavior. Mypy has special knowledge about attrs built in. Pylance doesn't have special-case knowledge of any third-party libraries, and we don't plan to add any.
We have made some accommodations for attrs and pydantic through this specification, which we are looking to make part of the Python typing standard. But there are areas where attrs behavior differs from the built-in dataclass, and we are not able to accommodate all of these special behaviors. See this section for details. There are known workarounds for most of these limitations if you are interested in using attrs with pylance.

I know we don't necessarily want to add any library specific functionality if we can achieve it via proper typing spec improvements, but I think there is still work to be done to better support attrs as the current coverage doesn't always meet user expectations (and I don't think it's true that we have no plans to try and work on handling specific libs as a whole either).
This one in particular is a problem because the diagnostic is emitted regardless of the type checking level, so anyone using attrs with code that happens to fall the bucket of an unsupported usage ends up with a message that can't be dismissed except via # type: ignore, in addition to it functionally not working as expected (which is another problem that would have happened before transforms anyway).


Bugfix for component handlers callbacks

Fixed javascript error that occured when trying to use "componentHandler.registerUpgradedCallback" caused by using the outer loop variable instead of the inner one.

I signed it!


ATS Should Fail to Start if sni.yaml Fails to Load

Starting ATS with a malformed sni.yaml in ATS 9.1 results in:
[Jul 30 19:24:30.069] traffic_server ERROR: <SSLSNIConfig.cc:172 (Initialize)> /opt/trafficserver/etc/trafficserver/sni.yaml failed to load: 1 [1]: yaml-cpp: error at line 1889, column 25: unknown value "STRICT"

But ATS still starts, just without loading or applying anything in sni.yaml.
This can be a security issue. If a user has records.config configured to allow everything, and uses sni.yaml to block or allow each FQDN, this will result in everything being allowed. And a user could easily miss the above log message.
It sounds like we probably want ATS to load anyway if sni.yaml doesn't exist.
But if it exists and is malformed, either with invalid YAML or with data errors (such as bad enums, as above), I think ATS should fail to start, for security.

@shinrich ^


Thanks,

Hi Jessie,
inspired by your blog post and the Docker file you are sharing here I wrote this blog post:
<EMAIL_ADDRESS>Maybe this Dockerfile - Gits could be of interest to you:
https://gist.github.com/theely/7ab9eb5a7e4b17c20a170d353324d849

Hi theely,
Your docker file looks interesting
I'm building a crawler based on chrome. I really want to run it into docker.
I build image from dockerfile successfully. But when I run it, I get an error
docker run --privileged newsriver.io/dyn-crawler-test https://www.redbulletin.com/us/us/lifestyle/experience-air-to-air-combat-like-a-fighter-pilot
Starting ChromeDriver (v2.9.248304) on port 15694
[0.173][WARNING]: PAC support disabled because there is no system implementation
Exception in thread "main" org.openqa.selenium.WebDriverException: chrome not reachable
  (Driver info: chromedriver=2.9.248304,platform=Linux 3.10.0-327.18.2.el7.x86_64 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 60.24 seconds
Build info: version: '2.53.0', revision: '35ae25b', time: '2016-03-15 16:57:40'
System info: host: '553f98a70322', ip: '<IP_ADDRESS>', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-327.18.2.el7.x86_64', java.version: '1.8.0_91'
Driver info: org.openqa.selenium.chrome.ChromeDriver
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:206)
	at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:158)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:678)
	at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:249)
	at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:131)
	at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:144)
	at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:170)
	at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:159)
	at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:116)
	at DynamicCrawler.main(DynamicCrawler.java:6)

Can you explain that?
PS: I run docker 1.11 in CentOS with root user.

For debugging dockerfiles maybe see #docker on IRC, it's very hard for me to find a fix based off this without knowing the context of what the dockerfile actually looks like, I'm good but I'm not that good ;)

Hi @rain1024 ,
looks like the current stable version of Chrome is not so stable after all, unfortunately I don't recall the exact version number i was running when I wrote the article. I would suggest you to replace "google-chrome-stable" in the Docker file with an exact version of Chrome (e.g. "google-chrome-stable-44.0.2403.155-1.x86_64") and test it. A good approach would be to start with the last version and decrement the version number till you find a stable one that works well with selenium. If you find any could you please send me add a comment to: https://gist.github.com/theely/7ab9eb5a7e4b17c20a170d353324d849 I will than correct the Docker file.
p.s. @jfrazelle the Docker file is locate here: https://gist.github.com/theely/7ab9eb5a7e4b17c20a170d353324d849

hi @theely
Today, I'm very happy when I run image jess/chrome in Ubuntu (still don't work with CentOS 7. I don't know what happend with centos).
Our crawler base on chrome extension instead of selenium. Have you tried inject chrome extension in chrome image?

@rain1024 nope, could you provide me with more informations? Do you have some examples to share?


update leader election settings for hoh agent.

try to fix: https://github.com/stolostron/backlog/issues/23768
Signed-off-by: morvencao<EMAIL_ADDRESS>

That is ACM standard to use customized values for controller runtime.
I am not sure if the bug was fixed or not. but anyway, we need to have this code.
/lgtm


Smart Energy Clusters

Initial Smart Energy Work

@phil-jamieson & @iwinterburn, I added you as reviewers but this is still a draft PR as I'm still working on the conversion. Right now the metering cluster is what I'm working on and my last note was:

Adds the metering cluster, though incomplete. Attributes are done and server received commands to RequestFastPollMode


Convert base_pricing_model.calc_time_stretch to return 1/t

Solidity returns the inverse of python. This issue has several corresponding TODOS (marked with this issue number) that should be resolved.

parity efforts moved to rust implementation


Now we have a Burndown chart

ZenHub has burndown charts, but we need Estimations on tasks to be able to have them.
Since ZenHub doesn't have number of tasks as a metric, I assigned "1" story point to all the issues in 2017Q4 which gave us a burndown chart showing our progress:
https://github.com/TorXakis/TorXakis/milestone/2#reports?report=burndown&milestoneId=2700224&showPRs=false
We will also have a Velocity Tracking report when this Milestone (2017Q4) is finished.

Btw, please remember to set the milestone to 2017Q4 and estimation to "1" whenever you start working on a task! (until we have planning and estimation process in place)


Badge counter not showing on effect bar

The 4.7 PF2e update puts the numerical badge overlay in the bottom left hand corner of the effect display. With Dorako turned on this hides it.
If there is a choice, personally I think the previous large sized centered number was better, the current number is... tiny on a 4k screen.

I fixed the effect value missing in 1.11.8 (regression due to the system change you mentioned).
I don't think Dorako UI has had the value large and centered since the SASS rewrite - I'm leaning towards keeping a similar layout as the system, since adjustments in this area were probably made with future capabilities in mind. (Perhaps afflictions?)


[TextField] TypeScript does not recognize "size" prop

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

When using TextField with "size" prop the following error is being reported by TypeScript:

No overload matches this call.
Overload 1 of 2, '(props: TextFieldProps, context?: any): ReactElement<any, string | ((props: any) => ReactElement<any, string | ... | (new (props: any) => Component<any, any, any>)> | null) | (new (props: any) => Component<...>)> | Component<...> | null', gave the following error.
Type '{ size: string; }' is not assignable to type '(IntrinsicAttributes & StandardTextFieldProps) | (IntrinsicAttributes & FilledTextFieldProps) | (IntrinsicAttributes & OutlinedTextFieldProps)'.
Property 'size' does not exist on type '(IntrinsicAttributes & StandardTextFieldProps) | (IntrinsicAttributes & FilledTextFieldProps) | (IntrinsicAttributes & OutlinedTextFieldProps)'.
Overload 2 of 2, '(props: PropsWithChildren, context?: any): ReactElement<any, string | ((props: any) => ReactElement<any, string | ... | (new (props: any) => Component<any, any, any>)> | null) | (new (props: any) => Component<...>)> | Component<...> | null', gave the following error.
Type '{ size: string; }' is not assignable to type '(IntrinsicAttributes & StandardTextFieldProps & { children?: ReactNode; }) | (IntrinsicAttributes & FilledTextFieldProps & { children?: ReactNode; }) | (IntrinsicAttributes & OutlinedTextFieldProps & { ...; })'.
Property 'size' does not exist on type '(IntrinsicAttributes & StandardTextFieldProps & { children?: ReactNode; }) | (IntrinsicAttributes & FilledTextFieldProps & { children?: ReactNode; }) | (IntrinsicAttributes & OutlinedTextFieldProps & { ...; })'.

Expected Behavior 🤔

The error should not be reported as size is specified by API reference
Steps to Reproduce 🕹

import React from 'react';
import TextField from '@material-ui/core/TextField';

export const Component: React.FC<{}> = () => {
 return (
  <TextField size="small"></TextField>
 );
};

Context 🔦

According to API reference, TextField shall support setting size prop to small, however types declarations do not include this property. The issue is visible on MUI 4.7.2 however problem was also observed on version 4.3.3.
Your Environment 🌎

Tech
Version

Material-UI
v4.7.2

React
16.9.0

Browser
78.0.3904.97

TypeScript
3.5.3

etc.
n/a

tsconfig:
{   "compilerOptions": {     "target": "es5",     "lib": [       "dom",       "dom.iterable",       "esnext"     ],     "allowJs": true,     "skipLibCheck": true,     "esModuleInterop": true,     "allowSyntheticDefaultImports": true,     "strict": true,     "forceConsistentCasingInFileNames": true,     "module": "esnext",     "moduleResolution": "node",     "resolveJsonModule": true,     "isolatedModules": true,     "noEmit": true,     "jsx": "react"   },   "include": [     "src"   ] }

@sarpt Thank you for the report, the TypeScript update is missing:
diff --git a/packages/material-ui/src/TextField/TextField.d.ts b/packages/material-ui/src/TextField/TextField.d.ts
index d1d9c9bb2..2cc053f23 100644
--- a/packages/material-ui/src/TextField/TextField.d.ts
+++ b/packages/material-ui/src/TextField/TextField.d.ts
@@ -38,6 +38,7 @@ export interface BaseTextFieldProps
   rowsMax?: string | number;
   select?: boolean;
   SelectProps?: Partial<SelectProps>;
+  size?: 'small' | 'medium',
   type?: string;
   value?: unknown;
 }

Do you want to submit a pull request? :)

Why isn't size="large" in the definition? It's in the docs, isn't it?
I'm migrating some code from JS to TS and I found:
<IconButton size="large" />

But it's complaining that large is not small | medium | undefined...


missing "isLoaded" from MixItUp 2

Hello,
I kind of miss the "isLoaded" state functionality in MixItUp 3 or maybe I just didn't get the point with new API and states:
In my HTML template I am fetching pages dynamically via AJAX with jQuery, which means I can't simply hook a new initialization to the DOM-ready any more and once an instance of MIU has been created its dead after I navigate back to the site that contains it.
So what I used to do with MIU 2 was to ask if an instance already exists, then destroy it and re-initialize it, kind of like this:
if(!$container.mixItUp('isLoaded')){
  $container.mixItUp('destroy'); // destroy first
  $container.mixItUp(...) // then re-initialize
}

What I don‘t seem to get is what this state is called in MIU 3 and what the syntax is to re-create the above if-statement

By the way, I currently get what I am aiming for, but I have the feeling that it’s dirty and bad practice and could be improved heavily. This is what I have in my jQuery Ajax 'success' callback:
if($('#container').length) {   mixer.destroy();   setTimeout(function(){     initMixItUp();     mixer.forceRefresh();   }, 1); }

Hi @tsawitzki,
I would recommend the following approach with MixItUp 3:

When your page loads, instantiate your mixer:

var mixer = mixitup('#container');

Whenever your ajax page load code is called, always destroy the active mixer:

if (typeof mixer !== 'undefined') {
   mixer.destroy();
}

When your ajax has finished and your new page has rendered, instantiate again:

var mixer = mixitup('#container');

You'll probably want to abstract 1 and 3 into a single function that can be called at various points in the  lifecycle of your site.
MixItUp 3 will never let your instantiate over the top of an active mixer on the same element. You will see a console warning if you try to do so. Therefore, if you always just instantiated and never destroyed, it would still work, but the above ensures that no warnings will be fired, and you get a fresh instance each time.
You'll just need to identify the appropriate places in your ajax code to hook into (via callbacks or promises or otherwise). Let me know if that helps.
As a side-note, and for other people reading this, the above code assumes you're working in a single top-level namespace for all your site's JS code (i.e. global variables), which is fine for basic static pages. However, if you are doing stuff like dynamically rendering pages via ajax, you may want to component-ize the reusable parts of your UI. For example - create a "filterable grid" component that manages the instantiation and garbage collection of mixitup, and can be instantiated whenever your newly-rendered view contains the appropriate elements (i.e. a grid). This probably isn't necessary for now, but something to bear in mind for the future. FYI, this is what most UI frameworks like React, Angular etc are doing on some level.

Hi Patrick Kunka, Thank you
it has solved my time.
`				function my_repeater_show_more() {
var mixer = mixitup('.gallery_wrap');
// make ajax request
jQuery.post(
my_repeater_ajax_url, {
// this is the AJAX action we set up in PHP
'action': 'my_repeater_show_more',
'post_id': my_repeater_field_post_id,
'offset': my_repeater_field_offset,
'nonce': my_repeater_field_nonce
},
function (json) {
// add content to container
// this ID must match the containter
// you want to append content to
jQuery('.gallery_wrap').append(json['content']);
/* mixItUp */
if (typeof mixer !== 'undefined') {
mixer.destroy();
}
setInterval(function () {
/* mixItUp */
var mixer = mixitup('.gallery_wrap');
},500);

						// update offset
						my_repeater_field_offset = json['offset'];
						// see if there is more, if not then hide the more link
						if (!json['more']) {
							// this ID must match the id of the show more link
							jQuery('#my-repeater-show-more-link').css('visibility', 'hidden');
						}
					},
					'json'
				);

			}`


fix(k8s.py): access API server by IP address

Accessing the k8s api by hostname fails sometimes from within the deis/workflow pod. This changes the requests.Session to use the IP address and port, which is more reliable, but at least for now requires disabling verification of the local SSL cert.
Cert verification is False here since the IP address in the request does match any of the hostnames in the server's cert, and neither that verification nor the HTTP Host header can be overridden in this case in the python requests library. That is, I couldn't see any way short of monkeypatching, after reading the requests source code and overriding several classes involved.

And I guess the k8s API can't be accessed by plain old http, eh? I haven't seen a way, so makes sense to me to disable SSL verification if we can't override the Host header.


Fix typo on adfs previousthumbrints json tag

🔧 Changes
Fixes a typo on the json tag for PreviousThumbprints on the ConnectionOptionsADFS struct
📚 References

🔬 Testing

📝 Checklist

[x] All new/changed/fixed functionality is covered by tests (or N/A)
[x] I have added documentation for all new/changed functionality (or N/A)

Codecov Report
Patch and project coverage have no change.

Comparison is base (4e0d47c) 94.79% compared to head (d0daf0c) 94.79%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #270   +/-   ##
=======================================
  Coverage   94.79%   94.79%
=======================================
  Files          46       46
  Lines        8738     8738
=======================================
  Hits         8283     8283
  Misses        353      353
  Partials      102      102

Files Changed
Coverage Δ

management/connection.go
75.00% <ø> (ø)

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


Add/feedback page

Add basic feedback page that send the form data to supabase database and added  a popup after form is submitted.

issue with merging 😭

did you rebase? commit history seems a bit off


Alternative for float

Currently it seems the DockMonitor floats above my content, making it hard to see my content and still keep the devtools open. Would there be a way to tun the docktools into an object that pushes your content to the side effectively making the content window smaller?

Just remove DockMonitor and use LogMonitor (or any other monitor) directly :-). DevTools you get from createDevTools is a regular React component. You can put it anywhere you like.


feat: Runtime toggle

Describe the solution you'd like
Thank you for your work on this plugin.
This may not be possible due to a OS/framework level limitation but is it possible to toggle privacy mode at runtime?
For example if the user is on a financials screen I would enable it but on other pages I’d disable it.
Not an issue if not possible, just curious.

Thanks for the feature request.
This should be possible.

Thanks for the feature request.
This should be possible.

Amazing thank you!

Amazing thank you!


Cannot add dependency for app_review.

Steps to Reproduce

When i try to add app_review plugin for my flutter project I get the error below:
Logs

[app_review] flutter packages get
Running "flutter packages get" in app_review...
Error on line 26, column 3 of pubspec.yaml: A package may not list itself as a dependency.

   ╷
26 │   app_review: ^0.1.0

   │   ^^^^^^^^^^

   ╵
pub get failed (65)
exit code 65

[✓] Flutter (Channel dev, v1.4.8, on Mac OS X 10.14.4 18E226, locale en-MY)
    • Flutter version 1.4.8 at /Users/thenesh/Documents/Development/flutter
    • Framework revision fbefd6b816 (2 days ago), 2019-04-01 10:58:30 -0700
    • Engine revision a850016454
    • Dart version 2.2.1 (build 2.2.1-dev.2.1 None)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/thenesh/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.2, Build version 10E125
    • ios-deploy 1.9.4
    • CocoaPods version 1.6.0

[✓] Android Studio (version 3.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 33.4.1
    • Dart plugin version 182.5215
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[✓] VS Code (version 1.32.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 2.25.0

[✓] Connected device (1 available)
    • iPhone 6 • C1E54BD2-CC9F-4DBC-ADD9-651209895641 • ios • com.apple.CoreSimulator.SimRuntime.iOS-12-2 (simulator)

• No issues found!

Please advise.

Try flutter clean. The plugin does required swift too.

Already tried few times. Still the same.

Does this happen with a fresh app? I have added it to several of my apps no issue.

Yes. Created brand new project. Still happens.

Im using this in multiple app, please test now

Don't know if it helps but I've got this open source app which I'm successfully using it in now, with version app_review: ^1.0.0.
https://gitlab.com/greycastle/travel-rates
If you want to compare code. I did have many issues getting it working as my project had not enabled swift to begin with. But maybe first step would be to ensure your position of the include is correct (that error message looks like it's complaining on something else) and then make sure your version is okay. It looks as though you're referencing 0.1.0 instead of 1.0.0


CUDA out of memory

I am NVIDIA GeForce RTX 3090 with 24GB of graphics memory, running at 1024 resolution, but the graphics memory is not enough

I am NVIDIA GeForce RTX 3090 with 24GB of graphics memory, running at 1024 resolution, but the graphics memory is not enough

https://github.com/PixArt-alpha/PixArt-sigma/issues/19   , follow this issue.

Training or testing?

培训还是测试？

testing

Training or testing?

Run script: Python scripts/interface.py

Try these
18GB minimum with https://github.com/PixArt-alpha/PixArt-sigma#3-pixart-demo.
8GB with https://github.com/PixArt-alpha/PixArt-sigma/blob/master/asset/docs/pixart.md

I have no problem running the reference code you provided. What is the reason for this?
eg:
import torch
from diffusers import Transformer2DModel
from scripts.diffusers_patches import pixart_sigma_init_patched_inputs, PixArtSigmaPipeline
assert getattr(Transformer2DModel, '_init_patched_inputs', False), "Need to Upgrade diffusers: pip install git+https://github.com/huggingface/diffusers"
setattr(Transformer2DModel, '_init_patched_inputs', pixart_sigma_init_patched_inputs)
device = torch.device("cuda:0" if torch.cuda.is_available() else "cpu")
weight_dtype = torch.float16
transformer = Transformer2DModel.from_pretrained(
"PixArt-alpha/PixArt-Sigma-XL-2-1024-MS",
subfolder='transformer',
torch_dtype=weight_dtype,
use_safetensors=True,
)
pipe = PixArtSigmaPipeline.from_pretrained(
"PixArt-alpha/pixart_sigma_sdxlvae_T5_diffusers",
transformer=transformer,
torch_dtype=weight_dtype,
use_safetensors=True,
)
pipe.to(device)
Enable memory optimizations.
pipe.enable_model_cpu_offload()
prompt = "A small cactus with a happy face in the Sahara desert."
image = pipe(prompt).images[0]
image.save("./catcus.png")

I don't get you. What's the problem?

I have no problem running the code you provided. What is the reason for the same 1024 resolution?
https://github.com/PixArt-alpha/PixArt-sigma?tab=readme-ov-file#2-integration-in-diffusers

No idea. Maybe diffusers have some optimization?


Fix nimble build

Fix the nimble build which was referencing outdated and not-anymore-existing versions
Because of problems with versioning of dependencies, this needs a lock file, which only works from nimble 0.14
0.14 is unfortunately not packages with the newest nim 1.6.2, making install a bit complicated. Here it goes:
nimble install nimble
~/.nimble/bin/nimble install
~/.nimble/bin/nimble test

Note: you might have to clean (remove) your ~/.nimble folder before.

Closing in favor of https://github.com/codex-storage/nim-codex-dht/pull/66.


Won bid items won't be listed

I'm using the bid function to bid a quite amount of players but the won items do not get listed. Any idea what I did wrong?

i don't know if the untradable players was the problem or not
Once I sold all the players from the league I was trading in, the program started list the players I won in the transfer market
I used to get this message a lot with red background " sorry, this item cannot be swapped because its duplicate is untradable "
But now the message no longer appears
This can help in developing the program
good luck

i don't know if the untradable players was the problem or not
Once I sold all the players from the league I was trading in, the program started list the players I won in the transfer market
I used to get this message a lot with red background " sorry, this item cannot be swapped because its duplicate is untradable "
But now the message no longer appears
This can help in developing the program
good luck

also the new update with black screen window doesnt autolist anymore!

also the new update with black screen window doesnt autolist anymore!

For the autolist to work on a bid item you have to run the tool till that items expiry time, if you tool the bot before the expiry time the card will go to unassigned

For the autolist to work on a bid item you have to run the tool till that items expiry time, if you tool the bot before the expiry time the card will go to unassigned


Add reveal command

This PR adds the reveal command, which is the opposite of the existing obscure command.
It will take as an argument an obscured password (that is, a password as stored in rclone.config) and will return the actual password value.
I'm taking for granted this command doesn't exist just because it was not implemented, and not because we don't want it to be easily available. In the end, my understanding is that obscurity is just an extra step for avoiding visual eavesdropping.
Lot of global flags are available for this command and are useless, but since obscure command also has them I didn't go further in removing them.

I'm taking for granted this command doesn't exist just because it was not implemented, and not because we don't want it to be easily available. In the end, my understanding is that obscurity is just an extra step for avoiding visual eavesdropping.

I didn't implement it just to add a small extra step in un-obscuring the passwords....
I'm fully aware that the rclone password obscuration isn't secure, it is just to protect against visual eavesdropping like you said (and a good way of putting it).
What do you think about making the command hidden - add Hidden: true in the command definition then it won't appear in the help but will still be usable?

Lot of global flags are available for this command and are useless, but since obscure command also has them I didn't go further in removing them.

Yes that is a different project!

What do you think about making the command hidden - add Hidden: true in the command definition then it won't appear in the help but will still be usable?

Added! In the end, my goal was to provide with a mechanism that will allow recovering this initial password. The scenario would be using auto generation of password but lack of awareness from the user that those passwords will be stored in an obscured format, ending up on a scenario where the original password is unknown by the user itself.
Just thinking, maybe a disclaimer when using auto-generated passwords would be good?

Added

Thanks!

Just thinking, maybe a disclaimer when using auto-generated passwords would be good?

Do you mean telling the user to make a copy of the password as it will be stored obscured in the password file?

Do you mean telling the user to make a copy of the password as it will be stored obscured in the password file?

Yes. Just a proposal to minimize the use cases of the need for a "reveal" option :)

Yes. Just a proposal to minimize the use cases of the need for a "reveal" option :)

Good idea. Fancy sending a PR for the relevant strings in the code?
I'll merge this now - thank you very much for your contribution :-)


Word of the day not displaying.

Hi,
I love this idea. Unfortunately it isn't working from me.
I installed per your installation guide and the logs shows that it gets the word.
[09.06.2023 11:03.09.645] [LOG]   WordGenius-Received notification: MMM_WordGenius_GetWord
[09.06.2023 11:03.09.647] [LOG]   {
  config: { updateInterval: 120000, headerText: 'Word Genius Word of the Day' }
}
[09.06.2023 11:03.09.647] [LOG]   WordGenius-Getting word
[09.06.2023 11:03.09.651] [INFO]  Checking git for module: MMM-WordGenius
[09.06.2023 11:03.09.680] [INFO]  Checking git for module: MagicMirror
[09.06.2023 11:03.09.887] [LOG]   WordGenius-Got word definition
[09.06.2023 11:03.09.888] [LOG]   {
  definitions: [],
  word: 'Decapod',
  pronunciation: '[DEK-ə-pod]',
  partOfSpeech: 'noun',
  origin: 'French, 19th century'
}
[09.06.2023 11:03.09.888] [LOG]   WordGenius-GotWord Sending Notification
[09.06.2023 11:03.09.888] [LOG]   WordGenius-sending notification
[09.06.2023 11:03.09.888] [LOG]   {
  definitions: [],
  word: 'Decapod',
  pronunciation: '[DEK-ə-pod]',
  partOfSpeech: 'noun',
  origin: 'French, 19th century'
}

But it doesn't display on the screen.

What's your config section look like?
Here's mine
		{ 			module: 'MMM-WordGenius', 			position: 'bottom_center', 			classes: 'default everyone', 			config: { 				updateInterval: 3600000, 				headerText: "WordGenius" 			} 		},
That's in magicmirror/config/config.js
I believe the "everyone" class is important.
If that doesn't help, try hitting the magic mirror with a browser and then viewing the raw HTML.
That might give you an indication of if the data is all there and it's just not visible, or if it's not actually pushing any data to the rendered HTML at all.

yea it's not working for me either

Yeah just tried it, cant get it to work either

Just given the log, it +looks+ like it's at least connected to the Word of the day server and getting a word, so that's good.


Updated Swashbuckle package to 6.3.1

Updated the Swashbuckle package to the latest version to verify an issue with this package.
There appears to be a breaking change in 6.3.1 which doesn't allow this package with its current dependency on 6.2.3 to work as intended. Appears that upgrading the package here works as intended.

Thank you! We've updated the packages.


Settings conditional dict

Description
Implementing concept of one entity value modifying children entities of dictionary. Added dict-conditional entity type which always have one entity with enumerator where value of enumerator change other children of dictionary.
Changes

added the dict-conditional entity type for settings
parent can tell if missing defaults can be skipped or not

Example schema of dict-conditional
{
    "type": "dict-conditional",
    "key": "my_key",
    "label": "My Key",
    "enum_key": "type",
    "enum_label": "label",
    "enum_children": [
        # Each item must be a dictionary with 'key'
        {
            "key": "action",
            "label": "Action",
            "children": [
                {
                    "type": "text",
                    "key": "key",
                    "label": "Key"
                },
                {
                    "type": "text",
                    "key": "label",
                    "label": "Label"
                },
                {
                    "type": "text",
                    "key": "command",
                    "label": "Comand"
                }
            ]
        },
        {
            "key": "menu",
            "label": "Menu",
            "children": [
                {
                    "key": "children",
                    "label": "Children",
                    "type": "list",
                    "object_type": "text"
                }
            ]
        },
        {
            # Separator does not have children as "separator" value is enough
            "key": "separator",
            "label": "Separator"
        }
    ]
}

Example output of example schema
# When enum is set to "separator"
{
    "type": "separator"
}

# When enum is set to "action"
{
    "type": "action",
    "key": "action_1",
    "label": "Action 1",
    "command": "run command -arg"
}

# When enum is set to "menu"
{
    "type": "menu",
    "children": [
        "child_1",
        "child_2"
    ]
}

How to test
Currently not used in schemas but example is available in example_schema.json.

SyncServer must be modified to be able use this ability

must have ability to return schemas for each provider without loading settings itself (endless loop of error)

if list will have ability to define it's object type using templates it would be possible to use conditional dict for scripts menu (similar to example but menu would have list with whole schema as children).

Depends on: https://github.com/pypeclub/OpenPype/pull/1753

For Menu item...

For Menu item...

Should be fixed now.


edit text body field not in focus when opening a node (desktop)

When opening a node to edit, the text field is not in focus.
This is especially annoying for nodes that are not new.

fixed via a90bca86c1320d27c20bae3288e1c8ae7cf3dc1f


Add Dijkstra's Algorithm in different languages

Proposal
Implement Dijkstra's algorithm in different languages
Describe the solution you'd like
Dijkstra's algorithm is an algorithm for finding the shortest paths between nodes in a graph
 Have you read the Contributing Guidelines on Pull Requests?
Yes
Please answer the following questions for yourself before submitting an issue.

[x] I checked the documentation and found no answer
[x] I checked to make sure that this issue has not already been filed

I would like to implement this in C++

I would Like to implement in C

Assigned the issue to @Shashwat545 in C++

Assigned the issue to @vidit21srivastava  in C


Migrate from MongoLab to other db

I think you can use cloudant. I have good experience using it and they have a npm module that makes things easy.

yeah, we will go to Cloudant

@germanattanasio do you know if we can create an account there without a credit card ? The doc I found mentioned a credit card required

you don't pay for it as long as you use bluemix and your ibm account.
On Thu, Nov 26, 2015 at 3:53 PM Paulo Cavoto<EMAIL_ADDRESS>wrote:

@germanattanasio https://github.com/germanattanasio do you know if we
can create an account there without a credit card ? The doc I found
mentioned a credit card required
—
Reply to this email directly or view it on GitHub
https://github.com/alanbraz/cognitive-head-hunter/issues/5#issuecomment-159992983
.

:+1:

almost done, just need to test one last method

done, migrantion of data and code completed

mongolab service removed


RawEditor update to support putting QuillEditor inside a Scrollable view

Hi,
First of all, thank you for your work on this package, it is really great !!
Here is the purpose of this PR :
I had to put a QuillEditor inside a SingleChildScrollView but this scrollView wasn't scrolling automatically when the text entered was down the screen. I needed the editor to be expandable and not scrolling by itself.
Example :

The solution I found was to use the ScrollController passed to the QuillEditor widget in the SingleChildScrollView containing the QuillEditor. Like so, the _showCaretOnScreen method from RawEditor calls the ScrollController used by the SingleChildScrollView to scroll if it has clients.
The result is the following :

The blue part is a Container with the Flutter logo in it. The purple part is the QuillEditor. Both of them are part of a Column contained inside a SingleChildScrollView.
The code used is the following :
class _ScrollPage extends StatefulWidget {
  const _ScrollPage({
    Key? key,
  }) : super(key: key);

  @override
  _ScrollPageState createState() => _ScrollPageState();
}

class _ScrollPageState extends State<_ScrollPage> {
  late final QuillController controller;
  late final ScrollController scrollController;
  late final FocusNode focusNode;

  @override
  void initState() {
    super.initState();
    controller = QuillController.basic();
    scrollController = ScrollController();
    focusNode = FocusNode();
  }

  @override
  void dispose() {
    controller.dispose();
    scrollController.dispose();
    focusNode.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: SafeArea(
        child: SingleChildScrollView(
          controller: scrollController,
          child: Column(
            children: [
              Container(
                color: Colors.blue[400],
                height: 200,
                child: const Center(child: FlutterLogo(size: 150)),
              ),
              Container(
                color: Colors.purple[100],
                child: Flexible(
                  child: QuillEditor(
                    controller: controller,
                    focusNode: focusNode,
                    scrollController: scrollController,
                    scrollable: false,
                    padding: const EdgeInsets.all(16),
                    autoFocus: true,
                    readOnly: false,
                    expands: false,
                  ),
                ),
              ),
            ],
          ),
        ),
      ),
    );
  }
}

Please, let me now if this change is causing conflicts with the current behavior.
Thank you !
(This PR is also fixing the issue discused here https://github.com/singerdmx/flutter-quill/discussions/291)

Thank you so much Kevin for the solution, this really helped.


applivery-ios 0.3.1

What's new

Conditionally upload Certificates and Provisioning Profiles by checking a new param called uploadCodeSigning
Prepared to support uploading of .app but yet ready.
Updated Step name (title)

New Pull Request Checklist
Please mark the points which you did / accept.

[x] I will not move an already shared step version's tag to another commit
[x] I read the Step Development Guideline
[x] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[x] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[x] I read and accept the Abandoned Step policy

Hi @BirmacherAkos,
Please find updated version of the Step including your recommendations in PR2018
Thank you again,
C.


experiment: fix bug in try-finally checking

follow on to #4507
The code was checking the effect of the finally clause in only one of the cases (inference or checking, but not both). Plus it's more consistent to just restrict the capability in the environment rather than checking the effect.
The error message is slightly worse, but then this is a rather obscure feature that I hope won't get used much....

LGTM! Rejecting throw a priori is certainly better than observing the effect a posteriori. Thanks for the fix!

Also, at one point in the past, sending a message didn't actually have a T.Await effect, IIRC, just await and other cps requiring operations did. Now they do, because we detect message queue full errors and report them as catchable errors.


GEOSgcm GNU runs do not pass regression

So, now that we've fixed the GNU run issue by updating to Chem 1.8.1 (#378), my tests are now showing that ALL GNU runs do not pass regression. I'm not sure if it's start-stop or layout, but I have to assume layout since start-stop is usually much more fundamental.
But I'm baffled as to why Intel would. My guess is this is some pointer thing again in either Chem or GOCART. I'll probably be pinging @tclune, @atrayano and @bena-nasa to help with this.
First, I'll try and confirm that it is layout.

May I just say:  "bleh".

Actually, it might be start-stop. I tried 4x24 and 3x12 and all was good. Time to make up a start-stop test.

Yeah. It's start-stop. Huh.

Okay. So with the help of @aoloso, I ran one instance at a time. And I got:

Instance
Restart Failures

DU
du_int, ss_int

SS
fvcore_int, moist_int, moist_imp, aiau_imp, turb_imp, gocart_imp, du_int, ss_int, hemco_imp, saltwater_imp

CA.oc
du_int, ss_int

CA.bc
du_int, ss_int

CA.br
du_int, ss_int

SU
du_int, ss_int, su_int

NI
du_int, ss_int, ni_int

I think I might need to ping @pcolarco to start.
Pete, for context, the runs above were made as so:

Run 2 steps, dump checkpoints
Run 1 step, stop, run 1 step, dump checkpoints

For each run, I edited these loops in Run1:
!   Run the children
!   -----------------
    do i = 1, size(gcs)
      call ESMF_GridCompRun (gcs(i), importState=gim(i), exportState=gex(i), phase=1, clock=clock, __RC__)
    end do

and Run2:
!   Run the children
!   -----------------
    do i = 1, size(gcs)
      call ESMF_GridCompGet (gcs(i), NAME=child_name, __RC__ )
      if ((index(child_name, 'data')) == 0) then ! only execute Run2 method if a computational instance
         call ESMF_GridCompRun (gcs(i), importState=gim(i), exportState=gex(i), phase=2, clock=clock, __RC__)
      end if
    end do

where I changed to loop to be:
    do i = 1, 1
...

and run, then did 2, 3, 4...
This was pretty much the only way @aoloso could figure out how to run just part of G2G. (Maybe there's a better way?)
What the table shows are which checkpoints are different when running just that instance. So for most instances, it's always DU and SS. But when only SS is run...hoo boy.

Comments/questions.

I've not yet tried running only a subset of the components. Some of them talk to each other (NI for example depends on what SU, SS, and DU are doing). It sounds like you are telling me you cannot run a subset without hacking the fortran, is that right?
If only running DU why are you looking at/getting an ss_internal_rst at all anyway? I don't understand what you are reporting your table.
If the aerosols are radiatively active (are they?) then turning on/off individual components will change the state of everything else in the model, including other species checkpoint values due to change in dynamics (at least). Is that what's going on?

Comments/questions.

I've not yet tried running only a subset of the components. Some of them talk to each other (NI for example depends on what SU, SS, and DU are doing). It sounds like you are telling me you cannot run a subset without hacking the fortran, is that right?

Well, I just wasn't sure how to run just a subset. I tried fiddling with GOCART2G_GridComp.rc but almost everything I tried sort of crashed the model.

If only running DU why are you looking at/getting an ss_internal_rst at all anyway? I don't understand what you are reporting your table.

What my test was was a variant of gcm_regress.j. The normal run is:

Run model for 1 day at NX x NY → Gives us Set #1 of Restarts.
Run model for 18 hours at NY x NX, stop.
Run model for 6 hours at 1x6 → Gives us Set #2 of Restarts.

The script then compares all of Set #1 to Set #2. It's a sort of "super zero-diff" test.
Now my tests with GNU show that changing the layout (4x24 vs 6x36 or whatever) was fixed by your bugfix that fixed it for Intel as well.
But I found that GNU does not handle start-stop regression. When you run with GNU, if you run for 1 day straight, you get different answers when you run for 18 hours and then 6 hours.
Further testing showed that you can see this by comparing 2 steps vs 1 step + 1 step.
My tests above show what you get when you compare ALL the restarts generated by a 2-step run versus a 1-step+1-step.
I was further then trying to figure out what component in G2G might cause this. I suspect G2G because it is the main difference from GOCART 1 days when GNU regressed just fine.

If the aerosols are radiatively active (are they?) then turning on/off individual components will change the state of everything else in the model, including other species checkpoint values due to change in dynamics (at least). Is that what's going on?

Well, I'm not comparing the model against any other configuration. I am just trying to see what happens if you run a 2 steps versus 1 step + 1 step changing nothing. With Intel, these two runs give the same answers, but we do not get that with GNU.

I take back part of my question. I think you can turn off a component in GOCART2G_GridComp.rc by removing its name like this, from:
ACTIVE_INSTANCES_SU:  SU
to
ACTIVE_INSTANCES_SU:
I did this working on the previous regression test to isolate SU as the culprit. Commenting it out (#SU) does not work, you have remove from the line entirely.
Now based on what you say I wonder if there's some sort of missing "import_rst" for the various components at play here. Alternatively, could be the alarm for the SU oxidants isn't behaving as expected.
Those are my pre-dinner thoughts.

I take back part of my question. I think you can turn off a component in GOCART2G_GridComp.rc by removing its name like this, from: ACTIVE_INSTANCES_SU: SU to ACTIVE_INSTANCES_SU:
I did this working on the previous regression test to isolate SU as the culprit. Commenting it out (#SU) does not work, you have remove from the line entirely.

Ahhh. Yeah, I think I was just commenting out since, well, there are other comments on the line. I'll try that.

Now based on what you say I wonder if there's some sort of missing "import_rst" for the various components at play here. Alternatively, could be the alarm for the SU oxidants isn't behaving as expected.

Glad you have an idea! I'll start doing some tests removing active instances.

Well, some more tests with turning off instances in RC/GOCART2G_GridComp.rc:

Instance(s) Turned Off
Restart Failures

DU
All but gwd_imp, irrad_int

DU, CA
CRASH (line 1817 in G2G GC)

SS
CRASH (NI need?)

SU
CRASH (NI need?)

NI
All but gwd_imp, irrad_int

NI, CA
fvcore_int, moist_int, aiau_imp, moist_imp, turb_imp, gocart_imp, du_int, su_int, hemco_imp, saltwater_imp

NI, SS
du_int, su_int

NI, SS, DU
CRASH (line 1700 in G2G GC)

NI, SS, DU, SU
CRASH (line 1700 in G2G GC)

NI, SS, SU
du_int

NI, SU
All but gwd_imp, irrad_int

NI, SU, DU
CRASH (line 1700 in G2G GC)

Not much logic here I can see.
Also, I'm beginning to think we might need some protections in GOCART saying things like "You can't run NI without SS" or something...

@mathomp4 Is that line in the aerosol activation code? (qaux = qa_)
Try making sure your AGCM.rc has this line as I paste it below:
USE_AEROSOL_NN: 0
Maybe you're crashing because the single moment cloud scheme is expecting all the aerosol species but you're not providing them.

@pcolarco Ah. Okay. Thanks. That did it. I'll try and re-run the line 1700 crashes with that option.

Well, some progress. I've updated the table and I seem to have found a way to get GNU to regress: Just run CA with aerosol activation off! 😄
I suppose one question that maybe @pcolarco can answer: How is CA different from SS, DU, SU, and NI+SS+DU?  Is there a routine that everything but CA uses? I tried doing some side-by-side comparisons, but CA doesn't seem that unique. I mean, it has the weird 'three instances in one' thing, but...not much else.

@mathomp4 Disclaimer: I was not involved in the aerosol activation bit and only learned it was a thing by stumbling over it myself. My suspicion is that--since the Brown Carbon bit in CA is newish--the brown carbon is not connected properly with the aerosol activation. I will try and look at it this morning.

Okay. So after some work, I can now say I can get GNU to regress...as long as I only run for 2 steps and set USE_AEROSOL_NN: 0. I can do this by setting mintracer in ConvPar_GF_GEOS5.F90 to zero instead of tiny(1.).
Unfortunately, this value of mintracer has been that way since we started on Git and I couldn't figure out in CVS land where it came from. I'm pretty sure the change came from @wmputman on one of his branches, but he probably got it from Saulo at some point.
That said, I'm not exactly sure why mintracer isn't zero. I mean...no aerosols or whatever is valid. Negative tracers is a bad thing, but zero isn't I don't think.

Update. I was in a telecon with @tclune @weiyuan-jiang @junwang-noaa and said "Let me try GCC 11.2 and Intel MPI" because I've been experimenting with that recently. And when I ran it...it regressed!
Meanwhile, last night GCC 11.2 + Open MPI did not (as usual). Buuuuuut, there was one more difference. In my IMPI test, I updated to my Baselibs 7.5.0/MAPL 2.23 branch of GEOSgcm first.
So, I now have new things to try. I will report back soon.

One more update to this. It also regresses just fine at NAS with MPT (hadn't noticed this, been blind).
So, Intel MPI: Pass, MPT: Pass, Open MPI: Fail.
Very weird that MPT works. I mean, MPT is always the one we have issues with!
This is some confusing stuff. I mean, the only MPI directly in GOCART is Bcasts of reals which can't be responsible. And the fact that it's start-stop which in a way is even less involved with MPI. I could imagine MPI stacks causing issues with MPI layout regression. But start-stop with no layout changes??
Well, might be time to become a beta-tester for @jsquyres, et al, and try out Open MPI 5...

Since you tagged me, I'm curious about this: did you find and resolve the issue?  Was it something to do with Open MPI?

@jsquyres In the end, no. It seemed like Open MPI was the cause since Intel MPI and MPT worked just fine. But I finally realized that we run with Open MPI, we run with one setting in our IO layer differently.
Long ago, Open MPI writing our checkpoint files in our normal code path was like 1000x slower or something, but it was fine in an alternate path. This was always weird to me since, in the end, the two paths are nigh-identical but, hey, it worked.
Once I figured that out, we looked at the alternate code path and found a bug in 4d writing. Fixed that and it seems good. Now any issues I have seem to be GNU related and not Open MPI related.
Of course, that said, you will probably be hearing more from me. My first attempt with Open MPI 5 already led to a couple questions:

https://github.com/open-mpi/ompi/issues/11299
<EMAIL_ADDRESS>


Hi 👋

Hi, I have a question that has nothing to do with the m5launcher but would it be possible for you to program me a firmware for m5stickcplus2 for free

And just to tell you, you can solve the problem on the Megaolodn games on the bruce frimware, we can only go down but nothing happens when we go up.


gltf2interface still on 4.1.0-beta.3, so I can't upgrade loaders to 4.1.0-beta.4

Bugs
I tried upgrading to 4.1.0-beta.4, but I depend on the loaders package, which itself depends on gltf2interface, but the latter is still on 4.1.0-beta.3.

Pinging @sebavan

This is really strange, let me publish it manually... I ll ping you once done

should be good now


Docs.MS Release Updates for Azure.Analytics.Synapse.Spark

Update docs metadata and targeting for release of Azure.Analytics.Synapse.Spark

Docs Build status updates of commit 3b2c43a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

api/overview/azure/analytics.synapse.spark-readme-pre.md
:warning:Warning
View
Details

api/overview/azure/analytics.synapse.spark-readme-pre.md

Line 17: [Warning-insecure-link] Link 'http://azure.microsoft.com/en-us/develop/net/' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 27: [Warning-insecure-link] Link 'http://azure.microsoft.com/en-us/downloads/?sdk=net' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 72: [Warning-InvalidBookmark] Invalid link: 'Delete spark batch job'. The file api/overview/azure/analytics.synapse.spark-readme-pre.md doesn't contain a bookmark named 'delete-spark-batch-job'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Don't lock child if parent already has lock

Changes as requested by @abeesh after seeing a 20x slow down with local synchronizations compared to batch connectors.

What problem does this solve? Storing the fact that we hold the lock on a newly created element seems less expensive (and is innocuous) than the query to find its parents.

What problem does this solve? Storing the fact that we hold the lock on a newly created element seems less expensive (and is innocuous) than the query to find its parents.
Edit: I now see we cache the lock on models, so it doesn't look like we'll need to look too far up the tree to find that an element's model is locked. I'm not sure which way will be more efficient. At any rate, this code doesn't "lock an element", it saves the fact that an element is already locked. What prompted you to change this?

Apologies, I just updated the description. Abeesh and team noticed a massive slow down with local synchronizations compared to batch connectors due to the existing behavior. Taking over 5 hrs for local sync vs 20 mins for a batch connector run.
With the included changes, they saw times reduce from 60 mins to under 3 mins.

It seems to me that this will be a better change (assuming you're trying to optimize insert performance);
change this to:
  protected static onInserted(arg: OnElementIdArg): void {
    const locks = arg.iModel.locks;
    if (locks && !locks.holdsExclusiveLock(arg.model))
        locks.elementWasCreated(arg.id);
  }

Keith is the expert here and the above-mentioned change should work for local sync.

With the included changes, they saw times reduce from 60 mins to under 3 mins.

I now see that we call SaveChanges on every call to elementWasCreated. I'm sure that's what is killing the performance. Probably should add some way to batch this up if we're doing a lot of inserting without the model lock held. We'd need some kind of begin/end batch technique. That can wait for some other time ; for LocalSync, I presume this is the case where they create a new Model so it will be locked. My suggestion above will eliminate almost all the lock overhead. There still is a query to the lock database to determine whether the model is locked, but that's way faster than querying the iModel for an element's model.

Thanks for the recommendation Keith, I've made the suggested changes. I'll add to the backlog an item to investigate and implement batching.


Unify most memory kinds

Following #680 which is related to processors, it would be good to reduce the number of memory kinds we have to the bare necessities, having applications rely on capability and affinity queries instead of some set features based on the KIND.
A good example of this is, instead of multiple SOCKET_MEM memories, have multiple SYSTEM memories that are bound to the various numa nodes, with their affinities reflected by their numa bindings.
Another example would be ZCMEM, which will eventually need to support NUMA affinities to specific GPU processors.  In this case, we plan to expose multiple ZCMEM memories with stronger affinities to their associated GPUs rather than introduce a new kind.
This should make Realm internal logic much easier to work with, Realm-based libraries easier to compose and handle compatibility cases, and Realm applications much easier to develop.

This is a user-visible change, so we should discuss the proposed interface (once you have one) in a Legion meeting.


Ideas for implementing Word document (.docx) support

Hi!
You mentioned in a previous issue that you are searching for a Word document displaying solution.
I can give you some thoughts on it :)
So, a word document can be converted to HTML. If you find a good 'docx to html' converter library, you can easily display the
HTML in a JavaFX WebView.
Some sites that can be helpful:

Convert Word doc to HTML programmatically in Java
Word Document (DOC/DOCX) to HTML Conversion using Java
java-mammoth - Convert Word documents to simple and clean HTML
Apache POI - WordToHtmlConverter

Another solution can be a 'Word to image' converter library, and then display the images below each other (but that has a lot of disadvantages).
Hope it helps you moving forward!
Best regards
Daniel

Hi Daniel
Thank you very much for the links.
A few of them I already saw. The others I will read soon.
I already had different ideas, like converting .docx-files into PDF. Problem is the most libraries I found were either commercial or terribly outdated / not maintained any more.
Anyhow I will have a second look at the "to HTML" approach.
Thanks again and best regards
Stephan

Added the Mammoth converter in version 1.5. Thanks again for the suggestion 🙏🏻

Wow, nice job! @stephansann


[SPARK-50510][CONNECT][TEST][FOLLOWUP][3.5] Fix flaky ReattachableExecuteSuite

What changes were proposed in this pull request?
Simplify org.apache.spark.sql.connect.execution.ReattachableExecuteSuite."reattach after connection expired" to make it more deterministic.
Why are the changes needed?
The test previously involved execution and interruption that made the test unnecessarily flaky, e.g., an exception was thrown when releasing the corresponding execution, not when reattaching the execution.

The test's sole purpose is to check whether the lack of 'session' results in the correct error code.
The involvement of actual query execution only makes the test flaky and complicated.

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Repeatedly ran testOnly org.apache.spark.sql.connect.execution.ReattachableExecuteSuite.
Was this patch authored or co-authored using generative AI tooling?
No.

https://github.com/changgyoopark-db/spark/runs/34523136586
https://github.com/changgyoopark-db/spark/runs/34523226244
https://github.com/changgyoopark-db/spark/runs/34523275936
-> triggered three jobs.

All three jobs passed!

Merged to branch-3.5.

Actually, this should be a followup to SPARK-50510, and the previous pr  was https://github.com/apache/spark/pull/49127 . Since the code has already been merged, it's not possible to change the commit log anymore. I've added the [FOLLOWUP] tag to the PR title on the page.

Thanks, @LuciferYang


change bulmaNavbarBurger to encapsulate the burger span elements

even though the Bulma documentation does make this explicitly clear (because it is kind of obvious), the a.navbar-burger must contain the following Node of three span elements:
concat {
    span { AriaHidden.ToAttrWithTrueValue }
    span { AriaHidden.ToAttrWithTrueValue }
    span { AriaHidden.ToAttrWithTrueValue }
}

These three spans represent the buns and patty of the burger 🍔

this change is a breaking change 🤕


Add exception class for transport logger

Exception class to transport a logger object is added. Quite useful when error log is generated in backend and displayed in the frontend.

Hi, thanks for the PR.
I am not sure I understand the use case. Could you be more specific?

I may be a coincidence but I've just came by similar code in Paul Hardy's eBite Refactoring Legacy ABAP Code? He uses a cx_no_check as a way to go up in the stack and display logger message.
Though, it is an interesting case, I'd prefer not to add it to ABAP-Logger package for the following reasons:

using exception for validation error is a contested use case (see Fowler)
this not an exception that ABAP-Logger would raise when facing an exceptional situation but rather a way to handle ABAP-Logger. Similarly to #18, I do not believe it belong to the core package.

I'll leave this PR open for a while just in case someone want to contribute to the discussion


LeaseDuration is currently mandatory

The xDhcpServerScope actually requires the LeaseDuration property to be defined or the resource execution fails, but the configuration doesn't  enforce this.

The LeaseDuration property should be marked as 'Required' in the schema.mof
Default the LeaseDuration to "00:08:00" (my preferred option).

IMHO I'd want to go with your preferred option (default the LeaseDuration).

If we add a simple if($LeaseDuration) around the get-validTimeSpan in the test it will be possible to leave LeaseDuration empty. This will not change the lease duration of any existing scopes and will default to the standard 8 days when creating a new scope. I don't think leaving a non-mandatory value blank should force the configuration to use a default value if the scope already exist.

The issue was fixed.  We still need a test to make sure the issue does not regress.

@TravisEz13 I'll add a test or two and update to the latest test template...


Merging master brach to admin Portal feature branch

Merging master brach to Admin Portal feature branch

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.18 out of 20 committers have signed the CLA.:white_check_mark: msm1992:white_check_mark: chathuranga95:white_check_mark: tharindu1st:white_check_mark: TheRasanjana:white_check_mark: tmkasun:white_check_mark: vithu30:white_check_mark: ChamodDamitha:white_check_mark: fazlan-nazeem:white_check_mark: Meruja:white_check_mark: dushaniw:white_check_mark: bhathiya:white_check_mark: malinthaprasan:white_check_mark: isharac:white_check_mark: Arshardh:white_check_mark: kavishkafernando:white_check_mark: hisanhunais:white_check_mark: Dinushi:white_check_mark: ruks:x: Senthuran100:x: tgtshanikaYou have signed the CLA already but the status is still pending? Let us recheck it.


update sshd

I was having issues trying to connect to the ssh server and i came across issue #508
My error was different but the experience from the client of having the connection immediately closed was the same, and I've had this experience before in a different context (that I don't currently have all the details of)
I'm not sure what the root cause is, but i figured updating the dependencies and getting on a major version of sshd-core at least wouldn't hurt (and was hoping, with some luck, it might just fix the issues i was having)
The stack trace from the initial error that started all this for me was:
[sshd-SshServer[763300f]-nio2-thread-3] WARN org.apache.sshd.server.channel.ChannelSession - Error processing channel request<EMAIL_ADDRESS>org.apache.sshd.common.SshException
	at org.apache.sshd.agent.common.AgentForwardSupport.initialize(AgentForwardSupport.java:51)
	at org.apache.sshd.server.session.ServerConnectionService.initAgentForward(ServerConnectionService.java:60)
	at org.apache.sshd.server.channel.ChannelSession.handleAgentForwarding(ChannelSession.java:559)
	at org.apache.sshd.server.channel.ChannelSession.handleRequest(ChannelSession.java:327)
	at org.apache.sshd.server.channel.ChannelSession$ChannelSessionRequestHandler.process(ChannelSession.java:602)
	at org.apache.sshd.server.channel.ChannelSession$ChannelSessionRequestHandler.process(ChannelSession.java:600)
	at org.apache.sshd.common.channel.AbstractChannel.handleRequest(AbstractChannel.java:100)
	at org.apache.sshd.common.session.AbstractConnectionService.channelRequest(AbstractConnectionService.java:274)
	at org.apache.sshd.common.session.AbstractConnectionService.process(AbstractConnectionService.java:153)
	at org.apache.sshd.common.session.AbstractSession.doHandleMessage(AbstractSession.java:431)
	at org.apache.sshd.common.session.AbstractSession.handleMessage(AbstractSession.java:326)
	at org.apache.sshd.common.session.AbstractSession.decode(AbstractSession.java:780)
	at org.apache.sshd.common.session.AbstractSession.messageReceived(AbstractSession.java:308)
	at org.apache.sshd.common.AbstractSessionIoHandler.messageReceived(AbstractSessionIoHandler.java:54)
	at org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:184)
	at org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:170)
	at org.apache.sshd.common.io.nio2.Nio2CompletionHandler$1.run(Nio2CompletionHandler.java:32)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.apache.sshd.common.io.nio2.Nio2CompletionHandler.completed(Nio2CompletionHandler.java:30)
	at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
	at sun.nio.ch.Invoker$2.run(Invoker.java:218)
	at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
	at org.apache.sshd.agent.common.AgentForwardSupport.initialize(AgentForwardSupport.java:45)
	... 24 more

getting java.lang.UnsupportedClassVersionError: org/apache/sshd/server/CommandFactory : Unsupported major.minor version 52.0 wouldn't think anything in the code changes here would cause that?

No idea about this particular case but that normally means you're using some class or library that's only compiled for a later version of Java; maybe you have something compiled for Java 8 that you're trying to run on Java 7?

I'd guess it has to be one of these updates
        "org.apache.sshd" % "sshd-core" % "1.3.0",
        "org.bouncycastle" % "bcprov-jdk15on" % "1.56",
        //-- test --//
        "com.jcraft" % "jsch" % "0.1.54" % "test",

compilation versions are out of my area of expertise, is there quick check like a www.jvm-version.com/org/apache/sshd/sshd-core/1.3.0 or something ?
i tried on my machine setting my java -version to 1.7 but then i got a different failure
[info] 'compiler-interface' not yet compiled for Scala 2.12.1. Compiling...
[info] 'compiler-interface' not yet compiled for Scala 2.12.1. Compiling...
java.lang.UnsupportedClassVersionError: scala/tools/nsc/Main : Unsupported major.minor version 52.0

Scala 2.12.x does not work with Java 1.7.x; perhaps try running the build with Scala 2.11.x if you want to test java 1.7 behavior?
You probably inspect the bytecode and determine the JVM version for every class file, and if the class files are in jars you can unzip them then check http://stackoverflow.com/questions/1096148/how-to-check-the-jdk-version-used-to-compile-a-class-file

ok, looks like sshd-core v1.3.0 required java8, v1.2.0 seems fine
i think this one is a transient failure
[info]         		ammonite.ops.ShelloutException: CommandResult 1

[info]         		Exception in thread "main" upickle.Invalid$Data: Expected Js.Arr (data: {

[info]         		    "message": "API rate limit exceeded for <IP_ADDRESS>. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",

[info]         		    "documentation_url": "https://developer.github.com/v3/#rate-limiting"

[info]         		})

@lihaoyi is there any way around the rate limit failing the test?

@emanresusername I've been thinking about it. My idea is to replace git.io api with something like this. gonna send a PR later today.

Looks good


Svelte 5 peer dependency conflict

Hello,
Are you planning to update Svelte package soon? When we add package to projects that user Svelte 5 we can conflicting peer dependency error.
npm error Conflicting peer dependency<EMAIL_ADDRESS>npm error node_modules/svelte npm error   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm error   node_modules/@iconify/svelte npm error     dev<EMAIL_ADDRESS>from the root project npm error
We can just force install but would be nice to not to do that.
Thank you.

Strange error. 5.0.5 should match requirement.

Created a blank project with latest Svelte, added @iconify/svelte. Works fine, no peer dependency errors.
Can you create a reproduction of bug you are seeing?

Im using shadcdn i think the error/warning shows with shadcdn beside

It went away when we recreated project with svelte 5 cli. When I checked the old project I saw that sveltekit pulls svelte5.next** whatever version. If it is not the next version error goes away.


Fix #185

 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.

LGTM (try read -> if EAGAIN wait for readable -> try read again)


Switch native trin-core types for ethportal-api

What was wrong?
I've been trying to use ethportal-api types inside trin-core - but I've found that since they're all inextricably linked, we can't transition gradually and need to convert them all simultaneously.
How was it fixed?
To-Do

[ ] Add entry to the release notes (may forgo for trivial changes)
[ ] Clean up commit history

Imo, #504 was rushed, had insufficient test coverage and code review. Resulting in unnecessary work & debate. Relying heavily upon reth for types was never fully justified imo. Such a significant refactor that affects the entire codebase requires a :+1: from everybody involved in the project. At the very least - the transition to reth-based types should have lived on a separate branch until the entire transition was complete, with passing tests (similar to my bridge work).
We now have 18 failing tests after integrating reth-based types. These are tests I've debugged before and tbh I have no interest in debugging them again on a whole new set of types. Nor do I think it's a worthwhile use of time.
To be honest, after working on this pr, I've developed some fairly strong opinions against using reth-based types. But, I am aware that there are blind spots in my understanding and that I could be the cause of these failing tests. So, I'd like to get a review from @jacob and @ognyan to make sure that I'm using the new types correctly, before we continue with the debate as to whether saving some lines of code justifies introducing these new types & new external dependencies.

I'm sorry about the frustration that the reth refactor is causing you. The scope of #504 was limited to ethportal-api and rpc, so that was my justification for foregoing a broader set of approvers. I still stand behind the decision to move to reth.
Looking at the test failures, it looks like those failures are for tests that should not even exist in trin. For example, receipts::tests::calculate_receipts_root tests the computation of the receipts Merkle root, but this is not logic that we maintain. I'm not sure why we opted to keep the tests in those files for which all type definitions were removed. The point of moving to reth is so that we do not have to have such tests. Ideally, tests are only necessary to test portal-specific encoding of the types.
re: usage of reth types, it looks like you have duplicated code that is already provided by reth (e.g. receipts root computation).

@jacobkaufmann No problemo, it's inevitable when it comes to working on a shared codebase.

receipts::tests::calculate_receipts_root tests the computation of the receipts Merkle root, but this is not logic that we maintain.

We do maintain that logic here

I'm not sure why we opted to keep the tests in those files for which all type definitions were removed.

Those type definitions exist in master. They were removed in this particular pr as part of the transition over to the ethportal-api types. The tests were left in their original location to minimize the diff in this pr.

The point of moving to reth is so that we do not have to have such tests.

Sure, but I don't feel comfortable switching out the native trin-core types (& tests) for the reth-based types until we can plug in the new reth based types into the old trin-core tests and get green. Then, I'm ok with removing the old types & tests completely.

so that was my justification for foregoing a broader set of approvers.

Fair enough, no harm done. Just wanted to point out that since the purpose of the ethportal-api types is to eventually replace all of the types inside trin-core, I think the scope of the consequences of the refactor is broader than you initially anticipated.

re: usage of reth types, it looks like you have duplicated code that is already provided by reth (e.g. receipts root computation).

Good point, hadn't noticed those. Integrated that code and got rid of a few failing tests, but we're still dealing with 15 or so failing tests. I'll continue to investigate those

I still stand behind the decision to move to reth.

For the record, I'm not against this ... eventually... I just want to make sure our old tests are passing with the new types and that we've evaluated all the pros & cons of such a move before committing to it

closing since we're moving ahead with #615