[Bug]: The score ts_rank on Postgres is relatively low compare to Embedding Distance score from PgVector, and cause problem on Hybrid Search

Bug Description
There are two problems with Postgres Hybrid Search.

The score from ts_rank used by Keyword Search is relatively low compared distance used by Vector Similarity Search. This will make the result from Keyword Search always in lower ranking compared to the result from Vector Similarity Search, or worst the keyword search result will be removed completely if you use Minimum Similarity PostProcessor
The score range from ts_rank is pretty wide, please see my example below.

Need to find a way to normalize both of them.
Version
latest
Steps to Reproduce
Run this query on your Postgres DB, and compare the score with you regular PgVector query result.
 OpenAI is not the only firm in its industry with an odd structure. Anthropic, created by rebels from OpenAI, and Inflection AI (whose co-founder, Mustafa Suleyman, is a board member of The Economist’s parent company)'),
    to_tsquery('anthropic')
  ) AS mentioned_once_long_sentence_1,
  ts_rank(
    to_tsvector('The quick brown fox jumped over the lazy dog. OpenAI is not the only firm in its industry with an odd structure. Anthropic, created by rebels from OpenAI, and Inflection AI (whose co-founder, Mustafa Suleyman, is a board member of The Economist’s parent company)'),
    plainto_tsquery('english', 'Mustafa')
  ) AS mentioned_once_long_sentence_2a,
  ts_rank(
    to_tsvector('The quick brown fox jumped over the lazy dog. OpenAI is not the only firm in its industry with an odd structure. Anthropic, created by rebels from OpenAI, and Inflection AI (whose co-founder, Mustafa Suleyman, is a board member of The Economist’s parent company)'),
    plainto_tsquery('english', 'Suleyman')
  ) AS mentioned_once_long_sentence_2b,
  ts_rank(
    to_tsvector('The quick brown fox jumped over the lazy dog. OpenAI is not the only firm in its industry with an odd structure. Anthropic, created by rebels from OpenAI, and Inflection AI (whose co-founder, Mustafa Suleyman, is a board member of The Economist’s parent company)'),
    plainto_tsquery('english', 'Mustafa Suleyman')
  ) AS mentioned_once_long_sentence_2c,
  ts_rank(
    to_tsvector('The quick brown fox jumped over the lazy dog. OpenAI is not the only firm in its industry with an odd structure. Anthropic, created by rebels from OpenAI, and Inflection AI (whose co-founder, Mustafa Suleyman, is a board member of The Economist’s parent company)'),
    to_tsquery('OpenAI')
  ) AS mentioned_twice_long_sentence,
  ts_rank(
    to_tsvector('The quick brown fox jumped over the lazy dog. OpenAI is not the only firm in its industry with an odd structure. Anthropic, created by rebels from OpenAI, and Inflection AI (whose co-founder, Mustafa Suleyman, is a board member of The Economist’s parent company)'),
    plainto_tsquery('english', 'Altman')
  ) AS never_mentioned_1,
  ts_rank(
    to_tsvector('The quick brown fox jumped over the lazy dog. OpenAI is not the only firm in its industry with an odd structure. Anthropic, created by rebels from OpenAI, and Inflection AI (whose co-founder, Mustafa Suleyman, is a board member of The Economist’s parent company)'),
    plainto_tsquery('english', 'satya nadella')
  ) AS never_mentioned_2,
  ts_rank(
    to_tsvector('The quick brown fox jumped over the lazy dog. OpenAI is not the only firm in its industry with an odd structure.
    “The mission continues,” tweeted Sam Altman, the co-founder of , the startup behind ChatGPT, on November 19th. But precisely where it will continue remains unclear. Mr Altman’s tweet was part of an announcement that he was joining Microsoft. Two days earlier, to the astonishment of Silicon Valley,  from Openai for not being “consistently candid in his communications with the board”. Then Satya Nadella, Microsoft’s boss, announced that Mr Altman would “lead a new advanced AI [artificial intelligence] research team” within the tech giant. At first it looked like Mr Altman would be accompanied by just a few former colleagues. Many more may follow. The vast majority of OpenAI’s 770 staff have signed a letter threatening to resign if the board fails to reinstate Mr Altman.
    The shenanigans involving the world’s hottest startup are not over. The Verge, a tech-focused online publication, has reported that Mr Altman may be willing to return to OpenAI, if the board members responsible for his dismissal themselves resign. Mr Nadella also seems to allow for that possibility. His manoeuvring could look shrewd either way. If Mr Altman returns, then Microsoft, Openai’s biggest investor, would have supported him at a time of crisis, strengthening an important corporate relationship. If Mr Altman and friends do join Microsoft, Mr Nadella could look even smarter. He would have brought in house the talent and technology that the world’s second-most valuable company is betting its future on.
    Microsoft has long invested in various forms of AI. It first announced it was working with OpenAI in 2016, and has since invested $13bn in the startup for what is reported to be a 49% stake. The deal means that Openai’s technology has to run on Azure, Microsoft’s cloud-computing arm. In exchange OpenAI has access to enormous amounts of Microsoft’s processing power, which it needs to “train” its powerful models.
    The investment became crucial to Microsoft one year ago with the launch of ChatGPT. The chatbot became the fastest-growing consumer software application in history, reaching 100m users in two months. Since then Microsoft has been busy working out how to infuse the startup’s technology into its software. It has launched ChatGPT-like bots to run alongside many of its offerings, including its productivity tools, such as Word and Excel; Bing, its search engine; and even its Windows operating system.
    Bringing parts of OpenAI in-house would be a smart move. The technology is central to Microsoft’s future. Having direct control over it eliminates the risk that OpenAI could take its technology in a different direction. And such influence would have been attained for a bargain. Before he was fired, Mr Altman was hoping to raise fresh funds for OpenAI that would value the firm at around $86bn. Hiring OpenAI’s boffins this way is something antitrust regulators would find harder to challenge than a straightforward acquisition. Investors appear keen. Microsoft’s share price fell slightly on the news of Mr Altman’s firing. That loss was reversed when his new gig was announced.
    Yet the move would also entail risks. One is reputational. A pillar of Microsoft’s AI strategy has been to keep the technology at arm’s length, thus insulating the company from any embarrassment caused when ChatGPT goes awry. When Meta, Facebook’s parent company, released Galactica, its science AI chatbot, the tool started to fabricate research. The public response was critical enough for Meta to take it down.'),
    plainto_tsquery('english', 'Why was Sam Altman ousted by the OpenAI board?')
  ) AS full_article_nlp_question,
  ts_rank(
    to_tsvector('Editor’s note (November 22nd 2023): OpenAI said it had agreed “in principle” that Sam Altman would rejoin the artificial-intelligence firm as its chief executive under a new board.
    “The mission continues,” tweeted Sam Altman, the co-founder of , the startup behind ChatGPT, on November 19th. But precisely where it will continue remains unclear. Mr Altman’s tweet was part of an announcement that he was joining Microsoft. Two days earlier, to the astonishment of Silicon Valley,  from Openai for not being “consistently candid in his communications with the board”. Then Satya Nadella, Microsoft’s boss, announced that Mr Altman would “lead a new advanced AI [artificial intelligence] research team” within the tech giant. At first it looked like Mr Altman would be accompanied by just a few former colleagues. Many more may follow. The vast majority of OpenAI’s 770 staff have signed a letter threatening to resign if the board fails to reinstate Mr Altman.
    The shenanigans involving the world’s hottest startup are not over. The Verge, a tech-focused online publication, has reported that Mr Altman may be willing to return to OpenAI, if the board members responsible for his dismissal themselves resign. Mr Nadella also seems to allow for that possibility. His manoeuvring could look shrewd either way. If Mr Altman returns, then Microsoft, Openai’s biggest investor, would have supported him at a time of crisis, strengthening an important corporate relationship. If Mr Altman and friends do join Microsoft, Mr Nadella could look even smarter. He would have brought in house the talent and technology that the world’s second-most valuable company is betting its future on.
    Microsoft has long invested in various forms of AI. It first announced it was working with OpenAI in 2016, and has since invested $13bn in the startup for what is reported to be a 49% stake. The deal means that Openai’s technology has to run on Azure, Microsoft’s cloud-computing arm. In exchange OpenAI has access to enormous amounts of Microsoft’s processing power, which it needs to “train” its powerful models.
    The investment became crucial to Microsoft one year ago with the launch of ChatGPT. The chatbot became the fastest-growing consumer software application in history, reaching 100m users in two months. Since then Microsoft has been busy working out how to infuse the startup’s technology into its software. It has launched ChatGPT-like bots to run alongside many of its offerings, including its productivity tools, such as Word and Excel; Bing, its search engine; and even its Windows operating system.
    Bringing parts of OpenAI in-house would be a smart move. The technology is central to Microsoft’s future. Having direct control over it eliminates the risk that OpenAI could take its technology in a different direction. And such influence would have been attained for a bargain. Before he was fired, Mr Altman was hoping to raise fresh funds for OpenAI that would value the firm at around $86bn. Hiring OpenAI’s boffins this way is something antitrust regulators would find harder to challenge than a straightforward acquisition. Investors appear keen. Microsoft’s share price fell slightly on the news of Mr Altman’s firing. That loss was reversed when his new gig was announced.
    Yet the move would also entail risks. One is reputational. A pillar of Microsoft’s AI strategy has been to keep the technology at arm’s length, thus insulating the company from any embarrassment caused when ChatGPT goes awry. When Meta, Facebook’s parent company, released Galactica, its science AI chatbot, the tool started to fabricate research. The public response was critical enough for Meta to take it down.'),
    plainto_tsquery('english', 'Sam Altman')
  ) AS full_article_simple_keyword;

type                            | keyword(s)        | score       |
--------------------------------+-------------------+-------------+
mentioned_once_short_sentence   | fox               | 0.06079271  |
mentioned_twice_short_sentence  | fox               | 0.075990885 |
mentioned_once_long_sentence_1  | anthropic         | 0.06079271  |
mentioned_once_long_sentence_2a | Mustafa           | 0.06079271  |
mentioned_once_long_sentence_2b | Suleyman          | 0.06079271  |
mentioned_once_long_sentence_2c | Mustafa Suleyman  | 0.09910322  |
mentioned_once_long_sentence_2d | Suleyman Mustafa  | 0.09910322  |
mentioned_twice_long_sentence   | OpenAI            | 0.075990885 |
never_mentioned_1               | Altman            | 0.0         |
never_mentioned_2               | satya nadella     | 0           |
never_mentioned_combined        | Fox or Altman     | 0.030396355 |
all_5_repeated_word             | dog               | 0.08897689  |
all_10_repeated_word            | dog               | 0.09421459  |
all_9_repeated_word_anomaly     | dog               | 0.09360665  |
perfect_match_1                 | dog               | 0.06079271  |
perfect_match_2                 | full sentencce    | 0.38170186  |
full_article_nlp_question       | nlp question      | 0.6724103   |
full_article_simple_keyword     | Sam Altman        | 0.19074538  |

Relevant Logs/Tracbacks
No response

I think ideally, relative rank fusion is applied (either in the vector store class, or as a node postprocessor?)
This blog posts details the two most common fusion algorithms
https://weaviate.io/blog/hybrid-search-fusion-algorithms

I wouldn't say this is a bug, more of a feature request. I am working on a PR to add relative score fusion, which will solve your problem.


calling kuroshiro from vuejs

Your npm package is really wonderful. I can build and use as a separate node application.
But when I wanted to integrate into my VueJS app, I encountered issues.
Isn't running npm install kuroshiro not enough?
I am using webpack and I am getting the following errors
Failed to load resource: the server responded with a status of 404 for the following two files:
bower_components/kuroshiro/dist/dict/base.dat.gz
bower_components/kuroshiro/dist/dict/check.dat.gz
and whole bunch of errors caused by the above two files missing.

Hello subregi, thanks for your feedback. By default, if you initiate kuroshiro without options in the web environment, kuroshiro will look for IPA Dictionary files(like base.dat.gz, check.dat.gz, etc.) in this path - bower_components/kuroshiro/dist/dict/. If IPA Dictionary files doesn't exist in this path, it will come up with 404 errors. To handle this issue, try set dicPath (the relative path where the IPA Dictionary files are) explicitly when initiating kuroshiro, like this:
kuroshiro.init({
    dicPath: '/lib/kuroshiro/dict/'
}, function (err) {
    // kuroshiro.js is ready
    // do something
});

hello qi, thanks for this. It worked like a charm.


Issues with CMIP6 data

Trying to provide a complete assessment of the CMIP6 data with both global mean and performance indices with the brand new xarray we are facing some issue with some model grid/files. This could be 1) an issue of the ECmean4 and the xESMF current interpolation method 2) some not regular cmor files in the CMIP6 archive.
Models on which ECmean4 is working completely:
(between parenthesis the time to process 30 years of data for global mean and performance indices, with 8 cores on wilma)

