[Request] Allow To Save/Store Repo Credentials

I'm not sure if this has been brought up before, but I'd love to not have to input my repo details every time I wanna view snapshots= contents.
Would there be a way to cache/save/store this info anywhere, and just have the repo kind of saved onto the client? If that's out of scope, then perhaps read from a file for all inputs, not just password?
I personally use Backblaze, so it's a lot of copy pasting every time.
Thanks!
Edit: Ideally you'd allow credentials to be saved for all types of repositories (local, S3, Backblaze), and allow for multiple repos to be saved too.

Ideally you'd allow credentials to be saved for all types of repositories (local, S3, Backblaze), and allow for multiple repos to be saved too.

Yes, that indeed would be nice, although we then would need to save the passwords too, which is always needs to be done with extra care.
There are a few other feature requests open, which require saving some form of a preference state for the Restic browser. Right now it uses no persistent options at all.  I'll try to add this first and then see how we can memorize previously used repository locations.

A workaround for now, which I'm using, is starting the Restic Browser from a shell with predefined restic repo environment variables:
If you e.g. define the RESTIC_REPOSITORY, RESTIC_PASSWORD in a shell and then start the Restic Browser from there, it will pick them up and use them as the initial repository credentials.

Thanks for creating Restic Browser!
Just tried setting those environment variables, and Restic Browser didn't act on them.
Might I suggest using the _FILE versions as well? This would allow secrets to stay in a file. E.g. ~/.config/restic.passwd, then define the env var RESTIC_PASSWORD_FILE=~/.config/restic.passwd.

Hi. This should work, even with RESTIC_PASSWORD_FILE. What platform are you on? Are you setting the ENV values globally?
Try setting the env values in a terminal, then run restic browser directly from that terminal.

See https://github.com/emuell/restic-browser/issues/61 for further discussion of this topic.


