Redirect URI hostname must match

I am using oauth2 for eventbrite but I am getting this error: ```Redirect URI hostname must match``
here is my code
let oauthswift = OAuth2Swift(
            consumerKey:    "x",
            consumerSecret: "x",
            authorizeUrl:   "https://www.eventbrite.com/oauth/authorize",
            responseType:   "token"
        )

        oauthswift.authorize_url_handler = SafariURLHandler(viewController: self)

        oauthswift.authorizeWithCallbackURL(
            NSURL(string: "Tara://oauth-callback/eventbrite")!,
            scope: "", state:"",
            success: { credential, response, parameters in
                print(credential.oauth_token)
            },
            failure: { error in
                print(error.localizedDescription)
            }
        )

This is my url scheme - http://take.ms/f9Q0y

Maybe you must declare the callback URL into evenbrite website. Many
providers want you to declare an URL white list
Le mar. 9 févr. 2016 05:22, Rustan Corpuz<EMAIL_ADDRESS>a
écrit :

I am using oauth2 for eventbrite but I am getting this error: `Redirect
URI hostname must match
here is my code
let oauthswift = OAuth2Swift(
consumerKey:    "XQH5AWPSEU4C25TBEF",
consumerSecret: "DQFBX3OQNVA5SMLLSQ7TB7BQ7E5EOIX5R5Z36GQM4LDUCFISYW",
authorizeUrl:   "https://www.eventbrite.com/oauth/authorize",
responseType:   "token"
)
    oauthswift.authorize_url_handler = SafariURLHandler(viewController: self)

    oauthswift.authorizeWithCallbackURL(
        NSURL(string: "Tara://oauth-callback/eventbrite")!,
        scope: "", state:"",
        success: { credential, response, parameters in
            print(credential.oauth_token)
        },
        failure: { error in
            print(error.localizedDescription)
        }
    )

This is my url scheme - http://take.ms/f9Q0y
—
Reply to this email directly or view it on GitHub
https://github.com/OAuthSwift/OAuthSwift/issues/181.

