Develop Script for Reaching out to PHDs

Problem Statement
As the Experience Team, we need a script to follow when we reach out to PHDs to get referrals for COVID reporting entities.
Acceptance Criteria

Create script or talking points to follow
Should include information about our standard schema & its documentation
Should include a demo of the CSV Uploader

Hi @kjt9cc @rhood23699 - Do we have any previous communications that can be shared with me that I can adapt as I'm developing this script? Do we have a demo recorded already? Otherwise, I just got access to Okta now and could do a screen record on my end too. cc: @loripusey

@BerniXiongA6 Please see this slack thread for some materials https://usds.slack.com/archives/C024MGSJZ38/p1639679337484800
There is not a demo recorded, and a screen recording would be great.

@rachelhanster I can't access the link you shared to the slack thread. It looks like I need be logged into USDS?

Interesting, good to know. It's the same thread that I also directly tagged you, in slack.


array.blockwise has incorrect output shape in task graph

What happened: The new_axes parameter only modifies the output array shape at compute time.  Because of this, it's not possible to build task graphs that depend on array.blockwise reshaping the array.
What you expected to happen: The output array should be registered as the correct shape in the computation graph, so that the in-dask statements in the example below run the same as the numpy ones.
Minimal Complete Verifiable Example:
import dask.array as da
from sklearn.metrics.pairwise import cosine_similarity
from sklearn.feature_extraction.text import TfidfVectorizer

tfidf = TfidfVectorizer().fit_transform([
    "Hello world",
    "Hello bugs",
    "Goodbye world",
    "Goodbye bugs"
])
"""
try to perform the following as a blocked computation in dask:
mat = cosine_similarity(tfidf, tfidf)
mat.shape
###(4,4)
mat.ravel().shape
### (16,)
mat.ravel()
### array([1. , 0.5, 0.5, 0. , 0.5, 1. , 0. , 0.5, 0.5, 0. , 1. , 0.5, 0. , 0.5, 0.5, 1. ])
"""

"""perform the blockwise function in dask"""
inputs = da.from_array([tfidf[:2,:], tfidf[2:,:]], chunks=(1))
mat = da.blockwise(
    (lambda x,y: cosine_similarity(x[0], y[0])), 'ij',
    inputs, 'i',
    inputs, 'j',
    dtype='f8',
    new_axes={0:4,1:4}
)

print(mat.compute().shape)
### (4,4)

