Split out machine-specific functionality into new file

I've introduced the idea of platforms. Platforms are the host medium for running a manycore, be it FPGA, VCS, or Verilator. This PR splits bsg_manycore.cpp into two files:
bsg_manycore.cpp: data copy in/out, packet tx/rx
bsg_manycore_platform.cpp: Machine-specific tx/rx, intialization
This should make supporting new machines easier. This work would have been needed eventually to support Black Parrot. It has probably already been done by Paul. It was definitely already done by me, for Verilator.
I also took the liberty of removing some old, outdated code. This simplifies the interface between manycore software and machine.
I need to test, and change how some verilog parameters are defined/passed to the ROM. Currently the FIFO depth is a gp in the AXI-Lite files, but it is read from the ROM like it is defined in the auto-generated manycore package files.
While not blocking, I also want to figure out how to make the VCS cosimulation specific clock switching code into something more generic.

This is ready for review. Passes on cosimulation (fast_n_fake, timing_v0_8_4) and on F1.

I'd say there are two directions here.

One is I can implement the host interface (MMIO fifos) in BP.  Then BP is just another host here.
What I've currently implemented is directly using physical addresses in the BP address space to do loads/stores from the manycore.  This is a more major change to the host interface.  Essentially we need to mmap the manycore into the host address space.  From there, the interface is simple MMIO.  All of these platform methods kind of...go away, since we are just using regular load/stores and native fencing.

We should have all have a meeting to discuss this further though.  But I guess my takeaway is this is a great abstraction if we continue to speak manycore packets.  Possibly the path forward is to implement host-api-on-blackparrot to sort out RISC-V wrinkles in the host software.  From there, moving to the new interface (or something like it) will be a matter of replacing software with hardware (which is my favorite thing to do :))

Yeah, we talked last (?) week. It's a good thought.
There are multiple ways to do this and I'm open to all approaches. It's turtles all the way down.
We could provide a DMA API (cuda-like), and a responder interface for manycore requests. (Hey! This exists!)
We could also provide a memory-mapped-like API. Then, like a normal linux driver we can mmap a region into BP. (Hey! This exists!)
One constant though: We will probably always speak manycore packets, or need to speak manycore packets. Verilator isn't going away.
So it's really up to what the BP folks decide to do. The manycore drivers are flexible.


Please write a template for VB.NET

I've tried everything I can think of to create a VB.NET version of the C# template, but I always end up with something like this in the output:
1>CONVERTTASK : Convert error : System.Exception: unknown call:System.String ExternalTest.TestFunctions::Main()
1>     at Neo.Compiler.MSIL.ModuleConverter._ConvertCall(OpCode src, AntsMethod to)
1>     at Neo.Compiler.MSIL.ModuleConverter.ConvertCode(ILMethod method, OpCode src, AntsMethod to)
1>     at Neo.Compiler.MSIL.ModuleConverter.ConvertMethod(ILMethod from, AntsMethod to)
1>     at Neo.Compiler.MSIL.ModuleConverter.Convert(ILModule _in)
1>     at Neo.Compiler.Program.Main(String[] args)

It has been done in https://github.com/neo-project/neo-devpack-dotnet/commit/2453bde48dd44afeb23c9103104901443111387d
Update your plugin and compiler before trying it.


[WIP]Adding pipelines e2e tests from console to console plugin .

Issue: https://issues.redhat.com/browse/ODC-7592

/ok-to-test

/retest

$ yarn test-cypress-headless
yarn run v1.22.22
$ cd integration-tests && node --max-old-space-size=4096 node_modules/.bin/cypress run --env openshift=true --browser ${BRIDGE_E2E_BROWSER_NAME:=chrome} --headless cypress:cli
node:internal/modules/cjs/loader:1146
  throw err;
  ^

Error: Cannot find module '/home/ppitonak/workspace/console-plugin/integration-tests/node_modules/.bin/cypress'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1143:15)
    at Module._load (node:internal/modules/cjs/loader:984:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:135:12)
    at node:internal/main/run_main_module:28:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v20.12.2
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

@sanketpathak Can you resolve the conflicts and update the PR?

Closing it in favor of pr https://github.com/openshift-pipelines/console-plugin/pull/133


Update map backend to handle crs

Issue: #
-Add a checker to convert map format if crs is used
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the met-public license (Apache 2.0).

Codecov Report

Merging #2273 (75c1677) into main (c1b874d) will decrease coverage by 0.02%.
Report is 3 commits behind head on main.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #2273      +/-   ##
==========================================
- Coverage   68.47%   68.46%   -0.02%
==========================================
  Files         472      472
  Lines       15602    15607       +5
  Branches     1191     1191
==========================================
+ Hits        10684    10685       +1
- Misses       4712     4716       +4
  Partials      206      206

Flag
Coverage Δ

