Input points for testing and training

Testing and training are based on 3 points. I would like to change it to 5 points (adding points with two feet). Where should I modify it?

Hey, you can simply change the data preprocessing code in prepare_data.py to add also foot pose, and increase the number of inputs of the network

嘿，你可以简单地在prepare_data.py中更改数据预处理代码，以添加脚姿势，并增加网络的输入数量

when i use z to up, wherever x and y are facing, it will cause this:

only when i use z to forward, x to left, y to up, it will cause this, but it not stand and Lifting feet is easy to fluctuate. when i see dataset_amass or your dataset_tracking, the data always z to up, but final result is right. my data z to up is not success. That's why? Thanks
Add a comment
Comment
Add your comment here...
Remember, contributions to this repository should follow our GitHub Community Guidelines.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development
No branches or pull requests
Notifications
Customize
You’re receiving notifications because you authored the thread.
2 participants


feat: add acquisition functions

You are right, I forgot to migrate np.nan_to_num() check from the playground script to the metric. With that function encapsulating the log the result will be the proper one as 0 * x = 0, where x is the substitute number in np.nan_to_num(). Negatives numbers shouldn't be expected as the input as a matrix of probabilities.

What if we transform it like the following: ModelWrapper will be an abstract class with one/two methods including predict_probabilities(data_path: Path). And it will be inherited by actual model classes like class LogisticRegressionModel(ModelWrapper):, class ResNetModel(ModelWrapper): etc. As an example, we can implement only the logistic regression thing, overall flow and the architecture is very good, I just want it to be more explicit for the user. This way we will be more explicitly saying that acquisition functions are agnostic to ML models, just implement the ModelWrapper class.


add default return on tracked schemas

In some cases when the Application environment is not fully filled this library tries to fetch tracked_schemas configuration value with no default return. It results in errors on functions that use it expecting a list of schemas.
This default return pattern is already used here on ExAudit.Type.Schema

@rauann Can you resolve the mix.lock conflict so this can get merged?

done @narrowtux

Cheers


Bump flutter_hooks version to 0.19.0

Resolves version solving failure by upgrading the flutter_hooks dependency version to the latest version.

@jezsung Thanks!


chore: Remove feature flag for application templates

Description
Removed feature flag for templates as we're planning to go live
Fixes #12484
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Manually

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

/ok-to-test sha=372a60252480355b6f53bc2cdc0ba21b10c515fe

/ok-to-test sha=3f8b5ae


Wallet should emit some kind of Channel Defunded event

The wallet should emit some event that indicates the funds have been withdrawn from a channel

Based on our challenging-v0 story we plan on handling the ChannelFinalized event internally to trigger PushOutcomeAndTransfer. Therefore we need an event to dispatch to the app to indicate that the challenge is complete and funds are ready to be withdrawn.
To do this we can emit a ChannelDefunded event that fires whenever we withdraw from a channel (via a cooperative or non-cooperative close).

After thinking about this, I think this is already covered by the ChannelUpdated events that get emitted when the holdingUpdated event fires.


Viz - various improvements

[browserify] re-add policyDebug option
[viz] vr: epic perf fix
[viz] vr: package label on hover

these changes were largely resurrected from some old incomplete viz work sessions

@weizman unexpected scuttling related test failure here

@weizman unexpected scuttling related test failure here

Just forgot to update policy.json #442 (merge to fix).
Also, there is a new file xyz.js in the root dir, in case you added it by mistake.

@weizman unexpected scuttling related test failure here

@kumavis  Just forgot to update policy.json #442 (merge to fix).
Also, there is a new file xyz.js in the root dir, in case you added it by mistake.

@weizman oh thanks!
the error message made me think it was scuttling related
 Error: LavaMoat - property "Math" of globalThis is inaccessible under scuttling mode. To learn more visit https://github.com/LavaMoat/LavaMoat/pull/360.
  at get (testBundle.js:11205:19)
  at Object.<anonymous> (testBundle.js:11723:35)
  at Object.<anonymous> (testBundle.js:11725:4)
  at internalRequire (testBundle.js:11265:27)
  at requireRelative (testBundle.js:11308:27)
  at requireRelativeWithContext (testBundle.js:11277:18)
  at Object._defineEntry (testBundle.js:11701:24)
  at Object.<anonymous> (testBundle.js:11703:6)
  at internalRequire (testBundle.js:11265:27)
  at runModule (testBundle.js:11679:12)
error Command failed with exit code 1.

Yea I'm pretty sure that is an error message being thrown on purpose by the scuttling test, not sure why it is being printed out in the process..

https://github.com/LavaMoat/LavaMoat/actions/runs/3888067554/jobs/6635015908
 [2023-01-10 23:15:13] [build-stderr] java.lang.OutOfMemoryError: Java heap space

:shrug:


Port algorithms from GraphSharp.Samples to here

It's been a while so it makes sense to port them here.

Done


Add sale pricing to detailed spotlight

Prior to merging, need to bump version and update Gemfile in https://github.com/deseretbook/nibley/pull/1006

 (2) Update Promo Banner

@ericsaupe will you code review this?

Looks good :panda_face:


How to save some parts of audio to a wav/mp3 file?

Hi, waveform.js is a great library, I am using it for my audio annotation project. Now I want to save some parts/regions of the loaded waveform as audio file (wav, ogg or mp3), how can I do this? Or at least how can get the raw audio data behind the waveform? Thanks a lot,

try the wavesurfer.exportPCM method.

no feedback, closing.

@nahansans please see https://github.com/katspaugh/wavesurfer.js/discussions/2932
You can extract a portion using .slice() on the array.
Something like
const audioData = wavesurfer.getDecodedData()
const channel = audioData.getChannelData(0)
const portion = channel.slice(5 * audioData.sampleRate, 40 * audioData.sampleRate)


DictionarySlim trim

Relates to https://github.com/dotnet/corefxlab/issues/2592
2 commits -
Remove Key/Value Enumerables to reduce instantiated size of type as discussed above
Remove Capacity to reduce unnecessarily publicness

Oh, let me add XML comments too

OK now also
Added XML docs (file temporarily included in the commit as I cannot find a way to consume $(OutputPath) in the project)
Removed Copy to (low value, extra size)

I think a key and value collection are still both needed just not the nested Enumerator struct. I think that's what @jkotas meant.

I think a key and value collection are still both needed just not the nested Enumerator struct. I think that's what @jkotas meant.

I'm missing something, if we still have ICollection<TKey> but no Enumerator struct what would it return from GetEnumerator<TKey> ?

yield return? Though that would create an iterator class. I guess we can just use a LINQ Select clause to replicate the Key and Value collections where needed.

Looks good to me.

I guess we can just use a LINQ Select clause to replicate the Key and Value collections where needed.

Yes, that's what I did in the tests. As with anything - it is always easier to add than remove API.

@safern is going to get the package signed and on NuGet in the next few days. After that is up @AnthonyLloyd are you interested in sending in the updated benchmark game submission? I think you deserve most of the credit.

@safern is going to get the package signed and on NuGet in the next few days. After that is up @AnthonyLloyd are you interested in sending in the updated benchmark game submission? I think you deserve most of the credit.

Yes sure, thanks you all. It may be a good idea to wait until the package has a few downloads. In the benchmarks game they want to see that it's not just a package put up for the benchmark only.

@anthonylloyd it already has 50K downloads :https://www.nuget.org/packages/Microsoft.Experimental.Collections/1.0.3-alpha


Do not allow removal of networks with attached tasks

added checks in control-api to prevent network with attached tasks from being removed.
Fixes #1692
But ideally this PR must go in alongside the fix for #440 as described in https://github.com/docker/swarmkit/issues/1692#issuecomment-256085823
Signed-off-by: Madhu Venugopal<EMAIL_ADDRESS>

ping @mrjana

Current coverage is 56.05% (diff: 36.36%)

Merging #1724 into master will increase coverage by 0.22%

@@             master      #1724   diff @@
==========================================
  Files            96         96
  Lines         14902      14913    +11
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           8321       8360    +39
+ Misses         5474       5445    -29
- Partials       1107       1108     +1

Powered by Codecov. Last update b693657...894d56c

https://github.com/docker/swarmkit/issues/1728 took care of the changes. closing it.


Remove Terraform from Dependabot Schedule

🗣 Description

Removes the terraform dependabot job from the schedule.

💭 Motivation and context

No terraform is in this repo, so this check is not required. @dav3r  asked me to remove it

🧪 Testing

Automated checks ran.

✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All future TODOs are captured in issues, which are referenced
in code comments.
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[x] Tests have been added and/or modified to cover the changes in this PR.
[x] All new and existing tests pass.

@dav3r Here's that pull request for the change you requested.


Integrating keystore to save password/keys

duplicated here: https://github.com/GaloyMoney/galoy-mobile/issues/848


No link between course section names and github chapter numbers

The chapter numbers here on github aren't in the course and the chapter names used in the course are not on the chapter numbers here , so only an expert could find there way to the content that needs changing.

OK. Maybe it does sort of match if you know how to count. But still.

The change that was made to the Java course -  Chapter Two (liking straight to the relevant code) is a good solution. Thanks.
I can't check the other chapters, but I'm assuming similar work was done there, and I'm closing this.


feat(sfc): migrate to floor_planner::V1

Motivation
Close #251
Overview
The method without_witness used inside V1

btw
ivc_of_poseidon/fold_1_step
                        time:   [17.921 s 18.000 s 18.099 s]
                        change: [-11.122% -9.8220% -8.4038%] (p = 0.00 < 0.10)
                        Performance has improved.

This is still a needed change, but it didn't work for increasing the number to 800+ of iterations within poseidon


Expose a flag to limit the number of batched tasks and enable Puffin by default

⚠ This PR is based on v1.4.0 and must not be used in production ⚠
The Docker Image CI tag is prototype-enable-puffin-by-default-1.
You can look at this README to understand how to use this feature.
TBD

Closed in favor of #4249


Integration with React Native

I can't setup raven with my React Native (0.26) project. I get the error:
Attempted to assign to readonly property.

