Native Notebooks - Changing kernel causes markdown to flicker, then disappear

VS Code Version: 1.57.0 & 1.57.0-insider

Steps to Reproduce:

Open notebook
Change kernel - markdown will flicker
Change kernel again - markdown disappears
This behavior continues every other kernel switch

The way I reproduced this issue is

create a code cell
change it markdown
double click to edit
escape
the markdown cell is blank

notebookWebviewPreloads.js:3 Uncaught (in promise) Error: Could not find renderer
    at Object.render (notebookWebviewPreloads.js:3)
    at K.updateContentAndRender (notebookWebviewPreloads.js:3)
    at new K (notebookWebviewPreloads.js:3)
    at Object.createMarkupCell (notebookWebviewPreloads.js:3)
    at notebookWebviewPreloads.js:3
    at Array.map (<anonymous>)
    at Object.ensureMarkupCells (notebookWebviewPreloads.js:3)
    at notebookWebviewPreloads.js:3

https://github.com/microsoft/vscode/issues/126056#issuecomment-859695620 this might be different from the original issue

@connor4312 I suspect this may be from 7c226ae15584cbf1cc62d328c489ab40cc3d33c6 (or related followup changes) but am still debugging. Any ideas off the top of your head?

Definitely related to some state not being preserved well between reloads, but I don't know what specific problem it could be off the top of my head.

Actually seem to making renderer async. Seems fixed with 3086bb5956b5161b0c22cd71c13427773be834be but I need to test a bit more and then back port to 1.57

Let me know if you still see this in the next insiders build

@rebornix while following https://github.com/microsoft/vscode/issues/126056#issuecomment-859695620, the markdown cell isn't blank, but when I change the code cell to a text cell in a github issues notebook, I see the message No renderer found for "text/plain" a.

I can still repro the original issue with the same steps.
The markdown shows up again after step 4 if one scrolls down and back up.

I can't reproduce this with a simple Jupyter notebook
@rzhao271 Can you please test using the latest insiders. If you still see this, please share the notebook you are using

Also getting this same issue with July 2021 (version 1.59.0-insider), but its happening in a notebook I can't share for confidentiality purposes. I tried reproducing this in a blank notebook with the goal of being able to share it, but I wasn't able to reproduce the issue.

Marking as verified, as I'm unable to repro the issue on my notebook, now. Feel free to reopen this issue or create a new one if there's a notebook you're seeing the issue with that you're able to share.


Add version 4.1.1 to gh-pages

Updates links and adds API reference for v4.1.1

Linux test FAILed.

Windows test FAILed.


Update kb.py

@CodiumAI-Agent /review

@CodiumAI-Agent /review

PR Reviewer Guide 🔍
Here are some key observations to aid the review process:

⏱ Estimated effort to review: 2 🔵🔵⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review
Type ConsistencyThe PR changes the import of Dict to dict for type annotations. Ensure that this change is consistent with the project's Python version requirements and coding standards.


error validating ClusterServiceVersion: unknown escape character

When trying to update our operator to the latest released version, I noticed the examples of our current version seem to work on the live site, but they fail make operator.test currently with an error that it cannot parse the alm-examples. This is against current master for an already released version:
✔ ~/dev/go/src/github.com/community-operators [master|✔]
09:53 $ make operator.test OP_PATH=upstream-community-operators/elastic-cloud OP_VER=1.0.1
Pulling docker image                              [  Processing  ]
Pulling docker image                              [  OK  ]
KIND cluster auto-creation                        [  selected  ]
Start KIND                                        [  Processing  ]
Start KIND                                        [  OK  ]
Building catalog image                            [  Processing  ]
Building catalog image                            [  OK  ]
Creating namespace                                [  Processing  ]
Creating namespace                                [  OK  ]
Lint operator metadata                            [  Processing  ]
Lint operator metadata                            [  OK  ]
Install OLM                                       [  Processing  ]
Install OLM                                       [  OK  ]
Building manifests                                [  Processing  ]
Building manifests                                [  OK  ]
Operator Deployment                               [  Processing  ]
    Applying object to cluster                    [  Processing  ]
    Applying object to cluster                    [  OK  ]
    Checking if subscriptions passes              [  Processing  ]
    Checking if subscriptions passes              [  OK  ]
    Checking if CSV passes                        [  Processing  ]
    Checking if CSV passes                        [  OK  ]
    Ensuring CSV stays alive                      [  Processing  ]
    Ensuring CSV stays alive                      [  OK  ]
    Checking if CSV stayed alive for 60 secs      [  Processing  ]
    Checking if CSV stayed alive for 60 secs      [  OK  ]
Operator Deployment                               [  OK  ]
Instrumenting Operator for test                   [  Processing  ]
    creating CR files                             [  Processing  ]
    creating CR files                             [  OK  ]
    injecting scorecard proxy                     [  Processing  ]
    injecting scorecard proxy                     [  OK  ]
    waiting for CSV to update                     [  Processing  ]
    waiting for CSV to update                     [  OK  ]
Instrumenting Operator for test                   [  OK  ]
Running scorecard trough all supplied CRs         [  Processing  ]
    Running required tests                        [  Processing  ]
time="2020-05-12T15:01:59Z" level=debug msg="Debug logging is set"
time="2020-05-12T15:01:59Z" level=info msg="Using config file: /tmp/scorecard-bundles/isvrvghykk.bundle.yaml"
time="2020-05-12T15:01:59Z" level=error msg="Plugin `Basic Tests` failed with error (error validating ClusterServiceVersion: Error: Value error converting YAML to JSON: yaml: line 3: found unknown escape character: error decoding example CustomResource\n)"
time="2020-05-12T15:01:59Z" level=error msg="Plugin `OLM Integration` failed with error (error validating ClusterServiceVersion: Error: Value error converting YAML to JSON: yaml: line 3: found unknown escape character: error decoding example CustomResource\n)"
	Basic Tests
	CR:
	Labels:
	Errors:
		plugin error
	Log:
		error validating ClusterServiceVersion: Error: Value error converting YAML to JSON: yaml: line 3: found unknown escape character: error decoding example CustomResource
:
Logs:

	OLM Integration
	CR:
	Labels:
	Errors:
		plugin error
	Log:
		error validating ClusterServiceVersion: Error: Value error converting YAML to JSON: yaml: line 3: found unknown escape character: error decoding example CustomResource
:
Logs:
    Running required tests                        [  FAILED  ]
make: *** [Makefile:85: operator.test] Error 1
make: *** [operator.test] Error 2

What's also odd is that the linting does not catch it:
10:02 $ make operator.verify OP_PATH=upstream-community-operators/elastic-cloud OP_VER=1.0.1
Pulling docker image                              [  Processing  ]
Pulling docker image                              [  OK  ]
Lint operator metadata                            [  Processing  ]
Lint operator metadata                            [  OK  ]

I would expect that this would not work on the website if it fails the test. I also would expect that a formatting error could be caught in the verify step rather than the full test. Happy to help contribute to a fix, but right now I'm a bit confused about why this is working live but not in the test. It's also odd to me that this made it into master but fails now, I assume the test was modified without the new test being run against existing versions?
For what it's worth I worked around this in the update by using literals and not escaping.

Hi @anyasabo, alm-examples are useful for users. But it does not have effect on functionality. Sometimes secret is missing or something which cannot be tested automatically. We do not use scorecard tests from test pipeline, but it is active for local testing. So you can ensure better operator quality.

@J0zi okay understood that the tests so not run as part of CI. I am still a bit confused why it seems to display appropriately on the website but fails the local test, can you help me understand?


chore(deps): update devDependencies

Coverage remained the same at 88.301% when pulling 250e9a3db01f91e0e0bfe8b7784980a2bf642091 on devDependencies into 5384dcfab6e5d565b97b2ff5d6cac3209aada6e8 on master.


Want to enhance the design for create test page

I want to enhance the design of the Create test page

Can I work on this issue?

@Ayushmaanagarwal1211 you can work on this.

@marvelxcodes , you can work on other issues in the meantime.

@Ayushmaanagarwal1211 , any updates?

@Ayushmaanagarwal1211 , I am removing you from this issue.

@marvelxcodes and others are welcome to work on this.

@vishalverma9572 Please assign it to me ...i ensure you that within a week a best UI will be infront of UI and promise you will love it

@Anurag-singh-thakur , You seem very energetic! I am assigning this issue to you. Please make sure to follow our code structure and UI theme as much as possible. If you face any issues, feel free to let me know.

@Anurag-singh-thakur , You seem very energetic! I am assigning this issue to you. Please make sure to follow our code structure and UI theme as much as possible. If you face any issues, feel free to let me know.
Ok thanks for Assigning it to me

@vishalverma9572 Bro there are errors in backend can you please fix that as i am registering for the first time it is showing that users already exist....and fot the create test ui i need to first register ..so please fix this . attaching screenshot for your better understanding

@Ayushmaanagarwal1211, Do you have MongoDB installed?

@Ayushmaanagarwal1211, If this issue persists, please let me know.

@Ayushmaanagarwal1211, Do you have MongoDB installed?

brother i have told you the issue you are replying to wrong person..yes i have installed the mongoDB


Use saneyaml instead of yaml

saneyaml is maintained by us (nexB) and it makes sense to update all the importers to use it instead of yaml.
Files currently using yaml:

importers/suse_backports.py
importers/elixir_security.py
importers/istio.py
importers/mozilla.py
importers/alpine_linux.py
tests/test_alpine.py
tests/test_suse_backports.py
helpers.py

@pombredanne  is there any advantage of using saneyaml over standard yaml . AFAIK there is yaml.safe_load , we really don't do nything else with it here.

After discussion with @pombredanne  I'm convinced that yaml is insane, and there is value in using  saneyaml .

@sbs2001 imho, if you could post that conversation here, it would be very helpful for future contributors.

Rationale:
>>> yaml.load("phil: yes")
{'phil': True}


Lambda NOT recognizing/loading src.zip files

When I browse to the repos "lambda/src" directory containing the src.zip file the lambda function zip upload does NOT see the *.zip file which is 4k. I've made sure I am in the correct directory and tried multiple "zip" programs.  Any idea what's up?

Never mind, too tired I guess.  Happy Holidays

Did you get this to work in the end? I get the same problem. Upload files but it says "too many files zip file" even though its just those 3 files needed?
Anyone?


Module called "LevelUp" to use Lucky egg when enough evolutions to level up available

Trying to store pokemon in order to use a lucky egg and perform bulk evolutions. Want to understand how I can perform this using some configuration in config.json.
Essentially, if i have 36 Pidgey candies, bot should let 3+ pidgey be. If 60 pidgey candies, let 5+ pidgey be.
Can someone help out with this kind of config? This can help ensure that i get the most out of my lucky egg in one go.

