Add the option to NOT push after commit on Submit when using LFS

Over time I've found it annoying that when using LFS locking, Submit to Source Control always pushes. The reasons I might not want to:

I have a sequence of commits to make and push each time slows that down
I know the push will fail because I'm working disconnected or behind the remote branch
I want to combine asset changes with C++ changes in one commit; without push I can amend the UE commit & add the C++ changes before push

The only reason for always pushing seems to be to unlock files, but I already implemented unlock-on-push in #137, so this is not a hard limit any more. So long as you do the final push in UE the files from the intermediate commits will be unlocked.
So I've added an extra option in the source control setup dialog to disable auto-pushing. It defaults to the previous behaviour.

Hey @sinbad, thanks a lot for all your awesome changes!
I wasn't available for quite a long time, with a baby at home, covid/wfh etc but I am now trying to come back to open source dev :)

Welcome back :)


Add __version__ at the module level

See details in the parent issue napalm-automation/napalm-base#70

Closing via https://github.com/napalm-automation/napalm-eos/pull/59


Update edr-in-block-mode.md

Identity & Threat Protection license is now known as Microsoft 365 E5 Security. Made changes accordingly.

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/5546


[top] cdc fix and cdc constraints

[rv_core_ibex] synchronize timer interrupts

timer interrupts do not currently come from the main clock domain
this PR is a quick fix that synchronizes the interrupts
long term, we should forward everything through rv_plic only and
give rv_plic the responsibility of synchronization like it does
with external interrupts now.

[top/cdc] Add a few cdc constraints to waive async fifo paths
Specifically, two types of paths are waived

fifo rdata outputs that are coupled into integrity errors,
which then affect whether ibex should cancel or continue
with the next data fetch

fifo rdata outputs that are coupled into socket_m1's
return path selection.  The source ID is used along side
rvalid to pick a specific dvalid

This fix is hacky right now, as we need to enhance the flow
such that an additional CDC constraint file can be supplied.

@eunchan
@jeoongp
are we okay to merge this now? or should we wait until i make this constraint a bit more specific?
let me know what you think.

I am OK with merging this

On Jun 6, 2022, at 1:47 PM, tjaychen @.***> wrote:
@eunchan https://github.com/eunchan
@jeoongp https://github.com/jeoongp
are we okay to merge this now? or should we wait until i make this constraint a bit more specific?
let me know what you think.
—
Reply to this email directly, view it on GitHub https://github.com/lowRISC/opentitan/pull/13016#issuecomment-1147909712, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJDG3RM5URKEGIYLJ3PH3LVNZPXNANCNFSM5XWDR4JA.
You are receiving this because you were mentioned.

thanks all. I filed a related issue to make sure we come back and clean this up.


Upgrade to react 15.5.0

Fixes this issue: #8
I needed a clean project and so i had to fixed all errors and warnings coming from current react version.
Everything works fine except the npm run test, but i have no idea what gets wrong. Maybe you have a clue whats the problem there.

You can use 'renderer' from 'react-test-renderer' instead of TestUtils and just do 'renderer.create' like this : https://github.com/GinjiBan/react-toggle-button/blob/master/tests/index-test.js

Any update on this? Would like to get this working with React 15.5+

closing this, just going to make the upgrade to react16 right now.


Remove owner % reserved rate when reserved rate is 0

Summary

Steps to reproduce

Go to '...'
Click on '....'
Scroll down to '....'
See error

What is the current bug behavior?
What is the expected correct behavior?
Relevant logs and/or screenshots
Environment

Device/OS: [e.g. iOS]
Browser: [e.g. chrome, safari]
Hardware wallet: [e.g. Ledger w/ Metamask]

This is closed by https://github.com/jbx-protocol/juice-interface/pull/1646
@johnnyd-eth


The meaning of gaussians_per_pixel and num_surfaces

Hi, thanks for your wonderful work! I am confused about the above two parameters. I notice that num_surfaces initialize the number of gaussians per pixel and gaussians_per_pixel control the topK probabilities of depth. Therefore, the final number of gaussians of each pixel equals gaussians_per_pixel*num_surfaces, am I correct? If I am wrong, what's the exact meaning of these two parameters? Besides, if I'd like to modify the gaussians of each pixel, which parameter should I choose to modify?

The gaussians_per_pixel parameter is the number of Gaussians sampled from each per-ray (per-pixel) probability distribution. The num_surfaces parameter is the number of independent probability distributions that exist for each ray. As you correctly say, the number of Gaussians per pixel is the product of the two parameters.
Our hypothesis was that by having multiple independent probability distributions for each ray, these distributions could converge around different surfaces. For example, the first and second distributions might always represent the first- and second- closest surfaces from the camera respectively. However, it turns out that having multiple distributions per ray doesn't really do anything, likely because the Real Estate 10k and ACID datasets contain mostly forward-facing scenes, where only one surface per ray is needed. We also found that the network can "cheat" and learn multiple surfaces even with num_surfaces == 1 by creating checkerboard patterns where pixels alternate between representing near and far surfaces. You can see this effect in figure 3 of the Splatter Image paper, which describes a similar approach to ours for object-centric scenes.
Which parameter you modify depends on what you're trying to do. Increasing gaussians_per_pixel makes training converge slightly faster (the thought is that you get gradients at more depths, so the overall gradient is a bit better). I recommend using num_surfaces == 1 unless you're trying to train the network on a dataset that looks very different from RE10k/ACID.


OID Wraparound

Description
This change adds a separate OID buffer for temp objects. Since temp objects are already session-local, we can allocate a separate buffer of OIDs set aside only for temp objects. This same buffer range can be used across all sessions.
Test Scenarios Covered
Unit tests in babelfishpg_unit for testing of individual functions. Standard JDBC tests for temp tables. In addition, a new JDBC module written that helps us test specific temp-table cases and inspecting OIDs of generated tables, among other things.
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 71.836%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
39777

Relevant Lines:
55372

💛  - Coveralls


Support switching to Iframes that are places in a Shadow Root

Related: https://stackoverflow.com/questions/55504936/accessing-an-iframe-within-shadow-dom-using-testcafe
What is your Test Scenario?
Use t.switchToIframe with an iframe element that is located inside a shadow root.
What are you suggesting?
Support this case. Currently, if you try to perform this, you will get the The iframe in which the test is currently operating does not exist anymore error.
Additional context
test.html
<!DOCTYPE html>

        <title>Test Shadow IFrame</title>

iframe.html
<!DOCTYPE html>

        <title>Shadow Iframe</title>

        <button onclick="logElement.textContent = 'It works'">Click me</button>

test.js
fixture `Test Shadow`
    .page`./test.html`;

test(`iframe`, async t => {
    await t
        .switchToIframe(() => shadowRootElement.shadowRoot.querySelector('iframe'))
        .click('button')
        .wait(3000);
})

We ran into this issue of testcafe, which became a blocker for automating certain UI features of ours. Do you have a timeline on putting in this support yet? We'd be very interested in trying it out when you do. @miherlosev

Hi @jzhang52
We cannot give you an estimate for this feature's release. We will update this thread as soon as we have news.

Just wanted to say we'd be making use of this when it's ready!

Nowadays working with shadow dom is quite common, isn't there a way to fix this?

@ddoice
The described issue still exists and, at present, I cannot give you an estimate on this.

Nowadays working with shadow dom is quite common, isn't there a way to fix this?

We agree with you and we are working on ShadowRoot support. For example, we introduced a special .shadowRoot() method, which allows querying shadow elements easily. If you are not familiar with this method, take a look at https://testcafe.io/documentation/402745/reference/test-api/selector/shadowroot


Update NodeStatus use subresources.

closes #6063

The problem I had yesterday was the reversed order in Validate... call. As Validate modifies (!) "old" object it caused status update to not work. I'm ashamed of myself for making this bug, and for the time it took me to find it, but I do believe that the fact that Validate modifies anything is plain wrong.

e2e is green

@lavalamp @gmarek said he's going on vacation, so if we need any changes here we may have to take the PR over.

LGTM


tryParse throws when monetary amount is empty

Example
Money.tryParse('', code: 'USD') //throws

Instead of returning null, an error is thrown.

Lewis,
I've just published 3.1.4 which includes your PR as well as fixes for Money.parse not throwing a MoneyParseException.
Greatly appreciate the PR.
I'm wondering if I could ask a favour.
I've just founded a company, OnePub and we have released our beta at onepub.dev.
It's a private package repository for dart.
I'm looking for beta testers and some feedback on the service.
The service is free during beta and anyone publishing a package during the beta receives a lifetime free subscription.
Brett


try to fix https://github.com/Microsoft/TypeScript/issues/8101

Fixes https://github.com/Microsoft/TypeScript/issues/8101

I left a comment about the return type in https://github.com/Microsoft/TypeScript/issues/8101#issuecomment-219497942. it will address the original issue, but will make clearer (i think :)).

let's change the return type from any to void, and we should be good to go.

Sorry for delay, a little busy.

thanks! might want to add a similar change to setImmediate as well.

Shouldn't the new overload be first since it's more specific?  Otherwise I think the compiler will still always choose the original overload.

Since setImmediate will need a similar overload as setTimeout, what about setInterval? a similar overload too?

sounds about right.


Service Provider/Container: Abstract Factory

hey guys,
i'm coming from zf2. Beside a huge more complexity there was one feature i really liked: Abstract factories. It was possible to define a factory class which can decide if it is able to build up an instance of the requested class. For example you could define an interface and every class that implements that interface the factory can build. I think for laravel it would be too much overhead to have this within a separate class, but we could for instance bind a closure to a service key that is an interface (and maybe add a flag to App::bind, so that we do not have to check every binding. or even new App::bindInterface method). Now if someone tries to fetch an instance of a class that is not registered explicitly the service container checks if it implements the forementioned bound interface and then use that bound closure.
One example - and the one because of that i come up with this - are doctrine repositories. You would only have to define one binding instead of as many repositories i have.
i'm curious about your opinions.
simon

Sorry to close this, but the forums are for discussions like this.


"ensure CRDs are installed first" while installing via HELM Chart

Hi,
I am trying to install the exporter, but I think I am doing something wrong because I get an error:
$ helm repo add aqua https://aquasecurity.github.io/helm-charts/
$ helm repo add giantswarm https://giantswarm.github.io/giantswarm-catalog
$ helm repo update
$ helm install trivy-operator oci://ghcr.io/aquasecurity/helm-charts/trivy-operator \
   --namespace trivy-system \
   --create-namespace \
   --version 0.21.3

$ helm upgrade -i starboard-exporter --namespace trivy-system  giantswarm/starboard-exporter

