yaml tranformer fails on a certain case where the file ends with a blank line

This happens with the pre-v1-launch branch, not reproducible with the master branch.
When a YAML file ends with a block style list of flow style maps followed by a blank line, scanning fails with "list index out of range" at line=lines[item['__line__'] - 1] because __line__ is n but the lines list has only n-1 items, no element for the final blank line.
Example:
foo:
  - { bar: 'baz' }

When it fails, __line__ is 3, but lines has only two items: ['foo:', '   - { bar: "baz" }']:
list index out of range
  File "/Users/gpflaum/ws/detect-secrets-pre-v1-launch/detect_secrets/transformers/yaml.py", line 193, in __iter__
    line=lines[item['__line__'] - 1],
  File "/Users/gpflaum/ws/detect-secrets-pre-v1-launch/detect_secrets/transformers/yaml.py", line 33, in parse_file
    items = sorted(YAMLFileParser(file), key=lambda x: x.line_number)
  File "/Users/gpflaum/ws/detect-secrets-pre-v1-launch/detect_secrets/core/scan.py", line 130, in _get_transformed_file
    return transformer.parse_file(file)
  File "/Users/gpflaum/ws/detect-secrets-pre-v1-launch/detect_secrets/core/scan.py", line 50, in scan_file
    lines = _get_transformed_file(f)
  File "/Users/gpflaum/ws/detect-secrets-pre-v1-launch/detect_secrets/core/secrets_collection.py", line 42, in scan_file
    for secret in scan.scan_file(filename):
  File "/Users/gpflaum/ws/detect-secrets-pre-v1-launch/detect_secrets/core/baseline.py", line 30, in create
    secrets.scan_file(filename)
  File "/Users/gpflaum/ws/detect-secrets-pre-v1-launch/detect_secrets/main.py", line 47, in handle_scan_action
    secrets = baseline.create(*args.path, should_scan_all_files=args.all_files)
  File "/Users/gpflaum/ws/detect-secrets-pre-v1-launch/detect_secrets/main.py", line 26, in main
    handle_scan_action(args)
  File "/Users/gpflaum/ws/detect-secrets-pre-v1-launch/detect_secrets/__main__.py", line 7, in <module>
    sys.exit(main())

Parsing is successful when the file doesn't end with a blank line:
foo:
  - { bar: 'baz' }]

Here are several cases that don't fail when the file ends with a blank line.
Block style map of block style list:
foo:
  -
    bar: baz

Flow style map that isn't in a list:
foo: { bar: 'baz' }

Block style list of flow style lists:
foo:
  - [ "bar", "baz" ]

Flow style list of flow style maps:
foo: [ { bar: 'baz' } ]

oof. Nice find. Thanks for providing great test cases to check if implemented logic is accurate.
Let me see what I can do.