#2780

@brambi this has nothing to do with that please delete your comment.
And @pranavperfect please use the template for making an issue.

@nivong I believe @brambi just wants to tell me to read 2780 which refers to an update in the wiki being an upcoming task and not an immediate task. And i understand that. Which is why you guys can close it and I can comment on it later after the wiki is updated.

@pranavperfect that issue where brambi was linking to has to do with the new encrypted updates and how to run the new bot ;)
Your "issue" isn't an issue it's a #newfeature.

Here is the detailed description of the new feature:
Just like we have modules for catching pokemon and evolving pokemon, if there could be a "level up" module which would act as follows:

Calculate XP required to new level ==> XP required for next level - XP present
Count number of Pidgey+Weedle+Caterpie in inventory available for level up
Calculate possible XP earned if evolved using lucky egg (2500no. of evolutions)
*Not taking into account XP earned from catching pokemon and swiping pokestops
If Possible XP earned >= XP required for Level up

Pause all other activity
Start Lucky Egg
Evolve Pidgey, Weedle and Caterpie
After leveling up, keep strongest by CP or IV as set in config file
Resume regular activity

Else, continue catching pokemon and re-check after x mins

For step 2 to happen, bot needs to catch and release weak pokemon such that
weak pokemon in inventory = (candy/12)+1
So if there was 60 Pidgey candy, there should be 6 Pidgey in inventory.
weak pokemon should not be governed by the keep_best_cp/iv rule.

@nivong please let me know if this is enough details.

And again, this will not be an "always on" feature since lucky eggs are limited.

@pranavperfect: in your release section, include settings like this:
"Caterpie": { "keep_for_evo": true },
"Weedle": { "keep_for_evo": true },
"Rattata": { "keep_for_evo": true },
"Zubat": { "keep_for_evo": true },
"Pidgey": { "keep_for_evo": true },

When you are ready you can add a task like:
{
        "type": "EvolvePokemon",
        "config": {
            "evolve_all": "Pidgey,Rattata,Weedle,Tentacool,Zubat,Ekans,Psyduck,Spearow,Caterpie",
            "first_evolve_by": "cp",
            "evolve_above_cp": 100,
            "evolve_above_iv": 0.1,
            "logic": "or",
            "evolve_speed": 20,
            "use_lucky_egg": true
        }
      }

YMMV, but this seems to work well for me (on latest dev branch)

@mousetree - First of all, the script does not display XP/stats periodically which i can monitor and be like "Hey i can level up now because i have enough evolutions etc.". Secondly, This would require me to keep changing my config whereas that is a module which actively monitors my possible evolutions and my required evolutions and then do it auto-magically. I'm just trying to have least restarts.
@nivong - Can we not display the stats periodically which are displayed only when the bot is stopped?
It would be helpful to know how we are progressing.

Please move your feature request/s to our feature hub - http://feathub.com/PokemonGoF/PokemonGo-Bot

https://github.com/PokemonGoF/PokemonGo-Bot/issues/3843#issuecomment-239708680

Done to an extent. Please reopen and expand if not.

I don't see the option? Do we have a wiki for it? Can you please explain where this feature has been added?

https://github.com/PokemonGoF/PokemonGo-Bot/commits/master

@nivong  i don't understand how the commit helps. I can't find any reference to my feature request in the commits.

Level up thing definitely doesn't work. Or i don't know how to make it work. some guidance is required.

@pranavperfect reopened for you :)

@k4n30 Thank you! I couldn't find a way to open it!
@mjmadsen mentioned that this feature has been built into the bot. But i don't see it happening. Is there some configuration that needs to be done for it?

@pranavperfect Sorry, I misread the wants. My bad!

@mjmadsen the config.json.optimizer.example has some content which relates to what i'd asked. but it is asking the user to tell how many evolutions are needed etc. but what the module should do is keep hoarding pidgey, weedle and caterpie and other "common" pokemon for an area and then once enough to level up using lucky egg, then start evolving. also taking into account that in 30 minutes, you'd be able to do roughly 60 evolutions.

@mjmadsen is this still under development or has been disregarded?

I don't know if anyone is currently working on this. A lot of bug fixes and small improvements.
Everything you asked for seems to be in the bot except for taking in account exp to next level or what not. Personally, I don't see much value in it. Exp is exp.

I agree with @mjmadsen . Exp is exp. No need to something like this.


Update the generated etcd ca command

The command to generate the certificate in the Chinese document is incorrect, which prevents the certificate from being generated. The correct command is "kubeadm init alpha phase certs etcd-ca"

I signed it

I signed it

/assign @haibinxie


Add License, Makes GitaJob open source!

deke left, deke right, half clapper top chedder. Open this baby up


GH2303: Use .NETCoreApp instead of .NETStandard

Fixes #2303

@mholo65 what is the state of this one?

@gep13 sorry, can't merge this until Cake.CoreCLR targets netcoreapp2.1.

@mholo65 is this now addressed by #2604?

Yes, fixed by #2604


This statement is misleading.

File: engine/release-notes.md
Customers have reported they have tried to set up multiple logging drivers because of this statement.
This should be reworded to specify that it is a feature of the docker logs command, not for multiple drivers.

@kavikat Could you please be more specific on which statement? Thanks.

“Add support for multiple logging drivers for docker logs.” <- bad (misleading statement)
"Added functionality for the docker logs command to include the output of multiple logging drivers." <- better (more specific)


StackOverflow with continue from try..except

From @ironpythonbot on December 9, 2014 18:8
We are running IronPython 2.7.3. We have been getting a StackOverflow error,
which we have reduced to the attached program. It only crashes when run under
ipy64, without -X:Debug.
The crash is very easy to make go away, with seemingly innocuous modifications
to the program, and different builds of IronPython 2.7.3 (e.g. a debug build)
produce different behavior and the program will need some modification in
order to exhibit the crash. I have never seen the problem with ipy.exe, only
with ipy64.exe.
But if I put this program, excon1.py, in my C:\Program Files (x86)\IronPython
2.7 folder, start a command prompt in that folder and type
ipy64 excon1.py
I see...
Process is terminated due to StackOverflowException.
It doesn't go very far before overflowing the stack. On my machine I can
reduce the range(1000) to range(50) and still see the crash.
===excon1.py===
def f(j):
    raise Exception("test")

for j in range(1000):
    try:
        f(j)
    except:
        continue

print "finished"

Work Item Details
Original CodePlex Issue: Issue 34186
Status: Proposed
Reason Closed:  Unassigned
Assigned to:    Unassigned
Reported on:    Jun 20, 2013 at 10:17 PM
Reported by:    shacktoms
Updated on: Jun 25, 2013 at 10:31 PM
Updated by: shacktoms
Plaintext Attachments
CodePlex Issue #34186 Plain Text Attachments
Copied from original issue: IronLanguages/main#1070

From @ironpythonbot on December 9, 2014 18:8
On 2013-06-26 05:31:39 UTC, shacktoms commented:
I did some poking around and found that the problem seems to be this. The generated code for an except clause includes a "LeaveExceptionHandler" instruction. The code for the "continue" appears to create a branch that skips this instruction.
The result is that Interpreter.HandleException never returns to Interpreter.Run, but instead continues to execute the frame within its loop. Then, on the next iteration, the raised Python exception causes Interpreter.HandleException to call itself recursively.
The stack thus fills with recursive calls to Interpreter.HandleException.
I also found that this problem also exists in ipy.exe, perhaps I didn't see it earlier because its stack is effectively deeper (maybe this is because the stack frames are smaller).
Because I thought the problem might arise from the "goto nature" of "continue", and exception handling might be different, I tried a workaround using an exception handling equivalent to the "continue" statement. That is in excon3.py.
However, this didn't work, so it appears the problem is more pervasive than just "continue". A workaround using a flag, placing the continue outside the except, did work.
===excon3.py===
class Continue(Exception):
pass
def f(j):
raise Exception("test")
for j in range(1000):
try:
try:
f(j)
except:
raise Continue()
except Continue:
pass
print "finished"

If I had an idea where to start it would have been resolved. It's quite a complex issue and the proper resolution is not obvious. I suggest reading through related issues, for example:
https://github.com/IronLanguages/ironpython2/issues/40
https://github.com/IronLanguages/main/issues/1070
https://github.com/IronLanguages/main/pull/1167

Note to future self: to consistently reproduce the issue, set LightCompiler.DefaultCompilationThreshold = int.MaxValue.


How to capture 1 frame?

