Exporting StarDist model to DeepImageJ model

Hi @deepimagej ,
I would like to use my own StarDist model ( we had to add images from our dataset with new annotations) but I can not find a way to export it (yet).
I tried re-using your code example but got these troubles  :
-I’ve loaded my model using the function from StarDist and got :
AttributeError                            Traceback (most recent call last)
<ipython-input-23-843654a17ca2> in <module>
     15
     16 signature = tf.saved_model.signature_def_utils.predict_signature_def(
---> 17             inputs  = {'input':  model.input},
     18             outputs = {'output': model.output})
     19

AttributeError: 'StarDist2D' object has no attribute 'input'

so I guessed that StarDist model might not have an input !
So I tried to use the keras function from your code and got :
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-27-81d916cc2deb> in <module>
      8
      9 K.set_learning_phase(1)
---> 10 model = keras.models.load_model(model_path_str)
     11 #model = StarDist2D(None, name=model_name , basedir=model_path)
     12

m:\2-stardist-env\stardist_0.3.2\lib\site-packages\keras\engine\saving.py in load_wrapper(*args, **kwargs)
    456                 os.remove(tmp_filepath)
    457             return res
--> 458         return load_function(*args, **kwargs)
    459
    460     return load_wrapper

m:\2-stardist-env\stardist_0.3.2\lib\site-packages\keras\engine\saving.py in load_model(filepath, custom_objects, compile)
    548     if H5Dict.is_supported_type(filepath):
    549         with H5Dict(filepath, mode='r') as h5dict:
--> 550             model = _deserialize_model(h5dict, custom_objects, compile)
    551     elif hasattr(filepath, 'write') and callable(filepath.write):
    552         def load_function(h5file):

m:\2-stardist-env\stardist_0.3.2\lib\site-packages\keras\engine\saving.py in _deserialize_model(h5dict, custom_objects, compile)
    237         return obj
    238
--> 239     model_config = h5dict['model_config']
    240     if model_config is None:
    241         raise ValueError('No model found in config.')

m:\2-stardist-env\stardist_0.3.2\lib\site-packages\keras\utils\io_utils.py in __getitem__(self, attr)
    316             else:
    317                 if self.read_only:
--> 318                     raise ValueError('Cannot create group in read-only mode.')
    319                 val = H5Dict(self.data.create_group(attr))
    320         return val

ValueError: Cannot create group in read-only mode.

so the StarDist model might not be compatible with keras function!
Would you have an example of code for stardist?
Best regards,
Romain

Hi @romainGuiet,
StarDist library works a bit different so the code needs to be adapted. There is a new notebook in the repository to store StarDist models as TensorFlow SavedModel:
https://github.com/deepimagej/python4deepimagej/blob/master/export_StarDist_to_TensorFlow_SavedModel.ipynb
It is written for StarDist version 0.3.6 (most updated version until now):
Once you read your model using StarDist2D:
model_paper = StarDist2D(None, name='your_model', basedir='/path_to_your_model/')
model_paper.load_weights('weights_best.h5')

the input and output are given as
# Input

model_paper.keras_model.input[0]

# Output 1: the object probability (normalized euclidean distance to the nearest background point)

model_paper.keras_model.output[0]

# Output 2: 32 radial distances to the boundary of the object

model_paper.keras_model.output[1]

Hence, to export it as a TensorFlow SavedModel you can now use a very similar code:
OUTPUT_DIR = "/content/drive/My Drive/the_path_where_you_want_to_save_your_model/new_folder"

builder = tf.saved_model.builder.SavedModelBuilder(OUTPUT_DIR)

# StarDist has two different outputs. DeepImageJ can only read one of them, so
# we concatenate them as different channels to use them in ImageJ.

signature = tf.saved_model.signature_def_utils.predict_signature_def(
            inputs  = {'input':  model_paper.keras_model.input[0]},
            # concatenate the output of StarDist
            outputs = {'output': concatenate([model_paper.keras_model.output[0],model_paper.keras_model.output[1]], axis = 3)})

signature_def_map = { tf.saved_model.signature_constants.DEFAULT_SERVING_SIGNATURE_DEF_KEY: signature }

builder.add_meta_graph_and_variables(K.get_session(), [tf.saved_model.tag_constants.SERVING],
                                             signature_def_map=signature_def_map)
builder.save()

I hope this helps!
Thank you for reporting the issue

Hi @esgomezm,
That's awesome!
Thanks a lot for your efforts!
Best,

Hi @romainGuiet Hi @esgomezm,
I was trying this code to export a 3D StarDist model, but the outputs won't concatenate. I'll include a picture of the error. I'm really new to this, so I'm sure I'm missing something very obvious, but any help would be much appreciated!
Thank you for providing all of this code, amazing work!
Best wishes,
Michael


Merge ctl and ops ConnectionConfigs and DatasetConfigs

@seanpreston can we get more info here? are you referring to ctl's credentials toml section?

@seanpreston I think this issue is covered by the tickets I created for the unified fides resources epic. Can this be closed now?


Configurable json content types

According to #5 added application/ld+json to defaults and made expected json content types configurable with:
# config/services.yaml

json_request:
    content_types: ['json', 'jsonld']

@gassan Thanks for your PR!


Feature Request: Add a feature to select channels on category Page.

Framework version: 0.1.1
The field should be multiselect so that one category can be selected for multiple channels.

This feature does not extend to product repository attributes
ProductRepository->channels does not work.
This feature needs baked into the core more. It is very difficult to use if integrated via API or directly through classes.


Error in running compute_pooled_results.py

Hi thanks for making the code public, I run evaluate_all_models.py, and on some data sets of smd, the log:
Error in evaluating models on entity:machine-1-6 . When I run compute_pooled_results.py, the len(ranking_obj.predictions.keys()) is 9 and not equal to N_MODELS

In eval_utils.py,
File "/home/tsadams/utils/eval_utils.py", line 97, in pool_predictions_of_entities
    predictions[mn][q] = np.concatenate(predictions[mn][q], axis=1)
  File "<__array_function__ internals>", line 180, in concatenate
ValueError: need at least one array to concatenate

predictions=[]

Hi Ningning,
Thanks for your interest in our code!
Regarding Error in evaluating models on entity: machine-1-6: You said that you get this error only on some datasets of SMD. I am not sure if I have enough information to help you debug the specific issue, but I am hoping that it is something data specific. I noticed that for some datasets, some trained models might yield such errors.
Regarding len(ranking_obj.predictions.keys()), can you check if all models were trained? Sometimes, some models fail during training.
For predictions=[], from the information I have, it seems that some model has failed to train, or produce predictions, and hence the prediction dictionary corresponding to that model is empty.
Overall, I think it would be good to check if all models have finished training successfully, and whether they are providing reasonable predictions by visualizing how well they reconstruct time-series.
Let me know if you have any more questions, I will close this issue for now, but feel free to open another issue!

Let me know if you face more issues! Feel free to open another issue!

The order I run is to first run download_data.py to download the data set,
then run train_all_models.py to train the model,
then run evaluate_all_models.py to evaluate the model,
and finally run compute_pooled_results.py.
At the stage of running evaluate_all_models.py, I found an error
Can't get attribute 'EuclideanDistance64' on <module 'sklearn.metrics._dist_metrics' from '/home/miniconda3/envs/tsadams/lib/python3.9/site- packages/sklearn/metrics/_dist_metrics.cpython-39-x86_64-linux-gnu.so


Add forEachRenderableTile

I noticed that Cesium3DTileset.cpp has a lot of duplication when iterating over tiles with UCesiumGltfComponent. So, for convenience / reusability, I added a forEachRenderableTile template function that allows for a callback on each UCesiumGltfComponent in a collection of tiles.
I've updated a handful of functions to use this call. It can also be reused if we ever need to collectively transform / iterate over tiles in future functionality. I haven't noticed any clear performance differences, but let me know if something here is in bad form.

Forgot that only Unreal 5.4 is on C++ 20 🤦 I'll add overloads for the time being.

Forgot that only Unreal 5.4 is on C++ 20

#1447 moves all UE versions to C++20.

Merged with main. This is ready for a look!


Unable to compile

Okay, it's been like two weeks that the code from repo is not compilable. What happened, what's been messed up with tor integration?

https://github.com/zcoinofficial/zcoin/issues/193
https://github.com/zcoinofficial/zcoin/issues/188
https://github.com/zcoinofficial/zcoin/issues/191 (closed with no explanation - unsolved to me)
https://github.com/zcoinofficial/zcoin/issues/192

Is there going to be any comment on this? How to approach the issue? Are there new dependencies required now, which are not mentioned in the build instructions?

Missed it. Added now, thanks :)

yeah thanks for making this. we should not have to use precompiled binaries.

It should build now with <IP_ADDRESS> as the latest. May we close this out please . . .


KFP v2 runs are broken in 2.0.0-alpha7

Checks

[X] I have searched the existing issues.
[X] This issue is NOT specific to the CLI. (If so, please open an issue on the CLI repo)

deployKF Version
0.1.3
Kubernetes Version
1.29.0

