option to allow calling RGeo "unsafe_" methods

I had some shapefiles that were throwing RGeo::Error::InvalidGeometry errors on polygons that seem to be valid (PostGIS accepts them in a geometry column and they can be imported using the shp2pgsql successfully and visualized on a map).
rgeo has some unsafe_* variants of methods available (like unsafe_within? instead of within?) mentioned here:
https://github.com/rgeo/rgeo/blob/main/NEWS.md#validity-handling
This PR adds an allow_unsafe_methods option to the RGeo::Shapefile::Reader#open method that accepts a list of acceptable unsafe_* methods to call.  I implemented the option and support for just the :within method since that's all that was needed to fix the issue with my specific shapefile polygons, but it could be expanded to the other spatial methods as needed.
RGeo::Shapefile::Reader.open(file, allow_unsafe_methods: :within) do |shapefile|
   # ...
end

also supports array-style value for the option:
RGeo::Shapefile::Reader.open(file, allow_unsafe_methods: [:within]) do |shapefile|
   # ...
end

Hi @ksouthworth thanks for the contribution I think this is a great feature to add. I'm curious how hard it would be to extend this for all unsafe methods out of the box and just make this something like allow_unsafe_methods: true. Quickly going through it seems like there's just 2 instances of within? and 1 of contains?. So instead of adding a rescue and then unsafe call we could do something like this:
within_method = @opts_[:allow_unsafe_methods] ? :unsafe_within? : :within?
if first_try_ >= 0 && part_data_[2].public_send(within_method, polygons_[first_try_].first[2])

or even
if first_try_ >= 0 && part_data_[2].public_send(@opts_[:allow_unsafe_methods] ? :unsafe_within? : :within?, polygons_[first_try_].first[2])

if we want to 1-line it.
What do you think?

I definitely like the 1-line, I wasn't a big fan (stylistically) of my begin/rescue style, but I did it that way because I'm not familiar with the internals of those rgeo methods like within to know if directly calling unsafe_within instead of within would yield different results for valid geometry?
So I opted to always try the "correct" version of the method first (e.g. within?) and then only call the unsafe_within? as a fallback.  I wasn't sure if calling unsafe_within? skips some important stuff or not?  I guess I should go read the internals of the rgeo gem to get a firm answer...

Definitely understandable. It's a reasonable assumption to make that they might behave differently.
Here's the source for the validity checking modifications.
https://github.com/rgeo/rgeo/blob/c70baceb7abd4803f137c73e295005c2bfd23740/lib/rgeo/impl_helper/validity_check.rb#L69-L96
It involves a bit of meta programming, but it basically takes the implementations that we write, and for the normal version, adds a validity check at the beginning and makes the unsafe_ variation the original implementation that's found in the package.
It's a little contrived if you're unfamiliar with the codebase, but makes it easy to add new methods without worrying about adding a validity check at the beginning.
In short, no there's no difference in behavior between the 2 versions. Let me know if you need any more clarification.

I have updated the code to use the 1-liner and renamed the option, and updated the README as well.
I suppose the option could just be named unsafe_methods: true now that I think about it

@ksouthworth sorry about the delay here. I think naming it unsafe_methods makes sense.
Thinking about it more, there are 2 things we should work out before it's ready to be merged

This gem is compatible with older versions of RGeo where unsafe_* methods do not exist, so we should probably handle that somehow. We can check if unsafe methods exist, do a version check of RGeo, or make a new major release that is only compatible with RGeo 3.0+. @BuonOmo what are your thoughts on this?

We should add a test that ensure the option works. How hard would it be to generate test data that this works for? If it's really difficult we can just test that it accepts the option in the instance and properly sets the instance variable.

@keithdoggett I think I'd restrain bumping a major for this, but rather do something like this (pseudocode):
@allow_unsafe = false
if opts_[:allow_unsafe_methods]
  if rgeo_version_too_low
    warn "ignored"
  else
    @allow_unsafe = opts_[:allow_unsafe_methods]
  end
end

And remove this message in next major (we'd have to note it somewhere for sure). WDYT?

Thinking again, if you have time to publish a major, it's also fine by me

@BuonOmo yeah I think that makes more sense actually. ideally we don't have a bunch of version checking but I think it's fine for this one case

Hello all! I have a vested interest in this being merged - Canadian CSDs appear to be raising RGeo::Error::InvalidGeometry when downloaded directly from the Census website. I can safely ignore these records so this is the perfect solution for me. Using this forked branch as the gem source works for me but it's not up to par with our security standards.
All of that said, I'm happy to contribute wherever I can. Unfortunately, I'm not super clear on the next steps forward so any guidance there would be great. Thanks in advance!

Hi @ObiWanKeoni I'm not sure that you can push on an already existing branch from someone else. I'd be ok with another PR if that isn't possible though.
The steps left to me are:

read and reply to review
add the test to ensure this option is working
add the warning message if rgeo version is not compatible

I think that without previous knowledge or rgeo's internal this might be up to 1 working day at most depending on your seniority 🙂.


[IDE] Fix ModelASTWalker passing syntax nodes before the corresponding AST nodes have been visited

This was causing the tokens comprising image literals to be output separately, rather than as a single object literal.
Resolves rdar://problem/55045797

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 888529cf97827d09bca13b6595e8663bfd7615cb

@swift-ci please test OS X Platform


Implement logging

What this PR does / why we need it:
Implements logging for redirects and incoming requests
Which issue this PR fixes (optional - uncomment and add issue):
fixes #37
Special notes for your reviewer:
We need to talk about what we want to log and what informations we need to include in logs. Now, it only logs the incoming requests and redirects URL.

I think each log line needs to be self contained or else you can't see which redirect was done by which request.
So something along the lines of <timestamp> [txtdirect]: requestURL > 302 > redirectedURL

LGTM

@dbriesz can take another look and then happy to merge.


Step 11 Grid Update

What (if anything) did you refactor?

Placed cell phone input within the same grid as email so they're aligned.

Any other comments, questions, or concerns?

Subheader font defaulting to serif here. Issue fixed in another PR. Line height for subheader is also too large here.

@sydney-devine can this be merged?

@sydney-devine can this be merged?

Yup!


Github discussions on https://langfuse.com/docs/prompts/get-started breaks in mobile view

Github discussions on https://langfuse.com/docs/prompts/get-started breaks in mobile view.

thanks for sharing, I think wrapping this correctly would be preferred. Are you interested in contributing to this?

fixed in https://github.com/langfuse/langfuse-docs/pull/887


fix some funky looking indents

there is more, but this is a start
they always look out of place with the normal indentation and have to change all lines when the first line changes,
so standardize on 2-space indent 🤷

OK 👍


Preparing for napalm-base>=0.18.0 and release 0.4.2

<!-- Make sure you have read http://napalm.readthedocs.io/en/latest/contributing/index.html --!>

Coverage increased (+0.08%) to 90.947% when pulling 5c17fb0e0440bc7072e02bc4673ed126fe6e6262 on mirceaulinic:NB0.18.0-COMAPT into 0bf04a12ff1e18aeb477f223ba40dc5bc9009345 on napalm-automation:develop.

+1


Notification messages do not close in IE11

Messages no longer close in IE11 either after a timeout or when clicking the close button. They just persist indefinitely.
I suspect this changed when jQuery was removed, as I see at least one replacement that isn't supported by IE.
For example, using the matches selector is not supported by IE11 without prefixing (see this caniuse entry)

The cause is IE not having Element.matches but Element.msMatchesSelector:
https://github.com/aexmachina/ember-notify/blob/master/addon/components/ember-notify/message.js#L65

@btecu Is there a way to polyfill matches for ember-notify? I'd be happy to open a pr, but I'm not sure how to go about it. Otherwise we're going to be stuck on ember-notify 5.2.1, which is using a deprecated version of babel.

@bryanhickerson You actually don't need to polyfill matches because IE 11 already supports it, it just has a different name.
Somewhere in your application:
if (!Element.prototype.matches) {
  Element.prototype.matches = Element.prototype.msMatchesSelector;
}

@btecu Ah, thanks. It seems like that should live in ember-notify. I'll open PR with that change.


bump log4j 2.15.0

To bump log4j 2.15.0 for CVE-2021-44228

2.16 was just released as well.   In my local storm install I manually updated to 2.16 but get an error with the lmax Distruper. ( admittedly this is an older 1.x series so that may have been updated ).

hi @talios thanks, I just verified 1.0.x branch with log4j 2.15.0 + disruptor 3.4.4. The log4j 2.16.0 still WIP.
https://github.com/apache/storm/pull/3426

@lukess We updated up our 1.0.x distro with 2.16 and disrupter 3.4.4 shortly after I made that comment, and it seems to be working fine.
Looks like 2.16 just removes all the message lookups and disabled JNDI by default.

Hello,
For whoever who might run still run in production with Apache Storm 1.2.3:
I just replaced existing log4j JAR files with their 2.16.0 version (not
event bothering to keep same file names) and restarted everything
=> everything works fine !
(for our own topologies, we were relying on SLF4J API for logging, so we
had nothing to change there...)
Alexandre
Le mar. 14 déc. 2021 à 11:54, Mark Derricutt @.***> a
écrit :

@lukess https://github.com/lukess We updated up our 1.0.x distro with
2.16 and disrupter 3.4.4 shortly after I made that comment, and it seems to
be working fine.
Looks like 2.16 just removes all the message lookups and disabled JNDI by
default.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/storm/pull/3425#issuecomment-993418345, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEIJEMMFPOUBF42YS3UAQQTUQ4O4PANCNFSM5J5QVLSQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

It would be good to release maintenance version for 2.3/2.2/1.x branches.

Can you open a storm JIRA and add it to the commit message and I will merge this.

thanks we have tested 1.16


Change schema and seed script

Added a records.csv.sample too.
closes #10 and #8

This works amazing @damianmarti !! great job
Thank you very much. I added some little tweaks.
I'll import the need schema/data to the live database in a bit.


YAML editor renamed to CAMP editor

Replacing the name for the text editor exposes more clear the standard used instead the language language used to write the blueprint. This opens more clearly to add support to other standards

Feel free to merge after the build passes @jcabrerizo


Remove auto category

Now that YNAB have payee management with auto categorising, i think we can get rid of all our logic:
http://docs.youneedabudget.com/article/611-payee-management

It depends how they do it in the web app. If the logic is on the client then send payee/categories to the api, then we still need to do the logic. But we might have some luck (like, push a transaction with a given payee, and get a return with an automatic category), but I wouldnt bet on it :-/

I suspect it needs to be server side as if it didn't work with auto
imports, people would be annoyed. Will test.
On 20 Jul 2017 03:35, "rienafairefr"<EMAIL_ADDRESS>wrote:
It depends how they do it in the web app. If the logic is on the client
then send payee/categories to the api, then we still need to do the logic.
But we might have some luck (like, push a transaction with a given payee,
and get a return with an automatic category), but I wouldnt bet on it :-/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/scottrobertson/fintech-to-ynab/issues/36#issuecomment-316665005,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAELCbRtTHPWY3VDEsxOmhQUE_HiiLGSks5sPy2MgaJpZM4OcFPU
.

This can now be removed once YNAB support this in the new API. This should be done by next week.

This issue notified me about some changes and the YNAB API is live, I hadnt seen it before. I see they provide a swagger spec, it's super great, that'll permit generation of a client library in Python in a matter of days :-) 👍

