"Mouse over" keyword seems not working in Google chrome.

"Mouse Over" keyword seems not working in google chrome. We are getting an error mentioning below
"WebDriverException: Message: u'Element is not clickable at point (-12789, 222.5)'
The same script with "mouse over" keyword which is not working in google chrome is working very fine in Firefox.
during the script run in firefox we could clearly see the mouse overing and the drop down components getting dropped and selected. but this is not happening in google chrome. the mouse over is over on the HTML element but the corresponding list which need tto be drop down on mouse over is not happening. In the robot script execution the "mouse over" keyword is executed and passed but the subsequent keyword (selection of an item from drop down) is failing with the error "WebDriverException: Message: u'Element is not clickable at point (-12789, 222.5)' .
Note: the same script which is failing in chrome is working seemlessly in firefox.
Could any correct / comment on this issue?

This issue hasn't seen any action in a while. I'm going to close it.
If anything new comes up please open a new issue.

It looks like Mouse Over doesn't work at all.


Can not setValue to EditBox on my excel 2016 ?

I have couple of editbox as a ribbon tab ( COM add-In) in my excel application. I am trying to navigate to that tab and trying to setvalue to the first edit box.
window.getControlByClassName("MyAddinTab", "NetUIRibbonTab").getElement().setFocus(); - This works and this opens up the editboxes in that tab.
window.getEditBox(1).getElement().setFocus();  - This works and set the focus on this edit box
window.getEditBox(1).setValue("Test"); - This seems to be not working.  There is no automationException or PatternNotfound exception.
( I am also not able to manually enter anything on the editbox after i run my code. I had to manually click on someother menu and the go back to my add-in tab & then my editbox works. This is totally strange)
Any idea/help on how to fix this issue ? or any workarounds?

I tried to implement this directly in C# using UI automation framework and still having same issues. I think this is a problem with excel 2016 version. I will try to downgrade it to 2014 and try again.


vscode-pytest unable to read testIds from temp file, file not created

I'm getting an error running Pytest on an individual test (using the Test Explorer).
It ends up running the entire test suite instead. Here are some more details. Was told to open this after finding a similar issue, but seems unconnected (https://github.com/microsoft/vscode-python/issues/24307#issuecomment-2457706172).
Error[vscode-pytest]: unable to read testIds from temp file[Errno 2] No such file or directory: '/tmp/test-ids-e2faf2fe418633dcef80.txt'
I'm trying to run one test but it 'fails to detect the test ID'.
Note that I'm using devcontainers, with Python + Pylance + pytest explorer installed inside.
Also, not sure if relevant: I looked at /tmp/ but can't see any files named like this. I only see files named like python-test-discovery-698debb64df061b8b350.sock
LOGS:
2024-10-31 22:11:25.650 [info] Attempting to use temp directory for test ids file, file name: test-ids-750dd803c28e00398642.txt
env vars: "TEST_RUN_PIPE":"/tmp/python-test-results-59956af0fc8ae043f0d0.sock","RUN_TEST_IDS_PIPE":"/tmp/test-ids-750dd803c28e00398642.txt"}

2024-10-31 22:11:25.658 [info] Running pytest with arguments: /root/.vscode-server/extensions/ms-python.python-2024.16.1-linux-arm64/python_files/vscode_pytest/run_pytest_script.py --rootdir=/code/myproj

2024-10-31 22:11:25.658 [info] > /usr/local/bin/python ~/.vscode-server/extensions/ms-python.python-2024.16.1-linux-arm64/python_files/vscode_pytest/run_pytest_script.py --rootdir=.

2024-10-31 22:11:25.658 [info] cwd: .

At this point I see this in my test results:
Error[vscode-pytest]: unable to read testIds from temp file[Errno 2] No such file or directory: '/tmp/test-ids-750dd803c28e00398642.txt'
Python logs don't show anything useful after that and I cancel the test runs. I also watch ls /tmp as I clicked on a test run and only saw the -result files appear. No IDs files.

It might be permissions issue with this. We might need to add a check that verifies that the temp file was created. The other thing is not really a file, it is a Unis Domain Socket. I would check permissions first.

For me on macOS 14.6.1 the error looks like this:
Error[vscode-pytest]: unable to read testIds from temp file[Errno 2] No such file or directory: '/var/folders/f5/9qsxm9ds2nd788spvqqq6hf40000gn/T/test-ids-bd662f439a6f58d10bbe.txt'
The directory exists and there are plenty of other vscode related files in there (called something like vscode-git-0b14b03a2b.sock, pyright-98926-9DQScs6SskRz, etc.), so maybe not a permission problem?


Setup Error

now actually the error that receive after installation and copy doctrine.php is the following:
In Setup.php line 139:
Type error: Argument 1 passed to Doctrine\ORM\Tools\Setup::createCacheConfiguration() must be of the type boolean, null given, called in /home/vagrant/code/test/vendor/doctrine/orm/lib/Doctrine/ORM/Tools/Setup.php on line 126
i have filled on file config/doctrine.php only the following line
'mapping'    => 'yaml',
Lumen (5.6.2) (Laravel Components 5.6.*)
Please include code that reproduces the issue. The best reproductions are self-contained scripts with minimal dependencies.
code goes here

I think you would be better off using https://github.com/laravel-doctrine/orm instead, we've been slowly migrating away from this library and none of us have tested it with newer Lumen versions than 5.4.

Okay i think to use this library many thanks for suggestion


[question] generate compile_commands.json over the command line

At the moment I am exporting compile_commands.json for a solution via Export Compilation Database button in visual studio.
Is there a way to do this over the command line?

Hello @FrancescElies ,
Naturally, all functionality of Clang Power Tools is accessible via clang-build.ps1, our automation script.
You can invoke it using Poweshell, e.g. .\clang-build.ps1 -proj "c:\myproject\sample.vcxproj" -export-jsondb
This will export the compilation database file in the current working directory.
Regards,
Gabriel

@hero101111
Thanks for your message, just gave it a shot but I got

Am I doing something wrong?

That message is displayed because of multiple clang-build.ps1 invocations in the same command-line session. We can take care of that but it is benign here. Also we should not display the 'Exported JSON Compilation Db to...' message when no projects are found, we will have to fix that.
However, the question to be addressed is why there are no projects discovered by CPT. Make sure that the current working directory contains Visual Studio solutions and projects and you do not pass a filter using the -proj parameter that would filter out all projects. What are your invocation command line args?

Alright I executed the previous command in a non developer prompt, now that error is gone.
Using powershell developer prompt with working dir C:\s\clang-power-tools\ClangPowerTools\ClangPowerTools
.\clang-build.ps1 "C:\s\eklang\src\eklang.sln" -export-jsondb
Now I get

Json is empty, but the same works fine for the same solution if I export things from visual studio.

Hi @FrancescElies
Please take note that you should give a project as argument to the script, not the solution file.
Retry and let us know if then it works correctly.
Regards,
Gabriel

With .\clang-build.ps1 -proj "c:\myproject\sample.vcxproj" -export-jsondb I get the previous kJsonCompilationDbPath error again.
Since this is not an open project where I could share the vcxproj with youI think I am just fine to export things with a click in visual studio, so feel fre to close this bug if you like.

Also, I failed to notice in your previous example that you have your working directory pointing to the CPT location, that is not how it's intended to be used. You should have the CWD pointing to the root directory of your projects/solutions.

I will Give it another try on Monday. Thanks for your help

So finally got to have a look into this again.
Executing the following with CWD a visual studio solution works.
C:\s\clang-power-tools\ClangPowerTools\ClangPowerTools\clang-build.ps1 -export-jsondb
At the begining I still get

But the script continues and endsup exporting compile_commands.json, shall we close this issue? I am already happy with this outcome.

Hi @FrancescElies
Good to hear that you got it working. I am now closing this issue.
Thanks for reaching out to us and we hope you continue enjoying using Clang Power Tools.
Regards,
Gabriel.


Encrypt properties couldn't be resolved from environment variables

When I set environment variables (like ENCRYPT_KEYSTORE_ALIAS) they are resolved during KeyCondition resolution but are not set in org.springframework.cloud.bootstrap.encrypt.KeyProperties instance during TextEncryptor instantiation in org.springframework.cloud.bootstrap.encrypt.EncryptionBootstrapConfiguration. This works only if I explicitly write encrypt section in bootstrap.yml.
Key Management section in Docs says that I should place encrypt section in application.yml but EncryptionBootstrapConfiguration works with bootstrap.yml.

Version 1.3.0.RELEASE

Just want to make sure I understand what you are doing...
Are you setting encrypt.keyStore.alias to ${ENCRYPT_KEYSTORE_ALIAS} and this does not work when places in application.properties but works when places in bootstrap.properties?

I can substitute application.yml properties with environment variables according to conversion rules (e.g. SERVER_PORT). And I can substitute for example Spring Cloud Config Client bootstrap.yml properties with environment variables (e.g. SPRING_CLOUD_CONFIG_NAME etc.). But I can't substitute encrypt properties in Spring Cloud Config server bootstrap.yml.
If I run application with application.yml like this:
server:
  port: 8888

security:
  user:
    name: root
    # password:

bootstrap.yml:
encrypt:
  key-store:
    alias: key
    location: classpath:keystore.jks
    password: ${ENCRYPT_KEYSTORE_PASSWORD}
    # secret:

and the following environment variables:
SECURITY_USER_PASSWORD=letmein
ENCRYPT_KEYSTORE_SECRET=secret
ENCRYPT_KEYSTORE_PASSWORD=letmein

Then application start would fail because keystore secret would be null.
Another question about documentation. It says:

Put the server.jks file in the classpath (for instance) and then in your application.yml for the Config Server...

followed by keystore configuration block. But these properties should be placed in bootstrap.yml not application.yml.

I am not seeing either problem.  If I take the sample config server app and move the encrypt.* properties from bootstrap.yml to application.yml I can still encrypt values.  I can also set the environment variable KEYSTORE_PASSWORD and it will be used when trying to unlock the keystore (using bootstrap.yml).

At this point I think we need a sample project that recreates the problem.