Description
Kubeflow v2 pipelines are broken in v2.0.0-alpha7 that is shipped by default with DeployKF.
Google in their infinite wisdom have hardcoded the kfp images here with the :latest tag:
https://github.com/kubeflow/pipelines/blob/2.0.0-alpha.7/backend/src/v2/compiler/argocompiler/argo.go#L110-L111
They are not exposed in config in any way, just hardcode, then they proceed to break them somewhere in upstream, making kfp2 unusable for anyone on 2.0.0a7: https://github.com/kubeflow/pipelines/issues/8446
Upgrading to 2.0.0 works in the meanwhile, but for the next deployKF, we need to make sure to be off this version.
I realize that this is not strictly a deployKF issue, but in the latest version said images are parametrized as envvars, so it would be nice to expose these in sample-values.yaml:
https://github.com/kubeflow/pipelines/blob/master/backend/src/v2/compiler/argocompiler/container.go#L28-L34
This is important for offline deployments and would be nice to have less dependence on whatever is happening in upstream image repos.
Relevant Logs
F0210 01:08:49.734299      17 main.go:74] KFP driver: driver.Container(pipelineName=hello-pipeline, runID=16b95bd1-dcab-4799-9d75-5345910efc1c, task="say-hello", component="comp-say-hello", dagExecutionID=14, componentSpec) failed: failure while getting executionCache: failed to list tasks: rpc error: code = Unimplemented desc = unknown method ListTasksV1 for service api.TaskService
time="2024-02-10T01:08:50.613Z" level=info msg="sub-process exited" argo=true error="<nil>"

@pbasov first, I want to clarify that v2.0.0-alpha7 is not actually able to run Kubeflow Pipelines v2 pipelines, it's only able to run v1 and v2-compatible pipelines. The version numbers are ridiculously confusing, I know.
Second, deployKF actually already has a way to override the kfp-launcher image (for v2-compatible pipelines, not v2) using the kubeflow_tools.pipelines.kfpV2.launcherImage value, which configures this Kyverno ClusterPolicy to mutate the Pods at runtime.

I want to clarify that v2.0.0-alpha7 is not actually able to run Kubeflow Pipelines v2 pipelines, it's only able to run v1 and v2-compatible pipelines. The version numbers are ridiculously confusing, I know.

I find the whole kf dsl system ridicilously confusing, tbh. Feels like it's supposed to make ML engineer's life easier, but it's exact opposite.

kubeflow_tools.pipelines.kfpV2.launcherImage value, which configures this Kyverno ClusterPolicy to mutate the Pods at runtime

This is really cool, gotta RTFM, consider this matter closed, then.

Second, deployKF actually already has a way to override the kfp-launcher image (for v2-compatible pipelines, not v2) using the kubeflow_tools.pipelines.kfpV2.launcherImage value, which configures this Kyverno ClusterPolicy to mutate the Pods at runtime.

Does this mean we can run a Kubeflow Pipeline v2 (newer than 2.0.0-alpha.7 from 1 year ago)?
What does "for v2-compatible pipelines, not v2" mean?

Second, deployKF actually already has a way to override the kfp-launcher image (for v2-compatible pipelines, not v2) using the kubeflow_tools.pipelines.kfpV2.launcherImage value, which configures this Kyverno ClusterPolicy to mutate the Pods at runtime.

Does this mean we can run a Kubeflow Pipeline v2 (newer than 2.0.0-alpha.7 from 1 year ago)? What does "for v2-compatible pipelines, not v2" mean?

@sebracs it's a bit confusing, Kubeflow Pipelines version 2.0.0-alpha.7 included a mode called v2-compatible which was like a "beta test" for the full v2. That is to say, you can't use v2 right now with deployKF v0.1, you must use pip install kfp==1.8.22 (which supports both v1 and v2-compatible, but NOT v2 pipelines).
When deployKF v0.2 is released, it will include Kubeflow Pipelines v2 (which may or may not fully support v1 pipelines, so users may want to stay on deployKF v0.1 until they are ready to upgrade).


[Bugfix] Respect modules_to_not_convert within awq_marlin

FIX https://github.com/vllm-project/vllm/issues/9894
AWQ respects this parameter but AWQ Marlin did not, this PR makes AWQ Marlin use the same ignore layer logic.

FYI - just tried this PR against the latest main branch and can confirm that it solves the issue with loading Qwen2-VL-7B's AWQ quant using awq_marlin.


source-filesystem: due creating nodes from files at random, the build ends up with different hashes despite content having not changed

I'm using source-filesystem plugin to get contents from a dozen content files and generate a page using graphQL.
I noticed that the build hash after runWebpack is finished
here https://github.com/gridsome/gridsome/blob/809aaf8a8b40d07ef89c34c32bfe783e33b61f43/gridsome/lib/build.js#L24 kept changing all the time, despite not having changed the files.
Tracked it down to here:
https://github.com/gridsome/gridsome/blob/809aaf8a8b40d07ef89c34c32bfe783e33b61f43/packages/source-filesystem/index.js#L60-L71
The files are globbed and then read all at once, and the .addNode function will be called in a somewhat random order, depending on when the handle becomes available.
It seems that adding nodes at random rather in a deterministic fashion results in the hash changing.
The app hash is added to the headers of all files as well as appended to the app.js filename and so, deploying twice even without changing any files, will result in cache busting.
The expectation is for the hash to be deterministic - same input should yield same output.
i've put in a kludge on my local build to fix the behavior:
  async createNodes (actions) {
    const glob = require('globby')

    const files = await (await glob(this.options.path, { cwd: this.context })).sort()

    let allOptions = [];
    await Promise.all(files.map(async file => {
      const options = await this.createNodeOptions(file, actions)
      allOptions.push(options);
    }))

    allOptions.sort((a, b) => a.fileInfo.path > b.fileInfo.path ? 1 : -1);
    allOptions.forEach(options =>{
        const node = this.collection.addNode(options)
        this.createNodeRefs(node, actions)
    });
  }

Sorting the files before calling addNode seems to do the job, but i'm not too familiar with the inner workings and maybe the actual fix needs to go someplace deeper.

Thanks for debugging this, @tstriker. I did some more tests yesterday and noticed that the order of the nodes affected the routes.js file in some cases. I fixed that by sorting the routes by priority, then the path.
And the webpack loader for page-query generates no code, which is correct. But results in a very random behavior where it sometimes is replaced with a boolean and some other times with a module from webpack. But I get a consistent build by just making it generate export default null.
At least, I get the same hash every time when building gridsome.org after these changes :)

But I am still getting different hashes when building gridsome.org with gridsome v0.7.20 😕 What's wrong?

https://github.com/gridsome/gridsome/commit/da5674fd248fd518963328628d578c0c93451d95#r62290122


Hbase Server Side Filters

This commit implements HBase Server Side Filtering. Server side filtering is off by default, but is functioning correctly and can be turned on.
All tests were run on the system and there were no failures.

you guys have any interest in re-writing in scala? we'd probably need a java class that extends the scala class to provide the static method required by the hbase interface, but that shouldn't be too bad.

has conflicts with master

@jnh5y do we want to include transforms in this filter too? Or will we add that as another PR?

All requested changes have been made! The commits have been rebased on locationtech/master to remove merge conflicts with the base branch.
Transforms will be added as a separate PR later. This pull request only implements HBase Filters.
If there are any other changes required please let me know!

replaced with #1430


Update to use new Az module

Category
[ ] Bug
[X] Enhancement
Problem Area
[X] Page Transformation: Error during the setup/use of the Page Transformation UI solution (did you check our troubleshooting guide?)
[ ] Page Transformation: Error during the use of page transformation from PnP PowerShell
[ ] Page Transformation: Error during the use of page transformation from .Net
[ ] Page Transformation: Page is not looking correct after transformation
[ ] Modernization Scanner: something went wrong...
Expected or Desired Behavior
Use current PowerShell modules
Observed Behavior
Using AzureRM module
Steps to Reproduce
Provision-ModernizationFramework.ps1

Hi @danmyhre ,
As mentioned in your previous issue (which was fixed by your PR) the UI component is currently not receiving much focus as we'll first want the provisioning engine component to be covering all scenarios. I'll leave this issue in, but will tag it as a future idea.

Given the UI component anyhow does not work in your scenario and that we're not actively planning any work on it I'm gonna close this one. Hope you don't mind @danmyhre .

Yep, no worries!


Replace "pallete" by "palette"

Throughout the code, the word "pallete" is used. This seems like a typo.

Ah yes, thank you!


[hotfix] Change FlussLakehousePaimon  to use  logging

 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.


Fix XML parsing in WASI environment

Final chunk of XML document was being skipped when parsing when in a WASI environment

@swift-ci please test

CC: @MaxDesiatov

@swift-ci please test

@swift-ci test macOS

I can't quite tell from the output of the macOS action- Are there legitimate test failures I need to address?

The test failure seems unrelated, but I requested at least one more review just in case.

@swift-ci please test macOS platform

@swift-ci please test macOS platform


Groups

Groups would be a new Apollo feature.

Backed by Discord roles
Anyone in the server can create a group with a non-conflicting name
Anyone can join or leave existing groups at any time
Ping the role
The person who created the group can delete it
Have an option to show a list of groups in the server

