Fix affiliation bug

There were two issues in the prepare-affiliatons.lua script

Somehow during the squash/merge process, the part where it got applied in the pdf and preprint configurations got lost. This adds them back!
This PR makes it more robust for string format for affiliation lists. I'm not sure if this was actually an issue before, but I updated the example PDF to contain one of these examples just to be sure.

@tarleb – would you mind taking a look at this? Unfortunately the current build of Inara is broken for JOSS: https://github.com/openjournals/joss-reviews/issues/6917#issuecomment-2331099794

I'm thinking it might be useful to add the make test into the CI pipeline to help us be more confident in adding changes in the future, too

I'm thinking it might be useful to add the make test into the CI pipeline to help us be more confident in adding changes in the future, too

We do that already as part of the build pipeline.

@tarleb ah, I see this! perhaps splitting it out into its own chunk would be good, since the image builder workflow fails for PRs since I don't have credentials for dockerhub built in

See #70

@arfon version 1.1.1 is deployed with a fix, build should work now 🤞


Transfer save name to raw_img_key

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

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.008%) to 83.183%

Totals

Change from base Build<PHONE_NUMBER>3:
0.008%

Covered Lines:
11129

Relevant Lines:
13379

💛  - Coveralls


Change Layout of Ad

How do I change layout of Ad. The current ad view is making the list look ugly.
Is it possible by adding project in gradle or I have to manually copy paste all required classes to my project to customize layout?

@hirakchhatbar Do you really expect the beatiful layout for free? :) :100:  The current layout was implemented only for demonstration... To be serious I got that you talking about Advanced ads ... I should warn you that it is unreleased by Admob yet than you could take a look at the Express ads instead of Advanced ones (see  the recipe 3 https://github.com/clockbyte/admobadapter/wiki/Cookbook#the-recipe-3-for-the-recyclerview-scrolling-with-express-ads). The layout for Express ads could be customized in your Admob console while creation of a native banner.
However, YES you could set you own layouts for the both InstallApps and Content types of Advanced ads with the following codesnippet (also see Recipe 1 or 2)
//inject your custom layout and strategy of binding for installapp/content  ads
//here you should pass the extended NativeAdLayoutContext
//by default it has a value InstallAppAdLayoutContext.getDefault()
InstallAppAdLayoutContext installContext  = new InstallAppAdLayoutContext(R.layout.yourInstallAdLayout);
adapterWrapper.setInstallAdsLayoutContext(...);
//by default it has a value ContentAdLayoutContext.getDefault()
ContentAdLayoutContext installContext  = new ContentAdLayoutContext (R.layout.yourContentAdLayout);
adapterWrapper.setContentAdsLayoutContext(...);

Also instead our  InstallAppAdLayoutContext/ContentAdLayoutContext  you could  use your own binding strategy. Just extend these classes overriding the method bind(). See the code to get it better :)


Launch at Login not working

I check Launch at Login but when I close the preference window and then open it again it is unchecked and doesn't launch at login.
macOS 10.14.3

I've been adding it as a login app via the user system setting, but yea this should be cleaner


improve hpo test

The test on the hpo use case has been failing in recent pr -- this attempts to fix the problem.

/ok to test


Are there any known issues with catch all routes?

Describe the bug
I have a catch all route in the root of my pages folder similar like this:
[...slug].tsx
login.tsx
profile.tsx

login.tsx and profile.tsx are loading the translations without any issue. But all catch-all routes from [...slug].tsx are not loading any translations.
Occurs in next-i18next version
v8.5.5 and Next 11.0.1
Expected behaviour
Translations in catch all routes should load
Screenshots
If applicable, add screenshots or a GIF to help explain your problem.
OS (please complete the following information)
all
Does this occur to anyone? I tried to reproduce put currently I am backed up with lot of tasks that I could not manage to isolate where this issue belongs

Please provide a reproducible repository.

@isaachinman I realised it only happened on Vercel deployments: https://github.com/isaachinman/next-i18next/issues/750
It might be cool to mention that repo you wired up for Vercel users, that would be convenient! Everything works as expected after modifying the config file


Change Makefile to use standard docker build method

@hyunsun missed dockerfile ;)

It doesn't need any changes on Dockerfile :)

@hyunsun ooh nice --label. Can we do this to other repos too?

@krsna1729 sure

@pingping-lin @zdw please review

I think it is unrelated as this PR does not touch any source codes.

TC1 failure is unrelated to this patch. LGTM

@zdw Could you merge this? @pingping-lin seems have a problem with her github account.

@zdw Could you merge this? @pingping-lin seems have a problem with her github account.

Any reason why Jenkins is failing this?  Is there something wrong with the job?
I'm hesitant to approve and merge patchsets where the tests are broken.

@zdw No idea. TC1 has not been working for about a month. I left a question about it in OMEC slack before but no response.

retest this please

retest this please

TC1 is still failing.

retest this please

retest this please


添付ファイルのサムネイル貼付

Coverage remained the same at 85.667% when pulling c0889c248f6e4c5004d2ad123d2bf1e50b367136 on itowtips:modal into ff43b780508bde63c3e1dc290ef681bbd0fbe537 on shirasagi:master.

Coverage increased (+0.003%) to 85.664% when pulling 0bda100b63605268b92e5eb67bea72fcf3de230b on itowtips:modal into 50d8903ffbf203c6254751681f14dd5bc3de7b01 on shirasagi:master.

Coverage decreased (-0.02%) to 85.64% when pulling 935e0264dce00ace805987c51fd400f5d4302eec on itowtips:modal into 50d8903ffbf203c6254751681f14dd5bc3de7b01 on shirasagi:master.

Coverage decreased (-0.003%) to 85.665% when pulling 4ffbfc719f895c047f1d0c20d197c7fae32d7b5c on itowtips:modal into 9b7f481177a4942fbabbe42c0a60853bd408a2de on shirasagi:master.


Mermaid doesn't work

Visit https://hellotham.github.io/hello-astro/blog/2022-08-20-mermaid-diagrams/ and looks like Mermaid Diagrams are broken.

I'm use MS Edge v119.0.2151.72

My apologies, it looks like Mermaid v9 no longer loads from CDN. I've fixed it by loading the latest version of Mermaid. Hopefully if you sync the codebase, it will work for you as well.


JFrog CLI allows NPM Packages to be published in Artifactory which NPM Client doesn't support

Describe the bug
When we publish a npm package which is already present in Artifactory using Jfrog CLI, The CLI allows to publish the same package which has same name and versioning but when we do the same with NPM client it will not allow to publish the package with same name and version and returns 403.
Current behavior
jf npm publish allows packages to be published in Artifactory which NPM Client does not support which cause discrepancy to Customers. Ideally when we publish a package with same name and version in Artifactory using npm publish the NPM client will give a 403 error but when we publish a package with same name and version in Artifactory using 'jf npm publish' which allows package to be published in Artifactory.
Reproduction steps

Create a local npm repository in an Artifactory instance.
Configure Artifactory instance with the Jfrog CLI using jf c add command.
Then Configure npm client with Jfrog CLI using jf npm-config command.
Then publish a sample package like below(2026.0.1+1000 & 2026.0.1+1001) using the jf npm publish command.

Below is the package.json file.
{
"name": "@testproject/test",
"version": "2026.0.1+1000",
"description": "sample project",
"main": "index.js",
"scripts": {
"test": "echo "Error: no test specified" && exit 1"
},
"author": "sample",
"license": "ISC"
}
Expected behavior
Jfrog CLI should return a 403 response when we try to publish a package which is already exist with same name and version.
JFrog CLI version
2.46
Operating system type and version
Arm64/linux
JFrog Artifactory version
NA
JFrog Xray version
No response

For me, this is also clearly a bug but I found a Help Center article on this topic mentioning the JFrog CLI publishing as a workaround. This seems to be very weird to me.
I'd be really glad to have at least an option to enable the default npm publish behaviour, like jf npm publish --fail-if-exists.


[Site] Fixed Programs Page

Signed-off-by: Nikhil Sharma<EMAIL_ADDRESS>Description
There were two issues( responsiveness and margin ) with the following programs page :

Community Bridge
GSOC
GSOD
MLH
CNCF

Screenshot

** Changes Made**

Fixed both issues for all programs pages.

Notes for Reviewers
Let me know if there are any other changes we can make.
Signed commits

[x] Yes, I signed my commits.

Thank you, @NikhilSharma03. 😄


Cleaned up dependencies and release version 0.1.0.

I have cleaned up the dependencies and removed the "SNAPSHOT" from the version number.  I would like the package to be published to clojars to allow lein-jupyter to be self contained and published to clojar itself.
many thanks again for this awesome kernel.

Hey Didier,
Awesome! Thanks so much for cleaning up the code. Feel free to merge this in, you should be able to push to this repository.

What about clojar, can I push the jar there too?

Yup! please do.

Cheers!


map not working

Hi,
All working perfectly only map not working give me blank page
Screenshots
https://imgur.com/4ROdgmP
https://imgur.com/sD8jnAr
Operating System (please complete the following information):

OS
**Linux 4.15.0-96-generic x86_64

NAME="Ubuntu"
VERSION="18.04.3 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.3 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic**

Version of Docker (docker -v)

Docker version 19.03.6, build 369ce74a3c

Version of Docker-Compose (docker-compose -v):

docker-compose version 1.17.1, build unknown
Elasticsearch, Logstash, Kibana (please complete the following information):

Version of ELK (cat /docker-pfelk/.env)
ELK_VERSION=7.6.1

