How to get HRESULT of Win32::Networking::ActiveDirectory::IDirectorySearch::GetNextRow?

I apologize if I'm asking a silly question.
I need the HRESULT to check whether more rows are available to search ActiveDirectory using Win32::Networking::ActiveDirectory::IDirectorySearch.

C++ example
ADSI Error Codes

How can I get actual HRESULT from Result<()>?
It seems executing GetNextRow() always returns Ok(()) even when no more rows.
https://microsoft.github.io/windows-docs-rs/doc/windows/Win32/Networking/ActiveDirectory/struct.IDirectorySearch.html#method.GetNextRow

This is the result of an issue with the Win32 metadata, that fails to contain enough information for windows-rs to provide a useful binding. The issue was initially reported here. Since then some API's (but not all) have received the proposed AlternateSuccessCodes attribute (such as DoDragDrop). Unfortunately, IDirectorySearch::GetNextRow is not one of them.
As I understand it, the AlternateSuccessCodes attribute is in the process of getting replaced with DllImport.PreserveSig (see this PR for reference). It doesn't look like the Win32 metadata team is planning to invest into the temporary AlternateSuccessCodes solution.
The maintainers of windows-rs may want to bring this to the attention of the Win32 metadata team, and possibly prioritize having the issue resolved. At this time, this specific API is rendered unusable.

Thank you for your explanation! I'll wait for the progress of win32metadata and windows-rs.:+1:
💭 (If it takes a long time, I wish win32metadata teams accept AlternateSuccessCodes solution first...)

Hi. I am blocked by issue. You can accept my solution AlternateSuccessCodes for now and later do solution better? Sorry for impatience I can not finish my project. Thank you for work and windows-rs. 👍

With 0.29.0, I can now get HRESULT as return type. I have confirmed that the actual implementation and documentation have been fixed.


amqp_ascoltatore ERROR ECONNREFUSED <IP_ADDRESS>:5672

I tried to launch the MQTT Server over amqp instead of MangoDB but I got this error :
events.js:165
throw er; // Unhandled 'error' event
^
Error: connect ECONNREFUSED <IP_ADDRESS>:5672
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1170:14)
Emitted 'error' event at:
at Connection. (C:\Users\Soal Abdeldjallil\Desktop\Mqtt-Server\node_modules\mosca\node_modules\ascoltatori\lib\amqp_ascoltatore.js:69:12)
at Connection.emit (events.js:185:15)
at Socket.emit (events.js:180:13)
at emitErrorNT (internal/streams/destroy.js:64:8)
at process._tickCallback (internal/process/next_tick.js:114:19)

please share the code base where you have configured it.

I solved the problem by using only websockets and i disabled the persistance and the backend module.
thank you so much

okay good luck :)


Cleanup() throws IOException

maybe some file handle  not closed properly?
edit: Exception translates to

IOException: The process cannot access the file 'file path' because it is being used by another process

fixed in theory in last release on contrib page 1.0.2. before archive was not released manually only with GC so if .vpm folder is deleted before that you get this error. now archives are released manually.


azure-servicebus samples Issues

azure-servicebus script:
sample_code_servicebus.py
sample_code_servicebus_async.py

Suggestion:
fully_qualified_namespace = os.environ['SERVICE_BUS_NAMESPACE']

Thanks @v-xuto!  cc: @KieranBrantnerMagee

thanks @v-xuto , I have applied your suggestions in my PR and get that one merged.
https://github.com/Azure/azure-sdk-for-python/pull/11047


changes static example topic to dynamic example topic

"latest AI trends" should be "latest {topic} trends".

Strange, I'm getting lint and whitespace problems on things I didn't touch.


Native Modules go unresolved

This package is unable to resolve native dependencies when they exist in a parent node_modules folder.
Currently, I have to make a copy of them using something like find-up in a postinstall script to properly run my executable in my consumer app.

Hey @calebboyd!
Thanks for the response.
That makes total sense, though I was really hoping to avoid a bundler. 😆
I saw a few issues in the nexe repo related to this.
You might want to put an example in the readme in that to use additional binaries section.
I'd be happy to add it myself.


Duplicate messages ignored by time

Hey @davidmckenzie
Just wondering if you could please add an option to ignore messages if it is within 20 (maybe have this user selectable?) seconds of the same message to the same address [as well as the current option to ignore if received in the last 10 messages].

I like that - user selectable time limit for the duplicate message filtering. Would be similar to how PDW works :)


I would like to have an example for Reactome for the new JSON schema

Provide an example evidence from Reactome of how it looks with the current JSON schema and how it should look like when they use the new schema

Example of the new evidence. A few disclaimers:

Based on iter13 - 20.11 data
Evidences are selected "randomly" from high-scoring evidence based on the next algorithm
Some fields here won't be necessary in the input evidence (e.g. id).
Desired further enhancements on the evidence, have not yet been included here
Overall, this evidence needs to be reviewed manually and some changes will be added

w2 = Window.partitionBy("sourceId").orderBy(col("score").desc())
out = df.withColumn("row", row_number().over(w2)).filter(col("row") == 1).drop("row")
out.write.json("/Users/ochoa/exampleEvidence.json")

For the case of reactome, there are 2 subtypes of evidence, that might be good flagging:
This evidence contains a mutation
{
  "diseaseFromSourceId": "EFO_1000647",
  "variantAminoacidDescriptions": [
    "L-leucine 389 replaced with L-proline"
  ],
  "targetModulation": "loss_of_function",
  "pathwayId": "R-HSA-5619098",
  "literature": [
    "9354798",
    "11044475",
    "10987651"
  ],
  "targetId": "ENSG00000163581",
  "targetFromSourceId": "P11168",
  "datasourceId": "reactome",
  "reactionId": "R-HSA-5638222",
  "datatypeId": "affected_pathway",
  "diseaseFromSource": "renal tubular transport disease",
  "pathwayName": "Defective SLC2A2 causes Fanconi-Bickel syndrome (FBS)",
  "diseaseId": "EFO_1000647",
  "id": "007703524f6f89940e179c786ea3a3a152ec588b",
  "score": 1,
  "sourceId": "reactome"
}

This evidence contain an altered expression:
{
  "diseaseFromSourceId": "EFO_0007328",
  "variantAminoacidDescriptions": [],
  "targetModulation": "up_or_down",
  "pathwayId": "R-HSA-192823",
  "literature": [
    "16630668"
  ],
  "targetId": "ENSG00000134419",
  "targetFromSourceId": "P62244",
  "datasourceId": "reactome",
  "reactionId": "R-HSA-192841",
  "datatypeId": "affected_pathway",
  "diseaseFromSource": "influenza",
  "pathwayName": "Viral mRNA Translation",
  "diseaseId": "EFO_0007328",
  "id": "0bb00f5495faa6ca7d10698e0703f0eb725d229d",
  "score": 1,
  "sourceId": "reactome"
}