Why was multi-instance launching removed?

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
I really want it back :(

yes

https://github.com/pizzaboxer/bloxstrap/wiki/Plans-to-remove-multi‐instance-launching-from-Bloxstrap


Preserve union type name within larger union

TypeScript Version:  3.1.0-dev.20180731
Code
type Value =
    | { kind: "number", n: number }
    | { kind: "string", s: string };
function f(value: Value | undefined): void {}
f(undefined);

Expected behavior:
Quick info on f shows function f(value: Value | undefined): void
Actual behavior:
Quick info shows:
function f(value: {
    kind: "number";
    n: number;
} | {
    kind: "string";
    s: string;
} | undefined): void

Related Issues: #14662

Reduced test-case without functions or tagged unions:
type Foo = 'a' | 'b'
declare const a: Foo;
declare const b: Foo;

const value = a // Foo (as expected)

const values1 = [a, b] // Foo[] (as expected)

const values2 = [a, 1] // (number | "a" | "b")[], but expected (number | Foo)[]

Will be fixed by https://github.com/microsoft/TypeScript/pull/42149?

Will be fixed by https://github.com/microsoft/TypeScript/pull/42149?


Csv headers with ""

when i try to create reader with:
var options = new CsvDataReaderOptions
{
HasHeaders  = false,
Delimiter = ';'
};
      using var  csvDataReader = CsvDataReader.Create(request.StreamReader, options);

I get sylvan.data.csv.csvformatexception, is there a way to tell the reader that headers are with quotes ("") so that we dont get the format exception?
I also have to point out that i dont know the header names in advance so i have to read them and store them thats why i have to set HasHeaders to false so i can parse the 1st line properly.

Here is an example file:
example.csv


Readme for first time users

Please describe what you would like to see in this project
I would like to see the current README replaced with a guide for first-time users of Carpenter to publish their own plugin.
Please describe your use case
Plugins in other organizations and/or CI systems.

I have began to create a new README.md that is more friendly to users here. This is a WIP. Additionally, the link will break when the naming convention is changed to simply README.md.


Input_number broken after activating PyLoxone

Hi,
I am using PyLoxone since some time. Now I wanted to set an input_number to define an alarm clock. The input_number can be set, but it doesn't change the value. If I disable PyLoxone (just # in front of the Loxone config lines in configuration.yaml) , the input_number works again.
Could you please take a look?
Regards,
Harald

Hi,
the input number works for me without problems. Can you please post a configuration.yaml with a minimal example. Furthermore you can post the log output of the Pyloxone? Do you get any errors displayed?

Sure, here is the configuration.yaml:
Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
Text to speech
tts:

platform: google_translate

#group: !include groups.yaml
#Home Assistant internals
homeassistant:
time_zone: Europe/Berlin
packages:
alarm_1: !include alarm_bedroom.yaml
#Loxone
loxone:
port: xxxx
host: xxx.xxx.xxx.xxx
username: username
password: password
generate_scenes: false # default is true
Unfortunately, I don't get any errors. It doesn't matter, if I create an input_number within a file (in this example I define an alarm clock in a separate file) or as a helper in the UI. The moment I comment all PyLoxone parts, the input_number works again.
Tested in HA supervised install and HA docker. The issue is reproducable.

Hi,
yes I can reproduce it. It is the EntityComponent for the Input_selects in the file switch.py.
When I comment the lines from 67-95 out like in the code below. Then the inputs work but you lost the
inputs from loxone. I have no solution for it now. Maybe someone else knows a solution.
        # elif switch_entity['type'] in ['LeftRightAnalog', 'UpDownAnalog', 'Slider']:
        #     switch_entity.update({'uuidAction': switch_entity['uuidAction'],
        #                           'name': switch_entity['name'],
        #                           'initial': switch_entity['details']['min'],
        #                           'min': switch_entity['details']['min'],
        #                           'max': switch_entity['details']['max'],
        #                           'step': switch_entity['details']['step'],
        #                           'cat': get_cat_name_from_cat_uuid(loxconfig, switch_entity.get('cat', '')),
        #                           'room': get_room_name_from_room_uuid(loxconfig, switch_entity.get('room', ''))
        #                           })
        #
        #     if switch_entity['type'] == 'UpDownAnalog':
        #         switch_entity.update({'mode': 'box'})
        #     else:
        #         switch_entity.update({'mode': 'slider'})
        #
        #     new_loxone_input_select = LoxoneInputSelect(**switch_entity)
        #     hass.bus.async_listen(EVENT, new_loxone_input_select.event_handler)
        #     entities.append(new_loxone_input_select)

    # component = EntityComponent(_LOGGER, 'input_number', hass)
    # component.async_register_entity_service(SERVICE_INCREMENT, {}, "async_increment")
    # component.async_register_entity_service(SERVICE_DECREMENT, {}, "async_decrement")
    # component.async_register_entity_service(
    #     SERVICE_SET_VALUE,
    #     {vol.Required('value'): vol.Coerce(float)},
    #     "async_set_value",
    # )
    # await component.async_add_entities(entities)

Yeah, I also saw that there is just an input_number in the switch file. But I am not a programmer. Is there a way for a workaround? I will try to define the inout_number before and after the installation of pyloxone. Maybe it makes a difference. How did you make it work in your environment?

Ok, seems like it doesn't matter when I create the input_number before or after setting up the PyLoxone integration. Pity that I can't make it work :-(

I do not know how to solve it without breaking the loxone input. But of course I will try it. Maybe I ask in the forum for help. What you can do is comment out the lines  from my last comment. You lose the loxone input and sliders but you can get the alarm input to work.

Right now I just use one input_number slider (due to the issue) but six or seven dimmer from Loxone (which rely on your implementation). I hope, you can solve the issue, but I won't break your great implementation (as Loxone bothers me more and more ;-) ).

I asked in the Forum:

That would be awesome. Your integration really allowed me to move away from the Loxone frontend. So thank you for all you work you put in here!

I managed to build a workaround. Maybe not the best solution, but it works:
I installed a second HA instance (docker, supervised, whatever) and used the "Remote Home-Assistant" integration from HACS. Then I just linked my main HA instance to the second instance and installed on the second instance just PyLoxone as integration. The rest is installed on my main HA instance. Even though it's not the most elegant solution, it works for me :-)

@Shogun1978 I removed the support for the Input_number because they are not supported to generate dynamically. I asked for a solution in the forum and on discord and they told me that I can not get it to work properly. You can stick with the old version on your  second HA instance. Maybe they implement the Input_numbers as normal component. Then it would be a easy task to integrate it. They already discuss that. Maybe we have luck and in future I can implement this feature.

@Shogun1978 I also updated the documention for integrating the inputs via a loxone websocket command. Maybe you can use this.
Please see here:
https://github.com/JoDehli/PyLoxone#example-2-with-a-updownanalog


Spanner session leak fix and tests

fixes #1474
typo fix. removes accidental call to method rather than using existing variable.

Codecov Report

Merging #1476 into master will decrease coverage by 0.35%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #1476      +/-   ##
============================================
- Coverage     69.58%   69.23%   -0.36%
+ Complexity     1543     1538       -5
============================================
  Files           217      217
  Lines          5981     5981
  Branches        611      611
============================================
- Hits           4162     4141      -21
- Misses         1561     1585      +24
+ Partials        258      255       -3

Flag
Coverage Δ
Complexity Δ

#integration
?
?

#unittests
69.23% <100%> (-0.36%)
1538 <0> (-5)

Impacted Files
Coverage Δ
Complexity Δ

...k/cloud/gcp/data/spanner/core/SpannerTemplate.java
73.39% <100%> (ø)
73 <0> (ø)
:arrow_down:

...gure/trace/sleuth/StackdriverHttpClientParser.java
4.76% <0%> (-80.96%)
1% <0%> (-3%)

...gure/trace/sleuth/StackdriverHttpServerParser.java
37.5% <0%> (-50%)
1% <0%> (-2%)

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 ca4d7f0...bc103f9. Read the comment docs.


Create a better looking Readme file

hello @ArslanYM
Can I do this for you

@Darlio88 Ofcourse!! Please sure do. Looking forward to it

Hey, the readme file looks good right now, would it be better if we could make it in table form?

@Shalini469717 Do you think creating a table would make the Readme better in readability?

@Shalini469717 Im really not sure. However, please lemme know if you have any other ideas.

Will try in cloned repo, if it doesn't feel good we can drop the idea


[Snyk] Upgrade eslint from 8.39.0 to 8.48.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade eslint from 8.39.0 to 8.48.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 9 versions ahead of your current version.
The recommended version was released a month ago, on 2023-08-25.

The recommended version fixes:

Severity
Issue
PriorityScore (*)
Exploit Maturity

Regular Expression Denial of Service (ReDoS) SNYK-JS-WORDWRAP-3149973
292/1000  Why? Proof of Concept exploit, CVSS 3.7
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Checkmarx One – Scan Summary & Details – ec4ed43d-a128-4070-9d7d-e7d872bce4bb
Fixed Issues

Severity
Issue
Source File / Package

CVE-2023-26115
Npm-word-wrap-1.2.3


Migrate from Appcenter to GitHub CI to publish apps in App Store Connect and Googles Play console

Microsoft's Appcenter retires as of March 2025, so we should find other solutions, it appears that we can do everything from Github's CI directly:
name: Deploy Flutter App

on:
  push:
    branches:
      - main

jobs:
  build-and-deploy:
    runs-on: macos-latest

    steps:
      # 1. Checkout the repository
      - name: Checkout code
        uses: actions/checkout@v3

      # 2. Set up Flutter
      - name: Set up Flutter
        uses: subosito/flutter-action@v2
        with:
          flutter-version: 'stable'

      # 3. Install dependencies
      - name: Install dependencies
        run: flutter pub get

      # 4. Set up Apple Code Signing
      - name: Import Certificates and Provisioning Profiles
        uses: apple-actions/import-codesign-certs@v1
        with:
          p12-file-base64: ${{ secrets.P12_FILE }}
          p12-password: ${{ secrets.P12_PASSWORD }}
          mobileprovision-file-base64: ${{ secrets.PROVISION_PROFILE }}

      # 5. Build iOS IPA
      - name: Build iOS IPA
        run: flutter build ipa --release
        env:
          CI: true

      # 6. Build Android AppBundle
      - name: Build Android AppBundle
        run: flutter build appbundle --release

      # 7. Deploy to Google Play Beta Track
      - name: Deploy to Google Play (Beta)
        uses: r0adkll/upload-google-play@v1
        with:
          serviceAccountJson: ${{ secrets.GOOGLE_PLAY_JSON }}
          packageName: com.example.yourapp
          releaseFiles: build/app/outputs/bundle/release/app-release.aab
          track: beta  # Publish to the beta track

      # 8. Upload Build to App Store Connect
      - name: Upload to App Store Connect
        uses<EMAIL_ADDRESS>        with:
          issuer_id: ${{ secrets.APP_STORE_ISSUER_ID }}
          key_id: ${{ secrets.APP_STORE_KEY_ID }}
          private_key: ${{ secrets.APP_STORE_PRIVATE_KEY }}
          ipa_path: build/ios/ipa/*.ipa

Current state in wip Branches:
IOS

WIP: https://github.com/encointer/encointer-wallet-flutter/tree/cl/publish-test

Finally found an action, which does all the heavy load. However, I still get the error that it can't find any provisioning profiles in the build phase. It is the same error as in the manual workflow before. Hence, I do think that we have to check our certificates in the Apple Developper Portal (review the pending licence agreement), and maybe re-import the secretes again in the secrets. I do think that the build setup is fine otherwise.
-> If it doesn't work, I suggest that Piero goes to through the steps outline in our actions readme with his Mac.
Android

WIP: https://github.com/encointer/encointer-wallet-flutter/tree/cl/android-store-publish

Setup is simpler, but we need to set up the service account, as outlined in the action we are using. https://github.com/r0adkll/upload-google-play?tab=readme-ov-file


Add Polish localization, changes in the column and tile menus

Polish language added.
"Play" button in the column menu now plays music starting from the column and continues playing it untill the end of the song.
New "Play column" button plays a single column.
New text entries added.
Labels of "Copy" and "Paste" tile menu options are now translatable.

@pattlebass I will appreciate any suggestions regarding commits and their messages to make them fit your style or naming convention.

Hey! Thanks for contributing!
Unfortunately I can't test the PR right now, but at first glance everything looks fine.
Only one thing. It would be perfect if you could separate this PR in two:

one that adds Polish translations and improves the context menu
another that makes changes to the column menu

That would make the git history a bit nicer. If not, it's ok.

Thank you for the review! I will close this PR then and create new ones with the corrections.


feat: test UBI image build

supersedes #1559
relates to #1192
This PR changes the Publish Image workflow to build an UBI image alongside the existing distroless.
The existing image tag schema stays the same. UBI images will be tagged with a suffix -ubi.
E.g.
ghcr.io/external-secrets/external-secrets:v1.2.3-ubi

Also, the binary is now built inside a docker container. It is way to slow. Not going to do that unless absolutely necessary.
Proof of Work
See publish jobs here: https://github.com/external-secrets/external-secrets/actions/runs/3101085916
I've been looking at this regarding FIPS compliant go builds: https://developers.redhat.com/articles/2022/05/31/your-go-application-fips-compliant.  But for the time being we can not build with ubi8/go-toolset because it's still running go 1.17 (we have dependecies that require 1.18) once 1.18 is available we can deliver FIPS compliant builds.
TODO:

[ ] build binaries inside a container to enable fips-compliant crypto (of possible)

That’s great! Yes, looking forward to go-toolset 1.18.
will this be part of 0.6?

Hey @IdanAdar sorry for the late reply. I think we can merge it asap once reviewed. There are no changes related to the controller, so this is safe to be pushed out asap.
Let me add a couple of comments and then it's ready for review.

@moolen Changes look solid. Unfortunately I can't add an approval record.

Should we change docs to let users know how to use this? Like changing the image value of helm install when needed? (Maybe the chart md generation so it also goes to artifacthub description screen)

Also, the binary is now built inside a docker container. It is way to slow. Not going to do that unless absolutely necessary.

[ ] build binaries inside a container to enable fips-compliant crypto (of possible)

We didn't then, right?

yeah, right. i've removed the check :D
We're going to do that for the ubi image once the ubi-toolchain supports go 1.18.

Should we change docs to let users know how to use this?

I added the image name/tag to the release notes. :+1: we can add that to the installation/getting started docs.

@moolen Anything missing?

I wanted to give @knelasevero or @gusfcarvalho a chance to take a look. If there are no objections let's merge :smile:

Is there a UBI based image available now @moolen ?

@moolen when is the 0.6 cut off so that we could begin using the image?

I'll do a release now!

I wanted to give @knelasevero or @gusfcarvalho a chance to take a look. If there are no objections let's merge 😄

super late, sorry. LGTM :P


Integrate Netlist into VlsirTools

Citing https://github.com/dan-fritchman/Hdl21/issues/108, VLSIR should be expanded to integrate Netlist into VlsirTools to make it possible to read and simulate external netlists. I propose the following plan:

[ ] Include Netlist as is into VlsirTools
[ ] Write conversion scripts to partially convert Netlist data model in VLSIR
[ ] Expand VLSIR protocol buffers to include the Netlist data model
[ ] Finish integrating Netlist into VlsirTools and parse all netlists to expanded VLSIR

Sounds great. Recommend a few tweaks:

Put Netlist as another python-package, alongside VlsirTools (and SpiceCmp) for that matter
I don't think we want to expand the VLSIR data model to include all the fun transistor-modeling stuff in Netlist, at least not yet.
Conversion into VLSIR will take a bit more than just a script. The Netlist parsing particularly needs to be expanded to do "resolution". I.e. in compiler terms, it currently makes the AST, and needs to make the CST for VLSIR to work. Example:

* First subcircuit named "who_am_i"
.subckt who_am_i
+ alpha beta gamma
.ends * who_am_i

.subckt outer a b c
  * Another, inner-scoped subcircuit with the same name "who_am_i"
  .subckt who_am_i x y z
  .ends * who_am_i

  * The trick: which subcircuit does this resolve to?
  * The answer can often be "none", if the expectation is it's provided externally
  x1 a b c who_am_i

.ends * outer

To date each Instance just stores a string-valued Module (or similar). They'll need to be resolved, sometimes nestedly as in the example above. And the ones that can't be resolved can create ExternalModules on the fly.

Okay, so here is the tweaked task list:

[ ] Add Netlist as a standalone Python package, alongside VlsirTools and SpiceCmp.
[ ] Expand the Netlist parsing process to perform "resolution" to construct a Spice CST.
[ ] Develop a method to convert from a Spice CST into a partial VLSIR representation.

So, I've taken a look at Netlist today and I believe as a first PR that the CST generation for the circuit description portions of a netlist are adequate to convert to VLSIR barring the pathological case above. But that is as far as I'll go, because I think there needs to be a more involved strategy, if any, to get simulation keywords correctly parsed out and converted to VLSIR. I'll then double back to dan-fritchman/Hdl21#108 and implement a few ways to go from_proto into the specific PDK ExternalModule libraries or native HDL21 primitives.

So on 2nd (3rd? 4th? whatever) thought here -

There's already lots of repetition between Netlist and VlsirTools - particularly for writing netlist-text.
It breaks plenty of the time, requires maintenance etc.
That would be good to centralize.

So perhaps:

Netlist becomes the (sole) writer for the two
Netlist retains its very-SPICE-specific data model
VlsitTools, instead of writing netlist-text, would primarily convert its stuff into the Netlist data model, and invoke its writer(s).

The one thing currently supported by VlsirTools that might get left behind is Verilog. That language has a lot more "stuff" in the data model, some of which maps more cleanly onto VLSIR schema than the spice-centric Netlist data model. VlsirTools would probably still need to implement that one itself.


browser version of "2D Water Ripple"

used 8 neighbors instead of 4, but otherwise same as Processing version (used to compare speed of canvas vs Processing)

lovely!


WA to torchvision dataset issue

Issue #, if available:
https://github.com/pytorch/vision/issues/1938
Description of changes:
Including the suggested WA to an issue with downloading mnist dataset from torchvision
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Closing as the pytorch has fixed the issue https://github.com/pytorch/vision/issues/1938#issuecomment-595332234


[riscv] Add support for RISC-V vector extension in arch

First part of initial support for RISC-V vector extension.
Full pack of patches for support could be found in https://github.com/jfalcou/eve/pull/1716
With this patch unit.arch tests are fully passed.

Hi,
is using stuff like Dockcross viable for testing ?
It would simplify our job of settign up a proper test image.

@ita-sc woudl you mind point em where to find info about the 1st part of the toolchain integration (the gcc-13 sysroot) ?

I am able to compile and run RISC-V random code using :

riscv64-linux-gnu-g++-13 -static -march=rv64gcvzvl128b -std=c++20 using the Ubuntu RISC-V g++ 13 package
qemu-riscv64 --cpu rv64,zba=true,zbb=true,v=true,vlen=128,vext_spec=v1.0

Could this be enough as a first CI target while clang settle down ?

I am able to compile and run RISC-V random code using :

riscv64-linux-gnu-g++-13 -static -march=rv64gcvzvl128b -std=c++20 using the Ubuntu RISC-V g++ 13 package
qemu-riscv64 --cpu rv64,zba=true,zbb=true,v=true,vlen=128,vext_spec=v1.0

Could this be enough as a first CI target while clang settle down ?

You mean simple code, without attributes for sized types? Unfortunately, in can not be used, as without them, vector types can not be put in structures (as they are sizeless by default).
I see that in gcc-14.2 there is some kind of support for sized vector types, but I need to check if requirement for this mr are supported.
As first stage, we can use even clang-19, the main reason for update is that without patch you can not create logical<wide<T, N>>, where N < 8.
And for full support in clang, we need quite new llvm: the patch with support required functionality in clang was merged last week (https://github.com/llvm/llvm-project/commit/635d20e9e72e25966b196bb012a90e750ae00c6d)

@ita-sc woudl you mind point em where to find info about the 1st part of the toolchain integration (the gcc-13 sysroot) ?

I usually build it myself, or use prebuild one (It seems you can use, for example https://syntacore.com/tools/development-tools - there path to folder riscv-gcc should be used as RISCV_GCC). If you anyway install of riscv-gcc-13 in your system, I suppose I can change scripts so you need to export variables to installed packages.

I am able to compile and run RISC-V random code using :

riscv64-linux-gnu-g++-13 -static -march=rv64gcvzvl128b -std=c++20 using the Ubuntu RISC-V g++ 13 package
qemu-riscv64 --cpu rv64,zba=true,zbb=true,v=true,vlen=128,vext_spec=v1.0

Could this be enough as a first CI target while clang settle down ?

You mean simple code, without attributes for sized types? Unfortunately, in can not be used, as without them, vector types can not be put in structures (as they are sizeless by default).

Of course :E

And for full support in clang, we need quite new llvm: the patch with support required functionality in clang was merged last week (llvm/llvm-project@635d20e)

I am OK with getting a trunk clang in our CI image no problem.

I usually build it myself, or use prebuild one (It seems you can use, for example https://syntacore.com/tools/development-tools - there path to folder riscv-gcc should be used as RISCV_GCC). If you anyway have install of riscv-gcc-13 in your system, I suppose I can change scripts so you need to export variables to installed packages.

Let's do that thanks

FYI - if you want to - we can set some time to pair up and review this on a call, so that we don't have to communicate asynchronously.
You can reach me on<EMAIL_ADDRESS>dyaroshev on twitter or cpplang slack.

I usually build it myself, or use prebuild one (It seems you can use, for example https://syntacore.com/tools/development-tools - there path to folder riscv-gcc should be used as RISCV_GCC). If you anyway have install of riscv-gcc-13 in your system, I suppose I can change scripts so you need to export variables to installed packages.

Let's do that thanks

Refactored in the same way you use clang for arm - you need to add to your LD_LIBARY_PATH path to RISC-V libs (seems /usr/riscv64-linux-gnu/lib/)

You can reach me on<EMAIL_ADDRESS>dyaroshev on twitter or cpplang slack.

I think this is a great idea, I've sent you an email.

OK so I have a working clang trunk for RISC-V. I'll be testing it this week-end on SPY and Kumi to see if it's OK.
Once done, I'll pass you a gist that you'll add to this PR to make your core run on our CI.
Thanks for all your pointers !

FYI: talked to @camel-cdr on twitter,
he says that probably LMUL=8 as default is not ideal: https://x.com/CamelCdr/status/1827684425418572151
This is not something for you to be concerned with at the moment, but this is another case where expected cardinal and max cardinal should be different.

I'd try to maximise LMUL without causing register spills.
If I understand eve correctly then it's a generic SIMD abstraction, and since you don't know the register preasure of code using eve, defaulting to LMUL=1 is the safest option. Considering that eve supports sse and avx2 which both only have 16 registers, going with LMUL=2, which gives you 16 registers would also be possible.

@ita-sc  - chosing better default won't be really possible at this stage, eve is designed around maximum being the right default. We'll fix that later.

Seems I've addressed all comments. Also in separate commit I change places, where for RISC-V I need to use simd_cast instead of bit_cast. RISC-V functions for bit_cast now can not change the size of underlying type, this work goes to simd_cast. @DenisYaroshevskiy, @jfalcou any more comments?

Sorry for being slow. Didn't have time to re-review again. Let me do a bit.
We are blocked on the ci supporting this update.
You will also have a small and annoying rebase coming, when @SadiinsoSnowfall finishes migrating operators (sorry about that) but it'll make the code simpler.

@jfalcou, @DenisYaroshevskiy thanks for adding CI for RISC-V. I've updated MR and add unit.arch tests.

There are more than 200 comments on this pr.
Github takes like like 20 seconds to load it for me.
How do you feel about recreating the pr? Just push as a clean branch.
Yeah - some things will be repeated but we will have less of a history in the way.

How do you feel about recreating the pr? Just push as a clean branch.

Created: https://github.com/jfalcou/eve/pull/1950

Closing, work continue in https://github.com/jfalcou/eve/pull/1950


Add examples for scaling a robot.

Feature Request
It would be nice to have an example showing how to load a robot from URDF / ROS (robot in meters) and then scale it (for millimeters).
robot = client.load_robot(load_geometry=True)
robot.artist = RobotArtist(robot.model)
robot.scale(1000)

It should also be ensured that scale() can be called before or after setting the artist, and lead to the same result.
Additionally, it should be clarified (eg in the documentation) whether scale() is idempotent or not, ie. calling .scale(100) twice in a raw causes twice the scaling (ie 10000) or is it idempotent in that multiple identical calls cause the same effect. Ideally, the call should be idempotent.

Hello good! I would like to add this example to the repository in a pr. Do you have a directory or folder where you would prefer me to add the example? or just in the root of the directory?

Hi @pblcc ! Great! Yes, we have a place that would make sense, I would suggest to put these examples under the examples/02_description_models together with other related examples: https://github.com/compas-dev/compas_fab/tree/main/docs/examples/02_description_models
Thanks!

Hello would love to contribute !

Hello @karshav16 thank you for the initiative. However, we are planning for a new major release where the scaling mechanism will change substantially. I think lets not work on this issue soon.


Can't find source with dash such as WEB-DL

Any ideas?

Nevermind...was passing in the file/torrent name rather than the title.


TypeError: expected dynamic type string', but had type int64'null

Hi guys, having some issue uploading image. I use "react-native-image-crop-picker": "^0.13.1" which returns me an image object with base64 data object, path, type and size. I use the base64 data and pass it as showed in the example for "multipart/form-data" upload.
"react-native": "0.42.3",
"react-native-cli": "^2.0.1",
"react-native-fetch-blob": "^0.10.5",

Here is my code:
RNFetchBlob.fetch('POST', url, headers, [
    { name : 'file', filename : "my_file.jpg", data: String(image.data)},
  ]).then((resp) => {
        console.log(resp)
  }).catch((err) => {
        console.log(err)
  });

image.data is a base64 representation of the picked image from the library using react-native-crop-picker. The error is the following:
Error: RNFetchBlob request error: TypeError: expected dynamic type string', but had type int64'null
P.S. Also have tried without using String(), but with no success. Either way, there's an error.
Would appreciate the help!
Thanks!

@gopchi , I've just finished running several test cases on multipart request and it turns out working seemly.
See the test case
Furthur to your error message, I think that's caused by a non-string field you've passed in data. Though the code snippet looks very well, perhaps you can check if the field is a String not null or some other types.

@wkh237 Hi and thanks for the response! I wanted to let you know that I resolved the issue by replacing 'file://' with 'RNFetchBlob-file://'.
const uploadUri = Platform.OS === 'android' ? uri.replace('file://', '') : uri;

RNFetchBlob.fetch('POST', url, headers, [
      { name: 'mission-img', filename: filename, data: 'RNFetchBlob-file://' + uploadUri }
]).then(response => {
      dispatch({ type: 'imageUploadSuccess', imageAdded: JSON.parse(response.data) });
}).catch(error => {
      dispatch({ type: 'imageUploadFailed', error: error });
});

@gopchi , thanks for reporting, I have to say this is a little confusing and we should somehow consider making the URI system more simple and clear as mentioned in #387. Anyway, just great to know the problem got resolved 👍

I just wanted to add that also the headers keys must all be of type string. Hopefully this will save time to people in the future.

@fabriziomoscon  +10000


Update unifi and unifi base OS versions

Unifi from 5.12.72 to 6.0.43
Base OS from Ubuntu 16.04 to 20.04
Mongodb from 3.4 to 3.6 & switch to OS supplied version
enabled https for version compare

Very nice. Worked well for me. Upgrade was seemless from existing mongo 3.4 data.

Unifi 6.0.28 is out: https://community.ui.com/releases/UniFi-Network-Controller-6-0-28/23c77a99-0957-449a-b3c0-58a37d4df81f

thanks, works for me. 6.0.36 out now too.
For anyone else who is about to look up how to fetch a pull request like I just did:
git fetch origin pull/549/head:thatsamguy-unifi
git switch thatsamguy-unifi

Unifi 6.1.17 confirmed working for me.

Unifi 6.2.26 is now out.
gosu can also be moved to Ubuntu based package.

Unifi 6.4.54 is now out.
Just bumping ENV UNIFI_VERSION "6.4.54" worked fine for me.

Closing PR as I'm no longer maintaining this for my own systems.


Add token name

So far this only adds the name property to the type and name values to the assets. It does not show the name under the asset in the Assets page.

Can we actually put this on hold until we work on the token info page? Unless it's super high prio?
I think we're going to add a lot more info per token soon.

@jonator why do we need to block this though on the token info page, instead of just doing this first?


Preparation for core protocol v3 first public working draft and RFC

This issue is intended for planning and coordination towards publishing a First Public Working Draft of the Zarr core protocol v3 specification and issuing a public request for comments (RFC).
We discussed this on today's community call, we suggested to aim for publishing the spec and issuing the RFC on Wednesday 4 November.
Suggested plan

Ask Zarr core devs to read through the current editor's draft and raise any issues they think need to be addressed before we can issue an RFC. N.B., the spec doesn't have to be perfect before RFC, so the goal here is just to deal with any obvious mistakes, inconsistencies, potential confusions, major gaps etc.
Spec editors (@Carreau, @alimanfoo) resolve any issues raised above.
Spec editors make a final PR to change the document type from "Editor's Draft" to "First Public Working Draft" and merge into the master branch on the zarr-specs repo.
Update the RTFD config for zarr-specs.readthedocs.io to serve from the master branch (currently serving from dev branch).
Write a blog post for the zarr blog declaring the spec is published, announcing the RFC, and providing any other useful information like motivation for this spec, pointers to current implementation work, plan for future timeline, etc.
Publicize the RFC via Twitter (@zarr_dev, ...) and other channels

Notes

The plan is to ask for comments to be submitted by raising issues on the zarr-specs repo.
It's suggested we follow a convention similar to W3C where they label a spec as "Editor's Draft" if it is an internal draft only intended for consumption within the group of people actively working on it, then will publish a "Working Draft" when the document has reached some maturity and they want to make it public and request comments from outside the core team. Here "Working Draft" indicates the documents maturity level. They will also add a date, e.g., "First Public Working Draft 21 October 2020", which then allows for publication of a second working draft if necessary.
Following on from this, it's suggested that we reserve the master branch on the zarr-specs repo for specs that are intended to be public, i.e., have a "Working Draft" maturity level or beyond.
At some point we should capture and document these conventions around process and document maturity levels.

Hi @zarr-developers/core-devs, @davidbrochart, I'd be very grateful if you could let me know if the plan outlined above sounds good, or if you have any other suggestions.
Also if you had any time to take a pass over the current editor's draft of the core protocol v3 spec some time in the next week I'd be very grateful if you could raise any issues that you think would need to be addressed before we could publish this document as a public working draft and ask for comments.
Many thanks :pray:

The v2 spec is currently working its way through the OGC "community standard" process. I was wondering if we wanted to consider involving the OGC community in the v3 RFC process.
Are there equivalent standards organizations in bioinformatics / bioimaging we could be working with here?

We're following the ZEP process now, (see ZEP 0), and just posted an update on the next steps: https://zarr.dev/blog/zep1-update.
The OGC proposal is tracked separately in issue #42, closing this issue for now.


Clean up the Container hierarchy

We need to look in detail at all the data that is currently in the Container hierarchy, as well as data that needs to be added (for things like Tracking, Pointing, HV monitoring, etc.) and decide if:

the structure is consistent or needs updating
the use-cases (e.g. how data are read or written into them) are met or understood
data items are missing or redundant

Note that the idea for at least some Containers is that they are schemas for output or input files (and can thus be serialized to HDF5, FITS, or database tables).  So making them fit into that context is important.

See also my proposal for typed fields: #501

Yes, perhaps we should wait until the typed fields are implemented, and then we can re-evaluate the contents.

It was decided in Annecy that we will change the container hierarchy such that the event containers only contain things that change per-event, and there will be a separate header (better name hopefully) container that has the instrument and other observation-specific information inside it.


Is there any way to express service dependencies so that kubectl creates them in order?

I have 2 services. One containing 2 pod replicas for a web application which is dependent on another backend service having pod (2 replicas) for mysql containers.
Web application uses environment variables set by backend db service. I've all the json inside same directory.
Is there any way to express the dependencies so that kubectl always create (and run) backend pods and services before it starts the web application service?

Short answer is not yet. Discussion is here: https://github.com/GoogleCloudPlatform/kubernetes/issues/1768#issuecomment-69665834
I recommend creating all services before any replication controllers.


Create template FTL directive

Create a new FTL directive with the following syntax:
<@template name = "my_template"/>

that describes the template's name and (possibly in future) its other attributes.
The directive outputs nothing, but prints a warning message in stderr if the described template name doesn't coincide with the name by wich the template was found by the template loader.

Done.


Link to Pango lineage

Github request: add a hotlink to https://github.com/cov-lineages/pango-designation/blob/master/lineage_notes.txt everywhere that it says “Pango lineage”, since I often go there to figure out who is descended from whom quickly. [Very minor, but I’m trying the Slack->Github posting.]
Slack Message

This is fantastic, though I must say I find it a bit confusing since it doesn't really show recent relationships between lineages. For example, for DN.1 it says:
DN.1	Alias of B.1.1.5<IP_ADDRESS>.<IP_ADDRESS>.1.5.1, S:K147N
so its not clear that is a descendant of BQ.1.1.5 - unless you know to look at BQ.1.1.5 and can see that it is:
BQ.1.1.5	Alias of B.1.1.5<IP_ADDRESS>.<IP_ADDRESS>.1.5, ORF1b:P2313L, ORF1a:V3855I
So, this is great, but it would be wonderful if it would also list what the variant before it is i.e.
DN.1	Descendant of BQ.1.1.5, Alias of B.1.1.5<IP_ADDRESS>.<IP_ADDRESS>.1.5.1, S:K147N
Then you can see the variant growing even when its being mispredicted or the lineage assignments aren't updated yet (such as for DN.1.1.1 right now)
Technically we could build such a table in an automated way, or mention it to them... :)

Where do you find that descendant information?

Here is an example of what should be printed automatically
DR:	DR is BQ.1.1.3, BQ is BE.1.1.1, BE is BA.5.3.1, BA is B.1.1.529
Here is a bash oneliner that should generate all the difinitions from the pangolineage file
cat data_needed/pango_designation_alias_key_viralai.tsv | grep -v lineage | sort -k2,2 | awk '{actualP=$2;is="";for(i=NR-1;i>0;i--){re="^"p[n[i]]"[^0-9]";if(actualP~re){gsub(p[n[i]],n[i],actualP);is=", "t[n[i]]""is}}n[NR]=$1;p[$1]=$2;t[$1]=$1" is "actualP""is;printf "%s:\t%s\n",$1,t[$1]}'

Update of the one liner :
cat data_needed/pango_designation_alias_key.tsv | grep -v lineage | sort -k2,2 | awk '{actualP=$2;is="";for(i=NR-1;i>0;i--){re="^"p[n[i]]"[^0-9A-Z]";if(actualP~re){gsub(p[n[i]],n[i],actualP);is=", "t[n[i]]""is}}n[NR]=$1;p[$1]=$2;t[$1]=$1" is "actualP""is;printf "%s:\t%s\n",$1,t[$1]}'


Fix SyntaxError: JSON.parse

@changeworld : Thanks for your contribution! The author, @cynthn, has been notified to review your proposed change.


README updates

Added some additional steps to the readme for proper developer setup.

python3 and sqlite3 requirement
virtualenv for environment isolation
loading data into database from fixture
a test URL for making sure the project is running properly

Current coverage is 94.95% (diff: 100%)

Merging #152 into master will not change coverage

@@             master       #152   diff @@
==========================================
  Files            29         29
  Lines           832        832
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            790        790
  Misses           42         42
  Partials          0          0

Powered by Codecov. Last update eba19d4...97fe5da


Remote config fetch callback not called on iOS 10

Xcode version: 11.4.1
Firebase SDK version: 6.24.0
Firebase Component: Remote Config
Installation method: CocoaPods

I'm facing an issue in my project, everything used to work completely fine, but recently while the app is live, we suddenly started facing crashes and those crashes are only on iOS 10 devices! I debugged the code to try to figure out the problem, and I discovered that the Remote Config values are not being fetched at all on iOS 10! While everything is working totally fine on the newer iOS versions. I don't exactly know if the Remote Config case is what caused the crashes.
The fetch callback of "RemoteConfig.remoteConfig().fetch(withExpirationDuration:)" is not being called at all, and this is only on iOS 10 devices.
Below is a sample of my code....
static var loadingDoneCallback: (() -> Void)?
static var fetchComplete = false
static private let config = RemoteConfig.remoteConfig()

class func fetchCloudValues() {

    let fetchDuration: TimeInterval = 0
    config.configSettings = RemoteConfigSettings.init()
    config.fetch(withExpirationDuration: fetchDuration) { (_, error) in
        if let error = error {
            AnalyticsManager.logEventToFireBase(eventName: "ios_remote_config_fetching_error", parameters: ["error":error.localizedDescription])
            return
        }
        config.activate { (err) in
            if let err = err {
                AnalyticsManager.logEventToFireBase(eventName: "ios_remote_config_activation_error", parameters: ["error":err.localizedDescription])
            }
            fetchComplete = true
            loadingDoneCallback?()
        }
    }
}

Please help, Thanks a lot!

This might be an incarnation of an Xcode 11.4.* armv7 optimizer bug. More details in #5233
The workaround is building with any non-Xcode 11.4.* version.

Firstly, Thank you so much for your help.
I downloaded Xcode 11.3.1 and build it and everything worked completely fine!
As a developer, the last thing I would expect is to face a bug like that on Xcode. I'm so thankful that the problem is solved.


Source member not showing

I created a filter 1, to display all objects in my library.  It returned a list with "undefined"
I created another filter - filter 2, to display source members.  The filter is returning empty list
Both filter should objects that I can work with.
OS Version is 7.3
VS Code is
Version: 1.78.1 (user setup)
Commit: 6a995c4f4cc2ced6e3237749973982e751cb0bf9
Date: 2023-05-04T09:48:08.683Z
Electron: 22.5.1
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19044
Sandboxed: Yes
plugin -  Code for IBM i,  Version is 1.8.0
I have attached some screen shots

Please share the contents of your Code for IBM i output channel after the list appears.

Hi Barry
I reply to the email.  I was not sure if I got all the attachments.
Here is the output you requested.  I have also attached the output from
those command
I also attached the IFS list and its output as well
Thanks

@Nithy29 you're almost there. I really just need you to copy and paste the output into this issue. Thanks!

.: pwd
{
"code": 0,

"signal": null,

"stdout": "/home/VA967",

"stderr": ""

}
/home/VA967: pwd
{
"code": 0,

"signal": null,

"stdout": "/home/VA967",

"stderr": ""

}
/home/VA967: /QOpenSys/usr/bin/qsh
liblist
{
"code": 0,

"signal": null,

"stdout": "RISCSYSLIB  SYS\nQSYS        SYS\nQSYS2       SYS\nQHLPSYS     SYS\nQUSRSYS     SYS\nQFNTCPL     SYS\nBNSOPR      SYS\nQSHELL      PRD\nBNSOPR3     USR\nUGLOBAL     USR\nFTP         USR\nQGPL        USR\nQTEMP       USR",

"stderr": ""

}
/home/VA967: system "CRTLIB LIB(ILEDITOR) TEXT('Code for i temporary objects. May be cleared.')"
{
"code": 255,

"signal": null,

"stdout": "",

"stderr": "CPF2111: Library ILEDITOR already exists."

}
/home/VA967: [ -d "/tmp" ]
{
"code": 0,

"signal": null,

"stdout": "",

"stderr": ""

}
/home/VA967: ls -p /QOpenSys/pkgs/bin/
{
"code": 0,

"signal": null,

"stdout": "[\nalternatives\natob\nbase32\nbase64\nbasename\nbash\nbashbug\nbtoa\nc2ph\ncat\ncertutil\nchcon\nchgrp\nchmod\nchown\nchroot\nchsh\ncksum\ncmsutil\ncomm\ncorelist\ncp\ncpan\ncrlutil\ncsplit\ncurl\ncut\ndate\ndd\ndebuginfo-install\nderdump\ndf\ndir\ndircolors\ndirname\ndu\necho\nenc2xs\nencguess\nenv\nexpand\nexpr\nfactor\nfalse\nfind-repos-of-install\nfmt\nfold\ngroups\nh2ph\nh2xs\nhead\nhostid\nid\ninstall\ninstmodsh\njoin\njson_pp\nkill\nlibnetcfg\nlink\nlistsuites\nln\nlogname\nls\nmd5sum\nmkdir\nmkfifo\nmknod\nmktemp\nmodutil\nmv\nneeds-restarting\nnice\nnl\nnohup\nnproc\nnss-policy-check\nnumfmt\nocspclnt\nod\npackage-cleanup\npaste\npathchk\nperl\nperl5.24.1\nperlbug\nperldoc\nperlivp\nperlthanks\npiconv\npinky\npk12util\npl2pm\npod2html\npod2man\npod2text\npod2usage\npodchecker\npodselect\npp\npr\nprintenv\nprintf\nprove\npstruct\nptar\nptardiff\nptargrep\nptx\npwd\npydoc\npython\npython2\npython2.7\nreadlink\nrealpath\nrepo-graph\nrepo-rss\nrepoclosure\nrepodiff\nrepomanage\nrepoquery\nreposync\nrepotrack\nrm\nrmdir\nrpm\nrpm2archive\nrpm2cpio\nrpmdb\nrpmgraph\nrpmkeys\nrpmquery\nrpmsign\nrpmverify\nruncon\nselfserv\nseq\nsha1sum\nsha224sum\nsha256sum\nsha384sum\nsha512sum\nshasum\nshow-changed-rco\nshow-installed\nshred\nshuf\nsigntool\nsignver\nsleep\nsmtpd.py\nsort\nsplain\nsplit\nssltap\nstat\nstdbuf\nstrsclnt\nstty\nsum\nsymkeyutil\nsync\ntac\ntail\ntee\ntest\ntimeout\ntouch\ntr\ntrue\ntruncate\ntrust\ntsort\ntstclnt\ntty\nuname\nunexpand\nuniq\nunlink\nupdate-alternatives\nupdate-ca-certificates\nuptime\nurlgrabber\nusers\nvdir\nverifytree\nvfychain\nvfyserv\nwc\nwho\nwhoami\nxsubpp\nyes\nyum\nyum-builddep\nyum-complete-transaction\nyum-config-manager\nyum-debug-dump\nyum-debug-restore\nyum-groups-manager\nyumdb\nyumdownloader\nzipdetails",

"stderr": ""

}
/home/VA967: ls -p /usr/bin/
{
"code": 0,

"signal": null,

"stdout": "ARS3WAPI64\nARS3WCGI\nARS400IDX\nARSADM\nARSADMIN\nARSDATE\nARSDB\nARSDOC\nARSEXPRT\nARSFTERM\nARSLOAD\nARSLOG\nARSLSYNC\nARSMAINT\nARSODF\nARSPRT400\nARSRPT\nARSSLU\nARSSMTSM\nARSSTASH\nARSSYSCR\nARSTBLSP\nARSTFMT\nARSUSEC\nARSWWW\nARSWWWSL32\nARSXAPI\nARSXML\nRfile\najar\nappletviewer\napt\narmsrv\narmsrvconv\narspdoci\narspdump\narsxafp\narsxline\nattr\nbasename\nbash\nbison\ncat\ncatsplf\nchgrp\nchmod\nchown\nclrtmp\ncmp\ncompress\ncp\ncpio\ncut\ndataq\ndatarea\ndate\ndb2\ndb2profc\ndb2profc_trace\ndb2profp\nddns-confgen\ndel\ndelv\ndfmadmin\ndhcpd\ndhcrelay\ndig\ndirname\ndnssec-dsfromkey\ndnssec-importkey\ndnssec-keyfromlabel\ndnssec-keygen\ndnssec-revoke\ndnssec-settime\ndnssec-signzone\ndnssec-verify\ndspmsg\necho\negrep\nenv\nexpr\nextcheck\nfgrep\nfile\nfind\nflex\ngawk\ngencat\ngetjobid\ngmake\ngrep\ngunzip\ngzip\nhead\nhost\nhostname\nhttpapi\nhwkeytool\nicc\niconv\nid\nidlj\nikeyman\nipcrm\nipcs\nixlc\njar\njarsigner\njava\njavac\njavadoc\njavah\njavap\njconsole\njdb\njdmpview\njextract\njpzip/\nkdestroy\nkeytab\nkeytool\nkinit\nklist\nkpasswd\nksetup\nld\nldapadd\nldapchangepwd\nldapcompare\nldapdelete\nldapdiff\nldapexop\nldapmodify\nldapmodrdn\nldapsearch\nln\nlocale\nlogger\nlogname\nls\nmkdir\nmkfifo\nmv\nnamed\nnamed-checkconf\nnamed-checkzone\nnamed-compilezone\nnamed-journalprint\nnamed-rrchecker\nnative2ascii\nnohup\nnslookup\nnsupdate\nod\norbd\npack200\npax\nperl\npolicytool\npr\nprintenv\nprofconv\nprofdb\nprofp\nps\npwd\npwdx\nqar\nqsh\nrexec\nrexx\nrm\nrmdir\nrmic\nrmid\nrmiregistry\nrndc\nrndc-confgen\nschemagen\nsed\nserialver\nservertool\nsetccsid\nsh\nsort\nsplit\nsqlj\nstrEKM\nsystem\nsysval\ntail\ntar\ntee\ntest\ntnameserv\ntouch\ntr\ntsig-keygen\nuname\nuncompress\nuniq\nunpack200\nunzip\nwc\nwsgen\nwsimport\nxargs\nxjc\nzcat\nzip",

"stderr": ""

}
/home/VA967: ls -p /QSYS.LIB/QZDFMDB2.PGM
{
"code": 0,

"signal": null,

"stdout": "/QSYS.LIB/QZDFMDB2.PGM",

"stderr": ""

}
/home/VA967: ls -p /QIBM/ProdData/IBMiDebugService/bin/startDebugService.sh
{
"code": 2,

"signal": null,

"stdout": "",

"stderr": "/QIBM/ProdData/IBMiDebugService/bin/startDebugService.sh not found"

}
/home/VA967: ls -p /QSYS.lib/ILEDITOR.lib/GE*.PGM
{
"code": 0,

"signal": null,

"stdout": "/QSYS.lib/ILEDITOR.lib/GENCMDXML.PGM\n/QSYS.lib/ILEDITOR.lib/GETNEWLIBL.PGM",

"stderr": ""

}
/home/VA967: echo $SHELL
{
"code": 0,

"signal": null,

"stdout": "/QOpenSys/pkgs/bin/bash",

"stderr": ""

}
/home/VA967: LC_ALL=EN_US.UTF-8 system "call QSYS/QZDFMDB2 PARM('-d' '-i' '-t')"
select OS_VERSION || '.' || OS_RELEASE as VERSION from sysibmadm.env_sys_info
/home/VA967: LC_ALL=EN_US.UTF-8 system "call QSYS/QZDFMDB2 PARM('-d' '-i' '-t')"
select max(ptf_group_level) as HIGHEST_DB2_PTF_GROUP_LEVEL from qsys2.group_ptf_info where PTF_GROUP_DESCRIPTION like 'DB2 FOR IBM I%' and ptf_group_status = 'INSTALLED';
{
"code": 0,

"signal": null,

"stdout": "DB2>\n  ?>\n\nVERSION                                                                                \n---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\n7.3                                                                                \n\n  1 RECORD(S) SELECTED.",

"stderr": ""

}
{
"code": 0,

"signal": null,

"stdout": "DB2>\n\nHIGHEST_DB2_PTF_GROUP_LEVEL \n----------------------------\n                          27\n\n  1 RECORD(S) SELECTED.\n\nDB2>",

"stderr": ""

}
/home/VA967: system "DSPFD FILE(VA967/*ALL) TYPE(*ATR) FILEATR(*PF) OUTPUT(*OUTFILE) OUTFILE(ILEDITOR/O_ykeme4db)"
{
"code": 0,

"signal": null,

"stdout": "CPF9861: Output file O_YKEME4DB created in library ILEDITOR.\nCPF9862: Member O_YKEME4DB added to output file O_YKEME4DB in library ILEDITOR.\nCPF3030: 47 records added to member O_YKEME4DB in file O_YKEME4DB in ILEDITOR.",

"stderr": ""

}
/home/VA967: system "QSYS/CPYTOIMPF FROMFILE(ILEDITOR/O_ykeme4db O_ykeme4db) TOSTMF('/tmp/vscodetemp-O_ChlndMOb') MBROPT(*REPLACE) STMFCCSID(1208) RCDDLM(*CRLF) DTAFMT(*DLM) RMVBLANK(*TRAILING) ADDCOLNAM(*SQL) FLDDLM(',') DECPNT(*PERIOD)"
{
"code": 0,

"signal": null,

"stdout": "",

"stderr": ""

}

It looks like from your first screenshot that the column names are missing. Can you run this and share the resulting streamfile (/tmp/issue1286)?

DSPFD FILE(VA967/*ALL) TYPE(*ATR) FILEATR(*PF) OUTPUT(*OUTFILE) OUTFILE(QTEMP/ABCD)
QSYS/CPYTOIMPF FROMFILE(QTEMP/ABCD ABCD) TOSTMF('/tmp/issue1286') MBROPT(*REPLACE) STMFCCSID(1208) RCDDLM(*CRLF) DTAFMT(*DLM) RMVBLANK(*TRAILING) ADDCOLNAM(*SQL) FLDDLM(',') DECPNT(*PERIOD)

Hi Allan,
sorry for taking long. I have to extract data from my work laptop and then email to my personal to upload to git.  My organization does not allow me to upload to git
Thanks
issue1286.txt

yes...

I am using the ADDCOLNAM(*SQL).  I also tried *SYS.  Both did not include the column names

@Nithy29 Just some follow-up questions:

Do you have SQL enabled on the connection?
Did you at any time see this error message: The data area QSYS/QCPTOIMPF exists on this system and may impact Code for IBM i functionality.?
If you right-click the connection and select Connect and Reload Server Settings, do you get the error mentioned above?

Just to ensure that our check for the data actually works - it should have caught this error!

Hi Christian
Yes I have the SQL enabled.
There were no errors regarding the data area  QCPTOIMPF or any sort.  Barry mention that the IFS file created by CPYTOIMPF did not include the heading names.  So I search for errors related to this. I found a post that was dealing with column name not included when using the CPYTOIMPF.
Here is the link
https://archive.midrange.com/midrange-l/201903/msg00678.html
This article is from midrange community
Hope this helps

Sorry I gave the wrong thread of the post
https://archive.midrange.com/midrange-l/201903/msg00679.html

Hi Christian
I don't think its anything related to Code for IBM i.   I believe the data area is part of OS to control the backward compatibility.   But may be you can mention this in the documentation as a check point
Thanks

Hi
I did what you told me and I received the warning message. Ir also gave me
an option to delete.
But I did not receive this error when I created the connection.
Hope this helps
Thanks
On Tue, May 16, 2023, 5:01 p.m. Christian Jorgensen <
@.***> wrote:

@Nithy29 https://github.com/Nithy29 Code for IBM i depends on correct
function of the CPYTOIMPF command (and the CPYFRMIMPF command), and we have
a check at connection time for these two data areas in QSYS. And this check
should have warned you about this situation and avoided you having to
create an issue. That's why I'm pursuing this...
The data areas are described in this IBM Support note
https://www.ibm.com/support/pages/cpyfrmimpf-and-cpytoimpf-data-areas.
And as they state, these data areas should be avoided and
customers need to completely get away from using the 'CPV5R2' data areas
because they are only temporarily allowed and may be removed at a release
boundary in the future.
Whats happens if you right-click the connection and select Connect and
Reload Server Settings, do you get a warning about these data areas? If
not, I will have to investigate further...
—
Reply to this email directly, view it on GitHub
https://github.com/halcyon-tech/vscode-ibmi/issues/1286#issuecomment-1550356385,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXO26HH64UTZ2X6NGTH2ABDXGPTJVANCNFSM6AAAAAAYCUIYZQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Nithy29 Thanks for verifying the check is still working as expected. We (the support team) must have this reload option in mind, when issues like this are reported.
Thanks again!


Prepare v2.0.0 release

@Flamefire I believe a v2.0.0 makes sense, as there are definitely some breaking changes.
Can you think of more changes than those listed here off the top of your head?

coverage: 99.596%. remained the same
when pulling 2a0f20666879ebabc9863a99d6e05fecb29de3ad on prepare-release
into a3c9605237e971b2da222cbec9032aef68bf4cb0 on main.


Batch breakdown can't see data

The new batch breakdown make it hard to see the numbers.

Already reverted in #334


Timezone check

[x] Add no-optional and isort
[x] Bump python version
[ ] Methods to check timezone

Codecov Report
Base: 89.04% // Head: 89.04% // No change to project coverage :thumbsup:

Coverage data is based on head (988b063) compared to base (b357785).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #19   +/-   ##
=======================================
  Coverage   89.04%   89.04%
=======================================
  Files           3        3
  Lines         219      219
=======================================
  Hits          195      195
  Misses         24       24

Impacted Files
Coverage Δ

regta_period/__init__.py
100.00% <100.00%> (ø)

regta_period/periods.py
88.05% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Update org.spyder_ide.spyder.appdata.xml to include content-rating, url, and releases

Update appdata to include content-rating, url, and releases.
Re-opened to pull request to 5.x release.

Description of Changes
This change add more information to appdata. This appdata are used by distributors to enhance their metadata.
This is part of an effort to ship Spyder to Flathub.
https://github.com/spyder-ide/spyder/issues/6898
https://github.com/flathub/flathub/pull/4344

[ ] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)

[ ] Included a screenshot or animation (if affecting the UI, see Licecap)

Issue(s) Resolved

Fixes #
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: Kavin Teenakul

nope


Dont populate cf-routes if CC does not send routes

This PR fixes a bug when a user deletes a route mapping, it updates the existing LRP's route to have a default port of 8080 and an empty hostname.

Don't send empty CF-Route to Diego if CC does not provide an http route.

Tracker story:
https://www.pivotaltracker.com/story/show/112640495
@leochu and @shashwathi
CF Routing Team

Thanks, @shashwathi and @leochu! Seems reasonable, I'll prioritize it for the Diego team to evaluate.


Proxy that requires authentication not working with helm init

Hello, I just started using Helm.  I've run into an issue.  My organization's proxy requires authentication, and I've set up my environment variables like so:
http_proxy=http://<my username>:<my password>@proxy.com:80/
https_proxy=http://<my username>:<my password>@proxy.com:80/

When I try to execute helm init, I get the following:
Creating /home/ssa-dev/.helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Error: error initializing: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Get https://kubernetes-charts.storage.googleapis.com/index.yaml: invalid proxy URL port "<first five characters of my password>"

It looks like Helm is assuming my password is the proxy port since it follows a colon, but that's just conjecture.  Any ideas?
Output of helm version:
Client: &version.Version{SemVer:"v2.14.2", GitCommit:"a8b13cc5ab6a7dbef0a58f5061bcc7c0c61598e7", GitTreeState:"clean"}
Error: could not find tiller

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.1+5115d708d7", GitCommit:"fff65cf", GitTreeState:"clean", BuildDate:"2018-07-09T18:09:52Z", GoVersion:"go1.7.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.1+5115d708d7", GitCommit:"fff65cf", GitTreeState:"clean", BuildDate:"2018-07-09T18:09:52Z", GoVersion:"go1.7.6", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):  RedHat OpenShift Container Platform v3.11.82

cc @jdolitsky

@mtelewicz I'm not sure where those proxy env vars come into play, it isn't something I believe that Helm recognizes.
What you can do is override the stable URL with the --stable-repo-url flag.
I've tested this works with basic auth as well, for example running a chartmuseum on port 8080 with basic auth:
docker run --rm -it \
  -p 8080:8080 \
  -e DEBUG=1 \
  -e STORAGE=local \
  -e STORAGE_LOCAL_ROOTDIR=/charts \
  -e BASIC_AUTH_USER=user \
  -e BASIC_AUTH_PASS=pass \
  -v $(pwd)/charts:/charts \
  chartmuseum/chartmuseum:v0.9.0

I can then do:
$ rm -rf ~/.helm/repository/
$ helm init --stable-repo-url=http://user:pass@localhost:8080 --client-only
Creating /Users/jdolitsky/.helm/repository
Creating /Users/jdolitsky/.helm/repository/cache
Creating /Users/jdolitsky/.helm/repository/local
Creating /Users/jdolitsky/.helm/repository/repositories.yaml
Adding stable repo with URL: http://user:pass@localhost:8080
Adding local repo with URL: http://<IP_ADDRESS>:8879/charts
$HELM_HOME has been configured at /Users/jdolitsky/.helm.
Not installing Tiller due to 'client-only' flag having been set

I would guess this should work for your proxy URL as well, please let us know

I'm going to close this ticket due to inactivity, but please re-open if this still needs to be addressed. Thanks!


Fix TLS

Fixes #30

@shailesh91 fixed the casesensitivity.
ready to merge?

@spitzerr Not yet. I have to test a lot of things and make a few changes. I have to add fallback in case only the certificates are specified at the server or portal block level.

@spitzerr Do you have any concerns about the new implementation?

@shailesh91 you made lots of changes to this. I Need more time to Review this. But I'll give you Feedback as soon as I looked it over

@spitzerr I agree with your first point. I will make the necessary change. As for the third probably the external DNS name parameter is not being set. Can you tell me what config where you using?
As for the second point, I agree that it is twice the work since 90% of the code base is same. But it is really hard to maintain a single code base for two configurations as their workings are very different. It is likely it will become less accessible and very hard to maintain over time. But since you have brought it up I will consult Nikhil about your concern.

@shailesh91 I attach my config for this. Maybe you could Elaborate the missing part:
config.json.txt
Thank you very much in advance.

@spitzerr One last thing to do, Add a self-signed cert to Portal Block (here) . Once that is done I think we are good to merge

@shailesh91 The Portal Comes with a Self-Signed cert Out of the box. From my perspective there is nothing to do in this case. Or do I miss something?

@spitzerr from my understanding, when you install for the first time I don't think so there is a certificate installed. But to be sure, I will confirm this once.

@shailesh91 if you install server or portal both of them bring certificates (self signed) OoB. Only WebAdaptor needs an handmade cert as it integrates in 3rd party webserver.

@spitzerr Just confirmed this. The Server and Portal creates a Self Signed Certificate at Service startup time if it is not installed already.

@spitzerr Everything else looks good. One thing that I saw happening is, the Urls printed out at the end are wrong. Just need to fix those.


Remove _logviewer

Remove _logviewer directory.
It contains abandoned project that never has been finished. We do not plan to invest into this.
Let's do some cleanup here.
/assign @marseel

/lgtm
/approve


Move blower_fsm implementations into cpp file.

Commits in this PR

Move blower_fsm implementations into cpp file.
Main motivation is to allow us to declare constants and functions that
are "private" to the file.

PR chain

#475 Update to new 3/4" Venturi specifications.
#483 Move flow zeroing into TVIntegrator.
#485 Units: Allow x / y to return a raw ratio.
👉 #486 Move blower_fsm implementations into cpp file. 👈 YOU ARE HERE

⚠⚠ Please do not click the green "merge" button unless you know what
you're doing.  This PR is part of a chain of PRs, and clicking the merge
button will not merge it into master. ⚠⚠

cc @asmodai27


Segmentation Annotation

If we use auto segmentation, how do I correct generated polygon points ? It is very tedious task to correct the predicted annotations as I can not select multiple points. Is there a way to deal with this problem ? Like group small regions or eraser or paint brush like tool ?

Hi @gaussiangit, in the newest version you can edit polygons in following ways:

Move points one by one
Move the whole polygon
Delete a point of a polygon (Ctrl + Click on a point)
Redraw a border of a polygon (Shift + Click on a point)
Redraw a whole polygon from scratch (Shift + N when a polygon is selected)

We do not support tools like brush. There were ideas to support masks as is (not like polygons) but we do not expect it will have been done in the nearest future. If you have other ideas how we could significantly accelerate the process and you are ready to provide details, you are welcome


How can I use vue-router along with async components for lazy loading?

Is there an example I can follow?

It's exactly like async components with Vue.js only: http://vuejs.org/guide/components.html#Async_Components
You can write:
import Vue from 'vue';
import VueRouter from 'vue-router';
import config from 'config';

Vue.use(VueRouter)

const router = new VueRouter({history: true, root: config.root});

router.map({
    '/': {
        name: 'home',
        component: view('home')
    },
    '/user/:oid/': {
        name: 'user',
        component: view('user')
    },
    '/post/new/': {
        name: 'new-post',
        component: view('post-wizard')
    },
    '/post/:oid/': {
        name: 'post',
        component: view('post')
    }
});

/**
 * Asynchronously load view (Webpack Lazy loading compatible)
 * @param  {string}   name     the filename (basename) of the view to load.
 */
function view(name) {
    return function(resolve) {
        require(['./views/' + name + '.vue'], resolve);
    }
};

export default router;

In my case, routable views always have views/name.vue as filename pattern.
Just adapt to your needs.

Hi noirbizarre,
Thanks for your solution! I have a question, and vue.js is very new to me; using your function it creates a new .js file with the four components above combined, for example (home, user, post-wizard and post). Doesn't this defeat the purpose of lazy loading by loading everything into one external file? Shouldn't they each be in a separate .js file? Sorry if I've misunderstood something.
Thanks

No that's the point, using this pattern with webpack is compatible with code splitting (http://webpack.github.io/docs/code-splitting.html).
Each view is in its own vue file (using vue-loader) and webpack will detect the pattern './views/' + name + '.vue' as a code splitting point and will create chunks for each (depending of your webpack configuration) that will be lazy loaded on first access (when you hit the route).

I mean shouldn't each vue component be split into multiple build .js files instead of merging the chunks into one build .js file? How does the lazy loading work if it loads a .js file containing all component chunks?
Thanks for your help explaining

The all-in-one file is created by the context ('./views/' + name + '.vue')
If you don't want that, rewrite it like that:
import Vue from 'vue';
import VueRouter from 'vue-router';
import config from 'config';

Vue.use(VueRouter)

const router = new VueRouter({history: true, root: config.root});

router.map({
    '/': {
        name: 'home',
        component: function(resolve) {
            require(['./views/home.vue'], resolve);
        }
    },
    '/user/:oid/': {
        name: 'user',
        component: function(resolve) {
             require(['./views/user.vue'], resolve);
        }
    }
});

export default router;

Each require([], resolve) will create a split point and a lazy loaded chunk.

Thanks @noirbizarre for the explanation :)

You're welcome ;)

hi @noirbizarre when I try your method above, each route I replace with the async function renders the view broken and the view will no longer load. In the dev console in chrome it just says 'Uncaught SyntaxError: Unexpected token <' when I try to change to a new asynchronously loaded view. What could be the problem?
Many thanks

I don't think this is related to async loading.
There might be a syntax error in one of your loaded view.
Without code sample I can't find the syntax error.
Given the fact it happen on every view you try to load and given the unexpected token is <, I'm wondering if your vue-loader is correctly configured in webpack.

Cool stuff here :)

