SPP-10585-add-method-spec-to-tpc

Description
The thousand pound correction method was missing the link to the method spec.
This ticket is to correct that.
Commenting and documentation changes not needed.
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Technical Enhancements

Checklist:
If any of these are not completed, please explain why in the notes.
Definition of Done
Code and merges

[x] Code to be commented on where applicable
[x] Documentation updated where required
[x] Have considered non-functional requirements such as Security, Performance, Scalability, and Fault Tolerance
[x] I have linted the code

Testing

[x] All levels of acceptance test are passing (automated, integration, manual, accessibility, etc.)
[x] I have run the behave command to check the selenium behaviour tests pass locally
[x] Acceptance criteria met

Other Checks

[x] I have performed a self-review of my own code
[x] I have checked for spelling errors
[ ] I have commented on my code, particularly in hard-to-understand areas
[x] My changes don't break anything unexpected
[x] I have checked and updated the security.txt file where required
[x] Up to date with the main branch
[ ] For a change that needs to be deployed in a release I have a commit with the fix:, feat: or BREAKING CHANGE:
tags and will copy this commit message to the squash
[ ] For a change that does not affect the deployed code I have added a commit with ci:, docs: or test:
depending upon which area of the solution was affected

Note when merging, squash commit must begin with one of the following tags:
"BREAKING CHANGE", "feat", "fix", "ci", "docs", "test"
Usage
BREAKING CHANGE: any change that breaks current functionality and may cause compatibility errors to users upgrading
E.G BREAKING CHANGE: refactored method x to take variable y as input (changed from variable z)
feat: A new feature
E.G feat: adding method x to future methods table
fix: A bug fix
E.G fix: amending page for method x to show correct release version
ci: Changes to our CI configuration files and scripts (Concourse)
docs: Documentation only changes
test: Adding missing tests or correcting existing tests

DEPLOY_URL=https://d15q12jlddbtl2.cloudfront.net/
cloudfront_id=E24466IFKO45RU

The change looks good, could we add a test to verify that methods in the Ready to Use table have user doc, source and methodological spec so that this is caught as part of CICD?

DEPLOY_URL=https://d15q12jlddbtl2.cloudfront.net/
cloudfront_id=E24466IFKO45RU

DEPLOY_URL=https://d15q12jlddbtl2.cloudfront.net/
cloudfront_id=E24466IFKO45RU

DEPLOY_URL=https://d15q12jlddbtl2.cloudfront.net/
cloudfront_id=E24466IFKO45RU

DEPLOY_URL=https://d15q12jlddbtl2.cloudfront.net/
cloudfront_id=E24466IFKO45RU

DEPLOY_URL=https://d15q12jlddbtl2.cloudfront.net/
cloudfront_id=E24466IFKO45RU


Decrypt fails when ValueRange is less than input

I'm trying to encrypt ids that are in the hundreds of millions (9 digits)  into an 8 digit integer. The encrypt function works fine. The decrypt function does not decrypt to the correct input. If I increase the ValueRange from 8 to 9 digits decrypt works.
I'm not well versed in the algorithm used so it could be that this just an inherent limitation that I'm not aware of.
Example of the issue:
$cryptomute = new Cryptomute(
    'aes-128-cbc',      // cipher
    '0123456789zxcvbn', // base key
    7                   // number of rounds
);

// doesn't work
$cryptomute->setValueRange(0, 99999999);
// does work
//$cryptomute->setValueRange(0, 999999999);

$password = '0123456789qwerty';
$iv = '0123456789abcdef';

for ($i = 100000000; $i <= 100000010; $i++) {
    $encoded = $cryptomute->encrypt($i, 10, true, $password, $iv);
    $decoded = $cryptomute->decrypt($encoded, 10, true, $password, $iv);
    echo "ID: ".$i." DECODED: ".$decoded." ENCODED: ".$encoded."<br>";
}

@acidreign This is expected behaviour. Format preserving encryption means you're performing a transformation that maps one element from given domain into another element from the same domain.
The setValueRange function is used to set the domain, eg. for 3-digit numbers you would do setValueRange(0,999).
You cannot apply a FPE transformation to a value out of domain range and expect to be able to decrypt it.
I will add a check and throw an expection if input is out of domain.

@loostro Ok, that makes sense. Thanks for the update!


dubbo3是怎么替换ReferenceConfigCache的功能的？

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Ask your question here

SimpleReferenceCache


AirTags support?

Hi does this support AirTags tracking of history?

From macOS Big Sur 11.3 and up, yes.

Hi Tim,
Just wondering will you be able to integrate this into an app? I am working on a project to build an app that has this feature so if you’re interested we can work something out.
Regards,
Sky
On 31 Jul 2023, at 11:44 AM, Tim Cinel @.***> wrote:

From macOS Big Sur 11.3 and up, yes.
—
Reply to this email directly, view it on GitHubhttps://github.com/fjxmlzn/FindMyHistory/issues/18#issuecomment-1657472763, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5SQ7LOYAJRGPCNW2OKB2J3XS4S2DANCNFSM6AAAAAA25R7DYA.
You are receiving this because you authored the thread.Message ID: @.***>

I don't see why you couldn't integrate it =)
Sorry at this point I can't offer any direct help.

I think we can close this issue.


Backport to PS 6 for Ubuntu 20.04 support

Describe the issue or request
PS is not supported on Ubuntu 20.04 and it is not clear when this will be the case
Describe your ideas for solutions
Back port scripts to PS 6 or use another language for the scripts

I would prefer a backport. We have other powershell scripts and I would like to avoid an extra tool requirement.

I would prefer a backport. We have other powershell scripts and I would like to avoid an extra tool requirement.

This is fine. Although, I do wonder the powershell's team commitment to Linux and canonical in the long term given the current lapse here.


Exceptions while trying to run Whisper ASR example

I was trying to run the Whisper ASR example.
However, I encountered some issues which I would like to point out.

After running the following lines:pip install "qai_hub_models[whisper_asr]"
python -m qai_hub_models.models.whisper_asr.demo

