Add Claude 3 and other models to the config.toml

Add Claude 3 and other models to the config.toml

LLM_MODEL="claude-3-haiku-20240307"
and
LLM_API_KEY="sk-xxx"
worked for me, however the Claude API's have pretty tight rate limits so it was mostly unusable with OpenDevin for any coding tasks.
Claude on bedrock works a treat.

See https://github.com/OpenDevin/OpenDevin/issues/332 for rate limiting

LLM_MODEL="claude-3-haiku-20240307" and LLM_API_KEY="sk-xxx"
worked for me, however the Claude API's have pretty tight rate limits so it was mostly unusable with OpenDevin for any coding tasks.
Claude on bedrock works a treat.

how did you run it on bedrock ? what does your command to run docker look like ?

I have not run on bedrock--I just know that it's supported

i'm running this but running into all kinds of error

using main branch works fine, but can someone please add requirement boto3 ?
Oops. Something went wrong: BedrockException - Traceback (most recent call last): File "/app/.venv/lib/python3.12/site-packages/litellm/llms/bedrock.py", line 712, in completion client = init_bedrock_client( ^^^^^^^^^^^^^^^^^^^^ File "/app/.venv/lib/python3.12/site-packages/litellm/llms/bedrock.py", line 575, in init_bedrock_client import boto3 ModuleNotFoundError: No module named 'boto3'

the error your seeing suggests that boto python package isnt installed into the docker instance ?
I got this running on an earlier version of Open Devin, not sure if its changed since but here is a snip of my config.toml

I will see if i can give it a go tomorrow with the latest and see how it runs, but from looking at the repo this has changed quite a bit since when i was testing 3 weeks ago

your settings look like its passing the correct env variables through to the container, so i suspect its because of the missing package, also check the version of boto3 on the container in case this is an old one from before the bedrock runtime was available.
Hope this helps, will update tomorrow once i have some time to play.

thanks, this worked for me :
docker run
-e  AWS_ACCESS_KEY_ID
-e AWS_SECRET_ACCESS_KEY
-e AWS_REGION_NAME
-e LLM_MODEL="bedrock/anthropic.claude-3-sonnet-20240229-v1:0"
-e WORKSPACE_MOUNT_PATH=$WORKSPACE_DIR
-v $WORKSPACE_DIR:/opt/workspace_base
-v /var/run/docker.sock:/var/run/docker.sock
-p 3000:3000
-e SANDBOX_TYPE=exec
-v $HOME/.aws:/root/.aws
-v /home/jdesa/Agent/llm_lite_bedrock.py:/tmp/llm_lite_bedrock.py
ghcr.io/opendevin/opendevin:main
/bin/bash -c "pip install boto3 &&
cp /tmp/llm_lite_bedrock.py /app/.venv/lib/python3.12/site-packages/litellm/llms/bedrock.py &&
uvicorn opendevin.server.listen:app --host <IP_ADDRESS> --port 3000"


Not able to commit after deleting some files

After deleting some files, I'm not able to do commit using the plugin because it says that there are no changes to be committed. I have not using the command git rm (not even using the plugin), I just deleted from the project tree.

Were those files staged and or already created in the git history? I can't replicate this.


meson: skip long-running tests

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[ ] Ready to merge

Summary

What does the PR accomplish, why was it needed?
Change meson tests to only run unit tests. The full test suite is taking nearly 2 hours in ptest pipelines.
Change Log

Change meson to only run unit tests

Does this affect the toolchain?

YES
Test Methodology

Pipeline build id: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=535530&view=results

After discussing with @PawelWMS , I'll keep the full test suite for now to maximize the test coverage. Will instead focus on general performance improvements to the package test infrastructure/pipelines.


New .edn file.

Heath! We will need to verify the instructions work for your team.

Have to override the review or Acrolinx won't work.

Docs Build status updates of commit a6d9a7e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.acrolinx-config.edn
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Create yow

/joke
/bark
/size

@objectiveous:

In response to this:

/joke
/bark
/size

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@objectiveous: What did one plate say to the other plate? Dinner is on me!

In response to this:

/joke
/bark
/size

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Exceptions should log to error

https://github.com/logstash-plugins/logstash-output-riemann/blob/master/lib/logstash/outputs/riemann.rb#L163
It's logging to debug, which is not helpful if there are exceptions.

Agreed.  I will fix this.

Why was this closed?

it was fixed by commit 04bea14


Offense abilities & special moves

I'm still not sure how I want to add these in to the UI, but certain abilities change type matchups, and certain moves bypass the normal type matchups. Even though Pokemon can only have one ability, I think making all of these multiple choice options would be good since the Offense page can be used to model a single attacker OR an entire team attacking, unlike the defense page where there needed to be a fully separate mode.

Tinted Lens (ability)
Scrappy (ability)
Freeze-Dry (move)
Flying Press (move)

Added it to the list, thanks!

Also Thousand Arrows also counts under the same umbrella as Flying Press and Freeze Dry.


hello

hello I would like to help me with a question I have, I would like to find the contact id in whatsapp to which you are receiving the message or how to automate the message so as not to click on the contact
Thank you!. :)

Hi LGudi,
Whatsapp Web does not provide a unique ID to each of your conversations. However, I will update my code next with how I am doing it. Remind me if I have not messaged you back.

Thanks, I'll wait for your message to review the update.

Hii LGudi,
Could you help me with this error, whenever i run the script i encounter this error
('/google bots', '14-05-28')
Command args: ['google', 'bots']
Message: no such element: Unable to locate element: {"method":"xpath","selector":"//*[@id="main"]/header/div[3]/div/div[2]/span/div/div/ul/li[1]/input"}
(Session info: chrome=73.0.3683.86)
(Driver info: chromedriver=73.0.3683.68 (47787ec04b6e38e22703e856e101e840b65afe72),platform=Windows NT 10.0.17134 x86_64)
('bot failed to retrieve search content, try again...', '14-05-42')

@mark104478 Issues should be fixed now


Add parsing char 0x1F in artist_mbids

Seems some strings are formed with unicode characters and fails to submit:
Example, where it failed due to \u001f:
[2024-11-11 08:41:26.020 -05:00] [DBG] [20] Jellyfin.Plugin.ListenBrainz.ListenBrainzApi: Got response:
Status: BadRequest
Data: "{\"code\":400,\"error\":\"artist_mbids MBID format invalid.\",\"track_metadata\":{\"additional_info\":{\"artist_mbids\":[\"06d98c74-1861-4717-86b2-00c0a8b863ce\u001f4dc77d86-5ecf-460b-b01d-41e8f1272b6e\"],\"duration_ms\":358000,\"media_player\":\"Jellyfin\",\"recording_mbid\":\"e9c4280a-3665-45b9-80b9-0dada4e68bd3\",\"release_group_mbid\":\"7bfc2d50-d3f2-332e-9956-d706e5a69949\",\"release_mbid\":\"3e380934-aa90-4887-93df-8d8bb7487fe0\",\"submission_client\":\"ListenBrainz plugin for Jellyfin\",\"submission_client_version\":\"<IP_ADDRESS>\",\"tags\":[],\"track_mbid\":\"39732df6-5a80-3b36-93b0-1869451e3dd7\",\"tracknumber\":3},\"artist_name\":\"System S.F. feat. Anna\",\"release_name\":\"V-RARE SOUNDTRACK 5 - DDRMAX2 -Dance Dance Revolution 7thMIX-\",\"track_name\":\"Look To The Sky (Trance Extended Mix)\"}}
"

This PR now fixes it.
I'm not really sure why these issues happen, but glad to submit this quick PR fix to solve them.

Sorry for late reply, lots of stuff going on lately...

I'm not really sure why these issues happen, but glad to submit this quick PR fix to solve them.

I'm not sure if these tag values are saved as Jellyfin reads them or if Jellyfin does some parsing before saving them. Anyway, it'll be probably for the best to make this configurable, so the Jellyfin admins can quickly fix it - instead of waiting for a pull request to be merged.

Created an improvement issue for making this configurable. In the meantime, let's merge this.
@moisespr123 Thank you and sorry it took so long.


Feature/tests

added tests and coverage reporting

Coverage increased (+19.5%) to 51.642% when pulling e19399563dd468a1b681b9ceb87d57b7cde85a04 on feature/tests into 569c668e9d01e6c6f540fdd03fe3b9b9d2820afd on development.

Codecov Report

Merging #3 into development will increase coverage by 20.5%.

@@               Coverage Diff               @@
##           development       #3      +/-   ##
===============================================
+ Coverage        31.68%   52.18%   +20.5%
===============================================
  Files               10       10
  Lines              344      343       -1
  Branches            54       54
===============================================
+ Hits               109      179      +70
+ Misses             235      164      -71

Impacted Files
Coverage Δ

samples/istanbul-test.js
0% <ø> (ø)
:white_check_mark:

lib/strategies/api-strategy-config.js
100% <100%> (+62.5%)
:white_check_mark:

lib/utils/token-util.js
100% <100%> (+43.47%)
:white_check_mark:

lib/strategies/webapp-strategy-config.js
100% <100%> (+67.21%)
:white_check_mark:

Continue to review full report at Codecov.

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

Coverage increased (+19.5%) to 51.642% when pulling 868269d642733a6afd166efbc57cd085644fd827 on feature/tests into 569c668e9d01e6c6f540fdd03fe3b9b9d2820afd on development.


Instantiate job store

Based on #49
This PR:

Finally makes up cabbages's mind regarding App instanciation: it takes an instance of JobStore
Adds version and other metadata at the top level
Add building of the docs in the CI, we realized it was missing

Codecov Report

Merging #50 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #50   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          12     14    +2
  Lines         381    440   +59
  Branches       32     41    +9
=====================================
+ Hits          381    440   +59

Impacted Files
Coverage Δ

cabbage/postgres.py
100% <100%> (ø)
:arrow_up:

cabbage/store.py
100% <100%> (ø)
:arrow_up:

cabbage/exceptions.py
100% <100%> (ø)
:arrow_up:

cabbage/retry.py
100% <100%> (ø)

cabbage/tasks.py
100% <100%> (ø)
:arrow_up:

cabbage/worker.py
100% <100%> (ø)
:arrow_up:

cabbage/jobs.py
100% <100%> (ø)
:arrow_up:

cabbage/app.py
100% <100%> (ø)
:arrow_up:

cabbage/__init__.py
100% <100%> (ø)
:arrow_up:

cabbage/metadata.py
100% <100%> (ø)

... and 3 more

Continue to review full report at Codecov.

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


Initialize s:pos in sourcing

When you calls :Denite miniyank and do the action put before any <Plug>(miniyank-*) has not been called, you see this bug below.
bug report
[denite] Traceback (most recent call last):
[denite]   File "/Users/delphinus/.cache/dein/repos/github.com/Shougo/denite.nvim/rplugin/python3/denite/rplugin.py", line 63, in do_map
[denite]     return do_map(ui, args[1], args[2])
[denite]   File "/Users/delphinus/.cache/dein/repos/github.com/Shougo/denite.nvim/rplugin/python3/denite/ui/map.py", line 20, in do_map
[denite]     return MAPPINGS[name](denite, params)
[denite]   File "/Users/delphinus/.cache/dein/repos/github.com/Shougo/denite.nvim/rplugin/python3/denite/ui/map.py", line 65, in _do_action
[denite]     return denite.do_action(name, is_manual=True)
[denite]   File "/Users/delphinus/.cache/dein/repos/github.com/Shougo/denite.nvim/rplugin/python3/denite/ui/default.py", line 86, in do_action
[denite]     self._denite.do_action(self._context, action_name, candidates)
[denite]   File "/Users/delphinus/.cache/dein/repos/github.com/Shougo/denite.nvim/rplugin/python3/denite/parent.py", line 63, in do_action
[denite]     return self._get('do_action', [context, action_name, targets])
[denite]   File "/Users/delphinus/.cache/dein/repos/github.com/Shougo/denite.nvim/rplugin/python3/denite/parent.py", line 84, in _get
[denite]     return self._put(name, args)
[denite]   File "/Users/delphinus/.cache/dein/repos/github.com/Shougo/denite.nvim/rplugin/python3/denite/parent.py", line 80, in _put
[denite]     return self._child.main(name, args, queue_id=None)  # type: ignore
[denite]   File "/Users/delphinus/.cache/dein/repos/github.com/Shougo/denite.nvim/rplugin/python3/denite/child.py", line 83, in main
[denite]     ret = self.do_action(args[0], args[1], args[2])
[denite]   File "/Users/delphinus/.cache/dein/repos/github.com/Shougo/denite.nvim/rplugin/python3/denite/child.py", line 260, in do_action
[denite]     if action['func']
[denite]   File "/Users/delphinus/.cache/dein/repos/github.com/bfredl/nvim-miniyank/rplugin/python3/denite/kind/miniyank.py", line 14, in action_put
[denite]     data = self.vim.call("miniyank#drop", data,  'p')
[denite]   File "/Users/delphinus/Library/Python/3.7/lib/python/site-packages/pynvim/api/nvim.py", line 299, in call
[denite]     return self.request('nvim_call_function', name, args, **kwargs)
[denite]   File "/Users/delphinus/Library/Python/3.7/lib/python/site-packages/pynvim/api/nvim.py", line 182, in request
[denite]     res = self._session.request(name, *args, **kwargs)
[denite]   File "/Users/delphinus/Library/Python/3.7/lib/python/site-packages/pynvim/msgpack_rpc/session.py", line 102, in request
[denite]     raise self.error_wrapper(err)
[denite] pynvim.api.nvim.NvimError: b'Vim(call):E121: Undefined variable: s:pos'
[denite] Please execute :messages command.

This patch fixes this.

Thanks. Though s:pos must be set in miniyank#drop(), because the old value from <Plug>(miniyank-*) might be bigger than zero.


Use builder instead of constructor in demo

The last character of the commit subject must not be a dot.

Fixed.


Latest obsidian update causes incomplete files

This issue is a duplicate of #170, however it is now present in the latest stable release of obsidian (v1.4).

The fix for this is complete, however I need to clean up some other stuff before I can make a new release. My goal is to release the fix on monday (along with a bunch of super exciting features)

Looking forward to the fix on this one! Just found your plugin since this bug came to be in the update and very excited to put this to good use!

It's coming!

Also expect this.....

Thanks!  I hope you understand why it's taking me a little bit longer than expected 😅 but it is on it's way and I am actually working on it as I write this

Thanks for the plugin @KosmosisDire !!!

use the previous version of obsidian (1.3.7)

I didn't find any means how to downgrade Obsidian. Is there any way to download older binaries for macos?

There are downloaders for each version here: https://github.com/obsidianmd/obsidian-releases/releases

I tried to use the older version of Obsidian (1.3.7) but It still produce an incomplete output.

I tried to use the older version of Obsidian (1.3.7) but It still produce an incomplete output.

Can you check if maybe it auto updated itself so that you are actually using the latest version again?

I tried to use the older version of Obsidian (1.3.7) but It still produce an incomplete output.

Can you check if maybe it auto updated itself so that you are actually using the latest version again?

Thank you so much! It turns out It automatically updates itself upon running so I had to turn off my internet temporary to disable the auto-update option.

I didn't find any means how to downgrade Obsidian. Is there any way to download older binaries for macos?

Check https://forum.obsidian.md/t/obsidian-versions-how-to-go-back/44437/3 (haven't tested myself but looks valid)

Thanks @stefanpausch, the link to .asar files was the crucial piece I was missing for obsidian downgrade. I needed to generate HTML today so I downloaded 1.3.7 renamed the obsidian-1.4.5.asar so that it doesn't get picked up by Obsidian automatically.
Thanks a lot, guys! Have a nice day.

I am packaging up the new version now! Prepare yourselves for an update! :)

New update is out everyone! Enjoy! :)

Hi, yes I have removed the release because it would not load for anyone except me which is very strange. So I have to reevaluate and send out a new release

Okay eveybody, the release is back out and I have verified that it does work! Let me know if you have any problems though :)


chore(userspace/falco/app): print all supported plugin caps

What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
/area engine
What this PR does / why we need it:
The newest plugin caps where not accounted for when printing plugin infos.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
chore(userspace/falco/app): print all supported plugin caps

/milestone 0.35.0

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

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

LGTM label has been added.  Git tree hash: 08b00aae3be02b586093682f061d8705fedc8b53

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce,leogr]

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,jasondellaluce,leogr]

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


Tomee 2746

Hello,
Just updated tomcat version to 8.5.49 in pom.xml.
Alexandre

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Hi,
I think, that the target branch for this PR should be 7.1.x and not the master as this branch uses tomcat 9.
In addition, it might be possible, that your forked repo is a bit out of sync. I would recommend, that you merge the latest changes of the related branches into your fork and then reopen the PR targeting the right branch in this repo.
Best,
Richard

Looks like this is pointing at the wrong branch as @rzo1 notes. I'll pull commit 5a8615f over to 7.1.x and backport to 7.0.x.

Done:
https://github.com/apache/tomee/commit/64aa743bd0131d3ee1939121c349d886e83d558a
https://github.com/apache/tomee/commit/e0b510a07a1ef86aa54418066d083f114871ecb3
Many thanks!


How change the wrong name of repo?

Hi,
Thank you for your project.
I'm the owner of the ng2-dnd (https://github.com/akserg/ng2-dnd) project.  Someone added my project into your resource with the wrong name and url:

Can we somehow fix it with right information:

Name: ng2-dnd
Npm repo: https://www.npmjs.com/package/ng2-dnd

Regards,
Sergey.

Hi,
Thanks for the nice library.

Yes in your case adding the correct URLs to the same category should work.
I.e. add the entry (https://github.com/akserg/ng2-dnd, https://www.npmjs.com/package/ng2-dnd) to Drag and Drop.

For future readers where both the GitHub URL and the npm URL is wrong;
You shouldn't directly add the entry with both corrected GitHub URL and npm URL. (Otherwise the library will end up having two entries.)
Instead following would work;

Add the entry with the correct GitHub URL and the old/current npm URL to the same category. I.e. add (https://github.com/org/correct-name, https://www.npmjs.com/package/wrong-name) to Same Category.
Add the entry with the correct GitHub URL and the correct npm URL to the same category. I.e. add (https://github.com/org/correct-name, https://www.npmjs.com/package/correct-name) to Same Category.

Regards,
Romuald.

See previous answer.


Cookie::expire & Cookie::forget Not recognised by IDE

Laravel Version: v9.18.0
PHP Version: 8.1.6
PHPStorm Version: 2021.3.3
Laravel IDE Plugin: 0.15.4

Description:
I am trying to delete a Cookie by using Cookie::expire($cookie_name) of the \Illuminate\Support\Facades\Cookie class.
It works as expected, but PHPStorm doesn't recognise these Methods. I tried to reindex the project but that didn't solve the issue. Warning:  Method 'expire' not found in Illuminate\Support\Facades\Cookie
Steps To Reproduce:

Create a new Composer Project in PHPStorm with the laravel/laravel package.
Make a Route to create a cookie using  \Illuminate\Support\Facades\Cookie::queue(...)
Make another Route to expire/delete the Cookie using \Illuminate\Support\Facades\Cookie::expire('SAME_COOKIE_NAME')

Admire PHPStorm complaining, that there is no expire Method on the Cookie Facade.

Have you tried the cookie()->expire('cookieName') method for this?

Hi @selcukcukur. YESS! IDE Intellisense works using the cookie() helper function. Thank you for this tipp! I'm wondering why this is nowhere mentioned in the official laravel docs.

@wavedeck I don't have clear information on this subject, it may have been overlooked.

Façades provides a way to proxy static method calls to an instance resolved from the container. Therefore they don't contain the underlying methods themselves and IDE cannot guess which methods it proxies without aids such as dokblocks or shallow classes that replicate the inner instance.
A IDE, as I am writing this, will resolve from the Cookie façade, in addition to the methods already defined in it, the methods: getQueuedCookie(), unqueue() and queue(), as the three of them are defined in the Cookie façade's class docblock:
https://github.com/laravel/framework/blob/4d46bda6f19d490080512fa053065081f737bf2f/src/Illuminate/Support/Facades/Cookie.php#L5-L12
This methods don't exist in the Cookie façade class definition, but a call to each of them is proxied to the underlying \Illuminate\Cookie\CookieJar instance, as noted on the @see \Illuminate\Cookie\CookieJar docblock tag above.
But \Illuminate\Cookie\CookieJar defines many other public methods, such as the expire() and forget() you noticed as not recognized by your IDE.
This is why packages such as https://github.com/barryvdh/laravel-ide-helper exist. To create shallow class stubs to help IDE resolve façade references, among other things such as a model field, that in the Eloquent ORM are not defined before hand, and as such an IDE won't suggest to autocomplete them automatically.
If you search previous PRs, there a several PRs that progressively adds missing public methods from a façade's underlying instance  to a façade class definition, to provide IDE autocompletion without the need to install an additional package.
If you follow this search link: https://github.com/laravel/framework/pulls?q=is%3Apr+is%3Amerged+docblock+facade you will see most PRs in the results just add missing public methods to a Façade's class definition docblock. And I am sure many other PRs doing the same are not listed by this query string.
There was a discussion some years ago if this docblocks should be maintained in sync with their underlying instances counterpart's public methods by maintainers, or by the community. And it was decided they would be added by demand from PRs contributed by the community.
The reason the cookie() helper works as you'd expect, is that the cookie() helper's docblock informs the IDE its return type is a \Illuminate\Cookie\CookieJar instance, so the IDE can auto-guess the methods:
https://github.com/laravel/framework/blob/4d46bda6f19d490080512fa053065081f737bf2f/src/Illuminate/Foundation/helpers.php#L293-L307
As such, an IDE not being able to autocomplete a method proxied by a façade, is not a bug. And even if your IDE complains it cannot resolve a method, your code would still work, again not rendering it as a framework's bug.
I do understand the benefits of having autocompletion, and code inspection from an IDE automatically working. I can suggest you 4 alternatives here:

Contribute a PR adding the missing public methods from the \Illuminate\Cookie\CookieJar to the Cookie façade class definition docblock. This a very nice first time contribution =)
Use a third-party package such as https://github.com/barryvdh/laravel-ide-helper to provide your IDE with the shallow stubs it needs to properly autocomplete and inspect code
As you said you are using PHPStorm, you can consider installing a plugin that helps with this, such as Laravel Idea. Note this is a paid plugin
Open a feature request within your IDE issue tracker asking them to add to the IDE code inspection engine the ability to resolve Laravel's façade proxy calls.

A good read about the matter, is the documentation page about Façades:
https://laravel.com/docs/9.x/facades
Hope this helps you out. Happy coding =)

@rodrigopedra That's a great explaination why things are as they are. Thank you for the Tip that other IDE Plugins might help with that, i'll install one right now ;)

