Cant transfer my hotspot. Cant cancel pending transfer(There is not)

When i try to transfer hotspot it says there is a pending transfer transaction to my address when i click it, nothing happens. This bug must be happen when i bought this hotspot. How can i solve this problem?
My address is : 14nVXtx1NnkZGxbeUjVCvF9jBmYCuz29QAvTyQxPsGmaBLw68mq
Hotspot Address : 112kcr1HS81qJ6KhzwP2D4j5ySGRRgqco5DN9EsuJUjVovXSX3sV
The previous seller(Sold to me) address : 13rxrypBWLWibndEhoym4sMgFVjF1eWgAvDbHmtUp75EVUneNb1
Successful transfer transaction hash : zj_kPMliUCy1WzxlsN-D5ttn-5ewg2U82FWxnQ7D7eE
I think there are 1 more transaction about this hotspot but me and the seller cannot see that transaction so we cant cancel it either. How can i get rid of it? ı have access both wallet i checked notifications on my wallet and there are 2 hotspot transfer notification, i click view transaction and then click complete transfer and it say "unable to complete transfer look like you sent or recieved hnt after the seller initiated....." for both notification. Its stucked.
Thank you !

Do you have a pending transaction hash for the transfer that you initiated? or are you not even getting there?

We know the issue. It’ll be fixed on Monday.

From: Marc Nijdam @.>
Sent: Sunday, November 28, 2021 7:38:29 AM
To: helium/hotspot-app @.>
Cc: Subscribed @.***>
Subject: Re: [helium/hotspot-app] Cant transfer my hotspot. Cant cancel pending transfer(There is not) (Issue #1123)
Do you have a pending transaction hash for the transfer that you initiated? or are you not even getting there?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/helium/hotspot-app/issues/1123#issuecomment-981105780, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AETPRSXNNMRAPVJECVRS4W3UOJEHLANCNFSM5I5F2MOQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Do you have a pending transaction hash for the transfer that you initiated? or are you not even getting there?

No i cant see the pending transaction hash. i just see this screenshot related to transaction and i cliked cancel like 500 times nothing happens. Also i can see 2 notifications on my wallet there are 2 transaction and i click complete transfer and it gives error and says contact with your seller to create a new transfer transaction but seller doesnt have this hotspot anymore i have it.

We know the issue. It’ll be fixed on Monday.
…
________________________________ From: Marc Nijdam @.> Sent: Sunday, November 28, 2021 7:38:29 AM To: helium/hotspot-app @.> Cc: Subscribed @.***> Subject: Re: [helium/hotspot-app] Cant transfer my hotspot. Cant cancel pending transfer(There is not) (Issue #1123) Do you have a pending transaction hash for the transfer that you initiated? or are you not even getting there? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#1123 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AETPRSXNNMRAPVJECVRS4W3UOJEHLANCNFSM5I5F2MOQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Im waiting with patience , thank you

By the way its been 18 days today.

it's been cleared. you should no longer see the pending message.

You are the best ty !


[F] Build mobile sub menu

Take MobileMenu out of global components, make into reusable layout component (for use in header and subnav)
Use named link object for TabNavs
Take TabLink styling out of TabNav component, make reusable (for use in TabNav and MobileSubNav)
Have a small existential crisis
Pass subnav data to PageHeader

Things we should consider doing:

[ ] Use one type for routes & links

Looks amazing. I don't know how you do it—that would have taken me days.
I didn't see an active state in the slide-out nav. Not a deal breaker for accepting the PR IMO, just something to mention.

👏 Thanks! A lot of the styling work was already done, it was just a matter of pulling pieces out and making them reusable. I'm not 100% happy with the solution, but when am I 100% happy with my code? 😉


Load large-size table from RS

Hi
I met a problem in loading a large-size(97G) table into my hdfs. I learned the code from Readme.md, as show in the following. If I set my spark conf as master = "local[2]", the program get error saying that 'Mkdirs failed to create temporary file in hdfs', but it works if I set master = "local[1]". Does it mean that I can not load large-size table using multiple threads? The error does not happen when I load a small-size table.
After I run successfully, I met the other problem. The program does not stop, seems the load process takes very long time. Is it possible to load in a compressed way?
Is there any good method to load large-size table into my server?
Read data from a table
df = sql_context.read
.format("com.databricks.spark.redshift")
.option("url", "jdbc:redshift://redshifthost:5439/database?user=username&password=pass")
.option("dbtable", "my_table")
.option("tempdir", "s3n://path/for/temp/data")
.load()
Thank you!

Can you post the stacktrace of the error? I'm not sure whether the "'Mkdirs failed to create temporary file in hdfs" message is a red-herring.

Closing as "cannot reproduce / underspecified for now." Please update and re-open when you have more information.


Reading from S3

I was trying to read LAZ files from S3, using s3fs and pylas' ability to read from streams:
import pylas
import s3fs

fs = s3fs.S3FileSystem()
las = pylas.open(fs.open('s3://bucketname/example.laz', 'rb'))

However, I get the following error:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/ubuntu/miniconda3/envs/pylas-env/lib/python3.6/site-packages/pylas/lib.py", line 34, in open_las
    return read_las_stream(source)
  File "/home/ubuntu/miniconda3/envs/pylas-env/lib/python3.6/site-packages/pylas/lib.py", line 90, in read_las_stream
    vlrs = vlr.VLRList.read_from(data_stream, num_to_read=header.number_of_vlr)
  File "/home/ubuntu/miniconda3/envs/pylas-env/lib/python3.6/site-packages/pylas/vlr.py", line 571, in read_from
    raw = RawVLR.read_from(data_stream)
  File "/home/ubuntu/miniconda3/envs/pylas-env/lib/python3.6/site-packages/pylas/vlr.py", line 61, in read_from
    data_stream.readinto(header)
AttributeError: 'S3File' object has no attribute 'readinto'

Looks like s3fs doesn't have an implementation of readinto. So, is there a recommended way to read from S3? Or, should I look into getting an implementation of readinto for S3File?

Ah, yes this is a change I made to try things out few days ago and encountered the same problem with s3fs but forgot to change it back.
I just pushed a commit that 'fix' this b724cb2177245d1799bfb853a1bf41a2fe7dc272

:+1: Works perfectly. Thanks for the quick fix!


[Submarine Spark Security] Different masking policies for different tables fail in the case of union

Hi, We ran into a problem with Submarine's Spark Security for Column Masking
For example,
select col_1, col_2 from tbl_1 union select col_3, col_4 from tbl_2
If masking policies for col_2 and col_4 are different, col_4 will use col_2's policy instead of its own
because col_4 is not in "plan.output"

I also encountered the same problem.

What is the expected output in this case?

Hi,I was also using spark security plugin to authorize SparkSQL,but when i execute command "show tables " or any sql command ,it report below errors:
22/01/11 10:23:26 WARN PolicyRefresher: cache file does not exist or not readable '/etc/ranger/sparkServer/policycache/sparkSql_sparkServer.json'
I have no idea why would this happen even though i configured a sparkService in hive in ranger?

The [Submarine Spark Security] functionality has been moved to the apache/incubator-kyuubi standalone project.


Bootstrap the very first GitSync CR

When controller first start, it should create the very first GitSync CR that watches the control repo.

After give it a more thought, it is cleaner to do a manual creation for the first GitSync CR instead of handling in the controller.

Close it as we will do a manual creation for bootstrap ATM, will re-open if we decide to switch dynamic creation.


Enhancement: spo term group get - Allow getting a tenant term group as well as a sitecollection term group on site-level

Currently spo term group get can only be run on the Global Termstore on tenant level.
This has two consequences:

You need the SPO administrator role to run this command.
You cannot use it on the sitecollection specific term store.

I propose fixing this.
Options

Option
Description

-u, --webUrl [webUrl]
If specified, allows you to get a term group from the tenant term store as well as the sitecollection specific term store. Defaults to the tenant admin site.

Remarks

To use this command without the --webUrl option you have to have permissions to access the tenant admin site.

When using the --webUrl option you can connect to the term store with limited permissions, and do not need the SharePoint Adminstrator role. You need be a site visitor or more. It allows you to get a term group from the tenant term store as well as a term group from the sitecollection term store.
Additional remarks
The webUrl option (if used) can just be swapped in instead of the currently used spoAdminUrl to achieve the desired result.

LGTM 👍

Can I work on this?

Certainly! 💪


Post / Publish to stash when running locally

I'm running a python script and want to post and publish to stash but that requires an oauth2 token for some reason. How to get around this?
Thanks

That endpoint requires an authenticated user session.
Follow the OAuth2 user authentication documentation.
On Mon, Aug 5, 2024 at 1:51 PM rbj @.***> wrote:

I'm running a python script and want to post and publish to stash but that
requires an oauth2 token for some reason. How to get around this?
Thanks
—
Reply to this email directly, view it on GitHub
https://github.com/wix-incubator/DeviantArt-API/issues/246, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYUW4QWMBT34KLHUTITMQ3ZP63SZAVCNFSM6AAAAABMAYGCOKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2DSMJUGUZDGNI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Karson Odette

That endpoint requires an authenticated user session. Follow the OAuth2 user authentication documentation.
…
On Mon, Aug 5, 2024 at 1:51 PM rbj @.> wrote: I'm running a python script and want to post and publish to stash but that requires an oauth2 token for some reason. How to get around this? Thanks — Reply to this email directly, view it on GitHub <#246>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAYUW4QWMBT34KLHUTITMQ3ZP63SZAVCNFSM6AAAAABMAYGCOKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2DSMJUGUZDGNI . You are receiving this because you are subscribed to this thread.Message ID: @.>
-- Karson Odette

I know.. that's why I asked...
Documentation says nothing...

From documentation:
Gaining OAuth 2.0 Credentials
In order to make API calls, you must first register your application (after logging in with your DeviantArt account)
After you've registered, you'll gain access to a pair of client_id and client_secret codes on the Applications & Keys page.
You can read the OAuth2 specification at http://tools.ietf.org/html/rfc6749 and the Bearer Token specification at http://tools.ietf.org/html/rfc6750

From documentation: Gaining OAuth 2.0 Credentials
In order to make API calls, you must first register your application (after logging in with your DeviantArt account)
After you've registered, you'll gain access to a pair of client_id and client_secret codes on the Applications & Keys page.
You can read the OAuth2 specification at http://tools.ietf.org/html/rfc6749 and the Bearer Token specification at http://tools.ietf.org/html/rfc6750

Did you even read my question? I'm running the script locally. The publish/post endpoint requires a redirect URL which is not possible when running locally...

use localhost


Validate message topics/tag before sending

Currently these fields are verified only by the receiver, which can lead to
sending a bad message that is rejected on the other end.

Codecov Report

Merging #365 (7e4a39c) into main (7065837) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Current head 7e4a39c differs from pull request most recent head 08d6388. Consider uploading reports for the commit 08d6388 to get more accurate results

@@            Coverage Diff            @@
##              main      #365   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          239       239
  Lines        12888     12893    +5
=========================================
+ Hits         12888     12893    +5

Impacted Files
Coverage Δ

pkg/fftypes/message.go
100.00% <100.00%> (ø)

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 7065837...08d6388. Read the comment docs.

Looks like on Fabric, we generate an invalid topic name for org broadcasts. Not sure why it was working before - perhaps we're not doing the receiver-side validation of messages when dealing with org broadcasts? Seems like that should be in effect for all messages, including system definitions.

After further investigation, there are actually a few layers of problems here.

We are ignoring message validation errors in many cases and persisting received messages that failed to validate
We are generating topic names for Fabric root org broadcasts which violate the 64-char max length (and could therefore overflow db columns)
Validation of FF names was extended to disallow UUIDs as names - but there are some cases (such as topic) where a UUID is acceptable, and other cases (such as token pools) where a UUID would cause confusion in a get-by-name-or-id scenario
Topics and tags are not being validated by the sender before sending a message (ie the original issue noted in this PR)

Pushed additional fixes for the issues noted above. See each commit message for more details.


add pyper-pip to rosdep/python.yaml

This Pull Request adds pyper provided in PyPI to rosdep/python.yaml.
pyper is a library for python which provides an interface between python and R language.

We've started using the -pip suffix for pip only packages. To allow future addition of upstream packaging w/o conflicting. Could you add that? And also comment here with a link to the package description for others reference?

@tfoote Thank you very much for reviewing! I updated my commit and information of PR.

+1


Load Balance Features Updated - #753 Follow-up

New Features and  API Documentation can be found: here.

@OCoutinho I put the review in a separate document here: https://docs.google.com/document/d/1gUGeTopZx_7pe0gemzgsUt2iOJQwLvRC4PxpD8lX3JY/edit?usp=sharing
Please feel free to comment in the doc. Overall I think the code structure looks good, but when I try to use REST APIs I got some issues.  Not sure if this is because I mis-use the APIs or what, but we need to work through those issues before we make a merge.
Thanks again for the contribution!

@QingWang0909  I will check the issues referred in the doc, I will also update the documentation with request  examples. I'll let you know when I got the issues corrected and ready to merge.

@OCoutinho any updates here? Let us know if you are ready for another review

@rizard Ryan, @OCoutinho and me actually keep in touch, and we're actually close on finish reviewing this one -- since I am occupied on working with BMF so I can't find time to finish testing it. Let me try to finish it tomorrow and post the update here.
@OCoutinho I was quite busy on last few months, sorry for taking long for reviewing!

I think it is ready to go. @OCoutinho thanks again for your great contribution! Do you have anything else to bring on before merging this PR? Please let us know. Otherwise, we can go ahead to merge it now.

No problem! All changes are in this PR, I think it is good to go :)

@OCoutinho Just merged : ) Thanks again for your kind contribution!


