Add measurement for private selection with known threshold

Implement #1781.

My reflection on a conversation with @Shoeboxam:
There are two primary tasks regarding private selection:

Return a result above a predefined threshold (this contribution falls into this bucket)
Return the best output

The second most important aspect of a private selection algorithm is how many times to run the mechanism (in either one of the tasks). It seems that the most general presentation is as follow: sample an integer K from a predefine specific distribution, run the mechanism at most K times and return the first result the passes the threshold (for task 1) or run the mechanism for K times and return the best output (task 2).
For task 1, K should be sampled from the geometric distribution with $0 \leq \gamma < 1$ (see Algorithm 1 in [LT19] and Appendix C in [PS21]). Therefore, we will have a single parameter stop_probability.
For task 2, the distribution for sampling K is the truncate negative binomial [1], and it is a generalization of the distribution presented in [LT19] (where is the truncate geometric distribution [2]), that can provide different privacy-utility tradeoffs. There are two parameters here: \gamma and \eta.
Therefore, unfortunately it seems that is less user-friendly to try and unify the API for the two tasks.
We will drop the epsilon_selection and steps parameters because they used to control the maximal runtime of the algorithm. But this can be controlled via the stop_probability without spending extra privacy budget.
[1] Negative binomial distribution is "a discrete probability distribution that models the number of failures in a sequence of independent and identically distributed Bernoulli trials (of probability $\gamma$) before a specified (non-random) number of successes $\eta$ occurs.
Truncate negative binomial distribution: setting Pr[K = 0] = 0.
[2] With $\eta = 0$.
The algorithms in [LT1] uses more explicit representation of the geometric distribution. Instead of sampling the number of attempts K, they flips a $\gamma$-based coin every iteration that decide whether to stop the algorithm. This is equivalent to sampling K ahead of time.
[LT19] Private Selection from Private Candidates
[PS21] Hyperparameter Tuning with Renyi Differential Privacy

#2126
#1782  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @shlomihod and the rest of your teammates on  Graphite

Sorry for the never-ending API picking, but I think the following API handles everything and is pretty accessible:
def make_select_private_candidate(
	measurement,
    stop_probability,
	threshold=None,
    num_trials=1,
	max_candidates=None
)

If you just specify measurement and stop_probability, you get algorithm 2/theorem 3.2 satisfying 3ε-DP.
If you then also specify threshold, you get algorithm 1/theorem 3.1.
num_trials controls eta (for PS21) but defaults to geometric (for LT19).
If max_candidates is set, you add an additional ε0 term.

Raise a construction-time error if an invalid combination of parameters is passed.
For now, the API would be this, following the same algorithm as in your existing PR:
def make_select_private_candidate(
	measurement,
    stop_probability,
	threshold,
)

We can add other features gradually as-needed in a backwards-compatible way later.
BTW the Rust impl in the PR linked above is working, but I still need to polish it and implement these changes.

API discussions are fun!
For max_iteration, I'm uncertain about the added value it provides to the user. While it offers more deterministic runtime control, the user incurs a privacy budget cost, ε0. It seems that the deterministic aspect may not be essential, as users can adjust the stop_probability parameter to achieve an expected runtime without added costs. Additionally, how does this parameter interact with PS21?


I'm getting an error when I try to build image in Azure

https://stackoverflow.com/q/76369434/139698
[Enter feedback here]

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

ID: 61801b87-f37b-1025-c41e-73689e49b9da
Version Independent ID: f66e1382-6bd2-1b08-bb15-1e1868bf0062
Content: Deploy to Azure Container Apps using Visual Studio Code
Content Source: articles/container-apps/deploy-visual-studio-code.md
Service: container-apps
GitHub Login: @alexwolfmsft
Microsoft Alias: alexwolf

I am facing the same problem with this guy.
First, if the user starts from a fresh Azure account, he won't have any container registry enabled and the section depending on that will fail. For me, I needed to manually create a CR through the portal for the guide to work. After the steps regarding the creation of a new CR worked.
Second, while building the image locally works (after running NPM for the first time, that is), it kept failing while building the container image on Azure in the first COPY step. I could not figure out what was the root cause of this failure but I think it might be worth checking with a fresh install and fresh account if the guide works as intended.

Thanks for your feedback and your contribution to Azure docs.
Feedback for this repository is moving away from GitHub to a system specific to the Microsoft Learn platform. Issues for this repository will soon be disabled, and additional comments from GitHub will no longer be possible. However, we are now tracking and triaging this issue in the new feedback system.
To learn more about our feedback systems, please see Provide feedback for Microsoft Learn content.
#please-close


[Typescript] Yield return value type safety

I'm ramping up on redux-saga and Typescript by working on a small project.
Something I've noticed is that the return value of yield effect(...) is always any. I'm not familiar enough with the platform to understand if this is a limitation of Typescript, or some missing type annotation in redux-saga/my code.
E.g.:
function selector(state: State) {
    return state.selected;
}

function* yieldNumber() {
    yield 1;
}

function* saga() {
    let num = yield call(yieldNumber); // num has inferred type of any
    let selected = yield select(selector); // selected: any

    // My workaround
    let num: number = yield call(yieldNumber); // works as long as I don't misrepresent the type
}

I believe this is a Typescript limitation, so I filed an issue on their end: https://github.com/Microsoft/TypeScript/issues/14883.

facing the same issue now that I'm trying to adopt Typescript.
@ssynix  did you find a workaround/pattern to have type safety for the saga's return values?

@raduflp There's no workaround since it's lacking support at the language level. There are several threads mentioned in the issue above that discuss this feature, saying that it was blocked on boolean literal types and default template parameters (both now implemented), but generator yield type propagation still hasn't seen any traction in the past year.
The closest thing to a workaround is still what I wrote in the code sample above: you can manually assert the type yourself to make sure the rest of the code is typesafe, but there's nothing you can do to automatically detect if that original type-assertion is wrong.

Is there anything new about this issue?

@nicgirault<EMAIL_ADDRESS>will supposedly come with better support for generators, so this is probably something which we'll tackle then.

Hi @Andarist Is there any in-progress task due to this issue? or help how I can make PR for that?
The microsoft/TypeScript#31639 is closed and it is available with next tag.
Thank you

@PejmanNik this is happening in https://github.com/redux-saga/redux-saga/pull/1892

Thank you @Andarist  👍

@PejmanNik I don't want to disappoint you, but note that my PR won't be sufficient to fix this issue properly. Saga generators would indeed be strongly typed, yet yielded effects return types would still be any as in the OP example. As far as I know, TS 3.6 still won't be able to make TNext depend on what is yielded.
However, I have a PoC running locally proving that it should be possible to make a ESLint rule which would assert that:

You always provide an explicit type for yielded effects
The type you provide is consistent with the return type of the effect

I'll work on this ESLint rule when #1892 gets merged if I have some time. Sure having proper type inference built at the language level would be way better, but such ESLint rule would at least prevent most mistakes I think.

Thank you @gilbsgilbs for your great work.
I have a crazy idea and want to know what do you think about it
after so many trials I found yield* can detect return type of function. so we can implement a custom version of each effect that must call with yield* and in that new custom function, we just handle type and then call real one with a yield. 🤷♂😓

@PejmanNik Well, I'm not sure to follow. Do you have a code example?
As far as I know, in this case:
function* gen0() {
  yield* [1, 2, 3];
  return 'foo';
}

function* gen1() {
  const result = yield* gen0();
}

result has type "any".

oh sorry @gilbsgilbs. I think this is crazy way but at last it work
function* callSafe<Fn extends (...args: any[]) => Generator>(fn: Fn, ...args: Parameters<Fn>)
{
  const result = yield call(fn,...args);
  return result as Parameters<ReturnType<Fn>["return"]>[0];
}

function* typeTest ()
{
  const result = yield* callSafe(fn);
}

result has ReturnType

This is very hackish, yet it makes sense and I think your approach is correct (typings-wise) and isn't a bug in TypeScript. I didn't realize yield delegation was improved in TS 3.6 and I made my test against TS3.5, but in TS3.6 we do actually get strong types with the same snippet.
Maybe this is something we could include in the TypeScript recipe or even in a third-party library :thinking: . Well done.

Thank you @gilbsgilbs
Yes I got the idea from there 😁
If you and other maintainers of saga think it can help. I can work on PR or a small third-party library.
What do you think?

I'm not a maintainer of Redux-Saga :wink: . Just a happy user who is looking for improved type-safety and trying my best to contribute towards this direction. Since it's a TS-specific hack, I don't think it has its place in the main repo.

so many of your comment help me. Thanks for having TS use back 😄
Yes, I agree. I just wonder how others think about making this as a library.

@PejmanNik I just threw this together, it might serve as a starting point.
https://github.com/agiledigital/typed-redux-saga

Wow @danielnixon 😒🤐 I already do it. I just start a repo for MY IDEA. I also work on the medium blog for it. please remove that. I really don't like this. you get my idea that I'm working on it and make repo from that

Shouldn't this be part of this library rather than a separate library?

Return typings worked for me with @danielnixon's library but it would be great to get this integrated into the main lib.

#2053 is about exactly that, but it's stuck in code-review. @Andarist seems to be busy. Not sure if there are other maintainers who could merge it.

Hey guys, three years since the topic was started...
We still have inferred type of any.
typed-redux-saga is good, yes but it's not serious whereas  big library has typing that does not work.
or may I have an example when it works good?