Yeah it's pretty great. Private beta for now, but it should be available to everyone soon :)

This is now handled by YNAB via the API.


year in publication

Hi, I've successfully imported my publications from bib but I can't see the year in the publication section. Only if I click in one I can see the full details including the date. Is it possible to add the date in the full list? Thanks

Refer to the docs such as https://sourcethemes.com/academic/docs/managing-content/#manage-archive-pages


Fix area:highway rendering of alleys, parking aisles, and other subclasses of highway=service

I am not entirely sure if this is the correct way to tag the area of an alley (or any other area:highway=service & service=* combination), but iD seems to render the area incorrectly.
To fix, change the code that renders the service=alley, driveway, etc to only render if highway=service is also present on the element.

hmm.. I'm also not sure if that is the correct way to tag it.
I would do highway=service + service=alley on a line down the center of the alley.  This part is required.  People really shouldn't map highways as areas and expect routers to work.
Then a separate polygon tagged area:highway=yes for the area of pavement.  iD has a preset for this called "Road Surface".  This part is very much optional, and really only people who want to micromap do it.

In the image above, the correctly added alleys are hidden, since only landuse is enabled.

In the image above, the correctly added alleys are hidden, since only landuse is enabled.

oh good!  I will try to fix the rendering so that only linear service=alley get the thick yellowish style.


Add information about Office Online

In the following Note, could you add more information about users using services in Office such as Excel Online or Word Online. Our users seem to be logged out while editing documents hosted from OneDrive and SharePoint locations. The expectation is that they should be able to remain signed in but are not. They are actively working on documents and get kicked out by our time out.
Note
If a user is active in another Microsoft 365 service (such as Outlook), but inactive in SharePoint and OneDrive, they are signed out across Microsoft 365. If a user has multiple tabs to OneDrive and SharePoint sites open at the same time, they won't be signed out unless they are inactive on all the sites. > Users won't be signed out if they selected to stay signed in when they signed in. ...

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

ID: cfaf9fb8-afec-06b3-ed85-244a7af5b6dd
Version Independent ID: 016c6f7d-8fd1-ba7f-ab54-a0ef1d34d026
Content: Sign out inactive users - SharePoint in Microsoft 365
Content Source: SharePoint/SharePointOnline/sign-out-inactive-users.md
Service: sharepoint-online
GitHub Login: @kaarins
Microsoft Alias: kaarins

@pagejustin Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hello @pagejustin Justin, how are you?
I tested this, however, I could not reproduce it, in case we need to adjust the documentation, can you detail browser used?
Thank you

@scanum please close.


How to fine tune the pre-trained model on Apple MPS?

I don't see any document regarding my question.
Could you please give me some hint?

RWKV training is using a CUDA kernel so I wonder if it can be accelerated on Apple chips


Includes need to be handled recursively

On the call with @ian-harshman-ck, I realized that include syntax was only being handled for the top-level file.  This needs to be handled recursively for all includes.

This is being handled now.


CI: "Auto commit expectations" is broken in WPT workflow

https://github.com/GoogleChromeLabs/chromium-bidi/blob/667186af58104e502db41703c8d26bb17dcfabc5/.github/workflows/wpt.yml#L22
...was added as a convenience CI workflow to update WPT expectations via Github Actions, without the need of fully checking out a repository locally. However, it is broken, effectively acting a no-op. Nothing is committed. We should either: investigate why it's broken (and fix it), or remove that functionality to avoid confusion.
cc @OrKoN FYI
Priority: Low

Possibly related: https://github.com/GoogleChromeLabs/chromium-bidi/issues/1266

Fixed via https://github.com/GoogleChromeLabs/chromium-bidi/commit/8caa15ea910e850afaeb5f3c9b4b944191817597
So happy to see you figured out the issue, and that it was just an artifact name mismatch! This was a mystery for months. Closing.


Feature1 -Merge conflict resolved code

PR to merge feature branch changes(after resolving merge conflict) to develop branch

Merging feature branch(resolving merge conflict) change to develop branch


Labels in the Example Logistic Regression

Hey! Thanks a lot for sharing your code. I am not sure, but I was going through the simple logistic regression example and I think the code generates labels in {0,1}:
https://github.com/trevorcampbell/bayesian-coresets/blob/0480ae467ab5f340726b18377a8818080d23a6bf/examples/simple_logistic_regression/main.py#L25
which I don't think work in this form of logistic regression, instead of using labels in {-1,1} (as it is actually specified in your paper). Is it so, or did I miss something? Thanks again!

You're totally right. Thanks for pointing that out. I'll fix that now!


How to get descriptions from videos?

Question
Which api call will get me the descriptions for the videos found underneath the videos while they are being played?
Calling getBasicInfo(id,'WEB') I found VideoInfo.basic_info.short_description, but that does not seem to be it.
Any ideas?
Other details

Checklist

[X] I am running the latest version.
[X] I checked the documentation and found no answer.
[X] I have searched the existing issues and made sure this is not a duplicate.
[X] I have provided sufficient information.

Try video.getInfo(), this is a little slower but gives more information than getBasicInfo(). Also, specifying the Web client isn't needed since that's the default.

Ahh that does it thank you!


Inverted error in the convert function implementation

The output is different from the expected output.
Output is the inverse of the input.

The url to the problematic code https://github.com/Csasaka19/CS50/tree/main/Week_3/atoi

I was processing the string from left to right .The instructions required processing from right to left, that is beginning from the null character('/0') back.


Credentials question

When I run the Android app from this page it's requiring me to hard code an account id and account key for my Azure sharing service of this same page. I don't see any such credentials by these names for my service?

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

ID: cb0af698-4a74-9098-691f-ecbbb0419398
Version Independent ID: d5fe9b9e-c802-423d-ac8e-dba87fa8766e
Content: Tutorial: Share anchors across sessions and devices - Azure Spatial Anchors
Content Source: articles/spatial-anchors/tutorials/tutorial-share-anchors-across-devices.md
Service: azure-spatial-anchors
GitHub Login: @RamonArguelles
Microsoft Alias: rgarcia

@kcovert Thanks for the question! We're investigating this and will get back to you shortly.

Hey @kcovert. Those values can be found in the section above as you setup your Azure Spatial Anchors Resource in the Azure Portal. See the section on the page here.

