Item Dublication: Explorer get items every time I relog into a server

I'm playing the Explorer class and every time I log in to my server I get a copy of all 9 maps, compass, and clock.
I will look for a log and post it
Edit:
Found this. Appears in the server console when I log in. Seems related:
[19:12:11] [Server thread/WARN]: Player class_3222['Ninjaneer0'/27463, l='ServerLevel[world]', x=8.03, y=64.00, z=671.11] could not be synced because server networking isn't set up yet.
Edit 2: Latest log file:
latest.log

Should be fixed if you update your Origins version (not Origins: Classes, though you can update that too). Let me know if you're still experiencing this, then I'll reopen this issue.


Question about Fusion Transformer

Hi, thanks for sharing this amazing project!
When I look into the file "layers/voxel_mix.py", I find the mixing code is a little different from your paper.

However, the code in line 57 is like this:
mix_feature = torch.cat([lc_feature,gl_feature],dim=1)

I am wondering which method do you use, thanks

Hi! Thank you for your question. This version of the code is used for an ablation study, and I apologize for not updating it to the Fusion Transformer version. In our work, we used the Fusion Transformer, which achieved better results but posed challenges during training. If you are working on a related project, I recommend trying the simplified version as shown in the code, by simplifying concate the features, the performance would also increase.

Thank you for your reply.
I find the ideal of mix layer very interesting. And I am wondering how to obtain the qkv in your fusion transformer?
Could you show us the code of this transformer module which described in your paper?


Remove redundant SignedTransaction::Signature

Since we can remove the op feature gated signature logic from reth-primitives, the signature AT is redundant
Ref https://github.com/paradigmxyz/reth/issues/12184

btw wondering which parts of the sdk actually need the fn signature() -> &Signature? wouldn't it be sufficient to just have something like trait Transaction { fn recover_signed(&self) -> Option<Address> }? that way the abstraction does not require each transaction to carry a concrete signature

right, perhaps we can get around it like this, I think the only place we need to interact with the sig directly is win rpc, and this likely goes away and can be abstracted.
so we can proceed with this pr and should consider removing the sig fn if possible


Policy and strategy for supporting evolving browsers

[ ] Firefox
[ ] Internet Explorer
[ ] Chrome
[ ] Safari

A browser support table has to be more specific than some browser names. Firefox releases a new version every six weeks, Chrome is on a similar schedule releasing 7 new versions in 2015 alone. Internet Explorer had a traditionally longer cycle, but has released 10 and 11 to fanfare, while some organizations are still stuck (very sadly) with the extremely crippled (and security vulnerable) 8 and 9. Meanwhile, they're releasing a completely new browser to replace Internet Explorer entirely in a few months. Safari, Chrome, and Firefox all have both desktop and mobile versions, with slightly different versions that track in parallel.
Current versions of major browsers:

Chrome 43
Firefox 38
Safari 8
Internet Explorer 11

A increasingly popular rule of thumb is to support the most recent two versions of each supported vendor, but in any policy you adopt you have to be clear about the versions you support and how you track the changing landscape of new browsers being released.

I am happy to go with the rule of thumb of the most recent two versions of each of the above 4 vendors.  I'd prefer to the maximal extent possible not to have a lot of browser specific conditionals.  If we can keep the code simple so that the same code works across all browsers that is preferable.

@mauriel133 has this testing been done on the current My Resources page?

I have conducted filtering tests in the latest versions for Chrome, Firefox and Safari. The issues we found were fixed before the deployment of the new My Resources page.
I will test next for Internet Explorer.

Title repurposed to reflect that we still need to address support for browsers, but that this is a back burner issue at present.

