question: Validating instruction and stack after terminating opcode

First question: I see that we dont reset the successor_stack_height after termination opcode, this would mean that we would increment its max value. Not sure if this is correct?
Second question: I see in spec that "no instruction may be unreachable", do we validate if opcodes are accessible after RJUMP or termination opcode. i dont see that part in the code, is it maybe covered by code below by making StackHeightRange::max initialise to a big number:
https://github.com/ethereum/evmone/blob/master/lib/evmone/eof.cpp#L520-L521|
Third one: I see that in MegaEOF spec: "Code basic blocks must be ordered in a way that every block is reachable either by a forward jump or sequential flow of instructions. In other words, there is no basic block reachable only by a backward jump."  https://notes.ethereum.org/@ipsilon/mega-eof-specification i can't find this check in code.
validate_rjump_destinations checks validity of jumps but not if it is touching every instruction only with a forward jump.

First question: I see that we dont reset the successor_stack_height after termination opcode, this would mean that we would increment its max value. Not sure if this is correct?

I don't think there is a problem. On termination instruction none of the successor instruction heights are updated (because there are no successors), then when it gets to the next instruction, it must already be visited and current stack height is read from saved earlier value:
https://github.com/ethereum/evmone/blob/7bd7596c2754229f37344e10cdd49d638391f90f/lib/evmone/eof.cpp#L377

Second question: I see in spec that "no instruction may be unreachable", do we validate if opcodes are accessible after RJUMP or termination opcode. i dont see that part in the code, is it maybe covered by code below by making StackHeightRange::max initialise to a big number:

This check covers unreachable code:
https://github.com/ethereum/evmone/blob/7bd7596c2754229f37344e10cdd49d638391f90f/lib/evmone/eof.cpp#L378-L383
All instructions are inspected sequentially, and if we reached an instruction that was not jumped to from earlier code, it is unreachable, due to the rule you mention in third question.

https://github.com/ethereum/evmone/blob/master/lib/evmone/eof.cpp#L520-L521|

This line just finds the max value in stack_heights.

Third one: I see that in MegaEOF spec: "Code basic blocks must be ordered in a way that every block is reachable either by a forward jump or sequential flow of instructions. In other words, there is no basic block reachable only by a backward jump." https://notes.ethereum.org/@ipsilon/mega-eof-specification i can't find this check in code. validate_rjump_destinations checks validity of jumps but not if it is touching every instruction only with a forward jump.

It's basically the same check for unreachable code.
If there is instruction reachable only by backwards jump, when we sequentially inspect every instruction and we reach this instruction, it's stack_height will be still LOC_UNVISITED, so then this code is unreachable according to this rule.

@gumb0 thank you for responding, it helped me figure out what I was missing and understand it better!


Is there a 256 leds limit?

Edit: found out my own mistake and removed the details here in my question!
Answer: no there is no limit but make sure your for loops use 16 bit vars and not uint8_t......

Still there seems to be an issue with more then 255 leds. I have 806 leds and only 38 are received from iCue.
806 = 0011 0010 0110
38 =           0010 0110
It seems that they are not copied from usb to ledChannel0[] array. So probably an uint8_t there somewhere.

Which type of hardware do you use, normally the memory only allows for a total of around 400 LEDs. You can not add that much LEDs via addLeds because iCUE does not support that much leds. You can add for example 135 LEDs, which maps to the maximum which is possible with iCUE LS100 Controller. Then you can scale that to a bigger LED array with the scale functions see https://github.com/Legion2/CorsairLightingProtocol#repeat-or-scale-led-channels


feat(@embark/blockchain): Add support for blockchain plugins

Blockchain clients can be added as plugins now. Existing geth and parity clients are still supported, however additional blockchains can used in your DApp as a plugin.
The blockchain plugin API can be used in the following way:
this.embark.registerBlockchain("lightchain", require.resolve("./client"), {options});

When Embark attempts to start a blockchain process, we first check to see if we have installed a blockchain client plugin, and also check that it's shouldInit function resolves to true.
If the blockchain client plugin is configured in the DApp's blockchain config for the current environment, we create an instance of the client and then run through some initialisation. Before this PR, the initialisation would attempt to create and unlock node accounts before starting up the blockchain process. With this PR, we assume that the CLI for the blockchain client does not support creation and unlocking of accounts from the command line, and instead allow the client to run an init routine before the main process is started.
In addition, we have added a new event, blockchain:provider:ready, that is fired once Embark's web3 provider has been configured and set up. This event will run actions configured with registerActionsForEvent("blockchain:provider:ready") and wait for those actions to complete before continuing. This allows an opportunity for custom blockchain plugins to perform account management before kicking off the blockchain client process. After the actions are finished, the blockchain:ready event will be fired. Because of this, it is important that any blockchain plugins using this event (by default, any that impelement BaseBlockchainPlugin) have a valid shouldInit method that prevents registration of these actions when the blockchain client is not being used by Embark (ie the blockchain config client is not set to the blockchain plugin for the current environment), otherwise the blockchain process may hang.
Implementing a blockchain plugin
This PR introduces two new base classes to assist developers in creating blockchain plugins.
BaseBlockchainPlugin
packages/embark-blockchain-process/baseBlockchainPlugin.ts was implemented as a base class for the blockchain plugin itself. Developers should extend this class when creating blockchain plugins. For example,
import {BaseBlockchainPlugin} from 'embark-blockchain-process';

const BLOCKCHAIN_CLIENT_OPTIONS = {
  defaults: {
    bin: "lightchain",
    networkType: "standalone",
    rpcApi: ['eth', 'web3', 'net', 'debug', 'personal'],
    wsApi: ['eth', 'web3', 'net', 'debug', 'pubsub', 'personal'],
    devWsApi: ['eth', 'web3', 'net', 'debug', 'pubsub', 'personal']
  },
  versSupported: ">=1.3.0",
  versionRegex: "Version: ([0-9]\.[0-9]\.[0-9]).*?",
  name: "lightchain",
  prettyName: "Lightchain (https://github.com/lightstreams-network/lightchain)",
  clientPath: require.resolve("./client")
};

export default class EmbarkLightchain extends BaseBlockchainPlugin {
  constructor(embark) {
    super(embark, BLOCKCHAIN_CLIENT_OPTIONS);
    this.logger = embark.logger;
    this.isDev = embark.config.env === "development";
  }

  async createAndUnlockAccounts() {
    // do node account mgmt here
  }
}

Once extended, developers should override the following methods:

protected async createAndUnlockAccounts(): Creates and unlocks accounts according to the blockchain configuration. Override this method to create a custom account management implementation. If you do not need to create and unlock accounts, override this method in your plugin class, and return immediately. Otherwise, an error will be thrown. This method is fired automatically by the base class in between the blockchain:provider:ready and blockchain:ready events.
protected shouldInit(blockchainConfig: any): Prevents or enables Embark to consider this plugin as a valid plugin at run time. Overridable if needed, the base class implements this method by returning true if the current run time environment's config is using this blockchain plugin's client.

BaseBlockchainClient
packages/embark-blockchain-process/baseBlockchainClient.ts was implemented as a base class for the blockchain client. This class introduces several methods that need to be overridden by the extending class, as can be seen in the embark-lightchain implementation:

public isReady(data: string): Determines whether the blockchain client is ready by examining the stdout output of the main command (determined by {@link mainCommand})
public needKeepAlive(): check if the client needs some sort of 'keep alive' transactions to avoid freezing by inactivity. If true, allows for txs to be sent at regular intervals via the devtxs on console command.
public getMiner(): Gets path to a miner class. If a miner is not needed, override this method and log a warning.
public determineVersionCommand(): Command to execute in the CLI to determine the blockchain client version.
public initChain(callback: Callback<null>): Fired before the main blockchain command is run, the client should use this method to perform any initialization routine that it needs.
public mainCommand(address: string, done: (bin: string, args: string[]) => void): Main command to run in the CLI that starts up the blockchain client process

Events added
blockchain:provider:ready: Fired once Embark's web3 provider has been configured and setup. This is fired before blockchain:ready.
Other notes

This PR is based on the v5 config changes (feat/new-config branch).
This PR will have some conflicts with the ongoing rebase and will need to be implemented slightly differently after the rebase lands.

note: added to pivotal to re-add later in v5


Job Posting Functionality Implementation

Feature: Job Posting Functionality
Closes #37
Closes #51
This PR introduces the core functionality for job posting, including:

Job Entity: Defines the structure of a job.
Job Repository: Provides data access for jobs.
Job Service: Handles job-related business logic.
Job Controller: Exposes REST endpoints for job management.
Job DTO: Defines data transfer objects for jobs.
Security: Implements role-based access control for job operations.

To test:

Start the application.
Send a POST request to /api/jobs/post with a valid JSON payload.
Verify job creation and retrieval.

Please review the code changes and unit tests.

In the job post, the client can add required skills for the job, but you missed implementing that

I think adding the required skills should be implemented in a separate endpoint to avoid complexity and keep the responsibilities of each API call clear and manageable. This approach would make it easier to maintain and extend the functionality if needed.

I think adding the required skills should be implemented in a separate endpoint to avoid complexity and keep the responsibilities of each API call clear and manageable.

I think it’d be a good idea to keep the required skills in the same endpoint. Splitting it into a separate endpoint could make things unnecessarily complicated.
We could let clients select from a list of matching skills, and if they don’t find what they need, they can create a new skill on the spot. This way, we’ll also reduce the number of API calls.

I think adding the required skills should be implemented in a separate endpoint to avoid complexity and keep the responsibilities of each API call clear and manageable.

I think it’d be a good idea to keep the required skills in the same endpoint. Splitting it into a separate endpoint could make things unnecessarily complicated.
We could let clients select from a list of matching skills, and if they don’t find what they need, they can create a new skill on the spot. This way, we’ll also reduce the number of API calls.

ok, i will implement it.

Done @AhmedMohamedAbdelaty  @AhmedYahia74


Ability to configure arbitrary EL variables

WDYT of being able to configure EL variables, that would be a bit like twig global variables:
bazinga_hateoas:
    expression_language:
        context_variables:
            base_rel: https://rels.example.com
            foo: bar

To then be able to:
/**
 * @Hateoas\Relation("expr(base_rel ~ '/users')", ...)
 */

If https://github.com/willdurand/BazingaHateoasBundle/issues/24 is a duplicate of https://github.com/willdurand/BazingaHateoasBundle/issues/13 and is closed, then we should consider closing Ability to configure arbitrary EL variables #13 (the current issue) as well.


Update browser_manipulation.en.md

C # comment line syntax correction

Why was this closed?

Hi, @diemol  I accidentally closed. I added it to other languages and made a pull request again. Pull request No: # 362. You can access it here. Thanks


How to use API to resolve DIDDoc?

I see the resolve DID endpoint: [/resolver/resolve/{did}]. But, I am trying to understand how I can resolve DIDDoc of verifier when holder gets a request from the verifier , they can verify if the verifier is legit. Or, holder can verify if a credential issuer is legit.

You have several things here:

Right now, the resolver only allows the resolution of public DIDs -- e.g. DIDs that have been published on a ledger.  If you have a connection with a verifier, you likely are using a private DID for that -- a did:peer that is shared only between the verifier and you. At this time, you can't access that information as a DID (although you should be able to!!), but you can get the information from the connection record.
If the establishment of the connection started from a public DID, then that public DID should be in the connection record and you can get it from then resolve using the API call.
The question of "how can I verify the verifier is legit" -- depends on what you trust as "legit" in your context.  It may be that the connection started from a Public DID (see above) and that you have a list of DIDs you trust.  Or, you could request a proof of a VC from the verifier.  There is nothing inherent in the connection or the DID that lets you "trust" the verifier.