Thanks for the quick response Craig. Kind of explains why I can’t find it as my screen for my sharing service has different info on it. No Account ID, etc…
<EMAIL_ADDRESS>I’m missing something here or not understanding,
Kirk
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Craig<EMAIL_ADDRESS>Sent: Thursday, March 26, 2020 11:29 AM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Credentials question (#50927)
Hey @kcoverthttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkcovert&data=02|01||c2714513109243c48aa908d7d19a87f0|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637208333938057394&sdata=x%2FsJXuuLWdU189B8v5FOTtV3zSRdwU4SEPfSyrzuDtQ%3D&reserved=0. Those values can be found in the section above as you setup your Azure Spatial Anchors Resource in the Azure Portal. See the section on the page herehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fspatial-anchors%2Ftutorials%2Ftutorial-share-anchors-across-devices%3Ftabs%3DVS%252CAndroid%23create-a-spatial-anchors-resource&data=02|01||c2714513109243c48aa908d7d19a87f0|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637208333938057394&sdata=MQOHZvIK1ctzsXhF1CS6cb1jZSnLouSLoCeAC9%2FEMZU%3D&reserved=0.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F50927%23issuecomment-604496643&data=02|01||c2714513109243c48aa908d7d19a87f0|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637208333938067389&sdata=peVuFoHC78RY4rM0WYdB4DYoKxn1r29AshEK8u5UMdw%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAMDUQIP2PW3TFPYXPMT5CLRJNYHBANCNFSM4LTWB3DQ&data=02|01||c2714513109243c48aa908d7d19a87f0|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637208333938077381&sdata=qi5PFD7yXWd2v8eRBzWDmMTehDRV7I7Zn5IbJEs5f6c%3D&reserved=0.

Hmmmm...it looks like you attempted to send a screenshot, but I can't see it.
Everything looks ok on my side. Things are where they should be. The only difference I see is that the "Keys" menu item is now called "Access Keys". Since you're doing the sharing tutorial, make sure you're looking at the Azure Spatial Anchors Resource in the Azure Portal instead of the Azure App Service where you deploy the Asp.NET Core app for the account access keys.

Attached picture this time. Still looking around to try and find Account ID. I don’t think this would be my kcovert56<EMAIL_ADDRESS>account ID. That would be bad if I had to embed my Azure credentials in my app.
From: Craig Treasure<EMAIL_ADDRESS>Sent: Thursday, March 26, 2020 11:50 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: kcovert<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Credentials question (#50927)
Hmmmm...it looks like you attempted to send a screenshot, but I can't see it.
Everything looks ok on my side. Things are where they should be. The only difference I see is that the "Keys" menu item is now called "Access Keys". Since you're doing the sharing tutorial, make sure you're looking at the Azure Spatial Anchors Resource in the Azure Portal instead of the Azure App Service where you deploy the Asp.NET Core app for the account access keys.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F50927%23issuecomment-604508578&data=02|01||c72bd5bf183d45b8050d08d7d19d4b8f|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637208345810483702&sdata=9fQmvjP0oehSfCPq2qVdcB%2FxRLqttVzOCrs8XOH2MBQ%3D&reserved=0, or unsubscribehttps://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAMDUQM4TPVI6BKHAZK5TMTRJN2RHANCNFSM4LTWB3DQ&data=02|01||c72bd5bf183d45b8050d08d7d19d4b8f|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637208345810493696&sdata=J5nWv4Z8e3QLIW2NduliOL3HzkKUV0Co6iQ1kj%2FIg6U%3D&reserved=0.

It looks like you're replying from emails and it appears that images don't come through that way.

Must be virus filtering on your Exchange server. The attached is an attempt to spoof it. You will need to change the file extension back to .png.  If that doesn’t work you can see the picture from m OneDrive here  https://1drv.ms/u/s!Aow_OnBrOlnk1dNpTGoIWWf1xXDZEA?e=2zcp2V
From: Craig Treasure<EMAIL_ADDRESS>Sent: Thursday, March 26, 2020 12:11 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: kcovert<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Credentials question (#50927)
It looks like you're replying from emails and it appears that images don't come through that way.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F50927%23issuecomment-604521244&data=02|01||3b5571fbdd1d4d5e06f908d7d1a05699|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637208358878019127&sdata=Ue8MZP2g12HErimD66NcU%2BunX6v5vfkLOsW70bdVOmU%3D&reserved=0, or unsubscribehttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAMDUQMEJYGMQUWBX67BALTRJN5CZANCNFSM4LTWB3DQ&data=02|01||3b5571fbdd1d4d5e06f908d7d1a05699|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637208358878029135&sdata=OoEIq5IhwIhATziWrfUwUR%2BoV1buGtMbvCLK6gyUQkA%3D&reserved=0.

Your email replies are relayed through GitHub. They don't go directly to others through email.
I was able to see the screenshot on OneDrive. It is as I thought. You are looking at the Azure App Service where you publish your Asp.NET Core application. You need to look instead at the Azure Spatial Anchors resource in the Azure Portal. Please follow the instruction here to create an Azure Spatial Anchors account resource.

That’s what I was missing, found them now, thanks Craig. I been working off this page https://docs.microsoft.com/en-us/azure/spatial-anchors/tutorials/tutorial-share-anchors-across-devices?tabs=VS%2CAndroid#download-the-sample-project
From: Craig Treasure<EMAIL_ADDRESS>Sent: Thursday, March 26, 2020 12:30 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: kcovert<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Credentials question (#50927)
Your email replies are relayed through GitHub. They don't go directly to others through email.
I was able to see the screenshot on OneDrive. It is as I thought. You are looking at the Azure App Service where you publish your Asp.NET Core application. You need to look instead at the Azure Spatial Anchors resource in the Azure Portal. Please follow the instruction herehttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fspatial-anchors%2Ftutorials%2Ftutorial-share-anchors-across-devices%3Ftabs%3DVS%252CAndroid%23create-a-spatial-anchors-resource&data=02|01||f9a45c5080984f41b3bd08d7d1a2f692|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637208370164325087&sdata=RqV2Z09wOzlSU6OpgDEUlhOJLuBGZd%2FTSnFagZYVVEo%3D&reserved=0 to create an Azure Spatial Anchors account resource.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F50927%23issuecomment-604531652&data=02|01||f9a45c5080984f41b3bd08d7d1a2f692|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637208370164335085&sdata=jHf%2BBJXM8WPRkiepPtmT8Ro9ZFAXkou%2BUMsJOC5Tvs8%3D&reserved=0, or unsubscribehttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAMDUQMQ3732TXSPCXUJJDTRJN7JLANCNFSM4LTWB3DQ&data=02|01||f9a45c5080984f41b3bd08d7d1a2f692|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637208370164335085&sdata=HNIO6beBgKpPzHz632b8ekEA4MuvBIHQEe%2F3WpOVTbM%3D&reserved=0.

@BhargaviAnnadevara-MSFT, this issue has been resolved and can now be closed.

Yes it may be closed and thanks again,
Kirk
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Craig Treasure<EMAIL_ADDRESS>Sent: Thursday, March 26, 2020 12:44:40 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: kcovert<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Credentials question (#50927)
@BhargaviAnnadevara-MSFThttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FBhargaviAnnadevara-MSFT&data=02|01||08d7c6f43e3a4733beb708d7d1a4faf2|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637208378816262856&sdata=RxcIPhoa1xEklOHkOiPR6SwQL0Rzbd2lFQjc%2FZNsZ0I%3D&reserved=0, this issue has been resolved and can now be closed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F50927%23issuecomment-604539855&data=02|01||08d7c6f43e3a4733beb708d7d1a4faf2|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637208378816272860&sdata=CApQI7JHBQWKRmSahVkciYHrIfjmRAlfJhDBreQPHxg%3D&reserved=0, or unsubscribehttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAMDUQN4LIBGU3ENL4VAJQDRJOA7RANCNFSM4LTWB3DQ&data=02|01||08d7c6f43e3a4733beb708d7d1a4faf2|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637208378816272860&sdata=1lwKPmuVRcvNFcoNSfyKZ%2FHZ91pa46o8W25iAE0j258%3D&reserved=0.

@kcovert Thanks for the confirmation.
@craigktreasure Thanks for the quick resolution.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


orbit_controls There is a bug

When using OrthographicCamera and maxPolarAngle is 0, it cannot be rotated after moving.

Hi @leesser,
I tried to replicate your issue on mac, ios, and web, but was not able to not get the desired result. Could you please provide what platform you are using.
Also please check out this example I have updated to see if this has the same issue.
Sorry for the inconvenience.


Results in object object

This is my markdown file

This is the resulting html file

The script part is aware of my .md file content.

Ah, there are breaking changes in the latest version of markmap-lib.

fixed in 90fddc14

You may need to run :CocUpdate to force update to the latest version.


[BUG]

Describe the bug
Unable to create source_response_list for twitter
Expected behavior
Want to fetch tweets and all metadata in source_response_list
Stacktrace
09/28/2021 02:01:41 - ERROR - searchtweets.result_stream -   Rate limit hit... Will retry...
09/28/2021 02:01:41 - ERROR - searchtweets.result_stream -   Will retry in 36 seconds...
09/28/2021 02:02:17 - ERROR - searchtweets.result_stream -    HTTP Error code: 429: Rate limit exceeded
| Too Many Requests
Please complete the following information:

OS: Windows
Version: 10

Additional context
Add any other context about the problem here.

@sumitkumar2000 Twitter recently changed their message format which caused this issue. I am trying to fix this, but due to my twitter API monthly limit unable to test the changes out. Can you please test changed from this PR https://github.com/obsei/obsei/pull/198


Fix SearchAfter usage

What changed?
Passing multiple values to searchAfter instead of a single slice

Why?
Previous usage of this function resulted in malformed ElasticSearch query

How did you test it?
Updated unit test

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 01887b55-1bed-4dca-8bc2-51c3711b3d5b

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
103 unchanged lines in 15 files lost coverage.
Overall coverage decreased (-0.01%) to 57.266%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

common/elasticsearch/client.go
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

common/cache/lru.go
2
92.2%

common/persistence/executionManager.go
2
78.94%

common/task/weightedRoundRobinTaskScheduler.go
2
89.64%

service/frontend/workflowHandler.go
2
60.35%

service/history/task/transfer_standby_task_executor.go
2
87.34%

service/matching/matcher.go
2
90.29%

common/persistence/nosql/nosqlplugin/cassandra/workflow.go
3
59.55%

service/history/task/fetcher.go
4
91.24%

common/persistence/statsComputer.go
5
94.64%

common/task/fifoTaskScheduler.go
5
84.54%

Totals

Change from base Build 01886f46-77ea-4306-8d9c-5f71c79fbe8a:
-0.01%

Covered Lines:
87022

Relevant Lines:
151962

💛  - Coveralls


Some problems about the use of postcss-cssnext

⚠ IMPORTANT ⚠ Please check the following list before proceeding. If you ignore this issue template, your issue will be directly closed.

[x] Read the docs.
[x] Use Vite >=2.0. (1.x is no longer supported)
[x] If the issue is related to 1.x -> 2.0 upgrade, read the Migration Guide first.

Describe the bug
When I use the postcss-cssnext, I defined a theme.css In the assets directory and I import it in the main.js.
I can use it elsewhere theme.css Variables in, but the command line window will prompt that the variable cannot be found.

Reproduction
Please provide a link to a repo that can reproduce the problem you ran into.
A reproduction is required unless you are absolutely sure that the the problem is obvious and the information you provided is enough for us to understand what the problem is. If a report has only vague description (e.g. just a generic error message) and has no reproduction, it will be closed immediately.
System Info

vite version:2.0.0-beta.12
Operating System: windows10
Node version: v14.15.4
Package manager (npm/yarn/pnpm) and version: yarn v1.21.1

Logs (Optional if provided reproduction)

Run vite or vite build with the --debug flag.
Provide the error log here.

That's a cssnext problem - this warning comes from the cssnext plugin, not vite.

That's a cssnext problem - this warning comes from the cssnext plugin, not vite.

Thanks! It's my problem. 发自我的荣耀手机-------- 原始邮件 --------发件人： Evan You<EMAIL_ADDRESS>2021年1月21日周四 22:41收件人： vitejs/vite<EMAIL_ADDRESS>szz19960815<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>  题： Re: [vitejs/vite] Some problems about the use of postcss-cssnext (#1619)
That's a cssnext problem - this warning comes from the cssnext plugin, not vite.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks! It's my problem. 发自我的荣耀手机-------- 原始邮件 --------发件人： Evan You<EMAIL_ADDRESS>2021年1月21日周四 22:41收件人： vitejs/vite<EMAIL_ADDRESS>szz19960815<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>  题： Re: [vitejs/vite] Some problems about the use of postcss-cssnext (#1619)
That's a cssnext problem - this warning comes from the cssnext plugin, not vite.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.


[bug 1253773] Consider upgrading/updating to the latest mapbox.js version, which is 2.3.0

Updated to mapbox 3.3.1 but require a new public key because the actual one is not working.

I did some initial tests, here are my findings:

Sometimes (not always) I get a white map and the API tells me that no access token was passed. I don't have a way to reproduce it, just happens from time to time :/ This has also happened on several different views. Can you see if you can reproduce that and fix it?
Create new event -> mark location -> fill out everything else -> save -> edit again -> click on location marker popup again -> view is not centered to the correct location. The same seems to happen on production, so your choice if you want to fix it here or just create a followup bugzilla bug for it. To keep the PR small in scope here, I'd suggest to do a followup.
The profile view is not the same anymore, check the screenshots below.

New:

Old/production:

Once those issues are fixed + the code comments I did above, I will do another testing round and then we can merge.

The access token are passed in the same old way, only with a different method. I saw that on changing the token I need to reboot docker for the env variable
I need to test that.
This is the zoom that in the new api is completelly different and I wasn't sure about it. I will change with a zoom less zoomed.

Working on the other feedback.

The new minimap, I cannot find the same theme of maps like in the previous version for the moment. I think that use a different theme can improve the feelings that the portal has new things.

About the issue I agree it exist also on the production portal. The problem is that the map doesn't include a marker and doesn't use the zoom. I think that to improve will be enough for the moment add a marker in the map and later see if it is enough.

We have also the problem that the value on the system seems truncated while leaflet give a more precise lat/lng.
I am looking to check this truncate of the value.

After a while of testing also changing the field for lat/lng I cannot get a way to have more 4 digits in this values.
Actually we use the location as area so we don't care to be precise, but last commit added a marker that show the right position and we need to save that value in the right way.

@Mte90 please ping me once you're done and I can test and review again.

For the moment I finished, I am not advanced in Django to understand what is happening before the save of the value.

I think that I will enlarge the height because actually is not showing few countries with the actual one.

@akatsoulas do you know why the geo coordinate are truncated?

Another ping for @akatsoulas
When we will have this approved and merged we can check for all the other tickets about the map

I will go through this PR asap. One thing that we should consider here is that we need to figure out what we will need in terms of subscription in order to be able to use the upgraded version.

Actually I am using a new key generated by mapbox because the actual in production doesn't work. They seems also different as string.

After a while of testing also changing the field for lat/lng I cannot get a way to have more 4 digits in this values.
Actually we use the location as area so we don't care to be precise, but last commit added a marker that show the right position and we need to save that value in the right way.

@Mte90 where exactly is that? for the profile? If so, I think truncating is a measure to prevent a full lat/lng information for somebody's exact location.

I've made another test to make sure we can capture everything that needs to be done. Here's the list:

Was there a specific reason why you added the marker? I personally think it's really hard to drag this and zoom in etc.
Can you answer my question regarding the truncated location values? I'm not sure what you mean by that.

Apart from this, I think everything is fine. I would do a final test after those two questions are answered.

With the new itnerface that use a marker we need a more precise value, actually Django save with a truncated version and not a compelte one and is missing 4 digits that can change a lot the position on the map.

Maybe I did something wrong, but the last time I tried I couldn't reproduce this. Can you share a video?

Uhm seems that now the problem of the digit of lat/lng is not happening anymore.
For the problem of the marker I recorded a video about how much is helpful on zooming https://youtu.be/sqoRE7bLAT4

On my view is not happening, maybe is something about retina on your mac?

On my view is not happening, maybe is something about retina on your mac?

Yes, seems to be something in my setup. Restarted everything and it looks good now.
@akatsoulas this is ready for a merge once the token is ready :)

@akatsoulas this is ready for a merge once the token is ready :)

or more specifically, let's wait with a merge here until we know everything will be fine. Otherwise we block ourself for a production release.

We need the keys to approve that, let's figure out that point.


error while compiling

when i try to set the optimization level in build.gradle I get this error :
./gradlew generateJavaScript
OpenJDK 64-Bit Server VM warning: Ignoring option --illegal-access=permit; support was removed in 17.0

FAILURE: Build failed with an exception.

* Where:
Build file '/workspaces/Eaglercraft-1.12-Project/build.gradle' line: 37

* What went wrong:
A problem occurred evaluating root project 'teavm'.
> Could not get unknown property 'OptimizationLevel' for root project 'teavm' of type org.gradle.api.Project.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 489ms

this is my build.gradle :
plugins {
    id "java"
    id "war"
    id "org.teavm" version "0.9.2"
}
repositories {
    mavenCentral()
}

// This is optional, but for real-world applications you need to interact with browser.
// This dependency provides useful wrappers.
dependencies {
    implementation teavm.libs.jsoApis
}

apply plugin: 'eclipse'

sourceSets {
    main {
        java {
            srcDir 'src/main/java'
            srcDir 'src/teavm/java'
        }
    }
}

teavm.js {
    addedToWebApp = true
    mainClass = "Main"
    outputDir = file("javascript");
    targetFileName = "classes.js"
    obfuscated = false;
    sourceMap = true;
    entryPointName = 'main';
    properties = null;
    optimization = OptimizationLevel.AGGRESSIVE;
    minHeapSize = 4;
    maxHeapSize = 128;
}

This is a configuration problem in your Gradle script, it has nothing to do with TeaVM

@radmanplays configuration relies on enum, but gradle couldn't recognize it without full package. So you should use:
optimization = org.teavm.gradle.api.OptimizationLevel.AGGRESSIVE;

@konsoletyper you can map property values in plugin to simplify configuration, like this:
final ExtraPropertiesExtension extraProps = project.getExtensions().getExtraProperties();
Arrays.asList(OptimizationLevel.values()).forEach(type -> extraProps.set(type.name(), type));

Enum value configuration becomes:
optimization = AGGRESSIVE;

(AGGRESSIVE here would be a known gradle property and so would be replaced by complete enum path)
Or longer variant could be used to just avoid the package:
Arrays.asList(OptimizationLevel.values()).forEach(type -> extraProps.set(type.getSimpleName()+"."+type.name(), type));

(for  optimization = OptimizationLevel.AGGRESSIVE;)

@xvik, nope, I won't do this trick. First, it pollutes global namespace. Second, it's Groovy-only. Third, users are expected to rarely configure this property manually. Optimization levels are carefully chosen for each particular platform. If a developer wants better debugging experience in their development machine, they can create separate run configuration for compiling debug JS by specifying -P command line. Another option is to create teavm-local.properties and exclude it from VCS, then specify all options for building locally. See more in documentation


Pad filenames with leading zeroes?

Would be nice to have an option to pad file/directory names with leading zeroes, so instead of a directory listing that goes:
1 10 100 101 102 103 104 105 106 107 108 109 11 110 (etc.)
instead it would produce a listing that goes
001 002 003 004 005 006 007 008 009 010 011 012 (etc.)

@Zehina this could be accomplished by first taking the argument end_chapter from function download_webtoon, calculating zeros = int(math.log10(end_chapter))+1 then passing it to download_chapter and then to download_image where you can use it in the file_name like this file_name = f'{chapter_number:0{zeros}d}_{page_number}'


mismatch template

I have a login_controller that renders index.html.drab in templates/login/ with this content:
<%= if @error !== nil do %>
    <p>
      <%= @error %>
    </p>
 <% end %>
<button drab-click="login"  type="button">Login</button>

I also defined the corresponding login_commander with simply:
defhandler login(socket, _sender) do
  poke socket, error: "Test error!"
end

When clicking the button, i got this error
[error] Drab Handler failed with the following exception:
** (Phoenix.Template.UndefinedError) Could not render "lib/tgshop_web/templates/layout/app.html" for TgshopWeb.LoginView, please define a matching clause for render/2 or define a template at "lib/tgshop_web/templates/login/*". The following templates were compiled:

* index.html

Assigns:

%{conn: %Plug.Conn{adapter: {Plug.MissingAdapter, :...}, assigns: %{}, before_send: [], body_params: %Plug.Conn.Unfetched{aspect: :body_params}, cookies: %Plug.Conn.Unfetched{aspect: :cookies}, halted: false, host: "www.example.com", method: "GET", owner: nil, params: %Plug.Conn.Unfetched{aspect: :params}, path_info: [], path_params: %{}, port: 0, private: %{phoenix_action: :index, phoenix_controller: TgshopWeb.LoginController, phoenix_endpoint: TgshopWeb.Endpoint}, query_params: %Plug.Conn.Unfetched{aspect: :query_params}, query_string: "", remote_ip: nil, req_cookies: %Plug.Conn.Unfetched{aspect: :cookies}, req_headers: [], request_path: "", resp_body: nil, resp_cookies: %{}, resp_headers: [{"cache-control", "max-age=0, private, must-revalidate"}], scheme: :http, script_name: [], secret_key_base: nil, state: :unset, status: nil}, error: "Test error!", view_module: TgshopWeb.LoginView, view_template: "lib/tgshop_web/templates/layout/app.html"}

Assigned keys: [:conn, :error, :view_module, :view_template]

    (phoenix 1.4.13) lib/phoenix/template.ex:341: Phoenix.Template.raise_template_not_found/3
    (phoenix 1.4.13) lib/phoenix/view.ex:410: Phoenix.View.render_to_iodata/3
    (phoenix 1.4.13) lib/phoenix/view.ex:417: Phoenix.View.render_to_string/3
    (drab 0.10.3) lib/drab/live.ex:692: Drab.Live.rerender_template/4
    (drab 0.10.3) lib/drab/live.ex:647: Drab.Live.process_poke/9
    (drab 0.10.3) lib/drab.ex:360: anonymous fn/7 in Drab.handle_event/6

What did I do wrong? Do I have to use mix drab.gen.commander Login instead of creating the files by hand?

Hmm, I'm still learning the internals of Drab's Live processing, so can you try a test for me, try changing your layout's app.html.eex to be app.html.drab and recompile all and see if that works then and tell me the result?  If that doesn't work would you be able to replicate it in a new minimized project and give me a git link for it here?  :-)

it is already app.html.drab :-) let me try to create a minimize project...

Yeah I'm quite curious now.  ^.^
Thanks!

whatt? ok, it is weird that it works now when I changed app.html.drab to app.html.eex. So I guess you dont need the mini project after all?

Hmm, not weird, that actually might tell me what's going on.  Go ahead and leave this open because that should still work regardless.  If you want to make a minimized project I'd be very grateful though!

so, here is the mini project: drab_test
There are two issues with it:

login handler only works if main layout is app.html.eex, fails when rename the layout to app.html.drab
CSS is messed up when layout has .eex extension. When changing it back to app.html.drab, CSS looks nice again!

Thanks a lot :+1:

Awesome!  I'll look at it when I can, thanks so much!


Add CDNJS version badge in README.md

This badge will show the library latest version on CDNJS!

Codecov Report

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

@@          Coverage Diff          @@
##           master    #11   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          70     70
  Branches       25     25
=====================================
  Hits           70     70

Continue to review full report at Codecov.

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


Hang in signal handler when printing stack trace

Working with backward and in most cases it handles printing our stack traces just fine. However, in one of our applications (for some reason) it seems to hang when resolving the stack trace using libdw. It appears that libdw is allocating some memory causing a deadlock within the signal handler. Below is the backtrace from gdb.
(gdb) bt
#0  0x00007fa52729e09c in __lll_lock_wait_private () from /lib64/libc.so.6
#1  0x00007fa527317698 in calloc () from /lib64/libc.so.6
#2  0x00007fa526bbe6ef in file_read_elf () from /lib64/libelf.so.1
#3  0x00007fa526bbf04f in __libelf_read_mmaped_file () from /lib64/libelf.so.1
#4  0x00007fa526bbf2ea in read_file () from /lib64/libelf.so.1
#5  0x00007fa528fb8326 in libdw_open_elf () from /lib64/libdw.so.1
#6  0x00007fa528fa9de2 in __libdwfl_getelf () from /lib64/libdw.so.1
#7  0x00007fa528faa090 in find_symtab () from /lib64/libdw.so.1
#8  0x00007fa528faad62 in dwfl_module_getsymtab () from /lib64/libdw.so.1
#9  0x00007fa528fb1810 in __libdwfl_addrsym () from /lib64/libdw.so.1
#10 0x00007fa528fb3053 in dwfl_module_addrinfo () from /lib64/libdw.so.1
#11 0x00007fa528fb1793 in dwfl_module_addrname () from /lib64/libdw.so.1
#12 0x00007fa529203aa1 in backward::TraceResolverLinuxImpl<backward::trace_resolver_tag::libdw>::resolve (this=this@entry=0x6e6cf98, trace=...)
    at xxx/extern/include/backward.hpp:1822
#13 0x00007fa5292068ad in backward::Printer::print_stacktrace<backward::StackTrace> (this=0x6e6cf80, st=..., os=..., colorize=...)
    at xxx/extern/include/backward.hpp:4034
#14 0x00007fa529201bd0 in backward::Printer::print<backward::StackTrace> (os=..., st=..., this=<optimized out>)
    at xxx/extern/include/backward.hpp:4000

Any ideas on what could cause this? I'm happy to help provide info and help fix the issue.

FYI looks like this was causing by the signal handler being called recursively from another malloc() call that raised SIGSEGV'd
#36 <signal handler called>
--Type <RET> for more, q to quit, c to continue without paging--
#37 0x00007f6fbf3f0a4f in raise () from /lib64/libc.so.6
#38 0x00007f6fbf3c3db5 in abort () from /lib64/libc.so.6
#39 0x00007f6fbf433057 in __libc_message () from /lib64/libc.so.6
#40 0x00007f6fbf43a1bc in malloc_printerr () from /lib64/libc.so.6
#41 0x00007f6fbf43babc in _int_free () from /lib64/libc.so.6
#42 0x00007f6f8071ade5 in osgeo::proj::common::UnitOfMeasure::~UnitOfMeasure() () from /usr/proj82/lib/libproj.so.22
#43 0x00007f6fbf3f31ec in __run_exit_handlers () from /lib64/libc.so.6
#44 0x00007f6fbf3f3320 in exit () from /lib64/libc.so.6
#45 0x00007f6fbf3dccaa in __libc_start_main () from /lib64/libc.so.6
#46 0x000000000040154e in _start ()

Problem appears to be in the shutdown of the proj library. Not sure why yet.
Closing since it's not a problem with backward-cpp

You either have a memory corruption. Which happens to mutate some malloc data. Or the wrong pointer to free. Or maybe even a double free. The next call to malloc (_int_free()) appears to abort the program. Which most likely leaves the malloc mutex locked behind. Then, when trying to print the trace, libdw calls malloc. Which deadlocks.


sslv3 alert handshake failure

Hello,
I always get that SSL errors. Can you please help me how to fixthis?
root@Server:/usr/lib/node_modules/homebridge-hisense-tv-remotenow/bin# python3.9 hisensetv.py <IP_ADDRESS> --authorize --ifname ens3 [2022-01-16 20:09:04,355] [INFO    ] Unverified SSL context created. Traceback (most recent call last):   File "/usr/lib/node_modules/homebridge-hisense-tv-remotenow/bin/hisensetv.py", line 6, in <module>     __main__.main()   File "/usr/lib/node_modules/homebridge-hisense-tv-remotenow/bin/hisensetv/__main__.py", line 128, in main     with tv:   File "/usr/lib/node_modules/homebridge-hisense-tv-remotenow/bin/hisensetv/__init__.py", line 137, in __enter__     self._mqtt_client.connect(self.hostname, self.port)   File "/usr/lib/python3/dist-packages/paho/mqtt/client.py", line 941, in connect     return self.reconnect()   File "/usr/lib/python3/dist-packages/paho/mqtt/client.py", line 1104, in reconnect     sock.do_handshake()   File "/usr/lib/python3.9/ssl.py", line 1309, in do_handshake     self._sslobj.do_handshake() ssl.SSLError: [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:1123)
Also --no-ssl also does not help:
root@Server:/usr/lib/node_modules/homebridge-hisense-tv-remotenow/bin# python3.9 hisensetv.py <IP_ADDRESS> --authorize --ifname ens3 --no-ssl [2022-01-16 20:12:54,347] [INFO    ] No SSL context specified. Traceback (most recent call last):   File "/usr/lib/node_modules/homebridge-hisense-tv-remotenow/bin/hisensetv.py", line 6, in <module>     __main__.main()   File "/usr/lib/node_modules/homebridge-hisense-tv-remotenow/bin/hisensetv/__main__.py", line 128, in main     with tv:   File "/usr/lib/node_modules/homebridge-hisense-tv-remotenow/bin/hisensetv/__init__.py", line 145, in __enter__     raise HisenseTvTimeoutError(f"failed to connect in {self.timeout:.3f}s") hisensetv.HisenseTvTimeoutError: failed to connect in 10.000s

It was solved using that SSL files: https://github.com/MrAsterisco/hisensetv/tree/master/cert


Feature/0568 fwd core tests

Submission Checklist

[x] Run unit tests: ./runTests.py test/unit
[x] Run cpplint: make cpplint
[x] Declare copyright holder and open-source license: see below

Summary:
Finishes testing for core C++ library component of mixed-mode autodiff up to 3rd order.
Required additions of logical operators (!, && and ||).
Tests switched from big enumerations to framework that tests against double results and tests derivatives with finite diffs.
Intended Effect:
Enable us to trust higher-order autodiff for core C++ lib.
How to Verify:
Lots and lots of tests.
Side Effects:
No.
Documentation:
Added doxygen doc for functions that didn't have it and for new functions.
Reviewer Suggestions:
anyone
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):
Columbia University
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

Even with six new function implementations, doc for all the operators, and much more thorough testing, it's still -3000 lines!


[BUG] API generator failing on main

What is the bug?
API generator workflow failing on main.
How can one reproduce the bug?
https://github.com/opensearch-project/opensearch-py/actions/runs/8307539570/job/22736852101

Related to issue https://github.com/opensearch-project/opensearch-py/issues/693#issuecomment-1987744124


Add fields to StarknetGeneralConfig

Add fields to StarknetGeneralConfig.
These fields will be used in the StarknetState y SharedState implementation

Codecov Report

Merging #56 (9c2d3cc) into main (09362aa) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #56   +/-   ##
=======================================
  Coverage   78.31%   78.31%
=======================================
  Files          15       15
  Lines         641      641
=======================================
  Hits          502      502
  Misses        139      139

Impacted Files
Coverage Δ

src/definitions/general_config.rs
100.00% <ø> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Adding material2 to an cli created app

Please provide us with the following information:

OS?  Mac OSX (Mavericks)

Versions.
angular-cli: 1.0.0-beta.1
node: 5.10.1
os: darwin x64

Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.

a. ng new myapp
b. cd myapp
c. ng serve
d. added toolbar import and directives to myapp.component.ts
e. view javascript console
f. Loading... remains showing
g. Console shows: GET<EMAIL_ADDRESS>404 (Not Found)

The log given by the failure. Normally this include a stack trace and some
more information.

zone.js:461 Unhandled Promise rejection: Error: XHR error (404 Not Found) loading<EMAIL_ADDRESS>at XMLHttpRequest.wrapFn [as _onreadystatechange] (http://localhost:4200/vendor/zone.js/dist/zone.js:769:30)
at ZoneDelegate.invokeTask (http://localhost:4200/vendor/zone.js/dist/zone.js:356:38)
at Zone.runTask (http://localhost:4200/vendor/zone.js/dist/zone.js:256:48)
at XMLHttpRequest.ZoneTask.invoke (http://localhost:4200/vendor/zone.js/dist/zone.js:423:34)
Error loading<EMAIL_ADDRESS>as "@angular2-material/toolbar" from http://localhost:4200/app/running-costs.component.js ; Zone:  ; Task: Promise.then ; Value: Error: Error: XHR error (404 Not Found) loading http://localhost:4200/vendor/@angular2-material/toolbar/toolbar.js(…)

Mention any other details that might be useful.
I followed these instructions https://github.com/angular/angular-cli/wiki/3rd-party-libs to add material to the app

@chrisvelevitch ,
Can you paste your /system-config.ts and /angular-cli-build.js here?

Please refer to https://github.com/angular/angular-cli/wiki/3rd-party-libs#adding-material2-to-your-project.

@hansl: I stated that link in the other details section of my original post.
@pkamdem: here are the files you requested:-
angular-cli-build.txt
system-config.txt


Update xpath-weekday-from-datetime.md

Noticed that the dates in the example are out by one day. I've tested this will all weekdays...

Thanks for the Pull Request,
Have asked development team to confirm this, and will then publish it.
Request for confirmation made in #datastorage_totw Slack channel today.

Hi @Andy-Fleming,
The developers here have tried to reproduce this case but have found that the day of the week is being returned as described in the original documentation (i.e. Wednesday (today) is day 4).
They suggest that there might be something else going on and ask that you raise a support ticket from the Submit a request button on https://support.mendix.com so that it can be investigated further.
As the results we get are different, I will close this pull request. If there is an issue, Mendix support will contact me with further documentation updates.
Thank you for taking the trouble to suggest an update to our documentation. We appreciate your desire to make Mendix documentation better.
Yours
Mark van Ments.


Check if enough bytes was received

@mehcode are Actions not running for PRs from forks? I don't see a build status on this one.

cc #7

@VersBinarii Please rebase on master and CI should run.

I've made a mess of this, let me create another PR


add docs to _relative_import

Thanks for your help! which cell edit below should I use?```python# hide`name` is the actual imported module name used in file `fname`, see examples below, and the output is the relative import name of `name` based its relative location to `fname`.```or ```md#hide`name` is the actual imported module name used in file `fname`, see examples below, and the output is the relative import name of `name` based its relative location to `fname`.```

Just write #hide at the beginning of your markdown cell:
# hide
`name` is the actual imported module name used in file `fname`, see examples below, and the output is the relative import name of `name` based its relative location to `fname`.


Can no longer do setPassword() from cloud code with the master key

We have an admin interface so CS can set passwords for users who are having trouble setting their own.  Unfortunately I can no longer seem to set the password for a user from cloud code using the master key.
Environment Setup
Get a user from cloud code using Parse.Query(Parse.User).get().  ACL is set so that the user can read/write their own data and anyone in the Admin role can read it, but we require the master key to actually change another user's data.
Steps to reproduce
Call user.setPassword("some new password") and attempt to save with useMasterKey: true.
Logs/Trace
error: ParseError { code: 101, message: 'Permission denied for this action.' }

How are you calling save?  The right way would be, user.save(null, { useMasterKey: true });

I get the error with the following test code, however I am now also getting a permission denied error for Parse.User.signUp which makes me wonder if there's some configuration problem with the schema or something.  Logging in works.
Parse.Cloud.define('testSetPasswordForUser', function(request, response) {
    new Parse.Query(Parse.User).get(request.params.userId, {
        useMasterKey: true,
        success: function(user) {
            user.setPassword(request.params.newPassword);
            user.save(null, {
                useMasterKey: true,
                success: response.success,
                error: function(obj, error) {
                    response.error(error.message);
                }
            });
        },
        error: function(obj, error) {
            response.error(error.message);
        }
    });
});

what error?.. I think you should json encode the object in a response to a cloud function:
Parse.Cloud.define('testSetPasswordForUser', function(request, response) {
  var query = new Parse.Query("_User");
  query.get(request.params.userId, { useMasterKey: true }).then((user) {
    user.setPassword(request.params.newPassword);
    return user.save(null, { useMasterKey: true });
  }).then((user) => {
    response.success(JSON.stringify(user));
  }, (obj, error) => {
    response.error(error.message);
  });
});

This may be a separate issue :)  But I'm trying to create a user to test the password setting in a clean way and this error is happening.  I am on 2.1.6.
Parse.initialize("testapp", "");
Parse.serverURL = 'http://localhost:1337/parse';

<EMAIL_ADDRESS>"somepass").then(function() {
    console.log('success');
}, function(e) {
    console.log(e);
});

POST /parse/users { host: 'localhost:1337',
  connection: 'keep-alive',
  'content-length': '245',
  'cache-control': 'max-age=0',
  origin: 'null',
  'user-agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36',
  'content-type': 'text/plain',
  accept: '*/*',
  'accept-encoding': 'gzip, deflate',
  'accept-language': 'en-US,en;q=0.8' } {
  "username"<EMAIL_ADDRESS>  "password": "somepass"
}
error: ParseError { code: 101, message: 'Permission denied for this action.' }

Take a look at the _SCHEMA collection, the row for the _User.. It's failing a class level permission, so tell me what is in the _metadata key of that object.

    "_metadata": {
        "class_permissions": {
            "get": {
                "*": true
            },
            "find": {
                "role:Admin": true
            },
            "update": {
                "*": true
            },
            "create": {
                "*": true
            },
            "delete": {},
            "addField": {},
            "readUserFields": [],
            "writeUserFields": []
        }
    },

Try adding "*": true temporarily to the addField object..   If that doesn't work, it's unclear which operation is being prohibited, and you should add a log line to node_modules/parse-server/lib/Schema.js in the validatePermission method: console.log(className, aclGroup, operation);

Okay, that did work, and after creating one user I set it back the way it was and it seems happy.  It also has fixed the original error with setting a user's password with the master key.
Looking at the schema, it seems to have added these fields to the schema record for _User that weren't there from the initial migration:
    "password": "string",
    "ACL": "object"

I'm pretty sure I've run User.signUp a bunch in the past so I'm guessing those were implicit fields in the past and upgrading to 2.1.6 means they're now explicit in the schema?  In any case, thanks for the help!

Ok, glad it's working..  CLPs are still an area in progress.

I think the actual fix here is if we are using the master Key canAddField (in DatabaseController) should always return true. I've created a PR https://github.com/ParsePlatform/parse-server/pull/1294
As for the issue with the password field not being part of the _User object, Shouldn't we explicitly check the defaultColumns as well in Schema.js.


Backport Release for v0.12.4

@ThummeTo can we get a backport release for this v0.12.4?

Had the same thought :-D
Tests are running (I opened a dedicated branch for that, see #108)


MINOR: Fix doc variable typos in TopicConfig

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@fxbing , thanks for the contribution!


Feature/octahedral grid support

Codecov Report
Patch coverage: 92.67% and project coverage change: -0.26 :warning:

Comparison is base (3d6bb90) 95.13% compared to head (68a41ad) 94.87%.

:exclamation: Current head 68a41ad differs from pull request most recent head 155be09. Consider uploading reports for the commit 155be09 to get more accurate results

Additional details and impacted files
@@             Coverage Diff             @@
##           develop      #40      +/-   ##
===========================================
- Coverage    95.13%   94.87%   -0.26%
===========================================
  Files           38       40       +2
  Lines         2405     2616     +211
===========================================
+ Hits          2288     2482     +194
- Misses         117      134      +17

Impacted Files
Coverage Δ

tests/test_cyclic_axis_slicer_not_0.py
100.00% <ø> (ø)

polytope/datacube/mappers.py
87.50% <87.50%> (ø)

polytope/datacube/xarray.py
96.55% <94.11%> (-2.34%)
:arrow_down:

polytope/datacube/datacube.py
96.15% <100.00%> (ø)

polytope/polytope.py
96.77% <100.00%> (ø)

tests/test_datacube_xarray.py
100.00% <100.00%> (ø)

tests/test_octahedral_grid.py
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Revert "Print line and column numbers for exception thrown (#1645)"

This reverts commit 74a89f7c383bc22758cbe55096ce3016c5c319d7.
Closes #1826
This commit is causing wrangler dev to not show uncaught exceptions. Reverting chrome-devtools-rs was also necessary.

@Electroid any idea if the underlying issue is in the changes for the lastest version of chrome-devtools-rs, or the changes here? It would be nice to fix that so we could keep line and exception numbers.

I couldn't find the root cause. It's something we can revisit after next release, but though it's better to get some exceptions than none in the meantime.


does not build with gradle 5.3

Cloned 22 March 2019
commit 6c474975be32a77b249a600c405ee09c02e127b3 (HEAD -> master, origin/master, origin/HEAD)
Merge: 7136933d8c3 e9b5611b2a2
Author: Sterling Greene<EMAIL_ADDRESS>Date:   Mon Jan 7 08:45:29 2019 -0500

$ gradle build

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':coreApi:compileGroovy'.
> Could not resolve all task dependencies for configuration ':coreApi:compileClasspath'.
   > Could not resolve project :buildCache.
     Required by:
         project :coreApi
      > Unable to find a matching variant of project :buildCache:
          - Variant 'apiElements' capability org.gradle:buildCache:5.2-20190321110000+0000:
              - Required minified 'true' and found compatible value 'true'.
              - Found org.gradle.category 'library' but wasn't required.
              - Required org.gradle.dependency.bundling 'external' and found compatible value 'external'.
              - Required org.gradle.jvm.version '6' and found incompatible value '8'.
              - Required org.gradle.usage 'java-api' and found compatible value 'java-api-jars'.
          - Variant 'runtimeElements' capability org.gradle:buildCache:5.2-20190321110000+0000:
              - Required minified 'true' and found compatible value 'true'.
              - Found org.gradle.category 'library' but wasn't required.
              - Required org.gradle.dependency.bundling 'external' and found compatible value 'external'.
              - Required org.gradle.jvm.version '6' and found incompatible value '8'.
              - Required org.gradle.usage 'java-api' and found compatible value 'java-runtime-jars'.
   > Could not resolve project :persistentCache.
     Required by:
         project :coreApi
      > Unable to find a matching variant of project :persistentCache:
          - Variant 'apiElements' capability org.gradle:persistentCache:5.2-20190321110000+0000:
              - Required minified 'true' and found compatible value 'true'.
              - Found org.gradle.category 'library' but wasn't required.
              - Required org.gradle.dependency.bundling 'external' and found compatible value 'external'.
              - Required org.gradle.jvm.version '6' and found incompatible value '8'.
              - Required org.gradle.usage 'java-api' and found compatible value 'java-api-jars'.
          - Variant 'runtimeElements' capability org.gradle:persistentCache:5.2-20190321110000+0000:
              - Required minified 'true' and found compatible value 'true'.
              - Found org.gradle.category 'library' but wasn't required.
              - Required org.gradle.dependency.bundling 'external' and found compatible value 'external'.
              - Required org.gradle.jvm.version '6' and found incompatible value '8'.
              - Required org.gradle.usage 'java-api' and found compatible value 'java-runtime-jars'.

Older versions of Gradle aren't expected to necessarily build with the latest version of Gradle.  Sometimes we may use a feature that didn't make a release or use internal APIs that have changed.
In this particular case, I think this is because of a real problem that 5.3 is detecting--we're trying to compile Java 6 targeting code against a Java 8 library.

In my case, my main and test source sets have different compile targets. And there's a common module shared between my submodules used only in tests with Java8 compile target.
    sourceCompatibility = JavaVersion.VERSION_1_6

    compileTestJava {
        sourceCompatibility = JavaVersion.VERSION_1_8
        targetCompatibility = JavaVersion.VERSION_1_8
    }

    dependencies {
        testImplementation project(':module-with-compile-target-1_8')
    }

I would say that this check should take into account that main and test compile targets may be different.

@SimY4 This particular issue was about building Gradle itself.  Could you open a new issue about your use case so it doesn't get lost?

Sure


Update airtable to latest version, v0.7.2

This updates airtable to the latest version, v0.7.2. See the changelog for more info on what changed.

v0.7.2 is no longer the latest version, so I'm going to close this. I encourage you to update to the latest version to get security fixes.


totp.verify always giving false.

Hey) @abhyuditjain could u elaborate on this issue resolution, please? Thx :)


Wrong definition of golden ratio?

Package defines golden ratio as
const GOLDEN_RATIO = (5.0^0.5 - 1.0) / 2.0

but wikipedia says
\varphi = \frac{ \sqrt{5} + 1}{2},

i.e., sign error?

You're right, it's not quite the "golden ratio" as defined there. Basically, we wannt $\text{width} / \text{height} = \varphi$. But we typically want to compute the height for a given width, i.e. $\text{height} = \text{width} / \varphi$. The GOLDEN_RATIO used in the package corresponds to $1 / \varphi$. Then height = width * GOLDEN_RATIO. So this is not a bug, just a not-completely-accurate variable name. If you think things should be different, feel free to make a PR! :)


Space name may not be unique if hierarchy is supported.

Currently the space-framework consider the space name (without the hierarchy path) to be unique across a provider instance. For providers that support hierarchy this is of course not correct.
path+name can be considered a unique identifier.

pushing to backlog at this time - decided not to support hierarchy in spaces, for now.

not  relevant for ks-0.20


Show adjusted modifier on strike MAP buttons

Closes #8775

Thanks for getting this sorted. Is this going to be a toggle?

Thanks for getting this sorted. Is this going to be a toggle?

No, it replaces the old button label.


Replace XInput library with updated one

This code adds better compatibility with newer controllers and different controller types
Also adds ASLR to the loaded library

This breaks docker since it tries to load xinput and hangs, presumably due to the messagebox.


Title from entity ?

I tried setting a dynamic title by using a entity, but that only results in [object Object]
By any chance, would this be possible?
title : {{ states.input_select.test.state }}

This is possible using the template card: https://github.com/iantrich/config-template-card


fix: correctly compile falsy property values

(This original post has been edited to reflect correctly the current content of PR.)
kuma-ui has some utility props but if the value of the properties are zero, the properties will be removed in spite of it is necessary.
Currently this behavior can be dismissed by the workaround of using a string "0" instead of numerical 0.
This PR makes the compiler recognize falsy values except null and undefined, as valid value and fixes the behavior.

Original Post
kuma-ui has some utility props that can change components' spaces, such as m and p but if the value of the properties are zero, the properties will be removed in spite of it is necessary.
Currently this behavior can be dismissed by the workaround of using a string "0" instead of numerical 0.
This PR makes the compiler recognize numerical 0 as valid value and fixes the behavior.

@mtripg6666tdr
Thank you! If you're up for it, would you mind adding this processing to the other utilities within the system as well?

By the way, using !propValue not only removes 0 but also empty strings. However, there may be cases where you want to insert an empty string into the content of ::before or ::after. I thought it might be good to create and reuse a function like isNonEmpty. What do you guys think? @kotarella1110  @taishinaritomi

Sure, it's good idea. Probably in many cases, what should be absolutely purged are null and undefined.
Considering empty strings are in many cases used as value of content, we may have to purge CSSs by seeing its property names and value, not only its value.
Anyway, if we use some so complex process that it can't write as one javascript statement, it's good to extract the utility method.

(Not directly relevant to the main point, but FYI "the value" of content never becomes "empty string" in JS representation since empty string is represented as quoted string like content: ""; (CSS) / {content: '""'} (JSON)). This is because we can also have non string values such as none content: none; (CSS) / {content: 'none'} (JSON). cf. MDN doc)

