Add README.md

I have compiled the necessary information for "New Submission for SciPy 2022 (SciPy Tutorials)" in a draft version in README.md.
@akaszynski @banesullivan @adeak If you have time could you review the contents?

I was going to commit my proofreading suggestions myself, but I don't believe I have commit rights to this repo. Could you please add the pyvista/developers team to this repo, @tkoyama010?

@adeak Thanks for review. I added pyvista/developers to administrator.

I added pyvista/developers to administrator.

Thank you @tkoyama010. Although admin rights might be too much. I think pyvista/developers only has write access to pyvista main repo for instance.
Also thanks for the work too :)

Excellent work @tkoyama010, thanks for getting this started. I'll be able to present, and might even be able to present there representing myself and potentially even Ansys.

Although admin rights might be too much. I think pyvista/developers only has write access to the pyvista main repo for instance.

@adeak  Now developers are maintainers now. If you want to be an Admin please mention it.

Let’s consider submitting this soon.

February 15    Tutorial submission deadline

How about submitting it on February 13?

@akaszynski @adeak @banesullivan Thanks for your help with the review. I'm proposing this content for the Scipy2022 Conference tonight. (Can someone APPROVE the changes? I need it for merging).

@tkoyama010, the deadline is extended, right? or do we need to submit tonight?

the deadline is extended, right? or do we need to submit tonight?

Yes, it is extended. I would have submitted it earlier if I didn't have any additional reviews, but @banesullivan gave it a useful review and I'll continue to elaborate.

Sorry for coming in late here! 😄 Thanks for all of your hard work on this!

@tkoyama010, thanks for your hardwork leading this! I made some minor changes. Ready to merge and we should submit soon here


KAFKA-7455: Support JmxTool to connect to a secured RMI port.

To connect to a secured RMI port (enabling remote JMX with password authentication and SSL), JmxTool should pass an envionrment map that contains relevant certification entry.

@omkreddy  Are there any plans to have this pull request being merged soon?

retest this please

@ijuma @omkreddy Could you help to review this minor improvement when you are available, thanks!

@murong00 Thanks for the PR. LGTM. Can you bump up the KIP-417 vote thread? We need one more binding vote to pass the KIP.

@omkreddy Binding vote via this thread, but I'm not sure whether it works.

retest this please

@murong00 Sorry for the delay. Merging to trunk.


Cannot read property 'Symbol(Symbol.iterator)' of undefined

The following code:
module Program

open System
open Fable.Import
open Fable.Core

[<EntryPoint>]
let main argv =
    let a = [ "prop" ==> "value" ]
    let b = createObj a
    0

