[WIP] Refresh development docs and flow

Part of #740

Proposed Changes

Release Note

Docs

Let's keep this as wip, i had another idea for the "catch all local dev script" :smile:

There isn't any kafka setup target (is it inside knative_setup?)

Yes, Kafka is a dependency just like eventing, in my dev loop, I usually deploy both of them when I start.

My problem with makefiles is that the way you developed it is not very "makefile" idiomatic. You should have target dependencies, naming "compliant" to best make practices (e.g. cleanall, buildall, all) etc. What you're really using here of makefiles is just the parsing of the "target" command, nothing else. I don't see the point of using makefiles only for that, because it sets "expectations" and using it as it should be used is also not fitting our needs (because then, for example, integration-test should rebuild everytime kind the whole project).
My idea to improve the local dev loop was something different: a single script, like ./dev.sh knative-setup, where we have pretty much the targets we have here, but not a single line of "build logic". If you just type ./dev.sh, it prints all the different things you can do with the script. How does that sound?

This is what I wanted with this PR, I chose makefile because I don't need to build the error-prone logic for parsing arguments.

Regarding command names:
I chose 2 terms, one the opposite of the other, and used them throughout: up and down.
These 2 terms follow a single component: chaos-(up|down), sacura-(up|down), deps-(up|down).
Your suggestion in my opinion make commands less rememberable:

sometimes run
sometimes deploy
sometimes clean
sometimes teardown

IMO a single term should be used, and I really like up and down, they are short and simple to type.

This is what I wanted with this PR, I chose makefile because I don't need to build the error-prone logic for parsing arguments.

I understand your point of view, but the makefile you've developed is not what an usual GNU make user is going to expect. When you use a tool like that, you inherently set expectations like the ones described above.
I know that going to a shell script adds error-prone parsing logic, but here we're merely talking about taking the first positional argument and do a switch case on it...

Also, If we use integration-test, unit-test, and so on, why the command to run sacura test should be test-sacura?

That was a mistake i think, sacura-test is fine :smile:

Ok, naming updates, I'll use deploy-<something>, teardown-<something>, and <something>-test

I understand your point of view, but the makefile you've developed is not what an usual GNU make user is going to expect. When you use a tool like that, you inherently set expectations like the ones described above.
I know that going to a shell script adds error-prone parsing logic, but here we're merely talking about taking the first positional argument and do a switch case on it...

Ok, I'll move this to a bash script.

/retest

/test pull-knative-sandbox-eventing-kafka-broker-unit-tests

/test all

Fancy output :)
Unrecognized action

Usage                                                      for more information read DEVELOPMENT.md
./hack/run.sh <command>

command:
   deploy-infra                                            Deploy eventing, Kafka (Strimzi), publish test images
   teardown-infra                                          Remove eventing, Kafka (Strimzi)
   deploy                                                  Deploy eventing-kafka-broker
   teardown                                                Remove eventing-kafka-broker
   unit-tests, unit-test                                   Run unit tests
   unit-tests-data-plane, unit-test-data-plane             Run data-plane unit tests
   unit-tests-control-plane, unit-test-control-plane       Run control-plane unit tests
   build-tests-control-plane, build-test-control-plane     Run build tests
   integration-tests, integration-test-control-plane       Run integration tests
   deploy-sacura                                           Deploy sacura job
   sacura-test                                             Run sacura tests
   teardown-sacura                                         Remove sacura job
   deploy-chaos                                            Deploy chaosduck
   teardown-chaos                                          Remove chaosduck
   profiler                                                Run profiling tests
   generate                                                Run code generators

/retitle Refresh development docs and flow

/retest

/test pull-knative-sandbox-eventing-kafka-broker-integration-tests

I cannot wait to start using this PR!

/test pull-knative-sandbox-eventing-kafka-broker-integration-tests
Maybe that's flakyness? It failed only a test or two... https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative-sandbox_eventing-kafka-broker/749/pull-knative-sandbox-eventing-kafka-broker-integration-tests/1396736967135203328


Submit code

Hi, are you planning on pushing the actual code for the project in the (near) future? 🙂 Would be much appreciated!

On my side too, I have been looking out for this code since the workshop

I sent them an email, I'll keep you posted :).

Thank you!


Lyche different openinghours

Remember to run the rake task created in this branch before deploying.

Remember to rebase away my commit that says "Nå skal alt være klart, Simon" :)

Probably squash everything at a point.

Probably squash everything at a point.

Yeah, that works too!


Duplicate migrations when "size" attribute specified

Consider following database schema (schema.yml for sfPropelORMPlugin) for MySQL:
propel:
table:
decimal_column:  { type: DECIMAL, size: "10,2" }
Propel will generate the following migration code for this column every time the diff command is issued:
ALTER TABLE table CHANGE decimal_column decimal_column DECIMAL(10,2);
Propel version 1.6.2

duplicate of 167


crash with C2ME

Mod Name
C2ME
Mod Homepage
https://www.curseforge.com/minecraft/mc-mods/c2me-fabric
Describe the bug
crash at start
Steps to reproduce

start
wait a little
see
...

Logs
https://pastebin.com/RAAvGS3Q
Additional context
It's not a normal crash and it look like it's C2ME with make something wrong

It doesn’t work out of box. Requires changes to config in order to work.

what I need to change ?

read the last 7-8 lines of your debug.log after your game crashes. it’ll tell you what mixin is failing. after that, go into c2me.toml and change values from “default” to false

OH one last thing - C2MEs results varies system to system. I have a AMD cpu, and my friend has Intel. We both used the same config in my modpack. Creating a world for me; no issues but, my friend's client crashed when they tried to create theirs. It's odd and not entirely Sinytra's fault. The mod C2ME is still in it's experimental stages, I would recommend shelving it for now or use Fastload mod

ok

Getting this crash with:

c2me-fabric-mc1.20.1-0.2.0+alpha.11.5
Connector-1.0.0-beta.41+1.20.1
fabric-api-0.92.0+1.11.5+1.20.1

Config:

noTickViewDistance off
threadedWorldGen on, without this the mod isn't actually very useful

made an issue in the c2me repository a while back https://github.com/RelativityMC/C2ME-fabric/issues/257

I tried adding compatibility but I got very little support in the Sinytra Connector Discord so I'm still stuck

Is there any plan to make this work? I really rely on that mod


Git archives

Anyone would not have happened to have cloned the original repository from iArtorias before it was removed? :-)

This is the closest thing we have to a clone right now, I had to pull it off the Internet Archive and reupload it manually.

I just turned on discussions, so no need to open issues for questions anymore. Moving to Q&A.


{Doc Improvement][AI library validation content update]

Updated validation guidelines for Apps powered by AI.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md
93
97
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/TOC.yml
99
6
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md
93
97
link
:white_check_mark:

msteams-platform/whats-new.md
93
35
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.


T020: openmm warning