It's here https://github.com/getsentry/raven-js/blob/3.0.4/src/raven.js#L738, when it attempt to redeclare properties in the window object. I'm running on iOS 9.3.2 with latest React Native.
I added this in my index.ios.js:
import Raven from 'raven-js';
require('raven-js/plugins/react-native')(Raven);
Raven.config('https://69b5de20ca684f63be2f96f95a055007@app.getsentry.com/80528').install();

See #586

It's been 3hours that I'm looking for a solution and I didn't find that... Thanks, it's working now!

No trouble at all, sir! There's nothin' better than a good deed on Monday ;)


Error when call https://vemid42929.pythonanywhere.com/api/v1/moonbix/play

Hi there, please publish the source code on https://vemid42929.pythonanywhere.com/api/v1/moonbix/play. We encountered an error due to the code on this.

Check my telegram channel


Fix typo in doc

Fixes #N/A
Description
How was this change tested?
Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

0 of 0   changed or added relevant lines in 0 files are covered.
16 unchanged lines in 4 files lost coverage.
Overall coverage increased (+0.2%) to 83.073%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/controllers.go
1
0.0%

pkg/test/environment.go
4
95.9%

pkg/operator/operator.go
4
9.2%

pkg/providers/instancetype/instancetype.go
7
95.63%

Totals

Change from base Build<PHONE_NUMBER>0:
0.2%

Covered Lines:
5595

Relevant Lines:
6735

💛  - Coveralls


Please support ESRI geometry for the Geometry Viewer

I manage both PostGIS databases and ESRI enterprise geodatabases on PostgreSQL for multiple projects using DBeaver.
While I can take a quick look at the geometry over the map using the Geometry Viewer, which is very nice, for PostGIS, that does not happen for ESRI enterprise geodatabases.
Although ESRI of course provides an extensive suite of products/tools/scripts to manage enterprise databases, SQL-based management tools such as DBeaver are still very convenient for the management tasks. That is one of the reasons for the fact that ESRI supports PostgreSQL, Oracle, SQL Server etc for enterprise solutions. So, I would be very grateful if the Geometry Viewer works on ESRI geometry.
Thank you for your consideration!
DBeaver Community 21.1.4

A workaround might be to cast to EWKT https://gis.stackexchange.com/questions/346647/convert-postgresql-geometry-to-esri-st-geometry


Feature Request: Folder Upload Report

[X ] I have checked that the CLI documentation and API documentation doesn't solve my issue

Description of the Issue
When I upload a folder structure via the folders:upload command there is no progress indicator on the progress but also no report about what was created in a deep structure. The only information being returned is the top level folder created e.g.
Type: folder
ID: '7XXXXXXXXX7'
Sequence ID: '0'
ETag: '0'
Name:
Created At: '2019-05-02T04:54:08-07:00'
Modified At: '2019-05-02T05:14:35-07:00'
Description: ''
Size: 0
Path Collection:
Total Count: 2
Entries:
....
Ideally I would be able to get a CSV/JSON report an everything that was created so that I can use the ID for further work
Versions Used
Box CLI: 2.x
Operating System: Mac
Steps to Reproduce
NA
Error Message, Including Stack Trace
NA

@jacquesvandermerwe This seems like a good feature; I've added it to our backlog!


Feature flag in prod off for offences from Ap and Delius

closing this as the feature flags have now been removed


Rustup

@bors r+

:pushpin: Commit a0f650619d653ade1108afe0c4b98306c4950d5e has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit a0f650619d653ade1108afe0c4b98306c4950d5e with merge 15e7b5a7c314ba7319dba0fb6524a7eefe4a9de4...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 15e7b5a7c314ba7319dba0fb6524a7eefe4a9de4 to master...


[azservicebus] Closing a session after it has idled out can take 30 seconds.

(We noticed this while troubleshooting a separate issue)
When a link is detached by the remotes service, because it was idle, it takes up to 30 seconds for us to actually close it locally. I haven't gotten a chance to dig in for root cause. Nothing appears to be broken afterwards - the client is still usable and new senders/receivers can be created.
Note that this doesn't happen if you force the service to detach you - for instance, updating the remote entities metadata via ARM.

Looking into this more the issue doesn't appear to be in go-amqp (or azservicebus). Here's some logging I added - this is basically what we see from the connection side, which eliminates a lot of code -it's just the frames being read and written on the TCP connection itself:
Our internal session object queues the session END frame
2024/01/12 18:40:18 ======================= BEGIN: CLOSING Session =========================
2024/01/12 18:40:18 =====> BEGIN: s.closeOnce.Do()
2024/01/12 18:40:18 =====> session.PerformEnd BEGIN: frame sent
2024/01/12 18:40:18 =====> session.PerformEnd END: frame sent

In this bit, the END frame is sent on the wire. Note there is no delay here:
2024/01/12 18:40:18 ====> Conn: sending frame on channel 0, frame: frames.Frame{Type:0x0, Channel:0x0, Body:(*frames.PerformEnd)(0xc000414008)}

After this nothing happens - there is no communication from the remote service until 30 seconds later, when we get the response to our END frame:
2024/01/12 18:40:44 =====> conn: frames.PerformEnd arrived for 0

As far as I can tell the 30 seconds is on the service-side - we didn't receive any other frames in the meantime.

(NOTE for service team)
To repro this I wrote a test where I create a Sender, send one message and then wait until 10.5 minutes pass, then attempt to close the sender. I pared down my logic so that the only thing that happens is that I attempt to close the session, which initiates the END frame being sent for that AMQP session.

CC: @karenychen, who has been interested in progress on this since this can artificially inflate send times on idle links.

Thank you for your feedback. We have opened an investigation task for this in our backlog, and will update this issue when we have more information.

My client is facing this issue and has a temporary workaround of sending/receiving a dummy message every 60 seconds. I hope this issue gets resolved soon!

The issue is affecting my client as well, but they are using a temporary solution of sending and receiving a dummy message every few minutes. I look forward to a resolution soon!

@richardpark-msft "When a link is detached by the remotes service, because it was idle, it takes up to 30 seconds for us to actually close it locally". What is it there? I am assuming it is not the link, but the AMQP session. Is that right? I think what is meant by "it" determines what to investigate.

@richardpark-msft "When a link is detached by the remotes service, because it was idle, it takes up to 30 seconds for us to actually close it locally". What is it there? I am assuming it is not the link, but the AMQP session. Is that right? I think what is meant by "it" determines what to investigate.

Ah, that is confusing. You are correct, it's the AMQP session. The link closes right away.

Another question. Does it happen every time a link is closed for idle time? or only sometimes?

I had a test that could cause it every time if the link idled out, but not if I forced the detach (for instance, by updating the queue using ARM).

We dug deeper! The main fix is in the go-amqp repo go-amqp, PR#320. It was a combination of a few factors:

The body of the frame was smaller than 8 bytes (the session end frame is small)
No other packets arrive from the service.

In this case the session end body is small (7 bytes) and the service unblocked us by sending an empty frame 26 seconds later, leading to the behavior we see here.
I've got my PR merged in go-amqp, and am getting the SB PR together to incorporate it.

Barring any problems, release will be out tomorrow!

This fix has been released. There are two AMQP-based packages (azeventhubs and azservicebus):

azservicebus v1.6.1
azeventhubs v1.0.4


Datasets versions issue

Unlike transformers and other libs tags, datasets tags do not start with prefix v: 2.1.0 vs v2.1.0.
Previously, this caused issue where Source links broken https://github.com/huggingface/datasets/issues/3939, which was solved by https://github.com/huggingface/doc-builder/pull/146
However, on moon-landing we expect the version part of url to start with prefix v here, which caused this bug today
manual fix.
So there are 2 potential solutions, and I'd like to hear your thoughts:

Make datasets tags start with prefix v (for me, it would be the easier solution I favour)
Handle this problem on moon-landing & doc-builder (which i'd rather not favour 😊)

cc: @lhoestq @albertvillanova @sgugger

Hi ! In datastes some very important files are checked from github, and use specifically URLs based on the version without a v.
For example in datasets 2.0.0, the squad dataset script is fetched from https://raw.githubusercontent.com/huggingface/datasets/2.0.0/datasets/squad/squad.py

Hi ! In datastes some very important files are checked from github, and use specifically URLs based on the version without a v.

ooh I see, thus, I'll go with option 2 then

we could maybe push tags 2.1.0 and v2.1.0, always pointing to the same commit? (that way we have long term consistency for all HF libraries)

As a user I would find it weird to find duplicate tags on github, but maybe it's not a big deal

Note that you can find the prefix (default "v") in the _config.py file of the doc source folder, so you can push that info anywhere that might be useful for moon-landing. Here it is extracted for the build command for instance.

(just linking to the variable in question: _config.py)

let's see what the PR to support this looks like in moon-landing and then let's decide what we do =)

