kubernetes-polaris: 9.5.0 -> 9.6.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/FairwindsOps/polaris/releases.
meta.description for kubernetes-polaris is: Validate and remediate Kubernetes resources to ensure configuration best practices are followed
meta.homepage for kubernetes-polaris is: https://www.fairwinds.com/polaris
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.6.0 with grep in /nix/store/2brgfg99ly5bf2zflkqqscff7xgmpsy5-kubernetes-polaris-9.6.0
found 9.6.0 in filename of file in /nix/store/2brgfg99ly5bf2zflkqqscff7xgmpsy5-kubernetes-polaris-9.6.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

kubernetes-polaris

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2brgfg99ly5bf2zflkqqscff7xgmpsy5-kubernetes-polaris-9.6.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A kubernetes-polaris https://github.com/r-ryantm/nixpkgs/archive/5c21bdb944e776bb8235faa00e556c497cd02de8.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5c21bdb944e776bb8235faa00e556c497cd02de8#kubernetes-polaris

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2brgfg99ly5bf2zflkqqscff7xgmpsy5-kubernetes-polaris-9.6.0
ls -la /nix/store/2brgfg99ly5bf2zflkqqscff7xgmpsy5-kubernetes-polaris-9.6.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

kubernetes-polaris

Maintainer pings
cc @LongerHV for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 360873

aarch64-darwin

:white_check_mark: 1 package built:

kubernetes-polaris


Make Codeartifact optional

At this point, when we deploy a seedkit using codeseeder, it deploys AWS Codeartifact domain and AWS Codeartifact Repository by default. This default behavior of creating  AWS Codeartifact will cause an issue in the regions where it is not supported. AWS Codeartifact should be created optionally

PR #6 fixes it.


feat(mlx-lm): add openAI like api server

Add basic OpenAI API like API server, with very basic implementation that only supports temperature,top_p, stop words, and streaming.
Integration with chat UI:
https://github.com/ml-explore/mlx-examples/assets/7523197/f36d043c-dd3d-4361-af95-5b3ce654db1c
Related issue: https://github.com/ml-explore/mlx-examples/issues/368
Draft API Spec
API Endpoint: /v1/chat/completions
Method: POST
Request Headers

Content-Type: Must be application/json.

Request Body (JSON)

messages: An array of message objects representing the conversation history. Each message object should have a role (e.g., user, assistant) and content (the message text).
role_mapping: (Optional) A dictionary to customize the role prefixes in the generated prompt. If not provided, default mappings are used.
stop: (Optional) An array of strings or a single string representing stopping conditions for the generation. These are sequences of tokens where the generation should stop.
max_tokens: (Optional) An integer specifying the maximum number of tokens to generate. Defaults to 100.
stream: (Optional) A boolean indicating if the response should be streamed. If true, responses are sent as they are generated. Defaults to false.
model: (Optional) A string specifying the model to use for generation. This is not utilized in the provided code but could be used for selecting among multiple models.
temperature: (Optional) A float specifying the sampling temperature. Defaults to 1.0.
top_p: (Optional) A float specifying the nucleus sampling parameter. Defaults to 1.0.

Launching the Server
To launch the server with a specific model, use the following command:
python -m mlx_lm.server --model <path_to_the_model_or_hf_model_id> --adapter-file <path_to_adapter_file>

--model: Required. The path to the MLX model weights, tokenizer, and config or a Hugging Face model identifier.
--adapter-file: Optional. The path to the trained adapter weights file.
--host: Optional. Host for the HTTP server. Defaults to <IP_ADDRESS>.
--port: Optional. Port for the HTTP server. Defaults to 8080.

@awni Currently, I am not taking any external dependency, so making it feature-rich may be challenging. Please let me know what you think.

Wowww! Super cool.

Currently, I am not taking any external dependency, so making it feature-rich may be challenging.

What kind of features are you thinking that would be hard to add?
Also I'm not morally opposed to dependencies in this example specifically, especially if they are well known, easy to install packages, pretty useful.

Wowww! Super cool.

Currently, I am not taking any external dependency, so making it feature-rich may be challenging.

What kind of features are you thinking that would be hard to add?
Also I'm not morally opposed to dependencies in this example specifically, especially if they are well known, easy to install packages, pretty useful.

It is more related to the features of the HTTP service. The built-in HttpService may not be as robust or feature-rich as some frameworks like FastAPI and Flask. However, it depends on what we want to offer in mlx-lm. If it is only for development and testing purposes, I believe it should be sufficient.

@mzbac Very excellent work positive efficient speed. I had a similar idea but the difference is that I haven't started it yet, thank you again.
@mzbac @awni The discussion above mentioned whether this commit will affect the simplicity of the mlx_lm model and whether it is appropriate to put it in this model, and whether it is possible to introduce some other third-party dependency libraries. The following are just our personal thoughts and are for reference only:
Is it possible to plan the above server functionality into a new python module, e.g. named mlx_server, with the mlx_server model relying on the mlx_lm module at the bottom. This way, you don't have to worry about mlx_lm getting more and more complex and functional, and at the same time, mlx_server can also be assured of introducing and using some better-performing third-party libraries.
In addition to this, Whisper could also take a generic approach and publish a module for mlx_whisper, which would also add the v1/audio/transcriptions service capability to the server module.
Here are some preliminary ideas from our side, as mentioned in https://github.com/ml-explore/mlx/discussions/654, there are already a lot of mlx-based projects and demos in the community, but I would suggest that we need to provide the basic layer of functionality, so that on one hand, we can ensure the quality of the library, and on the other hand, developers can more quickly develop some upper layer applications. This will ensure the quality of the library on the one hand, and allow developers to develop some upper layer applications more quickly on the other. Thanks to the mlx_server module, some existing projects can be quickly migrated to mlx.
Below is the ecological framework envisioned for what mlx could do next, depending of course on whether this goes against the starting point of the project itself.

@awni, this is ready for review. The server supports temperature, top_p, stop words, and streaming - these are commonly used features in the OpenAI-like API. Let me know if this is enough for the first cut or if we would like to go with @madroidmaq's proposed approach so that I can start adding some documentation on the API specifications.

Great job @mzbac this can help to leverage mlx with a ton of chat UI out there! Love the suggestion of @madroidmaq
+1 for FastAPI

@mzbac I would say this is definitely enough to start with. Looks great! I will plan to review it in the next 1-2 days.

Testing chat-ui integration using the setup from the repo: https://github.com/mzbac/LLM_web_apple_silicon.
Replace the "launch llama.cpp" part with:
python -m mlx_lm.server --model mlx-community/Mixtral-8x7B-Instruct-v0.1-hf-4bit-mlx

Is it feasible to maintain the loaded weights as a "keep_alive" option like in Ollama to facilitate quicker subsequent queries?

Is it feasible to maintain the loaded weights as a "keep_alive" option like in Ollama to facilitate quicker subsequent queries?

Not sure if I understand the question correctly, but currently the model is loaded during server launch and cached there for all requests. If you want to switch the model, you have to restart the server as there is no model switching in runtime.

hi @mzbac, Apologies for any confusion. I am referring to a feature e available on Ollama in the image below; however, you mentioned we currently have this capability. Thanks a lot for initiating this effort. I will take a look to see how we can improve it further

@mzbac anything we need to do before merging this? I think the code looks good and it's pretty self-contained so I think it's an easy addition.

@awni, I am currently working on refactoring the code. Maybe we could wait until tomorrow as it will fix some issues related to streaming stopping_criteria.

Ok great, let me know when you are ready and I can check / merge!

@awni, I have finished refactoring the PR. It primarily addresses two things:

Removing the tokens list from the generate function to make it more consistent with how we generate tokens in generate.py and reduce memory usage for the server.
Buffering up to the maximum length of stop word ids sequence in streaming mode to prevent sending back stop words to the client.

I have also tested unicode emojis and Chinese words with chat-ui integration on my local machine, and everything seems to be working well.
Please let me know if there is anything else I have missed.

Great work on starting this off!!
A really nice add would be to have continuous batching of incoming requests (run in parallel). Would that take a lot?

Great work on starting this off!!
A really nice add would be to have continuous batching of incoming requests (run in parallel). Would that take a lot?

Yeah, this API server is meant for local development and testing. so, adding continuous batching may not be the best fit for the mlx-lm package. However, it should be something that the mlx community would be able to build on top of the mlx.

Thanks, are parallel requests supported? Ronan
On Fri, Feb 16, 2024 at 1:38 PM Anchen @.***> wrote:

Great work on starting this off!!
A really nice add would be to have continuous batching of incoming
requests (run in parallel). Would that take a lot?
Yeah, this API server is meant for local development and testing. so,
adding continuous batching may not be the best fit for the mlx-lm package.
However, it should be something that the mlx community would be able to
build on top of the mlx.
—
Reply to this email directly, view it on GitHub
https://github.com/ml-explore/mlx-examples/pull/429#issuecomment-1948400863,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASVG6CXMG4H5K26R57ZHYPLYT5OMBAVCNFSM6AAAAABDCYSSA6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBYGQYDAOBWGM
.
You are receiving this because you commented.Message ID:
@.***>

Thanks, are parallel requests supported? Ronan
…
On Fri, Feb 16, 2024 at 1:38 PM Anchen @.> wrote: Great work on starting this off!! A really nice add would be to have continuous batching of incoming requests (run in parallel). Would that take a lot? Yeah, this API server is meant for local development and testing. so, adding continuous batching may not be the best fit for the mlx-lm package. However, it should be something that the mlx community would be able to build on top of the mlx. — Reply to this email directly, view it on GitHub <#429 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASVG6CXMG4H5K26R57ZHYPLYT5OMBAVCNFSM6AAAAABDCYSSA6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBYGQYDAOBWGM . You are receiving this because you commented.Message ID: @.>

Not in this PR, it's too complicated to be part of the mlx-lm package.


Adding Signature - Jack Sharkey

Would love to add my signature to the list!
Cheers,
Jack Sharkey
Edited: PR link - #942

Thanks!


Remove duplicate logic

Codecov Report

