refactor hammer : implement client factory for Compute client

closes #154

[x] implemented the creation of ComputeClient using the factory
[x] updated scanner.
[x] updated unit tests related to compute resources.
[x] added test for compute client factory.

thanks, agreed. I formatted the code with pycharm formatted. Also, the pylint we are using for this project approved this. But the formatting is indeed inconsistent. I will manually fix these formatting errors.

i am interested to contribute this issue you can please assign me this

We do not assign problem, feel free to just submit PR.


sanitizing canonical name

fyi

What does sanitizeWord do in 10 words or less?

it lower-cases and converts numbers to something like xnumx (normalizes) -- does not lemmatize or stem though

I'm rejecting your answer for excessive length.  You are welcome to revise and resubmit.


Automated cherry pick of #8335

Cherry pick of #8335 on release-5.37.
/cc  @koox00

/release-note-none


Extension is causing flairs to disappear on /r/NBA

So today I decided to finally find out why team flairs disappear on /r/NBA and I've narrowed it down to this extension. With the extension enabled and on old reddit, go to /r/NBA and you'll see flairs show up for a second, then the page does a mini reset by itself and then most flairs (weirdly neutral flairs like the NBA logo itself are unaffected) are gone until you manually refresh.
It only occurs on /r/NBA and none of the other sports subs I have tried like /r/soccer /r/NFL /r/hockey and /r/baseball. I've had this problem for about a year but never bothered to find the cause of it, but after clearing my cache and reenabling every extension one-by-one, I'm pretty sure this is the cause.
Think it can be fixed?

Looks like it's caused by their custom CSS expecting flair full class names to end with "1", meaning if additional classes are added, their selector will not
In r/NBA custom css: *[class^="flair flair"][class$="1"]:before { ... }

Interesting, thank you for taking a look. Can you walk me through adding that line to the custom CSS via either RES or TamperMonkey? I tried adding it as a CSS snippet in RES but it didn't work.

That's the problematic line, if you want to make an override style for the subreddit, you could add something like
*[class^="flair flair"][class*="1 "]:before {
    background-position-x:  0;
}

The extension (v. 3.16.3+) will now not add any classes to flair elements, so the issue is resolved


Implemented correct Raster.range

Fix for https://github.com/ioam/holoviews/issues/1020, it wasn't accessing the masked array directly and hence was returning inconsistent results with Image, which does.
%%opts Raster Image [colorbar=True]
tmp = np.random.rand(10,10)-0.5
tmp = np.ma.masked_where(tmp<=0, tmp)

hv.Image(tmp)+hv.Raster(tmp)

As we can see the masked values are no longer included in the range but are still indicated via the colorbar and the behavior is now consistent between Raster and Image.

Looks good. Any tests we can add to make sure we don't lose the new (desired) behavior?
Otherwise happy to merge.

Ready, merge when tests pass.

Tests are passing. Merging.


Question on EPH vs ECC

I have a question regarding the differences between EPH and Event hub consumer client.
I see on the latest official documentation of azure event hub sdk for node js version 5 is recommending Event hub consumer client with no mentioning of EPH. Is the ECC a wrapper around EPH? or is there a different use case scenario?

Will do! Thank you

Another question. I found that with the consumer client, it takes a few minutes until the messages are consumed.  I've followed the example at the very bottom of the migration doc and it seems like at the subscribing & processing events section it takes a while until the events are processed. Any thoughts?

@chradek should be able to answer your question
Meanwhile, can you share which overload of subscribe() method did you use? The one that takes a partitionId or the one that gives you events from all partitions? How many partitions do you have?

We are using the subscribe method that gives events from all partitions. 32 partitions and currently just single processor application. I know that from my experience with python sdk, load balancing partitions takes a few seconds, but never came across this cold start time prior to start of receiving events

We are also not setting a batch size and I think the default is set to 1?
@chradek

@kwontae Are you using a CheckpointStore when instantiating your EventHubConsumerClient? The EventHubConsumerClient should attempt to grab all partitions as fast as it can if there is no checkpointstore provided, but will claim on at a time every ~10 seconds otherwise.
We are investigating how to expose better control over how quickly an EventHubConsumerClient can ramp up with claiming partitions in the case where a checkpointstore is provided. I believe Python may let you adjust some of these options already.

Yes we are using a CheckpointStore

So the theory is that because we are using CheckpointStore, and the messages are being pushed to a partition 32 so it takes about ~320 seconds to claim?

@kwontae Correct. Currently if you had a single EventHubConsumerClient, and 32 partitions, it should take ~320 seconds to claim all partitions. You should start receiving events sooner than that though, since as soon as a partition is claimed (every ~10 seconds) you can start receiving events from that partition.

Hmm yeah. that's what I'm expecting as well, but doesn't seem to be the case here... So a few more things.

Do I need to have a promise like in the example so it closes after a certain timeout?
Process event is triggered when there is an incoming event to be ingested therefore the events in the example for(const event of events)  will never be empty when triggered?
Do we not have to set the startPosition if we are using the checkpointStore?

Getting this error when I run the example without the promise statement.

I see the issue occurs when it is claiming a partition without an event... which makes sense because if the events [] is empty, there won't be an event with the sequence number property therefore it throws an error when checkpointing. My understanding was that processEvent is only triggered when there is an event available for consumption upon partition claim.

@kwontae

Do I need to have a promise like in the example so it closes after a certain timeout?

I think you're referring to this piece:
https://github.com/Azure/azure-sdk-for-js/blob/4997350aa3ed80ea472fe7daed20ba95ec638010/sdk/eventhub/eventhubs-checkpointstore-blob/samples/typescript/src/receiveEventsUsingCheckpointStore.ts#L70-L78
No, you don't need to close the subscription/client unless you don't want to receive any new messages. For the purpose of the sample, that's just in place to show that you can stop receiving messages (and to let the sample exit).

Process event is triggered when there is an incoming event to be ingested therefore the events in the example for(const event of events) will never be empty when triggered?

The events can be empty if there weren't any events received within the maxWaitTimeInSeconds
So for example, let's say you were receiving events from partitions 0, 1, and 2. Let's also say that partitions 0 and 1 are continuously getting new messages, but partition 2 does not. You'll still see processEvents called for partition 2 every 60 seconds if there are no events. You can think of this as sort of a heartbeat that lets you know that the consumer client is still trying to receive events from the partition, even if no events are available.
You can increase the maxWaitTimeInSeconds to a very large value if you'd rather see processEvents called with an empty array less often: client.subscribe(handlers, { maxWaitTimeInSeconds: 3600 });

Do we not have to set the startPosition if we are using the checkpointStore?

The startPosition is used when a checkpoint does not already exist for a given partition. By default, the consumer client will use the startPosition latest, which means it will receive any events that are sent to Event Hubs after the subscribe call has started listening for events from the partition.
Since you're using the storage blob checkpointstore, when the client starts receiving messages from a partition, it first checks if storage blob has a checkpoint for that partition and if it does, it starts receiving events where the checkpoint left off. If the partition does not have a checkpoint, it will receive any new events that are sent to that partition (unless you specify a different startPosition).

The events can be empty if there weren't any events received within the maxWaitTimeInSeconds
So for example, let's say you were receiving events from partitions 0, 1, and 2. Let's also say that partitions 0 and 1 are continuously getting new messages, but partition 2 does not. You'll still see processEvents called for partition 2 every 60 seconds if there are no events. You can think of this as sort of a heartbeat that lets you know that the consumer client is still trying to receive events from the partition, even if no events are available.
You can increase the maxWaitTimeInSeconds to a very large value if you'd rather see processEvents called with an empty array less often: client.subscribe(handlers, { maxWaitTimeInSeconds: 3600 });

So in the example of using this with a checkpoint store, i see that the example has a try catch block where we try to updateCheckpoint(events[events.length - 1]) This would be an issue if this is called with an empty events. We should probably have an if else statement to catch this edge case so it doesn't call updateCheckpoint on an empty events array. Shouldn't this be captured in the Doc?

@kwontae
We've updated the sample and the documentation for processEvents to make it clearer that events can be an empty array, and why that can happen as part of #9340
Thanks for pointing out how we could improve our docs! I'll close this issue since I believe we've addressed the original questions, but feel free to comment or open a new issue if there's more you want to discuss.


FQCN fix for calls to ansible.utils.ipaddr in ceph playbook

Update ceph playbook to use ansible.utils.ipaddr in place of just ipaddr.
As a pull request owner and reviewers, I checked that:

[x ] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

+2

recheck

@fmount @fultonj We are investigating why podified-multinode-edpm-e2e-nobuild-tagged-crc is failing consistently, I'll let you know

recheck

/lgtm


[http] Swap default to legacy codec with runtime override to new (no-op)

Commit Message: Swap default codec to legacy codec implementation while codec error handling is improved. Backport some non-backported changes.
Risk Level: Low right now, legacy and codecs have not diverged
Testing: Integration tests now run by default with legacy, compile time options with new codecs. Unit tests are parametrized.
Release Notes: Updated
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]

The diff checker caused too many people's PRs to break format, so it got reverted https://github.com/envoyproxy/envoy/commit/6f17ae351ce006ea121abca3e1877c320f5530ca
(I think amongst merges was the real conflict... two codec merges would end up with conflicting diffs and break the diff checker).
Suggestions for how to do this cleanly? A big WARNING APPLY CHANGES TO LEGACY if format sees a change in codecs but no enforcement of a strict diff?
What's surprising is tests didn't pick up some of the functional detail changes.

Ahhh, I missed that, so it was my bad.  how about a simpler check that if you edit one file you edit the other?  That at least would make sure folks touched both and the reviewer could make sure it roughly looked right.

That suggestion orthogonal of the LGTM mind you :-P  Merge at your convenience!

Cool, will do in a follow-up!