Consider storing usernames as well


Please add ROUND function to Druid SQL

It is already implemented as part of http://druid.io/docs/latest/misc/math-expr.html
Please expose it in SQL.
In the meantime one can do:
CASE WHEN X - FLOOR(X) < 0.5 THEN FLOOR(X) ELSE CEIL(X) END

TIL that SQL ROUND is more complex than I thought

This is done


Address feedback from UX studies for 5.1.0-beta.x

[ ] Add visual to the documentation to explain the mined opinions structure and naming better. i.e. Small graphic with opinion, sentence etc. in sample/
[ ] Change documents in all batch samples to have multiple sentences instead of one.
[ ] Consider improving the docstrings for all the Options bag in the SDK to include what type of options are there.
[ ] Improve how we surface in the debugger properties that are in xxCollection types so they don't get lost in the Raw view area.
[ ] Adding helper method to get opinions? Is helper method for optional property feasible? Will removing details about offset/length will cause confusion in the future? What is the priority of adding helper methods?
[ ] Improve IsNegated docstring to include how this affects the sentiment of the Opinion.

Consider improving the docstrings for all the Options bag in the SDK to include what type of options are there.

PR https://github.com/Azure/azure-sdk-for-net/pull/16281

Improve IsNegated docstring to include how this affects the sentiment of the Opinion.

PR https://github.com/Azure/azure-sdk-for-net/pull/16281

Improve how we surface in the debugger properties that are in xxCollection types so they don't get lost in the Raw view area.

Issue https://github.com/Azure/azure-sdk-for-net/issues/16283 created

Adding helper method to get opinions? Is helper method for optional property feasible? Will removing details about offset/length will cause confusion in the future? What is the priority of adding helper methods?

Issue https://github.com/Azure/azure-sdk-for-net/issues/16284 created

Change documents in all batch samples to have multiple sentences instead of one.

Issue https://github.com/Azure/azure-sdk-for-net/issues/16361

Issues have been created for all work item. Will follow up progress in each individual one.


Azure yaml if then else for conditions

Hi,
At the moment, I have two conditions in my yaml. I want to add more conditions e.g.
('Saturday' and 'ScheduledBuild') and so on. I am unable to find a clean way of having additional conditions without repeating myself with the previous conditions.
    - task: DotNetCoreCLI@2
      inputs:
        command: test
        projects: '**/*MyTests/*.csproj'
        arguments: '--verbosity minimal --configuration $(buildConfiguration) --no-build --logger:trx --filter TestCategory!=LongRunningTests --settings $(DefaultUTSettings) /p:AltCover=true /p:AltCoverForce=true /p:AltCoverAssemblyFilter=NUnit /p:AltCoverCobertura="$(CodeCoverageResultsDir)/altcover.cobertura.xml"'
        publishTestResults: true
      continueOnError: true
      displayName: 'dotnet test'
      condition: not(and(succeeded(), eq(variables['DayOfWeek'], 'Sunday'), eq(variables['IsScheduledBuild'], 'True')))
    - task: DotNetCoreCLI@2
      inputs:
        command: test
        projects: '**/*MyTests/*.csproj'
        arguments: '--verbosity minimal --configuration $(buildConfiguration) --no-build --logger:trx --settings $(FullViewsComparisonTestUTSettings) /p:AltCover=true /p:AltCoverForce=true /p:AltCoverAssemblyFilter=NUnit /p:AltCoverCobertura="$(CodeCoverageResultsDir)/altcover.cobertura.xml"'
      continueOnError: true
      displayName: 'dotnet test'
      condition: and(succeeded(), eq(variables['DayOfWeek'], 'Sunday'), eq(variables['IsScheduledBuild'], 'True'))

