Add instruction analysis for amd64

Is this a stepping-stone towards dealing with crashes involving non-canonical pointers? (Because it sure feels like it!)

Is this a stepping-stone towards dealing with crashes involving non-canonical pointers? (Because it sure feels like it!)

It is indeed! I think that change will be coming quite shortly!

Is this a stepping-stone towards dealing with crashes involving non-canonical pointers? (Because it sure feels like it!)

Yes! And much more, see a bunch of ideas we had here

I did this mostly because I needed some trait anyway to make it easy to unit test without synthesizing my own fake memory list. I originally had a GetMemoryAtAddress single-function trait and changed it to this. I guess I will just go back to that

I'm always sympathetic to anything that makes it easier to write tests! I think the SynthMinidump bits we have are full-featured enough to make this straightforward. You can see an example of creating a synthetic x86-64 dump in this test:
https://github.com/rust-minidump/rust-minidump/blob/38edd05c27588f573a447d89d07bdba252f601d9/minidump/src/minidump.rs#L6561-L6574
The processor tests have a function to build a minimal minidump that they add additional info to:
https://github.com/rust-minidump/rust-minidump/blob/a6a486b8992008c6865ee70fc68421c38e45ef42/minidump-processor/tests/test_processor.rs#L136-L149
Calling SynthMinidump::add_memory automatically adds the memory region you provide to the minidump and also to the memory list stream.
 The stackwalker tests are a good point of reference, they set up the stack contents to test specific unwind scenarios, you could do virtually the same thing to create memory regions with specific instructions for your tests:
https://github.com/rust-minidump/rust-minidump/blob/a6a486b8992008c6865ee70fc68421c38e45ef42/minidump-processor/src/stackwalker/amd64_unittest.rs#L116-L130

I think with a little bit of up-front work you can write a function that generates suitable synthetic minidumps for your tests so that the individual tests can be very straightforward. I assume most of your tests will just want to test specific instructions, so you could write something like fn create_synth_dump(memory: Memory) -> SynthMinidump. Each test would use the Section APIs to populate the desired instructions then create a Memory with that as its contents and pass it to this function. create_synth_dump would add that memory to the dump, along withat least one thread with stack memory + context, an exception stream + context whose instruction pointer points into memory, and a module and a few other necessary stock bits.
If you get stuck, one of us can help you out.

@luser @Gankra
Alrighty -- In response to your feedback, I have removed the std::io::{Seek, Read} implementations on the memory lists, and now the public op_analysis convenience functions just directly take a &MinidumpMemoryListBase as their memory argument.
The unit tests now just directly use the get_instruction_memory_access() function, which simply takes a instruction_bytes: &[u8], so now I'm just skipping the memory list machinery in my unit tests altogether. I think it's actually better that way anyhow -- The memory list stuff is already well-covered by other tests, so this really breaks the unit tests down to "just test that your new assembly decoding logic is correct".

@Gankra As long as there are no further concerns, I believe this should be good-to-go :)

thanks for all the hard work, sorry for the delays!


Add order_by and limit

Sorry about the formatting, I have the editor to always do rustfmt on save. But maybe it would be good to just run cargo fmt on the whole project?

@FredrikNoren thanks for the PR! If you can, please add a rustfmt.toml and run cargo fmt on the whole project. The reason it looks diferent is because I use weird default settings and never added the rustfmt config to the repo.

@jquesada2016 Done; I just added an empty rustfmt so that it's the default formatting

@FredrikNoren thank you very much!


Can I hook into to send messages to different processes?

can I send messages to different Processes?

Hi @furesoft, no, Actress is a port of the MailboxProcessor from FSharp.Core, and is not a distributed actor framework like Akka.NET or Orleans.


Add custom JWT error messages for authentication failures

Fixes #22

Description

A custom AuthenticationEntryPoint has been implemented named JwtAuthenticationEntryPoint which intercepts any JWT Exceptions from the SecurityFilterChain and sets up the ProblemDetails accordingly  wrapped inside the ErrorRes Object . The response content type has been set to "application/json" for increased readability.
Screenshots

Hello @nmarulo, please check this PR also I has some queries:

The security filter chain allows all the request to be accessed without any authentication.
Are you planning on opening up the "/api/auth/**" open to everyone and then make the rest of the URL authenticated?
If so should this PR address this or is this going to be handled later on?

Hello @nmarulo, please check this PR also I have some queries:

The security filter chain allows all the request to be accessed without any authentication.

If this is correct, I want to be able to test the application without logging in or registering.

Are you planning on opening up the "/api/auth/**" open to everyone and then make the rest of the URL authenticated?

Yes, the idea is that if you want a private list, you will have to register and log in.

If so should this PR address this or is this going to be handled later on?

No, I just want if the token fails to return a custom message in the response body.

Also I forgot to mention to be able to test if the authentication handling is correct or not we can customize the SpringFilterChain accordingly:
    @Bean
    public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
        http.securityMatcher(appProperties.getPathPrefix() + "/**")
            .authorizeHttpRequests(authorize -> {
                authorize.requestMatchers(appProperties.getPathPrefix() + "/auth/**")
                         .permitAll()
                         .anyRequest()
                         .authenticated();
            })
            .httpBasic(AbstractHttpConfigurer::disable)
            .csrf(AbstractHttpConfigurer::disable)
            .sessionManagement(session -> session.sessionCreationPolicy(SessionCreationPolicy.STATELESS))
            .oauth2ResourceServer(configOAuth2())
            .cors(value -> value.configurationSource(corsConfigurationSource()));

        return http.build();
    }

This way we can get the bearer token after logging in then access all the other endpoints with the valid bearer token. If the bearer token is invalid (manipulation) or expired, the response body should output a custom error message with all the necessary details accordingly. Thanks!

@JinnJarBurger Thanks 👍

@JinnJarBurger Thanks 👍

Anytime! 😃


A few dataframe metadata fixes

Due to a bug in dd.utils.assert_eq, we weren't properly testing that index metadata was correct. This fixes that, as well as issues this turned up.

Use _meta_nonempty in assign
Use _meta_nonempty in groupby aggregations
Error nicely when trying to infer metadata from a dask.delayed
object (which we can't do since it could be any dtype).
Fix dd.utils.assert_eq to properly compare index dtypes

Fixes #2564.

Thanks for finding and resolving this @jcrist !
I'm curious, are the parquet errors related, or are they due to something else?

Not sure, I can take a look tomorrow.

This is due to a bug in our index metadata handling for pyarrow 0.13.0. I spent 20 mins or so trying to debug and haven't found an easy solution (the test fixes here turned up a few bad code paths). With our desire to rewrite all the parquet handling anyway, and other pyarrow 0.13.0 issues (no pickle support) would it be fine to just skip these tests?

Alternatively we could just error nicely if pyarrow 0.13 is installed and recommend people downgrade/upgrade? I'm not sure what the complete parquet & pyarrow 0.13.0 status is, but until we do a clean rewrite there may be too many bugs for me to completely trust the index handling logic here.

Some things are still broken after https://github.com/dask/dask/pull/4668 ?
The general problem with inference from parquet is that there are genuinely many possibilities in the schema contents, the file organisations and further metadata present in the files, and the engines' view of it (the latter of which may depend on version, as in the present case of arrow0.13). So partly the code is convoluted because it grew organically to accommodate a moving target, but also in no small part it reflects a genuinely complex situation. I've tried to be as clear as I can about the situation in comments in https://github.com/dask/dask/pull/4336 .
A "clear rewrite" should probably include stricter version requirements.
Since arrow is actively working on the parquet story for the next release, including pickle and metadata-file handling, I would be OK skipping some tests for now. Whether the rewrite will succeed in making a more maintainable situation remains to be seen.

A "clear rewrite" should probably include stricter version requirements.

+1

So partly the code is convoluted because it grew organically to accommodate a moving target

I recall early conversations when you were writing the first integration where there were open questions of "should this logic go in fastparquet, or in dask.dataframe?" to which we really didn't have any good answers :)

but also in no small part it reflects a genuinely complex situation

Indeed

Whether the rewrite will succeed in making a more maintainable situation remains to be seen.

I think that we're more than capable of making this happen if we act as a group.  I don't think that I am independently capable of this though.
I think that the parquet situation is important for Dask.

Whether the rewrite will succeed in making a more maintainable situation remains to be seen.

I think that we're more than capable of making this happen if we act as a group.

I should clarify that by "success", here, I mean greatly reducing the code complexity and maintenance burden. I'm sure we can make something that work well for the current situation :)

Some things are still broken after #4668 ?

This PR fixes a bug in our test suite that let metadata issues slip through. Yes things are still broken after #4668, and the fix seems to require refactoring the pyarrow code path significantly. To be clear, I'm not attacking the state of the code, I'm just saying that for now it seems easier to either say "don't use pyarrow 0.13.0 with dask" or skip these tests. I don't care which one we choose.

I'm totally ok with a "don't use pyarrow 0.13.0" with Dask warning

don't use pyarrow 0.13.0

Agree, since it doesn't work with distributed anyway

Cool, I'll push that here.

I think this is good to go now.

Merging later today if no comment.


Tune without Launch specialization macros

@piiswrong
Description
(Brief description on what this PR is about)
Checklist
Essentials

[ ] Passed code style checking (make lint)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] For user-facing API changes, API doc string has been updated. For new C++ functions in header files, their functionalities and arguments are well-documented.
[ ] To my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Removed extra workload_ex_ and made workload_ var into the vector of floats that used to be workload_ex_, this dropping the single scalar workload_ concept.


Demo LZ decompress did not work...