IPSL-CM6A-LR
CanESM5
EC-Earth3
MIROC6
TaiESM1
CNRM-CM6-1
AWI-CM-1-1-MR : oceanic interpolation from unstructured grid originally was not working, but nearest neighbour has been implemented when an unstructured grid is identified (not neat but fine)
CESM2
GFDL-CM4

Models on which ECmean4 is working partially:

CMCC-CM2-SR5
NorESM2-MM
ACCESS-CM2
With these three model a weird issue associated with sea ice is found. Apparentely remapping of sea ice does not work with the weight matrix computed on the ocean variables, since the sea ice model has a different grid!
An example error:

ValueError: The horizontal shape of input data is (291, 360), different from that of the regridder (292, 362)!

Most recent devel/clim-cmip6 presents now some issue with CESM2, might be only realted to the type of grid used for land-sea mask.

We have been able to introduce a safe check that avoid interpolation if the mask present a mismatch, so that also CMCC and NorESM can be processed (though we cannot get sea-ice). Some models shows issues because we had multiple grids in the same folders, but this is not an ECmean problem. I am closing this


Comprehensive Call Cache Capoeirae!

👍 once the extra sleep is removed

:+1: Very thorough!  Ironic the only backend not getting the Capoeira treatment is Amazon...


Finalize the PFB weigth function

Do we want apodization?

Done and have a function inside LN_spec under windows directory.
See also notch_response in notebooks/calibrator


Add multi-gpu github actions tests using horovod

Goals :soccer:
This PR adds a GitHub Actions workflow for multi-GPU tests.
Implementation Details :construction:

We currently have the workflow horovod (cpu) for running unit tests that depend on Horovod, but it only runs on CPU.
We use Conda environment mainly for cudatoolkit because installing the necessary Cuda and MPI libraries is easier and cleaner if we use Conda. It also has the advantage of testing the actual workflow for users that do not use the Docker environment and instead opt for installing the individual libraries. Note we also use Conda for the CPU test in horovod-cpu-environment.yml to make installing MPI cleaner.

Testing Details :mag:

GitHub Actions

Can I get more information as to why we need to set this up in an environment that should already have both the cuda toolkit and mpi? Like I can go on the merlin containers right now and I have mpirun and the cuda toolkit is that not enought?

@jperez999 I thought we were moving in the direction of using tox for tests on PRs, which is the main reason I had to install all the dependencies in the tox environment. If we don't want to be using conda and if we are okay with running some tests outside tox, I'm okay with that too.

@edknv ok now I get it. Yes we are running in tox but anything that is available on the actual environment we can use. For instance most of our tests run cudf, but we dont install cudf to each environment. I think it works where anything not in the environment is picked up from the main environment. So I think it should be possible to run the tox and use the packages available on the container. If this is not the case based on your testing let me know... because that will mean we have a ton of other problems... 😃 Al our other tox environments are running under the same premise.

I will close this and move it to #1009.


Need Parse the Transcript of a video

https://www.tiktok.com/@lacedmedia/video/7265345807103085866
i want scrap the transcript of this video i found your api is not providing any support
although how can i scrap full html  until feature release can i parse this manually from html response

@Russell-Newton any update on this

I have not had a chance to look at implementing this. I tried to do it a while ago but had some trouble. I'll take a look at it when I can, my priority is currently getting ready to go back to college. At the moment, there's no easy way to grab the HTML with this library, unfortunately.

@Russell-Newton i have done a workaroung  this api not pull subtitle info  def download_subtitles_file(subtitle_url):
print('Fetching video data ... ')
try:
    response = requests.get(subtitle_url, proxies={'http':'brd-customer-hl_13b9cb8c-zone-data_center:2b153vd2vt20@brd.superproxy.io:22225'})
    response.raise_for_status()

    print('Subtitles downloaded successfully!')

    subs = response.text
    subs = subs.replace('\n\d\d:\d\d:\d\d.\d\d\d --> \d\d:\d\d:\d\d.\d\d\d\n', '\n')
    subs = subs.replace('\n\n', '\n')
    subs = subs.replace('WEBVTT', '')

    return subs
except requests.HTTPError as http_err:
    print(f'HTTP error occurred: {http_err}')
    return {"error": True, "message": str(http_err)}
except Exception as err:
    print(f'Error occurred: {err}')
    return {"error": True, "message": str(err)}   subtitle_url = data['video']['subtitleInfos'][0]['Url']
  download_subtitles_file(subtitle_url) fix the subtitle info its coming empty

are we able to fix the subtitle issue ?

@Russell-Newton bro i done it and fix many more things please tell me how to become contributor where can i share changelog

@zakrian07 make a fork with your changes if you haven't already, then create a pull request from your fork to this repo. I appreciate any contributions, especially because I've been pretty much unable to work on this library since starting grad school.

I can share file source here you can review and merge then ?
On Sat, Nov 18, 2023 at 8:05 PM Russell Newton @.***>
wrote:

@zakrian07 https://github.com/zakrian07 make a fork with your changes
if you haven't already, then create a pull request from your fork to this
repo. I appreciate any contributions, especially because I've been pretty
much unable to work on this library since starting grad school.
—
Reply to this email directly, view it on GitHub
https://github.com/Russell-Newton/TikTokPy/issues/70#issuecomment-1817532474,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABPI5XK6BJGRNIVSY6BYASDYFDFEVAVCNFSM6AAAAAA3L4HDCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXGUZTENBXGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Please create a fork and pull request. Here's a short guide from GitHub on how to do that: https://docs.github.com/en/get-started/quickstart/contributing-to-projects

@Russell-Newton pull request done

Implemented in version 0.2.4.


Update //:test_integration to work with RBE

//:test-integration doesn't yet work with RBE. Follow the approach done by @graknlabs_grakn//test-end-to-end/client-java:client-java-e2e in order to make it work:

The test needs to depend on //:distribution so it knows to re-run the test when the distribution is changed in any way.
Grakn needs to be started and stopped from within the test as opposed to from circleci

Once the test has been made to work with RBE, change the circleci yml such that //n:test-integration is executed using the RBE mode:
bazel:
  command: bazel ...

Fixed


[build] symlink replay-assets during build

having an env var that can be used to override where we load these assets from is useful, but it shouldn't be necessary to use it unless they're coming from some non-standard place.
during the build, symlink the assets to the proper place in the out dir.
maybe copying would be better (since it would make things work the same as a build step when/if we ever rewrite these in typescript)?

oops, typo in the command handlers filename.  symlink is a-ok with it :facepalm:


Scrolling not working on Chrome for Android Beta (v35)

I use Hammer.js for horizontal gestures on list elements - the user can swipe left or right on list elements for additional options.
While I got this to work on Chrome for Android (v34) and on the Stock Browser on a Galaxy S2, I can't scroll on Chrome for Android Beta (v35). While the swipe gestures are working correctly, scrolling is not possible.
I have the following configuration (copy & pasted it together from various posts I found about this topic):
swipe_velocity: 0.2,
swipeVelocityX: 0.2,
swipe_time: 300,
dragLockToAxis: true,
dragBlockHorizontal: true,
drag: true,
drag_block_horizontal: true,
drag_lock_min_distance: 20,
hold: false,
release: true,
tap: false,
touch: true,
transform: false
I don't know if it is a bug in Chrome or another problem.

@RyanMG thanks for suggesting the workaround above. I tried it but doesn't seem to work for me. I seem to be in little different situation though. Touch scrolling breaks for me, but not 100% of time, its more like 85-90% of the time. It resumes if I open devtools or move the mouse cursor.
Of course, Chrome versions have moved on since you chatted here about this. I am using 46. Did you find anything more conclusive about this issue?
I am using hammer 2.0 to disable some events on the app global container, namely:
transform dragleft dragright swipe swipeleft swiperight
On top of it, I am using angular. So these elements are in an ng-repeat. Once the scroll breaks, if I don't resort to the mouse, the scrollbars do work with touch, but that's medieval. Why would pan-to-scroll be so difficult, I wonder. Anyway, cannot reproduce this issue with Canary.
Tried several chromium builds, thinking its this fix that made a difference, but haven't been able to prove that to myself.

Yes @majido has fixed at least one problem like that recently.

Weird, but what can you do.

As I mentioned above, you can filed a bug with repro steps and we'll get it fixed in the next Chrome release!  If you can still reproduce an issue on Chrome 47+ (especially if removing hammer makes no difference) then PLEASE file a bug with repro steps and we will get it fixed ASAP.