On the third code cell, the following warning appears
Warning: importing 'simtk.openmm' is deprecated.  Import 'openmm' instead.
/home/michael/.miniconda3/envs/teachopencadd/lib/python3.9/site-packages/MDAnalysis/coordinates/XDR.py:237: UserWarning: Reload offsets from trajectory
 ctime or size or n_atoms did not match
  warnings.warn("Reload offsets from trajectory\n "

I think this was addressed in T019 also at some point (PR https://github.com/volkamerlab/teachopencadd/pull/308). @dominiquesydow ?

Yes, I think this should have been addressed --- did you still see this issue after merging that PR?


Improvements to follow serialization + library compatabilities

@rmutter for review

We updated django-oauth-toolkit (https://github.com/yeti/YAK-server/commit/55e1d7df097cf8a9c09f9459d5395975c5a905ed) in test_requirements.txt but never updated setup.py, which still allowed for installation of v0.7.2. Rather than updating the version, I've included a version conditional so this still works with the older library version
DRF >= 3.1 doesn't support PaginationSerializer
DRF >= 3.1 deprecates PAGINATE_BY in favor of PAGE_SIZE
added FollowedMixin similar to LikedMixin and added tests for both

@baylee couple of comments - like the checking on versions logic :+1:

@rmutter updated


Bump up version

coverage: 96.762%. remained the same
when pulling 9828d4ece345797cd873e5b99d721f08a801662d on bumpup-version
into 20707b77d2ce7479d5de1309065ab8184d3f17ed on 2.0.


Torch and Torch-quantization module mismtach

Hello !
Thank you for making this repository, it has been very helpful with my research. I came across an error which is fully documented and solved in the following issue - https://github.com/Deci-AI/super-gradients/issues/1045#issuecomment-1690484940
The problem being torch 1.12 and torch-quantization 2.1.2 are incompatible so we need to downgrade to torch 1.11 which resolves the issue.
The requirements and the readme need to be updated to reflect the same

Hi @IamShubhamGupto ,
Thank you for finding this issue.
I actually forgot to update my installation requirements.
I did correctly for docker setup.
I am updating the requirements.


Add Verbose console type

Context
See #2642

@eriwen I would appreciate hearing your opinion on #2642 . The way I implemented is adding an overloading method
public OutputEventRenderer addConsole(Console console, boolean stdout, boolean stderr, ConsoleMetaData consoleMetaData, boolean verbose)

with extra verbose parameter, see the file diff subprojects/logging/src/main/java/org/gradle/internal/logging/sink/OutputEventRenderer.java in this PR and OutputEventRenderer.
However, to test it, I have to invoke attachAnsiConsole(OutputStream outputStream) with extra verbose argument here, but I don't want to modify attachAnsiConsole or write an overloading attachAnsiConsole. WDYT? Am I missing anything?

@eriwen Please take a look at this when you're free. :-)

@lacasseio could you take a look at this when you're free?

@lacasseio I've made some change, could you take a look at it when you're free?


use angular material instead of bootstrap

@creativepsyco should I switch over to material then (and hence merge this PR) ?

@championswimmer upto you. I think material is fine. But as long as the templating system is independent I think we can go for anything. Also do squash your commits into 1 before merging. @mananwason is already doing the same.

Cool !
On 7 June 2015 at 21:03, Mohit Kanwal<EMAIL_ADDRESS>wrote:

@championswimmer https://github.com/championswimmer upto you. I think
material is fine. But as long as the templating system is independent I
think we can go for anything. Also do squash your commits into 1 before
merging. @mananwason https://github.com/mananwason is already doing the
same.
—
Reply to this email directly or view it on GitHub
https://github.com/fossasia/open-event-webapp/pull/11#issuecomment-109765313
.


Add dollar output

Adds the --usd true|false option, which allows the user to get an USD output of his fee estimation.
the output now looks like this:
> howmuch-rs fees estimate-on-network --tx-hash=0x073251e7ff3843c4954aa2e7f38d8c29034e34a1ddbaeb1e62605ec10ca22367 \
  --source-block-number=21410 \
  --destination-block-number=15925 \
  --usd true`
0.000485046227677767 ETH ($0.6158 USD)

Closes #2

my bad, forgot to run the command after working on beerus haha :p


change 'lib'，how to solve this problem?

Description

Related Issues

did you find a solution?

Fixed by bumping typescript down to 3.3.3
In bottom right, click on the version number to change, but first we must npm install -g<EMAIL_ADDRESS>Now tell vs about this new version by F1-> open user preferences -> search for typescript.tsdk update .json to
{
"typescript.tsdk": "/home/ubuntu/.nvm/versions/node/v8.15.1/lib/node_modules/typescript/lib"
}
Now reopen file and change typescript version at bottom right, this will resolve the problem!

Fixed by bumping typescript down to 3.3.3
In bottom right, click on the version number to change, but first we must npm install -g<EMAIL_ADDRESS>Now tell vs about this new version by F1-> open user preferences -> search for typescript.tsdk update .json to
You can get npm global install path with npm root -g
{
"typescript.tsdk": "/home/ubuntu/.nvm/versions/node/v8.15.1/lib/node_modules/typescript/lib"
}
Now reopen file and change typescript version at bottom right, this will resolve the problem!

Thank you!!! I resolve this problem according to the way.

Update: typescript@3.5.1(which is used by vscode) and<EMAIL_ADDRESS>can also solve this issue.
Which means, code-server can solve this by updating underlaying vscode version.


createBucket results in incorrect Metadata-Flavor

I included @google-cloud/storage in my node project and am attempting to do a basic creation of a bucket, but the function just results in an error everytime, the Metadata-Flavor error listed below. I attempted to manually add this header to every request leaving my node server, but that didn't work, and I didn't see that anywhere in the guide so I'm really not sure where I went wrong.
Environment details

OS: macOS 10.14
Node.js version: 9.8.0
yarn version: 1.12.3
google-cloud-node version: 2.3.1

Steps to reproduce

require @google-cloud/storage
attempt to use basic createBucket functions
get Metadata-Flavor error

I get this error
Error: Unexpected error determining execution environment: Invalid response from metadata service: incorrect Metadata-Flavor header.     at GoogleAuth.<anonymous> (/Users/connorelsea/Projects/remix-server/node_modules/google-auth-library/build/src/auth/googleauth.js:163:23)     at Generator.throw (<anonymous>)     at rejected (/Users/connorelsea/Projects/remix-server/node_modules/google-auth-library/build/src/auth/googleauth.js:20:65)     at <anonymous>     at process._tickCallback (internal/process/next_tick.js:118:7) (node:20467) UnhandledPromiseRejectionWarning: Error: Unexpected error determining execution environment: Invalid response from metadata service: incorrect Metadata-Flavor header.     at GoogleAuth.<anonymous> (/Users/connorelsea/Projects/remix-server/node_modules/google-auth-library/build/src/auth/googleauth.js:163:23)     at Generator.throw (<anonymous>)     at rejected (/Users/connorelsea/Projects/remix-server/node_modules/google-auth-library/build/src/auth/googleauth.js:20:65)     at <anonymous>     at process._tickCallback (internal/process/next_tick.js:118:7)

Passing manually worked for me (FYI):
const storage: any = new Storage({
  keyFilename: "filename-here.json",
  projectId: "project-id-here"
});

In my case, running dotenv.config(); was overwriting my env.

@Connorelsea The error you received appears to be an authentication problem.
How are you authenticating your application? Credentials are normally passed via the GOOGLE_APPLICATION_CREDENTIALS environment variable. Have you tried @mattferrin's suggestion?

Greetings @Connorelsea!  If you're still running into issues here... please do let us know!  We're going to close this out for now.


[CssBaseline] Rename from Reboot

Closes #10233
Breaking change
The new wording should clarify the purpose of the component. For instance, it's not about adding JavaScript polyfills.
-<Reboot />
+<CssBaseline />

Is there any change log page to check this changes between versions?

@osdamv https://github.com/mui-org/material-ui/releases


Address or workaround 32-bit build issues.

This at least gets it building and can run the zlib benchmark on 32-bit builds.

Can you use a non-preprocessor branch to switch between 32-bit and 64-bit (e.g. sizeof(void*) == 4)? That will make it harder to break 32-bit support when compiling for 64-bit.

Reworked the patch to avoid the preprocessor conditionals, and to reuse more code.
Increased the max to 1.5GB and made it common, but what about a 64 bit runtime which can cope with more.
Still not clear on compileAddress(). There do not seem to be 'far addresses' in a 32 bit build and no 64 bit addresses so the code looks ok as-is?

The binary path is legacy and only has 32-bit addresses, so I'm not too concerned about whether it's limited to 1, or 2, or 4 GB of memory usage. 1.5GB is fine for the module max memory declaration, but I think as the address-space reservation size it will break the address masking which assumes the address-space is a power of 2.
compileAddress should do something like this:
auto byteIndex =
    sizeof(uintptr) == 8 &&  isFarAddress ? dispatch(*this,address,TypeId::I64)
  : sizeof(uintptr) == 8 && !isFarAddress ? irBuilder.CreateZExt(dispatch(*this,address,TypeId::I32),llvm::Type::getInt64Ty(context))
  : sizeof(uintptr) == 4 &&  isFarAddress ? irBuilder.CreateTrunc(dispatch(*this,address,TypeId::I64),llvm::Type::getInt32Ty(context))
  : sizeof(uintptr) == 4 && !isFarAddress ? dispatch(*this,address,TypeId::I32)
  : nullptr;
assert(byteIndex);

Yes, needs to be a power of two for now. Thanks.
Still don't see the need for handling the 'far address' on a 32-bit runtime, and it's not clear if truncating/wrapping is going to be what is agreed for wasm, but I guess you have something in mind and it seems fine to me for now. Thanks.

Thanks. Implicitly wrapping/masking the address is certainly not part of WebAssembly, and the 64-bit addresses have since been removed from the spec interpreter; just trying to keep things consistent with the other code that's there. :)


Print out hints when unknown option is used in cmdline

It will be easier for user to get instant feedback on screen about what is wrong.
For example, better to change ./src/tpm2_listpcrs.c as below:
        case '?':
-            //              printf("Unknown Argument: %c\n",optopt);
+                          printf("Unknown Argument: %c\n",optopt);
            returnVal = -6;
            break;

listpcrs is already done:
        case ':':             LOG_ERR("Argument %c needs a value!\n", optopt);             goto error;         case '?':             LOG_ERR("Unknown Argument: %c\n", optopt);             goto error;         }
but I get what you're driving at. We'll leave this open until someone verifies all tools.


source maps

https://sourcemaps.info/spec.html
https://www.bugsnag.com/blog/source-maps

add as output possiblity in new runMulti method

http://sokra.github.io/source-map-visualization/

https://www.youtube.com/watch?v=NkVes0UMe9Y
https://www.npmjs.com/package/vlq
https://www.npmjs.com/package/sourcemap-codec

https://github.com/webpack-contrib/coffee-loader

use https://www.npmjs.com/package/source-map as its the one used in webpack

done, closing
needs some adjusting, but it will be an ongoing effort


trtGptModelInflightBatching.cpp:(.text+0x25b6): undefined reference to `ompi_mpi_comm_world'

for benchmarks/cpp
make -j benchmarks
[  2%] Built target common_src
[  3%] Built target layers_src
[  8%] Built target runtime_src
[ 90%] Built target kernels_src
[ 90%] Built target tensorrt_llm_static
[ 91%] Built target tensorrt_llm
[ 98%] Built target nvinfer_plugin_tensorrt_llm
Consolidate compiler generated dependencies of target gptManagerBenchmark
Consolidate compiler generated dependencies of target gptSessionBenchmark
Consolidate compiler generated dependencies of target bertBenchmark
[100%] Linking CXX executable gptManagerBenchmark
[100%] Built target bertBenchmark
[100%] Built target gptSessionBenchmark
/usr/bin/ld: /root/autodl-tmp/files/TensorRT-LLM/cpp/tensorrt_llm/batch_manager/x86_64-linux-gnu/libtensorrt_llm_batch_manager_static.pre_cxx11.a(trtGptModelInflightBatching.cpp.o): in function `tensorrt_llm::batch_manager::TrtGptModelInflightBatching::getKvCacheMaxNumTokens(std::optional<int>, std::optional<float>, nvinfer1::DataType, float, tensorrt_llm::runtime::GptModelConfig const&, tensorrt_llm::runtime::WorldConfig const&)':
trtGptModelInflightBatching.cpp:(.text+0x25b6): undefined reference to `ompi_mpi_comm_world'
collect2: error: ld returned 1 exit status
make[3]: *** [benchmarks/CMakeFiles/gptManagerBenchmark.dir/build.make:111: benchmarks/gptManagerBenchmark] Error 1
make[2]: *** [CMakeFiles/Makefile2:1780: benchmarks/CMakeFiles/gptManagerBenchmark.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:1691: benchmarks/CMakeFiles/benchmarks.dir/rule] Error 2
make: *** [Makefile:582: benchmarks] Error 2

Please enable OpenMPI on linux. Thanks!

Please enable OpenMPI on linux. Thanks!

I am facing the same issue. can you tell how to enable OpenMPI on linux  . ths

Please enable OpenMPI on linux. Thanks!

I am facing the same issue. can you tell how to enable OpenMPI on linux . ths

apt-get install openmpi-bin libopenmpi-dev. Thanks.

Thanks. I'm closing that issue. Feel free to reopen if needed.


How can I use "initialPaintMode" in version 0.31

For some reason my project uses flutter v1.22.6, so I can't use image_painter v0.4.0

I am sorry, I can't go ahead and add features to previous versions because every time I add something to the existing code, I'll have to publish the change. I would suggest you migrate the project. Or you can fork the project and modify it to work on 1.22.6.

I understand.
Thank you.

I understand.
Thank you.


Dask inferior to Biggus for streaming NetCDF data

Encountered a specific problem while scoping #2839
It seems that streaming (unrealised) cube data from one NC file to another may be slower with Dask than Biggus.
More seriously, the memory usage seems much less well controlled, and can cause serious machine clogging,

Details:
Testing with this dataZoo file :
filepath = '/data/local/dataZoo/netCDF/largeFile/tas_day_HadGEM2-ES_historical_r1i1p1_18591201-20051130.nc'
nc_small = iris.load_cube(filepath)

print nc_small.shape
    (52560, 145, 192)

print nc_small.lazy_data().nbytes / 1.e6
    5853.0816

Size is such that 10 timepoints ~ approximately 1Mbyte of file data.
I have been timing saves of portions of this data to a new NetCDF file in the local temporary space.
Like this:
def time_datasave(cube):
    tmp_dir = os.path.join(os.environ['TMPDIR'], os.environ['USER'])
    tmp_filepath = os.path.join(tmp_dir, 'tmp.nc')
    t_start = datetime.datetime.now()
    iris.save(cube, tmp_filepath)
    t_end = datetime.datetime.now()
    print('Data size = {:.1f} Mbytes'.format(cube.lazy_data().nbytes / 1e6))
    print('Time taken : {:12.6f} seconds'.format(
        (t_end - t_start).total_seconds()))

Because of general Unix filesystem caching, things like this often need repeating to get consistent answers.
( For instance, loading this file can take about a minute, and repeating takes about 0.2 seconds ! )

Basic timings compared using above method + switching between Iris 1.13 and recent master (Iris commit db473b1b5) :

n-data-points
data-size
Dask time / secs (3 times)
Biggus time / secs (3 times)

5000
0.56 Gb
5, 1.5, 1.5

10000
1.1 Gb

15000

DASK
:5000 --> 0.56Gb
7, 7, 7
:10000 --> 1.1Gb
:15000 --> 1.7Gb

BIGGUS
:5000 --> 0.56Gb
5, 1.5, 1.5
:10000 --> 1.1Gb
8, 3, 3
:15000 --> 1.7Gb
10, 24, 17, 14

Viewing the system monitor during these tests reveals that Dask is using a lot of memory, whereas the Biggus operation hardly uses any.
The 15k-point case produces a memory graph like this :

Note: the load actually starts at about the -40 second points, and ends about 0.
What it may be doing for about 10 seconds after the memory is released is unclear.

It seemed obvious that the difference may be due to our crude chunking strategy.
But re-chunking the data does not seem to offer any immediate improvement :
>>> tmp = nc_small[:15000]
>>> tmp.lazy_data()
dask.array<getitem, shape=(15000, 145, 192), dtype=float32, chunksize=(15000, 145, 192)>
>>> tmp.data = tmp.lazy_data().rechunk((1, 145, 192))
>>> tmp.lazy_data()
dask.array<rechunk-merge, shape=(15000, 145, 192), dtype=float32, chunksize=(1, 145, 192)>
>>> time_datasave(tmp)
Data size = 1670.4 Mbytes
Time taken :    45.382178 seconds
>>>

The system memory graph of this operation looks basically just the same as before, which is very puzzling.

Progress report:
Investigating with @djkirkham Friday (2017-10-20).
Found that while the above attempt to re-chunk has no effect, you can get this approach to work by instead supplying a chunks keyword to da.from_array.
It seems...
Re-chunking only affects the graphs built from a lazy array, and not the usage of the array itself : That is still optimised overall.
Thus, if you say a1=da.from_array(proxy, (3,4)); a2=a1.rechunk((1,4)); a3 = a2 + 1,
then the subsequent graph of  a3 shows 3 separate chunks of size (1,4).
However, when you evaluate a3.compute(), Dask still makes a single access `[0:3, 0:4]' on the proxy.
Whereas...
a1=da.from_array(proxy, (1,4)); a3 = a2 + 1; a3.compute()
Performs three proxy accesses [0:1, 0;4], [1:2, 0;4], [2:3, 0;4],
which is what we basically need to avoid excessive memory usage.
Printing repr(a3) does not show any difference between these 2 cases, so the chunks keyword in the from_array call is setting not just the resulting property  'array.chunks' but also something fundamental about how the proxy is accessed (which can not be reset by a rechunk operation).

Awaiting #2844 merge
#2839 shows that it works

Think we can close this now @pp-mo? At the time of measurement, we were comparing apples & oranges (biggus with autochunking vs dask with full netcdf variable chunks). Now that we have a similar scheme for dask by default in iris, do we get back to a similar level of performance?

Think we can close this ... Now that we have a similar scheme [[as biggus chunks]] do we get back to a similar level of performance?

#2839 indicates it should be ok.
More significantly, checking with System Monitor, the nasty memory usage was definitely fixed


Supply License

I know it's just a tiny script, but it would be nice to supply a license (MIT is a great choice ;) )

Agreed

Thank you!


UX/UI: Empty message modal on reload

cobased.com:
Under MacOS/Safari, with an installed SecureLogin app, and logged in. Whenever I click on "Change securelogin" and press cancel - and/or allow and later on close the securelogin app -, doing a reload pops up an empty message modal with a close button in the browser.

Got it, it happens because the pulling request fails but for some reason readyState jumps right to 4 (successful response) which alerts empty body.
Actually it's only relevant to Playground because normal sites have better handling of responses. fixed
      if(cb && x.response.length > 1) cb( (x.response) )


Failing e2e tests - scorecard-golang on ossf-tests/scorecard-action

Matrix: {
"results_format": "sarif",
"publish_results": true
}
Repo: https://github.com/ossf-tests/scorecard-action/tree/main
Run: https://github.com/ossf-tests/scorecard-action/actions/runs/2504994475
Workflow name: scorecard-golang
Workflow file: https://github.com/ossf-tests/scorecard-action/tree/main/.github/workflows/scorecards-golang.yml
Trigger: push
Branch: main

I think there are issues going on with Rekor server causing these failures. Closing these for now and will investigate further is any action is necessary.


ASP.NET Core 2.1.1 fails with HTTP Error 502.5 - Process Failure

Hello,
After upgarding my project from .NET CORE 2.0 to .NET CORE 2.1, and upgraded all microsoft packages to 2.1.1. With updated visual studio to 15.7.4, .NET CORE 2.1 sdk(V2.1.3) and .NET CORE 2.1 runtime(V2.1.1) installed i am getting this error when i try run my app.

Please follow the troubleshooting steps and let us know if you still have an issue:
https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/troubleshoot?view=aspnetcore-2.1#app-startup-errors

I had the same exact issue.
Version v2.1.301 should fix that (Previously had v2.1.300) .

-Open Command Prompt
-Navigate to bin directory of your project. Let's assume your project name is 'test'
-Run 'dotnet .\test.dll' and you will see something like Microsoft.Aspnetcore.all version 2.1.2 was not found.
-Then run 'dotnet -info' and you will see your .netcore runtime. Mine was 2.1.1.
So I downgraded my Microsoft.Aspnetcore.all nuget package to 2.1.1 and it worked after.
Alternatively, you could upgrade .netcore runtime but that's more work :)

I had the same issue after installing the hosting package. The fix was much simpler for me. Just running IISRESET resolved it.

I added the following line in the csproj and it started working. All troubleshoots suggested by @Tratcher did not help me at all because of misleading information
<PackageReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Design" Version="2.1.0" PrivateAssets="All" />

I just update my dotnet sdk core version in global.json file with installed dot net version, and my project start working
C:>dotnet --version
2.1.402
global.json
{
"sdk": {
"version": "2.1.402"
}
}

-Open Command Prompt
-Navigate to bin directory of your project. Let's assume your project name is 'test'
-Run 'dotnet .\test.dll' and you will see something like Microsoft.Aspnetcore.all version 2.1.2 was not found.
-Then run 'dotnet -info' and you will see your .netcore runtime. Mine was 2.1.1.
So I downgraded my Microsoft.Aspnetcore.all nuget package to 2.1.1 and it worked after.
Alternatively, you could upgrade .netcore runtime but that's more work :)
The error on web browser and events log is useless. Can't wait for .netcore 3 :P

This answer is really helpful - only "Run 'dotnet .\test.dll'" should be "Run 'dotnet .\NameOfYourMainApplication.dll'" (obviously "NameOfYourMainApplication" is a placeholder for the name of your application DLL ;-)
Also, I personally found it easier to upgrade the .netcore runtime than doing another build and uploading it to my server. I guess after each Visual Studio update, you should probably check this URL and upgrade your server, if a new version is available: .NET Core 2.1 downloads
Eventually, you'll move to .NET Core 2.2 and that's simply "2.2" at the end of the URL: https://www.microsoft.com/net/download/dotnet-core/2.2
I'm leaving this here for others and my future self when I run into a broken Web app update process during the next crunch mode when the last thing I have time for is following useless "troubleshooting" guides.

@estomagordo have you tried the self-contained deployment? This worked for me.

@rpawlaszek yes, eventually I noticed someone mentioned this. And it worked. Thanks.

Downgrade nuget Microsoft.AspNetCore.All to 2.1

In the release folder:
      "Microsoft.AspNetCore": "2.1.1",
      "Microsoft.AspNetCore.All": "2.1.1",
      "Microsoft.AspNetCore.App": "2.1.1",
      "Microsoft.EntityFrameworkCore": "2.1.4",
      "Microsoft.EntityFrameworkCore.Tools": "2.1.4",
      "Microsoft.NETCore.App": "2.1.0",

Could the last line be throwing it off? If so, how to update? the package is blocked by nuget

@adamcweitzman, could you check your nuget version?

yes, copy and paste of the nugget:

maybe i need to manually set the path? in my runtime.config in \bin I still have the correct version

I meant the version of nuget you use. I had no problem with installing the 2.1.5 version of Microsoft.AspNetCore.App. Go to powershell and simply type in 'nuget'

The version I have installed is 4.8.1 Could you try with this one? And another thing: what is the environment you have set for the self-contained deployment? (mine: win-x86)

Got same error on a VM hosted on Azure with IIS,  the self-contained deployment seems to fix this issue for me for now.

I deployed an app to IIS in an Azure VM, came back to it after a few hours and it started showing this error.
-Run 'dotnet .\test.dll'  spins up the app fine (no errors).
self-contained deployment has not fixed this for me


Update the logic of openlineage.airflow.macros.lineage_parent_id

The macro openlineage.airflow.macros.lineage_parent_id currently generates the parent_id as namespace/name/run_id, where name however is a UUID generated from the task metadata, and run_id is the concatenation of the task instance timestamp and try number.
This isn't compliant with the OpenLineage conventions. I'd expect name=<dag_id>.<task_id>, as it's a convention in other parts of the codebase, and run_id to be a UUID.

May I propose is to just remove the lineage_parent_id macro, and instead use lineage_run_id with some new macro lineage_namespace. This allows passing values to child job like Spark session without parsing, e.g.:
SparkSubmitOperator(
  ...,
  config={
    "spark.openlineage.parentJobNamespace": "{{macros.OpenLineageProviderPlugin.namespace()}}",
    "spark.openlineage.parentJobName": "{{dag.dag_id}}.{{task.task_id}}",
    "spark.openlineage.parentRunId": "{{macros.OpenLineageProviderPlugin.lineage_run_id(task_instance)}}",
)

There is no need to deprecate the macro, we can simply add two new macros - then users can choose to either pass all the information and parse it in spark or pass everything separately.

we can simply add two new macros

Done: #2582


is it secure to listen on *:4001 ?

vscode 1.85.1 on macOS Sonoma 14.2.1
sudo lsof -i -P | grep -i listen

I get *:4001 instead of localhost:4001.
I think the default shall be listening on localhost only.
Probably offering an option in extension settings that allows changing the IP address on which it listens.

Good question. I don’t think that was intentional since I didn't specify which host to respond to:
https://github.com/fregante/GhostText-for-VSCode/blob/6f8f5f2fa96cb7f7287c4eda6fc56ba7d9960115/source/server.ts#L50
The Sublime Text version also doesn't specify the host, but its default behavior might be different:
https://github.com/GhostText/GhostText-for-SublimeText/blob/8ace809a1788ce99268cd585ac5c6635e84320f1/GhostText.py#L74C24-L74C46


Using S3 / Cloudfront as cache server

Hi,
I have setup mod_pagespeed to optimize my wesite content delivery .
I use ModPagespeedRedisServer to store all optimized content created by mod_pagespeed into a redis.
Could I use a S3 / Cloudfront to store / access it ?
Reards,

I think you can't really get around routing through Apache/mod_pagespeed to get to the optimized assets.


Add description meta tag

Add description meta tag to every page for better SEO.

Do a PR with your suggestions.


Don't use metricname or rowkey caches to optimize writes.

Prior to this change, the caching is buggy - it populates the cache before attempting to write to the Cassandra table. If the write fails and triggers a retry, the presence of the rowkey/metricname in the cache filters the insert out of the second write attempt. Then the write returns success.
@speezepearson and I discovered this bug while investigating why rollups were failing to populate all data from the source series into the rollup series for some high-cardinality metrics.
Tests we did to confirm this fix:

Hijacked hosts in our stage deployment and confirmed that the rollup query (A) reliably fails to populate the rollup series without this change, and (B) successfully populates with this change.
We've also been running a build with this change in our stage deployment for several hours today with no observable change in machine resource utilization.
On Friday, we ran this change on a prod host for several hours. Again, no observable change in machine resource utilization.

It's possible to make this caching correct, but it's much simpler to delete it. Since we don't observe any performance impact by doing so, it seems safe to pessimize this code path in pursuit of correctness.

This will cause huge write amplification due to always needing to write the index columns.

Not sure which host you hijacked, the end of this one particular host exceeding the rest in write rate does align with the last deployment (which I assume cleared your hijack/test):

This triples the write rate from that host versus its peers. Even if there is no noticeable impact now on query performance, this will have a pretty significant impact on the cluster.


WIP: DOC: new docs landing page + tutorial overhaul

This PR illustrates one idea for what a new documentation landing page might look like.  It's here to generate discussion / responses.. This PR is not a complete changeset (as it doesn't yet offer a new home for most of the things it removed from the old docs landing page) and thus should not be considered mergeable.
cc #5937

This looks cool! Of course, now the tutorials need a place to go. Maybe create a new top-level menu item for them?

@wmvanvliet I think we need to find them a story. That's a bit what is being discussed in #5937, #5883 and other places.

here is the rendered version of documentaiton.html https://11328-1301584-gh.circle-artifacts.com/0/dev/documentation.html

here is how it looks:
https://11328-1301584-gh.circle-artifacts.com/0/dev/documentation.html

FYI, I just discovered that sphinxcontrib-mermaid available in pip uses mermaid 7.1.0, which results in the class styling of the nodes not working.  With current mermaid release 8.0.0 it works as expected.  I'll see if I can push the sphinxcontrib-mermaid maintainer to release a new version to pip; otherwise maybe we can install the extension from github.

here is the dynamically-generated flowchart in-situ.  (see note above about the node styling not working; here is how it would look if using mermaid 8.0.0: http://dan.mccloy.info/data/mermaid-test.html)

to share all ideas, here is graph made by someone in neurospin based on the initial graph of Lauri.

I see that adding images to illustrate what blocks correspond to can be quite valuable. Is it possible with mermaid too?

@agramfort if you tie into the mermaid API directly (javascript), it is possible for the content of a node to be an image.  Here is an example on stackoverflow.  It also looks like if you're careful, you can put in <img> tags directly into the graph definition, as seen in this thread.  Meanwhile, I've forked mermaid, fixed the version number, and am telling CircleCI to install sphinxcontrib-mermaid from a zipball of my fork, so the node class defs should work now.  In the coming days I'll see what I can do with the images in the flowchart.

sounds good
images are not a blocker though

This pull request introduces 1 alert and fixes 1 when merging 3b1df7a1bf9422672ac085c309340cd765de531b into f9d19f48971d23113c2ef047df8910b6da37cd9f - view on LGTM.com
new alerts:

1 for Variable defined multiple times

fixed alerts:

1 for Variable defined multiple times

Comment posted by LGTM.com

not sure why circle failed, it's on tutorials I didn't really change (plot_brainstorm_auditory.py and plot_brainstorm_phantom_ctf.py).  Anyway, here's a first pass at the working with continuous data tutorial series.

A rebase should fix it

oops, yeah, meant to do that but it slipped through the cracks. will fix today.
On February 26, 2019 7:55:59 AM AKST, Eric Larson<EMAIL_ADDRESS>wrote:

larsoner commented on this pull request.
Can you rename the necessary no-plotting files and rebase?

@@ -397,6 +400,7 @@ def reset_warnings(gallery_conf, fname):
'show_memory': True,
'line_numbers': False,  # XXX currently (0.3.dev0) messes with style
'within_subsection_order': FileNameSortKey,

'filename_pattern': r'/.*(?<!).py$',  # anything that isn't
*.py

It looks like you got part of the way there but you'll need to rename
examples/datasets/spm_faces_dataset.py,
examples/decoding/decoding_rsa.py,
examples/visualization/make_report.py, and four files under
examples/realtime/ to have trailing underscores

@larsoner I've changed those filenames, but there was no rebase to do (the previous force-pushed commit was after a rebase around 15 hours ago, and nothing has changed since then)

@drammock this line is failing to do its job in `.config/circle.yml:
FNAMES=$(git diff --name-only $CIRCLE_BRANCH $(git merge-base $CIRCLE_BRANCH upstream/master));

On CircleCI we try to get a list of files that have changed. This list is used to determine which examples to run, and which datasets to download (including the BST ones, which otherwise require confirmation, hence the timeouts).
The problem is that it does not work with files that have been renamed, which your PR does a lot of. Instead of seeing tutorials/plot_brainstorm_phantom_elekta.py in the list, we need to see the name it moved to, tutorials/miscellaneous/plot_brainstorm_phantom_elekta.py. Can you see if you can fix this git command to give us the correct name list? In your case $CIRCLE_BRANCH should just be your local new-docs-landing-page.

aah, problem is that this isn't happening?  But why would it suddenly stop happening now; is it because the tutorial location moved from /tutorials/ to /tutorials/miscellaneous/?

See comment above; the changed-names autodetection fails due to moves rather than changes, and this set of names is used to find the set of datasets to download (while passing a command-line switch to accept license terms).

ah, yep.  Missed your prev. comment before I posted my supposition

This pull request introduces 1 alert and fixes 1 when merging ee22568aac6c25a7e99025bfab273f0530b4a61c into f9d19f48971d23113c2ef047df8910b6da37cd9f - view on LGTM.com
new alerts:

1 for Variable defined multiple times

fixed alerts:

1 for Variable defined multiple times

Comment posted by LGTM.com

@larsoner I think I figured out what's still wrong with circle, but I need some help fixing it.

These are the files that got renamed from filename.py to filename_.py to accord with the new practice of naming not-to-be-executed examples/tutorials with a trailing underscore (instead of naming to-be-executed examples/tutorials with a leading plot_).  I think what's happening is that those filenames are getting written to sg_execution_times.rst and then when that gets parsed to make an HTML file out of it, they're getting interpreted as links instead of just text, and sphinx gets mad because those links don't have matching targets anywhere.  What I can't figure out is why this doesn't fail for expyfun (notice version_checking_.py works fine there).

am I right about what's going wrong?
can you suggest an approach to fixing?

Try locally changing it to _noplot instead of just trailing underscore to test this idea. If it fixes things, it could be a SG problem that trailing underscores are not handled properly. As to why expyfun does not suffer from this, it's possible that it does not use / has not used SG master since the execution times PR was merged

https://github.com/sphinx-gallery/sphinx-gallery/pull/451

@larsoner in light of your lightning-quick fix to sphinx-gallery, should I just wait for that to get merged (.circleci/config.yml pulls a zipball of sphinx-gallery master), or should I update the circle config to pull a zipball from sphinx-gallery/larsoner:fix-exec?

I'd just wait, the error does not prevent the doc from being viewable in the meantime

This pull request introduces 1 alert when merging 4ec96426a9be4ed63d1aabed5ab7e14d9f4b04ee into e6a1f5e6e9640d2d90349b387b1395bf842560d7 - view on LGTM.com
new alerts:

1 for Unused import

Comment posted by LGTM.com

This pull request introduces 2 alerts when merging d7af7dc8dcaca06c4fad976b2d03669983c8b571 into c3e7571a9b698034cda94aae53004b55265057a9 - view on LGTM.com
new alerts:

2 for Unused import

Comment posted by LGTM.com

Very promising!

This pull request introduces 3 alerts when merging 807c94391a27a6ac028fe5e1fba8a6d85f23a4ba into 01a1aef46792d22dff39f38516268434a2497795 - view on LGTM.com
new alerts:

2 for Unused import
1 for Unnecessary pass

Comment posted by LGTM.com

This pull request introduces 2 alerts when merging 80ee4f460de8ed51c76b7d3daf970e35e57fff4b into 41f6f2bcd0b8e90807837e131314be81e0cd5ca6 - view on LGTM.com
new alerts:

2 for Unused import

Comment posted by LGTM.com

latest artifacts: https://11831-1301584-gh.circle-artifacts.com/0/dev/auto_tutorials/index.html

cool ! did you put the updated roadmap somewhere? just to know how long
still is road

This one is great! really great
https://11831-1301584-gh.circle-artifacts.com/0/dev/documentation.html#
I can stretch enough how I would like to land into that documentation.html.
some things I found (most probably you already have them in your list but just in case)
Now the buttons of the main page do not point properly. see https://11831-1301584-gh.circle-artifacts.com/0/dev/index.html
Maybe we should split the Tutorials with the same structure as the buttons of the main page and point there.
In the installations instructions there's a mismatch in the file naming(the file is named getting_started) + I would let the text be already in the page not only the outline.
https://11831-1301584-gh.circle-artifacts.com/0/dev/getting_started.html

@agramfort I changed the initial comment of this PR to include the roadmap with checkboxes.
@massich I've also added your suggestions to the checklist at the top of this PR.

This pull request introduces 2 alerts when merging b409bd02fc4869b717c672c70139bb8f8fc6d62b into 561ded7f8fa4c2c63ca8f429a2da98323d28d311 - view on LGTM.com
new alerts:

2 for Unused import

Comment posted by LGTM.com

This pull request introduces 2 alerts when merging e8655a63384c7f4406bfc7d8566038f73490569c into b74bb10d779dfd8144a4b6fd8fc5444f441f2141 - view on LGTM.com
new alerts:

2 for Unused import

Comment posted by LGTM.com

This pull request introduces 2 alerts when merging b0e72d91ff905a1e965d3a2761cac5b47e438528 into c30e70c53cd25997a8a9831ab5c3e827dd5f2966 - view on LGTM.com
new alerts:

2 for Unused import

Comment posted by LGTM.com

This pull request introduces 2 alerts when merging 97551293ac9e2875dee5bc75fc066bad8f85aeca into 56909cdbf35511d9837a5999ce1ffe2f47eee7bb - view on LGTM.com
new alerts:

2 for Unused import

Comment posted by LGTM.com

This pull request introduces 2 alerts when merging bc917f60ed75ecafa38103bffe632a7f1f1659d5 into 027f82d79b8055bad5c997829d409035de348fe8 - view on LGTM.com
new alerts:

2 for Unused import

Comment posted by LGTM.com

This pull request introduces 2 alerts when merging 03e810d2dbec76b833a1a46128aa4027e78145e3 into aa7b3a0ba1038e6ad7fb357e60844696e234c40b - view on LGTM.com
new alerts:

2 for Unused import

Comment posted by LGTM.com

This pull request introduces 2 alerts when merging 8af7554e4b202e01a5e4bdc2ed8d4497d6133058 into b3dfd7a1dd4cfc2fb501f9db9c4bcb3eb158cc2c - view on LGTM.com
new alerts:

2 for Unused import

Comment posted by LGTM.com

Killed
Makefile:44: recipe for target 'html_dev' failed
make: *** [html_dev] Error 137
Exited with code 2

Usually this is a memory problem. Probably you are using sample, uncropped, preloaded. Crop to 60 sec (and say this is for memory reasons) and it should work.
Also you need a rebase

(You can check this with mprof, anything over 2GB memory usage is asking for trouble)

This pull request introduces 2 alerts when merging b36a8262f30b36b1f5edee99134aeca05cc22797 into 9cc5d1457c29151eea73fa7f14619724182960c1 - view on LGTM.com
new alerts:

2 for Unused import

Comment posted by LGTM.com

This pull request introduces 2 alerts when merging d7fd58f3601451de10d53506a19eff60dc183a87 into 46055a3a4122bf30740f6cefcfb03310ce064738 - view on LGTM.com
new alerts:

2 for Unused import

Comment posted by LGTM.com

Errors are real (examples should not emit warnings so they are treated as errors)
https://circleci.com/gh/mne-tools/mne-python/12486

This pull request introduces 2 alerts when merging fdb50519ef59c8fe76863e7194117ca2bbb1ffe7 into ab49f9c124fe61f0d1c437ab33c2970833f2e71e - view on LGTM.com
new alerts:

2 for Unused import

Comment posted by LGTM.com

This pull request introduces 2 alerts when merging cf953efebb147f984424cf862731e5d7238f5012 into 767cd9246370d25b132b4d98206095e15779044f - view on LGTM.com
new alerts:

2 for Unused import

Comment posted by LGTM.com

This pull request introduces 2 alerts when merging 27a909f4cf788b21d1083d43e6f5c0508ddb06f4 into 767cd9246370d25b132b4d98206095e15779044f - view on LGTM.com
new alerts:

2 for Unused import

Comment posted by LGTM.com

rendered docs: https://12627-1301584-gh.circle-artifacts.com/0/dev/auto_tutorials/index.html

This pull request introduces 2 alerts when merging c164e414f9664d3666aafba639e1cccc424545cf into 5a9ae3c3d66b6275fffec217cf560acf651913d7 - view on LGTM.com
new alerts:

2 for Unused import

Comment posted by LGTM.com

@drammock is this PR still valid, or should we close? Can still use the list at the top, or maybe better, move to a dedicated issue.

@larsoner I've been avoiding closing it because I still reference the Circle rendering from time to time; I've been assuming that would get GC'd if we closed this PR.  Is that true?  If not, I'm fine with closing and migrating the checklist to a new "docs tracking" issue.

Apparently they keep them forever
https://discuss.circleci.com/t/circleci-artifacts-expiry/14212


Add tooltip to Filter input in Structured Logs and Traces page

Resolves #755
Screenshots
Structured Logs

Traces

@berkansasmaz please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@dotnet-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@dotnet-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@dotnet-policy-service agree company="Microsoft"

Contributor License Agreement

@dotnet-policy-service agree

Need to check if filter apply to field mentioned in text only or other too.

LGTM to me. @tlmii - Can you give another set of eyes?

Yep, will respond this afternoon.

Thanks again for the contribution, @berkansasmaz!

Thanks again for the contribution, @berkansasmaz!

I thank you very much for your interest and concern. My first experience of contributing to the dotnet organization was great and even a small contribution would make me feel very good, thank you again dotnet team 🙏🙏
See you next time 👋


Pseudo localized labels for Adoption testing

Critical Changes
Changes
Pseudo localized labels for Adoption testing. Please note that only "de" (German) labels went through pseudo process, you can ignore other languages.
@dcaballeroSf
Issues Closed
Community Ideas Delivered
New Metadata
Deleted Metadata

@dcaballeroSf FYI - this PR should only be used for creating a scratch org for lqa, but it will never be merged.

@dcaballeroSf FYI - this PR should only be used for creating a scratch org for lqa, but it will never be merged.

@dmkud It doesn't look like this PR was used, or even if it was for testing at one point, it's probably ready to be closed. Do you agree?

@force2b I agree. Closing it now


add edit button

Updated the mkdocs yaml file to include the edit and issue buttons. This will allow a user to create a GitHub issue or PR for the given page.
I also removed the mermaid plugin as a plugin is used now instead on the devhub side to render mermaid diagrams

Hi! Just following up on this PR. Is it ok to merge? Thank you!

Hi! Just following up on this PR. Is it ok to merge? Thank you!

@vijaivir, @bhuvan-aot - thoughts on this? I'm not sure what it does :D

@WalterMoar - the change adds an edit/issue button to the documentation pages. The Onboarding to application monitoring with Sysdig page has an example of it. Next to the title on the page, there is an icon of a page with a pencil. Clicking it will let a user open a PR or Issue on the repo. This lets users provide suggested edits to the page.
This PR is to add that functionality. Each page of this documentation would have that button.

@vijaivir, @bhuvan-aot @WalterMoar - is it ok for this PR to be merged?

bhuvan-aot - thank you for the approval. Do you have a timeline on when this PR will be merged?
Thanks!


3.0.0-alpha.51 TRV all enabled and wit set temp to 20ºC

Last upgrade broke all the config of my TRV ut changed it config and enabled all of them by default to 20ºC in Heat mode. I had some of them set to 35ºC and others Off. When I updated all of them changed. If I do any change in HA and restart they are again all On in 20ºC.

Thank you for your contributions and reports regarding climate/thermostat-related issues. I've noticed that this area has become increasingly complex, with overlapping tickets and discussions. To streamline the process and ensure we address everything effectively, I’ve decided to close the existing tickets on this topic.
Instead, I’m creating a centralized discussion where we can collectively revisit and tackle these challenges in a structured manner. Please feel free to share your insights, reproduce steps, and ideas there.


Configserver fails on startup because it tries to monitor changes inside jar

Caused by: java.nio.file.FileSystemNotFoundException: null
	at com.sun.nio.zipfs.ZipFileSystemProvider.getFileSystem(ZipFileSystemProvider.java:171) ~[zipfs.jar:1.8.0_92]
	at com.sun.nio.zipfs.ZipFileSystemProvider.getPath(ZipFileSystemProvider.java:157) ~[zipfs.jar:1.8.0_92]
	at java.nio.file.Paths.get(Paths.java:143) ~[na:1.8.0_92]
	at org.springframework.cloud.config.monitor.FileMonitorConfiguration.getFileRepo(FileMonitorConfiguration.java:201) ~[spring-cloud-config-monitor-1.2.0.RELEASE.jar!/:1.2.0.RELEASE]
	at org.springframework.cloud.config.monitor.FileMonitorConfiguration.start(FileMonitorConfiguration.java:135) ~[spring-cloud-config-monitor-1.2.0.RELEASE.jar!/:1.2.0.RELEASE]
	at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:173) ~[spring-context-4.3.3.RELEASE.jar!/:4.3.3.RELEASE]
	... 22 common frames omitted

The reason (I think) is that we set the profile to "native" and then ask it to monitor the config files at classpath:/launcher (which is inside the jar file). It works if you run from Maven or from the IDE, but not if you run the executable jar.

The problem is really that FileSystemNotFoundException is not an IOException and so the catch block in FileMonitorConfiguration doesn't work. Needs a fix in spring-cloud-config.

Some code: https://github.com/spring-projects/spring-boot-issues/tree/master/gh-7161

Moving to 1.2.1. For 1.2.0 we will remove the config server monitor feature.

Already fixed in spring-cloud-config.


Have a FieldGroup listen to its own changes

I have a FieldGroup, and whenever any field within that group changes, I want to run a function. Here are some approaches I've tried.
Firstly, we can't use the decorator form self.connect() because self isn't defined within the class.
Secondly, I tried doing so in the constructor:
from magicclass import FieldGroup, field

class Fields(FieldGroup):
    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)
        self.connect(self._changed)

    def _changed(self):
        print("Changed!")

    x = field(int)
    y = field(str)

Fields().show(run=True)

This doesn't seem to ever call _changed.
Lastly, if I instead use self.changed.connect(self._changed) in the constructor, it blocks the field group from listening to its child widget events.
How should I solve this?

Okay, it seems that overriding def _on_value_change(self, *args, **kwargs) -> None: for the FieldGroup does work.

Hi @multimeric ,
Just like other field objects, FieldGroup is supposed to be used as a class variable. Callbacks are connected via attribute access.
from magicclass import FieldGroup, field

class Fields(FieldGroup):
    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)
        self.connect(self._changed)

    def _changed(self):
        print("Changed!")

    x = field(int)
    y = field(str)