@mkanev  - the properties you're using is incorrect for environment variables.. when there is a camel case - spring requires it to be split with an underscore to be able to use as environment variable.
So when you have these variables below, you'll not need to have any declaration of them in your yaml files.
ENCRYPT_KEY_STORE_PASSWORD=letmein
ENCRYPT_KEY_STORE_ALIAS=testalias
ENCRYPT_KEY_STORE_SECRET=changeme

Tat works perfectly fine. Thanks.


Delete hugo "print" output type from section

Description
I'm trying to set up the local environment by following the steps in this guide.
It works until step:
cd <path_to_your_repo>/umh.docs.umh.app
hugo server --buildFuture

Which results in the error:
Error: command error: failed to create config: unknown output format "print" for kind "section"

The hugo.toml file contains a "print" Hugo output type under the section output. It's not mentioned in the list of Hugo output formats. If it's something custom I think it needs additional configuration.
Checklist
You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[X] I have read the contributing guidelines and the code of conduct.
[X] I have followed the documentation style.

Additional information
Removing the "print" entry fixes this particular issue. However, the build fails because some components are missing:
Error: error building site: assemble: "/home/denis/code/umh.docs.umh.app/umh.docs.umh.app/content/en/docs/architecture/microservices/community/tulip-connector.md:32:1": failed to extract shortcode: template for shortcode "swaggerui" not found

I will not include this error because I think this topic warrants a separate PR if it's an actual problem.

I have taken a look at the issue, and it's related to the documentation itself, not to the Hugo configuration. We recently made some changes that have not been documented.
So, the print output format actually comes from the Docsy theme, but following the current instructions, it's impossible to initialize the submodule.
The correct steps after cloning the repository and setting the remote would be:

Run the make install command to initialize the dependencies

Optionally, if GNU make is not installed the following:

git submodule update -f --init --recursive
cd umh.docs.umh.app/themes/docsy && npm install
cd ../.. && npm install postcss-cli autoprefixer

Run the make serve command to start the development server locally

Also, the make help command has been removed and should no longer be referenced
Regarding the swaggerui shortcode, that is also part of Docsy, therefore should work if following the new instructions.
cc @JeremyTheocharis that made the changes to the Makefile, as he can give more insights on how to change the documentation or even take over if needed.

I'm running into the following error when executing make serve:
Serving site...
Watching for changes in /home/denis/code/umh.docs.umh.app/umh.docs.umh.app/{archetypes,assets,content,i18n,layouts,package.json,static,themes}
Watching for config changes in /home/denis/code/umh.docs.umh.app/umh.docs.umh.app/hugo.toml, /home/denis/code/umh.docs.umh.app/umh.docs.umh.app/themes/docsy/config.yaml
Start building sites …
hugo v0.119.0+extended linux/amd64 BuildDate=unknown

Built in 476 ms
Error: error building site: "/home/denis/code/umh.docs.umh.app/umh.docs.umh.app/content/en/docs/architecture/datamodel/database/processValueStringTable.md:1:1": "/home/denis/code/umh.docs.umh.app/umh.docs.umh.app/layouts/_default/_markup/render-image.html:16:23": execute of template failed: template: _default/_markup/render-image.html:16:23: executing "_default/_markup/render-image.html" at <imageConfig (add "/static" ($dst | safeURL))>: error calling imageConfig: image: unknown format
make: *** [Makefile:56: serve] Error 1

Try to delete the local repository and clone it again, as maybe executing all the commands messed up something. Also, check that the version of Hugo is v0.111.3 and of Node.js is v18.16.0.
The current make install command supposes that you are running on a Debian-based system to install the correct version of Hugo, so if that's not the case for you, you might want to install Hugo manually

Deleting and cloning again did the trick. Thanks!


feat(executor): Add toggleterm

After run, toggleterm will be closed by pressing any key.
Type <C-\><C-n> to enter normal mode.
This process can be automated.
Terminal:new({
  -- dir, cmd, close_on_exit ...
  on_open = function(t)
    -- enter normal mode
    vim.api.nvim_feedkeys(vim.api.nvim_replace_termcodes([[<C-\><C-n>]], true, true, true), "", true)

    -- (optional) set close shortcut
    vim.api.nvim_buf_set_keymap(t.bufnr, "n", "q", "<cmd>close<CR>", { noremap = true, silent = true })
  end
})

Do you think it's better to add this?

I'm not really a toggleterm user, so I don't know how the workflow goes. Do what you think is the best and I'll merge it.

Although it does make sense to go into normal mode to view the output properly

fixed it.


RAC5846: SouceCode-Function-Test: implement a shell script to deploy rackhd with source code

Story RAC-5846

build.sh: A standalone shell script for building rackhd from source code

deploy.sh: A standalone shell script for deploying rackhd from source code

resources: The folder contains all the config file for pipelines.

resources/pipeline/rackhd/source_code/config.json: The config file for running docker with rackhd built from source code.

src/pipeline/rackhd/source_code/docker: The folder contains files for building docker images with rackhd built from source code.

@panpan0000 @changev @anhou @iceiilin

test this please

test this please


Docker images does not contain correct version of CMake (IDFGH-2559)

