Some tests result in pending state when testsettings file specified in Run Functional Tests task

If I specify a .testsettings file in the Run Functional Tests v1.* task, as many as 75 test cases out of 291 show pending status.  Even if the .testsettings file contains no sub elements, many tests still show pending status.  The second issue is these test results don't explain why these tests show pending status and why they didn't run.  This is a worse experience than MTM.  I have attached 2 .testsettings file and 2 screenshots.
Temp.zip

@yorhpokie sorry for the inconvenience.  Please feel free to share your feedback: https://visualstudio.uservoice.com/forums/330519-team-services. We will be glad to improve the experience.
Seems like these test cases are skipped/ignored. Do you have any filters on Run Functional Test task? Can you please attach DTAExecutionHost.exe.log file from Test agent machine [C:\dtalogs\dtaexecutionhost.exe.log or C:\testagent\dtaexecutionhost.exe.log]?

_Hi nigurr and prawalagarwal,
I don't have any filters on Run Functional Test task.  In the latest test run where I specify only 2 test agents, half of the tests ran and the other half resulted in pending state.  I have attached a zip file that contains the dtaexecutionhost.exe.log files for both test agents.  Please let me know what you find out.  Thank you!
DTAExecutionHost.exe.zip
_

@yorhpokie
Are you running the tests using Test Plan/Test suites?

Yes, the Test Plan/Test suites are from MTM.

@yorhpokie Are there any test cases are associated to same test method?
This is known issue where if multiple test cases are associated to same test method, there will be an error and tests wont be executed. This is fixed in VS 15.3 and later versions. We suggest you to remove duplicated test cases or duplicate the test methods and re associate test cases.

@nigurr All of our test cases have unique test method.  This issue only happens if a .testsettings file is specified in the Run Functional Test task, even when the .testsettings file is mostly empty.  Please investigate further.  This is blocking us from moving to the test infrastructure in TFS 2017, especially considering MTM will be deprecated in TFS 2018.

@yorhpokie We are happy to help you on this and help you to migrate. Can you please raise support ticket with Microsoft Customer Service? Please let me know if you need any assistance regarding the same.

Closing this. Please re-open if you still need assistance on this issue.


New output type: Webex

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area config

/area outputs

/area tests

What this PR does / why we need it:
This PR adds the 'Webex' output, enabling sending messages to a given Webex Room using a Webhook URL. As the format expected by the Webex API endpoint is very specific, using the Webhook output isn't possible.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
I've taken inspiration from the Teams output, which is quite similar, which is why I placed the various Webex declarations right below it. If you prefer another order, let me know.
I've tested it sucessfully using the provided curls's tests commands, and a few falco rules of my own.
Also let me now if I missed some docs/example ?
Regards !

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

5f77a47 feat: add webex output code
01b5f7f feat: add webex related docs
6b854f3 feat: add example config for webex
11e4ed5 fix: remove duplicated headers

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Welcome @k0rventen! It looks like this is your first PR to falcosecurity/falcosidekick 🎉

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: k0rventen
Once this PR has been reviewed and has the lgtm label, please assign issif for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

a409bdd feat: add webex output code

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Amazing proposal, and it seems very complete. I will do the full review asap. Thanks

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: k0rventen
Once this PR has been reviewed and has the lgtm label, please ask for approval from issif. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Amazing proposal, and it seems very complete. I will do the full review asap. Thanks

Hey thx ! I just pushed a few fixes, apparently I forgot to check if I changed 'teams' to 'webex' everywhere. Also an improvement on the template loading, which is now done only once instead of on every call of the post function (not a go expert but I think it's better ?)
Cheers !

could you also squash your commits once you fixed my comments, please

We should be good now !

could you also squash your commits once you fixed my comments, please

We should be good now !

Just the squash to do and I'll approve. Thanks

could you also squash your commits once you fixed my comments, please

We should be good now !

Just the squash to do and I'll approve. Thanks

yeah sorry when squashing I rewrote the commit message, leading to this one: 0db1a5f

the 6 commits are still there, most of them are typo fixes, rebase on the master then squash (rebase -i) your commits on the HEAD/master please

it's now all in 19a6aac7688860b778731152d4a8f0ba3cd93acb :smile:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif, k0rventen
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: d1c1e171724ca70bd871d06c25f03d8858aa0e9c


BUG: VCS status does not indicate problems if a tag was force-pushed

Problem
I have a repository I use. The authors created a tag v1.2.3 on commit A. Then, they deleted the tag and re-tagged, this time on a new commit  B. vcs status indicates the repository is on v1.2.3, but it's actually on commit A. v1.2.3 actually points to B.
Expected behavior
vcs pull src then vcs status shall show I am on commit B rather than the tag.
Actual behavior
VCS lets me be on the wrong commit with no warnings or errors, it's silently the wrong commit.

@Ryanf55 As a suggestion I advise to keep use or add the .gitmodules + GitExtensions.
It tracks things like that and shows desync-ed modules. But as a disadvantage you have to convert and commit changes from vcstool file into the .gitmodules file.

We migrated off of gitmodules because of all the issues of dysync, and the fact that we have a rolling HEAD for most of the 20 repositories to save time. We also develop in Linux, which it looks like GitExtensions is Microsoft specific.

We migrated off of gitmodules because of all the issues of desync, and the fact that we have a rolling HEAD for most of the 20 repositories to save time. We also develop in Linux, which it looks like GitExtensions is Microsoft specific.

And nevertheless you don't have to use .gitmodules for the checkout. You can keep checkout through the vcstool and track changes through the GitExtensions which tracks the .gitmodules status.

We also develop in Linux, which it looks like GitExtensions is Microsoft specific.

https://github.com/gitextensions/gitextensions/wiki/How-To:-run-Git-Extensions-on-Linux


Provide split APK components for other languages than English for com.android.vending

In the Sandboxed Google Play section of the Usage guide the link for com.android.vending does lead to a repository that only contains the English version, i.e. only the split_config.en.apk component for localisation is provided.
I'm currently looking up the matching version of the Google Play Store package on apkmirror and extract the German version split_config.de.apk. However, it would be much more convenient if the APK files for other languages would be available directly from https://apps.grapheneos.org/packages/com.android.vending.
Are these other localisation APKs easily accessible in the extraction process used to obtain the files for https://apps.grapheneos.org/packages/com.android.vending ?
If yes, would it be possible to include them please ?

The main issue is we don't know how to easily obtain these right now. We probably need to set up using the Play Store API to fetch them instead of grabbing them off a stock OS device, currently a Pixel 4 that's locked and used to securely obtain them.

This is filed as https://github.com/GrapheneOS/apps.grapheneos.org/issues/6.

This is implemented for our repository for major languages. We also now support Play Store updating itself and Play services. It will ask to reinstall even the same version and will install additional splits.


Instaloader command not found

Hi,
I Have installed Python 3,Python pip and installer on Ubuntu but when running the Following command installer profile i am receiving a error saying the command can not be found.
Can confirm that instaloader is installed but still receiving this message

I see no command line and also no error message in your report, please provide it otherwise issue will be closed.

I see no command line and also no error message in your report, please provide it otherwise issue will be closed.

Hi,
Managed to find the solution using this post
https://github.com/instaloader/instaloader/issues/440


No such file or directory: '/config/www/alexa_tts'

Describe the bug
After following some tutorials, I still can't get the service to find my devices.
The login works, but after that, no devices are found.
To Reproduce
Follow this tutorial:
https://www.youtube.com/watch?v=UEPt3edhwc0
Expected behavior
Devices are listed
Screenshots
System details

Home-assistant (version): 2023.09.2
alexa_media (version from const.py or HA startup):
alexapy (version from pip show alexapy or HA startup):
Amazon 2FA is enabled (y/n). Yes

Logs
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 362, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/alexa_media/media_player.py", line 157, in async_setup_entry
if await async_setup_platform(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/alexa_media/media_player.py", line 105, in async_setup_platform
os.mkdir(UPLOAD_PATH)
FileNotFoundError: [Errno 2] No such file or directory: '/config/www/alexa_tts'
Additional context

I fixed this, by just creating the requested folder structure manually...

I have updated and rebooted and I still see the same error:

I am on 4.7.1


test scope for junit

A small correction of the project dependencies.

Develop switched to a newer version of the build  system which uses JUnit5. I would consider this PR  deprecated.


fix issue #492

php artisan sail:install --with=none not handled properly

@taylorotwell sorry did not quite get why the PR was closed without merge. Actually this bug is really annoying as it forces anyone to deploy sail with at least an additional service, which is not wanted in a minimal sail build.


Regression: Steem() can no longer connect to custom node

In [15]: s = Steem(node='wss://this.piston.rocks')

In [16]: s
Out[16]: <steem.steem.Steem object at 0x7ff69c06c780>

In [17]: s.rpc.url
Out[17]: 'wss://steemit.com/wspa'

In [18]: s = Steem(node=['wss://this.piston.rocks'])

In [19]: s.rpc.url
Out[19]: 'wss://steemit.com/wspa'

A quick hack workaround:

On a slightly ranty note, I am not a fan of having both instance and class variables and the spaghetti of state and mutation thereof interleaved all over the place, as it makes it really hard to understand what is going on.
The problem becomes more pronounced in larger apps (especially if multithreaded), where different parts of code might need Steem in a different configuration (ie. different node url, or broadcast/nobroadcast state). Currently its impossible to reason about what will happen in production.
Perhaps it would be simpler to remove class variables alltogether, and in the Steem.__init__, lookup the piston config for settings that are not provided by the user. Furthermore, by always creating a Steem instance fresh, and containing state and state mutations to that instance only, users would have some level of certainty over what the expected state should be. Yes, this would add a bit of resource overhead, but I think its worth it.

The reason for having those class variables was that I would like multiple classes to share a single RPC connection. That way, a code like this:
from steem.block import Block
from steem.blockchain import Blockchain

Block()
BlockChain()

Share the same RPC connection and don't open up new ones.
Same holds true for the Wallet class.
However, I am also not very happy with the confusion that is added to the code this way.
How would you propose to get the best parts of both worlds, simple code and a singelton RPC interface?

All classes already support steem_instance parameter, for passing user defined instance.
If we want to share a single connection between all classes by default, perhaps a namespace bound variable can be created in steem which is only initialized once trough default_steem_instance(), from the default (piston) config.
Then, classes like Block and Blockchain can just do:
from steem import default_steem_instance

def __init__(..., steem_instance=None):
    self.steem = steem_instance or default_steem_instance()

This would allow users to:
1.) Override the default instance for all classes by modifying/overloading underlying default in steem.
2.) Override the default instance for single classs by providing their steem instance via steem_instance= argument.
3.) Ability to create clean and easy to reason with Steem() instances.
The Steem() class is the most fundamental part of python-steem, and by removing class instances it would be a lot simpler, stable and usable.

