KeepAlive not working in VueRouter

Version
4.0.0-alpha.11
Reproduction link
https://github.com/andrewspy/vite-app-keep-alive
Steps to reproduce
See App.vue
<template>

Hello Vite   Vue 3!

Edit ./App.vue to test hot module replacement (HMR).

    Count is: {{ count }}
    <button @click="count  ">increment</button>

    <router-link to="/">Home</router-link> |
    <router-link to="/about">About</router-link>

    <keep-alive :include="['Home', 'About']">
      <router-view />
    </keep-alive>

</template>

What is expected?
count in Home view should retain value on change route.
What is actually happening?
count in Home view always reset to 0.

I have read the missing features of KeepAlive in README, but not sure if it is related, or any workaround for KeepAlive for Vue3.

I shall close it as it's a known missing features at the moment. Thanks!

@andrewspy does it work now? Where is that readme mentioning KeepAlive is a missing feature? Thanks.

@andrisi See below:
https://next.router.vuejs.org/guide/migration/index.html#router-view-keep-alive-and-transition

@andrewspy thanks for the quick reply. I do use it as describe, but inside a Quasar Framework project, so I might be doing something wrong. Nothing is kept alive for now.

@andrewspy solution at https://stackoverflow.com/questions/66215625/vue-3-keep-alive-cache-routes - says: In Vue 3, put the key on the  rather than the


Intelligent cursor restoration after auto-formatting

I've never used tree-sitter so let me know if this is not possible or doesn't make much sense.
Restoring buffer position after applying styling fixes can be difficult. My frequent use case is with the black formatter using https://github.com/lassik/emacs-format-all-the-code on save.
Black makes a guarantee that the AST is unmodified after formatting, so it seems to me that combining tree-sitter with this the user could be placed on the same tree node as they were before the format. This would make it so that autoformatting would leave your cursor in the same logical place as it was before, even if the number of lines of code was radically changed.

This is a nice idea! I think it can be done as followed:

Before formatting, store the "path" leading from the root node to the current node.
After formatting, use that path to search for the corresponding node in the new syntax tree.

I think you could use TreeCursor::goto_first_child_for_byte to walk the cursor to the leaf node at a given byte offset (based on the cursor position) keeping track of the steps along the way.