As an example, suppose I want to add a condition for 'ScheduledBuild' other than Sunday, do something else with dotnet test. How do I do it without repeating myself in a complicated way?
condition: and(succeeded(), eq(variables['DayOfWeek'], 'Sunday'),
condition: and(succeeded(), ne(variables['DayOfWeek'], 'Sunday'),

condition:? <this is the tricky part which I can't understand>. An else condition here would be very helpful.

Thanks,
Anubhav.

pipeline node conditions are logically associated with the link (or edge) that connects them to the graph.
In your case if you're only dealing with compile time constants, you might be able to use yaml preprocessor macros, the ${{ }} syntax. We are currently developing features to make the preprocessor more powerful.
Another way that is to put the content of your job into a separate file and load it as a template in two places (controlled by conflicting conditions).

Agreed, I think we can do this with parameters once @jeschu1's new features ship. I'll leave this open which will hopefully remind me to ping the thread once that's out.


Question: How to add livy chart as dependent chart

First off - amazing work get this helm chart!!!
I tried specifying the dependencies
dependencies:
- name: livy
  version: "v2.0.2"
  repository: https://jahstreet.github.io/helm-charts

It does not work.
I might be doing something wrong here.
What is correct way to add livy chart as a dependencies?

For now I am manually copied helm chart for livy and added it under charts folder.
Let me if there is better way to do it.

Hi @manjiler , thx for the feedback. Can you share the errors you observe?

After adding livy as dependency in Chart.yaml. Running helm dependency update, give the below error
Error: can't get a valid version for repositories livy. Try changing the version constraint in Chart.yaml
Sample Chart.yaml
dependencies:
- name: livy
  version: "v2.0.2"
  repository: https://jahstreet.github.io/helm-charts

I know its too late to comment on this. The problem is with using v2.0.2 I think.
I am using it with "2.0.* " and the latest is 2.0.1 I think as thats the version I see getting used in my cluster.

Closing this issue in favour of https://github.com/JahstreetOrg/spark-on-kubernetes-helm/issues/82 within which it (and similar to it) should be resolved, lets continue there.
And thanks for the patience 🙏 .


Adds a nested event_type attribute in the response

OperatorEvents now have a nested attribute 'event_type' in the
response which are the serialized record for the OperatorEventType

@FBRTMaka @oceanzus @birdage

This makes sure the response from anything from operator_event returns the nested type in it.
    {
      "event_comment": "Shutdown the CTDBP on the inshore surface mooring.",
      "event_time": "2015-01-28T18:55:23.050320",
      "event_title": "Instrument Shutdown",
      "event_type": {
        "id": 1,
        "type_description": "General information event.",
        "type_name": "INFO"
      },
      "id": 1,
      "watch_id": 2
    }

I’m cool with it


module 'networkx' has no attribute 'write_gpickle'

hey
not able to find the write_gpickle for the sample code.
error msg:
    networkx.write_gpickle(self.graph, f"{graphname}.gpickle")
AttributeError: module 'networkx' has no attribute 'write_gpickle'
(myenv-lx) harshu@harshith-lx:~/personal/new-str/streamlit_app/dev-ing$

Indeed this is a packaging issue.
The latest version of NetworkX does not contain write_gpickle.
A workaround is to simply use joblib.dump
I'll implement this and close this issue ASAP.
Thanks !

fixed with latest update


Build: GitHub action build deploy

Hmm weird, it just won't build with the sub directory. Will investigate some other day.


How do I increase the function of downloading files?

How do I increase the function of downloading files?
I also hope to increase the download progress display function.

Hello @lockzero0! We're working on a new version with IPFS Web UI bundled with IPFS Desktop. Then, you'll have all the advantages that come from IPFS Web UI and Desktop together!

@lockzero0 we have a new release ready! Please try it out 😄


Small typo in dry-run of remove snapshot

This PR fixes a small typo in the diagnostic message of a dry-run forget command.

Current coverage is 51.33% (diff: 0.00%)

Merging #682 into master will decrease coverage by 0.14%

@@             master       #682   diff @@
==========================================
  Files            95         95
  Lines          7477       7477
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           3849       3838    -11
- Misses         3076       3090    +14
+ Partials        552        549     -3

Powered by Codecov. Last update ef9b974...5996d67

Great catch, thank you!


⚠ Digital Ocean - https://status.digitalocean.com/ has degraded performance

In 6b33896, Digital Ocean - https://status.digitalocean.com/ (https://status.digitalocean.com/api/v2/status.json) experienced degraded performance:

HTTP code: 200
Response time: 61 ms

Resolved: Digital Ocean - https://status.digitalocean.com/ performance has improved in dfcf1f9.


Extra conda badges

The badges below are not supported currently. It would be good to add them as well.
https://anaconda.org/anaconda/conda-build/badges/latest_release_date.svg
https://anaconda.org/anaconda/conda-build/badges/latest_release_relative_date.svg
https://anaconda.org/anaconda/conda-build/badges/platforms.svg

Do you have repo urls where those badges are being used?

PR #152

The badges were added in PR #152. Closing the issue.


AttributeError after login through the browser

Describe the bug
AttributeError after login through the browser.
Command Name
az login
Errors:
'SubscriptionClient' object has no attribute 'config'
Traceback (most recent call last):
python3.8/site-packages/knack/cli.py, ln 215, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 654, in execute
    raise ex
cli/core/commands/__init__.py, ln 718, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
cli/core/commands/__init__.py, ln 711, in _run_job
    six.reraise(*sys.exc_info())
lib/python3.8/site-packages/six.py, ln 703, in reraise
    raise value
...
azure/cli/core/_profile.py, ln 888, in _find_using_common_tenant
    client = self._arm_client_factory(token_credential)
azure/cli/core/_profile.py, ln 807, in create_arm_client_factory
    configure_common_settings(cli_ctx, client)
cli/core/commands/client_factory.py, ln 79, in configure_common_settings
    client.config.enable_http_logger = True
AttributeError: 'SubscriptionClient' object has no attribute 'config'

Expected Behavior
The azure-cli should login to azure.
Environment Summary
Linux-5.6.15-arch1-1-x86_64-with-glibc2.2.5
Python 3.8.3
Installer: PIP

azure-cli 2.7.0

Additional Context
Currently using SSO through office365 for login.

add to S172

@yonzhan I'm also experiencing the same issue on azure-cli 2.8.0. Happy to provide further debugging information if required.

Looks like you installed Azure CLI with pip and then manually installed the Track 2 SDK azure-mgmt-resource 15.0.0b1 which changed config to _config:
self._config = SubscriptionClientConfiguration(credential, **kwargs)

You may confirm the installed version of azure-mgmt-resource with pip list:
> pip list | Select-String azure-mgmt-resource

azure-mgmt-resource                   10.0.0

Azure CLI depends on
https://github.com/Azure/azure-cli/blob/b01fbe373a059aa6c746e6e067aac4ac77323211/src/azure-cli/requirements.py3.windows.txt#L71
Please reinstall Azure CLI with
pip install azure-cli --force-reinstall

We recommend using the official installation methods: Install the Azure CLI. If you have to install with pip, please make sure Azure CLI is installed in an isolated virtual environment so that its dependencies are not broken by any other installations.

Thanks for digging into this @jiasli. It does indeed look like a mismatch in expected versions.
It looks like @Dissonant-Tech is using Arch Linux, like myself, and probably is using the python-azure-cli which has a dependency on the python-azure-git package. This is quite unstable, but it looks like the azure-cli package is the best way forward. It uses the official install script, just packaged for Arch Linux.
It works well on my machine, and if you agree @Dissonant-Tech I think we can close this issue?

Hi @JamieMagee, thanks for the analysis.
However, the package on Arch Linux's repository is not maintained by Azure CLI team and is provided by the community. We only support installation method provided in the official doc Install the Azure CLI. See https://github.com/Azure/azure-cli/issues/9326#issuecomment-564364205 for a similar issue.
Thanks for understanding.


Help please!

Hello!
Im new on this and i would like to run this miner on a linux VPS.
Long time ago i got some linux VPS with unlimited time hosting and now im not using them, just personal webpages and some game hosting but i would like to mine with them.
Already i created an account on coinhive but im unable to run the javascript mining on the linux terminal. If someone could help me with some magic commands to make an easy and fast setup to mine i will apreciate a lot :)

You shouldn't mine on a shared server (virtual private server = shared). I doubt your host will appreciate you using up all the cores for mining. They will likely kill your account. If you have access to a dedicated server, you should be mining with xmr-stak-cpu instead of javascript based miner for higher hash rates. You want to use coin-hive if you have a popular website and your visitors help you mine.

Also have a dedicated server (linux debian), but i would like to learn how to mine from the terminal linked to my coinhive account (just to educational purposes).
sincerely i dont know too much about mining programs, but at the moment i see that coin-hive is the most easy to use (for browser) but i would like to learn in how to use on a Linux terminal.
In the past i used cgminer and bfgminer to mine bitcoins on many hardwares but i forgot all.

root@openkore:~# sudo coin-hive 4uqxBZzQhq2kLdyXeGhWbKaG49YCd7k7
Site key: 4uqxBZzQhq2kLdyXeGhWbKaG49YCd7k7
âââââââââââââââââââââ¬ââââââââââââââââââââ¬ââââââââââââââââââââ
â     Hashes/s      â       Total       â     Accepted      â
âââââââââââââââââââââ¼ââââââââââââââââââââ¼ââââââââââââââââââââ¤
â        0.0        â         0         â         0         â
âââââââââââââââââââââ´ââââââââââââââââââââ´ââââââââââââââââââââ
â  | Listening on localhost:3002 | 8 Threads
s: Start/Stop | +/-: Threads | a: Auto threads | q/Ctrl-C: Quit
An error occured Page crashed!
Got this

have you tried this? https://github.com/cazala/coin-hive#im-having-errors-on-ubuntudebian

@cazala Yes already i tried that.
Starting from a clean pre-configured basic linux server.
I did this in this order:
sudo apt-get update
sudo apt-get upgrade
curl -sL https://deb.nodesource.com/setup_9.x | sudo -E bash -
sudo apt-get install -y nodejs
sudo apt-get install nodejs npm
sudo apt-get -y install gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 ca-certificates fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils wget libxext6
sudo npm i -g coin-hive --unsafe-perm=true --allow-root
sudo coin-hive 4uqxBZzQhq2kLdyXeGhWbKaG49YCd7k7 --username test1

I'm curious to see if you can get this going, I want to do the same thing with my VPS

solved. In all case, i recomend to dont do it on VPS, do only if you have a dedicated.

what was it @Zelektor?

something about readding java script. i just installed a web interpreter that got all java script libraries.


[FEATURE] Confirm Annotation Delete Participants

Description
When deleting all annotations for a marker as participant, there should be a confirmation dialog asking if the deletion should really be executed

https://github.com/KoALa-MHF/koala-app/pull/323


Non-MD files in the content directory (like jpg's and png's) end up as html's

When I put non-md files in the content directory, they should just be copied over (untouched!).
Now they end up as html's

Any updates on the custom processors, as well? It's an idea that also interests me. For instance, one could optimize images on build.
Honestly, I found the content folder somewhat misleading as it's not meant to hold arbitrary site content, but processable inputs.
Also, if we are to think them as raw, unprocessed documents, it makes sense that's the place we'd place related data, full resolution images and etc., as well. They would then be processed on build: charts generated, images resized and optimized, html generated. Of course, a pass-through processor is still a valid processor. :)
As not every file could (easily) have a front matter, @stou's file extensions idea seems like an acceptable solution for processor selection, if slightly magic. Some ideas of what may be possible:

/content/articles/lengthy-research.md: Article.
/content/articles/lengthy-research/chart1.pngchart.json: json to png charting.
/content/articles/lengthy-research/image1.optim.png: image optimization.
/content/articles/lengthy-research/image2.optim-600x150.png: image optimization and resizing.
/content/articles/lengthy-research/image2.png: pass-through?

I like this idea, but @stou's file extension idea only allows for a single result from the process. What if I want to make a thumbnail, medium size and full size from a single image?