@mattklein123 Could you take a quick look at this for cross-org stamp? (It should be a very quick review. Had to backport some changes to legacy, currently no diff exists between new/legacy's except namespace diffs).


Unable to use custom made macOS Framework

Writing an addon, it needs to use a custom made mac framework. In one of my .mm files I import it as any other framework would via #import <fwname/fwname.h>. However, when it gets to that line, it crashes saying fwname/fwname.h file not found make failed with exit code: 2.
I can't just keep the dependent framework in the global directory (which fixes the issue), I needed to define a custom path within my project directory for it to look at for portability.
module/
    binding.gyp
    otherstuff(package.json,index...)
    customfws/
        fwname.Framework
    cppsrc/
        stuff.mm(and more)

I will show my binding.gyp file below, it doesn't complain about not being able to find the framework, and doing node-gyp configure -- -f xcode then opening it up in Xcode confirms that the Framework Search Path setting is pointing to the right directory.
I hope I'm heading in the right direction with this question, but do I need any other flags to make sure the objective-c files look in the proper directories for the framework?
{
  "targets": [
    {
      "target_name": "myproj",
      "cflags!": [ "-fno-exceptions" ],
      "cflags_cc!": [ "-fno-exceptions" ],
      "sources": [
        "cppsrc/wrapper.cc"
      ],
      "conditions": [
        ["OS=='mac'", {
          "xcode_settings": {
            "FRAMEWORK_SEARCH_PATHS": "$(SRCROOT)/**"
          },
          "link_settings": {
            "libraries": [
              "customfws/fwname.framework"
            ]
          },
          "sources": [
            "cppsrc/stuff.mm"
          ]
        }]
      ],
      "include_dirs": [
        "<!@(node -p \"require('node-addon-api').include\")"
      ],
      'defines': [ 'NAPI_DISABLE_CPP_EXCEPTIONS' ]
    }
  ]
}

Did see Issue #682 , but having the exact same format is throwing a multiple build files error.

Wild guess. Try this:
	"include_dirs":
		[
			"<path>/<library>.framework -F<path>"
                 ]

Specify a parameter -F (like for the lib) inside the include dir path.

I'm going to close this due to age and make the assumption that nobody here has anything else to add to it. Feel free to open a new issue with error messages and more specific questions, even example code and config files would be great.


Only upload artifacts in finish task if run was successful

Not sure if we should upload artefacts when the run failed. E.g. if we skip some stuff based on existing artefacts this might cause problem if one wants to re-run a failed pipeline which failed due to external issues (such as SQ being down or so).

For 0.1, we will not upload. We can reconsider later if there is a use case. One option could also be to parameterise this.


Orbit Bridge - MAINNET QA

Review Info

Description
Info

Subgraph Reviewed
https://subgraphs.messari.io/subgraph?endpoint=https://api.thegraph.com/subgraphs/id/QmQYBn6WNjnUhvJw2wGs3QDGAPGc3pwSRb1UGxzAmazc88&tab=protocol%3F

Schema Version
1.2.0

Subgraph Version
1.0.0

Methodology Version
1.0.0

Protocol Type
BRIDGE

Evidence Spreadsheet
https://docs.google.com/spreadsheets/d/15SdFTuDZ5W0QrCFSVgydDypwoUpCRb9T/edit?usp=drive_link&ouid=104027705798814439445&rtpof=true&sd=true

Metric to Review
Total Value Locked (TVL)

The most recent TVL (Total Value Locked) data from the subgraph on June 21, 2023, shows significant discrepancies of -60.75% and -47.17% when compared to the official website and Defi Llama data, respectively.

Subgraph - TVL
Official Website - TVL
Absolute difference
Difference %

53,201,004.45
135,549,854.39
-82,348,849.94
-60.75%

Subgraph - TVL
Defi Llama - TVL
Absolute difference
Difference %

53,201,004.45
100,708,638.75
-47,507,634.30
-47.17%

Furthermore, the 5-day average TVL data deviates by 46.58% from Defi Llama data. These findings indicate inaccuracies in the subgraph TVL data.
Refer to the 'Protocol' sheet

Revenue

Based on the documentation of Orbit Bridge, all fees collected, including layer fees and bridge fees, are allocated to the protocol. However, when comparing the daily fees/total revenue (also protocol side revenue), assuming that 83.94% belongs to Ethereum based on its TVL percentage as per the official website, we observe a significant deviation of -78.93% from Messari subgraph data.

Subgraph - Daily Total Revenue
Official Website - Implied Daily Total Revenue
Absolute difference
Difference %

454.16
2,155.54
-1,701.38
-78.93%

Please refer to the analysis on 'dailyTotalRevenueUSD' on the protocol sheet for further clarification.

Total Pool Count and Total Supported Token Count

Based on the Orbit Bridge documentation, the protocol is stated to support only 27 tokens/pools within the Ethereum network. However, this contradicts the subgraph data, which lists 69 tokens.

Pool Overview - TVL

Among the top 10 largest pools/tokens by TVL, four of them ($USDT, $TALK, $DKA, and $BIOT) have TVL discrepancies of 50% or more compared to Defi Llama data.
Two of the top 10 pools/tokens ($ORC and $DON) have no TVL data available according to Defi Llama.
The $DUCATO token is not listed on Defi Llama data.

Please refer to the attached worksheet for more details.

@tryouge QA for orbit

@bye43 - I did debug the diffs from the QA and have some potential fixes. Sorry, I've been travelling in the past month and just got back home. I'll be working on this, this week - should have an updated subgraph within a week or two.

Updated deployment metrics look good, but its hard to check revenue from one chain. We are going to deploy the other subgraph chains and then compare to the overarching Orbit dashboard.


double and int parse methods are now called with an Invariant culture

To avoid issues on machine with different culture settings, it is a good practice to specify an invariant culture for parsing methods.

Thanks! I just read about Invariant culture and the problems it solves. I'll start using it where appropriate.


Transfer app from old repo

Description
The mobile app source code is being transferred from my personal Github account over to the company Github.
Test Plan
Everything should and will be accounted for before this transfer fully takes place.
Motivation and Context
At the time of creating the project, we only had one dev working on this, so it didn't make a ton of sense for us to create more complexity by using a company Github to start. However, that's not the case anymore, so we would like to have a central place where we can all access the source code equally, without any direct tie to any one individual, but rather, a group of individuals.
How Has This Been Tested?
Thus far, all of the synchronous action creators and the reducer case functions handling those actions have been unit tested.
Screenshots (if appropriate)
N/A
Types of Changes

[x] Documentation
Bug fix
New feature
Breaking change

Bug Fixes
N/A
Breaking Changes
N/A
Checklist

[x] My code follows the code style of this project
My change requires tests to be written
I have written the tests necessary for my code
[x] My change requires a change to the documentation
[x] I have updated the documentation accordingly

 Transfer app to Brassroots repo

I messed up with this PR as well. I'm learning how Github manages the forks between public and private repos.


Changing build, build def to ensure Nuget files are copied to output, fixing nuget license and project URLs

Changing build, build def to ensure Nuget files are copied to output, fixing nuget license and project URLs

MWAH

:sheep: it


Add legend to parts of doughnutchart

Hi!
I'm working with the doughnutchart and I was wondering if there was any way to implement a legend that is attached to the corresponding part in the doughnutchart? Example:

I am open to any suggestions on how to achieve this. Thanks!

Closing for now. Please refer to the Chart.js documentation for questions around configuration and/or usage of the library. If you have a bug or enhancement related directly to Chart.js, please open an issue on their Github.


Update jay-gordon.yml

just a small edit to bio

Docs Build status updates of commit 87a1684:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

advocates/jay-gordon.yml
:white_check_mark:Succeeded
View

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


EVM-395 Implement RFC-175 BLS integration

Description
Implement RFC-175 conclusion:
bls implementation for polybft should be based on github.com/umbracle/go-eth-bn256
Currently used kilic bls library is not well supported and that is why we are replacing it.
Changes include

[X] Bugfix (non-breaking change that solves an issue)
[ ] Hotfix (change that solves an urgent issue, and requires immediate attention)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist

[X] I have assigned this PR to myself
[X] I have added at least 1 reviewer
[X] I have added the relevant labels
[ ] I have updated the official documentation
[ ] I have added sufficient documentation in code

Testing

[X] I have tested this code with the official test suite
[ ] I have tested this code manually

Just a comment: We do not check input data in some places like Aggregate (do not check if a signature is nil), Marshall, Unmarshall... Maybe that should be done to have a clear log if a bug occurs in code which is calling BLS functionalities and does not submit valid data.

We do check for Unmarshal functions for both Signature and PublicKey. I do not think it is necessary to check Aggregate since we assume Polybft uses Unmarshal to decode the points and the check has been performed already.


Some downloaded files are damaged.

Sometimes the video files are completely downloaded but have some incomplete parts. This broken files produce an error during reproduction, like "End of file" on mplayer or cuts on VLC.
Is there any way to avoid this behavior or to repair the file?
Thanks!

I've also been getting this a lot lately.

How often does this happen? Which version of peerflix are you using?

For me it has occurred on both 0.30 and 0.30.1.
Although they may not correlate, this did start after I installed El Capitan.

v0.30.0
It's occurs approximately one out five times.
If I take the completed file and put into Transmission, there are a little percentage (less than 1%) of incomplete download. When Transmission finishes, the file just works fine.

Twice out of twice I got pixrot and incomplete download with 0.30.0.
I was able to download the same magnet link in whole with 0.29.2; however, I still got a lot of pixrot.


[Bug]: Unable to create file normally

Is there an existing issue for the same bug?

[X] I have checked the troubleshooting document at https://docs.all-hands.dev/modules/usage/troubleshooting
[X] I have checked the existing issues.

Describe the bug
Unable to create file normally
Current OpenDevin version
ghcr.io/opendevin/opendevin:0.8

Installation and Configuration
WORKSPACE_BASE=$(pwd)/workspace
sudo docker run -it   --pull=always   -e LLM_API_KEY   -e SANDBOX_USER_ID=$(id -u)   -e WORKSPACE_MOUNT_PATH=$WORKSPACE_BASE   -e LLM_API_KEY=""   -e LLM_BASE_URL="https://api.deepseek.com"   -e DEFAULT_MODEL="openai/deepseek-chat"   -v $WORKSPACE_BASE:/opt/workspace_base   -v /var/run/docker.sock:/var/run/docker.sock   -p 3000:3000   --add-host host.docker.internal:host-gateway   ghcr.io/opendevin/opendevin:0.8

Model and Agent
deepseek-chat
CodeActAgent
Operating System
WSL
Reproduction Steps
No response
Logs, Errors, Screenshots, and Additional Context
INFO:     <IP_ADDRESS>:48460 - "GET /api/list-files?path=%2F HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:48460 - "GET /api/list-files?path=%2F HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:60552 - "GET / HTTP/1.1" 304 Not Modified
06:08:37 - opendevin:INFO: browser_env.py:128 - SHUTDOWN recv, shutting down browser env...
06:08:37 - opendevin:INFO: session.py:66 - WebSocket disconnected, sid: 3a7c836e-f50a-491d-a161-717ab623e9bb
06:08:37 - opendevin:INFO: agent_controller.py:145 - AgentController task was cancelled
INFO:     connection closed
INFO:     <IP_ADDRESS>:60552 - "GET /api/options/models HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:60552 - "GET /api/options/agents HTTP/1.1" 200 OK
INFO:     ('<IP_ADDRESS>', 57412) - "WebSocket /ws" [accepted]
INFO:     connection open
06:08:40 - opendevin:WARNING: llm.py:70 - Could not get model info for openai/deepseek-chat
06:08:40 - opendevin:INFO: agent.py:79 - Using runtime: server
06:08:40 - opendevin:INFO: ssh_box.py:135 - SSHBox is running as opendevin user with USER_ID=1000 in the sandbox
06:08:40 - opendevin:INFO: ssh_box.py:178 - Detected initial session.
06:08:40 - opendevin:INFO: ssh_box.py:180 - Creating new Docker container
06:08:40 - opendevin:WARNING: ssh_box.py:578 - Using port forwarding till the enable host network mode of Docker is out of experimental mode.Check the 897th issue on https://github.com/OpenDevin/OpenDevin/issues/ for more information.
06:08:40 - opendevin:INFO: ssh_box.py:586 - Mounting volumes: {'/home/monster/workspace': {'bind': '/workspace', 'mode': 'rw'}, '/tmp/cache': {'bind': '/home/opendevin/.cache', 'mode': 'rw'}}
06:08:41 - opendevin:INFO: ssh_box.py:597 - Container started
06:08:42 - opendevin:INFO: ssh_box.py:613 - waiting for container to start: 1, container status: running
06:08:43 - opendevin:INFO: ssh_box.py:342 - Connecting to SSH session...
06:08:43 - opendevin:INFO: ssh_box.py:345 - You can debug the SSH connection by running: ssh -v -p 37825 opendevin@localhost using the password 'eeb3c62c-0ec7-4dab-9008-eb0cae1e4a2b'
06:08:44 - opendevin:INFO: ssh_box.py:349 - Connected to SSH session
06:08:47 - opendevin:INFO: agent.py:100 - Creating agent CodeActAgent using LLM openai/deepseek-chat
06:08:47 - opendevin:INFO: mixin.py:42 - Initializing plugins in the sandbox
06:08:47 - opendevin:INFO: mixin.py:30 - Sourced /opendevin/bash.bashrc and ~/.bashrc successfully
06:08:47 - opendevin:INFO: mixin.py:59 - Copied files from [/app/opendevin/runtime/plugins/agent_skills] to [/opendevin/plugins/agent_skills] inside sandbox.
06:08:47 - opendevin:INFO: mixin.py:67 - Initializing plugin [agent_skills] by executing [/opendevin/plugins/agent_skills/setup.sh] in the sandbox.
06:08:54 - opendevin:INFO: mixin.py:85 - Plugin agent_skills initialized successfully
06:08:54 - opendevin:INFO: mixin.py:30 - Sourced /opendevin/bash.bashrc and ~/.bashrc successfully
06:08:54 - opendevin:INFO: mixin.py:59 - Copied files from [/app/opendevin/runtime/plugins/jupyter] to [/opendevin/plugins/jupyter] inside sandbox.
06:08:54 - opendevin:INFO: mixin.py:67 - Initializing plugin [jupyter] by executing [/opendevin/plugins/jupyter/setup.sh] in the sandbox.
06:08:57 - opendevin:INFO: mixin.py:85 - Plugin jupyter initialized successfully
06:08:57 - opendevin:INFO: mixin.py:30 - Sourced /opendevin/bash.bashrc and ~/.bashrc successfully
06:08:57 - opendevin:INFO: browser_env.py:78 - Starting browser env...
06:08:57 - opendevin:ERROR: state.py:127 - Failed to restore state from session: sessions/5a56c80e-ce14-4c32-9fab-169974afe6f1/agent_state.pkl
Error restoring state sessions/5a56c80e-ce14-4c32-9fab-169974afe6f1/agent_state.pkl
06:08:57 - opendevin:INFO: agent_controller.py:140 - [Agent Controller 5a56c80e-ce14-4c32-9fab-169974afe6f1] Starting step loop...
INFO:     <IP_ADDRESS>:60554 - "GET /api/list-files?path=%2F HTTP/1.1" 200 OK
06:09:04 - opendevin:INFO: browser_env.py:121 - Browser env started.
06:09:12 - USER_ACTION
MessageAction (source=EventSource.USER)
CONTENT: Please use Python to write a Fibonacci sequence script and execute it
INFO:     <IP_ADDRESS>:57408 - "GET /api/list-files?path=%2F HTTP/1.1" 200 OK
==============
CodeActAgent LEVEL 0 LOCAL STEP 0 GLOBAL STEP 0
06:09:17 - opendevin:INFO: llm.py:181 - Cost: 0.00 USD | Accumulated Cost: 0.00 USD
06:09:17 - ACTION
IPythonRunCellAction
THOUGHT: Sure! Let me create a Python script to generate the Fibonacci sequence.
First, I'll create a new file named fibonacci.py:
CODE:
create_file('fibonacci.py')
</execute_ipython
06:09:18 - OBSERVATION
IPythonRunCellObservation
Cell In[1], line 2
</execute_ipython
^
SyntaxError: invalid syntax
==============
CodeActAgent LEVEL 0 LOCAL STEP 1 GLOBAL STEP 1
06:09:21 - opendevin:INFO: llm.py:181 - Cost: 0.00 USD | Accumulated Cost: 0.00 USD
06:09:21 - ACTION
IPythonRunCellAction
THOUGHT: Apologies for the syntax error. Let me correct that and create the file again:
CODE:
create_file('fibonacci.py')
</execute_ipython
06:09:21 - OBSERVATION
IPythonRunCellObservation
Cell In[1], line 2
</execute_ipython
^
SyntaxError: invalid syntax
==============
CodeActAgent LEVEL 0 LOCAL STEP 2 GLOBAL STEP 2
06:09:24 - opendevin:INFO: llm.py:181 - Cost: 0.00 USD | Accumulated Cost: 0.00 USD
06:09:24 - ACTION
IPythonRunCellAction
THOUGHT: I apologize for the confusion. Let me correct the syntax and create the file properly:
CODE:
create_file('fibonacci.py')
</execute_ipython
06:09:25 - OBSERVATION
IPythonRunCellObservation
Cell In[1], line 2
</execute_ipython
^
SyntaxError: invalid syntax
==============
CodeActAgent LEVEL 0 LOCAL STEP 3 GLOBAL STEP 3
06:09:29 - opendevin:INFO: llm.py:181 - Cost: 0.00 USD | Accumulated Cost: 0.00 USD
06:09:29 - ACTION
IPythonRunCellAction
THOUGHT: I apologize for the repeated errors. Let me correct the syntax and create the file properly:
CODE:
create_file('fibonacci.py')
</execute_ipython
06:09:29 - OBSERVATION
IPythonRunCellObservation
Cell In[1], line 2
</execute_ipython
^
SyntaxError: invalid syntax
==============
CodeActAgent LEVEL 0 LOCAL STEP 4 GLOBAL STEP 4
06:09:33 - opendevin:INFO: llm.py:181 - Cost: 0.00 USD | Accumulated Cost: 0.00 USD
06:09:33 - ACTION
IPythonRunCellAction
THOUGHT: I apologize for the confusion. Let me correct the syntax and create the file properly:
CODE:
create_file('fibonacci.py')
</execute_ipython
06:09:33 - OBSERVATION
IPythonRunCellObservation
Cell In[1], line 2
</execute_ipython
^
SyntaxError: invalid syntax
==============
CodeActAgent LEVEL 0 LOCAL STEP 5 GLOBAL STEP 5
06:09:36 - opendevin:INFO: llm.py:181 - Cost: 0.00 USD | Accumulated Cost: 0.00 USD
06:09:36 - ACTION
IPythonRunCellAction
THOUGHT: I apologize for the repeated errors. Let me correct the syntax and create the file properly:
CODE:
create_file('fibonacci.py')
</execute_ipython
06:09:37 - OBSERVATION
IPythonRunCellObservation
Cell In[1], line 2
</execute_ipython
^
SyntaxError: invalid syntax
==============
CodeActAgent LEVEL 0 LOCAL STEP 6 GLOBAL STEP 6
06:09:40 - opendevin:INFO: llm.py:181 - Cost: 0.00 USD | Accumulated Cost: 0.00 USD
06:09:40 - ACTION
IPythonRunCellAction
THOUGHT: I apologize for the confusion. Let me correct the syntax and create the file properly:
CODE:
create_file('fibonacci.py')
</execute_ipython
06:09:41 - OBSERVATION
IPythonRunCellObservation
Cell In[1], line 2
</execute_ipython
^
SyntaxError: invalid syntax
==============
CodeActAgent LEVEL 0 LOCAL STEP 7 GLOBAL STEP 7
06:09:44 - opendevin:INFO: llm.py:181 - Cost: 0.00 USD | Accumulated Cost: 0.01 USD
06:09:44 - ACTION
IPythonRunCellAction
THOUGHT: I apologize for the repeated errors. Let me correct the syntax and create the file properly:
CODE:
create_file('fibonacci.py')
</execute_ipython
06:09:44 - opendevin:WARNING: stuck.py:225 - Action, Observation pattern detected
06:09:45 - OBSERVATION
ErrorObservation(content='Agent got stuck in a loop', observation='error')
06:09:45 - OBSERVATION
IPythonRunCellObservation
Cell In[1], line 2
</execute_ipython
^
SyntaxError: invalid syntax

Unfortunately the LLM does not follow the system prompt instructions to correctly specify the closing tag, which is constantly missing the closing > at the end.

Yes, unfortunately it seems like the language model that you're using is not strong enough. You could switch to gpt-4o or claude-3.5-sonnet.
This is a long-standing issue that we're working on resolving, but creating a good open LLM for OpenDevin is not trivial: #1085
I'm going to close this as a duplicate though, as we'll work on this in issue #1085


Selective pulling and update documentation with use cases.

Thanks to @rGaillard input and suggestion in #8 it became apparent that the behaviour of "pull sources" and "pull translations" should be decoupled from the action of committing the changes to the PR. For example, if you want to just sync translations, but not the sources.
This PR changes the inputs such that the pull_sources and pull_translations dictate what gets fetched for sync from transifex. The commit step becomes the input commit_to_pr
Some example use cases were added for clarification.
This is a breaking change, and will be a major release.
Also, managing the old workflow and new workflow is becoming harder (eg. managing mandatory parameters). Since the git flow now supports all use cases, that is now marked in the docs as deprecated, and this will be the last release that will support it.
Again thanks @rGaillard for the contribution

Thank you for this new PR :)
Do you already know when you will merge this PR and create a new version?