For what seems like such a common use case on the mobile web, it's a pretty silly bug.

This stuff is complicated (and a little brittle) because of our threaded scrolling architecture where we want handle touch scrolling completely in our compositor without blocking on the blink thread (which is the only thread that knows about the DOM in any detail).  Sorry for the pain this is causing!

Thanks @RByers for the detailed response.
I cannot reproduce my issues with Chrome Canary 48.0.2547.0, but downloading chromium builds until 48.0.2527.0 hasn't given me the same successful results.
I was hoping I could pin it to a commit, so I can watch out for it in upcoming chrome releases, but haven't been able to in my brief testing. Which commit by @majido are you mentioning about - I am curious?
I also downloaded Sawbuck and ran with chrome and chrome frame set to verbose. But when the locking freezes, or in general, I don't get any messages from the renderer. Perhaps I am missing something.

I was hoping I could pin it to a commit, so I can watch out for it in upcoming chrome releases, but haven't been able to in my brief testing. Which commit by @majido are you mentioning about - I am curious?

Just the bug you found.  I took a quick look through the other changes I was thinking about, and they all seem unlikely to be your issue.  I'd suggest trying Chrome Beta, if you don't see any problems there then it's likely to be fixed with Majid's change.

@RByers yes, I don't see the problem in the beta version. Do you know when the next release of chrome is going to be out, in other words, when will this beta be promoted to stable?

Chrome is released about every 6 weeks, and Chrome 46 went stable on Oct 13.  So I'd guess early December 47 should get promoted to stable.


Get download URL for the latest successful build and its artifact?

Is it possible to get download URL for the latest successful build and its artifact?

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

ID: 7175ebdc-0bba-7e00-d113-036a5cffe5fa
Version Independent ID: 149ab9f4-0b7d-97e7-6cf5-1b54fd04c63c
Content: Publish and consume build artifacts in builds - Azure Pipelines and TFS
Content Source: docs/pipelines/artifacts/build-artifacts.md
Product: devops
GitHub Login: @andyjlewis
Microsoft Alias: alewis

Pinging @vijayma here, I'm not aware that this is possible but it would be nice to put it on Vijay's radar as a potential improvement!

I have tried the REST API to download the artifact but it does not work, https://docs.microsoft.com/en-us/rest/api/azure/devops/build/artifacts/get artifact?view=azure-devops-rest-5.1

I dont get the downloadUrl in the response as described in the doc.
{"id":4,"name":"nrf-ble-driver-macos","resource":{"type":"PipelineArtifact","data":"850045660D5D5A88FB10CED8AF2428AA84F2F179A5199479037E94E3419B215701","properties":{"RootId":"4E69256EE1933637020D40A90CBC5DE4DB5A7A82947A5AD6CB47818E75C3E5B202"},"url":"https://dev.azure.com/ChunFan/66d06ed9-b064-45b4-9e3e-458cd15cb887/_apis/build/builds/48/artifacts?artifactName=nrf-ble-driver-macos&api-version=5.1-preview.5"}}

re-tagging as doc-bug per this comment:

I dont get the downloadUrl in the response as described in the doc.
{"id":4,"name":"nrf-ble-driver-macos","resource":{"type":"PipelineArtifact","data":"850045660D5D5A88FB10CED8AF2428AA84F2F179A5199479037E94E3419B215701","properties":{"RootId":"4E69256EE1933637020D40A90CBC5DE4DB5A7A82947A5AD6CB47818E75C3E5B202"},"url":"https://dev.azure.com/ChunFan/66d06ed9-b064-45b4-9e3e-458cd15cb887/_apis/build/builds/48/artifacts?artifactName=nrf-ble-driver-macos&api-version=5.1-preview.5"}}

Hey, I'm from one of the pipelines teams that works with build artifacts.
For a while, Pipeline Artifacts weren't populating that downloadUrl field in the Build Artifact, but that should now be fixed as a couple of months ago.

As Josh explained, you can view the artifacts now in the UI (enable multi-stage pipelines preview feature). You can find the URL by opening the browser tools and looking at the network call. It is of the form: https://dev.azure.com///_apis/build/builds//artifacts?artifactName=&api-version=5.1&%24format=zip

I would also like this option for my companies wiki page .. could this please be reopened?

@vijayma @elbatk can someone please recheck this issue? How is it possible its being closed if nothing is solved here? Please read again the issue description.

A simple one liner will do.
You can just inline some html in a data url: data:text/html,download
And then write some script to talk to the api as discussed. However, this hardcodes a PAT (private access token), so anyone with this link can access any artifacts. Make sure to scope the PAT to artifacts only.
The PAT has to be base64 encoded in a form like this: :[PAT]. example
var o="[organization]/[project]";
var b="[branch]";
var p="[pipeline]";
var a="[artifact]"
var k="[authentication-header]";

var r=new XMLHttpRequest();
r.open("GET","https://dev.azure.com/"+o+"/_apis/build/latest/"+p+"?branchName="+b,false);
r.setRequestHeader("Authorization",k);
r.send(null);
var d=new XMLHttpRequest();
d.open("GET","https://dev.azure.com/"+o+"/_apis/build/builds/"+JSON.parse(r.responseText).id+"/artifacts?artifactName="+a, false);
d.setRequestHeader("Authorization",k);
d.send(null);
document.getElementById("btn").href=JSON.parse(d.responseText).resource.downloadUrl;

Finally remove all the new lines and fit the script into the  tag to get your download url:
data:text/html,download
Hope it helps.

@vijayma I think this is still an open issue. In my case i want to link from the Projects READE.md (inside azure devops) to the last successful build (or even better its artifacts) to help my less technically inclined colleagues find the build result of the Pipeline.  Using a similar approach as @BrunoZell doesn't work there (and inlineing the PAT feels very wrong aswell).
I feel this feature could be quite helpful for many projects, maybe the badge example could even be upgraded to make the badge a link directly bringing the user to the latest build.

I also think it is really fundamental to get the latest successful build. So much so that I assumed I just couldn't figure out how to do so. Could this please be implemented?

It's kinda disgusting that you have to write scripts for every API calls which should be included.
Hope this feature is in your scope.

I'm opening because of MicrosoftDocs/azure-devops-docs/issues/11400 which I am going to close.
@Asinin3 - There's a lot of discussion in this issue. From your point of view, what is it you want addressed? Also, in thinking about this, separate documentation fixes from feature requests. Feature requests should go here.
@vijayma @steved0x for awareness

Just want to be able to have a static link to download the latest successful build's artifact without having to use scripts/api calls. e.g Bormm's suggestion.

Just want to be able to have a static link to download the latest successful build's artifact

In addition, would be nice if there was a separate link for (the latest successful build of) each branch.
For example: _build/results?branch=develop&buildId=latestSuccessful&view=artifacts&type=publishedArtifacts

@reunanen , @Asinin3--thank you for taking the time to share your feedback. We use these GitHub issues for documentation issues. To create feature requests, we're using our developer community site (we recently changed from User Voice). You can create the feature request here: https://developercommunity.visualstudio.com/search?space=21
It's the best way to get a feature request on the product team's radar. I'm closing this issue since it's no longer a documentation request.


Added remove materials stage

@leerichard42  I merged in master and fixed the conflicts, make sure to git pull from this branch.

Looks great!  Just those minor comments.

Updated!

Looks good. :+1:


Enum with Data compatability

Currently it is not possible to generate Typescript bindings for enums that contain data.
For example:
#[derive(TS)]
enum Foo {
    Bar(String),
    Other
}

Produces an error: "variant has data attached. Such enums are not yet supported."
In this case, we would expect typescript bindings like:
type Foo = string | "Other"

I'm exploring implementing this on my own. If you have any pointers, they're welcome.

I'm exploring implementing this on my own. If you have any pointers, they're welcome.


Bootstrap 4 Support

This is a great project. Thank you for the time and effort in developing and maintaining it. It's saved me a lot of time!
With the recent official release of Bootstrap 4.0 will this project be updated/forked to support Bootstrap 4 CSS?

I really hope a Bootstrap 3 fork will remain actively developed because there are developers who still have to support browsers that lack support for flexbox.

Hi there. thank you for using this project!
Currently there're no plans on Bootstrap 3->4 upgrading, Because there's already one exist: https://github.com/bootstrap-vue/bootstrap-vue. However, if you found some really good reasons that this lib HAVE to upgrade, I will think about it.
Anyway, Bootstrap 3 will always be supported here, with all latest Vue.js upgrades.

I would also like to see a Bootstrap 4 version.
Unfortunately, https://github.com/bootstrap-vue/bootstrap-vue only covers bootstrap and does not account for anything extra.  Like Date Picker, Time Picker, etc.  Where your repo seems to be more thought out for full development purposes.  Like not including every single thing that bootstrap comes with, but just the necessity for an App.  Which I like.
I also like that there is no prefix.

Also it would be nice when upgrading from bootstrap 3 to bootstrap 4 to not have to rewrite as much of the existing app code. I would add a link to this issue in the Readme.md, because longevity of a framework is a major concern when it it selected. If you are suggesting that no bootstrap 4 fork will be made, this framework has an expiration date.
However, this looks like a nice framework so my vote is that a fork for 4 would be started, so people can start contributing. I'd keep it in this same repo, just make it on a different branch.

@jleaders

I would add a link to this issue in the Readme.md

I think it's good to have more discussions on this issue. PR is welcome. If more people wanted the v4 upgrade, I will start working on it.

Thanks for reopening this, hope you'll consider it, great package, specially Typeahead and Notification
good luck

What I really like about this project is that it is lean - because you DON'T wrap every single Bootstrap class / component - unlike bootstrap-vue
I don't need "help" writing HTML with Bootstrap classes. I just want the JQuery stuff replaced with Vue.js. What you have here is perfect.
It would be so awesome to have the same for Bootstrap 4.

I agree! It will be great if uiv releases a fork for bootstrap 4. Yours is a much better aproarch imho compared to bootstrap-vue!
I consider it very bad that other libraries try to replace HTML, I just need the jquery bits replaced with vue components!

I'm planning to start using vue in a fairly big web project where we're currently using bootstrap 3. If we could migrate from non-vue boostrap to using uiv bootstrap 3 and then easily upgrade to a future uiv bootstrap 4 it'd save us a ton of work :-)


RWA-2139 Made a small changes to trigger image version update

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/RWA-2139
Change description
-make a small commit to trigger image version update
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

This ticket is not required anymore to trigger image version update since the image version has been updated yesterday


Finish replacing md5sum with md5sum.js

