Version 1.6.2 stops working on react-native 0.74.5

Hello there,
a while ago I updated to the new version and it stopped working on react-native 0.74.5, I do not know if it is something expected but at the moment I left forced to the previous version that still works perfectly.

v1.6.1
v1.6.2

See how in the new version (1.6.2) as soon as the screen loads nothing is displayed and should do as seen on version 1.6.1.
Note: ignoring the warning below is a behavior of my application.

Hmm, probably caused by https://github.com/oblador/react-native-collapsible/pull/475
Do you have a small reproduction of this issue?

Same issue for me 1.6.2 is no longer working with Expo 51

Same Issue for me

Same issue for me. It occurred after I updated to Expo 51 SDK (react native 0.74).
The issue is exactly the same as the OP. The view is not rendered initially (when 'collapsed' is set to true), you must set it to false then to true for it to show the content.

Same issue with 1.6.1. if collapsed is default to true, content is not expanded. This was working before upgrading to react-native 0.74.5

Had to rollback to 1.5.2. (You might lose some features).
NOTE:
Expanding and collapsing very quickly will throw an error: this.contentHandle.getNode() is not a function.
The ref is basically is the reference to Animated.View, for which getNode() does not work anymore. Instead you can call .measure(...) directly on the ref. So, you should patch the package.
From:

To:

Same issue for me on react-native 0.73.9 with 1.6.2. 1.6.2 works well.

RCA:
In https://github.com/oblador/react-native-collapsible/blob/038f436c9bdb8f7876fc2d4e98d0553737889da7/Collapsible.js#L191
Height will be 0 if hasKnownHeight is false. But hasKnownHeight is true only when users expand options (collapsed change from true to false)
https://github.com/oblador/react-native-collapsible/blob/038f436c9bdb8f7876fc2d4e98d0553737889da7/Collapsible.js#L45
In case the collapse is false initially, we should show the content, but we don’t have the logic to measure content -> hasKnownHeight is false -> height is 0
Solution:
We should trigger _toggleCollapsed in componentDidMount or _handleLayoutChange if this.props.collapsed is false
  componentDidMount(){
    if(!this.props.collapsed){
      this._toggleCollapsed(this.props.collapsed)
    }
  }

@oblador What do you think about my solution above?

Same issue.

In case the collapse is false initially, we should show the content, but we don’t have the logic to measure content

@truph01 I agree with the RCA, initially we don't have a logic to measure the content height and due to that height will remain 0 initially.

componentDidMount(){
 if(!this.props.collapsed){
   this._toggleCollapsed(this.props.collapsed)
 }
}

As proposed I think either we need to call function _toggleCollapsed or we can call _measureContent to avoid animation.
@truph01 can you plz raise a PR, @oblador will review it there.

@oblador  @Pujan92 PR is ready to review

RCA:
In
https://github.com/oblador/react-native-collapsible/blob/038f436c9bdb8f7876fc2d4e98d0553737889da7/Collapsible.js#L191
Height will be 0 if hasKnownHeight is false. But hasKnownHeight is true only when users expand options (collapsed change from true to false)
https://github.com/oblador/react-native-collapsible/blob/038f436c9bdb8f7876fc2d4e98d0553737889da7/Collapsible.js#L45
In case the collapse is false initially, we should show the content, but we don’t have the logic to measure content -> hasKnownHeight is false -> height is 0
Solution:
We should trigger _toggleCollapsed in componentDidMount or _handleLayoutChange if this.props.collapsed is false
  componentDidMount(){
    if(!this.props.collapsed){
      this._toggleCollapsed(this.props.collapsed)
    }
  }

Thank you so much.

