How should Do inference  using own resnet model?

I have trained the resnet18 model on the custom dataset. I would like to include that in the available networks. what are the steps to be followed?

Hi @bundelesneha05 - was it trained with PyTorch and has it been converted to ONNX?
If so, you can run it like this by specifying your custom model arguments on the command line:
https://github.com/dusty-nv/jetson-inference/blob/master/docs/pytorch-cat-dog.md#processing-images-with-tensorrt

Hi @bundelesneha05 - was it trained with PyTorch and has it been converted to ONNX?
If so, you can run it like this by specifying your custom model arguments on the command line:
https://github.com/dusty-nv/jetson-inference/blob/master/docs/pytorch-cat-dog.md#processing-images-with-tensorrt

Thanks for the reply. It has been converted to the ONNX. The above link worked.

Thanks for the reply. It has been converted to the ONNX. The above link worked.

I have also trained the ssd_fpn_resnet_18 model using TensorFlow(1.15.1) on a custom dataset. The model has converted to the ONNX format. Not getting how to do the inference for this model using detectnet.py.

I have also trained the ssd_fpn_resnet_18 model using TensorFlow(1.15.1) on a custom dataset. The model has converted to the ONNX format. Not getting how to do the inference for this model using detectnet.py.

Supporting different model architectures requires that the pre/post-processing code be added to jetson-inference/c/detectNet.cpp
The code supporting the ONNX models for detectNet.cpp/.py are currently setup for the SSD-Mobilenet models trained with PyTorch like here:   https://github.com/dusty-nv/jetson-inference/blob/master/docs/pytorch-ssd.md

Supporting different model architectures requires that the pre/post-processing code be added to jetson-inference/c/detectNet.cpp
The code supporting the ONNX models for detectNet.cpp/.py are currently setup for the SSD-Mobilenet models trained with PyTorch like here:   https://github.com/dusty-nv/jetson-inference/blob/master/docs/pytorch-ssd.md


control plane monitoring/alerting by default

As prometheus is shipped by default, control plane monitoring should be setup by default, and documented.

Prometheus 2.0 is available in the optional addon manifests, deployed via kubectl apply -f addons/prometheus -R. There is a tutorial at https://typhoon.psdn.io/addons/prometheus/ describing targets, alert rules, exporters, and grafana visualizations. Reasonable alerting rules are included by default and checked on all platforms. Have you gone through that tutorial?

Yes. I looked at the tutorial.

describing  targets, alert rules,

However it does not talk anything about the rule file you linked above. Also this config file (https://github.com/poseidon/typhoon/blob/master/addons/prometheus/config.yaml) should probable be linked to?
etcd also has pre-defined FQDN in typhoon setup. Why not provide a default set of targets (default size to 3 or 5)? Or at least, we can call it out so people know the importance of monitoring it? Based on my operational experience of Kubernetes, I would always prefer monitoring etcd first, and make sure the data store is reliable.
I even think the monitoring/alert addon should be promoted to a required component if typhoon is intended to provide sane configurations for production clusters.


mp4upload extractor code not working

Describe the bug
mp4upload changed html source, so the regular expression match is flawed

Can Confirm this. Happening to me too.

Please provide some screenshots of the problem and how to reproduce it.

@ItachiSharingan Please provide what @ngomile asked for. If no response is heard, I'll close this

Closing due to no response

@vn-ki, this is what I get.
Also, managed to do it in one of my other scripts without regex.
I'm assuming that mp4u_embed is the embed html as text and not soup (didn't see it being set to a beautifulsoup object)
So far, all the links I've tried this with have worked:
mp4u_embed = BeautifulSoup(mp4u_embed, 'html.paser')

#Named the variable this way since all the info is in the script tag
script = mp4u_embed. find_all(' script')[-1]. text.split('|')
domain = script[-92]
protocol = script[-10]
video_id = script[-11]
stream_url = f'https://{domain}.mp4upload.com:{protocol}/d/{video_id}/video.mp4'


RepayFromLadle and closeFromLadle send the collateral and remainder to the same address

repayFromLadle and closeFromLadle send the collateral and remainder to the same address, which means that they cannot be chained with other actions afterwards.
From the user point of view, if:

They add liquidity
Remove it before the pool they initially provided to reaches maturity
They have made a profit, or the interest rates rise significantly
They used "Borrow and Pool"
Then they will receive some fyToken instead of underlying.

RepayFromLadle and closeFromLadle should be refactored to take an address for each token transfer.
This can be coded as a new Ladle, first used as a module in the existing Ladle, and eventually promoted to main Ladle. Or we can do a complete swap.

Let's fix this with a Ladle module. @Sabnock01, could you please take care of it?

Resolved


Fail when =contains=> targets a non-map value

Ran into a bug when using ..some-metaconstant.. =contains=> [1 2 3] only to realize that =contains=> was never meant to be used with lists, or non-map values for that matter.
For example, the current metaconstant merging logic, which runs when ..mc.. =contains=> ... appears twice in against-background/provided forms, doesn't work with non-map values.
Also, what would be the semantics of the following?:
(fact
  (first (g)) => ????
  (provided
    (g) => ..result..
    ..result.. =contains=> [1 2]
    ..result.. =contains=> [3 4]))