Release "starboard-exporter" does not exist. Installing it now.
Error: unable to build kubernetes objects from release manifest: resource mapping not found for name: "starboard-exporter-psp" namespace: "" from "": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1"
ensure CRDs are installed first

Trivi is installed:
$ kubectl get all -n trivy-system
NAME                                            READY   STATUS    RESTARTS      AGE
pod/scan-vulnerabilityreport-7877b49d8c-s8lts   3/3     Running   0             36s
pod/trivy-operator-7cc7457867-gwwt7             1/1     Running   1 (45s ago)   5m51s

NAME                     TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
service/trivy-operator   ClusterIP   None         <none>        80/TCP    5m51s

NAME                             READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/trivy-operator   1/1     1            1           5m51s

NAME                                        DESIRED   CURRENT   READY   AGE
replicaset.apps/trivy-operator-7cc7457867   1         1         1       5m51s

NAME                                            COMPLETIONS   DURATION   AGE
job.batch/scan-vulnerabilityreport-7877b49d8c   0/1           36s        36s
$ kubectl get crds | grep -i aquasecurity
clustercompliancereports.aquasecurity.github.io        2024-04-03T17:48:51Z
clusterconfigauditreports.aquasecurity.github.io       2024-04-03T17:48:51Z
clusterinfraassessmentreports.aquasecurity.github.io   2024-04-03T17:48:51Z
clusterrbacassessmentreports.aquasecurity.github.io    2024-04-03T17:48:51Z
clustersbomreports.aquasecurity.github.io              2024-04-03T17:48:51Z
clustervulnerabilityreports.aquasecurity.github.io     2024-04-03T17:48:51Z
configauditreports.aquasecurity.github.io              2024-04-03T17:48:51Z
exposedsecretreports.aquasecurity.github.io            2024-04-03T17:48:51Z
infraassessmentreports.aquasecurity.github.io          2024-04-03T17:48:51Z
rbacassessmentreports.aquasecurity.github.io           2024-04-03T17:48:51Z
sbomreports.aquasecurity.github.io                     2024-04-03T17:48:51Z
vulnerabilityreports.aquasecurity.github.io            2024-04-03T17:48:51Z

Can you please help me with what is missing right now?
Thank you!

Closing this so I can take it off my todo list :smile: but do let me know if I can help further


Support for Jessie import loader implementation

@smotaal, I understand that you can help add an import loader for Jessica.
Such a loader would probably exist in lib/import.mjs.ts, with tests under lang/nodejs/__tests__/import.ts.  I would expect lib/import.mjs.ts to be something like the following, with explicit endowments:
fuction makeImport(
  assetLoader: (path: string) => Promise<string>,
  evaluator: (src: string, uri: string) =>Promise<any>): Promise<any>;
export default makeImport;

Looking forward to talking more aboot this.
Thanks,
Michael.

First off, thank you so much for yesterday's amazing walkthrough. It was very informative to understand the moving parts, not just PEG which in my world now evolves from being mysterious to down-right hypnotic 🙂.
I'd like us to get a chance to discuss things in more detail. Maybe hangouts, or I can set up a zoom slot. I think we can put in writing the necessary interfaces once we considered the finer aspects in both domains and outlined the suitable integration paths that would honour grammars, semantics and conformance.
From my side, I'd like to push us to consider assetLoader to be a more granular aspect than a univariate and idempotent (ie a single flat map expanding over time) because those to me have been a rather unspoken barrier to ESM adoption in today's pre-realms world, and yet we are working here with notions like attenuation and compartments. I know it's premature to get into specifics, but we should at least make sure we don't end up relying on things that will not translate well moving forward on these fronts.
Should we connect? When? I am open and fairly flexible as long as I am aboot and your are about 🎉

Just to document this publically, @SMotaal and I discussed the official constraint that Jessie's import and export statements are only for default imports.  Essentially, Jessica doesn't need an ESM (Ecmascript Standard Modules) implementation, just something that more resembles require.

importer.mjs.ts has a basically working implementation.


Have npm run build-dist always recreate dist

Description
So we don't get keep files we no longer need. I wanted to have pushed this with #246 but I didn't push the local commit 😄

[x] I have performed a self-review of my changes
[x] I have read and understood the contributing guidelines

No hurry on this one. 😄


[WebUI] Multi-Select and Delete reports

Is your feature request related to a problem? Please describe.
It's very troublesome when I uploaded many reports and want to delete some of them.
Describe the solution you'd like
A method in web-ui to multi-select reports and deletes.
Describe alternatives you've considered
Maybe a method to filter reports by tags
Additional context
Maybe filtering seems better choice, but there will be always a need to delete at some point.

Hello, this should be implemented in 0.43.0. If there are any problems feel free to create new issues.


Add -d --diff switch to open two files in diff view