class A:
    group = Fields()  # <--- as a field

a = A()
a.group.x.value = 4  # [Out:] Changed!

As usual for Container, you can use self.changed.connect instead of self.connect to immediately connect the callbacks.
But according to your example, it seems that FieldGroup is actually very useful as a simple container. Let me think more about that and I'll add some features including direct usage of connect 😄

Hi @multimeric ,
I realized that using self.connect for the direct container usage is not a good idea. To use a field group as a class attribute, it is necessary to reconnect all the callbacks to the newly generated widget. If self.connect will connect the calback to self iteself, newly generated widget will be connect twice.
class A(FieldGroup):
    a = field(int)
    def __init__(self):
        self.connect(self_some._callback)  # <-- if callback is connected to self...

class MyClass:
    group = A()

ui = MyClass()
ui.group  # <---- then, the same callback will be connected twice here.

I'll add more notes to the connect function to avoid this usage.


responsive layout for points page

resolve #36

minWidth was changed due to minWidth being too large; before, it would start overlapping before the breakpoints changed so I had to make it smaller


Split the config for server and client

Why do we need to do that?

Why do we need to do that?

If we look at the current config, it contains several values, where some are grouped with its own purpose and some are not. Usually, we run Optimus in two modes, as the client and as the server, making it not straightforward which config is for which mode. And in the implementation, we pass some config values that are actually not needed for one mode. If we have a better separation, then it will be easier to maintain. For example, when we are running in the server, we only need the following configs and for when running the client, we need the following config.
cc: @sravankorumilli