One could argue that letting =contains=> operate over sets would be useful and have clear semantics, but I'm in favor of restricting the capabilities of =contains=> because it is already a bit confusing to use.
The approach this PR takes to addressing the problem is to change the behavior of =contains=> from:
(use 'midje.repl)

(defn get-metaconstant-storage-str [m]
  (with-out-str (print (.storage m))))

(unfinished a-func)
(fact "example showing that you used to be able to store anything in a metaconstant"
  (get-metaconstant-storage-str (a-func)) => "[1]"
  (provided
    (a-func) => ..result..
    ..result.. =contains=> [1]))

to
(fact
  (get-metaconstant-storage-str (a-func)) => "[1]"
  (provided
    (a-func) => ..result..
    ..result.. =contains=> [1]))

FAIL at (form-init935422476386958100.clj:2)
    Midje could not understand something you wrote:
        In `..result.. =contains=> [1]`, [1] is not a map.

:+1:

:rubinho:, but 👏

@viniciushana & @ericvm looks like I missed the case where =contains=> points to a variable that points to a map or non-map value. Should be covered in this PR: https://github.com/marick/Midje/pull/400


[DRAFT] [c#] Address user study feedback in SampleTests.cs

Description of changes
Addresses a variety of feedback items received in the recent round of user studies for the C# sample. Specifically:

Moves the test setup/cleanup below the example test methods
Clarifies which using statements a reader is likely to care about
Adds a TestMethod demonstrating a basic scan of an entire page as the first example test, before the "scan one element in page" example
Ensures that there is an example test that actually fails in practice, to give a better idea of what a failure would look like
Clarify how Include works before using it incidentally alongside WithTags
Add a more precise/verbose description of what "tags" and "rules" are and how to find more information about them
clarify that Include/Exclude accept CSS selectors (not just IDs)
Update sample page element IDs to make it more obvious on first reading that they are, in fact, IDs

Starting as a draft until I work out what to do about the PR build now that we're intentionally failing a test.
Pull request checklist

[n/a] If this PR addresses an existing issue, it is linked: Fixes #0000
[nope!] yarn test passes in all affected samples
[x] Added any applicable tests

reopening to retrigger new PR builds


TypeError in /clan/the-storm-pvugqj2u

Error in ClashLeaders
TypeError in /clan/the-storm-pvugqj2u
Cannot read property 'field' of undefined
View on Bugsnag
Stacktrace
https://www.clashleaders.com/static/js/details-page.c91a87279822728cc63c.js:1 -

View full stacktrace
Created automatically via Bugsnag

An error linked to this issue has been marked as fixed in Bugsnag
TypeError in /clan/the-storm-pvugqj2u

An error linked to this issue has been reopened in Bugsnag
TypeError in /clan/devil-may-cry-c08jgyul

An error linked to this issue has been marked as fixed in Bugsnag
TypeError in /clan/devil-may-cry-c08jgyul


[BugFix] Fix the thrift library conflict in some cases by linking the required cachelib dependencies statically

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

When linking the cachelib dynamically by find_package,  all related libraries will be linked.  While some of them are not required in our usage scenarios, and even lead to dependency conflicts in some environments.
So, we choose to only link the required cachelib dependencies statically to avoid unnecessary conflicts. Also, with this change, it is no need to package lots of dynamic libraries in our be output.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

run starrocks_admit_test image

run starrocks_admit_test image

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

run starrocks_be_unittest

run starrocks_admit_test

run starrocks_fe_unittest

run starrocks_fe_unittest

run starrocks_admit_test

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

hi @GavinMar
I'm trying to customize a cachelib for our own purpose, but not knowing how to build a static cachelib so that it can still integrate into SR.
I'm using this version of cachelib: https://github.com/facebook/CacheLib/releases/tag/v2<IP_ADDRESS>,
and adding -DBUILD_SHARED_LIBS=OFF in contrib/build-package.sh to change default dynamic lib to static lib.
But I find the outcome .a files are significantly smaller than in https://cdn-thirdparty.starrocks.com/cachelib/cachelib-20230130.tar.gz:
my libs:
libcachelib_allocator.a 48M
libcachelib_common.a 4.4M
cdn-thirdparty:
libcachelib_allocator.a 170M
libcachelib_common.a 17M
am I doing it correctly ? can you please share some notes on how to build the cachelib?
can you pleas

hi @GavinMar
I'm trying to customize a cachelib for our own purpose, but not knowing how to build a static cachelib so that it can still integrate into SR.
I'm using this version of cachelib: https://github.com/facebook/CacheLib/releases/tag/v2<IP_ADDRESS>, and adding -DBUILD_SHARED_LIBS=OFF in contrib/build-package.sh to change default dynamic lib to static lib. But I find the outcome .a files are significantly smaller than in https://cdn-thirdparty.starrocks.com/cachelib/cachelib-20230130.tar.gz:
my libs:
libcachelib_allocator.a 48M libcachelib_common.a 4.4M
cdn-thirdparty:
libcachelib_allocator.a 170M libcachelib_common.a 17M
am I doing it correctly ? can you please share some notes on how to build the cachelib?
thanks!

Yes, I also built cachelib by adding DBUILD_SHARED_LIBS=OFF in contrib/build-package.sh. I'm not quite sure why your output is so much smaller than mine because you choose a newer cachelib version. So, if you could build all libraries successfully, I think you can try to integrate it into SR and check whether the block cache can work as expected.

hi @GavinMar
thanks for the reply.
may i know which cachelib version did you use?

hi @GavinMar
thanks for the reply. may i know which cachelib version did you use?

I used the version v2023.01.23 and I think your version is also ok. And you'd better build the cachelib with the same toolkits, such as g++ version, to avoid some abi compatibility problems.

thank you so much for the tips! I'll give another shot


Fix the read timeout implementation in NettyStream

Both the new approach and the original one achieve the guarantee that
there are no concurrent read timeouts scheduled for a channel.
This is an essential property needed for a timeout implementation,
let us call it "at-most-one".
The original approach of achieving the at-most-one property:

Schedule timeouts only by an event loop thread.
If another thread needs to schedule a timeout, it submits a new scheduleTimeout task
to the channel's event loop (asynchronous timeout scheduling).
The scheduleTimeout task schedules a new timeout if none is scheduled.
The original approach allowed executions in which a scheduleTimeout task runs after
completion of the read operation that submitted the task,
which resulted in unexpected timeout exceptions.

The new approach achieves the at-most-one property by using a lock.
As a result, timeouts can be scheduled by any thread and there is no
asynchronous timeout scheduling. This means we cannot miss removing a timeout
because it was submitted for scheduling, but has not been scheduled yet.
Other notable changes:

[related  bug fix] NettyStream now must always respect the requested additional timeout.
The original implementation had a chance to ignore the requested additional timeout
and schedule a timeout with the default delay. This is again due to the asynchronous
timeout scheduling in the original approach.
[performance optimization] Public read methods do not schedule timeouts anymore
if the requested number of bytes is available right away.
[performance optimization] Netty channel handlers do not try to schedule timeouts anymore,
timeouts may be scheduled only by the public read methods.
Trying to schedule timeouts from the method handleReadResponse was unnecessary
even in the original approach.
[performance optimization] NettyStream does not produce excessive garbage by re-creating PendingReader
objects each time a new piece of data arrives for a pending reader.
[code improvement] The fields NettyStream.pendingReader, pendingException are always written/read
inside synchronized blocks that use the same NettyStream object, so they can be plain.
Marking them volatile is unnecessary and potentially misleading.
[code improvement] ReadTimeoutHandler was removed because it wasn't acting as a handler and was not needed.

JAVA-3920

Almost all improvements described in the "Other notable changes" are done because of the suggestions expressed by @konrad-kaminski either verbally or via the proposed code. Thank you, Konrad!

Almost all improvements described in the "Other notable changes" are done because of the suggestions expressed by @konrad-kaminski either verbally or via the proposed code. Thank you, Konrad!

Can you think of any way to test this code?

We need a test that calls reads with variable added timeout on a NettyStream object and checks that reads do not fail because of a premature timeout. Since we cannot have concurrent pending readers on a single NettyStream, such a test needs to use many NettyStream objects to increase the number of concurrent attempts. This increases our chances to spot a problem without having to run the test for too long. Apparently, we also need a server that sends data with variable delays. It is important to note that while a test like this is probabilistic (may not spot the problem), it does not fail spuriously, i.e., when code is correct, because of the lack of hard real-time constraints (provided that we use System.nanoTime to measure time intervals, as it is guaranteed to be monotonic).
It would also be nice to have a way to check that reads do not fail due to timeouts if data is made available in a timely manner. Unlike 1., such tests are allowed to fail spuriously, i.e., fail even if the code is correct, because hard real-time computing is not what we do. However, if we set the max (soft) server delay as 2 seconds, while the min read timeout value is 30 seconds, then timing out almost certainly means we hit an actual code problem, e.g., a deadlock, rather than just experienced the expected behaviour of a non-real-time computing system.

As an alternative to writing and starting/stopping a test server bound to a loopback interface, we may try using EmbeddedChannel. Netty has it specifically to facilitate testing. From what I can see in the "Netty in action" book, this channel is supposed to be used for testing one or multiple channel handlers (it accepts an array of handlers as one of its constructor arguments and builds an internal pipeline), and I am not sure it can be used as a transport implementation. In other words, I am not sure we can specify it via Bootstrap.channel(Class<? extends C> channelClass). However, we can try, this will require changing NettyStream(...Class<? extends SocketChannel> socketChannelClass...) to NettyStream(...Class<? extends Channel> channelClass...) and changing the return type of the NettyStream.getSocketChannelClass method.
Writing such a test is not exactly a trivial task, so if we decide to write it, I am proposing to have a separate task in Jira. Should I create one?

Can you think of any way to test this code?

We need a test that calls reads with variable added timeout on a NettyStream object and checks that reads do not fail because of a premature timeout. Since we cannot have concurrent pending readers on a single NettyStream, such a test needs to use many NettyStream objects to increase the number of concurrent attempts. This increases our chances to spot a problem without having to run the test for too long. Apparently, we also need a server that sends data with variable delays. It is important to note that while a test like this is probabilistic (may not spot the problem), it does not fail spuriously, i.e., when code is correct, because of the lack of hard real-time constraints (provided that we use System.nanoTime to measure time intervals, as it is guaranteed to be monotonic).
It would also be nice to have a way to check that reads do not fail due to timeouts if data is made available in a timely manner. Unlike 1., such tests are allowed to fail spuriously, i.e., fail even if the code is correct, because hard real-time computing is not what we do. However, if we set the max (soft) server delay as 2 seconds, while the min read timeout value is 30 seconds, then timing out almost certainly means we hit an actual code problem, e.g., a deadlock, rather than just experienced the expected behaviour of a non-real-time computing system.

As an alternative to writing and starting/stopping a test server bound to a loopback interface, we may try using EmbeddedChannel. Netty has it specifically to facilitate testing. From what I can see in the "Netty in action" book, this channel is supposed to be used for testing one or multiple channel handlers (it accepts an array of handlers as one of its constructor arguments and builds an internal pipeline), and I am not sure it can be used as a transport implementation. In other words, I am not sure we can specify it via Bootstrap.channel(Class<? extends C> channelClass). However, we can try, this will require changing NettyStream(...Class<? extends SocketChannel> socketChannelClass...) to NettyStream(...Class<? extends Channel> channelClass...) and changing the return type of the NettyStream.getSocketChannelClass method.
Writing such a test is not exactly a trivial task, so if we decide to write it, I am proposing to have a separate task in Jira. Should I create one?

The ticket to add tests: JAVA-3946.

The ticket to add tests: JAVA-3946.


PubSub: add_methods() doesn't handle @classmethod-s as expected

Using the public interface, the @classmethod only works on instances:
>>> from google.cloud import pubsub_v1
>>> publisher = pubsub_v1.PublisherClient()
>>> publisher.topic_path('a', 'b')
'projects/a/topics/b'
>>> pubsub_v1.PublisherClient.topic_path('a', 'b')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File ".../google/cloud/pubsub_v1/_gapic.py", line 44, in <lambda>
    fx = lambda self, *a, **kw: wrapped_fx(*a, **kw)
TypeError: topic_path() missing 1 required positional argument: 'topic'

note that there is no issue with the base:
>>> from google.cloud.pubsub_v1.gapic import publisher_client
>>> publisher_gapic = publisher_client.PublisherClient()
>>> publisher_gapic.topic_path('a', 'b')
'projects/a/topics/b'
>>> publisher_client.PublisherClient.topic_path('a', 'b')
'projects/a/topics/b'

$ git log -1 --pretty=%H
4b107613b0fcf139569504e9d44fa4a0793b4fd0

I'm going to close this, these resource paths aren't useful without a client, and at any rate, we'd need to update the generator to do this.


frotz: init at 2.44

Motivation for this change
I'm a fan of IF. 😊
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[x] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Merged in https://github.com/NixOS/nixpkgs/commit/69cf5aa4f36648e470d1e322045ac4efca27b02a


Readme file

@Vikash-8090-Yadav
Created README.md file for each level and i have described the projects in a systematic manner . If your find it good then please merge it sir or else if any change required then also please comment

attach the images also

attach the images also

Ok sir  I will add images

Attached the images and also live working videos @Vikash-8090-Yadav

@Bharadwajshivam28 remove the videos.

@Bharadwajshivam28 update the level0 , as the level contains the 5 projects and  in your updated readme it shows only 4

@Bharadwajshivam28 remove the videos.

ok sir

@Bharadwajshivam28 update the level0 , as the level contains the 5 projects and in your updated readme it shows only 4

oh sorry sir it will be updated

Updated these sir

attach  only one image / screen shot for the particular project decsription .

attach  only one image / screen shot for the particular project decsription .

Sir please elaborate

attach  only one image / screen shot for the particular project decsription .

Ok sir

@Vikash-8090-Yadav Done with the changes sir

@Vikash-8090-Yadav Hello sir if no issue then please merge it sir


feat: Remove binaries from argoexec image. Fixes #7486

Signed-off-by: Alex Collins<EMAIL_ADDRESS>Fixes #8291
Fixes #7800
Fixes #7798
Fixes #7796
Fixes #7486
argoexec still runs as root with read-write FS, but is much lower risk.
This PR obviates the following:
Closes #7253
Closes #7799
Closes #7983
Closes #7797
Why? The big security issue with both alpine and debian base images is that, when compromised by an attacker:

As root, can install any app you want.
Anything installed can be run.

Using distroless/scratch only things pre-installed can be run: argoexec, jq and kubectl. Naturally, kubectl is still an bad escalation if the pod is over-permissioned.
Next steps:

#6895

Thanks let me know when ready for review.

This PR should have a tough review.

changes made - ready for review again

The removal of the git binary means that file:// scheme git artifacts are no longer supportedbecause go-git is not pure go: it relies on the git binary for the file:// cheme: https://github.com/go-git/go-git/blob/master/COMPATIBILITY.md#transport-schemes

Warning: this is not pure Golang. This shells out to the git binary.


Coredump on segfault

@enolan will point @jkrauska at this

We should test this and make sure it works. CI should be gathering coredumps though.


New Workers tutorial - Automated Analytics Reporting with Cloudflare Workers and Email Routing

Summary
Added a Workers tutorial - Automated Analytics Reporting with Cloudflare Workers and Email Routing
Documentation checklist

[x] The documentation style guide has been adhered to.

@Maddy-Cloudflare thanks for the review! updated with 7f5a44f


Remove MediatedEvictionConcurrentHashMap.

Use a regular ConcurrentHashMap. release() operations that return the final lease are responsible for eviction to disk. The node remains in the cache with a lease count of -1 this is used as a tombstone
in the cache while the eviction to disk is taking place.
Thanks to an earlier change where nodes must be leased prior to deletion, I don't think there is the possibility of a race condition with node deletion and node eviction. Also note that node state "-3" has been removed in this branch. It is no longer needed.
In the performance tests this branch performance no worse and sometimes slightly better than the MediatedEvictionConcurrentHashMap. Results are https://goo.gl/yk2ztF (internal access only).

Is the implication of this that the node cache will always miss unless there is enough contention between threads?

Err. Performance numbers show a 10x reduction in performance for one class of critical jobs.

Closing for now, as it does not seem safe to become the default (and only) option at this time. Might make an interesting toggle.


Inference Bounty

Hey @YassineYousfi!
Just learnt about this from your talk being (re)released, very cool!
Spent some time on the inference bounty, getting 0.2s per frame on 4090 and 0.28s on a 3090. May be more I can squeeze out, but not certain.
Some quick questions:

Is the bounty still open?
Does a pure PyTorch solution with some startup time due to compilation fit your criteria?
If yes to the above two, what's the standard process re: bounties?

Hey

yeah the bounty is still open
pure pytorch is fine, although the compile time is quite annoying (e.g. in https://github.com/pytorch-labs/gpt-fast/). is there a way to export the compiled model yet?
once you're ready, you can send me the code, then we pay out the bounty if it runs at less than 0.25 sec/frame on my 3090 :)

Watched about half the presentation replay last night and was looking to see if these were solved. Any updates on this front https://github.com/YassineYousfi and https://github.com/ae99?

Hey! Sorry, busy week. Thanks @YassineYousfi!
Yes have solved this I think, just some tinkering on exporting to go!

@ae99 Cool, congratulations! Looking forward to seeing your solution.

Have you had any luck on this? TensorRT seems to be able to run the model at around 230-235ms/frame though with wrong outputs...

Abandoned for now, good luck!


Currpage.close does not work as expected on pagetype confirmationDialog and Onvalidate trigger do not react on enter

Dialog Test.zip
We have 2 issues related to pagetype= confirmationDialog when using Onvalidate trigger

using currpage.close do not close the page after the onvalidate trigger is done

If you default some input into a field on a confirmationDialog page eg. on OnOpenPage you can not press enter to initiate the onvalidate trigger code to be triggered.
You have to enter some new text, this works in C/AL if you press ctrl+enter but not in the webclient and a scenario where this could be an issue would be in a scanner scenario where you do not want to write the input you need, but just need to confirm this by pressing enter to go to next step in the flow.

Steps and to reproduce the behavior:
I have attached a simple app that shows the problem, add Page 50101 as the startuppage in launch.json for issue 1 press enter
for step 2, enter something different to trigger the validation code, and a message should be shown but the dialog page do not close automatically.
AL Code to reproduce the issue
See attached files
Expected behavior

Expect the onvalidate code to be trigger when pressing enter og ctr+enter without changing the text in the input field.
expect the dialogpage to close when onvalidate code has been triggered.

Versions:

AL Language: 3.0.106655

This is no longer searchable  but under help

Business Central: Version: Platform 14.0.29530.31705 + program 31808 (DK Dynamics NAV 14.0)

Hi! In the last months, we've been working hard on adding new features that increase your productivity and on improving the quality of the tools. Unfortunately, this meant that we were not able to follow up on as many GitHub issues as we have liked.
Is this issue still a problem for you? Can you provide a sample project to reproduce the issue? Does it reproduce on the Wave 2 2019 release?

This issue has been closed because it needs more information and has not had recent activity. Please open a new issue if you believe this has not been resolved and reference the current issue.


Read VTS config from YAML/JSON

Implement a config reader to read in Store settings from YAML. Use it to
configure VTS and provisioning commands.
This addresses https://github.com/veraison/services/issues/7 and https://github.com/veraison/services/issues/11

@setrofim As this is touching both the Provisioning and Verification use case, request please do an end to end test as well, just to ensure that everything is still working intact with both P and V pipelines.

though we could also use viper :-)

True. I figured I'd keep things simple for now. We can always add viper as an IReader implementation once we require more sophisticated config management.


connect ECONNREFUSED <IP_ADDRESS>:8960

Greetings everyone.
I get the error "connect ECONNREFUSED <IP_ADDRESS>:8960" whenever I try to run the script within Code Studio. It used to work before. I have tried to press ALT+ENTER but I get the following errors:
"Failed to send text to FSI"
"Failed to spawn FSI, please ensure it's in PATH"
I'm running Ubuntu 18.04.1
Code 1.28.1
The log output:
[11:58:54 INFO ] Logging to output at level INFO. If you want detailed messages, try level DEBUG.
[11:58:54 INFO ] .Net runtime specified
[11:58:54 INFO ] finding FSAC for
	runtime: NET
	mono: mono
	dotnet: null
[11:58:55 ERROR] RES (001) <- {compilerlocation} ERROR in 7 ms: {stack: Error: connect ECONNREFUSED <IP_ADDRESS>:8960
	at Object._errnoException (util.js:1024:11)
	at _exceptionWithHostPort (util.js:1046:20)
	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14), message: connect ECONNREFUSED <IP_ADDRESS>:8960, code: ECONNREFUSED, errno: ECONNREFUSED, syscall: connect, address: <IP_ADDRESS>, port: 8960, config: [object Object], request: [object Object], response: undefined} Data=undefined
[11:59:00 ERROR] RES (002) <- {compilerlocation} ERROR in 2 ms: {stack: Error: connect ECONNREFUSED <IP_ADDRESS>:8960
	at Object._errnoException (util.js:1024:11)
	at _exceptionWithHostPort (util.js:1046:20)
	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14), message: connect ECONNREFUSED <IP_ADDRESS>:8960, code: ECONNREFUSED, errno: ECONNREFUSED, syscall: connect, address: <IP_ADDRESS>, port: 8960, config: [object Object], request: [object Object], response: undefined} Data=undefined