My webpack.config.js file is as follows:
var webpack = require('webpack');
var path = require('path');
//var CommonsChunkPlugin = require("webpack/lib/optimize/CommonsChunkPlugin");
module.exports = {
	cache: true,
	entry: {
		'init': "./src/init.js"
	},
  output: {
      path: './dist/js',
      filename: "[name].js",
      chunkFilename: "[chunkhash].js"
  },
  module: {
    preLoaders: [
      {
        test: /\.js$/,
        loader: 'eslint-loader',
        exclude: /(node_modules|bower_components)/
      }
    ],
    loaders: [
      {
        test: /\.vue$/,
        loader: 'vue'
      },
      {
        test: /\.js$/,
        exclude: /(node_modules|bower_components)/,
        loader: 'babel',
        query: {
            presets: ['es2015']
        }
      }
    ]
  },
  resolveLoader: {
      root: path.join(__dirname, 'node_modules')
  },
	plugins: [
		new webpack.ProvidePlugin({
			jQuery: "jquery",
			$: "jquery"
		})
	]
};

Weird because I have this pattern on my app and it's working.
The only difference is that I sticked on vue-loader 4.0.5 because 7.0.x is not working for me.

This is exactly what I need, really helpful. webpack code splitting is great.

Thank you for this. The webpack code splitting feature really is amazing!

Thank you for this.
感谢，解决了我的问题。

Exactly what I'm looking for! Thank you!

This worked excellent, thanks!
ES6:
const view = (name) => (resolve) => { require(['./components/' + name + '.vue'], resolve) }

@noirbizarre I'm having a similar issue, the difference is that my components are not inside a single directory where I can just pass in the name of the component I need to load, so what I was trying to do is passing the component path, however if I do that i get the following error:
Critical dependencies:
8:11-10:6 the request of a dependency is an expression

my method looks like this:
export const asyncLoader = path => {
  return resolve => require([path], m => resolve(m.default));
};

Notice I need to call resolve passing in m.default because my components are js files that use export default, so when they are required it gives an object {default: (your component)}
The method is being used like this:
import {asyncLoader} from "services";

export const aboutRoute = {
  path: "/about", component: asyncLoader("app/about/about.vue.js")
};

Notice that my components are not .vue files (at least not the route components)
Any suggestions how to get around the fact that Webpack needs to be able to read all require paths statically so just passing a parameter with the path doesn't work...
Thanks..

@noirbizarre Thanks  for the solution.
And I notice that you have no reject callback, I find that webpack2 has the reject callback,and it works well.For webpack1,you can use this plugin: require-error-handler-webpack-plugin.It has been a long time since you gave this  solution. Maybe you have found some more excellent solutions.
But I also have a question:
How to deal with the timeout of the require?
You konw that , when the network is bad， this maybe a long time to request the components.So i want to find out how can I set the timeout time,just like a ajax request.
At last , sorry for my poor English.

Hello everyone i tried this solution and it works perfectly on my code  by i have a doubt
do you know if you can load a component totally from another server for example i have this gist
https://gist.githubusercontent.com/shagflak/c9ab75ca4b811c04472169c724509335/raw/aa77f928b79c73d99d8c89e75da6a974c0903e22/users.vue
And i will like to lazy load this coponent remotely for example that component living on another server and ask for it to deploy it on my app like this on my main .js file i am currently using vue-cli webpack template
import Vue from 'vue'
import Router from 'vue-router'
import Hello from '@/components/Hello'
// import Users from '@/components/Users'

Vue.use(Router)

/**
 * Asynchronously load view (Webpack Lazy loading compatible)
 * @param  {string}   name     the filename (basename) of the view to load.
 */
function view (name) {
  return function (resolve) {
    // require(['../components/' + name + '.vue'], resolve)
    require(['https://gist.githubusercontent.com/shagflak/c9ab75ca4b811c04472169c724509335/raw/aa77f928b79c73d99d8c89e75da6a974c0903e22/' + name + '.vue'], resolve)
  }
}

export default new Router({
  routes: [
    {
      path: '/',
      name: 'Hello',
      component: Hello
    },
    {
      path: '/users',
      name: 'Users',
      // component: view('Users')
      component: view('users')
    }
  ]
})