@naruaway
Thanks for the clarification! Considering this, how do you envision the isNonEmpty function should be implemented?

I think actually there is no need to treat 0 in a special way. So there is also no need to do anything about content property.
"Emptiness" is already expressed as undefined. I feel like something like propValue === undefined (and propValue !== undefined) is more correct

I agree with @naruaway , I checked the TS type and it seems that you just need to exclude undefined. if you want to exclude null and undefined in consideration of JS users, you can use the equality (==) operator (propValue == undefined).

So... propValue != undefined is most appropriate to be a judgment way of excluded properties, right? If so, I'll apply this change to the other properties not only "space"s. Where should I put the utility method?

@mtripg6666tdr
Yes, thank you. I believe If the function only consists of the '==' operator, we might not need to separate it out into a function.

I just updated changes to reflect the discussion.

Thanks! Could you add some test cases?

Should I add test cases of property values of null or undefined?

would be sufficient if we could ensure that a numerical 0 is properly converted 👍

then i think all set!


feat(ai): LLM monitoring init

WIP. NOT MEANT FOR REVIEW. PLEASE DO NOT LOOK UNLESS CURIOUS. SO MANY THINGS WRONG WITH IT.

@JoshFerge also have a look at this: https://github.com/getsentry/sentry-python/pull/2791
Maybe it does already what you want to do? Or you can add your features there?