Optimus generates a single CLI binary, its just matter of use how you want to use it. It can be run as a server or a client interacting with the server. When you use in production, you won't be using it for both situation at the same time. A single config will be used for one thing only. Because both of these modes are part of main optimus, splitting config just based on cli modes doesn't look a better design choice to me.
Optimus has a serve section for the server mode which is exclusive for this only, how is this confusing? Maintaining one config file vs maintaining two config file, which is more hassle?

If we look at the current config, it contains several values, where some are grouped with its own purpose and some are not.

Can you give an example @irainia

no clear separation between config used on server and config used on client (aka project repo) that lead to confusion

Lead to confusion to whom? CLI users for deploy and other commands? @deryrahman
Okay, let me give an example, if I want to expose a config related to plugins like, custom directory to look for plugins, where should it go? New client config or new server config?

Optimus will have two sets of users. people who deploy server and rest who use Optimus to manage jobs to interact with the server.
IMO, Server config should be provided on the fly. And not managed in any file or so.
As an example. optimus serve -c config.yaml When we start the Optimus server we should pass the config file. It should also be able to accept env params.
While on the other hand, for optimus cli config, I think we should have optimus config init which init config in user home location. This config should only be related to Optimus client and no config of server should be leaked in it. I have abstracted out the loading of this config in salt package actually.
https://github.com/odpf/salt/blob/main/cmdx/config.go
Still have a few improvements to be made. If this sounds good idea then I think it will require us to split the structs for server and client configs. A similar implementation can be found in Guardian.