Merging #60 (90eaefa) into master (5e941d1) will increase coverage by 0.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #60      +/-   ##
==========================================
+ Coverage   95.38%   95.52%   +0.13%
==========================================
  Files           7        7
  Lines         628      625       -3
==========================================
- Hits          599      597       -2
+ Misses         29       28       -1

Impacted Files
Coverage Δ

lib/parser.js
95.97% <ø> (+0.20%)
: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 5e941d1...90eaefa. Read the comment docs.


Fixed some Typo's in example sketch

DS3231_set.pde was using the word day and the word date where it should have always been the word date. It was not setting the day at all, but leaving it at zero. This has been fixed.
Also re-named variables to follow proper case convention in the same sketch.
Set all Serial.begin statements to initiate at 57600. Some examples wre starting at 57600 and others at 9600. Now they are consistent.
And in reference to your comment in DS3231.cpp where you mention the fact that if someone does a setClockMode at the right millisecond, it will set the clock back by an hour ... here is a proposed solution, which I know is not perfect, but I only wrote it to illustrate one possible way of dealing with that scenario:
This would go towards the top of the setClockMode method.
bool h12Flag = false;
bool pmFlag = false;
byte h = getHour(h12Flag,pmFlag);
byte m = getMinute();
byte s = getSecond();
int diff = 59 - s;
if (h == 11 || h == 23) {
    if (m == 59) {
        if (diff <= 3) {
            delay(3500);
        }
    }
}

All it does is check to see if the clock is close to that moment, then if it is, it simply waits to make sure that moment has passed before issuing the setting.

Many thanks and my apologies for the delay in merging your improvements!
Thanks for the suggested solution for the just-before-roll-over issue; let's keep it in mind.


Adapted and fixed some issues for ansible 2.0

Is tested in Ansible 2.0.1 and works as expected. Testing in another environment would be great.

Thanks for your pull request @madonius!


Please update NVIDIA TensorRT Inference Server document for kustomize

Please update NVIDIA TensorRT Inference Server document for kustomize. Still the document uses ksonnet.
Thanks.

This is a duplicate of https://github.com/kubeflow/website/issues/959
/close

@sarahmaddox, Is anyone really working on #959 to update the document?
Thanks.


Touch offset is too great

Tap on Smith chart produces dot that is a little to high up

Fixed with #17


[$1000] Blue bottom border seperator among currencies is not pressent.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open “Actions”
Open “Request money”
Click “Select a Currency”.
Observe there is no separator among currencies.
Open “Settings”
Open “Profile”
Open “Pronouns”.
Open “Settings”
Open “Profile”
Open “Timezone”.

Expected Result:
Separator among currencies should be present like Pronouns or Timezone.
Actual Result:
Seperator among currencies is not pressent like Pronouns or Timezone.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/2133e63d-74bb-4b70-b9c1-93f9eeacff72

Expensify/Expensify Issue URL:
Issue reported by: @usmantariq96
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1684006680335189
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0142b4e1af1a58a18d
Upwork Job ID:<PHONE_NUMBER>115326464
Last Price Increase: 2023-05-16

Offers sent in upwork @dhairyasenjaliya @s77rt @usmantariq96

Offer accepted
Thanks

Hi @s77rt please complete the steps above and I'll get this paid out next week assuming no regressions!

The PR that introduced the bug has been identified: No PR to blame. The currency page  was implemented on May 2021 (PR) and at that time we didn't even have the option to add a separator. The separator feature was added later on Nov 2022 (PR).
The offending PR has been commented on: n/a
A discussion in #expensify-bugs has been started: Not a bug. This is a feature request.
Determine if we should create a regression test for this bug: No

@kevinksullivan Done!

Thanks for the quick turnaround @s77rt !

Paid everyone. @usmantariq96 I paid you for reporting, but upwork is bugging again and I can't close the contract. I'll try again tomorrow to wrap this up.

All set @usmantariq96


Turn on GCC conversion warnings

-Wconversion