Problem Description
The provided docker image contains the wrong CMake version.
-> Expected version: 3.13.4
(compare: https://github.com/espressif/esp-idf/blob/release/v4.0/tools/tools.json)
-> Actual version: 3.10.2
(compare: docker run -it espressif/idf:release-v4.0 cmake --version)
Expected Behavior
It is expected, that all provided build environments utilize the exact same tools.
Actual Behavior
Docker container uses a version of cmake which is deviated from the given tools.json file.
Steps to reproduce

docker run -it espressif/idf:release-v4.0 cmake --version

Fixed on release/v4.0 branch in https://github.com/espressif/esp-idf/commit/1b0473494fbaf53c945d267ac0cfbc2c8b78d98e. Newer version of CMake should now be part of the docker image with release-v4.0 and v4.0.1 tags.


[dont merge] Configure tests with random order

I confess that I don't have a lot of experience using Test Unit in Ruby - I've mostly used Rspec. For a while now I've been making changes and running all the tests with this:
$ bundle exec rake test

But I finally decided to stop being lazy and learn something about Test Unit - I discovered I could run an individual test like so:
$ ruby -I test path/to/file.rb

This really helped me make some progress on the stuff I'm trying to add to this library but then I discovered that I'm able to run tests in isolation that succeed in the full suite - test leakage!!
Here's an example:
$ ruby -I test test/unit/lookups/maxmind_geoip2_test.rb

test/unit/lookups/maxmind_geoip2_test.rb
Loaded suite test/unit/lookups/maxmind_geoip2_test
Started
.E
===============================================================================
Error: test_dynamic_localization_fallback(MaxmindGeoip2Test): Geocoder::ConfigurationError: When using MaxMind GeoIP2 you must specify a service and credentials: Geocoder.configure(maxmind_geoip2: {service: ..., basic_auth: {user: ..., password: ...}}), where service is one of: [:country, :city, :insights]
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:34:in `configured_service!'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:18:in `query_url'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:24:in `cache_key'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:245:in `fetch_raw_data'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:196:in `fetch_data'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:59:in `results'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:46:in `search'
/Users/jon/code/geocoder/lib/geocoder/query.rb:11:in `execute'
/Users/jon/code/geocoder/lib/geocoder.rb:22:in `search'
test/unit/lookups/maxmind_geoip2_test.rb:44:in `test_dynamic_localization_fallback'
     41:   end
     42:
     43:   def test_dynamic_localization_fallback
  => 44:     result = Geocoder.search('<IP_ADDRESS>').first
     45:
     46:     result.language = :unsupported_language
     47:
===============================================================================
E
===============================================================================
Error: test_dynamic_localization(MaxmindGeoip2Test): Geocoder::ConfigurationError: When using MaxMind GeoIP2 you must specify a service and credentials: Geocoder.configure(maxmind_geoip2: {service: ..., basic_auth: {user: ..., password: ...}}), where service is one of: [:country, :city, :insights]
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:34:in `configured_service!'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:18:in `query_url'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:24:in `cache_key'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:245:in `fetch_raw_data'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:196:in `fetch_data'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:59:in `results'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:46:in `search'
/Users/jon/code/geocoder/lib/geocoder/query.rb:11:in `execute'
/Users/jon/code/geocoder/lib/geocoder.rb:22:in `search'
test/unit/lookups/maxmind_geoip2_test.rb:34:in `test_dynamic_localization'
     31:   end
     32:
     33:   def test_dynamic_localization
  => 34:     result = Geocoder.search('<IP_ADDRESS>').first
     35:
     36:     result.language = :ru
     37:
===============================================================================
.E
===============================================================================
Error: test_result_attributes(MaxmindGeoip2Test): Geocoder::ConfigurationError: When using MaxMind GeoIP2 you must specify a service and credentials: Geocoder.configure(maxmind_geoip2: {service: ..., basic_auth: {user: ..., password: ...}}), where service is one of: [:country, :city, :insights]
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:34:in `configured_service!'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:18:in `query_url'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:24:in `cache_key'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:245:in `fetch_raw_data'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:196:in `fetch_data'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:59:in `results'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:46:in `search'
/Users/jon/code/geocoder/lib/geocoder/query.rb:11:in `execute'
/Users/jon/code/geocoder/lib/geocoder.rb:22:in `search'
test/unit/lookups/maxmind_geoip2_test.rb:10:in `test_result_attributes'
      7:   end
      8:
      9:   def test_result_attributes
  => 10:     result = Geocoder.search('<IP_ADDRESS>').first
     11:     assert_equal 'Los Angeles, CA 90001, United States', result.address
     12:     assert_equal 'Los Angeles', result.city
     13:     assert_equal 'CA', result.state_code
===============================================================================

Finished in 0.007089 seconds.
-------------------------------------------------------------------------------
5 tests, 2 assertions, 0 failures, 3 errors, 0 pendings, 0 omissions, 0 notifications
40% passed
-------------------------------------------------------------------------------
705.32 tests/s, 282.13 assertions/s

This test passes when you run the entire suite and fails when you run it in isolation. So then I looked around and found that you can configure Test Unit to run tests in a random order. I did that and ran the test rake task that was previously working every time and now it's not working at all. 😭 😭 😭
I looked at the failures and they aren't one thing. Some of them are related to constants being defined or not. I found a CGI issue. I actually did diagnose the one for the example above and it turns out to be due to a missing super call in the setup method. I'll PR that separately - seems worth merging.
But yeah, this is rough! I'm not sure where to go with this but I figured opening a PR and at least bringing this up was worth doing. I think ultimately it should be a goal of the geocoder project to be able to run the tests randomly because that's a best practice. What do you think @alexreisner?

Wow and yikes and thank you. I completely agree that the tests should run individually and in any order. I'd be happy to look at any PRs that help us towards that goal. Looks like there's a lot that needs to get cleaned up... Slightly embarrassing.

This turned out to be a fairly simple fix. None of the test classes were calling super from their setup methods, so the configuration wasn't being properly initialized between tests. The lookup-specific config was leaking. That was really the only issue. Thanks for pointing this out!


Hybrid model classification ROM and high-fidelity model runs

Issue Description
It would be nice to have a way to classify the data set based on when the high-fidelity model or the ROM are executed (e.g. plotting in different colors)

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[ ] 1. Is it tagged with a type: defect or task?
[ ] 2. Is it tagged with a priority: critical, normal or minor?
[ ] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[ ] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[ ] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[ ] 1. If the issue is a defect, is the defect fixed?
[ ] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[ ] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[ ] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[ ] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

@wangcj05


Add new site to 'General Tools' section

Learn. Teach. Upskill. A better way to build websites, apps, games and more.

@Ariyibi-Baseet I can solve this issue. Can you assign to me ?

I've done it already now

I would love to work on this issue. Kindly assign this issue!


Shuffle Step

Problem:
During the development of Pachyderm 1.8, many improvements were made to speed up the merging process, but this process still needs improvements and has some issues at high datum counts within a single job. The merging process makes many object storage requests (proportional to the number of datums) because it uses object storage as the intermediary storage for metadata. This high number of requests has caused unpredicatable object storage behavior in s3 on certain workloads because we make the requests much quicker and more bursty than the old merge which was much slower.
Potential Solution:
In order to avoid the high number of object storage requests during the merge, we can shuffle the output metadata between the workers within the cluster instead of using object storage as an intermediary storage for the merge. The exact implementation of this can vary, but I will lay out a high level algorithm that seems to make sense.

While a worker is processing datums in a chunk, it writes out the metadata that will be sent to each shard to files that correspond to each of the shards.
When the worker has finished processing a chunk, the metadata will be sent to the appropriate workers responsible for each shard.
A chunk will be marked as complete when both the processing is complete and the metadata has been sent to the appropriate workers.
The workers responsible for shards will perform the merge using this local data.

Potential Concerns:
What happens if a machine that fails had a worker who was responsible for a shard and we lose the datum hashtrees?
A way to handle this is to have the hashtrees also available in object storage in some format. In terms of first steps, we may want to have workers continue to write out datum hashtrees as they are processed because writing out the datum hashtree has not proved problematic up to this point. This would mean that we could download the hashtrees from object storage in the case that a machine with a worker responsible for a shard crashed and this would also allow us to introduce this change without needing migration. In the long run, we would probably want to batch output hashtrees and have them pre-filtered (objects correspond to shard metadata rather than full datum hashtrees).

Update
This is an update on where we are in terms of the shuffle step implementation. The model that we decided to go with is a pull-based model rather than a push-based model, which was what we described in the original design. The pull-based model has much cleaner failure semantics and is a simpler implementation that meets our performance requirements. The set of operations that happen now look like this:

While a worker is processing a chunk, it is writing the completed datum hashtrees to both object storage and a local datum cache.
When a worker finishes processing a chunk, it merges the datum hashtrees in the local datum cache into a hashtree that it stores in the local chunk cache (which stores merged chunks). Then, it marks the chunk as complete with its address in the chunk state.
As chunks are completing, workers responsible for shards are requesting the chunk hashtrees from the workers that processed them, and thus have them cached locally. The requesting workers also send a shard identifier that the workers will use to filter the results to just the data relevant to the requester. If a request for a particular chunk hashtree fails, then these workers will fall back on the old model to pull and filter datum hashtrees from object storage. This fallback happens at a per-chunk granularity, so one worker going down does not cause us to fallback to object storage for the later chunks.
After all processing is complete, the workers responsible for shards will merge the chunk hashtrees that are stored locally.

Notes:

Something new added that was not really talked about in the original post is new shard claiming logic that persists across jobs. When a worker starts, it will attempt to claim one of the shards and keep it for as long as possible. The goal with this is to support caching across jobs (to avoid re-downloading data for subsequent jobs) in the future. If a worker goes down or fails to renew its claim on a shard, all of the workers without shards will attempt to acquire the newly available shard (which may include the worker who originally claimed the shard)
In the full re-merge case (re-processed datums) each worker will download the skipped datum hashtrees in the chunks they process and merge them into the chunk tree. This a simple to reason about model, particularly in terms of the actual implementation, since the workers doing a merge will only need to have logic for determining if it is using a parent or not in the merge.

Discussion on whether we really want the shuffle aspect of the work we have done so far rather than better object storage batching
We discovered a serious bug in the process of implementing the shuffle step that may have been the primary contributor to the unpredictable object storage behavior. The bug essentially was a busy loop in each worker that failed to claim a chunk/merge when they were waiting on the last set of chunks/merges to complete. This resulted with a ton of CPU usage and network activity (100% CPU usage and ~2.5 million packets per node in a 10 node cluster (20 workers / 5 mergers) with machine type of r4.xlarge in AWS on a simple 100,000 datum workload). After discovering this, we decided to think a bit more about whether we really want shuffling logic or if just more effective batching to object storage would meet our needs. We are having some trouble reproducing the issues some users have been seeing with the merge hanging, but it is worth considering whether continuing down the route of managing a shuffle makes sense from a complexity vs value standpoint.
Pros of shuffling:

A constant factor improvement in merge time because we remove the object storage hop to get the data to the correct merger (this will come into play more when we are merging the actual data).
Could be noticeably less expensive in the case where there are many chunks

Pros of just batching on top of object storage:

Less complexity

I am leaning towards keeping the shuffling right now because the constant factor improvement could be very noticeable and the complexity does not seem excessive. In terms of complexity, the main concern is future complexity that will come with moving the actual output data between workers to be merged. I think for the most part the issues we would run into there (too much data for disk) will have to be addressed even if we are using object storage for the intermediary because we need to get all the data through disk and merged. There probably will be some check pointing during the merge in those particular cases.

Implemented.


Test for multi-inheritance for ranked labelsets

Suggest rather than fail we should post a prominent warning on startup that tree browser and writing to AnnData may be unsafe until this is fixed.

In testing


[OData] Incorrect handling expand and skip parameters combination

If we have a request like this:
Users?$skip=40&$top=20&$orderby=LastName%20asc&$filter=Active%20eq%20%27Yes%27%20and%20TechnicalUser%20eq%20%27No%27%20and%20ExternalUser%20eq%20%27No%27&$expand=Apps

we can see db requests like this
SELECT "T0"."Id" AS "Id_T0" FROM "CVUSER" AS T0 LEFT JOIN "CVAPP" AS "T1" ON "T1"."Id" = "T0"."Id" WHERE "T0"."Active" = ? AND "T0"."TechnicalUser" = ? AND "T0"."ExternalUser" = ? ORDER BY "T0"."LastName" ASC LIMIT 140 OFFSET 40

and
SELECT "T0"."CreatedOn" AS "CreatedOn_T0", "T0"."CreatedOnDay" AS "CreatedOnDay_T0", "T0"."CreatedBy" AS "CreatedBy_T0", "T0"."ChangedOn" AS "ChangedOn_T0", "T0"."ChangedOnDay" AS "ChangedOnDay_T0", "T0"."ChangedBy" AS "ChangedBy_T0", "T0"."ValidFrom" AS "ValidFrom_T0", "T0"."ValidFromDay" AS "ValidFromDay_T0", "T0"."ValidTo" AS "ValidTo_T0", "T0"."ValidToDay" AS "ValidToDay_T0", "T0"."Active" AS "Active_T0", "T0"."TechnicalUser" AS "TechnicalUser_T0", "T0"."ExternalUser" AS "ExternalUser_T0", "T0"."AzureStatusEmail" AS "AzureStatusEmail_T0", "T0"."AzureStatusSAML" AS "AzureStatusSAML_T0", "T0"."AzureCheckedOn" AS "AzureCheckedOn_T0", "T0"."AppIds" AS "AppIds_T0", "T0"."AppTitles" AS "AppTitles_T0", "T0"."GroupTitles" AS "GroupTitles_T0", "T0"."GroupDescriptions" AS "GroupDescriptions_T0", "T1"."Id" AS "Id_T1", "T1"."Title" AS "Title_T1", "T1"."CreatedOn" AS "CreatedOn_T1", "T1"."CreatedBy" AS "CreatedBy_T1", "T1"."DomainId" AS "DomainId_T1", "T1"."CreatedOnDay" AS "CreatedOnDay_T1" FROM "CVUSER" AS T0 LEFT JOIN "CVAPP" AS "T1" ON "T1"."Id" = "T0"."Id" WHERE "T0"."Id" IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) ORDER BY "T0"."LastName" ASC LIMIT 100 OFFSET 40

The first request does not set the correct limit and the second request should not set a limit and offset.

Issue cloned to https://github.com/eclipse/dirigible/issues/1650

fixed with https://github.com/eclipse/dirigible/pull/1651


Fix bitbucket upstreams

What I Did
Updated go-getter to include a fix for bitbucket upstreams, as https://github.com/hashicorp/go-getter/issues/183 has been resolved by https://github.com/hashicorp/go-getter/pull/189.
How I Did it
How to verify it
Bitbucket upstream unit tests have been reincluded.
Description for the Changelog
Bitbucket upstreams are once again supported
Picture of a Ship (not required but encouraged)

So it looks like the istio failures are legitimate failures, and not something that's happening randomly
I'll have to investigate this further


Added command line option to specify CL3.0 feature macros

This adds the ability to specify OpenCL3.0 feature macros that should be enabled by the clang frontend.
One thing I'm not sure about in this PR is the overlap of some options, specifically FP64 and ImageSupport. I think it would be best for the program to error out when one of these is disabled but the feature macro is enabled, but I'm not sure how CLSPV usually manages that.
This contribution is being made by Codeplay on behalf of Samsung.

