AttributeError: type object 'Dataset' has no attribute 'from_list'

I was trying to finetune on a raw text file. It has a few empty lines too. I'm getting this error.
When I looked into the Datasets class, I didn't find from_list function. There were others like from_dict and from_text ( reads from file). I wanted to know if this line of code needs to be changed.
PS: I tried replacing that line with data = datasets.Dataset.from_text(<file path>) and the training seems to be working fine. But I'm not sure how newline and multiple new line characters effect the training performance. Would appreciate some light shed on that.
To create a public link, set `share=True` in `launch()`.
Loading base model...
Number of samples: 28
Traceback (most recent call last):
  File "/home/datta0/.pyenv/versions/3.8.10/lib/python3.8/site-packages/gradio/routes.py", line 393, in run_predict
    output = await app.get_blocks().process_api(
  File "/home/datta0/.pyenv/versions/3.8.10/lib/python3.8/site-packages/gradio/blocks.py", line 1108, in process_api
    result = await self.call_function(
  File "/home/datta0/.pyenv/versions/3.8.10/lib/python3.8/site-packages/gradio/blocks.py", line 915, in call_function
    prediction = await anyio.to_thread.run_sync(
  File "/home/datta0/.pyenv/versions/3.8.10/lib/python3.8/site-packages/anyio/to_thread.py", line 31, in run_sync
    return await get_asynclib().run_sync_in_worker_thread(
  File "/home/datta0/.pyenv/versions/3.8.10/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread
    return await future
  File "/home/datta0/.pyenv/versions/3.8.10/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 867, in run
    result = context.run(func, *args)
  File "/home/datta0/.pyenv/versions/3.8.10/lib/python3.8/site-packages/gradio/helpers.py", line 588, in tracked_fn
    response = fn(*args)
  File "main.py", line 161, in tokenize_and_train
    data = datasets.Dataset.from_list(paragraphs)
AttributeError: type object 'Dataset' has no attribute 'from_list'
Number of samples: 11
Traceback (most recent call last):
  File "/home/datta0/.pyenv/versions/3.8.10/lib/python3.8/site-packages/gradio/routes.py", line 393, in run_predict
    output = await app.get_blocks().process_api(
  File "/home/datta0/.pyenv/versions/3.8.10/lib/python3.8/site-packages/gradio/blocks.py", line 1108, in process_api
    result = await self.call_function(
  File "/home/datta0/.pyenv/versions/3.8.10/lib/python3.8/site-packages/gradio/blocks.py", line 915, in call_function
    prediction = await anyio.to_thread.run_sync(
  File "/home/datta0/.pyenv/versions/3.8.10/lib/python3.8/site-packages/anyio/to_thread.py", line 31, in run_sync
    return await get_asynclib().run_sync_in_worker_thread(
  File "/home/datta0/.pyenv/versions/3.8.10/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread
    return await future
  File "/home/datta0/.pyenv/versions/3.8.10/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 867, in run
    result = context.run(func, *args)
  File "/home/datta0/.pyenv/versions/3.8.10/lib/python3.8/site-packages/gradio/helpers.py", line 588, in tracked_fn
    response = fn(*args)
  File "main.py", line 161, in tokenize_and_train
    data = datasets.Dataset.from_list(paragraphs)
AttributeError: type object 'Dataset' has no attribute 'from_list'

I just released v2 where I rewrote the whole thing from scratch. Give it a shot!

Seems that this line still exists in the latest version https://github.com/lxe/simple-llm-finetuner/blob/master/trainer.py#L163 :-(

@Datta0 I suppose your issue was caused by stale datasets pre-installed in your environment.
Running pip install datasets -U should fix your issue.
@lxe - Maybe change the pip install -r requirements.txt to pip install -r requirements.txt -U in README.md for clairification?


wrong gid of backupdba

https://github.com/oravirt/ansible-oracle/blob/535c2643da70f4e3454a8940f764a9f2d281ac8c/roles/orahost/defaults/main.yml#L14C13-L14C22
it must be 54324, not 54323
https://docs.oracle.com/en/database/oracle/oracle-database/12.2/ssdbi/required-operating-system-groups-and-users.html#GUID-EBE883F8-5692-43C6-9CEB-2953C2E2837D

and oper gid is 54323 and not 54324

Hi Markus,
the gids in the documentation from oracle are not mandatory. They could be changed per installation.
You could set your own gids in your installation to match the documentation but there is no need for itthat.
Changing the gids in ansible-oracle is a breaking change for existing installations.
Kind Regards
Thorsten


First run of az-cli is slow

Description
For quite some time we have been impacted by poor performance due to the nature of az-cli's command and module caching on it's first run. It would seem that az-cli was not written with ephemeral runners in mind, and it doesn't look like they could change this easily. Hence why we are opening this issue here.
We can see that the issue is fixed on windows images as a simple warmup has been implemented
https://github.com/actions/runner-images/blob/c5c9a7cd7b2cfd20d740f7667fdaca8a412f2b52/images/windows/scripts/build/Install-AzureCli.ps1#L22
Can you please implement a simple warm up like on the windows runners?
From a sample of our logs we have measured the following impact
Minimum 2 s
Maximum 31 s
Average 5 s
We estimate wasting roughly 6500 minutes per month which is more than 10% of our of total usage
Platforms affected

[x] Azure DevOps
[X] GitHub Actions - Standard Runners
[X] GitHub Actions - Larger Runners

Runner images affected

[X] Ubuntu 20.04
[X] Ubuntu 22.04
[X] Ubuntu 24.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240609.1
Is it regression?
no
Expected behavior
A build-in warmup in the ubuntu image creation similar to the windows image
Actual behavior
No warmup
Repro steps
None needed

HI @lanni-energinet ,
Thank you for bringing this issue to us, we are investigating on this issue and we will update you on this issue after our findings.

@lanni-energinet
Thank you for bringing this issue to us. We are looking into this issue and will update you on this issue after investigating.

@kishorekumar-anchala
i've attached a proposed implementation on the PR can you take a look
https://github.com/actions/runner-images/pull/10126#issuecomment-2262893593

@kishorekumar-anchala
Can we in any way assist in the resolution of this issue. We are wasting a lot of time and money on this

Not sure if the proposed fix would fix our issue, but when we run the login action on Ubuntu, it sometimes takes up to 2 minutes to simply run the first clear command like this, which is insanely long for such a basic task:

@lanni-energinet , We are considering your workflow and doing changes . we're facing the some issue , we'll get back to you Asap. THANK YOU !

@kishorekumar-anchala Any progress to report?

Feeling this pain too. Basically every one of our jobs begin with running azure/login@v2, which annoyingly always takes between 10 and 30 seconds.

HI @lanni-energinet ,
By implementing this we're getting permission error .   it would be helpful if you provide repro steps . thank you for your support !
==> azure-arm.build_image:     with open(self.config_path, 'w', encoding=CONFIG_FILE_ENCODING) as configfile:
==> azure-arm.build_image:          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
==> azure-arm.build_image: PermissionError: [Errno 13] Permission denied: '/home/root/.azure/config'
==> azure-arm.build_image: ToolVersionNode 'Azure CLI' has empty version
==> azure-arm.build_image: At /imagegeneration/SoftwareReport/software-report-base/SoftwareReport.Nodes.psm1:166 char:13
==> azure-arm.build_image: +             throw "ToolVersionNode '$($this.ToolName)' has empty vers …
==> azure-arm.build_image: +             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> azure-arm.build_image: + CategoryInfo          : OperationStopped: (ToolVersionNode 'Az…' has empty version:String) [], RuntimeException
==> azure-arm.build_image: + FullyQualifiedErrorId : ToolVersionNode 'Azure CLI' has empty version

@kishorekumar-anchala
Can you test this PR: https://github.com/actions/runner-images/pull/11173

@kishorekumar-anchala
Sorry about that. I overlooked that the install scripts was running as root, but the tests was running as packer.
I've updated the PR and tests are now passing.

Hi @lanni-energinet - I tested the changes ,  working good .  Thanks you for your support in implementing the request. PR will be in review. I will update you once it merged .


[EC-151] Block execution correct error handling

Description
Includes the correct handling of the errors that are raised during block execution and the removal of throwing exceptions when that were to happen.
This also fixes:

In case an error during execution happens, no account is deleted and the world state is rollbacked to its previous state

@LukasGasior1 I fixed your comments and updated the logging, please take a look at it and let me know if there's something else to fix.

@rtkaczyk @LukasGasior1 I just fixed a small bug I detected in how the rollback was done, in case the OutOfGasError happened in saveNewContract the world state wasn't rollbacked


CASSANDRA-16491 track and handle errors during nodetool bootstrap resume properly

There is some issue where the nodetool bootstrap resume command returns success successfully even when some error happens during the operation.  To address that, we now keep track of the errors when they occur in BootstrapMonitor and now throw them after signaling.  Also as part of this MR, I made a change so we don't send a ProgressEventType.COMPLETE event anymore when we see an error as that seems to be a bit misleading.
To reproduce a scenario, I killed one of the nodes involved in the bootstrap resume process and checked if errors were thrown in the terminal.

https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-16491-circle

Committed in https://github.com/apache/cassandra/commit/8ec04361b9e098430023e4776baf1941be958475


Try removing the minitest DSL

Motivation

Test plan

See included automated tests.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_LdqtqaDVC97TBr
→ https://go/builds/bui_LdqtV5KugHmtoV

This rewriter is very useful for us. Why is it considered for removal?

We think we might be able to replace it with T.proc.bind(T.attached_class).void on the ‘it’ method, which would let code like [true, false].each {it ‘’ {}} typecheck without needing to use test_each. Nathan was looking further into it

We think we might be able to replace it with T.proc.bind(T.attached_class).void on the ‘it’ method, which would let code like [true, false].each {it ‘’ {}} typecheck without needing to use test_each. Nathan was looking further into it

Despite the coolness of T.proc.bind(T.{self_type,attached_class}) is, it's not sufficient for modeling minitest, and the minitest rewriter, despite all its problems, is a much better option.


Tensorflow Lite Swift iOS: Cocoapods Integration Broken - No such module 'TensorFlowLiteC'

Click to expand!
Issue Type
Build/Install
Source
binary
Tensorflow Version
Latest from cocoapods
Custom Code
No
OS Platform and Distribution
XCode 13.2.1
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Take the image classification sample app for example:
 https://github.com/tensorflow/examples/blob/master/lite/examples/image_classification/ios/Podfile

Replace pod 'TensorFlowLiteTaskVision' with 'TensorFlowLiteSwift'

pod install.

Build for any ios device or try to archive the app.

Result: Compiler Error - No such module 'TensorFlowLiteC'

Expected Result: No Compiler Error.

This issue seems to have been introduced when Tensorflow Lite was distributed via cocoapods using  .XCFramework, it used to work with .framework, you can pin to version "1.14.0" and it works as expected.

Standalone code to reproduce the issue
platform :ios, '12.0'

target 'SampleApp' do
   use_frameworks!

  pod 'TensorFlowLiteSwift'
end

Relevant log output
No response

Hi @yusufoos !
Just quick observation, Is your Tensorflow version 2.1 ? It is pretty outdated.
You can use
pod 'TensorFlowLiteSwift' : 2.10.0
or
pod 'TensorFlowLiteSwift', '~> 0.0.1-nightly'
or
pod 'TensorFlowLiteSwift', '~> 0.0.1-nightly', :subspecs => ['CoreML', 'Metal'] or

@sachinprasadhs !
Could you look at this issue.
Thank you!

I just used the latest pod as shown which I believe resolved to 2.10

@mohantym @sachinprasadhs Gentle bump on this, and reminder this is not 2.1 it's for the latest 2.10.0

Hi sorry for the late reply, do you see this issue with the latest version v2.11.0?

@yusufoos , Could you please test your results against TesroFlowLite Swift 2.11 version and let us know the outcome.
For details visit here https://cocoapods.org/pods/TensorFlowLiteSwift

Or can you try the nightly build? I just tried 0.0.1-nightly.20230405 and it is working fine.

@yusufoos , It is not suggested to change the pod from 'TensorFlowLiteTaskVision' to 'TensorFlowLiteSwift'.
TensorFlowLiteTaskVision  will be compatible with Swift, whereas swift is more related to runtime.
Please find the below tutorial for reference https://www.tensorflow.org/lite/inference_with_metadata/task_library/image_classifier#run_inference_in_ios


Add type annotations to some fakefs functions

This is work in progress, trying to annotate the pyfakefs methods.
This hopefully helps to find some inconsistencies (already found some in str / byte handling), but it will take a while.
@AustinScola - if you want to take a look, there are certainly things that can be improved, as I don't have much experience with typing.

Nice! I'll check it out later today or tomorrow.

Going to merge this to avoid too many merge conflicts with other changes. Will continue in new PR(s).


form-data array submission support

What are the steps to reproduce this issue?

Have a doc with body that includes  form-data with array type field

E.g. :
 post:
      summary: Create
      tags:
        - Docs
      requestBody:
        content:
          multipart/form-data:
            schema:
              type: object
              properties:
                files:
                  type: array
                  items:
                    type: string
                    format: binary

generate orval client (client: axios | axios-functions)

What happens?
According to PHP documentation we need to user files[] field name to show it's an array of files. And when we are using orval to generate an endpoint for 'mutlipart/form-data' it creates form with field name just like files neither files[]. As a result have an error from server that files is not an array
What were you expecting to happen?
Expecting to have correct generated form-data
const postDocs = (
    postDocsBody: PostDocsBody,
    options?: SecondParameter<typeof customInstance>,
  ) => {
    const formData = new FormData();
    postDocsBody.files.forEach(value => formData.append("files[]", value));

    return ...
  };

Output:

const postDocs = (
    postDocsBody: PostDocsBody,
    options?: SecondParameter<typeof customInstance>,
  ) => {
    const formData = new FormData();
    postDocsBody.files.forEach(value => formData.append("files", value));

   return ...
  };

What versions are you using?
Operating System: macOS
Package Version: 6.29.1

In my project I have an endpoint in a .net backend that takes multiple files, which would not work if [] was appended, so this would have to be a setting of some kind..

@AffeJonsson in our example we are using PHP and it doesn't work without []. I was thinking of adding a new option in config to define form-data array submission. Cause in other languages another array type should be.

You can modify the input in the orval configuration to add [] to the name for this specific project in case you are using the swagger definition elsewhere. Orval also takes care of naming non-es5 names of variables by wrapping them in quotes:
interface myBody {
  "files[]": Blob[];
}

so accessing that name is possible using bracket notation:
const files = myBody["files[]"];

It looks like a crutch
Cause:

It's not the only field in form-data
All our projects are using PHP. And it's kinda annoying to write this stuff all the time
And main point is that for forms im using orval generating types:

  const initialValues: CreateDocData = {
    first_name: "",
    date_of_birth: "",
    country_id: 0,
    series: "",
    last_name: "",
    middle_name: "",
    files: [],
    number: "",
    issued_at: "",
    expire_at: "",
    gender: "male",
    who_issued: "",
    address: "",
  };

where CreateDocData is orval generated type from our request. And using orval generated method and formik there will be type error cause files[] is not in CreateDocData, it's expect to have just files

I have the same problem with the php backend. It would be great if there was a config that could be used to change the format for generating such arrays

One workaround for now could be to use the formData mutator:
output: {
  override: {
    formData: {
      path: "./path-to/form-data-mutator.ts",
      name: "customFormData"
    }
  }
}

with a file form-data-mutator.ts:
export const customFormData = <Body extends Record<string, any>>(
  body: Body,
): FormData => {
  const formData = new FormData();

  Object.entries(body).forEach(([key, value]) => {
    if (Array.isArray(value)) {
      value.forEach(entry => formData.append(`${key}[]`, entry));
    } else {
      formData.append(key, value);
    }
  });

  return formData;
};

export default customFormData;


Backend overhaul

In order to make cortex easier to use but less like a black box, various backend changes were made.
The user now has the option to change their build or routine functions, but also affect the main loop in various ways, adding needed flexibility without putting pressure on development to cover every use-case.
Notable methods are wrapped by cortex to take care of things better left to the backend, with things that people (hopefully) care about exposed to the user.
Several convenience functions were added to make it easier from the user standpoint to fetch data and pass arguments to functions.
Classifier, GAN, VAE, adversarial AE, ALI, and MINE are all implemented.
Finally, models can be trained using just python <path to file> <arguments> (see the classifier demo).

Maybe the PR should be merged without waiting for the reviews if it's working locally on the author's computer. As the multiple changes are changing the behavior of the plugins, which is primordial for stress testing.

For
cortex GAN --d.source CIFAR10 --d.copy_to_local
I get error
Traceback (most recent call last):
  File "/u/poulijoe/.conda/envs/python3.6/bin/cortex", line 7, in <module>
    from cortex.main import main
ImportError: cannot import name 'main'

Simple experiment cortex GAN --d.source CIFAR10 --d.copy_to_local  returns ImportError: cannot import name 'main'.


[NEW]: Crypto.com fined € 2.85 million by Dutch central bank

Date
2023-10-02
Description
De Nederlandsche Bank (DNB) today published about a fine handed to the company behind Crypto.com for serving Dutch customers without the required registration with DNB. This registration is required since 2020-05-21 by the Anti-Money Laundering and Anti-Terrorist Financing Act (Wet ter voorkoming van witwassen en financieren van terrorisme – Wwft).
This is similar to the earlier rulings (reported here as well, second and third link) against Coinbase and Binance.
Links
https://www.dnb.nl/nieuws-voor-de-sector/handhavingsmaatregel-2024/boete-voor-foris-dax-mt-limited-crypto-com-vanwege-het-tot-2-augustus-2023-zonder-de-wettelijk-vereiste-registratie-aanbieden-van-cryptodiensten-in-nederland/
https://www.web3isgoinggreat.com/?id=coinbase-fined-3-6-million-by-dutch-central-bank
https://www.web3isgoinggreat.com/?id=binance-fined-3-million-for-operating-in-the-netherlands-without-registering
Agreement

[X] I irrevocably agree to release my contribution under the CC-BY 3.0 License

Attribution name
No response
Personal link
No response

I see the earlier posts don't have links to the (Dutch) original press release. Should I add an issue linking them?
links:
https://www.dnb.nl/nieuws-voor-de-sector/oud/handhavingsmaatregel-2022/boete-voor-binance-holdings-ltd-vanwege-het-zonder-de-wettelijk-vereiste-registratie-aanbieden-van-cryptodiensten/
https://www.dnb.nl/nieuws-voor-de-sector/oud/handhavingsmaatregel-2023/boete-voor-coinbase-europe-limited-vanwege-het-tot-22-september-2022-zonder-de-wettelijk-vereiste-registratie-aanbieden-van-cryptodiensten-in-nederland/

Thank you! https://www.web3isgoinggreat.com/?id=cryptocom-fine


Filters module

Type of change

Refactoring

Description
Introduce a new kroxylicious-additional-filters module to maven hierarchy:

Externalising the filters which are not required for Kroxylicious to operate but offer compelling functionality.
Provides a useful extension point to ensure the additional filters do not depend on core Kroxylicious modules

Additional Context
I was reviving my Otel filter and realised I was introducing the third filter module and that seemed awkward to just lump into the root pom

[INFO] Reactor Summary for Kroxylicious Parent 0.2.0-SNAPSHOT:
[INFO]
[INFO] Kroxylicious Parent ................................ SUCCESS [  2.541 s]
[INFO] Kroxylicious API ................................... SUCCESS [  4.101 s]
[INFO] Code Generation plugin ............................. SUCCESS [  6.437 s]
[INFO] Kroxylicious Filter API ............................ SUCCESS [  5.885 s]
[INFO] Filter Unit Test tooling ........................... SUCCESS [  2.814 s]
[INFO] Kroxylicious Proxy ................................. SUCCESS [  8.613 s]
[INFO] Testing tools ...................................... SUCCESS [  6.818 s]
[INFO] Additional Filters ................................. SUCCESS [  0.083 s]
[INFO] Kroxylicious Multitenant ........................... FAILURE [  0.067 s]
[INFO] Kroxylicious Schema Validation ..................... SKIPPED
[INFO] Kroxylicious Integration tests ..................... SKIPPED
[INFO] Micro benchmarks ................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  37.515 s
[INFO] Finished at: 2023-06-07T11:03:56+12:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.3.0:enforce (filters-use-public-api) on project kroxylicious-multitenant:
[ERROR] Rule 0: org.apache.maven.enforcer.rules.dependency.BannedDependencies failed with message:
[ERROR] io.kroxylicious:kroxylicious-multitenant:jar:0.2.0-SNAPSHOT
[ERROR]    io.kroxylicious:kroxylicious:jar:0.2.0-SNAPSHOT <--- banned via the exclude/include list

A deliberately introduced failure to demonstrate.


removeWorksheet missing parameter, so callback not called

This code, calls makeFeedRequest with 3 parameters, where as makeFeedRequest takes 4 parameters. This means that the callback goes into query_or_data. Adding a null fixes that.
  this.removeWorksheet = function ( worksheet_id, cb ){
    if (!this.isAuthActive()) return cb(new Error(REQUIRE_AUTH_MESSAGE));
    self.makeFeedRequest( ["worksheets", ss_key, worksheet_id], 'DELETE', cb );
  }

Simple fix
  this.removeWorksheet = function ( worksheet_id, cb ){
    if (!this.isAuthActive()) return cb(new Error(REQUIRE_AUTH_MESSAGE));
    self.makeFeedRequest( ["worksheets", ss_key, worksheet_id], 'DELETE', null, cb );
  }

I've just a published a new version of this module which is a complete rewrite using Google's V4 Sheets API (v3 is being deprecated on March 3, 2020).
Docs available here - https://theoephraim.github.io/node-google-spreadsheet
I do believe this issue should be fixed in the new version.
Please test it out and if you find that there is still a problem, reopen the issue.
Thanks! 😄


List all available tasks

It would be great to be able to call fly -T and obtain a list of possible tasks. This could be similar to the cap -T for listing available recipes in capistrano.
Capistrano gives an output that looks like this:
cap deploy               # Deploys your project.
cap deploy:check         # Test deployment dependencies.
cap deploy:cleanup       # Clean up old releases.
cap deploy:migrate       # Run the migrate rake task.
...

Flightplan's output could look similar. (sans descriptions since there's no way to specify them yet)
fly build:production
fly build:staging
fly deploy:production
fly deploy:staging
...

Thoughts?

The question is whether tasks and targets should be listed separately. What do
you think?
Tasks:            Targets:
default           development
deploy            staging
reload            production
setup

The count of functions to be executed / target hosts could be displayed as well:
Tasks:            Targets:
default (2)       development (1)
deploy  (5)       staging     (1)
reload  (1)       production  (?) # <-- using dynamic config
setup   (2)

Sounds like a great idea to list them separately. Not sure if the count is needed though, I personally prefer the first one since the output is simple and easy to understand.

:+1:

:+1: wow.

This would be tremendously useful to have!

:+1:

0.6.7 now supports the following commandline options:
-t, --targets            output available targets
-T, --tasks              output available tasks

It will also list available targets when the target argument is missing, i.e.
$ fly
Error: No target specified. Use `--help` for more information

Available targets:
  single
  multi


TLS error

I am trying running drachtio-server with TLS enabled, I have got the certificate from goDaddy. Below is my drachtio.conf.xml section for TLS
  <sip>
         <contacts>
            <contact external-ip="18.216.*.*">sip:*;transport=udp</contact>
            <contact external-ip="18.216.*.*">sips:*;transport=tls</contact>
        </contacts>
  </sip>
  <tls>
        <key-file>/home/admin/certs/key.pem</key-file>
        <cert-file>/home/admin/certs/cert.crt</cert-file>
        <chain-file>/home/admin/certs/bundle.crt</chain-file>
  </tls>

The drachtio server is not able to run then. I see below lines in the logs
2023-09-11 15:35:50.786495 tport_type_tls.c:229 tport_tls_init_master() tport_tls_init_master(0x55c035df8c80): tls key file (TPTAG_TLS_CERTIFICATE_KEY_FILE) is required and not specified
2023-09-11 15:35:50.786509 tport.c:1165 tport_zap_secondary() tport_zap_secondary(0x55c035df8c80): zap tport 0x55c035df8c80 from (null)/(null):(null), count(wss) is 0, count(tcp) is 0
2023-09-11 15:35:50.786521 tport.c:758 tport_listen() tport_listen(0x55c035e28600): tls_init_master(pf=2 tls/[<IP_ADDRESS>]:5061): Address family not supported by protocol
2023-09-11 15:35:50.786531 nta.c:2345 nta_agent_add_tport() nta: bind(<IP_ADDRESS>:5061;transport=tls;maddr=*): Address family not supported by protocol
2023-09-11 15:35:50.786537 DrachtioController::run: Error adding additional transport

please refer to https://drachtio.org/docs/drachtio-server#tls
tls is a child tag of sip


Issues with Caucasian Languages

The model for Caucasian Languages are having very less accuracy. The languages of Abkhaz, Adyghe and Chechen have quite a lot of data in the internet and also bilingual corpuses. Chechen has a huge amount of Wikipedia data and Abkhaz, Kabardian, Lezgi, Adyghe, Ingush, Lak, Avar has Wikipedia data but the models using these languages have very less accuracy.

Contributions of clean aligned bilingual data sets would be very helpful to push the performance. Would you like to contribute? I welcome contributions to OPUS and that would feed into the NMT models as well ... Thanks!

Hi, I am interested in contributing. However, I'm not quite sure where to start.

More data would be the most practical thing that could help to improve the quality. I added an issue here to add some more data: https://github.com/Helsinki-NLP/OPUS-ingest/issues/14
If you happen to know more sources of parallel data sets then, please, let me know. Thanks!

@Plkmoi It's possible that the Google Translate team is working on adding Caucasian languages in the somewhat near future. In fact, I somehow feel pretty good about that hunch. But I can't say any more for legal reasons at the moment (wink wink).

@Plkmoi It's possible that the Google Translate team is working on adding Caucasian languages in the somewhat near future. In fact, I somehow feel pretty good about that hunch. But I can't say any more for legal reasons at the moment (wink wink).

If you have any contact, I'd be interested in helping out. I've also been getting together things for doing TTS tools.

@dotsuzu I do have a contact! What's a good email so I can reach out and cc you?

Great :)
<EMAIL_ADDRESS>(not .com)
Telegram: @suzumiyachan


Regarding computational power and training time

Hello! Thank you for your code implementation.
It would be very helpful if you mention approximately how much time was required for the model training per experiment. And what computational devices were being used during the experiments (Number and type of GPU/TPU's).
Looking forward to hearing from you soon.

We counted the training time, about 4 hours or so of training. We used 8 GPUs, our GPU is Tesla V100. if you want to go even faster, please use fp16 for acceleration.


Merge our branch with the master master

We did a lot of updates and had the client approve the work We would like to merge this back into tap-git:master

Ok, will do the merge.


GraphQL error: Could not resolve to a User with the login …

What's going wrong here and why?

Fehler im Cronjob:
🇩🇪  ✔ ~/temp [master|…1]
16:01 # diff -s ~/logs/crontab.root-ubuntu-cx11-02n ~/logs/crontab.root-ubuntu-cx11-02
41c41
< */15 * * * * df -t fuse.sshfs 2>&1 | grep -q 'Transport endpoint is not connected' && { ~/bin/hetzner.sh umount; ~/bin/hetzner.sh mount; systemctl restart<EMAIL_ADDRESS>docker.service; ~/bin/create-github-issue "$(echo "Am $(date +\%d.\%m.\%y) um $(date +\%H:\%M): Transport endpoint is not connected")" "$(docker ps; systemctl status<EMAIL_ADDRESS>pihole*)" thomas-merz https://github.com/thomasmerz/upptime/ >/dev/null; }
---
> */15 * * * * OUT="$(df -t fuse.sshfs 2>&1 | grep -q 'Transport endpoint is not connected')" && { ~/bin/hetzner.sh umount; ~/bin/hetzner.sh mount; systemctl restart<EMAIL_ADDRESS>docker.service; ~/bin/create-github-issue "$(echo "Am $(date +\%d.\%m.\%y) um $(date +\%H:\%M): Transport endpoint is not connected" "$(docker ps; systemctl status<EMAIL_ADDRESS>pihole*)")" thomas-merz https://github.com/thomasmerz/upptime/ >/dev/null; }
57,59c57,59
<  1 */3 * * 0-5 ~/mnt/hetzner/projects/cron/spotify-ripper1 >/dev/null || ~/bin/create-github-issue "$(echo "Am $(date +\%d.\%m.\%y) um $(date +\%H:\%M): Transport endpoint is not connected")" "" thomas-merz https://github.com/thomasmerz/upptime/
< 31 */3 * * 0-5 ~/mnt/hetzner/projects/cron/spotify-ripper2 >/dev/null || ~/bin/create-github-issue "$(echo "Am $(date +\%d.\%m.\%y) um $(date +\%H:\%M): Transport endpoint is not connected")" "" thomas-merz https://github.com/thomasmerz/upptime/
< 46 10  * * 6   ~/mnt/hetzner/projects/cron/spotify-ripper3 >/dev/null || ~/bin/create-github-issue "$(echo "Am $(date +\%d.\%m.\%y) um $(date +\%H:\%M): Transport endpoint is not connected")" "" thomas-merz https://github.com/thomasmerz/upptime/
---
>  1 */3 * * 0-5 OUT="$(~/mnt/hetzner/projects/cron/spotify-ripper1 >/dev/null)" || ~/bin/create-github-issue "$(echo "Am $(date +\%d.\%m.\%y) um $(date +\%H:\%M): Transport endpoint is not connected")" "" thomas-merz https://github.com/thomasmerz/upptime/
> 31 */3 * * 0-5 OUT="$(~/mnt/hetzner/projects/cron/spotify-ripper2 >/dev/null)" || ~/bin/create-github-issue "$(echo "Am $(date +\%d.\%m.\%y) um $(date +\%H:\%M): Transport endpoint is not connected")" "" thomas-merz https://github.com/thomasmerz/upptime/
> 46 10  * * 6   OUT="$(~/mnt/hetzner/projects/cron/spotify-ripper3 >/dev/null)" || ~/bin/create-github-issue "$(echo "Am $(date +\%d.\%m.\%y) um $(date +\%H:\%M): Transport endpoint is not connected")" "" thomas-merz https://github.com/thomasmerz/upptime/
🇩🇪  ✔ ~/temp [master|…1]

Does not seem to be related to https://github.com/cli/cli/issues/3224


Feature/1372/fc launch bug

Hide Launch with FireCloud if No Content
ga4gh/dockstore#1372
Created a launch-third-party component to both more easily unit
test and to add new upcoming third party integrations.
Turn on Launch with FireCloud by default
Unit test was failing with flag set to false. Since the flag has been
turned on in production, make it the default.

Codecov Report

Merging #280 into develop will increase coverage by 0.32%.
The diff coverage is 94.59%.

@@             Coverage Diff             @@
##           develop     #280      +/-   ##
===========================================
+ Coverage    63.06%   63.39%   +0.32%
===========================================
  Files          119      120       +1
  Lines         3577     3614      +37
  Branches       393      399       +6
===========================================
+ Hits          2256     2291      +35
  Misses        1230     1230
- Partials        91       93       +2

Impacted Files
Coverage Δ

...p/myworkflows/my-workflow/my-workflow.component.ts
48.67% <ø> (ø)
:arrow_up:

src/app/shared/dockstore.model.ts
100% <ø> (ø)
:arrow_up:

...launch-third-party/launch-third-party.component.ts
94.59% <94.59%> (ø)

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 201cf16...77bbb0b. Read the comment docs.


issues with hdf5 1.10.5

In openmeeg in macosx in Travis-CI we are use libmatio from brew and stoped working after https://github.com/Homebrew/homebrew-core/commit/b3eb55b6c5bc1aae035be9867208320fa35c9fe3
was merged. The combination is matio-1.5.12 and hdf5-1.10.5.
Can anyone replicate that matio test suit breaks when using hdf5-1.10.5 ?
here is my trace:
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
  * frame #0: 0x00007fff5bfbe23e libsystem_kernel.dylib`__pthread_kill + 10
    frame #1: 0x00007fff5c074c1c libsystem_pthread.dylib`pthread_kill + 285
    frame #2: 0x00007fff5bf271c9 libsystem_c.dylib`abort + 127
    frame #3: 0x0000000100159d98 libhdf5.103.dylib`H5check_version + 588
    frame #4: 0x00000001004899f6 libmatio.4.dylib`Mat_Create73 + 86
    frame #5: 0x000000010010eaba libOpenMEEGMaths.1.dylib`OpenMEEG::maths::MatlabIO::write(this=0x0000000100128c58, os=0x00007ffeefbff1f0, linop=0x00007ffeefbff688) const at MatlabIO.H:218:30
    frame #6: 0x0000000100105760 libOpenMEEGMaths.1.dylib`OpenMEEG::maths::operator<<(OpenMEEG::maths::MathsIO&, OpenMEEG::LinOp const&)(mio=0x00007ffeefbff4a8, linop=0x00007ffeefbff688) at MathsIO.C:89:26
    frame #7: 0x00000001000f1718 libOpenMEEGMaths.1.dylib`OpenMEEG::Vector::save(this=0x00007ffeefbff688, filename="tmp_matrix.mat") const at vector.cpp:165:70
    frame #8: 0x0000000100003591 OpenMEEGMathsTest-vector`main at vector.cpp:69:7
    frame #9: 0x00007fff5be7eed9 libdyld.dylib`start + 1
    frame #10: 0x00007fff5be7eed9 libdyld.dylib`start + 1
(lldb) frame select 5
frame #5: 0x000000010010eaba libOpenMEEGMaths.1.dylib`OpenMEEG::maths::MatlabIO::write(this=0x0000000100128c58, os=0x00007ffeefbff1f0, linop=0x00007ffeefbff688) const at MatlabIO.H:218:30
   215                      os.close();
   216                      std::remove(name().c_str());
   217                  }
-> 218                  mat_t* mat = Mat_CreateVer(name().c_str(),NULL,MAT_FT_MAT73);
   219                  if (!mat)
   220                      throw BadFileOpening(name(),maths::BadFileOpening::WRITE);
   221
(lldb) l
   222                  if (linop.dimension()==1)
   223                      write<Vector>(mat,linop);
   224                  else {
   225                      switch (linop.storageType()) {
   226                          case LinOp::SPARSE:
   227                              write_sparse(mat,linop);
   228                              break;
(lldb)

I would also propose to have some repos with the CI running system recipies: brew, conda, whatever people use. This would allow for early detection of problems.
@tbeu could this be related to fixes in 1.5.13? if so updating brew receipies should fix the problem.

Seems like a configuration issue, since H5check_version fails. Probably the hdf5 headers that were used when building libmatio do not match the version of the hdf5 libraries.

yes that's exactly it. I thought it was in our end, but not. However, having a CI running all these things would allow us to report issues faster. This was broken in Oct 2018. It cannot be that we realize about those things 6 month afterwards.


[cmake] Bump minimum version to 3.4.3

This pull request depends on https://github.com/apple/swift/pull/5112, which fixes warnings that are upgraded to errors in CMake 3.4.3. Please review that pull request before this one.
The Swift README states that the minimum CMake version required to build the Swift project is the same as LLVM's: 3.4.3. Bump the minimum version used by CMake to correspond to the README.

This addresses a suggestion left by @gottesmm and @llvm-beanz on https://github.com/apple/swift/pull/4999.

When I tried this once, IIRC, swift-remoteast-test target need ENABLE_EXPORTS to compile because of CMP0065:
set_target_properties(swift-remoteast-test PROPERTIES ENABLE_EXPORTS 1)

Oh cool, thanks for the tip!

When I tried this once

Do you still have that code somewhere? I'd be happy to resurrect your pull request, as opposed to using this one. :)

The LLVM_COMMON_DEPENDS part of this patch is actually hacking around a bug in LLVM's handling of LLVM_ENABLE_MODULES I would rather we didn't do that in Swift and instead fixed the bug in LLVM.
What is happening in LLVM is that when you set LLVM_ENABLE_MODULES=On intrinsics_gen gets added as a target of basically everything. That is done so that everything ends up depending on module generation. That is a hack. The bug you're seeing is that by putting intrinsics_gen in LLVM_COMMON_DEPENDS at the root CMakeLists file in LLVM it ends up getting written into the LLVMConfig.cmake export file. LLVM should never put anything in LLVM_COMMON_DEPENDS in the export file unless it is a target being exported. Since intrinsics_gen doesn't install any files, it doesn't exist in the exported targets.
I spoke with @vedantk about this last week. I'll circle back with him this morning, and we can get a fix into LLVM trunk and into swift-llvm this morning.

Code is here https://github.com/apple/swift/compare/master...rintaro:cmake-3.4.3, that's all I modified :)
I don't have PR for this because I haven't tested this in macOS environment.

@swift-ci please clean test

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 6eab4159d5a2ec3a331d449d21bdb533c543c7ea
Test requested by - @modocache

@swift-ci please clean test

The builds passed! Can I get someone's stamp of approval on this, to bring our CMake into 3.4.3? 😍
Also, thanks to @rintaro -- this pull request is nearly exactly what he wrote in https://github.com/apple/swift/compare/master...rintaro:cmake-3.4.3. 🙇

Whee! Thanks, @gottesmm!


GTot functions in lemmas

I would like to use GTot functions f in lemmas, which is not possible right now because GHOST and PURE effects are not compatible.
What would be the proper way to do that ?
I would like that f function to be erased by the backend but still be able to use it in proofs.

I made hide a pure function:
https://github.com/FStarLang/FStar/commit/6e440d07f89b25558ad8aeedbffb282e93240ce7
The idea that the only way you can use a hidden thing is by using reveal. But you can use reveal only in a ghost context. So, there is no need to require even hide to be in a ghost context.
Now, you can rewrite your f to have pure effect, but produce a hidden value.
I'll try to post a concrete example.

I do not see those elif functions, were they commited ?
Also my issue is that I want to define a recursive function like
val id : int -> Tot int
let id x =
    match x with
    | 0 -> x
    | _ -> 1 + id (x-1)

Because of the recursive call, if I return an erased int I also have to reveal it, which leads to a computed GTot effect rather than a Tot effect.
The function can probably be rewritten with an accumulator to make it work, but that means that existing specs have to be rewritten throuhoutly.
Since the new extraction no longer accepts the "erase" function, it makes it quite hard for me to switch to the new backend.

https://github.com/FStarLang/FStar/blob/master/lib/ghost.fst#L44
Going by the analogy of Coq's Prop, I think it is safe to remain in Pure effect as long as we return a hidden value. So, we should add a combinator to lib/ghost.fst that lets you define your I'd to have type (erased int) -> Tot (erased int)

Ghost functions that return non-informative types are promoted to PURE. This should now be possible today.


[proposal] (. ) checked application

[@bs] f (a,b,c)
-->
f (. a, b,c)

[@bs]
let f = (b,c) => {b + c }
-->
let f = (. b, c) => {  b + c}

I think this makes sense now, under the new application syntax

@chenglou  f (.)

cc @IwanKaramazow
I'm ok with this I think. Though it might not be the time to onboard newcomers and introduce two application syntax yet. Not sure

Ok, working on it

could this be prioritized? we will add a few libs, having a native syntax for uncurried callback will help people consume such libs

Yes, I'll see what I can do this week.

I believe the snippet should have been:
let f = [@bs] ((a, b) => a + b);

Would let f = (. a, b) => a + b; have type (int * int) -> int? or would it be int -> int -> int?

Nono, it has nothing to do with tuples. It's a BuckleScript-specific optimizations that annotates the type with some info that the BS compiler understands.
If you wanted tuple you can do it today (two layers of parens)

ah, okay. So it's typed the same way as a normal function, but with some annotations?


d_a_obj_xfuta match

You can update xfuta in configure.py to be "Matching" instead of "NonMatching". Then the system will automatically check it to be sure it's correct.

You still need to move tev_mode out of the header file.


Feature to specify binlog position, file and gtidset to start the replication

Feature to specify binlog position, file and gtidset to start the replication

Fixed in #260


[FLINK-22408]Flink Table Parsr Hive Drop Partitions Syntax unparse is Error

What is the purpose of the change
Flink Table Parsr Hive Drop Partitions Syntax unparse is Error
Brief change log
Flink Table unpase is error：
Synopsis:
SQL：
alter table tbl drop partition (p1='a',p2=1), partition(p1='b',p2=2);
hive muit partition unparse toSqlString is :

ALTER TABLE `TBL`\n" +
      "DROP\n" +
      "PARTITION (`P1` = 'a', `P2` = 1)\n" +
      "PARTITION (`P1` = 'b', `P2` = 2)

Missing comma in Partition SqlNodeList
Hive syntax：
ALTER TABLE table_name DROP [IF EXISTS] PARTITION (partition_spec) [, PARTITION (partition_spec)];

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@flinkbot run azure

@flinkbot run travis

@flinkbot run azure

@flinkbot run azure

@flinkbot run azure

close PR, fix this issue in release-1.12 branch


[5.9] Delegate to php native type casting

No need to call a library API, since the concrete is not going be a object type.
(string or an array of strings.)

It seems to be working fine as is and there can be subtle differences between Arr::wrap and casting.


Add a wiki: Mega Man Knowledge Base

An anonymous user has submitted a new wiki via our submission form.
Link to origin wiki: https://megaman.fandom.com/wiki/Mega_Man_Knowledge_Base
Link to destination (independent) wiki: https://megaman.miraheze.org/wiki/Mega_Man_Knowledge_Base

Leaning towards not including due to a (growing) content gap and lack of staff. The Fandom currently has 5,830 articles vs. the fork's 5,343, and the fork has only had 7 edits over the last 30 days. Fork has one staff member who hasn't edited since November.

Noting that there is another independent Mega Man wiki at https://megamanwiki.com/ -- this one is being written from the ground up and currently has 220 articles.


FAQ

As the project develops, we still don't have a section of Frequently Asked Questions to refer people to in social media interactions. We manually type answers to questions like: 'what is Locha mesh?' 'why a mesh?' Sometimes even 'what is a mesh?'
As more people is getting involved in the conversation, it is time to address this questions in a better way. I invite the devs to join in this topic by participating in the process of answering questions, correcting typos, concepts, suggesting, etc.
Questions listed by me:

What is a mesh network and what is Locha Mesh?
Why is Locha Mesh licensed under the Apache License 2.0?
What is a ‘Turpial’ node?
What is a ‘Harpia’ node?
How does the Locha Mesh work?
What can be transmitted over the Locha Mesh?
How far in kilometres (km) can you transmit data over the Locha Mesh?
What radio frequencies can a Turpial node or a DIY Turpial node use and why?
Why do we need a decentralized mesh network?
Can other devices join the Locha Mesh network?
How many devices running the Locha Mesh protocol are needed to create a mesh?
Do I need to be ‘on-line’ at all times to receive messages?
I want to contribute to this project. Where do I start?
I can’t donate any money, nor code. How else can I help?
Can’t find an answer to your question?

Note that every question follows a logic order. I will submit a PR with answers suggested by me to these questions.

What is a mesh network and what is Locha Mesh?

A Mesh network is conformed of distributed nodes that contribute to the network by maintaining connections, routing packets, etc. to other nodes.
Locha Mesh is a type of Mesh network that tries to improve the actual status of the available Mesh network solutions by providing an IPv6 capable network on which most applications can run most of the times.

Why is Locha Mesh licensed under the Apache License 2.0?

The Apache License 2.0 is very permissive, this means any user can use our code freely (giving proper attribution)  and modify them. Users of the source code aren't also forced to contribute back the changes they make or publish them.

What is a ‘Turpial’ node?

A Turpial node is a low current consumption portable device which participates in the Mesh network, it can be used to connect to the Locha Mesh up to four devices over Wi-Fi (to participate on the network) and a computer over USB (currently only Linux/Mac OS X support for USB, Wi-Fi works out of the box).

What is a ‘Harpia’ node?

A Harpia node is a Locha Mesh node that works standalone and can run/provide services on the network such as a Bitcoin transaction gateway, or any other.

How does the Locha Mesh work?

Locha Mesh works by having multiple nodes collaborate on the network, each node implements an specific routing protocol which makes all nodes connected to the network available through multiple hops. We use IEEE 802.15.4g radios (915 MHz on some countries, may vary), and a 6LoWPAN/IPv6 stack.
To route packets over the network we implemented an AODVv2 protocol which only finds a route to a node when we ask for it, so it's relatively efficient to use.

What can be transmitted over the Locha Mesh?

Pretty much anything that supports IPv6 can participate on the Locha Mesh network, if it sends IPv6 packets, it works.

How far in kilometres (km) can you transmit data over the Locha Mesh?

This depends where the node is located and the obstacles it might have, and the maximum transmit power. A normal IEEE 802.15.4g radio can transmit up to 14 dBm, and the Turpial can/could transmit at +26 dBm.

What radio frequencies can a Turpial node or a DIY Turpial node use and why?

As we use IEEE 802.15.4g we are going to use 915 MHz which license-free in most countries, or any of the others that are defined for IEEE 802.15.4g.

Why do we need a decentralized mesh network?

Decentralized networks are censorship resistant and are useful in areas where cabled internet connections are difficult to get. Also mesh networks are useful because they are failure-tolerant, any node can replace the functions of the other, this is typically useful in natural disasters or remote areas.

Can other devices join the Locha Mesh network?

If it implements an IEEE 802.15.4g radio and the protocols need to communicate then yes.

How many devices running the Locha Mesh protocol are needed to create a mesh?

At least two and they'll start talking each one if they're on range.

Do I need to be ‘on-line’ at all times to receive messages?

This question depends on the aim it's taking. Not easily answerable. If it's for the Chat app, then no, currently we don't implement re-transmissions of messages. However for other protocols it works the same way as Internet.

I want to contribute to this project. Where do I start?

There is the btcven/radio-firmware repository and the btcven/turpial-firmware repository which are the firmwares of the MCUs used to create the Locha Mesh network. There are issues labeled with good first issue with are a good start to contribute to the project and to get knowledge of the codebase.

I can’t donate any money, nor code. How else can I help?

Spread Locha Mesh to the world :D. Also if you know other languages you can help with the translation of the documentation to other languages.

Can’t find an answer to your question?

Open an issue for it, this way we can get in touch if something is not clear. Also, if you feel something is not in the FAQ, better yet, open a PR for it :).

I think it's better to answer point by point and to handle the discussion in a better way @jeandudey and not everything together.
So the first question

What is a mesh network and what is Locha Mesh?

This question should be split in two:

What is mesh network?
A mesh network is a network topology where each node connect directly, dynamically and non-hierarchically to as many other nodes as possible and cooperate with one another to efficiently route data from/to clients.

What is Locha Mesh?
It is a type of mesh network that tries to improve the real state of available mesh network solutions by providing an IPv6 compliant network that most current applications can run on.

Why is Locha Mesh licensed under the Apache License 2.0?
It's very permissive, this means any user can use our code freely and modify them. know more

What is a Turpial node?

A curated piece of hardware able to participate in the Locha Mesh network, can give network access up to four devices (PC, mobile, tablet,..) simultaneously via WiFi. It's therefore a router but in a portable format, battery powered and plug and play.

What is a ‘Harpia’ node?

I think the response of @jeandudey for this question is perfect

We need something shorter here:

How does the Locha Mesh work?

By having multiple nodes, their behavior can resemble a community of bees, they collaborate with each other to put the origin and destination in contact using AODVv2 as a routing protocol

We need something shorter here:

How does the Locha Mesh work?

By having multiple nodes, their behavior can resemble a community of bees, they collaborate with each other to put the origin and destination in contact using AODVv2 as a routing protocol

I really don't get the bees example, but this is something I prepared for this question:
"Mesh networks can relay messages following a routing protocol. The Locha Mesh uses an AODVv2 and we are adding an extra feature for control packets in order to be able to check if routes continue being valid and keep the routing tables updated.
Once the device is paired with the smartphone, it will start searching for neighbors in an attempt to relay messages from them. Knowing its neighbors will provide the routes the device needs for proper calculation of the path for the data to be transmitted."

Why is Locha Mesh licensed under the Apache License 2.0?

It's very permissive, this means any user can use our code freely and modify them. know more

Yes, the Apache License 2.0 is widely used in the tech industry as well, e. g. Android.

@jeandudey thanks for answering all the listed questions!

"Mesh networks can relay messages following a routing protocol. The Locha Mesh uses an AODVv2 and we are adding an extra feature for control packets in order to be able to check if routes continue being valid and keep the routing tables updated.

Once the device is paired with the smartphone, it will start searching for neighbors in an attempt to relay messages from them. Knowing its neighbors will provide the routes the device needs for proper calculation of the path for the data to be transmitted."

Imprecise
AODVv2 is not a proactive protocol, so it will search neighbors only when it's necessary: send a message, get access to a web server, etc.
anyway the response need to be shorter

remove the bees example:
By having multiple nodes, they collaborate with each other to put the origin and destination in contact using AODVv2 as a routing protocol.

How far in kilometres (km) can you transmit data over the Locha Mesh?

That depends on multiple factors, but an approach can be up to 6 km in line of sight and a clean environment of electromagnetic noise.
Add a new question:

what factors can affect the coverage range?

What radio frequencies can a Turpial node or a DIY Turpial node use and why?

This depends on your location, there are different frequencies for each location, 868MHz and 915MHz are available for EU and American respectively [See which band is used legally in your country] (link_to_table_freq)

what factors can affect the coverage range?

Electromagnetic noise, obstacles between antennas, antenna altitude or antenna type are the reasons that can most affect the coverage range.

This is a really good question, I'll add it to the FAQ!

What radio frequencies can a Turpial node or a DIY Turpial node use and why?

This depends on your location, there are different frequencies for each location, 868MHz and 915MHz are available for EU and American respectively [See which band is used legally in your country] (link_to_table_freq)

I wrote something similar to this:

The Turpial device uses a 915 MHz radio module, other versions of the same Turpial device could work with different radio modules for the 868 MHz band or 433 MHz band for different regions.

But I think it's important to mention the ISM band as unlicensed bands/frequencies that can be used permissionless.


Upgrade jemalloc to 4.2.1

Please note I've got an error:
Step 6 : ADD ./postgresql.tar.gz /tmp
lstat postgresql.tar.gz: no such file or directory
make: *** [cedar-14-stack] Error 1

so I had to comment out lines 13-28 from cedar-14-stack while building. Have no Idea why are these lines needed.
Here's the compiled jemalloc: https://www.dropbox.com/s/hsw795xjd6lg9cs/jemalloc-4.2.1-1.tar.gz?dl=0

Good catch. Those are leftovers from a different buildpack, so they should actually be removed. Mind adding that to the PR?
/cc @nateberkopec

@mojodna sure, done.

Sweet, thanks. It's late here, so I'm going to let Docker chug away at building the cedar image and merge this tomorrow (since merging immediately will break the buildpack, as it points to a non-existent-so-far binary).

Great, thank you.

@heaven tagged as v4.2.1. Can you test when you get a chance?

(To be clear, I've tested to make sure that the library gets dropped on Heroku in the right place, but it would be good to verify that it works with an app that's exercising it.)

Hey, just deployed an application and the build went well:
remote: -----> Fetching set buildpack https://github.com/mojodna/heroku-buildpack-jemalloc.git... done
remote: -----> jemalloc app detected
remote: -----> Vendoring binaries
remote:        Fetching https://github.com/mojodna/heroku-buildpack-jemalloc/releases/download/4.2.1/jemalloc-4.2.1-1.tar.gz
remote: -----> Configuring build environment
remote: -----> Building runtime environment

Both web and worker processes started well:
web jemalloc.sh bundle exec puma -C ./config/puma.rb
worker jemalloc.sh bundle exec sidekiq --config config/sidekiq.ym

A couple days ago I've also updated jemalloc from 3.6.0 to 4.2.1 on a few other servers which do run ruby/rails apps and so far they show much better memory utilization (we do suffer from severe heap fragmentation there).
Thank you for merging this!


Support contracts with the same name #1203

Hey @melnikaite, thanks for tackling this one! Let me know when it's ready for review :+1:.

Hi @jcarpanelli
I manage to successfully run oz push, but stuck with oz create, because it try to install contract/name as npm dependency, but obviously there is no such npm package and I didn't find the place where sdk check if it should run npm install

Hey @melnikaite! Thanks for the contribution :-)
Is this the function you are looking for regarding installing an npm dependency?
https://github.com/OpenZeppelin/openzeppelin-sdk/blob/5140c692f62a9858ee6580f2521197a938819a4b/packages/cli/src/models/dependency/Dependency.ts#L69-L74

Yes, but in fact my issue was in fromContractFullName
It seems functionality works fine for all commands, but currently I don't have time to fix all the tests


Supershell produces redudant lines

On the latest develop branch, if I run test in io, I get something like this:

It happens with both iterm2 and terminal.app.

Yea. I've seen that. I wonder if there are multiple reports running simultaneously, or it's printing on top of the other so it looks that way.

I don't know if this is the same or different, but with both 1.3.0-RC4 and 1.3.0-RC5 I'm seeing supershell output get mixed up with regular output, so for example over at https://github.com/SethTisue/Project-Euler :

Eugene I'm short on time at the moment but I could investigate / follow up more next week if you want

@SethTisue might be https://github.com/scala/nanotest-strawman/issues/20

looking at that animation, it appears to me that a bunch of tests are running in parallel, that's a good thing, and there's no issue? am I mistaken?

I'm not sure if it's multiple tests that's causing this, but I don't think there should be multiple lines of supershell countup clock displayed per task.
  | => io / Test / executeTest 4s
  | => io / Test / executeTest 3s
  | => io / Test / executeTest 3s
...

Yeah. That is specifically what I created this issue for. I’d expect only one io / Test / executeTest line.

@SethTisue is correct about the underlying cause though I think it's suboptimal from a ux perspective. The test task delegates to a number of anonymous tasks and they all inherit the name of the calling task, executeTest. This is actually a general problem for the progress reports. As it currently stands, we actually report something more like utime vs walltime in the reports:
Total time: 16714 ms
  io / Test / executeTests                                    : 48376 ms
  io / Compile / previousCompile                              :   159 ms

I think it would make sense to aggregate the tasks by name and calculate both the the wall time max(end) - min(start) as well as the total time sum(end - start) for all tasks. For the purpose of supershell, we'd just display a single time with a running counter based on the current max(end) - min(start).

that's interesting.
the impetus for super shell is to surface what's going on inside of sbt's task engine, so if it is in fact the case that there are multiple effect monads processing the test suites, that's great, and my stance then would be to visualize that fact more effectively. Maybe we should distinguish the tasks by some sequential number (test group id?), or JVM thread id.

I think I have a nice solution here: https://github.com/sbt/sbt/pull/5023

Closing since #5023 is merged.


fix: add param names to jsdocs, remove types separation

Hey,
while we tried to use this library discovered that there are small issues with type declarations:

Few typescript types miss names for variables as they are missing in jsdocs.
We couldn't use library as typescript types were exported to separate directory, while usually they are alongside source code (commonJS).

PR fixes both issues.

Hey, while we tried to use this library discovered that there are small issues with type declarations:
1. Few typescript types miss names for variables as they are missing in jsdocs.

2. We couldn't use library as typescript types were exported to separate directory, while usually they are alongside source code (commonJS).

PR fixes both issues.

What did you run into when using the library?

Hey, while we tried to use this library discovered that there are small issues with type declarations:
1. Few typescript types miss names for variables as they are missing in jsdocs.

2. We couldn't use library as typescript types were exported to separate directory, while usually they are alongside source code (commonJS).

PR fixes both issues.

What did you run into when using the library?

We are using it for node backend with nestjs.

Thank you @szaldivar for commenting and reviewing the Pull request. I will leave it with you since you have a deeper understanding of the topic.


Update documentation to remove warnings

Codecov Report

Merging #62 (75d864d) into main (0ba4f6e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #62   +/-   ##
=======================================
  Coverage   19.47%   19.47%
=======================================
  Files           4        4
  Lines         760      760
=======================================
  Hits          148      148
  Misses        612      612

Impacted Files
Coverage Δ

R/process1KG.R
42.78% <ø> (ø)

R/tools.R
10.47% <ø> (ø)

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 0ba4f6e...75d864d. Read the comment docs.


Remove duplicated CSS code

Do not really understand, why this code is not grouped.

Each group represents a type of reset. Please refer to the contribution guide before opening a PR.
Closing.


ISPN-10458 Address comments on ISPN-9723

https://issues.jboss.org/browse/ISPN-10458

@wburns https://github.com/infinispan/infinispan/pull/7168#pullrequestreview-271762541 :)

@danberindei

One thing that bothers me in a lot of tests is that you're using eventually* because notification/passivation/activation are non-blocking, but IMO even if they are non-blocking they should still prevent the read/write that triggered them from finishing.

So technically these are protected by the NonBlockingOrderer so atomicity is not lost. I figured it would be nice to improve throughput a bit by not having it block as we are just waiting on the store anyways. Unfortunately it makes usability for the product easier but tests are a bit more annoying. I thought it was a fair tradeoff

@danberindei

One thing that bothers me in a lot of tests is that you're using eventually* because notification/passivation/activation are non-blocking, but IMO even if they are non-blocking they should still prevent the read/write that triggered them from finishing.

So technically these are protected by the NonBlockingOrderer so atomicity is not lost. I figured it would be nice to improve throughput a bit by not having it block as we are just waiting on the store anyways. Unfortunately it makes usability for the product easier but tests are a bit more annoying. I thought it was a fair tradeoff

I see... I thought you'd have to wait for the store to finish, so that the PassivationPersistenceManager map size would be limited to the number of concurrent cache operations, otherwise the map could grow indefinitely.

I see... I thought you'd have to wait for the store to finish, so that the PassivationPersistenceManager map size would be limited to the number of concurrent cache operations, otherwise the map could grow indefinitely.

Technically waiting would help if a single thread was invoking put in a tight loop, but it wouldn't help putAsync or others. But doing put in a tight loop you would already be buying yourself breathing room as the user would be stuck waiting on other things besides the store, such as network replication - so it isn't as big of a deal as putAsync which is unaffected.

Overall looks good, just a couple of very minor things. Also, I'm happy keeping this as three commits, but could you make the inner message the top-level commit message. For example: "ISPN-10458 Fixed window of losing entry during activation and passivation".

Our guideline is to have the JIRA name as the first line.

Technically waiting would help if a single thread was invoking put in a tight loop, but it wouldn't help putAsync or others. But doing put in a tight loop you would already be buying yourself breathing room as the user would be stuck waiting on other things besides the store, such as network replication - so it isn't as big of a deal as putAsync which is unaffected.

Even for putAsync in a loop we can warn the users that they should set a limit on the number of concurrent operations, otherwise their cache could use unlimited memory. (And eventually I espect us to implement a mechanism to limit the number of concurrent operations, blocking or not.) Without delaying the operation end, I'm not sure there's anything users could do to limit the number of entries in the PassivationPersistenceManager map.

Our guideline is to have the JIRA name as the first line.

@wburns IMO that only applies if you have a single commit for the issue. Most of the time one sees only show the commit subject (i.e. the first line), so having 3 commits with the same subject doesn't look good.

Everything should be accounted for except renaming commits and
https://github.com/infinispan/infinispan/pull/7168/files/689930be94e2c3d51f4d19b8f92fbefa6af537cf#diff-d70f5361c5448faaa6e2d954a02b42bb
https://github.com/infinispan/infinispan/pull/7168/files/689930be94e2c3d51f4d19b8f92fbefa6af537cf#diff-734dc64b1cd5e29940a872f024271249

Just the two comments remain. I think they should be able to fixed separately. This PR itself fixes a bug that causes some tests to fail intermittently, where as the others are either an extreme edge case or something that needs to be investigated further.

Two other issues we will want to log
https://github.com/infinispan/infinispan/pull/7168#discussion_r313531023
https://github.com/infinispan/infinispan/pull/7168#discussion_r313452915

Our guideline is to have the JIRA name as the first line.

I thought our guideline was just for the JIRA ID to be in the top line. I don't think we ever stipulated that the top line message always has to be the same as the Jira title. If we did, we certainly don't follow that rule. For example: https://github.com/infinispan/infinispan/compare/e95d5a21826cd8fe3bb242a64fee47ac0c35a66c...9975bdc83b8e3d31a630f3b1ddc85570f6ab3b14

Oh I agree it hasn't been closely followed by everyone.
https://infinispan.org/docs/stable/contributing/contributing.html#comments
On Wed, Sep 4, 2019, 5:33 AM Ryan Emerson<EMAIL_ADDRESS>wrote:

Our guideline is to have the JIRA name as the first line.
I thought our guideline was just for the JIRA ID to be in the top line. I
don't think we ever stipulated that the top line message always has to be
the same as the Jira title. If we did, we certainly don't follow that rule.
For example: e95d5a2...9975bdc
https://github.com/infinispan/infinispan/compare/e95d5a21826cd8fe3bb242a64fee47ac0c35a66c...9975bdc83b8e3d31a630f3b1ddc85570f6ab3b14
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/infinispan/infinispan/pull/7191?email_source=notifications&email_token=AAE6H3Z4R5LHHGOWH6IW3LDQH56GDA5CNFSM4IKB5PAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD527DVA#issuecomment-527823316,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAE6H34EOBHWH4N3JE32NDDQH56GDANCNFSM4IKB5PAA
.

@wburns NPE on TxStoreTest.testTxRollbackOnStoreException still. The commits need rebasing etc as well

ah didn't notice it, fixing.

NPE fixed.

Updated per all the comments

I got a failure on my machine:
pr_wburns_ISPN-10458_review_20190926-1956_EvictionWithPassivationAndConcurrentOperationsTest-infinispan-core.log.gz

Fixed comments, looking at failure.

Test failure was caused by not replacing the original orderer in the test. So both threads were stuck waiting on the checkpoint and it was non deterministic which would acquire the orderer first. Now the test guarantees the proper thread retrieves the orderer as the test was designed to do.

Also added a couple more trace messages just to be safe :)

Should be ready again @danberindei !

Updated and rebased.

Integrated, thanks Will!


Setting ImplicitParagraph has no effect

As far as I understand, setting ImplicitParagraph to false should prevent markdig from wrapping rendered HTML in a
.
However, the following test does not behave as expected
            var pipeline = new MarkdownPipelineBuilder().Build();
            var writer = new StringWriter();
            var renderer = new Markdig.Renderers.HtmlRenderer(writer);
            renderer.ImplicitParagraph = false;
            pipeline.Setup(renderer);
            var foo = Markdown.ToHtml("test", pipeline);

            // foo is "
test
\n" and not "test"

Furthermore, this parameter (and the couple more similar) are only interesting at render time and as such, they should be directly settable -- the user should not be forced to go through 5 lines of setup to set a basic option, such as when rendering a snippet. This also makes them basically undiscoverable.

Furthermore, this parameter (and the couple more similar) are only interesting at render time and as such, they should be directly settable

I don't remember the details of this particular parameter, but these parameters on the Renderer class are often render states used by the renderers and not always settable by end-user. So their discover-ability was absolutely not a concern, unless you want to develop a new custom renderer.

Furthermore, this parameter (and the couple more similar) are only interesting at render time and as such, they should be directly settable -- the user should not be forced to go through 5 lines of setup to set a basic option, such as when rendering a snippet. This also makes them basically undiscoverable.

Well, the situation could have been worse, I could have decided back in the days to make them completely internal. But at least, the API is giving you a chance to have an access for it, so that's not that bad right?
I'm no longer in the details of the API to propose anything right now, nor I have dedicated personal time to track this, so if you could take the time to make a proposal, and a PR, that would be helpful.

ImplicitParagraph is false by default, if you don't want paragraph tags, set it to true.
Also Markdown.ToHtml creates its own renderer. If you create your own HtmlRenderer you have to render on it explicitly like so:
var pipeline = new MarkdownPipelineBuilder().Build();

var document = Markdown.Parse("test", pipeline);

StringWriter writer = new StringWriter();
var renderer = new HtmlRenderer(writer);
renderer.ImplicitParagraph = true;
pipeline.Setup(renderer);

renderer.Render(document);
writer.Flush();
string html = writer.ToString();
// test

OK, so first of all thanks for clarifying the problem and its solution. I agree that a helper method would improve the situation, perhaps with some extra docs.
This worked for me, although it needs to be moved to the right class, tested etc.
    public static class Mark {
        public static string ToHtml(string markdown, MarkdownPipeline pipeline, Action<HtmlRenderer> setupAction)
        {
            var writer = new StringWriter();
            var renderer = new Markdig.Renderers.HtmlRenderer(writer);
            setupAction(renderer);
            renderer.Render(Markdown.Parse(markdown));
            return writer.ToString();
        }
    }

If you like the approach I'll push a PR tomorrow
Thanks,

If @xoofx agrees with the API shape, the implementation would probably be like so:
(note that I changed the parameters)
public static string ToHtml(string markdown, Action<HtmlRenderer> configureRenderer, MarkdownPipeline pipeline = null, MarkdownParserContext context = null)
{
    if (markdown is null) throw new ArgumentNullException(nameof(markdown));
    if (configureRenderer is null) throw new ArgumentNullException(nameof(configureRenderer));

    pipeline ??= new MarkdownPipelineBuilder().Build();
    pipeline = CheckForSelfPipeline(pipeline, markdown);

    var writer = new StringWriter();
    var renderer = new HtmlRenderer(writer);
    pipeline.Setup(renderer);

    configureRenderer(renderer);

    var document = Parse(markdown, pipeline, context);
    renderer.Render(document);
    writer.Flush();

    return writer.ToString();
}

I feel like this is all massively overcomplicated for the end user, for something that seems so basic and fundamental. Clearly there are a lot of situations where the user is going to want to render markdown inline.
It seems like this is all just a very roundabout way of handling something that should be done with the existence of ToInlineHtml() or ToHtml(bool inline = false)

I don't know if this specific case is so common that a dedicated overload would be necessary.
Most users requiring fine-grained control will likely want to adjust more than one thing and will already be doing the pipeline setup and rendering steps manually.

@MihaZupan  For what it's worth, I need it and I'm frustrated. I've been poking around trying to find a solution that isn't an overblown hack with little luck.

@MihaZupan For what it's worth, I need it and I'm frustrated. I imagine this must be very common (especially considering the upvotes on the comment asking for an overload).

Let me reiterate from my original response, that if someone wants such a feature, this person will have to make a PR for it with tests. 🙂


Add quiet option

Hi again,
As I was trying to add this script to another step in my release process, I stumbled upon the fact that it wasn't so easy to get only the version that was just tagged, as the script's output is always printed on each run.
So, instead of capturing the output and extracting only the last line, I added a -q, --quiet option. It's implemented with minimal changes to the code, borrowing heavily from tldp.org and has some design choices that are worth mentioning:

I only suppressed output to stdout. Any messages echoed to stderr will continue to output.
In the case of -b and -p options, it still outputs the help if no input is provided.
In case a script returns an error that prevents tagging, it won't echo anything.

I'm specially hesitant about the second point, because although I want to keep the original behavior, I can totally see the situation in which you run something along the lines of git semver major --release "$(my_awesome_release_generator)" and after the awesome release generator returns nothing, the scripts outputs "something" instead of failing echoing nothing, which might incorrectly signal the code was actually tagged.
Also, a not about the implementation: I wasn't able to find a lot of documentation, but as far as I can tell from this, this, and this links, using /dev/null should be compatible with Cygwin and MinGW. And also again, I remember MacOS had a /dev/null so I guess it should also work with it.
So, if you find this feature useful, let me know of any problems of improvements, and thanks in advance for reviewing.

Seeing the diff, I just realized I branched from the wrong commit, as I thought I made this MR when I didn't :/
I amended the lines differing from master, so this code is what I actually want to submit, but if you see it necessary, I'll close this MR and open a new one branching from the correct place.
Thanks, Fernando


Expose event when a selection is made but value is not changed (ie user selects the same value)

The event could be called unchanged.bs.select and would signify that the user made a selection, however the selection was the same as the previous value (ie it is 'unchanged')

What is your use case is for this event?


Remove owner role assignments from live test ARM templates

Remove owner role assignment from digital twins ARM template

Recent updates to the New-TestResources.ps1 script will do this assignment on deployment already. It is creating role assignment already exists errors for these templates.
FYI @jsquire @heaths @weshaggard @azabbasi

/azp run java - digitaltwins - tests

/azp run java - digitaltwins - tests


updater: Update postgres

WIP. Opening this as an early pull request for CI.
Things which need fixing:

[x] Don't rollback when a postgres deploy fails, just bail as rolling back will not help the situation
[x] Handle starting new postgres jobs when postgres is read-only (cannot scale using formations), or avoid trying to start jobs in that state
[x] Retry creating deployment event records when postgres is down / read-only
[x] Investigate the updater succeeding when a deployment fails (I suspect e.Err() is returning nil)

I have dealt with the initial issues by avoiding getting stuck in a read-only state, and retrying requests when Postgres is read-only, but another issue has revealed itself:
When killing the existing Primary, the deployers all get disconnected, and upon connection to the new Primary one of them starts to work the already in progress Postgres deploy (because there are no longer any locks on it), detects it is in a bad state and fails the deploy. Meanwhile though the initial deploy still runs, and eventually succeeds, but by this time the deployment has already been marked as failed.
Possible solutions:

Revisit adding a locked_until column on deployments (see #603), ensuring the deployer connects to the new Primary to continue bumping the lock
Handle updating Postgres directly in the updater rather than using the deployer (i.e. move the logic in postgres deploy strategy into the updater)

@titanous WDYT?

@titanous ok I'll give the locked_until approach a try, unless you have other ideas?

@lmars One thing to evaluate is doing this in que-go as we may have jobs in the future that we want the same protection for.

This is part of #276.

@titanous ready for a review.
Most changes are around reconnecting and handling transient postgres errors, and whilst there is still potential for errors to occur during the update, I have verified the cluster returns to a normal state once the update is complete.

@titanous comments addressed

LGTM


gracefully handle errors when gitlab remote cannot be created

Attempting to use a Gitlab repository that does not exist or cannot be accessed will cause the program to exit with an unhandled 404 error:
[2021-08-04T00:26:22.756Z] DEBUG: cautious-journey/2204068 on cerberus: created gitlab remote (dryrun=true, logger=Logger, type=gitlab-remote, container=Container)
    data: {
      "host": "https://git.apextoaster.com",
      "token": "..."
    }
uncaught error during main: Response code 404 (Not Found)

Handle that and do something useful.

Errors are now caught and logged, allowing remotes and projects to fail individually, without impacting other projects in the same run.


Clarify Tag_RISCV_arch is the minimum execution environment requireme…

…nt of objects
And also add NOTE to mention we could use more than Tag_RISCV_arch
specify, but must make sure that should work on the execution
environment with what Tag_RISCV_arch specify only.

Regardless of whether a specific solution can be agreed ahead of 1.0 or not, I think it would be helpful for the psABI to comment on the case of one ELF file with functions that target different architecture baselines. If it's something that isn't handled well right now but is planned for future work, it would be helpful to say so.

Further reflecting on this - it's not immediately obvious to me if/how this PR alters the status quo (vs my understanding of the current text at least).
The current text talks about taking Tag_RISCV_arch from -march. This effectively means that Tag_RISCV_arch will reflect the set of ISA extensions that a compiler may have selected without runtime feature checks. This provides enough to e.g. produce a meaningful diagnostic from an ELF loader if trying to load an rv64gc_zba_zbb_zbc_zbs binary on a system with B support.
I think part of the confusion / challenge with these ELF attributes is that we've looked to use them to solve multiple problems, but they're not well suited to solving all of them as defined and the problems aren't the same priority:

Basic link-time diagnostics when mixing and matching ELF files targeting different ISA baselines. Can be particularly useful on embedded targets IMHO.
Load-time diagnostics on larger systems. e.g. suppose a new 'G' baseline adds bitmanip extensions in the future, a sensible diagnostic can be emitted on systems trying to load these binaries that don't support those extensions.
Helping to guide a disassembler in how to decode instructions (i.e. indicating which instructions may be found in the object file). Given the attribute doesn't describe all extensions that could possibly be found in an ELF (except in the case those ISA variants were enabled via -march, when they could be generated in other ways e.g. function-specific attributes), it won't work for that purpose in all cases. It also couldn't work in the case of extensions that overlap in encoding space but which are included in the same file.

Changes:

Rebase
Adding more non-normative to describe the usage and recommend execution environment could use this info to checking executable

After few rounds of off-list chat I realized I put the design story in different places like .option arch[1] and mapping symbol [2] and obviously not understand if just read the description of Tag_RISCV_arch, so I added bunch of word in this update try to telling the full story here.
@asb do you mind take a look to see it's much clear to you now? I intentionally NOT document about disassembler part since mapping symbol ins't included in this release yet.
[1] https://github.com/riscv-non-isa/riscv-asm-manual/pull/67
[2] https://github.com/riscv-non-isa/riscv-elf-psabi-doc/pull/196

What do you think about adding a sentence to clarify what is meant by "minimum execution environment". e.g. "this information
used as the minimum execution environment requirement." => "this information reflects the minimum execution environment requirement. i.e. the set of instruction set extensions that the compiler may have used in code generation without any runtime feature detection or gating."

@asb , thanks for the suggestion, applied!

Defer this change, and adding another tag to mark this tag is minimum execution environment requirement.

I think "this information reflects the minimum execution environment requirement. i.e. the set of instruction set extensions that the compiler may have used in code generation without any runtime feature detection or gating." is a logical consequence of the references to this tag being set based on -march and the current semantics of -march for bother clang and GCC. But I agree this is all a bit fuzzy and underspecified, so adding a new tag is probably the right approach.

The "minimal" set has its merits, but I'd vote to keep the exact user specified -march as well (and a superset when combining object files with disparate such entries in  an executable/dso). This could be used to make runtime decisions. See [1]
[1] https://sourceware.org/pipermail/libc-alpha/2023-January/144578.html

-march is the minimal set, without further application-specific knowledge about the conditions under which functions get called (there's no way for a compiler or linker to know that functions compiled in an -march=rv32if file are only ever called when F's existence has already been dynamically checked). For anything else you should be using __attribute__((__target__(...))) or .option arch to selectively and locally change the ISA in use, which does not end up in the ELF attributes (as for those you're expected to have checked you can use the extensions enabled).

Indeed I'm only referring to build time info available to compiler/linker and nothing about execution env itself.
And I would expect RV_ATTR_TAG_arch to capture that as is.
Kito's msg in above thread seemed to indicate that glibc with V based ifuncs won't have 'V' in attributes to convey a "minimal" execution env which is a problem for what I'm envisioning trying to the attr for.

V not showing up for V IFUNCs is a feature/deliberate design decision. In fact, this lets you have conflicting extensions in use by different IFUNCs, which is a feature that needs to be supported (for example, it lets you have F and Zfinx versions of floating-point library routines).


Optimize refcounting in memoryviewslices

Closes https://github.com/cython/cython/issues/5507
Defines a set of rules where it's safe to make the temp a borrowed reference when doing memoryview slicing. In that case we can optimize for the reasonably likely case that assignment needs no reference counting at all.
The two big things that this optimizes are:
for i in range(memview.shape[0]):
  subview = memview[i, :]  # about 20x faster

In this case only the first assignment is reference counted.
And
for i in range(memview.shape[0]):
  some_expression(memview[i, :])

where the whole thing is borrowed.

Needs some thought about how to test this I think.  Regexes of the generated code are always painful but I'm not sure I can think of anything much better.


Security issue in loadsh  4.17.4

Could you guys make a update for the loadsh package? How can I update my package-lock.json?

Updated in most recent build.


test: make tabbed dashboard a little more complex

SUMMARY
Update the test dashboard "Tabbed dashboard" to have more nested tabs so we can test more complex use cases.
Also updated the update_slice_ids function to use dict instead of sorted lists so that slices in position_json can be matched more correctly.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before

After

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@john-bodley I added an integration test for superset load_examples command. Can you take a look?


fix(dates) - fix date validation minDate and maxDate

1. Description
Add validation for minDate and maxDate for inputType date
Issue tracker (Private): https://linear.app/remote/issue/RMT-542

2. How to test this
I've created an internal MR where you can test that everything is working

I'll review this by EOD.


Migration: Document dialog

Document the ng-bootstrap notification overlay component (https://design-system.post.ch/#/ng-bootstrap-samples/notification-overlay) in storybook.
Since this is an Angular component, it can't be displayed in storybook. Use the Intranet Header documentation as a reference https://next.design-system.post.ch/?path=/docs/components-intranet-header-getting-started--docs for how to document with code only and link to the Demo App archive for a live demo.
### Tasks
- [ ] https://github.com/swisspost/design-system/issues/2469
- [ ] Migrate notification overlay documentation

Add Content to the new docs page:

[ ] Name
[ ] Link to ng-bootstrap docs
[ ] Link to archived demo docs
[ ] Installation guide (css imports)
[ ] Post specific informations/examples


Thing I want to know: What I am supposed to with Node.js

Please describe what you want to know in less than 255 characters.

Something happened

Something happened again


Adobe Creative Cloud Package

Not sure how much leverage you have at MS. But it would be nice to see MS and Adobe work together for Mac Admins to deploy their Adobe Creative Cloud Package.   I have been unsuccessful getting it to work 100% correctly.  I did manage to get it to work by putting their package in another package, signing it with Apple Developer ID, wrapping in Intune and uploading to Intune.  It runs and installs fine, but reports back to intune that it didn't know the status.
This lead me to use one of your scripts and purpose it for the Adobe CC package, I can take the Adobe CC package and downloaded it.  I have to put it on Amazon S3 which doesn't seem to like pkg files so I have to zip it first and then upload to S3 and then in your script I use the zip function to unzip it and changed one line in there to use installer to install the package after it's been unzipped and testing it twice now it has worked fine.  I'm fine now that I have a solution, but not sure what others are doing.  I have asked on slack and get no response.  Seen posts on web that it just doesn't work and really no solution except to wrap it in another package and go that route, but for me it didn't report back correctly.
But seems to be a bunch of hoops to get it to work.  Be nice to simply download the package, wrap it for Intune and upload it to Intune.

At this point I can't even get Creative Cloud to install correctly through Intune without an "Unable to reach Adobe servers" error message.
My script works fine when ran via Terminal, but then it doesn't install the program correctly yet doesn't log any errors when the exact same script is ran through Intune's Shell Scripts on the same iMac. Getting annoying that this is the one program we can't deploy, Adobe just can't make working deployment tools it seems.

I have had issues with installing Adobe via Sh script because the built in zip utility was crashing, once i got around that I found that Adobe don't sign their PKG unmanaged installers. So i'm working on signing them installers with our trusted root cert that i deploy anyway and seeing if it will install it then. Bit of a mess but i guess some parts at least make sense.


ImagesDetectionPrediction._images_prediction_lst is not List. It is Generator.

Describe the bug
Just as in the title: ImagesDetectionPrediction._images_prediction_lst is not List. It is Generator.
To Reproduce
>>> import torch
>>> from super_gradients.training import models

>>> DEVICE = 'cuda' if torch.cuda.is_available() else "CPU"
>>> VERSION = 'yolo_nas_l'
>>> model = models.get(VERSION, pretrained_weights="coco").to(DEVICE)

>>> SOURCE_IMAGE_PATH = f"{HOME}/data/dog-3.jpeg"
>>> result = model.predict(SOURCE_IMAGE_PATH, conf=0.25)
>>> type(result._images_prediction_lst)
generator

Expected behavior
ImagesDetectionPrediction._images_prediction_lst should be a list, not a generator.
Additional context
That leads to many weird/unwanted interactions:

Can't access prediction by index - ImagesPredictions - parent class for ImagesDetectionPrediction provide __getitem__ implementation but because _images_prediction_lst is a generator it does not work.

>>> result = model.predict(SOURCE_IMAGE_PATH, conf=0.25)
>>> result[0]

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
[<ipython-input-34-2c43f6f8ed53>](https://localhost:8080/#) in <cell line: 1>()
----> 1 result[0]

[/usr/local/lib/python3.10/dist-packages/super_gradients/training/models/prediction_results.py](https://localhost:8080/#) in __getitem__(self, index)
    122
    123     def __getitem__(self, index: int) -> ImagePrediction:
--> 124         return self._images_prediction_lst[index]
    125
    126     def __iter__(self) -> Iterator[ImagePrediction]:

TypeError: 'generator' object is not subscriptable

Can't get predictions count - ImagesPredictions - parent class for ImagesDetectionPrediction provide __len__ implementation but because _images_prediction_lst is a generator it does not work.

>>> result = model.predict(SOURCE_IMAGE_PATH, conf=0.25)
>>> len(result)

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
[<ipython-input-35-69290ace8698>](https://localhost:8080/#) in <cell line: 1>()
----> 1 len(result)

[/usr/local/lib/python3.10/dist-packages/super_gradients/training/models/prediction_results.py](https://localhost:8080/#) in __len__(self)
    119
    120     def __len__(self) -> int:
--> 121         return len(self._images_prediction_lst)
    122
    123     def __getitem__(self, index: int) -> ImagePrediction:

TypeError: object of type 'generator' has no len()

After you call show you loose your predictions

>>> result = model.predict(SOURCE_IMAGE_PATH, conf=0.25)
>>> result.show()
>>> list(result)
[]

Hi @SkalskiP ,
We fixed it in this PR, which will be available in the next release.
The nightly version can be installed via pip install -U git+https://github.com/Deci-AI/super-gradients@master.
If you don't want to change for nightly version, you can always cast it as a list (not tested but should work):
result = model.predict(SOURCE_IMAGE_PATH, conf=0.25)
result._images_prediction_lst = list(result._images_prediction_lst)

Hoping this helps

Yup that's what I did result = list(model.predict(image, conf=0.35))[0] :)

HI @SkalskiP , what other parameters rather than iou are available to customize for inference? I can't find it in the docs


Add glances sensors always

Description:
This seems to be wrong to start glances sensor only when there's host available. This leads to a system being not deterministic as we cannot auto-discover glances later when it shows.
Checklist:
If user exposed functionality or configuration variables are added/changed:

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

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

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Hi @ayufan,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

If we go down that path then more changes are needed:

The log level needs to be adjusted.
available() should be introduced. Otherwise it's hard to tell for the users why there are no values.

Any plans to go on with this PR?

This PR seems to have gone stale. Closing it. You can reopen it when you're ready to finish it.


Is there any one could provide the obj file which be rendered in clock_rendered.zip

@Caenorst
Could you put a link to the original clock.obj?
I wanna re-render it with other software to compare them.
clock_rendered.zip could be downloaded at here.

Hi @FavorMylikes , thank you for your interest in Kaolin, here is the dataset we used https://graphics.pixar.com/usd/release/dl_kitchen_set.html

@Caenorst
Thank you for responding. But this data is usd format, I'm trying to find a way to convert it to an obj file, do you have any suggestions?

We do not offer obj exporter, what software are you using? The tutorial generate an USD checkpoint for you, you can do the comparison in Omniverse

@Caenorst
Due to the hardware requirement of kaolin, I can not run it on my computer with only one 1060ti GPU.
I just found a way to load the .usd file on Blender and convert it to a file with obj format.
But I still can not understand what's the meaning of the metadata file which in rendered_clock.zip.
It looks like a 4x4 matrix, but why the translation vector is the same [0,0,0], whether it's a camera or an object?
Is there any documentation that could give more explanation? I have already read the doc on Kaolin Library Documentation

Hi @FavorMylikes , you can find how we are using the metadata in our loader: https://github.com/NVIDIAGameWorks/kaolin/blob/master/kaolin/io/render.py#L106-L125


Create button for navigating to user's current geolocation

Probably practical "on the field".

See https://github.com/axelpale/tresdb/issues/41 for implementation details.

Postpone to another milestone because the low priority.

Graphics: https://maps.gstatic.com/tactile/mylocation/mylocation-sprite-2x.png
Styles & implementation: https://stackoverflow.com/a/34609371/638546

Implemented in https://github.com/axelpale/tresdb/commit/8af62558c6f52bc59a65f98a807669f5b1528a91


The "--name" flag is deprecated and broke my CI build

When I use BitBucket Pipeline as our CI/CD tool, I found that I can't deploy anymore.
now --name $NOW_PROJECT --scope $NOW_TEAM --token $NOW_TOKEN --regions sin1
Now CLI 17.0.1
The "--name" flag is deprecated (https://zeit.ink/1B)
? Set up and deploy “/opt/atlassian/pipelines/agent/build”? [Y/n]

Is there any workaround here?

I've got my answer here: https://github.com/zeit/now/pull/3690#issuecomment-582954173