Verify the behaviour of opening times in advance of the Christmas/New Year closure

Closure date for Christmas/New Year 2024-25 are now up on the site at https://wellcomecollection.org/visit-us/opening-times.
The library will closed at the end of the day on Friday 20 December 2024 and re-open on Thursday 2 January 2025.
We should do this by w/c 2 December in case anything needs fixing before two weeks before closure on 20 December.
Previous tickets e.g. https://github.com/wellcomecollection/wellcomecollection.org/issues/8976 show how we've tested requesting for previous closures.
There is also some info at https://app.gitbook.com/o/-LumfFcEMKx4gYXKAZTQ/s/DPDDj27NI2F2kPukWrC1/end-of-year-closure
To do

Check requesting will behave as expected over the closure period

weco.org doesn't generate the available dates for requesting anymore so the above process https://github.com/wellcomecollection/wellcomecollection.org/issues/8976 will not work

The content-api /venue route provides the catalogue-api with opening times/available dates for requesting
It can easily be run locally, and uses the same index that the live APIs use (so, same data, same dates)
Running the content-api locally, we can set whatever date we want to test here, then

library
Hit http://localhost:3000/venues?title=library%2Cdeepstore will return a list of nextOpeningDates for both venues

As per our chat just now with @agnesgaroux and @pollecuttn
There are now two things to test, Agnès is currently re-writing the Github document to inform that.

[ ] Test what happens for closed stores in-building (same testing as usual)
[ ] Test what happens for Deepstore material.

For the latter, Agnès is meeting with LE&E on Wednesday to determine what is expected to happen, then we can catch up again and see how Experience can assist.
As this now sits on Prismic/Content API AND Catalogue API logic, it might be that this is a joint effort from both teams for 30mins every December.

Test chats happening on Slack

So I'm unsure how to test this properly without good knowledge of the logic done elsewhere (maybe on the Catalogue API?), which I think affects which dates come through?
Test done so far;

Changed the date in the Content API to pretend we're in Christmas closures.
Run Content API locally (cd api && yarn dev whilst logged on to AWS with the catalogue-developer role)
Go to http://localhost:3000/venues?title=library
See: results.nextOpeningDates

So far, when it's on an exceptional working day (let's say I change my date to be 2024-12-23T14:30:00.000Z), I see that day be the first result in the nextOpeningDates array:
{
"open": "2024-12-23T10:00:00.000Z",
"close": "2024-12-23T18:00:00.000Z"
},
{
"open": "2025-01-02T10:00:00.000Z",
"close": "2025-01-02T20:00:00.000Z"
},
{
"open": "2025-01-03T10:00:00.000Z",
"close": "2025-01-03T18:00:00.000Z"
},
{
"open": "2025-01-04T10:00:00.000Z",
"close": "2025-01-04T16:00:00.000Z"
},

I believe this is because this code removes it from "exceptional closing days" as it's considered to be in the past, even though it's on "day of". Therefore it shows as a nextOpeningDates, even though it probably shouldn't. I'm also not sure about the 2nd showing up, since that gives no time to our colleagues to fetch the work and make it available.
BUT, I believe there is code, probably in the Catalogue API, that removes those from the array, as "day of" will never be considered a valid option. When I inspect the WC.org code, available dates seem to be fetched at this stage. It is where I struggle to further my testing though, as I'm unsure of the spread of the logic, and do not know the Catalogue API. When I run it with today's date, it also returns today and tomorrow, but the first option on the FE is in two days. So I'm thinking it's probably fine, but don't feel comfortable confirming so.
I also feel like this test case makes me really want to be able to connect with local APIs easily for better testing 😄 something @kenoir and I touched on really quickly last week, one for a different time!


I got crash when load pdf file

Describe the bug
i got crash when load 6MB file pdf.
To reproduce
Code snippet to reproduce the behavior:
    var bitmap : Bitmap? = null
    try {
        val document = PDDocument.load(file)
        val renderer = PDFRenderer(document)
        bitmap = renderer.renderImage(0,0.1f,ImageType.RGB)
    }catch (e : IOException)
    {
        return null
    }
    return bitmap

PDF example
i load this pdf file and get error
https://drive.google.com/file/d/1avgr3cy_7aoThLPOuvtyaeJvbx-1dSpY/view?usp=sharing
Expected behavior
i want get first page of file pdf as bitmap
Actual behavior
A clear and concise description of what happened instead.
Environment details:

PdfBox-Android version: [e.g. <IP_ADDRESS>]
Android API version: [e.g. API 23]

Additional context
Picture error:

Might be this bug?  https://issues.apache.org/jira/browse/PDFBOX-4890 However the bug never occured with older versions of desktop pdfbox 2.0.* with that file.


CodeLens: Async processing?