Can reproduce it with this:
$ python -i
Python 3.8.0 (default, May  7 2020, 02:49:39)
[GCC 8.3.1 20191121 (Red Hat 8.3.1-5)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from detect_secrets.transformers.yaml import YAMLFileParser
>>> with open('blah.yaml') as f:
...     items = sorted(YAMLFileParser(f), key=lambda x: x.line_number)
...
Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
  File "/data/ws/detect-secrets/detect_secrets/transformers/yaml.py", line 193, in __iter__
    line=lines[item['__line__'] - 1],
IndexError: list index out of range

Oh, of course 🤦 . The __iter__ method isn't called until we sort it.

I took a quick peek at this -- I think this is going to be a lot harder to address than initially expected.
Why it Fails on Master
I was initially very surprised to see it failing on master, given that the core YAML parsing logic is mostly unchanged. I tested this side by side with a json dump, and confirmed my hypothesis -- they are near identical (at least, for the points that matter).

master branch

{
  "foo": [
    {
      "bar": {
        "__value__": "baz",
        "__line__": 3,
        "__is_binary__": false,
        "__original_key__": "bar"
      }
    }
  ]
}

v1 branch

{
  "foo": [
    {
      "bar": {
        "__value__": "baz",
        "__line__": 3,
        "__original_key__": "bar"
      }
    }
  ]
}

file content

foo:
    - { bar: 'baz' }
# this is a new line

It turns out that the v1 branch attempts to output the line itself, so that it can be handled in the filters logic (rather than the master branch's approach to let the YAML parser indicate which lines should be excluded), and as a result, it raises the IndexError since the newline is stripped from YAMLFileParser.content.
But the problem lies even deeper than this.
Incorrect Line Numbers
As I alluded to before, my local testing seem to suggest that YAML file parsing does not provide accurate line numbers, as previously designed. This bug is an artifact of this.
We can see this by extending the number of new lines within the file content itself, and checking the JSON output of YAMLFileParser. Apparently, it looks like within the YAMLFileParser._compose_node_shim function, the nested dictionary is tagged with the line number corresponding to the number of lines in the file itself!
Bizarre. But we must go deeper.
YAML Versioning Issue?
This YAMLFileParser operates on the assumption that the yaml loader knows the proper line number when parsing the file. It's debatable whether it has worked in the past (for this edge case specifically), but it certainly doesn't work now. The incorrect line numbers are obtained from the upstream's data source, so if we wanted to fix this, we need to read more core YAML parsing code, and figure out what has changed.
I'm currently able to reproduce this on pyyaml==5.1.2
Proposed Solution
I'm going to wait for my pending v1 branches to be merged in, before taking another look at this. My current thoughts are:

pin the YAML version (if an older version works better)
modify the parsing code to extract the proper line numbers based on upstream library

@domanchi we've also hit several .yaml files that cause the secrets scanner to crash using v1.0.3 (see below for the traceback). Although it does not seem to be related to ending with a blank line (adding or removing it makes no difference), it does seem related to your analysis above. I was wondering would it be helpful if I provided some of these files (after I strip it of some specific) for debugging purposes? Also happy to open another issue for it instead.
Traceback (most recent call last):
  File "/usr/local/bin/detect-secrets", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.9/site-packages/detect_secrets/main.py", line 30, in main
    handle_scan_action(args)
  File "/usr/local/lib/python3.9/site-packages/detect_secrets/main.py", line 66, in handle_scan_action
    secrets = baseline.create(*args.path, should_scan_all_files=args.all_files)
  File "/usr/local/lib/python3.9/site-packages/detect_secrets/core/baseline.py", line 26, in create
    secrets.scan_file(filename)
  File "/usr/local/lib/python3.9/site-packages/detect_secrets/core/secrets_collection.py", line 42, in scan_file
    for secret in scan.scan_file(filename):
  File "/usr/local/lib/python3.9/site-packages/detect_secrets/core/scan.py", line 141, in scan_file
    for lines in _get_lines_from_file(filename):
  File "/usr/local/lib/python3.9/site-packages/detect_secrets/core/scan.py", line 245, in _get_lines_from_file
    lines = get_transformed_file(cast(NamedIO, f))
  File "/usr/local/lib/python3.9/site-packages/detect_secrets/transformers/__init__.py", line 31, in get_transformed_file
    return transformer.parse_file(file)
  File "/usr/local/lib/python3.9/site-packages/detect_secrets/transformers/yaml.py", line 34, in parse_file
    items = sorted(YAMLFileParser(file), key=lambda x: x.line_number)
  File "/usr/local/lib/python3.9/site-packages/detect_secrets/transformers/yaml.py", line 194, in __iter__
    line=lines[item['__line__'] - 1],
IndexError: list index out of range

Yes, please do. I've hit some of these myself, but have been unable to reproduce them on the master branch (despite no relevant changes to this processing logic). My hypothesis is that it may have something to do with the PyYAML version. What version are you running with?

Yes, please do. I've hit some of these myself, but have been unable to reproduce them on the master branch (despite no relevant changes to this processing logic). My hypothesis is that it may have something to do with the PyYAML version. What version are you running with?

Sorry for the late reply. I'm using PyYAML 5.4.1. The following test cases are made using 1.1.0.
We used a slightly modified version of a default Verdaccio configuration file here, but the default one as presented there also fails on my machine with:
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/multiprocessing/pool.py", line 125, in worker
    result = (True, func(*args, **kwds))
  File "/home/picnic/.venv/lib/python3.9/site-packages/detect_secrets/core/secrets_collection.py", line 294, in _scan_file_and_serialize
    return list(scan.scan_file(filename))
  File "/home/picnic/.venv/lib/python3.9/site-packages/detect_secrets/core/scan.py", line 150, in scan_file
    for lines in _get_lines_from_file(filename):
  File "/home/picnic/.venv/lib/python3.9/site-packages/detect_secrets/core/scan.py", line 254, in _get_lines_from_file
    lines = get_transformed_file(cast(NamedIO, f))
  File "/home/picnic/.venv/lib/python3.9/site-packages/detect_secrets/transformers/__init__.py", line 31, in get_transformed_file
    return transformer.parse_file(file)
  File "/home/picnic/.venv/lib/python3.9/site-packages/detect_secrets/transformers/yaml.py", line 34, in parse_file
    items = sorted(YAMLFileParser(file), key=lambda x: x.line_number)
  File "/home/picnic/.venv/lib/python3.9/site-packages/detect_secrets/transformers/yaml.py", line 201, in __iter__
    line=lines[item['__line__'] - 1],
IndexError: list index out of range

Another one that fails similarly is:
postgresql_restarted_state: state
postgresql_databases:
  - name: some_database
postgresql_global_config_options:
  - option: listen_addresses
    value: "addresses"
postgresql_hba_entries:
  - { type: type, database: database, user: user, address: "<IP_ADDRESS>", auth_method: method }

I had another but that seems to be fixed as of 1.1.0.

@domanchi , i also face the same issue. Is there any ETA when this fix will be released?

Hi all,
Realized I left this thread in an unfinished state.  As of mid-April, I lost write-access to this repository which inadvertently halted all development for this project.
We're currently trying to figure out what's the future of this project to migrate it into a platform where development can continue again, but until then, I'd suggest that if you are having the same issue, you can patch your library yourself with the PR I referenced above.


Extended Task Docs: Take 2

Second take on #70. This PR includes only the Extended Task docs and updates the py-shiny submodule to the v0.7.0 tag.

Deploy preview looks good, I'm going to merge now


Application->register() BC break

With https://github.com/laravel/framework/pull/25028 our CI tests are failing on PHPstan since the function signature has changed. Its not a major thing but I'm wondering how we as a supporting library can cleanly support multiple Laravel versions with this change?

Depends on your use case, if you follow Semantic Versioning or if you follow the Laravel Versioning which is parading.minor.patch or if you follow something else?
I personally follow Semantic Versioning, therefore, when a new minor version of Laravel is released, i do a new major on my library.
This gives me flexibility to support old versions of Laravel but avoid these nasty breaking changes.

To clarify; yes, it's an obvious breaking change. Most changes to method signatures are. However, it's targeting an non-released Laravel version (the master branch which is currently the future 5.8 release) and is considered okay. We allow breaking changes between major releases (as in between 5.7 and 5.8).
The versioning scheme in use helps communicate how breaking changes are handled, not determining if something is a breaking change or not.
You probably need to have one code-base per Laravel release. This is often (always?) done by having one package branch per Laravel release. So your package' 5.8 branch (if I may suggest the name...) would only support 5.8. You may be able to have one branch for many Laravel releases, but that could require you to have checks for which Laravel version is in use.
Your composer.json file should always explicitly Laravel releases for peace of mind. Don't include version ranges that also matches non-released Laravel code, you have no idea if your current code will match Laravel 5.8 or not. When people ask about this I tell them that there has not been an official decision on if Laravel 5.8 will support VR or not, and you cannot declare that you support 5.8 before we're sure what is in the release.
A good example is orchestra/testbench which has one branch per Laravel version. I don't know about the decision behind it, but I presume it's based on the fact that they do some things that affect internal Laravel operations which may change between releases.
Ref: https://github.com/orchestral/testbench#version-compatibility

Also see here: https://laravel.com/docs/5.4/releases#versioning-scheme


Support set *_drbg reseed interval before seed

Description
Fixes ARMmbed/mbedtls#2927
Summary of change
mbedtls_hmac_drbg_seed() and mbedtls_ctr_drbg_seed() were setting the entropy context reseed_interval to the default value of 10 000 even when set_reseed_interval() had been called prior to seed(). The documentation did not describe the API behaving this way, and it doesn't make sense that seed() would remove any prior preference for reseed_interval so this behavior has been fixed. Now, the value set by set_reseed_interval() will persist through after a call to seed().
Impact of changes
This change would break any application that

set the reseed_interval and expected it to be reset to the default value once they called seed()
set the reseed_interval and was unknowingly using the default value for the lifetime of the DRBG object

The first situation could be dangerous if the set interval was very high and the PRNG was never reseeded. It is an unlikely scenario however because a user that understood the prior behavior would probably not design their application in this way anyways.
In the second situation, this change could expose a vulnerability in the user's application, so this could provide them with a net benefit.
Migration actions required
None
Documentation

Comments have been updated.
Some formatting was done to align comment indentation.

Pull request type
[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results
[] No Tests required for this change (E.g docs only update)
[] Covered by existing mbed-os tests (Greentea or Unittest)
[x] Tests / results supplied as part of this PR

Modifies *_drbg_entropy_usage() so that set_reseed_interval() is called before seed(). This would fail before this patch.

Hi @gacquroff . Thanks for your contribution.
It looks like this patch breaks our doxygen generation:
******************************************************************

* check_doxygen_warnings: Check: doxygen warnings (builds the documentation)

* Wed Jun  3 16:37:05 UTC 2020

******************************************************************

/var/lib/build/include/mbedtls/ctr_drbg.h:306: warning: Invalid list item found

FAIL

^^^^check_doxygen_warnings: Check: doxygen warnings (builds the documentation): tests/scripts/doxygen.sh -> 1^^^^

Could you please fix this before we review? Regards, Dan.

For some reason (network glitch?) the Travis log wasn't linked automatically.

Travis CI build passed, but I'm not sure about the PR-3393-head TLS Testing failure. Should I be able to see the log from that?

Hi @gacquroff, the PR-3393-head TLS Testing failure was just a CI glitch (a repo cloning failed) thus from the CI point of view it is all good now. Thanks for reverting the comment changes.

Hi @ronald-cron-arm, no problem. Let me know if I need to fix any other CI bugs.

FreeBSD failed again in a re-run, but it isn't the fault of this PR. We'll need a clean run on FreeBSD before merging, but I don't expect any problems.

@ronald-cron-arm Are those test failures another CI glitch? I'm happy to clean up anything else here.

The CI failed due to this having the "needs: work" label. I've removed and re-triggered now.

Please don't change the base of a pull request once it has been reviewed, unless there's a merge conflict. That makes it hard to re-review without reviewing from scratch. Can you please rebase back on top of 662deb38d61bb1fc6392c55a5134d1bd1a116118?

Rebased onto 662deb3. @gilles-peskine-arm

See backports:
2.16: #3938
2.7: #3937


Labels in pie charts

Hi,
Is it possible to write labels outside the pies with percentages and values tied to the pie wih line or arrow ?
Thks

same question here... could you solve it?


Auth Next: Support enforced auth and real auth in tests

Independent of #875 which is discussing a convenient test specific interface for working with auth, we need to allow support for using auth in its rawest form in the SDK tests, where enforcing is enabled and the same tools are available as will be available outside of tests.
While it's critical that we provide a simple interface for mocking, stubbing, or testing against auth without actually performing auth (the topic of #875), we also need to provide a way for developer to play with custom accounts in enforcing mode, where the actual contracts execute, and where developers can explore much like a playground the full scope of how auth works on a real network.
A goal of the test framework in the SDK is that to the largest extent possible it operates just like a contract will experience on the real network. In many ways it is a playground that lets a user discover and learn about Soroban, and auth is a big component of that.
Adding this capability should interact very little with whatever we plan to do in #875 because running in enforcing mode should just be a matter of not enabling the mocks/stubs/conveniences that #875 provides.

While I'm not strictly opposed to this in concept, there is a few things to keep in mind:

the enforcing mode requires passing the ContractAuth payloads to the host. these payloads have to have the call trees of require_auth
it also requires the correct accounting of nonces (though this might be simplified with temp storage nonces, https://github.com/stellar/rs-soroban-env/issues/655
it requires the ledger state for the account, classic or custom, depending on what we want to cover here. the ledger state for the accounts would also result in additional ledger state required for SAC
it requires the proper signatures

Keeping all these requirements in mind, I think the best way to cover this is to do that via sending transactions to the core, i.e. that would be an integration test (as in 'integration between dapp and stellar', not 'integration between contracts'). If we strive to emulate the real behavior and use the state external to the control invocation (such as the auth payload/sigantures/nonces), we should probably also take the footprints and resource consumption into account as well. This way the developers will be able to actually test the wallet interactions, auth payload building, footprint building etc.
I'm not sure about building this into the SDK directly though. It would still need to emulate a big chunk of the logic (unless we want the users to write boilerplate for the sake of boilerplate), while not providing any additional coverage. E.g. if we have a custom, SDK-implemented builder of the auth payloads, then it will be only usable by the SDK tests for the SDK tests. It doesn't help any real use case (as in reality XDR will have to be used) and it doesn't cover anything (because auth payloads are managed outside of the SDK).


Create Separate Hand Pose Recognition/Animation Service

Describe the problem
Gesture recognition and animation is currently tied up within several classes and controllers. This issue tracks bringing out that logic to a more unified system which handles gesture recogntion/animation.

Something which is still needed for v3, though we've made it so some gestures such as pinching will be driven from the system itself.


Implement POM backend

Here is a description of the new pom backend...
Intro:
Many java projects contain "pom" files. They are small xml metadata files that often contain a license field. Reference here: https://maven.apache.org/pom.html#Licenses
We want to look for these files, parse them, and when they have license information, return that so that it can be aggregated with the data from the other backends.
Design:
Please think about any design considerations you might have when working on this code. It is important to think about what you're going to build before you code it. Always do it this way, as it helps avoid re-writing things you could have solved earlier.
Code:
You'll probably want to implement a Pom struct. This will be a backend in the backend/ folder. It will probably look similar to the spdx.go backend in many ways. You might want to use that as a template.
The Pom struct will need to be included in lib/main.go where the other backends are pulled in.
You should add an example file in examples/.pom that shows how this works.
Testing:
If there is a reasonable type of test to write, please describe what kind of test you would write. Describe the details here before implementing them.
Questions:
Any questions you have please add them to this issue. When you have something minimally viable, please send a pull request to this repo and link it in this issue. We will track your progress publicly here.
Timeline:
A hacker experienced with golang and also with the yesiscan code base could probably implement this within 2 hours. An intermediate golang programmer could probably implement this within a day. Someone with some past experience coding but otherwise a beginner should be able to implement this within 2-3 days. If you feel you are blocked for more than 2-3 hours on any one aspect of this, please reach out and ask for help to avoid wasting your time! We're here to help and guide you!
Challenges:
The trickiest part here is finding out what needs to get written in the ScanData function that you will be implementing. Looking at the existing spdx example will guide you a lot. The other challenge will be writing an xml parser to pull out the license information.
Hints:
Use the spdx.go file as an example. Copy+paste it to pom.go and change all the relevant parts. Find a small example .pom file that you can use to test your code.
Confidentiality:
Please remember that this is all public so don't include any private information that your employer or team mates wouldn't want shared.
Thank you!

I am working on this.

Since I am not using a scanner I was wondering if I can use "pom scanner error" as an error message or should I say something else or is the scanner mentioned in the error message not talking about the scanner variable?

You should use the relevant error message. Either with fmt.Errorf("some message") or errwrap.Wrapf(parent_error, "some new message"). There is also errwrap.Append if you want to return multiple errors, but this is rare.

You should add an example file in examples/.pom that shows how this works.

Is there any specific place where I am not supposed to take the pom.xml files from? Or can they be from any where I find them?

Is there any specific place where I am not supposed to take the pom.xml files from? Or can they be from any where I find them?

Up to you! Do what works best. Think of it this way:
In the open source world, pretend that it is entirely your idea for this patch. I'm not your manager requesting it. You are out there on your own and independent and your job is to propose something and convince me that your code and idea and design make sense!
Let's see what you come up with!

Can I add the commands for POM in cmd/main.go? So I can try it out by running it on the command line.

This is done, we can close! \o/


Wezterm get flag as a virus

When downloading Wezterm, it gets flagged as a virus.

Guess this relates more to wezterm than to scoop itself: wez/wezterm#5746.
Duplicates e.g. #13033.

Thanks. My apology for the duplication.


Adjust Training Process

Describe the enhancement
Adjust the parameters of the training process like the epochs and the learning rate to ensure that the validation loss decreases more and to improve the convergence speed.

git fetch origin
git checkout 15-adjust-training-process


Print system only if provided in the CLI

Good point. What about printing default, native or something on those lines instead of None?
A better way wold be to read the system from the recipe, but probably a bit too convoluted for the purpose here.

Yes, the printed header is a summary of the command line arguments that were passed, not of the internal configuration of the recipe.
none or default are both valid choices.

I changed it to default, but please feel free to just close this PR if you prefer to keep None!


How to modify the size/style of points labels

Is there a way to modify the apperance of each point label when these are clicked from the user? Should I ovveride onValueSelected method? I can't find any code example about this in the sample. Thanks in advance.

i have the same request,there is anyone can help?

hey, yeah, the save here, I can't find solution for this, can somebody help us?

So I have found how to change label color, size, typeface and how to remove background. But I couldn't find more...
LineChartData data = new LineChartData();
data.setValueLabelsTextColor(Color.WHITE)
data.isValueLabelBackgroundEnabled = false
data.valueLabelTextSize = 25
data.valueLabelTypeface = ResourcesCompat.getFont(context, R.font.monteserrat)


substrate not starting after compile

Is there an existing issue?

[X] I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

[X] This is not a support question.

Description of bug
root@blipp14:~/substrate-node-template# ./target/release/node-template --dev
2023-04-04 22:13:26 Substrate Node
2023-04-04 22:13:26 ✌  version 4.0.0-dev-700c3a186e5
2023-04-04 22:13:26 ❤  by Substrate DevHub https://github.com/substrate-developer-hub, 2017-2023
2023-04-04 22:13:26 📋 Chain specification: Development
2023-04-04 22:13:26 🏷  Node name: delicate-snakes-4871
2023-04-04 22:13:26 👤 Role: AUTHORITY
2023-04-04 22:13:26 💾 Database: RocksDb at /tmp/substrateC3GvHN/chains/dev/db/full
2023-04-04 22:13:26 ⛓  Native runtime: node-template-100 (node-template-1.tx1.au1)
Error: Service(Client(VersionInvalid("cannot deserialize module: UnknownOpcode(192)")))
2023-04-04 22:13:26 Cannot create a runtime error=Other("cannot deserialize module: UnknownOpcode(192)")
I keep getting this error on Ubuntu 20.04 and Ubuntu 22.04. I spent many days figure it out but no luck. Can you help?
Steps to reproduce
No response

duplicated to https://github.com/paritytech/substrate/issues/13636

Hi,
I saw that. But not clear how can I solve this problem?
From: Xiliang Chen @.>
Sent: Tuesday, April 4, 2023 6:40 PM
To: paritytech/substrate @.>
Cc: Anil Rana (Nokia) @.>; Author @.>
Subject: Re: [paritytech/substrate] substrate not starting after compile (Issue #13822)
duplicated to #13636https://github.com/paritytech/substrate/issues/13636
—
Reply to this email directly, view it on GitHubhttps://github.com/paritytech/substrate/issues/13822#issuecomment-1496687990, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFOUWQSWO54RYJS53BGKDN3W7SPLBANCNFSM6AAAAAAWTJQLSY.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Either downgrade your nightly compiler version or check out latest master that contains a fix.

this is how i solved it:
rustup install 1.68.0
rustup default 1.68.0
rustup toolchain install nightly-2023-01-30
rustup target add wasm32-unknown-unknown --toolchain nightly-2023-01-30
rustup override set nightly-2023-01-30


Fixed an exception when a column specified in Flatten is of UNION type.

What is the necessity of this update? What is updated?
There is insufficient null exception handling when the column specified in Flatten is of UNION type and does not contain a SPREAD type as a child.
Processing will not be possible if this correction is not made.
How did you do the test? (Not required for updating documents)
Improvements were confirmed through unit testing.

LGTM


Duplicate Newtonsoft dll

When you clone main unity greets you with an error for having multiple newtonsoft.json dll's. I threw out the one included in SpeckleConnector/Core and that fixed the error.
Multiple precompiled assemblies with the same name Newtonsoft.Json.dll included or the current platform. Only one assembly with the same name is allowed per platform. (Assets/Speckle Connector/Core/Newtonsoft.Json.dll)

ah, this was an issue with my fork not being up to date. Closing now.


need this checks for easier testing without all imports

helps with running correct tests dependent on imports available.

rerun tests

rerun tests

rerun tests


Nasty direct path to own types.

Is your feature request related to a problem? Please describe.

Examples of this can be seen here:

I would like to have the option to just use the class names (edited using Inspect):

I do have some worse examples like this one, which is a pretty complex type but this doesn't make it better:

Could look like this instead:

Very noisy, but to all the fault of my own now.
Describe the solution you'd like
Some option to only use the class names. The same way that when you list a class you get Option and not wumpy.interactions.commands.option.Option. If this could be individually applied as well that would allow someone to add it where necessary.
Describe alternatives you've considered
Some how overriding pytkdocs, I don't even know where to start and it seems fragile.
Additional context
This is something I personally need and wouldn't mind looking into it if I just get a pointer to appropriate files.

I've seen users patching mkdocstrings functions to better fit their needs. Maybe your feature request could be implemented the same way (as a workaround for now), by patching the rebuild_category_lists to post-process types so as to remove the leading parts. Draft regex-replace: re.sub(r"(\w+\.)*", "", annotation) (a simple split could work: annotation.rsplit(".", 1)[-1])
I think it could also be done with custom templates as well (same logic, different place).
We could probably add an option in pytkdocs itself, but I'm pushing back on features right now because I'm working on a better replacement, that parses the code instead of introspecting objects in memory.

This is likely solved by the new handler. The annotations are rendered just as they are written in the source code. Feedback appreciated!


agent: Add scaling event reporting

This is part 2 of 2; see #1078 for the ground work and neondatabase/cloud#15939 for the full context.
In short, this PR:

Adds a new package: pkg/agent/scalingevents
Adds new callbacks to core.State to allow it to report on scaling events changes in desired CU.

Notes for review:
I'd like to add minio-based S3 tests to this, but it seemed like it'd be non-trivial, particularly because scaling events actually require that there's scaling that happens — unlike the existing billing tests.
So I figured I'd open this for review in the meantime.
Also note: This PR builds on #1078 and must not be merged before it.

Remaining items for me, on this:

Add more thorough e2e tests
Test on staging


JENKINS-33574 fix unicode attachments

Looks like it only fails on windows which is a pain since I run osx and linux. Passes locally for me but can see it failed on the jenkins ci server when run on windows

This change is not fixing the bug, only making the test output more verbose so we can debug it. Still, I was able to find more information about this annoying bug.
It does fail even on my MacOS High Sierra but if I add "LANG=en_US.UTF-8 mvn package" and run it i does pass. Sounds like an issue with java or maven and we need to find a way to bypass it.
Can you try to run it with these vars?
export MAVEN_OPTS='-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn'
LANG= LC_CTYPE= mvn package

Maybe this would allow us to narrow down and find a way to patch pom.xml or Jenkinsfile to make it pass. As last resort we can annotate the test and make it skip run on Windows platform.

Yes that makes it fail for me

So LANG= is what it breaks it. I just pushed some changes (found on stackoverflow) that may bypass this issue. Lets wait for their results. I know that Windows has Unicode support but is very different than Unix and I suspect that we get the failure due to the console encoding and not due to the Java and/or filesystem limitations.
I worked as internationalization engineer for 4 years so I had to do a lot of work around Unicode in the past, but that was like 6+ years ago. So glad I do not have to deal with Windows anymore.

@davidvanlaatum Time to merge it! It did fix the build. And after this you should be able to make a new bug fix release.

done


How to get the JSON object response from FuelError object in failure response?

If user sends a bad request, Im sending json object {"status" : "fail"}, But from error object im unable to get the json object. Please help me.

can you share the code you are using?

The Response object has a data property which represents the response body. It can be decoded using fuel-jackson, fuel-gson or any parser library you want.
If I understood the issue correctly, the API returns status code 400 and a JSON object with the field status in the body. If that is the case, the code below should work.
data class ApiResponseBody(val status: String)

object ApiResponseDeserializer : ResponseDeserializable<ApiResponseBody> {
    override fun deserialize(bytes: ByteArray) =
        jacksonObjectMapper().readValue<ApiResponseBody>(bytes)
}

fun main(args: Array<String>) {
    val url = "http://your.api.com/"
    val (_, response, _) = Fuel.get(url).responseObject(ApiResponseDeserializer)

    val apiResponseBody = ApiResponseDeserializer.deserialize(response.data)
    println(apiResponseBody.status) // "fail"
    println(response.statusCode) // 400
}

Close for inactivity, feel free to reopen this if you have any further question.


Translated READMEs (meta-issue)

In https://github.com/Microsoft/TypeScript-React-Native-Starter/pull/35#issuecomment-378803272, @phwb asked about providing a translated README.md in Russian.
We're welcoming translations and any help with reviewing those translations to help users from around the world learn more easily. If you'd like to help provide translations, let us know here!

Yes, I will do it in the near future


metrics: killall: do not use the binary path in killall

If you have any path characters in the argument to killall
then it will only kill the processes actually using that
binary. Thus, if you have any stuck processes that are using
a different (or previous that has since been replaced) binary,
killall will not find/kill them.
Change the killall to use just the process/file name (with no
path), which means it will kill all processes of that name
(even if they were launched from a binary in a different path)
which may feel a little more 'dangerous', but as we only run
this in reasonably well defined and constrained systems, it
should be fine.
Fixes: #757
Signed-off-by: Graham whaley<EMAIL_ADDRESS>

swarm fail on 16.04 CI - kicking a rebuild...

lgtm

Updated and added a warning section to the README.
Thanks @MarioCarrilloA for the nudge
/cc @iphutch for the docs update
Hey @jodh-intel , I figured out how to make a nice indended WARNING section appear in markdown ;-)
Also, this:
Fixes: #234
as well now I believe

@grahamwhaley - love it I do! ;)

@klynnrif - if you are in a 'docs review' mood/mode maybe you could check this one for me :-)
btw, if you are doing docs reviews, maybe we need to add you to our 'docs review group' so that any ACKs you do on the PRs actually get noticed by pullapprove, and hence will unblock stuck docs PRs etc.
thx!

lgtm

Hi @rcaballeromx, could you please take a look to this?

@grahamwhaley  please rebase it

@devimc - rebased
@klynnrif - changes applied


fatal error C1083: Cannot open include file: 'cblas_mangling.h': No such file or directory

I didn't find this header file in openblas include dir.

I commented this line ,then okay.
//#include "cblas_mangling.h"

Which version are you building ? I believe this problem of the 0.2.19 release should be fixed in the current "develop" branch already (something to do with import of the netlib lapack 3.7.0 release without noticing that a filename was changed compared to 3.6.x)

When you go to 'code' tab of this github project you can download .zip file with current develop version.

Actually I am no longer sure if there was a fix for this as such - while cblas_mangling.h (or actually a precursor for it) is included in the netlib CBLAS, it should not be installed or required as the build system of OpenBLAS creates its own cblas.h that does not use it. If you encounter this error (while compiling what ?), it could be that the compiler picked up a different copy of cblas.h installed somewhere else on your system.

@wguo68, did you have the problematic "#include cblas_mangling.h" in your own code, or where ? I believe this is internal to the netlib version (their cblas.h includes it, but for instance it is not present in the ATLAS blas either) and should not appear in user code. If you found that include in a cblas.h somewhere on your system, it cannot have been the cblas.h that is installed by OpenBLAS


Added prism.scss

added prism.scss for imports

@sivankanat Please explain your motivation and the changes of this PR in more detail.
@mAAdhaTTah What do you think about this? SASS/SCSS was discussed in #1055 but I view it as unnecessary rn.

@sivankanat Please explain your motivation and the changes of this PR in more detail.
@mAAdhaTTah What do you think about this? SASS/SCSS was discussed in #1055 but I view it as unnecessary rn.

@RunDevelopment Yeah, I had a more involved idea that would allow us to ensure some consistency & reuse between the themes, but we definitely didn't decide on it.
@sivankanat If you're interested in pushing this, I'd be happy to discuss what the goals are and how we go about accomplishing them if you want to open an issue with more info. I'm going to close for now, but please feel free to pursue this if you have ideas for improving Prism!

@RunDevelopment Yeah, I had a more involved idea that would allow us to ensure some consistency & reuse between the themes, but we definitely didn't decide on it.
@sivankanat If you're interested in pushing this, I'd be happy to discuss what the goals are and how we go about accomplishing them if you want to open an issue with more info. I'm going to close for now, but please feel free to pursue this if you have ideas for improving Prism!

@mAAdhaTTah
i think postcss, sass option is required in themes
for more customization and simple integration in a npm install
is there any idea on this subject?

@mAAdhaTTah
i think postcss, sass option is required in themes
for more customization and simple integration in a npm install
is there any idea on this subject?

i think postcss, sass option is required in themes
for more customization and simple integration in a npm install

A consumer installing via npm install won't be using our build tools. If someone clones our repo, they can add whatever tools they want. Neither of these require us to change our implementation.

i think postcss, sass option is required in themes
for more customization and simple integration in a npm install

A consumer installing via npm install won't be using our build tools. If someone clones our repo, they can add whatever tools they want. Neither of these require us to change our implementation.

i think postcss, sass option is required in themes
for more customization and simple integration in a npm install

A consumer installing via npm install won't be using our build tools. If someone clones our repo, they can add whatever tools they want. Neither of these require us to change our implementation.

ok, thanks

i think postcss, sass option is required in themes
for more customization and simple integration in a npm install

A consumer installing via npm install won't be using our build tools. If someone clones our repo, they can add whatever tools they want. Neither of these require us to change our implementation.

ok, thanks


Fix updating v3 npm lockfiles

Fixes https://github.com/dependabot/dependabot-core/issues/6270.

I tried this on a real repo and it worked fine, except for hitting this npm issue: https://github.com/npm/cli/issues/2700. I think the new PRs are still in a much better place that without updating the lockfile at all, so good to go I think!

https://github.com/npm/cli/issues/5470 also seems related. In any case, the better lockfile seems the one that includes "name" fields, and that's what Dependabot is generating. Whatever it is, it seems like a package manager issue.

Merging since missing lockfile updates is worse than some potential flip-flop on lockfile format due to npm issues.


Lazy Chord loading on Key Type

Description
From what I understand, when you initialize a Key, all the chords are generated inside the init.
However, if you want to create all the available keys for a certain note, the performance is pretty bad.
Here is a piece of code that illustrates this concept:
let newKeys = Scale.allCases.map {
    Key(root: note, scale: $0)
}

This code creates an array of keys for all the scales of a given note.
Proposed Solution
I would suggest implementing lazy chord creation. This would allow users to request the chords for a specific key only when needed, instead of generating them automatically during initialization. I believe that generating chords during initialization is unnecessarily complex and pollutes the domain of the Key Object, in addition, it also impacts the performance.
/// All the traditional triads representable root, third, and fifth from each note in the key
public func primaryTriads() ->[Chord] {
    let table = ChordTable.shared
    var primaryTriads: [Chord] = []
    let allowablePrimaryTriads: [ChordType] = [.majorTriad, .minorTriad, .diminishedTriad, .augmentedTriad]

    for (_, chord) in table.chords where chord.noteClassSet.isSubset(of: noteSet.noteClassSet) {
        if allowablePrimaryTriads.contains(chord.type) {
            primaryTriads.append(Chord(chord.root, type: chord.type))
        }
    }

    let primaryTriadsStartingWithC = primaryTriads.sorted(by: { $0.root.letter < $1.root.letter })
    let rootPosition = primaryTriadsStartingWithC.firstIndex(where: { $0.root == root }) ?? 0
    return Array(primaryTriadsStartingWithC.rotatingLeft(positions: rootPosition))
}

/// All chords that fit in the key
public func chords() -> [Chord] {
    let table = ChordTable.shared
    var chords: [Chord] = []
    for (_, chord) in table.chords where chord.noteClassSet.isSubset(of: noteSet.noteClassSet) {
        chords.append(Chord(chord.root, type: chord.type))
    }
    return chords
}

We could also think about adding a static global cache, similar to Chordtable, that stores a key and all the corresponding chords globally for faster access.
Wdyt?

These sound like good solutions. Thank you for pushing on this.


feat: add WithDateTimeKind to builder

fixes #83
This lets devs globally set the DateTimeKind of generated dates to, for example, more easily accommodate UTC in integration tests.
If #84 is approved, I'll add this toggle to TimeOnly as well

👋 @nickdodd79 any thoughts on this or the other PR?

This PR is over 2 years old.  Is there any chance of this getting merged and release?  It's a huge pain point in our integration testing.

This project isn't actively maintained AFAIK.
Check out AutoBogus life support for a minimal fork I made with latest .NET updates.
There's also this fork by @soenneker with more substantial mods geared towards better perf


chore(deps): update common-dev-assets digest to 32f3749

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
9fd0942 -> 32f3749

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

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

GitHub release
v1.7.0

Your semantic-release bot :package::rocket:


System.AccessViolationException: 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt.'

Hi,
I'm using Google OR.Tools with .NET CORE 2.1. However I'm getting a
System.AccessViolationException: 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt.' Error.
I remember getting it before when I didn't set the environment to x64, however it is set to a x64 env.
The error seems to occur when I add a certain amount of of variables to the objective. A few variables doesn't seem to  cause the error, but when I add more it crashes (not at a specific number, sometimes it crashes sometimes it doesn't). But I don' think this is an out of memory exception?

Thanks!

I'm not exactly sure, but I think this issue was caused by re-use of an objective or constraint without reinitialising the solver.

Hi,
I was using the CBC_MIXED_INTEGER_PROGRAMMING.
I fixed the issue when I last commented, but I'm not sure what exactly went wrong.
Like I said in my previous post I think it had to do with re-using objectives or constraints, but I'm not sure. It was definitly an error on my behalf (since I was able to fix it), but the error message provided was a bit unclear.

Closing the issue as the problem is resolved.

I'm not exactly sure, but I think this issue was caused by re-use of an objective or constraint without reinitialising the solver.

I was calling the code from the txtboxTextChanced. So, i make a new metho y call it from the load.

I am facing same issue in my project, i don't know why it's coming but error gone when i re-start the ISS and pool, Do you have any idea what a cause ?

I am facing same issue in my project, i don't know why it's coming but error gone when i re-start the ISS and pool, Do you have any idea what a cause ?

In my case it was not a framework issue rather a SQLite one. I had created 2 indices for the same table (and same set of columns and collation) with different index names. Removing one of the indices resolved the error. Hope this helps!

Hi . i have this problem too in my project
and i'm trying to change like to this answer but it doesn't work
maby do you have other answers to this problem?
i have "SQL Server database file"
and the request to the database works good but when i call this from the UI so the problem jumps.


Images do not display in strapi (wrong img src)

I am using a public subdomain set up over traefik with letsencrypt certificates. So my minio API is located at s3.xxxxx.be over https.
Uploads from within strapi work fine and I can see the files together with the previews inside my minio bucket.
But somehow strapi wants to display these images as src = http://minio:9000/... instead of my configured endpoint(s3.xxxxx.be) and port(443) in the strapi plugins.

I got it working, seemed to be a config issue.


[GURPS] 2.22.0

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

Changes / Description

BUGFIX: Fixed bug where base sprint value was not calculating correctly for zero encumbrance.
ENHANCEMENT: Combat > Your Hit Locations tab. Added a checkbox to each armor layer. The checkbox indicates if the armor is "On" or "Off". Toggling the checkbox will update the armor summary.

Character Sheet Info Roll20 Internal Use only.


Use the latest & greatest SwiftPrometheus, and utilize Middleware

This is a pretty big diff and change in approach, so definitely open to feedback! 🎉
I'm a fan of plugging in Middleware (and didn't see discussion on reasons to avoid this pattern, but if there are happy to help document them!) and that enabled us to clean up a good chunk of code.
Note that we do lose host-level metrics as part of this, but we'll absolutely need to get rid of RuntimeTools/SwiftMetrics because of the conflict with the Logging module.