The default_steem_instance could still see if there already is a open connection and reuse it as a default behavior?

Yes.
default_steem_instance() initializes the global steem instance, or returns the reference to said instance if it already exists.
Because python is pass by reference, with the above pattern, for most users, only a single instance/connection would exist.
For users who want to define their own instance and pass it to classes, there would be 2 connections at most, the default one and user defined one. So the worst case overhead is really minimal.

I have implemented the above proposal, see branch https://github.com/xeroc/python-steem/tree/24

Here are two examples of overloading the default Steem instance:
1.) Override the Steem instance for individual class (instance only).

2.) Override the Steem instance for all classes (classes initialized prior to change won't be affected).

Soon we're going to stop using websockets entirely in favor of plain ol' HTTP(s) requests, so I imagine this will be pretty unimportant, although you still might want to support different endpoint URLs (but reusing a connection won't be a thing).

hi @sneak, pleasure to see you lurking in here.
I actually kind of like WebSockets, since they are a lot more efficient than HTTP1.1 (there is no setup/teardown cost).
Can you tell us a little bit more about what exactly will change (just the transport or API)?
Will the new API be served by steemd?
Will it support HTTP2?
Is this feature 'planned' or has it already been developed? ETA release?

@sneak, the problem described here is actually independent of how the connection is made. There is some RPC connection and we would like it to share (if possible) with different classes. If websocket goes away, i would like to only chance the underlying rpc code and not the code that builds on top of it.
@Netherdrake Thanks for the pull request, but I think we can do something easier.
Your use-case basically breaks because of these lines:
https://github.com/xeroc/python-steem/blob/master/steem/steem.py#L142-L149
(which have been a stupid but quick implementation)
Anyway, I would like to fix this issue by simply distinguishing three cases:

There is a Steem.rpc defined already and no new url is provided: We use self.rpc = Steem.rpc
There is a Steem.rpc and a different url is provided, we set a new self.rpc and keep Steen.prc untouched
3, Steem.rpc is empty and no url is provided, we connect Steem.rpc with the default connection and refer to it with self.rpc

@xeroc if I understand correctly, this would remove all class variables but Steem.rpc.
I think this would mostly work, but break down when using fallback nodes (ie. Steem(node=['node1', 'node2', 'node3']).

The reason I have setup wallet as a class variable was to prevent the app from asking the user for an unlock password multiple times if he just forgot to hand over the steem intance.
I still see some advantages in using class variables and would like to propose a fork for testing today @Netherdrake

Good job on this pull request .. I like it so much that I am now also using it in pybitshares.
Also, I thin the instance.py could be used to define a new default if people don't want to use the explicit steem_instance all the time ..

@xeroc yes, thats what set_shared_steem_instance does. The user can just call it at beginning of their script, and thus effectively change the default instance to their own.

lol .. didn't know that you had that added already ... awesome job!


fix: multiline output

Fixes https://github.com/dagger/dagger-for-github/issues/161, a regression introduced in 1a00b8f (#153).

FYI @kpenfound added a commit at the end that fixes https://github.com/dagger/dagger-for-github/pull/162.
Noticed there was a bug that caused quotes in args/call to not quite work as expected, they were getting incorrectly expanded. So just fell back to the old behavior, and handled the replacement in github action expressions.


clear button on left side works

Clear button functionality works

Great job fixing this Jimmy, I should not be surprised anymore but wow


Adding Frequently Asked Questions

Put the frequently asked questions page under the More section. Could easily be moved somewhere else. I based the questions on the google doc I have access to. Should be easy to change or add other questions.
Wondering if the sections make sense or not.
Planning to merge in the next day or two unless changes are suggested.
Related to #1870
Styling:

I think it makes most sense under "More" but could alternatively be placed under "Learning." I'm working on additional the FAQs found on the channel today if you want to coordinate.


Modify how MCAS connects to AWS

Hi team, I am one of the original content authors for this document, it has recently come to light that some of the MCAS UI changes mean this document needs to be updated to reflect the new onboarding process for the AWS app to be managed via Session Controls.

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

ID: d4cac8b6-d73b-07aa-dac0-2f833e0b95f9
Version Independent ID: 29e460db-0e0a-265f-ff5e-e242cd24b165
Content: MCAS and Azure Sentinel for Amazon Web Services (AWS) - Azure Solution Ideas
Content Source: docs/reference-architectures/aws/aws-azure-security-solutions.yml
Service: architecture-center
Sub-service: reference-architecture
GitHub Login: @doodlemania2
Microsoft Alias: pnp

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 463254

Hi @richarddiver-ms,
Sorry for the delay.
The document has changed a lot since the issue was reported.
This issue was reported when the content looked like this: https://github.com/MicrosoftDocs/architecture-center/blob/b41e5098bea0c1d08e3729a0913deb3543f8c80d/docs/reference-architectures/aws/aws-azure-security-solutions-content.md
Now, there is not MCAS reference as before.
I will close the ticket, but feel free to open a new one if you still have concerns.
#please-close


Consider removing execute

And potentially start_detached as well. If we have a reasonable async_scope definition both fall out more safely that way.


Internationalise UI text messages

We should put our errors/dialogs/etc into plists so we can translate them into other languages more easily.

Something like this might be faster/better than using plists?

Yeah, could be.
On Fri, 23 Dec 2016 at 1:06 pm, Chris Hocking<EMAIL_ADDRESS>wrote:

Something like this https://github.com/kikito/i18n.lua might be
faster/better than using plists?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fcpxhacks/fcpxhacks/issues/121#issuecomment-268933848,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADbEw3sMiyEpg8lGdp85NS50t_QTrNJ5ks5rKzqXgaJpZM4LUizp
.

All the prep work has been done. Now we just need to do the actual translations.


pathwaymatcher: add coreutils

to allow for mv -t
also remove unnecessary redirections

Please bump the version number :)
We are waiting until testing is in place, do we?

looks good to me . version number is bumped :)

Can you please check that this is also getting uploaded? We probably need to set credentials, left?

Also I guess we need to update the travis badge on the main readme when this is working.

yep. credentials are missing: https://github.com/galaxyproteomics/tools-galaxyp/runs/565889196?check_suite_focus=true
we need tts_api_key and ts_api_key .. then we can restart the workflows listen in the Actions tab.

Did this yesterday evening.


Fix unit tests

Refactor code for improved maintenance
Get unittest coverage to 100%

This is on top of the previous pull requests, once that is merged the changes from that PR will disappear from this PR.

Looks really good, solid work! I left just small remarks.
There is one thing that I wanted to discuss - I see you run tox -e unit, and that is good - I was using it as well when converting a charm. I had to transfer some files (charmcraft.yaml most notably) to be able to charmcraft pack the converted charm. That's when I noticed the presence of ./run_tests - it is generated by default for new charms by charmcraft init. It runs flake8 and unittest with coverage report and doesn't seem to rely on tox in any way. I'm wondering what is the recommended way of testing charms, as https://juju.is/docs/sdk/styleguide#heading--testing still favors tox.

Looks really good, solid work! I left just small remarks.
There is one thing that I wanted to discuss - I see you run tox -e unit, and that is good - I was using it as well when converting a charm. I had to transfer some files (charmcraft.yaml most notably) to be able to charmcraft pack the converted charm. That's when I noticed the presence of ./run_tests - it is generated by default for new charms by charmcraft init. It runs flake8 and unittest with coverage report and doesn't seem to rely on tox in any way. I'm wondering what is the recommended way of testing charms, as https://juju.is/docs/sdk/styleguide#heading--testing still favors tox.

Yeh I noticed that too, in this repo there is also a makefile which seems to have some value. My preference is also tox rather than the ./run_tests command since there is a range of tests (unit and integration) which are easily managed by tox. The indico charm is also using tox, maybe @mthaddon  can enlighten us :)

Yeh I noticed that too, in this repo there is also a makefile which seems to have some value. My preference is also tox rather than the ./run_tests command since there is a range of tests (unit and integration) which are easily managed by tox. The indico charm is also using tox, maybe @mthaddon can enlighten us :)

In the IS team we favoured having a Makefile that then does whatever's needed for a particular target (typically it just calls tox targets). At some time after this, the charmcraft init template added ./run_tests which relies on sourcing a virtualenv first, which seems a little cumbersome to me. I think using tox is definitely the way to go here. We can remove the Makefile as well, and then just document how to develop/test locally on a documentation page for the charm similar to how we do on https://charmhub.io/indico/docs/contributing by updating https://charmhub.io/jenkins-agent-k8s/docs/contributing-hacking.

I asked about the ./run_tests on starcraft channel and it seems that will go away and the preferred way is to use tox. Wrapping it in a Makefile like IS does is fine with me, I like Makefiles. Point here is that tox is preferred over ./run_tests and is aligned with the documented practice in the SDK https://juju.is/docs/sdk/styleguide#heading--testing