You're welcome! Back in the days I started with Laravel I had the same doubts... Have a nice day =)


org.openrewrite.java.RemoveUnusedImports should not removed imports for public static inner class usage

org.openrewrite.java.RemoveUnusedImports doesn't appear to spot static public inner class usage that's used with wildcard imports statements.
What version of OpenRewrite are you using?
I am using version: 7.40.6
What is the smallest, simplest way to reproduce the problem?
Consider the following class
package com.a.b.c;
public final class ParentBaseClass {
  public static abstract class BaseImplClass {
     void foo() {
      }
  }
}

Which is then used in the following class
import com.a.b.c.ParentBaseClass.*
import java.util.List;
public class MyClass extends BaseImplClass {
   @Override
   public void foo() {
   }
}

What did you expect to see?
import com.a.b.c.ParentBaseClass.*
public class MyClass extends BaseImplClass {
   @Override
   public void foo() {
   }
}

What did you see instead?
public class MyClass extends BaseImplClass {
   @Override
   public void foo() {
   }
}

Hi, thanks for reporting this issue! Would you be open to contribute to write a unit test for it or even a fix?

Confirmed with this (slightly different) test.
@Test
void nestedImports() {
    rewriteRun(
      java(
        """
          package foo;

          public interface J {
              final class One implements J {}
              final class Two implements J {}
              final class Three implements J {}
              final class Four implements J {}
              final class Five implements J {}
              final class Six implements J {}
          }
          """
      ),
      java(
        """
          package bar;

          import foo.J;
          import foo.J.*;

          class Quz {
            void test() {
              J j = null;
              One one = null;
              Two two = null;
              Three three = null;
              Four four = null;
              Five five = null;
              Six six = null;
            }
          }
          """
      )
    );
}

@Laurens-W Since you evaluated RemoveUnusedImports in https://github.com/openrewrite/rewrite/pull/4450 it might make sense to briefly look at this one as well. The test is already there; perhaps the fix is similar?


[Modal] Modal service

Select one ...  (check one with "x")
[ ] bug
[ ] feature request
[x] enhancement

Right now, show or hide a modal is a little hardcoded, we need put the modal in our templates. I think we need something more dynamic. Something like this: https://material.angular.io/components/dialog/overview

@gperdomor
What do you mean by "we need put the modal in our templates"?
Maybe I'm missing something because I don't see anything on that link that can't be done with the Clarity modal...

@mathisscott for example if you have a page when you can show multiple types of modals you need to do something like this
<clr-modal [(clrModalOpen)]="showModal1"> MODAL CONTENT </clr-modal>
<clr-modal [(clrModalOpen)]="showModal2"> OTHER MODAL CONTENT </clr-modal>

You can simplify putting the content in their own components, like:
<clr-modal [(clrModalOpen)]="showModal1"> <component1></component1> </clr-modal>
<clr-modal [(clrModalOpen)]="showModal2">  <component2></component2> </clr-modal>

Maybe that modals could be appears in many pages, like some kind of confirm action to delete some items in a CRUD view... You can put a global modal in the root component, but this is ugly because not all pages need that modal...
A proper solution can be some kind of modal service with can open and close modal in a dynamic way:
// Imports

@Component({
// ...
})
export class ComponentExample {
    constructor(private modalService: ClarityModalService) {}

    showConfirmModal() {
        this.modalService.open(DialogExample)
    }
}

When DialogExample is other component, which can even open other component, without put them in the template html... Check the Material dialog example

@gperdomor
I think I understand what you are asking. You want to be able to reuse modals across your application and you feel the best way to do that is encapsulate their content in a component.
Why wouldn't you just make the modal itself a component?
<urapp-component1-modal></urapp-component1-modal>
<urapp-component2-modal></urapp-component2-modal>

