What is the order to install the environment, if want to use CTRL

i follow the order like this:
1.https://github.com/tusen-ai/SST/blob/main/docs/overall_instructions.md
install pytorch mmcv mmdet mmsegmentation mmdet3d
then pip install -e .
2.https://github.com/tusen-ai/SST/blob/main/docs/CTRL_instructions.md#step-2-use-immortaltracker-to-generate-tracking-results-in-training-split-bin-file-format
(2)https://github.com/Abyssaledge/ImmortalTracker-for-CTRL    run_mot.sh
i really need a specific code running instruction to follow, and need enviroment installation order

The order you follow is right. Did any errors occur?

1:
can you give me a scrennshot in ./data, i am confused the structure, and https://github.com/open-mmlab/mmdetection3d/blob/1.0/docs/getting_started.md,the link you give for mm3d to getting started wasn't existed, So I don't know if the dataset I'm using in mmdet3d v1.1.0 is useful for CTRL
i was confused about should we both use kiit_format and waymo_format,or just kitti_format?

$ python ./tools/ctrl/extract_poses.py
Traceback (most recent call last):
File "./tools/ctrl/extract_poses.py", line 31, in
idx_str = info['point_cloud']['velodyne_path'].split('/')[-1].split('.')[0]
TypeError: string indices must be integers

https://github.com/tusen-ai/SST/blob/main/docs/CTRL_instructions.md
if i  follow the instructions, should i  use waymo_format data?
my folder like this ./data/waymo_format
(1)bash preparedata/waymo/waymo_preparedata.sh  ./data/waymo
(2)bash preparedata/waymo/waymo_convert_detection.sh ./data/waymo_format/gt.bin cp
or  bash preparedata/waymo/waymo_convert_detection.sh ./data/kitti_format/train_gt.bin cp
(3) run_mot.sh

when i run_mot.sh
$ sh run_mot.sh
Tracking time cost: 0.22504878044128418s
evaluation/waymo/pred_bin.py:195: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
config = yaml.load(open(args.config_path, 'r'))
Converting TYPE vehicle into WAYMO Format
0it [00:00, ?it/s]
Merging different object types

No, you cannot use the dataset from mmdet3d v1.1.10, because the definition of box is different. Please use our code to generate the data. The point cloud data can be shared between different versions of mmdet3d (with minimal modifications), but the pickle info file needs to be regenerated.

If tracking time costs less than 1 second, there must be errors in the tracking process and the main body is skipped. And the errors would not be thrown due to the multi-process. So change it to single-process for debugging.

so can i use python tools/create_data.py waymo --root-path --out-dir --workers 128 --extra-tag waymo in ./SST/ to generate data,or i should use mmdet3d v0.15.0 to generate data

Yes, you could use ‘tools/create_data’ to generate data. And our repo is exactly v0.15.0.
Please reopen this issue if you need further discussion, or I may miss your posts due to too many issues.


Initial folder structure implementation

Also contains a small test page I used to make sure it is all working. Currently hidden away, but will eventually remove it once it's no longer needed.

You wanna use module.css files ?
There is currently 3 proposals :

x.module.css files
CSS in JS
Tailwind (current)

Not to familiar with Tailwind, researching online tells me doing it via the "module" method allows for css component to be loaded when they are needed vs. globally. But if Tailwind can also do this, I'm fine with that. Main worry is having things as modular as possible.

Making things too modular at the start can slow us down by a lot though so we need to be careful not to overmodularize everything ! That's my opininon

Yeah there's definitely a balance to have there. Personally, I like having things modular early on because it helps a lot when things scale up, but maybe some others can take a look at how I structure things and see what we want.


Display 2 now shows black screen.

[x] I have read the FAQ.
[x] I have searched in existing issues.

Environment

OS:pop os 22.04
scrcpy version: scrcpy 2.0
installation method:git pull,  ./install_release.sh
device model: Galaxy fold 4
Android version:13

Describe the bug
After connecting to adb and running
/usr/local/bin/scrcpy --video-bit-rate 2m --display 2 --window-title 'DexOnLinux' --turn-screen-off --stay-awake
I get a black screen and
[server] WARN: Display doesn't have FLAG_SUPPORTS_PROTECTED_BUFFERS flag, mirroring can be restricted
Which I didn't get before.
/usr/local/bin/scrcpy --video-bit-rate 2m --display 0 --window-title 'DexOnLinux' --turn-screen-off --stay-awake
Works fine, so it's just the actual dex output having problems
But display 0 doesn't respect the screen off option, so the phone display is always on. Whereas
/usr/local/bin/scrcpy --video-bit-rate 2m --display 2 --window-title 'DexOnLinux' --turn-screen-off --stay-awake
Used to let me use dex and keep the phone off.
I am using a USB c dock with an HDMI display terminator-I believe that is still necessary.

But display 0 doesn't respect the screen off option, so the phone display is always on.

That's unexpected. If you just run scrcpy --turn-screen-off, you don't get the main screen off?
Refs #3716.

[server] WARN: Display doesn't have FLAG_SUPPORTS_PROTECTED_BUFFERS flag, mirroring can be restricted
Which I didn't get before.

Probably due to a change in the device system. Refs #1238.

But display 0 doesn't respect the screen off option, so the phone display is always on.

That's unexpected. If you just run scrcpy --turn-screen-off, you don't get the main screen off?
Refs #3716.

[server] WARN: Display doesn't have FLAG_SUPPORTS_PROTECTED_BUFFERS flag, mirroring can be restricted
Which I didn't get before.

Probably due to a change in the device system. Refs #1238.

If I just do scrcpy --turn-screen-off it does the display, and turns off the screen. But if the screen is off to begin with, I get a the lock screen, and swiping up gives me a black screen I can't interact with.

Nevermind, I just have to start dex with the screen initially on.


Base64 needs padding at the end

According to RFC 4648 section 4.0 - Base 64 encoding. Padding at the end of the data is performed using the '=' character.
CBORObject.ToJSONString() converts a byte string to traditional base64 without whitespace or padding if it has 22. This seems to be a bug.

Omitting the padding is often done per section 3.2 of RFC 4648.

As it turns out, section <IP_ADDRESS> of RFC 7049 doesn't sufficiently clarify whether the base64 encoding for tag 23 uses padding or not, as is the case for base64url.  Therefore, the implementation assumes that padding is not used for base64 just as for base64url, which is a reasonable assumption.  @cabo , please weigh in on this.

Section <IP_ADDRESS> of RFC 7049 redirects the padding for tag 22 base64 to RFC 4648. My understanding of RFC 4648 section 3.2 is that padding is needed for base64.
3.2.  Padding of Encoded Data
In some circumstances, the use of padding ("=") in base-encoded data
is not required or used.  In the general case, when assumptions about
the size of transported data cannot be made, padding is required to
yield correct decoded data.
Implementations MUST include appropriate pad characters at the end of
encoded data unless the specification referring to this document
explicitly states otherwise.
The base64 and base32 alphabets use padding, as described below in
sections 4 and 6, but the base16 alphabet does not need it; see
section 8.

@peteroupc could you please extend CBOREncodeOptions to support base64_padding if you keep the default implementation as no_padding? Thank you!

I have included a feature to control Base64 padding when writing base64/base64url data to JSON.  @cabo : Please clarify whether section <IP_ADDRESS> of RFC 7049 intends traditional base64 encoding to use padding or not.

