code block first line has a space

Is there a fix for that?
for example if I type the following in markdown:
a=3
puts a

the first line (a=3) will be more padded than the second and subsequent lines in the code block.
like this
 a=3
puts a

Fixed


⚠ Bofrost.at has degraded performance

In 2a1e3de, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1470 ms

Resolved: Bofrost.at performance has improved in 7f73fe6 after 13 minutes.


Configurable generation of the builder

Currently, when a Java file is generated out of an avsc file, the included builder is in this form:

The factory method for builder obtaining is called the newBuilder()
The builder's setters are prefixed with set, e.g. builder.setValue()

It would be great if both the factory method and the setter prefix would be configurable.
In my team, we use the following conventions throughout the code:

builder() factory methods
builder.withValue() setters

Some teams even omit the setter prefix completely and use builder.value() for the setters.
Is this achievable in your plugin?

Thanks for the question. The answer is yes and no. How the Java files are generated is controlled by velocity templates. If desired you can provide an alternate set of templates, and that would be capable of achieving your desired result.
https://github.com/davidmc24/gradle-avro-plugin/blob/master/README.md#templatedirectory documents how to configure this.
https://github.com/davidmc24/gradle-avro-plugin/blob/master/src/test/groovy/com/commercehub/gradle/plugin/avro/OptionsFunctionalSpec.groovy has a test that further demonstrates this.
If you’re looking for an out-of-the-box way to do this without maintaining your own templates, I don’t believe that to currently be available. You’d need to get the Apache Avro project to add a new option to their Avro Java library, and then I would enhance this plugin to allow configuring that option.

Thanks for your prompt answer!
A built-in configuration in the plugin would be the best in terms of usability. Maintaining own templates will be way too complicated I think.
Anyway, if I understand you correctly, your plugin wraps an existing Avro Project's Java code generator which uses templates to generate the code (I have seen the the https://github.com/davidmc24/gradle-avro-plugin/blob/df6ceec970ffe26c2c38c39d1759b5754cfab763/src/test/resources/com/commercehub/gradle/plugin/avro/record.vm).
If so, then I understand the need to alter the official Avro project's implementation.
Thanks again for your help.

Yep, that’s correct.
To join the mailing list, report issues, or contribute code to the upstream
project, see here:
https://avro.apache.org
On Thu, Oct 10, 2019 at 4:17 PM Pavel Lobodinský<EMAIL_ADDRESS>wrote:

Thanks for your prompt answer!
A built-in configuration in the plugin would be the best in terms of
usability. Maintaining own templates will be way too complicated I think.
Anyway, if I understand you correctly, your plugin wraps an existing Avro
Project's Java code generator which uses templates to generate the code (I
have seen the the
https://github.com/davidmc24/gradle-avro-plugin/blob/df6ceec970ffe26c2c38c39d1759b5754cfab763/src/test/resources/com/commercehub/gradle/plugin/avro/record.vm
).
If so, then I understand the need to alter the official Avro project's
implementation.
Thanks again for your help.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/davidmc24/gradle-avro-plugin/issues/87?email_source=notifications&email_token=AADNKUKALH55RVN3C5ADSH3QN6EVZA5CNFSM4I7Q6UZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA5X6FQ#issuecomment-540770070,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADNKULCIKO75AKKXMBY3T3QN6EVZANCNFSM4I7Q6UZQ
.

--
David M. Carr
<EMAIL_ADDRESS>

Thank you!


unmap: Align start lba and split large num blocks into optimal ones.

NOTE: here we always asumme the OPTIMAL UNMAP GRANULARITY equals to UNMAP GRANULARITY ALIGNMENT, if not in feature and the align and split algorithm should be changed.
The next will add the alignment support in Write Same UNMAP.

Test output:
[root@wzy-2 ~]# sg_unmap --lba=7 --num=81990 /dev/sdh -v
unmap cdb: 42 00 00 00 00 00 00 00 18 00
[root@wzy-2 ~]#
[DEBUG] handle_unmap:2039 block1: Data-Out Buffer Length: 24, dl: 22, bddl: 16
[DEBUG] handle_unmap_internal:1855 block1: OPTIMAL UNMAP GRANULARITY: 8192, UNMAP GRANULARITY ALIGNMENT: 8192
[DEBUG] handle_unmap_internal:1871 block1: Parameter list 0, start lba: 7, end lba: 81996, nlbas: 81990
[DEBUG] handle_unmap_internal:1927 block1: Split 0: start lba: 7, end lba: 8191, lbas: 8185
[DEBUG] handle_unmap_internal:1927 block1: Split 1: start lba: 8192, end lba: 16383, lbas: 8192
[DEBUG] handle_unmap_internal:1927 block1: Split 2: start lba: 16384, end lba: 24575, lbas: 8192
[DEBUG] handle_unmap_internal:1927 block1: Split 3: start lba: 24576, end lba: 32767, lbas: 8192
[DEBUG] handle_unmap_internal:1927 block1: Split 4: start lba: 32768, end lba: 40959, lbas: 8192
[DEBUG] handle_unmap_internal:1927 block1: Split 5: start lba: 40960, end lba: 49151, lbas: 8192
[DEBUG] handle_unmap_internal:1927 block1: Split 6: start lba: 49152, end lba: 57343, lbas: 8192
[DEBUG] handle_unmap_internal:1927 block1: Split 7: start lba: 57344, end lba: 65535, lbas: 8192
[DEBUG] handle_unmap_internal:1927 block1: Split 8: start lba: 65536, end lba: 73727, lbas: 8192
[DEBUG] handle_unmap_internal:1927 block1: Split 9: start lba: 73728, end lba: 81919, lbas: 8192
[DEBUG] handle_unmap_internal:1927 block1: Split 10: start lba: 81920, end lba: 81996, lbas: 77

This will allow  MAXIMUM UNMAP LBA COUNT > max_xfer_len to speed up the unmap operation when VMWare doing the virtual machine migration or deletion with large size of block device.

if not in feature and

What does this mean? What is "feature"?

Patches look good to me.

+/* Temporarily limit this to 32M */
+#define VPD_MAX_UNMAP_LBA_COUNT            (32 * 1024 * 1024)

Not for this patchset, but some day in the future, what is the plan for all the unmap values? Were you going to make them configurable like the lio device attributes:
max_unmap_block_desc_count
max_unmap_lba_count
unmap_granularity
unmap_granularity_alignment
unmap_zeroes_data
?
Or is the plan to just have the handler set the values that work for them based on the hw they are using and their limits? For example, this is probably rbd/ceph specific:

+       max_xfer_length = tcmu_get_dev_max_xfer_len(dev);
+       tcmu_set_dev_opt_unmap_gran(dev, max_xfer_length);
+       tcmu_set_dev_unmap_gran_align(dev, max_xfer_length);

For file, you might want max_xfer_len 128K - N MBs, but then the unmap values could be really high like in the GBs for even common hw.

Not for this patchset, but some day in the future, what is the plan for all the unmap values? Were you
going to make them configurable like the lio device attributes:
max_unmap_block_desc_count
max_unmap_lba_count
unmap_granularity
unmap_granularity_alignment
unmap_zeroes_data
?
Yes, if this is needed and could make our tcmu-runner code more readable and easier to generate new patches for us.
After the WRITE SAME's UNMAP have support the granularity and alignment feature, I will add these.


#372 cross accounts role

partially fix for #372

Current coverage is 45.62%

Merging #386 into master will decrease coverage by -0.70% as of aae316b

@@            master    #386   diff @@
======================================
  Files          127     126     -1
  Stmts         2882    2926    +44
  Branches       234     240     +6
  Methods          0       0
======================================
  Hit           1335    1335
  Partial         54      54
- Missed        1493    1537    +44

Review entire Coverage Diff as of aae316b

Powered by Codecov. Updated on successful CI builds.

👍

:+1:


2-Stage Impl?

Hi @edz-o @Angtian @AdamKortylewski et al.,
It would be good if u could clarify where 2-stage is implemented in the current codebase. I have trouble localizing it. Thx!

Thanks for your interest in our work! As mentioned in the paper, in the implementation we just convert pretrained SMPL to NBV for convenience.


Update lilypond to 2.19.61-1

After making all changes to the cask:

[x] `brew cask audit --download {{cask_file}}` is error-free.
[x] `brew cask style --fix {{cask_file}}` left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as be873ac82e78ecf46209b88e0747dc5291cd8258. Your contribution is still credited to you.


Second option is not working In percentage Calculator

Describe the bug
Second option does not output anything In percentage Calculator in General Maths section.
Possible solution
I would like to rectify this problem.
Please assign it to me

Go ahead
Deadline 29 April,2021


getExtension api behave differently when tests is invoked by using script

Issue Type: Bug
Here is the codebase for our extension: https://github.com/alexa/ask-toolkit-for-vscode.
I am trying to set up some tests for our extension. And there are two tests available under test/extension.test.ts. When I invoke the tests through debug tab and execute the task extension tests: https://github.com/alexa/ask-toolkit-for-vscode/blob/master/.vscode/launch.json#L20, those two tests could pass successfully. However, if I invoke the runTest script: https://github.com/alexa/ask-toolkit-for-vscode/blob/master/test/runTest.ts, both two tests failed because the getExtension api returns undefined.
I am not sure what's the differences by using the two test methods. Did i miss setup something in the script ?
Thanks,
Shen
VS Code version: Code 1.48.1 (3dd905126b34dcd4de81fa624eb3a8cbe7485f13, 2020-08-19T17:09:41.484Z)
OS version: Darwin x64 18.7.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7660U CPU @ 2.50GHz (4 x 2500)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
3, 4, 6

Memory (System)
16.00GB (0.08GB free)

Process Argv
.

Screen Reader
no

VM
0%

Extensions (8)

Extension
Author (truncated)
Version

vscode-eslint
dba
2.1.8

prettier-vscode
esb
5.5.0

vscode-codemetrics
kis
1.24.0

vscode-github
Kni
0.30.3

vscode-docker
ms-
1.5.0

vscode-typescript-tslint-plugin
ms-
1.2.3

code-spell-checker
str
1.9.0

markdown-all-in-one
yzh
3.3.0

@ShenChen-Amazon Here is what I have tried:

npm install -g yo code-generator
I did a fresh TypeScript extension using yo code (this is to eliminate any other changes that might have been done in the repository)
I used the name webtest and the publisher name alex.
I have edited src/test/suite/extension.test.ts and added:

		const ext = vscode.extensions.getExtension('alex.webtest');
		if (ext) {
			console.log(JSON.stringify(ext.packageJSON));
		} else {
			console.log(`no extension`);
		}

When I run npm run test, I see the package json being printed in the console.

Hi @alexdima ,
Thanks for your help. I finally figure out the issue is caused by the wrong extensionDevelopmentPath. My folder structure is slightly different with the samples. Resolving the issue.
Thanks,
Shen


Replace check_ws with is_authenticated