It is posssible to do this? i had done some research and it looks like it's not possible but i am not really sure if it is because the require of webpack code splitting can't do that when running this code i get this warning on my console
This dependency was not found:

 https://gist.githubusercontent.com/shagflak/c9ab75ca4b811c04472169c724509335/raw/aa77f928b79c73d99d8c89e75da6a974c0903e22 in ./src/router/index.js

To install it, you can run: npm install --save https://gist.githubusercontent.com/shagflak/c9ab75ca4b811c04472169c724509335/raw/aa77f928b79c73d99d8c89e75da6a974c0903e22

I don't really think this will work with publicPath either because that it's only for assets called within thebrowser once everything it's compiled any response on this will be appreciatted.
Thanks for the help.

I had to replace in order to make it work with the most recent Webpack, Vue and Vue Router. Had to change require to System.import, whick returns a Promise, then I fire the callback and it do works.

My view() function:
function view(name) {   return function(resolve) {     System.import(./views/${name}.vue).then(mod => {       resolve(mod)     })   } }

what does import config from 'config'; mean.? I'm getting error

I use the view method to lazyload vue component, but has error:
Error: Failed to resolve async component default: AssertionError: path must be a string
    at /Users/Silence/Desktop/electron-demo/jdquant-client/node_modules/_vue-router@2.7.0@vue-router/dist/vue-router.js:1708:17
    at /Users/Silence/Desktop/electron-demo/jdquant-client/node_modules/_vue-router@2.7.0@vue-router/dist/vue-router.js:1766:15
    at /Users/Silence/Desktop/electron-demo/jdquant-client/node_modules/_vue-router@2.7.0@vue-router/dist/vue-router.js:1717:11
    at /Users/Silence/Desktop/electron-demo/jdquant-client/node_modules/_vue-router@2.7.0@vue-router/dist/vue-router.js:1742:66
    at Array.map (native)
    at /Users/Silence/Desktop/electron-demo/jdquant-client/node_modules/_vue-router@2.7.0@vue-router/dist/vue-router.js:1742:38
    at Array.map (native)
    at flatMapComponents (/Users/Silence/Desktop/electron-demo/jdquant-client/node_modules/_vue-router@2.7.0@vue-router/dist/vue-router.js:1741:26)
    at /Users/Silence/Desktop/electron-demo/jdquant-client/node_modules/_vue-router@2.7.0@vue-router/dist/vue-router.js:1677:5
    at iterator (/Users/Silence/Desktop/electron-demo/jdquant-client/node_modules/_vue-router@2.7.0@vue-router/dist/vue-router.js:1876:7)