Then you can register them in a service within your application and handle the open and close in your app (as opposed to relying on a component framework to dictate your application's services)?
Other than "Material is doing it", I don't see the advantage of the approach you are suggesting. Moreover, you're going to run into some i18n issues with the way Material is doing their modals. You may not care now. But you probably will later.

@youdz ^

Thanks @mathisscott for your answer, I am also stuck on this problem. How would you register/invoke <urapp-component1-modal></urapp-component1-modal> from a service?

@chrizy please see https://stackoverflow.com/questions/46664588/how-to-use-modal-dialog-with-vmware-clarity/46964407 for some details and an example.

Not sure that this is 100% related, so let me know if I should move it.
I'm trying to make components that may or may not be opened in a modal dialog. Imagine a Company Detail page with an Employee table listing the employees of that company (Employee component). Clicking edit opens the Employee Detail component as a modal dialog. There's also an Employee List component, listing all Employees across all Companies. Clicking edit there routes to the same Employee Detail component (use above as a modal) this time used as the left side of a page.
The Employee Detail HTML starts with a Form. Inside the form is a div with the Bootstrap "modal-body" class (wrapping the inputs) and another div with the save & cancel buttons wrapped in "modal-footer". The Employee List HTML holds the .
Final note, there's an *ngIf="model" on the form, showing it only when data is present.
My issue is that the modal does not seem to show the form, since it's outside of ["modal-title", "modal-body","modal-footer"] tags. Also, conceptually, it seems better if it followed the Material methodology, letting me create the Modal in the component TypeScript code, and pass it any other component that I wish to show.

@kdubious Could you create an example and start a new ticket or post to stackoverflow with vmware-clarity tag? This thread is specifically about the feature request, which might be related but your specific question is probably separate.

mb this is the solution
https://angular.io/api/common/NgComponentOutlet
you can create service that share observable property with components, and in the modal component through *ngFor show your modals
example:
`
export class Modal {
opened = false;
constructor(public component: Type, public data?: any) {}
open() {
this.opened = true;
}
close() {
this.opened = false;
}
}
@Injectable()
export class ModalService implements OnInit {
private modal = new Subject();
constructor() { }
ngOnInit(): void {
}
openModal(modal: Modal) {
this.modal.next(modal);
}
getModal(): Observable {
return this.modal.asObservable();
}
}
export class ModalComponent implements OnInit, OnDestroy {
modals: Modal[] = [];
subscription: Subscription;
constructor(private modalService: ModalService) { }
ngOnInit() {
this.subscription = this.modalService.getModal().subscribe(modal => {
modal.open();
this.modals.push(modal);
});
}
ngOnDestroy(): void {
this.subscription.unsubscribe();
}
close(modal: Modal) {
modal.close();
this.modals.splice(this.modals.indexOf(modal), 1);
}
}
modal component template:
<clr-modal *ngFor="let modal of modals" [(clrModalOpen)]="modal.opened" >
Title

`

For anyone ending up here, not knowing how to implement you own Modal service, this is a great start: https://medium.com/front-end-hacking/dynamically-add-components-to-the-dom-with-angular-71b0cb535286

mb this is the solution
https://angular.io/api/common/NgComponentOutlet
you can create service that share observable property with components, and in the modal component through *ngFor show your modals
example:
export class Modal {
  opened = false;
  constructor(public component: Type<any>, public data?: any) {}

  open() {
    this.opened = true;
  }

  close() {
    this.opened = false;
  }
}

@Injectable()
export class ModalService implements OnInit {

  private modal = new Subject<Modal>();

  constructor() { }
  ngOnInit(): void {
  }

  openModal(modal: Modal) {
    this.modal.next(modal);
  }

  getModal(): Observable<Modal> {
    return this.modal.asObservable();
  }
}

export class ModalComponent implements OnInit, OnDestroy {
  modals: Modal[] = [];
  subscription: Subscription;

  constructor(private modalService: ModalService) { }

  ngOnInit() {
    this.subscription = this.modalService.getModal().subscribe(modal => {
      modal.open();
      this.modals.push(modal);
    });
  }
  ngOnDestroy(): void {
    this.subscription.unsubscribe();
  }

  close(modal: Modal) {
    modal.close();
    this.modals.splice(this.modals.indexOf(modal), 1);
  }
}

modal component template:
<clr-modal *ngFor="let modal of modals" [(clrModalOpen)]="modal.opened" >

Title

    <ng-container *ngComponentOutlet="modal.component"></ng-container>

</clr-modal>

One use case where a ModalService would be useful is if you need to open some modal (for instance a confirmation modal) in a @ngrx/effect.
For instance I'd like to manage the logged in state in ngrx and I'd like to add an action to log out and asking confirmation in a effect

just as a reference, here is a good approach:
https://stackblitz.com/edit/clarity-light-theme-v11-3clpz8?file=app%2Fmodal.component.ts

@neaped My use case require to open a modal from something that's not a component. For instance a service or a ngrx/effect.

@mcosta74 I haven't code for this use case yet, but I think the link that provided above, it gave a good way to approach for you use case. As mathisscott mentioned,  a single (or even multiple) modal can be write as a component, then register it as a service. Once you want to use it,  just call the modal service, then use the modal component to control the modal behaviors.  In addition,  LubosD also provide a good reference.

Can you give more info about -> "i18n issues with the way Material is doing their modals. " ?
@mathisscott

@19Arne75
That comment was from around 8 months ago. ngMaterial at that time had a11y issues with keyboard navigation in their modals. Those seem to have been cleared up. Thanks!

@mcosta74 Something like this you looking for ?
https://stackblitz.com/edit/clarity-8jhcl5

that looks promising. Thanks

HI,
this is my proposal.
The main idea is to have a top level component (like the app alerts) controlled by a service.
The API shall be cleaned and documented but, if accepted I can work on a "formal" contribution proposal

@mcosta74 Thanks! That's exactly what I needed!
I'm new at Angular and Clarity, and was having a hard time finding a solution for multiples alerts and modals, without the need to each time write the complete modal from scratch.
Your solution allow me to only call a simple function from the service, and it's a go!

@Icebird99 Glad to hear this is useful for you.
To be honest there's something to clean in this example but is more or less what I needed (only confirmation Dialog/MessageBox)
I see @gnomeontherun added some labels: "needs: ux input" and "!" (what's this?).
Not sure the Clarity Team wants to introduce this kind of service in the core project. In case they accept the idea I can prepare something as proposal.

@mcosta74 - needs: ux input is where a design work is done that looks at the use cases for understanding and documenting the UX of the change as well as providing any visual design related to the UI that are needed for the proposal.
This design work produces a spec that can document the supported (and unsupported) use cases so we know what that the MVP is vs corner cases that may take longer or be more complicated to implement. From the spec we can proceed with development and also generate the documentation for guidelines and API related to the changes.
Its part of the process detailed in the contribution guidelines.

@hippee-lee thanks for the explanation but I was asking about the label !.
If I understand correctly you're working on the design side, so at some point we'll have spec and then the feature implemented.

Hey @mcosta74 - I'm not 100% sure what ! is for and I keep forgetting to ask @gnomeontherun. I'm not working on design for this but its the first thing that needs to happen here is to produce the design/spec based on the identified use cases.

Hello, I was also looking for a way to dynamically load modals so i actually have Material design just for MatDialog, MatDialogRef and MAT_DIALOG_DATA in my application. Its a bit hacky but with how many modals my application has it works.

Hello, I was also looking for a way to dynamically load modals so i actually have Material design just for MatDialog, MatDialogRef and MAT_DIALOG_DATA in my application. Its a bit hacky but with how many modals my application has it works.

to be honest I hate the Material solution for modals :D

I'm going to close this because we don't intend to support this behavior explicitly with a service and applications can easily set up their own service that fits their use cases and preferences.


Rajv2021 patch 55

55 - testing run

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes
Have you signed the CLA already but the status is still pending? Recheck it.


Making tests for plotter utilities

Increase code-cov by adding tests

Codecov Report

Merging #101 (cb2d7ba) into main (b2a3fa8) will increase coverage by 4.82%.
The diff coverage is 100.00%.

:exclamation: Current head cb2d7ba differs from pull request most recent head 5597445. Consider uploading reports for the commit 5597445 to get more accurate results

@@            Coverage Diff             @@
##             main     #101      +/-   ##
==========================================
+ Coverage   66.33%   71.16%   +4.82%
==========================================
  Files          15       15
  Lines        1423     1460      +37
==========================================
+ Hits          944     1039      +95
+ Misses        479      421      -58

Impacted Files
Coverage Δ

napari_clusters_plotter/_tests/test_plotter.py
98.30% <100.00%> (+2.85%)
:arrow_up:

napari_clusters_plotter/_utilities.py
60.00% <0.00%> (+2.85%)
:arrow_up:

napari_clusters_plotter/_plotter_utilities.py
88.46% <0.00%> (+71.79%)
:arrow_up:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Deploy the plugin as a visual studio code extension

As far as i understand, this should now be possible with vsc 1.20.
See https://code.visualstudio.com/docs/extensionAPI/extension-points#_contributestypescriptserverplugins
...or should this be an issue for vscode-tslint to include this plugin in the extension?

@angelozerr Any comment?

I followed the instructions and doesn't work with VSCode 1.22.2, sad


Are precompile's possible?

I'm currently working on a custom application using cosmos-sdk/cosmwasm and would like to know if there is a way to pre-compile certain contracts? And are there any size restrictions to the precompiled contracts?
Here is a usecase:
I want to compile a contract with a set of static lookup data (~100 million 32 byte records). We do not need this many for the start and can also be ok with 100k to begin with. And this needs to be deployed in the custom cosmos-sdk based application.
And this contract will then be used to lookup certain information in other cosmwasm contracts.
An alternative to this would be to have the static data exposed through a custom cosmos-sdk module and have the contract call the custom module to get the data. I'm not sure which one is feasible and gas efficient.

What could help you is pinned contract. A contract you pin is always compiled and kept in an in-memory storage for quick instantiation.
I just wonder if it is better to read this static data from a contract or from a database (i.e. blockchain state). You probably want to benchmark this.
The max Wasm size can be configured with a variable in wasmd. I don't have much practical experience but a 3MB contract does not sound too scary to me in a permissioned setup.


v4.0.0-beta.4 - [merged]

Merges v4.0.0-beta.4 -> master
Features:

[x] Improved Login page design with animations
[x] Updated About page #103
[x] Fix mandatory login redirect on unauthenticated case
[x] Added a button to periodically refresh the home page #104
[x] Fix submit written text on changing other options #102
[x] Hover all the experiment cards and not just the header on the home page
[x] Allow multiple select jobs to generate setstatus commands
[x] Migrated from vis-network to Cytoscape
[x] Add multiple select in graph/tree view
[x] Add select by status option in the graph view
[x] Add page size options on the experiment search

Waiting to get feedback from the CES and Climate DT users to extend the scope of this version

marked the checklist item Hover all the experiment cards and not just the header on the home page as completed

marked the checklist item Allow multiple select jobs to generate setstatus commands as completed

added 1 commit
8b444955 - added JobBasket component
Compare with previous version

added 1 commit
488cef2d - improve graph focus
Compare with previous version

added 1 commit
64174f51 - update experiment card hover
Compare with previous version

Preview of the Multiple Job Selection feature:

added 1 commit
67be9a47 - fix graph multiple select performance issue
Compare with previous version

added 1 commit
39ecd378 - add Cytoscape to the Graph View
Compare with previous version

marked the checklist item Add select by status option in graph view as completed

added 1 commit
318434e5 - select by status in graph view
Compare with previous version

added 1 commit
ef80dbb4 - add bottom panel in graph view
Compare with previous version

Migrated to Cytoscape and added a bottom panel to the graph view

added 1 commit
a20e24d4 - Home page improvements
Compare with previous version

added 1 commit
b239aa6b - fix fancy tree multiple select
Compare with previous version

added 1 commit
764c98f5 - add help text in graph viewport
Compare with previous version

added 1 commit
a5870031 - refactor fancy tree
Compare with previous version

added 1 commit
9bc5b88a - fix dropdown in experiment card
Compare with previous version

added 1 commit
103282a0 - add job history modal
Compare with previous version

added 1 commit
e0b654fd - improvements in multiple selection
Compare with previous version

added 1 commit
e2769c34 - multiple ui improvements
Compare with previous version

added 1 commit
192eb3e2 - adding react hook form
Compare with previous version

added 1 commit
626e06d6 - add localstorage save to bottom panel
Compare with previous version

added 1 commit
e15dc8bb - add statistics tooltip
Compare with previous version

added 1 commit
ec7e52d8 - improve performance tables
Compare with previous version

added 1 commit
fdd662a2 - update style of configuration view
Compare with previous version

added 1 commit
0145ea9f - add wrapper visualization
Compare with previous version

added 1 commit
8f464c89 - improve navbar resposiveness
Compare with previous version

added 1 commit
a936f4f5 - add tests for graph view
Compare with previous version

added 1 commit
178342eb - add more filters in exp search
Compare with previous version

added 1 commit
9a3be77a - add tree, performance and stats tests
Compare with previous version

added 1 commit
b22d4183 - lint fixes & improvements
Compare with previous version

mentioned in commit fb3f3c815fab89807049dcc3628ea344956d8d6f

added 7 commits
3c0cc06e - initial docse28738be - old pages reviewbd5bb559 - add installation instructionsb21c033a - add landing pagea2f5fb4a - add .readthedocs.yaml75e462ca - add sponsor logo optionca559ecf - Merge branch 'read-the-docs' into 'v4.0.0-beta.4'
Compare with previous version

added 1 commit
af769c17 - improve copy to clipboard button
Compare with previous version

approved this merge request


pretrain model

Excellent work!
Why does incremental reconstruction require loading a pre-trained model?

Hello @whwh747.  The goal is to minimize the impact of catastrophic forgetting on the results. You may check #29 and #19 for more details.


Create installation page

[ ] Create an installation page that describes how to install cargo risczero and the toolchain
[ ] Update Quick Start section in examples to point to installation page
[ ] Include instructions for how to check whether the toolchain is installed, and what version

FYI, if you do - [ ] instead of just [ ] github will treat that as a checklist: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists#creating-task-lists

I wonder if a stand-alone installation page is preferable to a clearly delineated installation step as part of a Quick Start guide?
I think this page may provide what we're looking for in an Installation page.

I think we should have a standalone installation page. Whether it makes sense to point everything to that page is a bit more of an open question to me -- it helps with maintenance, but I think the user experience can be worse (have to click too many things). But, for people coming from e.g. googling "install risczero" having a dedicated page is good, and there's nothing preventing us from keeping instructions on other pages (perhaps turning "install" into a link as well for the curious).
Right now risc0/website#286 does just this first part (of creating a separate install page)

I think we'll need to make sure this stays in sync with or we have a link to: https://github.com/risc0/risc0/blob/main/risc0/cargo-risczero/README.md#install

I think we'll need to make sure this stays in sync with or we have a link to: https://github.com/risc0/risc0/blob/main/risc0/cargo-risczero/README.md#install

I've linked this page in the latest revision of risc0/website#286, and I used a versioned link, which should prompt us to review if these got out of sync at least as often as we release.


Make EdgeSmoothness more efficient at the cost of doubling the memory…

… footprint of vertices.

performance drop is no longer ⚡
👍


GC back compat - Add flag at document to enable/disable

Right now it works like so: the flag on the metadata (in the summary) will specify a preference whether or not GC is allowed. True to enable GC, false to disable it, or undefined to leave the decision totally up to the runtime.

For documents earlier than summaryFormatVersion == 1 (i.e. if they don't have the metadata blob yet), then we assume summaryEnableGC is explicitly false, and will never runGC.
To set it the first time, just pass the desired value in runtimeOptions as summaryEnableGC. This can be done at any point up until it is set to either true or false, in which case it locks in that value. If nothing is passed to this runtime option, then it defaults to false and will stay that way.

We need tests to verify that we do enable / disable GC correctly based on different combination of these options.
We can probably add more combinations to the tests I have in this PR - https://github.com/microsoft/FluidFramework/pull/5539.

@vladsud - let me know if I got something wrong here. The suggestion is to include the runtime version in the metadata blob, and use it to map to "GC version", so we know which version of GC we are on, and thus which files we need to exclude/filter as "bad"? (2.2 above)

I can also imagine the property bag you mention in 1, but it just has the version for each feature, or 0/null/undefined if it is disabled. And it is stored in the metadata blob.
gcFeature: 0 | 1 | 2 - 0 is disabled, 1 is first version, 2 is second version, etc.
blobAggregationFeature: 0 | 1 - 0 is disabled, 1 is enabled


Types based bug fixes

Attempt to resolve #677

Added type test script npm run test:types
FIxed minor type issues across files
Pending: Error on src/json-type/system/tests/demo.ts:54:20 (Property 'kind' is missing in type ...)

Hi
Any feedback or review on this?


Bump kubernetes/client-node from 0.18.1 to 0.22.0

To support the latest Kubernetes features in the k8s package, we need kubernetes/client-node 0.22.0 that supports Kubernetes 1.30.

hi @Link-, my understanding is that @nikola-jokic is no longer working for GitHub, which may be the reason this repository has been largely quiet. is it possible to get this relatively safe dependency update reviewed and merged?


Improve handling of developement version numbers

The core idea here is that the repo contains version number of the "latest release", not the "next release"; and we dynamically change these if building a development version, transforming a.b.c to a.(b+1).0-devX on the fly.
This was prompted by the need to handle both a -rcX suffix and a -devX suffix on the version number, while making sure all version sort in the right way.
I also think this makes more sense than what we where doing; and is what setuptools-scm seems to be doing as well.
Another advantage is that we only have to do one commit for the release, bumping the version number & adding a tag to it (instead of many commits to change the version number in case of release candidate, tag, and then another commit to update the version to the next release).
The second commit make it so we can handle different "in-development" status for the different packages. The idea is that we will not tag the repo with v0.2.34, but instead with metatensor-core-v0.2.34. Potentially a single commit can be tagged with both metatensor-core-v0.2.34 and metatensor-operations-v0.56.1.

:books: Documentation preview :books:: https://metatensor--382.org.readthedocs.build/en/382/

I get the idea but have to think about this. Sounds good at first glance. This only works for the Python code though. The rust version will always be at the current release without the extra tag right?

This only works for the Python code though. The rust version will always be at the current release without the extra tag right?

Doesn't it make sense to also do this for the rust package, so imitating it with existing tools
https://github.com/rust-lang/cargo/issues/6583
https://crates.io/crates/cargo-edit

Currently the version seen by cargo/rustc is always set to the previous release version. Since there is no way to dynamically set the version for now, I don't think we can do much better. Also, it should not matter much, since the only way to use this code from other Rust project is to point to the git repo directly.
What we can and I think should do, is to change the version inside the CMakeLists.txt (which changes the version seen by users of the C and C++ API); and change the self-reported version in mts_version().

Currently the version seen by cargo/rustc is always set to the previous release version. Since there is no way to dynamically set the version for now, I don't think we can do much better. Also, it should not matter much, since the only way to use this code from other Rust project is to point to the git repo directly.

Can't we make a script for building the rust package where we set the version which is then used also in the CMakeLists.txt? Then its consistent in all packages.

Not really, since the rust version must be a string in the Cargo.toml file.  Also, there will only be some inconsistency for development versions, released version will have the same version number.

Not really, since the rust version must be a string in the Cargo.toml file.  Also, there will only be some inconsistency for development versions, released version will have the same version number.

Ah okay cargo set-version just changes the Cargo.toml file and overwriting the version in the build.rs seems not possible yet https://github.com/rust-lang/cargo/issues/7554 One could temporary change the Cargo.toml for build, but that seems not so robust

Updated the code again, switching back from bash to Python for the script which determines the number of commits since last tag since bash is a nightmare to fine on Windows. This adds a dependency on Python for pure C++ builds, but only in development mode, so I'm fine with it.


Update mac-jamfpro-policies.md

I have seen few customers using the example xml file as is , which will lead to exposing the device to risks (excluding pdfs , allowing users to create own exclusions , excluding the /home folder).
I modified the xml to include examples that would not expose the device to risk. Also added a comment for a customer to review the tags because if they dont change it all their devices will have the "ExampleTag" :)

@cventour : Any particular reason you closed this? Are you planning on reopening, or maybe creating a new PR?


Field args marked as @deprecated are lost when getting schema over HTTP

Which packages are impacted by your issue?
No response
Describe the bug
Given a schema like
type Query {
    example(arg: ID @deprecated): ID
}

type Foo {
    example(arg: ID @deprecated): ID
}

The args for the various fields that are marked as @deprecated are lost in all files generated by graphql-code-generator.
schema-ast produces:
type Foo {
  example: ID
}

type Query {
  example: ID
}

introspection produces:
      {
        "kind": "OBJECT",
        "name": "Foo",
        "description": null,
        "fields": [
          {
            "name": "example",
            "description": null,
            "args": [],
            "type": {
              "kind": "SCALAR",
              "name": "ID",
              "ofType": null
            },
            "isDeprecated": false,
            "deprecationReason": null
          }
        ],
        "inputFields": null,
        "interfaces": [],
        "enumValues": null,
        "possibleTypes": null
      },
      {
        "kind": "OBJECT",
        "name": "Query",
        "description": null,
        "fields": [
          {
            "name": "example",
            "description": null,
            "args": [],
            "type": {
              "kind": "SCALAR",
              "name": "ID",
              "ofType": null
            },
            "isDeprecated": false,
            "deprecationReason": null
          }
        ],
        "inputFields": null,
        "interfaces": [],
        "enumValues": null,
        "possibleTypes": null
      },

typescript generates
export type Foo = {
  __typename?: 'Foo';
  example?: Maybe<Scalars['ID']['output']>;
};

export type Query = {
  __typename?: 'Query';
  example?: Maybe<Scalars['ID']['output']>;
};

Your Example Website or App
https://stackblitz.com/edit/github-t8cgka
Steps to Reproduce the Bug or Issue
Visit the stackblitz reproduction and wait a few seconds for the server to start and graphql-code-generator to run
Expected behavior
I expect the args marked as @deprecated to be included
Screenshots or Videos
No response
Platform

OS: [e.g. macOS, Windows, Linux]
NodeJS: [e.g. 18.5.0]
graphql version: [e.g. 16.3.0]
@graphql-codegen/* version(s): [e.g. 2.6.2]

Codegen Config File
No response
Additional context
No response

In case it is helpful, I can confirm I am experiencing the same issue with the latest versions of the following:
"@graphql-codegen/cli": "^5.0.0",
"@graphql-codegen/schema-ast": "^4.0.0",
"@graphql-codegen/near-operation-file-preset": "^3.0.0",
"@graphql-codegen/typescript": "^4.0.1",
"@graphql-codegen/typescript-operations": "^4.0.1"

Can confirm this issue with
"@graphql-codegen/add": "5.0.0",
"@graphql-codegen/cli": "5.0.0",
"@graphql-codegen/fragment-matcher": "5.0.0",
"@graphql-codegen/near-operation-file-preset": "2.5.0",
"@graphql-codegen/schema-ast": "4.0.0",
"@graphql-codegen/typescript": "4.0.1",
"@graphql-codegen/typescript-operations": "4.0.1",
"@graphql-codegen/typescript-react-apollo": "3.3.7",

We are facing the same issue and it is affecting us severely , can we get a fix for this soon.
These are the package versions we are using for reference.
"@graphql-codegen/add": "^5.0.0",

"@graphql-codegen/cli": "5.0.0",

"@graphql-codegen/import-types-preset": "^3.0.0",

"@graphql-codegen/typed-document-node": "^5.0.1",

"@graphql-codegen/typescript": "4.0.1",

"@graphql-codegen/typescript-operations": "^4.0.1"

same here:
        "@graphql-codegen/cli": "^5.0.2",
        "@graphql-codegen/client-preset": "^4.2.5",

While undocumented, this seems to work:
generates:
  ./src/blah:
     schema: some-url
     ....

config:
  ...
  inputValueDeprecation: true

While undocumented, this seems to work:
generates:
  ./src/blah:
     schema: some-url
     ....

config:
  ...
  inputValueDeprecation: true

I ran into the same issue and this fixed it. Thank you

@AaronMoat That's a great tip! I figured it must be possible without any custom code.

@AaronMoat @mikew
This workaround works for codegen.js, but not when leveraging graphql config

We faced a similar issue in our project. After implementing the workaround, we can confirm that it effectively resolved the problem.


Inquiry about Fitness Score Location and Algorithm Experimentation in Source Code

Hello!
I hope this message finds you well. I am working with your open-source project and have a couple of questions that I believe you can provide insight on.
Fitness Score Location: I am trying to understand where the fitness score is calculated and stored within the source code. Could you please point me to the specific section or file where this is handled? This information is crucial for my understanding and potential modifications to the project.
Algorithm Experimentation: I noticed that your implementation utilizes the soea_DE_currentToBest_1_bin_templet, a differential evolution algorithm from Geatpy. I am curious if you have experimented with other genetic algorithms available in Geatpy, such as genetic algorithms or evolutionary strategies. I am currently working on the corresponding tasks in this area. Would you have any recommendations on how to proceed with such experiments?
Your guidance on these matters would be greatly appreciated as I aim to enhance the project's capabilities and performance.
Thank you for your time and support. I look forward to your response.
Best regards

You can find it in ProblemGA/aimFunc.
I have only attempted the method soea_DE_currentToBest_1_bin_templet, which was configured to initiate the population from the default values. You may wish to explore other methods.


test for SearchBarListItem component

Description
Written tests for SearchBarListItem component  using React-testing-library #1555
Screenshots

Checklist

[ ] 🔽 My branch is up-to-date with "development" branch
[ ] ✅All tests passed locally
[ ] ✨My changes working with up-to-date admin and back-end part locally, like charm
[ ] 🔗 Link pull request to issue

Please move tests to the general tests/unit/containers folder

done

done

Please move tests to the general tests/unit/containers folder

done


feat(transport): Add support for service call duration tracking

Coverage decreased (-0.02%) to 80.417% when pulling c63e6669136c4fd4ff7d95d0162b89e5d5db29e5 on orestes:master into a8446713ceffaaf2c78c99907dc189e3df05bf39 on kusanagi:master.


Issue258

This fixes issue 258 (about 'default' in filenames) and another issue (derived variables not plotted) involving plot set 7.

@glpotter, I'm naming you here so you'll get notified when this pull request is approved.


Bernd Proofread

Hello Peter,
let's try ;)
best,
Bernd

Hm, nope, seems like I've been wrong about GitHub picking the right target branch after all. We don't want to pull patch-1 to my master but translation-de... My mistake (I think), try again! When creating the pull request, choose this in the top instead. (It's confusing, but not nearly as confusing as it's been in the past. If you are confused by the concept of branches, info in the GitHub Guides as well)


Finally remove our copy of "archive/tar" now that Go 1.4 is the minimum!

IT'S ABOUT TIME. :tada:

I can barely even remember back to a time when we weren't forking or vendoring archive/tar! :joy:

ec61c46bf73b8c727fe8de1982d86a1417a8a0c4 is the oldest "use a different archive/tar" commit I can find :heart:

LGTM

b762d3a7391dd526826a0a1f1c983ea5e54852f5 is when we first officially vendored it

omg LGTM

omg omg omg omg

$ git diff --shortstat origin/release..origin/master
 736 files changed, 39777 insertions(+), 27858 deletions(-)


Dapper Multi Mapping

Thanks for this lovely application.
How does  DapperQueryBuilder work with Dapper's multi mapping? Is it supported?

Our CommandBuilder does not have facades for invoking Dapper Multi-mapper extensions directly, but you can combine CommandBuilder with Multi-mapper methods by explicitly passing CommandBuillder Sql and Parameters:
// DapperQueryBuilder CommandBuilder
var orderAndDetailsQuery = cn
    .QueryBuilder($@"
    SELECT * FROM Orders AS A
    INNER JOIN OrderDetails AS B ON A.OrderID = B.OrderID
    /**where**/
    ORDER BY A.OrderId, B.OrderDetailId");
// Dynamic Filters
orderAndDetailsQuery.Where($"[ListPrice] <= {maxPrice}");
orderAndDetailsQuery.Where($"[Weight] <= {maxWeight}");
orderAndDetailsQuery.Where($"[Name] LIKE {search}");

// Dapper Multi-mapping extensions
var orderAndDetails = cn.Query<Order, OrderDetail, Order>(
        /* orderAndDetailsQuery.Sql contains [ListPrice] <= @p0 AND [Weight] <= @p1 etc... */
        sql: orderAndDetailsQuery.Sql,
        map: (order, orderDetail) =>
        {
            // whatever..
        },
        /* orderAndDetailsQuery.Parameters contains @p0, @p1 etc... */
        param: orderAndDetailsQuery.Parameters,
        splitOn: "OrderDetailID")
    .Distinct()
    .ToList();

To sum, instead of using DapperQueryBuilder  CommandBuilder.Query<T> extensions (which invoke Dapper IDbConnection.Query<T>) you just invoke Dapper multimapper .Query<T1, T2, T3> directly, and use DapperQueryBuilder only for dynamically building your filters.

Awesome. Thanks


[DataSync] Do we need createdAt field for datasync?

Was just wondering if we need 'createdAt' for datasync? I am kinda leaning towards making it optional for datasync
This argument could be extended to creating some functionality for @versioned as well, where we could specify which fields we want, for example: @versioned(updatedAt: false) for someone who only wants the creation timestamp

It can be confusion. DataSync offers delta synchronization and conflict resolution. Default strategy for conflict resolution relies on lastUpdated.
I think we both know that this ended up little bit convoluted, but I will need to think of we need:

deltasync
conflict

And how to represent those two separately.
I wanted to keep them together to minimize amount of DataProviders we will need. I think you are right and we do not need it but we need to get some thoughts to avoid yet another deltadatasync. I think we need to avoid confusion for end users and also match some internal simplicity when maintaining data providers.
I think we need to push another strategy and then decide on what we will do here

I think we can sacrifice flexibility towards simplicity, but the challenge I have is that there are two ways to set this up: Conflicts are setup in code and versioning thing is set in schema.
Pulling strategies into schema makes less sense because you might want to have custom one anyway.
As I said it is easy to operate on the existing API once we bring the second strategy, but it looks like we going to have convoluted API so better to react quickly.
Let's dedicate some time next week to chat about this.

Hmm I completely agree, in hindsight the resulting API does seem rather convoluted but like you said let's bring in the strategy first maybe it will be better for us to look at it in entirety and then decide on improvements rather than ruminating before the fact hehe

I think if you work on strategy and conflict on separate branch without merging we will get 100 of the capacity we need and from there we going to work on improving this

This is outdated now because we have specific _lastUpdatedAt field for DataSync that's different from the one used with @versioned, added in #1771
Closing


Battery is limited at 92% and not 80%

The charge is stopping at 92% and not at 80%
I just recently installed it, did tow charges during night, one without force-discharging and one with. nothing change between the two charges

are you sure if the maintain level is correct? You can check via GUI seeing if the checkmark is on "enable 80% battery limit". If it is, can you send some logs with battery logs?


amazon-sagemaker-end-to-end-mlops workshop: add monitoring lab

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@kirit93 Ready for review!


Cannot upload .pptx file to local emulator

Does this occur consistently? Yes
Repro steps:

Right click one of the Blob containers in the Local Emulator in VS Code. Choose Upload Block Content, and select a file (I used a Powerpoint file "large_file.pptx")
Get pop-up: "Cannot retrieve storage account id for an attached account."

Action: azureStorage.uploadBlockBlob
Error type: Error
Error Message: Cannot retrieve storage account id for an attached account.
Version: 0.9.0
OS: win32
OS Release: 10.0.18363
Product: Visual Studio Code
Product Version: 1.47.3
Language: en
I can add that uploading this same file locally works in Microsoft Azure Storage Explorer.

Call Stack
AttachedStorageRoot.get storageAccountId [as storageAccountId] extension.bundle.js:31:438553
BlobContainerTreeItem.<anonymous> extension.bundle.js:31:231213
fulfilled extension.bundle.js:31:222469

Related to https://github.com/microsoft/vscode-azurestorage/issues/636

@Sti2nd I wasn't able to reproduce this error by

Making sure the Azurite extension is installed in VS Code
Expanding the "Local Emulator" node in the storage view
Selecting "Start Blob Emulator"
Creating a blob container and uploading a blob

Are you still running into the problem when you follow those steps?

@wwlorey I cannot reproduce anymore, either. Must have been fixed, thanks! ❤
When I could reproduce the menu option read "Upload Block Content" and now it reads "Upload Files".


add ESLint

why do you still prefer jshint over eslint? jshint doesn't validate code style :((

I'm working on moving over to ESLint. Will update this generator in a couple of weeks. I totally agree.

:+1:

I, who always forget space before parenthesis in function statement,  would :heart: this.

+1

Are we going to move xo in here @sindresorhus?

@kevva Yes, was planning that. Maybe in a few weeks.


is there any way that loop() function work during client.connect() training to connect to broker?

client.connect() halt ESP during trying to connect to broker, is there any way that loop() function work in this time?

No, the connect call is a blocking call.

Tx


file not found - tags.yaml

Hi, I'm new to wmii and wmiirc and I'm getting the following error:
https://gist.github.com/1554351
The rest seems to work fine if I comment out tags.yaml in my config.yaml:
https://github.com/jpablobr/wmiirc/blob/personal/config.yaml
I'm I missing something obvious? :/ I build wmii from:
http://hg.suckless.org/wmii/rev/f3d88385ea7c
$ ruby -v
ruby 1.9.3p0 (2011-10-30 revision 33570) [i686-linux]

$ gem list
*** LOCAL GEMS ***
barometer (0.7.3)
bundler (1.0.21 ruby)
httparty (0.8.1)
kwalify (0.7.2)
librmpd (0.1.1)
multi_json (1.0.4)
multi_xml (0.4.1)
nokogiri (1.5.0)
rake (0.9.2)
rumai (4.1.3)
tzinfo (0.3.31)

$ uname -a
Linux dell-17 3.1.5-1-ARCH #1 SMP PREEMPT Sun Dec 11 06:26:14 UTC 2011 i686 Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz GenuineIntel GNU/Linux

Thanks for reporting this.  I reviewed the code carefully and found that there is a race condition here:
  tags.each {|t| event 'CreateTag', t }
  event 'FocusTag', curr_tag

If the "1" tag does not exist when the first line is run, but later comes into existence when the second line is run, you will get that error.

Hmm, never mind that's not it.  The FocusTag handler also creates the tag before setting focus colors.

I noticed you're building wmii from the suckless hg.  That mirror is out of date; try the googlecode mirror instead:
https://code.google.com/p/wmii/source/checkout

I believe I built from http://libs.suckless.org/libixp, so now I tried with the google one. The following is the output:
https://gist.github.com/1554351/fd96043b3261db8b66d1640821591d77473836ca#file_libixp_from_google_code_build.log
and this is wmii's current error log when I uncomment tags.yaml:
https://gist.github.com/1554351/fd96043b3261db8b66d1640821591d77473836ca#file_wmii.log

Sorry to ask you about the compilation again but wmii needs to be rebuilt with your new libixp.  Try following these instructions completely.
By the way, when you comment-out the tags.yaml, does your status bar still work correctly?  Clicks and all?

And a temporary solution would be to add rescue nil to the end of the line that's causing the error.

I was testing your rumai lib by following the USAGE document:
https://github.com/sunaku/rumai/blob/master/USAGE
and again, most of it works fine, but some of the tag related stuff was blowing out. I added that log to my previews gist. Also in the red.untag "bar" code example section I got the following wmiirc rescue message:
https://gist.github.com/1554351#file_red_untag_bar_section_message.log
P.S mind = blowend :)

Thanks for reporting those errors, I'll look into it this weekend.  I haven't updated that tutorial in a long time, so it may have outdated instructions or examples.  By the way, that USAGE document is also available in a web-friendly format.

Thanks for reporting the bugs in Rumai documentation.  The red.next bug was an actual bug in my non-released (present on github, but not released as gem yet) code.  The push terms was incorrect usage in the tutorial: it doesn't make sense to push an array does it?  And the bar button example was just an updated file format in newer wmii versions.  Cheers.

Hi sunaku! Always ghedamat here :)
As usual one or twice a year I upgrade my local wmiirc conf to your master branch :)
this time I've noticed quite a lot of changes so I've decided to pull directly your master branch and your personal config to give it a try and I've occurred in a problem similar to jpablobr's...
In this Gist you can find wmiirc.log.1 that contains the error raised when I first launch wmii
adding a couple of rescue nil as jpablobr did leads to wmiirc.log.2 when I try to change view.
In both cases the /lbar does not contains any tag to see or click..
I've also updated to last wmii (patched) and libixp as you suggested in this Issue
so i'm running
wmii-hg2811+, ©2010 Kris Maglione