[11:59:02 ERROR] RES (003) <- {compilerlocation} ERROR in 47 ms: {stack: Error: connect ECONNREFUSED <IP_ADDRESS>:8960
	at Object._errnoException (util.js:1024:11)
	at _exceptionWithHostPort (util.js:1046:20)
	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14), message: connect ECONNREFUSED <IP_ADDRESS>:8960, code: ECONNREFUSED, errno: ECONNREFUSED, syscall: connect, address: <IP_ADDRESS>, port: 8960, config: [object Object], request: [object Object], response: undefined} Data=undefined
[11:59:02 ERROR] RES (004) <- {compilerlocation} ERROR in 3 ms: {stack: Error: connect ECONNREFUSED <IP_ADDRESS>:8960
	at Object._errnoException (util.js:1024:11)
	at _exceptionWithHostPort (util.js:1046:20)
	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14), message: connect ECONNREFUSED <IP_ADDRESS>:8960, code: ECONNREFUSED, errno: ECONNREFUSED, syscall: connect, address: <IP_ADDRESS>, port: 8960, config: [object Object], request: [object Object], response: undefined} Data=undefined
[11:59:02 ERROR] RES (005) <- {compilerlocation} ERROR in 1 ms: {stack: Error: connect ECONNREFUSED <IP_ADDRESS>:8960
	at Object._errnoException (util.js:1024:11)
	at _exceptionWithHostPort (util.js:1046:20)
	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14), message: connect ECONNREFUSED <IP_ADDRESS>:8960, code: ECONNREFUSED, errno: ECONNREFUSED, syscall: connect, address: <IP_ADDRESS>, port: 8960, config: [object Object], request: [object Object], response: undefined} Data=undefined
[11:59:02 ERROR] RES (006) <- {compilerlocation} ERROR in 3 ms: {stack: Error: connect ECONNREFUSED <IP_ADDRESS>:8960
	at Object._errnoException (util.js:1024:11)
	at _exceptionWithHostPort (util.js:1046:20)
	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14), message: connect ECONNREFUSED <IP_ADDRESS>:8960, code: ECONNREFUSED, errno: ECONNREFUSED, syscall: connect, address: <IP_ADDRESS>, port: 8960, config: [object Object], request: [object Object], response: undefined} Data=undefined
[11:59:02 ERROR] RES (007) <- {compilerlocation} ERROR in 3 ms: {stack: Error: connect ECONNREFUSED <IP_ADDRESS>:8960
	at Object._errnoException (util.js:1024:11)
	at _exceptionWithHostPort (util.js:1046:20)
	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14), message: connect ECONNREFUSED <IP_ADDRESS>:8960, code: ECONNREFUSED, errno: ECONNREFUSED, syscall: connect, address: <IP_ADDRESS>, port: 8960, config: [object Object], request: [object Object], response: undefined} Data=undefined
[11:59:34 ERROR] RES (008) <- {compilerlocation} ERROR in 5 ms: {stack: Error: connect ECONNREFUSED <IP_ADDRESS>:8960
	at Object._errnoException (util.js:1024:11)
	at _exceptionWithHostPort (util.js:1046:20)
	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14), message: connect ECONNREFUSED <IP_ADDRESS>:8960, code: ECONNREFUSED, errno: ECONNREFUSED, syscall: connect, address: <IP_ADDRESS>, port: 8960, config: [object Object], request: [object Object], response: undefined} Data=undefined
[12:01:46 ERROR] RES (009) <- {compilerlocation} ERROR in 4 ms: {stack: Error: connect ECONNREFUSED <IP_ADDRESS>:8960
	at Object._errnoException (util.js:1024:11)
	at _exceptionWithHostPort (util.js:1046:20)
	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14), message: connect ECONNREFUSED <IP_ADDRESS>:8960, code: ECONNREFUSED, errno: ECONNREFUSED, syscall: connect, address: <IP_ADDRESS>, port: 8960, config: [object Object], request: [object Object], response: undefined} Data=undefined
[12:02:27 ERROR] RES (010) <- {compilerlocation} ERROR in 4 ms: {stack: Error: connect ECONNREFUSED <IP_ADDRESS>:8960
	at Object._errnoException (util.js:1024:11)
	at _exceptionWithHostPort (util.js:1046:20)
	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14), message: connect ECONNREFUSED <IP_ADDRESS>:8960, code: ECONNREFUSED, errno: ECONNREFUSED, syscall: connect, address: <IP_ADDRESS>, port: 8960, config: [object Object], request: [object Object], response: undefined} Data=undefined
[12:03:35 ERROR] RES (011) <- {compilerlocation} ERROR in 4 ms: {stack: Error: connect ECONNREFUSED <IP_ADDRESS>:8960
	at Object._errnoException (util.js:1024:11)
	at _exceptionWithHostPort (util.js:1046:20)
	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14), message: connect ECONNREFUSED <IP_ADDRESS>:8960, code: ECONNREFUSED, errno: ECONNREFUSED, syscall: connect, address: <IP_ADDRESS>, port: 8960, config: [object Object], request: [object Object], response: undefined} Data=undefined
[12:04:53 ERROR] RES (012) <- {compilerlocation} ERROR in 3 ms: {stack: Error: connect ECONNREFUSED <IP_ADDRESS>:8960
	at Object._errnoException (util.js:1024:11)
	at _exceptionWithHostPort (util.js:1046:20)
	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14), message: connect ECONNREFUSED <IP_ADDRESS>:8960, code: ECONNREFUSED, errno: ECONNREFUSED, syscall: connect, address: <IP_ADDRESS>, port: 8960, config: [object Object], request: [object Object], response: undefined} Data=undefined
[12:05:28 ERROR] RES (013) <- {compilerlocation} ERROR in 3 ms: {stack: Error: connect ECONNREFUSED <IP_ADDRESS>:8960
	at Object._errnoException (util.js:1024:11)
	at _exceptionWithHostPort (util.js:1046:20)
	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14), message: connect ECONNREFUSED <IP_ADDRESS>:8960, code: ECONNREFUSED, errno: ECONNREFUSED, syscall: connect, address: <IP_ADDRESS>, port: 8960, config: [object Object], request: [object Object], response: undefined} Data=undefined