We want to replace the md5sum command because it adds an external dependency and has broken osx builds in the pase (#246). This PR finishes the work to fully replace the md5sum command with a node.js version, the lingering need was for the command to regenerate the shasums. The md5sum.js script now accepts -c like md5sum and behaves the same if that is not passed.

Current coverage is 95.00% (diff: 100%)

Merging #258 into master will increase coverage by 95.00%

@@           master       #258   diff @@
========================================
  Files           4          4
  Lines         420        420
  Methods        40         40
  Messages        0          0
  Branches        0          0
========================================
+ Hits            0        399   +399
+ Misses        420         21   -399
  Partials        0          0

Powered by Codecov. Last update 35ab470...8b1e497

Looks good, can you rebase and merge this in addition to the other related checksum pull requests.

Rebased, will merge once green on travis.

This branch is ready to go once travis reports green. It ensures the build errors when tests fail (#249) and then fixes the variety of issues to get the tests passing again. Next action after this merges is to backport the necessary things to 5.4.


Lockscreen fix

Just creating a PR for our own use case. @landrybr maybe explain what you did in the comments.

This PR resets the Django site server when the app goes to the background and restarts it when it's coming back to the foreground.  This prevents iOS from killing the server thread and saves memory for the phone user.


Bump to Go 1.23 (and allow certificates with negative serial numbers)

Preparations for https://github.com/cert-manager/trust-manager/pull/510 as K8s 1.32 dependencies require Go 1.23.
It seems like Go 1.23 rejects negative serial numbers by default in x509.ParseCertificate, but the old behavior can be restored - as least as a short-term fix.
Long-term fix is probably to ensure our default trust bundles don't contain offending certificates. Maybe https://github.com/cert-manager/trust-manager/issues/183?

/cc @SgtCoDFish

@erikgb do we know which certificate has a negative serial number?

@erikgb do we know which certificate has a negative serial number? Let's investigate that first.

@inteon See https://kubernetes.slack.com/archives/CDEQJ0Q8M/p1734108493381519?thread_ts=1734105432.142589&cid=CDEQJ0Q8M

We have decided to take another approach to fix this issue. See https://github.com/cert-manager/trust-manager/pull/515


Remove version: Insco.PicGuard version <IP_ADDRESS>1

Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/picguard/picguard/releases/download/v1.0.0%2B401/picguard_1.0.0+401_windows_x64_en-US.msi
OK
(Automated message - build 923)

Close with reason: Package still available;


mat progress bar. Add the ability to combine different modes

Please describe the feature you would like to request.
Add the ability to combine different modes.
What is the use-case or motivation for this proposal?
Lets say your progress is jumpy and goes from 0 to 50 to 100. It would be nice to still have some animations going.
HERE! I hacked my solution by layering two progress bars.
So
1
@Input()
mode: 'determinate' | 'indeterminate' | 'buffer' | 'query'

could be extended with new inputs: 'detIndeterminate' | 'detBuffer' | 'detQuery' or
2
a new @Input() addDetermination could be introduced to combine determination with animation.
3
mode: 'indeterminate' | 'buffer' | 'query' and the occurence of value could yield to the desired behaviour, but could possibly "break/alter" current UX.
Is there anything else we should know?
I would like to know how you like the idea?

This isn't something we plan on adding to the component directly; the app can always stretch out the values it hands to the progress-bar itself.

@jelbourn I tried to make something work, but no success yet. Lets say my mode="indeterminate" and my value="50". What do I have to stretch out where? Can't make it work to make a solid progressbar to 50%.


Changing project and closing app results in open error

When open a file, the filename is saved in user config as the last file you opened.  When changing the project and restarting the application, the last file is attempted to be opened from the new project, but doesn't exist.
This will be fixed in the refactor by clearing the last file user config option.

This appears fixed to me now.  The only related problem seems to be that user config isn't always saved.


GUI Apps Refuse to Run

Windows build number:
22621.1702
Your Distribution version:
22.04 Jammy
Your WSL versions:
WSL2
Steps to reproduce:
sudo aptitude install x11-apps
The following NEW packages will be installed:
  x11-apps xbitmaps{a}
0 packages upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
Need to get 743 kB of archives. After unpacking 2758 kB will be used.
Do you want to continue? [Y/n/?] y
Get: 1 http://archive.ubuntu.com/ubuntu jammy/main amd64 x11-apps amd64 7.7+8build2 [719 kB]
Get: 2 http://archive.ubuntu.com/ubuntu jammy/main amd64 xbitmaps all 1.1.1-2.1ubuntu1 [23.4 kB]
Fetched 743 kB in 3s (272 kB/s)
Selecting previously unselected package x11-apps.
(Reading database ... 200136 files and directories currently installed.)
Preparing to unpack .../x11-apps_7.7+8build2_amd64.deb ...
Unpacking x11-apps (7.7+8build2) ...
Selecting previously unselected package xbitmaps.
Preparing to unpack .../xbitmaps_1.1.1-2.1ubuntu1_all.deb ...
Unpacking xbitmaps (1.1.1-2.1ubuntu1) ...
Setting up x11-apps (7.7+8build2) ...
Setting up xbitmaps (1.1.1-2.1ubuntu1) ...
Processing triggers for man-db (2.10.2-1) ...

root@Crimson-8:/home/dbtsgds2023# export DISPLAY=<IP_ADDRESS>:0.0
root@Crimson-8:/home/dbtsgds2023# xeyes
Error: Can't open display: <IP_ADDRESS>:0.0
root@Crimson-8:/home/dbtsgds2023# xeyes
Error: Can't open display: <IP_ADDRESS>:0.0
root@Crimson-8:/home/dbtsgds2023# export DISPLAY=<IP_ADDRESS>:1.0
root@Crimson-8:/home/dbtsgds2023# xeyes
Error: Can't open display: <IP_ADDRESS>:1.0
root@Crimson-8:/home/dbtsgds2023# apt install gedit -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  gedit-common gir1.2-gtksource-4 gir1.2-peas-1.0 gstreamer1.0-plugins-good gstreamer1.0-x libdv4 libgspell-1-2
  libgspell-1-common libgstreamer-plugins-good1.0-0 libgtksourceview-4-0 libgtksourceview-4-common libhandy-1-0
  libharfbuzz-icu0 libiec61883-0 libjavascriptcoregtk-4.0-18 libmanette-0.2-0 libpeas-1.0-0 libpeas-common libv4l-0
  libv4lconvert0 libwebkit2gtk-4.0-37 libyelp0 python3-gi-cairo xdg-dbus-proxy xdg-desktop-portal-gtk yelp yelp-xsl
  zenity zenity-common
Suggested packages:
  gedit-plugins libdv-bin oss-compat gstreamer1.0-libav gstreamer1.0-plugins-bad gstreamer1.0-alsa evince
  xdg-desktop-portal-gnome
The following NEW packages will be installed:
  gedit gedit-common gir1.2-gtksource-4 gir1.2-peas-1.0 gstreamer1.0-plugins-good gstreamer1.0-x libdv4 libgspell-1-2
  libgspell-1-common libgstreamer-plugins-good1.0-0 libgtksourceview-4-0 libgtksourceview-4-common libhandy-1-0
  libharfbuzz-icu0 libiec61883-0 libjavascriptcoregtk-4.0-18 libmanette-0.2-0 libpeas-1.0-0 libpeas-common libv4l-0
  libv4lconvert0 libwebkit2gtk-4.0-37 libyelp0 python3-gi-cairo xdg-dbus-proxy xdg-desktop-portal-gtk yelp yelp-xsl
  zenity zenity-common
0 upgraded, 30 newly installed, 0 to remove and 1 not upgraded.
Need to get 30.9 MB of archives.
After this operation, 116 MB of additional disk space will be used.

Setting up zenity-common (3.42.1-0ubuntu1) ...
Setting up xdg-dbus-proxy (0.1.3-1) ...
Setting up libdv4:amd64 (1.0.0-14build1) ...
Setting up libpeas-1.0-0:amd64 (1.32.0-1) ...
Setting up libv4lconvert0:amd64 (1.22.1-2build1) ...
Setting up python3-gi-cairo (3.42.1-0ubuntu1) ...
Setting up libgtksourceview-4-common (4.8.3-1) ...
Setting up libgspell-1-2:amd64 (1.9.1-4) ...
Setting up yelp-xsl (42.0-1) ...
Setting up libhandy-1-0:amd64 (1.6.1-1) ...
Setting up libiec61883-0:amd64 (1.2.0-4build3) ...
Setting up gir1.2-peas-1.0:amd64 (1.32.0-1) ...
Setting up libv4l-0:amd64 (1.22.1-2build1) ...
Setting up libgtksourceview-4-0:amd64 (4.8.3-1) ...
Setting up gir1.2-gtksource-4:amd64 (4.8.3-1) ...
Setting up gstreamer1.0-plugins-good:amd64 (1.20.3-0ubuntu1) ...
Setting up libwebkit2gtk-4.0-37:amd64 (2.38.6-0ubuntu<IP_ADDRESS>) ...
Setting up libyelp0:amd64 (42.1-1) ...
Setting up zenity (3.42.1-0ubuntu1) ...
Setting up yelp (42.1-1) ...
Processing triggers for libglib2.0-0:amd64 (2.72.4-0ubuntu2) ...
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Setting up gedit (41.0-3) ...
update-alternatives: using /usr/bin/gedit to provide /usr/bin/gnome-text-editor (gnome-text-editor) in auto mode
root@Crimson-8:/home/dbtsgds2023# apt install gimp -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  gimp-data libamd2 libbabl-0.1-0 libcamd2 libccolamd2 libcholmod3 libcolamd2 libgail-common libgail18 libgegl-0.4-0
  libgegl-common libgexiv2-2 libgimp2.0 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libmetis5 libmypaint-1.5-1
  libmypaint-common libsuitesparseconfig5 libumfpack5 libwmf-0.2-7 libwmf0.2-7
Suggested packages:
  gimp-help-en | gimp-help gimp-data-extras gvfs-backends gvfs libwmf-0.2-7-gtk
The following NEW packages will be installed:
  gimp gimp-data libamd2 libbabl-0.1-0 libcamd2 libccolamd2 libcholmod3 libcolamd2 libgail-common libgail18
  libgegl-0.4-0 libgegl-common libgexiv2-2 libgimp2.0 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libmetis5
  libmypaint-1.5-1 libmypaint-common libsuitesparseconfig5 libumfpack5 libwmf-0.2-7 libwmf0.2-7
Setting up libmypaint-common (1.6.0-2) ...
Setting up libbabl-0.1-0:amd64 (1:0.1.92-1) ...
Setting up libmetis5:amd64 (5.1.0.dfsg-7build2) ...
Setting up libmypaint-1.5-1:amd64 (1.6.0-2) ...
Setting up libwmf-0.2-7:amd64 (0.2.12-5ubuntu1) ...
Setting up gimp-data (2.10.30-1build1) ...
Setting up libgegl-common (1:0.4.34-1build1) ...
Setting up libgtk2.0-common (2.24.33-2ubuntu2) ...
Setting up libgexiv2-2:amd64 (0.14.0-1build1) ...
Setting up libsuitesparseconfig5:amd64 (1:5.10.1+dfsg-4build1) ...
Setting up libamd2:amd64 (1:5.10.1+dfsg-4build1) ...
Setting up libcolamd2:amd64 (1:5.10.1+dfsg-4build1) ...
Setting up libwmf0.2-7:amd64 (0.2.12-5ubuntu1) ...
Setting up libgtk2.0-0:amd64 (2.24.33-2ubuntu2) ...
Setting up libcamd2:amd64 (1:5.10.1+dfsg-4build1) ...
Setting up libgail18:amd64 (2.24.33-2ubuntu2) ...
Setting up libgtk2.0-bin (2.24.33-2ubuntu2) ...
Setting up libccolamd2:amd64 (1:5.10.1+dfsg-4build1) ...
Setting up libcholmod3:amd64 (1:5.10.1+dfsg-4build1) ...
Setting up libgail-common:amd64 (2.24.33-2ubuntu2) ...
Setting up libumfpack5:amd64 (1:5.10.1+dfsg-4build1) ...
Setting up libgegl-0.4-0:amd64 (1:0.4.34-1build1) ...
Setting up libgimp2.0:amd64 (2.10.30-1build1) ...
Setting up gimp (2.10.30-1build1) ...
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
Processing triggers for man-db (2.10.2-1) ...
Unpacking vlc-plugin-notify:amd64 (3.0.16-1build7) ...
Selecting previously unselected package vlc-plugin-samba:amd64.
Preparing to unpack .../07-vlc-plugin-samba_3.0.16-1build7_amd64.deb ...
Unpacking vlc-plugin-samba:amd64 (3.0.16-1build7) ...
Selecting previously unselected package vlc-plugin-skins2:amd64.
Preparing to unpack .../08-vlc-plugin-skins2_3.0.16-1build7_amd64.deb ...
Unpacking vlc-plugin-skins2:amd64 (3.0.16-1build7) ...
Selecting previously unselected package vlc-plugin-video-splitter:amd64.
Preparing to unpack .../09-vlc-plugin-video-splitter_3.0.16-1build7_amd64.deb ...
Unpacking vlc-plugin-video-splitter:amd64 (3.0.16-1build7) ...
Selecting previously unselected package vlc-plugin-visualization:amd64.
Preparing to unpack .../10-vlc-plugin-visualization_3.0.16-1build7_amd64.deb ...
Unpacking vlc-plugin-visualization:amd64 (3.0.16-1build7) ...
Setting up vlc-plugin-video-splitter:amd64 (3.0.16-1build7) ...
Setting up vlc-bin (3.0.16-1build7) ...
Setting up fonts-freefont-ttf (20120503-10build1) ...
Setting up vlc-l10n (3.0.16-1build7) ...
Setting up vlc-plugin-visualization:amd64 (3.0.16-1build7) ...
Setting up vlc-plugin-access-extra:amd64 (3.0.16-1build7) ...
Setting up vlc-plugin-qt:amd64 (3.0.16-1build7) ...
Setting up vlc (3.0.16-1build7) ...
Setting up vlc-plugin-notify:amd64 (3.0.16-1build7) ...
Setting up vlc-plugin-samba:amd64 (3.0.16-1build7) ...
Setting up vlc-plugin-skins2:amd64 (3.0.16-1build7) ...
Processing triggers for libvlc-bin:amd64 (3.0.16-1build7) ...
Processing triggers for fontconfig (2.13.1-4.2ubuntu5) ...
Processing triggers for man-db (2.10.2-1) ...
root@Crimson-8:/home/dbtsgds2023# apt install x11-apps -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
x11-apps is already the newest version (7.7+8build2).
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
root@Crimson-8:/home/dbtsgds2023# wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
--2023-05-31 12:49:10--  https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
Resolving dl.google.com (dl.google.com)... <IP_ADDRESS>, 2404:6800:4015:800::200e
Connecting to dl.google.com (dl.google.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 93841272 (89M) [application/x-debian-package]
Saving to: ‘google-chrome-stable_current_amd64.deb’

google-chrome-stable_current_ 100%[=================================================>]  89.49M  11.4MB/s    in 7.9s

2023-05-31 12:49:18 (11.3 MB/s) - ‘google-chrome-stable_current_amd64.deb’ saved [93841272/93841272]

root@Crimson-8:/home/dbtsgds2023# dpkg -i google-chrome-stable_current_amd64.deb
Selecting previously unselected package google-chrome-stable.
(Reading database ... 208753 files and directories currently installed.)
root@Crimson-8:/home/dbtsgds2023# google-chrome
google-chrome: command not found
root@Crimson-8:/home/dbtsgds2023# apt install --fix-broken -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  libu2f-udev
The following NEW packages will be installed:
  libu2f-udev
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
Need to get 4190 B of archives.
After this operation, 14.3 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu jammy/main amd64 libu2f-udev all 1.1.10-3build2 [4190 B]
Fetched 4190 B in 1s (4087 B/s)
Selecting previously unselected package libu2f-udev.
(Reading database ... 208868 files and directories currently installed.)
Preparing to unpack .../libu2f-udev_1.1.10-3build2_all.deb ...
Unpacking libu2f-udev (1.1.10-3build2) ...
Setting up libu2f-udev (1.1.10-3build2) ...
Setting up google-chrome-stable (114.0.5735.90-1) ...
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/x-www-browser (x-www-browser) in auto mode
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/gnome-www-browser (gnome-www-browser) in auto mode
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/google-chrome (google-chrome) in auto mode
root@Crimson-8:/home/dbtsgds2023# dpkg -i google-chrome-stable_current_amd64.deb
(Reading database ... 208871 files and directories currently installed.)
Preparing to unpack google-chrome-stable_current_amd64.deb ...
Unpacking google-chrome-stable (114.0.5735.90-1) over (114.0.5735.90-1) ...
Setting up google-chrome-stable (114.0.5735.90-1) ...
Processing triggers for man-db (2.10.2-1) ...

According to this: https://learn.microsoft.com/en-us/windows/wsl/tutorials/gui-apps?source=docs

You could run GUI based Linux apps in an X11 server.

That's a lie.

Running any of the commands listed in the link when it comes to any of the installed apps results in this:

-bash: insert-app-name-here: command not found

Happens 24/7 with me.

You just cannot run ANY applications used on Linux distros with WSL2.

You must install Linux in order to use them.

Prove me wrong.

I'll fight back harder with log's and screenshots, because I am absolutely fed up with this ill explained instructions list from the link I have sent.

### WSL logs:

This directory is non-existent.

### WSL dumps:

Again, non-existent directory.

### Expected behavior:

The specified app opens without issue.

### Actual behavior:

Printed in "Steps to Produce".

I don't know why it still printed in the grey box after editing the issue to correct it but I'll just add a much a much more visable version of the issue here:
According to this: https://learn.microsoft.com/en-us/windows/wsl/tutorials/gui-apps?source=docs
You could run GUI based Linux apps in an X11 server.
That's a lie.
Running any of the commands listed in the link when it comes to any of the installed apps results in this:
-bash: insert-app-name-here: command not found
Happens 24/7 with me.
You just cannot run ANY applications used on Linux distros with WSL2.
You must install Linux in order to use them.
Prove me wrong.
I'll fight back harder with log's and screenshots, because I am absolutely fed up with this ill explained instructions list from the link I have sent.

export DISPLAY=<IP_ADDRESS>:1.0

May I suggest referring to the rather helpful architectural overview at https://github.com/microsoft/wslg to appreciate how WSLg works? This would highlight "XWayland" as one major building block.
Basically, running X11 GUI applications happens via XWayland; WSLg does not expose a native X11 (display) server anywhere, and at no stage are there any claims that this happens.
Leave out the explicit export of DISPLAY and everything will work just fine.
As a side note, language such as "is a lie", "prove me wrong", "fight back", "absolutely fed up" are all but inviting for anybody wishing to communicate with you.

Well, those instruction were vague, because I followed them, but they didn't work.

I just took the time to read the official Microsoft instructions you linked to.
I am unable to detect any vagueness in those instructions. When putting on my well-tuned "do not make me think" hat, I consider these instructions to be crystal clear, concise, and correct - and I expect that, once being followed, these instruction will lead to immediate success.
Even more, I am unable to notice anything suggesting that "export DISPLAY" or "runs an X11 display server" would in any way be relevant to WSLg.

Well, it doesn't work on my system.

I followed the same instructions you just read.
No Linux GUI apps run.

I was finally able to open Linux Apps on Windows 11's WSL2 platform....
It required a reboot.


Proposals: Implement rules of voice decay and rollover

Goals of voice decay and rollover

Incentivize users to participate -> decay
Dis-incentivize users to use their vote on things they don't care about -> rollover
Prevent hoarding of votes -> time limit on rollover

Potential better solutions
We might be able to come up with simpler rules to reach the same goals - open to suggestions.
Solution
Voice starts decaying halfway through a cycle

If a user has not used their voice on anything, it starts linearly declining towards 0 at the end of the cycle
if a user uses their voice or votes indifferent, then their voice does not decay
if a user used their voice during the cycle it carries over to the next cycle
max voice anyone could accumulate is 3 cycles worth - this timespan is in settings
In order to implement this we need to have a way to store the unused voice for each user each cycle.

Implementation suggestion
I would suggest having a rollover table scoped by user name - on each new cycle, new voice for that cycle is calculated and added to the rollover table with timestamp
Then we calculate total voice of all rollover timestamps (which includes the latest) < 3 cycles old and add it to the voice table (so the frontend can show total voice, and everyone knows what total voice is)
While we iterate we also delete entries > 3 cycles old
To implement voice decay, both the voice table entry and all rollover entries are decayed at the same time and same rate. Note that decay only starts 1/2 way through the cycle.

Hello, I have some questions:

If voice starts decaying and then a user uses their voice, the voice stops decaying, right?
What do you mean by vote indifferent?
How could I know in what part of the cycle we are, I mean, how could I know when the 1/2 cycle is reached?
What would be the period of time the voicedecay function would be executed?

Voice=trust

Yes once votes are cast the "current trust" is moved to "saved trust" and the decay stops (as decay is only affecting "current trust"

Indifferent being - abstain. Its a "vote" but one where no trust credits are cast. This is just to signify - I came, I saw, I'm indifferent.

Each cycles starts at full and new moon. Half cycles are at quarter and 3/4 moons.

Trust decay starts at half cycle and finishes at start of new cycle where the Full Trust is diminished within that week.


Emulator hangs on startup screen with "android" flashing

Hey, any one still working on this? This is super helpful from the look of it.
Also will this work on Azure VMs?
I followed the steps to setup this on my Azure VM, i can see the container started, and i can even use VNC to open the android emulator.
However it stuck at the startup screen with "android" flashing.
I am wondering if this is due to i am using the VM or i did not follow the steps correctly.
Thank you for your help.
Thanks
Ted

Hi, do you have enough memory and disk space to run container? It works not very fast, well, starts at least as usual Android VM, and if you are using weak machine it takes a lot of time get working instance.
"Android" screen means that you passed to Android boot loader, but VM can stuck on out of memory or disk space.

I also have this problem when trying to run it via the terminal with no GUI.  I narrowed it down to the last command in the entrypoint.sh file. If I look at the logs, it just stops and hangs after a while.  The last line in the log is:
emulator: ping command: /usr/local/android-sdk/tools/ddms ping emulator <IP_ADDRESS> "" "" ""
I also posted my question and ingfo about this on the Docker hub

Well, this is a correct last line. Usually, when you are connecting by VNC it also shows some connection parameters. Could you provide your machine specs? Are you using Docker in Linux or Windows with Oracle VirtualBox VM?

Hi I am using docker on a Linux Ubuntu server on Virtual Box VM.  VM has 4GB memory and 30GB disk space

Thank you very much for responding. Sorry i was off town for a while.
I just updated my Azure VM to 2 core and 14 GB memory and still has the same issue.
Here is what i did:

I start up the android docker with the following command:
sudo docker run -e "EMULATOR=android-22" -e "ARCH=x86" -d -P --name android tracer0tong/android -emulator
Wait until i see it started by using adb devices
I tried to use the default vnc port (5900) to connect it by usinvncviewer <IP_ADDRESS>:32768
Then i see the TightVNC:QEMU opened, but it shows "Android" and keep flashing.
Waited more than an hour, still stuck on that load page.

Is there anything i am doing wrong?
Thank you very much.
Ted

Any help please ?
Still have this issue.

Some update on this.
When i tried the default way to start the docker: "docker run -d -P --name android tracer0tong/android-emulator " it worked fine. I can use vncviewer to see the android emulator started.
But when i try:
sudo docker run -e "EMULATOR=android-22" -e "ARCH=x86" -d -P --name android tracer0tong/android -emulator
sudo docker run -e "EMULATOR=android-22" -e "ARCH=armeabi-v7a" -d -P --name android tracer0tong/android -emulator
They are not working, it still hangs on the android load screen. I also tried "EMULATOR=android-21"
It is still the same.
Can anyone help? Thanks

Sorry, I have vacation, so no time to check issues. I will try do reproduce problem.

On my case the problem APPARENTLY was that my machine was missing this package:
Intel x86 Atom_64 System Image
I have updated what was installed and selected this package that was not selected.
Running Windows 8.1 64bit / VS 2017

@InsomniumBR I'm currently also trying to get the android-22 x86 version running on Windows 10 in Docker for Windows, and I'm also getting the behavior described above.
(Emulator container begins booting, but is stuck on the flashing Android logo)
What do you mean by:

Intel x86 Atom_64 System Image
I have updated what was installed and selected this package that was not selected.

What exactly did you change ? the Dockerfile ?

@drywolf looks like @InsomniumBR rebuilt container by himself. I'm usually testing container from Dockerhub. Theoretically Android can stuck if he has not enough memory. If you can see logo - system started to boot (this is bootloader screen). Question is why he couldn't start. If you have tried to build container by yourself, try to install all ABIs from Dockerfile. All systems images and etc. Also try to use image from Dockerhub, which works at least for me on Windows 7.

@drywolf @tracer0tong Sorry guys! I am not using a docker or container. I just got here because I had the same symptoms on the title.
@drywolf I am out of office now, but I will try to remember. I was using Visual Studio 2017 with Android SDK Manager to debug some stuff here, and I could not boot an emulator based on x86 (Arm-based was working well.) So I found that package that I mentioned before inside the package lists to download from Android SDK manager. Then I recreated the AVD (android virtual device) selecting now x86_64 (something like that) instead of just x86. And It worked.
Sorry to no have more details on that. I am pretty new on Xamarin/Android/iOS development.

@drywolf @tracer0tong Sorry guys! I am not using a docker or container. I just got here because I had the same symptoms on the title.
@drywolf I am out of office now, but I will try to remember. I was using Visual Studio 2017 with Android SDK Manager to debug some stuff here, and I could not boot an emulator based on x86 (Arm-based was working well.) So I found that package that I mentioned before inside the package lists to download from Android SDK manager. Then I recreated the AVD (android virtual device) selecting now x86_64 (something like that) instead of just x86. And It worked.
Sorry to no have more details on that. I am pretty new on Xamarin/Android/iOS development.

@tracer0tong Thanks for the reply.
Up to now I only used the prebuild image from DockerHub, but I have just built the image myself and the behavior is the same (v21+ is stuck on the "Android" screen)
I looked at the adb log output for the v22 image, which gives the following:
I/qemu-props(    0): connected to 'boot-properties' qemud service.
W/auditd  (  915): type=2000 audit(0.0:1): initialized
I/auditd  (  915): type=1403 audit(0.0:2): policy loaded auid=4294967295 ses=4294967295
W/auditd  (  915): type=1404 audit(0.0:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
I/qemu-props(    0): receiving..
I/qemu-props(    0): received: dalvik.vm.heapsize=48m
I/qemu-props(    0): receiving..
I/qemu-props(    0): received: ro.config.low_ram=true
I/qemu-props(    0): receiving..
I/qemu-props(    0): received: qemu.sf.lcd_density=240
I/qemu-props(    0): receiving..
I/qemu-props(    0): received: qemu.hw.mainkeys=1
I/qemu-props(    0): receiving..
I/qemu-props(    0): received: qemu.sf.fake_camera=back
I/qemu-props(    0): receiving..
I/qemu-props(    0): exiting (5 properties set).
I/lowmemorykiller(    0): No kernel memory.pressure_level support (errno=2)
E/lowmemorykiller(    0): Kernel does not support memory pressure events or in-kernel low memory killer
--------- beginning of system
I/Vold    (  919): Vold 2.1 (the revenge) firing up
D/Vold    (  919): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
I/SurfaceFlinger(  920): SurfaceFlinger is starting
I/SurfaceFlinger(  920): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL  (  920): Emulator without GPU support detected. Fallback to legacy software renderer.
D/libEGL  (  920): loaded /system/lib/egl/libGLES_android.so
D/gralloc_goldfish(  920): Emulator without host-side GPU emulation detected.
I/gralloc (  920): using (fd=11)
I/gralloc (  920): id           =
I/gralloc (  920): xres         = 480 px
I/gralloc (  920): yres         = 800 px
I/gralloc (  920): xres_virtual = 480 px
I/gralloc (  920): yres_virtual = 1600 px
I/gralloc (  920): bpp          = 16
I/gralloc (  920): r            = 11:5
I/gralloc (  920): g            =  5:6
I/gralloc (  920): b            =  0:5
I/gralloc (  920): width        = 74 mm (164.756760 dpi)
I/gralloc (  920): height       = 123 mm (165.203247 dpi)
I/gralloc (  920): refresh rate = 260.42 Hz
E/SurfaceFlinger(  920): hwcomposer module not found
W/SurfaceFlinger(  920): no suitable EGLConfig found, trying a simpler query
W/SurfaceFlinger(  920): EGL_SLOW_CONFIG selected!
I/SurfaceFlinger(  920): EGL information:
I/SurfaceFlinger(  920): vendor    : Android
I/SurfaceFlinger(  920): version   : 1.4 Android META-EGL
I/SurfaceFlinger(  920): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image_base EGL_KHR_fence_sync EGL_ANDROID_image_native_buffer
I/SurfaceFlinger(  920): Client API: OpenGL_ES
I/SurfaceFlinger(  920): EGLSurface: 5-6-5-0, config=0x0
W/SurfaceFlinger(  920): no suitable EGLConfig found, trying a simpler query
W/SurfaceFlinger(  920): EGL_SLOW_CONFIG selected!
I/SurfaceFlinger(  920): EGL information:
I/SurfaceFlinger(  920): vendor    : Android
I/SurfaceFlinger(  920): version   : 1.4 Android META-EGL
I/SurfaceFlinger(  920): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image_base EGL_KHR_fence_sync EGL_ANDROID_image_native_buffer
I/SurfaceFlinger(  920): Client API: OpenGL_ES
I/SurfaceFlinger(  920): EGLSurface: 5-6-5-0, config=0x0
I/SurfaceFlinger(  920): OpenGL ES informations:
I/SurfaceFlinger(  920): vendor    : Android
I/SurfaceFlinger(  920): renderer  : Android PixelFlinger 1.4
I/SurfaceFlinger(  920): version   : OpenGL ES-CM 1.0
I/SurfaceFlinger(  920): extensions: GL_EXT_debug_marker GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_format GL_OES_compressed_paletted_texture GL
_OES_draw_texture GL_OES_matrix_get GL_OES_query_matrix GL_OES_EGL_image GL_OES_EGL_sync GL_OES_compressed_ETC1_RGB8_texture GL_ARB_texture_compression GL_ARB_texture_non_power_of_
two GL_ANDROID_user_clip_plane GL_ANDROID_vertex_buffer_object GL_ANDROID_generate_mipmap
I/SurfaceFlinger(  920): GL_MAX_TEXTURE_SIZE = 4096
I/SurfaceFlinger(  920): GL_MAX_VIEWPORT_DIMS = 4096
W/SurfaceFlinger(  920): no suitable EGLConfig found, trying a simpler query
W/SurfaceFlinger(  920): EGL_SLOW_CONFIG selected!
I/SurfaceFlinger(  920): EGL information:
I/SurfaceFlinger(  920): vendor    : Android
I/SurfaceFlinger(  920): version   : 1.4 Android META-EGL
I/SurfaceFlinger(  920): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image_base EGL_KHR_fence_sync EGL_ANDROID_image_native_buffer
I/SurfaceFlinger(  920): Client API: OpenGL_ES
I/SurfaceFlinger(  920): EGLSurface: 5-6-5-0, config=0x0
D/SurfaceFlinger(  920): Set power mode=2, type=0 flinger=0xb685c000
E/SurfaceFlinger(  920): ro.sf.lcd_density must be defined as a build property
D/libEGL  (  979): Emulator without GPU support detected. Fallback to legacy software renderer.
D/libEGL  (  979): loaded /system/lib/egl/libGLES_android.so
D/gralloc_goldfish(  979): Emulator without host-side GPU emulation detected.

The emulator is stuck at this point and does not print any other log messages. For comparison, the v19 android image keeps outputting adb messages pretty much all the time during boot and even when it is already booted.

@tracer0tong Which version of Docker are you using to run the image on Windows 7 ? "Docker Toolbox" or "Docker for Windows" ?

@drywolf I'm using Kitematic, hope this project still alive. This is Oracle Virtual Box VM with Linux and Docker inside.

Ok maybe using a VirtualBox based docker engine works arround this issue (I am using the "Docker for Windows" engine).
I have investigated this issue more deeply, and it seems that officially running the Android emulator in a virtualized environment (Docker, VMs, ...) has been dropped at some point (see https://developer.android.com/studio/run/emulator-acceleration.html#extensions)
I have tried several ways and multiple workarrounds to get the most current emulator + x86 android image versions running in docker, but to no avail (yet).

I have the same issue.
I tried to run your container inside VirtualBox with boot2docker image.

Last time I have tested container from Dockerhub, I think I should try to rebuild it to see how it works. If you don't need newest API versions, you can try to use the same container.

@tracer0tong
I think the new API has to run on a main machine with CPU hardware acceleration.
I spotted another docker, running:
docker run -it --device /dev/kvm -p 5554:5554 -p 5555:5555 --env ANDROID_EMULATOR_EXTRA_ARGS="-skin 480x800" thedrhax/android-avd

For more info see readme
https://github.com/thedrhax-dockerfiles/android-avd
I'm not on my machine, but will try it later on Arch or Ubuntu.
With kvm-ok you can check if your machine setup is OK.

I just encountered this problem I am using the android emulator for flutter

I'm using Memu player to test my android apps, and run into this issues..
is this happening due to lack of memory space available?
i don't think so - 2GB available yet...


Android InstallReferrerDetails: install_begin_timestamp & referrer_click_timestamp always wrong and install_begin_timestamp often missing

We came across that install_begin_timestamp and referrer_click_timestamp are always wrong, since the Snowplow SDK assumes that the Google Play installreferrer API response is in milliseconds but it is actually in seconds since epoch.
As you can see in this screenshot, I was able to proof this. I corrected the install_begin_timestamp through multiplying it by 1000 and got the correct timestamp.

Source from the official API documentation regarding the response format

install_begin_timestamp: The timestamp, in seconds, of when a referrer click happened (both client- and server-side)
referrer_click_timestamp: The timestamp, in seconds, of when an installation began (both client- and server-side)
https://developer.android.com/google/play/installreferrer

Related file:
https://github.com/snowplow/snowplow-android-tracker/blame/07536ea8db236e8f6efd74b07f3af901a136846e/snowplow-tracker/src/main/java/com/snowplowanalytics/core/tracker/InstallReferrerDetails.kt#L70-L71
Further more, the install_begin_timestamp is missing for about 30% of installs (sample size ~145k installs on Android 8 and higher).We are running InstallReferrer package to v2.2 and Snowplow Tracker versions 5+

thanks for the report 😵

@davidher-mann is it just the install_begin_timestamp missing in those 30% of installs, or the referrer_click_timestamp as well? Do you know anything more about the events where it's missing, maybe about device?


fix credential access check to work with GHES

fix #153
The credential write access check was hardcoded to use api.github.com but that prevents it from working with GItHub Enterprise.
This change uses the API endpoint defined in the input file if it's present, otherwise falls back to api.github.com.

I booted a GHES instance and verified this works.


Does not support cocoapod

pod search WeaverDI cannot find any pod

Hi @ZZHHAANNGG,
WeaverDI is referenced correctly on cocapods website and a pod search WeaverDI outputs correctly on my machine:
-> WeaverDI (0.9.9)
   Declarative, easy-to-use and safe Dependency Injection framework for Swift (iOS/macOS/Linux)
   pod 'WeaverDI', '~> 0.9.9'
   - Homepage: https://github.com/scribd/Weaver
   - Source:   https://github.com/scribd/Weaver.git
   - Versions: 0.9.9, 0.9.8, 0.9.7, 0.9.6, 0.9.5 [master repo]

Have you tried to do a pod repo update before searching?

I just tried, but still cannot find it
pod search WeaverDI  [!] Unable to find a pod with name, author, summary, or description matchingWeaverDI`
pod repo update
Updating spec repo master
$ /usr/bin/git -C /Users/zhb/.cocoapods/repos/master fetch origin --progress
remote: Counting objects: 9536, done.
remote: Compressing objects: 100% (155/155), done.
remote: Total 9536 (delta 3852), reused 3805 (delta 3805), pack-reused 5569
Receiving objects: 100% (9536/9536), 1.06 MiB | 269.00 KiB/s, done.
Resolving deltas: 100% (6372/6372), completed with 1445 local objects.
From https://github.com/CocoaPods/Specs
2c880fa4439..0abc6b1fc67  master     -> origin/master
$ /usr/bin/git -C /Users/zhb/.cocoapods/repos/master rev-parse --abbrev-ref HEAD
master
$ /usr/bin/git -C /Users/zhb/.cocoapods/repos/master reset --hard origin/master
HEAD is now at 0abc6b1fc67 [Add] MHInteractiveClock 0.0.7
CocoaPods 1.5.3 is available.
To update use: sudo gem install cocoapods
For more information, see https://blog.cocoapods.org and the CHANGELOG for this version at https://github.com/CocoaPods/CocoaPods/releases/tag/1.5.3
pod search WeaverDI
[!] Unable to find a pod with name, author, summary, or description matching WeaverDI
`

It looks like this happens when you local cache is out of date.
This is an issue talking about this problem: https://github.com/CocoaPods/CocoaPods/issues/6221
Could you try to do rm -rf ~/Library/Caches/Cocoapods and try to search again?

It works! Thanks


plugins/crates-nvim: init

Adds crates-nvim as a plugin instead of just a completion source for cmp.
Resolves: https://github.com/nix-community/nixvim/issues/1149

This PR Is a copy of #1205

Because it can be a cmp source in addition of a plugin could you add a test enabling the plugin in cmp too?

A PR has been made for this here

FWIW I had opened a PR a while back: https://github.com/nix-community/nixvim/pull/1205


Spark-1.4 and Spark-1.5 supported

Different Spark version supported.
Spark-1.5 will be the default version.
To compile with Spark-1.4 -> mvn clean install -P spark-1.4

Please create a Build section in README.md file explaing this packaging possibilities


initial commit for Service Fabric microservices

Please review all the elements for publishing.

OPS Build status updates of commit bc18aef:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit bc18aef:
:clock10: Incremental building: average incremental building time is 23 sec(s)

OPS Build status updates of commit bc18aef:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/reference-architectures/microservices/sf.md
:warning:Warning
View
Details

docs/_images/icons/sf.svg
:white_check_mark:Succeeded
View

docs/microservices/index.json
:white_check_mark:Succeeded

docs/microservices/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/index.json
:white_check_mark:Succeeded

docs/reference-architectures/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-arch.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-monitoring.png
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/sf.md

[Warning] Author PageWriter cannot be recognized in GitHub.

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.

OPS Build status updates of commit 1c1b518:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit 1c1b518:
:clock10: Incremental building: average incremental building time is 23 sec(s)

OPS Build status updates of commit 1c1b518:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/reference-architectures/microservices/service-fabric.md
:warning:Warning
View
Details

docs/_images/icons/sf.svg
:white_check_mark:Succeeded
View

docs/microservices/index.json
:white_check_mark:Succeeded

docs/microservices/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/index.json
:white_check_mark:Succeeded

docs/reference-architectures/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-arch.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-monitoring.png
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/service-fabric.md

[Warning] Author PageWriter cannot be recognized in GitHub.

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.

OPS Build status updates of commit a19edab:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit a19edab:
:clock10: Incremental building: average incremental building time is 23 sec(s)

OPS Build status updates of commit a19edab:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_images/icons/sf.svg
:white_check_mark:Succeeded
View

docs/microservices/index.json
:white_check_mark:Succeeded

docs/microservices/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/index.json
:white_check_mark:Succeeded

docs/reference-architectures/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-arch.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-monitoring.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/service-fabric.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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.

OPS Build status updates of commit 5a78a3c:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit 5a78a3c:
:clock10: Incremental building: average incremental building time is 23 sec(s)

OPS Build status updates of commit 5a78a3c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_images/icons/sf.svg
:white_check_mark:Succeeded
View

docs/microservices/index.json
:white_check_mark:Succeeded

docs/microservices/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/index.json
:white_check_mark:Succeeded

docs/reference-architectures/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-arch.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-monitoring.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/service-fabric.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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.

OPS Build status updates of commit 1f08233:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit 1f08233:
:clock10: Incremental building: average incremental building time is 23 sec(s)

OPS Build status updates of commit 1f08233:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_images/icons/sf.svg
:white_check_mark:Succeeded
View

docs/microservices/index.json
:white_check_mark:Succeeded

docs/microservices/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/index.json
:white_check_mark:Succeeded

docs/reference-architectures/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-arch.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-monitoring.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/service-fabric.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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.

OPS Build status updates of commit 508e802:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit 508e802:
:clock10: Incremental building: average incremental building time is 23 sec(s)

OPS Build status updates of commit 508e802:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_images/icons/sf.svg
:white_check_mark:Succeeded
View

docs/microservices/index.json
:white_check_mark:Succeeded

docs/microservices/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/index.json
:white_check_mark:Succeeded

docs/reference-architectures/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-arch.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-monitoring.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/service-fabric.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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.

OPS Build status updates of commit 0870790:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit 0870790:
:clock10: Incremental building: average incremental building time is 23 sec(s)

OPS Build status updates of commit 0870790:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_images/icons/sf.svg
:white_check_mark:Succeeded
View

docs/microservices/index.json
:white_check_mark:Succeeded

docs/microservices/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/index.json
:white_check_mark:Succeeded

docs/reference-architectures/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-arch.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-monitoring.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/service-fabric.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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.

OPS Build status updates of commit e81cb00:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit e81cb00:
:clock10: Incremental building: average incremental building time is 23 sec(s)

OPS Build status updates of commit e81cb00:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_images/icons/sf.svg
:white_check_mark:Succeeded
View

docs/microservices/index.json
:white_check_mark:Succeeded

docs/microservices/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/index.json
:white_check_mark:Succeeded

docs/reference-architectures/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-arch.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-monitoring.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/service-fabric.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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.

OPS Build status updates of commit 1ef3924:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit 1ef3924:
:clock10: Incremental building: average incremental building time is 23 sec(s)

OPS Build status updates of commit 1ef3924:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_images/icons/sf.svg
:white_check_mark:Succeeded
View

docs/microservices/index.json
:white_check_mark:Succeeded

docs/microservices/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/index.json
:white_check_mark:Succeeded

docs/reference-architectures/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-arch.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-monitoring.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/service-fabric.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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.

OPS Build status updates of commit 52001fe:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit 52001fe:
:clock10: Incremental building: average incremental building time is 23 sec(s)

OPS Build status updates of commit 52001fe:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_images/icons/sf.svg
:white_check_mark:Succeeded
View

docs/microservices/index.json
:white_check_mark:Succeeded

docs/microservices/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/index.json
:white_check_mark:Succeeded

docs/reference-architectures/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-arch.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-monitoring.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/service-fabric.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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.

OPS Build status updates of commit 78fcdf0:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit 78fcdf0:
:clock10: Incremental building: average incremental building time is 23 sec(s)

OPS Build status updates of commit 78fcdf0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_images/icons/sf.svg
:white_check_mark:Succeeded
View

docs/microservices/index.json
:white_check_mark:Succeeded

docs/microservices/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/index.json
:white_check_mark:Succeeded

docs/reference-architectures/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-arch.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-monitoring.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/service-fabric.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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.

OPS Build status updates of commit 7aa5847:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit 7aa5847:
:clock10: Incremental building: average incremental building time is 23 sec(s)

OPS Build status updates of commit 7aa5847:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_images/icons/sf.svg
:white_check_mark:Succeeded
View

docs/microservices/index.json
:white_check_mark:Succeeded

docs/microservices/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/index.json
:white_check_mark:Succeeded

docs/reference-architectures/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-arch.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/_images/ra-sf-monitoring.png
:white_check_mark:Succeeded
View

docs/reference-architectures/microservices/service-fabric.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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.


Fix clang uninitialized variable warning.

We could just initialize it, but to be consistent with the rest of the file it seemed to make more sense to just drop.

Pushed. Thanks.


Add a new type of API authentication: multiple

This mode allow to use oauth and private token at the same time.
Both the Authorization: Bearer  and PRIVATE-TOKEN header are set in
the requests sent to the server

Woops sorry, my bad, this PR was not meant for repo just yet. I might open an issue to disscuss the use case later on. Right now I just needed a quick hack to test something.


Use CockroachDB PostgreSQL parser

Fantastic idea & project @kyleconroy!
Just in case you find interesting, the people from CockroachDB created a pg-compatible SQL parser in pure go: https://github.com/cockroachdb/cockroach/tree/master/pkg/sql/parser.
The benefit of avoiding the cgo dependency is that it would open the project up to other platforms.

I have two hesitations when it comes to using the CockroachDB query parser instead of pg_query_go. First is incompatibilities between the two parsers. I'll need to do more investigating to make sure there aren't valid PostgreSQL queries the Cockroach parser can't handle.
The second issue is Cockroach's licensing. The query parser is licensed under the Business Source License (BSL), which is not an open-source license. I'm not entirely sure how that licenses interacts with a tool like sqlc.

I have two hesitations when it comes to using the CockroachDB query parser instead of pg_query_go. First is incompatibilities between the two parsers. I'll need to do more investigating to make sure there aren't valid PostgreSQL queries the Cockroach parser can't handle.

Maybe @mjibson or @knz have something more to say on this :) But AFAIK the parser should be fully compatible and when it comes to execute it they check the compatibility of the AST (pointing you to the specific issue in case whatever thing in query is not supported).

The second issue is Cockroach's licensing. The query parser is licensed under the Business Source License (BSL), which is not an open-source license. I'm not entirely sure how that licenses interacts with a tool like sqlc.

That's a fair point, maybe they could told you how possible is to use freely.

A couple points:

cockroachdb's parser definitely does nog support all of postgres' grammar.

you can't simply "adopt a parser". A parser is a function from text to an AST data structure. If you reuse a parser you're also choosing to reuse the AST it was made for. However, an AST is also tightly bound to the rest of the language analyzer. In particular CockroachDB (currently) hangs off type checking and scalar evaluation as methods of AST nodes, with different semantics from postgres. I doubt that's what's desired here.

FWIW the CockroachDB tree is not 'go build'-compatible and the parsing code in particular uses a 4-step Makefile

(The licensing code is only a minor point, we can consider forking an Apache-licensed alternative for interested parties)
Verstuurd vanaf mijn Android apparaat met K-9 Mail. Excuseer mijn beknoptheid.

I was going through older issues and noticed that I never responded to this one.
@knz thanks for the explanation. I think it solidifies my opinion that we should not be using the Cockroach parser at this time.


jscpd hangs while processing large repository (elasticsearch)

Describe the bug
jscpd never returns when trying to analyze elasticsearch code
To Reproduce
Steps to reproduce the behavior:
git clone git clone https://github.com/elastic/elasticsearch.git
/usr/local/bin/jscpd  --min-lines 10 --reporters xml
Expected behavior
The program returns and produce the XML output
Desktop (please complete the following information):

OS: linux/ubuntu
NodeJS Version 8.10.0
jscpd version 1.2.0

Additional context
Add any other context about the problem here.

thank you for the report, will analyze and give solution for that soon

Please, try to run jscpd with the following command:
node --max-old-space-size=8192 /path/to/bin/jscpd .

Looks like we have the low level of allocated memory, it depends on node.js settings. I guess with command at the top you can resolve the issue temporarily, but anyway I have the plan to add persistence storage and add an ability to detect duplication in really huge repos.

still - with the command mentioned above, the programs hangs forever. I even let it run for 90 mins to make sure this was not because I was using it on a large repository!

I got it, working on solution

Tried again to run for the night and I got the following trace

<--- Last few GCs --->

[7907:0x565554477260]  7322504 ms: Mark-sweep 1189.5 (1482.6) -> 1189.4 (1482.6) MB, 3547.9 / 0.1 ms  allocation failure GC in old space requested
[7907:0x565554477260]  7326618 ms: Mark-sweep 1189.4 (1482.6) -> 1189.4 (1446.6) MB, 3903.1 / 1.2 ms  last resort GC in old space requested
[7907:0x565554477260]  7330504 ms: Mark-sweep 1189.4 (1446.6) -> 1189.4 (1442.6) MB, 3885.5 / 0.2 ms  last resort GC in old space requested

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x39f3e8f18fe1 <JSObject>
    1: exec(this=0x1d616425f6f1 <JSRegExp <String[58]: \b0x[\dA-Fa-f]+\b|(?:\b\d+\.?\d*|\B\.\d+)(?:[Ee][+-]?\d+)?>>,0x1821edb385d9 <String[1]: {>)
    2: matchGrammar [/usr/local/lib/node_modules/jscpd/node_modules/prismjs/prism.js:369] [bytecode=0x268d89da8279 offset=591](this=0xcc16d5abee9 <Object map = 0x17f41e2c00b1>,text=0x1d616425d1b1 <Very long string[5872]>,strarr=0x1d6164260819 <JSArray...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [node]
 2: 0x565553492011 [node]
 3: v8::Utils::ReportOOMFailure(char const*, bool) [node]
 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [node]
 5: v8::internal::Factory::NewCode(v8::internal::CodeDesc const&, unsigned int, v8::internal::Handle<v8::internal::Object>, bool, int) [node]
 6: v8::internal::RegExpMacroAssemblerX64::GetCode(v8::internal::Handle<v8::internal::String>) [node]
 7: v8::internal::RegExpCompiler::Assemble(v8::internal::RegExpMacroAssembler*, v8::internal::RegExpNode*, int, v8::internal::Handle<v8::internal::String>) [node]
 8: v8::internal::RegExpEngine::Compile(v8::internal::Isolate*, v8::internal::Zone*, v8::internal::RegExpCompileData*, v8::base::Flags<v8::internal::JSRegExp::Flag, int>, v8::internal::Handle<v8::internal::String>, v8::internal::Handle<v8::internal::String>, bool) [node]
 9: v8::internal::RegExpImpl::CompileIrregexp(v8::internal::Handle<v8::internal::JSRegExp>, v8::internal::Handle<v8::internal::String>, bool) [node]
10: v8::internal::RegExpImpl::IrregexpPrepare(v8::internal::Handle<v8::internal::JSRegExp>, v8::internal::Handle<v8::internal::String>) [node]
11: v8::internal::RegExpImpl::IrregexpExec(v8::internal::Handle<v8::internal::JSRegExp>, v8::internal::Handle<v8::internal::String>, int, v8::internal::Handle<v8::internal::RegExpMatchInfo>) [node]
12: v8::internal::Runtime_RegExpExec(int, v8::internal::Object**, v8::internal::Isolate*) [node]
13: 0x28be44040bd

Just released<EMAIL_ADDRESS>with persistence db inside, for now, you can run jscpd on really big projects

Awesome! I will give a shot right now, this comes as a xmas present for me :D

Merry Christmas! :)
BTW: I have done the detection for the elasticsearch. Detection duration was ~40 mins on my Mac, but it was completed successfully.

Also, I'm going to implement a cache system it will increase detection for non-first runs.
Subscribe for updates :)


Beta editor removes tutorial instructions, and other tutorial from homepage

Describe the bug
Tutorial instructions disappear when Shark Attack Tutorial is opened in beta editor, then developer navigates to webpage.
To Reproduce

Open Shark Attack Block Tutorial from homepage - (Somehow this opened up a Beta version of the code editor, and I have no idea why???.)
Work through a few steps of the tutorial
Navigate to a webpage outside MakeCode Arcade
Return to Editor - Tutorial on top of screen has disappeared
Return to homepage to find Tutorial starter
Sidescroller Tutorial is gone

Expected behavior
I expect to return back to the editor where the tutorial steps are still visible on the top of the screen. Additionally, I expect the Sidescroller tutorial to remain on the Arcade homepage.
Screenshots
Expect tutorial instruction steps to remain:

Expect Sidescroller not to disappear from homepage:

Desktop (please complete the following information):

OS: Mac OS 11.1
Browser  Chrome
Version 87.0.4280.88

Additional context
I have no idea how the Beta Editor opened when I started the Shark Attack tutorial.
Going into Private Mode, the Sidescroller Tutorial reappers:

/beta & live doesn't work well side by side. They also use different home screen when we are launching new content.
I am unable to reproduce this issue for now. We will keep an eye  on this issue.
One way to avoid these issue is using /beta in private or in-cognito window.

/beta & live doesn't work well side by side. They also use different home screen when we are launching new content.
I am unable to reproduce this issue for now. We will keep an eye  on this issue.
One way to avoid these issue is using /beta in private or in-cognito window.