metapi
76.44% <0.00%> (-0.04%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

met-api/src/met_api/services/shapefile_service.py
41.17% <0.00%> (-1.69%)
:arrow_down:

... and 1 file with indirect coverage changes


Use condensed table for the resources tab in the service inventory.

The service inventory uses a table with much higher rows compared to the other tabs.

Hey team! Please add your planning poker estimate with ZenHub @andraskvr @bartv @Stijnkool


Rewrite the rewriter deployment

Rewriter deployment is currently handled as a mix of configuration in solrconfig.xml and additional artefacts (like the 'rules.txt' files for the Common Rules rewriter).
This approach has a number of issues:

Applying changes in the configuration requires a collection/core reload. Depending on how long it takes to load the rewriters and on the 'useColdSearcher' setting, Solr can be left without a core to answer queries for a few moments.
The deployment is just not handy: updating an additional artefact like 'rules.txt' requires pushing data to ZooKeeper in the first step and then reloading the collection in a separate HTTP request. Some Querqy users also had to work around the file size limit in ZooKeeper.

I'd like to suggest rewriting the rewriter configuration and deployment from scratch. The goals should as follows:

A rewriter should be defined using a single HTTP call (REST API). This call should define, the name under which the rewriter can be used, the rewriter class to be loaded and all the specific settings for this rewriter. This implies that, in the case of the CommonRules rewriter, there will be no separate rules.txt file. (Compare 'Defining a rewriter' in Querqy for Elasticsearch - https://github.com/querqy/querqy-elasticsearch#defining-a-rewriter )
The API request handler should take care of validating the rewriter definition, storing it and replacing a previously loaded rewriter instance of the same name in a background process so that search traffic will not be disrupted. The request handler should also make the configuration size handling transparent to the client.
The API should define means to unload and delete rewriters.
Rewriter deployment should work in both, SolrCloud and stand-alone mode.

A few thoughts on the implementation:
I think we should get rid of a pre-configured rewriter chain when implementing this instead of creating a second API endpoint to configure the chain. We currently have three elements that are defined at chain level:

The list of rewriters. This could be specified per request (see Querqy for Elasticsearch implementation). As a positive side-effect, this would make the chain more flexible.
The term query cache. Much as it helped us in older Solr versions (around 4.x), it doesn't seem to provide any performance gain for current Solr/Lucene versions. We might just want to deprecate and remove it.
Sinks and mappings for rewriter logging. I think we can just provide standard sinks that are always available and then configure the mapping at rewriter level.

There seem to be two ideas where to save the rewriter configuration: in ZooKeeper or in a separate collection (maybe Solr's blob store). I leave this as a matter for discussion. If we did it in ZK we would need to make sure that we work around ZK file size limits (splits, compression) and that we are not mis-using ZK. If we used a separate collection we would probably have to think about the order in which collections are loaded. In both cases, we would have to think about how we propagate rewriter update events across nodes.
I've talked with a number of people about this issue, pinging you to join the discussion here: @JohannesDaniel @mkr @MighTguY @tboeghk

Hi,
I would not worry too much about ZooKeeper. In my experience, ZooKeeper has (sometimes) problems with large files, but not with many files. I have seen Hadoop clusters, where every app (Hadoop, Hive, Spark, Kafka, NiFi, Solr, ...) coordinates its nodes and app-configs via the same ZK ensemble in subdirectories.
I think I have not seen the case "a collection depends on another collection" at all so far. The additional suggester / spellcheck collections all require a path to a local index to be configured. I think enforcing an order of collections to be loaded might be tricky to be done via plugin?  Another approach might be that (re)loading rules from an existing collection will also include dumping all rules to a local file as a fallback.
I think the ZK approach should be less hacky, but also limited for future feature enhancements. This approach will not allow to add/delete/update single rules or to search/filter for rules.
Anyway, this appears to be tough decision :)

Have you seen the work on having proper plugins for Solr???   Lots of work
to help abstract you away from just these issues...
I believe that some major components of Solr, like velocity and DIH may
move to this approach and no longer ship with Solr.
It may be too early for this, but when Solr 9 comes out, this will be big
part of it.
On Mon, Feb 3, 2020 at 5:04 AM JohannesDaniel<EMAIL_ADDRESS>wrote:

Hi,
I would not worry too much about ZooKeeper. In my experience, ZooKeeper
has (sometimes) problems with large files, but not with many files. I have
seen Hadoop clusters, where every app (Hadoop, Hive, Spark, Kafka, NiFi,
Solr, ...) coordinates its nodes and app-configs via the same ZK ensemble
in subdirectories.
I think I have not seen the case "a collection depends on another
collection" at all so far. The additional suggester / spellcheck
collections all require a path to a local index to be configured. I think
enforcing an order of collections to be loaded might be tricky to be done
via plugin?  Another approach might
be that (re)loading rules from an existing collection will also include
dumping all rules to a local file as a fallback.
I think the ZK approach should be less hacky, but also limited for future
feature enhancements. This approach will not allow to add/delete/update
single rules or to search/filter for rules.
Anyway, this appears to be tough decision :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/querqy/querqy/issues/76?email_source=notifications&email_token=AAAFO66CDGPD27A7U67C7E3RA7TZHA5CNFSM4KOU3XY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKTHAHQ#issuecomment-581333022,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAFO6ZYSOWQRJPDQEJLE6LRA7TZHANCNFSM4KOU3XYQ
.

@epugh Yes, thank you, I saw it - and forgot to mention it here. As far as I understand the new plugin API just loads the plugin classes in a well defined way -> doesn't help us much with the rewriter configuration.
We should use the plugin API anyway, but it's probably a separate issue.

Thank you, @JohannesDaniel.
I was wondering about the file sizes that would be stored (in many files) in the other systems that you mentioned. I guess a 1000 small files in ZK mighty behave not the same way as 10-20 files of up to 1 MB....

Hi,
I would not worry too much about ZooKeeper. In my experience, ZooKeeper has (sometimes) problems with large files, but not with many files. I have seen Hadoop clusters, where every app (Hadoop, Hive, Spark, Kafka, NiFi, Solr, ...) coordinates its nodes and app-configs via the same ZK ensemble in subdirectories.
I think I have not seen the case "a collection depends on another collection" at all so far. The additional suggester / spellcheck collections all require a path to a local index to be configured. I think enforcing an order of collections to be loaded might be tricky to be done via plugin?  Another approach might be that (re)loading rules from an existing collection will also include dumping all rules to a local file as a fallback.
I think the ZK approach should be less hacky, but also limited for future feature enhancements. This approach will not allow to add/delete/update single rules or to search/filter for rules.
Anyway, this appears to be tough decision :)

Thank you, @JohannesDaniel.
I was wondering about the file sizes that would be stored (in many files) in the other systems that you mentioned. I guess a 1000 small files in ZK mighty behave not the same way as 10-20 files of up to 1 MB....

Well, the Hadoop ecosystem files were not too big, of course. And I cannot give you a guarantee that the ZK is going to work as expected. However, over some time we created a new config set via Solr Config API even for smaller rule changes. We temporarily had more than 100 config folders in our ZK (on DEV). We never had any error / warn log entries in the ZK logs or problems in Solr. Again, I would not be worried about the file management in ZK. I think the most critical disadvantage of ZK is the inflexibility regarding additional features to manage rules.
Finally, I was just thinking about creating a ZK ensemble on our K8 and to create, update and read a lot of files in order to see whether sync issues can be observed. Do you think this would help to get a better feeling for ZK file management?

I like the idea of configuration change without core reload and the more dynamic rewriter selection. Especially the core reload (or distributed collection reload in SolrCloud) can be painful. It seems to be a “stop-the-world” event, can have unintended side effects (unwanted IW-Commits when the current core is closed etc.) and always disrupts caching.
I like the REST approach of GET/PUT/DELETEing rewriters but wonder whether one then needs to take extra caution that a search application which relies on the existence of certain rewriters (by their symbolic name) can still work gracefully in their absence (e.g. by someone accidentally(?) renaming/deleting a rewriter in a live environment). Currently, in most systems I've seen this step required some kind of software build/deployment with all its pros (tests!) and cons (time + resources). Do we agree that any code changes (i.e. adjustments to rewriter code) will still need software deployment outside the scope of this issue? My general impression of Solrs "Package Manager" (https://lucene.apache.org/solr/guide/8_4/package-manager.html) is that it's more catered for the code deployment rather than the config deployment use case.
I think using Zookeeper and Lucene/Solr's provided ResourceLoader abstraction might be easier to use than a dedicated collection to store configuration. Still a bit worried about ZK's limitations. I remember previous projects where the ZK ensemble became unresponsive when we had znodes with >1000 children. The canonical way was: Announce configuration metadata via ZK but load the configuration (tens of MB) from a shared HA file store (e.g. S3). I would be fine with just GZipping the configuration data (assume we are talking about a few hundred bytes to 100KB max compressed) and store one config blob per rewriter in separate znodes.
We can try the "collection store" route and might have a look at how the BlobStore API does it but I guess all in all it's a bit more effort as you have to control the full life-cycle of that collection (create, schema, configset, adjust replication factor to have it present on all nodes etc.).

Thank you, @mkr and @JohannesDaniel for sharing your thoughts.
@mkr - I think it will be okay to leave the responsibility for using correct rewriter names/assuring rewriter existence to the client of Solr/Querqy. In the end, we've heard this wish to be able to configure rewriters via a HTTP/REST API numerous times and there would always be a chance to mess things up in the configuration.
I'm getting more and more convinced that ZK is the right approach. ZK is where we are storing configurations today and it is the place in Solr where configurations should be stored. Last but not least, we'd need ZK anyway even if we used a collection to inform nodes about rewriter configuration updates and, finally, we could go with ZK first and still move to the collection approach later as this would be hidden behind the API.
@JohannesDaniel please feel free to go ahead with the experiments you mentioned. I tried to find some clues about limitations in ZK but wasn't very successful. This might have some interesting insights: https://stackoverflow.com/questions/29791134/zookeeper-max-number-of-children-per-node - related to @mkr's observation on nodes with many children. I think would not hit these sizes but we might want to consider node name lengths (as described in the post on Stackoverflow).

as we somehow lost the drive here: probably it might be a nice first step simply to think about how to change rules / redeploy without core reload and annoying timeouts.

as we somehow lost the drive here: probably it might be a nice first step simply to think about how to change rules / redeploy without core reload and annoying timeouts.

@JohannesDaniel I think this is already the most tricky part. Rules are specific to the common rules rewriter. As a rewriter cannot receive an update we will have to change the rewriter framework so that a single rewriter can have a more flexible deployment. In addition, updating the rules (= the rewriter config) means that we need to create a new SolrSearcher in order to invalidate the query caches.
(Re timeouts: do you see timeouts if you set useColdSearcher=true)

@renekrie timeouts are about indexing, collection modification & collection reload...

The above commit is a first cut to configure rewriters via HTTP.
The simplest configuration for Querqy will now be (solrconfig.xml):

<searchComponent name="query" class="querqy.solr.QuerqyQueryComponent"/>

<requestHandler name="/querqy/rewriter" class="querqy.solr.QuerqyRewriterRequestHandler" />

<queryParser name="querqy" class="querqy.solr.QuerqyDismaxQParserPlugin" />

This will already allow to execute search requests using the Querqy query parser via defType=querqy.
Rewriters can be configured using URL path http://mysolr/solr/<collection or core>/querqy/rewriter/<rewriter id>. The ultimate goal is to use REST semantics (PUT, DELETE, ...) when making requests against this endpoint. For now, we mimic REST predicates by making POST requests and appending /_put or /_delete to the URL because v1/standalone Solr only allows for POST and GET requests.
(TODO: add proper REST endpoints and delegate to the same methods that handle POSTs against _put and _delete. We'll keep _put and _delete additionally to cover standalone Solr and early Solr 8.x versions. Optional: add GET /querqy/rewriter/<rewriter id> to read the configuration and GET /querqy/rewriter to get the list of rewriters).
With this commit, a rewriter can thus be configured using  a request like this:
POST  http://mysolr/solr/<collection or core>/querqy/rewriter/commonrules1/_put with payload:
{
    "class": "querqy.solr.rewriter.commonrules.CommonRulesRewriterFactory",
    "config": {
        "rules" : "notebook =>\nSYNONYM: laptop"
    }
}

Except for the Solr-specific class name, the configuration is identical to the format we use in Elasticsearch. https://docs.querqy.org/querqy/rewriters.html#list-of-available-rewriters.
Updates to rewriter configurations are applied without core/collection reloads. Configurations are validated before saving. An invalid configuration will not be saved and, if available, the previous, valid configuration will be continued to be used.
To apply one or more rewriters, they must be listed in the new request parameter rewriters, for example:
q=notebook&defType=querqy&rewriters=replace,commonrules1,wordbreak
Rewriters are applied in the order of their occurrence in the parameter value. This means that the old rewrite chain - that was set at the query parser in solrconfig.xml - is now replaced by this parameter, which is much more flexible as it can be set per request. It will probably reduce the configuration size in solrconfig.xml, especially in multi-tenancy setups.
As this change makes breaking changes to the configuration anyway, I've renamed a number of classes and packages that are exposed to the Querqy user. I've also removed classes that we don't really support (like the Lucene AnalysisQueryParser). The most important refactorings include:

rename querqy.solr.contrib to querqy.solr.rewriter - all 'contribs' are rewriters and we fully support them
create a sub-package per rewriter under querqy.solr.rewriter if a rewriter has more than one class
get rid of names starting with 'Default...' or 'Simple...' - we are using just one implementation of the corresponding component anyway.

Given that this issue involves many breaking changes in the configuration, I suggest that we increase the major version number of querqy-for-lucene (to v5).
Notes on implementation
The core component is querqy.solr.QuerqyRewriterRequestHandler. It exposes rewriter management via HTTP and via the internal RequestHandler name.
The QuerqyDismaxQParserPlugin and the TermQueryCachePreloader Solr event listener both access rewriters via the RequestHandler. The RequestHandler is loaded before the QParserPlugin and the Solr event listener. When it is loading, it checks the configset in ZK or the conf folder in standalone Solr for rewriter configurations and loads the rewriter factories as they are defined in these configurations.
The loading and caching of rewriter factories is encapsulated in the RewriterContainer. The rewriter container also implements methods for saving and deleting rewriters. As this needs to be implemented differently for SolrCloud and standalone Solr, the RewriterContainer uses a template method approach with specific implementations for the two cases (ZkRewriterContainer vs StandaloneRewriterContainer) ZkRewriterContainer also implements ZK watchers so that rewriter configuration updates will be propagated to all nodes in the Solr cluster.
In the SolrCloud version, rewriter configurations are gzipped for storage in ZK. (TODO: automatically split files > 1 MB to avoid hitting the ZK default size limit).
TODO: I've tried to keep the QuerqyRewriterRequestHandler a zero-config component. Maybe this is not necessary - I don't know enough yet about how well configuring the request handler will work using the new plugin API and the v2 API plugin capabilities. If it's easy to configure, we could think about managing (or just updating) the term query cache (https://docs.querqy.org/querqy/solr-plugin-configuration.html#term-query-cache) ourselves from within the QuerqyRewriterRequestHandler (or the RewriterContainer) instead of relying on a separately configured SolrEventListener (the TermQueryCachePreloader). We would simply register the QuerqyRewriterRequestHandler as a Solr event listener and reload the term query cache when the event fires - however, the RequestHandler configuration would need to tell us so.
As already mentioned, the configuration looks very similar between Solr and ES, including the configuration validation method of the rewriter factories. We could think of providing a single implementation for the two cases but I'm hesitant to tie the two together too much.
I've started creating rewriter configuration request builders (RewriterConfigRequestBuilder, querqy.solr.rewriter.commonrules.CommonRulesConfigRequestBuilder, querqy.solr.rewriter.replace.ReplaceConfigRequestBuilder). They allow to set configuration properties using a 'meaningful' object model and also allow to read in resources from an input stream (for example, to recycle the old rules.txt files). I've started this more or less to make it easier for me to write tests but we might want to extend this to a nice configuration client support, including methods for building SYNONYM rules etc. for the CommonRulesRewriter.

As of a discussion with @JohannesDaniel: to facilitate the cold start, there should be a toggle that controls the handling of rewriters that are specified in request url parameter rewriters= but that are missing in the configuration. If that toggle is on, missing rewriters will be skipped and an error message will be logged. If the toggle is off, a 'bad request' error will be returned. The default should be 'off'.

Just added the request handler to get all rewriters as a pull request (https://github.com/querqy/querqy/pull/132).
A very helpful curl to add a rewriter at the current stage was:
curl --request POST 'http://localhost:8983/solr/CORE/querqy/rewriter/commonrules1?action=save' \
--data-raw '{
    "class": "querqy.solr.rewriter.commonrules.CommonRulesRewriterFactory",
    "config": {
        "rules" : "notebook =>\nSYNONYM: laptop"
    }
}'

Just added the request handler to get all rewriters as a pull request (https://github.com/querqy/querqy/pull/132).
A very helpful curl to add a rewriter at the current stage was:
curl --request POST 'http://localhost:8983/solr/CORE/querqy/rewriter/commonrules1?action=save' \
--data-raw '{
    "class": "querqy.solr.rewriter.commonrules.CommonRulesRewriterFactory",
    "config": {
        "rules" : "notebook =>\nSYNONYM: laptop"
    }
}'

The Solr testing framework can decide to have no live nodes in the cloud client -> I changed our tests to use HttpClients. I also made sure the rewriter cleanup after tests waits until the deletes have been propagated to the nodes. a67202c

The Solr testing framework can decide to have no live nodes in the cloud client -> I changed our tests to use HttpClients. I also made sure the rewriter cleanup after tests waits until the deletes have been propagated to the nodes. a67202c

Implemented and merged (PR #155)


Absolute image paths are overwritten

Problem
I've got an issue with absolute image paths. Images with an absolute path (e.g. /im/test.png) are turned into (.//im/test.png), which results in errors because the path is invalid and images cannot be found.
Cause
The error caused by these lines of urls.py:
https://github.com/timvink/mkdocs-print-site-plugin/blob/95f3b88fdafc679e84a7e6dc1bab1796bc7fb819/mkdocs_print_site_plugin/urls.py#L195-L196
Proposed Fix
Replace
new_url = '../' + new_url
with
new_url = os.path.join('../', new_url)
to prevent absolute paths from being overwritten.

Should be addressed in v1.0. Let me know if it's fixed for you.

Fixed! Thank you

Fixed! Thank you


44 consolidate input components to input set

still missing hook for overriding styles
still missing dropdown component

missing functionalities are still in progress and are not yet ready to be merged in, will work in a separate branch for those

thanks @mariatorrentedev apologies wasnt able to make progress much during the weekdays, currently addressing your comments. Will create a new commit with all the context of overriding styles as well. Hopefully this week I get to finish everything

addressed comments and wired all form styleable components with the withStylesWrapper


Ask for confirmation before taking action in job summary

This is related to #816, putting a confirmation dialog before running/stopping/deleting jobs seems like a good idea. Not using any fancy react libraries just good ol' javascript.
I am not specially sure about 7cfe1f3900 but it seems to work just fine, I believe it to be a typo because the function definition for deleteJob() in ln181 expects an event.

The travis failure seems unrelated to my change, as far as I can see?

Seems this repo has been abandoned.


gh-950 use Set instead of List in proxy descriptors

On Windows, it happens that proxy-config.json is generated with "repeated interface" when building native docker images (spring-boot:build-image with <BP_NATIVE_IMAGE>true</BP_NATIVE_IMAGE>)
Has spotted by @arielcarrera, this happens when a class is annotated with two annotations that require a proxy like @Validated and @ConfigurationProperties (in my case, it was a @Controller annotated with @RestController, @RequiredArgsConstructor and @PreAuthorize).
As I haven't unerstood the value of ordered collections inside proxy descriptors, I propose here to replace List by Set for private members and Collection in methods signatures.
This should fix https://github.com/spring-projects-experimental/spring-native/issues/950

Sorted collection must be used


[Bug]: Unable to import application due to missing binding path primaryColumns._class.computedValue

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When a user tries to import an application, the operation fails due to a missing binding path.
The binding path in question is - primaryColumns._class.computedValue
Actual Error:
com.appsmith.server.exceptions.AppsmithException: Unable to import application in workspace xxx. Error: "widgetType" : "xxx", "bindingPath" : "primaryColumns._class.computedValue", "currentKey" : "_class", "message" : "Binding path in the widget not found. Please reach out to Appsmith customer support to resolve this.

Steps To Reproduce

Eport an app
Import an app with the JSON
Import fails

Public Sample App
No response
Environment
Production
Severity
Low (Inconsistent UI/UX)
Issue video log
No response
Version
Cloud

Closing this as it does not have an appropriate label associated with a pod

Seems like a duplicate of https://github.com/appsmithorg/appsmith/issues/20744


feat(page): add drag and press function in mobile mode

What kind of change does this PR introduce?
Add drag and press function in mobile mode
Did you add tests for your changes?
Yes
If relevant, did you update the documentation?
Yes

there is no press and drag function in Touchscreen class, so user can only use tap in mobile
Does this PR introduce a breaking change?
No
Other information

It looks like a documentation update is still missing?

recently I can't push on my computer, it said my esbuild have some problem,@OrKoN did I miss something?
error:https://i.imgur.com/oeRaipB.png

looks like it fail on firefox mode, but I also saw 'should tap the button' and 'should report touches' failed, that's weird,
anything I doing wrong? or still need somthing? @OrKoN

@OrKoN Hello,should I change the drag function to touch move?
Is there still some code I need to change in my pull request?


Provide download for checksum of go releases.

On the (official) download page for releases, https://go.dev/dl/ links are provided for source an binary releases and for each release/platform size, checksum and some more info. The checksum is provided as text on the page, but i can not find a download link for it.
Our use case is regular and automatic update of developer installations with the latest version. The developer are behind a corporate firewall and we provide an intern repository that is updated by automatic processes and also manually.
We watch the website (using renovate) for update and download can download the new version automatically. But we would like to verify the download using the provided checksum as well (or by using a signed file or any other means). Screenscraping the checksum is possible but a bit cumbersome and often brittle.
I found related issues from 2016 (closed): github golang 14385 and golang.org 19783. From the discussion in these issues i found that it is possible to download, for example, the current linux binary and its checksum from

https://storage.googleapis.com/golang/go1.22.5.linux-amd64.tar.gz
https://storage.googleapis.com/golang/go1.22.5.linux-amd64.tar.gz.sha256

But since https://go.dev/dl/  is the official download site it would be, in some way, cleaner to be able to download the file with the sha256 checksum from there. For example the textual entry of the checksum in the table could be changed to be a link for the file (or just provide the link - who ever wants to see the checksum could just click on it ...).
May be am i missing some better ways to verify the download automatically  (beside checking the TLS cert of https://go.dev) ? In this case i would appreciate some pointers to those. Thank you.

Related Issues

Make .sha256 checksum files available at https://golang.org/dl #41172 (closed)
x/website/internal/dl: serve .sha256 checksum files by redirecting to https://dl.google.com/go #41894
x/website: #57143 (closed)
release: provide sha256 checksums in machine readable format #14385 (closed)
golang.org: suggestion for Go versions URL to enable automated downloads #25271 (closed)
x/website: link to signatures on Go releases and document how to validate #38910
dl: add go1.2.2, go1.3.3 and go1.4.3 #45608
website: use sha256 on download page #12057 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

Thank you very much - the first issue (https://github.com/golang/go/issues/41172) in the list of related issues provides a nice solution for my use case. So I close the ticket.

The json (https://go.dev/dl/?mode=json) download with link and checksum solves my problem. Thank you.


Cannot read property 'state of undefined

Recently some of my wiz bulbs have stopped responding. Here is the console output:
This plugin threw an error from the characteristic 'Color Temperature': Unhandled error thrown inside write handler for characteristic: Cannot read property 'state' of undefined. See https://git.io/JtMGR for more info.
[5/10/2021, 09:14:32] [homebridge-wiz-lan] TypeError: Cannot read property 'state' of undefined
    at Object.setPilot (/usr/local/lib/node_modules/homebridge-wiz-lan/src/accessories/WizBulb/pilot.ts:140:21)
    at Characteristic.<anonymous> (/usr/local/lib/node_modules/homebridge-wiz-lan/src/accessories/WizBulb/characteristics/temperature.ts:39:9)
    at Characteristic.emit (events.js:327:22)
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1632:16
    at new Promise (<anonymous>)
    at Characteristic.<anonymous> (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1630:14)
    at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
    at Object.next (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:124:57)
    at /usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:117:75
    at new Promise (<anonymous>)

No changes on my end. 2 of my 3 wiz bulbs have stopped responding

Thanks for the suggestions. I'll give that a try.

@Dadbo Were you able to fix the issue? I tried @MoTechnicalities's suggestions and added my device reserved ip directly in the config and made Wiz a child hub but I'm still getting the same error

Just chiming in to let you know my setup is still working great, using HomeBridge. But also, be sure to check that everything is up to date regarding your Node.js and Npm versions.

Working fine for me also now, @Dadbo  I followed the following steps in case you are still facing issues:

Ensure everything is updated including wiz plugin and homebridge.
Added bulbs manually with their reserved IPs
Ran Wiz as a child Hub
Removed Wiz Platform and re-added the complete config in homebridge.
Added wiz child hub again in homekit.

Everything is working perfectly fine after this. Thanks @MoTechnicalities :)


Adding dependabot.yml file

We need to add dependabot.yml file as it helps us to keep our dependencies up to date. Every day, it checks your dependency files for outdated requirements and opens individual PRs for any it finds.
@Abhirup-02 please assign me this issue under gssoc'23.

There are some major version changes in some of the dependencies, which doesn't support the previous version functions......so we have to go through the whole project to change them.
So right now I am thinking to not add the bot. Thanks


[Container app] Release version 0.3.51

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

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[ ] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Container app

Hi @zhoxing-ms @yanzhudd
Can you help to review and merge this PR? Thanks!


COM-486: add javascript and data filter to isLinkTarget validation function

Description
This PR adds a filter for javascript and data in the isLinkTarget function and decorator to prevent XSS attacks.

I know this is a bit out of scope, but could you please rename the files to the new name? This was forgotten in #1671.

Also, please add a changeset.

Also, please add a changeset.

Sure. What should be the content of that?

Also, please add a changeset.

Sure. What should be the content of that?

IMO it should be a patch. Maybe something like:
Prevent XSS attacks in `isLinkTarget` validator

@johnnyomair should isLinkTarget be exported in the index file?


Third-party restrictions

See Req. 6.3.

This is essentially done, however point: Req. 6.3.a.ii might not be.
Any thoughts, @jeongoks


Adding toaster, dynamically checking pewpewVersion

I just had a realization. These changes don't need to be in master since master doesn't have the 0.6.x vs 0.5.x split. These changes really are only needed in the scripting branch. We can put them in master, but they aren't needed in master. @bryan-e-lopez What do you want to do? Do you still want these in master or should we move these code changes to a PR on the 0.6.0-scripting-dev branch? I can help you with changing it if you like.

@bryan-e-lopez Run npm run lint to find and fix the issues you're having. You also may need to merge master into this branch since you're out of date with master now.


TSC Meeting 2024-03-21

Please respond to this issue with items you would like to see added to the agenda.
Items from attendees of TSC Meetings are prioritized above others, though ad-hoc reprioritization and discussion will occur.
Current agenda below:

ASWF

A lot of nice contribution in the docs and the code!
Plan for next release?
Progress on TAC's yearly review. We are scheduled for mid-April.

https://github.com/AcademySoftwareFoundation/rez/pull/1684

@isohedronpipeline wants to talk about his pull request.

Can we talk about #1668? Curious about where we are on that.

Sure! I added it to the agenda.

I've put together a document to describe some of the motivation for 1684 here:
https://docs.google.com/document/d/1zy3ydSpHWgvatFS--L2PK7AwwOaowr1sdI9B_2eNtFc/edit?usp=sharing


163 basicblind completion for kamel groovy

Pull Request informations
Rebase & Merge default requirements

Green build for master branch
Wait 24 hours after PR creation
Green job for PR
Approved PR

PR labels default process

READY_FOR_REVIEW  →  REVIEW_DONE  →  READY_FOR_MERGE

Tests

[ ] Are there Unit tests?
[ ] Are there Integration tests?
[ ] Do we need a new UI test?

PR workflow progress

[ ] Tagged with relevant PR labels
[ ] Green job for PR
[ ] PR was created more than 24 hours ago or All committers approved it
[ ] Green master branch build

My vote is for the file extension hack vs. something inside a file, as that doesn't change the file contents. Adding a one-line marker that essentially says "hey, this is for camel-k" is not very useful to the user who already knows the file is meant for camel-k. That said, a comment in the file is more explicit than the file extension.
I would go with the file extension if the Camel-K team is ok with it but we need to be on the same page.

discussed in call with Brian:

currently there is no priority on this task (completion on Camel-K files), so we would like to avoid to spend too much time for a first iteration (we already spent more times asking what to do and then discussing it than it took to implement it)
there is no plan to have mandatory modeline or shebang (or file extension) in future.
the current PR is letting users choose the way they want, they can use both (extension or modeline-like). Everything stays open for the future.
the modification is almost non-intrusive, there are very low chance that someone using a *.camelk.groovy file with a from/to method inside and having Camel extension installed is writing a file which is not a Camel-K file

given all of that we are thinking that we should merge to allow people play with it and if it comes with higher priority, we can rediscuss and rework it


A way to distinguish & iterate over an array-table?

So, first of all: Sol is awesome. Amazing job.
 I looked at this reference but I'd like to do it using native Sol APIs. The obj.is<vector<sol::object>>-esque stuff does not seem to work for this case. What approach should I use?
json encodeValue(const sol::object& val) {
    if (val.is<sol::string_view>()) {
        return val.as<sol::string_view>();
    } else if (val.is<int>()) {
        return val.as<int>();
    } else if (/* magical way to decide it's an array */) {
        auto arr = json::array();
        // fill arr with elements...
        return arr;
    } else if (val.is<sol::table>()) {
        return encodeTable(val.as<sol::table>());
    }

    return nullptr;
}

json encodeTable(const sol::table& table) {
    json out;

    for (auto& e : table) {
        auto key = e.first;
        auto encoded = encodeValue(e.second);

        if (key.is<sol::string_view>()) {
            out[key.as<sol::string_view>().data()] = encoded;
        } else if (key.is<int>()) {
            out[key.as<int>()] = encoded;
        }
    }

    return out;
}

Lua itself does not distinguish between "arrays" and "dictionaries". They are all tables. As such, there is no easy way to distinguish between them. Most approaches I've seen simply check if the keys start with "1" and are sequential with no gaps and if so they assume it's an array and otherwise they treat it as a dictionary.

It's as @OrfeasZ says: Lua has no way to accurately determine whether something is an array vs. a table without a potentially expensive check.
Them's just the breaks; sorry. A lot of requests for array functionality have been lobbied at Lua developers but they feel it is not worth the add. Not much I can do without actually forking the Lua language itself.


Fix package method error

This PR fixes the wrong method included in #77, some spelling mistake, and changed test package id.

Ha! Good catch on the typos. Unit tests are currently broken. I'm working on fixing; but I'm happy with this as is. :) thank you


Update SierraSource.lookupItemEntries to request more fields

In order to ensure that we have consistent item data for Sierra items between the items API and the search API we need to make sure the same data is sourced from Sierra in both cases.
This change adds the "status" and "varFields" fields to those requested when we look up item data directly from the sierra API.
This change resolves an issue where we were not seeing notes fields on items from the Items API (https://github.com/wellcomecollection/platform/issues/5305)

This looks fine, although I wonder if we'd be better off making the list of fields a parameter you pass in, so we can change it up as we need?

I think this makes sense and this change can function as a step on the way. We might want to create an ADT around the params, rather than allowing strings to be handed through.


Restart of daily production

Hi!
I'm having troubles with my statistics because the daily production counter restarts when the sun goes away and comes back. Mostly happens in the evening but also on very cloudy days. This causes further calculations that depend on that sensor to jump around. I would suggest to fix this by adding up the values of the inverter and reset only once at midnight. What do you think?
As previously, I can also suggest a fix (PR) if you want me to.
See the issue here:

Thanks for the offer, but I want this repo to get merged into HomeAssistant Core, so please don't open the PR here, but the PR is stuck at the moment, so I don't have a clue when this will get merged. You can check the PR here: https://github.com/home-assistant/core/pull/114531

Ok understood, I'll do some local fixes and hope for the best for your PR :crossed_fingers:. Ping me if you want me to provide the fixes.

Once it's merged, you can submit the fixes directly to HA. But I'm not sure the PR will ever get merged.

But I'm not sure the PR will ever get merged.

I had a look at the code, are you sure that all prerequisites like the coding style are fulfilled? I had a quick look and my linters (ruff, pylint) show a number of issues.

Will check that. Could be that the merges have messed sth up. It's been some weeks since I've checked everything.

I've now fixed a new linter warning. The rules has been enabled in the last few weeks. Everything passes now.


feat(obstacle_cruise_planner): add a hold stop distance feature (#4720)

Description
obstacle stop時に、前方の物体の形状が縦方向に0.3m変わったとしても再発進しないように
https://tier4.atlassian.net/browse/RT0-28929

Tests performed

Not applicable.
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

不備がある可能性があるので一旦PR閉じます


[WIP] Add codecov to the github actions

Secure Coding Practices Checklist GitHub Link

https://github.com/RedHatInsights/secure-coding-checklist

Secure Coding Checklist

[x] Input Validation
[x] Output Encoding
[x] Authentication and Password Management
[x] Session Management
[x] Access Control
[x] Cryptographic Practices
[x] Error Handling and Logging
[x] Data Protection
[x] Communication Security
[x] System Configuration
[x] Database Security
[x] File Management
[x] Memory Management
[x] General Coding Practices

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@993217f). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #31   +/-   ##
=========================================
  Coverage          ?   49.68%
=========================================
  Files             ?        7
  Lines             ?      483
  Branches          ?        0
=========================================
  Hits              ?      240
  Misses            ?      228
  Partials          ?       15

Flag
Coverage Δ

unittests
49.68% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Indefinitely "Discovering Python Interpreters"

Type: Bug

Behaviour
Expected vs. Actual
When i open a python project the language server never loads. It just stalls on "discovering python interpreters" forever.
In the output section i've put just one example of the errors ms-python is outputting. All the other errors are copies of the ones there but with different environment names and python versions.
It looks like it's searching for my old, deleted virtualenvs. I don't know where it's saving its information about those old envs or i'd delete that.
Steps to reproduce:

Open a python project with vscode-remote on my machine?

I'm sure it's something weird about my setup but i can't pin it down. I've reinstalled vscode, vscode-server, all extensions, ect.

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.11.2
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): PipEnv
Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

2023-09-21 14:16:59.993 [warning] Identifier for virt-virtualenv failed to identify /home/ablacklama/.virtualenvs/pyx_analysis-3.9/bin/python [Error: ENOENT: no such file or directory, scandir '/home/ablacklama/.virtualenvs/pyx_analysis-3.9/bin'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'scandir',
  path: '/home/ablacklama/.virtualenvs/pyx_analysis-3.9/bin'
}
2023-09-21 14:17:04.010 [error] Error: Command failed: /home/ablacklama/.virtualenvs/pyx_analysis-3.9/bin/python -I /home/ablacklama/.vscode-server/extensions/ms-python.python-2023.16.0/pythonFiles/get_output_via_markers.py /home/ablacklama/.vscode-server/extensions/ms-python.python-2023.16.0/pythonFiles/interpreterInfo.py
/bin/sh: 1: /home/ablacklama/.virtualenvs/pyx_analysis-3.9/bin/python: not found

    at ChildProcess.exithandler (node:child_process:420:12)
    at ChildProcess.emit (node:events:513:28)
    at ChildProcess.emit (node:domain:489:12)
    at maybeClose (node:internal/child_process:1091:16)
    at Socket.<anonymous> (node:internal/child_process:449:11)
    at Socket.emit (node:events:513:28)
    at Socket.emit (node:domain:489:12)
    at Pipe.<anonymous> (node:net:322:12) {
  code: 127,
  killed: false,
  signal: null,
  cmd: '/home/ablacklama/.virtualenvs/pyx_analysis-3.9/bin/python -I /home/ablacklama/.vscode-server/extensions/ms-python.python-2023.16.0/pythonFiles/get_output_via_markers.py /home/ablacklama/.vscode-server/extensions/ms-python.python-2023.16.0/pythonFiles/interpreterInfo.py'
}

User Settings

languageServer: "Pylance"

formatting
• provider: "none"
• blackArgs: "<placeholder>"

testing
• promptToConfigure: false
• pytestArgs: "<placeholder>"
• pytestEnabled: true

Extension version: 2023.16.0
VS Code version: Code 1.82.2 (abd2f3db4bdb28f9e95536dfa84d8479f1eb312d, 2023-09-14T05:55:25.390Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Remote OS version: Linux x64 5.15.0-83-generic

System Info

Item
Value

CPUs
AMD Ryzen 9 5900X 12-Core Processor             (24 x 3700)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
31.94GB (12.57GB free)

Process Argv
--crash-reporter-id 0e2b899c-1a5d-43cb-be1d-1dada59d9714

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: cahserver

OS
Linux x64 5.15.0-83-generic

CPUs
AMD Ryzen Threadripper 3970X 32-Core Processor (64 x 3997)

Memory (System)
251.54GB (242.35GB free)

VM
0%

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263cf:30792227
vscaac:30438847
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
3biah626:30602489
89544117:30613380
showlangstatbar:30737416
03d35959:30757346
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
copilotsettingc:30839828
synctok:30821570
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30821572
dsvsc015cf:30829746
pythonfb280951cf:30830811

Try out the pre-release version of the extension:

You may need to clear cache using Python: Clear cache and reload command.

You may need to clear cache using Python: Clear cache and reload command.

switching to pre-release didn't do anything. Clearing cache got rid of all the environment failures. Now I'm left with this set of warnings/errors that were probably the true cause all along.
2023-09-21 16:20:08.342 [warning] Retry failed, storage update failed for key PYTHON_GLOBAL_STORAGE_KEYS
2023-09-21 16:20:08.342 [warning] Retry failed, storage update failed for key PYTHON_GLOBAL_STORAGE_KEYS
2023-09-21 16:20:08.342 [warning] Retry failed, storage update failed for key PYTHON_GLOBAL_STORAGE_KEYS
2023-09-21 16:20:08.342 [warning] Retry failed, storage update failed for key PYTHON_GLOBAL_STORAGE_KEYS
2023-09-21 16:20:08.343 [warning] Retry failed, storage update failed for key PYTHON_WORKSPACE_STORAGE_KEYS
2023-09-21 16:20:08.343 [warning] Retry failed, storage update failed for key PYTHON_WORKSPACE_STORAGE_KEYS
2023-09-21 16:20:08.343 [warning] Retry failed, storage update failed for key PYTHON_WORKSPACE_STORAGE_KEYS
2023-09-21 16:20:54.231 [error] Autoselection timeout out, this is likely a issue with how consumer called execution factory API. Using default python to execute.
2023-09-21 16:20:54.274 [info] > python -c "import sys;print(sys.executable)"
2023-09-21 16:20:54.359 [info] Python interpreter path: ~/.pyenv/versions/3.10.5/bin/python
2023-09-21 16:20:56.423 [error] Autoselection timeout out, this is likely a issue with how consumer called execution factory API. Using default python to execute.
2023-09-21 16:20:56.430 [error] Autoselection timeout out, this is likely a issue with how consumer called execution factory API. Using default python to execute.
2023-09-21 16:20:56.873 [error] Autoselection timeout out, this is likely a issue with how consumer called execution factory API. Using default python to execute.

When i open a python project the language server never loads

The intention of pre-release was to help with this. We just made a fix to ensure Interpreter discovery to not block LS: https://github.com/microsoft/vscode-python/pull/22041, so even if Discovery does not finish, LS should ideally start, as long as you see an active interpreter on the bottom right:

Can you confirm whether you see it? Your log seems to indicate: Python interpreter path: ~/.pyenv/versions/3.10.5/bin/python, which suggests you do.

it waits for about a full minute (where i don't see an active interpreter) then selects an interpreter.
However, code completion is broken even after an active interpreter is selected.

Oh and I made a mistake when i said clearing the cache fixed the environment errors. They just took longer to show up after clearing the cache. It's still throwing errors while looking for the same deleted environments.

I'll also remind you that i'm using vscode remote ssh'd into an ubuntu box. Since that has often been a factor in previous issues i've had.

Oh i seem to have fixed code completion for now. I opened vscode without being ssh'd into the linux box and cleared the cache. That seems to have worked. I almost never open vscode without using vscode-remote so i hadn't tried that.
Now it's just stuck on "Refreshing Python Interpreters" but at least I can ignore that and still work effectively.

Great, now we can work on making that go away. For that I would need the complete debug logs:

Run Developer: Set log level command
Select Python -> Select Trace
Run Developer: Reload Window command
Provide the output:

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

It's still throwing errors while looking for the same deleted environments.

It's likely that other extensions like Jupyter are still looking for those deleted environments, in which you can try disabling the extension. The logs should contain this info as well.

Everytime i set the python log level to trace it goes back to being info when I reload the window.

I see, try setting it at VS Code level then:

I can't post some of the logs here since they contain private info. But here's the end of it. It prints that last line over and over indefinitely.
2023-09-21 17:18:13.365 [debug] Found interpreter for >> /home/ablacklama/.virtualenvs/random_analysis-3.11/bin/python -I /home/ablacklama/.vscode-server/extensions/ms-python.python-2023.17.12642044/pythonFiles/get_output_via_markers.py /home/ablacklama/.vscode-server/extensions/ms-python.python-2023.17.12642044/pythonFiles/interpreterInfo.py <<: {"versionInfo":[3,11,2,"final",0],"sysPrefix":"/home/ablacklama/.virtualenvs/random_analysis-3.11","sysVersion":"3.11.2 (main, Feb 21 2023, 18:01:51) [GCC 11.3.0]","is64Bit":true}
2023-09-21 17:18:13.366 [debug] Python API env change detected /home/ablacklama/.virtualenvs/random_analysis-3.11/bin/python update
2023-09-21 17:18:13.366 [debug] Clearing context for python dependencies not installed: undefined
2023-09-21 17:18:13.385 [debug] Found interpreter for >> /bin/python3 -I /home/ablacklama/.vscode-server/extensions/ms-python.python-2023.17.12642044/pythonFiles/get_output_via_markers.py /home/ablacklama/.vscode-server/extensions/ms-python.python-2023.17.12642044/pythonFiles/interpreterInfo.py <<: {"versionInfo":[3,10,12,"final",0],"sysPrefix":"/usr","sysVersion":"3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0]","is64Bit":true}
2023-09-21 17:18:13.386 [debug] Python API env change detected /bin/python3 update
2023-09-21 17:18:13.410 [debug] Python API env change detected /usr/bin/python3 add
2023-09-21 17:18:13.446 [info] > /usr/bin/python3 -I ~/.vscode-server/extensions/ms-python.python-2023.17.12642044/pythonFiles/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2023.17.12642044/pythonFiles/interpreterInfo.py
2023-09-21 17:18:13.447 [debug] Shell Exec: /usr/bin/python3 -I /home/ablacklama/.vscode-server/extensions/ms-python.python-2023.17.12642044/pythonFiles/get_output_via_markers.py /home/ablacklama/.vscode-server/extensions/ms-python.python-2023.17.12642044/pythonFiles/interpreterInfo.py with options: {
<i hid these since they had env var secrets>
}
2023-09-21 17:18:13.447 [debug] Clearing context for python dependencies not installed: undefined
2023-09-21 17:18:13.474 [debug] Found interpreter for >> /usr/bin/python3 -I /home/ablacklama/.vscode-server/extensions/ms-python.python-2023.17.12642044/pythonFiles/get_output_via_markers.py /home/ablacklama/.vscode-server/extensions/ms-python.python-2023.17.12642044/pythonFiles/interpreterInfo.py <<: {"versionInfo":[3,10,12,"final",0],"sysPrefix":"/usr","sysVersion":"3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0]","is64Bit":true}
2023-09-21 17:18:13.474 [debug] Python API env change detected /usr/bin/python3 update
2023-09-21 17:18:13.477 [debug] Finished searching for workspace virtual envs
2023-09-21 17:18:13.855 [debug] Clearing context for python dependencies not installed: undefined
2023-09-21 17:18:14.237 [debug] Clearing context for python dependencies not installed: undefined
2023-09-21 17:18:14.301 [debug] Clearing context for python dependencies not installed: undefined
2023-09-21 17:18:14.814 [debug] Clearing context for python dependencies not installed: undefined
2023-09-21 17:18:15.360 [debug] Clearing context for python dependencies not installed: undefined
2023-09-21 17:18:15.939 [debug] Cached data exists KeyPrefix=Cache_Method_Output_b._selectIfLaunchedViaActivatedEnv-Args=true
2023-09-21 17:18:15.939 [debug] Clearing context for python dependencies not installed: ms-python.python.Python
2023-09-21 17:18:15.939 [debug] Cached data exists KeyPrefix=Cache_Method_Output_b._selectIfLaunchedViaActivatedEnv-Args=false
2023-09-21 17:18:15.942 [debug] Cached data exists KeyPrefix=Cache_Method_Output_f.addKeyToStorage-Args="global"-Arg-Separator-"ssh-remote_WORKSPACE_FOLDER_INTERPRETER_PATH_/mnt/storage/programming/the_lab"-Arg-Separator-undefined
2023-09-21 17:18:15.942 [debug] Cached data exists KeyPrefix=Cache_Method_Output_f.addKeyToStorage-Args="global"-Arg-Separator-"ssh-remote_WORKSPACE_FOLDER_INTERPRETER_PATH_/mnt/storage/programming/the_lab"-Arg-Separator-undefined
2023-09-21 17:18:16.126 [debug] Clearing context for python dependencies not installed: ms-python.python.Python
2023-09-21 17:18:16.219 [debug] Clearing context for python dependencies not installed: ms-python.python.Python
2023-09-21 17:18:16.417 [debug] Clearing context for python dependencies not installed: ms-python.python.Python
2023-09-21 17:18:16.842 [debug] Clearing context for python dependencies not installed: ms-python.python.Python
2023-09-21 17:18:17.000 [debug] Clearing context for python dependencies not installed: ms-python.python.Python
2023-09-21 17:18:17.087 [debug] Clearing context for python dependencies not installed: ms-python.python.Python
2023-09-21 17:18:17.192 [debug] Clearing context for python dependencies not installed: ms-python.python.Python
2023-09-21 17:18:17.298 [debug] Clearing context for python dependencies not installed: ms-python.python.Python
2023-09-21 17:18:17.378 [debug] Clearing context for python dependencies not installed: ms-python.python.Python

Unfortunately this doesn't help, I would need the full logs. If you can provide an email we can privately share this there.

<EMAIL_ADDRESS>

Update: It keeps breaking in the same way and i keep having to use a non vscode-remote ssh'd window to clear the python cache in order to make code completion work for a few hours.

While I know it's not ideal, if you install conda on your Remote Linux machine, it can make the issue go away:
mkdir -p ~/miniconda3
wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh -O ~/miniconda3/miniconda.sh
bash ~/miniconda3/miniconda.sh -b -u -p ~/miniconda3
rm -rf ~/miniconda3/miniconda.sh
~/miniconda3/bin/conda init bash
~/miniconda3/bin/conda init zsh

Oh that looks like it worked! I just deleted the miniconda3 folder entirely since i wasn't using it and it's no longer stuck on discovering interpreters. Thanks a lot!
As a side note it still looks for old environments that don't exist, but at least that's not causing any issues on my side. Just some errors in the logs.

Awesome. Happy to help unblock you.
In the logs you sent me I don't see any, but let us know if that causes any trouble in the future.

By any chance do you know if ~/miniconda3/bin/conda actually existed in your system prior to the delete?

Yes ~/miniconda3/bin/conda did exist. Out of curiosity I tried calling ~/miniconda3/bin/conda info --json it manually and it just hung and never returned.

I have likewise had this stop working for me recently. I found my way here via Storage update failed for key PYTHON_GLOBAL_STORAGE_KEYS  retrying by resetting first.
I have a message of this form (<hash> removed):
2023-09-25 16:37:53.580 [error] Active interpreter type is detected as Unknown {"id":"/nix/store/<hash>-python3-3.11.3-env/bin/python","sysPrefix":"/nix/store/<hash>-python3-3.11.3-env","envType":"Unknown","envName":"","envPath":"","path":"/nix/store/<hash>-python3-3.11.3-env/bin/python","architecture":3,"sysVersion":"3.11.3 (main, Apr  4 2023, 22:36:41) [GCC 12.2.0]","version":{"raw":"3.11.3","major":3,"minor":11,"patch":3,"build":[],"prerelease":["final","0"]},"displayName":"Python 3.11.3 64-bit","detailedDisplayName":"Python 3.11.3 64-bit"}

The logs suggest that it is successfully invoking the python interpreter on ~/.vscode-server/extensions/ms-python.python-2023.16.0/pythonFiles/interpreterInfo.py, where it gets the output of the form:
>>>PYTHON-EXEC-OUTPUT
{"versionInfo": [3, 11, 3, "final", 0], "sysPrefix": "/nix/store/<hash>-python3-3.11.3-env", "sysVersion": "3.11.3 (main, Apr  4 2023, 22:36:41) [GCC 12.2.0]", "is64Bit": true}
<<<PYTHON-EXEC-OUTPUT

This was working as recently as last week.
Intriguingly, downgrading from v2023.9.20 to v2023.9.10 seems to have fixed the issue, in that completions start working if I do that, though I still have these errors showing on the python console.

Hm. I'm beginning to think my bug may different though it could be related. Could something have changed relating to symlink handling? The pylance logs indicate that it searches the relevant directory for a package being imported, but does not find it. In the older version of pylance, the directory is searched and the package is found. The package is symlinked into the directory which is in PYTHONPATH. Could the fact it is symlinked be relevant?

It appears the issue I described above is fixed on the pre-release pylance. Sorry for the noise.

No worries, and thanks for all the help 🙂 I've created a fix to bypass such problematic conda binaries on the system, ensuring discovery can complete even when they're present: https://github.com/microsoft/vscode-python/pull/22072.


Update Jinja2 dependency >= 3.1.0

Jinja2 <3.1 has reached end of support with the release of 3.1.0, so it may be a good time to update the dependency for new features and bugfixes.

Yes, good idea.


Update the spec test suite submodule

This commit updates the tests/testsuite submodule which is a copy of the spec tests from upstream and the various proposals repositories. The major change included here is the update to the lexing of the text format to allow "reserved" tokens to have string tokens embedded within them (in a sense). This doesn't affect any parsing in the crate, only the tokenization of the input.
Additionally there are a few minor updates to error messages plus an new exceptional case where the spec interpreter is printing "unknown global" for defined globals which I'm not really sure what's going on.

I've now additionally updated this to include the inclusion of relaxed-simd into the testsuite repo as well.

This seems to bump the minimum supported rust compiler; I'm now getting
#25 101.6   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/wast-47.0.0/src/names.rs:84:26
#25 101.6    |
#25 101.6 84 |         format!("unknown {ns}: failed to find name `${}`", id.name()),
#25 101.6    |                          ^^^^

in a dockerfile that had been working, so my little downstream project's unhappy now.
I guess I get to update it from alpine 2.15; I was about to anyway for other reasons.


Global attribute names for language

I know how to set custom attribute names for an instance of validator but I want to know is it possible to set them globally?  (i need something like below):
var validator = require('validatorjs');  validator.useLang('fa'); validator.setAttributes('fa',{     age: 'سن',     full_name: 'نام کامل',     ... });

Any progress on this issue?

Hi, I am not a library owner, so my opinion may be different and not committed to be the true one.
As I understand you need something like global .setAttributeNames. Here is what I think.
class Validator is responsible for creating a validator instance.  And as it is a constructor it defines the properties and methods for instance and holds some generic data. Class Validator does not interact with your form and knows nothing about your form fields(and about your form at all), but instance (validator) does.
Following your request, you are asking to break an encapsulation - in my opinion, this does not look good from the architectural point of view. The current implementation allows keeping some separation or responsibilities and roles.
What do you think?
Btw, @alisherafat can you help with one rule translation into Persian('fa') language? it is a "hex" rule https://github.com/skaterdav85/validatorjs/blob/master/src/lang/fa.js Can you reply me with translation here?

Hi @vict-shevchenko
Translation of hex rule for fa_IR is:
hex:  'فیلد :attribute باید در فرمت مبنای ۱۶ باشد'
As answered herer Laravel validator has option to modify attributeNames for a specific language globally and there is nothing wrong with that and is good thing to implement here.
actually attributes:{} property should be modifiable here

This has been tagged as a feature request and will consider this addition for a future release.

Cool! Glad to know this. Thanks a lot for translation.


Project/Company Custom File Page - When we try to clear all applied filter it does not work

Describe the bug

When we try to create customfile in project customfile and company customfile page and try some filter option to filter service then some filter like 'service' and 'is recurring' option filter is not clear when we click on clear all

https://www.berrycast.com/conversations/8ae4b3f7-eae3-561c-8fc4-c6a9e1791894

Here only Recurring Services are connected, so Removing Recurring filter should be disabled


[website] pick first line from package description

Currently we truncate the package description on the API overview page to 170 characters. It results with broken html syntax in several places.
The proposed solution is to pick the first line from the package description block rather than truncating the description block with an arbitrary character count.

Nice catch! Looks good!


Fix UI issues

This PR fixes some issues with the UI:
Context stays on deleted app on canvas
Unclear error when blueprint has space in name
No visual feedback when unauthorised user tries to change HS state

These have all been merged already.  PR can be closed.


[Feature]FlyteConsole LaunchForm should show show LaunchPlan Spec details

Motivation: Why do you think this is important?
LaunchPlan spec has many other details besides just Inputs. There is no way to browse all launch plans. We should be able to review other details of a launchplan - for e.g.

RAW path
labels
annotations
etc
Eventually user should be able to update them too for an execution

Goal: What should the final outcome look like, ideally?
Show in the UI details of a launchplan
Describe alternatives you've considered
FlyteCLI is the only option.
Flyte component

[ ] Overall
[ ] Flyte Setup and Installation scripts
[ ] Flyte Documentation
[ ] Flyte communication (slack/email etc)
[ ] FlytePropeller
[ ] FlyteIDL (Flyte specification language)
[ ] Flytekit (Python SDK)
[ ] FlyteAdmin (Control Plane service)
[ ] FlytePlugins
[ ] DataCatalog
[ ] FlyteStdlib (common libraries)
[x] FlyteConsole (UI)
[ ] Other

Additional context
It makes it extremely hard for users to understand their settings for a launchplan
Is this a blocker for you to adopt Flyte
NA

this is done, should be displayed under "Advanced Options"


[ENH,REF] Adds new region_agg parameter

Related to #125 (insomuch as it temporarily removes batch normalization as an option)
This adds the region_agg parameter (and renames metric to agg_metric) in the abagen.get_expression_data() function. This parameter controls how samples belonging to the same region are combined (i.e., [1] aggregated separately for each donor and then combined across donors or [2] aggregated across all donors simultaneously).
Also some minor updates to various typos and doc-strings throughout the package.
To Do:

[x] Update Donor normalization doc page to highlight sample_norm vs donor_norm differences
[ ] Add new doc page to highlight region_agg and agg_metric options
[ ] Ensure all documentation between abagen.get_expression_data() and abagen CLI is up-to-date
[ ] Add tests for new functions in abagen.samples
[ ] Add tests for new parameters to abagen.get_expression_data and abagen CLI

Codecov Report

Merging #131 into master will decrease coverage by 0.18%.
The diff coverage is 95.18%.

@@            Coverage Diff             @@
##           master     #131      +/-   ##
==========================================
- Coverage   90.14%   89.95%   -0.19%
==========================================
  Files          32       32
  Lines        1959     1962       +3
==========================================
- Hits         1766     1765       -1
- Misses        193      197       +4

Impacted Files
Coverage Δ

abagen/tests/test_correct.py
100% <ø> (ø)
:arrow_up:

abagen/correct.py
98.24% <100%> (-0.94%)
:arrow_down:

abagen/probes.py
97.27% <100%> (+0.21%)
:arrow_up:

abagen/cli/run.py
93.47% <100%> (+0.29%)
:arrow_up:

abagen/io.py
77.77% <100%> (ø)
:arrow_up:

abagen/allen.py
97.22% <100%> (-0.76%)
:arrow_down:

abagen/tests/cli/test_run.py
100% <100%> (ø)
:arrow_up:

abagen/samples.py
96.26% <87.09%> (-2.78%)
:arrow_down:

abagen/utils.py
93.38% <0%> (+0.82%)
:arrow_up:

Continue to review full report at Codecov.

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


Bottom Slider Added

Added "Sessions" bottom slider in start page
Fix for Issue #20

There's a few things that could be improved:

It's helpful to have an interactive preview so you can move it around and see how it works. Something like this:

when open, the bottom of the content should be in the same location as the bottom of the view. if you put in a test VStack with text and the top and bottom with a spacer you'll see the bottom text might get chopped off.
the bottom of the view should not have a corner radius
.animation() should only be used with "value" to limit the scope so that other changes in the UI don't trigger the same spring somewhere higher up in the view stack.
Setting a max height won't really work for variable device sizes. Really it should be set to move up to just under the top safe area when open and some minimum height at the bottom when closed.
you can remove "self" in a lot of cases here


Make redaction case insensitive and add messaging params

Fix https://github.com/evcc-io/evcc/issues/6036
@goebelmeier could you try this?

tried it, LGTM


New term - decimalCoordinates

Submitter: Ian Engelbrecht (Natural Science Collections Facility, South African National Biodiversity Institude, www.nscf.co.za)
Proponents (at least two independent parties who need this term): None, but see Justification below. We are using a term like this in our georeferencing workflows in the NSCF.
Justification (why is this term necessary?): Darwin Core includes terms verbatimCoordinates, verbatimLatitude and verbatimLongitude, and then decimalLatitude and decimalLongitude. The proposed decimalCoordinates is a convenience term for representing decimal coordinates in a single field. Systems such as the Google Maps API make use of coordinates in this format (a single string value with coordinates separated with a comma), and georeferencing workflows can be more efficient if we work with a single field (copying coordinates from QGIS for example, and it would be helpful if the Georeferencing Calculator provided coordinates as a single field).
Proposed definition of the new term: "The geographic coordinates as defined for decimalLatitude and decimalLongitude, but represented as a single concatenated string with the coordinates values separated by a comma. A convenience value intended to support mapping of records in particular systems such as Google Maps, and for efficient georeferencing workflows."
Term name (in lowerCamelCase): decimalCoordinates
Class (e.g. Location, Taxon): Location (although perhaps we should consider a new class for Georeference).
Comment (recommendations regarding content, etc.): "Tools such as the Google Maps API make use of concatenated coordinates, and georeferencing workflows can be expedited by only having to copy a single concatenated coordinate values from GIS or other tools into specimen databases".
Examples: "-23.24561,24.32146"
Refines (identifier of the broader term this term refines, if applicable): NA, but corresponds to verbatimCoordinates.
Replaces (identifier of the existing term that would be deprecated and replaced by this term, if applicable): NA
ABCD 2.06 (XPATH of the equivalent term in ABCD, if applicable): I have not checked.

Could DWC perhaps follow the Well-Known Text norm for encoding coordinates where the example above would be:
POINT(-23.24561,24.32146)
This would allow GDAL and other spatial libraries to decode these values unambiguously since coordinate reference system may also be included in the leteral vallue, e.g.
<http://www.opengis.net/def/crs/EPSG/0/4283> POINT(-23.24561,24.32146)
Use of WKT in this way could also be indicated better with a property of geometry rather than various xxxCoordinate properties. The CRS value can be used to distinguish reference systems.

What @nicholascar suggests is exactly what dwc:footprintWKT and dwc:footprintSRS are for. I would not recommend another term to accomplish the same thing.

Closing for lack of evidence of demand.


[Port] ToString() on CustomAttributeTypedArgument and CustomAttributeNamedArgument

System.Reflection.CustomAttributeNamedArgument::ToString()
System.Reflection.CustomAttributeTypedArgument::CustomAttributeTypedArgument.ToString()

On the surface, it looks like you could copy the CoreClr code directly over. The problem is that this algorithm invokes code that could throw MissingMetadataExceptions on NetNative. The cheap way out is to wrap the thing in a try-catch, but we generally prefer to write these things in an exception-avoiding style as not to trigger false-positive exceptions in the debugger.
Because these two types are structs, they may need to test if if the ArgumentType is runtime-implemented and thunk up to Reflection.Core for that part.

Diagnostics only - this can be deferred.

Done: https://github.com/dotnet/corert/pull/2684


Emit enums as union types instead of current string

Fixes #200
Current:
interface Request extends Object, Body {
    readonly cache: string;
    readonly credentials: string;
    readonly destination: string;
    readonly headers: Headers;
    readonly integrity: string;
    readonly keepalive: boolean;
    readonly method: string;
    readonly mode: string;
    readonly redirect: string;
    readonly referrer: string;
    readonly referrerPolicy: string;
    readonly type: string;
    readonly url: string;
    clone(): Request;
}

Fixed:
interface Request extends Object, Body {
    readonly cache: RequestCache;
    readonly credentials: RequestCredentials;
    readonly destination: RequestDestination;
    readonly headers: Headers;
    readonly integrity: string;
    readonly keepalive: boolean;
    readonly method: string;
    readonly mode: RequestMode;
    readonly redirect: RequestRedirect;
    readonly referrer: string;
    readonly referrerPolicy: ReferrerPolicy;
    readonly type: RequestType;
    readonly url: string;
    clone(): Request;
}

type ReferrerPolicy = "" | "no-referrer" | "no-referrer-when-downgrade" | "origin-only" | "origin-when-cross-origin" | "unsafe-url";
type RequestCache = "default" | "no-store" | "reload" | "no-cache" | "force-cache";
type RequestCredentials = "omit" | "same-origin" | "include";
type RequestDestination = "" | "document" | "sharedworker" | "subresource" | "unknown" | "worker";
type RequestMode = "navigate" | "same-origin" | "no-cors" | "cors";
type RequestRedirect = "follow" | "error" | "manual";
type RequestType = "" | "audio" | "font" | "image" | "script" | "style" | "track" | "video";

Will reopen after fixing build.

@zhengbli can you please review this change?

LGTM

Thanks @SaschaNaz !

We need to document this as a breaking change.


s3 ingester: refactor main loop to a worker pool

Closed by https://github.com/gravwell/gravwell/pull/884


[#1997] Fix some issues around fast-forward initiative rolls. Add support for preRollInitiative and rollInitiative hooks.

Some adjustments for things I missed in my initial review that came up in later testing such as missing fast-forward rolls and the advantage button not being highlighted in the roll dialog when 'advantage on initiative' was checked. Also adds rudimentary support for preRollInitiative and rollInitiative hooks.

Closes #1997

Fast-forwarding initiative rolls has been removed for now due to their relative permanence compared with other sheet rolls. I've moved the hooks into Actor5e#rollInitiative.


updated temp-write for workspace 3.14

Updated the dependency as it was giving warning in redwoodjs

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


This information is provided in the PDSC file through the  attributes and child elements.
Among the child elements, both the mountedDevice (the microcontroller device mounted on the development board) and the compatibleDevice (the compatible microcontroller devices) must have occurrence 1..*, meaning that at least one occurrence of both must be present.
This constraint doesn't allow to describe the development boards that do not have/require a microcontroller mounted on.
This is the case of the extension or expansion or daughter boards, which can be plugged through a connector (ARDUINO UNO, ST morpho, ...) on a mother board, equipped with an MCU, for expanding its features.
To allow the possibility to describe with the Open-CMSIS-Pack-Spec also these kind of boards, the /package/boards/board/mountedDevice and /package/boards/board/compatibleDevice elements should be optional, that is their occurrence should be set to 0..*.

As said, the advantage for the users is that they can describe with the standard a larger set of the development boards, in line with what they can already do for the <devices> and the <parts>.
In fact, like they can now create CMSIS packs for describing devices (MCUs) and parts (devices other than the MCUs), with this proposal they could create packs for describing both boards mounting MCUs + parts and boards mounting only parts.

I can see  where you are coming from, however I think we are weakening the schema if we make the mountedDevice and compatibleDevice optional. How about requiring a pre-defined value "NO_MCU"?

@jkrech do you mean that you want to prevent the pack developer from forgetting to think about the mounted device information and possibly miss the addition of the mountedDevice node?

@jkrech, to me your proposal sounds good.
In such a way we should satisfy both the needs of not weakening the schema and of allowing the daughter board description through the standard.
Hence, according to your suggestion, for a daughter board, we should have something like in the example hereafter:
<mountedDevice Dname="NO_MCU" Dvendor="Generic:5"/>
<compatibleDevice Dname="NO_MCU" Dvendor="Generic:5"/>
Since the Dvendor attribute is required by both the mountedDevice and compatibleDevice elements, we should use "Generic:5". Otherwise we should add a value like "NO_VENDOR" to the Device Vendors table of predefined value and use it, having something like this:
<mountedDevice Dname="NO_MCU" Dvendor="NO_VENDOR"/>
<compatibleDevice Dname="NO_MCU" Dvendor="NO_VENDOR"/>

@jkrech do you mean that you want to prevent the pack developer from forgetting to think about the mounted device information and possibly miss the addition of the mountedDevice node?

Correct, we are relying on this information in order to link boards with devices.
If a csolution target-type specifies only a board the tools need to derive the device information.

So the summary of the proposal is to add a predefined value for
Dname="NO_MCU"
and
Dvendor="NO_VENDOR:0"
to specify a board that does not have a processor device mounted.

PR #199 opened for this issue.

PR #199 merged into the main branch. I think this issue can be closed.


No such file or directory

error while loading shared libraries: libpaddle2onnx.so.1.0.0rc2: cannot open shared object file: No such file or directory

./paddlelit: error while loading shared libraries: libdnnl.so.3: cannot open shared object file: No such file or directory

Are you compiling with source code?you can add cmake .. -GNinja -DPY_VERSION=3.8 -DWITH_GPU=ON -WITH_ONNXRUNTIME=ON -WITH_ONEDNN=ON ，and ${paddle_inference_demo} compile.sh  set LIB_DIR=${paddle_path}/build/paddle_inference_install_dir.


No way to tell which version is running

@trouserless reports this and it is true

Fixed in 1.6.1

See: https://github.com/sidprobstein/swirl-search/blob/main/docs/RELEASE_NOTES_1.6.1.md


how can i add other api documentation?

I wanna add other documentation like vuetify documenation  in this app, how can i do it ?

@codeitlikemiley DevDocs Desktop is just a wrapper around https://devdocs.io/ (https://github.com/freeCodeCamp/devdocs/) and does not actually provide the documentation. You can suggest and vote for new docs on the official Trello board.


[Feature] add automation deploy violet_rails to heroku

addresses: https://github.com/restarone/violet_rails/issues/385
acceptance criteria

EC2 deployments using an older version of Node is still possible
New Node is only used on Heroku

deploy to heroku
Co-authored-by: Prashant<EMAIL_ADDRESS>Co-authored-by: donrestarone<EMAIL_ADDRESS>

What we learned from this release:

the rails_12factor gem is required to deploy to heroku
Since we have an Ember.js client + a full stack rails app we have 2 sets of node_module bundles
You can make your node configuration flexible by adding an || condition in your package.json-- this allows us to support 2 versions of Node.js without disruption production systems (we need permission to change supporting libraries or anything that may require us to re-issue Amazon AMI's).
The procfile is very important-- this is where we would define release hooks (DB migration, sitemap generation etc)


feat: default global app theme

What does it do
This PR implements the initial and default global theme the app will use. This will have to change later when we add user-customizable themes.
This PR also includes some components rewritten to use the global theme. This is still a work-in-progress.
Usage
The theme should be automatically applied in all the app.
This PR also includes some TextStyle extensions that should help set its Color. Just import the file and then use the withColor or withWeight methods.
Why is it needed
It should start to normalize the colors, fonts and more through all the app.

@amenes12 @AdrianAlzamoraG I rewrote both of your components that you made on #2, #3 and #7. Check it out so that you have an idea of how to work with the theme system.
PS.: I have deleted (for now) the form validation and controls since we'll be using the BLoC architecture and I'll add that on another PR.


Test case slow, but fast on cmdline

The following two tests (branch sw/error-msgs) cause a timeout when run as unit tests. But when invoked on the cmdline, they perform fast. See PR #38, file test/error_msgs_tests.erl
-module(invalid_map).

-compile(export_all).
-compile(nowarn_export_all).

-spec bar(atom()) -> integer().
bar(_) -> 0.

-spec foo([integer()]) -> [integer()].
foo(L) -> lists:map(fun bar/1, L).

-module(redundant_branch).

-compile(export_all).
-compile(nowarn_export_all).

-spec bar(integer()) -> a | b |c .
bar(_) -> a.

-spec foo(a | b | c) -> integer().
foo(X) ->
    case bar(X) of
        a -> 1;
        b -> 2;
        c -> 3
    end.

list_pattern_02 is also a test case that is fast on cmdline but sometimes timeouts in CI

list_pattern_07 is also slow (tally ~7s).

Both example take about 3s on the cmdline. That's not really fast.

Not relevant anymore. Closing until another example exhibits this behavior with the current branch.


🗣Oral  - The Evaluation of Chinese Human-Computer Dialogue Technology,SMP2019-ECDT

AMC Seminar Sign Up

Link to previous seminar meeting minutes issue:

#201
1. Oral / Poster Selection

Select one of the following selections for Oral or Poster:

Oral should be prepared for 15 - 30 minutes, and no more than 45 minutes, including Q/A.
Posters should be prepared for 5 - 10 minutes, and no more than 15 minutes, including Q/A.

[x] 🗣 Oral (15 MIN)
[ ] 📰 Poster (5 MIN)

2. Paper Information

Please fill the follow table and provide all the information as many as possible, for sharing with others better. (delete the rows that you did not fill)

Paper
Information

Name
SMP2019-ECDT

Recommendation
Human-Computer Dialogue in practice

Prior Knowledge
GPT

Year
2019

Publish
CIPS-SMP

Blog
http://conference.cipsc.org.cn/smp2019/evaluation.html

3. After Party 🍻

Everyone will be welcome. You can join or not join as you want (not required by the AMC), and change your mind at any time.

After Party will be started right after all the meeting agenda had been fulfilled.
We will find a bar and drink beers and talk whatever we want. (we can expect that it will be related to meeting topics of the day)
The bill will be paid AA

[ ] 🍻 YES! I'll definitely join the After Party!
[x] 🤔 Maybe. I'd like to decide later.
[ ] 🛌 No, I'm afraid not this time.

4. New Friend

Whether you have a new friend comes with you to the club.

[ ] 👥 I'll bring a new friend
[x] 👤 There's no new friend from me

Please fill the following table for the new friend sign up(if any), or delete it.

Artificial Intelligence & Machine Learning CLUB, 2018 - 2019 AI ML Club - AMC Member Manual

I love NLP oral!
Looking forward to hearing it! :clap:

However, I believe you linked to the wrong issue number.
The previous minus issue is #201, not #199 :)

我申请挂靠胜杰的 Oral 参会 @CyFeng16

@CyFeng16 申请此PR参加8\11的AMC


jersey-multipart 1.19

Type: Missing
Summary:
jersey-multipart 1.19
Details:
ClearlyDefined license is GPL-2.0-only WITH Classpath-exception-2.0
Maven license is same as above: https://mvnrepository.com/artifact/com.sun.jersey.contribs/jersey-multipart/1.19
Resolution:
GPL-2.0-only WITH Classpath-exception-2.0
Affected definitions:

jersey-multipart 1.19

@LandOfBliss This curation is missing the CDDL-1.1 license and I didn't catch it before merging. @capfei Is that something we can fix easily?


Let #response still return something

Changes Unknown when pulling b8d56e78a4e7e81c2ae3d0501cbc113432101e96 on JustinAiken:feature/alias_response into ** on adhearsion:develop**.

Any idea why we're getting code coverage information on a branch that was merged 18 months ago?