This looks like a sensible change to a Middleware-based approach. Are there plans for it to be reviewed/merged?

Thanks for the nudge! I think with 0.4.0 of SwiftPrometheus this should be ready for a review from maintainers 🎉

I only ask because I'm about to use it in a new project - thanks for your work 😀

@tonyarnold wanted to check in, were you having any trouble with this diff?

@Yasumoto no, I haven't! The setup for this branch is far simpler (and less intrusive) than the current release, so I'm 👍 on that.
I'd love to see this merged and tagged.
Segue: Can you recommend a service (or services) for actually collating and reviewing the metrics this spits out?

@tonyarnold If collating and reviewing == "View the metrics" then you'll want to setup Prometheus to scrape from the endpoint, then run a Grafana installation and set it up to query Prometheus as a data store.
This walkthrough looks right once you have both setup and are ready to hook them together.

Thank you, your advice is appreciated!

Thanks for the look!
@MrLotU I considered your great point about things like /posts/1, /posts/2 blowing up the cardinality of metrics, and backed that out so we're just tracking the top-level URL.
It's not ideal since we lose things like /blog/posts but I think for a default setup this is reasonable to catch the first pass.
As always, open to ideas!

Hey folks, I have been using this PR's branch locally for a bit in a Vapor 3.x project - I've updated today, and now I see:
SourcePackages/checkouts/SwiftPrometheus/Sources/Prometheus/Prometheus.swift:55:24: error: value of type 'ByteBuffer' has no member 'writeString'
                buffer.writeString("\n")
                ~~~~~~ ^~~~~~~~~~~

