polyline problem codeforces

https://codeforces.com/contest/617/problem/D
basically the link of this is given above

make PR of this


Improve the PDFViewerApplication._contentLength handling in the viewer, related mostly to scripting

Ensure that PDFViewerApplication._contentLength is always updated with the correct length, as returned by PDFDocumentProxy.getDownloadInfo, and only let the PDFViewerApplication._initializeMetadata method overwrite if it's not already been set.
Finally, in PDFViewerApplication._initializeJavaScript, the fallback _contentLength handling is now moved to just after the fallback documentInfo handling, such that all the fallback code is in one place within the method.

/botio integrationtest

/botio integrationtest

Looks good!

Looks good!


Please add a 'release' here on github

It is all very well having the Microsoft Store handle all releases but that is no good for those that do not use the Microsoft store for what ever reason. I do not.
You should be able to add your installer to be a release on github. That would provide us open-sourcers with a much more preferable download location.
For your information, the second I saw your release was only available from the MS store I decided to look at other alternatives. In the end I find I would rather spend time opening an issue here than visit the Microsoft Store even if it means I will never test your tool.
My team and I use github desktop and similar tools on several operating systems ranging from ReactOS/XP to Win 11 (mostly win 7/10 &11)  and various flavours of Linux, I am looking for an alternative that caters for lots of o/s variations/flavours.

@yereverluvinunclebert, I agree. We can of course install the application from https://store.rg-adguard.net/, but that's not a particularly trustworthy source.
Additionally, for this to be published on winget's repository, there needs to be a vanity link for the latest release, with GitHub releases provides.

That's insightful. Thanks for sharing that. I have limited time spent on JitHub, and there's a massive re-architecturing going on. But I'll will keep your request in mind and produce a open source friendly release on GitHub when the time comes.


More program options

Hi,
I've exposed the frame_id used in the published ROS messages and the counts_per_force/counts_per_torque values as program options. If none are provided, the previously hard-coded values are used as defaults to ensure backwards compatibility.
Other users might find this useful.
Greetings,
Chris

Long time coming, but great idea and thank you for making these changes!


Replace apis_core.apis_entities.autocomplete3.GenericNetworkAutocomplete

this should be rewritten in a cleaner and more generic manner.

This was dropped in c471255fb8415dc2d910a4ea4b31ed79b2936136


The app get restared when I press confirm button afer I take a photo with the camera [🐛]

Description
I'm having an issue with react-native-image-picker library.
Taking a photo from gallery is working perfectly. My problem is with the camera. Once that I take a photo and press on the confirm button to get the asset information, the app get restared.
I don't have errors on console and also I have the permissions. The app just get restared with no reasons.
How to repeat issue and example

step to reproduce the issue

Open camera
Take a photo
Press confirm button

Additional Information

Image Picker version: "^4.7.3"
React Native version: "0.68.1"
Platform: Android
Development Operating System: MacOS

Getting this issue too - if a fix can be issued sooner rather than later that would be great!
(Considering the entire library is useless without this functionality)

Many bugs will pops up for using react-native: 0.68+
because RN architecture has changed so maintainers has to update their repos and fix the bugs if package contains bridges

Does it mean downgrading RN to 0.67 is a possible solution

i upgraded to React Native 0.68.x and im getting crash when upload from gallery

implement camera UI in scope of thi

I got similar issue, but happens only with camera and only on android with low RAM. Looks like when this library opens system camera, android decides to kill origin app as wants to utilize RAM. Earlier such issues happen with me even on native android. Solution for android can be to implement camera UI in scope of this library and run this UI in same android process to avoid RAM utilization.

Kindly give an example as to how this can be achieved

implement camera UI in scope of thi

I got similar issue, but happens only with camera and only on android with low RAM. Looks like when this library opens system camera, android decides to kill origin app as wants to utilize RAM. Earlier such issues happen with me even on native android. Solution for android can be to implement camera UI in scope of this library and run this UI in same android process to avoid RAM utilization.

Kindly give an example as to how this can be achieved

I decided to migrate camera functionality from this library to react-native-camera-kit .
This will require more effort to implement some UI on your side.
And that's not all. If you used custom image width/height your'll need this library for image resizing of just captured photos - react-native-image-resizer .

i hope this issue get fixed by the maintainers in the next release

It looks as it's not really a library problem. When you launch the camera, it launches as new Activity a from Android P (9) and on, it's allowed the OS to kill background activities. That's why it don't give an error message.
There is a website about it: https://dontkillmyapp.com/
Just posted two solutions here: https://stackoverflow.com/questions/68206801/expo-image-picker-crashes-app-after-using-launchcameraasync-on-android/74816435#74816435

I have same problem with smartphone from company Xiaomi. After restarting my smartphone, then the bug dissapeared.

I have the same issue with React Native 0.59, but it is very intermittent and I can't reproduce this issue.

I got similar issue, but happens only with camera and only on android with low RAM. Looks like when this library opens system camera, android decides to kill origin app as wants to utilize RAM. Earlier such issues happen with me even on native android. Solution for android can be to implement camera UI in scope of this library and run this UI in same android process to avoid RAM utilization.

I have the same issue with React Native 0.59, but it is very intermittent and I can't reproduce this issue. Sometimes it happens and sometimes nothing happened:)

I got similar issue, but happens only with camera and only on android with low RAM. Looks like when this library opens system camera, android decides to kill origin app as wants to utilize RAM. Earlier such issues happen with me even on native android. Solution for android can be to implement camera UI in scope of this library and run this UI in same android process to avoid RAM utilization.

The package expo-image-picker is similar to this one. It states on docs: https://docs.expo.dev/versions/latest/sdk/imagepicker/#imagepickergetpendingresultasync

Android system sometimes kills the MainActivity after the ImagePicker finishes. When this happens, we lost the data selected from the ImagePicker. However, you can retrieve the lost data by calling getPendingResultAsync. You can test this functionality by turning on Don't keep activities in the developer options.

To reproduce the crash. Do the following:

Open your app
Open the camera
Turn on 'Don't keep activities'.
Finish working with the camera.

Sometimes turning dont keep activities on before, don permit camera to open.

Be prepared to crash. Save all states and navigation stack on local-storage, launchCamera. The app will restart, you will restore all the screen/navigation/data/etc, and get photo using the ImagePicker.getPendingResultAsync.

Is there an equivalent of ImagePicker.getPendingResultAsync in this package?

Anyone facing this app kill issue, a workaround is the notifee foreground service. By using that, it will keep your app alive.
What you must do:

Disaply an ongoing notification with notifee
Register your foreground service with notifee
When returning or unmounting cancel the notification and stop the foreground service

Anyone facing this app kill issue, a workaround is the notifee foreground service. By using that, it will keep your app alive.
What you must do:
1. Disaply an ongoing notification with notifee

2. Register your foreground service with notifee

3. When returning or unmounting cancel the notification and stop the foreground service

Looks very promissing!!!! I'll test your solution next week!
The Expo says that is possible to simulate the crash situation using the Android Developer option don't keep activities as stated on (expo docs)[https://docs.expo.dev/versions/v47.0.0/sdk/imagepicker/#imagepickergetpendingresultasync]
How to test:

Open your camera. (The notifee will pop up also)
Open android developer options and turn on the don't keep activities option (or just do a toggle), this option forces the android to kill all background activities. It works exactly the same way as the distributors "garbage collector".
Take a picture and check if the other activity is killed or not.

Also, for some reason the activity kill is not happening anymore. I use most samsung devices new and old, and both of them had performance and security updated.
Before, when i did a stress test of opening and closing the camera several times. After ~1min it would crash the app at least once.
But this is not happening anymore.

Anyone facing this app kill issue, a workaround is the notifee foreground service. By using that, it will keep your app alive.
What you must do:

Display an ongoing notification with notifee
Register your foreground service with notifee
When returning or unmounting cancel the notification and stop the foreground service

Note: See also this issue where I'm asking to documented better the limitations and explained better the solution

I tried using the Notifee notification using   asForegroundService: true, ongoing: true,autoCancel: false as explained in the main issue you opened. Could you provide a Codesandbox exemple?

I'll see what I can do since it is proprietary code. If you browse the linked issue, it gives more details that might answer your question.

@Asiratlan See https://github.com/react-native-image-picker/react-native-image-picker/pull/2245


Update options.cmake to utilize CUDAToolkit_FOUND

Use CUDAToolkit_FOUND forged by FindCUDAToolkit (available in CMake 3.17+)
The use case is to automatically fallback to CPU build if CUDA toolkit is not found.

Thank you @skyline75489. We will consider this functionality. Right now, we will leave it as is, to simplify each of the scenarios.


Attempt at biginteger support

I was trying to serialize an elliptic curve prime as an Integer with this library, but I noticed whenever I provide this (as a string - the result of gmp_strval), use pure PHP math operators in the Integer class winds up casting the value as an integer, which is limited by PHP_INT_MAX. https://github.com/fgrosse/PHPASN1/blob/master/lib/ASN1/Universal/Integer.php#L62-71
Note that this problem of initializing with the wrong value doesn't happen when parsing structures from elsewhere, since using GMP allows for arbitrarily sized integers. https://github.com/fgrosse/PHPASN1/blob/master/lib/ASN1/Universal/Integer.php#L85-95
I have a sort of working attempt here and a test for it also. It's a shame that PHP doesn't support arbitrarily sized integers yet :/
Anyways, it would be nice to support writing these integers somehow!

Tests fail only because of StyleCI, which seems to complain about some of the phpdoc type hinting in numerous classes that I didn't actually change. For coherence I won't change these in this PR.

Thanks for the PR @afk11 I will probably look at this PR over the weekend.
From quickly glancing over your description I guess this will solve issue #1 right?