@ulisesgasco - Can you provide a screenshot of Kibana>>Discover?  Depending on how Docker was configured the network may be inhibiting proper filtering.  Please update the 01-inputs.conf as follows, rebuild your docker and let me know if this corrects the issue:
# 01-inputs.conf
input {
  udp {
    port => 5140
  }
}
filter {
  mutate {
    add_tag => [ "pf", "Ready" ]
    add_field => [ "[observer][type]", "firewall" ]
  }
}
filter {
  if "pf" in [tags] {
    grok {
      # OPNsense - Enable/Disable the line below based on firewall platform
      match => { "message" => "<(?<[event][id]>.*)>%{SYSLOGTIMESTAMP:[event][created]} %{SYSLOGHOST:[observer][name]} %{DATA:labels}(?:\[%{POSINT:pf_pid}\])?: %{GREEDYDATA:pf_message}" }
      ########################################################################################################################################
      # pfSense - Enable/Disable the line below based on firewall platform
      # match => { "message" => "<(?<[event][id]>.*)>%{SYSLOGTIMESTAMP:[event][created]} %{DATA:labels}(?:\[%{POSINT:[event][id]}\])?: %{GREEDYDATA:pf_message}" }
    }
    mutate {
      rename => { "[message]" => "[event][original]"}
      remove_tag => "Ready"
    }
  }
}

Update line 17/20 as needed for pfSense/OPNsense

@ulisesgasco - Can you provide a screenshot of Kibana>>Discover? Depending on how Docker was configured the network may be inhibiting proper filtering. Please update the 01-inputs.conf as follows, rebuild your docker and let me know if this corrects the issue:
# 01-inputs.conf
input {
  udp {
    port => 5140
  }
}
filter {
  mutate {
    add_tag => [ "pf", "Ready" ]
    add_field => [ "[observer][type]", "firewall" ]
  }
}
filter {
  if "pf" in [tags] {
    grok {
      # OPNsense - Enable/Disable the line below based on firewall platform
      match => { "message" => "<(?<[event][id]>.*)>%{SYSLOGTIMESTAMP:[event][created]} %{SYSLOGHOST:[observer][name]} %{DATA:labels}(?:\[%{POSINT:pf_pid}\])?: %{GREEDYDATA:pf_message}" }
      ########################################################################################################################################
      # pfSense - Enable/Disable the line below based on firewall platform
      # match => { "message" => "<(?<[event][id]>.*)>%{SYSLOGTIMESTAMP:[event][created]} %{DATA:labels}(?:\[%{POSINT:[event][id]}\])?: %{GREEDYDATA:pf_message}" }
    }
    mutate {
      rename => { "[message]" => "[event][original]"}
      remove_tag => "Ready"
    }
  }
}

Update line 17/20 as needed for pfSense/OPNsense

same issue not working
note :- all traffics goes ------- openvpn clients not wan

@ulisesgasco - can you provide a screenshot of kibana>>discover?

I solved it
add map.proxyElasticMapsServiceInMaps true on kibana.yml
https://discuss.elastic.co/t/map-is-not-visible-in-kibana-7-1/186430/7


Update README.md is not working

Testing out profile activity, so I decided to create a new public issue to test out the CI/CD activity tracker.

Solved


Suppport for setting session attributes in MockMvcRequestSpecification

#671
Enhanced RestAssured mockMvc to attach custom objects to session before sending the request

Thanks for helping out, really appreciated.


RuntimeError: stft requires the return_complex parameter be given for real inputs, and will further require that return_complex=True in a future PyTorch release.

Today there's an error occurred, what should I do? thanks!
Bug report
Describe the bug
RuntimeError: stft requires the return_complex parameter be given for real inputs, and will further require that return_complex=True in a future PyTorch release.
To Reproduce
import s3prl.hub as hub
import torch
model_0 = getattr(hub, 'fbank')()  # use classic FBANK
model_1 = getattr(hub, 'modified_cpc')()  # build the CPC model with pre-trained weights
model_2 = getattr(hub, 'tera')()  # build the TERA model with pre-trained weights
model_3 = getattr(hub, 'wav2vec2')()  # build the Wav2Vec 2.0 model with pre-trained weights
device = 'cpu'  # or cpu
model_3 = model_3.to(device)
wavs = [torch.randn(160000, dtype=torch.float).to(device) for _ in range(16)]
with torch.no_grad():
reps = model_3(wavs)["hidden_states"]
Screenshots
If applicable, add screenshots to help explain your problem.

Environment
colab

If you install S3PRL from PyPi (with pip install s3prl):
!git clone https://github.com/s3prl/s3prl.git
%cd s3prl
!pip install -e .

pip install torch==1.13.1+cu117 torchvision==0.14.1+cu117 torchaudio==0.13.1 --extra-index-url https://download.pytorch.org/whl/cu117
This is due to the upgrade of PyTorch version to 2.0 in Colab, which has caused the issue. Currently, the most direct solution is to downgrade the version to 1.13, which can run normally. Can S3PRL be updated to adapt to PyTorch 2.0?

I've encountered the same bug, and I use the following solution
https://github.com/coqui-ai/TTS/issues/2449#issuecomment-1481957085
it works.

I've encountered the same bug, I change the code at ./s3prl/s3prl/upstream/baseline/preprocessor.py

add the argument return_complex=False
Then it works


Merge pboling/master to Dynamoid/master

pboling/master has been running intricately.com's data backend for months, and has some enhanced features, like batch writes, and batch deletes.  Thanks to @alexperto for much of the work.

Coverage decreased (-4.2%) to 90.96% when pulling 8df279edc0f4da390228be8b4e25a8edb1581ecf on pboling:master into 11927dace4f7ec9081360d85e5944279221d8b25 on Dynamoid:master.

@pboling oh hadn't seen this when I commented in other issue but I guess this has same test issue?  We could try a CI besides Travis and see if we can get a more consistent build elsewhere, but still looking over the diff, you've been busy!

Also just noticed @alexperto has the batch_write_item PR open, did you pull this from his branch? don't want him to lose credit for that so if you need to make any changes to his implementation maybe you can base off his branch so he still has his commits there, same for anyone else's work that's in this branch.

Coverage decreased (-5.7%) to 89.759% when pulling 26400c8c4da9cb51d16fcebb3ad1a47498fd3f8c on pboling:master into 29bbf1e9e91612f0ef70c49083e9006aa27bfcb7 on Dynamoid:master.

Coverage decreased (-5.4%) to 90.051% when pulling 83ec650e999c4fe41cc646df6eeb1f0d196beba1 on pboling:master into 29bbf1e9e91612f0ef70c49083e9006aa27bfcb7 on Dynamoid:master.

Coverage increased (+0.06%) to 95.501% when pulling c8e75d03936532b449dc8fd6e4322694f06607ba on pboling:master into 29bbf1e9e91612f0ef70c49083e9006aa27bfcb7 on Dynamoid:master.


Improve handling of fluctuating latency

The current version does not account for fluctuations in latency to the server, so there may be an instance where one action registers at 80ms ping, but the next action (not accounted for in calculations) is registered at 70ms ping. In this scenario, the program overcompensated and the player may be able to use an action outside of expected limits. While the player has no intention to cheat, it can still raise red flags on FFlogs.
Things in consideration with these changes:

The current version seems to attempt to simulate 0ms ping. Technically/theoretically possible, but not physically possible since the player will need to be plugged into the datacentre.
30ms appears to be a good baseline ping with no double weaving issues on fast GCD jobs.
60ms is close to what is required at minimum for double weaving without clipping.

These changes improve this by using two methods:

Adding a "penalty" variable for fluctuating latency. This is calculated by taking the deviation of ping samples (sample size is currently hard coded to 10). This will ensure that actions are calculated in a consistent way relative to the latency range.
Adding a "base latency" configurable setting. This is similar to the "penalty" variable except it is static, so it is essentially simulating a certain ping value. Range of this setting is 1-60, with 30 as default. No effect on players with less ping than this setting.

Technical difference from current version:

Removed MedianRttCalculationCount. This setting did not work in the first place due to using Config::ConfigRepository(), but this had potential in its current implementation to create a lot of issues with calculations.
Improved statistic functions (GetMedianServerResponseDelay, AddServerResponseDelayItem) and added new ones. Since server response time and latency are continuous data, the current implementation did not account for time properly. This may be a minor issue, but I believe it affects accuracy of calculation.
Added new settings: BaseLatencyPenalty (default: 30) and UseLatencyCorrection (default: enabled). UseLatencyCorrection will enable my changes, and is accessible from the tray menu.
Changed log entries format for latency mitigation logging:

2021-04-04 13:28:24.849	AnimationLockLatencyHandler<PHONE_NUMBER>000BE4: S2C_ActionEffect(027f): actionId=0089 sourceSequence=0056 wait=600ms->488ms rtt=399ms/280ms/73ms latency=127ms/120ms/5ms penalty=15ms delay=399ms extraDelay=287ms

rtt is now actual/median/deviation
latency is now actual/median/deviation

Forgot to mention, these changes allow user discretion for avoiding cases like #10 , even if said issue may be technically possible from players with low enough ping. I believe it may also help alleviate #39 , since it's possible that the ping might be fluctuating in a way that messes with the extraDelay calculation.

#10: That is unironically fine, as you also can actually find logs of Japanese players playing on Japanese datacenter showing 0.58s intervals between actions. People shouldn't be alerted just because there are less-than-0.6s weaves in their logs, as the averaged weave intervals will always be at least 0.6s.
#39: My ping to EU is stable 300±10ms, but that really can't explain the round trip time of 700ms, which results in ExtraDelay being 400ms. I believe that this PR won't fix that problem, as this PR is about jitter in ping, not about round trip times.

#10: That is unironically fine, as you also can actually find logs of Japanese players playing on Japanese datacenter showing 0.58s intervals between actions. People shouldn't be alerted just because there are less-than-0.6s weaves in their logs, as the averaged weave intervals for the whole encounter will always be at least 0.6s.

I suppose it can be thought of like that, but since this program is already in the grey zone I would personally err to the side of safety by allowing the user to define their "safe" interval between actions, as well as removing/reducing ping fluctuation in the calculations.