Improve the logging when loading handler code fails (#7757)

Pull request opened by the merge tool on behalf of #7757

Merged into branches iso6 in 65216b7b87314c063ac41819cddcd1a4f84e1e73


[FLINK-28503][docs][docs-zh] Fix invalid link in Python FAQ Document

What is the purpose of the change
Fix invalid link in Python FAQ Document
Brief change log

Replace invalid link with https://nightlies.apache.org/flink/flink-docs-release-1.12/downloads/setup-pyflink-virtual-env.sh

Verifying this change
Please make sure both new and modified tests in this PR follows the conventions defined in our code quality guide: https://flink.apache.org/contributing/code-style-and-quality-common.html#testing
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@HuangXingBo PTAL~


spyder error

Description
What steps will reproduce the problem?

Anaconda Navigator
Launch Spyder

What is the expected output? What do you see instead?
Please provide any additional information below
File "C:\Users\csy14\Anaconda3\envs\tensorflow\lib\site-packages\spyder\plugins_init_.py", line 511, in
toggled=lambda checked: self.toggle_view(checked),
File "C:\Users\csy14\Anaconda3\envs\tensorflow\lib\site-packages\spyder\plugins\ipythonconsole.py", line 713, in toggle_view
self.create_new_client(give_focus=False)
File "C:\Users\csy14\Anaconda3\envs\tensorflow\lib\site-packages\spyder\plugins\ipythonconsole.py", line 1009, in create_new_client
self.connect_client_to_kernel(client)
File "C:\Users\csy14\Anaconda3\envs\tensorflow\lib\site-packages\spyder\plugins\ipythonconsole.py", line 1035, in connect_client_to_kernel
stderr_file)
File "C:\Users\csy14\Anaconda3\envs\tensorflow\lib\site-packages\spyder\plugins\ipythonconsole.py", line 1440, in create_kernel_manager_and_kernel_client
kernel_manager.start_kernel(stderr=stderr)
File "C:\Users\csy14\Anaconda3\envs\tensorflow\lib\site-packages\jupyter_client\manager.py", line 257, in start_kernel
**kw)
File "C:\Users\csy14\Anaconda3\envs\tensorflow\lib\site-packages\jupyter_client\manager.py", line 203, in _launch_kernel
return launch_kernel(kernel_cmd, **kw)
File "C:\Users\csy14\Anaconda3\envs\tensorflow\lib\site-packages\jupyter_client\launc

The error message is cut off; please copy and paste the full thing. Also, to increase the chances this can be fixed and narrow down any problems with your installation, please provide at least some minimal information about the circumstances of the problem, including:
Is this your first time using anaconda on this machine? What anaconda and OS version? If not, has it worked before? What changed? Do you have all the dependencies installed in your tensorflow environment? If you can't get Spyder to launch to do so, provide conda list output. Anything you can think of that's unique/specific to your setup on this machine?

Closing because of lack of response.


Merge contexts across tabs

Merged processing of contexts is now restricted to contexts in a single tab. This gives an overhead for exercises with multiple tabs that could be eradicated if contexts could be merged across tabs.

Currently, if compilation fails, we try to compile each "execution unit" individually (this used to be per context, but since we have runs, it is per execution unit). However, with this change, an execution unit is potentially a complete test suite, rendering the fallback compilation mode moot.
Thus, should we try again by compiling each tab separately, or should we compile each context separately? The first is far more efficient, but the second one is "more" correct. A third alternative would be to first try compiling per tab, and then per context. If we want to make things complicated, we could even determine this per tab, e.g:

Try compiling everything together, if this fails:
Try compiling each tab. For each tab, if this fails:
Try compiling per context.

We could thus have a scenario where the first tab is compiled as a unit, after which tab 2 is compiled per context.


Data-type -> GeometryBase

Hi,
I think, there is no type for GeometryBase from the default list below.
How can I add a geometry-base type to this list?
Thank you :)

Added on https://github.com/compas-dev/compas-actions.ghpython_components/commit/ad34933f7202155d8b91667efd689d24ca076aca and available on the latest release

thank you


[FEATURE] Quiz Game App

Description
To add Quiz Game App made using React.js
User has to choose the correct option from the given options.
Screenshots

Additional information
No response

@panwar8279
Please assign the issue .

Hi @Ayushkumargit7 , I have assigned this task to you. Kindly complete within 2 days. Good luck


New PyPI release

We've made a number of changes to this library since releasing v0.1.1 on PyPI in December (1154e29). We should decide what work we want to do before releasing a new version (say, v0.2.0).
To start with, I'll create a draft PR containing some housekeeping changes on top of the current master branch for v0.2.0, and we can go from there.
Tentative checklist (feel free to add; discuss at start of collaborative session):