Hello, I want to render just one particular frame using bevy_image_export.
However, in this issue(https://github.com/paulkre/bevy_image_export/issues/1) there is only a way to start and stop capturing.
Any hint is welcome!

Hi, if you just want to export a single frame you might be better of using Bevy’s internal ScreenshotManager. Otherwise you would have to spawn an ImageExportBundle and then immediately despawn it in the subsequent frame.

Thanks for replying!
I used Bevy's ScreenshotManager, but I couldn't resize the result :(
Also I wrote the code to an ImageExportBundle and then immediately despawn it in the subsequent frame, but  save_buffer_to_disk() didn't stop. Is there any way?

So you’re saying, ImageExportBundle kept on exporting frames, even after you despawned the entity? Could you please send me the code of the systems you used?

Oh, I'm sorry. I made a mistake.
After I despawned, it crashed like this:
thread 'Compute Task Pool (1)' panicked at 'called `Result::unwrap()` on an `Err` value: NoEntities("bevy_ecs::query::state::QueryState<bevy_ecs::entity::Entity, bevy_ecs::query::filter::With<...::render::ExportBundleMarker>>")'
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Encountered a panic in system `...::render::save_image`!
thread '<unnamed>' panicked at 'The TimeSender channel should always be empty during render. You might need to add the bevy::core::time_system to your app.: "Disconnected(..)"', ./.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_render-0.11.0/src/renderer/mod.rs:91:44
Encountered a panic in exclusive system `bevy_render::renderer::render_system`!

My code is here:
#[derive(Component)]
pub struct ExportBundleMarker;

pub fn save_image(
    mut commands: Commands,
    mut export_sources: ResMut<Assets<ImageExportSource>>,
    output_texture: ResMut<TextureHandle>,
    input: Res<Input<KeyCode>>,
    export_bundles: Query<Entity, With<ExportBundleMarker>>,
) {
    if input.just_pressed(KeyCode::Space) {
        commands.spawn((ImageExportBundle {
            source: export_sources.add(output_texture.texture.clone().into()),
            settings: ImageExportSettings {
                extension: "exr".into(),
                ..default()
            },
        },));

        // after render
        commands.entity(export_bundles.single()).despawn();
    }
}

So I tried to use resource to change state after spawn, but save_buffer_to_disk() is on sub_app so it can't use world resource 🥲

The issue is that you are attempting to despawn the entity on the same frame you are spawning it on. You have to wait one iteration for Bevy to add the entity to the Query object (export_bundles). To address this, I made modifications to your code. Now, all entities with the ExportBundleMarker will be despawned on every frame. Consequently, the ImageExportBundle will exist for exactly one frame:
#[derive(Component)]
pub struct ExportBundleMarker;

pub fn save_image(
    mut commands: Commands,
    mut export_sources: ResMut<Assets<ImageExportSource>>,
    output_texture: ResMut<TextureHandle>,
    input: Res<Input<KeyCode>>,
    export_bundles: Query<Entity, With<ExportBundleMarker>>,
) {
    if input.just_pressed(KeyCode::Space) {
        commands.spawn((
            ImageExportBundle {
                source: export_sources.add(output_texture.texture.clone().into()),
                settings: ImageExportSettings {
                    extension: "exr".into(),
                    ..default()
                },
            },
            ExportBundleMarker,
        ));
    }

    for bundle in &export_bundles {
        commands.entity(bundle).despawn();
    }
}

You are currently exporting an HDR image (EXR), so please make sure to use TextureFormat::Rgba32Float as the format in your output texture’s image properties.

On top of that, you forgot to add the ExportBundleMarker to the entity holding the ImageExportBundle.

Wow it works! Thank you for your kind explanation :)
And yes, I forgot to add ExportBundleMarker 😂


Any changelog?

Recently gulp-if have updated to 2.0, I think maybe there is some breaking change, but couldn't find any changelog to see if I can upgrade my dependency safely.
Will there be a changelog or tag/release(helpfull too)?

Great idea.  I mostly bumped the major version because some dependencies bumped major versions, but the upgrade should be safe.  The only major functional change is it now matches on file.relative rather that the previous behavior of matching on file.path.

+1

+1 changelog please. Also, why aren't there git tagged versions?

@robrich add a changelog, at least "3.0.0: No breaking changes"

The only breaking changes were in dependencies. 3.0.0 now requires a
runtime that supports ES6.


No user feedback over BSP when there are version conflicts in library dependencies

steps

Create a hello-world project with sbt new scala/hello-world.g8
Open this project with Metals, ignore the prompt to import the build, and instead issues a "Metals Switch Build Server" Command (differs a bit per client)
Select sbt as your build server
Navigate to Main.scala and everything works fine, add something invalid, see diagnostics etc.
In your build add the following dep: libraryDependencies += "io.delta" %% "delta-standalone" % "0.4.0"
After saving you'll be prompted to re-import which will trigger a workspace/reload behind the scenes. This will work fine.
Again, navigate to Main.scala and everything will work fine
Now let's add another dependency libraryDependencies += "com.github.mjakubowski84" %% "parquet4s-akka" % "2.5.1"
Same process as before, answer the prompt to re-import which will trigger a workspace/reload. Now notice that everything from a users perspective seems fine. You don't get any errors forwarded to you and the workspace/reload didn't return an error either.
Navigate again to Main.scala and add something like val x: Int = "nope" and notice that no diagnostics are being forwarded.

problem
The problem here is that there is an issue with the build definition that is in no way forwarded to the user. The only way to see this would be if you looked in the trace logs and saw:
[Trace - 09:39:11 AM] Received notification 'build/logMessage'
Params: {
  "type": 1,
  "message": "java.lang.RuntimeException: found version conflict(s) in library dependencies; some are suspected to be binary incompatible:\n\n\t* com.github.mjakubowski84:parquet4s-core_2.13:2.5.1 (semver-spec) is selected over {1.2.1}\n\t    +- com.github.mjakubowski84:parquet4s-akka_2.13:2.5.1 (depends on 2.5.1)\n\t    +- io.delta:delta-standalone_2.13:0.4.0               (depends on 1.2.1)\n\n\nthis can be overridden using libraryDependencySchemes or evictionErrorLevel\n\tat scala.sys.package$.error(package.scala:30)\n\tat sbt.internal.LibraryManagement$.resolve$1(LibraryManagement.scala:89)\n\tat sbt.internal.LibraryManagement$.$anonfun$cachedUpdate$12(LibraryManagement.scala:133)\n\tat sbt.util.Tracked$.$anonfun$lastOutput$1(Tracked.scala:73)\n\tat sbt.internal.LibraryManagement$.$anonfun$cachedUpdate$20(LibraryManagement.scala:146)\n\tat scala.util.control.Exception$Catch.apply(Exception.scala:228)\n\tat sbt.internal.LibraryManagement$.$anonfun$cachedUpdate$11(LibraryManagement.scala:146)\n\tat sbt.internal.LibraryManagement$.$anonfun$cachedUpdate$11$adapted(LibraryManagement.scala:127)\n\tat sbt.util.Tracked$.$anonfun$inputChangedW$1(Tracked.scala:219)\n\tat sbt.internal.LibraryManagement$.cachedUpdate(LibraryManagement.scala:160)\n\tat sbt.Classpaths$.$anonfun$updateTask0$1(Defaults.scala:3690)\n\tat scala.Function1.$anonfun$compose$1(Function1.scala:49)\n\tat sbt.internal.util.$tilde$greater.$anonfun$$u2219$1(TypeFunctions.scala:62)\n\tat sbt.std.Transform$$anon$4.work(Transform.scala:68)\n\tat sbt.Execute.$anonfun$submit$2(Execute.scala:282)\n\tat sbt.internal.util.ErrorHandling$.wideConvert(ErrorHandling.scala:23)\n\tat sbt.Execute.work(Execute.scala:291)\n\tat sbt.Execute.$anonfun$submit$1(Execute.scala:282)\n\tat sbt.ConcurrentRestrictions$$anon$4.$anonfun$submitValid$1(ConcurrentRestrictions.scala:265)\n\tat sbt.CompletionService$$anon$2.call(CompletionService.scala:64)\n\tat java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)\n\tat java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)\n\tat java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat java.base/java.lang.Thread.run(Thread.java:829)"
}

[Trace - 09:39:11 AM] Received response 'buildTarget/scalaMainClasses - (42)' in 70ms
Result: null
Error: {
  "code": -32603,
  "message": "(update) found version conflict(s) in library dependencies; some are suspected to be binary incompatible:\n\n\t* com.github.mjakubowski84:parquet4s-core_2.13:2.5.1 (semver-spec) is selected over {1.2.1}\n\t    +- com.github.mjakubowski84:parquet4s-akka_2.13:2.5.1 (depends on 2.5.1)\n\t    +- io.delta:delta-standalone_2.13:0.4.0               (depends on 1.2.1)\n\n\nthis can be overridden using libraryDependencySchemes or evictionErrorLevel"
}

[Trace - 09:39:11 AM] Received notification 'build/logMessage'
Params: {
  "type": 1,
  "message": "(update) found version conflict(s) in library dependencies; some are suspected to be binary incompatible:\n\n\t* com.github.mjakubowski84:parquet4s-core_2.13:2.5.1 (semver-spec) is selected over {1.2.1}\n\t    +- com.github.mjakubowski84:parquet4s-akka_2.13:2.5.1 (depends on 2.5.1)\n\t    +- io.delta:delta-standalone_2.13:0.4.0               (depends on 1.2.1)\n\n\nthis can be overridden using libraryDependencySchemes or evictionErrorLevel"
}

This leads to confusion since it seems like nothing is working, no diagnostics are coming from the server when the user thinks that after adding this new dependency that everything was fine.
expectation
I'd expect the user to be notified somehow that there is an issue with their build definition that is prohibiting compilation from actually happening.
notes
This is using sbt 1.6.2

Thank you for opening this issue. This is indeed confusing for the user. However I think the problem should be addressed in Metals.
The build definition is correct in the sense that the build file can be compiled and loaded by sbt. What's not working here is the update task. After sbt has been reloaded Metals should request an update of the workspace/buildTargets and the buildTarget/dependencySources. Otherwise it would not know about the newly added, modified or removed library, or it would not know that there is a conflict in the library dependencies.
Notice also that sbt does respond with an error but Metals does not forward it to the user:
[Trace - 10:31:56 AM] Received response 'buildTarget/compile - (26)' in 59ms
Result: null
Error: {
  "code": -32603,
  "message": "(update) found version conflict(s) in library dependencies; some are suspected to be binary incompatible:\n\n\t* com.github.mjakubowski84:parquet4s-core_2.13:2.5.1 (semver-spec) is selected over {1.2.1}\n\t    +- com.github.mjakubowski84:parquet4s-akka_2.13:2.5.1 (depends on 2.5.1)\n\t    +- io.delta:delta-standalone_2.13:0.4.0               (depends on 1.2.1)\n\n\nthis can be overridden using libraryDependencySchemes or evictionErrorLevel"
}

Here the Result is null and the response is an Error.
Also this is not specific to libraryDependencies, Metals should also request an update of the buildTarget/sources, buildTarget/resources and the buildTarget/scalacOptions that could have possibly changed.

Notice also that sbt does respond with an error but Metals does not forward it to the user:

huh indeed. Looking if that compile request fails it looks like we don't handle it at all, but rather then try to get whatever the issue is from publishDiagnostics, which in this case doesn't happen. I'll need to dig in a bit more and I'll create an issue in Metals for this. Is it alright if I keep this open for now until I get more info and create on there, and then we can decide what to do.

Alright so I dug into this a little bit. My first reaction was to make some code changes here in Metals since we don't actually capture any failures here. However after making some changes and doing some tests it seems that it's not as clear cut as I was expecting.
When using Bloop if you have a piece of code like this:
object Main extends App {

  val x: Int = "hi"

}

The buildTarget/compile will come back with
[Trace - 01:58:23 PM] Received response 'buildTarget/compile - (9)' in 1130ms
Result: {
  "statusCode": 2
}
Error: null

wand then it will report the diagnostics. We can do a check on the compile result with isError and see that the compilation request was completed successfully but there is an error, which isError reflects and is confirmed with the diagnostics sent.
Based on that, I thought I could then capture the Failure and display those to the user, but given this same piece of code, sbt actually reports this compilation request as a failure with:
[Trace - 02:01:13 PM] Received response 'buildTarget/compile - (12)' in 137ms
Result: null
Error: {
  "code": -32603,
  "message": "(myproject / Compile / compileIncremental) Compilation failed"
}

as well as the expected diagnostics. However, this message shouldn't be shown to the user, so the question becomes how do we differentiate messages like this with message like in the original issue about version conflicts that the user should know about? And in this situation, show the buildTarget/compile really be failed with this?


Can't mock custom module

My Module:
// ./App/Services/MyBridge
import { NativeModules } from 'react-native'
export const MyBridge = NativeModules.MyBridge
export default MyBridge

My Mock:
// ./testSetup.js
mockery.enable()
mockery.registerAllowable('./App/Services/MyBridge', {
  nativeCall: () => {}
})

mockery.registerMock('./App/Services/MyBridge', {
  nativeCall: () => {}
})

Expected Behavior
MyBridge.nativeCall is mocked
Actual Behavior
Error message during test run Error: Cannot read property 'nativeCall' of undefined
I can't, for the life of me, figure this out. Mocking 3rd party modules works fine.
Any ideas<EMAIL_ADDRESS>

Found a workaround. In case anyone else runs into this:
import mockery from 'mockery'
import * as rn from 'react-native'

mockery.registerMock('react-native', {
  ...rn,
  NativeModules: {
    MyBridge: {
      nativeCall: () => {}
    }
  }
})

This feels a bit dirty though. So leaving this open to wait for some feedback if there's a better way to do it.

@chapati23 it's not really clear from your snippets, but remember the first arg of registerMock has to be exactly what's inside require(), not just a path to the file you want to mock. Are you doing this?

@RealOrangeOne not sure i understand. in this case i'm mocking the actual react-native npm package so it does work like it's in the snippet


Bug: Updating title not working when commas are included

Describe the Bug
I'm using YAML title alias function to insert title in frontmatter alias section also the function linter-yaml-title-alias is on.
Updating title and alias works fine until I put comma in the title.
Title is getting from H1,
How to Reproduce
---
linter-yaml-title-alias: test
title: test
created: 1970-01-01
updated: 2023-06-14
aliases: ["test"]
tags:
---
# test

---
linter-yaml-title-alias: test test2 test3
title: test test2 test3
created: 1970-01-01
updated: 2023-06-14
aliases: [test test2 test3]
tags:
---
# test test2 test3

---
linter-yaml-title-alias: "test, test2, test3"
title: test, test2, test3
created: 1970-01-01
updated: 2023-06-14
aliases: ["test, test2, test3"]
tags:
---
# test, test2, test3

---
linter-yaml-title-alias: test4
title: test4
created: 1970-01-01
updated: 2023-06-14
aliases: ["test, test2, test3"]
tags:
---
# test4

data.json.txt
Device

[X] Desktop
[ ] Mobile

Hey @jablonm . Thanks for reporting this. Commas are not currently handled properly with multiple levels of nesting. This may be something that can be fixed, but at this time this is expected to happen. I will see what can be done about his when I get a chance.

@jablonm , is the last scenario the only scenario that is not working correctly?
That is
---
linter-yaml-title-alias: test4
title: test4
created: 1970-01-01
updated: 2023-06-14
aliases: ["test, test2, test3"]
tags:
---
# test4

I believe I have a fix for this, but I will await your response, because I believe my previous statement about commas not being handled correctly applies for this rule, but I am not sure that it applies to all rules at this time.

I need to clarify one more thing, the problem is not in numbers but in commas. I apologize if I have caused unnecessary confusion.
1 st run with comma
---
linter-yaml-title-alias: "test, test"
title: test, test
created: 1970-01-01
updated: 2023-06-14
aliases: ["test, test"] ------------------------------------ using comma
tags:
---
# test, test

updating title this time without comma
---
linter-yaml-title-alias: test test
title: test test
created: 1970-01-01
updated: 2023-06-14
aliases: ["test, test"] ------------------------------------ not updated
tags:
---
# test test

No worries. The change I made was related to an existing change. It escapes values when it searches for them which is what was what needed to happen when dealing with number aliases which is why they are coupled together in that PR.

Wow, thank you for quick analyze and response :) I'm really impressed!