special cases in test/CMakeLists.txt
special cases in source files (e,g, #pragma warning)


nix: add Security to build inputs.

For some reason, this is required to build nix on Big Sur, even though it's not needed on earlier macOS versions.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This should also be added on the Nix repo:
https://github.com/NixOS/nix/blob/480426a364f09e7992230b32f2941a09fb52d729/flake.nix#L83


Add option to modify number of assets to load first

Hi,
Thank you for your useful library.
I have a little issue with this current setup, on my android device which is running expo go, it takes more than 6 seconds to wait function loadAssets() finished. It's a little bit too long.
I tried to test the first option. If I change the the first param to 60, it only took less than 2 seconds.
Thank you.
const getAssets = () => {
	try {
	    if (availableOptions.hasNextPage) {
		const params: AssetsOptions = {
		    first: 200, // => could you add option to modify this?
		    mediaType: assetsType,
		    sortBy: ['creationTime'],
		}
		if (availableOptions.after)
		    params.after = availableOptions.after
		if (!availableOptions.hasNextPage) return

		return permissions.hasMediaLibraryPermission
		    ? loadAssets(params)
		    : getMediaLibraryPermission()
	    }
	} catch (err) {
	    // need to add component that display where there is an error
	    // show it when any error happen and wrap any place that can have
	    // err with try and catch block
	}
}

yes

add on version 1.4.1
https://www.npmjs.com/package/expo-images-picker


dma: Allow for driver implemented channel pooling

DMA channels can be viewed as a pool of resources in some instances. When using struct dma_context the default channel request/release use an atomic bit flag to indicate channel availability and this works well in most cases.
In some cases however, when channel counts are low and peripheral counts high it might be beneficial to allow for thread pends to occur on channel requests on a mutex or semaphore.
Related to #61444

@pbalsundar


Added a TUD/SymPy CZI position.

Hi Jason, thanks for the job post!  The indentation in the yaml isn't quite right (text should be offset in the description section.  Also, the post is very long—you can take a look at the current posts for a rough idea of length and how that renders—would you be able to shorten it a bit?
Thanks!

I will fix the indentation. I can shorten it, but this is the approve job text from my university. I'd rather keep it as is.

I think I see why you ask about the length. Is ti because the entirety of the post displays on the front page?

Ok, I see how others linked to the full posts. I have indented and shortened.

Sorry, @moorepants, this got lost somewhere in all my notifications. Merging now.

Post is on the board with permalink https://jobs.numfocus.org/job/2022-02-04_sympy

Thanks!


Extract the CDN host configuration from the vizjson

Right now we are using the default one, which works in production, but we need to use the one specified in the the vizjson so it works locally and in staging.

@CartoDB/frontend / @javisantana: would you mind having a look, please?

@CartoDB/frontend: would you mind having a look, please?

we use the cdb_url is set in the layergroup call, we never use viz.json one. Why we decided to do this?

Because it wasn't working and I thought I had to explicitly set it using the one coming from the viz.json.

I'm creating a ticket to fix this.


The date parser enrichment is not supported

Keen has a pretty awesome date parser enrichment described here: https://keen.io/docs/api/#datetime-parser
However, when adding that configuration to the event body sent through Segment it seems to get stripped out by the time it reaches Keen. Can we add support for this by not overwriting the keen property in the body?

Hi @stringbeans, as part of the monorepo migration, this issue has been moved to new issue. Our engineers have been notified and will prioritize and work on it ASAP. Thank you!
For more information, see README.md.


Nodes and edges not rendering correctly when generated dynamically.

Hello, thanks for this great package.
Just a little query though. The package works great when the nodes and edges are created statically, but the edges are created one over another when the nodes and edges are created inside a for loop. Maybe I am missing something, can you please demonstrate how to create the nodes and edges dynamically and update the documentation.  Will be of so much help. Thanks.

Hi, which algorithm are you using?

Hi, which algorithm are you using?

I am using the BuchheimWalkerAlgorithm algorithm with TreeEdgeRenderer.

@DroidSU did u fix the issue?

@DroidSU did u fix the issue?

No Sir not yet.


Windows: Installer does not kill daemon process

The Issue
When on 0.21.2 and running the 0.21.2 installer while LBRY is running, the installer tries to shutdown the lbrynet-daemon.exe process. Since two processes are spawn during app launch, the installer is able to kill the first, but not the 2nd because it's a child of a child. This becomes a concern during updates when we upgrade the daemon version because the user will have to kill the current daemon after app install and then re-install the app again so the new daemon is written into the file system.
Startup process (per Igor):
App => Daemon process 1 => Daemon process 2
Steps to reproduce

Run LBRY 0.21.2
Launch 0.21.2 installer process
Notice that the daemon continues running and app restarts using that daemon process

Expected behaviour
Installer should kill all daemon processes
Actual behaviour
Daemon continues running
System Configuration

LBRY Daemon version: 0.19.1
LBRY App version: 0.21.2
LBRY Installation ID:
Operating system: Windows

Anything Else

Screenshots

We should look into this before the redesign release, especially if we will be updating the daemon along with it.
I'll try this on Mac to see if it's happening there.

The solution has to be implemented on the daemon. The daemon has to kill its children process if it's being exited.

We are working with the daemon team to see if they can get the daemon to run as a single process. If this is the case, we can update the predesign version to the latest daemon.
The upgrade procedure would be:

Don't autoupgrade - close LBRY completely and download latest installer from lbry.io/get
Run installer manually

or (most will opt for this because they will see the message)

Run autoupdate
App restarts to incompatible daemon screen which allows them to quit daemon and shows them https://lbry.io/faq/incompatible-protocol-version which walks them through making sure the daemon is killed, downloading installer and re-running

Did a little more digging - went back to 0.21.2 to perform in-app upgrades and it looks like we have a different issue. When upgrading in app, you get 2 prompts to run the installer, one after another. If you wait for a few seconds after the first to click proceed on the 2nd, then you end up in a situation where LBRY is killed but the daemon is left running. Still not sure why there are 2 UAC prompts, but one  is run with --updated --force-run parameter and then a second time with --updated /S. I'll open a separate issue for this.
This issue (daemon not getting closed) is still valid, but it only affects manual installation while LBRY is running and not the in-app upgrade process.

Opened https://github.com/electron-userland/electron-builder/issues/2894


ENONET  Error

Receive error:
lmauldin@9c68fd81e7d7:/var/www/html/pmtool/erp-extender/pms420$ ./node_modules/.bin/gulp less
[15:24:43] Using gulpfile /var/www/html/pmtool/erp-extender/pms420/gulpfile.js
[15:24:43] Starting 'less'...
Potentially unhandled rejection [2] Error: ENOENT, open '<input css 1>'
    at Error (native)

Relevant gulp file:
gulp.task("less", function() {
    var cleancss = new lessPluginCleanCSS({ advanced: true });
   var autoprefix= new lessPluginAutoPrefix({browsers: ["last 2 versions"]});
    //return gulp.src(['./assets/styles/application.less', './assets/styles/*/*.less'])
    return gulp.src(['./assets/styles/application.less'])
        .pipe(sourcemaps.init())
        .pipe(less({
            plugins: [autoprefix]
        }))
        .pipe(sourcemaps.write()) //.pipe(sourcemaps.write('./maps'))
        .pipe(gulp.dest('./webroot/styles'));
});

It looks like the same issue as in https://github.com/less/less-plugin-clean-css/issues/8, though I have no idea of it could be too. It looks like some incompatibility between how gulp-less and gulp-sourcemaps handle their sourcemaps (at least when Less plugins are used).

I disabled sourcemaps and now the plugin runs without error.  However, I don't see any prefixed CSS files?
gulp.task("styles", function() {
    var cleancss = new lessPluginCleanCSS({ advanced: true });
    var autoprefix= new lessPluginAutoPrefix({browsers: ["last 2 versions"]});
    return gulp.src(['./assets/styles/application.less', './assets/styles/*/*.less'])
        .pipe(changed('./webroot/styles'))
        //.pipe(sourcemaps.init())
        .pipe(less({
            plugins: [autoprefix]
        }))
        //.pipe(sourcemaps.write()) //.pipe(sourcemaps.write('./maps'))
        .pipe(gulp.dest('./webroot/styles'));
});

However, I don't see any prefixed CSS files?

Are you sure? Most of "last 2 browsers" versions may not need prefixes for most of properties, but nothing at all... hmm, try "last 99 browsers" just to make sure it's actually working.

I have updated my gulp file to the below and still don't see any prefixed CSS files in the output.
gulp.task("styles", function() {
    var cleancss = new lessPluginCleanCSS({ advanced: true });
    var autoprefix= new lessPluginAutoPrefix({browsers: ["last 2 versions"]});
    return gulp.src(['./assets/styles/application.less', './assets/styles/*/*.less'])
        .pipe(changed('./webroot/styles'))
        //.pipe(sourcemaps.init())
        .pipe(less({
            plugins: [autoprefix]
        }))
        //.pipe(sourcemaps.write()) //.pipe(sourcemaps.write('./maps'))
        .pipe(gulp.dest('./webroot/styles'));
});

I get this issue (Potentially unhandled rejection [2] Error: ENOENT: no such file or directory, open '$stdin') specifically when using this plugin in combination with sourcemaps. When using just the clean-css LESS plugin, I get correct source maps.
gulp.task('less', function () {
  return gulp.src(['./assets/css/main.less'], {base: '.'})
    .pipe(gulpIf(!isProd(), sourcemaps.init()))
    .pipe(less({
      plugins: [cleanCSS] // works
   // plugins: [autoprefix, cleanCSS] // doesn't work
    }))
    .pipe(gulpIf(!isProd(), sourcemaps.write('.')))
    .pipe(gulp.dest(DEST))
    .pipe(livereload());
});

It should be noted that this is on io.js 3.0.x and 3.1.x. Could be an io.js issue?

Confirming this issue on Node 4.0.0.

My current thinking is that this is not node version specific and is the same bug that @seven-phases-max pointed to, which is a bug in clean-css. https://github.com/less/less-plugin-clean-css/issues/8.. which is https://github.com/jakubpawlowicz/clean-css/issues/593
If you can reproduce without clean-css, I'll investigate.
If you are stuck on this bug consider helping to track down the problem in clean css (some progress and evidence is on that issue) or find a different css minifier (or don't use sourcemaps).

I'd like to help with this but am not very well-versed in the less package / its plugins. This is what my code roughly looks like:
var less = require('gulp-less');
var sourcemaps = require('gulp-sourcemaps');
var autoprefixer = require('less-plugin-autoprefix');

gulp.task('less', function () {

    var destFolder = projectDir + '/css';

    return gulp.src(projectDir + '/css/style-*.less')
        .pipe(sourcemaps.init())
        .pipe(less({
            plugins: [new autoprefixer()],
            relativeUrls: true
        }))
        .on('error', function (error) {
            console.log(error);
        })
        .pipe(sourcemaps.write('.'))
        .pipe(gulp.dest(destFolder));

});

What do you mean by "reproducing without clean-css"?

What do you mean by "reproducing without clean-css"?

okay so it isn't a clean-css issue, since you are reproducing with the above code.
is that in a repo somewhere? if I have an easy to reproduce test case it makes tracking it down easier

There isn't but I'll try to create one.

There you go: https://github.com/borekb/less-plugin-autoprefix-17

thanks, I'll take a look now

seems like it might be a regression in postcss, but am investigating further
https://github.com/postcss/postcss/issues/96
the sourcemap going into postcss has all less sources. coming out it has 1 more source, named <input css 1> which doesn't exist (of course).

Ok, it might not be a regression, but it is related to a quirk in postcss.
one way to fix it is to set
            sourceMap: {
                outputSourceFiles: true
            },

in gulp less.
basically postcss always adds its input to the sources. If you have an output filename its possible to get postcss to merge that source with the existing one (I don't really know why its like that). postcss source is less' output and actually isn't referenced by the map, because the map needs to go from the input less files straight to the output.
possible solutions

get postcss to fix this (I tried previously and wasn't listened to)
remove the postcss source from the sourcemap after it is returned
include the postcss source in the sources content, so nothing tries to fetch it

Please try again now, I found a simpler solution.
It is published as 1.5.1

:+1:, fixed it for me.

Yep, worked for me too. Thanks!

For some reason this still doesn't work for me with 1.5.1. I have version 5.0.10 of postcss installed - maybe some more changes were made that broke it again?
A real shame that postcss developers aren't listening to you at all!

@wazp I've re-installed @borekb example repo with the latest versions and re-ran the test case and it still passes.
Could you provide a test case?

The workarounds noted above don't seem to work for me either

@wolfy1339 Would this be a suitable workaround? https://github.com/Crunch/postcss-less

I will take a look, but in the mean time I can suggest another workaround, instead of using LESS plugins we use gulp or grunt plugins instead. For some reason that fixes the sourcemap problem
On Mon, May 16, 2016 at 8:07 PM -0700, "Matthew Dean" <notifications<EMAIL_ADDRESS>wrote:
@wolfy1339https://github.com/wolfy1339 Would this be a suitable workaround? https://github.com/Crunch/postcss-less

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://github.com/less/less-plugin-autoprefix/issues/17#issuecomment-219608224

Can someone with edit access please correct the title of this issue by replacing "ENONET" with "ENOENT"? This will save some time for people (like me) searching online for "ENONET"; this issue is the first one shown by Google.


Add Conditional URL Advertisements

Adds a link to https://github.com/HeroCC/yourls-conditional-urlads, my YOURLS plugin that redirects links through various advert pages

Neat


Calendar icon - wrong default SVG width

##
The Material Icon for Calendar_Today has a set width that makes it difficult to style next to input or text fields without having to set a z-index.

[x ] This is a v1.x issue.
[x ] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

The width of the actual icon should be set to max 30px
Current Behavior

The icon is set to 245px and overlaps other elements next to it
Steps to Reproduce

Link:

https://material.io/tools/icons/?search=calendar&icon=calendar_today&style=baseline

Context

Your Environment

Tech
Version

Material-UI
v1.4.1

material-ui/icons
^2.0.0

React
16.4.1

Browser

TypeScript

etc.

Please provide a full reproduction test case. This would help a lot 👷 .
A live example would be perfect. This codesandbox.io template may be a good starting point. Thank you!


drum app

add a drum app folder
#hacktoberfest 2024

Hello @DHEERAJHARODE  ,
I have raised this PR for Drum App.
Can you please add label hacktoberfest-accepted and approve it.
Thanks.


Fix/repair dropdown menu button

Description
This PR fixes the burger menu button for mobile devices, as it did not react to click events.
I tried reverting the changes to the point in time where the button worked to find out what introduced the wrong behavior. Unfortunately, it didn't help.
Most likely, the issue appeared due to our customizations to the theme. We fast forwarded the Blowfish theme (submodule) to upstream at some point, but the changes in the theme files that we store in ./layouts were not synced to their ./themes/blowfish/layouts/ counterparts. Updates to the theme files were done according to the Hugo guide Customize a Theme.
Related

#23

Testing
Tested the interaction with the burger menu button in the following environments:

My laptop's Firefox (Responsive Design mode)
My personal Android phone

Checklist
Before submitting a Pull Request, please ensure the following:

[x] 🚨 This PR does not introduce breaking changes.
[ ] All CI checks (GH Actions) pass.
[x] Documentation is updated as needed.
[ ] Tests are updated or added as necessary.
[x] Code is well-commented, especially in complex areas.
[x] Git history is clean — commits are squashed to the minimum necessary.

@pedrominatel Thanks!

@brianignacio5 PTAL

@georgik Feel free to review or share your feedback.

LGTM

Thank you for your help investigating this issue!


Blacked out documentation hurts PEOPLE OF COLOR.

We hope that the destruction that you feel today conveys even fraction of a fraction of a fraction of what those who are being oppressed are feeling. This page will remain downed for now and I ask that you consider reflecting on why you feel uncomfortable inconvenienced and then use that reflection to empathize for others and rally for their support. I am closing and locking this issue.
Originally posted by @TheLarkInn in https://github.com/webpack/webpack.js.org/issues/3763#issuecomment-637870616
I wasn't making the issue request just for me but for other PEOPLE OF COLOR who also rely on Webpack and it's documentation being available. However, if you feel exerting power to shut down the docs in attempt to show some sort of solidarity is the right way to go despite how it hurts the POC community, that's fine. That's on you.
It's disappointing there is no room for discussion about this. We are on the same side here.

I respect your opinion, but there is no room for discussion on this today. If you would like to reflect on ways to rally for people of color through our project in the future, we would happily welcome your contribution.
No show of solidarity is perfect, and to detract from the message by focusing on its imperfections vs the message itself defeats its purpose. I am going to close and lock this again. If you feed the need to have a thouughtful discussion you can reach me on twitter in my DM's or engage in public discussion. Not on this github. Another post about this will result in a 3 day ban from the org.


Small fixes

This PR fixes 3 small reported bugs. Translations will be added later.

Think I found one small bug with this.
For example, I see "This option will be added to the option set http://example.com/terms/options/condition." when it already is added to it.
Option set (nested view) > click on the uri link of an option > see the message (wrongly "will be", when it already is added)
Maybe the components need to take into account the elementAction?


Make Installation instruction platform agnostic

The lines to replace the esbuild with were specific to a Windows environment, calling cmd
This patch replaces these calls with the npm and node commands with the --prefix option, allowing these commands to run on all platforms that run node or npm

Thank you :fire:


Provide a way to install packages when using the buildpack workflow

I have a node.js application that I would like to use with libreoffice and unoconv.  I would like to use the standard node buildpack and git push workflow because that's how all of our other applications are set up, but as far as I can tell there is no way for me to install these two packages (aside perhaps from compiling them from source in a custom buildpack) without creating my own Dockerfile and discarding the benefits and simplicity of the buildpack workflow.
It seems like all I would really need is the ability to add a set of commands to the end of the shim.dockerfile file in the slugbuilder, or replace it entirely using an environment variable to specify a replacement file or file to be cat'd onto the end.
This would significantly improve the power and flexibility of deis while still maintaining simple buildpack workflows for common applications.

I can see how this would be beneficial, but maybe there's a way we can contribute to heroku's buildpack first and see what they have to say. In general, Heroku's answer has been that you should fork their buildpack if you want a custom environment.

Ya, the main problem with that is that it requires you to build everything from source, since buildpacks cannot use apt-get, which is much slower and more difficult generally.

I have created an alternate version of the builder component that implements this available here:
https://registry.hub.docker.com/u/ashaffer/builder/
To use it simply include a file in the root of your repository called shim.dockerfile.  For instance to install unoconv/libreoffice you might do:
USER root
RUN apt-get update
RUN apt-get install -qy libreoffice-script-provider-python unoconv
USER slug

Alternatively, I was notified that https://github.com/ddollar/heroku-buildpack-apt exists. Along with heroku-buildpack-multi you might be able to achieve the same effect.

@ashaffer since the recommended cross-platform workflow is to use heroku-buildpack-apt in tandem with heroku-buildpack-multi, I think it's safe to close this now. Thanks!


Many safe browsing testing links are not detected (as threats)

Hi,
We are using Web Risk with the following configuration (threat types):
$response = $webrisk->searchUris($url, [
    ThreatType::MALWARE,
    ThreatType::SOCIAL_ENGINEERING,
    ThreatType::UNWANTED_SOFTWARE,
]);

$threats = $response->getThreat();

For testing we use the links provided here: https://testsafebrowsing.appspot.com/
We noticed that many links were not detected as a threat. Some of them are:
(Safe) Safe Browsing Testing Links

Webpage Warnings (not dectected):

    3. [A/W/M/L/C/D] Should show a malware warning due to a bad subresource: https://testsafebrowsing.appspot.com/s/malware_in_iframe.html
    5. [W/M/L/C/D] Should show a malware warning due to bad assets: https://testsafebrowsing.appspot.com/s/image_medium.html
    6. [A/W/M/L/C] Should show a billing warning: https://testsafebrowsing.appspot.com/s/trick_to_bill.html

Desktop Download Warnings: NONE of the links were detected as a threat.

IOS/OSX Warnings (not detected):

    1. Should show malware warning (IOS): https://testsafebrowsing.appspot.com/apiv4/IOS/MALWARE/URL/
    2. Should show social engineering warning (IOS): https://testsafebrowsing.appspot.com/apiv4/IOS/SOCIAL_ENGINEERING/URL/

Permissions Blacklisting: NONE of the links were detected as a threat.

Password Protection: NONE of the links were detected as a threat.

Low Reputation: NONE of the links were detected as a threat.

Desktop DLP Warnings: NONE of the links were detected as a threat.

Malware deep scanning warnings: NONE of the links were detected as a threat.

Hi @FilipQL,
While we offer support for issues related to the client library, we're not able to help much with API-specific questions in this case. I suggest you refer to the list of available support resources, where you can get in touch with people with expertise in this service.


fix comments & coding style

Codecov Report

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

@@           Coverage Diff           @@
##           master      #66   +/-   ##
=======================================
  Coverage   55.37%   55.37%
=======================================
  Files           9        9
  Lines         186      186
=======================================
  Hits          103      103
  Misses         81       81
  Partials        2        2

Impacted Files
Coverage Δ

script/shell.go
88.23% <ø> (ø)
: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 9d5a6c4...6b0515a. Read the comment docs.


CUDA initialization error on current master

Hi! While I was trying to develop a PR for the shutdown lockup issue, I noticed that the recent commits on master broke model initialization:
RealTimeSTT: root - ERROR - Error initializing main faster_whisper transcription model: CUDA failed with error initialization error
Traceback (most recent call last):
  File "/nix/store/df8n8d04bdfdbwpgccjsaw8sc4hin2pk-python3-3.11.9-env/lib/python3.11/site-packages/RealtimeSTT/audio_recorder.py", line 629, in _transcription_worker
    model = faster_whisper.WhisperModel(
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/nix/store/df8n8d04bdfdbwpgccjsaw8sc4hin2pk-python3-3.11.9-env/lib/python3.11/site-packages/faster_whisper/transcribe.py", line 144, in __init__
    self.model = ctranslate2.models.Whisper(
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
RuntimeError: CUDA failed with error initialization error

If I leave everything the same and downgrade to v1.1.16 everything works fine. My guess is that this happens because you were previously calling torch.cuda.is_available() in each thread which initialized the cuda runtime in that thread. This isn't happening anymore possibly leading the observed error.

please try:
from pytorch_lightning.utilities.memory import is_oom_error


Non-linear performance for large size of delta log

In an attempt to create a delta table for #425, I attempted to load a relatively large delta log containing ~ 700k add actions and 9.5million remove actions.
 I've logged the time it takes to handle each separate checkpoint file:
  47.85s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000001.0000000021.parquet
 226.31s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000002.0000000021.parquet
 541.34s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000003.0000000021.parquet
 840.58s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000004.0000000021.parquet
1123.62s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000005.0000000021.parquet
1402.43s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000006.0000000021.parquet
1688.98s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000007.0000000021.parquet

It's seems that the load becomes slower and slower the more actions are already loaded. As this is not the case with a table that only includes add actions (see #435: 2 minutes for 5million files, no tombstones), the culprit must be in the remove actions.
fn process_action(state: &mut DeltaTableState, action: Action) -> Result<(), ApplyLogError> {
    match action {
        Action::add(v) => {
            state.files.push(v);
        }
        Action::remove(v) => {
            state.files.retain(|a| *a.path != v.path);
            state.tombstones.push(v);
        }
	...
	}
	...
}

This brings non-linearity: for each add action we seem to make a linear scan through the entire set of adds. The more add actions we have, the longer that takes.
One possible solution would be to collect all actions, build a set of all files that must be removed, and do that in one pass at the very end.
Also, it seems counter-intuitive for a checkpoint to contain both an add and a remove operation for the same file; I suspect that the behavior can be entirely skipped when loading a checkpoint, and only needs to be applied to (relatively small) incremental update operations.
``

I'm willing to look into this tomorrow, this seems relatively easy to fix (based on the assumption that my analysis above is correct).

I disabled the line containing the retain just to make sure I"m not staring at the wrong line.
2.21s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000001.0000000021.parquet
2.17s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000002.0000000021.parquet
2.16s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000003.0000000021.parquet
2.16s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000004.0000000021.parquet
2.17s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000005.0000000021.parquet
2.18s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000006.0000000021.parquet
2.20s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000007.0000000021.parquet
2.21s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000008.0000000021.parquet
2.24s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000009.0000000021.parquet
2.25s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000010.0000000021.parquet
2.25s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000011.0000000021.parquet
2.27s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000012.0000000021.parquet
2.25s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000013.0000000021.parquet
2.23s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000014.0000000021.parquet
2.23s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000015.0000000021.parquet
2.27s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000016.0000000021.parquet
2.25s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000017.0000000021.parquet
2.27s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000018.0000000021.parquet
2.27s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000019.0000000021.parquet
2.25s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000020.0000000021.parquet
2.25s: loading checkpoint data from f=<delta_root>/_delta_log/00000000000000002710.checkpoint.0000000021.0000000021.parquet

I was thinking about the same thing while reviewing https://github.com/delta-io/delta-rs/pull/431. We should definitely apply action state change in batch instead of one at a time.

Also, it seems counter-intuitive for a checkpoint to contain both an add and a remove operation for the same file; I suspect that the behavior can be entirely skipped when loading a checkpoint, and only needs to be applied to (relatively small) incremental update operations.

I think you just found a bug in our checkpoint implementation ;) Based on https://github.com/delta-io/delta/blob/master/PROTOCOL.md#action-reconciliation, this should never happen. cc @xianwill @mosyp this unnecessarily increased our checkpoint size.

I think you just found a bug in our checkpoint implementation ;) Based on https://github.com/delta-io/delta/blob/master/PROTOCOL.md#action-reconciliation, this should never happen. cc @xianwill @mosyp this unnecessarily increased our checkpoint size.

A collection of remove actions with unique paths. The intersection of the paths in the add collection and remove collection must be empty. That means a file cannot exist in both the remove and add collections. The remove actions act as tombstones.

If add / remove for the same file could be in one checkpoint, the final state would depend on the order of observing them. I'm glad the spec does not allow that.
I completely missed #431 btw, good that there's already something done. I repeated my tests with the newest revision, but it doesn't seem to change anything, probably because none of the remove action actually matches any of the add actions so we walk the vec to the very end for each tombstone anyway. I suspect that it improves performance for other use cases, though :+1:

but it doesn't seem to change anything, probably because none of the remove action actually matches any of the add actions

That's quite strange. This means we commit a remove action immediately after a file has been added? Anyway, I think this won't be a problem anymore once we move to batch update.
BTW, I am not actively working on these performance issues because I assume you are interested in solving them. If that's not the case, please let me know, I will be more than happy to help.

That's quite strange. This means we commit a remove action immediately after a file has been added? Anyway, I think this won't be a problem anymore once we move to batch update.

I try to formulate better: when loading a checkpoint, we never have a "remove" that matches an "add", because they'd be part of the same checkpoint, so the optimization from #431 can't be applied. Every add is kept, so the search (retain, or index computation in the newest revision) does not find a matching entry so it has to search state.files until the very end and does not modify it.

BTW, @dispanser I am not actively working on these performance issues because I assume you are interested in solving them. If that's not the case, please let me know, I will be more than happy to help.

Indeed. I'm having a day off today, and I don't see a better way to spend my time than learning some rust ;). I'll try to come up with something today.

I try to formulate better: when loading a checkpoint, we never have a "remove" that matches an "add", because they'd be part of the same checkpoint,

Oh, i see. Yeah, for a valid checkpoints, this optimization would have no effect. It only works for incremental version upgrades.


Missing layout call in terminal

Resizing the workbench called layout and fixed it. I can't repro unfortunately, sorry.

Actually, there's an extra pixel, even after a proper layout. Seems to be a separate issue.


Vote for TiKV character

We are looking for a new character for TiKV, and we need your vote!
Many of you may have read Illustrated Children’s Guide to Kubernetes. In this book, Phippy and her friends explain the core concepts of Kubernetes in simple terms. And the character Phippy, the yellow PHP application giraffe is well known after that.
As a CNCF project, TiKV is joining the adventure by donating a character to the Phippy and Friends family. The character will also be presented in Kubecon China. All we need is:

An animal that begins with the letter T (for TiKV) - like a tiger, tapir, toucan or tortoise.
A name for TiKV character, also beginning with the letter T (for example, CNCF has Linky the lobster who represents Linkerd, and Hazel the hedgehog who represents Helm.)

We have listed some animals in the comment below, you can vote thumb up for your favourite or list others you like. Also, you can help TiKV to have an easy-remember name by comment.
We will close the vote before 8PM on November 12th (GMT+8)
Reference:
https://www.cncf.io/phippy/
You can also get some inspiration from:
https://a-z-animals.com/animals/animals-that-start-with-t/
https://alphabetimals.com/animal-dictionary/animals-that-start-with-t/

Tiger

Tortoise

Tree frog

T-Rex

Tropicbird

Tetra

Toucans

a. "Tycho"
Related: astronomer Tycho Brahe, lunar crater Tycho, fictional space station Tycho

Eddie, an elephant.

tuckoo

Eddie, an elephant.

It's not start with T ><

Tom cat

Tarpon

thunderbird？

thunderbird？

cool!!! But already used by Mozilla for an open-source cross-platform email client
https://www.thunderbird.net/en-US/

T-800 robot
From the Future

do we vote for names in this issue or a separate issue

Teng
https://en.wikipedia.org/wiki/Teng_(mythology)

Tyrannosaurus, "霸王龙" in Chinese, lived in the Late Cretaceous.
https://en.wikipedia.org/wiki/Tyrannosaurus

Tyrannosaurus, "霸王龙" in Chinese, lived in the Late Cretaceous.
https://en.wikipedia.org/wiki/Tyrannosaurus

Same as "T-Rex"?

Ti　鯛

do we vote for names in this issue or a separate issue

in the same issue is fine :)

T-800 robot From the Future

It has to be animal ><

TiKiwi (kiwi)

Tapir

It's sooooo cute

Toco Toucan
https://en.wikipedia.org/wiki/Toco_toucan

Name：Trusty
start with T and include rust ><

We will use Tiger as the character, thank you all!


Update README.md with grammar changes and clarification of language

This does a quick pass through the README looking for grammar changes as well as some formatting recommendations to make it easier to follow, look more professional.
Changes Made

Normal grammar check/rewording of sentences to read more naturally
Moved motivation outside of of a details tag and added a small bit as an intro. This provides users with a hook immediately to understand what the plugin is and why they want to use it (the details for this make it easy to miss)
Moved Neovim version requirement to a new section rather than a note
Made tip summaries bold to make them more noticeable and less easy to scroll past

Thanks. Really appreciated your time and effort.


Question: Do you need service discovery enabled on the ECS tasks for this to work?

Question: Do you need service discovery enabled on the ECS tasks for this to work or does it use the API to get around the use of service discovery?

This code scrapes the AWS API for that information:
var interval = flag.Duration("config.scrape-interval", 60*time.Second, "interval at which to scrape the AWS API for ECS service discovery information")

Read main.go for more information :-)


Publish 01/14/2022, 10:30 AM

Docs Build status updates of commit af3ee6f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Remove-MailboxFolderPermission.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Multi User problem

Hi,
we tried to work with multiple user on the same Git repository.

When the first developer clones the dev package to the git repository in ABAP Git everything works fine
When the second developer clones the same package to the same git repository we get the error "package in use"

Do you have any ideas how to support multi user development on the same objects in ABAP Git?
Best regards

It is not going to work - it is just not technically possible. The git files are deserialized into objects and you cannot have multiple versions of object in your system.
You need private system for all users.
You can put your development system into a docker image and let the developers run it as a container anywhere.
Have a look at:
https://github.com/filak-sap/sap-nw-abap-docker
or
https://github.com/nzamani/sap-nw-abap-trial-docker

In the SAP kernel it is only possible to have one active version of a program/class at a time.

It is not my intention to work with multiple user on one one object at a time.
My developers work on different classes within one dev package at a time and i tried to organize this in one git repository.

okay, as code is global in SAP, one user installing the repository is enough.
Other users can find the code under the burger icon, and click the star icon to make it a favorite,

Yes, that's possible but they are going to commit/push to the same remote repository and branch which is sub-optimal and causes a lot of confusion, especially when you are git beginner.

you can also setup abapGit to push automatically without developer involvement, see https://blogs.sap.com/2017/05/07/abap-using-git-for-safety-and-transparency/
but it depends on you use-case/scenario


Segmentation fault (core dumped) - Node 0.12.0 / iojs 1.2

Hi, with the las release of Node (v0.12.0), node crashes when i want to make a request. Debugging i found the line that throws the error, is the 243 of writable-tracking-buffer.js
this.buffer.write(value, this.position, encoding);

But, there are something odd with the error, not always crash...
With this query, 'SELECT name FROM sys.databases', crash.
But with this one, 'select 1 as number', works fine.
I think, maybe, it a encoding problem... crashes when try to encode the query into the buffer with the 'ucs2' encode.
Thank!!

The problem only appear with a x64 local compilation. With the binary of the site work "fine" (i have some no related issues).
Thanks!

Hi do you still encounter segmentation fault?
var Connection = require('tedious').Connection;

var config = {
  userName: 'mssql',
  password: 'mssql',
  server: '<IP_ADDRESS>'
};

var connection = new Connection(config);

connection.on('connect', function (err) {
  console.log(err);
});

[1]    8104 segmentation fault (core dumped)
I get core dump when executing it from linux to windows machine. It is fine at local windows machine. However, it was fine 2 months ago.

This might be related to https://github.com/nodejs/node/issues/2457.
Where is your node version from?

@arthurschreiber v0.12.7

I'm closing this now, as I believe this was related to nodejs/node#2457 and is not something tedious specific.
Feel free to re-open if you still see this issue on recent Node.js versions.


images: Name final docker target as 'release'

This is in preparation for a subsequent additional target that is used
to wrap the existing logic with a debugger. This should be a purely
internal detail with no external impacts.
Related: #21108

/test

/mlh new-flake Cilium-PR-K8s-1.25-kernel-net-next


New Feature: Save Image

I often save images that I like so that I can repost them later without having to search through a thousand tweets. It'd be nice if AndStatus had a "Save Image" option in the context menu.
It should be relatively easy to implement, since AndStatus already saves the images to a bulk folder for offline viewing. It's just a matter of copying it to the target destination. For example, "/sdcard/Pictures/AndStatus". An option could be added to the settings to customize this location, too.

We already have "View image" context menu  option.
The application that can View an image, can usually save it. I just test on CM firmware...

Ah, I use QuickPic*, which doesn't have the ability to do so, at least for local files. Since they're stored on the SD card already, I can understand why that feature isn't usually necessary.
Warning: Unrelated rant below. Feel free to ignore. And my apologies in advance. XD

The last version before Cheetah Mobile took it over & inflated the apk to double the size just by adding their proprietary cloud service to it, that is. QuickPic already had support for GDrive, Dropbox & a few others btw, so the idea that a single cloud service added 2-3MB to the apk when the existing ones didn't even add 1MB is preposterous. They likely added other stuff that wasn't mentioned, & I don't trust devs with shady crap like that.

I see why QuickPic doesn't have "Save" option: exactly because they are promoting their cloud storage.
So if you want to save to SD, you better switch to some other viewer...
PS: Regarding 3Mb added with only one feature: this doesn't seem unusual to me...

The thing is, though, they didn't add a new feature. The 2MB apk I use from before Cheetah Mobile took over does have support for GDrive, Dropbox, & a few others. There's no reason adding an additional server to the support list should double that size. That's why it's suspicious to me.
btw, I've been hunting for a new photo viewer, but so far, none that I've tried have an explorer-like file browser. They all just list every folder with a picture, no matter where it's embedded in the filesystem. If you know of one offhand, I'd love any recommendations.
Anyway, I digress. I understand your reasoning for this, & it makes sense to me regardless of my personal feelings. I'll keep hunting for a new picture viewer app, & I thank you for your time.

@Yowlen Actually QuickPic was my favorite image viewer for many years. I don't know any better alternative yet... but it appears that most of the time I don't need much, and almost any viewer suffices... plus universal Total Commander.


CMake static build of OpenEXR 2.2 fails to link dwaLookups on Linux

I do a CMake build of ilmbase with -DBUILD_SHARED_LIBS=OFF and install to a directory /ilmbase-INSTALL.
Then I configure OpenEXR with the following CMake command:
cmake -DCMAKE_INSTALL_PREFIX=/openexr-INSTALL -DBUILD_SHARED_LIBS=OFF -DCMAKE_BUILD_TYPE=Release -DILMBASE_PACKAGE_PREFIX=/ilmbase-INSTALL -DZLIB_ROOT=/my_zlib_install ..

This will fail to link dwaLookups with the following error message:
/ilmbase-INSTALL/lib/libIlmThread-2_2.a(IlmThreadPosix.cpp.o): In function `IlmThread_2_2::Thread::start()':
IlmThreadPosix.cpp:(.text+0xb4): undefined reference to `Iex_2_2::throwErrnoExc(std::string const&, int)'
/ilmbase-INSTALL/lib/libIlmThread-2_2.a(IlmThreadSemaphorePosix.cpp.o): In function `IlmThread_2_2::Semaphore::Semaphore(unsigned int)':
IlmThreadSemaphorePosix.cpp:(.text+0x72): undefined reference to `Iex_2_2::throwErrnoExc(std::string const&)'
/ilmbase-INSTALL/lib/libIlmThread-2_2.a(IlmThreadSemaphorePosix.cpp.o): In function `IlmThread_2_2::Semaphore::post()':
IlmThreadSemaphorePosix.cpp:(.text+0x16a): undefined reference to `Iex_2_2::throwErrnoExc(std::string const&)'
/ilmbase-INSTALL/lib/libIlmThread-2_2.a(IlmThreadSemaphorePosix.cpp.o): In function `IlmThread_2_2::Semaphore::value() const':
IlmThreadSemaphorePosix.cpp:(.text+0x212): undefined reference to `Iex_2_2::throwErrnoExc(std::string const&)'
collect2: error: ld returned 1 exit status

Inspecting the command line by running VERBOSE=1 make reveals the source of the error:
/usr/local/bin/g++48   -O3 -DNDEBUG   CMakeFiles/dwaLookups.dir/dwaLookups.cpp.o  -o dwaLookups  -L/ilmbase-INSTALL/lib -rdynamic -lHalf -lIex-2_2 -lIlmThread-2_2 -lpthread -Wl,-rpath,/ilmbase-INSTALL/lib

The order in which the ilmbase libraries are specified is wrong. IlmThread depends on symbols from Iex, so they need to be swapped. Changing the command line to
/usr/local/bin/g++48   -O3 -DNDEBUG   CMakeFiles/dwaLookups.dir/dwaLookups.cpp.o  -o dwaLookups  -L/ilmbase-INSTALL/lib -rdynamic -lHalf -lIlmThread-2_2 -lIex-2_2 -lpthread -Wl,-rpath,/ilmbase-INSTALL/lib

makes the error goes away. Once dwaLookups has been built manually this way, the rest of the CMake run can complete without further errors.
Reproduced on a CentOS 5 Linux with gcc 4.8 and CMake 3.3.

I opened a pull request with a fix for the issue.

Looking into the OpenEXR issue backlog. This seems to have been merged, so closing.


resin-docker-build should track latest versions of dockerode

Currently we are pinned to 2.3.1 due to custom promise handling code in dockerode. This should be fixed.

Closed by https://github.com/resin-io/resin-docker-build/commit/fdf4105922edf753a6577e823bee1f0b474ae508 and https://github.com/resin-io/resin-docker-build/commit/a0efc1aa380c4a89bb3111c0872c76e2cf9b30ab


EQcorrscan 0.2.7

After tests the recipe should be good - uploaded to pypi - if all works then this is v 0.2.7!

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Updating readme from branch example

Updates
I Updated the readme file. Please review and accept.

Thoughts
I probably shouldn't but ok 👍


Problem with pulldown menu (in breadcrumb trail) when zoomed in.

I was zoomed in (on Chrome) looking for a specific string in the heap map.
This is an iterative process (I wish there were some way to go "back" in Observatory.)
When I land on the wrong instance, I use the root->heap map pulldown to bring the heap map up and to try again. While I am zoomed in, the menu is not working properly, as shown in the screenshot.

Attachment:
[Screen Shot 2014-05-12 at 1.29.36 PM.png](https://storage.googleapis.com/google-code-attachments/dart/issue-18778/comment-0/Screen Shot 2014-05-12 at 1.29.36 PM.png) (269.39 KB)

Don't know when it was fixed, but this is working today.


[OB3] - Hostname placeholder is not updated with configured hostname in GetInvocationDataApp.siddhi

Description:
Hostname placeholder is not updated with configured hostname in GetInvocationDataApp.siddhi file when executing the configure.sh script.
Siddhi file after executing the configure.sh script.

Suggested Labels:
Suggested Assignees:
Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Verified as Fixed


AppCacheIterator::AppCacheIterator has no upper bound

Iterating on AppCacheIterator does start on the first entry matching datatype, but does not stop at the last. In fact it continues to iterate to the end of app cache.
For example command execute getlistof project starts with listing project beacons, but also includes superblock and vote data.

Serves me right for not adding tests :(


[WIP 🚧 ] Add command to stop the device and put it into standby mode.

Add a --action optional argument to the command.
The possible values are:

monitor (default)
stop

If --action monitor is provided, or --action is omitted, the behavior is the same as before.
If --action stop is provided, the program will stop the belt and put the device into standby mode.
⚠ If there's already a process running the monitoring feature, a second invocation of the command, from another window, will not work. The device isn't found.
We need to have a way to have a primary process running, and notifying it somehow to perform some commands like stopping. Could be via a shared file, exposing a REST api, a socket...

Replaced by #28


Metrics: instrument executors

What this PR changes/adds

Changed state machine loop from an endless busy loop to a task that reenqueues itself with a delay
Use scheduled executor instead of thread sleep
Added Executor instrumentation to the state machine loops, and a few other places

Why it does that

Reduce thread usage
Running one executor task per loop execution allows metrics on loop execution time. In Prometheus:

(to reproduce this image, run commands in README from sample 04.3)
Further notes

Moved NullExecutorInstrumentation to a static interface method for simplicity and to make it more accessible to modules.
DPF executor will be instrumented in a follow up PR, to also make it the pool common to various sinks

Linked Issue(s)
Closes #790
Checklist

[x] added appropriate tests?
[x] performed checkstyle check locally?
[x] added/updated copyright headers?
[x] documented public classes/methods?
[x] added/updated relevant documentation?
[x] added relevant details to the changelog? (skip with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

@algattik LGTM. As a temporary solution until we clean up the developer documentation, can you add notes in docs/architecture-principles.md about using executor instrumentation?

@algattik LGTM. As a temporary solution until we clean up the developer documentation, can you add notes in docs/architecture-principles.md about using executor instrumentation?

@algattik LGTM. As a temporary solution until we clean up the developer documentation, can you add notes in docs/architecture-principles.md about using executor instrumentation?

@jimmarino this is documented in docs/metrics.md. Should we add a pointer from architecture-principles.md?

@algattik LGTM. As a temporary solution until we clean up the developer documentation, can you add notes in docs/architecture-principles.md about using executor instrumentation?

@jimmarino this is documented in docs/metrics.md. Should we add a pointer from architecture-principles.md?

+1

@jimmarino this is documented in docs/metrics.md. Should we add a pointer from architecture-principles.md?

Implemented

Codecov Report

Merging #912 (0f5d924) into main (e200d9e) will decrease coverage by 0.00%.
The diff coverage is 76.00%.

@@             Coverage Diff              @@
##               main     #912      +/-   ##
============================================
- Coverage     61.15%   61.14%   -0.01%
- Complexity     2228     2229       +1
============================================
  Files           586      585       -1
  Lines         12637    12652      +15
  Branches        901      901
============================================
+ Hits           7728     7736       +8
- Misses         4485     4492       +7
  Partials        424      424

Impacted Files
Coverage Δ

...dataspaceconnector/core/CoreServicesExtension.java
0.00% <0.00%> (ø)

...ceconnector/contract/ContractServiceExtension.java
0.00% <0.00%> (ø)

...connector/transfer/core/CoreTransferExtension.java
0.00% <0.00%> (ø)

...connector/dataplane/api/DataPlaneApiExtension.java
0.00% <0.00%> (ø)

...econnector/spi/system/ExecutorInstrumentation.java
0.00% <0.00%> (ø)

...egotiation/AbstractContractNegotiationManager.java
85.36% <50.00%> (-3.83%)
:arrow_down:

...sfer/core/transfer/TransferProcessManagerImpl.java
75.41% <60.00%> (-0.44%)
:arrow_down:

...aceconnector/common/statemachine/StateMachine.java
94.23% <100.00%> (+6.23%)
:arrow_up:

...iation/ConsumerContractNegotiationManagerImpl.java
88.26% <100.00%> (ø)

...iation/ProviderContractNegotiationManagerImpl.java
90.57% <100.00%> (ø)

... 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 e200d9e...0f5d924. Read the comment docs.

@jimmarino fixed by upstream merge - you can go ahead :)

LGTM, Can you look at what the failing tests are about an I'll merge once they turn green?

@jimmarino All checks are green now. Thank you.

Azure cosmos DB checks are failing due to emulator issue. And its behavior is unpredictable so hard to keep it green. You need to try multiple times and hope it works.
Also this PR changes does not have cosmos db related changes. Thanks.


Place your single stone bricks block.
It is automagically replaced with the stack you had "anywhere else into your inventory".
Do the same with a with a default:tree
You have to choose by yourself the replacing stack.
I'm sure it's not the only affected block, but I don't have other examples. Could we make a rule to make sure it always happens as for bricks, for constancy?

It's some callback blocking the mod again.
Mg goes away and curses to the heavens
I'll investigate and fix that sh!t once more.

@LeMagnesium Il faut rewrite la fonction, j'ai fait ce bout de code, par contre dans invtweak ça ne fonctionne pas, il faut rewrite dans default apparemment.
--minetest.rotate_node(itemstack, placer, pointed_thing)
local old_rotate_node = minetest.rotate_node
function minetest.rotate_node(itemstack, placer, pointed_thing)
	local stck_name = itemstack:get_name()
	local ret = old_rotate_node(itemstack, placer, pointed_thing)
	if not minetest.setting_getbool("creative_mode") and ret:get_count() == 0 then
		local index = placer:get_wield_index()
		local inv = placer:get_inventory()
		if inv:get_list("main") then
			for i,stack in ipairs(inv:get_list("main")) do
				if i ~= index and stack:get_name() == stck_name then
					ret:add_item(stack)
					stack:clear()
					inv:set_stack("main", i, stack)
					minetest.log("action", "Inventory Tweaks: refilled stack("..stck_name..") of "  .. placer:get_player_name()  )
					break
				end
			end
		end
	end
	return ret
end

il faut rewrite dans default apparemment.

Enlève juste le rotate_node, on s'en fiche après tout.

bah c'est pas mal de nodes qui ont cette fonction à la place de place_node(), ça gère le sneak et tout.

on_place = minetest.rotate_node

ça gère le sneak et tout.

Ça ne gère pas le sneak, seulement le placement statique, qui n'a aucun intérêt pratique.

si, la fonction appelle une autre fonction,
http://dev.minetest.net/minetest.rotate_node

calls minetest.rotate_and_place() with infinitestacks set according to the state of the creative mode setting, and checks for "sneak" to set the invert_wall parameter.

I personally think we should open an issue about that and let the devs properly fix their own sh*t. It's their fault, and their problem if logging and other callbacks do not work. Who here agrees?

+1 mais c'est invtweak qui se base sur le callback on_place_node pour vérifier l'inventaire, là je ne vois pas ce qu'ils peuvent faire a part faire un callback on_rotate_node.

+1 @LeMagnesium
But we need to link the devs here :)

maptools :
moretrees :
multitest :
quartz :
homedecor :
moreblocks :
nether :
default(minetest_game) :

This isn't something routine mods should ever have to consider.  Either you need to make a mod that wedges in before the rotate function to do what you're looking for, or make your changes at the subgame level.

make your changes at the subgame level.

I would rather do that. Minetest's dev will apparently never find a way to go around their sh*tty forceful callback blocking system, so we'll have to fix on our repo.
And next time they complain about node placement not logged, I won't help.

Well, finally do we want to fix that on our own way or I closed this issue (players will be sad...) ?

fixed https://github.com/MinetestForFun/server-minetestforfun/commit/3752bf2e645391afce10bdb7866406d03e95916d

Moved to _misc: 947b3014566a611675435e3ceb6f7bc485c4199c

Can't you just simply make rotate_node call the registered on_placenode functions?


Support compressed hdf5 files in Dataset.download()

Is your feature request related to a problem? Please describe.
HDF5 dataset views contain lots of redundant information, and it would be nice to store them in compressed format. However, dataset.download does not support unzipping.
Describe the solution you'd like
dataset.download should support unzipping view, perhaps with information about the type of zip file in the extension or view_metadata.

Closed by #488.


adding avioneo's airframe geometry VTOL Penta Tiltwings

avioneo's airframe doc init.d 13015 + CMakeLists
avioneo's airframe mixers main + aux
avioneo's airframe penta tiltwings geometry + CMakeLists
px4airframes Tools srcparser
svg also pull in docs&qgc

first commit for a newbie :)

This error means often means the flash is too big (>1MB). It could mean that you're not using the right compiler https://dev.px4.io/en/setup/building_px4.html#building_nuttx or that you've added too much to the Firmware, so that it has overflowed. I'd confirm that you're using the right compiler and that a "bog standard" build works first.

Was talking about the Jenkins test supposed to have the right compiler. The building process seems to be ok (W/O fatal error on my own docker)
testing into the pixhawk....
Thanks

As I said before,  the building run of px4fmuv3 on my local docker is ending fine w/o error. fmuv2 seems to be a common failure, so please help me to fix I you have any idea !

@bkueng Your advice appreciated.

There is a jenkins failure that appears unrelated to these changes.
Apparently FMUv3 builds, but FMUv2 fails (I think) when using the correct compiler. I think they means they will need to remove a module to get this in. Any thoughts on what.

@hamishwillee @bkueng at this point the fmuv3 I build doesn't work correctly with probably a bug somewhere (Missing Params : -1:FW_ARSP_MODE Preflight fail on QGC : compass Sensor 0 missing)
Any help will be appreciated

@TSC21 got the "ccache permission issues, disabling" mess from entrypoint.sh you contribute on. Anything to do ? Thx

@yvescharles I have no idea of what are you talking about

@TSC21 Find file containers/docker/px4-dev/scripts/entrypoint.sh line 16, you seem to be list in the 2 contributors ?

I never messed with the ccache part of the script. But as it says, you probably have permissions issues when accessing the ccache. But why is that even relevant you?
Also if you want to see who has done what on a file, you have a button on the top left corner of the page where you have the file opened called "Blame" ;)