print(mat.compute().ravel().shape
### (16,)

mat.compute().ravel()
### array([1. , 0.5, 0.5, 0. , 0.5, 1. , 0. , 0.5, 0.5, 0. , 1. , 0.5, 0. , 0.5, 0.5, 1. ])

"""So far so good, now perform the ravel in dask"""

print(mat.shape)
### (2, 2)

print(mat.ravel().shape)
### (4,)

mat.ravel().compute()
### ValueError: cannot reshape array of size 8 into shape (2,)

Anything else we need to know?:
Environment:

Dask version: 2.18.0
Python version: 3.6.9
Operating System: MacOS Catalina 10.15.4
Install method (conda, pip, source): pip
sklearn version: 0.20.3

Are your input arrays correct? Do you really want a 1D Dask Array of 2D sparse matricies, or do you rather want a 2D Dask Array?
In [90]: inputs[0]
Out[90]: dask.array<getitem, shape=(), dtype=int64, chunksize=(), chunktype=numpy.ndarray>

In [91]: inputs[0].compute()
Out[91]:
<2x4 sparse matrix of type '<class 'numpy.float64'>'
        with 4 stored elements in Compressed Sparse Row format>

If you want a 2D Dask Array, you might want to investigate the sparse package. Something like
In [94]: x = sparse.COO.from_scipy_sparse(tfidf[:2, :])

In [95]: a = da.from_delayed(dask.delayed(x), shape=x.shape, meta=x)

In [96]: b = da.from_delayed(dask.delayed(x), shape=x.shape, meta=x)

In [97]: da.concatenate([a, b])
Out[97]: dask.array<concatenate, shape=(4, 4), dtype=float64, chunksize=(2, 4), chunktype=sparse.COO>

I don't have time to look further right now unfortunately. But hopefully that gets you started.
As an aside, dask-ml implements FeatureHasher & HashingVectorizer: https://ml.dask.org/modules/api.html#dask-ml-feature-extraction-text-feature-extraction

Thanks for the response, I'll see if I can use sparse to get past this on the user side and will update once I find something that works.
I'm sure it's possible to compute tfidf in dask by vectorizing the texts and normalizing from there, but it's beyond the scope of the issue here.  As an aside, our input dataset is of manageable size N, it's computations over the N^2 similarity matrix that absolutely need to be distributed.
I still believe it should be possible to define a blockwise operation that changes the number of elements in each chunk (as a result of the computation, not re-chunking).  I have no idea why the new_axes parameter doesn't seem to affect the output shape until the computation is run, and I think it's a bug that you can't chain operations like ravel onto the resulting matrix.

Alright, the approach suggested by TomAugspurger works as long as you convert the sparse blocks back to scipy representation before calling cosine_similarity!  I'll keep following to see what ultimately happens with this but I'm no longer blocked.  The moral here I guess is if you can at all get your arrays into a native dask format, do so.  I wasn't aware of the sparse.COO chunktype!
mat = da.blockwise(
    (lambda x,y: cosine_similarity(x[0].to_scipy_sparse(), y[0].to_scipy_sparse())), 'ij',
    inputs, 'ik',
    inputs, 'jk',
    dtype='f8',
)

I'm sure it's possible to compute tfidf in dask by vectorizing the texts and normalizing from there, but it's beyond the scope of the issue here.

Agreed. We can chat about that in https://github.com/dask/dask-ml/issues/5 if you have questions / code it share :)
Glad to hear you got something working. One other important lesson though, is that operations like .ravel() might not work if the actual shape of the chunks doesn't match Dask's expectation.
So things like the following:
In [2]: mat
Out[2]: dask.array<lambda, shape=(2, 2), dtype=float64, chunksize=(1, 1), chunktype=numpy.ndarray>

In [3]: mat.shape
Out[3]: (2, 2)

In [4]: mat.compute().shape
Out[4]: (4, 4)

are a sign that something has gone wrong. There might still be issues in blockwise, but we should addess issues with the block shapes first.


Missing container package version when no tag provided for container image

Describe the bug
If you build a Dockerfile using a base OS without a tag, Tern reports a blank SPDX PackageVersion for the container in SPDX output. Instead, it should be latest.
To Reproduce
Example Dockerfile to reproduce this issue: FROM opensuse/leap
Error in terminal
PackageVersion:

Expected behavior
PackageVersion field should be latest since that is what Docker assumes.

This is a bug in the sense that the package version is missing in SPDX reports, but it's not missing because of the missing tag in the base OS refernece, it's missing because of the docker-daemon prefix for local images when Tern gets run. A fix for https://github.com/tern-tools/tern/issues/1212 will also fix this issue.


Cranelift: The error message for the clif-util  run -v command appears to be incorrect.

I constructed a clif file.
multi_func8.zip
I used the following command to run it.
clif-util run -v multi_func8.clif

And I got the following error message:
cases/multi_func8.clif: Compilation error: Unsupported feature: should be implemented in ISLE: inst = `store.f16x8 notrap aligned little v2, v1`, type = `None`
1 file
Error: 1 failure

I think the error is triggered by the store.f16x8 instruction, but I can't find any store.f16x8 instruction in this clif file.

It is possible that the store.f16x8 is introduced by optimizations given that you enabled optimizations using set opt_level=speed.

It is possible that the store.f16x8 is introduced by optimizations given that you enabled optimizations using set opt_level=speed.

Is it necessary to adjust the optimization strategy to avoid similar issues from occurring?

I would recommend avoiding f16 entirely until Cranelift has proper support for it.


Removes CNAME file until we're ready.

Removes CNAME file until we're ready... didn't realize Github would start doing auto redirects to custom domain.

LGTM
For future PRs like these, consider git revert. I believe it creates a more obvious change history (though I'm not positive it would be meaningfully different in this case).


Add a "sandbox" style integration test to allow the chain to just be brought up as is, such that the user can interact with the chain however they want

This isn't really a necessary change, I just think it would be useful to have a test like this to make it easier for users to bring up the bridge for testing purposes. I propose a test similar to:
package integration_tests

import (
        "fmt"

        "github.com/peggyjv/gravity-bridge/module/v2/x/gravity/types"
)

func (s *IntegrationTestSuite) TestSandbox() {
        s.Run("Bring up chain and see what happens", func() {
                // Write whatever code you need here. Alternatively, wait for the chain to start and
                // use a validator's private key to perform operations

                s.T().Log("Chain running. JSON-RPC server is at <IP_ADDRESS>:8545. Press enter to exit")
                fmt.Scanln()

        })
}

And a similar Makefile change:
$ git diff Makefile
diff --git a/Makefile b/Makefile
index 60bd039a..0a03d955 100644
--- a/Makefile
+++ b/Makefile
@@ -76,3 +76,5 @@ e2e_validator_out: e2e_clean_slate
 e2e_transaction_stress: e2e_clean_slate
        integration_tests/integration_tests.test -test.failfast -test.v -test.run IntegrationTestSuite -testify.m TestTransactionStress || make -s fail

+e2e_sandbox: e2e_clean_slate
+       integration_tests/integration_tests.test -test.failfast -test.v -test.run IntegrationTestSuite -testify.m TestSandbox || make -s fail
\ No newline at end of file

Sounds good!
do you want to create a PR for this? or I could it also?

I'll create one 😄

Created PR https://github.com/crypto-org-chain/gravity-bridge/pull/191

fixed in https://github.com/crypto-org-chain/gravity-bridge/pull/191


AssertionError in colbert/indexing/collection_indexer.py

Hello! When I tried to index my own corpus, I met with an AssertionError, shown in the following picture. Do you have any idea about what can cause such a problem? I also attach part of my code for indexing.

with Run().context(RunConfig(
        nranks=1,
        experiment="BioRADR",
        gpus=1,
        amp=False,
        overwrite=True,
)):
    config = ColBERTConfig(
        nbits=2,
        bsize=8,
        query_maxlen=64,
        doc_maxlen=512,
    )
    indexer = Indexer(checkpoint="colbertv2.0", config=config)
    indexer.config.save(f'bioradr/configs/{group_id}_config.json', overwrite=True)
    indexer.index(name=f"BioRADR-group-{group_id}",
                  collection=f'bioradr/tsv/{group_id}_collection.tsv', overwrite=True)

I have tried some different corpus and I find that this problem will only appear for a few specific document sets. So I guess this issue may be concerned with some features of the data. But I hope to obtain your advice on how to fix this problem, thank you!

I have tried some different corpus and I find that this problem will only appear for a few specific document sets. So I guess this issue may be concerned with some features of the data. But I hope to obtain your advice on how to fix this problem, thank you!

I get the same AssertionError when indexing my corpus. Any suggestions on why this could happen  is most welcome. Thanks.

We pushed a fix to this iirc. Let me know if you still face it. Closing otherwise.

Acknowledged. Thanks.


Precompiling assets before test suite

Hi there,
I'm precompiling assets before I run my test suite with:
config.before(:suite) do
   system('bundle exec rake assets:precompile')
 end

When I run my test suite with rspec in the command line I can see that the assets are being compiled, and a /asset folder is created with all assets in there, bu the tests fail with a few The asset ... is not present in the asset pipeline.
When I run the test suite a second time, all tests pass. Do I need to somehow reload the environment, after precomping assets in the spec_helper.rb?

You might be better off aliasing this into rake test and running that way to ensure its completed before booting rails, but otherwise you probably need to run this before your require(_relative) "(../)config/environment" which is typically in the rails_helper and required before any hooks can run


Disposed PlayerState

Use case / Problem
When you dispose an AudioPlayer object the PlayerState is set to stopped. How do you decide now if you want to replay this AudioPlayer object or not? if your condition is
if (player.state != PlayerState.playing && player.state != PlayerState.completed) {
    player.resume();
}

player.onPlayerComplete.listen((event) {
    circle.player.dispose();
});

you are out of luck...
Workaround is to assign null to player and then check if the player is null....
player?.onPlayerComplete.listen((event) {
    player?.dispose();
    player = null;
});

if (player != null && player?.state != PlayerState.playing && player?.state != PlayerState.completed) {
    player?.dispose();
    player = null;
}

Proposal / Solution
Add PlayerSate.disposed
Example Code
if (player.state != PlayerState.disposed && player.state != PlayerState.playing && player.state != PlayerState.completed) {
    player.resume();
}

yeah i think it's a nice addition. Although i'm not sure, if we want this to be in the same row with the other player states, or just another variable in the AudioPlayer. But I think it is reasonable to add this to the AudioPlayer().state property.

Sounds like it could be in the same state field as the rest to me, because a disposed player should never be started again right?

@spydon yeah that's the final state :D


Tests are run in Chromium when either the Firefox or Webkit browsers are selected

Verified that Firefox and the Playwright 1.1 Webkit browsers are used when the Firefox and Webkit browsers are selected


boards: olimexino_stm32: Enable CAN support for this board

This PR enables CAN support on the Olimexino STM32 board.

Splited the commits.

Tested the samples/drivers/CAN with the device an the output is the same as the sample output.

@alexanderwachter Does CAN need special setup on olimexino_stm32 board to work? I tried samples/drivers/CAN/ and tests/drivers/can/api/ but none of them worked.
Serial output of tests/drivers/can/api/:
E: Failed to exit sleep mode                                         |
***** Booting Zephyr OS build zephyr-v2.0.0-1685-g4499b5844336 *****

    Assertion failed at ZEPHYR_BASE/tests/drivers/can/api/src/main.c:602: test_main: (can_dev is NULL)
Device not found
ASSERTION FAIL [!(thread->base.user_options & ((1UL << (0))))] @ ZEPHYR_BASE/arch/arm/core/cortex_m/thread_abort.c7
        essential thread aborted
E: r0/a1:  0x00000004  r1/a2:  0x00000025  r2/a3:  0xffffffbf
E: r3/a4:  0x0800829e r12/ip:  0x00000009 r14/lr:  0x080031d1
E:  xpsr:  0x61000000
E: Faulting instruction address (r15/pc): 0x0800614e
E: >>> ZEPHYR FATAL ERROR 4: Kernel panic
E: Current thread: 0x20000334 (main)
E: Halting system

Serial output of samples/drivers/CAN/:
***** Booting Zephyr OS build zephyr-v2.0.0-1685-g4499b5844336 ***** |
CAN: Device driver not found.

@alexanderwachter Does CAN need special setup on olimexino_stm32 board to work? I tried samples/drivers/CAN/ and tests/drivers/can/api/ but none of them worked.

Actually not. It seems that the Controller is not initialized. This has nothing to do with the board but with the SoC.
Could you turn on logging and send me the log?

west build -b olimexino_stm32 tests/drivers/can/api --pristine
../../stm32flash/stm32flash -w build/zephyr/zephyr.bin -v -g 0x8 /dev/ttyUSB0
has following result:
�I: Init of CAN_1 done
***** Booting Zephyr OS build zephyr-v2.0.0-1685-g8cb622e369eb *****
Running test suite can_driver
starting test - test_set_loopback
PASS - test_set_loopback
starting test - test_send_and_forget
PASS - test_send_and_forget
starting test - test_filter_attach
PASS - test_filter_attach
starting test - test_receive_timeout
PASS - test_receive_timeout
starting test - test_send_callback
PASS - test_send_callback
starting test - test_send_receive_std
PASS - test_send_receive_std
starting test - test_send_receive_ext
PASS - test_send_receive_ext
starting test - test_send_receive_std_masked
PASS - test_send_receive_std_masked
starting test - test_send_receive_ext_masked
PASS - test_send_receive_ext_masked
starting test - test_send_receive_buffer
PASS - test_send_receive_buffer
starting test - test_send_receive_wrong_id
PASS - test_send_receive_wrong_id
Test suite can_driver succeeded
PROJECT EXECUTION SUCCESSFUL

@walzert So I am doing something wrong. How do you setup your board? For example, do you connect CAN_RX to CAN_TX?  Do I need another device with CAN support?

@ydamigos there is the loopback_mode. With that the example is working without a other can device. I just build the bin and flashed it. With a second device I can test it on monday.

@walzert Thanks for the tip. Enabling loopback mode tests/drivers/can/api/ is working.

approved by TSC for merge in 2.1


Always make TSA handle perf syscalls

This changes makes it so whenever TSA is enabled for net, it also
grants perf syscalls too "for free". This is an incremental step towards
enabling perf syscalls on all titus containers.
This is only part1. Part2 will come in a differnet PR unifying the
seccomp profiles.

@aloktiagi do you have opinions on this? Your new traffic steering will also adjust how this goes

@MyUmmaGumma when enabling ioctl + network syscall interception, doesn't that create a deadlock or was it only sendmsg?

@MyUmmaGumma when enabling ioctl + network syscall interception, doesn't that create a deadlock or was it only sendmsg?

On the perf one we only intercept 2 particular ioctls (if that makes a difference)

@MyUmmaGumma / @aloktiagi can you confirm: is it ok for me to add the perf (includes ioctl intercept) filter for network interception too?

I still want this in place. My ultimate goal here is to enable perf on all tasks, without opting in.
To do this, it means TSA needs to use the perf filter all the time.

Closing this as we are archiving this repository.


Make radius generator base class abstract

Codecov Report

Merging #165 into master will increase coverage by 0.07%.
The diff coverage is 75%.

@@            Coverage Diff             @@
##           master     #165      +/-   ##
==========================================
+ Coverage   56.26%   56.34%   +0.07%
==========================================
  Files          13       13
  Lines        1269     1269
==========================================
+ Hits          714      715       +1
+ Misses        555      554       -1

Impacted Files
Coverage Δ

dpemu/radius_generators.py
90.9% <75%> (+4.54%)
:arrow_up:

Continue to review full report at Codecov.

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


When loading scenes, the engine creates entity GUIDs then immediately overwrites them

Description
When loading scenes, entities are generated. The pc.Entity constructor calls pc.guid.create but this is immediately overwritten by the GUID in the scene JSON. Creating the GUID is one of the more expensive things in the constructor (probably due to creating and executing the regex).

After doing some profiling, it seems >50% of entity creation time is spent in pc.guid.create(!).


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 177 ms

Resolved: ClamAV performance has improved in 3be2373.


Pan-cancer comparison

Hi Guys
I have some question on the section of Pan-Cancer Comparison. I downloaded the maf data of LUSC from TCGA and try to use "pancanComparison" to analyze it. Since it needs the results from MutSigCV, I used an online website to finish the MutSigCV analysis. The website is genepattern. And I finally got the file of "LUSC.sig_genes.txt".
Then I try to do the pan-cancer comparison.
lusc.mutsig<-"/Users/XXX/tcga/LUSC.sig_genes.txt" pancanComparison(mutsigResults = lusc.mutsig,qval=0.1,cohortName = lusc,inputSampleSize = 200,label=1)
There comes an error.
"Error in as.character.default(new("MAF", data = list(Hugo_Symbol = c("TARDBP",  :
no method for coercing this S4 class to a vector"
Would you please give me some suggestions? Thank you very much.

Hi,
Is it possible to share your LUSC.sig_genes.txt file?
Also, just a heads up. pancanComparison is being deprecated in the upcoming bioconductor release (scheduled for next week) and will no longer be available.

Sure. Please see the attach.
It is a shame to hear this news. Is there any alternative function for the pancanComparsion?
Thank you very much.
LUSC.sig_genes.txt

It seems at given q-value threshold (q<0.1) there are no genes specific to LUSC. But increasing it to 0.2 identifies two genes CUL3 and OR2G6.
pancanComparison(mutsigResults = "~/Downloads/LUSC.sig_genes.txt",qval=0.2,cohortName = "lusc",inputSampleSize = 200,label=1)

There is a new function called tcgaDriverBP which takes an MAF object and compares compares a set of genes to known TCGA drivers drivers.

I see. Thank you so much. There will be a new introduction of new version maftools package, right?
Looking forward to it. Have a good day. Stay safe and healthy.
Thank you .

BTW, one last question. I am not fully understand the variates in the LUSC.sig_genes.txt. What are the meaning of "p" and "q"? Thanks.

p means p value, q means q value, i.e. FDR (adjust p value).

Thank you so much. I've leant a lot.


Remove tools dev-shell make target

Remove the left-over make dev-shell target and other targets, which stopped working with https://github.com/istio/istio/pull/16729, and that is now available in istio/tools.
Fixes https://github.com/istio/istio/pull/16729
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[x] Developer Infrastructure

@rlenglet: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-framework-local-tests_istio
4c52d64e1fe3dfdf2fbec2033e68810c6f98ca66
link
/test integ-framework-local-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-framework-local-tests

@rlenglet: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTestsMinProfile_istio
4c52d64e1fe3dfdf2fbec2033e68810c6f98ca66
link
/test e2e-simpleTestsMinProfile

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-simpleTestsMinProfile


check and compare other noise types

https://github.com/stegu/perlin-noise

used newer algorithm with derivatives now


Deploy UI with TIKI Shopify app URL and add add App Bridge to TIKI app UI

As a developer,
I want to use App Bridge from Shopify
so that I can do authenticated requests to Shopify from the UI.
At the moment, the UI is using just Polaris, with no authentication with Shopify. It does not allow the usage of the react components that need access to Shopify data, like the Resource Picker nor the authentication of the requests.
We already have the App Bridge Provider configured to be used in DiscountProvider. The frontend needs to be deployed to the app URL as static files so it can be correctly embedded in Shopify admin and use app bridge.

To simplify this we could remove the app bridge and use the access token from our backend worker to get the required data to the discount UIs. The original design was this, and it is simpler than using their app bridge SDK.

App bridge was removed.


Not  An Issue : Information

Thanks !
Helpful for my Application Reference Demo Server ....because most  people & developer not very easy with OpeniD
After some time to debug ....

Require Nuget PM 4.3 --> previous versions not load properly ms aspnetcore.all and netcore.app
Require asp net core sdk V2 --> last VS 2017 did not install it v1 installed --> return un error
/oauth2/default/.well-known/openid-configuration return 401 (however public data ...?)  use instead /.well-known/openid-configuration working correct without auth

Regards,

Thanks for the feedback @gmorieux!
I'll make sure the readme notes that this requires ASP.NET Core 2.0 (and .NET Core 2.0 SDK).


error when using for an sbt plugin Supplied file ... is a not an existing directory

With the latest 3.6 release, when using for an sbt plugin build, the following error happens during sonatypeBundleRelease:
[info] Created successfully: ioshiftleft-1539
[error] java.io.IOException: Supplied file /home/mp/Projects/shiftleft/sbt-ci-release-early/target/sonatype-staging/1.1.3 is a not an existing directory!
[error]         at org.sonatype.spice.zapper.fs.AbstractDirectory.<init>(AbstractDirectory.java:32)
[error]         at org.sonatype.spice.zapper.fs.DirectoryIOSource.<init>(DirectoryIOSource.java:68)
[error]         at org.sonatype.spice.zapper.fs.DirectoryIOSource.<init>(DirectoryIOSource.java:59)
[error]         at org.sonatype.spice.zapper.fs.DirectoryIOSource.<init>(DirectoryIOSource.java:50)
[error]         at xerial.sbt.NexusRESTService.uploadBundle(NexusClient.scala:189)
[error]         at xerial.sbt.Sonatype$.$anonfun$sonatypeBundleRelease$1(Sonatype.scala:151)

Build on travis.ci: https://travis-ci.org/ShiftLeftSecurity/sbt-ci-release-early/jobs/583381874
Repo: https://github.com/ShiftLeftSecurity/sbt-ci-release-early/tree/6f9ed3ce07d86dd7aa4d3a4ba53983bdba43909f
Any idea where this comes from? Somehow the localBundlePath is wrong for sbt plugin builds.
Update: other than I first thought, this is actually broken for both sbt 1.2.8 and 1.3.0.

Argh, user error. I didn't change the publishTo := sonatypePublishToBundle.value as per the docs.
Let me know if you would like me to send you a PR for the readme, under e.g. 'common pitfallse', along with https://github.com/xerial/sbt-sonatype/issues/100#issuecomment-530152853

Thanks. I'm releasing sbt-sonatype 3.7 with the latest http-client version. So only a PR for publishTo setting is necessary.


(DRAFT) Added support for manually setting an asset XML node as static.

There are still some bugs with this I need to sort out, along with code cleanup. The reason why I'm putting this up in the first place is just to make clear that this is in the works so that work is not duplicated.

Related issue: #113


Do not replace $SHELL with --command option

Fixes #501
Continue to allow user to override default shell in yaml config, but --command option is not guaranteed to be a shell command, and should not override $SHELL.

Thanks for the thorough issue and for assembling the PR. This looks great!

My pleasure.  Cheers!


Feat: decode request in threadpool

Before submitting

[ ] Was this discussed/agreed via a Github issue? (no need for typos and docs improvements)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure to update the docs?
[ ] Did you write any new necessary tests?

⚠ How does this PR impact the user? ⚠
faster request decoding if it contains binary data (images, audios, etc).
GOOD:
faster decoding in batched loop
BAD:
Might be overhead in the case of simple requests

What does this PR do?
Fixes #166
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in GitHub issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

Is this what was intended, or have I got something wrong?

@deependujha nice! love the "faster" claim haha. do you have a benchmark or something showing that it is indeed faster and by how much?

@deependujha nice! love the "faster" claim haha. do you have a benchmark or something showing that it is indeed faster and by how much?

Hi @williamFalcon , I stated so on the basis of what was claimed in the original issue. Testing on 4 GPU machine does not reflect the same.
Throughput stays in the similar range (300-380), averaging at 330.
I'll try testing it with an audio model. If performance doesn't differ much, I'll close the PR.

tough luck, tested with the audio model but no significant difference in performance. I'll go ahead and close the PR.

@deependujha how does your decode_request logic look like? Does it do a CPU intensive operation or IO?


'operator-sdk print-deps' command

Description of the change: add an operator-sdk print-deps sub-command to print the most recent operator dependencies and versions. The sub-command will print pretty (below) by default, or the full Gopkg.toml when passed the --as-file flag.
Motivation for the change: updating operator versions when upgrading to new binary versions requires looking at SDK source code. This command prints all version information for packages pre-defined by the SDK that can be copy and pasted into an operators' Gopkg.toml, or written over directly with the --as-file flag.
Sample of output:
NAME						VERSION		BRANCH		REVISION
github.com/operator-framework/operator-sdk			master
k8s.io/code-generator								6702109cc68eb6fe6350b83e14407c8d7309fd1a
k8s.io/api									2d6f90ab1293a1fb871cf149423ebb72aa7423aa
k8s.io/apiextensions-apiserver							408db4a50408e2149acbd657bceb2480c13cb0a4
k8s.io/apimachinery								103fd098999dc9c0c88536f5c9ad2e5da39373ae
k8s.io/client-go								1f13a808da65775f22cbf47862c4e5898d8f4ca1
sigs.k8s.io/controller-runtime			v0.1.4

required = [
 "k8s.io/code-generator/cmd/defaulter-gen",
 "k8s.io/code-generator/cmd/deepcopy-gen",
 "k8s.io/code-generator/cmd/conversion-gen",
 "k8s.io/code-generator/cmd/client-gen",
 "k8s.io/code-generator/cmd/lister-gen",
 "k8s.io/code-generator/cmd/informer-gen",
 "k8s.io/code-generator/cmd/openapi-gen",
 "k8s.io/gengo/args"
]

Closes #638

@estroz Can you follow this up by updating the CHANGELOG for the new cmd.


Please follow semver specification

According to the semver specification, upgrading the z version should not cause any breaking changes. However, when I upgraded g2 from 4.1.20 to 4.1.26, many syntax errors occurred:

I suggest that in the future releases of g2, it is strictly adhered to the semver specification to avoid such issues.

A very good  suggestion, we'll pay attention to it.


Too much space after first para

Issue in /src/pages/implement/mobile/use-location-service.md

Dupe of Issue #43 ; once (if/when) this is fixed for one instance, it will be fixed for all.


Highlighting active/current page in hugo

Solution in judaicalink-portal is only for django not hugo.
Good site: https://discourse.gohugo.io/t/another-way-to-make-a-menu-item-active/17029

No, it can be done with javescript. Fetch the current url and set and active flag in the menu if it matches.


Refactor query transformer to operate on GraphQL Document type

Right now, it works on query definitions, which means we have to extract those from the document before running the transformer.

I don't think this applies anymore because we have to end up extracting the query definition anyway


Calendar in ListView/ScrollView

Hi!
I'm new to Flutter so this issue might just be a general Flutter mistake. But I want to place this nice calendar carousel in a ListView but cannot find a way to make it work. I can make it work by setting a specific height of the calendar but it would be nice to make the height change since it might be different depending on which month that is displayed. The error I'm getting is "BoxConstraints forces an infinite height." I have tried to wrap the CalendarCarousel in IntrinsicHeight, Column with Expanded inside etc. but nothing seems to work. Any hints to make it work would be much appreciated.
Example code:
Widget build(BuildContext context) {
    return MaterialApp(
      title: 'My calendar',
      home: Scaffold(
          body: ListView(
        children: <Widget>[Text("Hello"), CalendarCarousel(), Text("Hello again")],
      )),
    );
  }

Try to wrap the ListView with the Container that has specific width and height.


Docker image is taking too much time to build

Hi guys, I am trying to build the Docker image, but it is taking too long during the 'install vllm' step. Is this normal? Is there any solution to resolve it?
python3.11 -m pip install -e<EMAIL_ADDRESS>

Just pushed an update to address this, let me know if you’re still facing the issue

Just pushed an update to address this, let me know if you’re still facing the issue

https://github.com/runpod-workers/worker-vllm/commit/5aecb628702777356778dbb871d87d790279200d
It seems like wrong branch name

Do you mean old-11.8 and old-12.1 ?

Yes, that’s the one. My sincere apologies!

Still take too much time :(((

Try adding something like this before the build and adjust the values based on your system:
ENV MAX_JOBS=48 # The number of CPU cores you have
ENV NVCC_THREADS=1024 # Changes depending on GPU

Try out 0.2.0, you no longer need to compile vLLM, so the build should be very fast.

I will try! Thanks for your help!


docs: add texlive-latexextra dependency for pdflatex exports

Exporting an org file to pdf via LaTeX (org-export-dispatch or 'SPC m
e', then 'l p') requires texlive-latexextra (Arch package name) to be
installed on the system.
For reference, the error raised when texlive-latexextra was missing was
that the file 'wrapfig.sty' was not found. The specific error likely
depends on the contents of the exported file. Internet searches reveal
that pdflatex may also complain about 'utf8x.def' being missing; this
file is also provided by texlive-latexextra.

Makes sense to me. Thanks for your help!


$in query stopped working in 1.6.1

I have a test which does a query like this:
db.translations.find({ "lang" : "de" , "platform" : { "$in" : [ { "$ref" : "platforms" , "$id" : "demo"}]}})
The test worked fine in 1.5.10 but stopped working in 1.6.1 (no results from that query).
    DBCollection translations = db.getCollection("translations");
    BasicDBList platforms = new BasicDBList();
    platforms.add(new DBRef("platforms", "demo"));
    DBObject query = new BasicDBObject("lang", "de").append("platform", new BasicDBObject("$in", platforms));
    DBCursor cursor = translations.find(query);
    cursor.hasNext(); // <- true in 1.5.10, false in 1.6.1

Thanks for the report.
$in change in 1.6.1, so try 1.6.0 and it will works correctly.


SP-108 usability improvements, includes SP-142 SP-125 SP-129 SP-130 SP-74 SP-145 SP-144

Lots of small improvements throughout the app.
SP-142 - Improving the blank state. Added extra info to the about page. Made the guide public. Made it easier for people to navigate when not signed in.
SP-125 - Admins now get emails when new members sign up but not more than one every 6 hours.
SP-129 and SP-130 - Remove references to "-1" as the question order which ends a scenario. This should make it much simpler for users.
SP-74 - Added help text which can be revealed on all the forms, and added some basic info to the main quiz builder view.
SP-145 - Admins can now delete users from their organization.
SP-144 - Admins can no longer remove their own admin rights.

Yeah, I looked at the admin controller this afternoon and classed the refactor as "not a Friday afternoon job".
I'll check out the rest of the comments on Monday - in all likelihood hood merge it as is and spin off the comments as future work.


Can't be installed on Kali

github.com/optiv/Ivy/Loader
/home/kali/Desktop/Ivy/Struct/Struct.go:444: error: invalid export data for ‘Macro’: invalid line number
/home/kali/Desktop/Ivy/Struct/Struct.go:443: error: invalid export data for ‘Macro’: invalid line number
Can you please assist?

This seems similar to issue #5 can you take a look at some of the steps recommended there and see if they work for you?

I have downloaded a new version of Kali and it works perfect :)
Thanks a lot!!!


[UT] Capture runtime env in reports -  oneAPI, Driver versions, GPU Device Name, wheel's and triton test suite commit id's, python version

Requirements
Capture runtime env parameter in reports:

oneAPI version
Diver version
GPU device name
Commit id used from which Triton wheel was built
Commit id for tests
Triton version
Pytorch version
IPEX version
Python version

Implementation approach
This is an enhancement for scripts/test-triton.sh UT runner script.
Runtime information capture should be implemented in the scripts/pytest-utils.sh script.
For each runtime env parameter new txt file in the reports folder should be created.
Notes on how to get these information
oneAPI version
echo $CMPLR_ROOT >cmplr_version.txt
echo $MKLROOT >mkl_version.txt
Driver version
apt info libigc1 | grep -oP 'Version: \K[^~]+' >libigc1_version.txt
apt info level-zero apt info libigc1 | grep -oP 'Version: \K[^~]+' >level-zero_version.txt

GPU
 xpumcli discovery | grep "Device Name" | sed -n 's/.*Device Name: \(.*\)\s*|/\1/p' >gpu.txt

Methods to identity GPU (depending on which tool is available):
xpumcli discovery --json | jq -r '.device_list[0].device_name'
xpu-smi discovery --json | jq -r '.device_list[0].device_name'
clinfo --json | jq -r '.devices[].online[].CL_DEVICE_NAME'

Both methods should produce the same result, for exmaple:
Intel(R) Data Center GPU Max 1100

As the last resort (if all the tools above are not present):
lspci | grep Display

Note that the last method produces slightly different result:
ad:00.0 Display controller: Intel Corporation Ponte Vecchio XT (1 Tile) [Data Center GPU Max 1100] (rev 2f)

Hi, as for "Commit id for tests", what does "tests" in the runtime environment refer to?

@AshburnLee it's possible to use nightly wheel and up to date main branch and / or special branch with different sommit ids

Pavel has approved the PR, only need Vlad to approve & merge the PR to close this issue.


Home Page: Create a smooth scrolling home page

https://user-images.githubusercontent.com/34008861/170483429-1e30c1d4-0af5-4970-8225-8dd202fce0ed.mp4

In addition, Could you add maybe on the video how the users go into the login / see the global page / tips page, etc..
Does this PR include the options of the main navbar of the site?
I haven't seen it on the video

The Main nav bar where the global, login and everything else is still on top

Oh OK, because it doesn't show on the clip


chore(doc): removing useless fragment

Ref apache/camel-website#819

Release Note
NONE

FYI @davsclaus

Thanks for the speedy help


BC Transformer is not autoregressive during inference

Hello, this is my first issue so apologies if I missed something.
I have been training with the algo/bc.BC-Transformer and comparing the performance with BC RNN. However, while the transformer is trained in parallel, during inference time is autoregressive since the agent must interact with the RoboSuite environment. ie:
a0 = f(o0)
a0,a1 = f(o0,o1)
...
problem
As it stands, the bc.py algorithms have no mechanism to use multiple observations with the get_action method. While this is not a problem for BC_RNN (as it maintains a hidden state reset after the episode), the BC_transformer does not have this hidden state and needs all the observations in order to accurately predict the next action in the sequence. Otherwise the model is not performing sequence modeling.
Further, in models/obs_nets.MIMO_Transformer the transformer model that sees only one observation, but expects cfg.context_length observations is broadcast across all timesteps in models/obs_nets.MIMO_Transformer.input_embedding()
in my experiments:
tensor.shape(1,512) + tensor.shape(10,512) = tensor.shape(10,512)
solution
I have fixed this problem by retaining observations in a buffer and selecting the last n observations for the rollout. The observations are padded in the event that the agent has not yet experienced cfg.context_length observations. Rather than selecting the last observation in the sequence, the correct observation (relative to padding) is selected. This is sometimes the last observation. At the end of the rollout episode the buffer is cleared.
def get_action(self, obs_dict, goal_dict=None):
    """
    Get policy action outputs.
    Args:
        obs_dict (dict): current observation
        goal_dict (dict): (optional) goal
    Returns:
        action (torch.Tensor): action tensor
    """
    assert not self.nets.training

    obs_dict = TensorUtils.to_sequence(obs_dict)
    self.rollhist.append(obs_dict)

    zeroes = TensorUtils.single_apply(obs_dict, lambda x: torch.zeros(x.shape, device=x.device))
    n = self.context_length - len(self.rollhist)
    in_dict = (self.rollhist + [zeroes] * max(0,n))[-10:]

    timecat = lambda x, y: torch.cat((x, y), dim=1)
    from functools import reduce
    in_dict = reduce(lambda a,b: TensorUtils.both_apply(a,b, timecat),in_dict[1:],in_dict[0])

    return self.nets["policy"](in_dict, actions=None, goal_dict=goal_dict)[:, min(self.context_length,len(self.rollhist))-1, :]
    # return self.nets["policy"](obs_dict, actions=None, goal_dict=goal_dict)[:, -1, :]

def reset(self):
    """prepare transformer for autoregressive inference in rollout"""
    self.rollhist = []

If you like these changes, please let me know how I can incorporate them. I am planning to use RoboMimic in the future and would be interested to speak with one of the maintainers about contributing further improvements.

Thank you for your clear explanation of the problem you are encountering.
We actually do something very similar to your proposed solution in the FrameStackWrapper, which is what is used at test-time during BC-Transformer rollouts.
Tagging @snasiriany @MBronars for visibility and in case they would like to comment further on this.

@amandlek Thanks for your reply! I was unaware of FrameStackWrapper.
I was planning to write in the following options: (for my own experiments)

training on many data sources simultaneously
multi-gpu / multi-node training
hindsight relabeling of goals (and packed hindsight relabeling https://arxiv.org/pdf/2306.00937.pdf)

Does RoboMimic already support these things? I was not aware of them when reading the documentation.

Re: "training on many data sources simultaneously" - we plan to support this in the next version!
Re: "multi-gpu / multi-node training" - this is not supported at the moment
Re: "hindsight relabeling of goals (and packed hindsight relabeling)" - this is not supported at the moment either


Nesting on documentation

Describe the bug
There's a empty section on docs: nesting
To Reproduce
Steps to reproduce the behavior:

Go to the documentation site
look for nesting

Expected behavior
To find something about nesting.

Hi @robsonsobral Thanks for reporting this !
Nesting just means that mj-components can be nested in each other, but it's true that just the example  on the right doesn't explain much, so we'll remove this since there are already examples for each mj-component, that shows where they are supposed to be placed.
This part of the doc is handled by the website, not this repo, so i'll close this issue.


[BUG] error logging into registry: fork/exec /root/.hauler/cosign: operation not permitted

Environmental Info:

Linux rke2-server 5.15.0-<IP_ADDRESS>.el8uek.x86_64 #2 SMP Tue Aug 20 10:44:07 PDT 2024 x86_64 x86_64 x86_64 GNU/Linux
Hauler Version:

Describe the Bug:

hauler login fails, where cosign login/ctr login/crictl login succeed.
Steps to Reproduce:

Create VM with Oracle Linux 8, with a single network interface, connected to the internet
curl -sfL https://get.hauler.dev | bash
hauler login regsitry1.dso.mil -u <my username> -p <my password>

Expected Behavior:

Receive a login succeeded messaeg.
Actual Behavior:

Here is a screenshot demonstrating hauler failing to login (left terminal) while ctr is able to login and pull an image (right terminal).

Here is an example of using cosign, which was installed along with hauler, to login to the target repository.

Additional Context:

As of ~3 weeks ago I had another VM and was able to install hauler via the command listed above, login to the registry, and add images to my image store. That is to say-- this is new behavior.

Hey @ertimas, in your first screenshot, on the left terminal, it looks like you have a typo in the command and that's probably why it failed to accept it. You have -password instead of --password or -p

Ah-- I failed to post the correct screenshot

Sorry @zackbradys  please see this one

Ah that would do it! Unfortunately this is more a limitation than a bug and shouldn't be a new issue to v1.1.0...
Basically hauler is unable to open multiple connections to the cosign binary. If you have multiple concurrent processes running with hauler, then one of them fail. If you stop any other processes using hauler and try the command again, it should work for you. Feel free to check with something like ps aux | grep hauler

We're actively looking at how we leverage cosign, since we don't use much of it, and should be addressed relatively soon... our recommendation is try not to run multiple concurrent processes at the same time...
Feel free to add any thoughts to Discussion https://github.com/hauler-dev/hauler/discussions/358

So Hauler Fileserver and Hauler Registry can't be run at the same time @zackbradys?

Running "multiple concurrent processes" stemmed from the implementation in Hauler it seems since cosign ran fine on its own and I simply ran hauler login to generate the error.

Meant to close

Just an FYI-- turns out fapolicy was preventing cosign from running...  My bad team.  Added a rule and it worked immediately
echo "allow perm=executable uid=<user> : path=<user_home/.hauler/cosign" >> /etc/fapolicyd/rules.d/80-cosign-rule.rules


[Docker] Update onnxoptimizer to 0.2.7

This pr updates onnxoptimizer to 0.2.7 to support AArch64.
We need this pr because we want to enable ONNX tests on AArch64, but the current version of onnxoptimizer does not support AArch64.

@Mousius @leandron @ashutosh-arm


Feature/deployment keys

#patch#

Coverage remained the same at 88.889% when pulling bd87722f7a7812554d9e66b4ef3587360b2c595a on feature/deployment-keys into 5a06afae6734b6ba32c114a442709dfb9271abcd on master.


Tracking state of the application

We add this application test state to support this functionality in further tests and test that we can correctly use messages to know the actual state. Alternative is use eden pod ps

will not use for now


publish<EMAIL_ADDRESS>

Requested by: @marandaneto
Merge target: (default)
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Leave the #retract comment under this issue to retract the release (original issuer only).
Targets

[ ] pub-dev
[ ] github

Targets marked with a checkbox have already been executed.  Administrators can manually tick a checkbox to force craft to skip it.

#retract

Done manually. https://github.com/getsentry/sentry-dart-plugin/releases/tag/1.0.0-beta.2


Recommend Blazor for UI in .NET 9

Internal previews

📄 File
🔗 Preview link

aspnetcore/tutorials/choose-web-ui.md
Choose an ASP.NET Core web UI

I'm a bit confused because the Blazor section already states it for >=8.0.

I'm a bit confused because the Blazor section already states it for >=8.0.

I'd like to say it right away. It says that in the Blazor section and some folks will skip that section because they haven't heard that much about Blazor. Is it too much to say it twice? Would it be better to remove the 2nd recommendation?
Blazor is a full-stack web UI framework ~and is recommended for most web UI scenarios.~
Recommended for what? I think saying it at the top makes it more clear.

Yes, I recommend removing the second mention.
Do you want to version this? It kind'a breaks with the Version-by-INCLUDE approach, and I don't think it matters that much if it says for 8.0 that Blazor is favored. I think that's what DR told me ... that he was pushing it as the primary app framework for 8.0.

Do you want to version this? It kind'a breaks with the Version-by-INCLUDE approach, and I don't think it matters that much if it says for 8.0 that Blazor is favored. I think that's what DR told me ... that he was pushing it as the primary app framework for 8.0.


Allow further data processing prior to returning it through API

Is your feature request related to a problem? Please describe.
You have models: Post and Tag with many-to-many relationship.
Because of the relationship type, you had to also add a model PostTag with fields post_id, tag_id.
If you tried to use HC to return multiple posts with related tags, you'd have to return PostTag and then dig deeper to get the actual tags - which in effect would return json as such:
...
{
	[
		{
			"id": 1,
			"tags":
			[
				{
					"tag":
					{
						"name": "test tag"
					}
				},
				{
					"tag":
					{
						"name": "another testtag"
					}
				}
			]
		}
	]
}
...

Clearly, the solution is subpar as there's an extra object wrapping tags because it has to go through PostTag model.
Describe the solution you'd like
An ability to dig deeper before returning data would suffice, perhaps:
descriptor.Field(x => x.PostTags).GetValue(x => x.Select(y => y.Tag))
.. or, considering the fact it'd have to also load related fields
descriptor.Field(x => x.PostTags).UseSelection(x => x.Select(y => y.Tag))
Describe alternatives you've considered
I've considered implementing virtual properties and methods on the EF Core DTO's that'd dig deeper, but putting this.PostTags.Select(x => x.Include(y => y.Tag).Tag) into a property/method sounded like a terrible idea.

This can be done with a request middleware.
.AddGraphQLServer().UseRequest(...


Implemented the feaure #32

Hello @Nilhcem,
I have added the feature being requested in #32. Could you please review my changes and give me any feedback regarding them?
Kind regards,
Vest

Thanks,
I'll check this when I have some time (hopefully soon)

Perfect, thanks!

Thanks for the merge.
Was everything fine with the code?

I could not do it better,
I wanted to see how the i18n behaves when there's no translation key specified for a give language (the startsrv.err.invalidHost added key) (e.g. if it uses english by default) and finally no, the error message is empty, so I added the translations for the other languages to make sure it works well


Add keyboard functionality to dev-site search

Summary

While yes, https://github.com/cerner/terra-dev-site/issues/178 has already been closed, the site search still felt like it needed keyboard a11y... so I added it real quick. 😀

@emilyrohrbough for sure, meant to leave a comment on this PR stating that tests were coming last night 👍

@dev-cprice Do you have an update for this PR?

@emilyrohrbough not at the moment, been tied up with quarterly commits
hoping to get back to this soon-ish in my free time

@dev-cprice  are you okay with close the review until it's ready for review?

@emilyrohrbough For sure, that's fine.

Closing PR for now till @dev-cprice has time to pick up the tests for this change.


Issue with Orebfuscator

LWC Version (/lwc admin version):  1.9.4
Server version (/version): Paper version git-Paper-1589 (MC: 1.12.2) (Implementing API version 1.12.2-R0.1-SNAPSHOT)
Short five word summary of issue: Players can access locked chests when using orebfuscator.
Detailed description of problem:
If you are using Orebfuscator, and chests appear as stone, if you are quick enough and spam right click, you can access the chest and modify its contents. An easy way to do this is way up to a chest, and teleport away, i.e /spawn or /home, and come back with /back and spam right click. When I disable Orebfuscator the chests are protected fine.

@GershonR This is a bug with Orebfuscator. As you mentioned, the problem is fixed if you remove the plugin. Please report it to them instead.

LWC locks the actual block and knows it's location, how would Orebfuscator fix this if its only changing the block type of the chest and is not responsible for the locking of it?

@GershonR LWC can't be held accountable for other plugins behaving irresponsibly. Orebfuscator may be cancelling the event that LWC requires to check permissions of locked blocks. Or, since it is using ProtocolLib, it could be intercepting packets and providing fake information to the event.
It is not LWC's fault for this, nor is it even possible to correct on our side. Your solution is to have Orebfuscator fix their plugin, or use a different anti-xray plugin.

Look, please, this isn't an Orebfuscator issue.
See related in Citadel, a similar block protection plugin, and how we fixed it -- hint -- it was a malformed Clientside packet, exploitable (and is exploited by hacked clients) ... only thing orebfuscator is guilty of, is making it so that otherwise well-behaved clients can create this packet by accident, which hacked clients can do at will.
https://github.com/DevotedMC/Citadel/issues/54 -- and the PR that fixed it -- https://github.com/DevotedMC/Citadel/pull/55
Hope that helps.
Orebfuscator does not change the world, period.

To be specific, this line here:
https://github.com/megoesrawr/Modern-LWC/blob/master/src/main/java/com/griefcraft/listeners/LWCPlayerListener.java#L635
Looks a lot like what got us in trouble with Citadel.
The malformed packet our dogged investigator found, basically triggers a USE but with the wrong hand, which shouldn't be possible, but is in both hacked clients and in the weird-state that Orebfuscator inadvertently unlocks. Remove this over-optimization and the problem will go away.

There isn't any special configuration required, you just need both plugins and be able to teleport to and from a locked chest / protected block, making sure the chunk gets unloaded. It would be more interesting to test this with some sort of cheat client that replicates the orebfuscator behavior by changing the chest to another block.

@GershonR Sorry for the long delay. We were having issues with the build server, and additionally life has been busy for me. Everything should be resolved now, however. I confirmed the bug, as well as that it should now be fixed in the latest development build.


Adding ability to run kube-burner without the container

Signed-off-by: Kedar Vijay Kulkarni<EMAIL_ADDRESS>Description
Connected to issue #163
When we run the router perf workload we run it within a pod on OpenShift. Hence instead of trying to sping up another container within there, it seemed as a better option to download kube-burner binary and use it directly.
Testing
I have tested this script locally on my machine as our PSI Jenkins is not available to test. Nonetheless, It should work just fine.
cc @rsevilla87 @mffiedler @mohit-sheth @chaitanyaenr

Can one of the admins verify this patch?

/rerun all

Results for e2e-benchmarking CI Tests

Workload
Test
Result
Runtime

router-perf-v2
ingress-performance.sh
PASS
00:07:33

etcd-perf
run_etcd_tests_fromgit.sh
PASS
00:03:05

scale-perf
run_scale_fromgit.sh
PASS
00:07:36

network-perf
smoke_test.sh
PASS
00:12:05

kube-burner
run_clusterdensity_test_fromgit.sh
PASS
00:05:16

kube-burner
run_maxnamespaces_test_fromgit.sh
PASS
00:03:44

kube-burner
run_maxservices_test_fromgit.sh
PASS
00:02:52

kube-burner
run_nodedensity_test_fromgit.sh
PASS
00:03:21

kube-burner
run_nodedensity-heavy_test_fromgit.sh
PASS
00:04:17

storage-perf
run_storage_tests_fromgit.sh
PASS
00:03:34

upgrade-perf
run_upgrade_fromgit.sh
PASS
00:00:53


master jobs are broken due to missing Changelog

Describe the Bug
No response
Steps to Reproduce the Problem
new commits on master
Expected Result
CI should not do the changelog check on master builds
Actual Result
https://build.libelektra.org/blue/organizations/jenkins/PermaplanT/detail/master/405/pipeline
PermaplanT version
master
Operating System
Linux
Browser
any
Versions of other relevant software/extensions
No response
Additional info/logs
No response

Ah, that is unfortunate.
Maybe we want to disable some other stages too in master?
Isnt the master pipeline performing exactly the same pipeline that was performed on the PR branch before merging?

Maybe we want to disable some other stages too in master?

No, the changelog-check is the only exception. (In Elektra it is also like this.)

Isnt the master pipeline performing exactly the same pipeline that was performed on the PR branch before merging?

Not necessarily:

As merging sometimes can be done manually, there is a possibility that master contains something slightly different, e.g. rebased, different merging strategy etc.
When merging several PRs, the later ones are not up-to-date with master, so the overall result is also slightly different.

So it is needed to rerun everything on master.


Missing Struct VkPipelineCacheHeaderVersionOne

According to Spec
VkPipelineCacheHeaderVersionOne is present since version 1.0, but missing in PyVulkan.
But it's  enums are present.
like 'VK_PIPELINE_CACHE_HEADER_VERSION_ONE' which is the header version.

It is now


Support flutter_gen

Same as the title.

@yusriltakeuchi I believe I can update it.
Do you want me to create a pull-request for this?

@yusriltakeuchi I believe I can update it.
Do you want me to create a pull-request for this?

Sure, you can create pull request and i will review


Intellisense fixes, comments

Performed various IDE intellisense fixes and grouping deps with comments. Each change has been submitted with different commits to avoid complexity.

This is really excellent @fulls1z3 !
Other than the one comment, I'd love to merge this, thank you.

Happy to hear it has been helpful :)
Thank you for your excellent contribution!


Performance regression since v0.32-beta.16 for optimized debug builds

First off, thank you for wasmi and congrats on the recent 0.32 release! I recently swapped out wasmtime for wasmi 0.32-beta.16 in a certain project (not yet public) and was quite happy with it. The build got faster and smaller, the project got more portable, and wasmi's balance of startup latency + wasm execution speed worked much better for that project than wasmtime's (even with winch, which was already an improvement over cranelift). Many tests in that project compile a medium-sized wasm module and run it for short but nontrivial amount of time, and switching to wasmi v0.32.0-beta.16 made those tests run faster.
Unfortunately and surprisingly, when I tried to update to v0.32.0-beta.18 and later to v0.32.0, I found that it got 5x to 6x slower in the configuration I care about the most: building my project in the dev/test profile but enabling optimizations for wasmi and wasmi_core (via profile overrides). I've managed to minimize it down to a 1 KiB wasm module and a fairly trivial embedding: wasmi-slow-repro.tar.gz. In that tarball:

The compiled wasm module is included for completeness but ought to be reproducible
The two host-* crates do the same thing with different wasmi versions: instantiate the guest and run its sole export
compare.sh builds everything and runs it through hyperfine

I would expect the performance to be the same for both wasmi versions, but in the dev profile (as exercised by the script) it differs:
Benchmark 1: host-beta16/target/debug/host
  Time (mean ± σ):      67.8 ms ±   2.9 ms    [User: 66.9 ms, System: 0.9 ms]
  Range (min … max):    65.3 ms …  76.0 ms    40 runs

Benchmark 2: host-newer/target/debug/host
  Time (mean ± σ):     382.9 ms ±  19.7 ms    [User: 381.9 ms, System: 1.0 ms]
  Range (min … max):   369.1 ms … 434.2 ms    10 runs

Summary
  host-beta16/target/debug/host ran
    5.65 ± 0.38 times faster than host-newer/target/debug/host

This is on x86_64-linux-unknown-gnu, Rust 1.77.1, Intel i7-6700K CPU. Again note that wasmi and wasmi_core are compiled with optimizations in the debug profile. Removing the opt-level = 2 lines from the respective Cargo.toml files makes both programs much slower (both take ca. 1.7s on my machine). Building them with --release instead makes them perform the same, but that's of little use to me if I can't figure out how to get the same performance without building my entire project in release mode. I've tried various tweaks to the profile overrides, without success. I've also tried profiling, but all I can see is that 99% of the time is spent in wasmi's interpreter loop.

Hi @hanna-kruppe ,
The only significant change since v0.32.0-beta.16 was https://github.com/wasmi-labs/wasmi/pull/1041.
This change was important to improve execution performance of host function calls significantly amongst others.
The downside of this change though was that the executor's implementation is now generic over a T which was avoided. We avoided this before because the executor's inner loop is the hot-path when executing instructions via Wasmi and thus the main target for optimizations. It is very fragile to the correct optimization settings as you figured and it might be that with the recent change the fragility got bigger despite the overall performance wins.
It probably comes down to codegen-units=1 because with this setting the optimizer has awareness of the entirety of the inner loop and thus can apply optimizations it otherwise could not. (suspicion) You could try to see if thing improve significantly with configs like codegen-units=2 or 4 etc. The default with 16 is quite high.
Also you could try to disable debug assertions if you only care about fast compilation.

Thanks for the swift response. Applying codegen-units and other common settings to wasmi and wasmi_core doesn't seem to make any difference. This may be the root cause:

The downside of this change though was that the executor's implementation is now generic over a T

If substantial parts of the executor are not codegen's in wasmi but in my code, then that would explain why the overrides that I've tried don't help. Increasing the optimization level on the host crate fixes the regression for the minimized example. I'll check how this shakes out in the actual code base.

Thanks for the swift response. Applying codegen-units and other common settings to wasmi and wasmi_core doesn't seem to make any difference. This may be the root cause:

The downside of this change though was that the executor's implementation is now generic over a T

If substantial parts of the executor are not codegen's in wasmi but in my code, then that would explain why the overrides that I've tried don't help. Increasing the optimization level on the host crate fixes the regression for the minimized example. I'll check how this shakes out in the actual code base.

Yes, this indeed is the issue that you are facing due to the mentioned change.
One way to fix this is if you are able to carve out the Wasmi usage into its own crate. However, this crate needs to provide a non-generic API to the Wasmi implementation that is to be consumed by your main crate. This way your main crate would profit from incremental builds and your problem is likely gone.

I'll check how this shakes out in the actual code base.

Please keep me updated about it. :)

Yeah, setting opt-level = 2 for dev builds of the real crate that uses wasmi with opt-level = 2 largely fixes my performance problems. I'll still have to shuffle some code around to avoid repeated rebuilds of that crate, and fine-tune the trade-off between build time and edit-compile-test cycles, but neither will be a problem. So I consider this issue solved. Thanks again for the swift and helpful responses!
You might want to consider adding a note about this somewhere in the documentation (e.g., next to the "production builds" section of the review). If I hadn't already tried beta.16 and noticed the performance difference when upgrading, I might never have figured out that the performance I get from the profile overrides I tried was very far from optimal.

Yeah, setting opt-level = 2 for dev builds of the real crate that uses wasmi largely fixes my performance problems. I'll still have to shuffle some code around to avoid repeated rebuilds of that crate, and fine-tune the trade-off between build time and edit-compile-test cycles, but neither will be a problem. So I consider this issue solved. Thanks again for the swift and helpful responses!
You might want to consider adding a note about this somewhere in the documentation (e.g., next to the "production builds" section in README). If I hadn't already tried beta.16 and noticed the performance difference when upgrading, I might never have figured out that the performance I get from the profile overrides I tried was very far from optimal.

Thank you for the update. Yes, a note is probably required here.

@hanna-kruppe Thank you for the recommendation to mention this footgun somewhere. This is now documented in the new Wasmi usage guide: https://github.com/wasmi-labs/wasmi/blob/master/docs/usage.md


Creating an Template Field item

I am trying to create an item based on a template field:
/sitecore/templates/System/Templates/Template field

My code looks like this:
new DbItem("TestField", ID.NewID, new ID("{455A3E98-A627-4B40-8035-E683A0331AC7}"))

This causes the following exception:
System.InvalidOperationException : Unable to create the item based on the template '{455A3E98-A627-4B40-8035-E683A0331AC7}'. An item with the same id has already been added ('/sitecore/templates/template field').
   at Sitecore.FakeDb.Data.Engines.DataStorage.AssertDoesNotExists(DbItem item)
   at Sitecore.FakeDb.Data.Engines.DataStorage.AddFakeItem(DbItem item)
   at Sitecore.FakeDb.Pipelines.AddDbItem.CreateTemplate.Process(AddDbItemArgs args)
   at (Object , Object[] )
   at Sitecore.Pipelines.PipelineMethod.Invoke(Object[] parameters)
   at Sitecore.Pipelines.CorePipeline.Run(PipelineArgs args)
   at Sitecore.Pipelines.CorePipeline.Run(String pipelineName, PipelineArgs args, String pipelineDomain, Boolean failIfNotExists)
   at Sitecore.Pipelines.CorePipeline.Run(String pipelineName, PipelineArgs args, String pipelineDomain)
   at Sitecore.Pipelines.CorePipeline.Run(String pipelineName, PipelineArgs args)
   at Sitecore.FakeDb.Data.Engines.DataStorage.AddFakeItem(DbItem item)
   at Sitecore.FakeDb.Data.Engines.DataStorage.AddFakeItem(DbItem item)
   at Sitecore.FakeDb.Data.Engines.DataStorage.AddFakeItem(DbItem item)
   at Sitecore.FakeDb.Data.Engines.DataStorage.AddFakeItem(DbItem item)
   at Sitecore.FakeDb.Db.Add(DbItem item)

Am I do something wrong?

Hi Mike,
That is the expected behavior. You're trying to create an item but the 'templateId' parameter contains not a template id. It contains the id of another item (which is already added to the database). 'Template field' is not a 'template'.
—
Sent from Mailbox
On Wed, Aug 12, 2015 at 7:02 PM, Mike Edwards<EMAIL_ADDRESS>wrote:

I am trying to create an item based on a template field:
/sitecore/templates/System/Templates/Template field
My code looks like this:
new DbItem("TestField", ID.NewID, new ID("{455A3E98-A627-4B40-8035-E683A0331AC7}"))
This causes the following exception:
System.InvalidOperationException : Unable to create the item based on the template '{455A3E98-A627-4B40-8035-E683A0331AC7}'. An item with the same id has already been added ('/sitecore/templates/template field').
at Sitecore.FakeDb.Data.Engines.DataStorage.AssertDoesNotExists(DbItem item)
at Sitecore.FakeDb.Data.Engines.DataStorage.AddFakeItem(DbItem item)
at Sitecore.FakeDb.Pipelines.AddDbItem.CreateTemplate.Process(AddDbItemArgs args)
at (Object , Object[] )
at Sitecore.Pipelines.PipelineMethod.Invoke(Object[] parameters)
at Sitecore.Pipelines.CorePipeline.Run(PipelineArgs args)
at Sitecore.Pipelines.CorePipeline.Run(String pipelineName, PipelineArgs args, String pipelineDomain, Boolean failIfNotExists)
at Sitecore.Pipelines.CorePipeline.Run(String pipelineName, PipelineArgs args, String pipelineDomain)
at Sitecore.Pipelines.CorePipeline.Run(String pipelineName, PipelineArgs args)
at Sitecore.FakeDb.Data.Engines.DataStorage.AddFakeItem(DbItem item)
at Sitecore.FakeDb.Data.Engines.DataStorage.AddFakeItem(DbItem item)
at Sitecore.FakeDb.Data.Engines.DataStorage.AddFakeItem(DbItem item)
at Sitecore.FakeDb.Data.Engines.DataStorage.AddFakeItem(DbItem item)
at Sitecore.FakeDb.Db.Add(DbItem item)
Am I do something wrong?
Reply to this email directly or view it on GitHub:
https://github.com/sergeyshushlyapin/Sitecore.FakeDb/issues/80

Could you please add a bit more details to the scenario you want to achieve? Thanks.

I want to create an item based on the standard Template Field template in Sitecore because I have an On Save event that manipulates the Template Field to set a title and to make sure the field matches a naming convention.

I have been playing around a bit more and I notice that FakeDb doesn't create the template fields as items. Take for example this code:
var tId1 = ID.NewID;
var fId1 = ID.NewID;
        using (var db = new Db
        {
                    new DbTemplate("TestTemplate1", tId1)
                    {
                        Fields = { new DbField("TestField",fId1)}
                    }
        })
        {

            Template temp = Sitecore.Data.Managers.TemplateManager.GetTemplate(tId1, db.Database);
            Assert.IsTrue(temp.ContainsField(fId1));  //this returns true

            var fieldItem = db.GetItem(fId1);
            Assert.IsNotNull(fieldItem);  //this fails

        }

So the template gets the field but the actual field isn't create in the DB.
I need to be able to actually create the templates and fields in the DB and treat them as items.

It is possible to create a template field item manually now, but the template fields are still not stored as items. I can rewrite your test in a slightly different way building the template using DbItem's:
using (var db = new Db
        {
                    new DbTemplate("TestTemplate1", tId1)
                    {
                        new DbItem("TestField",fId1, TemplateIDs.TemplateField)
                    }
        })
      {
        var fieldItem = db.GetItem(fId1);
        Assert.NotNull(fieldItem);  // does not fail now

        Template temp = Sitecore.Data.Managers.TemplateManager.GetTemplate(tId1, db.Database);
        Assert.True(temp.ContainsField(fId1));  // NOW FAILS :)
      }

I think both scenarios should be supported. I'll keep working on this, thanks.

Fixed and released as v0.29.1

@mikeedwards83 please let me know if your issue has been solved. Thanks.


Ensure Address Assignments Align between thread_wifi_*ap_service.json

Currently, the differences between the src/test-apps/happy/topologies/standalone/thread_wifi_on_tap_ap_service.json and src/test-apps/happy/topologies/standalone/thread_wifi_ap_service.json go beyond simply tap: true and tap: false, respectively. The former has different node addresses than the later. Since the Inet layer test has hard-coded addresses (itself a separate bug to be addressed), the Inet layer tests against LwIP can never work with the former topology (other issues notwithstanding).

Codecov Report

Merging #145 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #145      +/-   ##
==========================================
+ Coverage   53.62%   53.63%   +<.01%
==========================================
  Files         326      326
  Lines       55424    55424
==========================================
+ Hits        29723    29726       +3
+ Misses      25701    25698       -3

Impacted Files
Coverage Δ

src/test-apps/TestCASE.cpp
96.1% <0%> (+0.22%)
:arrow_up:

src/lib/profiles/security/WeaveCert.cpp
84.41% <0%> (+0.64%)
:arrow_up:

Continue to review full report at Codecov.

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


fix(libsinsp): fix -Wreorder warning

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build
/area libsinsp

Does this PR require a change in the driver versions?
No

What this PR does / why we need it:
As per title, fixes m_inspector / m_last_flush_time_ns ordering definition
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hmm it seems to me that sinsp_container_manager defines m_inspector before m_last_flush_time_ns, so your patch would introduce a -Wreorder warning. What am I missing?

Seems slightly above, or should we move it to private?
https://github.com/falcosecurity/libs/blob/9d8c0a4babbdd01752d5d86ed6dd23194b339fc0/userspace/libsinsp/container.h#L226

LGTM label has been added.  Git tree hash: b41b12d9df71b3861519b548454c51be0138215c

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: gnosek, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [LucaGuerra,gnosek]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, gnosek, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,LucaGuerra,gnosek]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/milestone 0.14.0


tsf importance curve normalization

Reference Issues/PRs
 Fixes #669
What does this implement/fix? Explain your changes.
 An option has been provided for the user if they want to normalize the importance curve by considering the fact that different time indices occur in the different numbers of intervals. Some cases might not require them to do so, as rightly pointed out by @TonyBagnall and @MatthewMiddlehurst and hence it is user-dependent.
I do this by assigning two variables: normalise_option ('False' initially) and normalise_type (I will be building on it later so I have just initialised it for now).
Based on the preference stored in normalise_option, user can either fis_norm or fis in return. fis_norm will be obtained by dividing the fis by fis_count that is obtained by empirical value addition as @aabanda suggests.
Does your contribution introduce a new dependency? If yes, which one?
 Nope
What should a reviewer concentrate their feedback on?

Just the edits in the code.
Any other comments?
 For future: I think we can add more kinds of normalizations. Apart from just based on count, we can have normalization based on maximum occurrence of intervals or mean occurrence in intervals.

hi @Aexousia, we are having a tidy of PRs and sktime has changed a fair bit since this was updated. Are you still working on this, or shall I close it? Fine to open a new PR later if you want

hi, I'll close this, feel free to reopen it at a later date if you want to


Find definition not working anymore in Node after 0.11.3

I have the node plugin included and this worked on 0.11.2

Mac OSX


Assignment

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Adding employee shifts to the ERD and updating the customer address management to consider both types (Type 1 and Type 2).
What did you learn from the changes you have made?
I learned the importance of distinguishing between change-overwriting (Type 1) and history-retaining (Type 2) methods in database design, and how adding shifts requires additional entity relationships to manage employee schedules effectively.
##Was there another approach you were thinking about making?
Yes, I considered merging the shift schedule with the employee table directly, but separating it allowed for better flexibility and extensibility in tracking multiple shifts.
##Were there any challenges?
The main challenge was designing the customer address table in a way that accommodates both overwriting and retaining changes. I overcame it by creating separate tables for historical and current addresses.
##How were these changes tested?
The changes were tested by running SQL queries to ensure referential integrity across the new shift and address tables, and by verifying expected behavior when updating address data.
##A reference to a related issue in your repository (if applicable)
The issue relates to expanding the existing ERD to improve scalability and data accuracy (the sample in Slack).
Checklist

[ ] I can confirm that my changes are working as intended

hi Amanda:
I corrected and submitted assignment_1  last night.
Best,
Marjan
On Sun, Sep 29, 2024 at 6:12 PM amanda-ng518 @.***>
wrote:

@.**** approved this pull request.
A1: 52/52
—
Reply to this email directly, view it on GitHub
https://github.com/marjanrajabi437/sql/pull/8#pullrequestreview-2336027347,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BKSZRPZ77PFV7QQOIBP5FR3ZZB3NBAVCNFSM6AAAAABPBHWBTGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDGMZWGAZDOMZUG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Marjan Rajabi
PhD in Statistics
Statistical Researcher & Data Scientist
Phone:<PHONE_NUMBER>


Holding the values in form when the post request is failed with error

Description
At first, I found that some vaules in the form were missing or changed to default values automaticly, when creating an org or a repo with invalid name.
e.g.

Visibility in this page is required so users will be aware of the change.
But if there are some no required params with this bug, user may post wrong data with no awareness of these changes.
Then I found func AssignForm in modules/web/middleware/binding.go which is used to assign form values back to the template data.
It seems we need to define same variable names between form data and template data?
e.g.
Visibility in this page is defined as DefaultOrgVisibilityMode in template data, but visibility in form data.
Gitea Version
87261f3fb95da92d74d72d057fc0f1e9819f16a7
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
build
Database
None

I could agree with you (at least partially)
In history, people come and go, no strict rules nor guidelines, various code gets merged, many framework designs and mechanisms get broken ....
So, a strong team with strict and reliable review workflow could help, that's a trade-off.

The document is renewing under https://docs.gitea.com/.
Maybe it is a good chance to supplement develop guidelines.
I will try to make a preview PR which will fix this in a better way.

I noticed that #22834 and #22846 are both trying to fix it too, but in different ways. #22834  is a quick patch.
So shall we merge #22834 first and wait for #22846 to finish?

I noticed that #22834 and #22846 are both trying to fix it too, but in different ways. #22834 is a quick patch.
So shall we merge #22834 first and wait for #22846 to finish?

@wolfogre
No problem.


Create C#hello.md

What the program do ?

In what programming language it is written?

This pull request do not contains files in specific folders. Please fix it and reopen


Inserting Earthquake Data into InfluxDB (Learn Grafana 7.x Chapter 6)

When I am trying to insert Earthquake data into InfluxDB 1.7.2. , I get an error that "ERROR:root:'latin-1' codec can't encode character '\u0101' in position 3702: Body ('ā') is not valid Latin-1. Use body.encode('utf-8') if you want to send it encoded in UTF-8." Most of the locations in the JSON i.e Pahala has special character 'a' with macron or characters not supported by Latin-1 encoding.
How can I get around those special characters when inserting into InfluxDB. I am planning to chart EarthQuake database via Grafana 7.x.
How can I modify earthquake.py script to post data as UTF-8 not as Latin-1 as Latin-1 cannot encode special characters in locations like Pahala which contains special character 'a' with macron.

Changing line 79 in earthquake.py to this:
    data = input_file.read().encode('utf-8')

should force the file to be sent to InfluxDB with the proper encoding.
I’ve updated the Chapter 06 repo script accordingly


src.plot different color for each source space

when doing src.plot for a volumic source space it would be nice to see in different colors (not just yellow) the source locations depending to which structure they belong.

Definitely.

In theory for the volume ones we might be able to get the colors from the Freesurfer LUT / aseg somewhere

+1 !

I'll take this one (sprint 2021) :)

closed in #9114


H6175 segment brightness is limited to the global brighness

turning segment brightness is relatively bound to global brightness.
examples:
global brightness: 60%
segment brightness: 100%
resulted segment brightness: 60%
expected segment brightness: 100%
global brightness: 60%
segment brightness: 50%
resulted segment brightness: 30%
expected segment brightness: 50%

I've added a FAQ that answers this: https://github.com/wez/govee2mqtt/blob/main/docs/FAQ.md


Correction for raw affiliation CIRAD, UPR AIDA, Montpellier F-34398, France

Correction needed for raw affiliation CIRAD, UPR AIDA, Montpellier F-34398, France
raw_affiliation_name: CIRAD, UPR AIDA, Montpellier F-34398, France
new_rors: 05kpkpg04;01hv86c27
previous_rors: 05kpkpg04
works_examples: W4388361421
contact: 934d6be520f5b45909f376290d6c914e:89fbbb06fd654cf7a1a78f63e17e @ cirad.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Building SuperPNG with Visual Studio 2015 Community Edition

Hi,
I'd like to build SuperPNG with VS 2015 CE. Can you please provide another project?
After auto converting the VC++ projects I tried to import all of the projects in the repo and did not succeed due to unreadable resource files, dependencies etc.
Any help would be appreciated.
thx in advance

Are you starting with the project in SuperPNG/vc/vc12? That was made with Visual Studio 2013 CE.

OK, tried opening and building the vc12 project, I have set up a new Win 10 64 VM with just git and VS 2013 installed.
I cloned the repo, copied the photoshop sdk into the ext folder and got the following errors cloning external modules:

updating external modules failed at pngquant module (so I cloned it manually, with the msvc branch and without it, as the pngquant readme says, but still getting compile errors)
SuperPNG_x64.rc cannot be read (but it doesn't produce compile errors so this is probably not important)
libpngquant cannot be built because of the MS compiler i think. I tried the msvc branch, but no success either.
sources from src/photoshop do not appear in the solution

Am I doing something wrong here and if so, how is it done right?

Yep, ext/pngquant-msvc was failing because Kornel killed his old msvc branch (which I was using) and started a new one, making the old commit inaccessible. I tried his latest stuff, but was not able to get it to build in vc12 (Visual Studio Express 2013). So what I did is resurrect that old branch under my own fork and added it as another submodule which the vc12 projects now point to. So re-clone everything and hopefully you'll have better luck.

Thanx a lot! I'll try tomorrow and post the results here.

Good morning,
I just tried to build with a new repo clone and it works like a charm :)
Thank you, Brendan, all issues are solved - even the files from /src/photoshop I thought were not listed. But they are linked in the SuperPNG project under "Project properties ->Linker->Additional Library Directories" and appear directly in the SuperPNG project's root.
Have  a nice day!

Glad to hear it. Thanks for posting the issue.

just wanted to add that it's building in Visual Studio 2015 CE as well.


theano env problem

the variable MERLIN_THEANO_FLAGS in  file setup_env.sh  should be MERLIN_THEANO_FLAGS="mode=FAST_RUN,device=cuda0,cuda.root=/usr/local/cuda-9.1,floatX=float32,on_unused_input=ignore" if you are using cuda-9.1. The device=cuda0  must be there or theano bug will occur.

I am using cuda-9.0 and there is no theano bug. But now I want to use tensorflow instead, is that safe? @shartoo

You can use tensorflow but theano is essetial to merlin,so you not escape installing theano, cuda-9.0 is safe for both tensorflow and theano.


Improve confusing warnings

Pull Request Description
What issue does this change request address?
https://github.com/gmlc-dispatches/dispatches/issues/173
#2074
What are the significant changes in functionality due to this change request?
Makes some warnings clearer.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[ ] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

Job Test Ubuntu 20-2 Optional on ccd9441 : invalidated by @joshua-cogliati-inl
FAILED: Diff tests/framework/ROM/TimeSeries/ARMA/InterpolatedMaxCycles

Job Mingw Test on ccd9441 : invalidated by @joshua-cogliati-inl
failed in fetch

Job Mingw Test on ccd9441 : invalidated by @joshua-cogliati-inl
FAILED:  Failed tests/framework/Databases/HDF5/load_and_push_reusing_same_hdf5  Failed tests/framework/ensembleModelTests/testEnsembleModelNonLinearParallel  Failed tests/framework/ensembleModelTests/testEnsembleModelLinearParallel

PR looks good, and checklist is satisfied.


enhancement: Add PartialEq derive to Annotation.

I think it would be useful to have some structs derive PartialEq within the jvm API.
One such example that would be handy for me is the  Annotation struct, as I need to filter out methods based on whether the method has a specific runtime_visible_annotations entry:
if method.runtime_visible_annotations.contains(
    &Annotation {
        annotation_type: FieldType::Object(
            ClassRef {
                binary_name: "some/package/Name".to_string()
            }
        ),
        element_value_pairs: vec![],
    }
) {
    // Filter...
}

I have added the derive in my own fork, but I was wondering if this could be usefully applied to any other structs - and commited in bulk.

I agree. I think Annotation is not the only structure where PartialEq is missing. It would be nice if we could figure out a list of structs that we should add PartialEq, and possibly Eq and Hash.

Annotation - and by proxy ElementValue.
TypeAnnotation - and by proxy TargetInfo, TypePathElement & ElementValue.

Both of these would make sense, and can be implemented with relative ease.


Stop-Computer, Restart-Computer on macOS: support graceful shutdown by default, implement -Force support

Summary of the new feature / enhancement
Note:

This would not be a breaking change, because Stop-Computer and Restart-Computer are currently broken altogether on macOS - see #19738

I do not know enough about Linux distros to tell if a distinction analogous to the one below is even possible or necessary there.

A fix for #19738 is being worked on in #19780, and it will delegate to  /sbin/shutdown -h now (shutdown) and /sbin/shutdown -r now (reboot) on macOS.
However, these commands amount to a forced shutdown: they do  not afford GUI applications enough time to shut down gracefully, such as browsers and VM software, inducing potential data loss.
Therefore, I propose the following:
Proposed technical implementation details (optional)
By default, use the following commands on macOS - they do shut down gracefully, but - as on Windows - do not guarantee a shutdown, if an app refuses to quit:

Shutdown:

osascript -e 'tell application "System Events" to restart'

Reboot:

osascript -e 'tell application "System Events" to shut down'

Use /sbin/shutdown ONLY if -Force is specified.

Shutdown:

/sbin/shutdown -h now

Reboot:

/sbin/shutdown -r now

Are these two comments backwards?
Shutdown:
osascript -e 'tell application "System Events" to restart'
Reboot:
osascript -e 'tell application "System Events" to shut down'

@krzydoug Oops! Thanks for catching that. I've fixed the initial post.


rtkspectralonestep.cxx with nMaterials = 2

rtkspectralonestep uses rtk::MechlemOneStepSpectralReconstructionFilter with a fixed nMaterials set to 3. I have modified the code to use this filter for nMaterials  = 2. Code is here :
https://github.com/SimonRit/RTK/compare/master...paRodesch:one_step_two_materials
But the change of nMaterials from 2 to 3 is hard coded in rtkspectralonestep.cxx. I want to be able to declare rtk::MechlemOneStepSpectralReconstructionFilter with either nMaterials = 2 or 3 according to the first dimension of args_info.attenuations_arg given as input of the command.

Adressed by d48e996


feat(http2): add http2 support

Solves #209.

Coverage remained the same at 91.085% when pulling 7c47415e7754449be53202c4e46b704404c3cc61 on feature/http2 into 0e1c9d1d52f3c5c8ad71de9e295ecbb81670b833 on master.


 We're converting our code style to use recompose and was hoping we could contribute this to the project.

Thank you!

Recompose already have similar HOC - lifecycle
As I know componentWillMount will be deprecated soon https://github.com/facebook/react/issues/7671

@istarkov Thanks for the reply. We'll just use lifecycle then!


Alphabetical classpath order breaks compatibilty for MergeStrategy

Hello.
I have updated the plugin to 0.14.10 after using old 0.14.6 version for some time in one of my projects and I was really surprised to find differences in assembled jar files
It turned out that #356 #357 fixes some builds, but breaks others.
I have spent quite some time on understanding the MergeStrategy mechanism and the classpath order which I believe is inherited from Maven. My findings are summed up HERE, maybe your comment on it could clarify my misunderstandings.
Anyways, currently, I am really confused with the merging mechanism which fails on my project structured like this:
project-A
 /src/main/resources/META-INF/persistence.xml

project-B
 /src/main/resources/META-INF/persistence.xml

projectB.dependsOn(projectA).settings{
   ...
  case x if x.contains("persistence.xml") => MergeStrategy.first
   ...
}

Before 0.14.10 assembling project-B resulted with persistence.xml being sourced from project-B. With 0.14.10, since project-A is first, alphabetically, it copies one from there.
I think previous order was based on some kind of dependency-graph-tree, which resulted in order being equal to some "depth". However now... it will be nearly impossible to pick the right file.
Imagine if project-C comes to play. How should I pick the middle file?
Currently, I would vote for reverting this change.
But what do you guys think?
Thanks a lot!

Apache Ivy used to return the modules in topological order, but I don't think Coursier does (yet)?
See https://github.com/coursier/coursier/issues/1466 and https://github.com/sbt/sbt/issues/5282.
I think depending on any sort of classpath ordering is unreliable, and my opinion is that you should make your own MergeStrategy for this, which might sound difficult, but I don't think it's bad. See the implementation of MergeStrategy.first for example:
  val first: MergeStrategy = new MergeStrategy {
    val name = "first"
    def apply(tempDir: File, path: String, files: Seq[File]): Either[String, Seq[(File, String)]] =
      Right(Seq(files.head -> path))
  }

The main part is a single line.

I understand that relying on dependency order may not sound like a silver bullet for merging files during the assembly process. However, I believe this may be a bigger issue for some (like me) and frankly, I don't think writing my own MergeStrategy should be necessary. Also, the old mechanism was here for years, especially since it was compatible with Maven so if one new how it works you could have find your way using first and last pretty easy.
I think that changing that behaviour on your side should be followed up by new handlers (strategies). Maybe one that could allow the user to select the file by project name? Or some path matcher? I believe this would be beneficial for all if you'd reopen the issue.
Thanks!


Norway and Sweden data...

Slightly off topic unless you have any interest in extending your project...
My brother lives in Norway so I was curious, found this has nice map for anyone curious.
https://github.com/jalgroy/covid19-norway-map
Interestingly there is a nice map on wikipedia for Sweden
https://en.wikipedia.org/wiki/2020_coronavirus_pandemic_in_Sweden
source?:
https://www.arcgis.com/sharing/rest/content/items/b5e7488e117749c19881cce45db13f7e/data
Statistikdatum,Totalt_antal_fall,Blekinge,Dalarna,Gotland,Gävleborg,Halland,Jämtland_Härjedalen,Jönköping,Kalmar,Kronoberg,Norrbotten,Skåne,Stockholm,Sörmland,Uppsala,Värmland,Västerbotten,Västernorrland,Västmanland,Västra_Götaland,Örebro,Östergötland
2/4/20,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/5/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/6/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/7/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/8/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/9/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/10/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/11/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/12/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/13/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/14/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/15/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/16/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/17/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/18/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/19/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/20/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/21/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/22/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/23/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/24/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/25/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
2/26/20,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0
2/27/20,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0
2/28/20,8,0,0,0,0,0,0,1,0,0,0,0,2,0,2,0,0,0,0,3,0,0
2/29/20,3,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,2,0,0
3/1/20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
3/2/20,5,0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0,0,0,3,0,0
3/3/20,13,0,0,0,0,0,0,0,0,0,0,1,10,0,0,0,0,0,0,2,0,0
3/4/20,29,0,0,0,0,0,0,0,0,0,0,7,21,0,0,0,0,0,0,1,0,0
3/5/20,25,0,0,0,0,0,0,0,0,0,0,0,22,0,2,0,0,0,0,1,0,0
3/6/20,60,0,0,0,2,0,0,0,0,0,0,8,36,0,1,11,0,0,0,1,1,0
3/7/20,33,0,0,0,0,0,0,0,0,0,0,5,21,0,1,0,0,0,0,5,1,0
3/8/20,46,0,0,0,0,1,0,2,0,0,0,0,29,0,1,0,0,0,0,11,2,0
3/9/20,101,0,0,0,0,4,0,6,0,0,1,3,64,1,0,7,0,0,0,15,0,0
3/10/20,98,1,0,0,0,1,0,0,1,1,0,34,26,0,4,3,8,6,0,13,0,0
3/11/20,196,6,1,2,1,16,3,16,2,7,4,37,32,6,4,2,0,0,0,57,0,0
3/12/20,151,2,3,0,2,9,5,7,2,2,0,32,42,3,11,4,1,3,0,19,3,1
3/13/20,152,0,1,0,1,9,3,4,0,3,1,42,31,6,10,3,0,2,5,19,2,10
3/14/20,71,0,0,0,1,0,3,0,2,1,0,25,18,1,4,1,3,0,0,5,0,7
3/15/20,69,1,0,0,0,2,7,4,0,1,0,4,17,4,0,1,1,0,0,18,0,9
3/16/20,83,0,0,0,2,1,1,2,0,0,0,3,34,12,2,2,2,1,7,6,0,8
3/17/20,120,1,3,1,4,3,0,1,0,1,1,6,35,5,5,1,4,1,6,13,16,13
3/18/20,145,1,2,1,2,2,4,2,1,1,0,8,58,0,17,1,3,1,0,10,3,28
3/19/20,143,0,2,1,0,2,1,2,1,1,1,2,66,5,5,0,2,0,1,14,9,28
3/20/20,180,0,5,0,5,5,3,3,1,0,5,5,84,4,1,2,5,0,2,23,5,22
3/21/20,134,0,0,0,4,3,14,4,1,0,3,5,71,6,2,1,0,0,0,8,0,12
3/22/20,117,0,5,0,0,1,9,1,1,0,3,3,59,11,5,1,1,0,0,4,0,13
3/23/20,182,0,9,0,3,4,0,2,3,0,5,7,99,2,8,2,0,2,3,9,6,18
3/24/20,230,0,9,0,5,0,4,5,1,2,6,5,105,14,11,3,3,2,4,10,11,30
3/25/20,314,3,13,1,7,7,2,7,2,1,5,13,154,37,15,0,4,2,3,19,8,11
3/26/20,286,0,8,4,5,9,7,9,6,2,3,7,132,16,12,0,3,3,5,20,6,29
3/27/20,366,2,15,1,9,3,3,15,5,4,4,10,176,26,20,1,2,2,11,18,6,33
3/28/20,301,0,6,0,12,6,8,9,1,2,4,2,147,9,7,3,5,2,3,25,8,42
3/29/20,281,4,10,0,11,2,2,8,1,4,2,3,150,4,11,1,1,9,0,15,3,40
3/30/20,413,0,9,0,10,5,2,15,3,1,5,5,169,60,21,1,7,6,23,27,17,27
3/31/20,475,1,23,1,14,7,1,17,2,5,6,7,209,49,15,0,8,13,10,29,11,47
4/1/20,486,5,19,0,30,4,0,13,5,1,5,8,206,49,24,2,5,2,11,29,5,63
4/2/20,554,3,6,0,17,9,4,32,5,7,8,8,217,34,28,0,12,1,18,47,28,70
4/3/20,601,1,20,2,16,12,2,29,2,2,6,24,246,59,38,1,17,3,27,46,21,27
4/4/20,357,4,18,0,12,2,2,15,1,2,3,12,129,17,11,1,17,6,14,30,3,58
4/5/20,341,1,7,0,7,3,0,12,3,2,2,6,172,27,9,1,9,2,7,30,0,41
4/6/20,390,0,16,0,12,10,4,10,5,3,10,7,130,18,31,2,5,4,18,54,12,39
4/7/20,739,1,28,0,16,13,5,23,4,14,17,24,243,42,37,7,14,10,46,64,74,57
4/8/20,656,2,28,1,17,9,8,19,2,7,12,15,271,33,29,1,12,5,23,68,37,57
4/9/20,605,0,30,1,18,11,8,21,1,5,5,11,229,37,27,4,12,4,24,100,4,53
4/10/20,123,0,0,0,0,0,0,0,0,0,0,0,96,0,0,0,0,0,2,8,0,17

This project is limited to UK COVID-19 data.