(BTW for the sake of consistency, which lack thereof very often leads at some point in time to a weird bug biting us in the behind, from now on let's try to enforce maximum consistency between all HF open source libraries!)

(Ok, after looking into other issues i realize this will probably be handle in doc-builder side... no worries at all then)


More preset automation & usability improvements

Description
This PR adds a handful of usability improvements:

allows the query template fields in the ML search request processors to be automatically populated
adds random name generation for index creation to prevent the easy case of name clashing when creating multiple workflows
sets default values for the select dropdowns (automatic population of the input maps when using a model with an interface)

Demo video showing that when all quick-config fields are filled out, and when using a model with an interface, ingest & search can be fully working by only configuring:
1/ passing in sample documents to ingest, and
2/ the query and input map for the search request processor (this may further be automated in the near future)
screen-capture (7).webm
Issues Resolved
N/A
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Looks good to me.


Add benchmarks to repo

I didn't find benchmarks in repository. What do you think on adding them here? It would be easier for new contributors to run them.

Hi @jastkand,
Thanks for the suggestions, but I want to keep the repo as small as possible.
I've specified which tool I used to perform the benchmarks and the results, that should be enough for someone that wants to perform benchmarks locally.
Otherwise we'll need to include a minimal Rails application to perform the benchmarks since has_scope only works with Rails.
Regards,
Ezequiel


Move PDC client to upstream repo

JIRA: PDC-949

+1

+1

Looks good to me. Please squash before merging.
We should also look if the monkey patch is still needed. It looks like the infinite recursion should be fixed upstream. But it is not part of this issue.

I will squash them after reviewing by team.

@lubomir, I am waiting for the testing result of 0.6.0 scratch build before making the official one. Even already had a new release branch in my local, when with make rpm, get_upstream.sh will clone latest code from upstream repo.
Could we stop merging any new change before release out 0.6.0? Otherwise it will involve in new changes which are not in the scope of this release.


Avoid using client-go master

Switching to v4.0.0 would makes things a bit more stable rather then using master. This release includes Kubernetes 1.7.

While I agree it would be better to use a tagged release, please keep in mind that things are "stable" in the sense that everyone installs the exact same commit of each dependency, the one that is specified in the Gopkg.lock.
I tried to specify a version, but gave up since it wasn't working, and went with master instead. This might be because 4.0.0 is still in beta.

4.0.0 was released, which should make fixing this easier.


Enable dotnet PGO and use final 6.0 image

Enable profile-guided optimization.
On my machine: 52650 before, 61255 after

Sounds good, thank you @JamesNK !


Modding an exe

Is it possible to mod an exe to load changed values automatically?
I'm good at coding but not good at exe modding.
Or is it not possible?

I don't know, maybe? But why? It's not how you do that kind of thing. It's easier to write a program which will work externally modifying game memory or an dll which will work internally. Not gonna mention that game executable is 500MB+, while your exe/dll will be <1MB, so it's much easier to share it.

What would be the best course of action, inject a DLL?

Some perhaps may argue, but yes, I think dll approach is slightly better. The only problem may be the language and the fact that you would also need an injector for it, but in exchange the only limitation what you can do and what not is your skill, time and imagination.


[REQUEST] Support for "Ngenic Track" product wireless energy meter reader

Please consider adding support for their new "Ngenic Track" product (a wireless energy meter reader)
https://ngenic.se/track/
Ngenic Track sensor connects to the same gateway plus uses the same API and app.
As Ngenic is a cloud based service so it includes data history of your energy usage as long as had it.

@sfalkman Swedish: Alla kunder har fått mail med 10% rabattkod "tracktack" (t.o.m. 31 dec 2019).

We're discussing Track support over here: https://github.com/sfalkman/ngenic-hass-platform/issues/1
You're welcome to help out with the debugging if you got a track :)

Cool, thanks! I have not yet bought/ordered one yet though but I am considering it still


Feat: use peer-dependencies to handle dependency to three.js

As described in #613, this replaces the previous method to handle the dependency to three.js with using peerDepdencies.
Tested in a typescript-project (vite) and in html via UMD and ESM.

Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[x] Make sure to open a GitHub issue as a bug/feature request before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[x] Ensure the tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Fixes #613 🦕

@usefulthink Looks awesome! Should we bump major version for this one?

I think semantic release will do that automatically, yes. I'll try to get a few more things done before we merge, so we don't end up with multiple major-releases.


docker container killed

I get this docker log

2016-02-19 20:30:00.516 [http-nio-8080-exec-3] INFO *******
Killed

and no other error log,where is wrong

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
For more information about reporting issues, see CONTRIBUTING.md.
You don't have to include this information if this is a feature request
(This is an automated, informational response)

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

@xssxyby  when you open bugs, please follow above info to help deveopers know that.
like docker info  and system info uname -a
also you couble enable debug level logs like docker daemon -D   which can give you good info.

I'm closing this issue, because there not a lot for us to work on without additional information, but happy to reopen if more information is added

Ah,I get these info.
uname -a

Linux 10-4-20-127 3.13.0-55-generic #94-Ubuntu SMP Thu Jun 18 00:27:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

dcoker verion

Client version: 1.7.0
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 0baf609
OS/Arch (client): linux/amd64
Server version: 1.7.0
Server API version: 1.19
Go version (server): go1.4.2
Git commit (server): 0baf609
OS/Arch (server): linux/amd64
and my docker info is

Containers: 109
Images: 609
Storage Driver: aufs
Root Dir: /data/docker_home/docker/aufs
Backing Filesystem: extfs
Dirs: 838
Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-55-generic
Operating System: Ubuntu 14.04 LTS
CPUs: 4
Total Memory: 7.798 GiB
Name: 10-4-20-127
ID: XSOY:UQIM:UTGY:OQGZ:NEB5:K242:VIVW:PERZ:ZN3W:H4XL:JRAE:FTJG
WARNING: No swap limit support

docker ps -a | grep mgmt

3c52da913bbc        boot_assetmgmt                                                     "/bin/sh -c 'java -j   21 hours ago        Exited (137) 14 hours ago                                       boot_assetmgmt_1
and my docker logs is

docker logs 3c52da913bbc

2016-02-20 21:29:40.953 [main] INFO  org.apache.coyote.http11.Http11NioProtocol - Initializing ProtocolHandler ["http-nio-8080"]
2016-02-20 21:29:40.963 [main] INFO  org.apache.coyote.http11.Http11NioProtocol - Starting ProtocolHandler ["http-nio-8080"]
2016-02-20 21:29:40.973 [main] INFO  org.apache.tomcat.util.net.NioSelectorPool - Using a shared selector for servlet write/read
2016-02-20 21:29:41.111 [main] INFO  o.s.b.c.e.tomcat.TomcatEmbeddedServletContainer - Tomcat started on port(s): 8080 (http)
2016-02-20 21:29:41.125 [main] INFO  com.creditcloud.assetmgmt.Application - Started Application in 208.133 seconds (JVM running for 222.285)
2016-02-20 21:29:41.125 [main] INFO  com.creditcloud.assetmgmt.Application -

         Server Started           *

2016-02-20 21:30:01.063 [http-nio-8080-exec-1] INFO  o.a.c.core.ContainerBase.[Tomcat].[localhost].[/] - Initializing Spring FrameworkServlet 'dispatcherServlet'
2016-02-20 21:30:01.064 [http-nio-8080-exec-1] INFO  org.springframework.web.servlet.DispatcherServlet - FrameworkServlet 'dispatcherServlet': initialization started
2016-02-20 21:30:01.090 [http-nio-8080-exec-1] INFO  org.springframework.web.servlet.DispatcherServlet - FrameworkServlet 'dispatcherServlet': initialization completed in 25 ms
Killed

it seems you container internal issue. Did you try other container like hello-world or busybox. is it OK?
And for your container case above, please also show output of docker server logs when such container started


Ignore locally smtp tests

Reference Issue

What does this implement/fix? Explain your changes.
It adds the decorator to the tests which use the connection (need to send e-mail etc) - those use to fail locally
Any other comments?

Hello @maikia! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file conftest.py:

Line 31:54: W291 trailing whitespace


[Testing] Using Etcd KvStore in testing GreptimeDB cluster in github action

What type of enhancement is this?
Other
What does the enhancement do?
Currently we are using MemStore in testing GreptimeDB cluster. It's best we can test against real Etcd.
However, setup a clean Etcd server in developer's environment is tedious everytime we do it when we run tests locally. Why not do it in github action?
Implementation challenges
Install a real Etcd server in github action is easy. The hard part is how the testing codes aware that they should run against an Etcd KvStore. Luckily, this can be done by action yaml's env. An example can be found at object_store_test.rs. Like this:

Adds ETCD_ADDR: "<IP_ADDRESS>:2379" in the test steps in develop.yml;
In GreptimeDbCluster,

  let kv_store = if let Ok(etcd_addr) = env::var(ETCD_ADDR) {
    EtcdStore::with_endpoints(etcd_addr).unwrap()
  } else {
    Arc::new(MemStore::default())
  }

Clean the data in Etcd, so we can get an clean start for next test case. It can be done when dropping GreptimeDbCluster.

The main challenge is that the tests are run in parallel. Consider wrapping the EtcdStore with a unique prefix for each test.

It seems that after https://github.com/GreptimeTeam/greptimedb/pull/2448 test-integration doesn't run anymore.  Or I omit somewhere we do the test.

@tisonkun It seems the tests-integration does run, see a recent github ci screenshot:

https://github.com/GreptimeTeam/greptimedb/actions/runs/6812357466/job/18524527569

@MichaelScofield Thank you! Perhaps we can improve the CI job/step name. I'll try to do it if I can work a solution for this issue alongside. Or if anyone would like to improve it alone.

@tisonkun feel free to improve the step name to a more appropriate one!


test: port most SILOptimizer tests for Windows

This adjusts the SILOptimizer test suite to work on Windows.  The
remaining SILOptimizer test failure is a memory issue in the standard
library.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test


Finalize and confirm naming convention for AstraDBOps, AstraDB, AstraDBCollection

Closing this issue as this has been discussed on slack and merged in for a while.


Convert Fingerprint Sample's Dialog to Kotlin.

Converted part of Dialog in #25

Finished to convert in #26


project can't be moved to another server

one version such as release1.8 is built successful and startall.sh is ran successful.
but cp this build to another server, and execute startall.sh, error appears:
such as:
2015/04/13 18:04:00 router.go:615: [fatal] zk: could not connect to a server
2015/04/13 18:04:58 main.go:98: [info] dump file path: /home/ochadoop/app/codis/codis/bin
2015/04/13 18:04:58 main.go:106: [info] running on  <IP_ADDRESS>:19000
2015/04/13 18:04:58 helper.go:312: [info] &{proxyId:proxy_1 productName:test zkAddr:ochadoop94:2181 f: netTimeout:5 proto:tcp}
2015/04/13 18:04:58 router.go:628: [info] start with configuration: &{proxyId:proxy_1 productName:test zkAddr:ochadoop94:2181 f: netTimeout:5 proto:tcp}
2015/04/13 18:04:58 router.go:652: [info] proxy_info:{Id:proxy_1 Addr:ochadoop94:19000 LastEvent: LastEventTs:0 State:offline Description: DebugVarAddr:ochadoop94:11000}
2015/04/13 18:04:58 router.go:600: [warning] proxy_1 wait to be online
2015/04/13 18:04:59 router.go:348: [info] ctrl-c or SIGTERM found, mark offline server
2015/04/13 18:05:01 router.go:437: [fatal] suicide {Id:proxy_1 Addr:ochadoop94:19000 LastEvent: LastEventTs:0 State:offline Description: DebugVarAddr:ochadoop94:11000}
2015/04/13 18:06:09 main.go:98: [info] dump file path: /home/ochadoop/app/codis/codis/bin
2015/04/13 18:06:09 main.go:106: [info] running on  <IP_ADDRESS>:19000
2015/04/13 18:06:09 helper.go:312: [info] &{pro
what i want to know is that how can i got the status and debug .
if i cp one version to another server, which should be redo or reconfigurations?

There is a deploy.tar in codis directory.
Using that tar to deploy.


[WIP] MXNet Extensions enhancements

Description
Enhancements to MXNet Extensions (subgraph property, custom ops, custom graph passes). Addresses a few points from #17236. More description on the way!
Features

Enhancement to supportedOps to allow for graph coloring (specifying which subgraph an op should be partitioned into)
Enhancement for partitioners to use Selector class instead of supportedOps
Added a new example for custom subgraph op using selector class
Clean up lib_api.h and library loading in c_api.cc
Added option to quiet library loading printing ops, partitioners, passes found in library
Add support for custom graph passes, and docs/README
Add a new example for custom pass libraries with 2 example passes
Added support for allocating new args/aux within the pass, or replacing existing args/aux
Add new custom pass lib to Makefile/CMakeLists.txt
Add building sparse custom op libraries to Makefile/CMakeLists.txt
Add compiling custom libs with lowest supported C++11, building with C++17 for testing with MXNet

SupportedOps Enhancements for graph coloring
In the custom partitioner API, custom library writers could implement the SupportedOps API to specify which ops to include in a subgraph by setting True/False for each node ID in the graph. This PR adds support for writers to identify which specific subgraph to include a node into by specifying a subgraph ID integer for each node, or -1 to indicate that a node can go into any subgraph.
Selector class for subgraph creation
In the custom partitioner API, custom library writers could implement the SupportedOps API to specify which ops to include in a subgraph. But some custom partitioners may want more control. This PR, adds support for the internal MXNet subgraph property SubgraphSelector class to be implemented in a custom library. Custom library writers can choose to implement SupportedOps API or CustomOpSelector class for their partitioner.
Custom Graph Passes
This PR adds the ability to register a custom graph pass in a library. Working backwards from the custom library writer, the Pass API is implemented with the following interface:
MXReturnValue myPass(const std::string& in_graph, const std::string** out_graph,
                     const std::unordered_map<std::string, std::string>& options,
                     const std::unordered_map<std::string, MXTensor>& args,
                     const std::unordered_map<std::string, MXTensor>& aux,
                     const PassResource& res)

The model graph is passed as a JSON string, and users provide a new JSON string for the modified graph. Options specified by the MXNet user at the Python level are passed in the options map. If the MXNet user provided the args/aux at the Python level they are provided to the pass in the args/aux arguments. The PassResource class res exposes two functions: alloc_arg and alloc_aux that allow the custom library writer to allocate NDArrays for new or replacement args/aux within the custom pass. Custom passes are registered in the library with this syntax:
REGISTER_PASS(myPassName)
.setBody(myPassFunc);

As custom passes are found in the library during loading, a lambda function is registered:
auto pass_lambda = [=] (nnvm::Graph&& g) {
    ...
    CHECK(callGraphPass(...));
    ...
    return out_graph;
};

nnvm::PassFunctionReg& pass = dmlc::Registry<nnvm::PassFunctionReg>::Get()->__REGISTER__(myPassName);
pass.set_body(pass_lambda);
pass.set_change_graph(true);

From the MXNet front-end, users call custom passes using the same optimize_for API. The backend name argument to the optimize_for API is attempted to be looked up in registered subgraph backends first, and if missing is attempted to be looked up in registered graph passes:
if (mxnet::op::SubgraphBackendRegistry::Get()->backend_map_.count(backend_name) > 0) {
    // use subgraph backend
    ...
} else if (dmlc::Registry<nnvm::PassFunctionReg>::Find(backend_name) != nullptr) {
    // use graph pass
    ...
    g = ApplyPass(std::move(g), backend_name);
    ...
}

Compilation
The lib_api.h was designed to be as generic as possible to allow users to compile their custom library with any version of C++ (C++11 or higher) and GLIBC to fit the needs of their application. This does not have to correspond to the version of C++ or GLIBC used to compile MXNet. To test this, we will compile with C++11 to check for compiler errors, but will also compile and test with C++17 to match was MXNet is using.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

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

Comments

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

@mxnet-bot run ci [sanity]

Jenkins CI successfully triggered : [sanity]

@mxnet-bot run ci [sanity]

@mxnet-bot run ci [sanity]

@mxnet-bot run ci [sanity]

also please lib_api update version to 10

also please lib_api update version to 10

changed to version 7

Synced offline with @samskalicky and @rondogency - they are ok with doing the last changes proposed by @rondogency in another PR targeting master specifically, so this PR is ready to merge.

@ptrendx let's not merge commits named "[WIP]" to master. You can edit the name prior to merge

Oops, you are right, sorry, I missed that.

@ptrendx let's not merge commits named "[WIP]" to master. You can edit the name prior to merge

We didnt want to rerun the whole CI. did we fix the problem where renaming the PR reruns CI @leezu ?

< We didnt want to rerun the whole CI. did we fix the problem where renaming the PR reruns CI @leezu ?
@samskalicky when merging the commit, Github allows to edit the commit message. So the commit message can be different from the PR title. Indeed we can't edit the PR title without retriggering the CI as of now (cc @ChaiBapchya)


[BUG] Invalid get index 'lb' (on base: 'Dictionary')

Calling plot on chart after it was added to the scene tree (so after ready, for example to plot some new functions) results in a crash. The error message reads:
Invalid get index 'lb' (on base: 'Dictionary')
After some experimenting, the error is most likely caused by the FunctionPlotter's x_domain and y_domain values not being initialized properly yet. This means, that the _draw function is called on the function_plotters, before it is called on chart, since this would set the domains, right? Adding the following to the end of the load_functions method of chart seems to solve the issue, but causes some other unexpected side effects:
var x_domain: Dictionary = calculate_domain(x)
var y_domain: Dictionary = calculate_domain(y)
for function_plotter in functions_box.get_children():
	function_plotter.update_values(x_domain, y_domain)

If plot is called repeatedly, older function_plotter nodes should also be removed from the scene tree, if not already doing so.

By the way:

This means, that the _draw function is called on the function_plotters, before it is called on chart, since this would set the domains, right?

the _draw() function is called first on the Chart object, and then on all the FunctionPlotters nodes. In this way the Chart sets the domain for the grid, and then functions are plotted.

For example, if I change the script example/bar_chart/Control.gd to
extends Control

@onready var chart: Chart = $VBoxContainer/Chart

# This Chart will plot 3 different functions
var f1: Function

func _ready():
        hide()
	set_process(false)

func _unhandled_input(event):
	if event.is_action_pressed("ui_accept"):
		show()
		plot()

func plot():
	# Let's create our @x values
	var x: Array = ["Day 1", "Day 2", "Day 3", "Day 4"]

	# And our y values. It can be an n-size array of arrays.
	# NOTE: `x.size() == y.size()` or `x.size() == y[n].size()`
	var y: Array = [20, 10, 50, 30]

	# Let's customize the chart properties, which specify how the chart
	# should look, plus some additional elements like labels, the scale, etc...
	var cp: ChartProperties = ChartProperties.new()
	cp.colors.frame = Color("#161a1d")
	cp.colors.background = Color.TRANSPARENT
	cp.colors.grid = Color("#283442")
	cp.colors.ticks = Color("#283442")
	cp.colors.text = Color.WHITE_SMOKE
	cp.y_scale = 10
	cp.draw_origin = true
	cp.draw_bounding_box = false
	cp.draw_vertical_grid = false
	cp.interactive = true # false by default, it allows the chart to create a tooltip to show point values
	# and interecept clicks on the plot

	# Let's add values to our functions
	f1 = Function.new(
		x, y, "User", # This will create a function with x and y values taken by the Arrays
						# we have created previously. This function will also be named "Pressure"
						# as it contains 'pressure' values.
						# If set, the name of a function will be used both in the Legend
						# (if enabled thourgh ChartProperties) and on the Tooltip (if enabled).
		{
			type = Function.Type.BAR,
			bar_size = 5
		}
	)

	# Now let's plot our data
	chart.plot([f1], cp)

	# Uncommenting this line will show how real time data plotting works
	set_process(false)

var new_val: float = 4.5

func _process(delta: float):
	# This function updates the values of a function and then updates the plot
	new_val += 5

	# we can use the `Function.add_point(x, y)` method to update a function
	f1.add_point(new_val, cos(new_val) * 20)
	chart.queue_redraw() # This will force the Chart to be updated

func _on_CheckButton_pressed():
	set_process(not is_processing())

it will throw said error message after pressing return a second time.
I was trying to create a separate project for demonstration, but for some reason, the data_tooltip folder appears to be missing from containers now when installing Easy Chart 4.x from the Asset Library? Or am I just being very confused right now?

the _draw() function is called first on the Chart object, and then on all the FunctionPlotters nodes. In this way the Chart sets the domain for the grid, and then functions are plotted.

Yeah, I also assumed it would work that why. To be honest, I am not entirely sure why I receive that error and what is happening. But x_domain and y_domain of function plotters not being set correctly seems to be involved in some way.

For example, if I change the script example/bar_chart/Control.gd to
extends Control

@onready var chart: Chart = $VBoxContainer/Chart

# This Chart will plot 3 different functions
var f1: Function

func _ready():
        hide()
	set_process(false)

func _unhandled_input(event):
	if event.is_action_pressed("ui_accept"):
		show()
		plot()

func plot():
	# Let's create our @x values
	var x: Array = ["Day 1", "Day 2", "Day 3", "Day 4"]

	# And our y values. It can be an n-size array of arrays.
	# NOTE: `x.size() == y.size()` or `x.size() == y[n].size()`
	var y: Array = [20, 10, 50, 30]

	# Let's customize the chart properties, which specify how the chart
	# should look, plus some additional elements like labels, the scale, etc...
	var cp: ChartProperties = ChartProperties.new()
	cp.colors.frame = Color("#161a1d")
	cp.colors.background = Color.TRANSPARENT
	cp.colors.grid = Color("#283442")
	cp.colors.ticks = Color("#283442")
	cp.colors.text = Color.WHITE_SMOKE
	cp.y_scale = 10
	cp.draw_origin = true
	cp.draw_bounding_box = false
	cp.draw_vertical_grid = false
	cp.interactive = true # false by default, it allows the chart to create a tooltip to show point values
	# and interecept clicks on the plot

	# Let's add values to our functions
	f1 = Function.new(
		x, y, "User", # This will create a function with x and y values taken by the Arrays
						# we have created previously. This function will also be named "Pressure"
						# as it contains 'pressure' values.
						# If set, the name of a function will be used both in the Legend
						# (if enabled thourgh ChartProperties) and on the Tooltip (if enabled).
		{
			type = Function.Type.BAR,
			bar_size = 5
		}
	)

	# Now let's plot our data
	chart.plot([f1], cp)

	# Uncommenting this line will show how real time data plotting works
	set_process(false)

var new_val: float = 4.5

func _process(delta: float):
	# This function updates the values of a function and then updates the plot
	new_val += 5

	# we can use the `Function.add_point(x, y)` method to update a function
	f1.add_point(new_val, cos(new_val) * 20)
	chart.queue_redraw() # This will force the Chart to be updated

func _on_CheckButton_pressed():
	set_process(not is_processing())

it will throw said error message after pressing return a second time.
I was trying to create a separate project for demonstration, but for some reason, the data_tooltip folder appears to be missing from containers now when installing Easy Chart 4.x from the Asset Library? Or am I just being very confused right now?

Could you try testing over the main branch please? Eventually the version you are using (I suppose from the AssetLib) had some bugs in it.

Hi
I'm having very similar issues with the main branch code.
The error disappears when calling queue_redraw() before plot.
	#chart.queue_redraw() # this fixes the crash
	var x_axis = [1, 2, 3];
	var y_axis = [1, 2, 3];
	var F = Function.new(x_axis, y_axis, "Eh", {color = Color.WEB_GREEN, type = Function.Type.LINE })
	chart.plot([F])

This code is called on a button click.

If plot is called repeatedly, older function_plotter nodes should also be removed from the scene tree, if not already doing so.

There is also an error happening here. When switching between a plot with a single function and one with 2 functions, I receive a graph with 3 functions when trying to display 2. The single plot works correctly.
I will open a separate Issue for this though, after investigating the issue myself a bit more.
Kim

Closing due to inactivity. Feel free to reopen.


Update roslyn version

This bump was already done as part of https://github.com/OmniSharp/omnisharp-roslyn/pull/1563 - however it is still not merged. can we merge that one instead?
i can also revise that PR to 3.3.0-beta2-19376-02

as mentioned, i have updated #1563 to 3.3.0-beta2-19376-02 and fixed there all the failing tests caused by this update

@filipw I merged your changes and added the changelog accordingly


Failed to deserialize the account

The error: Error: 3003: Failed to deserialize the account.
I have created an account that has a customized data field, enum for more precise.
#[repr(u8)]
#[derive(AnchorSerialize, AnchorDeserialize, Clone, Copy, Debug, PartialEq)]
pub enum CertState {
  Uninitialized,
  Active,
  PrintOnly,
  BurnOnly,
  Paused,
}

#[account]
pub struct Cert {
  pub printer: Pubkey,
  pub secure_token: Pubkey,
  pub numerator_rate: u64,
  pub denominator_rate: u64,
  pub state: CertState,
}

Then, make a call to init the account
pub fn exec(
  ctx: Context<InitializeCert>,
  numerator_rate: u64,
  denominator_rate: u64,
) -> ProgramResult {
  let cert = &mut ctx.accounts.cert;
  cert.printer = ctx.accounts.printer.key();
  cert.secure_token = ctx.accounts.secure_token.key();
  cert.numerator_rate = numerator_rate;
  cert.denominator_rate = denominator_rate;
  cert.state = CertState::Active;
  Ok(())
}

Can you show struct InitializeCert?
Please start to use discord.

I realize that I have configed wrong the Cert size that caused the issue. I will close this one due to personal misconfig.


Adding radio button component

What
Implement radio styling with basic documentation. Additional variants to be added in as and when required

How to review

Sense check
SPAG checks for the documentation copy

Who can review
Anyone

I've suggested a couple of changes. I got a bit confused with the description bit so do let me know if what I said makes no sense.
Should it be radio component rather than radios? Perhaps you could replace it with "radio button" if that makes more sense in some of the case

I had the same debate over radio or radios. I went with radios in the end as although it is possible to have a radio group with a single radio, this would have a detrimental affect on the end user. Also, I followed a similar pattern in the design system and GDS. I would avoid using "radio button" as although it is a common term, radios are an  <input> not a <buttton>. So, I think radios is an appropriate component name.

I'm not sure if this is coming later - but should there be an option to clear the selected radio button? Speaking from experience of frustrating radio buttons 😁

The cat is still in box (or not) on this one. Product need to confirm whether they want it as there's lots of conflicting research on being able to reset a form.


[mamba] fix: backport asprintf compilation error fix

@cbix Please fix the aarch64 CI builder and then merge this.


Remove is_a link between 'defense response to other organism' and 'immune response'

Read all comments on this topic in #16298 before commenting. I think this is the immediate course of action agreed upon (in 2018!) on that ticket.
Immediate course of action:

Remove is_a link between 'defense response to other organism' and 'immune response'
Examine all descendants of DRtOO and determine if they should be placed under 'immune response' (or ideally a more precise term)

E.g. CRISPR-CAS - No

There is a lot more to talk about here, but I suggest limiting this issue to be the immediate action above. We have an issue about CRISPR-CAS #16423  -- the defense response hierarchy seems pretty problematic to me on multiple levels but let's talk about that elsewhere

I had added the relation between 'defense response to other organism' and 'immune response' here
https://github.com/geneontology/go-ontology/issues/18737#issuecomment-779706661 (but without explanation, probably during a discussion). Now removed.

We should discuss this on a multiorg call, also with @addiehl

See also my long comment to #16423


Used Loop after update when filtering the slides

Hello, I did a function to filter the contents of the swipper.
The Swipper gets up to date after using my function combined with the update method.
However, I would like to use the carousel loop option and it does not work properly.
If my loop option is enabled when i loading the page, the Swipper duplicates the content.
I use my filter to delete elements, however the old duplicate elements are still present in the DOM.
Suddenly the old content appears when I comming to the end of the Swipper
Can you help me?
Another post talk about this problem
https://stackoverflow.com/questions/35601972/idangerous-swiper-duplicates

My guess is that you are not calling update at correct time. Have you tried using observer: true instead of calling update manually?

I use the update methode when i launch my function and after updating the data.
  public filterChange(test) {
    this.SystemsItemsFiltered = this.SystemsItems.filter(function(val){
      return val.developer === test;
    });
    this.usefulSwiper.swiper.update();
    console.log('this.SystemsItemsFiltered', this.SystemsItemsFiltered); // Good value
  }

i have already try observer: true but i have the same result :(

If you don't call the update from timeout the data has not been updated to DOM yet. So you are basically calling the update before the change not after.

Thanks for you help.
i have try this with the same issue i dont understand :( ````javascript
setTimeout(() => {
console.log('coucou');
this.usefulSwiper.swiper.update(true);
},1000);

Then I am guessing its a limitation or bug of Swiper.

Okay,
Do you think i am on the right place for the developper see my message an add a fix?

Well no, you should report it to Swiper issues. But I suspect that dynamic slide changing might not be in the main interest of the Swiper developer, but who know. So you might still end up doing it manually.
If you end up doing it by application code, one thing to try could be to force reset of the Swiper instance when ever the slides changes (any wrapper configuration change should do that). So if Swipers shutdown will cleanup the duplicated slides then this "hack" could work rather easily.


Make the slug generator a service

refs #6243

:+1: Approach looks good, just need to work out why those tests are failing.

@kevinansfield Should be fixed now :smile:

Awesome, thanks! Nice to get rid of that old SlugGenerator object :smile:


proxychains auth issues

Hi, when connecting through proxychains, if i submit right creds, I get a authentication failure.  if i submit bogus creds, script hangs? any ideas?

Do you have any screenshot of the commands used?


How to handle error from callHandler

It appears that when the callHandler returns successfully from flutter either by
throw 'Some String error'
throw Exception('Failed')
Returning either of the above results it the callHandler reaching the then bloc vs the catch bloc. I am looking to execute a success vs error callback on the callHandler based on what is returned from the flutter side.
Is this possible already, or am I missing something here?
Current version I am working off of:
flutter_inappwebview: 5.4.4+3

Are there any updates or suggestions on this issue?


Find root cause of catkin build failing

We currently use catkin build --no-jobserver as a workaround.

The following error also occurs when you do build with --no-jobserver.
make[2]: *** No rule to make target make[2]: *** No rule to make target `/home/mcopejans/tangoscan_ws/devel/.private/tango_ros_messages/include/tango_ros_messages/SaveMapRequest.h', needed by `/home/mcopejans/tangoscan_ws/src/tango_ros/tango_ros_common/tango_ros_messages/include/tango_ros_messages/SaveMapRequest.h'.  Stop.

This was fixed in #191.


[Feature Request] Ranged page download

Why/User Benefit/User Problem
Instead of downloading the entire chapter, user can download a portion of gallery for offline viewing. This could help if users like only a certain portion of the chapter, or don't want to download the whole chapter. Especially useful for Ehentai galleries which can have more than 1k pages.
What/Requirements
Add a ranged page download feature, where user can download custom page (ie, pg 352-675 instead of 1-1000)

I decided to just use 8Muses/AllPornComic to download the chapter instead of using ongoing  Eh titles, so closing this 😏


Provide a way to iterate over sections

Would be cool to iterate over sections instead of manually retrieving sections.
Not sure if there is a way to do this already, but I am unable to access the @sections var of Parser publicly.

Closing this out in favor of #30


*: fix some typos

What is changed and how it works?

Issue Number: ref #5456.
What's Changed:

Fix some typos.

Check List
Tests

Unit test
Integration test

Release note
None.

/check-issue-triage-complete

@overvenus Could you please help leave a /merge?

/merge

/test

/test


Unchanged files with check annotations

So we added nilaway to our github actions flow a couple weeks back (which is great - it makes zero sense why this isn't in the language as fatal). https://github.com/autobrr/autobrr/blob/aa6ac6d4db6ed5a2ba5fd8e3f9bead46674b3e42/.github/workflows/golang-linter.yml#L26
However, on every single PR it reports these Unchanged files with check annotations lines as seemingly a way to punish external to GitHub linters. Other tools seem to be able to change the reporter to github-pr-check from the default to work around the added layer of annoyance, however I'm not seeing such a capability with nilaway presently.
Thoughts, direction, approach, etc appreciated.

Kind of sounds like there's nothing out of the box here and it's something that has to be built? I'm coming up short on finding something to parse the json format that this outputs.

Yes, this has to be built (either as a separate formatter within NilAway, or a custom post-process script on your end).
Running NilAway with -json flag will instruct it to output the results in JSON format, and then you can post-process the output JSON in any way you want :) tools like jq may be handy, or you can write python (or any other language) scripts to do a post process.


dependency injection in the subclass inherits from WebsocketHandler

Hi,
it is possible to inject dependencies in the websocket handler ?

Hi!
Sure, the handler is just another class, meaning you should be able to inject dependencies as usual in ASP.NET Core.
Please let us know if this doesn't work as intended :)
Radu M

I try to use the entityframework context as a dependency and it throws me the next exception:
System.InvalidOperationException: 'Cannot consume scoped service 'app.DataContext' from singleton 'app.WebSocketService'.'
My Startup.cs
public class Startup
{
    public Startup(IConfiguration configuration)
    {
        Configuration = configuration;
    }

    public IConfiguration Configuration { get; }

    public void ConfigureServices(IServiceCollection services)
    {
        services.AddMvc();
        services.AddCors(options => options.AddPolicy("AllowAllOrigins", builder => builder.AllowAnyOrigin()));
        services.AddOptions();

        services.AddSingleton<IConfiguration>(Configuration);
        services.AddDbContext<DataContext>(options => {
            options.UseSqlServer(Configuration.GetConnectionString("Test"));
        });

        services.AddWebSocketManager();
    }

    public void Configure(IApplicationBuilder app, IServiceProvider serviceProvider)
    {
        app.UseWebSockets();
        app.MapWebSocketManager("/service", serviceProvider.GetService<WebSocketService>());

        app.UseMvc();
        app.UseCors("AllowAllOrigins");
    }
}

My Subclass
public partial class WebSocketService : WebSocketHandler
{
    private readonly DataContext _context;

    public WebSocketService(WebSocketConnectionManager webSocketConnectionManager, DataContext context)
        : base(webSocketConnectionManager)
    {
        _context = context;
    }

    public override async Task OnConnected(WebSocket socket)
    {
        await base.OnConnected(socket);
    }

    public override async Task OnDisconnected(WebSocket socket)
    {
        await base.OnDisconnected(socket);
    }
}

Hi, did you solve this problem ?


Initial implementation of Keybindings

This PR brings Keybindings to Gitea! You can bind a shortcut to a element with the new keybinding-shortcut attribute. I also added some of GitHub's shortcuts as example.

Would suggest you use https://github.com/ccampbell/mousetrap to capture the key events. It has multiple benefits, for example it (by default) does not trigger keybinds while a <input> element is focused.

It looks like mousetrap is no longer maintained, but I can add a check for input elements into my own code

It's stable, it does really not need maintainance. But there's also https://github.com/jaywcjlove/hotkeys which is very similar.

I use now hotkeys-js. Each lib my need some changes or bugfixes at some point in the future, so it's better to use a maintained one.
For anyone who wonders why I don't use the hotkeys() function: The Keybindings should be defined by a HTML attribute, to keep it as easy as possible for most things. Of course, this could also be done with the hotkeys() function, but this need a lot of binding and unbinding if something chnaged. This could cause problems, if somebody else want to use this lib in JavaScript code in the future. So I decided to use a keydown event combined with hotkeys.getPressedKeyString(). hotkeys.getPressedKeyString() has all benefits of the lib. If the User inputs texts in some Input field, it just returns a empty array.

Using hotkeys() would make the code clearer, but it'd likely need detection when the target element is removed from the DOM, which is tricky. Though I do wonder if we could just gracefully ignore keybindings targeting non-existant elements, should definitely be possible.

It may be necessary in the future to have some bindings work inside input,textarea and select. Ideally by defining an additional attribute on the target element. The method to allow these via hotkeys.filter seems very clumsy and unsuitable to me. So if we want that, I think we may be better off removing the dependency actually.

So if we want that, I think we may be better off removing the dependency actually.

So I should return back to the old code and add a check if currently some input filed in focus?

This is currently death because of I got no answer how to process. If there is interest in this, I can open anew PR, which would be easier than solving the conflicts.

@JakobDev I'll close this, and if you want you can open an issue for this feature idea not to be forgotten

On topic, I recently found https://github.com/RobertWHurst/Keystrokes which seems like a modern and suitable keybinding library.

If there is interest in this (it don't looks like that) I can open a new PR. But keep in mind: If we use a library, we need to stick with it, as this library has some custom formats that may not be supported by another one.

I think it's good that the library distinguises key sequences (>) from combos (+). Here is something to play with:
https://codesandbox.io/s/shy-cookies-zvrgcc?file=/src/index.js
You notice it will capture events when focus is inside the <input> too, so this is something we need to check via document.activeElement.
I'm generally favorable of having some keybindings, but really the only one I personally use on GitHub is the Y shortcut on file view. Documenting these is also a challenge.

Another possible contender: https://github.com/jamiebuilds/tinykeys. It does seem promising at least in the size department. I will soon attempt using one of these libs in another application of mine and then i should be able to give a recommendation, so maybe wait on that.


Restore smart contracts setup in the devnet

After first Holesky launch we should restore on the devnet the deployment of smart contracts and have validators and operators signed up in the devnet. This is needed to have a devnet be as close as possible to a production environment.

Related https://github.com/chainbound/ethereum-package/issues/21


WIP Pipelines and dockerfiles

closing in favor of https://github.com/BCWResearch/bcw_zk_evm/pull/6


Playground examples don't work

Dear developers,
I just want to communicate that the playground don't work.
Best,
Matteo

Fixed :) the playground is working again: https://st-pydantic.streamlit.app/

Thank you!
But... I'm sorry... if I select Data Validation it still doesn't work.
Thank you very much for your work!
Best,
Matteo
Il giorno dom 18 ago 2024 alle ore 16:48 Lukas Masuch <
@.***> ha scritto:

Fixed :) the playground is working again:
https://st-pydantic.streamlit.app/
—
Reply to this email directly, view it on GitHub
https://github.com/lukasmasuch/streamlit-pydantic/issues/58#issuecomment-2295288229,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJHMGUZXLM3GO6FA3EPYVSTZSCX2DAVCNFSM6AAAAABHGQWC7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGI4DQMRSHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks for checking. I will fix it today :)

Fixed it 👍


How to edit node in graph?

Hi
I can get the all the nodes in graph.
But they can't be updated.
I have to drop them first, and add them again after update.
Are there any other ways to do that?
Thanks

Mrs. Lee, you are under arrest


支持vue3么？

支持vue3么？

I'm working on it, a vue3 compatible version will be released today or tomorrow

The component code has been greatly improved,
I have released version 1.5.1 for Vue2 and version 2.0.0 for Vue3
Please use "npm i -s vue-drag-resize@next" for use in Vue3
The vue3 branch has completely rewritten the demo using the composition API. For examples of how to use it, go there


Setting up the micropcf development env, git clone failed

Following the guide micropcf/DEVELOP.md, git clone operation fails with error message

Submodule 'assets/rabbit-example-app' (https://github.com/pivotal-cf/rabbit-example-app.git) registered for path 'assets/rabbit-example-app'
Cloning into 'assets/rabbit-example-app'...
remote: Counting objects: 115, done.
remote: Total 115 (delta 0), reused 0 (delta 0), pack-reused 115
Receiving objects: 100% (115/115), 1.90 MiB | 1.72 MiB/s, done.
Resolving deltas: 100% (43/43), done.
Checking connectivity... done.
Submodule path 'test/src/github.com/pivotal-cf/cf-rabbitmq-smoke-tests/assets/rabbit-example-app': checked out '55b12318c9fb9677e06e10255b84c1e3da13553f'
Failed to recurse into submodule path 'releases/cf-mysql-release'
Unable to checkout 'dc571470ca621d3e919e47fb9538277452b2b1ab' in submodule path 'test/src/github.com/mdelillo/cf-mysql-acceptance-tests'

Navigating directly to github.com/mdelillo/cf-mysql-acceptance-tests I can see the module but not sure why is it failing to checkout
Also noticed another error message towards the beginning, but this one doesn't interrupt the git clone operation

remote: Repository not found.
fatal: repository 'https://github.com/fraenkel/candiedyaml/' not found
Clone of 'https://github.com/fraenkel/candiedyaml' into submodule path 'src/github.com/fraenkel/candiedyaml' failed

Thanks

This should be fixed on master. Feel free to re-open if you're still having issues.
Thanks!
Stephen


ApplicationDeployer fails with InvalidOperationException in VS2017 tests

Attempting to migrate MusicStore to VS 2017. The E2E tests fail with this error:
Stack Trace:
   at System.Diagnostics.Process.EnsureState(State state)
   at System.Diagnostics.Process.get_HasExited()
   at Microsoft.AspNetCore.Server.IntegrationTesting.ApplicationDeployer.ShutDownIfAnyHostProcess(Process hostProcess)
   at Microsoft.AspNetCore.Server.IntegrationTesting.SelfHostDeployer.Dispose()
   at E2ETests.SmokeTests.<SmokeTestSuite>d__2.MoveNext() in C:\dev\Universe\MusicStore\test\E2ETests\SmokeTests.cs:line 208

Repro: https://github.com/aspnet/MusicStore/blob/fbd6cee23e4f8a31944ec6293316e3e19ea05ae7/test/E2ETests/SmokeTests.cs

cc @BrennanConroy  any ideas?

Found the issue. This error occurs when the process fails to start because the ProcessStartInfo was incorrect.


Fix ledger processor hash2 race condition

Resolves #598, resolves #602.
A block's dependency (previous or source) was being added to the ledger after the hash2 was calculated, which caused the assert to fail. This fixes the problem.

Note that in some cases your database is already corrupted, since it has hash -> 0 hash2 mappings. This happens because the assert only triggers in debug mode.

Also, now that I think about it, there's still a possible race condition with elections, where a block can be removed from the ledger. Fixing that will be much harder.

This change might be effective but it doesn't look like it's addressing the root cause of the race.

Yeah, that's evident in the problem with voting. I thought lmdb transactions would take care of this, but I guess not...
Basically, a block can be added to the ledger between when ledger_processor::send_block checks ledger.store.block_exists (transaction, block_a.hashables.previous), and when hash2_visitor::send_block checks !store.hash2_get (transaction, block_a.hashables.previous).is_zero() (I condensed the expression a bit).
This fixes the problem when a block is added to the ledger between those checks, however, if voting removes a block from the ledger between those checks, then there could be a problem. I think that could be a problem even before hash2. Hash2 only amplified the issue because it could happen with both adding blocks and removing blocks. Because of that, I'd propose merging this PR until a more comprehensive locking system can be created (assuming this PR fixes the segfaults that is).


display() - maps - renderer google raises "a bytes-like object is required, not 'str'" error in Python 3.x

PixieDust 1.0.8: Using a Python 3.x kernel in DSX, the pixiedust google maps renderer fails with a bytes-like object is required, not 'str'. The problemn is not observed if Python 2.x is used.
Steps to reproduce the behavior
Simple data frame containing 2 columns: STATE and count, e.g. ("FL",1)
display(df)

Choose Map as the chart type.
Put STATE into the Keys box.
Put count in the Values box.
Set Aggregation to COUNT.
Click OK.
From the Renderer list, choose google.
From the Display Mode list, choose region.
From the Region list, choose US.

more info: https://docs.python.org/release/3.0.1/whatsnew/3.0.html#text-vs-data-instead-of-unicode-vs-8-bit


Create key bindings menu

This both displays the options and is critical for accessibility.

Related to #214.

We should solve #275 first, #214 second and this third.


invite-user-modal: Clean up of template HTML attributes.

Updates:

Removes the "for" attribute on the Custom time label so that clicking on that label does not move the focus to the Invitation expires after select element above the custom time inputs.
Moves a number of the "name" attributes from the nested option elements to the select elements; see  MDN select element doc and MDN option element doc.
Removes the currently unused "custom_time_choice" class.
Reorders the attributes in the custom time input and select element so that they are a bit more readable.

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks for cleaning up this mess!


Use a non-mutable default headers argument

Summary
When invoking api_call(), the default value for headers is a mutable
object! If at any point during invocation, api_call mutates this
dictionary, it will affect the behavior of future calls to the method.
Thankfully, the current source does not modify headers, so this
adverse behavior does not happen.
However, it's a much safer pattern (and consistent with the rest of this
file) to use None as the default argument, and construct a new
dictionary as required.
See: https://docs.python-guide.org/writing/gotchas/#mutable-default-arguments
Requirements

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

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

Happy to add some tests here if desired - though this should represent no new functionality.

@DavidCain This is a great catch. Thank you for the contribution!


Defend against programs with infinite loops, excessive allocation, etc.

Visibility of all running launches and test suites.
Kill programs after a timeout.
Launch programs with high niceness.
Launch programs with small memory bounds.
Ensure Collabode remains responsive with infinite loop launches.
Ensure running launches are terminated when Collabode is terminated.
(Imported from Bitbucket #46 reported by maxg on 2011-06-02)

Client-side responsiveness during infinite loop requires stopping or limiting pad updates.
(maxg on 2011-09-19)


Off-by-one buffer size error triggers Panic when constructing RecordBatch from IPC bytes (should return an Error)

Describe the bug

When reading Arrow Bytes, it seems boolean array inputs can trigger panics under certain conditions.
If my input bytes are bad, I want the arrow API to throw an Err, not panic.
In this case, I don't think there's something wrong with my input bytes - rather, it seems like there's an off-by-one error internally within arrow-rs which is causing invariants to be broken.
The error is being thrown in the validate routine:
https://github.com/apache/arrow-rs/blob/master/arrow-data/src/data.rs#L667-L673
And it's being unwrapped in the caller in create_primitive_array, which DOES NOT return a Result.
https://github.com/apache/arrow-rs/blob/master/arrow-ipc/src/reader.rs#L487
Judging by the fact that unwrap is used, this function presupposes certain invariants that make it safe to use unwrap, but for some inputs, these invariants seem to not be met.
Since the problem appears to be with the length of a buffer, I'm tracing the origin of that buffer (per my stack trace) to https://github.com/apache/arrow-rs/blob/master/arrow-ipc/src/reader.rs#L1140 - I might be wrong.
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: InvalidArgumentError("Need at least 321 bytes for bitmap in buffers[0] in array of type Boolean, but got 320")', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/arrow-23.0.0/src/ipc/reader.rs:486:14
stack backtrace:
   0: rust_begin_unwind
             at ./rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at ./rustc/897e37553bba8b42751c67658967889d11ecd120/library/core/src/panicking.rs:142:14
   2: core::result::unwrap_failed
             at ./rustc/897e37553bba8b42751c67658967889d11ecd120/library/core/src/result.rs:1785:5
   3: arrow::ipc::reader::create_primitive_array
   4: arrow::ipc::reader::create_array
   5: arrow::ipc::reader::read_record_batch
   6: arrow::ipc::reader::StreamReader<R>::maybe_next
   7: arrow::ipc::reader::StreamReader<R>::maybe_next
   8: arrow::ipc::reader::StreamReader<R>::maybe_next
   9: arrow::ipc::reader::StreamReader<R>::maybe_next
  10: arrow::ipc::reader::StreamReader<R>::maybe_next
  11: arrow::ipc::reader::StreamReader<R>::maybe_next
  12: arrow::ipc::reader::StreamReader<R>::maybe_next
  13: arrow::ipc::reader::StreamReader<R>::maybe_next
  14: arrow::ipc::reader::StreamReader<R>::maybe_next
  15: arrow::ipc::reader::StreamReader<R>::maybe_next
  16: arrow::ipc::reader::StreamReader<R>::maybe_next
  17: arrow::ipc::reader::StreamReader<R>::maybe_next
  18: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter
  19: core::iter::adapters::try_process
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

To Reproduce

I am using the following routine to read IPC bytes. I don't currently have an input bytes which triggers this, but I can find one if you think it's critical for you to debug this properly.
pub fn from_ipc_bytes(bytes: &[u8]) -> Result<Vec<RecordBatch>, anyhow::Error> {
    let cursor: Cursor<&[u8]> = Cursor::new(bytes);
    let reader = arrow::ipc::reader::StreamReader::try_new(cursor, None)?;
    let record_batches = reader.collect::<Result<Vec<RecordBatch>, arrow::error::ArrowError>>()?;
    Ok(record_batches)
}

Expected behavior

Either throw an error if there's a problem with my input bytes, or succeed if there is no problem with my input bytes, but do not panic.
Additional context

@alamb - You seem to have written these validation checks, so I wonder if you would understand what might be happening for me. Let me know if it's crucial for me to provide bytes inputs which trigger the panic, but I think the stacktrace and error message here might be enough to go off of.

Hi @aarashy  -- thank you for the report.
The validation routine you point to is basically saying that it expects that the size of the underlying buffer for the BooleanArray is at least 321 bytes, but for some reason the data has only 321.
I agree that the IPC reader should return the error rather than panicing in this case.
Not sure if you are up for proposing a PR to fix the issue (propagate the error) but if you are I would be most appreciative

@alamb - I appreciate the prompt response.
Do you think it would be crazy for create_primitive_array to return a Result so that I can question-mark the build result and remove the unwraps in that function entirely? It seems the only caller of create_primitive_array is create_array which returns a Result, so I think there wouldn't be too much refactoring there.
However, there's a bigger question of why the data has only 320 instead of 321 in the first place.
That, I am less sure about.
I'll try to get a bytes input that triggers this panic to enable a full repro and maybe it would be more obvious then.

Do you think it would be crazy for create_primitive_array to return a Result so that I can question-mark the build result and remove the unwraps in that function entirely?

I don't think that would be crazy at all -- sounds like a good idea to me

However, there's a bigger question of why the data has only 320 instead of 321 in the first place.

👍

I removed the unwraps here https://github.com/apache/arrow-rs/pull/3232
I have some bytes which reproduce this error, but the data is private. The bytes were the result of the apache-arrow NPM package function tableToIPC - https://github.com/apache/arrow/blob/5611f2bd0d6136b005d137a84b50709fc5c813bb/js/src/ipc/serialization.ts#L61
More info about the error stacktrace above
Let me share a little bit more about the error in ArrayData::validate above.

The value of len_plus_offset is 2565, and offset is 0. Thus, 2565 is the number of rows in the the record batch from higher in the callstack (read_record_batch).
2565 is not divisible by 8 (2565/8 = 320.625) - so it seems correct for the validate function to be expecting 321 bytes if we need to fit 2565 bits within byte-boundaries (there is a ceiling function being applied on the division, which seems correct).

Thus, I really want to understand why the buffer is given only 320 bytes. It seems like instead of correctly zero padding the 2565 bits to reach the next byte-boundary, the bits have truncated at the previous byte-boundary and the byte buffer is 1 byte too small.
I'm struggling to really find the origin of the length of the Array data byte buffers here which would be performing this truncation... I suppose it would be Message::header_as_dictionary_batch -> Message::buffers?
Another similar error stacktrace
I have another callstack which is throwing a similar panic on a different input bytes set. This one is from indexing into a slice out of bounds, again off-by-one.
thread 'tokio-runtime-worker' panicked at 'range end index 65 out of range for slice of length 64', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/arrow-buffer-28.0.0/src/util/bit_chunk_iterator.rs:57:23
stack backtrace:
   0: rust_begin_unwind
             at ./rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at ./rustc/897e37553bba8b42751c67658967889d11ecd120/library/core/src/panicking.rs:142:14
   2: core::slice::index::slice_end_index_len_fail_rt
             at ./rustc/897e37553bba8b42751c67658967889d11ecd120/library/core/src/slice/index.rs:76:5
   3: core::slice::index::slice_end_index_len_fail
             at ./rustc/897e37553bba8b42751c67658967889d11ecd120/library/core/src/slice/index.rs:69:9
   4: arrow_buffer::util::bit_chunk_iterator::UnalignedBitChunk::new
   5: arrow_buffer::buffer::immutable::Buffer::count_set_bits_offset
   6: arrow_data::data::ArrayData::new_unchecked
   7: arrow_data::data::ArrayDataBuilder::build_unchecked
   8: arrow_ipc::reader::create_dictionary_array
   9: arrow_ipc::reader::create_array
  10: arrow_ipc::reader::read_record_batch

In this case:

The record batch is of length 518, which is again not divisible by 8 (64.75).
The panic is coming from https://github.com/apache/arrow-rs/blob/master/arrow-buffer/src/util/bit_chunk_iterator.rs#L57 - the UnalignedBitChunk is being created downstream of the count_nulls routine in ArrayData::new_unchecked. This callstack doesn't perform validations or return Result, so it's awkward for me to add a slice-out-bounds check and return an error. To me this indicates, again, that the wherever the null_bit_buffer length is being initialized, it's being truncated incorrectly.
The data_type of the array being created here is Dictionary(Int32, Utf8).

I wonder if @tustvold, @alamb, or @HaoYang670 would know anything about improperly truncated / padded byte buffers during IPC byte reading. It's possible that my input is missing some padding, but perhaps this crate should generously perform padding which the Javascript apache-arrow crate is neglecting. It's also possible that this is a Javascript arrow package bug, but if we have an opportunity to be more permissive and flexible here, we should take it (and we at least shouldn't have panics),

If your IPC payload is generated by apache-arrow NPM package function tableToIPC, the size of buffers is produced by that, not from arrow-rs. IPC reader just reads provided buffer with provided offset/length.

@viirya , thanks for your helpful reply. I've created this issue in the arrow repo to track it there. (https://github.com/apache/arrow/issues/14791)
Now my last question is, are we okay with the fact that the UnalignedBitChunk indexes into the slice without checking the bounds first, causing a panic?
It seems like, in situations where the input arrow bytes are the correct shape but have some subtle bug like this, arrow-rs is vulnerable to panic. Do you think it's important to add appropriate checks here instead of using functions like new_unchecked? By its name, this function seems to believe that essential invariants like buffer size have already been verified, but in this case they are not.

Now my last question is, are we okay with the fact that the UnalignedBitChunk indexes into the slice without checking the bounds first, causing a panic?

I think the issue here is that currently create_dictionary_array isn't performing validation. I think this is incorrect and should be fixed.
UnalignedBitChunk expects that its inputs are already bounds checked, and panics as an invariant has been violated. This I think is fine.

I don't think there are further action items for this ticket, so closing. Feel free to reopen if I have missed something

label_issue.py automatically added labels {'arrow'} from #3247


feat:added email template

⚠⚠⚠ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma
Tick the checkbox if you understand [x]:

[ ] I have read and understand the pull request rules.

Description
Fixes #(issue)
Type of change
Please delete any options that are not relevant.

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

Checklist

[ ] My code follows the style guidelines of this project
[ ] I ran ESLint and other linters for modified files
[ ] I have performed a self-review of my own code and tested it
[ ] I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)
[ ] My changes generates no new warnings
[ ] My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)
Please do not use any external image service. Instead, just paste in or drag and drop the image here, and it will be uploaded automatically.

@CommanderStorm I think all his/her pull requests have to be on hold first.
@qburst-justinjoseph
Since you have not tick the checkbox. Could you please make sure you have read all rules?
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma
First, it is a bit strange that you closed 3 pull requests and open 3 new pull requests again.
Are you trying to contribute this project or you just develop for yourself, but you created to a wrong repo?
If you want to contribute this project. @chakflying's comment is still valid, did you read them?
https://github.com/louislam/uptime-kuma/pull/4124#issuecomment-1833195175
I really don't want to waste your time, but you are making something that definitely do not meet our standard. So I hope we can have a better communication.

#4166 Again, you closed it. If you keep doing this with saying something, I will restrict you to access this repo.

Checked your profile.
I assume that you were making some changes for your company:
https://github.com/qburst/uptime-kuma/pulls?q=is%3Apr+is%3Aclosed
It was created by mistake.


Offset on the left?

Hello, I really appreciate your work; it has been quite helpful to me. By the way, would it be possible to incorporate something like an offset on the left side of the table? This would greatly enhance the representation of data structures when drawing them.

@brightiup thanks, what exactly do you mean by an offset.  If i understand correctly you want something like
#import "@preview/bytefield:0.0.1": *
#grid(
  columns: (2cm, 1fr),
  [], ipv4
)

Sorry for the late answer i was at vacation.

Thanks for your answer. Is there a way to mark the offset on the left side of this table? This would be useful for describing data structures.

Not at the moment. You need to add annotations in the other side on the grid an need to move them so they fit. But this is not an ideal solution. I would like to integrate something like this but at the moment i don't have enough time. If you would like to contribute feel free.


Allow PHP 8.x in v1 branch

Solves #419

@ankitpokhrel Yes, Drupal 9 is PHP 8 but Symfony 4.

@drastik I see, thanks!
End of bug fixes for Symfony 4 is November 2022 and the end of security fixes will be on November 2023. PHP7.* and 8.0 has reached its end of life.
I don't know if it would be wise to work on adding support for PHP8 in v1 at this point if this requires a lot of work. I am open for PR tho. Or, perhaps you can maintain a fork for the time being?

I feel ya.  Yeah they recommend/soft-require PHP 8.1+, but I wish they hadn't stuck with Symfony 4 at the time of D9 development.  I guess we can close this?


Investigate searching for full phrase

When entering more than one search term, the current search functionality searches for elements containing at least one of the search terms.
Verify if it's possible to search for results containing all of the search terms first (or at least exclusively all of them), and if it's possible, deploy the solution for testing on Heroku.

Spike complete, development in #644


Shoulder_pan_joint of the fetch robot can't reach the upper limit

Hi!
Thanks to the work of Robohive team!
Before working with the fetch_reach_v0.xml, I found that the shoulder_pan_joint can only reach 1.04 instead of its upper limit of 1.6056.
Here is the PNG to illustrate this phenomenon:

Is this caused by the Mujoco actuator of the shoulder_pan_joint?

Thanks @STAY-Melody  for trying RoboHive. I was able to reproduce this at my end. It seems like the arms starts colliding with the back of the body.

The reason seems to be that the convex hull (used for mesh collisions) is not a good approximation of the actual geometry. The fix should involve creating a better collision surface that avoids that issue. The fix shouldn't be hard, I will update once it is available in the dev branch for you to try.

Fixed in e16059360032c300a7f6503b8b47ba7253070d6e


Is this project still active?

Hello 👋 ,
I just wanted to ask whatever this project is still being actively developed. There is already Adobe XD v34 but the latest release of typings here is for v25. Thanks.

Hi there 🙂
It is still alive, but it's maintained primarily by a student with a very limited amount of time (me 😜).
You can see the XD v29 PR (#77). Unfortunately, work, exams at university, and illness prevented me from getting to work on the repo since then.
All in all: Yes, it's still alive and maintained, I hope to get back to updating it soon. I'll review and merge any PRs, read every issue, etc., but updates may be slow.

Thanks, I find funny that Adobe has 22 thousand employees, and they dedicate a student to maintain this repo. I'm not saying it's bad, but it's kind of obvious that it's hard for you to stay up to date with XD releases.

@petrbrzek The project started during the plugin APIs' prerelease stage when I needed these definitions myself and developed them. They then became part of this GitHub organization at a later stage (after being published in an old-school fashion through zip-files in the prerelease forums). They remained a personal side-project (hosted in this GitHub organization to become the "official" Typescript definitions).
All in all, it is, therefore, less dedicating me to it.  This repository is (in its origin and up to today) a community-driven (with me as a somewhat sole contributor and @ericdrobinson reviewing my PRs) project. It's supposed to be a solution until Adobe provides some more official solution (which, rumor has it, might hopefully happen more sooner than later with UXP now also being available in Photoshop 😉 ).
Just as a disclaimer (as someone might, otherwise, possibly misinterpret my previous comment): I am (at least for now, I silently hope that this might change in the future? 😅 ) not an employee at Adobe (just another plugin developer 😜 ). I also haven't officially been declared as this repository's maintainer. The project just started as a personal project, and at least for now, no one at Adobe has "taken over" the repo. 😉


Move content of ts/Vec implementation directly into ts/Map

This should be done prior to fully transition to std::vector usage since we want no more of ts/Vec includes in ATS code - std::vector is the weapon of choice from now on.
After that is done we can remove source files related to ts/Vec.

Vec has been removed.