@rGaillard I didn't merge right away because I was in contact with Transifex and got an open source license for the CI tests. Added one or two more changes to make the CI pass.
Don't know what happened, but maybe the actions/checkout@v1 changed their default behaviour to cloning the entire repo instead of shallow copy? I have no idea why this did not fail in our organisation. Need to check.
I'll now merge and this version will be available in :edge tag. I'll confirm that this works in our org and make a release after I ensure that this is stable. 👍


Q&A - 不能编译成功

用的最新的release版本,也试过最新提交吃的版本,都不能编译成功,log如下

XeTeX is required to compile this document.
Sorry!
************.
\RequireXeTeX ...}
\endgroup \fi
l.26 \RequireXeTeX

This error message was generated by an \errmessage
command, so I can't give any explicit help.
Pretend that you're Hercule Poirot: Examine all clues,
and deduce the truth by order and method.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! Fatal fontspec error: "cannot-use-pdftex"
!
! The fontspec package requires either XeTeX or LuaTeX.
!
! You must change your typesetting engine to, e.g., "xelatex" or
! "lualatex"instead of plain "latex" or "pdflatex".
!
! See the fontspec documentation for further information.
!
! For immediate help type H .
!...............................................
l.28 \msg_fatal:nn {fontspec} {cannot-use-pdftex}
|'''''''''''''''''''''''''''''''''''''''''''''''
| This is a fatal error: LaTeX will abort.
|...............................................

这是因为你使用的编译器不对，将编译器换成 XeLaTeX 再试试。如果你是使用的在线编译，一般点击 Setting - Compiler，可以查到具体选项。
原因详见 https://tex.stackexchange.com/questions/400825/fontspec-cannot-use-pdftex-on-overleaf

感谢,原来是编译器的原因.

I had similar problem while trying to my file on Overleaf. The simple steps are

Click on the menu bar to open up more options.
go to Compiler and select "XeLaTex" as your compiler
Then return to your main.tex file and compile your project.

I have attached some pictures below as a guide.

@happymondaynkanta It seems you are trying to compile a file but not from this repo, since I can't get the context of your template, I suggest you google the keywords that displayed in the logs.
If you meet problems of compiling this repo on overleaf, you can have a look at README https://github.com/hijiangtao/resume/blob/master/README.md , or open a new issue for tracking the problem.


Add contributors using all-contributors

Issue for using the all-contributors bot to acknowledge people's contributions.
Bot usage: https://allcontributors.org/docs/en/bot/usage
Emoji key: https://allcontributors.org/docs/en/emoji-key

@all-contributors
please add @tom-andersson for code.
please add @kallewesterling for code.

@all-contributors please add @kallewesterling for doc

@all-contributors please add @tom-andersson for research, maintenance, bug, test, tutorial, doc, review, talk, question

@all-contributors please add @kallewesterling for infra, ideas, projectManagement, promotion, answering questions

@all-contributors please add @acocac for userTesting, bug, mentoring, ideas

@all-contributors please add @acocac for research

@all-contributors please add @wesselb for research, code, ideas

@all-contributors please add @scotthosking for fundingFinding, ideas, projectManagement

@all-contributors please add @patel-zeel for bug, code, userTesting, ideas

@all-contributors please add @jonas-scholz123 for userTesting, research, code, bug, ideas

@all-contributors please add @nilsleh for ideas, userTesting, bug

@all-contributors please add @kenzaxtazi for ideas

@all-contributors please add @polpel for userTesting, bug

@all-contributors please add @RohitRathore1 for code

@all-contributors please add @magnusross for tutorial, data

Closing this now because I've captured most DeepSensor contributions to date. To add future contributions we can use the all-contributors bot in context within issues/PRs. For contributions without a corresponding issue/PR (such as non-code contributions), we can continue using the bot in this issue.

Thank you!

@all-contributors please add @annavaughan for research

@all-contributors please add @ots22 for ideas

@all-contributors please add @davidwilby for bug

@all-contributors please add @davidwilby for bug

@all-contributors please add @davidwilby for bug

Note to self: @all-contributors calls need to be added to issues (like this one) so that the bot's automatic PR is forked from the latest commit in main. If done from a PR the bot can be behind main, leading to merge conflicts.


RangeArea fix for smooth curves broke straight line rangeArea plots.

Type of change

[X] Bug fix (non-breaking change which fixes an issue)

There's another update on this theme to come tomorrow. Sorry.
On Sun, 31 Mar 2024, 1:07 am Juned Chhipa, @.***> wrote:

Merged #4367 https://github.com/apexcharts/apexcharts.js/pull/4367 into
main.
—
Reply to this email directly, view it on GitHub
https://github.com/apexcharts/apexcharts.js/pull/4367#event-12300714512,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGBUF4YPU2MHTJY46UJPHZTY23BJDAVCNFSM6AAAAABFPSGZRWVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGMYDANZRGQ2TCMQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


sync to live

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

File
Status
Preview URL
Details

windows-iotcore/Resources.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


cephfs in GKE: PV / PVCs not being deleted

PVs and PVCs are being created properly using the provisioner, but once the hosting namespace is deleted, the cleanup fails. Logs follow:
E0717 01:49:33.363126       1 cephfs-provisioner.go:261] failed to delete share "kubernetes-dynamic-pvc-ccaa8dc9-8959-11e8-8e61-625c2d54d0bc" for "kubernetes-dynamic-user-ccaa8e64-8959-11e8-8e61-625c2d54d0bc", err: exit status 1, output: Traceback (most recent call last):   File "/usr/local/bin/cephfs_provisioner", line 336, in <module>     main()   File "/usr/local/bin/cephfs_provisioner", line 332, in main     cephfs.delete_share(share, user)   File "/usr/local/bin/cephfs_provisioner", line 291, in delete_share     self._deauthorize(volume_path, user_id)   File "/usr/local/bin/cephfs_provisioner", line 242, in _deauthorize     pool_name = self.volume_client._get_ancestor_xattr(path, "ceph.dir.layout.pool")   File "/lib/python2.7/site-packages/ceph_volume_client.py", line 756, in _get_ancestor_xattr     result = self.fs.getxattr(path, attr)   File "cephfs.pyx", line 954, in cephfs.LibCephFS.getxattr (/home/jenkins-build/build/workspace/ceph-build/ARCH/x86_64/AVAILABLE_ARCH/x86_64/AVAILABLE_DIST/centos7/DIST/centos7/MACHINE_SIZE/huge/release/13.2.0/rpm/el7/BUILD/ceph-13.2.0/build/src/pybind/cephfs/pyrex/cephfs.c:10083) cephfs.ObjectNotFound: [Errno 2] error in getxattr E0717 01:49:33.363179       1 controller.go:1314] Deletion of volume "pvc-cca339bb-8959-11e8-ad6a-42010a80000e" failed: exit status 1
This is running the v1.1.0-k8s1.10 image in GKE with nodes running version 1.10.5-gke.0, and Ceph version 12.2.5 (cad919881333ac92274171586c827e01f554a70a) luminous. RBAC is in place and the provisioner was deployed using the RBAC deployment files. Not seeing any clues in the logs on the monitor. Anyone seen anything like this before?

Followup: did some checking, it seems this release is geared for Mimic, where the cluster is Luminous. Going to try upgrading the cluster and see if that resolves the issue.

Cluster's upgraded to Mimic, and the problem persists.

I've tried getting a shell into the provisioner container, and have confirmed it can talk to the cluster. I've also tried deleting the PV / PVC only before deleting the namespace and get the same error as originally:
[root@cephfs-provisioner-6bfb6d6467-x2kmw ceph]# CEPH_AUTH_KEY=<KEY_HERE> CEPH_AUTH_ID=<ADMIN_USER_HERE> CEPH_MON=<MONITOR_IP> python /usr/local/bin/cephfs_provisioner -r -n kubernetes-dynamic-pvc-54a71e66-8a02-11e8-8e61-625c2d54d0bc -u kubernetes-dynamic-user-54a720ab-8a02-11e8-8e61-625c2d54d0bc Traceback (most recent call last):   File "/usr/local/bin/cephfs_provisioner", line 336, in <module>     main()   File "/usr/local/bin/cephfs_provisioner", line 332, in main     cephfs.delete_share(share, user)   File "/usr/local/bin/cephfs_provisioner", line 291, in delete_share     self._deauthorize(volume_path, user_id)   File "/usr/local/bin/cephfs_provisioner", line 242, in _deauthorize     pool_name = self.volume_client._get_ancestor_xattr(path, "ceph.dir.layout.pool")   File "/usr/lib/python2.7/site-packages/ceph_volume_client.py", line 756, in _get_ancestor_xattr     result = self.fs.getxattr(path, attr)   File "cephfs.pyx", line 954, in cephfs.LibCephFS.getxattr (/home/jenkins-build/build/workspace/ceph-build/ARCH/x86_64/AVAILABLE_ARCH/x86_64/AVAILABLE_DIST/centos7/DIST/centos7/MACHINE_SIZE/huge/release/13.2.0/rpm/el7/BUILD/ceph-13.2.0/build/src/pybind/cephfs/pyrex/cephfs.c:10083) cephfs.ObjectNotFound: [Errno 2] error in getxattr
I half-wondered if it could've been a race condition (something required being deleted in the namespace before the PV/PVC deletion op was run?) but I guess not.

More info: this has only started happening since updating the container image from:
quay.io/external_storage/cephfs-provisioner@sha256:d3be97e4f67632b5d3daed7fb38c5dbb160eeae34fc9fa79a03590a9bf7cc0d3

Another update - I reverted the container back to the version I listed in the previous comment and tried the ops again. This time, I got the following:
$ k logs -f cephfs-provisioner-78c9b8f54c-d4zz4 -n cephfs I0718 21:32:44.120905       1 cephfs-provisioner.go:403] Creating CephFS provisioner ceph.com/cephfs with identity: cephfs-provisioner-1, secret namespace: I0718 21:32:44.138002       1 controller.go:548] Starting provisioner controller 1b57c1fa-8ad2-11e8-80e6-6eb9a45be078! I0718 21:34:50.089471       1 controller.go:1264] scheduleOperation[delete-pvc-9659f1f3-8acb-11e8-ad6a-42010a80000e[96b46913-8acb-11e8-ad6a-42010a80000e]] I0718 21:34:59.245432       1 controller.go:1264] scheduleOperation[delete-pvc-9659f1f3-8acb-11e8-ad6a-42010a80000e[96b46913-8acb-11e8-ad6a-42010a80000e]] E0718 21:35:04.240964       1 cephfs-provisioner.go:273] Cephfs Provisioner: delete secret failed, err: secrets "ceph-kubernetes-dynamic-user-966055c3-8acb-11e8-830b-aee5241b11d7-secret" not found E0718 21:35:04.241393       1 controller.go:1235] Deletion of volume "pvc-9659f1f3-8acb-11e8-ad6a-42010a80000e" failed: failed to delete secret E0718 21:35:04.243489       1 goroutinemap.go:165] Operation for "delete-pvc-9659f1f3-8acb-11e8-ad6a-42010a80000e[96b46913-8acb-11e8-ad6a-42010a80000e]" failed. No retries permitted until 2018-07-18 21:35:04.743392067 +0000 UTC m=+140.754518742 (durationBeforeRetry 500ms). Error: "failed to delete secret" I0718 21:35:14.245831       1 controller.go:1264] scheduleOperation[delete-pvc-9659f1f3-8acb-11e8-ad6a-42010a80000e[96b46913-8acb-11e8-ad6a-42010a80000e]] E0718 21:35:14.619070       1 cephfs-provisioner.go:261] failed to delete share "kubernetes-dynamic-pvc-966054d5-8acb-11e8-830b-aee5241b11d7" for "kubernetes-dynamic-user-966055c3-8acb-11e8-830b-aee5241b11d7"
I think maybe it is a race condition after all, going by the delete secret failed comment above. Insight definitely appreciated. 😄

Have you configured the class parameter adminSecretNamespace? https://github.com/kubernetes-incubator/external-storage/blob/master/ceph/cephfs/example/class.yaml#L10 IIRC it was implemented to isolate secrets from user's namespace because they shouldn't have access to them & in case they delete them like here.

I've done a little more investigation and restarted the pod just to see what happened. The following output seems to indicate the secret namespace is blank:
$ k logs cephfs-provisioner-b597cc69c-5hkwg -n cephfs
I0725 16:17:58.849760       1 cephfs-provisioner.go:403] Creating CephFS provisioner ceph.com/cephfs with identity: cephfs-provisioner-1, secret namespace:
I0725 16:17:59.088369       1 controller.go:615] Starting provisioner controller 4bc355b1-9026-11e8-be56-1e6f5d05d357!
I0725 16:17:59.088466       1 controller.go:652] Started provisioner controller 4bc355b1-9026-11e8-be56-1e6f5d05d357!

I'm assuming that's the secret namespace for each dynamic user secret as opposed to the admin one? I'm going to try setting this in the container env and see if this sidesteps the issue.

After trying that, the provisioner still doesn't clean up the PV after the namespace is deleted. No errors are thrown, at least.

check ceph.dir.layout.pool attr:
getfattr -n ceph.dir.layout.pool <path>

mount cephfs to /mnt
check ceph.dir.layout.pool attr
getfattr -n ceph.dir.layout.pool /mnt
if no such attribute
setfattr -n ceph.dir.layout.pool -v "cephfs_data" /mnt

same issue
E0322 13:02:25.821003       1 cephfs-provisioner.go:268] failed to delete share "data-elasticsearch-elasticsearch-master-0" for "k8s.efk.data-elasticsearch-elasticsearch-master-0", err: exit status 1, output: Traceback (most recent call last):   File "/usr/local/bin/cephfs_provisioner", line 364, in <module>     main()   File "/usr/local/bin/cephfs_provisioner", line 360, in main     cephfs.delete_share(share, user)   File "/usr/local/bin/cephfs_provisioner", line 319, in delete_share     self._deauthorize(volume_path, user_id)   File "/usr/local/bin/cephfs_provisioner", line 260, in _deauthorize     pool_name = self.volume_client._get_ancestor_xattr(path, "ceph.dir.layout.pool")   File "/lib/python2.7/site-packages/ceph_volume_client.py", line 756, in _get_ancestor_xattr     result = self.fs.getxattr(path, attr)   File "cephfs.pyx", line 954, in cephfs.LibCephFS.getxattr (/home/jenkins-build/build/workspace/ceph-build/ARCH/x86_64/AVAILABLE_ARCH/x86_64/AVAILABLE_DIST/centos7/DIST/centos7/MACHINE_SIZE/huge/release/13.2.1/rpm/el7/BUILD/ceph-13.2.1/build/src/pybind/cephfs/pyrex/cephfs.c:10083) cephfs.ObjectNotFound: [Errno 2] error in getxattr E0322 13:02:25.821248       1 controller.go:1181] delete "pvc-047c2c0f-30a7-4e73-acfc-a79bf4460dcd": volume deletion failed: exit status 1 I0322 13:02:25.821665       1 event.go:221] Event(v1.ObjectReference{Kind:"PersistentVolume", Namespace:"", Name:"pvc-047c2c0f-30a7-4e73-acfc-a79bf4460dcd", UID:"57f96660-0ee2-4d5b-96d6-a82837049561", APIVersion:"v1", ResourceVersion:"440515", FieldPath:""}): type: 'Warning' reason: 'VolumeFailedDelete' exit status 1
Tried mimic and nautilus, rebuilt provisioner docker image to the latest code, tried different images, checked fattr as @zhoubofsy mentioned, nothing helped
Also checked secrets and so on.
The issue, as follows: pvc provisions well, client secret creates in cephfs namespace as well.
Then when I deleted pvc - it deleted, pv still remaining with Released status, the data from pvc actually remaining in the ceph storage, the client secret does not delete, and the error in the provisioner pod.
Then I can delete pv and user secret by hands - it is ok. But the data in the ceph storage still remaining.
Then if I create pvc with the same name - it will be with the previously stored data.

due to no env CEPH_VOLUME_GROUP  when delete, see this commit: https://github.com/kubernetes-incubator/external-storage/commit/fc016bc700030bb61ee3ff929a1ae4de28fe5cd0


Simplify function implementation returned by thunder.jit for easier instrumentation of different stages

This PR changes the thunder.jit.fn_ implementation to use just a few lines of code making it more readable and amenable to per-function instrumentation like cProfile, pyinstrument, or NVTX decorators.
I removed a few unused timer measurements or if there was just a stop with no start. Other than that all CompileStats time measurements are preserved in this PR.
There was a todo to rename "last_executed" to "last_computation", this change is included here.
Here is what the function looks like now:
def fn_(*args, **kwargs) -> Any:
    cache_entry, inps, pro_to_epi = get_computation_and_inputs(*args, **kwargs)
    check_storage_aliases(cache_entry, inps)
    result = cache_entry.computation_fn(*inps)
    result = maybe_connect_to_autograd(cache_entry, result)
    result = maybe_call_epilogue(cache_entry, result, pro_to_epi)
    return result

@tfogal, could you please review the changes? Would this PR work well with the planned nvtx marker decorators from https://github.com/Lightning-AI/lightning-thunder/pull/1268?

CI failures that I need to take a look what's going on:
=========================== short test summary info ============================
FAILED thunder/tests/test_jit_general.py::test_litgpt_variants_kvcache[cpu-llama1-like] - TypeError: tuple indices must be integers or slices, not tuple
FAILED thunder/tests/test_jit_general.py::test_litgpt_variants_kvcache[cpu-codellama2-like] - TypeError: tuple indices must be integers or slices, not tuple
FAILED thunder/tests/test_jit_general.py::test_litgpt_variants_kvcache[cpu-falcon-40b-like] - TypeError: tuple indices must be integers or slices, not tuple
FAILED thunder/tests/test_jit_general.py::test_litgpt_variants_kvcache[cpu-long-context-like] - TypeError: tuple indices must be integers or slices, not tuple
FAILED thunder/tests/test_jit_general.py::test_litgpt_variants_kvcache[cpu-llama2-like] - TypeError: tuple indices must be integers or slices, not tuple
FAILED thunder/tests/test_jit_general.py::test_litgpt_variants_kvcache[cpu-falcon-7b-like] - TypeError: tuple indices must be integers or slices, not tuple

There was a todo to rename "last_executed" to "last_computation", this change is included here.

Is this one of the timers that mixology is using? If so, we may want to hold off. @mpatel31415 ?

There was a todo to rename "last_executed" to "last_computation", this change is included here.

Is this one of the timers that mixology is using? If so, we may want to hold off on this part. @mpatel31415 ?

No, we use iter_t0 = time.perf_counter() and  t1 = time.perf_counter() from benchmark_litgpt.py script :)

There was a todo to rename "last_executed" to "last_computation", this change is included here.

Is this one of the timers that mixology is using? If so, we may want to hold off on this part. @mpatel31415 ?

No, we use iter_t0 = time.perf_counter() and t1 = time.perf_counter() from benchmark_litgpt.py script :)

oh, great!
I thought you were using some timers, though---how are you measuring compilation time, if not using these CompileStats timers?

There was a todo to rename "last_executed" to "last_computation", this change is included here.

Is this one of the timers that mixology is using? If so, we may want to hold off on this part. @mpatel31415 ?

No, we use iter_t0 = time.perf_counter() and t1 = time.perf_counter() from benchmark_litgpt.py script :)

oh, great!
I thought you were using some timers, though---how are you measuring compilation time, if not using these CompileStats timers?

We measure 2N iterations giving us iter_times = [t1,  t2, .. t_2N] and we assume that compilation (and warmup) time is sum(iter_times[:N]) - sum(iter_times[N:]). In this way it's easy to measure it irrespective of the compilation method in the same way.

I thought you were using some timers, though---how are you measuring compilation time [. . .]

We measure 2N iterations [. . .]

Oh! That's actually great news as I had (incorrectly) thought you were using the timers, and this makes it easier for us to change that interface.
Thanks!

Looks like tests pass and this is good to go, AFAICT.
@t-vi merge?

So when will we be able to drop the timers?

So when will we be able to drop the timers?

I can start looking at this after #1268


Explore using xlwt module for creating Excel appendix

https://github.com/python-excel/xlwt

xlwt will work -- created an .xls file successfully.  Need to implement for username, etc output.


fix: do not allow additional properties in output object

This would fix the issue described in #12 but breaks YAMLs that should be valid (tests are failing). Intended as a basis for discussion.

breaks YAMLs that should be valid (tests are failing)

Actually these yamls are not valid too 😅
fixes.patch
if you apply this patch, the examples should be in sync with the latest recipe format :)

@wolfv PTAL

Great stuff! :)


False positive for some anti virus programs

This isn't really a issue but more of a heads up to users.
some anti virus programs have started to report what is known as a false positive for the maxmix.exe, updater.exe, and firmwareinstaller.exe. so while your anti virus may be saying it is a virus it is not. if you are still doubting the file/s you can check the files by uploading them to virustotal.
virus total for maxmix.exe
virus total for updater.exe
virus total for firmwareinstaller.exe
the devs are aware of it and there doesn't seem to be much they can do about it

you can learn more about what a false positive is at these links:
https://www.howtogeek.com/180162/how-to-tell-if-a-virus-is-actually-a-false-positive/
https://blog.malwarebytes.com/security-world/2017/09/explained-false-positives/
https://www.pandasecurity.com/mediacenter/security/false-positives-what-are-they/

BitDefender seems to be the most stubborn. after adding maxmix.exe and updater.exe to exceptions + reinstalling the program everything is ok.

I tested this by unpacking the current .msi using 7zip, re-zipping it with 7zip, and uploading that zip to VirusTotal. The result was one detection from BitDefenderTheta.
What is worth noticing is the data in the "relations" tab. It shows that the detections are within MaxMix.exe, DriverInstaller.exe, and FirmwareInstaller.exe. These results are different from those shown in @pbanj's original post, but then the hashes show these files to be different from what @pbanj submitted.
It might be worth contacting the developers of BitDefenderTheta to get more information on why their software is triggering on these files. Having a clean VirusTotal scan is a good public relations move, if nothing else.

An even more amusing Microsoft Resolution is at this link.
It not only says that the antivirus detection is "not a bug", it also says "that antivirus has a false positive".  /facepalm

Windows Defender also quarantining the program due to false positives.

since it's been a while i told virus total to rerun the scans. seems bitdefender and ms defender aren't bitching about it anymore. is this still a problem for anyone?

https://www.virustotal.com/gui/file/2db81bb245fd6fdf240a4300388f8b84d2a05b477f4497d7377e6ccda448f3f9/detection
This is of the pre-release version. I'm gonna leave this open until full release.


NEXT-10881 - Feature Request: encrypted config field

Plugins don't have a standardized way of storing information securely. Ideally, there would be an input field from configuration that would store data encrypted using the app secret.
This is a clone of NEXT-5136

@swDennis @sensus-media are you working on it?


Sync VSCode Profile to cloud / login

In the same way that Firefox and Chrome store bookmarks, history, settings, etc. in a cloud account via login, I think it would be fantastic to offer that built-in functionality for VSCode to save in the Azure cloud the following:

User and Workspace settings
Installed extension
Git repositories (not the repos themselves, but what's necessary to automatically resync)

This would help a lot when using multiple machines. To get up and running on a new computer, the idea is like this:

Install VSCode
Sign in
Done... all settings, extensions, and connections to your Git repositories are now automatically synchronized.

I would like to voice my opinion against any type of Sign In/Sign Ups in vscode. That's exactly the reason why vscode is so good now, because it isn't overweighted with stuff like that. If you do want to sync, you can download existing extensions or make your one.

/duplicate #2743


[name bikeshed] Is "Context" the right name?

I don't have a concrete suggestion here, but context can be so broad that it can be meaningless. At the same time, we now have the decorator context argument, and while i don't think that collisions are imminent it might be worth discussing here.

I think it's acceptable to have both, but if we had to pick one, I'd rather rename the decorator argument :-)
Perhaps it's my React ecosystem bias, but "context" seems like the perfect name for what this proposal does.

Just like "global" to me implies top level, "local" implies to me bottom level :-/

I'm really partial to calling these "async contexts", mainly because I absolutely hate the names that Node gave it (AsyncLocalStorage, which is an AsyncLocal-Storage and not an Async-LocalStorage). "storage" is just the wrong name for this concept.
AsyncLocalContext could work with these called "async locals", but I don't have a better word than context.

There's also the fact that "async context" (or "async-local context") seems to refer to the general key-value map (the "snapshot", as we have sometimes called it). An AsyncContext instance represents an entry in that map.

altho to me "context" does imply the map. Maybe AsyncContextEntry or something?

I'm really partial to calling these "async contexts", mainly because I absolutely hate the names that Node gave it (AsyncLocalStorage, which is an AsyncLocal-Storage and not an Async-LocalStorage). "storage" is just the wrong name for this concept.

I believe the name AsyncLocalStorage came from the concept in C# called ThreadLocalStorage.
I've also been interested in this concept for a while.
I asked ChatGPT for some other name ideas:
AsyncScope: This name suggests the idea of a defined scope or boundary for asynchronous operations. It emphasizes the encapsulation of the context and its management within a specific area.
AsyncCarrier: This name implies that the proposal will carry or transport the context information throughout the asynchronous flow, ensuring the context is preserved and accessible when needed.
AsyncFlow: This name highlights the flow of asynchronous operations and how the context is maintained and passed along during the execution of those operations.
AsyncState: This name emphasizes the state of the context, which might change during the execution of asynchronous operations, and the need to manage that state effectively.
AsyncThread: This name draws a parallel between JavaScript's asynchronous operations and threads in other programming languages, emphasizing the need to manage context in a similar way to how threads manage their own context.
AsyncLink: This name suggests the idea of linking or connecting the context through various asynchronous operations, ensuring that the context remains consistent and available throughout the entire chain of execution.
AsyncChain: This name refers to the chain of asynchronous operations, emphasizing the continuity of context throughout the execution of these operations.
AsyncBinder: This name implies that the proposal will bind or tie together the context across asynchronous operations, making sure that the context is accessible and consistent at every stage.
AsyncRuntime: This name highlights the runtime environment where asynchronous operations occur, emphasizing the need for context management during the actual execution of the operations.
AsyncTrace: This name refers to the idea of tracing the context throughout the asynchronous operations, providing a clear path for the context to follow and ensuring its availability when needed.

In Project Loom for the JDK, they introduced ScopedValue which is very similar in both syntax and goals.
final static ScopedValue<...> V = new ScopedValue<>();

// In some method
ScopedValue.where(V, <value>)
           .run(() -> { ... V.get() ... call methods ... });

// In a method called directly or indirectly from the lambda expression
... V.get() ...

In clojure, there is a concept called "dynamic binding" which is used similarly to bind a value in a scope. Many functions which start or run on a thread implement what is called "binding conveyance" which propagates dynamic bindings across async contexts.
(def ^:dynamic *v* 1) ; dynamic values are typically denoted with earmuffs

(binding [*v* 2]
  (future (print *v*)))
;; 2

I think that if consumers end up finding it useful outside of async contexts then it would be worth leaving that part out of the name.
My 2c:

ScopedValue
DynamicBinding
BoundValue

From what I gather, in scheme and its variants, this concept is called a fluid.
Here is my suggestion:
FluidValue

I believe the name AsyncLocalStorage came from the concept in C# called ThreadLocalStorage.

C# also have AsyncLocal, and I believe the name is coming from ThreadLocal.

From what I gather, in scheme and its variants, this concept is called a fluid.

I tried looking up fluid scopes when Mark was talking about it in SES, and all I could find were esoteric CS papers and scheme. I'd really like to avoid this naming.

they introduced ScopedValue which is very similar in both syntax and goals

I wouldn't be opposed to ScopedValue, with the mapping of all values being a ScopedContext. Similar for AsyncLocal. I'm not going to call the individual items "storage".

after thinking through the motivation, I think we should avoid referencing TLS and its various names, as TLS is a different concept, though frequently confused with this space. TLS doesn't solve the problem of implicit information moving through an event loop, it handles the case of local information for a single thread and in a language like LISP, it looks like the same problem. However in JS the equivalent solution to this are globals on worker threads. It is a different genealogy than the one leading to the problem.
A couple of suggestions for naming:

Capture, on it's own or as a prefix (CapturedValue, CapturedBinding, CaptureMap) -- argument here is what we are doing is taking a selection of implicit values and propagating them. This is similar to captured bindings in c++, where an anonymous function by default does not have implicit or explicit values from it's outer scope, you have to pass them in intentionally. The name Capture communicates that we are not saving the entire context, but selecting what information we are passing through. The relationship with c++ may be a problem however, many people feel strongly about the language. This can also be used in combination with Scope or async, such as or ScopeCapture, AsyncCapture.
Conveyance which shu mentioned partially in jest also gets the idea of what is happen across. We are crossing the event loop barrier, so to speak, and we want to convey information from one call stack to another.  ConveyanceBinding or ConveyanceValue could also work -- the problem here is it is verbose and may be challenging to non-fluent english speakers.
SustainedValue -- similar benefits to capture, but without the history. It indicates a value persisted over time.
Ancestor along with AncestorValue -- not ... great. But this is bikeshedding so.
IncumbentValue -- I don't expect this one to be taken too seriously ;)

I am somewhat against the use of Dynamic in part because one of the reasons to select dynamic is to obfuscate the meaning (see dynamic programming) and the other is that it doesn't help with understanding the concept. Fluid is similarly problematic, it has great aesthetics but doesn't describe what is going on.
I am pretty ok with ScopedValue except for the muddying of the distinction that exists between implicit values from the call stack and explicit values from the function scope -- this can be confusing when we talk about the scope -- we are really capturing information from a scope higher up on the call stack. That said, the location where we do the capture is the ancestor scope in question. So, also a good name.

I ran the full thread through gpt 4 again 😬 and I'm sharing it here because I think it's insightful, especially for bikeshedding purposes:

After reviewing the thread, it appears that there are a number of different naming suggestions with various pros and cons. My thoughts on the naming options discussed are:

Context: As mentioned, this name can be broad and potentially confusing. It might be best to avoid it to prevent collisions with other concepts.
AsyncLocal: This name has roots in C# and could work, but may not be the most descriptive option.
AsyncContextEntry: This name emphasizes the map-like nature of the concept, but it might be too long and not as intuitive.
AsyncScope, AsyncState, AsyncCarrier, etc.: These names suggested by ChatGPT seem to emphasize different aspects of the proposal, but may not provide a clear winner.
ScopedValue, DynamicBinding, BoundValue: These suggestions from @lilactown could work, but the distinction between implicit and explicit values could be confusing.
FluidValue: This name has historical roots in Scheme, but it may not be as descriptive or intuitive for those unfamiliar with the background.
Capture, Conveyance, SustainedValue, Ancestor, IncumbentValue: These suggestions from @codehag all have various pros and cons, but may not provide a clear favorite.

Given the various trade-offs, I would suggest considering a combination of the names presented so far, such as "AsyncScopedValue" or "AsyncCaptureValue". This would emphasize both the asynchronous nature of the proposal and the capturing of values from the scope. However, it is important to ensure that the chosen name effectively communicates the concept to developers and avoids confusion with other features or concepts in the language.

When I first heard about AsyncLocalStorage, it wasn't clear what it should be used for. When I heard about the AsyncContext proposal, it immediately made sense and mapped to a problem I'd seen (accessing context down a chain of async operations). Seems like a pretty good name! 😄

Maybe it's enough to distinguish between an individual value and the global mappings? In my initial design AsyncContext was a namespace with a AsyncContext.Value class. So you'd have async context "values", and the overall mappings were the "async context".

I'm supportive of distinguishing an individual instance and the global mappings, regarding https://github.com/tc39/proposal-async-context/issues/21.
I'd avoid the term "dynamic" or "fluid" as they don't help to understand the concept productively. Async-"LocalStorage" is not a good term for the web platform too as it may suggest relations to the LocalStorage API.
A class in the namespace AsyncContext sounds like a good alternative. However, I find Variable or Binding better describes the instance that can be mapped to different values in distinct async control flow, than Value does.

Note, Python use the name "contextvars" as module/namespace, and have classes ContextVar, Context (and Token which could be used to reset the var). See https://peps.python.org/pep-0567/ for details.

I'd consider renaming AsyncContext to AsyncVariable (since an instance stands for a single variable--AsyncLocal or AsyncState or AsyncValue are reasonable alternatives), and using the term AsyncContext for AsyncResource/AsyncContext.Snapshot, as discussed in other issues like #21 .

During today's meeting, we decided to introduce new naming. We'll need to settle the exact names naming, but we're aligned with changing the proposal in a way that should solve this issue.

"Local" (or "Variable", or "Value", etc), which is a individual value
"Context", which is the overall mapping of all individual values

This ties into #21 a bit. We'll be introducing 2 new classes, one to represent a value and one to represent a snapshot of the current context. So we could have a AsyncLocal class, and a AsyncSnapshot class (which is an opaque object representing the current context).


Workaround for jobs failing with missing S3 credentials

Apparently it's a known problem: https://github.com/jtblin/kube2iam/issues/136

Pull Request Test Coverage Report for Build 1728

5 of 6 (83.33%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.005%) to 66.828%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

training/tasks/train.js
2
3
66.67%

Totals

Change from base Build 1718:
0.005%

Covered Lines:
6758

Relevant Lines:
9514

💛  - Coveralls


New design

@bebraw I asked Martin to help out with the design. Can you please check it and merge if everything is fine?

It's a good design especially on desktop resolution.
The problem is that in its current form it doesn't scale to smaller resolutions. It would be good to make the design responsive before merging so our mobile users get good user experience as well.

While it was designed for desktops and tablets, it doesn't look bad on mobile either - definitely not worse than the current site.

I also doubt our website is useful for mobile users

Feedback from designer:

The white separation lines are missing in Uptime chart
In the latency chart the tooltip is not centered but a bit to the right.
On 960px width you change the partners logos (class="partner") to margin: 1em
http://<IP_ADDRESS>:8090/resources/how-cdns-work missing the white background like everywhere

http://<IP_ADDRESS>:8090/resources/how-cdns-work

It would be good to fix the maximum content width for these pages. Perhaps fix maximum width between 700-900px to keep it readable.

@jimaek thanks for the feedback. 2 - 4 are fixed. The white lines are missing on purpose - it'd be somewhat more complicated and you set to keep it as simple as possible.
@bebraw done.

Looks good to me

It's alright. Let's merge and go with this.


[QUERY] Project setup questions for new RP

Query/Question
I'm setting up a new SDK for ImageBuilder RP. Swagger: link
I'm following README to set up a new SDK folder and generate c# code, however I'm hitting two problems. My fork and branch: link. Please help. Thanks.

Unable to generate code using ./generate.ps1. I run the command for other RP (like Compute) and no problem with that, but with out RP, I got this error (see below). Later I found out this error is thrown by autorest, confirmed by running cmd.exe /c autorest.cmd https://github.com/Azure/azure-rest-api-specs/blob/master/specification/imagebuilder/resource-manager/readme.md --csharp --version=latest --reflect-api-versions --csharp-sdks-folder=F:\azure-sdk-for-net\src\SDKs alone. I had to circumvent this issue by cloning the swagger to local and serve it to autorest.

"
AutoRest installed successfully.
Commencing code generation
Generating CSharp code
Executing AutoRest command
cmd.exe /c autorest.cmd https://github.com/Azure/azure-rest-api-specs/blob/master/specification/imagebuilder/resource-manager/readme.md --csharp --version=latest --reflect-api-versions --csharp-sdks-folder=F:\azure-sdk-for-net\src\SDKs
AutoRest code generation utility [version: 2.0.4283; node: v10.15.3]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
Loading AutoRest core      'C:\Users\user.autorest@microsoft.azure_autorest-core<EMAIL_ADDRESS>(2.0.4302)
Loading AutoRest extension<EMAIL_ADDRESS>(~2.3.79->2.3.82)
Loading AutoRest extension<EMAIL_ADDRESS>(2.3.55->2.3.55)
Write-ErrorLog :   Error: Cannot write data to 'https://github.com/Azure/azure-rest-api-specs/blob/master/specification/imagebuilder/resource-manager/generated/ImageBuilderClient.cs'. Protocol 'https:' not supported for writing. Make sure to specify a local, absolute
path as target file/folder.
At C:\Users\user\Documents\WindowsPowerShell\Modules\CodeGenerationModules\AutoRestCodeGenerationModule\AutoRestCodeGenerationModule.psm1:96 char:5
"

After I have the proj file ready I cannot build it. Similar to this issue #5038. Sadly I don't see any solution there. Error:

"
F:\azure-sdk-for-net\tools\SdkBuildTools\targets\ideCmd.targets(20,3): error MSB4018: System.IO.FileLoadException: Could not load file or assembly 'Microsoft.Azure.Management.ImageBuilder, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf385
6ad364e35' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A) [F:\azure-sdk-for-net\src\SDKs\ImageBuilder\Management.ImageBuilder\Microsoft.Azure.Management.ImageBuilder.csproj]
F:\azure-sdk-for-net\tools\SdkBuildTools\targets\ideCmd.targets(20,3): error MSB4018: File name: 'Microsoft.Azure.Management.ImageBuilder, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35' ---> System.Security.SecurityException:
Strong name validation failed. (Exception from HRESULT: 0x8013141A) [F:\azure-sdk-for-net\src\SDKs\ImageBuilder\Management.ImageBuilder\Microsoft.Azure.Management.ImageBuilder.csproj]
"
Why is this not a Bug or a feature Request?
I think I need help with the setup. If anything not documented discovered later, we could update README.
Setup (please complete the following information if applicable):

OS: Windows
IDE : VS2017
Version of the Library used: AutoRest code generation utility [version: 2.0.4283; node: v10.15.3]

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Query Added
[x] Setup information Added

CC: @shahabhijeet

Hi Feiyu, we are sorry for late response. As for the autorest issue, please add -SdkGenerationDirectory "$PSScriptRoot\Generated" in your generate.ps1; or equivently, specify a --csharp.output-folder=C:\sdk option to autorest.cmd.
If you have other questions concerning C# management plane SDK, please contact azdevxdotnet "at" microsoft.com . Thank you :)

thank you! it worked.


Needed gap between buttons in Text Buttons

There is need of gap between the button, currenlty they are sticked to other without any space in-between them.
Reproduce the issue

visit this link  https://sundarui.vercel.app/components/buttons/text-buttons

Screenshot

I can do that..Assign me


Can I use bip39 and Mnemonic wallets?

Hi,
can I use with your project bip39 and Mnemonic wallets?

No, IIRC, Bitcoin Core generates random private keys to be used as receiving and change addresses, contrary to deterministic (BIP39) wallets that can generate an unlimited number of addresses on the fly.
@GeorgeKimionis might have a better idea though.

hmm do you have an example how to generate random private keys for DASH?

No, I don't have one. (Closing this as it isn't an issue per se. Feel free to add comments to it, or reopen it.)


Describe how to add standalone techdocs

Description
The documentation regarding creating and publishing new techdocs refers to a documentation template that no longer seems to exist. At least it isn't created by create-app and the link the documentation points to also doesn't have the template.
I wasted a couple of hours trying to find out how to create standalone documentation and decided to document the minimal steps needed to set it up manually.
If the documentation template still exists, please point me to the new location and I can update the link. Maybe it would make sense to leave my little guide anyway in case someone wants to set it up themselves.
Changeset
Just documentation

Shoot, looks like that last commit wasn't signed

@awanlin yep, I'm on it. Prettier issues should be fixed now too and I squashed and signed-off my commits.


load/save_model for ML models

Propose two processes load_model and save_model to load and store ML models. Should be similar to load_results with loading from job id and URL. The input could be STAC items described with the (upcoming) ml-model extension: https://github.com/stac-extensions/ml-model

I guess this is the metadata spec that we're referring to:
https://github.com/radiantearth/geo-ml-model-catalog
?

The Geo-ML-Model-Catalog was the first attempt from Radiant to write this specification not based on STAC, but this evolved somehow into a work-in-progress STAC extension: https://github.com/stac-extensions/ml-model
I'll check with Jon what the long-term plan is with the Geo-ML-Model-Catalog repo is.

The STAC extension one is now the main repo. The GMLMC one will be archived after we [have] transfer[ed] everything.

@jdries @aljacob Do you have an idea what metadata would be minimally required for our use case?

Really minimally, the model just needs a name. But we'll probably also specify the type of model file, so we can determine if it's compatible with our software.

Thanks and good to know, but I guess I should have asked what you need minimally (so that I can ensure this is at least available) and what other information would be useful in addition? @jdries
From what you have listed right now, we may not really need a model extension yet.

The name is either the STAC id and/or title.
The generating software could be exposed via the processing extension although you'd run into issues if the software can generate multiple types so maybe a model file type would need to be part of a new extension. Looking at standardization: How could we ensure that model types match between implementations? Like is there a common name for each model type that we could refer to? Otherwise, implementations may choose different type names although they refer to the same thing.


Explain how to find channel arguments in our doc

Using channel arguments is always a confusing topic for gRPC Python users. Current documentation doesn't explain where are the available channel arguments. This PR links grpc_types.h to channel arguments. I didn't use permlink because this list might update, so the link to grpc_types.h is generated based on current version.
User question: yaqs/5503784213151744

Known failure: https://github.com/grpc/grpc/issues/22760


Updated perforce to version 2016.1.1411799

DO NOT CREATE NEW PULL REQUESTS ON THIS REPOSITORY!
Please create new pull requests at https://github.com/caskroom/homebrew-cask

You were beaten to it by a few days I'm afraid. Merged https://github.com/Homebrew/homebrew-binary/commit/c0ffb238d783c8f7202e82877da3eee752319dc6. Thanks for the submission nonetheless ❤.


hf_hub_url not giving appropriate URL

Describe the bug
I uploaded a video stored as a NumPy array to the hub: https://huggingface.co/datasets/hf-internal-testing/spaghetti-video.
However, when using hf_hub_url to give me the appropriate URL as follows:
from huggingface_hub import hf_hub_url

hf_hub_url("hf-internal-testing/spaghetti-video", filename="eating_spaghetti.npy")

I doesn't give me the appropriate URL: https://huggingface.co/hf-internal-testing/spaghetti-video/resolve/main/eating_spaghetti.npy. When clicking on this link, one gets a "Repository not found" error.
It seems that the appropriate URL is https://huggingface.co/datasets/hf-internal-testing/spaghetti-video/resolve/main/eating_spaghetti.npy
Reproduction
from huggingface_hub import hf_hub_url

hf_hub_url("hf-internal-testing/spaghetti-video", filename="eating_spaghetti.npy")

Logs
/

System Info
Using huggingface_hub v0.7.0 in Google Colab

hf_hub_url by default expects a model repo. You can add repo_type="dataset" when using a dataset repo, and then you would get the right url.

My bad, indeed, just discovered I had to use datasets/hf-internal-testing/spaghetti-video as the repo name.
Maybe this could be added to the docs?

Yes, I think that's a good idea! Would you like to open a small PR for it?


NBody wall kernels lose SPD property close to a wall

For this plot, I took a single particle at different heights approaching a bottom wall with DPStokes and NBody and applied only forces, then used the same procedure as in the fluctuation dissipation test to compute the full mobility matrix. This plot is the smallest eigenvalue of that 3x3 matrix. The plot shows that the NBody eigenvalues seem to become unbounded as the particle goes toward the wall.
I noticed this because there are times when the NBody wall kernels produce NaNs in the guesses while iterating in the Lancoz algorithm. This is configuration dependent and seemingly only depends on the distance between the wall and the closest particle.
I squinted at the NBody wall kernel for UF and it looked okay compared to the formulas in the Brady/Swan paper, but haven't investigated much further to see what's causing it.

I wonder if this is a bug in the code or a limitation of the theory that's being used in NBody.
What is the scale in X here? units of "a" I reckon?

Yup, the x-axis is in units of a!
I had the same question. The Swan/Brady paper declares that the corrections are SPD by construction but doesn't provide explicit proof. I wouldn't be shocked if this is a limitation of the theory since the Green's function for the wall is from Blake and uses the image system in the construction, but I don't know enough to say for certain.
If it's a bug in the code it's been around for a while since I believe these are tested against the old Python implementations from RigidMultiBlobs

This plot was made using double precision, and the results were visually identical between precisions. Accumulation of error is possible, but it starts happening for values of h that seemingly aren't that small numerically. Do you have any suggestions to look into? I'll keep thinking about it as well!

I do not think it is accumulation of error then. Assuming there is an error, given that there is only one particle, I reckon it should be in this code:
https://github.com/stochasticHydroTools/libMobility/blob/4dafab7f863842b5332e45cd3fdc78ce4cd4492a/solvers/NBody/extra/hydrodynamicKernels.cuh#L164-L173

Try to run it with a=1 and viscosity = 1/(6pi). The article states that correction formulas are normalized by 6pietaa^n, maybe the a^n part is being introduced incorrectly in this case?


Parsing of \verb

Not sure these issues are too serious, but just for the record...
The following command is allowed in LaTeX but not accepted by MathJax:
\sqrt{\verb!}!}
The following command does not work either in MathJax. When I try it with a latex program I get "LaTeX Error: \verb illegal in command argument."
\sqrt[\verb!]!]

==> In Testsuite
LaTeXToMathML/issue375.html


Haversine calculation could be more precise

Description
I noticed that our haversine function in regionalisation.py gives very different values from what I expect. https://github.com/CSHS-CWRA/RavenPy/blob/cda72b97e8b49f77e807bdf80b1fb6b8c5c08bb1/ravenpy/utilities/regionalization.py#L198
In other projects, I've used https://github.com/mapado/haversine to estimate this value. As a smoke test, I tried the example from the readme using our version:
# Our version
raven_haversine(*lyon, *paris)
>><PHONE_NUMBER>3187857 # Km's

# Haversine library
haversine(lyon, paris)
>><PHONE_NUMBER>594006 # Km's

I think it would be good to replace this function with the one offered by the Haversine library.

Closed with #124


[PSM Interop] Fail test if client or server pods restarted during test

Fail test if client or server pods restarted during test.
Testing
Tested locally, test will fail with message similar to:
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/local/google/home/xuanwn/workspace/xds/grpc/tools/run_tests/xds_k8s_test_driver/framework/xds_k8s_testcase.py", line 501, in tearDown
    ))
AssertionError: 5 != 0 : Server pods unexpectedly restarted {sever_restarts} times during test.

----------------------------------------------------------------------
Ran 1 test in 886.867s

Adhoc tests:

[ ] grpc/core/v1.54.x/branch/linux/grpc_xds_k8s_lb
[ ] grpc/core/v1.54.x/branch/linux/psm-security
[ ] grpc/core/v1.54.x/branch/linux/grpc_xds_url_map


[dataframe] update version of dataframe

Describe the pull request
update version of dataframe from 1.12.0 to 1.17.0

What does your PR fix?
None

Which triplets are supported/not supported? Have you updated the CI baseline?
All, No

Does your PR follow the maintainer guide?

Yes

Thanks @westfly !


Error handling issues

Duplicated mapping key error
Other general errors

If there is an error, it would be nice to know exactly where (on line or id) where it crashes, in which file (setup, or test)


Hi @mteodor I'm using code on v0.11.0 bracnh

in docker-compose.yml
add following change
instead of
image: mainflux/auth:latest
put
image: mainflux/auth:0.11.0
auth service is given as an example, yuo should do the same for all mainflux services

I have changed image version in docker-compose file as you suggested but it still not work

ah, sorry, you will have to build your own images
first do cleanup
make cleandocker
than
make dockers
and then start composition

@BuiVanDuc Check the name of the services because they changed since 0.11.0
Try with mainflux/authn:l0.11.0

now I double checked, yes there are tags for 0.11.0 so replacement solution must work
( I made a mistake and looked into auth service which is released after 0.11.0 and has only latest, auth service replaces authn )
additionally you have to start docker composition from the project directory as docker-comopse relies on .env file for reading environment variables

I did a workaround and I able to run 'make run' command.
The solution will be moving '.env' file from ./mainflux to ./mainflux/docker folder. Then you just have to redirect back to ./mainflux and run the 'make run' command.

Content of the docker-compose.yml
# Copyright (c) Mainflux
# SPDX-License-Identifier: Apache-2.0

version: "3.7"

networks:
  mainflux-base-net:
    driver: bridge

volumes:
  mainflux-authn-db-volume:
  mainflux-users-db-volume:
  mainflux-things-db-volume:
  mainflux-things-redis-volume:
  mainflux-es-redis-volume:
  mainflux-mqtt-broker-volume:

services:
  nginx:
    image: nginx:1.16.0-alpine
    container_name: mainflux-nginx
    restart: on-failure
    volumes:
      - ./nginx/nginx-${AUTH-key}.conf:/etc/nginx/nginx.conf.template
      - ./nginx/entrypoint.sh:/entrypoint.sh
      - ./nginx/snippets:/etc/nginx/snippets
      - ./ssl/authorization.js:/etc/nginx/authorization.js
      - ./ssl/certs/mainflux-server.crt:/etc/ssl/certs/mainflux-server.crt
      - ./ssl/certs/ca.crt:/etc/ssl/certs/ca.crt
      - ./ssl/certs/mainflux-server.key:/etc/ssl/private/mainflux-server.key
      - ./ssl/dhparam.pem:/etc/ssl/certs/dhparam.pem
    ports:
      - ${MF_NGINX_HTTP_PORT}:${MF_NGINX_HTTP_PORT}
      - ${MF_NGINX_SSL_PORT}:${MF_NGINX_SSL_PORT}
      - ${MF_NGINX_MQTT_PORT}:${MF_NGINX_MQTT_PORT}
      - ${MF_NGINX_MQTTS_PORT}:${MF_NGINX_MQTTS_PORT}
    networks:
      - mainflux-base-net
    env_file:
      - ../.env
    command: /entrypoint.sh
    depends_on:
      - things
      - users
      - mqtt-adapter
      - http-adapter

  nats:
    image: nats:1.3.0
    container_name: mainflux-nats
    command: "-c /etc/nats/nats.conf"
    restart: on-failure
    volumes:
      - ./nats/:/etc/nats
    networks:
      - mainflux-base-net

  authn-db:
    image: postgres:10.8-alpine
    container_name: mainflux-authn-db
    restart: on-failure
    environment:
      POSTGRES_USER: ${MF_AUTHN_DB_USER}
      POSTGRES_PASSWORD: ${MF_AUTHN_DB_PASS}
      POSTGRES_DB: ${MF_AUTHN_DB}
    networks:
      - mainflux-base-net
    volumes:
      - mainflux-authn-db-volume:/var/lib/postgresql/data

  authn:
    image: mainflux/authn:0.11.0
    container_name: mainflux-authn
    depends_on:
      - authn-db
    expose:
      - ${MF_AUTHN_GRPC_PORT}
    restart: on-failure
    environment:
      MF_AUTHN_LOG_LEVEL: ${MF_AUTHN_LOG_LEVEL}
      MF_AUTHN_DB_HOST: authn-db
      MF_AUTHN_DB_PORT: ${MF_AUTHN_DB_PORT}
      MF_AUTHN_DB_USER: ${MF_AUTHN_DB_USER}
      MF_AUTHN_DB_PASS: ${MF_AUTHN_DB_PASS}
      MF_AUTHN_DB: ${MF_AUTHN_DB}
      MF_AUTHN_HTTP_PORT: ${MF_AUTHN_HTTP_PORT}
      MF_AUTHN_GRPC_PORT: ${MF_AUTHN_GRPC_PORT}
      MF_AUTHN_SECRET: ${MF_AUTHN_SECRET}
      MF_JAEGER_URL: ${MF_JAEGER_URL}
    ports:
      - ${MF_AUTHN_HTTP_PORT}:${MF_AUTHN_HTTP_PORT}
      - ${MF_AUTHN_GRPC_PORT}:${MF_AUTHN_GRPC_PORT}
    networks:
      - mainflux-base-net

  users-db:
    image: postgres:10.8-alpine
    container_name: mainflux-users-db
    restart: on-failure
    environment:
      POSTGRES_USER: ${MF_USERS_DB_USER}
      POSTGRES_PASSWORD: ${MF_USERS_DB_PASS}
      POSTGRES_DB: ${MF_USERS_DB}
    networks:
      - mainflux-base-net
    volumes:
      - mainflux-users-db-volume:/var/lib/postgresql/data

  users:
    image: mainflux/users:0.11.0
    container_name: mainflux-users
    volumes:
      - ./users/emailer/templates/${MF_EMAIL_TEMPLATE}:/${MF_EMAIL_TEMPLATE}
    depends_on:
      - users-db
      - authn
    restart: on-failure
    environment:
      MF_USERS_LOG_LEVEL: ${MF_USERS_LOG_LEVEL}
      MF_USERS_DB_HOST: users-db
      MF_USERS_DB_PORT: ${MF_USERS_DB_PORT}
      MF_USERS_DB_USER: ${MF_USERS_DB_USER}
      MF_USERS_DB_PASS: ${MF_USERS_DB_PASS}
      MF_USERS_DB: ${MF_USERS_DB}
      MF_USERS_HTTP_PORT: ${MF_USERS_HTTP_PORT}
      MF_JAEGER_URL: ${MF_JAEGER_URL}
      MF_EMAIL_DRIVER: ${MF_EMAIL_DRIVER}
      MF_EMAIL_HOST: ${MF_EMAIL_HOST}
      MF_EMAIL_PORT: ${MF_EMAIL_PORT}
      MF_EMAIL_USERNAME: ${MF_EMAIL_USERNAME}
      MF_EMAIL_PASSWORD: ${MF_EMAIL_PASSWORD}
      MF_EMAIL_FROM_ADDRESS: ${MF_EMAIL_FROM_ADDRESS}
      MF_EMAIL_FROM_NAME: ${MF_EMAIL_FROM_NAME}
      MF_EMAIL_TEMPLATE: ${MF_EMAIL_TEMPLATE}
      MF_TOKEN_RESET_ENDPOINT: ${MF_TOKEN_RESET_ENDPOINT}
      MF_AUTHN_GRPC_URL: ${MF_AUTHN_GRPC_URL}
      MF_AUTHN_GRPC_TIMEOUT: ${MF_AUTHN_GRPC_TIMEOUT}
    ports:
      - ${MF_USERS_HTTP_PORT}:${MF_USERS_HTTP_PORT}
    networks:
      - mainflux-base-net

  things-db:
    image: postgres:10.8-alpine
    container_name: mainflux-things-db
    restart: on-failure
    environment:
      POSTGRES_USER: ${MF_THINGS_DB_USER}
      POSTGRES_PASSWORD: ${MF_THINGS_DB_PASS}
      POSTGRES_DB: ${MF_THINGS_DB}
    networks:
      - mainflux-base-net
    volumes:
      - mainflux-things-db-volume:/var/lib/postgresql/data

  things-redis:
    image: redis:5.0-alpine
    container_name: mainflux-things-redis
    restart: on-failure
    networks:
      - mainflux-base-net
    volumes:
      - mainflux-things-redis-volume:/data

  things:
    image: mainflux/things:0.11.0
    container_name: mainflux-things
    depends_on:
      - things-db
      - authn
    restart: on-failure
    environment:
      MF_THINGS_LOG_LEVEL: ${MF_THINGS_LOG_LEVEL}
      MF_THINGS_DB_HOST: things-db
      MF_THINGS_DB_PORT: ${MF_THINGS_DB_PORT}
      MF_THINGS_DB_USER: ${MF_THINGS_DB_USER}
      MF_THINGS_DB_PASS: ${MF_THINGS_DB_PASS}
      MF_THINGS_DB: ${MF_THINGS_DB}
      MF_THINGS_CACHE_URL: things-redis:${MF_REDIS_TCP_PORT}
      MF_THINGS_ES_URL: es-redis:${MF_REDIS_TCP_PORT}
      MF_THINGS_HTTP_PORT: ${MF_THINGS_HTTP_PORT}
      MF_THINGS_AUTH_HTTP_PORT: ${MF_THINGS_AUTH_HTTP_PORT}
      MF_THINGS_AUTH_GRPC_PORT: ${MF_THINGS_AUTH_GRPC_PORT}
      MF_THINGS_SECRET: ${MF_THINGS_SECRET}
      MF_JAEGER_URL: ${MF_JAEGER_URL}
      MF_AUTHN_GRPC_URL: ${MF_AUTHN_GRPC_URL}
      MF_AUTHN_GRPC_TIMEOUT: ${MF_AUTHN_GRPC_TIMEOUT}
    ports:
      - ${MF_THINGS_HTTP_PORT}:${MF_THINGS_HTTP_PORT}
      - ${MF_THINGS_AUTH_HTTP_PORT}:${MF_THINGS_AUTH_HTTP_PORT}
      - ${MF_THINGS_AUTH_GRPC_PORT}:${MF_THINGS_AUTH_GRPC_PORT}
    networks:
      - mainflux-base-net

  jaeger:
    image: jaegertracing/all-in-one:1.13
    container_name: mainflux-jaeger
    ports:
      - ${MF_JAEGER_PORT}:${MF_JAEGER_PORT}/udp
      - ${MF_JAEGER_FRONTEND}:${MF_JAEGER_FRONTEND}
      - ${MF_JAEGER_COLLECTOR}:${MF_JAEGER_COLLECTOR}
      - ${MF_JAEGER_CONFIGS}:${MF_JAEGER_CONFIGS}
    networks:
      - mainflux-base-net

  vernemq:
    image: mainflux/vernemq:0.11.0
    container_name: mainflux-vernemq
    restart: on-failure
    environment:
      DOCKER_VERNEMQ_ALLOW_ANONYMOUS: ${MF_DOCKER_VERNEMQ_ALLOW_ANONYMOUS}
      DOCKER_VERNEMQ_LOG__CONSOLE__LEVEL: ${MF_DOCKER_VERNEMQ_LOG__CONSOLE__LEVEL}
    networks:
      - mainflux-base-net
    volumes:
      - mainflux-mqtt-broker-volume:/var/lib/vernemq

  mqtt-adapter:
    image: mainflux/mqtt:0.11.0
    container_name: mainflux-mqtt
    depends_on:
      - vernemq
      - things
      - nats
    restart: on-failure
    environment:
      MF_MQTT_ADAPTER_LOG_LEVEL: ${MF_MQTT_ADAPTER_LOG_LEVEL}
      MF_MQTT_ADAPTER_MQTT_PORT: ${MF_MQTT_ADAPTER_MQTT_PORT}
      MF_MQTT_ADAPTER_WS_PORT: ${MF_MQTT_ADAPTER_WS_PORT}
      MF_MQTT_ADAPTER_ES_URL: es-redis:${MF_REDIS_TCP_PORT}
      MF_NATS_URL: ${MF_NATS_URL}
      MF_MQTT_ADAPTER_MQTT_TARGET_HOST: vernemq
      MF_MQTT_ADAPTER_MQTT_TARGET_PORT: ${MF_MQTT_BROKER_PORT}
      MF_MQTT_ADAPTER_WS_TARGET_HOST: vernemq
      MF_MQTT_ADAPTER_WS_TARGET_PORT: ${MF_MQTT_BROKER_WS_PORT}
      MF_JAEGER_URL: ${MF_JAEGER_URL}
      MF_THINGS_AUTH_GRPC_URL: ${MF_THINGS_AUTH_GRPC_URL}
      MF_THINGS_AUTH_GRPC_TIMEOUT: ${MF_THINGS_AUTH_GRPC_TIMEOUT}
    networks:
      - mainflux-base-net

  http-adapter:
    image: mainflux/http:0.11.0
    container_name: mainflux-http
    depends_on:
      - things
      - nats
    restart: on-failure
    environment:
      MF_HTTP_ADAPTER_LOG_LEVEL: debug
      MF_HTTP_ADAPTER_PORT: ${MF_HTTP_ADAPTER_PORT}
      MF_NATS_URL: ${MF_NATS_URL}
      MF_JAEGER_URL: ${MF_JAEGER_URL}
      MF_THINGS_AUTH_GRPC_URL: ${MF_THINGS_AUTH_GRPC_URL}
      MF_THINGS_AUTH_GRPC_TIMEOUT: ${MF_THINGS_AUTH_GRPC_TIMEOUT}
    ports:
      - ${MF_HTTP_ADAPTER_PORT}:${MF_HTTP_ADAPTER_PORT}
    networks:
      - mainflux-base-net

  es-redis:
    image: redis:5.0-alpine
    container_name: mainflux-es-redis
    restart: on-failure
    networks:
      - mainflux-base-net
    volumes:
      - mainflux-es-redis-volume:/data

  coap-adapter:
    image: mainflux/coap:0.11.0
    container_name: mainflux-coap
    depends_on:
      - things
      - nats
    restart: on-failure
    environment:
      MF_COAP_ADAPTER_LOG_LEVEL: ${MF_COAP_ADAPTER_LOG_LEVEL}
      MF_COAP_ADAPTER_PORT: ${MF_COAP_ADAPTER_PORT}
      MF_NATS_URL: ${MF_NATS_URL}
      MF_JAEGER_URL: ${MF_JAEGER_URL}
      MF_THINGS_AUTH_GRPC_URL: ${MF_THINGS_AUTH_GRPC_URL}
      MF_THINGS_AUTH_GRPC_TIMEOUT: ${MF_THINGS_AUTH_GRPC_TIMEOUT}
    ports:
      - ${MF_COAP_ADAPTER_PORT}:${MF_COAP_ADAPTER_PORT}/udp
      - ${MF_COAP_ADAPTER_PORT}:${MF_COAP_ADAPTER_PORT}/tcp
    networks:
      - mainflux-base-net

I'm running on Ubuntu 20.04

@BuiVanDuc what are versions of your docker and docker-compose clients? (docker-compose --version & docker --version)
Maybe you need to upgrade them

Thanks for your help
I tried it out at @mteodor 's suggestion: Here. It work success and I close the issue


Varying results when trying to add BLE key

When adding a the public.pem file to the car with ble, it sometimes works, and sometimes returns this error:
Error: failed to find BLE beacon for VIN (): can't scan: context deadline exceeded
The command is sent with terminal on Mac with this command:
./tesla-control -vin VIN -ble add-key-request public.pem owner cloud_key
Im sitting in the car, so range should not be an issue.

this has been reliable for me from Apple Watch and iPhone

Closing this ticket, but feel free to re-open if you're able to confirm permissions are correct and can still reproduce.


Bottom Panel visibility

I'm writing an extension and I'm struggling with toggling the bottom panel though the API.
I'm able to hide() or show() a terminal that leads to open and close the panel, but there is no toggle() feature or a way to test terminal or panel visibility to call either hide or show.
I saw that the Panel object has a visible member, but I can't find a way to access the panel instance through the API.

Why do you want to test visibility or toggle?

Giving a bit more of context here:
I'm adding a StatusBarItem that watch some terminal activity based on keywords. When user click on the StatusBarItem, it shows the terminal. I would like to hide the terminal with the same action instead of clicking the X.

In order to achieve that I need to know if panel is already visible or not (or a toggle API that would handle it for me).
Note that exactly the same behaviour that the error/warning built-in problems watcher StatusBarItem.

Hi, I am looking to contribute to the repo and this issue looked interesting. Is there a specific file to look into/edit to begin?

We currently do not accept PRs in this area.
Please search for issue tagged with help-wanted. Thank you


Fix shellcheck error SC1075: Use 'elif' instead of 'else if'

This is the only shellcheck error. 4 warnings are still present, I will take of them after.
Perhaps we could configure some CI to run shellcheck ? (a github action maybe?)

github actions for shellcheck and similar sounds good. And the patch looks good too.


Multiple pipelines support for HAL sample

added pipelines support
cleaned up some of the promises code
added detail pages for user and bug
added sample bug 789 in HAL

Big improvement. I like bringing in the Q library here. Also really like your use of .concat to build out the html. :shipit: