Wr/twinning

What does this PR do?
Adds --dev-debug flag with enhancements
You can now --dev-debug sf:config to limit DEBUG statements
✅ : the current promote-verify uses the correct command
Acceptance Criteria
run a command with --dev-debug to see the debug output, should be equivalent to setting DEBUG=* before running a command
Testing Notes
--dev-debug results in * debug statements
--dev-debug <filter> will filter the debug statements
Checklist

[x] This change has been approved by the CLI Review Board or approval isn't required. Anything that adds/changes/deletes commands, flags, output, or json output has to be reviewed.
[x] Does this follow the deprecation policy?

What issues does this PR fix or reference?
@W-12152987@

QA notes
./bin/run env list --dev-debug
✅ does all the debug output as expected
✅ ran with a few flags (--sort with a value, --help) after --dev-debug
✅ ran with a non-* debug value (sf:core) and saw only those logs
example from the comments
config get --dev-debug target-dev-hub --json
❌ command fails with NoConfigKeysFoundError (code is deleting the required argument after --dev-debug)
💡 what if this code ensured that, if present, --dev-debug is the last arg (or penultimate arg if followed by a non-flag value) ?  I'm not sure there's a good way to tell an arg from a debug value

QA notes:
previous issue fixed.  Tried all of
./bin/run config get --debug-filter sf:core target-dev-hub --dev-debug
./bin/run config get --debug-filter sf:core target-dev-hub
./bin/run config get --dev-debug --debug-filter sf:core target-dev-hub
./bin/run config get --dev-debug --debug-filter  target-dev-hub
All passed/failed as expected.


[thci] remove unneeded problematic command

Listing the table of rules results in SSH disconection under some circumstances. Removing the command since it doesn't add any functionality.

No idea, but it's quite deterministic. I tested the following for the 5.10.13 test with Nordic BRs:

Run test with ip6tables -L INPUT -v: Fail
Run test without ip6tables -L INPUT -v: Pass (x3)
Run test with ip6tables -L INPUT -v again: Fail
Run test without ip6tables -L INPUT -v: Pass


Uncaught TypeError: TabsToSpaces is not a function

[Enter steps to reproduce below:]

...
...

Atom Version: 1.2.3
System: Mac OS X 10.11.1
Thrown From: tabs-to-spaces package, v1.0.0
Stack Trace
Uncaught TypeError: TabsToSpaces is not a function
At /Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:825

TypeError: TabsToSpaces is not a function
    at Object.module.exports.loadModule (/Users/pnorvell/.atom/packages/tabs-to-spaces/lib/index.coffee:1:1)
    at /Users/pnorvell/.atom/packages/tabs-to-spaces/lib/index.coffee:45:14
    at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:86:11)
    at TextBuffer.module.exports.TextBuffer.saveAs (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/text-buffer.js:1010:20)
    at TextBuffer.module.exports.TextBuffer.save (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/text-buffer.js:1002:19)
    at TextEditor.module.exports.TextEditor.save (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:557:26)
    at Pane.module.exports.Pane.saveItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:530:18)
    at Pane.module.exports.Pane.saveActiveItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:513:19)
    at Workspace.module.exports.Workspace.saveActivePaneItem (/Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:631:35)
    at atom-workspace.commandRegistry.add.core:save (/Applications/Atom.app/Contents/Resources/app.asar/src/register-default-commands.js:173:32)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:533:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:356:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:99:36)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands
     -0:01.8.0 core:save (atom-text-editor.editor.is-focused.autocomplete-active)

Config
{
  "core": {
    "themes": [
      "atom-dark-ui",
      "solarized-light-syntax"
    ],
    "disabledPackages": [
      "move-panes"
    ]
  },
  "tabs-to-spaces": {
    "onSave": "untabify"
  }
}

Installed Packages
# User
Sublime-Style-Column-Selection, v1.3.0
atom-beautify, v0.28.19
go-plus, v3.5.2
language-docker, v1.1.3
language-groovy, v0.4.0
language-hcl, v0.1.2
language-powershell, v2.1.0
language-puppet, v0.15.0
line-ending-converter, v1.3.2
linter, v1.11.2
linter-puppet-lint, v0.6.1
minimap, v4.16.1
pretty-json, v0.4.1
project-manager, v2.6.5
tabs-to-spaces, v1.0.0

# Dev
No dev packages

Thanks for reporting. I'll take a look at it as soon as I get home from work in a couple hours.

I'm pretty sure that this is only an issue when upgrading from inside the application. I've got an idea to fix it though.

[Enter steps to reproduce below:]

...
...

Atom Version: 1.2.2
System: Unknown Windows Version
Thrown From: tabs-to-spaces package, v1.0.1
Stack Trace
Uncaught TypeError: TabsToSpaces is not a function
At /C:/Users/guilh/.atom/packages/tabs-to-spaces/lib/index.coffee:71