WIP: Adds CertificateRequest resource

What this PR does / why we need it:
Adds new CertificateRequest resource to enable obtaining signed certificates through a Certificate Signing Request (CSR).
More notes to come.
fixes #303
Special notes for your reviewer:
Heavily WIP.
Adds CertificateRequest resource to obtain a signed certificate via CSRs

/assign

/retest

/close


QA script for XLA under tensorflow-develop-upstream

QA team can use this to test XLA
./tensorflow/tools/ci_build/linux/rocm/run_xla.sh

Can you also add to: https://github.com/ROCm/tensorflow-upstream/tree/develop-upstream-QA-rocm62

done https://github.com/ROCm/tensorflow-upstream/pull/2495

retest Ubuntu-GPU-multi please
retest Ubuntu-GPU-single please

retest Ubuntu-GPU-single please

retest Ubuntu-GPU-single please

retest Ubuntu-GPU-single please

retest Ubuntu-GPU-single please

retest Ubuntu-GPU-single please

retest Ubuntu-GPU-single please

retest Ubuntu-GPU-single please

retest Ubuntu-GPU-single please

retest Ubuntu-GPU-single please

retest Ubuntu-GPU-single please

retest Ubuntu-GPU-single please

retest Ubuntu-GPU-single please

retest Ubuntu-GPU-single please