There's a macro in 0.5.0 for this: tree-sitter-save-excursion. It keeps the cursor on the same node, and on the same vertical position.
The following works for me in Python (provided that tree-sitter-mode is turned on in the buffer), with Black formatter:
(require 'tree-sitter-extras)

(define-advice format-all-buffer (:around (f &rest args) tree-sitter-save-excursion)
  (if tree-sitter-mode
      (tree-sitter-save-excursion
        (apply f args))
    (apply f args)))

I think it's better to combine this with the diff-based approach mentioned in the issue you linked, though.

@raxod502, who wrote apheleia.el, is knowledgeable about this. If we use Needleman-Wunsch as with apheleia, it's not clear to me how we'd combine this with a tree-sitter-based approach.

Yes, there are basically two good options for handling this issue:

The smart approach, which is to have an understanding of the AST and the cursor's position within a specific node
The dumb approach, which is to use a string alignment or regexp-based algorithm

If you've got the resources available to do the first approach, it'll probably work better. The reason I think the second approach is good is because the first approach requires a lot of work for each language / formatter, whereas the second approach works for all languages and formatters.
The disadvantages of the second approach are:

it needs some heuristics to optimize for large diff regions, because the dynamic programming algorithm scales quadratically (https://github.com/raxod502/apheleia/issues/4)
it needs some heuristics to nudge the cursor to the most appropriate position sometimes, because the dynamic programming algorithm can select one of several different string alignments which score equally well but which do not seem equally appropriate to a user (https://github.com/raxod502/apheleia/issues/2)


[FR] Embedding local pages / Page content in template

Hi! I started exploring SB for my personal daily notes and stuff i need to remember (and maybe share  with my wife).
I usually take some daily notes and at the end of a week, i review them and update more "stable" pages, if necessary.
Right now, any quick/daily note i create, feels somehow "lost", because it is not easily discoverable.
It would be great to have a way to get one page with all my daily notes concatenated to scroll through. I tried using a Query + template + embed but this resulted in problems with width not being used ideally and the header of SB getting duplicated for each daily note.
I may have missed how this could already work. If so, any pointers would be appreciated.
If not, consider it a feature request: allow local pages to be embedded with dynamic height and without header, Alternatively, allow templates to get the raw page content.
It could look something like this:

Daily Notes
2023-11-15

Missing browsing my daily notes easily, created a feature request

2023-11-14

told friend about SB, he seems intrigued

2023-11-13

Discovered silverbullet, played with the demo

<...more...>
(pagination may become an issue, but limiting it to x pages may work around this.)
I have noted a similar request #533 with a little different usecase. I did not want to hijack it but i think they could be solved together.
Thank you for building this interesting piece of software! 👍

Would using a live template not do the job? This embeds another page into the current one. You can use raw: true to avoid any processing of handlebars instructions.
```template
page: "[[some other page]]"
raw: true
```

This does not seem to work. I get an error
 end of the stream or a document separator is expected at line 1, column 24: page: [[📅 2023-11-15]]] ^

It can be replicated by appending this on silverbullet.md (i could not get the proper backticks properly escaped in this reply)
'''template
page: [[💡 Inspiration]]]
raw: true
'''

Hmm, seems to work for me?

After a good night of sleep i realized, i simply missed the quotes around page: "[[some other page]]"
To anybody looking for this, i got it working using this query:
```query
page
where name =~ /^📅/
order by name desc
render [[template/daily]]
```

and the following daily/template
## [[{{name}}]]
```template
page: "[[{{name}}]]"
raw: true
```

I assume pagination clashes with your model of writing the query result to the file, right?
What would be an alternative approach to this? Could a plug do this?

Query results are not written directly to a file anymore, this used to be the case with directives but no longer.
Pagination... yeah not sure how to handle that. You can limit your result set with e.g. a limit 10 clause in your query, but there's no offset or similar at this point.


Interactive window cell menu shows up underneath the input box

Testing #127378
Click on the ... on the last cell in the scrollbar

I'm seeing the same in the notebook, and the run button sub menu behaves correctly.

It's caused by transform: translate3d(0px, 0px, 0px); which will crop anything overflows.


Updates on CloudSigma driver

Updates on  CloudSigma driver
Description

Add all supported regions
Use example sizes  currently provided by CloudSigma
Change methods parameters to use actual  cores to define CPUs instead of MHz
Change Drive methods parameters to use GBs instead of bytes
Implement SSH key related methods ( list_key_pairs, get_key_pair, create_key_pair, import_key_pair_from_string, delete_key_pair), add ssh keys param on create_node
Implement ex_attach_drive, ex_detach_drive, ex_destroy_drive, reboot_node, ex_get_node
Make deleting all attached drives on destroy_node optional
Add tests on methods added
Add volume methods which call the appropriate ex_drive method ( since CloudSigma drives are pretty much volumes in the context of libcloud, I thought this makes sense)

Status

done, ready for review

Checklist (tick everything that applies)

[x] Code linting (required, can be done after the PR checks)
[ ] Documentation
[x] Tests
[x] ICLA (required for bigger changes)

Thanks for the contribution.
I added some comments, nothing major.


Shared directory fuzz tests with rebasing can be more aggressive

Description
Adjusting the shared directory fuzz test parameters so that it catches issues like the 0x331 which was missed by these tests..

AB#6044


Blocking commands connected to Redis Cluster aren't resubscribed after Master node failover

Fixed

@mrniko  we are facing problem related to connections broken between Redisson and Redis. we faced a lot of RedisTimeout Exception (unable to get connections). what is the right way to re-initiate the connection ? shall we shutdown and initialize ?

@eng7miky
Did you try to set pingConnectionInterval setting?

I am trying it from a while but I faced also a problem that not all results return from batch request (response.size != requested keys) and redisson don't throw any problem. it is a connection problem? or in this case how to recover this kind of issue? (just retry the batch again or re-initialize the client?

I am trying it from a while but I faced also a problem that not all results return from batch request (response.size != requested keys) and redisson don't throw any problem

Can you provide any test case to reproduce this?

I cannot reproduce the problem of not equal size between requests and responses but when it happened in the production, the problem kept happeningfrom request to another until I restarted the application so the client started to return the whole batch requested as expected. that's why I am asking if we can refer to recovery process for that client in case of unexpected problems between the client and Redis.


fixes #2274 : when user types a password less than 6 characters,text view error is overlapping with see password button.

Description
Edited loginactivity.java so that instead of setError method,used a toast message as when user types a password less than 6 characters,text view error is overlapping with see password button.
Related issues and discussion
#2274
screenshots

Checklist
Make sure you've done all the following (You can delete the checklist before submitting)

[x] Apply the AndroidStyle.xml style template to your code in Android Studio.
[x] Code is well documented
[x] Include unit tests for new functionality
[x] All user-visible strings are made translatable
[x] Code passes Travis builds in your branch
[x] If you have multiple commits please combine them into one commit by squashing them.
[x] Read and understood the contribution guidelines .

Looks good, thanks.


Feature Request:

          Feature Request:

When deploying the NFT images and metadata to IPFS, it is necessary to first upload the images (and get a unique CID).
Then I need to update the JSON files to point at this CID. I can not create the CID in advance of running the generative script (index.py) as I do not have the CID until I upload the images.
Could a script be added to run after the index.py & once I get the CID to go through all files in the metadata folder and update the baseURI to represent the IPFS CID? (Or regenerate them based on all-object.json?) Obviously the data needs to maintain the connection to the image. is these feature possible if yes than can you share a video reference or doc for the same .
Originally posted by @sriharsh1104 in https://github.com/Jon-Becker/nft-generator-py/issues/7#issuecomment-1477580989

Does this not solve this issue?
https://github.com/Jon-Becker/nft-generator-py/blob/main/update_cid.py


trivy: 0.15.0 -> 0.16.0

Motivation for this change
Bump trivy to 0.16.0
Things done

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

[X] NixOS (x86_64)
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 112383 run on x86_64-linux 1

1 package built:

trivy

Result of nixpkgs-review pr 112383 run on x86_64-linux 1

1 package built:

trivy

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 112383 run on x86_64-darwin 1

1 package built:

trivy


Markdown to static API

Hi, how could I can generate a .json file with a list of items that I got from page query?

@derevandal could you please elaborate what you are trying to accomplish?

@dominiquedutra I wanna generate static a way to my api consume my content without parse html.

@derevandal You can try to do something like this:
const path = require('path')
const fs = require('fs-extra')

module.exports = function (api) {
  api.createPages(async ({ graphql }) => {
    const { data } = await graphql('query { ... }')
    const filePath = path.join(api.config.outDir, 'filename.json')

    await fs.outputJson(filePath, data)
  })
}

It works! Thanks @hjvedvik o/


RepositoriesService: Add required status checks methods

This PR adds required status checks methods as detailed in https://developer.github.com/v3/repos/branches/#get-required-status-checks-of-protected-branch
and https://developer.github.com/v3/repos/branches/#list-required-status-checks-contexts-of-protected-branch

Happy with those changes - thanks for making them!

Sadly, @googlebot and collaborating on GitHub pull requests don't get along too well.
I checked that CLA was good before I pushed my commit, and I obviously consent to contribute my change (and I've signed CLA), so we can ignore that message and safely merge the PR.
However, it would be nice if @googlebot can be updated to handle this situation better. @willnorris, how realistic is it for that to happen? Is it a matter of doing some implementation work (that I can contribute to?), or will it be harder due to needing to be vetted by legal teams, etc.?

Thanks for the PR @jimmidyson!


URL encoding of connection string probably causes querystring parsing to break

As noticed by @2fast2fourier

Closing as a non-issue, after reviewing the URL encoding logic, I wasn't able to replicate this potential bug.


Basic implementation

Hey @rainliu,
this PR adds a basic implementation for WebRTC's data channels, based on Pion's implementation.
Disclaimers:

Since this crate depends on sctp, which at this point in time is not yet feature-complete I went ahead and define a few API stubs for the types and functions needed.

For now I omitted DataChannel's tests, since I'm still rather unfamiliar with Go and Pion's data-channel tests make use of github.com/pion/transport/test's Bridge, which makes quite heavy use of Go channels.

I figured however that even at an unfinished state it might be beneficial to open a PR for the stuff that's done.

Great! Thank you for contributions.

Could you do “cargo fmt” and cargo clippy, test, etc?

Done!

Interesting. cargo fmt --all -- --check succeeds on my checkout. 🤔
I'm running rustfmt 1.4.36-stable (7de6968e 2021-02-07).

try to update rust to 1.52.1?

Weirdly enough I already am on the latest Rust version:
$ rustc --version
rustc 1.52.1 (9bc8c42bb 2021-05-09)

it turned out Github Action's toolchain is too old, just upgrade it to 1.52.1


[bug] Wrong provider used to read files

ISSUE
The change to add a reedme file to the foundations repo ( used a provider "file". This is the wrong provider, and should be "local_file": See here

Opened for wrong repo


Refactor heron_executor to make it easier to customize

Currently the main function and the function for generating java command are single functions. In case some users might need to customize it, it is hard to reuse code in the existing executor. After the refactor, users should be able to create their own executor by extending the HeronExecutor class and use it in the main function.
class UserHeronExecutor(oss_heron_executor.HeronExecutor):
pylint: disable=no-self-use
def _get_jvm_instance_options(self, instance_id, component_name, remote_debugger_port):
options = oss_heron_executor.HeronExecutor._get_jvm_instance_options(
instance_id, component_name, remote_debugger_port)
....
return options
def main():
Instantiate the executor
parsed_args = oss_heron_executor.parse_args(sys.argv)
executor = UserHeronExecutor(parsed_args, os.environ.copy())
executor.initialize()
launch it
oss_heron_executor.start(executor)
if name == "main":
main()

Only code move around. No logic change other than a few extra logs.


Configure server log level

Please add one or more params to control logs from RESTful API server - namely in mii.serve() function.
You can see as reference -log- config params in vLLM: https://docs.vllm.ai/en/latest/serving/openai_compatible_server.html#command-line-arguments-for-the-server
It is especially important at startup, when there is a huge amount of logs (from several processes).

Hi @sedletsky-f5 - we will try to prioritize this, in the meantime, if you are able or willing, would you consider making a PR and we can review and get it merged?

thanks @loadams , I will wait for you implementation (I didn't get into the code to make this change)


Execute npm run hot with xcode when clicking on Build and run

Hello,
I was wondering where can modify the script executed when I click on Build and Run on XCode?
I was thinking in that it was a script executed in Build Phases > Run Script Phase, but I didn't found any.
Any suggestion?
Best,
Jean

You can find the script in Libraries/React.xcodeproj -> Build Phases -> Run Script, e.g.

Great, thanks!


[BUG] Library not exposing c++ symbols, still enforcing its STL in the abi.json

Describe the bug
As recommended by the guidance for middleware authors, we've switched our AAR to being built with the static STL. The library exposes a purely-C API/ABI, the use of C++ is an internal implementation detail. Exported symbols are limited with an exports file so in theory it should be unobservable that the library uses C++. However, now that we have a shared library with static STL, the gradle build (I think in the prefab tool itself) fails with Library is a shared library with a statically linked STL and cannot be used with any library using the STL.
To Reproduce
Steps to reproduce the behavior:

Add linking to the OpenXR 1.0.25 library AAR to a gradle project - this exposes only a C API but internally uses C++ with the static runtime, so you could do similarly yourself to any library.
Try building
You'll see an error "com.google.prefab.api.NoMatchingLibraryException"

Expected behavior
Would expect that it would link and run fine.
I'm told that for projects using it without Gradle (e.g. Unity projects) the contents of the AAR work fine, so it's specific to using prefab/gradle to do the build.
Logs
> Task :classic-teapot:configureCMakeDebug[arm64-v8a] FAILED
C/C++: prefabcom.google.prefab.api.NoMatchingLibraryException: No compatible library found for //OpenXR/openxr_loader. Rejected the following libraries:
C/C++: prefabandroid.arm64-v8a: Library is a shared library with a statically linked STL and cannot be used with any library using the STL
C/C++: prefabandroid.armeabi-v7a: User is targeting arm64-v8a but library is for armeabi-v7a
C/C++: prefabandroid.x86: User is targeting arm64-v8a but library is for x86
C/C++: prefabandroid.x86_64: User is targeting arm64-v8a but library is for x86_64

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':classic-teapot:configureCMakeDebug[arm64-v8a]'.
> C/C++: /home/ryan/src/androidteapots/classic-teapot/src/main/cpp/CMakeLists.txt debug|arm64-v8a : CMake Error at /home/ryan/src/androidteapots/classic-teapot/src/main/cpp/CMakeLists.txt:19 (find_package):
    Could not find a package configuration file provided by "OpenXR" with any
    of the following names:

      OpenXRConfig.cmake
      openxr-config.cmake

    Add the installation prefix of "OpenXR" to CMAKE_PREFIX_PATH or set
    "OpenXR_DIR" to a directory containing one of the above files.  If "OpenXR"
    provides a separate development package or SDK, be sure it has been
    installed.

Environment:
Prefab version: As provided in AGP 7.2.2
Host OS: Linux
Target platform: Android
Target ABI: any
Target OS version: SDK 33
Build system: Gradle
Additional context
Should we be specifying a different value in those abi.json files? Omitting that key fails, as does providing null. Looks like if we specify "none" as a string instead it will link and finish the build, at least.

Prefab doesn't create packages, it only reads them. You need to file this bug against whatever system created the package (looks to be AGP?)

Is the correct value to put in the file "none" then? Wasn't actually made with agp because of other bugs in agp, so more home brewed than that. But I suspect that agp probably does put the stl in the file because I doubt it's introspecting the symbols exported.

If your library does not enforce any STL constraints on the user, yes, use none.


Feature stage

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


(os/kern) invalid argument (error code: 4)

Hi,
I am trying to use the app, but getting this error when trying to inject Source:
an error occurred while injecting Simulator: (os/kern) invalid argument (error code: 4)
Xcode 8.2.1
iPhone 5 simulator with iOS 10.2 (not device)
MacOS Sierra 10.12.2
Not sure if app has iOS 10.x for simulators, read about device limitations only.
UPD: tried with another project and iPhone 5/iOS 9.3 simulator - got same error

ah, I think this could be becuase iPhone 5 is 32 bits? Injection bootstrap is 64bits only

@johnno1962 yes, you were right, on iPhone 5s app does not give an error.
It gives warning like:
/Users/sergii/Developer/***ViewController.swift
objc[41204]: Class _TtC14**21**ViewController is implemented in both /Users/sergii/Library/Developer/CoreSimulator/**Containers/Bundle/Application**/***.app/** and /Users/sergii/Library/Developer/Xcode/DerivedData/***Logs/iOSInjectionProject/build/Debug-iphonesimulator/InjectionBundle1.bundle/InjectionBundle. One of the two will be used. Which one is undefined.

So nothing is changed on simulator after injecting source. But maybe there is an issue for that already

You can ignore the warning. Have to reloaded the viewcontroller to see the changes take effect?


Support attaching to an existing request queue

Http.Sys has an API where you can attach to an existing request queue by name rather than creating a new one. In this mode you'd assume the queue was already configured so most settings would be ignored (e.g. prefixes, timeouts, auth, etc.).
This can be used in conjunction with the HttpWaitForDemandStart API where a central dispatcher sets up the queue, listens for requests, and then activates the site when the first request arrives.
Complications:

[ ] Prefixes / PathBase / HotAdd&Remove
[ ] Auth / Challenge
[ ] Ignored Options (Timeouts, queue length limit, etc.)

See the tratcher/sharedQueues branch

My team is interested in this feature as well.  Did the 'tratcher/sharedQueues' branch go away?

Try this one? https://github.com/aspnet/HttpSysServer/tree/tratcher/sharedQueue

Tri state mode.

Primary, only create
Secondary, only join existing
Try to join an existing, if it doesn't exist then create it. (or should we do that in reverse order?)

Does closing the primary queue shut it down for everybody?
When closing the primary queue why do we remove the url registrations?
Queue acls?

@muratg removing from backlog for re-triage

It looks like HttpQueryUrlGroupProperty can be used to retrieve information about what auth is enabled, and several other properties.

Bringing back to triage.


Rebroadcast last round messages when stuck at step longer than timeout

After some timeout that's longer than the usual step timeout, if stuck in a phase (haven't received from >2/3 of power), rebroadcast messages sent for the current and previous round that will support another node catching up. The simplest is probably to re-send everything since (inclusive) PREPARE from the prior round.
Note the DECIDE step is a special case, where only DECIDE need be rebroadcast.
See https://github.com/filecoin-project/FIPs/pull/998

rebroadcast messages sent for the current and previous round

The FIP only requires rebroadcast of messages in the current round.
Is there any reason other than faster consensus for rebroadcasting messages from previous round too?


Pin swift-async-algorithms to 1.0.1 in update-checkout-config.json

We've temporarily unpinned this repository in https://github.com/apple/swift/pull/72728 to get recent changes. Now a new tag is available, we should pin it again.

@swift-ci test

@swift-ci build toolchain

@swift-ci test

@shahmishal If you have a moment, could you update the dependency in the CI configuration? :pray:

Please also update next and rebranch scheme

@swift-ci test

@swift-ci build toolchain

Thanks!


Verify SAS interface with test suite

DP Requirement ID: SCI-04
The SAS client interface shall comply with all interface test cases defined in [2].
[2]
SSC-Wireless Innovation Forum, “Test and Certification for Citizens Broadband Radio Service (CBRS); Conformance and Performance Test Technical Specification; CBSD/DP as Unit Under Test (UUT)”, WINNF-TS-0122-V1.x.x Test and Certification for Citizens Broadband Radio Service (CBRS); Conformance and Performance Test Technical Specification; CB

There are dependencies in the WINNF test suite that are >50GB big - @jpad-freedomfi & @m-trojanowski will work on picking a subset of tests (i.e. excluding those aiming to test SAS itself) that don’t need those dependencies

Put on hold. This requires a lot of work on the CI code and on the WINNFs testing harness (which is not really supposed to be run in an automated fashion). Testing harness and WINNF 0122 should be done manually.

as per @jpad-freedomfi - closing with NoFix


Assistance Needed: Incorrect Calculation of Data Rewards for Sensor-Based Data Traffic

Dear Engineering Team,
We are facing an issue with the calculation of data rewards for sensor-based data traffic on our network, which has led to poor data rewards for Community Hotspot Operators. We seek your assistance in resolving this matter promptly.
Background:
Since the migration to Solana, our Community Hotspot Operators have observed that data rewards for sensors attached to a Helium Console prior to the Solana transition are not being credited with the new IoT token amounts as expected. This discrepancy in data rewards has caused consternation among the operators and has raised concerns within the community.
Observations from Fault Finding:
During the fault finding process conducted by the Community Hotspot Owners, an interesting discovery was made. It was noticed that when a sensor attached to the console prior to the Solana migration is removed and then re-entered into the console, it starts receiving significantly higher IoT token rewards compared to its previous reward levels. It seems that only the sensors that undergo this process are being affected positively, while others remain unaffected.
Challenges Faced by Community Hotspot Owners:
Unfortunately, the Community Hotspot Owners lack the necessary knowledge and access to accurately determine the appropriate data rewards for sensor-based data traffic. They are unfamiliar with the data credit reward accounting model, and they do not have the required access to data from the Helium Network oracles and the Solana blockchain.
Request for Assistance:
In light of the above situation, we kindly request your assistance in investigating and resolving this issue. Our objective is to ensure fair and accurate data rewards for all sensor-based data traffic within our network. We believe that your expertise and access to relevant systems and data will enable us to identify and rectify the problem effectively.
Please consider the following points during your investigation:

Examine the data reward calculation process for sensor-based data traffic after the Solana migration.
Identify any discrepancies or anomalies that may be causing the lower-than-expected data rewards.
Analyze the impact of removing and re-entering sensors on the console and its effect on data rewards.
Determine the root cause of the issue and develop a solution to ensure accurate and fair data rewards for all sensors.

We greatly appreciate your prompt attention to this matter and your commitment to resolving it. If you require any additional information or have any questions, please do not hesitate to reach out to us. We are eager to work closely with you to rectify this problem and restore confidence within our community.
Thank you for your support and cooperation.

Looks like github allows transferring of an issue while keeping the same owner. I was worried about copy-pasting it myself, as then you would be removed from notifications and that dev team may need more context.

After investigation, it looks like this is due to the fact that HPR did not write a packet report (not triggering reward / payment) for the Join Request (JR).
This only happens when the JR is sent to multiple OUIs, at this point HPR cannot make a proper decision on which OUI to charge, as a result it does not write a packet report (note that data is still transferred to LNSs). This is an intended behavior of HPR to avoid charging the wrong OUI in those edge cases (code here).
When the device got reseted, I am guessing that, the join credentials changed and only pointed to 1 OUI triggering the report to be written properly again.
Thank you for the report and I hope this help clarify the behavior that you saw.
Side note: It was brought to my attention that staging server (Console/Router) might have been used for testing, please note that staging is not a stable environment as it is used for release testing only and is subject to "data wipe out" at any time (devices / orgs ...). Furthermore the multi-buy setting for Staging's OUI has also been lowered to 1 (as it is only a testing server).

After investigation, it looks like this is due to the fact that HPR did not write a packet report (not triggering reward / payment) for the Join Request (JR).
This only happens when the JR is sent to multiple OUIs, at this point HPR cannot make a proper decision on which OUI to charge, as a result it does not write a packet report (note that data is still transferred to LNSs). This is an intended behavior of HPR to avoid charging the wrong OUI in those edge cases (code here).
When the device got reseted, I am guessing that, the join credentials changed and only pointed to 1 OUI triggering the report to be written properly again.
Thank you for the report and I hope this help clarify the behavior that you saw.
Side note: It was brought to my attention that staging server (Console/Router) might have been used for testing, please note that staging is not a stable environment as it is used for release testing only and is subject to "data wipe out" at any time (devices / orgs ...). Furthermore the multi-buy setting for Staging's OUI has also been lowered to 1 (as it is only a testing server).

Does not help the people missing out earning as once again things not working correctly

After investigation, it looks like this is due to the fact that HPR did not write a packet report (not triggering reward / payment) for the Join Request (JR).
This only happens when the JR is sent to multiple OUIs, at this point HPR cannot make a proper decision on which OUI to charge, as a result it does not write a packet report (note that data is still transferred to LNSs). This is an intended behavior of HPR to avoid charging the wrong OUI in those edge cases (code here).
When the device got reseted, I am guessing that, the join credentials changed and only pointed to 1 OUI triggering the report to be written properly again.
Thank you for the report and I hope this help clarify the behavior that you saw.
Side note: It was brought to my attention that staging server (Console/Router) might have been used for testing, please note that staging is not a stable environment as it is used for release testing only and is subject to "data wipe out" at any time (devices / orgs ...). Furthermore the multi-buy setting for Staging's OUI has also been lowered to 1 (as it is only a testing server).

Does not help the people missing out earning as once again things not working correctly

That's not what the answer implies, nor is the tone helpful.. it's working as specced right now.. If the device would stop trying to join multiple OUIs (by the user registering it with only one vs multiple) it would work as you would expect.

After investigation, it looks like this is due to the fact that HPR did not write a packet report (not triggering reward / payment) for the Join Request (JR).
This only happens when the JR is sent to multiple OUIs, at this point HPR cannot make a proper decision on which OUI to charge, as a result it does not write a packet report (note that data is still transferred to LNSs). This is an intended behavior of HPR to avoid charging the wrong OUI in those edge cases (code here).
When the device got reseted, I am guessing that, the join credentials changed and only pointed to 1 OUI triggering the report to be written properly again.
Thank you for the report and I hope this help clarify the behavior that you saw.
Side note: It was brought to my attention that staging server (Console/Router) might have been used for testing, please note that staging is not a stable environment as it is used for release testing only and is subject to "data wipe out" at any time (devices / orgs ...). Furthermore the multi-buy setting for Staging's OUI has also been lowered to 1 (as it is only a testing server).

Does not help the people missing out earning as once again things not working correctly

That's not what the answer implies, nor is the tone helpful.. it's working as specced right now.. If the device would stop trying to join multiple OUIs (by the user registering it with only one vs multiple) it would work as you would expect.

If you knew this community you would understand why they are annoyed about things not working correctly its everyone else's fault but whos for weeks being asked to supply data to be told its working as specced right now does not once say.. sorry it was broken for this reason and you were right there was an issue.. suppose next it will be Genesis was not paid out to many hotspots because of multiple attempts to send data. Bud honest i have been as respectful as i intend to be with you Have a good day

After investigation, it looks like this is due to the fact that HPR did not write a packet report (not triggering reward / payment) for the Join Request (JR).
This only happens when the JR is sent to multiple OUIs, at this point HPR cannot make a proper decision on which OUI to charge, as a result it does not write a packet report (note that data is still transferred to LNSs). This is an intended behavior of HPR to avoid charging the wrong OUI in those edge cases (code here).
When the device got reseted, I am guessing that, the join credentials changed and only pointed to 1 OUI triggering the report to be written properly again.
Thank you for the report and I hope this help clarify the behavior that you saw.
Side note: It was brought to my attention that staging server (Console/Router) might have been used for testing, please note that staging is not a stable environment as it is used for release testing only and is subject to "data wipe out" at any time (devices / orgs ...). Furthermore the multi-buy setting for Staging's OUI has also been lowered to 1 (as it is only a testing server).

Does not help the people missing out earning as once again things not working correctly

That's not what the answer implies, nor is the tone helpful.. it's working as specced right now.. If the device would stop trying to join multiple OUIs (by the user registering it with only one vs multiple) it would work as you would expect.

If you knew this community you would understand why they are annoyed about things not working correctly its everyone else's fault but whos for weeks being asked to supply data to be told its working as specced right now does not once say.. sorry it was broken for this reason and you were right there was an issue.. suppose next it will be Genesis was not paid out to many hotspots because of multiple attempts to send data. Bud honest i have been as respectful as i intend to be with you Have a good day Oh and in this case, and all the cases of missing rewards AU915 is the sensor unit with four different sensors and a glamos so they were all trying multiple were they

I do know this community and why they're annoyed. I really feel for you all.. This, however was not a "this is not working as specified" moment and assuming it is appears to be a trademark of this community.
If you'd like to have a productive, positive discussion about what can be improved, get into Discord and let's have at it. I think much positive progress has been made and, while definitely annoying that it's been taking this long, how do these negative comments here (which are not even accurate) actually help? Let's move forward.. get into Discord and have a normal, non confrontational, conversation

Not being negative just saying when people been trying for weeks and months it kicks the stuffing out of them hope you have a good rest of your day

Can you please clarify the process that a Community member sensor operator could have inadvertently placed their sensors into this edge case (the multiple OUI's)? Understanding this would enable a Community Sensor Operator to better be able to make deliberate decisions covering this point.
Continuing the side note - there are Helium Console organisations on both the Dev and Prod networks.

Can you please clarify the process that a Community member sensor operator could have inadvertently placed their sensors into this edge case (the multiple OUI's)? Understanding this would enable a Community Sensor Operator to better be able to make deliberate decisions covering this point.
Continuing the side note - there are Helium Console organisations on both the Dev and Prod networks in use by Community sensor operators. The dev organisations understand the purpose and operations of the Dev environment.

Not sure how a community sensor operator would have done this if following the videos of how to use or using the set up guide. i would also like to know as well

Not being negative just saying when people been trying for weeks and months it kicks the stuffing out of them hope you have a good rest of your day

hard to interpret "as once again things not working correctly" any other way.. try to make the best out of your day too!

Continuing the side note - there are Helium Console organisations on both the Dev and Prod networks in use by Community sensor operators. The dev organisations understand the purpose and operations of the Dev environment.

There were bugs filed against staging and dev consoles for "operational issues" which is definitely against using either of those.. just don't use them unless you understand the implications of losing data, rewards, connectivity

Continuing the side note - there are Helium Console organisations on both the Dev and Prod networks in use by Community sensor operators. The dev organisations understand the purpose and operations of the Dev environment.

There were bugs filed against staging and dev consoles for "operational issues" which is definitely against using either of those.. just don't use them unless you understand the implications of losing data, rewards, connectivity

Ok been wanting to ask then, if i had Mike V, Travis and Victor all on my console and all could not find the issue as they were connected correctly please answer how as a community member i could solve the issue.? maybe your get why we are frustrated

Can you please clarify the process that a Community member sensor operator could have inadvertently placed their sensors into this edge case (the multiple OUI's)? Understanding this would enable a Community Sensor Operator to better be able to make deliberate decisions covering this point.

Continuing the side note - there are Helium Console organisations on both the Dev and Prod networks in use by Community sensor operators. The dev organisations understand the purpose and operations of the Dev environment.

you'd add a sensor on one console (like vip, production, staging or dev or any of the other console operators out there)and then also add it on another..

Ok that makes sense to a degree. If I am understanding this correctly when you delete the sensor from one console there is a possibility that the Sensor doesn't correctly adjust the change or perhaps console doesn't correctly purge the relationship or the gateway doesn't do its bit? Is there more to it though when you factor in the AU Freq Band Change? I still have 2 sensors that refuse to connect to any console which I am working through with the hoster. These were previously configured to AU915sb6 and have been reconfigured to AU915sb2 since the Freq change.

Continuing the side note - there are Helium Console organisations on both the Dev and Prod networks in use by Community sensor operators. The dev organisations understand the purpose and operations of the Dev environment.

There were bugs filed against staging and dev consoles for "operational issues" which is definitely against using either of those.. just don't use them unless you understand the implications of losing data, rewards, connectivity

Ok been wanting to ask then, if i had Mike V, Travis and Victor, Slaven from glamos all on my console and all could not find the issue as they were connected correctly please answer how as a community member i could solve the issue.? maybe your get why we are frustrated

no need to rehash this over and over.. I certainly get why you're frustrated.. but repeating it isn't helping getting to resolution

Can you please clarify the process that a Community member sensor operator could have inadvertently placed their sensors into this edge case (the multiple OUI's)? Understanding this would enable a Community Sensor Operator to better be able to make deliberate decisions covering this point.

Continuing the side note - there are Helium Console organisations on both the Dev and Prod networks in use by Community sensor operators. The dev organisations understand the purpose and operations of the Dev environment.

you'd add a sensor on one console (like vip, production, staging or dev or any of the other console operators out there)and then also add it on another..

Ok that makes sense to a degree. If I am understanding this correctly when you delete the sensor from one console there is a possibility that the Sensor doesn't correctly adjust the change or perhaps console doesn't correctly purge the relationship or the gateway doesn't do its bit? Is there more to it though when you factor in the AU Freq Band Change? I still have 2 sensors that refuse to connect to any console which I am working through with the hoster. These were previously configured to AU915sb6 and have been reconfigured to AU915sb2 since the Freq change.

The most common mistake is that people do not remove it from one console before adding it to another. The gateway just forwards packets.. the HPR sees those devices registered with more than one OUI so it can't report which one should get rewarded.

Continuing the side note - there are Helium Console organisations on both the Dev and Prod networks in use by Community sensor operators. The dev organisations understand the purpose and operations of the Dev environment.

There were bugs filed against staging and dev consoles for "operational issues" which is definitely against using either of those.. just don't use them unless you understand the implications of losing data, rewards, connectivity

Ok been wanting to ask then, if i had Mike V, Travis and Victor, Slaven from glamos all on my console and all could not find the issue as they were connected correctly please answer how as a community member i could solve the issue.? maybe your get why we are frustrated

no need to rehash this over and over.. I certainly get why you're frustrated.. but repeating it isn't helping getting to resolution

Does not answer the question just side steps it. Only one console ever used only installed the sensors on a single console. Had your own team Checking this and still they could not find the issue. So please explain if experts from helium couldnt find the problem.. how comes the best option as you said above just don't use them unless you understand the implications of losing data, rewards, connectivity.. thought you wanted Data right now you do not.

Can you please clarify the process that a Community member sensor operator could have inadvertently placed their sensors into this edge case (the multiple OUI's)? Understanding this would enable a Community Sensor Operator to better be able to make deliberate decisions covering this point.

Continuing the side note - there are Helium Console organisations on both the Dev and Prod networks in use by Community sensor operators. The dev organisations understand the purpose and operations of the Dev environment.

you'd add a sensor on one console (like vip, production, staging or dev or any of the other console operators out there)and then also add it on another..

Ok that makes sense to a degree. If I am understanding this correctly when you delete the sensor from one console there is a possibility that the Sensor doesn't correctly adjust the change or perhaps console doesn't correctly purge the relationship or the gateway doesn't do its bit? Is there more to it though when you factor in the AU Freq Band Change? I still have 2 sensors that refuse to connect to any console which I am working through with the hoster. These were previously configured to AU915sb6 and have been reconfigured to AU915sb2 since the Freq change.

The most common mistake is that people do not remove it from one console before adding it to another. The gateway just forwards packets.. the HPR sees those devices registered with more than one OUI so it can't report which one should get rewarded.

What I am struggling with regarding this particular identified problem/rectification to the issue is that this could be an explanation for 1 or 2 instances but we are talking dozens of affected users. It is unlikely that this problem resolution is a root cause. Taking into account that a number of users did not alter their Sensor configs for the entire AS9123-1 period, electing to have them remain on AU915sb2 then when the switch back to AU915sb2 occurred they started processing data again but the rewards were reduced. Only after deleting and re-adding to the console did the DC rewards return to a level that appears inline with the data processed. Is it possible that there is a logic problem in the HPR code?

they started processing data again but the rewards were reduced

I cannot talk the frequency changes (nor my area of expertise) but I will look deeper into this ^.

I have not found any evidence of miss-calculation.
NOTE: We have posted a new update recently to Session Key Filters (SKF) to better handle packet copies.


Upgrade multiple catalog apps at once

How is it possible to update many (hundreds) of catalog apps at once to a new version? The rancher-cli seems not to be capable of that. We use Rancher 2.1.1. Thanks.

Thanks. I've been thinking about this. Just want to be sure there is no built in way.


luci-app-attendedsysupgrade: introduce rebuilders

This adds automatic verification builds to shift trust on multiple
server and multiple entities.
Currently just a proof of work.
Signed-off-by: Paul Spooren<EMAIL_ADDRESS>

Currently works only with a single rebuilder, I suspect I'm using the bind function wrong.

@jow- @stangri do you have an idea on how to use the poll and bind functions correctly? I want to poll multiple server and once they respond with a 200 status, stop polling them.

works fine.


fix: missing watch def from SDF

The new watch func is missing a definition in SDF, so it appeared untyped in the editor. We absolutely need a better way to do this.

bors r+


Update screeps-api to 1.4.0, use API tokens instead of email/password

This is great! I'll cut a new version of the software this weekend and launch it. The auto updater should pick it up as well.


Fix flaky QueryWorkflow tests

What changed?
Fix flaky QueryWorkflow tests

Why?

How did you test it?
run integration tests multiple times

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 01828892-ff85-4a87-b832-cee7a6ae4598

0 of 0   changed or added relevant lines in 0 files are covered.
54 unchanged lines in 10 files lost coverage.
Overall coverage increased (+0.07%) to 57.747%

Files with Coverage Reduction
New Missed Lines
%

common/backoff/retry.go
2
92.11%

common/persistence/historyManager.go
2
66.67%

common/task/parallelTaskProcessor.go
2
92.75%

common/persistence/nosql/nosqlplugin/cassandra/workflow.go
3
56.99%

common/persistence/statsComputer.go
3
94.64%

service/history/execution/mutable_state_task_refresher.go
3
66.14%

service/history/task/fetcher.go
3
91.79%

service/matching/taskListManager.go
5
76.63%

common/persistence/nosql/nosqlplugin/cassandra/workflowUtils.go
12
76.09%

common/persistence/nosql/nosqlplugin/cassandra/workflowParsingUtils.go
19
79.16%

Totals

Change from base Build 01828014-b220-4ae5-8811-94eda2de108b:
0.07%

Covered Lines:
84064

Relevant Lines:
145574

💛  - Coveralls


🚀 Feature: Enhanced Error Handling for API Calls and API Key Validation

🔖 Feature description
To improve robustness, this issue focuses on enhancing error handling mechanisms across all API calls in the chat_with_chatbot function. This includes catching network-related issues, providing meaningful error messages, and validating that the API key is present before making any requests.
🎤 Why is this feature needed ?
To improve robustness, this issue focuses on enhancing error handling mechanisms across all API calls in the chat_with_chatbot function. This includes catching network-related issues, providing meaningful error messages, and validating that the API key is present before making any requests.
✌ How do you aim to achieve this?
API Key Validation: Check that the apiKey variable is not empty before any API requests are made, and raise an error if it is missing.
Error Handling for Network Requests: Add exception handling to catch network errors for all API calls, returning a clear error message in case of a failure.
🔄 Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

Are you willing to submit PR?
Yes I am willing to submit a PR!

Ohh.. I have worked with APIs before and thought Error handling and Logging of API calls etc like functions are crucial for Debugging issues, so thought to mention


Ignore diagnostics

All changed packages have been documented.

You can try these changes at https://cadlplayground.z22.web.core.windows.net/typespec-azure/prs/306/
Check the website changes at https://tspwebsitepr.z22.web.core.windows.net/typespec-azure/prs/306/


CUDA error: device-side assert triggered

When I train the DW in coco, I have an unexpected problem, as following:
CUDA error: device-side assert triggered and it happen when I train some epochs.
I think It happen in
loc_loss = F.binary_cross_entropy and cls_loss = F.binary_cross_entropy, but I can't figure out why it happens.
Can you get me some helps?

How many GPUs do you use?

How many GPUs do you use?

1 GPU

This phenomenon often occurs in many FCOS-style label assignment methods (not only for DW) when using just 1 GPU. I suggest you can use at least 4 GPUs.

OK. Thanks.


What is fast storage?

The 3rd line of this document is saying "Performance is improved by temporarily copying frequently accessed data to fast storage located close to the application."
Whats the fast storage that was here talking about? Is it Azure blob storage??

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

ID: c84b7eee-6a44-a59b-a6ac-f9b483e51193
Version Independent ID: a01b9cf7-2ae7-7bcd-8c6c-8d0c01162970
Content: What is Azure Redis Cache?
Content Source: articles/redis-cache/cache-overview.md
Service: cache
GitHub Login: @wesmc7777
Microsoft Alias: wesmc

@raja4014 Thanks for your inquiry. In this case, 'fast storage' refers to a Redis Cache instance that has been optimally deployed to support a caching service. The section Why use Azure Redis Cache discusses the use cases in greater detail.
Redis Cache is deployed as a (PaaS) database service and is leveraged through application programming. There are Quickstart samples and Tutorials available to learn more:
Tutorial: Create a cache-aside leaderboard on ASP.NET
Quickstart: Use Azure Redis Cache with a .NET Core app
Please let me know if you have additional questions. Thanks, Mike

@raja4014 We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


IJ Plugin - Implements the DumbAware marker interface

This should prevent the tool window from blanking and becoming unusable while reindexing. Since that happens basically whenever IJ regains focus, it is a chronic issue.

Thanks @coyotesqrl!


Implement logical negation .not operator

Operator returns zero if expression is not zero. Operator returns one if expression is zero. Operator returns undef if expression is undefined. Returned type is byte.

Implemented by f56f7cc.


Added Loader in Jinja2 Environment initialisation

Description:
It adds a FileSystemLoader to the Jinja2 Environment object. http://jinja.pocoo.org/docs/2.10/api/#loaders
This will allow to import/include jinja2 templates from other templates:

http://jinja.pocoo.org/docs/2.10/templates/#import
http://jinja.pocoo.org/docs/2.10/templates/#include

so that we can export/reuse templates:
{% from script/communication_engine/phrases/greetings.j2' import greeting %}
I had to refactor a bit the get_default_config_dir because I was having issue with circular dependency. If there's a nicer/better way to achieve this I'm happy to refactor.
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#
I will create a PR for the documentation if people are happy with the change/PR
Example entry for configuration.yaml (if applicable):
No changes
Checklist:

[X] The code change is tested and works locally.
[X] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[X] Tests have been added to verify that the new code works.

Hello @onegambler,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

e6b5a4ad2b97816523294aeae1f44165558ddd0a - This commit has something that looks like an email address (roberto.magale@skyscanner.net). Maybe try linking that to GitHub?.
3cbdc59fa5a8a2a2e575e1cfeb934199d6b3050e - This commit has something that looks like an email address (roberto.magale@skyscanner.net). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

I see. I wasn't aware of concerns around the use of that. Do let me know if this can not be accepted.
Also, thank you for your comment. I am not sure I understand, ENV = TemplateEnvironment(...) is global so I don't have access to the hass object.
I am also unable to directly import config.py into template.py because of circular dependency: config -> config_validation -> template.

I think it's ok to add this feature. However, all paths for include/import have to be approved by  hass.config.allowed_path, including if an include itself contains an include.
Also, don't use get_default_config_dir, use hass.config.config_dir instead. This means that you have to create a function that takes in hass and returns the environment. It should cache the created env inside hass.data['template_env'].

I refactored the code. I managed to just modify template.py. There are some cases when hass is not initialised so I kept a default TemplateEnvironment without loader when hass is not defined.
Not sure about the solution, also I added lazy initialisation on the TemplateEnvironment and locks to avoid concurrency issues (might be overkilling).
@balloob I was having a look on how to use hass.config.allowed_path. The path I am setting is the configuration one ( so it will work with anything within .homeassistant). In my understanding allowed_path are external paths. Aren't paths within .homeassistant already allowed by default?
The path is used by the loader to decide which is the root path to start from when looking for a template to import, so we can do
{% from script/communication_engine/phrases/greetings.j2' import greeting %}
instead of
{% from /home/homeassistant/.homeassistant/script/communication_engine/phrases/greetings.j2' import greeting %}
Is necessary to add a check on allowed_path?
If we were to add the path to the allowed_path then we would have to create a loader per each allowed path in the list, even for those not used for templates.
Another options would be to create a new field template_paths alongisde allowed_path where we define the paths for templates.
Personally I am keeping my templates to import within .homeassistant config folder (as per previous example), so I wouldn't have to define an allowed path entry.
Thanks

Yes, .homeassistant is not allow default, or you can read stuff like password list or data from any config point.

Hi,
I added a new config parameter, template_dirs so that is possible to do:
homeassistant:
  template_dirs:
    - /home/.homeassistant/templates

in this way the user can explicitly specify if and where templates can be found. If no dirs are defined then it will use the "old" TemplateEnvironment.
Jinja allows you to use different loaders at the same time, wrapping them with a ChoiceLoader.
So for each path defined in template_dirs, the template environment will have a specific FileSystemLoader pointing to that specific dir and no other paths will be discoverable/accessible by the import/include.
Let me know your thoughts,
Thanks

@onegambler May I ask why this was closed?

Hi dale,
Apologies, I just didn't think people were that interested in the change.

The problem with includes is that all templates are rendered within the event loop and thus are not allowed to do any I/O.


Fix conformance issues exposed by https://github.com/miloyip/nativejson-benchmark

See https://rawgit.com/miloyip/nativejson-benchmark/master/sample/conformance.html#1. Parse Validation

Is this still on your agenda?

Hi @aggsol -- the only conformance issues are around the precision of very large and very small doubles, and when I looked into this last it looked like the only precision issues were at the least-significant digits.  That said, I do think this is worth improving.  I haven't prioritized it because many JSON encoders have precision issues for large and tiny doubles and I've yet to need it.  If you'd like, it might be fun to write up a test case and see why precision is getting lost.


[zh] Sync examples_test.go

[zh] Sync examples_test.go

/lgtm
/approve
Will merge and see if it works.


Separate Render core code from FFMpeg

To begin, I would like to thanks you for this incredible package ! Usage is simple and efficient 👌
Is your feature request related to a problem? Please describe.
As I mention it in another issue, I'm facing a problem when I want to use a different implementation of FFMpeg. Render depends of ffmpeg_kit_flutter_https_gpl which have only a few external library.
Describe the solution you'd like
I want to be able to write a custom MotionFormat that use libvpx external library (from ffmpeg_kit_flutter_video) for exemple.
This solution that seems the most obvious to me, is the separation of the code in two packages :

render_core, which provides abstractions and process of bitmap datas extraction. Datas will be interpreted/transformed by the new render package, or by custom implementations
render, which provides the current implementations, as the package is today

Also, it might be a good way to implements a web dedicated render package (i.e. render_web), based on render_core with no ffmpeg_kit_flutter deps.
Maybe there is a simplier and better solution (would be great !)
Describe alternatives you've considered
Fork the project an do it for myself.
I would be happy to work on this and open a PR, but it should be better to discuss about solutions before

Hi @Azramis,
Thanks for your input!
Generally, this seems a great idea, where render_core could become a platform for others to build ontop. So let me get this straight:
The render_core package (basic functions, without the processing, therefore eliminating imports of ffmpeg) is the centered main package.
And then the Packages that depend on render_core with the platform (or custom) ffmpeg imports that then take the data from render_coreand "only" process it.
There would be two "user-friendly" packages:

render: the default package -ffmpeg_kit_flutter for mobile
render_web: for people who want web, with  ffmpeg_wasm

For the forkers:

render_YourCustomName: for people who for example want to adjust the ffmpeg_kit_flutter plugin (such as ffmpeg_kit_flutter_video) and can copy/fork the code from render (...and eg. extend functions or MotionFormats)

Conclusion:
I think this separation would clear things up a bit, but it would not change the way it is handled right now anyway, right?
If People want a custom flutter import, they would still have to fork a package, just this time a bit smaller (render, without the code of render_core).
I agree, that this separation, might make extending the endpoint easier.
Don't get me wrong, I would love a simplification, but it might involve too much work (for you) and not too much of a gain?!
An extending idea:
If, on the other hand, we additionally add the packages like below, it might not be necessary to fork anything if there are ffmpeg import issues. (And would clear up issues like #18 )

render_ffmpeg_min
render_ffmpeg_min-gpl
render_ffmpeg_[other ffmpeg_kit_flutter plugins]
....

Here for reference the different packages offered by flutter_ffmpeg
PS. Let me know if understood your idea correctly :) And please correct me if I am wrong.

Thank you for the quick feedback !
You get the biggest idea behind my words ;)
In my opinion, render_core should only be responsible of extracting bitmap datas, one-shot (image) or streamed (motion), and delegate the processing of these datas to a... Delegate 😁  Therefore, it will be possible for anyone to "custom" process the datas, and to make what they want with it.
Possibilities become multiple :

Independance from FFMpeg
Stream frames through a network
Multi-threading

BTW, it should be necessary to build the new render package as it will cover the most retro-compatibility from the current. Lesser breaking changes, better the migration is !
Offer "ready-to-use" packages would be great, and the two you listed are a minima.
Forkers will probably be happy, but just like in my case, my app will only depends on the core and will implements only what I need. So I don't have to fork an entire project, and depends on a local package.
Main idea = Flexibility at most
Main changes

Remove ffmpeg_kit_flutter_* dependency
Don't use dart:io anymore in render_core, as we cant use it from Flutter Web
Think how to implements a Delegate in simpliest way (from code writing, to injection)

I'll be really enthusiast to be involved in these devs, and I'll try to take the time for its. My current work project depends of your package, and better flexibility in it means more possibilities for me 😁
What's next
I've forked the project and began to extract code.
A question remains: How do you imagine packages separation ?
From my experience, I worked with melos it allows to work with multi libraries on a mono repo. It manages versioning through conventional commits and local dependencies. Coupled with fvm it's a game killer in my opinion.
Despite this, it's important for me to have your opinion, as you are the creator of render
Extending Idea
I'm not for it, as it would complicate things.
It might be simplier to provide quickly, but I think maintenance will be nightmare when you want to upgrade dependencies versions...
Also, I prefer to have more flexibility, so... 🙃

Thanks for clearing things up and explaining.
I am quite busy, so I can't help you to write/rearrange the code too much.  It would be great if you could help us improve this plugin with your idea.
Execution:

Move main parts of the code to a new repository render_core
Link the current repo render to the render_core
Write documentation for extending render_core and which package to use (eg. for later render_web)

I have added you to the repository as a collaborator. You have my go :)

Sorry for the late feedback.
I'm currently working on it, and testing on a mono-repo. When I'll be satisfied with a first version, I'll push it to the render_core repo you have created.
I'll try to write documentation at my best, but let be honest, that's not where I'll be the best 😂


Update the Caddy configuration for Caddy v2

Caddy configuration page looks like it is currently for Caddy v1, which "will go away soon" https://caddyserver.com/v1/.  These docs should be updated for Caddy v2, https://caddyserver.com/docs/v2-upgrade. The docs should also explicitly note the Caddy version.

Feel free to update the docs @cboettig happy to accept any PR


Not able to open new channel with node that has already opened channel with me.

Someone opened a channel with me and I am trying to open back, but when I click "open channel" and type in their name or node address, it just says "connected" and doesn't let me open a channel back.

Hi @themickeyc the current channel UI has several issues like this and we are activly working on a completely new UI that we hope will provide a much better channel management experience.
In the current version of the app however, it is possible to open multiple channels to a node that you already have channels with. It's just not intuitive for to do it. Try this:
Instead of pasting the address of node that you want to connect to in the search bar, just type some random string that returns no search results, eg aaaaaaaa. You will see a message saying that no nodes were found and button to connect manually. If you click that button, you will access a form which you can paste the node address into and connect from there!


add from/into implementations for std::mspc errors

fixes #34
It ended up being that I did have to define both. From<mpsc::*Error> implemented crossbeam_channel::*Error::Into<mpsc::*Error> but not mpsc::*Error::Into<crossbeam_channel::*Error

hmm... it's possible I don't need the second one though. Just a sec.

nevermind, this implementation is correct. You need impl Into<mpsc::TryRecvError> for TryRecvError

Looks good. Before merging, let's also add conversions for SendError, RecvError, and RecvTimeoutError. :)

You want conversions to their std::sync variants right?

Yes - since we're adding conversions for TrySendError and TryRecvError, why not go all the way and do the same for the other three error types.

sounds good, will do.

I've added conversion methods SendError, RecvError, and RecvTimeoutError.

After #41 gets merged, we won't have error types anymore. Closing.


Support Widget header

Support Widget header  ,
forward does not appear and does not work ,
can support hls format quality ,
can support one controller for two dataSource one for video and one for audio ,
or Muti for audio ,
thanks for your player ,

I added the Widget Header and fixed the double-tap-forward

VideoPlayer isn't had multi-audio support. I thought of a solution but is not pretty.

we can two controller ;
VideoPlayerController  _controller = VideoPlayerController.network( otherAudioURL ,
videoPlayerOptions: VideoPlayerOptions(mixWithOthers: true , ) );
to work audio on other controller but i can not link theme ,
thanks for your response .

Added HSL format support an MixWithOthers on the release 1.0.5


[$250] Sage Intacct - Taxes are not imported for sage intacct integration

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v9.0.74-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Action Performed:
Prerequisite
Have a workspace connected to Sage Intacct

Navigate to the workspace connected to Sage Intacct
Navigate to Accounting > Import > Tax > Enable Tax
Wait for the sync to finish

Expected Result:
Taxes are imported and displayed on the menu
Actual Result:
Taxes are not imported to the workspace after the sync is finished
Workaround:
Unknown
Platforms:

[x] Android: Standalone
[x] Android: HybridApp
[x] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/61295963-2994-47a6-88f2-dfd73ab04f5c
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021866956095465608907
Upwork Job ID:<PHONE_NUMBER>465608907
Last Price Increase: 2024-12-18

Issue OwnerCurrent Issue Owner: @allgandalf

@yuwenmemon can you maybe advise on the expected behavior here and if the proposed changes looks good?

The key is syncTax - not
+                tax: {
+                    trackingEnabled: enabled,
+                },

@dsilva Just look up the API and follow the code in the back-end and you should be able to make an assessment on the proposal: https://github.com/Expensify/Web-Expensify/blob/2cb137fa83983e634c1498a18f6bb82519e9769e/api.php#L2598-L2604
Lemme know if you have any questions!

I'll assign it to you then since I have competing priorities now. Thanks for offering.

I guess I'm confused then... why do we have trackingEnabled in the FE? It should be set to mirror the BE ideally.


Restructure disk information to appease ELK

Per discussion with @haxmeister about these two lines in get_filesystem_info():
https://github.com/haxmeister/funtoo-reporter/blob/91bd29090d785d885d0966c2fa1c94aedea12f61/lib/Funtoo/Report.pm#L411-L412
It turns out these lines were intended as a defensive attempt to avoid an error raised by submitting the data directly from lsblk --json output:

haxmeister: the error I see is " elastic search has limited support for arrays"
haxmeister: but I didn't see the actual error until after those changes

We now suspect that this error is being raised not because of strings with square brackets in them, but because the section generated by this function (and other sections) includes arrayrefs of hashrefs:
   "blockdevices": [
      {"name": "fd0", "maj:min": "2:0", "rm": "1", "size": "4K", "ro": "0", "type": "disk", "mountpoint": null},
      {"name": "sda", "maj:min": "8:0", "rm": "0", "size": "111.8G", "ro": "0", "type": "disk", "mountpoint": null,
         "children": [
            {"name": "sda1", "maj:min": "8:1", "rm": "0", "size": "243M", "ro": "0", "type": "part", "mountpoint": "/boot"},
            {"name": "sda2"...

It was suggested that we instead translate this to a hashref structure, perhaps something like this:
   "blockdevices": {
      "fd0": {"name": "fd0", "maj:min": "2:0", "rm": "1", "size": "4K", "ro": "0", "type": "disk", "mountpoint": null},
      "sda": {"name": "sda", "maj:min": "8:0", "rm": "0", "size": "111.8G", "ro": "0", "type": "disk", "mountpoint": null,
         "children": {
            "sda1": {"name": "sda1", "maj:min": "8:1", "rm": "0", "size": "243M", "ro": "0", "type": "part", "mountpoint": "/boot"},
            "sda2": {"name": "sda2"...

This is straightforward to do and I'm willing to try it.

This looks really good.. I'm going to close this. Hopefully we will get more information about how these data structure  changes are work with ES


Email Notifications about registration and password retrieval

Hey Tom :)
I need you to add two functions to your EmailNotification class:

[ ]  notification about successful registration. The function should get an email address and send him a welcome email

[ ] password retrieval. In case user forgets his password, we will send him an email with his password. The function should get an email address and a password and should send an email with his password.

in issue #183


README: mention to omit the HotModuleReplacementPlugin

Operating System: OSX
Node Version: 8.11.0
NPM Version: 5.6.0
webpack Version: 4.6.0
webpack-hot-client Version: 2.2.2

[ ] This is a bug
[ ] This is a feature request
[x] This is a modification request

Description
Was using the API for setting up middleware and was not seeing hot reloading and getting a maximum callstack error. I had to omit HotModuleReplacementPlugin from my plugins and all worked. Might be worth a mention in the README. It's great that webpack is working towards zero config, without having to add the entry scripts etc. but I had to dig through source code to see that you were already including HotModuleReplacementPlugin

Thanks for the issue :beer:
I'll add a note but in fairness, it doesn't instruct users to add that to their config either.


Updated varibles.tf, chart values.yaml & ibm-mq-operator-0.2.4.tgz to…

… support cp4i 2021.4.1 MQ Operator
Signed-off-by: Cloud-Native Toolkit<EMAIL_ADDRESS>

Closing this PR as it came from my org and repo.


Make it easy to print to the app!

Yesterday was my first day using wave and I spent 5 hours pulling my hair out and feeling very confused.
One thing I found particularly frustrating was that you cannot easily print info directly to the app. If you run print() from your .py file it prints to the terminal which gets clogged with loads of other output so it's hard to tell what is happening.
For example, when loading a dataframe, it would be nice if I could run df.head() or even print('dataframe loaded successfully'). All DSs/MLEs do this countless times per day in jupyter notebooks... but it is very unintuitive in wave. For example, in streamlit anything written on its own is automatically printed to the app. Plus, they have the write() function/method. This is one of the first things they cover in their docs and makes debugging your apps an intuitive experience.
What is the recommended way to do this with wave? Adding this to your docs would be super helpful.

Hi @codeananda, you can set H2O_WAVE_NO_LOG. This way you can see your print statements easier. See configuration docs for more useful features.

What is the recommended way to do this with wave? Adding this to your docs would be super helpful.

You can use any logging mechanism as you wish. See our docs for an example.

Hi @codeananda, you can also write logs to a file, and view the tail of a file with -f option so that you only see your logs and the tail is automatically updated.
Ex: tail -f my_wave_app.log
Also, like @mturoci mentioned, setting H2O_WAVE_NO_LOG to True was quite helpful for me.

@mtanco I meant printing to the app itself. One reason for this is that I'm using plotly and this makes using the terminal for debugging impossible (see #1374 I just opened).
I've also been developing locally so wasn't worrying about other people seeing what I push to the app.
@mturoci thanks for the H2O_WAVE_NO_LOG point. Alas, it didn't solve my problem due to #1374.
@azim-b Being honest, I've never used logging before (probably a DS/ML sin, I know!) so it feels much less natural/overkill to do this than printing (especially when checking if df has loaded). I imagine many other devs will be in my shoes... though perhaps we just need to bite the bullet and use logging!

It would need to be custom, since in general Wave is focused on building web apps, but here are some functions for "logging" to your screen:
from h2o_wave import main, app, Q, ui
import pandas as pd

@app('/')
async def serve(q: Q):
    create_log_content(q)

    wave_log(q, "testin")
    wave_log(q, "testin moar")
    df = pd.DataFrame([1, 1, 2], columns=["test"])
    wave_log(q, df)
    print(df)
    await q.page.save()

def create_log_content(q: Q):
    # Each browser tab sees only their own logs
    q.client.log_content = "# My Logs\n"
    q.page["logs"] = ui.markdown_card(
        box="10 1 -1 -1",
        title="",
        content=q.client.log_content
    )

def wave_log(q: Q, content):
    content = str(content)
    content = content.replace("\n", "\n\n")
    content += "\n\n*---------*\n\n"
    q.client.log_content += content
    q.page["logs"].content = q.client.log_content


MB-16162: add param for original zip

Jira ticket
Summary
This removes the association of the ZipDestAddress param to the DDDSIT service item and replaces it with the newly created ZipSITDestHHGOriginalAddress param. The ZipDestAddress param is used across multiple service items and stores the shipment destination address zip. This new param stores the sit_destination_original_address_id from the mto_service_items table.
The migrations doesn't move data from old params to new ones. If you think this is something that should be added please let me know.
Verification Steps for Reviewers
These are to be checked by a reviewer.
Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test
Note: enter an address id to the sit_destination_original_address_id column in the mto_service_items table.
Follow the steps mentioned here
Screenshots

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

Messages

:book:
:link: MB-16162

  Generated by :no_entry_sign: dangerJS against 04a7ad1519d064715c9e747eb50e540c63435161

This should be good to review, minus the changes in pkg/testdatagen/scenario/shared.go that will be revisited once https://github.com/transcom/mymove/pull/10806 is merged in.

@NamibiaTorres Yeah we can discuss this more broadly with the team. I'll schedule some time for us.


Increase the size of SYNCHRONIZER_ARTEFACT_MESSAGE

Column SYNCHRONIZER_ARTEFACT_MESSAGE  in DIRIGIBLE_SYNCHRONIZER_STATE_ARTEFACTS is not long enough for some of the artifacts.

Issue cloned to https://github.com/eclipse/dirigible/issues/1633

To be resolved by truncating the artifact body and not trying to put the whole message in the database

Will be available with the next release of Eclipse Dirigible


#[serde(flatten)] does not compile without "std" feature: could not find Content in de

error[E0433]: failed to resolve: could not find `Content` in `de`
  --> src/lib.rs:45:24
   |
45 | #[derive(Clone, Debug, Deserialize)]
   |                        ^^^^^^^^^^^ could not find `Content` in `de`
   |
   = note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0412]: cannot find type `Content` in module `_serde::private::de`
  --> src/lib.rs:45:24
   |
45 | #[derive(Clone, Debug, Deserialize)]
   |                        ^^^^^^^^^^^ not found in `_serde::private::de`
   |
   = note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0433]: failed to resolve: could not find `ToString` in `export`
  --> src/lib.rs:45:24
   |
45 | #[derive(Clone, Debug, Deserialize)]
   |                        ^^^^^^^^^^^ not found in `_serde::export`
   |
   = note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing this trait
   |
5  | use std::string::ToString;
   |

error[E0433]: failed to resolve: could not find `Vec` in `export`
  --> src/lib.rs:45:24
   |
45 | #[derive(Clone, Debug, Deserialize)]
   |                        ^^^^^^^^^^^ not found in `_serde::export`
   |
   = note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing this struct
   |
5  | use std::vec::Vec;
   |

This is intentional - it needs a heap allocated buffer which is not present unless you use std or alloc.


Expose prometheus generic builder.

Motivation for this change
So that people can easily try newer prometheus versions in overlays:
 self: super: {
   prometheus_2 = (super.callPackage <nixpkgs/pkgs/servers/monitoring/prometheus> {}).generic {
     version = "2.8.1";
     sha256 = "0x8w0qdh4lcf19nmdlhvgzpy08c2a932d3k49cjwhi5npcsf858n";
     doCheck = false;
   };
 }

Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Maybe rename generic to buildPrometheus to give it a less generic name.

BTW I just tested the prometheus2 test on prometheus-2.8.1 and that finishes successfully. Will push a PR soon.

See: https://github.com/NixOS/nixpkgs/pull/59182. I'll merge that as soon as the checks complete.

I just pushed the rename myself. Will merge after the checks complete.

@basvandijk thanks, for some reason the checks did not pass on my machine when I tried to build 2.8.1, which was the original reason for this PR...


Convenience issue: Two exe files must be run to start the offline client.

It would be more convenient if YgoMasterClient.exe would start YgoMaster.exe automatically if it's not already running.
I wrote this batch script for that:
@echo off

C:
cd\Program Files (x86)\Steam\SteamApps\common\Yu-Gi-Oh!  Master Duel\Build

tasklist /fi "imagename eq YgoMaster.exe" |find ":" > nul
if not errorlevel 1 start "YGO Master" /B YgoMaster.exe

tasklist /fi "imagename eq YgoMasterClient.exe" |find ":" > nul
if not errorlevel 1 start "YGO Master Client" /B YgoMasterClient.exe

I could add something similar before this line of code to check for the YgoMaster.exe process and launch it if it doesn't exist. I'll look at doing that for the next update.
https://github.com/pixeltris/YgoMaster/blob/7b5e3ecb1a1afd9d7d2cd8a31a747816f87a32d7/YgoMasterClient/Program.cs#L54

OK, thanks :)

It would be more convenient if YgoMasterClient.exe would start YgoMaster.exe automatically if it's not already running.
I wrote this batch script for that:
@echo off

C:
cd\Program Files (x86)\Steam\SteamApps\common\Yu-Gi-Oh!  Master Duel\Build

tasklist /fi "imagename eq YgoMaster.exe" |find ":" > nul
if not errorlevel 1 start "YGO Master" /B YgoMaster.exe

tasklist /fi "imagename eq YgoMasterClient.exe" |find ":" > nul
if not errorlevel 1 start "YGO Master Client" /B YgoMasterClient.exe

Same scenario, my friends and I struggling of opening 2 executables to run the Offline YGO, I wrote also mine 2 weeks ago because my friends are just asking me since they lack of knowledge in this kind of topic, we will gladly appreciate for implementing it on your next update
@echo off
mode con: cols=97 lines=21

echo Offline Yu-Gi-Oh! Master Duel Game Launcher
timeout 3 >nul
cls
echo Checks if the Offline Server Console is already running.
tasklist /nh /fi "imagename eq YgoMaster.exe" | find /i "YgoMaster.exe" >nul
if not errorlevel 1 cls && echo It seems that the Offline Yu-Gi-Oh! Master Duel is improperly closed in it's last session. && timeout 2 >nul && cls && echo The Offline Server Console is running! && timeout 2 >nul && goto RestartIt
timeout 1 >nul
cls
echo Checks if the Offline Server Console is already running..
tasklist /nh /fi "imagename eq YgoMaster.exe" | find /i "YgoMaster.exe" >nul
if not errorlevel 1 cls && echo It seems that the Offline Yu-Gi-Oh! Master Duel is improperly closed in it's last session. && timeout 2 >nul && cls && echo The Offline Server Console is running! && timeout 2 >nul && goto RestartIt
timeout 1 >nul
cls
goto ItsNotRunning

:ItsNotRunning
cls
echo Nope!
timeout 2 >nul
cls
goto LaunchIt

:LaunchIt
cls
echo The Offline Yu-Gi-Oh! Master Duel is gonna start.
timeout 1 >nul
cls
echo The Offline Yu-Gi-Oh! Master Duel is gonna start..
timeout 1 >nul
cls
echo Launching the Offline Server Console.
start /min YgoMaster.exe
timeout 1 >nul
cls
echo Launching Offline Yu-Gi-Oh! Master Duel.
start YgoMasterClient.exe
timeout 1 >nul
cls
goto Waiting

:Waiting
cls
echo Gonna wait for Offline Yu-Gi-Oh! Master Duel to be launched properly before monitoring it.
timeout 1 >nul
tasklist /nh /fi "imagename eq masterduel.exe" | find /i "masterduel.exe" >nul
if not errorlevel 1 goto WatchIt
cls
echo Gonna wait for Offline Yu-Gi-Oh! Master Duel to be launched properly before monitoring it..
timeout 1 >nul
tasklist /nh /fi "imagename eq masterduel.exe" | find /i "masterduel.exe" >nul
if not errorlevel 1 goto WatchIt
cls
echo Gonna wait for Offline Yu-Gi-Oh! Master Duel to be launched properly before monitoring it...
timeout 1 >nul
tasklist /nh /fi "imagename eq masterduel.exe" | find /i "masterduel.exe" >nul
if not errorlevel 1 goto WatchIt
cls
goto Waiting

:WatchIt
cls
echo Monitoring Offline Yu-Gi-Oh! Master Duel if it's being closed by the user.
tasklist /nh /fi "imagename eq masterduel.exe" | find /i "masterduel.exe" >nul
if errorlevel 1 cls && echo It seems that Offline Yu-Gi-Oh! Master Duel is being closed by the user && timeout 2 >nul && goto KillIt
timeout 1 >nul
cls
echo Monitoring Offline Yu-Gi-Oh! Master Duel if it's being closed by the user..
tasklist /nh /fi "imagename eq masterduel.exe" | find /i "masterduel.exe" >nul
if errorlevel 1 cls && echo It seems that Offline Yu-Gi-Oh! Master Duel is being closed by the user && timeout 2 >nul && goto KillIt
timeout 1 >nul
cls
echo Monitoring Offline Yu-Gi-Oh! Master Duel if it's being closed by the user...
tasklist /nh /fi "imagename eq masterduel.exe" | find /i "masterduel.exe" >nul
if errorlevel 1 cls && echo It seems that Offline Yu-Gi-Oh! Master Duel is being closed by the user && timeout 2 >nul && goto KillIt
timeout 1 >nul
cls
if not errorlevel 1 goto WatchIt

:KillIt
cls
echo Terminating the Offline Server Console.
timeout 1 >nul
cls
echo Terminating the Offline Server Console..
timeout 1 >nul
taskkill /im YgoMaster.exe /f >nul

tasklist /nh /fi "imagename eq YgoMaster.exe" | find /i "YgoMaster.exe" >nul
cls
if errorlevel 1 echo The Offline Server Console is properly terminated! && timeout 2 >nul && goto Termination
if not errorlevel 1 echo The Offline Server Console is still running! && timeout 2 >nul && goto KillIt

:RestartIt
cls
echo Restarting the Offline Server Console.
timeout 1 >nul
cls
echo Restarting the Offline Server Console..
timeout 1 >nul
cls
taskkill /im YgoMaster.exe /f >nul

tasklist /nh /fi "imagename eq YgoMaster.exe" | find /i "YgoMaster.exe" >nul
cls
if errorlevel 1 echo The Offline Server Console is properly restarted! && timeout 2 >nul && cls && echo Restarting the Launcher. && timeout 1 >nul && cls && echo Restarting the Launcher.. && timeout 1 >nul && cls && goto LaunchIt
if not errorlevel 1 echo The Offline Server Console is still running! && timeout 2 >nul && goto RestartIt

:Termination
cls
echo The Game Launcher is going to end.
timeout 1 >nul
cls
echo The Game Launcher is going to end..
timeout 1 >nul
cls
exit

Added in v1.5 (commit https://github.com/pixeltris/YgoMaster/commit/fe9aa117fd3ea0318d189afbd9a3b7160b4549d6).  Currently this isn't done as a sub process so YgoMaster wont auto close when YgoMasterClient closes. I might eventually change this logic, but for now it stays as is.


Remove deprecation warnings for HeadingPitchRoll function in 1.40

Remove deprecation warnings for  HeadingPitchRoll.fromQuaternion, Matrix3.fromHeadingPitchRoll, Quaternion.fromHeadingPitchRoll, Transforms.headingPitchRollToFixedFrame, and Transforms.headingPitchRollQuaternion in the 1.40 release.
See https://github.com/AnalyticalGraphicsInc/cesium/pull/5848

This change was reverted, so this is no longer needed


TypeError: argument of type 'NoneType" is not iterable.

Describe the bug
When running excludarr radarr exclude -a not-monitored -d -e --progress, error on completion.  The results are not formatted as table.
To Reproduce
Run excludarr ***arr exclude -a not-monitored -d -e --progress
Expected behavior
No error.
Versions

OS Version: Ubuntu 20.04
Excludarr version: 1.06 and 1.07
Python version: 3.10.6

UPDATE:  I ran the command with sudo and it worked without issue.

Hi, cool! Sorry for the late reply, I have taken the development of excludarr on a pause for a while. I am aware of several issues in excludarr and I tend to fix it by creating a Web UI. Where users can control excludarr within an web interface. All the present features will be in there including some new features! I have started the development this week, but it will take some time, I hope to release it before christmas :) PS. I am replying with this message on every issue to make everyone aware.


gcloud.datastore.dataset is not a function

gcloud.datastore.dataset() seems to have disappeared when gcloud bumped from 0.29 to 0.30.

True, thanks for reminding me! I'll update the readme. I don't believe the code needs to be changed.


Doc Update : Enhancement Of Contributing.md

Describe the Documentation Update
Wanted to do the following changes :-

Enhance the project structure
Add star our repository section
Add the project structure
Add need help with the basics section
Enhance the pull request steps section
Add additional method of contributing through GitHub desktop section
Add good coding practices section
Add the pull request rules section
Add the issue process section

Add Screenshots (if applicable)
No response
Confirm

[X] I agree to follow this project's Code of Conduct
[X] I'm GSSOC'24 Extd registered Contributor
[X] I want to work on this documentation issue

https://github.com/vansh-codes/Gityzer/blob/master/PROJECT_STRUCTURE.md
We already have a file for project structure, its mentioned in README.md as well, so dont create a separate one, mention this one as done in README
Points on which you have to work as described by you in the issue description

2
4
5
6
7
8
9

https://github.com/vansh-codes/Gityzer/blob/master/PROJECT_STRUCTURE.md
We already have a file for project structure, its mentioned in README.md as well, so dont create a separate one, mention this one as done in README Points on which you have to work as described by you in the issue description

2
4
5
6
7
8
9

Sure I will work on the points that you have mentioned from my points 👍