#39: My ping to EU is stable 300±10ms, but that really can't explain the round trip time of 700ms, which results in ExtraDelay being 400ms. I believe that this PR won't fix that problem, as this PR is about jitter in ping, not about round trip times.

Maybe the current extraDelay calculation can be improved. That can be addressed in future development. If the users are experiencing an inconsistency with a "normal" round trip time, I get the feeling it has to do with ping. To know for sure we will need their logs.

#39: My ping to EU is stable 300±10ms, but that really can't explain the round trip time of 700ms, which results in ExtraDelay being 400ms. I believe that this PR won't fix that problem, as this PR is about jitter in ping, not about round trip times.

I think I just figured out the fix to that issue. I'll update this PR later after some extra testing.

I'll test this out at latest this weekend and merge it. Thanks for the contribution!

While I don't think this is going to fix servers looking like acting like potatoes when played over 300ms ping (700ms rtt is still unacceptable), the logic sounds good enough to deal with fluctuating latency (connectionwise). If you got any idea on how to deal with that situation, let me know!


ILauncher launch events and intercept

What does the pull request do?
Introduces new events on ILauncher implementations that triggers when a Uri/file launch occurs. The event arguments provide information about the Uri/file and include a property to cancel the default invocation.
What is the current behavior?
ILauncher invokes the platform handling of Uri/file directly. No event is raised.
What is the updated/expected behavior with this PR?
Desired Enhancements
Notification Event: We want to be notified by an event when a URI/file launch occurs.
Interception and Custom Handling: We aim to intercept the call and handle the URI/file launch in a customizable way.
How was the solution implemented (if it's not obvious)?
The PR adds two events to ILauncher: UriLaunching and FileLaunching. It also adds an abstract base class implementing the event handling. Existing ILauncher implementations are updated to derive from that common base instead.
The PR also turns the PlatformInfoPage in the ControlCatalog into more general Platform page and exposes Uri launcher for testing (opens Avalonia website). Additional platform features (think MAUI essentials) might be added here in the future?!
Fixed issues
See #15673

@profix898,
Please read the following Contributor License Agreement (CLA). If you agree with the CLA, please reply with the following:
@cla-avalonia agree

Contributor License Agreement
Contribution License Agreement
This Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ),
and conveys certain license rights to the AvaloniaUI OÜ ( “AvaloniaUI OÜ” ) for Your contributions to
AvaloniaUI OÜ open source projects. This Agreement is effective as of the latest signature date below.
1. Definitions.
“Code” means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to AvaloniaUI OÜ under this Agreement.
“Project” means any of the projects owned or managed by AvaloniaUI OÜ and offered under a license
approved by the Open Source Initiative (www.opensource.org).
“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
“Submission” means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
3. Originality of Work.  You represent that each of Your Submissions is entirely Your
original work. Should You wish to Submit materials that are not Your original work,
You may Submit them separately to the Project if You (a) retain all copyright and
license information that was in the materials as you received them, (b) in the
description accompanying your Submission, include the phrase "Submission
containing materials of a third party:" followed by the names of the third party and any
licenses or other restrictions of which You are aware, and (c) follow any other
instructions in the Project's written guidelines concerning Submissions.
4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term “You” in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
5. Licenses.
a. Copyright License. You grant AvaloniaUI OÜ, and those who receive the Submission directly
or indirectly from AvaloniaUI OÜ, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable
license in the Submission to reproduce, prepare derivative works of, publicly display, publicly perform,
and distribute the Submission and such derivative works, and to sublicense any or all of the foregoing
rights to third parties.
b. Patent License. You grant AvaloniaUI OÜ, and those who receive the Submission directly or
indirectly from AvaloniaUI OÜ, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license
under Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.
6. Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3 ). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6 , THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
7. Notice to AvaloniaUI OÜ. You agree to notify AvaloniaUI OÜ in writing of any facts or
circumstances of which You later become aware that would make Your representations in this
Agreement inaccurate in any respect.
8. Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the Republic of Estonia, and
the parties consent to exclusive jurisdiction and venue in the courts sitting in Talinn,
Estonia. The parties waive all defenses of lack of personal jurisdiction and forum non-conveniens.
10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by AvaloniaUI OÜ.
AvaloniaUI OÜ dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1.

@cla-avalonia agree

In my opinion this isn't the correct approach. ILauncher is clean and simple as is and works for most apps. If you need to customize a service, then you need to provide your own ILauncher implementation. That's the whole beauty of using services.
Inside your implementation you can do what you want first, raise events, then invoke the system ILauncher.
That said, I'm not sure we have a way of registering service overrides. We probably should support that.

I agree with @robloo.
Looking at your original issue:

Previously I had a custom Hyperlink(button) and URI launcher implementation. Having the launcher in Avalonia directly means that there will be third-party controls using ILauncher. So it would be great to have some flexibility to intercept, rewrite or handle Uri/file launch calls.

Typically, such scenario could be solved by having a special routed event on a Hyperlink control. Like, UriNavigating. Control would raise this event, while control consumers can handle it. If it wasn't handled - control launch the uri by itself.

Thanks for your feedback. But if I'm not mistaken, you can't do any such thing. Since V11 the service locator (AvaloniaLocator) is internal. You can't register additional services nor can you override existing ones. For that reason, you also can't modify Avalonia "core" services (by means of providing alternate implementations).
More specifically for this case, the launcher implementations are hardwired for the platform-specific ITopLevelImpl, e.g. AndroidLauncher is directly "embedded" in Avalonia.Android.Platform.SkiaPlatform.TopLevelImpl. It does not go through the service locator at all.

You can't register additional services nor can you override existing ones

That point was about a service in your application logic, not a replacement for Avalonia service.

So condensing a few ideas:

It's best to have your own services defined in your application (use Microsoft.Extensions.DependencyInjection). These services would include an ILauncher implementation like this PR where you can intercept and do whatever you want. Inside that service you would call Avalonia's built-in service.
HyperlinkButton can be customized by just handling the Click event and IsVisited properties yourself. This allows you to "intercept" the click and route it to your own launcher service first. Personally, I'm not against adding a cancellable Navigating event to HyperlinkButton in the future though.
It would be great if we could override Avalonia's own services implementation at some point in the future. Not sure when/if that will be supported though.

Closing this PR as per https://github.com/AvaloniaUI/Avalonia/issues/15673#issuecomment-2257127449
Let me know if you have any questions on redefining HyperlinkButton behavior.

Note that IsVisited can be manually set as well to indicate the URL has been navigated to visually.
I still think we should have a way of overriding core Avalonia services by an application. However, having an app-level service provider that does its own handling falling back to Avalonia's services has proven to be a solid approach so far.