@ktsirigos you can try to find the same evidence in the old pipeline. (ask @AsierGonzalez if you don't know how to do it)
@ireneisdoomed, we should iterate in the desired evidence further.

Example of the new evidence. A few disclaimers:

Based on iter13 - 20.11 data
Evidences are selected "randomly" from high-scoring evidence based on the next algorithm
Some fields here won't be necessary in the input evidence (e.g. id).
Desired further enhancements on the evidence, have not yet been included here
Overall, this evidence needs to be reviewed manually and some changes will be added

w2 = Window.partitionBy("sourceId").orderBy(col("score").desc())
out = df.withColumn("row", row_number().over(w2)).filter(col("row") == 1).drop("row")
out.write.json("/Users/ochoa/exampleEvidence.json")

For the case of reactome, there are 2 subtypes of evidence, that might be good flagging:
This evidence contains a mutation
{
  "diseaseFromSourceId": "EFO_1000647",
  "variantAminoacidDescriptions": [
    "L-leucine 389 replaced with L-proline"
  ],
  "targetModulation": "loss_of_function",
  "pathwayId": "R-HSA-5619098",
  "literature": [
    "9354798",
    "11044475",
    "10987651"
  ],
  "targetId": "ENSG00000163581",
  "targetFromSourceId": "P11168",
  "datasourceId": "reactome",
  "reactionId": "R-HSA-5638222",
  "datatypeId": "affected_pathway",
  "diseaseFromSource": "renal tubular transport disease",
  "pathwayName": "Defective SLC2A2 causes Fanconi-Bickel syndrome (FBS)",
  "diseaseId": "EFO_1000647",
  "id": "007703524f6f89940e179c786ea3a3a152ec588b",
  "score": 1,
  "sourceId": "reactome"
}

This evidence contain an altered expression:
{
  "diseaseFromSourceId": "EFO_0007328",
  "variantAminoacidDescriptions": [],
  "targetModulation": "up_or_down",
  "pathwayId": "R-HSA-192823",
  "literature": [
    "16630668"
  ],
  "targetId": "ENSG00000134419",
  "targetFromSourceId": "P62244",
  "datasourceId": "reactome",
  "reactionId": "R-HSA-192841",
  "datatypeId": "affected_pathway",
  "diseaseFromSource": "influenza",
  "pathwayName": "Viral mRNA Translation",
  "diseaseId": "EFO_0007328",
  "id": "0bb00f5495faa6ca7d10698e0703f0eb725d229d",
  "score": 1,
  "sourceId": "reactome"
}

@ktsirigos you can try to find the same evidence in the old pipeline. (ask @AsierGonzalez if you don't know how to do it)
@ireneisdoomed, we should iterate in the desired evidence further.

This is the original evidence in the 20.11 Reactome file that contains the mutation:
$ jq-1.6 'select(.unique_association_fields.mutations == "[L-leucine 389 replaced with L-proline]" and .unique_association_fields.target_id == "http://www.identifier.org/uniprot/P11168" and .unique_association_fields.reaction_id == "http://reactome.org/PathwayBrowser/#/R-HSA-5638222" and .unique_association_fields.disease_id == "http://www.ebi.ac.uk/efo/EFO_1000647" and .unique_association_fields.reaction_activity == "loss_of_function")' reactome-2020-10-12.json
{
  "type": "affected_pathway",
  "sourceID": "reactome",
  "target": {
    "target_type": "http://identifiers.org/cttv.target/protein_evidence",
    "activity": "http://identifiers.org/cttv.activity/loss_of_function",
    "id": "http://identifiers.org/uniprot/P11168"
  },
  "evidence": {
    "urls": [
      {
        "url": "http://reactome.org/PathwayBrowser/#/R-HSA-5619098",
        "nice_name": "Defective SLC2A2 causes Fanconi-Bickel syndrome (FBS)"
      }
    ],
    "known_mutations": [
      {
        "preferred_name": "L-leucine 389 replaced with L-proline",
        "functional_consequence": "http://purl.obolibrary.org/obo/SO_0001059"
      }
    ],
    "resource_score": {
      "value": 1,
      "method": {
        "description": "Curator inferred association"
      },
      "type": "probability"
    },
    "provenance_type": {
      "database": {
        "id": "Reactome",
        "version": "74"
      },
      "literature": {
        "references": [
          {
            "lit_id": "http://europepmc.org/abstract/MED/9354798"
          },
          {
            "lit_id": "http://europepmc.org/abstract/MED/11044475"
          },
          {
            "lit_id": "http://europepmc.org/abstract/MED/10987651"
          }
        ]
      }
    },
    "date_asserted": "2015-01-22T00:09:00.000Z",
    "evidence_codes": [
      "http://purl.obolibrary.org/obo/ECO_0000205"
    ],
    "is_associated": true
  },
  "validated_against_schema_version": "1.6.1",
  "access_level": "public",
  "unique_association_fields": {
    "mutations": "[L-leucine 389 replaced with L-proline]",
    "target_id": "http://www.identifier.org/uniprot/P11168",
    "reaction_id": "http://reactome.org/PathwayBrowser/#/R-HSA-5638222",
    "disease_id": "http://www.ebi.ac.uk/efo/EFO_1000647",
    "reaction_activity": "loss_of_function"
  },
  "disease": {
    "id": "http://www.ebi.ac.uk/efo/EFO_1000647",
    "name": "renal tubular transport disease"
  }
}

This is the original evidence in the 20.11 Reactome file that contains the mutation:
$ jq-1.6 'select(.unique_association_fields.mutations == "[L-leucine 389 replaced with L-proline]" and .unique_association_fields.target_id == "http://www.identifier.org/uniprot/P11168" and .unique_association_fields.reaction_id == "http://reactome.org/PathwayBrowser/#/R-HSA-5638222" and .unique_association_fields.disease_id == "http://www.ebi.ac.uk/efo/EFO_1000647" and .unique_association_fields.reaction_activity == "loss_of_function")' reactome-2020-10-12.json
{
  "type": "affected_pathway",
  "sourceID": "reactome",
  "target": {
    "target_type": "http://identifiers.org/cttv.target/protein_evidence",
    "activity": "http://identifiers.org/cttv.activity/loss_of_function",
    "id": "http://identifiers.org/uniprot/P11168"
  },
  "evidence": {
    "urls": [
      {
        "url": "http://reactome.org/PathwayBrowser/#/R-HSA-5619098",
        "nice_name": "Defective SLC2A2 causes Fanconi-Bickel syndrome (FBS)"
      }
    ],
    "known_mutations": [
      {
        "preferred_name": "L-leucine 389 replaced with L-proline",
        "functional_consequence": "http://purl.obolibrary.org/obo/SO_0001059"
      }
    ],
    "resource_score": {
      "value": 1,
      "method": {
        "description": "Curator inferred association"
      },
      "type": "probability"
    },
    "provenance_type": {
      "database": {
        "id": "Reactome",
        "version": "74"
      },
      "literature": {
        "references": [
          {
            "lit_id": "http://europepmc.org/abstract/MED/9354798"
          },
          {
            "lit_id": "http://europepmc.org/abstract/MED/11044475"
          },
          {
            "lit_id": "http://europepmc.org/abstract/MED/10987651"
          }
        ]
      }
    },
    "date_asserted": "2015-01-22T00:09:00.000Z",
    "evidence_codes": [
      "http://purl.obolibrary.org/obo/ECO_0000205"
    ],
    "is_associated": true
  },
  "validated_against_schema_version": "1.6.1",
  "access_level": "public",
  "unique_association_fields": {
    "mutations": "[L-leucine 389 replaced with L-proline]",
    "target_id": "http://www.identifier.org/uniprot/P11168",
    "reaction_id": "http://reactome.org/PathwayBrowser/#/R-HSA-5638222",
    "disease_id": "http://www.ebi.ac.uk/efo/EFO_1000647",
    "reaction_activity": "loss_of_function"
  },
  "disease": {
    "id": "http://www.ebi.ac.uk/efo/EFO_1000647",
    "name": "renal tubular transport disease"
  }
}

And this is the one for altered expression:
$ jq-1.6 'select(.unique_association_fields.target_id == "http://www.identifier.org/uniprot/P62244" and .unique_association_fields.reaction_id == "http://reactome.org/PathwayBrowser/#/R-HSA-192841" and .unique_association_fields.disease_id == "http://www.ebi.ac.uk/efo/EFO_0007328" and .unique_association_fields.reaction_activity == "up_or_down")' reactome-2020-10-12.json
{
  "type": "affected_pathway",
  "sourceID": "reactome",
  "target": {
    "target_type": "http://identifiers.org/cttv.target/protein_evidence",
    "activity": "http://identifiers.org/cttv.activity/up_or_down",
    "id": "http://identifiers.org/uniprot/P62244"
  },
  "evidence": {
    "urls": [
      {
        "url": "http://reactome.org/PathwayBrowser/#/R-HSA-192823",
        "nice_name": "Viral mRNA Translation"
      }
    ],
    "known_mutations": [],
    "resource_score": {
      "value": 1,
      "method": {
        "description": "Curator inferred association"
      },
      "type": "probability"
    },
    "provenance_type": {
      "database": {
        "id": "Reactome",
        "version": "74"
      },
      "literature": {
        "references": [
          {
            "lit_id": "http://europepmc.org/abstract/MED/16630668"
          }
        ]
      }
    },
    "date_asserted": "2007-01-28T00:02:00.000Z",
    "evidence_codes": [
      "http://purl.obolibrary.org/obo/ECO_0000205"
    ],
    "is_associated": true
  },
  "validated_against_schema_version": "1.6.1",
  "access_level": "public",
  "unique_association_fields": {
    "target_id": "http://www.identifier.org/uniprot/P62244",
    "reaction_id": "http://reactome.org/PathwayBrowser/#/R-HSA-192841",
    "disease_id": "http://www.ebi.ac.uk/efo/EFO_0007328",
    "reaction_activity": "up_or_down"
  },
  "disease": {
    "id": "http://www.ebi.ac.uk/efo/EFO_0007328",
    "name": "influenza"
  }
}

And this is the one for altered expression:
$ jq-1.6 'select(.unique_association_fields.target_id == "http://www.identifier.org/uniprot/P62244" and .unique_association_fields.reaction_id == "http://reactome.org/PathwayBrowser/#/R-HSA-192841" and .unique_association_fields.disease_id == "http://www.ebi.ac.uk/efo/EFO_0007328" and .unique_association_fields.reaction_activity == "up_or_down")' reactome-2020-10-12.json
{
  "type": "affected_pathway",
  "sourceID": "reactome",
  "target": {
    "target_type": "http://identifiers.org/cttv.target/protein_evidence",
    "activity": "http://identifiers.org/cttv.activity/up_or_down",
    "id": "http://identifiers.org/uniprot/P62244"
  },
  "evidence": {
    "urls": [
      {
        "url": "http://reactome.org/PathwayBrowser/#/R-HSA-192823",
        "nice_name": "Viral mRNA Translation"
      }
    ],
    "known_mutations": [],
    "resource_score": {
      "value": 1,
      "method": {
        "description": "Curator inferred association"
      },
      "type": "probability"
    },
    "provenance_type": {
      "database": {
        "id": "Reactome",
        "version": "74"
      },
      "literature": {
        "references": [
          {
            "lit_id": "http://europepmc.org/abstract/MED/16630668"
          }
        ]
      }
    },
    "date_asserted": "2007-01-28T00:02:00.000Z",
    "evidence_codes": [
      "http://purl.obolibrary.org/obo/ECO_0000205"
    ],
    "is_associated": true
  },
  "validated_against_schema_version": "1.6.1",
  "access_level": "public",
  "unique_association_fields": {
    "target_id": "http://www.identifier.org/uniprot/P62244",
    "reaction_id": "http://reactome.org/PathwayBrowser/#/R-HSA-192841",
    "disease_id": "http://www.ebi.ac.uk/efo/EFO_0007328",
    "reaction_activity": "up_or_down"
  },
  "disease": {
    "id": "http://www.ebi.ac.uk/efo/EFO_0007328",
    "name": "influenza"
  }
}

New evidence for evidences that contains mutation:
{
    "datasourceId" : "reactome",
    "datatypeId" : "affected_pathway",
    "diseaseFromSource" : "renal tubular transport disease",
    "diseaseFromSourceMappedId" : "EFO_1000647",
    "literature" :  [
        "9354798",
        "11044475",
        "10987651"
    ],
    "pathwayId" : "R-HSA-5619098",
    "pathwayName" : "Defective SLC2A2 causes Fanconi-Bickel syndrome (FBS)",
    "reactionId" : "R-HSA-5638222",
    "targetFromSourceId" : "P11168",
    "targetModulation" : "loss_of_function",
    "variantAminoacidDescriptions" : [
        "L-leucine 389 replaced with L-proline"
    ]
}

diseaseFromSourceId - Include if available in the resource
Include in reactionName the name of the given reaction ID
Include in functionalConsequenceId the SO ID corresponding to the term contained in target.activity (e.g. "http://identifiers.org/cttv.activity/loss_of_function").
Currently all possible activities and which need to be mapped are: loss_of_function, partial_loss_of_function, increased_translational_product_level, up_or_down, decreased_transcript_level, and gain_of_function

New evidence for evidences that contains mutation:
{
    "datasourceId" : "reactome",
    "datatypeId" : "affected_pathway",
    "diseaseFromSource" : "renal tubular transport disease",
    "diseaseFromSourceMappedId" : "EFO_1000647",
    "literature" :  [
        "9354798",
        "11044475",
        "10987651"
    ],
    "pathwayId" : "R-HSA-5619098",
    "pathwayName" : "Defective SLC2A2 causes Fanconi-Bickel syndrome (FBS)",
    "reactionId" : "R-HSA-5638222",
    "targetFromSourceId" : "P11168",
    "targetModulation" : "loss_of_function",
    "variantAminoacidDescriptions" : [
        "L-leucine 389 replaced with L-proline"
    ]
}

diseaseFromSourceId - Include if available in the resource
Include in reactionName the name of the given reaction ID
Include in functionalConsequenceId the SO ID corresponding to the term contained in target.activity (e.g. "http://identifiers.org/cttv.activity/loss_of_function").
Currently all possible activities and which need to be mapped are: loss_of_function, partial_loss_of_function, increased_translational_product_level, up_or_down, decreased_transcript_level, and gain_of_function

New evidence for evidences where expression is altered:
{
    "datasourceId" : "reactome",
    "datatypeId" : "affected_pathway",
    "diseaseFromSource" : "influenza",
    "diseaseFromSourceMappedId" : "EFO_0007328",
    "literature" :  [
        "16630668"
    ],
    "pathwayId" : "R-HSA-192823",
    "pathwayName" : "Viral mRNA Translation",
    "reactionId" : "R-HSA-192841",
    "targetFromSourceId" : "P62244",
    "targetModulation" : "up_or_down",
    "variantAminoacidDescriptions" : []
}

diseaseFromSourceId - Include if available in the resource
Include in reactionName the name of the given reaction ID

New evidence for evidences where expression is altered:
{
    "datasourceId" : "reactome",
    "datatypeId" : "affected_pathway",
    "diseaseFromSource" : "influenza",
    "diseaseFromSourceMappedId" : "EFO_0007328",
    "literature" :  [
        "16630668"
    ],
    "pathwayId" : "R-HSA-192823",
    "pathwayName" : "Viral mRNA Translation",
    "reactionId" : "R-HSA-192841",
    "targetFromSourceId" : "P62244",
    "targetModulation" : "up_or_down",
    "variantAminoacidDescriptions" : []
}

diseaseFromSourceId - Include if available in the resource
Include in reactionName the name of the given reaction ID

The document to submit to the provider has been reviewed and can be consulted here.


Spells in Normal Inventory

we've been seeing a big increase of players getting spells into their normal inventory and also we occasionally get a full wand inventory being placed into their normal inventory.

it's been happening for a while but i don't have a reliable way to reproduce it

This hasn't been reported in a long while, closing unless I hear about it again.


Segmentation fault

When mining with multiple GPUs this happens after a few minutes.
I can potentially share the core dump but it's a 255mb file. Grin-miner log is available here: https://pastebin.com/cUUkHhWE

no longer applies since rewrite


Plug_in question

Hello! I want to insert "context_block" into the backbone Resnet, and the position ="after_conv2". Is the structure like that :

Do you want to insert codes into our codebase? Or just ask where to insert these codes?

where .and i just want to know the meaning of "after_conv2"发自坚果 R2

body { background-color: #ffffff; line-height: 1.4;word-wrap: break-word; word-break: normal; } div {word-wrap: break-word; word-break: normal; } p {word-wrap: break-word; word-break: normal; text-indent: 0pt !important; } span {word-wrap: break-word; word-break: normal; } a {word-wrap: break-word; word-break: normal; } td {word-wrap: break-word; word-break: break-all; }Guangchen Lin @.***>
于 2021年11月3日 下午7:07写道：
Do you want to insert codes into our codebase? Or just ask where to insert these codes?

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.
[
{
@.": "http://schema.org",
@.": "EmailMessage",
"potentialAction": {
@.": "ViewAction",
"target": "https://github.com/open-mmlab/mmdetection/issues/6434#issuecomment-958927584",
"url": "https://github.com/open-mmlab/mmdetection/issues/6434#issuecomment-958927584",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
@.": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]

I think your diagram references stem/stages.  after_conv2 refers to the position of the plugin within the forward pass of each Bottleneck block.
If your intention is to run the plugin between stages rather within each Bottleneck (or within the Bottlenecks of a subset of the stages) the forward pass of the ResNet class should be edited to include your plugin.  Currently this behavior cannot be set by config.

Thank you! I had read the paper "An Empirical Study of Spatial Attention Mechanisms in Deep Networks" . And i had read the word : "in the last two stages"

Is "the last two stages" the same as "after_conv2" ?

The Resnet backbone stage naming convention in this codebase is stem > stage_idx 0 > stage_idx 1 > stage_idx 2 > stage_idx 3.  This corresponds to c1 through c5 in your diagram.
Each Resnet stage is a sequence containing multiple Basic blocks or Bottleneck blocks.
The plugins are applied within Bottleneck blocks.  There are three convolution layers in each Bottleneck block and the plugin may be applied after any of them.
The plugins have two settings to determine where they are added to the network.
Stages determines which stages contain Bottleneck blocks with the plugin.  In your case it would be stages = (False, False, True, True).
Position sets the location of the plugin within each Bottleneck block.

Wow!!!!Thank you Peter! I Got IT!!!


Making E-commerce shopping website fully responsive

Issue Type:

[x] Bug Report

Describe the bug

In the mobile view, extra white spaces are there in the right corner.
The navbar isn't fully responsive as it leaves space on the top.
The footer needs to be made responsive and fixing the overflowing text.

Screenshots

I want to work on this issue, and can work on it on an urgent basis, can you please assign it to me??


[feature request] Kagome

First of all: I think you did a really great job by creating tenpy!
I was wondering, how one could use tenpy to simulate Kagome cylinders. For this reason I have implemented a class Kagome, which you can find below. If I understood the internals of tenpy correctly, this always corresponds to what is called YCn-0 in PRX 7, 031020 (2017)? How could one implement YCn-2, YCn-4, ...? Wouldn't it be nice to have this built into tenpy? Thank you already in advance for your answers.
from tenpy.models.lattice import Lattice
import numpy as np

class Kagome(Lattice):

    def __init__(self, Lx, Ly, siteA, siteB, siteC, order="default", bc_MPS="finite"):

        basis = np.array([
            [2., 0.],
            [1., 3.**0.5]
        ])
        pos = (
            np.array([0., 0.]),
            np.array([0.5, -3.**0.5 / 2.]),
            np.array([1., 0.])
        )

        self.nearest_neighbors = [
            (0, 1, np.array([0, 0])),
            (0, 2, np.array([0, 0])),
            (1, 2, np.array([0, 0])),
            (1, 0, np.array([1, -1])),
            (2, 0, np.array([1, 0])),
            (2, 1, np.array([0, 1]))
        ]

        self.next_nearest_neighbors = [
            (0, 1, np.array([0, 1])),
            (0, 2, np.array([-1, 1])),
            (1, 0, np.array([1, 0])),
            (1, 2, np.array([-1, 0])),
            (2, 0, np.array([0, 1])),
            (2, 1, np.array([-1, 1]))
        ]

        self.next_next_nearest_neighbors = [
            (0, 0, np.array([0, 1])),
            (1, 1, np.array([1, 0])),
            (2, 2, np.array([1, -1]))
        ]

        Lattice.__init__(self, [Lx, Ly], [siteA, siteB, siteC], order, bc_MPS, basis, pos)

First of all: this looks great! Would you mind to directly include this class in tenpy? If you create a pull request, you'll get the credit for it ;-) You can insert it below the Honeycomb class in tenpy.models.lattice.
Strictly speaking, the Lattice class does not now about the coupling boundary conditions. The Lattice defines the arrangement of sites, while the "Model" contains the couplings between the sites.
For this reason, it's actually the CouplingModel, where you specify the boundary conditions of the couplings.
Indeed, the couplings which you get from using the CouplingModel are what is called the YCn-0 in the referenced paper. Shifts of the form YCn-m are not implemented as of now, but I agree that this would be very useful. The place where the shifts would appear is in CouplingModel.add_coupling (and MultiCouplingModel.add_multi_coupling). Actually it shouldn't be too complicated to implement it...
PS: I guess you haven't seen it yet, but I've recently set up a community forum with a subforum for feature requests ;-)

I've actually implemented this feature yesterday afternoon.
Commit 873319d39c7b1023bd1e0457e7d7a1cd22403647 adds the option of integers for bc_coupling in the CouplingModel. As it allows only a shift in the cylinder direction, it's not the most general case one can imagine, but I'm sure it suffices in practice - the more general case would only be needed in 3 or more dimensions...
Therefore, I close this "issue". If it's unclear how to use it, please ask in the forum :)


2 - Upgraded Sentiment Analysis: TypeError: '<' not supported between instances of 'Example' and 'Example'

When working on the multiclass classification problem, TypeError: '<' not supported between instances of 'Example' and 'Example' has occurred. It has to do with BucketIterator sortkey  or something.
BucketIterator

Are you using a custom dataset?

Yes, I figured that out, using sort_key in BucketIterator solves that problem but I think it lead to another error.
RuntimeError: Length of all samples has to be greater than 0, but found an element in 'lengths' that is <= 0.


Can we execute the repo over any cloud platform.

I am facing the following problem when tried to import test_Sony using google colab--
ValueError                                Traceback (most recent call last)
 in ()
----> 1 import test_Sony
/content/Learning-to-See-in-the-Dark/test_Sony.py in ()
100 in_image = tf.placeholder(tf.float32, [None, None, None, 4])
101 gt_image = tf.placeholder(tf.float32, [None, None, None, 3])
--> 102 out_image = network(in_image)
103
104 saver = tf.train.Saver()
/content/Learning-to-See-in-the-Dark/test_Sony.py in network(input)
40
41 def network(input):
---> 42     conv1 = slim.conv2d(input, 32, [3, 3], rate=1, activation_fn=lrelu, scope='g_conv1_1')
43     conv1 = slim.conv2d(conv1, 32, [3, 3], rate=1, activation_fn=lrelu, scope='g_conv1_2')
44     pool1 = slim.max_pool2d(conv1, [2, 2], padding='SAME')
/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/framework/python/ops/arg_scope.py in func_with_args(*args, **kwargs)
181       current_args = current_scope[key_func].copy()
182       current_args.update(kwargs)
--> 183     return func(*args, **current_args)
184
185   _add_op(func)
/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/layers/python/layers/layers.py in convolution2d(inputs, num_outputs, kernel_size, stride, padding, data_format, rate, activation_fn, normalizer_fn, normalizer_params, weights_initializer, weights_regularizer, biases_initializer, biases_regularizer, reuse, variables_collections, outputs_collections, trainable, scope)
1152                      trainable,
1153                      scope,
-> 1154                      conv_dims=2)
1155
1156 convolution2d.doc = convolution.doc
/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/framework/python/ops/arg_scope.py in func_with_args(*args, **kwargs)
181       current_args = current_scope[key_func].copy()
182       current_args.update(kwargs)
--> 183     return func(*args, **current_args)
184
185   _add_op(func)
/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/layers/python/layers/layers.py in convolution(inputs, num_outputs, kernel_size, stride, padding, data_format, rate, activation_fn, normalizer_fn, normalizer_params, weights_initializer, weights_regularizer, biases_initializer, biases_regularizer, reuse, variables_collections, outputs_collections, trainable, scope, conv_dims)
1055         _scope=sc,
1056         _reuse=reuse)
-> 1057     outputs = layer.apply(inputs)
1058
1059     # Add variables to collections.
/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/base_layer.py in apply(self, inputs, *args, **kwargs)
803       Output tensor(s).
804     """
--> 805     return self.call(inputs, *args, **kwargs)
806
807   def _set_learning_phase_metadata(self, inputs, outputs):
/usr/local/lib/python3.6/dist-packages/tensorflow/python/layers/base.py in call(self, inputs, *args, **kwargs)
360
361       # Actually call layer
--> 362       outputs = super(Layer, self).call(inputs, *args, **kwargs)
363
364     if not context.executing_eagerly():
/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/base_layer.py in call(self, inputs, *args, **kwargs)
726         if all(hasattr(x, 'shape') for x in input_list):
727           input_shapes = nest.map_structure(lambda x: x.shape, inputs)
--> 728         self.build(input_shapes)
729         self.built = True
730
/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/layers/convolutional.py in build(self, input_shape)
159         constraint=self.kernel_constraint,
160         trainable=True,
--> 161         dtype=self.dtype)
162     if self.use_bias:
163       self.bias = self.add_weight(
/usr/local/lib/python3.6/dist-packages/tensorflow/python/layers/base.py in add_weight(self, name, shape, dtype, initializer, regularizer, trainable, constraint, use_resource, synchronization, aggregation, partitioner)
274             synchronization=synchronization,
275             aggregation=aggregation,
--> 276             getter=vs.get_variable)
277
278         if regularizer:
/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/base_layer.py in add_weight(self, name, shape, dtype, initializer, regularizer, trainable, constraint, partitioner, use_resource, synchronization, aggregation, getter)
563         use_resource=use_resource,
564         synchronization=synchronization,
--> 565         aggregation=aggregation)
566
567     if regularizer is not None:
/usr/local/lib/python3.6/dist-packages/tensorflow/python/training/checkpointable/base.py in _add_variable_with_custom_getter(self, name, shape, dtype, initializer, getter, overwrite, **kwargs_for_getter)
533     new_variable = getter(
534         name=name, shape=shape, dtype=dtype, initializer=initializer,
--> 535         **kwargs_for_getter)
536
537     # If we set an initializer and the variable processed it, tracking will not
/usr/local/lib/python3.6/dist-packages/tensorflow/python/ops/variable_scope.py in get_variable(name, shape, dtype, initializer, regularizer, trainable, collections, caching_device, partitioner, validate_shape, use_resource, custom_getter, constraint, synchronization, aggregation)
1465       constraint=constraint,
1466       synchronization=synchronization,
-> 1467       aggregation=aggregation)
1468
1469
/usr/local/lib/python3.6/dist-packages/tensorflow/python/ops/variable_scope.py in get_variable(self, var_store, name, shape, dtype, initializer, regularizer, reuse, trainable, collections, caching_device, partitioner, validate_shape, use_resource, custom_getter, constraint, synchronization, aggregation)
1215           constraint=constraint,
1216           synchronization=synchronization,
-> 1217           aggregation=aggregation)
1218
1219   def _get_partitioned_variable(self,
/usr/local/lib/python3.6/dist-packages/tensorflow/python/ops/variable_scope.py in get_variable(self, name, shape, dtype, initializer, regularizer, reuse, trainable, collections, caching_device, partitioner, validate_shape, use_resource, custom_getter, constraint, synchronization, aggregation)
508       if "constraint" in function_utils.fn_args(custom_getter):
509         custom_getter_kwargs["constraint"] = constraint
--> 510       return custom_getter(**custom_getter_kwargs)
511     else:
512       return _true_getter(
/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/layers/python/layers/layers.py in layer_variable_getter(getter, *args, **kwargs)
1742   def layer_variable_getter(getter, *args, **kwargs):
1743     kwargs['rename'] = rename
-> 1744     return _model_variable_getter(getter, *args, **kwargs)
1745
1746   return layer_variable_getter
/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/layers/python/layers/layers.py in model_variable_getter(getter, name, shape, dtype, initializer, regularizer, trainable, collections, caching_device, partitioner, rename, use_resource, **)
1733       partitioner=partitioner,
1734       custom_getter=getter,
-> 1735       use_resource=use_resource)
1736
1737
/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/framework/python/ops/arg_scope.py in func_with_args(*args, **kwargs)
181       current_args = current_scope[key_func].copy()
182       current_args.update(kwargs)
--> 183     return func(*args, **current_args)
184
185   _add_op(func)
/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/framework/python/ops/variables.py in model_variable(name, shape, dtype, initializer, regularizer, trainable, collections, caching_device, device, partitioner, custom_getter, use_resource)
295                  caching_device=caching_device, device=device,
296                  partitioner=partitioner, custom_getter=custom_getter,
--> 297                  use_resource=use_resource)
298   return var
299
/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/framework/python/ops/arg_scope.py in func_with_args(*args, **kwargs)
181       current_args = current_scope[key_func].copy()
182       current_args.update(kwargs)
--> 183     return func(*args, **current_args)
184
185   _add_op(func)
/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/framework/python/ops/variables.py in variable(name, shape, dtype, initializer, regularizer, trainable, collections, caching_device, device, partitioner, custom_getter, use_resource)
250                   caching_device=caching_device,
251                   partitioner=partitioner,
--> 252                   use_resource=use_resource)
253
254
/usr/local/lib/python3.6/dist-packages/tensorflow/python/ops/variable_scope.py in _true_getter(name, shape, dtype, initializer, regularizer, reuse, trainable, collections, caching_device, partitioner, validate_shape, use_resource, constraint, synchronization, aggregation)
479           constraint=constraint,
480           synchronization=synchronization,
--> 481           aggregation=aggregation)
482
483     # Set trainable value based on synchronization value.
/usr/local/lib/python3.6/dist-packages/tensorflow/python/ops/variable_scope.py in _get_single_variable(self, name, shape, dtype, initializer, regularizer, partition_info, reuse, trainable, collections, caching_device, validate_shape, use_resource, constraint, synchronization, aggregation)
846                          "reuse=tf.AUTO_REUSE in VarScope? "
847                          "Originally defined at:\n\n%s" % (
--> 848                              name, "".join(traceback.format_list(tb))))
849       found_var = self._vars[name]
850       if not shape.is_compatible_with(found_var.get_shape()):
ValueError: Variable g_conv1_1/weights already exists, disallowed. Did you mean to set reuse=True or reuse=tf.AUTO_REUSE in VarScope? Originally defined at:
File "/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/framework/python/ops/variables.py", line 252, in variable
use_resource=use_resource)
File "/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/framework/python/ops/arg_scope.py", line 183, in func_with_args
return func(*args, **current_args)
File "/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/framework/python/ops/variables.py", line 297, in model_variable
use_resource=use_resource)

Required python (version 2.7) libraries: Tensorflow (>=1.1) + Scipy + Numpy + Rawpy.
You seem to be using python3.6

Since google colab is basically running a virtual machine, you need to extra pay attention to the root folders and files. I've tried and it's really a painful thing to work on.

Required python (version 2.7) libraries: Tensorflow (>=1.1) + Scipy + Numpy + Rawpy.
You seem to be using python3.6

@nthacks I actually are using python version 3.10 and it works with all the libraries. Not sure why 3.6 is not working that the OP had.


Show credits on screen

Fixes #765

Thanks for the pull request @joseph-kaile!

:x: Missing CLA.

Please send in a Contributor License Agreement (CLA) and comment back here to let us know to check this!
Maintainers, here's how to check for a submitted CLA.

Reviewers, don't forget to make sure that:

[ ] Cesium for Unreal Samples works.


Refactor python scripts to consolidate some common functions

Some of our driver scripts (like glsl-to-spv-worker, inspect_compute_results, etc.) have some repeated helper functions or have to directly import an irrelevant script(runspv) for its fairly useful helper functions. With more scripts being added, it'd be nice to have some kind of 'common' file that would both hold helper functions useful in more than one script and wrap around runspv's helper functions(since runspv is meant to be standalone, we can't modify it to depend on this file).

Fixed by #587.


Adding value_and_grad to mlir. Continued work from #622

Before submitting
Please complete the following checklist when submitting a PR:

[x] All new functions and code must be clearly commented and documented.

[x] Ensure that code is properly formatted by running make format.
The latest version of black and clang-format-14 are used in CI/CD to check formatting.

[x] All new features must include a unit test.
Integration and frontend tests should be added to frontend/test,
Quantum dialect and MLIR tests should be added to mlir/test, and
Runtime tests should be added to runtime/tests.

When all the above are checked, delete everything above the dashed
line and fill in the pull request template.

Context:  Adding value_and_grad to mlir. Continued work from #622
Description of the Change: frontend and mlir tests for value_and_grad needs to be added
Benefits: catalyst.value_and_grad can now be used on a qjit-ted function or qnode
Possible Drawbacks:
Related GitHub Issues:
[sc-55116]

Changes from @rauletorresc 's previous work #622:

Added a new optional string attribute requester to BackpropOp. This is to be set to "GradOp" when a BackpropOpis created from HybridGradientLowering::matchAndRewrite(), and to "ValueAndGradOp" when from HybridValueAndGradientLowering::matchAndRewrite(). Based on who created the backprop, in ConversionPatterns.cpp, bool dupNoNeed can be appropriately set.

This optional attribute does not break any existing tests: there are many instances in the existing test suites where gradient.backprop operations don't have this new attribute (e.g. https://github.com/PennyLaneAI/catalyst/blob/8330b7529a19ea1128830c2cb4b8f1c67efd5342/mlir/test/Gradient/BufferizationTest.mlir#L41)

In the test where the ConversionPatterns.cpp actually takes place, i.e. ConversionBackprop.mlir,  this new attribute is added, once "GradOp", once "ValueAndGradOp", and once "helloworld" (to test against any possible future uses in other cases)

(TODO) add frontend tests for catalyst.value_and_grad

reminder to do changelog!

Reminder to add value and grad to the grad op interface

LGTM, however I will prefer @dime10 to approve, as I consider I might lack enough background


partialCache not flushed on content changes

Only template changes flush the cache.

Duplicate of #4931 which was resolved (verified) in v0.44 with https://github.com/gohugoio/hugo/pull/4932.


Fix issue 2456- Broken Edit patient Details functionality]

Check the questionnaire type in questionnaireviewModel

IMPORTANT: Where possible all PRs must be linked to a Github issue
Fixes #2456
Engineer Checklist

[ ] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[ ] I have added any strings visible on UI components to the strings.xml file
[ ] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[ ] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[ ] I have built and run the FHIRCore app to verify my change fixes the issue and/or does not break the app
[ ] I have checked that this PR does NOT introduce breaking changes that require an update to Content and/or Configs? If it does add a sample here or a link to exactly what changes need to be made to the content.

Code Reviewer Checklist

[ ] I have verified Unit tests have been written for any new feature(s) and edge cases
[ ] I have verified any strings visible on UI components are in the strings.xml file
[ ] I have verifed the CHANGELOG.md file has any notable changes to the codebase
[ ] I have verified the solution has been implemented in a configurable and generic way for reuseable components
[ ] I have built and run the FHIRCore app to verify the change fixes the issue and/or does not break the app

@SebaMutuku please add a test that reproduce the error condition in the issue, which fails on main but passes on this branch -- not sure if this requires a new test or removed/reducing mocking on an existing related test, either would be acceptable

Requesting @aurangzaibumer & @FikriMilano reviews on this PR.

@pld this PR needs further discussion. Once that's closed, I will update the code and tests cc @ellykits @aurangzaibumer

this is working for me, let's have qa take a look tomorrow


HLS options not working on ios.

HLS options don't work on ios. This works perfectly when I use any other platform. The bearer token is simply not getting attached to the header. I used console.log() and on ios alone the xhtSetup is never executed. How do I make it work on ios?
config={{                 file: {                   hlsOptions: {                     xhrSetup: function(xhr, url) {                         xhr.setRequestHeader('Authorization',localStorage.getItem('jwtToken'))                     }                   }                 }               }}

HLS.js is not supported on iOS, so your config won't be applied. See https://github.com/video-dev/hls.js/issues/2367#issuecomment-530939229

The hls works perfectly fine under IOS, only the Authentication token is not send with the header, is there any way to add this? When I remove the security of my server the video is played also in IOS


[MGDCTRS-2210] - Implement ManagedProcessor CRD

https://issues.redhat.com/browse/MGDCTRS-2210

This is pretty much the same as a ManagedConnector so it is pretty ok, however in the ManagedConnector CRD there are some tech depth that it may be better not to repeat:

the spec of the connectors is blindly copied in a secrtet, this has been done in order oto avoid leaking sensitive information in the CR, however for processors, we expect the route definition not to include any sensitive info hence, the definition and the shard meta can be embedded in the CR which greatly simplify things
there is *DeploymentSpec that is duplicated in the Spec and Status section of the CRD and for connectors, it was done to help detecting drifts, however that "drift detection" is far from be ideal and I would really recommend to get rid of it and implement a continuous reconciliation via patch

Thanks for headsup @lburgazzoli

the spec of the connectors is blindly copied in a secrtet, this has been done in order oto avoid leaking sensitive information in the CR, however for processors, we expect the route definition not to include any sensitive info hence, the definition and the shard meta can be embedded in the CR which greatly simplify things

In our secret we are planning to keep client_id and client_secret

there is *DeploymentSpec that is duplicated in the Spec and Status section of the CRD and for connectors, it was done to help detecting drifts, however that "drift detection" is far from be ideal and I would really recommend to get rid of it and implement a continuous reconciliation via patch

I had removed the DeploymentSpec from status. We would use the patch in implementation.

Thanks for headsup @lburgazzoli

the spec of the connectors is blindly copied in a secrtet, this has been done in order oto avoid leaking sensitive information in the CR, however for processors, we expect the route definition not to include any sensitive info hence, the definition and the shard meta can be embedded in the CR which greatly simplify things

In our secret we are planning to keep client_id and client_secret only. gist.github.com/vaibhavjainwiz/2c8d15e19e1f7dde8a9a73a8ef090cb1#file-managedprocessor-yaml-L49

You can even include the route inside the spec, it make things easier to detect changes

there is *DeploymentSpec that is duplicated in the Spec and Status section of the CRD and for connectors, it was done to help detecting drifts, however that "drift detection" is far from be ideal and I would really recommend to get rid of it and implement a continuous reconciliation via patch

I had removed the DeploymentSpec from status. We would use the patch in implementation.

You can remove also from spec and flatten the fields

You can remove also from spec and flatten the fields
@lburgazzoli Does it make sense if I also remove DeploymentId & DeploymentResourceVersion as well?

I don't know, that's depends if you plan to use them or not, In RHOC the resources version is used to optimize polling from the fleet manager

I don't know, that's depends if you plan to use them or not, In RHOC the resources version is used to optimize polling from the fleet manager

Polling in the fleet manager is done by the sync, not the operator so we might assume that the operator could avoid using deployments entirely

Yeah, I know that but for connectors, the sync uses the ManagedConnector CRs to compute what it the lates resource version known by the data plane.
Do you have plans to use other machinery ?

Yeah, I know that but for connectors, the sync uses the ManagedConnector CRs to compute what it the lates resource version known by the data plane.
Do you have plans to use other machinery ?

The simplest solutions that comes to my mind is to copy just the resource version than the whole deployment. This decouples the operator from the concept of deployments and simplify the boundaries a little bit. But I suggest to start working on the actual operator impl to see if this works or not, rather than discussing at the data level

Currently I am adding both DeploymentId and DeploymentResourceVersion to PR. We could optimize it later.


[FEATURE] Enable configurable custom and default text roles

See https://docutils.sourceforge.io/docs/ref/rst/directives.html#role

We usually define textroles in the includes.rst.txt which is included at the beginning of each document. So I supose it is probably defined on document level. will have a look at it

@jaapio Each DocumentParserContext now manages a clone of the TextRoleFactory such that changes made to it by one directive do not apply to another document. Also added a test for this.


Makes IntelliJ freeze for some time

From<EMAIL_ADDRESS>on October 10, 2012 00:58:34
What steps will reproduce the problem? 1. You could try and clone git://github.com/ldash/OpenCytoPreprocessing.git
2. Then open OpenCytoPreprocessing.r file and try to edit it for some time: copy, paste, type...
What is the expected output?
For it to work smoothly
What do you see instead?
The IntelliJ window becomes unresponsive.
What version of the product are you using?
Latest from the IntelliJ repository browser
On what operating system?
(K)Ubuntu 11.10 (oneiric) Please provide any additional information below. Started happening, when I upgraded from Oracle Java 6 to Oracle Java 7...
Original issue: http://code.google.com/p/r4intellij/issues/detail?id=43

can't reproduce


Remove package storage

Partially addresses DCOS-15975.
I'll have a follow-up PR that updates the README and removes the package storage command-line flags. That change will require an update to the sbt-dcos build plugin so that we don't pass the storage flags to the cosmos instance under test.

@cruhland Can I get a high-level description of what this PR is doing?

@jsancio updated. Let me know if you want more detail, e.g. a summary of the classes removed.


adapt this script to call and output other files

Love the layout of this script and wondered it anyone help me to adapt this script to call and output other files
ie
step 1
run file1.php and output response
step 2
run file2.php and output response
thanks

Well this is a javascript/jquery utility (which runs client-side in the browser) so if you want to execute PHP files you'll need to make http requests (ajax) to run server-side php code.
Google for how to do ajax with jquery. There are a lot of good tutorials on the internet.

thanks, i am no coder and been trying for days to get something working. I love your design. do you have any spare time to help me out using your code?
many thanks


add regex phone number validation for Serbia

Towards #251

 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.

@subotic Thanks for your work on this! Can you resolve conflicts?

Thank you for your work on this!
Good to merge when the conflicts are resolved and the build is passing! Be sure to format your code using scalafmt commands in the console.

@jdegoes I decided to ignore spaces after checking for the right prefix. I don't know if this is how it should be done. Input is appreciated.

@jdegoes this should be ready for merging

One minor conflict, then good to merge!

closing, because nothing left to merge ...


ACL (spike)

See https://github.com/remind101/empire/wiki/ACL-Proposal
This is a spike into an ACL system using policy documents, similar to how IAM functions. This allows you to provide a set of policies when executing an action on empire.Empire to determine if the action should be authorized or not.
For example, if you wanted to deny the ability for anyone to create new apps, you could do this:
ctx := acl.WithPolicy(acl.Policy{
        {
                Effect: acl.Deny,
                Action: []string{"Create"},
        },
})

empire.Create(ctx, empire.CreateOpts{
        Name: "acme-inc",
})
// Output: not authorized to perform empire:Create

Internally, this provides a very flexible system for performing granular access control. How this gets consumed and configured in cmd/empire is still a question. For the GitHub authentication backend, I'm thinking that you would attach a set of policies to the github teams that you want to provide access to (See server/auth/github/acl.go)
I think this will dovetail into a 2fa integration, so that you can easily configure what commands you want to require 2fa on.
Feedback much appreciated!
TODO

[ ] Add the authorize(ctx, action, resource) pre-check to all core Empire methods.
[ ] Implement github.TeamACL.
[x] GitHub deployments layer
[x] CloudFormation layer.
[ ] Docs
[ ] Changelog

One thing that's a little tricky right now, would be cases where you want to allow deployments to a specific set of apps. To do that, you might provide a policy like so:
policy := Policy{
        Effect: Allow,
        Action: []string{
                "empire:Deploy",
        },
        Resource: []string{
                "acme-inc",
                "frontend",
                "backend",
        },
}

Now, the problem is that you can provide empire.Deploy with a Docker image, but an empty app name and empire will resolve it to the correct app internally. I think the desired behavior would be for empire to resolve the app name, and then determine if the policy allows the action.

I think it would also be possible to define Empire policies within IAM, since IAM doesn't appear to do any validation on the actions defined. So, you could create IAM roles for GitHub teams, and attach the Empire policies to it, then provide those to empire server like --github.team.policies=Developers:arn:aws:iam::066251891493:role/GitHubDevelopersRole
That could get confusing though? Also may be constraining of the Policy type needs to be expanded.

Or potentially, ship with a set of managed policies (like user, and admin) that work for most use cases, that you can map a GitHub team to:
--github.team.policies='Developers:user,Empire Admins:admin'
Where the policies would be defined like:
user := Policy{
        Effect: Allow,
        Action: []string{
                "empire:Deploy",
                "empire:Config",
                "empire:Set",
                "empire:Rollback",
                "empire:Scale",
        },
        Resource: []string{"*"},
}

admin := Policy{
        Effect: Allow,
        Action: []string{
                "empire:*",
        },
        Resource: []string{"*"},
}

but I have a feeling most people will want to have more granular control over access.

This looks very promising. I have a couple of questions after reading through the wiki and your comments:

how are you planning to apply these policies to empire? Do they need to be applied at startup? Or they can be changed 'online'?
do you think it'd make sense to allow providing policies on a per-app basis? (i.e. emp create email-service<EMAIL_ADDRESS>
Also, I also believe that providing more granular control over the API will be better. You could ship with defaults which provide 'readonly' access (maybe just allowing you to list processes, see releases, etc) and 'full' access, which includes running one-off commands, deploying etc.
Re. using IAM to create policy documents, we use terraform (v. similar to cloudformation) to provision/configure all the AWS resources required by our empire apps, so by using IAM we could get a completely reproducible environment in AWS. Otherwise we'd have to think of an alternative way of storing these policies.

how are you planning to apply these policies to empire? Do they need to be applied at startup? Or they can be changed 'online'?

My thought right now is that they would just be provided at startup.

do you think it'd make sense to allow providing policies on a per-app basis? (i.e. emp create email-service<EMAIL_ADDRESS>
Actually, you'll be able to do that using the Resource attribute in the ACL, e.g.:
// Only allow app1 to be restarted.
app1 := Policy{
        Effect: Allow,
        Action: []string{
                "empire:Restart",
        },
        Resource: []string{"app1"},
}

// Only allow app2 to be rolled back.
app2 := Policy{
        Effect: Allow,
        Action: []string{
                "empire:Rollback",
        },
        Resource: []string{"app2"},
}

Also, I also believe that providing more granular control over the API will be better. You could ship with defaults which provide 'readonly' access (maybe just allowing you to list processes, see releases, etc) and 'full' access, which includes running one-off commands, deploying etc.

Yeah, I agree. There may be some value in shipping with some default roles that can be used easily (we'll need to define what the most valuable roles would be), but I think most people that use Empire seriously will want to have granular control.

Re. using IAM to create policy documents, we use terraform (v. similar to cloudformation) to provision/configure all the AWS resources required by our empire apps, so by using IAM we could get a completely reproducible environment in AWS. Otherwise we'd have to think of an alternative way of storing these policies.

Right. Just storing the policies in IAM, and then having Empire translate into it's internal Policy structure seems like it'd work well from my initial poking around with custom actions/resources in IAM policies. I think that might be a good place to start, and if it ends up not working well, we can look into alternative ways of providing policies before the next release.

👍 I like where this is heading.  Storing the policies in IAM would be great - does IAM actually allow free form documents to be stored? I could swear I've had the editor complain about an incorrect action, but I may be confusing it.

does IAM actually allow free form documents to be stored? I could swear I've had the editor complain about an incorrect action, but I may be confusing it.

From some quick testing I did:

Actions are only checked that they contain a :. The service prefix and action postfix are not validated, so I can do things like foo:Bar.
Resource seems to be checked that it's a valid ARN. The service and resource components inside the ARN isn't checked, so this works: arn:aws:empire:::app/*

So, I think it'd work okay. Empire would just pull the policy document, then translate it internal an internal policy.

Ok, added more authorization checks for more actions. The following actions are supported:
Create
Destroy
Config
Set
Restart
Run
Rollback
Deploy
Scale
StreamLogs
CertsAttach

The following still need to be added, but I want to work out naming before:
DomainsCreate
DomainsDestroy

Next up will be the IAM translator, and a way to attach policies to github teams.

👍 on the storing policies in IAM, that sounds like a great start


Used by Php Form Builder

Hi,
Thanks for your amazing Bootstrap select.
I just wanted to suggest my Php Form Builder

be added to your "used by" list:
https://www.phpformbuilder.pro/
https://codecanyon.net/item/php-form-builder/8790160?ref=migli
I'll publish a new release very soon with Bootstrap 4 - Now BS4 is the official Bootstrap latest release: will you update your plugin?
Thanks again for this great work,
Gilles

Thank you for your support of bootstrap-select! Unfortunately, we are discontinuing the "used by" section.


UNITPREFIX

In https://github.com/TeamFlowerPower/kb/wiki/humanReadable the UNITPREFIX is missing

Fixed in<PHONE_NUMBER>ffe4213a7d4f5ce72d186b1193e956


PowerToys Run - UI after switch to WPF-UI is too small

Description of the new feature / enhancement
After updating to v0.76.0, the UI for PowerToys Run is suddenly substantially smaller.  Both text and icons, making it hard to read. Please add the ability to set the font, size, scale or similar.
Scenario when this would be used?
Every time PowerToys Run is launched.
Supporting information
No response

Thanks for your message. This is a Duplicate of an other issue. Additional comments may be added there. /dup #30158


How to change background color fully?

I have this:
<NavigationBar
    style={{ backgroundColor: 'red' }}
    title={titleConfig}
    rightButton={rightButtonConfig}
    leftButton={leftButtonConfig} />

and this is what it's giving me

How can I make everything one color?

Use tintColor: 'red' instead of the style.

Yep, @adamterlson is right, you should use tintColor property instead. Take a look on public API for this component

Got it thx!


Action should not fail credentials are not provided for ChatClient

Related to #5

For more details, open the Copilot Workspace session.

.github/workflows/summarizePR.yml

Added a step to check for the presence of the AI_API_KEY secret. If not provided, the action is skipped, avoiding unnecessary execution.

src/Summarize.PR/Program.cs

Refactored the main program to check for the presence of the APIKey before attempting to create a ChatCompletionsClient.
Introduced a condition to skip ChatClient operations if the APIKey is missing.
Enhanced logging to inform whether the API Key or Commit SHA is missing, providing better insights during execution.

File: .github/workflows/summarizePR.yml

Updated Step Name: Changed the name of the step that checks for API keys to include "Action Token" as well.
Added Token Check: Introduced a new check for the presence of the ACTION_TOKEN secret. If it is not available, the action now skips execution with a message indicating the absence of the Action Token.


Current Satisfier API should operate on entire psbt and index instead of psbt::Input

psbt::Input does not have information about nSequence and nLocktime needed for a complete implementation of Satisfier.
We should probably create a new struct with that information and implement Satisfier on it

Addressed by #142


jQuery UI Calendar Widget: minDate / maxDate no longer working

Are you requesting a feature, reporting a bug or asking a question?
Reporting a Bug
What is the current behavior?
The jQuery UI Calendar widget no longer ignores minDate / maxDate settings.
What is the expected behavior?
The jQuery UI Calendar widget should allow the minDate / maxDate settings via the config / minDate / maxDate properties.
This appears to be regression as it was last working in 1.8.49.
How would you reproduce the current behavior (if this is a bug)?

Create a survey with a datepicker widget that has a minDate / maxDate.
Open the jQuery UI calendar widget.

Provide the test code and the tested page URL (if applicable)
Tested page URL: https://plnkr.co/edit/w2WNo464gDSt8BEu
Test code
Survey
    .StylesManager
    .applyTheme("modern");

var json = {
    "elements": [
        {
            "name": "date",
            "type": "datepicker",
            "inputType": "date",
            "title": "Your favorite date:",
            "dateFormat": "mm/dd/yy",
            "isRequired": true,
            "config": {
                "maxDate": 0
            }
        }
    ]
};

window.survey = new Survey.Model(json);

survey
    .onComplete
    .add(function (sender) {
        document
            .querySelector('#surveyResult')
            .textContent = "Result JSON:\n" + JSON.stringify(sender.data, null, 3);
    });

$("#surveyElement").Survey({model: survey});

Specify your

browser: Microsft Edge
browser version: 99.0.1150.46
surveyjs platform (angular or react or jquery or knockout or vue): jQuery / Vue
surveyjs version: 1.9.20

@joshcampbell191 We missed this one. Sorry about it.
We have fixed this issue some time ago. Please use min/max and minValueExpression/maxValueExpression
Here is the example.
Thank you,
Andrew


MPI test failed

I build your code with OpenMPI/1.10.3 and gcc/6.3.0 and then used this command: ./test/Ising_OPV_MPI_tests.exe but it shows this error:
[==========] Running 5 tests from 1 test case.
[----------] Global test environment set-up.
[----------] 5 tests from MPI_Test
[ RUN      ] MPI_Test.CalculateProbHistAvgTests
test/test_mpi.cpp:46: Failure
Expected equality of these values:
  6
  (int)prob.size()
    Which is: 3
[  FAILED  ] MPI_Test.CalculateProbHistAvgTests (0 ms)
[ RUN      ] MPI_Test.CalculateVectorAvgTests
test/test_mpi.cpp:68: Failure
Expected equality of these values:
  4.5
  data_avg[0]
    Which is: 0
test/test_mpi.cpp:69: Failure
Expected equality of these values:
  5.5
  data_avg[1]
    Which is: 1
test/test_mpi.cpp:70: Failure
Expected equality of these values:
  6.5
  data_avg[2]
    Which is: 2
[  FAILED  ] MPI_Test.CalculateVectorAvgTests (1 ms)
[ RUN      ] MPI_Test.CalculateVectorSumTests
test/test_mpi.cpp:83: Failure
Expected equality of these values:
  18.0
    Which is: 18
  data_sum[0]
    Which is: 0
test/test_mpi.cpp:84: Failure
Expected equality of these values:
  22.0
    Which is: 22
  data_sum[1]
    Which is: 1
test/test_mpi.cpp:85: Failure
Expected equality of these values:
  26.0
    Which is: 26
  data_sum[2]
    Which is: 2
test/test_mpi.cpp:94: Failure
Expected equality of these values:
  18
  data_sum2[0]
    Which is: 0
test/test_mpi.cpp:95: Failure
Expected equality of these values:
  22
  data_sum2[1]
    Which is: 1
test/test_mpi.cpp:96: Failure
Expected equality of these values:
  26
  data_sum2[2]
    Which is: 2
[  FAILED  ] MPI_Test.CalculateVectorSumTests (0 ms)
[ RUN      ] MPI_Test.GatherValuesTests
[       OK ] MPI_Test.GatherValuesTests (0 ms)
[ RUN      ] MPI_Test.GatherVectorsTests
test/test_mpi.cpp:151: Failure
Expected equality of these values:
  12
  (int)data_all.size()
    Which is: 3
test/test_mpi.cpp:162: Failure
Expected equality of these values:
  12
  (int)data_all2.size()
    Which is: 3
[  FAILED  ] MPI_Test.GatherVectorsTests (0 ms)
[----------] 5 tests from MPI_Test (1 ms total)

[----------] Global test environment tear-down
[==========] 5 tests from 1 test case ran. (1 ms total)
[  PASSED  ] 1 test.
[  FAILED  ] 4 tests, listed below:
[  FAILED  ] MPI_Test.CalculateProbHistAvgTests
5 FAILED TESTS

Any idea how to resolve these errors?

I still need to correct the readme


Add OTel Agent e2e pipeline tests

What does this PR do?
This PR adds e2e pipeline tests for the OTel Agent and refactors the file structure of new-e2e/tests/otel according to our testing plan.
These tests use four different collector config files:

complete.yml for a complete config file to use with the converter disabled
minimal.yml for a minimal config file to test that the converter adds components as expected
sampling.yml for adding the probabilistic sampler and verifying APM stats still work
ia.yml for a minimal config file to test the infra attributes processor with high cardinality

The following test cases are implemented in utils/pipelines_utils.go:

Verify fakeintake receives scraped prometheus metrics: collector metrics, trace agent metrics, and agent metrics
Verify fakeintake receives telemetry from telemetrygen

Resource attributes are tagged as expected
Telemetry attributes are tagged as expected
Infraattributesprocessor adds kubernetes tags as expected
Service, env, and version tags appear as expected
Host appears as expected and consistent across all signals
Trace metrics are received by fakeintake

Verify trace metrics work with sampling as expected

Motivation

Additional Notes
The non-pipeline tests have been moved to utils/config_utils.go, and will be expanded on in a future PR for adding extensive config tests.
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


11 apr release

Cherry picking these commits into main:

https://github.com/gretelai/gretel-blueprints/pull/244
https://github.com/gretelai/gretel-blueprints/pull/243

Had some Merge conflict with both of these commits, @kboyd could you double check the notebooks and confirm I've resolved the conflicts correctly?

Is there any way to keep develop and main in sync so these releases are easier?

Ideally, everyone would follow a process of changing develop, then pulling those changes into main. Unfortunately, I don't think that's the common flow with the notebooks...
Frontend doesn't really work with notebooks much, which makes it hard for us to figure out how best to resolve the conflicts. @hhpang , can you catch up with @nakolean and work out what we need the end result to be in prod? There were conflicting changes between your develop-based changes and main that need to be sorted out.


Not able to view the full response

The response view is a bit limited. I had a response that was a json as one long line, but I couldn't view the end of that line.
So, I suggest the following simple alternatives,

Key bindings to scroll to the end of the line
Toggle line wrapping on/off
Possible to reformat well known formats like json

Yes the lack of horizontal scrolling is something I've been punting on for a while. Horizontal scrolling is slightly annoying because left/right arrow are already used to change tabs.
Line wrapping would work but is slightly complicated to implement so again, I've been punting.
It actually will automatically reformat JSON, but only if it recognizes it as JSON via the Content-Type header of the response. If it's not happening in your case, that means the Content-Type header has something other than application/json. Could you post the value of that header from your response? it's possible this is #103

Yes, an extended json is used for the response.

Horizontal scrolling is possible now (pending the next release). I'm not going to implement line wrapping yet, because it's a lot more complicated. Ratatui supports it, but then the line numbers get completely messed up. I'm hoping horizontal scrolling is enough for now.


TF_BINARY_URL

Would be so grateful for some guidance.
Please advise on the appropriate TF_BINARY_URL for compiling Tensor Flow on an Odroid XU4 which uses a Samsung Exynos5422 Cortex™-A15 2Ghz and Cortex™-A7 Octa core CPUs and a Mali-T628 MP6(OpenGL ES 3.1/2.0/1.1 and OpenCL 1.2 Full profile).
Please advise on the TF_BINARY_URL to use for:
Ubuntu/Linux 64-bit, CPU only, Python 2.7
Ubuntu/Linux 64-bit, CPU only, Python 3.5
Is there a GPU version that supports the Mali-T628 MP6(OpenGL ES 3.1/2.0/1.1 and OpenCL 1.2 Full profile) on the Odroid XU4
Thank you!

OpenCL support is currently quite primitive, so there aren't any binaries yet. You'd have to compile from source, and it will likely not be super smooth to use yet. Thanks!

See #22

Thanks Andrew, appreciate it!
The key part of the question was not so much about the GPU, but how to compile a version of tensor flow NOT using a GPU on the Odroid XU, any pointers please?
Thanks
David
Sent from my iPhone

On Jun 12, 2017, at 5:33 PM, Andrew Selle<EMAIL_ADDRESS>wrote:
See #22
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Perhaps this...
https://forum.odroid.com/viewtopic.php?f=140&t=24385
Also it is probably similar to rasbperry pi or other android builds.

Thanks, will take a look, appreciate it!
Sent from my iPhone

On Jun 12, 2017, at 6:25 PM, Andrew Selle<EMAIL_ADDRESS>wrote:
Perhaps this...
https://forum.odroid.com/viewtopic.php?f=140&t=24385
Also it is probably similar to rasbperry pi or other android builds.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


lvm: fix parsing values of absolute amounts for volumes

This fix also is a candidate to stable branch 1.2

[x] Installs cleanly on a fresh build of most recent master branch
[ ] Upgrades cleanly from the most recent release
[ ] Updates documentation relevant to the changes

Also should be tested with -e debug_storage_setup=True

@avnik What are the testing criteria? Do we have to change a default variable so that the new code is tested (besides debug_storage_setup)?

On Thu, Jul 14, 2016 at 03:09:44AM -0700, Langston Barrett wrote:

@avnik What are the testing criteria? Do we have to change a default variable so that the new code is tested (besides debug_storage_setup)?

Testing critria is seting  docker volume for absolute size:  docker_lvm_data_volume_size: 15G for example.
This fix make it works.
debug_storage_setup only force scripts from repo, instead of RPM. I'll update RPM asap, when testing will be done.

I got an error. Here's my config:
mantl > cat roles/docker/defaults/main.yml | grep data_volume_size
docker_lvm_data_volume_size: 10G
docker_lvm_data_volume_size_min: 2G
docker_volume_size: "{{ docker_lvm_data_volume_size }}"

And the message:
TASK: [docker | process with mantl storage setup] *****************************
failed: [lb0-worker-002] => {"changed": true, "cmd": "/usr/bin/mantl-storage-setup", "delta": "0:00:00.176288", "end": "2016-07-15 10:04:21.784482", "rc": 1, "start": "2016-07-15 10:04:21.608194", "warnings": []}
stderr: Traceback (most recent call last):
  File "/usr/bin/mantl-storage-setup", line 296, in <module>
    main()
  File "/usr/bin/mantl-storage-setup", line 289, in main
    iterate_config("volume", process_volume, cp)
  File "/usr/bin/mantl-storage-setup", line 277, in iterate_config
    fun(each, cp)
  File "/usr/bin/mantl-storage-setup", line 147, in process_volume
    size, size_opt, size_unit = parse_size(size)
  File "/usr/bin/mantl-storage-setup", line 135, in parse_size
    return int(m.group(1)), "L", m.group(2)
IndexError: no such group
stdout:   Physical volume "/dev/xvdh" successfully created
  Volume group "mantl" successfully created
==> Processing: /etc/mantl/filesystems.d/10-volume-group.conf
READ:  ['/sbin/pvs', '--nameprefix', '--noheadings', '--unquoted', '-o', 'pv_all,vg_name', '--separator', ';']
READ:  ['/sbin/vgs', '--nameprefix', '--noheadings', '--unquoted', '-o', 'all', '--separator', ';']
==> Processing: /etc/mantl/filesystems.d/20-docker-volume.conf
failed: [lb0-control-03] => {"changed": true, "cmd": "/usr/bin/mantl-storage-setup", "delta": "0:00:00.162313", "end": "2016-07-15 10:04:21.783770", "rc": 1, "start": "2016-07-15 10:04:21.621457", "warnings": []}
stderr: Traceback (most recent call last):
  File "/usr/bin/mantl-storage-setup", line 296, in <module>
    main()
  File "/usr/bin/mantl-storage-setup", line 289, in main
    iterate_config("volume", process_volume, cp)
  File "/usr/bin/mantl-storage-setup", line 277, in iterate_config
    fun(each, cp)
  File "/usr/bin/mantl-storage-setup", line 147, in process_volume
    size, size_opt, size_unit = parse_size(size)
  File "/usr/bin/mantl-storage-setup", line 135, in parse_size
    return int(m.group(1)), "L", m.group(2)
IndexError: no such group
stdout:   Physical volume "/dev/xvdh" successfully created
  Volume group "mantl" successfully created
==> Processing: /etc/mantl/filesystems.d/10-volume-group.conf
READ:  ['/sbin/pvs', '--nameprefix', '--noheadings', '--unquoted', '-o', 'pv_all,vg_name', '--separator', ';']
READ:  ['/sbin/vgs', '--nameprefix', '--noheadings', '--unquoted', '-o', 'all', '--separator', ';']
==> Processing: /etc/mantl/filesystems.d/20-docker-volume.conf
failed: [lb0-control-02] => {"changed": true, "cmd": "/usr/bin/mantl-storage-setup", "delta": "0:00:00.158287", "end": "2016-07-15 10:04:21.789124", "rc": 1, "start": "2016-07-15 10:04:21.630837", "warnings": []}
stderr: Traceback (most recent call last):
  File "/usr/bin/mantl-storage-setup", line 296, in <module>
    main()
  File "/usr/bin/mantl-storage-setup", line 289, in main
    iterate_config("volume", process_volume, cp)
  File "/usr/bin/mantl-storage-setup", line 277, in iterate_config
    fun(each, cp)
  File "/usr/bin/mantl-storage-setup", line 147, in process_volume
    size, size_opt, size_unit = parse_size(size)
  File "/usr/bin/mantl-storage-setup", line 135, in parse_size
    return int(m.group(1)), "L", m.group(2)
IndexError: no such group
stdout:   Physical volume "/dev/xvdh" successfully created
  Volume group "mantl" successfully created
==> Processing: /etc/mantl/filesystems.d/10-volume-group.conf
READ:  ['/sbin/pvs', '--nameprefix', '--noheadings', '--unquoted', '-o', 'pv_all,vg_name', '--separator', ';']
READ:  ['/sbin/vgs', '--nameprefix', '--noheadings', '--unquoted', '-o', 'all', '--separator', ';']
==> Processing: /etc/mantl/filesystems.d/20-docker-volume.conf
failed: [lb0-edge-01] => {"changed": true, "cmd": "/usr/bin/mantl-storage-setup", "delta": "0:00:00.153066", "end": "2016-07-15 10:04:21.939292", "rc": 1, "start": "2016-07-15 10:04:21.786226", "warnings": []}
stderr: Traceback (most recent call last):
  File "/usr/bin/mantl-storage-setup", line 296, in <module>
    main()
  File "/usr/bin/mantl-storage-setup", line 289, in main
    iterate_config("volume", process_volume, cp)
  File "/usr/bin/mantl-storage-setup", line 277, in iterate_config
    fun(each, cp)
  File "/usr/bin/mantl-storage-setup", line 147, in process_volume
    size, size_opt, size_unit = parse_size(size)
  File "/usr/bin/mantl-storage-setup", line 135, in parse_size
    return int(m.group(1)), "L", m.group(2)
IndexError: no such group
stdout:   Physical volume "/dev/xvdh" successfully created
  Volume group "mantl" successfully created
==> Processing: /etc/mantl/filesystems.d/10-volume-group.conf
READ:  ['/sbin/pvs', '--nameprefix', '--noheadings', '--unquoted', '-o', 'pv_all,vg_name', '--separator', ';']
READ:  ['/sbin/vgs', '--nameprefix', '--noheadings', '--unquoted', '-o', 'all', '--separator', ';']
==> Processing: /etc/mantl/filesystems.d/20-docker-volume.conf
failed: [lb0-control-01] => {"changed": true, "cmd": "/usr/bin/mantl-storage-setup", "delta": "0:00:00.172491", "end": "2016-07-15 10:04:22.003993", "rc": 1, "start": "2016-07-15 10:04:21.831502", "warnings": []}
stderr: Traceback (most recent call last):
  File "/usr/bin/mantl-storage-setup", line 296, in <module>
    main()
  File "/usr/bin/mantl-storage-setup", line 289, in main
    iterate_config("volume", process_volume, cp)
  File "/usr/bin/mantl-storage-setup", line 277, in iterate_config
    fun(each, cp)
  File "/usr/bin/mantl-storage-setup", line 147, in process_volume
    size, size_opt, size_unit = parse_size(size)
  File "/usr/bin/mantl-storage-setup", line 135, in parse_size
    return int(m.group(1)), "L", m.group(2)
IndexError: no such group
stdout:   Physical volume "/dev/xvdh" successfully created
  Volume group "mantl" successfully created
==> Processing: /etc/mantl/filesystems.d/10-volume-group.conf
READ:  ['/sbin/pvs', '--nameprefix', '--noheadings', '--unquoted', '-o', 'pv_all,vg_name', '--separator', ';']
READ:  ['/sbin/vgs', '--nameprefix', '--noheadings', '--unquoted', '-o', 'all', '--separator', ';']
==> Processing: /etc/mantl/filesystems.d/20-docker-volume.conf
failed: [lb0-kubeworker-001] => {"changed": true, "cmd": "/usr/bin/mantl-storage-setup", "delta": "0:00:00.214339", "end": "2016-07-15 10:04:22.038969", "rc": 1, "start": "2016-07-15 10:04:21.824630", "warnings": []}
stderr: Traceback (most recent call last):
  File "/usr/bin/mantl-storage-setup", line 296, in <module>
    main()
  File "/usr/bin/mantl-storage-setup", line 289, in main
    iterate_config("volume", process_volume, cp)
  File "/usr/bin/mantl-storage-setup", line 277, in iterate_config
    fun(each, cp)
  File "/usr/bin/mantl-storage-setup", line 147, in process_volume
    size, size_opt, size_unit = parse_size(size)
  File "/usr/bin/mantl-storage-setup", line 135, in parse_size
    return int(m.group(1)), "L", m.group(2)
IndexError: no such group
stdout:   Physical volume "/dev/xvdh" successfully created
  Volume group "mantl" successfully created
==> Processing: /etc/mantl/filesystems.d/10-volume-group.conf
READ:  ['/sbin/pvs', '--nameprefix', '--noheadings', '--unquoted', '-o', 'pv_all,vg_name', '--separator', ';']
READ:  ['/sbin/vgs', '--nameprefix', '--noheadings', '--unquoted', '-o', 'all', '--separator', ';']
==> Processing: /etc/mantl/filesystems.d/20-docker-volume.conf
failed: [lb0-worker-001] => {"changed": true, "cmd": "/usr/bin/mantl-storage-setup", "delta": "0:00:00.215793", "end": "2016-07-15 10:04:22.100355", "rc": 1, "start": "2016-07-15 10:04:21.884562", "warnings": []}
stderr: Traceback (most recent call last):
  File "/usr/bin/mantl-storage-setup", line 296, in <module>
    main()
  File "/usr/bin/mantl-storage-setup", line 289, in main
    iterate_config("volume", process_volume, cp)
  File "/usr/bin/mantl-storage-setup", line 277, in iterate_config
    fun(each, cp)
  File "/usr/bin/mantl-storage-setup", line 147, in process_volume
    size, size_opt, size_unit = parse_size(size)
  File "/usr/bin/mantl-storage-setup", line 135, in parse_size
    return int(m.group(1)), "L", m.group(2)
IndexError: no such group
stdout:   Physical volume "/dev/xvdh" successfully created
  Volume group "mantl" successfully created
==> Processing: /etc/mantl/filesystems.d/10-volume-group.conf
READ:  ['/sbin/pvs', '--nameprefix', '--noheadings', '--unquoted', '-o', 'pv_all,vg_name', '--separator', ';']
READ:  ['/sbin/vgs', '--nameprefix', '--noheadings', '--unquoted', '-o', 'all', '--separator', ';']
==> Processing: /etc/mantl/filesystems.d/20-docker-volume.conf

@siddharthist hm, this worked for me. Any idea what might be different? did you definitely run with debug_storage_setup=True?
diff --git a/roles/docker/defaults/main.yml b/roles/docker/defaults/main.yml
index 9255889..6a1da3a 100644
--- a/roles/docker/defaults/main.yml
+++ b/roles/docker/defaults/main.yml
@@ -43,7 +43,7 @@ docker_storage_driver: overlay
 ## These are not used for overlay on lvm
 ## Refer to commentaries in ../templates/docker-storage-setup.conf.j2
 ## or `man lvcreate` for acceptable sizes, and their syntax
-docker_lvm_data_volume_size: 40%FREE
+docker_lvm_data_volume_size: 10G
 docker_lvm_data_volume_size_min: 2G

 docker_lvm_auto_extend_pool: yes
diff --git a/roles/lvm/defaults/main.yml b/roles/lvm/defaults/main.yml
index ceba16a..868d625 100644
--- a/roles/lvm/defaults/main.yml
+++ b/roles/lvm/defaults/main.yml
@@ -7,4 +7,4 @@ lvm_physical_device: >
   {%- elif provider == 'openstack' -%}/dev/vdb
   {%- endif -%}{%- endif -%}

-debug_storage_setup: False
+debug_storage_setup: True

$ sudo lvdisplay
  --- Logical volume ---
  LV Path                /dev/mantl/docker
  LV Name                docker
  VG Name                mantl
  LV UUID                uD85jX-F3nq-PWmF-t9cA-GHcy-fhh3-aGFgKl
  LV Write Access        read/write
  LV Creation host, time ip-10-1-2-163.ec2.internal, 2016-07-15 15:11:37 +0000
  LV Status              available
  # open                 1
  LV Size                10.00 GiB
  Current LE             2560
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     8192
  Block device           253:0

$ sudo pvdisplay
  --- Physical volume ---
  PV Name               /dev/xvdh
  VG Name               mantl
  PV Size               100.00 GiB / not usable 4.00 MiB
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              25599
  Free PE               23039
  Allocated PE          2560
  PV UUID               hAEfnv-HeQf-IDY1-CJrS-RFIc-Yamx-8rfe27

Oh, I thought it had to be tested with both debug_storage_setup=True and debug_storage_setup=False. This works for me with debug_storage_setup=True. :+1:

@avnik it looks like this works - can you update the rpm (and this pr if needed) with the updated mantl-storage-setup so that it will work without setting debug_storage_setup=True?

@ryan sure. I merge it now. And fix RPM today


react-router-redux for react-native (NativeRouter)

Hi guys! Thank you for the great and very-very reasonable v4.
The only thing to mention is that I'm lacking support for react-router-redux in react-native.
I'm ready to make a PR with the feature, as I see that this means to reimplement <MemoryRouter> just replacing <Router> with <ConnectedRouter> and wrap it with <ConnectedNativeRouter>.
Am I right? If no, then give me a key of where I'm mistaken, if yes just tell me go on and I'll help with this part.

Hey,
I haven't tested this yet but I think you can already do this. You need to give the <ConnectedRouter> an in memory history object. (history/createMemoryHistory) See usage from the history package: https://github.com/ReactTraining/history#usage

Right now native integration is lacking. But we're going to work on it. (I have a major product release at the end of the month, so I'm blocked on that until next month)

Hey man
Did you integrated react native and react-router-redux?
When set 'history/createMemoryHistory' routerMiddleware, I have got message "cannot read property apply of undefined"


Create  database tables

Create tables and queries

@Davidosky007 can you please look at the comment i left the last reviewer and then please tell me whats wrog because am confused

@ @Davidosky007 i put the screen shot there, even the last reviewer referenced it. so am confused. The query isnt supposed to return anything and so the screen shot reflects that with an empty return, so am confused, how is it supposed to be?


Jwt_Secret_Bruteforce Added

Description
Jwt_Secret_Bruteforce is added
#398
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes

Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I've edited the SCRIPTS.md and link to my code.
[x] I have created a helpful and easy to understand README.md
[x] My documentation follows Template for README.md
[x] My changes generate no new warnings

@avinashkranjan don't merge this PR.
This is copied from https://github.com/bing0o/Python-Scripts/blob/master/jwt-secret-bruteforce.py
Proof
@Kalivarapubindusree Code

Original code

This is the case of all the  PR , So can you please take some action  against him.

Can you please give labels for this pr u merged it but didn't give labels @avinashkranjan


Call to a member function __setLocation() on null

FatalErrorException in Service.php line 348:
Call to a member function __setLocation() on null

i get this when i add my location url to:

->location('https://....')

to fix this and make my add work i added location in:

->options(['location'=>'https://....'])

Can you post your code here please?

Thanks!

It works for laravel 5.4?

Laravel version 5.4 is not released yet, Laravel is on 5.2.

oh yes sorry! i mean 5.2

It should work fine in 5.2.

Yes, i'm on Lumen 5.2 beside the known bugs all ok.

i get this error with the readme example:
FatalThrowableError in ControllerDispatcher.php line 110:
Fatal error: Call to undefined method cajas\Http\Controllers\SoapController::getMiddleware()

Please create a new issue, as this is the issue for my bug.
Thanks!

Fixed in version 0.3.*


Only consider LLM content for text splitting

Description
Our text splitters should only consider LLM content/metadata when splitting text. This is because people may put a lot of extra text in the metadata that is only intended to be used for embeddings.
Type of Change

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

How Has This Been Tested?

[x] I stared at the code and made sure it makes sense

close in favour of https://github.com/jerryjliu/llama_index/pull/7182


installation: untar libzmq in venv folder instead of /usr/local

on a linux-host docker build, the user can't write to /usr/local and installing pyzmq fails
untar libzmq to venv instead
normal installation also changed because it's sensible to have all pyzmq dependencies in the venv
jukebox.Dockerfile: removing ZMQ_PREFIX=${PREFIX} since PREFIX variable doesn't exist in docker environment
jukebox.Dockerfile: use ENV to set ZMQ_DRAFT_API

Hi, thanks for your contribution.
My thoughts about this:

To solve access rights in the docker build, the libzmq download and unpacking has to be done before the user is set.
libzmq is not a python lib and so it does not belong in the venv, in my opinion. A venv is also designed to be reproducable by removing and reinstalling all python modules, which libzmq cant fullfill. The recommended installation for libzmq is via a package installer, but as we need to build it ourself, "/usr/local/" is the correct folder to place it.
IF we would decide to not put it on system level, i would recommend to place it in a new folder in the project root, like .libs, but i am not aware of any problems with the current solution.
Theres already a PR to address some problems with the docker setup (https://github.com/MiczFlor/RPi-Jukebox-RFID/pull/2167), so i would suggest to bring this together (i think the problem with the access right is an important hint, which was missed there.

* libzmq is not a python lib and so it does not belong in the venv, in my opinion. A venv is also designed to be reproducable by removing and reinstalling all python modules, which libzmq cant fullfill. The recommended installation for libzmq is via a package installer, but as we need to build it ourself, "/usr/local/" is the correct folder to place it.
  IF we would decide to not put it on system level, i would recommend to place it in a new folder in the project root, like `.libs`, but i am not aware of any problems with the current solution.

I'm not a pythonm expert, so if you say that's something one doesn't do that's fine with me. My reasoning was that libzmq, though not a python package, is a python package dependency, but I haven't found a clear rule/suggestion on the web whether non-pyhton dependencies should be put in the venv or not, so I'll just use your suggestion to untar as root in docker and leave the normal installation unchanged.

* Theres already a PR to address some problems with the docker setup ([Fix Docker for pyzmq #2167](https://github.com/MiczFlor/RPi-Jukebox-RFID/pull/2167)), so i would suggest to bring this together (i think the problem with the access right is an important hint, which was missed there.

OK so how does this work, I make the changes and create a merge request with MR #2167?

OK so how does this work, I make the changes and create a merge request with MR #2167?

@pabera has created a new PR #2307, where all relevant changes from the different PRs will be gathered.
Feel free to test this change and give feedback :)

PR #2307 works and fixes this issue, so I'm closing this PR.


Expose XHR instance

Fixes gh-64

Hi @mzabriskie.
I hate to have to ask this, but could you take a look at this PR? We (the team behind Github.js) have switched to axios for our requests and this is the only piece left for the new release. In the previous versions we exposed the XHR istance, so not having it would cause a breaking change.

Any chance to review this PR so that we can address #214?

@mzabriskie ping.

@AurelioDeRosa I'm fine merging this, but will you please do the same for the http adapter?

@mzabriskie is req the object you want to return in the http adapter?

@AurelioDeRosa sorry, I just saw your response. Yes, req would be the object to use.

@mzabriskie Applied the change and also rebased.


Multiple GraphQlJSON typedefs gives "Duplicate schema type name JSON"

After upgrading to 2.23, when using multiple GraphQlJSON scalar in my schema, makeExecutableSchema() returns a Duplicate schema type name JSON.
Everything is working with 2.22.
Example:
import GraphQLJSON from 'graphql-type-json'

const compileSchema = makeExecutableSchema({
  typeDefs: `
    scalar Product
    scalar Category
  `,
  resolvers: {
    typeDef: {
      Product: GraphQLJSON,
      Category: GraphQLJSON,
    }
});

Error (with paths partially removed):
/node_modules/graphql-tools/dist/schemaVisitor.js:240
                    throw new Error("Duplicate schema type name " + actualName);
                    ^

Error: Duplicate schema type name JSON
    at /node_modules/graphql-tools/src/schemaVisitor.ts:323:17
    at /node_modules/graphql-tools/src/schemaVisitor.ts:698:5
    at Array.forEach (<anonymous>)
    at each (/node_modules/graphql-tools/src/schemaVisitor.ts:697:30)
    at heal (/node_modules/graphql-tools/src/schemaVisitor.ts:312:7)
    at healSchema (/node_modules/graphql-tools/src/schemaVisitor.ts:300:3)
    at Function.SchemaDirectiveVisitor.visitSchemaDirectives (/node_modules/graphql-tools/src/schemaVisitor.ts:607:5)
    at attachDirectiveResolvers /node_modules/graphql-tools/src/schemaGenerator.ts:717:26)
    at makeExecutableSchema (/node_modules/graphql-tools/src/schemaGenerator.ts:142:5)
    at Object.<anonymous> (src/schema.js:111:23)

I'm just experienced this when trying to to directives for the first time. This is still broken for v2.24.0. I'm surprised no one else has commented on this in a month.

I have similar issue here https://stackoverflow.com/q/50373038/3620044

Interesting - this looks like the library is using the name included in the scalar type object, rather than the key in the dictionary. Could someone open a PR with a failing test? That would be the first step to a fix, and will prevent this from breaking in the future!

We haven't heard back regarding the request for a repro, so closing for now. Thanks!

@BrendanBall @Alex-PK Did you manage to solve this issue? - having the same problems!