I wanted to use VSCodes diff view for the Perforce source control I am using. In this case it allows to call third party tools for the diff view. At the moment I launch it with command line arguments to open those two files (modified client and the original depot file) and than manually select both working items and compare them to each other.
I realize it might be very useful overall to add a -d or --diff %f1 %f2 switch to the launch option of vscode to launch Visual Studio Code immediately in the diff view.
Example
code --diff original.cpp modified.cpp (vscode launches immediately in the diff view for those two files

#1768


Setting DNS servers for systemd-resolved doesn't work as expected.

What did I expect: After connection establishment I expected the find the DNS server provided by the VPN peer associated with the VPN interface, either for all domains, or for domains I configured in config.yaml.
The following output was created on a Debian 11 system, using systemd-resolved for name resolution:
# /etc/resolv.conf
nameservers <IP_ADDRESS>
search wdf.sap.corp

The config.yaml doesn't configure anything about resolv handling.
Output of starting the VPN:
021/09/12 12:08:09 id: 1, id2: 3, Local IPv4 not acknowledged: <IP_ADDRESS>
2021/09/12 12:08:09 id: 1, id2: 3, Local IPv4 acknowledged: <IP_ADDRESS>
2021/09/12 12:08:09 Using wireguard module to create tunnel
2021/09/12 12:08:09 Created tun0 interface
2021/09/12 12:08:09 Detected systemd-resolved
2021/09/12 12:08:09 Forwarding all DNS requests to ["<IP_ADDRESS>" "<IP_ADDRESS>"]
2021/09/12 12:08:09 Setting routes on tun0 interface
2021/09/12 12:08:09 Applying routes, pushed from F5 VPN server

Now I expected from running resolvectl that my search domain and the nameservers are associated with the tun0 link. But, running resolvectl shows:
Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: foreign
Fallback DNS Servers: <IP_ADDRESS>
          DNS Domain: wdf.sap.corp

Link 2 (ens3)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: <IP_ADDRESS>
       DNS Servers: <IP_ADDRESS>

Link 8 (tun0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Once I manually issue
root@ntt:~# resolvectl domain tun0 wdf.sap.corp
root@ntt:~# resolvectl dns tun0 <IP_ADDRESS> <IP_ADDRESS>

I get the expected output from running resolvectl:
Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: foreign
Fallback DNS Servers: <IP_ADDRESS>
          DNS Domain: wdf.sap.corp

Link 2 (ens3)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: <IP_ADDRESS>
       DNS Servers: <IP_ADDRESS>

Link 8 (tun0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
     Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
   DNS Servers: <IP_ADDRESS> <IP_ADDRESS>
    DNS Domain: wdf.sap.corp

What am I missing?

I built the client from the new-tuncfg branch and the issue doesn't seem to persist as bad as it was in the first place.
Now the global DNS servers are replaced by the ones I got from the tunnel. I'm not sure if this is 100% correct. At least, in case the tunnel provides me a search list (or the client is configured to use a searchlist), I'd expect this list and the VPN provided DNS servers attached to the created tun0 interface.


Point, billboard, and labels roadmap

[ ] Optimize ray/terrain intersection when getting height.  At least add a 2x2 or 4x4 grid, if not an octree/quadtree that is a few levels deep.  That will probably take a day and produce a 10x gain.  Also consider temporal coherence, adjacency info, and simplifying the math for the case when the ray is along (well opposite) the ellipsoid normal.
[ ] Clamp points to terrain.
[ ] Billboard ground shadows to give a better sense of placement.  These could be faked like the Milktruck shadows.  Perhaps have a sparse texture with the longitude/latitudes and then do a simple blurred black circle at each point in the terrain pass.
[ ] Multipass with transform-feedback or occlusion queries (CC #797), e.g., we could determine if a billboard is x% visible in one pass then cull it in the next pass to be more precise than VTP.

See also some ideas re-thinking the way points/billboards/labels could be separated from the 3D scene, in https://github.com/AnalyticalGraphicsInc/cesium/issues/2694#issuecomment-339086615


[Next Theme] Set base font size to 18px

Description
Since the text font for the Next theme has a smaller appearance, a larger font-size is employed.
PS, this will probably need some followups to fine tune other areas.
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] All tests pass

[ ] yarn lint
[ ] yarn test-unit

[x] Update CHANGELOG.md
[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Normally I'd ask for screenshots and such, but since this is localized to next theme, I'm alright with pushing it through and iterating quickly

Matt, i have this hosted. There is certainly more to do for this and I have just tackled a few of the obvious ones.


what are the regions where this feature is supported?

Hi,
I was following the steps in this article and got the errors below.
"message":"Feature is not supported in the current region
I am using East us2, what are the regions which support this feature?
Thanks!
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: acf1d359-23da-2f07-af0d-d16284f738ba
Version Independent ID: eba6f1fd-cfe9-d038-b139-f02c0b48f4e0
Content: Quickstart: Use Document Summarization (preview) - Azure Cognitive Services
Content Source: articles/cognitive-services/language-service/summarization/quickstart.md
Service: cognitive-services
Sub-service: language-service
GitHub Login: @aahill
Microsoft Alias: aahi

@sixfu Thanks for the question. We are investigating the issue and will update you shortly.

Thanks for reaching out, currently the summarization feature is available in the following regions:

North Europe
East US
UK South

I'll update this article to specify this information!
#please-close


Add Skull/unskull notifications

Useful at revs, idk where else.

I have a skull timer PR also, I don't have the knowledge to make it 100% accurate when reseting your skull in pvp which is why that one is on hold for now. Yes I can move this to idle notifications but personally I didn't feel this was fitting.

I'm pretty sure i'll keep the skull timer as a separate PR, this is in a finished state and the skull timer is not. And the skull timer would do into a completely separate plugin anyways.

I guess it is convenient to put this in the idle notifier but I'm not sure how many people skull when idle.

I think I was the only person who ever wanted this, probably useless.


add login detail

test:
login

Hi @0guanhua0 thanks for the contribution.
Could you please add more explanation behind it? From what I understand, the suggestion you're adding is incorrect, but maybe I'm missing something.

no container, hint
guanhua@arch ~/ib (git)-[master] % sudo docker stop $(sudo docker ps -aq)
guanhua@arch ~/ib (git)-[master] % curl -X GET "https://localhost:5000/v1/api/one/user" -k
curl: (7) Failed to connect to localhost port 5000 after 0 ms: Couldn't connect to server

no login, no hint. silent success
guanhua@arch ~/ib (git)-[master] % sudo docker-compose up -d
guanhua@arch ~/ib (git)-[master] % curl -X GET "https://localhost:5000/v1/api/one/user" -k
guanhua@arch ~/ib (git)-[master] % echo $?
0

with login, cmd return account data
maybe we should add hint. silent success without output confuse me. if the design is to separate container start & login, then add this as hint
echo $?

Thanks for expanding! I must admit I'm not entirely sure I'm still following you - sorry - so bear with me just a little longer.
The steps you describe in your addition - accessing localhost:5000 and inputting the credentials - is something that IBeam should do automatically for you. Hence my previous comment, that adding such lines to the README would be incorrect in this case.
Are you trying to say that IBeam does not perform the authentication for you automatically, and you have to login manually?
Could you please share contents of your docker-compose (redacting any credentials) and the full output log of your container once started?

since container run in detach mode, no wonder no output
guanhua@arch ~/ib (git)-[master] % sudo docker-compose up -d

to check log
guanhua@arch ~/ib (git)-[master] % sudo docker compose logs -f

now with the log, i can verify. around 2 min for the auth process.
you are right on auto login. before no output so i just manual login, and this break other web api call.

Ahh, great, I'm glad you've managed to figure it out 👍


Change tiles

Change tiles by removing background

Hey, I have solved this issue should I make a pull request ?

yes


We should test security best practices in k8s

I think it would be best to remediate as much as possible in an automated manor.
So we could run something like kube-bench in our test pipeline and then remediate most of the issues.
Target should be that the kubeadm deployment is hardened automatically without a lot of customization from customers.
@thesephirot @eliobischof @stebenz inputs?

did a basic kube-bench test,... the "doing" is not that bad,... I guess we should test this on a control plane to have a complete log and check the output
citadel-kube-bench-logs.txt


add optimal binning

some issue with subtracting the background

I have change the fits handling to the same as yours and I have successfully reproduce the figure with the configuration.

imported to newest "czfork" branch for testing and fixing


[HW] Rebecca Zee

Name: Rebecca Zee
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/rebecca-zee-677761117/
Attach the homework step I screenshots below:

Attach the homework step II screenshots below:

Hey Rebecca Zee, great job! Congrats! Here is your badge! https://api.badgr.io/public/assertions/KHP-FgCwTv2Psb1cPKMB-Q


Add bold heading typography styles

Is your feature request related to a problem? Please describe.
We do not have bold any bold styles in our Typography specs.
Describe the solution you'd like
After speaking with @edwardbarraza about this issue, he and I agreed that we would add in bold variants for the H1-H6 font styles.
Describe alternatives you've considered
N/A
Additional context
N/A
Applicable requirements
N/A

@edwardbarraza I've added the bold typography styles, please review when you have a moment before I publish.  Or we can review during our UX tag up tomorrow.

Just reviewed them. They look good. Publish!

Thanks @edwardbarraza . they are published.


listen only one song

Good morning all :)
Thank you for all the work already done on your project.
I come to you because my librespot instalation works just for one song :(
(RPI 3B+ RASPIAN BUSTER LITE, connected at one LG bluetooth soundbar to bluealsa)
If I change the usual or if the song is finished and passes to the following, there is no sound ... :(
I can show you the result of any command to solve this problem, and I hope it will be useful to others :)
Yours truly.
PS: sorry for my english

I think I have the same problem, if I understand HarryCover78 correctly.
I am using librespot with the current librespot kodi addon (from awiouy) on a CoreElec installation.
Starting to playing a complete album I am used to start the first song and spotify automatically plays the complete album. This has worked good in the past. Since a while this often fails. Only the first song is in the playlist.
If I play local on the mobile, this works always.
As a workaround I can add the complete album to the playlist (spotify menu option on the album)
Best regards

I have the same issue with LibreELEC on my Raspberry Pi.

I have not observed this problem anymore for a while, now. Was it related to the spotify side? And is it fixed, already? We will see.

I'm new to the code but I think the way it works is that some player (Spotify app, Kodi, etc.) tells Spotify what song to play, and Spotify passes that to librespot.  The player can pass either a song ID (of one song only) or a playlist ID.  If the playlist ID is sent, librespot will play all the songs on the playlist automatically, even if the player is closed.  But if the ID of only one song is passed through, then librespot will stop once that song is complete.
If you're only hearing one song, but it works with an official Spotify client (e.g. website), I think this is a problem with the player you're using rather than librespot.


Add logo for Tyne and Wear Fire and Rescue service

This is a simplified version of their actual logo, with a lot of the gradients and strokes removed because:

they won’t show up at the small size
they made the file too complicated for our PDF thing to handle

Also add Thames Valley Police logo


full-screen preview isn't full-bleed in android 2.3

about 1/3 of the screen is blank for me

Depending on the device, sometimes a full screen preview is not available.


Fix auth bugs

mostly merged, except for the make config less magical commit. I don't actually remember what that was solving and it caused issues, so I'm going to close for now.


Get USB drive info

Provide an ability for the External Device Subsystem to get an ID of the plugged device. (USB flash VID, PID, Serial).

Done via windows registry.


Any plans for moving to Symf 3.1?

I'm working on a small project built around Symf 3.1 and current dependency limits installation to 3.0

Found a working combination:
    "minimum-stability": "dev",
    "require": {
        ...
        "rch/jwt-user-bundle": "dev-restrict_fosuser"
        ...

but this implies, as seen above, a change in the minimum stability. :)

Hello @CristianSitov
The bundle actually supports symfony 3.1 on a technical pov, but not in a stable release at the moment.
That's because the friendsofsymfony/user-bundle dependency causes some conflicts.
Here is how you can make it works.
First, install FOSUB in its 2.0 version (stability dev):
composer require friendsofsymfony/user-bundle:~2.0-dev

Then, require the bundle in its 2.0.x-dev version:
composer require rch/jwt-user-bundle:2.0.x-dev

And it should work as expected, involving to have a minimum-stability to dev, as you pointed out.
IMO this installation process is not something that I can write in a README, so it's a workaround.
The restrict_fosuser branch is here to work on this way, trying to remove ~1.3  from friendsofsymfony/user-bundle: ~1.3|~2.0 and make the bundle directly usable via composer require rch/jwt-user-bundle:2.0.x-dev, pending a stable release that should be draft right after.
Please don't close this issue while this bundle is not properly installable on symfony 3.1.
Thank you!

Awesome! Will keep this open.
Thanks!


fBitFlags is strange

fBitFlags is defined as a unsigned char. However, TGRSIDetectorHit seems to be trying to hold all of the flags for itself and the derived detector hit classes.  I'm hoping this is just for the enumeration, and we aren't planning on storing the info here.
The clear function says fBitFlags = fBitflags&0xff00. Why not just set it to 0? This is probably going to be closable pretty quickly, just throwing out some of the weirdness I've seen while trying to make it always be forced to write as 0 to the tree.

@pcbend we can kill the problem once and for all with custom streamers for each thing in the tree. I cannot for the life of me make the streamer get called during sorting. If we have access to the copy of the hit/fragment that is getting written to the tree, we are done with this problem.

we can do that.  I don't think we even want to use the streamer while
sorting - in general I think they are pretty slow.  I should have some time
this weekend to look into it a bit deeper.
On Fri, Oct 28, 2016 at 1:08 PM, Ryan Dunlop<EMAIL_ADDRESS>wrote:

@pcbend https://github.com/pcbend we can kill the problem once and for
all with custom streamers for each thing in the tree. I cannot for the life
of me make the streamer get called during sorting. If we have access to the
copy of the hit/fragment that is getting written to the tree, we are done
with this problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/812#issuecomment-256975278,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAacI7HSa93Hz0JIWSjfp2F8g78xzqnKks5q4iwWgaJpZM4KjlbI
.

Here is the goal. I'm assuming you are caught up with the branched, parallel, loop sorting? We need to be able to do things like SetEnergy etc for our histogrammer and maybe analysis builder, but we don't want to write those set energy things to disk. This means that when the fragment or event gets sent to be filled into the tree it has its bits reset in a way that can't be touched by the other loops.
I have an idea how to get around this. We could have setter functions that get called during sorting that are different than the setters called during playback via a global flag, or "constness". The playback setters would set fBitFlags while the sorting ones do not.

Wait...couldn't we just make class TSortFragment : public TFragment with overridden getters and written to the tree as a fragment? Then you only use the sort classes while sorting? Then we don't have to worry about locking anything at any point, and the fBits will always be zero regardless of getters that we use in the sort fragment. The only line in the entire code that would need to change is when you create the fragment instead of TFragment *frag = new TFragment we use TFragment *frag = new TSortFragment.

I believe Vinzenz solved this by writing copies of TGRSIDetectors and TFragments to the trees


Slack integration

Just curious, but I was wondering if there was interest in installing slack integration to clisops (and possibly other repositories)? I'm not sure if the roocs team uses slack, but it's useful in that the slack integrations allows you to watch issues and PRs on slack with build checks updated in real-time.
We presently use it for some Bird-house/PAVICS repositories (xclim included). Seems like a good fit for coordinating efforts/conversing. For more info: https://github.com/integrations/slack

Thanks @Zeitsperre, we do use Slack integrations with some github projects. We can discuss this when we meet.


[Accordion] Accordion-Item won't work with other elements than

Hi together, I found a Bug with the current version (6.1.2).
Accordion-Items won't open or close when you use another element than li for the Accordion-Items.
However I found out, that updating jQuery to version 2.2.0 solves this issue.
I created a Fiddle to demonstrate the issue. The Fiddle includes two Accordions, the first is build with ul and li markup. The second one is build with div markup. As long as jQuery 2.2.0 is included both versions work. If you change jQuery to the current version which is required by Foundation the second example will break.
https://jsfiddle.net/tobiasmalikowski/fd2av3r7/
Here is the link to the docs:
http://foundation.zurb.com/sites/docs/accordion.html
Quote from docs: Note that the data-accordion-item attribute on each list item is required when not using li.

I'm seeing this was patched in 6.0.6 and works in the codepen http://codepen.io/rafibomb/pen/XXQWBM
The current tested version is jQuery 2.2 - we'll be testing an upgrading to 3.0 in a later release.
For now staying on 2.2 is best
bower install jquery#2.2 --save

I put together a test case for accordion item attributes. It verifies that each of these use cases are working:

Items as
s
Items with data-accordion-item
Accordions that mix both methods

The way the initializer code was written, if you had any
s, it would skip checking for data-accordion-item, but now it just checks for both at the same time.
I also tested in jQuery 2.1.4 and 2.2.0 and saw no differences.


Why is vue-resize-directive not firing?

three  steps

npm install vue-resize-directive --save

// ES6
import resize from 'vue-resize-directive'
//...
export default {
    directives: {
        resize,
    }
//...

3.<div v-resize="onResize">
finnally   div  no effect

What is your implementation of onResize method?
What is the scenario you are testing and give "no effect"?

@David-Desmaisons  thank you very much ，I wrongly thought this Library was used to resize Dom 。 。
sorry 。 and  i suggest  your project name shoud be  vue-resize-listen


require of pure ESM module is not supported

I am trying to use https://github.com/remarkjs/react-markdown#install (pure ESM package) in my project that is set up with loadable-components but on the server side I am getting an error like:
loadable-components: failed to synchronously load component, which expected to be available {
  fileName: '/Users/behlul/dev/project/client/src/client/pages/Page.js',
  chunkName: 'pages-Page',
  error: 'require() of ES Module /Users/behlul/dev/project/client/node_modules/react-markdown/index.js from /Users/behlul/dev/project/client/src/client/pages/Page.js not supported.\n' +
    'Instead change the require of index.js in /Users/behlul/dev/project/client/src/client/pages/Page.js to a dynamic import() which is available in all CommonJS modules.'
}
Error [ERR_REQUIRE_ESM]: require() of ES Module /Users/behlul/dev/project/client/node_modules/react-markdown/index.js from /Users/behlul/dev/project/client/src/client/pages/Page.js not supported.
Instead change the require of index.js in /Users/behlul/dev/project/client/src/client/pages/Page.js to a dynamic import() which is available in all CommonJS modules.
    at Object.newLoader [as .js] (/Users/behlul/dev/project/client/node_modules/pirates/lib/index.js:104:7)
    at Object.<anonymous> (/Users/behlul/dev/project/client/src/client/pages/Page.js:24:45)

My babel config is like below:
{
  "presets": [
    [
      "@babel/env",
      {
        "targets": {
          "edge": "17",
          "firefox": "60",
          "chrome": "67",
          "safari": "11.1"
        },
        "useBuiltIns": "usage",
        "corejs": "3.6.4"
      }
    ],
    "@babel/preset-react"
  ],
  "plugins": [
    "@babel/plugin-syntax-export-default-from",
    "@loadable/babel-plugin"
  ]
}

What can be the issue here? Or to put it in other way, how can we use pure ESM modules with loadable?

The error is

require() of ES Module /Users/behlul/dev/project/client/node_modules/react-markdown/index.js from /Users/behlul/dev/project/client/src/client/pages/Page.js not supported.

The proposed solution is to use dynamic import, but the problem is we need to to synchronously load component, which is not possible using dynamic import.

The origin of the problem is nodejs and your webpack configuration marking all node_modules as external, thus keeping them under nodejs control. And this is a setting you want to have.
A solution i can propose and the one you need to check - try to hide this dependency behind a local file

src/client/pages/Page.js -> loadable(() => import('../../services/react-markdown'))
⬇ "indirection" ⬇
src/services/react-markdown -> export { default } from 'react-markdown';

However I am not sure that will work. ESM modules are not really supposed to be "required" even via indirection.
If this trick will not work for you - try imported-component as it does not transform imports (by the cost of importing everything at server side)

Thanks, I ended up using webpack to transpile the esm modules that created the issue.
here is an example webpack 4 config that would transpile some node_modules and create a bundle with them for SSR (probably it has some unnecessary things such as loadable plugin as i didn't optimize it fully but it got the job done):
var path = require("path")
const nodeExternals = require('webpack-node-externals')
const LoadablePlugin = require('@loadable/webpack-plugin')

const paths = require('./config/paths');
console.debug("Paths are:", paths)

const imageInlineSizeLimit = parseInt(
  process.env.IMAGE_INLINE_SIZE_LIMIT || '10000'
)

var commonLoaders = [
	{ test: /\.js$/, loader: "jsx-loader" },
	{ test: /\.png$/, loader: "url-loader" },
	{ test: /\.jpg$/, loader: "file-loader" },
];

var outputPath = path.join(__dirname, "build-server")
var publicPath = "assets/"

const isEnvProduction = true;

module.exports = [
	{
		// The configuration for the server-side rendering
		name: "server-side rendering",
		entry: "./src/server/app.js",
		target: "node",
		output: {
			path: outputPath,
			filename: "bundle.js",
			publicPath: publicPath,
      library: "server",
      libraryExport: 'default',
			libraryTarget: "commonjs"
		},
		externals: [nodeExternals({
      allowlist: ["react-markdown", /vfile/, "unified", "bail", "is-plain-obj",
        "trough", "remark-parse", /micromark/, "decode-named-character-reference",
        "character-entities", /remark/, /mdast/, /unist/, /trim-lines/,
        /property-information/, /hast/, "space-separated-tokens", "comma-separated-tokens",
        /ccount/, /markdown/
      ]
    })],
		module: {
      strictExportPresence: true,
      rules: [
        // Disable require.ensure as it's not a standard language feature.
        { parser: { requireEnsure: false } },

        // First, run the linter.
        // It's important to do this before Babel processes the JS.
        {
          test: /\.(js|mjs|jsx|ts|tsx)$/,
          enforce: 'pre',
          use: [
            {
              options: {
                cache: true,
                formatter: require.resolve('react-dev-utils/eslintFormatter'),
                eslintPath: require.resolve('eslint'),
                resolvePluginsRelativeTo: __dirname,

              },
              loader: require.resolve('eslint-loader'),
            },
          ],
          include: paths.appSrc,
        },
        {
          // "oneOf" will traverse all following loaders until one will
          // match the requirements. When no loader matches it will fall
          // back to the "file" loader at the end of the loader list.
          oneOf: [
            // "url" loader works like "file" loader except that it embeds assets
            // smaller than specified limit in bytes as data URLs to avoid requests.
            // A missing `test` is equivalent to a match.
            {
              test: [/\.bmp$/, /\.gif$/, /\.jpe?g$/, /\.png$/],
              loader: require.resolve('url-loader'),
              options: {
                limit: imageInlineSizeLimit,
                name: 'static/media/[name].[hash:8].[ext]',
              },
            },
            // Process application JS with Babel.
            // The preset includes JSX, Flow, TypeScript, and some ESnext features.
            {
              test: /\.(js|mjs|jsx|ts|tsx)$/,
              loader: require.resolve('babel-loader'),
              options: {
                presets: [
                  [
                    "@babel/env",
                    {
                      "targets": {
                        "edge": "17",
                        "firefox": "60",
                        "chrome": "67",
                        "safari": "11.1"
                      },
                      "useBuiltIns": "usage",
                      "corejs": "3.6.4"
                    }
                  ],
                  "@babel/preset-react",
                  "@babel/preset-typescript"
                 ],
                plugins: [
                   "@babel/plugin-syntax-export-default-from",
                   "@loadable/babel-plugin"
                ],
                // This is a feature of `babel-loader` for webpack (not Babel itself).
                // It enables caching results in ./node_modules/.cache/babel-loader/
                // directory for faster rebuilds.
                cacheDirectory: true,
                // See #6846 for context on why cacheCompression is disabled
                cacheCompression: false,
                compact: isEnvProduction,
              },
            },
          ],
        }
      ],
    },
    plugins: [
      new LoadablePlugin()
    ]
	}
]

after this i could run the app as node build-server/bundle.js and loadable-components worked with no issues. build-server is still only 232 kb so seems like a good solution unless there are tons of node_modules to transpile.


Saved login suggestion not working in iOS app

Describe the bug
After having downloaded the Railsdevs iPhone app, when you go to log in you're not presented with your saved login from 1Password/iCloud keychain. You have to go search for it. I have confirmed it works as expected in Safari when not using the app.
To reproduce
Steps to reproduce the behavior:

Download iOS app from the App Store
Go to the sign in page
Tap on the email field
No suggested login pops up, you have to search

Expected behavior
I expected iOS would've suggested my saved login information to be used
Actual behavior
iOS didn't suggest my saved login to be used
Additional context
I have verified that my saved login information is suggested on railsdevs.com using Safari on iPhone. I'm not seeing the same behavior when using the iOS Railsdevs app.

This is what I have in 1Password

Adding www in front of railsdevs.com in 1Password doesn't make a difference either - just tried to see if that was it

Interestingly, iCloud passwords find it OK.

Yep. Works fine for me with iCloud passwords as well - I missed that earlier, my bad. It was early :D

Closing this because iCloud passwords is good enough for me, for now.


Add: Tracker history position:

URL: https://graph.tractive.com/3/tracker/{tracker_id}/positions
Method: GET
Parameters:

time_from: Start time for position data retrieval.
time_to: End time for position data retrieval.
format: Data format (json_segments in this case).

Purpose: This URL is used to retrieve the position data for a specific tracker within a specified time range.

I create pull request https://github.com/zhulik/aiotractive/pull/22


Parallelise on HPC

Running well on google cloud but could parallelise on HPC

Parallelised on Cloud. HPC would be overkill


Stop patching vm.spec.{instancetype,preference}.revisionName and instead update vm.status

/area instancetype
/cc @rmohr
What happened:
At present the VirtualMachine controller will directly patch vm.spec.{instancetype,preference}.revisionName when a new ControllerRevision is captured for the associated resource. By doing this we potentially break declarative management systems who expect the core spec of the VirtualMachine to not change post admission. For more on this particular topic see the following sig-architecture document:
https://github.com/kubernetes/community/blob/f88bbbabe89e01bd8f436c339128154e4032d0d5/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
If possible we should stop patching vm.spec.{instancetype,preference}.revisionName and instead hold this information somewhere under  vm.status.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Additional context:
Environment:

KubeVirt version (use virtctl version): N/A
Kubernetes version (use kubectl version): N/A
VM or VMI specifications: N/A
Cloud provider or hardware configuration: N/A
OS (e.g. from /etc/os-release): N/A
Kernel (e.g. uname -a): N/A
Install tools: N/A
Others: N/A

Do we have an explicit example for this? E.g. ArgoCD being unhappy with a VM that was mutated? IIRC ArgoCD should not mind about fields being added which it does not have in its manifests to deploy.

This is in general a complex topic and there is no clear behaviour across different components. Just to outline different solutions which try to cope with defaulting or unpredictable values added differently:

some components (often operators) have the desire to keep a spec exactly in place and actively revert out-of-band changes. They literally do a DeepEqual check and "normalize" the objects before for values which get defaulted or added at runtime (e.g. IP on service is a classical example here in kubevirt and also many openshift operators).
some components treat it as a user error when underlying components are changed behind their back. They typically annotate the managed object and do not perform a deep equal check. Some keep internal revisions to be able to efficiently detect spec changes. That is especially common where a "useless" rollout is expensive. Like a VM restart. Some just check if their own spec changed and then just hammer over the owned objects.
some just periodically "apply" and "delete" and don't care about anything else

All these solutions exist and are in use. Especially higher level objects like Deployment, DaemonSet, VirtualMachine, ... typically don't default via webhooks or controllers, since they are typically the main entrypoint for users and user-owned automation. I am not aware of any hard rule, but we cause less trouble if we just keep the spec as is.
If operators are doing deepequal checks (very strict on avoiding behind-the-back misconfigurations) or go with revisions (with revisions being immune against webhook modifications and the like) is often a matter of project priorities and taste.

Also I'm not sure if we should store this information in the status of a VM. IIRC the status should always be reconstructable from the current state, while a change like this would make it impossible.

Idepdendent of the above: I think the revision information is a classical case for storing in the status. If a revision still exists when a VM gets recreated is absolutely not clear for users. The internally generated revision number is:

neither guaranteed to still exist when the VM gets created
nor transferable across clusters.

Also an instance type may no longer exist, but then this is ok, since we talk about direct managed objects.

/reopen
/remove-lifecycle rotten

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale


About Page Deletions - "Our Partners"

On the "Our Team" page, please delete the "Our Partners" section in its entirety.
https://mapletestimony.org/about/our-team

Hey @mvictor55 . I can work on this. Just to confirm, do you want the our partners section deleted as well as all the child components that are only used by this?

Sure. Update me and I can work on this.

Hey @mvictor55. Just to get it right, we need to remove the "Collaborators" section along with any child components that are being used by this section only.


Consider changing default TTL for the multicast datagrams

Currently, porla makes use of the default TTL (Time-To-Live, see for example: https://docs.oracle.com/cd/E19683-01/816-5042/sockets-137/index.html) which is 1, i.e. bound to the same subnet.
This leaves room for potential clashes between multiple users of porla on different hosts in the same subnet which is probably not the expected behavior. Perhaps the default should be 0 (constrained to the same host) with a user option to widen it?
Related to #11

Closed by #12


Linux+TFVC checkout failures after Azure DevOps 2020 RC1 upgrade

Agent Version and Platform
Version of your agent? 2.170.0/2.172.2 with tf cli 14.134.0 (team explorer every where)
OS of the machine running the agent?Ubuntu 18.04+20.04
Azure DevOps Type and Version
If on-premises, which release? Azure DevOps 2020 RC1
What's not working?
After upgrading to Azure DevOps 2020 RC1, pipelines checking out from TFVC that had jobs running on a linux build agent began failing.
The jobs failed at the checkout stage and continued failing after upgrading to vsts-agent-linux-x64-2.172.0.tar.gz and 2.172.1
##[error]Exit code 100 returned from process: file name 'tf', arguments 'workspaces -format:xml "-collection:https:///" -jwt:*** -noprompt'.
Note that the 'tf' command actually outputs the workspaces correctly, what it does after that fails - when we enable debug logging on the pipeline there is no more information - the text output looks fine but the exit code is not acceptable.
We gathered more details on the failures by adding a ~/.microsoft/Team Foundation/4.0/Configuration/log4j-teamexplorer.properties to enable debug logging.
it appears that the tf command hits four urls with the same JWT, the first three work fine but the last fails with a HTTP 401

/tfs//Services/v3.0/LocationService.asmx		-> ok 200
/tfs//VersionControl/v4.0/repository.asmx		-> ok 200
/tfs//VersionControl/v4.0/repository.asmx		-> ok 200
/tfs/TeamFoundation/Administration/v3.0/LocationService.asmx	-> 401

I eventually got pipelines working again by replacing 'tf' with a script to

always return exit code 0
suppress the output of "No workspace matching..." strings which looked it inhibit xml parsing of the workspace lists

I can provide more logs but there is no more useful information in the pipeline/agent logs. This is more a problem of the compatibility of the 'tf' application and whatever is invoking it.

Would be nice to know if anyone knows of anyone successfully using TFVC on a linux build agent with Azure DevOps 2020 RC1...
I struggle to understand how it could work with the 'No workspace matching...' string issue.

Does anyone use TFVC on Linux agents? test it? Support it?
You just need to have a minimal pipeline that simply checks out a file from TFVC on a linux build agent to reproduce this problem.

Does anyone use TFVC on Linux agents? test it? Support it?
You just need to have a minimal pipeline that simply checks out a file from TFVC on a linux build agent to reproduce this problem.
Would really appreciate it if someone with a linux agent could quickly test this.

@MaximMalygin @RuslanRasulovAkv Please take a look at this issue.
@JonathonQuinn This sounds like the following known issue with tf and newer versions of Java, in which case using Java 8 should work.

@mjrogheliaI @JonathonQuinn  I think it's two different errors. In mentioned issue error raised by 'tf -eula accept' command and in this one we have error in 'workspaces' command ( which follows 'tf eula -accept' ). We investigate this problem and hope provide more information soon.

@JonathonQuinn @MaximMalygin @mjroghelia  I've tested it with downgraded version of Java and had the same error with:
Exit code 127 returned from process: file name 'tf', arguments "workspaces"
I'll try to provide some updates soon.

https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-linux?view=azure-devops-2020

If you'll be using TFVC, you will also need the Oracle Java JDK 1.6 or higher. (The Oracle JRE and OpenJDK are not sufficient for this purpose.)

Is this still the official position? the 'known issue' mjroghelia posted suggests OpenJDK is kinda supported (yay)
Here is the java version on our 18.04 build agent
linuxbuildagent@gglvbuild06:~$ /usr/bin/java -version
openjdk version "1.8.0_265"
OpenJDK Runtime Environment (build 1.8.0_265-8u265-b01-0ubuntu2~18.04-b01)
OpenJDK 64-Bit Server VM (build 25.265-b01, mixed mode)
linuxbuildagent@gglvbuild06:~$ which java
/usr/bin/java
linuxbuildagent@gglvbuild06:~$ ls -l /usr/bin/java
lrwxrwxrwx 1 root root 22 Aug 12  2019 /usr/bin/java -> /etc/alternatives/java
linuxbuildagent@gglvbuild06:~$ ls -l /etc/alternatives/java
lrwxrwxrwx 1 root root 46 Aug 12  2019 /etc/alternatives/java -> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java

@JonathonQuinn  The default version for java on Ubuntu 18 is openjdk 1.8.0_265 which you mentioned. Could you please check the JAVA_HOME variable in your machine? Is it set and is it have a correct path?

@RuslanRasulovAkv JAVA_HOME is not set for the user account that I can log in with and we register the build agents with.
The build agents do have a 'java' system capability which is set to '/usr/bin/java'
I don't believe there are any alternative jvm implementations available
linuxbuildagent@gglvbuild06:/usr/lib/jvm$  ls -l
total 4
lrwxrwxrwx 1 root root   20 Jul 18  2019 java-1.8.0-openjdk-amd64 -> java-8-openjdk-amd64
drwxr-xr-x 5 root root 4096 Aug 12  2019 java-8-openjdk-amd64
linuxbuildagent@gglvbuild06:/usr/lib/jvm$ cd ..
linuxbuildagent@gglvbuild06:/usr/lib$ find . -name 'java'
./jvm/java-8-openjdk-amd64/jre/bin/java
./jvm/java-8-openjdk-amd64/bin/java
linuxbuildagent@gglvbuild06:/usr/lib$ cd /usr/bin
linuxbuildagent@gglvbuild06:/usr/bin$ find . -name 'java'
./java
linuxbuildagent@gglvbuild06:/usr/bin$ ls -l java
lrwxrwxrwx 1 root root 22 Aug 12  2019 java -> /etc/alternatives/java

@JonathonQuinn  Azure-pipeline-agent use java with the help of JAVA_HOME variable and if it is not set you should do it, otherwise agent will not be able to find java.

@JonathonQuinn would you have a chance to see comments from @RuslanRasulovAkv

I have seen it - it confuses me as I would expect the 'tf' executable to not operate at all if Java could not be found...
I do want to test this but other critical priorities at the moment.

We have added JAVA_HOME="/usr/lib/jvm/java-8-openjdk-amd64" to /etc/environment, rebooted the the machine, reconfigured and restarted the agent. The agent .env file now contains JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64 and a test build with a 'Command Line Script' task could echo $JAVA_HOME and printenv showed that JAVA_HOME was present as expected.
But when we try fetch source code out via TFVC it still fails...
~/.microsoft/Team Foundation/4.0/Logs/teamexplorer-clc-2020.09.08-00.50.53.log :
Caused by: com.microsoft.tfs.core.ws.runtime.exceptions.UnauthorizedException: Authorization failure connecting to 'https://ggltfs.local.gallagher.io/tfs/TeamFoundation/Administration/v3.0/LocationService.asmx' (authenticating using credentials (OAuth JWT Credentials))

Can anyone confirm that they have Linux+TFVC pipelines working with Azure DevOps 2020 RC1?
I don't know if we're the only one attempting this or everyone else has no problems...

@JonathonQuinn  I can confirm it. Today i run build pipeline inside docker (with Ubuntu 18.04) and Azure DevOps RC2 and had no errors ( RC2 and RC1 have no changes which can influence on your error, the reason of error is on agent side). In docker i run
"apt-git install openjdk-8-jdk" to install appropriate version of java (the "java -version" returned  openjdk version "1.8.0_265" )
But i run it with the latest version of agent ( 2.174.2 ) and according your logs you used the old one ( 2.170.1 )

Thanks @RuslanRasulovAkv

...RC2 and RC1 have no changes which can influence on your error, the reason of error is on agent side)...

We actually experienced errors immediately after upgrade, before agents upgraded. There error is a server side rejection of the authentication attempt. I do wonder if some weird obscure permissions option has been changed but we've investigated all we can find in that area.
We will be updating to RC2 some time in the future, I'll update as to the results.

@JonathonQuinn Ok, excellent! Can we help you elsewhere?

Can you run the build with debug logging on and report whether the text 'No workspace matching...' is output by the 'tf' utility?
From my testing it runs the tf utility to check no workspaces exist after deleting the appropriate one...and since there are no results outputs this string, but then the agent barfs because this is not correct xml.
Would really appreciate if you posted the entire logs of the build with debug logging enabled so I can compare ours

logs.zip
Here my test build logs. Hope they will be useful for you.

@JonathonQuinn Can we close this issue?

Thanks @RuslanRasulovAkv but the file "Checkout testProject@ to s.txt" is truncated...so none of the useful content is present
I would like to confirm RC2 fixes this issue before closing.

logs.zip
Here the full logs ( with 'No workspace matching...' in Checkout step. )

Thanks @RuslanRasulovAkv
After further testing I don't believe the 'No workspace matching...' text is a problem.
The problem is that when it exits with code 100 no xml is output.
My new workaround script is now
#!/bin/bash
# rename 'tf' command as 'tfreal' and install this as 'tf'
TFOUT=$($(dirname "$(readlink -f "$0")")/tfreal "$@")

printf '%s\n' "$TFOUT"
if [[ "$TFOUT" == *"No workspace matching"* ]]
then
        printf "<\?xml version=\"1.0\" encoding=\"utf-8\"?><workspaces/>"
fi
exit 0

One thing that has jumped out at me is that we are using a project team collection which changes some of the URLs
https://docs.microsoft.com/en-us/azure/devops/server/admin/manage-project-collections?view=azure-devops-2020#:~:text=A group of projects is,within that collection can use.

tf workspaces -format:xml "-collection:https://dev.azure.com/v-rurasu/" -jwt:*** -noprompt
...
No workspace matching *;**ProjectName** Build Service (v-rurasu) on computer eb7817e534a2 found in Team Foundation Server https://dev.azure.com/v-rurasu/.
<?xml version="1.0" encoding="utf-8"?><workspaces/>

@JonathonQuinn Have the update of tfs version helped you? If yes can we close this Issue?

We have not updated to Azure DevOps 2020 RC2 yet, will update with my results.
Do you know of a specific fix in that release that would fix this problem?

@JonathonQuinn Not at all, we still investigate this issue. Can you provide the full log in debug mode?

Tee <IP_ADDRESS>010141426 has fix our issues but only after I copied slf4j-api-1.7.19.jar and slf4j-log4j12-1.7.19.jar into the lib directory from <IP_ADDRESS>804261732.

It failed due some gnome keyring dependency without it
https://github.com/microsoft/team-explorer-everywhere/issues/323

Close as Tee was upgraded and it seems resolved this item. (no activity for 180 days).

https://github.com/microsoft/azure-pipelines-agent/issues/3423#issuecomment-852128925


enhance(typeahead): Application details now popup when application na…

…me is selected in typeahead AMLNG-114
Currently when an option in the type down is selected it just replaces the search term and does another search which now thanks to smart search will return more than the exact name of the application. Instead the desired behavior is when the name of the app is selected in the drop down it will also open the application as if the search result was single clicked
Acceptance criteria:
Type in a search result into the search bar
Select one of the applications listed in the dropdown
The application preview is opened as if it were single clicked from the search result page.
Other existing behavior is not changed

@akonsowski @blynch11p @rkenyon1969

Note: Need to pull backend master branch for this to work right

Looks good :+1:
Unrelated to the checkin, but related to the suggestion list...
Is/was there a style for the suggestion list for mouseover or arrow up/down to highlight what's selected?  Both of the dropsdown to the right show a hover indicator. I'd expect this to be similar.

:+1:


Can I make a footer for the website.

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like

A clear and concise description of what you want to happen.

I would like to work on the issue.

@sairish2001 do we need a footer? Please Have a look on this issue

It's more likely a webapp, rather than website, so no need of any footer.
Thanks


Images hosted outside of Imgur

Some channel images are hosted outside of Imgur which makes it impossible to request a scaled version on the fly.

All the images are hosted are linked to the https://github.com/iptv-org/database repo.
Feel free to submit a PR if you would like to change some of the images.


Missing release items for releases after 5.3.0

We recently tried to update OpenLayers in OSGeoLive and realized that the dist zip package is available up to 5.3.0 release.
Can you please provide provide the dist package for 5.3.3?

https://github.com/OSGeo/OSGeoLive/blob/master/bin/install_openlayers.sh#L40

see https://github.com/openlayers/openlayers/releases/tag/v5.3.3

We stopped providing distribution archives for bugfix releases. We encourage our users to use the npm package. @kalxas, what is the dist archive used for on OSGeo Live?

I find these really useful for playing around in sites like codepen. What are my options when using a site like this?

codesandbox.io is a similar site that works with npm packages. We use that also for the examples now. See https://openlayers.org/en/master/examples/

OK thanks good to know


Update config to 2.0

Signed-off-by: Felix Wong<EMAIL_ADDRESS>

@radcortez Please review, thanks!


Customtkinter integration?

Will this project ever be converted to use customtkinter? Or maybe somehow allow the video player to work with ctk apps?

@dishb you can easily use this with customtkinter.  Refer https://github.com/PaulleDemon/tkVideoPlayer/discussions/23#discussioncomment-4475005.

@dishb you can easily use this with customtkinter. Refer #23 (comment).

Did not see that for some reason 😅 Thank you!


Transfer repo to me?

Yo -- you want to transfer this over to me since, as you said, you don't use it much anymore?

Apparently I can't transfer it because you already have a fork. How about we redirect users to your fork in the README?

That's fine by me, but it would be easy to delete the fork on github and just update the remotes locally...

Let's just do that then.

Boom, done

Donezo


Restore state on slave after the fork/exec.

Following change in Hack that use 'Daemon.spawn' to create slave, the
'global references' have to be copied "manually" on slave. This is done
in server/serverWorker.ml.
This is tied with D45423.
PS: This work was done in order to make version 0.19.1 work on
Windows. We couldn't rebase it as it depends on previous PR that have
not been merged in master yet.

@facebook-github-bot import

Sorry, just followed the trail to this PR. Let me test it out.

About commit OCamlPro@97c51d7 Is there any reason not to immediatly take the lock ?

I think grabbing the lock earlier should be fine.

Is there a reason for 'ocamlbuild' not to build Flow with -DOSS_SMALL_HH_TABLE_POWS ?

Hmm, interesting point. I wasn't actually aware of that option. My guess is that it's probably fine.

Could you confirm that your internal CI use a linux kernel < 3.17 and owns a too "small" '/dev/shm' ? In that case, does setting HH_SHMDIR=/tmp fix the problem ? if /tmp is not too small also.

My kernel is 3.10 at the moment, but I have a 71G /dev/shm. When testing with the previous PR, I did notice that some hack tests passed individually but failed when run together, so it could be an out of space thing.

Ok! This has finally been merged as 7 commits:

https://github.com/facebook/flow/commit/e60b1bd7549182342faa105afaa31a8cecc1e1ce
https://github.com/facebook/flow/commit/51f0bfb4d298821d011ddbb693c26dd13d36e9c8
https://github.com/facebook/flow/commit/fa6d3e87fad4e091a7cf11b9fa689f7f220d0918
https://github.com/facebook/flow/commit/8a737f43e6deb107ada8cac9c6e4168cc8a6739e
https://github.com/facebook/flow/commit/5c0b0485f1a6571ed501a50e20a436af7433c0c5
https://github.com/facebook/flow/commit/c94194c6c04e3fb1680abd8fa0a9fafdc2cab280
https://github.com/facebook/flow/commit/77569bc430707b2faebdb2d1b414e8d8ec2a18f8

Yay!

Hi,
I think I stumbled upon an error that is related to this issue.
when flow check is executed as part of a Makefile  or from tmux it fails with exit status 15.
after some digging with strace -ff I saw that a call to fallocate on an /run/shm/fb_heap-.. file fails with EINVAL:
fallocate(3, 0,<PHONE_NUMBER>9741734912, 138) = -1 EINVAL (Invalid argument)
37099 exit_group(15)

I guess it has something to do with the fork/exec or with signal handlers and the deamon creation done in these commits above, cause what else can be so different for a process that is executed from a Makefile...
thanks!


Package request: prettier-plugin-go-template

Project description
Prettier plugin for go template files eg. for the Hugo static site generator.
This is an NPM package.
Metadata

homepage URL: https://github.com/NiklasPor/prettier-plugin-go-template
source URL: https://github.com/NiklasPor/prettier-plugin-go-template
license: mit
platforms: unix, linux, darwin

Add a :+1: reaction to issues you find important.

If I understand correctly, this should be as easy as adding prettier-plugin-go-template to node-packages.json and running generate.sh. Unfortunately my hardware, and especially my internet speed, don't allow me to do this locally. Is there a way around this?


GTA IV has the system mouse cursor stuck over the game after bringing the Steam overlay up and down

The cursor won't go away until the game is restarted. Sometimes it happens sometimes it doesn't.
Software information
Game: Grand Theft Auto IV: The Complete Edition v<IP_ADDRESS>
Graphics API: DirectX 9
Architecture: x86
System information

GPU: GTX 950
Driver: 471.41
DXVK version: 1.9
OS: Windows 10 64-bit (21H1)

Apitrace file(s)
N/A
Log files

GTAIV_d3d9: https://pastebin.com/6PdqCV5z

The problem is still present under DXVK 1.9.3. Curiously, the Rockstar and Reshade overlays don't seem to cause issues.

Yep, the issue is still present.

Don't expect this to get fixed.

It's been there too long to be expecting anything.

steam overlay has been a source of constant joy and happieness for the longest time, so you may want to disable it?

steam overlay has been a source of constant joy and happieness for the longest time, so you may want to disable it?

I have no idea what you're talking about.

as of 2024 DXVK version 2.3.1 issue is still present.
Opening and closing steam overlay while game is running in windowed borderless, makes system mouse cursor be always present on screen. Only possible workaround is to run the game in fullscreen.

DXVK has no interaction with the Steam Overlay in this way. This would probably be a Steam bug.


[CI] add error code utility runner workflows

Signed-off-by: Bariq<EMAIL_ADDRESS>Description
This PR fixes #254
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

This is great to see, @bariqhibat

https://github.com/meshery/meshery-istio/pull/255/checks?check_run_id=3164224134#step:4:7
This particular dependency for meshkit v0.2.17+ is causing multiple checks to fail across multiple repos.
Any idea @mgfeller @utkarsh-pro? :thinking:
see also: https://github.com/meshery/meshery-traefik-mesh/pull/100/checks?check_run_id=3155023285#step:4:7

Hey @DelusionalOptimist I think we also need to use go get github.com/layer5io/meshkit/cmd/errorutil to get the latest version of the meshkit ?

Hey @DelusionalOptimist I think we also need to use go get github.com/layer5io/meshkit/cmd/errorutil to get the latest version of the meshkit ?

No @sayantan1413 this adapter uses a newer version of meshkit already. So no worries : ).

Oh okay got it 👍

https://github.com/meshery/meshery-istio/pull/255/checks?check_run_id=3164224134#step:4:7
This particular dependency for meshkit v0.2.17+ is causing multiple checks to fail across multiple repos.
Any idea @mgfeller @utkarsh-pro? thinking
see also: https://github.com/meshery/meshery-traefik-mesh/pull/100/checks?check_run_id=3155023285#step:4:7

@DelusionalOptimist this looks familiar, for this specific library. It used to pass after a while, as far as I can remember.

https://github.com/meshery/meshery-istio/pull/255/checks?check_run_id=3164224134#step:4:7
This particular dependency for meshkit v0.2.17+ is causing multiple checks to fail across multiple repos.
Any idea @mgfeller @utkarsh-pro? thinking
see also: https://github.com/meshery/meshery-traefik-mesh/pull/100/checks?check_run_id=3155023285#step:4:7

@DelusionalOptimist this looks familiar, for this specific library. It used to pass after a while, as far as I can remember.

Re-run jobs, and this error did not occur anymore, some tests are failing though.

#255 (checks)
This particular dependency for meshkit v0.2.17+ is causing multiple checks to fail across multiple repos.
Any idea @mgfeller @utkarsh-pro? thinking
see also: meshery/meshery-traefik-mesh#100 (checks)

@DelusionalOptimist this looks familiar, for this specific library. It used to pass after a while, as far as I can remember.

Re-run jobs, and this error did not occur anymore, some tests are failing though.

Great!
Don't know about this test https://github.com/meshery/meshery-istio/pull/255/checks?check_run_id=3165350665.
It has always been failing :confused:


[Feature] Support for SVGs, images and more

Fix for https://github.com/Laravel-Backpack/basset/issues/84.

Added FileOutput helper.
Basset now outputs the most common file extensions.

Basset Output is now much more organized, and all the available output file extensions are in separate blade files 🎉
How fancy is that!?

Awesome! Muuuuch cleaner, I like it. Now let's please document and test this. Steps:

[ ] We merge https://github.com/Laravel-Backpack/basset/pull/85 so we can work on that newer README.
[ ] We improve the section about the @basset() directive, to list all the file types it now treats, and what the output is for each one.
[ ] Two-three people test this.
[ ] We merge and tag this as 1.3.0

We improve the section about the @basset() directive, to list all the file types it now treats, and what the output is for each one.

Added a table with the know extensions 🙌

Two-three people test this.

Assigned here @pxpm, @karandatwani92, @phpfour, if any of you guys can, please give this a quick test 🙌

<!DOCTYPE html>
getLocale()) }}">

    CSS & JS
    @basset('https://cdn.jsdelivr.net/gh/RobiNN1/elFinder-Material-Theme/Material/css/theme.min.css')
<EMAIL_ADDRESS>
    Image
    @basset('https://backpackforlaravel.com/presentation/img/backpack/logos/backpack_logo.svg')

    Audio/Video
    @basset(base_path('vendor/studio-42/elfinder/sounds/rm.wav'))
    @basset('https://download.samplelib.com/mp4/sample-5s.mp4')

    ICO
    @basset('https://www.learningcontainer.com/wp-content/uploads/2020/09/Sample-ICO-file-Download-for-testing.ico')

    PDF
    @basset('https://www.africau.edu/images/default/sample.pdf')

    VTT
    @basset('https://gist.githubusercontent.com/samdutton/ca37f3adaf4e23679957b8083e061177/raw/e19399fbccbc069a2af4266e5120ae6bad62699a/sample.vtt')

Output

Tags are OK ✅
NOT CACHED❌  - I tried php artisan basset:fresh not resolved.

Hey @karandatwani92, by default on local development dev_mode is active, so yes, no cache.
'dev_mode' => env('BASSET_DEV_MODE', env('APP_ENV') === 'local'),
In order to test cache locally you should add BASSET_DEV_MODE=false to your .env.


Crashes if port 9000 blocked

How to reproduce:

run an app that listen's on port 9000 (like https://cider.sh or netcat -l 9000)
run the first usage example from https://docs.rs/axum-prometheus/latest/axum_prometheus/index.html which uses port 3000, not port 9000.

Result:
thread 'main' panicked at /home/blarsen/.cargo/registry/src/index.crates.io-6f17d22bba15001f/axum-prometheus-0.7.0/src/lib.rs:850:14:
Failed to build metrics recorder: FailedToCreateHTTPListener("Address already in use (os error 98)")
stack backtrace:
   0: rust_begin_unwind
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panicking.rs:652:5
   1: core::panicking::panic_fmt
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/panicking.rs:72:14
   2: core::result::unwrap_failed
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/result.rs:1654:5
   3: core::result::Result<T,E>::expect
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/result.rs:1034:23
   4: <axum_prometheus::Handle as core::default::Default>::default
             at /home/blarsen/.cargo/registry/src/index.crates.io-6f17d22bba15001f/axum-prometheus-0.7.0/src/lib.rs:837:29
   5: axum_prometheus::GenericMetricLayer<T,M>::pair
             at /home/blarsen/.cargo/registry/src/index.crates.io-6f17d22bba15001f/axum-prometheus-0.7.0/src/lib.rs:766:46
   6: prom_test::main::{{closure}}
             at ./main.rs:7:45
   7: tokio::runtime::park::CachedParkThread::block_on::{{closure}}
             at /home/blarsen/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/park.rs:281:63
   8: tokio::runtime::coop::with_budget
             at /home/blarsen/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/coop.rs:107:5
   9: tokio::runtime::coop::budget
             at /home/blarsen/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/coop.rs:73:5
  10: tokio::runtime::park::CachedParkThread::block_on
             at /home/blarsen/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/park.rs:281:31
  11: tokio::runtime::context::blocking::BlockingRegionGuard::block_on
             at /home/blarsen/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/context/blocking.rs:66:9
  12: tokio::runtime::scheduler::multi_thread::MultiThread::block_on::{{closure}}
             at /home/blarsen/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/scheduler/multi_thread/mod.rs:87:13
  13: tokio::runtime::context::runtime::enter_runtime
             at /home/blarsen/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/context/runtime.rs:65:16
  14: tokio::runtime::scheduler::multi_thread::MultiThread::block_on
             at /home/blarsen/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/scheduler/multi_thread/mod.rs:86:9
  15: tokio::runtime::runtime::Runtime::block_on_inner
             at /home/blarsen/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/runtime.rs:363:45
  16: tokio::runtime::runtime::Runtime::block_on
             at /home/blarsen/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/runtime.rs:335:13
  17: prom_test::main
             at ./main.rs:22:5
  18: core::ops::function::FnOnce::call_once
             at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/ops/function.rs:250:5

main.rs for reference, copied from https://docs.rs/axum-prometheus/latest/axum_prometheus/index.html:
use std::{net::SocketAddr, time::Duration};
use axum::{routing::get, Router};
use axum_prometheus::PrometheusMetricLayer;

#[tokio::main]
async fn main() {
    let (prometheus_layer, metric_handle) = PrometheusMetricLayer::pair();
    let app = Router::new()
        .route("/fast", get(|| async {}))
        .route(
            "/slow",
            get(|| async {
                tokio::time::sleep(Duration::from_secs(1)).await;
            }),
        )
        .route("/metrics", get(|| async move { metric_handle.render() }))
        .layer(prometheus_layer);

    let listener = tokio::net::TcpListener::bind(SocketAddr::from(([127, 0, 0, 1], 3000)))
        .await
        .unwrap();
    axum::serve(listener, app).await.unwrap()
}

Cargo.toml:
[package]
name = "prom-test"
version = "0.1.0"
edition = "2021"

[dependencies]
axum = "0.7.5"
axum-prometheus = "0.7.0"
tokio = "1.39.2"

axum-prometheus 0.6.1 does not have this problem.

Don't think this is an issue with axum-prometheus. This error originates from metrics-exporter-prometheus.
0.6.1 does not have this issue, because that code I linked is a very recent change. I'm pretty sure you should file an issue for them.

The documentation for metrics-exporter-prometheus' PrometheusBuilder indicates that it opens port 9000 by default, so it's behaving as documented.

Well, axum-prometheus is clear about using metrics-rs and its ecosystem, so what could we possibly do in the default implementation? There're plenty of ways to work around this via lower level APIs that give you finer control.. basically just don't use pair/pair_from and with_default_metrics functions from this crate. BaseMetricLayer is completely decoupled from the metric exporter initialization code, and you may perform it as you like.
I'd rather not duplicate the documentation of metrics-exporter-prometheus in this crate either.

Ah yeah, it looks like this is a consequence of using PrometheusBuilder::build to ensure the upkeep thread is started, but which also builds an exporter future... which will end up triggered the binding of the port. 😓
I'll have to think a little bit about what a better builder API could look like... because it seems like like this keeps coming up.

I'd rather not duplicate the documentation of metrics-exporter-prometheus in this crate either.

It's not documented that http-listener feature (which overlaps the scope of axum to me). The documentation gives an example that manually wire the rendering code into a axum route. That makes me assume that there would be no other listener otherwise.
Could we disable this feature by default? Downstream users can still enable it if they want (features will merge). But currently, downstream users cannot disable it because it's explicitly enabled via axum-prometheus.

The reason why this crate changed the defaults is because the upkeep task needs to be started in metrics-exporter-prometheus in order to prevent unbound histogram growth, see #52 . This led to an unfortunate consequence that metrics-exporter-prometheus binds the default (or configured) HTTP port.. but that http listener is not used in any way in axum-prometheus .
It's possible to avoid that if you reach for PrometheusMetricLayerBuilder::with_metrics_from_fn and construct the PrometheusBuilder yourself (you either don't care about the upkeep task, or bind a different random port, etc).
I do not intend to disable the http-listener feature, because the crate has essentially no point if you use it with metrics-exporter-prometheus, but you have neither http-listener nor push-gateway enabled.  You have an option to disable the prometheus feature, which is exactly what people should do if they don't want to work with Prometheus.
As a workaround, I could probably start the http listener explicitly on <IP_ADDRESS>:0, so that the operating system will choose an available random port, but I don't think that's a viable solution.. I'd rather like to have the root cause fixed.

Thanks for the explanation and with_metrics_from_fn does work for me.

#52

In my own setup, I use .build_recorder() and manually spawn the upkeeping thread (because I want tokio tasks rather than system threads). Also, leaking threads (there is no way to stop it even though all Handles are dropped) in Default::default sounds so dirty. I'd say I don't like the API design for this. If we need to spawn threads, we should use build_recorder to avoid different behaviors depending on upstream features, and spawn our own upkeeping thread when building PrometheusMetricLayer (if we want to).

I do not intend to disable the http-listener feature, because the crate has essentially no point if you use it with metrics-exporter-prometheus, but you have neither http-listener nor push-gateway enabled.

Why saying "essentially no point"? I do use metrics-exporter-prometheus with default features disabled. As mentioned above, I use .build_recorder(), spawning my own upkeeping thread and run axum for serving the scraping server. It runs perfectly fine and never tries to bind :9000. Thus I don't think http-listener is technically required when having axum.

Why saying "essentially no point"? I do use metrics-exporter-prometheus with default features disabled. As mentioned above, I use .build_recorder(), spawning my own upkeeping thread and run axum for serving the scraping server. It runs perfectly fine and never tries to bind :9000. Thus I don't think http-listener is technically required when having axum.

Oh, maybe I'm just completely off with my mental model. Currently I don't actively use this library, and forgot some stuff. I think it's worth a try then to just disable the default features completely for metrics-exporter-prometheus. I'm not sure when I'll have the find to really work on this, and figure out whether it is a breaking change.
Would you mind sharing your setup code you're using with axum?

Hello, I'm having the same problem. @oxalica do you mind sharing the code for how you worked around this using with_metrics_from_fn?

Resolved this on the master branch, if you can afford to use axum = 0.8.0-alpha1. This is a workaround, and not pretty, but should work.


"Test output" does not show the name of the func generating the output

Can you provide a bit more detail. I'm not sure what circumstances you're looking at here.

What kind of detail? This is the output I see:
...
TEST OUTPUT
[test_TBuffer.c]

"0/F/TBuffer.c:24/Failed to malloc TBuf: No Memory"
"0/F/TBuffer.c:24/Failed to malloc TBuf: No Memory"
""

FAILED TEST SUMMARY
[test_TBuffer.c]
Test: test_TBuf_Create_OK
At line (83): "Expected 0x00000004 Was 0x00000040. Function tmalloc Argument size. Function called with unexpected argument value."

OVERALL TEST SUMMARY
TESTED:  3
PASSED:  2
FAILED:  1
IGNORED: 0

BUILD FAILURE SUMMARY
Unit test failures.
Note that the filename test_TBuffer.c is given under TEST OUTPUT, but not the test function names.
Meanwhile, for the FAILED TEST SUMMARY, both test file and test function names are given, which would be the correct behavior I guess.

On 29 Apr 2016, at 15:19, Mark VanderVoord<EMAIL_ADDRESS>wrote:
Can you provide a bit more detail. I'm not sure what circumstances you're looking at here.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

Sorry, looks like the answer I sent through mail got broken? I'll repeat here.
What kind of detail? This is the output I see:
...
-----------
TEST OUTPUT
-----------
[test_TBuffer.c]
  - "0/F/TBuffer.c:24/Failed to malloc TBuf: No Memory"
  - "0/F/TBuffer.c:24/Failed to malloc TBuf: No Memory"
  - ""

-------------------
FAILED TEST SUMMARY
-------------------
[test_TBuffer.c]
  Test: test_TBuf_Create_OK
  At line (83): "Expected 0x00000004 Was 0x00000040. Function tmalloc Argument size. Function called with unexpected argument value."

--------------------
OVERALL TEST SUMMARY
--------------------
TESTED:  3
PASSED:  2
FAILED:  1
IGNORED: 0

---------------------
BUILD FAILURE SUMMARY
---------------------
Unit test failures.

Note that the filename test_TBuffer.c is given under TEST OUTPUT, but not the test function names.
Meanwhile, for the FAILED TEST SUMMARY, both test file and test function names are given, which would be the correct behavior I guess.

Ah. Ceedling doesn't make any attempt to correlate data that you are manually dumping to stdout with the data that it is looking for. It simply captures it and displays it so that you can use it for whatever you like. This is intentional. In order to correlate it to a test, Ceedling would have to keep that data around, then apply it to the test when it is completed. In addition to this being a lot of overhead for a feature that is seldom used, it could easily be wrong if the output was dumped from setUp, tearDown, the RUN_TEST macro, etc. In any of those cases, you would see the extra output incorrectly assigned to the next completed test.
The output summary is really just there for the convenience of the test writers. The majority of the time, it is completely empty.

OK, I think I understand.
My assumption was that, just as each stderr output is connected to a test function, the stdout would also be connected, and that the problem of not seeing which test function printed something was just a problem in the test result printer.
From what you say, I understand now that in fact the stdout is NOT captured specifically for each test function, and that doing so would be too much overhead. Right? That's a pity, I assumed it would be the same procedure already being done for stderr.
Just to be clear, I can kinda work-around this myself in my tests by adding the printf("%s",__func__); thing as the first line of each test, just to know that the coming text was output by such-and-such test. It's just strange boilerplate. Though I understand that usually (ideally) unit tests don't even use stdout.
So, as a way to reduce the boilerplate in a generic way: would it be possible to have the name of the test be passed to the setUp() function? So I could do something like
void setUp(char * test_func){
    printf("%s",test_func);
}

(... or maybe this isn't even about stderr and stdout and then I'm totally off??)

Actually all the output from stdout is being captured. The part that makes it more challenging is that the name of the test is announced with the results, so it happens at the END of the test. (This is necessary for quite a few reasons, all of which are odd little details. Long ago, we used to print the test name at the beginning and then the pass/fail result at the end of the test... everything else would get inserted in between. this didn't really work very well because people's results parsers would get all messed up by anything they output in the middle).
ANYWAY, it happens at the end now... which means that anything you output would have to get stored away separately, then associated with that test once it was announced. This would be correct most of the time... but if the user chose to write something from setup or teardown or anything like that, it would still get associated with the nearest test, which may not be what they were looking for.
Maybe we add a TEST_INFO_MESSAGE macro to output an info line with whatever you want?

How would that TEST_INFO_MESSAGE macro be used?

It would output the text you pass it, but prefix it with the usual info... maybe something like filename:line:function:INFO:message? I'm just thinking aloud here.

If it is something that could be used in setUp(), then OK. But things like filename, line, function, can already be done with standard compiler-provided macros, so... I don't know.
In general, IMO anything that maximizes info in case of debugging and minimizes boilerplate is good :).