Optimus config in home directory won't work nicely, we use that config to organise projects. Keeping it in home directory(for clients) is restricting it to be used with only one project where as keeping it in a git directory of project will scope it out to only that project. @ravisuhag
optimus serve -c config.yaml I agree providing this explicitly to override the config file make sense but I guess there should be a default location as well where the binary can look on its own right?
In an actual use case, a config file will never have both already according to design, unless you are a developer and experimenting something. Why do you think we are leaking server config at the moment?

Yes, fair enough for the first part. We can treat client config as root level as a project level. Something on the lines of global .gitignore and the local one. Any global config users want to put they can put at home.
Yes, even if there is a default location. Sever config we can go with the thought that the scope of that is only limited to server command and it does not mix with the client config at all.
The way I see server config from a user perspective is that they only need to take that into account when they start the server. I think even behind the scene, code can also reflect that. wdyt?

Any global config users want to put they can put at home.

Although I think it will be difficult for users to trace which config is effecting a certain behaviour when we choose to go with hierarchical configs but okay, not a big deal, thats a different problem we can discuss separately.

The way I see server config from a user perspective is that they only need to take that into account when they start the server.

This is already true with the current design. We have different keys for client and server configs. Thats what I am confused, why do we think splitting it into two files will achieve this?

it does not mix with the client config at all