Hi @fgrosse - yes I believe this should fix it. That said, I would appreciate if you could try running 'afk11/asn1', a fork with this patch put through, in some of your applications to rigorously test? I am a bit unsure about the handling of large negative numbers. (see one of the tests).
All I did was mirror the operations using GMP equivalents, but I worry I might have overlooked something - AFAIK the standards use two's complement for integers, making 2^256 a negative number when encountered in binary.. So if you have any tests that might already capture this, it'd be cool to see how it does.

I have been busy the past while, but will follow up with something today tomorrow

Yeah I have been distracted with other thing myself so dont worry. If you need some help drop a  line.

I finished this up and addressed the nits from before. It has more tests for large negative/positive numbers, so think it's good to go.

Ping @fgrosse - made some progress with storing the gmp_init() right away in Integer. I tweaked Integer::fromBinary() to call new static(gmp_strval()) in order to create a proper instance.
The only issue is with <=PHP5.5 (IIRC), GMP encapsulates values with resources instead of objects. Unfortunately this means objects with resources cannot be directly compared.
It's actually worse than it sounds, because if Set contains an Integer, you can't compare the whole set with another.
The way around this is to:

don't save the result of gmp_init($arg), and make sure it's called every time $this->value is used throughout the code
Don't directly compare $object with $parsedObject.

I have an extreme distaste for not being able to compare objects directly - serialization logic shouldn't be necessary just for this, and the side effects for larger structures is not good. What do you think?

I agree that storing the gmp_init value is just not worth loosing comparability.
According to some benchmarks I ran later that day it doesnt even improve overall speed so we can savely leave it as it is now :)


send revisionid to notification service

Notification service is only sent the workitem id when it is updated.
This makes the information very limited to generate useful notification.
This commit makes it possible to send the revision id along with
workitem id.
To send the revision id it makes use of the custom attribute of the
notification service. This way notification service does not need to
make any changes to accept this new information.

Codecov Report

Merging #2176 into master will decrease coverage by <.01%.
The diff coverage is 76.47%.

@@            Coverage Diff            @@
##           master   #2176      +/-   ##
=========================================
- Coverage   69.61%   69.6%   -0.01%
=========================================
  Files         170     170
  Lines       15681   15692      +11
=========================================
+ Hits        10916   10923       +7
- Misses       3773    3776       +3
- Partials      992     993       +1

Impacted Files
Coverage Δ

remoteworkitem/scheduler.go
60.97% <0%> (ø)
:arrow_up:

controller/workitems.go
77.31% <100%> (ø)
:arrow_up:

workitem/workitem_revision_repository.go
93.33% <100%> (+0.22%)
:arrow_up:

remoteworkitem/trackeritem_repository.go
74% <100%> (ø)
:arrow_up:

controller/iteration.go
78.32% <100%> (ø)
:arrow_up:

notification/notification.go
18.98% <61.53%> (+6.13%)
:arrow_up:

controller/workitem.go
78.69% <75%> (-0.56%)
:arrow_down:

workitem/workitem_repository.go
69.9% <85.71%> (+0.27%)
:arrow_up:

Continue to review full report at Codecov.

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

@DhritiShikhar removed all the changes that were unnecessary! PTAL

@DhritiShikhar done :-)

@surajssd I'm really sorry. I've implemented the same functionality in https://github.com/fabric8-services/fabric8-wit/pull/2256 and was thinking to myself: "you were reviewing a PR the other day that was using the "custom" map to sent something to the notification service". When @alexeykazakov asked on the planner channel if we can make the notification service more informative, I hacked away without noticing that you actually had something in place already. I hope you're not mad at me because of this. I really forgot about your PR. As you might have seen, I've extended the endpoint for fetching events from fabric8-wit. You can now pass along a revision ID and then you only get back the changes for that revision. I started implementing something the notification service but had to stop. Shall we maybe work on this together and do a pair programming session maybe? Then no work is lost.

@kwk no don't worry I am not mad at anyone :-) , just wanted someone to take this forward after I left RH. Me and @DhritiShikhar has some discussion around this. I have no issues who takes it forward.


[Task] Add unit test cases for MessageProcessor

Task Description:
Currently, we run unit tests using jest which can be found here.
However, the test cases are not yet comprehensive enough and work can be done to cover more grounds. Specifically for this issue, we hope to add test cases for the MessageProcessor.
Deliverable(s):
New unit test cases that cover the testing of the MessageProcessor.
Additional Context:

The MessageProcessor can be found here
An example for AudioService can be found here which may serve as a good source for reference

I would like to work on this.

Go for it!


doc: samples/compression/lz4/README should indicate how to enable lz4 module

Describe the bug
The documentation for the LZ4 sample needs to be updated to indicate that LZ4 is an optional module, and should give guidance on how to activate it.
Environment

Page: samples/compression/lz4/README
Version: main
SHA-1: 588e0a69dc3c3d907b299878ae558876d0839b9b

https://github.com/zephyrproject-rtos/zephyr/pull/76184 address the document update


Push in Bg

Hi everyone !
I'm using ngrok to access to my server by ssh.
Here is the thing, the connection is limited. So I would like to use the push command in background, is it possible ?
Best Regards

@LordBli, I am not sure if I understand you correctly, but in Bash, you can append & to any command in order to run that command in background. List of backgrounded commands (called jobs) you can run jobs, where each command gets a number (starting from 1) using which you can access it. Note that is --no-prompt drive command option that is used to auto-accept all changes. For example: drive push --no-prompt &
When you want to put the job to the foreground, you can use fg command optionally followed by the number from jobs command output. When no number is used, the the shell's notion of the current job is used (usually the last job, the one with highest number).

Using & still output the backgrounded command output. If you don’t want to see the output, you can use &> /dev/null, i.e. redirect both stdout and stderr to /dev/null (which in this case behaves like a black hole) and the follows the &. Note that even you put such backgrounded command to foreground, no output will be output. For example: drive push --no-prompt &> /dev/null &

However, when your SSH connection disconnects, such jobs will be terminated, which I think you don’t want.
You have two options:

you can use a terminal multiplexer / screen manager like tmux or screen` (search their usage on the Internet);
disown the jobs.

The second option is quite easy: run disown optionally followed by the number from jobs. It essentially (not actually) transfers the ownership from the user you are currently logged in and it will make the job keep running (if the job won’t exit/terminate by other means) even when the user you are currently logged in, logs out (e.g. when the SSH session ends). Of course, it will be terminated when the computer/server is shut down. For example:
# On one line
drive push --no-prompt &> /dev/null & disown

# One separate lines
drive push --no-prompt &> /dev/null &
disown

Running processes (jobs/commands) you can still see using many utilities monitoring processes:

ps (e.g. ps aux | grep 'command name or whole command');
top or htop.

Most expected answer ! Thanks a lot.
Your answer is juste what I needed !


feat(evm-optimism): add OpBlockAccessListExecutor

Adds the optimism variant of the BlockAccessListExecutor

nice! is there test coverage for this?

There is not

@Rjected thanks for implementing this, can we merge this? I'll merge these changes into my branch to make debug_execution_witness work


refactor: remove cache's HashBuilder generic parameter

What's changed and what's your intention?
#300
While the addition of an optional generic hash parameter offers increased flexibility and convenience, it also introduces a effect that complicates the module's generic complexity. Furthermore, we do not have a significant number of hash parameters requiring substitution at this time. With these factors in mind, I've decided to eliminate the generic parameter.
Checklist

[x] I have written the necessary rustdoc comments
[x] I have added the necessary unit tests and integration tests
[x] I have passed make all (or make fast instead if the old tests are not modified) in my local environment.

Related issues or PRs (optional)

Hi @xiaguan , thanks for the effort. But I'm afraid I can't agree with this PR.

we do not have a significant number of hash parameters requiring substitution at this time

The customized hasher builder is provided for the following 2 cases at least:

Sometimes the key hash has already been calculated or the key is already a hash, so there is no need to calculate it again. And the user can pass a transparent hasher (for now, I'll implement one in foyer). e.g. the sst meta cache in RisingWave.
The default ahash hasher cannot balance the shards well.

it also introduces a effect that complicates the module's generic complexity

For the complexity part, IMO, it is okay to introduce additional complexity for foyer itself if it is needed and we can hide it well for other users that do not need it.
Specifically, though the generic type of the foyer in-momory cache is complex, a naive user can still use the enum cache type with 2 generic parameters only. (Cache<K, V>). For users that need a customized listener, only 3 generic parameter types are needed to eliminate dynamic dispatch, whose overhead can not be ignored sometimes (Cache<K, V, L>). And for users who have higher requirements on performance and need a customized hasher, 4 generic types are required.

BTW, I had a very short and casual discussion about the complexity of the internal types of a lib with @xuanwo at twitter(Chinese) . We can continue the discussion if you have your idea. 🥰
And thank you again for the effort. Wish we will make foyer a better lib.

I got it. I agree with it.
I will close the pull request.

Thanks for your help anyway. Let me see what I can do to make the development experience better.


Sharing option "Automatically display to all users" does not work

When I activate this option and then open the video with a different user in the annotation tool, the shared track is not shown.

Making public and sharing with admin does work as expected.

Should be fixed on staging.

Thx. Works fine now.


How should I specify the downloadUrl?

Issue Type

[x] Bug Report
[ ] Feature Request
[ ] Other

Current/Missing Behaviour
I'm a Chinese developer. I can't download from https://dl.nwjs.io because of the network environment.
It has been stuck at 8MB and does not support breakpoint reconnect.
Fortunately, Alibaba has a mirror site in China: https://npmmirror.com/mirrors/nwjs/ and https://npm.taobao.org/mirrors/nwjs/ .
Now I don't know how to configure this site address.
I tried to specify using the downloadUrl parameter, but it didn't work:
nwbuild({
  srcDir: "./temp/*",
  outDir: outDir,
  cacheDir: "./cache", // "./cache" | string
  mode: "build", // "run" | "build"
  version: version, // "latest" | "stable" | string
  flavor: "normal", // "normal" | "sdk"
  platform: platform, // "linux" | "osx" | "win"
  arch: arch, // "ia32" | "x64" | "arm64"
  downloadUrl: 'https://npmmirror.com/mirrors/nwjs',
})

And I also tried to modify the source code in nw-builder/src/get/download.js , but it still doesn't work:
28th line
  let url;
  let out;
  return new Promise((res, rej) => {
    if (downloadUrl === "https://dl.nwjs.io" || downloadUrl === "https://npmmirror.com/mirrors/nwjs") {
      url = `${downloadUrl}/v${version}/nwjs${
        flavor === "sdk" ? "-sdk" : ""
      }-v${version}-${platform}-${architecture}.${
        platform === "linux" ? "tar.gz" : "zip"
      }`;
      out = resolve(cacheDir, `nw.${platform === "linux" ? "tar.gz" : "zip"}`);
    }

Expected/Proposed Behaviour
Additional Info

Package version:
Operating System:
Node version:
NW.js version:
Repro link:
...

The npmmirror link errors out:
<Error>
NoSuchKey
<Message>The specified key does not exist.</Message>
<RequestId>63FF7C45B9DB8531312AFCA7</RequestId>
<HostId>npmmirror.oss-cn-shanghai.aliyuncs.com</HostId>
<Key>binaries/nwjs</Key>
<EC>0026-00000001</EC>
</Error>

Looks like the mirror download link format is slightly different and is not supported. This gives me a 404 error:
https://registry.npmmirror.com/mirrors/nwjs/v0.73.0/nwjs-sdk-v0.73.0-linux-x64.tar.gz

the link is :
https://npmmirror.com/mirrors/nwjs/v0.73.0/nwjs-sdk-v0.73.0-linux-x64.tar.gz

Ahh my bad, typing from my phone. I'm currently afk. What you tried out should work. What's the response/error you get?

I was able to reproduce the issue even after allow listing the mirrors.

This has been fixed in v4.1.0-beta.3


About the test data used in aigc cross model evaluation？

thank you for your excellent work. I'm very interested in your AIGC cross-model validation on github code. I want to know which part of these datasets (such as AGIQA-3k) serves as the test set. Is it the entire data set or a part of it (such as 20%). hope to your reply, thanks.

@zht8506 Hi, thanks for your interest ! In the cross-dataset setting, all the evaluation are perfomed on the entire datasets.

Thank you for your prompt reply. Have a nice day!

Thank you for your prompt reply. Have a nice day!


Documentation for the Airflow Operator

We should have a quick description of how to test the airflow operator, how to run a simple airflow instance and how to test the Armada Airflow Operator.

Hey team! Please add your planning poker estimate with ZenHub @dejanzele @jayofdoom @kannon92 @richscott

Chatting with Adam Pitt.  We will make this a bit simpler.  We will focus on a README.md on building the airflow operator and testing.
Airflow Integration will be a followup.  Airflow integration is a pain and it is changes based on how you set up your executors.


Added the Alex workflow

Signed-off-by: Venkatesh K<EMAIL_ADDRESS>

I have created new PR. Since, it is the patched one. I'm not able to update the file in this PR.
https://github.com/Seagate/cortx-k8s/pull/63


chore: use @sveltejs/eslint-config

This version has almost no formatting rules as prettier takes care of that now

I'm going to go ahead and merge this based off Rich's approval on Discord and since we merged https://github.com/sveltejs/svelte/pull/8608

Err I rescind my approval, this deleted some code that we need. Gonna revert, then we can try again


stack overflow

I am having a stack overflow and I don't know how to start hunting it.
The source code for the parser is located here: https://github.com/viperML/len/blob/fd93282fdb50d181af7652526b3b308475fefac1/src/ast.rs#L43
(The overflow can be triggered with cargo test or with the language repl with cargo run and typing anything, like a literal 1 )
This has started ocurring after adding a .delimited_by to repeatedly parse my lang's struct elements (foo: val , bar: val) (I haven't added yet the delimited by {}) https://github.com/viperML/len/blob/fd93282fdb50d181af7652526b3b308475fefac1/src/ast.rs#L71
The error might have some interaction with the pratt parsers at the end of the function, as returning early the atom won't trigger a SO.

The most likely candidate here is the use of atom inside the pratt parser at the bottom.
atom.clone().pratt((
    prefix(3, atom, |op: Ast, o: Ast| {
        Ast::FunctionCall(FunctionCall {
            function: Box::new(op),
            argument: Box::new(o),
        })
    }),
    ...
))

This looks for an atom directly before another atom, which I think it likely to result in infinite recursion. What happens if you comment out this operator?
Regardless, I think function calls are better expressed as postfix operators, with the args trailing afterward.

Ineed, it seems that prefix operator is the cause.
Just changing it to a postfix however, it seems that it enters an infinite loop. The parser doesn't crash immediately, but seems to loop without stop.

Infinite loop is better (and makes sense given how pratt parsers work)!
So I think the problem here is that the rule contains itself. Every time it tries to recurse into atom, it sees atom right there as a candidate pattern. It's effectively just a strange form of left recursion.
My advice would be to parse function application specifically using operator precedence (i.e: have a distinct rule like the following):
let atom = ... ;

let app = atom.foldl(app.repeated(), ...);

app.pratt((
    // All of the other ops here
))

Ofc you can switch the order if you want to reduce the precedence of function application too.

You are right, moving the function application to that different parser fixes the issue. Initially that was my implementation (for the infix operators too), but I moved too much into the pratt.
On a unrelated note, thank you and the contributors for this amazing lib :+1:


Image Upload issue

Only one image gets uploaded, that too only in the first conversation.
To enable uploading images in any no of different conversations

Now different images can be uploaded  in any conversations
Note that same image cant be uploaded twice as it is not required


[WIP][GWS] facility enhancement

Coverage decreased (-0.07%) to 82.875% when pulling 311381dd041b759c2e2c742817068555e8756eaa on sunny4381:features/gws-facility-enhancement into 01c31499824d3b331c9eefd91a0a9b26a539fb3b on shirasagi:dev/gws.

Coverage decreased (-0.1%) to 82.842% when pulling e43f4e8946b7e3d962a0111384a4a8d80b992fa8 on sunny4381:features/gws-facility-enhancement into 01c31499824d3b331c9eefd91a0a9b26a539fb3b on shirasagi:dev/gws.

Coverage decreased (-0.3%) to 82.674% when pulling 6eb34363029864c8a6343c72464f13fdd9c85285 on sunny4381:features/gws-facility-enhancement into 3e7190accea63b7671f8284b825ca228b0270891 on shirasagi:dev/gws.


Parse is the best what can (I / average developers/the ex parsers) do to help this thing grow?

Recently Bucky Henry from http://scaphold.io contacted me and asked me about how I'm managing since parse shut down. Below is my response:

Initially I was devastated. I only knew swift.
But after I...
Taught myself node; JavaScript
Installed mongodb on a old lap top, followed the parse server YouTube setup tutorial. Ran parse server off the same laptop, learnt about port forwarding, updated my cloud code + my iOS app (www.tipp3d.com). I've never looked back.
Because parse shut down it forced me to get uncomfortable and learn node and js which really improved my app because I've refactored so many of my client side requests into cloud code functions 👊🏻.
I love parse so much because... yea it lets you leverage an amazing node backend, without having to do boring stuff like messing around with mongoose and manually setting schemas. + push notification + user auth but mainly because it turned me into a better more confident developer. Just simply awesome. And it's even better now it's open source, less restrictions and I can run my server free at home until I get enough users and make money which only then it would make sense to get a droplet at digital ocean for only 5$ a month. Not bad.
Learning react js +  react native ATM...but I'm always gonna use parse server as my go to server side framework. There's simply nothing as good as parse - dashboard for mongodb out there. from my research node + mongodb is the way to go... Or am I wrong?
Also I'm building out Tipped cross platform. Parse has an android, js and rest api that makes it easy for my devs to get going faster. Like parse has all the tools to build simple social apps, and that's what Tipped is so yea love it.
My only worry is that someday soon people on GitHub might stop maintaining the parse SDKs, then I'm ****ed. But I guess that's the case with any framework one picks.

Anyways since I wrote that I got to thinking, man there must be something we could do to help make parse the obvious choice to newbie developers (me before the parse migration) who only know one client side language.
Ideas? I have some...
1: Your parse-server-example youtube tutorial was awesome. Perhaps the geniuses who built parse could take it one step further and setup a Udemy.com course that goes through a few simple but awesome apps one could make on each of the parse SDKs, android, ios, maybe even a few react - native apps all running off of parse-server. Surely the facebook react + react-native teams want more people coding in react. Quality Udemy courses is an amazing way to convert new devs onto your frameworks. This would be a good investment because people are lazy, and once you can build something that works one way why learn to do the same thing another way? I'm so lazy i'd rather figure out how to grow parse then learn something like firebase. so yea new devs = long term.
1.1: Then use the money from the Udemy courses to market parse. or just go on a vacation. you guys deserve one!

for me I just loved that I could take my old macbook pro that was collecting dust, and turn it into a parse powered web server hooked up to a locally running mongodb. It felt so good knowing I could run my app completely for free. Felt like I was hacking the system lol. Maybe do a Udemy course on that. This one would be unique. heck, I might just do this myself.

2: Convince Digital ocean/ Heroku, to do a promotional 6month free droplet for Parsers. Then a discounted rate until your droplet reaches a certain amount of traffic. Didn't Heroku have some sort of deal with Parse before it shut down?
3: Once theres all this Udemy content the parse social channels will have stuff to post about. Perhaps people watching this repo could retweet, share ect... and drive traffic to the Udemy courses.
Even if only a few read this and it ends at that. I just wanna say thanks for making parse. You guys helped me so much.

Thanks for the kind words! Now that the shut down is behind us, we will soon be working with the community to ensure contributors can continue developing Parse Server and the SDKs without us getting in the way. I don't think we will be working on new content or seeking out partnerships ourselves, but as we have seen in the past year, multiple companies have stepped forward to provide hosting solutions for Parse Server users.


Added href to local links, fixed rafinograde external links

Hello again!! It looks like I changed a lot but that was just my sublime text deleting trailing white space, whoops!!

I fixed a typo/error in lexicon.tome for Rafinograde where the iTunes/Github links were linking to nothing
I also added href attributes to local links to allow opening in a new tab/right-clicking to get URL/middle-clicking/etc! I tested in Firefox 61 and Chromium 66 and everything seems to work fine.

Could you fix the conflict, sorry I just pushed a tiny thing.

lexicon.tome is now lexicon.ndtl

ah whoops, i forgot to update my fork so i'm super behind yours. will commit the fixed versions later!!

Fixed!

Thanks for that : ) It'll make a lot of people happy!


[BUG] Non deterministic ROCKET transform with short series

Describe the bug
just redoing ROCKET tests and found that repeated runs of ROCKET with the same seed do not give the same results for all features. Strangely, they are always the same on one run of the code below, but they differ from one run to another!
I think this is to do with the fact I have series length 10, but the max length for kernels is 11 and nothing crashes, it just does weird C things. I'll look closer
To Reproduce
from aeon.transformations.panel.rocket import Rocket
uni_test_data =np.array([
    [[1,2,3,4,5,6,7,8,9,10]],
    [[10,9,8,7,6,5,4,3,2,1]],
    [[5,5,5,5,5,5,5,5,5,5]],
    [[1, 2, 1,2,1,2,1,2, 1,2]],
])
print(uni_test_data.shape)
r = Rocket(num_kernels=100,random_state=42)
r.fit(uni_test_data)
z = r.transform(X)
print(z[0][0])
print(z[1][5])
print(z[2][198])
r = Rocket(num_kernels=100,random_state=42)
r.fit(uni_test_data)
z = r.transform(X)
print(z[0][0])
print(z[1][5])
print(z[2][198])

Expected behavior
Same seed should produce exact same transform
Additional context

Versions

System:
    python: 3.9.9 (tags/v3.9.9:ccb0e6a, Nov 15 2021, 18:08:50) [MSC v.1929 64 bit (AMD64)]
executable: C:\Code\aeon\venv\Scripts\python.exe
   machine: Windows-10-10.0.22621-SP0
Python dependencies:
pip: 23.0.1
setuptools: 67.3.2
sklearn: 1.2.2
aeon: 0.16.0
statsmodels: None
numpy: 1.23.5
scipy: 1.10.1
pandas: 1.5.3
matplotlib: None
joblib: 1.2.0
numba: 0.56.4
pmdarima: None
tsfresh: None

my bad!


Responde to "help" message in dm

As per this guideline:
https://www.youtube.com/watch?v=ACY9HQeQUXE&list=PLWlXaxtQ7fUaCBINEYlxfW0jE5WIre5vA&index=2
When a user sends help as a direct message, the slack app should respond.
We could use that as a replacement of the /hello-github help command.

actually, simpler: just disable the messages tab.

I turned of direct messages


Make include more consistent

This came up while using the podspec file to be able to debug on iOS. It also matches the syntax from the two new m114 includes below it.

Does this fix an issue we had? Like enabling debugging of the classes? Or is it more a cosmetic change?

This fixes debugging on my side.

I agree we can make the dx more pleasant here. Probably with a new yarn command.
In the meantime here's the podspec file in case this help: https://gist.github.com/wcandillon/375b3df650322fb2148eadddb6afd03d

I agree we can make the dx more pleasant here. Probably with a new yarn command.
In the meantime here's the podspec file in case this help: https://gist.github.com/wcandillon/375b3df650322fb2148eadddb6afd03d

We also need to document the PRs better when doing low level stuff like this - Adding the error messages you're seeing when building with the updated podspec-file would be a nice addition to this PR - sorry for being picky - but documentation is everything when it comes to these low-level things :)


When sideloading incorrect (nonexistant) file, error hangs CLI rather than quitting immediately

(Strangely, seems to have quite itself after ~20 seconds; but perhaps that was just me pressing something)

Dup of #4


overlap with policy-switch.el

Are you aware of policy-switch.el: http://www.emacswiki.org/emacs/PolicySwitch ?
It seems quite similar to perspectives.el

No, that's very interesting. Thanks.

I've been doing some work to improve it: https://github.com/vapniks/policy-switch


create devtools package

Current dependencies on/for this PR:

main

PR #6   👈

PR #7

PR #8

This comment was auto-generated by Graphite.


ci.yml: test result summary is confusing

Steps to reproduce

build vim via .github/workflow/ci.yml
open job result, windows (HUGE, mingw, yes, yes, x86, stable, yes)
view step log, Test and show the result of testing Vim
on this step, some oldstyle tests are done.
but summary report Execute/Skip/Fail is 0.

  if exist dostmp\test23.in del dostmp\test23.in
  ..\vim -u dos.vim -U NONE --noplugin --not-a-term --gui-dialog-file guidialog "+set ff=dos|f dostmp\test23.in|wq" test23.in
  move test23.in test23.in.bak > nul
  copy dostmp\test23.in test23.in > nul
  copy test23.ok test.ok > nul
  ..\vim -u dos.vim -U NONE --noplugin --not-a-term --gui-dialog-file guidialog -s dotest.in test23.in
  ..\vim -u dos.vim -U NONE --noplugin --not-a-term --gui-dialog-file guidialog "+set ff=unix|f test.out|wq"  dostmp\test23.out
  if not exist dostmp\NUL md dostmp
  if exist dostmp\test24.in del dostmp\test24.in

Test results:

Skipped:

-------------------------------
Executed:     0 Tests
 Skipped:     0 Tests
  Failed:     0 Tests

ALL DONE

Expected behaviour
if summary is correct, no test is done. this step shoud be skipped.
if summary is wrong, fix to show testing result correctly.
Version of Vim
9.1.0252 and 9.0.0421
Environment
runs-on: windows-2022
(from steps Check version)
VIM - Vi IMproved 9.1 (2024 Jan 02, compiled Apr 17 2024 07:54:36)
MS-Windows 32-bit GUI/console version
Included patches: 1-252
Compiled by runneradmin@fv-az731-743
Huge version with GUI.
Logs and stack traces
No response

ah, you are talking about testing console vim.


Localized routing with optional lang param not working from Qwik v.1.2.8

Please refer to this issue: https://github.com/BuilderIO/qwik/issues/5049

I checked Qwik-Speak 0.15.3 with Qwik 1.2.10 and it now runs well on my machine.

@ThuKieuIC2 qwik-speak is not used to generate the localized router, but only Qwik City.
The fix was done in Qwik, but it hasn't been released yet. Maybe it works for you because you have a single page?

I have a multi-page website. It works for static MD/MDX generated HTML but it bugs for other tsx files.
I faced this from the day asking you about MD/MDX and confused to think due to your Speak.
Sorry!
Okay, just way the new Qwik City.

Maybe throw a redirect to the default locale when there isnt a locale specified in the pathname?

@samyung0 Speak is ready to redirect to the default locale. You can see the console log.
But the Qwik update affects some deployed-production.
We also cancel some other projects due to this Qwik way, back to Vite React is still the best.

It should be fixed in the latest Qwik release: v.1.2.11

it seems not work with SSG config, all pages routed to 404.

@robisim74 Yes. I config SSG for all pages from your tutorial. The build commnand (pnpm build) export all localed SSG files but when run it all shows 404 page.
I changed back to 1.2.6 version and it runs well again.

@ThuKieuIC2 Thanks for the invitation, I'll try to take a look at it later, but the behavior of routing and adapters like SSG don't depend on this library.

@ThuKieuIC2 In your app there is still too much confusion, with too many things started and not finished (even the use of this library). There are links that don't work at all (like terms and privacy, even with previous versions and in dev mode).
However, I believe that your problem arises from the 404.tsx file located in [...lang]: try removing it.
Sorry but I don't have time to go in depth into applications that are still in early development.


vimPlugins.jinja-vim: init at 2020-06-18

Description of changes
Add plugin jinja.vim.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 250267 run on x86_64-linux 1

3 packages built:

vimPlugins.dressing-nvim
vimPlugins.jinja-vim
vimPlugins.neogit


FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory

Hello!
On my TSX project after ~60 tests I always get this error under UNIX and Win7:
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
When I look at task manager, I see that node.exe takes about 1.9GB of ROM at this moment. I think that it happens because of large sourcemaps. The project is small (about 30 files). May be there is a way to preprocess and/or process files not all at one moment and keep everything in memory, but 5 or 10 files?
Here is my karma config
const webpack = require('webpack');
const autoprefixer = require('autoprefixer');

module.exports = (config) => {
config.set({
browsers: ['Chrome'],
singleRun: true,
concurrency: Infinity,
autoWatch: false,
frameworks: ['jasmine'],
plugins: [
'karma-sourcemap-loader',
'karma-webpack',
'karma-jasmine',
'karma-remap-istanbul',
'karma-coverage',
'karma-chrome-launcher',
'karma-spec-reporter'
],
files: [
  'node_modules/babel-polyfill/dist/polyfill.js',
  'src/**/*.spec.*'
],

preprocessors: {
  'src/**/*.spec.*': ['webpack', 'sourcemap'],
},

reporters: ['karma-remap-istanbul', 'spec'],

webpackMiddleware: {
  stats: 'errors-only',
  noInfo: true,
},

remapIstanbulReporter: {
  src: 'coverage/coverage-final.json',
  reports: {
    lcovonly: 'coverage/lcov.info',
    html: 'coverage/report',
    'text-summary': '',
  },
  fixWebpackSourcePaths: true,
},

autoWatchByDelay: 3000,

level: 'debug',

webpack: {
  devtool: 'source-map',
  module: {
    rules: [
      {
        test: /\.tsx$/,
        loader: 'awesome-typescript-loader',
      }, {
        test: /\.tsx$/,
        loader: 'istanbul-instrumenter-loader',
        enforce: 'post',
        options: {
          esModules: true,
        },
      },
      {
        test: /\.css$/,
        use: [
          { loader: 'style-loader' },
          { loader: 'css-loader' },
          {
            loader: 'postcss-loader',
            options: {
              plugins: () => [autoprefixer('ie >= 11')],
            },
          }
        ],
      },
      {
        test: /\.svg|ico|png|gif|jpg|scss|eot|ttf|woff|woff2($|\?)/,
        loader: 'null-loader',
      }
    ],
  },
  resolve: {
    extensions: ['.js', '.ts', '.tsx', '.css', '.scss', '.png'],
  },
  plugins: [
    new webpack.SourceMapDevToolPlugin({
      filename: null,
      test: /\.tsx($|\?)/i,
    })
  ],
  externals: {
    cheerio: 'window',
    'react/addons': true,
    'react/lib/ExecutionEnvironment': true,
    'react/lib/ReactContext': true,
  },
},

});
};

If someone has the same propblem check how do you pass files to karma.
If you use something like this src/**/*.spec.* you will have a problem like mine.
the correct way to call files is var testsContext = require.context(".", true, /_test$/); testsContext.keys().forEach(testsContext);
Taken from https://webpack.github.io/docs/usage-with-karma.html#alternative-usage


TSC Meeting 2022-12-15

Please respond to this issue with items you would like to see added to the agenda.
Items from attendees of TSC Meetings are prioritized above others, though ad-hoc reprioritization and discussion will occur.
Current agenda below:

ASWF

Confirm TAC representative delegate
Governance model is now in place!

Follow ups

Shells paths (Sam's PR)

New rez-pip PoC (https://github.com/JeanChristopheMorinPerso/rez-pip/tree/poc)

Duplicates #1410


legacy mode additional fixes

Allure Report
allure-report-publisher generated test report!

processReports: ✅ test report for 3ff90223

passed
failed
skipped
flaky
total
result

Total
32
0
4
0
36
✅


Upgrade snakeyaml to 1.32

Description of PR
Upgrade snakeyaml to 1.32 to mitigate CVE-2022-25857 and and CVE-2022-38752 for branch-3.3.
JIRA - HADOOP-18443

[X] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
10m 48s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+0 :ok:
shelldocs
0m  1s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-3.3 Compile Tests _

+0 :ok:
mvndep
14m 56s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
23m 55s

branch-3.3 passed

+1 :green_heart:
compile
18m 15s

branch-3.3 passed

+1 :green_heart:
mvnsite
20m 40s

branch-3.3 passed

+1 :green_heart:
javadoc
7m 13s

branch-3.3 passed

+1 :green_heart:
shadedclient
30m 18s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 35s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
22m  6s

the patch passed

+1 :green_heart:
compile
17m 40s

the patch passed

+1 :green_heart:
javac
17m 40s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
20m 18s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
javadoc
6m 57s

the patch passed

+1 :green_heart:
shadedclient
31m 20s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
746m 56s
/patch-unit-root.txt
root in the patch passed.

+1 :green_heart:
asflicense
2m 19s

The patch does not generate ASF License warnings.

962m 59s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.namenode.TestNameNodeMXBean

hadoop.hdfs.server.namenode.TestFileTruncate

hadoop.hdfs.server.namenode.ha.TestHAAppend

hadoop.yarn.client.api.impl.TestAMRMClient

hadoop.yarn.sls.appmaster.TestAMSimulator

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4873/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4873

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint shellcheck shelldocs

uname
Linux 27cc55b7a77e 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 /<PHONE_NUMBER>ec8533dafe7ad9cf83f28ddef5e85d

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~18.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4873/1/testReport/

Max. process+thread count
3276 (vs. ulimit of 5500)

modules
C: hadoop-project . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4873/1/console

versions
git=2.17.1 maven=3.6.0 shellcheck=0.4.6

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Failures look unrelated and passing in local.
hadoop.hdfs.server.namenode.TestNameNodeMXBean -> Verified and passing in local
hadoop.hdfs.server.namenode.TestFileTruncate ->  Verified and passing in local
hadoop.hdfs.server.namenode.ha.TestHAAppend -> Verified and passing in local
hadoop.yarn.client.api.impl.TestAMRMClient -> Verified and passing in local
hadoop.yarn.sls.appmaster.TestAMSimulator -> Verified and passing in local

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 50s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+0 :ok:
shelldocs
0m  1s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-3.3 Compile Tests _

+0 :ok:
mvndep
15m 28s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
24m 13s

branch-3.3 passed

+1 :green_heart:
compile
18m  5s

branch-3.3 passed

+1 :green_heart:
mvnsite
20m 36s

branch-3.3 passed

+1 :green_heart:
javadoc
7m 14s

branch-3.3 passed

+1 :green_heart:
shadedclient
30m 30s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 34s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
21m 57s

the patch passed

+1 :green_heart:
compile
17m 37s

the patch passed

+1 :green_heart:
javac
17m 37s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
20m 15s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
javadoc
6m 58s

the patch passed

+1 :green_heart:
shadedclient
31m 16s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
744m 57s
/patch-unit-root.txt
root in the patch passed.

+1 :green_heart:
asflicense
2m 10s

The patch does not generate ASF License warnings.

951m 38s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestDecommissionWithStriped

hadoop.hdfs.TestReconstructStripedFile

hadoop.hdfs.TestViewDistributedFileSystem

hadoop.yarn.server.timelineservice.security.TestTimelineAuthFilterForV2

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4873/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4873

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint shellcheck shelldocs

uname
Linux c157e0358827 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 044fd6f4c63b76b203a472f59d51009ca8bd55dc

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~18.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4873/2/testReport/

Max. process+thread count
3066 (vs. ulimit of 5500)

modules
C: hadoop-project . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4873/2/console

versions
git=2.17.1 maven=3.6.0 shellcheck=0.4.6

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

UT Failures in 2nd last build are unrelated to this change.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
6m 58s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-3.3 Compile Tests _

+0 :ok:
mvndep
15m 31s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
26m 14s

branch-3.3 passed

+1 :green_heart:
compile
19m 53s

branch-3.3 passed

+1 :green_heart:
mvnsite
22m 30s

branch-3.3 passed

+1 :green_heart:
javadoc
7m 43s

branch-3.3 passed

+1 :green_heart:
shadedclient
31m 45s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 37s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
24m 27s

the patch passed

+1 :green_heart:
compile
19m 21s

the patch passed

+1 :green_heart:
javac
19m 21s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
22m 20s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
javadoc
7m 29s

the patch passed

+1 :green_heart:
shadedclient
32m 39s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
709m 21s
/patch-unit-root.txt
root in the patch passed.

+1 :green_heart:
asflicense
2m 23s

The patch does not generate ASF License warnings.

936m 47s

Reason
Tests

Failed junit tests
hadoop.fs.contract.router.web.TestRouterWebHDFSContractCreate

hadoop.hdfs.server.datanode.TestDataNodeRollingUpgrade

hadoop.hdfs.server.datanode.TestDataNodeErasureCodingMetrics

hadoop.yarn.sls.appmaster.TestAMSimulator

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4873/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4873

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint shellcheck shelldocs

uname
Linux 75edc11803a1 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 5d89d8853a7f44b81362aca7927fb923c77c28fa

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~18.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4873/4/testReport/

Max. process+thread count
3156 (vs. ulimit of 5500)

modules
C: hadoop-project . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4873/4/console

versions
git=2.17.1 maven=3.6.0 shellcheck=0.4.6

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
10m 23s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+0 :ok:
shelldocs
0m  1s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-3.3 Compile Tests _

+0 :ok:
mvndep
14m 52s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
27m 20s

branch-3.3 passed

+1 :green_heart:
compile
18m 59s

branch-3.3 passed

+1 :green_heart:
mvnsite
21m 26s

branch-3.3 passed

+1 :green_heart:
javadoc
7m  9s

branch-3.3 passed

+1 :green_heart:
shadedclient
32m  0s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
24m 59s

the patch passed

+1 :green_heart:
compile
18m 26s

the patch passed

+1 :green_heart:
javac
18m 26s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
20m 54s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
javadoc
7m  4s

the patch passed

+1 :green_heart:
shadedclient
32m 50s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
727m 29s
/patch-unit-root.txt
root in the patch passed.

+1 :green_heart:
asflicense
2m 11s

The patch does not generate ASF License warnings.

955m  4s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.blockmanagement.TestBlockTokenWithDFSStriped

hadoop.hdfs.TestRollingUpgrade

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4873/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4873

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint shellcheck shelldocs

uname
Linux bf0c86e8f29c 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 5d89d8853a7f44b81362aca7927fb923c77c28fa

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~18.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4873/3/testReport/

Max. process+thread count
2304 (vs. ulimit of 5500)

modules
C: hadoop-project . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4873/3/console

versions
git=2.17.1 maven=3.6.0 shellcheck=0.4.6

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 54s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+0 :ok:
shelldocs
0m  1s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-3.3 Compile Tests _

+0 :ok:
mvndep
14m 39s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
27m 19s

branch-3.3 passed

+1 :green_heart:
compile
19m  9s

branch-3.3 passed

+1 :green_heart:
mvnsite
21m 32s

branch-3.3 passed

+1 :green_heart:
javadoc
7m  6s

branch-3.3 passed

+1 :green_heart:
shadedclient
32m  9s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
25m 21s

the patch passed

+1 :green_heart:
compile
18m 26s

the patch passed

+1 :green_heart:
javac
18m 26s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
21m 15s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
javadoc
7m  1s

the patch passed

+1 :green_heart:
shadedclient
32m 54s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
729m  2s
/patch-unit-root.txt
root in the patch passed.

+1 :green_heart:
asflicense
2m 35s

The patch does not generate ASF License warnings.

948m 29s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.balancer.TestBalancerRPCDelay

hadoop.hdfs.TestRollingUpgrade

hadoop.hdfs.server.balancer.TestBalancer

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4873/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4873

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint shellcheck shelldocs

uname
Linux ebdc7925b0b1 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 339f10ab764955b750aaf6447d0503af9942e2c1

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~18.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4873/5/testReport/

Max. process+thread count
2435 (vs. ulimit of 5500)

modules
C: hadoop-project . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4873/5/console

versions
git=2.17.1 maven=3.6.0 shellcheck=0.4.6

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

UT failures are related.

UT failures are related.

Probably you meant they are not related. I ran the tests locally and they passed.

UT failures are related.

Probably you meant they are not related. I ran the tests locally and they passed.

Thanks @aajisaka for correcting. I meant they are not related. (Edited my previous comment as well)


respect build instructions like // +build go1.9

Please dont run into crashes while disrespect // +build go1.9 comments...
Cant check now my own code, because of use 1.8.3 but the tools check also go1.9 code...

go1.9 is not a stable version,so I did not test whether it was supported.

go1.9beta2 is not a stable version and I did not test whether it was supported. You can post your error and I will test it!

github.com/go-siris/siris

I test it and the error message is not goreporter does not skip the vendor directory,but required in
these packages in the unit test , so you must ensure that the project is runable.

I have tested siris. The error message is not goreporter does not skip the vendor directory,but siris required these packages in the unit test , so you must ensure that the project is runable.

yeah, i have add now all the sources but its fails with the abdove error.


fixup changelog

this should hopefully help with #662 a bit, since there are multiple sections meaning less change for conflicts

bors r+


Anmacdonald/calloutupdates

Samples have been updated to use the Callout class as given by the Esri.ArcGISRuntime.Toolkit.Controls module. Beforehand these modules relied on ad-hoc Quick widgets overlaid upon the map to perform the same behaviour.
The samples are as follows:

Edit Data / Delete Features
Edit Data / Edit Feature Attachments
Edit Data / Update Attributes
Search / Find Address

This has been done for both the C++ and QML version of the samples, so a total of 8 samples have been updated in this branch.
Small stylistic differences have arisen:

Font bolding / font size / text positioning is now locked into the Callout's limited scope. Some style tags have been used to make the samples look like their older counterparts.
All callouts now have a tail which points to the position on the map in question.
Red/Blue buttons are now grey buttons.
Previous "delete" button has now become a trash-can.

Minor behavioural differences have arisen:

For all "Edit Data" samples, the callout's location is no longer tied to where the mouse was clicked, but are now tied to the centroid of the fixed feature.
The "Find Address" sample now resizes the callout based upon available window size and auto-changes its leader position.

assigning @ldanzinger to take a look as well


Common part on different pages in single file

@shivshankar9 This is the change regarding issue #55, please review about changes

@shivshankar9 This is the change regarding issue #55, please review about changes

@shivshankar9 Here, I used fetch API and put the common part in a file nav.txt and fetch the content in all the pages. After fetching the content, applying the js, that make the navbar responsive.

@shivshankar9 Check this link: https://abaran803.github.io/Student-portal/


Optimized riscv simulation performance

This PR is in progress and is ready for merging, aiming at improving the page table walk and TLB's performance. There will be more commits in the near future after https://github.com/gem5/gem5/pull/1387/ is merged.
The first commit https://github.com/gem5/gem5/pull/1519/commits/e1fd222aca8b6b0f0cb370701ec45ebf8ee7c9bc is aimed at solving the TODO below, when the RISC-V version is done, it could also be ported to other ISA(x86, etc).
https://github.com/gem5/gem5/blob/b1a44b89c7bae73fae2dc547bc1f871452075b85/src/arch/riscv/pagetable_walker.cc#L76-L78

Thanks for the contribution, @Kingfish404 !
Could you give some more detail in the commit message about the purpose and the design of this commit? It is difficult to review code without the context of why the code was modified and how the code was modified.
Also, "feat" is not an official tag. "arch-riscv" would be better for this change. See https://github.com/gem5/gem5/blob/stable/MAINTAINERS.yaml for a list of tags.

Hi @Kingfish404,
None of the commits in this pull request contains a Change-ID, which we require for any changes made to gem5.   Thank you.

@saul44203 can probably take a look at this.
I though we were already coalescing request.

I think this looks good. The only thing is that we merged #672 a while ago with a similar idea, in this case squashing pending walks that already hit in the TLB before starting them. Maybe with this patch that's no longer necessary.

Hi @Kingfish404, could you please address Jason's comments/questions? Thanks!


Improve Contributing, Coding, and Pull Request Guidelines

Overview
As our contributors get more diverse, having clear expectations for contributions (code, tests, documentation, pull requests) will help ensure we maintain quality and reliability of MRTK.
This change expands our coding guidelines to discuss coding philosophy/approach. It also clarify expectations for pull requests, and experimental features. Finally, the contributing page has been updated to include latest contact info and process.
I have also removed all references to the Feature_Contribution_Process.md page, which contains guidance for contributing large features to MRTK before the 2.0 release. The guidance there is no longer accurate, however keeping the page there so we can reference it as we revise guidance for large features.
Changes

Fixes: #6156

Verification
docfx generation passes

This optional section is a place where you can detail the specific type of verification
you want from reviewers. For example, if you want reviewers to checkout the PR locally
and validate the functionality of specific scenarios, provide instructions
on the specific scenarios and what you want verified.
If there are specific areas of concern or question feel free to highlight them here so
that reviewers can watch out for those issues.
As a reviewer, it is possible to check out this change locally by using the following
commands (substituting {PR_ID} with the ID of this pull request):
git fetch origin pull/{PR_ID}/head:name_of_local_branch
git checkout name_of_local_branch

/azp run

Suggestion from troy, mention the following two extensions for documentation editing:
Docs Markdown Extension for Visual Studio Code - Use Alt+M to bring up a menu of docs authoring options like:
Docs Markdown Extension for Visual Studio Code - Use Alt+M to bring up a menu of docs authoring options like
Code Spell Checker - misspelled words will be underlined; right-click on a misspelled word to change it or save it to the dictionary.

/azp run mrtk_docs


Verify pgp signatures on the downloaded deb file

Just as a bit of defense in depth so we verify the downloaded installer.
cc: @Johannestegner

It might be a good idea to build and publish a base file which already have the keybase files installed. Importing pgp keys sometimes take a while and if the servers don't respond (which they sometimes do not...) the build will fail.
It could also be a possibility to export the keychain and import it during build time.

I created a keybase and a keybase-sshca docker image which you can take a peak at and copy whatever from if you wish, all MIT :P
https://github.com/jitesoft/docker-keybase/blob/master/Dockerfile
https://github.com/jitesoft/docker-keybase-sshca/blob/master/Dockerfile


Add VSCODE_SHELL_INTEGRATION variable

A special variable that signifies that VSCode is attempting to enable shell integration. For example, VSCODE_SHELL_INTEGRATION=1. It has to be set at the very beginning so that user rc files can see it.

Originally posted by @romkatv in https://github.com/microsoft/vscode/issues/142004#issuecomment-1073263418

We want to warn via the log service if possible or not at all otherwise, not the shell as per https://github.com/microsoft/vscode/pull/145610#issuecomment-1076229419

To verify on mac or linux:

Enable shell integration
Open a bash terminal, ensure the shell integration message appears
Add unset VSCODE_SHELL_INTEGRATION to your ~/.bashrc
Open a bash terminal, ensure the shell integration message does not appear
Repeat 2-4 but with zsh and ~/.zshrc

Fixed in https://github.com/microsoft/vscode/pull/145884

Bash doesn't execute .bashrc for login shells, which is the default bash profile on MacOS. Verified after changing the profile to not be a login shell, also verified with default profile but in .bash_profile instead of .bashrc. One note, bash displays a message when integration is disabled zsh does not:

@JacksonKearl good observation, created a bug for April: https://github.com/microsoft/vscode/issues/146057


Custom proprietary license support

Library has following license metadata:
License: X Proprietary
Classifier: License :: Other/Proprietary License

And liccheck.ini file has following authorized license in it:
[Licenses]
authorized_licenses:
        x proprietary

But liccheck fails, because it needs Other/Proprietary License (as classifier license) to be in liccheck.ini file
However, this doesn't reproduce on versions below 0.5.2
I suppose changing:
https://github.com/dhatim/python-license-check/blob/668ea7b4aa471023a28fe2b1c5fac5c83a77f901/liccheck/command_line.py#L119
to:
https://github.com/dhatim/python-license-check/blob/3cbce20de685c944c8c2e6e7387be18f8cb5d5f2/liccheck/command_line.py#L119
caused it.
Maybe liccheck should handle proprietary licenses differently to avoid allowing all Other/Proprietary License instead of custom proprietary licenses?

Is it still problem?


Add and validate new translations for fr_FR

Also ran lupdate to translate the fresh strings

Ping @jeromelebleu if you want to review

Let's merge this by now. Thanks :+1:

Ping @jeromelebleu if you want to review

Thanks for the ping. I didn't have time yet to have a look, sorry about that, merging it was a good choice so!


Keepkey Support

no Idea how far this will/can go when there seem to be plans to ax nano and switch to banano, but if nano stays, it would be awesome to add Keepkey support as the Keepkey firmware allegedly can do Nano, but I have not seen yet any vault with support for both Keepkey and nano

Do you have the link to a library (or API) we can integrate with that supports Nano?

would seem like it. no idea how or even whether a lib needs to support nano specifically tho.

There isn't much documentation here so hard to know for sure, but it looks like it isn't supported yet
https://github.com/shapeshift/hdwallet/blob/master/packages/hdwallet-core/src/wallet.ts
Only Bitcoin, Ethereum, Cosmos, Binance, Ripple & EOS

okay, well I opened an issue over there, maybe it helps.


test_pr

Summary
test pr
Description
test pr
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

/canary-publish

/canary-remove

/canary-remove

/canary-publish

/canary-remove

/canary-remove

/canary-publish


feat: add methods to update and delete new entities

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[WIP] [#604] Normalize organisations names

https://github.com/opentrials/opentrials/issues/604

So, played a bit with the failing build issue, here are some observations:

Invoked without cache (pip install --no-cache-dir -r requirements.txt) it fails around fastcluster due to not finding numpy.
Calling pip install -r requirements.txt uses the pip cache, so once the issue was fixed (see below) locally it won't reproduce anymore.
Prior numpy installation with pip seems to fix it (just numpy, for now).
Installing line by line fixes it. Two ways to do it:

iterate over package names in requirements.txt:
$ for line in `grep -o '^[^#]\{1,\}' requirements.txt`; do pip install $line; done

iterate over requirements.in then do the remaining requirements.txt normally:
$ while read p; do pip install --no-cache-dir $p; done < requirements.in
$ pip install --no-cache-dir -r requirements.txt

There must be a pip gotcha I'm missing, though. Whoever finds the elegant fix for this (or the root cause, for that matter), please let me know :wink:

Just for the record, this discussion summarizes the issue we are facing here. Apparently the most elegant solution comes from the libs (fastcluster and pyhacrf) which shouldn't use numpy as requirement on their setup.py
@nightsh both workarounds you've suggested work, and if we choose to go for any of them, I would also suggest to avoid the tox deps and add the custom command on the commands target, right before the tests itselves

All code issues were resolved. We're still looking into how to train the clustering algorithm to avoid incorrect clusters


I'v' made an updated version with new functionalities

Hi peeps,
Based on this project I've made my own repository
with added functionalities (and modernisations to be compliant with modern browers, mainly Chrome).
Added options;
Record the audio from your live performance.
Choose a sound file instead of the microphone to add effects to.
The project: https://github.com/jonathanneels/Audio-Input-Effects
Test it here: https://liveaudioeffects.herokuapp.com/
Enjoy!

Thank you so much!


CI: Combine test, example, and cli jobs for better caching

By running a single job, we only need to store one cache per OS. Since the jobs share large parts of the dependencies, the total cache size of our workflow becomes smaller. This makes cache eviction less likely (GitHub only keeps the newest 10GB of caches).

Closing this for now. Our current CI setup seems to stay just under the 10 GB mark, so it should be fine for now. Also, combining the jobs seems to exhaust the available disk space on the Windows runner...


How to work wifi

Hello.
I installed McCatalina on my Lenovo E560 laptop.Of course with your tips.
Is it possible to use WiFi ?!  Because it does not seem to work.  And the second question is how to install Mac Big Sur on my laptop and it works like the current Mac ?! 🌹🙏🏻

Hello.
I installed McCatalina on my Lenovo E560 laptop.Of course with your tips.
Is it possible to use WiFi ?! Because it does not seem to work. And the second question is how to install Mac Big Sur on my laptop and it works like the current Mac ?! 🌹🙏🏻

This is my last EFI with working native Intel WiFi and Big Sur Beta
https://mega.nz/file/2kFgQJob#LQmxb7tndnybHWV2ojkNrK3pjM61PxU88HMNXJ5-7ro


100 using spnego similarly like in enceladus to negotiate the auth

Added Kerberos Auth that can be used:
curl -i --negotiate -u : "http://localhost:9090/token/generate"
The Current implementation is kind of working but testing has been difficult to implement. Currently getting a Bad Credentials Exception. Not sure if it's the Ldap search, the Keytab or the kerberos ticket that is currently causing the issue.
closes #100

Excuse the messy code if anyone tries to read this, just trying to find a configuration that works. A lot of code is duplicated or in the wrong folders, this will be cleaned up once we get a working solution.
So Far have tried multiple implementations such as those found in Enceladus as well as the official SPNEGO Documentation and Examples
The current implementation is being called correctly in the security filterchain if "curl -i --negotiate -u : "http://localhost:9090/token/generate" is being called. The Security filterchain is also successfully skipping this auth process if Basic Auth is stipulated in the http message and then BasicAuth is used.
The Current issue that's happening is currently getting a BadCredentials exception when trying to test it using MIT Kerberos on Windows. The Specific Error: `2024-06-12 12:52:52.666  WARN 17980 --- [nio-9090-exec-1] w.a.SpnegoAuthenticationProcessingFilter : Negotiate Header was invalid: Negotiate XXXX
org.springframework.security.authentication.BadCredentialsException: GSSContext name of the context initiator is null`
Current Hypothesis on the issue:

Something missing from the code. I've been using the above examples to write this code but it's possible that I've misinterpreted something or missed something. Another set of eyes may be able to point this out but currently I'm trying to experiment but not getting any changes.
Error with Keytab. Keytab was created by Active Directory team but it's possible that a mistake was made or encryption type is incorrect etc.
KRB5 is incorrect. So far I've tried 2 different KRB5 files and both have given the same output, so not sure if I have the correct data here.
Testing on windows: Kerberos and keytabs are mostly used on Linux distributions. Attempting to try and use Curl and MIT Kerberos to test this but it's possible that something on Windows is causing issues as kerberos is quite rigid.
Perhaps a SSL error with verifiying against the Absa KDC specified in the KRB5 files?
Possibly a cross-domain issue as the test machine is D_ABSA but the Kerberos Keytab and KDC's are CORP domain? Possible that this may be causing issues?

Is anyone able to see a different error that I perhaps missed?

Has anyone been able to test this code or find any glaring issues while I was away? I had a think about this during some time off and I don't understand what else is required to work or how to debug what the issue is, as I stated above there's a lot of different issues that could be present.


Auto sidecar injected pod report Init Crash Loop Back-off

Describe the bug
installed 1.0.1 on openshift origin 3.10, auto inject sidecar succeed, but proxy_init container keep report Crash Loop Back-off. so the Pod stay PodInitializing status
Expected behavior
should start pod with sidecar container.
Steps to reproduce the bug
lable a project as auto inject.
deploy a pod to the project.
Version
istioctl version
Version: 1.0.1
GitRevision: 42773aacced474d97159902d20579a25b1f98106
User: root@832d5020b1d4
Hub: gcr.io/istio-release
GolangVersion: go1.10.1
BuildStatus: Clean
kubectl version
Client Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.0+b81c8f8", GitCommit:"b81c8f8", GitTreeState:"clean", BuildDate:"2018-08-20T18:04:21Z", GoVersion:"go1.9.7", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.0+b81c8f8", GitCommit:"b81c8f8", GitTreeState:"clean", BuildDate:"2018-08-20T18:04:21Z", GoVersion:"go1.9.7", Compiler:"gc", Platform:"linux/amd64"}
Is Istio Auth enabled or not?
install with ansible
ansible-playbook main.yml
Environment
Atomic Centos
Istio 1.0.1
Openshift origin 3.10
Docker 1.13.1
Cluster state
istio-dump.tar.gz
proxy_init logs:

Environment:
ENVOY_PORT=
ISTIO_INBOUND_INTERCEPTION_MODE=
ISTIO_INBOUND_TPROXY_MARK=
ISTIO_INBOUND_TPROXY_ROUTE_TABLE=
ISTIO_INBOUND_PORTS=
ISTIO_LOCAL_EXCLUDE_PORTS=
ISTIO_SERVICE_CIDR=
ISTIO_SERVICE_EXCLUDE_CIDR=
Variables:
PROXY_PORT=15001
INBOUND_CAPTURE_PORT=15001
PROXY_UID=1337
INBOUND_INTERCEPTION_MODE=REDIRECT
INBOUND_TPROXY_MARK=1337
INBOUND_TPROXY_ROUTE_TABLE=133
INBOUND_PORTS_INCLUDE=6006, 8888,
INBOUND_PORTS_EXCLUDE=
OUTBOUND_IP_RANGES_INCLUDE=*
OUTBOUND_IP_RANGES_EXCLUDE=

iptables -t nat -N ISTIO_REDIRECT
iptables -t nat -A ISTIO_REDIRECT -p tcp -j REDIRECT --to-port 15001
iptables: No chain/target/match by that name.
dump
iptables-save

Generated by iptables-save v1.6.0 on Fri Aug 31 01:13:58 2018
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
COMMIT
Completed on Fri Aug 31 01:13:58 2018
Generated by iptables-save v1.6.0 on Fri Aug 31 01:13:58 2018
*nat
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:ISTIO_REDIRECT - [0:0]
COMMIT
Completed on Fri Aug 31 01:13:58 2018

after i manually add privileged to proxy-init, it works. because selinux is enforcing......
this option is needed when inject.

This help me in the exact same situation. Thanks

Hi, I'm facing the same issue with istioctl 1.0.2.
Has it been fixed somewhere, I don't see any git commit to it to solve the istioctl injection.

With a helm based setup on v1.0.2 you can just set this parameter:
--set global.proxy.privileged=true

What are the implications of privileged proxy?


overwrite option for the tests

Problem:
As a test owner, if I want to update my test or re-create from scratch, I've to delete the test and re-create again. This is extra effort
Solution:
I've implemented a overwrite=true/false option for the proxy. If overwrite=true, proxy first delete the old tests with the hash (same control mechanism for create) then will work as expected. I've cleaned the create function to list and check if there is any conflict control but proxy handler.
Open to discussions

+1


Fix non-int user_ids in user popovers.

I mainly want to put out the fire here.  The popover code could definitely be cleaned up.

Looks reasonable.  We should also consider making that a more generic helper and using it in a few other files (see $ git grep data-user-id static/js/).


Fixed the nav bar and the position of sun icon

Related Issue
The toggle icon for dark mode isn't responding
Fixes:  #451
Description
The navbar isn't visible on white background so I adjusted the shadow of text and improved visibility and the toggle icon for dark  mode was not aligned properly. I adjusted it and fixed the position as well

Type of PR

[x ] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
Checklist:

[ x] I have made this change from my own.
[ x] I have taken help from some online resources.
[ x] My code follows the style guidelines of this project.
[ x] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ x] My changes generate no new warnings.
[ x] I have tested the changes thoroughly before submitting this pull request.
[ x]  have provided relevant issue numbers and screenshots after making the changes.

@Samar-Ali-Ansari Please see the conflicts . Resolve the conflicts . Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


Utilise 'prefetch_related' to reduce the number of queries needed for rendering

Generally, when rendering a menu, we're only ever dealing with one instance of a menu at a time, so using 'prefetch_related'  to fetch menu items doesn't really gain us anything (a query is still required to fetch the menu items - the difference is, that query would just be made earlier in the process).
Since we offer hooks for changing the menu item queryset, prefetching the menu items might just be a waste of resources, since any custom queryset manipulation would result in a fresh database query anyway.


Use OT_URI_PATH_* names for paths.

It seems astyle is broken, switch to uncrustify?

We can switch to uncrustify after merging #1764 :)


Add instance-properties group to sort-comp. Issue #599.

Relevant issue: https://github.com/yannickcr/eslint-plugin-react/issues/599
It's a common convention to have instance properties on top(right below the static properties/methods), like this:
class Hello extends React.Component {
  static displayName = 'Hello';

  count = 0;

  componentDidMount() {
    // ...
  }

  handleClick = () => {
    this.count += 1;
    // ...
  }

  render() {
    // ...
  }
}

Right now sort-comp rule doesn't allow that and wants count to be below componentDidMount, unless you specify it by name in the configuration.
This PR's aim is to allow placing instance properties separately.
The default configuration is not changed.

Allowing it to be configurable is excellent. However, changing the default order makes it a breaking change. Should this preserve the default order, and be semver-minor, and change the default later?

@ljharb I've reverted the default order. My initial way of thinking was that this change could be part of 6.0.0, considering that it's in alpha now.

That's a fair point. @yannickcr should weigh in on that.

Since 6.0.0 is imminent we could do this, but I don't know if it is a good thing to force instance properties on top in the default configuration.
What is the most common order used by React users here?

Instance properties are still stage 1, so we don't use them yet at Airbnb. However, since instance properties run almost as if they were in the constructor, i think they absolutely should all be placed just like the constructor - at the top.

This has become a common pattern for the react community, and one that I would certainly like to enforce in my projects. Mind taking another look at this and weighing in on why it is not accepted? (other than the conflicts to be resolved now)

Public Class Fields are on stage 2 already, why it still hasn't been merged into 7.x?...

@klimashkin this needs reviews from more collabs first.
Separately, stage 3 is the time when it's safe to start using a feature, so that's when it will become critical to be supported here.

Class fields is now a stage 3 proposal. Happy to contribute if this needs someone else to take it on.

Unfortunately @le0nik deleted their fork, so this PR can never land.


Fix files_dropped in HTML5 export mono builds.

This PR fixes #55593
(There was an exception thrown on FS.mkdir() because the path ends with a trailing slash)

(Updated commit author because I was using old git config. Otherwise no change to the code)

@Fro-Z are you using a custom build? I can't reproduce the linked issue with official 3.4 builds, but it's something that might have changed in more recent emscripten versions (I know they are doing and heavy refactoring of the FS library).

@Faless No, I am using the official 3.4 mono release. Godot Engine v3.4.stable.mono.official.206ba70f4 to be precise

@Fro-Z oh, I see, so it was the other way around, old versions of emscripten (used for mono builds) does not support it.

Thanks!

Cherry-picked for 3.5.

Cherry-picked for 3.4.1.


Throw IllegalArgumentException in public API when table names aren't valid

For many public API operations, we accept a table name or namespace name argument. These are often sent to the server as-is, where an exception may be generated and returned to the client because the argument is not in the correct format.
In our API, wherever we accept a table or namespace name as an argument, we should validate it on the client side to see if it even makes sense, and throw an IllegalArgumentException with an appropriate message when it doesn't. This would allow for fast failure, and achieve consistent behavior when a table or namespace name doesn't make sense.
Table names (without a namespace, or in the default namespace) and namespace names (except the default namespace, which is an empty string) should match: ^\w{1,1024}$
A fully-qualified table name is a name that consists of a namespace name, plus a dot separator, and then a table name.
Constants.java currently contains constants for the maximum lengths of the namespace and table name components, and the current validation code is somewhat scattered between several different classes. I found existing validation code in Namespaces.java, Tables.java, FateServiceHandler.java, and TableValidators.java. There may be more.
(originally: https://issues.apache.org/jira/browse/ACCUMULO-2133)

@ctubbsii Per our conversation, I would like to be assigned to this task.

Hi @EdColeman. I am looking forward to working more on this project. Please let me know if any new contributions would be needed. For my skills and ability, please visit my profile and let me know if can contribute.
I would ❤  to contribute more.
Thank you 😄

This was fixed in #2156 and #1971


Run SonarCloud only on pull requests to master

Run SonarCloud less often to reduce build times for normal CI builds.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: ociosan sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


A service message will not be sent from iframe if it is removed afterwards (fix #64)

/cc @churkin @miherlosev

\r-

FPR

\r-

FPR

lgtm

lgtm

lgtm


[cirque] Cleanup thread network setup code

Problem
Currently, we setup thread network for EchoTest, InteractionModelTest and OnOffClusterTest, these tests are using ThreadNetwork as IPv6 backbone. The openthread setup code is not clean due to lots of remote shell execution and time.sleeps for constant time.

Summary of Changes

Use ot-ctl dataset set active to setup thread network in one command
Avoid sleep(15) when waiting for thread network becoming stable.

@erjiaqing conflict


Order, orientation -> transpose ?

The orientation keyword is used to transpose 1d plots and make them vertical.
In the same way, the order keyword is used in 2D plots to change the way dims are interpreted.
https://github.com/lukelbd/proplot/blob/591dac72fd33124b793e6d1e37e297005196a633/proplot/wrappers.py#L410
I'm not sure this is crucial since you always have to check the consistency between coordinates and data. In addition, this latter keyword can be confused with the matplotlib keyword. Is this one no longer accessible?
Don't you think a global transpose keyword would be more appropriate, for both 1D and 2D plots? For 2D plots, a value like "auto" would even try to guess the appropriate orientation depending on coordinates variations along dimensions, and potentially, attributes (lon, lat, time, etc....).

Makes sense to me. Note order derives from numpy, was just trying to go with their conventions. Want to submit a PR? I can also get to it sometime in December.
Also since you seem to be digging into these wrapper functions, keep an eye on #45 -- wrappers will soon be broken up into private helper functions, applied to dedicated ax.plot, ax.contour, etc. methods individually, and the documentation bits associated with each wrapper will be automatically embedded in the ax.plot, ax.contour, etc. methods using matplotlib's docstring interpolation.

I've finally added transpose as an alternative to order (b90cac4).
I haven'ted added transpose for the 1D plotting commands but I decided I'd rather not -- the new paradigm is to use "horizontal" versions of each plotting command (e.g. plot/plotx, boxplot/boxploth, etc. -- all of the new "horizontal" commands were motivated by matplotlib's bar/barh and fill_between/fill_betweenx).


Is this project maintanied anymore?

Last merge was July 19, 2022...

Yikes ok just read this thread ☹


Bztools nosetests phonebook

@sylvestre
The self.demo_dict we treat as a primary Dict, if there is any mess up in the people.json, we could catch it with this.
by the way phonebook.py is just reading that people.json and processing it. In tests also if we are doing the same, then there is no pint in testing. Isn't it?
We  make sure that people.json processing done by Phonebook is correct by comparing this dict(self.demo_dict) with the desired output; Kind of testing the methods and Testing the people.json also :)

@sylvestre any updates ?

Sorry, traveling!


Custom icons problem

customCollections: {
        // key as the collection name
        'my-icons': {
          play: '<svg><!-- ... --></svg>',
          // load your custom icon lazily
          settings: () => fs.readFile('../public/svg-icon/play.svg', 'utf-8'),
          /* ... */
        },
      },

// generated by unplugin-vue-components
 Iconplay: typeof import('~icons/ic/onplay')['default']

console.error
Icon `ic:onplay` not found

There seems to be a problem with the automatically generated path
The correct path is more likely to be like this
 Iconplay: typeof import('~icons/my-icons/play')['default']

How did you solve this?


colab installation broken (dependencies)

Hi! It seems there is some dependency issue going on. I've been troubleshooting locally with no luck.
When running the installation bit of the colab notebook I'm getting the following:
  Preparing metadata (setup.py) ... done
ERROR: Could not find a version that satisfies the requirement torch==1.9.0 (from clmr) (from versions: 1.11.0, 1.12.0, 1.12.1, 1.13.0, 1.13.1, 2.0.0, 2.0.1)
ERROR: No matching distribution found for torch==1.9.0

Currently investigating a good dependency configuration for this repo. Info welcome.

I found a combination of packages that seems to be working well:
python = "^3.10"
torch = "1.12.0"
torchaudio = "0.12.0"
pytorch-lightning = "1.9.0"
torchaudio-augmentations = "0.2.4"
simclr = "1.0.2"
torch-pitch-shift = "1.2.4"
soundfile = "^0.12.1"
matplotlib = "^3.7.1"
scikit-learn = "^1.2.2"

I want to implement the CLMR model for genre detection on GTZAN dataset and and then try to tweak the architecture a bit maybe. Can someone please help?