OK should ask @daga, Daniel could you help ? Thx
MacBook-Air-de-Yves:Firmware yv$ sudo ./Tools/docker_run.sh "make airframe_metadata"
Password:
guessing PX4_DOCKER_REPO based on input
PX4_DOCKER_REPO: px4io/px4-dev-nuttx:2018-11-22
Starting with UID : 0
chown: changing ownership of '/Users/yv/.ccache': Operation not permitted
ccache permission issues, disabling
ninja: Entering directory `/Users/yv/Docker/Px4/src/Firmware/build/px4_sitl_default'
[0/1] Re-running CMake...
-- PX4 config file: /Users/yv/Docker/Px4/src/Firmware/boards/px4/sitl/default.cmake
-- PX4 config: px4_sitl_default
-- PX4 platform: posix
-- PX4 version: v1.8.0-1828-g0c2c8cad22
-- cmake build type: RelWithDebInfo
-- PX4 ECL: Very lightweight Estimation & Control Library v0.9.0-608-gacde4eb
-- Configuring done
-- Generating done

I never messed with the ccache part of the script. But as it says, you probably have permissions issues when accessing the ccache. But why is that even relevant you?
Also if you want to see who has done what on a file, you have a button on the top left corner of the page where you have the file opened called "Blame" ;)
trying to understand to find the bug origin
at this point the fmuv3 I build doesn't work correctly with probably a bug somewhere (Missing Params : -1:FW_ARSP_MODE Preflight fail on QGC : compass Sensor 0 missing)
Any help will be appreciated

@yvescharles do you know what ccache is for? Even if you get ccache disabled, it's not relevant for your problem.

@TSC21 thanks; as it written in the top it's my first commit from a newbie ;) Thx for your help, I apprericate

Btw: this is supposedly a pull request to add an airframe configuration upstream. So where are the config files? Why are you constantly reverting and readding the files on commits.

@TSC21 Nuno, I probably misunderstanding something simple for you somewhere for sure ! Indeed, this conversation is for me attached to a pull request where the config files commited can be seen here : https://github.com/PX4/Firmware/pull/10931/commits/6b91be99bd62d7a22ddc5813cb5caeb2d1eecf25
where I'm wrong ?


Refactor to allow passing endpoints

i.e. const client = createClient("https://api.eos.eosn.io")

test


(request org repo) highlightjs-riscvasm

I would like to request the creation of a highlightjs-riscvasm repository for my 3rd party grammar.

[x] I have an existing personal repository ready to go

Metadata

Grammar Name: riscvasm
Link to repo: https://github.com/aana-h2/highlightjs-riscvasm

Requirements

[x] I've read the language Contributor Checklist
[x] I've read the Language Contribution Guide
[x] I'm currently willing to support and maintain this grammar over time
[x] That repo includes a dist folder with CDN-ready CJS and ESM builds
[x] That README.md includes examples of simple web usage
[x] That README.md includes examples of Node.js usage

Afterwards
Submit a PR that:

[x] adds mention of your new language to CHANGES.md
[x] updates SUPPORTED_LANGUAGES.md in the main library

Looking forward to seeing this finished!

Looking forward to seeing this finished!

Sorry, too busy. But I am sure that it will be finished in the next week.

@joshgoebel  what is the nest step?

Done. https://github.com/highlightjs/highlightjs-riscvasm


mouse not fired event

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:
Version : 1.73.0 (user setup)
Validation : 8fa188b2b301d36553cbc9ce1b0a146ccb93351f
Date : 2022-11-01T15:34:06.111Z
Electron : 19.0.17
Chromium : 102.0.5005.167
Node.js : 16.14.2
V8 : <IP_ADDRESS>-electron.0
Système d’exploitation : Windows_NT x64 10.0.19045
Sandboxé : No

Steps to Reproduce:

pass mouse hover symbole, get fix menue, and click fix with mouse pointer
sometime is randomly not work,  and need ~10 click to success click!
Or required to use keyboard instead of mouse to fix issue with the menue.

@sandy081 I believe this is about the error hover

@mjbvz It seems the user is able to get the quick fixes drop down by running the command editor.action.quickFix but quick fix is not getting applied after selecting a quick fix. Can you please help to understand why quick fix is not getting applied?
https://github.com/microsoft/vscode/blob/070de6c570b34b332f00d6b426ab000f2b71da55/src/vs/editor/contrib/hover/browser/markerHoverParticipant.ts#L222

@djmisterjon It is difficult to tell what the gif is supposed to be showing. Please share steps to reproduce the problem

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


ApexGauge cannot be updated

Hi There.
Can we extend ApexGauge to allow redrawing or updating the control?
Other chart components can be updated by calling:

UpdateOptionsAsync(false, false, false);
RenderAsync()

Why would this be needed?
I have a scenario where when I need to flip between dark and light themes, and requires me changing my ApexGauge's Chart-ForeColor to adapt to the theme.

Hello,
The Gauge chart is just a simplified version of a radial bar chart with one series.
If you use the radial bar you will get all features.
https://apexcharts.github.io/Blazor-ApexCharts/radialbar-charts
Thank you


updated readme (login)

added where to find login informations so user of cockpit-docker can immediately start with it.
Otherwise they have to search for it (like I) e.g. in Issues.

Thanks!


gRPC: support a stream protocol to notify TiKV

PD will wait the leader peer of the region sending heartbeat and then response the operator for the region, the heartbeat sending interval is 1m which is not immediate if PD want to let the region do an operator ASAP.
We can define a Push stream, if PD want to schedule a region or do other things quickly, it can send the message with the stream, TiKV receives the message and then handles it.
Of course, Push is not reliable sometimes, E.g, PD pushes an operator but the leader is changed to other TiKV, so we still need the origin heartbeat feature.

Fixed by #669.


fix(entropy)!: use enum for resource status and change UpdateResourceRequest to include only urn and configs.

BREAKING CHANGE:

make Resource.status an enum type.
Remove resource from UpdateResourceRequest and add urn and configs only.

Breaking CI workflows can be ignored as the commit includes breaking changes on recently merged protobuf definition.


Connections persist when switching active databases

When I right click a different database and "set active", I look in pg_stat_activity and I can see that I have two connections, one to the newly active database and also the database I came from (no longer active). I'd expect that the old connection would be dropped.
System information:

Windows 7 Professional - SP1
DBeaver 6.2.2

Connection specification:

PostgreSQL 9.4
postgresql-42.1.4.jar
localhost connection

Steps to reproduce

Connect to connection (db1)
SELECT * FROM pg_stat_activity (shows one connection, correct)
Set db2 as active database
SELECT * FROM pg_stat_activity (shows two connections, incorrect)

Unfortunately it is not that easy.
Old connection still may be needed (e.g. to read database metadata when you browse database navigator tree).
We can add new option, something like "shutdown old database on activate database change". It will disconnect and collapse database navigator elements.
WDYT?

I have my connection setup to use only one connection (shared between tabs, and to read the metadata). If you feel it needs an extra option, I'd personally expect that as default behavior but as long as it works then I don't mind having another setting.

the same is true hive

It is PG-driver specific behavior. PostgreSQL needs separate physical connection to each database.

I don't see how we can fix this.
We can't just drop previous connection.
Changing "Active" database doesn't mean that previous database is not needed - it still may be used by SQL editor(s) or open metadata object editors or some background database tasks.
Perhaps we can implement some sort of "connection garbage collection" but it won't be easy to implement.
Workaround: do Disconnect to close all extra connections or use separate dbeaver connection for each PG database.


vscode: Warning: 'ozone-platform-hint' is not in the list of known options, but still passed to Electron/Chromium.

Describe the bug
I am using Gnome Wayland. I am trying to run code in the console and get the following warnings:
➜  ~ code
Warning: 'ozone-platform-hint' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.

By the way, I cannot use input method (fcitx5-rime) on Chromium or most Electron apps (including vscode) after some upgrades. Not sure if it is related or I need to open a new issue to report it.
Steps To Reproduce
Steps to reproduce the behavior:

Run vscode with code in the console
observe the warnings

Expected behavior

No warnings
Input method (fcitx5) is functional in vscode

Notify maintainers
@eadwu
@Synthetica9
@amaxine
@bobby285271
@Enzime
@poscat0x04
Metadata
➜  ~ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.2, NixOS, 24.05 (Uakari), 24.05.20231129.e92039b`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - nixpkgs: `/nix/store/mdl8yp9lzzzjla69qm42sk96p15vym7d-source`