TypeError: TabsToSpaces is not a function
    at Object.module.exports.loadModule (file:///C:/Users/guilh/.atom/packages/tabs-to-spaces/lib/index.coffee:1:1)
    at atom-workspace.commands.atom.commands.add.tabs-to-spaces:tabify (file:///C:/Users/guilh/.atom/packages/tabs-to-spaces/lib/index.coffee:14:32)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (C:\Users\guilh\AppData\Local\atom\app-1.2.2\resources\app.asar\src\command-registry.js:260:29)
    at CommandRegistry.handleCommandEvent (C:\Users\guilh\AppData\Local\atom\app-1.2.2\resources\app.asar\src\command-registry.js:3:61)
    at CommandRegistry.module.exports.CommandRegistry.dispatch (C:\Users\guilh\AppData\Local\atom\app-1.2.2\resources\app.asar\src\command-registry.js:160:19)
    at AtomEnvironment.module.exports.AtomEnvironment.dispatchApplicationMenuCommand (C:\Users\guilh\AppData\Local\atom\app-1.2.2\resources\app.asar\src\atom-environment.js:987:28)
    at emitOne (events.js:77:13)
    at EventEmitter.emit (events.js:169:7)

Commands
  2x -4:45.8.0 core:move-down (atom-text-editor.editor.is-focused)
     -4:43.9.0 snippets:next-tab-stop (atom-text-editor.editor.is-focused)
     -4:43.9.0 snippets:expand (atom-text-editor.editor.is-focused)
     -4:43.9.0 editor:indent (atom-text-editor.editor.is-focused)
  4x -4:34.2.0 core:backspace (atom-text-editor.editor.is-focused.autocomplete-active)
     -4:32 autocomplete-plus:confirm (atom-text-editor.editor.is-focused.autocomplete-active)
     -4:32 snippets:expand (atom-text-editor.editor.is-focused.autocomplete-active)
     -4:27.5.0 editor:move-to-end-of-screen-line (atom-text-editor.editor.is-focused)
     -4:26.3.0 core:move-down (atom-text-editor.editor.is-focused)
     -4:25.9.0 editor:newline (atom-text-editor.editor.is-focused)
     -4:24 autocomplete-plus:confirm (atom-text-editor.editor.is-focused.autocomplete-active)
     -4:24 snippets:expand (atom-text-editor.editor.is-focused.autocomplete-active)
     -4:20.1.0 core:move-down (atom-text-editor.editor.is-focused)
     -1:04.3.0 core:paste (atom-text-editor.editor.is-focused)
  2x -1:02.1.0 core:save (atom-text-editor.editor.is-focused)
     -0:03.0 tabs-to-spaces:tabify (atom-text-editor.editor.is-focused)

Config
{
  "core": {},
  "tabs-to-spaces": {
    "onSave": "untabify"
  }
}

Installed Packages
# User
aligner-python, v1.0.1
autocomplete-python, v0.10.4
color-picker, v2.0.13
minimap, v4.16.1
pigments, v0.19.0
python-tools, v0.6.6
tabs-to-spaces, v1.0.1

# Dev
No dev packages


DBZ-1297 Expand JSON escaped string as JSON

This is a first step of DBZ-1297 for managing transformation of an escaped JSON string into JSON, inferring the connect Schema from the JSON document structure.
This allow the Outbox Event Router to directly produce JSON message on Kafka like:
# Kafka Topic: outbox.event.order
# Kafka Message key: "1"
# Kafka Message Headers: "id=4d47e190-0402-4048-bc2c-89dd54343cdc"
# Kafka Message Timestamp:<PHONE_NUMBER>484
{
  "id": 1, "lineItems": [{"id": 1, "item": "Debezium in Action", "status": "ENTERED", "quantity": 2, "totalPrice": 39.98}, {"id": 2, "item": "Debezium for Dummies", "status": "ENTERED", "quantity": 1, "totalPrice": 29.99}], "orderDate": "2019-01-31T12:13:01", "customerId": 123
}

This option is off by default and can be turned-on using: transforms.outbox.debezium.expand.json.payload=true

@lbroudoux  We are near the release of 1.7.0.Final. The PR will be merged right after the realse into 1.8 master.

And applied; thanks again, @lbroudoux, that's a great addition!


examples/server doesn't change SCID after sending Retry packet.

C routine examples/server.c doesn't change SCID after sending Retry packet:

according to RFC, server should select a new SCID to send Initial packet once it previously initiated a Retry

currently C-API quiche_accept just takes two SCIDs:
// Creates a new server-side connection.
quiche_conn *quiche_accept(const uint8_t *scid, size_t scid_len, <== server generated SCID
                           const uint8_t *odcid, size_t odcid_len, <== client temporarily generated DCID
                           quiche_config *config);

I think this API is not sufficient to complete Retry-Initial-Handshake process.

The example text in the specification is not normative, there is no normative text that requires S2 and S3 be different values.

As per @LPardue's comment, this is not a bug, so closing.

As per @LPardue's comment, this is not a bug, so closing.


NB 12.6 install

Hello and all wishes for 2022,
(sorry for question but i'm not into java developpment)
How to install this plugin in Apache Netbeans 12.6 ?

Hey @symio the old plugin portal is gone so you need to build it by your own. Just clone the repo, open the project with NetBeans and build it. At the end you will find the nbm file in the target folder :).

Hello!
Sorry for my bad English.
I try build this project, but I have a error.
BUILD FAILURE
Total time:  10.640 s
Finished at: 2022-01-27T14:50:11+03:00
Failed to execute goal on project nbshell: Could not resolve dependencies for project com.qualixium:nbshell:nbm:1.2.3: Failed to collect dependencies at org.netbeans.api:org-netbeans-api-annotations-common:jar:RELEASE81: Failed to read artifact descriptor for org.netbeans.api:org-netbeans-api-annotations-common:jar:RELEASE81: Could not transfer artifact org.netbeans.api:org-netbeans-api-annotations-common:pom:RELEASE81 from/to netbeans (http://bits.netbeans.org/nexus/content/groups/netbeans): Authentication failed for http://bits.netbeans.org/nexus/content/groups/netbeans/org/netbeans/api/org-netbeans-api-annotations-common/RELEASE81/org-netbeans-api-annotations-common-RELEASE81.pom 401 Repository decommissioned. Please refer to https://netbeans.apache.org/about/oracle-transition.html for more information. -> [Help 1]
To see the full stack trace of the errors, re-run Maven with the -e switch.
Re-run Maven using the -X switch to enable full debug logging.

You should update the RELEASE81 to minimum RELEASE90 or later. I think this will solve the problem. RELEASE* means the platform for NetBeans. RELEASE81 means the API/Packages for NetBeans 8.1 which is very old. We are now close to NetBeans 13.0 which will be RELEASE130 soon. Latest is RELEASE126

You should update the RELEASE81 to minimum RELEASE90 or later. I think this will solve the problem. RELEASE* means the platform for NetBeans. RELEASE81 means the API/Packages for NetBeans 8.1 which is very old. We are now close to NetBeans 13.0 which will be RELEASE130 soon. Latest is RELEASE126

Sorry, but I Have a latest version NetBeans
Product Version: Apache NetBeans IDE 12.6
Java: 17.0.2; Java HotSpot(TM) 64-Bit Server VM 17.0.2+8-LTS-86
Runtime: Java(TM) SE Runtime Environment 17.0.2+8-LTS-86
System: Windows 8.1 version 6.3 running on amd64; Cp1251; ru_RU (nb)
User directory: C:\Users\DimmKo\AppData\Roaming\NetBeans\12.6
Cache directory: C:\Users\DimmKo\AppData\Local\NetBeans\Cache\12.6

It is not about your IDE that you are working with, it is that you need to build the plugin with the correct platform. Just change this: https://github.com/pedrohidalgo/nbshell/blob/master/pom.xml#L177 to that what I mentioned. The plugin is just build with maven but with the platform 8.1. Doesn't matter which IDE you have.

O, Thanks!
I succefull build projectand install plugin after that!
Now syntaxhighlight for my shell script.

Yes !
With pom modification ...
I suggest to write it in the readme for non java developpers on how to install and configure for nb versions.
Btw great job and thanks for the plugin it's better with syntax to work with shell script in ide instead of separated editors.


added decoupler-like API

Hi,
as mentioned, I added a score_cells.run_gssnng() method that works with decouplers input format (genesets as a simple pandas.DataFrame) and output format (storing scores in adata.obsm['estimate_xyz'].
The function is pretty much a wrapper around the existing code that works with Genesets objects for scoring
I had to change the genesets class quite a bit:

constructor takes lists of genesets now (used to be a .gmt file). Added genesets_from_gmt() function to do that instead.
move some methods out of the class, they were static anyways

There's a new notebook in notebooks/gssnng_decoupler.ipynb to showcase the usage. Needs decoupler and omnipath:
pip install --upgrade decoupler omnipath

Maybe we should include that pip command in the notebook too

btw, I just did a quick comparison of gssnng vs other scoring methods (e.g. simple summing up the counts, or more sophisticated things like AUCell) on the PBMCs (notebooks/gssnng_decoupler.ipynb).
For two scoring methods, I calculate the "score" for each cell with each method and look at the correlation of the scores across cells. Here's the result (each panel is a different geneset/signature):

While the three "external" methods seem to correlate reasonably well, gssng is almost uncorrelated. Why is that, am I doing something wrong
-> needs more investigating!

Hmm, well gssnng contains ~6 scoring methods.. which are you using?  Want
to send me the function call?
-dave
On Thu, May 25, 2023 at 12:47 PM redst4r @.***> wrote:

btw, I just did a quick comparison of gssnng vs other scoring methods
(e.g. simple summing up the counts, or more sophisticated things like
AUCell) on the PBMCs (notebooks/gssnng_decoupler.ipynb).
For two scoring methods, I calculate the "score" for each cell with each
method and look at the correlation of the scores across cells. Here's the
result (each panel is a different geneset/signature):
[image: image]
https://user-images.githubusercontent.com/5718498/241016660-f4105854-4fa5-4464-9666-3adba6eabb67.png
While the three "external" methods seem to correlate reasonably well,
gssng is almost uncorrelated. Why is that, am I doing something wrong
-> needs more investigating!
—
Reply to this email directly, view it on GitHub
https://github.com/Gibbsdavidl/gssnng/pull/17#issuecomment-1563424083,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEJFSOHTOFBLYZCSQ2YDILXH6ZONANCNFSM6AAAAAAYOLSXOM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Aucell should be like gssnng “summed_up”
On Thu, May 25, 2023 at 12:47 PM redst4r @.***> wrote:

btw, I just did a quick comparison of gssnng vs other scoring methods
(e.g. simple summing up the counts, or more sophisticated things like
AUCell) on the PBMCs (notebooks/gssnng_decoupler.ipynb).
For two scoring methods, I calculate the "score" for each cell with each
method and look at the correlation of the scores across cells. Here's the
result (each panel is a different geneset/signature):
[image: image]
https://user-images.githubusercontent.com/5718498/241016660-f4105854-4fa5-4464-9666-3adba6eabb67.png
While the three "external" methods seem to correlate reasonably well,
gssng is almost uncorrelated. Why is that, am I doing something wrong
-> needs more investigating!
—
Reply to this email directly, view it on GitHub
https://github.com/Gibbsdavidl/gssnng/pull/17#issuecomment-1563424083,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEJFSOHTOFBLYZCSQ2YDILXH6ZONANCNFSM6AAAAAAYOLSXOM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

here's how I called gssnng (no particular rationale, I think I copied it from another notebook)
score_cells.run_gssnng(
    adata, model, source='source',target='target', weight='weight',
    groupby=None, # "louvain",
    smooth_mode='connectivity',
    recompute_neighbors=0,
    score_method="singscore",
    method_params={'normalization':'theoretical'},
    samp_neighbors=0,
    ranked=True,
    cores=6
)

I tried to disable any sampling, and no splitting into clusters (groupby) to make it as comparable as possible to the other methods

I’ll check this out today, thanks!! I found the new notebook.
On Thu, May 25, 2023 at 6:37 PM redst4r @.***> wrote:

here's how I called gssnng (no particular rationale, I think I copied it
from another notebook)
score_cells.run_gssnng(
adata, model, source='source',target='target', weight='weight',
groupby=None, # "louvain",
smooth_mode='connectivity',
recompute_neighbors=0,
score_method="singscore",
method_params={'normalization':'theoretical'},
samp_neighbors=0,
ranked=True,
cores=6
)
I tried to disable any sampling, and no splitting into clusters (groupby)
to make it as comparable as possible to the other methods
—
Reply to this email directly, view it on GitHub
https://github.com/Gibbsdavidl/gssnng/pull/17#issuecomment-1563701269,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEJFSNQ63CRKNQRTD2AMOTXIACNRANCNFSM6AAAAAAYOLSXOM
.
You are receiving this because you commented.Message ID:
@.***>

It's complicated! My comparison to decoupler was too naive:

gssnng uses adata.X, whereas decoupler (usually) uses adata.raw.X. For the PBMCs thats a huge difference (2k genes vs 13k genes)
I used gssnng with ranks (even for summed_up)
The smoothing itself makes quite  a bit of a difference

I'll try to tease apart the effects of those. For starters, I'll try to make gssnng as similar as possible to the existing methods, adding complexity (smoothing, sampling) in one by one. I'll update the notebook tomorrow

I tried the summed up method, grouped on cluster, and for TRAIL, it agreed
well with the others.
On Sat, May 27, 2023 at 1:54 AM redst4r @.***> wrote:

It's complicated! My comparison to decoupler was too naive:

gssnng uses adata.X, whereas decoupler (usually) uses adata.raw.X.
For the PBMCs thats a huge difference (2k genes vs 13k genes)
I used gssnng with ranks (even for summed_up)
The smoothing itself makes quite a bit of a difference

I'll try to tease apart the effects of those. For starters, I'll try to
make gssnng as similar as possible to the existing methods, adding
complexity (smoothing, sampling) in one by one. I'll update the notebook
tomorrow
—
Reply to this email directly, view it on GitHub
https://github.com/Gibbsdavidl/gssnng/pull/17#issuecomment-1565287437,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEJFSKRIGI3YRGKYIFIPETXIG6KVANCNFSM6AAAAAAYOLSXOM
.
You are receiving this because you commented.Message ID:
@.***>

I tried the summed up method, grouped on cluster, and for TRAIL, it agreed
yeah, summed_up is pretty consistent (it better should, thats as simple as it gets)

I've been playing around with GSEA today, what a mess :)  3 different implementations, 3 different answers:

the ssGSEA implementation in gssnng
my own ssGSEA implementation
decoupler's GSEA version

Some people report the "integral" of the two ECDFs, others the maximum difference... And it makes a difference if you filter out genes not expressed anywhere.
Couldn't get any consistent  results yet

made some progress on the GSEA discrepancies:

There's some odd behavior in ssgsea(), see #20
Gene filtering is a bit unpredictable in gssnng and the total number of genes (in and outside of a geneset) matter.

About 2): There's some unexpected (to me at least) way of how data is sent to those scoring functions in gssnng. In particular its about score_cell_data._get_cell_data(). That function takes the smoothed expression matrix and pulls out a single cell's expression vector as a pd.DataFrame. But it also filters out any non-expressed genes (zero counts) in that cell. This dataframe is then fed to the scoring function.
Here's the filtering code:
gene_mat = (smoothed_adata.obsm['X_smooth'])[cell_ix]
# then we subset it to only the genes with counts
_, gdx, _ = sparse.find(gene_mat)

if gene_mat.ndim == 2:
    df = pd.DataFrame(gene_mat[:, gdx].A.flatten(), index=smoothed_adata.var.index[gdx])  ## ????

Here's the problem with that:

In the scoring function, we now have no idea how big the "universe" of genes is: GSEA computes this running sum for genes in the set, but also for genes outside the set (which we now dont have access too). One can use the dataframes .len() as a substitute (not fully correct of course).
The scoring function receives an expression pd.DataFrame with different length/#genes for each cell due to the above filtering of non-expressed genes. Hence, we can't even compare the scores of individual cells (they all use a different background set)

Filtering away the non-expressed genes is probably done to keep memory low, but it creates this problem.
I don't really know an easy way to fix this atm (anything short of disabling that filtering altogether). We could wrap this dataframe into its own class, SparseExpressionVector, where we keep track of the the expressed genes (in the dataframe) and the universe of all genes in a separate variable and pass that into the scoring functions. But it might get pretty ugly, as it carries into the scoring functions

But overall, if I fix 1) and 2) I get consistent results with GSEA scoring in gssnng and decoupler. We're on the right track!