Database Password [2019] update?

Any update on Database Encryption / Password? it's now 2019 last post was 2017.

This has indeed been resolved: https://github.com/JoshuaWise/better-sqlite3/issues/188


Add app name to the label to ensure uniqueness

Wow! Thanks for the quick response and merge! 😄

I'm glad I could help somehow! 😃


vim_configurable: Add packPath option to vimrcConfig

Commit message:

Version 8 of vim adds the concept of "vim packages": subdirectories of
any directory listed in vim's "packpath" option, containing one or more
vim plugins. Vim will automatically load plugins placed in a package's
"start" subdirectory, while those placed in an "opt" subdirectory can be
loaded manually.
Correspondingly, vimrcConfig's packPath option accepts a set with
"start" and/or "opt" attributes containing lists of nix packages, which
are then combined into a vim package, which is then added to vim's
packpath.

I just tried to find the simplest thing that would work.  Feedback welcome.
Things done

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

[ ] NixOS
[x] macOS
[ ] Linux

[x] 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.

I admit that I don't understand the ci error.  The OS X build timed out after successfully building the test derivations?

That CI error looks like it's probably bogus and can be ignored.

Corrected a typo in the documentation comment.

Ah, I just remembered doc/language_frameworks/vim.md.  To be honest, I never fully understood it.  Will leaving it as-is block this PR?