Priorities
Add a :+1: reaction to issues you find important.

unfortunately, the answer is to stop using ozone wayland, i.e. remove the envvar NIXOS_OZONE_WL from your config

also, this is fine, it's not bad

@pearsche ?

I should've been clear. Those warnings are not negative. They just warn the user because they're not a default setting. Just telling the OP in case they didn't know.

unfortunately, the answer is to stop using ozone wayland, i.e. remove the envvar NIXOS_OZONE_WL from your config

@eclairevoyant Thanks! It works! I will close the issue.

Glad to help. More context about this behaviour is explained in https://github.com/NixOS/nixpkgs/pull/262343.

oh wow, sorry, didn't see...

https://github.com/microsoft/vscode/pull/135191
There is no way to catch the warning on the Electron app side, according to a VSC dev.
Luckily support for a global env var for all electron apps was added in https://github.com/electron/electron/pull/39792

It is worth noting that IME works with NIXOS_OZONE_WL on, though running code from terminal still gives
➜  ~ code
Warning: 'ozone-platform-hint' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'enable-wayland-ime' is not in the list of known options, but still passed to Electron/Chromium.


Remove Scratchpad and Worker folders.

Summary
In order to remove the amount of unused code, we are removing the Scratchpad and the Sdk\Worker code folders.
No other changes.
Related work items