an exception is raised as reported in https://github.com/quic/ai-hub-models/issues/15.
Solving that as reported in the same issue and proceeding with the export commands  python -m qai_hub_models.models.whisper_asr.export raises another exception which is equivalent to the one before and that can be fixed in a similar manner inside the source code.
Then, trying to execute the command again gives another exception during the profiling step: qai_hub/client.py", line 1097, in _determine_model_type
 raise UserError(qai_hub.client.UserError: Unsupported model type. The following types are supported
     - TorchScript: Extension .pt or .pth
     - Core ML Model: Extension .mlmodel
     - Compiled Core ML Model: Extension .mlmodelc or .mlmodelc.zip
     - Tensorflow Lite: Extension .tflite
     - ONNX: Extension .onnx
     - ONNX (ORT model format): Extension .ort
     - QNN Binary: Extension .bin
     - AIMET Model: Directory ending with .aimet

Trying to skip the profiling operation  ( python -m qai_hub_models.models.whisper_asr.export --skip-profiling) can of course avoid that the previous exception is encountered, but gives another exception similar to the first one:qai_hub_models/utils/base_model.py", line 187, in sample_inputs
 inputs_dict[input_name] = [inputs_list[i].numpy()]
TypeError: can't convert cuda:0 device type tensor to numpy. Use Tensor.cpu() to copy the tensor to host memory first.

Why is it not possible to proceed with the profiling operation? The same issue is also encountered when trying to run the inference step, but I guess that these two problems are due to the same reason.
I hope that the information I reported can be helpful.

Thanks for reporting the issue. We are actively working on a fix so the next release should have it.

@shreyajn, I tested the new release 0.4.0r1 of the AI Hub and did not experience these issues anymore.
I will close this issue and open it again only if I encounter similar problems.
Thanks for the support!


DNS tunelling/exfiltration POC

The base idea is as in the picture below:

The working branch for POC is: https://github.com/criblio/appscope/tree/feat-dns-poc

The current plan:

get a working DNS tunelling scenario: currently I am testing (https://github.com/tbenbrahim/dns-tunneling-poc)
Focus on implement detection methods on scope listener as described for example here

detect malicous characters
detect mailicious size
detect DNS type ? TXT
check traffic occurence

Pass the whole payload via DNS event
TODO:
Get a test domain to provide more reliable example.

The initial changes supports detecting mailicious size of DNS domain and I am able to send notificatio to slack channel
TODO:
Consider extending dns request and response with dns type information.

The blog post proposal about it is presented in #1606


Transaction Verification and Storage

Description

Add L1Handler and Deploy Account Transactions
Add L1Handler and Deploy Account Hash calculations
Verify all transaction hashes based on the following rules:

Deploy: no verification since it will be deprecated
Declare: verify v1 but not v0
Invoke: verify v1 but not v0
Deploy Account: verify v1 (there is no v0)
L1 Hander: verify v0 (with some caveats see comments)

Some sanity checks for Transactions and Transaction Receipts
Add Transaction and Receipt Storage
Store Block Headers, Transaction and Receipts separately

Types of changes

New feature (non-breaking change which adds functionality)

Testing
Requires testing: Yes
Did you write tests??: Yes

@omerfirmak i have made all the changes. Please have another look.

@omerfirmak @jelilat @joshklop pr is ready for review. The easiest way to review is by going through each commit individually.


Recent build changes break usage of User Package Registry

Hi,
in my toy project I import EnTT with
find_package(EnTT REQUIRED CONFIG)
target_link_libraries(${PROJECT_NAME} PRIVATE EnTT::EnTT)

and the help of the User Package Registry. This fails since 23e839b40e23f7aaaad4aefb5cce194e78d16ff6 with:
CMake Error at /path/to/entt/build/EnTTConfig.cmake:23 (message):
  File or directory /home/user/include referenced by variable
  ENTT_INCLUDE_DIRS does not exist !
Call Stack (most recent call first):
  /path/to/entt/build/EnTTConfig.cmake:39 (set_and_check)
  src/CMakeLists.txt:9 (find_package)

dropping the offending set_and_check line from cmake/in/EnTTConfig.cmake.in solves that as nothing seems to need ENTT_INCLUDE_DIRS after all.
Trying again gives me the next error:
CMake Error at /path/to/entt/build/EnTTConfig.cmake:40 (include):
  include could not find load file:

    /path/to/entt/build/EnTTTargets.cmake
Call Stack (most recent call first):
  src/CMakeLists.txt:9 (find_package)

This seems to be fixed by adding the following stanza in CMakeLists.txt:
export(
    EXPORT EnTTTargets
    FILE "${CMAKE_CURRENT_BINARY_DIR}/EnTTTargets.cmake"
    NAMESPACE EnTT::
)

which I adapted from the example given in the cmake documentation.
And with that my project compiles again. :tada:
I have quite literally no idea what I am doing though, cmake is akin to witchcraft for me.

I have quite literally no idea what I am doing though, cmake is akin to witchcraft for me.

Yeah, removing a line here and adding a duplicate of an export doesn't look like the right solution actually. :smile:
Can you provide a minimal example to reproduce the error? This way I can look directly into the issue.
Thank you.

I've updated the build system and tested it. Everything works as expected.
May I ask you to test branch experimental and report your errors if any?
Thanks.

Thanks for taking a look, but the issue remains with the exact same remedies – which isn't too surprising as I am not make install so PACKAGE_CMAKE_INSTALL_INCLUDEDIR probably doesn't contain something sensible (and I consider a may or may not existing include/ dir in my home directory as not sensible). And the export(EXPORT … is what is suggested in the example in cmake docs, so while I have no idea I have some hope that they know what they are doing.
As you asked for an example (assuming a linux machine), here we go:
git clone 'https://github.com/skypjack/entt'
cd entt && mkdir build && cd build
cmake -DUSE_LIBCPP=OFF -DBUILD_DOCS=OFF -DBUILD_TESTING=OFF -DFIND_GTEST_PACKAGE=ON ..
make
mkdir -p ~/.cmake/packages/EnTT
echo "$(pwd)" > ~/.cmake/packages/EnTT/buildpath
mkdir /tmp/toyproject && cd /tmp/toyproject
cat > CMakeLists.txt <<EOF
cmake_minimum_required(VERSION 3.4.0)
project(toyproject VERSION 0.0.0 LANGUAGES CXX)
find_package(EnTT REQUIRED CONFIG)
add_executable(${PROJECT_NAME} main.cc)
target_link_libraries(${PROJECT_NAME} PRIVATE EnTT::EnTT)
EOF
cat > main.cc <<EOF
#include <entt/entity/registry.hpp>
int main() {
        return static_cast<int>(entt::registry{}.create());
}
EOF
mkdir build && cd build && cmake ..

(typos I made are all copyright me, everything else is free to use elsewhere :wink: )

I am not make install

Ah.

so PACKAGE_CMAKE_INSTALL_INCLUDEDIR probably doesn't contain something sensible

I must admit that I haven't even taken in consideration the case in which the library isn't properly installed, so yeah, it may be that this variable doesn't contain anything sensible actually.

so while I have no idea I have some hope that they know what they are doing

The problem with their examples is that they are fragmented and they use a feature here, a fixed variable there, and so on. They are a good starting point but hardly the right solution for all cases.

As you asked for an example (assuming a linux machine), here we go

That's good! I didn't get what you were doing and this example will help to wrap my head around your problem now that I got it.
Thank you very much for spending your time with this. Really appreciated. Let's reopen the issue and address also your case. :+1:

Aaaaaaaaand... I apologize.
I should have read more carefully your first message that seemed to me in conflict with the current install process.
I noticed... kind of... 10 minutes ago that you weren't adding a duplicate for the export clause. Instead, you were adding an export directive for the build tree.
So I picked out the commit in which I reviewed that part and realized that I removed too much. :smile:
My fault and really thanks for insisting on this issue.
I'm cleaning up anyway the previous solution because another comment of yours triggered me:

nothing seems to need ENTT_INCLUDE_DIRS after all

This isn't due to the fact that nothing needs this variable. We are exporting stuff, so it goes without saying that nothing in EnTT needs it.
Instead, the key part is that we are already exporting targets as a whole and you can link to include directories by linking to the targets rather than by using this variable. That is, this variable quicly becomes obsolete and is mainly targeted to a non-modern cmake model that EnTT isn't supporting at all.
Good catch and thank you again for making me reopen the issue and investigate further.
You contributed to make EnTT a better place for cmake users. :wink: :heart:

May I ask you to test branch experimental?

Can confirm that the experimental branch works for me™. :+1:

Thanks for testing and thank you again for insisting. :+1: :wink:


Cannot add new SSH connections

Version: 1.0.108
Platform: linux 5.4.39-1-MANJARO
Plugins: clickable-links, quick-cmds, scrollbar
I've entered all the details for the new SSH connection, click Save does nothing.
From DevTools:
 /opt/Terminus/resources/app.asar/node_modules/@angular/core/bundles/core.umd.js:4265 ERROR TypeError: Cannot convert undefined or null to object
    at Function.entries (<anonymous>)
    at EditConnectionModalComponent.save (editConnectionModal.component.ts:99)
    at Object.eval [as handleEvent] (EditConnectionModalComponent.ngfactory.js:1403)
    at Object.handleEvent (/opt/Terminus/resources/app.asar/node_modules/@angular/core/bundles/core.umd.js:31448)
    at Object.handleEvent (/opt/Terminus/resources/app.asar/node_modules/@angular/core/bundles/core.umd.js:32001)
    at dispatchEvent (/opt/Terminus/resources/app.asar/node_modules/@angular/core/bundles/core.umd.js:21743)
    at /opt/Terminus/resources/app.asar/node_modules/@angular/core/bundles/core.umd.js:30652
    at HTMLButtonElement.<anonymous> (/opt/Terminus/resources/app.asar/node_modules/@angular/platform-browser/bundles/platform-browser.umd.js:815)
    at ZoneDelegate.invokeTask (/opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:421)
    at Object.onInvokeTask (/opt/Terminus/resources/app.asar/node_modules/@angular/core/bundles/core.umd.js:28321)
    at ZoneDelegate.invokeTask (/opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:420)
    at Zone.runTask (/opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:188)
    at ZoneTask.invokeTask [as invoke] (/opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:503)
    at invokeTask (/opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:1671)
    at HTMLButtonElement.globalZoneAwareCallback (/opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:1697)
    at HTMLButtonElement.sentryWrapped (/opt/Terminus/resources/app.asar/dist/sentry.js:1882)
defaultErrorLogger @ /opt/Terminus/resources/app.asar/node_modules/@angular/core/bundles/core.umd.js:4265
ErrorHandler.handleError @ /opt/Terminus/resources/app.asar/node_modules/@angular/core/bundles/core.umd.js:4313
dispatchEvent @ /opt/Terminus/resources/app.asar/node_modules/@angular/core/bundles/core.umd.js:21747
(anonymous) @ /opt/Terminus/resources/app.asar/node_modules/@angular/core/bundles/core.umd.js:30652
(anonymous) @ /opt/Terminus/resources/app.asar/node_modules/@angular/platform-browser/bundles/platform-browser.umd.js:815
ZoneDelegate.invokeTask @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:421
onInvokeTask @ /opt/Terminus/resources/app.asar/node_modules/@angular/core/bundles/core.umd.js:28321
ZoneDelegate.invokeTask @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:420
Zone.runTask @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:188
ZoneTask.invokeTask @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:503
invokeTask @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:1671
globalZoneAwareCallback @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:1697
sentryWrapped @ /opt/Terminus/resources/app.asar/dist/sentry.js:1882

Same here bug in my case :
Version: 1.0.111
Platform: openSUSE Leap 15.1
Plugins: only from core, none added

Yes, the same error for me:
Version: 1.0.111
OS: Kubuntu 20.04
Plugins: Default

Okay, I see what the problem is with SSH options. When you click on SSH in the menu, the following error appears in the DevTools:
The name org.freedesktop.secrets was not provided by any .service files
This error means that you need to have the gnome-keyring package installed.
After installing it, it worked fine:

So there's no option to use KWallet or whatever the KDE equivalent is called?

KWallet doesn't implement the Freedesktop Secret Service, but there's ksecretsservice, which isn't fully stable yet AFAIK

Yes, you're right, I hope I'll still remember this bug when it will be completed, thank you very much!

No problem anymore on alpha 112. Fixed from my side


Using the original publisher's name in the identifier for a custom build shoud be forbidden unless it is admitted

It's normal for people to make and release custom builds for the projects that didn't provide any pre-built binary or pre-built Windows binary (i.e., only the source code or ELF binaries are provided, which is common in Linux-based projects). However, these customs builds should not use the original author's name in the package identifiers if they haven't been admitted by the author like being listed in the project website or README. Otherwise there might be some security concerns.
This came into my attention when I was handling the package AdrianThurston.Ragel (added in #153218), which is actually the PolarGoose's custom build of Adrian's Ragel, while I couldn't find any places where the author mentioned this build. I'm not suspecting PolarGoose, but moderates should pay attention to such issues.

ℹ Suggestions
Third-party builds should be identified with the "builder" instead of "original author". In the above case, the package identifier should be moved to PolarGoose.Ragel.

This appears to be too esoteric to be detected by deterministic automation.


Adding HashAnalyzers for MD5, SHA, and bcrypt hashes.

This PR addresses issue #15.
This PR should be merged before my other MR for minimal merge conflict resolution.

More Analyzers. Well done :)


Provision cleanup failed

Description
Cleanup of failed provision fails:
# oneprovision create --verbose packet2hosts.yaml
2019-04-15 13:37:53 INFO  : Creating provision objects
WARNING: This operation can take tens of minutes. Please be patient.
2019-04-15 13:37:53 INFO  : Deploying
2019-04-15 13:39:51 INFO  : Monitoring hosts
2019-04-15 13:39:59 INFO  : Checking working SSH connection
2019-04-15 13:40:01 INFO  : Configuring hosts
2019-04-15 13:44:33 WARN  : Command FAILED (code=2): ANSIBLE_CONFIG=/tmp/d20190415-23694-1nktxwh/ansible.cfg ansible-playbook --ssh-common-args='-o UserKnownHostsFile=/dev/null' -i /tmp/d20190415-23694-1nktxwh/inventory -i /usr/share/one/oneprovision/ansible/inventories/static_vxlan/ /usr/share/one/oneprovision/ansible/static_vxlan.yml
ERROR: Failed to configure hosts
...
original message: no test named 'in'
1. quit
2. retry
3. skip
4. cleanup
Choose failover method:
4
/usr/lib/one/oneprovision/lib/provision.rb:67:in `delete': wrong number of arguments (0 for 2) (ArgumentError)
	from /usr/lib/one/oneprovision/lib/provision.rb:226:in `rescue in create'
	from /usr/lib/one/oneprovision/lib/provision.rb:172:in `create'
	from /usr/lib/one/ruby/cli/one_helper/oneprovision_helper.rb:85:in `create'
	from /usr/bin/oneprovision:210:in `block (2 levels) in <main>'
	from /usr/lib/one/ruby/cli/command_parser.rb:470:in `call'
	from /usr/lib/one/ruby/cli/command_parser.rb:470:in `run'
	from /usr/lib/one/ruby/cli/command_parser.rb:84:in `initialize'
	from /usr/bin/oneprovision:56:in `new'
	from /usr/bin/oneprovision:56:in `<main>'

(note: the problem here is not the failed Ansible, but failed failover cleanup after)
Details

Affected Component: Provision
Version: 5.8.1

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

PRs to merge:
OpenNebula/one: https://github.com/OpenNebula/one/pull/3238
OpenNebula/docs: https://github.com/OpenNebula/docs/pull/592


Bug in get_even_track_cascade_indicies

Contrary to the other indicies functions, the output of data.utils.get_even_track_cascade_indicies is not shuffled properly.
Most likely, the events.sample(frac = 1) in line 143 is meant to shuffle the data, but does nothing instead.
Reproducible example in the attached .py-file which produces the image also attached, showing the function in question alongside two working functions.
Tagging @RasmusOrsoe who I believe has written the function

import matplotlib.pyplot as plt
from graphnet.data.utils import get_even_track_cascade_indicies, get_desired_event_numbers, get_equal_proportion_neutrino_indices
db = 'datafromrasmus/dev_level7_muon_nu_classification_pass2_fixedRetro_v4/data/dev_level7_muon_nu_classification_pass2_fixedRetro_v4.db'
# Load different selections
train_selection_TC, _ = get_even_track_cascade_indicies(db)
train_selection_nu, _ = get_equal_proportion_neutrino_indices(db)
train_selection_desired = get_desired_event_numbers(
    db_path=db,
   desired_size=1_000_000,
   fraction_muon=.25,
    fraction_nu_mu=.25,
    fraction_nu_e=.25,
    fraction_nu_tau=.25
)
selections = [train_selection_TC, train_selection_nu, train_selection_desired]
names = ['get_even_track_cascade_indicies', 'get_equal_proportion_neutrino_indices', 'get_desired_event_numbers']
# Plot event nos as a function of index
fig, axs = plt.subplots(1, 3, figsize=(20,7))
for i in range(3):
    ax = axs[i]
    ax.scatter(range(len(selections[i])), selections[i], s=.1)
    ax.set_title(names[i])
    ax.set_xlabel('Index')
axs[0].set_ylabel('Event no')
plt.suptitle('Event nos as a function of their order of appearance in the ouput list from each selection function. Far left is the one with the bug')
plt.savefig('indices_test')


⚠ Site ANTS has degraded performance

In 0d9e808, Site ANTS (https://ants.gouv.fr) experienced degraded performance:

HTTP code: 200
Response time: 4707 ms

Resolved: Site ANTS performance has improved in dd9876a.


Not well formed xml related error

Hi there,
I'm still having this error every time I launch SublimeText.
Traceback (most recent call last):
  File "~/.config/sublime-text-3/Packages/SublimeLinter/lint/util.py", line 264, in generate_color_scheme_async
    plist = ElementTree.XML(scheme_text)
  File "./python3.3/xml/etree/ElementTree.py", line 1356, in XML
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 8, column 2
Traceback (most recent call last):
  File "~/.config/sublime-text-3/Packages/SublimeLinter/lint/util.py", line 264, in generate_color_scheme_async
    plist = ElementTree.XML(scheme_text)
  File "./python3.3/xml/etree/ElementTree.py", line 1356, in XML
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 8, column 2

Which information can I provide to help?

It was related to my not well formed color scheme xml. Sorry about that!


Hunks not working with GitGutter

The hunks extension doesn't seem to be working with the latest version of GitGutter (anymore). I tested it with airblade/vim-gitgutter@339f8ba079ed7d465ca442c9032b36bc56c21f61 and the second section in the airline was empty even though the GitGutter diff signs next to the line numbers were visible.
From what I can tell, the extension uses the GitGutterGetHunkSummary command [1] which I think doesn't exist anymore. When I type :GitGutter<TAB>, the auto completion doesn't suggest that command.
Works fine with Signify.
[1] https://github.com/bling/vim-airline/blob/master/autoload/airline/extensions/hunks.vim#L52

Never mind, it works for me now. I'm not exactly sure why...


[5.7][CSClosure] Fix handling of property wrapped pattern bindings

Cherry-pick of https://github.com/apple/swift/pull/59300

Property wrappers trigger initializer synthesis. Synthesized
initializers should not be re-typechecked when encountered e.g.
while re-solving closure with a different contextual type.
Resolves: https://github.com/apple/swift/issues/59294
Resolves: rdar://94506352
(cherry picked from commit 066bbd18eb6cfbe081aafd621c84c1b1ab403708)

@swift-ci please test


Config Context not present in dynamic-groups/members API endpoint

Environment

Nautobot version (Docker tag too if applicable): 1.4.2-py3.8
Python version:
Database platform, version:
Middleware(s):

Steps to Reproduce

Make an API call to https://host/api/extras/dynamic-groups/c500ffdb-27a6-4721-9627-2f58812f87c8/members

Expected Behavior
[...]
            "local_context_schema": null,
            "local_context_data": null,
            "config_context": {
                "command_list": [
                    {
                        "command": "show ip interface brief",
                        "template": "cisco_ios_show_ip_interface_brief.textfsm",
                        "command_alias": "show_ip_int_br",
                        "template_type": "textfsm"
                    }
                ]
            },
            "created": "2022-10-27",
[...]

Observed Behavior
[...]
            "local_context_schema": null,
            "local_context_data": null,
            "created": "2022-10-27",
[...]

We'd need to make the dynamic-groups/<group>/members/ endpoint understand the ?include=config_context parameter, but only for groups of devices or VMs. Not sure it's worth the trouble.


Fix for Yosemite

Need to add a NULL for execv argument for Yosemite. Otherwise a "Bad address" error is raised.

Thanks for the patch! :smile:


Fix error log spam by not sendToAll on client side

long running instance can have several dozen megabytes worth of log. This is the new !a2, in a sense.

Why the first check is on the server and the second on the client?

fixed


Removed check if /mattermost/config/config.json already exists before…

… using config.template and environment values to create new config.json.
When Dockerfile install mattermost it will always write /mattermost/config/config.json file, therefore using environment values to create new config.json never happens if there is this file check.
Also if one whishes to restart docker with new database value there is good reason to always create new config file from environment values.

When Dockerfile install mattermost it will always write /mattermost/config/config.json file, therefore using environment values to create new config.json never happens if there is this file check.

No, if in the host ./volumes/app/mattermost/config/config.json exists mattermost reuse it and that is my intention.

Ok. So app-docker only works when attaching volume when running it? Isn't that bit complicated? How about just delete extra /mattermost/config/config.json in Dockerfile after extracting .tar.gz? So intended usage with volumes still works, but it would be possible to run without.

@Tobatus Good point. I'll try to fix it.


use http rather than https for ubuntu cloud images.

using http by default means benefit of caching proxies.
Also here, remove FIXME comment that is now fixed.

This pull request didn't trigger Jenkins as its author isn't in the whitelist.

LGTM, travis is whining because we need a Signed-off-by (git commit --amend -s should get you there).


Treat 'package' as a buildy action. [phab:D163]

Created by zarko at 2015-04-02 22:25:39:

schroederc accepted this revision at 2015-04-02 22:25:57

zarko closed via commit 59938dc6e67f6f3174f437b75bde70b37b9cb0d8 at 2015-04-02 22:28:14


Run offline

Can we run this offline with downloades models?

Yes if you have downloaded the model, it uses the cached model

Yes if you have downloaded the model, it uses the cached model

I mean with models downloaded for other projects.


Additional spot instance types disappear on cluster create

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

In Rancher create an EKS cluster.
During node group creation, enable Request Spot Instances
Click Add Instance Type once.
Create cluster.

Result:
Additional spot instance types disappear on cluster create:

As a result, cluster creation errors out with Nodegroup [aaron-test-spot-ng] in cluster [c-qk2pj]: spotInstanceTypes must be specified when requesting spot instances
Other details that may be helpful:
To get past this error during cluster creation, the user must select a different instance type first (then may switch back to the default instance type).

If the user tries to use the default instance type, they will hit this error.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): rancher\rancher:master-head version 990c1ad and rancher\rancher:v2.5-head version 8b65a6a
Installation option (single install/HA): Single install

The bug fix is verified with Rancher server rancher\rancher:master-head version d7203b4 and rancher\rancher:v2.5-head version 05fbcbb
Additional spot instance type does not disappear and cluster creation does not go into error state.


sql/sqlite: bug fixes and migration support

Looks great, just missing the ent integration tests, is that for another PR?

Yes.


Integration causes Home Assistant to lock up for 30-40 seconds when generating map (vacuum running)

Describe the bug
When using v2.0.0b16 on Home Assistant 2024.8.1 the integration causes Home Assistant to lock up and become unresponsive for a while (30-40 seconds) before coming back again. This seems consistent to when the map updates, it does only happen when the vacuum is moving and the map is updating, not when it is docked.
Disabling the integration gives me no issues with slowdowns on Home Assistant.
I have tried redownloading and installing the integration again. Restarted Home Assistant through UI and the Docker container.
I have tried with the low resolution map without any change.
Running Home Assistant in docker on a dedicated NAS with i5-4670K and 24GB RAM.
To Reproduce
Activate Dreame integration v2.0.0b16 and start cleaning with vacuum. When the map is being created Home Assistant slows down and locks up for about 30-40 seconds before being responsive again until the next time the map updates.
Expected behavior
The integration to not cause Home Assistant to lock up.
Debug log
home-assistant_dreame_vacuum_2024-08-16T09-44-19.366Z.log
Additional Information (please complete the following information)

Integration version: v2.0.0b16
Model Name [e.g. dreame.vacuum.p2028]: dreame.vacuum.r2228o
Firmware Version [e.g. 1156]: 4.3.9_3204
Home Assistant Version: 2024.8.1
Configuration Type [With or without map support]: Map support with Xiaomi Vacuum Map Card
Errors or warnings shown in the HA logs (if applicable):

Your 11 year old CPU cannot keep up with the rendering. If you think about it, the CPU you are using is actually older than Home Assistant itself.

I have had no issues at all with previous versions of this integration. No performance issues at all.

It may be because of a map data corruption in a way that the integration does not expect. That bug will be very hard to find and fix so if that was the case, restoring the map to a previous state should resolve your issue.

How do I restore the map?
I have removed my vacuum completely, and added it again. Same thing happened. I will try to downgrade to an earlier beta to check.
When looking at my servers CPU usage I can see that one of the CPU cores is at 99-100% when this occurs. However the overall load is about 20-30% on the whole CPU. Is it possible to use more cores, or is this a limitation in Home Assistant with Docker maybe?
Weird that this started happening, as I have done no changes to my server, not running anything else at the moment.
Would it be possible to render an even lower quality map that is easier on the CPU?

In this comment you are talking about a RPi 3 being able to render the map:
https://github.com/Tasshack/dreame-vacuum/issues/52#issuecomment-1692143931
Surely my old i5 is more powerful than that?

How do I restore the map?

Check the Map Management from the app.

Is it possible to use more cores, or is this a limitation in Home Assistant with Docker maybe?

I am not familiar with the HA Docker setup.

Would it be possible to render an even lower quality map that is easier on the CPU?

Normally Low resolution map option should fix your issue if not that means it is not the rendering that causes the issue. You can confirm this by disabling the Current Map and Saved Map entities from HA manualy. If you disable the camera entities from HA, there won't be any rendering at all.

I see no difference in map quality when enabling Low resolution map, is there any way to confirm this setting really takes action?

Is there a good option for removing the map, but still get some information of the progress. Like how far it has gotten (percentage), or current location (room name)?

I have 800mb mem free , when i start the  integration it fills it and the system hangs.
I had the SSH open and was looking at memory usage. As soon as the integration starts the memory starts filling.
Some  seconds later the connection was lost.
I see you saying enable Low resolution map.
What is "Low resolution map" where and how can i enable it?

Thanks for your reply.
I installed your latest beta and chose low resolution map.
It works now and i can see the map.
But guess what!
The map it gets from the vacuum includes a part that doesn't exist. it is 4x larger.
So no wonder i suddenly started running out of memory.
I think for some people It may be as simple as to reset your map in the xiaomi/dreame app.

@somenewaccountthen Normally integration should crop empty pixels from the map but I am not sure what is going on. Can you share a debug log so I can reproduce and fix it?

Not really i have no log, i don't think it's relevant either.
The map was just bigger (4x) than the house.
This is the bad map.

I rolled back to an older map in the Xiaomi app and that works fine.
That's all it was in the end.

Anyway.. crisis averted.
And me and my dad are now on the v2 beta.
On his pi 2G he now has 30% mem free again.
On mine Mem is not an issue :P
If you tell me where the log is i can send it.
But like i said i think the image was just too big for his pi to handle.
Nothing to do with your code.


How to use authentication passing credentials using code.

Hi guy,
I see HERE
// Imports the Google Cloud client library.
const {Storage} = require('@google-cloud/storage');

// Instantiates a client. Explicitly use service account credentials by
// specifying the private key file. All clients in google-cloud-node have this
// helper, see https://github.com/GoogleCloudPlatform/google-cloud-node/blob/master/docs/authentication.md
// const projectId = 'project-id'
// const keyFilename = '/path/to/keyfile.json'
const storage = new Storage({projectId, keyFilename});

// Makes an authenticated API request.
async function listBuckets() {
  try {
    const [buckets] = await storage.getBuckets();

    console.log('Buckets:');
    buckets.forEach((bucket) => {
      console.log(bucket.name);
    });
  } catch (err) {
    console.error('ERROR:', err);
  }
}
listBuckets();

With CloudBuildClient Document

When I use this for my code:

I has error

But when i use google-auth-library => It's work.

Please help!!!

@pvhieuit I believe you should be able to pass in an auth instance like this:
const authClient = auth.fromJSON(keys)
const client = new CloudBuild({
  auth: authClient
})

☝ does this approach work for you?

@bcoe thank you for help, but it not working.

Where are you running the code?  Depending on the environment, you can use the default authorization of the caller.  If you don't specify auth, it uses the default.  For instance, this works for me when I'm running locally:
  // Imports the Google Cloud client library
  const {CloudBuildClient} = require('@google-cloud/cloudbuild');

  // Creates a client
  const cb = new CloudBuildClient();

  const request = {
    projectId
  }

  const result = await cb.listBuildTriggers(request)
  console.info(result)

If this doesn't work, you can try running gcloud auth application-default login (info here) and then try again.
If you want to explicitly pass credentials through, you can use a service account key like this:
/  // Imports the Google Cloud client library
const {CloudBuildClient} = require('@google-cloud/cloudbuild');

client_options = {"keyFilename": "cloudbuildkey.json"}

// Creates a client
const cb = new CloudBuildClient(client_options)

const request = {
  projectId
}

const result = await cb.listBuildTriggers(request)
console.info(result)

Make sure your service account has permission to use the Cloud Build API.  I gave mine the Cloud Build Service Agent role.
You can see more about authentication options here.


all functionality back on current master?

I think we got this working again, but wanted to make an official issue in case that is not the case!

Yeah, I think you're talking about what I fixed with #12. If not let's figure it out and fix it!


More documentation with samples in typescript

There's this walkthrough but it's using java as the language, and it's not very easy to understand.
From the documentation perspective, I don't understand how to call dynamodb from the handlers for example. It looks like I need to use the SessionProxy, but it's not documented how to get a hold of dynamodb aws client.
In the init example:
// Example:
        try {
            if (session instanceof SessionProxy) {
                const client = session.client('S3');
            }

Where's the documentation of which string should I pass in the .client([string]) to get dynamodb, stepfunction (or others) clients?

Even after I run npm install to install the dependencies, VSCode still does not find @amazon-web-services-cloudformation/cloudformation-cli-typescript-lib

Also, do I need to implement all "create, update, list, read..." operations? I was looking for to implement only create, update and delete.

This will be out of order but for

Also, do I need to implement all "create, update, list, read..." operations? I was looking for to implement only create, update and delete.

The minimum needed would be "create", "read", and "delete".
https://docs.aws.amazon.com/cloudformation-cli/latest/userguide/resource-type-develop.html#resource-type-develop-implement-handlers

Even after I run npm install to install the dependencies, VSCode still does not find @amazon-web-services-cloudformation/cloudformation-cli-typescript-lib

Not sure on the VSCode error but is your node modules directory included in your tsconfig.json configuration?

Where's the documentation of which string should I pass in the .client([string]) to get dynamodb, stepfunction (or others) clients?

I'm deeper into the python stack but services are extended from the SDKs.  In python this would be the reference I would use.
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/core/session.html
Hopefully that helps?

I would like to also add a request for additional documentation. This plugin deserves its own document for how to write handlers with progress chaining and stabilization. The Java docs are not very useful here.


upload to testflight failed

New Issue Checklist

[x] Updated fastlane to the latest version
[ ] I read the Contribution Guidelines
[ ] I read docs.fastlane.tools
[ ] I searched for existing GitHub issues

Issue Description

Complete output when running fastlane, including the stack trace and command used

[INSERT OUTPUT HERE]

Environment

[INSERT OUTPUT HERE]

Please open a new issue where you include the information the bug report template asks for, otherwise there is no way we can understand the problem and possibly help you.


Update portaudio::pa::is_format_supported to use optional input/output stream parameters.

This adds support for testing whether a non-duplex format is supported.
Not sure if InvalidDevice is the best error for the None/None case.
Also -- not sure if you have a column width limit. I saw up to 100 elsewhere.

Not sure if InvalidDevice is the best error for the None/None case.

Hm, it looks like InvalidDevice is what PortAudio itself returns in this case.

Nice, thanks @rryan!

Publish to crates.io as 0.4.16


Add support for HDF5 transient types

These are compound or enum datatypes stored directly in the dataset itself, and so aren't read as standalone objects during the initial metadata gathering when the file is opened
Closes #2651
Fixes #267
I've added a fairly simple test, maybe it should be expanded to include transient types on attributes, and other types (like enums, as in #267)
~This change unfortunately also causes nc_test4_tst_h_refs to fail, and I've not managed to work out why.~ Fixed

You could use your hdf5 test program to create the test file and then see what happens when
netcdf-java tries to open it.

@ZedThree - The netCDF-Java library uses its all Java implementation to read nc-4/HDF5 files. Writing, on the other hand, is done through the netCDF-C library.

Right, but it must be able to read the file created by your hdf5 program.

I don't have a Java development environment set up, but I was able to use the ToolsUI utility to view the file created by this test, and it was able to view the presence of the variables at least:

Try the ncdump tab also on toolsui

I tried the ncdump tab on a few files, and it didn't work for any of them. It doesn't produce any error messages, so I can't debug it

Is it possible for someone with access to re-run the nc-cmake-tests-oneoff-parallel (1.12.2) build to see if it is an intermittent failure, please?

Oh, I've just seen #2555  and #2558, could the test failure be related to them?

Re-running jobs.  I'll echo what @ethanrd and @DennisHeimbigner mentioned above; if netCDF-Java can read these out of the box, great, if not, we'll need to have that broader conversation.  But first things first, I've started the tests.  Thanks!

Hello, is there anything I can do to help move this along? It would be a very useful feature to enable greater compatibility between different netCDF implementations: netCDF-Java and h5netcdf can both already read these kinds of files.

This PR needs to be reversed. It is creating types with empty names and that violates the netcdf-4
specification. Plus it will cause various programs to crash.

It passed all the tests; do we need to update our test suite in a way that will test for the failures you're observing?

The test is bogus. It never checks for the type name.

It is creating types with empty names and that violates the netcdf-4 specification.

This is absolutely not the case, it only adds the ability to read such types. From my comment above:

There's also no issues of backwards compatibility that I can see -- no previously valid files will become invalid. It also only affects reading, so newer versions of netCDF won't make possibly invalid files for older versions.
More files written by other tools (such as h5netcdf with invalid_netcdf=True) would be able to be read using this feature.

NetCDF-Java can already read such types, so this only brings netCDF-C functionality in line with the Java library.
It's also not clear that it is against the spec. Is there a more formal spec than this page in the docs? In relation to user-defined types, it says:

Each user-defined data type in an HDF5 file exactly corresponds to a user-defined data type in the netCDF-4 file. Only base data types which correspond to netCDF-4 data types may be used.

I don't see the issue here.

Plus it will cause various programs to crash.

If you can provide a minimal reproducer, I will be happy to fix any bugs I've introduced and expand the test suite. As it is, the entire existing test suite passes along with the additional tests I wrote. As you requested, I also verified that netCDF-Java can already correctly read files with unnamed types in them.

This is absolutely not the case, it only adds the ability to read such types. From my comment above:
Modify your test program to print the type name.

NetCDF-Java can already read such types, so this only brings netCDF-C functionality in line with the Java library.

netcdf-java assigns names to those types. your code does not.

As it is, the entire existing test suite passes along with the additional tests I wrote.

But no other tests operate on a transient type. The only test that does is your test case.

The spec requires type names to be unique within a group. Your code produces types all with the same empty name.

The right thing to do here is to make sure that these transient types have proper names.
So, your suggestion above about using "var_XXX" seems a good starting point.
We have a precedent WRT anonymous dimensions in DAP2. I would suggest that we add a counter that is incremented whenever a transient type is created. Then we create the name of the type as, say, "anonamousN".
Also, it is possible to encounter transient types associated with attributes?


StringToArrayArgumentProcessRector breaks Process instance method calls

This is a failing test to show the issue. Basically I think it is overzealous with the instance methods of the Process class.
The Process class API for setWorkingDirectory is
public function setWorkingDirectory(string $cwd)

The StringToArrayArgumentProcessRector changes the proper string argument to an array argument when it should not.

I cherry-picked your commit at PR https://github.com/rectorphp/rector-symfony/pull/70


Volunteer call to action

This branch introduces a single change:

I've added a call to action paragraph to the top of the page (at the suggestion of @tomviner)

+1


Allow disabling automatic MVC reference

Less of a hammer than https://github.com/aspnet/AspNetCore/pull/8147/files

Looks like the Mvc reference is no longer added in most samples ☹


Pin all dependencies versions

Pin all dependencies versions
Signed-off-by: Mohab Usama<EMAIL_ADDRESS>

:+1:

👍


enhance the warning when not explicitly declare the variable

fix: #4305
No idea how to add test,  because it will broken other test. So I add !__TEST__ to avoid test fail.😢
You can clone this project: https://github.com/caozhong1996/v3-warn-demo.
I added those code in vue.js:
// line 7468
} else if (
  !(key[0] === '$' || key[0] === '_')
) {
  warn$1(
    `Property ${JSON.stringify(key)} was accessed during render ` +
      `but is not defined on instance.`
  )
}

No idea how to add test, because it will broken other test

Could you please try to add an e2e test case?

No idea how to add test, because it will broken other test

Could you please try to add an e2e test case?

Done, I almost forgot about this pr, I'm glad to see that you're still persisting in maintaining vue-next. It has been a really long time, salute🫡 @edison1105


No CUDA

Hi, just wondering if it is possible to build without CUDA? I don't have a NVIDIA GPU so I want to do inference with CPU

I've built it, but now have this error when doing inference:
Run once on empty image
----------New Frame----------
pre-process takes : 22 ms
inference takes : 366 ms
terminate called after throwing an instance of 'c10::Error'
what():  isTuple() INTERNAL ASSERT FAILED at "/home/derek/Documents/libtorch-yolov5-master/libtorch/include/ATen/core/ivalue_inl.h":931, please report a bug to PyTorch. Expected Tuple but got GenericList
Exception raised from toTuple at /home/derek/Documents/libtorch-yolov5-master/libtorch/include/ATen/core/ivalue_inl.h:931 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::__cxx11::basic_string<char, std::char_traits, std::allocator >) + 0x69 (0x7fd5c5523b89 in /home/derek/Documents/libtorch-yolov5-master/libtorch/lib/libc10.so)
frame #1: c10::IValue::toTuple() const & + 0xf3 (0x560cfd15ba2f in ./libtorch-yolov5)
frame #2:  + 0x18677 (0x560cfd154677 in ./libtorch-yolov5)
frame #3:  + 0x36a4b (0x560cfd172a4b in ./libtorch-yolov5)
frame #4: __libc_start_main + 0xf3 (0x7fd5b38440b3 in /lib/x86_64-linux-gnu/libc.so.6)
frame #5:  + 0x17bde (0x560cfd153bde in ./libtorch-yolov5)
Aborted (core dumped)
Any idea what is wrong?


Default module store sidebar selectors to none selected

There's no easy way if you want to quickly disable your theme to clear the categories in the store, maybe there should be a button for that?

Done in last commit.

Done in last commit.


Colours on the UMAP are unclear.

The colours on the UMAPs and TSNE are unclear/too similar.

I realise @parkyed you have done this.
I will close this issue when we have merged the pull request.

[ECP 3.06.24 - swapped tab20 for accent, as tab20 colours are in similar pairs]
May need to remove tab20 or change the order of colour maps further if the issue re-occurs.


Split extension for each platform

VSCode added support for platform specific extensions: https://code.visualstudio.com/api/working-with-extensions/publishing-extension#platformspecific-extensions
This will allow to have separate extension files including only the bindings for the respective platform.

With the update to SerialPort 10 they now provide NAPI bindings for different platforms, so I do not see any benefit for making this split. Closing.


Can't add roles to users?

I have a slash command that I'm attempting to assign the user the role but there doesn't seem like a clear way of doing that. Am I missing something or is this not implemented?

everything is implemented, did you look at cluster::guild_member_add_role?
https://dpp.dev/classdpp_1_1cluster.html#aeffb7f4f32ca342886a79692ed8fb416

The issues section is probably not the best place for obtaining library help. For questions such as this it is probably better if you use the official discord server at https://discord.gg/dpp


swagger generate spec -m gives inconsistent json every other run

We have models like following definitions which are composed. Where the MyBase might reside in another package not directly related to api package.
// MyBase holds the base attributes
type MyBase struct {
    AttributeA string `json:"attributeA"`
    AttributeB string `json:"attributeB"`
}

// MyBaseResponse used as api response
// swagger:model MyBaseResponse
type MyBaseResponse struct {
    *MyBase
    AttributeC string `json:"attributeC"`
}

Now when running the following command we do see inconsistent results in the generate json.
swagger generate spec -m -o docs/swagger.json && git diff

One time it contains the MyBase and the other time we see it is getting removed again. We have this for a bunch of definitions. So one run it removes MyBaseA next time it adds it and removes another one etc. To me this looks like a bug which is not properly traversing composed structs to include those attributes as part of the MyBaseResponse. The behavior is also random as sometimes nothing changes.
using above bash command using git diff it is easy to detect the changes. For us this is really a blocking issue as goreleaser project does not allow dirty state to make a release, which is pretty logical as your release might be jeopardized when generated code changed during a build compared to the committed code.

I would have to create an example to reproduce as the real project is propietary and I can't share. Let me try to create small example tomorrow to reproduce.

I can reproduce this.  I'll need to continue looking why this occurs
The relevant debug output is:
Adds elements:
2019/10/05 15:22:18 got the named type object: github.com/marcofranssen/go-swagger-issue/api.ExampleResponse | isAlias: false | exported: true
2019/10/05 15:22:18 maybe allof field(true) Example: *github.com/marcofranssen/go-swagger-issue/domain.Example (*types.Pointer) [""](anon: true, embedded: true)
2019/10/05 15:22:18 maybe allof field Example: *github.com/marcofranssen/go-swagger-issue/domain.Example(*types.Pointer) [""]
2019/10/05 15:22:18 embedded *github.com/marcofranssen/go-swagger-issue/domain.Example
2019/10/05 15:22:18 embedded struct{Title string "json:\"title\""; Description string "json:\"description\""; Priority int "json:\"priority\""}
2019/10/05 15:22:18 embedded named type: *types.Struct
2019/10/05 15:22:18 skipping field "Title" for allOf scan because not anonymous
2019/10/05 15:22:18 skipping field "Description" for allOf scan because not anonymous
2019/10/05 15:22:18 skipping field "Priority" for allOf scan because not anonymous
2019/10/05 15:22:18 field Title: string(*types.Basic) ["json:\"title\""] ==>
2019/10/05 15:22:18 field Description: string(*types.Basic) ["json:\"description\""] ==>
2019/10/05 15:22:18 field Priority: int(*types.Basic) ["json:\"priority\""] ==>
2019/10/05 15:22:18 got the named type object: github.com/marcofranssen/go-swagger-issue/api.ExampleListResponse | isAlias: false | exported: true
2019/10/05 15:22:18 skipping field "Examples" for allOf scan because not anonymous
2019/10/05 15:22:18 skipping field "Page" for allOf scan because not anonymous
2019/10/05 15:22:18 skipping field "Limit" for allOf scan because not anonymous
2019/10/05 15:22:18 field Examples: []github.com/marcofranssen/go-swagger-issue/api.ExampleResponse(*types.Slice) ["json:\"examples\""] ==>
2019/10/05 15:22:18 named refined type github.com/marcofranssen/go-swagger-issue/api.ExampleResponse
2019/10/05 15:22:18 field Page: int(*types.Basic) ["json:\"page\""] ==>
2019/10/05 15:22:18 field Limit: int(*types.Basic) ["json:\"limit\""] ==>
2019/10/05 15:22:18 got the named type object: github.com/marcofranssen/go-swagger-issue/domain.Example | isAlias: false | exported: true
2019/10/05 15:22:18 skipping field "Title" for allOf scan because not anonymous
2019/10/05 15:22:18 skipping field "Description" for allOf scan because not anonymous
2019/10/05 15:22:18 skipping field "Priority" for allOf scan because not anonymous
2019/10/05 15:22:18 field Title: string(*types.Basic) ["json:\"title\""] ==>
2019/10/05 15:22:18 field Description: string(*types.Basic) ["json:\"description\""] ==>
2019/10/05 15:22:18 field Priority: int(*types.Basic) ["json:\"priority\""] ==>

Removes elements:
2019/10/05 15:22:39 got the named type object: github.com/marcofranssen/go-swagger-issue/api.ExampleListResponse | isAlias: false | exported: true
2019/10/05 15:22:39 skipping field "Examples" for allOf scan because not anonymous
2019/10/05 15:22:39 skipping field "Page" for allOf scan because not anonymous
2019/10/05 15:22:39 skipping field "Limit" for allOf scan because not anonymous
2019/10/05 15:22:39 field Examples: []github.com/marcofranssen/go-swagger-issue/api.ExampleResponse(*types.Slice) ["json:\"examples\""] ==>
2019/10/05 15:22:39 named refined type github.com/marcofranssen/go-swagger-issue/api.ExampleResponse
2019/10/05 15:22:39 field Page: int(*types.Basic) ["json:\"page\""] ==>
2019/10/05 15:22:39 field Limit: int(*types.Basic) ["json:\"limit\""] ==>
2019/10/05 15:22:39 got the named type object: github.com/marcofranssen/go-swagger-issue/api.ExampleResponse | isAlias: false | exported: true
2019/10/05 15:22:39 maybe allof field(true) Example: *github.com/marcofranssen/go-swagger-issue/domain.Example (*types.Pointer) [""](anon: true, embedded: true)
2019/10/05 15:22:39 maybe allof field Example: *github.com/marcofranssen/go-swagger-issue/domain.Example(*types.Pointer) [""]
2019/10/05 15:22:39 embedded *github.com/marcofranssen/go-swagger-issue/domain.Example
2019/10/05 15:22:39 embedded struct{Title string "json:\"title\""; Description string "json:\"description\""; Priority int "json:\"priority\""}
2019/10/05 15:22:39 embedded named type: *types.Struct
2019/10/05 15:22:39 skipping field "Title" for allOf scan because not anonymous
2019/10/05 15:22:39 skipping field "Description" for allOf scan because not anonymous
2019/10/05 15:22:39 skipping field "Priority" for allOf scan because not anonymous
2019/10/05 15:22:39 field Title: string(*types.Basic) ["json:\"title\""] ==>
2019/10/05 15:22:39 field Description: string(*types.Basic) ["json:\"description\""] ==>
2019/10/05 15:22:39 field Priority: int(*types.Basic) ["json:\"priority\""] ==>

@casualjim @fredbi - Can we expect solution for this issue in any time sooner.?

And it looks like when ExampleResponse gets processed first things work out fine, but when the ExampleListResponse gets processed first it doesn't add the base type as discovered model

@casualjim I think it's not about which model is processed first. I found out that the Models map while iterating over is being updated with new embedded models (btw. should that happen?). Sometimes loop will not read new entries from the map that's why we have inconsistent results.
That's the place where it happens:
https://github.com/go-swagger/go-swagger/blob/3552147e71fdc4346fa205161a7ff8801c2af430/codescan/spec.go#L196
I solved that by copying the s.ctx.app.Models map to new one before processing. What do you think @casualjim @fredbi? If the solution is ok with you then I can create a PR.

I created a fix for that https://github.com/go-swagger/go-swagger/pull/2209


Google map ref

Hi All,
I am using 6.3.0 version and want to get map reference using below code but unable to get map ref.
const AsyncGettingStartedExampleGoogleMap = withScriptjs(
withGoogleMap(
props => (
<GoogleMap  mapElement={

                    } googleMapURL="https://maps.googleapis.com/maps/api/js?key=MYKEY&v=3.exp" loadingElement={

                }
                    containerElement={

                }
                 ref={googleMap => {
                        if (!googleMap) {
                            return;
                        }
                      console.log(googleMap);
                    }}

                </GoogleMap>
                )
              )
            )

I am getting this "__SECRET_MAP_DO_NOT_USE_OR_YOU_WILL_BE_FIRED" as a map context , please let me know how I can get real map ref, I need map ref for marker click and set map on center and other feature like display traffic and route.

This from the docs can be useful:
const MapWithControlledZoom = compose(
  withProps({
    googleMapURL: "https://maps.googleapis.com/maps/api/js?key=AIzaSyC4R6AN7SmujjPUIGKdyao2Kqitzr1kiRg&v=3.exp&libraries=geometry,drawing,places",
    loadingElement: <div style={{ height: `100%` }} />,
    containerElement: <div style={{ height: `400px` }} />,
    mapElement: <div style={{ height: `100%` }} />,
  }),
  withState('zoom', 'onZoomChange', 8),
  withHandlers(() => {
    const refs = {
      map: undefined,
    }

    return {
      onMapMounted: () => ref => {
        refs.map = ref
      },
      onZoomChanged: ({ onZoomChange }) => () => {
        onZoomChange(refs.map.getZoom())
      }
    }
  }),
  withScriptjs,
  withGoogleMap
)(props =>
  <GoogleMap
    defaultCenter={{ lat: -34.397, lng: 150.644 }}
    zoom={props.zoom}
    ref={props.onMapMounted}
    onZoomChanged={props.onZoomChanged}
  >
    <Marker
      position={{ lat: -34.397, lng: 150.644 }}
      onClick={props.onToggleOpen}
    >
      <InfoWindow onCloseClick={props.onToggleOpen}>

          <FaAnchor />
          {" "}
          Controlled zoom: {props.zoom}

      </InfoWindow>
    </Marker>
  </GoogleMap>
);

Take a look at " ref={props.onMapMounted}" and "onMapMounted".

Cool but show for us as you use this component, him should seem like that:
let mapsRef = React.createRef();
<MapWithControlledZoom ... onMapMounted={ mapsRef } />

@viveksrivastawa @beavcast @rflmyk Please take a look at @react-google-maps/api We have rebuild this API to support new React.js 16.8. We had rewritten it to TypeSript, and implified API. Also we have a ton of examples and documentation. You get autocomplete in VScode for free. https://github.com/JustFly1984/react-google-maps-api/tree/master/packages/react-google-maps-api

After several hours simply trying to get a map reference, and yes, unsuccessfully trying the tricks in this thread and elsewhere, I have had to say "screw it" and just use the reference that is easily available despite being named __SECRET_MAP_DO_NOT_USE_OR_YOU_WILL_BE_FIRED.
I'm using a functional component and the new React useState() hook to store the map ref in state:
const [mapRef, setMapRef] = useState(null)
Then in the  component, I include this prop:
ref={ref => setMapRef(ref)}
This allows me to later (in event handlers, etc) to access the "raw" google map object:
const map = mapRef.context.__SECRET_MAP_DO_NOT_USE_OR_YOU_WILL_BE_FIRED
If you don't want me to use context.__SECRET_MAP_DO_NOT_USE_OR_YOU_WILL_BE_FIRED then how about a simple getMap() method, please?!
:coffee:

Try typing "google" in your browser console while developing. If it returns a map object, you can use the global variable "google" in your code in order to obtain the google map object that your're searching for. I'm using this library for a project and this trick works.

guys, try our new lib @react-google-maps/api

@molimauro , close but fail for me. I do see some folks report this works for them, so not sure what's different for me, but the google object contains the classes but not my map instance.

Don't be fooled by google.maps.Map as that is just the Map class--not my map instance. I did not find any methods that would allow me to get my instance either. Ideas?
@JustFly1984 I WANT TO! I saw your comment about your newer version in another thread and checked it out. I installed yesterday and rewrote my component to use it--VERY easy, less code, and easy to get a map reference. However, I ran into some issues I did not know how to handle.
First was every time my data reloaded (graphql polling every 15 seconds), the map would recenter to the original center setting. The user's modified zoom would survive, but not position. So if the user pans and zooms, after about 15 seconds, the map recenters. react-google-maps does not do this.
Second issue was several things just didn't work as described in the very clear documentation. For example, if I tried to use the useGoogleMap() hook and other hooks in the package, things fail with:
Error: invariant requires an error message argument
I am using React 16.8.6.
Googling for that error resulted in VERY few hits---like a Google search unicorn. I'm not using Typescript and am admittedly naive about Typescript. Does this make my project not fully compatible with your package?
Thanks! :coffee:

@viveksrivastawa @TroyWolf may I ask you why you need the map instance? Is there something that you can't do with the available library functions?

@molimauro Something I'd consider very normal for a map application: Upon Marker click, I want to do things like:

Center map on the Marker  map.setCenter() or map.panTo()
Zoom in a few levels  map.setZoom()
Pop a small modal with info about the item

In my Marker onClick handler, how does the package intend for me to perform map.setZoom(11)?

@TroyWolf I currently do all the things you've mentioned in this way:
<GoogleMap
    center={{props.center}} // center instead of defaultCenter
    zoom={props.zoom}
    ref={props.onMapMounted}
    onZoomChanged={props.onZoomChanged}
    ...
  >

where props.center is an object = {lat: -24.397, lng: 160.644}. If you change this props upon the marker click the map will be recentered.
The same for props.zoom
<Marker
      position={{ lat: -34.397, lng: 150.644 }}
      onClick={ () => props.changeZoomAndCenterAndDoOtherStuff(-34.397, 150.644, 11)}
    >

And in the map parent component define the function:
changeZoomAndCenterAndDoOtherStuff(lat, lng, zoom) {
     this.setState({
      center: {lat: lat, lng: lng}
      zoom: zoom
    });
}

Of course this is only an example, hope it helps and let me know if this works for you.

@molimauro, that does help. Thank you!  @JustFly1984 , it also explains my center issue with your package. It's the difference between center and defaultCenter. Fixed by maintaining a state variable for the center position, changing it in my Marker onClick handler, and using it here:
<GoogleMap center={center} ...other props />

Glad it helped. The effect of panning, in my case, happens when the actual center of the map and the center you're going to set are close, otherwise no effect is obtained (this happens also in Google Maps website when you search for a close location and for a far one).

‘Error: invariant requires an error message argument’ Means that you forgot to include correct ‘libraries’ prop to LoadScript

@JustFly1984 , quick FYI -- I'm using @react-google-maps/api now. Thanks for being so responsive! :coffee:
THANKS to @molimauro, too!

@react-google-maps/api did not work for me. It has many bugs, including one in which using "directionsService" makes a lot of requests. I tried to handle this error in many ways but I still think that tomchentw's library with all its problems still better for production.

@Kolimar
You need to handle directionService requests using debounce pattern. People has different business requirements, and our app is plain layer on top of google maps api. You have all the freedom and usability.
If you think there is issues in component's design, file an issue in our repository, or even better - make a PR.
You are welcome.

Changing the default center will rerender the map. I don't think that is desirable.

@TroyWolf I currently do all the things you've mentioned in this way:
<GoogleMap
    center={props.center} // center instead of defaultCenter
    zoom={props.zoom}
    ref={props.onMapMounted}
    onZoomChanged={props.onZoomChanged}
    ...
  >

where props.center is an object = {lat: -24.397, lng: 160.644}. If you change this props upon the marker click the map will be recentered.
The same for props.zoom
<Marker
      position={{ lat: -34.397, lng: 150.644 }}
      onClick={ () => props.changeZoomAndCenterAndDoOtherStuff(-34.397, 150.644, 11)}
    >

And in the map parent component define the function:
changeZoomAndCenterAndDoOtherStuff(lat, lng, zoom) {
     this.setState({
      center: {lat: lat, lng: lng}
      zoom: zoom
    });
}

Of course this is only an example, hope it helps and let me know if this works for you.

I know it's an old thread but I came across it as I am facing issue in implementing a simple functionality
Trying to move the zoom controls to top-left from the default position of bottom-right. Unable to do it as 'google' is not defined.
Do you have any idea?

@vipulm124, Unfortunately, I have not been using any of these Google Map related packages for almost a year now--I moved off the project where I was using this heavily. I no longer have access to that code to research this for you.
However, I can tell you this from memory.... I switched to using react-google-maps/api
https://react-google-maps-api-docs.netlify.app/
The secret, as I recall was to use their useLoadScript() helper. It resulted in window.google being available.

Hi @vipulm124, try this:
<GoogleMap
    center={props.center} // center instead of defaultCenter
    zoom={props.zoom}
    ref={props.onMapMounted}
    onZoomChanged={props.onZoomChanged}
    defaultOptions={{zoomControlOptions: {position: 1}}} // 1 === window.google.maps.ControlPosition.TOP_LEFT
    ...
  >

Let me know if this works!

defaultOptions={{zoomControlOptions: {position: 1}}}

Hi @molimauro
I think I forgot to mention, but I am using react-google-maps/api.
Although, your idea worked just by updated it as
options={{zoomControlOptions: {position: 1}}}
Still, I will keep searching the way to use 'google' keyword in react-google-maps/api package
Thanks alot for your help

@vipulm124, Unfortunately, I have not been using any of these Google Map related packages for almost a year now--I moved off the project where I was using this heavily. I no longer have access to that code to research this for you.
However, I can tell you this from memory.... I switched to using react-google-maps/api
https://react-google-maps-api-docs.netlify.app/
The secret, as I recall was to use their useLoadScript() helper. It resulted in window.google being available.

@TroyWolf
Sorry I forgot to mention, I am using react-google-maps/api.
Unable to use 'google.maps' there itself.
Let me know if you have any idea about this
Thanks in advance

Sorry for the question but also the variable window.google is undefined?

Sorry for the question but also the variable window.google is undefined?

@molimauro  - Yes, even the window.google is giving error that 'google is undefined

@TroyWolf So Is it safe to use this "__ SECRET_MAP_DO_NOT_USE_OR_YOU_WILL_BE_FIRED" sir ? because it's working lol


donations from my profile to a collective are showing up as amount raised

I made two donations today from my profile with my credit card and they are showing up as amounts raised instead of amount donated. I checked the DB and I show up as backer not fundraiser.

I see two donations of $10. They increased your total amount donated from $680 to $700.
But they shouldn't have counted in the total amount raised. Looking into it.


Trigger event with payload from stubbed component

I want to test that my ParentComponent correctly handles an event emitted by the ChildComponent:
const ParentComponent = {
  template: `<div><child-component id="childComponent" @myevent="myHandler" /></div>`,
  components: { ChildComponent },
  methods: {
    myHandler(payload) {
      console.log(payload)
    },
  },
}

const ChildComponent = {
  template: `<p>Child</p>`,
  emits: ["myevent"],
}

I am not concerned with the underlying workings of the ChildComponent, only that it emits this particular event. For
that reason I have stubbed the ChildComponent. This leaves me with a DOMWrapper which has a trigger() method available:
test("handles my event", async () => {
  const wrapper = shallowMount(ParentComponent)
  await wrapper.find(`[id="childComponent"]`).trigger("myevent", { example: "Test 1" })
})

However, when adding a payload to the event it does not get passed as expected to the handler:
//console.log
{
  isTrusted: [Getter],
  example: 'Test 1'
}

Likewise, if I pass a string as the payload it gets split as follows:
test("handles my event", async () => {
  const wrapper = shallowMount(ParentComponent)
  await wrapper.find(`[id="childComponent"]`).trigger("myevent", "Test1")
})

//console.log
{
  '0': 'T',
  '1': 'e',
  '2': 's',
  '3': 't',
  '4': '1',
  isTrusted: [Getter]
}

I suspect I am passing the payload incorrectly, but how else can I test an event with payload from a stubbed component?

You should use findComponent and vm.$emit to emit custom events. trigger is only for DOM Events like click or focus.
const child = wrapper.findComponent({ name: 'ChildComponent' })
await child.vm.$emit('myevent', { example: "Test 1" })

That’s great, love it when there’s a simple fix to doing something wrong 😁

Hello. I don't know if I'm missing something about this. I followed the suggestion of using vm.$emit for triggering a custom event from the child component. The issue I'm having is that if I check the event array returned by wrapper.emitted(), I'm getting the event I triggered from the child component. Does this make sense? I would expect that this event array should only contain events emitted by the wrapper itself and not events from children. And I'm sure I'm not emitting the same event from the component I mounted for testing
const child = wrapper.findComponent({ name: 'ChildComponent' })
await child.vm.$emit('myevent', { example: "Test 1" })

const events = wrapper.emitted()
console.log(events) // or if you want, assert something

So, checking the events array, this is what I'm getting:
{
  myevent: [
    [
      {
        example: 'Test 1',
      },
    ],
  ],
}

OK. I found out why this wasn't working. The component that I'm testing goes kind of like this:
<script setup lang="ts">
const props = defineProps<{
  someProp: string
}>()

const emit = defineEmits<{
  (event: 'parentSubmit', formData: object): void
}>()

const handleSubmit = (newFormData) => {
  emit('parentSubmit', newFormData)
}
</script>

<template>
  <MyChildForm
    @childSubmit="handleSubmit"
    data-test-id="ParentComponent__form"
  >
  </MyChildForm>
</template>

So, I wanted to test that when the MyChildForm component submits something with childSubmit event, the parentSubmit event was being emitted. It seems easy.
const wrapper = shallowMount(ParentComponent, {
  props: { someProp: 'some value' },
})

const child = wrapper.findComponent({ name: 'MyChildForm' })
await child.vm.$emit('childSubmit', { example: "Test 1" })

expect(wrapper.emitted()).toHaveProperty('parentSubmit') // <- this fails

So the assert fails and actually, wrapper.emitted() contains childSubmit. You would expect that it would contain the parentSubmit, since I'm taking it from the wrapper.
Guess what?
Since MyChildForm is the root node of the component, it's inheriting all attributes. Even I printed out the props for both wrapper.props() and wrapper.findComponent({ name: 'MyChildForm' }).props() and they're the same.
Wow!!!
When I changed wrap MyChildForm inside a div, everything changed. wrapper.emitted() no longer has the childSubmit event. Well, now it's empty and I need to understand why. Maybe I'm missing something.


Parameters and Flops of Fast-ACVNet

Hi, since your code has not been published, could you tell me the information on your parameters of [Fast-ACVNet] and also the Flops at KITTI's resolution?

Thank you for your attention, I have uploaded all the codes


[Bug]: - Layer call changes/breaks graph?

Module
Layers
Contact Details
No response
Current Behavior
It seems that a layer call changes/breaks its tensor graph.
The error is easily visible when trying to copy a layer after this layer was called. A deepcopy at this point throws a runtime error:
RuntimeError: Only Tensors created explicitly by the user (graph leaves) support the deepcopy protocol at the moment
It should be noted that this is not the case if the layer is exported (vanilla_export) before its called.
Expected Behavior
A layer call shouldn't change/break its tensor graph. And a deepcopy should be possible even after a layer call.
Version
v0.1.0
Environment
- OS: Linux arch 5.18.9-arch1-1
- Python version: 3.7
- PyTorch version: 1.11.0+cu102
- Packages used version: deel-torchlip torch

Relevant log output
RuntimeError: Only Tensors created explicitly by the user (graph leaves) support the deepcopy protocol at the moment

To Reproduce
The example uses SpectalLinear but this error is not layer dependent. I also tested FrobeniusLinear, SpectralConv2d and FrobeniusConv2d and got the same result.
#!/usr/bin/env python3
from copy import deepcopy
from deel.torchlip import SpectralLinear
import torch

lin = SpectralLinear(1, 1)
#lin = lin.vanilla_export()
x0 = torch.tensor([1.])
copy = deepcopy(lin)  # ok
lin(x0)
copy = deepcopy(lin)  # fail if not vanilla_export
# RuntimeError: Only Tensors created explicitly by the user (graph leaves) support the deepcopy protocol at the moment

Hello @HeinrichAD,
The Lipschitz layers use reparameterization to compute normalized weights. The SpectralLinear and SpectralConv2d modules are in particular based on torch.nn.utils.spectral_norm. However, it seems that deepcopying layers with weight reparameterization in PyTorch does not work (see this or this issue). And they unfortunately don't provide any workaround.

@cofri thank you for clarification.
That's unfortunately but apparently seems to be unavoidable.
A possible workaround is to always evaluate etc. on the vanilla export. That's fine for me.


Add cephUser and cephPools to cephBackend

Extend API to support cephUser and cephPools within the
cephBackend struct. Without this patch the operator can
only configure glance to connect to a Ceph cluster which
has the cephx user set to 'openstack' and the pool name
set to 'images'. Instead, support any user or pool name.
Signed-off-by: John Fulton<EMAIL_ADDRESS>

@fmount @abays would you please review? thanks


bom-refs not updated and ordered anymore

I upgraded a couple of packages in my python environment that upgraded shared dependencies with sbommerge. The effect is that the numbered bom-refs are not updated correctly after merging two sbom files. I also noticed some missing information in the "dependencies" section. After some hours of panic with my SBOM generation workflow messed up, I found that the culprit was the most recent version of lib4sbom. I progressively downgraded lib4sbom and found that the most recent version for this to work correctly is lib4sbom==0.6.1. I am wondering, would it be possible to also add lib4sbom in the SBOM's "tools" section?

@ogbautista The bom-refs will just be copied in the merged SBOM. Need to look into this
Lib4sbom is under constant development but it isn't a tool and shouldn't be included in the tools section of an SBOM. Many SBOM tools will use libraries but these are not specified within the SBOM.


Pdf content is getting scrambled after embedding the image

Hi
After embedding the image pdf is getting scrambled. Below is the example, how the pdf becomes It's happening only some selected pdfs. I have attached that pdf too. Please help me to fix this.

20190718.pdf
Thanks

Hello @sanjeet-leewayhertz! I'm unable to reproduce the issue. I used the following script to load the PDF you shared and add a JPG image to it. The resulting PDF looks just fine, and does not appear to be scrambled at all.
import fs from 'fs';
import { PDFDocument } from 'pdf-lib';

(async () => {
  const pdfDoc = await PDFDocument.load(
    fs.readFileSync('20190718.pdf'),
  );

  const img = await pdfDoc.embedJpg(
    fs.readFileSync('assets/images/cat_riding_unicorn.jpg'),
  );

  pdfDoc.getPages()[0].drawImage(img, img.scale(0.1));

  const pdfBytes = await pdfDoc.save();

  fs.writeFileSync('./out.pdf', pdfBytes);
})();

Page 1 of out.pdf:

In addition to the PDF you provided, would you please share a script and image that I can use to reproduce the issue? Also, what environment are you running pdf-lib in? E.g. Node, browser, React Native, etc...

Hi @Hopding
I am using the Node environment. And it's weird same pdf if I open through chrome it's appeared scrambled. And if we open it through any pdf viewer then it appears correct. Here is the screenshot of the same pdf(Opened in chrome browser) that you attached.

Thanks

I was able to find the issue. It is due to a bug in the page Resources normalization code. It only surfaces in documents with a specific page tree structure. And the resulting PDF files are displayed with binary jargon in certain readers (e.g. Chrome and Acrobat), but not others (e.g. macOS's Preview).
I'm working on a fix. I hope to have it released in the coming days.

Thanks, @Hopding for the quick reply. I will wait for the fix.

Version 1.2.1 is now published. It contains the fix for this issue. The full release notes are available here.
You can install this new version with npm:
npm install<EMAIL_ADDRESS>
It's also available on unpkg:

<EMAIL_ADDRESS><EMAIL_ADDRESS>


Is there a rails 5 sample?

I'm starting a new project and I'd rather start with rails 5 than having to migrate later.

Hi @retorquere, you can take a look here https://github.com/auth0-samples/auth0-rubyonrails-api-sample/issues/4 API only example using Rails 5

I've gone with Sinatra, but thanks

Closing as this issue is over two years old.


Change to StaticConnectionPool for Multiple Hosts

Change Example for Connection to Multiple Elastic Sever Hosts, which are known already, to use StaticConnectionPool instead of SniffingConnectionPool. Using SniffingConnectionPool was giving Null Pointer Exception in the method RequestPipeline.CreateClientException(). I was not able to pinpoint the parameter which was null.

@huzefakagdi I much rather solve the NRE do you have a stack trace when this happens?

Hi Martijn,
The relevant stacktrace for the NRE when we use StickyConnectionPool to create ElasticLowLevelClient is as below:
   at Elasticsearch.Net.RequestPipeline.CreateClientException[TResponse](TResponse response, IApiCallDetails callDetails, RequestData data, List1 pipelineExceptions)
at Elasticsearch.Net.Transport1.FinalizeResponse[TResponse](RequestData requestData, IRequestPipeline pipeline, List1 seenExceptions, TResponse response)
at Elasticsearch.Net.Transport1.Request[TResponse](HttpMethod method, String path, PostData data, IRequestParameters requestParameters)    at Elasticsearch.Net.ElasticLowLevelClient.DoRequest[TResponse](HttpMethod method, String path, PostData data, IRequestParameters requestParameters)    at Elasticsearch.Net.ElasticLowLevelClient.Index[TResponse](String index, String type, PostData body, IndexRequestParameters requestParameters)
The code that we are using is similar to the example in the documentation. The only difference is that we are calling the BasicAuthentication on the ConnectionConfiguration that is created.
The only change in code required to get rid of the exception is to change the connection pool to StaticConnectionPool.
We are using the Elasticsearch.Net version 6.0.0.

If you update to the latest version of NEST/Elasticsearch.NET 6.6.0 is the problem still there?

I updated to the latest version on my local machine and we do not get the error for SniffingConnectionPool. It seems that there were issues with the older package. But unfortunately we cannot update to v6.6 in our actual code as we will need to upgrade to .NET Framework v4.6.1 for that.
Thanks for your help. You may reject the PR.

https://www.nuget.org/packages/NEST/6.2.0 was our latest version on 4.5 hopefully that contains the fix for it as well @huzefakagdi thank you for bringing it to our attention :+1:


Add screenshots of working application

Add screenshots of different activities / layouts / screens within the application.

Updated details on Figma Prototype.


Container width props based on device sizes

For designing layouts, sometimes its necessary to have width for containers. It makes the layout  flow easy to understand and manage. It would be helpful to have these devices sizes as container props based on the existing responsive values.

To keep the current naming convention we can have something like:
--size-container-xxs : 240px,
--size-container-xs: 360px,
--size-container-sm: 480px,
--size-container-md: 768px,
--size-container-lg: 1024px,
--size-container-xl: 1440px
--size-container-xxl: 1920px
These can be individual prop packs.

this is a great idea, thanks for bringing it up! 🙂
def works best imo as a prop pack. i think this work could be done swiftly!
curious your thoughts on naming them like this, removing the word container?
more abstract so maybe more use cases?
--size-xxs: 240px;
--size-xs:  360px;
--size-sm:  480px;
--size-md:  768px;
--size-lg:  1024px;
--size-xl:  1440px;
--size-xxl: 1920px;

to me, this make the sizes match the previous naming style closer and doesnt imply any use cases, just a straight port of the media query t-shirt sizes style values into usable prop utilities.

Yes, i agree. We don't need the container word.

@argyleink , should i add them to the props.media.css or the props.sizes.css. The sizes files already exists so not sure where these props should go? I can create a PR for it once you confirm it.  I think props.sizes.css seems to make more sense. wdyt?

at the end of the sizes props yeah! make sure to edit the js file, the css file is generated from that JS 👍🏻


Relative imports do not work in settings file

Any relative imports in settings files do not work as it is being copied to a different location.

Can you give me an example to help reproduce? Where are your settings file located?

settings
├── base.py
├── __init__.py
├── production.py
└── staging.py

This is the structure of my settings directory in my application. I import settings from base.py in production.py and staging.py
from base import *

Gotcha, thanks for reporting. Will try to get to this when I can, but will accept PR!

If anyone is looking for a workaround, do a full path import.
e.g. from <project_name>.settings.base import *
@Miserlou can you give some points on how to fix this?


Port number on server

Hi,
I have pulled the deb file of timeseriesadmin and installed it on my ubuntu 18.04 server VM. I dont find instructions on port number on VM server, as in from which port does this application run? I observe a process that is utilising port 8088 after installation, but can't confirm it is timeseriesadmin as my webpage doesn't load

I'm not sure about your issue. If you downloaded the .deb package you should be able to install it and run like a regular system application. There is no need to open a web browser to use Timeseries Admin installed as a .deb package.
If you are asking about Influx DB database the default port is 8086, so in case you are running InfluxDB locally it should expose its API on http://localhost:8086 which you can check by entering for example https://status.predictail.com:8086/query?q=SHOW DATABASES
Please let me know if this was any help for you.

Please reopen if any further assistance would be needed.


Improve article 2210.03629

The macro \model is not rendered. It should be rendered as ReAct.

Info:ignore:\model Ignoring redefinition (\newcommand) of '\model'
 at iclr2023_conference.tex; line 72 col 0 - line 72 col 35

We may need a iclr2023 binding if this is a sticky error.


dep: add full feature to derive_more

As per the derive_more documentation and specifically https://github.com/JelteF/derive_more?tab=readme-ov-file#installation, it seems that in last versions of Rust, to compile properly, we need to specify features to avoid errors of this type:
error[E0432]: unresolved imports `derive_more::Deref`, `derive_more::DerefMut`, `derive_more::From`, `derive_more::IntoIterator`
   --> crates/consensus/src/request.rs:10:19
    |
10  | use derive_more::{Deref, DerefMut, From, IntoIterator};
    |                   ^^^^^  ^^^^^^^^  ^^^^  ^^^^^^^^^^^^ no `IntoIterator` in the root
    |                   |      |         |
    |                   |      |         no `From` in the root
    |                   |      no `DerefMut` in the root
    |                   no `Deref` in the root

Since we are using quite a few elements currently, we are choosing the full configuration for now.

how to reproduce the compiler error, can we instead enable the required features in the consensus crate?

Maybe my version of rust or something, anyway seems to be gone now but I've added the specific features we need for the consensus crate to be consistent with the other usages on the other crates.


OTG Test - RT-2.1: Base IS-IS Process and Adjacencies

OTG conversion of RT-2.1: Base IS-IS Process and Adjacencies
Fixes #589
Output log here

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1602

Relevant Lines:
2177

💛  - Coveralls

@dplore could you please assign

/gcbrun


Rust keywords are not escaped in all situations

Currently code generation produces invalid rust code for a schema like this:
schema {
  query: Query
  mutation: Mutation
}

"""This directive allows results to be deferred during execution"""
directive @defer on FIELD

"""The top-level Query type."""
type Query {
  """Keyword type"""
  search: Self
}

"""Keyword type"""
type Self {
  """
  A keyword variable name with a keyword-named input type
  """
  transactions(struct: extern!): Result
}

"""Keyword type"""
type Result {
  """Keyword field."""
  for: String
  """dummy field with enum"""
  status: AnEnum
}

"""Keyword input"""
input extern {
  """A field"""
  id: crate
}

"""Input fields for searching for specific values."""
input crate {
  """Keyword field."""
  enum: String

  """Keyword field."""
  in: [String!]
}

"""Enum with keywords"""
enum AnEnum {
  where
  self
}

There are some keyword tests in the code now. Is this resolved or is it still incomplete? Can we add a test for the missing cases if incomplete?

I think there is enough coverage now that we can close this issue, and open a new one if we find specific cases that aren't covered.


Build: Fix Github actions

The environment used to run GitHub actions has been updated upstream, which breaks the build. This is mainly due to the use of pip. That is, the use of upstream pip and not the one provided by Debian through apt-get install python3-pip.
This updates all the build scripts to use the standard Debian packages (if available) and not rely on "pip install".

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 58.12%. Comparing base (d75c240) to head (ecfbf2d).
Report is 9 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #431      +/-   ##
==========================================
+ Coverage   57.63%   58.12%   +0.48%
==========================================
  Files          16       16
  Lines        2627     2629       +2
==========================================
+ Hits         1514     1528      +14
+ Misses       1113     1101      -12

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


add info column

add a column with a brief description / explanation about the key and values displayed

fixed in https://github.com/rampall/doctor-bee/commit/6264018fa602d3e90caaa0fba4ad793c87d91dac


About CUDA Memory Usage During Training

Hi, thanks for your excellent work.
I‘m curious about how much CUDA memory is used when the model is trained on images with a resolution of 256x256 (as mentioned in the paper). Is it possible to train successfully at higher resolutions, such as 512x512?

hi, thanks for checking out spad!
we used H100s 80GB cards to train our models, and were able to fit a batch of 10 samples (40 images) when training 4-view model, and a batch of 36 samples (72 images) when training 2-view model on one GPU.
increasing number of views in training leads to sharper decrease in number of images per batch because of the quadratic complexity of self-attention and unoptimized implementation of epipolar attention in xformers (based on masking, here). i believe it is possible to optimize it further.
i believe it would be feasible to train a 2-view model at 512x512 with SD1/2. also, i think stable-cascade may alleviate this issue since it has a smaller latent space, however I have not tried it myself.
hope this helps!

Thanks for your reply, it's very helpful for me.


Histogram default to density=True

The purpose of the SingleObsComparer.hist() and the ComparerCollection.hist() should be to compare distributions. not counts. The number of observations can be wildly different from the number of modelled data, which makes comparing counts pretty useless.

Before:

After:

I also considered to add a Plotly histogram, but concluded that it was not very useful.