[nagios] use event_type passed to create_event method

What does this PR do?
use event_type passed to create_event method as the msg_text['event_type'].
Motivation
1200-host-alert-event-incorrectly-shows-up-as-unknown-check
event_payload.pop('event_soft_hard', None) will always be null since none of the event types in EVENT_FIELDS contain an event_type field.
Additional Notes
Review checklist (to be filled by reviewers)

[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] Feature or bugfix must have tests
[ ] Git history must be clean
[ ] If PR adds a configuration option, it must be added to the configuration file.

Looks handled by #3979

haha. you're right. didn't see that; rather > didn't look..
Thanks! closing this one.


BatAlgorithm Implmentation for python > 3.0

There are some minor changes in the BatAlgorithm.py so that it can run in python >3.0

Thank you for your change. I would like to apologize for waiting such a long time.


Setting 'result.rewrite-rule.xsl' does nothing

Hi,
I'm trying to rewrite result file names in HTML5 default transformation.
The parameter 'result.rewrite-rule.xsl' does nothing, I found this related and resolved issue https://github.com/dita-ot/dita-ot/issues/3689.
I tried several version of dita-ot (3.6.1, 4.0.2, 4.1, 4.1.2) to investigate a little bit. From 3.6 to 4.0.2 it worked but after no.
Expected Behavior
setting parameter 'result.rewrite-rule.xsl' should use the provided XSLT file https://www.dita-ot.org/dev/parameters/parameters-base#base__result.rewrite-rule.xsl
Actual Behavior
the parameter seems to be set in buid_preprocess.xml but nothing happen.
Possible Solution
Steps to Reproduce

I'm attaching a little test case testcase.zip, and running this command :
dita-ot-4.1.2/bin/dita --input="testcase/map.ditamap" --format="html5" --verbose --propertyfile="testcase.properties"

Copy of the error message, log file or stack trace
There should be an error because in the XSLT file, there is <xsl:message terminate="yes">Terminate in rewrite-url-output.xsl</xsl:message> but the transformation run without problem
Environment

DITA-OT version: 4.1.2
Operating system and version: MacOS 13.2.1 (22D68)
How did you run DITA-OT? dita command (see above)
Transformation type: HTML5

@jelovirt here "CleanPreprocessModule.init(Map<String, String>)" for the attached project the value of the parameter "result.rewrite-rule.xsl" is "rewrite-url-output.xsl", probably it should have been made an absolute path in the build file.
Besides this, the "CleanPreprocessModule.init" passes the value of the parameter through the catalog resolver which will return null:
 Optional
    .ofNullable(input.get("result.rewrite-rule.xsl"))
    .map(file -> {
      try {
        return catalogResolver.resolve(URLUtils.toURI(file).toString(), null);
      } catch (TransformerException e) {
        throw new RuntimeException(e.getMessage(), e);
      }
    })

so when the catalog resolver returns null, we should probably create a stream source directly over the path to the XSLT.

Hello,
I confirmed the same behavior in my test environment, where parameter result.rewrite-rule.xsl doesn't work as intended. For perspective, I also compared the result to my production environment that doesn't yet use DITA-OT 4.x.
Test DITA environment
In the test environment, I tested the parameter's behavior using two versions of DITA-OT 4.x. These are the only ones I tried, so I can't claim to have tested any other 4.x versions.

DITA-OT 4.1.2 - result.rewrite-rule.xsl only operates correctly when its value is an absolute path.
DITA-OT 4.2.2 - result.rewrite-rule.xsl only operates correctly when its value is an absolute path.

To illustrate, this example won't successfully invoke rewrite.xsl even though it should:
  <target name="custom-rewrite">
    <property name="result.rewrite-rule.xsl" value="${resources.dir}/rewrite.xsl"/>
  </target>

Conversely, when the Ant property is "flattened" so that the resulting value is an absolute path instead, the parameter result.rewrite-rule.xsl correctly invokes rewrite.xsl which successfully renames output files and paths:
 <target name="custom-rewrite">
    <property name="result.rewrite-rule.xsl" value="file:/Users/shocum/docs/myframework/rewrite.xsl"/>
  </target>

We would soon like to transition many authors to DITA-OT 4.x in production, yet we'll be unable to until a DITA-OT 4.x release can once again interpret relative paths and/or Ant properties inside the value of parameter result.rewrite-rule.xsl.
You may reach out to me if I can be of any assistance.
Production DITA environment
In the production environment, I tested the parameter's behavior using DITA-OT 3.7.4.

DITA-OT 3.7.4 - result.rewrite-rule.xsl operates correctly in all cases, such as absolute paths and paths that use Ant properties (i.e. variables).

Environment

DITA-OT version: Reproduced on 4.1.2 and 4.2.2 (the only two I tried), while 3.7.4 operates correctly
Operating system and version: Version 14.4.1 (23E224)
How did you run DITA-OT? Ant build (custom build.xml)
Transformation type: LWDITA (Github-flavored Markdown)

To what value does that ${resources.dir} expand? If it's an absolute file path like "/Users/.. some folder" maybe you need to make it an URL-like file path by prepending "file:" to it or by using the Apache Ant makeurl task:
https://ant.apache.org/manual/Tasks/makeurl.html
If the ${resources.dir} expands to a relative path, then to what folder would you consider that it is is relative to?

Hi @raducoravu,
By placing  <echo message="Resolves to: ${resources.dir}"/> in my main Ant <target>, I get this console output:
(I'm using /pppp/ to obfuscate our company name, but everything else is verbatim.)
[echo] Resolves to: /Users/shocum/cs/projects/product-documentation/frameworks/pppp/resources

I then tried your first hypothesis of prepending with file: to make it URL-like:
  <target name="custom-rewrite">
    <property name="result.rewrite-rule.xsl" value="file:${resources.dir}/rewrite.xsl"/>
  </target>

And...that worked!! 🥇 This is a huge relief, Radu!!
I wonder if OP @ruthrapr needs to try something similar. And more importantly, barring an underlying code change in DITA-OT 4.x, how can we best communicate to all users coming from 3.x that they'd need to make this adjustment? Would this justify an entry in the DITA-OT's Migrating customizations documentation?
Small aside: I'm attending ConVEx '24, so I'll be sure to swing by!

@HocumS according to the example in the docs:
https://www.dita-ot.org/dev/topics/plugin-rewrite-rules
<property name="result.rewrite-rule.xsl"
          value="${dita.plugin.com.example.rewrite.pdf.dir}/custom-rules.xsl"/>

the property should work by giving it an absolute file path (no "file:" prefix necessary). So the fact that the value only works now as an URL-like path is a bug to me (present issue), meaning that probably we should not go around documenting a bug, but maybe fix it by allowing the value to be either a file on an URL-like path.


Performance improvements, safety checks

Reduce amount of calls made to webpack runtime functions when possible
Harden remote loading and initialization against async quirks or poorly implemented remote loading conventions when mixing remote injector tools
Adding my default initialized marker to remote for compatibility with my ecosystem and plugins
Adding Comment blocks for suggested ways to improve performance by executing startup functions in parallel and remote initialization + exposed module get in parallel

Closing the PR because all of the suggested changes were made in another PR


App crashes if marginBottom is a string

The sample crashes if marginBottom is a String. Using a number solves the crash.

Deploy preview for react-native processing.
Building with commit 9173ac30352a803b54247f70b0b672e8462b960c
https://app.netlify.com/sites/react-native/deploys/5e8e5748f8e3740006715292

Good catch, thank you! This should be corrected on the website.
But I assume that the crash is not an expected behaviour in this situation. It seems like Android specific issue. On iOS and Web invalid property is omitted and besides that app is running correctly.
Let me ask you two questions:

Can you reproduce this crash on Android device using Expo example (not web player)?
Did you reported this crash to expo  or  react-native?

Hi.

Yes it repros on Android, both on a real device and using the play on device inside the browser feature.
No, I didn't, it was one of the firsts attempts running react native & expo, so I'm not sure if it's an issue on expo or react native side.

@EzequielB Can you update also versioned docs for 0.62 to fix tutorial linked on the home page?

@Simek can you point me to the branch? I don't seem to get the structure here.

Sure, you can find 0.62 files in website/versioned_docs/version-0.62.


fps++: 1.13.2 Cemu crash

Using fps++ 1.13.2 for BoTW, Cemu crashes after loading/compiling cached shaders.

You should provide your log.txt.
Regardless try cemuhook 5.6.6 and report back.

Same thing with cemuhook 5.6.6.
Here's the log.txt:
log.txt

Alright.  In this log it crashes before it applies fps++ patches.  Maybe it crashes at the exact instance it tries?  I'm not sure.  The crash is in cemuhook though.
Post the log from cemuhook 5.6.8.

It crashes only when fps++ is selected.
Here's the new log:
log.txt

Seems like it crashes in another section and probably has to do with some weird timing. Doubt it's related to graphic packs. Let us know if this is an issue with a new instance of Cemu and an updated Cemuhook.

did you fix it im having the same problem, botw crashes when i enable FPS++ graphics packs cemu 1.15.9c
[00:17:43] ------- Init Cemu 1.15.9c -------
[00:17:43] mlc01 path: D:\Games\Cemu stuff\Cemu Emulator Backup\mlc01
[00:17:43] Cemuhook version: <IP_ADDRESS>
[00:17:43] CPU: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
[00:17:43] RAM: 14458MB
[00:17:43] Used CPU extensions: SSSE3, SSE4.1, AVX2, AES-NI
[00:22:50] Loading U-King.rpx
[00:22:51] Creating OpenGL canvas
[00:22:51] Loaded RPL module u-king (checksum 0x6267BFD0)
[00:22:51] Thread quantum set to 100000
[00:22:51] ------- Loaded title -------
[00:22:51] TitleId: 00050000-101c9500
[00:22:51] TitleVersion: v208
[00:22:51] Update path: \usr\title\00050000\101C9500
[00:22:51] AOC path:    \usr\title\00050000\101C9500\aoc
[00:22:51] Save path:   \usr\save\00050000\101C9500\user
[00:22:51] shaderCache name: dcac9927
[00:22:51] gameprofile path: gameProfiles\00050000101c9500.ini
[00:22:51] RPX hash: fb7911ad
[00:22:52] RPL link time: 187ms
[00:22:52] HLE scan time: 94ms
[00:22:52] ------- Active settings -------
[00:22:52] CPU-Mode: Triple-core recompiler (gameprofile)
[00:22:52] Load shared libraries: true (gameprofile)
[00:22:52] GPUBufferCacheAccuracy: low (gameprofile)
[00:22:52] Use precompiled shaders: auto (gameprofile)
[00:22:52] Full sync at GX2DrawDone: false
[00:22:52] ------- Init OpenGL graphics backend -------
[00:22:52] GL_VENDOR: NVIDIA Corporation
[00:22:52] GL_RENDERER: GeForce GTX 1060/PCIe/SSE2
[00:22:52] GL_VERSION: 4.6.0 NVIDIA 430.86
[00:22:52] Using precompiled shaders: false
[00:22:52] OpenGL extensions:
[00:22:52] ARB_clip_control: available
[00:22:52] ARB_get_program_binary: available
[00:22:52] ARB_clear_texture: available
[00:22:52] ARB_copy_image: available
[00:22:52] NV_depth_buffer_float: available
[00:22:52] Activate graphic pack: The Legend of Zelda: Breath of the Wild - LWZX Crash workaround
[00:22:52] Activate graphic pack: The Legend of Zelda: Breath of the Wild/Mods/Cel-Shading Removal (SkalFate & Altros)/Amiibo Mode [Preset: Plastic %100]
[00:22:52] ------- Init Audio backend -------
[00:22:52] DirectSound: available
[00:22:52] XAudio 2.8: available
[00:22:52] ------- Run title -------
[00:22:53] Shader cache loaded. Commited mem 186MB. Took 1157ms
[00:22:53] Recompiler initialized. CPU extensions: LZCNT MOVBE AVX
[00:22:53] Custom timer mode: QPC
[00:22:53] Applying patch group BotwPlsNoCrashV208 from pack 'The Legend of Zelda: Breath of the Wild - LWZX Crash workaround' v2 to module u-king (checksum 0x6267BFD0)
[00:22:53] IOSU_CRYPTO: No otp.bin found. Online mode cannot be used
[00:22:53] IOSU_CRYPTO: No Seeprom.bin found. Online mode cannot be used
[00:23:46] Applying patch group BotwFPSV208 from pack 'Dynamic Gamespeed' v3 to module u-king (checksum 0x6267BFD0)


Remove request module dependency in v4

Why not let users provide their own request module? request-promise already has request listed as a peer dependency and displays a very descriptive error message when it can't import request so all that need be done is to remove request from the list of dependencies. Just saying, whenever v4 comes around it'd be nice.

This would also emphasize that we're using request-promise by default. Users could always opt to use request as the requester per the example in the root of this repository.

#198 introduces this change.


Why there is no OpenJ9?

Why I could not find builds for OpenJ9 on adoptium.net?
I only can find them on AdoptOpenJDK.net

The Adoptium project charter does not allow for building OpenJ9 builds, but stay tuned as we understand that you will soon be able to get the same OpenJ9 builds you are used to receiving from a new location :-)