https://github.com/temporalio/sdk-dotnet/issues/32

Details
We continue to use manual validation for the functionality.
Automated unit and integration testing is getting ever closer, but we still need to implement a few bits and pieces to provide this effectively. In particular, integration testing will be easier to implement once serialization functionality is complete.
Note: This change contains everything in https://github.com/temporalio/sdk-dotnet/pull/28 and https://github.com/temporalio/sdk-dotnet/pull/31 plus the actual changes.
I'll mark this as draft until https://github.com/temporalio/sdk-dotnet/pull/28 & https://github.com/temporalio/sdk-dotnet/pull/31 are merged, and the delta is reduced for an easier review.

I just realized much of this is also at #31. I may end up copying my comments there for visibility.


Remove unused pressure at cell faces

This PR removes pressure at cell faces, since it's no longer used. In this PR, density at the surface is extrapolated from the prognostic density, instead of computed using CA.compute_ref_density!
This turns out to be non-behavior changing

bors r+


KAFKA-7223: add unit tests in preparation for suppression

This is Part 2 of suppression.
Part 1 was https://github.com/apache/kafka/pull/5567
In an effort to control the scope of the review, I'm sending this PR with just the unit tests for buffered suppression.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@guozhangwang @bbejeck ,
When you have a chance please take a look at this PR.
As the description says, it contains only the unit tests that we will use for buffered suppressions.
Clearly, since it's not implemented yet, the tests can't all pass, so you'll notice that many have been configured to expect exceptions. This expectation will be removed when I add the implementation.
I'm hoping that this progression is more reviewable than one large chunk, and also that it makes sense in its resemblence to TDD. I'd like to think of this as writing/reviewing the tests first, so we agree on the expected behavior. With that agreement in place, we'll be able to concentrate on the implementation in a follow-on PR.
WDYT?