How about introducing the concept of external alternatives to front matter? Appendix, lol?
This could make things slightly more consistent: every input (to be processed) must have a front matter, either embedded (markdown's front matter) or external (stand alone yaml and toml files that select the processor?). On the other hand, it adds to the project complexitivity and, potentially, build time.

/content/articles/test.md: embedded front matter.
/content/articles/test/image.png: means nothing by itself.
/content/articles/test/image.toml: what to do with image.png.

This could get annoying pretty fast, though. Another option would be to add the processing options to the pages' front matter:

/content/articles/test/image-{1,2,3}.png: do nothing by themselves.
/content/articles/test.md: embedded front matter saying hey, include images 1, 2 and 3, using preprocessor x with arguments y and z.

I think this could work, but it would limit our ability to process arbitrary files: they would to belong to an article. Perhaps on top of that there could exist support for stand alone .toml and .yaml files, that simply contain instructions for other files, similarly to the first suggestion but without the 1:1 toml/file relation.

Think we might be getting a little side tracked here, with the discussion on preprocessing files. That's a nice to have for non markdown files, but for a first cut, I will be quite happy in *.md files are the only ones that are processed, and everything else just gets copied as-is.
Creating a rails or docpad style asset pipeline based on multiple file extensions is a nice to have, but I think simply being able to put images referenced in a markdown file in the same folder as the markdown file will aid authoring in Hugo quite a lot.

+1

+1 what bguiz says

+1 I agree. The processing chain can easily be postponed

One note to he who implements the "copy files from content without processing" -- it would be very nice if static images/css could be treated as their cousins in the /static folder for livereloads (soft, not hard refreshes).

I'm 90% done with this today.
Steve Francia
spf13.com
@spf13

On Jan 23, 2015, at 11:02 AM, Bjørn Erik Pedersen<EMAIL_ADDRESS>wrote:
One note to he who implements the "copy files from content without processing" -- it would be very nice if static images/css could be treated as their cousins in the /static folder for livereloads (soft, not hard refreshes).
—
Reply to this email directly or view it on GitHub.

Glad to arrive to this issue and it's 90% ready! This improves the UX of writing complex articles.
I was thinking to have a developer blog with "demo.js" or "demo.css" per article or even JSON files .. so each article could be customized. Not only it would be useful for dev blogs.. also is a trend called "JavaScript Journalism", like you can see in some New York Times articles.

+1
The current logic feels counter-intuitive. Some posts need assets, such as images. These images are, by their name, assets, and hence belong with the post. I shouldn't have to worry about where they are located as a result of rendering the website, but currently I have to. I have to either refer to them by their rendered path or use the static folder trick to mirror the post's directory structure, and place my assets there, afterwhich I can then refer to them in the post simply by their name.
This, again, is counter-intuitive. Not only for the extra work, but also for the fact that the filesystem already provides for a way for me to bundle things together that belong, together, by using directories. Now if I have to mirror this directory structure, I have broken the connection between the post and it's assets [in the filesystem], then during rendering Hugo rebuilds the connection, and as a result the outcome is the same as if Hugo just let me have my damn files in the post's directory and be done with it.

100% agree. Working on making it better.

@spf13 are you pushing your work somewhere ? I would be very interested to see this being built. I have been working myself on thumbnailing pipeline recently and would be willing to contribute / adapt some of it to hugo.

+1

It's in master. The foundation is there to handle specific file types
differently. CSV already has a handler as an example / prototype.
--
Steve Francia
http://stevefrancia.com
http://spf13.com
http://twitter.com/spf13
On Wed, Mar 4, 2015 at 5:38 AM, Ivan Juras<EMAIL_ADDRESS>wrote:

+1
—
Reply to this email directly or view it on GitHub
https://github.com/spf13/hugo/issues/147#issuecomment-77132928.

+1 It would be awesome to be able to store assets next to the content files.
As I've outlined in File-Based CMS and Hugo as Static Site Generator it would be great to also allow .toml files as content instead of .md files.

@spf13 You stated the foundation is already in master.  Could we get an example of how to use it?
Out of all comments, @gima said it best: it is akward and the file system already provides me a way to organize with directories.  :+1:
My current blog, started way back in 2002, has been through 3 serious "technology/generator" changes.  In doing so, and preventing broken links, I have a wide swath of existing static content next to posts and articles.  Things like:
/blog/archives/2015-02-22-hello-world.aspx
/blog/archives/images/hello-world.jpg
/blog/2nd-overhaul-posts.html
/blog/images/newer-images-and-thumbnails-here/...
/current-version-at-root.html
/images/different-format-images

And I have quite a few videos, PDFs and such lined up next to their posts.
I liked Octopress exactly for this, as I was free to create any directory and/or file I wanted anywhere, and it would be copied over in that exact place.  I will admit that Hugo's forced separation approach irked me for some time - and still does.  I haven't launched my new overhaul yet because of these restrictions - I don't want to separate 1000s of posts and content.  Asking me to break up my site for a migration is a deal breaker.
Octopress (aka Jekyll) allowed you to create your own structure - and it would only process files by their extension type.  .html files are treated differently than .md files.  Have a new .adoc type?  No problem, copy a plugin (or write your own) to process that file extension.
^- Hey, someone had to mention Octopress/Jekyll already does this in this thread (and kind of trains you to do this).

@eduncan911 Yup, you're venting the very same frustrations that I have with Hugo, when I commented on this thread earlier: https://github.com/spf13/hugo/issues/147#issuecomment-71126819

Think we might be getting a little side tracked here, with the discussion on preprocessing files. That's a nice to have for non markdown files, but for a first cut, I will be quite happy in *.md files are the only ones that are processed, and everything else just gets copied as-is.
Creating a rails or docpad style asset pipeline based on multiple file extensions is a nice to have, but I think simply being able to put images referenced in a markdown file in the same folder as the markdown file will aid authoring in Hugo quite a lot.

Rather than whitelist a select number of file extensions which should get pre-processed, and error on everything else, I would much rather have a select number of extensions which get pre-processed, and have everything else simply pass through, by simply getting copied from the source folder to the destination folder.
I am currently using Hugo on a couple of static sites, but am still stuck on Docpad for my blog. I would very much like to switch that to Hugo too, but I am waiting for this issue to pan out, mainly due to me not wanting to copy images that are currently in the same folder as my markdown files into a separate parallel folder structure - it would simply be way too much tedious work!
@spf13 could we please get files extensions without a handler simply copied across?

Yes. I'll work on that this week.

"I'm 90% done with this today."
This was January. I understand it's not uncommon in software development that the last 10% is the toughest  - but is it possible to get a realistic estimate? Should we remove this from the v.0.14 milestone?

I'd really really like to see this feature make it into the next release,
can we please keep it in the milestone?
W: http://bguiz.com
On 30 April 2015 at 04:22, Bjørn Erik Pedersen<EMAIL_ADDRESS>wrote:

"I'm 90% done with this today."
This was January. I understand it's not uncommon in software development
that the last 10% is the toughest - but is it possible to get a realistic
estimate? Should we remove this from the v.0.14 milestone?
—
Reply to this email directly or view it on GitHub
https://github.com/spf13/hugo/issues/147#issuecomment-97531420.

v0.14 is long overdue and we cannot release something that isn't there, but I'm not doing the release, so I wouldn't know.

just ran into this problem. it's really annoying, particularly when using hugo as part of a pipeline for a bigger site.

Let me just add that the other day I was playing with Nikola which allows to use code like this:
/path-to/content/post/hello-world.rst
/path-to/content/post/hello-world/image.jpg

and the image is referenced within the post with:
.. thumbnail:: image.jpg
                  :alt: Some alt-text
                  :align: center
                  :scale: 60
                  etc.

Simple & clean way to keep images/assets along with posts...

Hello @Gour
Could you give us more details?
What version were you using? Latest from master?
Can you give/link to a full example?   I don't recognize :alt: :scale:.
Thanks!
On May 7, 2015 1:09 AM, "Gour"<EMAIL_ADDRESS>wrote:

Let me just add that the other day I was playing with Nikola
https://getnikola.com/ which allows to use code like this:
/path-to/content/post/hello-world.rst
/path-to/content/post/hello-world/image.jpg
and the image is referenced within the post with:
.. thumbnail:: image.jpg
:alt: Some alt-text
:align: center
:scale: 60
etc.
Simple & clean way to keep images/assets along with posts...
—
Reply to this email directly or view it on GitHub
https://github.com/spf13/hugo/issues/147#issuecomment-99720985.

@eduncan911 I am speaking how one can tie one's assets (e.g. images) close to the post in Nikola static-site-generator, iow. it's not about Hugo, but example how it could the problem of tying images close to the post be solved within Hugo.

Oh, I didn't catch that.  Yeah, Octopress/Jekyll does as well.
On Thu, May 7, 2015 at 3:14 PM, Gour<EMAIL_ADDRESS>wrote:

@eduncan911 https://github.com/eduncan911 I am speaking how one can tie
one's assets (e.g. images) close to the post in Nikola
https://getnikola.com/ static-site-generator, iow. it's not about
Hugo, but example how it could the problem of tying images close to the
post be solved within Hugo.
—
Reply to this email directly or view it on GitHub
https://github.com/spf13/hugo/issues/147#issuecomment-99986020.

This seems like a great place to hook in an image processing pipeline, which has two major stages I can think of:

Compression & Optimization
We could check for the availability of some commandline tools like optipng, jpegtran, etc and use them if they are available. If not, the user doesn't know the difference. The user could specify in their config file whether they want to enable processing.

Resizing & Cropping
As mentioned in #1014, it would be nice to provide this as an option. Off the top of my head, you could also use the config file in a similar fashion to WordPress to register specific file sizes that can be referenced elsewhere in the code. https://codex.wordpress.org/Function_Reference/add_image_size

This is obviously much more intensive than just generating html files, so it'd have to come with some sort of caching mechanism so it didn't have to copy and regenerate all the image files every single time.

The more I think about it, the more that seems a little intense for Hugo. While it would be super nice if it could fit the workflow, it may be more suited to a CI environment to go through and build all the right sizes on deployment. The only thing you lose by doing that is not being able to set the right width / height attributes inside your html tags.

This is not to address only images next to md files, but all file types.
We all agree that Hugo:

should not try to process files it doesn't know about in the /content
directory.
move all files it finds in /content over to that same directory in the
generated site, keeping the exact same structure.

E.g., side-by-side files:
/content/post/summer-fun/what-i-did-last-summer.md
/content/post/summer-fun/jet-skiing.png
/content/post/summer-fun/jet-skiing.mkv
/content/post/summer-fun/jet-ski-for-sale.zip
On Thu, May 14, 2015 at 8:19 PM, Derek Perkins<EMAIL_ADDRESS>wrote:

The more I think about it, the more that seems a little intense for Hugo.
While it would be super nice if it could fit the workflow, it may be more
suited to a CI environment to go through and build all the right sizes on
deployment. The only thing you lose by doing that is not being able to set
the right width / height attributes inside your html tags.
—
Reply to this email directly or view it on GitHub
https://github.com/spf13/hugo/issues/147#issuecomment-102207530.

To everyone. I committed a generic file handler that simply places the files in the same path in the destination directory. This will enable people to place images and other files along side their content. There's still a bit more to do around this, but the fundamental issue / request in these 3 tickets is solved. It does need a bit of testing so I'd love everyone to check out head and play with it.

Awesome Steve!
Will let know in the next few days!
-E
On May 20, 2015 7:06 PM, "Steve Francia"<EMAIL_ADDRESS>wrote:

To everyone. I committed a generic file handler that simply places the
files in the same path in the destination directory. This will enable
people to place images and other files along side their content. There's
still a bit more to do around this, but the fundamental issue / request in
these 3 tickets is solved. It does need a bit of testing so I'd love
everyone to check out head and play with it.
—
Reply to this email directly or view it on GitHub
https://github.com/spf13/hugo/issues/147#issuecomment-104067783.

Works for me.

Thank you very much for this change.

Running into an issue when I have HTML files (specifically reveal.js stuff) along with markdown files:
ERROR: 2015/05/21 Error rendering site: Error(s) rendering pages: template: __research/search/presentation/bower_components/reveal.js/plugin/notes-server/notes.html:188: function "socketId" not defined
Available templates:
ERROR: 2015/05/21 	__research/search/presentation/bower_components/reveal.js/test/examples/embedded-media.html
ERROR: 2015/05/21 	__research/search/presentation/bower_components/reveal.js/test/test-markdown-element-attributes.html
ERROR: 2015/05/21 	_internal/shortcodes/test.html
ERROR: 2015/05/21 	partials/header.html
ERROR: 2015/05/21 	partials/photos.html
ERROR: 2015/05/21 	__research/search/presentation/bower_components/reveal.js/test/examples/barebones.html
ERROR: 2015/05/21 	__research/search/presentation/bower_components/reveal.js/plugin/notes/notes.html
ERROR: 2015/05/21
ERROR: 2015/05/21 	_internal/shortcodes/ref.html
ERROR: 2015/05/21 	_internal/_default/sitemap.xml
ERROR: 2015/05/21 	partials/navbar.html
ERROR: 2015/05/21 	_internal/google_news.html
ERROR: 2015/05/21 	404.html
ERROR: 2015/05/21 	partials/article-contents.html
ERROR: 2015/05/21 	partials/github.html
ERROR: 2015/05/21 	_internal/shortcodes/highlight.html
ERROR: 2015/05/21 	_internal/_default/rss.xml
ERROR: 2015/05/21 	_internal/disqus.html
ERROR: 2015/05/21 	_internal/twitter_cards.html
ERROR: 2015/05/21 	__research/search/presentation/bower_components/reveal.js/plugin/markdown/example.html
ERROR: 2015/05/21 	__research/search/presentation/bower_components/reveal.js/test/examples/slide-backgrounds.html
ERROR: 2015/05/21 	_internal/pagination.html
ERROR: 2015/05/21 	_default/single.html
ERROR: 2015/05/21 	_internal/shortcodes/relref.html
ERROR: 2015/05/21 	_internal/shortcodes/figure.html
ERROR: 2015/05/21 	__research/search/presentation/bower_components/reveal.js/test/test-pdf.html
ERROR: 2015/05/21 	__research/search/presentation/bower_components/reveal.js/plugin/notes-server/notes.html
ERROR: 2015/05/21 	__research/search/presentation/bower_components/reveal.js/test/test-markdown-slide-attributes.html
ERROR: 2015/05/21 	__research/search/presentation/bower_components/reveal.js/test/test.html
ERROR: 2015/05/21 	__research/search/presentation/index.html
ERROR: 2015/05/21 	_internal/schema.html
ERROR: 2015/05/21 	partials/article-summary.html
ERROR: 2015/05/21 	partials/footer.html
ERROR: 2015/05/21 	__research/search/presentation/bower_components/reveal.js/index.html
ERROR: 2015/05/21 	_internal/opengraph.html
ERROR: 2015/05/21 	_default/list.html
ERROR: 2015/05/21 	__research/search/presentation/bower_components/reveal.js/test/examples/math.html
ERROR: 2015/05/21 	__research/search/presentation/bower_components/reveal.js/test/test-markdown.html
CRITICAL: 2015/05/21 Error(s) rendering pages: template: __research/search/presentation/bower_components/reveal.js/plugin/notes-server/notes.html:188: function "socketId" not defined

It appears that Hugo tries to interpret them as templates.

Html files are interpreted as content files and will be parsed as such when in the content directory.
If you would like them to not be parsed then they need to be in the static directory.
This error seems to indicate that they are not in the content directory but in layouts as that is the only place where templates are looked for. Can you provide more complete paths for these files?
Best,
Steve
--
Steve Francia
<EMAIL_ADDRESS>Docker Inc
http://spf13.com

On May 21, 2015 at 12:56:46 AM, Alex Yatskov<EMAIL_ADDRESS>wrote:
Running into an issue when I have HTML files (specifically reveal.js stuff) along with markdown files:
ERROR: 2015/05/21 Error rendering site: Error(s) rendering pages: template: __research/search/presentation/bower_components/reveal.js/plugin/notes-server/notes.html:188: function "socketId" not defined
Available templates:
ERROR: 2015/05/21   __research/search/presentation/bower_components/reveal.js/test/examples/embedded-media.html
ERROR: 2015/05/21   __research/search/presentation/bower_components/reveal.js/test/test-markdown-element-attributes.html
ERROR: 2015/05/21   _internal/shortcodes/test.html
ERROR: 2015/05/21   partials/header.html
ERROR: 2015/05/21   partials/photos.html
ERROR: 2015/05/21   __research/search/presentation/bower_components/reveal.js/test/examples/barebones.html
ERROR: 2015/05/21   __research/search/presentation/bower_components/reveal.js/plugin/notes/notes.html
ERROR: 2015/05/21
ERROR: 2015/05/21   _internal/shortcodes/ref.html
ERROR: 2015/05/21   _internal/_default/sitemap.xml
ERROR: 2015/05/21   partials/navbar.html
ERROR: 2015/05/21   _internal/google_news.html
ERROR: 2015/05/21   404.html
ERROR: 2015/05/21   partials/article-contents.html
ERROR: 2015/05/21   partials/github.html
ERROR: 2015/05/21   _internal/shortcodes/highlight.html
ERROR: 2015/05/21   _internal/_default/rss.xml
ERROR: 2015/05/21   _internal/disqus.html
ERROR: 2015/05/21   _internal/twitter_cards.html
ERROR: 2015/05/21   __research/search/presentation/bower_components/reveal.js/plugin/markdown/example.html
ERROR: 2015/05/21   __research/search/presentation/bower_components/reveal.js/test/examples/slide-backgrounds.html
ERROR: 2015/05/21   _internal/pagination.html
ERROR: 2015/05/21   _default/single.html
ERROR: 2015/05/21   _internal/shortcodes/relref.html
ERROR: 2015/05/21   _internal/shortcodes/figure.html
ERROR: 2015/05/21   __research/search/presentation/bower_components/reveal.js/test/test-pdf.html
ERROR: 2015/05/21   __research/search/presentation/bower_components/reveal.js/plugin/notes-server/notes.html
ERROR: 2015/05/21   __research/search/presentation/bower_components/reveal.js/test/test-markdown-slide-attributes.html
ERROR: 2015/05/21   __research/search/presentation/bower_components/reveal.js/test/test.html
ERROR: 2015/05/21   __research/search/presentation/index.html
ERROR: 2015/05/21   _internal/schema.html
ERROR: 2015/05/21   partials/article-summary.html
ERROR: 2015/05/21   partials/footer.html
ERROR: 2015/05/21   __research/search/presentation/bower_components/reveal.js/index.html
ERROR: 2015/05/21   _internal/opengraph.html
ERROR: 2015/05/21   _default/list.html
ERROR: 2015/05/21   __research/search/presentation/bower_components/reveal.js/test/examples/math.html
ERROR: 2015/05/21   __research/search/presentation/bower_components/reveal.js/test/test-markdown.html
CRITICAL: 2015/05/21 Error(s) rendering pages: template: __research/search/presentation/bower_components/reveal.js/plugin/notes-server/notes.html:188: function "socketId" not defined
It appears that Hugo tries to interpret them as templates.
—
Reply to this email directly or view it on GitHub.

I ended up moving the stuff out of content into static and it's all groovy now. I was just under the impression that with this new change, when processing the content directory, Hugo would convert markdown files to HTML, and pass everything else through without processing it (I thought that the layout directory is the only place that would be processed for templates). I'll post a repro in a few.

The intent of /content is things are in there to be processed. This change does permit files to live alongside the content and if a dedicated handler isn't found it will just copy them over. This isn't the safest thing to do as in the future a handler may be defined for the file type and change the behavior. For instance, we could (and probably will) add a handler that does some automatic optimization to images... a generally but not universally desirable feature. If you want the images untouched...
The intent of /static is that things in there are not to be processed and will be copied over exactly as they are.

It's also the case that hugo supports html, markdown, asciidoc and rst currently as content files.

There's the list... Was searching the docs for what is currently processes.
Maybe someone with a little more time can update the docs and submit a pull
request.  (FYI, the Hugo docs is in github as well, generated by Hugo
itself - by Steve I am guessing).
On May 21, 2015 8:30 AM, "Steve Francia"<EMAIL_ADDRESS>wrote:

It's also the case that hugo supports html, markdown, asciidoc and rst
currently as content files.
—
Reply to this email directly or view it on GitHub
https://github.com/spf13/hugo/issues/147#issuecomment-104254811.

In case there is interest, I put up the website that illustrates the issue I was having here (5mb download):
http://foosoft.net/dl/hugo-repro.tar.gz

Can you make hugo ignore desktop.ini files? Google Drive puts that file in there if your using Google Drive sync on Windows. So you have to manually delete all the desktop.ini files to get Hugo to work.

@zachdyer ini-files should be covered by fc946ded29149443e21587c7f513d4550dc67f39 . Have you tested this with Hugo 0.14?

Actually no but good job dude yes!
On Wed, May 27, 2015 at 3:48 PM, Bjørn Erik Pedersen <
<EMAIL_ADDRESS>wrote:

@zachdyer https://github.com/zachdyer ini-files should be covered by
fc946de
https://github.com/spf13/hugo/commit/fc946ded29149443e21587c7f513d4550dc67f39
. Have you tested this with Hugo 0.14?
—
Reply to this email directly or view it on GitHub
https://github.com/spf13/hugo/issues/147#issuecomment-106069347.

--
[image: ZachDyerDesignHeaderGoogle.png]
Zach Dyer
1471 W South St.
Ozark, MO 65721
417.582.5445
www.zachdyerdesign.com
hosting.zachdyerdesign.com
Breach of confidentiality & accidental breach of confidentiality
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system. If you are not the intended recipient
you are notified that disclosing, copying, distributing or taking any
action in reliance on the contents of this information is strictly
prohibited.

Does not work with permalinks.
Files are laid out in a directory path matching the pre-permalink URL, thus effecively ignoring permalinks completely.

Interesting discussion. I am in the process of converting a WP blog to Hugo, and my last big hurdles are image gallery handling and ATOM support. To be a world-class platform, Hugo needs fully integrated media management.
I am experimenting with a different approach than what was suggested above: treat JPEG files in /content as an external media type (the same way asciidoc, mmark, ReST and HTML are treated), copy the file as-is, but process its metadata (EXIF/IPTC/XMP/ICC) as implied front matter, and provide templates with functions that can perform standard image operations like thumbnail generation, resizing, watermarking, cropping, and so on.
This would allow templates to become full-fledged gallery generators, e.g. automatically generate a photoblog or galleries from photos dropped into /content/photos/ by Lightroom et al. This seems to me like more powerful and extensible, and aligned with the design of Hugo (and the limitations of Go in terms of lacking dynamic linking or similar extensibility mechanisms to implement plugins).
I'll share my work if it turns out to be successful. Happy Thanksgiving!


Script not working on Windows

When executing python -m makefile_creator on Windows command line the script finishes without console output and doesn't create the makefiles.

Closed with 531ccd0e4757124c731e2df2530dfb9f74fd264b


Host compodocs on github pages

A request came from the community to host the output of compodocs somewhere public. Having an overview of all available modules/services (e.g. CurrentProductService) without having to search through the code is great and could help in general to get a better overview of the whole architecture
Let's host it in our github pages for spa.

just publish every release (automate? up to Louis) (make sure this is in our list of release steps)

To see the final result, you can look at :

https://github.com/LTiger14/cloud-commerce-spartacus-storefront/tree/gh-pages
&
https://ltiger14.github.io/cloud-commerce-spartacus-storefront/index.html

PR
https://github.com/SAP/cloud-commerce-spartacus-storefront/pull/4847


Failed test while building

Hi,
Running mvn package yields this:
Failed tests:   clean(webapp.runner.launch.TomcatBaseDirResolutionTest): expected [true] but found [false]
Any idea how to solve it?

What OS are you using?

Windows

@aghasemi i think this should be fixed now. please let me know if it still occurs.


Parse parenthesized where-clause

As seen in this test case.
where U: (FnOnce(T) -> V) + 'static

Fixed in d9faf441387895f1b36710e20ac104c16e0fe296.


Fixed typo of type in user docs

Changed vec3x4 to mat3x4

 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.

Thank you for catching the typo!


Activate csrf token and validations

This PR activates csrf tokens and tests for them. It has a small fix for the adhoc query web page. Testing relies on lxml but is only added for development.

If required I can clean up the commits, I seem to have squashed it a bit awkward.


⚠ ClamAV has degraded performance

In 51b69c9, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 69 ms

Resolved: ClamAV performance has improved in 2311a64.


Meta Report Issue

It would be nice to have these static structure reports:

[ ] charger states.
[x] door states. Related issue #254
[ ] error / warning messages
[x] lift states. Related issue #260
[ ] negotiations succeed/failed
[x] robot states. Related issue #253
[ ] robot motion plans (great schedule dumps)
[ ] robot actions (sounds, bays open/close, …). Related issue #257
[ ] user actions. Related issue #258
[x] tasks issued/completed/failed. Related issue #259
[ ] workcell states. Relared issue #256
[x] user Authentication (logins / logouts / login-failures) #261

This is not a closed list, more reports can be added.

Reporting removed via https://github.com/open-rmf/rmf-web/pull/628


Fix Result component

This attempt to fix some errors on Result components.

Many iteration renders without key for children
Multiple wrong prop types

⚠  Although this PR already solve them, I'm not comfortable with what we have now, specially the JSON.stringify(props) for keys. I'm opening this to receive suggestions on how to improve it.
https://user-images.githubusercontent.com/28108272/130797069-137ca75e-23b7-4722-8d78-0e167c174601.mp4

Why don't use index as key instead JSON.stringify(props)?

Why don't use index as key instead JSON.stringify(props)?

no-array-index-key

Why don't use index as key instead JSON.stringify(props)?

no-array-index-key

no-array-index-key is a good practice, is not wrong. I think is better and more performative than JSON.stringify(props). array-index-key is good to avoid when you remove itens from list, I think is not the case, right?

Why don't use index as key instead JSON.stringify(props)?

no-array-index-key

no-array-index-key is a good practice, is not wrong. I think is better and more performative than JSON.stringify(props). array-index-key is good to avoid when you remove itens from list, I think is not the case, right?

Makes sense. I assume I'm not sure because I had no idea of how is this component, I was just looking at this code. But it seems that its usage really don't expect to change these items


doc(trait): sourceless Integrations

Release Note
doc(trait): sourceless Integrations

Thanks @mertdotcc for the initial inception of this work ;)