Thanks


Setting version @latest for models in YAML pipeline definitions not working

Hi!
According to the docs, one should be able to reference the latest model and environment versions in YAML pipeline definitions with the @latest tag (e.g.: azureml:mymodel@latest).
I registered a custom model to my AML workspace as yolov5.
ml_client.models.get(name="yolov5", label="latest") gives the folllowing output:
Model({
  'job_name': None,
  ...
  'name': 'yolov5',
  ...
  'version': '1',
  'latest_version': None,
  ...
  'arm_type': 'model_version',
  'type': 'custom_model',
  ...
'})

However, when I reference it in the YAML definition with the @latest tag and try to run a job, I get the following error:
$schema: https://azuremlschemas.azureedge.net/latest/pipelineJob.schema.json
type: pipeline

...

jobs:
  my_component_job:
    type: command
    component: ./path_to_component/my_component.yaml
    inputs:
      data: ${{parent.inputs.pipeline_input_data}}
      model: azureml:yolov5@latest
    outputs:
      output_data:

(UserError) The specified resource was not found.
Code: UserError
Message: The specified resource was not found.
Exception Details:      (ModelNotFound) Model container with name: azureml:yolov5 not found.
        Code: ModelNotFound
        Message: Model container with name: azureml:yolov5 not found.

If I reference it with an explicit version number, e.g.: azureml:yolov5:1 the job starts and is executed without any problem.

The relevant Azure service or technology - Azure Machine Learning
A link to the published documentation article that you have feedback about - How to deploy a pipeline to perform batch scoring with preprocessing (preview)

Relevant part in the docs:
$schema: https://azuremlschemas.azureedge.net/latest/pipelineComponent.schema.json
type: pipeline

name: batch_scoring_uci_heart
display_name: Batch Scoring for UCI heart
description: This pipeline demonstrates how to make batch inference using a model from the Heart Disease Data Set problem, where pre and post processing is required as steps. The pre and post processing steps can be components reusable from the training pipeline.

inputs:
  input_data:
    type: uri_folder
  score_mode:
    type: string
    default: append

outputs:
  scores:
    type: uri_folder
    mode: upload

jobs:
  preprocess_job:
    type: command
    component: azureml:uci_heart_prepare@latest
    inputs:
      data: ${{parent.inputs.input_data}}
      transformations:
        path: azureml:heart-classifier-transforms@latest
        type: custom_model
    outputs:
      prepared_data:

  score_job:
    type: command
    component: components/score/score.yml
    inputs:
      data: ${{parent.jobs.preprocess_job.outputs.prepared_data}}
      model:
        path: azureml:heart-classifier@latest
        type: mlflow_model
      score_mode: ${{parent.inputs.score_mode}}
    outputs:
      scores:
        mode: upload
        path: ${{parent.outputs.scores}}

My bad,
If I specify the model with the path and type keys, the @latest tag works as expected.
$schema: https://azuremlschemas.azureedge.net/latest/pipelineJob.schema.json
type: pipeline

...

jobs:
  my_component_job:
    type: command
    component: ./path_to_component/my_component.yaml
    inputs:
      data: ${{parent.inputs.pipeline_input_data}}
      model:
        path: azureml:yolov5@latest
        type: custom_model
    outputs:
      output_data:

I am closing the issue, as it is solved (never was an issue at all).

@pezosanta
It looks like your issue is resolved since you closed this thread.
If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion. Thanks!!!

@ManoharLakkoju-MSFT thanks, I have a separate question.
Where should I make a question/feature request regarding to AML Batch Endpoint invokes?
The feature request would be to create experiment_name, job_name and tags arguments for the ml_client.batch_endpoints.invoke() function.
Should I write an issue on this here, or on another forum?

@pezosanta
You can submit your feature request or bug report on the Azure Machine Learning feedback forum. This forum is monitored by the Azure Machine Learning product team and they will be able to provide you with more information on the status of your request. Here is the link to the forum: https://feedback.azure.com/forums/34192--general-feedback.


⚠ Bofrost.lu has degraded performance

In 73ecee4, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1192 ms

Resolved: Bofrost.lu performance has improved in 4200245 after 13 minutes.


python37Packages.ldap3: 2.5.1 -> 2.5.2

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/python3.7-ldap3/versions.
meta.description for python37Packages.ldap3 is: '"A strictly RFC 4510 conforming LDAP V3 pure Python client library"'.

Checks done (click to expand)

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.5.2 with grep in /nix/store/1ms7g8cgwl40dlx1za8sv9nxrcl4x19j-python3.7-ldap3-2.5.2

directory tree listing: https://gist.github.com/1d81849a800bec2d643b36807d36edd9

du listing: https://gist.github.com/8fc5a7a77eb61ecbfdb41ffdf6a7c091

Rebuild report (if merged into master) (click to expand)

19 total rebuild path(s)
5 package rebuild(s)
5 x86_64-linux rebuild(s)
5 i686-linux rebuild(s)
4 x86_64-darwin rebuild(s)
5 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
matrix-synapse
mitmproxy
python27Packages.ldap3
python37Packages.jupyterhub-ldapauthenticator
python37Packages.ldap3

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1ms7g8cgwl40dlx1za8sv9nxrcl4x19j-python3.7-ldap3-2.5.2 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A python37Packages.ldap3 https://github.com/r-ryantm/nixpkgs/archive/eb641d59d5444bb2ec1d04101c5bc73fc4ca8c99.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1ms7g8cgwl40dlx1za8sv9nxrcl4x19j-python3.7-ldap3-2.5.2
ls -la /nix/store/1ms7g8cgwl40dlx1za8sv9nxrcl4x19j-python3.7-ldap3-2.5.2/bin

@FRidh do you know what's going on (on PyPI, probably)?
PyPI links to source tarball with empty ldap3/protocol/sasl/digestMd5.py, even though the linked egg contains a non-empty file at this location. Upstream GitHub repository also contains a nonempty file.
Should I switch src to the GitHub release tarball?

No idea. Go ahead.

f27fe449b10c65830a2f27cae5d3213077b6f07e


Week 10 plan

Fake permalink, fake video watch practice.
Review exercise 4.1-4.3

https://github.com/AmyChen20021003/110-1-r4ds-main/blob/7bb5df0498f2279fa9c2a3800eb9cb1e56e7d16f/week10.Rmd#L3


Thanks!

No problems. Just a hearty :+1: for putting this together. Cheers!

Long overdue: thank you! Cheers!


THRIFT-4984: Handle wrapped io.EOF errors

Client: go
TCompactProtocol (which is used by THeaderTransport to read headers)
could wrap the underlying error with TProtocolException, which breaks
err == io.EOF test in some cases.

@dcelasun Sorry we have to do this yet again :(


[Bug]: Unable to view/edit AWK (.awk) files via the built-in code editor

Current Behavior
You can see below that I opened the awk file in question in the bottom pain via: wsh view assert.awk and got the message: Preview (application/x-awk) instead of seeing the code. I then also printed the file in the shell pane via cat assert.awk to illustrate that there is indeed AWK code in the file. I tried this on multiple .awk files in multiple locations, with and without spaces or other characters that need to be properly escaped in their path. All produced the same result. So my test from the screenshot below was as simple as possible, using an .awk file in the current working directory:

Expected Behavior
We should get a syntax-highlighted, editable copy of the code in the said .awk file.
We should be able to read and edit the code as with other file types.
Steps To Reproduce

Open an awk file in the editor via: wsh edit myawkfile.awk
Notice that you see only the message: Preview (application/x-awk)

No code is displayed.
No syntax highlighting

Wave Version
v0.9.0
Platform
Windows
OS Version/Distribution
Windows 11 - v: 22H2 - b: 22621.4317
Architecture
x64
Anything else?
No response
Questionnaire

[ ] I'm interested in fixing this myself but don't know where to start
[ ] I would like to fix and I have a solution
[ ] I don't have time to fix this right now, but maybe later

thanks for reporting, those should definitely be editable.  will be fixed in the next release

fixed in v0.9.1


[Sonarqube] - Onboard Now

Hi :wave:
This PR has been created to help your team integrate SonarQube with this repo.
Next Steps:

We have added a template sonar-project.properties file so that all you have to do is update the details to match your repository's structure. Please refer to the  Onboarding Steps for further details on how to complete SonarQube configuration.

To automatically execute the SonarQube analysis and upload the results please add the following snippet to your github workflow to run the SonarQube analysis for your PRs and on merge to master:

name: SonarQube
on:
  pull_request:
  push:
    branches: master

jobs:
  main:
    runs-on: [self-hosted,zendesk-stable]
    name: Test and SonarQube
    steps:
      - uses: zendesk/checkout@v2
      - ...
      - ...
      - name: SonarQube scan PR
        if: github.event_name == 'pull_request'
        run: |
          sonar-scanner \
          -Dsonar.host.url="${{ secrets.SONARQUBE_HOST }}" \
          -Dsonar.login="${{ secrets.SONARQUBE_TOKEN }}" \
          -Dsonar.sourceEncoding=UTF-8 \
          -Dsonar.pullrequest.base="${{ github.base_ref }}" \
          -Dsonar.pullrequest.branch="${{ github.head_ref }}" \
          -Dsonar.pullrequest.key="${{ github.event.number }}" \
          -Dsonar.pullrequest.github.repository="zendesk/${{ github.event.repository.name }}" \
          -Dsonar.scm.revision="${{ github.event.pull_request.head.sha }}"
      - name: SonarQube scan master \
        if: github.event_name == 'push' && github.ref == 'refs/heads/master'
        run: |
          sonar-scanner \
          -Dsonar.host.url="${{ secrets.SONARQUBE_HOST }}" \
          -Dsonar.login="${{ secrets.SONARQUBE_TOKEN }}" \
          -Dsonar.sourceEncoding=UTF-8 \
          -Dsonar.branch.name=master

Please feel free to reach out to us on #ask-sonarqube for any additional details or support.
If you think this PR is not relevant for your repository please comment why and close.
Thank you!
cc @zendesk/test-frameworks

Hi Team,
We are reaching out as we have not seen any action from your side on this PR for the last 2 weeks.
We are trying to onboard all the repositories by the 30th of October 2020 and require your support for the same.
For any queries or support please reach out to us on #ask-sonarqube
For more information please refer: ADR
Thank you!
PS: If your application is internal or non-production and you think that SonarQube integration is not important for this repository please feel free to close the PR with a suitable comment.

Closing this as Sonarqube is not required for public repositories


nbd: add patch to fix reading port setting from nbdtab

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 285431 run on x86_64-linux 1

27 packages marked as broken and skipped:

libvmi
qemu_xen
qemu_xen-light
qemu_xen-light.debug
qemu_xen-light.ga
qemu_xen.debug
qemu_xen.ga
qemu_xen_4_15
qemu_xen_4_15-light
qemu_xen_4_15-light.debug
qemu_xen_4_15-light.ga
qemu_xen_4_15.debug
qemu_xen_4_15.ga
qubes-core-vchan-xen
xen
xen-guest-agent
xen-light
xen-slim
xenPackages.xen-light
xenPackages.xen-slim
xenPackages.xen-vanilla
xenPackages.xen_4_15-light
xenPackages.xen_4_15-slim
xenPackages.xen_4_15-vanilla
xen_4_15
xen_4_15-light
xen_4_15-slim

1 package built:

nbd


sdkconfig files ignored

I tried building on Windows and the stack always overflows after drawing text with feature ttgo. I tried cargo clean; cargo +esp build --release to no avail. CONFIG_ESP_MAIN_TASK_STACK_SIZE=20000 is set in sdkconfig.defaults and I tried duplicating it in sdkconfig.defaults.esp32, again clean and build but still no luck, still overflows, I also tried doubling that value, same result. Eventually I suspected that it's ignored.
I tested if the files actually get picked up by checking the stack size at runtime and as suspected, it's too small:
if esp_idf_sys::CONFIG_MAIN_TASK_STACK_SIZE < 20000 {
    error!("stack too small: {} bail!", esp_idf_sys::CONFIG_MAIN_TASK_STACK_SIZE);
    return Ok(());
}

Prints the idf-sdk default value:
E (296) rust_esp32_std_demo: stack too small: 3584 bail!
The only non-standard conf I have is that I've set the following env var:
$Env:CARGO_TARGET_DIR="C:/espt/"
Because It's the only way I could get the paths short enogh to not get CMake build errors about path length. Perhaps that could be the cause. Any ideas?

I tried copying the sdkconfig files to C:/ and indeed that works, so I suppose they are assumed to be in target/.. I'll leave this open as the problem with path lengths causes this in the first place. Perhaps the problem with path length could be fixed somehow or perhaps it's possible to modify the build process to sdkconfig files are searched for in the project root rathet than target/..

Hi i can reproduce this bug on linux too, is there any workaround to set the MAIN_TASK_STACK_SIZE on linux ?

Hi i can reproduce this bug on linux too, is there any workaround to set the MAIN_TASK_STACK_SIZE on linux ?

Yes, just place your sdkconfig.defaults file in the parent directory of your target directory. Unless you've overridden the target directory with CARGO_TARGET_DIR as the original poster did, the parent of your target directory is the binary crate directory itself.

I'd like to add that if your binary is part of a cargo workspace, the sdkconfig.defaults file has to be in the root directory of the workspace and not of the binary (found that out through trial and error).

I'd like to add that if your binary is part of a cargo workspace, the sdkconfig.defaults file has to be in the root directory of the workspace and not of the binary (found that out through trial and error).

That's true and that's usually the culprit.

Just for forgetful people digging up old projects which do not compile due to "ignored sdkconfig.defaults": Don't forget, that in .cargo/config.toml one can set funny things, such as:
[env]
ESP_IDF_VERSION = { value = "release/v4.4" }
ESP_IDF_TOOLS_INSTALL_DIR = {value = "global"}
ESP_IDF_SDKCONFIG_DEFAULTS = { value = "/path/to/sdkconfig.defaults" }
# or
# ESP_IDF_SDKCONFIG_DEFAULTS = { value = "sdkconfig.defaults", relative = true }


illuminate/database not working on PHP 7?

I'm using "illuminate/database": "5.2.7" in my Slim3 app, and when I use save() on Model, it throws internal server error.
Is it compatible with PHP/7.0.0-dev?

Insufficient information. Please create a new issue if you'd like to provide more information.


Adds Splunk alert webhook payload and result retrieval info

This adds info to the DEVELOPMENT.md file about Splunk Alert SIDs and webhook payloads, and retrieval of search results.
Signed-off-by: Chris Collins<EMAIL_ADDRESS>

/lgtm


python3Packages.sentry-sdk: disable tests

Description of changes
disable tests in the wake of Flask and Werkzeug update. Also disable failing tests on non-x86_64-linux architecture.
Fixes #169130
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review run on x86_64-linux 1

3 packages marked as broken and skipped:

python39Packages.spacy
python39Packages.spacy-transformers
python39Packages.textacy

3 packages failed to build and already failed to build on hydra master:

alerta-server: log was empty
gns3-gui: log was empty
gns3-server: log was empty

11 packages built:

cura
home-assistant-component-tests.sentry
moodle-dl
moz-phab
netbox
openai (python39Packages.openai)
python39Packages.django-rq
python39Packages.sentry-sdk
python39Packages.spacy-loggers
python39Packages.wandb
tribler

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 169414 run on aarch64-linux 1

6 packages failed to build and already failed to build on hydra master:

alerta-server: log was empty
gns3-gui: log was empty
gns3-server: log was empty
openai: log was empty
python39Packages.spacy-loggers: log was empty
python39Packages.wandb: log was empty

2 packages failed to build and are new build failures:

netbox: log was empty
(python39Packages.openai): log was empty

7 packages built:

cura
home-assistant-component-tests.sentry
moodle-dl
moz-phab
python39Packages.django-rq
python39Packages.sentry-sdk
tribler

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 169414 run on aarch64-linux 1

6 packages failed to build and already failed to build on hydra master:

alerta-server: log was empty
gns3-gui: log was empty
gns3-server: log was empty
openai: log was empty
python39Packages.spacy-loggers: log was empty
python39Packages.wandb: log was empty

2 packages failed to build and are new build failures:

netbox: log was empty
(python39Packages.openai): log was empty

7 packages built:

cura
home-assistant-component-tests.sentry
moodle-dl
moz-phab
python39Packages.django-rq
python39Packages.sentry-sdk
tribler


Add an output to export resource_id

what

Exports the resource_id

why

The resource_id is needed in order to create a least-privileges IAM policy to provide using RDS IAM authentication.

references

Use closes #111

/test all


Migrations should not be modified

I've noticed some changes to migrations that might have been applied.
This will need to be rolled back, as these migrations will not be applied again.
It might be a good idea to verify with git that all migrations that existed in current live (i.e. 0a17f268ecd3f633bb0643bcde73854639af8d69) have not been changed in current master.

@M4rkD Does M4rkD#3 close this issue or is there more to come?

I haven't checked the migrations against live yet.

Checked all migrations, and the ones which existed in the production server are now the same in development.


Java: In Java, there should be a constructor for ChatMessageContent that just takes required inputs

Today, there's a constructor that accepts just the role and string content. The other common scenario is to provide just the role and an array of content items. The second scenario does not have a constructor (that doesn't force the user to provide null values for all the other properties).
Default values should be available for the following properties when the message comes from a user:

modelId
innerContent
encoding
metadata

Below is the current signature
 public ChatMessageContent(
    AuthorRole authorRole,
    List<KernelContent<T>> items,
    String modelId,
    T innerContent,
    Charset encoding,
    FunctionResultMetadata metadata) {
    super(innerContent, modelId, metadata);
    this.content = null;
    this.authorRole = authorRole;
    this.encoding = encoding != null ? encoding : StandardCharsets.UTF_8;
    this.items = new ArrayList<>(items);
}
`java

Nvm, found the nullable one


IndexError: list index out of range

Looking for old dir at ./stls/agentsmith99\GrotMeks-Trakta-Gun-Warehammer-40K Copying 0 unchanged files. Downloading 11 new files of 11 Downloading 13 images. Downloading license Downloading thing 9 - 3170298 [0, 22, 2018] [0, 22, 2018] [0, 22, 2018] [0, 22, 2018] [0, 22, 2018] [0, 22, 2018] [0, 22, 2018] [0, 22, 2018] [0, 22, 2018] [0, 22, 2018] [0, 22, 2018] [0, 22, 2018] [0, 22, 2018] [0, 22, 2018] [0, 22, 2018] [0, 22, 2018] [0, 22, 2018] Looking for old dir at ./stls/agentsmith99\Grot-Hanomag-Warhammer-40K Traceback (most recent call last):   File "D:\waste\thingygrabber\thingy_grabber.py", line 660, in <module>     main()   File "D:\waste\thingygrabber\thingy_grabber.py", line 648, in main     Designs(user, args.directory, args.quick).download()   File "D:\waste\thingygrabber\thingy_grabber.py", line 241, in download     RC = Thing(thing).download(self.download_dir)   File "D:\waste\thingygrabber\thingy_grabber.py", line 433, in download     new_last_time = new_file_links[0].last_update IndexError: list index out of range
This was done using thingy_grabber.py -d .\stls\ user agentsmith99
That's not the only user I'm getting it on.  Just incase you think it's an isolated case.  AntomanElven\Lucius-Pattern-head-for-Mars-Warlord-Titanicus-scale is another.  So far I've gotten it about 4 times today on different ones.

interesting, so it thinks the model has been updated, but none of the files have newer timestamps. Possibly a readme change or something?

In my list of 150 odd users to grab it's happening quite frequently.
On Mon, Apr 6, 2020 at 10:39 PM Oliver Matthews<EMAIL_ADDRESS>wrote:

interesting, so it thinks the model has been updated, but none of the
files have newer timestamps. Possibly a readme change or something?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cwoac/thingy_grabber/issues/5#issuecomment-609768932,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABE665ZWTOD2FRKS5DHC6ETRLHEQLANCNFSM4L7T2AVA
.

Turned out to be an actual bug rather than just another thingiverse edge case - parsing dates was broken for things where all the files were in October, after the 9th (would also have been wrong for some others, but wouldn't have failed).
Fixed by 1267e583c51d66001bf9aeac090ddd37132ee027


UI enhancements for datatable, header, etc.

[x] in all datatables, action column should have min length zero
[ ] #1744
[x] folders and files should be shown in one table (first folders, then files)
[x] create/update folder should be done in modal
[x] create/update file should be done in modal
[ ] #1743
[x] add download button to file
[x] add a row in datatable (first row) for linking to parent folder
[x] develop new button components being used in page headers and action sections in datatables

All of these tasks are done except 2 task which has dedicated issue


Support child windows in Windows

This PR adds support for child (with type WS_CHILD) windows in Windows.
Main difference between a tooltip window and child window is that the child:

Moves along with the parent and,
Cannot leave parent's client area.

Sounds good! I'm a bit confused about the comment though (and please bear in mind that I know almost nothing about the win32 API).

which part of this PR deals with the child-following-parent behavior? Is that something automatic when you use WS_CLIPCHILDREN?
what do you mean by "cannot leave the parent's client area," and where is that implemented? Is the dropdown allowed to "stick out" past the edge of the parent window? What happens if the dropdown is bigger than the parent?

I know at some point we discussed having children follow parents, but I don't remember where it was or what the outcome of the discussion was. But it's a decision that should be made intentionally and then documented. Right now, the only documented difference between WindowLevel::Tooltip and WindowLevel::DropDown is that they have different z-order. That makes me reluctant to introduce platform-specific changes without at least thinking about the cross-platform story.

which part of this PR deals with the child-following-parent behavior? Is that something automatic when you use WS_CLIPCHILDREN?

No. It's the WS_CHILD flag that is passed when creating the sub/child window. Windows created with this flag are only visible in parent's client. The only thing that sticks out in this PR is the flag WS_CLIPCHILDREN. In Windows, a paint message (specifically WM_PAINT) is generated in response to update regions. If parent/child update regions overlap, then a paint message is sent to parent first and then to all its children allowing children to re-paint themselves in case parent painted on top of them in first paint message. This flag basically tells Windows NOT to send us the second paint message. And in druid land this makes sense because if child needs to be painted/re-painted, we invalidate it separately which in turn would generate child specific WM_PAINT messages. Paint message for child will NOT generate another paint message for its parent.
TBH all this information is dispersed. But the meat of it is here.

what do you mean by "cannot leave the parent's client area," and where is that implemented? Is the dropdown allowed to "stick out" past the edge of the parent window? What happens if the dropdown is bigger than the parent?

All of the heavy lifting is does by Windows. Children are clipped if they do stick out.

That makes me reluctant to introduce platform-specific changes without at least thinking about the cross-platform story.

That is good point. I honestly dont know how children are implemented in other platforms. Or if that concept even exists. That's why this PR has only Windows specific changes. I think it is fine to introduce something that is platform specific without changing shell API.

I also forgot to include documentation for this new sub-window. But now I guess that'll depend on whether the the rationale behind this PR is accepted.

I see, thanks for the explanation.
The mental model I have for a "window" (based on linux, and I think it also applies to mac) is that it's basically a region that handles events and draws itself. The OS/window manager/compositor is in charge of positioning the windows, which includes giving them a z-order and figuring out which parts of which windows are visible. This makes WS_CLIPCHILDREN pretty confusing to me, because it goes against this mental model: I expect the parent to draw itself, the child to draw itself, and the OS to be in charge of presenting those drawings on screen.
Anyway, so my main opinion here (and I'm happy to get push-back, also cc'ing @cmyr who may have thoughts) is that we do not want to clip the children when they stick out: as far as I understood it (and bearing in mind that I'm working in the mental model above, which might not be the best one) the entire point of spawning new windows was to allow them to stick out if they're too big. For example, if we only wanted druid to support tooltips that stay in the main window, we'd just use a druid widget instead of bothering with all the portability issues that platform windows bring.
I have fewer opinions about the child-window-follows-parent thing, mainly just that whatever we decide on should be consistent across platforms and documented.

This makes WS_CLIPCHILDREN pretty confusing to me

WS_CLIPCHILDREN is a window style and window styles are used abundantly in win32 platform code.
Every platform is different. If it's easier to do thing X in one platform should we not do it because it is unavailable in others? Should we ignore it for the sake of platform consistencies?
I would like to emphasize that we can take up a platform specific feature iff it doesnt break shell API contract.
FYI, Im not trying to be difficult. Dont get me wrong. I truly appreciate all your responses

I am also confused by the "child cannot leave parent's client area". If this is intended to be used mainly for things like combo-boxes, I would expect that the child would, in some circumstances, need to draw outside of the parent's frame. Is this not a convention on windows?

This makes WS_CLIPCHILDREN pretty confusing to me

WS_CLIPCHILDREN is a window style and window styles are used abundantly in win32 platform code.

Sorry, I didn't express myself clearly. I wasn't trying to say that anything is wrong with WS_CLIPCHILDREN. I was just trying to explain why I need so much help understanding this: because it doesn't match my internal mental model.
Also, I appreciate your responses and I don't think you're being difficult at all. In fact, I think this sort of discussion is exactly what we need in order to have druid-shell behave sanely across platforms.
Anyway, I think the key here is to identify:

what kind of behavior can be implemented (glitch-free and with reasonable performance) across platforms, and
what is the use-case in druid.

My concern about windows-leaving-the-parent-rect was motivated by point 2, because my understanding behind the motivation for child windows was that sometimes we want dropdowns or tooltips or dialogs to be able to extend past the parent. For example, here is how firefox behaves on my system if it has a very small window:

@cmyr

I am also confused by the "child cannot leave parent's client area". If this is intended to be used mainly for things like combo-boxes, I would expect that the child would, in some circumstances, need to draw outside of the parent's frame. Is this not a convention on windows?

What Im trying to say is if a window might lay completely/partially outside parent, then it is tooltip. Not a child.
This PR allows users to pick what behavior they want. If they want a window to not cross parent boundary AND move along with parent then they have to use WS_CHILD. If not, they can use tooltip (ie a WS_POPUP).
It falls down to how end users utilize these windows.
In Intellij (Ctrl + Q) shows me a tooltip. But it would have been better if it was a child so it doesnt obscure the app behind it.

@jneem
That is an instance of a tooltip. Firefox also has a child instance. Eg:

Suggestions dropdown does not cross parent. It must be a child. They very well could have made it a tooltip.
Again, it goes back to what end users want.

All this also raises another question: can we not have a tooltip that follows the parent when it is dragged? This will remove the need to have a WS_CHILD. But I think redrawing/re-painting_ wont be as smooth. I might be wrong.
Another question: what about modals? They definitely should move with parent and lay within parent. So they cannot be tooltips.

Thanks for the example, that definitely helps me. (I do think there is some possibility for cross-platform terminology issues, because at least the way that the word "tooltip" is used in WindowLevel -- which I think was inspired by the mac terminology -- it only refers to the z-order, and not to any other aspect of the window behavior.)
So as far as I understand it:

there is a use-case for things that are restricted by the parent window. (I hesitate to use the word "clipped" because I think the real desired behavior involves them being aware of the size constraints and adapting appropriately.)
there is a use-case for things that are not restricted by the parent window.

In both cases, it may be desirable to have them follow the parent when dragged, but maybe in the second case it can't be made smooth on Windows?
I agree that it would be nice for modal dialogs to move with the parent, although I'm not sure about them being restricted to it. Here's an example of a file dialog that doesn't fit in my firefox window, and I think I like the fact that it doesn't get constrained or clipped:
Anyway, my main question is: for case (1) above, is it necessary to have them backed by a child window from the operating system? Like, if I want a dropdown-like widget in druid and I want it to always remain within the bounds of the parent window, couldn't I just implement it as a widget?

for case (1) above, is it necessary to have them backed by a child window from the operating system? Like, if I want a dropdown-like widget in druid and I want it to always remain within the bounds of the parent window, couldn't I just implement it as a widget?

I guess you can. I say guess because I dont know if z-order indexing is implemented in druid today. And also it will get complicated real quick (not saying we shouldnt do something just because it is complicated). Like you said (and Manmeet) in Zulip topic:

Would that complex logic not apply to your widget dropdown?

Just out of curiosity, I did a search on child windows in gtk and macos.
I didnt find much in gtk at all. Leading me to believe it either doesnt exists or is difficult to implement.
But in macos there is such concept. And from the description it is exactly what Windows has.
So, for gtk, we might have to this the widget way like you are suggesting. And if it done with widgets, then it will be platform independent which will address your platform consistency concern.
Is that the point you are trying to make?

@cmyr what are you thoughts on this?
There have been many attempts in the past to address this most notably #429. But what I want to ask you is not addressed anywhere.
There are two categories of sub windows. Ones that are unbounded (maybe drawn outside parent) and ones that are bounded (lie wholly within parent). Context menus are a good example. Here's example from Firefox and VSCode respectively:

Two things to keep in mind in VSCode image:

VSCode is painting context on the left because there isnt enough space on right. (Normally it is painted right)
The context follows the parent (like in issue description). I havent attached a gif but trust me on this.

Should druid support both types of contexts?

VSCode doesn't actually do any of this intentionally. They are highly limited by electron / the web model that doesn't allow them to have proper child windows / drop downs, so they have to bind it to the parent window. This isn't intentional.

Users requesting something similar is a fair request.

I some how managed to F this branch up. :(
Please see https://github.com/linebender/druid/pull/2087.


This condition will always return 'false' since the types 'true' and 'false' have no overlap

**TypeScript Version: "typescript": "^3.2.2"
This is an asynchronous method that controls its pause externally, so it needs to be removed at the right time. However, an error warning was given to indicate that this method is not feasible.
  public async show() {
    this.showing = true;
    while (this.showing) {
      for (const frameKey in DogDto.EffectSaveInfo) {
        // [ts] This condition will always return 'false' since the types 'true' and 'false' have no overlap.
        if (this.showing === false) {
          this.container.removeAllChildren();
          break;
        }
        const frameInfo = DogDto.EffectSaveInfo[frameKey];
        const frameIndex = Number(frameKey);
        const frameBitmap = await BitmapUtils.getBitmap(DogDto.EffetcSaveImageList[frameIndex]);
        frameBitmap.x = -1 * frameInfo.origin.x;
        frameBitmap.y = -1 * frameInfo.origin.y;
        container.removeAllChildren();
        container.addChild(frameBitmap);
        await LarkDate.delay(frameInfo.delay);
      }
    }
  }
  public hide() {
    this.showing = false;
  }

usage
  public async showEffect() {
    this.effectSave.show();
    await LarkDate.delay(3 * 1000);
    this.effectSave.hide();
  }

Looks like control flow needs to be more pessimistic around await.

Temporarily changed to recursive writing    :)
public async show() {
    this.showing = true;
    const container = this.container;
    const frame = DogDto.EffetcSaveImageList[0];
    const frameInfo = DogDto.EffectSaveInfo[0];
    const bitmap = await BitmapUtils.getBitmap(frame);
    bitmap.x = -1 * frameInfo.origin.x;
    bitmap.y = -1 * frameInfo.origin.y;
    container.addChild(bitmap);
    await this.play();
  }
  private async play() {
    const container = this.container;
    for (const frameKey in DogDto.EffectSaveInfo) {
      const frameInfo = DogDto.EffectSaveInfo[frameKey];
      const frameIndex = Number(frameKey);
      const frameBitmap = await BitmapUtils.getBitmap(DogDto.EffetcSaveImageList[frameIndex]);
      frameBitmap.x = -1 * frameInfo.origin.x;
      frameBitmap.y = -1 * frameInfo.origin.y;
      container.removeAllChildren();
      container.addChild(frameBitmap);
      if (this.showing === false) {
        this.container.removeAllChildren();
        break;
      }
      await LarkDate.delay(frameInfo.delay);
    }
    if (this.showing === true) {
      await this.play();
    }
  }
  public hide() {
    this.showing = false;
  }

This is basically the same as calling a function, method or callback that could modify a narrowed variable. There should be plenty of duplicate issues, IIRC there was at least one regarding await.
The proposed solution was using a method to retrieve the value instead of accessing the property directly.

yes,  it work ...
class Test{
  private status = false;
  public async test(){
    while(this.status){
      if(this.getStatus() === false){
        break;
      }
    }
  }
  private getStatus(){
    return this.status;
  }
}


Make ResourceProfiler more robust

Previously processes could be dropped after a tracking loop was started,
which may lead to an exception due to trying to get memory/cpu info from
a dead process. This PR fixes this to handle dead processes whenever
information is recorded.
Fixes #2284.

+1


Do you any algorithm in Assembly Language?

Hi, everyone!

Do you know any algorithm implementation in any language, that you wanna share with us?

Open a pull request in any of the programming languages available, or in Assembly this case

I added KMP string search algorithm, which I have implemented a long while ago for a school homework. (PR #7 )


input-group-addon and alpha6

.input-group-addon no longer works with alpha6 (tested with codepen in README)

Thanks for reporting! Actually I already fixed that (421c32327234a854a57e8fcb2f5e175b403f8cda).
Release is coming! You can already checkout alpha.6 demo here: https://bootstrap-kit.com/.

Ok- it will be in v4.0.2.


Error after installing HA Core 2024.2.2

Hi,
after update all entities are no longer available.
Any infos what I can do?
Regards
Michael
This is the error log:
Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:344
Integration: Sensor (documentation, issues)
First occurred: 12:28:40 (1 occurrences)
Last logged: 12:28:40
Error while setting up mobile_alerts platform for sensor
Traceback (most recent call last):
File "/config/custom_components/mobile_alerts/sensor.py", line 430, in fetch_data
async with session.post(url, data=json_data, headers=headers) as response:
File "/usr/local/lib/python3.12/site-packages/aiohttp/client.py", line 1194, in aenter
self._resp = await self._coro
^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/client.py", line 605, in _request
await resp.start(conn)
File "/usr/local/lib/python3.12/site-packages/aiohttp/client_reqrep.py", line 961, in start
with self._timer:
File "/usr/local/lib/python3.12/site-packages/aiohttp/helpers.py", line 735, in exit
raise asyncio.TimeoutError from None
TimeoutError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/config/custom_components/mobile_alerts/sensor.py", line 163, in _async_update_data
return await self._mobile_alerts_data.fetch_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/mobile_alerts/sensor.py", line 457, in fetch_data
raise ApiError()
custom_components.mobile_alerts.sensor.ApiError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 313, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/mobile_alerts/sensor.py", line 165, in _async_update_data
raise UpdateFailed(f"Error communicating with API: {err}")
homeassistant.helpers.update_coordinator.UpdateFailed: Error communicating with API:
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 344, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/mobile_alerts/sensor.py", line 121, in async_setup_platform
await coordinator.async_config_entry_first_refresh()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 285, in async_config_entry_first_refresh
raise ex
homeassistant.exceptions.ConfigEntryNotReady: Error communicating with API:

Hi,
its magic. I am getting again data.
Now HA is running on OS 12.0 and core 2024.2.3


Link to Python set up instructions is broken

In this section: https://github.com/nasa/HLS-Data-Resources#prerequisitessetup-instructions there is a link to python set up instructions (https://github.com/nasa/LPDAAC-Data-Resources/setup/setup_instructions.md) that reports as Not Found.

This issue is resolved.


Add IntentMessage filter;

@BillZengMSFT,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Fixing must-gather ceph resources accordind to shell check

/assign @ashishranjan738

@crombus I think this PR needs a rebase.

/ok-to-test

/retest

/lgtm

https://github.com/openshift/ocs-operator/issues/235


Copy to clipboard

Please add option to automatically copy to clipboard, including when making notes or highligts. This is my final showstopper to replace Windows own snipping tool that will be abandoned by Microsoft and replaced by fat bloatware app. Thanks.

Done. Check out the latest release:
https://github.com/ryanries/SnipEx/releases/tag/v1.3.27

Thank you so much, exactly like i wanted, copies changes too like windows snipping tool. Thank you.


I've improved the Sentiment-Analyzer project and included it in the awesome-streamlit.org gallery. Hope it's ok?

Hi Patidar
I'm reaching out because I saw your awesome Sentiment-Analyzer-Tool developed in Streamlit.
I think it's so awesome that I wanted to included it in the awesome-streamlit.org Gallery. I hope that is OK?
In order to include it I had to refactor it so that the files are not loaded from the file folder.
And then I took a look and did a larger refactoring of the layout and flow. After that I thought that I had done so many things that it was ok to credit the two of us in the way shown below. I hope it is Ok?

You're welcome to publish your awesome streamlit examples with you as Author at https://github.com/marcskovmadsen/awesome-streamlit. It's only a pull request away :-)
Please note I have yet to solve some performance issues on Azure where it's deployed. The awesome-streamlit app is really fast locally :-)
Thanks.
Marc

Thanks, @MarcSkovMadsen for including my project and I am good with the improvements you have done.


Junit Tests

Ensure we are asserting the correct behaviour

I went through the entire test code and based on what i could see, the JUnit asserts are correct. The tests seem to be on target (Except for 1 i think).
Could possibly use one more revision by someone else to make sure we catch all the assert problems (if any are left).


check txn receipt for transfer

This PR fixes the wallet spend error for eth wallet.

Coverage remained the same at 39.505% when pulling 81ad177a2dd87851d7ec3217bbd2ca7cca28f1a7 on fix_wallet_spend into 0e1f030aeecd9b33e308e2135edf29e24c3de5ea on ethereum-master.


Linearize first layer

I want to linearize my first later and combine the outputs of my first layer to a single activation function in the second layer. Would this be possible.
i tried initializing the model as linear but when training, the activation functions in the first layer also become non linear. I know this is not the right approach however, i would appreciate any feedback.
For instance like this:
model = KAN(width=[input_feature_length,1, 1], grid=10, k=2, seed=0, base_fun=lambda x: x, noise_scale = 0.0)
Any help or guidance would be appreciated.

you can use the class multiKAN, which contains a base_func identity.

yes, KAN(..., base_fun='identity', ...) should work

I tried it and it resulted in linear activation on all layers. I was wondering if there was a way where one could have different activation for different layers? For example linear in the first layer and silu on the second.


Pixelated search results

Hello @little-wow, this is the result of a tradeoff between a filled masonry layout grid and a grey-area padded one. These thumbnails must have been very small in dimension, particularly width, and were therefore stretched out to fill the width of the column. If the results appear pixelated, try checking the option at the top right corner:

[x] Prevent overscaling

This should return them to their actual, smaller size and get rid of pixelation.

Okay, thanks, that worked, but I don't think that's intuitive as a design function for a few reasons:

As an average user, I'm not sure what overscaling means without a few seconds of thought
It's all the way to the right and not within my field of vision. I'd suggest maybe moving it up closer to the search results.

@little-wow now that you've experienced the option, what according to you would be a better label for the checkbox? That could be a start.
If the checkbox itself is confusing for the average user, I'd love to work on the issue but with concrete ideas from a UX designer as I have zero experience in the field.

Maybe try "scale images to box" and move the checkbox closer to the # of search results. @brenoferreira what do you think?

HI! I'm new to CC and would like to work on this. @little-wow May I?

Go ahead!

Hi

Removing in progress label since there has been no update for a month.

I'll take a stab at this for Hacktoberfest!

Can I take this up?
Thank you.
Dhruvi.

@dhruvkb Can I take this up

Hi, can I work on this?

We don't have that checkbox anymore, so I think this is no longer relevant.
Thanks for your interest in contributing. Feel free to look at other open issues and picking something that interests you


Potential UnboundLocalError in error-handling context manager

I'm working on unrelated things while this came up, and it's possibly unlikely to happen in real development, but just to track it in case someone cares,
https://github.com/tensorflow/tensorflow/blob/5e5dc97dd3523509ce5f536d7be5122d016fc6b5/tensorflow/python/framework/errors_impl.py#L471
that is an UnboundLocalError if it was line 463 that raised there (i.e. if TF_NewStatus failed entirely).
Without any insider knowledge, possibly that line belongs outside the try block.

Nice catch, thank you!  I'll fix, unless you feel like submitting a PR.

how to make tensorflow pull request https://gist.github.com/yaroslavvb/bdb0a92f2a516ebbe2d386c48f5e2c45


update the version of TCGC to 0.46.1

Description
Add your description here!
Checklist
To ensure a quick review and merge, please ensure:

[ ] The PR has a understandable title and description explaining the why and what.
[ ] The PR is opened in draft if not ready for review yet.

If opened in draft, please allocate sufficient time (24 hours) after moving out of draft for review

[ ] The branch is recent enough to not have merge conflicts upon creation.

Ready to Land?

[ ] Build is completely green

Submissions with test failures require tracking issue and approval of a CODEOWNER

[ ] At least one +1 review by a CODEOWNER
[ ] All -1 reviews are confirmed resolved by the reviewer

Override/Marking reviews stale must be discussed with CODEOWNERS first

Looks good to me. Just to confirm: for multipart cases, there is a new anonymous model in tspCodeModel.json (but no real code generated), is that expected?

I believe it is part of the fixes in 0.46.1 by Yuchao about multipart, but my PR does not implement it yet because I am not very familiar with it.


Less verbose transform of nullish coalescing and optional chaining

Search Terms
Nullish !=
Suggestion
I love nullish coalescing and optional chaining and I love Typescript! But TS could transpile nullish coalescing a bit less verbose since:
(expr !== null && expr !== void 0)

...is equivalent to:
(expr != null)

See http://adripofjavascript.com/blog/drips/equals-equals-null-in-javascript.html.
I've created a PR #42044 that would make this change. This is my first PR in this repo so I'm not sure what the test requirements are. Seems it got cought in something.
Use Cases
As a library vendor, I want to use nullish coalescing and optional chaining without sacrificing the final size of my library.
Examples
Source:
return {
  from: range.lower ?? -Infinity,
  to: range.upper ?? Infinity
}

Transpiled:
var _c, _d;
return {
  from: (_c = range.lower) != null ? _c : -Infinity,
  to: (_d = range.upper) != null ? _d : Infinity
}

Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

Duplicate of #34670.

I also note that there was an explanation of this browser-specific exception https://github.com/microsoft/TypeScript/issues/34670#issuecomment-581196685 including a conclusion to be using != null as the better alternative, given the use case for document.all and it's reason.

For those who still want this to happen: I wrote a little transformer that hooks into the compilation and changes the output to the compact version using loose equality comparison: https://www.npmjs.com/package/ts-transform-compact-nullish-compare

For those who still want this to happen: I wrote a little transformer that hooks into the compilation and changes the output to the compact version using loose equality comparison: https://www.npmjs.com/package/ts-transform-compact-nullish-compare


feat(transition): Using router push/replace instead of private history functions

I've found myself overriding the main Router to be able to control the .back method to prevent the user clicks on my app button a leaves the application. Check this example:
class Router extends VueRouter {
  constructor (...args) {
    super(...args)

    this.counter = 0
  }

  push (location, ...args) {
    super.push(location, ...args)

    this.counter++
  }

  go (n) {
    if (this.counter + n < 0) {
      super.replace({ name: 'home.feed' })
    } else {
      super.go(n)
    }

    this.counter += n
  }
}

Thanks to this approach, product links can be shared without worring the back button that linked pages contain will destroy the application once pressed. (The same behaviour as Twitter PWA)

What I mean is the beforeEach guard is not respecting the overriden methods (push, replace, etc...), because it uses the history driver directly when it has to redirect to a route, instead of using the router instance.
This could be taken as a Breaking Change for users like me that decided to wrap the router in their own classes, but I honestly think that this usage of the router is outside of the scope of the vue-router maintainers.
What do you all think?

hey, sorry for the delay. Do you have a boiled down reproduction of this?

Mmmh honestly  I don't remember the issue anymore xD. Anyways, I resolved this problem with a different approach. (Not related to VueRouter I think)
I'll close this one 👍


Should use_field_init_shorthand differentiate preserve and false

For the use_field_init_shorthand configuration option, currently the (default) "false" option is actually "preserve" while the "true" option is more akin to "force".
Would it be beneficial for this to be changed to match many of the other options that have a default of "preserve" and the option of overriding it in either direction (where possible) via "false" and "true"?
EDIT:
Also, the example for use_field_init_shorthand has a bug where the last SLOC is emitted from the second example. This actually makes it look like there's no difference between the "false" and "true" cases.

Thanks for reaching out. I think true and false are appropriate for the option since there isn't really an in between that I can think of. Did you have something in mind? Are you suggesting that Preserve and Force would be clearer options?
As demonstrated by #5488, we can't always use the shorthand even when the value is set to True.

Thanks for reaching out, but no, that's not a change we'd want to make especially not for an already stable option. In strictly boolean cases like this, we feel it's more natural for the option to follow the typical true/false paradigm. The Preserve variant is typically reserved for options that are non-binary in nature, and often connote more of a "use the original formatting to inform output formatting" as opposed to a "no, don't do that".

Also, the example for use_field_init_shorthand has a bug where the last SLOC is emitted from the second example. This actually makes it look like there's no difference between the "false" and "true" cases.

No, not really. There's varying interpretations/perspectives have about the config examples, but it's not intended to be interpreted as there being a relationship between the snippets from different values (there's no input/output relationship). The snippets are meant to be used as independent inputs such that running rustfmt over that snippet with that particular value would result in no code changes.
We've discussed trying to evolve the config documentation to try to include a separate input snippet that would be used and all the option value snippets would show the output of that snippet, but that's a large bucket of work no one has attempted to tackle yet

Ok, thanks for taking the time to respond.


fixes: Course Cards Layout Problem on /courses Route #478

Issues Identification
Closes: #478
Description
The course cards on the /courses route were previously stuck to the left and right edges of the page, with no margin on the X-axis. This created a cramped and unbalanced layout, affecting the overall user experience.
Changes Made:

Added appropriate margins to the left and right sides of the course cards container to ensure proper spacing from the page edges.
Reduced the gap between the course cards slightly to maintain a balanced and clean layout.

Steps to Verify:

Navigate to the /courses route.
Confirm that the first and last course cards no longer stick to the edges of the page.
Verify that there is now consistent margin on both the left and right sides, creating a more balanced layout.

Please check the boxes that apply

[x] Bugfix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (Documentation content changed)
[ ] Other (please describe):

Checklist
Please check the boxes that apply

[x] My code follows the style guidelines 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
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] My changes do not break the current system and pass all existing test cases
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Screenshots

@sagarbendale2004 while i was checking the preview
it's coming like this

i can't see both the images
please check and make the required changes.

@sagarbendale2004 please check the above message and update it.

@sagarbendale2004 please resolve the conflicts.

@sagarbendale2004 it is coming like this.

@sagarbendale2004 now it has gone entirely

There is a way to solve this,
Will it be okay If i close this PR, so that you can sync the repository and make updates, and then Create NEW Pull Request.

@vivekvardhan2810 check the latest preview of my changes it solved this issue very well so you can merge the pull request after reviewing the preview. if any update then please tell me.

Done. @sagarbendale2004 Good.


Reduced jQuery Usage (for Theme/Plugin loading, CustomCSS, Utils, and BdApi)

No point in this PR still being up, as a replacement should come along soon enough.


[JOSS] misc small items

xref: https://github.com/openjournals/joss-reviews/issues/5657

some misc typo corrections and some questions:

[ ] what is this file about? It looks like a local config file that could/should be removed: https://github.com/powerfulbean/mTRFpy/blob/0df8aa66c23e480829336889b977ff7bff9e1c54/mtrf.conf#L1-L2
[ ] The license file only contains one of the authors of this software, is this by choice? https://github.com/powerfulbean/mTRFpy/blob/0df8aa66c23e480829336889b977ff7bff9e1c54/LICENSE#L3
[ ] is this call to sys needed? What is it for? https://github.com/powerfulbean/mTRFpy/blob/0df8aa66c23e480829336889b977ff7bff9e1c54/mtrf/init.py#L5
[ ] could you please add a link to the documentation in the "about" section of the repository:

[ ] You can also "switch off" the packages and releases information there, which you do not seem to use:

[ ] I would like to see a PyPI badge in the README:
[ ] I think you would benefit from a .mailmap file, because running git shortlog --email --summary on your repo results in many different identities. For an example, see: https://github.com/mne-tools/mne-bids/blob/main/.mailmap

Not sure if you already have it and I can't see it, but it would be nice to switch on the Readthedocs PR preview feature for this repo: https://docs.readthedocs.io/en/stable/pull-requests.html


[BUG] Log4j.properties file in root jar file - azure-servicebus

Describe the bug
Log4j.properties file exists in the root jar file
To Reproduce
Include the jar file in an existing project
Expected behavior
No file should exist
Setup (please complete the following information):

Version of the Library used: azure-servicebus:3.0.0

Additional context
When adding a dependency to the servicebus jar our full project logging configuration is broken because this log4j.properties, we can not just remove this file or we should create a new uber jar with an exclude filter (Maven Shade Plugin)

@spylightadmin, thank you for reporting this issue. We will review our jar package and mitigate any packaging problems.

@spylightadmin, Thanks for reporting this bug. We acknowledge that we have a packaging problem. We are working to release a new version that will solve your problem.

Fixed in #5463.
Also, follow up issue - #5307


HTML Base tag causes problems

Since 0.17.1 the HTML base tag carries a port number in case the Tatin server does not use a standard port (80 or 443).
This is required because otherwise the links in the documentation would not work when one runs a Tatin server on her own machine with a non-standard port.
However, when Tatin is run behind, say, Apache then the port is not a standard one but must not be assigned to the HTML base tag anyway, because Apache will most probably use a standard port.

In general, I think any server needs a configuration parameter which tells it how it is being exposed to the outside world. It might be inside a container on an unsecured port, think it is http://localhost:8088, but to the outside work be exposed as a secure server on a standard port, e.g. https://tatin.dev.

In general, I think any server needs a configuration parameter which tells it how it is being exposed to the outside world. It might be inside a container on an unsecured port, think it is http://localhost:8088, but to the outside work be exposed as a secure server on a standard port, e.g. https://tatin.dev.

Fixed. New INI entry [CONFIG]BaseTagPort introduced that defaults to 0: no port added to the HTML base tag.

Fixed. New INI entry [CONFIG]BaseTagPort introduced that defaults to 0: no port added to the HTML base tag.


following codegened symbols

Even if the developer's Capi server is running, they are unable to follow codegened symbols. This hinders exploration of a given chain.

https://user-images.githubusercontent.com/4893548/220090512-953b9c9e-c7db-4400-94d6-d088ff48a6d3.mov

denoland/deno#18460

Closing as capi.dev is now the primary experience, and go-to-definition works there.