@guozhangwang , thanks for the review. I think I've addressed all your comments.
About the punctuation overhead, I share your concern, and I think we can optimize it, but I agree we should table this discussion until part 3.

@vvcephei Thanks for your replies. I do not have further comments. And once @bbejeck is happy with the current patch we can merge it.

Ok @bbejeck, I believe I've addressed all your and @guozhangwang 's comments.
Do you mind making a final pass?

Once again, my sincere thanks for the reviews, @guozhangwang and @bbejeck


Refractor

This PR tracks the refractoring of the first version of the server (also in preparation of the second version).
This should remove duplicated code and improve the readability, without introducing new features or fixing anything else.

This could already be reviewed, it does not change anything but the file and class structure.
In the end, a summary of the changes is:

the big file that  was in main has been splitted in one dedicated to the server (so the TCPhandler and the main function) and in one dedicated only to qickprograms definition
in qickprogram, now there is a GeneralQickProgram abstract class that is used to initialize both ExecutePulseSequence and ExecuteSingleSweep. This has removed a lot of duplication since the majority of the functions are the same.
Some large functions (like initialize) have been splitted to improve the readability

The documentation was updated and the coverage is not decreasing (obviously, there are no tests in main for now, I will need to update the tests-PR)

Two comments about the if __name__ == "__main__"::