uiprotect does not have a check_ws method. is_authenticated appears to provide a similar enough function for the use case in event_listener.py to allow it to be a drop-in replacement.

AttributeError: 'ProtectApiClient' object has no attribute 'check_ws'

Alas it does not seem like these two functions do the same thing.
the purpose of check_ws is to check if the websocket is currently connected:
    def check_ws(self) -> bool:
        """Checks current state of Websocket."""

        if self._websocket is None:
            return False

        if not self._websocket.is_connected:
            log = _LOGGER.debug
            if self._last_ws_status:
                log = _LOGGER.warning
            log("Websocket connection not active, failing back to polling")
        elif not self._last_ws_status:
            _LOGGER.info("Websocket re-connected successfully")

        self._last_ws_status = self._websocket.is_connected
        return self._last_ws_status

the code of is_authenticated does not do this at all:
def is_authenticated(self) -> bool:
        """Check to see if we are already authenticated."""
        if self._session is None:
            return False

        if self._is_authenticated is False:
            return False

        if self._last_token_cookie is None:
            return False

        # Lazy decode the token cookie
        if self._last_token_cookie and self._last_token_cookie_decode is None:
            self._last_token_cookie_decode = decode_token_cookie(
                self._last_token_cookie,
            )

        if (
            self._last_token_cookie_decode is None
            or "exp" not in self._last_token_cookie_decode
        ):
            return False

        token_expires_at = cast(int, self._last_token_cookie_decode["exp"])
        max_expire_time = time.time() + TOKEN_COOKIE_MAX_EXP_SECONDS

        return token_expires_at >= max_expire_time

Ah, didn't realise you were packaging your own fork of uiprotect. Was running against the main.

This project uses upstream uiprotect, but possibly not the most up to date version

Found the issue - uiprotect moved to a websocket state subscription and removed check_ws, resulting in the :dev docker build erroring on event_listener.
https://github.com/uilibs/uiprotect/commit/d7083ab8ced2dc3cc65dcaf6ea2dd8c869e70a96
Will send through a PR with a shift to using the state subscription, but would probably be cleaner ways to do it. That fix has been enough to get it running correctly for me when I patch it into the :dev docker build.


METRON-366: Add MODEL_APPLY to Stellar

The preferred method of applying models should be via stellar integration. This should be added as a function and made available as a FieldTransformation and as part of Threat Triage.
This has been run on full-dev.  Testing instructions pending...

Testing Instructions
Free Up Space on SNV
First, let's free up some headroom on SNV.  If you are running this on a multinode cluster, you would not have to do this.

Kill monit via service monit stop
Kill tcpreplay via for i in $(ps -ef | grep tcpreplay | awk '{print $2}');do kill -9 $i;done
Kill existing parser topologies via

storm kill snort
storm kill bro

Kill flume via for i in $(ps -ef | grep flume | awk '{print $2}');do kill -9 $i;done
Kill yaf via for i in $(ps -ef | grep yaf | awk '{print $2}');do kill -9 $i;done
Kill bro via for i in $(ps -ef | grep bro | awk '{print $2}');do kill -9 $i;done

Install Prerequisites and Mock DGA Service
Now let's install some prerequisites:

Flask via yum install python-flask
Jinja2 via yum install yum install python-jinja2

Now that we have flask and jinja, we can create a mock DGA service to deploy with MaaS:

Download the files in this gist into the /root/mock_dga directory
Make rest.sh executable via chmod +x /root/mock_dga/rest.sh

This service will treat yahoo.com and amazon.com as legit and everything else as malicious.  The contract is that the REST service exposes an endpoint /apply and returns back JSON maps with a single key is_malicious which can be malicious or legit.
Deploy Mock DGA Service via MaaS
Now let's start MaaS and deploy the Mock DGA Service:

Start MaaS via /usr/metron/0.2.0BETA/bin/maas_service.sh -zq node1:2181
Start one instance of the mock DGA model with 512M of memory via /usr/metron/0.2.0BETA/bin/maas_deploy.sh -zq node1:2181 -lmp /root/mock_dga -hmp /user/root/models -mo ADD -m 512 -n dga -v 1.0 -ni 1
As a sanity check:

Ensure that the model is running via /usr/metron/0.2.0BETA/bin/maas_deploy.sh -zq node1:2181 -mo LIST.  You should see Model dga @ 1.0 be displayed and under that a url such as (but not exactly) http://node1:36161
Try to hit the model via curl: curl 'http://localhost:36161/apply?host=caseystella.com' and ensure that it returns a JSON map indicating the domain is malicious.

Adjust Field Transformations for Squid to Call Model
TBD
Adjust Threat Intel Triage to Adjust Risk Based on Model
TBD

Please note that it is non-optimal to only be able to reference models from the beginning (i.e. parsers) and end (i.e. threat triage) of the pipeline.  As a follow-on, I'll be adding an enrichment adapter which can be called from the enrichment or threat triage phase and perform arbitrary stellar statement transformations.  This should fill in the gap and allow the user to apply their models anywhere in the pipeline.

+1 by inspection.  Will try to run it up on full-dev later today or this weekend.  Nice job!

Do you have documented anywhere the model classes in org.apache.metron.maas?  These classes seem to represent core abstractions.
A few questions come to mind that some simple javadoc might help with.  But one example... A Model has a version and a ModelEndpoint has a version.  Why do they both have versions?  Wouldn't they evolve together and so have the same version?

happy to add javadoc to that package.  To answer your question, Model and ModelEndpoint are different in the sense that Model is a reference to the model.  The ModelEndpoint is a reference to where the model is currently being served.  You generally search for a Model and are returned a set of ModelEndpoints.  If you do not specify a version in the search, you will get ModelEndpoints of multiple versions of the same model.

+1, worked like a champ!
I'm going to run it up one more time with some additional skip tags. Since we're close on memory headroom, it doesn't make sense to me to take time to install a bunch of stuff I'll just have to shut down. If I have any success, I'll put the commands here.
I'm also using the new quick-dev image (vagrant box update).

  Woah!  @dlyle65535 is my hero.


Cursors don't work

In query.getList:
selector._id = {
  $in: _id.map((id) => processId({id}))
};

_id is not an Array. It is actually { $gt: ... }

Can you demonstrate the problem? I can't see the error in the code.

@rushidesai Please provide more info, or I will close this.

@rushidesai I am closing this for now, ping me if you have anything.


CSV loader

From #32:
Abstract
For testing purposes, it's quite common to preload some known data in the database. CSV files are a good way to handle data rows, and many data-manipulation tools have a support for CSV extraction.
Implementation

The first line of the CSV file will contain the column names
Next lines will contain the data
Each data row will be converted by the new module to pop SQL inserts.
The query can be prepared and reused, since it will use the same INSERT query, but with different data.

w00t w00t!

@larrymjordan Is it better now? :)

Looks good to me, great job!

@stanislas-m @u007 should this, perhaps, be it's own separate package? Seems like it could easily live on its own. Not a deal breaker, just a question. :)

@markbates It can be. :)

I'm closing this, and will rework it as a plugin package.


Unexpected argument warning from pycharm

Pycharm indicates unexpected arguments but code work without problems
My code:
from attrs import define

@define
class Property:
    name: str
    value: Any

    @classmethod
    def from_dict(cls, data: dict):
        return cls(
            name=data['name'], #  Unexpected argument
            value=data['value'] #  Unexpected argument
        )

That's a PyCharm bug ;)
They probably haven't added support for import attrs (vs import attr) yet. You can keep using from attr import define until they do, it's the same.


Enhancement: Add paste option

Can you add a paste option? I'd like the default when I press enter not to be going to the Youversion website but to immediately paste the text (not just ref.) into whatever application I'm using without having to copy it first and then paste it in a separate action. But maybe going to the Youversion website could be one of the other keystrokes like Shift + Enter, or Fn + Enter.
P.S. To be able to use it with multiple languages, I duplicated the workflow and changed the keywords so they can work alongside each other. I also added hotkeys so I can rapidly go straight to references. I love this workflow so much – thank you!

When editing the workflow double click on the "copy to clipboard" option and tick "automatically paste to front-most app".

In the yvset command you can set copy to be the default, and open in browser to require holding command.

Ah yes, it's working with paste now. Thank you for your grace & patience!

My final issue for today is that duplicating the workflow doesn't seem to allow for multiple languages, as updating the language on one then changes the default language for the other workflow as well. Any possible support for using Turkish & English for example?

@kenanmike It is an interesting thought though for it to be configurable.
@caleb531 Thoughts on adding another variable that has the copy to clipboard/copy and paste baked into yvset?

My final issue for today is that duplicating the workflow doesn't seem to allow for multiple languages, as updating the language on one then changes the default language for the other workflow as well. Any possible support for using Turkish & English for example?

The preferences are stored globally for the workflow at present, so they will be the same across both/all instances.

@kenanmike

My final issue for today is that duplicating the workflow doesn't seem to allow for multiple languages, as updating the language on one then changes the default language for the other workflow as well. Any possible support for using Turkish & English for example?

You need to change the bundle ID in the workflow settings (double-click the workflow in the Workflows list), AND update the WORKFLOW_UID variable in yvs/core.py. Please see my attached screenshots.

@kenanmike Unfortunately, there's no good way to update the workflow to the latest version while keeping these customizations intact. I will add to my list the request for adding a Paste-by-Default preference, however I cannot provide a timeline of when I can get to it.
Fortunately, @bevanjkay's workaround is by far the simplest and most easily replicable solution for now.

@kenanmike Unless you have any further comment, I think it's safe to close this issue.


Update for Kibana 8.3.3

Include in this update receiving and passing along query parameters for logging and tracking:
-X-Opaque-ID
-User info data