Take a look at ParseOptions in lib/Compiler.cpp to see how we handle incompatible options specifications.
I think longer term we may want to deprecate (and remove) some options if we want to specify feature macros.

Thanks @alan-baker, that worked well for me.

I think I've fixed the MSVC compile error, unfortunately I don't have a machine to test it on.


PHP 8 dependency problem

Problem 1
- phphleb/updater[dev-master, v1.0.0, ..., v1.0.10] require php ^7.0.0 -> your php version (8.0.14) does not satisfy that requirement.
- phphleb/hlogin[v1.2, ..., v1.2.14] require phphleb/updater * -> satisfiable by phphleb/updater[dev-master, v1.0.0, ..., v1.0.10, 9999999-dev].
- Root composer.json requires phphleb/hlogin ^1.2 -> satisfiable by phphleb/hlogin[v1.2, ..., v1.2.14].

@evan70
Fixed
https://github.com/phphleb/updater/commit/08471286f42961732da15b9f7d8a69113dafd325
https://github.com/phphleb/ucaptcha/commit/d5adac1060b77676bb4466e5cd5cdef4b23b5e5b

Thank Ya <3


Constrúct SessionCounter once

Creating SessionCounter every time we need the next session is wrong,
we might end up getting the same session id for two different
deployments, e.g. if they are happening in two different threads or on
two different config servers at the same time.

If application A and B for the same tenant is deployed simultaneously on 2 different config servers in a cluster getNextSessionId() might be called simultaneously. Say A creates counter, initializes it to 1, then creates a new session, so new value should be 2. But B might initialize it to 1 (because it finds no existing sessions) although it has already been increased to 2. See InitializedCounter(). I guess this can still happen after this PR, but haven't looked into it yet.
We have had unstable system tests with issues that seems to be caused by session id not being incremented correctly. I haven't seen any of them after this went in (but I haven't looked at all tests, so can't say for sure).

If application A and B for the same tenant is deployed simultaneously on 2 different config servers in a cluster getNextSessionId() might be called simultaneously. Say A creates counter, initializes it to 1, then creates a new session, so new value should be 2. But B might initialize it to 1 (because it finds no existing sessions) although it has already been increased to 2. See InitializedCounter(). I guess this can still happen after this PR, but haven't looked into it yet.
We have had unstable system tests with issues that seems to be caused by session id not being incremented correctly. I haven't seen any of them after this went in (but I haven't looked at all tests, so can't say for sure).


⚠ Geosearch has degraded performance

In 0fffe74, Geosearch ($SITE_URL_GEOSEARCH) experienced degraded performance:

HTTP code: 200
Response time: 3162 ms

Resolved: Geosearch performance has improved in cc1ab3a after 8 minutes.

Resolved: Geosearch performance has improved in b12d75d after 8 minutes.


Search response resource fixed (FINERACT-1370)

Description
Fixed the response for search/ and search/advance endpoints. Earlier it was returning the objects, now changed to lis of respective objects(GetSearchResponse and PostAdhocQuerySearchResponse).
For more info see Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

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

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

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

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

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

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

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

please review the PR, @ptuomola, @thesmallstar , @vidakovic .
Thanks :)


Add AllowPolyBase and PolyBaseSettings properties to SqlDWSink

Add AllowPolyBase and PolyBaseSettings properties to SqlDWSink.

Can one of the admins verify this patch?

Hi @iRainbow5, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (bowan). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@azuresdkci add to whitelist

@akromm Can you suggest an appropriate person on the SQL team to review?

@iRainbow5 We need an official review from the SQL team for this PR.  I have tagged Adam to take a look and assign a reviewer.

@markcowl I typically own the ADF SDK process. I've left a few comments on this, though we also do codeflow reviews internally before sending PRs.

@iRainbow5 this has merge conflicts. Please resolve and also squash your commits: Git Interactive Rebase, Squash, Amend and Other Ways of Rewriting History

@bgold09 Comments resolved. Please help to take a look. Thanks.

@azuresdkci add to whitelist

@azuresdkci retest this please

@iRainbow5 @markcowl Looks good, please merge.


Drop code-font on "Cloud Tools for PowerShell"

Especially with three full-fixed-width spaces in the name, putting it in <code> looks totally awkward. In any case, <code> should be reserved for things you will actually type at the command line, which you never do with "Cloud Tools for PowerShell", unlike gcloud or even Add-GcdManagedZone.
Also rewords text with an incorrect use of "latter" in the last paragraph. It seems "later" was meant, but even then it was in need of  more extensive restructuring for English grammar and clarity.

I signed it. I am a Google employee<EMAIL_ADDRESS>but have an existing GitHub account linked to my Gmail and other personal e-mail accounts.

LGTM, thank you for the PR! We are currently working with a UX designer on another rev of our cmdlet reference website, which can certainly use some more improvements like the one you just made.


Use prebuilt igraph library in macOS.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Automatic IDs support