Four years in 25 days already, @egorovsa ! But that's not fair, we should start counting at least from the release of TS 3.6 - which is 1.5 years.
I would like to thank everybody trying to have it done, guys. It was funny to discover that yield* "magically" works where yield does not. IIRIC 4.2.2 now is the current version and yet there's no a solution for typing yields. Alas, it's not that easy.

// My workaround
let num: ReturnType = yield call(yieldNumber); // Don't work with generics such as Promise

This is a serious issue. I spent a whole day to fix this. I added a * just next to yield as per typescript suggestion but my whole saga stopped working. One way is to disable typescript chekc strcit mode off untill this is fixed

@saswat3115 Honestly, I ended up just putting dozens of // @ts-ignore after upgrading to TS 4.2 the day before yesterday. That's because things like const token = yield select(getToken) just don't work anymore. As for the stars — that can only work with  https://github.com/agiledigital/typed-redux-saga , as the underlying stuff need to be changed as well.

I've been using typed-redux-saga in production for two years now, and I haven't had any problems with it at all. I highly recommend switching instead of bending over backwards trying to make redux-saga type safe.

@harvey56 did you try to restart webpack?

undefined TypeScript error in undefined(undefined,undefined): Cannot find global type 'Array'. TS2318

@harvey56 are you compiling from within VS Code? if you started getting an error when you upgraded VS code, it may be a new version of typescript that's causing the problem. The typed-redux-saga repo has ^4.2.3 in its devDependencies, so try putting that in your package.json, rebuild node_modules, then change the typescript version VS code is using by running typescript: select typescript version with ctrl/cmd+shift+p. Can you paste a snippet of the code that causes this error?

Use the response type of your api .
For me, I am using Apisauce. You can refer below code.
import { ApiResponse } from 'apisauce';
const response : ApiResponse<any,any> = yield call(api.machinesList, action.params);

Hi there, I was crazy with this thing before. Then I found that If I add an interface for responce..., that warning was gone.
I'm using graphQL, so this is what I did:
interface IResponse {
    data?: any;
}

export function* getStreets(payload: any) {
    const variables = payload.payload;
    const response: IResponse = yield call(services.getStreets, variables);
    const { getStreetByProvinceAndDistrict } = response?.data?.result || {};
   // ......
}

Hi there, I was crazy with this thing before. Then I found that If I add an interface for responce..., that warning was gone.
I'm using graphQL, so this is what I did:
interface IResponse {
    data?: any;
}

export function* getStreets(payload: any) {
    const variables = payload.payload;
    const response: IResponse = yield call(services.getStreets, variables);
    const { getStreetByProvinceAndDistrict } = response?.data?.result || {};
   // ......
}

That will work, but the problem with doing it that way is if someone changes the signature of services.getStreets to return IFoo, any code downstream of the saga will still think it has an IResponse. You lose the benefits of type inference and won't catch potential runtime errors. That's the reason @danielnixon created typed-redux-saga. 🙂


Add view for Gardener Shoots

Description
Changes proposed in this pull request:

...
...
...

Related issue(s)

/test pre-busola-integration-test-k3s

This was just a POC. We can close this


Unopenable.

No matter what i do i can't open it, i have re-downloaded it and even restarted my computer but it doesn't open no matter what.

I have re-downloaded it 2 more times and it still doesn't work.


Add: Tekkit SMP

Description
Tekkit SMP has been released, so I decided to make an egg for it. The only problem is that the Technic download servers are very slow so the installation takes some time...
I have also updated the links in java/technic/
Checklist for all submissions

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you tested and reviewed your changes with confidence that everything works?
[ ] Did you branch your changes and PR from that branch and not from your master branch?

If not, why?: I made the changes directly in the master branch because I am a bit confused about the recommendation to use a separate branch.

[x] You verify that the start command applied does not use a shell script

[ ] If some script is needed then it is part of a current yolk or a PR to add one

[x] The egg was exported from the panel

New egg Submissions

[x] Does your submission pass tests (server is connectable)?
[ ] Does your egg use a custom docker image?

[ ] Have you tried to use a generic image?
[ ] Did you PR the necessary changes to make it work?

[x] Have you added the egg to the main README.md and any other README files in subdirectories of the egg (e.g /game_eggs) according to the alphabetical order?
[x] Have you added a unique README.md for the egg you are adding according to the alphabetical order?
[x] You verify that the start command applied does not use a shell script

[ ] If some script is needed then it is part of a current yolk or a PR to add one

[x] The egg was exported from the panel

On first look this is fine. But please use Parker images please.

Done

hi, is there anything else I should change?


BitmapData Causing Crash - Windows

package;
import openfl.display.*;
class Main extends Sprite
{
public function new()
{
super();
var bitmapdata = new BitmapData(1024, 1024, true, 0);
}
}
lime: 2.3.0 git [dev:D:\SDKs\haxe3\haxe\lib/lime/git]
openfl: 3.0.0-Beta3 git [dev:D:\SDKs\haxe3\haxe\lib/openfl/git]
Called from ApplicationMain::main ApplicationMain.hx line 122
Called from ApplicationMain::create ApplicationMain.hx line 30
Called from lime.app.Preloader::create lime/app/Preloader.hx line 61
Called from openfl.display.Preloader::start openfl/display/Preloader.hx line 93
Called from NMEPreloader::onLoaded NMEPreloader.hx line 107
Called from openfl.display.DisplayObject::dispatchEvent openfl/display/DisplayObject.hx line 784
Called from openfl.events.EventDispatcher::dispatchEvent openfl/events/EventDispatcher.hx line 266
Called from openfl.display.Preloader::display_onComplete openfl/display/Preloader.hx line 129
Called from lime.app.Preloader::start lime/app/Preloader.hx line 234
Called from ApplicationMain::init ApplicationMain.hx line 86
Called from ApplicationMain::start ApplicationMain.hx line 152
Called from Type::createInstance D:\SDKs\haxe3\haxe\std/cpp/_std/Type.hx line 82
Called from DocumentClass::new ApplicationMain.hx line 210
Called from Main::new Main.hx line 8
Called from openfl.display.BitmapData::new openfl/display/BitmapData.hx line 197
Called from lime.graphics.Image::new lime/graphics/Image.hx line 129
Called from lime.graphics.Image::fillRect lime/graphics/Image.hx line 365
Called from lime.graphics.utils.ImageDataUtil::fillRect lime/graphics/utils/ImageDataUtil.hx line 292

I wonder if this is related to this:
https://github.com/openfl/openfl/pull/639

What target are you using? CPP I imagine?

Yes CPP.  Using Flash Develop to compile openfl based Haxe program to
Windows
Sincerely,
Joe Williamson
Chief Technology Officer
<EMAIL_ADDRESS><EMAIL_ADDRESS>https://www.realitycharting.com
(Direct)<PHONE_NUMBER>
(US)<PHONE_NUMBER>
www.RealityCharting.com http://www.realitycharting.com/
On Tue, Apr 28, 2015 at 11:25 AM, Lars Doucet<EMAIL_ADDRESS>wrote:

What target are you using? CPP I imagine?
—
Reply to this email directly or view it on GitHub
https://github.com/openfl/openfl/issues/637#issuecomment-97162318.

I updated after the merge from jgranick and it did not fix this issue

I can't reproduce it using latest git versions of lime and openfl

I was using haxe 3.2 rc2.  Downgraded to 3.1.3 and it didn't resolve the issue. project.xml below

This is the full output from FD
Running process: D:\SDKs\haxe3\haxe\haxelib.exe run lime run "project.xml" windows -debug
Could not find primitive lime_image_data_util_color_transform__3.
Could not find primitive lime_image_data_util_copy_channel__MULT.
Could not find primitive lime_image_data_util_copy_pixels__5.
Could not find primitive lime_image_data_util_fill_rect__3.
Could not find primitive lime_image_data_util_flood_fill__4.
Could not find primitive lime_image_data_util_get_pixels__3.
Could not find primitive lime_image_data_util_merge__MULT.
Could not find primitive lime_image_data_util_multiply_alpha__1.
Could not find primitive lime_image_data_util_resize__4.
Could not find primitive lime_image_data_util_set_pixels__4.
Could not find primitive lime_image_data_util_unmultiply_alpha__1.


Dictionary with parameters specific to an experiment

It would be nice to have a dictionary stored in a preferences folder, which contains parameters like qubit frequency, pi pulse amplitudes, etc. These parameters are used in various measures, so it would be convenient to have them stored in a single location. This way, we could run calibration procedures where we run an experiment which updates these values, and subsequently, this changes the parameters in all other measures.

@leghtas do you want a roadmap for that and then implement it yourself or do you want me to do it ?

@MatthieuDartiailh  I am happy to do it, maybe we can talk about it tomorrow so you can give me some guidance.


Reduce gap between navigation link and dropdown so that it doesn't close

Describe the task
When I hover on a nav item and then try to go to the dropdown below, there is a certain space in between that closes the dropdown.
Here's a small recording to understand:
https://user-images.githubusercontent.com/12053186/157629862-89c6f0b2-0610-42ee-8ef8-77c39e58738f.mov
Expected behavior

Reduce the spacing between menu link and dropdown so that it doesn't close
Don't make them too close!

This issue has been fixed
Refer screenshot


Suggestion: Have a reference for the IO object

Perhaps I have missed something, but while looking around I couldn't find a reference that told me what the IO object does. There may even be other objects out there that I don't even know exist.
I think that a reference for the IO object would be useful to newcomers to the language.