No problem. I was already looking at things in the area so I decided to tackle the issue. Hopefully it addresses the issue with no side-effects.

The change for this has been merged into master and should go out with the next release. Please let us know if there are any issues with it on master or in the next release.


support sendmmsg and recvmmsg

is there an plan to support sendmmsg and recvmmsg on unix platform? or WSARecvMsg on windows platform?

Which boost library are you referring to here?

Which boost library are you referring to here?

boost_1_76_0, i searched the source code with visual studio code, but not found any keywords likes "sendmmsg" or "recvmmsg"

@zkas Boost is a collection of libraries, so once again: Which Boost library you aim with your suggestion?

@zkas Boost is a collection of libraries, so once again: Which Boost library you aim with your suggestion?

asio network, i also searched boost_1_79_0, but not found too.we need "sendmmsg" or "recvmmsg" to realize
aggregate sending and receiving data through udp socket

@zkas

asio network,

👉  https://github.com/chriskohlhoff/asio

we need "sendmmsg" or "recvmmsg" to realize aggregate sending and receiving data through udp socket

Then, speak to Asio developers, not the whole Boost community.

thank you for your replay


Refactor new ECS rubble further

After merging #593 the "golden test asteroid" that spawns in front of the starting station now uses ECS-based rubble creation! There are some outstanding next steps however:

[ ] The rubble starts with no momentum added - they should be flying all over the place (if they get bumped they also start acting bizarrely, like flying in circles)
[ ] The rubble is invincible (same state before #593, normal asteroids are fine) and needs to be destructible
[ ] The tubble goes straight to the tiniest size - a larger asteroid should first break into smaller pieces
[ ] Smaller pieces should probably also have a chance to drop loot, but destroyed tiny rubble pieces should not?
[ ] Maybe really a separate item: regular asteroids should be updated to the new system - but this may involve a fair bit more work including spawning, despawning, and random starting momentum/movement if any

If anybody new wants to work on this feel free - it isn't necessarily a Good First Issue since the topic is complex, but the area is relatively tiny and approachable and we can give more directions here or on Discord as needed in response to well-informed questions :-)

This isn't closed yet! Not all the issues have been solved.


MVC totorial: There is already an object named 'Course' in the database

[Enter feedback here]
In Migration, at the ASP.Net Core MVC totorial
Using both CLI and PMC I got the following error:
"There is already an object named 'Course' in the database".
Help.

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

ID: e56e675b-5964-a75b-7e45-6f6d1a607e65
Version Independent ID: 78e47218-58a3-f8d9-e091-306126871a67
Content: Tutorial Part 5, apply migrations to the Contoso University sample
Content Source: aspnetcore/data/ef-mvc/migrations.md
Product: aspnet-core
Technology: aspnetcore-data
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

That's a good error. Easiest thing is to Drop and re-create the database

To fix this:
Make an include and add to both series that point to Drop and re-create the database


Ability to change color scheme for the bash prompt

When installing the bash prompt from the linux utility can there be a user interaction with options for different color schemes for basic colors like: red, blue, green, purple ... etc.
Oh and i forgot about kitty/alacritty also

Only the installation scripts are included in Linutil at the moment, you would have to request this in the mybash repository on ChrisTitusTech's profile if you want to see this implemented. Those projects will be moved over to this repository in the future though.


No 0.10.1 container available

Celestia Node version
0.10.1
OS
Docker
Install tools
No response
Others
No response
Steps to reproduce it
Hi,
it seems there is no docker container available yet. When will it be released?
# docker pull ghcr.io/celestiaorg/celestia-node:v0.10.1
Error response from daemon: manifest unknown

Expected result
Docker container tagged with the same version.
Actual result
Tagged container not available.
Relevant log output
No response
Notes
No response

docker pull ghcr.io/celestiaorg/celestia-node:v0.10.1

We accidentally missed adding v in the release. Now, that it fixed, try again


Revisit GetServiceInstance and GetBind return objects in broker.

GetServiceInstance in broker.go returns a ServiceInstance. GetBind returns a BindResponse. Most of the broker methods return a *Response. Maybe we should add a GetServiceInstanceResponse method to the broker and have the handler call that. Keep GetServiceInstance simply as util method.

Closing, we can refactor if we want, but not really a bug.


schema-revision: annotationToEntity.schema.json

the verifiable property only makes sense to me between user-defined annotations to atlas defined entities
even then its not really verifiable but just the confirmation/judgment of the curator that needs to be captured here
can this be solved differently?

I would remove it all together. Our original thought was to give an estimation for whether or not an user-annotationToEntity can be verified as correct by a curator (given in its own curator-annotationToEntity). This is mostly a provenance/curation progres tracking thing. I don't think these things should be recorded with SANDS (or at least not with the first version of it). Curators do record the information, and maybe we could make it available in a different way (e.g. as report shared along with the data).

solved differently now; directly solved in annotation via "definingTerm" and "relatedAtlasTerm" in addition to official terminologies identifiable via their connection to an ontology


Data Set

Does the data set support for this kind of model if we use : .csv types
I mean as an example: news_headings.csv
Please help me!

Does the data set support for this kind of model if we use : .csv types
I mean as an example: news_headings.csv
Please help me!


Update FOX asset description with fancy copy.

Overview
We now support custom descriptions and we're pulling the lame description from coingecko.

Reference
https://github.com/shapeshift/lib/blob/main/packages/asset-service/src/service/descriptions.json
Acceptance Criteria

Fancy new description from product is implemented above.

Need By Date
n/a
Ownership

[X] If my bounty needs engineering or needs product I have added the respective labels on the right
[X] As the sponsor of this bounty I will review the changes in a preview environment (ops/product) or review the PR (engineering)

Bounty Hunters

Join our discord
Include an expected timeline for you to complete work in the work plan when you apply for this bounty!
Please refer to this link for some basic info
Please do not start work on this issue until you are approved in Gitcoin.

@0xdef1cafe here's an updated description that has green lights from Diggy and willy to go live when FOXy does. please let me know if anything else is needed and will knock it out! ty ser
FOX is an ERC-20 token created by ShapeShift which serves as the governance token for the ShapeShift DAO. Token holders can vote on proposals relating to the operation and treasury of the DAO. The FOX token supports and provides utility for a borderless, cross-chain crypto trading platform and portfolio manager for user self-sovereignty.
The ShapeShift ecosystem has been expanding rapidly around the new, decentralized, open source web app that allows users to not only trade and swap assets cross-chain, but also earn yield through staking assets across platforms such as Curve.Finance, Yearn.Finance, and the Cosmos ecosystem.
Holders of the FOX token are also able to stake their FOX for ShapeShift's new FOXy token, where they will benefit from active yield management conducted by the ShapeShift DAO without any effort on their part. FOXy holders will receive additional FOXy generated from avenues such as the FOX Tokemak reactor, as well as a portion of revenue generated by the DAO through affiliate partnerships. The FOXy token is an "only-up" rebasing token always redeemable 1:1 with FOX, and is the best way to earn yield on FOX holdings.

@purelycrickets 2 hours

will also note that we can circle back to this and update with links once FOXy is live as well

Ser, should we include FOXy links now?

@gomesalexandre  @0xdef1cafe looks like a PR was submitted for this ticket. Does it still need a bounty?


Unable to install postman

brew doctor output
yusf@yusf:~$ brew doctor
Your system is ready to brew.

Verification

[X] My "brew doctor output" above says Your system is ready to brew. and am still able to reproduce my issue.
[X] I ran brew update twice and am still able to reproduce my issue.
[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

brew config output
yusf@yusf:~$ brew config
HOMEBREW_VERSION: 3.6.16
ORIGIN: https://github.com/Homebrew/brew
HEAD: 740f9ddcc620d4812770a0f12854ddd79c643874
Last commit: 10 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 14fe99d63e0c3c7270c89fd6a089b791f4c54ec8
Core tap last commit: 79 minutes ago
Core tap branch: master
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: :0
HOMEBREW_MAKE_JOBS: 8
Homebrew Ruby: 2.6.8 => /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.8_1/bin/ruby
CPU: octa-core 64-bit unknown_0x6_0x8c
Clang: N/A
Git: 2.34.1 => /bin/git
Curl: 7.81.0 => /bin/curl
Kernel: Linux 5.15.0-56-generic x86_64 GNU/Linux
OS: Ubuntu 22.04.1 LTS (jammy)
Host glibc: 2.35
/usr/bin/gcc: 11.3.0
/usr/bin/ruby: N/A
glibc: N/A
gcc@11: N/A
gcc: N/A
xorg: N/A

What were you trying to do (and why)?
installing postman
https://learning.postman.com/docs/getting-started/installation-and-updates/
What happened (include all command output)?
~$ brew install --cask postman
Usage: brew install [options] formula|cask [...]
Install a formula or cask. Additional options specific to a formula may be
appended to the command.
Unless HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set, brew upgrade or brew
reinstall will be run for outdated dependents and dependents with broken
linkage, respectively.
Unless HOMEBREW_NO_INSTALL_CLEANUP is set, brew cleanup will then be run for
the installed formulae or, every 30 days, for all formulae.
Unless HOMEBREW_NO_INSTALL_UPGRADE is set, brew install formula will
upgrade formula if it is already installed but outdated.
-d, --debug                      If brewing fails, open an interactive
debugging session with access to IRB or a
shell inside the temporary build directory.
-f, --force                      Install formulae without checking for
previously installed keg-only or non-migrated
versions. When installing casks, overwrite
existing files (binaries and symlinks are
excluded, unless originally from the same
cask).
-v, --verbose                    Print the verification and postinstall steps.
-n, --dry-run                    Show what would be installed, but do not
actually install anything.
--formula, --formulae        Treat all named arguments as formulae.
--ignore-dependencies        An unsupported Homebrew development flag to
skip installing any dependencies of any kind.
If the dependencies are not already present,
the formula will have issues. If you're not
developing Homebrew, consider adjusting your
PATH rather than using this flag.
--only-dependencies          Install the dependencies with specified
options but do not install the formula
itself.
--cc                         Attempt to compile using the specified
compiler, which should be the name of the
compiler's executable, e.g. gcc-7 for GCC
7. In order to use LLVM's clang, specify
llvm_clang. To use the Apple-provided
clang, specify clang. This option will only
accept compilers that are provided by
Homebrew or bundled with macOS. Please do not
file issues if you encounter errors while
using this option.
-s, --build-from-source          Compile formula from source even if a
bottle is provided. Dependencies will still
be installed from bottles if they are
available.
--force-bottle               Install from a bottle if it exists for the
current or newest version of macOS, even if
it would not normally be used for
installation.
--include-test               Install testing dependencies required to run
brew test formula.
--HEAD                       If formula defines it, install the HEAD
version, aka. main, trunk, unstable, master.
--fetch-HEAD                 Fetch the upstream repository to detect if
the HEAD installation of the formula is
outdated. Otherwise, the repository's HEAD
will only be checked for updates when a new
stable or development version has been
released.
--keep-tmp                   Retain the temporary files created during
installation.
--debug-symbols              Generate debug symbols on build. Source will
be retained in a cache directory.
--build-bottle               Prepare the formula for eventual bottling
during installation, skipping any
post-install steps.
--bottle-arch                Optimise bottles for the specified
architecture rather than the oldest
architecture supported by the version of
macOS the bottles are built on.
--display-times              Print install times for each package at the
end of the run.
-i, --interactive                Download and patch formula, then open a
shell. This allows the user to run
./configure --help and otherwise determine
how to turn the software package into a
Homebrew package.
-g, --git                        Create a Git repository, useful for creating
patches to the software.
--overwrite                  Delete files that already exist in the prefix
while linking.
--cask, --casks              Treat all named arguments as casks.
--[no-]binaries              Disable/enable linking of helper executables
(default: enabled).
--require-sha                Require all casks to have a checksum.
--[no-]quarantine            Disable/enable quarantining of downloads
(default: enabled).
--adopt                      Adopt existing artifacts in the destination
that are identical to those being installed.
Cannot be combined with --force.
--skip-cask-deps             Skip installing cask dependencies.
--zap                        For use with brew reinstall --cask. Remove
all files associated with a cask. May remove
files which are shared between applications.
--appdir                     Target location for Applications (default:
/Applications).
--colorpickerdir             Target location for Color Pickers (default:
~/Library/ColorPickers).
--prefpanedir                Target location for Preference Panes
(default: ~/Library/PreferencePanes).
--qlplugindir                Target location for QuickLook Plugins
(default: ~/Library/QuickLook).
--mdimporterdir              Target location for Spotlight Plugins
(default: ~/Library/Spotlight).
--dictionarydir              Target location for Dictionaries (default:
~/Library/Dictionaries).
--fontdir                    Target location for Fonts (default:
~/Library/Fonts).
--servicedir                 Target location for Services (default:
~/Library/Services).
--input-methoddir            Target location for Input Methods (default:
~/Library/Input Methods).
--internet-plugindir         Target location for Internet Plugins
(default: ~/Library/Internet Plug-Ins).
--audio-unit-plugindir       Target location for Audio Unit Plugins
(default:
~/Library/Audio/Plug-Ins/Components).
--vst-plugindir              Target location for VST Plugins (default:
~/Library/Audio/Plug-Ins/VST).
--vst3-plugindir             Target location for VST3 Plugins (default:
~/Library/Audio/Plug-Ins/VST3).
--screen-saverdir            Target location for Screen Savers (default:
~/Library/Screen Savers).
--language                   Comma-separated list of language codes to
prefer for cask installation. The first
matching language is used, otherwise it
reverts to the cask's default language. The
default value is the language of your system.
-q, --quiet                      Make some output more quiet.
-h, --help                       Show this message.
Error: Invalid usage: Options --formula and --casks are mutually exclusive.
What did you expect to happen?
get postman installed
Step-by-step reproduction instructions (by running brew commands)
brew install --cask postman

Casks are macOS-only. We should have a better error message here, but the fact that you're unable to install the postman cask is expected behaviour.

Casks are macOS-only. We should have a better error message here, but the fact that you're unable to install the postman cask is expected behaviour.

first time using brew, so i believe yes error message needed to be bit clear
Thank you very much for your help

It's supposed to throw an error when --cask is used on Linux so this is definitely a bug.


[Error handling] Evaluate MCAD code base for better error handling

WHY
This change is needed to retry or appropriately update etcd
WHAT
Review code base for error handling scenarios
HOW
Make relevant code changes and print appropriate error strings.
TESTS
Write additional tests for error handling
DONE
Increase in test cases that support error handling use case.

Hi @asm582, just a question about this issue which I have started working on. Is it appropriate to update some functions to return errors, so that we can catch the errors when the functions are called or do we just want to add logging of errors for other function calls inside the functions?
I just don't want to many any changes that could effect others using MCAD if that's not what is required. Please let me know what you think. Thank you.

Hi @Fiona-Waters , I think it's a good idea to start logging errors for now and then we can design later how we can gracefully handle errors.


handle errors

The code example works great if the login is successful.  However how do you handle or parse through any JSON if there is an error on the login action?

You can handle it like any other promise. Taking the code from example:
import Ember from 'ember';

export default Ember.Controller.extend({

    actions: {
        login() {
            this.get('session').authenticate('authenticator:firebase', {
                'email': this.get('email'),
                'password': this.get('password')
            }).then(() => {
                this.transitionToRoute('index');
            }, (error) => {
                // error logic
            });
        },
    }
});

(re-wrote in ES6 syntax)

ahh of course, thank you!


Create Ordlinks collection listing

Create this listing for the Project Ordlinks

https://docs.google.com/document/d/1omEZx6mhyVoOlurqJwAnVZcWVkc-LbO0d8G_ZgR_T60/edit?usp=sharing.    Please refer to this and modify it.


MySQL dump file corrupted since 24.2.0

Description
I created a table with 500 lines, each line has 100 as in one column, and 100 1s in another column.

Then I used dump database with these settings.

However the dump results are different each time I dump, and they are all corrupted sql files.
dump.zip
For example in 2.sql, some parts got truncated

DBeaver Version
Community Editon 24.2.0
Operating System
Windows 10
Database and driver

Database: MySQL 5.7.34
Driver: MySQL Connector 8.0.29

Steps to reproduce
No response
Additional context
No response

Seems to be duplicate of #35421

@WEGFan Thank you for the report

Duplicate: https://github.com/dbeaver/dbeaver/issues/35421


ASP.NET non-Core support

What is the Asp .Net non-Core support road-map?
When will the below tab be removed?
What will be the workflow for Asp .Net Web Api non-Core projects when the below tab will be removed?

I don’t plan to remove this tab as long as it’s feasible to maintain asp.net support... it’s mainly deprecated for core projects. However I personally will not put a lot of work into improving the legacy asp.net generator... as long as this is still used by people i’ll keep it - no worries, but new features will only lang in the core generator.

Great, looks like the deprecation plan has been dropped

Yeah, but please dont use it for asp.net core


fix #15798 (yii\grid\CheckboxColumn, yii\grid\RadioButtonColumn conte…

…nt option has no effect)

Q
A

Is bugfix?
yes

New feature?
no

Breaks BC?
no

Tests pass?
no

Fixed issues
#15798

@lesha724 could you add unit tests, please?
There are already tests for CheckboxColumn and RadioButtonColumn

Great! The last thing to do is to add a line in a CHANGELOG.md. Could you do it, please?

Thank you!


Use c++11 'using' instead of 'typedef'

What's in this pull request?
Use c++11 'using' instead of 'typedef'

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci Please test

Upstream LLVM is still using typedef for these sorts of types.  I'd prefer to stay consistent with it for now.  If you're interested in driving this, please try to can convince them to change (email the llvm-dev mailing list).
-Chris


Error: Cannot find module 'package-json-versionify' from ...

Hi @feross
I'm trying to install webTorrent client. But there is small problem like below.
I got the following error code after npm start and I typed the npm install package-json-versionify command.
But problem is still that.
Any idea what could fix it?
Error: Cannot find module 'package-json-versionify' from '/root/myGit/instant.io/node_modules/webtorrent'
    at /root/myGit/instant.io/node_modules/browserify/node_modules/resolve/lib/async.js:46:17
    at process (/root/myGit/instant.io/node_modules/browserify/node_modules/resolve/lib/async.js:173:43)
    at ondir (/root/myGit/instant.io/node_modules/browserify/node_modules/resolve/lib/async.js:188:17)
    at load (/root/myGit/instant.io/node_modules/browserify/node_modules/resolve/lib/async.js:69:43)
    at onex (/root/myGit/instant.io/node_modules/browserify/node_modules/resolve/lib/async.js:92:31)
    at /root/myGit/instant.io/node_modules/browserify/node_modules/resolve/lib/async.js:22:47
    at FSReqWrap.oncomplete (fs.js:82:15)

npm ERR! Linux 3.13.0-32-generic
npm ERR! argv "/root/.nvm/versions/v4.4.7/bin/node" "/root/.nvm/versions/v4.4.7/bin/npm" "run" "build-js"
npm ERR! node v4.4.7
npm ERR! npm  v2.15.8
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>build-js: `browserify client > static/bundle.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build-js script 'browserify client > static/bundle.js'.
npm ERR! This is most likely a problem with the instant.io package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     browserify client > static/bundle.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs instant.io
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls instant.io
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /root/myGit/instant.io/npm-debug.log

npm ERR! Linux 3.13.0-32-generic
npm ERR! argv "/root/.nvm/versions/v4.4.7/bin/node" "/root/.nvm/versions/v4.4.7/bin/npm" "run" "build"
npm ERR! node v4.4.7
npm ERR! npm  v2.15.8
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>build: `npm run build-css && npm run build-js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'npm run build-css && npm run build-js'.
npm ERR! This is most likely a problem with the instant.io package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run build-css && npm run build-js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs instant.io
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls instant.io
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /root/myGit/instant.io/npm-debug.log

npm ERR! Linux 3.13.0-32-generic
npm ERR! argv "/root/.nvm/versions/v4.4.7/bin/node" "/root/.nvm/versions/v4.4.7/bin/npm" "start"
npm ERR! node v4.4.7
npm ERR! npm  v2.15.8
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `npm run build && node server`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'npm run build && node server'.
npm ERR! This is most likely a problem with the instant.io package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run build && node server
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs instant.io
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls instant.io
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /root/myGit/instant.io/npm-debug.log

I suggest running rm -rf node_modules/ && npm cache clean && npm install once more. Can't think of why this one package would be missing for you.


(migrated) Journal does not render dice symbols

Looks like at some point in the last few releases we started using the default journals again, which do not properly render dice expressions.

I'm not sure it's just here. Our Tuesday PF2e game suddenly started showing the old journals, as well (and confused the heck out of all of us). Something changed in base Foundry, perhaps?

It is replacing with the symbols for me.

@Rysarian interesting. I see that as well, for a new Journal. But for one migrated, it does not work properly. A step in the right direction!

Update: this is toggleable by enabling/disabling "display page title."

fixed, should be good in the next release


WSL2: VSCode WSL - Remote broken on Windows 19555

When starting the VSCode with the WSL - Remote extension on Windows Build 19555, the WSL terminal shows the following error:
[2020-02-01 14:56:02.345] Unable to detect if server is already installed: Error: Command failed: C:\WINDOWS\System32\wsl.exe -d Ubuntu -e sh -c "[ -d ~/.vscode-server/bin/26076a4de974ead31f97692a0d32f90d735645c0 ] && printf found || ([ -f /etc/alpine-release ] && printf alpine-; uname -m)"
[2020-02-01 14:56:02.345] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

https://github.com/microsoft/WSL/issues/4860 is similar, but fixing the PATH length does not help for VSCode.
The workaround is to rollback Windows from 19555 to 19541:
Start -> Settings -> Update and Security -> Recovery -> Go back to the previous version of Windows 10

Workaround without rollback:  https://github.com/microsoft/WSL/issues/4860#issuecomment-581592480

I pushed new versions of the Remote - WSL extension (0.41.9, 0.42.3) with a workaround (use a empty PATH when calling wsl.exe).
Please let me know if this works for you.

@aeschli Yes, this works! I'm using 0.41.9. Thanks so much!


Issue with Board View using custom List formatting "inlineEditField" and "columnFormatterReference" in "customCardProps"

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
Declarative list formatting
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[X] 💥 Google Chrome
[X] 💥 FireFox
[X] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details
since all is json with pre defined properties not enviroment detail is needed.
Describe the bug / error
When Power user have "Board" view and is formatting view with JSON and need to create a dialog "customCardProps" the following properties inside the customcard doesn't work (cannot edit) "inlineEditField" and "columnFormatterReference"  for a choice field doesn't appear with fields formatted just the raw data text.
Issue:

Steps to reproduce

Create New Microsoft List.
Create support fields and choice field with multiple values and for each choice associate color formatting.
Create new View and select "Board"
Access to "Format View" and add custom json with property "customCardProps"
When formatting JSON inside "customCardProps" include  "inlineEditField" and "columnFormatterReference" options.
Save format and validate if options are working.

Expected behavior
When user is using View "Board" and click in a custom view JSON format with "customCardProps" the options  "inlineEditField" and "columnFormatterReference" should work as image below:

@shagra-ms
I would like to address you this issue regarding declarative JSON Microsoft List

@aaclage Thanks for reporting this. Will check.

Fixed with https://github.com/SharePoint/sp-dev-docs/issues/9614


Spring Cloud Config reference document section

Adds the missing Spring Cloud Config section to the Spring Cloud GCP
reference document.

@jabubake FYI

All -- this is likely the last missing piece for M1, a timely review is appreciated so M1 can be launched asap :)