and

rumai 4.1.3

Not sure of what's happening here, my fault as I never had the time to dig deeper in rumai and try to understand its internals a bit better...
Hope that you can help me as you've always did, I the meanwhile I'll try to dig a bit too and I hope to be of some sort of help :D
Many thanks as usual!
Ghedamat

I wonder why there's no error on my system.  Maybe you are launching different apps at startup?  Please post your .xinitrc file also; here is mine for comparison.

I was actually trying to debug this the other day without much success... However, the following is what I've found (I might be completely wrong though :D).
Basically, it seems like Rumai is not being able to generate the correct Rumai::IXP type. When Rumai::IXP::Agent#recv tries to set the msg via msg = Fcall.from_9p(@stream) which then will call Rumai::IXP::Fcall#from_9p and which in turn (and based on the provided @stream) requests Rumai::IXP::Struct#from_9p for a proper Rumai::IXP type. It is actually returning an exception since the Rumai::IXP type is getting is a Rumai::IXP::Rerror.
That's just based on the stack trace... However, and here is where I'm really confused, I notice that this Rumai::IXP::Rerror only occurs when Rumai::IXP::Agent#recv tag variable is =4 and the Rumai::IXP::Fcall#from_9p size and type variables set to 23 and 107 (which is the Rumai::IXP::Fcall::CLASS_TO_TYPE Rerror) respectively.
So again, seems like Rumai is not being able to generate the proper primitives out of the 9P2000 protocol (I guess... :/). Here is the log file I was using (with a bunch of DBG: puts statements). Maybe @sunaku will be able to make more sense out of it.
And my ~/.xinitrc :)