it is better if you encapsulate the content in a main() function, since in this way it would also be possible to test
the actual execution makes your package an application, but it is rather weird if you then deploy it as a package: how would you run after installing with pip install qibosoq? (solution python /path/to/env/lib/python3.x/site-packages/qibosoq/rfsoc_server.py... not the best...)

Point 2. has an actual standard solution in Python: a __main__.py file inside your package. Same question: how would you run this after package installation? Solution: python -m qibosoq, much more convenient :)
I'm writing here to you since you're refactoring, but it is fine to keep this for a further PR. In case, just open a dedicated issue.

Thank you @AleCandido for the suggestions, I will open a new issue for the second point and solve the first here

Btw, you have a consistent and interesting typo: refractor

Have a look at comments on #15

Thanks @AleCandido for the comments, everything should be corrected now. I had copied the main part of the code from  qiboteam/workflows, maybe some of these problems can also be corrected there?

For the failing pylint and the inheritance chain, maybe its better if I explain a bit more... I don't think I'm able to solve this on my own, but it does not seem impossible.
Eventually I want to have this structure:

class GeneralQickProgram(ABC, QickProgram):
  def __init__ (...):
    ...
    super().__init__(...)  # here it should call AveragerProgram/RAveragerProgram init

 def acquire (...):
    ...
    super().acquire(...)  # here it should call AveragerProgram/RAveragerProgram acquire

class ExecutePulseSequence(GeneralQickProgram, AveragerProgram):
  ...

class ExecuteSingleSweep(GeneralQickProgram, RAveragerProgram):
  ...

if I just add the QickProgram inheritance, however, the super().__init__ calls the QickProgram init and same thing for acquire.
Also, pylint complains since the GeneralQickProgram does not know some of the attributes used just by the sweeper class and defined in its init... should I define them in GeneralQickProgram as None or is there a better way?

Actually is just a pylint problem... it sees the super init and acquire as the ones of QickProgram, but these have different numbers of parameters so it raises an error.
I could just skip these lines in pylint (at least I could see the pylint output), but it's probably not the best idea ever

I would like to merge this PR: this has already been reviewed and I think it's kinda ok. Also it's a bit easier to have it on main since every new PR had to start from here.
I will open a specific issue for the global soc problem


ci(build): action add macos

 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.