I think I resolved every comment, but let me know if there is anything I missed.
Thanks!


Bootstrap toggle is not working with jquery steps

bootstrap toggle is working fine inside simple form, but not working with jquery steps plugin. when user clicks on toggle button, it creates duplicate html inside existing toggle.
Is this compatible with jquery steps plugin
BEFORE CLICK:

AFTER  CLICK:

Im facing the same issue. any update on it?

For anyone that runs into this issue—the issue for us is that the elements housing the toggle were dynamically generated, and in our HTML mark-up we had data-toggle='toggle' (the dynamically generated elements were $.clone() from an element that probably was instantiated due to the HTML mark-up). Removing the HTML mark-up and instantiating via JavaScript ($(input).bootstrapToggle()) fixed the issue for us.


Another tone fix - "IPFS aims to replace HTTP..."

This whole sentence needs a rework, but here are a couple of suggestions for replacing "replace" for now.

@autonome I vote for "upgrade" or "go beyond", but defer to decision of @momack2.

while I like how "upgrade" sounds better, the connotations don't make sense (sounds like we're just iterating within the spec of HTTP, not building a new envisioning of how a hypertext transport protocol should work).
Would "surpass" work here? Same meaning as "go beyond"/"leapfrog", but slightly pithier IMHO. =]

"Surpass" works in the sense that it sounds like a successor.
cc @autonome @momack2

To "surpass HTTP in order to build a better web" strikes me as redundant.
Although kind of clinical, would a simple line such as this suffice (especially given that this is a supporting caption, as opposed to a header)? …
"IPFS aims to replace HTTP and build a better web for all of us."

@ericronne I can see both ways. Again -- deferring to @momack2.

I prefer the former. I don’t think the latter suggestion mitigates the
point Deitrich made and seems fuzzier to me.
On Mon, Sep 16, 2019 at 2:01 PM Jessica Schilling<EMAIL_ADDRESS>wrote:

@ericronne https://github.com/ericronne I can see both ways. Again --
deferring to @momack2 https://github.com/momack2.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ipfs/website/pull/337?email_source=notifications&email_token=AAEXAFZVMH4GVZFA7TWTNN3QJ7XZLA5CNFSM4IXF32Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD62QGFQ#issuecomment-531956502,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEXAF2NO5QHEBVKNTYRTH3QJ7XZLANCNFSM4IXF32QQ
.

re "replace" - The criticism I received was explained as "replacing http" is arrogant - not only does it not acknowledge how amazing the http web actually is, it far oversells IPFS in a way that gives people a negative feeling.

@autonome Thank you for chipping away at these!


Add --log-level flag and default to error level

Current logs are noisy and I'm sure everyone got bored reading them a while back.
This adds a --log-level flag which defaults to error and these new log messages.
$ apptestctl bootstrap --kubeconfig="$(kind get kubeconfig)"
bootstrapping app platform components
app platform components are ready

Checklist

[x] Update changelog in CHANGELOG.md.

Thx! @piontec ❤
Once the new app-operator and chart-operator releases are out I'll cut a v0.14.0 release and update ATS


Enable Auth0 login

What

Add login with Auth0
Add ensureLoggedIn middleware to protect views
Add login and logout views in base app

How to review

Add the following environment variables:

Variable name
Value

AUTH0_DOMAIN
Domain from client settings page in Auth0

AUTH0_CLIENT_ID
Client ID from client settings page in Auth0

AUTH0_CLIENT_SECRET
Client Secret from client settings page in Auth0

AUTH0_CALLBACK_URL
http://localhost:3000/callback

Run the app
Click the Login button in the top right on the home page
Get prompted to login via Auth0
Click Logout link
Click Apps link and get redirected to login again

My knowledge of this stuff is limited but as far as I can tell it looks good 👍 (also, see comments)


Add a README note about JSHint extraction in 2.x

…since there's no changelog to explain the major version bump

@reidab awesome, thanks!


(cmd_fixes)fix: make chaos inject and kill cmds as tunable

Signed-off-by: ksatchit<EMAIL_ADDRESS>

apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
  name: catalogue-chaos
  namespace: sock-shop
spec:
  annotationCheck: 'false'
  engineState: 'active'
  auxiliaryAppInfo: ''
  appinfo:
    appns: 'sock-shop'
    applabel: 'name=catalogue'
    appkind: 'deployment'
  chaosServiceAccount: pod-cpu-hog-sa
  monitoring: false
  jobCleanUpPolicy: 'retain'
  experiments:
    - name: pod-cpu-hog
      spec:
        components:
          env:
            # Provide name of target container
            # where chaos has to be injected
            - name: TARGET_CONTAINER
              value: 'catalogue'

            #number of cpu cores to be consumed
            #verify the resources the app has been launched with
            - name: CPU_CORES
              value: '1'

            - name: TOTAL_CHAOS_DURATION
              value: '60' # in seconds

            - name: CHAOS_KILL_COMMAND
              value: "kill -9 $(ps afx | grep \"[md5sum] /dev/zero\" | awk '{print$1}' | tr '\n' ' ')"

apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
  name: catalogue-mem-chaos
  namespace: sock-shop
spec:
  annotationCheck: 'false'
  engineState: 'active'
  auxiliaryAppInfo: ''
  appinfo:
    appns: 'sock-shop'
    applabel: 'name=catalogue'
    appkind: 'deployment'
  chaosServiceAccount: pod-memory-hog-sa
  monitoring: false
  jobCleanUpPolicy: 'retain'
  experiments:
    - name: pod-memory-hog
      spec:
        components:
          env:
            # Provide name of target container
            # where chaos has to be injected
            - name: TARGET_CONTAINER
              value: 'catalogue'

            # Enter the amount of memory in megabytes to be consumed by the application pod
            - name: MEMORY_CONSUMPTION
              value: '500'

            - name: TOTAL_CHAOS_DURATION
              value: '90' # in seconds

            - name: CHAOS_KILL_COMMAND
              value: "kill -9 $(ps afx | grep \"[dd] if /dev/zero\" | awk '{print $1}' | tr '\n' ' ')"


VstsTaskSdk missing in AzureWebPowerShellDeployment Task

Hi, when I start a deployment task of Azure App Service: Classic today, I found the following problem
2017-09-21T00:06:52.6276856Z ##[error]File not found: 'C:\VSTS-Agent-2.104.0\_work\_tasks\AzureWebPowerShellDeployment_dcbef2c9-e4f4-4929-82b2-ea7fc9166109\1.0.46\ps_modules\VstsTaskSdk\VstsTaskSdk.psd1'

After some investigation, it seems to me that my VSTS agent has downloaded a new version of AzureWebPowerShellDeployment (1.0.46) few hours ago, Comparing the folder structure between the  latest version and older version, seems it used to have a VstsTaskSdk folder under ps_modules, but now the whole folder and its scripts inside are missing.

Please can we get a fix for this Microsoft - we are using VSO and this is happening since yesterday using Hosted agents. Why did you even mess with it in the first place? It is deprecated so leave it alone.

hi @kinoro , we are hotfixing this. I will update here once that is done. Meanwhile, can you please tell me your account name.

Hi,
Is there any workaround available while you work in the hotfix?
Thanks.

@chadidbarnero , if you use private pipeline, you can copy the whole VstsTaskSdk folder from old version to new version. Probably @arjgupta can help if you use hosted pipeline?

thanks @thomasmktong. Unfortunately I only have hosted pipelines...

we have hotfixed the task. Can you please confirm if you are unblocked. The newer version is 1.0.47

@arjgupta , I confirm that my build agent has picked up the new version and deployment can be done successfully. Many thanks.

It is working now. thanks.

I am closing this issue, please feel free to open this issue, if you are still facing it


Fixed typographical error, changed accross to across in README.

@elastic, I've corrected a typographical error in the documentation of the puppet-elasticsearch project. You should be able to merge this pull request automatically. However, if this was intentional or if you enjoy living in linguistic squalor, please let me know and create an issue on my home repository.

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run; then  say 'jenkins, test it'.

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run; then  say 'jenkins, test it'.

Hi, could you sign the CLA so i can merge it? thanks!

I do have to admit English is not my primary language and dyslexia doesn't help either.
Thank you for the fix though!


Fix #3838: Component is left in broken state after redeployment of the pod

What type of PR is this?
/kind bug
What does does this PR do / why we need it:
See https://github.com/openshift/odo/issues/3838#issuecomment-682259193
Which issue(s) this PR fixes:
Fixes #3838
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

[X] I have read the test guidelines

How to test changes / Special notes to the reviewer:
See https://github.com/openshift/odo/issues/3838 for test reproduction steps.

/ok-to-test

/approve

/retest


Feat: Agent (except reports)

Closes #23 #22 #21 #20 #19 #18 #17 #16

General

Show what page we're on - in titlebar?

Done bad0942

Hover explanations for various buttons, particularly the ones containing images instead of text
Gray out Navigate {Backward, Forward} when action is unavailable
Can we somehow make this more like Android navigation instead of a history of places we've - been? Although Android doesn't have forward navigation, so I guess it's inherently different
File menu sometimes flickers when opening menu item? (Can't reproduce this anymore)
Can we somehow hide the bottom pointing arrows in the toolbar when there are no overflowing items?

ArrangementReport

Table unstyled
{Previous, Next} Page buttons use text instead of arrows
Doesn't have standalone Cancel/Back button - we have this for ArrangementAdd and ArrangementEdit, should stay consistent

ArrangementAdd

Back/Next/Finish buttons don't have their text centered inside the button. In fact, none of the buttons seem to have their text centered - is this deliberate? Does it not look jarring?
Would be nice if the stepper items on the left were navigable as well - is this unorthodox behavior for steppers?
Cancel button doesn't have red X image, whereas ArrangementEdit's cancel button does

ArrangementList

Search bar isn't bound to Enter
Toggling visibility of all three arrangement types doesn't seem to show all arrangements in the list? Do I not understand how this should work or is it broken?
...I see now we paginate the arrangements. Still, we should fit more than two arrangements per page, although I assume this is temporary for testing purposes
Confirm deletion dialog removes hover effect from list item
Speaking of said dialog, the Yes/No options are not centered

PlacesList

Search bar isnt' bound to Enter
Confirm deletion dialog removes hover effect from list item
Speaking of said dialog, the Yes/No options are not centered

LocationAdd

Starts off with Location name preselected

Help window(?)

Back/Forward text color poor contrast in dark theme; text is dark

Menu bar

In "Settings", "Preferences" opens "General", "Customize toolbar" opens "Toolbar"? Make consistent
Proposal: rename "Settings" to "Tools", "Preferences" to "Settings", remove "Customize toolbar"?
Opening Settings->General automatically seems to update the user config; add way to cancel/save changes

Can we somehow make this more like Android navigation instead of a history of places we've been? Although Android doesn't have forward navigation, so I guess it's inherently different
This is different, I wanted our navigation system to be like the built-in one (which was hard to style, which is why I made custom buttons in the first place).

File menu sometimes flickers when opening menu item? (Can't reproduce this anymore)
Can't reproduce.

ArrangementReport

Someone else can do this.

Back/Next/Finish buttons don't have their text centered inside the button. In fact, none of the buttons seem to have their text centered - is this deliberate? Does it not look jarring?
It's not that noticeable. I couldn't fix vertical alignment, VerticalContentAlignment="Center" does nothing.

Confirm deletion dialog removes hover effect from list item
Can't fix this. It seems that, because the confirm dialog takes focus, it un-selects items (I tried to forcefully select the list item before/after opening the dialog, doesn't work).

Starts off with Location name preselected
Is that bad? I deliberately added it in if he gets tired of clicking everything and uses tab-navigation.


[1.10.2 - TC6 6.0.BETA3] Arcane Ear (Toggle) not craftable

I can make the Arcane Ear but the Toggle version (Arcane Ear + Lever) does not show up when trying to craft it. JEI doesn't recognize it as an existing recipe as well. I can post a screen shot but I don't think it'll show anything that wasn't said just now.

Its fixed in beta 4


Missing directives

The standalone library contains these directives for the specifier string:
var parses = {
    "a": parseShortWeekday,
    "A": parseWeekday,
    "b": parseShortMonth,
    "B": parseMonth,
    "c": parseLocaleDateTime,
    "d": parseDayOfMonth,
    "e": parseDayOfMonth,
    "f": parseMicroseconds,
    "H": parseHour24,
    "I": parseHour24,
    "j": parseDayOfYear,
    "L": parseMilliseconds,
    "m": parseMonthNumber,
    "M": parseMinutes,
    "p": parsePeriod,
    "Q": parseUnixTimestamp,
    "s": parseUnixTimestampSeconds,
    "S": parseSeconds,
    "u": parseWeekdayNumberMonday,
    "U": parseWeekNumberSunday,
    "V": parseWeekNumberISO,
    "w": parseWeekdayNumberSunday,
    "W": parseWeekNumberMonday,
    "x": parseLocaleDate,
    "X": parseLocaleTime,
    "y": parseYear,
    "Y": parseFullYear,
    "Z": parseZone,
    "%": parseLiteralPercent
};

However, the default bundle (version 4.11.0 at the time of writing) contains only these:
var parses = {
    "a": parseShortWeekday,
    "A": parseWeekday,
    "b": parseShortMonth,
    "B": parseMonth,
    "c": parseLocaleDateTime,
    "d": parseDayOfMonth,
    "e": parseDayOfMonth,
    "H": parseHour24,
    "I": parseHour24,
    "j": parseDayOfYear,
    "L": parseMilliseconds,
    "m": parseMonthNumber,
    "M": parseMinutes,
    "p": parsePeriod,
    "S": parseSeconds,
    "U": parseWeekNumberSunday,
    "w": parseWeekdayNumber,
    "W": parseWeekNumberMonday,
    "x": parseLocaleDate,
    "X": parseLocaleTime,
    "y": parseYear,
    "Y": parseFullYear,
    "Z": parseZone,
    "%": parseLiteralPercent
};

As you can see, it is missing: "f", "Q", "s", "V" and "u".
Because of that, some users are facing issues when using just the default bundle. Two recent examples can be seen here and here  (in this last one the user was incorrectly using "%L", but changing for "%f" - which is the correct specifier - will return null).
I don't know if this was intentional, but I don't think so.
Cheers,

The D3 default bundle does not yet include the latest release of this library but will be updated in the near future.

Thanks for your reply, good to know that. Cheers,

Thanks for your promptly reply. Only after opening this issue I realised that the standalone microlibrary's last version was released on 9th October, while the default bundle's last version was released on 3rd October, and that explains why it doesn't contain the latest directives. I'll be more careful before opening an issue next time.
Cheers,


[owasp] Suppress ZooKeeper 3.8.0 vulnerabilities

Motivation
After the ZK upgrade the OWASP check fails because ZK has known vulnerability. The owasp suppression aims ZK 3.6.2.
Modifications

Edited the ZK suppression to 3.8.0

[x] no-need-doc

We released 3.8.0 last week and the owasp checker passed (I actually cancelled one RC due to a owasp check failure)
I am not aware of any security issue in ZooKeeper
Please explain  more

I get this output
zookeeper-3.8.0.jar<EMAIL_ADDRESS>cpe:2.3:a:apache:zookeeper:3.8.0:*:*:*:*:*:*:*) : CVE-2021-28164, CVE-2021-29425, CVE-2021-34429
zookeeper-prometheus-metrics-3.8.0.jar<EMAIL_ADDRESS>cpe:2.3:a:apache:zookeeper:3.8.0:*:*:*:*:*:*:*, cpe:2.3:a:prometheus:prometheus:3.8.0:*:*:*:*:*:*:*) : CVE-2021-28164, CVE-2021-29425, CVE-2021-34429