Duplicate of #939


Homepage will close file in right-top corner area after reload window

Details

Steps to reproduce
drag a file into right-top corner, and restart obsidian, it will close the file. but it won't be close when disable Homepage plugin
Debug information
No response
Checklist

[X] I updated to the latest version of the plugin.

This is intentional. You can change the homepage settings to retain other notes that you have open though. Any option that is not "Replace all open notes" should work.

If you want it to close all notes in the main pane but keep ones in the right, that is currently not an option.


Centos8 and latest

@rmohr @ksimon1 Can you please have a look?
Please find an example image in quay.io/dholler/centos .

/test pull-containerdisks-build

/close
Thanks for reviewing #8  which makes this PR obsolet.


No examples for configuration files

The chronologer command line entry point asks for a configuration file, but it does not appear to be documented and there are no examples anywhere.
Documentation on this, or at least an example, would be useful.

Hi @zachriggle, thanks for these. I think this line in the README is intended to address this:

For your own project, take tests/chronologer.yaml as a starting point.

If you'd like to improve the documentation that would be great.

Thanks! Not sure how I missed that!
On Thu, Oct 22, 2020 at 2:36 PM Dan Davison<EMAIL_ADDRESS>wrote:

Hi @zachriggle https://github.com/zachriggle, thanks for these. I think
this line in the README is intended to address this:
For your own project, take tests/chronologer.yaml as a starting point.
If you'd like to improve the documentation that would be great.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dandavison/chronologer/issues/6#issuecomment-714716320,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA3IGDYMSHWRH7X7AEH3ULSMCCTLANCNFSM4S3UJW4A
.

--
Zach Riggle


Tilemap shows seams when zoomed in

Godot version: 3.0.6
OS/device including version: Windows 8.1
Issue description:
When I set camera zoom to anything less than 1, my tilemaps have hard seams between them:

Everything looks fine if it's zoomed to 1x though:

Steps to reproduce:

Create a project, set Pixel Snap on
Import an image, create a tileset, create a tilemap and draw tiles
Add a Camera2D, set zoom to something like (0.3, 0.3)
Run the scene. Note the seams.

NB: I also tried with various combinations of pixel-snap on and off, and my texture with no flags, mipmapping only, filter only, mipmapping and filter both. Same behaviour.
Minimal reproduction project: available upon request

Duplicate of #26730 by the sound of it.

Your zoomed tilemap looks blurry. To me, it means you have tiles which you upscaled in a image editor to look "pixel-arty", and then imported to Godot with default settings. However, default settings have filter enabled, and that would be where the seams come from. Do you have an example project to verify this?

I don't have an MVP project. I have a large project. I will try to cut it down to a reasonable size and deliver it to you as an MVP.
You are correct about my sprites: they're originally 16x16, and scaled up to 64x64 without aliasing.
As I mentioned, I already tried disabling filter (and mipmaps, and pixel snap) in various combinations, all to no avail.
@Sslaxx I don't think they're the same: in #26730, the seams appear at 1x zoom, and when you move. Mine appear only when zoomed in, and all the time - not just when moving.

As I mentioned, I already tried disabling filter (and mipmaps, and pixel snap) in various combinations, all to no avail.

Your screenshot is blurry, still. Are you sure you disabled that filter in import settings and clicked "Reimport"? (Modifying the texture directly won't have any effect).

@nightblade9 another option is to try this out in 3.1 and see if you can reproduce it. A lot has changed between 3.0.6 and now, so your issue may very well have been fixed. Hence why its so hard to reproduce.
@Sslaxx This bug report relates to version 3.0.6 so I dont think a PR from last week is going to be the problem. 😄

@Zylann I didn't reimport the textures. I didn't know that's necessary. I'll try that.
I'm not clear on what blurry textures has to do with the seams. Could you explain that a bit further?

@nightblade9 I was just able to reproduce your issue. But I fixed it by turning filter off and using pixel snap.
Filter reads the color from four pixels with each lookup and blends them together. When using a single sprite the neighbouring pixel on the edge of the sprite gets clamped to the edge so you dont get borders, but on a spritesheet you read from an empty pixel on the sheet. This pixel gets blended with the one you want to read from resulting in a slightly darker pixel on all the borders.

Thanks @clayjohn @Zylann, reimporting the PNGs with "Filter" off fixed the issue for me. For reference, I didn't even notice the warning in the Godot UI.


1:1   warning  Resolve error: webpack with invalid interface loaded as resolver                 import/extensions
1:1   error    Resolve error: webpack with invalid interface loaded as resolver                 import/named
1:1   error    Resolve error: webpack with invalid interface loaded as resolver                 import/no-duplicates
1:1   error    Resolve error: webpack with invalid interface loaded as resolver                 import/order
1:1   error    Resolve error: webpack with invalid interface loaded as resolver                 import/no-self-import
1:1   error    Resolve error: webpack with invalid interface loaded as resolver                 import/no-cycle
1:1   error    Resolve error: webpack with invalid interface loaded as resolver                 import/no-unresolved
1:1   error    Resolve error: webpack with invalid interface loaded as resolver                 import/no-named-as-default
1:1   error    Resolve error: webpack with invalid interface loaded as resolver                 import/no-named-as-default-member
3:41  error    Unable to resolve path to module '../../../translations/ui-marc-authorities/en'  import/no-unresolved
/home/jenkins/workspace/io-org_ui-marc-authorities_PR-41/project/test/jest/jest-transformer.js
1:1  error  Resolve error: webpack with invalid interface loaded as resolver  import/order
1:1  error  Resolve error: webpack with invalid interface loaded as resolver  import/no-self-import
/home/jenkins/workspace/io-org_ui-marc-authorities_PR-41/project/test/jest/jest.setup.js
1:1  error  Resolve error: webpack with invalid interface loaded as resolver  import/no-unresolved
1:1  error  Resolve error: webpack with invalid interface loaded as resolver  import/no-duplicates
1:1  error  Resolve error: webpack with invalid interface loaded as resolver  import/no-self-import
1:1  error  Resolve error: webpack with invalid interface loaded as resolver  import/no-cycle
1:8  error  Unable to resolve path to module '@testing-library/jest-dom'      import/no-unresolved
/home/jenkins/workspace/io-org_ui-marc-authorities_PR-41/project/test/jest/setup-tests.js
1:1  warning  Resolve error: webpack with invalid interface loaded as resolver  import/extensions
1:1  error    Resolve error: webpack with invalid interface loaded as resolver  import/no-unresolved
1:1  error    Resolve error: webpack with invalid interface loaded as resolver  import/no-duplicates
1:1  error    Resolve error: webpack with invalid interface loaded as resolver  import/no-self-import
1:1  error    Resolve error: webpack with invalid interface loaded as resolver  import/no-cycle
2:8  error    Unable to resolve path to module './mock'                     import/no-unresolved
✖ 537 problems (471 errors, 66 warnings)
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

yarn run v1.22.15
$ eslint .
/home/jenkins/workspace/io-org_ui-marc-authorities_PR-41/project/src/components/SearchFilters/SearchFilters.js
53:6  warning  React Hook useCallback has a missing dependency: 'setFilters'. Either include it or remove the dependency array. If 'setFilters' changes too often, find the parent component that defines it and wrap that definition in useCallback  react-hooks/exhaustive-deps
/home/jenkins/workspace/io-org_ui-marc-authorities_PR-41/project/src/hooks/useSectionToggle.js
21:5  error  Expected blank line before this statement  padding-line-between-statements
/home/jenkins/workspace/io-org_ui-marc-authorities_PR-41/project/src/views/AuthoritiesSearch/AuthoritiesSearch.js
119:6  warning  React Hook useEffect has missing dependencies: 'history' and 'location.pathname'. Either include them or remove the dependency array  react-hooks/exhaustive-deps
✖ 3 problems (1 error, 2 warnings)
1 error and 0 warnings potentially fixable with the --fix option.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.


Interface validation rework

I've been reworking Grackle's interface validation code for schemas to more closely follow the algorithm outlined in the latest graphql spec and to cover some cases that the previous implementation did not (namely the former implementation did not deal with the case where a field is a subtype of that defined by the interface).  From this work a couple of design questions have arise that I'd be keen to get feedback on:

I'm finding a need to dealias type aliases and invoke subtyping logic, both of these are already sipported by the Schema type however presently the validation is invoked before the schema is populated and so I'm wondering whether I should move where the validation happens, change the way schemas are constructed or re-implement this logic just for validation purposes?
both objects and interfaces can implement interfaces but presently they lack a common supertype that exposes what interfaces they are attempting to implement, should I introduce one or adopt some other strategy?

I can't apologize enough for neglecting this PR.
Your observations were spot on and that's the approach I've taken in #426.


Incorrect/incompatible version recommended while installing bugsnag-cocoa via Swift Package Manager

Describe the bug
When using Swift Package Manager to install the bugsnag-cocoa library, XCode's default recommended exact version is 3.1.3 and default "up to major version" range is from versions 3.0.0 to 4.0.0. When you attempt to install this version (which is obviously outdated), it throws a package resolution error, as it cannot find a Package.swift file for that version.
Steps to reproduce

Follow installation instructions for SPM.

Here's an example screenshot of the default that pops up after I paste in the Github link that was supplied during the onboarding flow on the Bugsnag website.

Steps to fix
Switching to "exact version" and supplying the latest version tag I could find in the repository (6.16.6) fixed this issue.
Environment

iOS/tvOS/macOS version(s): Monterey 12.0.1
Swift version (if applicable):

Hi @harimohanraj you should find that Xcode now defaults to the latest 6.16.7 release by default 👍


Does EasyEdit support training on H800?

In order to train on H800, I change the version of torch to 2.1.0+cu121. The other dependencies are installed with the version specified in requirements.txt.
After I run my demo, which is adapted from the code in tutorial, I got this error:
Use device: cuda:0
2023-10-10 10:41:37,603 - easyeditor.editors.editor - INFO - Instantiating model
10/10/2023 10:41:37 - INFO - easyeditor.editors.editor -   Instantiating model
Loading checkpoint shards: 100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 7/7 [00:46<00:00,  6.67s/it]
Getting coarse neurons for each prompt...: 100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 1/1 [00:02<00:00,  2.49s/it]

484 coarse neurons found - refining
484 neurons remaining after refining

Before modification - groundtruth probability: tensor([2.2667e-07], device='cuda:0')
Argmax completion: `King`
Argmax prob: 0.17146547138690948
Traceback (most recent call last):
  File "/home/workspace/EasyEdit/demo-chatglm2.py", line 31, in <module>
    metrics, edited_model, _ = editor.edit(
  File "/home/workspace/EasyEdit/easyeditor/editors/editor.py", line 241, in edit
    edited_model, weights_copy = self.apply_algo(
  File "/home/workspace/EasyEdit/easyeditor/models/kn/kn_main.py", line 46, in apply_kn_to_model
    results_dict, unpatch_fn = kn.edit_knowledge(
  File "/home/workspace/EasyEdit/easyeditor/models/kn/knowledge_neurons/knowledge_neurons/knowledge_neurons.py", line 906, in edit_knowledge
    return self.modify_weights(
  File "/root/anaconda3/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/workspace/EasyEdit/easyeditor/models/kn/knowledge_neurons/knowledge_neurons/knowledge_neurons.py", line 831, in modify_weights
    output_ff_weights[:, position].detach().clone()
TypeError: 'Linear' object is not subscriptable

Should I change some part of the code to make it work?
The code is as follow:
import os
import logging

from easyeditor import BaseEditor
from easyeditor import KNHyperParams

PROJECT_PATH = os.path.dirname(os.path.abspath(__file__))
USE_DEVICE = f"cuda:0"
logging.info(f"Use device: {USE_DEVICE}")

prompts = ['Ray Charles, the',
            'Grant Hill is a professional',
            'The law in Ikaalinen declares the language'
            ]
ground_truth = ['piano',
                'basketball',
                'Finnish'
                ]
target_new = ['violin',
              'soccer',
              'Swedish'
              ]
subject = ['Ray Charles',
            'Grant Hill',
            'Ikaalinen'
            ]

hparams = KNHyperParams.from_hparams(os.path.join(PROJECT_PATH, 'hparams/KN/chatglm2-6b.yaml'))
editor = BaseEditor.from_hparams(hparams)
metrics, edited_model, _ = editor.edit(
    prompts=prompts,
    ground_truth=ground_truth,
    target_new=target_new,
    subject=subject,
    keep_original_weight=True
)

print(metrics)

print('*'*20)

from transformers import AutoTokenizer, AutoModel

# tokenizer = GPT2Tokenizer.from_pretrained('./hugging_cache/gpt2-xl')
tokenizer = AutoTokenizer.from_pretrained('/home/workspace/pretrain-model/chatglm/chatglm2-6b', trust_remote_code=True)
# tokenizer = AutoTokenizer.from_pretrained('/home/workspace/pretrain-model/THUDM/chatglm2-6b', trust_remote_code=True)
# tokenizer.pad_token_id = tokenizer.eos_token_id
tokenizer.padding_side='left'
generation_prompts = [
    "Ray Charles, the",
    "The law in Ikaalinen declares the language"
]

model = AutoModel.from_pretrained('/home/workspace/pretrain-model/chatglm/chatglm2-6b', trust_remote_code=True).to(USE_DEVICE)
# model = AutoModel.from_pretrained('/home/workspace/pretrain-model/THUDM/chatglm2-6b', trust_remote_code=True).to(USE_DEVICE)
batch = tokenizer(generation_prompts, return_tensors='pt', padding=True, max_length=30)

pre_edit_outputs = model.generate(
    input_ids=batch['input_ids'].to(USE_DEVICE),
    attention_mask=batch['attention_mask'].to(USE_DEVICE),
    max_length=10
)

post_edit_outputs = edited_model.generate(
    input_ids=batch['input_ids'].to(USE_DEVICE),
    attention_mask=batch['attention_mask'].to(USE_DEVICE),
    max_length=10
)

Thank you for your attention, EasyEdit currently supports chatglm2，If you have any other questions, please feel free to leave a message.

Thank you for your attention, EasyEdit currently supports chatglm2，If you have any other questions, please feel free to leave a message.

My question is, why would I get this error message when I run the codes that are just slightly modified from the tutorial codes?

We deeply apologize for the inconvenience regarding your situation with ChatGLM. Its architecture is quite unique; it is not the encoder-only structure found in Llama and GPT, but rather an encoder-decoder structure. Additionally, the coding style of ChatGLM is different from that of the prevailing large models, leading to bugs when trying to localize neurons. As of October 11th, we did not fully support ChatGLM. However, we have recently begun to fully support all fine-tuning methods for ChatGLM. If you encounter any issues while running the code, please feel free to contact us.

We have updated the code,EasyEdit now supports ChatGLM2. You can git pull  to retrieve the latest version. If you encounter any further issues, please feel free to contact us

Thank you for your attention, EasyEdit currently supports chatglm2，If you have any other questions, please feel free to leave a message.

My question is, why would I get this error message when I run the codes that are just slightly modified from the tutorial codes?
Traceback (most recent call last):
  File "/home/workspace/EasyEdit/demo-chatglm2.py", line 31, in <module>
    metrics, edited_model, _ = editor.edit(
  File "/home/workspace/EasyEdit/easyeditor/editors/editor.py", line 241, in edit
    edited_model, weights_copy = self.apply_algo(
  File "/home/workspace/EasyEdit/easyeditor/models/kn/kn_main.py", line 46, in apply_kn_to_model
    results_dict, unpatch_fn = kn.edit_knowledge(
  File "/home/workspace/EasyEdit/easyeditor/models/kn/knowledge_neurons/knowledge_neurons/knowledge_neurons.py", line 906, in edit_knowledge
    return self.modify_weights(
  File "/root/anaconda3/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/workspace/EasyEdit/easyeditor/models/kn/knowledge_neurons/knowledge_neurons/knowledge_neurons.py", line 831, in modify_weights
    output_ff_weights[:, position].detach().clone()
TypeError: 'Linear' object is not subscriptable

Hi buddy, you can pull the code and try again. If any problems, please contact us.

Have you solved your issue?


TECH : bump package version to 0.2.0, update documentation

Purpose of this PR

Bump version to 0.2.0
Update documentation with events

Checks

[ ] Documentation is very clear, even for a newcomer
[ ] All relevant usecases of are tested
[ ] These changes won't cause memory / CPU problems even if business grows by a factor of 100
[ ] It's ok if these changes go to production and then are rolled-back

Codecov Report

Merging #4 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master     #4   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           4      4
  Lines         126    126
=====================================
  Hits          126    126

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9f01f01...90c233a. Read the comment docs.


Quote Endpoint

This PR adds the Quote endpoint to the SDK, and includes all relevant documentation and tests.

Hey @richdynamix , just wanted to follow up to see if there was a timeline on merging PRs. I am utilizing your package for my senior project in college and am in need of this feature. If there is anything else you need from me to get this in please don't hesitate to ask!


USB CDC ACM UART driver's interrupt-driven API hangs when no host is connected

Describe the bug
If there is no host connected, either there never was or it has disconnected, the CDC ACM UART driver will stop accepting input when using the interrupt-driven API.
The CDC ACM UART does not do this when using the UART polling API.  If no host is connected, the polling API will drop transmitted data.  It is only the CDC ACM UART with the interrupt-driven API that has this behavior.
Other UART drivers, which do not even have the concept of a connected host, do not block if there is no remote device to receive data.  Any code written for a generic UART won't correctly handle this behavior of the CDC ACM UART.
To Reproduce
Steps to reproduce the behavior:

Use the CDC ACM USB sample with this simple patch applied to produce some output to the CDC ACM UART without needing a connected host to supply input to be echoed back.
0001-Add-output-to-cdc-acm-sample.patch.gz
Connect to the CDC ACM UART to pass the sample app's DTR check.
Disconnect to host.  E.g., close minicom.

After disconnecting, the next ping will enable tx on the uart.  The interrupt handler will be called once, call uart_fifo_fill() and not disable TX.  The interrupt handler should be called again, but it is not.  The app is basically hung in uart TX and will wait forever for the data to be sent to a USB host.
Expected behavior
The interrupt handler will continue to be called as long as it is enabled and more data is supplied to the FIFO.
Impact
Anything outputting data to a CDC ACM UART will hang if the USB host disconnects.  Other UARTs don't behave this way.
Logs and console output
[00:00:11.480,590] <inf> cdc_acm_echo: Sending ping to uart
[00:00:11.480,621] <dbg> cdc_acm_echo: interrupt_handler: Interrupt handler called
[00:00:11.480,651] <dbg> cdc_acm_echo: interrupt_handler: ringbuf -> tty fifo 6 bytes
[00:00:11.480,804] <dbg> cdc_acm_echo: interrupt_handler: Interrupt handler called
[00:00:11.480,834] <dbg> cdc_acm_echo: interrupt_handler: Ring buffer empty, disable TX IRQ
[00:00:12.480,926] <inf> cdc_acm_echo: Sending ping to uart
[00:00:12.480,957] <dbg> cdc_acm_echo: interrupt_handler: Interrupt handler called
[00:00:12.480,987] <dbg> cdc_acm_echo: interrupt_handler: ringbuf -> tty fifo 6 bytes
[00:00:13.481,140] <inf> cdc_acm_echo: Sending ping to uart
[00:00:14.481,231] <inf> cdc_acm_echo: Sending ping to uart

The 1st ping, at 11.480, has a USB host connected and completes.  The interrupt handler is called, data is sent to the UART, then the interrupt handler is called again and the ring buffer is now empty and TX is stopped.
The 2nd ping, at 12.480, is after the host disconnected.  The interrupt handler is called, data is sent to the UART, and then we hang.  The interrupt handler is never called again.
Environment (please complete the following information):

OS: Linux
Toolchain: Gcc  10.3.1
zephyr-v3.2.0-2637-gde1bd1fa04

Additional context
An obvious fix is to cdc_acm_fifo_fill() drop data immediately.  But consider how the interrupt handler in the sample will call fifo_fill in a while loop until either it runs out of data or the UART stops accepting more.  If the amount of data to send was very large or infinite, it could loop in the interrupt handler for a long time or forever.  This is generally bad.  On a real UART, eventually the hardware FIFO would fill and the irq handler would be throttled to the baud rate.
So it may be better to have cdc_acm_fifo_fill() add data to the queue with a 1ms delay, as is now done for the poll mode API, see PR #53003.  The interrupt handler will be throttled if it fills the ring buffer during that 1ms delay.  This also allows multiple calls to fifo_fill to be merged into a single USB URB, greatly increasing throughput if the data was provided in small chunks.

Other UART drivers, which do not even have the concept of a connected host, do not block if there is no remote device to receive data. Any code written for a generic UART won't correctly handle this behavior of the CDC ACM UART.

What if there is hardware flow control? Wouldn't plain UART block when the FIFO fills and the CTS is inactive?

So it may be better to have cdc_acm_fifo_fill() add data to the queue with a 1ms delay, as is now done for the poll mode API, see PR https://github.com/zephyrproject-rtos/zephyr/pull/53003. The interrupt handler will be throttled if it fills the ring buffer during that 1ms delay. This also allows multiple calls to fifo_fill to be merged into a single USB URB, greatly increasing throughput if the data was provided in small chunks.

Relying on the throttling sounds like bad application design, however delayable work items are inherently throttled by reschedule points (won't execute until scheduler is invoked). While k_work_schedule_for_queue documentation mentions that K_NO_WAIT is equivalent to k_work_submit_to_queue, there are scheduling differences between the two. I am not sure if the documentation is wrong or the implementation, of it is way too low-level difference (@andyross what do you think?). The difference boils down to the fact k_work_submit_to_queue is effectively submit_to_queue_locked followed by z_reschedule_unlocked while k_work_schedule_for_queue called with K_NO_WAIT is only submit_to_queue_locked.

What if there is hardware flow control? Wouldn't plain UART block when the FIFO fills and the CTS is inactive?

It would depend on hardware design.  Without pull-ups or pull-downs, which are not standard on RS-232 control lines, CTS would be floating.  So it would randomly transmit or not.
In cases of an external port with flow-control (which is very rare nowadays), usually the designer will have chosen to add a pull-up or pull-down to CTS.  It could be either way, based on what the design calls for.  A pull-down would cause the uart to always transmit with no external device connected.  A pull-up would halt transmission.
I haven't seen RTS/CTS used outside of on-board connections to a BT HCI UART for years now.  It would be by far the most common to see code using a UART to assume no control flow that will detect a connected host.

Relying on the throttling sounds like bad application design, however delayable work items are inherently throttled by

Suppose the FW wants to send a lot of data through the UART as fast as possible.  Most CPUs are now more than capable of saturating a UART at 115.2 kbaud or more.  So they write a loop in the interrupt callback that writes until uart_irq_tx_ready() returns false.  Which is after all how the examples do it.  Isn't this how one would normally write code to send data a UART as fast as it can accept it.
This works fine for any normal UART and CPU combination.  It doesn't seem like bad design to me.
The important thing is that the hardware has a limit to the rate it can accept data, and the CPU can meet this rate.
Even for USB ACM, which on e.g. nRF52840 can do about 3-4 Mbaud, the CPU is faster than the USB hardware.
But if the UART immediately drops data, then the hardware is now infinity fast.  Most of the uart examples or other users I see in Zephyr are not designed to handle the case of an infinitely fast uart.
Note that the throttling is not supposed to come from scheduling details.  IMHO, that would be too hard to keep working with any changes to scheduling details.
The USB CDC ACM driver should have a ring buffer of a limited size.  The size of the buffer multiplied by the 1 ms (or whatever) delay used produces a maximum throughput.

After disconnecting, the next ping will enable tx on the uart. The interrupt handler will be called once, call uart_fifo_fill() and not disable TX. The interrupt handler should be called again, but it is not. The app is basically hung in uart TX and will wait forever for the data to be sent to a USB host.

The only possible problem I see is "After disconnecting, ...The interrupt handler will be called once,".  Ideally, interrupt handler should not even be called once after disconnected event. This does not look like a bug, rather a discussion.
Can you please tell what in the description of UART driver API makes you think "The interrupt handler should be called again"? What do you mean by "hung in uart TX"?

On all other UART drivers, the interrupt handler will continue to be triggered as long as tx is enabled.  Does it not seem like the API is supposed to work this way, when all other drivers do it?
It is also not how the CDC ACM driver works when the polling API is used.
That the CDC ACM driver in interrupt mode behaves differently in all other UART drivers and also from itself in polling mode should be proof that the behavior is not correct.
There is no description of how the UART API works.  There are comments for individual functions.  The one for uart_irq_tx_enable() is "Enable TX interrupt in IER."  That's it.  So the only way to define how the API should work is to look at the example code and the drivers and see how they work.
And all code expects than when uart_irq_tx_enable() is called the irq callback function will continue to be triggered at the rate at which the UART consumes the data.

@tmon-nordic Can we acknowledge that this driver behaves different than other UART drivers?

@tmon-nordic Can we acknowledge that this driver behaves different than other UART drivers?

Well, it is operating on different "hardware" which than the other UART drivers. I don't quite agree on the fake throttling part. For the dropping data, please open PR fixing the issue so we can review it.

closing


ISPN-12004 JGroups INSERT_BEFORE

https://issues.redhat.com/browse/ISPN-12004
This should only land after we branch for 12.

Thanks @tristantarrant


New timezone token ZZ for +02:00 timezone format

This PR adds support for ZZ format token to output date with +02:00 format timezone.
There also added grunt test task for running tests in PhantomJS.
I haven't updated README.md.

:+1:


Style: Change Storage::SetReadOptions to Storage::DefaultScanOptions

Search before asking

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

Motivation
class Storage {
 public:
  explicit Storage(Config *config);

  void SetWriteOptions(const Config::RocksDB::WriteOptions &config);
  void SetReadOptions(rocksdb::ReadOptions &read_options);

  const rocksdb::WriteOptions &DefaultWriteOptions() { return write_opts_; }
};

Now kvrocks has SetWriteOptions and SetReadOptions. However, there syntax doesn't same. SetWriteOptions would set the Storage internal rocksdb::WriteOptions during intialize, and the detail option can be get by DefaultWriteOptions().
However, SetReadOptions only does some fixup when called:
void Storage::SetReadOptions(rocksdb::ReadOptions &read_options) {
  read_options.fill_cache = false;
  read_options.async_io = config_->rocks_db.read_options.async_io;
}

Would we create a DefaultScanOptions, and remove SetReadOptions for that ?
Solution
class Storage {
 public:
  explicit Storage(Config *config);

  void SetWriteOptions(const Config::RocksDB::WriteOptions &config);
-  void SetReadOptions(rocksdb::ReadOptions &read_options);

  const rocksdb::WriteOptions &DefaultWriteOptions() { return write_opts_; }
+ rocksdb::ReadOptions DefaultScanOptions();
};

Are you willing to submit a PR?

[X] I'm willing to submit a PR!

Sounds good to me


option to limit PSM output to defined q-value

it would be nice to be able to limit PSM output to 0.01 q-values and below, for example.

Would this just affect the PSM output to the TSV files or for everything (like the total number of PSM count in the results file)

This would only affect writing PSM output to TSV (and maybe other formats containing PSMs, like mzID and pepXML). all other calculations would be the same

done in #1327


Analysis Milestone: 1

Context
As a result of our analysis in #1 #2 #3, we have come to a point where we need guidance on some questions effecting the end product. This issue contains those questions and the context that surrounds them.
Open Questions
1. Is it possible to have more than one retail vault manager?
In other words, for a given and already accepted collateral type, is it safe to assume that all incoming new vault managers will be of type institutional or can EC choose to create a new retail vault manager?
I believe the answer to this question is most likely "yes". See #3
2. Can EC add new accounts to the whitelist for a particular vault manager?
Adding new accounts to an existing institutional vault manager can be done. However, it will (probably) go through EC so it will result having its own user flow. Do we want this?
3. Can EC remove accounts from the whitelist for a particular vault manager?
I am not sure how this can be done but I think this would make sense when we think about the possibility business relationships coming to an end with certain institutions. Should we work on solving this problem?
Splitting the work

Important !

When writing this section, we assume the answer to the question 1 above is "yes".
Currently all structure surrounding inter protocol assumes vault managers are indexed by their collateral type. This structure includes;

dapp-inter FE
@agoric/synthetic-chain
agoric-sdk - SwingSet test tools
agoric-sdk - Unit test tools
...and probably more stuff that I can't think of at the moment

This situation indicates that there's a considerable amount of effort that HAS to go into making sure we adjust all the effected parts are updated and works as expected. So we suggest we split the work into multiple iterations, see what each iteration includes below. Please note that all iteration will come with their e2e implementation. Meaning iteration one will have the FE changes relating to its features etc.
Iteration One: Enable only institutional vault managers first
The idea behind this iterations is to make sure we ship the intended features first (partially - retails not shipped yet at this point) and then focus on the complexity of enabling multiple retail vault managers. This way we can make sure we do most of the ground work for enabling multiple vault managers per one collateral type while avoiding the complexity that comes with ensuring our changes do not break rest of the system.
Sample FE flow for iteration one
sequenceDiagram
    participant user as institutionalUser
    participant int as dapp-inter
    participant vs as vStorage
    participant vf as vaultFactory

    user ->> int: connect keplr
    int ->> vs: query = list of institutional managers and the white-list
    vs -->> int: [manager0, manager1]
    Note over int, int: find which managers the user is whitelisted
    int ->> int: display retail AND institutional managers
    int ->> int: display all vaults belonging to the user
    int -->> user: page loaded
    user ->> int: Click "open vault" for institutional manager
    int ->> int: calculate prevOfferId
    Note over int,int: Inst users can send offers using continuing invitations
    Note over int,int: e.g {address}-manager-{managerIndex}-{?iteration}
    int ->> vf: Send vault offer
    Note over int, vf: offer = {invitationSpec = {source = continuing, prevOfferId, makeVaultInvitation}}
    vf -->> int: success

Iteration Two: Enable retails vault managers
At this point we will already be solved the complexity of enabling multiple vault managers for a collateral type so we can focus on making sure we support all the tooling around inter protocol vaults across the agoric-sdk.

@anilhelvaci re: 1 - yes. both. EC should be able to create a new retail or institutional vault type of an existing collateral type
re: 2 - yes
re: 3 - no
Re: enabling institutional vaults first then retail - this works. There is more business value in delivering institutional vaults than retail vaults


roman-numerals: Rewrite to return a Maybe.

Considering what was discussed in https://github.com/exercism/xhaskell/issues/194#issuecomment-235112332, we should probably rewrite roman-numerals to make it more idiomatic.
Currently, the reference json file only suggests test for values between 1 and 3000.
Should we really add new tests for:

Negative values?
Zero?
Numbers greater than 3000?

Or should we just change the return type to a Maybe, leaving to the user to choose how it will handle those cases?

All the description.md says is "There is no need to be able to convert numbers larger than about 3000.", has not mentioned lower limits. I assume we could test it.
Questions to ask:

If we change to Maybe and add a test for 0, would we expect it to be Nothing or Just ""?
If we change to Maybe and add a test for -1, would we expect it to be Nothing or Just "-I"?

I don't know if there is historical basis for the proposed Just answers so really I am making things up. If you asked me what I would pick, I'd pick Nothing for both of those, and also a Nothing for 4000.

Or should we just change the return type to a Maybe, leaving to the user to choose how it will handle those cases?

Interesting, we haven't done it before. It could be a worthy experiment. You may recall at #292 I wondered whether people would get confused by that, but maybe if we told them "it's up to you!" then people need not be confused.

If we change to Maybe and add a test for 0, would we expect it to be Nothing or Just ""?

For historical reasons, I would prefer to use Nothing. Nulla would probably be too much for the sake of correctness. :smile:

Interesting, we haven't done it before. It could be a worthy experiment. You may recall at #292 I wondered whether people would get confused by that, but maybe if we told them "it's up to you!" then people need not be confused.

I would favor this approach, using a note in HINTS.md.


Systemd Taking too long to Restart or Shutdown when using Display manager eg. lightdm

Hi, Recently Ive notice some Timeout in Systemd
It took me too long to Restart or Shutdown...
before i was running all auto start script at .xprofile
its ok but when U have implemented Something like
optimus-manager , where its managing also your script.
I found out that Intel Video card got stuck,
And it will took more than 1 minute before you can shutdown and restart....
So what I did was add this patch https://dwm.suckless.org/patches/cool_autostart/
so now i have this on config.h
static const char *const autostart[] = {
    "remaps", NULL,
    "setbg", NULL,
    "dwmblocks", NULL,
    "dunst", NULL,
    "xset r rate 300 50", NULL,
    "fusuma", NULL,
    "matebook-applet", NULL,
    "unclutter", NULL,
    "compton", NULL,
    "sh", "-c", "/usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1", NULL,
    "clipmenud", NULL,
    "optimus-manager-qt", NULL,
	NULL /* terminate */
};

Its good coz everytime you logout or leave dwm it just take care of stopping those background task/scripts.
Also on the patch make sure you dont remove the restart , or everytime you press super +f2 to refresh dwm it would just quit
void
quit(const Arg *arg)
{
	if(arg->i) restart = 1; // Maintain this line of code
    size_t i;

	/* kill child processes */
	for (i = 0; i < autostart_len; i++) {
		if (0 < autostart_pids[i]) {
			kill(autostart_pids[i], SIGTERM);
			waitpid(autostart_pids[i], NULL, 0);
		}
	}

	running = 0;
}

I just share this coz it might be useful to others if not useful for the maintainer

Ive put the wrong title lol,
changed it ...
Yeah this might be an issue for users who is not using display manager...
but as more and more users uses dwm
i dont think majority would use without a display manager,
me at first i didnt used it, but at later point in time
when i need display manager ive installed it...
the issue is when you have a background task running...
and systemd cant really shut it forcefully
Ive saw many issue and not one good fix to it...
but all issue is the same...
as a developer i narrow than the point where u can faced this issue....
and i found out that dwm has patch cool autostart
that patch not only auto start any script or background task
but it shut it off when you log out session or shutdown or reboot...
which systemd cant kill
Now if you think this is still non issue yeah, your right...
but the likelyhood that the users will face this issue is 90%
coz sooner or later you will uses a display manager
coz other packages required it...

@goldcoders well larbs doesn't use a display manager by default so I would still say this isn't a relevant issue


TypeLoadException when creating the AspNetCoreKernel

I'm trying to get this going, and I've followed your instructions (I think) pretty carefully. But I get this TypeLoadException:

System.TypeLoadException
HResult=0x80131522
Message=Method 'Resolve' in type 'Ninject.Web.AspNetCore.Components.ConstrainedGenericBindingResolver' from assembly 'Ninject.Web.AspNetCore, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc1f638e4e277871' does not have an implementation.
Source=Ninject.Web.AspNetCore
StackTrace:
at Ninject.Web.AspNetCore.AspNetCoreKernel.AddComponents()
at Ninject.KernelBase..ctor(IComponentContainer components, INinjectSettings settings, INinjectModule[] modules)
at Ninject.KernelBase..ctor(INinjectSettings settings, INinjectModule[] modules)
at Ninject.StandardKernel..ctor(INinjectSettings settings, INinjectModule[] modules)
at Ninject.Web.AspNetCore.AspNetCoreKernel..ctor(INinjectSettings settings, INinjectModule[] modules)
at TA.Starquest.Web.Program.CreateNinjectKernel() in Z:\repos\Tigra-Astronomy\TA.Starquest\TA.Starquest.Web\Program.cs:line 41
at Ninject.Web.Common.SelfHost.NinjectSelfHostBootstrapper.<>c__DisplayClass1_0.<.ctor>b__0()
at Ninject.Web.Common.Bootstrapper.Initialize(Func1 createKernelCallback)    at Ninject.Web.Common.SelfHost.NinjectSelfHostBootstrapper..ctor(Func1 createKernelCallback, Object[] selfHostConfigurations)
at TA.Starquest.Web.Program.Main(String[] args) in Z:\repos\Tigra-Astronomy\TA.Starquest\TA.Starquest.Web\Program.cs:line 29

The exception happens on this line:
        var kernel = new AspNetCoreKernel(settings);

in this method:
    private static IKernel CreateNinjectKernel()
    {
        var settings = new NinjectSettings();
        // Unfortunately, in .NET Core projects, referenced NuGet assemblies are not copied to the output directory
        // in a normal build which means that the automatic extension loading does not work _reliably_ and it is
        // much more reasonable to not rely on that and load everything explicitly.
        settings.LoadExtensions = false;

        var kernel = new AspNetCoreKernel(settings);

        kernel.Load(typeof(AspNetCoreHostConfiguration).Assembly);
        kernel.Load(new StarquestModule());

        return kernel;
    }

This is confusing, because I can see in the source code that method does have an implementation, so I'm not really sure what this even means. Any ideas?

Um, I think I figured it out. Looks like I somehow got a beta release of Ninject 4.0 installed, which of course breaks everything.
On that basis, I'm closing the issue.
P.S.. I would have used a discussion for this if they were enabled...... :)


Run tests in parallel on CI

closes #20

I had to use --oversubscribe because the CI runner doesn't seem to have more than 1 core. Though it shouldn't matter for the logic of the tests themselves.


ql-qlf: k6n10f: ql_dsp_simd: change naming scheme

RTLIL::Cell 'name' field contains path to source verilog file. Assigning two of those as the name of new DSP cell will likely cause generation of very long module names, especially when the path argument to 'read_verilog' is a long absolute path.
Long module names will propagate to long net names through 'autoname' pass and cause readability issues in post-synthesis verilog. This change prevents that.
Signed-off-by: Pawel Czarnecki<EMAIL_ADDRESS>

Hi @tpagarani, please have a look at this.


Bacalhau logs websocket error

When I try to look at the logs I get the following error. It did work one time on a bacalhau job and has not worked since.
bacalhau logs -f 472734f4-4615-40ec-8670-1c1ff41e0202
failed to read: websocket: close 1006 (abnormal closure): unexpected EOF%
Note this is pointing towards our requester node, which requires running the following to test directly
export BACALHAU_API_HOST=<IP_ADDRESS>

Looking at this.

This is also happening on Bacalhau public demonnet, it's not just you. Investigating the regression.

@thetechnocrat-dev I think this is because the server silently enforces that the Client ID of the job submitter and the Client ID of the logs requester must match. Can you try running this against one of your own jobs and see if you can get the logs back?
I can't remember why this protection is there. Either way, we need to fix up the error message, CLI validation, and documentation.

cc @rossjones

Annoyingly in trying to return an error, it exceeds the maximum length for control messages and triggers another error which is the 1006 you're seeing.  I need to refactor a little to add error messages as explicit message types, but will take a look in the morning.
Do we want the current behaviour of blocking access to the logs for users who didn't start the job, or is it something we should remove until we've a better view on how to control access to all of the commands?

Thanks that makes sense. We had jobs getting triggered from a Google Colab Notebook and I was trying to monitor the logs from my local machine, which of course has a different client ID.
When I run the log command from the Google Colab Notebook terminal it does stream the logs 🎉
The only downside from my perspective is that Google Colab requires the $9.99 a month Pro version to use the terminal feature. So, Google Colab users without a Pro version can't use the log streaming feature.

I've fixed the output of the error message, but will leave this issue open pending a decision on open access to logs or not.
My gut feel is that it's type of thing we might encapsulate within the job somehow to mark the job as open to anyone accessing the logs (or output, or describe) - but probably needs further thought.

I do like the idea of having the ability to set the logs access at the job level.

Authorisation is a wider issue we will be tackling over the next few months and the result of that work should be a general approach to authz. In that case, I actually think we should remove this auth requirement for logs for now, under the logic that it's getting in the way of people doing stuff, and then come back to it when we implement general auth.

Did you address this with the authorization work?

It will be addressed, but that work is in progress.

closing as noisy logs have been resolved, and auth is a wider topic addressed in multiple other issues


Shifted chat leads to desynced position for links in chat

As per the title, if using a hud type that shifts the chat, the point where you would have to click to use a link in chat is still in the unshifted position, which makes clicking them annoying at best.

I'll look into it once I've finished setting my new PC up^^
Give me 1 or 2 days.

This was slightly more than 1 or 2 days. Sorry for that.
I'm finishing up 3.6.4 right now (pure bugfix version) which contains a fix to this.


Spelling and style updates

count down to countdown
livestreamed to live-streamed
setup to set up
1 minutes to 1 minute
5-minute and 55-minute - added hyphens
Time capitalization consistency "am" to AM to match PM
minuntes to minutes

Combining into patch-108


[BUG] It takes a lot of time to execute, especially tailwindcss/classnames-order

Describe the bug
It takes a lot of time to execute Eslint.
And I use TIMING=1 to find the reason.
here is what I get
Rule                                   | Time (ms) | Relative
:--------------------------------------|----------:|--------:
tailwindcss/classnames-order           | 10097.373 |    50.0%
prettier/prettier                      |  2399.615 |    11.9%
tailwindcss/enforces-shorthand         |  2330.436 |    11.5%
import/no-cycle                        |  1044.403 |     5.2%
import/no-relative-packages            |   455.328 |     2.3%
import/order                           |   397.291 |     2.0%
tailwindcss/no-custom-classname        |   264.854 |     1.3%
import/no-extraneous-dependencies      |   257.201 |     1.3%
import/extensions                      |   253.208 |     1.3%
tailwindcss/no-contradicting-classname |   179.790 |     0.9%

It takes almost half of the time to run tailwindcss/classnames-order and about 10% of the time to run ailwindcss/enforces-shorthand
To Reproduce
Steps to reproduce the behavior:

On the terminal, run TIMING=1 npx eslint src
check the result

Expected behavior
I think the time sould not take so much.
Environment (please complete the following information):

OS: macOS 12.3.1
Softwares + version used:
node v16.14.0
npm v8.3.1

Additional context
Add any other context about the problem here.
eslint config file or live demo
{
    // ...
   "tailwindcss": {
      "callees": ["joinClassNames"],
      "config": "tailwind.config.js",
      "cssFiles": ["**/*.css"]
    }
}

Hi @ronny1020,
Parsing the css files is not very fast, can you use a narrower glob pattern than **/*.css for the cssFiles option ?
Also, I believe you need to avoid parsing the main css file generated by Tailwind CSS 🔁
Can you try this? Make sure to reboot your IDE too after editing the option, just to be sure.
If you need help for the glob pattern(s) please share the files/folders structure.
Let me know if it works 🥸

I only have one CSS file under src, which is src/index.css. It's just a small file.
I just tried {..., "cssFiles": ["src/index.css" ]}. Actually, I do feel it's a little bit faster. However, The result is similar.
Rule                                   | Time (ms) | Relative
:--------------------------------------|----------:|--------:
tailwindcss/classnames-order           | 10251.320 |    51.3%
prettier/prettier                      |  2327.852 |    11.6%
tailwindcss/enforces-shorthand         |  2271.232 |    11.4%
import/no-cycle                        |   993.849 |     5.0%
import/no-relative-packages            |   457.439 |     2.3%
import/order                           |   359.858 |     1.8%
import/no-extraneous-dependencies      |   275.121 |     1.4%
import/extensions                      |   247.653 |     1.2%
tailwindcss/no-custom-classname        |   196.434 |     1.0%
tailwindcss/no-contradicting-classname |   165.654 |     0.8%

Questions:

Could you share the content of that CSS files ?
What IDE are you using ? VSCode ?
Which version of eslint-plugin-tailwindcss are you on ?

Thanks

Thanks for your reply.

Here is the content of the src/index.css file.

@tailwind base;
@tailwind components;
@tailwind utilities;

:root {
  font-size: 12.8px;
}

@layer utilities {
  /* Hide arrows on number input for Chrome, Safari, Edge, Opera */
  input[type='number']::-webkit-inner-spin-button,
  input[type='number']::-webkit-outer-spin-button {
    -webkit-appearance: none;
    margin: 0;
  }

  /* Hide arrows on number input for Firefox */
  input[type='number'] {
    -moz-appearance: textfield;
  }
}

I use Vscode, the version is 1.66.2. The TIMING=1 npx eslint src is run on zsh, which version is 5.8.

the version of eslint-plugin-tailwindcss is 3.5.0, and the version of tailwindcss is 3.0.7

You should exclude this file from the plugin because it includes the @tailwind calls and no extra classnames.
The plugin determines the classnames based on the config and the CSS file option is just there to whitelist custom classnames...
so faster:
"cssFiles": []
or if you plan on using custom classnames in other css files:
"cssFiles": ["!src/index.css", "**/*.css"]

Thank you for all your assistance.
I tried "cssFiles": []. However, I think it makes no difference.
Rule                                   | Time (ms) | Relative
:--------------------------------------|----------:|--------:
tailwindcss/classnames-order           | 10078.333 |    49.9%
prettier/prettier                      |  2455.688 |    12.2%
tailwindcss/enforces-shorthand         |  2189.178 |    10.8%
import/no-cycle                        |  1075.851 |     5.3%
import/no-relative-packages            |   496.908 |     2.5%
import/order                           |   350.433 |     1.7%
import/extensions                      |   281.046 |     1.4%
import/no-extraneous-dependencies      |   275.882 |     1.4%
tailwindcss/no-custom-classname        |   200.517 |     1.0%
tailwindcss/no-contradicting-classname |   159.997 |     0.8%

Do you run the lint process via a npm script or npx script ?
If so, it may parse all your source files and not just the modified files...
I believe if you run it via the eslint extension, it will only run on opened files and it may reduce the process time...
How big is your source base ? Few hundred files, few thousands ?
Also, are you using the officialSorting option or not ?

Yes, It's much faster if I just parse the modified files. The eslint extension works fine.
However, our team will run Eslint during the ci/cd process, which would parse all my source files.
I know if there are a lot of files. Of cause, It would take a long time.
That's the reason I use TIMING=1, which will show the relative time per rule.
I don't use officialSorting. I had tried it, but it would take a longer time.
Thank you anyway.

After 3.5.2, it's much better, thanks for both @mpsijm and @francoismassart.

:100: @mpsijm 👍


Support for alternative tags executables

It would be nice to have support for language specific tags executables (For example jsctags). These executables do not always have flags with the same names as ctags. I suggest using something similar to what easytags uses:
let g:easytags_languages = {
\   'language': {
\     'cmd': 'jsctags',
\       'args': [],
\       'fileoutput_opt': '-f',
\       'stdout_opt': '-f-',
\       'recurse_flag': '-R'
\   }
\}

I just added proper support for project-type-specific tags executables (see 52a1f72819e08c4c16fb263b6d1d0c99983f339a), but not yet for specific arguments. I suppose for now you could get away with wrapping the "real" executable inside a script that forwards ctags-standard arguments into other arguments... I'm curious to hear about what other people think, I don't know much about what other tags programs there are out there, and what CLI they have.

My only exposure has been to the easy_tags plugin. I think the interface it provides is easy to use. However, I do not think it is necessary.
The only issue I can see with using a wrapper is handling reading the ctags.options file.

:+1:
I've been looking for a way to configure gutentags to work with vim-gutentags, but to no avail so far. The problem is that vim-gutentags doesn't support --options for option files, nor --append, and their support seems to be a hard-coded assumption of gutentags.
Also the failure is silent. As it's an example in the gutentags doc, I was expecting let g:gutentags_ctags_executable_ruby = 'ripper-tags' to just work, but it turned out it failed silently. Only a quick ps aux | grep tags let me know what command was rerunning, so I could rerun it and see what the error was:
➜ /bin/sh /Users/ejoubaud/.dotfiles/link/.vim/plugged/vim-gutentags/plat/unix/update_tags.sh -e ripper-tags -t /Users/ejoubaud/src/marketplace/tags -p /Users/ejoubaud/src/marketplace -s /Users/ejoubaud/src/marketplace/app/inputs/text_input.rb -o /Users/ejoubaud/.dotfiles/link/.vim/plugged/vim-gutentags/res/ctags.options
Locking tags file...
Removing references to: /Users/ejoubaud/src/marketplace/app/inputs/text_input.rb
grep -v /Users/ejoubaud/src/marketplace/app/inputs/text_input.rb "/Users/ejoubaud/src/marketplace/tags" > "/Users/ejoubaud/src/marketplace/tags.temp"
Running ctags
ripper-tags -f "/Users/ejoubaud/src/marketplace/tags.temp"  --options=/Users/ejoubaud/.dotfiles/link/.vim/plugged/vim-gutentags/res/ctags.options --append "/Users/ejoubaud/src/marketplace/app/inputs/text_input.rb" "/Users/ejoubaud/src/marketplace"
ripper-tags: invalid option: --options=/Users/ejoubaud/.dotfiles/link/.vim/plugged/vim-gutentags/res/ctags.options

Ok I've updated the help file with more information.
Since ripper-tags looks like a fairly popular plugin, if anybody made a wrapper to it to support --append and --options (I'm guess you could get away with making --options do nothing silently), you could post it somewhere and we could bundle it with Gutentags!


SLVS-3835 [serverless-init] Compute trace stats in serverless-init

What does this PR do?
Adds the _dd.compute_stats:1 tag so that trace metrics are created when using serverless-init.
Motivation
Sister PR of https://github.com/DataDog/logs-backend/pull/65802 (currently WIP), which will start to allow us to use second primary tags for AAS and Container Apps.
Example in staging where datacenter is the second primary tag.

Additional Notes
Unrelated to these changes, the the way serverless-init currently computes tags adds all tags like _dd.origin or _dd.compute_stats to metrics, logs and traces

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes
Updated unit tests

/merge


Brackets freezing on startup

Hello,
yesterday (after long "battle") I was forced to downgrade Brackets to version 1.1 because ver 1.3 freezes on startup and I can't even use it (ver 1.2 is very slow btw). It works a bit after clean install (but slow to use), but after a while it's the same and it's totally useless. I'm running Win 7 Ultimate 64bit and it used to work pretty well until some update. The navbar (File, Edit, etc) responds, but not doing anything, because the rest of Brackets not working (I can click on "Restart without plugins" but it's working eg.).
Thanks.

@Vaetas Can you try uninstalling Brackets and deleting the Brackets folder inside "%appdata%".
See if it helps you go through the startup with a fresh installation.
By the way, you can try Brackets v1.4 releasing in the coming week.

I tried reinstalling Brackets with deleting appdata, but after a while it started freezing again. I will wait for v1.4., thanks.

We are at 1.8 now, if you still have problems please open a new issue.


Remove invalid assets from assets_info API table

In fact the problem does not come from the assets_info table but from the issuances table.
Fixed here https://github.com/CounterpartyXCP/counterparty-core/pull/2212


⚠ Bofrost.lu has degraded performance

In b4ba94c, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2140 ms

Resolved: Bofrost.lu performance has improved in 4d1d742 after 40 minutes.


How to dump key as buffer?

I need to dump the key as a buffer, but currently there is only an API for dump as a string, the dumped string cannot be used for restore, an error of ERR DUMP payload version or checksum are wrong will be occured when restore.
I saw in this issue https://github.com/luin/ioredis/issues/222#issuecomment-167565186 that it seems to be possible to dump as buffer by api dumpBuffer, but I didn't find any code about this API in the code of this repository, whether there is a new alternative API?

Hey @cweijan 👋
It's supported and documented: http://luin.github.io/ioredis/classes/default.html#dumpBuffer

If you are using a version prior to v5.0.0, @types/ioredis may not provide a declaration for dumpBuffer, but the library does support it.

Thanks for the feedback, I do currently use ioredis4, I will try to migrate to ioredis5.

I migrated to ioredis5 and it works perfectly now, Thanks.


template refactoring + error page + refactor default DB names

refactor and move templates to a dedicated folder
added error page
update default DB names
some changes to templates to reflect project status
added credits to README.md

tested in staging, will deploy soon


Updated Fullname for Person

Fixes #218, but as specified in https://github.com/ucd-library/rp-ucd-harvest/issues/42

There are a couple issues I see (other than inconsistent formatting).  The code stops using rdfUtils.getFirstValue() which protects against array values (even if unintended in the spec).   You are hard coding in to the client only odr entries will have middle names?

Ok, I've updated for ghet getFirstValue, and yes, per https://github.com/ucd-library/rp-ucd-harvest/issues/42 only ODR names include middle names.


Audio2Motion Training Code Release

Hi, I was wondering when will the Audio2Motion training code be released. The previous comments said it'd be around 2024/06/01, would it be any time soon? Thank you!

check another repo of the author, just updated
https://github.com/yerfor/Real3DPortrait
[2024.07.02] We release the training code of the whole system, including audio-to-motion model...
The  Pre-trained audio-to-motion  model of these two repo have same size and config settings. I guess they are the same.

But Post-Net still not public


Add support for Java 7

Although Java 7 has been EOLed by Oracle, it is still in widespread use and might be worth supporting. However, Java 7 does not support obtaining method argument names by reflection. This would need to be implemented via some other means.

Just reviewed the parameter handling code. This would be a non-trivial change and probably isn't justified at the moment.


chore: add commit lint workflow and add some nodejs configuration

Hii @RobyCigar, can you explain about your commits and PR?
Is this to help the commit message or help the git flow?  Dia diceknya setiap mau commit

Ah sorry @algonacci I forgot to attach some description on the PR, as @NurfitraPujo said, husky + commit lint is to check the commit message whether it is conventional or not, if it's not conventional commit husky will automatically reject the commit.
And about the .nvmrc, this file can automatically change contributor's nodejs version if someone is using nvm
https://stackoverflow.com/questions/23556330/run-nvm-use-automatically-every-time-theres-a-nvmrc-file-on-the-directory