cmake: fix the LLVM linking logic

This pull request fixes the LLVM linking logic when the system contains both shared and static libraries. Currently, even if shared libraries are preferred over static ones, the build system will still link static libraries.
Should fix #1855.
Checklist

[X] Language changes are updated in man/adoc/bpftrace.adoc
[X] User-visible and non-trivial changes updated in CHANGELOG.md
[X] The new behaviour is covered by tests

The commit message was updated to include explanations of why certain changes are needed.

Comments addressed.

Thanks!


Adding The Installation Of Root Dependencies For Npm

Problems
We are faced with the fact that cdxgen does not generate SBOM for a project where the package.json file exists at the root, but the package-lock.json file is missing. In this case, the installDeps dependency installation flag does not initiate the installation of dependencies.
Decision
We have implemented the installation of dependencies with npm for the case when:

There is a package.json file in the root of the project.
The package-lock.json file is missing in the root of the project.
installDeps flag is set to true.

@prabhu Thank you for your recommendation. She's really important. Therefore, we have implemented simple support for choosing a package manager according to the manual https://nodejs.org/api/packages.html#packagemanager and https://nodejs.org/api/corepack.html#supported-package-managers .
At the same time, the logic of the work is such that if the value is not found, then the default npm package manager is used.

@aryan-rajoria wdyt?