It looks like the change to the upstream URL of SwiftPrometheus may have caused this?
It changed from:
https://github.com/MrLotU/SwiftPrometheus.git with a version of 0.4.0-alpha.1
To:
https://github.com/Yasumoto/SwiftPrometheus.git with no version, but a branch of nio1

@tonyarnold So sorry for the trouble! What’s your Package.resolved look like for SwiftPrometheus and Swift NIO?
In theory that branch should be the same tag along with https://github.com/MrLotU/SwiftPrometheus/pull/17 rebased on top, but I must’ve accidentally included the wrong side. Very curious how I kept everything working locally after a rm .swiftpm despite this error..

@tonyarnold https://github.com/Yasumoto/SwiftPrometheus/commit/fe69dfa28f885360eb268ec8fa06c2243a845a26 should fix this up

No need to apologise - I know what “alpha” means 😉 I appreciate the hard work and time you’ve put into improving this library.

Status update: this PR is currently on hold and waiting for https://github.com/vapor/routing-kit/pull/80 and https://github.com/vapor/vapor/pull/2089


Add Pallas field

Add Pallas field
Description
This PR add the Pallas base field in order to later construct the Pallas curve. There is no issue associated to this PR, but it was requested in Lambdaworks.
Type of change
Please delete options that are not relevant.