Hi Peter,
thanks for bringing this up again.  We discussed this in the CBOR WG at iETF100 (
https://datatracker.ietf.org/meeting/100/materials/minutes-100-cbor/), but it seems we didn't reach a conclusion.  Note that the issue is not really a CBOR one — the objective is to interoperate best with the JSON side, and we don't have a very good survey of what is the usual form of base64 on the JSON side.  (I have seen both the redundant base64 padding and no padding; while padding seems to be rare with base64url.)
So it would be most useful to collect some data before resolving this issue.

Re-sending.

According to cbor-wg/CBORbis#48 , the CBOR revision will be clarified to say that padding is indeed used for writing tag 22 data to JSON. This is a breaking change that can only be implemented in the next major version, version 4.0 (which is currently in its second alpha).
Now, how will this impact existing JSON data written using my current implementation (which uses no padding in both base64 and base64url)? And how should I restructure the JSON padding option added in #16 (which adds padding to both base64 and base64url, or removes it from both)? Should it be changed, or should it be deprecated in favor of yet another JSON option?

I think it is rare to find a JSON object that has both base64classic and base64url in it.  But if you do, and these do not use the standard choices for padding (yes for base64classic, no for base64url), those choices may also vary throughout your object, so you may need to specifically tag those places where the non-standard places occur.  So, to me it seems we'll need to fill the matrix and do a 21' with padding and a 22' without padding.  (Say, 1021 and 1022.)

Closing for now.  I have decided to deprecate the JSON padding option, mentioned in a previous comment here, in my CBOR library, and use the JSON padding policy in the revised CBOR specification in future versions by default.


Make PDF errors non-blocking

During a conversation about handling PDF generation errors, I came to the thought that we maybe should make generate_pdf not throw errors at all.
Instead, these should be catched and logged as either ERROR or even CRITICAL.
While we do not want PDF generation to fail, it's better if the user is not blocked from submitting their proposal because we made a mistake there. Thus, we should also investigate a way to get those logs to us.
Ideally, we'd have a logging service for all our apps that notifies us on any errors or ciriticals; but as a stop-gap we could configure an AdminEmailHandler?
This is just an idea; what do y'all think @miggol @EdoStorm96 ?

I think it is a good idea! I agree with the premise that users should not be kept from submitting because of our mistakes.


feat: support multiple binding versions

Description
This PR changes a few things:

Adds support for ONLY allowing a specific range of binding versions
Adds support for defaulting to the latest version of the bindings
Adds support for explicitly only check the appropriate binding schema when bindingVersion is explicitly defined.
Now only validate a binding if needed instead of all bindings, which could cause issues when reporting back errors.
Add missing message binding for AMQP
Add missing server binding for MQTT5
Add missing operation binding for HTTP
Fix the wrong version for MQTT5 server schema
Fix incorrect regex for pattern properties for Kafka 0.4 and MQTT5

Here is how the binding schema changes work (example with mqtt5 bindings):
    "mqtt5": {
      "properties": {
        "bindingVersion": {
          "enum": ["0.2.0"]
        }
      },

Is added to ensure only a specific range of binding versions (if the property bindingVersion is set) are valid i.e. it gives you an error if you use "bindingVersion": "0.3.0",, while still allowing no values.
      "allOf": [
        {
          "description": "If no bindingVersion specified, use the latest binding",
          "if": {
            "not": {
              "required": [
                "bindingVersion"
              ]
            }
          },
          "then": {
            "$ref": "http://asyncapi.com/bindings/mqtt5/0.2.0/server.json"
          }
        },

The first entry in the allOf is for matching the default version, i.e. when no specific bindingVersion has been sat. If so it defaults to the newest, in this case, version 0.2.0.
        {
          "if": {
            "required": [ "bindingVersion" ],
            "properties": {
              "bindingVersion": {
                "const": "0.2.0"
              }
            }
          },
          "then": {
            "$ref": "http://asyncapi.com/bindings/mqtt5/0.2.0/server.json"
          }
        }

The next entry in the allOf includes the validation for when the user explicitly states a binding version, i.e. if the property bindingVersion has been sat, and is of value 0.2.0 we validate against http://asyncapi.com/bindings/mqtt5/0.2.0/server.json.

Need to double check it validates correctly.

Had to update with latest changes, just need a single review 🙂

Thanks @char0n!
/rtm

@derberg do you know why merging is blocked? https://github.com/asyncapi/spec-json-schemas/actions/runs/4125615904/jobs/7126408523

Lets try again, thanks @dalelane 😄
/rtm

/dnm


Enrich ''Storage Variables'' chapter

Hi @enitrat  ,
after completing the Starknet Storage Layout quest yesterday on NG, i spent a few hours facing a problem due to a misunderstood concept.
from cairo book :
In mappings, the address of the value at key k_1,...,k_n is h(...h(h(sn_keccak(variable_name),k_1),k_2),...,k_n) where ℎ is the Pedersen hash and the final value is taken mod2251−256. You can learn more about the contract storage layout in the Starknet Documentation
I think this section should be enriched : when reading it, it feels like the nested pederson scheme should only be applied to nested mappings, with 2 different keys to use in the pedesen hash function.
But if you have a single mapping, with a u256 as a key, you should also apply 2 nested pedersen hash, with the only key of the mapping (actually 2 felt252, but with max size U128) considered as 2 separate keys. so basically, a single mapping with a u256 as a key is identical to a 2 nested mappings?
I think i could try to rewrite this section to make it clearer, and maybe add more content about structs storage, and more important about how u256 are stored underneath the hood.
Just let me know if you think this is relevant, but i think it is as i didn't fully understand all this concept when reading cairo book and starknet documentation.
i've been  partially helped with this blog post, but it's all about cairo 0, maybe some fresh content about u256 in cairo book would be great.
https://dev.to/peterblockman/cairo-uint256-ojf

so basically, a single mapping with a u256 as a key is identical to a 2 nested mappings?

Not only restricted to u256 but I think that's how it would work for all structs? Since a struct is not something that can be the input of a hash function, but it's serialized members are.
Anyway, if you want to take this work, I'll be happy to support it! I really appreciate external initiatives :)

yes, it seems logic this would work this way for all structs.
I think i went wrong because of starknet documentation :
"If it is a (nested) mapping, then the address of the value at key k_1,...,k_n is h(...h(h(sn_keccak(variable_name),k_1),k_2),...,k_n)  mod2^251−256."
The "nested" word made me understand it as :

if you have a single mapping -> h(sn_keccak(variable_name),k_1)
if you a mapping into a mapping -> h(h(sn_keccak(variable_name),k_1),k_2)

probably because i spent multiple months on solidity and i know a struct or array cannot be a key for a mapping with the EVM.
But it actually meant : if the key of your single mapping is more than a single felt252, then use all these ''felt 252 sub-keys'' with nested pedersen hash to obtain the address. Am i right?
If yes, what about mappings into mappings? does it work the same way? and it it possible to have an array as a key with cairo, and serialize all values to pass it to pedersen function?
What i though i could add :

2.2. Data types : add a section into ''Integer types'' , or a separate one, to talk about uint256 specifically, as i doesn't fit into a felt252. explain how it works  under the hood (struct of 2 felt252 that contains 2 * 128 bits of interest, with left padding for each felt).  Btw, maybe the chapter ''Data types'' could be renamed ''Basic Data Types'', as it doesn't include custom data types such as structs?

12.3.1 Storage Variables :
-  add a section '' Storing basic data types '' which explains how and where types that fit into a felt252 are stored (first 250 bits of sn_keccak("variable name"). We could also add a specific sub-section for u256,  which takes 2 contiguous slots with a specific format (low, high).  (btw, i saw once a u512, is it a specific custom type or is it available in core library? If it is in core library, maybe we could add it in the array in 2.2 Data types.
- In Storing customs struct, just add a few lines to precise that it works like basic data types for the location (first 250 bits of sn_keccak("variable name"), and then elements are stored contiguously .

Tell me what you think of these potential updates :)

2.2. Data types : add a section into ''Integer types''

There is already a section "Integer type", but it doesn't talk about the inner construction of u256. Feel free to add you changes there

(btw, i saw once a u512, is it a specific custom type or is it available in core library? If it is in core library, maybe we could add it in the array in 2.2 Data types.

u512 is a type defined in the corelibrary that is used for u256_wide_mul. As it doesn't implement common traits required to perform operations with it, it has been excluded from the book on purpose. Moreover, the requirement for a u512 type is extremely rare

add a section '' Storing basic data types '' which explains how and where types that fit into a felt252 are stored (first 250 bits of sn_keccak("variable name").

Sounds good. This is basically every non-struct type

We could also add a specific sub-section for u256, which takes 2 contiguous slots with a specific format (low, high)

I don't really agree, u256 should be treated like any other struct, I would rather rename Storing Custom Structs to Storing structs, and add details about the address calculation here
Perhaps it would be best to have
Storage Variables
Storing Structs
Storing Mappings
Reading from Storage
Writing to Storage


Rasa Core Error: Error: connect ECONNREFUSED <IP_ADDRESS>:5005

Rasa Core version:
rasa-core==0.9.7
Python version:
Python 2.7.15rc1
Operating system (windows, osx, ...):
Ubuntu 18.0.4
Issue:
hamin101@ubuntu:~/rasaui$ sudo npm start

><EMAIL_ADDRESS>start /home/hamin101/rasaui
> node server/server.js

Rasa UI Server: http://localhost:5001

Express server listening on port 5001

Rasa NLU Error: Error: connect ECONNREFUSED <IP_ADDRESS>:5000
Using connection string from: package.json

Rasa Core Error: Error: connect ECONNREFUSED <IP_ADDRESS>:5005
Using connection string from: package.json

Postgres DB Connected
Using connection string from: package.json
Postgres Server: <IP_ADDRESS>:5432
Database:rasa
Schema:public

Why am I getting the Error: connect ECONNREFUSED <IP_ADDRESS>:5000 for Rasa NLU and Error: connect ECONNREFUSED <IP_ADDRESS>:5005 for Core?
Content of domain file (if used & relevant):

Rasa NLU Error: Error: connect ECONNREFUSED <IP_ADDRESS>:5000
Using connection string from: package.json
what is the solutions any body solve this issuess


Some wording tweaks that may make the post a slightly smoother readin…

Tried to preserve linguistic style.

Thank you!!!


Initial manual validation plan

cc @DustinCampbell @TheRealPiotrP @akshita31

@DustinCampbell Done--I made the section about unit tests more obvious.


Implemented sort feature on created date column

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[X ] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[X] Tested manually in dev environment.

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Merging it for now, but there are a few open issues: https://github.com/Real-Dev-Squad/feature-flag-service/issues/69


Update NPM Dependencies

Notes
Ran npm update to update the dependencies and address the concerns brought by dependabot. Specifically, the following dependencies were updated:

follow-redirects updated to 1.14.9
json-schema updated to 0.4.0
jsprim updated to 1.4.2
nanoid updated to 3.3.1
sass-loader updated to 10.2.1
selfsigned updated to 1.10.14
url-parse updated to 1.5.10
json-schema updated to 0.4.0
jsprim updated to 1.4.2

Testing
I ran npm start to deploy a developer version of the site on my local machine. I was able to switch between the different versions of the site for each location, as well as type in the usernames. Anything that did not involve hitting the lambda backend was successful, as trying to hit the lambda results in CORS errors.

Until we implement #62 the React App needs to be manually built & the build artifacts need to be checked into cdk/visit/console/. Currently this PR updates the source, but won't impact the deployed website.


Official Gradle Plugins Support

Would you be able to put your plugin up on plugins.gradle.org? Instructions on how to do that are here: https://plugins.gradle.org/docs/submit. This makes it much easier to create a robot project with newer versions of Gradle. Instead of
buildscript {
  repositories {
    mavenCentral()
    maven {
        name = "GradleRIO"
        url = "http://dev.imjac.in/maven"
    }
  }
  dependencies {
    classpath group: 'jaci.openrio.gradle', name: 'GradleRIO', version: '+'         //Change this line if you wish to Update GradleRIO
  }
}
apply plugin: 'GradleRIO'

we could simply be able to do:
plugins {
    id: 'jaci.openrio.gradle.GradleRIO' version '# here'
}

I'll see what I can do tonight

Any progress on this? This would be really helpful.

I'll see what I can do when the next release rolls around. This may require a bit of changing on GradleRIO's own build system, as well as either uploading to both my personal server and the official plugins server, or adding some redirect trickery to maintain compatibility with existing projects.

Now that the 2016-17 season is coming up, it would be great to have this implemented for the build season; thanks for the great work!

I've decided to drop this idea for the time being, or at least until GradleRIO gets a major update. There's a few reasons for this, and I'll list them below:

Breaks compatibility. Running GradleRIO on plugins.gradle.org and pulling it from my person dev.imjac.in/maven repository will break every single project that depends on it. I could run this side by side, but managing two publishing targets just to save a few lines of a build.gradle file isn't worth it IMHO.
Breaks Toast Projects specifically. GradleRIO is published with two branches, vanilla and toast. The vanilla version is for regular WPILib projects, while the toast version changes some behaviour with WPILib linkages and build deploying to suit Toast projects. On my maven repo, this difference is given in the classifier to the project. Unfortunately plugins.gradle.org does not support this, and I don't believe there is a  way to publish a second plugin based on build artifacts (GradleRIO is built twice, changing the value of manifest attribute GradleRIO-Flavour between builds)
Moving GradleRIO to plugins.gradle.org means that its dependencies (i.e. NetworkDelegate) will have to be moved, too. This is a fairly minimal effort, but this is just a second instance of the first issue

I'll keep this idea incubating for future releases, at which point I may replace the GradleRIO versions on my own repo with a stub that fails a build and prints "we have moved" or something similar

This has been included with the new versions. Use plugin jaci.openrio.gradle.GradleRIO from now on


Notify Systemd About Device Runtime Status

Device runtime should make use of systemd notify feature: https://www.freedesktop.org/software/systemd/man/sd_notify.html.
READY=1 and STATUS=foo should be used as a starting point.
It should be also explored wether using systemd as an optional dependency.

Already merged here #30 .


Unable to build 0.7.2 for armv7

0.6.0 builds fine for armv7, but I am unable to build 0.7.2 for armv7 due to:
[  179s] error: failed to run custom build command for `tss-esapi-sys v0.1.1`
[  179s]
[  179s] Caused by:
[  179s]   process didn't exit successfully: `/home/abuild/rpmbuild/BUILD/parsec-0.7.2/target/release/build/tss-esapi-sys-2076e3c7eb1fcc79/build-script-build` (exit code: 101)
[  179s]   --- stderr
[  179s]   thread 'main' panicked at 'Compilation target (armv7-unknown-linux-gnueabihf) is not part of the supported targets (["x86_64-unknown-linux-gnu", "aarch64-unknown-linux-gnu", "armv7-unknown-linux-gnueabi", "arm-unknown-linux-gnueabi"]). Please compile with the "generate-bindings" feature or add support for your platform :)', /home/abuild/rpmbuild/BUILD/parsec-0.7.2/vendor/tss-esapi-sys/build.rs:34:13

Thanks for the report!
If you can modify features, you can compile adding the feature "tss-esapi/generate-bindings" to go over that bug.

Your immediate bug will be fixed with #381 (hopefully). It's a bit more tricky to add cross-compilation of the TPM provider as one needs to also cross-compile the TSS libraries. It will be looked at in #382.
The tss-esapi crate has its own cross-compilation tests in here.

That should be fixed in the latest main but feel free to say if not and we will re-open :)


issue 2460: use Generated annotation with CLASS retention

I added the @Generated annotation to the querydsl-core module because only the core and jpa modules are needed in an application using QueryDsl.
I also wanted to add <property name="illegalClasses" value="javax.annotation.Generated"/> to IllegalImport but I guess the version of checkstyle is to low because it is a documented property but failed to be accepted.
Fixes #2460
Fixes #2612
Fixes #2242

Not clear why that build fails on missing @Paramin Javadoc which was added in 2013

Hi @rob-valor ,
I want to integrate this patch, but I would like the transition as smooth as possible, as the latest releases have caused enough trouble for our users.
Do you see any way of making the used Generated annotation parameterizable so that the default annotation remains javax.annotation.Generated? (At least until a next major release, but hopefully we can integrate this sooner).

@jwgmeligmeyling Since this is the first time OSS (code) contribution for me and I changed a lot of files that I have to "undo", what is the best approach for the current pull request? Do I just delete my fork and start over again? (Don't know how Github and this pull request handles this). A rollback of this current change would pollute the git history, no?

Hey @rob-valor, thanks for the contribution. The PR will be squashed so the commit history is irrelevant. You can choose whichever option is most comfortable. :)

@idosal I have some questions:

Is there any objection to write the annotation as fully qualified (like @javax.annotation.Generated("..."))? This makes injection of class as String in the Serializereasier than having to parse the String for import and use simple class name as annotation on the class.
I would just add a boolean to the AptOptions to use the CLASS retained annotation and if not set use javax.annotation.Generated for java8 and earlier and javax.annotation.processing.Generated for java9 and newer (depending on which one can be loaded with a Class.forName). Is that ok?
about BeanSerializer, ExtendedBeanSerializer and GroovyBeanSerializer because they can be also instantiated in AbstractModule#get(Class, String):
I'm adding the annotation class as a fully qualified class name (String) because instantiation in that AbstractModule.get method does not support injecting a Class (it binds only instances of a specific class). Those 3 serializers seem to be instantiated with the default constructor. To support that annotation class to be injected in the serializer constructor I need a constructor with a String parameter. Now BeanSerializer and GroovyBeanSerializer already have an overloaded constructor with a String parameter javadocSuffix which doesn't seem to be used by the framework. I could add a constructor with 2 parameters and add the default value of javadocSuffix or propertyAnnotations (depending on which one used as 2nd parameter) as binding in CodegenModule#configure. Is that ok?

Hi @rob-valor , I don't have any objections to your suggestion. Perhaps the approach suggested in 3 will work for 2 as well (for consistency). All's fine!

I think this should be it. (but again with that javadoc failing :disappointed:)
There is however SpatialRefSys and QSpatialRefSys which have also the javax.annotation.Generated annotation. I'm not sure why its added to the querydsl source code but I think those should not be there.  Also it looks like these are added by BeanSerializer and MetaDataSerializer which have dynamic class name for annotation now.

Thanks @rob-valor , I'll have a look and integrate it ASAP.
I'll fix the Javadoc issues myself. Thats not a major issue.
There's no need to port this to the Groovy and Scala processors yet. Its obviously nice to have but these modules are much less frequently used.

No need to work on the comments. I am already integrating this in my java-11 support branch which will make it into the 5.x.x release.

To be clear: I don't have to take any action for these review remarks?

No you don't, I already addressed them. I'll push as soon as all the tests pass.


Enable low level function calls for different chains.

As of today developers find it difficult to interact with polkadot/api for low level calls like asset transfers between two accounts on different chains. If capi could create simple declarative wrapping functions over each/most low level apis then DX will drastically improve; even for new devs.
Attaching screenshot of a questions asked (about asset transfer and balance queries) in polkadot channel which supports this use case:

@jainkrati can you please elaborate on the problem? Not exactly sure what's meant by "low-level interactions" or why @polkadot/api would not service these interactions.

In scenarios where developer has launched their own tokens/assets on the parachain and want to transfer these tokens from account1 to account2 (as seen in the screenshots above), developers can benefit if Capi provides a utility to transfer these user created assets. The complexity of doing so using polkadot or cumulus can be abstracted out.

Ah, okay. What are the "low-level interactions" of which this pattern would be composed? Seems Westmint's assets pallet's transfer should do the trick? What's missing?

Yes, it should do the trick. I guess I wrongly used "low-level" interactions. I meant "basic asset" interactions

Gotcha. In that case, this should be covered. Not sure if we need this issue to represent any corresponding work. Want to mark this as closed?

Closing the issue.


[Marker.io] there is not muchspace between heading and nav bar

Steps to reproduce:

check the heading in header area and compare with figma

Actual result: space is not too much. it is les
Expected result: please improve this
refer the below actual  screenshot:

Reported by: vinod<EMAIL_ADDRESS>- Contact via Marker.io
Source URL: https://wf-b.stg.prezzee.com/en-us/prepaid-visa-card
Issue details: Open in Marker.io
Device typedesktopBrowserChrome <IP_ADDRESS>Screen Size1366 x 768OSWindows 10 (10.0.0)Viewport Size1366 x 641Pixel Ratio@1x

Attached files:
- image.png (276.5KB)

on tab ( landscape mode):  it is overlapping with nav
resolution: 1024768 (viewport: landscape: 1024665)
ipad 6th gen, safari
https://drive.google.com/file/d/1uhNhZMdsbXID2t-O8rtGhTQ0r7GrM4pe/view?usp=sharing

Still seeing the same behaviour on my tab(as mentioned in previous comment) and also the spacing is same on my laptop too.

still needs fixing on both tab and for desktop. can be observedon new staging too
https://stg.prezzee.com/business/m/en-us/prepaid-visa-card


Update release notes file path in auto release workflow

Description
Update release notes file path in auto release workflow
Issues Resolved
https://github.com/opensearch-project/cross-cluster-replication/pull/712
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

BWC and security test failing due to known issues.


cmake: copy liveviz headers

Fixes #2863.

Still doesn't work for me.

Is it still not finding liveViz.h ?

When building this branch, I get:
$ ls include/liveViz*
include/liveViz.decl.h  include/liveViz.h   include/liveViz3d.decl.h  include/liveVizPoll.decl.h
include/liveViz.def.h   include/liveViz0.h  include/liveViz3d.def.h   include/liveVizPoll.def.h

I get:
git branch

(HEAD detached at origin/cmake-liveviz)

./build ChaNGa netlrts-linux-x86_64 -j8 -O2
...
ls include/live*
include/liveViz3d.decl.h  include/liveViz.decl.h  include/liveVizPoll.decl.h
include/liveViz3d.def.h   include/liveViz.def.h   include/liveVizPoll.def.h

@trquinn Thanks for the update. Could you try again with the updated branch?

Now "CkCache.h" is not found (perhaps should have checked this earlier.
Also: now the AMPI library is being built, which is not useful for ChaNGa, and generates lots of warnings.

There are still a lot of messages like:
pi-io/mpiu_external32.c:117:9: warning: ‘MPI_Unpack_external’ is deprecated: currently unimplemented in AMPI [-Wdeprecated-declarations]
  117 |         mpi_errno = MPI_Unpack_external("external32", tmp_buf, bytes,
      |         ^~~~~~~~~
In file included from ./adio/include/adio.h:72,
                 from mpi-io/mpioimpl.h:15,
                 from mpi-io/mpiu_external32.c:6:
/home1/00333/tg456090/src/charm/ucx-linux-x86_64-smp/bin/../include/ampi_functions.h:651:23: note: declared here
  651 | AMPI_FUNC_NOIMPL(int, MPI_Unpack_external, const char datarep[], const void *inbuf, MPI_Aint insize, MPI_Aint *position, void *outbuf, int outcount, MPI_Datatype datatype)
      |                       ^~~~~~~~~~~~~~~~~~~
/home1/00333/tg456090/src/charm/ucx-linux-x86_64-smp/bin/../include/ampi/mpi.h:30:27: note: in definition of macro ‘AMPI_FUNCPTR’
   30 |   #define AMPI_FUNCPTR(x) x
      |                           ^
/home1/00333/tg456090/src/charm/ucx-linux-x86_64-smp/bin/../include/ampi/mpi.h:1388:19: note: in expansion of macro ‘AMPI_API_DEF’
 1388 | #define AMPI_FUNC AMPI_API_DEF
      |                   ^~~~~~~~~~~~
/home1/00333/tg456090/src/charm/ucx-linux-x86_64-smp/bin/../include/ampi/mpi.h:1389:45: note: in expansion of macro ‘AMPI_FUNC’
 1389 | #define AMPI_FUNC_NOIMPL AMPI_UNIMPLEMENTED AMPI_FUNC
      |                                             ^~~~~~~~~
/home1/00333/tg456090/src/charm/ucx-linux-x86_64-smp/bin/../include/ampi_functions.h:651:1: note: in expansion of macro ‘AMPI_FUNC_NOIMPL’
  651 | AMPI_FUNC_NOIMPL(int, MPI_Unpack_external, const char datarep[], const void *inbuf, MPI_Aint insize, MPI_Aint *position, void *outbuf, int outcount, MPI_Datatype datatype)
      | ^~~~~~~~~~~~~~~~
[100%] No install step for 'romio'
[100%] Completed 'romio'
[100%] Built target romio

I've now got an error from another recent change:
../charm/bin/../include/conv-autoconfig.h:4:23: error: too many decimal points in number
    4 | #define CHARM_VERSION 6.10.1
      |                       ^~~~~~
DataManager.h:16:5: note: in expansion of macro ‘CHARM_VERSION’
   16 | #if CHARM_VERSION > 60401 && CMK_BALANCED_INJECTION_API
      |     ^~~~~~~~~~~~~
../charm/bin/../include/conv-autoconfig.h:4:23: error: too many decimal points in number
    4 | #define CHARM_VERSION 6.10.1
      |                       ^~~~~~
DataManager.h:280:5: note: in expansion of macro ‘CHARM_VERSION’
  280 | #if CHARM_VERSION > 60401 && CMK_BALANCED_INJECTION_API
      |     ^~~~~~~~~~~~~

There are still a lot of messages like:

Thank you @trquinn for the report. With the current version of this branch, I'm able to build ChaNGa. The AMPI warnings are still there, but I'll address those in a different PR.

It now builds for me as well.
However, there is another version issue, when I run ChaNGa, I get:
Charm++> Running in SMP mode: 1 processes, 1 worker threads (PEs) + 1 comm threads per process, 1 PEs total
Charm++> The comm. thread both sends and receives messages
Converse/Charm++ Commit ID: v61001

I used to get a git hash in the Commit ID line, which is quite important for reproducing results (and tracking bugs!).  Can we get that back?

It now builds for me as well.
However, there is another version issue, when I run ChaNGa, I get:
Charm++> Running in SMP mode: 1 processes, 1 worker threads (PEs) + 1 comm threads per process, 1 PEs total
Charm++> The comm. thread both sends and receives messages
Converse/Charm++ Commit ID: v61001

I used to get a git hash in the Commit ID line, which is quite important for reproducing results (and tracking bugs!). Can we get that back?

Agreed, we need to get this back. Furthermore, the current display seems misleading, I think it should be using git describe or something of that ilk so that it uses the most recent tag to reflect that we are currently on something like "v6.11.0-devel-272-g800278a9d".

Version number should be fixed now.

This now looks good.


fix(bundles): Use ESM tslib build for the browser bundles

tslib is weird. The esbuild version that YouTube.js uses, isn't able to automatically pick the correct tslib build to bundle into the browser bundles, so it uses the commonjs one, which isn't treeshakable. This makes it pick the correct one, reducing the size of the bundles:

Bundle
Before
After

browser.js
893.3kb
875.8kb

browser.min.js
479.6kb
471.7kb

More recent versions of esbuild added support for tslib's weirdness, however they now aggressively preserve comments while bundling (previously they only preserved webpack's magic comments), so that tools like vite can add magic comments without esbuild stripping them. Unfortunately that means that it blows up the sizes of the node.cjs and browser.js bundles, because newer esbuild versions keep all of the jsdoc comments 😔. The browser.min.js bundle isn't affected by that, as part of the mimification process is striping comments.
Doesn't look like there is a sensible way to disable that behaviour.

Very strange behavior indeed. Thanks for the PR.


Performance impact of out-of-process for AKS-hosted function apps

What is the performance impact of the new out-of-process/GRPC based approach for function aps hosted in AKS? I assume the performance will be inferior to the in-proc .net core 3.1 azure functions runtime, or?

how will the overhead of the underlying azure function host vs your app be billed? (when you're paying per second, per MB), starting up functions, then starting a second out-of process host.

how will the overhead of the underlying azure function host vs your app be billed? (when you're paying per second, per MB), starting up functions, then starting a second out-of process host.


Shortcut for toggling editing mode

It would be so easy if there is a toggle short-cut for switching editing and preview mode
Ctrl + E, for example, will make switching easy

Control alt J already exists for togging edit and preview mode.


tsc errors

I am using latest - thanks for the quick response. However, for some reason tsc is throwing errors.
I added an exclude section to tsconfig:
"exclude": [         "node_modules"     ]
'npm run tsc' produces the following:
node_modules/ng2-bootstrap/components/buttons/button-checkbox.directive.d.ts(14,22): error TS1005: '=' expected.
node_modules/ng2-bootstrap/components/buttons/button-checkbox.directive.d.ts(15,22): error TS1005: '=' expected.
node_modules/ng2-bootstrap/components/buttons/button-radio.directive.d.ts(10,14): error TS1005: '=' expected.
node_modules/ng2-bootstrap/components/buttons/button-radio.directive.d.ts(10,22): error TS1005: ';' expected.
node_modules/ng2-bootstrap/components/dropdown/dropdown-toggle.directive.d.ts(11,14): error TS1005: '=' expected.
node_modules/ng2-bootstrap/components/dropdown/dropdown-toggle.directive.d.ts(11,20): error TS1005: ';' expected.
node_modules/ng2-bootstrap/components/modal/modal.component.d.ts(14,14): error TS1005: '=' expected.
node_modules/ng2-bootstrap/components/modal/modal.component.d.ts(14,21): error TS1005: ';' expected.
node_modules/ng2-bootstrap/components/modal/modal.component.d.ts(22,22): error TS1005: '=' expected.
node_modules/ng2-bootstrap/components/position.d.ts(29,22): error TS1005: '=' expected.
node_modules/ng2-bootstrap/components/position.d.ts(30,22): error TS1005: '=' expected.
node_modules/ng2-bootstrap/components/tooltip/tooltip-container.component.d.ts(21,14): error TS1005: '=' expected.
node_modules/ng2-bootstrap/components/tooltip/tooltip-container.component.d.ts(21,24): error TS1005: ';' expected.
node_modules/ng2-bootstrap/components/typeahead/typeahead-container.component.d.ts(18,14): error TS1005: '=' expected.
node_modules/ng2-bootstrap/components/typeahead/typeahead-container.component.d.ts(18,26): error TS1005: ';' expected.
node_modules/ng2-bootstrap/components/typeahead/typeahead-container.component.d.ts(18,44): error TS1005: '(' expected.
node_modules/ng2-bootstrap/components/typeahead/typeahead.directive.d.ts(46,14): error TS1005: '=' expected.
node_modules/ng2-bootstrap/components/typeahead/typeahead.directive.d.ts(46,21): error TS1005: ';' expected.
node_modules/ng2-bootstrap/components/typeahead/typeahead.directive.d.ts(46,33): error TS1005: '(' expected.

Hm, try to add "skip lib check" option to tsc config

Having the same problem, adding skipLibCheck did not solve the problem. Seems to be a problem with anything marked "readonly".

Are you using gulp? If so you should explicitly pass typescript as option
Check #982

using visual studio 2015 and Microsoft.TypeScript.Compiler v1.8.11

You need ts 2, 1.* will not work
ng2 is using ts2, so I had to use it too
On Fri, Sep 16, 2016, 19:03 pj-martins<EMAIL_ADDRESS>wrote:

using visual studio 2015 and Microsoft.TypeScript.Compiler v1.8.11
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/valor-software/ng2-bootstrap/issues/989#issuecomment-247639244,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDk47i0tGtcR5JTb9hNHBCi61qtMMk6ks5qqr1mgaJpZM4J_A0j
.

here's what I have:
package.json
"devDependencies": {
"concurrently": "^2.2.0",
"lite-server": "^2.2.2",
"typescript": "^2.0.2",
"typings": "^1.3.2"
}
packages.config

but still no luck

https://blogs.msdn.microsoft.com/typescript/2016/07/11/announcing-typescript-2-0-beta/
You guys need to manually install typescript 2

I am using VS Code + TSC Version 2.0.0. I tried again to compile but am getting the same error.

after installing 2, opening up the project file in notepad and replacing
<TypeScriptToolsVersion>1.8</TypeScriptToolsVersion>
with
<TypeScriptToolsVersion>2.0</TypeScriptToolsVersion>
did the trick

For now I think the error went away. Had to remove node_modules, re-install everything including tsc. Now I have other growing pains upgrading to 2.0.0. Fingers crossed.

Good luck :)
On Fri, Sep 16, 2016, 20:29 Kai Langlie<EMAIL_ADDRESS>wrote:

For now I think the error went away. Had to remove node_modules,
re-install everything including tsc. Now I have other growing pains
upgrading to 2.0.0. Fingers crossed.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/valor-software/ng2-bootstrap/issues/989#issuecomment-247659460,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDk4wwUS47xgF1uSPnJPj6p54NzUoUcks5qqtIBgaJpZM4J_A0j
.

Well all of the above does not describe my world.  I get the same error and I am under webpack.  So stuff about tsc explicitly doesn't make a lot of sense to me.  My package.json says I am at typescript "2.0.3".  It is not a good story when module by module we have these worries.  BTW why does typings get used for this now at all?   It is my understanding that in later versions of angular (I am at 2.4.4) that some of this went away.

With ng v2 you need ts at least 2.0.10
With v4+ ts 2.1+


[Focus: Customer/Developer] Add placeholder document for business date

Ref:

Write new documentation on transaction idempotency and business and effective date configuration
Business & Effective Date Separation - https://github.com/apache/fineract/pull/2358/files
https://mifosforge.jira.com/wiki/spaces/P/pages/3079733251/Introducing+Business+Date+into+Fineract+community+version
https://github.com/openMF/mifos-documentation/issues/14

cc @edcable.
Description
Describe the changes made and why they were made.
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[ ] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[ ] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[ ] Create/update unit or integration tests for verifying the changes made.

[ ] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[ ] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes

[ ] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

@tapaswenipathak are there any plans to make this PR ready? Do you need help with it?

plans: yes. soon, this week most probably, a couple of more or a bunch.
cc @edcable.
On Monday, August 22, 2022, Arnold Gálovics @.***>
wrote:

@tapaswenipathak https://github.com/tapaswenipathak are there any plans
to make this PR ready? Do you need help with it?
—
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/2490#issuecomment-1222338156,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA7TVISU2HVWDJ2NUB2LGDDV2N3ZHANCNFSM554GBPRQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@tapaswenipathak would be great if you could format the PR title according to this pattern: "FINERACT-XXXX: Title of Jira ticket". If there's no Jira ticket yet and you are unable to create one yourself then please contact me, I'll help out. Thanks.

sure, but i dont't think any jira ticket(s) exist, can you sync w/ Ed on
slack? please loop me in, if there is anything i can help w/.
On Tuesday, August 23, 2022, Aleksandar Vidakovic @.***>
wrote:

@tapaswenipathak https://github.com/tapaswenipathak would be great if
you could format the PR title according to this pattern: "FINERACT-XXXX:
Title of Jira ticket". If there's no Jira ticket yet and you are unable to
create one yourself then please contact me, I'll help out. Thanks.
—
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/2490#issuecomment-1223997174,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA7TVIWITWO6ZXVFQO4WBZDV2S7MPANCNFSM554GBPRQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

looped in both of you in the email. not sure if there should be one,
multiple or no jira ticket.
On Tuesday, August 23, 2022, Tapasweni Pathak @.***>
wrote:

sure, but i dont't think any jira ticket(s) exist, can you sync w/ Ed on
slack? please loop me in, if there is anything i can help w/.
On Tuesday, August 23, 2022, Aleksandar Vidakovic @.***>
wrote:

@tapaswenipathak https://github.com/tapaswenipathak would be great if
you could format the PR title according to this pattern: "FINERACT-XXXX:
Title of Jira ticket". If there's no Jira ticket yet and you are unable
to
create one yourself then please contact me, I'll help out. Thanks.
—
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/2490#issuecomment-1223997174,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/
AA7TVIWITWO6ZXVFQO4WBZDV2S7MPANCNFSM554GBPRQ>
.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/2490#issuecomment-1224114646,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA7TVIV4DOAABFFUYYTQV2TV2TKCTANCNFSM554GBPRQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Lost contact or Timeout with empty error

After a while without navigate into the UI and come back, Every click on existing app or others don't provides according change. It seams that the UI have lost the connection with docker (swarm in my case).
If I make a F5 refresh I've got an empty error :

After that it seams to recover with the swarm connection

do you have any log message in the docker-compose-ui container logs?

can't reproduce from now I close it


Comment update

Updated comment to index instead of table

@all-contributors please add @rajscode for code

Thank you! Good catch.


Can't start ghost

Issue Summary
Can't start ghost after I updated it
Steps to Reproduce

Update it to latest version
Run ghost start, it will get the error

Technical details:

Ghost Version: latest
Node Version: v6.9.0
Browser/OS: macOS High Serria
Database: sqlite

More infos
Debug Information:
    Node Version: v6.9.0
    Ghost-CLI Version: 1.1.1
    Environment: production
    Command: 'ghost start'
Message: An error occurred.
Stack: Error: An error occurred.
    at ChildProcess.cp.on (/usr/local/lib/node_modules/ghost-cli/lib/utils/local-process.js:55:35)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at process.nextTick (internal/child_process.js:744:12)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)

Hi @hzb
We're sorry to hear you're having problems, but ask that you do not use our GitHub repo for support. Please read our support guide. You can always use our slack community - https://slack.ghost.org, if you're not able to find the answer in our documentation - https://docs.ghost.org.
I'm closing this issue here, as it - if it turns out to be an issue - needs to be opened in the Ghost-CLI repository, but kindly ask you to first seek help in the above mentioned Slack community.

@hzb don't normally do this in GitHub, but this sounds like a variation of https://docs.ghost.org/docs/troubleshooting#section-task-execute-is-not-a-function
Essentially, you need to update Ghost-CLI before you can update Ghost.

@ErisDS Thanks, can I ask how to update Ghost-CLI? I google it, but I can't find the answer.

@hzb the link I provided has a link to the upgrade docs.

@ErisDS got it, thank you.

@ErisDS BTW, can i submit issues or bugs here in Github repo?

GitHub is for reporting bugs, yes :)


No module named 'dmlc_tracker'

Description
pip install mxnet-cu91 (or mxnet-cu90) does not install dmlc-tracker.
Running distributed training after pip install gives this error
ubuntu@ip-172-31-33-187:~$ mxnet/tools/launch.py -n 2 -s 2 --launcher local python cifar10_dist.py
Can't load dmlc_tracker package.  Perhaps you need to run
    git submodule update --init --recursive
Traceback (most recent call last):
  File "mxnet/tools/launch.py", line 128, in <module>
    main()
  File "mxnet/tools/launch.py", line 96, in main
    args = dmlc_opts(args)
  File "mxnet/tools/launch.py", line 48, in dmlc_opts
    from dmlc_tracker import opts
ImportError: No module named dmlc_tracker

The error goes away if dmlc-core is built separately and PYTHONPATH is set correctly.
After pip install mxnet-cu, shouldn't users be able to run distributed training without any more installations?
Environment info: Ubuntu p2 instance
Package used (Python/R/Scala/Julia):
1.2
Steps to reproduce
(Paste the commands you ran that produced the error.)

Create an instance with 4 or more gpus.
wget https://raw.githubusercontent.com/indhub/mxnet/e5b89cf9d7c35ac749ed14b54c0faa6dfffa15ef/example/distributed_training/cifar10_dist.py
mxnet/tools/launch.py -n 2 -s 2 --launcher local python cifar10_dist.py

Thanks @indhub for submitting the issue!

dmlc_tracker will be included in nightly builds starting from tonight.

@szha is the issue resolved? Do we have tests for proper install?

yes, the scripts are included. since the module is pure python, I manually validated their existence in site-packages after installing.


Orange Brand design tokens to customize v5

Ensure to properly use Orange Brand design tokens, through the new Utility API as much as possible:

[ ] colors
[ ] fonts
[ ] type scale
[ ] spacings
[ ] borders
[ ] etc.

Pay attention to:

[ ] Helvetica Neue (!)
[ ] locking contrasts on color and backround utilities

Using $tehem-colors so to double-check:

alerts
buttons
list-group
colored links


Terraform Fmt failing on .tf files

Description
Getting this error message when beautifying a .tf file:
"Only .tf and .tfvars files can be processed with terraform fmt"
Happening for all my .tf files.
Steps to Reproduce

Add code to Atom editor
Run command Atom Beautify: Beautify Editor
Error is displayed

Package version: 0.33.4
Atom version: 1.37.0
OSX version: 10.14.5
Beatify on other file types seems to work fine.
Stack trace
Error:
Error: Only .tf and .tfvars files can be processed with terraform fmt

    at /Users/username/.atom/packages/atom-beautify/src/beautifiers/executable.coffee:183:23
    at tryCatcher (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:694:18)
    at _drainQueueStep (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/async.js:138:12)
    at _drainQueue (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/async.js:131:9)
    at Async._drainQueues (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/async.js:147:5)
    at Async.drainQueues (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/async.js:17:14)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)

Checklist
I have:

[x] Tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[x] Reloaded (or restarted) Atom to ensure it is not a caching issue
[x] Searched through existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
so I know this is not a duplicate issue
[x] Filled out the Input, Expected, and Actual sections above or have edited/removed them in a way that fully describes the issue.
[ ] Generated debugging information by executing Atom Beautify: Help Debug Editor command in Atom and added link for debug.md Gist to this issue

Same for me on terraform 0.12

I have the same issue.
Package version: 0.33.4
Atom version: 1.40.1 x64
OSX version: 10.13.6
Also failed beautifying my terraform code.

Severity 	Provider 	Description	Line
 Error: Only .tf and .tfvars files can be processed with terraform fmt

Error: Only .tf and .tfvars files can be processed with terraform fmt

Hide Stack Trace
Error:
Error: Only .tf and .tfvars files can be processed with terraform fmt

    at /Users/username/.atom/packages/atom-beautify/src/beautifiers/executable.coffee:183:23
    at tryCatcher (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:517:31)
    at Promise._settlePromise (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:574:18)
    at Promise._settlePromise0 (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:619:10)
    at Promise._settlePromises (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:699:18)
    at _drainQueueStep (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/async.js:138:12)
    at _drainQueue (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/async.js:131:9)
    at Async._drainQueues (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/async.js:147:5)
    at Async.drainQueues (/Users/username/.atom/packages/atom-beautify/node_modules/bluebird/js/release/async.js:17:14)
    at run (/Users/username/.atom/packages/git-plus/node_modules/core-js/modules/es6.promise.js:75:22)
    at /Users/username/.atom/packages/git-plus/node_modules/core-js/modules/es6.promise.js:92:30
    at flush (/Users/username/.atom/packages/git-plus/node_modules/core-js/modules/_microtask.js:18:9)
    at process._tickCallback (internal/process/next_tick.js:61:11)

+1

+1

+1

Is there any update on this to be fixed?

+1

+1

+1

+1

Is there any solution for this problem by now?

+1

Sounds like he may be working on another project.
I've switched to Visual Studio Code and will likely stay. Worth giving a go.

FWIW you can apply the fix from the PR yourself by editing %HOMEPATH%\.atom\packages\atom-beautify\src\beautifiers\terraformfmt.coffee
  beautify: (text, language, options) ->
    @exe("terraform").run([
      "fmt"
-      tempFile = @tempFile("input", text)
+      tempFile = @tempFile("input", text, ".tf")
      ])

Might I also highly recommend you add -no-color to the args to make the lint messages more readable. (The garbage chars are from Terraform trying add pretty shell colors)
  beautify: (text, language, options) ->
    @exe("terraform").run([
      "fmt"
+     "-no-color"
      tempFile = @tempFile("input", text, ".tf")
      ])

FWIW you can apply the fix from the PR yourself by editing %HOMEPATH%\.atom\packages\atom-beautify\src\beautifiers\terraformfmt.coffee
  beautify: (text, language, options) ->
    @exe("terraform").run([
      "fmt"
-      tempFile = @tempFile("input", text)
+      tempFile = @tempFile("input", text, ".tf")
      ])

Both this and your "-no-color" tip worked great for me. Thanks. Maybe it's time to submit a PR.

@lmasaya It already is actually, just needs a merge https://github.com/Glavin001/atom-beautify/pull/2351/files

Minus the no-color flag, but somehow I think this project is abandoned now.


fix(core): Add stack to detect circular ref in object

Related: #1619

:tada: This PR is included in version 6.75.10 :tada:
The release is available on:

v6.75.10
GitHub release

Your semantic-release bot :package::rocket:


Sync templates to apify/actor-templates on update

It might be enough to just generate .zip files of the generated templates in a github action in this repo and change the manifest in actor-templates to reference that.

@janbuchar
I gave that a shot and came up with this approach: gist
Let me know what you think!

Hi @Telomelonia, thanks for the snippet, but the transformation between the template formats will be significantly more complex. Also resolving this is not very high on our priority list, so it might be a better idea for you to pick one of the "hacktoberfest" issues.


[VTP-1835] Fix empty token value stored in github actionoutputs

This patch fixes incorrectly stored CDA token in a special outputs storage.
Previously token was set as a secret and the stored in outputs. This resulted in an empty value stored.
Solution: store token in outputs first and then set it as a secret.
See example in the comment below.

great catch! 👏🏻 👏🏻 👏🏻
@slash3b I think you'll want to increment the version number, no?

oh my 🤦 You are right! thank you, totally forgot


Not all published ports are getting exposed

This could be environment specific, and it has been very reproducible in that environment.  I was unable to reproduce on a fresh installation of Rancher.
Issue:
Deploying a stack The published ports are not exposed on the host. Looking at the iptables rules the first port is exposed, but the second is not. Creating a single container with a published port causes all of the ports to be exposed and functional.

I believe I have this problem too, I publish port 80 as 8080:
![rancher]
(https://beemapp.s3-eu-west-1.amazonaws.com/5a9df9dc-4df2-43b3-8f2d-a59877020227.jpg)
But on docker ps I don't see the port translation:
![docker ps]
(https://beemapp.s3-eu-west-1.amazonaws.com/1ae657e4-eecd-459e-be2c-5546595d7886.jpg)
Strange thing is I can access to it from outside the Docker host:
admin@stream-2:~$ curl stream-1.*****.com = OK
admin@stream-1:~$ curl stream-1.*****.com = Connection refused

It looks like Rancher didn't pass the port settings to Docker.

@ebuildy, rancher manages the ports, and they will not show up in docker. In order to verify you need to do iptables -L -t nat and you should see the ports being handled there.

@ebuildy Different issue...
The public ports are never show in docker ps because they can be dynamically changed in Rancher but we can't change the output of Docker to match.  So the port is exposed, but your issue is that "Hairpin NAT" is not currently supported.
This is where you're making a request from the host to the public IP of itself back to itself.  There's just not a rule in iptables to handle that.

Haaa ok, sorry for bother you for that, didn't check with the right iptables command..
So the Rancher agent is in charge of managing this on each host?
You said they can be dynamically changed in Rancher, how?
Thanks you very much,

If using the "managed" networking (which is the default), yes.  You can click the edit action on a container and change the public port bound to each container port.

Sometimes ports are not well exposed, I have to restart container to expose all ports:
![]
(http://b3.ms/raNnPVd89bXP)
Here I have the same stacks running on 2 hosts, port 843 is not exposed on the second, if I restart the container, the port is exposed fine.
Note: I have this problem after cloned service, delete original and start new one.

@cloudnautique Do you have a reproducible failing test case?  If so I could quickly fix this I'm sure.

@ebuildy I have the same issue, when I restart the container for the first time both ports are exposed fine, but when a I restart again, only the first port is exposed.

@ebuildy This happens consistently? Is the container part of a service? Does it have a sidekick? Do you have a compose yaml that you'd be able to share so that we could try to reproduce?

Yes it's happen all the time I remove then create new containers of a service. Then if I restart new created container, I can see the ports opened.

I am having exactly this problem and very reproducible. Only one port of any container is ever exposed.
Docker hosts are CentOS-7 and are running Docker 1.7.1, build 3043001/1.7.1 if that helps.

@sangeethah can we try to reproduce this in-house?

The problem with this issue is that there is plenty of reasons why a port might not be accessible due to environmental issues (such has bad security group configuration) or user error.  To really proceed forward on this issue we need some reproducible tests case.

I don't disagree. The issue I saw had incomplete iptables rules. When doing an iptables -L -t nat the port was missing. Adding another container forced a config load and things worked. I haven't seen it since reporting the issue.

This was completely reproducible on my setup. Just to be annoying though I tried several times today and all is working as it should. I did attempt to upgrade from Rancher 0.35 to 0.39 (with errors as mentioned in the forum) so maybe that updated something on the hosts.

This might be related to https://github.com/rancher/rancher/issues/1730

Back to this one again. Upgraded to Docker 1.8.3 and now on Rancher 0.42 all running on CentOS 7. This is still very reproducible to me.  Using stack imported from docker-compose.yml (https://gist.github.com/jest/7ffd79833865b10d2909) I can see that port 10022 is being published, while 10080 is not.
Chain CATTLE_PREROUTING (1 references)
target     prot opt source               destination
DNAT       udp  --  <IP_ADDRESS>/0            <IP_ADDRESS>/0            ADDRTYPE match dst-type LOCAL udp dpt:4500 to:<IP_ADDRESS>:4500
DNAT       udp  --  <IP_ADDRESS>/0            <IP_ADDRESS>/0            ADDRTYPE match dst-type LOCAL udp dpt:500 to:<IP_ADDRESS>:500
DNAT       tcp  --  <IP_ADDRESS>/0            <IP_ADDRESS>/0            ADDRTYPE match dst-type LOCAL tcp dpt:10022 to:<IP_ADDRESS>:22

The UI shows both 10022 and 10080 as published.
Rancher v0.42, Docker 1.8.3.

I never  see  this bug fixed, it happens sometimes when i remove /
re-create containers.
UI says no  error but ports are not mapped.
Le 27 oct. 2015 5:19 PM, "Przemek Wesołek"<EMAIL_ADDRESS>a
écrit :

Same for me. Using stack imported from docker-compose.yml (
https://gist.github.com/jest/7ffd79833865b10d2909) I can see that port
10022 is being published, while 10080 is not.
Chain CATTLE_PREROUTING (1 references)
target     prot opt source               destination
DNAT       udp  --  <IP_ADDRESS>/0            <IP_ADDRESS>/0            ADDRTYPE match dst-type LOCAL udp dpt:4500 to:<IP_ADDRESS>:4500
DNAT       udp  --  <IP_ADDRESS>/0            <IP_ADDRESS>/0            ADDRTYPE match dst-type LOCAL udp dpt:500 to:<IP_ADDRESS>:500
DNAT       tcp  --  <IP_ADDRESS>/0            <IP_ADDRESS>/0            ADDRTYPE match dst-type LOCAL tcp dpt:10022 to:<IP_ADDRESS>:22
The UI shows both 10022 and 10080 as published.
Rancher v0.42, Docker 1.8.3.
—
Reply to this email directly or view it on GitHub
https://github.com/rancher/rancher/issues/1898#issuecomment-151556279.

Removing and re-creating container doesn't help (at least not in last 5 times I tried)

You have to restart it, this will  run the  Rancher networking process at
the  end.
Le 28 oct. 2015 9:44 AM, "Przemek Wesołek"<EMAIL_ADDRESS>a
écrit :

Removing and re-creating container doesn't help (at least not in last 5
times I tried)
—
Reply to this email directly or view it on GitHub
https://github.com/rancher/rancher/issues/1898#issuecomment-151767270.

Restarting doesn't always work. Some ports may still not be connected after the restart. In any case that's not a workable option as we're trying to do automated deployment and scaling so there isn't always going to be someone there,

Absolutely agree  , this makes impossible automatic deploy.
Also i dont like  the  fact that Rancher manages ports whereas Docker can
do that very  well.
Le 28 oct. 2015 11:00 AM, "kevin-thorpe"<EMAIL_ADDRESS>a
écrit :

Restarting doesn't always work. Some ports may still not be connected
after the restart. In any case that's not a workable option as we're trying
to do automated deployment and scaling so there isn't always going to be
someone there,
—
Reply to this email directly or view it on GitHub
https://github.com/rancher/rancher/issues/1898#issuecomment-151787128.

Try adding another container to the host. It sounds odd, but the entire network config is supposed to be reloaded.

I'm so sorry this hasn't been fixed. I will resolve this.  Don't give up on me yet 🙏
The reason we manage the ports and not docker is that docker can't dynamically change the port mapping.  If they could we wouldn't do this.
I've misread this issue in the past.  I didn't realize the issue was related to multiple ports.  That gives me something to work with.
Again, I'm sorry this has taken so long to resolve.

@cloudnautique was able to reproduce this for me.  I'll get a fix in, probably won't make it for v0.44 but for sure v0.45.

Great, at least we have a timescale now. The unreproducible ones are always
annoying.
On 28 October 2015 at 17:39, Darren Shepherd<EMAIL_ADDRESS>wrote:

@cloudnautique https://github.com/cloudnautique was able to reproduce
this for me. I'll get a fix in, probably won't make it for v0.44 but for
sure v0.45.
—
Reply to this email directly or view it on GitHub
https://github.com/rancher/rancher/issues/1898#issuecomment-151922939.

I'm having the same issue here, note that only one port is mapped on iptables the rest isn't mapping.

From earlier correspondence Darren now can reproduce and is aiming to fix
by 0.45
On 29 Oct 2015 07:34, "Mohammad Ali Alfarra"<EMAIL_ADDRESS>wrote:

I'm having the same issue here, note that only one port is mapped on
iptables the rest isn't mapping.
—
Reply to this email directly or view it on GitHub
https://github.com/rancher/rancher/issues/1898#issuecomment-152102767.

Tested with latest build from master - Nov 13
Created a service with 11 exposed ports.
Once the service is activated and started , we see all 11 exposed ports being programmed in the iptables of the host. Verified that all these ports are accessible.
Fix will be made available in the next release.

Thank you.


Doesn't work out of the box, getting some HTTP 500 errors

Installed the extension but can't get it to work

Can you share me the screenshot please ?

I have same results

I think there might be issue with XSD. Is it possible for you to share me the one ?

Sure, I'm trying to create this form sdscom-xml.zip

@hasirci declaration of the base type eSDScom:BaseExposureControlPersonalProtection is missing.
'Undefined complexType 'http://www.esdscom.eu/eSDScom:BaseExposureControlPersonalProtection' is used as a base for complex type extension.'
<xs:complexContent>
			<xs:extension base="eSDScom:BaseExposureControlPersonalProtection"> </xs:extension>
</xs:complexContent>

I have to close this issue as it is the XSD issue.


Forward to new dashboard

When a user goes straight to login.cloud.gov, they will be presented with a page with two buttons: Deck and Invite users after they login. The "Deck" button should instead point to the new dashboard
Acceptance criteria:

[ ] The icon for the deck shoudl be changed to an image of a dashboard (posted in comments)
[ ] The text for the deck icon should be "dashboard"
[ ] The link for the icon should go to dashboard.cloud.gov.

Here's the image that has to be replaced, it should be the right size:

Here's were the data for that page needs to be switched: https://github.com/18F/cg-deploy-cf/blob/636bd3c7b2c94e94716bcff2c8be236b21452267/cf-properties.yml#L310

Currently blocked on getting access to upload the S3 image.

upload: ./dae8a1c4-4828-11e6-982e-45399af2767d.jpg to s3://18f-cloud-gov/deck.jpg

We concluded that I should add the image to the dashboard at an accessible URL and then update the url for it in the cf-properties.yml file.

This is currently blocked by not being able to deploy cg-deploy-cf. I've asked the Atlas team to deploy it but it hasn't happened yet.


Bump versions

bump framework and identity-apps-core versions

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7839406328

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7839406328
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7840155283

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7840155283
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7840190078

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7840190078
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7840201037

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7840201037
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7841625981

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7841625981
Status: failure

https://github.com/wso2/product-is/pull/19476


Add Linea zk Chain

Background
Any information that gives more context as to why this task exists, and why it matters. This might include: links to discussions, documentation, or other Jira issues / tasks
Linked Issues & Documentation

List of linked issues, external links, etc

Definition Of Done
Describes in 1-2 sentences what the output of the Task is, so that it can be verified by another team member easily. “Feature X is implemented as described and can be verified by using it”
Tasks

[ ] Task 1
[ ] Task 2
[ ] Task 3

All tasks in the epic are completed


Missing type annotation for T even when return type is specified

I want to define a wrapper function which takes a generic input T and wraps it in an object. All return types are defined and it also works, if the returned structure is simply T. But returning a new object which contains T does not work. I wouldn't know where to add another return type?
Is it possible to get the following to typecheck while using a generic wrapper function?
/* @flow */

declare function id<T>(fn: T): T;
declare function wrap<T>(fn: T): {fn: T};

export const a = id(3); // works
export const b = wrap(3); // does not work

https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVATApgYxgQwCcswoBXAOxwBcBLOCsWjAHgBUA+ACigoC4wbAJQC2Abky4CxUpRr1GCQvgAO7br1EiwAb02CAvhNRYAHiriFqYHAwDO1-GAC8TDFwDMQsWGDAwCJYA1nYm5pbWthQOYABGLgHKKp7evv4YcFh2YBRw1oGEQUA

By the way, it works without the export in front of the const for whatever reason. Being explicit happens to work too, as in
export const b = wrap<number>(3);

My general understanding is that flow's type inference at module borders is minimalistic to reduce overall performance overhead. That's why it works without the export token or with explicit typing the exported variable.
I know this limitation exists for cases, such as functions, for which return types have to be annotated explicitly. Apparently, it's also the case when exporting variables which are the return value of type-parameterized functions. So, maybe this is not an issue in the end.

The issue here is that wrap uses T in an invariant position. If you mark fn as covariant with + the issue goes away.

My general understanding is that flow's type inference at module borders is minimalistic to reduce overall performance overhead. That's why it works without the export token or with explicit typing the exported variable.

Yep! That's right. Right now we ask for annotations on any types used in invariant or contravariant positions that are reachable through exports. id only used T is a covariant position, which is why we did not complain.

Awesome, that's exactly the kind of information I was looking for. If the flow error contained that hint, it would be even better, of course.
Thank you, @jbrown215!

@philippotto I've done some work recently to try to improve this error message a bit. Do you have recommendations for phrasing the covariance in a concise and clear way? I didn't explain why the annotation was required because I find that variance is usually a subject that most people don't ever really learn. Also, these annotations can be super deep down in the structure of the type, so working out exactly how they are invariant or contravariant is also not always clear just by a loose inspection.
If you have recommendations for rephrasing I'll definitely put up a diff to run it by the team.

@philippotto I've done some work recently to try to improve this error message a bit. Do you have recommendations for phrasing the covariance in a concise and clear way? I didn't explain why the annotation was required because I find that variance is usually a subject that most people don't ever really learn. Also, these annotations can be super deep down in the structure of the type, so working out exactly how they are invariant or contravariant is also not always clear just by a loose inspection.

I think the most important part is that the error message differs from the usual Missing type annotation for T message which, for example, appears if you export a function without a return type annotation. That's why searching for the above error message yields a lot of unhelpful discussions right now (at least for the case in this issue).
Also, I'd definitely include the information about covariance, since this is at least googleable.
Maybe something like this?
"Missing type annotation for T. Make sure to annotate any types used in invariant or contravariant positions that are reachable through exports. Alternatively, consider marking annotations as covariant when possible."


Separate python files for a better folder hierarchy

Hello team,
Is it possible to separate my bolt app into multiple files.
For example, my python script currently looks like the below:
main.py
import....

app = App()

@app.error()
def error():
       ... something ...

@app.command()
def command():
       ... something ...

@app.event()
def event():
       ... something ...

I wanted to break this into multiple files namely main.py, command.py, event.py and error.py.
The slack_bolt version
slack-bolt 1.18.0
slack-sdk 3.21.3
Python runtime version
Python 3.10.11
OS info
ProductName: macOS
ProductVersion: 13.3.1
ProductVersionExtra: (a)
BuildVersion: 22E772610a
Darwin Kernel Version 22.4.0: Mon Mar 6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
Steps to reproduce:
(Share the commands to run, source code, and project settings (e.g., setup.py))
N/A
Expected result:
Have slack bolt resource in multiple files
Actual result:
Everything resides in main.py
Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

@eddyg Thanks to the 2 issues that you mentioned, i was able to find this repository through them: https://github.com/slack-samples/bolt-python-starter-template
Thank you so much!


(high priority) two push transitions corrupts tab bar (and presumably 2+)

After returning from a push transition, the footer tab bar operation is corrupted, switch to first tab no longer works. I verified that the tab bar urls are correct in the markup.
reproducible sequence:

open https://kadist-ios.herokuapp.com/kmap_main
click the 4th tab "Artists"
click any item in the list to push transition to a new view
click/swipe back
click the first (left most) tab. You'll notice that the tab doesn't do anything, the return from a push transition causes Jasonette to get the tabs mixed up.

@gliechtenstein - one of my users showed me their iPhone X that did not exhibit this behavior. I wasn't able to tell if she had the latest code base but thought that this might help determine the cause (recent change in the code, or timing related)
It seems to assume that the push always happens from the first (left most) tab and restores the current view (on push view's close) to the left most tab, but that's not the tab that initiated the push. The same behaviour can be reproduced in other tabs/parts of the application too. I marked this high priority because it affects users and can't be fixed by simply pulling to refresh (because that refreshes the wrong view)
(@gliechtenstein  as a temporary workaround while this is pending - switching from push to modal prevents the issue - possibly that's also useful info)

I was trying to look into this just now, but it's hard to test this because I've run into a couple of problems:

I understand you're using the modal as a workaround for now, but this means I can't test the push transition unless I replicate your entire app on my side just to change the transition to push. It would be great if you can share a markup that doesn't change so I can test it.
I am at step 3 and the transition is not working. The markup seems to not have a rendering action so the view just ends up being blank. Is this on production?

Anyway I'll try to fix this as soon as I can once you help me out with these issues. Thank you.

thanks - I've put it back to "push" and the issue reproduces for me...

The view doesn't render after transitioning from step 3.

As for coming back to the first tab, for me it does come back to tab 1 when i press the tab bar item after coming back from step 4.

I'm using the develop branch. Which version are you using?

I'm also on the develop branch. I just added
        "$load": {
          "type": "$render"
        }

but oddly for me that view renders fine without it.
Does the issue still not reproduce with the $render added?

I've fixed it. https://github.com/Jasonette/JASONETTE-iOS/commit/bba2f912497d0b7f66d3902d69fa183688a50221
Also I've started keeping track of these small test cases just so it's easier to test every time there's a change in how tab bars work https://github.com/Jasonette/Jasontests/blob/master/tabs/index.json
Feel free to send PRs for future bugs when you encounter problems, but I can also keep updating the repo myself.
Anyway it should be fixed now, can you check?

Re-opening because the issue still reproduces with slight variation from previous steps:

open https://kadist-ios.herokuapp.com/kmap_main
click the 4th tab "Artists"
click "A" item (doesn't matter which)
click any item in the list to push transition to a new view
click/swipe back
click/swipe back (again)
click the "News"(left most) tab. You'll notice that the tab doesn't do anything, the return from a push transition causes Jasonette to get the tabs mixed up.

Thanks!

@gliechtenstein any chance you'll have time to take a look at this please?

This was happening because none of the bottom tab bar items urls were matching the current url. The previous commits had fixed this to a certain extent, but this particular case was an additional layer of edge case that happened when you have multi-level hrefs.
It should be fixed now https://github.com/Jasonette/JASONETTE-iOS/commit/2cdf9ef4a2ce17456f78e56f4345fb32eddcb92a

thanks for taking a look, I'll merge this into my branch and give it a try.
There is no tab bar on any of the push transition views, so I'm not sure I understand the explanation. Only top-level views have the tab bar in my app, is this not an ok idea? I could change it so that all views contain the tab bar but I'm not sure that would work because the tab bar url for the currently shown view would be different each time (for each level of push transition)
What is the best practices for tab bars? I'll change to whatever you recommend and works best in the app, but my understanding was that they should only be used on the top-level view?

Your https://kadist-ios.herokuapp.com/kmap_artists_by_letter?letter=A has footer tab bars.
And none of the tab bar item URLs match the https://kadist-ios.herokuapp.com/kmap_artists_by_letter?letter=A
This is fine, and things like this should just work, which was the point of this entire thread and the fix.

What is the best practices for tab bars? I'll change to whatever you recommend and works best in the app, but my understanding was that they should only be used on the top-level view?

As I mentioned just above, no you should be able to use tabs anywhere. That was the whole point of this fix.

ok great, thanks, merging now, well, installing the multigigabyte update to xcode first. Finger's crosses xcode still works.

I just merged the code and unfortunately it doesn't fix the problem except for the single case where upon returning to the top-level-view I click the left most tab. If I click any other then the tabs are "confused", (mixed up, clicking one for News, opens, for example, Artists tab)
If I read you properly if I remove the tab bar from the first level on the artist's tab then it should work right, as a workaround.
I'm releasing this app soon so if there's a fix then I'll hold off, otherwise if the best solution is to remove the first level tab in the artist's tab then I can do that.
Just to be clear, steps to reproduce:

open https://kadist-ios.herokuapp.com/kmap_main
click the 4th tab "Artists"
click "A" item (doesn't matter which)
click any item in the list to push transition to a new view
click/swipe back
click/swipe back (again)
click the "videos" tab
click the "News"(left most) tab. The tab that actually get's rendered is the Artists tab (not News)

I think from looking at your code you have to maintain a stack rather than a flag, the visible tab when moving to an untabbed view should push the previous tab's url onto a stack so that as the transitions unwind the correct view is rendered.

Please try the latest fix https://github.com/Jasonette/JASONETTE-iOS/commit/c95f275a9d73b096ce38293286d3c3bef7c452af - There can be many different solutions but i've been trying to fix this while making least amount of change so as to minimize unknown factors, but historically tab bars has been really tricky.
I tried multiple different scenarios and confirmed they're working but there could be some case I overlooked, so feel free to share if there's another issue.

I went to the trouble of making sure that for every push transition I replace that tab's url with the current one (which was easier than I thought) and the tabs still get messed up after only a few clicks around. By messed up I mean click "news" and get "artists" or some other tab.
I'll leave it like this then back out the tabs-on-every-view on Sunday (so it works again) in case you want to look at it. Here's one of many sequences that reproduces the issue:

open https://kadist-ios.herokuapp.com/kmap_main
click "artists" tab
click  and letter
click any artist name
(without clicking back) click "news" tab
click artists tab
click "news" tab

at this point the "news" tab shows  the "artists" view
Since I've taken a lot of your time with this if you prefer not to do more on this (due to the risk of destabalizing other things) then just say and I'll only put my tabs on the top level views.
Aside: the work to replace the tab's url with the push transition's url was pretty easy with flask, but it would be possible to do this internally to Jasonette. It's definitely easier for Jasonette to be stateless and it's not that hard for users to do it but it would certainly be nice to have an option in transition like "keep_footer": "true" to auto inject the footer of the parent markup for all depth levels.

OK let's try this one more time. Try the latest develop. If it fails again I think it's best to just go with tab bar on level0 only for now. At least it's much better than the previous state where the only way to use tab bars was to have the current view's URL always match the tab you're in.
The stateless tabbar thing has given me too much headache and it sure is tempting to drop the policy (the majority of the buggy behaviors on Jasonette have something to do with this), but that kind of feels like selling the soul to the devil so I'll try to get this right as much as I can.

This is worse - now the tabs lose their push state, if for news tab I move to level 1 (from 0) then switch tabs to artists and then back I’ve lost the chevron to go back in the news tab to level 0. This happens for all tabs so the app becomes unusable because you can never get back to level 0 pretty quickly.
I reverted this change in my branch and will remove the tab bar from any where other than level 0.
I think that for apps using tabs there should be a top level app.json that defines the tabs so the views aren't stateless, the tabs then wouldn’t need to be defined in any of the child view levels, they would be managed at the app level. Not sure how this would work in your code but that seems like a better design. Tabs really live outside of any view. Each view belongs to a tab and all child views inherit from that tab. I don’t know iOS coding so maybe this isn’t how they work. It seems like the idea of jasonette understanding an app holistically as opposed to a set of stateless independent views might be quite challenging to change. However, I think that would be worthwhile because there are quite a few other things that are really app properties (that belong in json) but not associated with any particular view. Style classes for example would be another use for an app.json, global data is another. This though would break everyone’s apps currently. Not sure what the roadmap looks like, if you’re already planning other v2 breaking changes then might be something to consider.

On Jun 9, 2018, at 6:11 AM, gliechtenstein<EMAIL_ADDRESS>wrote:
OK let's try this one more time. Try the latest develop. If it fails again I think it's best to just go with tab bar on level0 only for now. At least it's much better than the previous state where the only way to use tab bars was to have the current view's URL always match the tab you're in.
The stateless tabbar thing has given me too much headache and it sure is tempting to drop the policy (the majority of the buggy behaviors on Jasonette have something to do with this), but that kind of feels like selling the soul to the devil so I'll try to get this right as much as I can.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


Is it possible to use multiple match conditions with same GET method but different uri exact and prefix

Hi  , please help me understand is there any issue in following match conditions ?
There are two match conditions and both of them have same method equal GET but have different uri exact and prefix with same value /
  http:
  - match:
    - method:
        exact: GET
      uri:
        exact: /
    rewrite:
      uri: /teritori-rpc
    route:
    - destination:
        host: pn-frontend
        port:
          number: 3000
  - match:
    - method:
        exact: POST
      uri:
        prefix: /
    - method:
        exact: GET
      uri:
        prefix: /
    - method:
        exact: OPTIONS
      uri:
        prefix: /
    route:
    - destination:
        host: pn-backend
        port:
          number: 4000

no problem, istio will apply them in order rather than most exact matching


newsboat: 2.29 -> 2.30.1

Description of changes

👉 Kindly requesting folks reviewing this PR to also have a look at #199486, TY!
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

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

1 package built:

newsboat


Added rel="stylesheet" property to external CSS

Codecov Report

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

@@          Coverage Diff          @@
##           master    #81   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          23     23
  Lines         529    529
  Branches       59     59
=====================================
  Hits          529    529

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ec4c668...7262da1. Read the comment docs.


Pico W does not reboot after flashed with custom made UF2 image.

It works okay when flashed (either on Windows or Linux). But didn't start when reconnected USB (no bootsel pressed).
When using MicroPython it does works after reboot.
I build that UF2 image with this CMakeFiles.txt file:
set(APP_NAME "motion_sensor")

cmake_minimum_required(VERSION 3.13)

set(PICO_BOARD pico_w)

include(../pico-sdk/external/pico_sdk_import.cmake)

project(${APP_NAME} C CXX ASM)
set(CMAKE_C_STANDARD 11)
set(CMAKE_CXX_STANDARD 17)

pico_sdk_init()

add_executable(${APP_NAME}
    src/motion-sensor.c
)

pico_enable_stdio_usb(${APP_NAME} 1)
pico_enable_stdio_uart(${APP_NAME} 0)

pico_add_extra_outputs(${APP_NAME})

target_link_libraries(${APP_NAME} pico_stdlib pico_cyw43_arch_none)

This issue came from this other: https://github.com/raspberrypi/pico-feedback/issues/299

I resolved my issue. In my case it was my error. I was initiating the Wifi module (cyw43) in order to use the Onboard Led. Calling cyw43_arch_init() was working okay when flashing because the Pico was yet connected to the power supply. It was falling on reboots because this function was returning not success and I was closing my app in that case.
The solution is simple: a) to await an undefined amount of time (in my case I am lighting the LEDs for 3 seconds) or b) to execute that function without delay and retrying until success.


don't log file contents when writing via kv:key put <key> --path <path>

There are a couple of reasons we don't want to log the contents; it could be secret, or it could just be very long. This commit changes the messaging to instead just say which file is being uploaded. I also took this opportunity to add a log when we're deleting a key with kv:key delete <key>.

cc @petebacondarwin I can't add you as a reviewer until you accept the team invite haha

I copied the initial message from wrangler1 (and honestly disliked it) We still have some enhancements to make like adding a spinner when the call is in flight, and actually showing a proper success message, but that's something we need to do all over the app for every command really.


check release keystore path

Fixes #34800.
I'm checking if release keystore isn't empty, if it isn't then check if keystore file exist or not. Hence if now the keystore doesn't exist Export button will get disabled.
In future it will be better to put warning just like when debug keystore isn't configured to avoid confusions, I didn't do that because of error translation issues.

@Anukriti12 Is there anything that made this pull request no longer relevant?

Seems like it was closed automatically by a force push which removed the commit of this PR.

I'm sorry I think I accidentally messed it up

I'm sorry I think I accidentally messed it up. Shall I create another PR covering 2 commits? (one other issue that I was working on)

Sorry for the late answer.
If you are working on two separate issues, I would suggest to make two PRs from separate branches, so that you can update each independently and we can merge them independently too.


Support multiple html-webpack-plugin instances

I wrote most of the html-webpack-plugin code and would ask you to adapt your plugin a little bit.
Instead of string search and replace you might want to alter the assets array:
https://github.com/jantimon/resource-hints-webpack-plugin/blob/master/index.js#L87-L89
Instead of using the options of your plugin you might want to extend the html-webpack-plugin options so it can be used in multiple instances:
https://github.com/jantimon/resource-hints-webpack-plugin/blob/master/index.js#L64

Thanks for the valuable input, @jantimon. Still getting with hang of what are idiomatic best practices for Webpack plugins :)
https://github.com/jantimon/resource-hints-webpack-plugin/blob/master/index.js#L87-L89 feels a lot cleaner than the approach we're currently using here. I'm in favor of switching to it.
https://github.com/jantimon/resource-hints-webpack-plugin/blob/master/index.js#L55 appears to be where you're merging html-webpack-plugin's options with custom ones. I see no reason not to switch over to doing something similar there. I hadn't considered the multiple instance usecase but appreciate the tips!

@addyosmani cool 👍 for the html-webpack-plugin 3 version there will be an api to create custom tag elements:
https://github.com/jantimon/html-webpack-plugin/blob/version-3.x/lib/html-tags.js#L28
Maybe we will also backport it to the 2.x branch

@addyosmani We can actually keep the current API as the default options for every hmtl-webpack-plugin instance, and each instance can override them if required. One thing to consider moving options into html-webpack-plugin is naming conflicts with other plugins.

@bekos

We can actually keep the current API as the default options for every hmtl-webpack-plugin instance, and each instance can override them if required.

That sounds pretty reasonable to me as well.

cool 👍 for the html-webpack-plugin 3 version there will be an api to create custom tag elements:

@jantimon Oh that's totally rad. Thanks for sharing that insight. I'd be interested in it being backported, but don't want to add too much to your workload - is V3's api surface vastly different?

The tag structure is compatible with the current html-webpack-plugin version. The main idea behind 3.x is to get closer to the webpack 2.x internals and that causes some breaking changes but we try to introduce as few api changes as possible. Your plugin shouldn't be affected at all.