The makefiles seem handy for things like building the images and then running tox with the right resources etc, reduces the mental overhead of having to remember how to do things. I would prefer keeping it, although it does require some cleanup for this repo (for which I'll add an issue).
@merkata / @mthaddon please complete the review, there is another PR for linting that is waiting on this one


condenseFlow results in invalid object keys

jsYaml.safeDump({key: 'value'}, {
    flowLevel: 0,
    indent: 0,
    lineWidth: Infinity,
    noCompatMode: true,
    sortKeys: true,
    noRefs: true,
    condenseFlow: true
})

results in actual YAML:
{key:value}

but parsing that with safeLoad() results in
{ 'key:value': null }

Expected YAML:
{"key":value}
# or
{key: value}

which results in
{ key: 'value' }

cc @eseliger

Oh
Will look into that


https://github.com/google/benchmark

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/31142658-https-github-com-google-benchmark?utm_campaign=plugin&utm_content=tracker%2F1032790&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1032790&utm_medium=issues&utm_source=github).

Note: CMake based

I plan to implement this package but benchmark is very generic name. Any suggestions on a better one? GBenchmark, google-benchmark?

as far as I can see user need to include benchmark/benchmark.h, so it's okay to name it benchmark

WIP: https://github.com/ruslo/hunter/pull/672

GitHub: https://github.com/google/benchmark

Did this in #1088. Can be close.


Media plugin bug on Android when pressing home and reentering application which calls TakePhotoAsync() again

Steps to reproduce:

After Activity initialization call:
var photo = await CrossMedia.Current.TakePhotoAsync(new StoreCameraMediaOptions{
Directory = SOME_DIRECTORY,
Name = SOME_NAME
});

When you have photo app opened, press HOME button on device.

Reenter the app, go to your activity which calls method above.

InvalidOperationException -> Only one operation can be active at a time.

It doesn't matter if it's Xamarin.Forms or Xamarin.Android, obviously.
Workaround:
In Xamarin.Android just use the standard way with intents and OnActivityResult, or at least you can make some use of intent creation method, from this library.
var media = new MediaImplementation();
var intent = media.GetTakePhotoUI (new Abstractions.StoreCameraMediaOptions {
Directory = DIRECTORY,
Name = NAME
});
StartActivityForResult (intent, ...);

This issue was moved to jamesmontemagno/MediaPlugin#26


Save conflict: left hand diff editor does not update on changes to file

Steps to Reproduce:

have a dirty file
change it outside VS Code
try to save
open the save conflict diff editor
continue to make changes outside VS Code

=> left hand side of diff editor does not update from these changes
We should update the left hand side automatically when changes are being done.

I should see the diff editor auto reloading the file when it's changed externally? I do not see it updating with those changes.

@roblourens I am glad we have verification 👍


Manually detect and force CUDA version passed into install_v2.sh