In the demo (http://pieroxy.net/blog/pages/lz-string/demo.html), after compressing the readable text, clicking on the LZ decompress button causes does not re-populate the readable text.

You're right. I have screwed up something in there. I'll look into it tomorrow.
Thanks.

There. Not perfect yet, but it's working.


feat(HAM-336) grouping carousel dots

Checklist

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Please check if the PR fulfills these requirements

[x] Tests for the changes have been added (for bug fixes / features)
[x] Storybook or docs have been added / updated (for bug fixes / features)

What is the ticket / issue associated with this change? (Link to the ticket or issue)

HAM-336

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

No breaking changes

Other information:
Storybook Link (Link to a local storybook url to review new functionality)

https://5eed577398d08d0022b52d76-oszkynchge.chromatic.com/?path=/story/carousel-carousel--playground&args=visibleSlides:4;totalSlides:13

there is an issue with the Carousel when using arrows to navigate, which can be reproduced by visiting this story and use the arrows to navigate

Great catch! Thank you!
It turns out that the arrows and dots should be in sync. And for that, we should set the step prop to equal the number of visibleSlides.
Since this is an opinionated version of the Carousel, I have dropped the step prop  because consumers can set the number of visibleSlides instead. That change turns this into a breaking a changing.


How can I build a convolutional neural network with DL4J?

I can't find any Class or API of DL4J can help me build a convolutional neural network.

Little late for me atm...will post an example tomorrow. The crux of it is in <IP_ADDRESS>: everything is a layer. Right now, we have a max pooling layer:
https://github.com/SkymindIO/deeplearning4j/blob/master/deeplearning4j-core/src/main/java/org/deeplearning4j/nn/layers/ConvolutionDownSampleLayer.java

thank you so much.


Corrections to Azure auth service definition after refactor

This adds the missing items from the azure auth support that were causing the head branch code to fail to log in via AAD.
Tested on our installation with head as at 28/02/2020.

Thanks for catching this. Merging your PR...


[bug]: Can't INVOKE, InvokeAI UNUSABLE = Invoker.create_execution_state() got an unexpected keyword argument 'queue_id'

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
8GB
What version did you experience this issue on?
b152fbf
What happened?
I've just did a git pull and i can't invoke anymore.
Whenever i invoke i get this error now:
Invoker.create_execution_state() got an unexpected keyword argument 'queue_id'
This is the log:
[2023-09-22 11:29:21,186]::[uvicorn.access]::INFO --> <IP_ADDRESS>:50921 - "GET /api/v1/images/?board_id=none&categories=general&is_intermediate=false&limit=0&offset=0 HTTP/1.1" 200
[2023-09-22 11:29:34,289]::[uvicorn.access]::INFO --> <IP_ADDRESS>:50924 - "POST /api/v1/sessions/ HTTP/1.1" 500
[2023-09-22 11:29:34,289]::[uvicorn.error]::ERROR --> Exception in ASGI application

Traceback (most recent call last):
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\uvicorn\protocols\http\httptools_impl.py", line 436, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\uvicorn\middleware\proxy_headers.py", line 78, in __call__
    return await self.app(scope, receive, send)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\fastapi\applications.py", line 270, in __call__
    await super().__call__(scope, receive, send)
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\starlette\applications.py", line 124, in __call__
    await self.middleware_stack(scope, receive, send)
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\starlette\middleware\errors.py", line 184, in __call__
    raise exc
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\starlette\middleware\errors.py", line 162, in __call__
    await self.app(scope, receive, _send)
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\starlette\middleware\cors.py", line 92, in __call__
    await self.simple_response(scope, receive, send, request_headers=headers)
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\starlette\middleware\cors.py", line 147, in simple_response
    await self.app(scope, receive, send)
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\fastapi_events\middleware.py", line 43, in __call__
    await self.app(scope, receive, send)
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\starlette\middleware\exceptions.py", line 79, in __call__
    raise exc
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\starlette\middleware\exceptions.py", line 68, in __call__
    await self.app(scope, receive, sender)
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\fastapi\middleware\asyncexitstack.py", line 21, in __call__
    raise e
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\fastapi\middleware\asyncexitstack.py", line 18, in __call__
    await self.app(scope, receive, send)
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\starlette\routing.py", line 706, in __call__
    await route.handle(scope, receive, send)
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\starlette\routing.py", line 276, in handle
    await self.app(scope, receive, send)
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\starlette\routing.py", line 66, in app
    response = await func(request)
               ^^^^^^^^^^^^^^^^^^^
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\fastapi\routing.py", line 235, in app
    raw_response = await run_endpoint_function(
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\...\invokeai\.venv\Lib\site-packages\fastapi\routing.py", line 161, in run_endpoint_function
    return await dependant.call(**values)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\...\invokeai\InvokeAI\invokeai\app\api\routers\sessions.py", line 33, in create_session
    session = ApiDependencies.invoker.create_execution_state(queue_id=queue_id, graph=graph)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: Invoker.create_execution_state() got an unexpected keyword argument 'queue_id'

Updated with git pull to c485cf5 and still getting the error

Updated to e3de996 and still not working.
InvokeAI is literally unusable, if anyone know a workaround i'll appreciate.

exact same issue here. I'm on e3de996 as well. Cant generate anything, regardless of what settings i try to change.
Windows 11, 8GB RTX 2060 super

Hi, it looks like you haven't rebuilt the UI.
If you use main, you'll need to do that if there are any changes to the UI that are sync'd with changes to the backend.
When we release updates, we do the build for the release. Between releases, main typically does not have a current UI build.
You can see the instructions here for setting up a development environment and then doing a production build: https://github.com/invoke-ai/InvokeAI/blob/main/docs/contributing/contribution_guides/contributingToFrontend.md
That should get your UI updated.
If you don't want to do that, you should revert to a previous commit.

The problem was found and now fixed!

I

Hi, it looks like you haven't rebuilt the UI.
If you use main, you'll need to do that if there are any changes to the UI that are sync'd with changes to the backend.
When we release updates, we do the build for the release. Between releases, main typically does not have a current UI build.
You can see the instructions here for setting up a development environment and then doing a production build: https://github.com/invoke-ai/InvokeAI/blob/main/docs/contributing/contribution_guides/contributingToFrontend.md
That should get your UI updated.
If you don't want to do that, you should revert to a previous commit.

forgive me i am relatively new to coding if i misunderstood the solution there  @psychedelicious
I just ran an update to InvokeAI and got the same error
on PC, I go to invokeai.venv\Lib\site-packages\invokeai\frontend\web, run in windows powershell did a 'yarn install' as per the document says, i got "success Already up-to-date." and assumed that's it.
but still i ran back to the same error when re-run the invoke.bat, did i miss anything?:
File "C:\Users\Adrian\invokeai\.venv\lib\site-packages\invokeai\app\api\routers\sessions.py", line 33, in create_session     session = ApiDependencies.invoker.create_execution_state(queue_id=queue_id, graph=graph) TypeError: Invoker.create_execution_state() got an unexpected keyword argument 'queue_id'

This is expected. You can periodically clean up images using the clear intermediates button in settings.


Default reporter swallow console.log

test.js
import test from 'ava';

test('log test', t => {
	console.log('log1\nlog2');
});

terminal output
log1

  1 passed

Seems like the last string of logged text is swallowed.It complicate debuggin.

I noticed this too. This is because of the animated reporting. Although, logging like that isn't very useful when you have more than one tests as the logging is synchronous while the test is not, so the logging could be outputted with a different test. I think a solution here is to handle the logging so that it's outputted with the correct test in verbose mode and with the default minimal reporter we could either show all logging at the end or during the testing by pushing the animated output down (meaning calling logUpdate.done()).
For now you can use the --verbose flag.
// @vdemedes

I noticed this too. This is because of the animated reporting. Although, logging like that isn't very useful when you have more than one tests as the logging is synchronous while the test is not, so the logging could be outputted with a different test. I think a solution here is to handle the logging so that it's outputted with the correct test in verbose mode and with the default minimal reporter we could either show all logging at the end or during the testing by pushing the animated output down (meaning calling logUpdate.done()).
For now you can use the --verbose flag.
// @vdemedes

I think a solution here is to handle the logging so that it's outputted with the correct test in verbose mode

That would be hard to do with console.log unless we either:

Force --serial when --verbose is used (I don't like this idea).
Use domains to determine which test console.log is used from.
Provide a t.log method.

I think 3 is pretty interesting. It won't help much with capturing logs from production code (unless you use proxyquire to inject it some how). For the verbose reporter, we could always print t.log statements. For the mini reporter, only output logs with failed tests

I think a solution here is to handle the logging so that it's outputted with the correct test in verbose mode

That would be hard to do with console.log unless we either:

Force --serial when --verbose is used (I don't like this idea).
Use domains to determine which test console.log is used from.
Provide a t.log method.

I think 3 is pretty interesting. It won't help much with capturing logs from production code (unless you use proxyquire to inject it some how). For the verbose reporter, we could always print t.log statements. For the mini reporter, only output logs with failed tests

Yes, 3 is what I was thinking.

For the mini reporter, only output logs with failed tests

I think we should still log it with the mini reporter as it's still useful to quickly print out some values.

Yes, 3 is what I was thinking.

For the mini reporter, only output logs with failed tests

I think we should still log it with the mini reporter as it's still useful to quickly print out some values.

@sindresorhus, @jamestalmage: We could also try hijacking/monkey-patching wither process.stdout/stderr or console.log.

Yes, we could, but I have a feeling that comes with a lot of edge-cases, so we should first figure out t.log.

Humble lurker here, so feel free to tell me I'm wrong --
Usually, when I find myself dropping in log statements for debugging, it's in the code under test, not the test itself. If the data I'm trying to learn about is accessible from the test, I'd just write an assertion anyway. I doubt I'd use t.log very much.
I've found debugging particularly tricky when experimenting with AVA since it also seems to give debuggers like node-inspector a hard time. In an ideal world, I'd love to see the log output for failed tests alongside the failed assertion or error. Successful tests could hide logs unless handed --verbose. Of course, easier said than done, right?

I think we should just hide the output from the mini reporter. I've encountered many TAP/mocha reporters, that just don't show console.log()s and that's it. With our animated beauty, there is simply no good way to display console.log() output.

I doubt I'd use t.log very much.

Highly agree with @ecowden, I don't think anyone would use t.log.

But how to debug?

use --verbose

@jamestalmage++

I don't think anyone would use t.log

Yeah, that was my concern as well. However, I think having a way to log output that you can be sure will be printed right underneath the :white_check_mark: of the related test is pretty valuable. Obviously --serial is a way to achieve that.
At some point I think we need to start developing a "best practices / hints and tips / faq" document with stuff like this in it. For example, a good heading for the discussion we are having here would be "Debugging async tests", that talks about the difficulty of debugging async tests (it's hard to reason about console.log statements unless you enable --serial).

For the mini reporter, only output logs with failed tests

I think we should still log it with the mini reporter as it's still useful to quickly print out some values.

@sindresorhus - for quickly printing out some values, console.log works just as well, assuming you intend to delete the log statement later. The output of the mini reporter offers no context for log statements in passing tests anyways. There are advantages to not displaying in the mini reporter unless there is a failure:

The log statements can be given context (by being grouped with the failure output for that specific test).
You can leave the log statements in the test. As long as the test passes, it is not cluttering up your output. If/when the test fails - you are given additional information beyond the simple assertion failure.

The output of the mini reporter offers no context for log statements in passing tests anyways.

Usually I just console log in one place so I don't really need a context, but ok with using --verbose when I do that.

Usually I just console log in one place so I don't really need a context

In that case the mini reporter should be fine. Though maybe we should somehow use hook-std or something to detect a line has been written and avoid deleting lines.

Yup, already suggested something like that initially, using logUpdate.done(). Would be nice.

Yes, we could, but I have a feeling that comes with a lot of edge-cases

Not really. Patching process.stdout, process.stderr and fs.write could do it completely. The only thing that this wouldn't cover is native modules writing to either of those, though that's hard to cover anyway.


No lexicons for ASL 😅

I was looking into this repo and wanted to integrate this repo code with my school project, It would be great if you could provide the lexicons for ASL as well.

Unfortunately, there is no license-permissive ASL lexicon that I am aware of.
If you are familiar with one, please let us know and we could try to add it.
For your school project, if you would like to use a licensed lexicon, you could do that at your own risk. What you must add is a loading function in this file, and then the rest would work normally.

Unfortunately, there is no license-permissive ASL lexicon that I am aware of.

What about this one
https://github.com/sign/translate/issues/135

ASL-Lex won't work, not allowed to download the videos.
MSASL or WLASL maybe?

https://dxli94.github.io/WLASL/

https://www.microsoft.com/en-us/research/project/ms-asl/

https://www.kaggle.com/competitions/asl-signs PopSign ASL might also work

(WLASL has 2000 signs, MSASL has 1000, and PopSign has 250)

Yes, I ended up using WLASL in @SignBridgeApp

hi I am wondering how do you adopt WLASL into download_lexicon?

hi I am wondering how do you adopt WLASL into download_lexicon?

You can check dummy_lexicon folder there, to get the structure to use

@bipinkrish would you like to contribute your code for WLASL for the download_lexicon?

@bipinkrish would you like to contribute your code for WLASL for the download_lexicon?

I could, but for 2,000 words it has 12,000 videos so for each word there is 5-7 video sample. I manually selected the best ones but through code i could just select the first one.

Hi I'm also currently in the process of selecting WLASL videos from https://www.kaggle.com/datasets/risangbaskoro/wlasl-processed. Do you have any specific criteria for video selection? Additionally, would you be able to share the videos you've already selected?

@bipinkrish would you like to contribute your code for WLASL for the download_lexicon?

I could, but for 2,000 words it has 12,000 videos so for each word there are 5-7 video sample. I manually selected the best ones but through code i could just select the first one.

Hi I'm also currently in the process of selecting WLASL videos from https://www.kaggle.com/datasets/risangbaskoro/wlasl-processed. Do you have any specific criteria for video selection? Additionally, would you be able to share the videos you've already selected?

As I said I have done this manually. You can get my selections from the below file
https://github.com/SignBridgeApp/models/blob/main/selection/selected.json

@bipinkrish would you like to contribute your code for WLASL for the download_lexicon?

I could, but for 2,000 words it has 12,000 videos so for each word there are 5-7 video sample. I manually selected the best ones but through code i could just select the first one.

@AmitMY Do you have any suggestions?

Hi I'm also currently in the process of selecting WLASL videos from https://www.kaggle.com/datasets/risangbaskoro/wlasl-processed. Do you have any specific criteria for video selection? Additionally, would you be able to share the videos you've already selected?

As I said I have done this manually. You can get my selections from the below file
https://github.com/SignBridgeApp/models/blob/main/selection/selected.json

Thanks for sharing!


Modular Screens

I am the maker of the military doctrine mod. I recommend the CQUI mod for modular compatibility with my mod so people have a button in the launch bar, otherwise they have to use a hotkey. I'm not sure this has come up before but it seems that since I believe the last patch for CQUI the modularity isn't working. Another version that I have of CQUI from Oct 22nd is working and it did work with the last game patch.
Has something changed since then or is this a problem that has not been addressed?
Thanks in advance!

Do you mean that LuaEvents.LaunchBar_AddExtra() is not working ? You don't have any errors in the logs ?

This is what I had before (taken from an example sukritact had), I noticed that the references were commented out in the launchbar for cqui - was this something causing problems with the latest patch?
I am not getting any log errors.
`local sTooltip = Locale.Lookup("Doctrines[NEWLINE][NEWLINE]View and choose your military doctrines.")
local tButton = {
InstanceType = "LaunchBarItem",
SelectFunc = function() LuaEvents.DoctrineOpenManager() end,
IconTexture = "LaunchBar_Hook_Doctrine.dds",
Tooltip = "Doctrines[NEWLINE][NEWLINE]View and choose your military doctrines."
}
table.insert(g_TrackedItems, tButton)
-- ===========================================================================
-- Just in case we need to make changes to the button
-- We can grab the instance from the global table via the unique tooltip!
-- ===========================================================================
local DoctrineInstance
function Doctrine_OnLoadScreenClose()
for i,v in ipairs(g_TrackedInstances) do
if v.LaunchItemButton:GetToolTipString() == sTooltip then
v.LaunchItemButton:SetTexture("LaunchBar_Hook_DoctrineButton.dds")
DoctrineInstance = v
break
end
end
end
Events.LoadScreenClose.Add(Doctrine_OnLoadScreenClose)`
I tried to implement it through the examples shown for Modular Screens but this did not work either, though this I cannot confirm was working before so maybe I missed something in this code.
`function Doctrine_OnLoadScreenClose()
PRINT('LOADING DOCTRINE BUTTON');
textureOffsetX, textureOffsetY, textureSheet = IconManager:FindIconAtlas("ICON_UNIT_JAPANESE_SAMURAI", 38);
local button2Info = {
-- ICON TEXTURE
IconTexture = {
OffsetX = textureOffsetX;
OffsetY = textureOffsetY+3;
Sheet = textureSheet;
Color = UI.GetColorValue("COLOR_PLAYER_BARBARIAN_PRIMARY");
};
	-- BASE TEXTURE (Treat it as Button Texture)
	BaseTexture = {
	  OffsetX = 0;
	  OffsetY = 0;
	  Sheet = "LaunchBar_Hook_Doctrine";
	  -- Color = UI.GetColorValue("COLOR_BLUE");
	  HoverOffsetX = 0;
	  HoverOffsetY = 0;
	};

	-- BUTTON INFO
	Callback = function() LuaEvents.DoctrineOpenManager() end;
	Tooltip = "Doctrines[NEWLINE][NEWLINE]View and choose your military doctrines.";
  }

 LuaEvents.LaunchBar_AddIcon(button2Info);

end
function Initialize()
Events.LoadScreenClose.Add(Doctrine_OnLoadScreenClose);
end
Initialize();`

Ok I have figured this out, I just placed onloadscreen into my doctrine UI panel instead of seperate and it works. Thanks

Glad that you figured it out ! 👍


Add animation options to tabris-templates

Add snippets for animation options.

@cpetrov note I would like to support that with tern https://github.com/angelozerr/tern-guess-types


Nakamoto can sync blockchain and scan for transactions

To be used with Sosthene00/donationwallet@6846ab1a676a0cd98bc12ce135f6932b83c3e95a

Looks good,  send_nakamoto_run is called in a commit earlier than the Add Nakamoto run stream commit, but I'll squash them so they are in the same commit


Laplacian pyramid

@LakshmiKumar23 this commit has only one file change, is this ready to be merged?

@kiritigowda Yes, that's all @hansely commited. Is this correct @hansely?


TiFlash server can not restart normally when meet tidb#31048

Enhancement
A user met this error when using tidb v5.2.2 https://github.com/pingcap/tidb/issues/31048. The error message indicates that tidb-server unexpectedly change the column type from Nullable(datetime(0)) to Nullable(int).

After that, the user set the tiflash replica to be 0 for the table (with table_id=756 in this case) through SQL, and restarts all three TiFlash servers. However, after restarted, two of the TiFlash server can restart but one TiFlash server can not restart normally. This made trouble for the user cause it made almost all queries to the TiFlash server fail.

We'd better figure out after setting the tiflash replica to be 0, why 2 out of 3 TiFlash servers can restart normally but 1 of them is NOT.
Minimizing the impact on users after this kind of exception (e.g. make the tiflash server can restart and serve queries to other tables that don't meet this exception)

After user setting the tiflash replica to be 0, we may accept the column type change from datetime to int. But the log above is not as expected.
https://github.com/pingcap/tiflash/blob/ad6b8310fc733045ae7f188c22726620706a513f/dbms/src/TiDB/Schema/SchemaBuilder.cpp#L1298-L1304
https://github.com/pingcap/tiflash/blob/ad6b8310fc733045ae7f188c22726620706a513f/dbms/src/Storages/StorageDeltaMerge.cpp#L1066-L1095

/assign hongyunyan

close as not reproducable


Finetuning in ocrd-train

In the Makefile, here is the code for finetuning
ifdef START_MODEL
$(LAST_CHECKPOINT): unicharset lists $(PROTO_MODEL)
mkdir -p data/checkpoints
lstmtraining
--traineddata $(PROTO_MODEL)
--old_traineddata $(TESSDATA)/$(START_MODEL).traineddata
--continue_from data/$(START_MODEL)/$(START_MODEL).lstm
--net_spec "[1,36,0,1 Ct3,3,16 Mp3,3 Lfys48 Lfx96 Lrx96 Lfx256 O1chead -n1 data/unicharset]"
--model_output data/checkpoints/$(MODEL_NAME)
--learning_rate 20e-4
--train_listfile data/list.train
--eval_listfile data/list.eval
--max_iterations 10000
Why do we need the following line? I thought it was only used in training from scratch.
--net_spec "[1,36,0,1 Ct3,3,16 Mp3,3 Lfys48 Lfx96 Lrx96 Lfx256 O1chead -n1 data/unicharset]" \
Should the learning rate be set lower for fine-tuning?  The learning rate for training from scratch is 20e-4, so it would seem that the learning rate for fine-tuning should be significantly lower?
--learning_rate 20e-4 \

Used https://github.com/OCR-D/ocrd-train/blob/f89efdd46c01aedea615d35e0561c50d7f86e584/Makefile

See https://groups.google.com/forum/#!topic/tesseract-ocr/tmXv6U8Dviw

See https://groups.google.com/forum/#!topic/tesseract-ocr/tmXv6U8Dviw


Remove syslog support (inappropriate) and replace with pipe to logger (for use in scans)

Syslog support removed. Not currently used for scanning mechanism, so ignoring that part.


Handle fetching media length for large number of files

It should be possible to load thousands of files at once. We need a strategy for getting file duration which does not kill the browser. Maybe we schedule a few at a time? Maybe we do this in a web worker?

https://github.com/captbaritone/winamp2-js/commit/5836e9f542d1ac51decf833c8bb6c6d0ce56ce18


Implement testing for functions in read_count_functions.R

Via #153
Create testing for functions in read_count_functions.R to check inputs & outputs are valid and verify how/whether they work.

duplicate of #258; closing

duplicate of #258; closing


Add shot for simultaneous switches

This came from the idea of wanting a way to do a "flipper cancel" for bonus, cut scenes, etc. Originally I thought we could post an event when both flippers were active at the same time, but why reinvent the wheel?
Let's add an option to shots where you can specify a shot based on two or more switches being active at the same time. That way we could create a "flipper_cancel" shot and the game could simply enable it when it wanted to watch for it.

I think a regular shot here is fine. Give it two switches and a really low delay, like 100ms. Since nobody actually hits the flipper buttons simultaneously anyway (there's always some slop), that should work.

use a logic block with a timeout


update etcd to 3.3.1

Coverage decreased (-3.4%) to 81.159% when pulling 0bce1f22f39abd17b0f491dcc76cebc7b138fcf9 on xyl_update_etcd into a74e13012f27a4ea5c4d95cc6c09b531d3d0ed8b on master.


[BUG] - Can't deploy on azure if project name includes a dash

Describe the bug
I tried deploying on Azure with the project name dd-nebari and the deployment had an error.  I didn't copy it but the error mentioned this line.  It seems likely that using "a" as the escape character makes it impossible to tell if other "a" characters are escape characters or not, but I haven't tracked this down specifically.
Expected behavior
No error
OS and architecture in which you are running Nebari
Linux x86-64
How to Reproduce the problem?
See above
Command output
2024.3.3

Versions and dependencies used.
No response
Compute environment
Azure
Integrations
No response
Anything else?
No response

Just tried to deploy Nebari on Azure with the project name ne-bri and I get the following error just after the terraform state resource group, storage container, and storage account are created.
[terraform]: module.terraform-state.azurerm_resource_group.terraform-state-resource-group: Creating...
[terraform]: module.terraform-state.azurerm_resource_group.terraform-state-resource-group: Creation complete after 1s [id=/subscriptions/901d2965-5cce-4799-aa15-44991169568b/resourceGroups/ne-bri-dev-state]
[terraform]: module.terraform-state.azurerm_storage_account.terraform-state-storage-account: Creating...
[terraform]: module.terraform-state.azurerm_storage_account.terraform-state-storage-account: Still creating... [10s elapsed]
[terraform]: module.terraform-state.azurerm_storage_account.terraform-state-storage-account: Still creating... [20s elapsed]
[terraform]: module.terraform-state.azurerm_storage_account.terraform-state-storage-account: Creation complete after 23s [id=/subscriptions/901d2965-5cce-4799-aa15-44991169568b/resourceGroups/ne-bri-dev-state/providers/Microsoft.Storage/storageAccounts/nebridevxhz2]
[terraform]: module.terraform-state.azurerm_storage_container.storage_container: Creating...
[terraform]: module.terraform-state.azurerm_storage_container.storage_container: Creation complete after 0s [id=https://nebridevxhz2.blob.core.windows.net/ne-bri-dev-state]
[terraform]:
[terraform]: Apply complete! Resources: 3 added, 0 changed, 0 destroyed.
[terraform]: [terraform]:
[terraform]: Initializing the backend...
[terraform]: Upgrading modules...
[terraform]: - kubernetes in modules/kubernetes
[terraform]: - registry in modules/registry
[terraform]: ╷
[terraform]: │ Error: Failed to get existing workspaces: Error retrieving keys for Storage Account "nea2Dbridevxhz2": storage.AccountsClient#ListKeys: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ResourceNotFound" Message="The Resource 'Microsoft.Storage/storageAccounts/nea2Dbridevxhz2' under resource group 'ne-bri-dev-state' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix"```

The issue is that we mutate the project_name to get the storage account name (e.g. strip dashes), but we create the storage account in a different place from where we read the storage account name and we don't apply the same mutation when we're creating the storage account as we do when we're reading (terraform importing) the storage class name.
So with a project name of ne-bri. we end up creating a storage account called nebridevxhz2, but then Nebari looks for a storage account called nea2Dbridevxhz2


ExternalDNS attempts to create records in the wrong zone.

From slack:
Eric Greer [7:24 AM]
Hey guys, Just joined up on the k8s slack here…
[7:24]
I was looking for channels and wanted to mention something we hit today with external dns
[7:24]
We noticed that external dns was having a permissions issue with creating external records in route 53, but we had granted it access
[7:25]
closer inspection revealed that it was attempting to register the entry in the wrong domain… We have several k8s in that same VPC
[7:25]
the domain we expected it to register DNS entries in was k8s.aor.company.com, but it appeared to somehow enumerate and attempt to register in k8s-circus.aor.company.com
[7:26]
i havent looked in the code or anything, but my team members today mentioned that this appeared to be a bug in extenal dns. After granting permmissions to the incorrect k8s-circus.aor.company.com domain, external dns was able to make entries in the correct k8s.aor.company.com domain
[7:27]
it appears there is some kind of enumeration on X.aor.company.com that fails?

Hi, I work with Eric Greer - here is some clarification on this issue:
We have two kubernetes clusters in one AWS region.  These two clusters were created with KOPS and have their own Route53 regions - k8s.aor.company.com and k8s-circus.aor.company.com.  Additionally we have a Route53 zone we had previously created - aor.company.com.
Our k8s.aor.company.com kubernetes cluster has permissions (by default) to edit its own route53 zone, and we have given it additional permissions to the aor.company.com zone.  We are attempting to use external-dns to create an entry in aor.company.com. Pods with correct (they work in other regions with a single kubernetes cluster and even worked in this region before we added the circus cluster) external-dns annotations fail to create the expected route53 entries due to an AWS permissions error:
time="2017-11-27T21:22:50Z" level=error msg="AccessDenied: User: arn:aws:sts::REDACTED:assumed-role/nodes.k8s.aor.company.com/i-027b669412571fa08 is not authorized to perform: route53:ListResourceRecordSets on resource: arn:aws:route53:::hostedzone/Z2MT32GMFXJQT
Z2MT32GMFXJQT is the hosted zone for k8s-circus.aor.company.com and is completely unrelated and totally separate from the k8s.aor.company.com cluster.  It appears that external-dns is attempting to scan every route53 zone that matches the aor.company.com pattern and fails when trying to scan the unrelated k8s-circus.aor.company.com zone because it doesnt (and shouldnt) have permissions to that zone.
TL:DR -
Expected:
External-dns has permissions to the zone we are asking it to create records in and is able to create said records. Record.aor.company.com would only need permissions in aor.company.com to create this record.
Actual behavior:
External-dns appears to try to list every zone that matches the requested record.  Record.aor.company.com wants permissions to aor.company.com, k8s.aor.company.com, k8s-circus.aor.company.com and presumably any other zone we create that contains aor.company.com even though these zones aren't where the record is being created and some are completely unrelated to the kubernetes cluster in question.

@lolimjake Awesome, makes total sense. I'll try to discuss it tomorrow and we make a fix soon-ish if nobody beats us to it.
Summary (applies to AWS): ExternalDNS retrieves a list of hosted zones but might not have access to read/write records in each of them. It should not fail because of it. Furthermore, the zone auto-detection should refrain of trying to create records in zones where we don't have permission.


transform: remove ".ts" extension in output

Given that this is typically used for library/bundler transformations, the generated output shouldn't contain extensions in the output.
I suppose the jury can still be out in regards to JS extensions, but TS extensions should definitely not be there.
Input
// src/walk.ts
import { join } from 'node:path';
import * as walk from './walk.ts';
import type { Options } from './walk.ts';

export type { Options };

export function up(name: string, options?: Options): string | undefined {
  // ...
}

Output
// output/find.mjs
import { join } from "node:path";
import * as walk from "./walk.ts";
export function up(name, options) {
  // ...
}

// output/find.d.mts
import type { Options } from "./walk.ts";
export type { Options };
export declare function up(name: string, options?: Options): string | undefined;

Note that both the generate dts and JS still contains the walk.ts reference.

Desired
// output/find.mjs
import { join } from "node:path";
import * as walk from "./walk";
export function up(name, options) {
  // ...
}

// output/find.d.mts
import type { Options } from "./walk";
export type { Options };
export declare function up(name: string, options?: Options): string | undefined;

Because this particular case is a library, ./walk will be re-resolved to the correct "exports" condition when needed.
And arguably, any bundler (or even runtime) contexts that ingest an extension-less import will still be able to resolve the local file sibling.

Hi Luke, are we talking about a feature request for the up coming transformer https://www.npmjs.com/package/oxc-transform or something else?

Hey -- Yes, I'm using that package, but it's currently a bug and not a feature request. When generating TS source to JS, the generated JS still has imports referencing *.ts files.

For reproduction:
import { transform } from "oxc-transform";

let sourceText = `
import { join } from 'node:path';
import * as walk from './walk.ts';
import type { Options } from './walk.ts';

export type { Options };

export function up(name: string, options?: Options): string | undefined {
  // ...
}
`
console.log(transform("asdf.ts", sourceText, {
  typescript: {
    onlyRemoveTypeImports: true,
    declaration: true,
  }
}))

{
  sourceText: 'import { join } from "node:path";\n' +
    'import * as walk from "./walk.ts";\n' +
    'export function up(name, options) {}\n',
  declaration: 'import type { Options } from "./walk.ts";\n' +
    'export type { Options };\n' +
    'export declare function up(name: string, options?: Options): string | undefined;\n',
  errors: []
}

(On an unrelated note, sourceText is kinda a funny name for generated output. Renaming it is obviously breaking, but I'd suggest something like contents or javascript because "source text" makes me think it's the TypeScript source.)

@Dunqing apparently we need to port https://babel.dev/docs/babel-preset-typescript#rewriteimportextensions
import { transformSync } from "@babel/core";

let sourceText = `
import { join } from 'node:path';
import * as walk from './walk.ts';
import type { Options } from './walk.ts';

export type { Options };

export function up(name: string, options?: Options): string | undefined {
  // ...
}
`

console.log(
transformSync(sourceText, {
presets: [["@babel/preset-typescript", { onlyRemoveTypeImports:true, rewriteImportExtensions:true }]],
filename: 'script.ts',
})
)
  code: "import { join } from 'node:path';\n" +
    'import * as walk from "./walk.js";\n' +
    'export function up(name, options) {\n' +
    '  // ...\n' +
    '}',

(On an unrelated note, sourceText is kinda a funny name for generated output. Renaming it is obviously breaking, but I'd suggest something like contents or javascript/js because "source text" makes me think it's the TypeScript source.)

We'll align everything with babel.

That "./walk.js" output is still incorrect/invalid. There needs to be no extension.

Interesting, I suppose we need to change the API to allow removal. I see people had to come with more plugins to fix this problem https://www.npmjs.com/package/babel-plugin-replace-import-extension?activeTab=readme 🤯

rewriteImportExtensions: 'rewrite' | 'remove' | false

Well, babel predates TS and export conditions, which are the two main players in affecting path resolution. Babel also positions itself & wants to be the be-all, end-all... AKA, it assumes it's always the final build.
I didn't know that OXC is aligning with Babel. NGL that makes me really nervous

I didn't know that OXC is aligning with Babel

Our goal is not 100% compat, but we are currently aligning with Babel 8 to bootstrap ourself, otherwise we'll never ship. (Babel 8 is never going to be shipped isn't it ...)
We can always bend the API to allow current and future use cases.

The latest<EMAIL_ADDRESS>includes the option rewriteImportExtensions: 'remove', but it's not declaration yet.
In:
let ret = transform("asdf.ts", sourceText, {
  typescript: {
    onlyRemoveTypeImports: true,
    rewriteImportExtensions: 'remove',
    declaration: true,
  }
});

console.log('Transformed:')
console.log(ret.code);

console.log('Declaration:')
console.log(ret.declaration);

Out:
Transformed:
import { join } from "node:path";
import * as walk from "./walk";
export function up(name, options) {}

Declaration:
import type { Options } from "./walk.ts";
export type { Options };
export declare function up(name: string, options?: Options): string | undefined;

Declarations shouldn't remove extensions right? Otherwise type resolution will fail.

They should be removed. If only publishing a build/ directory with the JS and DTS, the dts points to nothing if retains the *.ts import

They should be removed. If only publishing a build/ directory with the JS and DTS, the DTS points to nothing if retains the *.ts import

I don't fully understand why we need to remove them, I have tried the above example in tsc, and our output is the same as tsc's.


No intellisense for typings even with jsconfig.json created

I have typings/extjs/ExtJS.d.ts and jsconfig.json at root level of my Sencha ExtJS 6 project folder:
{
    "compilerOptions": {
        "module": "commonjs",
        "target": "ES5",
        "outDir": "out",
        "noLib": true,
        "sourceMap": true
    },
    "exclude": [
        "node_modules",
        "ext",
        "overrides",
        "resources",
        "sass",
        "build",
        "packages",
        "help"
    ]
}

When I open any js file I just get a popdown Warning saying:
Sorry, but there are too many JavaScript source files for VS Code. Consider using the exclude-property in jsconfig.json.

And no IntelliSense.
I have another web project that is not a Sencha MVC project, but uses ExtJS 4 on js files. In this project I get no warnings, but I get no IntelliSense as well.

There an issue with exclude properties not being honoured property. It got fixed with the work on #703

I see. I understand it is two distinct issues so.
1- Is too many files to deal with because ignore is being... ignored.
2- Is no IntelliSense even in small projects where ignore can be ignored. (What makes me create this issue)

We cannot handle large amount of files in web workers - Will be fixed by adopting project Salsa asap Microsoft/TypeScript#4789
Failing to handle the exclude-property correctly leads to large project (node_modules et al). That is fixed in master (#703)


Overwrite centroids instead of adding to file

When rerunning Stage2, new centroids will be appended to the end of the output file instead of overwriting the file.

Fixed in ac2f0f7


Wrong redis version used

Environment

docker-redis-cluster version: 6.0.10
redis-server version: 6.0.10
git hash (If applicable): latest
CLI command used to build the container: docker-compose up --build redis-cluster

Steps to Reproduce
I have the following Dockerfile and docker-compose file.
# Dockerfile.redis
FROM grokzen/redis-cluster

version: '3.8'
services:
  redis-cluster:
    build:
      context: .
      dockerfile: ./Dockerfile.redis
      args:
        - redis_version=6.2.0
    environment:
      - INITIAL_PORT=7000
      - MASTERS=3
      - SLAVES_PER_MASTER=1
      - IP=<IP_ADDRESS>
    ports:
     - 7000-7005:7000-7005

After the docker-compose build command I ssh into the container I got redis version 6.0.1 instead of 6.2.0
root@e4bc4c9006af:/data# redis-server --version
Redis server v=6.0.1 sha=00000000:0 malloc=jemalloc-5.1.0 bits=64 build=0

Expected Behavior
When I run redis-server --version inside the container I should get 6.2.0

Observed Behavior
I got back 6.0.1 instead of 6.2.0

@kristof-kasa You are using the args value wrong. Please reference the example file in the repo for exact syntax https://github.com/Grokzen/docker-redis-cluster/blob/master/docker-compose.yml
It should be
    build:
      context: .
      args:
        redis_version: '6.2.0'

Still the same issue sadly.

What versions of docker compose and docker are you running? There is no issue on my end running this with the args i specified. Are you really sure you are running the same build that you built? If you rebuild the image, look in the stdout on the step where it downloads from redis if it uses the redis version you specify or if it downloads anything else. Also note that if it would not be using the variable you specify then it should download latest 6.2 release so you even getting the wrong major version makes even less sense


Have dnstap info send to external dnstap collector

related: ensure there is a good example of how to do this, order of processes to be started and reasonable documentation.  Many of the dnstap parsers expect a pre-existing unix socket and listener on them to be started before you start your daemon.


Changes API

This API will detect changes in Graph API and notify users in Graph Explorer with a blue star on the samples with changes.
Requires intelligent mapping on the url to detect the query that the user types and checks if it has changed in the recent past.

Created this as a project instead of an issue.


Emulator UI does not show up on Windows w/ WSL2

Note: As I was writing this I realized it probably is more of a Emulator UI issue. I created a new ticket there but am fairly new to this and not sure if I should close this or admin
New Ticket: https://github.com/firebase/firebase-tools-ui/issues/377
Browser: Google Chrome (Also tested firefox/edge)
Browser version: Version 86.0.4240.75 (Official Build) (64-bit)
Operating system: Windows 10 Pro Version 2004
Running WSL2 with Ubuntu 20.04
uname -r : 4.19.128-microsoft-standard
Operating system version:
What steps will reproduce the problem:

I follow the through step 3 (no issues yet)
On step 4 I run firebase emulators: start

What is the expected result?
I should be able to login web UI via localhost:4000
What happens instead of that?
The emulators seems to start ok
tom-linux@DESKTOP:~/emulators-codelab/codelab-initial-state$ firebase emulators:start
i  emulators: Starting emulators: functions, firestore, hosting
⚠  functions: The following emulators are not running, calls to these services from the Functions emulator will affect production: auth, database, pubsub
⚠  Your requested "node" version "8" doesn't match your global version "12"
i  firestore: Firestore Emulator logging to firestore-debug.log
i  hosting: Serving hosting files from: public
✔  hosting: Local server: http://localhost:5000
i  ui: Emulator UI logging to ui-debug.log
i  functions: Watching "/home/tom-linux/emulators-codelab/codelab-initial-state/functions" for Cloud Functions...
✔  functions[calculateCart]: firestore function initialized.

┌───────────────────────────────────────────────────────────────────────┐
│ ✔  All emulators ready! View status and logs at http://localhost:4000 │
└───────────────────────────────────────────────────────────────────────┘

┌───────────┬────────────────┬─────────────────────────────────┐
│ Emulator  │ Host:Port      │ View in Emulator UI             │
├───────────┼────────────────┼─────────────────────────────────┤
│ Functions │ localhost:5001 │ http://localhost:4000/functions │
├───────────┼────────────────┼─────────────────────────────────┤
│ Firestore │ localhost:8080 │ http://localhost:4000/firestore │
├───────────┼────────────────┼─────────────────────────────────┤
│ Hosting   │ localhost:5000 │ n/a                             │
└───────────┴────────────────┴─────────────────────────────────┘
  Other reserved ports: 4400, 4500

Issues? Report them at https://github.com/firebase/firebase-tools/issues and attach the *-debug.log files.

However I can't access the UI via any web browser
I get Error: ERR_CONNECTION_RESET
At first this seems very similar to:
https://github.com/firebase/firebase-tools-ui/issues/332
However users in that thread were able to
1.) Access the UI using the linux host IP address in place of local host
2.) Had a successful work-around using: microsoft/WSL#5706 (comment)
That leads to running a custom script here: #4150 (comment)
After adding additional ports: 22,80,443,8080,10000,3000,4000,5000,5001,8081,8082,4200,3128,4400,4500
However both of the above workarounds do not work with my setup.
Additional Debug Logs
firebase-debug.log
firestore-debug.log
ui-debug.log

@b0ot thanks for filing this feedback and for doing your research.  As you noticed this is the larger issue being discussed in https://github.com/firebase/firebase-tools-ui/issues/332 ... the thing is we have not yet been able to identify a solution for everyone or identify a root cause.  It seems that workaround work for some, but not others.
I'm going to leave this open in case some other codelab user can point out a potential solution!  But I personally don't have any advice for you beyond the various workarounds on the threads you linked.

@samtstern  Appreciate the feedback.
Two pieces of additional information

Additional Information on Bug
Potential Workaround Idea

1.)
I should note that I am able to access other services that are being run on the same WSL2 Ubuntu system.
Examples:

(Quasar | Vue | Firebase) project via (quasar run dev) port: 8080, 8082, 8084, 8086
Many other web projects via (npm run serv) port 8080
To answer your next question: No, I'm not trying to run the emulators suite while also running these other projects. 👍

2.)
As I mentioned, I'm fairly new to web programming so apologies if this is off track but I was curious if it might be possible to setup a solution in Windows using Docker.
The main goals in using WSL2 was to

Keep projects seperate from my main Windows OS
Easier command line support

Would it be possible to meet these goals where one could get the codelab running in a docker solution?
Eventually I'm interested converting my projects using firebase from WSL2 to another solution until the emulator suite / WSL2 integration is fixed.  I thought Docker might be the next best option.

This should be fixed with Firebase CLI v8.15.1. See https://github.com/firebase/firebase-tools-ui/issues/332#issuecomment-722742959 for details. If you still see the issue, just kindly open a new issue in firebase-tools.


Cannot achieve paper's RawNet3 results using an official recipe

Dear author,
I cannot reimplement the paper's results using the RawNet3 script, which should get EER 0.8932. I am wondering if the paper's result is wrong. Can you please upload a recipe so that we can reimplement the result on paper?

Hi, can you share your results?
I cannot share the exact training recipe because it includes internal codes, which is one of the reasons why I shared trained weight parameters.
However, model architecture is exactly the same and you should be getting similar results.

Hi, we're encountering a similar issue. The pre-trained RawNet3 achieves an EER of 0.9809% with the full-length enroll and full-len test utterances. But when we train RawNet3 with the voxceleb1 & 2 dev set and use noise and reverberation addition as augmentation methods, the EER increases to 1.20% after 40 epochs. Besides, the EER  rises to 1.4% after applying speed perturbation for voxceleb 2 dev.
During training, the mixedprec and distributed arguments are used to accelerate training.
Could you please provide some advice on how to address this?  Thank you!

@JunLi0514 , hi, thanks for reporting your status. Speaking of EER 0.98%, did you follow the same setup by segmenting it into ten 4-second segments? If you input the full-length utterance, it would be different to what we did and hence result might be affected.
Note that I trained RawNet3 using another codebase. Only the model architecture has been updated to this repo (VoxCeleb_trainer).
FYI, due to my changed affiliation, I recently developed a RawNet3 reproducible recipe in ESPnet2, where I achieved EER of 0.73% with RawNet3 and it was reproducible several times when tested.

Hi, @Jungjee , thank you for your quick reply! The work is impressive and the training recipe described in the paper is detailed. With your kind advice, we'll test the pretrained model with a duration of 4s and try training on  ESPnet2 ^ ^


"saved model" or .ONNX format of PreTrained 20180402-114759 model?

Does someone have it, or is able to create it?

To create a saved model you can use the following code:
`import tensorflow._api.v2.compat.v1 as tf
tf.disable_v2_behavior()
from tensorflow.python.saved_model import signature_constants
from tensorflow.python.saved_model import tag_constants
def covert_pb_to_server_model(pb_model_path, export_dir, input_name='input:0', output_name='output:0'):
graph_def = read_pb_model(pb_model_path)
covert_pb_saved_model(graph_def, export_dir, input_name, output_name)
def read_pb_model(pb_model_path):
with tf.gfile.GFile(pb_model_path, "rb") as f:
graph_def = tf.GraphDef()
graph_def.ParseFromString(f.read())
return graph_def
def covert_pb_saved_model(graph_def, export_dir, input_name='input:0', output_name='output:0'):
builder = tf.saved_model.builder.SavedModelBuilder(export_dir)
sigs = {}
with tf.Session(graph=tf.Graph()) as sess:
	tf.import_graph_def(graph_def, name="")
	g = tf.get_default_graph()
	print(input_name)
	print(output_name)
	all_ops = [op.name for op in g.get_operations()]
	for name in all_ops:
		print(name)
	inp = g.get_tensor_by_name(input_name)
	out = g.get_tensor_by_name(output_name)

	sigs[signature_constants.DEFAULT_SERVING_SIGNATURE_DEF_KEY] = \
	tf.saved_model.signature_def_utils.predict_signature_def(
	    {"input": inp}, {"output": out})

	builder.add_meta_graph_and_variables(sess,
	                                 [tag_constants.SERVING],
	                                 signature_def_map=sigs)
	builder.save()`

just remember that the output layer name is embeddings and not outputs, and it is necessary to inform the input and output layers in the code above.

So I managed to finish the conversion, by deleting the ns() after sess --this might be a typo--.
After that, I got the following error. Any insights?
Unable to lift tensor <tf.Tensor 'embeddings:0' shape=(None, 512) dtype=float32> because it depends transitively on placeholder <tf.Operation 'phase_train' type=Placeholder> via at least one path, e.g.: embeddings (Mul) <- embeddings/Rsqrt (Rsqrt) <- embeddings/Maximum (Maximum) <- embeddings/Sum (Sum) <- embeddings/Square (Square) <- InceptionResnetV1/Bottleneck/BatchNorm/Reshape_1 (Reshape) <- InceptionResnetV1/Bottleneck/BatchNorm/Shape (Shape) <- InceptionResnetV1/Bottleneck/MatMul (MatMul) <- InceptionResnetV1/Logits/Dropout/cond/Merge (Merge) <- InceptionResnetV1/Logits/Dropout/cond/dropout/mul (Mul) <- InceptionResnetV1/Logits/Dropout/cond/dropout/Floor (Floor) <- InceptionResnetV1/Logits/Dropout/cond/dropout/add (Add) <- InceptionResnetV1/Logits/Dropout/cond/dropout/random_uniform (Add) <- InceptionResnetV1/Logits/Dropout/cond/dropout/random_uniform/min (Const) <- InceptionResnetV1/Logits/Dropout/cond/switch_t (Identity) <- InceptionResnetV1/Logits/Dropout/cond/Switch (Switch) <- phase_train (Placeholder)


Bug 2095224: affinity rules list has stuck loader for non-privileged user

📝 Description
when adding affinity rule as non-privileged user, below the rules list to be applied there is a stuck loader,
🎥 Demo
before:
https://user-images.githubusercontent.com/67270715/172847605-ab869ab3-7170-4c54-ace6-6b43f2429abe.mp4
after:
https://user-images.githubusercontent.com/67270715/172848624-24608eda-5692-4f2a-9e2f-fe4198a133cc.mp4
Signed-off-by: Aviv Turgeman<EMAIL_ADDRESS>

/retest


cc-shim is not showing the commit from where it was built when installed from packages

$ /usr/libexec/clear-containers/cc-shim --version
shim version: 3.0.0-alpha.4 (commit: 0)

$ rpm -qa | grep cc-shim
cc-shim-bin-3.0.0beta.2+git.1f545df-2.1.x86_64
cc-shim-3.0.0beta.2+git.1f545df-2.1.x86_64

@gorozco1 that's because OBS pulls a github tarball, which normally does not contain the git history, we can append the commit hash when doing make, in this case. The issue I see here is, after doing ./autogen.sh the Makefile has VERSION=3.0.0-alpha4. It's not taking the version from the VERSION file.

Closing this is a duplicate of #62


refactor: Operations

make code much more clear and readable format.

I'll review this in depth during the weekend, this is easy to make a mistake.

Closed by mistake


No profiles returned

Hi,
When running ./okta_aws.sh -l I get an empty profile list:
Available profiles:

I've tried configuring role_arn as the okta name you select via the portal and the ARN of the role, but still no luck.
My config is pretty minimal,
[general]
username = "myuser"
okta_server = "mytenant.okta-emea.com"

[some-profile-name]
role_arn = "arn:aws:iam::123456788901:role/admins"

Anything I can try or am missing?

@shoekstra Sorry we haven't replied to this issue!
Did you get this working? if so, do you remember the solution and can you post it here?

I went back to what I was using before - I'll give it another go as I'm not overly happy with how I do it now.

@jtimberman Installed the latest version and still same result.
I can authenticate, get the cookie, no profiles returned using --list.

Again, sorry we didn't follow up here. Version 0.6.0 returns a list for me for all the AWS accounts in my Okta profile. Please try the latest version (it's available via homebrew or pypi) and reopen this issue if it's still a problem.


Envoy version pointing to envoy dev branch in istio 1.19.4

Bug Description

After upgrading istio from 1.18.5 to 1.19.4 the envoy proxy version is pointing to 1.27.3-dev
as per istio 1.19.x it should be mapped to 1.27.x and latest stable envoy is 1.27.2 https://github.com/envoyproxy/envoy/releases

Can anyone help here to fix using stable envoy version 1.27.2 while installing istio 1.19.4 or higher version
Version
istioctl version
client version: 1.19.4
control plane version: 1.19.4
data plane version: 1.18.5 (10 proxies), 1.19.4 (3 proxies)

Additional Information
No response

istio does not use upstream releases directly, we build our release with istio's extensions.

+1, see https://github.com/istio/istio/discussions/48064#discussioncomment-7794044

Never mind, it already has, except that the css issue doesn't look like a link.


Visual Studio Test can't find tests when I add .Net Core project

Environment
Azure Pipeline
accountname: durabletaskframework
team project name: Durable Task Framework CI
build definition: Build & Run Tests-singleexp
Hosted Agent 2017 with Visual Studio Test (v2)
Issue Description
We have a Solution which include both several project for  net451 and netstandard2.0.  It works fine. However, once I add .NetCore project on the solution, it suddenly can not find my tests.
I eventually change the .NetCore project into net451 project.  The problem has gone. I'd like to know why it happens. I don't want to use net451.  Instead, I'd like to use netstandard2.0 or .net core with Multi agent test running parallel.  Also, I'd like to know why it happens for my learning.
Error

Test run is aborted. Logging details of the run logs.

New test run created.

Test discovery started.

Test Run Discovery Aborted . Test run id : 1000120

Unexpected error occurred during test execution. Try again.

Error : No test is available in d:\a\1\s\Test\DurableTask.AzureStorage.Tests\bin\Debug\net451\DurableTask.AzureStorage.Tests.dll d:\a\1\s\Test\DurableTask.AzureStorage.Tests\bin\Debug\net451\DurableTask.Core.Tests.dll d:\a\1\s\Test\DurableTask.Core.Tests\bin\Debug\net451\DurableTask.Core.Tests.dll d:\a\1\s\Test\DurableTask.Emulator.Tests\bin\Debug\net451\DurableTask.Emulator.Tests.dll d:\a\1\s\Test\DurableTask.ServiceBus.Tests\bin\Debug\net451\DurableTask.Core.Tests.dll d:\a\1\s\Test\DurableTask.ServiceBus.Tests\bin\Debug\net451\DurableTask.ServiceBus.Tests.dll. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.

Test run aborted. Test run id: 1000120

System.Exception: The test run was aborted, failing the task.

@TsuyoshiUshio : Can you share the logs when the issue happens (please run with System.debug set to true to get the test platform logs) ?

Hi @caltseng ,  Thank you for the comment. Attached is the one.
17.txt

@TsuyoshiUshio please upload the full zip that you get. There are additional logs in there that we need. Thanks. Also is this a github project? If so can you please share the repo url or a sample stripped down solution where this repro's?

logs_145.zip
Thank you, see attached. This branch.
https://github.com/TsuyoshiUshio/durabletask/commits/correlation/refactor
I already fix this to change from .NetCore to net451. However, you can use this commit hash
0a80b185a2cfa0f5584def9f126e28ab719bc5af

@TsuyoshiUshio as of today we do not support running Full .Net and dotnetcore tests in the same session. You will have to split them up in to 2 vstest task instances.

@ShreyasRmsft Good to know. Thank you very much.


Access to some bins that are temporarily saved are missing

Hello guys,
Our team has been using JSBin for as long as I can remember and it has been one of the tools that has been very helpful. But just recently, we came across an issue. There were some links that for some reasons weren't accessible anymore. Can someone assist us in retrieving the codes added on the following bins:
https://jsbin.com/petuxigeza/
https://jsbin.com/barimoduvu/
https://jsbin.com/mivaxodoxa/
For some reasons, we weren't able to access this links and we have codes in here that is a bit vital. Hope someone can assist us here. Thank you

I missed this coming in - but it's fixed now.

Thank you very much. This is very helpful.


Adding markdown-it-eleventy-img to the list.

Hope this qualifies to be added to the plugin list. Thanks!

Thank you!


Update sass npm packages (gulp-sass and node-sass)?

I suggest to update gulp-sass and node-sass because:

It allows to solve the GitHub Dependabot alert requiring an upgrade of tar to version 4.4.18 or later. tar is currently held back at<EMAIL_ADDRESS>due to<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>It prepares the way to update to Node.js 16 at some later date (see https://github.com/corona-warn-app/cwa-website/issues/2155)

gulp-sass would go from 4.1.1 to 5.0.0
node-sass would go from 4.14.1 to 6.0.1
tar would go from 2.2.2 to 6.1.11
If there is interest from the Open Source Team I can submit a PR for this change. I already tested that it works.

@MikeMcC399 Thanks. We will have a look also at this one.

@dsarkar
To make this more concrete I have submitted a draft tested PR https://github.com/corona-warn-app/cwa-website/pull/2178.

We will have a look at your pull request soon.
Thank you very much @MikeMcC399 !

@svengabr

We will have a look at your pull request soon.

I am happy to hear that. As soon as you are actively considering it, please let me know and I will rebase PR #2178, retest it and take it out of draft status.

@svengabr / @dsarkar
Thank you very much for merging. It is good to see that tar  has now disappeared from the Dependabot alerts due to the version update.
I'm also happy that the workflows continue to work without errors! 🙂

@MikeMcC399 Thank you very much for the suggestion and analysis!


The addtional thread for GPU

It seems that offload plugin or down to hsa creates additional thread to communicate with the GPU. Such additional thread seems floating around and competing with regular OpenMP threads. It is also hard to control its affinity and make performance very complicated. HIP got rid of such an additional thread by "Direct Dispatch" as ROCm 4.5 release note mentions.

The plugin doesn't spawn additional threads on trunk. Aomp will do if the kernel uses host services, e.g. malloc or printf, which if I understand correctly qmcpack doesn't. I think HSA does create additional threads, but not to launch kernels. I'll see if I can find the release notes in question.

FYI: From a miniQMC run
OMP_NUM_THREADS=8 rocprof --hsa-trace ./bin/check_spo -n 1

3916422 is not an OpenMP thread but it only calls many hsa_system_get_info in the initialization.
I'm refering to  3916430 which is not an OpenMP thread and calls hsa_signal_wait_scacquire all the time.

We need a long discussion on this.   For now, the start of the thread can be eliminated by removing printf , malloc, and free from target regions.   They need to be removed even if they are not executed.


Document request_headers config option

Closes #171

Merging this so we can reference it in the blog post.
Feel free to review this when you have time @jeffkreeftmeijer .


Login & Register's frontend and backend

Hopping this is the latest version of login&register Before midterm presentation

🤙


flake8: F821 undefined name 'unpack_db'

$ flake8 . --count --select=E901,E999,F821,F822,F823 --show-source --statistics
./idb/analysis.py:187:32: F821 undefined name 'unpack_db'
        return self._do_unpack(unpack_db)
                               ^
1     F821 undefined name 'unpack_db'

good catch, thanks!
ran across this myself today, but that was by chance, which simply makes me lucky. your use of flake8 is a great idea to improve code quality, so i'll certainly merge that.
closed in 8ad5c4ea80f930e4fb90e828f6421922afbde3b8


iOS Simulator & Physical Device build

Motivation
There is a crash of the iOS simulator build after last commits + physical device was not working even before, this is preventing  the further integration of Scandit library
Results

iOS simulator build is working
build into physical iPhone device is working

Tech description
--please-put-logs-screens-etc--

Hi Michael (@mppub), please document the steps done from the cloning of the epi-workspace and until the build of the mobile app.

@fp-prg-mdc guys could you please include the reproduction steps? thank you

The app needs camera access, ios simulator does not provide access to one. That’s why a real device should be used for the development.
I did some tests and there was a small problem that i fixed regarding the error thrown at the run time o a device connected to the xcode.
Please check a fresh clone if the bug that you identified is still there.

Issue was fixed. Thanks @asaccool for resolving it!


feat(core): add support for eip-4788 parentBeaconBlockRoot header field

Description
Based on https://eips.ethereum.org/EIPS/eip-4788

Solution

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

master

PR #3

PR #34

PR #35

PR #43   👈

This stack of pull requests is managed by Graphite.


Invalid mention of vote type?

"users can rate the page either by using the rating scale or voting, depending on the type chosen when the control was added to the page template" - we have no access to the rewrite templates, do any of the OOTB templates even have the vote up/down control?

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

ID: 325c389a-06ad-15b5-3a95-cbd94948028d
Version Independent ID: e843492b-d1da-56d4-3fc8-78ce0ac73257
Content: Rate or vote on a webpage or blog post on a portal in Dynamics 365
Content Source: ce/portals/rate-webpage-blog-post.md
Service: dynamics-365-customerservice
GitHub Login: @sbmjais
Microsoft Alias: shjais

Content has been updated.


Modify URL to previous commit

I found that the README.md of this repo contains only one line about COVID-19, same thing happened on some other repos from the same author, so I think maybe we can use the URL of previous commit temporarily?

Sounds reasonable. I respect their intentions, but in the interest of providing a survey of analysis tools, I prefer the original content for our purposes.


def solve arguments don't match example.py solve call

In example.py:
solution = tree_of_thoughts.solve(input_problem, k, T, b, vth, timeout, confidence_threshold=confidence, max_iterations=max_iterations, convergence_threshold=convergence_threshold, convergence_count=convergence_count)
but in treeofthoughts.py:
class TreeofThoughts
...
def solve(self, x, k, T, b, vth, timeout=None)

I think i fixed it! Download the latest version again and try pls

With use_v2=False there is no execution path that sets solution.


MusicKit with SPM

This is probably not the place to ask this question, but I'm not sure where else to ask...
I am building a CLI tool which would use MusicKit and MusadoraKit
Package.swift:
// swift-tools-version: 5.10
// The swift-tools-version declares the minimum version of Swift required to build this package.

import PackageDescription

let package = Package(
    name: "Yatoro",
    dependencies: [
        .package(url: "https://github.com/apple/swift-argument-parser.git", from: "1.5.0"),
        .package(url: "https://github.com/apple/swift-log.git", from: "1.6.1"),
    ],
    targets: [
        .executableTarget(
            name: "Yatoro",
            dependencies: [
                .product(name: "ArgumentParser", package: "swift-argument-parser"),
                .product(name: "Logging", package: "swift-log"),
            ],
            linkerSettings: [
                .unsafeFlags([
                    "-Xlinker", "-sectcreate",
                    "-Xlinker", "__TEXT",
                    "-Xlinker", "__info_plist",
                    "-Xlinker", "Sources/Yatoro/Resources/Info.plist",
                ])
            ]
        ),
    ]
)

Info.plist:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>CFBundleName</key>
    <string>Yatoro</string>
    <key>CFBundleIdentifier</key>
    <string>mybundleidentifier.yatoro</string>
    <key>NSAppleMusicUsageDescription</key>
    <string>This app requires access to Apple Music to play music tracks.</string>
</dict>
</plist>

The problem is whenever I run the built executable from the command line it crashes on MusicAuthorization.request()
If I run it from Xcode the app runs fine. But if I also try run Xcode built executable from the command line it also fails.
It's kind of frustrating, not really know when to look. Any advice?
To Reproduce
Steps to reproduce the behavior:

Build the project with swift build
Run the executable from command line

Desktop (please complete the following information):

OS: macOS Sonoma 14.6.1
Terminal: macOS terminal, wezterm

Additional context
Also tried the release version and running with sudo

Solved by manually adding terminals and the app itself in System Settings > Privacy & Security > Media & Apple Music


Requesting to include Digital Signature(SHA 256) for the assembly

Is your feature request related to a problem? Please describe.
After referencing the Scintilla.NET NuGet package (v5.6.2) in our project, we encountered a build issue indicating that an assembly should be digitally signed.
Describe the solution you'd like
Request to include the digital signature for the assemblies used while referring to the Nuget package.
Describe alternatives you've considered
Additional context

My initial thought is to reject this feature request.  I don't have a digital signature, nor do I want to purchase one to get this digitally signed.  If someone wants to fork the repo and take on the digital signature piece for those scenarios that need it, that is fine by me.
I'm open to other ideas, but that is my initial thoughts.

@KalyaniURS You can digitally sign Scintilla5.NET.dll yourself with the same certificate you use to sign binaries that reference it. There is no need to build it from source.

[like]  Upadhyayula Rama Surya Kalyani reacted to your message:

From: Ahmet Sait @.>
Sent: Friday, October 25, 2024 7:52:29 AM
To: desjarlais/Scintilla.NET @.>
Cc: Upadhyayula Rama Surya Kalyani @.>; Mention @.>
Subject: Re: [desjarlais/Scintilla.NET] Requesting to include Digital Signature(SHA 256) for the assembly (Issue #143)
WARNING: Do not click links or open attachments unless you recognise the sender and the content is safe. Please contact IT support if you have any suspicions.
@KalyaniURShttps://github.com/KalyaniURS You can digitally signhttps://learn.microsoft.com/en-us/windows/win32/seccrypto/signtool Scintilla5.NET.dll yourself with the same certificate you use to sign binaries that reference it. There is no need to build it from source.
—
Reply to this email directly, view it on GitHubhttps://github.com/desjarlais/Scintilla.NET/issues/143#issuecomment-2437129757, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BGQVNFNCTHMIXKWWK5ORALTZ5H2D3AVCNFSM6AAAAABQQ6PV4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZXGEZDSNZVG4.
You are receiving this because you were mentioned.Message ID: @.***>


BlockSolve should handle empty partitions

After discussion with @tomerk it seems that it would be really useful to have the various Block Sovlers not choke on empty partitions. Empty partitions can arise in the course of cross-validation when you want to fiter your data RDD into a "train" rdd and a "test" rdd.

Also @tomerk suggests that the reshuffle that follows this warning: "15/12/27 21:22:21 WARN BlockWeightedLeastSquaresEstimator: Partitions do not contain elements of the same class. Re-shuffling" can sometimes create empty partitions as well

Hmm the reshuffle creates an RDD with exactly numClasses partitions afaik, does this happen when you have have no examples in a class ? Anyways we can make the rest of the algorithm work with empty partitions

@shivaram In that case I was running up against https://github.com/amplab/keystone/issues/197 so all my data were being assigned the same class label. That said, empty partitions are still a problem.

Ah yes - That makes sense. If you have it handy, could you paste a stack trace you get when you have empty partitions ?


Add drop_nulls plugin and bump version

This PR implements the drop_nulls plugin.
It ignores all keys of maps whose values are included in the 'nulls' option of the encoding.
Example
1> {ok, JSON} = euneus:encode_to_binary(#{a => 1, b => undefined}, #{plugins => [drop_nulls]}).
{ok,<<"{\"a\":1}">>}

1> {ok, JSON} = euneus:encode_to_binary(#{a => 1, b => undefined, c => foo}, #{nulls => [undefined, foo], plugins => [drop_nulls]}).
{ok,<<"{\"a\":1}">>}

Credits
Thanks both @asabil and @leonardb for the suggestions at the Erlang forums topic.

Sort of surprising the the drop_nulls plugin does not drop nulls by default but converts the null into a string value "null"
4> {ok, JSON} = euneus:encode_to_binary(#{a => 1, b => undefined, c => null}, #{plugins => [drop_nulls]}).
{ok,<<"{\"a\":1,\"c\":\"null\"}">>}

@leonardb Yes, that's intentional but sounds strange due to the plugin name. The default for the nulls option is [undefined]. Maybe worth changing it to [null, undefined]? Elixir mostly uses 'nil'. Maybe then the default can be [null, undefined, nil]. What about?

edit: Should the same behavior apply to empty maps? IE, when the recursed processing of a map results in an empty map, should that be treated as a null/undefined? I'm really not sure, but it's not what I'd 'expect'

I'm not aware of this. I think the behavior should be the same of the Javascript:
1> JSON.stringify({})
'{}'

2> JSON.stringify({f: undefined})
'{}'

@leonardb Yes, that's intentional but sounds strange due to the plugin name. The default for the nulls option is [undefined]. Maybe worth changing it to [null, undefined]? Elixir mostly uses 'nil'. Maybe then the default can be [null, undefined, nil]. What about?

The Principle of Least Surprise (based on the name of the plugin) would seem to dictate that the default be [null, nil].
Since the initial request that launched the feature was around handling of undefined and matching the JSON.stringify behavior, maybe that should stand alone rather than part of what is really a drop_map_keys_for_matching_values plugin. Or maybe just better renaming it?

The name is based on the nulls option, so all terms in that list would be ignored, you can define anything there and the default, currently, is [undefined].
The reason for this default is because I mostly see undefined as the null term for Erlang.
Javascript has null and undefined built-in, but we do not have them in Erlang.
That's the reason the nulls option exists in Euneus. I do not have another name in my mind for this option.
FWIW there is a null_term option for decoding, it also can be anything and the default is undefined, for the same reason of the nulls option.
1> {ok, JSON} = euneus:encode_to_binary(#{a => undefined, b => null, c => nil}, #{nulls => [undefined, null, nil]}).
{ok,<<"{\"c\":null,\"a\":null,\"b\":null}">>}

2> euneus:decode(JSON, #{null_term => nil}).
{ok,#{<<"a">> => nil,<<"b">> => nil,<<"c">> => nil}}

So we cannot have exactly the same behavior of the Javascript.

It's a bit confusing thinking about null, undefined, nil, etc in Erlang vs JSON.
I agree with you when you say about the Principle of Least Surprise, but I'm to implement the drop_nulls plugin as it is in this PR and change it in the future if needed.
Feel free to open an issue about this. I will be happy to discuss it in a dedicated topic and with more people involved :)


Update to the latest version of upstream Terraform-provider-scm v0.9.2

This contains some sdk fixes for 5xx level error retries.

This was merged in https://github.com/pulumi/pulumi-scm/pull/25; our publish job failed. See #22.

It looks like 0.1.2 is out


Update module k8s.io/apiserver to v0.30.3

This PR contains the following updates:

Package
Type
Update
Change

k8s.io/apiserver
require
patch
v0.30.1 -> v0.30.3

Release Notes

kubernetes/apiserver (k8s.io/apiserver)
v0.30.3
Compare Source
v0.30.2
Compare Source

Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

5 additional dependencies were updated

Details:

Package
Change

k8s.io/api
v0.30.1 -> v0.30.3

k8s.io/apimachinery
v0.30.1 -> v0.30.3

k8s.io/client-go
v0.30.1 -> v0.30.3

k8s.io/component-base
v0.30.1 -> v0.30.3

k8s.io/kms
v0.30.1 -> v0.30.3


How to create an initial template using Hugin

I am creating own template using Hugin, because generated picture was misaligned when using the template uploaded on Github.
I created it by watching the tutorial video uploaded to Youtube, but I do not know how to create control points.
There was no change when creating control points and not creating.

I read the note written in the description section of Youtube.
Is the version of Hugin I use bad? (The version is 2<IP_ADDRESS>92917e7a55.)
If there is no problem, would you like to upload the file including 360_0529.JPG described in the template(gear360tmpl.pto)?
Accordingly, I want to confirm this problem.
Also, how accurate is the image created by Hugin stitched?
I am glad if you show me the example of the result.
I appreciate your help.
Thank you.

Hi,
Do you have any previous experience stitching panoramas using Hugin?
The workflow is like this:

Add photos, set masks, etc. (just like in the photo).
Add control points (same points on two different photos).
Optimise panorama parameters.
Once satisfied stitch panorama.

Point 3 is tricky as at this step Hugin actually modifies parameters of photos (their position, distortion, etc.) to match them together. When I was creating the template I used, more or less, trial and error which parameters should be optimised.
L.

@ultramango Sorry for the late reply.
It is the first time I have used hugin.
It seems that the modification of the parameter was insufficient.
So, I will study from basically usage of Hugin.
Thanks for your advice.

No worries.
The key is the optimisation process which will modify the photos parameters (rotation, movement, etc.) to fit them all together.
Also ensure that you have control points that point to the same things on various photos.
L.


Fix/google usernames

fixes issue where google users with already taken username could not use google as a provider


Graphs are confusing

In particular the combination of shading for confidence interval and shading for strength of likelihood. This makes it hard to tell what is going on - the graph being all one colour (particularly unsure) looks a bit broken and it's hard to identify the difference between Increasing and Likely Increasing and the same will be true of the blue.

This relates to #82 but is focused on the graph.
I think it may have been amplified by cherry picking graphs out the results but the graph could do with a note about CI on the key and perhaps needs a more significant change of hue with the likelihood so that the saturation change for CI is clearer.

What about introducing a different pattern for confidence intervals, e.g. for the whiskers a color-white-color-white-stripe pattern, that is easy to discriminate from the high confidence areas?


Replace usages of wait_for_active_timeline

Describe your changes
This commit replaces all usages of connection_manager.rs: wait_for_active_timeline with Timeline::wait_to_become_active. wait_to_become_active is better and in the right module.
Issue ticket number and link
https://github.com/neondatabase/neon/issues/4189
Checklist before requesting a review

[X] I have performed a self-review of my code.
[X] If it is a core feature, I have added thorough tests.
[X] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[X] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

@jkosh44 Looks good and thanks for contributing!!!


doesn't work with kubernetes extension installed

It was reported that the ytt extension does not work with the kubernetes extension already installed, which installed the yaml extension (https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml).
We should try to make these work together, if possible.

For anyone else looking to get ytt extension working: I needed to uninstall the YAML plugin above.
But to uninstall YAML I had to uninstall Kubernetes extension. To uninstall Kubernetes extension I had to uninstall Helm extension.

Simple fix for this problem is to create a new language identifier for .ytt files instead of using the YAML identifier.
YAML identifier in VSCode is already overloaded, with everyone coming up with their own extension for Kubernetes and Helm :D

@cppforlife What do you think about this solution?

Thanks for the suggestion @ig0rsky! This change (4d3be9b) was included in our latest release which has been published to the marketplace. Users will still need to explicitly select the ytt language from the language selector if they have other YAML extensions installed, but otherwise it should work.


Scroll bar color inconsistent with OS color mode

🐛 Bug Report
Scroll bars are showing based on the OS theme and not the light/dark theme sent to the provider. This is a regression that happened when upgrading from Chrome 87 to Chrome 88
Light Mode OS vs Dark Mode Theme

Dark Mode OS vs Light Mode Theme

🤔 Expected Behavior
Scroll bars should match the theme passed into the Provider.
😯 Current Behavior
Scroll bars match the OS theme regardless of theme passed into the Provider.
💁 Possible Solution

🔦 Context

💻 Code Sample
https://react-spectrum.adobe.com/react-spectrum/Picker.html#asynchronous-loading
Open the select menu in the async picker to observe
OR
https://git.corp.adobe.com/pages/taborski/rsp-storybook/?path=/story/v2-v3-components-v3dialog-v2select--v-3-dialog-v-2-select
Open the dialog and ensure you can scroll within it.
🌍 Your Environment

Environment is important for this issue:
Mac
Chrome 88.0.4324.96, macOS 10.15.7
Mac OS -> Display -> General -> Light vs Dark & Always Show Scrollbar
🧢 Your Company/Team
Adobe Analytics

I'm able to see this in our docs, and to reproduce it, I've created a sandbox to simplify https://codesandbox.io/s/determined-noether-htry2?file=/index.html
Chrome 86.0.4238.0 (r799004) appears affected by this too, so I think you were doing a bigger leap than 87 -> 88
Bisecting revealed
You are probably looking for a change made after 798993 (known good), but no later than 799004 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/49673ad671f71162a8a81ee992f642be7fedc8f1..38b5919f7e3c17b697cd6424a07b14716b3c6895

I've been able to reproduce this in Safari as well.
Safari has an additional bug, which happens when switching between color schemes https://bugs.webkit.org/show_bug.cgi?id=206771
I propose this PR to fix Chrome https://github.com/adobe/react-spectrum/pull/1547
The Safari issue will need to be resolved by Safari.
FF does not support color-scheme yet, so scroll bars will appear in light unless you get a plugin. https://developer.mozilla.org/en-US/docs/Web/CSS/color-scheme#browser_compatibility