[x] New feature

Checklist

[x] Unit tests added

Codecov Report
Attention: 17 lines in your changes are missing coverage. Please review.

Comparison is base (8677b06) 96.58% compared to head (1aca2cf) 96.12%.
Report is 8 commits behind head on main.

Files
Patch %
Lines

math/src/field/fields/pallas_field.rs
82.22%
16 Missing :warning:

math/src/field/fields/vesta_field.rs
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #690      +/-   ##
==========================================
- Coverage   96.58%   96.12%   -0.47%
==========================================
  Files         127      134       +7
  Lines       29329    29995     +666
==========================================
+ Hits        28328    28832     +504
- Misses       1001     1163     +162

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


When opening a new console, the cursor is not in the entry field

When I open a new console, the cursor is not put in the entry field. I have to click it to to start typing things. I am using jupyterlab master.

Confirming, just came here to open this very issue. Thanks @asmeurer for beating me to the punch :) Tagging for 0.90, it's a fairly up-front usability issue.

This is something that the new focus tracker will help resolve. We talked
about it a bit and decided to not implement it "the wrong way" in the
meantime since upgrading to the phosphor mono repo is imminent.
cc: @sccolbert
On Thu, 14 Jul 2016 at 17:59 Fernando Perez<EMAIL_ADDRESS>wrote:

Confirming, just came here to open this very issue. Thanks @asmeurer
https://github.com/asmeurer for beating me to the punch :) Tagging for
0.90, it's a fairly up-front usability issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jupyter/jupyterlab/issues/388#issuecomment-232816816,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJvKU-0k_WVmVR6onkVTellN7dzajD3ks5qVr9mgaJpZM4JM6T0
.

No worries, there's no rush. As long as we're tracking it :)

Fixed by #636.

Confirming fix, thx!!


Additional Features

Worked on this over a week ago.
Additional features include the following:

Line linking.
Selection Linking.
Multiple Selection linking.
Scroll to top selection by link.

This was written specifically to get line numbering and syntax highlighting working
with Fossil (an alternative to git). However, the changes should be generally useful
otherwise. Can work on the pull request further to make it further compatible as
needed.
For an example of how it works, go to https://code.amlegion.org/hljs_line_numbers
For a full commit history same link as above.
Ask questions and let me know if further work is needed to progress this.

Note:
Also fixes displaying "{1}" on empty lines for some languages
(though probably should have been fixed via the format function
instead of a quick hack elsewhere).

#7 is fixed with this as well.

@llmII do you still have an example around for this? The link current 404s. I took at look at the other projects hosted (in fossil) but it wasn't clear synax highlighting was available when viewing code (e.g. https://code.amlegion.org/jlogger/file?name=logging/log.lua&ci=tip ). Thanks!

@clach04 look at simplelog.lua. It has syntax highlighting and line numbers (per that link).
We are no longer using highlightjs-line-numbers for this as there's builtin ways to do this with fossil now and I'd have to create a new patch to regain compatibility with the pull request here that is now incompatible with upstream.
I'm happy to help in relation to the fossil/highlighting setup, though we'd need to establish a way to contact each other (maybe look at one of our projects, might list a way to contact me).
The reason you don't see highlighting with jlogger is because it's in the Janet programming language and I'd either have to tweak my hljs to pretend janet files are clojure files or find a syntax highlighter that exists for janet in hljs and I haven't found it necessary to do so at this point in time.

thanks for the speed response @llmII! My interest was more in highlightjs-line-numbers than Fossil.
I'll make time to play with this from your fork :)


"Cannot find module 'handlebars'" when running examples

Can't even run up a basic example.

Cloned this repo, cd into examples/basic
'npm install'
nodemon server.js
(after following output) manually installed handlebars, still same error

Output:
[nodemon] 2.0.2
[nodemon] to restart at any time, enter `rs`
[nodemon] watching dir(s): *.*
[nodemon] watching extensions: js,mjs,json
[nodemon] starting `node server.js`
internal/modules/cjs/loader.js:983
  throw err;
  ^

Error: Cannot find module 'handlebars'
Require stack:
- /home/access/code/web/node/express-handlebars/lib/express-handlebars.js
- /home/access/code/web/node/express-handlebars/index.js
- /home/access/code/web/node/express-handlebars/examples/advanced/server.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:980:15)
    at Function.Module._load (internal/modules/cjs/loader.js:862:27)
    at Module.require (internal/modules/cjs/loader.js:1040:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at Object.<anonymous> (/home/access/code/web/node/express-handlebars/lib/express-handlebars.js:12:18)
    at Module._compile (internal/modules/cjs/loader.js:1151:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1171:10)
    at Module.load (internal/modules/cjs/loader.js:1000:32)
    at Function.Module._load (internal/modules/cjs/loader.js:899:14)
    at Module.require (internal/modules/cjs/loader.js:1040:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/home/access/code/web/node/express-handlebars/lib/express-handlebars.js',
    '/home/access/code/web/node/express-handlebars/index.js',
    '/home/access/code/web/node/express-handlebars/examples/advanced/server.js'
  ]
}
[nodemon] app crashed - waiting for file changes before starting...

please disregard


UTM not able to reboot Ubuntu 20.04 and 22.04

Good afternoon, I'm a university student and I have to work with Ubuntu for an exam. I encountered a strange issue: I opened UTM and start Ubuntu and it didn't work (I don't remember the error). I thought that I did something wrong so I tried to reinstall Ubuntu Server to have Ubuntu Desktop with the commands sudo apt install tasksel and sudo tasksel install ubuntu-desktop   but I can't because of this error. Can someone helped me? I tried also to uninstall and reinstall UTM, but there is always the same problem.

P.s. The error is also with command sudo apt update

Configuration

UTM Version: 3.2.4
OS Version: macOS Monterey 12.4
Intel or Apple Silicon? Apple Silicon M1 Pro

This means your VM is not connected to the internet, which can have any of a number of reasons. Please check out the Ubuntu install guide which includes network troubleshooting steps.

@conath I followed the guide to resolve network troubleshooting, but for me is all ok! Please look at this :(

Been struggling with this as well till i came across a simple hack. Simply modify resolv.conf nameserver to a working one.
Manually set the following name servers in the /etc/resolv.conf file, so that you access the FQDMs of Ubuntu repository servers on the internet.
Add to /etc/resolv.conf:
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
Also consider applying permanent changes

Been struggling with this as well till i came across a simple hack. Simply modify resolv.conf nameserver to a working one. Manually set the following name servers in the /etc/resolv.conf file, so that you access the FQDMs of Ubuntu repository servers on the internet.
Add to /etc/resolv.conf: nameserver <IP_ADDRESS> nameserver <IP_ADDRESS>
Also consider applying permanent changes

It works now!!! Thank you so much!


Add Lazy.nvim installation guide to README

I've added the installation guide for the new popular package manager lazy.nvim

Thank you. I'm not using lazy.nvim and not familiar with it so I didn't include it in the installation section. Btw, you could try v2 branch, Dark Modern theme, ported from VSCode Dark Modern that is the official successor of Dark+.

Yeah, I have been trying out v2 branch since sometime. And it looks great. Thanks for the awesome work :)


Update Games List.json

Added "Hydro Thunder" information
Wanna contribute on adding games with pictures and backgrounds? Now you can! Just do a pull request editing the Games List.json file!

"titlename" should have the original name of the game that shows on Xbox, remove any Copyright or Trademark symbols
Images on "titleicon" should be 1024x1024, and "titlebackground" can be any size but choose one that fits on the app correctly
"titleimage" is a Discord parameter, give it any name or the game name, i will edit it after the pull request
"type" (number) is the kind of game or app, Use the following numbers depending of the type of app or game:

(1) For games, it will show "Playing (game)"
(2) For video apps, it will show "Watching (app)"
(3) For another kind of apps, it will show "Using (app)"

Remember, edit the complete code and add your game array, make sure to add
any necessary commas and brackets
I will check the code later, edit it with my titleimage and merge it if everything is ok.
You can delete this text before doing the pull request if you want

Forgot to pull this request, sorry! I thought I did pull all of your requests


Rename namespace_registry to registry

Closes #477

LGTM, just address those small typos

Thanks for catching that!


[question] JavaScript completion not working?

Hey there @roxma, I decided to open a separate issue/question to avoid muddying up the other issue that you've already fixed (feel free to close it, I've confirmed it working -- thanks!)
I'm having a tough time getting javascript completion working.. I presently have tern_for_vim installed (and working via deoplete), and would love to get it working with n-c-m. When I enter a .js file, and type a prototype, such as Object, it doesn't complete with anything, but the command input message does display: autoload/cm/sources/cm_tern.py exit.
Is there anything else I can do to debug further, or are there specific settings I need setup in my config?
Thanks again!

Plug 'roxma/nvim-completion-manager', {'do': 'npm install'}

If you are not using vim-plug, go to the directory of this plugin and execute npm install after installing this plugin.

If npm install doesn't work, use NVIM_PYTHON_LOG_FILE=nvim.log NVIM_PYTHON_LOG_LEVEL=INFO nvim to start neovim, this will generate some log file with the nvim.log_* prefix on your current working directory, then check the content of nvim.log_py3_cm_tern

Perfect! thanks @roxma, will get right back to you on that.

unfortunately, this is all I'm seeing:
2017-02-04 19:55:57,186 [INFO @ session.py:request:97] 93455 - 'Received error: [0, b'Failed to evaluate expression']
2017-02-04 19:55:57,186 [INFO @ cm.py:main:270] 93455 - Exception: b'Failed to evaluate expression'

Also, of note, npm i does rundl as expected with vim-plug.

open a javascripot file, check the result of these two command:
:echo split(globpath(&rtp,"node_modules/tern/bin/tern"),"\n")[0]
:echo [expand("%:p"),&filetype]