The install_v2.sh script does not properly detect CUDA installations at the moment (see #255), so we do the detection ourselves in moxin-runner and then pass in the correctly-detected CUDA version as an argument into that bash script.
Partially addresses #255.

Still needs some testing, marking as draft until I can test it thoroughly.


Battleban: Require a battle replay if used outside of a battle

https://www.smogon.com/forums/threads/approved-suggestions.3514540/post-7939081

Oh that’s pretty cool how you can “apply changes.” That makes things a lot easier, thanks even though I just wanted to try it lol


12.1.1 Edit

DO NOT MERGE UNLESS POLL PASSES

Poll passed https://vote.makerdao.com/polling/QmZJVohz
Can be merged.


Plz add Live support for youtube video and speedo meter and quality options as soon as possible

Plz add Live support for youtube video and speedo meter and quality options as soon as possible

bro i m not getting you plz share code for Live support for youtube video and speedo meter and quality options

@shailendra-rajpoot Live youtube video is not supported yet.


Prune data on busy-bot redis db

On busy-bot-master redis db, the keys rsmq:PAST_UPVOTERS_QUEUE and rsmq:PAST_UPVOTERS_QUEUE:Q have each a size of 300K. It seem that these keys only get bigger and bigger and force a database upgrade too often. Can we workout a system to prune this data and keep a stable db size?

@Sekhmet can you size this mission from 1 to 5 effort?


remove vestigal /admin UI

Functionality is now in /, and things have changed sufficiently that this endpoint doesn't even do anything, just shows a empty UI.

Specifically, the /admin endpoint is useless.


Document struct of database objects

@muneeb-ali commented on Thu Oct 08 2015
For using the registrar, the code currently assumes that incoming registrations are stored in a DB and the registrar reads from that DB to process registrations.
The structure of the DB objects is not properly documented yet.

This is now all internally-facing.


Got a Weird Access Violation crash when using connector's latest 1.20.1 version

Mod Name
Connector
Mod Homepage
https://www.curseforge.com/minecraft/mc-mods/sinytra-connector
Minecraft version
1.20.1 (LTS)
Describe the bug
Game crashes, maybe out of memory but mentions a few mods, just dont know if connector is involved
Steps to reproduce
hs_err_pid41528.log
What log said before crash: https://pastebin.com/DDnQTMnA'
Ill try to reproduce it
Logs
https://pastebin.com/DDnQTMnA
Additional context
No response

As our LTS support target, 1.20.1 now only receives critical fixes related to Connector bugs. Please upgrade to the latest version for mod compatibility support.


refactor: split delivery rates according to mech type

Split delivery rates according to mech type.

@DavidMinarsch @Sfgangloff

if mech.is_native_withdrawal() {
}
if mech.is_erc20_withdrawal() {
}

There's no way this is going to be pretty - this means all these interfaces. We still have to introduce something like payment_type value, which makes it a mech type, even if you don't call it so.
Re: ERC-20 - MM still needs to escrow it, there's just no other way. You can't account for allowance() as by the time of delivery the funds could be already gone, so only transferFrom, and thus - escrow. So what do we have? Escrow for pure msg.value, escrow for ERC-20, then why keep pushing for MM having all this burden?
For the Nevermined stuff we discussed that the fee must be managed as pre-paid, and thus all the escrow is going to do is to just check if there's enough credits on a subscription - and transferFrom from subscription and burn on withdraw.
Why having these endless if-else-s in the MM itself when it's super complicated already?
re: marketplaceFee - that's why there's a TODO comment there, as it's not set in stones. Things with subscriptions are more clear now. That is why we need to take all the payment management stuff outside of MM, otherwise we'll keep on redeploying it!

It's safe to remove the staking related stuff no? The activity checking would still function afaik

Should let mech allow to call itself - marketplace will collect fees and could be an interesting use case at best, at worst nothing changes


Write down that "import './b.js'" does read b.ts

Moved from https://github.com/microsoft/TypeScript/issues/37547.
• Document that import ./b.js reads the file b.ts
I use nodejs 13.11.0 with {"type": "module"} in package.json: all .js files are handles as ES6 modules.
I create a file module b.ts:
var m = [1,2,3];
export default m;
and also a.ts:

and
import x from "./b";
console.log(x);

Now, the file TypeScript has actually to import is b.ts. If I write in a.ts import ./b.ts,then the resulting javascript will contain import ./b.ts which does not work and in fact tsc does not allow import ./b.ts.
If I keep import "./b", then the resulting code in JavaScript is import "./b";. This does not work (in Node and in the browser), since the filename to be imported is b.js and the extension has to be specified. See also nodejs/node#32442.
Then the last resort is to write in TypeScript import "./b.js";. This is not logical, as at the time this is read, the b.js file probably does not exist yet and TypeScript has to read b.ts. In fact, TypeScript does exactly this, when I run the process behing strace: On import './b.js'; tsc 3.8.3 reads b.ts.
But this does match the documentation:
At https://www.typescriptlang.org/docs/handbook/modules.html all sample imports do not use file extensions. except in the discouraged examle at https://www.typescriptlang.org/docs/handbook/modules.html#import-a-module-for-side-effects-only .
The final code must contain import "./b.js"; otherwise Node does not find the file.
At https://www.typescriptlang.org/docs/handbook/module-resolution.html it is not described what shall the TS-input contain so that both:
• the result is import "/.b.js"; and
• TypeScript handles the imported file as TypeScript file-module

I'm not sure I want to document this until we have proper support for node's ESM modules - it's still experimental, and our only support is because the classic module resolution happens to work in a some cases but breaks in many many others.

How shall one work with modules/import under Node 13 and TypeScript now, after reading the documentation?  I personally wrote this after I struggled a while.  Yes, the classic module search performed by TS is not the one that is documented, see  https://github.com/microsoft/TypeScript-Website/issues/373, https://github.com/microsoft/TypeScript-Website/issues/371.
Having a team for deveopment and a team for documentation means that on discrepancies between the teams the implemented behaviour is not documented.
Please document the way the software works on import ./b.js: it reads b.ts.

I'm on the compiler team... In my opinion, you should wait until it's not experimental and we have support for it.
That said, you're welcome to use the classic hack, but there's a whole lot of stuff necessary for us to support correct module resolution which still hasn't been decided by the modules working group - we're not going to be supporting it until decisions have been made and are finalized, it's the same thing we do with emcascript features.

In typescript import ./b.ts does not work, I have to use instead import ./b.jsor import ./b.
But if I use babel’s preset-typescript to just cut the type hints from rollup, rollup cannot find b, unless I use import ./b.ts.
There are two kinds of ES6 modules:

a directory module, where import ./b means to handle b as directory containing files, if b is a   directory, or
a file module, where import ./b means to handle b as a file-module, if b is a file.

In particular import ICAL as * from ical.js does mean to use ical.js as directory-module.
In my use case, b.ts exists and b does not exist, so I want to use import ./b.ts.
Please align the behaviour of typescript to the ES6-module behaviour, when it comes to imports:

file extensions are ignored
if X is a directory import X as * from ./X handles ./X as directory module
if X is a file import X as * from ./X handles ./X as file module

For X = Y.ts

if Y.ts is a file import X as * from ./Y.ts does not read Y.js

If X=Y.js is a directory

import X as * from Y.js looks for the directory Y.js in node_modules/

Hi - the website repo isn't really the right place for this discussion, there's already a lot of ongoing in the issues noted in https://github.com/microsoft/TypeScript/pull/35148


[INTERNAL] CodeQL: Schedule at least one execution per week

CodeQL constantly adds new queries

Coverage remained the same at 93.195% when pulling 194b4d91e8c91a4d9ed9cdc3dc06264d9de3cdc1 on codeql-cron-schedule into 049b9ee22f8bf6c1bb41f9ba32be65a8fce38f23 on master.


Links to ODBC (all platforms) and Node.js (Windows) drivers are broken

The links to download ODBC drivers for Ubuntu, Mac, and Windows at https://intersystems-community.github.io/iris-driver-distribution/ lead to status 404 error pages. This appears to be because the main branch of this repository doesn't contain the linked files - it looks like the driver versions have been updated in the repository but the links have not been updated.
Also, the link to download the Node.js driver for Windows has no effect - I see this error in the browser console when I click it:
Uncaught TypeError: document.getElementById(...) is null
iris-driver-distribution:1:10
onclick https://intersystems-community.github.io/iris-driver-distribution/:1

ODBC buttons have now been fixed in the distribution page. There's no Node.js driver for Windows so I've now removed that button


Create the output directory if it doesn't exist

Fixed: #110

Sorry, I completely forgot about the PR in my email deluge. Thanks for cleaning up after me!


TitleBar display issues with ExtendContentIntoTitleBar

Describe the bug
Setting the TitleBar color to a solid color using the following:
<SolidColorBrush x:Key="WindowCaptionBackground">Orange</SolidColorBrush>

causes the underlying content to be occluded.
Changing the value to the following solves the issue:
<SolidColorBrush x:Key="WindowCaptionBackground">Transparent</SolidColorBrush>

however this causes another display issue, with regards to the z-index ordering. The example uses the following layout:
Window->Grid->NavigationView->Frame->Page->Grid->SplitView->Grid->Canvas
When dragging the Image added to the canvas, it then occludes the TitleBar content.
Steps to reproduce the bug
Run application.
Expected behavior
Setting a solid color for the WindowCaptionBackground should not occlude the content that has been extended into the TItleBar.
The content of the NavigationView->Frame should not occlude the content in the TitleBar. Please see screenshots.
Screenshots

WindowCaptionBackground set to Orange:

WindowCaptionBackground set to Transparent, you can see the content added to Navigation.ContentOverlay clearly visible ( TextBlock with wording "Test" ):

Content visible in NavigationView->Frame->...->Canvas:

Content in the canvas is moved/dragged:

NuGet package version
1.1.4
Packaging type
Packaged (MSIX)
Windows version
Windows 10 version 21H1 (19043, May 2021 Update)
IDE
Visual Studio 2022
Additional context
Windows App SDK version is 1.1.5, but option was not available in Nuget package version.

Hi @onslauth ,  thanks for letting us know. It is a known issue and we no longer suggest doing this way. Setting WindowCaptionBackground to Transparent is the way to go. 👍🏾For setting background color, set background color of titlebar element used in SetTitlebar and it will not occlude anything.  Hopefully, that will fix the image issue too
MSDN page on SetTitlebar needs a change too. I am doing a overhaul of winui titlebar under the hood design and hence, the docs are not yet touched yet because they will be touched again.
I am closing this this issue. if it doesn't fix it or you have more related questions, feel free to open it again.


map must lock

// Compare pattern segments to URL.
	if ok, v := handler.try(segments); ok {
		vars[r] = v
		handler.ServeHTTP(w, r)
		delete(vars, r)
		return
	}

对map的操作不加锁会崩溃的

I always felt it was best to let the user handle errors in their http handlers.
What are your thoughts?


Inline datetimepicker time scrollbar not Showing.

The scroll bar is not working in inline view the time is only shown from 00:00 to 05:00.
On clicking the bottom button the is no scrolling.

FWIW, I have NOT experienced this in quite a while with the latest versions.  E.g., the scroll bar DOES appear, HOWEVER it is NOT scrolled to the selected time #31.


Broken icons

Can we fix the broken icons (see png)? Looks like a trivial fix

That is an IG Publisher issue.  I'm not sure how much we can easily do, but we can look into it.
The first thing I'll probably try is updating us to the latest IG Publisher.

The missing files are three: tbl_vjoin_slice.png, tbl_vline_slice.png, and tbl_vjoin_end_slice.png

Fixed some time ago. Closing.


ReplaceNicks is broken after 1.8.0

I use rocketchat <-> telegram bridge. I have
ReplaceNicks=[ ["iprok","Ivan"] ] in rocketchat section. It normally works in 1.8.0 (I have messages from "[rocketchat] " in telegram) and stop working after upgrading to 1.9.0 or 1.9.1 (I have messages from "[rocketchat]  in telegram) without any config change.

Fixed in master now, thanks for reporting


Make types command work with folders

This PR https://github.com/fdiaz/SwiftInspector/pull/41 introduced the types command, but it only works today with files.
Let's extend it to work with folders too.

No longer true, the PR that introduced this command ended up adding that option.

No longer true, the PR that introduced this command ended up adding that option.


Actually call the solver in the parallel AMGX test

I needed to adjust the tolerance of the outer solver to make the test pass for me locally.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #207   +/-   ##
=======================================
  Coverage   88.52%   88.52%
=======================================
  Files          57       57
  Lines        3217     3217
=======================================
  Hits         2848     2848
  Misses        369      369

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 d0f6466...9701fb5. Read the comment docs.

This needs to be rebased.

Squashed and rebased.


Read marker: not updated when scrolling up in the "preview"

To reproduce:

In a room, hit "Jump to read first message" banner
In the "preview", scroll up a few times to display older messages
Leave the preview
Hit again the "Jump to read first message" banner

I expect the read marker to be a bit a below the one from step 2, but it's at the exactly same place.

Not sure I get it, did you also scrolled down at step 2 ?
At the moment, in preview mode, we only update the read marker when the user leaves the preview or goes in background, considering what we are seeing on the screen at that moment. It means that if you scroll down in the preview then scroll up, if when you leave the preview the last visible message is older than the current read marker, it won't be updated.
I'll improve this to regularly save the read marker in the preview and not only when leaving it.

Now, in preview mode, we also update the read marker at the end of scroll (i.e. when the user removed his finger from the screen and the scroll animation is finished).

Validated


chore: Update naming conventions for container graphql and tsx files

Summary by Sourcery
Update naming conventions and refactor components to improve code clarity and maintainability. Enhance documentation to provide clearer guidelines for component and GraphQL file structures.
Enhancements:

Refactor the MembersDetailContainer component to simplify the rendering logic by removing the content function and directly returning the JSX.
Refactor the MembersAccountsAdd component to extract the form submission logic into a separate handleFinish function.
Update the MembersAccountsList component to use the AdminMembersAccountsListContainerMemberAccountFieldsFragment type for data and column definitions.

Documentation:

Expand the documentation in 002-ui-tsx-files.md to include additional rules and examples for React component naming conventions, functional components, and usage of AntDesign components.
Update the documentation in 001-ui-container-graphql-files.md to clarify naming conventions and structure for container GraphQL files.

@sourcery-ai review

@sourcery-ai review

@sourcery-ai review


Log out

Task Test:
In the settings page, user can click the log out button to logout.
When click the logout button, a confirmation message will pop up.
If user confirm the action, the APP will navigate to the login page
If user cancel the action, nothing happens


Rule idea: Enforce using property destructructuring when properties are referred to N > 1 times

A common pattern that I often see (and like) is to use property destructors in render methods.
React Native:
render() {
  const {
    firstName,
    lastName,
    photo,
  } = this.props;

  return <View>
    <Text>{firstName}</Text>
    <Text>{lastName}</Text>
    <Image source={photo} />
  </View>;
}

Since object destructuring is a JavaScript feature and not specific to React, I think this rule would be more appropriate in something more general than a React-specific plugin.

However, #556 and #216 are related, and I could definitely see the value in a rule that required all props and state to always be destructured at the top of component methods.

Yes, definitely.


Bandwidth utilization experiment

We're needing a few features but need to do more investigating to determine which approach we should take. More info in the tracking issue
We want to be able to measure bandwidth utilization over a realistic geographically distributed network using different stacks such as TCP+BBR and QUIC. To close this issue, we should report the bandwidth utilized by a very simple reactor that only sends bytes for each stack. such a branch can be found on this branch. The bandwidth should be measured "back to back", meaning the same exact set of nodes and connections should be used to ensure that the comparisions are meaningful.

This was handled here: https://github.com/celestiaorg/celestia-core/issues/1385


Arrow keys to switch files

@DecathectZero don't forget to change the keyboard shortcut help window too.


Funkin Forever maintinence / potential deprecation

cam edit: original title from eric was "both of these are gone"

were there any archives of these? or just gone forever...

Forever Engine is in a weird state because the original author deleted everything.
I believe this person is maintaining a fork still? https://github.com/crowplexus/Forever-Engine/

So is current Forever Engine repo is being worked on? or is work being done on another fork / repo somewhere (also renaming this PR!)

(also #160 also seems to add some links to Forever Engine related stuff)

So is current Forever Engine repo is being worked on? or is work being done on another fork / repo somewhere (also renaming this PR!)

well, it’s more of a community continuation because the original owner had some very bad history, and they deleted all of their socials, including GitHub, so this is more of a continuation from the original Forever engine to dissociate it from the original owner

So is current Forever Engine repo is being worked on? or is work being done on another fork / repo somewhere (also renaming this PR!)

The link Eric sent is the right Forever Engine repo. New updates goes there as well


Where do I download it

title

It's not released yet, you'd have to build it from source.
git clone https://github.com/samolego/MobDisguises.git
./gradlew build

Then go to fabric/build/libs or forge/build/libs.
Note that it might not be stable yet


Replace the thermistor spec

Sadulli currently uses KTY81/120 (the other models specified in the mfg docs are not used), identified as KTY81_120 in Telega v0. As it has reached EOL, it has to be replaced with an alternative that is still available for purchase, such as KTY81/110, KTY81/121, KTY81/122, or KTY81/150.
The spec needs to be updated to contain only the above-listed thermistors plus the original KTY81/120.

I added two more suitable alternatives here.


Problems with Polling Sensor

Hello everybody,
I can't get any further, I just can't get the sensor to work anymore.
It worked once, suddenly it disappeared and I get the following error message:
Traceback (most recent call last):
File "/config/custom_components/fasthue/sensor.py", line 42, in async_setup_entry
device = next(
StopIteration
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 250, in _async_setup_platform
await asyncio.shield(task)
RuntimeError: coroutine raised StopIteration
I also reinstalled the bridge and Fast Hue, nothing helps. The sensor just doesn't show up anymore!
Can you help?
Merci

Hi @clipse2004,
If you are using HA >=2021.6.0, now the Hue integration has local push communications with the Hue bridge (see #22), so this custom integration is not necessary anymore, as hue cannot be faster than that :)
You should remove it 👍

Oh damn, I noticed something new there. However, I did not know that this replaces the pooling :/
And I would like to beat my ears to find the error :D
Thank you!


Fix typo

Thanks for maintaining this website. The tutorial is pretty useful :smiley:
Noticed this small typo when reading through it.
-If this code
+In this code

@googlebot I signed it!


Set constant SPAN_BUILTIN with netcoreapp2.1 AND later .Net versions

Thanks. Can you retarget this PR to the v2.6 branch? I'll need to service that version as well.


Update 0038-OLIQ to match implementation

During discussions it was found that the core implementation is as it should be, however, the spec should be updated to make it clearer:
From https://github.com/vegaprotocol/vega/issues/6904 ->
According to 038-OLIQ:

Note: if the resulting price for any of the entries in the buy / sell shape is outside the valid price range as provided by the price monitoring module (the min/max price that would not trigger the price monitoring auction per triggers configured in the market, see price monitoring spec for details) it should get shifted to the valid price that's furthest away from the mid for the given order-book side. If the reference price itself is outside the valid price range the order should get placed at - when bid/ask is used as a reference, or one tick away from it - when mid is used as a reference.

The price monitoring bit works fine in isolation, the reference price outside bounds bit works fine when BID/ASK is used as a references however when MID is used as a reference and:

MID is above the max valid price bound the sell side is deployed as expected, however the buy side gets placed at the lower valid price range bound,
MID is below the min valid price bound the buy side is deployed as expected, however the sell side gets placed at the upper valid price range bound.

See https://github.com/vegaprotocol/vega/pull/6902/files for details (test passes now, but associated comments point at the problems)

closing as superseded by:L

https://github.com/vegaprotocol/specs/pull/1438


oEmbed Url Previews Handler

Idea
A Rocketlet can register a url it would like to add additional information to the request of the oEmbed information request.
Example
Rocketlet which allows for a GitHub authentication information to be attached to oEmbed requests out to GitHub, this way links to private repositories can have their information shown instead of showing nothing.

Wrong repository :see_no_evil:

Moved: https://github.com/graywolf336/temporary-rocketlets-ts-definition/issues/22


Switch to emotion or styled-components instead of styled-jsx.

styled-components
emotion

I think that now we can close this issue because now we are using CSS modules instead of CSS in JS approach.


CI: fix create release workflow

Summary
By some reason push event is not being triggered on version tags (Lerna implementation? :thinking: ), so I'm trying with on.create event now, then checking tag name on job level condition.
Related to https://github.com/netlify/netlify-cms/pull/3930

Test plan
N/A

A picture of a cute animal (not mandatory but encouraged)

Hey @erezrokah ,
Yup, I've read both too, but generally new tags are created with a push, in many repositories I use a very similar workflow with on.push.tags, as example:
https://github.com/ecomplus/client/blob/master/.github/workflows/create-release.yml => https://github.com/ecomplus/client/actions?query=workflow%3A"Create+release"
So, I still don't know why it didn't work here :thinking:
Anyway, on.create should work I guess...

Ahh @erezrokah ,
I realized now that publish commit is done by action-user, and automatic commits by action-user never trigger another workflow, so the problem is not the workflow itself, change the event will not work anyway...
I'll take another look here further.

I realized now that publish commit is done by action-user

That's actually something we've just added...


[Feature] add an expiration date for cached items

is there a way to add an expiration date to the cached/stored items so it can be cleared automatically ?

Since the various browser storage methods aren't designed primarily for caching but are general purpose implantations this isn't backed in, neither in the browser storage implementations nor in localforage implementations. I would suggest to create a different helper service for your data access calls, which would wrap your data in an other object containing such lifetime statistics (create date, expression date).

do something like that
export default {
get: async (key) => {
    let { expire, value } = await localForage.getItem(key);

    if(expire < Date.now()){
        localForage.removeItem(key);
        return null;
    }

    return value;

},
set: async (key, value, expire = false) => {

    if(expire && typeof expire === 'number')
        expire = Math.round(expire * 1000 + Date.now()); // * 1000 to use seconds

    return await localForage.setItem(key, { value, expire });

}

}

It will be nice If localforage has official support for expiration.

As mentioned by @thgreasi, this isn't something we want to support in core as we've designed localForage to be a bit more general-purpose. Adding an expiration mechanism/helper should be straightforward, but as it's more useful for caching than generic storage, I don't think it's appropriate to include in localForage core.

I think the generic storage some times need expiration too.

I'm not 100% sure about that @ferco0 :thinking:
None of the generic browser storage mechanisms (localStorage, webSql, IndexedDB) have the concept of expiration in them, nor the filesystem on my computer.
While having the cache user case in mind though, it definitely makes sense to support expiration dates for keys. Perhaps this could be implemented as an extension for localForage.
Skeleton of a backwards compatible solution:
Given a user defined localForage instance "A" with a store "Sa", the extension should maintain a separate localForage instance "A-exp" with its own store "Sa-exp", that for each key of "A" that needs to have an associated expiration, it will hold the expiration date using the same key on "A-exp".
The extension would extends the setItem() method to allow amn optional object third argument that will look like: setItem('test', 'testValue', { expiration:<PHONE_NUMBER>755 }); .

what i want to say is that, us developers, sometimes need this feature.

I went ahead and created a wrapper around localforage that adds this capability called "localforage-cache".

I'm not 100% sure about that @ferco0 🤔
None of the generic browser storage mechanisms (localStorage, webSql, IndexedDB) have the concept of expiration in them, nor the filesystem on my computer.

Cookies do.

Cookies aren't a storage mechanism, or at least not like that. They're a way for a client and a server to exchange information and maintain state in an otherwise stateless transaction.
Sure, you can use cookies as storage the same way you can use generic browser storage mechanisms (localStorage, WebSQL, IndexedDB) to store a JWT and maintain state with an API, but the design of cookies isn't to be generic storage. For instance: cookies usually have a storage limit of about 4kB, compared to localStorage's 5MB. Even the 5MB offered by localStorage isn't amazing, but it's orders of magnitude better and illustrates why cookies shouldn't be considered a generic storage mechanism. You'd struggle to cache a single image file or even a small cache of API/app state data for a modest app in 4kB.
So: I don't think it's constructive to bring them up in this discussion, particularly in an issue that's been closed as something core of localForage doesn't aim to fix and with a contributor pointing out they released a library with this feature: https://github.com/localForage/localForage/issues/774#issuecomment-599208849.

Cookies aren't a storage mechanism

I think we'll have to agree to disagree on that one.
Sorry if my comment wasn't constructive, I'll use LuddJanssen's wrapper or write my own.

I don't get it. What all this resistance against natural evolution. Sure, thanks for creating this library. But ultimately a library is nothing if it doesn't fulfill its user's needs. Features that come out of any library are consumer-driven. If the very people who have decided to trust and use this library are asking for a feature, why is it being shut down with such energy?
Whether the underlying storage layers are using an expiration date or not, that should not be a justification for not implementing it. For instance, many things now exist in Javascript because they grew in popularity thanks to some open source libraries. For instance, there is a great chance that we will soon has LESS or SASS style CSS preprocessor available in web browsers and Chrome already has some experimental flag for using mixins.
Whether the underlying storage layers are using an expiration date or not, that should not be a justification for not implementing it. For instance, many things now exist in Javascript because they grew in popularity thanks to some open source libraries. For instance, there is a great chance that we will soon have LESS or SASS style CSS preprocessor available in web browsers and Chrome already has some experimental flag for using mixins.

I need to store a lot of data to avoid requesting them again from a given user on the same computer. The stored data is not sensitive.
When the user logs out, and another user logs in, the data for the new user should be separate from that of the previous one. And this scenario should scale up if more that one user routinely accesses that computer.
If one of the previous users does not connect for an extended amount of time, then the corresponding data should be removed

The data does not need to be automatically garbage collected. But it can be done opportunistically by the localForage library on access (read or write) in an efficient manner with little impact of the page's performance. But that is an implementation detail that is out of scope for now. It would seem like @LuudJanssen already did it anyway.
The main message I was to pass along is that there are many libraries and software out there that led to the creation of even better forks because they didn't listen to the developers that were using them in a first place. Checkout MySQL vs MariaDB for instance. MariaDB is by a landslide more feature-rich than MySQL and depending on which version of MySQL you are using, MariaDB is a drop-in replacement.

I'll chip in real quick, because of my efforts to create the localforage-cache package.
Surprisingly, I think I actually agree with @tofumatt and @thgreasi here. Libraries need to set their boundaries of what to support and what not to support. React could add a component library to their core react implementation, but they don't, because it's out of the scope of the library.
Similarly, I think Localforage's soul purpose is to abstract away API's for different browser storage solutions and create one unified API. It's purpose is not to add features on top of these storage API's, like expiry.
Don't get me wrong, there's clearly a need to be able to set expiry dates for browser storage entries, else I wouldn't have created the wrapper. I just think that it would make more sense to create a separate package which uses localforage underwater, but adds caching functionality on top of it (with expiry dates for example). That way localforage can keep its purpose as a library to unify browser storage API's, and another package has the purpose to create a cross-browser cache storage.
I get what you're saying @asiby, but in this case I think localforage is not really comparable to MySQL, because MySQL was designed and intended to have a lot of features. Localforage's use case is just different, because it's intended to do one thing, and do that thing very very good, which is to provide a generic API for browser storage solutions.
I think this issue / discussion is actually a good sign of the need for a new open source project which creates a generic caching solution for the browser. localforage-cache isn't that, but it might be a start for someone looking to create such a package.

Yeah, to be clear, I'm working on a new site for localForage and want to feature plugins, extensions, and other libraries that it works well with. localforage-cache would be on that list for sure. I like the idea of that library, it's just that it isn't a feature that:

all users require
is better-implemented in the core library (or can only be implemented by the core library)
is trivial to maintain by the core maintainers (@thgreasi and myself)
is in the scope of what the core maintainers want localForage to be

It's really lovely to see libraries like a caching library come about using localForage, but implementing it in the core of the library doesn't have any clear benefits in usage to me, but is a burden for the core maintainers and extra complexity for a reduced use-case.
I'm very happy and not resistant to seeing the abilities of localForage grow, but please note that we don't even include features like getItems in localForage core, but rather as separate modules: https://github.com/localForage/localForage-getItems. We consider that a localForage-backed repo, but we don't ship it in core because we don't think it covers the use-case for the broadest of localForage users. I've used our extensions to localForage, but only in a fraction of apps I've used the very core of localForage in.
So it's a balancing act, and here we're saying "not in core". But we've always said that we'll happily (and do) promote third-party extensions and tools. We are also open to including them in the localForage organisation implying more "official support" if the conditions are right.
I think that's all to say on the subject, but thanks for everyone's feedback. Not resisting more features, but trying to direct them to the right place 🙂

Thanks guys for the explanations. I am now convinced that you did the right thing. Keep up the good work.


New version: TopalaSoftwareSolutions.SIW version 2022.03.17c

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.1 schema?


Add types on tests

Which issue(s) this PR fixes

Fixes None
Additional comments

Add types on tests parameters to help identify errors in test implementation.
Display command output when cli test fails

Agreements

[X] I hereby declare this contribution to be licensed under the Apache License Version 2.0, January 2004.
[X] I hereby agree to grant TOSIT a copyright license to use my contributions.

tdp/core/models/test_deployment_log.py line 329 (def test_one_stale), parameter minimal_collections is a Collections instance.

Didn't see it as it was done in a previous commit. Thx, I fixed it.

When I execute tdp service-versions, I have the following error :
2023-08-11 18:30:50,262 - DEBUG - tdp.<module> - Logger initialized
Traceback (most recent call last):
  File "/home/mdrutel01/projets/git/tdp-ops/venv/bin/tdp", line 6, in <module>
    sys.exit(tdp())
  File "/home/mdrutel01/projets/git/tdp-ops/venv/lib/python3.9/site-packages/click/core.py", line 1128, in __call__
    return self.main(*args, **kwargs)
  File "/home/mdrutel01/projets/git/tdp-ops/venv/lib/python3.9/site-packages/click/core.py", line 1053, in main
    rv = self.invoke(ctx)
  File "/home/mdrutel01/projets/git/tdp-ops/venv/lib/python3.9/site-packages/click/core.py", line 1659, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/mdrutel01/projets/git/tdp-ops/venv/lib/python3.9/site-packages/click/core.py", line 1395, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/mdrutel01/projets/git/tdp-ops/venv/lib/python3.9/site-packages/click/core.py", line 754, in invoke
    return __callback(*args, **kwargs)
  File "/home/mdrutel01/projets/git/tdp-ops/tdp/tdp-lib/tdp/cli/commands/service_versions.py", line 30, in service_versions
    + tabulate(
  File "/home/mdrutel01/projets/git/tdp-ops/venv/lib/python3.9/site-packages/tabulate.py", line 1528, in tabulate
    list_of_lists, headers = _normalize_tabular_data(
  File "/home/mdrutel01/projets/git/tdp-ops/venv/lib/python3.9/site-packages/tabulate.py", line 1191, in _normalize_tabular_data
    rows = list(map(list, rows))
TypeError: 'ComponentVersionLog' object is not iterable


Add documentation for all commands

I'm wondering whether we want to include this in the documentation. I've checked the main README file, it currently does not provide a complete list of all commands (e.g. bash-it reload). We might want to add that at one point - probably as a separate PR when (hopefully at one point) rework the documentation.
Originally posted by @nwinkler in https://github.com/Bash-it/bash-it/pull/1672#issuecomment-709528853

There are so many commands. Well making a proper markdown for each command should be done in docs folder and then use it to serve documentation on readthedocs.io

I guess it is a possible solution, although we already cover some of the commands in the readme.md. I want the easiest and cleanest way we can do it

As part of the discussion to happen in https://github.com/Bash-it/bash-it/issues/1678 I have both composure about descriptions and bashdoc annotations. For example. running a bash-it help plugins all (a new helper I added to show about descriptions for all enabled plugins + core functions) will print:
bash-it:core
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
_bash-it-backup                              backs up enabled components (plugins, aliases, completions)
_bash-it-describe                            describes bash-it components by listing the component, description and its status (enabled vs. disabled)
_bash-it-disable                             disable a bash-it component (plugin, component, alias)
_bash-it-doctor                              reloads a profile file with a BASH_IT_LOG_LEVEL set
_bash-it-enable                              enable a bash-it component (plugin, component, alias)
_bash-it-grep                                outputs a full path of the grep found on the filesystem
_bash-it-reload                              Reloads the bash profile that corresponds to the correct OS type (.bashrc, .bash_profile)
_bash-it-restore                             restores enabled components (plugins, aliases, completions)
_bash-it-show                                List available bash_it components or allow filtering for a specific type e.g., plugins, aliases, completions
_bash-it-update                              Updates the bash-it installation by fetching latest code from the remote git
_bash-it-version                             Shows current bash-it version with the Current git SHA and commit hash

bash-it:core:cache
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
_bash-it-component-cache-add                 gets the component cache path in the /tmp directory
_bash-it-component-cache-clean               caches the component view in the /tmp directory

bash-it:core:components
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
__check-function-parameters                  check the passed parameter to make sure its valid and matches a component type
_bash-it-component-help                      show the about description for a component
_bash-it-component-item-is-disabled          checks if a given item is disabled for a particular component/file-type
_bash-it-component-item-is-enabled           checks if a given item is enabled for a particular component/file-type
_bash-it-component-list                      returns a list of items within each component (plugin, alias, completion)
_bash-it-component-list-disabled             returns a list of disabled items within each component (plugin, alias, completion)
_bash-it-component-list-enabled              returns a list of enabled items within each component (plugin, alias, completion)
_bash-it-component-list-matching             returns a list of items within each component (plugin, alias, completion) that match a string
_bash-it-pluralize-component                 pluralize component name for consistency especially for search
_bash-it-singularize-component               singularize component name for consistency especially for search

bash-it:core:help
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
_help-aliases                                shows help for all aliases, or a specific alias group
_help-completions                            summarize all completions available in bash-it
_help-plugins                                summarize all functions defined by enabled bash-it plugins

bash-it:core:utils
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
_array-contains                              searches an array for an exact match against the term passed as the first argument to the function
_array-dedupe                                creates a concatenated array of unique and sorted elements
_clean-string                                cleans a string from whitespace give a passed cleaning mode
_command_exists                              check if the command passed as the argument exists
_is_function                                 check if the passed parameter is a function
_read_input                                  reads input from the prompt for a yes/no (one character) input

bash-it:log
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
_bash-it-get-component-name-from-path        get a component name from a component path
_bash-it-get-component-type-from-path        get a component type from a component path in a singular form (alias, plugin, completion)
_log_component                               log a component loading message by echoing to the screen the name and type
_log_debug                                   log a debug message by echoing to the screen
_log_error                                   log an error message by echoing to the screen
_log_general                                 internal function used for logging, uses BASH_IT_LOG_PREFIX as a prefix
_log_warning                                 log a warning message by echoing to the screen

bash-it:search
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
_bash-it-component-term-matches-negation     matches the negation of the search term entered
_bash-it-search                              searches for given terms amongst bash-it plugins, aliases and completions
_bash-it-search-component                    searches for given terms amongst a given component

Thanks - good thoughts, all!
The composure documentation of the functions is great, although it only provides help for the actual functions (with the underscore prefix). We should definitely add that, but it's only one option. Some more thoughts:

The README file is already crowded as it is. It needs some major rework.
I had thought about adding more documentation to the repo's Wiki instead of the README.
@tbhaxor's suggestion about generating the documentation is great - potentially we could generate the Wiki from that documentation.
We already have a bash-it help command, but it does not go into detail on each subcommand. How about adding support for things like bash-it help reload. The documentation could be sourced from @ahmadassaf's about documentation.

Thoughts?

I guess it is a possible solution, although we already cover some of the commands in the readme.md. I want the easiest and cleanest way we can do it

Then i would ask you to go for readthedocs.io as it support in document searching also

Great thoughts everyone :smiley:
My votes:

use generation of some kind (composure is probably not enough)
preferably include an enumerated list of functions and aliases found in each file, possibly with annotation parsing for documenting them
break up the documentation as the readme is already big
no preference on readthedocs vs wiki, but only use one

I wish there was a "subscribe" button on GitHub mobile app...

This issue is something that I am looking into right now, really want to improve our docs

I'd like to suggest something like shocco for file-level comments/documentation. I'm a huge fan of "literate programming" for code-level  documentation as the documentation is in the code! Single source of truth, harder to forget to update, easier to refer to when coding, &c.
(Not-code-level documentation should be separate, or the code gets unreadable. I've made that mistake in other projects.)


If a log is sent as discord attachment, it will upload it to the SMAPI site.

If someone sends a log as a discord attachment, the bot will send the URL on the smapi site to the channel.
I don't know what happened with commit/changes if I'm going to be honest, I used VSC for it so blame microsoft™.

Whoops didn't mean to press the request a review button, sorry

The console thing was from testing, I'll fix the indents and I changed the end of line sequence to LF, but won't that change the git history again?

When I go to accept the pull request, I can squash all the changes into a single commit, which should then only show the actual changes made.

Everything looks good. I'll do some testing to make sure once I have some free time later today, but nothing sticks out to me for now.

This is pretty slick. The one thing to note is that if an invalid SMAPI log is processed, the bot will throw an index error when attempting to parse the URL. I think the odds of this are pretty low, if someone is uploading a file with that exact filename, it's probably valid, but it's something I'll keep an eye on in the future.


[BUG]  unable to read SD

Downloaded the newest software of MIB2 but enable to read SD card when updating, not sure if I’ve done something completely wrong
installed SW train version
MST2_EU_VW_PQ_PO245T
SW MU Version
0245
part number
5C0035680C
SW version
H25.14.78_STD2NAVPQ_EU

Wrong toolbox. this is for MHI, you have MST ;-)
go here: https://github.com/olli991/mib-std2-pq-zr-toolbox

Downloaded the newest software of MIB2 but enable to read SD card when updating, not sure if I’ve done something completely wrong
installed SW train version
MST2_EU_VW_PQ_PO245T
SW MU Version
0245
part number
5K70_EU_VW_PQ_P2045T
SW version
H25.14.78_STD2plusPQPQ_EU

Did you even read the messegaes in this thread?

Hello hello Yes I managed to sort it all out had to swap the cpu file from the toolbox 👍👍On 11 Aug 2024, at 00:36, Olli @.***> wrote:
Did you even read the messegaes in this thread?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Hi,  Thanks for your reply.
My car is VW sharan. Mib not have navi button and only one sd slot.


Theme color - "Continue" button color in checkout steps

Umbraco Commerce Checkout version - 12.0.0 and Umbraco version 12.2.0
Theme color (uccThemeColor) "black" is not working. bg-black css is missing. Other colors are working.
How to make new theme colors work?

Looks like we might need to update the safe list to include this https://github.com/umbraco/Umbraco.Commerce.Checkout/blob/main/src/Umbraco.Commerce.Checkout/Client/tailwind.config.js#L10

Thanks for the quick reply. Your solution would fix black backgroud color. Thats great.
Is it customizable to add new color theme to the data type "[Umbraco Commerce Checkout] Theme Color Picker"

ok. Can you guide me to create a custom build?

You should be able to fork the repo, make the changes you need and then in the root of the solution run dotnet pack Umbraco.Commerce.Checkout.sln --configuration Release --output artifacts which should compile a custom NuGet package into an artifacts folder. You can then followin instructions here for using the artifacts folder as a local NuGet feed https://learn.microsoft.com/en-us/nuget/hosting-packages/local-feeds

Thanks a lot for support.

Fixed on 10.0.3, 12.0.2 and 13.1.1.


[Feature] Generating Sessionid with Xendit's public key

Generating Session Id using Xendit's Public key

the code LGTM


Refactor TestExternalities

As I wanted to extend functionnalities of TestExternalities it seems I ended up just copying the Ext implementation with InMemory backend and thins.
I can't make use of Ext directly because TestExternalities would be a self referencing struct.
I think we could update the test to create TextExternalities in two call one for creating backend stuff and another one for creating the referencing Ext.
Also test could make use of with_storage. All in all it seems code is redundant between TestExternalities, BasicExternalities and Ext

I am not much aware of everything that happens under the hood when you simply create an externalities (storage, backend etc.) so can't judge much, but already had in mind to propose:

We can make an approach like the ExtBuilder sort-of standard and refactor all modules to use it + isolate the struct in a generic way (if possible) as the standard substrate test framewrok.

Not sure if it is possible but having some kind of a before_each() and afte_each() in my fantasies also sounded nice-to-have.

maybe we can do that:
impl<H: Hasher> TestExternalities<H> where H::Out: Ord {
       /// Return externalities
       pub fn ext(&mut self) -> Ext<H, InMemory<H>, ChangesTrieInMemoryStorage<H>, NeverOffchainExt> {
               Ext::new(&mut self.overlay, &self.backend, Some(&self.changes_trie_storage), None)
       }
}

and then in most test we have to add .ext() I have a wip branch there, note test of sr-api-macros fails for a reason still unknown to me. https://github.com/paritytech/substrate/tree/gui-refactor-test

Okay, I see your changes but I see that we are sorta not on the same page and maybe they should be different issues. What I envisioned and wanted to add was a way to minimize the boilerplate needed to set up the test. I should talk to you in person about this.

My main concern was I wanted to use Ext and InMemoryBackend stuff as much as possible instead of a custom implementation of Externalities.
Yes sure

might be easier to solve with https://github.com/paritytech/substrate/pull/3793

Test externalities is refactored, maybe we can improve test tools in general but this is another issue.


bugbash - Zip deployment failed

Information:

Tools Libraries: AZ CLI
Libraries' Versions: Latest everything. AZ CLI from bug bash
OS: Win 10

Issue Description:
Zip deployment is reported as failing, although it appears to work.
Reproduction Steps:

From bug bash, run scenario 1 with yeoman/Typescript
Run the az bot publish... command towards the end

Adding the --debug flag didn't really help:

Seems to be happening for other users and scenarios, as well.
Expected Behavior:
No errors for a successful zip deployment.
Actual Results:
Zip deployment reports as failed, although appears to succeed (except maybe with build).

JS Sample 12. NLP-with-LUIS worked fine. I wonder if it's an issue with the generator and the post-install-script that's causing issues, since this sample does not have a post-install script.

Dupe of #987


Implement Reorg Changes Outbound Tx Index

Reorg Changes Outbound Tx Index
An outbound, unconfirmed transaction in a specific block changes height in the event of a reorg
The wallet handles this change, reflects it appropriately in local storage, and funds remain spendable post confirmation.
Pre-conditions:

Wallet has spendable funds

Setup w/ default dataset
applyStaged(received_Tx_height)
sync up to received_Tx_height
create transaction
stage 10 empty blocks
submit tx at sentTxHeight

a. getIncomingTx
b. stageTransaction(sentTx, sentTxHeight)
c. applyheight(sentTxHeight + 1 )

sync to  sentTxHeight + 2
stage sentTx and otherTx at sentTxheight
applyStaged(sentTx + 2)
sync up to received_Tx_height + 2
verify that the sent tx is mined and balance is correct
applyStaged(sentTx + 10)
verify that there's no more pending transaction

https://github.com/zingolabs/zingolib/pull/627
completed but fails due to bugs already reported


Collapse indicator dont match the collapse state of categories

Actual behavior:
Set Collapse after how many categories of the Local Menu Component to something less then 5.

Reproduce steps:
Set Collapse after how many categories of the Local Menu Component to something different then 5.
Version:
TI: v3.0.4-beta.27
Local: v1.10.0
Fix
Use $menuCollapseCategoriesAfter instead of 5 in the grouped.blade.php on line 11

Your commit looks good as a fix.. Open a PR! Thanks.

PR is created :)


fix memery leak bug

You should have called Py_DECREF to release the memory allocated by Py_BuildValue

@bergundy @dvirsky Can you review this code for me? This library is required for my project.
Thanks!


Test using latest Python in Grabl

What is the goal of this PR?
To investigate whether it's possible to build the current client-python in Grabl with the Python version installed in Grabl.

This PR should be deleted once Max's PR (that it is based off) is merged.


Client just crashes on Quest 2

Description

When running the server on Linux, the Client crashes almost immediately after displaying a status message (like "Waiting for server" or "Stream will begin soon", depending on the server's state) for a brief moment on my (up-to-date) Oculus Quest 2.
Here's what the Dashboard log says:
11:32:38.081261568 | [INFO] | ClientConnected
-- | -- | --
11:32:38.081562983 | [INFO] | Serial Number: 1WMGH000XX0000
11:32:38.081580674 | [INFO] | Model Number: Miramar
11:32:38.081591276 | [INFO] | Render Target: 3648 1920
11:32:38.081602108 | [INFO] | Seconds from Vsync to Photons: 0.005000
11:32:38.081611212 | [INFO] | Refresh Rate: 90
11:32:38.082914664 | [INFO] | CEncoder::Run
11:32:38.083028157 | [INFO] | CEncoder Listening
11:32:38.085217964 | [INFO] | CEncoder client connected, pid 4704, cmdline /home/tcrass/.steam/steam/steamapps/common/SteamVR/bin/linux64/vrcompositor
11:32:38.091158900 | [INFO] | Setting new IPD to: 0.061007
11:32:38.164709128 | [INFO] | failed to create VAAPI encoder
11:32:38.165232036 | [INFO] | failed to create NvEnc encoder
11:32:38.181131742 | [INFO] | using SW encoder
11:32:39.667017879 | [INFO] | ClientDisconnected
11:32:39.667058782 | [INFO] | Client disconnected. Cause: At alvr/sockets/src/control_socket.rs:32: Connection reset by peer (os error 104)

General Troubleshooting

[x] I carefully followed the instructions in the README and successfully completed the setup wizard
[x] I read the ALVR Wikis here and here

Environement
Hardware
Note: for Linux, an upload to the hw-probe database is preferred: hw-probe -all -upload
https://linux-hardware.org/?probe=bc0462d8e3
CPU:
GPU:
Audio:
Installation
ALVR Version:
17.0.1+1643781622+0541c19e on both client and server
SteamVR Version:
1.20.4
Install Type:

[x] Packaged (exe, deb, rpm, etc)
[ ] Portable (zip)
[ ] Source

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions):
Debian GNU/Linux 11 (bullseye) (up-to-date)

Disabling audio streaming fixed that issue but now I don't have audio. Found this workaround here: #923 (comment)

Confirmed, disabling audio streaming in the Dashboard prevents the client from crashing. But still no VR -- see https://github.com/alvr-org/ALVR/issues/964

Hi
this is from your log...
11:32:38.164709128 | [INFO] | failed to create VAAPI encoder
11:32:38.165232036 | [INFO] | failed to create NvEnc encoder
11:32:38.181131742 | [INFO] | using SW encoder
Can you install ffmepg properly so you've got hardware video encoding? on AMD you'll need VAAPI and you should get a video output

Hi this is from your log... 11:32:38.164709128 | [INFO] | failed to create VAAPI encoder 11:32:38.165232036 | [INFO] | failed to create NvEnc encoder 11:32:38.181131742 | [INFO] | using SW encoder

Yea, I was wondering about that... Haven't experienced any video decoding issues so far, so I was surprised to see that encoding acceleration support was not available in ALVR.

Can you install ffmepg properly so you've got hardware video encoding? on AMD you'll need VAAPI and you should get a video output

What do you mean by "properly"? I've had the default ffmpeg package installed for ages and used it numerous times for transcoding purposes.
Cheers --
Torsten

OK, after deleting my .config/alvr/session.json I started all over again with default settings. And with the default of 75% video resolution I do get a decent framerate of 30 fps -- still crappy compression artifacts, though. And -- according to the log -- still no harware-accellerated video encoding. Not great, but at least enough to start developing VR applications with Godot ;-)
Should I open a new issue for the fact that there's no hardware accelerated encoding support on Debian Stable?

Disabling audio streaming fixed that issue but now I don't have audio. Found this workaround here: #923 (comment)

Confirmed, disabling audio streaming in the Dashboard prevents the client from crashing. But still no VR -- see #964

so what the solution? playing without sound? i have the same issue


hello,thank you share,

How to use it?

[root@localhost ~]# cd dnsdigger
[root@localhost dnsdigger]# ls
dns.go  dns_test.go  go.mod  go.sum  LICENSE  README.md
[root@localhost dnsdigger]# ./dns.go
-bash: ./dns.go: Permission denied
[root@localhost dnsdigger]# chmod +x dns.go
[root@localhost dnsdigger]# ./dns.go
./dns.go: line 1: package: command not found
./dns.go: line 3: syntax error near unexpected token `newline'
./dns.go: line 3: `import ('
[root@localhost dnsdigger]# ls
dns.go  dns_test.go  go.mod  go.sum  LICENSE  README.md
[root@localhost dnsdigger]# cat /etc/redhat-release
CentOS Linux release 7.7.1908 (Core)
[root@localhost dnsdigger]#

This is setup as a library, not a command line tool.  You need to setup your own project and import this to use it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Optimised vendor libraries

This is a really useful benchmark, just what I was looking for!
I was wondering if there would be a difference if bundled, optimised vendor bundles were used along with unbundled app modules.
Something like ReactHN using react.min.js but it's own scripts unbundled
Would load times improve enough to be as good as bundled or at least good enough to the point where the gains in caching might be a decent tradeoff for larger load times?

Hey @bkazi, thank you! Sorry for the late reply, only saw this now.
As part of the build process, this does do minification for both the bundled and unbundled versions. This is not the same minification that the original projects did, I'm sure, but I needed something consistent across all three versions.
In any case, the numbers you get from the bundled versions that this produces should be similar to if you were to use the foo.min.js.
Hope this helps!


python312Packages.aiohomekit: 3.1.5 -> 3.2.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.aiohomekit is: Python module that implements the HomeKit protocol
meta.homepage for python312Packages.aiohomekit is: https://github.com/Jc2k/aiohomekit
meta.changelog for python312Packages.aiohomekit is: https://github.com/Jc2k/aiohomekit/releases/tag/3.2.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.2.0 with grep in /nix/store/l5y1sqyi41yp2sv87yfrh7vk031d21gs-python3.12-aiohomekit-3.2.0
found 3.2.0 in filename of file in /nix/store/l5y1sqyi41yp2sv87yfrh7vk031d21gs-python3.12-aiohomekit-3.2.0

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath

home-assistant-component-tests.homekit_controller
python311Packages.aiohomekit
python312Packages.aiohomekit

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/l5y1sqyi41yp2sv87yfrh7vk031d21gs-python3.12-aiohomekit-3.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.aiohomekit https://github.com/r-ryantm/nixpkgs/archive/4651aba5fbfb3d3cf39cb66f87b4cfb8d475517a.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/4651aba5fbfb3d3cf39cb66f87b4cfb8d475517a#python312Packages.aiohomekit

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/l5y1sqyi41yp2sv87yfrh7vk031d21gs-python3.12-aiohomekit-3.2.0
ls -la /nix/store/l5y1sqyi41yp2sv87yfrh7vk031d21gs-python3.12-aiohomekit-3.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

home-assistant-component-tests.homekit_controller

4 packages built:

python311Packages.aiohomekit
python311Packages.aiohomekit.dist
python312Packages.aiohomekit
python312Packages.aiohomekit.dist

Maintainer pings
cc @fabaff for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.aiohomekit is: Python module that implements the HomeKit protocol
meta.homepage for python312Packages.aiohomekit is: https://github.com/Jc2k/aiohomekit
meta.changelog for python312Packages.aiohomekit is: https://github.com/Jc2k/aiohomekit/releases/tag/3.2.1
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.2.1 with grep in /nix/store/l807sxl3pdd6kbf2dpz8vyhrjbqhhyly-python3.12-aiohomekit-3.2.1
found 3.2.1 in filename of file in /nix/store/l807sxl3pdd6kbf2dpz8vyhrjbqhhyly-python3.12-aiohomekit-3.2.1

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath

home-assistant-component-tests.homekit_controller
python311Packages.aiohomekit
python312Packages.aiohomekit

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/l807sxl3pdd6kbf2dpz8vyhrjbqhhyly-python3.12-aiohomekit-3.2.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.aiohomekit https://github.com/r-ryantm/nixpkgs/archive/e98a5315e7e896e5ac1165582a497c47eb2fc6ce.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e98a5315e7e896e5ac1165582a497c47eb2fc6ce#python312Packages.aiohomekit

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/l807sxl3pdd6kbf2dpz8vyhrjbqhhyly-python3.12-aiohomekit-3.2.1
ls -la /nix/store/l807sxl3pdd6kbf2dpz8vyhrjbqhhyly-python3.12-aiohomekit-3.2.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

home-assistant-component-tests.homekit_controller

4 packages built:

python311Packages.aiohomekit
python311Packages.aiohomekit.dist
python312Packages.aiohomekit
python312Packages.aiohomekit.dist

Maintainer pings
cc @fabaff for testing.


Fix the 'click-to-fork' link in contributer notes

Found by @ekargee on FOSS4G 2015 codesprint. Thanks!

Thanks Marc and @ekargee!


Admin User Roles Bug

Selecting User Role 'Admin' as Admin deletes the admin privelage and won't allow sign in

Has anybody tried this?

Can't reproduce. Could you give some more details?

when you click the admin role button it will immediately log you out of the application and if you try to sign back in it will not allow you to

It happens to non-master admins which is correct behaviour.

I got this error to. I nee to create new user, but  I can't.
I am not very sure, but I fix it in the model of userProfile. At least it is a temporary solution.
type: String
blackbox: true
optional: true
defaultValue: "admin"


Enable Sovrin TestNet and MainNet endorser, and update endorser agent settings

Ready for review.  These updates have been deployed and tested in all environments as part of https://github.com/bcgov/dts-endorser-service/issues/34


[godot-cpp] Update to 4.2.2

Updates the godot-cpp port to use version 4.2.2 and add support for hot reloading.

[X] Changes comply with the maintainer guide.
[X] SHA512s are updated for each updated download.
[X] The "supports" clause reflects platforms that may be fixed by this new version.
[X] Any fixed CI baseline entries are removed from that file.
[X] Any patches that are no longer applied are deleted from the port's directory.
[X] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is added to each modified port's versions file.

Time to update to 4.3.

Time to update to 4.3.

PR https://github.com/microsoft/vcpkg/pull/41246 updates godot-cpp to 4.3.

Closed as duplicate of #41246.


Possibly use bcrypt compare instead of compareSync

Try to figure out if there is a way to change compareSync to some sort of from(compare)at this point in the code. Just to make better use of RxJS. Maybe a mergeMap and iif can be used.

Actually instead of iif(0 I could just make the map() a mergeMap() make the function async, await the compare() and return from(Promise.resolve(objectAlreadyhere)) and it should work out just fine. At least I think it will...


Job FIFO will be broken periodically

Currently, job FIFO is controlled by priority value, whose calculation is based on mod result of Unix timestamp.
FIFO will be broken every 2^23 / 3600 / 24 = 97.09 days.
After #4959, the period becomes every 16 * 2^24 / 3600 / 24 = 3106.89 days, that is around 8.5 years.

Add next break time into issue title?