Results in the following error
C:\Dev\Fable\lib\fable-core.js:977
      for (var i = 0, cur = null, iter = xs[Symbol.iterator](); ; i++) {
                                           ^

TypeError: Cannot read property 'Symbol(Symbol.iterator)' of undefined
    at Object.Seq.fold (C:\Dev\Fable\lib\fable-core.js:977:44)
    at Object.Util.createObj (C:\Dev\Fable\lib\fable-core.js:59:16)
    at C:\Dev\Fable\sample\node\react\Program.js:16:68
    at C:\Dev\Fable\sample\node\react\Program.js:17:5
    at Object.<anonymous> (C:\Dev\Fable\sample\node\react\Program.js:20:2)
    at Module._compile (module.js:425:26)
    at Object.Module._extensions..js (module.js:432:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:313:12)
    at Function.Module.runMain (module.js:457:10)

but the following code does work
module Program

open System
open Fable.Import
open Fable.Core

[<EntryPoint>]
let main argv =
    let b = createObj [ "prop" ==> "value" ]
    0

Yeah, I noticed that today too :)I forgot to add fields in this line (and of course JS doesn't complain at all). It should be fixed now.


Circular dependencies are now red

In this branch I have done the following:
Added basic test coverage through the Data class using RSpec
Implemented the feature
Added example file in lib to test behavior.
I am happy to discuss switching to another testing framework if you prefer, I simply chose what I am most comfortable with. Also, I am hoping for a better way to test the app then pollute it with the test classes.
Fixes #3

Finally all good

Perfect, now lets go through the changes 🏋

Comments have been addressed.

I see some changes are still added through the last couple days, should I wait a little before merging?

I looked to the changes and there are a lot of unrelated files and changes, I see a log file committed for example, and other files related to rails and initializers, can you go over the changes and make sure we only have what we need for the feature and nothing more?

I would wait, I am testing this build with a project I am working on and I noticed some scalability issues with the code. I'm still sussing those out and want to confirm that it works as expected with a very large code base.

Alright, the app is able to effectively find circular dependencies. I will do the remaining work to omit the Rails noise.

I ended up deleting the feature tests as they were too flaky. I've tested this with a large project and am happy with it.

@emad-elsaid Let me know if there are any remaining concerns

Thanks @steven-solomon for that contribution, I reviewed the changes locally now before releasing, and released 0.3.0 just now.


Provide optional release branch merging option

Would you be open to add another optional feature that does the following: whenever it finds a new release and tags it, it also looks for a branch with the name release-1.2.3, and if that exists try to merges that into master, but only if it can be done with a fast-forward merge. If that succeeded, it also deletes the branch. If the ff merge didn't work, it opens a PR to merge that branch into master. The whole thing could be opt-in via a config option for the action.
This is the backstory for this feature: I have a rewrite of PkgDev.jl that provides a tag function. When you call PkgDev.tag("MyPkg"), the following things happen:

it figures out what the next release version shall be (you can also specify that in the call to tag)
it will create a new branch release-1.2.3 for that version
it sets the version field in Project.toml to that version and commits
it modifieds the version field in Project.tomlto1.2.4-DEV` and commits
it pushes that branch to origin
it then uses Registrator.jl to open a PR against the registry where this package is registered (with support for public and private registries) that registers the new version

At that point it stops.
If TagBot would do the additional things that I mentioned above, then we would have a complete, super easy package tagging story, IMO. Essentially as a pkg dev I would call Pkg.tag("MyPackage"), tne then the bots would do everything else, from modifying the Project.toml, to opening PRs that trigger various checks.
I'd be happy to help write the code, just wanted to check whether this might be acceptable in this repo first :)

Bump, any progress on this? Now that package butler enables tagbot, this would be awesome to have :)

Sorry, I'm swamped for time lately. It'll happen in a couple weeks I'd wager.

Okay, I'm looking into this now. One question comes to mind:
Does it matter if this merge process happens before or after the release is created? One difference that I can think of is if we merge before we tag, we can use master as the release target and avoid the problem outlined in #10.
The more I think about this, I don't think the order matters at all, since the release is not attached to a Git branch but rather a Git commit. So if the merge is fast-forward as it should be, nothing actually changes. But I just want to make sure that this sounds sane.

Yes, I think that is right, the order doesn't really matter at all, so perfectly fine to first merge and then tag.
I guess the other case is that we can't fast-forward merge, because someone has pushed something to master in the meantime. I suggested above that in that case a PR could be opened to merge the release-1.2.3 branch into master, but I think the tagging should still just happen, right?

Yep, if we can't FF then a PR will be made, and the release will still be made but with the target being the commit SHA instead of master. I don't think we should use the release-x.y.z branch name as the target because then the "n commits to BRANCH since this release" will not be useful.


add support for categories frontmatter

resolves #129

atom:entry elements MAY contain any number of atom:category elements.

Rather than include one or the other, I guess we should include both post.category and all post.categories.
Oh Jekyll, sometimes I must try so hard to love you 😏

Sure! I'll update.
On Sep 20, 2016 5:24 PM, "Pat Hawks"<EMAIL_ADDRESS>wrote:

@pathawks requested changes on this pull request.
I have requested changes.
Sorry, I am still getting used to the new GitHub flow.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jekyll/jekyll-feed/pull/130#pullrequestreview-866080,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACHZWwWX3zddRwcEZHjSEj6h4GtmKnLBks5qsHlOgaJpZM4KCRtF
.

updated. included fix for #131 too.

fixed and squashed commits

I would love to get one more LGTM from @jekyll/plugin-core

to be fullproof I suppose category should be pushed into the categories array and ensured that the array is unique and just iterate over the categories.

@digitalvapor I think Jekyll does that already which is why I bring up the concern.

Jekyll does that already which is why I bring up the concern.

That means we could just get rid of lines 74-76 and leave this new for loop, which is awesome.
Trouble is, we don't currently have any tests for <category>.
@digitalvapor Would you mind adding to the fixture site a post with a category and a post with categories set in the front matter and adding a test to make sure that both output correctly?

sure!
On Sep 27, 2016 8:18 PM, "Pat Hawks"<EMAIL_ADDRESS>wrote:

Jekyll does that already which is why I bring up the concern.
That means we could just get rid of lines 74-76 and leave this new for
loop, which is awesome.
Trouble is, we don't currently have any tests for .
@digitalvapor https://github.com/digitalvapor Would you mind adding to
the fixture site a post with a category and a post with categories set in
the front matter and adding a test to make sure that both output correctly?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jekyll/jekyll-feed/pull/130#issuecomment-250061601,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACHZW6sNfK4TFskdgwlErbCjoq3arwBAks5qudyHgaJpZM4KCRtF
.

I was hoping to clean this up to get it ready to merge, but the branch has been deleted❗😑
Will instead get this across the finish line in #153

thanks for following up @pathawks. I think it was because I changed my username :man_facepalming:.


Fix response type bug

The last PR was in WIP, and I did more test today with that version, and I found that the message send along the grpc is not the type that defined in the proto, it was FileBoxChunk, which should be wrapped into the request/response message.
So I created two new helper function that wrap the FileBoxChunk message into the request/response message class, unwrap the request/response message to FileBoxChunk. These two functions are fully defined with typings, and also covered by tests.

Great job, and thank you very much for sync the gRPC code to the latest version!


Update limit order and stop loss contracts to monitor the swapping ratio instead of input token price

@fieldtheory123 please QA this with @webelf101 and @rootedbox so that it is working. I'm assuming this is not the DEX swap ratio, but the middleware ticket?

Closing. Not needed.


[RESOURCE] Gen Dread

Resource title
Gen Dread
URL
https://gendread.substack.com/about
Relevant tags (1 per line)
Healthy Living
Education
Resource Summary
A newsletter about staying sane during the climate crisis. Essays and interviews of an assortment of scientists, journalists and philosophers, from a team led by Stanford climate change and mental health researcher Britt Wray.
Relevance
Mental health resource, invaluable for the essay lovers
Other comments
No response

Sorry about the late review on this. Looks good! Just removing the "Individual Action" tag as I feel that this is more of an infromational resource (than something that spurs action within the community). Please correct me if you feel that I am wrong 😄

No worries, I won't challenge that removal. All good!


F-Droid

Hi
great app
Would it be possible to publish the app to F-Droid?
thank you for your work

@kollerlukas did you give up on this app? There was no release in 2 years – and no response here?

I am really sorry for not responding.
Currently I am really busy as a student and it is difficult for me to find time to work on personal projects.
On the other hand I don't use TODOList anymore. It would take a lot of work to update everything.
Also this app was never thought to be a fully maintained commercial app, it was more like a cool project to learn more about mobile and android applications.

No bad feelings, Lukas (that also explains the "silence" in versions for CameraRoll). If you say you have no time to work on it now, that's completely fine. If you plan to pick it up later, we can delay "actions" until then.
But reading between your lines, you'd rather give up this app but are afraid to admit it (even to yourself). That's of course fully OK as well (though we might be unhappy about it). Just state it straight, and I'd add a corresponding note to the app description in my repo – whichever way you decide.
And thanks for all your work!


Hello everyone, I based on quartz encapsulates a distributed task scheduling platform, called XXL JOB

Hello everyone, I based on quartz encapsulates a distributed task scheduling platform, called "XXL-JOB"。
The purpose is to contribute to open source, welcome you all to use。
大家好，我基于quartz封装了一个分布式任务调度平台，叫做 “XXL-JOB” 。
目的是为开源做贡献，欢迎大家使用啊。
https://github.com/xuxueli/xxl-job

Not an "issue" with quartz.


Error in running

Error while running python code

Please do not use this version, this repo has been EOL (End-of-life) for many years. Update to the new repo -> society


Rewrite git history to exclude big example notebook

I accidentally committed the bokeh plots, which grew this repo quite significantly. I'll be rewriting some of the history very aggressively from today, so consider recloning if you have a copy...

Removed this as best as I could; might still be hanging around in GH PR data


Cypress is a dependency

Describe the bug
It seems as part of this commit, Cypress got moved to dependencies object instead of keeping it in devDependencies
Expected behavior
Cypress should be in the devDependencies object
Screenshots

Additional context
npm audit now complains that there is vulnerability
> npm audit
# npm audit report

json-schema  <0.4.0
Severity: moderate
json-schema is vulnerable to Prototype Pollution - https://github.com/advisories/GHSA-896r-f27r-55mw
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/json-schema
  jsprim  0.3.0 - 2.0.1
  Depends on vulnerable versions of json-schema
  node_modules/jsprim
    http-signature  1.0.0 - 1.3.5
    Depends on vulnerable versions of jsprim
    node_modules/http-signature
      @cypress/request  *
      Depends on vulnerable versions of http-signature
      node_modules/@cypress/request
        cypress  >=4.3.0
        Depends on vulnerable versions of @cypress/request
        node_modules/cypress
          react-chrono  >=1.12.2
          Depends on vulnerable versions of cypress
          node_modules/react-chrono

6 moderate severity vulnerabilities

@Johannes-Andersen thanks for flagging this. cypress now is a dev dependency.


messaging/localization

Trying to send localised messages.
I'm getting the following error:
Invalid JSON payload received. Unknown name "title_loc_args" at 'message.notification': Cannot find field.

Notification type does not support titleLocArgs: https://firebase.google.com/docs/reference/admin/node/admin.messaging.Notification
It's only supported in AndroidNotification and ApsAlert.


chore(main): release 1.1.4

:robot: I have created a release beep boop
1.1.4 (2024-03-21)
Bug Fixes

Improve NPM module definition (ae6dbef)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/javalent/obsidian-utilities/releases/tag/v1.1.4 :sunflower:


Java 11 Support

Compiling is failing on Java 11.
object Cleaner is not a member of package sun.misc

Apache Spark suggests to use some JVM flags to use low level Java code https://spark.apache.org/docs/3.0.0/index.html#downloading, we may have a check with in the same way.

Opened this ticket in wrong repo. Closing.


Lightweight-charts not working on Android browser

Android version: 5.0 and 6.0.1
Lightweight-charts demo can not be rendered on Android browser, but Chartinglibrary of TradingView work correctlly, it is a serious problem. Does anyone have solutions?

I think the reason is in polyfills, see https://github.com/tradingview/lightweight-charts/issues/101#issuecomment-517117573.

I've imported pollyfill, it's not polyfill reason, the problem is canvas rendering a weird black and white content, I tried in two devices, Android5 and 6.0.1, both have the same issue.

Do you have any errors on the page? Can you please share screenshots what's going wrong?

There are no errors on the page, here are some screenshots in Android 6.0.1 native browser.

I tried on my old phone and it worked fine. Mi 4i with android 5.0.2, but I use latest chrome browser from play store.

I tried on my old phone and it worked fine. Mi 4i with android 5.0.2, but I use latest chrome browser from play store.

Hi, you should try in Android Native Browser, it not works!
I want use the chart in React-Native, so I need native browser support.
Any solutions?

We'll investigate it and will back here with updates.

@yuyic can you please check it on https://github.com/tradingview/lightweight-charts/tree/141-fancy-canvas branch?

It looks like Android browser doesn't like undefined as the first argument in fill method (we have a lot of errors about it - are you sure that you haven't any JS error?).

Thanks for your quick response, it works now!
Sorry I didn't do a complete debug, it's my fault, I just saw the errors...


Articles disappear when updating django-cms

djangocms-blog==0.5.0
django==1.8.17
When updating djangocms from 3.2.1 to >3.2.1, the blog list view shows no entries anymore. The paginator is still there.
Likewise, the blog post detail-view is reachable, but also shows no content.
Do you have any idea why that could be?

Just to clarify: this happens even when migrating to 3.2.2, right?

To clarify: yes, even when updating to 3.2.2.
And yes, djangocms is the only dependency updated.
And no, the site is in German only.

In the meantime, I've updated djangocms_blog to 0.6.3.
Still when updating djangocms from 3.1.1 to 3.1.2, all posts disappear.
Shall I try 0.7.x? Could that make any difference?

Which parler version are you using? If you output the primary key of the post in the template, is it printed?

Using parler==1.7.
The primary keys are printed indeed.
Based on that comment of yours I was able to find out that something is not quite right with my template include there... I'm using custom templates for the blog. To make matters worse, they are also written in jade (pyjade).
But I think I now know how to debug it. Will let you know.

As a matter of fact, the flaw seems to be in this line:
{% render_model post "abstract" "" "" 'truncatewords_html:TRUNCWORDS_COUNT'  %}

Sorry, that was wrong. The flaw is not in that line, but it is for sure in my template. Will have to investigate.
I'm closing the issue for now, as it doesn't really seem to be a problem with djangocms_blog.
Thanks for your help!

you're welcome feel free to open it again if you need

A little bit further down the debugging road, I'm inclined to think that there is indeed a problem with the {% render_model post "any_attribute" %} cms template tag... That's where things break.
Now as I said I'm using pyjade as a template processor, so it is difficult to really say who's to blame here. Also, djangocms_blog is the only app in the project whose templates use the render_model tag.
My workaround is to use {{post.abstract}} instead of {% render_model post "abstract" %}, which is fine for the list view. In the detail view, the render_model tag is somewhat crucial however.
I saw that the render_model tag is mentioned in the cms release notes for 3.2.4. Do you think it could have anything to do with that?

@creimers it's definitely that

Indeed. I have also tried 3.2.5, and there it's the same problem.

In the end: {{ post.some_attribute }} works, {% render_model post "some_attribute" %} doesn't. Right?

That's right.

Ciao @yakky. Have you had a chance to give this issue some more thought? I would really like to update my project's dependencies, otherwise I'm falling too much behind.

Not yet, sorry. I'll try to reproduce this today and will update you here

@creimers I create a POC project started with djangocms-blog 0.5 / django CMS 3.2.1 and I updated it to 3.2.2 and there is no issue in blog post display. Could you check this project  https://github.com/yakky/djangocms-blog-0.5-poc ? Master is with django cms 3.2.1 / cms_3_2_2

@yakky
Thanks for your effort. You're right, on both branches the posts list is perfectly visible...
Will have to keep debugging this I'm afraid.

I ended up removing all traces of render_model from the blog templates. It does the trick for now. Thanks again.

@creimers it's probably some interaction with pyjade, but I don't know it so can't think of a possible issue with it


featset actual row count in physical plan according to merged profile

Proposed changes
physical plan is already printed in profile.
however, it is hard to compare the estimated rows of sql operator and the actual rows.
In this pr, we get actual rows from merged profile, and set it to corresponding physical node in physical plan.
here is an example:
"PhysicalHashJoin[13890]@115  (  stats=17,964.27  actualRows=20499,  type=INNER_JOIN,  hashCondition=[(l_suppkey#19  =  s_suppkey#33)]"
the estmated rows is 17,964, the actual rows is 20499
Issue Number: close #xxx

run buildall

run buildall

run buildall

Can we pick this pr to branch-3.0 ?

based on ##35144

Can we pick this pr to branch-3.0 ?

YES


flag async_sent  is thread safe?

Version 1.x:
Platform windows:

on  src/win/async.c
void uv_process_async_wakeup_req(uv_loop_t* loop, uv_async_t* handle,    uv_req_t* req) {
assert(handle->type == UV_ASYNC);
assert(req->type == UV_WAKEUP);
handle->async_sent = 0;
if (handle->flags & UV_HANDLE_CLOSING)
{
      uv_want_endgame(loop, (uv_handle_t*)handle);
 }
else if (handle->async_cb != NULL) {
      handle->async_cb(handle);
}}

Read: Use _InterlockedOr8(&flag, 0);
Write: Use flag = 0;
that is safe ?
use InterLocked or memory fence to insteads?

Thanks for the report. It looks like a legitimate bug. The code seems to assume that volatile acts as a memory barrier.


rustup-install 0.1.0

What to do if the build fails?
At the moment contributors do not have access to the CI workflow triggered by StepLib PRs. In case of a failed build, we ask for your patience. Maintainers of Bitrise Steplib will sort it out for you or inform you if any further action is needed.
New Pull Request Checklist
Please mark the points which you did / accept.

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

Bash shell to install the Rust Toolchain and make it available in a Bitrise Workflow.
Example builds are available here bitrise-step-rustup (it's kinda barebone for now but I'll update the workflows later on).
Output of bitrise run audit-this-step on 0.1.0 (1ff9372e7e36e2d60003e4237709b53df0ef2c97):
➜  bitrise-step-rustup git:(main) bitrise run audit-this-step

  ██████╗ ██╗████████╗██████╗ ██╗███████╗███████╗
  ██╔══██╗██║╚══██╔══╝██╔══██╗██║██╔════╝██╔════╝
  ██████╔╝██║   ██║   ██████╔╝██║███████╗█████╗
  ██╔══██╗██║   ██║   ██╔══██╗██║╚════██║██╔══╝
  ██████╔╝██║   ██║   ██║  ██║██║███████║███████╗
  ╚═════╝ ╚═╝   ╚═╝   ╚═╝  ╚═╝╚═╝╚══════╝╚══════╝

  version: 1.49.3

INFO[19:01:46] bitrise runs in Secret Filtering mode
INFO[19:01:46] bitrise runs in Secret Envs Filtering mode
INFO[19:01:46] Running workflow: audit-this-step

Switching to workflow: audit-this-step

INFO[19:01:46] Step uses latest version -- Updating StepLib ...
+------------------------------------------------------------------------------+
| (0) script                                                                   |
+------------------------------------------------------------------------------+
| id: script                                                                   |
| version: 1.2.0                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2022-08-08T19:01:49+02:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
+ stepman audit --step-yml ./step.yml
INFO[19:01:49]  * [OK] Success audit (./step.yml)
|                                                                              |
+---+---------------------------------------------------------------+----------+
| ✓ | script                                                        | 2.45 sec |
+---+---------------------------------------------------------------+----------+

+------------------------------------------------------------------------------+
|                               bitrise summary                                |
+---+---------------------------------------------------------------+----------+
|   | title                                                         | time (s) |
+---+---------------------------------------------------------------+----------+
| ✓ | script                                                        | 2.45 sec |
+---+---------------------------------------------------------------+----------+
| Total runtime: 2.45 sec                                                      |
+------------------------------------------------------------------------------+

Submitting anonymized usage information...
For more information visit:
https://github.com/bitrise-io/bitrise-plugins-analytics/blob/master/README.md

Bitrise build successful

New Step
Thank you for the new Step share! The CI check might will fail due to our extended validation engine. Nothing to worry about yet, we will get back to you shortly.

 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.

Looking good @nick0602, thank you for creating this new step 🚀
Currently the CI validation is failing because the boolean input types should be wrapped in quotes for historical reasons.

Apologies for that! I applied the suggestions, fixed the boolean input values in the step repo as well, and updated the SHA in this fork to reflect the tag changes (https://github.com/nick0602/bitrise-step-rustup/releases/tag/0.1.0).
Audit run if needed:
➜  bitrise-step-rustup git:(main) ✗ bitrise run audit-this-step

  ██████╗ ██╗████████╗██████╗ ██╗███████╗███████╗
  ██╔══██╗██║╚══██╔══╝██╔══██╗██║██╔════╝██╔════╝
  ██████╔╝██║   ██║   ██████╔╝██║███████╗█████╗
  ██╔══██╗██║   ██║   ██╔══██╗██║╚════██║██╔══╝
  ██████╔╝██║   ██║   ██║  ██║██║███████║███████╗
  ╚═════╝ ╚═╝   ╚═╝   ╚═╝  ╚═╝╚═╝╚══════╝╚══════╝

  version: 1.49.3

INFO[14:11:27] bitrise runs in Secret Filtering mode
INFO[14:11:27] bitrise runs in Secret Envs Filtering mode
INFO[14:11:27] Running workflow: audit-this-step

Switching to workflow: audit-this-step

INFO[14:11:27] Step uses latest version -- Updating StepLib ...
+------------------------------------------------------------------------------+
| (0) script                                                                   |
+------------------------------------------------------------------------------+
| id: script                                                                   |
| version: 1.2.0                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2022-08-09T14:11:30+02:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
+ stepman audit --step-yml ./step.yml
INFO[14:11:30]  * [OK] Success audit (./step.yml)
|                                                                              |
+---+---------------------------------------------------------------+----------+
| ✓ | script                                                        | 2.64 sec |
+---+---------------------------------------------------------------+----------+

+------------------------------------------------------------------------------+
|                               bitrise summary                                |
+---+---------------------------------------------------------------+----------+
|   | title                                                         | time (s) |
+---+---------------------------------------------------------------+----------+
| ✓ | script                                                        | 2.64 sec |
+---+---------------------------------------------------------------+----------+
| Total runtime: 2.64 sec                                                      |
+------------------------------------------------------------------------------+

Submitting anonymized usage information...
For more information visit:
https://github.com/bitrise-io/bitrise-plugins-analytics/blob/master/README.md

CI check now passes but let me know if let me know if any other change is required, thanks a lot :rocket:


[Bug]: BingAI will say one less word in special cases

Contact Details
No response
What happened?
When I ask BingAI some questions it will search for, it will write one word less (at the beginning) when outputting
Here's an example:

Steps to Reproduce
1.Ask BingAI some questions that require an internet connection
2.When BingAI finishes searching the web and is ready to output, it will write one less word at the beginning
What browsers are you seeing the problem on?
Microsoft Edge
Relevant log output
No response
Screenshots

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Please see the following discord channel for common solutions for Bing. This particular issue could be IP related.
https://discord.com/channels/1086345563026489514/1143941308684177429

BingAI access is hacky and not fully supported. There are too many issues that can be specific to your location/IP/microsoft account, etc.

yeah, this has been going on for a while, (since bing is showing searching the web for:...) It one of the thing we have to accept due to the hacky nature of the integration.


stat.rs: Refactor to remove #[allow(clippy::cognitive_complexity)] #5881

Good work, thanks!

Thanks for you cooperation


Alternative random generator support for PSA: negative tests

The main goal of this pull request is to add negative tests for MBEDTLS_PSA_CRYPTO_EXTERNAL_RNG which was introduced in https://github.com/ARMmbed/mbedtls/pull/3895.
In addition:

I had to do some refactoring of psa_crypto_helpers.h.
The insecure implementation of mbedtls_test_enable_insecure_external_rng in the test suite is now disabled by default as requested in https://github.com/ARMmbed/mbedtls/pull/3895#discussion_r528245140.
I made a minor bug fix in RSA (bad error code in unusual circumstances) which needs backports → #3988.
I added some missing parts to include/mbedtls/config_psa.h so I could declare correct dependencies in new tests.
mbedtls_to_psa_error now favors low-level errors over high-level errors. This doesn't seem to make any difference to our tests, except in one of the new test cases added by this PR, which required it (RSA error + MBEDTLS_ERR_ENTROPY_SOURCE_FAILED should come out as PSA_ERROR_INSUFFICIENT_ENTROPY).

This pull request includes #3895 and will need to be rebased once #3895 is merged. I've raised it separately to facilitate the review of #3895 which was big enough as it is. The first new commit is 4547df5710ee6b3818fe8a33e7ee74a43b728b3f “Use mbedtls_test_ prefix on all PSA helper functions”.

Now that https://github.com/ARMmbed/mbedtls/pull/3895 is merged, I'm rebasing this PR on top of development. Changes compared to 44ee6a58b10cd40a86baf78d09dcf4fa52fbd2ca:

“Support PSA_WANT_xxx and MBEDTLS_PSA_BUILTIN_xxx for hashes” and “In old-style PSA configuration, define PSA_WANT_xxx” were merged through #3916, so they are no longer present here.
“Include psa_crypto_helpers.h in helpers.function” was tweaked due to two unrelated changes happening in the same place (this PR removes #include <test/psa_crypto_helpers.h> and development added some extra function definitions at the same place).

Some tests are now failing and I haven't acted on Ronald's review yet. The intermediate rebases of this PR are available at https://github.com/gilles-peskine-arm/mbedtls/tree/psa-external-random-test-1 through https://github.com/gilles-peskine-arm/mbedtls/tree/psa-external-random-test-6.

Now that https://github.com/ARMmbed/mbedtls/pull/3895 is merged, I'm rebasing this PR on top of development. Changes compared to 44ee6a58b10cd40a86baf78d09dcf4fa52fbd2ca:

“Support PSA_WANT_xxx and MBEDTLS_PSA_BUILTIN_xxx for hashes” and “In old-style PSA configuration, define PSA_WANT_xxx” were merged through #3916, so they are no longer present here.
“Include psa_crypto_helpers.h in helpers.function” was tweaked due to two unrelated changes happening in the same place (this PR removes #include <test/psa_crypto_helpers.h> and development added some extra function definitions at the same place).

Some tests are now failing and I haven't acted on Ronald's review yet. The intermediate rebases of this PR are available at https://github.com/gilles-peskine-arm/mbedtls/tree/psa-external-random-test-1 through https://github.com/gilles-peskine-arm/mbedtls/tree/psa-external-random-test-6.

@gabor-mezei-arm, thanks for looking at this.

@gabor-mezei-arm, thanks for looking at this.


[enhancement] checkbox doesn't appear properly (a suggestion on Material Design icon usage)

Let me start by saying thanks for this awesome work.
I'm sure that I'm not as good as you at Java and React-Native.
Probably you had thought about the following issue but you didn't for a valid reason on your own.

Indeed there is a checkbox icon in Material Design here https://design.google.com/icons/#ic_check_box.
And the icon color can be changed such as made in mrn library with together react-native-vector-icons. React-native-vector-icons library offers the icon usage as font. So the icon can be colored as you want.
Your theme logic is perfect. I mean just that there are already icons created perfectly by Android.
For instance there are MDL samples as well.
Also I've been discovering this awesome library and that whether I can contribute on or not.
ps: I've created a PR (#117) to correct checkbox appearance a bit.

Thank you for the reporting and the PR!
The reason why I wrote my own TickView is that I don't want to include resources (like icons) in this lib.
I think the ideal solution may be giving the flexibility to the users of the lib, one can use react-native-vector-icons, commercial licensed artworks..., besides the default built-in TickView.
I'll try to do it in the future releases.


docs: Add new copy-to-clipboard plugin

Adds a new section to the plugins page for a plugin that adds a "Click to copy" button to all preformatted code blocks.

Awesome!


Nit fixes in reviewing

@muga Reviewed embulk-filter-calcite. Almost lgtm. Added just some changes as results of reviewing.

Thank you for reviewing and fixing. In particular, thank you for upgrading calcite 1.11.0 👍


The Skin Manager goes back to version <IP_ADDRESS> after installing latest 2.0.1

After installing the latest version 2.0.1 and restarting Jellyfin(to enable the plugin) the version goes to <IP_ADDRESS>. Is jellyfin detecting it as higher version on the repo?

+1

The only solution that I found was to rename the 2.0.1 package to <IP_ADDRESS>. it would show as <IP_ADDRESS> but you'll have the latest version

Recommend moving this issue to a bug.
From some digging this issue is caused by an improperly built Jellyfin.Plugin.SkinManager.dll bundled in release version 2.0.1. The built dll still uses the old assembly version of <IP_ADDRESS> instead of 2.0.1.
When Jellfin loads the plugin at boot it uses the reported dll version instead of using the version in the Skin Manager meta.json file. This can results in broken references (such as a missing plugin image) which can be 'fixed' by changing the version in Skin Manager's meta.json file to <IP_ADDRESS> and creating a "Skin Manager_<IP_ADDRESS>" symbolic link that points to Skin Manager_2.0.1 in the jellyfin plugin folder ("/config/plugins" on Linux).

Recommend moving this issue to a bug. From some digging this issue is caused by an improperly built Jellyfin.Plugin.SkinManager.dll bundled in release version 2.0.1. The built dll still uses the old assembly version of <IP_ADDRESS> instead of 2.0.1.
When Jellfin loads the plugin at boot it uses the reported dll version instead of using the version in the Skin Manager meta.json file. This can results in broken references (such as a missing plugin image) which can be 'fixed' by changing the version in Skin Manager's meta.json file to <IP_ADDRESS> and creating a "Skin Manager_<IP_ADDRESS>" symbolic link that points to Skin Manager_2.0.1 in the jellyfin plugin folder ("/config/plugins" on Linux).

can you please fix it

Recommend moving this issue to a bug. From some digging this issue is caused by an improperly built Jellyfin.Plugin.SkinManager.dll bundled in release version 2.0.1. The built dll still uses the old assembly version of <IP_ADDRESS> instead of 2.0.1.
When Jellfin loads the plugin at boot it uses the reported dll version instead of using the version in the Skin Manager meta.json file. This can results in broken references (such as a missing plugin image) which can be 'fixed' by changing the version in Skin Manager's meta.json file to <IP_ADDRESS> and creating a "Skin Manager_<IP_ADDRESS>" symbolic link that points to Skin Manager_2.0.1 in the jellyfin plugin folder ("/config/plugins" on Linux).

can you please fix it

+1

Please fix it, same issue here

The only solution that I found was to rename the 2.0.1 package to <IP_ADDRESS>. it would show as <IP_ADDRESS> but you'll have the latest version

Can you please tell me how did you do that exactly? Would nice to have a workaround until it's fixed

AFAICT, issue is caused by the dll version inside of release 2.0.1 still being <IP_ADDRESS>. I guess during release somehow older version of dll was published.
@danieladov, can you please bump the version and trigger new release?

P.S. Image for skin not showing up in the plugin manager also caused by this. Jellyfin tries to fetch image from /Plugins/e9ca8b8eca6d40e785dc58e536df8eb3/<IP_ADDRESS>/Image but gets 404. And /Plugins/e9ca8b8eca6d40e785dc58e536df8eb3/2.0.1/Image get image normally.

Hi, I've just released a new version, it should be working now

Yep, after update correct version is loaded:

Also, image is showing up now)

Thank you!


666k firmware flash

My firmware is big so i added (https://github.com/SuperHouse/esp-open-rtos/issues/674)
    *sdklib*:*(.irom.* .irom.*.* .irom0.*)

I came here from https://github.com/SuperHouse/esp-open-rtos/issues/498
SuperHouse rboot is not working for a simple blink firmware...
I found another lib which flashes blink.bin but blink.bin size is 250k https://github.com/apiel/aboot/issues/2
I am lost now, is it possible to make an 666k bin flash?

rBoot is a bootloader, it does not affect the running of your code. In fact from the other issue you linked it does not look like you can get your code to compile and link, so you haven't even got to using rBoot yet.


feat: add visualization for no detection area

Signed-off-by: Tomohito Ando<EMAIL_ADDRESS>Description
Added visualization for the polygon tagged as no_detection_area
Related PR:

https://github.com/autowarefoundation/autoware.universe/pull/1530

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

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

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

[ ] The PR follows the pull request guidelines.

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

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

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

I discussed with @yukkysaito and some changes are needed.

[ ] change the name of no_detection_area to no_obstacle_segmentation_area and no_obstacle_segmentation_area_for_run_out
[ ] add library to be able to get lanelet polygon with any tag
[ ] add documentation for no_obstacle_segmentation_area and no_obstacle_segmentation_area_for_run_out

@yukkysaito
I added changes in this comment. could you please review?
https://github.com/autowarefoundation/autoware_common/pull/92#issuecomment-1220532184

@yukkysaito
Could you approve runnning the workflow?

@yukkysaito
Thanks!
Could you merge this PR because I don't have the write access?


Captcha validation issue

Hi, im facing an issue who block your code to submit the solution token, i have try multiple way to avoid this but the issue persist.
The thing is that the submit button of the website is enabled only when the MTCaptcha is completed by typing the right code, but when the code solve it using the solution token it doesn't enable this button , i have tried to remove the disabled attribute of the buton but i still get the error 'Please fill the captcha correctly'

Here the piece of code who archieve this :
				var mtcaptchaConfig = {
					"sitekey": "MTPublic-6dZ4hzZ6U",
					"theme":  "chrome" ,
					"lang": "fr",
					"loadAnimation": "false",
                    "verified-callback": function(state) {
						if (state.isVerified) {
							$('#captchaToken').val(state.verifiedToken);
							$('.btn-submit-vote').removeAttr('title').removeAttr('disabled');
                        }
                    }
				};
				(function(){var mt_service = document.createElement('script');mt_service.async = true;mt_service.src = 'https://service.mtcaptcha.com/mtcv1/client/mtcaptcha.min.js';(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(mt_service);
					var mt_service2 = document.createElement('script');mt_service2.async = true;mt_service2.src = 'https://service2.mtcaptcha.com/mtcv1/client/mtcaptcha2.min.js';(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(mt_service2);}) ();

@SPYNARY  Could you tell me the address of the page with the captcha, and the algorithm for how to get it?

Sure here it is :
https://top-serveurs.net/rdr/vote/last-red-line

I tried some manipulation and i think it may be possible to trick the page because the verification seem to be done on the client side

Here the piece of code who archieve this :
				var mtcaptchaConfig = {
					"sitekey": "MTPublic-6dZ4hzZ6U",
					"theme":  "chrome" ,
					"lang": "fr",
					"loadAnimation": "false",
                    "verified-callback": function(state) {
						if (state.isVerified) {
							$('#captchaToken').val(state.verifiedToken);
							$('.btn-submit-vote').removeAttr('title').removeAttr('disabled');
                        }
                    }
				};
				(function(){var mt_service = document.createElement('script');mt_service.async = true;mt_service.src = 'https://service.mtcaptcha.com/mtcv1/client/mtcaptcha.min.js';(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(mt_service);
					var mt_service2 = document.createElement('script');mt_service2.async = true;mt_service2.src = 'https://service2.mtcaptcha.com/mtcv1/client/mtcaptcha2.min.js';(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(mt_service2);}) ();

And if you want to fidn this you have to type sitekey in dev tool element

I also found in mtcaptcha documentation the mentionned part :
https://www.mtcaptcha.com/dev-guide-autoformvalidate

I also had an issue with your package idk why but it was returning an unsolvable error so i built my own using v2 api :
async function waitForTaskCompletion(clientKey, taskId) {
    while (true) {
        try {
            const res = await axios.post("https://api.2captcha.com/getTaskResult", {
                "clientKey": clientKey,
                "taskId": taskId
            });

            if (res.data.status === "ready") {
                console.log('Solution found');
                return res.data.solution;
            } else if (res.data.status === "processing") {
                console.log('In process, retry');
                await new Promise(resolve => setTimeout(resolve, 5000));
            } else {
                console.log('Solution search failed');
                throw new Error(`Error ${res.data.errorId}: ${res.data.errorDescription}`);
            }
        } catch (error) {
            throw error;
        }
    }
}

const res = await axios.post("https://api.2captcha.com/createTask", {
    "clientKey": "",
    "task": {
      "type": "MtCaptchaTaskProxyless",
      "websiteURL": "https://top-serveurs.net/rdr/vote/last-red-line",
      "websiteKey": mtCaptchaKey
    }
  });

 const solution = await waitForTaskCompletion('', res.data.taskId);

 const captchaAnswer = solution.token;

@SPYNARY Hi.
I checked the MTcaptcha solution on this site using 2captcha-ts, the captcha is solved in the service, the 2captcha service returns the token, but the site not accepts the token using the code described in this repository.
Sites can add additional protection methods, such as callback functions, or something else. In order to correctly use the token, it is necessary to figure out how the token is used on this site.

@SPYNARY  The easiest way is to use a different method of solving the captcha. Try using the Normal captcha method. To do this, you just need to take a screenshot of the captcha task and send it to the service, then the service will return the text from the image to you. After that, you will only have to enter the text in the text field. And then click on the required button.
Since the text in the task is case-sensitive, it is advisable to send an additional parameter case: true:

Okay perfect thank's a lot, that blow my mind since 1 day XD

@SPYNARY   Hi again, I made a simple demo, it works for me, but apparently you also need to use a proxy, since the number of votes is tied to the ip.
Demo:
import puppeteer from "puppeteer";
import { Solver } from "2captcha-ts";
const solver = new Solver("you_2captcha_api_key");

const sleep = (ms) => new Promise((res) => setTimeout(res, ms));

(async () => {
  const browser = await puppeteer.launch({
    headless: false,
    devtools: true
  });

  const [page] = await browser.pages();
  await page.setViewport({ width: 1080, height: 1024 });

  // Open target page that contains MTCaptcha.
  await page.goto("https://top-serveurs.net/rdr/vote/last-red-line");

  // show sometimes, depends on ip
  // await page.waitForSelector(".fc-consent-root");
  // await page.waitForSelector(".fc-cta-consent .fc-button-label");
  // await page.click('.fc-cta-consent .fc-button-label')

  await page.type('#playername', 'user3d3dd')
  await page.waitForSelector("#mtcaptcha-iframe-1");

  // Getting the frame
  const iframeElementHandle = await page.$("#mtcaptcha-iframe-1");
  const iframe = await iframeElementHandle.contentFrame();

  // Wait
  await sleep(2000);

  // Grab captcha image(`base64`)
  const captcha = await iframe.evaluate(() => {
    console.log(document.querySelector('.mtcap-image img'))
    const captcha = document.querySelector('.mtcap-image img').src
    console.log(captcha)
    return captcha
    });

  // Wait
  await sleep(3000)
  // console.log(captcha)

  // solve image captcha
  const res = await solver.imageCaptcha({
    body: captcha,
    regsense: 1
  });

  console.log("Answer:");
  console.log(res);

  const frameHandle = await page.$("#mtcaptcha-iframe-1");
  const frame = await frameHandle.contentFrame();
  await frame.click('#mtcap-inputtext-1')
  // type captcha answer
  await frame.type('#mtcap-inputtext-1', res.data)

  await sleep(3000)

  // click submit btn
  await page.click('button[type="submit"]')

})();

@SPYNARY   Please check or this method works for you.

It work, thanks ;)


Part 2 of the big training refactor

This is on top of #458, and implements GPU training using Kubernetes Jobs.
In principle, this could also allow us to train in parallel (or have different queues for different models) but this is not implemented yet.
Not tested yet, but I'd love a review of the design before I dig deep into bugfixing.
Fixes #430 and makes progress towards a number of other issues.

This pull request introduces 23 alerts when merging aee0dad into b292d5f - view on LGTM.com
new alerts:
* 21 for Property access on null or undefined

* 1 for Self assignment

* 1 for Illegal invocation

Wow this is a new record. As I said, I did not test this :joy:

Pull Request Test Coverage Report for Build 1487

260 of 330 (78.79%)  changed or added relevant lines in 16 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.5%) to 65.114%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

training/tasks/prepare-training-set.js
20
21
95.24%

training/tasks/train.js
27
28
96.43%

training/tasks/update-dataset.js
10
11
90.91%

training/run-training-task.js
37
40
92.5%

scripts/download-dataset.js
30
34
88.24%

training/daemon.js
15
19
78.95%

training/training_job.js
23
27
85.19%

nlp/nlp_model.js
7
14
50.0%

training/backends/local.js
27
34
79.41%

util/abstract_fs.js
40
78
51.28%

Files with Coverage Reduction
New Missed Lines
%

model/entity.js
2
65.71%

training/training_job.js
3
73.61%

Totals

Change from base Build 1481:
0.5%

Covered Lines:
6376

Relevant Lines:
9228

💛  - Coveralls

Let's merge this, and fix any remaining issue in a follow-up PR after we test in the staging cluster.


Plan to Remove Custom Code and Still have Job Board Implemented

From here we should have a discussion of ways to improve raytha core to make both the help center and job board easier and more intuitive to build.  Task to be specified

Implement top item from roadmap: https://github.com/RaythaHQ/raytha/discussions/172
https://github.com/RaythaHQ/raytha/issues/177
Then use this feature to replace custom code to still have job board implementation

Added PR:
https://github.com/RaythaHQ/raytha/pull/183
Refactored with functions:
https://raytha.awards-dev-test-server.office.getfullstack.co:8006
https://raytha-job.awards-dev-test-server.office.getfullstack.co:8006
<EMAIL_ADDRESS>/ 12345678


Development of ExcitedDampedPendulum dynamic system

The systems require reimplementation ( improvement of innit method and implementation of components method).

Done: class fixed


fix(web/appeals): fix upload file on statements form (boas-185)

Describe your changes
Passing Multer().none() to the express middleware fixes the JsDocs error but creates a new one when trying to upload files.
Now the whole instance of multer() is passed and the error is just ignored.
Also,
No reason to have this working differently on the test env.
Issue ticket number and link
https://pins-ds.atlassian.net/browse/BOAS-185
Type of change 🧩

[ ] 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)
[ ] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[ ] I have performed a self-review of my own code
[ ] I have double checked this work does not include any hardcoded secrets or passwords
[ ] I have made corresponding changes to the documentation
[ ] I have provided details on how I have tested my code
[ ] I have referenced the ticket number above
[ ] I have provided a description of the ticket
[ ] I have included unit tests to cover any testable code changes

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


libcurl-devel + homebrew gcc

Hi!
Having issues installing bcbio-nextgen on a new machine (centos 7).
With this command:
export CC=${CC:-which gcc} && export CXX=${CXX:-which g++} && export SHELL=${SHELL:-/bin/bash} && export PERL5LIB=/usr/local/lib/perl5:${PERL5LIB} && /usr/local/bin/brew install -v --env=inherit  --ignore-dependencies  git
The first problem is apparently solved by installing libcurl-devel on the machine, which might be a good idea to add to the requirements.
But then, this complaint arrives:
Error: The requested Homebrew GCC was not installed. You must:
brew install homebrew/versions/gcc44 .
Trying this :
$ brew install homebrew/versions/gcc44
==> Installing gcc44 from homebrew/homebrew-versions
==> Installing dependencies for homebrew/versions/gcc44: gmp4, mpfr2, hom
==> Installing homebrew/versions/gcc44 dependency: gmp4
Error: homebrew/versions/gmp4 cannot be built with any available compilers.
To install this formula, you may need to:
brew install gcc
Trying this:
$ brew install gcc
==> Installing dependencies for gcc: zlib, gmp, mpfr, libmpc, isl
==> Installing gcc dependency: zlib
Error: zlib cannot be built with any available compilers.
To install this formula, you may need to:
brew install gcc
... and so on..
gcc 4.8.3-9 is the version installed on the system. I'm trying to get homebrew to point to gcc in /usr/bin/gcc, but I can't seem to figure out how. Any help is appreciated!
//Pär

Pär;
Sorry about the issues with the build. Are all of these errors coming from trying to build git, or another dependency? I pushed a fix that makes bcbio less aggressive about trying to install git since it seems to be leading to lots of issues. If you rm -rf tmpbcbio-install and then re-run your install/upgrade it should hopefully skip it now and build cleanly.
libcurl-devel is a required dependency and we currently list those here (https://bcbio-nextgen.readthedocs.org/en/latest/contents/installation.html#isolated-installations). Definitely let us know if we're missing anything else.
Hope this fixes your issues and gets things installing cleanly.

Hi,
sorry about that. Sometime it happened to me. Don't not exactly the
reason behind but this post helped me
https://github.com/Homebrew/linuxbrew/issues/137. They say maybe is
because you don't have the /usr/bin/gcc4.*. You will see some work around.
hope this help, or maybe @chapmanb has a better solution.
On 09/09/2015 08:21 AM, Pär Larsson wrote:

Hi!
Having issues installing bcbio-nextgen on a new machine (centos 7).
With this command:
export CC=${CC:-|which gcc|} && export CXX=${CXX:-|which g++|} &&
export SHELL=${SHELL:-/bin/bash} && export
PERL5LIB=/usr/local/lib/perl5:${PERL5LIB} && /usr/local/bin/brew
install -v --env=inherit --ignore-dependencies git
The first problem is apparently solved by installing libcurl-devel on
the machine, which might be a good idea to add to the requirements.
But then, this complaint arrives:
Error: The requested Homebrew GCC was not installed. You must:
brew install homebrew/versions/gcc44 .
Trying this :
$ brew install homebrew/versions/gcc44
==> Installing gcc44 from homebrew/homebrew-versions
==> Installing dependencies for homebrew/versions/gcc44: gmp4, mpfr2, hom
==> Installing homebrew/versions/gcc44 dependency: gmp4
Error: homebrew/versions/gmp4 cannot be built with any available
compilers.
To install this formula, you may need to:
brew install gcc
Trying this:
$ brew install gcc
==> Installing dependencies for gcc: zlib, gmp, mpfr, libmpc, isl
==> Installing gcc dependency: zlib
Error: zlib cannot be built with any available compilers.
To install this formula, you may need to:
brew install gcc
... and so on..
gcc 4.8.3-9 is the version installed on the system. I'm trying to get
homebrew to point to gcc in /usr/bin/gcc, but I can't seem to figure
out how. Any help is appreciated!
//Pär
—
Reply to this email directly or view it on GitHub
https://github.com/chapmanb/bcbio-nextgen/issues/1008.

Great!
I actually managed to move past this just now - but have no idea how I did it. Thanks, Ipantano. I'll take a look at that issue. I have another machine i have to install on as well.
Sorry, missed the libcurl-devel dependency (not actually doing an isolated installation.)

Looks like this got resolved-- @chapmanb has been a hero unwinding the linuxbrew dependencies in place of bioconda so hopefully we won't have these issues moving forward.


Normalize angle for index in radialLinear scale

getIndexAngle returns a normalized angle value so that it stays between 0 and PI * 2. For the unit tests, support for textAlign property is added in the mock context.
Master: https://jsfiddle.net/nagix/gynkp7ec/

This PR: https://jsfiddle.net/nagix/ef7r0w8h/

Fixes #6160

Thanks @nagix


settings from rubocop.yml are ignored

I have an example haml file:
- some_val = 123456
= some_val + 1

My rubocop.yml says:
Style/NumericLiterals:
  Enabled: false

When cding to /path/to/project and running haml-lint test.haml I get 1 file inspected, 0 lints detected. Works.
Sublime Console tells me the following:
SublimeLinter: #17 linter.py:1636     Running ...

  /path/to/project  (working dir)
  $ /path/to/.rvm/bin/rvm-auto-ruby -S haml-lint /var/folders/l2/j37t2cjs5ssgcgsrk1xyt1x40000gn/T/tmpl2k7vx.haml

SublimeLinter: #17 linter.py:1202     hamllint: output:
  /var/folders/l2/j37t2cjs5ssgcgsrk1xyt1x40000gn/T/tmpl2k7vx.haml:1 [W] RuboCop: Style/NumericLiterals: Use underscores(_) as thousands separator and separate every 3 digits with them.

  1 file inspected, 1 lint detected

So haml-lint in Sublime ignores my settings in rubocop.yml.
SublimeLinter.sublime-settings does not have any settings regarding haml-lint.
I'm using

Sublime v3.2.2
SublimeLinter v4.14.0
SublimeLinter-haml-lint v2.1.0

Unfortunately I can't say for how long this has been the case.
Any ideas? Happy to help debugging.

How does haml look up the configuration?

Don't know, but it seems like it leaves the heavy lifting for the rubocop gem.

Hm, you point to the parser.
https://github.com/sds/haml-lint#configuration
https://github.com/sds/haml-lint/blob/5cd2e0ae5a2aeddbe5731bd0d66bbb7a4a17ed40/lib/haml_lint/configuration_loader.rb#L11

Sorry, misunderstood your question. I thought since it‘s an issue with rubocop you were interested in where that is coming from.
So yeah, haml-lint expects a haml-lint.yml (which works fine) but also integrates with rubocop (which does not work for me).

It loads the configuration based on the directory haml-lint is being run from, ascending until a configuration file is found.

This is just me guessing, again, but maybe this bit from the linters documentation helps:

You can also explicitly set which RuboCop configuration to use via the HAML_LINT_RUBOCOP_CONF environment variable. This is intended to be used by external tools which run the linter on files in temporary directories separate from the directory where the HAML template originally resided (and thus where the normal .rubocop.yml would be picked up).

Maybe haml-lint does not executed in the correct context, so it doesn't find path/to/projetc/.rubocop.yml.
If there's anything I can do to help investigating this let me know.

👍 Yeah that's it probably.  See also https://github.com/dense-analysis/ale/blob/2b785688ead505dcbc1007374d3dca9914aa247a/ale_linters/haml/hamllint.vim#L10-L33

So, it looks up a .haml-lint.yml based on the working dir (as per the doc cited), but the rubocop.yml must be set explicitly because it is looked up by looking at the filepath we pass in which is a temp file.  🤷 funky

The work-around or test is to set it in the SL settings.
"linters":
  "haml-lint":
     "env": {
		"HAML_LINT_RUBOCOP_CONF": "${folder}/.rubocop.yml"
	}

If that works a PR can be made to automate this.

Ok, I try my best to give reproducable test case.
First You need to have ruby and also rubygems installed. Afterwards you need to run gem install haml_lint to install haml-lint executable.
As for the actual source files you need kaste.haml und rubocop.yml.
Contents of kaste.haml:
- some_var = 123456
%p
  = some_var

Contents of rubocop.yml:
AllCops:
  NewCops: enable

Style/NumericLiterals:
  Enabled: false

If you run haml-lint kaste.haml you should get 1 file inspected, 0 lints detected as output. No lint offenses.
To recreate what the plugin does, the haml-file needs to be copied elsewhere. So if you run ...
cp kaste.haml /some/where/else/kaste.haml
haml-lint /some/where/else/kaste.haml

... you should get a lint offense along the lines of:
/some/where/else/kaste.haml:1 [W] RuboCop: Style/NumericLiterals: Use underscores(_) as thousands separator and separate every 3 digits with them.

Possible fixes:

do not copy the file elsewhere because why?
copy the file to the project's root and delete it afterwards
change the command to include HAML_LINT_RUBOCOP_CONF, i.e. HAML_LINT_RUBOCOP_CONF="/path/to/project/.rubocop.yml" haml-lint /some/where/else/kaste.haml

I did not consider the environment dance with rvm because it's not necessary in this case.
Hope this helps. If I can assist any further, let me know.

Okay, setting env works for me.
"hamllint": {
            "env": {
                "HAML_LINT_RUBOCOP_CONF": "${folder}\\.rubocop.yml"
            },
        },

Note that hamllint,  in my previous post I spelled it haml-lint.

A bit ridiculous because that exact config was in the last version of this plugin.  Removal 5bfe0fb (#10)

That totally explains why it used to work for our team. Fun fact: now we have

a gem called haml_lint,
a cli command called haml-lint and
a sublime linter namespace called hamllint 😱

What is the best way to go from here? Documenting this (probably not too rare) use case? Will gladly create a PR. Reverting parts of the mentioned commit? Or do you plan to give this plugin a proper rewrite to fix all those other weird issues (tempfile, executable and use_bundle_exec settings not being implemented)?

We should set the env variable if possible.  But if it throws if there is no such file we shouldn't take the same kinda static approach t.i. just assuming it is in the root folder.
Executable can be fixed by removing the ruby -S from cmd which is really a mistake.
I consider renaming this plugin to haml-lint although that's breaking (everyone has to change its settings) but hamllint is so confusing, and the double l in the middle is ugly.
The other stuff must be implemented in SL core.

Isn't this solved now that we use stdin?  We don't use the indirection ruby -S anymore so that seems solved too.

I don't need the manual config anymore, indeed. Thx 🙏


Improve the login page

Description
I wannt to improve the ui of the login
Steps to reproduce

Remove the nav from the login and sign up page
create a new look for login

Screenshots

Desktop (please complete the following information)
window, chrome
Smartphone (please complete the following information)
No response
Additional information
No response

yes i would like to work on it

can i work on it?

Sure, go ahead @Walexz01 :)


"Library not found for -lFolly" --> Facing this error after upgrading to "react-native": "0.67.2"

Description
I was using "react-native": "0.63.2". I just upgraded to "react-native": "0.67.2" by following SO Answer. Then I did pod install and ran the project from Xcode. Eventually I sendup with following error,
"Library not found for -lFolly"
Version
0.67.2
Output of npx react-native info
System:
     OS: macOS 11.6
     CPU: (8) x64 Apple M1
      Memory: 28.67 MB / 8.00 GB
      Shell: 5.8 - /bin/zsh
 Binaries:
       Node: 12.13.0 - /usr/local/bin/node
       Yarn: Not Found
       npm: 6.12.0 - /usr/local/bin/npm
       Watchman: Not Found
 Managers:
        CocoaPods: 1.11.2 - /usr/local/bin/pod
 SDKs:
        iOS SDK:
        Platforms: iOS 15.0, DriverKit 20.4, macOS 11.3, tvOS 15.0, watchOS 8.0
        Android SDK: Not Found
 IDEs:
       Android Studio: 4.2 AI-202.76<IP_ADDRESS>51085
       Xcode: 13.0/13A233 - /usr/bin/xcodebuild
 Languages:
       Java: 11.0.10 - /usr/bin/javac
 npmPackages:
       @react-native-community/cli: Not Found
       react: 17.0.2 => 17.0.2
       react-native: 0.67.2 => 0.67.2
       react-native-macos: Not Found
npmGlobalPackages:
       *react-native*: Not Found

Steps to reproduce
1.You must have initial project with  "react-native": "0.63.2" or lower
2.Upgrade React-Native version to latest and do pod install
3.Run project from Xcode then you will face with above mentioned error.
Snack, code example, screenshot, or link to a repository
I do not have any code snippet to share since this error is pertaining to React-Native version upgrade.

I found solutionhere


HMMER3

Hi. Hope you are doing great!., could you help me please? what does this means?  where should i install HMMER3? sorry for being this dumb, i really doesnt know about this kind of things. I just installed it from source, using mamba, following the instructions on github. I'd be really thankful if you answer me, whenever you can.
Cheers from Chile, South America.

Hi David,
I just need a few bits of information to help with debugging:

How did you install ggCaller?
What command did you run using ggCaller?
What is the output when you run hmmscan -h?
What is the output when you run mamba list? If this is too large, you can save this to a file using mamba list > mamba_list.txt and send the file across.

Hi, thanks for answering, you are very kind!
I first write this command on a server: nohup ggcaller --refs input.txt --threads 50 &. The nohup.out file contains this:
(base) [mdavid@soroban IMSAR217cc11]$ cat nohup.out
Building coloured compacted DBG...
Generating graph stop codon index...
Mapping contigs to graph...
Need HMMER3 to be installed and available in PATH
Downloading databases...
Building coloured compacted DBG...
Generating graph stop codon index...
Mapping contigs to graph...
Need HMMER3 to be installed and available in PATH
then i installed ggcaller on my laptop, and then i run it using ggcaller --refs input.txt --threads 5. It ended up giving me the same message "Need HMMER3 to be installed and available in PATH ".
This is what appears when i write hmmscan -h:

And this when i write mamba list:
mambalist.txt
Thanks again, in advance.
Cheers

Hi David, thanks for sending all of this information through. This was very helpful, I was able to identify the issue (it was due to an update to HMMER3), this is now fixed in commit 1d85587. Please update to the latest commit and rerun python setup.py install


mruby: 2.0.0 -> 2.0.1

Motivation for this change
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Release note: https://mruby.org/releases/2019/04/04/mruby-2.0.1-released.html

Tested with nix-review on nixos too


[5.8] Fix the remaining issues with registering custom Doctrine types.

This PR removes the TinyInteger type from the core and allows the user to register their own custom Doctrine DBAL types. No connection wil be established by only instantiating the builder class, only as soon as you call the registerCustomDoctrineType method. Therefore it won't cause issues like #28282 anymore.

If support for tinyint is being removed from core Laravel, does the documentation ned to be updated to remove references to tinyIncrements , tinyInteger, and unsignedTinyInteger?
https://laravel.com/docs/5.8/migrations#creating-columns

@kevindb tinyint support wasn't removed in general, just the MySQL override introduced by https://github.com/laravel/framework/pull/28214 because of the bug from https://github.com/laravel/framework/pull/28214.


Feat: init Reaktoro service (c++ mode)

The value of this PR is in the valid C++ Dockerfile powered by Anaconda3 and Crow.

Closed as an experimental.


sokol_gfx.h: Can't clear just stencil buffer for an offscreen pass with GL3.3

I'm trying to do something like this
   sg_pass_action pass_action = {
        .colors[0] = { .action = SG_ACTION_DONTCARE },
        .depth = {
            .action = SG_ACTION_DONTCARE,
        },
        .stencil = {
            .action = SG_ACTION_CLEAR,
        },
    };
    sg_begin_pass(pass, &action);

but this assert is failing: https://github.com/floooh/sokol/blob/a3278884e3895d996e79a38bd74e44826e3efb74/sokol_gfx.h#L6293
I narrowed it down and it looks like the problem is here: https://github.com/floooh/sokol/blob/a3278884e3895d996e79a38bd74e44826e3efb74/sokol_gfx.h#L6288
This documentation (https://www.khronos.org/registry/OpenGL-Refpages/gl4/html/glClearBuffer.xhtml) says glClearBufferuiv can only be called with GL_COLOR, so I think it should be changed to glClearBufferiv? That fixes the issue for me.

Yep, looks like an oversight on my part. I'll commit a fix ASAP.
Thanks for the bug report!

Ok, fixed. On macOS (Big Sur Beta) the old code wasn't actually throwing an error (I didn't check whether the stencil buffer is actually cleared though with *uiv()), but the documentation is pretty clear about using glClearBufferiv().


Warning on scdel for objects

scmake("merged_flow")
Starting build at 2017-12-07 14:33:57
<  MAKE > merged_flow
blah blah
Build completed in 0.31 minutes
scdel('merged_flow')
(   DEL ) merged_flow                                            |  rm("merge...
[1] FALSE
Warning message:
In file.remove(status_files) :
  cannot remove file 'build/status/.yml', reason 'No such file or directory'

Good call, scdel shouldn't even attempt to remove non-file .yml files. We should still be able to apply that function to objects (and a mix of files and objects, and a mix of .ind files and regular files and objects, in case those aren't yet in good shape).

We must have fixed this already. For a remake.yml that contains
targets:
  wqp_pull_string:
    command: c(I('hi mom!'))

I can run the following without error or warning:
Starting build at 2019-08-30 16:27:00
<  MAKE > wqp_pull_string
[ BUILD ] wqp_pull_string                                  |  wqp_pull_string <- c("hi mom!")
[  READ ]                                                  |  # loading packages
Finished build at 2019-08-30 16:27:00
Build completed in 0.00 minutes
> scdel('wqp_pull_string')
(   DEL ) wqp_pull_string                                  |  rm("wqp_pull_string")
> scmake('wqp_pull_string')
Starting build at 2019-08-30 16:27:03
<  MAKE > wqp_pull_string
[ BUILD ] wqp_pull_string                                  |  wqp_pull_string <- c("hi mom!")
Finished build at 2019-08-30 16:27:03
Build completed in 0.00 minutes
> scmake('wqp_pull_string', force=TRUE)
(   DEL ) wqp_pull_string                                  |  rm("wqp_pull_string")
Starting build at 2019-08-30 16:27:07
<  MAKE > wqp_pull_string
[ BUILD ] wqp_pull_string                                  |  wqp_pull_string <- c("hi mom!")
Finished build at 2019-08-30 16:27:07
Build completed in 0.00 minutes


Deposit not received memo not included

I left the memo off my deposit to BitMart. Now my money is missing, what can I do?

havent heard anything back yet

Me either...we'll find our money.  Keep trying every avenue, lets stay diligent.  Also, ETH is about to go $4300!
From: devthedude93 @.>
Sent: Tuesday, May 11, 2021 8:43 PM
To: stellar-expert/stellar-expert-explorer @.>
Cc: ReithKichards @.>; Comment @.>
Subject: Re: [stellar-expert/stellar-expert-explorer] Deposit not received memo not included (#449)
havent heard anything back yet

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fstellar-expert%2Fstellar-expert-explorer%2Fissues%2F449%23issuecomment-839409299&data=04|01||a0a07915049b492b633d08d914f802cf|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637563877694030451|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=dGwiUjc8ThDZK%2F2sio9IwiAj7CJellcM1wiJOCZ1DQo%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAUAVYEADTY2VJOE5UFHYZE3TNH2LPANCNFSM44PMUVSQ&data=04|01||a0a07915049b492b633d08d914f802cf|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637563877694040444|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=YP9gHZ6F0zGQWyfsNAPVPC37qaxYGffa%2FXulG1hMlVk%3D&reserved=0.

Me either...we'll find our money. Keep trying every avenue, lets stay diligent. Also, ETH is about to go $4300! From: devthedude93 @.> Sent: Tuesday, May 11, 2021 8:43 PM To: stellar-expert/stellar-expert-explorer @.> Cc: ReithKichards @.>; Comment @.> Subject: Re: [stellar-expert/stellar-expert-explorer] Deposit not received memo not included (#449) havent heard anything back yet - You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fstellar-expert%2Fstellar-expert-explorer%2Fissues%2F449%23issuecomment-839409299&data=04|01||a0a07915049b492b633d08d914f802cf|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637563877694030451|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=dGwiUjc8ThDZK%2F2sio9IwiAj7CJellcM1wiJOCZ1DQo%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAUAVYEADTY2VJOE5UFHYZE3TNH2LPANCNFSM44PMUVSQ&data=04|01||a0a07915049b492b633d08d914f802cf|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637563877694040444|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=YP9gHZ6F0zGQWyfsNAPVPC37qaxYGffa%2FXulG1hMlVk%3D&reserved=0.

not too worried anymore bought some other crypto made it back :( but they need give us our money back

I have sent an email to BitMart but so far no reply yet.
On Tue, May 11, 2021 at 10:45 PM ReithKichards @.***>
wrote:

Me either...we'll find our money. Keep trying every avenue, lets stay
diligent. Also, ETH is about to go $4300!
From: devthedude93 @.>
Sent: Tuesday, May 11, 2021 8:43 PM
To: stellar-expert/stellar-expert-explorer @.>
Cc: ReithKichards @.>; Comment @.>
Subject: Re: [stellar-expert/stellar-expert-explorer] Deposit not received
memo not included (#449)
havent heard anything back yet

You are receiving this because you commented.
Reply to this email directly, view it on GitHub<
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fstellar-expert%2Fstellar-expert-explorer%2Fissues%2F449%23issuecomment-839409299&data=04|01||a0a07915049b492b633d08d914f802cf|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637563877694030451|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=dGwiUjc8ThDZK%2F2sio9IwiAj7CJellcM1wiJOCZ1DQo%3D&reserved=0>,
or unsubscribe<
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAUAVYEADTY2VJOE5UFHYZE3TNH2LPANCNFSM44PMUVSQ&data=04|01||a0a07915049b492b633d08d914f802cf|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637563877694040444|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=YP9gHZ6F0zGQWyfsNAPVPC37qaxYGffa%2FXulG1hMlVk%3D&reserved=0

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stellar-expert/stellar-expert-explorer/issues/449#issuecomment-839409942,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUAJRXFTMCE5A66TEVIXU6LTNH2VBANCNFSM44PMUVSQ
.

--
Kash Siraj
REALTOR® | Performance USA Realty
8501 Wareham Dr, Plano, TX 75024
Cell:<PHONE_NUMBER> | Email: @.**
@.**>
TREC Consumer Protection Notice
https://www.trec.texas.gov/sites/default/files/pdf-forms/CN 1-2.pdf
Texas law requires all real estate licensees to give the following
information about brokerage services to prospective buyers, tenants,
sellers and landlords.

https://drive.google.com/file/d/1fIlLWEoTjW70lXyAlyyGoeCZNvtFEtiH/view*

Information About Brokerage Services
https://www.trec.texas.gov/sites/default/files/pdf-forms/IABS 1-0.pdf
Confidentiality notice: This e-mail message, including any attachments,
may contain legally privileged and/or confidential information. If you are
not the intended recipient(s), or the employee or agent responsible for
delivery of this message to the intended recipient(s), you are hereby
notified that any dissemination, distribution, or copying of this e-mail
message is strictly prohibited. If you have received this message in error,
please immediately notify the sender and delete this e-mail message from
your computer.

Same here.  I'm in it for the long run...should have kept it in Coinbase, legit
From: kashifsiraj786 @.>
Sent: Tuesday, May 11, 2021 9:34 PM
To: stellar-expert/stellar-expert-explorer @.>
Cc: ReithKichards @.>; Comment @.>
Subject: Re: [stellar-expert/stellar-expert-explorer] Deposit not received memo not included (#449)
I have sent an email to BitMart but so far no reply yet.
On Tue, May 11, 2021 at 10:45 PM ReithKichards<EMAIL_ADDRESS>wrote:

Me either...we'll find our money. Keep trying every avenue, lets stay
diligent. Also, ETH is about to go $4300!
From: devthedude93<EMAIL_ADDRESS>Sent: Tuesday, May 11, 2021 8:43 PM
To: stellar-expert/stellar-expert-explorer<EMAIL_ADDRESS>Cc: ReithKichards<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [stellar-expert/stellar-expert-explorer] Deposit not received
memo not included (#449)
havent heard anything back yet

You are receiving this because you commented.
Reply to this email directly, view it on GitHub<
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fstellar-expert%2Fstellar-expert-explorer%2Fissues%2F449%23issuecomment-839409299&data=04|01||a0a07915049b492b633d08d914f802cf|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637563877694030451|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=dGwiUjc8ThDZK%2F2sio9IwiAj7CJellcM1wiJOCZ1DQo%3D&reserved=0>,
or unsubscribe<
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAUAVYEADTY2VJOE5UFHYZE3TNH2LPANCNFSM44PMUVSQ&data=04|01||a0a07915049b492b633d08d914f802cf|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637563877694040444|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=YP9gHZ6F0zGQWyfsNAPVPC37qaxYGffa%2FXulG1hMlVk%3D&reserved=0

.

You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stellar-expert/stellar-expert-explorer/issues/449#issuecomment-839409942,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUAJRXFTMCE5A66TEVIXU6LTNH2VBANCNFSM44PMUVSQ
.

--
Kash Siraj
REALTOR(r) | Performance USA Realty
8501 Wareham Dr, Plano, TX 75024
Cell:<PHONE_NUMBER> | Email<EMAIL_ADDRESS><EMAIL_ADDRESS>TREC Consumer Protection Notice
https://www.trec.texas.gov/sites/default/files/pdf-forms/CN 1-2.pdf
Texas law requires all real estate licensees to give the following
information about brokerage services to prospective buyers, tenants,
sellers and landlords.

https://drive.google.com/file/d/1fIlLWEoTjW70lXyAlyyGoeCZNvtFEtiH/view*

Information About Brokerage Services
https://www.trec.texas.gov/sites/default/files/pdf-forms/IABS 1-0.pdf
Confidentiality notice: This e-mail message, including any attachments,
may contain legally privileged and/or confidential information. If you are
not the intended recipient(s), or the employee or agent responsible for
delivery of this message to the intended recipient(s), you are hereby
notified that any dissemination, distribution, or copying of this e-mail
message is strictly prohibited. If you have received this message in error,
please immediately notify the sender and delete this e-mail message from
your computer.

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fstellar-expert%2Fstellar-expert-explorer%2Fissues%2F449%23issuecomment-839426022&data=04|01||c07fac80f318443f1ee208d914ff3ab7|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637563908696512931|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=CD3x0IvJW5zxrAdzJvommQCp8gzy2XgFYoVLSYjnL3w%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAUAVYEB6W576WRZ656UKX33TNIANHANCNFSM44PMUVSQ&data=04|01||c07fac80f318443f1ee208d914ff3ab7|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637563908696522928|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=FH%2BE%2BqoshtXdlcMtPi%2FEUca5ZL1suuDHiIvukAUAYII%3D&reserved=0.


add cellery update, list dependency and route-traffic commands to README

Purpose

Add cellery update, list dependency and route-traffic commands to the CLI readme file.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #508   +/-   ##
=======================================
  Coverage   64.45%   64.45%
=======================================
  Files          34       34
  Lines        1176     1176
  Branches       98       98
=======================================
  Hits          758      758
  Misses        365      365
  Partials       53       53

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 923c6a4...aedf3ae. Read the comment docs.


fix(license) replace boilerplate year/corp

https://github.com/bytecodealliance/wasmtime/issues/4064


Allow to output the SPDX identifier

Describe the solution you'd like
Can we have some sort of a lookup to make sure that license output matches SPDX codes?
As this is the standard, I assume that a lot of people will be wanting to use this

Describe alternatives you've considered
Writing my own lookup, but that seems redundant
Additional context
Add any other context or screenshots about the feature request here.

@RHeynsZa
We have a plan to generate a result file with spdx format.
Currently, most package managers in FOSSLight Dependency Scanner take the license name through manifest file.
And some package managers doesn't support the SPDX identifier.
If the SPDX identifier is invalid, do you have any ideas about changing it?


Change Bit Marker position and make it equal to the bit, rather than array styled markings.

Problem Statement
The bit markers for the Bit Flip pane feel off and awkward to read, so instead add the marker under the highest bit.

Evidence or User Insights
Me and my peers were discussing this, and we all agreed it was tougher to read when the first bit is marked as the 0 byte.

Proposal
I have already created a branch and a pr with a fix if it is agreed upon.

Goals
Simply change the position of the markers below and set the highest bit number as 64.

Non-Goals
N/A

Low-Fidelity Concept

Requested Assignment

If possible, I would like to implement this.

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.


Switch to Dioxus desktop

The egui_graph library doesn't support some features we need (mainly working with any) types. Egui itself has issues with layout (you cannot have a expandable scrollbar). Dioxus desktop is not immediate mode, so it should be easier to do complex layous. We will need to create a graph interface ourselves, but that will give us more control over how the interface looks and how types are implemented

This is blocked on https://github.com/Demonthos/dioxus-flow


Universal Code: access to table "Licence Information"

Hi,
To make apps compatible with "Universal Code" is required target must be Cloud in app.json.
I want to convert an existing app that I'm using in BC OnPrem. This app shows the data of onprem license, like the old RTC Client was in help (license information).
The problem is, the table "License Information" is marked as scope=OnPrem, and when I try to generate de package, this error is generated:  error AL0296: The application object or method 'License Information' has scope 'OnPrem' and cannot be used for 'Cloud' development.
I think this table would be accessible as a Universal App, because a table isn't a resource inaccesible in a isolated environment (as a Cloud).
Could yo do something to allow the use of tables in Universal Apps?
I propose some improvements:

Relax the error AL0296 when the object is a table, change to a Warning.
Create a method that return the data of license information.

Best regards,
José Antonio López

Information about the license does not come from the license information table in a cloud enabled world. This means if you have a dependency to the License Information table then you are developing for onpremises only and not cloud ready.
The solution can no longer be moved to the cloud.
So the question is what type of information are you in need of getting from the license information table?

We are currently processing a PR, which addresses the same issue you have brought up. We haven't landed on a solution quite yet, but it's probably interesting for you to follow and contribute to the discussion. Take a look: https://github.com/microsoft/ALAppExtensions/pull/20445.

We are currently processing a PR, which addresses the same issue you have brought up. We haven't landed on a solution quite yet, but it's probably interesting for you to follow and contribute to the discussion. Take a look: microsoft/ALAppExtensions#20445.

Ok, I've done that and I've contributing to the discussion.
Thanks.
Best regards,


Laravel 5.2 > 5.3

when upgrade laravel into 5.3 I have a problem,
Method gatherRouteMiddlewares does not exist.

public function gatherRouteMiddlewares($route)     {         return $this->router->gatherRouteMiddlewares($route);     }
there is typo at here.
fixed with
public function gatherRouteMiddlewares($route)     {         return $this->router->gatherRouteMiddleware($route);     }

@wardwar how did you update dingo/api to use laravel 5.3? when i try to update it I get
'Your requirements could not be resolved to an installable set of packages.'
dingo/api v0.10.0 requires illuminate/routing 5.1.* -> satisfiable by illuminate/routing[v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.41, v5.1.6, v5.1.8].
Thanks in advance

@shez1983 I don't know, I just edited the file. and it work for me.
did you done composer update after require laravel 5.3?

https://github.com/dingo/api/pull/1152
Here's the PR that implements Laravel 5.3 support. I think the dev will soon pull it to the repo :)

Any simple way to install it over Laravel 5.3?

Closed by #1152 being merged. Install dev-master or the latest tag (v1.0.0-beta6 at the time of this comment)

Even I am using Laravel 5.3
As @wardwar said, edit file at vendor/dingo/api/src/Routing/adapter/Laravel.php
Overwrite this line:
public function gatherRouteMiddlewares($route)      {          return $this->router->gatherRouteMiddlewares($route);      }
in to this:
public function gatherRouteMiddlewares($route)     {         return $this->router->gatherRouteMiddleware($route);     }
Thank you @wardwar , I owe you a beer for saving my day bud!

@rohitpaniker the merged file already include this changes.

@crynobone Ohkay really? As I did a fresh install as well as update so I came across the same issue few minutes back. Anyway, thank you for pointing it out :)

Using Laravel 5.4, the file isn't fixed :
https://github.com/dingo/api/blob/master/src/Routing/Adapter/Laravel.php


dtc: add yaml support and enable tests

Motivation for this change
I noticed dtc has yaml support, but this was not avaiable in the nixpkgs version. Getting the feature is as easy as providing the correct library at compiletime.
Things done
Set libyaml as a buildInput. Make sure tests of the dtc project run.

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Result of nixpkgs-review pr 118700 at a8ddf1dd run on aarch64-linux 1

1 package marked as broken and skipped:

odroid-xu3-bootloader

1 package failed to build:

crosvm

1 package skipped due to time constraints:

ubootRockPro64

24 packages built successfully:

bareboxTools
cloud-hypervisor
diffoscope
dtc
fwts
python38Packages.libfdt
python39Packages.libfdt
spike
ubootBananaPim64
ubootNanoPCT4
ubootOdroidC2
ubootOrangePiZeroPlus2H5
ubootPine64
ubootPine64LTS
ubootPinebook
ubootPinebookPro
ubootQemuAarch64
ubootROCPCRK3399
ubootRaspberryPi3_64bit
ubootRaspberryPi4_64bit
ubootRock64
ubootRockPi4
ubootSopine
ubootTools

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.

crosvm is fixed. Can you check if upstream allows later versions of the GPL and clarify metadata accordingly?
Result of nixpkgs-review pr 118700 1

1 package marked as broken and skipped:

odroid-xu3-bootloader

9 packages built:

bareboxTools
crosvm
diffoscope
dtc
fwts
python38Packages.libfdt
python39Packages.libfdt
spike
ubootTools

@lourkeur: Can you check if upstream allows later versions of the GPL and clarify metadata accordingly?

Upstream says SPDX-License-Identifier: GPL-2.0-or-later. I updated the metadata accordingly.

In Apple M1(darwin-aarch64),
check failed to pass with errors below, seems to be an upstream issue.
tests/trees.S:216:8: error: expected relocatable expression
 .byte ((ovf_size_strings_end - ovf_size_strings) >> 24) & 0xff ; .byte ((ovf_size_strings_end - ovf_size_strings) >> 16) & 0xff ; .byte ((ovf_size_strings_end - ovf_size_strings) >> 8) & 0xff ; .byte (ovf_size_strings_end - ovf_size_strings) & 0xff ;
       ^
tests/trees.S:217:8: error: expected relocatable expression
 .byte ((ovf_size_strings_struct - ovf_size_strings) >> 24) & 0xff ; .byte ((ovf_size_strings_struct - ovf_size_strings) >> 16) & 0xff ; .byte ((ovf_size_strings_struct - ovf_size_strings) >> 8) & 0xff ; .byte (ovf_size_strings_struct - ovf_size_strings) & 0xff ;
       ^
tests/trees.S:218:8: error: expected relocatable expression
 .byte ((ovf_size_strings_strings - ovf_size_strings) >> 24) & 0xff ; .byte ((ovf_size_strings_strings - ovf_size_strings) >> 16) & 0xff ; .byte ((ovf_size_strings_strings - ovf_size_strings) >> 8) & 0xff ; .byte (ovf_size_strings_strings - ovf_size_strings) & 0xff ;
       ^
tests/trees.S:219:8: error: expected relocatable expression
 .byte ((ovf_size_strings_rsvmap - ovf_size_strings) >> 24) & 0xff ; .byte ((ovf_size_strings_rsvmap - ovf_size_strings) >> 16) & 0xff ; .byte ((ovf_size_strings_rsvmap - ovf_size_strings) >> 8) & 0xff ; .byte (ovf_size_strings_rsvmap - ovf_size_strings) & 0xff ;
       ^
tests/trees.S:224:8: error: expected relocatable expression
 .byte ((ovf_size_strings_struct_end - ovf_size_strings_struct) >> 24) & 0xff ; .byte ((ovf_size_strings_struct_end - ovf_size_strings_struct) >> 16) & 0xff ; .byte ((ovf_size_strings_struct_end - ovf_size_strings_struct) >> 8) & 0xff ; .byte (ovf_size_strings_struct_end - ovf_size_strings_struct) & 0xff ;
       ^
make: *** [Makefile:349: tests/trees.o] Error 1


Map Doesn't work

Map Preview isn't working for 2.6.2 Build 110
https://github.com/user-attachments/assets/783cae05-8cc5-479e-a9a4-a7f918b8a796

for me, it works on Android but not showing on iOS

@garudaonekh sorry for the issue. Will fix as soon as possible. Though wont be until september as i dont have a ios devices with me right now

There was some map fixes resolved now in both the latest (build 144) Google Play Store and the Github versions, not sure if the iOS version is up on their appstore latest iOS should be 2.9.1 Build 123 if you want to test/test this weekend or Monday.


TraceEvent FormattedMessage is always null

Transferred from issue in diagnostics repo opened by Zheltov.
Hello everyone!
I have been using DiagnosticsClient for subscribe to EventSource in same process. I have got events successfully, but TraceEvent.FormattedMessage is always null. However, i can see the message in Diagnostics Events window in Visual Studio.
What happened?
using Microsoft.Diagnostics.NETCore.Client;
using Microsoft.Diagnostics.Tracing;
using System;
using System.Diagnostics;
using System.Diagnostics.Tracing;
using System.Threading;
using System.Threading.Tasks;

namespace ETWSelfSignedAgentTest
{
    class Program
    {
        static void Main(string[] args)
        {
            RunAgent();

            Task.Run(() =>
            {
                for(int i =0; i < int.MaxValue; i++)
                {
                    ServiceEventSource.Log.Iteration(i);
                    Thread.Sleep(1000);
                }
            });

            Console.ReadLine();
        }

        private static void RunAgent()
        {
            Task.Factory.StartNew(() =>
            {
                var client = new DiagnosticsClient(Process.GetCurrentProcess().Id);
                using var session = client.StartEventPipeSession(new EventPipeProvider[] { new EventPipeProvider("ExampleEventSource", EventLevel.Verbose, long.MaxValue) });
                using var source = new EventPipeEventSource(session.EventStream);
                source.Dynamic.All += (TraceEvent traceEvent) =>
                {
                    Console.Write($"{traceEvent.ProviderName} [{traceEvent.Level}] FormattedMessage: {traceEvent.FormattedMessage}");
                    foreach (string payloadName in traceEvent.PayloadNames)
                    {
                        Console.Write($"{payloadName}: {traceEvent.PayloadStringByName(payloadName)}");
                    }
                    Console.WriteLine();
                };

                try
                {
                    source.Process();
                }
                catch (Exception e)
                {
                    Console.WriteLine(e.ToString());
                }
            },
            TaskCreationOptions.LongRunning);
        }
    }

    [EventSource(Name = "ExampleEventSource")]
    public sealed class ServiceEventSource : EventSource
    {
        public static readonly ServiceEventSource Log = new ServiceEventSource();

        private ServiceEventSource() : base() { }

        [Event(1, Level = EventLevel.Informational, Message = "It`s {0} iteration")]
        public void Iteration(int i)
        {
            WriteEvent(1, i);
        }
    }
}

This is due to the fact that EventPipe doesn't serialize the message as part of the event metadata.  This would need to be addressed in the runtime.

@mikelle-rogers, can you please file this in the runtime repo instead?

Thanks @mikelle-rogers!