@roxma, should i open the JS file from nvim-completion-manager dir?

don't have to be nvim-completion-manager dir

this commit  may fix this issue, possibly, update the plugin, and try it out. I also add some more logs for helpful infomation.

hmm. my only thought  is that the:
first:
E684: list index out of range: 0
E15: Invalid expression: split(globpath(&rtp,"node_modules/tern/bin/tern"),"\n")[0]

second:
['/Users/me/code/helpers.js', 'javascript.jsx']

it is indeed installed, confirmed (despite it not finding it). i also confirmed my runtimepath does indeed point to my ~/.config/nvim/plugged/nvim-completion-manager/, and this path exists therein: node_modules/tern/bin/tern.

bummer.. i see it installed in the location i'm expecting.. is it that my runtimepath is a little whacky? i see the path to the n-c-m plugin if i :echo &rtp

Oh, I need to check for some more commands:
:echo globpath(&rtp,"node_modules/tern/bin/tern")
:echo &rtp  may be helpful for me reproducing this issue

@roxma, the result from : echo &rtp
/Users/megalithic/.config/nvim,/Users/megalithic/.config/nvim/plugged/base16-vim/,/Users/megalithic/.config/nvim/plugged/oceanic-next/,/Users/megalithic/.config/nvim/plugged/vim-airline/,/Users/megalithic/.config/nvim/plugged/vim-airline-themes/,/Users/megalithic/
.config/nvim/plugged/golden-ratio/,/Users/megalithic/.config/nvim/plugged/yajs.vim/,/Users/megalithic/.config/nvim/plugged/vim-javascript/,/Users/megalithic/.config/nvim/plugged/vim-js-indent/,/Users/megalithic/.config/nvim/plugged/vim-javascript-syntax/,/Users/seth
.messer/.config/nvim/plugged/es.next.syntax.vim/,/Users/megalithic/.config/nvim/plugged/vim-jsx/,/Users/megalithic/.config/nvim/plugged/javascript-libraries-syntax.vim/,/Users/megalithic/.config/nvim/plugged/jspc.vim/,/Users/megalithic/.config/nvim/plugged/vim-flow/
,/Users/megalithic/.config/nvim/plugged/vim-node/,/Users/megalithic/.config/nvim/plugged/vimproc.vim/,/Users/megalithic/.config/nvim/plugged/vim-git/,/Users/megalithic/.config/nvim/plugged/vim-fugitive/,/Users/megalithic/.config/nvim/plugged/vimagit/,/Users/seth.me
sser/.config/nvim/plugged/vim-conflicted/,/Users/megalithic/.config/nvim/plugged/gist.vim/,/Users/megalithic/.config/nvim/plugged/elm-vim/,/Users/megalithic/.config/nvim/plugged/vim-misc/,/Users/megalithic/.config/nvim/plugged/neomake/,/Users/megalithic/.config/nvi
m/plugged/vim-commentary/,/Users/megalithic/.config/nvim/plugged/vim-pasta/,/Users/megalithic/.config/nvim/plugged/VimAutoMakeDirectory/,/Users/megalithic/.config/nvim/plugged/vim-surround/,/Users/megalithic/.config/nvim/plugged/vim-repeat/,/Users/megalithic/.confi
g/nvim/plugged/auto-pairs/,/Users/megalithic/.config/nvim/plugged/lexima.vim/,/Users/megalithic/.config/nvim/plugged/rainbow_parentheses.vim/,/Users/megalithic/.config/nvim/plugged/closetag.vim/,/Users/megalithic/.config/nvim/plugged/vim-endwise/,/Users/megalithic/
.config/nvim/plugged/mirror.vim/,/Users/megalithic/.config/nvim/plugged/codi.vim/,/Users/megalithic/.config/nvim/plugged/iron.nvim/,/Users/megalithic/.config/nvim/plugged/neoformat/,/Users/megalithic/.config/nvim/plugged/vim-readdir/,/Users/megalithic/.config/nvim/
plugged/vim-tmux-navigator/,/Users/megalithic/.config/nvim/plugged/vim-tmux-runner/,/Users/megalithic/.config/nvim/plugged/vim-tmux-focus-events/,/Users/megalithic/.config/nvim/plugged/quick-scope/,/Users/megalithic/.config/nvim/plugged/DidYouMean/,/Users/seth.messe
r/.config/nvim/plugged/vim-cursorword/,/Users/megalithic/.config/nvim/plugged/incsearch.vim/,/Users/megalithic/.config/nvim/plugged/incsearch-fuzzy.vim/,/Users/megalithic/.config/nvim/plugged/vim-search-pulse/,/Users/megalithic/.config/nvim/plugged/FastFold/,/Users/
megalithic/.config/nvim/plugged/deoplete.nvim/,/Users/megalithic/.config/nvim/plugged/deoplete-ternjs/,/Users/megalithic/.config/nvim/plugged/echodoc.vim/,/Users/megalithic/.config/nvim/plugged/nvim-completion-manager/,/Users/megalithic/.config/nvim/plugged/context
_filetype.vim/,/Users/megalithic/.config/nvim/plugged/tern_for_vim/,/Users/megalithic/.fzf/,/Users/megalithic/.config/nvim/plugged/ultisnips/,/Users/megalithic/.config/nvim/plugged/vim-snippets/,/Users/megalithic/.config/nvim/plugged/vim-es2015-snippets/,/Users/set
h.messer/.config/nvim/plugged/vim-react-snippets/,/Users/megalithic/.config/nvim/plugged/vim-esearch/,/Users/megalithic/.config/nvim/plugged/vim-operator-user/,/Users/megalithic/.config/nvim/plugged/vim-textobj-user/,/Users/megalithic/.config/nvim/plugged/vim-textob
j-indent/,/Users/megalithic/.config/nvim/plugged/vim-indent-object/,/Users/megalithic/.config/nvim/plugged/targets.vim/,/etc/xdg/nvim,/Users/megalithic/.local/share/nvim/site,/usr/local/share/nvim/site,/usr/share/nvim/site,/usr/local/Cellar/neovim/0.1.7/share/nvim/ru
ntime,/usr/share/nvim/site/after,/usr/local/share/nvim/site/after,/Users/megalithic/.local/share/nvim/site/after,/etc/xdg/nvim/after,/Users/megalithic/.config/nvim/plugged/oceanic-next/after,/Users/megalithic/.config/nvim/plugged/vim-javascript/after,/Users/seth.mess
er/.config/nvim/plugged/es.next.syntax.vim/after,/Users/megalithic/.config/nvim/plugged/vim-jsx/after,/Users/megalithic/.config/nvim/plugged/javascript-libraries-syntax.vim/after,/Users/megalithic/.config/nvim/plugged/jspc.vim/after,/Users/megalithic/.config/nvim/pl
ugged/vim-flow/after,/Users/megalithic/.config/nvim/plugged/tern_for_vim/after,/Users/megalithic/.config/nvim/plugged/ultisnips/after,/Users/megalithic/.config/nvim/after

thanks again for helping to debug this!

additional logs with your commit:
2017-02-04 20:25:42,094 [INFO @ cm_tern.py:__init__:83] 74997 - eval for tern: split(globpath(&rtp,"node_modules/tern/bin/tern"),"\n")[0]
2017-02-04 20:25:42,095 [INFO @ session.py:request:97] 74997 - 'Received error: [0, b'Failed to evaluate expression']
2017-02-04 20:25:42,095 [INFO @ cm.py:main:270] 74997 - Exception: b'Failed to evaluate expression'

I'm missing the result of this command, :echo globpath(&rtp,"node_modules/tern/bin/tern")

@roxma that returns an empty string. :/

:help globpath on vim should give you the information on how this plugin find the tern executable
If globpath doesn't work as expected, this may be a neovim issue.
Anyway, I may use  pure python implementation workaround for finding the tern executable

oh right on.. in the meantime, here's a screenshot of the actual location. i'll read up on globpath real quick too. thanks again!
https://www.dropbox.com/s/9urhc3eysud7s7v/Screenshot 2017-02-04 20.34.21.png?dl=0

@roxma, interesting, if i glob for node_modules in the plugin folder, it returns the only 2 plces that i've installed npm modules for neovim plugins:
['/Users/megalithic/.config/nvim/plugged/nvim-completion-manager/node_modules', '/Users/megalithic/.config/nvim/plugged/tern_for_vim/node_modules']

however, if i glob any further past node_modules/, it returns an empty array. :/

Is there any special file/directory permission under the node_modules directory?

hah, i was just asking about that in freenode#neovim. will read up a bit more about it and see if there is something specific for node_modules in a plugin folder. just seems so odd that it would be.

@roxma: maybe my wildignores settings could be causing this? let me dig a bit further. we're almost there!