For example
https://nvd.nist.gov/vuln/detail/CVE-2021-34429#match-7614933
https://nvd.nist.gov/vuln/detail/CVE-2021-28164#match-7615085

I checked and ZK doesn't contain the mentioned libraries. I don't know how it is the process for that but is ZooKeeper problem.
I will highlight the problem to the ZooKeeper maintainers (or @eolivelli I'll let you proceed if you want)
For now I think we can keep the specific vulnerabilites; actually they are wrong (at a first glance at the ZK repo) so it makes sense to suppress them. btw they are already suppressed now, this will unblock the CI

in the ZK project we added these exclusions due to false positives:
https://github.com/apache/zookeeper/commit/3004c909b78b3056985c8e39925e14bde3baa430
<suppress>
      <!-- Seems like false positives about zookeeper-jute -->
      <cve>CVE-2021-29425</cve>
      <cve>CVE-2021-28164</cve>
      <cve>CVE-2021-34429</cve>
   </suppress>

So it is fine to add the same exclusions there

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks


ARM Neon support?

Hi thanks for the lib! I wonder this library supports ARM neon SIMD instructions?

Rayon doesn't do any explicit instruction-level parallelism, but it's still possible that the LLVM vectorizer will optimize inner loops. We try to push things down to Iterator::fold and the like after splitting it up for thread parallelism.

Thanks!


Enable ApiCheck for Socket Transport

https://github.com/aspnet/KestrelHttpServer/pull/2173/files#r151965500

Looks like we have ApiCheck enabled for all of the Kestrel packages. However, it looks like the base lines are out of date since they were last updated to 2.0. We should set the baselines at 2.1 and then see whether anything changed for 2.2


[HUDI-4994] Fix bug that prevents re-ingestion of soft-deleted Datahub entities

Change Logs
JIRA: https://issues.apache.org/jira/browse/HUDI-4994
Datahub has a notion of soft-deletes (the entity still exists in the database with a status=removed:true). Such entities could get re-ingested with new properties at a later time, such that the older one gets overwritten. The current implementation in DatahubSyncTool does not handle this scenario. It fails to update the status flag to removed:false during ingest, which means the entity won't surface in the Datahub UI at all.
This PR fixes that, via setting status="removed:false" into the metadata object. This will have no impact on new entities, or hard-deleted entities (which will have nothing inside Datahub anyway)
Ref: See sections on Soft Delete and Hard Delete in the Datahub docs: https://datahubproject.io/docs/how/delete-metadata/#soft-delete-the-default.
Impact
Soft-deleted entities will re-surface in UI if re-ingested again, compared to existing behaviour.
Risk level: low
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Added a test as of now. I might add more on the same lines.

CI passed https://dev.azure.com/apache-hudi-ci-org/apache-hudi-ci/_build/results?buildId=12123&view=results


Don't call Az cli command to dry run PITR restore on overview page.

This PR fixes #

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 13 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.004%) to 41.656%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/arc/src/ui/dashboards/miaa/miaaBackupsPage.ts
0
1
0.0%

extensions/arc/src/models/miaaModel.ts
0
12
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.004%

Covered Lines:
27179

Relevant Lines:
59210

💛  - Coveralls

@shagunt @candiceye Is this something you're still planning on getting in?


stuntrally: Compilation fails with "reference to 'optional' is ambiguous"

Steps To Reproduce
Steps to reproduce the behavior:

build stuntrally

Build log (excerpt)
/build/source/source/vdrift/track.cpp:186:1: error: reference to 'optional' is ambiguous
  186 | optional <const BEZIER *> ROADSTRIP::FindBezierAtOffset(const BEZIER * bezier, int offset) const
      | ^~~~~~~~
In file included from include/boost/container_hash/hash.hpp:111,
                 from include/boost/functional/hash.hpp:6,
                 from include/boost/thread/detail/thread.hpp:41,
                 from include/boost/thread/thread_only.hpp:22,
                 from include/boost/thread/thread.hpp:12,
                 from /nix/store/8z6i68vm553b86gi1c6cnxnwfg0mfcj1-ogre-1.9.1/include/OGRE/Threading/OgreThreadHeadersBoost.h:50,
                 from /nix/store/8z6i68vm553b86gi1c6cnxnwfg0mfcj1-ogre-1.9.1/include/OGRE/Threading/OgreThreadHeaders.h:34,
                 from /nix/store/8z6i68vm553b86gi1c6cnxnwfg0mfcj1-ogre-1.9.1/include/OGRE/OgreLog.h:35,
                 from /nix/store/8z6i68vm553b86gi1c6cnxnwfg0mfcj1-ogre-1.9.1/include/OGRE/OgreLogManager.h:34,
                 from /build/source/source/vdrift/../ogre/common/Def_Str.h:5,
                 from /build/source/source/vdrift/configfile.h:8,
                 from /build/source/source/vdrift/track.cpp:5:

Additional context
Fails at 99%
I'm guessing it has to do with the latest 2.6.1 release of stuntrally, but couldn't find the relevant PR
Notify maintainers
@pSub
Metadata
❯ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.27-xanmod1-tt, NixOS, 22.05 (Quokka), 22.05pre368735.33772708c6d`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.7.0`
 - channels(root): `"home-manager, nixos, nur"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Thank you for reporting this issue @ThibaultLemaire. I have updated stuntrally to 2.6.2 and switched to gcc11 in #176001. This builds fine for me. Unfortunately I couldn't test if the game runs due to graphic driver issues on my side. Cloud you give it a try?

Fixed in #176001.

Thank you @pSub and sorry I was facing issues of my own with my box. I'll take the time to report back here when I get around to testing stuntrally :)

Everything's working perfectly, thanks again!


Restamp only specific pages

It would be useful if we could specify which pages to always restamp and which not.

It should be as easy as modifying this line to restamp || this.restamp and adding the property restamp to iron-lazy-page. Could you submit a PR with that? :smile:

Guessing that master has changed  since the above was posted - Is [this the line] you're talking about - I can submit that PR 💯

Yes, but templates and restamping will be removed in 2.0 sadly. See #44

Yikes - that's a shame.
It's not quite clear in #44 as to why they are being removed.

Is it because they are not supported in all major browsers?

First of all type extension is not supported by all major browsers.
It is therefore not possible to rely on

Is it because it's more clean and lean to not use templates at all?

Secondly, upgrading from iron-pages to iron-lazy-pages was quite intrusive
and the template syntax was confusing to users.

If the 1st point is the case then perhaps the Polymer team can shed some light as to why it's not working cross-browser. If the 2nd point is the case then it's a shame to ditch such a major performance enhancement just for the sake of ergonomics.
I'm pushing this because I've seen major performance improvements when restamping. It allows for very  complex DOM's to be used whilst still keeping performance high - which feels very "native-y"

@nicholaswmin Thanks for the feedback! Could you provide me two timelines: 1. using the current 2.0-preview wihout restamping and 2. the 1.0 version with restamping. I would be very interested in seeing the flamecharts of both actions when navigating between pages. You can upload the data as a gist here on GitHub. Please check out https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/timeline-tool#save_and_load_recordings on how to export the data from the dev tools.
Once again thank you and I am very open to improvements with templates, if we can have data proving the performance gains of restamping.

@TimvdLippe  you got me there.

I'm pushing this because I've seen major performance improvements when restamping

I haven't run any benchmarks at all and the flamecharts don't support so much my case as it is now - I'll call this a white lie and try to get away with it.
It's really about scalability that I'm interested in. I'd like to know that I can keep adding stuff to my DOM and still be careless about it since I can just restamp pages if and when needed.

@nicholaswmin No problem, even if you later find a usecase that does justify template do not hesitate to post it here!

It's really about scalability that I'm interested in. I'd like to know that I can keep adding stuff to my DOM and still be careless about it since I can just restamp pages if and when needed.

To my knowledge, using CSS to show/hide elements is a lot faster than recreating the DOM tree multiple times. Maybe we should ask in the Polymer Slack whether this claim is true. Now the implication of using CSS is that the state is maintained even when the element is hidden. This is something the user of the element should be aware of and is different behavior than in 1.0.

On a different note, my current thinking is supporting dom-if as possible sub-page, but it might have some limitations compared to the previous implementation.

To my knowledge, using CSS to show/hide elements is a lot faster than recreating the DOM tree multiple times

That's true when you have a flat tree of hierarchies in terms of iron-pages.
If an iron-page contains multiple levels of nested iron-pages, restamp should allow much faster switching of the parent iron-page, since it won't need to render all the subpages.
This is still just speculation from my end - I just want to get my use-case across

So, theoretically here's a use case:

A top level iron-page containing 10 subpages.
Each subpage contains a 4 subpages.
For brevity, let's assume that each sub page of either level takes ~50ms to render.

First rendering the component that contains all these iron-pages would need 10 x 4 x 50ms = 2000ms.
With restamp, it would take 100ms since it renders only 1 page out of each level. Things could get messier as more and more levels are added.
Sure, restamp-ing is going to make navigation a bit clunkier. I'd take it that it's a matter of balance between first render time of the whole component, and smoothness when navigating between pages.
The restamping option would, again, theoretically, work wonders if you have many sub-levels with small DOM chunks in each sublevel page. restamp wouldn't create a smoothness issue when navigating and first-render time (or navigating through higher levels) wouldn't need to naively re-render all the lower-level DOM chunks.

restamp can be useful when you have to re-run some iron-ajax requests each time the DOM is recreated.

@nicholaswmin You should be lazy-loading the element definitions instead. Therefore you only pay 1 x 4 x 50ms per page navigation if it is the first time you are navigating to that page. See data-path in the 2.0-preview and path on iron-lazy-page in 1.0.
@web-padawan Yes exactly I do think that is a valid usecase, therefore I am considering to include <dom-if> compatibility

Restamp is also a nice way to do grabage collection of dom elements.

This has been fixed per #48


Gradio Demo ?

Can we have a Gradio Demo of the results (someplace where we can upload a punch of images and it produces the 2d model of it) ?

I don't know how to do it. Do you know?

It's quite simple if you have the process of Nerf in a closed function.
What will you need is an account on huggingface and some knowledge of Gradio (it's really easy) and upload your huggingface space and let us all enjoy it.

It doesn't seem straightforward to me, besides this project requires colmap reconstruction which I believe cannot be easily integrated (notice that instant-ngp also requires running colmap separately). If someone is interested in integrated, you are welcomed to contribute, but this functionality won't be in my plan.


⚠ Spryr has degraded performance

In 31a7a08, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3824 ms

Resolved: Spryr performance has improved in ae49ed4 after 10 minutes.