My .xinitrc is REALLY simple,
here you are
xmodmap .Xmodmap
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation" 8 1
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Button" 8 2
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Axes" 8 6 7 4 5

/home/tha/.dropbox-dist/dropbox &
# launch wmii ( no loop )
exec /usr/local/bin/wmii -r /home/tha/.wmii/wmiirc

Thanks for debugging @jpablobr.  I ran Rumai's test suite and noticed that many tests fail due to 107 (Rerror) responses.  Something must have changed in the wmii codebase itself to break things.

Mmm, don't know if it can be helpful but @sunaku notice that I was having the same error also using an older version of wmii ( don't remember exactly but was around r2750) installed last summer, and that version is working perfectly with my old wmiirc

Thanks for clarifying @ghedamat.  I'm debugging the issue now, seems like a fid allocation problem in Rumai.

Also, I've just cloned git version of rumai and all tests seems to pass here (?)
pass: 57
time: 0.178013578

You're right.  I'm converting the test suite to use minitest and it fails there.  Sigh, I don't know anymore.  Maybe it's time to break away from the computer and enjoy the weekend? :P

maybe you're right :) also because here it's 3am in the morning :D time to go to bed :P
I'll back on this tomorrow :)

I got the test suite working again under minitest/spec and pushed it to Rumai.  Anyway, @ghedamat is right about that not being the issue.  Anyway, it's hard to debug the issue when I can't reproduce it on my system.
Try adding the following lines to the top of your CreateTag handler in display/tags.yaml:
lbar = Rumai.fs.lbar
p lbar: lbar
p exist: lbar.exist?
p entries: lbar.entries
test = lbar.testing123
p test: test
p exist: test.exist?
p create: test.create
p exist: test.exist?
p write: test.write("label testing 123")
p remove: test.remove
p exist: test.exist?