Help me understand a single user behaviour example where its mixing right now? 😄

Think if it in this way, why did we choose to go with one binary for client and server and not two? Why do you think users are not confused with which command to run(client/server) and now we think they will get confused with configs?
Also you know this will also cause lot of duplication in configs right? Things that goes in both cases like log levels, plugin directories, etc.

If we look at the current config then there are few areas it is little confusing.

when someone looks at the config the first time, then it appears the serve section is the only section for server config, but there are other configs which needs to be configured for server.
host & serve.ingress_host, server.host what is used for what is another instance.

I believe because of these primary concerns, it is not very clear when we are consuming configs which configs we expect to be available and not available.
IMO, either.

We can have a clear segregation for client & server configs even if that means a duplication(log_level,plugin_path), everything defined in the optimus.yaml though
Or we avoid duplication and provide configs for both client & server combined, then we can have a single config for clients to reach optimus server avoid rest all (host,serve.ingress_host,serve.host), until & unless we process these configs differently.

From implementation point of view,  in both the options we can have additional structs for Client&Server configs, such that it is clear for the developer on what configs to use on when acting as a client & what configs to use when optimus is deployed as server. The only place to bother about that is while preparing that client & server configs.

From implementation point of view, I agree we need to have 2 struct, to define server config and client config. @sravankorumilli . But for the how we define the config in .optimus.yaml, I've several concern on that.
For the first suggestion, I believe it can be much cleaner because we explicitly define client and server config in single .optimus.yaml. For example, our config will be looked like this
...
client:
    log_level:
    project:
        name:
        config:
    namespace:
        name:
        ...
server:
    log_level:
    host:
    port:
    ...
...

But the drawback is, there's no case we run optimus in both mode, so there's no point we put field client on current project directory as well as there's no point we put field server in home directory.
For the second suggestion, we can have combined config without explicitly define the mode. The pros is, we can have a lot of flexibility and avoid duplication. For example, on our home directory, we can have config like this
log_level:
host:
port:
...

On our project dir, we can have config like this
log_level:
project:
    name:
    config:
    ...

The drawback is, we're mixing the server and client in .optimus.yaml. But, as long as we have a clear comment in .optimus.sample.yaml on which part is using on which mode, it's not an issue.
For both approach, we still need to have separate struct. Not a combined one as we currently have now.

I'm partially concluding our discussion, let me know if there's anything missing / uncovered

we can pass config explicitly if we want to run the server as @ravisuhag suggested, but still provide default location to load the config (@kushsharma concern) as well as from env param. So, server command will use config from env, explicit flag -c .theconfig.yaml, exec_binary_location, and home_root respectively
for the client commands, the config will be loaded from explicit and current_project_dir. I agree that loading config from home dir won't work nicely for organize project as @kushsharma mentioned
as @sravankorumilli mentioned, our server config is not only defined from field serve but also scheduler and log. Either we can have clear separation in .optimus.yaml or combine both, we still need 2 struct for clear separation readability as developer

@deryrahman
I would also recommend using optimus.yaml name only for client config and always use config.yaml for server config default and keeping these two files separate to draw a clear distinction.


Update android build setup

We need to update our android build setup and make sure it works with recent Android build tools and IDEs. Some recent issues suggest that this is no longer the case and people can't build our samples for Android.
I'll take a look at that.

This won't be easy. Upgrading to recent Android build tools shows a lot of problems and errors. We need to do this more regularly.

Would you like some help?  I'm happy to take a look.

Thx :) Currently assessing what required fixing. If I get stuck I'll reach out for help.

@SaschaWillems spdlog doesn't build with the latest upstream branch yes, but given that you are using submodules, you could connect your fmt submodule to v11.2 tag / 0c9fce2ffefecfdce794e1859584e25877b7b592 commit which is the latest release.
spdlog should build with it.
So my recommendation would be:-

Spdlog latest commit or tag
FmtLib at v11.2 tag as spdlog would support it.
The negative of course is that the fmt version in use at Vulkan Samples would not be upstream but that shouldn't be an issue though right?

If y'all need any help with this, am open. I have zero idea about how Vulkan works or for that matter how Android builds but this seems very interesting to me.

Thank you very much. That's very useful, updating the fmt submodule to that tag is totally fine and not problematic in anyway. With that combination, spdlog latest and fmt with tag 11.0.2 building on Android works now 👍🏻
Now on to the remaining issues with our build setup...


Are there any compiled executable Linux clients and servers available?

Not yet, this project is still in pretty active development. I'll update this ticket when they are published though!
The current plan is to use a Docker container to build the binaries which would allow us to also build them on Github Actions CI/CD without having to have a GPU attached to CI/CD.

wow, I will continue to pay attention

Bei @kevmo314 Checkout my fork https://github.com/K0IN/scuda I added buildpiplens for prebuilt servers (docker) and client binaries (see Releases) I'm a bit hesitant, to create a pr just now since I'm using earthly (pleas let me know if this is fine) and it seems to not work on my machine (I'm investigating), feel free to test and send me some feedback.
If you're not a fan of earhtly I can change the build using docker (got it in docker anyway).