Yes I have tried it on juice-shop.


[distributed tensorflow] End of sequence after a few batch with dataset.shard

When running distributed training, my session gets terminated after a few batches when using dataset.shard. The issue disappears when I run distributed training with an independent dataset object on each worker (in which case the same data gets shuffled and read on each worker).
Have I written custom code: No.
OS Platform and Distribution: ubuntu
TensorFlow installed from: standard TF1.5 distribution
Bazel version: NA
CUDA/cuDNN version: CUDA 9.1
GPU model and memory: No GPU
Exact command to reproduce: Cf Below
Dataset construction:
def construct_dataset(filenames, labels, batch_size, num_workers,worker_index):
    dataset = tf.data.TextLineDataset(filenames)
    dataset = tf.data.Dataset.from_tensor_slices((filenames,labels))
    dataset = dataset.shard(num_workers, worker_index) #works fine when commenting this out
    dataset = dataset.shuffle(buffer_size=10000)  # Equivalent to min_after_dequeue=10000.
    dataset = dataset.map(_parse_function)
    dataset = dataset.batch(batch_size)
    return dataset

main
with tf.device(device):
        filelist, labels = get_filelist(FLAGS.data_dir)
        dataset = construct_dataset(...)
        iterator = dataset.make_one_shot_iterator()
        batch = iterator.get_next()
        img_batch, filepath_batch, label_batch = batch
        ...

       hooks=[tf.train.StopAtStepHook(last_step=1000000)]

    with tf.train.MonitoredTrainingSession(master=target,
        is_chief=(FLAGS.task_index == 0),checkpoint_dir=logs,hooks = hooks) as sess:
        try:
            while not sess.should_stop():
                sess.run(train_op)
        except Exception as e:
            print(e)

