release maven package by actions

ci errors:
Error:  Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 2.866 s <<< FAILURE! - in com.baidu.hugegraph.core.CoreTestSuite
Error:  com.baidu.hugegraph.core.CoreTestSuite  Time elapsed: 2.859 s  <<< ERROR!
com.baidu.hugegraph.exception.ConnectionException: Failed to connect to MySQL
	at com.baidu.hugegraph.core.CoreTestSuite.init(CoreTestSuite.java:68)
Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
	at com.baidu.hugegraph.core.CoreTestSuite.init(CoreTestSuite.java:68)
Caused by: java.io.EOFException: Can not read response from server. Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost.
	at com.baidu.hugegraph.core.CoreTestSuite.init(CoreTestSuite.java:68)

Error:  com.baidu.hugegraph.core.CoreTestSuite  Time elapsed: 2.862 s  <<< ERROR!
com.baidu.hugegraph.exception.ConnectionException: Failed to connect to MySQL
	at com.baidu.hugegraph.core.CoreTestSuite.clear(CoreTestSuite.java:80)
Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
	at com.baidu.hugegraph.core.CoreTestSuite.clear(CoreTestSuite.java:80)
Caused by: java.io.EOFException: Can not read response from server. Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost.
	at com.baidu.hugegraph.core.CoreTestSuite.clear(CoreTestSuite.java:80)


support filtering a variant collection to variants overlapping specified gene names

Currently I have to call variant.gene_names() for every variant, which is slow (I have ~80k variants).
A better implementation would be to use pyensembl to lookup the intervals for the genes I'm interested, then filter the variants by position quickly. It would be useful if that functionality were part of VariantCollection.

@timodonnell Do you think we still need this?

I have no current need for this, feel free to close


Prerelease 1.0 chart editor bugs

Describe your bug here.
When you click the "Swap section" it doesnt swap in the chart preview (f12), only when you playtest the chart and go back that it changes it.
Also when you copy and paste, swap section, mirror notes, the Disable Note RGB has to be updated because the notes get their rgb again.
Those are the bugs, but I have a few suggestions in features that would help with charting:
Would be awesome if you could swap the oponent and the player in the editor, its really confusing to have to chart the player in the left side and the oponent in the right;
"Mirror Notes" if there are notes selected, it would only mirror the selected ones;
Add an option in viewing of the waveform where you could make it so it is split so each side shows their respective waveform, so you dont need to me switching in the options all the time;
Command Prompt/Terminal logs (if existing)
nuh uh

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
Yes, but nothing in the code, just adding songs and characters.

It's because that is Pre-Release.
Close the issue, 1.0 is out


Breakpad binaries?

Hi! Your instructions require us to first build Google's Breakpad tool; however, I'm unable to figure-out how to get that build working (macOS host). Might I strongly urge you to provide pre-build binaries for x86, arm, arm64, x86_64 etc.? I presume you must have already done this, otherwise you'd not have been able to test your solution. Without a compiled Breakpad, I'm unable to use your Android NDK code...

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

ID: 5dbf28d0-dedf-3e44-7c5b-4d2a2ed22c02
Version Independent ID: 353d51d2-d428-c95d-2746-1d8b285a312d
Content: Android NDK - Visual Studio App Center
Content Source: docs/diagnostics/Android-NDK.md
Service: vs-appcenter
GitHub Login: @winnieli1208
Microsoft Alias: yuli1

I was able to find just one location that I could use to help me build the libraries for Android.
The instructions I followed were in last section here:
http://zompi.pl/symbolicating-crash-dumps-for-android-in-unreal-engine-4/#lastchapter
I had to edit APP_API three times and remake, once for each target (x86, armeabi-v7a, x86_64)
It would be great for future developers if you could reproduce and verify these steps, and document them.

@sseyod thank you for the suggestion, I'll assign this to the PM to take a look.

@jwargo furthermore, is there any reason why dump_syms can't be fixed so that it can be run from macOS to work with Android ELF format files?
Thanks, Pete

@sseyod I have no idea as I didn't understand much of what you asked :-). The PM is out for the next three weeks, but I'll get you an answer as soon as I can.

@jwargo No worries John, thanks for helping :) Hopefully this'll make sense to the PM! Pete

I just wanted to add - it is great that Microsoft are open to receiving feedback from developers. Top stuff!

@sseyod Thanks!

@sseyod thanks for the feedback and apologies for the delay! We have an engineering team looking into our NDK support to fix a few issues in the next week or so. We'll address your comments and post updates then.
Thank you for your patience!

Thanks. We're not seeing any crash reports coming through from the NDK crash reporting system, which makes me think that the current implementation might be broken (you mentioned there are a few issues)... so, looking forward to updates as they arrive! Pete