Hope that helps. Closing assuming it does, but feel free to ask more questions or re-open.


npm package is out of date

the npm package is out of date https://www.npmjs.com/package/fetch-event-source

the npm package is 1.0.0-alpha.2 published 9 months ago
the latest tagged release is v2.0.1 published 3 months ago

there is a different/newer package under a different name https://www.npmjs.com/package/@microsoft/fetch-event-source


[Webpack Plugin] Support add [hashcontent] to file name.

Is your feature request related to a problem? Please describe.
Currently with webpack config like below, a file with the name styles.css is created after the build.

Describe a solution you'd like
I'm expecting a hashcontent will be added to the file name according to the webpack output.filename config to resolve the caching issue.
Describe alternatives you've considered
Or can @stylexjs/webpack-plugin support add [hashcontent] to the filename config? like this:
new StylexPlugin({
      filename: 'styles.[hashcontent].css',
}),

This is a known issue and something we've been unable to prioritise so far. Would appreciate a PR for this.

i will work on it

Since there are no updates, I'd like to work on this.

I'm happy to accept whichever PR comes first, so @pramodgoud7 if you've made progress on this, you should let @Afterdie know so one of you doesn't end up wasting your time.

Hi guys! I pulled the latest code and ran npm run build -w webpack-example but it still not working.

Ah.. I was looking at the wrong place for build files my bad.

I'll look into it.


Invalid example setting collection->SomeStrings = new Collection

In the example, the code shows   collection->SomeStrings = newCollection; But the class indicates the property setter violates the warning. I believe the example should remove the line of code "collection->SomeStrings = newCollection;" as it is not needed. The Clear and AddRange will set the SomeStrings value.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8db6af07-b7d6-9395-223e-1a0f83fb2405
Version Independent ID: 5ee87730-ff01-2571-494e-91d29c5fe211
Content: CA2227: Collection properties should be read only - Visual Studio
Content Source: docs/code-quality/ca2227-collection-properties-should-be-read-only.md
Service: unspecified
GitHub Login: @gewarren
Microsoft Alias: gewarren

@colbroth thank you for the feedback! I will look into this.

@colbroth I looked at this a little more closely, and while it probably could be made more clear in the code comments, I think the example was intentionally written that way. It's trying to show that if the collection property is not read only, the entire collection can be replaced in that line of code. I'll update the code comments to make this more clear.


[Rust] Use schema semantic version to populate Rust crate version.

Not sure if this is something you would be willing to accept.

It is common for SBE schemas to use a FIX version name or $major.$minor, e.g., in Aeron Archive's SBE schema, as the messageSchema#semanticVersion. The SBE specification doesn't specify any particular format for the semanticVersion attribute value. Therefore, it would be best not to expect a particular format in the code generator.
From all the file changes, I assume you need to output in x.y.z format?
Please can you make the code generator more lenient and reduce the number of changes across existing schema files?
You could consider using a system property to specify the crate version instead of using the semanticVersion attribute value. I suspect there are cases where the crate version may change, e.g., when you upgrade the SBE code generator, but the schema does not.

From all the file changes, I assume you need to output in x.y.z format?

Exactly.

Please can you make the code generator more lenient and reduce the number of changes across existing schema files?

Done.

You could consider using a system property to specify the crate version instead of using the semanticVersion attribute value. I suspect there are cases where the crate version may change, e.g., when you upgrade the SBE code generator, but the schema does not.

Makes sense.  What about this?


[Bug]: Unable to serialize to JSON

Contact Details
<EMAIL_ADDRESS>What happened?
Hi, When Updated to the latest version of Olarm integration everything stopped working. When I try and add the integration I get this error? Am I missing something. Running version 2.2.5
Sample of error on front end