[x] Update REST scripts (#28)
[ ] Add Sphinx documentation (Angus working on setting up Sphinx; general documentation see #9)

[ ] readthedocs?

[ ] BertViz? (#11)
[x] Update README (#33)
[x] Target Python >=3.7, <=3.8 (#31, #34)
[x] Update PyTorch dependency version (#37)
[ ] Add DistilBERT support (#35)
[x] Fix pathing issue in transform_uci_drug.py (#41)
[x] Fix missing anaforatools dependency (#40)

Future:

Clean up existing code: remove unused imports, discuss code style (use Black? pre-commit hooks? GitHub Actions?)
Automated testing (codecov?)

Spinning off DistilBERT support for future release

Separating documentation/ReadTheDocs from the release, to add in patch releases as docstrings are fleshed out and added

Spinning off BertViz support for future release


Title: Enhancing Calendar UI

Which pre-existing JavaScript project will you be working on?
Calendar
Describe your enhancement/improvement
Actually, the calendar page  lacks an attractive look. I want to make some changes in it which are as follows:
Firstly , there should be subtle borders to make it good looking .Secondly, introducing a more dynamic color scheme for dates, months, and years can make the calendar more engaging and visually appealing. Also, a nice color combination will improve readability and visual appearance of the calendar. I'm enthusiastic about contributing to this enhancement and have the necessary skills.
Anything you need to say to the Reviewers
No response
Add any other context or relevant screenshots about the enhancement here.
No response

Can you please assign this to me as I am very interested in it.

@Changingthegame Thank you for providing your insight but it is not required as of now.


Initial attempt at setting up astro

I'm excited to see how Astro matches up to the other SSG's! Let me know if there's anything I need to fix, I tried to follow microsites's config for the most part - @natemoo-re strikes again working on another ssg :D
https://astro.build/chat for the discord

@jasikpark Thanks for this! I'm a big fan of what Astro is working on. Curious to see how it stacks up here.
I ran the dev (super small) job manually and it looks good. Going to merge and then run the larger jobs and see if it can handle them.

Awesome! I'm really excited to see how it stacks up now & how it improves in the coming months!

Hmm is Astro failing at the highest file count? Or is it just suddenly getting really magically efficient? 😅
https://cdn.discordapp.com/attachments/845430950191038464/891775632302821467/unknown.png

@jasikpark Yeah, seems to be having some issues. I created #74 with further details.


Trying to repair JS bundle

Changed directories line in package.json to source, as per microbundle documentation.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
266

Relevant Lines:
266

💛  - Coveralls


No Wrap Mode

I frequently run commands that have outputs which wrap text onto newlines (as we all do), the way we handle this today is the correct default behavior, but it would be neat to have the ability to active a "no wrap mode" where the arrow keys (h,j,k,l too) would scroll around the text. This would remove a very common pattern of rerunning the last command piped to less -S.
I understand this project is resistant to new features (for good reason), so I won't be offended if this is closed in the name of complexity. I do think this would be a relatively small complexity add if we are already thinking of adding modes as in #262, and #1017.

Besides the obvious complexity issues that might be out of scope of this project, this might conflict severely with the current way the storage buffer is designed.
Right now we store every cell in a 2D matrix that has a fixed number of cells in each row. So if you would want to have horizontal scrolling you'd need to have a pretty much infinite number of cells in each row. Otherwise there wouldn't be any place these could be stored. Then ofc there's the question how the current renderer would deal with that.
Even though this might not sound like a totally easy thing to implement, I can see this getting far more difficult than one might initially expect. And I'd say it's not unlikely that the abstractions that need to be added to make this work could slow down Alacritty even when the option is disabled.
I'm not trying to shoot down this proposal, just trying to give some context why adding this might be out of scope for the project. If someone else has an idea how to implement this without any of the issues I've mentioned, I'm open for this addition! :)

Isn't this similar to #591? If we're able to reflow on resize, this option would only need to reflow to the longest line known. And I think that reflow is somewhat important, as "losing" shortend lines is painful.

This is quite a bit different than #591, for scrolling we'd have to always store everything in infinitely long lines basically.
Reflowing properly instead of truncating is something Alacritty can definitely do when resizing, however reflowing when growing is not something that's easily done.


Twitter feed cut off on mobile

It does this both in portrait and landscape, in chrome and safari, on my phone

Kim

That annoying.  I tested on my non-iPhone phone and tablet and it doesn't get cut off.  We might need to debug it live sometime.

ok, happy to do so when you're up for it.

I'm not seeing this issue, @Antonialock  do you still see this?

I've made a tweak that I think might help, but I can't test it.  :-)

The issue didn't affect me. @Antonialock  could you look?

looks good on my phone now


Document All Flows Through the Application

It'd be great if we could document all flows through our application.
I have this in mind to be able to test the front-end properly. Something like Selenium could build these tests beautifully.
This would be great for a newcomer to get involved and better understand the project. Look at the wiki page for examples. @roryaronson you probably know this best at the moment.
https://github.com/openfarmcc/OpenFarm/wiki/User-Flows

I just did most of these, though there are plenty more I'm sure

Yeah, I've been adding them as I've been testing things on the front-end. Keep on discovering new ones.

I'm going to close this because it's never going to happen.


https://github.com/CyberReboot/poseidon/issues/232

Test creation: get_endpoint_next #232

Codecov Report

Merging #307 into master will increase coverage by 0.18%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #307      +/-   ##
==========================================
+ Coverage   76.03%   76.21%   +0.18%
==========================================
  Files          22       22
  Lines        1160     1169       +9
  Branches       91       91
==========================================
+ Hits          882      891       +9
  Misses        258      258
  Partials       20       20

Impacted Files
Coverage Δ

...bstraction/test_NorthBoundControllerAbstraction.py
98.88% <100%> (+0.12%)
:arrow_up:

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 68545e4...0469989. Read the comment docs.


Timeout exception when sending a subscription request after unsubscribing from a previous subscription

Steps to reproduce:

Make a first subscription request with Nostr.pool.subscribe and await for its returned Future to complete.
Close the first subscription with Nostr.pool.unsubscribe.
Make a second subscription request and watch things break. "No response from [relay URL]" log message is printed.

Observed in v0.6.1

Root cause is fairly obvious. Messages sent to relays are async operations whose Futures complete upon the relay acknowledging the message was processed. nostr_dart uses Command Results and EOSE notices as this acknowledgement however neither of these messages are returned in response to a "CLOSE" message which is sent by Nostr.pool.unsubscribe.


Remove built gem from source.

Fixes: The gemspec at /Users/mitch/railsdev/reactive-ruby/reactive-ruby.gemspec is not valid. The validation error was 'reactive-ruby-0.7.27 contains itself (reactive-ruby-0.7.27.gem), check your files list'

This issue was moved to reactrb/reactrb#75


[WIP]User roles

Describe your change in plain English.
Edit database to reflect new architecture. Re work models and fixtures to work with new db. Tests are not currently passing.
Link to the issue
#72

@jadekstewart3 Let me know if you want help on this PR! I can pair sometime if that might help.

@Thrillberg I would LOVE that! I'm available all day tomorrow!

Closing to rethink about how we can do this in the future <3


Export interface changed (jest)

Not sure what happened, but after upgrading to<EMAIL_ADDRESS>jest cant fully mock ioredis module
<EMAIL_ADDRESS>> jest.genMockFromModule('ioredis').Cluster
undefined

<EMAIL_ADDRESS>> jest.genMockFromModule('ioredis').Cluster
ƒ Cluster() {return mockConstructor.apply(this,arguments);}

@artur-ma You are correct. Sorry for didn't notice that. Created a fix!
@liaoliaots Thanks for the solution here.


After update, the value of the ignored field gorm:"-" in struct is not updated

Your Question
In gorm V1 , the value of the ignored field gorm:"-" will changed after update
type User struct {
	gorm.Model
	UserID         uint
	Age              uint         `gorm:"-"`
}

// Age Initialize to 0 , updates to 18 now.
db.Model(u).Updates(&User{Age: 18})

// log
u.Age = 0 before update.
u.Age = 18 after update.

In gorm V2 now , the value will not changed.
u.Age = 0 before update.
u.Age = 0 after update.

GORM Playground link :
https://github.com/go-gorm/playground/pull/480
Is this behavior change a bug ?
If not , is there a writing style to get results like V1 ?
Thanks so much !

The document you expected this should be explained

Expected answer

this question move to https://github.com/go-gorm/gorm/issues/5386


Expending chapter in the left menu doesn't expend the scrollable area

To reproduce the bug :

Go to a path where you can find an item with children and with items below it.
Click on the item to expand it

I don't get the issue here. Someone to clarify it?

Let us consider it as not reproducible or already fixed.


deadlock when trying to delete a machine

Steps to reproduce :

Create an invalid machine - you can use the following manifest that doesn't specify required credentials https://github.com/kubermatic/machine-controller/blob/master/examples/machine-digitalocean.yaml
Delete the previously created machine.
List machine resources

Result:
The machine was not deleted and the server keeps saying machine1 failed with: failed to get instance for machine machine1 after the delete got triggered
The only way of getting out of this situation is to manually edit the machine's spec and remove finalizers.
In general the described state exists because we add finalizers to a machine before creating a node because we want to prevent deletion of a machine resource.
As I can imagine that the call that requests a node can fail for many reasons, I think that this issue could help us track discussion on possible solutions to this issue.

Would it solve the problem when we add the finalizer directly after we successfully created the instance at the cloud provider?
Or we do a getInstance in the sync loop and add the finalizer as soon as we get an instance?
That way we would solve the problem when the Patch/Updated fails in the case above.

Would it solve the problem when we add the finalizer directly after we successfully created the instance at the cloud provider?

I think so, but then we introduce another issue - a user decided to delete Machine while we were making a call to "create an instance"

Noticed that issue some time ago as well. IMHO the approach of adding the finalizer after the first getInstance succeeded makes most sense.
If for whatever reason getInstance stops working later on (e.G. credentials got invalidated) then the user has to delete the finalizer manually to be able to delete the machine, but I think that is way better than risking to leave orphaned instances at the cloud provider.

From a user perspective orphaned instances at cloud provider mean losing some money.Thus setting finalizers as we do at the moment seems to be good and prevents exactly that scenario.
In situation like the one described we will make use of terminal errors (defined in the spec) to indicate erroRs that have to be resolved manually.


Update kaloom-member.svg

Logo update
Pre-submission checklist:
Please check each of these after submitting your pull request:

[ ] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[ ] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[ ] Have you picked the single best (existing) category for your project?
[ ] Does it follow the other guidelines from the new entries section?
[ ] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[ ] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[ ] Does your project/product name match the text on the logo?
[ ] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~15 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Deploy preview for landscape ready!
Built with commit 06b37e179256aafd9582efd6aa5e75a938fa06a6
https://deploy-preview-1977--landscape.netlify.app

Deploy preview for landscape ready!
Built with commit 06b37e179256aafd9582efd6aa5e75a938fa06a6
https://deploy-preview-1977--landscape.netlify.app


Dependency on old version of netrc gem

This project depends on a 2-year-old version of the netrc gem.
s.add_dependency('netrc', '~> 0.8')
There are other gems I would like to use that depend on newer versions. Is there a reason why the version needs to be so restricted?

~> is a pessimistic version constraint, so that dependency reads as '>= 0.8', '< 1.0'. The current latest version of netrc is 0.11.0, so there shouldn't be any issue with using that version.
Perhaps you wanted to remove your Gemfile.lock or run bundle update?
http://guides.rubygems.org/patterns/#pessimistic-version-constraint


Doc - Create a Architecture diagram for Cairo Foundry

Using tools such as excalidraw or lucidchart, create a comprehensive diagram explaining high-levels interactions occurring during a Cairo-Foundry run.
A good example would be Kakarot's architecture diagram:

Proposal:


Add missing publish cli flag

:tada: This PR is included in version 2.0.19 :tada:
The release is available on postcss-colorguard-v2.0.19
Your semantic-release bot :package::rocket:


 Unexpected server response: 401

Hello, i was working on my unifi box and i see that i am now getting this error from unifi2mqtt:   Unexpected server response: 401
im running unifi 7.3.83 with 2 sites. has anyone run into this? any suggestions on how to debug it?
thanks
Raptor

issue was the password, i think i used chars that were not allowed. closing the issue


Question : when exit fullscreen , the player still running on the background

When i enter the full screen mode , it works right .
But when i tap the button to exit full screen mode ,
the voice is still playing , but the original page`s controller has reload ，
and i cant stop the voice except shutdown this app .
here is my code :
class VideoApp {
  static produceVideo(BuildContext context, String url) {
    var videoPlayerController = new VideoPlayerController.network(url);
    ChewieController videoWidget = ChewieController(
        videoPlayerController: videoPlayerController,
        aspectRatio: 3 / 2,
        autoPlay: false,
        autoInitialize: true,
        allowFullScreen: true,
        placeholder: new Container(
          color: Colors.grey,
        ),
    );
    return Chewie(
      controller: videoWidget,
    );
  }
}

_video(String url) {
  Chewie produceVideo = VideoApp.produceVideo(context, url);
  _controller = produceVideo.controller;
  _chewie = produceVideo;
  return Container(
    child: produceVideo,
    color: Colors.white,
  );
}

Make sure that VideoPlayerController and ChewieController is used with one instance, so you should call dispose when use them for another video.

@override
void initState() {
var videoPlayerController = new VideoPlayerController.network(url);
ChewieController videoWidget = ChewieController(
videoPlayerController: videoPlayerController,
aspectRatio: 3 / 2,
autoPlay: false,
autoInitialize: true,
allowFullScreen: true,
placeholder: new Container(
color: Colors.grey,
),
);
}
That's it@MessiMercy

how did you fix it?

@MessiMercy your class should extend StatefulWidget. You can then setup your controller in initState. A full example can be found here:
https://github.com/brianegan/chewie/blob/master/example/lib/main.dart
Please comment if you still have issues.


VUEPRESS使用总结 DO NOT CLOSE THE ISSUSE

1，不支持

转换项目从docsify到vuepress，发现这个东西太难用了，或者说太复杂了，开发学习难度很大，同样优点也是有的表现能力强，但是门外汉用起来很头疼

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

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

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
t0thkr1s, @syedhali, @shaojunyang, @mybestcool, @cnydo, @dgrr, @ChaoticCrypto, @louiszgm, @rnyn, @eagle453, @ch3rub1m, @prestonhunter, @imjdl, @askiebaby, @bing2008, @killeder, @ttbowen, @kodycode, @black2996, @smileymi6, @theLeroy, @tomagoyaky, @robotparty, @kllmctrl, @hurskar, @xiaotiansky, @sunsetyan, @SushritPasupuleti, @adrianmejias, @ylxg12345, @reza35, @rikster, @beetlepig, @amazingandyyy, @damujen, @siemens84cn, @coollineme, @jack-siren, @zhenalexfan, @jiangkai886, @jeskol, @danielblair, @JackTWallace, @KhanShaheb34, @rblaine95, @enayet123, @mohrezani, @nikzaugg, @GordenChoy, @kaykybbboot, @shenzhigang, @franmaranchello, @mujinqi, @mabehiry, @Nahuelito, @HuaxuDuan, @bluenet13, @rjcnitsche, @liulxiang, @Coinward, @chenlexing, @congim, @yidahis, @siddarth7, @viren-proxy, @vinberm, @yinengy, @jaeminChung, @nicoboou, @abdllah2, @boboyuwu, @pmattos, @valinsky, @DeeLMind, @riwala, @cksmct, @AugustFirst, @GuiminChu, @x1957, @fengjw1, @rock-git, @lyledavids, @samwalls, @maczhao, @outdamud, @R-Y-M-R, @navvvidi, @klenty-rajesh, @AldousCheng, @coding364, @muhammad-hamdi, @JoinBelieve, @WahedSlet, @kouzhudong, @bogdanlungu, @vihaankapoor, @wanmaoxian, @mariokandut, @joaozarate


#5477 Print message after succesfully added classpath by magic command.

i don't think this is printing the status like it is stdout.  that means if you have a %classpath add, followed by a value that returns something, you should see the status from the classpath, and also the result.  i am seeing the status be lost.

the status should not be printed if the jar is already loaded.  if you run the same %classpath add twice, it should only print that it's loading the 1st time.


Fix scala 3 compiler warnings

Does scala 3 have fatal warnings available already? Lots of warnings haven't been implemented so far.

Oh, maybe not.  My only Scala 3 experience is maintaining libraries. :shrug:


'404 - Not Found' error when v3 bot attempts to list conversation members in Team channel

Version
v3.15
Describe the bug
The 'core-getConversationMembers' sample bot returns a '404 - Not Found' error when attempting call the Teams REST API in order to retrieve a list of conversation memebers.
Initial findings:
It looks like the 404 error is a result of an invalid request url due to percent encoding.
First the bot gets the ‘conversationId’ from the Teams channel, which is in this general format:
a:1quZ5Bs6Mbp…
The colon (invalid char for a url path) gets percent encoded resulting in this:
a%3A1quZ5Bs6Mbp…
It then uses that encoded ID as one of the path parameters for the REST call aimed at pulling down the conversation members list:
https://smba.trafficmanager.net/v3/conversations/a%3A1quZ5Bs6Mbp…/members
The encoding breaks the integrity of the conversationId and so no corresponding conversation can be found, resulting in a 404 error.
Two options for fixing this could be:

Reformat the conversationId generation mechanism to avoid inserting any reserved characterS
Send the conversationId in the request body instead of in the url.

To Reproduce
Steps to reproduce the behavior:

create bot from sample 'core-getConversationMembers'
Add bot to Teams channel
Enter text to initiate conversation
Observe error in console

Expected behavior
Expect bot to list conversation memebers
[bug]
[javascript]

Update: After further investigation, I found that rather than this error being related to url encoding it was in fact due to the base path of the service url being omitted.
I've fixed this by setting the base path before invoking the rest endpoint. Pull request for this change is here:
https://github.com/Microsoft/BotBuilder-Samples/pull/1426

Retested after fix merge and conversation members are now being listed as expected.


RockPiS - autostart of Satellite fails

Installed the satellite on an RockPiS.
Sadly the satellite can´t be started via service.
When starting with: "sudo satellite-update" - everything works fine and as expected.
After an reboot the satellite app isn´t starting.
root@rockpis:/home/rock# systemctl start satellite
Job for satellite.service failed because of unavailable resources or another system error.
See "systemctl status satellite.service" and "journalctl -xe" for details.

Result of: systemctl status satellite.service
● satellite.service - Bitfocus Companion Satellite
     Loaded: loaded (/etc/systemd/system/satellite.service; enabled; vendor preset: enabled)
     Active: failed (Result: resources) since Sun 2023-09-10 21:06:35 CEST; 1min 38s ago

Warning: some journal files were not opened due to insufficient permissions.

Result of: journalctl -xe
-- The unit satellite.service has entered the 'failed' state with result 'resources'.
Sep 10 21:10:44 rockpis systemd[1]: Failed to start Bitfocus Companion Satellite.
-- Subject: A start job for unit satellite.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit satellite.service has finished with a failure.
--
-- The job identifier is 1265 and the job result is failed.

Can you rerun those commands with sudo, that output does not show any information

rock@rockpis:~$ sudo systemctl start satellite
[sudo] password for rock:
Job for satellite.service failed because of unavailable resources or another system error.
See "systemctl status satellite.service" and "journalctl -xe" for details.

rock@rockpis:~$ sudo systemctl status satellite.service
● satellite.service - Bitfocus Companion Satellite
     Loaded: loaded (/etc/systemd/system/satellite.service; enabled; vendor preset: enabled)
     Active: failed (Result: resources) since Wed 2023-09-20 17:51:15 CEST; 48s ago

Sep 20 17:51:15 rockpis systemd[1]: satellite.service: Scheduled restart job, restart counter is at 5.
Sep 20 17:51:15 rockpis systemd[1]: Stopped Bitfocus Companion Satellite.
Sep 20 17:51:15 rockpis systemd[1]: satellite.service: Start request repeated too quickly.
Sep 20 17:51:15 rockpis systemd[1]: satellite.service: Failed with result 'resources'.
Sep 20 17:51:15 rockpis systemd[1]: Failed to start Bitfocus Companion Satellite.

rock@rockpis:~$ sudo systemctl status satellite.service
● satellite.service - Bitfocus Companion Satellite
     Loaded: loaded (/etc/systemd/system/satellite.service; enabled; vendor preset: enabled)
     Active: failed (Result: resources) since Wed 2023-09-20 17:51:15 CEST; 48s ago

Sep 20 17:51:15 rockpis systemd[1]: satellite.service: Scheduled restart job, restart counter is at 5.
Sep 20 17:51:15 rockpis systemd[1]: Stopped Bitfocus Companion Satellite.
Sep 20 17:51:15 rockpis systemd[1]: satellite.service: Start request repeated too quickly.
Sep 20 17:51:15 rockpis systemd[1]: satellite.service: Failed with result 'resources'.
Sep 20 17:51:15 rockpis systemd[1]: Failed to start Bitfocus Companion Satellite.
rock@rockpis:~$ sudo journalctl -xe
-- Automatic restarting of the unit satellite.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Sep 20 17:51:15 rockpis systemd[1]: Stopped Bitfocus Companion Satellite.
-- Subject: A stop job for unit satellite.service has finished
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A stop job for unit satellite.service has finished.
--
-- The job identifier is 898 and the job result is done.
Sep 20 17:51:15 rockpis systemd[1]: satellite.service: Start request repeated too quickly.
Sep 20 17:51:15 rockpis systemd[1]: satellite.service: Failed with result 'resources'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit satellite.service has entered the 'failed' state with result 'resources'.
Sep 20 17:51:15 rockpis systemd[1]: Failed to start Bitfocus Companion Satellite.
-- Subject: A start job for unit satellite.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit satellite.service has finished with a failure.
--
-- The job identifier is 898 and the job result is failed.
Sep 20 17:52:03 rockpis sudo[386]:     rock : TTY=pts/0 ; PWD=/home/rock ; USER=root ; COMMAND=/usr/bin/systemctl status satellite.service
Sep 20 17:52:03 rockpis sudo[386]: pam_env(sudo:session): Unable to open env file: /etc/default/locale: No such file or directory
Sep 20 17:52:03 rockpis sudo[386]: pam_unix(sudo:session): session opened for user root by rock(uid=0)
Sep 20 17:52:05 rockpis sudo[386]: pam_unix(sudo:session): session closed for user root
Sep 20 17:52:45 rockpis sudo[389]:     rock : TTY=pts/0 ; PWD=/home/rock ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Sep 20 17:52:45 rockpis sudo[389]: pam_env(sudo:session): Unable to open env file: /etc/default/locale: No such file or directory
Sep 20 17:52:45 rockpis sudo[389]: pam_unix(sudo:session): session opened for user root by rock(uid=0)

After an evening of experimenting, I finally understand what is happening. I have found a few issues when using rockpis_ubuntu_focal_server_arm64_20210924_0418-gpt.img:

The ubuntu image is only mounting /boot on demand, and the systemd unit for companion is not triggering this mount causing it to fail as /boot/satellite-config does not exist
The linux kernel in the image is so old that it causes segfaults when using an original 15 key streamdeck.
The image is also very behind on updates and is a couple of releases of ubuntu behind.
As you already found, the image has a broken apt key, causing some apt commands to fail until the missing key is imported

I would advise using the images produced by armbian. https://www.armbian.com/rockpi-s/ I don't know for certain how stable they are, but I don't see why they wouldnt be. Plus they are an up to date image, and are closer to a standard debian os so should generally be simpler to work with.

I've just double checked, and with the latest armbian image, I simply had to follow the prompts to change the default passwords, and then run the one line installer and after waiting for it to run, then rebooting and it works fine.

Downloaded Armbian 23.8 and flashed it. After that running the one line installer which comes back with an error...
root@rockpi-s:~# curl https://raw.githubusercontent.com/bitfocus/companion-satellite/master/pi-image/install.sh | sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1908  100  1908    0     0   1828      0  0:00:01  0:00:01 --:--:--  1831
This will attempt to install Companion Satellite as a system service on this device.
It is designed to be run on headless servers, but can be used on desktop machines if you are happy to not have the tray icon.
A user called 'satellite' will be created to run the service, and various scripts will be installed to manage the service
Adding user `satellite' ...
Adding new group `satellite' (1001) ...
Adding new user `satellite' (1001) with group `satellite (1001)' ...
Creating home directory `/home/satellite' ...
Copying files from `/etc/skel' ...
Adding new user `satellite' to supplemental / extra groups `users' ...
Adding user `satellite' to group `users' ...
 Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
git is already the newest version (1:2.39.2-1.1).
zip is already the newest version (3.0-13).
zip set to manually installed.
unzip is already the newest version (6.0-28).
curl is already the newest version (7.88.1-10+deb12u1).
nano is already the newest version (7.2-1).
The following additional packages will be installed:
  cmake-data fontconfig-config fonts-dejavu-core libarchive13 libfreetype6
  libjsoncpp25 librhash0 libuv1
Suggested packages:
  cmake-doc cmake-format elpa-cmake-mode ninja-build lrzip
Recommended packages:
  libusb-1.0-doc
The following NEW packages will be installed:
  cmake cmake-data fontconfig-config fonts-dejavu-core libarchive13
  libfontconfig1 libfreetype6 libjsoncpp25 librhash0 libudev-dev
  libusb-1.0-0-dev libuv1
0 upgraded, 12 newly installed, 0 to remove and 5 not upgraded.
Need to get 11.8 MB of archives.
After this operation, 43.6 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bookworm/main arm64 libarchive13 arm64 3.6.2-1 [316 kB]
Get:2 http://deb.debian.org/debian bookworm/main arm64 libjsoncpp25 arm64 1.9.5-4 [72.3 kB]
Get:3 http://deb.debian.org/debian bookworm/main arm64 librhash0 arm64 1.4.3-3 [131 kB]
Get:4 http://deb.debian.org/debian bookworm/main arm64 libuv1 arm64 1.44.2-1 [133 kB]
Get:5 http://deb.debian.org/debian bookworm/main arm64 cmake-data all 3.25.1-1 [2,026 kB]
Get:6 http://deb.debian.org/debian bookworm/main arm64 cmake arm64 3.25.1-1 [6,806 kB]
Get:7 http://deb.debian.org/debian bookworm/main arm64 fonts-dejavu-core all 2.37-6 [1,068 kB]
Get:8 http://deb.debian.org/debian bookworm/main arm64 fontconfig-config arm64 2.14.1-4 [315 kB]
Get:9 http://deb.debian.org/debian bookworm/main arm64 libfreetype6 arm64 2.12.1+dfsg-5 [369 kB]
Get:10 http://deb.debian.org/debian bookworm/main arm64 libfontconfig1 arm64 2.14.1-4 [381 kB]
Get:11 http://deb.debian.org/debian bookworm/main arm64 libudev-dev arm64 252.12-1~deb12u1 [51.8 kB]
Get:12 http://deb.debian.org/debian bookworm/main arm64 libusb-1.0-0-dev arm64 2:1.0.26-1 [83.0 kB]
Fetched 11.8 MB in 2s (4,991 kB/s)
Preconfiguring packages ...
Selecting previously unselected package libarchive13:arm64.
(Reading database ... 40755 files and directories currently installed.)
Preparing to unpack .../00-libarchive13_3.6.2-1_arm64.deb ...
Unpacking libarchive13:arm64 (3.6.2-1) ...
Selecting previously unselected package libjsoncpp25:arm64.
Preparing to unpack .../01-libjsoncpp25_1.9.5-4_arm64.deb ...
Unpacking libjsoncpp25:arm64 (1.9.5-4) ...
Selecting previously unselected package librhash0:arm64.
Preparing to unpack .../02-librhash0_1.4.3-3_arm64.deb ...
Unpacking librhash0:arm64 (1.4.3-3) ...
Selecting previously unselected package libuv1:arm64.
Preparing to unpack .../03-libuv1_1.44.2-1_arm64.deb ...
Unpacking libuv1:arm64 (1.44.2-1) ...
Selecting previously unselected package cmake-data.
Preparing to unpack .../04-cmake-data_3.25.1-1_all.deb ...
Unpacking cmake-data (3.25.1-1) ...
Selecting previously unselected package cmake.
Preparing to unpack .../05-cmake_3.25.1-1_arm64.deb ...
Unpacking cmake (3.25.1-1) ...
Selecting previously unselected package fonts-dejavu-core.
Preparing to unpack .../06-fonts-dejavu-core_2.37-6_all.deb ...
Unpacking fonts-dejavu-core (2.37-6) ...
Selecting previously unselected package fontconfig-config.
Preparing to unpack .../07-fontconfig-config_2.14.1-4_arm64.deb ...
Unpacking fontconfig-config (2.14.1-4) ...
Selecting previously unselected package libfreetype6:arm64.
Preparing to unpack .../08-libfreetype6_2.12.1+dfsg-5_arm64.deb ...
Unpacking libfreetype6:arm64 (2.12.1+dfsg-5) ...
Selecting previously unselected package libfontconfig1:arm64.
Preparing to unpack .../09-libfontconfig1_2.14.1-4_arm64.deb ...
Unpacking libfontconfig1:arm64 (2.14.1-4) ...
Selecting previously unselected package libudev-dev:arm64.
Preparing to unpack .../10-libudev-dev_252.12-1~deb12u1_arm64.deb ...
Unpacking libudev-dev:arm64 (252.12-1~deb12u1) ...
Selecting previously unselected package libusb-1.0-0-dev:arm64.
Preparing to unpack .../11-libusb-1.0-0-dev_2%3a1.0.26-1_arm64.deb ...
Unpacking libusb-1.0-0-dev:arm64 (2:1.0.26-1) ...
Setting up libarchive13:arm64 (3.6.2-1) ...
Setting up libusb-1.0-0-dev:arm64 (2:1.0.26-1) ...
Setting up libuv1:arm64 (1.44.2-1) ...
Setting up libfreetype6:arm64 (2.12.1+dfsg-5) ...
Setting up libjsoncpp25:arm64 (1.9.5-4) ...
Setting up fonts-dejavu-core (2.37-6) ...
Setting up libudev-dev:arm64 (252.12-1~deb12u1) ...
Setting up librhash0:arm64 (1.4.3-3) ...
Setting up cmake-data (3.25.1-1) ...
Setting up fontconfig-config (2.14.1-4) ...
Setting up cmake (3.25.1-1) ...
Processing triggers for libc-bin (2.36-9+deb12u1) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for sgml-base (1.31) ...
Setting up libfontconfig1:arm64 (2.14.1-4) ...
Processing triggers for libc-bin (2.36-9+deb12u1) ...
Checking dependencies for the installation script...
Checking availability of curl... OK!
Checking availability of unzip... OK!
Downloading https://github.com/Schniz/fnm/releases/latest/download/fnm-arm64.zip...
######################################################################## 100.0%
Installing for Bash. Appending the following to /root/.bashrc:

  # fnm
  export PATH="/opt/fnm:$PATH"
  eval "`fnm env`"

In order to apply the changes, open a new terminal or run the following command:

  source /root/.bashrc
Cloning into '/usr/local/src/companion-satellite'...
remote: Enumerating objects: 1320, done.
remote: Counting objects: 100% (499/499), done.
remote: Compressing objects: 100% (111/111), done.
remote: Total 1320 (delta 459), reused 390 (delta 388), pack-reused 821
Receiving objects: 100% (1320/1320), 2.57 MiB | 4.26 MiB/s, done.
Resolving deltas: 100% (816/816), done.
Installing Node v18.16.0 (arm64)
Using Node v18.16.0
npm ERR! code ENETUNREACH
npm ERR! syscall connect
npm ERR! errno ENETUNREACH
npm ERR! request to https://registry.npmjs.org/yarn failed, reason: connect ENETUNREACH 2606:4700::6810:23:443

npm ERR!
Installing Node v18.16.0 (arm64)
Using Node v18.16.0

added 1 package in 11s
npm notice
npm notice New major version of npm available! 9.5.1 -> 10.1.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.1.0
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
yarn config v1.22.19
success Set "network-timeout" to "100000".
Done in 0.73s.
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
warning Pattern ["node-hid@npm:@julusian/hid@2.5.0-3","node-hid@^2.1.1","node-hid<EMAIL_ADDRESS>is trying to unpack in the same destination "/usr/local/share/.cache/yarn/v6/npm-node-hid-2.5.0-3-4d0a1aabef8a47b79a3ccdb30fc5b53e8618f5e1-integrity/node_modules/node-hid" as pattern ["node-hid@npm<EMAIL_ADDRESS>This could result in non-deterministic behavior, skipping.
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
[4/5] Linking dependencies...
[5/5] Building fresh packages...
[6/7] ⠈ electron
[-/7] ⠈ waiting...
[-/7] ⠁ waiting...
[-/7] ⠁ waiting...
./pi-image/update.sh: line 20:  4411 Killed                  yarn

RockPi is connected via LAN to my router...  I don´t get it why it´s failing. It has an IP and can connect to the internet.

That looks like it ran out of memory.. Do you have a 256mb memory model?
I should be able to provide a fix for that

Finally it´s working....
Used the Minimal https://redirect.armbian.com/rockpi-s/Bookworm_current_minimal instead of the large one.
Had to run: sysctl net.ipv6.conf.all.disable_ipv6=1 - without that it hung up on Node install everytime.
After that, running your install script: curl https://raw.githubusercontent.com/bitfocus/companion-satellite/master/pi-image/install.sh | sh
And voilá! It´s up and running, even after reboot.
Thanks for all your help!
Two short questions:
Would it be possible to show the IP of the board and the IP of the Companion on the screen, when it has not connection to companion? That would be really helpful :-)

Ill add some notes to the readme about this image recommendation.

Would it be possible to show the IP of the board and the IP of the Companion it´s trying to reach on the screen, when it has not connection to Companion?
It already does do that

Would it be possible to show the IP of the board and the IP of the Companion it´s trying to reach on the screen, when it has not connection to Companion?
It already does do that
Whoops, missed that. Wasn´t there in the old versions.

Did an reinstall, now the script hangs up on yarn:
root@rockpi-s:~# curl https://raw.githubusercontent.com/bitfocus/companion-satellite/master/pi-image/install.sh | sh   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100  1908  100  1908    0     0   2486      0 --:--:-- --:--:-- --:--:--  2487 This will attempt to install Companion Satellite as a system service on this device. It is designed to be run on headless servers, but can be used on desktop machines if you are happy to not have the tray icon. A user called 'satellite' will be created to run the service, and various scripts will be installed to manage the service Adding user satellite' ...
Adding new group satellite' (1001) ... Adding new user satellite' (1001) with group satellite (1001)' ... Creating home directory /home/satellite' ...
Copying files from /etc/skel' ... Adding new user satellite' to supplemental / extra groups users' ... Adding user satellite' to group `users' ...
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
Hit:3 http://deb.debian.org/debian bookworm-backports InRelease
Hit:4 http://security.debian.org bookworm-security InRelease
Hit:5 http://mirrors.xtom.de/armbian bookworm InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
curl is already the newest version (7.88.1-10+deb12u5).
libfontconfig1 is already the newest version (2.14.1-4).
nano is already the newest version (7.2-1).
The following additional packages will be installed:
cmake-data git-man libarchive13 liberror-perl libjsoncpp25 libpam-systemd
librhash0 libsystemd-shared libsystemd0 libudev1 libxml2 systemd
systemd-sysv udev
Suggested packages:
cmake-doc cmake-format elpa-cmake-mode ninja-build gettext-base
git-daemon-run | git-daemon-sysvinit git-doc git-email git-gui gitk gitweb
git-cvs git-mediawiki git-svn lrzip systemd-container systemd-homed
systemd-userdbd systemd-boot systemd-resolved libqrencode4
libtss2-esys-3.0.2-0 libtss2-mu0 libtss2-rc0
Recommended packages:
gcc make patch libusb-1.0-doc libnss-systemd
The following NEW packages will be installed:
cmake cmake-data git git-man libarchive13 liberror-perl libjsoncpp25
librhash0 libudev-dev libusb-1.0-0-dev libxml2 unzip zip
The following packages will be upgraded:
libpam-systemd libsystemd-shared libsystemd0 libudev1 systemd systemd-sysv
udev
7 upgraded, 13 newly installed, 0 to remove and 11 not upgraded.
Need to get 26.2 MB of archives.
After this operation, 89.4 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bookworm/main arm64 systemd-sysv arm64 252.19-1~deb12u1 [41.8 kB]
Get:2 http://deb.debian.org/debian bookworm/main arm64 libpam-systemd arm64 252.19-1~deb12u1 [208 kB]
Get:3 http://deb.debian.org/debian bookworm/main arm64 systemd arm64 252.19-1~deb12u1 [2,828 kB]
Get:4 http://deb.debian.org/debian bookworm/main arm64 libsystemd-shared arm64 252.19-1~deb12u1 [1,506 kB]
Get:5 http://deb.debian.org/debian bookworm/main arm64 libsystemd0 arm64 252.19-1~deb12u1 [307 kB]
Get:6 http://deb.debian.org/debian bookworm/main arm64 udev arm64 252.19-1~deb12u1 [1,600 kB]
Get:7 http://deb.debian.org/debian bookworm/main arm64 libudev1 arm64 252.19-1~deb12u1 [102 kB]
Get:8 http://deb.debian.org/debian bookworm/main arm64 libxml2 arm64 2.9.14+dfsg-1.3~deb12u1 [619 kB]
Get:9 http://deb.debian.org/debian bookworm/main arm64 libarchive13 arm64 3.6.2-1 [316 kB]
Get:10 http://deb.debian.org/debian bookworm/main arm64 libjsoncpp25 arm64 1.9.5-4 [72.3 kB]
Get:11 http://deb.debian.org/debian bookworm/main arm64 librhash0 arm64 1.4.3-3 [131 kB]
Get:12 http://deb.debian.org/debian bookworm/main arm64 cmake-data all 3.25.1-1 [2,026 kB]
Get:13 http://deb.debian.org/debian bookworm/main arm64 cmake arm64 3.25.1-1 [6,806 kB]
Get:14 http://deb.debian.org/debian bookworm/main arm64 liberror-perl all 0.17029-2 [29.0 kB]
Get:15 http://deb.debian.org/debian bookworm/main arm64 git-man all 1:2.39.2-1.1 [2,049 kB]
Get:16 http://deb.debian.org/debian bookworm/main arm64 git arm64 1:2.39.2-1.1 [7,023 kB]
Get:17 http://deb.debian.org/debian bookworm/main arm64 libudev-dev arm64 252.19-1~deb12u1 [51.9 kB]
Get:18 http://deb.debian.org/debian bookworm/main arm64 libusb-1.0-0-dev arm64 2:1.0.26-1 [83.0 kB]
Get:19 http://deb.debian.org/debian bookworm/main arm64 unzip arm64 6.0-28 [157 kB]
Get:20 http://deb.debian.org/debian bookworm/main arm64 zip arm64 3.0-13 [223 kB]
Fetched 26.2 MB in 2s (10.6 MB/s)
Armbian live patch apt
DF00FAF1C577104B50BF1D0093D6889F9F0E78D5
Patch file is signed with Armbian GPG key
Running Armbian Live Patch
(Reading database ... 54654 files and directories currently installed.)
Preparing to unpack .../systemd-sysv_252.19-1~deb12u1_arm64.deb ...
Unpacking systemd-sysv (252.19-1~deb12u1) over (252.17-1~deb12u1) ...
Preparing to unpack .../libpam-systemd_252.19-1~deb12u1_arm64.deb ...
Unpacking libpam-systemd:arm64 (252.19-1~deb12u1) over (252.17-1~deb12u1) ...
Preparing to unpack .../systemd_252.19-1~deb12u1_arm64.deb ...
Unpacking systemd (252.19-1~deb12u1) over (252.17-1~deb12u1) ...
Preparing to unpack .../libsystemd-shared_252.19-1~deb12u1_arm64.deb ...
Unpacking libsystemd-shared:arm64 (252.19-1~deb12u1) over (252.17-1~deb12u1) ...
Preparing to unpack .../libsystemd0_252.19-1~deb12u1_arm64.deb ...
Unpacking libsystemd0:arm64 (252.19-1~deb12u1) over (252.17-1~deb12u1) ...
Setting up libsystemd0:arm64 (252.19-1~deb12u1) ...
(Reading database ... 54654 files and directories currently installed.)
Preparing to unpack .../udev_252.19-1~deb12u1_arm64.deb ...
Unpacking udev (252.19-1~deb12u1) over (252.17-1~deb12u1) ...
Preparing to unpack .../libudev1_252.19-1~deb12u1_arm64.deb ...
Unpacking libudev1:arm64 (252.19-1~deb12u1) over (252.17-1~deb12u1) ...
Setting up libudev1:arm64 (252.19-1~deb12u1) ...
Selecting previously unselected package libxml2:arm64.
(Reading database ... 54654 files and directories currently installed.)
Preparing to unpack .../00-libxml2_2.9.14+dfsg-1.3~deb12u1_arm64.deb ...
Unpacking libxml2:arm64 (2.9.14+dfsg-1.3~deb12u1) ...
Selecting previously unselected package libarchive13:arm64.
Preparing to unpack .../01-libarchive13_3.6.2-1_arm64.deb ...
Unpacking libarchive13:arm64 (3.6.2-1) ...
Selecting previously unselected package libjsoncpp25:arm64.
Preparing to unpack .../02-libjsoncpp25_1.9.5-4_arm64.deb ...
Unpacking libjsoncpp25:arm64 (1.9.5-4) ...
Selecting previously unselected package librhash0:arm64.
Preparing to unpack .../03-librhash0_1.4.3-3_arm64.deb ...
Unpacking librhash0:arm64 (1.4.3-3) ...
Selecting previously unselected package cmake-data.
Preparing to unpack .../04-cmake-data_3.25.1-1_all.deb ...
Unpacking cmake-data (3.25.1-1) ...
Selecting previously unselected package cmake.
Preparing to unpack .../05-cmake_3.25.1-1_arm64.deb ...
Unpacking cmake (3.25.1-1) ...
Selecting previously unselected package liberror-perl.
Preparing to unpack .../06-liberror-perl_0.17029-2_all.deb ...
Unpacking liberror-perl (0.17029-2) ...
Selecting previously unselected package git-man.
Preparing to unpack .../07-git-man_1%3a2.39.2-1.1_all.deb ...
Unpacking git-man (1:2.39.2-1.1) ...
Selecting previously unselected package git.
Preparing to unpack .../08-git_1%3a2.39.2-1.1_arm64.deb ...
Unpacking git (1:2.39.2-1.1) ...
Selecting previously unselected package libudev-dev:arm64.
Preparing to unpack .../09-libudev-dev_252.19-1~deb12u1_arm64.deb ...
Unpacking libudev-dev:arm64 (252.19-1~deb12u1) ...
Selecting previously unselected package libusb-1.0-0-dev:arm64.
Preparing to unpack .../10-libusb-1.0-0-dev_2%3a1.0.26-1_arm64.deb ...
Unpacking libusb-1.0-0-dev:arm64 (2:1.0.26-1) ...
Selecting previously unselected package unzip.
Preparing to unpack .../11-unzip_6.0-28_arm64.deb ...
Unpacking unzip (6.0-28) ...
Selecting previously unselected package zip.
Preparing to unpack .../12-zip_3.0-13_arm64.deb ...
Unpacking zip (3.0-13) ...
Setting up unzip (6.0-28) ...
Setting up libusb-1.0-0-dev:arm64 (2:1.0.26-1) ...
Setting up liberror-perl (0.17029-2) ...
Setting up zip (3.0-13) ...
Setting up udev (252.19-1~deb12u1) ...
Setting up libsystemd-shared:arm64 (252.19-1~deb12u1) ...
Setting up libjsoncpp25:arm64 (1.9.5-4) ...
Setting up libudev-dev:arm64 (252.19-1~deb12u1) ...
Setting up librhash0:arm64 (1.4.3-3) ...
Setting up git-man (1:2.39.2-1.1) ...
Setting up cmake-data (3.25.1-1) ...
Setting up libxml2:arm64 (2.9.14+dfsg-1.3~deb12u1) ...
Setting up libarchive13:arm64 (3.6.2-1) ...
Setting up systemd (252.19-1~deb12u1) ...
Setting file flags is only supported on regular files and directories, cannot set on '/var/log/journal'.
Setting up git (1:2.39.2-1.1) ...
Setting up cmake (3.25.1-1) ...
Setting up systemd-sysv (252.19-1~deb12u1) ...
Setting up libpam-systemd:arm64 (252.19-1~deb12u1) ...
Processing triggers for libc-bin (2.36-9+deb12u3) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for dbus (1.14.10-1~deb12u1) ...
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.1.63-current-rockchip64
update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.1.63-current-rockchip64
Image Name:   uInitrd
Created:      Sat Dec 30 02:23:32 2023
Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
Data Size:    14118752 Bytes = 13787.84 KiB = 13.46 MiB
Load Address: 00000000
Entry Point:  00000000
update-initramfs: Armbian: Symlinking /boot/uInitrd-6.1.63-current-rockchip64 to /boot/uInitrd
'/boot/uInitrd' -> 'uInitrd-6.1.63-current-rockchip64'
update-initramfs: Armbian: done.
Checking dependencies for the installation script...
Checking availability of curl... OK!
Checking availability of unzip... OK!
Downloading https://github.com/Schniz/fnm/releases/latest/download/fnm-arm64.zip...
######################################################################## 100.0%
Installing for Bash. Appending the following to /root/.bashrc:
fnm
export PATH="/opt/fnm:$PATH"
eval "fnm env"
In order to apply the changes, open a new terminal or run the following command:
source /root/.bashrc
Cloning into '/usr/local/src/companion-satellite'...
remote: Enumerating objects: 1648, done.
remote: Counting objects: 100% (906/906), done.
remote: Compressing objects: 100% (281/281), done.
remote: Total 1648 (delta 717), reused 758 (delta 610), pack-reused 742
Receiving objects: 100% (1648/1648), 4.23 MiB | 3.87 MiB/s, done.
Resolving deltas: 100% (1004/1004), done.
Installing Node v18.16.0 (arm64)
Using Node v18.16.0
➤ YN0000: Successfully set httpTimeout to 100000
➤ YN0000: · Yarn 4.0.1
➤ YN0000: ┌ Resolution step
➤ YN0000: ⠋ typescript@patch:typescript@npm%3A^4.0.2#optional!builtin<compat/typ➤ YN0000: └ Completed in 5s 647ms
➤ YN0000: ┌ Fetch step
➤ YN0000: ⠙ ==================-------------------------------------------------
./pi-image/update.sh: line 20: 13221 Killed                  yarn
root@rockpi-s:~#
`

the device ran out of RAM.

the device ran out of RAM.

How do you know? I can't tell from the error message...

./pi-image/update.sh: line 20: 13221 Killed                  yarn
It doesn't explicitly say it, but this is typical behaviour when it runs out of memory

Can´t be the issue... Also tested it on a much beefier NanoPi. - same result. --- And: Back in September it worked without any issues. Something must have changed since then. There must be something up with "yarn" I guess...

Tried to run Yarn manually. Same result. It got killed at exactly the same point.

I have reworked the install script, so that it now downloads builds off the website similar to how companionpi does it.
This both reduces the disk usage of satellite, and reduces the cpu and memory cost of updating satellite.
So far there is a single beta build that can be installed, it wont be released until the pi-image building is updated to use this new flow (it currently builds the image the old way, and the first update will switch to the new way)
A consequence of this is that armv7 is no longer supported (it never was officially, but it generally did work. but no builds are produced for it, so the updater fails to find something to install), when attempting to update on that now it should complain before it manages to break anything, the only solution is to switch to an arm64 image.
If there is sufficient demand for armv7, I can look at whether builds can be produced for it, but I don't want to commit to it unless it is needed. In my testing any board which doesnt do arm64 typically has a weaker cpu that results in a more visible rolling update of streamdeck buttons, so isn't a great fit for satellite.
Of course, it is still possible to use on armv7, but it requires manually building from source, and not using the update scripting we provide

This install rework is done, which means this should now be resolved


please explain the which type of data  provides  to  this  model

I would like to inquire about * * self.root dir * * = * * ' /path / to / data ' * *. This  * * data folder * * either  includes  images  and annotations? ,and please explain the format of annotation as well
https://github.com/pfjaeger/medicaldetectiontoolkit/blob/master/experiments/toy_exp/configs.py

please run the generation script for the toy data set. it will create a folder structure which should be explicatory.


chore: update upload-artifact download-artifact actions to v4

What kind of change does this PR introduce?
Bug fix, feature, docs update, ...
What is the current behaviour?
You can also link to an open issue here.
What is the new behaviour?
...
Does this PR introduce a breaking change?
What changes might users need to make in their application due to this PR?
Other information:
Please check if the PR fulfills these requirements:

[ ] Tests for the changes have been added
[ ] Docs have been added / updated
[ ] Relevant Changeset has been added

coverage: 100.0%. remained the same
when pulling e8f8da97acba3f25915ea07cdd9767bc51b74bcd on download-upload-artifacts
into a2328a777c1b4de561f6368ce6230a1cb342a44b on master.


Getting Started Guide for REST APIs is not present

Description:
The following sections are not present in APIM-3.0.0 REST APIs doc space.
Getting started
Configuring the REST API

This has been fixed in 3.1.0 in https://github.com/wso2/docs-apim/pull/1130

This has been fixed in the 3.0.0, 3.1.0 and 3.2.0 docs.


better warning message for reportMissingImports

All (?) users of workspaces with >1 editable installation will run into this issue by default. Many of them, like myself until today, will not know why they're getting orange squiggles in their code and they will give up trying to fix it. I'd suggest that naive browser searches won't easily lead them to #3473.
At least for me, one of the most confusing aspects of this is that some of my editable installations would be found, but not others (even though they were all installed using pip the same way). This made me think that it was some kind of PATH or WSL problem and that somehow I wasn't selecting the correct interpreter somewhere. Retrospectively, perhaps the confusion was exacerbated by uninstalls not removing everything and/or going back and forth between WSL and Git Bash.
The quick fixes suggested include:

changing interpreter. This does not resolve this problem.
"learn more" link to this help page. Clicking the pyright documentation page leads to this. I'd argue that the wording is a bit misleading because it states "and is currently set up to use import hooks" and also uses language suggesting it's optional, however, since I didn't (knowingly) make such a choice it's not obvious that it applies to me. I'm not even sure what an "import hook" is... 😓

I doubt there's a quick fix available. Could you add a helpful recommendation to the reportMissingImports tooltip? Maybe a new category of error if pylance thinks it's a misconfigured editable install? Or maybe rewrite some of the text on the help page to be obvious?
Or maybe just by writing this up this issue, people will be able to find it more easily...

We could detect that there are problematic .pth files in your environment and warn you about that in every import failure diagnostic message. Unfortunately we don't see a way to reliably connect a particular import failure to a particular .pth file.
@qci-amos, would that have helped in your situation?

FYI, I also opened https://github.com/microsoft/pylance-release/issues/4855 to improve the language in our docs.

@qci-amos, would that have helped in your situation?

I'm not sure if this would have been sufficient... but yea, while I generally don't know details about how editable installations happen, informing me that there's more than one way to install them (that's the part that was news to me) should have set me on the right track!
I don't know if it helps, but feel free to cite me if it helps prod things in the right direction a la your comment here! 😁

I'll go ahead and close this issue as a duplicate of #4855 for now. Feel free to keep an eye on the progress of the documentation improvement over there. Thanks


GUI interface is not displayed

Hi, when I open the localhost:config GUI keeps loading and not displaying, both the cuda version and the non-cuda version I've tried, could you please tell me what's causing this?

Hi,
Can you post the logs of console, then I maybe can figure out the problem


feature: Add integer, base_specifier and bit_value for bit_string_literals

Did you check the tree-sitter docs?

[X] I have read all the tree-sitter docs if it relates to using the parser

Is your feature request related to a problem? Please describe.
I am looking at the 2008 LRM 15.8 "Bit string literals", specifically:
 bit_string_literal ::= [ integer ] base_specifier " [ bit_value ] "

In the current version of the treesitter we only see "bit_string_literal". I like the look of it much better when the syntax highlighting can differentiate between its integer, base_specifier and the bit_value instead. Users can then still choose the same color for all of them if they prefer that.
Describe the solution you'd like

Describe alternatives you've considered

Additional context
No response

I can do that...
Will take a bit longer though -- the scanner needs an extra state
On this note -- I mark "01110110" as "string literal" instead of "bit string literal"...  With a little bit of effort I should be able to convince the scanner to only change it to a "string literal" when the string contains non-std_logic letters -- what do you think?  Should I do that?

I mark "01110110" as "string literal" instead of "bit string literal"

A bit_string_literal must always have a base_specifier, see LRM 15.8. So "01110110" can never be a bit_string_literal. Unless I am missing something in the LRM, "01110110" must always be a string_literal.

Strictly by standard, I would agree with you.  But what about code readability...?  I think I might find it useful to be able to instantly notice "011011XXXLLHH" as something else to "My Error Message"

How about I alias string literals that only contain std_logic values as string_literal_std_logic?  Then it's still differentiable.

Yeah I see what you mean. But imho this should be handled by the highlighting.scm. Like when there is the string_literal after a std_logic_vector (or unsigned, signed, etc) signal declaration or assignment, then it should be captured as such and such. Else capture it as a normal string.
I think the syntax tree should be as close to LRM as possible. I am dabbling a bit in the VHDL_LS LSP and a good treesitter syntax tree makes life much easier. What you suggested might lead to confusion. Just my opinion though.

Similar vein...
Would you split based literals as well?  At the moment I simply return based_literal and based_literal_float.
based_literal  ::= base "#" based_integer [ "." based_integer ] "#" [ exponent ]
base           ::= integer
based_integer  ::= extended_digit { [ underline ] extended_digit }
extended_digit ::= digit | letter
exponent       ::= "E" [ "+" ] integer | "E" "–" integer

...  this should be handled by the highlighting.scm

How would you handle the following in the highlighting queries?
process(clk) begin
  if(rising_edge(clk)) then
    if(A = B) then
      A <= "100110101";
    else
      B <= "101100110";
    end if;
  end if;
end process;

I'm liking my string_literal_std_logic solution, then you can simply treat both string_literal and string_literal_std_logic  as the same thing in your other tools, and they won't interfere with bit_string_literal...

based literals

With these rarely used syntax elements I would actually prefer simplicity. Unless someone actually requests this as a feature or something. Or unless it is trivial to implement. Again, just my opinion.

With these rarely used syntax elements I would actually prefer simplicity...

I'll run an experiment and see what it looks like -- I can always revert later.  It'll be trivially easy to implement after I've figured out how to split up the bit_string_literal, because the scanner treats them similarly.

string_literal_std_logic

Yeah I see what you mean now. But your solution to it sounds good to me. My main concern was to prevent confusion when treating syntax elements as something that would clearly go against the LRM.

@Chris44442
Please could you test the commits above (feature/split_bit_strings branch)...?  I'll merge to develop once you give the OK

I've gone ahead and implemented the split to based literals as well: feature/split_based_literals branch, which runs on top of feature/split_bit_strings.

Done. Highlighting looks good. Inspecting the tree looks good. Nothing wrong as far a I can tell so far.
I actually like that the bit_string_length and not just integer. This way users will have more freedom.

Merged to develop and pushed

Yep, nice!
Right now I am a bit indecisive though if I like bit_string_length better than integer. I guess it's not a big deal either way. Readers of the syntax tree will know what is going on with "bit_string_length" even though it might not be the same as what the LRM says should be expected. On the other hand referencing the LRM and the syntax tree might be easiest when there are as many similarities as possible. Mhhh.

I had it as "integer" and then changed it to "length", because I think it better describes what it is...  Same with "base" and "value" instead of "base_specifier" and "bit_value".
I'll change it if someone opens an issue to complain about it ;-)


Error when creating profile from current profile with partial extensions.

Does this issue occur when all extensions are disabled?: No

VS Code Version: 1.80.0 (Universal)
OS Version: macOS 13.4.1

Version: 1.80.0 (Universal)
Commit: 660393deaaa6d1996740ff4880f1bad43768c814
Date: 2023-07-04T13:39:33.766Z
Electron: 22.3.14
ElectronBuildId: 21893604
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.5.0

Steps to Reproduce:

Go the command palette and start 'create profile from current profile'.
At the side bar uncheck some of the extensions.
The profile is created with no extension and showing the following error message.

/duplicate

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


kafka discovery and configs

Description:

Link to Splunk idea: <Link to Splunk idea, see https://ideas.splunk.com>
Testing:
Documentation:

I have read the CLA Document and I hereby sign the CLA

I have read the Code of Conduct and I hereby accept the Terms


Add condition for the case of repeated timestamp

this case happened for NBC videos. In time-based pagination, It had only one video in the last page (oldest video) and it shows even after we changed timestamp to date format.

Coverage remained the same at 100.0% when pulling fb989b840178a0b3f1ccccb098b7859ba6a638d5 on nbc into a49969f87921ccef7c56a2830707c995a56d9f62 on master.


Create ampform-dpd Conda package

ampform-dpd is currently only available on PyPI. We should create a conda-forge feedstock, just like https://github.com/conda-forge/ampform-feedstock.
### Tasks
- [x] Create feedstock --> https://github.com/conda-forge/staged-recipes/pull/26195
- [x] Build older releases

See https://anaconda.org/conda-forge/ampform-dpd


[Inky] Menu updates

Todo:

[x] add <th> tags to CSS so it is responsive in Android 4.4 - Resolves https://github.com/zurb/foundation-emails/issues/241
[x] remove padding, padding-right if needed (styled like simple inline list) - Resolves https://github.com/zurb/foundation-emails/issues/233
[x] get rid of simple class
[ ] Menu links not blue in Outlook - Resolves https://github.com/zurb/foundation-emails/issues/231
[x] in Inky, add width attribute width="600"
[x] In Inky, <center> tags wrapped around should add align: center - Resolves https://github.com/zurb/foundation-emails/issues/238
[ ] In Inky, <center> tags wrapped around menu should add .float-center to each .menu-item.

Todo:

remove padding, padding-right if needed
get rid of simple class
in Inky, add width attribute width="600"

Fixed the CSS and HTML for menus. Here are the significant changes that will effect Inky @kball:

Needs another <table> so that padding is respected.
Classes are updated. We now include .menu-item.

These changes are reflected in the new menu.html in the testbed. Simple menus are now obsolete!
We still need to optimize the CSS, but it works as expected in all email clients!

<center> and <menu> fixes implemented via zurb/inky@97fde356d79602e3c8ac9789d3d081df18e6b9eb

All Inky updates are in 1.2.6. Passing assignment to @rafibomb for the last menu issue.

@gakimball Can you help with the last item?

Updates to <center> and <item> via zurb/inky@f25859c3dc0612231687458885d578f5e3893b4a

Fixed somehow :+1:


Naming discrepancies need to be addressed

src/test/java/AddStuffToStringTest.java should reflect the package/class that it is testing. Which is AddSyntaxToString
Also, tests should not be camel cased. Currently there are a mix of naming conventions in the class. Ideally, tests should be snake_cased

merged into master


chore: add typing to propagator carrier

Adds typing where there was none before :)

Codecov Report

Merging #772 into master will increase coverage by 1.13%.
The diff coverage is 100%.


Cleanup platform details on landing and platform pages

Discusses changes to

the landing page: https://pub.dartlang.org/experimental/
the platform page: https://pub.dartlang.org/experimental/packages

Follow-up to https://github.com/dart-lang/pub-dartlang-dart/pull/660

[ ] Header in main content (both pages)

H2
color: gray
font-weight: 500

I was planning to put the same landing blurb on the platform pages (when there is no active search). WDYT?


reduce number of failed project lookups

When a project is assigned that doesn't exist, the projectidcache
was ineffective. we can make that more optimal by first collecting
the set of all projectnames, then looking it up, and then
assigning it to the users.
UNTESTED

How many projects are there in current json file?

@dirkmueller I fixed the pep8 violation in https://github.com/cmurphy/keystone-json-assignment/pull/4 so you'll have to rebase

@bbobrov there are 31 projects and 727 users.

@cmurphy and how many of them do not exist?
I mean, why do we even care to optimize it? :)

@bbobrov They really should all exist, there's very little reason to have this JSON mapping if the projects don't exist. But it could help in test environments to only have to create a couple of projects instead of all 31. @dirkmueller did you run into a problem like this on the production env?

@cmurphy no, its just something I hit on the tst env where I didn't create the projects and it spends about 30s on hanging, which is not so nice.
I'll test it.

@cmurphy updated


windows_service resource prints ruby warnings from win32-service gem

Description
We are in the process of upgrading from chef-client 13.x to 14.x. We encountered an unexpected behavior in the 14.x client where the windows_service resource prints out a bunch of warnings from the win32-service-0.8.10 gem. The warnings all deal with one particular service (CDPUserSvc) which apparently is checked each time the windows_service resource is used in a recipe. As far as I can tell, these warnings are just warnings and don't actually cause the windows_service resource to not work properly. It's an annoyance to see the warnings in the run output though, makes it much harder to read the logs or STDOUT of a chef run quickly.
Chef Version
chef-client 14.1.12
Platform Version
Windows Server 2016 (long term servicing build 1607, w/ desktop experience)
Replication Case

Install Windows Server 2016 with desktop experience
Install chef-client 141.12
Define a recipe with example windows_service resource like the following example:

windows_service "W32Time" do
        action          [:configure_startup, :start]
        startup_type    :automatic
        run_as_user     'NT AUTHORITY\LocalService'
        run_as_password ""
end

Run chef-client from an elevated command prompt on the server's desktop. Observe output similar to the sample below. The session ID appended to the CDPUserSvc service name will likely be different.

Client Output

  * windows_service[W32Time] action configure_startupC:/opscode/chef/embedded/lib/ruby/gems/2.5.0/gems/win32-service-0.8.10/lib/win32/service.rb:1081:in `block in services' : C:/opscode/chef/embedded/lib/ruby/gems/2.5.0/gems/win32-service-0.8.10/lib/win32/service.rb:1081: warning: constant ::Fixnum is deprecated
 (StructuredWarnings::BuiltInWarning)C:/opscode/chef/embedded/lib/ruby/gems/2.5.0/gems/win32-service-0.8.10/lib/win32/service.rb:1088:in `rescue in block in services' : WARNING: Failed to retrieve description for the CDPUserSvc_5fa8f service. (StructuredWarnings::StandardWarning)C:/opscode/chef/embedded/lib/ruby/gems/2.5.0/gems/win32-service-0.8.10/lib/win32/service.rb:1101:in `rescue in block in services' : WARNING: Unable to get delayed auto start information for the CDPUserSvc_5fa8f service (StructuredWarnings::StandardWarning)C:/opscode/chef/embedded/lib/ruby/gems/2.5.0/gems/win32-service-0.8.10/lib/win32/service.rb:1159:in `rescue in block in services' : WARNING: Unable to retrieve failure actions for the CDPUserSvc_5fa8f service (StructuredWarnings::StandardWarning) (up to date)
  * windows_service[W32Time] action startC:/opscode/chef/embedded/lib/ruby/gems/2.5.0/gems/win32-service-0.8.10/lib/win32/service.rb:1088:in `rescue in block in services' : WARNING: Failed to retrieve description for the CDPUserSvc_5fa8f service. (StructuredWarnings::StandardWarning)C:/opscode/chef/embedded/lib/ruby/gems/2.5.0/gems/win32-service-0.8.10/lib/win32/service.rb:1101:in `rescue in block in services' : WARNING: Unable to get delayed auto start information for the CDPUserSvc_5fa8f service (StructuredWarnings::StandardWarning)C:/opscode/chef/embedded/lib/ruby/gems/2.5.0/gems/win32-service-0.8.10/lib/win32/service.rb:1159:in `rescue in block in services' : WARNING: Unable to retrieve failure actions for the CDPUserSvc_5fa8f service (StructuredWarnings::StandardWarning) (up to date)

Stacktrace
No stacktrace, the issue does not result in an error condition.

This was fixed in win32-service here https://github.com/chef/win32-service/commit/7b1720fca8ae39a10368fe10b4918deddbd622b1. We just need to get that gem released and then bump our dep to fix that. Thanks for the report @flakzilla. These are annoying and easy to get rid of.

Well enough. We'll keep an eye on this and update to the newer client version when it becomes available. I can confirm the issue is still present in 14.2.
Speaking of, the 14.2 client spits a bunch of these out unexpectedly:
WARN: Using deprecated positional arguments for sign(), please update to keyword arguments (from C:/opscode/chef/embedded/lib/ruby/gems/2.5.0/gems/chef-14.2.0-universal-mingw32/lib/chef/http/authenticator.rb:114)

Do you want another bug report for this?

That last one we already have a fix for. It's in master and that'll get resolved with 14.3's release.

Sounds good to me. Thanks for taking care of it.

Resolved by #7405


Changes to oracle migration

Hitas Pull Request
Description

More debug messages
Edge case handling
More generous owner combining logic

Pull request checklist
Check the boxes for each DoD item that has been completed:

Testing

[x] Changes have been tested
[ ] Automatic tests have been added

Database

[ ] Database migrations will work in the DEV & TEST environments
[ ] initial.json has been updated to work with migrations
[x] Oracle migration has been updated

Documentation

[ ] Tooltips have been added in the frontend for all new fields
[ ] OpenAPI definitions have been updated
[ ] Test instructions have been written for the customer in the appropriate ticket in Jira
[ ] Terminology page in Confluence has been updated

Test plan

[x] Run migration without anonymization and check errors.

Tickets
This pull request resolves all or part of the following ticket(s): HT-534, HT-548

This was a "just throw it in there" kind of pull request so :D


2 New modules & Preparation for some user config.

Awesome project, been looking for something like this for a while.
Looking forward to contributing in my free time.
#36 Is mostly handled with this pull request & have some more lined up.
Note, we maybe need to look closer at the fetching of the editor themes.
Currently working on: #32 & some major styling updates.

btw Will be creating future branches with either feat/ or fix/ nomenclature.

Note, exporting colors & palettes will be possible in my next pull request 🎉

This is amazing I will take a look 🎉

@Sparkenstein  Dropping the hamonies module right now, it contains some code cleanup and removal of unused utils.

Sure. If you are using pnpm i'd recommend to not push the lockfile, I have'd issues with tauri and pnpm in the past especially in the CI. so currently I am working with yarn to avoid any unnecessary build changes

@Sparkenstein yeah I noticed, could u remove that massive file? Before considering merging it. Didn't know it would cause issues 👍
I'll try to remember, I'm normally using pnpm mostly out of habit.

You will be working on the color blindness simula thing right?