YEP! that was it! ok, now that i have that figured out (which stinks, will just have to handle node_modules ignoring within .agignore i reckon.
here's the output of the tern logging with your handle logging trick:
2017-02-04 20:58:03,364 [INFO @ cm_tern.py:__init__:83] 61190 - eval for tern: split(globpath(&rtp,"node_modules/tern/bin/tern"),"\n")[0]
2017-02-04 20:58:04,584 [INFO @ cm.py:main:270] 61190 - Exception: 'NoneType' object has no attribute 'group'

So this should produce the expected result?
:echo globpath(&rtp,"node_modules/tern/bin/tern",1)

yep, here is the output from the above:
/Users/megalithic/.config/nvim/plugged/nvim-completion-manager/node_modules/tern/bin/tern
/Users/megalithic/.config/nvim/plugged/tern_for_vim/node_modules/tern/bin/tern

I've committed this fix, let's check if it is working

@roxma:
2017-02-04 21:06:04,234 [INFO @ cm_tern.py:__init__:83] 82979 - eval for tern: split(globpath(&rtp,"node_modules/tern/bin/tern",1),"\n")[0]
2017-02-04 21:06:04,350 [INFO @ cm.py:main:270] 82979 - Exception: 'NoneType' object has no attribute 'group'

Oh,
what's the output when you execute
/Users/megalithic/.config/nvim/plugged/nvim-completion-manager/node_modules/tern/bin/tern
on your shell?

bah, man, i'm so sorry, i should have tried that already. an issue with my ~/.tern-project file. wow, man, again, so sorry for putting you through all this. so embarrassing. :(

i'm going to close this issue. thank you once more for sticking with this to help me debug the issue. i learned a lot with this. thank you again for your great plugin!

Thank you for helping it get better!

my absolute pleasure!

@megalithic
Just for update, I moved the javascript completion into a standalone plugin
Plug 'roxma/nvim-cm-tern',  {'do': 'npm install'}

Since the npm install required for this plugin might lead to confusion for  those not being familliar with javascript.

@roxma +1 for moving th completions to a separate repo. I would also love seeing rest of the language completions move.

@roxma Thanks for the new plug, but it might be better if we implement the completion within NCM? A plugin for a plugin(like Deoplete's approach) could be a little too much, in my opinion.

@roxma thanks for the heads up! well done sir.


Failed to activate the editor-background package.

Atom : 1.16.0 x64
Electron: 1.3.13
OS: Microsoft Windows 10 Home
Thrown From: editor-background package 1.2.38
Stack Trace
Failed to activate the editor-background package
At Cannot find module '**request**'

Error: Cannot find module 'request'
    at Module._resolveFilename (module.js:455:15)
    at Module._resolveFilename (~/AppData/Local/atom/app-1.16.0/resources/electron.asar/common/reset-search-paths.js:35:12)
    at Function.Module._resolveFilename (/app.asar/src/module-cache.js:383:52)
    at Function.Module._load (module.js:403:25)
    at Module.require (module.js:483:17)
    at require (/app.asar/src/native-compile-cache.js:50:27)
    at /packages/editor-background-master/lib/youtube.coffee:2:11)
    at /packages/editor-background-master/lib/youtube.coffee:1:1)
    at Module._compile (/app.asar/src/native-compile-cache.js:109:30)
    at /app.asar/src/compile-cache.js:216:21)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.require (module.js:483:17)
    at require (/app.asar/src/native-compile-cache.js:50:27)
    at /packages/editor-background-master/lib/editor-background.coffee:5:6)
    at /packages/editor-background-master/lib/editor-background.coffee:1:1)
    at Module._compile (/app.asar/src/native-compile-cache.js:109:30)
    at /app.asar/src/compile-cache.js:216:21)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.require (module.js:483:17)
    at require (/app.asar/src/native-compile-cache.js:50:27)
    at Package.module.exports.Package.requireMainModule (/app.asar/src/package.js:796:27)
    at Package.module.exports.Package.activateNow (/app.asar/src/package.js:207:16)
    at /app.asar/src/package.js:190:32
    at Package.module.exports.Package.measure (/app.asar/src/package.js:96:15)
    at /app.asar/src/package.js:183:26
    at Package.module.exports.Package.activate (/app.asar/src/package.js:180:34)

Commands

Non-Core Packages

What's the reason for that?

I don't get it.

how to solve the problem

@lesinliu
So, something weird happened. I had a different error pop up this time, but somehow, on the settings page for this package, if you click on the view code button, it will open an additional window with the editor-background package already loaded.
Not sure why this happens but that's how I got it to work. Also, if you try to open a file with code in it the code will not be rendered it will just be the background. To render the code I opened the settings page
(ctrl + (comma) ) and then opened the project pane (ctrl + ' ' ) and opened one of my files from there and the code was finally rendered.


Websocket handshake response missing added headers

Describe the bug
spring-boot-dependencies:2.5.2
spring-cloud-dependencies:2020.0.4 (spring-cloud-gateway-server:3.0.4)
We are using SCG to front a set of web applications implemented in Streamlit. Streamlit applications establish a websocket connection which is used to dynamically return data to the page. When the websocket connection is estabished, the streamlit server returns a Set-Cookie header that contains an XSRF token.  This token is then used for operations such as file upload.

After placing this app behind SCG, we noticed that we are no longer receiving the "additional" response headers. They are being lost as the response transits through the gateway.
I have put together a basic setup that replicates the issue using a simple Node.js websocket server, a client HTML page, and the SCG setup.
Steps to Reproduce

Run the node server.mjs file:

// install the one dependency:
// npm install ws

import { WebSocketServer } from 'ws';

const wss = new WebSocketServer({ port: 5678 });

wss.on('headers', (headers) => {
    headers.push('Set-Cookie: _xsrf=1234599');
    headers.push('X-Other-Header: hello');
});
wss.on('connection', function connection(ws) {
    console.log('Connection')
    ws.send('hi from the server');
});

Open the client.html in your browser. It should establish a connection to the websocket server and display hi from the server on the page.

<!DOCTYPE html>
<html lang="en">
<head>
    <title>WebSocket demo</title>
</head>
<body>
<script>
    port = "5678" // Go direct to server
    //port = "6600" // Go through gateway

    let ws = new WebSocket("ws://<IP_ADDRESS>:" + port + "/"), messages = document.createElement('ul');

    ws.onmessage = function (event) {
        let messages = document.getElementsByTagName('ul')[0],
            message = document.createElement('li'),
            content = document.createTextNode(event.data);
        message.appendChild(content);
        messages.appendChild(message);
    };
    document.body.appendChild(messages);
</script>
</body>
</html>

Open up the network tab, and you should also observe that the browser received two response headers (Set-Cookie and X-Other-Header).

Now configure and start up a gateway to front this server:

# Spring Cloud Gateway Config
spring:
  cloud:
    gateway:
      routes:
        - id: websocket
          uri: http://localhost:5678
          predicates:
            - Host=**
server:
  port: 6600
logging:
  level:
    org:
      springframework:
        cloud:
          gateway: TRACE

The client.html page needs to be updated to go through the gateway. This is done by changing the port number from 5678 to 6600.

<script>
    //port = "5678" // Go direct to server
    port = "6600" // Go through gateway

Go back to the browser and refresh the client.html page. You should one again see hi from the server on the page. Now examine the network tab and notice our two added headers are absent from the server response.

Setting a breakpoint in WebsocketRoutingFilter.java, I can see the missing response headers in the proxySession.handshakeinfo.headers map.
But how to get them into the response back to the browser... 🤔. I would appreciate any tips and/or hacks to get these headers through the gateway! Thanks.

Related to https://github.com/spring-cloud/spring-cloud-gateway/issues/2225

@andrewkcarter Hi, hope you are doing well. did you mange to find a solution for this issue?

Not through SCG. We had to put that websocket application behind nginx instead.

Still not fixed. Is there any workaround to this issue other than implementing WebSocketRoutingFilter ourselves?


fix(perception): adopt awsim (tlr) camera topic

Description
This PR enable to adopt awsim camera topic.
link

https://github.com/autowarefoundation/autoware.universe/pull/8676
https://github.com/autowarefoundation/autoware_launch/pull/1144

Tests performed
I have checked on AWSIM

Effects on system behavior

Not applicable.
Interface changes

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

I've rebased this to the latest main. Now testing with AWSIM Labs. https://github.com/autowarefoundation/AWSIM-Labs/releases

Works with the latest AWSIM Labs :+1:

@MasatoSaeki -san please next time test with AWSIM Labs.
AWSIM Labs is much more advanced, faster, lighter and with more features than the original AWSIM.
And it works with the main branch of the Autoware.

https://github.com/autowarefoundation/AWSIM-Labs/releases
https://autowarefoundation.github.io/AWSIM-Labs/main/
https://autowarefoundation.github.io/AWSIM-Labs/main/GettingStarted/QuickStartDemo/


investigate RW's integration with Migrate

https://github.com/golang-migrate/migrate
There is a PostgreSQL driver in migrate, but it uses some unsupported features such as
lock, transaction, not null constraints. https://github.com/golang-migrate/migrate/blob/master/database/postgres/postgres.go
Requested by PoC user

We might need to fork the file (postgres.go), to remove the not null constaint.

Let's come up with a baseline of how RisingWave works with current Migrate before next plan.

Can also refer to https://github.com/golang-migrate/migrate/blob/master/database/clickhouse/clickhouse.go
seems to use much fewer advanced features in the driver.

Forked here https://github.com/xxchan/migrate/pull/1
To test/use it:
git clone https://github.com/xxchan/migrate && cd migrate && git checkout risingwave
make

./migrate -database "risingwave://postgres@localhost:4566/dev?sslmode=disable" -path database/risingwave/examples/migrations up
./migrate -database "risingwave://postgres@localhost:4566/dev?sslmode=disable" -path database/risingwave/examples/migrations down

Notes about how it works
Basically migrate is a very simple tool. (almost close to scripting)
It's just used to go up and down from "versions" (used to recording the history?). No complex guarantees are provided.
The current state (version) is stored in a dedicated table.
v1.down.sql
v1.up.sql
v2.down.sql
v2.up.sql

migrate up 1       # this just executes v1.up.sql
migrate up 1       # this just executes v2.up.sql
migrate down 1     # this just executes v2.down.sql

IMO the advanced features like lock, transaction and not null are simply fool-proof instead of must-have, so we can remove them, just like clickhouse's implementation.


Confirmations controller rendering methods added

Confirmations controller rendering methods were missing. This PR adds following rendering methods for confirmations controller:

render_create_error_missing_email
render_not_found_error
render_not_found_error

Does this come from devise?

Yes. Devise shows some information after sending instructions.

@MaicolBen I change the test description to make it clear.


Fix tests on main.

request_headers in defaults.py is still a property, the rns_client one is now
a function.

Current dependencies on/for this PR:

main

PR #317   👈

PR #308

PR #309
PR #298

PR #300

PR #315

PR #316

PR #301

This stack of pull requests is managed by Graphite.

Merge activity

Jan 5, 8:39 PM: @rohinb2 started a stack merge that includes this pull request via Graphite.


text search takes long time.

What OS?

local computer is Mac but using remote-ssh vscode) Amazon Linux2

Description
I have a document 1500 rows x 26 columns. Ist a datatable only one column have 500 characters. I wouldnt call this necessarily bug sometimes but search is taking so much time whereas other times it gives instant result. Same search is still instant when i open the csv with editor.
Expected behavior
I think it should be instant with this size of the document.
Steps to reproduce
I cant reproduce it effectively.
Maybe helps

This file is in Amazon EFS so my one guess is when someone else is doing IO heavy jobs maybe locks it. Could you maybe help me to monitor this? Like which console I should check then this long searches are happening?

Thank you very much for developing this tool. This is making my life very easy and its realiable.
Best,
T.

Glad you like it so far.
First of all, what is long? 1s, 10s, 1 minute?
And do all your columns have 500 chars? Or only some or all?
I have tested locally with 100 000 rows, 14 columns and it takes 4/5s.
The search does not access the disk, but only the memory.
Maybe the vm is low on memory and swapping?
And what does the user interface look like? The search has a progress bar, does it fill up slowly or does it fill up and the display of results is delayed?

Okay. I can answer these questions.
First of all, what is long? 1s, 10s, 1 minute?
10s + seconds maybe 30. No more than 1 minute.
And do all your columns have 500 chars? Or only some or all?
Definetely no. Some cells in the colums are long query links. Some of them are 10 char string.
Maybe the vm is low on memory and swapping? An what does the user interface look like? The search has a progress bar, does it fill up slowly or does it fill up and the display of results is delayed?
UI is responsive. The ideal case is instant. My problematic case, progressing slowly. its not jumping in 20-30% jumps. but rather steadily going up. (for instance today is not happening). I will check next time happens and report here htop output for memory/swap. Feel free to close this, i will reopen with the new data.. I would definitely report this here.