Stacktrace -
	 [[Node: IteratorGetNext = IteratorGetNext[output_shapes=[[?,300,300,?], [?], [?]], output_types=[DT_UINT8, DT_STRING, DT_INT32], _device="/job:ps/replica:0/task:0/device:CPU:0"](OneShotIterator)]]
	 [[Node: Training_Loss_S17 = _HostRecv[client_terminated=false, recv_device="/job:worker/replica:0/task:0/device:CPU:0", send_device="/job:ps/replica:0/task:0/device:CPU:0", send_device_incarnation=-379211586651304706, tensor_name="edge_133_Training_Loss", tensor_type=DT_STRING, _device="/job:worker/replica:0/task:0/device:CPU:0"]()]]

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

Done.

I apologize, but I don't quite understand the issue here. Could you provide the full stack trace?
Also, a side observation, the first line in construct_dataset seems unnecessary, since the very next line ignores it and creates a new Dataset using from_tensor_slices?

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 29 days with no activity and the awaiting response label was assigned. Is this still an issue?


testing

Type: Other
Summary:
testing
Details:
test
Resolution:
test
Affected definitions:

pyzmq 22.0.2

@nellshamrell Since this is a test, can this be closed?

@capfei - maybe we should clean up the declared field on this one..  Would you agree with "BSD-3-Clause" as the "declared" license here?

@ariel11 I'm leaning to BSD-3-Clause AND LGPL-3.0-or-later since it seems they updated most files to BSD-3-Clause and kept some legacy files as LGPL. Stated here:
https://github.com/zeromq/pyzmq/tree/master/RELICENSE
https://github.com/zeromq/pyzmq/blob/master/docs/source/changelog.rst#220
zmq/core is now under zmq/backend/cython
Even the setup.py states BSD and LGPL. 🤷♀ Those are my two cents, wishy-washy as they may be.

Closing this PR (another PR was opened for this package) - https://github.com/clearlydefined/curated-data/pull/10074

Sorry, forgot to close this after testing. Thanks @ariel11!