👍

In vim terms, what I've written creates a single package named 'nix'.  Another possible api would expose the concept of multiple packages with arbitrary names.  I don't know what people would use that for, but it could look like this instead:
vim_configurable.customize {
  vimrcConfig.packages.nixOrWhateverOtherNameYoudLike = with vimPlugins; {
    start = [ youcompleteme ];
    opt = [ elm-vim ];
  };

I didn't like the idea of forcing people to come up with package names when they don't seem to matter; once vim is running, packages seem to be transparent, with all of their plugins made available the same way.
Maybe package is a better attribute name than packPath though...

@nicknovitski sorry, I've reread you message 3 times and can't understand what do you want to say.

Forgive me, I'll try to explain myself clearly.
Currently my patch adds a packPath argument to vimrcConfig. Using that argument creates a nix package which contains a single vim package named nix.
I asked two questions.

First, should the API expose or hide the name of the vim package?
Currently it's hidden:
vimrcConfig.packPath.start = [ vimplugin1 vimplugin2 ];

By exposing it, users would be able to create multiple vim packages, but they would have to name all of them:
vimrcConfig.packPath.vimPackage1.start = [ vimPlugin1 ];
vimrcConfig.packPath.vimPackage2.start = [ vimPlugin2 ];

Second, should the argument name be package or packages, instead of packPath?
vimrcConfig.package.start = myVimPlugins;
# OR
vimrcConfig.packages.vimPackage1.start = myVimPlugins;

I've change my patch to use the more explicit approach, and to use packages instead of packPath, like so:
vimrcConfig.packages {
  myVimPackage = with vimPlugins; {
    start = [ youcompleteme ];
    opt = [ elm-vim ];
  };
};

@nicknovitski Do you see a use case for multiple packages rather then having a single package called nix like your first implementation?


Feature request: colorcolumn supporting multiple values (only in settings.json)

Having multiple highlighted columns is useful in some cases.
For example, Git commit messages usual practice: first line 50 columns, body text 72 columns.
    "ft:git-commit": {
        "colorcolumn": [50, 72]
    },

In Python, the black formatter defaults to 88 columns for code, but for the docstrings and comments, our team prefers breaking them at 80 columns.
    "ft:python": {
        "colorcolumn": [80, 88]
    },

In general, 80 columns is what I like to have, for any other file type.
    "colorcolumn": 80

This is a similar request to the rejected #2694, but my proposal here would be simpler: no new/renamed commands, no user-noticeable changes on the use of set colorcolumn.
We could keep the interactive use as it is, aiming for the simple/common case: set colorcolumn <integer> to set it to a specific column, or zero to turn it off. No changes here.
But, if the user has manually changed the settings.json file and set the value to a list of numbers, those will be respected.
If this makes more sense, maybe it could be valid only for scoped settings (ft: and glob), since those are already not changed by the interactive set command.
Would that be acceptable?

Although I think the value of colorcolumn should be not an array of numbers but a simple comma-separated string of numbers, for compatibility and user convenience reasons.

Hmm, actually even that would not be backwards compatible, since currently the value of colorcolumn in settings.json is a number, not a string, and currently micro requires any standard option's value to have the same type all the time, it doesn't provide "dynamic typing" for that. So it's not so easy.


[AutoRelease] t2-logic-2023-11-02-83989(can only be merged by SDK owner)

https://github.com/ChenxiJiang333/test/issues/1
Live test success

issue link:https://github.com/ChenxiJiang333/test/issues/1


Add ESLint

Add ESLint with custom configuration

Perfect guys, it's gonna help a lot to review work of everybody now. Same formatting for everybody reduce significantly the number of changes.


cpu2017 on P8 miscompares with 500.perlbench_r

I'm running CPU2017 on a P8 machine built with xlC/at11.0 and getting miscompares with 500.perlbench_r:
Any idea?
Running Benchmarks
Running (#1) 500.perlbench_r test base P8_4S (1 copy) [2018-08-10 19:39:24]
Error with '/home/cpu2017/bin/specinvoke -d /home/cpu2017//p8_4S/benchspec/CPU/500.perlbench_r/run/run_base_test_P8_4S.0000 -f compare.cmd -E -e compare.err -o compare.stdout'; no non-empty output files exist
Command returned exit code 1
***** Miscompare of test.out; for details see**
/home/cpu2017//p8_4S/benchspec/CPU/500.perlbench_r/run/run_base_test_P8_4S.0000/test.out.mis
Invalid run; unable to continue.
If you wish to ignore errors please use '-I' or ignore_errors
The log for this run is in /home/cpu2017//p8_4S/result/CPU2017.002.log
The debug log for this run is in /home/cpu2017//p8_4S/result/CPU2017.002.log.debug

Temporary files were NOT deleted; keeping temporaries such as
/home/cpu2017//p8_4S/result/CPU2017.002.log.debug and
/home/cpu2017//p8_4S/tmp/CPU2017.002
(These may be large!)

runcpu finished at 2018-08-10 19:40:02; 44 total seconds elapsed
[root@localhost cpu2017]# cat /home/cpu2017//p8_4S/benchspec/CPU/500.perlbench_r/run/run_base_test_P8_4S.0000/test.out.mis
0254:  t/run/noswitch .............................. ok
t/run/noswitch ..............................
^
'test.out' short
[root@localhost cpu2017]#

Hello,
My apologies for the delayed response.
Looking at the error and consulting with others, we think the issue lies on the P9 configuration file, which is not meant for direct use on P8 without tweaking it first.
In the LE64Test_P9.cfg config file the line:
EXTRA_COPTIMIZE = -O5 -qarch=pwr9 -qtune=pwr9
should be:
EXTRA_COPTIMIZE = -O5 -qarch=pwr8 -qtune=pwr8
Also, please ensure that the cpu binding corresponds to the system-under-test's characteristics.
Let me know if this works or not.
-JM

Hello,
My apologies for the delayed response.
Looking at the error and consulting with others, we think the issue lies on the P9 configuration file, which is not meant for direct use on P8 without tweaking it first.
In the LE64Test_P9.cfg config file, the line:
EXTRA_COPTIMIZE = -O5 -qarch=pwr9 -qtune=pwr9
should be:
EXTRA_COPTIMIZE = -O5 -qarch=pwr8 -qtune=pwr8
Also, please ensure that the cpu binding corresponds to the system-under-test's characteristics.
Let me know if this works or not.
-JM

sure, i swapped pwr8 <=> pwr9 at very beginning. Also i adjusted numa settings but it shouldn't make sense because i'm running copies=1 and still see miscompares

fixed by re-installing full environment from scratch

Closing for now.
Please reopen if you see behavior again.


Make sure externals logic works on Windows.

This should fix failing tests on Windows.

@arunoda An idea: It might be easier to start a pattern of normalizing file paths with 'slash' rather than accounting for both possibilities.

@zenflow that's a great idea. That's a good one for another PR.
If you can do it sooner, we can take it.
Otherwise, I'll add it to my TODO list.


Index route promise warning

When providing a JSON-API representation of the index route, fortune reports:
Warning: a promise was rejected with a non-error: [object Object]
    at processImmediate [as _immediateCallback] (timers.js:383:17)
From previous event:
    at Server.connection (/home/ravenous/dev/mayfly/bikeshop/node_modules/fortune/lib/net/http_server.js:229:6)
    at emitTwo (events.js:87:13)
    at Server.emit (events.js:172:7)
    at HTTPParser.parserOnIncoming [as onIncoming] (_http_server.js:533:12)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:103:23)

The request is fulfilled fine, but just curious as to why the index route output is being thrown as if it were an error

The index route is a hack basically. Either it can make an invalid request to fortune or skip it altogether by throwing.

This warning is now suppressed by throwing an actual error: https://github.com/fortunejs/fortune-json-api/commit/53d83250be3144a005416a3f85c8ba8d0043a1ce#diff-27a1c86133de4310373decfdad200a91R91
p.s. the JSON API spec doesn't define any index route at all, so this is pretty implementation specific.

Nice one! I didn't realise JSON API didn't stipulate an index route; good to know.


Movement is buggy at high speedz and can be interrupted at inappropriate timez.

Setting another target while moving causes movement to be confused, and on high speedz Gruntz fizzle a bit and stop sometimes while moving.

Make it so that Gruntz finish the movement they already began, and only then change direction, if they have another target set for them.


Add required rule for a column

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.002%) to 96.853%