a google search show you that it's an Eventbrite message
and maybe custom url scheme is not supported yet (ie. Tara://)
https://twitter.com/eventbriteapi/status/590861041317187587
If callback/redirect url must be http
https://github.com/OAuthSwift/OAuthSwift/wiki/API-with-only-HTTP-scheme-into-callback-URL

@phimage thanks i'll check it out.

can you tell me with whats wrong on this?
class FirstViewController: UIViewController, UIWebViewDelegate {

    @IBOutlet weak var webView: UIWebView!

    override func viewDidLoad() {
        super.viewDidLoad()

        webView.delegate = self

    }

    override func viewDidAppear(animated: Bool) {

        let oauthswift = OAuth2Swift(
            consumerKey:    "XQH5AWPSEU4C25TBEF",
            consumerSecret: "DQFBX3OQNVA5SMLLSQ7TB7BQ7E5EOIX5R5Z36GQM4LDUCFISYW",
            authorizeUrl:   "https://www.eventbrite.com/oauth/authorize",
            responseType:   "token"
        )

        oauthswift.authorize_url_handler = SafariURLHandler(viewController: self)

        oauthswift.authorizeWithCallbackURL(
            NSURL(string: "")!,
            scope: "", state:"",
            success: { credential, response, parameters in
                print(credential.oauth_token)
            },
            failure: { error in
                print(error.localizedDescription)
            }
        )

    }

    func webViewDidFinishLoad(webView: UIWebView) {
        let url = NSURL(string: (webView.request?.URLString)!)
        OAuthSwift.handleOpenURL(url!)
    }
}

next time please open an other issue
handle method must not call OAuthSwift.handleOpenURL()
handle must load the url to a web view to let user login and authorize
then the website/provider will redirect to the callback url passed (and OAuthSwift.handleOpenURL() will be call with an url containing information like token)
see demo code or readme


Columns

Hi!
Great work, congratulations!
I have a long list of options, like 60 or more, then i thinked about split the result in columns, to avoid long scroll.
Is there this option? If not, I think that is a good idea.
Thanks!

This is a good idea and that is because the pulldown list is left "compact" (not stretched from side to side).
You can add id manipulating css:

in scss

 ul.dropdown-menu {
        list-style-type: none;
        column-count:2 ..

in configuration using css through js configuration parameters

$multiSelects.bsMultiSelect(
    cssPatch : {
        choices: {columnCount:'2' },
    }
);

There are drawbacks of this - you wille need to manage it on mobile platforms 'manually'. Share your expirience. If it will be reach enough we would add the plugin that manage columns from js (I guess that SCSS can manage them from @media ).
Currently I'm working on plugins API.

https://dashboardcode.github.io/BsMultiSelect/snippetColumns.html


Atomic replication: ETCD Changes

Background: https://airtable.com/tblD3oZPLJgGhCmch/viwchkdQkRUw6hZ3z/recEjVou4DKjRbShz?blocks=hide
PM: @awoods187
Eng: @tbg, @bdarnell

Closing this as it's the same basic issue as #4722 AFAICT.
@tbg I can't see any reason why this would have doc impact given that #4722 did not.  No need to respond unless you disagree with that assessment.


Permanently free all babies from the tyranny of Baby Jail

Description
apology for poor english
when were you when hopper dies?
i was sat at home eating mothroachburger when nik post
‘hopper is kill’
‘no’
Actual, non-meme description
Baby Jail, the "new player and whitelist" server feature, was created to help guard the servers versus newbro tiders after the PC Gamer trailer. Its server, Hopper, has been removed from Wizden (because it outlived its purpose, turned into LRP-with-whitelist, and there is currently not enough admins to juggle the pre-Nov 2024 workload). This code should now be removed from the codebase or matured into a permanent fixture without a silly name.
Additional context
Baby Jail was a joke name for the feature, referring to "baby jail", a term I first heard from @peptron1 during her time adminning on TG. It's actually a regular internet meme. It probably shows how mentally stressed the contrib/maint crew were pre-trailer that the name got past the sniff test to begin with.

Paging @VasilisThePikachu on this as I know they wanted to do this recently.

My idea as to remove it after #33339 since I don't want to give myself a conflict currently (as easy as it will be to resolve)
Originally attempted to revert it in #29891, but it was during the time of hopper and despite many agreements it got added back until hopper was removed recently. Where I think It's pretty safe to say to remove it as we are like the only servers who use it anyway. And we got other servers to take a blow with us in case of a tide, so we don't really have the need to spin up new servers.

I've been triaged
this is an injustice


Automated cherry pick of #8407: fix informer backend

Cherry pick of #8407 on release/3.4.
#8407: fix informer backend

/lgtm
/approve


Solved Issue #1031: Add search suggestion in search bar

Fixes Issue
Closes: #1031
Changes proposed

Added a new Component for listing matching Links
The search returns list containing the website name and it's subcategory for context
This is done by searching through all the website names from database/index.ts
Not all logic from the previous components have been removed but only disabled through hardcoding.
Other older unwanted useEffects have been removed.

Screenshots

@rupali-codes , Thank you for your time with this PR.
Regards,
@vishnu9865

Deployment is getting failed could you resolve the deployment issue ? (that will enable us to see the changes on live website)

@rupali-codes @CBID2 isn't this issue same as #1144 👀

Deployment is getting failed could you resolve the deployment issue ? (that will enable us to see the changes on live website)

Ok @ujjawaltyagii looking into it.

@rupali-codes @CBID2 isn't this issue same as #1144 👀

Yeah, we are already working on this issue since.

@CBID2 👀

@CBID2 👀

Ooh, should we close this PR @rupali-code?s

@vishnu9865 this pull request seems duplicate to #1180, so unfortunately we will have to close this PR. We appreciate your time and willingness to contribute in LinksHub. Please feel free to raise another issue or PRs.
Thanks


Compact interface closes when clipping through blocks

Whenever you noclip through blocks, the compact interface opened by WE_CompactInterface closes automatically.
I don't have any workarounds for this issue at the time. If you know of any, please let me know!

After having spoken with Healthire, it appears a solution will be made available in a future game patch. The issue exists because line of sight to the source entity of the interface is lost, once inside blocks.
When your line of sight breaks (usually to the object, but here to 'yourself'), interfaces close automatically.
Setting the source entity to 0 (null entity) when opening the interface should solve this issue, but this does not currently work. https://github.com/Silverfeelin/Starbound-ItemInterfaces Should be updated to allow custom entity ids being given through the item parameters.

No longer an issue with changes in Starbound.


Update reference tests to the latest stable version?

People only test locally on the latest stable version, and as a result some PRs can introduce test failures (like #441). This would be easier to avoid if the reference tests were kept up to date with the latest stable version, so 1.9.4 at the time of writing.
On the other hand, it means that once we re-generate the fixtures with a new version, they are basically useless. Indeed, by definition, they will agree with the output of the code.
@oxinabox any idea how to resolve this conundrum?

More generally, this raises the question of what reference tests are for

We actually need to keep testing on 1.7  even if we update the fixtures,
because 1.8 changes how IO works in tests,
so we can't run the interactive tests on 1.8
though maybe it would just be ok to stop testing them?

In general the notion of reference tests is that you look at them before merging after regenerating, and confirm that they actually are correct

In general the notion of reference tests is that you look at them before merging after regenerating, and confirm that they actually are correct

So if we work on the assumption that the code is correct whenever reference tests pass, we could use that correct code to re-generate new reference tests at each Julia release?

Yes, because we assume that new julia releases are not breaking our stuff.

Okay. I'll try a big PR that does only that, re-generate all the fixtures with 1.9.4

Solved by https://github.com/JuliaCI/PkgTemplates.jl/pull/453


Flui

Description:

Give a detailed explanation of the issue

Steps to Reproduce:

Steps to reproduce this behaviour

Technical Information:

Minecraft:
Fabric API:
Industrial Revolution:
Modpack:

Logs:

Use a paste service, do not paste the logs directly here.

Details:
Extra information that might be helpful like screenshots or technical information about your computer.

accedentally submitted it srry


Adding some more new members!

Overview
Added 6 new members!
Member count is now 36!
Relevant Issue
Link issue this PR is related to

✅ By submitting this PR, I have verified the following

[x] Reviewed the contributing guidelines 🔍
[x] Added my name to the bottom of the list under the Contributors section in the README.md with a link to my personal website or GitHub profile 👥

@FrancesCoronel Image resized! ...& then there were 36!


Update tutorial005_py39.py

In line 146 the response_mode is specified as Token.  When we return a dict instead of a Token object, pydantic raise a Validation error

Hey there! The response_model is used to convert and validate the data sent from the function, so the function should be able to return a dict and it would be validated and converted with the Token model. The code example is intentional.
Is it not working for you? Could you write an example of what is not working?


Ability to perform automated installs in a kURL embedded cluster

It would be great to be able to completely automate the setup of kots in an embedded kURL cluster, the same way is possible with Automated Installations into existing clusters today. This would mean eliminating the following manual browser steps from the install process for kURL+kotsadm:

uploading license
supply Config values
reviewing preflight check results

Right now, when using the kotsadm addon for https://kurl.sh, kotsadm gets wired up to the rook RGW in a special way that's not possible to replicated today using kots install.
This means that if you were to run a kubectl kots install against a kurl cluster with kotsadm already installed, you end up with minio and an extra copy of the migration job. While not technically a blocker, I get the feeling this is not officially endorsed by the kots/kurl team.
Do we have any intentions for allowing automated installs in an officially supported way?

@dexhorthy isn't this the same as #809

@divolgin good catch, will close as dupe of #809


New package: LinearSolvePardiso v0.1.0

Registering package: LinearSolvePardiso
Repository: https://github.com/SciML/LinearSolve.jl
Created by: @ChrisRackauckas
Version: v0.1.0
Commit: efeb3a1cb1ffa3bbe9b7c93335717aa0f06ec118
Reviewed by: @ChrisRackauckas
Reference: https://github.com/SciML/LinearSolve.jl/issues/17#issuecomment-1129499082
Description: LinearSolve.jl: High-Performance Unified Linear Solvers

@ChrisRackauckas please see the message above.  Once you fix the automerge issues you can register again the new revision without changing the version number and this pull request will be automatically updated.
[noblock]


💄 color revamp

red / green gradients produce brown which is less exciting than red / blue purplish gradients... ¯_(ツ)_/¯


Nav mesh issue with custom moons

Hey,
i did setup a new moon of my conception ( sketchfab free assets conception tho ) and the only issue i finally cannot fix is quite hard to debug, the navmesh of the moon.
every npc spawning on the moon seems to not be placed on a navmesh ( log spamming nav mesh agent not on a navmesh etc )
my way to bake this one was as much like of the template moon : baking the navmesh then cut and paste the navmesh file in my moon folder with a name matching the new planet
i cannot visualize ingame if there is a nevmesh on my moon, quite hard to debug
ty for ur help

Hey,
i did setup a new moon of my conception ( sketchfab free assets conception tho ) and the only issue i finally cannot fix is quite hard to debug, the navmesh of the moon.
every npc spawning on the moon seems to not be placed on a navmesh ( log spamming nav mesh agent not on a navmesh etc )
my way to bake this one was as much like of the template moon : baking the navmesh then cut and paste the navmesh file in my moon folder with a name matching the new planet
i cannot visualize ingame if there is a nevmesh on my moon, quite hard to debug
ty for ur help

Do you visualize it though the prefab or directly on a scene ?

hey thanks for the quick reply,
my prefab is edited on a duplicate of the scene builder scene ( i dont like to mess with examples ) and i can fully visualize the navmesh on the map, it still doesnt really work ingame
could you tell me your process for baking a navmesh in ur maps ?

hey thanks for the quick reply,
my prefab is edited on a duplicate of the scene builder scene ( i dont like to mess with examples ) and i can fully visualize the navmesh on the map, it still doesnt really work ingame
could you tell me your process for baking a navmesh in ur maps ?

Simply click on bake, save the prefab, build the bundle


Testing Chosen.js

Chosen.js testing: http://cfpb.github.io/cfgov-refresh/blog_static/landing.html
Browsers

[x] Chrome (31)
[x] Safari (6,7)
[x] FF (28)
[x] IE11
[x] IE10
[x] IE9
[ ] IE8

Everything works well except for the bg img. The issue is with Legacssy and an issue has been created here: https://github.com/robinpokorny/grunt-legacssy/issues/7

[x] IE7 N/A Chosen is disabled on IE7, a standard select menu is the fallback
[x] Opera (12)
[ ] iOS (6,7)

Chosen is disabled on the iphone and ipod, a standard select menu is the fallback
Chosen is NOT disbaled on the ipad and does not work well because it activates the select underneath it. It's also very difficult to close it once opened.

[x] Android (4.4,4.3) N/A Chosen is disabled on Android, a standard select menu is the fallback
[ ] Blackberry Bold

Chosen is NOT disabled on Blackberry and suffers from a known issue where clicking on the drop down will activate items underneath it

Accessibility

[x] Keyboard friendly
[ ] Screen reader friendly

Not screen reader friendly, we will address this in the next sprint

Other

[x] Is useable without CSS

I'm going to assume since chosen is already implemented we can close this?

Seems like it. Looks like it was tested almost all the way, and the gaps would surface in general testing as well.

Ok closing for now


[Screen Reader - Open and close New Tab]: Screen reader does not announce position number for the tabs navigating via "Ctrl+Tab" or "Ctrl+Shift+Tab" key.

User Experience:
If the correct  information and relationships are not provided, it would be difficult for people with different disabilities as the information and relationships that are implied by visual or auditory formatting will not be preserved when the presentation format changes.
Having these structures and these relationships programmatically determined or available in text ensures that information important for comprehension will be perceivable to all.
Test Environment:
OS: Win 10 2004 Build (20262.1010)
App: Windows Terminal
App version: 1.4.3243.0
Repro Steps:

Open Windows terminal app.
Launch Narrator.
Press "Ctrl+Shift+T" to open multiple tabs.
Now press "Ctrl+Tab" or "Ctrl+Shift+Tab" key to navigate between tabs.
Observe the issue.

Actual Result:
Screen reader does not announce position number for the tabs navigating via "Ctrl+Tab" or "Ctrl+Shift+Tab" key.
Expected Result:
Screen reader should announce the position number for the tabs navigating via "Ctrl+Tab" or "Ctrl+Shift+Tab" key.
For e.g. If total 5 tabs are present and currently the focus is at 3rd tab then narrator should announce it as "3of 5".
Note: Same issue repro with NVDA.
Observation:  In scan mode narrator announces position number.
MAS Reference:
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}&cid=a7f80d30-34d6-4e03-af19-fa3c97a5bf31
MAS1.3.1_Position no does not get announced for tabs.zip

I'm guessing that this is the same thing as #8464, where we provide a little bit of metadata in the message. /cc @carlos-zamora

@zadjii-msft
Any update on this issue?

@akash07k @carlos-zamora is the one who's currently working on our accessibility bugs.
Carlos, do browsers do this? If so, then I'm betting this is also something that the WinUI team should implement themselves, like #8464

Thanks @zadjii-msft
@carlos-zamora I'd love to know the progress on this issue if possible. :-)

@akash07k @carlos-zamora is the one who's currently working on our accessibility bugs.
Carlos, do browsers do this? If so, then I'm betting this is also something that the WinUI team should implement themselves, like #8464

Ya, if WinUI team implements it then it will be fixed for many more apps too and it would be win-win for all.
I'd be investigating this issue in more detail tonight.

I have good news and bad news.
Good news:

tested this on v1.7.501.0 (preview selfhost) and v1.5.10411.0 (stable public release). It got fixed (probably by WinUI)

Bad news:

seeing a regression on v1.7.501.0. Tab names are not being read out by the screen reader. Submitting a separate issue for that.

@Chandresh1007 since this is fixed now, could you close the bug? Thanks.

Er, I tried this in 1.7 and didn’t hear an announcement for the tab index. Maybe the tab switcher interferes?

@carlos-zamora
Thanks for confirming,
Can you please let me know that where can I find that selfhosted build? is it publicly available or not?
And, please give the issue link for "tab names not being read" Would love to track it's progress.

I have good news and bad news.
Good news:

tested this on v1.7.501.0 (preview selfhost) and v1.5.10411.0 (stable public release). It got fixed (probably by WinUI)

Bad news:

seeing a regression on v1.7.501.0. Tab names are not being read out by the screen reader. Submitting a separate issue for that.

Apologies. I was in the process of writing a comment then got distracted with something else. The tab switcher actually "fixes" this functionality. However, when the tab switcher is not enabled, this bug occurs. So it's still valid, I think?
The default functionality setting includes the tab switcher though. That's the only reason I can think of disqualifying it, but that's not a good enough reason, I think.

Issue is fixed. Now the screen reader is announcing the position number along with its name and state. Verified on following Test Environment:
OS: Win 10 2004 Build (21301.1010)
App: Windows Terminal
App version: 1.5.10411.0
Hence, closing the bug.

Closing the bug as issue has been fixed.


Code hygiene

Please consider code hygiene as a value opposed to a burden.
https://scrutinizer-ci.com/g/szepeviktor/rainloop-webmail/?branch=master
https://scrutinizer-ci.com/g/szepeviktor/rainloop-webmail/issues/master?selectedLabels[0]=9&selectedSeverities[0]=10&orderField=path&order=asc&honorSelectedPaths=0
For example code coverage and automated styling check could be beneficial.
Thank you.

Thanks


Geo-location Filtering

Currently Geo-location location filtering only happens on the UI side.  However there are APIs, like Plenar.io that offer Geo-location filtering, when using the API.  So it would be nice to have some way of saying if the service can handle the filtering and then pass the Geo-location data down to the service, in a API call.

Proposed API changes:
new /capabilities resource
Sample response:
{
    “geoSpatialFiltering” : “true”
}

new "geo" param to  /{dataset id}/query resource
geo param=> geometry object
{
  "type": "Polygon",
  "coordinates": [
    [
        [
          -87.68353700637817,
          41.79390441395615
        ],
        [
          -87.68353700637817,
          41.79883151649387
        ],
        [
          -87.67439603805542,
          41.79883151649387
        ],
        [
          -87.67439603805542,
          41.79390441395615
        ],
        [
          -87.68353700637817,
          41.79390441395615
        ]
      ]
    ]
}

data tier

MongoDB -> $geoWithin (geometry can be polygon or multiPolygon)

Plenar.IO -> location_geom_within

Does Plenar.IO support "type": "MultiPolygon"?

No, we don't yet support multipolygons in API calls. How would you describe the priority of multipolygon support? Is it a must-have or a nice-to-have?

It turns out we support MultiPolygons and I just wasn't aware. Pleasant surprise! I made our multipolygon support "official" by adding it to our API test suite.
Here's a working example with a multipolygon consisting of a rectangle over downtown and a rectangle over Hyde Park:
http://plenar.io/v1/api/detail/?dataset_name=flu_shot_clinic_locations_2013_standard_format&obs_date__ge=2013-01-01&obs_date__le=2013-12-31&location_geom__within={"type":"MultiPolygon","coordinates":[[[[-87.616782188416,41.780144914492],[-87.616782188416,41.802286661135],[-87.569317817688,41.802286661135],[-87.569317817688,41.780144914492],[-87.616782188416,41.780144914492]]],[[[-87.667894363403,41.851662061565],[-87.667894363403,41.891799452396],[-87.597513198853,41.891799452396],[-87.597513198853,41.851662061565],[-87.667894363403,41.851662061565]]]]}

@WillEngler - that's about the best surprise a developer can ever find.
@nfspeedypur and @rladines - does this work and fit into the semantics?

As far as the API enhancement is concerned, this should work since this looks to be just the standard geoJson MultiPolygon construct.

@rladines To confirm, yes, it is just standards-compliant GeoJSON.


387 add custom history user

ISSUE 387

Do we also need to capture the date of the change along with the user ID, or is that automatically captured by the django history package (don't know the proper name for it) we're using?
Also flagging for you that there's a merge conflict in one of the migration files. Probably because I took too long to review this. Sorry!

That's correct, django simple history package by default takes care of the created_at and updated_at data fields.
No worries, Thanks for reviewing this PR :)

Code LGTM so I'm happy, although it looks like the action for backend tests failed???

Should be fixed now, Thank you!


Add integration tests for XCFramework support

Looks like BCSymbolMaps and dSYMs are actually stored inside the XCFramework itself, so the tests are much more straightforward.
I ran Rome with --use-xcframeworks and it looks like the .*.version weren't copied back into the Carthage/Build folder. Not sure if that's a mistake on my system or if there's something missing in the command.

@tmspzz I'm having trouble getting bats setup to run the tests, but I believe they should work. Are you able to verify them locally? Once that's done, we can merge this into @vikrem's PR and merge that into Rome.

@mpdifran
I am impressed this works with .ini as well. 🤯
This is great work!
One thing that is missing tho is testing for the current framework. Or did I miss it while reviewing 🤔


Epic: Plan for documenting and extending existing tools to serve MAAP users

Description
This epic focuses on planning for future work on the project based on the opportunities identified during the discovery and development process. This will involve defining future functionality and visualizing more kinds of data, among other tasks.
Tasks

Plan a workshop to brainstorm and define the future work for the project.
Define future functionality based on opportunities identified during the project, such as styling layers and allowing users to add their data.
Explore ways to achieve feature parity with similar tools in the market.
Investigate visualizing more kinds of data beyond raster data, such as extensive point and Zarr data.
Determine the feasibility and technical requirements for implementing the identified future work.
Create a roadmap or plan for implementing future work.
Document the outcomes of the workshop and the plan for future work.

Acceptance Criteria

A workshop is conducted, and future work is defined based on the opportunities identified during the project.
Future functionality is defined and explored, including ways to achieve feature parity with similar tools in the market.
Investigation of visualizing more kinds of data is conducted, and the feasibility and technical requirements are determined.
Roadmap or plan for implementing the future work is created and documented.

based on feedback from @abarciauskas-bgse : This roadmap should include feedback from users on using leafmap and its downsides. This roadmap should include a priority for new features to add, such as the ability to visualize point cloud datasets or create a mosaic from a STAC catalog query.

Research and explore existing tools which might help us achieve those new features. For example, can we visualize point clouds with kepler.gl and how? To visualize mosaics from COGs we probably need titiler-pgstac, can we test that out?

https://docs.google.com/spreadsheets/d/1KHSwtKfqEQA_uDwsaqj42i4dF60orbnN_iaWSvIk4lY/edit#gid=0


Discrepancy between Chinese_S_ZH.json and English_GB.json

Hi Will,
First off, thank you for creating my recent favorite rougelike game. I just discovered the DLC and bought it to verify my translation text.
There is some discrepancy between Chinese_S_ZH.json and English_GB.json. Note line 239 in the image below:

I have checked the Google spreadsheet and it looks like the English_GB.json file merely misses a few lines.
-CW

Thanks! Looks like I added an older version of the English file to the repo - I've now updated it


Refactor SMQTK search

@jeffbaumes
Primarily, this removes the Mongo db mapping that was required (and undocumented). It also generalizes the Solr chunked request utility and adds an event so I was able to move some of the uppercase logic out of ImageSpace proper and into the weapons plugin.

@jeffbaumes Can you review this? Just ensuring basic similarity searches still work.

LGTM

LGTM but needs README update.

Added a readme for the SMQTK plugin documenting the new environment variable.
Thanks all.

We also need to update the main ImageSpace README.md and explain how to configure and use these plugins. Thanks @danlamanna


No Music System exist in game.

No description provided.

#3 Solved along with modified UI( Plz merge it into master branch )


Music stops playing after a while

When using the in-browser client, music stops playing after a while:

Sometimes it stops looping after a while (choosing a new song and going back to Auto works)
Sometimes music (possibly all audio) stops working altogether (possibly main menu too); it comes back after a quick page refresh

This is fixed in the next update whenever server pulls client changes in. Thank you for the report!


"Uncaught ReferenceError: $day is not defined" when cursor moves over a cell

Get this in both the latest Chrome and Edge versions. Everything else aside from the "smooth" painting and erasing modes seem to work despite the errors.
index.js:266 Uncaught ReferenceError: $day is not defined
    at SVGRectElement.<anonymous> (index.js:266)
    at SVGRectElement.handle (jquery.min.js:1382)
    at HTMLDocument.dispatch (jquery.min.js:1316)
    at HTMLDocument.v.handle (jquery.min.js:1253)
(anonymous) @ index.js:266
handle @ jquery.min.js:1382
dispatch @ jquery.min.js:1316
v.handle @ jquery.min.js:1253

Can you send a screenshot of the file where the error appears?
If you installed via npm, you may have the transpiled version, therefore different line numbers.
Thanks!

Closing due to no reply...


Feature request - Higher upvotes required if post contains keyword(s)

My feed is dominated by Ukraine news, not against having some, it's important obviously, but I'd like a little less.
Is something like this possible;
If post contains terms: Russia, Ukraine, Putin, Zelenskyy  require 1000 upvotes,
If post does not contain those terms require 500 upvotes

This could probably work, I don't know if it would complicate the yml config file, I was thinking a web UI could help a little organizing all the settings.


[Service Bus] Revisit Client Library Live Test Timing Dependencies

Summary
During migration of the Service Bus client library into the central repository, work was done to stabilize the Live tests and ensure they ran with consistent results.  During this work, it was noted that many of the tests have timing components to them, as a way of dealing with the non-determinism of messaging.
With the suite now refactored to allow test isolation and parallel runs, it is suspected that areas of this timing code can be safely removed or refactored since tests no longer share global state.
Scope of Work

Review the Live tests for the Service Bus client and analyze the use of timing-based code, such as Thread.Sleep,  Task.Delay and loops that iterate and spin wait to determine if they are still needed.

Make any adjustments to refactor and clean timing code that is no longer needed or can be made more efficient.

Ensure that the Live tests continue to have deterministic and stable behavior when run locally and within the engineering system.

Out of Scope

Refactoring of the general approach for testing, the test cases, code style, and other artifacts of the code base unrelated to timing-related items.

Adding of additional test cases or new testing scenarios.

Success Criteria
The individual performing this work has confidence that timing code that could be removed or made more efficient has been or has filed follow-up issues to allow for deeper inspection and refactoring of areas that were unable to be addressed.
Details
The following were noted as potential areas of investigation:

SessionDiagnosticsTests (see line 180 and nearby)

PluginTests (a large portion of the class)

TestSessionHandler (a large portion of the class)

TransactionTests (a large portion of the class)

This issue was based on analysis of the track one client during the initial migration into this repository.   As efforts are now underway on a track two client, this items is no longer needed.


Add option to override symbols

Describe the change
Instead of using ASCII symbols on Windows and Unicode everywhere else this change defaults to Unicode everywhere.  Additionally options are offered to switch to the Unicode symbol set and/or override individual symbols.
Usage examples also added to readme:
TTY::Markdown.parse(markdown_string, symbols: :ascii)
TTY::Markdown.parse(markdown_string, symbols: {base: :ascii})
TTY::Markdown.parse(markdown_string, symbols: {override: {bullet: "x"}})

Also included is the fix for unescaped quotes in the ASCII symbol set (previously WIN_SYMBOLS, mentioned in #17/#14)
Benefits
Lets the user choose appropriate symbols for their platform/terminal/font situation.
Drawbacks
Defaulting to Unicode won't necessarily display well immediately on older machines.  In such scenarios the user can opt in to the ASCII symbol set instead.
Requirements
Put an X between brackets on each line if you have done the item:
[x] Tests written & passing locally?
[] Code style checked?
[] Rebased with master branch?
[x] Documentaion updated?

Pull Request Test Coverage Report for Build 57

21 of 21 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 97.329%

Totals

Change from base Build 53:
0.1%

Covered Lines:
1640

Relevant Lines:
1685

💛  - Coveralls

Thank you! ❤ I like this approach. The only slight thing I'm not super keen on is the :base and :override keys. I will have a play and see if we can achieve the desired effect without involving new keys.


Mobile Filesize = Great, Older Mobile Performance = ?

Hi Scott,
1st, thanks for this brilliant script!
2nd, I'm curious how respond.js performs on older mobile phones (infact more so then how it handles ie6-8 ...which I'm sure is very well). Personally I don't own any old mobile phones, nor do I have the resources to get my hands on any.... But I suspect you might.
My scenario is that for browsers that don't natively support media queries they get a "basic.css" stylesheet (ie6-8, older mobiles, etc). Its a single column layout, and desktop browsers will hit a max-width 720px, keeping everything nicely contained for ie6-8. It's less likely that their browser window will be <720px.... So my main target audience for running respond.js is older mobile devices.
Ideally I would like to use media queries in my basic.css, and "cascade" / progressively enhance upwards to a second stylesheet - advanced.css for modern browsers ...
An alternative to respond.js+media queries is to run use JavaScript  to append min-width-x class attributes to the root element... Then use something like .min-width-480 In basic.CSS ... But classes like this don't cascade very well upwards into advanced.CSS - which is given to users with known media query support.
Respond.js's file size & framework independence is perfect. But I wonder how well the performance is on older mobiles ...with ajax getting the css, then js parsing and injecting Dom elements?
Thanks in advance for any insight / feedback you're able to offer.

Hi Chris,
Sorry I never responded to this one - I went on sabbatical last fall and piles of jquery mobile work has kept me from Respond stuff... UNTIL NOW :)
So, I'd say your mobile-first approach is a great first step for older devices, since if the initial HTML and CSS delivery is usable on them, you won't need a JS polyfill for that experience. Some devices could perhaps encounter an error, but I've yet to see that in pretty extensive testing on popular older devices, and even then, it won't be a deal breaker to accessibility.
Thinking further on this though, I think most people use Respond to polyfill IE 6-8, and maybe Windows Phone, and I'm unsure how relevant other non-mq supporting browsers are anymore, particularly with a mobile-first approach. I can think of a few, like Firefox 3, that'd no longer be polyfilled, but they'd still get a usable mobile layout at least. I think I'll pose the question tomorrow on Twitter of whether Respond should be adapted to a purely-IE polyfill, which would mean I could run a conditional comment test to check the browser, instead of running a heavier media query support test. Many other areas could be lighter in weight if a browser-agnostic approach is no longer needed too, and I assume that'd help other low-end devices, if nothing else by lowering code weight further.
Thoughts on that? By the way, I'm going to close this one out, as it's not really an "issue", but thanks for posting nonetheless!

Hi Scott,
No worries about the delayed response (I knew you were on holiday - how creepy is that - thx to twitter).
An IE optimised branch would be interesting - but it would probably anger the masses if the whole project went that way.
I'll let you make the judgement call on whether you want to support/develop it - I'm just thankful for everything you've contributed, and continue to contribute.
Thanks again,
Chris


Updated README

fixes #57

Use right issue number for PR

Send me output here

Issue number is correct
Pics :

.
.

Perfect 👍

Can you add my social media handle like LinkedIn and insta YouTube?

Can you add my social media handle like LinkedIn and insta YouTube?

sure
do send the links here

kindly solve merge conflic

Done , do check it now as I dont know much about resolving conflicts

Bro. kindly send me any screen shot so that I can review it then I will merge your PR


when we scan 50 students for for student data is getting skip in between .

-> when i am scanning 50 students for save marks  and using skip functionality then it is replacing student info with null  .

test result of above bug is:

When we were using skip functionality and skipping every student and when I try to unskip all students only last student data was getting saved . But with above changes suppose we are scanning 4 student sheet it will save all 4 student in db after unskip.
Now after scanning 50 students for save marks and using skip functionality then it is not replacing student info with null .


Text window slider not working on TensorFlow.org Download and Setup page

On TensorFlow.org - Download and Setup page
https://www.tensorflow.org/versions/master/get_started/os_setup.html
Under Pip Installation
For python3:
the text window slider does not allow you to slide to the right.
If works for the text window slider above under Install TensorFlow:
As a work around you can visit the instructions on the GitHub page
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/g3doc/get_started/os_setup.md

It works for me. What browser are you using?

Closing. Please reopen with more information if it persists.


Skin modified problems

Hi i add to skin frosted glass plugin with acrylic effect and skin fix for this effect but now is skin bar and buttons and text more in left. Not look good.

Skin is super THX. Please we can help me with fix this??

I don't have a plan to implement the forested glass plugin to the skin.

It seems that the forested glass plugins does not support the rounded corners on Windows 10.
The NowPlaying Lite skin can be changed background rounded corners radius 0-20, the forested glass plugins can not be changed corners radius.

but now is skin bar and buttons and text more in left.

I will see the code If you share the .zip or .rmskin of the whole skin.

Are you using Windows 11?
There are some kind of frosted glass plugins. Which one do you use?

Could you try this?

Open Skins\NowPlaying Lite\Skin.ini with text editor.
Modify

From:
[Container2]
Meter=Shape
X=(#$M#)R

To:
[Container2]
Meter=Shape
X=(2*#$M#)R

Save file and Refresh skin.

I don't have a plan to implement the forested glass plugin to the skin.
* It seems that the forested glass plugins does not support the rounded corners on Windows 10.

* The **NowPlaying Lite** skin can be changed background rounded corners radius `0-20`, the forested glass plugins can not be changed corners radius.

but now is skin bar and buttons and text more in left.

I will see the code If you could share the .zip or .rmskin of the whole skin files.
* Are you running on Windows 11?

* There are some kind of frosted glass plugins. Which one are you using?

I use win 11 rounded corners support. I use this plugin = https://github.com/KazukiGames82/FrostedGlass

Could you try this?
1. Open `Skins\NowPlaying Lite\Skin.ini` with text editor.

2. Modify

From:
[Container2]
Meter=Shape
X=(#$M#)R

To:
[Container2]
Meter=Shape
X=(2*#$M#)R

3. Save file and Refresh skin.

This not work.

This is full skin
NowPlaying Lite.zip

You have modified Config.inc to use FrostedGlass plugin.
from $M=(Trunc(10*#$#)) to $M=(Trunc(0*#$#)). This will affect whole layout.
$=1.03
;; Border width
$B=(Round(#$#-0.25))
;; Margin - Background
$M=(Trunc(0*#$#))
Hidden=1

Original - Hold Ctrl+Alt and click on the skin to highlight

Your modified

Basically Skin users should not modify the Config.inc and if you will do modify the Config.inc and get problems, you need to solve the problems by your self.
Hint: Find all #$M# in the Skin.ini and adapt to the layout.
If you only need transparent background, you can change tranceparency by Context menu > Styles > Background transparency > 0-100%

You have modified Config.inc to use FrostedGlass plugin. from $M=(Trunc(10*#$#)) to $M=(Trunc(0*#$#)). This will affect whole layout.
$=1.03
;; Border width
$B=(Round(#$#-0.25))
;; Margin - Background
$M=(Trunc(0*#$#))
Hidden=1

Original - Hold Ctrl+Alt and click on the skin to highlight  Your modified
Basically Skin users should not modify the Config.inc and if you will do modify the Config.inc and get problems, you need to solve the problems by your self. Hint: Find all #$M# in the Skin.ini and adapt to the layout.
If you only need transparent background, you can change tranceparency by Context menu > Styles > Background transparency > 0-100%

Hmm sorry i know. I modified to this... But your skin.ini is very complicated write... I not understand as it fix it.

I change $M=(Trunc(0*#$#)) to $M=(Trunc(3.5*#$#))..... Looks better =

You have modified Config.inc to use FrostedGlass plugin. from $M=(Trunc(10*#$#)) to $M=(Trunc(0*#$#)). This will affect whole layout.
$=1.03
;; Border width
$B=(Round(#$#-0.25))
;; Margin - Background
$M=(Trunc(0*#$#))
Hidden=1

Original - Hold Ctrl+Alt and click on the skin to highlight  Your modified
Basically Skin users should not modify the Config.inc and if you will do modify the Config.inc and get problems, you need to solve the problems by your self. Hint: Find all #$M# in the Skin.ini and adapt to the layout.
If you only need transparent background, you can change tranceparency by Context menu > Styles > Background transparency > 0-100%

Hmm sorry i know. I modified to this... But your skin.ini is very complicated write... I not understand as it fix it.

It have only transparent on picture must add measure to main ini =
[FrostedGlass]
Measure = Plugin
Plugin = FrostedGlass
Type = Acrylic
Corner = Round
BlurEnabled = 1
BorderVisible = 0


Autocomplete formcontrol valueChanges fired when user select option

What is the expected behavior?
Autocomplete formcontrol valueChanges should not be fired when user select option
What is the current behavior?
Autocomplete formcontrol valueChanges fired when user select option
What are the steps to reproduce?
Please, look at this (open console): https://stackblitz.com/edit/angular-8zucqs?file=app/autocomplete-display-example.ts
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular - 7.2.0, Material - 7.2.1
Is there anything else we should know?
Bros, i need this functionality.

If you look at an example to autocomplete component, you will see something like this:
constructor() {
    this.filteredStates = this.stateCtrl.valueChanges
      .pipe(
        startWith(''),
        map(state => state ? this._filterStates(state) : this.states.slice())
      );
  }

I'm as a regular developer, think that is a place where I can make a call to API. So I place code into map pipe. If I type something in input, that call will be fired (it is OK), but when I select an option, that call will be fired again (valueChanges). So if it isn't an issue, please, give me example how to avoid it.

When you select option, valueChanges fired with [Object], try filter
constructor() {
    this.filteredStates = this.stateCtrl.valueChanges
      .pipe(
        startWith(''),
        filter(x => typeof x === 'string'),
        map(state => state ? this._filterStates(state) : this.states.slice())
      );
  }

Closing since this works as expected.


limit published artifacts

Hello,
I have recently come across this repository (and related guidesmiths packages) and I am a fan. Thanks for sharing them.
I have noticed that the published package is quite large, and it seems to include some CI/CD files that are probably not required - specifically, a cc-test-reporter file in the root of the package directory. I am aware that there can be different opinions on what exactly should be included in a published package. I personally prefer a minimal approach, but others often like to include more.
Could I propose the use of the files field in your package.json (instead of the deny-listing .npmignore) to ensure that only the intended files make their way in to the published package. I would be happy to open a branch and make a PR, if you give me some guidance on (a) if this proposal is acceptable, and (b) how much you would wish to see included in the (allow-listing) files field.

Hi @adjoinant,
Thanks for taking the time to raise this issue, pointing out the unnecessary files being published to npm, suggesting we use the files field in package.json and the offer of a PR. You are absolutely right about cc-test-reporter - I hadn't spotted that was being included in the package. I will sort it out promptly.
I'm generally reluctant to use files (in this or any other library) as think it's highly likely that at some point we would forget to update it when adding or renaming a file. This could result in a broken package, and a whole lot of problems, more serious that including a surplus.
I'm glad you're enjoying systemic et al.
Best,
Steve

Hi @adjoinant,
Thanks for taking the time to raise this issue, pointing out the unnecessary files being published to npm, suggesting we use the files field in package.json and the offer of a PR. You are absolutely right about cc-test-reporter - I hadn't spotted that was being included in the package. I will sort it out promptly.
I'm generally reluctant to use files (in this or any other library) as think it's highly likely that at some point we would forget to update it when adding or renaming a file. This could result in a broken package, and a whole lot of problems, more serious that including a surplus.
I'm glad you're enjoying systemic et al.
Best,
Steve

Hi @cressie176,
Thanks for the swift response and for sharing your thoughts on files - was a fair and interesting point to consider.
Best,
Adam

Hi @cressie176,
Thanks for the swift response and for sharing your thoughts on files - was a fair and interesting point to consider.
Best,
Adam

Down to 31.8 kB. Thanks once again for reporting. I checked a sample of other GuideSmiths packages and they were OK. I think systemic was different because we'd been experimenting with publishing from travis.

Down to 31.8 kB. Thanks once again for reporting. I checked a sample of other GuideSmiths packages and they were OK. I think systemic was different because we'd been experimenting with publishing from travis.


Allow different versions of Atom to run simultaneously on Win32

Allow side-by-side versions to run rather than whichever version of Atom was launched first ends up opening all subsequent requests.

Looks good to me!

This should at least apply #9247, if not fix it, yes?

Maybe instead :fire: this whole code path and replace it with app.makeSingleInstance instead?

@paulcbetts Does that auto-distinguish between versions and can we also still provide an override? - we do that in specs to allow multiple side-by-side https://github.com/atom/atom/blob/720ad9c0b4b46e5e10b6d2381f150d23cf775433/spec/integration/helpers/start-atom.coffee#L14
@lee-dohm Would we be okay with deprecating the socket-path command line option?

@damieng It distinguishes via the path to the executable so it should Just Work. You can always choose not to call it in certain circumstances too (you definitely should not call it in the Squirrel event handler for example)

@lee-dohm It doesn't completely solve that issue - we still need the shell integration options to honor atombeta.exe but that will happen as part of moving the shell options into settings.

While I agree that long-term we should switch to the electron version that's more time and consideration than I have right now and this unblocks the current desired scenarios so I'm going to go ahead and merge unless I see an objection.


Emmet 'Go to matching pair' doesn't work

I updated to VS Code 1.17.2 and now Emmet 'Go to matching pair' command doesn't work at all (before this update it worked). Today is Oct 25 2017

Just checked in VS Code 1.17.2 in Windows
The command works just fine.
There has been no changes to this part of the code in over 4 months.
Did it work as expected in 1.16, 1.17.0, 1.17.1 ?
Are you trying it on an HTML file or any other file type?
Any errors pop up?
Can you try on a simple/small HTML file?
Share your sample code where you see the issue

I'm having a similar issue, I'm not sure if it's a misunderstanding on my part of the command or unexpected behavior.
I attached a file that the issue is present for me. I can use the command just fine on regular html, but if I'm working on a template the command doesn't do anything. Replacing the "script" tags with "body" makes it work fine, so it might just be something with how Emmet sees tags.
test.zip

@GammaGames thanks for the sample code. I get a repro. The issue seems to occur inside script tags only.
@Dagge1 @Bushrut can you confirm that you see the issue inside script tags as well? Or do you see it in any other tags?
The root cause seems to be that the Emmet parser I am using ignores the contents of script and style tags assuming the contents arent html.
I have logged an upstream issue for this: https://github.com/emmetio/html-matcher/issues/2
@GammaGames A suggestion: The sample code you share was just a few lines, could you please just paste the code in the comments instead of zipping it next time? Saves us (and am sure you as well) some time :)

@ramya-rao-a I restarted PC and now it works inside .html file, I do not reason why it didn't work before. But it doesn't work inside

@Dagge1 Thanks for confirming that the issue is indeed inside the script tags
By php tag you mean <?php? Then the answer is no.

Has there been any activity around this lately? I experience the same issue inside of script tags.

@bwasilewski I don't see the upstream issue getting fixed anytime soon, but we can definitely attempt to fix this from our end by re-parsing the contents of the script tag.
PRs are very much welcome.

Location where we should determine whether or not re-parsing is needed is here based on the current node
Example of how we re-parse an already parsed node is here
Whitelist of types that a script tag should have to be considered as html content is here

cc @JacksonKearl https://docs.emmet.io/actions/go-to-pair/ describes the feature being discussed in this issue.
The bug is described in https://github.com/Microsoft/vscode/issues/36905#issuecomment-340481398
And pointers for the bug fix are in https://github.com/Microsoft/vscode/issues/36905#issuecomment-386906618


Have ballerina error values to represent client errors from different API

Description:
From different third party APIs, we will get multiple error values as below. Need to have ballerina error values to represent client errors.
Eg:
"errors": [
{
"reason": string,
"location": string,
"debugInfo": string,
"message": string
}
]
Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

@rdhananjaya / @hasithaa As per the discussion in https://github.com/wso2-ballerina/module-bigquery/pull/3#discussion_r264565147 it seems this is a compiler side improvement. Do we have that support now?

Error design has changed and I don't think this is applicable anymore. Hence, closing this issue.


Depreciation of 'Get All Users in Organization'

The getUsersREST page documents that this mechanism will be depreciated, yet there is no known date, and no documented API alternate to get the Adobe ID of a user.
What is the state of this API?

The alternative APIs are:
Get a single user: https://adobe-apiplatform.github.io/umapi-documentation/en/api/getUser.html
Get Users: https://adobe-apiplatform.github.io/umapi-documentation/en/api/getUsersWithPage.html
The getUsersREST API is still available but not actively maintained.


Proposal: Change declaration of RangeQuery

Problem Description
RangeQuery is currently declared as:
/** @codegen_names date, number, terms */
// Note: deserialization depends on value types
export type RangeQuery = DateRangeQuery | NumberRangeQuery | TermsRangeQuery

This declaration is highly problematic for statically typed clients as there is no way to correctly deserialize into the correct union variant, because for example the following variants share the same underlying JSON type:
export class TermsRangeQuery extends RangeQueryBase {
  gt?: string

export class DateRangeQuery extends RangeQueryBase {
  gt?: DateMath // string

Proposal
It seems like on server side, there is only one RangeQuery with an object/any type and the actual semantics are applied on base of the type mappings.
It would make sense to reflect this in our specification while still providing hints about potential specializations to the code generator.
The naiv approach would be to change the specification like this:
export class RangeQuery extends RangeQueryBase {
  gt?: any
  // ...
}

This would allow serialization and de-serialization of arbitrary value types. However, this would as well complicate building queries in statically typed languages.
A better way could be a construct like this:
export type RangeQuery = GenericRangeQuery<any>;

export class GenericRangeQuery<T> extends RangeQueryBase {
  gt?: T
   // ...
}

Potentially with new annotations:
@known_generic = [DateMath, "DateRangeQuery" ]
@known_generic = [double  , "NumberRangeQuery"]
@known_generic = [string  , "TermRangeQuery"  ]
export type RangeQuery = GenericRangeQuery<any>;

Based on this, generators could generate specialized code only for serialization (deserialization always uses DateRange<any>):
// Untyped/any variant always used for deserialization; can optionally be used by the user when building queries
public class RangeQuery
{
	public object? Gt { get; set; }
}

public abstract class GenericRangeQuery<T> : RangeQuery
{
	public new T? Gt { get; set; }
}

// Specialized range query for numbers
public sealed class NumberRangeQuery : GenericRangeQuery<double>
{
}

// Specialized range query for dates
public sealed class DateRangeQuery : GenericRangeQuery<DateMath>
{
}

Side Notes
There are more types for which the same issue applies, for example:
/** @codegen_names date, numeric, geo */
// Note: deserialization depends on value types
export type DecayFunction =
  | DateDecayFunction
  | NumericDecayFunction
  | GeoDecayFunction

/** @codegen_names geo, date */
// Note: deserialization depends on value types
export type DistanceFeatureQuery =
  | GeoDistanceFeatureQuery
  | DateDistanceFeatureQuery

cc @elastic/clients-team @swallez @technige

It seems like on server side, there is only one RangeQuery with an object/any type and the actual semantics are applied on base of the type mappings.

That's correct: this is a mappings-aware deserialization. Something we definitely cannot to client-side. RangeQuery, as it is defined, is indeed serializable but not deserializable. This was deemed acceptable since it's only found in requests and not in responses (at least when it was introduced).
However, the Java client ended up simplifying it by replacing it with the definition of DateRangeQuery with DateMath types replaced with UserDefinedValue (i.e. the equivalent of GenericRangeQuery<UserDefinedValue>)
DateRangeQuery was chosen as the blueprint because it has additional format and timezone fields that are not found in other variants. So the GenericRangeQuery would need to have those.
That being said, I don't see how the new annotation solve the issue, since deserialization is still impossible. I may be missing something.

The idea is to implement asymmetric (de-)serialization.
RangeQuery would always be used for deserialization. The user would have to perform type checks on the any/object fields to work with the data. The deserialized object would however still be round-trippable, which is a huge bonus.
The specialized variants are never used for deserialization. They are only meant to simplify serialization/query building. Instead of RangeQuery, the user could pass RangeQuery and work with the DateMath fields in a native way instead of having to deal with any/object.

I created a draft PR that, for now, keeps the current declarations, but slightly rearranges them to always follow this pattern for these kind of untagged unions:
export class MyTypeBase<T1, T2, ...> { ... }

export class MyTypeSpecialized1 extends MyTypeBase<int> {}
export class MyTypeSpecialized2 extends MyTypeBase<int> {}
export class MyTypeSpecialized3 extends MyTypeBase<int> {}

/** @codegen_names 1, 2, 3*/
// Note: deserialization depends on value types
export type RangeQuery = MyTypeSpecialized1 | MyTypeSpecialized2 | MyTypeSpecialized3

It already was like this for DistanceFeatureQuery, but not for RangeQuery and DecayFunction.

I think this is still not perfect as we declare artificial types in the specification that do not really exist on server-side. The annotation based solution is preferrable imo, but for the time being, this change at least allows code generators to detect this specific pattern and drive specialized code generation.

We decided to go with the solution I provided in #2548 with a small addition of adding a new variant type untagged for these kinds of unions to:

Make this case easier detectable by the code generators
To make this construct more explicit for new contributors
To be able to add a compiler validation of the pattern based on the presence of this new variant decorator (later)

This has been implemented in #7428


What are the Differences to a shipped DIO-Firmware?

Does my DIO module behave exactly the same with the custom compiled firmware as with the shipped firmware?
How about any bootloader? Are the modules shipped with a bootloader which can accept a new firmware directly from the Revpi Core via the RS485? If so, is this bootloader included in this repo?

Hi Karl,
source code is the same as the one we use in the shipped module. But your guess is correct. The code for the firmware update is missing.

@mduckeck So if I flash this slef compiled firmware into my DIO module, it will behave identical?
What about the serial number?

Yes, it should have the same behaviour.
There is a global variable ctKunbusFirmwareSecriptor_g in the File FW_Desc.c. The second value is the serial number (0xffffffff).


Failed to login with 2FA GA

Description
I'm failed to login to my account via
instascrape login

    Saved Cookies

(1) + [Login New Account]

(1-1)choice> 1
Username: $USER
Password:
[2FA] Security Code: 711389
✖ HTTPError: 400 Client Error: Bad Request for url: https://i.instagram.com/api/v1/users/1382407697/info/

I'm using Google Authenticator for 2FA codes.
There is following content at https://i.instagram.com/api/v1/users/1382407697/info/
{
"message": "useragent mismatch",
"status": "fail"
}

Information

OS: Mageia 6 (Linux)
Version of instascrape: v2.0.1

Here is the solution: https://mpsocial.com/t/any-api-end-point-to-request-user-info-by-ig-id/86705

This bug's already been fixed in<PHONE_NUMBER>da0c93af8ce1440b1b91dd2f1378a8. It will be included in the next release.
For now, you can install the latest commit of instascrape using pip.
$ pip install git+https://github.com/a1phat0ny/instascrape.git@master


Documenting OrthographicProjection.

Objective
Documentation for OrthographicProjection is something that is often asked for implicitly in the #help channel on Discord. More explicitly, we now have #5818 , which this PR aims to fix.
Solution
Provided explanation for what left/right/top/bottom are, and in what units they are given. Also provided explanations for concepts like "field of view", "scale" and "window".

@superdump ping as you've requested, for rendering related docs 😄

@alice-i-cecile This PR has been inactive so I've started another and applied most changes suggested here.

Closing in favor of #6177.


DOF - Implementation of dbt models

[x] Overlapping footprints #175 #178 #190
[ ] Data updates that preserve historical ones
[x] Data enrichment (joins to other datasets) #168 #182 #189

@britt-allen can you link the relevant issues to this?

Closing as complete, updates incorporating historical edits will be handled using a local workflow


BUG - second manual process run freezes the async app.serve()

Describe the bug
When Rocketry works in async fashion through app.serve(), it becomes frozen when specific manual-run task sequence is executed.
Task sequence:
run_me_madam starts on async
run_me_madam finishes
run_me_sir starts on process (not async)
app.serve() becomes frozen
To Reproduce
For reproducing the bug I will paste code at the bottom of issue and will pinpoint commit, after which the aforementioned bug arose.
Expected behavior
starting manually a task after one has finished, should not freeze the async Rocketry.serve(). In this case it is expected to see run_me_sir finish.
Screenshots
When trying to KeyboardInterrupt the frozen async Rocketry.serve(), such error always appears:

Desktop (please complete the following information):

OS: Windows 10 Home
Python version 3.10.4
On Rocketry v2.4.1 bug does not exist.
On Rocketry v2.5.0, v2.5.1 and latest codebase bug does exist
Specific commit, that introduces the bug: pip install git+https://github.com/Miksus/rocketry.git@c9480a9c847704a0a57b4c6770eeb1028bf029a0

Additional context
Here I paste the code.
from time import sleep
import asyncio

from rocketry import Rocketry

# #
# Rocketry app
app = Rocketry(
    config={
        "execution": "async",
        "max_process_count": 100,
    }
)

# #
# tasks
@app.task("every 10 seconds")
async def mark_10_seconds():
    print("10 seconds have passed")

@app.task(execution="async")
async def run_me_madam():
    print("Madam, I am going to sleep for 2 seconds")
    sleep(2)
    print("Madam, I am done with sleeping")

@app.task(execution="process")
async def run_me_sir():
    print(f"Sir, I am going to sleep for 2 seconds.")
    sleep(2)
    print("Sir, I am done with sleeping")

if __name__ == "__main__":

    async def task_manual_run_flow():
        await asyncio.sleep(3)
        print(
            "will run run_me_madam task - on async (or even if on process, result would be the same)"
        )
        app.session["run_me_madam"].run()
        await asyncio.sleep(10)
        print("madam task should be done by now")
        print("will run run_me_sir - on process")
        app.session["run_me_sir"].run()
        print("doing await asyncio.sleep(5). If it takes forever, you are stuck here.")
        await asyncio.sleep(5)
        print(
            "launched run me sir through session. If you do not see this message, it means that app.serve() never returned control via await."
        )

    async def main_main():
        return await asyncio.gather(app.serve(), task_manual_run_flow())

    asyncio.run(main_main())

I hope I have collected enough information to be of help 🤝


Json serialization fixes

This branch fixes serialization issues that cause stetho to die when we try to send back NaN, Infinity or -Infinity. These values are not part of the JSON specification. What this patch does is to serialize them as String since JavaScript will accept them back as Doubles.

only a minor comment, looks good otherwise


Test CI fail with pytest==8.1.0

Description
Since pytest==8.1.0, the test CI fails; only the plotting tests seem to be affected.

@michalk8, I pinned the pytest as a quick fix.


Added 100 licenses limit to teams-exploratory.md

Closes https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/6264.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@dstrome PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


[3.4.0] Reports warnings about default exports

What is the current behavior?
Since updating to<EMAIL_ADDRESS>the compiler shows warnings about export 'default'.
If the current behavior is a bug, please provide the steps to reproduce.
import Vue from 'vue'
import VueRouter from 'vue-router'
import Vuex from 'vuex'
import Vuetify from 'vuetify'

What is the expected behavior?
No warnings.
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
WARNING in ./src/main.ts
18:8-17 "export 'default' (imported as 'VueRouter') was not found in 'vue-router'

WARNING in ./src/main.ts
19:8-12 "export 'default' (imported as 'Vuex') was not found in 'vuex'

WARNING in ./src/router.ts
42:24-33 "export 'default' (imported as 'VueRouter') was not found in 'vue-router'

WARNING in ./src/services/store.ts
8:23-27 "export 'default' (imported as 'Vuex') was not found in 'vuex'
webpack: Compiled with warnings.

Tried setting
devServer: {
	clientLogLevel: 'error',
},

but still reported these warnings.
vuejs.org#Recommended-Configuration

i'm seeing this too. It only happens to me on rebuilds though (with webpack-dev-server). not the initial one. it first started when i went from webpack 3.3 to 3.4. everything still works, but i get lots of warnings. it's not just default exports though. "export 'connect' was not found in 'react-redux'

I'm seeing it in 3.4.0 only on rebuilds as well with webpack-dev-middleware.  If I have babel transpile the es6 modules by disabling the modules: false directive then I don't see the warnings with 3.4.0 (but obviously that prevents tree shaking).

fixed in 3.4.1

Thanks for fixing that so quickly!


Update for new challenge

https://github.com/Anorov/cloudflare-scrape/issues/193

Unfortunately i won't be able to release a new version earlier than in 10 hours.

@pro-src and of course thank you for the pull request :) !

Done. 3.1.0 was released


ENH: Introduce from npreadtext import monkeypatch_numpy

This allows:
from npreadtext import monkeypatch_numpy

printing out a warning and then replacing loadtxt in NumPy with our version.  It also does some smaller fixups first (and two small bug-fixes, grrr).

Lets put this in, so people can try ASAP we can always fix it up.

@rossbar we have to remember to update the README before we do the proper announcement also.  (one thing to remember, is that this is right now not quite meant for production, since it is meant to test inclusion into NumPy, e.g. I use a private loadtxt helper functions directly from NumPy.)


lntest/itest: update error whitelist

Add outstanding error whitelist entries.

It will be retried, and therefore it is benign?

It will be retried, and therefore it is benign?

@halseth that's my guess, tho i didn't investigate further


Page is rendered as a component: > details

It is possible for a page to be rendered as a component.
This give incorrect render of the page. And it confused the person editing content.
Previewing [/new-platform-page]...
Is renderable request for: new-platform-page
Accessing dynamic component at: new-platform-page
Previewing [/new-platform-page]...
Accessing static page (preview) at: new-platform-page
Is renderable request for: new-platform-page
{
    "type": "app:landing-page",
    "path": "new-platform-page",
    "requestType": "component",
    "renderMode": "edit",
    "canRender": true,
    "catchAll": false,
    "apiUrl": "http://localhost:8080/site/web/draft",
    "baseUrl": "/admin/site/inline/web/draft/homepage/",
    "requestedComponent": {
        "fragment": null,
        "type": "part",
        "path": "/main/0/top/1",
        "page": null,
        "layout": null,
        "text": null,
        "part": {
            "descriptor": "app:feature-box",
            "config": {
                "image": null,
                "text": null,
                "alignment": "right",
                "border": null,
                "docked": null
            }
        },
        "image": null
    }
}
Warning: data for page "/[[...contentPath]]" (path "/new-platform-page") is 138 kB which exceeds the threshold of 128 kB, this amount of data can reduce performance.
See more info here: https://nextjs.org/docs/messages/large-page-data
Warning: data for page "/_component" (path "/_component?contentPath=new-platform-page") is 138 kB which exceeds the threshold of 128 kB, this amount of data can reduce performance.
See more info here: https://nextjs.org/docs/messages/large-page-data

Couldn't reproduce it, so it was either fixed or needs special conditions to trigger.


XML Variable Substitution removes comments

File Transform task after doing an xml variable substitution it removes the comments from the original file, is there a way to escape this?

Thanks for reporting. Fixed as per attached PR #11224

Thanks for bringing this up. We are working on the fix. Will update the thread once fix is available.


publish aug 1 release

@rloutlaw,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/index.yml
:white_check_mark:Succeeded

docs-ref-conceptual/node-azure-tools.md
:white_check_mark:Succeeded

docs-ref-services/authorization.md
:white_check_mark:Succeeded

docs-ref-services/monitor.md
:white_check_mark:Succeeded

docs-ref-services/service-bus.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Failure iam.amazonaws.com

Hello ,
tried the cloudmapper already with different Linux distributions but get everytime
Failures:
iam.get_account_authorization_details({}): Connection was closed before we received a valid response from endpoint URL: "https://iam.amazonaws.com/".
root@2a04454fd49a:/opt/cloudmapper#
==>Found the solution. The permission mentioned are not enough.

if I try the report anyway afterwards I get:
root@2a04454fd49a:/opt/cloudmapper# python cloudmapper.py report --account Training

Getting resource counts

Training

Getting IAM data

Training
Traceback (most recent call last):
File "cloudmapper.py", line 72, in
main()
File "cloudmapper.py", line 66, in main
commands[command].run(arguments)
File "/opt/cloudmapper/commands/report.py", line 471, in run
report(accounts, config, args)
File "/opt/cloudmapper/commands/report.py", line 228, in report
account_stats = get_access_advisor_active_counts(account, args.max_age)
File "/opt/cloudmapper/shared/common.py", line 378, in get_access_advisor_active_counts
*json_account_auth_details["UserDetailList"],
KeyError: 'UserDetailList'
root@2a04454fd49a:/opt/cloudmapper#

For the first issue, it looks like your internet connection was broken.
For the second issue, nothing will work if you can't get the IAM data.


Quicksilver 1.5.6 Crashes Immediately When Clicking "Triggers" Pane in Preferences

Ever since I upgraded to High Sierra 10.13, Quicksilver is crashing as soon as I click the "Triggers" preferences pane. See full crash log in attachment.
Application Specific Information:
abort() called
*** error for object 0x604000207d50: pointer being realloc'd was not allocated

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff55b7dfce __pthread_kill + 10
1   libsystem_pthread.dylib       	0x00007fff55cbb150 pthread_kill + 333
2   libsystem_c.dylib             	0x00007fff55ada32a abort + 127
3   libsystem_malloc.dylib        	0x00007fff55bd8909 realloc + 410
4   com.apple.ImageIO.framework   	0x00007fff30de8178 ICNSReadPlugin::GetGlobalICNSInfo(IIOImageReadSession*) + 556
5   com.apple.ImageIO.framework   	0x00007fff30de7684 ICNSReadPlugin::decode(unsigned char*, unsigned long) + 214
6   com.apple.ImageIO.framework   	0x00007fff30de8473 ICNSReadPlugin::copyImageBlockSet(InfoRec*, CGImageProvider*, CGRect, CGSize, __CFDictionary const*) + 485
7   com.apple.ImageIO.framework   	0x00007fff30de7581 ICNSReadPlugin::CopyImageBlockSetProc(void*, CGImageProvider*, CGRect, CGSize, __CFDictionary const*) + 85
8   com.apple.ImageIO.framework   	0x00007fff30d64711 IIOImageProviderInfo::copyImageBlockSetWithOptions(CGImageProvider*, CGRect, CGSize, __CFDictionary const*) + 361
9   com.apple.ImageIO.framework   	0x00007fff30d62535 IIOImageProviderInfo::CopyImageBlockSetWithOptions(void*, CGImageProvider*, CGRect, CGSize, __CFDictionary const*) + 663
10  com.apple.CoreGraphics        	0x00007fff2e8ff007 CGImageProviderCopyImageBlockSetWithOptions + 137
11  com.apple.CoreGraphics        	0x00007fff2e900483 CGImageProviderCopyImageBlockSet + 196
12  com.apple.CoreGraphics        	0x00007fff2e921c42 img_blocks_create + 333
13  com.apple.CoreGraphics        	0x00007fff2e921acc img_blocks_extent + 98
14  com.apple.CoreGraphics        	0x00007fff2e904fc9 img_data_lock + 9031
15  com.apple.CoreGraphics        	0x00007fff2e901705 CGSImageDataLock + 230
16  com.apple.CoreGraphics        	0x00007fff2e9d1da0 RIPImageDataInitializeShared + 88
17  com.apple.CoreGraphics        	0x00007fff2e9b6da1 RIPImageCacheGetRetained + 674
18  com.apple.CoreGraphics        	0x00007fff2e9d1e9e ripc_AcquireRIPImageData + 207
19  com.apple.CoreGraphics        	0x00007fff2e9dedc0 ripc_DrawImage + 753
20  com.apple.CoreGraphics        	0x00007fff2e948a30 CGContextDelegateDrawImage + 41
21  com.apple.CoreGraphics        	0x00007fff2e900d0b CGContextDrawImageWithOptions + 544
22  com.apple.CoreGraphics        	0x00007fff2e900ad1 CGContextDrawImage + 51
...

Quicksilver_2017-09-29-171748_iMac-2.crash.txt

Sorry, looks like a duplicate of #2396 which was just filed a few days ago. Feel free to mark this as such.

It could be related to the new windowing system, but I haven’t seen any issues. The original title of your report makes more sense, at least if you were trying to view recent documents for an application via right-arrow.

This appears to be an issue with drawing the icons for one of your triggers, potentially the 'recent documents' object as skufer mentioned.
I will close this now due to inactivity.  However, if you're still facing an issue with the latest version of Quicksilver, please create a new issue.
Thanks!


HDDS-9336. OMKeyDeleteRequest Remove redundant code

What changes were proposed in this pull request?
OMKeyDeleteRequest Remove redundant code
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-9336
How was this patch tested?
existing UT

Thanks @guohao-rosicky for the cleanup, @sodonnel for the review.


Disable/enable a Job

I see that a Job struct has a disable status. What do you do to change the disable status after job creation? Regards.

Haha, never realized these endpoints were not documented! Sorry about that @dzakaammar
As you can see here, all you have to do is sent a POST request to either: /api/v1/job/disable/{id} or /api/v1/job/enable/{id} where {id} is the Job ID of the Job you want to disable or enable. That will disable or enable that job.

Haha, no problem. Big thanks!


Build UPG as an external VPP plugin

[x] use vpp-base image as the base for docker images
[x] produce dev-debug and dev-release images along with debug and release images
[x] produce deb artifacts along with the images
[x] enable interrupt-driven mode for e2e tests to reduce flakes
[x] check that the release mechanism is not broken in CI

After this PR the main README.md/Documentation has become completely outdated as most of the targets in the makefile do not exist anymore. vpp-base docker image is behind an authenticated harbor registry, it's not clear if that one is plain upstream or if still relies on patches (nor the respective upstream required version).


complete new IRC connection

It's almost done, still need to implement basic support for ping and irc number commands (nick taken etc)

Closed by #63


Content: instructions for app use

@mburridge has indicated

Might be worth adding some simple instructions for use. I think Android prompts the user to install the app to the home screen (not sure, I'm not an Android user) but iOS makes you jump through a couple of hoops I think.
It's also worth adding that only very recent versions of iOS support PWA technologies.

Please provide us with a complete text to be included in our blog announcement. thnx!

Hi @jennybeaumont, is this task for us?

@rmartinezduque Yes please. If you could provide indications on how we could announce the app, that would be perfect. The above quote was for a standard app, but if you know of any limitations/strange behaviour in Android or iOS (in one or the other version) or if you have minimum requirements (like Android or iOS version) please let us know. Of course any other text on how to promote the app is also welcome.
Thanks.

If I could get this by today end of day, that would be much appreciated!

I'll tag this for us (dev-team). @rmartinezduque could please take care of it?

Sure, I'll work on this today :)

Any progress? :)

Hi @jennybeaumont, yes, sorry! Here you have some instructions for use and other information you can use to announce the app if you wish. Hope it helps. Please let me know if you need anything else.
What is WordCamp Europe’s Progressive Web App?
The official WordCamp Europe’s Progressive Web App (PWA from now on) is an app-like mobile web (https://app.wp-europe.org/) that can be accessed instantly from a mobile browser. It delivers the same native experience than a mobile app without the hassle of installing it, just using the web (a URL).
The PWA provides practical information about WordCamp Europe 2018. More specifically, it contains:

Schedules (On now, up next and full schedule with all sessions per track)
Information on sessions (including time and location)
Information on speakers
Venue maps
Announcements
Lunch menus
Code of conduct
Other useful information about Contributor Day, After Party, etc.

Minimum requirements

Android: Chrome 40+ or above
iOS: Safari 9.0 or above

Features:

Instant loading: the PWA is designed to load nearly instantly and reliably, even if attendees are under uncertain network conditions.

Security: this PWA is served over HTTPS, a secure connection that protects sensitive information. This way the user and the session do not get exposed to attacks and vulnerabilities.

Favorites: the attendees can use the Favorites feature to add stars to all talks of their interest or the ones that they plan to attend (look out for the ⭐ icon). Marked talks will automatically appear under the “Only favorites” option in Full schedule.

Push notifications: these are instant messages that pop up on the attendee’s device (if he/she has explicitly opted in to receive them). They are sent with the sole objective of keeping attendees notified of updates and important notices.

On iOS, this feature is only available for 11.3 version or above.

Offline support: this PWA is aimed to be reliable if the network fails. This means that if attendees temporarily lose their connection, they will not be interrupted while using the app and will continue accessing the site offline. They may not see the newest data but a stored version instead.

On iOS, this feature is only available for 11.3 version or above.

Add to Home Screen: when attendees visit the PWA, they will have the choice to add it to their home screen. This feature helps them save the PWA for instant access and start using it regularly without running out of device space. If no “Add to home screen” popup shows up, attendees can refer to the instructions below.

Instructions for app use
The PWA can be directly opened by accessing the page URL https://app.wp-europe.org/ on a mobile browser, just like any other mobile website.
In order to add the PWA to the home screen, please follow these instructions:
Android (Chrome)
Step 1. Open website (app.wp-europe.org) in Chrome for Android and tap the Menu button.
Step 2. Tap Add to Home Screen option

Step 3. Rename the button (optional) and tap Add

iOS (Safari)
Step 1. Open website (app.wp-europe.org) in Safari and tap the Action button.

Step 2. Tap Add to Home Screen button

Step 3. Rename the button (optional) and tap Add or Done

This is amazing, thank you! (going to leave this open until tomorrow when we finalize the post, cheers!)

@jennybeaumont please note that Offline support is not ready yet but I'll work on it next week to make sure it is available before the event. The rest of the features are already in place.

I got everything I needed here - will refer back for the attendee email going out June 11, but have copied the link so closing this out! :)

This is the updated text of the Push Notifications:

Push notifications: these are instant messages that pop up on the attendee’s device (if he/she has explicitly opted in to receive them). They are sent with the sole objective of keeping attendees notified of updates and important notices. On iOS, this feature is not available.


[SPARK-30459][SQL] Fix ignoreMissingFiles/ignoreCorruptFiles in DSv2

What changes were proposed in this pull request?

Fix ignoreMissingFiles/ignoreCorruptFiles in DSv2:
When FilePartitionReader finds a missing or corrupt file, it should just skip and continue to read next file rather than stop with current behavior.
Why are the changes needed?

ignoreMissingFiles/ignoreCorruptFiles in DSv2 is wrong comparing to DSv1.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Updated existed test for ignoreMissingFiles. Note I didn't update tests for ignoreCorruptFiles, because  there're various datasources has tests for ignoreCorruptFiles. So I'm not sure if it's worth to touch all those tests since the basic logic of ignoreCorruptFiles should be same with ignoreMissingFiles.

Test build #116314 has started for PR 27136 at commit 2bf1992.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/21106/
Test PASSed.

cc @cloud-fan @gengliangwang

Test build #116314 has finished for PR 27136 at commit 2bf1992.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/116314/
Test PASSed.

Hi @Ngone51 ,
Thanks for the fix!
I think the PR only fixes the option ignoreMissingFiles. Could you update the PR/Jira title?

I think the PR only fixes the option ignoreMissingFiles.

I think I fixed both. Do I miss something? Please point it out so that I can fix them together.

I think I fixed both. Do I miss something? Please point it out so that I can fix them together.

Oh, I missed one branch. You are right.

Test build #116338 has started for PR 27136 at commit afef6ad.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/21129/
Test PASSed.

Test build #116338 has finished for PR 27136 at commit afef6ad.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/116338/
Test FAILed.

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/21150/
Test PASSed.

Test build #116360 has started for PR 27136 at commit afef6ad.

Test build #116360 has finished for PR 27136 at commit afef6ad.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/116360/
Test FAILed.

retest this please

Test build #116368 has started for PR 27136 at commit afef6ad.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/21158/
Test PASSed.

Test build #116368 has finished for PR 27136 at commit afef6ad.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

retest this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/116368/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/21183/
Test PASSed.

Test build #116392 has started for PR 27136 at commit afef6ad.

Test build #116392 has finished for PR 27136 at commit afef6ad.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/116392/
Test FAILed.

retest this please

Test build #116400 has started for PR 27136 at commit afef6ad.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/21191/
Test PASSed.

Test build #116400 has finished for PR 27136 at commit afef6ad.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/116400/
Test PASSed.

Thanks, merging to master.

Thank you all!

Thanks a lot!


EOF Troubleshooting Tips Not Working

Error Message
 Expected a top-level item to end with a new line, comment or EOF, but got '-' instead.
Version
Hugo Static Site Generator v0.14 BuildDate: 2015-05-26T01:29:16Z
Notepad ++ showing EOF's
https://imgur.com/a/iq47xLW
Relevant STRACE error
open("/var/www/html/dirtysj/archetypes/default.md", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0777, st_size=105, ...}) = 0
read(3, "+++\ntitle = \"{{ replace .Transla"..., 617) = 105
read(3, "", 512)                        = 0
close(3)                                = 0
write(1, "ERROR: 2018/07/03 Near line 2 (l"..., 139ERROR: 2018/07/03 Near line 2 (last key parsed ''): Expected a top-level item to end with a new line, comment or EOF, but got '-' instead.
) = 139

archetype/default.md
+++
title = "{{ replace .TranslationBaseName "-" " " | title }}"
date = {{ .Date }}
draft = true
+++

v0.14 might be a bit outdated. Can you upgrade to the latest release (v0.42.2)?
I am also not sure if template functions work inside Front Matter.

Your suggestion worked!
I was following this tutorial from DigitalOcean
The line in question was wget https://github.com/spf13/hugo/releases/download/v0.14/hugo_0.14_amd64.deb
I had to uninstall and reinstall Hugo by doing the following
Uninstall
sudo apt-get remove hugo
sudo apt-get remove --auto-remove hugo
sudo apt-get purge hugo
sudo apt-get purge --auto-remove hugo
Reinstall Latest Version
 sudo wget https://github.com/gohugoio/hugo/releases/download/v0.42.2/hugo_0.42.2_Linux-64bit.deb
 sudo dpkg -i hugo_0.42.2_Linux-64bit.deb

Glad I could help!


The default value of delegatesFocus is not very reasonable

https://github.com/alex-vukov/css-boundary/blob/5e0109e72bef183f0657d69360df8b0d25b9f76c/src/styleLoader.ts#L12
The option delegatesFocus is set to true that the user cannot select text.
check the follow example https://codepen.io/liamdebeasi/pen/xxYMvLB
Maybe we can make users customize this option.
createShadowInstance(parentElementId: string, options: { delegatesFocus: boolean  })

Thank you for your feedback and for the example! I am able to select the text but I agree that delegatesFocus should be configurable and should not have true as a default value. I will prepare a new version with this change and I will close the issue when it's released.

Is there any progress?

Yes! I just pushed a fix in version 1.0.2 and it is released. The default value of delegatesFocus will be false. You can also now pass an optional init object to override this if you need to. I also updated the Readme with this information!


JWT_SESSION_FIELD and subscriptions

Setting JWT_SESSION_FIELD for example to /username causes requests to /_rig/v1/connection/ws/xxx/subscriptions to 500
In the logs the crash happens for this
Request: PUT /_rig/v1/connection/ws/xxx/subscriptions
** (exit) an exception was raised:
    ** (Protocol.UndefinedError) protocol Enumerable not implemented for {:ok, %{"email" =><EMAIL_ADDRESS>"exp" =><PHONE_NUMBER>, "fullname" => "TEST FULL", "iat" =><PHONE_NUMBER>, "name" => "John Doe", "sub" => "1234567890", "username" => "testusername"}}. This protocol is implemented for: Date.Range, File.Stream, Function, GenEvent.Stream, HashDict, HashSet, IO.Stream, List, Map, MapSet, Range, Stream, Timex.Interval
        (elixir) /usr/local/src/elixir/lib/elixir/lib/enum.ex:1: Enumerable.impl_for!/1
        (elixir) /usr/local/src/elixir/lib/elixir/lib/enum.ex:141: Enumerable.reduce/3
        (elixir) lib/enum.ex:2979: Enum.reduce/3
        (elixir) lib/enum.ex:1925: Enum."-reduce/3-lists^foldl/2-0-"/3
        (rig_auth) lib/rig_auth/session.ex:43: RigAuth.Session.do_update/3
        (rig_inbound_gateway) lib/rig_inbound_gateway_web/v1/subscription_controller.ex:72: RigInboundGatewayWeb.V1.SubscriptionController.set_subscriptions/2
        (rig_inbound_gateway) lib/rig_inbound_gateway_web/v1/subscription_controller.ex:1: RigInboundGatewayWeb.V1.SubscriptionController.action/2
        (rig_inbound_gateway) lib/rig_inbound_gateway_web/v1/subscription_controller.ex:1: RigInboundGatewayWeb.V1.SubscriptionController.phoenix_controller_pipeline/2
pid=<0.2328.0>

I have tried different fields inside the jwt, and using an extractor to try and get the field, but nothing has worked.
Im using docker run -p 4000:4000 -p 4010:4010 -e SUBSCRIPTION_CHECK=jwt_validation -e JWT_SESSION_FIELD=username -e JWT_SECRET_KEY=secrettoken -e HTTPS_CERTFILE=cert/selfsigned.pem -e HTTPS_KEYFILE=cert/selfsigned_key.pem accenture/reactive-interaction-gateway:2.0.2 to start the service
I am able to call subscriptions successfully without the JWT_SESSION_FIELD, but as soon as i add it, they start crashing.

Thanks for reporting - I'll take a look at this as soon as possible.

I've prepared a fix for this, but I'm waiting for #166 to land in master first. The fix will most likely get published with the next (bugfix) release within the next two weeks.
Regarding your example, please make sure to pass a JSON pointer rather than a field name - from the docs:

The JWT_SESSION_FIELD is specified using the JSON Pointer notation. Given that the JWT contains a user ID in its "userId" field, the configuration could look like this: JWT_SESSION_FIELD=/userId.

@OverFlow636 should be fixed with the latest Docker image. Can you confirm?

@kevinbader when trying the latest update i ran into an issue where the old environment variables i was using to start the service are now crashing it (https certfile and keyfile)
When i run the following it crashes, however removing the HTTPS env vars allows it to run now
docker run -p 4000:4000 -p 4010:4010 -e SUBSCRIPTION_CHECK=jwt_validation -e JWT_SESSION_FIELD=/username -e JWT_SECRET_KEY= secrettoken -e HTTPS_CERTFILE=cert/selfsigned.pem -e HTTPS_KEYFILE=cert/selfsigd_key.pem accenture/reactive-interaction-gateway:latest
With the modified command it will now accept subscriptions, however its no longer validating jwt's
docker run -p 4000:4000 -p 4010:4010 -e SUBSCRIPTION_CHECK=jwt_validation -e JWT_SESSION_FIELD=/username -e JWT_SECRET_KEY=secrettoken accenture/reactive-interaction-gateway:latest
and testing with https://github.com/Accenture/reactive-interaction-gateway/blob/master/examples/ws-demo-jwt.html
the call to subscription 204s when it should error out because the jwt in the example file is not hashed with the correct JWT_SECRET_KEY
when i was using 2.0.2 requests to subscribe would 500 if their jwts were invalid.

Hm I see... will fix this and let you know. Thanks!

Should be fixed with #186 and included in the upcoming release.


" No communication with the instrument " error

I'm currently trying to use this library but I'm getting this error:
>> from solarshed.controllers.renogy_rover import RenogyRover
>>>
>>> controller = RenogyRover('/dev/ttyUSB0', 1)
>>>
>>> controller.battery_voltage()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/nexus/.local/lib/python3.10/site-packages/solarshed/controllers/renogy_rover.py", line 86, in battery_voltage
    return self.read_register(257, numberOfDecimals=1)
  File "/home/nexus/.local/lib/python3.10/site-packages/minimalmodbus.py", line 258, in read_register
    return self._genericCommand(functioncode, registeraddress, numberOfDecimals=numberOfDecimals, signed=signed)
  File "/home/nexus/.local/lib/python3.10/site-packages/minimalmodbus.py", line 697, in _genericCommand
    payloadFromSlave = self._performCommand(functioncode, payloadToSlave)
  File "/home/nexus/.local/lib/python3.10/site-packages/minimalmodbus.py", line 795, in _performCommand
    response = self._communicate(request, number_of_bytes_to_read)
  File "/home/nexus/.local/lib/python3.10/site-packages/minimalmodbus.py", line 930, in _communicate
    raise IOError('No communication with the instrument (no answer)')
OSError: No communication with the instrument (no answer)
>>>

Basically, I'm using this cable to connect the Renogy Rover controller to my Raspberry Pi. I'm not sure if my wire is at fault here. I also tried to create my own homemade cable but I can't figure out the pinout of the RJ12 connector since Renogy doesn't share that information (my controller didn't come with the proper RJ12 to USB cable that seems to be included according to some blogs I read).
If someone could help me, it would be really appreciated. Thanks :)

After some digging I found out taht the the cable is completely fine and is not the problem. The problem was in the slave address. I had to change it from 1 to 16. So my controller instance is now:
controller = RenogyRover('/dev/ttyUSB0', `1)
Hope that can help someone else!


Ability to install GPU Linux Drivers

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
NO
Describe the solution you'd like
A clear and concise description of what you want to happen.
I wanted to ask as I don't know if the devs will include the driver/module I've requested.  To give some back ground, I'm using Xpenology/Synology. The kernel for Synology NAS units have been compiled to work on third party hardware. I'm currently running it on an old Dell Poweredge T320 server, 40gb of RAM, 7.5tb of storage on a SHR raid, and a installed AMD HD 6450 1gb GPU. Motherboard picks it up no problem, however the software doesn't. I've requested for this to be added to the kernel (of xpenology), but no word or really a response to it being added. I've installed Frigate NVR via docker-compose (through portainer). How possible is it to install the drive to the container and if so how in the world would I be able to do it? And if not can this be a new feature? I know that you 've added the GPU via the UUID, but of course that doesn't work without drivers. Thanks in advance.

If the OS can't see the hardware, then Docker won't be able to see the hardware. If Docker can't see the hardware, then Portainer won't be able to access it either, as Portainer is a wrapper around Docker's functionality. Until XPEnology adds support for this in their kernel / Synology adds GPU support to DSM, Docker won't support GPUs and as such, neither will Portainer in this configuration.

What I was afraid of. So there is nothing else I can do.

Not unless support is provided for GPUs at the OS / kernel level.
Unless you have a particular need to run Synology's software, it might be a better idea to look at a more flexible platform that is designed for running on standard server hardware (like TrueNAS for example).