@Id dep: Clz
@Id(fq = true) dep: Clz
@Id("customname" dep: Clz

or
@Id dep: Clz
@FqId dep: Clz
@CustomId("customname" dep: Clz

Is this fixed now?

Nope, it's a separate story. It may be a discussable but usable complementation for #306  but it's not smth urgent.


Worker process randomly dies during MOSMIX parsing

Hi, thanks for providing this great API!
I have been trying around for some days now but I think there is an issue. During the past 48 hours (approx.) the field "last_record" shows "2022-08-08T16:00:00+00:00" in the forecast sources. Is there maybe a problem with updating the forecasts or is this normal behaviour?
Thank you in advance!

Hi @smilingchemist,
thanks for the report, I must've falsely judged a Sentry notification as "one-time error" there. Seems that restarting our worker fixed it for now, I'll look into the cause once I'm back from vacation.
Cheers,
-Jakob

Hi Jakob,
I fear the issue came back. I wish you a nice holiday anyway.
Frank

Digging through the Sentry issue suggests that this is based on worker processes breaking while processing MOSMIX files. Maybe it's some memory issue (although we do have plenty of free memory). I will try playing around with the number of huey workers and/or their type, although this is more wild guessing than actually knowing what's going on.

4f02502

Closing as this hasn't happened in forever. The memory footprint during parsing was greatly reduced when we refactored to use dwdparse.


[5.1] Fix routing outside of default namespace

Fix applied as per Taylor's comments in #9217
URL generation fails for routing to controllers outside of default namespace.
Added a test for this eventuality and a fix so that the test passes.
Tests controller routing outside of default namespace, when a default namespace is set.

@GrahamCampbell any idea why the build has not completed? Is this a problem?


Distelli support?

Would be neat :)

Thanks for the suggestion! It seems to have builds much like Travis CI, we may have build badges.
The API is here: click me.

+1

@espadrine anything come of this?

+1

Hey @ramonsaraiva would you be interested in working on this? We have a great tutorial.

Yeah i'm thinking about tackling this when i get some free time.

Awesome. If you have any questions feel free to post them here.

Tagging needs-upstream-help based on https://github.com/badges/shields/pull/1310#discussion_r154740710.

Distelli is now part of Puppet, so I'm not sure if this is still a thing.
If it is, and read-only token have become available, feel free to ping this issue and one of the maintainers will reopen!

It is still working CI, do you need to find some issue tracker of distelli ? To request a token ?

Does it have support for read-only tokens?


import error

I have installed torchtext and using pytorch 0.4 and python=3.6
I am getting the following error while testing one of my files
  File "conll.py", line 7, in <module>
    from torchtext.datasets import SequenceTaggingDataset, CoNLL2000Chunking
ImportError: cannot import name 'CoNLL2000Chunking'

any clues?

I think it's coming from torchtext, as even without this repo there is that problem


fix: text color

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Please add support pytest

Please add support for python pytest test execution.
Changing internal/ui/tests.go line 158 unitest to pytest seems to work ok, but would be great to have support for setting the test runner in the configuration along with it's flags.

changed python tests to pytest by default


DataSet: .drop() wanted!

We should provide a method can be used to remove a column or array completely from the DataSet data and meta.

duplicate. closed.


Make sensu services more robust

Without this change I get this error in my server:
---- Begin output of /etc/init.d/sensu-dashboard restart ----
STDOUT: * Stopping sensu-dashboard
   ...fail!
 * Starting sensu-dashboard
   ...fail!
STDERR: /var/lib/gems/1.9.1/gems/bundler-1.5.1/lib/bundler/rubygems_integration.rb:240:in `block in replace_gem': sensu-dashboard is not part of the bundle. Add it to Gemfile. (Gem::LoadError)
        from /opt/sensu/bin/sensu-dashboard:22:in `<main>'
---- End output of /etc/init.d/sensu-dashboard restart ----

I'm closing this as we are unable to merge in current condition, and EMBEDDED_RUBY=true is now the default behavior. Feel free to reopen a new issue if you think this is a change still worth pursuing.


[RHBRMS-2546] Kie Server - Creating container has releaseId null

Same as on 6.5.x branch (https://github.com/droolsjbpm/droolsjbpm-integration/pull/597)

@jakubschwan could you please rebase as there was a fix for compilation error

jenkins retest this

jenkins retest this

test case failed does not seem to be related but let's retest it once again

again no space left on device while running the build... @psiroky is it possible to increase the disc or do the cleanup more frequently?

Not easily possible to increase the disc space. I did some config tweaks to run the clean-up more frequently.

build successful so +1


package install ignored because of python version "markers"

I get some troubles about missing packages.
But it depend on which Python i really have installed!
Currently i use LinuxMint and there is only Python 3.11.0~rc1-1~22.04 and i get the errors. I thought it was because it was only an RC version. So i used ppa:deadsnakes/ppa to get a newer Python 3.11 Version and it's currently 3.11.5
The boring thing about the PPA Version: It doesn't provide pip/ensurepip ... So i have to bootstrap via get-pip.py, install pipenv and the wrong matching is away...
But the get-pip.py solution is boring. So i decided to deinstall the PPA version and install Python 3.11 from source... I get:
>>> sys.version
'3.11.6+ (heads/3.11:79b81d1, Oct 11 2023, 13:42:51) [GCC 11.4.0]'
>>> sys.version_info
sys.version_info(major=3, minor=11, micro=6, releaselevel='final', serial=0)

and now i have the wrong matching errors back :(
tl;td;

Python 3.11.0 rc1 -> error: "don't match your environment"
Python 3.11.5 -> worked
Python 3.11.6+ -> error: "don't match your environment"

I seems it doesn't depends on pipenv and pip Version: I tried some downgrades from pipenv 2023.10.3 and pip 23.2.1 without success.
$ pipenv --support
Pipenv version: '2023.10.3'
Pipenv location: '/home/jens/.local/pipx/venvs/pipenv/lib/python3.11/site-packages/pipenv'
Python location: '/home/jens/.local/pipx/venvs/pipenv/bin/python'
OS Name: 'posix'
User pip version: '23.2.1'
user Python installations found:
PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.11.6',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '6.2.0-10027-tuxedo',
 'platform_system': 'Linux',
 'platform_version': '#33 SMP PREEMPT_DYNAMIC Wed Sep 27 15:55:17 UTC 2023',
 'python_full_version': '3.11.6+',
 'python_version': '3.11',
 'sys_platform': 'linux'}

Would need to be addressed in https://github.com/pypa/packaging

Maybe... Think https://github.com/pypa/packaging/issues/522 addressed this.


Remove networks module

As CTL run RPC nodes have been removed, users can choose from community-run RPC nodes from Chainlist; there is no need for this module any more.
@aiman in order for tests to pass, the RPC_URL secret should be set for the onpush GitHub action.

This is not going to be treated as a breaking change, as the module doesn't work as intended,  since there are no post-Tiber CTL nodes, and so removing a broken feature that nobody was able to use is not breaking any user workflows.

Merged, thanks!


AssertionError: Cannot extract prediction target since the index of forecast is outside the index of target

Description
I get an "AssertionError: Cannot extract prediction target since the index of forecast is outside the index of target" when trying to evaluate the prediction (code snippet below).
I probably don't understand something about GluonTS behavior, but if I am feeding in the data to evaluate, shouldn't the forecast dates match the time series by construction?
To Reproduce
I can't easily create an example or share my data. The problem is possibly with my understanding of GluonTS behavior.
After training a simple predictor, I try to evaluate the forecasts on the test data but get an error:
from gluonts.evaluation import make_evaluation_predictions

forecast_it, ts_it = make_evaluation_predictions(
    dataset=tds.test,
    predictor=predictor,
    num_samples=100,
)

forecasts = list(forecast_it)
tss = list(ts_it)

from gluonts.evaluation import Evaluator
evaluator = Evaluator(quantiles=[0.1, 0.5, 0.9], num_workers=None)
agg_metrics, item_metrics = evaluator(iter(tss), iter(forecasts), num_series=len(tds.test))
print(json.dumps(agg_metrics, indent=4))

I have checked that the shapes/length are correct:

tss entries have length 168,
forecast entries have samples of length 24 (the prediction length I specified when constructing the dataset)

The problem is that the  forecast start doesn't match the time series.  It seems as though perhaps the order of the
forecast and/or tss gets messed up? This would be easier to debug, btw, if the error message include item_ids and not just the dates.
Error message or code output
Running evaluation:   0%|          | 0/3710 [00:00<?, ?it/s]/home/datascience/conda/derv0/lib/python3.7/site-packages/gluonts/evaluation/_base.py:306: FutureWarning: Timestamp.freq is deprecated and will be removed in a future version
  date_before_forecast = forecast.index[0] - forecast.index[0].freq
Running evaluation:   2%|▏         | 68/3710 [00:00<00:16, 218.64it/s]

---------------------------------------------------------------------------
AssertionError                            Traceback (most recent call last)
<ipython-input-28-48ee4a1293b7> in <module>
      1 from gluonts.evaluation import Evaluator
      2 evaluator = Evaluator(quantiles=[0.1, 0.5, 0.9], num_workers=None)
----> 3 agg_metrics, item_metrics = evaluator(iter(tss), iter(forecasts), num_series=len(tds.test))
      4 print(json.dumps(agg_metrics, indent=4))
      5 #item_metrics.head()

~/conda/derv0/lib/python3.7/site-packages/gluonts/evaluation/_base.py in __call__(self, ts_iterator, fcst_iterator, num_series)
    226             else:
    227                 for ts, forecast in it:
--> 228                     rows.append(self.get_metrics_per_ts(ts, forecast))
    229
    230         assert not any(

~/conda/derv0/lib/python3.7/site-packages/gluonts/evaluation/_base.py in get_metrics_per_ts(self, time_series, forecast)
    312         self, time_series: Union[pd.Series, pd.DataFrame], forecast: Forecast
    313     ) -> Mapping[str, Union[float, str, None, np.ma.core.MaskedConstant]]:
--> 314         pred_target = np.array(self.extract_pred_target(time_series, forecast))
    315         past_data = np.array(self.extract_past_data(time_series, forecast))
    316

~/conda/derv0/lib/python3.7/site-packages/gluonts/evaluation/_base.py in extract_pred_target(time_series, forecast)
    266             forecast.index
    267         ), (
--> 268             "Cannot extract prediction target since the index of forecast is outside the index of target\n"
    269             f"Index of forecast: {forecast.index}\n Index of target: {time_series.index}"
    270         )

AssertionError: Cannot extract prediction target since the index of forecast is outside the index of target
Index of forecast: DatetimeIndex(['2019-06-07 07:00:00', '2019-06-07 08:00:00',
               '2019-06-07 09:00:00', '2019-06-07 10:00:00',
               '2019-06-07 11:00:00', '2019-06-07 12:00:00',
               '2019-06-07 13:00:00', '2019-06-07 14:00:00',
               '2019-06-07 15:00:00', '2019-06-07 16:00:00',
               '2019-06-07 17:00:00', '2019-06-07 18:00:00',
               '2019-06-07 19:00:00', '2019-06-07 20:00:00',
               '2019-06-07 21:00:00', '2019-06-07 22:00:00',
               '2019-06-07 23:00:00', '2019-06-08 00:00:00',
               '2019-06-08 01:00:00', '2019-06-08 02:00:00',
               '2019-06-08 03:00:00', '2019-06-08 04:00:00',
               '2019-06-08 05:00:00', '2019-06-08 06:00:00'],
              dtype='datetime64[ns]', freq='H')
 Index of target: DatetimeIndex(['2020-09-19 07:00:00', '2020-09-19 08:00:00',
               '2020-09-19 09:00:00', '2020-09-19 10:00:00',
               '2020-09-19 11:00:00', '2020-09-19 12:00:00',
               '2020-09-19 13:00:00', '2020-09-19 14:00:00',
               '2020-09-19 15:00:00', '2020-09-19 16:00:00',
               ...
               '2020-09-25 21:00:00', '2020-09-25 22:00:00',
               '2020-09-25 23:00:00', '2020-09-26 00:00:00',
               '2020-09-26 01:00:00', '2020-09-26 02:00:00',
               '2020-09-26 03:00:00', '2020-09-26 04:00:00',
               '2020-09-26 05:00:00', '2020-09-26 06:00:00'],
              dtype='datetime64[ns]', length=168, freq='H')

Environment
Operating system: Linux
Python version: 3.7.10
GluonTS version: 0.9.4
MXNet version: 1.7.0.post1

Running in a notebook, in a cloud session, on a CPU machine (no GPU).

I probably don't understand something about GluonTS behavior, but if I am feeding in the data to evaluate, shouldn't the forecast dates match the time series by construction?

Normally, yes.
What is strange here is that the dates of the forecast are in 2019, while the input data is from 2020.
What model are you using?

When I started, I had a small number of very long time series, and on those the code seems to run fine.  I then split these into smaller segments, and at some point started getting this error. I now thought it may be due to multiple time series having the same item_id after splitting, so I integrated start_time (the date) into item_id, ex:
> instances_test=[x for x in iter(tds.test)]
> [(x['item_id'],x['start'],len(x['target'])) for x in instances_test[0:5]]

[('9973--2019-08-03', Timestamp('2019-08-03 04:00:00', freq='H'), 168),
 ('9973--2019-08-10', Timestamp('2019-08-10 04:00:00', freq='H'), 168),
 ('9973--2019-08-17', Timestamp('2019-08-17 04:00:00', freq='H'), 168),
 ('9973--2019-08-24', Timestamp('2019-08-24 04:00:00', freq='H'), 168),
 ('9973--2019-08-31', Timestamp('2019-08-31 04:00:00', freq='H'), 168)]

However, the errors still occur...

How are you splitting the data?
Can you provide a reproducible example? I suspect that you might have a typo or got the ordering of arguments wrong somewhere. Our evaluation API is a bit rough at the moment, something we want to improve in the future :)

I am splitting about two years of data into monthly chunks before converting to GluonTS format. I'll try have a simple reproducible example next week.

I had the exactly same error when running examples/evaluate_model.py.

That's weird, for me it runs without errors.
What Pandas version are you using?