WebAssembly module is (sometimes) included in initial chunk.

Bug report

What is the current behavior?
When including a wasm module with const wasmPromise =<EMAIL_ADDRESS>the build sometimes fails without any other changes being done to the code or configuration (like 1 in 15 times). Otherwise it works as expected, wasm module is not included in initial chunk and is loaded asynchronously when requested.
I have even tried wrapping the import in an additional function as suggested, but the behaviour stays the same.
export function import_wasm (): Promise<any> {
    return<EMAIL_ADDRESS>}

The full error is:
WebAssembly module is included in initial chunk.
This is not allowed, because WebAssembly download and compilation must happen asynchronous.
Add an async splitpoint (i. e. import()) somewhere between your entrypoint and the WebAssembly module:
multi ./src/boot.ts --> ./src/boot.ts --> ./src/store/index.ts --> ./src/store/modules/builder/index.ts --> ./src/store/modules/builder/actions.ts --> ./src/wasmWrapper.ts --> ./src/wasm/import_wasm.ts --> ./src/wasm/module.wasm

What is the expected behavior?
Webpack build is deterministic.
Other relevant information:
webpack version:  4.46.0
Node.js version:  7.7.6
Operating System: Docker image based on debian:stretch
Additional tools: Webpack config as generated by @vue/cli 4.5.11
Full package.json:
https://gist.github.com/jkosir/3d83889c63244184d38ead44084d7188