Above that lazy load must rely on webpack? While, I am not use it.
I am trying many way, but there is no way to work properly. such as:

'use strict';
import Vue from 'vue/dist/vue.js';
import Router from 'vue-router/dist/vue-router.js';

Vue.use(Router);

let router = new Router({
    routes: [
        {
            path: '/',
            redirect: '/index'
        },
        {
            name: 'login',
            path: '/login',
            // component: require('./components/Login.vue') //working
            // component: resolve => System.import('./components/Login.vue') //not working
            // component: () => import('./components/Login.vue')  //not working
            component: view('Login')  //not working
        },
        {
            name: 'test',
            path: '/test/:userId',
            component: resolve => require(['./components/Test.vue'], resolve)  //not working
        },
        {
            path: '*',
            redirect: '/'
        }
    ]
});

/**
 * Asynchronously load view (Webpack Lazy loading compatible)
 * @param  {string}   name     the filename (basename) of the view to load.
 */
function view(name) {
    return function(resolve) {
        require(['./components/' + name + '.vue'], resolve);
    }
};

export default router;

Can your help me point out the mistake? Thanks! waiting...

another approach without playing with require/import:
main.js
import subfolder1 from './components/subfolder1/index'

const componentsMap = {
    'subfolder1': subfolder1
}
const getComponent = (subfolder, name) => {
  return (resolve) => {
    resolve(componentsMap[subfolder][name])
  }
}

const router = new VueRouter({
  mode: 'history',
  base: __dirname,
  routes: [
    {
      path: '/asd', component: getComponent('subfolder1', 'Asd')
    }
  ]
})

in subfolder1/index.js
import Asd from "./Asd.vue"

export default  {
    Asd: Asd
}

Im having similar issue and trying to asyncly load a component inside the Router component and getting the following error:
Failed to resolve async component: ()=>t.e(6).then(t.bind(null,151)) Reason: Error: Loading chunk 6 failed.
Route config:
export default new Router({   routes: [     {       path: "/",       name: "HomePage",       component: HomePage     }   ] });
HomePage.vue:
`
import WhyChooseUs from "./WhyChooseUs";
const BelowFold = () => import(/* webpackChunkName: "below-fold" */ './BelowFold.vue'); // eslint-disable-line
export default {
name: "HomePage",
components: {
WhyChooseUs,
BelowFold
}
};
`
Im only trying to lazy load the components that are in the BelowFold Components.

@bajras Did you end up fixing this?

@bajras Did you end up fixing this? +1

The all-in-one file is created by the context ('./views/' + name + '.vue')
If you don't want that, rewrite it like that:
import Vue from 'vue';
import VueRouter from 'vue-router';
import config from 'config';

Vue.use(VueRouter)

const router = new VueRouter({history: true, root: config.root});

router.map({
    '/': {
        name: 'home',
        component: function(resolve) {
            require(['./views/home.vue'], resolve);
        }
    },
    '/user/:oid/': {
        name: 'user',
        component: function(resolve) {
             require(['./views/user.vue'], resolve);
        }
    }
});

export default router;

Each require([], resolve) will create a split point and a lazy loaded chunk.

The address of the vue component is obtained through the backend. Why does the browser prompt that it cannot be found after the string is loaded?


DRep expiry update after a contiguous set of epochs with no proposals to vote on

Description
Closes #3723

Add vsNumDormantEpochs field to VState.

This field counts the number of contiguous epochs in which the number of active governance proposals that can be voted on remained zero. It will be incremented in every EPOCH if the number of active governance actions that can be voted on continues to remain zero. It will be reset when a new governance proposal is submitted successfully

Add updateNumDormantEpochs in GOV, introduce GovRuleState datatype.

Add a updateNumDormantEpochs function in ConwayEPOCH rule to update the dormant-epochs counter in VState whenever the previous epoch has had zero governance proposals.
Introduce the GovRuleState data-type as the State for the ConwayGOV rule, made up of VState in addition to the already existing GovSnapshots. We need this to implement resetting of the counter and bumping of the DRep expiries upon new successful submissions of governance proposals.

Update DRep expiry on first proposal after dormant epochs.

Add updateDRepExpiry to the addAction function in GOV to update the expiry of DReps and reset the dormant-epochs counter to zero - only on the first successful submission of a governance proposal after a contiguous set of dormant epochs.
In API.State.Query.queryDRepState, add the number of dormant epochs to the DRep expiries for correct reporting if it is not zero.
Add lenses for GovRuleState

Checklist

[x] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[x] When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
versioning process.
[x] The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
[x] All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
[x] Code is formatted with fourmolu (use scripts/fourmolize.sh)
[x] Cabal files are formatted (use scripts/cabal-format.sh)
[x] hie.yaml has been updated (use scripts/gen-hie.sh)
[ ] Self-reviewed the diff