Hmm, that is indeed a strange ommission. The Meta class is also undocumented, but this is easier to understand since it has only just been added.
In any case you can find all methods of the IO class over here for now:
https://github.com/munificent/wren/blob/master/builtin/io.wren

Thanks!
That is very helpful :)

I have submitted pull request #275 that includes my attempt at documenting the IO class. I took a look at the way the other classes were documented, and applied the same rules to the IO class.
On a side note I have also written a pseudo-random number generator (using the xor128 algorithm) in wren - just ask if you are interested :)

I have submitted pull request #275 that includes my attempt at documenting the IO class.

Thank you! :D

No problem :)

Fixed by https://github.com/munificent/wren/pull/275.


[DOC] The Linkis debug doc needs to be improved

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Problem Description
Though there is a brief debug doc, it missed alot. For example remote debug, local environment configuration, etc. Needs to be improved.
EN:
https://github.com/apache/incubator-linkis-website/blob/master/docs/development/linkis_debug.md
CN:
https://github.com/apache/incubator-linkis-website/blob/master/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/linkis_debug.md
Description
No response
Use case
No response
solutions
No response
Anything else
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

I would like to write some docs about how to debug front-end and back-end. Please assign this to me. @peacewong


The problem with keyboard shortcut hints.

Microsoft PowerToys version
0.56.1
Running as admin

[ ] Yes

Area(s) with issue?
Shortcut Guide
Steps to reproduce

Disable Keyboard Shortcut Suggestions.
Activate suggestions by holding down the Win key.

This doesn't always work.

✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

Tried replicating this without success.
Was this right after update to 0.56.1? Wondering if you might have two PowerToys instances running at the same time.
Could you please send a bug report? That might contain some clues. /bugreport

I have one copy of the program.
I have noted that this does not always work.

i can't repro this on a 0.58 build, lets mark a revisit tag and try out on a 0.58 when it is released in the next few days


Custom text

would it be possible to create feature to include different text than the label says. i.e. label is ABC-123 and I would like to print under the barcode only 123. thx

EAN8(label).write(f, {'write_text': False, 'text': "%s\n123. thx" % (label)})
'write_text': False  makes it turn off the default text.
'text': "my new text" changes the default text to that new text.
Turn off the default then turn, write your own, including the original label.

I couldn't get this inline method working. I was able to get @QuickLearner171998 's method to work.
To adapt it to this scenario, it'd look like:
#Put this under the `import` statement but above your code
barcode.default_writer_options['write_text'] = False
barcode.default_writer_options['text'] = "my new text"


feat: add Window::set_enabled and Window::is_enabled

closes #6660

the macOS implementation is NOT tested


Update Architectural Diagram

Since DB now has only one table, will need update the diagram to reflect new structure.
Also remove elasticsearch.

Completed new diagram to reflect our architecture more accurately 💯

Completed new diagram to reflect our architecture more accurately 💯


version set to ...-snapshot for maven package type yields not the latest but all snapshots

I need to download the latest snapshot for a given artifact and version:
- task: DownloadPackage@1
  inputs:
    packageType: 'maven'
    feed: 'Artifacts'
    definition: 'package:cc-messagerelay'
    version: '0.0.1-snapshot'
    files: '*.jar'
    downloadPath: './target/'

but this does not yield the latest snapshot of version 0.0.1 but all snapshots e.g.:
##[debug]rm -rf /home/vsts/work/1/s/target/cc-messagerelay-0.0.1-20221212.120339-19.jar
##[debug]rm -rf /home/vsts/work/1/s/target/cc-messagerelay-0.0.1-20221212.105844-18.jar
...
##[debug]rm -rf /home/vsts/work/1/s/target/cc-messagerelay-0.0.1-20221208.131120-3.jar
##[debug]rm -rf /home/vsts/work/1/s/target/cc-messagerelay-0.0.1-20221208.130455-2.jar
##[debug]rm -rf /home/vsts/work/1/s/target/cc-messagerelay-0.0.1-20221207.165101-1.jar

So how to acquire the the latest snapshot of a given version?

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

ID: 769d848b-315d-86bf-1673-5a87f87a970d
Version Independent ID: 769d848b-315d-86bf-1673-5a87f87a970d
Content: DownloadPackage@1 - Download package v1 task
Content Source: task-reference/download-package-v1.md
Service: azure-devops-pipelines
Sub-service: azure-devops-pipelines-tasks
GitHub Login: @steved0x
Microsoft Alias: sdanie

See also #67.

Thank you for your feedback. We are migrating this issue to our new documentation feedback system, and closing this issue.
As we phase out GitHub issues for this repository, we encourage you to propose changes using public PRs or submit feedback through our updated control at the top of the page. For more information on our feedback systems, see https://aka.ms/contentuserfeedback.


TypeError: option expires is invalid