Totals

Change from base Build<PHONE_NUMBER>:
-0.002%

Covered Lines:
2524

Relevant Lines:
2606

💛  - Coveralls


Could not propose DLC channel: Wallet error Wallet does not hold enough UTXOs

Even though the coordinator has enough utxos (and funds) it happens now frequently that the coordinator still fails to propose a dlc channel.

Built a tool to check the coin selection locally with the prod seed, but couldn't reproduce the error. Michael eventually succeeded, but I can't say why.

@bonomat @luckysori I've also assigned you to this ticket since all of us have been working on this so far. Any ideas what we could do next?

My only direct experience with this problem was solved my doing a full sync.
My first few attempts at doing a full sync failed because I misinterpreted the API and thought it accepted a JSON body. For reference, this is what the request should look like to trigger a full sync:
curl -X POST "localhost:8000/api/admin/sync?full=true&gap=200"

What do you think of allowing to specify the wallet seed separately to the coordinator and then switch on-chain wallets once in a while to reduce the gap we have to carry forward?


Add Upstage AI Integration (Document Parse, Embeddings, and Generation)

This PR introduces comprehensive integration with Upstage AI services, adding three new components.
They have high performance. (For more information, visit https://www.upstage.ai/ and https://www.upstage.ai/products/document-parse)

Document Processing:

Added UpstageDocumentParseReader for converting documents to structured HTML format
Integrated with Upstage Document AI API for enhanced document parsing

Embedding Support:

Added UpstageEmbedder supporting 'embedding-query' and 'embedding-passage' models
Implemented vector generation for both documents and queries

Text Generation:

Added UpstageGenerator supporting Solar models (solar-pro, solar-mini)
Implemented streaming response generation with context handling

Configuration Updates:

Added new environment variables:

UPSTAGE_API_KEY: For authentication
UPSTAGE_BASE_URL: For custom endpoint configuration (optional)

Updated README.md to reflect new capabilities and configuration options

The integration is available in both production and development environments, maintaining consistent API patterns with existing integrators.
Testing:

Verified document parsing functionality with various file formats
Tested embedding generation and similarity search
Validated streaming text generation with context windows
Confirmed proper error handling and rate limiting

Dependencies:

No new package dependencies required
Uses existing aiohttp/httpx for API communication

Documentation:

Updated README.md with new features and configuration options
Added inline documentation for all new components

This integration enhances Verba's capabilities with state-of-the-art document processing, embedding, and generation features from Upstage AI.

If you agree, you can simply add a comment to this PR that you agree with the CLA so that we can merge.
I agree. Thanks!!

Thanks a lot for the PR ❤  Sorry for the delay, I'll look into it


chore updated change log

Description

updated change log.

Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[x] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[x] Copyright and license header are present on all affected files

Closing this PR for app version correction.


Change color of the Text Select Handle in the input dialog

Is it possible to change the color of the Text Select Handle in the Input Dialog like it is in the Custom View Dialog?

That's not a library feature, that's part of the Material theme on API 21+ or AppCompat for all API levels.

I use AppCompat but it's still not colored, it only works if i use a custom view.

Make sure you're passing an Activity context to your dialog builder.

I do and the edittext itself is colored, only the Text Select Handle isn't, like in the first screenshot i posted.

Hmm, well there's not really much I can do. That's handled by the Android framework, not me.
If you're not using Android 5.0 or above, there might be an issue there.

Oh sorry, didn't look into at those screenshots long enough (since I'm doing homework). It's very odd that it's not the right color when you're on Lollipop. But like I said, that's handled by the framework so there shouldn't be an issue.

I'm doing this with a custom view now, is it possible to use a content message AND a custom view?

No, you'll need to put a TextView in there

Wait! I found a bug related to this that will fix this issue @Hoolycraap

Ok, when are you going to release the fix?

ASAP, there's a few other small things going into this release too.

Currently the issue here is theme being used for the dialog.
In MaterialDialog's constructor:
protected MaterialDialog(Builder builder) {
        super(DialogInit.getTheme(builder));
        mBuilder = builder;
        final LayoutInflater inflater = LayoutInflater.from(getThemedContext());
        view = (MDRootLayout) inflater.inflate(DialogInit.getInflateLayout(builder), null);
        DialogInit.init(this);
}

In DialogInit.getTheme():
public static ContextThemeWrapper getTheme(MaterialDialog.Builder builder) {
        boolean darkTheme = builder.theme == Theme.DARK;
        if (!darkTheme) {
            darkTheme = DialogUtils.resolveBoolean(builder.context, R.attr.md_dark_theme, false);
            builder.theme = darkTheme ? Theme.DARK : Theme.LIGHT;
        }
        return new ContextThemeWrapper(builder.context, darkTheme ? R.style.MD_Dark : R.style.MD_Light);
}

The dialog is still using the Context that you pass to the Builder, but I think MD_Dark and MD_Light are overidding colorAccent or something. I'm currently doing homework so I'll have to look at this later.
@plusCubed @teslacoil

As a work around, I made the default accent colors in the dialog themes black (for light dialogs) and white (for dark dialogs). It looks significantly better than the Material theme's default teal.

The only place you notice this is the input dialog, because all other dialogs use views that don't show small theming issues like this or use views that theme themselves with library code.

https://github.com/afollestad/material-dialogs/releases/tag/v<IP_ADDRESS>

A lot of this will be improved with the next update also

https://github.com/afollestad/material-dialogs/releases/tag/v<IP_ADDRESS>