Version
2.2.5
Relevant log output form Home Assistant
Logger: homeassistant.components.http.view
Source: components/http/view.py:62
Integration: HTTP ([documentation](https://www.home-assistant.io/integrations/http), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+http%22))
First occurred: 17:33:03 (1 occurrences)
Last logged: 17:33:03

Unable to serialize to JSON. Bad data found at $.errors<key: <class 'str'>>=<class 'str'>(<class 'type'>

Downloaded integration debug logs.
Logger: homeassistant.components.http.view
Source: components/http/view.py:62
Integration: HTTP ([documentation](https://www.home-assistant.io/integrations/http), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+http%22))
First occurred: 17:33:03 (1 occurrences)
Last logged: 17:33:03

Unable to serialize to JSON. Bad data found at $.errors<key: <class 'str'>>=<class 'str'>(<class 'type'>

Hi @rwoeke ,
This seems to be an issue with Home Assistant itself as specified here: homeassistant.components.http.view in the logs. Maybe just try to redownload the integration and check again?

Only way I could get it to work is to redownload as  2.2.2
in other words happen when I upgrade olarm integration to latest

If you download 2.2.2 and then instal 2.2.5?

not sure if thats a trick question, but I re-downloaded version 2.2.2 and installed it as well.
Running on 2.2.2 there is no issue.

Ok. Let me look at the options one. Does it install but not later allow configuring?

I had 2.2.2 installed, updated the integration and tried to configure.
both ways does not work

Also had issues when I upgraded to 2.2.5. Uninstalled everything and re-installed to 2.2.6 and seems to be working again.

Hello
I'm running on 2.2.6 now, but see this in the log pop up many times. Any idea what could be the cause of this. I have two devices, but only the one was selected. (Mon R) is my active one and everything seems to be working, just this error popping up in the logs.
This error originated from a custom integration.
Logger: custom_components.olarm_sensors
Source: custom_components/olarm_sensors/olarm_api.py:277
Integration: Olarm Sensors (documentation, issues)
First occurred: 07:23:58 (26 occurrences)
Last logged: 07:39:59
Olarm sensors error for device (Mon R): list index out of range


Update npm dependencies

The react-document-meta is a breaking change. I've got an issue open with that project, but I couldn't get it to work. If you can, then I can accept this PR.

I got react-document-meta working.


What are the sink configuration settings for this?

Hi, looking to use the flume-logstash-sink to experiment with different collectors for my data environment but there is no documentation on how to configure the sink? I would like to know how to specify the ES cluster host and port number.

Hi, nothing changes apart from the two configuration attributes mentioned in the README
This is extracted from the flume docs with the serializer and index builder cusomised for an agent named a1 and a sink k1:
a1.sinks.k1.type = org.apache.flume.sink.elasticsearch.ElasticSearchSink
a1.sinks.k1.hostNames = <IP_ADDRESS>:9200,<IP_ADDRESS>:9300
a1.sinks.k1.indexName = foo_index
a1.sinks.k1.indexType = bar_type
a1.sinks.k1.clusterName = foobar_cluster
a1.sinks.k1.batchSize = 500
a1.sinks.k1.ttl = 5
a1.sinks.k1.serializer = com.gilt.flume.elasticsearch.ElasticSearchLogStashEventSerializerV12
a1.sinks.k1.indexNameBuilder = com.gilt.flume.elasticsearch.TimeBasedIndexNameBuilderV12


Tern fails with ScanCode parsing error

Describe the bug
When scanning tomcat:10.0.6-jdk11-openjdk-buster with Tern, it fails after some time with the following output:
[...]
2021-10-21 14:17:33,554 - DEBUG - executor - Collecting file data...
2021-10-21 14:17:33,608 - DEBUG - common - Loading packages from cache: layer "139d3387e9"
2021-10-21 14:17:33,612 - DEBUG - common - Loading files from cache: layer "139d3387e9"
2021-10-21 14:17:33,625 - DEBUG - rootfs - Running command: sudo /usr/bin/scancode -ilpcu --quiet --timeout 300 -n 12 --json - /home/mhuber/.tern/temp/20da00f8ad0ba43d129dd08970e6649d63ca28412be31b0ff6d391862a085e68/contents
2021-10-21 14:18:56,208 - DEBUG - executor - Collecting file data...
2021-10-21 14:18:56,231 - DEBUG - common - Loading packages from cache: layer "bff998acef"
2021-10-21 14:18:56,297 - DEBUG - common - Loading files from cache: layer "bff998acef"
2021-10-21 14:18:58,745 - DEBUG - rootfs - Running command: sudo /usr/bin/scancode -ilpcu --quiet --timeout 300 -n 12 --json - /home/mhuber/.tern/temp/2306ce4f319a711c553242f8ab16abf709bc6a1853f122f50eafba0e2fa96487/contents
Traceback (most recent call last):
  File "/opt/tern.venv/lib/python3.8/site-packages/tern/extensions/scancode/executor.py", line 86, in filter_pkg_license
    return declared_license['license']
KeyError: 'license'

To Reproduce
Steps to reproduce the behavior:

Run Tern with -x scancode on tomcat:10.0.6-jdk11-openjdk-buster and wait

Environment you are running Tern on
executed in dockerized environment. Observed both in container build from docker/Dockerfile.scancode and in a custom docker image.
$ tern --version
Tern version 2.8.0
   python version = 3.8.11 (default, Oct 16 2021, 17:24:33)
$ uname -a
Linux x1extremeG2 5.13.0-rc6 #1-NixOS SMP Sun Jun 13 21:43:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ scancode --version
/opt/scancode/src/cluecode/copyrights.py:3382: FutureWarning: Possible set difference at position 3
  remove_tags = re.compile(
ScanCode version 30.1.0
ScanCode Output Format version 1.0.0
SPDX License list version 3.14

tern.log

I can reproduce this. Working on a fix.


"Continue playing" prompt annoyance

Now that, thanks to your effort, we can play longer Youtube videos, I am getting the dreaded "Video paused. Continue watching?" prompt. Obviously, I can't reproduce it at will.
On Chromium for Linux, I am using Youtube Nonstop, an extension with the ID nlkaejimjacpillmajjnopmpbkbnocid . Looking at its source code, it appears that it employs a webworker,with, every two seconds, checks on ($('.html5-video-player').hasClass("paused-mode")). When that turns true, it simulates a $("video").click();. Unfortunately, I don't understand how is the Chromium addon distinguishing between manual pauses and server-imposed pauses.

My report refers to this addon as used with Firefox on Android.

Can you remember how long it took that prompt to appear?

It seems to happen about 20 to 30 minutes without activities.

Tried playing an almost hour-long playlist on Android in the background and didn't experience any problems.

I remember using u block origin. Maybe that blocks something that helps to keep the video playing. It's not related to bg playing, also happens if firefox is in the foreground and I don't touch the phone for that time.
@buttercookie42 did you play the hour-long playlist without touching your mobile? Maybe it only appears if there is no interaction at all. … most people touches their phone so much that they won't notice. I found on businessinsider that "the typical cellphone user touches his or her phone 2,617 time[s] every day"

I remember using u block origin

Of course it also depends on the precise settings, but I tested with uBlock as well.

did you play the hour-long playlist without touching your mobile?

Yes I did, and besides, for the "Continue playing" prompt it's only interactions with the Youtube page that count.


No Firebase App '[DEFAULT]' has been created - call Firebase.initializeApp() in Flutter

I am using the web (Chrome) to run my application. But, I get an error.
    },
    (Object error, StackTrace stack) {
        debugPrint(error.toString());
        debugPrint(stack.toString());
    },
  );
}

I never get this error when I run my app with Android Emulator.
How can I fix this error? Appreciate if someone can advise. Thank you in advance!

Initialize your app using flutterfire configure
https://firebase.google.com/docs/flutter/setup
await Firebase.initializeApp(
  options: DefaultFirebaseOptions.currentPlatform,
);

@iqfareez, I get the error zsh: command not found: flutterfire.

https://firebase.google.com/docs/flutter/setup?platform=ios
see this link

@superciccio, I get the error zsh: command not found: flutterfire.

have you followed this steps
https://firebase.google.com/docs/cli#setup_update_cli

Yes, I have followed this steps.

The solution is add the path to .zshrc. The .zshrc file should look like this:
export PATH="$PATH:/Users/tech/Desktop/flutter/bin"
export PATH="$PATH":"$HOME/.pub-cache/bin"


Support parameters

Fixes #15
Changes proposed in this pull request:

Support parameters

Might be a good idea to also update readme in this PR.


fixup clippy errors

Rust 1.67 brings new clippy suggestions, this causes CI errors.

looks like it was already fixed ... and I'm just a dummy with git :D
git fetch will fetch from my remote and not origin when I'm on a branched with my fork set as upstream. Made that mistake before, and made it again.
Anyway, sorry for the noise.


did u ever done the overfitting check on openchat v1.0

although your file has split the dataset into the training set and validation set, it seems that training for 5 epochs with 6k samples will encounter overfitting.

According to the LIMA paper, the evaluation loss is not correlated with the final human evaluation. Thus, in the context of LLM fine-tuning, "overfitting" may either improve or degrade performance.

According to the LIMA paper, the evaluation loss is not correlated with the final human evaluation. Thus, in the context of LLM fine-tuning, "overfitting" may either improve or degrade performance.

Oh, thanks for your information.
Can I ask if your group just takes the last checkpoint for inference, or also use ChatGPT to score the effect of each checkpoint and decide which one to use for inference?

We used the last checkpoint for inference. We have run GPT-4 scoring on different sets of training epochs/hyperparameters etc. to select the best one.

Closing this issue now. If you have further questions, plz re-open.


Move read_exif_data to Image as an instance method

Creates a method to read the image's exif data, from code that had been in the show action of the Images::EXIFController. (This is an AJAX response to show an image's exif header). The method reads the info off the actual file on the server; we do not store this info in the Image record.
PR makes the method available outside that controller, in other words.
I would like to use it in the edit obs interface.

Also clears up a method name that I hadn't understood:

rename Image::URL.file_name method to full_filepath
rename Image.local_file_name to full_filepath

These methods return the full path of the image on the server per environment, like this: /Users/nimmo/Documents/GitHub/developer-startup/mushroom-observer/public/images/orig/1663403.jpg
...which I would call a filepath. I had assumed no method existed to get this, due to the name.
And changes some Image class methods returning immutable hashes or arrays to frozen constants, e.g. Image.all_sizes -> Image::ALL_SIZES.

coverage: 94.426% (-0.003%) from 94.429%
when pulling 39b67a2b53e2ad9d2ec008583d824870a296dee0 on image-exif-data
into de869882727602161f602d499d47b7ec4d1f29f1 on main.


add enter/exit to cursor and connection classes

Thanks for the PR, can you separate test for context manager style, please?


Hint that onChangeText will pass "Search Text".

I just guessed that this was the case and sure enough it was, so that's pretty good design by you. :)
However, I think it would be good to lead the reader a little bit more.
I know there is an example directory but this doesn't hurt to get people started.

I think it'd be better to put it in the example project. If not, onSearchBarChangeText is kind of missing the context.

You bet. Probably the best way to tie it all together.


goal-ontology: design goal ontology for warehousecontroller

Warehousecontroller takes the mission from MOO_Manager and generates goal which is to be
served by the OSLC server attached to the warehousecontroller.  When Warehousecontroller calls the planner, it puts the URI for the goal and URI for the current state on the message queue meant for the planner adapter. Planner adapter pulls the goal and state RDFs and processes them for planner reasoner.

Hi @swarupmohalik!
In regard to calling the Planning service: I think that it is still valid to do HTTP calls even when we have messaging infrastructure. So I would suggest that we create a resource PlanningRequest that is managed by the Planning service and WarehouseController service creates a PlanningRequest via a POST request. The Planning service would hopefully reply with a 201 Created code and the Location header to the newly created planning request. WarehouseController can then listen on the MQTT topic for the completion event of that planning request. The benefit of the HTTP call is an immediate feedback when a request has been registered (or rejected).
In regard to the state: I firmly believe the there is no single state S in our system, because everything is part of the global distributed state. In my view, Planning service would subscribe to the state updates of certain resource types (e.g. Robot waypoint position) and decide whether the state change should trigger replanning. BUT for now we are not ready to perform reactive planning just yet, so I suggest to pass the State as a property of the PlanningRequest together with the Mission or the set of Goals (which is the task of this bug to figure out) as well as the planning/execution deadlines (execution deadline might be part of the goal).
For now I have ignored the MOO part and used mission.json as the guideline for my RDF vocabulary. Here is how my two domains look now (@eanevul will probably blow the whole thing out of the water tomorrow):

Here is how the OSLC adaptors are connected right now in my prototype:

And finally, in regard to the "served by the OSLC server attached to the warehousecontroller": I don't think we should "attach" the OSLC server, but implement the warehouse controller as an OSLC server. I just happen to have all the tooling in place for Java, we can implement OSLC discovery/serialisation/capability features using Flask as well if needed. @likelion is making an OSLC library for Prolog right now.

@swarupmohalik please your comments from today telco here

Addressed in https://github.com/EricssonResearch/scott-eu/pull/42


[BUG] CodeInterpreterTool Error while fetching server API version: (2, 'CreateFile', 'The system cannot find the file specified.')

Description
Hi, I am using Crew AI to set up an agent to convert JSON data to an Excel file and save it in the current directory. I used CodeInterpreterTool for the setup. When I run the agent, it showed (the same error exists even with unsafe mode):
I encountered an error while trying to use the tool. This was the error: Error while fetching server API version: (2, 'CreateFile', 'The system cannot find the file specified.').
Tool Code Interpreter accepts these inputs: Code Interpreter(code: 'string', libraries_used: 'array') - Interprets Python3 code strings with a final print statement. code: 'Python3 code used to be interpreted in the Docker container. ALWAYS PRINT the final result and the output of the code', libraries_used: 'List of libraries used in the code with proper installing names separated by commas. Example: numpy,pandas,beautifulsoup4'

And the final answer is:
Below is the Python script that would accomplish the task of converting the JSON data to an Excel file, given a functioning Python environment with pandas installed:

python
import pandas as pd
...

This script first flattens the JSON data into a list of dictionaries, each representing a row in the final dataframe. Then it uses pandas to convert this list into a dataframe. Finally, it writes this dataframe to an Excel file named 'output.xlsx' in the current working directory. To execute this script, one would need a Python interpreter and the pandas library installed on their system.

It seems that the codes were not executed to generate an Excel file.
Steps to Reproduce
The error occured when running the codes below.
Expected behavior
An Excel file is generated and saved in the current directory.
Screenshots/Code snippets
from crewai import Agent, Task, Crew
from crewai_tools import CodeInterpreterTool

code_interpreter_tool = CodeInterpreterTool(libraries_used = ['pandas', 'openpyxl', 'json', 'ast', 'os'])

coding_agent = Agent(
    role="Python software developer",
    goal="Analyze the input data {input} and do file conversion using Python",
    backstory="You are an experienced software developer with strong Python skills.",
    allow_code_execution=True,
    verbose=True,
    allow_delegation=False,
    llm="azure/gpt-4-1106-preview",
    tools = [code_interpreter_tool]
)

json_to_excel_task = Task(
    description="Write Python codes to convert the input JSON data {input} to Excel file and save to the current directory",
    expected_output="A saved Excel file with the data from the input JSON data {input}",
    agent=coding_agent
)

analysis_crew = Crew(
    agents=[coding_agent],
    tasks=[json_to_excel_task],
    verbose=True
)

nested_json = '''{
    "Kitchen": {
        "temperature": 30,
        "adjacent_room": {
            "Toilet": {
                "temperature": 24,
                "shared_wall_area": 13.48
            },
            "Living_Rm1": {
                "temperature": 27,
                "shared_wall_area": 21.6
            }
        }
    },
    "Toilet": {
        "temperature": 24,
        "adjacent_room": {
            "Kitchen": {
                "temperature": 30,
                "shared_wall_area": 42.6
            },
            "Living_Rm1": {
                "temperature": 27,
                "shared_wall_area": 21.6
            }
        }
    }
}'''

result = analysis_crew.kickoff(inputs={"input": nested_json})
print(result)

Operating System
Windows 11
Python Version
3.10
crewAI Version
0.70.1
crewAI Tools Version
0.12.1
Virtual Environment
Venv
Evidence

Possible Solution
None
Additional context
NA

I don't know if it's related but I can't make the CodeInterpreterTool work either.
That said, I don't want to hijack the OP, just maybe complete the debugging info.
For simplicity, I have everything in a single python file:
import os
from crewai import Agent, Task, Crew, Process, LLM
from crewai_tools import SerperDevTool, SeleniumScrapingTool, ScrapeWebsiteTool, FileReadTool, FileWriterTool, CodeInterpreterTool, ScrapeWebsiteTool

os.environ["SERPER_API_KEY"] = "XXXXX"

llm_researcher = LLM(model="ollama_chat/qwen2.5:32b-instruct-q4_K_M_11k", base_url="http://localhost:11434", temperature=0.05)
llm_journalist = LLM(model="ollama_chat/qwen2.5:32b-instruct-q4_K_M_11k", base_url="http://localhost:11434", temperature=0.05)

researcher = Agent(
  role='Web Researcher',
  goal='Find any information on the web.',
  backstory="""You work at a leading web monitoring company.
  You have a knack for dissecting complex data and presenting it.""",
  verbose=True,
  allow_delegation=False,
  llm=llm_researcher,
  tools=[SerperDevTool(), SeleniumScrapingTool(), FileWriterTool(), FileReadTool()]
)

coder = Agent(
  role='Coder',
  goal='Solve coding problems and automate tasks.',
  backstory="""You are an experienced coder working at a leading BigTech company.
  You have a knack for writing efficient code to solve complex data problems.""",
  verbose=True,
  allow_delegation=False,
  llm=llm_researcher,
  tools=[CodeInterpreterTool(), FileWriterTool(), FileReadTool()]
)

journalist = Agent(
  role='Journalist',
  goal="""Summarize any received text, regardless of what type it is.
  Go in depth, detail everything.
    Organize your summary using headings and subheadings, paragraphs, text styles, lists, quotes, or tables as needed to make the content easy to read.
    Adapt the vocabulary so that it is accessible to anyone.""",
    backstory="""You are a renowned rigorous journalist known for insightful and engaging articles. You excel at transforming complex concepts into compelling narratives.""",
  verbose=True,
  allow_delegation=False,
  llm=llm_journalist,
  tools=[FileWriterTool(), FileReadTool()]
)

task1 = Task(
  description="Get the current date/time by executing a minimal python script.",
  expected_output="""The current date.""",
  agent=coder
)

task2 = Task(
  description="Keeping in mind the current date obtained from task1, scrape the content from the second to most recent article on xxxx.",
  expected_output="""The raw text of the article.""",
  output_file="""article.txt""",
  agent=researcher
)

task3 = Task(
  description="""Provide a detailed summary of the article contained in article.md.""",
  expected_output="""A summary (formatted in Markdown), along with the sources links which it could eventually contain.""",
  output_file="""summary.md""",
  agent=journalist
)

crew = Crew(
  agents=[researcher, journalist],
  tasks=[task1, task2, task3],
  verbose=True,
  #process = Process.hierarchical,
  #manager_llm = LLM(model="ollama_chat/qwen2.5:32b-instruct-q4_K_M_11k, base_url="http://localhost:11434", temperature=0.05),
  process = Process.sequential
)
result = crew.kickoff()

print("######################")
print(result)

And here is the error I keep on getting:
# Agent: Coder
## Task: Get the current date/time by executing a minimal python script.

I encountered an error while trying to use the tool. This was the error: Error while fetching server API version: ('Connection aborted.', FileNotFoundError(2, 'No such file or directory')).
 Tool Code Interpreter accepts these inputs: Tool Name: Code Interpreter
Tool Arguments: {'code': {'description': 'Python3 code used to be interpreted in the Docker container. ALWAYS PRINT the final result and the output of the code', 'type': 'str'}, 'libraries_used': {'description': 'List of libraries used in the code with proper installing names separated by commas. Example: numpy,pandas,beautifulsoup4', 'type': 'list[str]'}}
Tool Description: Interprets Python3 code strings with a final print statement.

# Agent: Coder
## Using tool: Code Interpreter
## Tool Input:
"{\"code\": \"from datetime import datetime\\nprint(datetime.now())\", \"libraries_used\": []}"
## Tool Output:

I encountered an error while trying to use the tool. This was the error: Error while fetching server API version: ('Connection aborted.', FileNotFoundError(2, 'No such file or directory')).
 Tool Code Interpreter accepts these inputs: Tool Name: Code Interpreter
Tool Arguments: {'code': {'description': 'Python3 code used to be interpreted in the Docker container. ALWAYS PRINT the final result and the output of the code', 'type': 'str'}, 'libraries_used': {'description': 'List of libraries used in the code with proper installing names separated by commas. Example: numpy,pandas,beautifulsoup4', 'type': 'list[str]'}}
Tool Description: Interprets Python3 code strings with a final print statement..
Moving on then. I MUST either use a tool (use one at time) OR give my best final answer not both at the same time. To Use the following format:

Thought: you should always think about what to do
Action: the action to take, should be one of [Code Interpreter, File Writer Tool, Read a file's content]
Action Input: the input to the action, dictionary enclosed in curly braces
Observation: the result of the action
... (this Thought/Action/Action Input/Result can repeat N times)
Thought: I now can give a great answer
Final Answer: Your final answer must be the great and the most complete as possible, it must be outcome described

I encountered an error while trying to use the tool. This was the error: Error while fetching server API version: ('Connection aborted.', FileNotFoundError(2, 'No such file or directory')).
 Tool Code Interpreter accepts these inputs: Tool Name: Code Interpreter
Tool Arguments: {'code': {'description': 'Python3 code used to be interpreted in the Docker container. ALWAYS PRINT the final result and the output of the code', 'type': 'str'}, 'libraries_used': {'description': 'List of libraries used in the code with proper installing names separated by commas. Example: numpy,pandas,beautifulsoup4', 'type': 'list[str]'}}
Tool Description: Interprets Python3 code strings with a final print statement.

I also tried qwen2.5-coder:32b-instruct-q4_K_M without any success.
The other tools are working as intended.

I tried with LLM(model="groq/llama-3.1-70b-versatile", temperature=0.05) but same result

I also need this solution. any one please help to resolve this.

I am also getting RuntimeError: Docker is not installed. Please install Docker to use code execution with agent: Coder when set "unsafe"

Expected script behavior: Local endpoint self-host example run with code execution (without Docker):
import os
from crewai import Agent, Task, Crew
from crewai_tools import CodeInterpreterTool

os.environ['OPENAI_API_BASE'] = 'http://<IP_ADDRESS>:5000/v1'
os.environ['OPENAI_API_KEY'] = 'sk-1111'

def main():
    agent = Agent(
        role="Coder",
        goal="Execute simple Python code",
        backstory="Python expert",
        tools=[CodeInterpreterTool()],
        code_execution_mode="unsafe",  # Try direct execution
        allow_code_execution=True      # Enable code execution
    )

    task = Task(
        description="Print: x = 2 + 2",
        expected_output="Simple calculation result",
        agent=agent
    )

    crew = Crew(
        agents=[agent],
        tasks=[task],
        verbose=True
    )

    result = crew.kickoff()
    print("\nResult:", result.raw)

if __name__ == "__main__":
    main()

(venv) C:\>no_docker_agent_CodeInterpreter.py
Traceback (most recent call last):
  File "C:\no_docker_agent_CodeInterpreter.py", line 34, in <module>
    main()
  File "C:\no_docker_agent_CodeInterpreter.py", line 9, in main
    agent = Agent(
  File "C:\venv\lib\site-packages\pydantic\main.py", line 214, in __init__
    validated_self = self.__pydantic_validator__.validate_python(data, self_instance=self)
  File "C:\venv\lib\site-packages\crewai\agent.py", line 242, in post_init_setup
    self._validate_docker_installation()
  File "C:\venv\lib\site-packages\crewai\agent.py", line 525, in _validate_docker_installation
    raise RuntimeError(
RuntimeError: Docker is not installed. Please install Docker to use code execution with agent: Coder

Modify from docs/how-to/coding-agents.mdx

Without Docker we should set:code_execution_mode="unsafe",  allow_code_execution=True as explained by the docs

docs/tools/codeinterpretertool.mdx states that it requires Docker:
https://github.com/crewAIInc/crewAI/blob/c7c0647dd225d655d928ec9cc96c6b933ad77e0e/docs/tools/codeinterpretertool.mdx?plain=1#L16-L18

But code_execution_mode="unsafe" should allow Direct execution (no Docker)
https://github.com/crewAIInc/crewAI/blob/c7c0647dd225d655d928ec9cc96c6b933ad77e0e/docs/concepts/agents.mdx?plain=1#L233-L236
https://github.com/crewAIInc/crewAI/blob/c7c0647dd225d655d928ec9cc96c6b933ad77e0e/docs/concepts/agents.mdx?plain=1#L45
https://github.com/crewAIInc/crewAI/blob/c7c0647dd225d655d928ec9cc96c6b933ad77e0e/src/crewai/agent.py#L125-L127

Along allow_code_execution=True:
https://github.com/crewAIInc/crewAI/blob/c7c0647dd225d655d928ec9cc96c6b933ad77e0e/docs/concepts/agents.mdx?plain=1#L293-L296
https://github.com/crewAIInc/crewAI/blob/c7c0647dd225d655d928ec9cc96c6b933ad77e0e/docs/concepts/agents.mdx?plain=1#L42

Without allow_code_execution=True we get::
I encountered an error while trying to use the tool. This was the error: Error while fetching server API version: (2, 'CreateFile', 'The system cannot find the file specified.').

In case it helps:
I just tried again my same crewai script without touching anything: the issue is fixed on 0.86.0.
I didn't set allow_code_execution=True and neither code_execution_mode="unsafe"
(crewai) user@user-PC:~/workspaces/crewai$ /home/user/miniforge3/envs/crewai/bin/python /home/user/workspaces/crewai/TEMPLATES/duo_simple.py
# Agent: Coder
## Task: Get the current date/time by executing a minimal python script.

# Agent: Coder
## Thought: I will use the Code Interpreter tool to execute a Python script that retrieves the current date and time using the datetime module. I'll ensure to print out the result.
## Using tool: Code Interpreter
## Tool Input:
"{\"code\": \"from datetime import datetime\\nprint(datetime.now())\", \"libraries_used\": []}"
## Tool Output:
2024-12-07 11:01:03.152320

# Agent: Coder
## Final Answer:
2024-12-07 11:01:03.152320

I don't know from which release it's been fixed out but given that my case is solved, the issue seems specific to windows.
PS: congrat and thanks to the commiter

For me, the issue originated from the docker client library.
The docker client could not find my docker daemon, and hence connect to my running docker engine.
The solution was to set the DOCKER_HOST environment variable explicitly to my docker.sock.
You can find the docker.sock file using docker context ls. Then
 DOCKER_HOST=unix:<path to docker.sock file>
To test:
from crewai_tools import CodeInterpreterTool

tool = CodeInterpreterTool(user_dockerfile_path='path to dockerfile where code is executed')
r = tool.run()

Hope this helps.


Wildcard request are sent with zero-length ResourceNamesSubscribe

Description:
The XDS doc describes wildcard requests as the following:
For [Listener](https://www.envoyproxy.io/docs/envoy/v1.22.0/api-v3/config/listener/v3/listener.proto#envoy-v3-api-msg-config-listener-v3-listener) and [Cluster](https://www.envoyproxy.io/docs/envoy/v1.22.0/api-v3/config/cluster/v3/cluster.proto#envoy-v3-api-msg-config-cluster-v3-cluster) resource types, there is also a “wildcard” subscription, which is triggered when subscribing to the special name “*”

Historically, wildcard requests are documented as special name "" (empty string).
In practice, when Envoy is configured to boot with LDS and CDS enabled, it appears to be sending a DeltaDiscoveryRequest with zero-length resource_names_subscribe.
Repro steps:
Boot Envoy with the following config:
---
node:
  cluster: cluster-42
  id: node-42
admin:
  access_log_path: /dev/null
  address:
    socket_address:
      address: <IP_ADDRESS>
      port_value: 9901
layered_runtime:
  layers:
    - name: static
      # Without specifying overload.global_downstream_max_connections, Envoy will throw a warning at bootstrap.
      static_layer: {overload.global_downstream_max_connections: 65536}
    - name: admin
      admin_layer: {}
    - name: rtds
      rtds_layer:
        name: rtds
        rtds_config: {ads: {}, resource_api_version: V3, initial_fetch_timeout: 1s}
static_resources:
  clusters:
    - name: xds_cluster
      connect_timeout: 5s
      type: STATIC
      lb_policy: ROUND_ROBIN
      common_http_protocol_options:
        max_stream_duration: 300s
      http2_protocol_options:
        connection_keepalive:
          interval: 30s
          timeout: 5s
      load_assignment:
        cluster_name: xds_cluster
        endpoints:
          - lb_endpoints:
              - endpoint:
                  address:
                    socket_address:
                      address: <IP_ADDRESS>
                      port_value: 8980
dynamic_resources:
  lds_config: {ads: {}, resource_api_version: V3, initial_fetch_timeout: 1s}
  cds_config: {ads: {}, resource_api_version: V3, initial_fetch_timeout: 1s}
  ads_config:
    api_type: DELTA_GRPC
    transport_api_version: V3
    grpc_services:
      envoy_grpc:
        cluster_name: xds_cluster
cluster_manager:
  load_stats_config:
    api_type: GRPC
    transport_api_version: V3
    grpc_services:
      envoy_grpc:
        cluster_name: xds_cluster

Observe the initial LDS and CDS request received on the control plane side (we use our in-house control plane). The request will show empty list for resource_names_subscribe.

@adisuissa @markdroth I think it might make sense to update delta behavior here under runtime guard, WDYT?

Thanks for bringing this up.
I think it is already runtime guarded in Envoy by envoy.restart_features.explicit_wildcard_resource. Can you please double check if this flag is set to true in your environment?


⚠ Fortnite has degraded performance

In 0c09cff, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1572 ms

Resolved: Fortnite performance has improved in a810351.


Add types from WithStoreInterface for supporting Functional Components

Finally I found the solution for the next issue.
e.g.
interface Properties extends CarouselInjectedProps { }
const Anything: React.FC<Properties> = (props) => <div />
export const AnythingWithCarouselStore = WithStore<Properties>(Anything)
While I'm trying to make something like that TypeScript throws the next error:
Argument of type 'FC' is not assignable to parameter of type 'ComponentClass<Properties, any>'.
Type 'FunctionComponent' provides no match for the signature 'new (props: Properties, context?: any): Component<Properties, any, any>'.
So in this commit I've solved this one and now the WithStore module supports FunctionalComponents
I leave some examples below

@cbasJS sorry for the delay on this - jumping on this now.
I have limited knowledge of TypeScript, but my understanding is you are allowing withStoreInterface to accept either a React Class Component or a React Functional Component (React.FC). Do I have this right?

@cbasJS sorry for the delay on this - jumping on this now.
I have limited knowledge of TypeScript, but my understanding is you are allowing withStoreInterface to accept either a React Class Component or a React Functional Component (React.FC). Do I have this right?

@tim-steele No worries. Things happen!
Yeah, that's right. I updated some lines for supporting React.FC. =)


bundlr failing with UNPREDICTABLE_GAS_LIMIT

I'm getting an issue on the bundlr CLI, trying to send MATIC to a bundlr node. It didn't happen a week ago or a month ago, but it's happening now.
Here's the command I used:
bundlr fund 1479016 -h https://node1.bundlr.network --no-confirmation -c matic -w 8c14<rest-of-MATIC-private-key>

Here's the output:
Loaded address: 0x8be6c8126c4383745c25f3b3ca76d73e3caf8544
Error whilst funding: cannot estimate gas; transaction may fail or may require manual gas limit [ See: https://links.ethers.org/v5-errors-UNPREDICTABLE_GAS_LIMIT ] (error={"reason":"cannot estimate gas; transaction may fail or may require manual gas limit","code":"UNPREDICTABLE_GAS_LIMIT","error":{"reason":"processing response error","code":"SERVER_ERROR","body":"{\"error\":{\"code\":-32000,\"message\":\"gas required exceeds allowance (1301)\"},\"id\":55,\"jsonrpc\":\"2.0\"}","error":{"code":-32000},"requestBody":"{\"method\":\"eth_estimateGas\",\"params\":[{\"type\":\"0x2\",\"maxFeePerGas\":\"0xaf9b72c9c8\",\"maxPriorityFeePerGas\":\"0xaf9b72c9c8\",\"value\":\"0x169168\",\"from\":\"0x8be6c8126c4383745c25f3b3ca76d73e3caf8544\",\"to\":\"0xb4de0833771eae55040b698af5eb06d59e142c82\"}],\"id\":55,\"jsonrpc\":\"2.0\"}","requestMethod":"POST","url":"https://polygon-rpc.com/"},"method":"estimateGas","transaction":{"from":"0x8bE6c8126C4383745c25F3b3Ca76D73E3Caf8544","maxPriorityFeePerGas":{"type":"BigNumber","hex":"0xaf9b72c9c8"},"maxFeePerGas":{"type":"BigNumber","hex":"0xaf9b72c9c8"},"to":"0xb4DE0833771eae55040b698aF5eB06d59E142C82","value":{"type":"BigNumber","hex":"0x169168"},"type":2,"accessList":null}}, tx={"to":{},"value":"0x169168","from":"0x8be6c8126c4383745c25f3b3ca76d73e3caf8544","type":2,"maxFeePerGas":{"type":"BigNumber","hex":"0xaf9b72c9c8"},"maxPriorityFeePerGas":{"type":"BigNumber","hex":"0xaf9b72c9c8"},"nonce":{},"gasLimit":{},"chainId":{}}, code=UNPREDICTABLE_GAS_LIMIT, version=abstract-signer/5.7.0)

Note that that account holds more than enough MATIC to do this transaction.
This is a big problem: if bundlr doesn't work, pybundlr doesn't work.

I just reported the issue to bundlr, via their discord.
https://discord.com/channels/864852288002850866/994913536906109029/1044691737320374312

I just funded a node using the SDK with no issues

Via help by the bundlr team on discord, I got to the bottom of the issue.
Summary: While my wallet had enough MATIC for the gas fees and to send, bundlr does a big multiplier based on max possible gas. And it seems that my wallet didn't have enough for that.
I tried with a different wallet that held way more MATIC, and it went through.
What this means: just hold more MATIC, the rest is fine.
Details, from my chat with bundlr support in discord:

Hello! I'm a big fan of bundlr:) I'm getting an issue on the bundlr CLI, trying to send MATIC to a bundlr node. It didn't happen a week ago or a month ago, but it's happening now.
Here's the command I used:
bundlr fund 1479016 -h https://node1.bundlr.network/ --no-confirmation -c matic -w 8c14
Here's the output:
Loaded address: 0x8be6c8126c4383745c25f3b3ca76d73e3caf8544
Error whilst funding: cannot estimate gas; transaction may fail or may require manual gas limit [ See: https://links.ethers.org/v5-errors-UNPREDICTABLE_GAS_LIMIT ] (error={"reason":"cannot estimate gas; transaction may fail or may require manual gas limit","code":"UNPREDICTABLE_GAS_LIMIT","error":{"reason":"processing response error", ...
Note that that account holds more than enough MATIC to do this transaction.
Help?
Hello! I'm a big fan of bundlr:) I'm getting an issue on the bundlr CLI, trying to send MATIC to a bundlr node. It didn't happen a week ago or a month ago, but it's happening now.
Here's the command I used:
bundlr fund 1479016 -h https://node1.bundlr.network --no-confirmation -c matic -w 8c14
Here's the output:
Expand
message.txt
3 KB
Jesse — Yesterday at 4:22 PM
Hey @trentmc0 , just a thread to keep things tidy
Jesse — Yesterday at 5:10 PM
what version of the bundlr client do you have installed? (you should be able to check via bundlr -v)
trentmc0 — Today at 12:58 PM
0.9.2
And I just ran a new install via npm install -g @bundlr-network/client, after that it still gives 0.9.2
I just tried running the command again today, to see if anything's changed. Interestingly, I get a different error this time: "insufficient funds for intrinsic transaction cost". But the wallet does have funds (though not a lot).
Here's the command, and error in detail
bundlr fund 1479016 -h https://node1.bundlr.network/ --no-confirmation -c matic -w 8c142
Loaded address: 0x8be6c8126c4383745c25f3b3ca76d73e3caf8544
Error occurred while sending a tx - Error: insufficient funds for intrinsic transaction cost [ See: https://links.ethers.org/v5-errors-INSUFFICIENT_FUNDS ] (error={"reason":"processing response error","code":"SERVER_ERROR","body":"{"jsonrpc":"2.0","id":57,"error":{"code":-32000,"message":"insufficient funds for gas * price + value"}}","error":{"code":-32000},"requestBody":"{"method":"eth_sendRawTransaction","params":["0x02f8708189508555d3a0de488555d3a0de4882520894b4de0833771eae55040b698af5eb06d59e142c828316916880c001a09d2caa5ace2bf82aab0d13fdabf8617f9e41d6bab5d3023f9606147786f1a282a04fba6befe738517b9c3eedb89ec0c8768018d84dd348636dc4dc1806db1987e6"],"id":57,"jsonrpc":"2.0"}","requestMethod":"POST","url":"https://polygon-rpc.com/"}, method="sendTransaction", transaction="0x02f8708189508555d3a0de488555d3a0de4882520894b4de0833771eae55040b698af5eb06d59e142c828316916880c001a09d2caa5ace2bf82aab0d13fdabf8617f9e41d6bab5d3023f9606147786f1a282a04fba6befe738517b9c3eedb89ec0c8768018d84dd348636dc4dc1806db1987e6", code=INSUFFICIENT_FUNDS, version=providers/5.7.2)
Error whilst funding: insufficient funds for intrinsic transaction cost [ See: https://links.ethers.org/v5-errors-INSUFFICIENT_FUNDS ] (error={"reason":"processing response error","code":"SERVER_ERROR","body":"{"jsonrpc":"2.0","id":57,"error":{"code":-32000,"message":"insufficient funds for gas * price + value"}}","error":{"code":-32000},"requestBody":"{"method":"eth_sendRawTransaction","params":["0x02f8708189508555d3a0de488555d3a0de4882520894b4de0833771eae55040b698af5eb06d59e142c828316916880c001a09d2caa5ace2bf82aab0d13fdabf8617f9e41d6bab5d3023f9606147786f1a282a04fba6befe738517b9c3eedb89ec0c8768018d84dd348636dc4dc1806db1987e6"],"id":57,"jsonrpc":"2.0"}","requestMethod":"POST","url":"https://polygon-rpc.com/"}, method="sendTransaction", transaction="0x02f8708189508555d3a0de488555d3a0de4882520894b4de0833771eae55040b698af5eb06d59e142c828316916880c001a09d2caa5ace2bf82aab0d13fdabf8617f9e41d6bab5d3023f9606147786f1a282a04fba6befe738517b9c3eedb89ec0c8768018d84dd348636dc4dc1806db1987e6", code=INSUFFICIENT_FUNDS, version=providers/5.7.2)
error.txt
3 KB
Here's the wallet on polygonscan. Like said, it has some funds, and the funds it has is >> the funds it's trying to send to bundlr. https://polygonscan.com/address/0x8bE6c8126C4383745c25F3b3Ca76D73E3Caf8544
Polygon (MATIC) Blockchain Explorer
Address 0x8bE6c8126C4383745c25F3b3Ca76D73E3Caf8544 | PolygonScan
The Address 0x8bE6c8126C4383745c25F3b3Ca76D73E3Caf8544 page allows users to view transactions, balances, token holdings and transfers of both ERC-20 and ERC-721 (NFT) tokens, and analytics.
Image
Idea: perhaps polygon or bundlr has some minimum threshold of funds needed, to even bother with a tx. To test this, I tried the CLI command with a wallet having more funds (>$100 of MATIC). It worked!
Details of successful run
bundlr fund 1479016 -h https://node1.bundlr.network/ --no-confirmation -c matic -w bc4ee
Loaded address: 0xf5dcd98a1c99c2c65c62025cb23cfb6f12f35497
Funding receipt:
Amount: 1479016 with Fee: "671189180214000" to 0xb4DE0833771eae55040b698aF5eB06d59E142C82
Transaction ID: 0xde6f95916396116f5a53e3452bd9eff56cbd5af5b4e3fee64cf7b3dc917874e8
success.txt
1 KB
Jesse — Today at 1:06 PM
less this, more that the network fees for matic are pretty high (we also add a multiplier to them to prevent the error you initially encountered)
trentmc0 — Today at 1:06 PM
Yeah, that could be the issue.
The network fee for the tx that just happened was: 0.000000000001479016 MATIC (< $0.000001)
tx: https://polygonscan.com/tx/0xde6f95916396116f5a53e3452bd9eff56cbd5af5b4e3fee64cf7b3dc917874e8
So the other address should have had more than enough. It held 0.000981761157456348 MATIC. https://polygonscan.com/address/0x8bE6c8126C4383745c25F3b3Ca76D73E3Caf8544
Jesse — Today at 1:08 PM
that's the resultant fee, but not the one we tried to use
trentmc0 — Today at 1:09 PM
For me, at least now I have an actionable path forward: just make sure my wallets have more funds
Jesse — Today at 1:09 PM
look at the max fee per gas
and you'll see that it's very high - the tx wil fail if you can't cover the gas limit * the max gas fee
trentmc0 — Today at 1:09 PM
OK. It's: 0.00000031961389534 MATIC
trentmc0 — Today at 1:09 PM
Yep
Jesse — Today at 1:09 PM
yeah so times that by 21,000
trentmc0 — Today at 1:10 PM
And I guess that explains it!
This is fine.
Jesse — Today at 1:10 PM
yup
trentmc0 — Today at 1:10 PM
Now I have an actionable path forward too:)
Jesse — Today at 1:10 PM
👍
trentmc0 — Today at 1:11 PM
I guess if you guys wanted, the bundlr error message could be better, explaining how much MATIC was actually needed. Though TBH most people will probably have a good margin of MATIC in their wallet? So probably not a high priority


Can't delete on explorer panel

VSCode Version: 1.36.0
OS Version: Arch linux (5.1.15-arch1-1-ARCH)

Steps to Reproduce:

Click on a file on explorer panel
Try removing the file with delete key.

Does this issue occur when all extensions are disabled?: Yes
Here is a picture:

Here I have clicked on main file on the explorer panel and pressed delete key three times.

/duplicate of #76514


Document adjustment to GitHub hosting

sync

I have read the CLA Document and I hereby sign the CLA

recheck


fix: improve setupCliCommandTest output type

Make the test command also have access to the context

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


sat passes when it should fail if sigmap(wire) has dupes, but differing \init

Retry of #1431 since that got merged in by accident

Here is a test case that show that this is not really fixing something, just changing one incorrect behavior into another (this is expected to pass):
read_verilog -formal <<EOT
module test (input clk, x, y, z, w);
        reg [2:0] a, b, c, d;

        initial a = 2'b01;
        initial b = 2'b10;
        initial c = 2'b01;
        initial d = 2'b10;

        always @(posedge clk) a[0] <= x;
        always @(posedge clk) b[0] <= y;
        always @(posedge clk) c[1] <= z;
        always @(posedge clk) d[1] <= w;

        always @* a[1] = a[0];
        always @* b[1] = b[0];
        always @* c[0] = c[1];
        always @* d[0] = d[1];

        reg first = 1;
        always @(posedge clk) first <= 0;

        always @* begin
                if (first) begin
                        assert (a == 2'b11);
                        assert (b == 2'b00);
                        assert (c == 2'b00);
                        assert (d == 2'b11);
                end
        end
endmodule
EOT

prep -top test
sat -seq 10 -prove-asserts -verify -show-public test

The real fix would be to change proc to eliminate init attributes on things that don't hold any state.


Add National College "Emil Racovita" Cluj-Napoca

Add National College "Emil Racovita" http://www.e-racovita.ro to the school list.

@MarcAureliusVana Pull request merged. Thank you!


No strings on translation file to Wallet connect, so I can't translate to PT-BR

Hi,
No strings on translation file to Wallet connect, so I can't translate to PT-BR

Duplicate of #3


[Note] File system support

KVM
qemu
Hyper-V
vfkit
WSL

9P
O
O
O
O
✓

sshfs
O
O
O
O
O

virtiofs
O
O
🞨
✓
🞨

✓ = Natively supported
🞨 = unsupported
O = possible (custom development)

I would mark KVM/9p and qemu/9p as supported as I far as I can tell this works out of the box (podman-machine is using this)
KVM/virtiofs is also supported in my opinion, worked out of the box when  I tried it on my fedora.
A bunch of 9p/qemu links
https://www.systutorials.com/docs/linux/man/1-virtfs-proxy-helper/
https://wiki.qemu.org/Documentation/9psetup
https://wiki.qemu.org/Documentation/9p

Minikube used a thirdparty library go9p to expose a UFS (Userspace file server)

We will reconsider 9P for use with Windows as this is also implemented for Podman Machine; this will happen as issue #3870


MCX Bluetooth and Wifi controls are just really broken

Affects: managedmac::mcx::bluetooth managedmac::mcx::wifi
This is a long standing bug in Apple's MCX implementation and we use MCX to control the state of these antennas. We should be able to fix this insofar as the Puppet module is concerned with some supplementary code.

The current methodology for controlling these antennas is simply broken. MCX is not reliable and other means of controlling these will need to be employed.

Controlling these antennas is pretty easy, but you know what sucks? State cannot be enforced without MCX and the MCX features for this are broken.

You can do this using execs, which I am working with at the moment:
https://gist.github.com/loyaltyarm/069c7fab1386c9d7f3fd
One issue I'm personally having using this though, is that my execs are not run in the order the are listed. I know this might be because Puppet wants you to use relationships to specify ordering, and those don't seem to be included in the execs class...reference: https://docs.puppetlabs.com/puppet/3.8/reference/lang_relationships.html
Any thoughts?

My comment here...

Controlling these antennas is pretty easy, but you know what sucks? State cannot be enforced without MCX and the MCX features for this are broken.
... says it all.
Controlling the antennas is easy (using Execs or whatever). Enforcing policy is difficult. I don't think stringing together Puppet exec resources is the right solution, but you should be able to do this using the subscribe => Exec['whatever'] notation. It's a bit different passing this in YAML-ese but it looks like this...

managedmac::execs::commands:
  disable_bluetooth:
    command: /usr/bin/defaults write /Library/Preferences/com.apple.Bluetooth ControllerPowerState '0'
  unload_bluetooth_service:
    command: /bin/launchctl stop com.apple.blued
    subscribe: Exec[disable_bluetooth]


Need help creating events

I want to create an event for created, updated and deleted package action.
but it shows error as:
An invalid history type was supplied: Package
Is there something that I forgot to do? help me, please

You need to add an entry for 'Package' in your historyType table

I already did that. anything else???

oh i forgot to add it in the table. thanks for the help tho


Failed to read index from Dbeaver

I am using a Dbeaver to access Elasticsearch service on AWS.  I am facing an error while trying to access an index having around 100 fields.  Though I am able to query the index from the editor, I can't see the schema in the data explorer.
Please find below image for more details about the error.

Thanks for reporting the issue.
Is it possible to share the index mapping to help debug the issue.
My current guess is the type is missing from the ElasticsearchType.

Attached the index mapping
kbs-datalake-index-mapping.txt

The issues in because the SQL plugin return the field without type info when the field in Elasticsearch mapping is object type. User are not required to set the field type to object explicitly, as this is the default value.

The mapping in Elasticsearch index which use implicit Object type.

        "stats" : {
          ”type":"object",
          "properties" : {
            "100%" : {
              "type" : "float"
            },
            "25%" : {
              "type" : "float"
            },
            "50%" : {
              "type" : "float"
            },
            "75%" : {
              "type" : "float"
            },
            "count" : {
              "type" : "float"
            },
            "max" : {
              "type" : "float"
            },
            "mean" : {
              "type" : "float"
            },
            "min" : {
              "type" : "float"
            },
            "std" : {
              "type" : "float"
            }
          }
        },

Result of query DESCRIBE TABLES LIKE kbs-datalake COLUMNS LIKE %
    [
      "elasticsearch",
      null,
      "kbs-datalake",
      "stats",
      null,
      null,
      null,
      null,
      null,
      10,
      2,
      null,
      null,
      null,
      null,
      null,
      10,
      "",
      null,
      null,
      null,
      null,
      "NO",
      ""
    ],

One workaround is add the "type":"object" for the field explicitly


Output declarations with emitDeclarationOnly

Previously, if there was no JavaScript output from a file, the output would be skipped entirely. This meant that when emitDeclarationOnly was enabled, the declarations would not be written to the dts stream.
Fixes #607.
One note on the test case: I found it actually passed even before making the change because gulp-diff only checks the files that exist in the stream. For example, if the stream is empty, the test will pass, even if there are files in the baseline directory. I did verify that, after my change, if the output differs, the test will fail.

Thanks Evan! I'll open an issue for the test issue that you described

Thanks for merging! Could we please get a release including this fix?

I want to fix some other issues as well, the release should be there in a few days

Published as 6.0.0-alpha.1.


[CLI] ability to remove dialogs

Hello folks,
I recently worked with the dialogs created by stacked-cli. I noticed there is no command to remove dialogs by cli
stacked delete -h
Provides access to the different deletion tools we have for stacked.

Usage: stacked delete <subcommand> [arguments]
-h, --help    Print this usage information.

Available subcommands:
  service   Deletes a service with all associated files and makes necessary code changes for deleting a service.
  view      Deletes a view with all associated files and makes necessary code changes for deleting a view.

Run "stacked help" to see global options.

would be very nice to see some kind of implementation

Added in https://github.com/Stacked-Org/cli/pull/34 and available in https://github.com/Stacked-Org/cli/releases/tag/v1.11.0


chore(master): release 1.5.4

:robot: I have created a release beep boop
1.5.4 (2022-07-16)
Bug Fixes

fix build:test error (14530cf)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/kailong321200875/vue-element-plus-admin/releases/tag/v1.5.4 :sunflower:


Difference between get_cert/set_cert checks

I'm looking at the check function for get_cert
/**
 * Certificate Check for SPDM leaf cert when get_cert command
 *
 * @param[in]  cert                  Pointer to the DER-encoded certificate data.
 * @param[in]  cert_size             The size of certificate data in bytes.
 * @param[in]  base_asym_algo        SPDM base_asym_algo
 * @param[in]  base_hash_algo        SPDM base_hash_algo
 * @param[in]  is_requester_cert     Is the function verifying requester or responder cert.
 * @param[in]  is_device_cert_model  If true, the local endpoint uses the DeviceCert model.
 *                                   If false, the local endpoint uses the AliasCert model.
 *
 * @retval  true   Success.
 * @retval  false  Certificate is not valid
 **/
bool libspdm_x509_certificate_check(const uint8_t *cert, size_t cert_size,

and the one for set_cert
/**
 * Certificate Check for SPDM leaf cert when set_cert command.
 *
 * @param[in]  cert                  Pointer to the DER-encoded certificate data.
 * @param[in]  cert_size             The size of certificate data in bytes.
 * @param[in]  base_asym_algo        SPDM base_asym_algo
 * @param[in]  base_hash_algo        SPDM base_hash_algo
 * @param[in]  is_requester_cert     Is the function verifying requester or responder cert.
 * @param[in]  is_device_cert_model  If true, the local endpoint uses the DeviceCert model.
 *                                   If false, the local endpoint uses the AliasCert model.
 *
 * @retval  true   Success.
 * @retval  false  Certificate is not valid.
 **/
bool libspdm_x509_set_cert_certificate_check(const uint8_t *cert, size_t cert_size,

The get_cert check ends up calling libspdm_verify_leaf_cert_basic_constraints(), which has this documentation
/**
 * Verify leaf cert basic_constraints CA is false
 *
 * @param[in]  cert                  Pointer to the DER-encoded certificate data.
 * @param[in]  cert_size             The size of certificate data in bytes.
 *
 * @retval  true   verify pass,two case: 1.basic constraints is not present in cert;
 *                                       2. cert basic_constraints CA is false;
 * @retval  false  verify fail
 **/
static bool libspdm_verify_leaf_cert_basic_constraints(const uint8_t *cert, size_t cert_size)

libspdm_verify_leaf_cert_basic_constraints() doesn't seem to support the basic_constraints_true_case for alias certs
While the set_cert check calls libspdm_verify_set_cert_leaf_cert_basic_constraints(), which does support the alias cert model and uses basic_constraints_true_case.
From what I can tell set_cert will correctly verify an alias cert, but get_cert will not as there is no basic_constraints_true_case check.
Doesn't this mean that we can not set and then retrieve an alias cert?

When SET_CERTIFICATEing an alias certificate chain the Requester does not provide the complete certificate chain; the Responder will append its certificate(s) to the chain provided by the Requester. In 1.2 the intermediate chain may contain CA==TRUE in the basic constraints. In 1.3 that was strengthened to all non-leaf certificates must have CA==TRUE.

Ah, I see. Thanks for pointing that out


ninja compile error for ../network.cpp/nla_get_s32 not declared in this scope

Hi
at this stage of compiling  (I run as root)
ninja -C build
I see error
../src/modules/network.cpp: In member function 'void waybar::modules::Network::parseSignal(nlattr** ': ../src/modules/network.cpp:504:28: error: 'nla_get_s32' was not declared in this scope      signal_strength_dbm_ = nla_get_s32(bss[NL80211_BSS_SIGNAL_MBM]) / 100;                             ^~~~~~~~~~~ ../src/modules/network.cpp:504:28: note: suggested alternative: 'nla_get_u32'      signal_strength_dbm_ = nla_get_s32(bss[NL80211_BSS_SIGNAL_MBM]) / 100;                             ^~~~~~~~~~~                             nla_get_u32
I am compiling on a tower but my coding skills are not great. Any chance you know how to get around this?
Am compiling on Tinycore v 10 64 bit which defaults to /usr/local
If you need it...some dropbox links to various files
https://www.dropbox.com/s/mrsuscim5cyver2/meson-log.txt?dl=0
^^ only thing not found is .....Program clang-tidy found: NO
.ninja log converted from hidden file to txt file
https://www.dropbox.com/s/li8j6rckifcet57/ninja_log.txt?dl=0
build ninja
https://www.dropbox.com/s/pav70pimo8cz3hh/build.ninja?dl=0
my "incomplete" build script so far
https://www.dropbox.com/s/t40oe9ebracmtk0/build-waybar.sh?dl=0
umm not sure what else to link to....so if you have need more let me know please
thanks for sharing any thoughts
gordon aka aus9

Seems we need to define nla_get_s32 when it's not available cause of an outdated version

Hi
what package on your system provides nla*?
I just did a private update of libnl but issue remains
../src/modules/network.cpp:504:28: error: 'nla_get_s32' was not declared in this scope      signal_strength_dbm_ = nla_get_s32(bss[NL80211_BSS_SIGNAL_MBM]) / 100
Or
are you saying I just need to define it and if so....how?
thanks for sharing any thoughts on this matter

Hi
Similar compile issue for 0.6 release but libnl has been updated in repository
Still missing clang-tidy
I have not got tray support working correctly in sway so until I resolve that issue, please close this thread
Thanks


Allow marking relationships as async

All Submissions:

[x] I've checked to ensure there aren't other open Pull Requests for the same update/change.
[ ] I've submitted a ticket for my issue if one did not already exist.
[ ] My submission passes all tests. (Please run the full test suite locally to cut down on noise from travis failures.)
[ ] I've used Github auto-closing keywords in the commit message or the description.
[x] I've added/updated tests for this change.

New Feature Submissions:

[ ] I've submitted an issue that describes this feature, and received the go ahead from the maintainers.
[x] My submission includes new tests.
[x] My submission maintains compliance with JSON:API.

Test Plan:
Reviewer Checklist:

[ ] Maintains compliance with JSON:API
[ ] Adequate test coverage exists to prevent regressions

@krasnoukhov Could you please write up a description of this feature?

We're going to handle this by allowing control over the generation of links as the relationship is defined. We can also use this to control the generation of the relationship routes.


Website is down

www.markusproject.org refused to connect.

markusproject.org no longer exists. References to it have been/should be removed from documentation. See #3893
@jellycsc Sorry for the confusion


fix: quick fix of #6405 by removing context from value note utils

Please read contributing guidelines and remove this line.

Benchmark results
Metrics with a significant change:

tx_sequencer_processing_time_ms (0): 1,522 (+16%)
app_circuit_proving_time_in_ms (FPC:fee_entrypoint_public): 8,851 (-46%)
protocol_circuit_witness_generation_time_in_ms (base-parity): 1,399 (+63%)
protocol_circuit_proving_time_in_ms (public-kernel-app-logic): 888 (+27%)
protocol_circuit_proving_time_in_ms (public-kernel-tail): 1,177 (+31%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
740
740
740

l1_rollup_calldata_gas
6,680
6,692
6,692

l1_rollup_execution_gas
586,865
586,877
586,877

l2_block_processing_time_in_ms
1,613
6,060
12,038

l2_block_building_time_in_ms
35,327
139,112 (+1%)
276,077 (-1%)

l2_block_rollup_simulation_time_in_ms
35,105
138,331 (+1%)
274,548 (-1%)

l2_block_public_tx_process_time_in_ms
16,523
70,831 (+1%)
142,525 (-1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
17,866 (-1%)
33,556

node_database_size_in_bytes
21,389,392
38,010,960

pxe_database_size_in_bytes
29,868
59,425

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
13.2
21.5
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.7
31.8
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.772
0.663
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
61.5
97.1
316
608
1,197
2,373
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.631
0.601
0.575
0.568
0.568
0.567
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
73.8
143
456
892
1,776
3,534 (-1%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
106
208
692
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.646
0.644
0.619
0.615
0.617
0.617
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
80.6

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
108

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.709

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
84,440
673,183

Transaction size based on fee payment method
| Metric |  |
| - |  |
Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes
2 new note hashes

tx_pxe_processing_time_ms
37,018 (-1%)
3,686
113,578

Metric
0 public data writes
1 public data writes
2 public data writes
4 public data writes
8 public data writes

tx_sequencer_processing_time_ms
:warning: 1,522 (+16%)
2,268 (-1%)
1,831 (-4%)
2,826 (-1%)
1,820


job pod succeeds, but worker registeres a FATAL error

I've got a simple job setup:
const { events, Job } = require('brigadier')

events.on("push", (brigadeEvent, project) => {
    var job = new Job("demojob", "alpine:3.4")
    job.env = {
        "leakme": project.secrets.leakme
    }
    job.tasks = [
        "echo Line 1",
        "echo Line 2",
        "echo $leakme"
    ]

    job.run()
})

events.on("pull_request", (brigadeEvent, project) => {
    var job = new Job("pulljob", "alpine:3.4")
    job.env = {
        "leakme": project.secrets.leakme
    }
    job.tasks = [
        "echo Line 1",
        "echo Line 2",
        "echo $leakme"
    ]

    job.run()
})

When a pull request job comes in, I can see the worker pod fire off, and the logs show something interesting:
> kubectl logs brigade-worker-01c07578kfq4gk6gf9nt8aredx-11426f2c
yarn run v1.3.2
$ node prestart.js
prestart: src/brigade.js written
$ node --no-deprecation ./dist/src/index.js
Creating PVC named brigade-worker-01c07578kfq4gk6gf9nt8aredx-11426f2c
looking up default/github-com-j2sol-demobrigade-pulljob
Creating secret pulljob-1512068853475-11426f2c
Creating Job Cache PVC github-com-j2sol-demobrigade-pulljob
undefined
Creating pod pulljob-1512068853475-11426f2c
Timeout set at 900000
default/pulljob-1512068853475-11426f2c phase Pending
default/pulljob-1512068853475-11426f2c phase Pending
default/pulljob-1512068853475-11426f2c phase Succeeded
FATAL: job pulljob(pulljob-1512068853475-11426f2c): [object Object] (rejection)
error handler is cleaning up
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

The pulljob pod appears to be successful, but gets marked as fatal?
Here's the log from pulljob:
> kubectl describe pod pulljob-1512068853475-11426f2c
Name:		pulljob-1512068853475-11426f2c
Namespace:	default
Node:		<IP_ADDRESS>/<IP_ADDRESS>
Start Time:	Thu, 30 Nov 2017 11:07:33 -0800
Labels:		build=01c07578kfq4gk6gf9nt8aredx
		commit=11426f2c689a6a7ccb78a6c6e366ce040e5f797d
		component=job
		heritage=brigade
		jobname=pulljob
		project=brigade-463662f2bc06a89c2464d52d1b248602a1085ed2ccf2953df6a8fa
		worker=brigade-worker-01c07578kfq4gk6gf9nt8aredx-11426f2c
Annotations:	<none>
Status:		Succeeded
IP:		<IP_ADDRESS>
Init Containers:
  brigade-vcs-sidecar:
    Container ID:	docker://7fe43d4a2133b673ed88d5e960a2a24a440d58d9bd79a20cf015bc9812396246
    Image:		iamjlk/git-sidecar:jlk
    Image ID:		docker-pullable://iamjlk/git-sidecar@sha256:39515695d5c0582e13aa603220976244196dd43c4053ca7554c9029047821ab3
    Port:		<none>
    State:		Terminated
      Reason:		Completed
      Exit Code:	0
      Started:		Thu, 30 Nov 2017 11:07:35 -0800
      Finished:		Thu, 30 Nov 2017 11:07:36 -0800
    Ready:		True
    Restart Count:	0
    Environment:
      VCS_REPO:		https://github.com/j2sol/demobrigade.git
      VCS_LOCAL_PATH:	/src
      VCS_REVISION:	11426f2c689a6a7ccb78a6c6e366ce040e5f797d
      VCS_AUTH_TOKEN:	<hidden>
    Mounts:
      /src from vcs-sidecar (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from brigade-worker-token-4dbns (ro)
Containers:
  brigaderun:
    Container ID:	docker://c6fb7791eb9a5f3819e9757b5e9d220e1f906b2065dbb1204840760f0dec2324
    Image:		alpine:3.4
    Image ID:		docker-pullable://alpine@sha256:915b0ffca1d76ac57d83f28d568bcb516b6c274843ea8df7fac4b247440f796b
    Port:		<none>
    Command:
      /bin/sh
      /hook/main.sh
    State:		Terminated
      Reason:		Completed
      Exit Code:	0
      Started:		Thu, 30 Nov 2017 11:07:37 -0800
      Finished:		Thu, 30 Nov 2017 11:07:38 -0800
    Ready:		False
    Restart Count:	0
    Environment:
      leakme:		<set to the key 'leakme' in secret 'pulljob-1512068853475-11426f2c'>	Optional: false
      CLONE_URL:	https://github.com/j2sol/demobrigade.git
      HEAD_COMMIT_ID:	11426f2c689a6a7ccb78a6c6e366ce040e5f797d
      CI:		true
    Mounts:
      /hook from pulljob-1512068853475-11426f2c (rw)
      /src from vcs-sidecar (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from brigade-worker-token-4dbns (ro)
Conditions:
  Type		Status
  Initialized 	True
  Ready 	False
  PodScheduled 	True
Volumes:
  pulljob-1512068853475-11426f2c:
    Type:	Secret (a volume populated by a Secret)
    SecretName:	pulljob-1512068853475-11426f2c
    Optional:	false
  vcs-sidecar:
    Type:	EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
  brigade-worker-token-4dbns:
    Type:	Secret (a volume populated by a Secret)
    SecretName:	brigade-worker-token-4dbns
    Optional:	false
QoS Class:	BestEffort
Node-Selectors:	<none>
Tolerations:	node.alpha.kubernetes.io/notReady:NoExecute for 300s
		node.alpha.kubernetes.io/unreachable:NoExecute for 300s
Events:
  FirstSeen	LastSeen	Count	From			SubObjectPath					Type		ReasonMessage
  ---------	--------	-----	----			-------------					--------	-------------
  45s		45s		1	default-scheduler							Normal		Scheduled		Successfully assigned pulljob-1512068853475-11426f2c to <IP_ADDRESS>
  45s		45s		1	kubelet, <IP_ADDRESS>							Normal		SuccessfulMountVolume	MountVolume.SetUp succeeded for volume "vcs-sidecar"
  45s		45s		1	kubelet, <IP_ADDRESS>							Normal		SuccessfulMountVolume	MountVolume.SetUp succeeded for volume "brigade-worker-token-4dbns"
  45s		45s		1	kubelet, <IP_ADDRESS>							Normal		SuccessfulMountVolume	MountVolume.SetUp succeeded for volume "pulljob-1512068853475-11426f2c"
  43s		43s		1	kubelet, <IP_ADDRESS>	spec.initContainers{brigade-vcs-sidecar}	Normal		PulledContainer image "iamjlk/git-sidecar:jlk" already present on machine
  43s		43s		1	kubelet, <IP_ADDRESS>	spec.initContainers{brigade-vcs-sidecar}	Normal		Created			Created container
  43s		43s		1	kubelet, <IP_ADDRESS>	spec.initContainers{brigade-vcs-sidecar}	Normal		Started			Started container
  41s		41s		1	kubelet, <IP_ADDRESS>	spec.containers{brigaderun}			Normal		PulledContainer image "alpine:3.4" already present on machine
  41s		41s		1	kubelet, <IP_ADDRESS>	spec.containers{brigaderun}			Normal		Created			Created container
  41s		41s		1	kubelet, <IP_ADDRESS>	spec.containers{brigaderun}			Normal		Started			Started container

> kubectl logs pulljob-1512068853475-11426f2c -c brigade-vcs-sidecar
+ : /src
+ : https://github.com/j2sol/demobrigade.git
+ : 11426f2c689a6a7ccb78a6c6e366ce040e5f797d
+ git clone --depth=50 https://github.com/j2sol/demobrigade.git /src
Cloning into '/src'...
+ cd /src
+ git fetch origin 11426f2c689a6a7ccb78a6c6e366ce040e5f797d
From https://github.com/j2sol/demobrigade
 * branch            11426f2c689a6a7ccb78a6c6e366ce040e5f797d -> FETCH_HEAD
+ git checkout -qf FETCH_HEAD
+ git reset --hard -q 11426f2c689a6a7ccb78a6c6e366ce040e5f797d

> kubectl logs pulljob-1512068853475-11426f2c -c brigaderun
Line 1
Line 2
I am not a crook

I can't see where this error is coming from. Any help?

All I can figure is that something about the last echo is not returning 0. But I don't see why that would be.

And the thing you are testing there is something we're looking into. We'd like to obfuscate or redact secrets that are leaked into the logs.

is this related to the comment i did for arguments of a function in a previous merged PR? just saying

Are you referring to https://github.com/Azure/brigade/pull/178? If so no, that’s different.

I am experiencing this same problem. With this Brigade file:
const { events, Job } = require('brigadier')

events.on('image_push', (e) => {
  let payload = JSON.parse(e.payload);

  let job = new Job(
    "deploy-k8s-demo",
    "<myawsaccountid>.dkr.ecr.us-east-1.amazonaws.com/k8s-deploy:1.1.0", [
      `<mycommand> ${payload.imageTag}`,
      `echo $?`
    ]);
  job.run().then((e) => {
    console.log(`In success: ${e.toString()}`);
  }, (e) => {
    console.log(`In failure ${e.toString()}`);
  });
});

and I'm getting 0 echoed out in the pod logs
 The current Primary Color in use is: blue
It is taking 100% of traffic for the service
...
0

but the promise is rejecting
 operations/deploy-k8s-demo-1513979239919-ed2e182d phase Pending
operations/deploy-k8s-demo-1513979239919-ed2e182d phase Running
operations/deploy-k8s-demo-1513979239919-ed2e182d phase Running
operations/deploy-k8s-demo-1513979239919-ed2e182d phase Running
operations/deploy-k8s-demo-1513979239919-ed2e182d phase Running
operations/deploy-k8s-demo-1513979239919-ed2e182d phase Succeeded
In failure job deploy-k8s-demo(deploy-k8s-demo-1513979239919-ed2e182d): [object Object]
after: default event fired
beforeExit(2): destroying storage
Destroying PVC named brigade-worker-01c2033nvkp79c4n8w0xwm4p97-ed2e182d
Done in 12.66s.

I can't find a way to dig more into the [object Object] thing either


Issues import bpnet negatives

Hi here,
I'm working through the turtorials and there's an issue when I run the following segment of code from the Training turtorial. The code block
negatives = grelu.data.preprocess.get_gc_matched_intervals(
    peaks,
    binwidth=0.02, # resolution of measuring GC content
    genome=genome,
    chroms="autosomes", # negative regions will also be chosen from autosomes
    #gc_bw_file='gc_hg38_2114.bw',
    blacklist=genome, # negative regions overlapping the blacklist will be dropped
    seed=0,
)
negatives.head(3)

outputs the following error: ModuleNotFoundError: No module named 'bpnetlite.negatives'. And this is after bpnet-lite has been install with pip. Any idea how to fix this bug? Either update the function calls in bpnetlite? Or reverting verisons?

Thanks for raising this @Jome0169 . What version of bpnetlite are you using?

The current version I have installed is: "0.8.1"

We are still using 0.5.7 (https://github.com/Genentech/gReLU/blob/main/setup.cfg#L70). You'll need to downgrade bpnetlite to 0.5.7 for this to work.

This fixed it! Thank you.


MMCA-4547-Update to version 3

Scalastyle warning is being flagged for below test. Please address this as well
warn] /Users/vineet.tyagi/hmrc/codebase/customs-manage-authorities-frontend/test/views/AccountsViewSpec.scala:101:0: Whitespace at end of line


Connection reached timeout

Using the latest version of ARRT (2.3.6) when I try to start the session I get the following error:
SESSION: Connection reached timeout (10 sec). Session ID:  "XXXXXXXX"
Both ARR and Storage connection checks are correct.
Detailed log output:

XCESSPAK-MAIN.07-25-2022.19-17-14.etl.zip
mine also connection reached timeout kindly solve this problem


Javascript interface

Reading google/flatbuffers#60 made me realize we could interface with the WWW quite easily: as both enet and flatbuffers are rather plain C(++) with only system dependencies, we should be able to translate them to JS thanks to Emscripten.
Using something like node-restify, this enables us to provide a full-fledge RESTful API for more integration, given this service is just another client to the server.

On the reading / parsing end of things, a potentially simpler alternative to Emscripten is using the DataView API to parse an ArrayBuffer, which can be directly extracted from an XHR2 response, as described here.

As a proof-of-concept exercise, I've written a tiny library that can help with this:
https://github.com/prideout/flatbin
I wouldn't recommend using it in production since it doesn't have unit tests yet, but hopefully you get the idea from the README.  One neat thing is that it can extract a typed array from a portion of the binary blob without incurring any copies.  And, there's no use of Emscripten.  :)

Thanks Philip.
But I see that flatbuffers now has a JS binding (don't know if you have anything to do with it) as well as enet.
I think a nodejs/iojs app is the way to for www integration.


Populate src/wiseagents/llm init.py

Can populate this to be able to import things from this package using wiseagents.llm instead of wiseagents.llm.module_name and then adjust imports accordingly.

Closed via https://github.com/wise-agents/wise-agents/issues/79


I have made some minor changes in the comments of the code and some modifications in documentation. It is very useful when we have a crystal clear comments to explain the code which makes it well documented and clean code.

Description
Test Options

[x] fast test
[x] full test - HPO
[x] full test - NAS
[x] full test - compression

Checklist

[x] test case
[x] doc

How to test

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree


[FTX]Adding FTX fundingPayments and borrowingHistory support

Also, adding a starting point for ftx-stream

Because i thought that we must a create an ExchangeException for every
exchange, everytime
Στις Κυρ, 7 Μαρ 2021 στις 9:50 μ.μ., ο/η Erick Arce <
<EMAIL_ADDRESS>έγραψε:

@earce commented on this pull request.
In
xchange-ftx/src/main/java/org/knowm/xchange/ftx/service/FtxAccountServiceRaw.java
https://github.com/knowm/XChange/pull/3968#discussion_r589078657:

}

}

public FtxResponse<List> getFtxFundingPayments(String subaccount, Long startTime, Long endTime, String future)

     throws FtxException, IOException {

try {

 return ftx.getFundingPayments(

         exchange.getExchangeSpecification().getApiKey(),

         exchange.getNonceFactory().createValue(),

         signatureCreator,

         subaccount,

         startTime,

         endTime,

         future);

} catch (FtxException e) {

 throw new FtxException(e.getMessage());

why don't you just throw e back?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/knowm/XChange/pull/3968#pullrequestreview-605878763,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHIWQ7YOME462UJAWOSBZN3TCPKINANCNFSM4YWXIAUA
.


Invalid Github URL.

I just copy and paste the command to my terminal, here is the result:

Same issue here.

@wiscaksono @ahamedzoha Fixed


add max

Codecov Report

Merging #13 (53858ef) into main (aa993cb) will decrease coverage by 1.15%.
The diff coverage is 62.50%.

@@            Coverage Diff             @@
##             main      #13      +/-   ##
==========================================
- Coverage   95.47%   94.32%   -1.16%
==========================================
  Files           3        3
  Lines         221      229       +8
==========================================
+ Hits          211      216       +5
- Misses          7        9       +2
- Partials        3        4       +1

Impacted Files
Coverage Δ

numeric/collection.go
84.21% <62.50%> (-15.79%)
:arrow_down:

Continue to review full report at Codecov.

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


Nuget

Microsoft Reviewers: Open in CodeFlow

Despite merging, nuget cli doesn't seem to be in manifests\Microsoft at all.
Reason why? or some problem caused it?
@aortiz-msft @anangaur @chgill-msft

@rrelyea it was reverted in https://github.com/microsoft/winget-pkgs/pull/248 :)


netlify throws an error if git is not installed

I don't know if this is a bug report or a feature request.
I tried netlify-cli on a bare bone alpine linux and forgot to install the git package first. If netlify cannot spawn the git command, it throws this error. A more user friendly error message would be nice, something like: "git command not found, please install git".
# netlify init -m
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: spawn git ENOENT
    at exports._errnoException (util.js:1018:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
    at onErrorNT (internal/child_process.js:367:16)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)
    at Module.runMain (module.js:606:11)
    at run (bootstrap_node.js:390:7)
    at startup (bootstrap_node.js:150:9)
    at bootstrap_node.js:505:3

Git is required for some repo interactions.  Leaving this open to verify what happens on the 2.0.0 branch.

Closing this as stale, please re-open if still relevant


WriteSchema can deadlock

Hello,
I've recently discovered that WriteSchema has a potential deadlock, due to this PR that Authzed put up to the Rudd library: https://github.com/dalzilio/rudd/pull/1
That PR introduced recursive read locking on a sync.RWMutex, which is not supported. What happens is that the logic that is run when calling WriteSchema does a recursive read lock, and a GC finalizer does a write lock. If a GC happens in between a first RLock() and the second, recursive RLock(), the finalizer will call Lock(), and cause a deadlock: the second RLock() will never succeed, since the call to Lock() is preventing new RLocks() from occurring, and yet the first RLock() will never be unlocked.
The recursive lock occurs because these functions that do operations on if a node is marked are called from this function, which also acquires a read lock.
I have a test harness that issues a lot of WriteSchema requests against a SpiceDB running in serve-testing mode, and this occurs quite frequently.
I have put a test up on my fork that shows the deadlock with WriteSchema is possible: https://github.com/epaulson10/spicedb/commit/18cd91c0e4e36233d02185abe84e2dc81cad9573. The test issues a bunch of WriteSchema calls against a locally running test server using one of your large example schemas, while hammering runtime.GC() in a goroutine to make the race condition happen more often.
I opened up https://github.com/dalzilio/rudd/pull/2 to fix this. I tested with your reproducer and didn't see any deadlocks after making this change locally.


Mutliple deploys

On first deploy admin breaks, on second deploy everything works

In fact, it was the migrations which were ignoring the migration files and therefore it was creating the databse correctly