Hi guys,
I'm not sure if this is a bug or me being stupid, but no matter what I try, I can't seem to get the expires option to work.
Ideally I'd like to use moment, but I've also tried using a plain old new Date().
Here is my code:
cookie.set(key, value, {         path: "/", expires: moment().add(30, "days").valueOf()       }
And the error:
TypeError: option expires is invalid     at Object.serialize (index.js:145)
Any help is greatly appreciated!

Hi @thehaytonproject
You can simply change .valueOf() by .toDate(). The first returns the unix timestamp (that could be technically transformed into a Date) and the second is transforming it to a Date instance.
The option expires is invalid error happens when your not using a Date instance.


Organize magenta.music into library.

We should start by re-organizing the functions in sequences_lib, etc. and exporting them directly under magenta.music.

+1. There are functions and data structures in Magenta that could be very useful to the MIR community, but it can be impractical to have Magenta as a dependency. For example, I would like to use the NoteSequence proto to store some pre-processed MIDI files, but I can't install Magenta because I need to use an older version of TensorFlow.
If there's any way I can help with this, I can look into it.

Thanks for the offer! Like I mention here, a first step would be refactoring what's under magenta/music and exposing it (for now) as a library within magenta. That would make it easier to pull out later and put into its own package. Of course, totally separating it from tensorflow dependencies might be a challenge still...

Most of the tensorflow dependencies are around tf.logging, which we can easily replace with abseil, and tf.gfile, which is more of a problem since we need it for internal compatibility. I suppose we could do something like write our own magenta.gfile wrapper, but that seems a little hacky.

Maybe I misunderstood what "library" meant in this context (presumably it's about creating a Bazel rule and not a separate Python package). If that's the case, sorry for spamming this issue and I should probably create a new one.

No, it does mean a separate package. But before we can do that we first need to break all of the internal dependencies.

OK, thanks for clarifying. So the goal would be to move the code (everything under music and protobuf?) to a new directory in this repo (eventually with its own setup.py), is that correct?
I tried to find things that music depends on. The only ones which I don't really see how to resolve are pipeline.statistics and common.testing_lib, which are imported in music.*_lib or the associated tests. On the other hand, many modules (notably music.*_io plus the protobuffers) seem to be already self-contained. I'm wondering if it would be reasonable to start by moving out the self-contained or easy-to-resolve things and leave the rest for later.

I gave it a stab (see #1519). The only dependency left seems to be pipeline.statistics; I'm not sure what it does, but it doesn't seem to be music-specific enough to move it under music.

Thanks! @cghawthorne can you help review this?
Doing this will also allow us to put MAESTRO in TFDS.

I believe the next step is to make a pip package. @cghawthorne thoughts on how to best do this?

Note that there is still the dependency on pipelines.statistics (imported e.g. from chords_lib).

I think there might still be some tensorflow dependencies to trim too?
Once those are done, I think we can just add a new setup.py in the music subdir and modify our root setup.py to exclude the music subdir.

I guess the TF dependencies can stay for now and potentially be removed later after the pip package is done?
As for the pipelines.statistics dependency, I can't think of any solution other than also making it a separate package (which does make some sense, since it already seems to be independent, and not tied to pipelines or anything else in Magenta in any way).

@adarob @cghawthorne Any thoughts?

Sorry, but we are both currently out of the office. We'll get back to you
as soon as we can!
On Fri, Jun 7, 2019 at 2:38 AM Ondřej Cífka<EMAIL_ADDRESS>wrote:

@adarob https://github.com/adarob @cghawthorne
https://github.com/cghawthorne Any thoughts?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/magenta/issues/1360?email_source=notifications&email_token=AAIJV2G3B2IGEKSDXIVO3QTPZIUCVA5CNFSM4GGGXB3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXFLDJA#issuecomment-499823012,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIJV2CPDYBBTLXBVEZZSU3PZIUCVANCNFSM4GGGXB3A
.

@iansimon what do you think about the pipelines.statistics dependencies (e.g., in drums_lib.py)? I'm thinking we can maybe just move the extract_* methods that have that dependency to the relevant files in the pipelines directory.

That's one option, another is to have those methods return a dict of plain old integer counts instead of a statistics.Counter.  I don't have a strong opinion.

The methods could accept a dict of callback functions that would get called in place of .increment(). Then the caller would create their own Counters and Histograms (only for the statistics they actually need) and pass their increment methods as the callbacks.

...something like this: #1551

I dunno, I maybe lean toward just moving the extract_* methods out of music. We don't really want to encourage more use of the pipelines code because all our new pipeline-style code is using Beam, which has its own ideas about metrics.

Thanks for the PR! As a followup, would you mind moving performance_rnn_pipeline and pianoroll_rnn_nade_pipeline into magenta.piplines? That way we won't have inter-model dependencies. Sorry, missed this in the initial review.

OK, should be straightforward.
What doesn't seem as straightforward is making the pip package. After reading this and this, I think there are two options moving forward:

Make magenta a namespace package and keep magenta.music inside.
Rename magenta.music to magenta_music (i.e. a completely separate package).

In both cases, music needs to be moved out into its own directory so that it can have its own setup.py, but the first option will allow it to stay logically inside magenta. However, it also requires removing the top-level __init__.py (I think this is to avoid shipping the same file in two different distributions) and I don't know if it's OK to do that.

Hi @cifkao. @adarob and I were wondering if there's some way to preserve the current directory structure. From reading the native namespace package docs, it looks like the main reason __init__.py can't be in the main magenta directory is so that find_packages ignores it. However, you can pass an exclude list to find_packages. So, would it be possible to keep the existing directory structure, add exclude=['magenta/music'] to the current setup.py, and then have a new setup.py in magenta/music for that package?
BTW, we'd be fine if the resulting packages only work with Python 3, since Python 2 support is going to end soon anyway.

@cghawthorne

So, would it be possible to keep the existing directory structure, add exclude=['magenta/music'] to the current setup.py, and then have a new setup.py in magenta/music for that package?

I doubt the setup.py can be inside the package it's supposed to install, usually it's one level above the top-level package (and it definitely needs to be run from there to find all the packages correctly).

From reading the native namespace package docs, it looks like the main reason __init__.py can't be in the main magenta directory is so that find_packages ignores it.

I think (one of) the reason(s) is that normally when you import pkg.subpkg, pkg's top-level __init__.py will run as well. In the namespace package case, you want to avoid this, because:

You want import pkg.subpkg to behave consistently whether or not some other part of pkg is installed.
You don't want to distribute two or more versions of the same __init__.py file.

The result is that a namespace package is really just a container for other packages rather than a full-fledged package. Anyway, I think that if you try to keep the current __init__.py, you might manage to make the setup work, but then the import mechanism will fail to recognize it as a namespace package and it won't work as expected.
Maybe all this just means that using a namespace package for this purpose is a bad idea, I don't know.

I tried the trick with find_packages(exclude=['magenta.music', 'magenta.music.*']) and symlinking magenta/music. It seems to work with setup.py, but it breaks installing magenta.music with pip install . (because it doesn't follow the symlink). In any case, I still think it's not possible to keep magenta's __init__.py for this to work.
The other (IMO cleaner) option is to make the package completely separate (e.g. magenta_music), as I suggested above.
What do you think? @adarob @cghawthorne

@cifkao thanks again for your patience with us!
The challenging part is how we sync these changes up with our internal infrastructure, which isn't set up for these types of cases.
We think the best approach is probably 2. Would you mind preparing a CL for that and we'll see if we can get it to be compatible with our internal codebase.

@adarob Great!
There is already #1570, but it will probably need to be updated.
One more idea: According to this, it should be possible to have a namespace package inside a non-namespace package. So we could have a magenta.lib namespace package that music would get installed into, and keep the top-level __init__.py. Later some other independent or optional components of Magenta could also end up in lib (or whatever you would like to call it). So maybe that would be cleaner or easier to integrate in the internal codebase?

@adarob I rebased #1570 to the current master, could you have a look now?

Hi @adarob, I just wanted to check to see when you see this happening.
I will soon need to release my code which uses NoteSequences, so I'm thinking of creating a provisional package containing only the code in magenta.music to depend on until this gets resolved. Let me know if I can do this in a way that would make it possible for you to reuse that.

Hi Ondrej,
Sorry about the delays on this. It is going to be a couple more weeks until
we can do this on our end, but I can commit to having it done by the end of
January.
-Adam
On Tue, Dec 10, 2019 at 12:56 PM Ondřej Cífka<EMAIL_ADDRESS>wrote:

Hi @adarob https://github.com/adarob, I just wanted to check to see
when you see this happening.
I will soon need to release my code which uses NoteSequences, so I'm
thinking of creating a provisional package containing only the code in
magenta.music to depend on until this gets resolved. Let me know if I can
do this in a way that would make it possible for you to reuse that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/magenta/issues/1360?email_source=notifications&email_token=AAIJV2HPLSQUKZFA37KAQDLQX77BTA5CNFSM4GGGXB3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGQ5NVI#issuecomment-564254421,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIJV2A5JQYBSXOUOI66WRTQX77BTANCNFSM4GGGXB3A
.

Thank you Adam, that would be great!

Any news on this? Any way I can help?

Thanks for the reminder Ondrej. I think we actually need to make these
changes internally first. I will get the ball rolling today.
On Mon, Mar 16, 2020 at 11:50 AM Ondřej Cífka<EMAIL_ADDRESS>wrote:

Any news on this? Any way I can help?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/magenta/issues/1360#issuecomment-599703954,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIJV2F3FOOEJX4PJXMMDFTRHZYI3ANCNFSM4GGGXB3A
.

@adarob Sorry to bother you with this again, I'm just curious if there's anything new...
BTW, I might have some additions to sequences_lib once this is done!

Sorry that this still hasn't happened yet. @gauravmishra was leading this effort so I will follow up with him and update the thread on Wednesday.

So, we haven't been able to make progress on this internally thus far, but we are planning to move our repo to the magenta org in the next 2-3 weeks. I am setting a condition of that move that we split out the magenta music package. Stay tuned!

Fixed by eed016ad0f179e5896056d660653a6478a6a181c

New library exists at https://github.com/magenta/note-seq

Great news!


add feature categories to documentation

Hi @haesleinhuepf,
This PR solves Issue #20. As discussed, I added a feature section to the documentation.

I structured the categories similar to the napari-skimage-regionprops documentation
I categorized the features as you did structure the label_statistics function

Best,
Mara

Awesome, thank you @marabuuu !


Samples - question

Are there any samples for Identity using VNext Web API only not the MVC identity sample?

@rustd do you know?

@stephenstroud What specifically are you looking for?

I was looking for an interface for external API's to register users etc, however, I will create this. Thanks


Remove the camera item in the picker?

Hey,,
How can i remove the first item i.e Camera icon from the picker?
Thanks in advance.
@zhangao0086

and one more thing how to change the title and done button title.

If you want to hide the camera icon, please try this:
pickerController.sourceType = .photo

About how to change the title and done button title, see also: https://github.com/zhangao0086/DKImagePickerController#camera-customization


Add qemu into build process for OpenJ9 RISC-V cross-compiles

May add this into the playbooks in future, but for now I'm going to download dynamically during the build. Required to execute constgen. Should fix https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-linux-riscv64-openj9/

I'll rebase - this PR shouldn't have the CUDA stuff in it ... I accidentally based these changes off the wrong branch

Fixes https://github.com/adoptium/infrastructure/issues/2368

@karianna Are you ok with the above explanation? This is to resolve a current build break so would be good to get it resolved ASAP.

Merged and testing at https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-linux-riscv64-openj9/500/console


From concourse to travis

Coverage remained the same at 97.403% when pulling 59533a03a7a1561d19c31b1cd2c41057224ca105 on ebolyen:travissss into 7f0608614c20d94b4db95448cc3ec564658fa44f on nervous-laughter:master.


Fix swagger spec 11

Add misising schema reference for default case that was left out in f708e0e9084a51e6ca02876f2b6f3ee39273d310
Fix swagger spec for body params:
According to the swagger spec, when defining parameters if in is body
then the schema field is required. Using type in the current way is
invalid, and actually crashes go-swagger.

@RackHD/corecommitters please review.

Jenkins, ok to test

*** BUILD #1250 ***
Test Name: Redfish Event Service should return a valid event service root
Error Details: expected 200 "OK", got 400 "Bad Request" Response body: { message: 'Cannot read property \'contents\' of undefined' } Error: expected 200 "OK", got 400 "Bad Request"     at Test.assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:205:15)     at assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:132:12)     at /home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:129:5     at Test.Request.callback (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:746:30)     at Test.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:135:10)     at Test.EventEmitter.emit (events.js:95:17)     at IncomingMessage.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:938:12)     at IncomingMessage.EventEmitter.emit (events.js:117:20)     at _stream_readable.js:920:16     at process._tickDomainCallback (node.js:459:13)
Stack Trace: Error: expected 200 "OK", got 400 "Bad Request"
    at Test.assert (node_modules/supertest/lib/test.js:205:15)
    at assert (node_modules/supertest/lib/test.js:132:12)
    at node_modules/supertest/lib/test.js:129:5
    at Test.Request.callback (node_modules/supertest/node_modules/superagent/lib/node/index.js:746:30)
    at Test.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:135:10)
    at IncomingMessage.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:938:12)
    at _stream_readable.js:920:16

Test Name: Redfish Event Service should fail to create existing subscription
Error Details: expected 409 "Conflict", got 400 "Bad Request" Response body: { message: 'Cannot read property \'contents\' of undefined' } Error: expected 409 "Conflict", got 400 "Bad Request"     at Test.assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:205:15)     at assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:132:12)     at /home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:129:5     at Test.Request.callback (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:746:30)     at Test.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:135:10)     at Test.EventEmitter.emit (events.js:95:17)     at IncomingMessage.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:938:12)     at IncomingMessage.EventEmitter.emit (events.js:117:20)     at _stream_readable.js:920:16     at process._tickDomainCallback (node.js:459:13)
Stack Trace: Error: expected 409 "Conflict", got 400 "Bad Request"
    at Test.assert (node_modules/supertest/lib/test.js:205:15)
    at assert (node_modules/supertest/lib/test.js:132:12)
    at node_modules/supertest/lib/test.js:129:5
    at Test.Request.callback (node_modules/supertest/node_modules/superagent/lib/node/index.js:746:30)
    at Test.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:135:10)
    at IncomingMessage.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:938:12)
    at _stream_readable.js:920:16

Test Name: Redfish Event Service should return a valid subscription collection
Error Details: expected 200 "OK", got 400 "Bad Request" Response body: { message: 'Cannot read property \'contents\' of undefined' } Error: expected 200 "OK", got 400 "Bad Request"     at Test.assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:205:15)     at assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:132:12)     at /home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:129:5     at Test.Request.callback (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:746:30)     at Test.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:135:10)     at Test.EventEmitter.emit (events.js:95:17)     at IncomingMessage.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:938:12)     at IncomingMessage.EventEmitter.emit (events.js:117:20)     at _stream_readable.js:920:16     at process._tickDomainCallback (node.js:459:13)
Stack Trace: Error: expected 200 "OK", got 400 "Bad Request"
    at Test.assert (node_modules/supertest/lib/test.js:205:15)
    at assert (node_modules/supertest/lib/test.js:132:12)
    at node_modules/supertest/lib/test.js:129:5
    at Test.Request.callback (node_modules/supertest/node_modules/superagent/lib/node/index.js:746:30)
    at Test.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:135:10)
    at IncomingMessage.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:938:12)
    at _stream_readable.js:920:16

Test Name: Redfish Event Service should return a valid subscription
Error Details: expected 200 "OK", got 400 "Bad Request" Response body: { message: 'Cannot read property \'contents\' of undefined' } Error: expected 200 "OK", got 400 "Bad Request"     at Test.assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:205:15)     at assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:132:12)     at /home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:129:5     at Test.Request.callback (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:746:30)     at Test.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:135:10)     at Test.EventEmitter.emit (events.js:95:17)     at IncomingMessage.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:938:12)     at IncomingMessage.EventEmitter.emit (events.js:117:20)     at _stream_readable.js:920:16     at process._tickDomainCallback (node.js:459:13)
Stack Trace: Error: expected 200 "OK", got 400 "Bad Request"
    at Test.assert (node_modules/supertest/lib/test.js:205:15)
    at assert (node_modules/supertest/lib/test.js:132:12)
    at node_modules/supertest/lib/test.js:129:5
    at Test.Request.callback (node_modules/supertest/node_modules/superagent/lib/node/index.js:746:30)
    at Test.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:135:10)
    at IncomingMessage.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:938:12)
    at _stream_readable.js:920:16

Test Name: Redfish Event Service should fail on invalid subscription
Error Details: expected 404 "Not Found", got 400 "Bad Request" Response body: { message: 'Cannot read property \'contents\' of undefined' } Error: expected 404 "Not Found", got 400 "Bad Request"     at Test.assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:205:15)     at assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:132:12)     at /home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:129:5     at Test.Request.callback (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:746:30)     at Test.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:135:10)     at Test.EventEmitter.emit (events.js:95:17)     at IncomingMessage.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:938:12)     at IncomingMessage.EventEmitter.emit (events.js:117:20)     at _stream_readable.js:920:16     at process._tickDomainCallback (node.js:459:13)
Stack Trace: Error: expected 404 "Not Found", got 400 "Bad Request"
    at Test.assert (node_modules/supertest/lib/test.js:205:15)
    at assert (node_modules/supertest/lib/test.js:132:12)
    at node_modules/supertest/lib/test.js:129:5
    at Test.Request.callback (node_modules/supertest/node_modules/superagent/lib/node/index.js:746:30)
    at Test.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:135:10)
    at IncomingMessage.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:938:12)
    at _stream_readable.js:920:16

Test Name: Redfish Event Service should fail to delete an ivalid subscription
Error Details: expected 404 "Not Found", got 400 "Bad Request" Response body: { message: 'Cannot read property \'contents\' of undefined' } Error: expected 404 "Not Found", got 400 "Bad Request"     at Test.assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:205:15)     at assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:132:12)     at /home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:129:5     at Test.Request.callback (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:746:30)     at Test.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:135:10)     at Test.EventEmitter.emit (events.js:95:17)     at IncomingMessage.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:938:12)     at IncomingMessage.EventEmitter.emit (events.js:117:20)     at _stream_readable.js:920:16     at process._tickDomainCallback (node.js:459:13)
Stack Trace: Error: expected 404 "Not Found", got 400 "Bad Request"
    at Test.assert (node_modules/supertest/lib/test.js:205:15)
    at assert (node_modules/supertest/lib/test.js:132:12)
    at node_modules/supertest/lib/test.js:129:5
    at Test.Request.callback (node_modules/supertest/node_modules/superagent/lib/node/index.js:746:30)
    at Test.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:135:10)
    at IncomingMessage.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:938:12)
    at _stream_readable.js:920:16

Are these false positives? Nothing changed re: Redfish, and I also don't think the monorail.yml file actually serves as input to anything...

Looks like it.  Jenkin's test this please.

:+1:

👍


Animator crossing cycle boundaries on InterpolatingAnimator

Describe the bug
Animation is "overstepping its bounds" when calling InterpolatingAnimator. Namely it starts a new cycle even though it should not.
I've implemented one (its below), used it in a 1 sec, 1 iteration animation  and wrote the progress values to debug channel and I got this list. Notice the last value in the list.
0
0.0128132
0.0320269
0.0494498
0.0736184
0.091936
0.1104608
0.1285988
0.1466262
0.1647193
0.1831139
0.2073717
0.225215
0.2433908
0.2614369
0.279927
0.298107
0.3221744
0.3403775
0.3585794
0.3766357
0.4008884
0.4191277
0.4373313
0.4553597
0.4735485
0.4918658
0.5104386
0.5283607
0.5464908
0.576647
0.5948195
0.6189997
0.6373238
0.6555238
0.673539
0.6977308
0.7160618
0.7343293
0.75259
0.7707779
0.7888818
0.8071246
0.825004
0.8434078
0.8674329
0.8857384
0.9039245
0.9221742
0.9462927
0.9644614
0.9826485
1
0.0010295

To Reproduce
Create and register an implementation of InterpolatingAnimator, use it.
Expected behavior
In the example above, it needs to stop at 1. Generally, I think it should stop at cycle boundaries no matter how many iterations there are and which easing it uses..
Screenshots
Not applicable
Desktop (please complete the following information):

OS: Windows 11
Version 11.0.3

Additional context
I created a translated Heaveside animator to make a discrete jump of a non-interpolatable values at 100% (bool in this example). Unfortunately, the last value causes the value to revert back to false.
    /// <summary>
    /// Animator class that handles animation progression using translated Heaviside jump at 1.0 (100%).
    /// This allows discrete value changes in animations
    /// </summary>
    public class TranslatedHeavisideAnimator<T>: InterpolatingAnimator<T>
    {
        public override T Interpolate(double progress, T oldValue, T newValue)
        {
            System.Diagnostics.Debug.WriteLine(progress);
            return progress < 1 ? oldValue : newValue;
        }
    }

    public class DiscreteBoolAnimator: TranslatedHeavisideAnimator<bool> { }

...
Animation.RegisterCustomAnimator<bool, DiscreteBoolAnimator>();

            <Style Selector="DockPanel#WorkPanel">
                <Style.Animations>
                    <Animation Duration="0:0:1" IterationCount="1">
                        <KeyFrame Cue="0%">
                            <Setter Property="IsVisible" Value="False"/>
                        </KeyFrame>
                        <KeyFrame Cue="100%">
                            <Setter Property="IsVisible" Value="True"/>
                        </KeyFrame>
                    </Animation>
                </Style.Animations>
            </Style>

@the-black-wolf Where/how do you actually use DiscreteBoolAnimator?


Support generation of documentation.

Fixes #42

Codecov Report

Merging #45 (4542e6d) into 0.6.0 (3edd923) will increase coverage by 0.13%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##            0.6.0      #45      +/-   ##
==========================================
+ Coverage   87.50%   87.63%   +0.13%
==========================================
  Files           9        9
  Lines         560      566       +6
==========================================
+ Hits          490      496       +6
  Misses         70       70

Impacted Files
Coverage Δ

word_filter_codegen/src/lib.rs
82.41% <100.00%> (+0.80%)
:arrow_up:

word_filter_codegen/tests/trybuild.rs
100.00% <100.00%> (ø)

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 3edd923...4542e6d. Read the comment docs.


Add gorbit99/codewindow.nvim

Checklist:

[X] The plugin is specifically built for Neovim.
[X] The lines end with a .. This is to conform to awesome-list linting and requirements.
[X] It's not already on the list.
[X] The title of the pull request is Add `username/repo`  when adding a new plugin.
[X] Neovim is spelled as Neovim (not nvim, NeoVim or neovim), Vim is spelled as Vim (capitalized), Lua is spelled as Lua (capitalized).
[ ] If it's a colorscheme, it supports treesitter syntax.

Thanks for the PR!


Removing .local/share/ockam-cli directly, results in encountered an error in command handler code for most CLI commands.

This is more of a misuse by me and this issue is for documenting it as I wasn't able to find it.
TLDR: Use ockam node delete --all rather than deleting files.
Ockam creates two folders; /.local/share/ockam-cli for storing node data and /.config/ockam-cli for config.json storing details about all nodes.
Trying to debug, I had a lot of nodes and was out of colour name. Rather than reading documentation, I deleted .local/share/ockam-cli, which lead to almost all commands outputting general Err encountered an error in command handler code.
So use delete --all.

@anuvratsingh thank you for reporting this.
We should show a better error here.

Closing this since the way this now works has evolved quite a bit. Thank you @anuvratsingh.


[SPARK-8069][ML][WIP] add cutoff aka thresholds to random forest

Merged build triggered.

Merged build started.

Test build #36463 has started for   PR 7205 at commit a4e33ee.

Merged build finished. Test FAILed.

Test build #36463 has finished for   PR 7205 at commit a4e33ee.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: Param[Array[Double]] = new Param[Array[Double]](this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build triggered.

Merged build started.

Test build #36594 has started for   PR 7205 at commit f9baa0a.

Test build #36594 has finished for   PR 7205 at commit f9baa0a.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: Param[Array[Double]] = new Param[Array[Double]](this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36636 has started for   PR 7205 at commit 8c1cada.

Test build #36636 has finished for   PR 7205 at commit 8c1cada.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: Param[Array[Double]] = new Param[Array[Double]](this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36639 has started for   PR 7205 at commit 5c74483.

Test build #36639 has finished for   PR 7205 at commit 5c74483.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: Param[Array[Double]] = new Param[Array[Double]](this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36642 has started for   PR 7205 at commit 3751760.

Test build #36642 has finished for   PR 7205 at commit 3751760.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: Param[Array[Double]] = new Param[Array[Double]](this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36643 has started for   PR 7205 at commit 4dd4f33.

Test build #36643 has finished for   PR 7205 at commit 4dd4f33.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: Param[Array[Double]] = new Param[Array[Double]](this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36719 has started for   PR 7205 at commit 8e00c44.

Test build #36719 has finished for   PR 7205 at commit 8e00c44.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: Param[Array[Double]] = new Param[Array[Double]](this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #36731 has started for   PR 7205 at commit 4d3081f.

Test build #36731 has finished for   PR 7205 at commit 4d3081f.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: Param[Array[Double]] = new Param[Array[Double]](this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test FAILed.

jenkins, retest this please

Merged build triggered.

Merged build started.

Test build #36843 has started for   PR 7205 at commit 4d3081f.

Merged build triggered.

Merged build started.

Test build #36849 has started for   PR 7205 at commit ac187ac.

Test build #36843 has finished for   PR 7205 at commit 4d3081f.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: Param[Array[Double]] = new Param[Array[Double]](this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test FAILed.

Test build #36849 has finished for   PR 7205 at commit ac187ac.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: Param[Array[Double]] = new Param[Array[Double]](this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36965 has started for   PR 7205 at commit 0018bd9.

Test build #36965 has finished for   PR 7205 at commit 0018bd9.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: Param[Array[Double]] = new Param[Array[Double]](this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test PASSed.

cc @jkbradley

Thanks for the PR!  I started writing up comments yesterday but then wanted to take time to look around at other libraries' practices + think more about the design.  I'm finishing up a little doc which I'll post here soon.
However, could you please separate out the changes which make the tree models extend ClassificationModel, and send those as another PR for that JIRA?

Here the design doc is: [https://docs.google.com/document/d/1nV6m7sqViHkEpawelq1S5_QLWWAouSlv81eiEEjKuJY/edit?usp=sharing]
I also put it on the JIRA.  Please let me know if you have feedback on the JIRA.  Thanks!

Sure, I'll split it out the switch to classificaiton models in another PR & JIRA :)

Thanks!  I'll check back for updates

Ping.  Did you want me to check out the other PR (implementing Classifier) before this one?

Yah, that would be rad, its open at https://github.com/apache/spark/pull/7432 , I figured I'd rebase this one once 7432 goes in.

@holdenk I'd like to squeeze this in.  Would you be able to send an update in a few hours?  If not, I'd be happy to send a PR to your PR (but you would need to check it and merge it). Thanks!

I can totally get something out today, grabbing a taco but I'll get back to
you in a few.
On Saturday, August 1, 2015, jkbradley<EMAIL_ADDRESS>wrote:

@holdenk https://github.com/holdenk I'd like to squeeze this in. Would
you be able to send an update in a few hours? If not, I'd be happy to send
a PR to your PR (but you would need to check it and merge it). Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/7205#issuecomment-126948075.

--
Cell :<PHONE_NUMBER>
Twitter: https://twitter.com/holdenkarau
Linked In: https://www.linkedin.com/in/holdenkarau

Build triggered.

Build started.

Test build #39386 has started for   PR 7205 at commit 3ebb2b5.

Test build #39386 has finished for   PR 7205 at commit 3ebb2b5.

This patch fails Scala style tests.
This patch does not merge cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: Param[Array[Double]] = new Param[Array[Double]](this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Build finished. Test FAILed.

Merged build triggered.

Merged build started.

Merged build triggered.

Merged build started.

Test build #39388 has started for   PR 7205 at commit 600316b.

Test build #39388 has finished for   PR 7205 at commit 600316b.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: Param[Array[Double]] = new Param[Array[Double]](this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test FAILed.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #39390 has started for   PR 7205 at commit 4ceeb9e.

Test build #39390 has finished for   PR 7205 at commit 4ceeb9e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: Param[Array[Double]] = new Param[Array[Double]](this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test FAILed.

@holdenk Thanks for updating this.  After you push more updates, I'd like to send a PR to your PR to update some items like docs and style, since we're pressed for time.

Merged build triggered.

Merged build started.

Test build #39399 has started for   PR 7205 at commit 4a37838.

Test build #39399 has finished for   PR 7205 at commit 4a37838.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: Param[Array[Double]] = new Param[Array[Double]](this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #39403 has started for   PR 7205 at commit d5b0a2f.

Test build #39403 has finished for   PR 7205 at commit d5b0a2f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: Param[Array[Double]] = new Param[Array[Double]](this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #39424 has started for   PR 7205 at commit 4b11041.

Test build #39424 has finished for   PR 7205 at commit 4b11041.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: Param[Array[Double]] = new Param[Array[Double]](this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test FAILed.

Right, I hadn't thought about that: This will require updating the PySpark implementation in the same PR since it calls the JVM Param get/set methods.

So I think the code freeze was yesterday right? I can try and fix it up today and see if it can go in the next RC if thats a chance.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

jenkins, retest this please.

Merged build triggered.

Merged build started.

Test build #189 has started for   PR 7205 at commit aa89af6.

Merged build triggered.

Merged build started.

Test build #189 has finished for   PR 7205 at commit aa89af6.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: DoubleArrayParam = new DoubleArrayParam(this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test FAILed.

Test build #39467 has started for   PR 7205 at commit aa89af6.

Test build #39467 has finished for   PR 7205 at commit aa89af6.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: DoubleArrayParam = new DoubleArrayParam(this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #39470 has started for   PR 7205 at commit a7dc7b5.

Test build #39470 has finished for   PR 7205 at commit a7dc7b5.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: DoubleArrayParam = new DoubleArrayParam(this, "thresholds", "thresholds in multi-class classification prediction, must be array with size of classes.")

Merged build finished. Test PASSed.

@holdenk In the interests of time, do you mind if I push a PR to update this before merging?

@jkbradley sure if you think it would be faster and the window is closing.

@holdenk Please let me know if the PR I sent to you looks OK.  Thanks! [https://github.com/holdenk/spark/pull/1]

@holdenk Would you mind closing this PR now that the copy was merged?  Thanks!


Upgrade Vagrant Manager.app to v2.5.4

Thank you for the contribution. It was merged directly as 8ae507494393870c3ba8e1770c3b99c01729ad73 to keep commit history cleaner. Your contribution is still credited to you.


Questions about the Iterative Bounding Box Refinement based on the Single-Stage pipline

Hi.
As mentioned in A.4 in your paper, the center coordinates (x, y) and dimensions (w, h) of the box both will be refined iteratively, and the initial box is set with b_w=0.1 and b_h = 0.1.
https://github.com/fundamentalvision/Deformable-DETR/blob/11169a60c33333af00a4849f1808023eba96a931/models/deformable_detr.py#L172
In the code, under the single-stage setting (two_stage=False), the reference.shape[-1] seems to be 2 consistently, including only the center coordinates, which indicates that only the center coordinates are refined iteratively. The dimensions of the box seem to be independently predicted among decoder levels, which is inconsistent with the paper and really puzzles me.
I will be very grateful if you can give me some hints.

Hi，you can refer to these lines.

Hi, I also have problem understanding that part. Specifically, in the case in witch the reference points are computed by a linear projection of the query embedding (two_stage=False) the predicted centers are refined iteratively. However, I don't understand the need to detach the new reference points, this would lead to no gradient to update the embeddings. Am I wrong? I would appreciate any hint

did you figure out the reason? im also stuck here


error messages not showing

ADD ISSUE DESCRIPTION HERE
(CS50 SPECIFIC)
when I use the make function it doesn't tell me any syntax errors
Version: 1.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>
Embedder: codespaces

Please use your CS50 course support channel
/question

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


Home

If you are reporting a bug, please fill in below. Otherwise feel free to remove this template entirely.
Description
What are you reporting?
Expected behavior
Tell us what you think should happen.
Actual behavior
Tell us what actually happens.
Environment
Run these commands in the project folder and fill in their results:

npm ls react-scripts (if you haven’t ejected):
node -v:
npm -v:

Then, specify:

Operating system:
Browser and version:

Reproducible Demo
Please take the time to create a new app that reproduces the issue.
Alternatively, you could copy your app that experiences the problem and start removing things until you’re left with the minimal reproducible demo.
(Accidentally, you might get to the root of your problem during that process.)
Push to GitHub and paste the link here.
By doing this, you're helping the Create React App contributors a big time!
Demonstrable issues gets fixed faster.

@cpojer This issue looks like it is just the default bug template with no details. It should probably be closed.


Camperbot is down

Camperbot is down across all the chat rooms since today (09/20), that I know of. Just FYI.

this problem is solved.


is support hdc device command ?

adb shell
hdc shell
hdc is openharmony sdk tool like adb

Short answer: No.
HarmonyOS is Android and still works with adb.
Why not?

Short answer: No. HarmonyOS is Android and still works with adb. Why not?

OpenHarmony develop board is not supporte adb command but use hdc command communication with PC

I don't know hdc, but if it behaves exactly like adb (for example hdc devices with the same output), then you can just set the environment variable ADB=hdc and run scrcpy.

Oh! I misunderstood, you meant OpenHarmony and not HarmonyOS. as far as I know, OpenHarmony can't run Android apps and the Scrcpy server relies on the Android SDK. so even if the hdc command is supported, it still doesn't make much sense. I personally recommend you to refer to the scrcpy implementation (refer to Develop.md) to implement your own server that can be used for OpenHarmony.

I developed a screening tool called OHScrcpy to support Openharmony (3.2+). It's just that the name is similar to Android Scrcpy, and the development technology and implementation methods are completely different. Temporarily close the source but provide software installation packs for free.
Video demonstration:

OHScrcpy 1.0 beta1: https://www.bilibili.com/video/BV1xz4y1q7S1
OHScrcpy 1.0 beta2: https://www.bilibili.com/video/BV1W14y1o75Y
In the future...

Software download:

https://www.bilibili.com/read/cv24125018

@westinyang dear westinyang, how to download your tool outside of China? Both links in your article lead to cloud storages which allow download only after registration. At the same time it's impossible to register there without chinese phone number :(

@ruperson All right, I uploaded another copy to Google Drive, I hope it can help you, download link: https://drive.google.com/drive/folders/1cVjr_pZO99C0Al20g7tV6CYrAsx63c5U?usp=drive_link
Also, I'm curious, what model of OpenHarmony device are you using now?

I developed a screening tool called OHScrcpy to support Openharmony (3.2+). It's just that the name is similar to Android Scrcpy, and the development technology and implementation methods are completely different. Temporarily close the source but provide software installation packs for free.
Video demonstration:

OHScrcpy 1.0 beta1: https://www.bilibili.com/video/BV1xz4y1q7S1
OHScrcpy 1.0 beta2: https://www.bilibili.com/video/BV1W14y1o75Y
In the future...

Software download:

https://www.bilibili.com/read/cv24125018

It seems that only Windows version is available, is there a MacOS version?

I developed a screening tool called OHScrcpy to support Openharmony (3.2+). It's just that the name is similar to Android Scrcpy, and the development technology and implementation methods are completely different. Temporarily close the source but provide software installation packs for free.
Video demonstration:

OHScrcpy 1.0 beta1: https://www.bilibili.com/video/BV1xz4y1q7S1
OHScrcpy 1.0 beta2: https://www.bilibili.com/video/BV1W14y1o75Y
In the future...

Software download:

https://www.bilibili.com/read/cv24125018

大佬未来有支持macOS的计划吗

@sheng-di Because it is a beta version, we are not considering developing a multi-platform version yet.

Open source will make it better.


Removed pedantic

flutter test
00:13 +3: TransformerPageView controller
===================build:0
00:13 +4: All tests passed!

solves #2

Thank you for your contribution !


Fix warnings #2

Many of warnings are fixed.
Some of them are trivial, but others can lead to crashes.
Check these commits, please.

Good job, thanks for contribution! Reviewed and approved.
Only one small question - see diff comments

Ты заходи, если что..

Good job, thanks for contribution! Reviewed and approved.
Thank you for this great project!

Only one small question - see diff comments
Just answered there.

Ты заходи, если что..
Хорошо )

I still can't fix the last warning from Analyzer about +0 retains count.

I still can't fix the last warning from Analyzer about +0 retains count.

Now fixed in f5346137caf0d23577ee0f74b397752de98a2c96


Fix disabled problem for Radio, Checkbox, Checkbox List & Toggle

This commit wants to fix Radio, Checkbox, Checkbox List & Toggle that can't be disabled.

[x] Changes have been thoroughly tested to not break existing functionality.
[x] New functionality has been documented or existing documentation has been updated to reflect changes.
[x] Visual changes are explained in the PR description using a screenshot/recording of before and after.

Isn't this a Livewire bug in v3? Should we really have to implement hacks in the Filament codebase like this? 🤔

Would be great if you just made a failing test PR to Livewire instead

Closing this as there's more places that need to be handled.
Agree with Dan that this should be fixed in Livewire.


Document deletion of default GCP permissions

Document deletion of default org-wide permissions in one-time setup doc.

LGTM


Is it possible to connect to 9i ?

Hi!
Thanks for the good work, i use it on various oracle DB we have, but we have one legacy DB, Enterprise Edition Release <IP_ADDRESS>.0. I tried with hello_ora v1  but got "Can't open connection: the packet received is not data packet."
I know it is not a good situation running 9i in 2022, but just curious on this driver is tested on it or if there is some trick to make it work ?

use v1
before 10.2 use v1

do you have any problem?

Well, as i said i use v1 but still got "Can't open connection: the packet received is not data packet". I have compiled to both 386 and x64 wihout luck. I was using the "hello ora" go program in examples with correct connection string as argument. I have a trace log, showing some write/read op and that i cant connect but not proceed. Is it safe to public upload part of that log seems to include lots of connection details ?

please note that I don't regularly upgrade v1 as v2 so may the connection need some feature that I don't add
so can you share log file so I can know what is the problem

did issue resolved ?

We have the same problem with usql. We can not connect with usql to an Oracle 9i database because as you said it uses the v2 driver. Can i somehow use v1 with usql or build usql with v1 of your driver?

I built the usql with your go-ora v1. I can connect to Oracle 10 Databases but still i can not connect to Oracle 9i. I get the same message.
error: the packet received is not data packet

now you can connect to oracle 9 using v1.3.1


Update completionCertificate.md

incorrect link replaced with the correct one

@waghmaredb  Approved! Great catch and thank you so much for making the update!!!


Module not found

Error: Can't resolve 'core-js/modules/web.dom.iterable'

Any suggestions on where to start to solve this?

https://github.com/zloirock/core-js/issues/500 looks like this requires a core-js update


Dependancy on algolia

Describe the bug
When doing npm install flowbite-svelte you got lack of algoria warning. algolia is used for docs site but should not be needed for package.
 WARN  Issues with peer dependencies found
.
└─┬ flowbite-svelte 0.35.3
  └─┬ @docsearch/js 3.3.4
    └─┬ @docsearch/react 3.3.4
      └─┬ @algolia/autocomplete-preset-algolia 1.8.2
        └── ✕ missing peer @algolia/client-search@">= 4.9.1 < 6"
Peer dependencies that should be installed:
  @algolia/client-search@">= 4.9.1 < 6"

Reproduction
N/A
Flowbite version and System Info
System:
    OS: Linux 6.2 Arch Linux
    CPU: (8) x64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
    Memory: 8.43 GB / 15.50 GB
    Container: Yes
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 19.9.0 - /usr/bin/node
    Yarn: 1.22.19 - /usr/bin/yarn
    npm: 8.19.2 - /usr/bin/npm
  Browsers:
    Chromium: 113.0.5672.92
    Firefox: 113.0
  npmPackages:
    @sveltejs/kit: ^1.5.0 => 1.16.3
    flowbite-svelte: ^0.35.3 => 0.35.3
    svelte: ^3.54.0 => 3.59.1
    vite: ^4.3.0 => 4.3.5

Yes, we need to move   "@docsearch/js": "^3.3.4", to devDependencies.

I just moved it to devDependencies.


Blog Post:  Working Groups in admiral

Blog Post
Discuss:

Argument Aligning
Date/Time Rework
Lab Working Grou
IG Review
Environment handling
Blogging!
?

I think this was closed in error @federicobaratin

Hi @bms63!
Could you please provide more info on it? I have not understood well what happened

oh i am sorry @federicobaratin - I meant @manciniedoardo.  For some reason I confuse you both in my brain when doing @

Yeah looks like the wrong issue was mentioned in the PR - sorry for not spotting!


Update baseimg from nvidia/cudagl to nvidia/cuda

The Docker image nvidia/cudagl has been deprecated and replaced with nvidia/cuda. The new image has the updated cuda repo signing key so that sudo apt update works, but deprecates some tags: see the Announcement section of https://hub.docker.com/r/nvidia/cuda for more details, and #276 for some context.
What I did is replace every instance of cudagl with cuda in the codebase.
References

New cuda image: https://hub.docker.com/r/nvidia/cuda
Original/deprecated cuda image: https://hub.docker.com/r/nvidia/cudagl

I wonder what do we do with nvidia/opengl...

WRT CI failure, looks like we hit https://github.com/docker/docker-py/issues/3113

Thanks @patrick-5546

Could you please rebase onto latest master branch, so that CI tries to run again?

@patrick-5546 I seem to be getting issues with it not finding a suitable Vulkan surface renderer when it tries to bring up the editor interface. It compiles the shaders fine but after that it fails.
Have you run 5.0+ with the CUDA base image?

Okay so there is no vulkan support in the CUDA image.

This is my attempt at a fix:
https://github.com/Greenroom-Robotics/ue4-docker/commit/b8bd15277930d7bc35ba5f8b1233be04009caddc

Edit: I found we have to do the following apt install https://gitlab.com/nvidia/container-images/vulkan/-/blob/master/docker/Dockerfile.ubuntu#L28 to get it to report the vulkan devices properly.

I believe I also had to install vulkan-utils to get it working on ue4.

Edit: I found we have to do the following apt install https://gitlab.com/nvidia/container-images/vulkan/-/blob/master/docker/Dockerfile.ubuntu#L28 to get it to report the vulkan devices properly.

I believe I also had to install vulkan-utils to get it working on ue4.

Okay good to know. Maybe I will make a PR for this. Now called vulkan-tools.


[Event Request] Application “Tests-Graph”, Codeunit 135514 "Sales Order Line E2E Test"

[Event Request] Application “Tests-Graph”, Codeunit 135514 "Sales Order Line E2E Test"

Could you please insert the OnTestInitialize Event at the beginning of the procedure Initialize?

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Update common to support credential types

Fix #5107
Signed-off-by: Julien Pivotto<EMAIL_ADDRESS>

It seems that I am only using authorization when refering to the option name or the header name. I guess your concern is then addressed.


Invalid hex chars

Added missing check for digit characters being equal to '0' or greater. As the used way of tightly coupled SWAR testing of character being is around byte range, some character from upper half of ASCII were considered as valid also not filter by existing checks and thus check for characters being less or equal to '9' added also.
There may be better way - smaller number of operations - for testing hexadecimal characters after this change.
There were some troubles with little / big endian integer encoding, it should be verified whether they do not occur on other platform than tested - Intel.

Thank you very much for providing a fix for this issue. 😀
Based on your merge request, I have now commited a fix that uses one operation less. I made multiple commits to the main branch. The most significand was probably this one: a67caba534d5bd7eab05e02220da746da8d99db7


Aplying force while on the ground causes lag spikes

Activating engines (main or hover), rolling on the ground (no engines) or even rcs (rot or lin) causes the sim to get very low fps for about 6 seconds and then it recovers its normal functioning. I tested it both in the moon and in earth, both with the same results. The low fps will also affect if you are not focused on that vessel in particular. For example, I was on a dragonfly in orbit and still got low fps when the dg on earth crashed and started touching the ground

I've seen this issue before. I'm currently investigating.

I remember seeing this problem a while ago, but I haven't been able to reproduce it with the OrbiterSkyboltClient_1_0_2_Win64 release. Is this the version you're using? I think the problem may have something to do with collision detection against Orbiter's quadtree terrain. What is the git SHA of the orbiter version you're testing with? I'm using 351248aea746c3611e5c8e29d22da8755257514d
As a test, try disabling "Surface elevation" in Orbiter's Visual Effects tab.

I dont really know how to get the git sha on visual studio 2019 (pretty new with it) but I built it 5th August, so it says v.20220805 in the launcher.
As per the problem itself. I can confirm that cubic interpolation seemed to be the problem. I tried linear and disabling surface elevation altogether and it got rid of the lag. But plot twist! when I turned cubic interpolation back on just to confirm, the fps drop didnt return. Closed the launcher and opened it again (with cubic activated) and still normal fps. So it seems that just changing the surface elevation setting got rid of the lag?

The Orbiter version you're using is similar to what I'm testing on which is good. It sounds like there's a bug either in the skybolt plugin or in Orbiter itself, but it only causes problems intermittently. I'll investigate further if I can reproduce the issue again in the future.

Will try to reproduce it on my end. Maybe it was because, when I first compiled OpenOrbiter (and added Skybolt), I launched the simulation for the first time with cubic interpolation activated. But I think this issue its not as important as it is intermittent and it looks like its easily fixable by changing the surface elevation type


DRILL-6747: Fixed IOB in HashJoin for inner and right joins on empty probe side

Fixed IOB in HashJoin for inner and right joins on empty probe side.
Documentated expected behavior of RecordBatch after returning NONE.
Made UnorderedReceiver obey contract after returning NONE.

@Ben-Zvi


Tokens count overmuch fixed

When we set change_headers_on_each_request to false it is possible to get an unlimited count of tokens and max_number_of_devices is ignoring.
In a casual case - it's not a problem because we remove the token on sign_out. But if your application is API - nobody uses sign_out.

@JerryGreen - tests are failing on bundle install. can you rebase this PR branch to exclude the Gemfile change? I'd definitely take a dependency update with passing tests in a separate PR if it helps.

Did it.
Why don't you describe a certain version for every dependency?

thanks @JerryGreen !


Feat upgrade packages

It upgrades packages and adds breaking changes from package next-mdx-remote, you can read more at next-mdx-remote/releases/tag/3.0.0.

Thanks, happy to upgrade next-mdx-remote to v3, but there seems to be an error in building.
Here's the error message from vercel:
21:29:08.391	Error occurred prerendering page "/blog/code-sample". Read more: https://nextjs.org/docs/messages/prerender-error
21:29:08.391	TypeError: (0 , external_next_mdx_remote_.serialize) is not a function
21:29:08.391	at getFileBySlug (/vercel/path0/.next/server/pages/blog/[...slug].js:575:66)
21:29:08.391	at getStaticProps (/vercel/path0/.next/server/pages/blog/[...slug].js:3845:51)
21:29:08.391	at async renderToHTML (/vercel/path0/node_modules/next/dist/next-server/server/render.js:28:1689)
21:29:08.391	at async /vercel/path0/node_modules/next/dist/export/worker.js:26:6
21:29:08.391	at async Span.traceAsyncFn (/vercel/path0/node_modules/next/dist/telemetry/trace/trace.js:6:584)
...
You can try building it locally with npm run build and verifying that it works on your side.

Fixed. The import was wrong, my bad.


Allow a way to disable update-notifier

Operating System: Linux
Node Version: 8.9.1
NPM Version: n/a
webpack Version: 4.8.1
webpack-command Version: 0.2.0

This issue is for a:

[ ] bug
[x] feature request
[ ] modification request

Code
CLI Command
I run build steps under a containerized filesystem sandbox (this is for the Bazel build which does this to enable remote build execution.)
I suspect that's why any execution of webpack-command prints
┌──────────────────────────────────────────────────────────────────────────────┐
│                     webpack-command update check failed                      │
│                     Try running with sudo or get access                      │
│                     to the local update config store via                     │
│ sudo chown -R $USER:$(id -gn $USER) /usr/local/google/home/alexeagle/.config │
└──────────────────────────────────────────────────────────────────────────────┘

Expected Behavior
Either update-notifier should be quiet when it's running in a context where it can't work (not sure if feasible)
or webpack-command would let me disable this output, either directly or via --log-level or --reporter
Actual Behavior
Always get this ugly error for any build step that runs webpack-command
How Do We Reproduce?

Install Bazel
Clone https://github.com/alexeagle/rules_nodejs/tree/webpack
bazel build internal/webpack/test

Thanks for the issue 🍺
This is one of those sticky wickets that falls into the opinionated category. If you can convince npm to allow disabling their update notice, I'll follow suit. Until then, I'm afraid stays. FWIW, we're using the same package for this as npm. I'm gonna tag this won't fix and waiting on upstream in the event they've introduced a configuration option to disable that, or you manage to convince them to that effect :smile:

But it's not npm doing this behavior, there's an explicit call here
https://github.com/webpack-contrib/webpack-command/blob/master/lib/index.js#L13
which I imagine being guarded
On Fri, May 11, 2018 at 4:59 PM Andrew Powell<EMAIL_ADDRESS>wrote:

Thanks for the issue 🍺
This is one of those sticky wickets that falls into the opinionated
category. If you can convince npm to allow disabling their update notice,
I'll follow suit. Until then, I'm afraid stays. FWIW, we're using the same
package for this as npm. I'm gonna tag this won't fix and waiting on
upstream in the event they've introduced a configuration option to
disable that, or you manage to convince them to that effect 😄
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/webpack-contrib/webpack-command/issues/17#issuecomment-388513377,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAC5I-fQnuqKOfaRU9uzz2dVutr9WMaiks5txiXXgaJpZM4T8KIb
.

You may have missed my point there. I'm not saying that npm is performing that check. I'm saying that webpack-command (as well as webpack-serve) uses the same method and module that npm does to perform its update check. Keeping users apprised of new versions is a good thing, and it outweighs the inconvenience of an extraneous log message in environments where it isn't necessarily needed. The same can be seen when running npm in a CI environment. Providing an option to disable the feature is not something that npm does, and it's not something that webpack-command does at this time.

One can disable "check for updates" by adding an environment variable
NO_UPDATE_NOTIFIER

or you can pass --no-update-notifier in cli
https://github.com/yeoman/update-notifier#user-settings

Closing citing comment by @ankurk91