[resolves #639] JAXBIntegrationTest may fail with shrinkwrap resolver…

… issue

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/wildfly-camel-pullreq/456/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/wildfly-camel-pullreq/457/
Test PASSed.


Missing Barracuda Web Application Firewall

Missing "Barracuda Web Application Firewall" and please add it's supported by Barracuda

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

ID: d6b717dc-2897-f89c-5d96-d517a0965286
Version Independent ID: 0827b9a2-1b47-f517-a9c5-2076e57f581e
Content: Find your Microsoft Sentinel data connector
Content Source: articles/sentinel/data-connectors-reference.md
Service: microsoft-sentinel
GitHub Login: @cwatson-cat
Microsoft Alias: cwatson

@applefacts
Thanks for your feedback! We will investigate and update as appropriate.

@cwatson-cat
Can you please check and add your comments on this doc update request as applicable.

@applefacts
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.

@prtanej Can you please get the offer ID for this solution in the source file updated to match the published offer ID?

#label:"backlog-item-created"

#label:"automated-data-connectors"

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close


move the PlatformMethods generation from TransformExpectPlatform to RemapInjectables, where its used

so that i dont have a completely useless architectury_inject_blah_common_hashhashblahblah thing in my jar
p.s.: i dont really know how i would test this, so please dont kill me if it doesnt work properly

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

If you want to test it you can publish the artifacts to your local maven repository using gradle publishToMavenLocal and then in your arch project you put the artifact version (shown in the console) like this
allprojects {
    architectury {
        transformerVersion = "2.1.35"
    }
}

Tests
All tests were made using Architectury Loom 1.7.412 using Java 17 on windows and linux
1.20.4 Fabric 0.15.11 ✅
1.20.4 Forge 49.1.4 ✅


no id in rpc response

Hi,
I am testing a simple use case and have found no "id" field in my response !
Am I doing something incorrect in my implementation ?
Thanks

I am sorry - I notice that it is only the case if no id is entered in the request.


Mask cache Performance Optimization for vllm

Problem
The current implementation allocates a mask for every token during generation, which significantly impacts performance.
Proposed Solution
To improve the performance, we can cache the mask on the device, as it depends on the allowed tokens from the FSM. Additionally, limiting the input to the hash function to the first 2k tokens results in a notable speedup.
Discussion
While using only the first 2k tokens for the hash may introduce potential cache collisions, the likelihood of such collisions is very low.
TODO

[ ] Provide measurements of the performance impact

My worry with limiting the number of tokens for the hash is that we might return identical masks for different lists of tokens; it is not excluded that first 2048 allowed tokens would be the same but next ones different.

I've made additional optimizations and determined that caching based solely on the state id is sufficient. This eliminates the need for the sometimes expensive hashing of allowed input tokens. As a result, on our A100 and H100 hardware, generation performance is nearly as fast as it is without a logits_processor

Could you please rebase onto main? Your diff is currently the entire repo.

Rebase is done. Don't know what happened there.
Benchmark
I also ran some benchmarks on 128 samples using an H100 PCIe GPU using LLaMA3 8B:
Without Cache:
128/128 [03:46<00:00,  1.77s/it, Generation Speed: 81.87 toks/s]

Cold Cache:
128/128 [00:41<00:00,  3.11it/s, Generation Speed: 451.46 toks/s]

Warm Cache:
128/128 [00:13<00:00,  9.74it/s, Generation Speed: 1412.09 toks/s]

In addition here are the plots of the GPU utilization during the benchmark:
No cache

Cold cache

Warm cache

As depicted in the plots: Without caching the masks, the gpu utilization remains very low. A fully warmed up cache results in an improvement of over 17x and an almost fully used GPU (in terms of GPU utilization and power consumption). I would estimate that the difference could be even higher for larger amounts of samples.

Looks good to me, thank you for contributing!


Add Table for the daprd/ CLI/Annotations for reference

Take the table from the issue here https://github.com/dapr/dapr/issues/1717 and put into reference section.
Make sure this is aligned with this existing table https://github.com/dapr/docs/tree/master/howto/configure-k8s for K8s.

Related to #378

/assign

Addressed in #1681


ImportError: No module named 'boto3'

@ljwolf There is a fresh problem with geopandas dependency on fiona (the issue is also referenced here) in that boto3 is being imported, but not listed as a requirement for geopandas, which is causing spaghetti builds to fail. Would you recommend just waiting this out or is there something more concrete I could do?

resolved

Weird bug. Good you sorted this.

I did nothing LOL. @ocefpaf fixed it.

Sorry for the headache. Due to an issue in conda-forge the dev version of fiona ended up in the main channel. I just moved it to the dev label and things should be OK now.

@ocefpaf no problem! and thanks for all your work!


UI Overhaul: Title Bar, Dark Mode, and Enhanced Visuals !!

Related Issue
[Cite any related issue(s) this pull request addresses. If none, simply state “None”]
Fixes:  #4893
Description

Revamped Title Bar: Redesigned the title bar to improve visibility and aesthetics, ensuring a modern, clean look.
Dark Mode Toggle: Added a dark mode toggle for a seamless switch between light and dark themes, enhancing user experience.
Background Redesign: Updated the background styling to improve readability and visual appeal.
Improved Container Padding: Adjusted padding for a balanced layout and better content alignment.
Hover Effects on Cards: Introduced a new hover effect on cards, changing the background and text colors for an interactive, engaging feel.
Color Scheme Update: Enhanced colors to ensure consistency and accessibility across the interface.
Overall Page Optimization: Refined layout and visual elements to create a cohesive and user-friendly experience.

These updates collectively elevate the UI, making it more responsive, visually appealing, and accessible.
Type of PR

[x] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
BEFORE:

AFTER:

Checklist:

[x] I have made this change from my own.
[x] I have taken help from some online resources.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

For this pr , please increase the level #4824

@SrijaVuppala295

The cards are not aligned properly. Cant see the content

@atmajaa ,  I have made some changes , please review it !!

@atmajaa  @sailaja-adapa , please review and merge and add level 3 PR

#4880 has already resolved the issue , she has worked on the benefits section .


Be faster

The blur in particular is still rather slow despite our many efforts to optimize it

I had some free time recently and really looked at it again, and I noticed something: All[^1] of the SIMD (AVX, to be specific) instructions are the ss (scalar single) variant, and not the ps (packed scalar) one. This means that we're effectively using the xmm registers to hold ONE float, and are just using the register to use the FMA instructions.
We should be able to get at least the horizontal pass to do packed instructions. Though I'm sure it'd be fairly difficult, because of the way the algorithm accesses memory (bounds "checking", 2 accesses per pixel). Maybe libjxl can serve as an inspiration on how to do it.
[^1]: with some relatively unimportant exceptions like mov and xor


Transpile bug when using sx basis with Y and -Y

Informations

Qiskit version: 0.23.2
Python version: 3.9.1
Operating system: 10.15.7

What is the current behavior?
Transpile gives wrong native circuit with sx basis but correct circuit with u basis for Armonk.
Steps to reproduce the problem
We will define a 180 degree rotation about y axis (i.e. the Y gate) and about the -y axis (i.e. -Y gate) using the decomposition of an arbitrary rotation.
# First the Y circuit
y_circ = QuantumCircuit(1, 1)
y_circ.barrier(0)
y_circ.rz(-np.pi / 2, 0)
y_circ.ry(-np.pi / 2, 0)
y_circ.rz(np.pi, 0)
y_circ.ry(np.pi / 2, 0)
y_circ.rz(np.pi / 2, 0)
y_circ.barrier(0)

# Now the -Y circuit
my_circ = QuantumCircuit(1, 1)
my_circ.barrier(0)
my_circ.rz(-3*np.pi / 2, 0)
my_circ.ry(-np.pi / 2, 0)
my_circ.rz(np.pi, 0)
my_circ.ry(np.pi / 2, 0)
my_circ.rz(3*np.pi / 2, 0)
my_circ.barrier(0)

Now we will transpile these using Armonk as the backend (1) with the sx basis and (2) with the u basis.
y_tcirc = transpile(y_circ, armonk)
y_tcirc.draw()

my_tcirc = transpile(my_circ, armonk)
my_tcirc.draw()

y_tcirc_u = transpile(y_circ, armonk,  basis_gates=['u1', 'u2', 'u3', 'cx'])
y_tcirc_u.draw()

my_tcirc_u = transpile(my_circ, armonk, basis_gates=['u1', 'u2', 'u3', 'cx'])
my_tcirc_u.draw()

Notice that the sx basis gives same exact transpiled circuit whereas u basis differs in the argument of u3. If you simulate the circuit, they differ by a global phase (i.e. whether you get i|1> or -i|1>), and the phase difference between Y and -Y is important, i.e. for DD, so this isn't good.
Note: You can do the same procedure with X and -X, but you actually get a difference in both bases as expected.
What is the expected behavior?
Using the sx basis shouldn't destroy phase information that the u basis preserves, as this is important for implementing real procedures.
Suggested solutions
I'm not sure how transpile works under the hood, so it's hard to offer suggested solution. However, if it's expected that sx basis may loose phase information, it would be nice for a warning to be given.
P.S. If I specify things in u basis, are they still transpiled to sx before being run, and if so, how can I implement Y and -Y as I want?

@naezzell have you tried this on qiskit 0.23.3 or 0.23.4 (which was just released a little while ago)? 0.23.3 included some fixes for the transpiler around global phase tracking (see #5618 and #5474). I haven't looked at this issue in detail yet, so I'm not sure if it will fix it, or there is something else going on.

Things seem to work in qiskit 0.23.4. Thanks for the heads up!

@naezzell have you tried this on qiskit 0.23.3 or 0.23.4 (which was just released a little while ago)? 0.23.3 included some fixes for the transpiler around global phase tracking (see #5618 and #5474). I haven't looked at this issue in detail yet, so I'm not sure if it will fix it, or there is something else going on.

Things seem to work in qiskit 0.23.4. Thanks for the heads up!


[FEATURE REQUEST] Multi-Month View for Budgets

In YNAB4, I could view multiple months of budget at a time and I really miss it! It's helpful to me to be able see the past few months of spending, by category, as I budget the current and future months. Can we bring this back?

There is already a request for this on our Trello board where requests are tracked. Check it out here; https://trello.com/c/5ON361ra/34-add-multi-month-view-to-budget-screen


use:enhance with input type="hidden" causes significant data loss for base64-encoded images

Describe the bug
When using the use:enhance directive with a form action, there is significant data loss between the client and the server. In this case, I'm passing base64-encoded PNG image data via a hidden input.
The client correctly converts to base64 and reports the correct length for the base64 image data (~1.76MB). When the data is sent to the server, the server reports that the length of the file is much less (~767kB), and the data is truncated.
I noticed this when uploading the base64-encoded data to a storage bucket and redownloading the file - only ~half the image data was transferred.
This issue disappears when the use:enhance directive is removed, and the server receives the full image.
Reproduction
https://stackblitz.com/edit/sveltejs-kit-template-default-ezby2t?file=src/routes/+page.svelte
Relevant files are:

routes/+page.svelte
routes/+page.server.js

To see the bug in action, upload the following PNG file (assuming GitHub doesn't compress it), then click the Submit button. You should see that the file size reported by the client and server differ. This issue disappears if use:enhance is removed from the form.
Note: the use of the store is not strictly necessary, but when I discovered this bug, I was working across multiple pages and using a store to transfer the data, so I've included it in this reproduction.

Logs
Server:
{ size: 1048576, last10: 'SGZWDcghqZ' }

System Info
(from StackBlitz)
  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 7.17.0 - /usr/local/bin/npm
  npmPackages:
    @sveltejs/adapter-auto: ^2.0.0 => 2.0.0
    @sveltejs/kit: ^1.5.0 => 1.13.0
    svelte: ^3.54.0 => 3.57.0
    vite: ^4.2.0 => 4.2.1

Severity
serious, but I can work around it
Additional Information
No response

Me too I’m having this problem.
No problem if I upload files with input type file, with node adapter I’ve correctly setup BODY_SIZE_LIMIT env.
But with base64 in hidden inputs the data get’s cutted

Any update on this one?

Same issue here. I solved it by converting the string to a blob on the client and then converting it back on the server for anyone else in future.
For some reason, SvelteKit reports a success (204), but truncates any string FormData to exactly 1MB.
I wouldn't mind so much but it's undocumented, so would be good to throw an error or something I think?


Misc minor fixes

@dborkmann I have gone through the bpf directory and tried to fix some of the __uX usage, but most of the changes ended up focusing on silencing the check output. @tgraf took care of the port related ones in c5c24504bf8e (bpf: Use __be16 consistently to indicate ports in network byteorder, 2017-08-29).
The output from sparse still seems mostly related to the macros, not sure how to fix them without breaking compilation. Do you see anything wrong or missed? Please let me know, thanks!

@scanf Is this just an ordering issue with github? I see the bpf.sha update commit in the middle of the series

I think the web UI is sorting on date, which is incorrect. Because of rebasing.
One easy way to know what the last commit is independent of the UI order is to look for the CI indicator (green check mark, yellow circle, etc), which shows you the last commit on the CI.
Squashed the commit to avoid confusion.


Create file before appending to a non-existing file

These test-cases show bugs reported in #8

If on Node appending creates the file (that’s what I expect) I’ll merge this right away.

Node docs: 'a' - Open file for appending. The file is created if it does not exist.

Don‘t recompile the ti-fs.js file, I’ll do it in a release.

Please also compare with #10. I fear that Ti's behaviour changes from version to version. On 3.5.0 mkdir/rmdir fail. Probably one needs multi-SDK test runs in grunt. For this take a look at https://github.com/sttts/ti-exit to exit the sim after testing.

Remove the last compile patch.

I need to set all this up. Have a look at https://github.com/yuchi/ti-cross-ci-experiments/blob/master/.travis.yml for how I do multi sdk version tests.

Very nice.

Are you in a rush? I need some time to set everything properly.
would it be ok for you to work with your homebrewed fork in the meanwhile?

Using a git hash url in my package.json for the moment. So take your time.


Author search links with archives

Pull Request Test Coverage Report for Build 115

5 of 6 (83.33%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 92.455%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

browse/controllers/abs_page/init.py
1
2
50.0%

Totals

Change from base Build 95:
0.02%

Covered Lines:
1985

Relevant Lines:
2147

💛  - Coveralls


feat: allow recipe envars parameterization

Signed-off-by: Francesco Racciatti<EMAIL_ADDRESS>
What type of PR is this?

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

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

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

/area build

/area tests

/area proposals

What this PR does / why we need it:
The value of some recipe's environment variables could be unknown when Kilt runs locally.
As a result, users need to edit the resulting template to set such variables.
This PR allows parameterizing the recipe's environment variables in the resulting template. In this way such environment variables can be easily initialized at deployment.

Special notes for your reviewer:

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

Needs approval from an approver in each of these files:

OWNERS

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

/assign @gnosek

LGTM label has been added.  Git tree hash: 60057a318bc8e909ccbe3750b6fd700ba4247352


installation issue - Let vbaDeveloper import its own code

Hi
I've set installed everything correctly or it seems, as stated in the instructions contained in the build.bas file.
Yet when start the step 10, the vbaDeveloper is expecting to import its own code. But nothing is being imported in an automatical sense...
I have to manually import the remaining .bas files.
Is it what is expected for me to do?
I'm new to the VBS environment and any help would be great.
Thanks

I went back to the issue, I clicked on F5 and everything was imported


[FEATURE] Last heard channel

I frequently monitor two different repeaters with the radio (dual watch mode), and I think it will be useful that the radio show in the screen some indication of the last received channel.
An example use case: if I'm not in front of the radio and I heard someone calling on a channel, if that station is not transmitting it is impossible to know in which channel the station was calling. Maybe a simple "LR" (last received) mark in the channel row could help in which channel TX to reply the call.
Thanks @kamilsss655 for this great firmware!

Not the Author, but based on the example they gave, I think they'd want something that last longer. The DWR indicator only lasts for a few seconds, and its purpose is to indicate you can respond on that VFO.
A dedicated LR mark that stays on permanently (unless the other VFO receives something, of course) would certainly be nice, and I think that's what fsclavo meant. This would work in "dual RX, main TX" mode (DW) too, not just DWR.

That is exactly what I mean. Dual respond is useful, but it lasts just a few seconds so if you can't reach the radio in that seconds it is useless to identify which frequency was the station calling on.

@fsclavo would making the dual respond marker stay longer resolve your issue?

Yes, at least it will be more useful!

@fsclavo sorry but this would increase the DUAL WATCH hang time from 3.6 to 10 seconds, making radio deaf to other station for 10 seconds, which is opposite of what the user want with dual watch. Because of that it will not be implemented.
For your specific use case you can modify this line of code:
const uint16_t    dual_watch_count_after_2_10ms    =  10000 / 10;
to have it at 10 seconds.

I'll give it a try, thanks!

The problem I'm trying to solve is when you close to your radio but you can
hear it.
El vie, 19 ene 2024 a las 9:12, Vertice @.***>)
escribió:

A possible but slightly ugly workaround:

Put your 2 (or more in this case) stations into a scanlist
Set ScnRev to CARRIER
Start a normal (not spectrum) scan with that scanlist

Right now, this is functionally almost equivalent to having Dual Watch
Respond on, with one added bonus: hit PTT or menu anytime, and you will
stop scan mode and go to whatever channel last received something. Restart
the scan when you're done.
The downside is having to hit PTT twice if you want to respond, the scan
hangs a bit longer than regular DWR, and you need to stop and restart your
scan to see who last sent something. A dedicated Last Received marker,
distinct from and independent of the DWR respond marker, would be better,
but this is close enough probably.
—
Reply to this email directly, view it on GitHub
https://github.com/kamilsss655/uv-k5-firmware-custom/issues/80#issuecomment-1900306375,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACAPKSQZM6GFAVEKVMTONPTYPJPLJAVCNFSM6AAAAABCAUOG36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBQGMYDMMZXGU
.
You are receiving this because you were mentioned.Message ID:
@.***>


Establish versioning strategy.

Goals
Because JupyterLab relies on the goodwill of early testers, alpha users, and extension authors, we need to try as hard as possible to reward these community members with new features and endeavor to limit breakage as much as possible. Correct use of semantic versioning is a necessary but insufficient part of achieving this.
Extensions
Extensions will require the jupyterlab package from npm, which means that extension authors will be able to specify the version range that their extensions support.
Before we have an extension loading system
Currently, we have used the "identifier" portion of a semantic version in the master branch between releases:

0.1.3-alpha.0 (i.e., the -alpha.0 portion of this version)

However, this has caused extensions that require 0.1.x or ^0.1.2, etc., to detect a mismatch and the built webpack bundle has consequently contained multiple versions of JupyterLab. This has not caused a build error and instead has generated a run-time error.
This means that at the moment, if we use optional identifiers in our versions, all users of master and all extension authors will end up with broken application state. So until we have the new extension system, use of the identifier portion of semantic versioning should be discontinued. Otherwise we will effectively be punishing the users and testers of the bleeding edge.
But this problem is going away.
After we have an extension loading system
When the new extension system is ready to go, extensions will be loaded by the server. The server will be able to check what the current version of JupyterLab is and it will be able to use the "loose" interpretation of semantic versioning, in effect discarding the identifier portion of the version. So our earlier example: 0.1.3-alpha.0 will be interpreted as 0.1.3 which will match the constraints that an extension will be using (e.g., 0.1.x or ^0.1.2).
This frees us to create -rc.1, .rc-2, etc., releases without worrying about breaking things for extension authors or for users of the master branch. An extension author who wants to test against the latest code will be able to check out master and rely on the semantic versioning constraints to just work.
Versioning between releases
Because it is never clear whether our next release will be a patch, a minor release, or a major release, I would propose that the version number in the master branch's package.json file reflect the currently released version. The semantic versioning spec is not prescriptive about this and if we adopt another policy, that's alright, but it seems to me that until we know exactly what our next version is going to be, there's no point in creating a preemptive version string that we may have to roll back upon discovery of a last-second patch or roll forward upon discovery that no new patch was needed before jumping major or minor numbers.
cf. https://github.com/jupyter/jupyterlab/pull/225

Also cf. https://github.com/mojombo/semver/issues/200 and https://github.com/mojombo/semver/issues/124.

+1 to not using prerelease versions (i.e., the -alpha.N postfix) for the time being. I'm not sure it's a good idea (in that it may cause confusion) to change semver policies with respect to the prerelease version compatibility, but we can definitely cross that bridge when we can have 3rd party extensions. I also like the purity of the idea of using an incremented version number just after we release (nominally a patch increment, but when a breaking change is made, incrementing the minor or major versions), but as you can see on the semver issues I linked above, there is a lot of discussion about how to do that. One interesting idea was to (ab)use the build postfix (+dev.N) for this.

I'm open to other strategies than the one I outlined, but I would argue against doing any very "clever" like using postfixes in a nonstandard way.
Your other suggestion of using an incremented patch is at least non-magical (:zap: + :sparkles:), which I find preferable.

By the way, that's essentially what we did in this last release - we released 0.1.2, and we ended up incrementing the patch level to 0.1.3.
I'm generally -1 on abusing the system (i.e., making build information to actually indicate changes...), so I'm agreeing with you there.

cf https://github.com/jupyter-incubator/dashboards_server/pull/275#issuecomment-236209488, we need to be careful about making patch releases that affect other users.

+1 on incrementing the patch level right after every release. Otherwise it is not possible for downstream consumers to communicate through the version that they depend on the latest HEAD.

@svenefftinge That's a good point, I hadn't considered that extension authors might build extensions that are dependent on master and not on published versions.

I'll give this a read. @jhpedemonte might want to also.

I agree with incrementing the patch number on master immediately after a release. How about adding the following rule to account for breaking changes ahead of 1.0:
Before cutting a release from master, if there are breaking changes since the patch number was last incremented, commit an increment to the minor number. Then make the release.
This helps prevent unexpected breaks like https://github.com/jupyter-incubator/dashboards_server/pull/275. I'm not sure if it helps or hurts packages that want to depend on master HEAD.

@parente I would actually take it one step further: as soon as you know you're committing breaking changes, even before a release, I would propose that very first PR that has the breaking changes should include the version bump in it. That way if it is not merged, no harm done, but if it is, the master version will reflect its level of compatibility with the existing ecosystem.

@afshin That works too, as long as you can coordinate one minor version bump per release across everyone making breaking changes.

There is a small risk to incremement it more than once though if there are
multiple backward incompatible changes.
On Aug 3, 2016 6:03 AM, "Afshin Darian"<EMAIL_ADDRESS>wrote:

@parente https://github.com/parente I would actually take it one step
further: as soon as you know you're committing breaking changes, even
before a release, I would propose that very first PR that has the breaking
changes should include the version bump in it. That way if it is not
merged, no harm done, but if it is, the master version will reflect its
level of compatibility with the existing ecosystem.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jupyter/jupyterlab/issues/566#issuecomment-237131164,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACSXFhChbFBlsL4bne4rcX4IOTlF-jnJks5qcBMggaJpZM4JXYoX
.

@afshin In the case if you have nightly builds(https://github.com/jupyter/jupyterlab/issues/665)
the version between releases should be different from the latest release.

@akosyakov For nightly builds, we can use the identifier portion of the version once we have a plugin build system. Before then, any build that uses identifiers is going to break builds, so we're probably going to hold off on nightly builds until plugins are ready.

very first PR that has the breaking changes should include the version bump in it

I think version bumps should be done in master, after a PR is merged, not in PRs. Otherwise we get into situations where multiple PRs have multiple increments, depending on when they were started, and the merge order makes the version number jump around.
@minrk, if I recall correctly, you had a system for doing this and have the version bump tested in CI before merging. How did you do that?

I think what you are referring to is the way I typically build a release:

bump version, commit (to master, or 4.x, etc.)
push to my repo, not jupyter or ipython
this triggers CI, which I have enabled on my fork, in addition to the main repo
tag, push to jupyter once CI finishes on my branch

I think it's generally fine to bump versions in PRs if people are more comfortable with that, but we don't usually do it that way in other repos. Version bump PRs shouldn't be outstanding for long at all (in particular, they probably shouldn't do anything but bump version), so I wouldn't worry about multiple outstanding version bumps or anything.

Version bump PRs shouldn't be outstanding for long at all (in particular, they probably shouldn't do anything but bump version), so I wouldn't worry about multiple outstanding version bumps or anything.

I think the proposal under discussion was bumping version number in the PR making the breaking changes. If there is a specific PR for bumping a version, then it's -0 for me (and +0 if the merge for that PR is a fast-forward merge).

Needs a bit more discussion...

@afshin, @blink1073, @ellisonbg, and I discussed this. @blink1073 brought up that many npm packages use the "bump just before release" model, with the understanding that if you are running a dev version, you should use a git commit hash or the github URL to pull down changes since the version was released.

For example, Backbone has v1.3.3 in their package.json file, but it was released a dozen commits and a few months ago.

OTOH, CodeMirror takes the approach of bumping a patch version after a release: https://github.com/codemirror/CodeMirror/commit/08b8b7b0d4a2168756829d421649ca149e3cc151

Consistency is great: jQuery uses a -pre tag: https://github.com/jquery/jquery/commit/93f706200c6101df137469ba2e0d965e93508991

Decision
At the Jupyter Lab dev meeting, we decided that we should bump the version number immediately before a release.
The idea is that an extension author who wants to test against the development version will only have issues if there is an actual incompatibility in the dev version ... which would have happened whether the version had been changed or not, but the default scenario will be that an extension author who wants to test an extension against master and has no incompatibilities will have a smoother path.


Find out if okay to change "Log In" to "Sign In"

0

ZenHub Information
This information is updated automatically. To modify it, please use ZenHub.

Fine with me. Seems like there's already some UX research behind this that supports "Sign In / Sign Out" but also "Register / Join" instead of "Sign Up"


Re-add the ghost import to da init

Needed for libraries that implicitly assumed da.ghost namespace was
automatically imported.
See #3830.

Failure is unrelated. @shoyer, can you confirm this fixes your issue?

Well this should be done anyway as part of the deprecation process. Merging. Thanks for catching this @shoyer.

Thanks @shoyer for the report and @jcrist for the fix. Sorry we missed it in the review.


Add camel-splunk and camel-splunk-hec starters

Adds splunk and splunk-hec as per https://issues.redhat.com/browse/CSB-3062
Hopefully I didn't miss anything ... cc @cunningt
Thanks !

@johnpoth Can we close this one out?    I think these changes went into the initial productization.


How to set project loglevel

Hi,
Thanks for putting this library together.  In using kotlin, I was putoff by the long/complex answers to the simple question "how do you log in kotlin (http://stackoverflow.com/questions/34416869/idiomatic-way-of-logging-in-kotlin)".
I'm using Klogging as follows:
    companion object: KLogging()

     init {
        logger.info("NewsArticle initialized: " + this)
      }

This works nicely, but when I do logger.debug, my IntelliJ IDEA run console doesn't show any output.  Do you know how I could set the console logger to debug or trace levels?  Is this an IDE setting, or can it be set in the call to KLogging()?

I saw a similar question on SO: http://stackoverflow.com/questions/43146977/how-to-configure-kotlin-logging-logger
Let me know if that clear things.

updated the frequently asked questions

Despite the FAQ entry I believe we desperately need a concrete example on how to set the log level when using e.g. logback as the logger implementation. I have in build.gradle:
dependencies {
    // Use logback-classic as the logger for kotlin-logging / slf4j as it allow changing the log level at runtime.
    compile 'io.github.microutils:kotlin-logging:1.4.5'
    compile 'ch.qos.logback:logback-classic:1.2.3'
}

And in my main.kt:
internal val log = KotlinLogging.logger {}

// ...

    if (!debug) {
        // Logback's default log level is DEBUG, so change that to INFO unless --debug is given.
        (log as ch.qos.logback.classic.Logger).level = ch.qos.logback.classic.Level.INFO
    }

But that gives
Exception in thread "main" java.lang.ClassCastException: mu.internal.LocationAwareKLogger cannot be cast to ch.qos.logback.classic.Logger

So how am I supposed to access the logger implementation via kotlin-logging in order to call the logger implementation-specific code to set the log level?

Can you try to do it without the casting?

I think I understand the issue you mention. What I suggest is to add to the KLogger interface a method - getUnderlyingLogger() or something similar that will provide the underlying log implementation which can be casted to ch.qos.logback.classic.Logger in the case of logback. What do you think about this solution?

getUnderlyingLogger() or something similar that will provide the underlying log implementation

That would probably work, although it seems a tad inconvenient. That is, slightly less convenient than being able to just casting the main class.

Another alternative is to use xml configuration

But that does not seem to be usable if I need to change the log level at runtime triggered by external events (potentially multiple times).

I can add that, probably a property underlyingLogger is more appropriate. will you use that if such exists?

will you use that if such exists?

Well, given that I just migrated to slf4k because of that missing feature, probably not right away, but I'll certainly give it a try in one of my next projects.

ok, I will add that to 1.4.6.
On Tue, Jul 11, 2017 at 9:45 PM, Sebastian Schuberth <
<EMAIL_ADDRESS>wrote:

will you use that if such exists?
Well, given that I just migrated to slf4k because of that missing feature,
probably not right away, but I'll certainly give it a try in one of my next
projects.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/MicroUtils/kotlin-logging/issues/20#issuecomment-314536524,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACj0QYANW6kVho2ylzmT74LCLZ3MidSlks5sM8LPgaJpZM4M0wmA
.

1.4.6 released

This works although it's not ideal:
import ch.qos.logback.classic.Level
import ch.qos.logback.classic.Logger
import org.slf4j.LoggerFactory.getLogger

var org.slf4j.Logger.level
    get() = (getLogger(name) as Logger).level
    set(value) { (getLogger(name) as Logger).level = value }

logger.level = Level.DEBUG

This is already an old thread but the topic fits my question. How do you set the log level for the non-JVM targets. What is the underlying logger in that case? I am specifically asking for iOS and wasmJs.

This is already an old thread but the topic fits my question. How do you set the log level for the non-JVM targets. What is the underlying logger in that case? I am specifically asking for iOS and wasmJs.

See: https://github.com/oshai/kotlin-logging/wiki/Multiplatform-support

Via your link I finally found the solution but the description in there is wrong.
Instead of
KotlinLoggingConfiguration.LOG_LEVEL = KotlinLoggingLevel.DEBUG
it must be
KotlinLoggingConfiguration.logLevel = Level.DEBUG
Maybe you can fix the documentation but many thanks for the hint and the tool anyway. I like it.

I updated the wiki.


Feature Request: slideshow pictures and video together

When I enter an album the photos and videos are separated for the purpose of starting a slideshow, I'd like to do both together.
Am I missing something?

Slide shows are photo specific or you can play videos, not both in a single selection today. It's been thought about in the past but have never had any requests for it. We'll keep it in for consideration.

This is the primary reason that I use Google Photos. The slideshow shows videos along with the photos. My slideshows always include strategically placed short video clips. Photo View is not useful to me without this feature

We love the Google Photo View app, thanks for providing it.
Google Photos now supports mixing photos and videos in "slideshow" playback as a standard feature.  I am not sure if it was included in the API.  It was an excellent enhancement.  If you could implement it here it would be great.
One additional feature would make it perfect - the ability to switch sound on and off.  We usually leave a show running while people are over (and by ourselves) and when using Google Photos directly often have to sprint to the volume as a video blasts out it's own sound over the top of whatever else we are playing.
Thanks again.

Add me to the list of users requesting this feature.  Google Photos doesn't discriminate against videos that are interspersed with photos in an album, so Photo View shouldn't either.

I installed this app with the hopes of making a mixed videos+photos screensaver for my Roku tv.  If this feature ever gets competed you'll be the only service to have done it correctly.  Other's have tried, none seem to work...

@ibdone - Roku doesn't allow Video's to be played in the screensaver. Due to this limitation, only photos are played.

I would like to request this feature as well.  We want to be able to include videos in our slide shows so that we can break up the stream of pictures with some videos.


matterjs  sleep problem

The rigid body first sleeps, then moves to its position and then activates. But why does it disappear after activation instead of falling down??
this my code
https://codepen.io/a6965921/pen/MWbazwm
  setTimeout(function(){
         imageBody.position.x=231;
        imageBody.position.y=111;
    Matter.Sleeping.set(imageBody, 0)

  },1000)

I think you need to use Body.setPosition instead here rather than setting position directly (some properties require using setter functions, you can find them in the docs).


Fix issue where reordering of previous searches list may cause thrash…

Hm, so selecting a previous search at index two or above may cause thrashing of elements in the "Recent Searches" list, which may now cause selection events to fire, preventing navigation. Don't know why this wasn't happening last week under the same test conditions. Hooray.
Solution (for now) is to not update the previous searches array used in the dom-repeat template on new search, but rather only update the list in localStorage, and update the recent searches array on widget load.
Bah.

Seems to fix the issue for me on Chrome (MacOS). In Firefox the search terms are still not actionable, and in Safari items are never added to the list.

So this fixes up the FireFox stuff as indicated by https://github.com/Brightspace/d2l-my-courses-ui/pull/102/commits/ff3f142ca2488f78bfb9b1a383c794dd27402843.
Safari is still broken for me completely, in the sense that the previous searches are not displayed. I investigated and it is purely a display issue, so not related to this PR in any way. I have logged this as #104 .

Hokay, fixed the deps problem, should be good to just use ^ now.

Poked around with this - seems to make sense to load recent searches on page load anyway, LGTM! :shipit:

...having said that, just looked at @CodeBaboon's comment and #105. That's a separate thing, though, I'd imagine? (Considering it exists with and without this PR)

Yeah my PR is separate. This one LGTM.


Localizely SDK dependency version constraints

Hello!
I didn't find a better place to report the issue.
The Logger dependency seems to be constrained to version 1.0.0, which causes an issue when trying to use a newer version.
Overriding the dependency works but it is not ideal.

Hi @atoka93
Thanks for reporting this!
We will consider updating it for the next sdk version release.

The latest release (localizely_sdk 2.5.3) should fix this issue.
Closing it as resolved. In case of any irregularities, feel free to open it.


command provided on readme does not work

DS:DiskStation[~/Synology_HDD_db]$ sudo -i ./syno_hdd_db.sh -nr
Loading module 'filesystem' ...
Loading module 'kernel' ...
Loading module 'message' ...
Loading module 'mount' ...
Loading module 'platform' ...
Loading module 'utils' ...
Loading module 'volume' ...
-ash: ./syno_hdd_db.sh: No such file or directory
so i use this insisted
DS:DiskStation[~/Synology_HDD_db]$ sudo su
DS:DiskStation[/volume1/homes/leonpano/Synology_HDD_db]# ./syno_hdd_db.sh -nr
Synology_HDD_db v3.4.82
DS2419+ DSM 7.2.1-69057-3
StorageManager 1.0.0-0017

Using options: -nr
Running from: /volume1/homes/leonpano/Synology_HDD_db/syno_hdd_db.sh

... output after is not needed for this issue

Thanks.
If the script is in your home folder and you try to run the script with sudo -i ./syno_hdd_db.sh you'll get the "No such file or directory" error. This is because sudo -i uses root's profile, and the script is not located in root's home.
I've changed the readme to show sudo -s which doesn't change to root's profile.


Add site.github.public_repositories[].releases

For each public repository rendered, we will also list releases for them.
Fixes #221.

@mattr- It's already allowed: https://github.com/jekyll/github-metadata/blob/master/lib/jekyll-github-metadata/client.rb#L19
Pushed a fix for Rubocop.

@jekyllbot: merge +minor


Wasi input-stream: use same errors as output-stream

Based on #7022

Making input-stream use the same error type as output-stream is nice, however I'm curious why you chose to change read to work like write, instead of changing write to work like read.
Read returning a tuple<list<u8>, stream-status> on success meant it could report a successful read with data and end-of-stream at the same time. The earlier idea was that hosts could eventually use that to save guests an extra trip through poll_list and read just to find out that the stream is closed. It's admittedly not urgent that we do that optimization right now, but unless there's a reason not to, it seems worth keeping the option in the interface.

My take on it was, its a very rare corner case that we can indicate the end of stream has been reached while still returning some input, whereas it makes the interface more difficult to understand, use, and implement. As we went through and changed the implementation and tests to this new interface, both "felt" more appropriate. It is subjective, and initially I did it the other way because that seemed like an advantage, but now that I've done it both ways I prefer this.


[docs] crontab example

I suggest to add crontab -e example code on README.md.
crontab -e

0 0,6-23 * * * PATH=$PATH:/opt/homebrew/bin && dhapi buy_lotto645 -q

Sadly, closed by this comment: https://github.com/roeniss/dhlottery-api/pull/43#issuecomment-1584858381


SpaceBeforeTokenChecker triggers on unary_?

This triggers the SpaceBeforeTokenChecker with colon
def unary_- : scala.Int = ....
Obviously the same applies to + ~ too.

SpaceBeforeTokenChecker is very generic. It isn't meant to have too many exceptions.


Add license information

Creative Commons Attribution 4.0 International
In nutshell:

Attribution required - Appropriate credit and link to license
Can be modified and reused in any medium and format
Can be used for any purpose, even commercially

Signed-off-by: Dimitar Tomov<EMAIL_ADDRESS>

The boring step that is needed, so everyone knows what we do is to be shared in any way or form. Goal is to lower the knowledge barrier and make it easier for newcomers :)

@iolivergithub we should figure out the license.
I firmly believe we must guarantee the (future) valuable information here can be reused and currently there is no such guarantee. So, I will add it as topic of discussion for the next https://developers.tpm.dev/events/past call

Please close this PR


feat: Added support for Cross-Account ECR for docker-build module

Description
Support for Cross-Account ECR for docker-build module
Motivation and Context
AWS Lambda now supports cross-account container image pulling from Amazon Elastic Container Registry https://aws.amazon.com/about-aws/whats-new/2021/11/aws-lambda-support-cross-account-image-amazon-elastic-container-registry/
Breaking Changes
None
How Has This Been Tested?

I have tested and validated these changes using this example

module "docker_image" {
  source = "../../modules/docker-build"

  create_ecr_repo = false
  ecr_address     = "XXXXXXXX.dkr.ecr.eu-central-1.amazonaws.com"
  ecr_repo        = random_pet.this.id
  image_tag       = "1.0"
  source_path     = "context"
  build_args = {
    FOO = "bar"
  }
}

Thanks, @panessa !
v2.24.0 has been just released.


[META] System Indices for Extensions

OpenSearch plugins utilize system indexes to store information that persists through the cluster, such as the security configuration for the Security Plugin or .replication-metadata-store indexes for cross cluster replication. These indexes contain data specific to the plugin and should not be altered by any other plugin or application.
This meta issue is tracking what associated work needs to be done

[x] https://github.com/opensearch-project/security/issues/2530
[x] https://github.com/opensearch-project/OpenSearch/issues/6589
[x] Pick a solution
[ ] #2553
[ ] #2554
[ ] Create documentation issue for new permission once ready

Option 2b: Extension service account, scoped to specific system index [Recommended] is best aligned based on the current considerations and discussion topic.  I'll add associated work to this meta issue.

@opensearch-project/security I've added work items for this META issue, please review the tasks on this item and if we need any more detail.
Small note; I did not create an issue for the documentation because I think we should create the task on the documentation-website by whoever will own that work when its ready.

I agree with your point @cwperks , though I lack end user viewpoint what made me agree with you is tha, from a code structure point of view, the issue became much clearer once i considered these "Extension Indicices: as a different category from the already existing "protectedIndices"  listed in the SecurityIndexAccessEvaluator class

'System index' is the name of the feature in OpenSearch so we seem pretty locked in.  I'm open to alternative names, when I think of 'extension index' / 'protected index' or something, it would be implemented differently without the relationship to SystemIndexPlugin which is a requirement for backward compatibility with the existing plugins.

@peternied Can we mark this issue as closed for 2.10?

@DarshitChanpura I still see tasks that are incomplete, seems like we shouldn't close it.  What do you think?

Is https://github.com/opensearch-project/security/issues/2554 still needed?
https://github.com/opensearch-project/documentation-website/issues/4736 is pending PR merge.

@DarshitChanpura  thanks for creating the other tracking issue, I'm going to consider this one resolved and we can us that seperate issue for tracking what might be needed for extensions release


Allow JSCS to run stand-alone (ensure ember-suave custom rules are only declared once)

Currently, stand-alone JSCS linting doesn't work with ember-suave because of the custom additionalRules used by ember-suave.  So, this PR allows you to specify the ember-suave custom rules in your .jscsrc as additionalRules without breaking the brocolli build that also wants to add the ember-suave custom rules.
Running stand-alone JSCS is very handy if your editor supports JSCS linting (I'm using this with sublime text 3)
This PR addresses https://github.com/dockyard/ember-suave/issues/43

LGTM - :+1:
As an aside: we might also want a blueprint that generates the default into the project at .jscsrc (to make it simpler to get started if you need/want to configure manually).

@rwjblue great!  I think adding a blueprint would be a nice addition although probably should be a separate PR.  I can amend this PR to update the README if that sounds like a good interim step?

Totally, agree that it should be a separate PR. I was just observing that it would be nice to have once this lands (hint hint :wink: )...

@rwjblue gotcha! :)

@spovich Sorry for the long delay! I want to bump some dependency versions as well, but I'll release shortly. Thanks!!


pion / chunk-upload.php

return [
/*
* The storage config
/
'storage' => [
/
* Returns the folder name of the chunks. The location is in storage/app/{folder_name}
*/
'chunks' => 'chunks',
'disk' => 's3',
]
how to change disk from local to s3 to upload chunk file to my bucket s3 ?

You can use s3 chunk cloud upload using their SDK - currently not in this package or you can upload it after chunks were merged: https://github.com/pionl/laravel-chunk-upload/wiki/Saving-to-Cloud


Blank white output

Hi,
Can I using html2image on Ubuntu Server 20.4?
I am runnig with custom parameter "hti.browser.flags = ['--no-sandbox']" but output is blank png.
Without --no-sandbox parameter I get this error:
Running as root without --no-sandbox is not supported. See https://crbug.com/638180.

Try adding a timeout parameter? I was getting partially blank pages sometimes without it. Number is in milliseconds.
hti = Html2Image()
hti.browser.flags = ['--virtual-time-budget=50000']

Its still white for me I even use more than budget like 500000 @maphew


test: Upgrade Mockito to 4.11.0

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

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

Fixes #<issue_number_goes_here> ☕
If you write sample code, please follow the samples format.

This PR build on work from @suztomo: https://github.com/googleapis/java-firestore/pull/1344


Solution Canvas app support

Hi - great tool. I'm not sure who to reach out to for discussion, so apologize for this issue.
Use Case:
We want to have multiple versions of the same canvas app in a solution and then use power apps unpack/pac to merge.
For example:

MainApp
MainAppVnext
MainAppOtherFeature

Do you know if the solution has other metadata we also need to merge?
At a fundamental level, should using the canvas app unpack and pac work across multiple canvas apps?
Thanks!
Jon

Hi Jon,
Pac/unpack is for .msapp files and don't support solutions at this time. We don't know the answer about solution metadata. One way you can try is to pac/unpack the different versions of apps respectively, then merge them manually or with some version control tools.
Hope it helps.
Best,
Claire

Hey @JonKragh - I'd recommend checking out the solution verb available in the Power Platform CLI: https://learn.microsoft.com/en-us/power-platform/developer/cli/reference/solution
You may be able to use the solution unpack command to accomplish this.

@tomjschneider @clairewu0218 we actually now have pac/unpack for the canvas apps working in conjunction with solutions. I think we may be doing some unique ALM things now with branching/merging apps similar to typical prodev workflows.


Remove all flake 8 issues

Some people will run flake8 on their repos so code in this repo should be flake8 neutral.
Also commented out trove classifiers for Python versions that are EOL or will be EOL in the next 30 days.
flake8 testing of https://github.com/kennethreitz/setup.py on Python 2.7.13
$ flake8 . --count --exit-zero --max-complexity=10 --show-source --statistics
./setup.py:48:1: W293 blank line contains whitespace

^

./setup.py:64:16: F821 undefined name 'FileNotFoundError'
        except FileNotFoundError:
               ^

./setup.py:68:80: E501 line too long (87 > 79 characters)
        os.system('{0} setup.py sdist bdist_wheel --universal '.format(sys.executable))
                                                                               ^

./setup.py:110:34: W291 trailing whitespace
    # $ setup.py publish support.
                                 ^

./mypackage/__init__.py:1:1: F403 'from .core import *' used; unable to detect undefined names
from .core import *
^

./mypackage/__init__.py:1:1: F401 '.core.*' imported but unused
from .core import *
^

./mypackage/core.py:1:25: W291 trailing whitespace
# Insert your code here.
                        ^

1     E501 line too long (87 > 79 characters)
1     F401 '.core.*' imported but unused
1     F403 'from .core import *' used; unable to detect undefined names
1     F821 undefined name 'FileNotFoundError'
2     W291 trailing whitespace
1     W293 blank line contains whitespace

7

I hate every one of these changes, except two (fixing whitespace at the end).

Python's will be removed when they are EOL'd, not before.


Inconsistent Shipment Search Results: No Records Found Despite Default Listing

Current behavior
Inconsistency in the shipment search functionality of our application. When users perform a search for shipments, the system is returning "No records found" even when shipments are displayed in the default listing view. This behavior is confusing and can lead to frustration for users trying to locate specific shipments.
Expected behavior
The search results should display relevant shipments when users perform a search, and the results should align with what is displayed in the default listing view.
Steps to reproduce the issue

Can you handle fixing this bug by yourself?

[ ] YES
[ ] NO

Environment details

Browser:
OS:
Code Version:

Additional information
Screen recording

Closed by #265


[#1964] Implement data structures for storing activities

Introduces the templates and data structures for storing, fetching, and updating activities on items.

ActivityTemplate: Adds activities and uses to items
ActivitiesField: Mapping field that stores activities and initializes as a custom Collection.
ActivityField: Field inside the mapping field that stores an individual activity, initializing as a data model of the correct type.
ActivityCollection: Subclass of Collection that organizes activities and provides a getByType method to retrieve a list of activities of a certain type.

In the process this splits fields.mjs into separate files because the original file was getting quite long.

This introduces the base activity type, UtilityActivity, which doesn't have much behavior of its own and can be used for when an item doesn't have a more specific activity it requires. For example the spell "Mage Armor" would have a UtilityActivity that is just responsible for applying the active effect to the caster.
In order to support the necessary inheritance structure, the base behavior of all activities is implemented in ActivityMixin. This mixin doesn't have much behavior now, but will eventually handle activing the activity and consuming uses.

A few modifications have been made to Item5e in order to support CRUD operations on activities using the same API that is used for other documents (e.g. calling
item.createEmbeddedDocuments("Activity", [{ type: "utility }]) to create a new activity). This involved adding some additional behavior to getCollectionName and getEmbeddedCollection to recognize special collections defined withing system data.
In addition, ActivityMixin inherits from PseudoDocumentMixin, a new set of base methods to implement these CRUD operations. Eventually Advancement should be modifies to use this new setup so that the createAdvancement and related methods on Item5e can be removed.

Before I continue with review, I wanted to comment on the high-level direction of this PR. I really don't think we should be going to all this effort to make activities behave like pseudo embedded documents. It seems like a lot of extra complexity and overhead, without obvious tangible benefits. Can we stick with a simple CONFIG.DND5E-based registration, and some Item5e helper methods like createActivity, updateActivity, and deleteActivity, until it becomes more clear that we would need more complex things like pre- and post- CRUD handlers.

The main advantage is no having to figure out a bespoke API just for activities. If you know how to use the existing createEmbeddedDocuments API that core offers then you can use that to create and manipulate activities rather than having to find the createActivity API and figure out how to call it.

rather than having to find the createActivity API and figure out how to call it.

Not gonna lie, that isn't a big ask.

The main advantage is no having to figure out a bespoke API just for activities. If you know how to use the existing createEmbeddedDocuments API that core offers then you can use that to create and manipulate activities rather than having to find the createActivity API and figure out how to call it.

It's an awful lot of plumbing just for that. We also have to keep the API surface in-sync whenever the core embedded Document API changes. It doesn't seem worth it in order to enable calling item.createEmbeddedDocument("Activity") vs. item.createActivity().
I may not be understanding the full extent of the proposal or plans, but it doesn't seem like complex manipulation of activities is necessarily required in order to achieve our goals with them. Basic CRUD operations will be limited to the item sheet creating, editing, and deleting activities. Then the majority of their implementation complexity comes from what happens when  an activity is invoked, which seems mostly tangential to their CRUD workflow to me.


.nav-pills focus, background still blue

Hello,
The v2 is very good, but (there is always a but) I found a graphic "bug" for nav-pills : after selecting a pill, it becomes blue. You have fixed this for hover, but not for the focus.

I corrected that way:
I replaced
.nav-pills > li.active > a,
.nav-pills > li.active > a:hover {
  background-color: #f4f4f4;
  border-top-color: #3c8dbc;
  color: #444;
}

By
.nav-pills > li.active > a,
.nav-pills > li.active > a:hover,
.nav-pills > li.active > a:focus {
  background-color: #f4f4f4;
  border-top-color: #3c8dbc;
  color: #444;
}

Thank you for your work!

Hello,
Thank you for reporting this! I will get to it as soon as possible. A fix will be provided in v2.1.0.

Hello, thank you for your reactivity :)
2015-03-23 15:38 GMT+01:00 Abdullah Almsaeed<EMAIL_ADDRESS>
Hello,
Thank you for reporting this! I will get to it as soon as possible. A fix
will be provided in v2.1.0.
—
Reply to this email directly or view it on GitHub
https://github.com/almasaeed2010/AdminLTE/issues/300#issuecomment-85028439
.

--
Anthony D.

Fixed in v2.1.0

This still seems to be broken on nav-stacked nav-pills.  You can see the same as above here: https://almsaeedstudio.com/themes/AdminLTE/pages/mailbox/mailbox.html
This fixed it for me, pretty sure it's the wrong way to do it:
.nav-pills > li.active > a:focus {
    background-color: inherit !important;
    color: inherit !important;
}


nanobox start fails on macOS High Sierra 10.13.4

I downloaded nanobox using the installer, ran nanobox configure, and then tried nanobox start but received the error message below.
Nanobox Version: Nanobox Version 2.3.0-180117T2039 (4b3d14f)
VirtualBox Version: 5.2.8
Starting Nanobox :
  ! Booting VM
    Starting "nanobox"...
    (nanobox) Check network to re-create if needed...
    (nanobox) Creating a new host-only adapter produced an error: /usr/local/bin/VBoxManage hostonlyif create failed:
    (nanobox) 0%...
    (nanobox) Progress state: NS_ERROR_FAILURE
    (nanobox) VBoxManage: error: Failed to create the host-only adapter
    (nanobox) VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
    (nanobox) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
    (nanobox) VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 94 of file VBoxManageHostonly.cpp
    (nanobox)
    (nanobox) This is a known VirtualBox bug. Let's try to recover anyway...
    Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue

Troubleshooting is handled in our Slack workspace. You should have gotten an invitation when you registered for Nanobox, or you can go to slack.nanoapp.io to join us manually.