Bei @kevmo314 Checkout my fork K0IN/scuda I build pipelines for prebuilt servers (docker) and client binaries (see Releases). I'm a bit hesitant, to create a pr just now since I'm using earthly (please let me know if this is fine for you) and it seems to not work on my machine (I'm investigating), feel free to test and send me some feedback.
If you're not a fan of earhtly I can change the build using docker (got it in docker anyway).

Very cool! I'd love to get that in, if we'd like to publish it to github releases it would be good to keep it as a Docker container though for the most flexibility. Feel free to open a PR even it's just a draft, we can iterate on the changes together.


ARROW-12400: [Rust] Re-enable tests in arrow::array::transform

These tests were all commented out in #9329. Given the PR made changes to the commented out code, I'm inclined to think this was an accidental omission? If not, happy for this to be closed :grinning:
FYI @jorgecarleitao
Signed-off-by: Raphael Taylor-Davies<EMAIL_ADDRESS>

Codecov Report

Merging #10048 (3d3f407) into master (26a5a04) will increase coverage by 0.24%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master   #10048      +/-   ##
==========================================
+ Coverage   78.70%   78.95%   +0.24%
==========================================
  Files         286      286
  Lines       64213    64664     +451
==========================================
+ Hits        50538    51054     +516
+ Misses      13675    13610      -65

Impacted Files
Coverage Δ

rust/arrow/src/array/transform/mod.rs
93.20% <100.00%> (+22.96%)
:arrow_up:

rust/parquet/src/encodings/encoding.rs
95.05% <0.00%> (+0.19%)
:arrow_up:

rust/arrow/src/array/equal/mod.rs
93.58% <0.00%> (+0.34%)
:arrow_up:

rust/arrow/src/array/data.rs
78.37% <0.00%> (+1.50%)
:arrow_up:

rust/arrow/src/array/array_binary.rs
89.86% <0.00%> (+3.80%)
:arrow_up:

rust/arrow/src/array/transform/variable_size.rs
100.00% <0.00%> (+12.12%)
:arrow_up:

rust/arrow/src/array/transform/primitive.rs
100.00% <0.00%> (+28.57%)
:arrow_up:

rust/arrow/src/array/transform/structure.rs
83.33% <0.00%> (+38.88%)
:arrow_up:

rust/arrow/src/array/transform/null.rs
66.66% <0.00%> (+66.66%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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

@andygrove I assume we'd like to have it in the release.

@andygrove I assume we'd like to have it in the release.

FWIW @kszucs  I don't think this is something that we should hold the release for -- it does not have any change to the actual code, only the tests.

Ok, thought that implementation was affected as well. I'm still waiting for other PRs so feel free to merge on green.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 78.95%. Comparing base (26a5a04) to head (3d3f407).

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #10048      +/-   ##
==========================================
+ Coverage   78.70%   78.95%   +0.24%
==========================================
  Files         286      286
  Lines       64213    64664     +451
==========================================
+ Hits        50538    51054     +516
+ Misses      13675    13610      -65

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix discovery page crash when secret missing label

Replace bang operator with optional chaining when checking for secret
provider type.
Issue: open-cluster-management/backlog#18148
Signed-off-by: Jakob Gray<EMAIL_ADDRESS>

/lgtm


Campaign | Posters: warning message near polling stations

When the user tries to enter a poster near a polling station #220, a warning message appears.
Pollion reference: https://github.com/pollion/sunflower-app/issues/81

The suggested 20m rule most likely does not reflect Germany-wide legislation since this determined at the Land regional level.
For example, in Berlin the limit is 30m: https://www.berlin.de/sen/uvk/mobilitaet-und-verkehr/infrastruktur/oeffentliche-beleuchtung/wahlwerbung-an-lichtmasten/
Suggestion: Instead of implementing a strict rule with such a warning, which may be too strict in many instances, we simply indicate a hover message over the polling station:
"Informieren dich, in welchem Abstand zu einem Wahllokal du Plakate vor Ort aufhängen darfst."

The suggested 20m rule most likely does not reflect Germany-wide legislation since this is determined at the Land regional level. For example, in Berlin the limit is 30m: https://www.berlin.de/sen/uvk/mobilitaet-und-verkehr/infrastruktur/oeffentliche-beleuchtung/wahlwerbung-an-lichtmasten/
Suggestion: Instead of implementing a strict rule with such a warning, which may be too strict in many instances, we simply indicate a hover message over the polling station icon:
"Informieren dich, in welchem Abstand zu einem Wahllokal du Plakate vor Ort aufhängen darfst."

Totally agree. After a short research I found distance regulations between 20m and 100m. This is regulated completely differently depending on the city, municipality and federal state. Therefore I advocate a solution using hover message that says:
"Die Wahlwerbung in unmittelbarer Umgebung zu Wahllokalen ist unzulässig. Bitte informiere dich bei deinem KV nach den örtlichen Regelungen zur Wahlwerbung."

Please move to "Ready for Development" if ok.

Concept requires further refinement (see related discussion in #274). Due to this and the priority of other features for the federal elections in 2025, polling stations are to be parked in the backlog until further notice / capacities become available.
@nscharioth fyi


Removing git artifact

This file has nothing to do here...

Coverage remained the same at 70.087% when pulling b1324e82396e8db6f5a1eebc97aecada76ba2dbc on mistercrunch:rm_art into 1fb8716231a83474ea9a0ee74041e4b0e6b6ec3a on apache:master.


fix(chat): exclude replay attachments for publish

Description:

Add filter option for getAttachments selector
Filter attachments for publication request to not include replay files

Issues:

Issue #1860

Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review

/deploy-review


No device

I have this problem: the integration is there, but it doesn't let me see the 3 conditioners I have (now I use HASSIO, on the old docker installation I see them correctly..)

Hey, I think you used another integration on your old installation 🤔
Unfortunately we don't support air conditions so far, if you send me the pyhon data, I can add the support.

We have now better support for air conditioner, please try the latest beta.


Couldn't import file

I have problems with the teapot model.

ImportFBX Errors:
Couldn't import file         > /Users/solkar/Developer/Samples/Unity/_keijiro.github.io/Klak/Assets/Test/Teapot.fbx.
File is corrupted (or invalid)

I can't reproduce this. Which version of Unity are you using?

v5.1.4
On Mon, Jan 11, 2016 at 4:53 PM, Keijiro Takahashi<EMAIL_ADDRESS>
wrote:

I can't reproduce this. Which version of Unity are you using?
—
Reply to this email directly or view it on GitHub
https://github.com/keijiro/Klak/issues/1#issuecomment-170577550.

Okay. I'll check it later.
P.S. I'm using 5.2.4

Bingo. That's because Unity 5.1 doesn't support FBX2016. I re-exported the model with FBX2014.
1c66c467e6eeabfeeec08c51f0a79b42b893491e

Awesome!
Just curious, how do you know which formats are supported? Is there any reference doc for that?

On 12 Jan 2016, at 14:24, Keijiro Takahashi<EMAIL_ADDRESS>wrote:
Bingo. That's because Unity 5.1 doesn't support FBX2016. I re-exported the model with FBX2014.
1c66c46
—
Reply to this email directly or view it on GitHub.

I saw a note in the changelog that said FBX2016 issue was solved. I'm not sure if there is a doc about it.

Neither do I 😁
One chili to bind them into hotness

On 12 Jan 2016, at 14:47, Keijiro Takahashi<EMAIL_ADDRESS>wrote:
I saw a note in the changelog that said FBX2016 issue was solved. I'm not sure if there is a doc about it.
—
Reply to this email directly or view it on GitHub.


adding temporary file for building to sif from squashfs or ext3

Hey @yhcote, I think this should be working now.  It passes all of the build tests, but it doesn't pass the python function tests.  However, I suspect there is currently something the matter with them from the shub end.

Cool thanks !


Try using ServiceExt::oneshot in tower_batch::Worker

This issue was obsoleted by the fixes to the underlying issue in tower::Buffer, see #1593 for details.
Is your feature request related to a problem? Please describe.
tower-batch::Worker uses the ready_and().await?.call() pattern, but we prefer the ServiceExt::oneshot pattern.
Describe the solution you'd like
We should see if we can use the ServiceExt::oneshot pattern, to prevent future poll_ready/call mismatches:

[ ] Worker::process_req - https://github.com/ZcashFoundation/zebra/blob/main/tower-batch/src/worker.rs#L74
[ ] Worker::flush_service - https://github.com/ZcashFoundation/zebra/blob/main/tower-batch/src/worker.rs#L96
[ ] Document the poll_ready/call invariants

See #1593 for details.
Describe alternatives you've considered
Do nothing: the code might hang if future changes break the poll_ready/call invariants.
Additional context
This issue was discovered during the review in #1593. It is a routine cleanup.

This issue was obsoleted by the fixes to the underlying issue in tower::Buffer, see #1593 for details.


add jetson compile doc.

add compile guide for paddle inference on jetson

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

需要可视化确认一下正确性。

需要可视化确认一下正确性。


this bot doesn't even work btw

this bot isn't online in their discord server, and it also doesn't even check if usernames are available.

All this bot does is spit out an error.
"This interaction failed
Only you can see this • Dismiss message"

happy @nickfullstack?


[SMALLFIX] Changed the signature of 'usedInSecurityContextTest' in 'UserTest'

The usedInSecurityContextTest in the UserTest doesn't throw an Exception. Removed it from the signature of the method.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/7387/
Test PASSed.

Thanks for the improvement! LGTM.


Receiver: Logically split router and ingestor mode

PR closes #5643

[x] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

In the runReceive method, I have added two separate calls to ingestion and router mode, if the receiver has to run in ingestion mode then the call to ingestionMode is made and if it is to be run in router mode then the call to routerMode is made.
Even though both the modes are present in the same file, they can now be treated as separate components.
Verification

E2E and unit tests are passing.

@matej-g could someone from team please review this PR? :)

What's the goal here? Refactor for readability or anything else? (Please state in description)

What's the goal here? Refactor for readability or anything else? (Please state in description)

@bwplotka I have added the description in the PR, thanks for the review comment :smile:

@matej-g It's alright, please take your time, no hurries :smile:


feat: add missing Metrics.ClientConfig to configmap

Adds configurable, optional ExcludeTags and Prefix to the managed ConfigMap to allow metrics exposed by temporal to be excluded/prefixed

Can't quite tell what's up with that e2e test - as far as i can tell from the logs it seems like it's successful

Thanks @ed-marks ! 👍


Rename Paragraph long and short and consider wether this is component props at all

Today we have Paragraph, Paragraph variant="short" and Paragraph variant="long".
This means our consumers can make any Paragraph component short or long.
I understand we need short and long in context of i.e. text inside a Card, but I'm unsure wether we want Paragraph component aka. body text to be varying in line height, breaking the typographic flow.
I suggest we make a distinction between what is a text style and what is a typography component.
Also, variant="long" and variant="short" is a bit confusing for me - may be personal opinion, but could density="compact" and density="loose" better? ☺

replaced by 2503


Client Disconnected without Exception on localhost UDP

After debugging for a while i finally found the reason my client crashed:
Because I used connection.sendUDP() on my server, while working on localhost.
This resulted in a client connection lost with no exceptions appearing from kryonet,
so I had to debug every step until I found this. (The server just said client disconnected).
Now I know you cant send UDP to localhost, but maybe throwing an exception in KryoNet would be nice.

There's no problem sending UDP to localhost. See PingPongTest and others.

Hmmm, sending from my server with udp to my clients doesnt work. Maybe I have a wrong UDP port, that doesnt work on localhost.

I noticed only the server cant send via UDP to the client (both on localhost). The clients sendUDP to the server works. But it still crashes if the server tries to send UDP. (with TCP it doesnt happen).


Public get text action

Fixes #452
Checklist

[x] I have added tests
[x] I have updated the docs and cheatsheet
[x] I have not broken the cheatsheet

we should prob have api test for this, no?

Extension side we actually have multiple tests for this already
eg
https://github.com/cursorless-dev/cursorless/blob/a723b253c61106dfc7e32638e2d20b53292d17a0/packages/cursorless-vscode-e2e/src/suite/fixtures/recorded/actions/findVest.yml

Yes but I mean the talon-side api introduced by this PR. We have tests for our other talon-side APIs

I'm not in love with the argument silent. It's much less descriptive than no_decorations.

I'm not in love with the argument silent. It's much less descriptive than no_decorations.

I agree. But I also really don't like double negatives (ie no_decorations = False). Any better ideas? Chatgpt suggests

omit_decorations
hide_decorations
suppress_decorations

cc/ @josharian

I'm not in love with the argument silent. It's much less descriptive than no_decorations.

I agree. But I also really don't like double negatives (ie no_decorations = False). Any better ideas? Chatgpt suggests
* `omit_decorations`

* `hide_decorations`

* `suppress_decorations`

cc/ @josharian

hide_decorations sounds reasonable

Ok made some final tweaks and confirmed talon tests work locally. I'll give you a chance for a quick look in case I did anything dumb; merge if happy


Implement Default trait for StateDiff

Replace the StateDiff empty method by implementing the Default trait for it.
Also, replace every invocation of StateDiff::empty with a call to default().

Imma take this one !


Support for GitHub Enterprise Server

Please add support for GitHub Enterprise Server. This is mainly for generating the correct URLs in githubUserToUrl(). I'll submit a PR for consideration.

Sounds like a great addition! I think we could probably add a configuration option or maybe figure out some way to look in the .git directory

I had thought about trolling the .git/config for remotes but unless the URL is one of "github.com", "gitlab.com", or "bitbucket.org" there's no way I can tell if the remote is running GitHub Enterprise Server or Gitlab self-managed or Bitbucket Datacenter or Gogs/Gitea/whatever. While CODEOWNERS can use email addresses, when it comes to username and team names, there are syntax similarities between GitHub and Gitlab, such as "@username" but team name syntax does differ between GitHub, Gitlab, and Bitbucket.
The approach I've taken is to query the vscode workspace for the github-enterprise.uri setting from the GitHub Enterprise Server Authentication Provider extension which is baked in to VSCode (nothing else to install so no missing dependencies to worry about.) GitHub's official extensions (at least "Pull Requests and Issues" and "Actions") rely on that for working with GHES. So far, everything is working a treat.

If you want to make a PR, I can merge it

Fixed in #23


Parameter is missing for class constructor for boolean properties

Input class:
class SomeInput
{
    public function __construct(
        #[Field(inputType: 'Boolean!')]
        public readonly bool $x,

        #[Field(inputType: 'Boolean!')]
        public readonly bool $y,
    ) {
    }
}

Mutation:
mutation {
  updateSomething(someInput:
    {
      x: false
      y: false
    }
  )
}

Result:
"Parameter 'x' is missing for class 'SomeInput' constructor. It should be mapped as required field."

If I change type to any other (e.g. string) - it works. If I pass true instead of false as x or y argument - it also works.
Looks like problem occurs for boolean fields with false values.

@ozahorulia yea, this is very likely.  Are you using master?  Also, what's your Type annotation look like?  There have been some recent improvements for Input types with a new "update" option.

The project is in production, so not master, bust last available version (5.0.2).
My Type class looks like this:
#[Type(class: SomeClass::class)]
#[SourceField(name: 'x')]
#[SourceField(name: 'y')]
class SomeClass
{
}

And the referenced SomeClass itself of course has getX(): bool and getY(): bool methods.

That's understandable @ozahorulia.  We should have a new update released soon, 6.0.  You'll likely need to wait until that happens before this issue is resolved.  However, in the meantime, you might test master to see if it resolves your issue, so that we can proceed towards a PR, otherwise.
As you can see in the docs here there is a new update option for Input type annotations.  This denotes the Input as an update action, and alters the behavior of nullable fields.  I suspect that false would be evaluated properly under an "update" Input type.

As for Type annotation - I have no problems with that, it works just as expected. It's separated from the referenced class just in order to separate models, so it doesn't change anything in case of this issue.
I just tried #[Input(update: true)] option, as it exists in 5.0.2. Unfortunately it does not change anything for me. But it's very clear that the problem appears only if properties are promoted in the constructor.
If I declare it like this, everything works perfectly:
#[Input]
class SomeInput
{
    #[Field(inputType: 'Boolean!')]
    public bool $x,

    #[Field(inputType: 'Boolean!')]
    public readonly bool $y,
}

For me it looks pretty similar to #410. Is it possible to merge #411 and tag it as 5.0.3 or something?

@ozahorulia happy to get that merged in.  We need to get at least one test written for that though.  Could you help us out and push a test on the author's branch?


[SPIKE/RESEARCH]  Azure Functions and Azure Service Bus

Acceptance Criteria:
Document possible options and selection reasons for a particular library in this GitHub issue via a Summary comment.
Find a Python library that supports Synchronous implementation for Azure functions and Azure Service Bus  if the official library does not support it.
Ensure that connection is set up and working.

Started working on the Azure service bus, installed the package
- pip install azure-servicebus
- pip install azure-identity
Running the sample sync code version

Tried out few examples in service bus and azure functions, captured few in nation page
Notion page link:
Service Bus: https://www.notion.so/astronomerio/Azure-Service-Bus-130e1721f68f4526b20d081798dd66da
Azure Functions: https://www.notion.so/astronomerio/Azure-Functions-f249d866785b43fdb5610c25088e3e1e

Updated the list service bus Async operators in the notion page
https://www.notion.so/astronomerio/Azure-Service-Bus-130e1721f68f4526b20d081798dd66da

@bharanidharan14 please close this in case your research is done.


如何使用rancher 部署helm应用到所有下游集群中，并且下游集群指定values来覆盖values.yaml的内容

Description
kubenetes 1.24.1
rancher version 2.7.1
Rancher uses helm offline deployment
Here are my helm parameters

Using GitOps multi-cluster delivery, the number of copies of the application deployed to the downstream cluster and custom values cannot be specified when deploying the application

How does this relate to a Helm Dashboard UI project? Our project is about building UI for Helm, not generic Helm support.
If your question is not about Dashboard UI, please ask it at the more relevant forum. If it is about Dashboard, please clarify the problem.


Update text or reference to aims of the Solid Gitter channels

The Solid Code of Conduct links to https://github.com/solid/information#connect with "defined aims of the Solid gitter channels" but the URL moved (redirects) to solid-archive repo and I can't find anything pertaining to "connect" in the README after checking the commit log. There is https://github.com/solid/process/blob/main/gitter-chat-overview.md (with outdated content) .. but I'm not sure if that's intended to be the "defined aims" after content getting reshuffled.
I think the Solid CoC need not be overly specific to Gitter (at the top of the document) and needs to be applied uniformly in the Solid community irrespective to the channels/services/applications that are being used.

Link fix is proposed in above mentioned PR.
The 'uniform application of CoC' is addressed in this issue: https://github.com/solid/deit/issues/13 (can be continued there)

Ups. I closed my PR because the previous work on this pr: https://github.com/solid/process/pull/275 solved the link and much more.

We removed this reference in the latest version of CoC. Can this usse be closed?


PEP8 format

changed variable "filenames" to "file_names" to remain consistent with existing PEP8 under_score conventions

@isaidcode Thanks!


sqlite api to create a db

I noticed that there is an api/interface to open an existing db, but is there an api to create a db that is mostly used to create and seed a db?

You mean like migrations?

yes, and I just noticed that despite method being named open it still can create dbs

https://github.com/kriasoft/node-sqlite#migrations ?


Bug: fetchEvents never returns if one of the explicit relays is unreachable

Is there a way to pass a timeout for fetchEvents?

Is this why my fetchEvents never returns....?

I think so. I switched to using subscribe instead (which is a lot better anyway)

I have the same problem

when I use:
const filter = {     kinds: [10015],     "#t": ["artists"],     since:<PHONE_NUMBER>,     limit: 2,   };
my fetchEvents never returns?

Hey, this issue is very anoying and difficult to fix.
How we can process a series of fetchEvents to different relays, and not throw an error if an Relay is unreachable


Refactor error responses

Refactor error responses to avoid OpenAPI generator creating multiple models for each error response

Hello,
thank you for the suggestion but I'd like to point out here that it's true that we should avoid having duplicated lines but in this case if we refactor to use model error also for error codes, the problem is that we loose control over conceptually valid errors for each case. With the refactored code, by API definition it will be valid if you use for example UNAVAILABLE or TIMEOUT as "403" error where it only can be an "PERMISSION_DENIED" or any other specific error specially defiend for it (for example NUMBER_VERIFICATION.USER_NOT_AUTHENTICATED_BY_IP). Here is a screenshot of the suggested version:

I think the current version is more suitable and avoids false validations.

closing - discussion handled inside commonalities WG. @ChinthakaJay please open new issue inside Commonalities WG Commonalities


fix(typescript): Stop using csstype for CSS properties

Closes #245
It was breaking some components. Since those properties weren't picked by pickCSSProps they wouldn't be rendered anyway.

Codecov Report

Merging #246 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #246   +/-   ##
=======================================
  Coverage   70.25%   70.25%
=======================================
  Files          96       96
  Lines         659      659
  Branches      132      132
=======================================
  Hits          463      463
  Misses        163      163
  Partials       33       33

Impacted Files
Coverage Δ

packages/reakit/src/_utils/getComponentName.ts
100% <ø> (ø)
: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 e9ca767...e948813. Read the comment docs.


Integration Test - Release - 2019/06/17 23:04:26

Auto create for integration test. AnotherAuthorUpdatedArticleFlow

@PRMergerTest2 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


IGAPP- 3: Adjust workflows and deliveries

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword IGAPP.

The PR is quite big (once again). Nearly half of the changes are probably from the config.yml, which could be ignored though because its autogenerated. Anyway, I totally understand if it is not possible to review it. Thend I'd just merge it. Deliveries itself have not been tested yet, will be done in a separate PR.


feat(docs): add --check flag to format docs

Let me know if there is anywhere else this info should be added

Hello, is there any update on this? @Dev-Connections


chore: mark AREnableAuctionImprovementsSignals feature flag as ready for release

This PR resolves []
Description
This PR marks the feature flag AREnableAuctionImprovementsSignals as readyForRelease

PR Checklist

[ ] I have tested my changes on iOS and Android.
[ ] I hid my changes behind a feature flag, or they don't need one.
[ ] I have included screenshots or videos, or I have not changed the UI.
[ ] I have added tests, or my changes don't require any.
[ ] I added an app state migration, or my changes do not require one.
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

mark AREnableAuctionImprovementsSignals as ready for release - mrsltun

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (mark AREnableAuctionImprovementsSignals as ready for release - mrsltun)

  Generated by :no_entry_sign: dangerJS against 4a9772ff009f091585d17b4f2393c2bd22766410


aws-device-farm-runner 0.0.5

New Pull Request Checklist
Please mark the points which you did / accept.

[x] I read the Step Development Guideline
[x] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[x] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[x] I read and accept the Abandoned Step policy

0.0.5 (2017 Jun 20)

Incorporate patch from andreschab90: add opportunity for metered/unmetered BillingMethod
Make boolean options into drop-downs in step editor
Add error message with hint about test_package_name
point users to wiki for setup instructions
fix up formatting of input descriptions

making last-minute doc tweaks

updated PR at https://github.com/bitrise-io/bitrise-steplib/pull/1071