Let's see what you get on your systems.

This is what I get:
{:lbar=>#<Rumai::Node:0x932baf0 @path="/lbar">}
{:exist=>true}
{:entries=>[]}
{:test=>#<Rumai::Node:0x94b94d0 @path="/lbar/testing123">}
{:exist=>false}
{:create=>#<Rumai::IXP::Rcreate:0x94c6a7c @fields=[#<Rumai::IXP::Struct::Field:0x8e12e60 @name=:tag, @format=2, @countee=nil, @counter=nil>, #<Rumai::IXP::Struct::ClassField:0x8e02e98 @name=:qid, @format=Rumai::IXP::Qid, @countee=nil, @counter=nil>, #<Rumai::IXP::Struct::Field:0x8e02268 @name=:iounit, @format=4, @countee=nil, @counter=nil>], @values={:tag=>9, :qid=>#<Rumai::IXP::Qid:0x94c6a2c @fields=[#<Rumai::IXP::Struct::Field:0x8e18b80 @name=:type, @format=1, @countee=nil, @counter=nil>, #<Rumai::IXP::Struct::Field:0x8e18644 @name=:version, @format=4, @countee=nil, @counter=nil>, #<Rumai::IXP::Struct::Integer8Field:0x8e18158 @name=:path, @format=8, @countee=nil, @counter=nil>], @values={:type=>0, :version=>0, :path=>30064771074}>, :iounit=>8168}>}
{:exist=>true}
{:write=>nil}
{:remove=>#<Rumai::IXP::Rremove:0x94c3ac0 @fields=[#<Rumai::IXP::Struct::Field:0x8e12e60 @name=:tag, @format=2, @countee=nil, @counter=nil>], @values={:tag=>0}>}
{:exist=>false}

Thanks @jpablobr.  So the very first time CreateTag is called, the lbar is indeed empty.  This proves the fs.lbar.clear line is working.  What about the rest of the CreateTag handler?  Does it still raise the error if you remove the rescue nil workaround?

I currently have the same problem and I'm trying to debug it. What's the path of your XPI_SOCK_ADDR? is it set to ENV[WMII_ADDRESS] or the generic one in /tmp?

Weird, I don't have anything regarding wmii or xpi in my env. If I do an $ env | grep -i xpi or for wmii would not return a thing.
the following is what I get if I do a p EVN in my tags.yaml
{"SHELL"=>"/bin/bash", "TERM"=>"xterm", "GTK2_RC_FILES"=>"/etc/gtk-2.0/gtkrc:/home/jpablobr/.gtkrc-2.0", "QT_XFT"=>"true", "IRBRC"=>"/home/jpablobr/.rvm/rubies/ruby-1.9.3-p0/.irbrc", "WMII_CONFPATH"=>"/home/jpablobr/.wmii-hg:/usr/local/etc/wmii-hg", "HUSHLOGIN"=>"FALSE", "MY_RUBY_HOME"=>"/home/jpablobr/.rvm/rubies/ruby-1.9.3-p0", "rvm_verbose_flag"=>"0", "rvm_trust_rvmrcs_flag"=>"1", "USER"=>"jpablobr", "GDK_USE_XFT"=>"1", "ACK_PAGER"=>"less -FirSwX", "__array_start"=>"0", "escape_flag"=>"1", "LSCOLORS"=>"ExGxBxDxCxEgEdxbxgxcxd", "XDG_CONFIG_DIRS"=>"/etc/xdg", "rvm_prefix"=>"/home/jpablobr", "PATH"=>"/usr/lib/jvm/java-7-openjdk/bin:/home/jpablobr/.rvm/gems/ruby-1.9.3-p0/bin:/home/jpablobr/.rvm/gems/ruby-1.9.3-p0@global/bin:/home/jpablobr/.rvm/rubies/ruby-1.9.3-p0/bin:/home/jpablobr/.rvm/bin:/home/jpablobr/.cabal/bin:/usr/local/sbin:/usr/sbin:/sbin:/bin:/usr/bin:/usr/local/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl", "_"=>"/home/jpablobr/.wmii-hg/wmiirc", "HG"=>"/usr/bin/hg"<EMAIL_ADDRESS>"PWD"=>"/home/jpablobr", "JAVA_HOME"=>"/usr/lib/jvm/java-7-openjdk", "EDITOR"=>"emacsclient -c --alternate-editor emacs", "LANG"=>"en_US.utf8", "_second"=>"1", "GIT_PS1_SHOWUNTRACKEDFILES"=>"true", "HISTIGNORE"=>"&:ls:[bf]g:exit", "rvm_make_flags"=>"-j 7", "rvm_env_string"=>"ruby-1.9.3-p0", "rvm_version"=>"1.10.0", "SHLVL"=>"5", "HOME"=>"/home/jpablobr", "XDG_CONFIG_HOME"=>"/home/jpablobr/.config", "rvm_ruby_string"=>"ruby-1.9.3-p0", "GIT_PS1_SHOWSTASHSTATE"=>"true", "XDG_CACHE_HOME"=>"/home/jpablobr/.cache", "LESS"=>" -R ", "_first"=>"0", "LOGNAME"=>"jpablobr", "VISUAL"=>"emacsclient -c", "GEM_PATH"=>"/home/jpablobr/.rvm/gems/ruby-1.9.3-p0:/home/jpablobr/.rvm/gems/ruby-1.9.3-p0@global", "XDG_DATA_DIRS"=>"/usr/share/:/usr/local/share/", "WINDOWPATH"=>"7", "DISPLAY"=>":0"<EMAIL_ADDRESS>"RUBY_VERSION"=>"ruby-1.9.3-p0", "G_BROKEN_FILENAMES"=>"1", "WMII_FONT"=>"xft:proggynormal-8", "WMII_FOCUSCOLORS"=>"#111111 #EEF3E2 #ECF1EF", "WMII_NORMCOLORS"=>"#111111 #F8F8F8 #ECF1EF"}

I'm quite new to wmii so not sure if that's what you are asking for...

seems like the lbars do not exist. running the following code from rumai console "fixes" this.
4.times { |i|  Rumai.fs.lbar[i+1].create }

I removed fs.lbar.clear from display/tags.yaml#L18 and have not seen any breaks yet.

If I do the:
x.times { |i|  Rumai.fs.lbar[i+1].create }

the lbars get created... but If I then click on one of them, it errors out with the following:
E, [2012-01-17T09:27:33.887240 #26907] ERROR -- : bad color string -- in reply to #<Rumai::IXP::Twrite:0x8bcf054 @fields=[#<Rumai::IXP::Struct::Field:0x8496e7c @name=:tag, @format=2, @countee=nil, @counter=nil>, #<Rumai::IXP::Struct::Field:0x8483ad4 @name=:fid, @format=4, @countee=nil, @counter=nil>, #<Rumai::IXP::Struct::Integer8Field:0x8483570 @name=:offset, @format=8, @countee=nil, @counter=nil>, #<Rumai::IXP::Struct::Field:0x8482fa8 @name=:count, @format=4, @countee=#<Rumai::IXP::Struct::Field:0x8482990 @name=:data, @format=nil, @countee=nil, @counter=#<Rumai::IXP::Struct::Field:0x8482fa8 ...>>, @counter=nil>, #<Rumai::IXP::Struct::Field:0x8482990 @name=:data, @format=nil, @countee=nil, @counter=#<Rumai::IXP::Struct::Field:0x8482fa8 @name=:count, @format=4, @countee=#<Rumai::IXP::Struct::Field:0x8482990 ...>, @counter=nil>>], @values={:fid=>27, :offset=>0, :count=>13, :data=>"colors normal", :tag=>6}> (Rumai::IXP::Error)

I also tried removing the fs.lbar.clear from the tags.yaml (without the rescue nil statments) and it still errors out:
E, [2012-01-17T09:37:54.187572 #28340] ERROR -- : file not found -- in reply to #<Rumai::IXP::Twalk:0x997b20c @fields=[#<Rumai::IXP::Struct::Field:0x94b1e60 @name=:tag, @format=2, @countee=nil, @counter=nil>, #<Rumai::IXP::Struct::Field:0x94ab380 @name=:fid, @format=4, @countee=nil, @counter=nil>, #<Rumai::IXP::Struct::Field:0x94aaa98 @name=:newfid, @format=4, @countee=nil, @counter=nil>, #<Rumai::IXP::Struct::Field:0x94aa430 @name=:nwname, @format=2, @countee=#<Rumai::IXP::Struct::ClassField:0x94a9c24 @name=:wname, @format=String, @countee=nil, @counter=#<Rumai::IXP::Struct::Field:0x94aa430 ...>>, @counter=nil>, #<Rumai::IXP::Struct::ClassField:0x94a9c24 @name=:wname, @format=String, @countee=nil, @counter=#<Rumai::IXP::Struct::Field:0x94aa430 @name=:nwname, @format=2, @countee=#<Rumai::IXP::Struct::ClassField:0x94a9c24 ...>, @counter=nil>>], @values={:fid=>0, :newfid=>2, :wname=>["lbar", "1"], :tag=>7}> (Rumai::IXP::Error)

@niklas so, your problem is just that the lbars are not getting displayed? everything else works fine? no Rumai::IXP::Errors?
@sunaku, in this comment I mentioned that everything (besides the tags not showing) was working fine. However, not sure if I was wrong or something changed, but as you can see from above now it's not :/ If I try to switch windows it errors out.

@jpablobr no, my problem are IXP::Errors, too. But I refactored rumai a bit so it catches them all and logs them. Look at my fork https://github.com/niklas/rumai/commit/0ea121d282c86d537ddf556e2c4e374f806520a2 here. The log showns more concise which path was accessed.
Still not everything working fine, my wmii (standard oneiric 3.9.2+debian-3ubuntu) seems to be missing /rules, independently of the configuration.

Let's see if wmiir(1) hits the same error, since it's really WMII raising that "file not found" error via IXP:
system "echo 'label testing' | wmiir create /lbar/1"
system "wmiir ls /lbar"

Add that above the spots in display/tags.yaml where you hit the error.

Yes, that works fine. I guess I'm gonna play a bit more with wmii(1) and test a bit further the tags mechanism. So far I've only play with it via rumai.

Got it. display/barlet.yaml was loaded to late, thus inheriting TagBarlet from Rumai::Barlet instead of <Sandbox>::Barlet. So the implicit create of the Barlets wasn't called and the later write failed.
Adding the former to the imports in config.yaml before the glob display/*provides me with a nice tag list.
This shouldn't happen (TM), right? The YAMLs should require their depending imports immediatly before executing the before code. Too tired to find this now, mut maybe it helps

It works!

Excellent work @niklas! :metal:

Excellent work @niklas! :metal:  I moved all Ruby logic from barlet and the bars into lib/wmiirc/ in ceb2043090a2edf43a556b1c2dce17c493b85bce.  Tell me if that re-exposes the issue (works fine here).

There was a bug in the importing logic.  Data from import N was being merged with data from import N-1 instead of being merged with import 0 (the top-level config).  Now you can import tags before barlet safely:
diff --git a/config.yaml b/config.yaml
index 4d805ea..81e1048 100644
--- a/config.yaml
+++ b/config.yaml
@@ -3,6 +3,8 @@ import:
   - status/music/mpd.yaml
   - control/*.yaml
   - control/action/*.yaml
+  - display/tags.yaml
+  - display/barlet.yaml
   - display/*.yaml
   - display/color/zukitwo-dark.yaml
   - display/desktop/feh.yaml

Thanks to @niklas and everyone else involved for not giving up and squashing this bug! :sparkles:

thanks to everybody! :)

hurray!


Update storage blobs checkout action version

Use latest version of checkout action in examples: https://github.com/marketplace/actions/checkout

Learn Build status updates of commit cb38f78:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/storage/blobs/storage-blobs-static-site-github-actions.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit c1749b8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/storage/blobs/storage-blobs-static-site-github-actions.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Thanks @Dean-Coakley!
#sign-off


how to auto renew access token

PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Hi:
From https://www.npmjs.com/package/google-auth-library, I use the following example:
const {auth} = require('google-auth-library'); // load the environment variable with our keys
const keysEnvVar = process.env['CREDS'];
if (!keysEnvVar) {
  throw new Error('The $CREDS environment variable was not found!');
}
const keys = JSON.parse(keysEnvVar);
async function main() {
  // load the JWT or UserRefreshClient from the keys
  const client = auth.fromJSON(keys);
  client.scopes = ['https://www.googleapis.com/auth/cloud-platform'];
  const url = `https://dns.googleapis.com/dns/v1/projects/${keys.project_id}`;
  const res = await client.request({url});
}

the problem is client.credentials.access_token will expire in 1 hour.
I also see:
Handling token events
This library will automatically obtain an access_token, and automatically refresh the access_token if a refresh_token is present. The refresh_token is only returned on the first authorization, so if you want to make sure you store it safely. An easy way to make sure you always store the most recent tokens is to use the tokens event:
const client = await auth.getClient();
client.on('tokens', (tokens) => {
  if (tokens.refresh_token) {
    // store the refresh_token in my database!
    console.log(tokens.refresh_token);
  }
  console.log(tokens.access_token);

});
const url = `https://dns.googleapis.com/dns/v1/projects/${projectId}`;
const res = await client.request({ url }); // The `tokens` event would now be raised if this was the first request

But how to combine these two examples together to let client.credentials.access_token auto reflesh?
I try to ask the question in Google Cloud Developers<EMAIL_ADDRESS>but they tell me to ask question here.

Most built-in auth types know how to refresh their own tokens before expiry - the exception being direct access tokens. If the credentials loaded via JSON in the first example are service account key or user credentials (with refresh token), it should automatically refresh.

I use the first case and service account key and use them in an application. The application will call gcloud api in every 5 minutes. In the first hour, it works ok. But when one hour pass, it shows:
401 ***
error: ***
node:internal/process/esm_loader:94
internalBinding('errors').triggerUncaughtException(
code: 401,
^
message: 'Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.',
true
status: 'UNAUTHENTICATED',
(Use node --trace-uncaught ... to show where the exception was thrown)
details: [ [Object] ]

Any idea how to deal with my case?

Your code in main.js is fetching a token once (because it's making an API call https://github.com/chaowenGUOorg/audio/blob/0cd43fd26cfb1062c38142fa0856ca80fa2ac632/main.js#L8) and then re-using that token for the rest of the requests.
If you use your auth client to make the request, it will refresh its token. Can you try making the subsequent requests with client.request rather than fetch?

Thank you problem solved


[FLINK-32334] Also check if no taskmanager are running while waiting for cluster shutdown

What is the purpose of the change
This pull request add a check to ensure that no TaskManager pods are running while waiting for cluster shutdown.
With standalone mode the TaskManager pods are managed through a deployment managed by the operator.
If we do not check that no TaskManager pods are running we can face issue when redeploying the standalone app (during a config change for ex.) if the TaskManager deployment has not really being deleted.
Brief change log

Ensure TM pods are not running while waiting for cluster shutdown

Verifying this change

(Please pick either of the following options)
This change is already covered by existing tests, such as (please describe tests).

https://github.com/apache/flink-kubernetes-operator/blob/main/flink-kubernetes-operator/src/test/java/org/apache/flink/kubernetes/operator/service/StandaloneFlinkServiceTest.java#L93

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changes to the CustomResourceDescriptors: no
Core observer or reconciler logic that is regularly executed: no, only affect the check during cluster shutdown

Documentation

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

The PR looks good but you have some check style validations before I can merge this