Workshop-Spring-Stargate Michael Scarpace

Name: Michael Scarpace
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/michael-scarpace
Attach the homework step I screenshots below:
Attach the homework step II screenshots below:

Hey there Michael, thank you for your submission. Nice job getting the app correctly configured and deployed. The only thing we are missing is step 2 of the homework.
2. Learn more about spring in the course and complete scenario Build a Spring Boot REST Service at the bottom of the page and make a screenshot of the "congratulations" page.
Please post an image of the "completed" screen once finished.

I added step two snippets into git hub.
On Tuesday, September 7, 2021, 09:29:28 AM EDT, David Jones-Gilardi<EMAIL_ADDRESS>wrote:

Hey there Michael, thank you for your submission. Nice job getting the app correctly configured and deployed. The only thing we are missing is step 2 of the homework.
2. Learn more about spring in the course and complete scenario Build a Spring Boot REST Service at the bottom of the page and make a screenshot of the "congratulations" page.
Please post an image of the "completed" screen once finished.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

I added step two snippets into git hub.

Are you talking about a different github issue than this one?


TypeError: no _dump_data is defined for class OpenSSL::X509::Store

Playing around with rest-graph. Simple test yields error:
RestGraph.new access_token: token
client.get 'me'

RestGraph: spent 0.307645 Requested https://graph.facebook.com/me?access_token=REMOVED
TypeError: no _dump_data is defined for class OpenSSL::X509::Store
from ~/.rvm/gems/ruby-2.3.1@REMOVED/gems/redis-store-1.1.7/lib/redis/store/marshalling.rb:29:in `dump'

First I'll suggest you to move to rest-more's facebook client because I am no longer actively working on rest-graph.
And I can't seem to reproduce the problem you have here. Your error was raised from redis-store gem, did it do some weird monkey patching break this? Also if you don't have rest-client installed, you might want to install it because rest-graph is using it. (or em-http-request, that's why it's not strictly set as a dependency)

@godfat Thanks for the help!
I found how to solve the issue with rest-graph: the redis cache isn't compatible with whatever rest-client is doing, it's probably trying to cache non-PORO objects. Giving the cache: {} option solved the problem.
I however followed your advice and moved to rest-more, which worked better.
Thank you!

@hickscorp Awesome! Thanks for moving and letting me know how it went. Let me know if you have any issues with rest-more, by filing an issue or chatting on gitter, or perhaps using the old google group or new mailing list. Personally I am ok with using issues as the discussion threads though, so just pick whatever you like.


Multi-start and hyper-parameter optimization

Would be nice to use MultistartOptimization.jl or HyperOpt.jl to optimize the hyper-parameters of optimization algorithms including the starting point.

Now available.


Space won't release

I used my Google Drive to download some movies, and deleted after got a warning of free space less than 1 GB. However, the space won't release.
I checked from both sides, the machine mounted onto, and the Google Drive page, see nothing from both of them. I believe I have removed all the files and folders.
Any idea? Is this a fuse problem?

It shouldn't be a fuse problem. Have you checked your trash? Is it empty?

I didn't even know this (maybe because I cannot see the 'trash' from the mount point. Problem solved, but can you add some features to do with the trash? I removed a file, that means I don' need it any more, not "in trash"...Or maybe just make "rm" from a mounted google drive means "permanent delete"?

Trash is mapped in ./.Trash subdirectory. If you enable delete_forever_in_trash_folder, when you remove files in trash, they will be removed permanently. If you use the -skiptrash switch, the files will not be trashed.

OK, thanks very much


Implement new structure

Implement updated data-structure propsed by @Cudok

[ ] add description of fields as db_comment
[ ] focus-attribute for datasets and norms
[ ] add scale, targetGroup, lifeCyaclePhase, developmentState to datasets, norms and protocols
[ ] alternatives-atribute is also useful in datasets and norms. Not sure if needed in protocols
[ ] datasets should have a field datatype or encoding or file-ending
[ ]  make license be shown in tools

[ ] datasetCategory -> classification (maps to ClassificationDataset-Table)
[ ] datasets__comment -> delete
[ ] datasets__dataSources -> furtherinformation
[ ] merge dataSources and includedNonResidential and put it into dataSets__furtherInformation
[ ] nameDataset -> name
[ ] datasets__reference -> provider
[ ] datasets__refernceLink -> datsets__resources
[ ] datasets__useCaseCategory -> applicationArea
[ ] remove description of scope in frontend

-[ ] in protocols: remove associatedStandard and create M2M relation to norms associatedNorms

[ ] bring license into seperate table and include open-source flag, and fee-flag to it

Done
collectedDatasets

changed nameDatasets -> name
added db_comment="Name of the dataset"
changed useCaseCategory -> applicationArea
added db_comment="Typical application area in which the dataset is used. An application area describes all possible methods and datasets, that can be used to achieve a specific purpose."
changed categoryDataset -> classification
added db_comment="General type of dataset - Which category does the data set belong to?"


device-type/getInstructions: Overload to accept the device type contract

Change-type: minor

Resolves: #
HQ:
See:
Depends-on:
Change-type: major|minor|patch

Contributor checklist

[ ] Includes tests
[ ] Includes typings
[ ] Includes updated documentation
[ ] Includes updated build output

I self-certify!


Add option to include formatted messages

Fixes https://github.com/serilog/serilog-sinks-opentelemetry/issues/100
I am not sure if this is a desired approach but perhaps it can help move along the discussion

Thanks @danelson 👍
I think an IncludedData.FormattedMessageBody option (naming uncertain) would fit in with the existing design more closely, perhaps that needs more investigation?
I can see how it'd be a breaking change, given the way IncludedData is opt-in today (existing code wouldn't opt-in and behavior would change), so perhaps the option would need to be more like IncludedData.TemplateBody....
The other (minor) concern I have with this setup is that without some indication of schema, receivers wanting to render the full message text need to heuristically determine whether or not the body is a template; is there an OTLP field we could try using for this purpose? 🤔

I think an IncludedData.FormattedMessageBody option (naming uncertain) would fit in with the existing design more closely, perhaps that needs more investigation?

I can see how it'd be a breaking change, given the way IncludedData is opt-in today (existing code wouldn't opt-in and behavior would change), so perhaps the option would need to be more like IncludedData.TemplateBody....

I didn't initially try this approach because I thought it would be weird that you would be able to include IncludedData.MessageTemplateTextAttribute and IncludedData.TemplateBody (or whatever we call it). I can create another PR to make it easier to compare.

The other (minor) concern I have with this setup is that without some indication of schema, receivers wanting to render the full message text need to heuristically determine whether or not the body is a template; is there an OTLP field we could try using for this purpose? 🤔

If this was the desired behavior wouldn't they just use the current behavior? I am actually not aware of any semantic conventions for logs. Something could be introduced like what was done for message_template.text.

I didn't initially try this approach because I thought it would be weird that you would be able to include IncludedData.MessageTemplateTextAttribute and IncludedData.TemplateBody (or whatever we call it). I can create another PR to make it easier to compare.

Thanks; yeah, there's definitely some opportunity there to create a nonsense configuration - but a lot of options combine in pointless ways, so I don't think this would be a blocker (given IncludedData is the home of all content configuration right now).

If this was the desired behavior wouldn't they just use the current behavior? I am actually not aware of any semantic conventions for logs. Something could be introduced like what was done for message_template.text.

Meant this more as a point to ponder than a direct question; self-describing data is just nicer to deal with in lots of ways. It's hard for a receiver to act on this without knowledge of the configuration of the source, something the semantic conventions for log record attributes deal with quite nicely, and why the default is to use message_template.text 👍
I don't think it's harmful to offer this configuration option, though - only that it's a bit less optimal IMHO :-)


UI: Add domain and account fields to Register/Upload Template/ISO view

Description
This PR allows passing the optional parameters domainid and account to the registerTemplate/registerISO/uploadISO/uploadTemplate APIs (was only possible to pass these parameters through the API):
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

Register a template as an admin to another account in other domain -> verify domainid and account parameters are passed correctly
Register a template as an admin without setting any domain or account -> verify domainid and account parameters are not passed
Login as a user, verify the domain dropdown is not displayed

@nvazquez should similar fields be added in the ISO form?

UI build: :heavy_check_mark:
Live QA URL: https://qa.cloudstack.cloud/simulator/pr/7872 (QA-JID-147)

@nvazquez should similar fields be added in the ISO form?

make sense
cc @nvazquez

Thanks @shwstppr @weizhouapache - I have added them to the Register/Upload ISO view as well

@blueorangutan ui

@nvazquez a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

@nvazquez
can you fix the conflicts ? thanks

Done thanks @weizhouapache
@blueorangutan ui

@nvazquez a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: https://qa.cloudstack.cloud/simulator/pr/7872 (QA-JID-149)

@DaanHoogland a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: https://qa.cloudstack.cloud/simulator/pr/7872 (QA-JID-150)

Packaging result [SF]: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 6815


Fix Cypress Test for Country Select

┆Issue is synchronized with this Trello card by Unito

This is done, right, Brock?

Ya, done.


[WIP] [Proposal] Revision: SE-0132 Rationalizing Sequence end-operation names

This is an update of SE-0132, which was returned for revision at the end of the Swift 3 cycle. Functionally, it removes the parts of the proposal that were later handled by SE-0172 and updates the source stability plan, but this version is also much less verbose and has better formatting, so it should be easier to discuss.
There's an implementation in apple/swift#3793, but it targeted Swift 3 and needs to be updated before the proposal can go forward. I will work on that shortly and then tag the necessary people to get this rolling.

Okay, we have an up-to-date implementation, so hold on to your butts.

@dabrahams @lattner Since you were shepherding this the first time, can you take a look at the update?

Well, I left a bunch of comments.  I agree there’s something to improve here, but I don’t think the fixes proposed are the right ones.  The overall problem may be that you are misled by the fact that many of these operations appear first on Sequence and not on Collection or BidirectionalCollection, and thus the importance of SubSequence to their semantics is much less apparent than it might otherwise be.  Sequence is really a marginal protocol in that almost every real model is actually multipass, and therefore should conform to Collection.  The names and semantics of these operations should always be considered first with respect to collections, where they are most relevant.
Hope this helps,
Dave

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Sent from my iPhone

On Nov 23, 2017, at 12:44 PM, Xiaodi Wu<EMAIL_ADDRESS>wrote:
I see. So x[..<3] always gives you three,

No. Try x=42...50. Or x=[1,2,3,4,5,6][..<2]

and only if the index type is an integer, but x[..<^3] gives you at most three, and even if the index type is opaque?

I don’t know what opaque means here, but yes, that would give at most 3.

@dabrahams Well, yes, I am fully aware of what happens in those examples: implied in the statement is that x[..<3] will trap if it cannot give you three--it's not as though Swift can materialize nonexistent elements out of nowhere--and it will not work when indices are deliberately disabled by being an opaque type as in ranges (hence, "only if the index type is an integer").

Sent from my iPhone

On Nov 23, 2017, at 12:06 PM, Brent Royal-Gordon<EMAIL_ADDRESS>wrote:
I lost the first version of this comment, but tl;dr is, I think these are best modeled as a mutating/nonmutating pair.

I disagree; dropXXX is a slicing operation that applies to any collection and returns a SubSequence while removeXXX is only available on range replaceable collections and a non-mutating version would return Self.

Sent from my iPhone

On Nov 23, 2017, at 3:45 PM, Xiaodi Wu<EMAIL_ADDRESS>wrote:
@dabrahams Well, yes, I am fully aware of what happens in those examples: implied in the statement is that x[..<3] will trap if it cannot give you three--it's not as though Swift can materialize nonexistent elements out of nowhere--and it will not work when indices are deliberately disabled by being an opaque type as in ranges (hence, "only if the index type is an integer").

The point is that some integer-indexed collections don’t start with 0. (-500...500)[..<3] doesn’t trap but it doesn’t return 3 elements.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

The point is that some integer-indexed collections don’t start with 0. (-500...500)[..<3] doesn’t trap but it doesn’t return 3 elements.

I'm quite sure that it's precisely because of this potential confusion that this notation was deliberately prohibited for ranges. That is, it's not an accident that (-500...500)[..<3] does trap:
error: cannot subscript a value of type 'CountableClosedRange<Int>' with an index of type 'PartialRangeUpTo<Int>'
(-500...500)[..<3]
~~~~~~~~~~~~^~~~~~

Think again.  Closed range indices just don’t happen to be Ints, but (-500..<500)[..<3].count works, as does [1,2,3,4].dropFirst()[..<3].count, and neither are 3.
Sent from my iPad

On Nov 24, 2017, at 11:17 AM, Xiaodi Wu<EMAIL_ADDRESS>wrote:
The point is that some integer-indexed collections don’t start with 0. (-500...500)[..<3] doesn’t trap but it doesn’t return 3 elements.
I'm quite sure that it's precisely because of this potential confusion that this notation was deliberately prohibited for ranges. That is, it's not an accident that (-500...500)[..<3] does trap:
error: cannot subscript a value of type 'CountableClosedRange' with an index of type 'PartialRangeUpTo'
(-500...500)[..<3]
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Yup, I get the point, and it serves a reasonable purpose for slices.
With respect to ranges, (-500..<500)[3] is deliberately disabled, (-500...500)[..<3] is disabled because the index type has no public initializer, and perhaps we ought to look into doing the same for (-500..<500)[..<3] by wrapping the integer in a similar type.
But to the original point, though, I'm wary of introducing more "stuff" into subscripts because it only amplifies the issue here. The difference in behavior between (-500..<500)[..<3] and the proposed (-500..<500)[..<^3] is anything but clear in notation.

The core team discussed this proposal again. We felt that the naming changes it proposes for the Standard Library are too extensive to consider given Swift's source compatibility goals. I'm closing this pull request and retroactively changing the status of SE-0132 from "Deferred" to "Rejected" in https://github.com/apple/swift-evolution/pull/898.

Thanks—even if I don't like the names, I'm glad to have some closure on this.


Change ARTS model to save args, env and channels as object arrays, not strings

Currently env, args and channels are saved as strings.

Changed args, env, channels, etc to JSONField when I started the ARTS refactor.


Axis Banner Message not fully visible after adding scroll bar in request view page

Describe the bug in current situation
Axis Banner Message not fully visible after adding scroll bar in request view page
Link bug to the User Story
Impact of this bug
Describe the impact, i.e. what the impact is, and number of users impacted.
Chance of Occurring (high/medium/low/very low)
High
Pre Conditions: which Env, any pre-requisites or assumptions to execute steps?
Steps to Reproduce
Steps to reproduce the behavior:

Login as IAO user.
Go to Request View Page of a request with valid Axis Id.
Check the Axis Banner.
See error

Actual/ observed behavior/ results
Some of the text on the right side of the banner is not visible.
Expected behavior
The message on the banner should be visible.
Screenshots/ Visual Reference/ Source
If applicable, add screenshots to help explain your problem. You an use screengrab.

Thanks for the fix, @aparna-aot


NPM readme contains inaccurate instructions

Just wanted to let you know that the NPM readme contains old instructions, I was halfway through it when I discovered that it was referring to an old version titled homebridge-cmd.
https://www.npmjs.com/package/homebridge-cmd4

Nevermind, the issue was that the instructions were incorrect for me, my folder location is /usr/local/lib/node_modules/homebridge-cmd4/ (not /usr/lib/node_modules/homebridge-cmd4)

BTW, the copy config.json step is kind of stupid, as it overwrites the previous Homebridge configuration without any warning.
Thankfully Homebridge makes frequent config.json backups, but I shouldn't have to restore my config just after following the installation steps while tired.

Thanks for the tip.  I'll have a look.
TTFN,
John
On Fri, Feb 7, 2020 at 10:38 PM NewsGuyTor<EMAIL_ADDRESS>wrote:

BTW, the copy config.json step is kind of stupid, as it overwrites the
previous Homebridge configuration without any warning.
Thankfully Homebridge makes frequent config.json backups, but I shouldn't
have to restore my config just after following the installation steps while
tired.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/45?email_source=notifications&email_token=ABSBCX4J3CXZY2ZJESVS7PLRBYSLDA5CNFSM4KRX23A2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELFIROI#issuecomment-583698617,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3WYTLVKOLGPPF5BMLRBYSLDANCNFSM4KRX23AQ
.


Add chart image to readme

Same idea as outlined in https://github.com/AstroDraw/AstroChart/issues/70 -- to immediately give the user the visual idea of what is possible.
You can see the rendered version of the README with image here: https://github.com/harlantwood/AstroChart/tree/patch-1?tab=readme-ov-file#astrochart

Hey @harlantwood ,
From where this image is? https://github.com/AstroDraw/AstroChart/assets/38769/0adc6822-7145-4e33-9e0b-53065e96d61a
Sorry, if I'm missing something, but I did not found where this image is.

Hey @harlantwood ,
From where this image is? https://github.com/AstroDraw/AstroChart/assets/38769/0adc6822-7145-4e33-9e0b-53065e96d61a
Sorry, if I'm missing something, but I did not found where this image is.

I made the PR via GitHub UI, uploaded the image in the UI, and GitHub gave it that URL… so, GitHub magic. ✨

I made the PR via GitHub UI, uploaded the image in the UI, and GitHub gave it that URL… so, GitHub magic. ✨
Hmmm... so I fhink that is better to upload the image to the repo in a folder and reference it in the README.

Added the image in a separate PR: #75.
We should merge that one first.
After that, the branch behind this PR will show the image correctly in its readme when clicking this link:
https://github.com/harlantwood/AstroChart/tree/patch-1#example
What you should see there will be something like:


Update deps

So sorry for the noise 🙈 Atom PR management picks the wrong upstream by default
Feel free to delete this PR if you would like (if you're on that beta feature of GitHub)


fix gildegoma issue

org.eclipse.egit.github.core.client.RequestException: Git Repository is empty. (409)

your profile should work now @gildegoma : https://github-profile-summary.com/user/gildegoma

@tipsy thank you 😉 ❤


No way to clear cell outputs

I was unable to find a way to clear the cell outputs in the Visual Studio Notebook Editor.

@zewditu


Support Lucene HNSW merge optimization

Description
In Lucene, in https://github.com/apache/lucene/pull/12050, an optimization was added to create a new segment HNSW graph by initializing the graph from the largest graph without any deletes from the collection of segments-to-be-merged. Also, see https://github.com/apache/lucene/issues/11354 for related benchmarks. This will speed up merge operations for larger graphs.
This change will go out in Lucene 96, which we will pick up by default - we wont have to make any code changes. Once we are able to test this change in OpenSearch, we should run performance tests to measure benefit.

With 2.8 k-NN received Lucene 9.6 with the mentioned fix, performance test is completed so we can check on changed numbers. Perf results added to release issue: https://github.com/opensearch-project/k-NN/issues/905


Implement remote activation

The remote activation features is missing from the C# implementation.
I've added the Register and GetKnownKinds methods.
We need the Activator actor to be implemented too.

Fixed by #88


Files Refuse To Import

🔍 Issue Description
This could 100% be an issue on my side with either the files or Blender itself. In the file exploring section after selecting "Import" none of the files appear. When I disable the filter and force them to import it seems to skip them all as you can see by the below image showing the import time of 194 files.

🛠 Sollumz Version(s)
2.5.0
🖥 Blender Version(s)
4.2.1 LTS
🧩 Area
Navmesh
🔄 Reproduction steps
Please find attached one of the many files. Simply attempt to import the file. prop_vesp_5_2_detec_b.zip
🎯 Expected Result
It is expected to import correctly
⚠ Current Result
Its import gets skipped and still returns a success and no information or indication that something went wrong.
📎 Attachments
Relevent files already attached

You need CodeWalker to export them as XML first. Then, you import those XML files in Blender.

Thats fair, thank you <3. I will do this now. This issue can be closed or deleted and I will make a new one if I have more issues


The value doesn't change to red when state=problem

You stated in the issue before:

The conditional formatting is there..
      if ( hass.states[config.entity].attributes.problem.indexOf(_sensors[parseInt(i)]) !== -1){
        _class += " state-problem";
      }

      .state-problem {
        color: var(--google-red-500);
      }

However this does not seem to work.
See screenshot:

I think the problem is with the color: var(--google-red-500);
If I change the css in the chrome devtools to color: #db4437; it works fine.

This is the same as the plant status card uses - https://github.com/iantrich/home-assistant-polymer/blob/ef18f9eac99dd8b5bc04fc1349ce4cde9f46c946/src/panels/lovelace/cards/hui-plant-status-card.ts#L194

Hmm.. that's weird. Since the default plant card works fine and shows red text, but your custom card doesn't show red text.
Also the default plant card shows color: #db4437; in the chrome devtools when checking the CSS from the default plantcard, so somewhere this gets converted from color: var(--google-red-500); to color: #db4437;

It works for me. I'm using the latest released version. The CSS var(--xxxxx) variables are converted in the Home Assistant themes.

Hmm weird, i'm fully updated with HassOS and HA Core. Still the text won't show as red.
I've fixed it for now by changing the code to the hex value.

I have the same problem.
Latest HA Core 0.114.4 and any theme has the same problem...


Design layout

The aim of this task is to design layout in Figma.

Duplicate of https://github.com/blumilksoftware/meetup/issues/33.


neo4j_config.session leading to stack too deep

Found this weird issue after upgrading to rails 5.1.
Whenever the final_session_config  method is called on neo4j/railtie.rb and it calls neo4j_config.session I get a stack level too deep error. The issue seems to be related with the ActiveSupport::OrderedOptions which allows to call neo4j_config.session.
I was able to get around it by changing the code to call neo4j_config[:session] instead.
Would gladly submit a PR with the alteration if need be.
neo4j gem version: 8.3.4
neo4j-core gem version: 8.1.0

Thanks, released as version 9.1.3!


Improve the metadata and check finding and move variables to defaults

Many improvements in the ansible code:

Move the actual check roles to the checks folders. This makes easier to find the real checks in the code
Move the metadata information to the defaults folder. This allows us to use these variables in the checks execution as well, which is really interesting if we want to add some new options, like on_failure: warning, etc
Automatize the check and metadata files finding. Now we don't need to declare all the checks, we just need to put them in the checks folder.

PD: Most of the changes are just movement of metadata variables
@brett060102 Could you have a look?

@brett060102 Issues fixed. Could you review back again? Thanks


Add snippet for page component block and Route

I added page component, route, and redirect route. Still don't sure that I should separate this to another file or not.

@teerasej thanks for the PR. Not sure yet if we need to separate it into another file. We can see when adding more components


Fixing another SSR bug when navigating

Fixing a bug in SSR when the modelPath is not sanitized correctly when passing the model data on init.

eslint errors.. il take a look at later


Starting TREE header from 0 instead of nCores

The tree number in the header was starting from nCores instead of 0, since treesStarted is initialized to it.
Inside WriteTree this number is only used to print the header so I changed it to treesFinished since I noticed --progress uses it and reports the tree numbers correctly.
Output of grep TREE on the .sf file before:
TREE=16,TARGET="B:ispathogenic"
TREE=17,TARGET="B:ispathogenic"
TREE=18,TARGET="B:ispathogenic"
TREE=19,TARGET="B:ispathogenic"
TREE=20,TARGET="B:ispathogenic"
(...)
TREE=98,TARGET="B:ispathogenic"
TREE=99,TARGET="B:ispathogenic"
TREE=100,TARGET="B:ispathogenic"
TREE=100,TARGET="B:ispathogenic"
TREE=100,TARGET="B:ispathogenic"
(repeats till the end)

Output of grep TREE on the .sf file after:
TREE=0,TARGET="B:ispathogenic"
TREE=1,TARGET="B:ispathogenic"
TREE=2,TARGET="B:ispathogenic"
TREE=3,TARGET="B:ispathogenic"
TREE=4,TARGET="B:ispathogenic"
(...)
TREE=94,TARGET="B:ispathogenic"
TREE=95,TARGET="B:ispathogenic"
TREE=96,TARGET="B:ispathogenic"
TREE=97,TARGET="B:ispathogenic"
TREE=98,TARGET="B:ispathogenic"
TREE=99,TARGET="B:ispathogenic"
<<EOF>>

I'm travelling this week but good catch, i'll merge this in when i'm back home.

:+1:
No problem. I opened issue #50 too, but that's more of a question, no hurry.

Do you mind if I close and re-open this? It's following the master on my fork instead of a branch, as it should be, I want to fix it.

Go a head...I need to find a chunk of time to land this and some other
stuff i've been working on locally. Hopefully soon.
On Tue, Jun 30, 2015 at 12:02 PM, Vitor De Mario<EMAIL_ADDRESS>wrote:

Do you mind if I close and re-open this? It's following the master on my
fork instead of a branch, as it should be, I want to fix it.
—
Reply to this email directly or view it on GitHub
https://github.com/ryanbressler/CloudForest/pull/49#issuecomment-117284727
.


Update microk8s howto docs prerequisites

Updating the MicroK8s howto docs to make the users aware of the --enable-bootstrap-token-auth. If it's not enabled, the bootstrap authentication process fails with a 401 Unauthorized.

thank you!


Cannot filter journal log lines from loki.source.journal with loki.process component

What's wrong?
Dropping specific lines from loki.source.journal matching a stage.drop stage from loki.process component does not have any effect and all journal logs are sent.
Steps to reproduce
Given the provided configuration, I would expect no logs in Loki, yet all logs are sent. Changing expression to any other value also produces the same result.
System information
Linux 5.10.225-213.878.amzn2.x86_64
Software version
Grafana Alloy v1.4.0
Configuration
loki.source.journal "logs" {
  path = "/var/log/journal"
  relabel_rules = discovery.relabel.journal.rules
  forward_to = [loki.process.journal.receiver]
}

discovery.relabel "journal" {
  targets = []

  rule {
    source_labels = ["__journal__transport"]
    action = "keep"
    regex = "kernel"
  }

  rule {
    source_labels = ["__journal__hostname"]
    target_label  = "instance"
  }
}

loki.process "journal" {
  stage.drop {
    expression = ".*"
  }

  forward_to = [loki.write.default.receiver]
}

loki.write "default" {
  endpoint {
    url = "http://loki:3100/loki/api/v1/push"
  }
}

Logs
No response

Hi @sergeykranga, are you sure that you are using this config? Could you be looking at old logs on Loki? When I use this config, I see journald logs:
loki.source.journal "logs" {
  forward_to = [loki.echo.default.receiver]
}

loki.echo "default" {}

When I switch to this one, I no longer see logs:
loki.source.journal "logs" {
  forward_to = [loki.process.journal.receiver]
}

loki.process "journal" {
  stage.drop {
    expression = ".*"
  }

  forward_to = [loki.echo.default.receiver]
}

loki.echo "default" {}

I also see from the metrics that the logs were dropped due to loki.process:
# HELP loki_process_dropped_lines_total A count of all log lines dropped as a result of a pipeline stage
# TYPE loki_process_dropped_lines_total counter
loki_process_dropped_lines_total{component_id="loki.process.journal",component_path="/",reason="drop_stage"} 27


ConsulDiscoveryClient uses the node name instead of the address for the service instance URI

I'm still new to Consul so I may have confused myself but when I saw the property preferIpAddress I assumed it was a switch between hostname vs ipAddress but it seems that it (also?) toggles between node names and the actual host providing the service.
The behavior is therefore very different when you run in an environment where the Consul server is not running on the same host as your services. If you have preferIpAddress false you basically get the wrong URIs.
Here is my very basic code:
    @Autowired
    private DiscoveryClient discoveryClient;

    public void printInstances(String serviceName) throws Exception {

        List<ServiceInstance> list = discoveryClient.getInstances(serviceName);
        if (list == null) {
            System.out.format("===== Null list returned for %s%n", serviceName);
        } else {
            System.out.format("===== Found %d instances of %s%n", list.size(), serviceName);
            for (ServiceInstance serviceInstance : list) {
                System.out.println(
                        serviceInstance.getServiceId() + " -- " + serviceInstance.getUri());
            }
        }
    }

With preferIpAddress=false, the output (with hostnames simplified) is:
===== Found 2 instances of myservice
myservice -- http://consulhost:9010
myservice -- http://consulhost:9010

With preferIpAddress=true, the output is then:
===== Found 2 instances of myservice
myservice -- http://servicehost1:9010
myservice -- http://servicehost2:9010

Note that Consul server runs on port 8500, so there's nothing running on port 9010 on consulhost.

This may come from a6b2519475d27767782fd53974d3457c798b64c2 which fixed #76

I'm thinking preferIpAddress doesn't have any business in getCatalogServiceHost.

:+1:


Content-Type from layer HEAD checks used on image push for manifest 2v2 images

For Manifest 2v2 images, during an image push, Docker relies on the Content-Type returned from the layer HEAD check to set the mediaType in the manifest being pushed.
On the first push of the config layer, the mediaType is set as "application/vnd.docker.distribution.manifest.v2+json", but on later pushes it relies on the Content-Type being returned. As a result, registries that don't provide this "Content-Type" end up either missing the mediaType in the subsequent images being pushed or setting incorrectly (i.e. to "text/plain"). The Registry V2 API documentation includes only "Content-Length" and "Docker-Content-Digest" for successful responses and does not mention "Content-Type".
Is this intended behavior for Docker? If so, how should a registry determine the Content-Type for the config layers?

The content type headers are part of the specification; Given that this is about the registry, could you reopen this in that issue tracker, because that's where that specification lives https://github.com/docker/distribution/tree/master/docs/spec (https://github.com/docker/distribution/issues). Thanks!

I've posted #2084 to the registry repository.

Thank you!


dgoss race condition on sercvice boot

As linked in https://github.com/aelsabbahy/goss/issues/324 and https://github.com/aelsabbahy/goss/issues/323 I am building a Docker image that would validate the automation. The goal is to use the same test suite for Docker and for real installs ad-hoc basis.
So I have my own docker image that installs and sets up RabbitMQ. The only difference there is on real system it runs through systemd and on Docker its:
CMD ["rabbitmq-server"]

I've noticed a difference in behaviour when running dgoss run and edit.
dgoss run
dgoss run rabbitmq-docker-image
INFO: Starting docker container
INFO: Container ID: <ID>
INFO: Sleeping for 0.2
INFO: Running Tests
User: rabbitmq: exists: matches expectation: [true]
Port: tcp6:5672: listening:
Expected
    <bool>: false
to equal
    <bool>: true
Package: rabbitmq-server: installed: matches expectation: [true]
Package: rabbitmq-server: version: matches expectation: [["3.5.0n"]]

dgoss edit
dgoss edit rabbitmq-docker-image
INFO: Starting docker container
INFO: Container ID: <ID>
INFO: Run goss add/autoadd to add resources
sh-4.2# goss validate
....

Total Duration: 0.054s
Count: 4, Failed: 0, Skipped: 0

RTFM applies to this. Setting GOSS_SLEEP sorted it out. I guess it would be nice to apply this in a smarter way such as waiting for port listen or file appearing rather than expanding all the test runs by a set amount of time representing the worst case scenario or otherwise being flaky.
Example test for this is simple bash script:
timeout 120 bash -c 'until echo > /dev/tcp/${IP}/9042; do sleep 1; done

where IP is the IP to be monitored.

Take a look at goss_wait and the related options.
Here's an example:
https://github.com/aelsabbahy/dgoss-examples/tree/master/vote
Feel free to reopen if that doesn't meet your needs.

Looks exactly like what I need. I'll test it tomorrow.

So it does work, however, is there a timeout to that? If I understand, I should pass something like that through "GOSS_WAIT_OPTS", but there is no information for what it refers to or what it accepts or not that I can find.


io: 2013.12.04 -> 2015.11.11

Motivation for this change
Updating IO language
Things done

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

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Updating IO language to latest version

Help! the failure in hydra is not locally reproducible.

I never could get this to build either, it consumes all my memory and crashes. If memory serves, io has been broken for a long time, so this update couldn't make it any worse in any case.

@joachifm Are you getting the same errors as in hydra? (a permission denied error)
Also, at what point does the compilation die in your case? I have compiled it using a 4GB RAM machine

@vrthra oh, are you talking about travis? This is the error I got, IIRC, same as Hydra: https://hydra.nixos.org/build/36719171/nixlog/1/raw

@vrthra if you can build this locally in a sandbox, I'd trust that more than travis.

@joachifm This seems to build without fail using nix-env -i io -f ~/nixpkgs --option build-use-chroot true in my machine.

If you're on NixOS, I think you must configure the Nix daemon to use sandboxing, passing it via command line won't suffice.

I have build-use-chroot = true set on /etc/nix/nix.conf too

@joachifm there is something odd here I think. I have a 4G NixOS box I use for Nix development, where I can build and install this package. However, when I try installing it on a VM, with 12G, the memory use rapidly claims as you mentioned, and fails on IoAsyncRequestInit.c generation. Not sure why this is happening. Putting this on hold until I can understand what is happening.

On further investigation, it seems that there is something specific to a VM happening here. Checked the build in a NixOS installation on a Macbook Pro, and the build completed just fine, with IoAsyncRequestInit.c generation compiling really fast.

@vrthra I think we can merge this anyway. You could specify an empty meta.hydraPlatforms to make explicit that there's no point in trying to build it on the build farm, until the problem is resolved.

@joachifm I disabled addon generation completely. It builds on my VM. could you please see if this fixes the problem at your machine too? If so, it can be merged now, and the addon problem can be investigated later.

@vrthra it builds for me now, nice work


[sqllab] proper, quoted, select * on the server side

Reserved words should be properly quoted now, indent is arguably better than before

LGTM, once test is fixed.


Interpolation in attachment text doesn't work

I'm having this issue too. Doing something like this:
attachments:
      - color: '#99ccff'
        text: |
          Build status: running
          $ATC_EXTERNAL_URL/teams/$BUILD_TEAM_NAME/pipelines/$BUILD_PIPELINE_NAME/jobs/$BUILD_JOB_NAME/builds/$BUILD_NAME

will output the string verbatim, whereas I would expect it to interpret the metadata variables.

I will take a look at this tonight, @analytically

Thanks!

This works great - interpolation of values in the fields array would also be useful.

+1 for the fields array too.


Domain access request from sandbox

What domain(s) needed? Please describe.
accounts.google.com
earthengine.googleapis.com
Why this domain(s) needed? Please describe.
Authenticate to GEE for data access
Provide impacted notebook reference and purpose.
None - per-requisite for demonstrating data collaboration between DEA and GEE
Additional context
Assisting in overlaying DEA data holdings with GEE data holdings.

Resolved


Allocations in thread sampler

In recordStackForAllThreads: https://github.com/EmergeTools/ETTrace/blob/f791b54c68f62cbf5fa4b0253d91182c522c2c21/ETTrace/Tracer/EMGTracer.mm#L166 some objects are created using new. This is before threads are suspended so does not cause reentrancy issues, but is still not the most performant way to implement this function. We should avoid allocating memory here since it's called every time we record a new sample.

This is now fixed


Added an API for reading direct counters associated with a table in the p4 program

@serhatarslan-hub This looks great! Thank you for adding this functionality.
Can you add a few lines of documentation to the Reading Counters section of the README? Also, do you think you could extend examples/counter.p4app with a direct counter in the data plane, and an example of how it's read from the control plane?

You can find the documentation and example on my last commit.

:+1: LGTM! Thank you @serhatarslan-hub


removed hendrik and added real maintainers

Please ask
@RickyLB
@izik
@0xivanov
@andrix10
to visit https://github.com/LFDT-Hiero to accept the invite


SDF icon option to generate sprite

elastic/spritezero has an option to generate SDF icon. spritezero of elastic version relies on @elastic/fontnik which also have similar issue with mapnik, I am not sure SDF icon can be generated without fontnik library.
However, it would be good if sprite-one also can have an option for SDF icon.

I see.
I don't know how to generate SDF icons however I will try it.

This stackoverflow can be useful for generating SDF icon
https://stackoverflow.com/questions/63299999/how-can-i-create-sdf-icons-used-in-mapbox-from-png


[HOLD for payment 2023-12-20] [$500] Request money - Not here page appears in RHP after requesting money

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v1.4.11-1
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Go to staging.new.expensify.com.
Open a new chat,
Click + > Request money.
Enter amount and proceed to confirmation page.
Click Request.
(Might need to repeat Step 3 - 5 to see the issue).

Expected Result:
Not here page will not show up in RHP after requesting money.
Actual Result:
While RHP is closing, not here page can be seen in the RHP.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/11bbdfe2-84f1-4167-9f45-cb5e50465e17

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01e13942c515d900b4
Upwork Job ID:<PHONE_NUMBER>696989184
Last Price Increase: 2023-12-11
Automatic offers:

getusha | Reviewer | 28036036
paultsimura | Contributor | 28036038

I'm going to demote this from being a deploy blocker. It doesn't effect the user in any way and the flow still works. I've applied the help wanted label to get some more eyes on this.

Ah, cool. I didn't know about the isFocused hook. Looks like that would do the trick. I like using shouldShow. I don't think we want a loading indicator during those transitions.

Thanks. The PR is ready for review: https://github.com/Expensify/App/pull/32849

@Julesssss This shouldn't have been closed as it's not paid out yet, if I'm not mistaken.

Thanks

$500 to @paultsimura for Contributor, paid and thanks!
@getusha could you take a spin through the regression checklist, and then accept the offer?

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x] The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/28618

[x] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/28618/files#r1434478894

[x] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/a

[x] Determine if we should create a regression test for this bug. i think this bug is minor and hard to notice so No*.

[ ] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

@peterdbarkerUK accepted the offer

@peterdbarkerUK Is there more to do here to complete the payments?

Nope, was just OoO.
Payments processed!


Load Weights in demo.py going wrong - YOLOV3 OBJECT DETECTION

Hello,
while testing for frist time. I downloaded the yolo weights and try the image_demo.py. but at load_weights() in conv_layer_name = conv2d_9
model.Summary():
conv2d_9 (Conv2D)               (None, 52, 52, 256)  294912      zero_padding2d_2[0][0]
traceback
Traceback (most recent call last):
  File "image_demo.py", line 41, in <module>
    utils.load_weights(model, "./yolov3.weights")
  File "/PATH/TensorFlow2.0-Examples/4-Object_Detection/YOLOV3/core/utils.py", line 51, in load_weights
    conv_weights = conv_weights.reshape(conv_shape).transpose([2, 3, 1, 0])
ValueError: cannot reshape array of size 95566 into shape (256,128,3,3)

Any clue of what is going on? i dont really want to change the load_weights func.
kind regards

Nevermind. Only weights file corrupted.


Loading the url tag from the future library is deprecated.

Using the url tag directly has been supported for quite a while.
django/templatetags/future.py:24: RemovedInDjango19Warning: Loading the`url` tag from the `future`
library is deprecated and will be removed in Django 1.9. Use the default `url` tag instead.

We can't do that as long as we support Django 1.4 LTS, as the build failure shows.

Do you have a development branch I can target instead of master? It seems extremely wasteful to stall all new development until Django 1.4 is deprecated sometime in October.

Well, it's also quite wasteful to engage in hyperbolic arguments that discredit your position.
This doesn't stall all new development, plenty of tickets can move forwards.

Quick to jump on people who are trying to be supportive to the debug-toolbar. @aaugustin  Try working on your aspergers instead of your programing abilities.

Kevin, please refrain from personal attacks. The toolbar follows Django's version support. That means Django 1.4 will be supported by the toolbar until October.

I'm just trying to pave way for the upcoming Django 1.8 release. But it was apparently in vain.

Here's a couple of suggestions though on my way out the door:

Create a LTS/1.4 branch, merge everything to master and backport bugs and stuff to the release branch.
Do the opposite, create a develop (or something) branch which is allowed to break backward compatibility for forward compatibility. And merge it to master when appropriate.
Just create a new release (v2.0.0 or something) and tell everyone still on Django 1.4 that they have to install < v2.0.0. This is kind of what iPython did with Python 2.6 and their v2.0 release.

Now I remember why I refrained from touching this repo in months... Anyway...
@renstrom Our problem is that the debug toolbar gets at best five hours of its maintainers' time per month (@tim-schilling and myself).
A handful of people have offered to help but none of them have gone as far as submitting a patch for a non-trivial issue, which isn't a good indicator of long term commitment.
There are plenty of things we could do, but we aren't keen to:

add admistrative overhead (like managing backports): that could make us go from "make a release with some bugfixes from time to time" to "not making any releases"
do anything that could result in a stream of support tickets (like requiring different versions of the toolbar depending on the Django version)

I'm not saying this is a great situation, but that's where we are. It used to be worse: at some point there was an unmaintained! disclaimer in the README.

Right, fair enough, it's not always easy to maintain a popular repo. I don't really have a great solution, just thought I'd offer some suggestions. Thanks for taking your time reply though.

Cool. I understand you were trying to help and I'm sorry we don't have a good solution for accepting help in this area at this time.

One way to fix the original issue without breaking Django 1.4 is to ship different sets of templates for different Django versions. Thanks @apollo13 for the suggestion.


Wind speed meaning in different data

Hi, dear author, another question.
I fount that the wind speed in your project is normalized by min&max of uv in one data.
And when I have two different data that min&max of uv is different far away.  like one's uv is smaller total, the another's uv is bigger total. then I can't tell which position has a bigger wind in your project when I compare them at the same time.

If I want have the same meaning of wind speed in project by many different data, what should I do？

Probably you can merge these data into a single NetCDF file?  In this way all data is normalized with same min/max.

Probably you can merge these data into a single NetCDF file? In this way all data is normalized with same min/max.

I think I need a more free way. because the data is random. Maybe I will define same min/max follow common sense, and use this min/max in all data.


Dataset used

Hi,
I'm currently working on table detection myself. Would you mind sharing which dataset you used for this project and how to get it?
Thanks!

I have created my own dataset. As it is an old project i am unable to find the dataset.

Thanks for the response. I actually ended up creating my own dataset as well :) Cheers

Great.

@mroyce1
Can you share your implementation?

@LidorPrototype training code?

Yes looks like he/she was trying a machine / deep learning approach with it, and I want to see if its possible to use and learn from his approach with your code.


Fixed #27505 -- Added i18n for Paginator's errors

I'd like to understand the use case a bit better. How are these messages user facing (is Django doing that or only your own application)? (It would be useful to elaborate on the use case in the ticket rather than in the PR.)
About the implementation, it doesn't seem ideal that to override a single message, you have override the entire error_messages. I guess some implementation similar to validators with default_error_messages and an error_messages kwarg might be better.

You can never know in advance whether those messages are user facing or not, it depends on the exception usage done by the developer. It does not harm to make them translatable.
@toshka I'd like to see separate commits, one that simply mark the strings for translation (that I'll push ASAP), and one that makes them overridable (to be discussed as of Tim's message).

buildbot, add to whitelist.


Error whil trying to set fan mode white climate sensor

Hello,
In the Klover application my stove has 4 configuration parameters: Ventilation (OFF, from 1 to 5 and A), Power (from 1 to 5), Stand by (On or OFF) and Temperature (from 7 to 40).

In Home Assistant, AguaIOT reports 2 climate entities.
The first, with the parameters Temperature and Power.
Moreover this last parameter is displayed "Fan mode" instead of "Power".

The second climate entity has only the parameter "Fan mode" (the real one this time).

At first, I have a problem when I want to change the parameter "Fan mode". Home Assistant indicates "Climate/set_fan_mode service call failed. Value muste be between 0 and 6." Would it be possible to fix this problem please?

Secondly, is it possible to combine all the parameters in a single climate entity?
Thank you very much for your work.
HA Core log :
`Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:238
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 16:38:57 (1 occurrences)
Last logged: 16:38:57
[547647552192] Value must be between 0 and 6
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 238, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2067, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2104, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 272, in handle_service
return await service.entity_service_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 878, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 948, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/config/custom_components/aguaiot/climate.py", line 358, in async_set_fan_mode
await self._device.set_register_value_description(
File "/config/custom_components/aguaiot/aguaiot.py", line 611, in set_register_value_description
await self.set_register_value(key, value)
File "/config/custom_components/aguaiot/aguaiot.py", line 585, in set_register_value
value = self.__prepare_value_for_writing(key, value)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/aguaiot/aguaiot.py", line 455, in __prepare_value_for_writing
raise ValueError(
ValueError: Value must be between 0 and 6`

Hi @38decibel, thank you for the detailed bug report. I answered upon most of your questions/comments here.
On the value error I will take a look. Can you please supply your diagnostics file?

Please find my diagnostic file
config_entry-aguaiot-eddedabcfdf71fb41efe83fd4e1718fb.json

Value error should be fixed in v0.3.5.

Hi,
Thanks a lot, that's work fine !


Docker final delivery

This PR updates the Dockerfile, specfile, and add missing dependency in environments.yml for the final delivery.
Please note that s1reader is being installed from conda forge as it became available thanks to @scottstanie.

@vbrancat Thanks for the quick turnaround. I'll merge this after making sure that it passes  the CI test.

two things-

If I make a lockfile from the environment here, and I compare it to the one by deleting the Testing and Raider sections, it goes from 261 lines to 201 lines (so 60 fewer dependencies).
The biggest one is that geopandas is used in the QA script, imported at the top level, so it's unavoidable right now it's unavoidable. it would be nice to not have to install all of geopandas (which has a huge dependency tree, e.g. scitkit-learn) just to read the shapefile. Here's a demo of using shapely/fiona instead: https://github.com/seongsujeong/COMPASS/compare/docker_final_delivery...scottstanie:COMPASS:docker_final_delivery_shapely?expand=1

What if we put the raider depencies in a separate file and called --file ... twice on the other one to keep it separate? We could then also delete the testing section of the environment.yml file because we already have a separate testing requirements file so we could just reference that (though I dont think we need to install testing dependencies into the main docker anyway?)

2. he other one to keep i

Totally agree on the dependency of geopandas. I expressed my concerns on it in private conversations with @seongsujeong. I have provided Python code on how to open a shapefile with ogr. @seongsujeong let's work on avoiding adding this dependency.

two things-

If I make a lockfile from the environment here, and I compare it to the one by deleting the Testing and Raider sections, it goes from 261 lines to 201 lines (so 60 fewer dependencies).

That is expected. And I hope you have made sure that you have made sure that CI passed with the lockfile (i.e. not the YAML file) you have without Testing and RaiDER, especially without Testing.
In the PR #196, you have updated environment.yml. I appreciate your effort to make COMPASS as lightweight as possible, but we need an environment that makes COMPASS works, including the unit test. You said it's fine, and I initially agreed that it should be okay, because it passed the CI, but please note that the dependency during the CI gets installed by using specfile.txt. So CI pass on that PR does not mean environments'yaml is okay, unless you update the specfile based on the new yaml file.

The biggest one is that geopandas is used in the QA script, imported at the top level, so it's unavoidable right now if you want to run s1_geocode_slc.py. it would be nice to not have to install all of geopandas (which has a huge dependency tree, e.g. scitkit-learn) just to read the shapefile. Here's a demo of using shapely/fiona instead: https://github.com/seongsujeong/COMPASS/compare/docker_final_delivery...scottstanie:COMPASS:docker_final_delivery_shapely?expand=1
After the discussion with @vbrancat , I decided to write shapely-based anyhow. Doing that will get rid of the necessity of geopandas. But please note that geopandas is a dependency of RaiDER's dependency, and we need RAiDER for the final SAS delivery. I cannot guarantee that RAiDER works without geopandas.

What if we put the raider depencies in a separate file and called --file ... twice on the other one to keep it separate? We could then also delete the testing section of the environment.yml file because we already have a separate testing requirements file so we could just reference that (though I dont think we need to install testing dependencies into the main docker anyway?)

Not sure if you mean to have a separate .yml file or lockfile, but in either case, I am not sure if conda will attempt to resolve the dependency, which I don't want. The .yml for sure, The lockfile I'm not sure.
Please, note that we need to focus on two things as ADT: to deliver the SAS in the spec we promised, and to make CI run correctly to deliver SAS that is robust enough. Optimizing the Docker size is a great thing we can do before the delivery, and I again thank you for your efforts, suggestions, and tips. They are really helpful. However, I am going to focus more on the first two prongs rather than the latter one.
About the implementations I've recently put in s1_cslc_qa.py, I will spend some time to re-write it using shapely. I'll either submit another PR, or include that in this one.

@LiangJYu I've changed the implementation of the land mask computation to use osgeo modules (i.e. ogr, osr, and gdal). Hope you don't mint taking a look at the new code. Than you :)


Fix comment regarding macro order

Follow-up for #130.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT license.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 89.49%. Comparing base (ae34509) to head (1c7da1c).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #131   +/-   ##
=======================================
  Coverage   89.49%   89.49%
=======================================
  Files         173      173
  Lines       31416    31416
=======================================
  Hits        28116    28116
  Misses       3300     3300

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

Thanks for fixing this.
It would be nice to know why this is... perhaps one of the two crates can be changed so that the order can stay the same in the two cases. It's not super important now, but I hope to look into this eventually.

It would be nice to know why this is

Apparently uniffi can't deal with the lifetimes in the code generated by async_trait.


Does WSLg will arrive in Windows 10 21H2?

Hello,
Since Windows 11 was announced and the readme states:

WSLg is going to be generally available alongside the upcoming release of Windows.

I'm not sure if WSLg will be included in Windows 10 21H2; my computer will not support Windows 11, so I hope that WSLg won't be exclusive for Windows 11..

Maybe this question belongs to the Discussions tab


Platform spec missing

Hi! Maybe I just miss an important point, but I don't get on what platforms it is supposed to work. Is it Ubuntu 14.04? Or 12.04. Thanks for clarification!

The master branch currently targets 14.04 (trusty) and I don't believe (but haven't confirmed) that this code ever supported 12.04. The initial commit is from September 2014 so I'd bet that it was built for Trusty.

Ok thx for the clarification!


LDAP protocol improvements and scan-network module bugfix

In this pull request I tried fixing some LDAP related issues.
Changes
cme/protocols/ldap.py:

When the --no-smb is provided, automatic domain lookup is disabled and --domain should be provided.
The LDAP module uses the kdchost or domain parameter to resolve the target ldap server(s?!), instead of designated host parameter. I restored the use of the host parameter as the ldap server
The baseDN is generated using the kdchost or domain parameter, depending on the login function (kerberos_login/ plaintext_login/hash_login), which does not make sense. For example when the kdchost points to an actual DC (e.g. dc01.test.com), this results in the invalid baseDN dc=test,dc=test,dc=com. Additionally, using the domain parameter result would result in an incorrect baseDN  during cross domain/forest authentication where user domain != target domain. I added twp additional methods to resolve the baseDN: 1. the baseDN parameter and 2. anonymous LDAP lookup to resolve the baseDN.
During kerberos login the self.username variable is never defined, this can cause issues in other places (e.g. the new whoami module). I implemented the ldap whoami request to retrieve the username after succesfull kerberos authentication.
Fix various inconsistencies between ldap login functions including: missing admin checks, missing add_user_bh calls and improved success logging messages

cme/modules/scan-network.py:

The ldap2domain function does not check if the prodived DN is lowercase when searching for "dc=".

Other notes that are not (yet?) addressed:

Should the ldap module really implement the --local-auth parameter?
The ports parameter is not used

Hello thanks for the PR. This is a lot of change while you are solving different problem in one PR.
Can you post some screenshot for the cross domain fix before and after ? Actual code was working pretty well for this kind of situation last time I use it so I'm kind of surprise.

Hi, yes sorry if there are to many changes in this PR. While reading and fixing the code. I came across quite a few inconsistencies and with the limited time I have I just tried to fix as much as possible.
My current lab environment looks like this:
forest 1: nurfed.lab (dc01.nurfed.lab)
forest 2: test.lab (dc02.test.lab)
I deduced the following command for my lab environment (using your sample command):
cme ldap nurfed.lab -u nurfedlab.user1 -p 'McsvgVw3to7cBRy8' -d nurfed.lab --kdcHost dc02.test.lab --users
First of all, I have to note that the actual command seems odd because, it will perform NTLM authentication and therefore the kdcHost parameter should not be used? Where I would expect the command to connect to nurfed.lab, it actually connects to the kdchost dc02.test.lab (as shown below).
As seen in the screenshot below, the command fails because the incorrect basedn "dc=dc02,dc=test,dc=lab" is generated based on the kdchost.

After tweaking the kdcHost parameter, we get the following command:
cme ldap nurfed.lab -u nurfedlab.user1 -p 'McsvgVw3to7cBRy8' -d nurfed.lab --kdcHost test.lab --users
The results in the following output, the command reports that it connected to DC01, but in fact it actually connected to DC02.TEST.LAB and returned it's users.

With my code changes, the following command would ignore the kdchost parameter due to ntlm auth and connect to nurfed.lab:
cme ldap nurfed.lab -u nurfedlab.user1 -p 'McsvgVw3to7cBRy8' -d nurfed.lab --kdcHost test.lab --users
The adjusted command to connect to test.lab would look like the following :
cme ldap test.lab -u nurfedlab.user1 -p 'McsvgVw3to7cBRy8' -d nurfed.lab --users

Hi,
Sorry if there are to many changes in this PR. While reading and fixing the code. I came across quite a few inconsistencies and with the limited time I have I just tried to fix as much as possible.
My current lab environment looks like this:
forest 1: nurfed.lab (dc01.nurfed.lab)
forest 2: test.lab (dc02.test.lab)
I deduced the following command for my lab environment (using your sample command):
cme ldap nurfed.lab -u nurfedlab.user1 -p 'McsvgVw3to7cBRy8' -d nurfed.lab --kdcHost dc02.test.lab --users
First of all, I have to note that the actual command seems odd because, it will perform NTLM authentication and therefore the kdcHost parameter should not be used? Where I would expect the command to connect to nurfed.lab, it actually connects to the kdchost dc02.test.lab (as shown below).
As seen in the screenshot below, the command fails because the incorrect basedn "dc=dc02,dc=test,dc=lab" is generated based on the kdchost.

After tweaking the kdcHost parameter, we get the following command:
cme ldap nurfed.lab -u nurfedlab.user1 -p 'McsvgVw3to7cBRy8' -d nurfed.lab --kdcHost test.lab --users
The results in the following output, the command reports that it connected to DC01, but in fact it actually connected to DC02.TEST.LAB and returned it's users.

With my code changes, the following command would ignore the kdchost parameter due to ntlm auth and connect to nurfed.lab:
cme ldap nurfed.lab -u nurfedlab.user1 -p 'McsvgVw3to7cBRy8' -d nurfed.lab --kdcHost test.lab --users
The adjusted command to connect to test.lab would look like the following :
cme ldap test.lab -u nurfedlab.user1 -p 'McsvgVw3to7cBRy8' -d nurfed.lab --users

I see, interesting ! I will review it :)

I tried to make a similar comparison for kerberos authentication and I came across additional issues. It seems impacket ldap implementation fails to properly request kerberos tickets for cross forest authentication and It only succeeds when there already are kerberos tickets in the ccache.
During the testing of my code there were proper kerberos tickets in my ccache file and therefore I didn't encounter errors  during cross forest authentication in the past. Thereforce I conclude the my code also doesn't fix cross forest auth but it does fix the following odd behavior.
Tthe following two commands result in unexpected behavior, Where I would expect the command to connect to test.lab, it actually connects to the kdchost dc01.nurfed.lab. The screenshot also incorrectly shows DC02 instead of DC01.
cme ldap test.lab -k -d nurfed.lab --kdcHost dc01.nurfed.lab --users
cme ldap dc02.test.lab -k -d nurfed.lab --kdcHost dc01.nurfed.lab --users

I'm not sure if I'm capable enough to fix impacket ldap or add a workaround in cme myself, but I'll have a look.

Hi mpgn,
Please ignore my comment about impacket ldap cross domain kerberos authentication being broken. I think something in my lab broke instead, (ended up rebuilding everything last night)...
My code however did still have some issues with cross domain kerberos authentication and the kerberoasting/asreproasting commands. This should all be fixed in the lastest commit.
All commands are now properly tested (kerberoasting, asreproast, trusted-for-delegation, -password-not-required, admin-count, ...)

Ok I will check it in my lab :)


People animation demo exception thrown on subsequent tap

To reproduce: tap quickly more than one time on a face. An exception is thrown: "Error: Object is disposed".
The animationend callback cannot be removed on subsequent animation as the animation target was already disposed in the previous animationend callback.

The problem is that when an animation ends, the animated widget may already be disposed. We're missing a disposed check in the wrapped callback in Events.js/once.


Create Summon Transaction

Overview
On form submission the we need to trigger the summonBaalAndSafe function on the baal factory contract.
Details
See rage spec with more details:
https://hackmd.io/35DFxb31TnW2d7lIMKDu9Q
summonBaalAndSafe args

initializationParams
initializationActions
_saltNonce

initializationParams

abiCoder.encoded values:

share token name, share token symbol, lootSingleton address, sharesSingleton address, multisend address

initializationActions

encoded function calls

setAdminConfig, setGovernanceConfig, setShamans, mintShares, mintLoot, post

Reference
contract addresses:
https://github.com/HausDAO/daohaus-monorepo/wiki/Contracts
rage function:
https://github.com/HausDAO/daohaus-rage/blob/master/apps/summon/src/utils/summon.ts
rage notes/spec:
https://hackmd.io/35DFxb31TnW2d7lIMKDu9Q

NOTE that the new version of the contract has a separate shares token just like the loot token, so we will need to include the singleton of that in the initializationParams just like with loot token. Hack md updated.

contract addresses:
https://github.com/HausDAO/daohaus-monorepo/wiki/Contracts
new summoner contract/abi
https://goerli.etherscan.io/address/0x9425f47e808d9d4fE56f5F9f517CbBDd802DcdFb
poster contract to grab abi
https://goerli.etherscan.io/address/0x000000000000cd17345801aa8147b8d3950260ff

Going to add a TimePicker component to this.


Added a border search feature

This is a feature I've been using in a local version of page-ruler for a while. Thought it may make a nice addition to the tool. Turning on "border search" adds some arrows to the ruler that you can click to make the ruler expand in that direction until it detects a border. It considers a border a change in color above a threshold. There are 8 arrows (2 facing up/down, left/right in each of the 4 corners). It is handy if you are measuring parts of regions, across regions, or images.
On the code side it uses Chrome's captureVisibleTab function to take a screenshot so it can look at the pixel colors. There is some devicePixelRatio math to convert from the css pixels of the ruler to pixels on the screenshot.  For the arrows I just reused the arrow png's you already had in the project.

@wrakky Let me know if you think this would be a good addition to page-ruler. Sorry, more used to Bitbucket, wasn't sure how to add you to the PR.

It sounds like a potentially good idea! I'll give the feature a try and and review the code when I get a chance.


you forgot " " in show_number

In bufferline.vim line 48, you forgot to add a space.
Now it looks like this:
    let l:name = s:get_from_number_map(a:i + 1) . l:name
It should look like this
    let l:name = s:get_from_number_map(a:i + 1) . ' ' . l:name

Thanks. I made the separator customizable via the new setting number_separator.
This separator is used in all options of the show_number setting.


correct error in yaml frontmatter

This PR fixes a bunch of stuff. Like, a lot. Really.

Do not merge. Having an unrelated [to the docs] issue.


Initial testing of user manager

Is this how we should test managers @duvholt?
The mocked function is basically what mongodb does, so it does make sense in some way. I think.

Makes sense yeah.
But tbh I don't think we will have time to make unit tests for everything so I think it's better to make integration tests (testing of channels) instead.


Rebuild for r-base 4.4 and UCRT mingw toolchain

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

Hi @danielnachun ,
It has been a long time I am not involved in maintaining R packages on Conda Forge. I would not be relevant anymore on such PR for a major migration.
Please see with @conda-forge/r for a proper review.

Do you want to be removed as a maintainer for this package?  At the moment all pull requests will automatically ask for your review.

Sure, if there is someone to take over I will gladly leave the spot to active maintainers 🙂

All R packages are maintained the team of maintainers in @conda-forge/r so there will still be maintainers.  I'll remove your name from maintainers list in this PR so you don't get notified any more.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.
Here's what I've got...
For recipe/meta.yaml:

This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see https://github.com/conda-forge/conda-forge.github.io/issues/2102.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.


Fix duplicated values (fixes #28)

Jena's internal model doesn't treat an RDF graph as a set of triples. Instead, repeated triples (meaning triples with the same subject, predicate, and object) are represented as different Java objects, even though they are the same w.r.t. equals. It seems that Jena's internal model repeats triples for blank nodes annotated with rdf:nodeID="genid3", leading to duplicates in our LDTab output.
The proposed change fixes this issue. However, it would prevent us from round-tripping files with duplicate triples. This is not exactly desirable. I'll see whether I can come up with a better solution. At least we know where the 'bug' is located.

This is a tricky issue - I don't think there is a 'correct' way to solve this.
The RDF specification says that "[Identifiers] are not persistent or portable [...] for blank nodes. Blank node identifiers are not part of the RDF abstract syntax, but are entirely dependent on the concrete syntax or implementation."
This means we are not required to handle blank node identifiers (such as rdf:nodeID="genid3") in LDTab as far as the RDF spec is concerned. However, handling blank node identifiers is necessary if we want to offer a perfect round-trip service (without some normalization procedure). In other words, we'd need to assign blank node structures (with "datatype":"_JSON") an ID ... but this obviously goes against the design of LDTab to eliminate blank nodes where possible.
So, we have three options:

RDF as sets of triples: Accept commit f039757 as is (and drop support for persisting any duplicate triples)
RDF with duplicates: Change  f039757 to only remove duplicated triples where the subject is a blank node (so there is still support for persisting duplicated triples - but we don't offer support for persisting blank node identifiers)
Full support for blank node identifiers: introduce a meta key to persist blank node IDs when it matters.

We discussed this on a call, and tentatively agreed on 1.


Some thoughts

Will it be better to support the following format?

# Specify 443 port
echo google.com:443 | aquatone

aquatone_report.html preview add title

Thanks for your suggestions!
The google.com:443 specification would be a bit non-standard as port specification is not part of a hostname. It is however part of the URI specification, so it can be achieved by simply adding a scheme to the input like https://google.com:<port> and it should work just fine.
Adding a title to the report is a great idea! I am currently working on a refactoring to make the HTML report part of the tool better, and I will add page titles to the report data.


Summary Report and Aggregate report in JMeter s different value for Minimum response time.

Expected behavior
If we add any listeners to jmeter, we should get all values intact in every listener.
Actual behavior
I executed jmeter script via gui mode and noticed that, the min value in both the reports(Summary report & aggregate report ) is different, wears other values were same in both listeners
Steps to reproduce the problem
1.Any sample request to jmeter.
2.Add Summary report and Aggregate report listeners to jmeter.
3.Now run the test for 2-3 minute.
4.Now observe results in both listeners.
5.The min value will differ in both listeners
JMeter Version
5.6.2
Java Version
1.8.0_271
OS Version
Windows 11 enterprise 22h2

You are right. I ran the tests; min column values were all zeroes.
It occurred in case of Summary Report listener (JMeter 5.6.2). However, Version 5.5 worked fine.

Looks like a duplicate of #6043
Feel free to re-open, if you think that this is a different issue.


A BinanceAPI error has occurred. Code = -2010

Hi,
I used to make profits of up to 90% on pumps doing it manually but since using this bot I'm always getting errors. I don't get any error on tests trying out different pairs and configs. Only on the actual pumps it doesn't work. I'm pretty fast buying the pumped coin manually but I was hoping to be even faster using the bot. Missing out on all pumps during the last 2 months trying different configs. Also using the latest version always hoping the issue was fixed.
config:
"quotedCoin": "BTC",
"buyLimit": 1,
"percentOfWallet": 80,
"manualQuoted": 0.00000000,
"profitMargin": 180,
"stopLoss": 0.90,
"endpoint": "default",
cmd:
Caching all BTC pairs average prices...
This can take a while. Please, be patient...
Sucessfully cached BTC pairs!
Checking BNB balance if topup required.

(  \                             (  _\        ( )
| |) ) _   _   ___ ___   _ _      | () )   _   | ,)
| ,__/'( ) ( )/' _ _( '\    |  _ <' /'_\ | |
| |    | () || ( ) ( ) || () )   | () )( () )| |_
()    \___/'(_) (_) (_)| ,__/'   (____/'___/'`_)
| |
(_)
Investing amount for BTC: 0.0018328
Investing amount in USD: 109.08
Coin pair: VIA
A BinanceAPI error has occurred. Code = -2010
Account has insufficient balance for requested action.. Please use https://github.com/binance/binance-spot-api-docs/blob/master/errors.md to find greater details on error codes before raising an issue.
Quitting, this could take a few seconds!
Have enough BNB to cover the fees. Using just 80% of my BTC to avoid conflicts with price changes. Tried limit_buy with different values and market_buy as well. How can I have insufficient balance?
I know this error has been discussed before but I don't understand if it is a rounding issue or something else.
Also my log file remains empty. Running cmd as administrator won't let me run the bot.
Had other errors before but I guess the percentOfWallet 98 was too high and the buyLimit 1.10 too low. Now I always get insufficient balance error but as I said only during actual pumps. Non-pump is working fine.
Hope we can find a solution for this.
Thanks
crunkpinoy

Same for me. Before the pump bot works correctly. During the pump always same error when trying to buy coin
Coin pair: VIA
A BinanceAPI error has occurred. Code = -2010
Account has insufficient balance for requested action.. Please use https://github.com/binance/binance-spot-api-docs/blob/master/errors.md to find greater details on error codes before raising an issue.
Quitting, this could take a few seconds!

There has been a problem with the percentage value in calculations for a long time. I recommend setting it to 50%
( Also, let me give you some information you need to pay attention to yesterday's pump. The number of people doing VIA BTC PUMP at 20:03:15 when the pump started is 7 and the price reached 0.0007500 The number of people doing VIA BTC PUMP at 20:04:25 when the pump started is 3 and the price reached 0.0010200
first they buy and sell them. and you take it from high.
You do not earn your money easily, please be careful.
sorry i didn't take a screenshot, you could understand what i wanted to say.

Let me give an example pump image
2021-04-13 02:30:30.440000  |  ZECBTC           |  Ticks:3 |  %:0.35    |  %:0.35   | Price: 0.003735
2021-04-13 02:30:29.960000  |  ZRXBTC           |  Ticks:1 |  %:-0.14   |  %:0.14   | Price: 3.54e-05
2021-04-13 02:30:30.336000  |  ALPHAUSDT    |  Ticks:1 |  %:-0.17   |  %:0.17   | Price: 1.626
2021-04-13 02:30:31.418000  |  ZECBTC           |  Ticks:4 |  %:0.37    |  %:0.37   | Price: 0.003736
2021-04-13 02:30:32.366000  |  RAMPBUSD         |  Ticks:2 |  %:0.34    |  %:0.49   | Price: 0.8229
2021-04-13 02:30:32.409000  |  NEOUSDC          |  Ticks:1 |  %:-0.39   |  %:0.39   | Price: 64.225
2021-04-13 02:30:33.427000  |  ALPHAUSDT        |  Ticks:2 |  %:-0.03   |  %:0.30   | Price: 1.62991
2021-04-13 02:30:33.233000  |  QSPBTC           |  Ticks:1 |  %:-0.55   |  %:0.55   | Price: 1.82e-06
2021-04-13 02:30:37.385000  |  CHRBTC           |  Ticks:2 |  %:0.00    |  %:0.33   | Price: 6.15e-06
2021-04-13 02:30:39.407000  |  NEBLBTC          |  Ticks:2 |  %:-0.86   |  %:0.86   | Price: 7.664e-05
2021-04-13 02:30:38.906000  |  HOTEUR           |  Ticks:2 |  %:0.25    |  %:0.63   | Price: 0.01593
2021-04-13 02:30:42.423000  |  ZENBNB           |  Ticks:1 |  %:0.87    |  %:0.87   | Price: 0.127
2021-04-13 02:30:42.430000  |  ORNUSDT          |  Ticks:2 |  %:-0.67   |  %:0.67   | Price: 14.7885
2021-04-13 02:30:43.446000  |  CHRBTC           |  Ticks:3 |  %:-0.33   |  %:0.65   | Price: 6.12e-06
2021-04-13 02:30:43.156000  |  CHZGBP           |  Ticks:3 |  %:0.60    |  %:0.60   | Price: 0.4166
2021-04-13 02:30:43.437000  |  LINKDOWNUSDT             |  Ticks:3 |  %:0.21    |  %:0.41   | Price: 5.041751
2021-04-13 02:30:43.044000  |  CELRBTC          |  Ticks:1 |  %:0.97    |  %:0.97   | Price: 1.04e-06

@fj317 Do you have a chance to fix it as quentity = balance / coinprice, not as a percentage? then we can make the maximum amount of purchases binance is having trouble with percentage calculation here...

@fj317 Do you have a chance to fix it as quentity = balance / coinprice, not as a percentage? then we can make the maximum amount of purchases binance is having trouble with percentage calculation here...

I'm confused by what you mean here?
The code that works out the quantity is:
amountOfCoin = AmountToSell / float(averagePrice)

Where AmountToSell is the whatever the user's balance mutiplied by their percentOfWallet parameter; and averagePrice is the cached average price of the coinPair.

Thanks for the reply. 50% is actually the default config. I will try that next time. However the buylimit of 1.15 is too low. It is pumping too fast and is far above 15% until my order is placed. Obviously the coins are always pre-pumped. The VIA pump was actually suspected by some groups to be the pump coin and many bought it already days before the pump. Also some of the previous pumps were exposed. Seems the host is feeding the coins with obviously huge amounts which makes it easier to detect.
Just saw you gave it a bug label. Until it is fixed I will try the 50% size.
Thanks

crunkpinoy can you please share the groups which shared info about VIA pump ?

Yes artia I can't remember because I'm in many groups on telegram and searching for VIA gives too many results. You can just search for "binance signals" but be careful because there are also so many scammers. Besides of pumps some also provide good signals for scalping, swing trades etc. but I recommend to observe those signals first to know which channels are actually giving profitable information.

@crunkpinoy Does the Pump bot work now? We can make a 'market order' to quickly buy the coins.

@fj317 Does the Pump bot work now?

@fj317 Also will it work if we set percentOfWallet = 100 ?
Or will there be an error ?


Consider using KotlinPoet for code generation

I think writing text as a file isn't the safest solution. KotlinPoet would help you by generation correct kotlin code.

@StefMa initially I also thought of using it only, but this code generation was very simple and straightforward. So I skipped using it for initial try out.


caffe2_pybind11_state.so: undefined symbol: _ZN6caffe216TimeObserverBaseINS_12OperatorBaseEE5StartEv

Building was successful without any notable issues. However when testing it I get the following error :
python
>>> from caffe2.python import core
WARNING:root:This caffe2 python run does not have GPU support. Will run in CPU only mode.
WARNING:root:Debug message: No module named caffe2_pybind11_state_gpu
CRITICAL:root:Cannot load caffe2.python. Error: /usr/local/caffe2/python/caffe2_pybind11_state.so: undefined symbol: _ZN6caffe216TimeObserverBaseINS_12OperatorBaseEE5StartEv

I have already checked suggestions at #1543,#197 and #346 but no luck.  Any help is appreciated.
System information

Operating system: Ubuntu 16.04
python: 2.7.12
gcc: 5.4.0

The build is without GPU support, without anaconda, using MKL.

How did you install Caffe2?
Can you give me the output of
nm -A /usr/local/lib/* 2>/dev/null | grep TimeObserverBase


Does not work on Catalina / Photos 5.0

Photos 5.0  on Mac OS 10.15 / Catalina uses an entirely new database format.  osxphotos will not work with Photos 5.0.

Version 0.13.0 provides alpha support for MacOS 10.15 / Photos 5.  I'll continue testing. Let me know if you find any issues.

Photos 5 seems to be working on parity with earlier versions as of 0.14.0.


default namespacesize of 9GB does not make sense on HW-based deployment

We have left namespacesize=9GB in example deployment, which has been left there
from dev.times when we used emulated storage.
That size will result in creation of large amount of namespaces on HW-based systems with large devices.
We should put bigger value there.
Note that default is 32GB, which is improvement over 9 GB,
but may also feel too small for multiple hundreds of GB devices.
Nothe that putting a larger value than device size does not cause failure, pmem-ns-init will reduce the actual size to adjust for remaining size, i.e. with large setting we will get
one device-size namespace, which is also not bad for tester systems (with small emulated device)

@okartau maybe its time to reevaluate our design about namespaces in lvm mode, Do we really need to split the nvdimm region and merge back with LVM?. Instead, how about creating a single namespace(per namespace mode) with the size of the region. This simplifies namespace creation logic and even speeds-up driver startup time on Nodes, i feel.

I agree, let's go to single namespace.
The idea behind multiple namespaces was to make the potentially failing unit smaller, also to leave possibility for manual fixes and adjustments in smaller scale (for example, possibility to detach or add device slices in smaller sets).
In production case, none of that has real value, right. We don't expect admin to configure single namespaces and PVolumes. It's actually the opposite, creation of multiple objects adds risk of inconsistency.
There is another way to partition in LVM mode by setting "use for" ratios, and creating one more level by slicing space to many pre-allocated namespaces, is unneeded complexity.
I will prepare a PR replacing many namespaces during pre-allocating with single namespace. It will simplify the code.


Not found for existing package

Hi,
For some reasons, it seems that I cannot add my package on Godoc. Here is my package on GitHub: https://github.com/AntoineAugusti/moduluschecking
And the corresponding link on Godoc shows the 404 page: https://godoc.org/github.com/AntoineAugusti/moduluschecking
Any help would be really appreciated!

It just appeared after a good 30 minutes...

@AntoineAugusti Actually this was just ninja me ;)
There's no .go files in the top directory of your package that's why it was responding with 404.
What I did is to navigate on godoc.org to a directory of your package that contains .go files, navigate back to its top directory and refresh it. Not sure if it's desirable ux or a workaround.

@rjeczalik Ah ah, thanks for the ninja fix :+1: Seems like a workaround for me.
You raise another interesting question: how can I add a short sentence to the root of the directory if I don't have any go files? Is it even possible?


🎉 2.0.2

ℹ About this release

Version: 2.0.2
Type: patch
Last Release: 2.0.1 (10/8/2024, 4:35:09 AM) [?]
Commits to merge: 6 [?]

📦 Dependencies

Update jsr from ^0.13.1 to ^0.13.2

📦 Development Dependencies

Update @eslint/js from ^9.9.0 to ^9.13.0
Update @types/mocha from ^10.0.7 to ^10.0.9
Update @types/node from ^22.5.0 to ^22.9.0
Update eslint from ^9.9.0 to ^9.13.0
Update mocha from ^10.7.3 to ^10.8.2
Update tsup from ^8.1.0 to ^8.3.5
Update tsx from ^4.17.0 to ^4.19.2
Update typedoc from ^0.26.6 to ^0.26.11
Update typescript from ^5.5.4 to ^5.6.3
Update typescript-eslint from ^8.2.0 to ^8.8.1

:tada: This PR is included in version 2.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release
v2.0.2

Your semantic-release bot :package::rocket:


Conflict with OBS

It seems the unlocker is conflicted with the Game Capture source of OBS. Every time I use the unlocker, Game Capture will only show a black screen

It shouldn't, is your obs running as admin

That sounds like a conflict with another overlay software, fps unlocker has nothing to mess with screen capture functionalities

That sounds like a conflict with another overlay software, fps unlocker has nothing to mess with screen capture functionalities

Yeah it seems to work now. Will have to be more careful with performance overlay I guess


Added documentation for stackengine as a backend

Great work with confd! It's super useful, and easy to use.
I've added the necessary documentation on how to use stackengine as a backend into the various documenation files. I'm pretty sure I've updated all the required files, but if I missed something, let me know!
Thanks.

Hi @kelseyhightower can this be merged please?

@karthequian Rebase and then I can merge.

Updated @kelseyhightower; thanks!


When will configBuilders be added to the schema as a valid app settings attribute?

I'm trying to precompile an application for use with WebDeploy and it's throwing errors due to it not being part of the schema.

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

ID: ea24ffb0-1e4a-4c73-c566-18b67e3bd69c
Version Independent ID: 1d1c4a41-9dfd-82f9-ed0c-993c45b16b25
Content: <appSettings> element for <configuration>
Content Source: docs/framework/configure-apps/file-schema/appsettings/appsettings-element-for-configuration.md
Product: dotnet-framework
GitHub Login: @guardrex
Microsoft Alias: mairaw

Thanks @GingerSnap-xx. @csharpfritz is this something you can help with?

I too am interested in how that works. If I have two builders (User Settings for local dev and Azure Key Vault for production) do I give them both separate names and specify them both in the configBuilders attribute? If I specify both what delimiter should I use? Does it matter what order they are specified in? Does that even work or do I need to use a different config file in production so I specify a different builder?


Create a receiver for testing

Description
Create a new receiver that can be used for testing purposes. Maybe it contains some baked in payloads so api calls don't actually have to be made. It could also have an interface for developers to provide their own payloads that get sent to bolt listeners.
What type of issue is this? (place an x in one of the [ ])

[x] enhancement (feature request)

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Related issue: #638

We could consider bringing this up in the discussion in #638 as an option, but I feel like the receiver itself contains code that would need testing, too. So, replacing the receiver could potentially yield different app code, which would reduce the integrity of any testing.
Going to close this but we can re-consider this once the focus is put on addressing first-class testing within bolt (#638).


CONTRIBUTING.md updated

#58 issue solved and updated the CONTRIBUTING.md as provided in README.md. For preview check forked CONTRIBUTING.md...

@all-contributors please add @Muhammed-Rahif and @eltociear  for data and content


UseErrorPage null refs for specific TagHelper use-case resulting in no error page.

Original issue that exposed this: https://github.com/aspnet/Mvc/issues/2710. To reproduce this problem, follow the steps mentioned in the Mvc issue.
I debugged through it a bit and found that frame.ContextCode was null at the following line: https://github.com/aspnet/Diagnostics/blob/791ec1a0161d608265e155655c029bd4f2e08bf3/src/Microsoft.AspNet.Diagnostics/Views/ErrorPage.cshtml#L100.

commit 191ffe17219405c6c7c9607c20ba6dd6fbdeecde


Implement DISCARD_STMT new version of pg_query

The DISCARD_STMT constant is only available in master. Let's implement this when there is a new version of pg_query.
See https://github.com/lfittl/pg_query/blob/master/lib/pg_query/node_types.rb#L38

Whoops 😅, wrong repo 🙈

https://github.com/mvgijssel/arel_toolkit/issues/55


MLJModelInterface 1.3.5 has broken MLJModels

It seems MLJModelInterface 1.3.5 has broken MLJModels:
@OkonSamuel
julia> X, y = @load_boston;

julia> models(matching(X, y))
WARNING: both ScientificTypes and MLJModelInterface export "scitype"; uses of it in module MLJModels must be qualified
ERROR: UndefVarError: scitype not defined
Stacktrace:
 [1] matching(X::NamedTuple{(:Crim, :Zn, :Indus, :NOx, :Rm, :Age, :Dis, :Rad, :Tax, :PTRatio, :Black, :LStat), NTuple{12, SubArray{Float64, 1, Matrix{Float64}, Tuple{Base.Slice{Base.OneTo{Int64}}, Int64}, true}}}, y::SubArray{Float64, 1, Matrix{Float64}, Tuple{Base.Slice{Base.OneTo{Int64}}, Int64}, true})
   @ MLJModels ~/.julia/packages/MLJModels/fsSbS/src/model_search.jl:198
 [2] top-level scope
   @ REPL[10]:1

It seems this an issue for any package that simultaneously does using MLJModelInterface and using ScientificTypes. Note MLJModels cannot do ScientificTypes -> ScientificTypesBase because it needs the coerce function.

I've made a fix for MLJModels at #424.
However, on reflection, I think the lesser of two evils would be to be yank MLJModelInterface 1.3.5, MLJBase 0.19.2 and issue a patch for MLJFlux, the package broken by MLJModelInterface 1.3.4. The rationals are:

Backwards compatability of MLJModels is more important that backwards compatibility of MLJFlux
MLJModelInterface 1.3.4 -> 1.3.5 is really a backwards step in the general plan of exporting less from MLJModelInterface (https://github.com/JuliaAI/MLJModelInterface.jl/issues/132).

@OkonSamuel Thoughts?

I've made a fix for MLJModels at #424. You can see this is a bit awkward.
However, on reflection, I think the lesser of two evils would be to be yank MLJModelInterface 1.3.5, MLJBase 0.19.2 and issue a patch for MLJFlux, the package broken by MLJModelInterface 1.3.4. The rationals are:

Backwards compatability of MLJModels is more important that backwards compatibility of MLJFlux
MLJModelInterface 1.3.4 -> 1.3.5 is really a backwards step in the general plan of exporting less from MLJModelInterface (Perhaps MLJModelInteface should not export any method in the future MLJModelInterface.jl#132).

@OkonSamuel Thoughts?

I agree with you on this. We shouldn't export the scitype method from MLJModelInterface. But we should still leave the newly added scitype method there.

But we should still leave the newly added scitype method there.

👍🏾

Actually, backwards compatibility of MLJModels is less of an issue as we just tagged a breaking version, which can be yanked. So, after further investigation and off-line discussion @OkonSamuel  and I are recommending merging the fix #424 after all.