Endpoint rejecting correlation_data that contain zeros

Hi again,
Currently client and server / broker reject messages with a correlation_data property that contains zeros.
The endpoint rejects such a message with a "malformed packet error".
This is because the correlation_data property is processed as a string.
https://github.com/redboltz/mqtt_cpp/blob/a292c9c21ce7af627134769d25dc65af5dfb7a8d/include/mqtt/endpoint.hpp#L6400-L6404
Instead it should be processed as binary data.
        case v5::property::id::correlation_data: {
            process_binary(
                force_move(self),
                force_move(session_life_keeper),
                force_move(buf),

Maybe I'm wrong here but I didn't find any limitation on correlation data in the MQTT protocol.
https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901115
Thanks for considering,
Dino

Thank you for reporting the issue.
The issue should be fixed by #889.


If rename a file I cannot open neo-tree again.

As title. Sorry I will provide debug details later, have to work.

Is this still happening?

I think this can be closed since I cannot reproduce it now.


Use lpsum function when solving the schedule

Fixes #36

Coverage remained the same at 100.0% when pulling fb64116ee719e55708c4453b87586d6e0d874227 on issue-36 into 80485d15c33583276ef53d2ee922584da1d9acb7 on master.


Future of iAPI and eAPI

iAPI and eAPI have been in fairly inactive development for more than 3 years and still haven't really gotten anywhere. This is one of the worst failures you can imagine, and it has to be fixed. They either have to be officially discontinued, or finished soon. Here are my plans for them:
eAPI needs a really big rework. Two options:

We could use a better file structure with less files, like already suggested in #15.
We could support a protocol like REST, gRPC, GraphQL, ... instead.

iAPI got some improvements in 316889ea2ed1aac16a6a9af593113650576ba2b2 already, and it should get some more. But the real thing it needs is dogfooding. First of all, we can use its previous versions for patching #17. But the more important part is rebuilding the CXClient core to use the iAPI.

I have actually now come up with the perfect solution for the eAPI: It is replaced by my RCON ideas.
To explain that slightly: I have wanted to implement an RCON server in CXClient for a little while, just as a remote way of running CXClient commands (#foo). Now I have realized that this can actually replace the eAPI by just providing a few more machine-readable commands. (e.g. a command to list all enabled mods or get a JSON with the settings of all mods)


Move email digest triggering to default zulip config

Based on our mailing list exchange at https://groups.google.com/forum/#!topic/zulip-help/wOkfHg9Wc2g, this change should cause daily digest e-mails to trigger in auto-configured zulip environments.
Questions/issues:

the current digest functionality hardcodes a list of days on which digests are sent (Tue-Thu). It might be good to expose this decision in settings.

the current digest functionality will double-send e-mails if you trigger the digest generator twice. Ideally it would be nice to "mark" the point at which the last digest was sent for each user, to avoid this.

Automated message from Dropbox CLA bot
@jmandel, it looks like you've already signed the Dropbox CLA. Thanks!

Looks like you forgot to git add puppet/zulip/files/cron.d/send-digest-emails

Re-wrote as a move"

Merged, thanks for working on this @jmandel!  I opened #549 for the follow-up issues you mentioned.


Typo 12: slide 46 (Moving added fields On-Prem - Workarounds)

r is missing in Script.

Fixed, thanks


fixed some comment errors

What is the purpose of the change
fixed some comment errors
Brief changelog
Verifying this change

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #7509 (229fa28) into master (0ddc988) will decrease coverage by 0.40%.
The diff coverage is 60.78%.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5692210...229fa28. Read the comment docs.


Store session token locally

The session token should be:

[x] stored locally
[x] included in subsequent API calls

...so that the user doesn't have to reauthenticate themself

this seems to be done


List of users does not contain roles

Seems like createQuery from Morphia Datastore does not resolve DBRef attributes.

Fixed with 53030f34cd4563bcbd62f29306653b394fa8bd14


Auto Discovery does not remove learned nodes when updating declaration

Environment

AS3 Version: 3.18
BIG-IP Version: 14.0.1

Summary
Create Service-HTTP with poolmember auto-discovery and 'overwrite' this by Creating an Service-HTTPS with the same config to change an existing HTTP service into HTTPS.
With the first declaration the pool members are getting auto-discovered. But when you POST the second declaration (HTTPS) the poolmembers are already known as members from the first declaration and existing in the 'local > nodes' and therefore can not get auto-discovered and attached to the pool. This results in an unavailable VS.
Steps To Reproduce
Steps to reproduce the behavior:

Submit the following declaration:

{
    "class": "AS3",
    "action": "deploy",
    "declaration": {
        "class": "ADC",
        "schemaVersion": "3.7.0",
        "id": "Deploying_App_Services",
        "label": "Deploying_App_Services",
        "remark": "Deploying_App_Services",
        "App_Services": {
            "class": "Tenant",
            "HTTP_Service": {
                "class": "Application",
                "template": "http",
                "serviceMain": {
                    "class": "Service_HTTP",
                    "virtualAddresses": [
                        "<IP_ADDRESS>"
                    ],
                    "snat": "auto",
                    "pool": "Pool1"
                },
                "Pool1": {
                    "class": "Pool",
                    "monitors": [
                        "http"
                    ],
                    "members": [
                        {
                          "servicePort": 80,
                          "addressDiscovery": "aws",
                          "updateInterval": 1,
                          "tagKey": "Autodiscovery",
                          "tagValue": "true",
                          "addressRealm": "private",
                          "accessKeyId": "{{accessKeyId}}",
                          "secretAccessKey": "{{secretAccessKey}}",
                          "region": "eu-west-1"
                        }
                    ]
                }
            }
        }
    }
}

HTTPS-Service
 {
    "class": "AS3",
    "action": "deploy",
    "declaration": {
        "class": "ADC",
        "schemaVersion": "3.7.0",
        "id": "Deploying_App_Services",
        "label": "Deploying_App_Services",
        "remark": "Deploying_App_Services",
        "App_Services": {
            "class": "Tenant",
            "HTTPS_Service": {
                "class": "Application",
                "template": "https",
                "serviceMain": {
                    "class": "Service_HTTPS",
                    "virtualAddresses": [
                        "<IP_ADDRESS>"
                    ],
                    "snat": "auto",
                    "pool": "web-pool",
					"profileHTTP": "basic",
					"serverTLS": "webtls"
                },
                "web-pool": {
                    "class": "Pool",
                    "monitors": [
                        "http"
                    ],
                    "members": [
                        {
                          "servicePort": 80,
                          "addressDiscovery": "aws",
                          "updateInterval": 1,
                          "tagKey": "Autodiscovery",
                          "tagValue": "true",
                          "addressRealm": "private",
                          "accessKeyId": "{{accessKeyId}}",
                          "secretAccessKey": "{{secretAccessKey}}",
                          "region": "eu-west-1"
                        }
                    ]
                },
				"webtls": {
                    "class": "TLS_Server",
                    "certificates": [
                        {
                            "certificate": "webcert"
                        }
                    ]
                },
                "webcert": {
                    "class": "Certificate",
                    "certificate": {
                        "bigip": "/Common/default.crt"
                    },
                    "privateKey": {
                        "bigip": "/Common/default.key"
                    }
                }
            }
        }
    }
 }

--
2. Observe the following error response:
{
    "code": 500,
    "message": "declaration failed",
    "response": "Something bad happened",
    "host": "localhost",
    "tenant": "Tenant",
    "runTime": 5234
}

Expected Behavior
The Auto-discovery process should remove all discovered nodes.
Since you create a POST which does an overwrite of the first HTTP-Service declaration, you would expect that when POST-ing the HTTPS-service declaration everything gets removed. Considered that you use the same tenant and same app to get from HTTP to an HTTPS service.
Actual Behavior
The discovered nodes from the first HTTP-Service declaration are still there when the next HTTPS-service is declared. This results in the nodes not getting attached to the pool and an unavailable VS.

It looks like any renaming of the pool path is causing this problem. I have added this bug to our internal product backlog as AUTOTOOL-1676.
I believe if you keep the application and pool name the same between declarations, it should work as expected.

If you are still looking for a fix, please reach out to us at<EMAIL_ADDRESS>


How does the update websocket protocol ideally behave?

How does the update websocket protocol ideally behave? And what are a relayer's responsibilities for updates? The documentation is a bit vague at the moment.
Will it send you an update when an order:
is canceled?
is partially filled?
is fully filled?
expires?
I'm assuming all of the above. And how should this scheme be formatted for all of the above scenarios?
{
    "type": "update",
    "channel": "orderbook",
    "requestId": 1,
    "payload": {.....}
}

If it were me, I'd do something like the below to handle the above cases. But the docs only show the type "updated"
"type": "filled",   // Fully filled orders that are no longer available at all

"type": "updated",   // Partially filled or canceled orders

"type": "expired",   // Expired orders that are no longer available

Closing as this is fixed with the orderbook aggregator (tk). Not going to bake into SRA.


Fix no-ssl-trace

Ensure we use OPENSSL_NO_SSL_TRACE guards where appropriate.

The CI failure is probably unrelated but highly suspicious anyway!

This pull request is ready to merge

Pushed. Thanks.


ECOPROJECT-180: Adding a support of disconnect a device

https://github.com/jakub-dzon/yggdrasil/pull/4

/lgtm
@bardielle please rebase

@bardielle - please rebase.


Include support for empty user-supplied halo catalogs.

Resolves #936
CC @rainwoodman

The Appveyor failure is unrelated and will be resolved elsewhere - Travis passes including the new regression test, so going ahead with the merge.


Merge from Global Sites to JP site

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #1
Test URLs:

Before: https://main--accenture-newsroom-jp--hlxsites.hlx.page/
After: https://main--accenture-newsroom-jp--hlxsites.hlx.page/

Closing this because we can just sync fork to get the changes incorporated into this fork.


Code splitting & bundle size reduction

this implements code split as described here https://github.com/react-page/react-page/issues/698
its based on https://github.com/react-page/react-page/pull/699
I also included https://github.com/react-page/react-page/pull/695 because i wanted to also lazy load slate
Further refactorings i did:

i slightly changed to structure of the plugins: Controls now contains only the controls (as the name suggests), it used to also call the Renderer, but that was not so clean. Now, the Renderer is called in the plugins Component and conditionally lazy-loads the Controls, if readOnly is false.
i exported some types into their own files, because some types were imported across packages and i was not sure, if this would also lead to that whole file beeing bundled
i added a bundle analyzer in the examples to see the different webpack bundles.
I removed support for StaticComponent, it was only used for slate and it was confusing with the introduction of Renderer. This might be breaking for external plugins, but i think its good to simplify the api. Having said that, we further refactor this, so that a plugin always accepts a Renderer (or name it again StaticComponent) and a Control. When the editor is in readOnly, every plugin renders its Renderer, when not, it renders Renderer AND its Control. This logic is now still in the plugins, but could be abstracted away. Currently one Plugin - slate again - slightly differs from this logic: it does not render Renderer, when in edit mode, because it's Control component also includes the whole slate editor, but that could be fixed.

What's next:

i hope this pr can be merged. I know, it's a lot, but the changes are more simple than it looks like
publish a test version: i would like to publish a test version so that people can try this with in different environents

hooray, tests work now! (there is something wrong on master with the @types versions and some other typescript problems, this has been fixed here)

sorry for the messy comit history, i will do a better rebase


walk introduced in 1.5.2 leads to memory leak + crash

Versions + Platform

[ >= 1.5.2] SDK version - @sentry/electron@v?.?.?
[ witnessed on 9 and 10 ] Electron version - electron@v?.?.?
[ mac ] Platform - Windows/macOS/Linux

Description
Unfortunately I don't have a reproducible demo to show for this, but it appears the introduction of the walk function in 1.5.2 causes my application to endlessly spin when that function is hit for a very certain input (I can't pinpoint it, but it is fully replicable). When this occurs, my entire application would freeze and be unclickable, and eventually it would leak enough memory to crash. walk was seemingly introduced to break circular references, but I think in my case it has caused one that does not occur in 1.5.1.
While I don't have a demo, I can get a maintainer or anyone interested in fixing this set up with my app so they can encounter the issue directly.

Commented on the wrong issue a bit ago, it's this issue that still exists in 2.0.4, sorry about that.

Seeing this same issue with 2.1.0 as well. Freezes, totally unusable, then crashes. I removed the Sentry.init(...) call in the renderer process and it no longer crashes.

I just opened that ^ over where @sentry/utils lives, Electron 12 will require the latest @sentry/electron once the latest PR taken is in a release (it may already be).

cc @HazAT who seemed to introduce usage of wallk in 1.5.2

@james-criscuolo @drinksbydrew I think we might be having our app freezing in the same manner you're describing with @sentry/electron 2.4.0.
I'm still trying to determine if this is the cause. Our users have sent videos and screenshots of the app freezing, but internally at our company we're not able to reliably reproduce this. Do you know of any contrived ways to reproduce this?
You say "a very certain input" do you mean an  box? Our app is a search app and people use an  all day. Any tips on how to trigger this would be greatly helpful. Thanks.

We are on it!

If I'm to stand any chance of fixing this I'm going to need to reproduce it or get a stacktrace.
@james-criscuolo do you still have an app to reproduce this that you can share privately with me?

@aguynamedben with our production app we see a small trickle of unresponsive renderer events from all platforms logged to sentry. Our app does long term data logging so is left running for days. I've witnessed one first hand where the renderer hung when switching back to the app after not being used for hours. We still don't know the cause but have seen something similar from Electron for years so haven't suspected @sentry/electron.
Our initially temporary and now looking Ng term "solution" is to listen for the  unresponsive renderer event in the main process and kill + restart the hung renderer. Since our app stores it's state outside of the renderer, we can kill and restart them and continue from where we left off.
What platforms are your users reporting this issue with?

I was able to get around this, but I believe I can still create the situation to recreate. We were logging an Array of fairly nested objects, and as soon as the code hits that it would spin. I have it commented out, so I should be able to re-add it and reproduce.

I went back to the commit where I was reproducing and can no longer reproduce. I now get a JSON circular reference error instead, and it does not infinite loop. I don't have time at the moment to dig into it and get back to reproducible, sorry.

@james-criscuolo thanks for checking!

I've just managed to reproduce this myself locally. In my case console logging a seemingly basic object causes it to go off walking a huge recursive object tree and leaks around 1GB every 10 seconds!
My limited debugging so far suggests that the walk function is not correctly detecting circular references in some cases.

I haven't had time to reproduce this, but I recently I saw some Electron team members asking people to repro bugs in Electron using Electron Fiddle. https://www.electronjs.org/fiddle @timfish it might be worth trying to copy/recreate that exact object in an Electron Fiddle if you have 10 extra mins. I kicked the tires on it the other week and it's pretty good.

I can reproduce it easily in our production app but I have a feeling that getting anything close to that running in Electron fiddle will take an inordinate amount of time and not bring us any closer to the cause.
The object that I carelessly console.log'ed and made it into breadcrumbs would no doubt have caused issues anyway if it had made it into an event.  Event payloads sizes are limited so it almost certainly makes sense to reduce the depth to < infinity! Something around 100 could be enough any anyone hitting that limit will likely do it only by mistake.
I'm also going to test a few JSON.stringify(crazyObj, walk) to see if I can reproduce this in a more isolated fashion.

For now we've limited the recursion depth to 50 to remove the chance of this happening and this was released in 2.4.1.

👏 @timfish Thank you. We never had a good repro case proving this was an issue, but it's good to know recursion depth is limited. We'll be testing out 2.5.0 in our next release. Thanks again.

Even with the depth limited to 50, I've still managed to managed to find a case where I can get a hand and high memory consumption due to logging of a recursive object.
Reopening this for more investigation.

Still exists in 2.5.4, unfortunately I don't have a reproducible demo to show for this, but i can show you the stack.

@alderzhang Did it crash your app? Bugs like this in the Sentry SDKs are definitely something I'm concerned about, we had a bad one one time that was fixed quickly, but still resulted in a lot of pain for our users and our engineer team.
Is this going to be addressed with urgency?

@aguynamedben Yes, it crash my app. It cause huge error log print per second, then makes render process consumes a large amount of memory in a short time, finally the app will crash due to OOM

Add a logpoint at walk function head with format: 'walk-log', key, value, depth, memo.  Then I get log like this.

There is another type of stack:

I think my problem is something wrong(JS Exception) occur while walk, then VUE runtime catch it and try to print error log by console.error, but sentry catch console.error again and try to call walk function leads to infinity loop. So, maybe I can fix this by silent VUE warning. Or we need to use some method to prohibit catching exceptions again during the execution of the walk function.

Update: silent VUE warnings only makes log not to print, the walk function still infinity loop, it means sentry catch exception directly without console.error.

Thanks for the reports.

Add a logpoint at walk function head

Logging inside walk will cause breadcrumbs and scope updates to be generated which will in turn call walk.
The only time I've been able to trigger this was when we accidentally logged a huge object tree to the console

@alderzhang It looks like the issue you are seeing is related to this:
https://github.com/getsentry/sentry-javascript/issues/2957

Thanks for the reports.

Add a logpoint at walk function head

Logging inside walk will cause breadcrumbs and scope updates to be generated which will in turn call walk.
The only time I've been able to trigger this was when we accidentally logged a huge object tree to the console

You are right! Make beforeBreadcrumb always return null solved my problem.
Sentry.init({   dsn: 'xxx',   beforeBreadcrumb = (breadcrumb, hint) => null, });
It seems that the problem is caused by the following log printing (just some exception stack, It doesn't seems to have any huge objects).
localhost-1639020358884.log

There's been a lot of improvements to the underlying Sentry SDKs in this area and this will be released in version 3.0.6 of the Electron SDK. Please open a new issue if anyone finds this is still causing issues.

Still exists in 3.0.7, @alderzhang  saved my life

Thanks for the reports.

Add a logpoint at walk function head

Logging inside walk will cause breadcrumbs and scope updates to be generated which will in turn call walk.
The only time I've been able to trigger this was when we accidentally logged a huge object tree to the console

@timfish Thanks! You are right, make beforeBreadcrumb always return null solved my problem.
Sentry.init({
  dsn: 'xxx',
  beforeBreadcrumb = (breadcrumb, hint) => null,
});

It seems that the problem is caused by the following log printing (just some exception stack, It doesn't seems to have any huge objects). localhost-1639020358884.log


LightCycle swallows onOptionsItemSelected

If you create an activity which extends LightCycleAppCompatActivity and it contains a fragment which extends LightCycleSupportFragment, the activity receives a callback to onOptionsItemSelected when you select an option item (as usual), but the fragment doesn't.
It seems like this might be due to LightCycleAppCompatActivity not calling super.onOptionsItemSelected() - therefore the event doesn't get propagated to the fragments in the activity.
See: https://github.com/soundcloud/lightcycle/blob/master/lightcycle-lib/src/main/java/com/soundcloud/lightcycle/LightCycleAppCompatActivity.java#L47

As a temporary solution, forwarding the call manually does the trick. Example:
// In the Activity
    @Override
    public boolean onOptionsItemSelected(MenuItem item) {
        String tag = getString(R.string.fragment_example);
        return findExampleFragment("tag").onOptionsItemSelected(item);
    }


Nested components and children

Very interesting stuff 🙂
Do you have any plans for supporting nested components and children?
const Button = ({ children }) => <button>{children}</button>;
Button.templateVars = ["children"];

const App = ({ message }) => <Button>{message}</Button>;
App.templateVars = ["message"];

everything comes out "flat" so if you have nested components, we'll still need to supply data like

Ohh, ok. I get it now, thanks.

So the data supplied server side would need to be called children and of course we could get duplicates in different components.

Why do you need children if you're flattening it out? Shouldn't you replace children with the resulting markup generated by the parent?
Imagine:
const Message = ({ className, children }) => (
  <>
    Message:
    {children}
  </>
);

const App = ({ title, message }) => (
  <>

{title}

      <Message className="my-message">This is my {message}</Message>

  </>
);
App.templateVars = ["title", "message"];

  <?php echo $data["title"]; ?>

  Message:

    This is my <?php echo $data["message"] ?>

I think this stuff becomes more important again when thinking about nested components in loops for example

Yeah. At first glance, it seems like flattening everything out is simpler. But I wonder if the complexity will grow over time without reproducing the concept of components in PHP.
Do you have any thoughts about that?

Why do you need children if you're flattening it out? Shouldn't you replace children with the resulting markup generated by the parent?

Yeah exactly, we should probably just set the message on the App level, and we can forget about children, but I imagine there are some use cases where you might want to set it on the button level for example.
Your code example is correct, it's how it should work today in it's current state.

Yeah. At first glance, it seems like flattening everything out is simpler. But I wonder if the complexity will grow over time without reproducing the concept of components in PHP.

This is an interesting idea... it would be cool to break it down into to components (and challenging) but still need to figure out how necessary it is...
Right now I can think of 3 levels to this:

Keep it flat (as we already discussed) and maybe use naming of exported variables to avoid collisions
We could kindof "namespace" PHP keys:
$data['app/button/message']
Or we could completely go another route and deconstruct the whole thing into component parts - still not sure what that would look like yet...

I do like the idea of number 3 in principle but I think it would need more testing to see if its even viable with this approach.
Right now the way this works is it allows a regular render of an app, and pulls out the rendered html.
And we inject bits of "code" (just html strings) and occasionally change the logic (so certain things are always rendered, even if the a condition says it should not be).
To break it into seperate components - I'm not sure what that would look like yet - or if its possible -  we would need to greatly alter the output application and render clean components side by side...
Some thoughts / questions:

If we did have multiple components in PHP and reconstruct the app essentially, how could we supply the data, considering some components are responsible for their own data (not passed in as props) - eg useinstanceId()
What does a complicated use case look like so we could try to test some of these theories, to see how "ugly" it gets...

These are not questions for you specifically but good questions I think that are worth investigating... I would like to see how far we could get this.

Just to add, the nesting of components in loops, I think will be viable in the current paradigm with some work. This is my current thinking and what I'm working to towards at the moment (please excuse the not completely realistic example 😆):
const Radio = ({ className, value, children }) => {
	const [ checked, setChecked ] = useState( false );
	const uid = useInstanceId( Radio );
	return (
		<>
			<input type="radio" id={ uid } className={className} value={value} checked={checked} />
			{children}
		</>
	);
};
App.templateVars = ["checked", "value", "uid", "children"];

const App = ({ title }) => {
	const radios = [
		{ value: 'radio1', label: 'Radio 1' },
		{ value: 'radio2', label: 'Radio 2' },
	];

	return (
		<>

{title}

				{ radios.map( ( radio ) => (
					<Radio className="my-radio" value={radio.value}>{radio.label}</Radio>
				) ) }

		</>
	);
};
App.templateVars = ["title", ["radios", {type: "list"} ]];

Here it probably make more sense to have some of templateVars on the Radio itself, and then we could supply data like:
$data['title'] = 'My app title';
$data['radios'] = array(
    array(
		'children' => 'Radio 1',
		'value' => 'radio1',
		'uid' => 'radio1',
		'checked' => true,
	),
	array(
		'children' => 'Radio 2',
		'value' => 'radio2',
		'uid' => 'radio2',
		'checked' => false,
	),
);

In this instance it would be cool to be able to rename "children" (although this is a contrived example, and we would probably just pass in "label" instead)..

Oooh interesting idea! Been busy on some other projects but hoping to get back into this fully in about in about a week.


GPU slot failing to start

Background: I have a cluster with a few nodes with GPUs and capacity, so I wanted to use that extra capacity for this project.
First, I tried running the provided image as a daemonset on my GPU enabled nodes, but that failed because FAH couldn't find the CUDA libraries and thus did not detect the GPU. I solved that by make a new container based on the nvidia/cuda:10.0-runtime-ubuntu18.04 container, which enabled the FAH to find the CUDA libraries and detect the GPU.
Now though I'm seeing the following error:
ERROR:WU01:FS01:Failed to start core: OpenCL device matching slot 1 not found, try setting 'opencl-index' manually
Based on some googling, this is either a problem with my drivers, or with the config in FAH. Has anyone else seen this error? It seems like it can be solved from the FAH control interface, but I'm not sure how to expose that.

I can confirm the same behaviour. I tried to run on server with 8x2080ti and get following in beginning of log:
05:57:08: OS Arch: AMD64
05:57:08: GPUs: 0
05:57:08: CUDA: Not detected: Failed to open dynamic library 'libcuda.so':
05:57:08: libcuda.so: cannot open shared object file: No such file or
05:57:08: directory
05:57:08: OpenCL: Not detected: clGetPlatformIDs() returned -1001

05:57:09:Enabled folding slot 00: READY cpu:56
05:57:09:Enabled folding slot 01: READY gpu:0:TU102 [GeForce RTX 2080 Ti] M 13448
05:57:09:Enabled folding slot 02: READY gpu:1:TU102 [GeForce RTX 2080 Ti] M 13448
05:57:09:Enabled folding slot 03: READY gpu:2:TU102 [GeForce RTX 2080 Ti] M 13448
05:57:09:Enabled folding slot 04: READY gpu:3:TU102 [GeForce RTX 2080 Ti] M 13448
05:57:09:Enabled folding slot 05: READY gpu:4:TU102 [GeForce RTX 2080 Ti] M 13448
05:57:09:Enabled folding slot 06: READY gpu:5:TU102 [GeForce RTX 2080 Ti] M 13448
05:57:09:Enabled folding slot 07: READY gpu:6:TU102 [GeForce RTX 2080 Ti] M 13448
05:57:09:Enabled folding slot 08: READY gpu:7:TU102 [GeForce RTX 2080 Ti] M 13448
05:57:09:ERROR:No compute devices matched GPU #0 NVIDIA:8 TU102 [GeForce RTX 2080 Ti] M 13448. You may need to update your graphics drivers.
05:57:09:ERROR:No compute devices matched GPU #1 NVIDIA:8 TU102 [GeForce RTX 2080 Ti] M 13448. You may need to update your graphics drivers.
05:57:09:ERROR:No compute devices matched GPU #2 NVIDIA:8 TU102 [GeForce RTX 2080 Ti] M 13448. You may need to update your graphics drivers.
05:57:09:ERROR:No compute devices matched GPU #3 NVIDIA:8 TU102 [GeForce RTX 2080 Ti] M 13448. You may need to update your graphics drivers.
05:57:09:ERROR:No compute devices matched GPU #4 NVIDIA:8 TU102 [GeForce RTX 2080 Ti] M 13448. You may need to update your graphics drivers.
05:57:09:ERROR:No compute devices matched GPU #5 NVIDIA:8 TU102 [GeForce RTX 2080 Ti] M 13448. You may need to update your graphics drivers.
05:57:09:ERROR:No compute devices matched GPU #6 NVIDIA:8 TU102 [GeForce RTX 2080 Ti] M 13448. You may need to update your graphics drivers.
05:57:09:ERROR:No compute devices matched GPU #7 NVIDIA:8 TU102 [GeForce RTX 2080 Ti] M 13448. You may need to update your graphics drivers.

05:58:41:WU01:FS01:Starting
05:58:41:ERROR:WU01:FS01:Failed to start core: OpenCL device matching slot 1 not found, try setting 'opencl-index' manually

06:00:41:WU04:FS04:Starting
06:00:41:ERROR:WU04:FS04:Failed to start core: OpenCL device matching slot 4 not found, try setting 'opencl-index' manually

It sounds like a driver issue that or that you are missing some cuda packages.
You should at least be able to run this ``docker run --gpus all nvidia/cuda:10.0-base nvidia-smi
I had the  ERROR:WU01:FS01:Failed to start core: OpenCL device matching slot 1 not found, try setting 'opencl-index' manually error myself but it seems to just have resolved itself.
I have 2 different k8s clusters one with K80's and one with 1080s and 2080s and I'm having no issue so far with the images on the master branch at the time of writing this.
Here's a screenshot for one of the pods on the clusters with K80's

Though I have cuda installed locally on the nodes, that might be the issue for other that don't have it installed locally
Cuda Driver: https://developer.nvidia.com/cuda-downloads?target_os=Linux

I don't have any clusters with GPUs for testing this myself, but it I expect your theory is right @skandix - the nodes themselves will need cuda and/or GPU drivers installed. Otherwise any container is not going to be able to utilize the GPUs

I have these drivers installed on the nodes:
http://us.download.nvidia.com/XFree86/Linux-x86_64/435.21/NVIDIA-Linux-x86_64-435.21.run
We are running other software like jupyter notebooks utilizing GPUs which work fine.
CUDA needs to be included in the docker image, thus is not installed on the nodes.

When starting container with nvidia/cuda:10.0-runtime-ubuntu18.04 image:
root@foldingathome-6ddd455-pk8kz:/# nvidia-smi
Tue Mar 31 19:08:13 2020
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 435.21       Driver Version: 435.21       CUDA Version: 10.1     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce RTX 208...  Off  | 00000000:1A:00.0 Off |                  N/A |
| 30%   26C    P8     1W / 250W |     10MiB / 11019MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce RTX 208...  Off  | 00000000:1B:00.0 Off |                  N/A |
| 31%   29C    P8     2W / 250W |     10MiB / 11019MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce RTX 208...  Off  | 00000000:1F:00.0 Off |                  N/A |
| 31%   24C    P8    17W / 250W |     10MiB / 11019MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce RTX 208...  Off  | 00000000:20:00.0 Off |                  N/A |
| 31%   26C    P8    15W / 250W |     10MiB / 11019MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   4  GeForce RTX 208...  Off  | 00000000:21:00.0 Off |                  N/A |
| 30%   28C    P8    16W / 250W |     10MiB / 11019MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   5  GeForce RTX 208...  Off  | 00000000:22:00.0 Off |                  N/A |
| 32%   29C    P8    15W / 250W |     10MiB / 11019MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   6  GeForce RTX 208...  Off  | 00000000:23:00.0 Off |                  N/A |
| 30%   30C    P8    22W / 250W |     10MiB / 11019MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   7  GeForce RTX 208...  Off  | 00000000:24:00.0 Off |                  N/A |
| 31%   30C    P8    16W / 250W |     10MiB / 11019MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+

@skandix Do you think it would help to switch the base docker image from nvidia/opencl:runtime-ubuntu18.04 to nvidia/cuda:10.0-runtime-ubuntu18.04 ?
I'm not sure what the difference is between opencl and cuda, but maybe this images includes more compatible libraries?

@richstokes  I can make the edit and build a new image and see how that works.
@danielxolsson I have cuda toolkit installed as well as these drivers. nvidia-headless-440 nvidia-compute-utils-440 nvidia-utils-440
Running on Ubuntu 18.04.3 (pulled all drivers from ubuntu repo's and installed cuda toolkit with the instructions found here )

Built a new docker image based on nvidia/opencl:runtime-ubuntu18.04 and still get following error:
06:03:29: OpenCL: Not detected: clGetPlatformIDs() returned -1001
<snip>
06:05:16:WU01:FS01:Starting
06:05:16:ERROR:WU01:FS01:Failed to start core: OpenCL device matching slot 1 not found, try setting 'opencl-index' manually
06:05:22:WU02:FS02:Starting
06:05:22:ERROR:WU02:FS02:Failed to start core: OpenCL device matching slot 2 not found, try setting 'opencl-index' manually

However this is gone:
05:57:09:ERROR:No compute devices matched GPU #0 NVIDIA:8 TU102 [GeForce RTX 2080 Ti] M 13448. You may need to update your graphics drivers.
05:57:09:ERROR:No compute devices matched GPU #1 NVIDIA:8 TU102 [GeForce RTX 2080 Ti] M 13448. You may need to update your graphics drivers.

Got it working with following Dockerfile which is pushed to danielxolsson/fah-gpu:latest if @adrsamanta wants to try:
FROM nvidia/cuda:10.0-runtime-ubuntu18.04
ENV DEBIAN_FRONTEND noninteractive

RUN apt update && apt upgrade -y
RUN apt install wget -y

# just creating the doc dir for fahclient and moving supplied config.xml there as a "sample"
RUN mkdir -p /usr/share/doc/fahclient/
ADD config.xml /usr/share/doc/fahclient/sample-config.xml

# Download/Install latest FAH client
# See here for latest - https://foldingathome.org/alternative-downloads/
RUN apt-get update && \
  wget https://download.foldingathome.org/releases/public/release/fahclient/debian-stable-64bit/v7.5/fahclient_7.5.1_amd64.deb && \
  dpkg -i --force-depends fahclient_7.5.1_amd64.deb && \
  rm fahclient*.deb && \
  apt-get autoremove -y && \
  apt install ocl-icd-opencl-dev nvidia-headless-440 nvidia-compute-utils-440 nvidia-utils-440 -y

# EXPOSE 7396 36396

ADD config.xml /etc/fahclient/config.xml

WORKDIR /var/lib/fahclient
CMD	["/usr/bin/FAHClient", \
	"--config", "/etc/fahclient/config.xml", \
	"--config-rotate=false", \
	"--gpu=true", \
	# "--run-as", "fahclient", \
	"--pid-file=/var/run/fahclient.pid"]

FAH only seems to utilize about 35% of the GPU:
I have no name!@fah-gpu-cpu-647c856656-jhjxf:/var/lib/fahclient$ nvidia-smi
Wed Apr  1 08:04:25 2020
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 435.21       Driver Version: 435.21       CUDA Version: 10.1     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce RTX 208...  Off  | 00000000:1A:00.0 Off |                  N/A |
| 31%   50C    P2    85W / 250W |    323MiB / 11019MiB |     38%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce RTX 208...  Off  | 00000000:1B:00.0 Off |                  N/A |
| 32%   32C    P8     8W / 250W |     10MiB / 11019MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce RTX 208...  Off  | 00000000:1F:00.0 Off |                  N/A |
| 32%   24C    P8    13W / 250W |     10MiB / 11019MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce RTX 208...  Off  | 00000000:20:00.0 Off |                  N/A |
| 32%   48C    P2    87W / 250W |    225MiB / 11019MiB |     32%      Default |
+-------------------------------+----------------------+----------------------+
|   4  GeForce RTX 208...  Off  | 00000000:21:00.0 Off |                  N/A |
| 32%   48C    P2    68W / 250W |    197MiB / 11019MiB |     31%      Default |
+-------------------------------+----------------------+----------------------+
|   5  GeForce RTX 208...  Off  | 00000000:22:00.0 Off |                  N/A |
| 32%   28C    P8    18W / 250W |     10MiB / 11019MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   6  GeForce RTX 208...  Off  | 00000000:23:00.0 Off |                  N/A |
| 33%   53C    P2    79W / 250W |    225MiB / 11019MiB |     34%      Default |
+-------------------------------+----------------------+----------------------+
|   7  GeForce RTX 208...  Off  | 00000000:24:00.0 Off |                  N/A |
| 32%   28C    P8     7W / 250W |     10MiB / 11019MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

I'll give that a try @danielxolsson thanks.
I should have the drivers installed on my nodes, I'm running this on a GKE cluster though so I'm using their installed drivers.

@danielxolsson I've been running a Dockerfile with only cuda for the last few hours and seeing that it doesn't work as well as it did with, with both opencl and cuda.
However, I will say that installing gpu drivers inside the dockerfile isn't a long term solution aswell you should have the drivers installed on the host system.  The dockerfile should have cuda-toolkit included and not drivers as these is supposed to be on the system itself.  I will make a new build and test it out today.

I do have the drivers installed on the host system. But now I might have some kind of combo if drivers are installed in any of following packages:
nvidia-headless-440 nvidia-compute-utils-440 nvidia-utils-440

@danielxolsson Your new docker file did the trick. I'm not going to close the issue, as @skandix said this isn't a great long term solution, but at least I've got it working for now.

I've made a new dockerfile, things seems to work as they should now with both opencl and cuda support. I'm testing it for a few hours before i make the pull request @richstokes

@adrsamanta @danielxolsson have you tried out the new built image ?

I am having issues with the cuda drivers and the k80, see below...  It seems related to this..
17:12:28:Enabled folding slot 00: READY cpu:30
17:12:28:Enabled folding slot 01: READY gpu:0:GK110 [Tesla K80]
17:12:28:Enabled folding slot 02: READY gpu:1:GK110 [Tesla K80]
17:12:28:ERROR:No compute devices matched GPU #0 NVIDIA:3 GK110 [Tesla K80].  You may need to update your graphics drivers.

@jsloyer i have a cluster running with multiple k80s, with @richstokes latest image running with No problem,have you tried that?

It looks like things are working fine with the latest richstokes image

then hopefully you would like to use that instead :), it fixed the issues a bit better than just installing new pair of drivers inside the dockerfile as what was @danielxolsson temp fix... @richstokes maybe close this issue now or ?

Yep, I think so :-) thanks guys


After making any changes to existing backup targets(add/delete) , no backup targets are listed in "Create Backup" page.

Rancher Version: Build from master
Steps to reproduce the problem:
Add a backup target.
Added target shows up in the backup target list.
Launch Storage->pool-> Pick a snapshot and do "Backup Snapshot" on it.
No backup targets are listed in "Create Backup" page.
We need to "cancel" this page and refresh  Storage->pool page , after which we see the backup target being listed in the  "Create Backup" page.
Add another backup target , so u have 2 targets now.
Launch Storage->pool-> Pick a snapshot and do "Backup Snapshot" on it.
No backup targets are listed in "Create Backup" page. Even the 1st target does not get listed.
Once we refresh  Storage->pool page we see both the backup target being listed in the  "Create Backup" page.

Tested with UI - v1.1.6 . There is no need for manual refresh for the newly added targets to show up in the "Create Backup" page.


Update IP from xip to nip

cc @DomFleischmann

Nice catch! Fixed

/retest

/test all

/test kubeflow-website-link-check

The tests are failing and automation to relaunch seems not to be working..
I'll make another PR.
@Bobgy @joeliedtke do you know if we should fix the test triggers? Or is it working and I am simply not finding the right command? :)

/close


fix typescript 'sourceMap' compiler option must be set

Running yarn build complains with:
(!) Plugin typescript: @rollup/plugin-typescript: Typescript 'sourceMap' compiler option must be set to generate source maps.

even when tsconfig.json has "sourceMap": true.
btw, source maps are still built, but they seem incorrect :/

seems to be fixed with the latest rollup-plugin-svelte ^7.0.0


axios-cache-adapter causes leaks in unit tests when running jest with --detect-leaks

This took a while to track down - we're seeing issues with the performance of tests in our monorepo when running in the CI, and after some investigation using the --detect-leaks flag in jest, I've identified that the leaks are occurring in our use of the axios-cache-adapter package.
Repository to reproduce this issue:
https://github.com/ahayes91/TestTimeouts

https://github.com/ahayes91/TestTimeouts/pull/2 shows that the leak is removed when running yarn workspace @test/parentApp test --detect-leaks if the cache functionality is commented from the functional code
https://github.com/ahayes91/TestTimeouts/pull/3 shows that the leak is removed for the App.integration.test.js file if the axios-cache-adapter module is mocked in the test file (you can run yarn jest PATH_TO_FILE --detect-leaks to test this one individually)

Can we find out what code in the module is causing the leakage & fix it / have you seen this before?
Can you advise on how best to mock the module globally for unit tests without having to put jest.mock in every test file? https://jestjs.io/docs/en/manual-mocks didn't seem to work for me, even when I put the manual mocking file in a __mocks__ directory beside the root level node_modules and in a __mocks__ directory beside the package level node_modules.

Edit: I've updated our jest config to load the mock in the setupFilesAfterEnv step:
// mockAxiosCache.js
/* eslint-disable no-undef */
jest.mock('axios-cache-adapter', () => {
  return {
    setupCache: jest.fn().mockReturnValue({ adapter: 'mockAdapter' }),
  };
});

// jest.config.js
...
setupFilesAfterEnv: [
    '@testing-library/jest-dom/extend-expect',
    './mockAxiosCache.js',
  ],
...

Hello @ahayes91
Thank you for this investigation and for uncovering this leak issue. I've been away for a while (as you probably noticed).
I will look into this as soon as I can.
Cheers


When removing "INSDC sample accession" field's value the field got an empty string value

Steps to reproduce:

Go to Ingest UI
Select a submission with Archiving status
Edit one of the biomaterial and remove the value from the INSDC sample accession field
Save the biomaterial
Click on the ingest api url and check the JSON.

Expected behaviour:
There should not be a field inside biomaterial_core with a key insdc_sample_accession.
Actual behaviour:
There is a field inside biomaterial_core with a key insdc_sample_accession and its value is: "" (an empty string).
The biomaterial also gets a validation error: .biomaterial_core.insdc_sample_accession : should match pattern "^[DES]RS[0-9]+$"

to verify if this is the same issue : https://embl-ebi-ait.slack.com/archives/C016R78CDV1/p1644502236844049


docs: fix typos

Found via codespell -S .mypy_cache -L bu,fo,nd,onw,ore,te,hould,ect

@kianmeng can you please change you branch from master to develop?

@fabclmnt Done.

:partying_face: :partying_face: :partying_face: :partying_face: :partying_face:


Mahdi Aryayi / Fixed CFD risk value

Description
Changed CFD risk value from 74% to 71% and changed some contents in the footer.
Changes:

Changed CFD risk from 74% to 71%

Changed some content in the footer

...

Type of change

[x] Bug fix
[ ] New feature
[ ] Update feature
[ ] Refactor code
[ ] Translation to code
[ ] Translation to crowdin
[ ] Script configuration
[ ] Improve performance
[ ] Style only
[ ] Dependency update
[ ] Documentation update
[ ] Release

please change the base for this to crowdin

I changed the base branch

please change the base for this to crowdin

I changed the base branch


Question on howto use "fmt"

(I'm a ocaml newbie)
I try to test the "fmt" module and ran into a problem. While "pam install fmt" seems to succeed, I cannot load it open Fmt;; :  Error: Unbound module Fmt.
I tried to run the test/test.ml example but I dont really know howto compile it.
$ocamlc test.ml
File "test.ml", line 23, characters 34-48:
Error: Unbound module Fmt

Please ask these questions on https://discuss.ocaml.org/ where people are willing to help newcomers. Also formulate them with a little bit more details about the context.
Presumably you are trying to do this from the ocaml (or utop) toplevel. This should do:
#use "topfind"
#require "fmt"

In the REPL I can use "#require "fmt" however when using ocamlc the modules is not found.

Try something like ocamlfind ocamlc -package fmt yourfile.ml but please continue that discussion on discuss.ocaml.org.

ok thanks

Sorry, just one more comment. I now tried "pkg/pkg.ml build" and copied the _build/src/* to ".opam/default/lib/fmt/" and then I can run "open Fmt;;". Seems to be some incompatibility of the opam binary files of fmt....

Don't do these things... and also what you inferred doesn't make any sense.

Here's a small tutorial to compile things by hand and use libraries. But please these questions are OT for this issue tracker,  ask these questions on discuss.ocaml.org where it might benefit other newcomers aswell.


Crash fixed; equipment and consumbable icons now should load properly

More proper fix of #39

You can download compiled release from fork's one:
https://github.com/L11R/tankinspector/releases


Adding jhaddix DNS entries file.

Added JHaddix file from gist to repo under Discovery/DNS path.
This pull request addresses issue https://github.com/danielmiessler/SecLists/issues/184

Pinging @g0tmi1k for visibility since he created the issue in the first place.

Looks great to me!
Merging


⚠ Fortnite has degraded performance

In 72d3fce, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1603 ms

Resolved: Fortnite performance has improved in 2a58ade.


Right-hand rule polygons not followed with most recent matplotlib versions

Hello from Norway !
It looks like, since matplotlib 3.8.?, the geojson files computed with geojsoncontour are not always following the right-hand rule. This was probably taken care of by matplotlib before, but recent release notes suggest some "revert contour" deprecation.

https://pypi.org/project/geojson-rewind/ seems to be able to rewind geojson polygons. Could be used to fix this, or provide tips on how to fix this.

When using geojsoncontour.contour_to_geojson on contours created by plt.contour from matplotlib>=3.8.0, different isolines (with same values) were are connected together:

After downgrading to matplotlib==3.7.3, the output from geojsoncontour.contour_to_geojson is normal again:

They are some breaking changes concerning contourf method in the 3.8 release of matplotlib
https://matplotlib.org/stable/api/prev_api_changes/api_changes_3.8.0.html#contourset-is-now-a-single-collection

When using geojsoncontour.contour_to_geojson on contours created by plt.contour from matplotlib>=3.8.0, different isolines (with same values) were connected together for my usecase:

After downgrading to matplotlib==3.7.3, the output from `geojsoncontour.contour_to_geojson` is normal again:

I made a fix for it, here is my PR #26
Matplotlib still allows you to have an access to each closed contour in contour.allsegs field, while contour.get_paths() contains a single Path for each level. I understand, there is a room for improvement, maybe it's better to get only one feature for every level instead of one feature for each closed contour.


There is no need to generate the gRPC code

YugabyteDB goes not use gRPC. It uses the Hadoop RPC variation which relies on protobuf sent over regular TCP connection. More details here: https://github.com/yugabyte/yugabyte-db/blob/v2.7.2/src/yb/rpc/README.
As such, it is not worth generating gRPC code because it is not used by the client anyway. This library will not generate gRPC code for YugabyteDB versions 2.7.3+.

The decision is now reverted due to the: https://github.com/radekg/yugabyte-db-go-client/pull/16#issuecomment-907672188.


fix(ng-update): properly handle update from different working directory

In some situations, developers will run ng update from a sub directory
of the project. This currently results in a noop migration as file
system paths were computed incorrectly. This is because ng-update
always assumed that the CWD is the workspace root in the real file
system. This is not the case and therefore threw off path resolution.
We can fix this by determining the workspace file system path from
the virtual file system host tree's. This is not ideal, but best
solution for now until we can parse/resolve TypeScript projects
purely from within the virtual file system. This is currently
not easy to implement and requires helpers from TS which are
not exposed yet. See: https://github.com/microsoft/TypeScript/issues/13793.
This is tracked with: COMP-387.
Fixes #19779.

Thanks for reviewing. I went ahead and made the long-term changes that we need anyway in framework too, rather than fiddling more with the non-ideal tricks to get the TS compiler API work for schematics. See: #19934


Version Compatibility

Describe the feature you would like to see
It would be great if a minimum release version could be included in the main README.
I have a production server on PHP 7.2 and I don't know whether release 5.19.0 of firebase-php, which is the latest version that is compatible with v7.2, will work with the Firebase api.
Does anyone know whether 5.19.0 still works?
Thanks.

Thanks for bringing this up, it's a fantastic idea! I will add a supported versions table to the README.
Here's roughly what it will contain (I'm using this response as my initial draft, non-binding of course 😅).
I actively maintain (add features and fix bugs) only the latest version (currently 7.x). The latest version supports actively supported PHP versions (currently 8.1 and 8.2).
The previous version (currently 6.x) will receive security fixes as long as its PHP requirement receives security fixes. For 6.x, this means that security support ends on 2023-11-26.
I do not support and do not add features, restore broken functionality or bugfixes to other/older versions unless a request is from a GitHub sponsor with a certain $-tier, or attached with the offer to pay an invoice 😅. This will require the requester to agree that the implemented changes/additions are made available to the community.
I also do not provide free 1:1 support, especially not in non-public channels (that's not addressed to you, but I receive such emails quite often).
To come back to your original question: I don't support version 5.x anymore. The problem here is that I shouldn't have used such a wide PHP version constraint, that's why you're stuck with an old feature release of this old version.
That being said: Although older versions obviously have less features, they should (:tm:) work, unless Firebase has removed APIs.
I do, of course, recommend upgrading to a supported PHP version, but I also understand very well that this isn't always possible in (especially large, mostly commercial) legacy projects. In that case, I would point to the "Sponsor or Invoice" paragraph. This project is used in many, many commercial projects, and I don't have the resources for unpaid work.
I know you didn't expect such a long response with information you didn't ask for, but I hope for your understanding!

It's also very nice to have such a compatibility matrix for distributions packagers (like me), so, thanks for this :)

Thank you for making such a thorough response to my request.  Fortunately, my sysops has agreed to upgrade the PHP version on our production server. But in any case, I really appreciate the work that you are doing.
Grüß Gott!

The readme now includes a supported versions table, thanks again for your suggestion!


💡 scaffold .vscode/settings.json with checkJS enabled when creating repository

.vscode/settings.json
{
  "js/ts.implicitProjectConfig.checkJs": true
}

Do you think it could be intereting for users? Maybe making it optional under a prompt({type: "confirm"})?

How about we add
// @ts-check

to the first line of the script.js file? That will make it work for all editors that support it?
I also wonder if we should run the tsc --checkJs check with npx on CI, as part of the "test" step in test.yml? What do you think?

How about we add
// @ts-check

to the first line of the script.js file (docs)? That will make it work for all editors that support it?

I can give it a try but... this would leave responsibility to developers adding on each js file they create this comment and, with settings.json would be for every .js file by default right?

I can give it a try but... this would leave responsibility to developers adding on each js file they create this comment and, with settings.json would be for every .js file by default right?

yes, but that way we don't force yet another file on people, and they can enable / disable it as they like. Also not everyone is using VS Code, I don't want to add editor-specific settings. The alternative would be to add jsconfig.json, but I think I would prefer to just adding the // @ts-check for now. I think most scripts will be a single file anyway

Yes, you are right:
settings.json would be Specific to VS Code and we don't want to be close to it so in case we need to scaffold a configuration, would be better to be .editorconfig (if they support the js check part) or jsconfig.json

Tried in script-renovate-setup and it works fine to me so... I would say to go for this solution for the moment.

If you like the solution, I would create an Octoherd script to add //ts-check to script.js for already existing files in the org

Yes, let's add it to the npm init octoherd-script and create an @octoherd script that will add it to existing scripts that do not have it yet


Improve parsing of header fields

Here in cpr/util.cpp#L30-L37:

For Header:\r\n or Header: \n, the program asserts an error because value is empty.
For Header:\n, the program throws a std::out_of_range exception because of found + 2.

A real-life example would be GitHub returning X-Geo-Block-List:\r\n. There's also #127.
If the code I changed looks too cryptic, here's the expanded version:
auto found = line.find(":");
if (found != std::string::npos) {
    auto value = line.substr(found + 1);
    found = value.find_first_not_of("\t ");
    if (found != std::string::npos) {
        value.erase(0, found);
    }
    found = value.find_last_not_of("\t\n\r ");
    if (found != std::string::npos) {
        value.resize(found + 1);
    }
    header[line.substr(0, found)] = value;
}

Note that \n is not actually a part of line due to std::getline, but I included it in "\t\n\r " anyway in case the splitting method is changed in the future.
This also makes cpr more compliant with the specification. From what I understand:

\t is allowed as optional whitespace:
OWS            = *( SP / HTAB )
Leading/trailing OWS is insignificant and should not be a part of the field value:
header-field   = field-name ":" OWS field-value OWS

This looks good! I'm writing tests that capture this and will merge it in soon.


dark mode bug

in dark mode text navbar and many more things are not visible

in contact us dark mode is not available

@codervivek5 please assign me this issue


PHP API - empty response body

Hello,
about 2-3 weeks ago I was implementing SendGrid php api to my client. Back then when I was using:
$response = $client->client->contactdb()->recipients()->post([$request_body]);
I've received:
object(SendGrid\Response)[5]   public '_status_code' => int 201   public '_body' => string '{"error_count":0,"error_indices":[],"new_count":0,"persisted_recipients":["bS5waWV0cmFzekBuZXVyb3N5cy5wbA=="],"unmodified_indices":[0],"updated_count":0}' (length=153)   public '_headers' => string 'HTTP/1.1 201 CREATED Server: nginx ... ...
this was on version 5.0.9.
Right now in 5.1.1 I receive this:
/home/michal/sendgrid/lib/SendGridHelper.php:76: object(SendGrid\Response)[5]   protected 'statusCode' => int 201   protected 'body' => boolean false   protected 'headers' =>      array (size=1)       0 => string '1' (length=1)
as you can see the response body is empty. But weird is that I can catch proper body with this code:
ob_start(); $response = $client->client->contactdb()->recipients()->post([$request_body]);         $curl_response = ob_get_contents();
so in my $curl_response variable I would have this:
{"error_count":0,"error_indices":[],"new_count":0,"persisted_recipients":["bS5waWV0cmFzekBuZXVyb3N5cy5wbA=="],"unmodified_indices":[0],"updated_count":0}
Please fix this bug because right now I need to use old version :)

Hi @madara84,
Thanks for letting us know and for providing a detailed issue!
I've added this to our backlog for a fix.

could you give me an estimation time when it will be fixed on master branch ?

Hi @mpietraszneurosys,
It does not look like this would get fixed this quarter unless we get more people voting on this issue or if someone submits a pull request.

@mietraszneuo
Quick Fix:
Edit sendgrid's Client.php and add the following lines :
    curl_setopt($curl, CURLOPT_RETURNTRANSFER, true);
    curl_setopt($curl, CURLOPT_HEADER, true);
    curl_setopt($curl, CURLOPT_CUSTOMREQUEST, strtoupper($method));
    curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, false);

After the following line:
    curl_setopt($curl, CURLOPT_HTTPHEADER, $this->headers);

in makeRequest function.

I encountered the same problem.  @vsmori 's solution works.

Same issue here, @vsmori 's solution worked as well. Please address.

Thanks for sharing your solution @vsmori. Please fill out this form so we can send you some swag :)
@haibo3318, @cballenar,
Thanks for your votes, I've added them to our backlog.

@thinkingserious , please send again the form.

@vsmori, sorry about that, here it is.

I am also seeing this issue.  The above worked for me.

Stop turning off CURLOPT_SSL_VERIFYPEER and fix your PHP config
Disabling verification of the certificate allows bad guys to man-in-the-middle the communication without you knowing it. Disabling verification makes the communication insecure. Just having encryption on a transfer is not enough as you cannot be sure that you are communicating with the correct end-point.
References :
https://snippets.webaware.com.au/howto/stop-turning-off-curlopt_ssl_verifypeer-and-fix-your-php-config/
https://curl.haxx.se/libcurl/c/CURLOPT_SSL_VERIFYPEER.html
Remove this setting by default and let unsecure users to turn it off with a configuration.
if ($this->disableSSLVerifyPeer) {
  curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, false);
}

Thanks for the feedback @ylupien,
I have added your vote.

For clarity, is this a new BUG introduced in 5.1.1 (I never had an issue prior to this)?
If @vsmori solution has a security flaw, what is the recommended approach, revert to a previous version?
Many thanks

@birdy247,
I suggest you use the previous version until we have time to investigate deeper.

Isn't this all related to #328, #333 and the fact that the cURL PHP module missing CA certificates so by default it will reject all SSL certificates as unverifiable?

Is there any update on this?

Hi @birdy247,
It's still fairly low on our backlog. The only thing that would give this issue a significant bump in priority would be a PR.
With Best Regards,
Elmer

Hello Everyone,
Please follow progress at this thread: https://github.com/sendgrid/sendgrid-php/issues/321

Hi ,
I'm geting this response on the clinet server when run the code. But on local its working fine and laos show log in activity on send grid. But when put code on client server and test it give this response and email goes. But not showing in activity log
Thanks To  All
SendGrid\Response Object
(
[statusCode:protected] => 0
[body:protected] =>
[headers:protected] => Array
(
[0] =>
)
)

@siwach22,
Please review this this thread: https://github.com/sendgrid/sendgrid-php/issues/348
Thanks!

I was facing the same problem and spent a couple of figuring out and set the CURLOPT in Client.php of sendGrid API.
I have set CURLOPT_SSL_VERIFYPEER => to false instead of true

I hope this may help others to a void getting the 0 status code.


added Gen ZZ or WW information to from gen_selection_dict to skimmer…

… for extrapolation purposes.

Thanks for looking into this! It looks the information we need was already being saved with the GenHiggsChildren variable, so I don't believe we need to add the individual booleans. Sorry about that.


[SPARK-46375][DOCS] Add user guide for Python data source API

What changes were proposed in this pull request?

This PR adds a new user guide for the Python data source API with a simple example. More examples (including streaming) will be added in the future.
Why are the changes needed?

To improve the documentation
Does this PR introduce any user-facing change?

No
How was this patch tested?

doctest
Was this patch authored or co-authored using generative AI tooling?

No

Merged to master.


rnn/translate: IOError: [Errno 2] No such file or directory: '/mnt/tf1/translate/giga-fren.release2.fr.gz'

Environment info
Operating System:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.4 LTS
Release:    14.04
Codename:   trusty

Installed version of CUDA and cuDNN:
(please attach the output of ls -l /path/to/cuda/lib/libcud*):
NONE
If installed from binary pip package, provide:

A link to the pip package you installed:
The output from python -c "import tensorflow; print(tensorflow.__version__)".
$ python -c "import tensorflow; print(tensorflow.__version__)" 0.10.0rc0

If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)
$ cd tensorflow/tensorflow/models/rnn/translate/
$ python translate.py --data_dir /mnt/tf1/translate
Preparing WMT data in /mnt/tf1/translate
Downloading http://www.statmt.org/wmt10/training-giga-fren.tar to /mnt/tf1/translate/training-giga-fren.tar
Succesfully downloaded training-giga-fren.tar<PHONE_NUMBER> bytes
Extracting tar file /mnt/tf1/translate/training-giga-fren.tar
Unpacking /mnt/tf1/translate/giga-fren.release2.fr.gz to /mnt/tf1/translate/giga-fren.release2.fr
Traceback (most recent call last):
  File "translate.py", line 290, in <module>
    tf.app.run()
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/platform/app.py", line 30, in run
    sys.exit(main(sys.argv))
  File "translate.py", line 287, in main
    train()
  File "translate.py", line 147, in train
    FLAGS.data_dir, FLAGS.en_vocab_size, FLAGS.fr_vocab_size)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/models/rnn/translate/data_utils.py", line 265, in prepare_wmt_data
    train_path = get_wmt_enfr_train_set(data_dir)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/models/rnn/translate/data_utils.py", line 83, in get_wmt_enfr_train_set
    gunzip_file(train_path + ".fr.gz", train_path + ".fr")
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/models/rnn/translate/data_utils.py", line 68, in gunzip_file
    with gzip.open(gz_path, "rb") as gz_file:
  File "/usr/lib/python2.7/gzip.py", line 34, in open
    return GzipFile(filename, mode, compresslevel)
  File "/usr/lib/python2.7/gzip.py", line 94, in __init__
    fileobj = self.myfileobj = __builtin__.open(filename, mode or 'rb')
IOError: [Errno 2] No such file or directory: '/mnt/tf1/translate/giga-fren.release2.fr.gz'
ubuntu@ip-10-169-182-86:~/tensorflow/tensorflow/tensorflow/models/rnn/translate$ ls /mnt/tf1/translate/training-giga-fren.tar

$ ls -l /mnt/tf1/translate/training-giga-fren.tar
-rw-rw-r-- 1 ubuntu ubuntu<PHONE_NUMBER> Aug 31 10:53 /mnt/tf1/translate/training-giga-fren.tar

What other attempted solutions have you tried?
$ python translate.py --data_dir /mnt/tf1/translate
Preparing WMT data in /mnt/tf1/translate
Extracting tar file /mnt/tf1/translate/training-giga-fren.tar
...(same error)

$ ls -l /mnt/tf1/translate/
total 5073524
-rw-rw-r-- 1 ubuntu ubuntu<PHONE_NUMBER> Aug 30 19:55 giga-fren.release2.fixed.en.gz
-rw-rw-r-- 1 ubuntu ubuntu<PHONE_NUMBER> Aug 29 21:43 giga-fren.release2.fixed.fr.gz
-rw-rw-r-- 1 ubuntu ubuntu<PHONE_NUMBER> Aug 31 10:53 training-giga-fren.tar

Logs or other output that would be helpful
(If logs are large, please upload as attachment or provide link).

Same happens for giga-fren.release2.en.gz, so I have partially solved it by symlink
ubuntu@ip-10-169-182-86:/mnt/tf1/translate$ ls -l
total 9536168
lrwxrwxrwx 1 ubuntu ubuntu         30 Aug 31 15:17 giga-fren.release2.en.gz -> giga-fren.release2.fixed.en.gz
-rw-rw-r-- 1 ubuntu ubuntu<PHONE_NUMBER> Aug 30 19:55 giga-fren.release2.fixed.en.gz
-rw-rw-r-- 1 ubuntu ubuntu<PHONE_NUMBER> Aug 29 21:43 giga-fren.release2.fixed.fr.gz
-rw-rw-r-- 1 ubuntu ubuntu<PHONE_NUMBER> Aug 31 15:15 giga-fren.release2.fr
lrwxrwxrwx 1 ubuntu ubuntu         30 Aug 31 15:13 giga-fren.release2.fr.gz -> giga-fren.release2.fixed.fr.gz
-rw-rw-r-- 1 ubuntu ubuntu<PHONE_NUMBER> Aug 31 10:53 training-giga-fren.tar

In tensorflow/models/rnn/translate/data_utils.py  line 76

train_path = os.path.join(directory, "giga-fren.release2")

train_path = os.path.join(directory, "giga-fren.release2.fixed")

Ideal solution is that someone hosts the file that won't change it.  Not sure what else is different besides file name.

I don't know if this error is related to the new files, but when I try to run it, with the new files hosted at statmt.org. The program fails when trying to train.
reading data line 13900000
reading data line 14000000
reading data line 14100000
reading data line 14200000
reading data line 14300000
reading data line 14400000
ubuntu@ip-10-147-46-5:~/tensorflow/tensorflow/models/rnn/translate$

I don't think this is tensorflow problem.
the files inside training-giga-fren.tar have been renamed:
After extracting you get this error:
IOError: [Errno 2] No such file or directory: ...
ls into the folder of the data downloaded, in the default example it's /tmp/ and what you will see is this:
giga-fren.release2.fixed.en.gz
giga-fren.release2.fixed.fr.gz
training-giga-fren.tar
...

Next, try doing this:
mv /tmp/giga-fren.release2.fixed.fr.gz /tmp/giga-fren.release2.fr.gz
mv /tmp/giga-fren.release2.fixed.en.gz /tmp/giga-fren.release2.en.gz
Which will recorrect name of the files into (giga-fren.release2.en or giga-fren.release2.fr) rather than the one with fixed.
re turn the python translate and bam it works now 😄

pull requests are welcome!

In the tensorflow-0.10.0rc0 release, changing line 76 by adding '.fixed' in data_utils.py doesnt work. Instead creating the soft link for giga-fren.release2.fixed.en.gz  and giga-fren.release2.fixed.fr.gz  in the data_dir works as of today.

Hello everyone,
I executed the code translate.py from sequence to sequence models tutorial of tensorflow 60 hours ago and still waiting for the output.
Can anyone tell me how much more time will it take to display the output
System specifications:
I installed Ubuntu 16.04 on VMware with a disk space of 100

GB and RAM of 1 GB.

Automatically closing due to lack of recent activity. Since this issue is old at this point, please reopen the issue if it still occurs when tried with the latest version of Tensorflow. Thank you.


[ENH] Add mypy to CI build

PR Description
Please describe the changes proposed in the pull request:

Adds mypy to CI build.
Fixes a number of issues identified by mypy inside the codebase.

This PR resolves #332.
Relevant Reviewers
Please tag maintainers to review.

@zbarry

Btw, that long list of commits is prob from not rebasing 👀

Yeah, I should have rebased haha.

That said, now that I've enforced only squash + merge, the commit history on dev should become much, much cleaner.

@zbarry @szuckerman one thing about the CI system is that it's designed to catch things we definitely want to pass before merging.
For now, pyjanitor's list includes:

code formatting
tests
test coverage

From my observations last sprint at PyCon, it's a great library for newcomers to learn:

Git workflow
Writing tests
Writing good docstrings
Other best practices.

So my big question here is: Should we enforce docstyle, type annotations, and other good practices, both for consistency and to help this package also be a great pedagogical experience for newcomers to build up good practices?
I think for a newcomer at sprints, it could be great to put in the effort surrounding one really nice PR that incorporates all of the good practices enforced. The downside here is that without the experience of in-person guidance, it's much harder for remote sprinters to get involved. That would make this less beginner-friendly, as you rightly mention, @zbarry.

We do have a lot of good examples in the form of other functions for users to model their contributions off of, so that helps a bit. Maybe we could make a really nice skeleton function and skeleton unit tests for things like confirming exceptions are raised to lower the barrier a bit.

Note for myself: the last thing left to do is to add mypy checking into the Azure pipeline.

You decide to not integrate this, or you working on a different approach now?

I realized I wasn't sure what I think we need to check. Let's take the discussion back to the Issue Tracker.

🚀


Clarify Size() method

Clarify that Array.size() only counts non-NULL elements within an array

This is not what size() does. What size() returns is the number of "cells" in the array. The doc said "number of elements in the array", but null is also counted as an element.
Example:
var a = [null, null, null]
print(a.size())

Prints 3.

@Zylann is correct, Array.size() does take into account null elements.


ng-golang-http-80-q13117-20190613-02 to 0.0.2

Promote ng-golang-http-80-q13117-20190613-02 to version 0.0.2

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


[UI] Issue in Selection in Navigation Menu

Current Behavior
Currently, when an option in the navigation bar is selected, it remains highlighted even if another option is subsequently chosen.
Desired Behavior
The desired functionality is that when an option is clicked, it should remain highlighted only until a different option is selected.
Screenshots/Logs

Environment

Browser: Chrome Edge Firefox
Host OS: Linux
Meshery Server Version: stable-v
Meshery Client Version: stable-v
Platform: Kubernetes

Contributor Guides and Handbook

🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🖥 Contributing to Meshery UI
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

I fixed the issue sending it in the next pr

@saurabh100ni @Jougan-0 I think there is some miscommunication....As far as I checked, there was no issue related to navigation and I confirmed it from @leecalcote....he told me to raise the issue. So I would like to work on it.

@suzy-g38  i am sorry didn't knew the issue was not assigned so i thought it was open so sent the fix @leecalcote can you please help us out

@suzy-g38 as you can see in the image the submenu is not closing once you click on other option so the issue was in toggle

@suzy-g38 i am sorry didn't knew the issue was not assigned so i thought it was open so sent the fix @leecalcote can you please help us out

@Jougan-0  it's okay....as you have already raised the pr so it's fine.

@suzy-g38  , @Jougan-0   please guyz ,  only work on  the issues that are assigned to you . this prevents  potential conflicts and back and forth .   We assign issues on first come first serve basis so all you need is to comment and wait till a maintainer assigns it to you .
While you wait for getting a issue assigned , you can add your valuable feedback and reviews on open pr's . it counts as a worthy contribution and no permission needed there  .

@saurabh100ni  //

@aabidsofi19 it's my fault i knew but didn't asked I'll ask and wait for the issue to be assigned I am sorry @aabidsofi19

@suzy-g38 , @Jougan-0 please guyz , only work on the issues that are assigned to you . this prevents potential conflicts and back and forth . We assign issues on first come first serve basis so all you need is to comment and wait till a maintainer assigns it to you .
While you wait for getting a issue assigned , you can add your valuable feedback and reviews on open pr's . it counts as a worthy contribution and no permission needed there .

Okay got it....thanks @aabidsofi19

Thanks for your sincerity ,  guys .  There are lots of open issues to chew through 😉


Panel Version
1.0.0-beta3
Wings Version
1.0.0-beta3
Service
proxy/velocity
Modified
No, I did not modify the egg
Expected Behavior
When I run the server, the config in the velocity.toml file should change the bind_address value to "<IP_ADDRESS>:{{SERVER_PORT}}" as its specified in its Configuration Files field:
{
    "velocity.toml": {
        "parser": "file",
        "find": {
            "bind = ": "bind = \"<IP_ADDRESS>:{{server.build.default.port}}\""
        }
    }
}

Actual Behavior
Instead, every time I run my server the bind_address value changes to:
bind = "<IP_ADDRESS>:"

Steps To Reproduce

Create a Velocity Server on your panel
Start the server
Now the server will run on port 25565 or 25577, because its the default port that velocity applies to your server. Even if you try to manually edit the velocity.toml file to replace the port, every time you restart the server the bind_address gets replaced again with the wrong port.

Install logs
https://pteropaste.com/8kw6

Every time I said bind_address value I meant the bind value, I just confused.

Please read the discord announcement for that. Its broken, we know.

oh sorry


Switch from Grunt to Gulp

https://github.com/yeoman/generator-chrome-extension

Or remove Grunt completely 😉

Grunt was removed in https://github.com/asciidoctor/asciidoctor-chrome-extension/pull/173


Updating payment method/mandate

Provide a convenient helper method for updating the payment method/mandate.

A must have! It would be useful to handle retries for failed payment too

+1

+1 from me too. Is this possible in v2?

Yes it will be available on v2


Escape OR pipe in table

Use HTML escaping as a workaround.
Markdown parser does not handle pipes inside table cells correctly.

@jorgebay,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


Font changed for Web pages, but not for UI

As title, I changed the font but it's only apparent in Web pages, and non of the system UI has changed. I have the stock font in all my settings, keyboard etc.
Running an OPO on CM11

Any reason for closing it? Has it been fixed?

Nevermind, I see why it's not been fixed. And I doubt you'll fix it.
Just tried on v2.2 and UI fonts are still not working.
Gonna try someone else's app.

Sorry I assumed that I had fixed the issue after the full rewrite of the app.
Does the installation of the font go through without any errors? Could you get a log of the app during an installation. Thanks.

I updated to v2.3, and still not working.
The font downloaded fine, installed fine and when I rebooted, the font in the browser had changed (so on a website, like facebook.com, the font was different) but the UI font hadn't changed,
Changing the font with CM theme engine worked.
But I have just updated to Lollipop now, so I may not be able to get you the logs you need.


migration issue

https://github.com/pgjones/quart-db/blob/2f597a2187484dc085c147509afe553ecb1f5cc4/src/quart_db/extension.py#L148
is this meant to divide 2 strings or create a path?

See pathlib


Add workarounds for colocation with os-conf ca_certs job for issue #71

As noted in #71, here is a hacky patch for discussion.

Thanks, @DennisDenuto! Actually, I think that's a much cleaner solution. It doesn't quite stick with the spirit of what should be done during start versus pre-start, but addresses the problem and is much less of a hack. I'll update this PR with this proposed idea instead of a sleep statement.

Went ahead and updated PR to move the cert manipulation to the start section of uaa_ctl

@DRuggeri thanks for the updated PR. we have added a chore for someone on the team to review this PR.

How about this pull request? I suffer from exactly the same issue as mentioned in https://github.com/cloudfoundry/uaa/issues/766

We have made some additional commits to address this issue.
see https://github.com/cloudfoundry/uaa-release/commit/61ae508f5344bd31322d6301379e4320540180bb
There were concerns with the process cert timing out the uaa job. Therefore if uaa is being deployed without os-conf then the certs will continue to be loaded during pre-start. However if os-conf is co-located and there is a race condition where os-conf loads the ca certs after the uaa pre-start job has run, then during the start lifecycle, every certificate will be reloaded (including the certs from the os-conf job)


Brigandyne-V2 First commit

Character Sheet Info Roll20 Internal Use only.

Submission Checklist
Required
[x ] The pull request title clearly contains the name of the sheet I am editing.
[x ] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x ] The pull request makes changes to files in only one sub-folder.
[x ] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)
New Sheet Details
The name of this game is: < Brigandyne > (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)
The publisher of this game is: < independent > (i.e. Wizards of the Coast, Evil Hat)
The name of this game system/family is: < none > (i.e. Dungeons & Dragons, FATE)
[x ] I have followed the Character Sheets Standards when building this sheet.
This sheet has been made on behalf of, or by, the game's publisher.
[x ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at:
https://www.lulu.com/fr/shop/james-tornade/brigandyne-2e-édition-livre-premier-pdf/ebook/product-q96zwz.html?q=&page=1&pageSize=4


Question(Hosting)

Hey, im just wondering whats the best way to host this bot to be online 24/7. I cant host it on repl.it, because it contains ctypes module that is made for windows and repl is linux based. Thank you!

Hey, im just wondering whats the best way to host this bot to be online 24/7. I cant host it on repl.it, because it contains ctypes module that is made for windows and repl is linux based. Thank you!

ctypes is just to set the console title of it, it's not a crutial part of the code so if you want torun it on linux, remove that part where it set the console title and you are fine. for the hosting question, i personally use aws


Type query params

Can't find up to date library maybe it's not that important. Good documentation can probably make up for it.


How to change the dragging css?

I have a component that looks like this and I only want to swap the Answer between Question.

I've managed to swap the answer only, but when I drag the Answer it will pull both Question and Answer out.

How can I fix it to only make the visual for the dragging to be only Answer?
Here is my demo on https://codesandbox.io/s/quiz-swap-y9etz
P/s: I have tried using the draggable and filter

Hi @VnVentX, did you find a solution yet?


run_preCluster.py --cpus=30 CalledProcessError(retcode, cmd)

Hello All,
I am receiving following error while running the Family finding step of Cogent for a large dataset.  Kindly suggest.
input file:
isoseq_flnc.fasta
command:
python /path/to/cDNA_Cupcake/cupcake2/tofu2/run_preCluster.py --cpus=30
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '/usr/bin/time -v minimap2 -H -f 0.00001 -N 2000000 -m 20 -t 20 seed0.fasta seed0.fasta > seed0.fasta.seed0.fasta.f00001.minimap 2> seed0.fasta.seed0.fasta.f00001.minimap.log' returned non-zero exit status 127

Hey, this script seems to have been removed in v29 of cupcake, but for anyone attempting to run cogent with v28, this issue is caused by the default time program on macos being different from the linux one. To fix it, you can run
brew install gnu-time
if you have brew installed and then going into the script AlignerRunners.py mentioned further up in the error message and changing /usr/bin/time to gtime. Though that's a bit of a hack and I would recommend running Cogent on a linix platform if possible.


Update dependencies

Pull request
Description
This PR updates a couple of dependencies and fixes a Lint warning.
Changes made

Update the following dependencies:

AndroidX Compose 1.7.2:

Animation
Foundation
UI

AndroidX Navigation 2.8.1

Fix a Lint warning: https://github.com/SRGSSR/pillarbox-android/security/code-scanning/1404

Checklist

[ ] Your branch has been rebased onto the main branch.
[ ] APIs have been properly documented (if relevant).
[ ] The documentation has been updated (if relevant).
[ ] New unit tests have been written (if relevant).
[ ] The demo has been updated (if relevant).
[ ] All pull request status checks pass.

I've un-ignore these dependencies from Dependabot.
Let's see if it updates them next Monday.
Also, these are already outdated now 😅


Add private keyword

 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.

Why browserstack reponse 404 error?
How can I do pull request?

That's an internal CI error unrelated to this PR. You've already created the pull request, but you need to sign the CLA before I can review and approve your PR.

Thank you 👍


Update helpernode and ocp4-playbooks tags for latest code

Fixes: #96
Signed-off-by: Prajyot Parab<EMAIL_ADDRESS>

@Prajyot-Parab Did you test this?
Specially https://github.com/RedHatOfficial/ocp4-helpernode/blob/master/vars/main.yml#L11 is required. In my experience, this will download x86 version and fail during extraction

We either wait for https://github.com/RedHatOfficial/ocp4-helpernode/pull/140 OR provide ppc64le url in helpernode_vars.yaml.

Yes @yussufsh this would fail because of helm_source. Thanks for pointing it out.
I am fine with waiting for that PR to get merged or going ahead and doing changes related to setting helm_source.

reopening to run the terraform validate job

Keywords which can automatically close issues and at(@) mentions are not allowed in commit messages.
The list of commits with invalid commit messages:

6c9a5eb Update helpernode and ocp4-playbooks tags for latest code

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Prajyot-Parab
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@Prajyot-Parab are we good to update this? Can you follow up with Christian on helpernode changes to ignore helm binary?
If that is taking more time then better add helm ppc link?

Closed by mistake. Re-opening...

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Prajyot-Parab
To complete the pull request process, please assign bpradipt
You can assign the PR to them by writing /assign @bpradipt in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@Prajyot-Parab: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

pull-ocp4-upi-powervm-terraform-validate
6c9a5eb3fa3dcd678062cfb79847cd2838396b25
link
/test pull-ocp4-upi-powervm-terraform-validate

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Closing this one as no longer needed.


python311Packages.zamg: 0.3.1 -> 0.3.3

Diff: https://github.com/killer0071234/python-zamg/compare/refs/tags/v0.3.1...v0.3.3
Changelog: https://github.com/killer0071234/python-zamg/releases/tag/v0.3.3
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.05 Release Notes (or backporting 23.05 and 23.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.

Priorities
Add a :+1: reaction to pull requests you find important.

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

5 packages built:

home-assistant-component-tests.zamg
python310Packages.zamg
python310Packages.zamg.dist
python311Packages.zamg
python311Packages.zamg.dist


File not existing

Heyyy, so I am having a problem where only by importing the library i gett this error:
Metro has encountered an error: While trying to resolve module
'react-native-
mesh-gradient from file '/Users/ Armando09/PROGRA2/javascript/reactNative/ baiaUI/app/index.jsx*, the package / Users/Armando09/PROGRA2/javascript/ reactNative/baiaUI/node_modules/react-native-mesh-gradient/package.json* was successfully found. However, this package itself specifies a 'main module field that could not be resolved (*/Users/ Armando09/PROGRA2/javascript/reactNative/ baiaUI/node_modules/react-native-mesh-gradient/lib/commonjs/index.js'. Indeed, none of these files exist:

/Users/Armando09/PROGRA2/javascript/ reactNative/baiaUI/node_modules/react-native-mesh-gradient/lib/commonjs/ index.js(.ios.ts|.native.ts|.ts|.ios.tsx| .native.tsx|.tsx|.ios.mjs|.native.mjs|.mj s/.ios.js|.native.js|.js/.ios.jsx|.native
•jsx|.jsx.ios.json.native.json|.json.i os.cjs|.native.cjs|.cjs|.ios.scss|.native .scss|.scss|.ios.sass|.native.sass|.sass| .ios.css|.native.css|.css)
/Users/Armando09/PROGRA2/javascript/ reactNative/baiaUI/node_modules/react-native-mesh-gradient/lib/commonjs/ index.js/ index(.ios.ts|.native.ts|.ts/.ios.tsx|.na tive.tsx|.tsx|.ios.mjs|.native.mjs|.mjs|. ios.js|.native.js|.js|.ios.jsx|.native.js x|.jsx|.ios.json|.native.json|.json|.ios. cjs|.native.cjs|.cjs|.ios.scss|.native.sc ss| .scss|.ios.sass|.native.sass|.sass|.10 s.css|.native.css|.css): /Users/ Armando09/PROGRA2/javascript/reactNative/ baiaUI/node_modules/metro/src/node-haste/ DependencyGraph.js (243:17)
241
}
242
if (error instanceof
InvalidPackageError) {

243 |
throw new
PackageResolutionError({
244
packageError: error,
245
originModulePath:from，
246 |
targetModuleName: to,

I did install the library and i got the error.
Things to coonsider:

I am using expo to run the app
When viewing the installed module on /node_modules, the folder of 'react-native-mesh-gradient' only contains a package.json file
I tried installing the liibrary manually by downloading the zip from github and putting it with the correct name, in node_modules, and I got the same error

Hope anyone could help me, thank yoouu

hello. i corrected the package name on the github repo readme, but unfortunately i forgot to sync it with npm.
please install the @wilmxre/react-native-mesh-gradient library instead of react-native-mesh-gradient and let me know if it works or not

Heyy, noo unfortunately doesn't works yet, do you know what else could it be?

also i updated the docs with information in regards to expo usage, please take a look at it at https://github.com/wilmxre/react-native-mesh-gradient?tab=readme-ov-file#expo-support
you will need to create a custom expo dev build, because expo-go doesn't support custom native modules. it is only a sandbox/playground environment, where you can play with the UI and with the native modules that are already built in the expo go app. these are expo specific packages, that are supported out-of-the-box.
when you create a custom dev build, you basically create your own "expo go" app, that includes custom native code.

And for creating playgrounf environment, you need to have an Apple Developer Program account right?

if you want to install the app on a real device, then yes, you will need an Apple Developer membership, but you can install it on a simulator without needing one.
take a look at: https://docs.expo.dev/develop/development-builds/create-a-build/#create-a-build-for-emulatorsimulator

but for this you will need Xcode, which means you need to have a macbook

Cool cool thanks so much

@wilmxre hey! I encountered the same issue with the library, it looks like the build output is not included in the npm package. the main field of the package references "module": "./lib/module/index.js",, but lib folder is missing from the package itself https://www.npmjs.com/package/@wilmxre/react-native-mesh-gradient?activeTab=code. Might it be that the build command hasn't been ran prior to publishing the package?