Fixed in webpack v5, please consider to update, webpack v4 only accept security fixes, sorry, also you can ask vue cli about webpack v5 compatibility


Adding Hub Collaborators

My username is @austinmurry. Please @ebeshero add me as a collaborator to this Hub

@Yuying-Jin @austinmurry You have been sent two invitations:

to the newtfire GitHub organization
to the introDH-Hub.

You will need to accept the invitations to join!


Add Promise.withResolvers Polyfill

What
Missing Promise.withResolvers
Details
react-pdf recently upgraded and no longer includes a polyfill for this API, which is now baseline available in 2024.
We've got some older safari clients breaking.
Happy to make a PR:
ref: CoreJS Polyfill
Code roughly:
if (typeof Promise.withResolvers === 'undefined') {
  window.Promise.withResolvers = function () {
    let resolve, reject;
    const promise = new Promise((res, rej) => {
      resolve = res;
      reject = rej;
    });
    return { promise, resolve, reject };
  }
}

Your suggested polyfill isn't compliant as it doesn't handle subclassing:

Promise.withResolvers() is generic and supports subclassing, which means it can be called on subclasses of Promise, and the result will contain a promise of the subclass type.

There is a corejs example I provided if you need help implementing to spec. This is an issue report not a PR or an implementation plan.
On Thu, Jul 18, 2024, at 8:52 PM, Daniel Lo Nigro wrote:

Your suggested polyfill isn't compliant as it doesn't handle subclassing:

Promise.withResolvers() is generic and supports subclassing, which means it can be called on subclasses of Promise, and the result will contain a promise of the subclass type.