My CodeLens make a call to a REST endpoint that seems to cause blocking effects on VSC as a whole. For example, I tried to create a new file while codelens was processing and got this error:
Running 'File Create' participants...
Is there any way to have CodeLens make async calls on a separate thread, or at the least prevent them from blocking?
Relevant Code:
public provideCodeLenses(document: vscode.TextDocument, token: vscode.CancellationToken): vscode.CodeLens[] | Thenable<vscode.CodeLens[]> {
        if (vscode.workspace.getConfiguration().get('stenography.codeLensMode')) {
            ...
                return vscode.window.withProgress({
                    location: vscode.ProgressLocation.Window,
                    cancellable: false,
                    title: 'Fetching from Stenography Autopilot'
                }, async (progress) => {
                    try {
                        progress.report({ increment: 0 });
                        return fetchStenographyAutopilot(STENOGRAPHY_API_KEY!, document.getText(), language, false).then((data: any) => {
                            try {
                                 ...
                                data.code_blocks.forEach((block: any) => {
                                    var firstLine = document.lineAt(block.startPosition.row - 1);
                                    var textRange = new vscode.Range(firstLine.range.start, firstLine.range.end);
                                    let command = {
                                        title: "<stenography autopilot />",
                                        tooltip: block.stenographyResult.pm,
                                        command: "stenography.codelensAction",
                                        arguments: [block.stenographyResult.pm]
                                    };
                                    this.codeLenses.push(new vscode.CodeLens(textRange, command));
                                    this.cache.codeLensCache[filename]!.push({
                                        boundTo: block.stenographyResult.code,
                                        command: command
                                    });
                                });

                                return this.codeLenses;
                            }
                           ...
    }

(full file)

Found this answer: https://stackoverflow.com/questions/40938129/how-to-properly-implement-codelens-in-visual-studio-code
If creating the code lenses may involve intensive computation or any sort of non-deterministic behavior – such as network – then provideCodeLens should only return skeleton Code Lenses with ranges. You would then complete the CodeLens' command in resolveCodeLens, which will only be called when the CodeLens actually needs to be displayed.

closing this issue and trying this method!

Reopening because on further assessment, resolveCodeLenses seems to only work for commands. My network call supplies line numbers as well, meaning I can't set up the skeleton lenses until the call is complete

https://stackoverflow.com/questions/70058746/async-call-result-provides-ranges-and-command-for-codelens


Update to fido2 0.9.1

Updates solo-python to use 0.9.1 fido2.
Everything should work just the same except:

Can no longer use anything serial_number related, unless fido2 is manually updated.
Can no longer connect to a simulated Solo over UDP.

I created a PR to bring back UDP support: #138


Please use github tags for releases

Version tags would make it easier to download and use via sites like rawgit.com

I do have tags, except that I've forgotten to push them with git push --tags
Thanks for the reminder!


Support optional meta file that describes boilerplates

Yaml file:
.boilerplate-generator.yaml
---
- boilerplates:
      - name: README
        dest: README.md

      - name: package
        dest: package.json

Not necessary anymore


ART-9183 Add rclone() wrapper function

rclone is using a default configuration file stored at /home/jenkins/.config/rclone/rclone.conf. This file currently carries AWS secrets in clear text. This PR proposes a different approach:

store the secrets in Jenkins (already done)
turn the config file into a template, where the secrets are replaced with env vars
at runtime, render the template by filling the placeholders with real values coming from Jenkins (use envsubst for this`
call rclone with the --config option, pointing to the locally rendered file
when done, remove the rendered file (do that in a finally block to make sure this always happens)

Awesome work! Can we get a job run in action with this script, I think --dry-run should work?

Awesome work! Can we get a job run in action with this script, I think --dry-run should work?

@thegreyd yeah I've added a test Jenkinsfile (on a different branch, not to pollute this PR) that runs an rclone ls. I have moved the legacy rclone config file to a backup location, and ran https://art-jenkins.apps.prod-stable-spoke1-dc-iad2.itup.redhat.com/job/hack/job/dpaolell/job/test-rclone/10/console which succeeded.

awesome
/lgtm


Noise on generated high-resolution images

Hi, I have utilized your code to generate images successfully. But I notice that there are some noisy points on the generated images, as the following images shows. Is this phenomenon normal?

I also meet the same problem.

Checkout https://github.com/tkarras/progressive_growing_of_gans/blob/original-theano-version/h5tool.py#L508, the jpeg lib used by Pillow should be jpeg8d ( libjpeg.so.8.4.0 ) while the highest version support by ubuntu ( 18.04 LTS for me )  seems to be 8.1.2, which would cause tiny difference for jpeg decoding.
You build the libarary from source code and link it to somewhere like /usr/lib/x86_64-linux-gnu/libjpeg.so that your Pillow linked with.


Splash Screen does not resize based on content

Looks like the splash screen is currently hard coded with a height value.  Content will get cut off if it goes beyond the max height of the div

Already added, will be included in next release
https://github.com/Esri/information-lookup/commit/c349fc2c5f94f748007746d4e882e28162fff636


Website: Add Slack link to header

Public-Facing Changes
Add Slack link to website header.
Rationale: Make it easier to find.

Is there a way to make a slack link that goes to a specific channel?

You can link directly to a channel, but I'm not aware of any ability to combine that with invite links.


Highlight unusually low headways in chart

Motivation
Show headways which are 50% under the benchmark, often meaning that there's bunching
relates to #969
Changes

Testing Instructions

I'm not married to blue as the color, I just didn't want to use a color we already use on the legend

I think we should consider repurposing yellow for bunched trips. Then we could do something like this:

You thinking we shouldn't differentiate 25% late vs 50% late with different colors like we do today and instead just do red for all late trips?

Well, I think the system that we have works well, but if we're introducing a color for bunched trips, I think it should be a "warning" color like orange or yellow. My first thought was that we'd no longer be able to use it for slightly late trips, but maybe we could keep it for both?

You thinking we shouldn't differentiate 25% late vs 50% late with different colors like we do today and instead just do red for all late trips?

So basically yes, that's the proposal. But I don't feel very strongly about it.

Perhaps we can call out late trips (25%-) and bunched trips (50%-) with the same colors as 25%+ and 50%+?

yes I think that makes the most sense!

How about this @idreyn?


use new plugin to start Deploy action

I saw this github action was failed to run because of deploy job is failed, I fixed it now. Follow steps below:

get token from personal settings
repo secerts set FLOW_TOKEN key and token value

Then workflow will run success.

Thanks for the PR!
I found another solution to this problem by adding write permission to Github Actions: https://github.com/CaiJimmy/hugo-theme-stack-starter/commit/11da5cc8a961ad23e841a68f9672e2386dc22f4a so there's no need to generate personal token manually.


Demo site is down

Showing nginx splash page. Hopefully just needs a server reset!

This is also true for "browse the sandbox" (http://latest.oscarcommerce.com). Should be better to drop the navigation items on the site or to fix this (I would be happy to help).

The demo site was removed in #1911 because it was out of date. If there are still reference to the demo site then we should probably remove them (thought i removed them all)
Regarding the sandbox we will need to ask @codeinthehole

The demosite is still referenced on the homepage of http://oscarcommerce.com

@mvantellingen I'd just like to say that having a demo site is very helpful for people like me. I'm evaluating eCommerce frameworks and haven't done an eCommerce project before. Django-oscar's documentation is great but it's large and it's a lot to take in. Being able to see the system working before committing to installing it is very helpful in deciding whether it suits my requirements.

I totally agree @rogueleaderr +1

@rogueleaderr I think that the sandbox gives a much better demo experience. It is also kept up-to-date with all the changes in Oscar.
I've just created a new repository with the old demo code for history purposes (https://github.com/django-oscar/django-oscar-demo), although if people want to work on making it compatible with the latest oscar release again that would be great.


Null/Empty check with null safety

The existing approach for calling the API at https://api.climatetrace.org/v4/country/emissions?countries=ANT results in receiving an empty array. This outcome isn't presently handled in our data class and the Ktor JSON serialization workflow.
To replicate the issue, initiate a search for Netherlands Antilles, which leads to the application crashing.
https://github.com/joreilly/ClimateTraceKMP/assets/4012000/02d8194e-864c-47af-a059-21914294532e
https://github.com/joreilly/ClimateTraceKMP/assets/4012000/3b5558e3-d6ff-40f9-bd8c-18345f9c1d00
@joreilly please review

Nice, thanks!


[fix][doc] There are some typos in ManagedLedgerConfig

Fixes #17941
Motivation
I found some typos in ManagedLedgerConfig file. You can search when when keyword.
Modifications
Remove one when
Verifying this change

[ ] Make sure that the change passes the CI checks.

This change just removes when  from the comment, with no code change.
Does this pull request potentially affect one of the following parts:
If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] Anything that affects deployment

Documentation
No document need change.

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository: https://github.com/Hongten/pulsar.git

/pulsarbot rerun-failure-checks


Why must set the webdriver.gecko.driver system property?

Bug report

Node Version: 6.10.3
Protractor Version: 5.1.2
Angular Version: 4.2.6
Browser(s): Firefox 52.2.0 (64-bit), Google Chrome 59
Operating System and Version RHEL 7
Your protractor configuration file: Angular CLI 1.2.0 defaults +

    capabilities: {
        browserName: 'firefox',
        marionette: true
    },
    directConnect: false,
    localSeleniumStandaloneOpts: {
        jvmArgs: ['-Dwebdriver.gecko.driver=/home/rkrisztian/projects/testProject/node_modules/protractor/node_modules/webdriver-manager/selenium/geckodriver-v0.18.0']
    },

A relevant example test: Not needed, issue is driver-specific, and when driver is OK, tests pass.
Output from running the test:

When I specify no jvmArgs in the configuration file, I get:
[13:54:20] I/launcher - Running 1 instances of WebDriver
[13:54:20] I/local - Starting selenium standalone server...
[13:54:24] I/local - Selenium standalone server started at http://<IP_ADDRESS>:59199/wd/hub
[13:54:25] E/launcher - The path to the driver executable must be set by the webdriver.gecko.driver system property; for more information, see https://github.com/mozilla/geckodriver. The latest version can be downloaded from https://github.com/mozilla/geckodriver/releases

Otherwise everything is OK and tests are executed:
[13:55:03] I/launcher - Running 1 instances of WebDriver
[13:55:03] I/local - Starting selenium standalone server...
[13:55:05] I/local - Selenium standalone server started at http://<IP_ADDRESS>:33088/wd/hub
Jasmine started
(...)

But specifying the full path to the GeckoDriver defeats the purpose of the webdriver-manager which should just provide this setting for me, including whatever version is available. I shouldn't be setting this jvmArg property, it doesn't make any sense. As we don't do the same with Chrome, which just works.

Steps to reproduce the bug:

I'm using Angular CLI 1.2.0, and the developers there provide no support in this regard, so I came here.

Hi @rkrisztian
I don't have any experience with RHEL 7, but looking at the error that is thrown and the site that is shown in the error you should take a look at this

Selenium client bindings will pick up the geckodriver binary executable
from your system’s PATH environmental variable
unless you override it by setting the webdriver.gecko.driver
Java VM system property:

System.setProperty("webdriver.gecko.driver", "/home/user/bin");

Can you please check the provided info and let us know if that works for you?

Hi, @wswebcreation,
I hope it's clear that my real problem is that I shouldn't have to care about the webdriver.gecko.driver system property. Protractor should handle it somehow using the webdriver-manager. If I set the jvmArg myself, it will be a lot of scripting in protractor.conf.js and code duplication coming from webdriver-manager, just to fetch the right path.
Regardless, the following also works:
ln -s /home/rkrisztian/projects/testProject/node_modules/protractor/node_modules/webdriver-manager/selenium/geckodriver{-v0.18.0,}
export PATH=$PATH:/home/rkrisztian/projects/testProject/node_modules/protractor/node_modules/webdriver-manager/selenium

Then I don't need the jvmArg.

I just also came to the same conclusion that this is not good. Protractor should be able to get this done. With Chrome, we let users set chromeDriver in the configuration file and the local driver will use it...if not we check the webdriver-manager/selenium folder.
Proposed idea to fix this: https://github.com/angular/protractor/issues/4411
I think I can fix this now. I've been meaning to have a distraction from writing my book.

Oh good news. We have this in the config: firefoxPath. So I just need to use it for local. :) #suchWin

Huzzah! PR in.

Tnx @cnishina ,
Didn't saw that, sorry


strange behavior serving static files

What version of Go are you using (go version)?

$ go version
go version go1.13.5 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/tiagocardoso/.cache/go-build"
GOENV="/home/tiagocardoso/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/tiagocardoso/Code/local-environment/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/tiagocardoso/Code/local-environment/test-json/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build214163253=/tmp/go-build -gno-record-gcc-switches"

What did you do?
package main

import (
	"fmt"
	"log"
	"os"

	"github.com/gin-gonic/contrib/static"
	"github.com/gin-gonic/gin"
)

// Foo -
func Foo(c *gin.Context) {
	c.AbortWithStatus(200)
}

func main() {

	router := gin.Default()
	router.Use(static.Serve("/", static.LocalFile("/app/public", false)))

	router.GET("/", Foo)

	log.Println("App is now running")

	if err := router.Run(fmt.Sprintf(":%s", "8200")); err != nil {
		log.Fatal("Failed to run the application")
	}
}

I'm serving a version.json which is located under public folder
What did you expect to see?
The Content-Type using Docker image golang:1.13.5-alpine from version.json  is: text/plain; charset=utf-8
The Content-Type using Docker image golang:1.13.5 from version.json is: application/json
What did you see instead?
The Content-Type using Docker image golang:1.13.5-alpine from version.json  should be: application/json instead of text/plain; charset=utf-8
The Content-Type using Docker image golang:1.13.5 from version.json is: application/json which is correct
I'm I missing something?

I believe that gin-gonic's static package uses net/http's FileServer.
From the docs https://pkg.go.dev/net/http/?tab=doc#ServeContent:

If the response's Content-Type header is not set, ServeContent first tries to deduce the type from name's file extension and, if that fails, falls back to reading the first block of the content and passing it to DetectContentType. The name is otherwise unused; in particular it can be empty and is never sent in the response.

http.ServeContent uses mime to detect by extension, so let's look there:

The built-in table is small but on unix it is augmented by the local system's mime.types file(s) if available under one or more of these names:

/etc/mime.types
/etc/apache2/mime.types
/etc/apache/mime.types

On Windows, MIME types are extracted from the registry.

It looks like golang:1.13.5-alpine doesn't include /etc/mime.types, so on that distribution you'll have to manually handle your mime types for static file servers, or first install an appropriate package on alpine.
I don't think this is a bug with Go or the standard library, so I will close this issue. Let me know if I am mistaken.

Thank you, I really appreciate your explanation and that's what I was looking for.
Best regards :)


Database sync should start automatically when peers connect

I am running 2 nodes on two different machines. First node starts and adds a entry in eventlog and keeps on running. Then Second node starts and fetch all eventlog entries and prints every 3 seconds.
In this scenarios, Second node only prints empty arrays.
But If I change code of first node to add a entry every 3 seconds. Second node starts getting all entries.
So I deduced,  When a new node starts, it won't be able to get any data unless some other node pushes something to eventlog. I think, its becuase new nodes will not have any heads sync unless other nodes pushes something.
Is my understanding right? Is there any workaround for this other then periodically pushing data to eventlog?

One solution I come up with is, when a new node starts, it will push something to eventlog, so that other listening peers can connect with it, and sync but it doesn't seems to be working.

Does orbitdb have any way to periodically push heads without saving these pubs into eventlog ? If not, is it good idea to add this feature? I will create PR.

@beingmohit Thanks you for opening the issue on this! This is indeed a problem currently and what you describe is correct.
Periodically pushing updates might not be the best solution though, and we definitely don't want extra "update" entries in the log.
We previously used this https://github.com/libp2p/js-libp2p-floodsub/pull/32 to solve the problem but it looks like it won't end up in floodsub as a feature, so it has been suggested by @diasdavid that we would do that on app layer, ie. in orbit-db.
I haven't looked into what exactly needs to be done here, but from functionality perspective, we need a way to determine when "new" peers connect (in pubsub) and send them our latest local entry.
This seems like a good place to start to determine when peers connect: https://github.com/ipfs/js-ipfs/blob/master/src/core/components/pubsub.js#L75.
Perhaps we can keep track of peers in https://github.com/orbitdb/orbit-db-pubsub/blob/master/src/ipfs-pubsub.js and use callbacks back to https://github.com/orbitdb/orbit-db/blob/master/src/OrbitDB.js and then directly send a message to the peer (instead through publish() in pubsub).
Sorry if this doesn't help much or sounds vague, I haven't had time to properly think about it yet.
@beingmohit would you be interested to think this through and dig deeper as to what needs to be done here?
(I changed the topic to reflect the issue described in OP)

@haadcode Ok, I will think this through and come up with possible solutions.

@beingmohit awesome, thank you! ❤
If you need any help, best to jump on #orbitdb in IRC or post questions here. Don't hesitate to ask! 😄

@beingmohit we could probably use https://github.com/ipfs-shipyard/ipfs-pubsub-room that @pgte implemented. Wanna take a look and see if it's what's needed and how it could be integrated to https://github.com/orbitdb/orbit-db-pubsub?

@beingmohit did you have a chance to take a look at this?
I started to look into it to see if we can use pfs-pubsub-room (I believe we can) and made a quick example: https://github.com/orbitdb/orbit-db-pubsub/commit/fdf5202e26473d5920d082cddd3a71d3c951b9e8.
There's a small bug in ipfs-pubsub-room atm which I reported here and as that gets fixed, it should be all good.
In addition to the changes in orbit-db-pubsub, we need to get the callback when a new peer was connected and send them the latest heads we have. This is done in orbit-db/OrbitDB.js by adding a callback to the subscribe function in _createStore(), eg:
this._pubsub.subscribe(addr, this._onMessage.bind(this), this._onPeerConnected.bind(this))

and adding that callback function to OrbitDB class:
  _onPeerConnected (address, peer, room) {
    const store = this.stores[address]
    if (store) {
      let heads = store._oplog.heads
      if (heads.length > 0) {
        room.sendTo(peer, new Buffer(JSON.stringify(heads)))
      }
    }
  }

I think that should do it. I might be overlooking some details, but it's working on my machine.
@beingmohit would you be interested to champion this all the way to a PR across all the different repos and land it in orbit-db? You can absolutely say no, too! :) Let me know.

@haadcode I love to do this stuff. But i am unable to spare time for this. Please do you rely on me.

Got it. I'll work on this over the next few days and keep the thread updated on the progress.

This has now been fixed in v0.18.0! Thank you everyone for reporting it and helping to fix it! ❤


fix: Interrupt thread handled and interrupted not set

Direct catching action in runnable, developers are unable to check interruption occurrence when do downloadtask.execute(), add 'interrupted' flag in interruption catch block to fix it.
refer to this link

Codecov Report

Merging #310 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #310      +/-   ##
==========================================
+ Coverage   83.15%   83.16%   +<.01%
==========================================
  Files          64       64
  Lines        3836     3837       +1
  Branches      619      619
==========================================
+ Hits         3190     3191       +1
  Misses        377      377
  Partials      269      269

Impacted Files
Coverage Δ

...a/com/liulishuo/okdownload/core/NamedRunnable.java
92.3% <100%> (+0.64%)
:arrow_up:

Continue to review full report at Codecov.

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


neat 2.0?

bourbon: 5.0beta-6
neat: 2.0beta-1
bitters: 1.4
I'm using node-sass. I just updated to bourbon 5.0beta and neat 5.0beta and some components stopped working with following:
Error: no mixin named media
Seems like there's no mixin called media in neat 2.0
Any migration guide to move current components to neat 2.0 will be very helpful. Also, I saw that refills have been updated to support bourbon 5.0, is there any immediate plan to port the components to neat 2.0?

Hi @afm-sayem
Since most of the components would need to be rewritten, Refills does not currently support Neat 2.0. It would be best to stick to 1.8.
This will likely change once neat 2.0 is a bit closer to coming out of beta. If we were to do a wholesale update, we would need a way of tying together the "use X version of neat with X version of refils, etc, etc…". cc: @brendastorer

Any update on getting refills up to snuff with Neat 2.0? Suspenders now uses both refills and neat 2.0 (beta) and things work when bootstrapping a new project because it only uses the flashes refill, but if you try to pull in the navigation refill it blows up with the error @afm-sayem mentioned. I downgraded my fork of suspenders (with customizations) to use neat 1.8 for now as suggested by @whmii, but having an updated refills for neat 2.0 would be mo bedda! Happy to help, if feasible. LMK. Thanks!

@jondkinney This is more be more of a refills issue, would you mind crossposting this to https://github.com/thoughtbot/refills/issues

deleted My comment. thought I was in another project.

Any word on when Refills is going to support Neat 2.0?


JSON Pointers single prefix limitation

Would be very helpful if this limitation could be lifted:

Important: You can only use a pointer prefix once in a class. For example, you can't use /user and /user/name in the same class.

@simc Can you explain why that is?
I never used json pointers before, but using multiple pointers sounds like a valid use case for me 🤔


Can not import css file not exported from package.json

I am working on https://github.com/CesiumGS/cesium-webpack-example.
This is very simple web pack configured web app.
It works well with webpack 4(original version).
But after I update web pack version, it shows following error.
Module not found: Error: Package path ./Build/Cesium/Widgets/widgets.css is not exported from package E:\MyResearch\CesiumJsGIS\node_modules\cesium (see exports fiel
d in E:\MyResearch\CesiumJsGIS\node_modules\cesium\package.json)
In a short I could not import css file from node_module.
This is original webpack version.

This is the updated part of the config file.

Thank you for creating this issue. However, issues need to follow one of our templates so that we can clearly understand your particular circumstances.
Please help us help you by recreating the issue using one of our templates.

Expected, because https://github.com/CesiumGS/cesium/blob/master/package.json#L35, css is not exported for other packages

https://github.com/webpack/webpack/issues/11467#issuecomment-708871353, but I strongly don't recommend to do this

so what is the solution?

Solutions:

open an issue in repo and ask to export CSS files
avoid using not exported CSS files and use copy-webpack-plugin
Use workaround above, right now and search alternatives

I see. Thanks.

I have this same problem with cesium. but the fullySpecified trick doesn't work:
			{
				test: /\.css$/i,
				use: ['style-loader', 'css-loader'],
				exclude: /node_modules\/(?!cesium)/,
				resolve: {fullySpecified: false}, // https://github.com/webpack/webpack/issues/11787
			},

I still get
Module not found: Error: Package path ./Source/Widgets/widgets.css is not exported from package /home/trusktr/app/node_modules/cesium (see exports field in /home/trusktr/app/node_modules/cesium/package.json)


sort custom queries higher in main query selection page

fix for issue #26

Works for me, thanks!


Fix Minor UI Issues

Fixes the alignment of the placeholder box ("No Iterations Found") when viewed on wider screens.

before
after

Codecov Report

Merging #93 (bfa2a00) into master (44e1a26) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #93   +/-   ##
=========================================
  Coverage     48.82%   48.82%
  Complexity      453      453
=========================================
  Files           104      104
  Lines          2132     2132
  Branches        228      228
=========================================
  Hits           1041     1041
  Misses         1044     1044
  Partials         47       47

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

Great eye for detail @seelengxd, really appreciate your help!


Implement FromRawFd, AsRawFd, and from_std for TcpListener.

This enables socket configuration for the listener.

@Icelk You can use cargo test and cargo doc --no-deps to get most tests run locally. Sometimes the failure in CI will be because the CI kernel is 5.15 and not 6.0 or 6.1 but maybe that's not the current case.

Fixed the test now. Sorry for the CI failure.

Thanks!

Thank you! You've made it very easy to contribute.


feat(access_token): scheduler workflow implementation for access token

Type of Change

[x] New feature

Description

This PR adds support for generating the access token by the scheduler. This will offload the task of generating the access token by a new payment and save us some time for a new payment.
Motivation and Context

Reduce access token creation time during payments.
How did you test it?

For testing purposes, the next schedule time is set to 60 seconds.

Create a payment using a connector which requires access_token for payment.

The process tracker entry is created.

After one minute, new access token is created and stored in redis. The task is requeued and new schedule time is created.

Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed submitted code

Closing this PR since changes will be taken up in a separate PR. This has a lot of conflicts and better to copy over changes to a separate PR because a lot has changed since this change was made.


Incorrect handling of custom images

Information

Onefuzz version: 3.2.0
OS: Azure Function App

Provide detailed reproduction steps (if any)

The documentation for using custom OS images within OneFuzz scale sets (https://github.com/microsoft/onefuzz/blob/main/docs/custom-images.md) says that ti accepts Azure Compute Gallery resource IDs, such as: /subscriptions/MYSUBSCRIPTION/resourceGroups/MYGROUP/providers/Microsoft.Compute/galleries/MYGALLERY/images/MYDEFINITION/versions/MYVERSION
When creating a VM scale set, the get_os function gets called to identify the operating system type of the image within create_vmss  (onefuzzlib/azure/vmss.py - line 317). The get_os function of image.py in the onefuzzlib library (https://github.com/microsoft/onefuzz/blob/main/src/api-service/app/onefuzzlib/azure/image.py) attempts to fetch the image information using "client.images.get" (line 25). Unfortunately, that Azure SDK method fetches definitions from Azure Images and not Azure Compute Galleries.
The correct code for supporting Azure Compute Galleries would be:

name = client.gallery_images.get(parsed["resource_group"], parsed["name"], parsed["child_name_1"]).os_type.lower()

There is also a second issue in the same section of code. The existing code for retrieving the image from Azure Images tries to access the 'name' property of the 'os_type' which does not exist. This should instead be a call to '.lower()'. Both issues are described in further detail in the Actual Result section below.

Expected result
It does not appear to be possible to create a scale set from an Azure Image. Therefore, the code needs to be updated to correctly handle Compute Galleries. Assuming that the Azure Image approach within get_os is necessary for other workflows within OneFuzz,  the os_type reference to the  'name' property should be replaced with a call to '.lower()'.
Actual result
The code throws a ResourceNotFound error because it is given an Azure Compute Gallery resource ID and it is expecting an Azure Images resource ID. The code needs to be updated to leverage client.gallery_images.get() instead in order to support Azure Compute Galleries (https://docs.microsoft.com/en-us/python/api/azure-mgmt-compute/azure.mgmt.compute.v2021_07_01.operations.galleryimagesoperations?view=azure-python#get-resource-group-name--gallery-name--gallery-image-name----kwargs-).
In addition, existing references to Azure Images fail due to trying to access a nonexistent property of the os_type.  It appears that the existing code is expecting a resource ID for Azure Images, such as:
/subscriptions/MYSUBSCRIPTION/resourceGroups/MYGROUP/providers/Microsoft.Compute/images/MYIMAGE
However, if the above image resource ID from Azure Images is provided, then the code will still result in an error. In this case, the get_os code is able to find the Azure Image resource. Unfortunately, the code then tries to access a nonexistent property of that image when it executes line 27:
.storage_profile.os_disk.os_type.name
For Azure Images, the 'os_type' is a string / OperatingSystemsType Enum and it does not have a 'name' property (https://docs.microsoft.com/en-us/python/api/azure-mgmt-compute/azure.mgmt.compute.v2021_07_01.models.imageosdisk?view=azure-python).  In this case, the code should be: .os_type.lower() similar to line 39.
Proposed solution
I do not know the code well enough to know if the existing get_os parsing behavior is necessary for the other use cases within the overall application. If it is necessary, then an if clause could be added to preserve backwards compatibility. The following code change for /onefuzzlib/azure/image.py (lines 23-30) includes the 'os_type' fix for Azure Images to address the nonexistent 'name' property issue, and it allows support for both Compute Galleries and Images reference IDs:
    if "resource_group" in parsed:
        if parsed["type"] == "galleries":
            try:
                name = client.gallery_images.get(
                    parsed["resource_group"], parsed["name"], parsed["child_name_1"]
                ).os_type.lower()
            except (ResourceNotFoundError, CloudError) as err:
                return Error(code=ErrorCode.INVALID_IMAGE, errors=[str(err)])
        else:
            try:
                name = client.images.get(
                    parsed["resource_group"], parsed["name"]
                ).storage_profile.os_disk.os_type.lower()
            except (ResourceNotFoundError, CloudError) as err:
                return Error(code=ErrorCode.INVALID_IMAGE, errors=[str(err)])
    else:
           ...

Per the contributing guidelines, I am holding off on submitting a pull request until the issue gets reviewed.

Thanks for the detailed bug report, @puhley (and for reading the contribution guidelines!). We would be happy to review a PR addressing this.

Closing. PR #1450 addressed this issue.


Refactor build tests

Refactor the build tests suite in order to reduce testing logic in test.dart and allow for later implementing package:test onto the existing build tests
Part of https://github.com/flutter/flutter/issues/145482
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] I followed the breaking change policy and added Data Driven Fixes where supported.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Keeping as a draft since this relies on the refactoring done in https://github.com/flutter/flutter/pull/146592


Finalizer Removal Bug Fix & Logging clean up

lgtm
There's some overlap with #122 where UpdateStatus is now called and with some err msg refactoring.

lgtm


Unhandled Runtime Error

Bug Description
spinning up a new test_env results in a fatal error right away int he ui
Steps to Reproduce

Bring up the test_env
Open the Fides UI

Expected behavior
Screenshots

Environment

Version:
OS:
Python Version:
Docker Version:

Additional context
Add any other context about the problem here.

Here is the PR

@Roger-Ethyca PR has been merged into main branch.


Cpu usage

Hey Mvis,
Do you see room to improve CPU usage?
on multi gpu systems the miner tends to crash because theres not enough cpu power on a tiny celeron cpu

What OS?
AMD or Nvidia?

Windows, nvidia.
Its over using the cpu so its unable to start some times.
I know for speeds its better to use another miner, but yours is the only one with multi-gpu support in 1 instance

I've had a few reports of Nvidia users experiencing 100% CPU useage.  I think there might be some bugs in Nvidia's implementation of OpenCL.  Unfortunately I don't have any Nvidia GPU's so I can't test much.

I understand. It only does it this in the initialization phase.
Once its running cpu usage is a lot lower, happens on Intel Celeron G1840 @ 2.80GHz.
This does not happen on Linux. Works marvelous.


Group netdev is missing when using Avahi

Here is a snippet from /nix/store/…-system-path/etc/dbus-1/system.d/avahi-dbus.conf:
  <!-- Allow everything, including access to SetHostName to users of the group "netdev" -->
  <policy group="netdev">
    <allow send_destination="org.freedesktop.Avahi"/>
    <allow receive_sender="org.freedesktop.Avahi"/>
  </policy>

netdev is one of those groups used by all the distros, just like video and plugdev (the latter one, actually, also doesn’t get created by NixOS and I’m not sure what implications this has).
I think this group should be created in config/users-groups.nix. Your thoughts?

Relevant issue from Arch (about "plugdev" group): https://bugs.archlinux.org/task/35602

Right, it seems that plugdev is really evil and it is not needed, since NixOS uses systemd. But unfortunatelly there are still packages that ship udev rules with references to plugdev.
On the other hand, netdev group seems to be completely harmless. I don’t what it is used for nowadays, I think NetworkManager used to decide whether user was allowed to create wifi connections based on membership in this group, but I’m pretty sure that right now I can do whaterver I want with networking with an empty netdev group.
Based on this I assume that the only real use for netdev right now is this avahi dbus rule. Avahi package creates this group in distros I checked (Gentoo, Fedora), so we should do this too.

@bjornfor BTW apparently Fedora fixed your issue by replacing all the plugdev with users in the rules they ship.

(triage) Do we really need another group? Has there been another issue about this? Maybe it’s getting replaced by systemd anyway.

It hasn't bothered me enough to do anything about it. My user is (overly) privileged, so I didn't have a use for the "netdev" group. But I can imagine there are use cases where it's useful. (Less privileged users that are allowed to do certain things with networking / avahi.
Also, I'm worried about exhausting the user/group namespace in NixOS :-)

Also, I'm worried about exhausting the user/group namespace in NixOS :-)

Yes, that could very well become a problem in the mid future.

For me, closing is fine. If this becomes an issue for me later I'll probably open a PR that adds the group.
CC @kirelagin.

@Profpatsch What do you mean being replaced by systemd? There's still lots of modules and hardware devices that still advise udev rules that use the plugdev group. We should either document that users should probably have the plugdev group by default, or standardise the handling of USB device modules and the groups/authentication system they use.

Are you talking about this kind of stuff: TAG+="uaccess", TAG+="udev-acl”?


Cannot access assets under the assets folder

Please provide the environment you discovered this bug in.
Stackblitz
github
live
Which area/package is the issue in?
Don't know / other
Description
For some reason i cannot load any ressources provided under the assets folder.

The request finishes with 200 but has no content

if directly requested i get a my default page if something is not found

Please provide the exception or error you saw
No response
Other information
No response
I would be willing to submit a PR to fix this issue

[ ] Yes
[X] No

The problem, as it is so often, was the human infront of the screen. I have not set the proper publicdir:
after changing it, i got my images 🙂


For new extensions:

[x] My extension description/summary conforms to the Extension Summary Guidelines.

Thank you for your contribution! We will review the pull request and get back to you soon.

@kairu-ms, could you please merge it unless you have any concerns/feedbacks for me to address


Doxygen deprecated PERL_PATH and MSCGEN_PATH

Was compiling a Dome workspace on Focal with Doxygen version 1.8.17 and almost all packages generated a warning similar to this:
warning: Tag 'PERL_PATH' at line 2125 of file '/home/osrf/Workspaces/ignDome_ws/build/ignition-launch3/api_tagfile.dox' has become obsolete.
         To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u"
warning: Tag 'MSCGEN_PATH' at line 2147 of file '/home/osrf/Workspaces/ignDome_ws/build/ignition-launch3/api_tagfile.dox' has become obsolete.
         To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u"

the packages that this happens for are:
12 packages had stderr output: ignition-common3 ignition-fuel_tools5 ignition-gazebo4 ignition-gui4 ignition-launch3 ignition-math6 ignition-msgs6 ignition-physics3 ignition-plugin1 ignition-rendering4 ignition-sensors4 ignition-transport9

Based on Doxygen's changelog, PERL_PATH and MSCGEN_PATH have been removed in 1.8.16

It should probably be safe to remove them, I don't think we're using Perl, and mcsgen isn't even set:
https://github.com/ignitionrobotics/ign-cmake/blob/a4c8568a4ef91b0abc6c64a50185721f2fd1a33d/doc/doxygen/api.in#L2112-L2116
https://github.com/ignitionrobotics/ign-cmake/blob/a4c8568a4ef91b0abc6c64a50185721f2fd1a33d/doc/doxygen/api.in#L2131-L2138

This would have to be removed for all 12 packages as well (e.g., ign-common, ign-gazebo, etc)

Luckily most packages are just using the doxygen config from ign-cmake, so I think that removing those here would remove most of the warnings.
I only see those variables in a few other packages:
https://github.com/search?q=org%3Aignitionrobotics+PERL_PATH&type=code

ign-rndf isn't actively maintained, so we can ignore it
ign-tools doesn't use ign-cmake, so we need to update it
ign-fuel-tools uses ign-cmake, so I think it shouldn't have that file, we should look into removing that

I tested removing PERL_PATH and MSCGEN_PATH from ign-cmake/doc/doxygen/api.in on a clean build and do not receive any errors from ign-tools, ign-fuel-tools, or any other package except for ign-gui:
--- stderr: ignition-gui4
error: Illegal format for option TAGFILES, no name specified for item '='
error: Illegal format for option TAGFILES, no name specified for item '='
error: Illegal format for option TAGFILES, no name specified for item '='
error: Illegal format for option TAGFILES, no name specified for item '='
error: Illegal format for option TAGFILES, no name specified for item '='
error: Illegal format for option TAGFILES, no name specified for item '='
error: Illegal format for option TAGFILES, no name specified for item '='
error: Illegal format for option TAGFILES, no name specified for item '='
---

Interesting, here's where TAGFILES is defined for ign-gui:
https://github.com/ignitionrobotics/ign-gui/blob/12198ffae7fffd96d155f71c8f86fb96063bf0ab/CMakeLists.txt#L114-L120

Fixed in #136.
I'm closing this, but feel free to open a new one for the TAGFILES, @jennuine .


Will this project replaced by Azure AD Workload Identity ?

I see a new project: https://azure.github.io/azure-workload-identity/docs/introduction.html
It enables to connect to Azure Key Vault using AAD on any Kubernetes cluster.
Will it replace this project ?

Hello @HoussemDellai, Thanks for opening the issue.
Azure Workload Identity will serve as yet another identity access method for secrets store CSI AKV provider.
We are working on adding support for same in this project. This will be our recommended method to connect with AKV when using this project and it will not replace CSI AKV provider.

Thanks very much @nilekhc 💯

Closing this. Please open new one if you face any problems.


add e2e testcases for ci

These test cases are developed with bats test framework, which covers compile related components, run container with rafs image and zran image.
Signed-off-by: Yiqun Leng<EMAIL_ADDRESS>

@yqleng1987 please sign-off your commit.


Derive additional implementations for MaybeUndefined

It would be very helpful if MaybeUndefined<T> implemented:

Debug
Clone
Serialize
Deserialize
Possibly other "basic" ones?

Iff T implements those, so we don't require T to implement them.
Is everyone ok with that?

This compiles:
#[derive(Clone)]
pub enum MaybeUndefined<T> {
    Undefined,
    Null,
    Value(T),
}

but I have never thought about it in detail. Does this mean "implement Clone for all T that implements Clone, otherwise: do not implement Clone"? I would assume so, because it compiles and I didn't need to add constraints on T. This SO post seems to indicate that I only need to add that attribute.
Or do I need to do something like:
impl<T> Clone for MaybeUndefined<T>
where
    T: Clone,
{
    fn clone(&self) -> Self {
        match &self {
            MaybeUndefined::Undefined => MaybeUndefined::Undefined,
            MaybeUndefined::Null => MaybeUndefined::Null,
            MaybeUndefined::Value(val) => MaybeUndefined::Value(val.clone()),
        }
    }
}

I don't know how I have never come across this in my experience with Rust 🤔

FYI: You only need to add the attributes and Rust automatically takes care of adding the appropriate constraints 😄
e.g. #[derive(Deserialize)] expands to:
impl<'de, T> _serde::Deserialize<'de> for MaybeUndefined<T>
where
    T: _serde::Deserialize<'de>,
{
    fn deserialize<__D>(__deserializer: __D) { ... }
}


CuppaAlert / Restore window scroll position

Hi!
Thank you for your great library!
I have a little problem with CuppaAlert. At the bottom of a long page I have a button which triggers the alert. The alert is shown (and the the website in the background is scrolled up to the top). When I close the alert, the website is still scrolled up. Is there any way to preserve/restore the scroll position?
Thank you!

Hi @schube, I was trying to reproduce the issue but it was not possible, are you sure that the problem is the component?
If you check this doc , you will see that alert is not modifying the page scroll position.
Is it possible for you to replicate the issue in CodePen or any similar online tool?, so I will be able to check the issue and fix the bug if necessary.
Also, a quick solution for you will be to capture the scroll position with JS before add the alert and restore the scroll to that position after close the alert, you can use the callback event to know when alert is closed

Hi @tufik2, thank you for your fast reply. I tried it with Safari and Chrome v106 and with the debugger on, the scroll (or better "jump") to the page start happens when this line is executed: document.body.append(alert);. Alert beeing
let alert = new CuppaAlert({`
        	title: _this.data('message-title'),
        	message: _this.data('message-confirm'),
        	backdropEnabled: true,
        	acceptText: 'Ja',
        	cancelText: 'Nein',
        	callback:(res)=>{
				console.log(res);
				if(res.value==true) {
					onConfirm();
				}

        	}
    	});

I will try to create a CodePen to reproduce this soon.
Thank you!

I think I found the problem, but I am not 100% sure yet where to look for the solution:
The website has this CSS style definition like that:
html, body {
	height: 100%;
}

And this results in the behavior described. You can test it here: https://kunden.schubec.com/cuppa/
So this is more a CSS problem I guess and not really related to cuppa. I guess, cuppa also cannot do much there.
I don't know why the style is defined like that. I guess that is a left over from my predecessor.
So sorry for bothering you and thanks for your cool component(s)!
Best,
Bernhard


feat: add back file upload

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

GitHub release
v1.15.0

Your semantic-release bot :package::rocket:


External methods with Span overload need the correct buffer size passed

In Use:

.NET 5.0 Console-Application
Microsoft.Windows.CsWin32 0.1.319-beta

When adding VirtualQueryEx to NativeMethods.txt the following is produced:
        [DllImport("Kernel32", ExactSpelling = true, SetLastError = true)]
        internal static extern unsafe BOOL ReadProcessMemory(CloseHandleSafeHandle hProcess, [In] void *lpBaseAddress, [Out] void *lpBuffer, nuint nSize, [Out, Optional] nuint*lpNumberOfBytesRead);
        /// <inheritdoc cref = "VirtualQueryEx(CloseHandleSafeHandle, void *, MEMORY_BASIC_INFORMATION*, nuint)"/>
        internal static unsafe nuint VirtualQueryEx(CloseHandleSafeHandle hProcess, void *lpAddress, Span<MEMORY_BASIC_INFORMATION> lpBuffer)
        {
            fixed (MEMORY_BASIC_INFORMATION*lpBufferLocal = lpBuffer)
            {
                return PInvoke.VirtualQueryEx(hProcess, lpAddress, lpBufferLocal, (nuint)lpBuffer.Length);
            }
        }

The overload with Span<MEMORY_BASIC_INFORMATION> is not working as expected.
After executing, the returned int is 0 and the buffer contains only default values.
I am totaly new to P/Invoke, Span and so on, so i had to lookup some stuff and experiment.
I hope my understanding is somewhat correct.
I have manually created an external method and used the types from Microsoft.Windows.Sdk.PInvoke to build this working example:
        //[DllImport("kernel32.dll", SetLastError = true)]
        //internal static extern int VirtualQueryEx(IntPtr hProcess, IntPtr lpAddress, out MEMORY_BASIC_INFORMATION lpBuffer, uint dwLength);

        [DllImport("kernel32.dll", SetLastError = true)]
        internal unsafe static extern int VirtualQueryEx(CloseHandleSafeHandle hProcess, IntPtr lpAddress, MEMORY_BASIC_INFORMATION* lpBuffer, uint dwLength);

        internal unsafe static int VirtualQueryEx(CloseHandleSafeHandle hProcess, IntPtr lpAddress, Span<MEMORY_BASIC_INFORMATION> lpBuffer)
        {
            fixed (MEMORY_BASIC_INFORMATION* lpBufferPointer = lpBuffer)
            {
                return VirtualQueryEx(hProcess, lpAddress, lpBufferPointer, (uint)(Marshal.SizeOf<MEMORY_BASIC_INFORMATION>() * lpBuffer.Length));
            }
        }

The parameter dwLength needs the size of the buffer.
Span.Length returns the number of elements of type T.
So the length will be 1 for Span<MEMORY_BASIC_INFORMATION> span = new MEMORY_BASIC_INFORMATION[1];.
But a single element of type MEMORY_BASIC_INFORMATION does not have the size of 1 byte.
So the actual size of the buffer-size has to be queried Marshal.SizeOf<MEMORY_BASIC_INFORMATION>().
Passing the size of the element type should be sufficient in this case, because VirtualQueryEx will only provide a single element anyway.
Not sure if it is a good pattern in this case, but i have also multiplied the size of the element type with the buffer length.
I am also not sure of other cases, but if there are any cases that handle multiple elements, it might be a good practice to multiply the element size with the buffer length.

I think some APIs need the byte length and others need the element count, and bad information was gathered about which way VirtualQueryEx is (and maybe other APIs).

Great report. I have filed a new bug against the metadata that must first be fixed, then we can update CsWin32 to adjust code gen based on their update.

Ironically, it never came up till now that the 3rd parameter isn't even supposed to be an array. Go figure.
https://github.com/microsoft/win32metadata/issues/284
But you still caught a bug in our handling of length by count vs length in bytes, so I'm finalizing a fix for that.

But our own bug is implicitly fixed by the metadata change, so I'll close this with no further changes.


"Bass Enhancing + Perfect EQ.json" needs adapting after installation to new /home/{user} folder for .irs settings

FYI: By default the path is set to
"kernel-path": "\/home\/matteo\/.config\/PulseEffects\/irs\/Dolby ATMOS ((128K MP3)) 1.Default.irs",
so the Convolver part will not work - also I had to select one of the irs profiles in the Convolver part of the app to make it work.
In a nutshell:
Just select the irs profiles in the Convolver part of the Application via the "impulse response file" setting (the wave form button) the first time you launch it - and it should be fine,
Great settings ! - loving the irs files - never had this great sound output on Linux so far <3
Thanks

Wops, I forgot about that xD
Maybe I could use sed in the installation script for automatically adjust the path :)


EKS kubelet metrics

What happened?
Description
In EKS, kubelet is managed by AWS and so the (as far as I can see) the ServiceMonitor for KubeLet needs to be disabled. The metrics for volume are still available, for example, the following works:
kubectl get --raw /api/v1/nodes/ip-10-0-1-199.eu-west-2.compute.internal/proxy/metrics | grep kubelet_volume_stats_used_bytes
What is the recommended method for getting these metrics from EKS?
Steps to Reproduce
Expected Result
The Metrics available
Actual Result
Prometheus Operator Version
quay.io/prometheus-operator/prometheus-operator:v0.77.1

Kubernetes Version
clientVersion:
  buildDate: "2020-06-22T12:00:00Z"
  compiler: gc
  gitCommit: c96aede7b5205121079932896c4ad89bb93260af
  gitTreeState: clean
  gitVersion: v1.18.4
  goVersion: go1.19.9
  major: "1"
  minor: "18"
  platform: linux/amd64
serverVersion:
  buildDate: "2024-09-21T09:31:42Z"
  compiler: gc
  gitCommit: 194b08f0b9db51e750f3a3dcc2ffe5dda0103c0d
  gitTreeState: clean
  gitVersion: v1.30.5-eks-ce1d5eb
  goVersion: go1.22.6
  major: "1"
  minor: 30+
  platform: linux/amd64

Kubernetes Cluster Type
EKS
How did you deploy Prometheus-Operator?
helm chart:prometheus-community/kube-prometheus-stack
Manifests
No response
prometheus-operator log output
NA

Anything else?
No response

@nicolastakashi  Thankyou for the reply.
When I enable kubelet.enable=true and kubeletService.enable=true, I get the following errors:
I also see the Service being created, but I cannot port-forward onto it because I get the error:
error: cannot attach to *v1.Service: invalid service 'monitoringlayer-prome-kubelet': Service is defined without a selector
Update: I think I have "fixed" it, it was me not understanding what was going on :(
Thanks


Update to master

We can update the master changes into this so we can re-request for review once again :)

@ktsivkov Take a look ^

@SoulPancake merged


Cannot update a model with composite keys through a referenced model

Bug description
Prisma is unable to update a model which references another model that has composite keys.

How to reproduce
I've provided a repo https://github.com/iRoachie/bug-free-pancake
Expected behavior

A new row in ActiveProvider table should be added to reflect the update.
createSite-raw.ts does it in plain SQL as an example of what should happen.
Prisma information

Provided in the repo
Environment & setup

OS: MacOs
Database: MySQL
Node.js version: v14.9.0
Prisma version:

@prisma/cli          : 2.10.0
@prisma/client       : 2.10.0
Current platform     : darwin
Query Engine         : query-engine af1ae11a423edfb5d24092a85be11fa77c5e499c (at node_modules/@prisma/cli/query-engine-darwin)
Migration Engine     : migration-engine-cli af1ae11a423edfb5d24092a85be11fa77c5e499c (at node_modules/@prisma/cli/migration-engine-darwin)
Introspection Engine : introspection-core af1ae11a423edfb5d24092a85be11fa77c5e499c (at node_modules/@prisma/cli/introspection-engine-darwin)
Format Binary        : prisma-fmt af1ae11a423edfb5d24092a85be11fa77c5e499c (at node_modules/@prisma/cli/prisma-fmt-darwin)
Studio               : 0.304.0

I can confirm this. Thanks for reporting!

Glancing over the code makes me think this is either the same or a closely related issue to https://github.com/prisma/prisma/issues/3081, will say more when I looked into it.

A fix will be available in version 2.11.


Specify the location of the .caddy directory?

Sorry if I missed this, but is there a way to specify .caddy's location?
I'm running Caddy inside of Docker so it would be a lot easier if that directory could be mounted from the host system.

Yes, it goes into the $HOME folder. https://caddyserver.com/docs/automatic-https
Make sure the folder is persisted even if the container disappears or you'll run into LE rate limits pretty quick.

When I try to mount /somedir/.caddy:/root/.caddy and try to start the Caddy container I get:
Activating privacy features... done.
2016/02/03 03:31:28 open : no such file or directory

Not sure if open : no such file or directory is from Caddy or not but the .caddy directory does get mounted to the container. If anyone has any ideas, I'd appreciate it. Thanks!

Does /somedir/.caddy exist on the host?
Can you please provide more info on how you run your docker container?

@hubertbanas Yup, the directory exists on the host. I'm using this image: https://github.com/ianwalter/docker-caddy and I'm running it like so: docker run --name caddy -p 80:80 -p 443:443 -v /var/www:/var/www -v /var/data/.caddy:/root/.caddy --link influxdb quay.io/ianwalter/caddy

Try a directory within the home directory on the host. I've had that issue before.
To clear your doubt that it is not caddy related, remove the .caddy mount and leave only /var/www and see if it works.

@abiosoft I just tried that and got the same error. I had Caddy working before I added the mount for .caddy. Also, when I tried to mount the .caddy directory I just created on the host's home directory, it did get populated with the letsencrypt data so it seems like the mount is working properly and it's Caddy thats having a problem reading it.


Nexys Video fails timing

I have two Nexys Video boards and they seem to be on the slower end of the speed grade, resulting in the fact that they cannot run an OpenTitan system, neither the last from CI nor self built. There are over a hundred failing endpoints on the timing report, which makes that no real surprise.
So, we need to lower the clock(s) and I am wondering if there is some guidance on how to do this in the hjson. Does anyone remember a commit that changed the clock to fix timing before?

https://github.com/lowRISC/opentitan/pull/3647 was the last PR where we did decrease the frequency.

Timing was not the issue, its borderline but okay


Import css to remove white space on bottom of page 🥲

UX crash
Note; this only requires a pull from Emily's prototype. It is already fixed there.
Weird empty bar on the bottom of our pages appeared after removing the top warning bar

Solution
Get new css from Emily prototype https://github.com/ugent-library/biblio-ugent-prototype

@mietcls the white space bar is actually always there, as stated in the css for element main:

main {
    background-color: #fafafa;
    height: calc(100% - 4.8rem);
    overflow: hidden;
    width: 100%;
}

When you resize the height (e.g. by opening the javascript console),
the space used for the side bar also becomes smaller.
When I remove that line with height, the full height is always used for the side bar,
even when I open the javascript console.
As the html body uses display flex, it should not be problematic to remove
the height property?

@nicolasfranck It is fixed with the pull of Emily her prototype – we just need to update the css on this repo. We just did not notice it on the test environment because of the topbar. No need to fix it anymore!

@nicolasfranck is this something you can do, just updating the css (reeling it in from Emily's prototype)? Or does this need to be passed on to someone else?

@mietcls i'll import it
@nicolasfranck i'll show you how next time we're in the bt


Use base permission

Include base permission in CRUD operations. Except of the root account.

Covered by: https://github.com/bytelab-studio/syntra.plugin/issues/13


Paste not working in "search and replace" toolbar

VSCode Version: 1.9.1 (1.9.1)
OS Version: macOS Sierra 10.12 Beta

Steps to Reproduce:

Copy anything from anywhere.
Try to paste in either of the Search or Replace

P.S.: Context Menu -> Paste works fine, but cmd+v doesn't.

This works for me. This is the find widget (cmd+f) right?

No, this happens in the "search and replace" (cmd+shift+f). Find (cmd+f) works fine.

Ok, so nothing happens when you press cmd+v? @sandy081 Any idea what could be the problem?

@roblourens Sorry, I just checked, cmd+v isn't working in find, search and replace, extensions search, cmd+p or cmd+shift+p. But it's working in the editor.

And I tried the --verbose mode too, but nothing came up in the console on cmd+v.

Are there any errors in chrome devtools? (Help > Toggle Developer Tools)
And could you try downloading the Insiders build to see if it works there?

Sorry again, it was due to an emacs binding extension I had installed, which overrode the cmd+v binding. I'll open an issue there. Thanks.


Remove diagnostic setting retention policy

When creating a azurerm_monitor_diagnostic_setting resource, the following warning is shown:
╷
│ Warning: Argument is deprecated
│
│ `retention_policy` has been deprecated in favor of `azurerm_storage_management_policy` resource - to learn more https://aka.ms/diagnostic_settings_log_retention
╵

Migrate all modules using an azurerm_monitor_diagnostic_setting by removing any retention_policy blocks.
Could try running this script to create PRs for all modules with diagnostic settings:
#! /bin/bash

set -eu

modules=(
  "acr"
  "app-config"
  # "app-insights"
  "automation"
  # "databricks"
  "event-grid"
  "function-app"
  "grafana"
  # "identity"
  "key-vault"
  "log-analytics"
  # "nat"
  # "network"
  "postgres"
  "public-ip"
  "service-bus"
  "sql"
  "storage"
  # "synapse"
  "web-app"
)

for module in "${modules[@]}"; do
  # Clone repo
  repo="terraform-azurerm-$module"
  git clone "https://github.com/equinor/$repo.git"
  cd "$repo"

  # Create new branch
  branch="fix-remove-diagnostic-setting-retention-policies"
  git switch -c "$branch"

  # Make changes
  file="main.tf"
  lines=$(cat "$file" | grep --line-number "retention_policy {" | cut -d : -f 1)

  num_of_lines_to_remove_before=1
  num_of_lines_to_remove_after=3
  num_of_lines_to_remove=$((1 + num_of_lines_to_remove_before + num_of_lines_to_remove_after))

  num_of_removed_blocks=0

  while read -r line; do
    initial_line=$((line - num_of_removed_blocks * num_of_lines_to_remove))

    start_line=$((initial_line - num_of_lines_to_remove_before))
    end_line=$((initial_line + num_of_lines_to_remove_after))

    sed -i "${start_line},${end_line}d" "$file"

    num_of_removed_blocks=$((num_of_removed_blocks + 1))
  done <<< "$lines"

  # Commit changes
  commit_message="fix: remove diagnostic setting retention policies"
  git add "$file"
  git commit -m "$commit_message"
  git push

  # Create PR
  gh pr create --title "$commit_message" --body ""

  # Delete local repo
  cd ..
  rm -rf "$repo"
done

Script has been run, and PRs created successfully.


Day255

Resolves #525.

Pull Request Test Coverage Report for Build 991

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 980:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls

Pull Request Test Coverage Report for Build 982

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 980:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls


Implement initial DSSE verification

This adds dsse envelop processing and tests. This also adds an
inmemory keystore that can be used for now until we figure out
what we are using long term for fetching and storing public keys
for verification. This also creates a verifier interface along
with a Sigstore verifier for the purposes of verifying DSSE
envelopes through Sigstore

Is DCO working right?

oh looks like commits were rewritten so I just cherry-picked. Closing this one.


fix: Toggle rotate look down-side when opened

Description of Changes

Toggle rotate look down-side when opened
The shape of the toggle triangle was slightly modified.
Add pointer cursor

Video
https://github.com/user-attachments/assets/d79b418a-ee56-47f6-b0d0-bee319873e64

This is my first time using Storybook, so I found it difficult. How do I test the components in dark mode? A problem is expected as the toggle will not be visible properly when the background is in dark mode.

한글로 올려도 되는거죠 .. ? 영문으로만 가능한가요 ?

it's global library~ english only on pr

umm could you upload original(?) bug too?
you uploaded fixed version right?

This is my first time using Storybook, so I found it difficult. How do I test the components in dark mode? A problem is expected as the toggle will not be visible properly when the background is in dark mode.

@JoSuwon https://discord.gg/yAjKwDb7xR
join discord!

https://github.com/user-attachments/assets/fc7d2d97-ab53-47ab-b4ec-3512a48acdd0
this is upstream main branch's toggle-component

umm could you upload original(?) bug too?

upload completed (in first comment)

you uploaded fixed version right?

yes
@Moon-DaeSeung


Time Unit Converter working

Describe the bug

Time Unit Converter working over negative values. Since time is never negative so this error needs to be handled

Possible solution

Approriate checks over entered values needs to added in order to resolve this issue;

Screenshots

Kindly assign this issue to me @sairish2001

Go ahead
Deadline 7 April,2021 (11:59 PM IST)


Bundle analyzer does not opens browser, if running from docker

When executing the pnpm analyze command through Docker, the report is generated but the browser does not open automatically. This issue makes it difficult for users to view the report easily.
Expected Behavior:
The pnpm analyze command should generate the report and open the default browser to show it when executed through Docker.
Steps to Reproduce:
Run pnpm analyze command in a Docker container.
Check if the report is generated and saved.
Check if the browser opens to display the report.
Suggested Solution:
Modify the Docker container to automatically open the browser when the pnpm analyze command is executed.
Tasks:
Update the Dockerfile to include the necessary browser package.
Modify the command that executes pnpm analyze to automatically open the browser after generating the report.
Test the changes to ensure that the browser opens successfully and displays the report.
Optional:
Document the changes made in the README file of the repository to help other contributors.

Fixed in https://github.com/wayofdev/next-starter-tpl/pull/94


Build fails while trying to deploy on blue mix

I could deploy this App when Blue mix was on DEA , Now after it moved to Diego when I try to deploy it again it was showing the following error .
Download http://repo1.maven.org/maven2/xalan/xalan/2.6.0/xalan-2.6.0.jar
Download http://repo1.maven.org/maven2/com/ibm/icu/icu4j/2.6.1/icu4j-2.6.1.jar
:findbugsMain FAILED
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':findbugsMain'.

FindBugs rule violations were found. See the report at: file:///home/pipeline/f1354224-5d67-4a0e-99fe-25a53aef37f3/build/reports/findbugs/main.xml

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED
Total time: 3 mins 27.22 secs
Finished: FAILED**

I'm working on this.


Scan: test_without_building not working like expected

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
I used this examples from the docs
I would like to use scan to build it once (build_for_testing) and then test different tests in different lanes.
For creating the xctestrun I use the following command which works like expected:
scan(
      workspace: 'Awesome.xcworkspace',
      scheme: 'AwesomeScheme',
      derived_data_path: "target/derivedData",
      sdk:'iphonesimulator',
      build_for_testing: true,
      slack_only_on_failure:true
    )

In the next step I would like to use the generated xctestrun file to run the UnitTests. This is not working.
scan(
        xctestrun: 'target/derivedData/Build/Products/Awesome_iphonesimulator10.3-x86_64.xctestrun',
        destination: '"platform=iOS Simulator,name=iPhone 6',
        only_testing:'UnitTests'
    )

The output is:
DEBUG [2017-08-16 10:27:35.78]: Checking if there are any plugins that should be loaded...
INFO [2017-08-16 10:27:35.99]: -------------------------------------------------
INFO [2017-08-16 10:27:35.99]: --- Step: Verifying required fastlane version ---
INFO [2017-08-16 10:27:35.99]: -------------------------------------------------
INFO [2017-08-16 10:27:35.99]: Your fastlane version 2.53.1 matches the minimum requirement of 2.53.1  ✅
INFO [2017-08-16 10:27:35.99]: ------------------------------
INFO [2017-08-16 10:27:35.99]: --- Step: default_platform ---
INFO [2017-08-16 10:27:35.99]: ------------------------------
INFO [2017-08-16 10:27:36.01]: Driving the lane 'ios unit_test' 🚀
INFO [2017-08-16 10:27:36.01]: ------------------
INFO [2017-08-16 10:27:36.01]: --- Step: scan ---
INFO [2017-08-16 10:27:36.01]: ------------------
INFO [2017-08-16 10:27:36.05]: $ xcodebuild -list -workspace ./Awesome.xcworkspace
Select Scheme:
1. Awesome Alpha
2. App Store Screenshots
3. Awesome

Before fastlane I was using the following command which works correctly:
xcodebuild test-without-building -xctestrun "target/derivedData/Build/Products/Awesome_iphonesimulator10.3-x86_64.xctestrun" -destination "platform=iOS Simulator,name=iPhone 6" -only-testing:UnitTests
From this I would assume that scan should looks like:
scan(
        xctestrun: 'target/derivedData/Build/Products/Awesome_iphonesimulator10.3-x86_64.xctestrun',
        destination: '"platform=iOS Simulator,name=iPhone 6',
        only_testing:'UnitTests',
        test_without_building:true
    )

But the output is the following:
INFO [2017-08-16 10:33:54.41]: -------------------------------------------------
INFO [2017-08-16 10:33:54.41]: --- Step: Verifying required fastlane version ---
INFO [2017-08-16 10:33:54.41]: -------------------------------------------------
INFO [2017-08-16 10:33:54.41]: Your fastlane version 2.53.1 matches the minimum requirement of 2.53.1  ✅
INFO [2017-08-16 10:33:54.42]: ------------------------------
INFO [2017-08-16 10:33:54.42]: --- Step: default_platform ---
INFO [2017-08-16 10:33:54.42]: ------------------------------
INFO [2017-08-16 10:33:54.43]: Driving the lane 'ios unit_test' 🚀
INFO [2017-08-16 10:33:54.44]: ------------------
INFO [2017-08-16 10:33:54.44]: --- Step: scan ---
INFO [2017-08-16 10:33:54.44]: ------------------
ERROR [2017-08-16 10:33:54.46]: You passed invalid parameters to 'scan'.
ERROR [2017-08-16 10:33:54.46]: Check out the error below and available options by running `fastlane action scan`
WARN [2017-08-16 10:33:56.61]: Lane Context:
INFO [2017-08-16 10:33:56.61]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios unit_test"}
ERROR [2017-08-16 10:33:56.61]: Unresolved conflict between options: 'xctestrun' and 'test_without_building'

Environment

<details><summary>✅ fastlane environment ✅</summary>

### Stack

| Key                         | Value                                       |
| --------------------------- | ------------------------------------------- |
| OS                          | 10.13                                       |
| Ruby                        | 2.2.4                                       |
| Bundler?                    | true                                        |
| Git                         | git version 2.11.0 (Apple Git-81)           |
| Installation Source         | ~/.fastlane/bin/bundle/bin/fastlane         |
| Host                        | Mac OS X 10.13 (17A330h)                    |
| Ruby Lib Dir                | ~/.fastlane/bin/bundle/lib                  |
| OpenSSL Version             | OpenSSL 1.0.2g  1 Mar 2016                  |
| Is contained                | false                                       |
| Is homebrew                 | true                                        |
| Is installed via Fabric.app | false                                       |
| Xcode Path                  | /Applications/Xcode.app/Contents/Developer/ |
| Xcode Version               | 8.3.3                                       |

### System Locale

| Variable | Value       |   |
| -------- | ----------- | - |
| LANG     | en_US.UTF-8 | ✅ |
| LC_ALL   | en_US.UTF-8 | ✅ |
| LANGUAGE | en_US.UTF-8 | ✅ |

### fastlane files:

<details><summary>`./fastlane/Fastfile`</summary>

```ruby
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
# All available actions: https://docs.fastlane.tools/actions
# can also be listed using the `fastlane actions` command

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.53.1"

default_platform :ios

platform :ios do

  ############################## PRE ##############################

  before_all do
    ENV["SLACK_URL"] = ""
  end

  desc "Build for testing"
  lane :build_for_testing do
    scan(
      workspace: 'Awesome.xcworkspace',
      scheme: 'AwesomeScheme',
      derived_data_path: "target/derivedData",
      sdk:'iphonesimulator',
      build_for_testing: true,
      slack_only_on_failure:true
    )

    slack(
      message: "Successfully built for testing"
    )
  end

  desc "Unit test on iPhone"
  lane :unit_test do
    scan(
        xctestrun: 'target/derivedData/Build/Products/Awesome_iphonesimulator10.3-x86_64.xctestrun',
        destination: '"platform=iOS Simulator,name=iPhone 6',
        only_testing:'UnitTests'
    )

    slack(
      message: "Successfully unit tested"
    )
  end

  after_all do |lane|

  end

  error do |lane, exception|
    slack(
      message: exception.message,
      success: false
    )
  end
end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://docs.fastlane.tools/actions

# fastlane reports which actions are used. No personal data is recorded.
# Learn more at https://github.com/fastlane/fastlane#metrics

`./fastlane/Appfile`
app_identifier "com.....lab" # The bundle identifier of your app
apple_id "...@com" # Your Apple email address

team_id "...." # Developer Portal Team ID

# you can even provide different app identifiers, Apple IDs and team names per lane:
# More information: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Appfile.md

fastlane gems

Gem
Version
Update-Status

fastlane
2.53.1
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
1.5.1

terminal-notifier
1.7.1

unicode-display_width
1.1.3

terminal-table
1.7.3

CFPropertyList
2.3.5

public_suffix
2.0.5

addressable
2.5.1

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.5.0

babosa
1.0.2

colored
1.2

highline
1.7.8

commander-fastlane
4.4.5

excon
0.55.0

faraday
0.12.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.0

gh_inspector
1.0.3

uber
0.0.15

declarative
0.0.9

declarative-option
0.1.0

representable
3.0.4

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

little-plugger
1.1.4

multi_json
1.12.1

logging
2.2.2

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.12.0

json
1.8.1

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.1

security
0.1.3

xcpretty-travis-formatter
0.0.4

bundler
1.14.6

faraday_middleware
<IP_ADDRESS>

plist
3.3.0

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.3

xcodeproj
1.5.1

generated on: 2017-08-16

```

Yeah, it looks like we restrict xctestrun, it's not allowed to run with build_for_testing or test_without_building
which, looking at the docs (as I suspected) you're totally right... you should be able to do what you're trying to do.
one thing you can try is running fastlane from a local checkout. inside scan/lib/scan/options.rb#159, you can remove test_without_building from conflicting_options:  array

@taquitos great thanks a lot and thanks for the fix! :)


Feature Request for signing up

#20 Feature Request for signing up

@Jinal-Prajapati  and @KanjiyaJinesh Please merge my PR if it looks good to you and let me know if you want any changes in it.

@Nevilkumar LGTM


FileDownloadRequestChain can get ReadRequest of length > 2GB which causes integer overflow

All RequestChains have been implemented considering the standard read method of InputStream where client asks for length in a int variable, hence we can never get read of more than 2GB.
But FileDownloadRequestChain is created during parallel warmup phase, in which we wait for readRequests on a file to accumulate for 10sec(default) and then merge the neighbouring reads and trigger FileDownloadRequestChain to download the data. These readRequests can belong to several read requests on InputStream and when accumulated can lead to a contiguous read of more than 2GB. Due to this the length variable in FileDownloadRequestChain will overflow leading to NegativeArraySizeException, see https://github.com/prestosql/presto/issues/3494.
Another issue to fix is the high consumption of memory by FileDownloadRequestChain. Since the readRequests it handles can be of large size, we should not allocate buffers of same size to download the data in one shot. Instead, we should read data in smaller buffer over multiple iterations.

Fixed by  #368


Use official LLVM git mirror

See https://llvm.org/docs/GettingStarted.html#git-mirror
The official LLVM project git mirror is at https://git.llvm.org/git/llvm.git/
The Clang mirror is https://git.llvm.org/git/clang.git/
Need to fix the deps.json file (and the README?)

I think @alan-baker fixed this.


Collaborate with SUSE/azurectl

Proposal: Work with the folks that are building this: https://github.com/SUSE/azurectl
I'm looking at adopting azurectl because I really don't want to keep having to use PowerShell and Windows to publish Linux images into Azure. azurectl today has the feature set needed to do an image publish. However, they lack other basics like being able to discover all/new regions to replicate too (https://github.com/SUSE/azurectl/issues/159).
It seems there might be an opportunity for collaboration and reduction of duplicated effort. At the very least, can we take their image publishing work and integrate it into azure-cli?

What became of this? Is there image publishing functionality in azure-cli at the moment?


fix(nuxi): Improve server listening when 3000 already used

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
fixed #19560 ,Improve server listening when 3000 already used

📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

The issue should be fixed with<EMAIL_ADDRESS>


Fix NameErrorRequire: uninitialized constant ActiveSupport::IsolatedExecutionState

Rails does not support requiring a specific internal file without first requiring 'active_support'.
This change resolves the following error:
AvaTax-REST-V2-Ruby-SDK/vendor/bundle/ruby/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:274:in `registry': uninitialized constant ActiveSupport::IsolatedExecutionState (NameError)
	from AvaTax-REST-V2-Ruby-SDK/vendor/bundle/ruby/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:269:in `instrumenter'
	from AvaTax-REST-V2-Ruby-SDK/vendor/bundle/ruby/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:206:in `instrument'
	from AvaTax-REST-V2-Ruby-SDK/vendor/bundle/ruby/2.7.0/gems/faraday-1.10.3/lib/faraday/request/instrumentation.rb:48:in `call'
	from AvaTax-REST-V2-Ruby-SDK/vendor/bundle/ruby/2.7.0/gems/faraday-1.10.3/lib/faraday/rack_builder.rb:154:in `build_response'
	from AvaTax-REST-V2-Ruby-SDK/vendor/bundle/ruby/2.7.0/gems/faraday-1.10.3/lib/faraday/connection.rb:516:in `run_request'
	from AvaTax-REST-V2-Ruby-SDK/vendor/bundle/ruby/2.7.0/gems/faraday-1.10.3/lib/faraday/connection.rb:202:in `get'
	from AvaTax-REST-V2-Ruby-SDK/lib/avatax/request.rb:26:in `request'
	from AvaTax-REST-V2-Ruby-SDK/lib/avatax/request.rb:10:in `get'
	from AvaTax-REST-V2-Ruby-SDK/lib/avatax/client/companies.rb:428:in `query_companies'
	from AvaTax-REST-V2-Ruby-SDK/spec/spec_helper.rb:20:in `<top (required)>'
	from AvaTax-REST-V2-Ruby-SDK/spec/avatax/client/accounts_spec.rb:1:in `require'
	from AvaTax-REST-V2-Ruby-SDK/spec/avatax/client/accounts_spec.rb:1:in `<top (required)>'
	from AvaTax-REST-V2-Ruby-SDK/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.5.4/lib/rspec/core/configuration.rb:1435:in `load'
	from AvaTax-REST-V2-Ruby-SDK/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.5.4/lib/rspec/core/configuration.rb:1435:in `block in load_spec_files'
	from AvaTax-REST-V2-Ruby-SDK/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.5.4/lib/rspec/core/configuration.rb:1433:in `each'
	from AvaTax-REST-V2-Ruby-SDK/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.5.4/lib/rspec/core/configuration.rb:1433:in `load_spec_files'
	from AvaTax-REST-V2-Ruby-SDK/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.5.4/lib/rspec/core/runner.rb:100:in `setup'
	from AvaTax-REST-V2-Ruby-SDK/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.5.4/lib/rspec/core/runner.rb:86:in `run'
	from AvaTax-REST-V2-Ruby-SDK/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.5.4/lib/rspec/core/runner.rb:71:in `run'
	from AvaTax-REST-V2-Ruby-SDK/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.5.4/lib/rspec/core/runner.rb:45:in `invoke'
	from AvaTax-REST-V2-Ruby-SDK/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.5.4/exe/rspec:4:in `<main>'

@svc-developer, could this be merged?

🍃


Fixed issue related to warning message: Re-preparing already prepared

It fixes warning message: Re-preparing already prepared query is generally an anti-pattern and will likely affect performance. Consider preparing the statement only once.

@lucius-pl Thank you, it looks like useful update. Can you fix diff which shows every line as changed (line ending issue probably)?

Fixed.


Update System.Reactive.Experimental to target .NET Standard

System.Reactive.Experimental (4.1.0 at time of reporting) targets .NET Framework 4.6:
https://github.com/dotnet/reactive/blob/1888ca8e4aced0f7168b5e3e23b40b92fe0a5ec2/Rx.NET/Source/facades/System.Reactive.Experimental/System.Reactive.Experimental.csproj#L3-L5
Any reason it cannot be updated to target .NET Standard 2.0 like System.Reactive?

Closing since #821 got closed.


Date is Incompatible with ColumnType

I have something like this
import { type Generated } from "kysely"

interface User {
  id: string
  createdAt: Generated<Date> // same with  ColumnType<Date>
}

const f = (u: User) => {
  return u
}

f({id: "id", createdAt: new Date()})

tsc -V
Version 5.1.3

tsc test.ts
test.ts:12:15 - error TS2739: Type 'Date' is missing the following properties from type 'Generated<Date>': __select__, __insert__, __update__

Any help will be appreciated.

Hey 👋
You're not supposed to use the type with the Generated columns in anything beyond what you provide to Kysely. Use Selectable<User> instead.

Thank you very much


Bug： Amino:JSON int/int64/uint/uint64 expects quoted values for javascript numeric support, got: 80.)

$rly tx link ping2kava
E[2020-05-01|01:22:05.315] - [kava-ibc] -> err(invalid character -- Amino:JSON int/int64/uint/uint64 expects quoted values for javascript numeric support, got: 80.)

I've been unable to consistently reproduce this issue and I'm pretty sure it has to do with version mismatch. If you continue to see this error please reopen the issue


Friends List #13431

Closes #13431, Ability to enable 'Delete friend' as a first click option in the friends list interface.

First ever PR, and I didn't find out how to link the issue to the Pull Request :(

I don't really see any valid use cases for having to mass-delete friends quickly. When do you intend on using it for?

I don't really see any valid use cases for having to mass-delete friends quickly. When do you intend on using it for?

Ah, so not every issue on the issue board should be open for a fix? I didn't create the issue, but seems like something good for a first contribution. So should this become obsolete then?


Unable to run test script

Are you requesting a feature or reporting a bug?
Bug
What is the current behavior?
Getting this exception: ERROR Unable to establish one or more of the specified browser connections. This can be caused by network issues or remote device failure.
How would you reproduce the current behavior (if this is a bug)?
testcafe chromium:headless testscript.js
Specify your

operating system: CentOS6
testcafe version: 0.19.2
node.js version: 8.11.3

testcafe --list-browsers
Using locally installed version of TestCafe.
chromium
$ yum list installed | grep chromium
Note Red Hat Network repositories are not listed below. You must run this command as root to access RHN repositories.
chromium.x86_64                  31.0.1650.63-2.el6        @chromium-el6

Hi @cmaree, please check that you have all required dependencies installed.


[BUG][python] Reference Error when using schema with optional properties

Bug Report Checklist

[x] Have you provided a full/minimal spec to reproduce the issue?
[x] Have you validated the input using an OpenAPI validator (example)?
[x] Have you tested with the latest master to confirm the issue still exists?
[x] Have you searched for related issues/PRs?
[x] What's the actual output vs expected output?
[ ] [Optional] Sponsorship to speed up the bug fix or feature request

Description
When transforming the schema that have a additional properties, the created python file will have unresolved references in the TypedDict for the optional properties.
Given the yaml file below, the created multi_properties_schema.py file will have following definition for the optional properties:
MultiPropertiesSchemaOptionalDictInput = typing.TypedDict(
    'MultiPropertiesSchemaOptionalDictInput',
    {
        "data": typing.Union[
            DataTupleInput,
            DataTuple
        ],
        "message": str,
    },
    total=False
)

However, the DataTupleInput and DataTuple can not be referenced which lead to an error NameError: name 'DataTupleInput' is not defined during runtime.

openapi-json-schema-generator version
Version 4.1.2

OpenAPI declaration file content or url
openapi: 3.0.0
components:
    examples: {}
    headers: {}
    parameters: {}
    requestBodies: {}
    responses: {}
    schemas:
        MultiPropertiesSchema:
            properties:
                status:
                    type: integer
                    format: int32
                data:
                    items:
                        $ref: '#/components/schemas/ItemsSchema'
                    type: array
                message:
                    type: string
            type: object
            required:
                - status
            additionalProperties: false
        ItemsSchema:
            properties:
                name:
                    type: string
                additionalProperty:
                    type: string
                secondAdditionalProperty:
                    type: string
info:
    title: the test title
    version: '1'
    description: 'The test REST API'
    contact: {}
paths:
    '/example/get':
        get:
            operationId: GetExample
            responses:
                '200':
                    description: Ok

Generation Details

Steps to reproduce

Related issues/PRs

Suggest a fix

Thank you for reporting this bug. Will ItemsSchema always be type object?
In your definition, when it is type object, the properties constraints apply, and if not then it can be any other type.

This has been fixed in version 4.1.3


Update azure-stack-vaas-troubleshoot.md

Update the location to the images

@sethmanheim - as this is in the public repo, the author must sign off.  Is this ready to merge?
Thanks.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@Jak-MS Thanks for the sanity check -- I sometimes assume if it's from an internal person, it's in the private repo. #sign-off


Update ORC and Hive dependency versions in the license binary file

The ORC and Hive dependency versions were upgraded in https://github.com/apache/pinot/pull/12956. This patch updates the license binary file with the new versions.

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

Project coverage is 62.06%. Comparing base (59551e4) to head (e8753f6).
Report is 347 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master   #12986      +/-   ##
============================================
+ Coverage     61.75%   62.06%   +0.30%
+ Complexity      207      198       -9
============================================
  Files          2436     2502      +66
  Lines        133233   136503    +3270
  Branches      20636    21128     +492
============================================
+ Hits          82274    84716    +2442
- Misses        44911    45511     +600
- Partials       6048     6276     +228

Flag
Coverage Δ

custom-integration1
<0.01% <ø> (-0.01%)
:arrow_down:

integration
<0.01% <ø> (-0.01%)
:arrow_down:

integration1
<0.01% <ø> (-0.01%)
:arrow_down:

integration2
0.00% <ø> (ø)

java-11
<0.01% <ø> (-61.71%)
:arrow_down:

java-21
62.06% <ø> (+0.43%)
:arrow_up:

skip-bytebuffers-false
62.03% <ø> (+0.28%)
:arrow_up:

skip-bytebuffers-true
62.02% <ø> (+34.30%)
:arrow_up:

temurin
62.06% <ø> (+0.30%)
:arrow_up:

unittests
62.05% <ø> (+0.31%)
:arrow_up:

unittests1
46.57% <ø> (-0.32%)
:arrow_down:

unittests2
27.93% <ø> (+0.20%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


[Feature] Not Found text after using search

Currently, whenever using search, and typing not existing resources, the user sees an empty page.
It'd be great to at least have a text there's nothing found.

Did I add a search input to mine?

No, sorry. I confused the forks.

@eduardconstantin, what about having something on the last page of the exam? I think it's also for your codebase.

I think that is the practice mode, it should go to the first question if you press next

I think that is the practice mode, it should go to the first question if you press next

Yes, some kind of overview would be nice, I think.


Docs say about isScrollable  which is not supported

Describe the bug
Not sure this should be a feature request.. The regular TabBar supports isScrollable property to make the tabs scroll. The GFTabBar source code has few lines about this property but it's support is not present.
Expected behavior
isScrollable boolean property should be present.
Smartphone :

Device: Redmi Note 7 Pro
OS: Android 9

@Purus Hey, it will be fixed in our upcoming version


Bump org.sonarqube from <IP_ADDRESS>3 to <IP_ADDRESS>29

Bumps org.sonarqube from <IP_ADDRESS>3 to <IP_ADDRESS>29.

updated-dependencies:

dependency-name: org.sonarqube dependency-type: direct:production update-type: version-update:semver-major ...

Change description
Enter a description.
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/SPTRIBS-
Before merging a pull request make sure that:

[ ] tests have been updated / new tests has been added (if needed)
[ ] README and other documentation has been updated / added (if needed)

If this ticket will have any visible impact on users and is not behind a feature toggle, make sure that:

[ ] this ticket been reviewed by QA
[ ] the user story been signed off by the PO

Note that bug fixes, dependency updates and technical tasks do not directly impact the user experience and can be merged without QA and PO review.
If this user story cannot be immediately merged find a way to put it behind a feature toggle and get it merged.

Bump org.sonarqube from <IP_ADDRESS>3 to <IP_ADDRESS>29