I have pandas 1.3.4.  (Can't run the example in my environment due to not having internet access.)

Any updates on this? Thanks.

Any updates on this? Thanks.

I was not able to reproduce the error -- examples/evaluate_model.py runs just fine.
Are you running a modified version?

After updating GluonTS to the latest version. This issue disappears. Thanks!

I've got a self-contained example. Looks like this happens when predictor is trained with freq and prediction_length that doesn't match the data. So if this happens, it is possible there was a mix-up with the wrong predictor or dataset being used.
import pandas as pd
import numpy as np
import json
from gluonts.evaluation import Evaluator
from gluonts.evaluation import backtest
from gluonts.dataset.common import ListDataset, TrainDatasets, MetaData
from gluonts.evaluation import make_evaluation_predictions

# from gluonTS tutorial: https://ts.gluon.ai/tutorials/forecasting/extended_tutorial.html#Training-an-existing-model
# create data
N = 10  # number of time series
T = 24*7  # number of timesteps
prediction_length = 24
freq = "1H"
custom_dataset = np.random.normal(size=(N, T))
start = pd.Timestamp("01-01-2019", freq=freq)  # can be different for each time series

# train dataset: cut the last window of length "prediction_length", add "target" and "start" fields
train_ds = ListDataset(
    [{'item_id': str(i),'target': x, 'start': start} for (i,x) in enumerate(custom_dataset[:, :-prediction_length])],
    freq=freq
)
# test dataset: use the whole dataset, add "target" and "start" fields
test_ds = ListDataset(
    [{'item_id': str(i),'target': x, 'start': start} for (i,x) in enumerate(custom_dataset[:, :])],
    freq=freq
)

custom_ds_metadata = MetaData(target={'name': 'target'},
                            time_granularity=freq,
                            prediction_length=prediction_length)

dataset=TrainDatasets(custom_ds_metadata, train_ds, test_ds)

from gluonts.model.simple_feedforward import SimpleFeedForwardEstimator
from gluonts.mx import Trainer

estimator = SimpleFeedForwardEstimator(
    num_hidden_dimensions=[10],
    prediction_length=4, #dataset.metadata.prediction_length,
    context_length=100,
    freq='W', #dataset.metadata.freq,
    trainer=Trainer(
        ctx="cpu",
        epochs=2,
        learning_rate=1e-3,
        num_batches_per_epoch=100,
    )
)
predictor = estimator.train(train_ds,test_ds)

evaluator=Evaluator(quantiles=[0.1, 0.5, 0.9], num_workers=None)
back_agg_metrics, back_item_metrics = backtest.backtest_metrics(test_ds, predictor, evaluator)

@dmitra79 I can confirm that the issue was solved in the 0.10.x releases: all information about frequency comes now directly from the data (see #1997) and any mis-configuration of the model will result in the model underperforming (if it's configured with the wrong freq), or in wrong experimental results (in case the prediction_length is set differently from what the experimental data expects).
Also note that in recent releases SimpleFeedForwardEstimator does not have a freq argument, and that all timestamp in the data are supposed to be pd.Period instead of pd.Timestamp.


I got some errors while using DSCFromGPO

I am unsure how many of these errors could be "new user error" on my part and are easy fixes, and how many of them could be related to something that you should be alerted to.
WARNING: ConvertFrom-GPO:PowerOptions XML file is not implemented yet.
WARNING: Write-DSCString: DSC Module (Printer) not found on System.  Please re-run the conversion when the module is available.
WARNING: Write-GPOGroupsXMLData: Deleting all users or groups en masse is not supported
Apologies if this is just related to me not reading the manual first.  :)

I think this is because of settings that are not implemented yet (could be parser or resource). Do you know which policy settings are tripping the errors? Looks like power settings, something related to printing, and I can't tell the last one.


4.2 style cleanup

Implemented code review changes suggested in slack yesterday.  Renamed VariantFilter to variant-toggle, fixed HTML indentation, refactored variant toggle info button to use InfoPopup component.  Did not refactor inline styling to CSS yet, as this caused unexpected inheritance issue

quarantest build successful. Demo link at
http://dc454a19.quarantest.iobio.io


Add "Sleep"

As stated in https://www.youtube.com/watch?v=AJdEqssNZ-U When an enemy is hit, and when they die, the game pauses for 20 milliseconds. This makes the game feel better, but is not very noticeable to the human eye.

Already did in alpha 3.0, closing this see issue #20


Restrict handling of display help flag

Fixes #126 edge case by making the handling more strict.
To shortcut to displaying the help message now requires specifically "-h" with no value behind.
Additionally, some code cleanup is done.

Codecov Report

Merging #158 (3eb10e0) into master (8ce8b36) will increase coverage by 0.09%.
The diff coverage is 59.25%.

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

running find -h mala seems like itll run find mala instead and ignores displaying the help, might need more work

running find -h mala seems like itll run find mala instead and ignores displaying the help, might need more work

There is no way to avoid this behaviour (fix one or the other) without a major rework to the tokenizer. I presume this may be less common.
In either case, I've added a minor edit to the UG to warn users against this type of input. They should call -h on the command alone.


Restart (rs) and the Webpack plugin do not work with a native module

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version
6.0.0-beta.67
Electron version
v20.1.1
Operating system
Windows 10 Version 21H1 Build 19043.2130
Last known working Electron Forge version
No response
Expected behavior
I have better_sqlite3 included in my project, which is based on the Webpack+Typescript template.
npm start works fine, and so does npm run package -- after either of these I can access the SQLite API.
It should also work when I restart it using rs as mentioned here:

https://www.electronforge.io/cli#start

If you type rs (and hit enter) in the same terminal where you ran the start command, the running app will be terminated and restarted.
Forge plugins can override this command to run custom development logic. For example, the Webpack Plugin runs a webpack-dev-server instance to provide live reloading and HMR.

Actual behavior
I get an error message when I type rs as follows:

Steps to reproduce
FYI the git commit I made to include better-sqlite3 in my project is here ...

https://github.com/cwellsx/electron_forge_template/commit/e0248593eb0ae30bdb05f34e7f260629b0112f6b

... but it was easy to do, nothing special, i.e.:

Install better-sqlite3 as a run-time dependency
Install the latest Node.js with the "Windows build tools" option enabled so that it can be built for Electron
Include it in the Main process using import sqlite from 'better-sqlite3';

Additional information
It finds better_sqlite3.node when it starts but not when it restarts.
The error message says it's looking for undefinedbuild/Release/better_sqlite3.node
In fact the better_sqlite3.node exists in the following directories:
C:\Users\Christopher\Source\Repos\pic>dir /s better_sqlite3.node
 Volume in drive C is Windows
 Volume Serial Number is 6EBC-4C1A

 Directory of C:\Users\Christopher\Source\Repos\pic\.webpack\main\native_modules\build\Release

05/11/2022  18:29         2,659,328 better_sqlite3.node
               1 File(s)      2,659,328 bytes

 Directory of C:\Users\Christopher\Source\Repos\pic\node_modules\better-sqlite3\build\Release

23/10/2022  09:41         2,659,328 better_sqlite3.node
               1 File(s)      2,659,328 bytes

 Directory of C:\Users\Christopher\Source\Repos\pic\out\pic-win32-x64\resources\app\.webpack\main\native_modules\build\Release

29/10/2022  09:52         2,659,328 better_sqlite3.node
               1 File(s)      2,659,328 bytes

     Total Files Listed:
               3 File(s)      7,977,984 bytes

The one which it's successfully using when it starts is presumably the one in the .webpack\main\native_modules\ directory -- and this is the path fragment that's replaced with "undefined" during a restart.
I see there are previous issues related to rs -- https://github.com/electron/forge/issues?q=rs -- but they're all close.

Hey @cwellsx, would you mind trying this with v6.0.0? I think we may have addressed this issue in a later beta version than the one you’re running, just want to make sure that’s the case.

Hi @VerteDinde thank you.
Yes, I should try with v6.0.0.
Probably next week-end (Nov, 12-13).

I tested this on latest forge (inited from template, added depedency, etc.)
Had to drop to Electron 19 because that module doesn't support Electron 20 or higher yet (https://github.com/WiseLibs/better-sqlite3/pull/870) but other than that it works fine during both start, restart and package

Yes thanks, I confirm I no longer have the problem with the released 6.0.0 version.
BTW instead of dropping the Electron version I install the pull request:
npm install WiseLibs/better-sqlite3#pull/870/head

@MarshallOfSound I confirm that I still have this problem, with the 6.0.0 release.

This loads fine -- npm start and then rs
But this errors -- if I edit the source code, after  npm start and before rs

BTW instead of dropping the Electron version I install the pull request:
npm install WiseLibs/better-sqlite3#pull/870/head

Let me know if you want more information or anything.

The problem is this line of code:

https://github.com/WiseLibs/better-sqlite3/blob/master/lib/database.js#L48

		addon = DEFAULT_ADDON || (DEFAULT_ADDON = require('bindings')('better_sqlite3.node'));

That TypeScript statement translates to this JavaScript:
		addon = DEFAULT_ADDON || (DEFAULT_ADDON = require(__webpack_require__.ab + "build/Release/better_sqlite3.node"));

When I press rs without modifying the code, the value of __webpack_require__.ab (on my machine) is

'C:\Users\Christopher\Source\Repos\pic\.webpack\main/native_modules/'

And it's undefined when I have the problem on restart.
Maybe it's related to this, because that's to do with setting the __webpack_require__.ab value:

https://github.com/vercel/webpack-asset-relocator-loader/issues/97

IOW maybe the @vercel/webpack-asset-relocator-loader is not being re-run or something.
I can work-around the problem using their nativeBinding option which is described here:

https://github.com/WiseLibs/better-sqlite3/blob/master/docs/api.md#class-database

if you're using a complicated build system that moves, transforms, or concatenates your JS files, better-sqlite3 might have trouble locating its native C++ addon (better_sqlite3.node). If you get an error that looks like https://github.com/JoshuaWise/better-sqlite3/issues/534#issuecomment-757907190, you can solve it by using this option to provide the file path of better_sqlite3.node (relative to the current working directory).

So for example if my code looks like this then I don't get the error:
export function createSqlDatabase(filename: string): SqlApi {
  const options: sqlite.Options = {
    nativeBinding:
      "C:\\Users\\Christopher\\Source\\Repos\\pic\\.webpack\\main\\native_modules\\build\\Release\\better_sqlite3.node",
  };
  const db = sqlite(filename, options);

That's not ideal, especially when the application is packaged.
In summary I guess this problem related to the @vercel/webpack-asset-relocator-loader is not being re-run on restart.

Simple workaround that worked for me (same error when using @napi-rs/canvas): adding __webpack_require__.ab = __dirname + "/native_modules/"; at the very beginning of index.js (above the imports)
This reproduces the same path even if rs is used


Alerts - Block Reference Messages

Typing alert in an existing block would use that block as the alert message with a link to the block. Could also type in a block ref in the message for the same effect

DM Source

For this to work, this also must be true:

If I schedule an alert, but roam isn't open when the time is up, I should still see the alert when I do open roam.

For this to work, this also must be true:

If I schedule an alert, but roam isn't open when the time is up, I should still see the alert when I do open roam.


[BUG] chalk.hex crashes when color is not supported

On a terminal where color is not supported, when I run the following code:
console.log('supportsColor:', chalk.supportsColor);
chalk.hex('ff5f6d')('A');

I get the following output:
supportsColor: false

X:\Boris\gradient-string\node_modules\chalk\index.js:75
    const open = ansiStyles.color[levelMapping[level]][model].apply(null, arguments);
                                                      ^

TypeError: Cannot read property 'hex' of undefined
    at Function.<anonymous> (X:\Boris\gradient-string\node_modules\chalk\index.js:75:55)

I guess the expected result would be a white string (without any color), am I right?
N.B: as you can see, I run this on a Windows machine 😕

Duplicate of #176.


Allow trailing commas in labels macro

This small PR allows for trailing commas when using the labels! macro. It also tidies up the logic a little bit.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks!

CI failed

@overvenus PTAL


switch id creation to timestamp

Description
Fix the id creation on datasource tag and vsphere locations

Acceptance tests

[ ] Have you added an acceptance test for the functionality being added?
[ ] Have you run the acceptance tests on this branch?

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccAnxCloudVSphereLocationsDataSource'
$ make testacc TESTARGS='-run=testAccAnxCloudTagsDataSourceExists'

Release Note
Release note for CHANGELOG:

References

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

/ok-to-test sha=5d04f66

/ok-to-test sha=5d04f66

/ok-to-test sha=5d04f66

/ok-to-test sha=5d04f66

/ok-to-test sha=5d04f66

/ok-to-test sha=5d04f66


[BUG] Integration is using deprecated DEVICE_CLASS_* constants

Describe the bug
This custom integration uses deprecated DEVICE_CLASS_* constants in its codebase.
The DEVICE_CLASS_* constants have been deprecated and replaced in Home Assistant Core 2021.12 (over a year ago). I would highly suggest updating/migrating this integration to the new enums.
For example, for the device classes supported by the sensor platform, there is now a SensorDeviceClass enum. So if a sensor previously used the DEVICE_CLASS_ENERGY constant, it should now use SensorDeviceClass.ENERGY. Other platforms (like binary_sensor, and number) provide similar enumerations for their supported device classes.
The migration thus only consists of replacing constants with an enumeration member and is, therefore, very low impact and should be fairly straightforward.
If I can help resolve any questions regarding this change or migration, feel free to ask or respond to this issue. I'm happy to help!
Kindest regards,
../Frenck
Please complete the following information:

HASS version: 2021.12 and newer
Component version All
Router model [e.g. AX9000]
Router firmware version [e.g. 1.0.155 CN]

Fixed in release https://github.com/dmamontov/hass-miwifi/releases/tag/v3.0.0
@frenck thanks.

Thanks for addressing @dmamontov 👍
../Frenck


Need formal schema for build-info JSON documents

While this project has a java library for build-info metadata, it's also the best description of the build-info format for those of us interfacing with Artifactory using other languages/tools.
While the README.md has an example build-info JSON document, it's not really sufficient.  This week I've been writing a script to upload our build metadata to Artifactory, and it's been a constant cycle of trial and error in order to determine what objects are required and which are optional, the valid types and format of data values, etc. It would be useful if this project also provided a JSON schema definition which rigorously defined the build-info metadata.

Thanks for your input @johntconklin .
We'll try improving the readme. We'll also gladly accept contributions to the readme documentation.

I completed the first-draft of a JSON schema based on my experimentation and the existing documentation in README.md at work today.  I'm not sure it's 100% correct with regards to what fields are required and what fields are optional, especially with regards to issues and license check metadata (which I don't use), but it should be close enough, and you guys can help clarify the details.
Since I did this at work, I need to jump through some hoops in order to contribute, but I don't anticipate any problems getting approval.

Sure @johntconklin. That would be great. Thank you. Please submit what you have, and we'll go over it and correct if needed. Issues and License BTW are optional.

@eyalbe4, I've started on getting the management approvals I'll need to contribute this.
In the mean time, where would be a good place for the new build-info-schema.json file? Should I put it in the toplevel directory?  Or should I create a new doc/ or schema/ subdirectory?  If the longer term, if someone gets inspired and creates JSON schemas for all the Artifactory REST endpoints, it may make the most sense to create a single repository specifically for that...

@johntconklin, I think that for now, we can put it in the existing readme.md file, in a new section next to the one containing the existing build-info example. If needed, we will modify the documentation structure in the future following additional contributions.

@eyalbe4,
Before I raise a pull request, please take a look at the README.md
in my fork and let me know what you think.
Some notes on the build-info JSON schema.

Most string types do not define minimum or maximum sizes or
validation patterns.  For example, it's not clear to me whether
the "type" property of artifacts and dependencies can be arbitrary
strings, or if there is a list of acceptable types. Similarly, it's
not clear whether there is a fixed set of "scopes".

I've defined artifact and dependency objects to require a md5 hash,
a sha1 hash, or both.  That being said, I've been able to upload
build-info JSON without either, although Artifactory reports "No
path found (externally resolved or deleted/overwritten)", so this
may be considered too restrictive. If so, we can remove the some
of the complexity for these object types.

I haven't set additionalProperties to false, so objects with extra
properties not defined by the schema will still validate. I'm torn
on this one. Minor additions will still validate, but so will mistakes.

Object and data type descriptions were adapted from example in
README.md. Those that didn't have a description there, don't have
a description in the schema.

Since don't use licenseControl, buildRetention, issues, or
governance objects, I've marked every property as required.  This
may or may not be true.

We can address some of these issues before the changes are merged,
others can wait until afterwards.

I looked at the README.md at your fork. Looks good @@johntconklin!
Here are answers to your questions:

The type property of artifacts and dependencies can be every string. The same goes for scopes.
SHA1 and MD5 both should be required, because that's how Artifactory is able to perform operations (such as promotion)
on a build. Artifactory also uses the checksum to determine and display the path of of each artifact in the build UI.
Question: If you look at the "Build info json format", you'll see that it can include properties such as env vars and system
properties (in the exanple at the README - "buildInfo.env.JAVA_HOME". The "version", "name", "number" etc. are at the same
level of "properties" and not inside it. I think it should be corrected in the schema.
I'm not sure I understabd your question about the additionalProperties. Can you please clerify?
You're correct - not aall fields have a description. We can add them later.
As for the required fields, licenseControl and issues are good. In buildRetention however, only one of the following is required: either minimumBuildDate or count (it is okay to send both).

Thanks @eyalbe4.
I've updated my fork in response to your questions.

I've changed the buildRetention object schema to require the count and/or minimumBuildDate properties.

There can be some confusion because the build-info JSON and the JSON schema both use the property "properties".
That being said, my first version didn't support the module "properties" property because I wasn't sure how to represent the open-ended set of properties that can be provided. Since then, I've re-read the JSON schema specification and figured out how to use "patternProperties" to match all property names and constrain the values to strings.
I've added this to the schema.

If additionalProperties is set to false in the build-info object definitions, a build-info JSON document will fail to validate if any additional properties are specified. There are cases where this could be considered a good thing, and there are other cases where this could be considered bad.
For example, suppose the user has a typo in the code (or template) that they're using to generate build-info and instead of "buildRetention" they have "bldRetention". This would validate, and the user may not realize Artifactory is not taking the desired build retention policy into account. But if you added a new "foo" property in a future Artifactory release, the schema wouldn't necessarily have to be updated to account for that new property and build-info JSON documents that used it would still validate.
My personal preference is to set additionalProperties to false so that the JSON schema validation is strict, as I feel that's more important than being relaxed for future-proofing. If you every add additional properties, it should be easy enough for you (or me) to update the schema to match.

Finally, do you really think both MD5 and SHA1 hashes should be required, or should it be like "count" and "minimumBuildDate" where one or the other or both are required?  My experiments with Artifactory show that it's happy with just one hash.

Thanks for your feedback.

Is the version property for agent and buildAgent objects required?  I noticed that the test file "./build-info-extractor/src/it/resources/org/jfrog/build/client/testfile.txt" contains a buildAgent object without a version.  BuildAgent.java seems to handle this as well.

Hi @johntconklin,

I also think it is better to be stricked to avoid mistakes in the json, and therefore
set additionalProperties to false.

Already mentioned this in a previous message. Just pasting this
again because I saw it hadn't yet been changed in your repository:
If you look at the "Build info json format", you'll see that it can include properties such as env vars and system properties (in the exanple at the README - "buildInfo.env.JAVA_HOME". The "version", "name", "number" etc. are at the same
level of "properties" and not inside it. I think it should be corrected in the schema.

We can leave only SHA1 as required, and allow not to add the MD5.
Artifactory uses the SHA1 to perform operations on the build artifacts and dependency. MD5
is used mostyl for Maven repositories, so I guess this can be okay.

I've never tried deploying the build-info json without the buildAgent or version.
My concern is that the UI of Artifactory will be negatively effected by this. I suggest
you give it try and eploy without those sections. If the build UI for this
specific build in Artifactory look okay, then I guess we can leave this as not required.

Hi @eyalbe4,
I think we're very close now.

I've changed the schema to set "additionalProperties" to false on all objects.
Thanks for repeating that. I didn't notice that there is a "properties" property at the top level as well as for each module.  I've changed the schema so the "properties" property can be provided at either location.
I've changed the schema to make both MD5 and SHA1 required properties of attributes and dependencies objects. It is generally easier to relax this in the future if it turns out to be too strict, than it will be to tighten it if it's too loose.
When testing the schema with ./build-info-extractor/src/it/resources/org/jfrog/build/client/testfile.txt, I discovered that it defined a "LicenseViolationRecipients" list in addition to "licenseViolationsRecipientsList".  I added the new property, but additional changes are probably necessary to indicate whether one or the other or both are required.
I've left the "version" property of "agent" and "buildAgent" objects as required.  However, this means that testfile.txt does not validate, as it's missing "version" in the "buildAgent" object definition.

Looks really good @johntconklin!

Either licenseViolationRecipients or licenseViolationsRecipientsList should be used.
Artifactory actually takes licenseViolationsRecipientsList (which is a Space-separated string) and turns it into licenseViolationRecipients
(a string array), so one of them should be mandatory.

I think that "properties" is duplicated here:

  "properties": {
    "properties": {
      "type": "object",
      "description": "Environment variables and properties collected from the CI server",
      "patternProperties": {
        "^.+$": {
          "type": "string"
        }
      }
    },

Shouldn't it be changed into?
  "properties": {
    "type": "object",
    "description": "Environment variables and properties collected from the CI server",
    "patternProperties": {
      "^.+$": {
        "type": "string"
    }
  },

Hi @eyalbe4
The "properties" keyword is confusing because it is both a property in the JSON-schema schema and the build-info schema.  The "outer" properties is part of the JSON-schema schema, where it defines the list of properties that are allowed in the build info schema (e.g. "properties", "version", "name", "number", "type", "buildAgent", etc.).  The "inner" properties is part of the build-info schema itself, where we define the type of properties that are provided by the CI server.
Since this is an open ended set of property names, I'm using a "patternProperties" with a regex to say that any string is allowed (we can tighten the regex if Artifactory only supports a subset, e.g. only alphanumeric chars, etc.)
I can move the "inner" properties definition so it's not immediately adjacent to the "outer" properties definition if you think that's warranted.  I left it first because the example build-info json earlier in the file also has it first.

I've updated the schema to handle the licenseControl object's licenseViolationRecipients and licenseViolationsRecipientsList properties.
With this change, I'm pretty much at the end of what I can do with the schema definition.
However If you have additional examples you can share, especially examples from each of your supported plugins, and examples that provide "licenseControl", "governance", and "issues" objects, I'm willing to run them through a schema validator and fix any remaining nits to ensure that the schema represents reality.

@johntconklin, thanks again for the great work. If you send your mailing address to<EMAIL_ADDRESS>we'll make sure to send you a JFrog T-shirt.
I think you can submit the pull request (please make sure to sign JFrog CLA so that I can merge the new content.

Hi @eyalbe4.  I've executed the CLA.  No worries on the T-Shirt, as I received one at a recent meetup at jFrog's Santa Clara office.

https://github.com/JFrogDev/build-info/pull/83 merged.

Hi Guys,
I'm having some odd problems related to this.  I am uploading a buildinfo with some artifacts, when I navigate to my artifact it shows my new "build" in the builds tab list, yet if I try to go the other way and browse the modules from the new "build" I get "(externally resolved or deleted/overwritten)" in the modules list (file names are correct).
My buildinfo was uploaded with correct sha1, md5 and name for each artifact item.  It seems odd that the relationship has been added in one direction and not the other. If I'd got it wrong I'd have expected neither direction.
Really sorry if this is the wrong place to ask this.
Thanks,

I encountered the same problem. It turns out you also need to have the build.name and build.number properties set on the uploaded artifact itself. This requirement wasn't in the Artifactory REST API documentation at the time, but is now.

@johntconklin thank-you! that worked perfectly!


Allow the inline diff editor to be centered.

This PR fixes #97165
The issue here was that while DiffEditorInput is an instance of SideBySideEditorInput, it still allows for inline editing based on the config value diffEditor.renderSideBySide.
My proposed fix involves handling that case and centering appropriately, as well as calling Layout.centerEditorLayout when the configuration changes since centering behaviour is now contingent on the above configuration option.
One thing to note is that this will also cause the layout to be centered/uncentered when workbench.editor.centeredLayoutAutoResize changes, since we're also using this config option to determine centering behaviour. I think the fact that we weren't already updating based on config changes counts as a bug as well.
To test these changes use the test case outlined in the issue(#97165)

Thank you very much for this PR. I tested the changes and it works great. Thus merging in.


Setting "focused" property true and closing app does not show keyboard

See https://github.com/eclipsesource/tabris-js/issues/925

Closing as duplicate of #925


netbox_3_6: init, netbox_3_3: drop

Description of changes
Depends on #252852.
Draft as the tests OOMs… Please feel free to take over as I am doing this on vacations :D.
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Done in https://github.com/NixOS/nixpkgs/pull/257047


940 | Distinct Subsequence II | C++

Distinct Subsequence II -
What will change - Adding new code
Type of Issue - Soln for the problem
Please add/delete options that are not relevant.

[x] Adding New Code

Programming Language
Please add/delete options that are not relevant.

[x] C++

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

Hi, can you assign this to me?

Hi, can you assign this to me?

Hi, sorry but I opened this issue for myself.

Ok, no problem


Jeji/sdkforskill

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please add REST spec PR link to the SDK PR
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

Can one of the admins verify this patch?

#sign-off

@jeji1101 please reference the rest spec PR

The corresponding swagger spec PR is: https://github.com/Azure/azure-rest-api-specs/pull/3386. Thanks.

@azuresdkci Retest this please

@jeji1101 please pull latest changes from upstream and update the PR

@brjohnstmsft could you please update the search-preview branch with the latest psSdkJson6 in order to fix these build issues

@azuresdkci Retest this please

@jeji1101 Please update your branch with remote search-preview and update the PR

@dsgouda I've updated the branch. Please do not merge until I've had a chance to review it.

@jeji1101 would you like to close this in favor of https://github.com/Azure/azure-sdk-for-net/pull/4609

@dsgouda @jeji1101 Fine by me.


Raspbian Stretch Lite

Have tested raspi-sump for a while now, and has been working great. Tried installing it a smaller and more lightweight build today using Raspbian Stretch Lite, but that doesn't work.
Time formatting doesn't work, graph line is not displayed and the graph doesn't update with cronjob. Is there a known issue with some dependencies and Raspbian Lite?
Raspberry Pi 3
Python version 3.5.3
Running lighttpd on the same PI

I have always used Raspbian Lite .  Did you use no-binary all when
installing?  See the install doc.
On Sun, Jun 9, 2019, 2:52 PM bjornarfonn<EMAIL_ADDRESS>wrote:

Have tested raspi-sump for a while now, and has been working great. Tried
installing it a smaller and more lightweight build today using Raspbian
Stretch Lite, but that doesn't work.
Time formatting doesn't work, graph line is not displayed and the graph
doesn't update with cronjob. Is there a known issue with some dependencies
and Raspbian Lite?
Raspberry Pi 3
Python version 3.5.3
Running lighttpd on the same PI
[image: screengrab raspi-sump]
https://user-images.githubusercontent.com/19434691/59162841-407d8080-8af8-11e9-81a4-fca1001e8b0a.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/alaudet/raspi-sump/issues/47?email_source=notifications&email_token=ABZWS5YSS5A66QCY26242ALPZVGO3A5CNFSM4HWMUKXKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GYOME5A,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABZWS57GNFZZ7JMTQE7INGDPZVGO3ANCNFSM4HWMUKXA
.

Yes, installed as per install doc. Formatted the sd card and re-installed everything again, still the same issue? Anything you could point me too in terms of troubleshooting?

So after some trials and errors, it seems that it failed to start running the process? I tried changing /etc/rc.local adding sudo;
sudo /usr/local/bin/rsump.py &
It seems to be producing charts now, will try some more testing. Is this something you have any experience with?

usually with stretch you don't need to run sudo.  you def don't need to run it from rc.local as you are already starting the process with elevated priviledges at that point.
What happens if you kill the process and then try and start it without.
sudo killall 09 rsump.py
/usr/local/bin/rsump.py &

hmm... i spoke to soon when i said i got it running. It did one graph and that was it.
removed the sudo as your comments states, its starting with privileges.
Trying to killall gives me this output;
pi@raspberrypi:~/raspi-sump/logs $ sudo killall 09 rsump.py
09: no process found
rsump.py: no process found
Starting it manually using /usr/local/bin/rsump.py &
then trying to generate new graph by doing $ rsumpwebchart.py does nothing.
Starting it manually and stopping it again gives me this output;
pi@raspberrypi:~/raspi-sump/logs $ sudo killall 09 rsump.py
09: no process found
rsump.py: no process found
[1]+  Done                    /usr/local/bin/rsump.py
My logs folder is also empty, so there is no help there

try running it not as a process to start.  Simply run rsump.py
Does it create a csv file in /home/pi/raspi-sump/csv?
What subfolders are in you /home/pi/raspi-sump/csv file?

It works when adding rsump.py to crontab with 1minute intervals. It's a weird issue, as basically the startup file is doing the same thing, the difference being its starting as a continual process rather than starting occasionally.
So my crontab is running rsump.py every minute, that produces a sample from the sensor every minute, and then I am generating a chart every 10 minutes (will change this when deployed outside) this all seems to work. So, I guess I'm happy with this so far.
*/1 * * * * /usr/local/bin/rsump.py
*/10 * * * * /usr/local/bin/rsumpwebchart.py
*/5 * * * * sudo /usr/local/bin/rsumpmonitor.py

If you launch it as a process manually does it work as intended?  Or is it
just when you use rc.local?
On Mon, Jun 10, 2019, 3:59 AM bjornarfonn<EMAIL_ADDRESS>wrote:

It works when adding rsump.py to crontab with 1minute intervals. It's a
weird issue, as basically the startup file is doing the same thing, the
difference being its starting as a continual process rather than starting
occasionally.
So my crontab is running rsump.py every minute, that produces a sample
from the sensor every minute, and then I am generating a chart every 10
minutes (will change this when deployed outside) this all seems to work.
So, I guess I'm happy with this so far.
*/1 * * * * /usr/local/bin/rsump.py
*/10 * * * * /usr/local/bin/rsumpwebchart.py
*/5 * * * * sudo /usr/local/bin/rsumpmonitor.py
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/alaudet/raspi-sump/issues/47?email_source=notifications&email_token=ABZWS53JYTDOT3YK3QFQI43PZYCXNA5CNFSM4HWMUKXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXJGL3Y#issuecomment-500327919,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABZWS5YDD3P4UQNEQQVO5DTPZYCXNANCNFSM4HWMUKXA
.


Large message support

Right now large messages are not supported.
The example below is a message of 3MB. This size is not correct, the message text is nog vissible.

See #592

See @SeanFeldman comments


Improved test coverage for runner.js (issue #161)

100% Statement, function and line coverage for lib/runner.js.
Covers the case where Runner is not called with "new".

@sohamkamani That build failure is almost certainly not your fault, so don't worry about that.

Failure noted in the tracking issue.

@sohamkamani Awesome! Keep 'em coming :D