Here is a diff based on the PR @Pujan92 was kind enough to file.
index dc4d3b8..d69d1e7 100644
--- a/node_modules/react-native-collapsible/Collapsible.js
+++ b/node_modules/react-native-collapsible/Collapsible.js
@@ -53,6 +53,12 @@ export default class Collapsible extends Component {

   contentHandle = null;

+  componentDidMount() {
+    if (!this.props.collapsed) {
+      this._measureContent((height) => this.state.height.setValue(height));
+    }
+  }
+
   _handleRef = (ref) => {
     this.contentHandle = ref;
   };```

In my case, I encountered a crash when rotating the device to landscape mode under specific circumstances. The crash occurred if I opened a modal from the page where the accordion component is used, and the modal supports landscape orientation. To prevent this, I had to add an additional check to the patch. Without this fix, rotating the device while the modal is open causes the app to crash.
+  componentDidMount() {
+    if (!this.props.collapsed) {
+      this._measureContent((height) => height != null && this.state.height.setValue(height));
+    }
+  }
+

Experiencing the same with 1.6.2 and RN 0.72.3 and Expo 49.0.5.
Downgrading to 1.6.1 worked for me.
Not sure why @oblador is ignoring this PR though...

@oblador please plan to merge the PR. Thanks

I've created a fork with the fix. You can just use the following line in your package.json
    "react-native-collapsible": "github:sheff3rd/react-native-collapsible#master",

I took this comment as a base:
https://github.com/oblador/react-native-collapsible/pull/480#discussion_r1763553225
Kudos to @Pujan92 and @truph01 for working on the fix


Should this repo be archived?

I noticed the version 8.0.0 of enketo-core was released ~3 weeks ago but I couldn't find anything about it on this repo.
After digging for a bit, I found out about the decision to merge packages into a monorepo and there I found the recent changes that were shipped as part of enketo-core v8.0.0
Is the monorepo now the only place we should look at for updates about enketo? If so, should this repo be archived?
As part of the transition to the monorepo, what will happen to the remaining open issues of each package?

In addition consider updating the URLs in the package.json to the new repo

https://github.com/enketo/enketo/blob/main/packages/enketo-core/package.json#L21
https://github.com/enketo/enketo/blob/main/packages/enketo-core/package.json#L37

Hoping I can get to both next week. Tracked at https://github.com/enketo/enketo/issues/3


Rewrite Scratch extension(s)

[ ] Find a better bugfix for #122
[ ] Find a fix for #103
[ ] Rewrite B3.0/S3.0
[ ] Rewrite S4.0
[ ] Rewrite S4.1
[ ] Rewrite archived Suite
[ ] Rewrite (and update) Turbowarp-specific variant

Ref for myself:
https://stackoverflow.com/questions/23051416/uncaught-invalidstateerror-failed-to-execute-send-on-websocket-still-in-co

Found various fixes and I'm implementing events properly this time around. Expecting rewrite to be finished soon.

Almost done.


Rewrite location config tests using tables

This pull request rewrites the location config tests using tables and subtests. It does not introduce functional changes.
It depends on https://github.com/artefactual-sdps/enduro/pull/854.

Looks good I was considering doing this once I saw what location configuration test was like in #842.


How to uninstall EasY_HaCk please help

I need to uninstall EasY_HaCk how can i do it .pls respond fast
I am running out of space.

I need to uninstall EasY_HaCk how can i do it .pls respond fast
I am running out of space.

Type rm -rf  I hope you have been useful


EMR Spark job with SigV4 signing

Hi, my team is adding SigV4 signing to all of the read/write requests that our resources send to Elasticsearch. We've successfully added signing to requests from our backend Java service and to a Lambda function. We're now trying to add signing to our EMR Spark jobs, which are using emr-6.6.0, Spark 3.x, Scala 2.12, and opensearch-hadoop (Maven-org-opensearch-client_opensearch-spark-30_2_12). The Elasticsearch cluster is version 7.10
After reading the opensearch-hadoop User Guide and the Configuration Options for Maven-org-opensearch-client_opensearch-spark, I updated our OpenSearch config to the following
private val basicOpenSearchConfig = Map(
    "opensearch.nodes" -> <opensearch_endpoint>,
    "opensearch.nodes.wan.only" -> "true",
    "opensearch.port" -> "443",
    "opensearch.net.ssl" -> "true",
    "opensearch.net.ssl.cert.allow.self.signed" -> "true",
    "opensearch.net.ssl.protocol" -> "SSL",
    "opensearch.aws.sigv4.enabled" -> "true",
    "opensearch.aws.sigv4.region" -> "us-east-1")

After enabling the SigV4 signing config, I tested if the Spark job could read index names from a cluster that has fine-grained access control enabled and got "Unauthorized" as the response. Here's what I've tried for troubleshooting:

Copying aws-java-sdk-bundle-1.12.170.jar into the EMR host during bootstrapping, as recommended by the opensearch-hadoop User Guide. It didn't make a difference, and the lack of this jar in the EMR host also didn't cause any ClassDefNotFound errors
Made sure that the following policy is associated with the IAM role that the EMR cluster is using

{
  "Effect": "Allow",
  "Action": "es:ESHttp*",
  "Resource": "arn:aws:es:us-east-1:<aws_account_id>:domain/<domain_name>/*"
}

Any ideas for troubleshooting?

@joyfulwang Have you mapped the EMR job's IAM role to a internal user within ElasticSearch/OpenSearch according to the documentation here: https://docs.aws.amazon.com/opensearch-service/latest/developerguide/fgac.html#fgac-access-control


Standardizes the Index::create_* APIs

This pull request addresses the create half of #286
The goal here is to create a consistent api that will flow well in IDE's that support code completion since there are grouped together.
The docs now have them next to each other as well

Ok, this is an "important" change since its the API for creating indices. Let me have it with the questions and comments. :)
After this I'll do a PR for the open_* API's with what was learned from here.

I was ill at ease with the spec of create (wiping off the previous data) but it has the merit of being in line with the File::create API.
In this case, I think the previous files should be garbage collected correctly but we probably want to double check that. Also, it might be a good idea to trigger GC right after the meta.json have been overwritten.

Let's allow ourselves to break public API until 1.0.
I'll merge this right now and look forward your PR for the open API.


Since we bit the bullet and moved to a testing machine with python 2.7,
this requirement is no longer necessary.  We just don't support 2.6 now.
Which is a valid course, in our opinion.


Plugin System

I want to trace RPC calls. However, looking through the code, this doesn't seem to be possible yet as there is no catch-all way to start and propagate traces.
Thus, I propose a Ktor-like Plugin System that allows you to add handlers throughout the service call lifecycle. As an initial implementation, adding pre- and post-RPC service call hooks would do just fine.
The user-facing API could look something like this:

Later, more hooks can be added, for example pre and post serialization, error handlers, ...

Hi, @SIMULATAN ! Thank you for logging the issue, we are considering the extension points (aka plugins) in our work, and they will be added, though I can't say when for now


stable/nginx-ingress gives CrashLoopBackOff when installing with vaules.yaml file

Is this a request for help?:

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug

Version of Helm and Kubernetes:
K8s version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.1", GitCommit:"3a1c9449a956b6026f075fa3134ff92f7d55f812", GitTreeState:"clean", BuildDate:"2018-01-04T11:52:23Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.1", GitCommit:"f38e43b221d08850172a9a4ea785a86a3ffa3b3a", GitTreeState:"clean", BuildDate:"2017-10-11T23:16:41Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
helm version
Client: &version.Version{SemVer:"v2.8.0", GitCommit:"14af25f1de6832228539259b821949d20069a222", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.8.0", GitCommit:"14af25f1de6832228539259b821949d20069a222", GitTreeState:"clean"}
Which chart:
stable/nginx-ingress
What happened:
nginx-ingress-controller pod fails to start when deployed using values.yaml file.
NAME                                                   READY     STATUS             RESTARTS   AGE
front-nginx-ingress-controller-6c968cfc54-tvszl        0/1       CrashLoopBackOff   3          1m

> $ kubectl logs front-nginx-ingress-controller-6c968cfc54-tvszl -n=kube-system
> -------------------------------------------------------------------------------
> NGINX Ingress controller
> unknown flag: --nginx-configmap
> Usage of :
>   Release:    0.10.2
>   Build:      git-fd7253a
>   Repository: https://github.com/kubernetes/ingress-nginx
> -------------------------------------------------------------------------------

What you expected to happen:
should start pod
How to reproduce it (as minimally and precisely as possible):

copy values.yaml, make no changes
$ helm install stable/nginx-ingress --name front -f values.yaml --namespace kube-system

Anything else we need to know:

from what i just saw, the chart has the wrong args for nginx. it's using '--nginx-configmap' when the correct arg is '--configmap'. i just edited the deployment in kubernetes and it fixed it.

@kwtalley this works.
is there a PR for this already?

@egeland could you please take a look at this?

@tuananh I hadn't created one but i'd be happy to if you'd like

Must be a bug in this code:
  {{- if (semverCompare ">=0.9.0-beta.1" .Values.controller.image.tag) }}
    - --configmap={{ .Release.Namespace }}/{{ template "nginx-ingress.controller.fullname" . }}
  {{- else }}
    - --nginx-configmap={{ .Release.Namespace }}/{{ template "nginx-ingress.controller.fullname" . }}
  {{- end }}

I'm guessing that the semverCompar doesn't consider 0.11.0 to be ">=0.9.0-beta.1"...

that's the conclusion i came to as well, which is frustratingly common with version string comparison/parsing (likely is comparing 9 to 1 or it could be the 'beta' part). i haven't done a lot with testing helm charts so i need to look that up and see if there's a better way to do the comparison. reason being as i don't want to just EOL any support for >0.9.0-beta.1. thoughts?

yeah, i checked that as well but it seems the code looks correct to me.

We can add an additional conditional for >= 0.9.0 which should, in theory, cover the rest of the versions after the beta...?

will it break for v0.9.0? from what i thought, the change was introduced in 0.9.0-beta?

Doesn't the -beta mean that it's a candidate of the number?
So 0.9.0 is based off the final 0.9.0-beta.x?

I use the chart without any problems. Just did a helm template. The result is correct.
        - name: nginx-ingress-controller
          image: "quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.11.0"
          imagePullPolicy: "IfNotPresent"
          args:
            - /nginx-ingress-controller
            - --default-backend-service=default/RELEASE-NAME-nginx-ingress-default-backend
            - --election-id=ingress-controller-leader
            - --ingress-class=nginx
            - --configmap=default/RELEASE-NAME-nginx-ingress-controller

cc @mattfarina

@unguiculus indeed helm template gives me this when I clone the charts repo locally and run template there:
$ helm template nginx-ingress --name ing -f ../../../nginx-ingress-conf.yaml
...
      containers:
        - name: nginx-ingress-controller
          image: "quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.11.0"
          imagePullPolicy: "IfNotPresent"
          args:
            - /nginx-ingress-controller
            - --default-backend-service=default/ing-nginx-ingress-default-backend
            - --election-id=ingress-controller-leader
            - --ingress-class=nginx
            - --configmap=default/ing-nginx-ingress-controller
...

But
$ helm install stable/nginx-ingress --name ing -f nginx-ingress-conf.yaml --debug --dry-run
...
      containers:
        - name: nginx-ingress-controller
          image: "quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.11.0"
          imagePullPolicy: "IfNotPresent"
          args:
            - /nginx-ingress-controller
            - --default-backend-service=default/ing-nginx-ingress-default-backend
            - --nginx-configmap=default/ing-nginx-ingress-controller

Curiously enough if I package the chart locally, the problem doesn't happen:
$ helm package nginx-ingress
$ helm install ./nginx-ingress --name ing -f ../../../nginx-ingress-conf.yaml --debug --dry-run
...
      containers:
        - name: nginx-ingress-controller
          image: "quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.11.0"
          imagePullPolicy: "IfNotPresent"
          args:
            - /nginx-ingress-controller
            - --default-backend-service=default/ing-nginx-ingress-default-backend
            - --election-id=ingress-controller-leader
            - --ingress-class=nginx
            - --configmap=default/ing-nginx-ingress-controller
...

helm fetch stable/nginx-ingress --untar
helm template ./nginx-ingress -f ./values-nginx-ingress.yaml
->
    spec:
      containers:
        - name: nginx-ingress-controller
          image: "quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.11.0"
          imagePullPolicy: "IfNotPresent"
          args:
            - /nginx-ingress-controller
            - --default-backend-service=default/RELEASE-NAME-nginx-ingress-default-backend
            - --nginx-configmap=default/RELEASE-NAME-nginx-ingress-controller
          env:

Getting the same behaviour with template as with helm upgrade/install. controller.tag = "0.11.0"

@oivindoh If you get 0.8.22, your cache is probably stale. Do a helm repo up.


Tie in the Tidbits bot

[ ] add support for adding new projects and shoutout entries by text box
[ ] add support for adding new project and shoutout entries by email
[ ] move the bot to a public repository and refactor
[ ] add support for directly adding those with the bot
[ ] add support for updating existing entries
[ ] add Discord support for Tidbits bot

see also #27


Update horizontal-pod-autoscale-walkthrough.md

fix typo and broken links

What is this trying to fix?

And ...  this is targeting release-1.19, why is that?
The "master" branch we see today is for 1.19, until we release 1.20.

It's my fault for not following the new rules, closing this pr


Unexpected end of string error

Source information
Comicabc v 1.4.2
Source language
Chinese
Steps to reproduce
Source: ComicABC v1.4.2
Select any manga
Select any chapter
Expected behavior
Load the chapter for viewing
Actual behavior
Get an "Unexpected end of string" error
Mihon/Tachiyomi version
0.17.0
Android version
Android 15
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

/edit-title "無限動漫 / 8comic (Comicabc): Unexpected end of string error"


Fix broken image link

Fixes broken link detected by docs-csm team when reviewing #5260 's linkchecker.

/backport release/1.5 release/1.4 release/1.3 release/1.2 release/1.0


How to make it work with Azure Databricks - MLFlow

In Azure Databricks, MLFlow is supported and can be accessed via API. The MS docs says:

You can invoke the MLflow REST API using URLs of the form https://<databricks-instance>/api/2.0/mlflow/<api-endpoint>, replacing <databricks-instance> with the <region>.azuredatabricks.net domain name of your Azure Databricks deployment.

So in my appsettings.json I have:
{
  "MLFlowConfiguration": {
    "MLFlowServerBaseUrl": "https://southeastasia.azuredatabricks.net",
    "APIBase": "api/2.0/mlflow/"
  }
}

But trying that with the lines of code below returns an exception:
var experimentName = Guid.NewGuid().ToString();
var experimentRequest = await _mlFlowService.GetOrCreateExperiment(experimentName);

Error:
'Object reference not set to an instance of an object.'
   at MLFlow.NET.Lib.Services.MLFlowService.<GetOrCreateExperiment>d__4.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at MLNETMLFlowSampleConsole.Program.<RunExperiment>d__3.MoveNext() in C:\Samples\2019\MLNETMLFlowSample\MLNETMLFlowSampleConsole\Program.cs:line 55
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at MLNETMLFlowSampleConsole.Program.<Main>d__2.MoveNext() in C:\Samples\2019\MLNETMLFlowSample\MLNETMLFlowSampleConsole\Program.cs:line 34

I'm also interested in using this to monitor a remote MLFlow server.  I'm using Azure ML Studio, so I have an azure:// based uri provided for my workspace.  Can one of the maintainers of this repo chirp in here to let us know if it's possible?  I don't mind chipping in a little of my time to make it happen if it is currently not possible.

Hi @xentropy-git I was one of the original developers on this project. Unfortunately we've not looked at this project in quite some time and we really should be marking this repo as read only. I don't have current knowledge of the product to say yes or no directly to your answer sorry!


[VMWare, Trivial] Improve readability of required_vars dict

In 'ocp-on-vmware.py' and 'add-node.py' python modules by spliting
loooooong line to several small with nice indentation.
It eases source code readability and possibility to add more values
to the dicts in future.
Is there a relevant Issue open for this?
No. Trivial improvement.
Who would you like to review this?
cc: @tomassedovic PTAL @dav1x

lgtm! merged


Importing CSS not working on Dioxus Desktop

Problem
On Dioxus Desktop (0.6.0-alpha.2 and alpha.3), the following syntax to import an css file is not functional:
       document::Link {
            rel: "stylesheet",
            href: asset!("./assets/fileexplorer.css")

The above example is taken from the file explorer example project in this repo. Indeed, upon dx serve of this project, the styling is obviously broken
Steps To Reproduce
Steps to reproduce the behavior:

Include css using the above syntax
Run dx serve
CSS not working
Look at inspector: you can see the file (e.g., dioxus://index.html/maincssad0597f224a3fdb7.css). However, you get "An error occured trying to load this resource." in the inspector when trying to open the file

Expected behavior
CSS file is included and CSS is applied
Environment:

Dioxus version:  0.6.0-alpha.2
Rust version:   latest stable
OS info:  Arch Linux
App platform:   Desktop

I'm running 0.5.7 and having the same issue on both Windows and OSX

I'm not sure if dx new actually imports the CSS file by default; iirc I don't think it does for 0.6.0 on Desktop? I might be wrong though. The macro still doesn't seem to work though, or it's corrupting the CSS file somehow

same issue on web.

Oh really? What version? I was testing web on 0.6.0-alpha.2 and it seemed fine, using the new head::Link and asset! syntax

Update: If there are any Dioxus devs here, it would be great if you could confirm whether or not you are aware of this bug and/or what might be causing it. I am on the Discord and it seems many people can replicate it; one person pointed out that doing something like href: format!("/{}", asset!("assets/main.css")) causes the file to no longer show as unloadable. However, the file still shows as empty and the CSS doesn't apply.

Update: If there are any Dioxus devs here, it would be great if you could confirm whether or not you are aware of this bug and/or what might be causing it. I am on the Discord and it seems many people can replicate it; one person pointed out that doing something like href: format!("/{}", asset!("assets/main.css")) causes the file to no longer show as unloadable. However, the file still shows as empty and the CSS doesn't apply.

Update 2: If you do dx new and select tailwind it uses a syntax which can be modified to function properly. Here is how I successfully integrated it:
fn main() {
    let cfg = Config::new()
        .with_window(WindowBuilder::new().with_resizable(true))
        .with_custom_head(r#"<link rel="stylesheet" href="./assets/main.css">"#.to_string());

    dioxus::LaunchBuilder::desktop().with_cfg(cfg).launch(App)
}

However, the fact that document::Link doesn't work is clearly a bug, so I will leave this issue open

This has been fixed in #2779.
Additionally, paths in the asset macro should start with absolute paths relative to the crate root. e.g. /assets/main.css for
- my-cool-project (crate root)
    - assets
        - main.css
    - src
    - Cargo.toml


Restructure Tutorials in About Learn page

Create ordered list of tutorials in About Learn page.

Fixed order.
https://ei.docs.wso2.com/en/latest/ballerina-integrator/learn/about-learn/
Add the following text and customize for BI:
The integration tutorials will walk you through the main capabilities and features of WSO2 Enterprise Integrator (WSO2 EI), and help you understand how to build an integrated system using WSO2 EI. In these tutorials, we will build an integrated Health Care System by using the capabilities of all the profiles in WSO2 EI (ESB profile, Micro Integrator profile, Message Broker profile, Business Process profile, MSF4J profile and the Analytics profile). Each of the tutorials in this section will provide step-by-step instructions on how to build and test the various parts of this system until the integrated Health Care system is complete.


[feature request] contribution guide

Adding a guide on how to contribute missing nodes or edges would be helpful.  Is the correct procedure adding the new compilers to https://github.com/mohd-akram/compilers and re-generating ./js/compilers.js?

@SKalt please review #14, whose aims include addressing this need. I am also curious about the "re-generating ./js/compilers.js" step, though -- hopefully @mohd-akram can clarify that point.

@waldyrious, #14 does close this.  How to manage The periodic updates remains unclear, but now falls under dependency management. I'd recommend  adopting either npm or yarn so you can npm install --save https://github.com/mohd-akram/compilers.  That would require adopting a bundler, which I could help with.

For what it's worth, at tldr-pages we use Travis to automatically make commits to another repo that keeps an archive of all the commands in the original repo, as soon as any commits is merged in. To see how we set it up, check the travis.yml file and the build.sh script it calls to do that.
Something like that could certainly be adapted to work here, so that no manual work (by contributors and maintainers alike) would be necessary :) what do you guys think?

I like the "no work required" part.  If you want to set it up, you've got
my support.  Any thoughts on git subtree and git submodule to manage
the other repo as a dependency?
On Sat, Jul 7, 2018 at 1:50 PM Waldir Pimenta<EMAIL_ADDRESS>wrote:

For what it's worth, at tldr-pages https://github.com/tldr-pages/tldr
we use Travis to automatically make commits
https://github.com/tldr-pages/tldr-pages.github.io/commits/master to
another repo that keeps an archive of all the commands in the original
repo, as soon as any commits is merged in. To see how we set it up, check the
travis.yml file
https://github.com/tldr-pages/tldr/blob/master/.travis.yml and the
build.sh script
https://github.com/tldr-pages/tldr/blob/master/scripts/build.sh it
calls to do that.
Something like that could certainly be adapted to work here, so that no
manual work (by contributors and maintainers alike) would be necessary :)
what do you guys think?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/mohd-akram/languages/issues/11#issuecomment-403232562,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ9G5ebmeRbknQzru5oXRqU8_kd9tou2ks5uEPTggaJpZM4VFgH8
.

Any thoughts on git subtree and git submodule to manage the other repo as a dependency?

They certainly would work, as would build tools like those you mentioned; but neither would be automatic, "no work required", which for the purposes of this demo I think would be preferable.

I agree they'd be more work, at least for now.  I'm still wrestling with automating git sub(tree|module)  to coordinate two apps and a library for work.  Hopefully I'll get that done and be able to disagree in the future :)


Question: Unable to read data from the transport connection

Describe the issue
Please can you help me with my problem. I am using function Get-BCContainerApp and I get this error: "Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.". This only happens sometimes and completely randomly and I have not found any rule. When I run the function again it runs without a problem. It happens when I download Base Application (other appliactions are ok). Do you have any idea? Can helps if I set higher any of the timeouts?
Thank you for your help.

I have 10 containers on my PC. When I decide to upgrade the containers to a newer version, 3 of the 10 end up with this error. The error occurs more often when the PC is more busy and downloading extensions takes more time.
The problem is always with the Base Application extension, which is the largest. That's why I think it might help to increase some timeout. When I run the function again, it usually completes without problems. When the function ends with an error again, I stop one of the containers and then the function always completes without an error.
It is not even possible to simulate this, because the next time all containers are upgraded, the error can affect different containers than the first time. So they are not always the same containers.

In the Get-NavContainerApp.ps1 (under Program Files\WindowsPowerShell\Modules\BcContainerHelper\version\AppHandling) line 104 - it uses Invoke-RestMethod to download the app
Invoke-RestMethod is supposed to wait indefinite (doc: https://docs.microsoft.com/da-dk/powershell/module/microsoft.powershell.utility/invoke-restmethod?view=powershell-5.1), but I found articles indicating that there is a timeout of 100sec.
You could modify the file and add
-TimeoutSec 300
to that line - which would be 5 minutes.
Then give me a heads up on whether that makes a difference.

I actually thought I had replaced all occurrences of Invoke-RestMethod -outfile  with Web Client download.
A similar pattern is used in Compile-AppInBcContainer
Will fix this one as well.

Thanks for editing. Your tool saves me from a lot of container problems every day.


[Bug] Not found reference script in UTxO after build tx with toAddressWithData

tx.collectFrom([fundUtxo]).pay.ToAddressWithData(         ownAddr,         {           kind: "inline",           value: datum ?? Data.void()         },         {         },         script       )
https://preview.cardanoscan.io/transaction/8665bcd1586fbf524b36ffd52777dddc7e91015290b1ef70649b8f8f021dc99f?tab=utxo
"@lucid-evolution/lucid": "^0.3.51
I am building a transaction with scriptRef but the returned results do not have scriptRef even though I have checked that there is a "script" log.

Try https://preview.cexplorer.io/tx/8665bcd1586fbf524b36ffd52777dddc7e91015290b1ef70649b8f8f021dc99f


Coordinate system mapping in developer documentation

developer docs state this:

glTF 2.0 also uses a right-handed coordinate system, but with x point right, y point up and z backward.

On the other hand, GLTF spec says this:

The front of a glTF asset faces +Z.

Do developer docs imply that "backward" is the direction away from user into computer monitor?
If so, i think developer docs can be made concise stating what direction does the asset face.

That mapping table in the docs looks wrong.  Blender's +Z (Blender up) gets mapped to glTF's +Y (glTF up).  Blender's -Y is actually (per ortho view presets, such as Numpad 1) considered Blender's "front", so Blender -Y gets mapped to glTF's +Z (glTF forward).
This all amounts to a simple 90 degree rotation about the X axis, so not as complicated as it sounds.
We should fix the docs.

New docs (https://docs.blender.org/manual/en/dev/addons/io_gltf2.html) mention glTF convention is +Y up. More details would be welcome but not high priority in my opinion.


Added Failure Plugin

Resolves #254.

@JonasVautherin did we already add failure to mavsdk_server by now?

@julianoes sorry, I am currently very busy and did not have time to do this yet.


CI auto update failed

https://github.com/sustainable-computing-io/kepler/actions/runs/12100596870/job/33739402478
I suppose we can't use auto update in CI as default branch is protected? cc: @rootfs

or should I grant a write permission on https://github.com/sustainable-computing-io/kepler/blame/c8ed7eb14d6db3c2c1e7506cda83c962dccea998/.github/workflows/pre-commit-auto-update.yml ?

sorry my bad - it does need write permissions or a PAT as per here: https://github.com/peter-evans/create-pull-request?tab=readme-ov-file#token


Capitalises first letter in ordinal string (e.g. 1St, 2Nd, 3Rd)

I'm trying to use this package across a range of strings which on occasion include written ordinal numbers e.g. 1st time, 2nd time, 3rd time.
This unfortunately returns 1St Time, 2Nd Time, 3Rd Time.
I'm willing to have anyone challenge otherwise here but I can't really see a use case for this so i'm proposing that strings starting with numbers are included.
(Or at least provide an optional parameter for it?)

PR: https://github.com/grncdr/js-capitalize/pull/13


Duplicated content

The section "How to set an application’s single sign-on mode" and the section "How to set an application’s provisioning mode
" show identical instructions (steps 1 to 5) and outdated (step 6 - filter control is named "Application Type" not "Show").
The same instructions are presented in the Quick start page "View your Azure Active Directory tenant applications" https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/add-application-portal
To improve maintainability, and reduce duplicates, I suggest to replace steps 1 to 5 with a link to View your Azure Active Directory tenant applications page.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1dd45c32-90cb-2c55-e450-35b0aeced0d0
Version Independent ID: 203ead09-b07a-b789-944a-24eecf1f2ffc
Content: How to choose which application type to use when adding an application
Content Source: articles/active-directory/manage-apps/choose-application-type.md
Service: active-directory
GitHub Login: @CelesteDG
Microsoft Alias: celested

Thank you for the feedback, @javierruizjimenez - This content set just transitioned over to my new team and I'll be doing an audit of the entire doc set. Please feel free to continue sending us your feedback and suggestions (like this one). It's very much appreciated. :)
Please do note that because this doc enhancement request/suggestion may require more time (transition on my part and some other priorities on our end), I've gone ahead and opened a work item 631834 in Azure DevOps and add a reference to this original GitHub issue/suggestion. For now, we'll have to close this GitHub issue, but I'll update it again once the work item on our side has been resolved. Thank you for your understanding and please continue to send us your suggestions/feedback.

#please-close
I have opened a separate work item in DevOps to track this doc enhancement and will address that once I've fully transitioned this doc set and will prioritize along with other work items in our backlog.


Fix guest invitation ui spec

Summary
Fix failing guest invitation ui spec. There are behavior changes especially on the MM-18042 Verify Add New/Existing Guest Users test. Not sure if release spreadsheet test cases are up to date but I captured the current behavior from master.
Ticket Link
none, failing on daily Cypress test

/update-branch

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.

Trying to auto merge this PR.

Pull Request successfully merged
SHA: 3121c02f4d0fa57d74da65b2a488817cdae3280c


Add turnstile to forgot-password page

Resolves #326
Add turnstile to forgot-password page
(For the screenshot I just made the back-end block. That's why there's a discrepency.)

Looks good to me

Merged, because the failing actions were unrelated.


PowerToys Run ran into an issue

Microsoft PowerToys version
<IP_ADDRESS>
Running as admin

[X] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce
Version: <IP_ADDRESS>
OS Version: Microsoft Windows NT 10.0.19043.0
IntPtr Length: 8
x64: True
Date: 30/06/2021 20:03:26
Exception:
System.InvalidCastException: Unable to cast object of type 'System.Windows.Documents.Run' to type 'System.Windows.FrameworkElement'.
at PowerLauncher.MainWindow.SuggestionsList_PreviewMouseLeftButtonUp(Object sender, MouseButtonEventArgs e)
at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
at System.Windows.UIElement.OnPreviewMouseUpThunk(Object sender, MouseButtonEventArgs e)
at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.ContentElement.RaiseTrustedEvent(RoutedEventArgs args)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

✔ Expected Behavior
open normally as usual
❌ Actual Behavior
PowerToys Run ran into an issue
** Something went wrong.**
Other Software
When I run Powertoys, I also open discord at the same time

PowerToysReport_2021-06-30-20-44-08.zip

we're have a fix checked in, we are tracking in #11898 and hope to have a fix out shortly.

I am having this same issue, error code 12029 on trying to install. Unable to install, for several weeks now.


Font-family viewer setting (in addition to font-size, margins)

See also:
https://github.com/readium/readium-js-viewer/issues/115

also see readium/readium-js-viewer/pull/532

Fixed by PR: https://github.com/readium/readium-shared-js/pull/301


Cannot query S3 paths containing whitespace

Describe the bug
I cannot register a path containing a space.
create external table test2 stored as parquet location 's3://andygrove-benchmark-data/trip data/yellow_tripdata_2022-06.parquet';
ObjectStore(NotFound { path: "trip%20data/yellow_tripdata_2022-06.parquet"

It works if I change the path to not have spaces:
create external table test stored as parquet location 's3://andygrove-benchmark-data/trip_data/yellow_tripdata_2022-06.parquet';
0 rows in set. Query took 0.429 seconds.

To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.

@tustvold Here is another potential object store bug that I found

This is sadly expected, https://docs.rs/object_store/latest/object_store/path/struct.Path.html#path-safety, I'm not really sure what can be done about this...

We should add least add a check and throw an error? The S3 error response is somewhat obscure.
It will be a shame if DataFusion and Ballista cannot support querying certain public data sets like nyc-tlc because they have spaces in paths. Other query engines support it. One example: https://coiled.io/blog/nyc-taxi-parquet-csv-index-error/
I will plan on digging into this more soon to understand the issue better.

We should add least add a check and throw an error?

Agreed, I would have expected DataFusion to refuse that query as the parquet location is not a valid URL. Possibly ObjectStoreUrl is escaping rather than parsing.

It will be a shame if DataFusion and Ballista cannot support querying certain public data sets

I welcome alternative suggestions for how to handle path escaping

Perhaps some kind of user-provided config to override the default behavior? I will take a look this weekend.

There is a somewhat related issue I ran into when playing with this, but you most definitely can create, read, etc... objects with paths containing spaces - https://github.com/apache/arrow-rs/issues/2800

I think this was fixed by #2801


HHH-9469 Windows platform build fixes

This was done ages ago when I was unit testing with Windows(Intellij/Eclipse) and  PostgreSQL(running over network on Linux).
Maybe there are other files added since the date of the patch to the tree, but I try to just do the minimum needed to fix the unit test.  If you know more about the status of the HIB project that a wildcard would be better.
Also it is eof=lf you are setting the mode of the 'eof' parameter.
Are you looking for an updated patch ?  I need to checkout tree again, and retest, etc... could take a few weeks to sort (I am not a HIB developer).

Thanks for the Pull Request. Did you sign the CLA?

@vladmihalcea these can be merged without needing the CLA.

I have a Windows machine and even without these changes all tests are running just fine now.

What is your EOL setting for git on windows.  So maybe they work for you but still do not work for others.
So please check the tests they related to have changed to not be fussy over the EOL conventions of the sample output data.  This way it does not matter what the EOL is.  Or manually change the EOL of the marked files to the other kind of EOL and rerun the tests.

I have core.autocrlf=true and everything works just fine. Are you able to replicate the test failure on your machine?


Reverted space

Summary
Related Issues
PR Overview

[ ] This PR requires new unit tests [y/n] (make sure tests are included)
[ ] This PR requires to update the documentation [y/n] (make sure the docs are up-to-date)
[ ] This PR is backwards compatible [y/n]
[ ] This PR changes the current API [y/n] (all API changes need to be approved by fchollet)

Thanks for the pull request, in general, you don't need to open a new pull requests to update it. If you just add commit to the original one, it works fine. I'll merge this pull request and close the other one.


[haskell-updates] staging some mass rebuilds

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.

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

@ofborg eval

Is there anything I can do to help move this forward? I'd love to be able to use GHC 9.10 in Nixpkgs.


Heroku Run: Provide a better warning when user is not connected to the internet

This is what the user sees when they fly into an offsite and are up late and don't realize they haven't set up internet at the AirBnb.
➜ ~/dev/api (cdwort-track-addon-billed-price)⚡ $ heroku run "echo 1" -a addons-production
 ▸    ENOTFOUND: getaddrinfo ENOTFOUND api.heroku.com api.heroku.com:443
 !   Error in heroku-run:
 !   getaddrinfo ENOTFOUND api.rollbar.com api.rollbar.com:443
 !   See /Users/aunger/.heroku/error.log for more info.

this is now sort of fixed here: https://github.com/heroku/heroku-cli-util/commit/afdb9314c649e45dc8884528b357e819a47089f2
At least it won't show the rollbar error. At some point I might look into decorating ENOTFOUND, but there are probably a few different errors that could show up if there is no internet connection (like ETIMEOUT)


HandleDeath isnt called if a player is killed during HandleQuit

This is a bit of a problematic issue. Currently we explicitly make sure HandleDeath is always called before HandleQuit to prevent the player from already effectively being disconnected. Calling any other event after HandleQuit sounds like a recipe for disaster. I don't know how to deal with this.

Not sure if classifying this as a bug is accurate. I don't know what the right course of action is here. This is expected behaviour right now.


Release 0.1.16

The controller namespace adjustment requires us to make a new point release for future SDK work.

Requires #288


Add APIResourceListing class

This change is

Coverage decreased (-3.0%) to 45.899% when pulling 5713abbcdccb7dd31bd56f8a91aa4f604d5efcc2 on annawzz:a329191765491209_move_get_listing into d90f7d6950630cda031c51fdab35501677562856 on openprocurement:a258001251842882_refactoring.

Coverage decreased (-3.0%) to 45.899% when pulling 5713abbcdccb7dd31bd56f8a91aa4f604d5efcc2 on annawzz:a329191765491209_move_get_listing into d90f7d6950630cda031c51fdab35501677562856 on openprocurement:a258001251842882_refactoring.


PMM-12631 added PMM-T1830 check to test

https://pmm.cd.percona.com/blue/organizations/jenkins/pmm2-ui-tests/detail/pmm2-ui-tests/40995/pipeline


404 page not found

WHEN I'm request http://localhost:8080/index.php/index/index it's error 404.
Anything else path is ok, like http://localhost:8080/index.php/contact/index

You raised this yesterday, and it was flagged as a duplicate ... Duplicate of #3451.


Invalid characters in page titles cause a trouble for Exporting Section to Hierarchial Files

NoteWidget won't generate hierarcial files, if their page titles contain invalid characters for Windows file names. I notice that you already deal with the issue when you export a single file, by replacing these invalid characters with "-".
Ref.
https://gist.github.com/doctaphred/d01d05291546186941e1b7ddc02034d3
https://stackoverflow.com/a/12924582/5746539

Fixed.


Demo/IE11: Double scrollbar when opening the property editor in demos.

Description
Another IE11 special:
When the property Editor in the demo files is opened in IE11, there is a double vertical scrollbar but you can't scroll up/down the content of the file to view/edit using the inner vertical scrollbar; however, touchpad works for scrolling.
Most visible with table-data editor that contains large content in basic examples/more rows tab demo.
For what it's worth, this is currently the case with other components as well.
Version
Data-grid: V1.2.3
Browser: IE11
Screenshot

@ppeyro This is px-demo issue since px-modal was changed, We don't do anything for that part of UI, so reopen bug there, thanks.

That was meant for us to fix later, that's why I marked the summary with "Demo".  Could you please reopen and label it as external dependency/GE response? Thanks.

There is nothing to fix on our side.

Closing


Precompiled assemblies still GPL?

On GitHub we see that the project is MIT, but on the HomePage it is still showing GPL.
But it also says "All downloads are for version 0.86.0, built on 2010/05/2".
Are there precompiled assemblies available under the MIT license, and for the latest versions of the source code?

The relicensing effort was after this version shipped, so strictly speaking we'd have to release a new version that is after the last author agreed to the relicensing (commit post the issue comment).

The MIT-licensed 1.0 version is on Nuget https://www.nuget.org/packages/SharpZipLib/1.0.0

Closing issue due to inactivity.


fixed #137

Codecov Report

Merging #200 into pyconkr2017 will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           pyconkr2017     #200   +/-   ##
============================================
  Coverage        96.98%   96.98%
============================================
  Files               10       10
  Lines              199      199
============================================
  Hits               193      193
  Misses               6        6

Continue to review full report at Codecov.

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


scripts: small fixes for the new add path venv

@seppewyns I modified your script because it was not immediately working


Shuffle offers before turning them into worker slots.

We've found that with few topologies running and limited resource demand, the iteration over the list of hosts with offers results in all worker slots being assigned to the same physical machine more often than not. This is less than ideal.
This change is to shuffle the offers before we make any slots on them, so as to distribute things more evenly.

Before, using grep "Schedule the per-topology slots:" nimbus.log
2017-10-09T21:29:27.485+0000 s.m.s.StormSchedulerImpl [INFO] Schedule the per-topology slots: {TestTopology, [worker4:31010, worker2:31000]}
2017-10-09T21:30:07.709+0000 s.m.s.StormSchedulerImpl [INFO] Schedule the per-topology slots: {TestTopology, [worker4:31008, worker2:31000]}
2017-10-09T21:32:18.431+0000 s.m.s.StormSchedulerImpl [INFO] Schedule the per-topology slots: {TestTopology, [worker4:31007, worker2:31000]}
2017-10-09T21:34:29.183+0000 s.m.s.StormSchedulerImpl [INFO] Schedule the per-topology slots: {TestTopology, [worker4:31007, worker2:31002]}
2017-10-09T21:35:19.465+0000 s.m.s.StormSchedulerImpl [INFO] Schedule the per-topology slots: {TestTopology, [worker4:31008, worker2:31000]}
2017-10-09T21:37:10.093+0000 s.m.s.StormSchedulerImpl [INFO] Schedule the per-topology slots: {TestTopology, [worker4:31007, worker2:31000]}
2017-10-09T21:39:30.887+0000 s.m.s.StormSchedulerImpl [INFO] Schedule the per-topology slots: {TestTopology, [worker4:31010, worker2:31000]}
2017-10-09T21:40:21.338+0000 s.m.s.StormSchedulerImpl [INFO] Schedule the per-topology slots: {TestTopology, [worker4:31008, worker2:31000]}

Of 8 slot assignment rounds, distribution of assignments to workers (x,y) are at the following frequencies:

assignments
frequency

(1,2)
0

(1,3)
0

(1,4)
0

(2,3)
0

(2,4)
8

(3,4)
0

After a re-deploy, grepping for the same code on the same file:
2017-10-09T21:42:01.926+0000 s.m.s.StormSchedulerImpl [INFO] Schedule the per-topology slots: {TestTopology, [worker4:31007, worker2:31000]}
2017-10-09T21:43:02.382+0000 s.m.s.StormSchedulerImpl [INFO] Schedule the per-topology slots: {TestTopology, [worker3:31002, worker2:31000]}
2017-10-09T21:44:33.198+0000 s.m.s.StormSchedulerImpl [INFO] Schedule the per-topology slots: {TestTopology, [worker3:31005, worker1:31000]}
2017-10-09T21:45:13.678+0000 s.m.s.StormSchedulerImpl [INFO] Schedule the per-topology slots: {TestTopology, [worker2:31000, worker1:31000]}
2017-10-09T21:46:54.442+0000 s.m.s.StormSchedulerImpl [INFO] Schedule the per-topology slots: {TestTopology, [worker4:31007, worker3:31002]}
2017-10-09T21:47:34.729+0000 s.m.s.StormSchedulerImpl [INFO] Schedule the per-topology slots: {TestTopology, [worker2:31002, worker1:31000]}
2017-10-09T21:49:05.387+0000 s.m.s.StormSchedulerImpl [INFO] Schedule the per-topology slots: {TestTopology, [worker2:31000, worker1:31000]}
2017-10-09T21:49:55.716+0000 s.m.s.StormSchedulerImpl [INFO] Schedule the per-topology slots: {TestTopology, [worker4:31004, worker2:31005]}

Of 8 slot assignment rounds, distribution of assignments to workers (x,y) are at the following frequencies:

assignments
frequency

(1,2)
3

(1,3)
1

(1,4)
0

(2,3)
1

(2,4)
2

(3,4)
1

LGTM!

@JessicaLHartog : LGTM too.  One minor note I'd like to record is that this doesn't "shuffle offers" directly; i.e., it shuffles groups of offers by their host.   Just to be precise.

@erikdw Yea, it doesn't actually shuffle the offers themselves either, it just shuffles the order in which we access hosts before making slots on them. Though I feel like that's a mouthful. I can change the commit message if you want. Suggestions?

Nah, I would just ship it, just something I thought of.

Erik

On Oct 18, 2017, at 9:20 AM, JessicaLHartog<EMAIL_ADDRESS>wrote:
@erikdw Yea, it doesn't actually shuffle the offers themselves either, it just shuffles the order in which we access hosts before making slots on them. Though I feel like that's a mouthful. I can change the commit message if you want. Suggestions?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


'Unused variable' warnings from ivory_asserts.h

HI! We faced 'unused variables' warnings with -Wall. The source of the problem is the following definitions in ivory_asserts.h:
#else /* IVORY_TEST */

#define REQUIRES(arg)
#define ENSURES(arg)
#define ASSUMES(arg)
#define ASSERTS(arg)
#define COMPILER_ASSERTS(arg)

#endif /* IVORY_TEST */

Next is an example of generated code which emits warnings:
    int32_t n_cse1 = (int32_t) -(int32_t) 1;
    COMPILER_ASSERTS((bool) ((bool) ((int32_t) 0 < (int32_t) 1024) && (bool) (n_cse1 <= (int32_t) 0)));

Here, the n_cse1 variable is only used in COMPILER_ASSERT, which maps its argument to nothing in the default case.

Yes, this is a known problem that is at the intersection of common subexpression elimination (CSE) and ifdefs. The CSE helps with readability and code size dramatically.
I would suggest using -Wno-unused-variable; for Ivory generated code, those warnings shouldn't be needed to find bugs.
I would prefer not to decide at Ivory compile-time whether to to use assertions or not, so that the same generated code can be used with or without assertions.
Do you have another proposed solution?

Well, I thought about re-definition of empty macros with popular cast-to-void trick[1] in the following manner:
#define COMPILER_ASSERTS(arg) ((void) (arg))

AFAIK, with this declaration compiler has a chance to keep the arg expression in final code, but in practice it optimizes it out. But I am not sure, further research is needed.
[1] http://stackoverflow.com/questions/4178695/c-what-is-the-purpose-of-casting-to-void

I believe that would work. Would you mind testing and doing a pull request?

I don't believe (void)(something) will always work as expected, i. e. as nop. A better solution would be something like
#ifdef IVORY_TEST
    COMPILER_ASSERTS_BLOCK(init_block, cond) do { init_block; assert(cond) } while(0);
#else /* IVORY_TEST */
    COMPILER_ASSERTS_BLOCK(init_block, cond)
#endif /* IVORY_TEST */

    COMPILER_ASSERTS_BLOCK(
        (
            int32_t n_cse1 = (int32_t) -(int32_t) 1;
        ),
        ((bool) ((bool) ((int32_t) 0 < (int32_t) 1024) && (bool) (n_cse1 <= (int32_t) 0)))
    );

@cblp, but then the Ivory common subexpression elimination pass, creating n_cse1, needs to know if the variable is only used within the assertion, I think. While this is possible, it starts complicating the (Ivory) compiler. If we want to go down that path, we might as well make the use of assertions be something that has to be given at Ivory compile-time. As mentioned, I think it's preferable to defer that decision to C compile-time.


Improve order of "Main Focus" List

In short:

Rename Layer1 & 2
Add Layer3 to auto-tag eCash applications
Re-order items to make things easier on the eyes

Note that we don't do LTS for education, which is why it's missing there.

One nit might be to add a space between layer 1, layer 2, and layer 3. Other than that, LGTM.


[BUG] torch.distributed

INFO:torch.distributed.nn.jit.instantiator:Created a temporary directory at /tmp/tmp312csgvg
INFO:torch.distributed.nn.jit.instantiator:Writing /tmp/tmp312csgvg/_remote_module_non_scriptable.py

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

@vyomakesh09 tried to fix now


Manually revert PR #2722 and add deprecations/checks

See: https://github.com/deeplearning4j/nd4j/pull/2722#issuecomment-373933362
Github won't let me automatically revert the PR, so I'm doing it manually.
Also adding check + deprecation.

@raver119 ok, I'll merge this and open an issue to separately handle the removal of the setters/enum etc properly.

cool thanks!

LGTM. Thank you!

@enragedginger np, and thanks for flagging the original issue


[FLINK-9138][docs][tests] Make ConfigOptionsDocsCompletenessTest an IT case

What is the purpose of the change
This PR modifies the ConfigOptionsDocsCompletenessTest to be an IT case instead. You can now regenerate the docs without having to skip tests, since the docs are now generated before the completeness check.

+1


Update storage docs for content-addressability

Signed-off-by: Tonis Tiigi<EMAIL_ADDRESS>Mostly the text already described the new system better, as before we really didn't have a separate concept of a layer. All images really only had one layer that was unique to them and a pointer to the parent.
Big difference is that layer IDs are not currently visible any more. This means you can't easily preview the files on the disk by container/image ID. We could provide some helper tools for that later. AUFS files are still stored in the same place, only the IDs are different.
Other changes that we may want to communicate better:

Read-only layers are stored by crypo hash. Read-write layers ares stored by random UUID.
Layer IDs have "sha256:" prefixes (but as they are not visible it doesn't matter much).
We don't ever create any new empty layers any more. But old images still have them so it would be wrong to just remove them from ubuntu:15.04 diagrams.

Let me know if there are more docs that need updating.
@moxiegirl @thaJeztah

and /cc @nigelpoulton :-)
I'll have a look tomorrow to see if we need other changes

@tonistiigi Thank you.  I'm a bit swamped at the mo..so I'll be looking closer in a day or two. Nigel's commentary here would be super helpful too.

ping @moxiegirl do you want to move forward with this PR, or do a more extensive rewrite?

@thaJeztah I think it warrants a proper check through the docs in light of the changes. @moxiegirl tell me if you disagree.
I can do this tomorrow if you want.  I'll go through the changes (PR 17924) and vet the docs for any potential changes and make some suggestions.
LMK.

@nigelpoulton good to go. I'll email you.

I'll close this PR, thanks for starting the work on this @tonistiigi (and looking forward to your changes, @nigelpoulton !)

Oh, let me keep it open for now, then @nigelpoulton can carry

@thaJeztah @tonistiigi @moxiegirl Just wanna check..... I'm going through the docs and wanted to check whether engine 1.10.0-dev has this PR merged and is valid for me testing and updating outputs etc in the docs?
I'm also aware of this from @tonistiigi

@nigelpoulton yes, the PR is merge in master, so you can either build master, or download from https://master.dockerproject.org (the experimental channel probably also includes this change)

@tonistiigi A few quick questions for clarification/my understanding....

Is this PR merged in 1.10 and later?
Are we formally calling images pulled by engines with this PR merged "flat images"?
The PR readme says that when graph metadata is migrated as part of an engine upgrade the old metadata is kept. Where is the new and old metadata? E.g. After an upgrade from 1.9.1 to 1.10.0-dev I only have /var/lib/docker/0.0/../..
Will engines with this PR merged have the "0.0" directory under /var/lib/docker/ or is this just part of the experimental build?
Are image ID's based on a hash of the images config file - e.g. /var/lib/docker/0.0/image/aufs/imagedb/content/sha256/)
From the PR readme: "Images can securely share underlying layers" < Is the new content addressable model more secure than the old way?

Thanks!
@moxiegirl @thaJeztah

@nigelpoulton

Is this PR merged in 1.10 and later?

Changes that this PR is describing were merged with #17924

Are we formally calling images pulled by engines with this PR merged "flat images"?

It's a term we use internally to distinguish images that don't require parent chain. There may be a better way to call them.

The PR readme says that when graph metadata is migrated as part of an engine upgrade the old metadata is kept. Where is the new and old metadata? E.g. After an upgrade from 1.9.1 to 1.10.0-dev I only have /var/lib/docker/0.0/../..

We don't change old files. Old image configs are in graph/ for example but docker does not use them any more.

Will engines with this PR merged have the "0.0" directory under /var/lib/docker/ or is this just part of the experimental build?

This is part of a userns feature in #12648 not content addressability. I think  currently it is only for experimental, but userns should land on stable for v1.10. The directory scheme could change though. One alternative is smth like /var/lib/docker/aufs/0.0/layers.

Are image ID's based on a hash of the images config file - e.g. /var/lib/docker/0.0/image/aufs/imagedb/content/sha256/)

Yes, they are the same thing.

From the PR readme: "Images can securely share underlying layers" < Is the new content addressable model more secure than the old way?

Yes, it is more secure because it avoids all collisions for different data. The sharing aspect itself is not a security feature though.

Much appreciated @tonistiigi

Ping @moxiegirl?

@tonistiigi Thanks for the change and the assist on @nigelpoulton questions. LGTM on this.

@tonistiigi is there an easy way to map image layer IDs as shown with docker pull to directories under /var/lib/docker/../..
Cheers.

@nigelpoulton What you see on pull are the IDs in the distribution manifest. If that ID is sha256:abc, then /image/overlay/distribution/diffid-by-digest/sha256/abc contains the actual layer ID(the one in image conf, also the ID that is stable). If layer ID is sha256:def then image/overlay/layerdb/sha256/def/cache-id contains the graphdriver ID.

@tonistiigi thanks!


Update to PureScript 0.15

package-set psc-0.15
ESM style FFI modules
fixed type-error in Test/App.purs/Main

Sorry missed some tests - one moment...

Hi - there are a few problems left - mainly with the tests and with examples.
The performance tests are compiling but both test time-out after 30sec. - to be honest: I have no idea why - any hints?
The other issue is that the examples seem to import halogen-storybook so I guess I'll have to look at converting this first - I'll try my luck tomorrow.

seems for me puppeteer is not working (it does not launch a browser) on my machine
it's probably because I have a more or less non-standard chrome installation (it's installed via AUR into /opt/google/chrome and by default not in path ... adding it does not help though)
I'm looking into it but I guess if the examples would compile this would probably work in CI.
storybook is quite old and I think not actively maintained - any thought on if I could drop this example?

Turns out there seems to be an issue with the way test.js is bundled.
The output if just flat functions declarations and one of those is
// output/Web.HTML.Window/foreign.js
function document(window2) {
  return function() {
    return window2.document;
  };
}

which will fail in a browser (there is already a top-level document):
Uncaught SyntaxError: Identifier 'document' has already been declared
    at test.js:1:1`

is there a way to use something like global name with spago bundle-app?

I've found a fix for the performance-test (just tell spago to minify the bundled-app so that document is renamed) - no idea what to do with the storybook example.
@thomashoneyman any idea?

Seems I've got it working.
Merging should probably not happen till halogen-storybook was upgraded so there is no need to overwrite this dependency any more.
I've queued another pull request for that also.
Again sorry for this messy PR :(


npm package?

not sure if this falls into the category of "other JS lint or build tools" you'd rather avoid introducing - but a published npm package for this would be great! discoverability, ability to pull upstream changes, &etc

I second this. I want to try this out, but without npm support, this would make my release cycle more complicated.

@joaosa - would recommend reviewing the code and then pulling it into your own source tree, it's unlikely that there will be significant modifications to the codebase in the near future.


Create DSR access package export

Description
The will use the access request json that's created by the DSR to fill in the export package. It will consist of a few steps:
The file/folder structure will work like this:

root index page containing a list of datasets: ./index.html
index page for each dataset containing a list of collections ./dataset/index.html
index page for each collection containing a list of items ./dataset/collection/index.html
individual page for each item ./dataset/collection/1.html

The exact folder structure can change but there needs to be some folder nesting to avoid file name clashing

Covered by https://github.com/ethyca/fides/pull/3427

moving to done


Fix: Adding checks before we check for disallowCopy

Description
Sentry#6030 error when other items in the list widget expect for the first item are copied.
Sentry#6167 error when any widget inside a tab is deleted and before the undo toast goes away if the user deletes the parent tab and manages to click on undo.
Fixes #6030
Fixes #6167
FIxes #6168

if no issue exists, please create an issue and ask the maintainers about this first

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce.
Please also list any relevant details for your test configuration.

Test A
Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:red_circle: Total coverage has decreased
// Code coverage diff between base branch:release and head branch: fix/6030

Status
File
% Stmts
% Branch
% Funcs
% Lines

:red_circle:
total
53.38 (-0.01)
34.97 (-0.01)
31.5 (-0.01)
53.93 (-0.01)

:red_circle:
app/client/src/sagas/WidgetOperationSagas.tsx
43.97 (-0.32)
30.4 (-0.13)
48.31 (-1.12)
44.23 (-0.36)

@marks0351 I am still getting Cannot read property 'defaultProperties' of undefined error for #6167
https://www.loom.com/share/91d59924f96547959686ce26949d993d
#6030 This is working fine.

@marks0351 I am getting error on undo tab widget for issue #6167
https://www.loom.com/share/750dbb1b4aca4e50914f3aba5a89b306

@marks0351 Working fine on latest deploy preview.

@marks0351 LGTM


Update Tekton Dashboard release url in docs

Tekton updated its documentation, including the url of the latest Tekton Dashboard Release. The release is not available via the old url anymore. See commit in Tekton repo: https://github.com/tektoncd/dashboard/commit/e549cc17cc146e9a1d3873e80c947e2ca8ebedf7#diff-162b45a313f5f057a233411edbe31e72a13185f4df0ae0e1af2c13521bc05d5aL53

Thanks @nf3lix for the contribution.
Could you please next time create an issue first. It would easier to track release changes
https://github.com/apache/camel-karavan/issues/678


Tests: import_all_modules

Proposed changes
Test importing all modules.
The idea is simple: there are definition in __init__.py files and other files such as settings.py, configurations.py, etc. Simply importing these will execute their code and in that sense is preferable over using # pragma: no cover.
Fixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[ ] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[ ] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[ ] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have locally run services that could be impacted and they do not present failures derived from my changes

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

This will result in failures of the package command tests:

TestPackages.test_lock
TestPackages.test_lock_check_fail

This needs to be investigated. Usage of subprocesses may prevent this, and may well be related to issues #1590 and #1657

the issue is interesting but not relevant. Two of the packages lock command tests are flaky

failures:================================== FAILURES ===================================
___________________________ TestPackages.test_lock ____________________________

self = <tests.test_autonomy.test_cli.test_packages.TestPackages object at 0x000002208433D588>

    def test_lock(self) -> None:
        """Test lock"""

        target = "autonomy.cli.packages.get_package_manager"
        with mock.patch(target, return_value=mock.MagicMock()) as m:
            with mock.patch("sys.exit") as sys_exit_mock:
                result = self.run_cli()
                assert result.exit_code == 0
                assert "Updating hashes..."  Called %s times." %
                   (self._mock_name or 'mock', self.call_count))
>           raise AssertionError(msg)
E           AssertionError: Expected 'get_package_manager' to have been called once. Called 0 times.

c:\hostedtoolcache\windows\python\3.7.9\x64\lib\unittest\mock.py:859: AssertionError
______________________ TestPackages.test_lock_check_fail ______________________

self = <tests.test_autonomy.test_cli.test_packages.TestPackages object at 0x00000220834CC348>

    def test_lock_check_fail(self) -> None:
        """Test lock --check failure"""

        DummyPackageManager = namedtuple("DummyPackageManager", "verify")
        return_value = DummyPackageManager(lambda *_, **__: 1)
        target = "autonomy.cli.packages.get_package_manager"
        with mock.patch(target, return_value=return_value):
            result = self.run_cli(("--check",))
>           assert result.exit_code == 1
E           assert 0 == 1
E             +0
E             -1

The failures somehow have to do with "autonomy.cli.packages.get_package_manager" not being mocked properly. I have pin-pointed the issue somewhat. It has nothing to do with sys.modules, sys.path, sys.metapath. Also cache invalidation using the importlib machinery does not resolve the issue. I find that is one does not import cli.packages module as part of the test, there are no failures.

I don't see the point of this PR. In fact, the modification of sys.modules is suboptimal.

I don't see the point of this PR. In fact, the modification of sys.modules is suboptimal.

if you look real closely, you'll see that sys.modules in not modified :eyes:
The only reason I opened this was to investigate why package lock command failed. It turns out to be an issue with the mock and, as I stated, not relevant. I fully agree with closing this PR.


How to change the API Endpoint

As far as I know, the open-webui can be configured to Ollama server and OpenAI.
Currently, I've developed an FastAPI application using the langchain and OpenAI. I could create the similar endpoints like Ollama.
Is there any solutions oepn-webui can work with customized APIs ?
Thank you

Create a Function or Pipeline adapter for it 💪


glucose & transcription PMID:18430926

increased level of glucose starvation gene mRNA during vegetative growth
decreased negative regulation of transcription by glucose
exact synonym: decreased glucose repression
related synonym: increased transcription of glucose starvation gene during vegetative growth
also see #2546
PMID:18430926 / 40c52ec90ce2de0e

increased level of glucose starvation gene mRNA during vegetative growth FYPO:0005287
decreased negative regulation of transcription by glucose FYPO:0005288

edit file: 6ed67908e769470d4cd5e32b2e31751cba8581c2
release: 177067ba0b96083275fece46904f9eb490e908ca


merge changes from 3.0 to 3.2

this is to merge the slimdown changed in to the 3.2 version

grrrr


Installation Documentation

Hi all,
I am trying to install fritz_exporter using Docker on my Synology NAS in order to read my Fritzbox 7490 via Prometheus.
I am struggeling with the setup.
How exactly to provide User and Password to fritz_exporter?
Can you support and update documentation?
Thx

Please take a look into the Running with Docker section of the readme: https://github.com/chr-fritz/fritzbox_exporter#running-with-docker
I can not provide any further documentation about running on Synology NAS as i don't have access to one.


Regarding login api url

Hi @alexandrtovmach
I want to tell you about one change you have to make in your code.
Like you are using this url

" https://api.instagram.com/oauth/authorize?app_id=${appId}&redirect_uri=${uri}&scope=${scope?.join(
","
) || "user_profile"}&response_type=code`;
};

"
But, it is working fine when it is redirecting to our given path and gives us the code that we are going to use for another access token.
but that code is not working in getting access token because you are using old URL.
Could you change the URL in your code?
The new URL is: https://api.instagram.com/oauth/authorize?client_id={client_id}&client_secret={clinet_secret}&redirect_uri={redirect_uri}&scope=user_profile,user_media&response_type=code
Thanks @alexandrtovmach

is thie Instagram Auth working?
I heard that it stopped working at some point..


Support decimal types in HTTP proxy

We want to be able to support decimal types in the HTTP proxy without the JSON library first converting to float, which would lose precision. The raw JSON should support it fine, since it is represented as a string in decimal format.

Handled by new msgpack serialization


Use DefaultSettings for curl proxy settings

Should fix issue #123
Changes:

Updated DefaultSettings to include curl proxy settings
Use DefaultSettings in HttpRequest helper
Update .gitignore for .idea folder and fix composer.json intendation

@eyecatchup Are you currently accepting pull requests?

Do we have something similar for user agent?

@prionkor See my last commit to this pull request, which allows to set it dynamically: https://github.com/eyecatchup/SEOstats/pull/129/commits/be4c91dd5b44e6912982ac038ef25eb176a54605
You can use my fork in composer until this pull request is accepted.

Got it! Thanks for your quick response :)


Replace deprecated render tag with function

I'm targeting branch 3.x cause it's a bugfix.
However it's not BC compatible with all symfony2 versions.

Fixes : No open issues.
Changelog

### Fixed : Change call of render function to make it compatible with Symfony greater than 3.0
Cf. https://github.com/symfony/symfony/blob/master/UPGRADE-3.0.md and Twig Bridge section

Subject

Change from a render tag to a render function

Another twig template with the render tag


Not an issue but a question

So I am trying to create a new label for certain applications and was wondering if the Team ID is necessary.. after running spctl it doesn't seem like a couple of the applications i want to install have it or its just not pulling it and was wondering if it was crucial or if the download URL name and other stuff will suffice.

nvm im dumb.. and figured it out.


Notsobot not responding

Every day about once or twice at different times of day I've checked to see if notsobot and I've heard from some people it only works a half hour a day but when I have tried when I have my free time it doesn't work at all.

The old bot (that uses commands with the prefix .) is basically dead. Use the prefix .. for the new, re-write bot.

The old bot (that uses commands with the prefix .) is basically dead. Use the prefix .. for the new, re-write bot.

do you still use the not responding notsobot or a different bot?

Use the one you've always been using, except use that new prefix.

???


prey creates crontab entry for root

NixOS already handles cron installation, disable prey generation of the crontab.

(triage) @domenkozar do you still want to fix thi?

Closing since no reaction (reopen if necessary).