@aniketd Needs golden test adjustment, since we added a new field and some other test failures. Not sure what they are about


Warnings when defining variable definitions in GM.

I've tried to use cast  but I get an error.

Maybe a quick fix for this might be to disable warnings for #event properties.

Thanks :)


Currently broken ports

These ports have TEST() added but currently fail
Status:

dev-lang/tcc: tcctest.gcc fails because weak_v1 is not resolved by dyn linker
dev-lang/spidermonkey: multiple tests failed, all SIGSEGV

Track status in #1832


Add ASTC SFLOAT formats

Feel free to reject this if it's out of scope :)
I've been playing around with the HDR ASTC formats recently and I thought I'd add their variants to the format enum. I'd understand if you just want to only define the base Vulkan formats.
See https://registry.khronos.org/vulkan/specs/1.2-extensions/html/vkspec.html#VkFormat.
Checklist

[x] cargo clippy reports no issues
[x] cargo doc reports no issues
[x] cargo deny issues have been fixed or added to deny.toml
[x] cargo test shows all tests passing
[x] human-readable change descriptions added to the changelog under the "Unreleased" heading.

[] If the change does not affect the user (or is a process change), preface the change with "Internal:"
[ ] Add credit to yourself for each change: Added new functionality @githubname.

Per your link, these are core in Vulkan 1.1, so I see absolutely no reason not to include them. I'm not even specifically opposed to extension-specific format values if someone has a use case for them; (pseudo) variants are cheap.

Per your link, these are core in Vulkan 1.1

Ah great, didn't know that!


Manually load plugins

A nice feature would be to load new plugins without restarting the server.

Like a /lukkit load  or something like that would be great.

Are we talking loading new plugins or reloading current plugins with changes?

Closing and moving to Trello board for collation purposes


http timeout

Running this command:

lego.exe --accept-tos="true" --http="<IP_ADDRESS>:80" --tls="<IP_ADDRESS>:443"<EMAIL_ADDRESS>--domains="rtc.tellfree.com.br" run

I get this response:

2016/05/12 16:12:41 Could not create client: get directory at 'https://acme-v01.api.letsencrypt.org/directory': failed to get "https://acme-v01.api.letsencrypt.org/directory": Get https://acme-v01.api.letsencrypt.org/directory: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

This is happening only on our Brazil server (Windows Server 2008 R2, lego.exe enabled on firewall, both 80 and 443 ports available for it).
The same is working fine on our UK server.
If I open the "https://acme-v01.api.letsencrypt.org/directory" URL from Firefox on the same Brazil server, i get the answer in around 10 seconds. So from Brazil the 10 second timeout usually is not enough.
Proposed solution:
Increase the http timeout in the http.go file by replacing:
this line: var defaultClient = http.Client{Timeout: 10 * time.Second}
with this: var defaultClient = http.Client{Timeout: 20 * time.Second}
If you wish you might also add a command line option to specify the http timeout.

I guess making the timeout configurable via a CLI option would be the most sensible option here. I'm sure that if we raise the default timeout, somebody else will still hit it 😄

Hmmm yeah I feel like the permanent solution to this is to fix your network connection (you or them, depending where the problem is)

This is a server with 100 mbits internet connection used for VoIP with hundred of simultaneous calls. I don't think that the problem is with the internet connection. If you don't wish to increase the timeout so much, then my proposal:
-increase only a little bit the default (make it 14 seconds and it will be fine for the whole South America by default)
-and make it configurable via a CLI option

You are now able to supply a --http-timeout flag to set the timeout in seconds.

I've try to make lego works on my Asus-AC68U router. I've got exactly same message as in issue when run lego

Could not create client: get directory at 'https://acme-v01.api.letsencrypt.org/directory': failed to get "https://acme-v01.api.letsencrypt.org/directory": Get https://acme-v01.api.letsencrypt.org/directory: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

When I run lego from the same network from windows PC - it's works correctly.
I've try to use latest release v0.3.1 lego_linux_arm build and build my own build from master branch with exactly the same result. It's fails almost instantly - in 3-4 seconds. --http-timeout doesn't do anything.


Emerald vein for the mining rig

Description:

Describe your suggestion with as many details as possible.

I would like to see a vein type added to the mining rig that yields emerald ore. I don't know enough about real world ore vein types to suggest where this vein should occur, what it should be called or what else should be in it aside from stone, but vanilla ore generation would suggest mountainous biomes to be a good place.
Reason:

Why do you think your suggestion should be added?

Quite simply, having an emerald vein would mean that the mining rig makes emerald ore as a block renewable easier to obtain in large quantities, which it is not in vanilla. This allows it to be 'farmed' to obtain it in large quantities for builds, and also makes it obtainable in skyblock. The mining rig already makes all of the other vanilla and IR ore blocks renewable easier to obtain in large quantities, so why not emerald?

Emerald has been part of some veins for a while now, forgot to close this issue. Thanks for the suggestion


update rebar to ver 2.5.1

On OTP 17.4 I'm seeing compile time errors when building lager_syslog as a dependency of a rebar3 based project. Upgrading rebar seems to fix it.
The error in question:
==> syslog (compile)
Uncaught error in rebar_core: {'EXIT',
                               {badarg,
                                [{re,split,
                                  [[118,99,115,95,105,110,102,111,95,109,115,
                                    103,95,48,95,61,32,111,110,32,37,123,27,
                                    91,51,54,109,37,125,109,97,115,116,101,
                                    114,37,123,27,91,51,51,109,37,125,32,9679,
                                    37,123,27,91,51,49,109,37,125,32,9679,37,
                                    123,27,91,48,48,109,37,125],
                                   "=",
                                   [{return,list},{parts,2}]],
                                  [{file,"re.erl"},{line,170}]},
                                 {rebar_port_compiler,'-os_env/0-lc$^0/1-0-',
                                  1,[]},
                                 {rebar_port_compiler,'-os_env/0-lc$^0/1-0-',
                                  1,[]},
                                 {rebar_port_compiler,os_env,0,[]},
                                 {rebar_port_compiler,setup_env,1,[]},
                                 {rebar_core,'-setup_envs/2-lc$^0/1-0-',2,[]},
                                 {rebar_core,setup_envs,2,[]},
                                 {rebar_core,execute,4,[]}]}}

This PR is pointed toward the 2.1 branch, as master appears to be stale at this point.

Hey @tsantero
I tried building locally and noticed a difference on how it handles the deps - make clean or make tests don't recurse into deps.
jons-mbp13:lagersyslog17 jmeredith$ git branch
* (HEAD detached at tsantero/bugfix/upgrade-rebar)
  master
jons-mbp13:lagersyslog17 jmeredith$ make clean
./rebar clean
==> lagersyslog17 (clean)
jons-mbp13:lagersyslog17 jmeredith$ git checkout master
Previous HEAD position was 35f04bb... update rebar to ver 2.5.1
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
jons-mbp13:lagersyslog17 jmeredith$ make clean
./rebar clean
==> goldrush (clean)
==> lager (clean)
==> syslog (clean)
==> lagersyslog17 (clean)

Do you get the same thing... old rebars are old
jons-mbp13:lagersyslog17 jmeredith$ ./rebar --version
rebar version: 2 date: 20110624_180307 vcs: git 3e41385

Also breaks R14 support on Travis - which I can live without :)

@tsantero @jonmeredith I just tested this on my workstation and confirm Jon's comment about the recursion. Must be switch somewhere where new rebar ignores deps and old rebar just honeybadgers right on through.

I had forgotten about this. Sorry for leaving it open so long with no response, @jonmeredith
Closing as this issue is solved elsewhere.


Update date.past params format

Make date.past accepts one single object parameter.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (6686af1) to head (f221352).
Report is 6 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #40   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           15        16    +1
  Lines          139       144    +5
  Branches        21        23    +2
=========================================
+ Hits           139       144    +5

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


commenting issues on channel page

From KP:

[ ]  I can't seem to change the channel to comment in a Channel Page's discussion section.

[ ] Also, it crashes when I tap on my name in that page.

He thinks it may be something with his account, so need to repro first.

What do you mean by "can't change the channel to comment"?

The "Comment as @xxx" should be a dropdown for users to select the channel to comment as, but it seems like just a text.

Ah, I see. Would making it link/button coloured be okay?

The UI is the same for all the comment areas as it uses the same view controller.
On Fri Jul 1, 2022 at 10:07 PM +08, Thomas Zarebczan wrote:

It should look the same as commenting on other pages (I don't recall if we do a drop down there?)
--
Reply to this email directly or view it on GitHub:
https://github.com/OdyseeTeam/odysee-ios/issues/336#issuecomment-1172388095
You are receiving this because you commented.
Message ID: @.***>

Yeah, I'm not seeing it selectable in any place.

Ah, I see. Would making it link/button coloured be okay?

Should be fine, as long as consistent everywhere like Tom mentioned.


How to start Timelord properly

Hi @Achi-Coin,
I have 16 core CPU (AMD Ryzen 5950X) with 128 GB RAM, so I want to provide Timelord for Achi.
How to run Timelord properly? I have timelord service enabled, also I have destination-NAT for port 9975 on my public IP. Logs are full of some Timelord activities, but I don't see any rewards related to 0.02%/block for working Timelord.
Probably there are some next requirements?

Hello Ag3ntt!
Your setup is absolutely correct.
Final step to make your Timelord rewaded is ro define DEFAULT_CONSTANTS.TIMELORD_PUZZLE_HASH. Add reward_puzzle_hash to config.yaml. For example:
timelord:
reward_puzzle_hash:
59ae00d2jhlkjhkjlhads34fhjklaerr34eerhd34skjfhkj43543dsahfjkhhh87y873
Please bear in mind that reward goes to the fastest timelord in the network. Use command vdf_bench square_asm 400000 to check computation speed of your timelord.
Good luck!

Thank you, @Achi-Coin.
What is value for reward_puzzle_hash? Where I can take it?
Btw, result of my ./vdf_bench square_asm 400000 is:
Time: 1889 ms; n_slow: 74; speed: 211.7K ips
a = 0x6ce27bdb0240cadd4f5ba8eda519bfbe0ffd5ad3004ff27b9d6f65c62815265730bce32258434615674124e204f3c3429e6c214fd171846f5c0acf27c754ac42
b = -0x2040323dc47947c6161535b2e1366a274671d9bd1f9cb7644cb0da6b237a886a8414c9d9fa33f3fd9d9072b34561bc51e93ec1fbb341f6a18de5dd5c63fa421f
c = 0x78869cb37a6a7d392b19000ce9dc30358093871a2753ea79c0cabe40e283d1a2f60234c2f2f8777fde662a87f55a4cb7fea3489750e83c9cefff52fc594b19ab`

I think that i got it :)
Reward puzzle hash can be generated by commands below (you need your achi wallet address). For chia (but not for an achi) there is a tool https://www.chiaexplorer.com/tools/address-puzzlehash-converter
cd /path/to/achi-blockchain/
. ./activate
python -c 'import achi.util.bech32m as b; print(b.decode_puzzle_hash("HERE-YOUR-ACHI-WALLET-ADDRESS").hex())'