I am more accustomed to seeing this type of ticket in Jira/Trello and not GH Issues. The challenge with HydroShare is that it is cross-organizational (and technically open source, though we don't have any/many contributors in that regard as far as I know) and coordinating that Trello would be more meta/overhead work than value provided. I like our current way of working, sometimes chaotic but efficient and workable. Still vote to move this ticket out to a google doc or something.

Design, Customer Support, Customer Documentation, QA Testing Frameworks and Infrastructure ....

Closing.  This has drifted from the original problem which was that 4 years ago something did not work on some type of browser.  I am closing.  We can manage the browser support and other items mentioned elsewhere.


Spelling mistake in tools/cds-cli.md

The section Sample Records in the cds add documentation in tools/cds-cli.md contains a spelling mistake.
The current text is "Watch a short video by DJ Adams to see this in acion."
It text should read "Watch a short video by DJ Adams to sett this in action."

Hello,
Thank you for reporting this issue!

Hello,
This has been changed on the deployed branch and will be seen on main when the two are synchronised.
Best regards,
Maha

Fixed on cap.cloud.sap:
https://cap.cloud.sap/docs/tools/cds-cli#sample-records


ud851-Exercises/Lesson06-Visualizer-Preferences/T06.01-Solution-SetupTheActivity/

Is return true; missing from onOptionsItemSelected in the SettingsActivity when the menu item is home? Asking this because the official guide has the return statement: https://developer.android.com/training/implementing-navigation/ancestral.html#NavigateUp

The code should have return true; since the event is consumed.


New version, please?

Hi - I know these issues asking for new versions are sometimes annoying, and I apologize if this is one of them... but I'd really like to use the changes in #594 (82a5de08212ce5004d3bf2a923786ec4cb19b73b), which was merged a couple of months ago. #562 has been sitting for a little longer than that.
Is there anything that I/we can do to help get a new version published to npm? ❤

Sorry, I'm close but still hoping to drive to 0 open issues for the next release. Various PRs have taken time I'd otherwise have spent on this. The upcoming holiday period will hopefully give me an opportunity to wrap this up.

Here's an easy one: I'd like someone to verify this change correctly interoperates with Prettier and add the missing ol_single parameter to the example: https://github.com/DavidAnson/markdownlint/commit/cc701ea70023ce172883e916c9ec91ffc940d8e9
A new unit test for Prettier interoperability might be nice, but I do not want to add a dependency on that project. It is probably enough to make the one-line edit to the sample.

Note to self: Improve MD011/MD013/MD022/MD031/MD032/MD033/MD034/MD040/MD043/MD051/MD053, generate/separate documentation, improve documentation, update dependencies.

🎉 Hooray! Thanks!


browser-plugin: fix full update handling

This is a problem? Since I wrote the code for this I'd personally like to resovle it. Could you explain how it's broken exactly?

I need to verify what happens, but when I did a full update after the browser had already received diff updates it did not appear to update the template.

I'll look into the issue for you

This may actually be because the update went out before sending the mqtt message.

Yeah, just verified that was the issue.


Make the CI Green Again

Added helper scripts to run python tests and linter locally
Also run linter on api module
Fix most issues

Closes #186

Does the title of this PR imply, that the CI was ever green before?

it was, about 150 prs ago
On Wed, Oct 10, 2018, 12:00 PM Thomas Gassmann<EMAIL_ADDRESS>wrote:

Does the title of this PR imply, that the CI was ever green before?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mobydq/mobydq/pull/187#issuecomment-428430207, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AE3bVlQ831L9hLJQa_pdmB8zIiJPG8Qaks5ujXDhgaJpZM4XSUX6
.


Adding two openfoam installs:

new containerised module openfoam-org-container/10
new bare-metal installation of openfoam/v2206

The openfoam-org:10 image is already in quay, so the creation of the corresponding containerised module with shpc should work fine (as for other openfoam containers). Installation of the containerised module can proceed immediately.
The bare-metal install was ready since december but never went through as I did not updated the installation path to be an application. I have modified the modules.yaml file for that to be ready. Installation of the bare-metal vesion can proceed immediately.

@marcodelapierre

PR to the singularityhub requested an update to use full paths in the aliases, this has been done and re-submitted

The settings.sh file has been updated to only install as modules those containers that have been rebuilt with mpich base image from ubuntu20.04.

PR to the singularityhub is now waiting for a review from @marcodelapierre


npm links with git:// protocol

Link of some modules anchors git URL not github repo.
For example, gulp's package.json
Hover mouse on deprecated, interpret, etc...

Thank you very much for reporting this, @highdali. This was just solved by https://github.com/fiatjaf/module-linker/commit/2a6ae1a0d9b45f01492f6f77d09c4d0693cd8eef and will be released.


Autorotate based on exif not working

Both in the browser and in node, Jimp is not autorotating based on exif.  I'm using Jimp.read(buffer), does autorotate not work with buffers?
Here's the typescript code
let image = await Jimp.read(buffer);
let photo = await image.cover(
1920.
1920,
Jimp.HORIZONTAL_ALIGN_CENTER | Jimp.VERTICAL_ALIGN_MIDDLE,
);
buffer = await photo.getBufferAsync(Jimp.MIME_JPEG);
the buffer then contains an image with the rotation exif information stripped out, but not rotated properly.  This also happened on 0.13.0.

The behavior I'm seeing is that jimp is rotating the image but preserving the exif data that says the image is rotated.

I can confirm the behavior described by Nigel.
I load a picture from a buffer and resize it (I want to make thumbnails). The thumbnail is saved with the proper orientation in the raw image data (the picture is rotated so that the up is up, etc in the raw image data) but it retains the EXIF metadata that say the picture should still be rotated. So my thumbnail ends up misoriented.
Here's the relevant code:
    this.imgJimp = await Jimp.read(this.image); // <= this.image is a Buffer
    // *snip* some stuff to get proper values for maxW and maxH *snip*
    return this.imgJimp
      .resize(maxW, maxH)
      .quality(this.THUMBNAIL_JPEG_QUALITY)
      .getBufferAsync(Jimp.MIME_JPEG);

My source image is 90° to the right, with EXIF data saying to put it straight.
My thumbnail is straight... with EXIF data saying to put it 90° to the left
(my wanted result is a straight thumbnail with no EXIF rotation data)

Actually, since OP mentioned it might be a Buffer-specific issue, I tried the following and still had the problem, so it's not Buffer-specific:
    const dummyPicPath = path.join('/', 'dummy4242.jpeg');
    fs.writeFileSync(dummyPicPath, this.image);
    this.imgJimp = await Jimp.read(dummyPicPath);
    fs.unlinkSync(dummyPicPath);
    // then same "return" as in my previous comment

Has anyone figured out how to overcome this or have an estimated fix date? This is causing a lot of problems for me right now.

You could probably implement a JS workaround using stuff like ts-exif-parser and/or this
https://stackoverflow.com/questions/41490122/strip-exif-data-from-image-node-js-addressing-a-possible-bug-in-the-original-v
I ended up implementing my thumbnailing thing in Rust. It seemed the cleaner way to go and I liked the speed improvement.

No exif data is sometimes better than wrong exif. The 'ugly patch' I've used is to clear out the internal exif buffer
(jimp.bitmap as any).exifBuffer = undefined;

Right before jimp.getBufferAsync.

I have the same issue. And for me 'v0.10.3' is the latest version that auto rotate images (and resize). From a EXIF meta tag to actual pixels that are rotated. Rotating the pixels is what I would like to achieve.
Anyone a suggestion to get this working in a newer version. I'm using the following javascript code:
jimp.read(sourceFilePath)
.then(image => {

	image.resize(1000, jimp.AUTO);
	image.quality(80);

	image.write(targetFilePath, () => {
		process.stdout.write("≈");
		resolve(true);
	});

})
.catch(err => {
	console.error(err);
	resolve(false);
});


Missed opportunity to name the repository goreTeX

Haha. Good Old REproducible TeX?

That's horrible. All of it.


Errors on using NamedTuple in function argument

I'm a Julia noob coming from the statically checked TypeScript world, so don't assume competence here.
I have this code in main.jl:
Circle = @NamedTuple begin
    radius::Float64
end

function area(c::Circle)
    pi * c.radius^2
end

area(Circle(2))

When I report_and_watch_file("main.jl"; annotate_types = true) I get
[toplevel-info] entered into src/main.jl
[toplevel-info]  exited from src/main.jl (took 0.008 sec)
═════ 1 toplevel error found ═════
┌ @ src/main.jl:31
│ ArgumentError: invalid type for argument c in method definition for area at src/main.jl:31
└──────────────────

Ok, so @krrutkow's suggestion is to add const:
const Circle = @NamedTuple begin
    radius::Float64
end

function area(c::Circle)
    pi * c.radius^2
end

area(Circle(2))

and that works. Close the issue if you see fit!

Yes, a top-level definition (like function definition) with accessing to global variables is really troublesome for JET.jl.
#143 will fix this kind of case, though.
As a side note, you can have a configuration file like below and the specified pattern will be concretized as actual execution,
and you can analyze your file w/o problem even if you don't declare Circle as const (even w/o #143)

.JET.toml

concretization_patterns = ["Circle = x_"]

(see https://aviatesk.github.io/JET.jl/dev/config/#JET.ToplevelConfig if interested)


Add support for building on python3.8

Python 3.8 should be back-compatible with everything on the previous versions, furthermore, I have run the pre_push checks and the unit tests on 3.8 without any new syntax errors or DeprecationWarnings.

Should we add a line here as well: https://github.com/praw-dev/praw/blob/master/setup.py#L33

Should we add a line here as well: https://github.com/praw-dev/praw/blob/master/setup.py#L33

Sure, if you want you can start a PR on my branch, but I am going to implement that change now.

Thanks! I love these great efforts of your.


FormBuilderValidators

In the new version 7.1.1
I don't find FormBuilderValidators for create a list of validators??
How I can add list of validators?

The last year I used flutter_form_builde 6.0.1 and used FormBuilderValidators without add other package.
So does that mean now in the new version we need to add separated?

I get It.
I'm going to use the packages in the new way.
Thanks a lot!

Thanks a lot!


tests exercising the go linker functionality

Hi there,
We're about to pull this change from you into our buildpack:
https://github.com/heroku/heroku-buildpack-go/commit/a0a82e1a3fc0d0a2158b24826b2e6c45559799cd
We wrote these tests to exercise this functionality if you're interested in pulling them in:
https://github.com/cloudfoundry/go-buildpack/commit/3a6deb112ffe2da76614de1c350f904d9192d859
Thanks!

For full context, the Cloud Foundry team maintains a buildpack that's downstream from heroku's buildpack.
The -ldflags feature didn't have test coverage, so we added test coverage downstream. This ticket is just pointing out our tests, in case Heroku wants to pull them in (or do something similar) in the Heroku repo.
Thanks!

There is now a test for this when using godep, but handling is the same no matter which manager is in use atm: https://github.com/heroku/heroku-buildpack-go/blob/master/test/run#L112-L127


hard mode will make hekate3.8.0 frozen when hekate frontpage right site emuNAND is pressed+using v4 hwfly OLED chip

After getting in atmosphere first time, going back to hekate3.8.0,
modifying the .ini by hard mode will make hekate3.8.0 frozen when hekate frontpage right site's  emuNAND is pressed+using v4 hwfly OLED chip.
EZ mode no problem. Soft modding switch no problem.

johnkelvinliu

This repository does not include any hekate configs, are you sure you're submitting this issue to the correct repository?
The generated 'patches.ini' ( https://github.com/borntohonk/SigPatches/blob/master/hekate_patches/patches.ini ) is not a config file, nor is it loaded without a proper hekate config file.

@johnkelvinliu I'm also assuming you mean hekate version 5.8.0, not 3.8.0, as 5.8.0 is the latest. ( https://github.com/CTCaer/hekate/releases/tag/v5.8.0 )


Add population pyramid

Add a population pyramid to each country.

(This feature is beyond the proposal and may not be implemented.)

Looks cool! How would this pyramid be displayed in the map if implemented? Hover by country?

@anqi-lu I plan to display it in the right-bottom of the map, so that you can change the year to see its changing over time.

This is cool! My project has a similar issue to interactively select a country : https://github.com/Q-Zhao/dataviz-project-QZhao/issues/3

Looks awesome, great design. It inspires me a lot.


1x, 2x results using the inference_s3diff.py and s3diff.pkl

I would like to infer a 1x & 2x SR results too using the provided model 's3diff.pkl'  and   inference_s3diff.py.
My test image is 128x128. The results of prediction are always 4x (512x512) even if I mention '--scale 1'
But when I use the 'gradio_s3diff.py'  I can easily get the 1X, 2X results

The same applies for models trained on custom dataset.
How to infer 1X, 2X results using inference_s3diff.py ?
Thanks in advance.

You can change the argument sf in S3Diff/configs/sr_test.yaml to 1 or 2 to obtain 1X or 2X results.


Using FBSnapshotTestCase for testing UI

[x] I have read this issue template and provided all possible information.
[x] I'm using CocoaPods and have run pod update before filing this issue.

Hello!
Just wanted to ask what do you think on testing UI with FBSnapshotTestCase.
If you think it's fine — i can prepare initial PR.
Want we need to decide is:
— Devices which we will be testing on.

Hi @Austinate! Sorry for the late reply.
Sounds interesting! What would it entail exactly?


Reorder Python artifact commands

What it says on the tin. Explanatory comments added inline.

Can one of the admins verify this patch?

Can one of the admins verify this patch?


Ensure equivalence between a nested composite and the same state/processes merged into the outer composite

We should be able to perform a "cut", and wrap a subtree in a "composite", and also "uncut" where we unwrap a composite and merge its states, and have everything behave in an equivalent way.

The cut needs to generate a bridge (!)


ProgressBar for .apply when looping over rows

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 20.04.4 LTS
Modin version (modin.__version__): 0.14.1
Python version: 3.8
Code we can use to reproduce:

import modin.pandas as pd
import tqdm
from modin.config import ProgressBar
ProgressBar.enable()

X = pd.DataFrame([[1,2,3]]*100, columns=["a", "b", "c"]) # be wary that this produces its own progress bar
X.apply(lambda x: 1, axis=1) # does not produce progress bar; if axis=0, progress bar is produced

Describe the problem

The ProgressBar seems to not appear when apply is used with axis=1 (iterating over rows). It does appear for axis=0, but oddly not if a Series is returned (common pattern for constructing new dataframes).
If running the example, be careful to disregard the progress bar generated by the pd.Dataframe command.
Source code / logs

@Bonnevie thank you for reporting this issue! I also see the behavior you're describing. I'm investigating what it would take to extend the progress bar to axis=1 and to axis=0 functions that return Series.

@Bonnevie
Thanks for opening this issue! ProgressBar currently works by counting the number of successful Ray remote tasks completed, where each task corresponds to a Modin Block Partition. The apply function you declared is a "full-axis" function. To compute these types of functions, Modin converts the Block Partitions to Full Axis Partitions and applies the asynchronously. However, we have not instrumented Full Axis Partitions to report progress, so neither apply with either axis will show the progress of the function.
Confusingly, with axis=1, after applying the function on Full Axis Partitions (and converting back to Block Partitions), we need to compute a transpose on each Partition in order to return the column-oriented Partition as a row-wise series (note the result will be a Series with the old columns as the new row index)
a 1
b 1
c 1

It is this transpose which is applied to Block Partitions that is being Progress Bar'ed.
TDLR: ProgressBar is not implemented for the type of function you applied (full axis), but is for the transpose applied at the end of a columnar operation. This was a super interesting issue that you raised, and we are now considering adding ProgressBar for full axis operations too.

@Bonnevie I would also like to add to @jeffreykennethli 's response:

Issue #4167 says that we're missing some functions at the internal level of the Modin dataframe. Among those are the ones we would need to give an estimate of apply progress. I think just making apply work shouldn't be too much effort. I mentioned it in a comment on #4167 and we will try to address the feature soon.
Each progress bar should tell users which frame-level operation it's for. In the case of axis=0 apply that you show here, it should explain that it's showing the progress of the transpose. I have filed #4447 for that new feature.

@Bonnevie please let us know whether our explanations help. If you understand the behavior you're seeing, I'll close this issue and the Modin contributors will try to address the issues that I mentioned in my previous comment.

@Bonnevie I'm closing this issue. If you have any more concerns, please comment here. We'll continue tracking work on the followups: https://github.com/modin-project/modin/issues/4443#issuecomment-1121221578


Investigate and move away from deprecated io/ioutil on go 1.16

io/ioutil is deprecated in go 1.16: https://golang.org/doc/go1.16#ioutil
Move away from it. Our uses:
vic@viccuad ~/suse/hypper $ ag ioutil
cmd/hypper/require/args_test.go
20:     "io/ioutil"
74:                     cmd.SetOutput(ioutil.Discard)

cmd/hypper/hypper_test.go
5:      "io/ioutil"
97:             KubeClient:   &kubefake.PrintingKubeClient{Out: ioutil.Discard},

cmd/hypper/hypper.go
4:      "io/ioutil"
74:     actionConfig.KubeClient = &kubefake.PrintingKubeClient{Out: ioutil.Discard}
77:             b, err := ioutil.ReadFile(path)

internal/test/test.go
22:     "io/ioutil"
65:     actual, err := ioutil.ReadFile(actualFileName)
85:     expected, err := ioutil.ReadFile(filename)
101:    return ioutil.WriteFile(filename, normalize(in), 0666)

While it's nice to be on the bleeding edge, one of the goals of this project is to be imported by others and used as a go package.
I just looked at rancher/rancher and it's using Go 1.14. I wouldn't be surprised if they move to 1.15 next rather than right to 1.16. We should be conservative with adopting the 1.16 changes for wider support. When ranchers other stuff moves to 1.16 we could look at a move.

Thanks for the information :). Fair enough, I was too eager with book keeping. Closing this for now then, it's going to be quite a while.


Add snippets for markdown

At the moment, the snippets for markdown cover most of the basic syntax, however there are no snippets for inserting different heading levels. For extended syntaxes, there are no snippets for tables, strikethrough, and task lists.
I propose adding the following snippets to markdown.code-snippets:
{
  "Insert heading level 1": {
    "prefix": "heading1",
    "body": "# ${1:${TM_SELECTED_TEXT}}",
    "description": "Insert heading level 1"
  },
  "Insert heading level 2": {
    "prefix": "heading2",
    "body": "## ${1:${TM_SELECTED_TEXT}}",
    "description": "Insert heading level 2"
  },
  "Insert heading level 3": {
    "prefix": "heading3",
    "body": "### ${1:${TM_SELECTED_TEXT}}",
    "description": "Insert heading level 3"
  },
  "Insert heading level 4": {
    "prefix": "heading4",
    "body": "#### ${1:${TM_SELECTED_TEXT}}",
    "description": "Insert heading level 4"
  },
  "Insert heading level 5": {
    "prefix": "heading5",
    "body": "##### ${1:${TM_SELECTED_TEXT}}",
    "description": "Insert heading level 5"
  },
  "Insert heading level 6": {
    "prefix": "heading6",
    "body": "###### ${1:${TM_SELECTED_TEXT}}",
    "description": "Insert heading level 6"
  },
  "Insert table": {
    "prefix": "table",
    "body": [
      "| ${1:Column1}  | ${2:Column2}   | ${3:Column3}   |",
      "|-------------- | -------------- | -------------- |",
      "| ${4:Item1}    | ${5:Item1}     | ${6:Item1}     |",
      "${0}"
    ],
    "description": "Insert table"
  },
  "Insert strikethrough": {
    "prefix": "strikethrough",
    "body": "~~${1:${TM_SELECTED_TEXT}}~~",
    "description": "Insert strikethrough"
  },
  "Insert task list": {
    "prefix": "task",
    "body": ["- [${1| ,x|}] ${2:text}", "- [${3| ,x|}] ${4:text}", "${0}"],
    "description": "Insert task list"
  }
}

I propose removing the "Insert heading" snippet. "Insert heading level 1" would does the same thing and would be consistent with the other heading levels snippets:
I would modify the "Insert code" snippet to include the word "inline" in the name and description:
Insert code": {
  "prefix": "code",
  "body": "`${1:${TM_SELECTED_TEXT}}`$0",
  "description": "Insert code"
}

I am happy to make a pull request for this if you wish?

I'd take a PR for the header and strike through snippets, along with the change to insert code
Tables and tasklist are probably better for an extension (the built-in markdown preview doesn't support task lists)

Cool. I'll submit a PR for that then 👍

I need to upgrade the RAM on my box to fufil the compile task, I only have 4GB atm 🙈 It will be a week for me to sort this out. 💪


Firefox: Console Errors

I'm seeing the following console error, even on the demo website in latest Firefox.
NotSupportedError: Operation is not supported

I've been seeing the same lately but thought it was related to Firefox (41.0.1) osx..

Any ideas on what it could be? I was also seeing this error on earlier versions of Firefox. I have a browserstack account so I'll investigate the infected versions.

No idea but I'd also try some older wavesurfer.js version.

@thijstriemstra I've verified that it's only on Firefox 41.0.1 on OSX. I tested 40 on both Windows 7 and OSX and it's fine. I don't know what Firefox changed in that patch but that's certainly something that broke your library.

Console errors appearing on Windows Firefox 44.0 same error message NotSupportedError: Operation is not supported

I'm afraid trying to find this bug involves dissecting all of the source code, a long process.


Problematic observations from recent engineering time, 20220413, 20220414, 20220416

This was discussed on Slack and by email, but I am unclear as to the status.  The beginning of the night on 20220413 featured engineering observations on main survey tiles.  We need to mark some of these exposures as bad.
QA for observations 20619/130091 and 25297/130094 look fine to me, though the night log reports that 25297/130094 did not have a turbulence correction applied.  I think we should keep these two observations.
QA for 22170/130095 looks terrible and this exposure needs to be marked bad and the tile reprocessed.  This duplicates https://github.com/desihub/desisurveyops/issues/43 and https://github.com/desihub/desisurveyops/issues/40 .
Night log reports observations of a few other tiles that may have already been marked bad and do not make the nightly QA (e.g., 22202, 22211, 22203, 20638).  Because there is no QA, I have not inspected these tiles.
On 20220414 the observers started observing backup tiles to avoid problems like the above.  But then they moved to BRIGHT tile 23075 and did more test observations.  It looks like we got 4 back to back short exposures there.
https://data.desi.lbl.gov/desi/spectro/redux/daily/tiles/cumulative/20375/20220414/tile-qa-20375-thru20220414.png
QA looks fine to me and I don't see major positioning problems like those we saw for other fast sequencer test observations.  It's certainly not normal survey observations to have 4 short exposures on a BRIGHT tile, though, so we could consider marking all of these as bad.  The rest of 20220414 looks fine to me.
On 20220417, I don't see anything dubious in the night log.  There's a weird exposure of 42426 in the nightqa.  It's weird because:

the QA only shows one observation on 20220416, so why am I seeing it on 20220416?  (note: tile was also observed on 20220417, so maybe the observation on 20220417 was marked bad, but I'm not sure I want to see it in that case?)
Positioning is bad on all petals except P0, so we'd want to mark the exposure as bad?
It looks to me like the 20220416 exposure on this tile was good, but the 20220417 exposure was bad.  But the QA script includes the flagged bad exposure on 20220417, making the positioning on all petals look bad despite the fact that this exposure was marked bad?  @araichoor .
https://data.desi.lbl.gov/desi/spectro/redux/daily/tiles/cumulative/42426/20220416/tile-qa-42426-thru20220416.png
https://data.desi.lbl.gov/desi/spectro/redux/daily/tiles/cumulative/42426/20220417/tile-qa-42426-thru20220417.png
I don't know why we would have failed to position on all petals; that never happens normally?

Nothing else exceptionally alarming.
Short version: let's mark 22170/130095 bad and reprocess.  Let's discuss 23075, 20619, 25297, but probably keep all of these; their QA is fine.  Let's check to see if there's a bug in the QA script where data from bad, excluded exposures are included in the positioner offset plots, as suggested by 42426.

about 42426 on 20220416/20220417:
I ve looked a bit, I m not 100% sure of what s going on.
but I suspect the issue comes from the fact that the daily cron job has not been run around those dates (see https://desisurvey.slack.com/archives/C01HNN87Y7J/p1650217810827989).
first, for instance, looking at the spectra-*log files, I see that the 20220417 redux does not use the 20220417 exposure, only the 20220416 one:
raichoor@cori03:~/Scripts> grep RUNNING /global/cfs/cdirs/desi/spectro/redux/daily/tiles/cumulative/42426/20220417/logs/spectra-0-42426-thru20220417.log
RUNNING srun -N 1 -n 1 -c 64 --cpu-bind=none desi_group_spectra --inframes exposures/20220416/00130563/cframe-b0-00130563.fits exposures/20220416/00130563/cframe-r0-00130563.fits exposures/20220416/00130563/cframe-z0-00130563.fits --outfile tiles/cumulative/42426/20220417/spectra-0-42426-thru20220417.fits --header SPGRP=cumulative SPGRPVAL=20220417 NIGHT=20220417 TILEID=42426 SPECTRO=0 PETAL=0

that explains why tile-qa-42426-thru20220417.png only reports the 20220416 exposure (it grabs the exposure list from the spectra*fits files).
then, about the disagreement between the two qa plots (20220416 vs. 20220417):
as those are both only using the 20220416 exposure, I d have expected those to be similar.
but the MEAN_DELTA_{XY} columns in the tile-qa-42426-thru2022041{6,7}.fits files are different, except for PETAL_LOC=0.
e.g.:
d16 = Table.read("/global/cfs/cdirs/desi/spectro/redux/daily/tiles/cumulative/42426/20220416/tile-qa-42426-thru20220416.fits","FIBERQA")
d17 = Table.read("/global/cfs/cdirs/desi/spectro/redux/daily/tiles/cumulative/42426/20220417/tile-qa-42426-thru20220417.fits","FIBERQA")
for petal in range(10):
    sel = d16["PETAL_LOC"] == petal
    print(petal, (d16["MEAN_DELTA_X"][sel] != d17["MEAN_DELTA_X"][sel]).sum())
=>
0 0
1 500
2 499
3 496
4 496
5 498
6 498
7 495
8 498
9 500

I don t understand how that could be.
I thought about a possible re-processing of the 20220416 exposure in between, but from the timestamps, it looks like not.
maybe @sbailey or @akremin could figure that out?

Just noting that some of the exposures from the night 20220413 were indeed already rejected as you've speculated.  That list here:
https://desi.lbl.gov/trac/tracmailman/browser/private/desi-survey/2022-April/003733.html

thanks; though the exposure in question here is from 20220417.
if I m correct, rejected exposures have EFFTIME=0, and this exposure from 20220417 has EFFTIME~4s, so it does not look to be blacklisted.
but, I realize now that this low EFFTIME may be the reason why it got filtered out by the pipeline, as I think I recall there is a cut on low EFFTIME (btw, is the cut value lower for BACKUP tiles?).
that at least explains the first part of the puzzle.
d = Table.read("/global/cfs/cdirs/desi/spectro/redux/daily/exposures-daily.fits","EXPOSURES")
d[d["TILEID"]==42426]["NIGHT","EXPID","TILEID","EXPTIME","EFFTIME_SPEC"]
<Table length=2>
 NIGHT   EXPID  TILEID      EXPTIME          EFFTIME_SPEC
 int32   int32  int32       float64            float64
-------- ------ ------ ------------------ -----------------
20220416 130563  42426<PHONE_NUMBER>835938 72.46405029296875
20220417 130673  42426 60.013885498046875 4.093623638153076

And, sorry to make this issue so multi-layered, but we need to decide whether or not to keep these tiles:
23075 - 4 back to back short exposures maybe with new sequencer on; no other reasons I know of to be unhappy with this tile
20619 - maybe observed with new sequencer
25297 - observed with new sequencer, night log says turbulence corrections are missing
Since these would all pass our normal QA metrics, I am inclined to keep them all, in which case we could do an MTL update tomorrow.  If we want to reflect more on these, we need to mark them as unsure to enable MTL updates in the interim.

We accepted 23075, 20619, 25297 when we did MTL updates yesterday.  I'm fine with that.  Outstanding issue in this ticket is to resolve the inconsistent MEAN_DELTA_X, MEAN_DELTA_Y on 42426 where an excluded exposure is being included in the mean X and Y?

about tileid=42426: I found the issue.
forget my previous comments, apologies.
the reason is that, the exposures list is inferred from looking at the first spectra*fits file found.
here, it is for petal 0, but that petal is discarded for the 20220417 exposure (130673); so the tile_qa/tile_qa_plot codes miss that exposure, which creates the apparent mismatch.
the plotted MEAN_DELTA_X and MEAN_DELTA_Y columns come from the redrock FIBERMAP extensions, so those consider both exposures for all petals, except for petal=0.
I m opening a PR with a fix...
thanks @schlafly for reminding me about that!

PR here: https://github.com/desihub/desispec/pull/1767
for this tile, maybe we d want to blacklist expid= 130673, and rerun the daily pipeline?

I think we just need to reprocess 20220417/130673, tileid 42426 to close this ticket.  @akremin, maybe?

Exp 130673 was marked to ignore, and the files removed at some point in the past. The claim was bad positioning, but I may have just been following Anand's May 9th message.
The tiles-daily.csv hadn't been updated, which led to the continued inconsistency. I have rerun that and the nightly QA. tiles-daily.csv now reflects the fact that 220416 is the LASTNIGHT and exposures-daily.csv reflects the 0s EFFTIME_SPEC for 20220417.
The one exposure on 20220416 got 72.5s EFFTIME_SPEC, so the tile remains completed even without these 4s of time.


uib date picker popup to be displayed in full screen width for mobile screen

Hi,
In desktop browser, the uib datepicker popup is displayed as configured. (either bottom top etc).
But in mobile screen, i want the popup to be displayed as full width.
current display

what i wanted..

i tried modifying the CSS, but its not positioning properly.
Can any one please help?

Closing this as this project is no longer being maintained, per the README and the ISSUE_TEMPLATE.


Package ... contains libraries, but not for the selected TargetFramework net452 in project ...

When I run paket.exe install, I got these warnings:

Package ... contains libraries, but not for the selected TargetFramework net452 in project ...

If 452 is not available will this fallback to net451 and net45?
It seems that packages xunit.assert and xunit.core are using dnxcore50 (.Net Core) and referencing all these libraries as Nuget-packages. So of course I use System.Collections and System.Linq in my other projects, but they are not using dnxcore. I don't have direct reference to core libraries via nuget.

Package Microsoft.Bcl contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\backend\myproj.fsproj.
Package Microsoft.Net.Http contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\backend\myproj.fsproj.
Package Zlib.Portable contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\backend\myproj.fsproj.
Package Zlib.Portable contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\backendcalc\backendcalc.fsproj.
Package Zlib.Portable contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Collections contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Diagnostics.Contracts contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Diagnostics.Debug contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Globalization contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.IO contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Linq.Expressions contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Private.Uri contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Reflection contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Reflection.Extensions contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Reflection.Primitives contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Reflection.TypeExtensions contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Resources.ResourceManager contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Runtime contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Runtime.Extensions contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Text.Encoding contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Text.Encoding.Extensions contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Threading contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Threading.Tasks contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\integrationtests\integrationtests.fsproj.
Package System.Collections contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.
Package System.Diagnostics.Contracts contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.
Package System.Diagnostics.Debug contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.
Package System.Globalization contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.
Package System.IO contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.
Package System.Linq.Expressions contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.
Package System.Private.Uri contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.
Package System.Reflection contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.
Package System.Reflection.Extensions contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.
Package System.Reflection.Primitives contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.
Package System.Reflection.TypeExtensions contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.
Package System.Resources.ResourceManager contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.
Package System.Runtime contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.
Package System.Runtime.Extensions contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.
Package System.Text.Encoding contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.
Package System.Text.Encoding.Extensions contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.
Package System.Threading contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.
Package System.Threading.Tasks contains libraries, but not for the selected TargetFramework net452 in project C:\git\myproj\unittests\unittests.fsproj.

Adding limit framework >= 4.0 will significantly lower the amount of warnings.

We're getting this issue as well and it's causing a bit of confusion.
Basically, if we install a package that supports .netcore but we don't use the .netcore support we get these warnings.
It's a weird situation really. I've made a reproduction here:
https://github.com/Rcomian/paket3dotnetcoreissue
It's a very simple repro.
We had a secondary issue which was warned correctly and we could resolve it, but was harder to see since the initial reaction is always, oh there's a hundred pointless warnings, ignore all.

that framework limit is fine since you don't use coreclr

@forki thanks. Buuuuuut I can't help feel that paket might be able to work this out itself. As I say, we have had legitimate warnings in this area that we don't want to quiet.

there is framework: auto-detect

There is and it works, but doing so means that now my .net core packages have been removed.
If I then switched to .netcore as a build target, we would have to re-run paket install, or maybe just restore.
But paket has this wonderful structure of conditionals everywhere so that we've not had to do that before - all packages were available and we could just build for different targets without having to recalculate packages in between.
The framework is fine as a workaround, I'm just not sure it's a solution.

I think this is an underlying issue that's causing other bugs, I've got 2 further build problems based on the same dependency issues:

I'm building from msbuild to single output folder for the solution. I'm getting "Could not find a part of the path 'bin\Release\System.Collections.dll'" for my non-dotnetcore build.
I'm trying to build projects with wixproj. But it's no longer including the wix targets because somehow the dotnetframework checks aren't working and the wix target import name isn't being set. This results in either trying to pull wix from the installed location (legacy wix upgrade) or trying to import with an empty path.

I'm not sure I can follow

I'll try for a reproduction on that repository

I've updated
https://github.com/Rcomian/paket3dotnetcoreissue
Double click paket.update.cmd for the warnings,
Double click build.cmd for the first build failure.

what do you expect it to do differently?

The paket.update.cmd I would expect to complete without warnings. It does the right thing to the files as far as I can tell, but the warnings are spurious, unnecessary.
The build.cmd - there's no reason for that to fail.
If you remove the /p:OutDir flag from the command, it does work.
But it's failing when looking for dependencies that it doesn't need.

so if the files are ok, then only thing for me to do is to look at the additional warnings and see if we get rid of those!?

warnings is step 1, for sure.
Step 2 would be to get the build.cmd working when we specify an output directory through msbuild. This might be a separate issue, looking at it.

still don't understand why you think the message is not correct?
It has libs for netcore, but not for net45!?

Ah, ok, no problem.
Ok this is really long, I'm sorry, but I'm trying to supply as much detail as I can.
This might be 3 or 4 different issues or 1 root issue, I'm not sure.
The message is a warning based on the currently selected framework.
Basically, one of the packages in the tree doesn't have libs for the currently selected framework.
That's fine as stands - but there's a problem.
That package (lets use System.Collections as an example). is not being depended on directly. It's indirect.
The direct dependency is AutoMapper.
With full .net 4.5.2, AutoMapper has no dependencies. So for the selected framework, we're good.
Now AutoMapper can depend on System.Collections, if the framework is .netCore.
I think it's correct that System.Collections should be downloaded and installed in the packges folder for this reason.
It's also correct to add System.Collections to the list of references behind the guard conditionals that say "If the currently selected framework is .netcore, then reference this assembly".
Paket has had this behaviour since day 1 and I love it. It's really powerful and correct to not have to re-install your nuget packages every time you switch frameworks.
So all that works.
But then paket looks at System.Collections, sees it only has assemblies for .netcore and not .net452 as currently selected, and prints the warning.
I come down hard on warnings in general, warning fatigue hides real problems. So I don't want spurious warnings.
But System.Collections isn't even going to be brought in as a dependency when we're building for .net452.
So the build would work - because we don't need System.Collections with this configuration, but the warning implies it won't.
So that's the warning issue. If that makes sense. I can try to explain another way if you like.
You can stop there for a moment, but there's an additional thing on the back of this:
Paket now creates an "AfterBuild" build step that copies dependencies to the output. This step is copying System.Collections to the output folder even tho it's not required in the current build.
That is, a build that is being built for .net4.5.2 that depends on AutoMapper which has no dependencies when used with .net4.5.2 is getting its additional dependencies from .netcore added to the output during build.
More than that, if you then specify the output folder using /p:OutDir on the msbuild commandline, it fails to copy System.Collections. It looks like the build step builds the path of where it expects the output to be, but because we specify it directly, the build step gets the wrong path and can't find what it's after.
So the build fails trying to copy something from the wrong location when it doesn't need it in the first place.
Which is messing our builds up :P
Now there is a workaround of sorts. Putting in Framework: >4.0
This helps for now.
But we would like to target .netcore in the future as well as .net4.5.2 (or 4.6 or 4.7 or whatever).
So although this workaround appears to solve the issue, it's kind of sidestepping it, rather than getting to the root of the problems.
There's another workaround: framework: auto.
This only installs the dependencies for the currently selected framework.
But if we want to target .netcore and .net452, we can't just change the msbuild commandline like we can now:
http://stackoverflow.com/questions/12003475/override-target-framework-from-command-line
The commandline version works normally because of the wonderful conditionals that paket adds to the csproj file that ensures that the right assemblies are referenced in the right situations.
But if you use framework: auto, those conditionals are cut down to only the framework that was selected when paket install was run.
So if you change the framework, suddenly there's no assemblies being referenced.
We'd need to run paket-install with the newly selected framework and change all the .csproj files.
There is an additional problem with the .wixproj files which I'm trying to pin down with a reproduction. Effectively it's looking like there are some conditionals being used that are always false, but right now I'm not sure.
To sum up.
I think there's an issue with paket bringing in dependencies it doesn't need. In particular, .netcore dependencies when the currently selected framework is .net452, or .net46
(I've just noticed the latest version of paket doesn't fail the build as I discuss here, it successfully copies the unnecessary dependent assemblies into the wrong folder).

thanks for clarification. that message should be gone in latest alpha.
Please test and if it works I will release it properly

Sorry for the delay. Yes the warning is gone, but is it right to get rid of the warning entirely? I still think it's valid to warn if, for example, I depend on AutoMapper with .net 452 and AutoMapper only supports .netcore ...

the warning is not gone entirely

Ok cool :D
works then

Thank you!


Query - how to report on number of connections in pool to upstream?

Hi
It doesnt appear to me at least, that there is any way to get at internal pingora metrics including the number of connections in the pool. Is there any way to do this?

or could we implement an optional trait for the proxy to receive pool connection callbacks for push/pop?

We might have the solution in place already depending on the exact problems to solve.  What problems are we trying to solve here?

So my upstream service has a soft limit on number of connections say 20000 on each upstream peer node, and I would like to be able to keep track of the number of connections open by the proxy to each upstream peer, reporting it as a metric every minute or so. Ideally I would have the number of inflight connections to each peer as well as number of connections idling in the pool for each peer. Currently i am able to keep track of number of inflight connections using the ProxyHttp trait, but I am unable to keep track of number of connections idling in the pool.
Thank you.

Excellent! That was something I expected.
So when you try to connect to your upstream with HttpPeer, you can put a Tracer object into it. Where the tracer itself can hold a Arc<AtomicUsize> where the tracing evens will be called whenever a connection is created and disconnected. From there you can access the real time number of connections (both active and in the pool idling) via a copy of the Arc<AtomicUsize>.

sounds good. many thanks.


Graphical saturation issue

Issue Type: Bug

Open VSC on my machine
Observe colors being whack

The above picture shows what the theme "Andromeda Italic Bold" looks like on my machine. This doesn't just pertain to the editor itself -- viewing a screenshot in the extensions marketplace on VSC will also show the colors looking the same way.

This above image shows what the colors should look like (pictured on another machine).
This happens no matter what theme I use, and happens regardless of if extensions are enabled.
VS Code version: Code 1.42.1 (c47d83b293181d9be64f27ff093689e8e7aed054, 2020-02-11T14:45:59.656Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (12 x 3696)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.92GB (8.66GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (6)

Extension
Author (truncated)
Version

csharpfixformat
Leo
0.0.84

gml-support
lia
1.7.2

python
ms-
2020.2.63072

csharp
ms-
1.21.11

unity-debug
Uni
2.7.2

vscode-icons
vsc
10.0.0

(2 theme extensions excluded)

Is #65816 relevant? Do you have multiple monitors?

Doesn't seem so, I have tired the various command line arguments suggested on this thread and other similar ones with no change. I only use one single monitor. A lot of similar issues seem to indicate this was an issue resolved with Electron 6.0.x but I am on the latest version of VSC.

@imlazyeye is this still an issue with latest insiders https://code.visualstudio.com/insiders ? Also what are the command line options you have tried so far ?


Idea: Infer types / parameters from runtime (V8 debugger/inspector protocol)

Given the new "infer parameters from usage" functionality, it would seem doable to do something similar like "infer parameters from runtime/debugger", especially in environments like VSCode, which tightly integrate a debugger.
In runtime you get most of the information to generate pretty good types, at least for a start, so... why not? This would be a massive help in migrating JavaScript to TypeScript.
Also, V8 has just recently introduced takeTypeProfile to the inspector protocol, that could be used to leverage just that. There's an example usage here: https://github.com/fhinkel/type-profile.

https://github.com/Microsoft/dts-gen attempts to do something like this, although it doesn't integrate with the editor.

You can implement some of these features in a language service plugin today. would love to see someone experiment with that.

dts-gen's functionality is now integrated into the compiler with #26588, so I think we've done this.


[SPARK-31468][SQL] Null types should be implicitly casted to Decimal types

What changes were proposed in this pull request?

This PR intends to fix a bug that occurs when comparing null types to decimal types in master/branch-3.0;
scala> Seq(BigDecimal(10)).toDF("v1").selectExpr("v1 = NULL").explain(true)
org.apache.spark.sql.AnalysisException: cannot resolve '(`v1` = NULL)' due to data type mismatch: differing types in '(`v1` = NULL)' (decimal(38,18) and null).; line 1 pos 0;
'Project [(v1#5 = null) AS (v1 = NULL)#7]
+- Project [value#2 AS v1#5]
   +- LocalRelation [value#2]
...

The query above passed in v2.4.5.
Why are the changes needed?

bugfix
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Added tests.

Test build #121404 has started for PR 28241 at commit 8b18deb.

Merged build finished. Test PASSed.

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

Test build #121404 has finished for PR 28241 at commit 8b18deb.

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

Merged build finished. Test PASSed.

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

cc: @cloud-fan @viirya

good catch! LGTM

merging to master/3.0

Thanks for the quick response, @cloud-fan !

Thanks always, @viirya


[Question]: Error in FileTransform@2

Task name
FileTranform
Task version
2
Environment type (Please select at least one enviroment where you face this issue)

[X] Self-Hosted
[ ] Microsoft Hosted
[X] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows Servr 2019
Question
I know that the question has been asked, but I can't find the answer. I am using the task to do substitution in appsettings.json file , so the task is defined as follows
- task: FileTransform@2
  displayName: 'Transform File'
  inputs:
    folderPath: 'some folder'
    jsonTargetFiles: */appsettings.json
So the substitution is happening , but I get the error
##[error]Unable to apply transformation for the given package - Changes are already present in the package.
I know that the error is due to xml transformation, which I am not doing. It is cosmetic, but I do get errors showing up on the pipeline summary page. Is there anyway to supress this error ?

Does anyone know how to solve this ?

@elvovsky according to the docs there's a default value for the xmlTransformationRules parameter. Presumably, therefore, the issue is that the default transformation is being executed and doesn't apply to your scenario. I haven't tried this, but could you try passing an empty string to the parameter to prevent it from executing the default transformations?

@antonysmith-mando I understand why I am seeing this. I don't understand why there is no parameter for suppressing the message or at least saying don't do xml transformation. I will certainly try your suggestion.

@dsosunov in your log output, it would appear that the enableXmlTransform option is not being evaluated. Both getBoolInput and getDelimitedInput call getInput, which writes a debug log of the setting's name and value: https://github.com/microsoft/azure-pipelines-task-lib/blob/master/node/task.ts#L272
We can see this happening for xmlTransformationRules, xmlTargetFiles and jsonTargetFiles, but not enableXmlTransform:
##[debug]xmlTransformationRules=-transform **\*.Release.config -xml **\*.config
##[debug]xmlTargetFiles=undefined
##[debug]jsonTargetFiles=**/appsettings.json

My earlier comment expected this to be the case, because the docs don't include this as an option. However, I see in the code you've linked to that this option should be evaluated, therefore we'd expect to see that debug message included in the output.
Looking at that code, it was changed last week in this commit: https://github.com/microsoft/azure-pipelines-tasks/commit/bcbc0c9f3367ce02cbb916695b0aae75cf41d4f2. As you can see, that change updated the implementation to include evaluation of the enableXmlTransform parameter instead of inferring its value based on whether xmlTransformationRules had a value.
The previous implementation would have aligned with my previous comment (i.e. to disable XML transformation, the xmlTransformationRules default value needed to be removed), but it looks like this new version should fix that by allowing the enableXmlTransform setting to be evaluated instead.
I've tried to run a FileTransform@2 task this morning and it shows me: Version      : 2.246.1
I would suspect that, once the new 247 version of this task is running on Azure Pipelines, your script will work. In the meantime, setting the xmlTransformationRules property to an empty string should do it.


Update docker and singularity files for new synax

Forcing merge as it's the same update as everywhere else. Tests only failing as we're still on the master branch.


vcpkg.txt support!

Can I write a vcpkg.txt to tell vcpkg what packages I need? just like requirements.
The VCPKG_TARGET_TRIPLET should not show in this file.
such I has a file:
# vcpkg.txt
spdlog
cpr
...

then vcpkg -r vcpkg.txt --triplet=x64-windows

as far as I remember vcpkg supports response files. So ./vcpkg.exe @somefile should work.

yes, thanks :)

as far as I remember vcpkg supports response files. So ./vcpkg.exe @somefile should work.

But what's the format of response file? Can you give a sample?

the response like:
cpr
gettext
spdlog
cxxopts
fmt

then the command like: vcpkg install @vcpkg.txt --triplet=x64-windows


Will support webrtc?

thanks :beer:

Unlikely to be implemented directly inside of react native core. The goal is for the plugin api to be good enough so that people from the community can build webrtc support

@qingfeng - if you're interested in building a WebRTC plugin that would be very welcome! ping me in irc if you want to know how to get started, I'm notbrent

Any update about this #222

@brentvatne I am now doing ~

@brentvatne @qingfeng
any news about it?

@qingfeng awesome! Is there on GH yet? (I understand it's very much WIP, that's alright.)

I have built a plugin to support WebRTC in React Native.
Please checkout https://github.com/oney/react-native-webrtc


chore(deps): update pre-commit dependencies

This PR contains the following updates:

Package
Type
Update
Change

alessandrojcm/commitlint-pre-commit-hook
repository
minor
v9.13.0 -> v9.16.0

astral-sh/ruff-pre-commit
repository
minor
v0.3.5 -> v0.4.2

pre-commit/pre-commit-hooks
repository
minor
v4.5.0 -> v4.6.0

Note: The pre-commit manager in Renovate is not supported by the pre-commit maintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.

Release Notes

alessandrojcm/commitlint-pre-commit-hook (alessandrojcm/commitlint-pre-commit-hook)
v9.16.0
Compare Source
Features

bump the commitlint group with 2 updates (75c8c9b)

v9.15.0
Compare Source
Features

bump the commitlint group with 2 updates (b27b4a4)

v9.14.0
Compare Source
Features

bump the commitlint group with 2 updates (8f4d925)
bump the commitlint group with 2 updates (a5e9a14)
bump the commitlint group with 2 updates (a884f9a)

astral-sh/ruff-pre-commit (astral-sh/ruff-pre-commit)
v0.4.2
Compare Source
See: https://github.com/astral-sh/ruff/releases/tag/v0.4.2
v0.4.1
Compare Source
See: https://github.com/astral-sh/ruff/releases/tag/v0.4.1
v0.4.0
Compare Source
See: https://github.com/astral-sh/ruff/releases/tag/v0.4.0
v0.3.7
Compare Source
See: https://github.com/astral-sh/ruff/releases/tag/v0.3.7
v0.3.6
Compare Source
See: https://github.com/astral-sh/ruff/releases/tag/v0.3.6

pre-commit/pre-commit-hooks (pre-commit/pre-commit-hooks)
v4.6.0: pre-commit-hooks v4.6.0
Compare Source
Features

requirements-txt-fixer: remove duplicate packages.

#1014 PR by @vhoulbreque-withings.
#960 issue @csibe17.

Migrating

fix-encoding-pragma: deprecated -- will be removed in 5.0.0.  use
pyupgrade or some other tool.

#1033 PR by @mxr.
#1032 issue by @mxr.

Configuration
📅 Schedule: Branch creation - "* * 1 * *" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.0.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Adds modulo support to Float

Should probably be Float#remainder, see #559

Oh blergg, Libm fmod + remainder functions don't match ruby's results at all. Closing until I have something that actually works


Are you planing to implement the libinput library here?

I think will be a nice idea to have it, if already is not implemented or you used a better form

We already have a project for libinput: https://github.com/Smithay/input.rs

Oooh cool, thanks


Pressing "Command + W" does not close the file in the left sidebar.

A very stange issue where when you press Cmd+W the file closes in the main window, but the tile name is still showen in the left sidebar.
Here is that I am running:
{
    "uuid": "6c5c1ba4-4f5c-40a7-a242-3bcfe1289c92",
    "snapshotTime":<PHONE_NUMBER>457,
    "os": "mac",
    "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Brackets/1.6.0 Chrome/39.0.2171.36 Safari/537.36",
    "osLanguage": "en",
    "bracketsLanguage": "en",
    "bracketsVersion": "1.6.0-16680",
    "ProjectDetails": {
        "prj-1147418143": {
            "numFiles": 2572,
            "cacheSize": 143431211
        },
        "prj98782": {
            "numFiles": 186,
            "cacheSize": 8599276
        }
    },
    "fileStats": {
        "openedFileExt": {
            "js": 39,
            "html": 19,
            "scss": 13
        },
        "workingSetFileExt": {
            "html": 6,
            "js": 13
        }
    },
    "searchDetails": {
        "searchNew": 2,
        "searchOnReturnKey": 2,
        "searchInstant": 3
    },
    "projectLoadTimes": ":137",
    "fileOpenTimes": ":452",
    "ModuleDepsResolved": 148401,
    "AppStartupTime": 149180,
    "prefNodeSearchDisabled": false,
    "prefInstantSearchDisabled": false,
    "installedExtensions": []
}

Fixed with https://github.com/adobe/brackets/pull/12145

Thank you!
I just noticed that the "X" button in the left sidebar has a similar issue. It does not close all untouched files...

#12145 should fix that too: if it doesn't, do open a new issue :+1:

Great!
Do you think that fix will be added to 1.6.1 or 1.7?

Cannot comment about that myself, but you can apply the fix by following the guidelines on How to hack on Brackets and then doing git fetch upstream swmitra/BugFixesFor1.6 && git merge fetch_head :+1:

A build refresh is scheduled by his week or next for 1.6 and after that the new installers posted will contain this patch.

Closing as fixed


Add argument to keep sound ?

Sorry if I am overstepping the bounds of the project, but I have found that the interpolated output has no sounds. It would be awesome if you could add an argument (like --sounds) to keep the sound on the generated output -- or at least when output is the same length as input.
EDIT: Temporary solution:
ffmpeg -i "$video_name" audio.mp3 -y
ffmpeg -i "video_4x.mp4" -i "audio.mp3" -map 0:0 -map 1:0 -c:v copy -c:a copy "video_4x_audio.mp4" -y

I intend to support it. I need to learn some ffmpeg and perform a lot of tests. It takes a few days.

@Tempetek  Hi,you can check out lossless cut on github.It can seperate or merge different tracks in a video without re-encoding in a super-fast way.

https://superuser.com/questions/277642/how-to-merge-audio-and-video-file-in-ffmpeg#277667
This article discusses multiple ways of combining an audio file and a video file into one.
I personally found ffmpeg -i video.mp4 -i audio.wav -c:v copy -c:a aac output.mp4 to execute at x58 playback speed, and ffmpeg -i video.mp4 -i audio.wav -c copy output.mkv to execute at x126 playback speed. both are acceptably fast, though it looks like we will get speed gains if we are willing to export to .mkv instead of .mp4
I just tested and LosslessCut does indeed provide a GUI tool for instantly ripping the sound from a video. I have not looked into using that via CLI yet.

@hzwer If this was fixed, there was no documentation created for telling users how to use it.

# import dependancies
if True:
    import moviepy.editor
    import os
    import shutil

# main program
if True:

    # declare constants
    if True:
        originalVideoFile = "./video.mp4"
        audiolessVideoFile = "./video_2X_48fps.mp4"
        tempAudioFileName = "./temp/audio.mp3"

    # split audio from original video file and store in "temp" directory
    if True:

        # extract audio from video
        if True:
            video = moviepy.editor.VideoFileClip(originalVideoFile)
            audio = video.audio

        # clear old "temp" directory if it exits
        if os.path.isdir("temp"):
            # remove temp directory
            shutil.rmtree("temp")

        # create new "temp" directory
        os.makedirs("temp")

        # write audio file to "temp" directory
        audio.write_audiofile(tempAudioFileName)

    # combine audio file and new video file
    os.system("ffmpeg -y -i " + audiolessVideoFile + " -i " + tempAudioFileName + " -c copy output.mkv")

    # remove temp directory
    shutil.rmtree("temp")

In case this hasn't already been fixed, here is an example script I made showing how to transfer audio from the original video to the new video. Assuming you have both file names.
I am happy to make a pull request containing this fix but I have yet to identify where this should go in inference_video.py
Notes:
Audio extraction in this script is not instant like in losslessCut but it works. Instant lossless audio stripping could be an optimization for the future.
Per issue #28 the video/audio synchronization in these videos might be off by a tiny amount but it's in sync enough to implement audio for now.


how to make view title show month and year

I have two views in my scene. one centered and the other lower_right
I want the title over them to be the month and year (like December 2019, and then January 2020
the current thing puts the module-header there, but no distinction on which is which (I would have thought it would have the view name attached so I could set the style of that header..
but haven't found how to make the text dynamic  (some algorithm to format the month/year)
screenshot

for class access in calext2_view.js
    if (this.config.title) {
      var header = document.createElement("header")
      header.classList.add("module-header")
      if (this.config.className) header.classList.add(this.config.className)  //< --- add this line after 130

for the header text content, i need it to change dynamically, so some function executed on each refresh returns the string to be used

month view has its own dynamic view title. ('monthFormat') but not as module title.
I'll consider callback function to change module title on runtime.
Thanks for suggestion. I'll add this feature on next week.

I've updated. Now title can have a callback function to return contextual title text.
title: (mObj) => { // arguments as `moment` object of first slot starting time.
  return mObj.format("[My Weekly:] Wo")
}


LinuxBridge allow arbitrarily named interfaces

Removed unnecessary filter which only allowed interfaces
named like BRIDGENAME-* (e.g. s1-eth1) to be added
to bridge (class OVSSwitch does not have a filter like that,
so LinuxBridge also should not have it). Thus, now e.g. real
interfaces like eth0 can be added to bridge.
In more detail: Like examples/hwintf.py demonstrates, it is possible to add e.g. real network interfaces like eth0 to an instance of OVSSwitch or OVSBridge, however that did not work with LinuxBridge. This PR fixes that.
Example script to reproduce the issue:
#!/usr/bin/python
import mininet.net
import mininet.log
import mininet.cli
import mininet.link
import mininet.nodelib

MYNIC='eth0'

mininet.log.setLogLevel('debug')
net = mininet.net.Mininet()
h1 = net.addHost('h1')
h2 = net.addHost('h2')
#s1 = net.addSwitch('s1', cls=mininet.node.OVSBridge)
s1 = net.addSwitch('s1', cls=mininet.nodelib.LinuxBridge)
net.addLink(h1, s1)
net.addLink(h2, s1)
mininet.link.Intf(MYNIC, node=s1)
net.start()
mininet.cli.CLI(net)
net.stop()

Or are there other usage scenarios where enforcing of interface names like s1-eth1 is important? I guess not, or else OVSSwitch would enforce this, too.

This is interesting - I think the purpose is to avoid avoiding adding lo (and any non-mininet interfaces) to the bridge if it's in the root namespace?


Add a CI check that everything compiles

Complements #250, but proposes a more likely path to landing in the short term.
This should catch the compilation failure of #314

I think that to fully test the WASM, we would also need to manage wasm-bindgen.
Is it valid to just do a cargo check --target wasm32-unknown-unknown?

Cargo check will ensure it can be compiled, at the least.
WASM-bindgen provides the #[wasm-bindgen-test] macro for testing on WASM
I'm not sure if it will try to run your current tests on WASM, that might be an issue and I see what you mean.
I still think a compile check would be helpful :)


istio-iptables.sh: Specify default filter table where table is omitted

By default, if -t  is not specified; then the default table is filter.
Explicitly specify this table in bash script; becomes easier for golang implementation
Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Hi @abhide. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

@abhide: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-dashboard_istio
d2927c25a4bce496d14fe5923e73334939ed8275
link
/test e2e-dashboard_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-dashboard_istio
d2927c25a4bce496d14fe5923e73334939ed8275
link
/test e2e-dashboard_istio

integ-mixer-k8s-tests_istio
d2927c25a4bce496d14fe5923e73334939ed8275
link
/test integ-mixer-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@duderino @mandarjog Can either of you take a look?

thanks @mandarjog


feat: Allow existing secret import

Example config
name: test-aws
provider<EMAIL_ADDRESS>region: ap-southeast-2
imports:
  secrets:
    test: <your_secrets_arn>

Codecov Report
Patch and project coverage have no change.

Comparison is base (75404c6) 53.66% compared to head (ec66e4c) 53.66%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #449   +/-   ##
========================================
  Coverage    53.66%   53.66%
========================================
  Files           25       25
  Lines         1692     1692
========================================
  Hits           908      908
  Misses         708      708
  Partials        76       76

Flag
Coverage Δ

unittests
53.66% <ø> (ø)

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

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


KAFKA-10287: Skip unknown offsets when computing sum of changelog offsets

In PR #8962 we introduced a sentinel UNKNOWN_OFFSET to mark unknown offsets in checkpoint files. The sentinel was set to -2 which is the same value used for the sentinel LATEST_OFFSET that is used in subscriptions to signal that state stores have been used by an active task. Unfortunately, we missed to skip UNKNOWN_OFFSET when we compute the sum of the changelog offsets.
If a task had only one state store and it did not restore anything before the next rebalance, the stream thread wrote -2 (i.e., UNKNOWN_OFFSET) into the subscription as sum of the changelog offsets. During assignment, the leader interpreted the -2 as if the stream run the task as active although it might have run it as standby. This misinterpretation of the sentinel value resulted in unexpected task assigments.
Committer Checklist (excluded from commit message)

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

Started 10x runs of the failing system test here: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/4074/

Call for review: @ableegoldman @mjsax @vvcephei @guozhangwang

Retest this please.

@cadonna Should the PR be against trunk ?

I started a run of Streams system tests:
https://jenkins.confluent.io/job/system-test-kafka-branch-builder/4077/

@mjsax I thought this fix is most urgently needed on 2.6 to unblock the release. I will open a new PR for trunk.

@ableegoldman I agree it should be a blocker.

@ableegoldman I agree that having the extra protection you propose makes sense. I will open a follow-up PR.

Test this please

Ok to test

Test this please

@vvcephei I don't think there should be any issue there, since the checkpointed  OFFSET_UNKNOWN is just ignored on read (or should be) and will never make it into the subscription info.
That said, it does make me a bit nervous and I wouldn't count on this always being true, so I'd rather choose a different sentinel to be safe.
Maybe we can put together a brief list of all sentinel values used in Streams (and the clients) to keep track and avoid issues like this going forward. I had to spend a long time digging around the client code to figure out whether an offset of -1 was ever possible in non-error cases (the answer seems to be "yes"). We'd have to actually keep it up to date of course, which might be...challenging

@vvcephei Thanks for checking! Given your finding, I will change UNKNOWN_OFFSET to -4L. Actually, we do not to change UNKNOWN_OFFSET at all, because we now never write it into the offset sums. I just thought it would be better to change it to not end up in a similar situation after a future refactoring. I will follow the same reasoning in this case.

Test this please

Test this please

Test this please

Test this please

Java 11 failed with
08:16:38 org.apache.kafka.streams.integration.EosBetaUpgradeIntegrationTest > shouldUpgradeFromEosAlphaToEosBeta[true] FAILED
08:16:38     java.lang.AssertionError: Did not receive all 20 records from topic multiPartitionOutputTopic within 60000 ms
08:16:38     Expected: is a value equal to or greater than <20>
08:16:38          but: <0> was less than <20>

Java 14 failed with

06:37:03 kafka.network.SocketServerTest > testIdleConnection FAILED
06:37:03     org.scalatest.exceptions.TestFailedException: Failed to close idle channel

Java 8 failed with
java.lang.AssertionError: Did not receive all 168 records from topic multiPartitionOutputTopic within 60000 ms
Expected: is a value equal to or greater than <168>
     but: <167> was less than <168>

kafka.network.SocketServerTest and org.apache.kafka.streams.integration.EosBetaUpgradeIntegrationTest works on my local.

Test this please

@chia7712 Only committers can trigger Jenkins builds.

Java 8 passed the tests in question are know to be flaky. Might be good enough? Leave it to @vvcephei to make a call and merge.

Only committers can trigger Jenkins builds.

It seems I can trigger the jenkins by comment “ Test this please”. Let me test it again.

Jenkins is running now :(
Maybe it does not exclude the committers from other Apache projects. At any rate, I will not trigger Jenkins in the future.

Ah yes. I work for all committers -- it's not project specific. Missed that you are HBase Committer/PMC :)

Java 8 was aborted due to a timeout.
04:56:02 Build timed out (after 270 minutes). Marking the build as aborted.

@chia7712 Please do trigger Jenkins in the future. The more we have that have permission to trigger Jenkins and do it, the better it is. Especially for people like me that do not have permissions to trigger it.

Please do trigger Jenkins in the future.

Copy that. Let me do it at once. Test this please

Java 11 failed with
org.apache.kafka.streams.integration.EosBetaUpgradeIntegrationTest > shouldUpgradeFromEosAlphaToEosBeta[false]
13:25:38     Expected: <[KeyValue(0, 0), KeyValue(0, 1), KeyValue(0, 3), KeyValue(0, 6), KeyValue(0, 10), KeyValue(0, 15), KeyValue(0, 21), KeyValue(0, 28), KeyValue(0, 36), KeyValue(0, 45), KeyValue(0, 55), KeyValue(0, 66), KeyValue(0, 78), KeyValue(0, 91), KeyValue(0, 105)]>
13:25:38          but: was <[KeyValue(0, 0), KeyValue(0, 0), KeyValue(0, 1), KeyValue(0, 3), KeyValue(0, 6), KeyValue(0, 10), KeyValue(0, 15), KeyValue(0, 21), KeyValue(0, 28), KeyValue(0, 36), KeyValue(0, 45), KeyValue(0, 55)]>

13:29:44 org.apache.kafka.streams.integration.EosBetaUpgradeIntegrationTest > shouldUpgradeFromEosAlphaToEosBeta[true] FAILED
13:29:44     java.lang.AssertionError: Did not receive all 168 records from topic multiPartitionOutputTopic within 60000 ms
13:29:44     Expected: is a value equal to or greater than <168>
13:29:44          but: <167> was less than <168>

13:47:10 org.apache.kafka.connect.mirror.MirrorConnectorsIntegrationTest > testReplication FAILED
13:47:10     java.lang.AssertionError: Connector MirrorCheckpointConnector tasks did not start in time on cluster: org.apache.kafka.connect.util.clusters.EmbeddedConnectCluster@7e44a25d
13:47:10         at org.apache.kafka.connect.util.clusters.EmbeddedConnectClusterAssertions.assertConnectorAndAtLeastNumTasksAreRunning(EmbeddedConnectClusterAssertions.java:296)
13:47:10         at org.apache.kafka.connect.mirror.MirrorConnectorsIntegrationTest.waitUntilMirrorMakerIsRunning(MirrorConnectorsIntegrationTest.java:191)
13:47:10         at org.apache.kafka.connect.mirror.MirrorConnectorsIntegrationTest.setup(MirrorConnectorsIntegrationTest.java:184)
13:47:10
13:47:10         Caused by:
13:47:10         java.lang.AssertionError: Condition not met within timeout 30000. The connector or at least 1 of tasks are not running.

Java 11 failed with
13:22:42 > Task :connect:mirror:integrationTest
13:22:42
13:22:42 org.apache.kafka.connect.mirror.MirrorConnectorsIntegrationTest > testReplication STARTED
13:24:09
13:24:09 org.apache.kafka.connect.mirror.MirrorConnectorsIntegrationTest > testReplication SKIPPED
13:24:09
13:24:09 > Task :connect:mirror:integrationTest FAILED

Test this please

@chia7712, looks like all tests passed.

looks like all tests passed.

yep. we need someone to merge it. @vvcephei @mjsax :)

@vvcephei, @mjsax: this is targeted to the 2.6 branch. Does this need to be forward merged to trunk, or is that the purpose of #9074?

Thanks all. Merged to 2.6.
@cadonna will follow up with a fresh fix for trunk.

Note, I've tracked the need for a trunk port with https://issues.apache.org/jira/browse/KAFKA-10319


Fix leaf function mutations for existing components

Description
This PR fixes leaf function mutations for existing components by creating attribute values when needed. Specifically, this commit focuses on mutations at the schema variant level found when regenerated assets with components in existence.
It contains an integration test used for testing leaf function additions intermingled with variant regenerations with existing components on the diagram. The test also looks at the raw attribute prototypes alongside the qualifications views themselves (update_variant_with_leaf_func).

Secondary Changes

Polish functions related to leaf upsertion (i.e. finding attribute
values, input calculation logic, component listing for schema
variants, tracing touchups and more)
Remove unused component-related leaf information for leaf upsertion
methods
Add integration test for new prototypes for func, which was originally
written for another bug, but is added in this commit as a regression
test (update_variant_with_new_prototypes_for_new_func)

bors merge


Commit time distance before

Used to compute a feature reflecting the distance from a commit and the vulnerability publication data,
through comparing timestamps. The score is equal to 0.0 if the commit is after the release date,
and between 0.5 and 1.0 if the commit was before the vulnerability release.
The closer the commit is to the release, the higher the value.

Ez is mehet SAP issue-ba


PA2 level5 flatMap compilation error

Summary
keep getting a compilation error in PA2 in level5. not sure why as my implementation of flatMap and my level5 are both very similar to the one gone through in the walkthrough. full error description is below.
Description
level5_JS.java:5: error: incompatible types: cannot infer type-variable(s) R
.flatMap(x -> {
^
(argument mismatch; bad return type in lambda expression
StateM<Integer,Integer> cannot be converted to StateM<R,FuncStat>)
where R,T,S are type-variables:
R extends Object declared in method flatMap(Function<T,StateM<R,S>>)
T extends Object declared in class StateM
S extends Object declared in class StateM
1 error
Grading terminated.
Idea s
Describe the approach used (if applicable)
Screenshots (if any):
Insert Images here if necessary

You are returning StateM<something, Integer> when it should be StateM<something, FuncStat>, you likely missed out something from the walkthrough.

ahhh i see thank you very much

You need to return StateM<Integer, FuncStat> ack(int m, int n) {
Not StateM<Integer, Integer> ack(int m, int n) {

thanks! much appreciated!

Summary
keep getting a compilation error in PA2 in level5. not sure why as my implementation of flatMap and my level5 are both very similar to the one gone through in the walkthrough. full error description is below.
Description
level5_JS.java:5: error: incompatible types: cannot infer type-variable(s) R .flatMap(x -> { ^ (argument mismatch; bad return type in lambda expression StateM<Integer,Integer> cannot be converted to StateM<R,FuncStat>) where R,T,S are type-variables: R extends Object declared in method flatMap(Function<T,StateM<R,S>>) T extends Object declared in class StateM S extends Object declared in class StateM 1 error Grading terminated.
Idea s
Describe the approach used (if applicable)
Screenshots (if any):
Insert Images here if necessary

thanks

You are returning StateM<something, Integer> when it should be StateM<something, FuncStat>, you likely missed out something from the walkthrough.

thanks


CI check against prod bundle

Prod fires prevention
It happened once and just happened twice. We build and thoroughly test our dev bundle only to find that our prod bundle is completely flawed and can potentially crash the entire site.
The best way to mitigate this is by extending our test suite to test with our production bundle as well as dev. My hunch is that we don't need to test the entire matrix like we do for dev but we should at least test one browser + collab, this should already give us some good confidence in that the prod bundle is behaving just as well as the dev one.

Closes #1631

As per @trueadm's offline suggestion, I'm reducing the workload while still retaining the runs that give us the most value


update the agitoon address again.

Source information
agitoon
Steps to reproduce
URL Redirection
Expected behavior
Please update me again.
https://agit665.xyz/
The address seems to be updated every two to three weeks.
Actual behavior
It doesn't download normally.
LNReader version
LNReader v2.0.0-beta.2
Android version
android 13
Other details
Thank you to the project developer.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 1.1.19.
[X] I have updated all installed extensions.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Are you on version 3.1.0 of the plugin?
Because it still works for me

It connects and downloads well.
There is an error.
If you click to start all downloads
"Expressed URL scheme 'http' or 'https' but no colon was found"

Can you send a video because I can't reproduce

https://streamable.com/65wuaf
Some novels have download errors.
Other novels are down.

it still works for me.
try clearing cookies in advance setting app

clear cached novels , clear cookies , library
After clearing it, I downloaded it again and it was the same error.

Just in case, I completely delete the app and reinstall it, so it works well.
thank you

I can confirm this as well, still not working.
For certain apps, would it be possible to manually change the domain?

Agitoon was banned iirc, so changing the url wouldn't change anything


Update about-the-graphql-api.md

Updating the doc specifically to update the URL to the API & Webhooks community that's currently displayed in the article under the Requesting Support header: https://docs.github.com/en/graphql/overview/about-the-graphql-api#requesting-support
When editing the doc I noticed that that particular section is auto-filled using a variable. I couldn't find the variable's source so I manually entered the text on my end and updated the links and description of the community.

Why:
Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[ ] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[ ] For content changes, I have completed the self-review checklist.

Hey @sophietheking, sure thing!

@sophietheking, heads up, edits were made here:

https://github.com/github/docs-internal/pull/45690
https://github.com/github/docs-internal/pull/45689

Thanks for this PR and the other two PRs you made for this change @ghostinhershell! We appreciate the contribution 📚 ❤
I merged the changes from https://github.com/github/docs-internal/pull/45689 into your other pull request https://github.com/github/docs-internal/pull/45690. This way, all the changes publish to the docs.github.com site at the same time, as one pull request.
For future reference, you can suggest changes to any number of files at the same time using a single pull request. For more info, check out our contribution docs and docs about pull requests.

dear brother can help me projuct building

Yes do you have a project??
On Tue, 17 Dec 2024, 8:50 am iamabdisalanahmed, @.***>
wrote:

dear brother can help me projuct building
—
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/29784#issuecomment-2547712835, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A7NQT4DYM7UTQWLQJZA6XY32F7JUTAVCNFSM6AAAAABTXZJXBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBXG4YTEOBTGU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Add support for password protected RAR archives

Is there a way to open rar with password?
If it is based on libunrar it should have option, but I can't figure out if it is possible.

I haven't tested it. I'll have to see if I can get it to work.

Fixed in 0e78f654a15ead8afe1583ba80bd28997d718fac


set youtube channel banner image

I am able to upload image to youtube channel arts.
this is the ruby script i am having https://gist.github.com/anbublacky/ff76b56642613bfe3066
i am unable to set the uploaded image as banner
https://developers.google.com/youtube/v3/docs/channels/update
They have given python example, where i don know what this function does
image_url = resumable_upload(insert_request)
they are assinging image url to
channel_brandingSettings["image"]["bannerExternalUrl"] = banner_url
and again don know how to convert this to ruby
channels_update_response = youtube.channels().update(
part='brandingSettings',
body=dict(
brandingSettings=channel_brandingSettings,
id = channels_response["items"][0]["id"]
)).execute()
How to set uploaded image as banner?
This  is not a bug/issue, please help me, i have also asked stackoverflow
http://stackoverflow.com/questions/31137906/set-youtube-v3-channel-banner-image-through-ruby
as there is not enough documentation for ruby i am asking here
updated:
This is what i'm trying to set banner
banner_url = JSON.parse(image_insert_response.body)["url"]
channel_list_res["items"][0]["brandingSettings"]["image"]["bannerExternalUrl"] = []
channel_brandingSettings = channel_list_res["items"][0]["brandingSettings"]
channel_brandingSettings["image"]["bannerExternalUrl"] = banner_url

channels_update_response = client.execute!(
:api_method => youtube.channels.update,
:parameters => {
:part => 'brandingSettings',
},
:body => {
'brandingSettings' => channel_brandingSettings,
'id' => channel_list_res['items'][0]['id']
})
shows this error  undefined method `bytesize' for #Hash:0x0000000438e178
the body part i'm sending is wrong don know how to send

Change :body to :body_object. It expects :body to be the raw body content (string or IO), not a hash and should rarely be used, if ever. Most cases you should be using :body_object.

Thanks @sqrrrl , you are my saviour, and it worked fine. I am able to set youtube channel banner now
This is the new file, https://gist.github.com/anbublacky/aedee0284f1bd2ea0a71. Hope it helps someone.

Hi,
I got into a problem, in local when i execute the script  https://gist.github.com/anbublacky/aedee0284f1bd2ea0a71, it will open up a browser and ask for authorization, i thought i would send the access token file which created during authorization would be enough  to set banner from vps, but when i run the it is trying to open up a browser and showing the error.
Launchy::CommandNotFoundError: Unable to find a browser command. If this is unexpected, Please rerun with environment variable LAUNCHY_DEBUG=true or the '-d' commandline option and file a bug at https://github.com/copiousfreetime/launchy/issues/new

Is there anyway i could use the access toke to post it, or how to run the script in vps terminal
As the script is going to be run in cron job.


[WIP] Refactoring on exploreReducer.js

Changed return statement to have es6 syntax insteas of Object.assign() function call
@betodealmeida @mistercrunch

Please fix the build failure and merge conflict.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #4836   +/-   ##
=======================================
  Coverage   76.91%   76.91%
=======================================
  Files          44       44
  Lines        8522     8522
=======================================
  Hits         6555     6555
  Misses       1967     1967

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 eac97ce...aaf43cd. Read the comment docs.

I was following the same pattern for the Object.assign which is merging state and controls together. I've refactored it using the spread operator notation.

a
{ foo: 'bar' }
b
{ hugh: 'miles' }
{...a, ...b}
{ foo: 'bar', hugh: 'miles' }

LGTM


Issue 4807 Fix movem PC instruction bug on 68000

The movem instruction's (d16, PC) addressing mode has an instruction word, a mask word, and then an extension word. The addressing mode uses the value of PC incremented to the extension word, in this case instr_start + 4. The sleigh code incorrectly uses instr_start + 2. The issue is present for both movem.w and movem.l variants. This PR fixes the PC offset to +4.
See 68000 reference manual page 2-13 for PC indirect addressing mode, and 4-128 for MOVEM documentation.
Partially addresses #4807.

Aaah, thanks for this @Phlosioneer  .  I was running in circles for a bit today before I figured out the problem, then came here to look for an issue ... bingo.
Glad to see you also list the reference to the page # in the docs, saved me some time there too.
Anything in particular holding this back ?


Correct animation speed on some of the effects

In trying to track down why some animation speeds are incorrect, I found several easy fixes, where the animation speed was doubled for some reason.  This fixes those ones.
(Still need to figure out how to make the 'fold' one more accurate (it needs to be scaled according to the number of slices, I think) and the various box effects -- Probably need to calculate something about how many total boxes there will be animated and thus how long they will take to animate, and then adjust the actual timings based on that and the desired total animation speed.)
This modification doesn't include the packed javascript file - I couldn't tell what tool you were using to pack your javascript.

@danwood can you expand on what it is you're trying to fix with this? I'm not able to see any speed changes between animations.