Hi, I also see no native crashes on the appcenter UI for our app.
If I set AppCenter.setLogLevel(Log.VERBOSE), I see a bunch of logs which look like the send succeeded:
e.g.
2019-07-12 16:28:47.432 12071-12129/my_app D/AppCenter: checkPendingLogs(group_core) pendingLogCount=0 batchTimeInterval=3000
2019-07-12 16:28:47.650 12071-12242/my_app V/AppCenter: Calling https://in.appcenter.ms/logs?api-version=1.0.0...
2019-07-12 16:28:47.651 12071-12242/my_app V/AppCenter: Headers: {Content-Encoding=gzip, Install-ID=(redacted), App-Secret=(redacted), Content-Type=application/json}
2019-07-12 16:28:47.675 12071-12242/my_app V/AppCenter: {"logs":[{"type":"errorAttachment","timestamp":"2019-07-12T15:28:45.015Z","device":{"sdkName":"appcenter.android","sdkVersion":"2.1.0","model":"Pixel","oemName":"Google", etc. redacted
2019-07-12 16:28:49.165 12071-12242/my+app V/AppCenter: HTTP response status=200 payload=CorrelationId: (redacted)  ReasonCode: Success
2019-07-12 16:28:49.227 12071-12129/my_app D/AppCenter: Deleting logs from the Persistence database for groupErrors with (redacted)
2019-07-12 16:28:49.227 12071-12129/my_app D/AppCenter: The IDs for deleting log(s) is/are:
2019-07-12 16:28:49.227 12071-12129/my_app D/AppCenter: 	3
Let me know if you need more info and I'll open a ticket.
Cheers

Thanks @jbazeley, glad to know it wasn't just me :) Pete

Apologies for the delay. Our engineering team is looking into our NDK support now. We'll get back to you shortly.
Thanks for your patience!

Hi @sseyod,
While working on this I made myself a script to easily run dump_syms and generate a ready-to-upload archive. This uses Docker to compile and run the tool on a Linux VM:
https://github.com/jpeg-ms/breakpad-tools-appcenter
Also, note that you probably don't need to set APP_API. All ABIs will be compiled by default, see: https://developer.android.com/ndk/guides/application_mk
I hope this helps!
Sorry if this isn't the most convenient solution.

Thanks for that. I, too wrote a similar script. For most developers, I'd have thought that that sort of scripting is probably a bridge too far in terms of complexity, and will stop them using Microsoft's Crash Reporting for the Android NDK. Come on Microsoft : provide a native Mac solution :) Pete

I still have an issue with reporting JNI crashes and presenting them on AppCenter web side. I can see in log that dump file is proceed and sent successfully, but somehow they don't appear in appcenter, neither in unsymbolicated crashes part. Do you have any news on this, what you suggest since the reporting jni crashes is very important to me?

Hey @marko88 do you mind starting a support thread via the blue chat bubble in App Center? This will put you in direct contact with our engineering and support team so they can take a closer look. Thanks!


port CombineGVCFs

The requirement is to port the CombineGVCFs tool and the tests (test data needs to be reviewed for sharability and made public if possible)

Feel free to bounce this back if you want to an we can talk about how to proceed.

this was mismarked as beta. It's an alpha goal


Prevent Sentry changes breaking the bootstrapping script

I regressed this a while back when removing Docker initialization code. I thought we added something to let me know when things would break.

I also need to determine if some alerts should have triggered.


Error when trying to upload image by link

When trying to upload image by url i get an error
Access to fetch at 'https://www.ixbt.com/img/x780/n1/news/2023/1/2/3.png' from origin 'https://video.test' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Is it downside of using fetch() in js for geting file content? Or some error in CORS in my application?
Cause getting same file by url works fine in this integration with livewire https://github.com/maxeckel/livewire-editorjs
It is using serverside loadImageFromUrl
    public function loadImageFromUrl(string $url)
    {
        $name = basename($url);
        $content = file_get_contents($url);

        Storage::disk($this->downloadDisk)->put($name, $content);

        return Storage::disk($this->downloadDisk)->url($name);
    }

I also tried to use CORS proxy (cors.sh - first found).
In this case i get error
Undefined array key "name" in file /Users/mikhailpanyushkin/code/mtube/vendor/livewire/livewire/src/WithFileUploads.php on line 17
Looks like with Cors Proxy i don't get filename?


training_step is called once for each optimizer

If model returns multiple optimizers, a closure is created for each one of them. This results in training_step called for each optimizer which is wasteful in most cases.
In addition to this, training_step is being called with additional parameter ( optimizer id) - this is not documented and results in an exception which ( calling 2 argument function with 3 parameters )
To Reproduce
Steps to reproduce the behavior:

Create model with two or more optimizers.
training_step should take ( batch, batch_nb) as per documentation and a print statement printing batch_nb
Run trainer.fit
Exception should be thrown re call to training_step with 3 parameters
change training_step to take ( batch, batch_nb, optimizer_idx)
Run trainer.fit
Observe batch_nb printed as many times as there are optimizers.

Expected behavior

In most cases training_step can be called only once - that's efficiency improvement.
Documentation should specify the extra parameter being passed when multiple optimizers are used, to prevent the exception.

this is pretty well documented and is the expected behavior.
https://williamfalcon.github.io/pytorch-lightning/LightningModule/RequiredTrainerInterface/#training_step

Ok, I've not noticed the documentation of the idx. But what about calling the training step multiple times? I can see how this could be useful for GANs. In the case of having different optimizers for different parts of the model, this might not be desirable.

I also encountered this problem, where I only want to set different optimizers for different parts of my model, but they should all update the model in each iteration.
Can pytorch_lightening provide a way to achieve this? For example in configure_optimizers we can mark multiple optimizers as a group where they should all update parameters (so behave like a single optimizer in current pytorch_lightening implementation).

this is pretty well documented and is the expected behavior.
https://williamfalcon.github.io/pytorch-lightning/LightningModule/RequiredTrainerInterface/#training_step

not found, where is the new documentation?

this is pretty well documented and is the expected behavior.
https://williamfalcon.github.io/pytorch-lightning/LightningModule/RequiredTrainerInterface/#training_step

It is giving not found, can you please link the updated docs?

Hi @L1AN0 ,
For doing that you can create a single optimizer with multiple optimizers inside. You can check out this link:
1. Multiple optimizers of Same type:
Here
optim.SGD([{'params': model.base.parameters()},
           {'params': model.classifier.parameters(), 'lr': 1e-3}],
           lr=1e-2, momentum=0.9)

2. Multiple Optimizers of Different Type
class MultipleOptimizer(object):
    def __init__(*op):
        self.optimizers = op

    def zero_grad(self):
        for op in self.optimizers:
            op.zero_grad()

    def step(self):
        for op in self.optimizers:
            op.step()

opt = MultipleOptimizer(optimizer1(params1, lr=lr1),
                        optimizer2(params2, lr=lr2))

loss.backward()
opt.zero_grad()
opt.step()

Hi @L1AN0 ,
For doing that you can create a single optimizer with multiple optimizers inside. You can check out this link:
1. Multiple optimizers of Same type:
Here
optim.SGD([{'params': model.base.parameters()},
           {'params': model.classifier.parameters(), 'lr': 1e-3}],
           lr=1e-2, momentum=0.9)

2. Multiple Optimizers of Different Type
class MultipleOptimizer(object):
    def __init__(*op):
        self.optimizers = op

    def zero_grad(self):
        for op in self.optimizers:
            op.zero_grad()

    def step(self):
        for op in self.optimizers:
            op.step()

opt = MultipleOptimizer(optimizer1(params1, lr=lr1),
                        optimizer2(params2, lr=lr2))

loss.backward()
opt.zero_grad()
opt.step()

Thanks. But that won't be sufficient because the MultipleOptimizer class is not an Optimizer. For example, when pytorch lightning is creating a checkpoint, the optimizer will fail because there's no state_dict in MultipleOptimizer.
Sadly, making MultipleOptimizer an appropriate Optimizer is not trivial.

Also need the feature as @L1AN0 . Same with this need (https://github.com/PyTorchLightning/pytorch-lightning/issues/29#issuecomment-611006872).
Basically, I need to change the optimizer after 5 epochs. If I define two optimizers, the training_step will be executed two times with two different optimizer_idxs. But this is not needed. I only need to call the training_step once for each step since the two stages are not overlapped.


not wholly fatal ValueError in production

In production, most but not all POSTs to new_event get a 500:

ValueError: The future belongs to a different loop than the one specified as the loop argument

but the message is in fact successfully sent to the websocket.
One approach to examining this would be to set up a postgres DB container in dev.

Closed in f5df460
There's no need to await channel_layer.close_pools(); the client now gets 200 every time, even though we see some
2023-03-15 17:47:30,672 ERROR    Task exception was never retrieved
future: <Task finished name='Task-2433' coro=<Connection.disconnect() done, defined at /root/.cache/pypoetry/virtualenvs/dostuff-9TtSrW0h-py3.9/lib/python3.9/site-packages/redis/asyncio/connection.py:723> exception=RuntimeError("Task <Task pending name='Task-2433' coro=<Connection.disconnect() running at /root/.cache/pypoetry/virtualenvs/dostuff-9TtSrW0h-py3.9/lib/python3.9/site-packages/redis/asyncio/connection.py:736>> got Future <Future pending> attached to a different loop")>
Traceback (most recent call last):
  File "/root/.cache/pypoetry/virtualenvs/dostuff-9TtSrW0h-py3.9/lib/python3.9/site-packages/redis/asyncio/connection.py", line 736, in disconnect
    await self._writer.wait_closed()  # type: ignore[union-attr]
  File "/usr/local/lib/python3.9/asyncio/streams.py", line 359, in wait_closed
    await self._protocol._get_close_waiter(self)
RuntimeError: Task <Task pending name='Task-2433' coro=<Connection.disconnect() running at /root/.cache/pypoetry/virtualenvs/dostuff-9TtSrW0h-py3.9/lib/python3.9/site-packages/redis/asyncio/connection.py:736>> got Future <Future pending> attached to a different loop

on the backend in development and production.


Read Child Data when Streaming Parent

Hello,
I am currently streaming a parent of an unknown amount of children. I want to read all children whenever one changes, so I am streaming the parent. How can I access the children when the parent is streamed?

You should see the examples first.
You will get the answer since you tested it.
The issue open here should be related to bugs, usage problems and enhancement of this library.


Bug: Images are missing for ledger wallet instructions when signing a transaction

I'm submitting a…

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request

Expected Behavior
Ledger wallet instructions should be displayed.

Current Behavior
See screenshot.  The images for the ledger steps are missing when you attempt to sign a transaction:

Possible Solution
This could actually be a problem in unchained-wallets.

Steps to Reproduce (for bugs)

Create a wallet that includes a ledger as one of the xpubs
Create a spend transaction
Attempt to sign with the ledger
Note that images are missing

Environment

Where are you running caravan:  localhost
Operating system: Linux
Browser and version: Chrome

<EMAIL_ADDRESS>/home/walden/code/caravan
├──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>
npm: 6.14.4
node: v12.16.2
Linux 5.6.13-arch1-1 #1 SMP PREEMPT Thu, 14 May 2020 06:52:53 +0000 x86_64 GNU/Linux

I think this might be a bug with unchained-bitcoin not having these images yet rather than caravan but I'd have to double check.


Total refact

Interface based APIs

Aged
Asymmetric
Symmetric
Hash
Compression
Generic

New implemented compression

Flate
Zlib

New hash algorithm

Blake2b-384
SHA3-384
SHA3-512

KDF

Argon2ID dynamic KDF parameters

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


New version: Ubisoft.Connect version 151.2.11050

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

https://github.com/microsoft/winget-pkgs/issues/147885

Microsoft Reviewers: Open in CodeFlow

Perhaps CDN is still propagating changes across the cache; Will rerun in a bit

Automatic Validation ended with:

Installer Verification Analysis Context Information:
Specified hash doesn't match.
Actual hash:   48AA6A6FC3A3C255F38774A14B20D5C9FDA156EF5435A31A45B44DFF50CDC3E0
Expected hash: 34478fb74672e95ec16be1826901f85581410cc89bf24dcf09e6b8bf82e3d6bf

4/5/2024 2:31:29 PM

Installer Validation

(Automated response - build 876.)

@wingetbot run

@wingetbot run

Automatic Validation ended with:

Installer Verification Analysis Context Information:
Specified hash doesn't match.
Actual hash:   48AA6A6FC3A3C255F38774A14B20D5C9FDA156EF5435A31A45B44DFF50CDC3E0
Expected hash: 34478fb74672e95ec16be1826901f85581410cc89bf24dcf09e6b8bf82e3d6bf

4/5/2024 4:55:26 PM

Installer Validation

(Automated response - build 876.)


portforward: Support background task cancelation

The portforward utility spawns a background task and returns a future
that completes when the background task completes, but the spawned
task's JoinHandle is discarded, so there's no way to cancel the
background tasks before all of the port forwards complete.
This change updates the Portforwarder type to hold the JoinHandle
and exposes a Portforward::abort method that cancels the spawned task.
impl Future for Portforward changes to await the background task's
completion. A portforward::Error variant is added to expose task
failures.

I'm realizing there's another issue with the port forward API: as far as I can tell, there's no way to take ownership of any of the Port streams (to, for instance, hand off to a hyper client, for instance). I'm going to propose opening up the API further to explicitly return port streams and a task so that the caller can determine what to do with them.

Thanks for this! The portforward PR (#446) was sitting there for about a year, and we basically merged to get further feedback like this from users. You are welcome to propose changes however you like :laughing:

@kazk Thanks for the quick review. I decided to propose a slightly API change after using the existing one. Let me know what you think. I'm happy to revert those changes, but I thought a shallower API was easier to follow. Let me know what you think!

I'll rewrite AttachedProcess like this, and remove all the panics.


Missing dependencies

This looks really interesting.
Now I have made two attempts to set this up.
First I tried with Ubuntu on my Windows bash prompt,
then I started a Ubuntu EC2 and did the Make there.
Same result:
Testing the Lambda i get an error:
`START RequestId: nnn-bnnn-nnnn-nnnn Version: $LATEST
Script starting at 2018/12/18 12:26:12 UTC
Attempting to create directiory /tmp/clamav_defs.
Starting freshclam with defs in /tmp/clamav_defs.
freshclam output:
./bin/freshclam: error while loading shared libraries: libjson-c.so.2: cannot open shared object file: No such file or directory
Unexpected exit code from freshclam: 127.
Script finished at 2018/12/18 12:26:12 UTC
...
`
Any ideas about how to get trough this?

Changing build_lambda.sh as follows worked for me
-yumdownloader -x \*i686 --archlist=x86_64 clamav clamav-lib clamav-update +yumdownloader -x \*i686 --archlist=x86_64 clamav clamav-lib clamav-update json-c pcre2 +rpm2cpio pcre2*.rpm | cpio -idmv +rpm2cpio json-c*.rpm | cpio -idmv

@ocasta
Thanks, it worked for me too.
Merry Xmas

Changing build_lambda.sh as follows worked for me
-yumdownloader -x \*i686 --archlist=x86_64 clamav clamav-lib clamav-update
+yumdownloader -x \*i686 --archlist=x86_64 clamav clamav-lib clamav-update json-c pcre2
+rpm2cpio pcre2*.rpm | cpio -idmv
+rpm2cpio json-c*.rpm | cpio -idmv

Worked fo me to. Thanx!

I believe this is fixed as evidenced by this code: https://github.com/upsidetravel/bucket-antivirus-function/blob/master/build_lambda.sh#L32-L37


Not working with expo-router

Describe the bug
Graphs will not render when using expo-router.
When space is interacted with, throws error:
Cannot read property 'handler' of undefined. from dispatchEventsToZRender
To Reproduce

Get the example project within this repo
Follow steps to manually add expo-router here
Delete App.js
Rename src/App.tsx to src/app/index.tsx
Run the project. Screen will be blank.
Tapping on where the graphs would be will throw error.

Expected behavior
Graph should behave as intended.
Desktop (please complete the following information):

OS: Windows 11

Smartphone (please complete the following information):

Device: Galaxy A54 5G
OS: Android 14

I tried the reprolapse step, and it worked normally.

I was experiencing the same error, but after upgrading echarts to version ^5.5.1, the error stopped occurring.

There may be multiple zrender or echarts libraries in your project. Can you check them?
yarn why zrender

Can you provide an example that can be reproduced

Can you provide an example that can be reproduced

Just run latest expo application and add basic example from your library.
Web - all charts on place
mobile - no charts rendered
Everything latest Expo 51, echarts and react-native-echarts, expo-router used as routing solution


Bump Otel and dependencies from 1.11.2 to 1.14.0

Intended to replace #12040 and friends with a single update of all Otel libraries.
Direct imports:
- go.opentelemetry.io/otel v1.14.0
- go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.14.0
- go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.14.0
- go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.14.0
- go.opentelemetry.io/otel/sdk v1.14.0
- go.opentelemetry.io/otel/trace v1.14.0
These seem to correspond:
- go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.39.0
Other direct dependencies required to update by Otel:
- github.com/stretchr/testify v1.8.2
- google.golang.org/grpc v1.53.0
The changes in this release of gRPC are additional comments and constants in generated code.
I have not re-run the code generator.
Indirect dependencies required to update by Otel:
- cloud.google.com/go/compute v1.15.1
- github.com/cncf/xds/go v0.0.0-20230105202645-06c439db220b
- go.opentelemetry.io/otel/exporters/otlp/internal/retry v1.14.0
- go.opentelemetry.io/otel/metric v0.36.0
^^ this last one is suspicious because release notes say v0.36.0 corresponds to v1.13.0.
Also the import of go.opentelemetry.io/otel/semconv had to be updated to v1.17.0 to match https://github.com/open-telemetry/opentelemetry-go/blob/60f7d42d1eedae6381f1d6524374b57a274e1639/sdk/resource/process.go#L25

Thanks!


Planning: TokenScript attestation Java repo

Need to have a plan around the attestation.jar about the next updates to the Maven repo.

@jot2re should I close this item.

Yes, I am closing this how as it is handled by the the CI/CD work by Hu.


fix spinner styles

This bug happens if you use a spinner without a script. See on codepen

@sgomes wanna take a look at this v1 change?

Thanks for the PR, @enniel! I'll take a closer look next week.

LGTM, thanks @enniel!


CP-SAT: Minor version removed function

I don't think it is good practice to remove functions like AddSumConstraint in a minor release.
The new AddLinearConstraint function seems to be more powerful, but maybe marking the old function as deprecated first and removing them in a major release would be nice :)
Nevertheless, keep up the good work and support 👍

I know, but I am stretched too thin to maintain multiple code, especially
since internally, we port all user's code.
And frankly, calling it 8.0 would not have helped much, unless you really
want to block update based on version.
What is missing are the full release notes. They will come in soon.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
*De : *Phibedy<EMAIL_ADDRESS>*Date : *jeu. 9 mai 2019 à 21:07
*À : *google/or-tools
*Cc : *Subscribed
I don't think it is good practice to remove functions like AddSumConstraint

in a minor release.
The new AddLinearConstraint function seems to be more powerful, but maybe
marking the old function as deprecated first and removing them in a mayor
release would be nice :)
Nevertheless, keep up the good work and support 👍
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1262, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3MP2GJNZAUA64LGP5TPURZAXANCNFSM4HL5GIBA
.

Ok, good to know, thanks :)

Since at Google they use a monorepo there is no real notion of semantic versioning.
i.e. you break an API you can change all call site/user code and it's OK.
Further more since or-tools is a "software suite" while v7.1 have introduce breaking change CP-SAT this is not the case for the LinearSolver or Routing component -> major change for one component is a minor for an other component...
note: we don't have enough human resource to split in true separate component with their own version scheme....
note: You can also look at presentation on the Live At Head from abseil-cpp Team -> since it's a mandatory dependencies there are likely to impose their workflow/vision (i.e. no versioning) to all dependents (i.e. or-tools) (and most Google projet in near future ?)...

Could you please let me know what function is to replace addLinearSumEqual in Java?

https://developers.google.com/optimization/support/release_notes#cp-sat-api-changes
*De : *Dimitar Bakardzhiev<EMAIL_ADDRESS>*Date : *dim. 12 mai 2019 à 07:43
*À : *google/or-tools
*Cc : *Laurent Perron, State change
Could you please let me know what function is to replace addLinearSumEqual

in Java?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1262#issuecomment-491566551,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3LXEF4UVNZQ33YKCNLPU6VAVANCNFSM4HL5GIBA
.


Add dthang1972's file

created a branch, created a file and made a commit, and opened a pull request

Step 8 is done!


Possible missing text in fingerprint setup screen

On the "Set up fingerprint unlock" screen that provides details about how fingerprints work, on the last subsection named "Keep in mind", there are two paragraphs, and then there is a chain link icon with no text next to it.
I'd imagine if something is missing here, the issue is upstream as I don't believe this screen is ours. That said, it is worth exploring and confirming.

the corresponding string resource is empty at upstream.

https://android.googlesource.com/platform/packages/apps/Settings/+/master/res/values/strings.xml#831
https://github.com/GrapheneOS/platform_packages_apps_Settings/blob/14/res/values/strings.xml#L843

I see the stock pixel screen shows this link.
so we can either hide the row if empty or add an appropriate link.


Move preview GIF to GH user content thingy

True, maybe this will help (need to force-push to overwrite the history)

I managed to do it without rewriting every commit! I will close this PR though as it still has the Preview.gif blob.
I will instead change the link and co-author you on this one.


[PROCESS] Docusaurus v. MkDocs Assessment

Issue/Feature Description

Consider alternative build process infrastructure such as Docusaurus.

Discussion Topics

Internationalization
Website customization
Portable Markdown Content
Content Development Workflow

At this moment, I cannot say which tool I prefer based on personal experience, as I have no such experience.
However, in the eSSIF-Lab project, a Terminology section is currently being setup - not yet available now - using Docusaurus v2 (the new development they're doing). Since I'm involved in that I have a personal interest to align as much as possible, and therefore I second going to Docusaurus.


Include ripser as c++ library

Hi. Thanks for the great work.
Is there a chance to include ripser in a c++ project using a header file?
Thanks and cheers
Conrad

Hi,
this is easily possible by removing the main() method from ripser.cpp and turning it into a header file. You can then call ripser.compute_barcodes() like in the main method.
At some point, I might refactor the code to make this possible without editing the files.


Differentiate view/defaultView creation

Hi,
When a RCTViewManager call -(UIView*)view method, it is possible to know whether the call is for rendered view or default view?
Without this option I am not able to customize the defaultView further say don't set delegate property.
Thanks.

@skatou I'm confused by your question. Could you provide more information as to what you're trying to do?

@skatou this is not supported. You could work around it by sending a dummy prop from JS whenever the component is rendered and that would tell you which view is truly on the screen.
@nicklockwood do you think it's desirable to expose whether a view is the template default view?

I have a use case here where I'm using a shared video player instance and I determined I was in the rendered view and not in the default view since willMoveToSuperview was called.
This is an alternative to setting a dummy prop from JS.
// This is in the implementation of the view created by the view manager
override func willMoveToSuperview(newSuperview: UIView?) {
    super.willMoveToSuperview(newSuperview)

    // We're in the rendered view (and not in the default view)

    // Since we're sharing the player view and react
    // needs new view instances when calling the viewManager.view
    // we make sure only the displayed view has the player view with the video
    if player.view.superview != self {
        addSubview(player.view)
    }
}

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/differentiate-viewdefaultview-creation
ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub.
Also, if this issue is a bug, please consider sending a PR with a fix.
We're a small team and rely on the community for bug fixes of issues that don't affect fb apps.


Publishing artifacts requires build information to have already been collected

The current model for a Binary Artifact is:
{
    "_id" : ObjectId("57d2c61646e0fb000d3ef42d"),
    "_class" : "com.capitalone.dashboard.model.BinaryArtifact",
    "timestamp" : NumberLong(0),
    "artifactName" : "Helloworld",
    "canonicalName" : "Helloworld",
    "artifactGroupId" : "mygroup",
    "artifactVersion" : "myversion",
    "buildInfo" : {
        "_id" : ObjectId("57d2c6014cedfd0018e051e9"),
        "collectorItemId" : ObjectId("57d15681d601800018b4e626"),
        ...
   }
}

where buildInfo is a duplicate of what would exist in the build collection. At present buildInfo is populated by BinaryArtifactService by using a String representing an ObjectID that is passed in to the /artifact rest API endpoint.
This model requires a build to already exist in the database by the time artifact data is populated. It is also redundant. The result of this coupling prevents an artifact collector from being feasible as there wouldn't be a reasonable way to coordinate it with an independent build collector.
I propose that the BinaryArtifact document be changed to look something like this:
{
    "_id" : ObjectId("57d2c61646e0fb000d3ef42d"),
    "_class" : "com.capitalone.dashboard.model.BinaryArtifact",
    "timestamp" : NumberLong(0),
    "artifactName" : "Helloworld",
    "canonicalName" : "Helloworld",
    "artifactGroupId" : "mygroup",
    "artifactVersion" : "myversion",
    "buildData" : {
        "buildNumber" : 140
        "buildUrl" : "mybuildurl/job/etc"
   }
}

Code that needs to relate artifacts to builds can still do so by using buildUrl + buildNumber as a composite key to search for a unique build in the builds collection. This loosens the coupling allowing for artifact information and build information to be pulled independently of eachother. As a result an artifact collector could be created in the future (note that the artifacts would have to have metadata to associate them to builds such as artifactory properties).

PR #815


feat: minor bug fixes for BCSC

Codecov Report
Attention: Patch coverage is 83.16832% with 17 lines in your changes missing coverage. Please review.

Please upload report for BASE (test@cbfb7d1). Learn more about missing BASE report.
Report is 10 commits behind head on test.

Files
Patch %
Lines

...ambda/shared/templates/orphan-integration/index.ts
85.71%
5 Missing :warning:

lambda/app/src/controllers/requests.ts
55.55%
4 Missing :warning:

lambda/app/src/keycloak/idp.ts
20.00%
4 Missing :warning:

.../IntegrationInfoTabs/BcServicesCardStatusPanel.tsx
90.90%
1 Missing :warning:

app/utils/helpers.tsx
87.50%
1 Missing :warning:

lambda/app/src/keycloak/integration.ts
50.00%
1 Missing :warning:

...ions/2024.06.21T11.35.24.add-bcsc-prod-approved.ts
90.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             test    #1235   +/-   ##
=======================================
  Coverage        ?   71.63%
=======================================
  Files           ?      315
  Lines           ?    10957
  Branches        ?     2549
=======================================
  Hits            ?     7849
  Misses          ?     3108
  Partials        ?        0

Flag
Coverage Δ

unitests
71.63% <83.16%> (?)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Feature bug reporter

Moving this PR to track the version of feature-BugReporter on the leapmotion-examples repo and not @yuwilbur 's fork.


expire table metadata with ExpireSnapshots

This PR takes care of the issue #181 and is follow-up of #631.

Adds new method expireMetadataRetainLast to ExpireSnapshots.
If expireMetadataRetainLast(n) is called,  retains at least n latest metadata files and deletes rest.

I think this PR is a follow-up on #631.
As far as I remember, we planned that the main place to remove old metadata JSON files will be while expiring snapshots. After a quick look, it seems we won't delete metadata files unless the user explicitly calls a method in ExpireSnapshots. I would, probably, always reduce the number of metadata JSON files to a smaller number and expose a method to overwrite the number of files to keep. For example, we can have a table property that defines the default number of files to keep while expiring snapshots and a method to override this value programmatically.

FYI @arina-ielchiieva

I think the purpose of this PR is to implement a comment I made on #631:

I think if we add expiration during ExpireSnapshots, then that's when the number of metadata versions would be pruned. For example, expiration might keep 10 previous metadata file references. Between expiration calls, the ones tracked continues to grow.

The open question is how this should behave. I'm not sure I agree with what I suggested the last time, with separate configurations for number to keep when cleaning up during expiration and for the maximum number to keep when writing metadata. If possible, it would be better to have just one configuration and let users choose whether to delete old metadata files as new ones are written (the current implementation) or to delete old metadata files during snapshot expiration.
I think we need to have the ability to delete old metadata files as new ones are created, or else tables with lots of transactions will suffer from larger and larger metadata files between snapshot expiration runs. I'm not so sure that we need to clean up old files during snapshot expiration. It would be nice to do it, but we don't want metadata file contents to grow too large because of this.
Right now, I'm leaning toward not doing this cleanup during snapshot expiration. It's additional complexity for not much benefit. What do you think, @yathindranath, @aokolnychyi, and @arina-ielchiieva?

The default TableProperties.METADATA_DELETE_AFTER_COMMIT_ENABLED is false, if we enable this at a later point can leave orphan metadata files. I believe, it's better to do clean up of old metadata files during snapshot expiration and remove the current logic from the commit what we added in #631
@aokolnychyi we can have table properties for snapshot retention interval, number snapshots to retain

The main problem with removing old metadata versions in snapshot expiration is that the number of old metadata references in the metadata file can grow very large. How would we keep that from being a performance problem for tables if we only support removing old metadata files with expire snapshots?

@rdblue TableProperties.METADATA_PREVIOUS_VERSIONS_MAX limits the references of previous metadata files in the metadata file and won't grow very large after reaching max. The default value is 100 and it only keeps references of previous 100 metadata files at max.

Yes, the maximum limits the growth. But if we remove references to old metadata without deleting it, then files are still leaked. The purpose of keeping a list of old metadata files is to track and delete them.
That leak is why the approach I suggested in the other PR doesn't work. By the time expire snapshots runs, references may have been removed without deleting the files. That, or you let the list grow large with a huge maximum and probably hit performance problems. The only way to avoid the list growing large and avoid leaking files is to enable cleanup after commit.
And if we recommend cleanup after commit, then what is the value of cleaning up while expiring snapshots? I don't see much value in this because we can't reasonably get rid of the other cleanup method.
I think the best path forward is to default write.metadata.delete-after-commit.enabled to true.

Yes, the maximum limits the growth. But if we remove references to old metadata without deleting it, then files are still leaked. The purpose of keeping a list of old metadata files is to track and delete them.

Will dropped files be still referenced in old metadata JSON files? Whenever we expire snapshots, the list of files in the current version file might not have all of the old files we need to clean up. But what if we load some older files? We should be able to trace of them, right? (not sure about the complexity)
We definitely want to avoid the situation when the number of old metadata JSON files grows beyond a threshold as we've been in that situation before manifest lists.

As @aokolnychyi mentioned, we should be able to trace all of the files to delete by reading few metadata files. This PR follows the above approach to list all the files to delete.
May be we could deprecate write.metadata.delete-after-commit.enabled property and if write.metadata.previous-versions-max is defined, always cleanup after commit and no clean up while expiring snapshots.

Will dropped files be still referenced in old metadata JSON files?

Yes, but do we want to open lots of metadata files to get the set of files to delete? I'm assuming that we don't want to open multiple files to do this.

Yes, but do we want to open lots of metadata files to get the set of files to delete?

It is a bit unclear whether that will become a problem as we don't have to open every previous metadata file, it is enough to open only the last referenced. We will read 1 per 100 metadata files under the default configuration.
Having said that, I don't have a strong argument/opinion here. I want us to explore all options as it seems nice to have this logic if it does not complicate things or affect performance.

@rdblue any thoughts or suggestions?

@yathindranath, I don't think it's a good idea to include this in snapshot expiration, though I could be convinced otherwise. To keep this moving forward, let's start by adding a separate utility (maybe MetadataUtil.clean?) that traverses the old metadata lists to clean them up. Once we have that, it would be fairly easy to add that to snapshot expiration if we think it's a good idea.

@rdblue sounds good, shall I close this PR then?

Since we want to build actions for things like cleaning up orphan files, we can use this utility class there.

@yathindranath, that sounds good to me. I'll close this one.


Add support for Python 3.7-3.11, drop EOL 2.7-3.6

Add support for newer Python 3.7-3.11.
Python 2.7-3.6 are EOL and no longer receiving security updates (or any updates) from the core Python team.

cycle
latest
release
eol

3.6
3.6.15
2016-12-23
2021-12-23

3.5
3.5.10
2015-09-13
2020-09-13

2.7
2.7.18
2010-07-03
2020-01-01

They're also little used.
Here's the pip installs for thefuzz from PyPI for March 2022:

category
percent
downloads

3.8
84.01%
260,275

3.7
7.80%
24,177

null
4.06%
12,579

3.9
2.60%
8,051

3.6
0.82%
2,532

3.10
0.65%
2,017

3.5
0.06%
179

2.7
0.01%
20

Total

309,830

Date range: 2022-03-01 - 2022-03-31
Source: pip install -U pypistats && pypistats python_minor thefuzz --last-month
Also upgrade to modern Python syntax with https://github.com/asottile/pyupgrade/ and unit tests with https://github.com/isidentical/teyit.
Sample build:

https://github.com/hugovk/thefuzz/actions/runs/2082115423

Mind rebasing this?

Done! Please see PR https://github.com/seatgeek/thefuzz/pull/27 to fix the failing tests.

Rebased to include https://github.com/seatgeek/thefuzz/pull/27.

Looking forward to this pr merged!

While people are waiting for this to be merged in, you can still use these changes into your project by cloning hugos fork of the repo, checking out their branch, and installing the dependencies locally.
cd ~/apps  # just some folder that is outside of your project repo
git clone https://github.com/hugovk/thefuzz.git
cd thefuzz
git checkout update-versions
cd ~/path/to/your/project/repo

If you are a pipenv user like me, you can then install this as an editable dependency
pipenv install -e ~/apps/thefuzz

Advance warning: I normally close unmerged PRs after around a year (so ~April 2023 for this one), but hopefully this will be merged before then :)
I've also added 3.11 because RC1 is due out tomorrow and it's very important to test widely in advance of the full release in October:
https://discuss.python.org/t/the-last-3-11-beta-release-3-11-0b5-is-now-available/17693#warning-please-help-us-to-test-this-release-warning-1

@josegonzalez @bigtoast is there anything stopping this from getting merged?

Can we please get this merged?

Thanks for the pull request!


BUTTON LEVELS DO NOT APPEAR

Checklist:

[x ] I updated to the latest version available
[ ] I cleared the cache of my browser

Release with the issue:
V 1.4.4
Last working release (if known):
Browser and Operating System:
CHROME - WINDOWS 10

Description of problem:
I'am working with .GLB file. After update Home Assistant the buttons levels are not appearing at the top left of the 3d canvas.
I cleared the cache and nothing changed.
HA Actual Version
Home Assistant 2022.8.7
Supervisor 2022.08.5
Operating System 8.5
Frontend: 20220802.0 - latest

This is happening for me with .glb files as well. When I use .obj and .mtl files the level buttons appear correctly (but the model takes much longer to load)

@VITCHEPF It just started working for me. I switched to using the .obj and .mtl files, and then switched back to .glb and the level buttons were still present. I also closed the Sweet Home 3D app and reopened it, and the exported again. I'm not sure what exactly fixed it, but it's now working for me.

Ah this was the commit that broke it: https://github.com/adizanni/floor3d-card/commit/c000babf23210508eb4045caa92e02c358e4889d
You need to have hideLevelsMenu: 'no' in your config otherwise they are hidden by default. The condition should be updated to be!= 'yes' instead of == 'no'.

Hi @ndbroadbent, thanks for your support.
My Floor-3D plugin was working perfectly, until I did the HA update indicated in the bug report.
After this update the level menu disappeared.
I prove to check many things:  hideLevelsMenu: 'no' is correct in my config, I've already tried to use the obj + mtl version, I've uninstalled and reinstalled the plugin, I've cleared the cache several times, but the levels menu still hidden.
I've tried everything you can imagine, but the problem persists.
In this moment, I changed hideLevelsMenu: to 'yes', Closed the browser, Clearead the cache, Reopen the HA, Changed hideLevelsMenu: to 'no' and suddenly "Voila", the levels menu reappeared....
Unbelievable !


Error with Multiple Use of Embedded Type

Describe the bug
Bug? Expected?
I get an error when I use the same embedded type in one type.
To Reproduce
Create:
type Hoge @db(name: "hoge") {
  id: ID! @id
  name: String!
  foo: Fuga
  bar: Fuga
}

type Fuga @embedded {
  value: Int!
  time: DateTime! @createdAt
}

and prisma deploy. Then will get
Hoge
    × The relation field `foo` must specify a `@relation` directive: `@relation(name: "MyRelation")`
    × The relation field `bar` must specify a `@relation` directive: `@relation(name: "MyRelation")`

Expected behavior
I believe it should be like
Hoge: {
  id: "someId",
  name: "hogehoge",
  foo: {
    value: 100,
    time: "someTime"
  },
  bar: {
    value: 200,
    time: "certainTime"
  }
}

Versions (please complete the following information):

Connector: MongoDB
Prisma Server: 1.35-beta
OS: Windows 10 x64
other dependencies: "nexus": "^0.12.0-beta.6", "nexus-prisma": "^0.3.7", "prisma-client-lib": "^1.34.0"

Can you please name the relations like shown in the error message? with a @relation directive?
There are ambiguous relations that need manual resolution.
Hoge
    × The relation field `foo` must specify a `@relation` directive: `@relation(name: "MyRelation")`
    × The relation field `bar` must specify a `@relation` directive: `@relation(name: "MyRelation")`

Please refer to this section of docs: https://www.prisma.io/docs/datamodel-and-migrations/datamodel-MYSQL-knul/#the-@relation-directive

Hey,
we used to do this internally by generating names, but ran into situations where it was not possible to infer the users intentions during datamodel changes if the relations were not explicitly named. Since we do not want to write into your datamodel files we now require the user to name ambiguous relations.

Hmm that makes sense, understood. Thanks for the info.

@seed-of-apricot Thanks, please feel free to close the issue if you think that your issue is resolved. Thanks.


Issue with Volkov Labs Echarts Panel Plugin After Upgrading to Grafana 11.1.0

I recently upgraded my Grafana instance from version 10.0.2 to 11.1.0. I have been using the Volkov Labs Echarts Panel plugin installed via Dockerfile (volkovlabs-echarts-panel) with Apache Echarts without any issues in the older Grafana version. However, after the upgrade, the plugin now appears under the name Business Charts in Grafana, and chart not works, chart what i use is Sankey chart.
I understand that the volkovlabs-echarts-panel plugin might now be referred to as Business Charts, but this change has caused some confusion, and I am experiencing errors when trying to use my existing dashboards that previously worked without any problems.
What steps can I take to resolve the errors and ensure my dashboards using this plugin function correctly after the upgrade?
I appreciate your help in resolving this issue, as this plugin is crucial for my Grafana setup.
Error output
ECharts Execution Error
data is not defined
ReferenceError: data is not defined     at eval (eval at <anonymous> (https://name-of-grafana-instance/public/plugins/volkovlabs-echarts-panel/module.js?_cache=6.2.0:175:4689), <anonymous>:7:1)     at https://name-of-grafana-instance/public/plugins/volkovlabs-echarts-panel/module.js?_cache=6.2.0:175:6740     at Ud (https://name-of-grafana-instance/public/build/1247.34022e0fa8ad25da7b32.js:953:26125)     at nl (https://name-of-grafana-instance/public/build/1247.34022e0fa8ad25da7b32.js:953:45489)     at https://name-of-grafana-instance/public/build/1247.34022e0fa8ad25da7b32.js:953:43678     at O (https://name-of-grafana-instance/public/build/1247.34022e0fa8ad25da7b32.js:1036:1549)     at MessagePort.J (https://name-of-grafana-instance/public/build/1247.34022e0fa8ad25da7b32.js:1036:1913)

@ArtursTrubacs Apache ECharts panel joined Business Suite for Grafana we are developing and was renamed to Business Suite. The same time, we implemented breaking changes in v6. Please refer to the migration guide in the blog: https://volkovlabs.io/blog/echarts-panel-6.0.0-20240406/#migration-guide
We implemented migration logic in the panel, but it's not possible to cover all use cases.
Please let us know if there is anything else.


WSL turicreate.SFrame.explore error

Does TuriCreate explore GUI support Windows Subsystem for Linux? When I import some annotations and images and create ground truth annotation array in the SFrame then turicreate.SFrame.explore(), I get the below error
Materializing SFrame
>>> [0721/213119.241580:FATAL:zygote_host_impl_linux.cc(126)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
I saw a reference to opening the visualization tool using the python webbrowser library and tried to install and use firefox-esr like below but the same zygote/No usable sandbox error shows.
import os
os.environ['BROWSER'] = '/usr/bin/firefox'
import turicreate

Is this a known issue and lack of support for WSL? I am running the debian WSL image and have x11 setup with XMing running on the windows side. x11 programs such as xeyes work fine. Thanks.

Not a known issue, but not too surprising -- this is happening because we're trying to load CEF, and at least with the version we're using and the way we're using it, it doesn't appear to work in WSL. There is also code in master to allow turicreate.visualization.set_target('browser') to open a browser window to the URL at localhost, though it hasn't landed yet in a release. This may serve as a workaround until this issue is fixed more fully, but only if webbrowser.open generally works in Python in WSL (not sure if it does).
I'll keep this issue open to track fixing it on our end. Ideally we can provide a better experience for WSL users here.

After installing a bunch of dependencies (libnss3 libxcursor1 libgconf-2-4 libasound2 libxss1 libatk1.0-0 libcups2 libgtk2.0-0), I can reproduce this issue, using WSL1 and Ubuntu 18.
Using turicreate.visualization.set_target('browser') is not a workaround. That loads a webpage which contains only the text:
The resource '/index.html?type=table&id=0' was not found..


bug: root node get pruned when it's still referenced

Wrote a unit test to reproduce.
thanks @mmsqe
the problem is here, we can't simply delete the old root node because it might be referenced by other versions down the road, but I guess we also can't leave it there, because it might create a gap in the versions, which violates the assumption in the design, right? @cool-develope

Wrote a unit test to reproduce.
thanks @mmsqe
the problem is here, we can't simply delete the old root node because it might be referenced by other versions down the road, but I guess we also can't leave it there, because it might create a gap in the versions, which violates the assumption in the design, right? @cool-develope

thanks for this report, fixed in https://github.com/cosmos/iavl/pull/1007/files#diff-6df49839605c94e5caeb7d4549afe697ad97a00144ef26ec6746d9b5e8a3019cR162-R175

great, closing this one.


Using adoptResources:  Disabled fails to propagate FederatedNamespace, but federates consisting resources.

I have a single-cluster, control-plane scoped federation setup. Although it is an edge case, following the steps below results in an interesting behavior. (global.scope = "Cluster", syncController.adoptResources = "Disabled")

Create a test-namespace namespace
Create a FederatedDeployment in test-namespace. It won't be federated yet, because we haven't created the associated FederatedNamespace yet.
Create a FederatedNamespace in test-namespace.

The FederatedDeployment status shows as: PropagationStatus: False, Status: AlreadyExists, however the actual FederatedDeployment is schedule normally (PropgationStatus: true).

What would you like to be added:
I think of following solutions, but happy to hear other's opinions and suggestions.

Exclude namespaces from adoptResources rule. (always adopt)
Make special case in case of Host Cluster (adoptResource always enabled for Namespace in host cluster)

/kind feature

tl;dr Namespaces in a self-joined host cluster should always be adopted.
This is an interesting case.  Note that disabling adoption is intended to prevent accidental deletion of resources, so whether always adopting makes sense depends on whether a resource can be deleted.

In the case of a self-joined host cluster, the namespace has to exist and can't be deleted, so always adopting would appear to make sense.
In the case of a non-host member cluster, the namespace doesn't have to exist and can be deleted, so always adopting does not make sense.

In the case of contained resource propagation (i.e. 3), I think it's fine that resources are propagated if the namespace exists in the member cluster but the namespace can't be adopted.

I would like to work on this task.

Fixed by #1026


Fancy Zones - To be treaded as application to be visible in MS Teams

Description of the new feature / enhancement
In the PowerToys Fancy Zone template editor choose a Zone that will run as application. Once activated, application or current desktop will be visible in MS Teams under Share Application. Any app dropped in this fancy zone region will be able to quickly share without a need to open Share menu in MS teams.
Scenario when this would be used?
Context:
Currently on ultrawide monitors there is no option to share part of screen in MS Teams,
MS Teams only recognizes monitors/desktops and applications. Since there is no plan to enable custom screen region share in MS Teams currently. Perhaps there is an easy way to define a Fancy Zone as Application and share this via MS Teams as a workaround.
Supporting information
No response

This is such a needed feature for me as well.

/dup #2774


Bug: dragging repeatedly makes the arrows drift away from the block

When you drag a block repeatedly, the connecting arrows start moving away from their original position. To reproduce, go to the demo (https://alyssax.com/x/flowy/) and link two blocks. Now, drag the parent a minuscule amount several times.
Video:

Oops, the code in the live demo wasn't up to date with the codebase. It should work fine now :)


Text To Speech doesn't working

Hello,
Thank you for your tool, it's amazing.
I'm having some issues trying to initialize the text-to-speech or speech-to-text module. They don't appear in the popup generated by the icon. These options simply do not show up, even with the default configs.
I've tried inserting "textToSpeechLang" or "textToSpeech" in various places within the options, but without success so far.
I also tried to manage with the interfaces or even replicate in a new project, but without success.
I'm using Next.js v13, Node 18, with your module on the latest version.
Below is the custom component I created to be loaded in _app.tsx.
import { useEffect } from "react";
import { Accessibility } from "accessibility/dist/main";
import { IAccessibilityOptions } from "accessibility/dist/accessibility";
interface AccessibilityInitializerProps {}
const labels = {   resetTitle: "Reiniciar",   closeTitle: "Fechar",   menuTitle: "Opções de Acessibilidade",   increaseText: "Aumentar texto",   decreaseText: "Diminuir texto",   increaseTextSpacing: "Aumentar espaçamento de texto",   decreaseTextSpacing: "Diminuir espaçamento de texto",   increaseLineHeight: "Aumentar altura da linha",   decreaseLineHeight: "Diminuir altura da linha",   invertColors: "Inverter cores",   grayHues: "Escala de cinza",   underlineLinks: "Sublinhar links",   bigCursor: "Cursor grande",   readingGuide: "Guia de leitura",   textToSpeech: "Texto para voz",   speechToText: "Voz para texto",   disableAnimations: "Desabilitar animações",   screenReader: "Leitor de tela", };
const AccessibilityInitializer: React.FC<
AccessibilityInitializerProps
> = () => {
const options: IAccessibilityOptions = {
   labels: labels,
    textToSpeechLang: "en-US",
    speechToTextLang: "en-US",
    icon: {
      circular: true,
      position: {
        bottom: {
          size: "50",
          units: "%",
        },
        left: {
          size: "10",
          units: "px",
        },
      },
    },
  };
  useEffect(() => {
    new Accessibility(options);
    return () => {};
  }, []);
  return null;
};
export default AccessibilityInitializer;
Also, I've attached a screenshot of the generated popup without the text-to-speech option.
Sometimes I got this issue also which was fixed adding this module with npm install.
regeneratorRuntime is not defined
Please let me know if I could help you in somehow.

Well, searching a little further I actually found the solution.
Based on your docs website inspection, the script that it's initialized contains the language inside the options with something declared like this:
language: {
        textToSpeechLang: 'en-US',
        speechToTextLang: 'en-US'
    },
So the full options variable should be like this:
var options = {
    hotkeys: {
        enabled: true
    },
    icon: {
        circular: true
    },
    language: {
        textToSpeechLang: 'en-US',
        speechToTextLang: 'en-US'
    },
}
It's working now. Thanks.


Better error message for &. on non-nilable receiver

This adds a less confusing error message for cases where &. ("safe navigation") is used on a receiver that is not nilable. (Currently this shows up as a "code is unreachable" error inside the if-then-else generated by the desugarer.)
Implementation is as @DarkDimius outlines in #36, with the very slight difference that the "magic send" winds up being the second instruction in the block, not the first. (First instruction is an alias for the <Magic> class constant.)
Example:
# typed: true

extend T::Sig

if T.unsafe(false)
  foo = "hi"
else
  foo = 33
end

bar = foo&.to_s

Before:
editor.rb:11: This code is unreachable https://srb.help/7006
    11 |bar = foo&.to_s
              ^
Errors: 1

After:
editor.rb:11: Used &. operator on a receiver which can never be nil https://srb.help/7034
    11 |bar = foo&.to_s
              ^
  Type of receiver is String | Integer, from:
    editor.rb:6:
     6 |  foo = "hi"
                ^^^^
    editor.rb:8:
     8 |  foo = 33
                ^^
Errors: 1

Motivation
The weird error message in this case is a pretty common source of confusion among users.
Test plan
See included automated tests.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build result here:
→ https://go/builds/bui_ILJVnmh6v450Th


Improve message highlight visibility

Currently, the messages are highlighted by putting a halo around the appropriate point.  If this point is "in the back", it is often swamped by points on top of it.  If I added a dummy extra point, I could move it to on top of all the points and at the location of the highlighted point, and then show it, so it wouldn't get obscured.

The user who commented on this also thought colors could be different, but didn't have any better suggestions than that.  He thought that red for messages looked "too important or urgent" and that a different color should be used.


Re-order rows feature

Hi,
Seems there is no feature for reordering rows.

+1

This was added to RATreeView in version 0.9.0.
Closing. Feel free to reopen if necessary.

Maybe I wasn't entirely clear when I I closed this ticket.
There are no plans to add built in feature for row rendering. I added moveItemAtIndex:inParent:toIndex:inParent: method so that it is possible to implement reorder feature by adding some custom logic to the RATreeView. Unfortunately, as for now I don't see a way how could I add reordering feature in a way that would make it generic and possible to use it in different cases.

I have gotten reordering working. It is in a pull request.

I couldn't succeed reordering with moveItemAtIndex:inParent:toIndex:inParent: method  Any tips ?

I haven't looked at it for a while. You can clone my fork https://github.com/etresoft/RATreeView
I fixed a couple of bugs in the original that would prevent it from working. Then I added move support to the underlying UITableView and then added some delegate methods at the treeView layer. You should be able to extract it from the pull request.

I haven't looked at it for a while. You can clone my fork https://github.com/etresoft/RATreeView
I fixed a couple of bugs in the original that would prevent it from working. Then I added move support to the underlying UITableView and then added some delegate methods at the treeView layer. You should be able to extract it from the pull request.

How do you move the items physically on the screen? I tried your fork and didn't manage to move items.


bonds representation in fractors

To declare the bond type with a token call "ABC" and how does it work with ABC to be having 3 decimal for example 100.123 ABC that can be traded and swapped. How doe it handle on this case?

There are no decimal places involved. 1ABC would be considered the smallest unit of the ABC token. So to have 100.123ABC, one would have to work with 100123ABC (without the decimal point). If a decimal point is strictly required, this has to be added at a higher level as a wrap around the blockchain.

denom and token name should be declare correctly.
name: ABC
token: uabc
is that the right way to do so?

The bond name is descriptive and can be anything in reality. The token has to be a valid Cosmos SDK token denomination. Your example uabc is 100% valid!

Please do add some more explanation to the doc for the best practice.. I was getting confused.

Resolved by 2510156


[Bug] auto update

Description
funktionierende Updates kommen bald
Version
0.5
What browsers are you seeing the problem on?
No response
Steps to Reproduce

Screenshots
No response
Console output
No response
Additional Context
No response

fixed with version 1.0


Integration with HTML5 Canvas

Hi, I would like to integrate your library (to recognize hand-written Japanese) with a web app through html5 canvas.

I have a full time job and do this just as a hobby - I am not up for paid
assignments. Programming a web-app is beyond what I can do on my spare
time.
Of course, if you (or some other developer) want to go for it, it'll be
happy to answer questions or fix bugs of the lib.
regards
On Thu, Jan 29, 2015 at 10:33 AM, ocyedwin<EMAIL_ADDRESS>wrote:

Hi, I would like to integrate your library (to recognize hand-written
Japanese) with a web app through html5 canvas.
—
Reply to this email directly or view it on GitHub
https://github.com/asdfjkl/ctegaki-lib/issues/1.

If still relevant after all this time, see https://asdfjkl.github.io/kanjicanvas/ and https://github.com/asdfjkl/kanjicanvas (Implementation in client-side only Javascript). Ready to be embedded in other website.


Some tests fail when tensorflow is imported before catalyst

The imports
import tensorflow
import catalyst

do not always work, and some tests are failing if tensorflow is imported first. We can see that in when testing the wheels.
FAILED frontend/test/pytest/test_autograph.py::TestConditionals::test_qubit_manipulation_cond[lightning.qubit] - RuntimeError: random_device could not be read
FAILED frontend/test/pytest/test_conditionals.py::TestCond::test_qubit_manipulation_cond[lightning.qubit]
FAILED frontend/test/pytest/test_jax_integration.py::TestJAXJIT::test_multiple_calls[lightning.qubit]
FAILED frontend/test/pytest/test_mid_circuit_measurement.py::TestMidCircuitMeasurement::test_basic[lightning.qubit] - RuntimeError: random_device could not be read
FAILED frontend/test/pytest/test_mid_circuit_measurement.py::TestMidCircuitMeasurement::test_more_complex[lightning.qubit] - RuntimeError: random_device could not be read
FAILED frontend/test/pytest/test_pytree_args.py::TestPyTreesReturnValues::test_return_value_float[lightning.qubit] - RuntimeError: random_device could not be read
FAILED frontend/test/pytest/test_pytree_args.py::TestPyTreesReturnValues::test_return_value_tuples[lightning.qubit]
FAILED frontend/test/pytest/test_measurements_results.py::TestOtherMeasurements::test_multiple_return_values[lightning.qubit]
FAILED frontend/test/pytest/test_jit_behaviour.py::TestCallsiteCompileVsFunctionDefinitionCompile::test_equivalence[lightning.qubit] - RuntimeError: random_device could not be read
FAILED frontend/test/pytest/test_jit_behaviour.py::TestDecorator::test_function_is_cached[lightning.qubit] - RuntimeError: random_device could not be read
FAILED frontend/test/pytest/test_pytree_args.py::TestPyTreesFuncArgs::test_args_used_in_measure[lightning.qubit] - RuntimeError: random_device could not be read
FAILED frontend/test/pytest/test_jit_behaviour.py::TestCaching::test_function_is_cached[lightning.qubit] - RuntimeError: random_device could not be read
FAILED frontend/test/pytest/test_pytree_args.py::TestPyTreesFuncArgs::test_args_used_indirectly_in_measure[lightning.qubit] - RuntimeError: random_device could not be read
FAILED frontend/test/pytest/test_jit_behaviour.py::TestShots::test_shots_in_decorator_in_sample[lightning.qubit] - RuntimeError: random_device could not be read
FAILED frontend/test/pytest/test_jit_behaviour.py::TestShots::test_shots_in_callsite_in_sample[lightning.qubit]
FAILED frontend/test/pytest/test_qnode.py::test_variable_capture[0-False]
FAILED frontend/test/pytest/test_pytree_args.py::TestPyTreesReturnValues::test_return_value_dict[lightning.qubit]
FAILED frontend/test/pytest/test_loops.py::TestWhileLoops::test_alternating_loop[lightning.qubit]
FAILED frontend/test/pytest/test_conditionals.py::TestCond::test_identical_branch_names[lightning.qubit] - RuntimeError: random_device could not be read
FAILED frontend/test/pytest/test_contexts.py::TestTracing::test_fixed_tracing[lightning.qubit] - RuntimeError: random_device could not be read
FAILED frontend/test/pytest/test_contexts.py::TestTracing::test_cond_inside_while_loop[lightning.qubit]
FAILED **frontend/test/pytest/test_variable_wires.py::TestBasicCircuits::test_measurements[lightning.qubit-args0]**

I have contributed to the discussion on this ticket after our investigation https://github.com/tensorflow/tensorflow/issues/61741#issuecomment-1749307431

Looks like this issue has been fixed upstream.


Java Code for Maximal Square

Hey!
I would like to contribute the solution for this problem in Java.
https://leetcode.com/problems/maximal-square/
Please assign this issue to me

Create a PR and tag this issue there.

This repo supports adding code files directly in PRs(after reading Contributing.md). If you were found creating unnecessary Issues/PRs, then this can lead to a permanent ban or disqualification from hacktoberfest.


Allow AbstractUnitRanges for indices for composition with OffsetArrays

Pending https://github.com/JuliaArrays/OffsetArrays.jl/pull/296


[fix][io] Include Alluxio in the distribution

Motivation
Currently, the alluxio submodule is not included in the Pulsar IO distribution.
$ ./mvnw clean install -DskipTests

...

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  12:09 min
[INFO] Finished at: 2022-12-27T11:14:55+09:00
[INFO] ------------------------------------------------------------------------
$ ls -l distribution/io/target/apache-pulsar-io-connectors-2.12.0-SNAPSHOT-bin
total 1721216
-rw-r--r-- 1 sekikn sekikn     13300 12月 27 11:02 LICENSE
-rw-rw-r-- 1 sekikn sekikn   8352752 12月 27 11:02 pulsar-io-aerospike-2.12.0-SNAPSHOT.nar
-rw-rw-r-- 1 sekikn sekikn  15910726 12月 27 11:02 pulsar-io-batch-data-generator-2.12.0-SNAPSHOT.nar
...

Modifications
This PR fixes the problem above and addresses some checkstyle and OWASP issues.
Verifying this change

[x] Make sure that the change passes the CI checks.

This change is already covered by existing tests, such as unit tests under pulsar-io/alluxio/src/test.
Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[x] Dependencies (add or upgrade a dependency): upgraded Alluxio 2.5.0 to 2.7.3 for addressing OWASP issues.
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[x] doc
[ ] doc-required
[ ] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository: https://github.com/sekikn/incubator-pulsar/pull/4
There are a few failures in the BROKER_CLIENT_IMPL and OWASP tests, but I think the former is unrelated with this PR and no CVE is newly introduced in the latter.

/pulsarbot run-failure-checks

Codecov Report

Merging #19095 (a3a14d1) into master (492a9c3) will decrease coverage by 10.21%.
The diff coverage is 16.66%.

@@              Coverage Diff              @@
##             master   #19095       +/-   ##
=============================================
- Coverage     47.46%   37.24%   -10.22%
+ Complexity    10727     1990     -8737
=============================================
  Files           711      209      -502
  Lines         69456    14452    -55004
  Branches       7452     1577     -5875
=============================================
- Hits          32964     5382    -27582
+ Misses        32810     8486    -24324
+ Partials       3682      584     -3098

Flag
Coverage Δ

unittests
37.24% <16.66%> (-10.22%)
:arrow_down:

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

Impacted Files
Coverage Δ

...va/org/apache/pulsar/client/impl/ConsumerImpl.java
15.06% <0.00%> (-0.04%)
:arrow_down:

...lsar/client/impl/conf/ClientConfigurationData.java
96.66% <100.00%> (ø)

...broker/stats/prometheus/metrics/ObserverGauge.java

...he/bookkeeper/mledger/offload/OffloadersCache.java

...a/org/apache/bookkeeper/mledger/ManagedCursor.java

...schema/exceptions/IncompatibleSchemaException.java

...org/apache/pulsar/proxy/stats/ConnectionStats.java

...ulsar/broker/stats/BookieClientStatsGenerator.java

...ar/common/naming/PartitionedManagedLedgerInfo.java

... and 495 more


Deploy namespace during Shoot migration flow

How to categorize this PR?

/area high-availability
/area control-plane-migration
/kind enhancement
What this PR does / why we need it:
The control-plane namespace in the seed should be redeployed during shoot migration flow, mainly to update the zone information in the namespace similar to #8079.
Without this clusters could get stuck in migration phase because the zones specified in the namespace could be outdated. This can especially happen for hibernated clusters where pods from the etcd-events statefulset could have a node affinity for nodes in a differing zone than the one specified in the nodeAffinity of their PV because of #8563
Special notes for your reviewer:
/cc @timuthy
Release note:

The shoot namespace in seeds is redeployed during the shoot migration flow to update the zones in use.

/approve
/retest


Cycle 4 Funding: Array API and astrowidgets (Craig)

Issue to track progress of Cycle 4 funding request which was approved in https://github.com/astropy/astropy-project/pull/393 .

Project Description
Awarded Amount: $11,250 (US)
Period of Performance: 2024-05-01 through 2025-04-30
Finance Committee Contact: @jdswinbank
COTR: @pllim

Hey Matt
Let's get you started on getting a new contract with NumFocus because I think that's gonna take them a little while. Here are the instructions:
Go to https://numfocus.org/rocket
Click on Independent Contractor Registration
Form fields
Project: Astropy
Grant: NASA
Full Name
Email address
Street Address
Street Address
City
State
Postal Code
Country
Start Date: May 1, 2024-Feb 28, 2025
Description: Specreduce and spectroscopy development
Project Contact name: Astropy Finance Committee
Project Contact email<EMAIL_ADDRESS>Payment method: ACH, Wire Transfer, PayPal
Bank Information
Comments about payment
Upload W9 or W8
Please let me know that you have submitted the form so we can keep track of it.

Hi @AnaGabela -- I just filled out the contractor form.

Just so we're clear what I should be tracking, Awarded Amount: $11,250 (US) means Astropy is only funding "ccdproc and astropy.nddata work" section of https://github.com/astropy/astropy-project/blob/main/finance/proposal-calls/cycle4/mwcraig-cycle4-ccdproc-astrowidgets.md ?

Yes I only see the Awarded Amount: $11,250 (US)

Ah, I see https://github.com/astropy/astropy-project/pull/393#issuecomment-2090515053 now but unclear from the comment what exactly is being funded for a year. @jdswinbank , can you please clarify? Thanks!

... Astropy is only funding "ccdproc and astropy.nddata work" section ...

This is correct.

I think it would be appropriate for mwcraig to choose

Should this be decided upfront so we can set the expectations early on?

Should this be decided upfront so we can set the expectations early on?

Probably -- the work I've started doing was on ccdproc since the funded amount matched that part of the proposal, and because it was pretty out of date infrastructure-wise.
We should talk about whether it makes sense to do a mix of things from both projects, though.

Okay. Is that talk between Matt and Finance Committee? Do I have to be involved too as COTR? My "job description" says I have to make sure the progress meets expectation so I don't want to end up bugging Matt about things that are not actually relevant here. Thanks!

From the PR with the proposal:

Rather than have the Finance Committee select from the various options you presented, we suggest that you discuss this and agree a course of action with the COTR when assigned.

I'm fine if we just want to declare that the course of action is to do the ccdproc/nddata stuff, but if you think it would be better to do a mix of tasks that would work for me too.

Since I am also personally involved in Astrowidgets, I cannot give an unbiased opinion on what work should be done. But if I say "both," I am worried that each will not have enough progress given the reduced funding. What combo would give us the best return of investment here? Any ideas?

I'd lean towards the ccdproc/nddata work since there is other work being in astropy to adopt the array API.


Install gRPC extension

I am using firestore in my php project the cal I use with ddev, I would like you to install the grpc extension, since I must install it manually to be able to use firestore with ddev thanks.

I think the solution in https://stackoverflow.com/a/60554990/215713 will work for you. That shows a pecl install of a different extension, so you just need to swap mcrypt for grpc according to https://cloud.google.com/php/grpc
AFAICT there isn't a debian package for php-grpc, so you'd need to use the Dockerfile approach.  It's easier with the packaged approach.

No response from OP, but the suggested solution should work. Happy to continue the conversation here or elsewhere, but closing for now.

Maybe that can help: https://github.com/cmuench/grpc-demo/blob/master/examples/php/.ddev/web-build/Dockerfile


Add parsing logic for GoogleMeshCaConfig

Note that some of the default values might change pending discussion.

This change is

Issues:#23597

Thanks for reviewing!


Set up blog to show progress of LionWeb

As decided on 2023-09-29, we want to create roughly monthly blog posts to inform publicly about our progress.

Added on 2023-10-27:

Create LionWeb org on LinkedIn (e.g. OMG is a company)
Should (also) be on LW page (e.g. in .github/blogs)


Does the @profile decorator affect memory usage?

I added the @profile decorator to the method of the class I use for training deep learning models. However, when I checked the memory usage with nvtop, I noticed that memory consumption decreased compared to before adding the decorator. Additionally, surprisingly, the run time also seemed to be shorter. I initially thought that the Memory Profiler only tracks memory usage, but does it actually influence memory usage?
Thank you!

The line-profiler makes a torch.cuda.empty_cache() call after every lines of the function being decorated.
So probably you have too many memory fractions and allocating \ freeing cuda memory may cost considerable time in this case.

Thank you for your detailed explanation!
It clarified my doubts and gave me a good opportunity to review my implementation.


Reminder 6.2.1802-pyxy_2 freecad issues

this build has issues with freecad. I guess it is caused by the added patch. I will change this once smesh is able to build on osx.

@conda-forge/core sry again there is the need to disable some builds:
all 6.2.1802-py_2 and 6.2.1802-py_1

Just did that. Can you check if I got the right ones?

perfect, thanks


Deprecate Go 1.15 and 1.16

Issue #, if available:
Description of changes:
After EKS-D started supporting K8 1.27, EKS-D has stopped supporting k8 1.22. All our projects supporting k8 1.23-1.27 are build from EKS-Go 1.17-1.20. Thus, we are moving forward with deprecating EKS-Go 1.15 and 1.16 (will not update or backport new CVE'ss). All our Golang artifacts from EKS-Go 1.15 and 1.16 are still will be available in our Public ECR.
As this poses immediate risk to users of EKS-Go 1.15 and 1.16, we advise them it is HIGHLY recommended that users of EKS-GO v1.15 - v1.16 update to a supported version of EKS-Go (v1.17+) as soon as possible.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


No Data Explorer on latest Insider Build is not visible

Issue Type: Bug
Installed latest insider build download. I receive this error when opening:

There is no ability to view a SQL Server instance in server explorer.

Process explorer does not show the services is running:

Azure Data Studio version: azuredatastudio 1.6.0-insider (1bac929ab38e64560a6f663baa086a9b540c083c, 2019-03-25T23:25:02.789Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2112)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.88GB (5.19GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

Additional details found... The log file showing in the message is not actually generated.

@wsmelton Thanks for reporting the issue. We are aware of the issue and it's fixed in the coming latest insider release.

So no "hey yeah don't let insiders update because it will become unusable" notice or anything?!!??
I mean we can't roll back to a previous version of insiders....

@wsmelton Sorry about the issue, the next insider's build shouldn't have this issue.

Is that going to be pushed out within the next hour?

@wsmelton Yes, it will be out soon today.


Follow stdlib's leading underscore rule

Renames a couple of non-public symbols which don't follow stdlib's Leading Underscore Rule:
OrderedDictionary.Elements.SubSequence.Iterator.init(_ base: OrderedDictionary.Elements.SubSequence)

changed to
OrderedDictionary.Elements.SubSequence.Iterator.init(_base: OrderedDictionary.Elements.SubSequence)

and
OrderedSet.SubSequence.init(base: OrderedSet, bounds: Range<Int>)

changed to
OrderedSet.SubSequence.init(_base: OrderedSet, bounds: Range<Int>)

Checklist

[x] I've read the Contribution Guidelines
[x] My contributions are licensed under the Swift license.
[x] I've followed the coding style of the rest of the project.
[ ] I've added tests covering all new code paths my change adds to the project (if appropriate).
[ ] I've added benchmarks covering new functionality (if appropriate).
[x] I've verified that my change does not break any existing tests or introduce unexplained benchmark regressions.
[x] I've updated the documentation if necessary.

@swift-ci test


Table.getRow() is 0-based

...which would be fine, but it retrieves the first data row, so there isn't a way to retrieve the header row, should you want it.

I think table.ordinals will give you what you want (and they Weill be in order too!)

To clarify, table.ordinals is the header row (in order); Table.getRow(0) returns row 2 in the sheet.


Recommend more idiomatic way to trust user in Cachix error

When using devenvs without having set up Cachix, it gives the following output.
✖ You're not a trusted user of the Nix store. You have the following options:

a) Add yourself to the trusted-users list in /etc/nix/nix.conf by editing configuration.nix for devenv to manage caches for you.

{
    nix.extraOptions = ''
        trusted-users = root victor
    '';
}

b) Add binary caches to /etc/nix/nix.conf yourself by editing configuration.nix:
{
    nix.extraOptions = ''
        extra-substituters = https://devenv.cachix.org
        extra-trusted-public-keys = devenv.cachix.org-1:w1cLUi8dv3hnoSPGAuibQv+f9TZLr6cv/Hm9XgU50cw=
    '';
}

Disable automatic cache configuration in `devenv.nix`:

{
    cachix.enable = false;
}

Lastly, rebuild your system:

  $ sudo nixos-rebuild switch

• Failed to get cachix caches due to evaluation error

Solution a) uses nix.extraOptions to add the user to the trusted ones of the Nix store, but there is a more idiomatic way to do this (I don’t know when it was added, but it seems at least present in 24.05 and above).
{
  nix.settings.trusted-users = [
    "victor"
  ];
}

Whoops, just realised it has been fixed upstream.


Add Article for Hello World in Julia

Merged script #9 but never wrote article.

Publishing tomorrow: https://therenegadecoder.com/code/hello-world-in-julia/
Adding link now.

Added link.


What is a "non-algebraic" solver?

Do you mean geometric multigrid?

Among others, yes.
A non-exhaustive list of what we have/have planned is:

Vanka methods
Subspace correction methods
Geometric MultiGrid
Domain Decomposition methods, such as BDDC
...

Perhaps this is the "best" name. So what is actually implemented?

Yes, all the things in the README are implemented.


Doc | Adding CODE-OF-CONDUNCT.md and CONTRIBUTING.md

What?
Commits on Feb 10, 2023

Adding 1st version of the binbash Leverage standard CODE-OF-CONDUNCT.md and CONTRIBUTING.md  - @exequielrafaela

Why?
Necessary and in line to the following issues:

https://github.com/binbashar/le-ref-architecture-doc/issues/150
https://github.com/binbashar/le-ref-architecture-doc/issues/143

@juanmatias I'll move forward merging this PR as a 1st iteration that's linked in the leverage doc.

CC: @diego-ojeda-binbash @angelofenoglio


Error running mnist_simple.jl

Hi
Training runs fine, the /tmp/tms.tm is saved but it fails at the following step, compiling the model:
_, tm = combine(tms[1:500], 2, x_test, y_test, batch=true)
My julia version is 1.10.2 (2024-03-01)
OS is Linux  6.5.0-26-generic #26~22.04.1-Ubuntu
Below is the full output.

Running in 4 threads.
Accuracy over 1 epochs (Clauses: 2048, T: 32, R: 0.94, L: 12, states_num: 256, include_limit: 128):
#1  Accuracy: 96.01%  Best: 96.01%  Training: 124.452s  Testing: 0.247s
Done. 1 epochs (Clauses: 2048, T: 32, R: 0.94, L: 12, states_num: 256, include_limit: 128).
Time elapsed: 00:02:05. Best accuracy was: 96.01%.
Saving model to /tmp/tms.tm... Done.
Loading model from /tmp/tms.tm... Done.
ERROR: LoadError: BoundsError: attempt to access 1-element Vector{Tuple{Float64, Main.Tsetlin.AbstractTMClassifier}} at index [1:500]
Stacktrace:
[1] throw_boundserror(A::Vector{Tuple{Float64, Main.Tsetlin.AbstractTMClassifier}}, I::Tuple{UnitRange{Int64}})
@ Base ./abstractarray.jl:737
[2] checkbounds
@ ./abstractarray.jl:702 [inlined]
[3] getindex(A::Vector{Tuple{Float64, Main.Tsetlin.AbstractTMClassifier}}, I::UnitRange{Int64})
@ Base ./array.jl:973
[4] top-level scope
@ ~/tmp/Tsetlin.jl/examples/mnist_simple.jl:46
in expression starting at /home/cezar/tmp/Tsetlin.jl/examples/mnist_simple.jl:46

Thanks.

I found when this happens - because the # of epochs was smaller than best_tms_size (=500) and lower than the 500 value in
_, tm = combine(tms[1:500], 2, x_test, y_test, batch=true)
btw, shouldn't there be best_tms_size instead of a literal 500 ?
So it assumes # of epochs should be high. I cannot afford that amount of time to see results. it took 5 minutes for first 6 epochs, with reduced clauses.
A piece of biased advice, for a first demo I recommend a piece of code able to finish in ~2 minutes instead of hours on ordinary hardware, because it is more inviting for would-be followers to keep ... following.
Expedience often trumps top accuracy.

Otherwise what you do in this repository seems to have great potential

So it assumes # of epochs should be high. I cannot afford that amount of time to see results. it took 5 minutes for first 6 epochs, with reduced clauses.
A piece of biased advice, for a first demo I recommend a piece of code able to finish in ~2 minutes instead of hours on ordinary hardware, because it is more inviting for would-be followers to keep ... following.

Thank you for the feedback.
As far as I know, Tsetlin.jl is one of the fastest Tsetlin Machine implementations available.
You can try the following hyperparameters to achieve satisfactory results with a small number of clauses:
const EPOCHS = 300
const CLAUSES = 128
const T = 8
const R = 0.89
const L = 16

@Blimpyway
How many predictions did you obtain on mnist_benchmark_inference.jl using your CPU?
Run julia --project=. -O3 -t 32,1 mnist_benchmark_inference.jl where 32 is the number of your logical CPU cores.

I've posted it on reddit, I have a 4 core cpu. The benchmark  is fine, what I found slow was the default 1000 epochs (?) and 2048 clauses in mnist_simple.jl - that training would take hours.
I don't deny it is fast  among tsetlin implementations, for a casual curious (as I was) a shorter train which achieves a significant result (97-98%) in minutes would be more relevant/appealing.  Maybe two demos "a really simple first try" one and a "overnight great expectations".
Another issue I noticed the optimised network is  made using x_test and y_test which casts doubt on whether final best performing combination is a test data-aware cerry picked combination of best networks, which is a no-no for paper reviewers.  Not touching x_test until the final benchmark (base all optimizations on x_train alone) does not significantly change end result.

Yes, the combinatorial merge example is overfitted on test data and is not suitable for paper reviews. However, this approach is still useful for k-fold cross-validation or augmented validation datasets.

Regarding dataset - I'm really happy with a single threshold - e.g. 0.33
MNIST is really on/off turning a couple bits on or off doesn't really change anything, and expanding the training set from 60k to 120k or 180k points might get picky reviewers suspicions of data augmenting (which it isn't).
so I'm happy with the results (98.49% in under 8 minutes, 4 threads) with the following parameters:
x_train = [TMInput(vec([
[x > 0.33 ? true : false for x in i];
])) for i in x_train]
x_test = [TMInput(vec([
[x > 0.33 ? true : false for x in i];
])) for i in x_test]
const EPOCHS = 20
const CLAUSES = 512
const T = 32
const R = 0.94
const L = 16

JFYI: For 512 clauses optimal parameters are:
const CLAUSES = 512
const T = 16
const R = 0.92
const L = 12

Thanks.
Regarding the parameters you recommended - as a quick demo ending in a couple minutes it works great with 30 epochs instead of 300 - 97.65% on a tiny 20k param model, before finishing a cofee - very happy with that!
    const EPOCHS = 30
    const CLAUSES = 128
    const T = 8
    const R = 0.89
    const L = 16

Since I'm a Julia (and Tsetlin) illiterate to really understand the code, I hope you don't mind a few following questions here.
One is about the README stating the L (number of literals) is different from vanilla Tsetlin.
Assuming a MNIST binarized digit input (x) with 784 bits, what mapping is assumed between a clause with only e.g. 16 literals and the 784 input bits?
Does the "canonical" tsetlin assigns 784 literals per clause?
Thanks
.

Thank you, it was a typo in the README.
The hyperparameter L limits the number of included literals in a clause.
The main idea is described in this paper: https://arxiv.org/pdf/2301.08190.pdf with additional performance improvements from my side.
You can add the verbose=2 parameter to the train!() function to get statistics on included literals during training:
train!(tm, x_train, y_train, x_test, y_test, EPOCHS, best_tms_size=best_tms_size, shuffle=true, batch=true, verbose=2)

Don't forget to do a git pull before using this functionality.

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
mxmlsn, @luotuo29, @jiaoqsh, @roylee17, @mengguang, @stormtrooper42, @alakesh, @jwaugh, @gabbieianatangan180, @baryon, @eddiewang, @yaxinr, @esneider, @bzeron, @zhiyuan2007, @davecgh, @inancgumus, @sajad2212, @debuggor, @YoheiShinozaki, @tcpaul, @mosjin, @kissthink, @FarYoung, @monomania, @Lord-Menes, @codeliger, @qcbit, @bijeebuss, @zackslash, @shino1486, @hina1975, @donghquinn, @gusutabopb, @felipecsl, @ZhiliangGong, @hughwang41, @Jackneill, @theodesp, @f13end, @xrash, @msafi, @mastercyb, @hiroki-money, @danryan, @cute-angelia, @boolw, @t32k, @zhongfu, @paddyva


[release-4.3] Bug 1796822: Support deployment on OpenStack with self-signed certificate

This is a backport of #445.

/lgtm

/assign @adambkaplan
PTAL

/retest

/approve


Adds Pi Day post

Hoping to post this to HackerNews and Reddit on Pi Day 2023.

Though is there something we can do about the S-strings? If I saw this and didn't know much PRQL, I'd think "Ha, that's pretty cool!", but then also "this does not look pretty at all, it's much less clear worse than SQL."
I'd be partially-but-not-fully comforted by "these are workarounds, they're only needed because we have a bug in our compiler"...

I've added an explanation for the presence of the s-strings and also a blurb about functions and how they are used here.
From my side, this is good to go now.
Welcoming any improvements on the flow of the text, typos etc...


How to set / clear custom boolean attribute?

Currently I cannot set/clear custom boolean attribute as stated in the hyperHTML docs.
It is only possible with a workaround IMO however, see the example code here:
import { html, render } from "lighterhtml";

document.body.appendChild(
  html`

      set custom attribute top (wrong top="true")

      clear custom attribute top (wrong top="false")

      clear custom attribute top (working)"

      Different behaviour for well known attributes

      <button disabled="${true}">Disabled button</button>
      <button disabled="${false}">Enabled button</button>

  `
);

A link to codesanbox:
boolean attribute example
An intended behaviour or my bad understanding of documentation?
Sorry this might be related or duplicate of #19

top is not a boolean attribute ... boolean attributes are those defined by specs as such, like button.disabled and similar.
to drop attributes that are not standard, use null or be are, whatever thing you pass will be set as string, even an empty one.
I also suggest to not use non standard attributes, you have both custom elements, and data- attributes for that.