—
Reply to this email directly, view it on GitHub https://github.com/polyfillpolyfill/polyfill-service/issues/2886#issuecomment-2237876511, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATQYQ4CLUXNF52B4WB2QTLZNBWNBAVCNFSM6AAAAABJJFX2CKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZXHA3TMNJRGE.
You are receiving this because you authored the thread.Message ID: @.***>


Add an option to allow the SDK to process echo messages

Why are we doing this?
Two enable two bots one page for a new conversation logger, you need the ability to make a bot that can listen to echo messages. Otherwise, the observer bot can only observe humans.
Did you document your work?
README has the new constructor option and some cleanup.
How can someone test these changes?
Steps to manually verify the change:
Just unit tests. After this, I can open up the logger as an example bot. This requires an elaborate setup to manually verify.
What possible risks or adverse effects are there?

none

What are the follow-up tasks?

release a new version

Are there any known issues?

if you use npm v2, the peer dependencies will fail. Don't use npm 2. I thought about explicitly putting it in the package.json engines declaration but at this point, no one should run into this.

Did the test coverage decrease?
stays the same. some improvements to the tests:

messenger no longer leaks state
document an assertion that double checks that your listener fired or not. If you have assertions in an event listener but the even never fires, you could get a passing tests that should have failed.

the main question is... do we need this code? From the README:

To enable this advanced feature and tell your bot to process echo messages, you have to enable message_echoes in your Messenger webhook and set this to false

It's already an opt-in feature. Do we need a double opt-in? We could just remove the if check and just document the quirks discovered.

closed in favor of #37


feat: add new client function

feat: The branch here is adding compatibility for csphere and proxmox. A load balancing solution for vsphere and proxmox needs to communicate with API using a specific, non jwt, token.


Labels reconfiguration failed for daemon if specified in the command line and daemon.json

Output of docker version:
Client:
 Version:      1.12.0-rc3
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   91e29e8
 Built:        Sat Jul  2 00:17:11 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.0-rc3
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   91e29e8
 Built:        Sat Jul  2 00:17:11 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 1.12.0-rc3
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 0
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: overlay bridge host null
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.14-boot2docker
Operating System: Boot2Docker 1.12.0-rc3 (TCL 7.1); HEAD : 8d9ee9f - Sat Jul  2 05:02:44 UTC 2016
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 995.9 MiB
Name: test
ID: HU6Z:T5PF:ZCA6:LCTC:64C6:DCXZ:PZIK:MKWX:2ICG:ERIT:CX2W:CEH2
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 13
 Goroutines: 24
 System Time: 2016-07-04T12:42:44.157142413Z
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):
Docker for Mac Version 1.12.0-rc2-beta17 (build: 9779)
Steps to reproduce the issue:

Create a new machine with docker-machine -d virtual box test
Edit /etc/docker/daemon.json on the machine and add {"labels":["mylabel=1"]}
Restart daemon with SIGHUP

Describe the results you received:
Labels from daemon.json are ignored.
Docker log contains the following message:
time="2016-07-04T12:31:43.356902144Z" level=info msg="Got signal to reload configuration, reloading from: /etc/docker/daemon.json"
time="2016-07-04T12:31:43.357524115Z" level=error msg="the following directives are specified both as a flag and in the configuration file: labels: (from flag: [provider=virtualbox], from file: [mylabel=1])"

ps aux | grep docker
root      2653  0.0  3.8<PHONE_NUMBER>2 ?        Sl   12:30   0:00 dockerd -D -g /var/lib/docker -H unix:// -H tcp://<IP_ADDRESS>:2376 --label provider=virtualbox --tlsverify --tlscacert=/var/lib/boot2docker/ca.pem --tlscert=/var/lib/boot2docker/server.pem --tlskey=/var/lib/boot2docker/server-key.pem -s aufs
...

No labels flag is specified in the command line only label but the message is still generated.
Describe the results you expected:
Labels must be merged. In case of conflict, labels from config file must be prioritized.

From documentation:

The options set in the configuration file must not conflict with options set via flags. The docker daemon fails to start if an option is duplicated between the file and the flags, regardless their value. We do this to avoid silently ignore changes introduced in configuration reloads. For example, the daemon fails to start if you set daemon labels in the configuration file and also set daemon labels via the --label flag. Options that are not present in the file are ignored when the daemon starts.

I think the solution would be that docker-machine provision what can be provisionned using the config file (for labels for example).

As this is explicitly documented as being the expected behaviour I am going to close the issue, but feel free to open an issue on docker/machine as @vdemeester suggested.


Website time axis

User may need to select time scale for data to be displayed on CTD website, as well as starting date.
For example, sensor may send data every 1 minute, in which case current website shows about 10 mins of data; however, user may want to see 1 hour averages over 10 hour period, or 1 day averages over longer period. It would be useful to add feature to website allowing user to select time period and starting date.

Tested scaling time window changing for online data - js changes only. Started implementing changes for historical data on js and reading from blob on backend.

Working on js part.

Stale


Status#changed? is case-sensitive despite git config

Subject of the issue
When the git repo is configured to track files case-insensitively and a file name has a different letter case, Status#changed? will not report if the file has been modified.
Your environment

git (1.11.0)
ruby 2.7.3

Steps to reproduce

init a new git repo
(have default config core.ignoreCase true)
commit FILE
rename to file
edit file
in ruby-git, call Status#changed?("file")

Expected behaviour
expected to compare tracked file case-insensitively with given filename (ie "FILE".downcase == "file".downcase)
Actual behaviour
returns false

your file system coule be case insensitive
wiki: "In filesystems in Unix-like systems, filenames are usually case-sensitive (there can be separate readme.txt and Readme.txt files in the same directory). MacOS is somewhat unusual in that, by default, it uses HFS+ and APFS in a case-insensitive"
see https://github.com/pinglamb/changelog-rb/issues/12#issuecomment-1165073855 for demo
so issue might not on the gem 🤣

I believe https://github.com/ruby-git/ruby-git/pull/724 will fix this (and the matching issue for added?, deleted?, and untracked?).
Note that the reproduction instructions should also mention that it must be performed on a system with a case insensitive FS - git doesn't actually support setting core.ignoreCase when the filesystem is case-sensitive; you'll get confusing results from both git and this gem in that context.


Fallback in "Range" for pagination requests

implement equivalent changes as initially thought by @teizenman
Closes #82

Codecov Report

Merging #84 into master will decrease coverage by 0.17%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #84      +/-   ##
==========================================
- Coverage   94.89%   94.72%   -0.18%
==========================================
  Files           8        8
  Lines        1784     1686      -98
==========================================
- Hits         1693     1597      -96
+ Misses         91       89       -2

Impacted Files
Coverage Δ

taxii2client/test/test_client_v20.py
100.00% <100.00%> (ø)

taxii2client/v20/__init__.py
89.91% <100.00%> (-0.23%)
:arrow_down:

taxii2client/v21/__init__.py
90.85% <0.00%> (-0.70%)
:arrow_down:

taxii2client/test/test_client_v21.py
100.00% <0.00%> (ø)

taxii2client/common.py
81.69% <0.00%> (+0.70%)
: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 6a3f4f0...39c8cba. Read the comment docs.


Merge from branch master of laravel/installer

Merged as of https://github.com/GerardBalaoro/laravel-installer/commit/a219e51859cff88ddef4277f94b86e7a852a958a


update readme link to prepend tip to fix Page Not Found

[ ] I added CHANGELOG entry for this change. (not sure which section to put under Fixed or Changed?)
[ ] Change is not relevant to the end user.

Changes

trying to fix the incorrect readme links that showing Page Not Found which were changed by this PR https://github.com/thanos-io/thanos/pull/2802/files#diff-6b3df26d750e09528185b365bbd99a76R72-R77 as shown below

Verification

click links from github readme

CI is still failing though, do you mind running make docs and committing changes
?

I will do that for you if you don't mind (:

Ahh, thx, please help me, make docs acting weird to me, it delete t character at the end of each word.

Ahh, thx, please help me, make docs acting weird to me, it delete t character at the end of each word.

@bwplotka do you by any chance know what happen for failed CI checks? seems besides docs one, linter and end-to-end tests also failed.

Yea I am on it - unlucky day for CI ;p

Ok let's disable Liche we need long term fix now :/ Let's do this in separate PR and merge this on green. At least README links will be working

hope google will crawl the latest webpages update pagerank soon since they link to the old ones


Feature: Project level kubernetes service account

What kind of request is this (question/bug/enhancement/feature request):
feature request
Desired result
Ability to create a service account that manages a project and it's resources as opposed to cluster or just a namespace.

Create a role that allow a service account to create a number of namespaces within a single project, in other word like project-admin (cluster-admin which is pre-defined by kubernetes)

gz#4574

I second this idea.  I've been toying around with how to create service accounts in rancher 2.6 and it seems really wonky


Support for Subscription on deleted resources

https://github.com/medplum/medplum/issues/2194

coverage: 94.388% (+0.006%) from 94.382% when pulling d441a80c2e039812eace4d3625a6e1a906348230 on james-webhook-delete into 35b7796cb248eaf2274b4cd168ac1ee5d29176c5 on main.