dear @janisdd
I had the problem yesterday. This is the screen from the htop sorted by the memory. the only striking thing i see is the VIRT column of the vscode remote server.

Should I check any of the other logs in the vscode side?
Best,
T.

In the next update I'll add some timing measurements for the search. You can then look at the console (command palette: >Developers: Toggle Developer Tools) to see some timing data.


BootstrapFewShotVision

Is there interest in a BootstrapFewShotVision module?
It could bootstrap examples for vision models using image generation models and be added similar to other components:
dspy.settings.configure(lm=turbo, rm=colbert, ig=sd_xl)

If this is something that could be merged I would look into it.

Yes please! I have multiple tasks where I need something like this

I sent them this issue. Ping me if you don't hear from us within 2-3 days! Closing the issue for now.

Following, am also interested in using Dspy for vision models!

Hey @myfatemi04 ,
Omar and the team are working on dspy for the vision. Sorry for the lat reply. Can I have your email so that we can have the meeting with the team regarding the project. It will be nice if you join the project.
Thanks,
Sahil

@sahil02235<EMAIL_ADDRESS>

@sahil02235 I’m<EMAIL_ADDRESS>

Thanks guys, will send you the invite .

Also interested in applying dspy on vision tasks. May I know the latest progress for the vision part?


chore: bdd-spring-1582791822 to 0.0.1

chore: Promote bdd-spring-1582791822 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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


Added the notes feature from original watson repo

Applied the work of https://github.com/aero31aero
from the PR 405 in the original jazzband watson repo
https://github.com/jazzband/Watson/pull/405
to this watson-next repo.
watson add/start/stop now accept an optional --note and report/aggregate/log can optionally show these entries

added configuration option "options.notes_concatenate" to configure if notes specified at start/stop should be overwritten or concatenated.
small bugfixes
changed makefile to more modern python build tools

Sorry for the wait. Lots of stuff to do before Chis mas. Expect me to review and hopefully merge this next week.


Demo page not playing Audio on IOS

I'm on an iPad Pro on IOS12 and loaded the site using Chrome browser. The page loaded but the audio did not play on the button press action.
I am on a plane and the network a bit squiffy but page load seemed to be complete before I tried this.

Hi Ken thanks for reporting this bug. I’m seeing this on my end also. This bug seems to affect Chrome/Firefox/Safari iOS.
uifx was only tested on desktop browsers.
I don’t have time to fix this rn, but I would welcome a patch if you’re able to fix it.

On Jun 14, 2019, at 11:55 AM, Ken Snyder<EMAIL_ADDRESS>wrote:
I'm on an iPad Pro on IOS12 and loaded the site using Chrome browser. The page loaded but the audio did not play on the button press action.
I am on a plane and the network a bit squiffy but page load seemed to be complete before I tried this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/wle8300/uifx/issues/1?email_source=notifications&email_token=AABEVZMKSCSZ2OOA2Q2JSD3P2PSQ3A5CNFSM4HYMKNV2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GZT6C7Q, or mute the thread https://github.com/notifications/unsubscribe-auth/AABEVZI6YGNZIRWMUGAR4NTP2PSQ3ANCNFSM4HYMKNVQ.

If I can find time I will look into but like most of us my time is a rare commodity. Either way, thanks for the contribution. Small effects based sounds are definitely something I feel the modern web could benefit from (although of course overdoing it can be awful 😄 )

@wle8300 Thanks a lot for this cool library!
I've experienced similar problems with loading audio files on mobile via the Audio API. One thing that helped me doing this is to call the load function on the HTMLMediaElement.
https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement/load
So it would be something like this:
const audioElement = new Audio(this.asset);
audioElement.load()

If you want I could create a PR for this issue.

Oh awesome! Yea! Can you create a PR?
Someone else mentioned this bug last week so I think his bugfix would be a pretty big deal!

On Jul 2, 2019, at 7:38 AM, Felix Saaro<EMAIL_ADDRESS>wrote:
@wle8300 Thanks a lot for this cool library!
I've experienced similar problems with loading audio files on mobile via the Audio API. One thing that helped me doing this is to call the load function on the HTMLMediaElement.
https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement/load
So it would be something like this:
const audioElement = new Audio(this.asset);
audioElement.load()
If you want I could create a PR for this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

#2

Thx Felix! Give me a week and I’ll test/merge this. I’ll ping you to let you know!

On Jul 2, 2019, at 8:12 AM, Felix Saaro<EMAIL_ADDRESS>wrote:
#2
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@ksnyde @MrF3lix This bug has been addressed in 1.0.8. You can see it on npm.
Thanks @MrF3lix for the PR request!


Fix build for people without $GOPATH/bin in $PATH.

See https://github.com/prometheus/prometheus/issues/1574.

@sdurrheimer

👍

👍


✨ Create ERC1967 Proxy Factory

Description
Outline:
This is a factory that creates upgradeable ERC1967 proxies.
Each proxy has one admin. Conceptually, a mapping(address proxy => address admin) is stored on the factory (implemented via a functionally similar custom mapping in assembly).
To upgrade a proxy, the admin has to call an upgrade method on the factory, which will call the proxy with the required calldata. The proxy’s bytecode will perform the upgrade if and only if called by the factory.
Motivation:

We can simply use transparent proxy approach instead of UUPS approach. The UUPS approach is intended to eliminate the need for an ProxyAdmin contract, but requires devs to inherit UUPS on their implementation. We simply use the ProxyFactory as the proxy admin contract instead.
Almost optimal runtime gas performance (for non admin delegatecalls). Overhead of checking if caller is factory is 21 gas.
No need to redeploy a ProxyAdmin contract for every new proxy.
No need to verify an admin or proxy contract anymore.
Enable easy vanity addresses for upgradeable proxies via create2crunch.

Todo:

[x] Check if Etherscan supports it seamlessly.
[x] Write more thorough tests.
[x] Mine a canonical create2 vanity address for the factory. Then make a ERC1967FactoryConstants.sol that contains that canonical address as a constant, and the bytecode of the deployment (useful for testing purposes via vm.etch).

Checklist
Ensure you completed all of the steps below before submitting your pull request:

[x] Ran forge fmt?
[x] Ran forge snapshot?
[x] Ran forge test?

Pull requests with an incomplete checklist will be thrown out.

Ok, let's go.
https://etherscan.io/address/0x0000000000000c5b7100000b04dbcb3daceee29c
https://sepolia.etherscan.io/address/0x0000000000ffe8b47b3e2130213b802212439497
https://goerli.etherscan.io/address/0x0000000000000c5b7100000b04DbcB3daCeeE29c#code
https://optimistic.etherscan.io/address/0x0000000000000c5b7100000b04dbcb3daceee29c
https://arbiscan.io/address/0x0000000000000c5b7100000b04dbcb3daceee29c
https://mumbai.polygonscan.com/address/0x0000000000000c5b7100000b04dbcb3daceee29c
https://polygonscan.com/address/0x0000000000000c5b7100000b04dbcb3daceee29c


Allow connectivity to any VPN endpoint. Not just EMC

Hi @mcowger ,
First off, thank you for this awesome script, it's been very useful to me.
Basically, this PR includes the possibility to connect to any VPN server endpoint. Not just the EMC VPN servers as it was hardcoded before.
As you now have to specify the full VPN server endpoint (e.g. vpn-usa-west.emc.com) and not just the region (e.g. west), I have added the possibility to read the endpoint from an environment variable (i.e. VPNSERVER). This way you don't have to type it every time you call the script.
I have also updated the README file accordingly.
Please let me know what you think.
Thanks!

Right @mcowger, should be fixed now.

Thanks!


Add cli option for secio (default on)

Debugging is much easier without.

Duplicate of https://github.com/polkadot-js/client/issues/112


automatic handling of env vars, boto configs, etc.

i should just be able to point dbcrossbar at a gcloud keyfile and it should do the rest in terms of writing boto config files, setting BOTO_CONFIG, etc.

Honestly, as long as we're shelling out to gsutil, I would strongly prefer to use 100% standard gsutil configuration, even if it's ugly. This simplifies dbcrossbar's code considerably, and allows us to troubleshoot by troubleshooting gsutil.
Now, if we want to get rid of gsutil entirely, that's a very interesting subject, and it would allow us to tackle many other problems with regard to memory usage, setup headaches, etc.

good point


Alter Site model's capacity_kw column to support null values

Alter Site model's capacity_kw column to support null values (by making the field nullable). Other alternatives could be discussed.
Detailed Description
Context: I'm with the Hack4Impact UIUC team working on the https://github.com/openclimatefix/pv-sites-mobile repo, and we'll be giving users the chance to submit their max production capacity for their own sites. After some discussion, we've determined that this should be optional for users who might not know such information, so they can see just percent yield. Thus, we'd think the above change could let us support these users.
If this isn't possible for data generation purposes, there a few alternatives we had thought of: creating a boolean field to store whether their capacity is "real", or just putting in "1". If we store 1 in this field by default, we'd miss out on the context in the section below (though it's not of upmost importance).
Further Context
The goal here is to store whether or not a user's site has a real capacity available, so that in our UI we allow the user to see real power output (and block that if they don't have one, since it doesn't make sense to show it).
Possible Implementation
Not sure how this proposed change (making the attribute nullable) would propagate through the pv-site prediction system you have set up, so I can't say if the suggested implementation is at all feasible or accurate.

Hey @AndrewLester thanks for getting in contact.
Would you be able to explain more why users would not know their site capacity? I would have thought they would at least know a guess for their site.

@peterdudfield, thanks for your response. I think the core reason for this feature is that we want the new site to be accessible to the widest possible audience. People whose panels were set up for them, and who might not have available inverter data, could use the percent yield. @dantravers suggested we go with one of the workarounds I mentioned above: just setting their capacity_kw to 1. This would give us appropriate data (% yield), but would leave our UI with no way to know whether to hide the power units.
Let me know what you think of this additional context, and whether or not you think the workaround makes more sense. We could consider that a capacity_kw of exactly 1 might be rare, and use it as a signal for our UI.

Done with https://github.com/openclimatefix/pv-site-datamodel/pull/50!


docs: Update docs URLs to point to the new location

Summary by Sourcery
This pull request updates the documentation URL in the README.md file to reflect the new location of the docs.

Documentation:

Updated the documentation URL in README.md to point to the new location.

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

Project coverage is 88.84%. Comparing base (ed54e3c) to head (18b2e55).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #606   +/-   ##
=======================================
  Coverage   88.84%   88.84%
=======================================
  Files          41       41
  Lines        3605     3605
=======================================
  Hits         3203     3203
  Misses        402      402

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