The X-Opaque-Id is a value that is passed into Elasticsearch queries by the client that allows you to correlated specific client requests with specific queries/tasks within Elasticsearch.  In the ElasticSearch client this can be passed on each search (https://github.com/elastic/elasticsearch-py/issues/847).
The intention is that each tile request would generate a new X-Opaque-Id so that if we see a hung-task or a slow query we can directly track it down to the specific tile request in the Datashader .datashader_tiles index.

Ok, I was thinking that this was something like x-proxied-entities to track who is running queries.
Would it make sense to set it to something like sha1 of the url, and log the url/hash so we could look up and recreate the exact query?
sha_1 = hashlib.sha1()
sha_1.update(url)
query_hash = sha_1.hexdigest()
queryid = "DS-"+query_hash
logger.info(queryid,url)
es = Elasticsearch(["http://localhost:9200"], headers={"x-opaque-id": queryid})

I don't have a preference on how the opaque-id is created, but there are two considerations:

The user who ran the query, the URL, and the full query are stored in .datashader_tiles already
Using the hash will cause two identical requests to have the same opaque-id, so if two identical URLs are accessed we cannot differentiate them.

Looks like the user information on who ran the query isn't in the .datashader_tiles. Nothing from the header is in there. I can add that also if we want. right now I have the x-opaque-id at
"params.x-opaque-id": [
    "e83066df-fe66-4a27-a508-de8f85d9bf99"
  ],```

I can also move the x-opaque-id up to the document root if we have a preference.

Fixed and merged.


need hotspot support

can you please add hotspot support too?

What do you mean by hotspot support ?

kind of like green indicators in http://demo.app-technologies.com/viewing360-web/upload/tour/28/4/rDVV14990873131499087338/

What you've mentioned would only be needed if the library supported navigating between multiple images. Currently, it doesn't. Therefore I'm gonna mark this one as enhancement and give it a better definition for future reference.


Cannot authenticate using feathers token

app runs smoothly on my local but after deploying my app to server, calling feathersApp.authenticate() returns error:

Bad "options.jwtid" option. The payload already has an "jti" property.

i tried downgrading feathers-authentication to version 1.2.7 and it worked.

Probably a regression due to https://github.com/feathersjs/authentication/pull/539 Are you overriding the jwtid in production?

i was not. it might be due to jsonwebtoken update, but i'm not sure.
https://github.com/auth0/node-jsonwebtoken/blob/master/CHANGELOG.md

I have the same issue but it occurs both in development and production.

Can someone please share a reproducible example?

I can try to set one up. Shouldn't take long. Just make a service that creates a JWT with createJWT.

What are you calling createJWT for? There might be a good reason but Feathers authentication should normally not require you to ever do that directly.

I have a service that issues JWTs to clients that call it with an API key. Reason for this is that the clients aren't real "clients", but other servers.

@FreeLineTM why don't you use a custom auth module using passport-custom for api key authentication. I use it to completely circumvent creating JWTs. I've added it to the docs here https://github.com/feathersjs/docs/pull/885
@daffl could you please review and merge it?

@subodhpareek18 I didn't know how to do that and the solution I'm using was a suggestion from someone else. Didn't have any better ideas myself.

I'm having the same problem  I was running feathers-authentication 1.2.7 on my server and everything was fine.  I upgraded today and I get the same error now. My client is using feathers-authentication 1.3.0 with no issues before the update so it's something that was introduced between 1.2.7 and 1.3.0.

Here is a copy of the error: (I get it when I open a new tab to the same URL.  The JWT is re-read from window.localstorage and checked to see if it's still valid.  The new window tab is the one that throws the server error, not the original one).
And my package.json diff:

info: error: authentication - Method: create: Bad "options.jwtid" option. The payload already has an "jti" property.
error:  Error: Bad "options.jwtid" option. The payload already has an "jti" property.
at C:\code\jsapi\server\node_modules\feathers-authentication\node_modules\jsonwebtoken\sign.js:165:24
at Array.forEach ()
at Object.module.exports [as sign] (C:\code\jsapi\server\node_modules\feathers-authentication\node_modules\jsonwebtoken\sign.js:161:35)
at C:\code\jsapi\server\node_modules\feathers-authentication\lib\utils.js:54:28
at Promise ()
at Authenticator.createJWT (C:\code\jsapi\server\node_modules\feathers-authentication\lib\utils.js:46:10)
at Object.create (C:\code\jsapi\server\node_modules\feathers-authentication\lib\service.js:48:28)
at C:\code\jsapi\server\node_modules\feathers-hooks\lib\hooks.js:101:31
at Promise ()
at C:\code\jsapi\server\node_modules\feathers-hooks\lib\hooks.js:85:16
at
at process._tickCallback (internal/process/next_tick.js:188:7)

I have a fix in https://github.com/feathersjs/authentication/pull/600 which should be released shortly.

Closed via #600

thanks @daffl! 💯

It now works for me.  Thank you so much for the quick turn around!


Unable to compile for Web

Hi! Thank you so much for this library!
I'm using Flutter 1.15.17 on the beta channel to build web apps. Once I do import 'package:spotify/spotify.dart', I'm introduced to a compiler error
Compiler message:
../../../../.pub-cache/hosted/pub.dartlang.org/spotify-0.3.0/lib/src/spotify_mock.dart:26:20: Error: Too few positional arguments: 2 required, 1 given.
    var file = File('test/data/$partialPath.json');
                   ^
Failed to compile application.

From delving into the code, I'm seeing that if the app is a web app the package imports dart:html, but the File constructor in html takes two arguments instead of the one given
factory File(List<Object> fileBits, String fileName, [Map options])
I could be doing something wrong, so any insight would be very helpful
Thank you again!

So I removed the test directory and spotify_mock.dart while also commenting out the dependency in spotify.dart. It works for web now! The issue lies with the test.

Hi @thelostmachine, thanks for all of the details on the issue!
Could you try using the branch for https://github.com/rinukkusu/spotify-dart/pull/44 and see if that fixes the problem for you?

Ah sorry for the late reply @LeviHassel
It works beautifully now! Thank you so much!


Error opening connection with SQLite

Describe the bug
After installation and creation of a connection, it was working fine.
Then I needed to change my project's directory, and now SQLtools can't connect anymore to the same SQLite database file.
To Reproduce
Steps to reproduce the behavior:

Add new connection

Fill data
2.1 Connection name: MyDB
2.2 Dialects: SQLite (Node Native)
2.3 Database: mydb.db

Click on CREATE

Click on Connect Now

See Error

Expected behavior
Create a database connection.
Desktop:

SQLTools Version: v0.20.3
VSCode Version: 1.37.1
Dialect Used/Version: SQLite
OS: Windows 10

Error Message
INFO: Executing SQLTools.selectConnection
ERROR: Error:  { Error: SQLITE_CANTOPEN: unable to open database file
    at c:\Users\User\.vscode\extensions\mtxr.sqltools-0.20.3\extension.js:1:22921
    at c:\Users\User\.vscode\extensions\mtxr.sqltools-0.20.3\extension.js:1:23328
    at Immediate.module.exports.messageQueue.size.setImmediate (c:\Users\User\.vscode\extensions\mtxr.sqltools-0.20.3\extension.js:1:23872)
    at runCallback (timers.js:694:18)
    at tryOnImmediate (timers.js:665:5)
    at processImmediate (timers.js:647:5)
  code: -32001,
  data: { dialect: 'SQLite', dialectOptions: {} } }

Additional Info
I've checked file-system permissions
Uninstalled SQLTools
Deleted c:\Users\User.vscode\extensions\mtxr.sqltools-0.20.3
Reinstalled
Same issue

Hey, problem solved.
If someone comes up with the same problem, do as follows:

Open %appdata%\Code\Workspaces\
You'll see a folder with some big number
Enter this folder and open workspace.json
3.Locate  "sqltools.connections" and edit "database" with the absolute path to your sqlite db:

this:

"database": ".\db\mydb.sqlite3",

to something like this:

"database": "C:/web/my-project/db/mydb.sqlite3",


Add Java project to examples

@coreylight Updated this to simplify it/try to word it more for users looking at examples and it cleared the review; also open to suggestions re: welcoming language!


Upgrade Spring Boot

Some major dependency updates for the Typed PID Maker should be done soon:

Update to current Spring Boot major version
Update service-base
Update repo-core

Helpful material:

https://www.baeldung.com/spring-boot-3-migration
The Spring Boot Migrator, which seems to be helpful (https://github.com/spring-projects-experimental/spring-boot-migrator) only available for maven
https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-3.0-Migration-Guide
(paywall) https://www.heise.de/tests/Spring-Framework-6-im-Ueberblick-Major-Version-setzt-Java-17-voraus-7351343.html
(paywall) https://www.heise.de/ratgeber/Spring-Boot-3-Datenbankanbindung-leicht-gemacht-8984292.html

Merged into master, done with next release (2.0.0).


Add general-purpose serving infrastructure

This standardizes our http/grcp server creation and lifecycle handling.

Another question: would it make sense to push this out to sandwich?

Another question: would it make sense to push this out to sandwich?
Or is there value there in having less indirection for someone new to the codebase?

It depends on how "production ready" you want the examples in sandwhich to be.

It depends on how "production ready" you want the examples in sandwhich to be.

Can you elaborate? We intend to write production-ready code for Sandwich, though we're getting there iteratively.
It's not clear to me if the interface in this PR is something we'll want to adopt or even be able to adopt in Sandwich (given our use of Chi there), but from the PR description it sounds like we probably should.

It's not clear to me if the interface in this PR is something we'll want to adopt or even be able to adopt in Sandwich (given our use of Chi there), but from the PR description it sounds like we probably should.

This is for serving, Chi is for routing. Chi implements http.Handler, so a Chi instance could be passed to ServeHTTPHandler or ServeHTTP with an http.Server#Handler.


Jump to a certain state

Problem:
Let say I have several states. State1 to State50. Example I want State4 to State10 and State15 to State20 each jump to State50, i'm aware that you can switch state via StateCondition but with that the StateMachine would have a very long list of repetitive conditions for the purpose of jumping to a certain state.
Question:
Is there any method available to jump to a certain state instead of using of using a StateCondition to verify and change state?

I just made a quick solution for that on a separate branch, since I don't know if changing the state from outside the state machine is a good idea. If you want to try it, change the repo link on the package manager to this:
https://github.com/luisoliveiras/scriptable-states.git#feature/direct-transition-to-state

You have a point, probably it would be better solution if you can put multiple OriginState? So we can group those States with similar condition that going to a certain state.

Ok, that should be a better sollution for this problem. I'll try it here!

Just sent a new commit, same branch, you can try it on the same link as before. I added a list of states to the transitions, and check if the origin state is in there before trying the condition. It should work as you thought. This is just a draft, I'll make a few tests tomorrow to see if it runs ok for different scenarios. Thank you for this contribution.

I created another branch in which I organize the transitions in the state machine by origin. It should have a better performance since internally I'm using a dictionary to get the possible transitions for that origin. It becomes a bit more organized, but you would still have some repeated transitions.

Yeah can still have repetitive, let say in your example you have PlayerNormalState, PlayerRunningState, PlayerRecoveringState all those origin states could go to a certain state like PlayerDieState if a death condition is triggered then I probably still need to repeat those transitions on those three Origins.

@luisoliveiras I can't seems to find the feature/transitions-as-dictionary branch, please keep also the direct transition to state function as I know what actually good usage for it, like example in multiplayer games wherein you have to make sure the states are synced between objects and jumping to states could solve it.

The branch feature/transitions-as-dictionary has been merged to develop and I just added the method MoveToState(ScriptableState targetState) so you can jump directly to a specific state. You can target the package to the develop branch to get this changes.


Build jyable

ok

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

Pull Request create by mistake. It's azure DevOps sample Exercice


Fixing typo in README.md

Fixed typo at line 263

Thanks for noticing that, I have some other tweaks I'm making so I'll just roll that in with them.


sourceProtocol: automatic option not handles TCP-only stream

Which version are you using?
v0.12.1
Enhancement request
Hi!
If camera streams from NAT/FW network, rtsp-ss reports UDP timeout, retrying with TCP, then method PAUSE failed: 551 Option not supported, then stops. But if I change sourceProtocol: automatic to sourceProtocol: tcp all works fine! :)
VLC player correctly works with same situations and automatically switches to TCP only protocol. I think if I choose sourceProtocol: automatic rtsp-ss must apply the same logic.
This is an example of the same task execution with ffmpeg (stream from HikVision IPC):
$ ffmpeg -hide_banner -i rtsp://xxx:zzz@example.com:503/Streaming/Channels/102 -c copy -f null -
[rtsp @ 000001ea47e8d800] UDP timeout, retrying with TCP
[rtsp @ 000001ea47e8d800] method PAUSE failed: 551 Option not supported
[rtsp @ 000001ea47e8d800] Could not find codec parameters for stream 0 (Video: h264, none): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
Input #0, rtsp, from 'rtsp://xxx:zzz@example.com:503/Streaming/Channels/102':
  Metadata:
    title           : Media Presentation
  Duration: N/A, bitrate: N/A
    Stream #0:0: Video: h264, none, 90k tbr, 90k tbn, 180k tbc
Output #0, null, to 'pipe:':
Output file #0 does not contain any stream

Hello, i always disliked the ffmpeg behavior, because it doesn't allow users to recognize if the stream is being pulled with UDP or TCP, and therefore doesn't allow to catch eventual firewall problems.
BUT since the server has a streamProtocol: automatic parameter, it should probably switch to TCP automatically to solve these kind of problems - users that want to force UDP can use streamProtocol: udp

Hello, i always disliked the ffmpeg behavior, because it doesn't allow users to recognize if the stream is being pulled with UDP or TCP, and therefore doesn't allow to catch eventual firewall problems.
BUT since the server has a streamProtocol: automatic parameter, it should probably switch to TCP automatically to solve these kind of problems - users that want to force UDP can use streamProtocol: udp

I don't get it, what is the current purpose of "automatic" if it doesn't switch automatically to tcp?

The automatic value switches protocol automatically if the server replies with 451 - unsupported protocol - currently it doesn't switches if there's a NAT problem - this 2nd case must be handled with an enhancement.

This feature is implemented in main and will be added to the next release.

added in v0.15.2


[Feature Request] Renaming a folder/file should be mirrored in code

Use case:
folder1 and index.ts on the same level
/folder1
   FileFromFolder1.ts
index.ts

Following code in index.ts
import './folder1/FileFromFolder1';
Action: rename folder1 to folder2
Expected: all the places in the code where folder1 is referenced automatically update to folder2.

Duplicate of #19439


How to increase scanning area in camera?

im searching for how to increase scanning area in this library, but not find them

Yes, I would like to know too. On devices that have larger screen resolution, scanning area is really small and hard to scan QR/barcodes.

Have you guys got any solution??

Hi! Can somebody provide a solution for this topic? Cheers and thanks in advance, Nikola

In my opinion it's also not correct, that the showed scanning area is small and rectangular if I set:
Barcode.TWO_D_CODE_TYPES
In my case I just wanna scan QR-Codes and data-matrix codes.

any updates on this?


Signing a Transaction Offline Guide

2 screeshots
1 example code (typescript)

Looks good to me, we will improve the process before merging to not have to open the SDK to construct the URI.

Some notes to myself:

It would be nice if the process could be done completely using only CLI (See nemtech/symbol-cli#328)
TS and CLI code should be shown together using example code blocks as done in the Delegated Harvesting guide #531.
"Create an offline account" should be a prerequisite and explain where to get all that info.
Obviously no screenshots, only text


Panic on ubuntu-server / wsl

If i try use this on ubuntu-server or windows subsystem for linux (wsl) / bash on windows I get the following error
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: SecretServiceError(Dbus(D-Bus error: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 (org.freedesktop.DBus.Error.NotSupported)))', /checkout/src/libcore/result.rs:916:4

is X11 really needed to access the keyring?

This was fixed in release 0.10.4.  See the README for info about using the keyring on headless systems.


Regenerate local development certificate for ETCD/GAPI

How to categorize this PR?

/area dev-productivity
/kind enhancement
What this PR does / why we need it:
The old client certificate for gardener-apiserver to talk to ETCD has expired, see e.g. in https://storage.googleapis.com/gardener-prow/pr-logs/pull/gardener_gardener/7067/pull-gardener-e2e-kind-ha-single-zone/1599666466070728704/artifacts/gardener-local-ha-single-zone-worker2/pods/garden_etcd-0_16e43430-e0f8-4bb9-8037-32016e7a8195/etcd/0.log:
2022-12-05T07:34:30.381852537Z stderr F {"level":"warn","ts":"2022-12-05T07:34:30.381Z","caller":"embed/config_logging.go:169","msg":"rejected connection","remote-addr":"<IP_ADDRESS>:37212","server-name":"etcd-client.garden.svc","error":"tls: failed to verify client certificate: x509: certificate has expired or is not yet valid: current time 2022-12-05T07:34:30Z is after 2022-12-03T06:11:00Z"}

This PR regenerates the certificates with a longer validity (10y).
Release note:

NONE

/cherry-pick release-v1.59

/cherry-pick release-v1.60

/cherry-pick release-v1.61

/cherry-pick release-v1.61


Troubleshooting - Add GPOs

Peer discovery appears to be affected by GPO settings (such as the "Minimum disk size allowed to use peer caching" setting) and should be added as Troubleshooting steps to ensure GPO is not being too strict and preventing machines from being peers or discovering peers.

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

ID: eb67e518-6f60-23e0-2545-c2839e2b4159
Version Independent ID: e9a31629-e3cb-0367-31c4-5661284d89bf
Content: Configure Delivery Optimization for Windows 10 updates (Windows 10) - Windows Deployment
Content Source: windows/deployment/update/waas-delivery-optimization.md
Product: w10
Technology: windows
GitHub Login: @jaimeo
Microsoft Alias: jaimeo

@officedocsbot assign @jvsam

Hello @Jlentz4, we appreciate you taking the time to share your feedback. Do you have any suggestion on the exact messaging that you want to see on the the documentation so we can assist in creating a Pull Request (PR), and submit it to the author for review and approval? And if this is the topic (Delivery Optimization for Windows 10 updates) where update should be added? Also, there is already information under More detail on Delivery Optimization settings regarding requirements and best practices. Thank you.
NOTE: This GitHub-based documentation feedback system is designed to allow community contributions. If you have suggestions or ideas that you want the MS authors to review and apply (if approved) to the docs, you can create a Pull Request (PR) and start contributing to Microsoft Docs. You can check and read the Microsoft Docs contributor guide, if you are interested. The content page contains information on working with GitHub repositories, Markdown tools, etc.

Just to add, this MS Video provides a great explanation when it comes to Custom Device Settings and Peer Caching.
https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/Peer-Caching-Part-1-Caching-Understanding-the-options/ba-p/657036

Hi,
Yes, this is where it should be added. Specifically I think it would be a good idea to add a section in troubleshooting to double-check existing GPO and Local GPO settings to ensure they aren’t set too strict which would prevent clients from becoming peers. For instance, if the minimum disk drive size is set too large, devices may not become peers. Does this answer your question?
Thanks,
Joe Lentz
IT Infrastructure Engineer
Corporate Workstation Engineering
From: Jo<EMAIL_ADDRESS>Sent: Sunday, December 29, 2019 10:11 AM
To: MicrosoftDocs/windows-itpro-docs<EMAIL_ADDRESS>Cc: Lentz, Joe<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [EXTERNAL] Re: [MicrosoftDocs/windows-itpro-docs] Troubleshooting - Add GPOs (#5726)
EXTERNAL SENDER
Hello @Jlentz4https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FJlentz4&data=02|01|Joe.S.Lentz%40lowes.com|055ae4b8ab964b6733d408d78c715051|bcfa3e87841e48c7983b584159dd1a69|0|0|637132290627392323&sdata=MM6X5pH22ojJKhyIgOSZfWItx90pOmc66%2F4XDPLkT%2Bk%3D&reserved=0, we appreciate you taking the time to share your feedback. Do you have any suggestion on the exact messaging that you want to see on the the documentation so we can assist in creating a Pull Request (PR), and submit it to the author for review and approval? And if this is the topic (Delivery Optimization for Windows 10 updates) where update should be added? Also, there is already information under More detail on Delivery Optimization settingshttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fupdate%2Fwaas-delivery-optimization-reference%23more-detail-on-delivery-optimization-settings&data=02|01|Joe.S.Lentz%40lowes.com|055ae4b8ab964b6733d408d78c715051|bcfa3e87841e48c7983b584159dd1a69|0|0|637132290627392323&sdata=qPIqYmUWjL6ei34mGmdfMaOpf%2F6J64icx8DrITT6Prs%3D&reserved=0 regarding requirements and best practices. Thank you.
NOTE: This GitHub-based documentation feedback system is designed to allow community contributions. If you have suggestions or ideas that you want the MS authors to review and apply (if approved) to the docs, you can create a Pull Request (PR) and start contributing to Microsoft Docs. You can check and read the Microsoft Docs contributor guidehttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fcontribute%2F&data=02|01|Joe.S.Lentz%40lowes.com|055ae4b8ab964b6733d408d78c715051|bcfa3e87841e48c7983b584159dd1a69|0|0|637132290627402266&sdata=qhInHjpqTj%2FBekmPBz4lS9cIe4w5SJOn7RphShi%2BjrE%3D&reserved=0, if you are interested. The content page contains information on working with GitHub repositories, Markdown tools, etc.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwindows-itpro-docs%2Fissues%2F5726%3Femail_source%3Dnotifications%26email_token%3DAOC4MNIUVDUVDVETWQXRNLLQ3C4X7A5CNFSM4J6BX4H2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHZBRLA%23issuecomment-569514156&data=02|01|Joe.S.Lentz%40lowes.com|055ae4b8ab964b6733d408d78c715051|bcfa3e87841e48c7983b584159dd1a69|0|0|637132290627402266&sdata=HluRaTfEnCIpR7LCDlZOeImb9mquH9W407HB1Ybj6Qo%3D&reserved=0, or unsubscribehttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOC4MNJ37NS6UYXDIJ2LKWTQ3C4X7ANCNFSM4J6BX4HQ&data=02|01|Joe.S.Lentz%40lowes.com|055ae4b8ab964b6733d408d78c715051|bcfa3e87841e48c7983b584159dd1a69|0|0|637132290627412231&sdata=4dhpO0i2VVUlCmcJ8x6SUGgt6aqOFTtDQNJpk90KKwg%3D&reserved=0.

NOTICE: All information in and attached to the e-mails below may be proprietary, confidential, privileged and otherwise protected from improper or erroneous disclosure. If you are not the sender's intended recipient, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this message. If you have erroneously received this communication, please notify the sender immediately by phone<PHONE_NUMBER>) or by e-mail and destroy all copies of this message electronic, paper, or otherwise. By transmitting documents via this email: Users, Customers, Suppliers and Vendors collectively acknowledge and agree the transmittal of information via email is voluntary, is offered as a convenience, and is not a secured method of communication; Not to transmit any payment information E.G. credit card, debit card, checking account, wire transfer information, passwords, or sensitive and personal information E.G. Driver's license, DOB, social security, or any other information the user wishes to remain confidential; To transmit only non-confidential information such as plans, pictures and drawings and to assume all risk and liability for and indemnify Lowe's from any claims, losses or damages that may arise from the transmittal of documents or including non-confidential information in the body of an email transmittal. Thank you.


Current Suggestions

Suggestions for Improvement
Error Handling: Implement error handling to catch and respond to common issues, such as permission errors, file not found, or directory not empty errors. This will make your application more robust and user-friendly.
File and Directory Checks: Before performing operations like delete, rename, or move, check if the file or directory exists. This can prevent exceptions from being raised and provide a clear message to the user if the operation cannot be performed.
Path Validation: Validate paths in methods like move_file, copy_file, etc., to ensure they are valid and accessible. This can help avoid errors and inconsistencies.
Enhance list_directories Method: Currently, your method for listing directories iterates over self.files, which may not always be up-to-date with the current directory's state. Consider fetching a fresh list from the filesystem at the start of this method or utilizing pathlib for more sophisticated filesystem interactions.
Use of pathlib: You've imported pathlib but haven't used it. pathlib offers a more intuitive approach to handling filesystem paths. Consider using pathlib.Path objects for path operations, as they can make your code cleaner and more Pythonic.
Unit Testing: Start thinking about how you can add unit tests for your classes and methods. This will help ensure your functions behave as expected under various conditions and make your code more maintainable in the long run.

README:
Thanks for sharing your README file! It provides a clear outline of your project and its objectives. Your File Management System (FMS) aims to be a versatile tool that integrates educational aspects of programming with practical file management capabilities.
Here are a few suggestions and considerations to focus on as you continue with the development of your FMS:
Code Structure and Organization
Modular Design: Ensure your code is organized in a modular fashion to facilitate maintenance and future expansions. This could involve separating file operations, user interface, and error handling into different modules or classes.
Class Design: Given your focus on object-oriented programming, make sure your classes are well-designed, encapsulating related properties and methods. This not only makes your code cleaner but also easier to understand and test.
Testing and Documentation
Unit Testing: Start writing tests alongside your code development. This will help you catch bugs early and ensure each part of your system works independently before integrating them.
Documentation: Continue to document your code extensively, especially functions and classes. Python's docstrings can be very handy for this purpose. This will make it easier for others (and your future self) to understand the code.
Features and Functionalities
Cross-platform Compatibility: Ensure that your application truly works across different operating systems. This might involve extensive testing on each platform or using a CI/CD pipeline to automate some of these tests.
Error Handling: Robust error handling will be crucial, especially since file operations can often result in permissions issues or file not found errors. Make sure these are handled gracefully and communicated to the user clearly.
User Experience
CLI Usability: Since the application is command-line based, consider the user experience in a terminal environment. Ensure commands are intuitive and feedback messages are helpful. You might want to include a help command or detailed usage instructions.
Performance: For operations like searching, ensure that they are optimized for performance, especially as the size of the data grows. This might involve considering different data structures for storing file metadata for quick searches.
Future Directions
GUI Consideration: While the CLI is great for simplicity and cross-platform compatibility, you might consider a GUI as a future enhancement to make the system more accessible to non-technical users.
Automation Features: Explore more automation possibilities such as scheduled backups or cleanups which can enhance the utility of your FMS.
Feedback and Community Involvement
Open Source: If you haven’t already, consider making the project open source to attract community contributions and feedback. Tools like GitHub can facilitate issue tracking, feature requests, and community engagement.
Conclusion
Your project is ambitious and covers a comprehensive range of functionalities. Focus on clean, maintainable code and don’t hesitate to refactor as you learn more during the development process. Testing and documentation should go hand-in-hand with your coding to ensure quality and maintainability.

You've made substantial progress with your File Management System (FMS). The code is well-organized and covers the functionalities you described in your README. Below, I'll provide feedback on potential improvements, bug fixes, and best practices.
General Observations and Improvements
Exception Handling:
Your current implementation does not handle exceptions that might occur during file operations (e.g., file not found, permission errors). It would be beneficial to add try-except blocks to handle such exceptions gracefully and inform the user of what went wrong without crashing the program.
Refactoring Suggestions:
Consider separating the logic for user input and file management operations more distinctly. This would make your CLI class primarily responsible for input/output, while the FileManager class handles all the logic related to file manipulations.
The method FileManager.refresh_files() is being called frequently. You might consider calling it automatically inside methods that change the filesystem (like create_file, delete_file, etc.) to ensure the file list is always up-to-date without requiring explicit calls.
Performance Considerations:
Repeatedly listing the directory contents (using os.listdir) can be inefficient, especially for directories with a large number of files. Consider optimizing this by maintaining an updated list of files within your class unless significant changes are detected.
Usability Enhancements:
Adding more detailed user prompts or help descriptions can improve the user experience, especially for users unfamiliar with command-line tools.
Implementing tab completion and history navigation (using libraries like readline in Unix-like systems) could significantly enhance the usability of your CLI.
Code Quality and Maintainability:
Adding docstrings to your methods would improve the maintainability of your code, making it easier for others (or yourself in the future) to understand what each method is supposed to do.
Consider using more descriptive variable names where possible. For example, instead of old_name, use current_filename to make it clear what the variable represents.
Specific Code Suggestions
Here’s how you can handle exceptions in a file operation, for example, when deleting a file:
python
Copy code
def delete_file(self, file_name):
try:
os.remove(file_name)
self.files.remove(file_name)
self.needs_refresh = True
print(f'File {file_name} deleted successfully.')
except FileNotFoundError:
print(f'Error: The file {file_name} does not exist.')
except PermissionError:
print(f'Error: You do not have permission to delete {file_name}.')
except Exception as e:
print(f'An unexpected error occurred: {e}')
Testing
Unit Testing: Begin writing unit tests for each class and method. Python's unittest or pytest frameworks can be used for this purpose. Testing will ensure that each function behaves as expected and also helps in catching errors early in the development process.
Final Thoughts
Overall, your project is well on its way to becoming a robust file management system. Incorporating these suggestions will not only improve the current functionality but also help in maintaining and scaling the project in the future. Keep up the great work, and continue documenting and testing as you develop your project. If you encounter specific issues or need further clarification on any part, feel free to ask!

Current Focuses Include:

Fixing method bugs - complete through sanitise method call adjustment
Fixing containment of Manger
Pausing implementation for cleaner CLI
Listing Directory contents


next release anytime soon?

Just wondering if there's a plan to make another release anytime soon, this tool is really useful but its usefulness is very limited without #893 . Thanks!

I will work on the release in the upcoming two weeks.


Add tests for errors in...

Opening output streams.

Done.


Feat/semantic release

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.94%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1522

Relevant Lines:
1522

💛  - Coveralls


[Bug]: table 290 "VAT Amount Line"

Describe the issue
In procedure SetInvoiceDiscountAmount(NewInvoiceDiscount: Decimal; NewCurrencyCode: Code[10]; NewPricesIncludingVAT: Boolean; NewVATBaseDiscPct: Decimal):
Within calculation of "Invoice Discount Amount"
 if "Invoice Discount Amount" <> Round(NewRemainder, Currency."Amount Rounding Precision") then begin
     Validate(
         "Invoice Discount Amount", Round(NewRemainder, Currency."Amount Rounding Precision"));
     CalcVATFields(NewCurrencyCode, NewPricesIncludingVAT, NewVATBaseDiscPct);
     Modified := true;
     Modify();
end;

Expected behavior
Instead of Currency."Amount Rounding Precision", field Currency."Invoice Rounding Precision" should be used for invoice amounts.
Our suggestion:
if "Invoice Discount Amount" <> Round(NewRemainder, Currency."Invoice Rounding Precision") then begin
    Validate(
        "Invoice Discount Amount", Round(NewRemainder, Currency."Invoice Rounding Precision"));
        CalcVATFields(NewCurrencyCode, NewPricesIncludingVAT, NewVATBaseDiscPct);
        Modified := true;
        Modify();
end;

Steps to reproduce
Set up Currency with different rounding values before calling the procedure SetInvoiceDiscountAmount(...)
Additional context
No response
I will provide a fix for a bug

[X] I will provide a fix for a bug

Why should be used this type of amount rounding?? "Invoice Rounding Precision" is meant for document rounding, not particular amounts. Or...?

You might be on to something here, but since the code you are referring to is in the BaseApp, you'd have to suggest and fix this code in the BaseApp contribution pilot: https://github.com/microsoft/businesscentralapps. For access to the pilot, please fill out the following form: https://forms.office.com/r/E9wyE5a58f.
This repository is only for extensibility requests or pull requests towards the 1st party Business Central apps.
Would you like me to move the issue to the contribution pilot for you?
IMPORTANT: Microsoft is not going to address the reported issue for you. You will have to get the issue approved, and then push a pull request with the suggested changes yourself. If you would like Microsoft to address the issue, please create a support request.

Please open issue in BusinessCentralApps repo, if you would like to address this issue.


🐞 [BUG] - Add Appropriate Route to "View More Hackathons" Button and Update Hackathons Section

Description
The "View More Hackathons" button in the hackathons section of the website currently reloads the page upon clicking, instead of navigating to a designated page or section displaying additional hackathons. This results in a poor user experience and does not provide users with the expected functionality to explore more hackathons. Additionally, the hackathons section needs to be updated with appropriate hackathon content to ensure accurate and up-to-date information.
Please assign me this issue,I will fix routes and add relevant hackthons in hackathon section
Current behaviour
Clicking the "View More Hackathons" button reloads the page, providing no additional hackathon content or navigation.
Expected behaviour
Upon clicking the "View More Hackathons" button, users should be directed to a designated page or section that displays additional hackathons, allowing them to explore more opportunities. The hackathons section should also be regularly updated with appropriate hackathon content to reflect the latest and relevant information.
Reproduction steps
1. Visit the website's homepage.
2. Locate the hackathons section.
3. Click the "View More Hackathons" button.

Screenshots
No response
Logs
No response
Browsers
No response
OS
Windows
Are you contributing for a program ?
GSSoC2023
Code of Conduct

[X] I have read and agree to the Contributing Guidelines of this project.

ok


FancyZones "Enable quick layout switch" not working

Microsoft PowerToys version
0.47.0
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
I have two custom layouts assigned to #1 and #2. When I hit CTRL + WIN + ALT + 1 (or 2), the layout I currently have selected flashes on the screen, but I cannot change between the layouts unless I manually go into FancyZones and select with the mouse.
✔ Expected Behavior
Be able to change between FancyZones layouts with intended keyboard shortcuts
❌ Actual Behavior
I cannot change layouts as described above.
Other Software
No response

Thank you for reporting!
This issue is a duplicate of https://github.com/microsoft/PowerToys/issues/13585. The fix would be in the next release.


Improve Ractor-compliance

In order to become Ractor-compliant, CSV should avoid relying on class variables and global variables.
Additionally, since Converters and HeaderConverters are not accessible from Ractors, defining get_converters and get_header_converters (which access Ractor-local versions) can allow for an alternative within Ractors.

How did you confirm that these changes are needed to use in Ractor?
Can we create test cases for Ractor?

How did you confirm that these changes are needed to use in Ractor?
Can we create test cases for Ractor?

If CSV tries to parse a file from a Ractor, it looks for the converters, but since they are unfrozen shared constants, it can't access them.
I've written some tests for using CSV in Ractors. I can upload them soon.

Thank you so much for your suggestions! I will update the pull request and rebase within the next few days.

I have made the updates and done the rebasing. I hope it is okay! Please let me know if there is any way I can improve it.

I'll merge this.
Thanks!

I'll merge this. Thanks!

Thanks so much for your support and patience!


⚠ Community has degraded performance

In a265887, Community (https://community.wrk.com/health) experienced degraded performance:

HTTP code: 200
Response time: 282 ms

Resolved: Community performance has improved in 3f48498.


Nvt dtypes

Sets up nvt dtypes

please refer to rfc here: https://github.com/NVIDIA-Merlin/rfcs/pull/1

Closing since this PR has gotten out of date with main, but I still think we should consider grouping dtype, is_list, and is_ragged into a small dataclass that represents NVT dtypes.


Pytest assert functions

Is this a reasonable function to use with py.test? In place of the inheritance .assertVariableEqual etc.

Do we want separate functions for each class?
There's a comment or just switch to py.test and add an appropriate hook. - is that different to what's here?
This still needs to be completed, with additional functions for assert _identical and assert_approx_equal.
Do we want more description for the failure, above just printing the arguments? That can also be added later

Do we want separate functions for each class?

That seems like overkill -- I think one is fine.

There's a comment or just switch to py.test and add an appropriate hook. - is that different to what's here?

I was thinking of something like how python lets you override the message for assert a == b. But it actually looks like there is no suitable hook for custom explanations when using methods. __traceback__ = False, like you do here, is about the best you can do.

Do we want more description for the failure, above just printing the arguments? That can also be added later

It's nice to at least print the objects on separate lines, e.g., using something like '%r\n%r' % (a, b) for the assert message. Otherwise multi-line reprs end up with the start of the second object on the same line as the first.

Updated.
Is it worth 'testing the tests'? I couldn't find tests for the existing functions

Thanks for the feedback and apologies for the silly errors. Updated.

@shoyer green

This looks good to me. The last thing I would do is switch the existing test methods like assertDatasetEqual to use these functions, just to reduce the amount of redundant code (and also test your new functions more extensively).

The last thing I would do is switch the existing test methods like assertDatasetEqual to use these functions, just to reduce the amount of redundant code (and also test your new functions more extensively).

All of tests? I think that's a fairly heavy lift for this PR. It also happens to be really tedious and unfortunately I don't think Find / Replace-able... If you feel strongly I'll plug in and go through though!
Otherwise we can roll out over time as people write new tests

No no no... Just the definitions of the methods like assertDatasetEqual on
the bass xarray TestCase class, which you can now define as aliases to your
new functions.
On Wed, Dec 14, 2016 at 8:17 PM Maximilian Roos<EMAIL_ADDRESS>wrote:

The last thing I would do is switch the existing test methods like
assertDatasetEqual to use these functions, just to reduce the amount of
redundant code (and also test your new functions more extensively).
All of tests? I think that's a fairly heavy lift for this PR. It also
happens to be really tedious and unfortunately I don't think Find /
Replace-able... If you feel strongly I'll plug in and go through though!
Otherwise we can roll out over time as people write new tests
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pydata/xarray/pull/1147#issuecomment-267234900, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABKS1hhpkMSPNJZ4mPZ-ncrUwRBuYVfeks5rIL9ogaJpZM4LA_ql
.

You might also add these to the API docs page and what's new. I know there has been interest in public test functions for quite some time.

I know there has been interest in public test functions for quite some time.

Yes, see also https://github.com/pydata/xarray/issues/754

@shoyer do you have ideas for when the types are not the same? For example, many of the tests compare Variable to IndexVariable. Should we not check types? Add a check_type=True argument to the testing functions? Change the tests so they're compliant?

In most cases I would guess these are broken tests?

There are more than a dozen: https://travis-ci.org/pydata/xarray/jobs/184356287#L2611
Also some binary / unicode errors - let me know if you have context

@shoyer I think I fixed all the tests. Running now
I didn't quite realize how many .assertVariable... tests were relying on coercion, so I ended up changing the tests in a lot of places. The test is explicit at the test site, at least.
There were a couple that I think are probably breaks - things like .argsort changing the type of a Variable. I marked those with comments but haven't fixed them - or we'll never get this in! Let me know if you have thoughts on any notes

Rebased on https://github.com/pydata/xarray/pull/1175, so that should be merged first if people agree

This is great! Before merge it would be good to add the new standalone assert_* functions to the API doc?

@fmaussion had a go - is that what you were thinking?

Thanks @MaximilianR , this will be useful for all libraries downstream of xarray

This is great.  At least in terms of the functionality I was looking for, I'd say this closes #754.

@shoyer green!

@shoyer green!


Upgrade dependencies to support Spring Boot 3.0.0-M4 and Spring Cloud 2022.0.0-M4

This original branch feature/spring-cloud-azure-6.x is our target branch to support Spring Boot 3, the major version 6.x will be a milestone version for Spring Cloud Azure developers, and the main branch will keep supporting the release version of Spring Boot.
We are preparing a Spring Cloud Azure milestone version based on Spring Boot 3.0.0-M4 and Spring Cloud 2022.0.0-M4 version. The Spring Data Cosmos and Spring Cloud Aapconfiguration parts will be excluded in the first Spring Cloud Azure milestone plan due to not compatibility with Spring Boot M4, they may be in the second milestone version.

Hi @rickle-msft , could you help to fix this test class BlobBaseAPITest failure?
[ERROR]   BlobBaseAPITest » Runtime PlaybackOnly has expired. Test must be reenabled https://dev.azure.com/azure-sdk/public/_build/results?buildId=1790627&view=logs&j=db7f3316-29bb-5f13-7d13-93829baced1b&t=80498dcb-de51-5a57-0f05-1252d7fcc56a&l=7718

Hi @kushagraThapar, could you help to fix this below failure in the Cosmos ci pipeline?
[ERROR] Error occurred during initialization of boot layer [ERROR] java.lang.module.FindException: Unable to derive module descriptor for /mnt/vss/_work/1/.m2/repository/io/micrometer/micrometer-core/1.10.0-M3/micrometer-core-1.10.0-M3.jar https://dev.azure.com/azure-sdk/public/_build/results?buildId=1790628&view=logs&j=c1fb1ddd-7688-52ac-4c5f-1467e51181f3&t=270374a4-721a-5366-7f60-bad5b1983827&l=27

/azp run java - spring - tests

Hi @sima-zhu we ran into the below issue when using the Spring Boot 3.0.0-M4 dependencies, could you help to release the newest version for the SDK azure-storage-file-share to support us as we move forward with the Spring Cloud Azure milestone release?
NoSuchMethod 'reactor.core.scheduler.Scheduler reactor.core.scheduler.Schedulers.elastic()' https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1793583&view=logs&j=9e025025-7104-51a5-7583-c78a51c691cc&t=942208af-db0c-5a9f-4ec0-d792ce77c137&l=1850

Hi, @ZejiaJiang  we ran into the same below issue when using the Spring Boot 3.0.0-M4 dependencies, could you help to release the newest version for the SDK azure-messaging-servicebus to support us as we move forward with the Spring Cloud Azure milestone release?

@moarychan - micrometer is a common module which is used across multiple azure SDKs. Wondering if the issue is only with cosmos CI pipeline, or with micrometer in general.
Is the issue with a specific micrometer version? If so, we can update it.

Hi @moarychan , we've already release the latest version SDK for azure-messaging-servicebus which is v7.10.1 on 8/18/2022.
The error message show that there may be a conflict version about the project-reactor I assumed. So could you please double check the reactor-core version is correct? The former comments for azure-storage-file-share is same.
<dependency>
  <groupId>io.projectreactor</groupId>
  <artifactId>reactor-core</artifactId>
  <version>3.4.21</version> <!-- {x-version-update;io.projectreactor:reactor-core;external_dependency} -->
</dependency>

Hi @moarychan , we've already release the latest version SDK for azure-messaging-servicebus which is v7.10.1 on 8/18/2022.
You can try it. I think it will work.

Thanks for your update! @JimSuplizio @srnagar please help set up the pipeline to sync this difference.

/azp run java - spring - tests

@moarychan - micrometer is a common module which is used across multiple azure SDKs. Wondering if the issue is only with cosmos CI pipeline, or with micrometer in general. Is the issue with a specific micrometer version? If so, we can update it.

Hi @kushagraThapar , I can not reproduce the error [ERROR] java.lang.module.FindException: Unable to derive module descriptor for /mnt/vss/_work/1/.m2/repository/io/micrometer/micrometer-core/1.10.0-M3/micrometer-core-1.10.0-M3.jar, but I can reproduce the below exception, could you help to take a look?

@moarychan  - this exception looks like out of memory issue - since the VM crashed. However, I will take a look at the exception logs and will update this thread.

I don't understand the reason for excluding the appconfiguration and cosmos spring libraries from the generate_from_source_pom and their respective ci.yml files. It seems that if these libraries are also going to need to be updated to this later version of spring, that these should be building as normal and not being excluded.

@JimSuplizio thanks for your update!
We plan to roll out the millestone version of Spring Cloud Azure 6.0 as soon as possible, there is currently not much effort to upgrade the test cosmos and appconfiguration spring modules, so we want to exclude them first, this is a temporary solution, the excluded changes will be reverted soon. At the same time, @stliu is promoting the migration of Spring-related modules to sdk/spring, including appconfiguration and cosmos spring libraries, so that we can manage and maintain them in a unified and timely manner.

This is the first PR to support Spring Boot 3, the below are main change categories:

Code changes:
1.1 Upgrade dependencies align with Spring Boot 3.0.0-M4 and Spring Cloud 2022.0.0-M4
1.2 Change imported package, migrates to jakata api, more detail from here https://spring.io/blog/2022/05/24/preparing-for-spring-boot-3-0
1.3 Commented out azure-spring-data-cosmos and its test modules in sdk/cosmos/pom.xml, because no Spring Data 3-based dependency is available.
1.4 Commented out azure-spring-cloud-appconfiguration-config and its associated modules in sdk/appconfiguration/pom.xml, because no compatible version is available.
1.5 Commented out spring-cloud-azure-starter-data-cosmos module in sdk/spring/pom.xml because there is no azure-spring-data-cosmos compatible version available, and also it will not be managed in spring-cloud-azure-dependencies.

Known issues left:
2.1 Spring Data for Azure Cosmos DB SQL API needs to be upgraded for Spring Data 3, more detail from here https://github.com/Azure/azure-sdk-for-java/issues/30458.
2.2 Azure Spring Cloud Feature Management Web needs to be upgraded for Spring Data 3, more detail from here https://github.com/Azure/azure-sdk-for-java/issues/30465.
2.3 No compatible dependency for wiremock, more detail from here https://github.com/wiremock/wiremock/issues/1760

Next
3.1 Migrate the Spring-related modules from the non-spring directory into sdk/spring, this action should include the appconfiguration and cosmos spring libraries.
3.2 Update reference doc and samples. The samples update is WIP, more detail from here https://github.com/Azure-Samples/azure-spring-boot-samples/pull/470.
3.3 Support Spring Cloud Azure 6.x in Spring Initialzr. more detail from here https://github.com/Azure/azure-sdk-for-java/issues/30357.

Hi @saragluna The code of the Spring Cloud Azure side is ready for supporting Spring Boot 3, please help review it, thanks!

API change check
API changes are not detected in this pull request.


WIP: Add optional dependent services to start

I wanted to get this PR out early and get notes before I moved too far along with it.
The gist of it is, links in docker-compose are deprecated and there really isn't a clean way (that I've found) to start dependent services inside of compose unless you do it manually. That's what this PR adds, a deps array to specify dependent services in your yaml that will be started at a scale of 1 for you to test against.
I'm happy to take any feedback or questions you might have around motive or what the end result looks like.

Signed-off-by: Elliott Davis<EMAIL_ADDRESS>

Have you investigated the Docker Compose depends_on configuration property? I think that does what you might need, and we may not need an extra plugin configuration option.

Thank you for taking the time to submit a Pull request though! That’s awesome 🙌🏼😊

Afaik the depends_on syntax was removed in compose version 3. Links is
still there but is marked for deprecation. I am currently leveraging
external_links but those don't start dependent containers in compose.
On Fri, Mar 1, 2019, 6:24 PM Tim Lucas<EMAIL_ADDRESS>wrote:

Thank you for taking the time to submit a Pull request though! That’s
awesome 🙌🏼😊
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/buildkite-plugins/docker-compose-buildkite-plugin/pull/203#issuecomment-468858388,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABE_baMEirRQXs-JxVpE-oJr7NJPyDthks5vScS6gaJpZM4bZ-Jt
.

Afaik the depends_on syntax was removed in compose version 3

I don't believe so, that's basically the point of docker-compose! Check out https://docs.docker.com/compose/compose-file/#depends_on-1.
They deprecated links a while back.
I'd be in favour of a depends_on param that allows extra dependencies to be added though!

Version 3 no longer supports the condition form of depends_on

I misread that line in the docs
I'll get this PR fixed up based on your suggestion. Thanks again for the feedback!

Alternatively, if you don't need the option anymore, it's probably best if we just leave it until someone needs the extra functionality?

depends on worked as advertised - closing this - thanks again @toolmantim

🙌🏼 Nice one @elliott-davis


Horizontal rule hard-coded margin introduced in Beta

Since the beta version of Bootstrap, the margin of the horizontal rule defined in _type.scss is a hard-coded making it difficult to customize.
In latest alpha:
// type.scss line 53:
hr {
  margin-top: $spacer-y;
  margin-bottom: $spacer-y;
  //...
}

In beta:
// type.scss line 53:
hr {
  margin-top: 1rem;
  margin-bottom: 1rem;
  //...
}

I would like this margin to use a variable so that it can be customized.

Hi @ernestbofill it was updated here: https://github.com/twbs/bootstrap/commit/ed1de86794cc0911dc7a3dbbf3bb9dfe421ef4b6
I'll create a PR to add hr variables.


Configure failure with Qt >= 5.10

The failure is caused by https://github.com/fanout/pushpin/blob/2a386e5ec9219003edc8185e0b91fc595dc1f6a2/configure#L216
?.?.? fails to match a two-digit minor version. So any version > 5.9 will fail.
The error is
==> ./configure --prefix=/usr/local/Cellar/pushpin/1.17.0 --configdir=/usr/local/etc --rundir=/usr/local/var/run --logdir=/usr/local/var/log --extraconf=QMAKE_MACOSX_DEPLOYMENT_TARGET=10.11
Configuring Pushpin ...
Verifying Qt build environment ... fail

Reason: Unable to find the 'qmake' tool for Qt 4 or 5.

Be sure you have a proper Qt 4.0+ build environment set up.  This means not
just Qt, but also a C++ compiler, a make tool, and any other packages
necessary for compiling C++ programs.

If you are certain everything is installed, then it could be that Qt is not
being recognized or that a different version of Qt is being detected by
mistake (for example, this could happen if $QTDIR is pointing to a Qt 3
installation).  At least one of the following conditions must be satisfied:

 1) --qtdir is set to the location of Qt
 2) $QTDIR is set to the location of Qt
 3) QtCore is in the pkg-config database
 4) qmake is in the $PATH

This script will use the first one it finds to be true, checked in the above
order.  #3 and #4 are the recommended options.  #1 and #2 are mainly for
overriding the system configuration.

I can work around it by string replacing "?.?.?" with "?.??.?"

Thanks for the report. Version 1.17.1 released with a fix.

Thanks @jkarneges! Voilà https://github.com/Homebrew/homebrew-core/pull/21624

Thank you for updating our packages. :)


ci: auto-discover all strategies and matrix forge tests across them

:v: started studying the repo and saw that mev-share-uni-arb was not getting tested in ci
this should prevent that step in the future
tested locally with act:
act --container-architecture linux/amd64 --workflows .github/workflows/contracts.yml

Local output
[Solidity/Strategy list] 🚀  Start image=ghcr.io/catthehacker/ubuntu:act-latest
[Solidity/Strategy list]   🐳  docker pull image=ghcr.io/catthehacker/ubuntu:act-latest platform=linux/amd64 username= forcePull=false
[Solidity/Strategy list]   🐳  docker create image=ghcr.io/catthehacker/ubuntu:act-latest platform=linux/amd64 entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[Solidity/Strategy list]   🐳  docker run image=ghcr.io/catthehacker/ubuntu:act-latest platform=linux/amd64 entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[Solidity/Strategy list]   🐳  docker exec cmd=[mkdir -m 0777 -p /var/run/act] user=root workdir=
[Solidity/Strategy list]   🐳  docker cp src=/Users/sam/dev/artemis/. dst=/Users/sam/dev/artemis
[Solidity/Strategy list]   🐳  docker exec cmd=[mkdir -p /Users/sam/dev/artemis] user= workdir=
[Solidity/Strategy list] ⭐  Run actions/checkout@v2
[Solidity/Strategy list]   ✅  Success - actions/checkout@v2
[Solidity/Strategy list] ⭐  Run echo "::set-output name=matrix::$(ls ./crates/strategies | jq -R -s -c 'split("\n")[:-1]')"
[Solidity/Strategy list]   🐳  docker exec cmd=[bash --noprofile --norc -e -o pipefail /var/run/act/workflow/set-matrix] user= workdir=
[Solidity/Strategy list]   ⚙  ::set-output:: matrix=["mev-share-uni-arb","opensea-sudo-arb"]
[Solidity/Strategy list]   ✅  Success - echo "::set-output name=matrix::$(ls ./crates/strategies | jq -R -s -c 'split("\n")[:-1]')"
[Solidity/tests-2      ] 🧪  Matrix: map[target:opensea-sudo-arb]
[Solidity/tests-2      ] 🚀  Start image=ghcr.io/catthehacker/ubuntu:act-latest
[Solidity/tests-1      ] 🧪  Matrix: map[target:mev-share-uni-arb]
[Solidity/tests-1      ] 🚀  Start image=ghcr.io/catthehacker/ubuntu:act-latest
[Solidity/tests-1      ]   🐳  docker pull image=ghcr.io/catthehacker/ubuntu:act-latest platform=linux/amd64 username= forcePull=false
[Solidity/tests-2      ]   🐳  docker pull image=ghcr.io/catthehacker/ubuntu:act-latest platform=linux/amd64 username= forcePull=false
[Solidity/tests-2      ]   🐳  docker create image=ghcr.io/catthehacker/ubuntu:act-latest platform=linux/amd64 entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[Solidity/tests-1      ]   🐳  docker create image=ghcr.io/catthehacker/ubuntu:act-latest platform=linux/amd64 entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[Solidity/tests-2      ]   🐳  docker run image=ghcr.io/catthehacker/ubuntu:act-latest platform=linux/amd64 entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[Solidity/tests-1      ]   🐳  docker run image=ghcr.io/catthehacker/ubuntu:act-latest platform=linux/amd64 entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[Solidity/tests-2      ]   🐳  docker exec cmd=[mkdir -m 0777 -p /var/run/act] user=root workdir=
[Solidity/tests-1      ]   🐳  docker exec cmd=[mkdir -m 0777 -p /var/run/act] user=root workdir=
[Solidity/tests-2      ]   🐳  docker cp src=/Users/sam/dev/artemis/. dst=/Users/sam/dev/artemis
[Solidity/tests-2      ]   🐳  docker exec cmd=[mkdir -p /Users/sam/dev/artemis] user= workdir=
[Solidity/tests-1      ]   🐳  docker cp src=/Users/sam/dev/artemis/. dst=/Users/sam/dev/artemis
[Solidity/tests-1      ]   🐳  docker exec cmd=[mkdir -p /Users/sam/dev/artemis] user= workdir=
[Solidity/tests-2      ] ⭐  Run actions/checkout@v2
[Solidity/tests-2      ]   ✅  Success - actions/checkout@v2
[Solidity/tests-1      ] ⭐  Run actions/checkout@v2
[Solidity/tests-1      ]   ✅  Success - actions/checkout@v2
[Solidity/tests-2      ] ⭐  Run Install Foundry
[Solidity/tests-2      ]   ☁  git clone 'https://github.com/onbjerg/foundry-toolchain' # ref=v1
[Solidity/tests-1      ] ⭐  Run Install Foundry
[Solidity/tests-1      ]   ☁  git clone 'https://github.com/onbjerg/foundry-toolchain' # ref=v1
[Solidity/tests-2      ]   🐳  docker cp src=/Users/sam/.cache/act/onbjerg-foundry-toolchain@v1/ dst=/var/run/act/actions/onbjerg-foundry-toolchain@v1/
[Solidity/tests-2      ]   🐳  docker exec cmd=[mkdir -p /var/run/act/actions/onbjerg-foundry-toolchain@v1/] user= workdir=
[Solidity/tests-1      ]   🐳  docker cp src=/Users/sam/.cache/act/onbjerg-foundry-toolchain@v1/ dst=/var/run/act/actions/onbjerg-foundry-toolchain@v1/
[Solidity/tests-1      ]   🐳  docker exec cmd=[mkdir -p /var/run/act/actions/onbjerg-foundry-toolchain@v1/] user= workdir=
[Solidity/tests-2      ]   🐳  docker exec cmd=[node<EMAIL_ADDRESS>user= workdir=
[Solidity/tests-1      ]   🐳  docker exec cmd=[node<EMAIL_ADDRESS>user= workdir=
| Downloading Foundry 'nightly' from: https://github.com/foundry-rs/foundry/releases/download/nightly/foundry_nightly_linux_amd64.tar.gz
[Solidity/tests-2      ]   💬  ::debug::Downloading https://github.com/foundry-rs/foundry/releases/download/nightly/foundry_nightly_linux_amd64.tar.gz
[Solidity/tests-2      ]   💬  ::debug::Destination /tmp/d4fabce3-ee14-419d-99ff-8009e30a83eb
| Downloading Foundry 'nightly' from: https://github.com/foundry-rs/foundry/releases/download/nightly/foundry_nightly_linux_amd64.tar.gz
[Solidity/tests-1      ]   💬  ::debug::Downloading https://github.com/foundry-rs/foundry/releases/download/nightly/foundry_nightly_linux_amd64.tar.gz
[Solidity/tests-1      ]   💬  ::debug::Destination /tmp/8040b3de-742f-4e6a-9f02-eefe023ed7fe
[Solidity/tests-1      ]   💬  ::debug::download complete
[Solidity/tests-1      ]   💬  ::debug::Extracting /tmp/8040b3de-742f-4e6a-9f02-eefe023ed7fe
[Solidity/tests-1      ]   💬  ::debug::Checking tar --version
[Solidity/tests-1      ]   💬  ::debug::tar (GNU tar) 1.34%0ACopyright (C) 2021 Free Software Foundation, Inc.%0ALicense GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.%0AThis is free software: you are free to change and redistribute it.%0AThere is NO WARRANTY, to the extent permitted by law.%0A%0AWritten by John Gilmore and Jay Fenlason.
| [command]/usr/bin/tar xz --warning=no-unknown-keyword --overwrite -C /tmp/c1873a17-2b87-4110-a498-6f9de8f1f33a -f /tmp/8040b3de-742f-4e6a-9f02-eefe023ed7fe
[Solidity/tests-2      ]   💬  ::debug::download complete
[Solidity/tests-2      ]   💬  ::debug::Extracting /tmp/d4fabce3-ee14-419d-99ff-8009e30a83eb
[Solidity/tests-2      ]   💬  ::debug::Checking tar --version
[Solidity/tests-2      ]   💬  ::debug::tar (GNU tar) 1.34%0ACopyright (C) 2021 Free Software Foundation, Inc.%0ALicense GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.%0AThis is free software: you are free to change and redistribute it.%0AThere is NO WARRANTY, to the extent permitted by law.%0A%0AWritten by John Gilmore and Jay Fenlason.
| [command]/usr/bin/tar xz --warning=no-unknown-keyword --overwrite -C /tmp/086c1522-b1dc-4fb9-abe1-0e0634ae9561 -f /tmp/d4fabce3-ee14-419d-99ff-8009e30a83eb
[Solidity/tests-1      ]   💬  ::debug::Resolved Keys:
[Solidity/tests-1      ]   💬  ::debug::["linux-foundry-chain-fork-88fb49346eb32b983fab9c7a035436ffc603a8d7","linux-foundry-chain-fork-"]
[Solidity/tests-1      ]   💬  ::debug::Checking zstd --version
[Solidity/tests-1      ]   💬  ::debug::*** zstd command line interface 64-bits v1.4.8, by Yann Collet ***
[Solidity/tests-1      ]   💬  ::debug::getCacheEntry - Attempt 1 of 2 failed with error: Cache Service Url not found, unable to restore cache.
[Solidity/tests-2      ]   💬  ::debug::Resolved Keys:
[Solidity/tests-2      ]   💬  ::debug::["linux-foundry-chain-fork-88fb49346eb32b983fab9c7a035436ffc603a8d7","linux-foundry-chain-fork-"]
[Solidity/tests-2      ]   💬  ::debug::Checking zstd --version
[Solidity/tests-2      ]   💬  ::debug::*** zstd command line interface 64-bits v1.4.8, by Yann Collet ***
[Solidity/tests-2      ]   💬  ::debug::getCacheEntry - Attempt 1 of 2 failed with error: Cache Service Url not found, unable to restore cache.
[Solidity/tests-1      ]   💬  ::debug::getCacheEntry - Attempt 2 of 2 failed with error: Cache Service Url not found, unable to restore cache.
[Solidity/tests-2      ]   💬  ::debug::getCacheEntry - Attempt 2 of 2 failed with error: Cache Service Url not found, unable to restore cache.
[Solidity/tests-1      ]   🚧  ::warning::Failed to restore: getCacheEntry failed: Cache Service Url not found, unable to restore cache.
[Solidity/tests-1      ]   💬  ::debug::Failed to delete archive: Error: ENOENT: no such file or directory, unlink ''
[Solidity/tests-1      ]   ✅  Success - Install Foundry
[Solidity/tests-1      ] ⭐  Run Foundry version
[Solidity/tests-1      ]   🐳  docker exec cmd=[bash --noprofile --norc -e -o pipefail /var/run/act/workflow/2] user= workdir=
| forge 0.2.0 (06a17bf 2023-08-19T00:14:54.453240995Z)
[Solidity/tests-1      ]   ✅  Success - Foundry version
[Solidity/tests-1      ] ⭐  Run Run ${{ matrix.target }} tests
[Solidity/tests-1      ]   🐳  docker exec cmd=[bash --noprofile --norc -e -o pipefail /var/run/act/workflow/3] user= workdir=
[Solidity/tests-2      ]   🚧  ::warning::Failed to restore: getCacheEntry failed: Cache Service Url not found, unable to restore cache.
[Solidity/tests-2      ]   💬  ::debug::Failed to delete archive: Error: ENOENT: no such file or directory, unlink ''
[Solidity/tests-2      ]   ✅  Success - Install Foundry
[Solidity/tests-2      ] ⭐  Run Foundry version
[Solidity/tests-2      ]   🐳  docker exec cmd=[bash --noprofile --norc -e -o pipefail /var/run/act/workflow/2] user= workdir=
| forge 0.2.0 (06a17bf 2023-08-19T00:14:54.453240995Z)
[Solidity/tests-2      ]   ✅  Success - Foundry version
[⠢] Compiling...
[Solidity/tests-2      ] ⭐  Run Run ${{ matrix.target }} tests
[Solidity/tests-2      ]   🐳  docker exec cmd=[bash --noprofile --norc -e -o pipefail /var/run/act/workflow/3] user= workdir=
[⠔] Installing solc version 0.8.21
[⠆] Compiling...
[⠃] Successfully installed solc 0.8.21
[⠰] Installing solc version 0.8.21
[⠘] Successfully installed solc 0.8.21
[⠔] Compiling 19 files with 0.8.21
[⠔] Solc 0.8.21 finished in 15.59s
| Compiler run successful with warnings: ...
|
| Running 1 test for test/BlindArb.t.sol:BlindArbTest
| [PASS] testArb() (gas: 255388)
| Test result: ok. 1 passed; 0 failed; 0 skipped; finished in 4.40s
| Ran 1 test suites: 1 tests passed, 0 failed, 0 skipped (1 total tests)
[Solidity/tests-1      ]   ✅  Success - Run ${{ matrix.target }} tests
[⠒] Compiling 124 files with 0.8.21
[⠊] Solc 0.8.21 finished in 65.91s
| Compiler run successful!
|
| Running 5 tests for test/SudoOpenseaArb.t.sol:SudoOpenseaArbTest
| [PASS] testFuzzTransferOwnership(address) (runs: 1024, μ: 17324, ~: 17324)
| [PASS] testFuzzTransferOwnershipUnauthorized(address) (runs: 1024, μ: 15295, ~: 15295)
| [PASS] testFuzzWithdraw(uint256) (runs: 1024, μ: 17953, ~: 18150)
| [PASS] testFuzzWithdrawUnauthorized(address) (runs: 1024, μ: 11934, ~: 11934)
| [PASS] testOwner() (gas: 9665)
| Test result: ok. 5 passed; 0 failed; 0 skipped; finished in 656.60ms
|
| Running 2 tests for test/SudoPairQuoter.t.sol:SudoPairQuoterTest
| [PASS] testCorrectSingleQuote() (gas: 38910)
| [PASS] testCorrectnessMultiQuote() (gas: 50341)
| Test result: ok. 2 passed; 0 failed; 0 skipped; finished in 1.68s
|
| Running 2 tests for test/SudoOpenseaArbFork.t.sol:SudoOpenseaArbForkTest
| [PASS] testArb() (gas: 475627)
| [PASS] testUnprofitableArb() (gas: 476083)
| Test result: ok. 2 passed; 0 failed; 0 skipped; finished in 5.29s
| Ran 3 test suites: 9 tests passed, 0 failed, 0 skipped (9 total tests)
[Solidity/tests-2      ]   ✅  Success - Run ${{ matrix.target }} tests

this just a tmp pr to make sure actions were running successfully


Alternative MDNS (CON-595)

If I turn off CONFIG_USE_MINIMAL_MDNS=y  the BLE bridge example won't build.
I am doing this to debug MDNS issues.

Thanks for the issue. We will fix it ASAP


Fix assertion in EntryPointInfo expiring

Previously when fixing a bug that when codegen failed, entryPointInfo is cleanedup with wrong(previously jitted code/thunk) address and causes the jit code freed prematurely.
I added the assert to capture we should not be expiring the entryPointInfo which has the address still installed on the functionType.
Here's another situation that the entryPointInfo on deferredPrototypeType (which is same as the default m_defaultEntryPointInfo) is already cleanedup due to some other reason (most likely hit the JitLimit, added Unknown to capture other cases). In this situation the Assertion can be wrong.

@curtisman @digitalinfinity can you review

LGTM


definitions for ml: concepts to be used by Croissant.

So it seems to me that we don't intend to use them as JSON-LD @type but more as dataType values. So I kind of feel strange to have them in the spec itself, but could be convinced otherwise.

Great! Left some very minor comments

Thanks!


Add influxdb metrics flags

What this PR does / why we need it:
Adds missing influxdb metrics emitter configuration options to the concourse atc.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:

/assign @william-tran

/assign

/ok-to-test

/ok-to-test

/lgtm