docs: update content source comment(also docs)

Since plain has been marked as deprecated and replaced by inline,  the comment should be updated (which also affects the documentation) to avoid confusion.
https://unocss.dev/config/#content

✅ Deploy Preview for unocss ready!
Built without sensitive environment variables
Name	Link
🔨 Latest commit	496ba26
🔍 Latest deploy log	https://app.netlify.com/sites/unocss/deploys/659b6a6779ca9100080410b9
😎 Deploy Preview	https://deploy-preview-3497--unocss.netlify.app
📱 Preview on mobile
Toggle QR Code...
To edit notification comments on pull requests, go to your Netlify site configuration.

The documents on the preview here seem to have not been updated, is there something wrong?


[XLA] Add a scheme for disabling tests based on type support by backends

This change allows CPP tests to be marked as requiring certain type support.  As it stands, I have updated only the scalar math test with the annotations.  I will do the rest once this change is debated.
The plugin config has something like this added to the 'copts' option:
    "copts": [
      "-DXLA_TEST_DISABLE_F64",
    ],

Can one of the admins verify this patch?

after discussion on the xla dev forum, cancelling this.


Request: Add Table Support

Could you add table support (https://tiptap.scrumpy.io/tables) at some point?

Was was trying to add this just now and submit a PR, however the dependency on that pro font-awesome icons is overkill.... I would suggest getting ride of it and using some free ones. however I still would like this feature.. seems pretty straight forward to implement... any chance of an update @manogi ?

@milewski You are right - tbh this is my first real open source contribution and I did not think about other contributors having to add font awesome pro. I will remove that dependency in my next update. Trying to do that today, don't know if I can finish it.

I have removed the dependency now in the new release 0.3.2.

It is true that the table support seems straightforward - I will give it a shot myself, and if I don't succeed I will get back to you, @milewski

Am pretty far with adding table support.
Had to fix a bug introduced in the 0.3.2 release though - it is fixed in 0.3.3.
Now I just need some icons to use for all those table buttons ("add row below", "add row above" etc.).

@manogi - Wordpress' Gutenberg uses Material Icons, which has a TON of options and you should be able to find some good ones. https://material.io/tools/icons/?style=baseline
There's an icon font and SVGs available, whichever works better with the project.

@manogi - any word on this? I'd really like to switch to this editor but currently table support is buggy (it won't let me add the "resizeable = true" part, and trying to edit tables is just very jumpy and i don't get all the row and column buttons properly.

Hey @manogi has this project been abandoned? thank you

Not really abandoned, but I don't find any time next to customer work atm. This is an open source projects - PRs are welcome. I hope I find the time to get back to this project in the nearer future.

finally found the time to include table support (in v1.1.0):


[applications] Display badges for env and app empty data

:nut_and_bolt: Description
Integrate the new badges inside the service-group table, use them to display/represent no data for environment and applications fields.
NOTE: This change doesn't include the link inside the tooltips since we currently can't.
This change will be covered with https://github.com/chef/automate/issues/473
:+1: Definition of Done
In table rows, when there is no data for the app or env columns, display NO APP and NO ENV using the badge component shown in the mockup, with the tooltip during mouse hover and keyboard focus state:

Add application data. Learn more in Configuring the Habitat Supervisor.
Add environment data. Learn more in Configuring the Habitat Supervisor.

App no-data

Env no-data

(EXTRA) Channel no-data

:athletic_shoe: Demo Script / Repro Steps

Build and start the automate-ui component.
Populate the applications database and navigate to the Applications Tab.

:chains: Related Resources
Jira: https://chefio.atlassian.net/browse/A2-823
Closes: https://github.com/chef/automate/issues/471
:white_check_mark: Checklist

[ ] Necessary tests added/updated?
[ ] Necessary docs added/updated?
[x] Code actually executed?
[x] Vetting performed (unit tests, lint, etc.)?

Should we modify the applications_populate_database helper to include these cases?


Make explicit where Instructors can include accommodations they need when signing up for workshop

Addresses but does not close #2436.

@maneesha are you happy with this wording?


readme updates with samples

You have inserted an additional reference to HTML5 Rocks that should be removed.
The HTML5 Rocks web page contains incorrect examples and currently throws an error (at the end).


Automatically Create Draft Gmail Replies To Form Responses

Solution title: Automatically Create Draft Gmail Replies To Form Responses
One sentence summary: Use Apps Script to quickly create draft email replies to Google Form Responses.
Description (1 - 2 paragraphs):
Quickly respond to large volumes of Form Responses by having Apps Script generate draft email replies ready for sending. The draft replies include the form responses, which can be reviewed inside the email. A generic thank you message is created and additional personal feedback can be added before hitting send.
Design Details:
Form submit trigger runs function that creates a draft email in Gmail with the Form Response data included.

Sounds great! Approved. You can get started with our template directory: https://github.com/gsuitedevs/solutions/tree/master/template for your implementation

Completed here:
https://github.com/gsuitedevs/solutions/tree/master/course-feedback-response


[Serialization] Load swiftmodule files as volatile to avoid mmap

Avoid mmaping swiftmodule files to hopefully fix issues seen when building Swift projects in parallel on NFS. This change only affects loading ModuleFile, it doesn't affect scanning swiftmodule for dependencies which are still handled as non-volatile.
Let's try always avoid mmap at first to confirm if this was the issue. However, this will likely affect memory usage so we may need a way to restrict this further if it causes issues on memory-constrained systems.

@swift-ci Please smoke test

@swift-ci Please smoke test

Could you elaborate more about what kind of issues in parallel building could potentially be resolved by avoiding mmaping swiftmodule file?

Right, I believe the issue here is that swiftmodule files are being changed by a different process while they are mmaped. The precise behavior of mmap when the underlying file changes is unspecified AFAICT. This setting in LLVM mentions specifically issues on NFS and it could be an important factor here as we don't see this issue on engineers' desks.
And in practice, there may be three scenarios where the swiftmodule files can change while it's being read:

For a framework without installapi, a client could be using the baseline swiftmodule while the framework replaces it on disk if there is a missing dependency edge.
For a framework with installapi, if the framework reinstalls a swiftmodule in the install phase while a client is reading the one from the installapi phase.
When lock files are unavailable because of a read-only file system and many processes rebuild the same module interface at once. I would have expected this one to be safe but we often see this error after rebuilds and failed locks.

This would explain failures that show up as deserialization errors without an explanation which indicates that it's a memory consistency issue: (An expected deserialization error would have an explanation between those two lines.)
*** DESERIALIZATION FAILURE (please include this section in any bug report) ***
(see "While..." info below)

And low-level failures in LLVM bitstream code, and segfaults when using values from the swiftmodule files for index access.

OK. Though I'm not entirely convinced using mmap really caused these deserialization errors, it's worth experimenting by landing this change. Could you add the rationals as comments and file a radar to revert this change if similar deserialization errors still happen?

@swift-ci Please smoke test

@nkcsgexi Done!


Unable to consume AI Provider using Bearer Token as authentication method.

What are you trying to achieve?
Consume AI provider through Bearer token as authentication method instead of API_KEY.
What do you get instead?

Access denied error since the AI provider was set to just allow authentication through Bearer token instead of API_KEY.

Provide test source code if related

Not Applied

Details

CodeceptJS version: 3.6.3
NodeJS Version: 14.21.1
Operating System: MacOS
Configuration file: N.A.

Interesting! Could you please give us more info regarding the AI section in Codeceptjs conf? That'll help us understand more the context.

Sure thing

Hi @kobenguyent , I tried to use your suggestion on both ways but I'm getting different error messages:
    request: async (messages) => {
     // Using @azure/openai library
      const AzureOpenAI = require("@azure/openai");
      const azureADTokenProvider = {
        token_type: "Bearer",
        expires_in: 9999,
        ext_expires_in: 9999,
        access_token: "MY_ACCESS_TOKEN"
      };
      const deployment = "MY_DEPLOYMENT_NAME";
      const apiVersion = "2024-04-01-preview";
      const client = new AzureOpenAI({ azureADTokenProvider, deployment, apiVersion });
      const result = await client.chat.completions.create({
        messages,
        model: 'gpt-3.5-turbo', // your preferred model
      });
      return result.choices[0]?.message?.content;
    },

But the error I was getting is the following:
⠋ Processing AI request...
AI service error: AzureOpenAI is not a constructor

Then I switch the library to "openai" but getting a different error:
    request: async (messages) => {
      const AzureOpenAI = require("openai");
      const azureADTokenProvider = {
        token_type: "Bearer",
        expires_in: 9999,
        ext_expires_in: 9999,
        access_token: "MY_ACCESS_TOKEN"
      };
      const deployment = "MY_DEPLOYMENT_NAME";
      const apiVersion = "2024-04-01-preview";
      const client = new AzureOpenAI({ azureADTokenProvider, deployment, apiVersion });
      const result = await client.chat.completions.create({
        messages,
        model: 'gpt-3.5-turbo', // your preferred model
      });
      return result.choices[0]?.message?.content;
    },

The new error to be received is the following:
⠋ Processing AI request...
AI service error: The OPENAI_API_KEY environment variable is missing or empty; either provide it, or instantiate the OpenAI client with an apiKey option, like new OpenAI({ apiKey: 'My API Key' }).

@kobenguyent , sorry for the delay, I tried to follow the provided advices, however I'm still getting stuck with the same error, token is retrieved successfully, however at the moment I try to use AI it is requiring me an API-KEY


install ansible via pip. pin version to <IP_ADDRESS>

rebased and merged dac1ca7c35e48f702a6fab629a7ff1728d9b1445


make create or make create-project?

Based on the documentation (PROJECT-EXISTING.md, PROJECT-NEOS.md, PROJECT-SYMFONY.md, PROJECT-TYPO3.md) the Makefile task should be make create-project, not make create (https://github.com/mblaschke/TYPO3-docker-boilerplate/blob/develop/Makefile#L9).
Or is the documentation wrong?

Should be make create but I'm unsure if i should keep this feature. Makefile doesn't support parameters for tasks and I've added this feature with a hack.
But you can deploy your web projects into code/ directory. You don't have to use make create. Just git clone, svn co or cp your projects into code/ :)

Next version of this docker boilerplate will focus in TYPO3.
For any other PHP project I've created a fork without the TYPO3 stuff:
https://github.com/mblaschke/php-docker-boilerplate

Closed as it's no longer an issue


FramedRead only calls decode_eof when there is buffered data

This issue is related to the discussion in tokio-rs/tokio-core#178
Given the tokio-proto pattern of representing a body stream as Body(Option<Chunk>), an HTTP 1.1 Decoder would require decode_eof to be called even if there is no more data.
In the case of streaming bodies w/ Connection: close and no content length, the body stream is all the data until the socket is closed. This means that an HTTP 1.1 decoder would need to emit a Body(None) frame on EOF when there is no buffered data.

Yeah this was sort of the ... "easy" mode? Do we want it to support everything? Do you have an idea how to fix? (I don't)

It could be unconditionally called, but then it would require changing the return signature of decode_eof -> Result<Option<Item>> or something like that.

Perhaps yeah, but I'd be wary of how the meaning of None is then very different between decode and decode_eof.

I'm open to alternatives :)
Given that decode_eof has a default impl, I think it is OK to expand on
it a bit and still have framed be "easy mode"
On Thu, Mar 2, 2017 at 1:17 PM Alex Crichton<EMAIL_ADDRESS>wrote:

Perhaps yeah, but I'd be wary of how the meaning of None is then very
different between decode and decode_eof.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alexcrichton/tokio-io/issues/7#issuecomment-283784435,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAYJLyJ-A_tLG85-iGwiph8dm7sOJKnks5rhzHcgaJpZM4MQhGk
.

It's true yeah being a default method could help quite a bit here. That means most will never implement the method itself.
Perhaps we could try itout and see how it goes? (I can't think of any other alternatives myself)

It could be unconditionally called, but then it would require changing the return signature of decode_eof -> Result<Option> or something like that.

This was the approach that I introduced in #1, motivated purely by it seeming much more obvious to me. It was reverted in cddbdb349cc597b2ab378f3ae26ebeeb7747ecab.

As mentioned in the original PR. The change to generic errors was not
rejected, but the API change should be made & discussed in isolation in a
PR. That makes it easier to evaluate + leaves a discussion that can be
linked to in the future when people ask questions.
It was my fault for including the change in the PR. I mostly just adapted
#1 without looking at master.
On Thu, Mar 2, 2017 at 5:32 PM Benjamin Saunders<EMAIL_ADDRESS>wrote:

It could be unconditionally called, but then it would require changing the
return signature of decode_eof -> Result or something like that.
This was the approach that I introduced in #1
https://github.com/alexcrichton/tokio-io/pull/1, motivated purely by it
seeming much more obvious to me. It was reverted in cddbdb3
https://github.com/alexcrichton/tokio-io/commit/cddbdb349cc597b2ab378f3ae26ebeeb7747ecab
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alexcrichton/tokio-io/issues/7#issuecomment-283838358,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAYJFP-HZEmkG7h1ejFHunBn3qs0p7iks5rh22ngaJpZM4MQhGk
.

To be clear, I was referring to the EOF handling, not generic errors (which are offtopic in this PR).


move simulator-server go module to another one directory

Currently, we have one go module in root dir.
https://github.com/kubernetes-sigs/kube-scheduler-simulator/blob/master/go.mod
And, we need to create other go modules for these KEPs.
https://github.com/kubernetes-sigs/kube-scheduler-simulator/tree/master/keps/140-scenario-based-simulation
https://github.com/kubernetes-sigs/kube-scheduler-simulator/tree/master/keps/159-scheduler-simulator-operator
https://github.com/kubernetes-sigs/kube-scheduler-simulator/tree/master/keps/184-scheduler-simulation
I would propose to put only dirs for each go module (+ simulator-web) in root dir like:
├── simulator-server/
├── simulator-web/
├── scheduler-simulation/
├── simulator-operator/
├── README.md, etc (other docs can be placed in root dir)

/assign
/priority important-soon
/kind cleanup

Also, need to change prow-job
https://github.com/kubernetes/test-infra/tree/master/config/jobs/kubernetes-sigs/kube-scheduler-simulator


Fliteration removing 90% of the data

The code in /src/common/objects/dataset.py removes documents if the TFIDF value is lower than 75%. This is removing almost 90% of the data that might be useful otherwise.

Just comment this line:
Line 37 in  /src/common/objects/dataset.py
# self.filter_rules.append((Constants.FILTER_RULE_ANY, Constants.FILTER_RULE_ANY, Constants.FILTER_RULE_ANY, (Constants.FILTER_TFIDF_REMOVE, Constants.FILTER_TFIDF_LOWER, 75.0)))


[React] Apply blank scroll view fix to 0.34.1

https://github.com/facebook/react-native/issues/8607#issuecomment-249530803
Fixes #1961

I’ve reviewed the code of the patch, I see no obvious problems, so going to do a release.


Scrollbar zindex

I have a scrollbar (overflow-y) on an element, when I open a modal, the scrollbar is still here and overlap modal.

Bug fixed !


Update Windows Installer instructions

We now have a windows installer for yotta, updating instructions appropriately.
Got rid of get_yotta.py and manual install because we really dont want them doing that.

Do we have any guide for users who like to set up manually, if this PR gets accepted?

Nope, there isn't one for Mac or linux, so don't see why its necessary for
windows
On Fri, Sep 25, 2015, 1:39 AM Martin Kojtal<EMAIL_ADDRESS>wrote:

Do we have any guide for users who like to set up manually, if this PR
gets accepted?
—
Reply to this email directly or view it on GitHub
https://github.com/ARMmbed/yotta/pull/431#issuecomment-143142224.

Fixed, should work now. Nice catch!

I'm nervous about completely removing the manual installation instructions, especially until the installer is widely tested (despite what you say for Mac and Linux the full list of dependencies is visible to people in the instructions).

Im more nervous about leaving them in and having people have a terrible time trying to install yotta on windows. If you really want the manual way to be there then I'll add it back.

I think that's best for now – we can definitely recommend the installer, list it first, etc.
Also, it seems like https://github.com/ARMmbed/yotta_windows_installer/releases isn't public yet?


Add types skeleton of coin selection and largestFirst algo implementation

Issue Number

#92
Overview

[x] I have added coin selection proposal for coin selection and fee calculation

Comments

just rebased to update the branch with master


detection opencl platform problem

Hello,
I have the error message
Initializing...failed to get Device IDs: -1
I have two nvidia card and i believe the error is due to this :
http://stackoverflow.com/questions/24200539/cant-get-my-graphics-card-device-in-opencl
The code in this miner is :
// Get Platform/Device Information
ret = clGetPlatformIDs(1, &platform_id, &ret_num_platforms);
if (ret != CL_SUCCESS) { printf("failed to get platform IDs: %d\n", ret); exit(1); }
ret = clGetDeviceIDs(platform_id, CL_DEVICE_TYPE_GPU, 1, &device_id, &ret_num_devices);
if (ret != CL_SUCCESS) { printf("failed to get Device IDs: %d\n", ret); exit(1); }
If I read correctly, this means the opencl platform is supposed to be 1, but it can be another number.
according to the :
for(int i=0; i<num_of_platforms; i++)
if(clGetDeviceIDs(&platform_id, CL_DEVICE_TYPE_GPU, 1, &device_id, &num_of_devices) == CL_SUCCESS){

I made my comment too quickly and I don't know how to edit it.
Obviously I was wrong, the code above doesn't suppose the platform id is 1 but try to find the id. I suppose the call clGetPlatformIDs doesn't return the good platform id in my system.

The code on the wolfpr branch addresses this issue by allowing you to tell the program which platform id and device id you want it to use. We plan on adding support for running multiple GPUs in the same program, but for now you'll have to run two different instances of the program with different device flags.
The code will most likely be added to master tonight and a binary created soon after. Hope it fixes your problem!

when you close something, you should write a little closing message.
code to fix this problem is now in master


Unknown command: 'prune_presence'

After installing and configuring the plugin, it seems to have no problem adding values to the channels_presence_room and channels_presence_presence tables.
Also, setup a javascript to send a heartbeat.
This works, and updates the timestamp in the channels_presence_presence.
The problem is that the pruning doesn't seem to work.
I have setup the celery task, but i'm not sure it is ever being called as the values are never pruned from the DB.
I do use celery for many other tasks, so I know that my celery install is fine.
Also, I activated the enviroment and attempted to run
./manage.py prune_presence
This command fails.
Unknown command: 'prune_presence'
This command works:
./manage.py prune_rooms
but returns no results, and doesn't remove the room from the DB.
Also, one thing I just noticed is that the channel_name shows up as
daphne.response.AVmlqaOxtA!xfruPXOqRj
Not sure if that is expected.

Do you have "channels_presence" listed in INSTALLED_APPS in settings.py?  The management command not showing up sounds like a symptom of that.

I do. Also, this command doesn't error:
This command works:
./manage.py prune_rooms
It just doesn't do anything.
Do you know what values are supposed to be pushed into
channels_presence_presence table ?
Is this what I should expect to populate into the channel_name field of the table?
channel_name
daphne.response.KHuOGxrzrv!crPawQQxvK
The @touch_presence decorator does work and updated the timestamp in that table.
All seem to work, except for the pruning.

Ah, it's a docs problem; the management command is prune_presences (plural).
The channel_name field in Presence is populated with the connection's reply channel name, which is autogenerated by channels.  The value you listed looks right; though the details are up to channels and might change.

That explains why it wasn't working via manag.
I think I may have found out why it is not working via celery schedule or automatically though.
When running it manually via manag, I get this error:
./manage.py prune_presences
Traceback (most recent call last):
  File "./manage.py", line 22, in <module>
    execute_from_command_line(sys.argv)
  File "/opt/testsite/venv/lib/python3.5/site-packages/django/core/management/__init__.py", line 364, in execute_from_command_line
    utility.execute()
  File "/opt/testsite/venv/lib/python3.5/site-packages/django/core/management/__init__.py", line 356, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/opt/testsite/venv/lib/python3.5/site-packages/django/core/management/base.py", line 283, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/opt/testsite/venv/lib/python3.5/site-packages/django/core/management/base.py", line 330, in execute
    output = self.handle(*args, **options)
  File "/opt/testsite/venv/lib/python3.5/site-packages/channels_presence/management/commands/prune_presences.py", line 6, in handle
    Room.objects.prune_presences()
  File "/opt/testsite/venv/lib/python3.5/site-packages/channels_presence/models.py", line 56, in prune_presences
    room.prune_presences(age)
  File "/opt/testsite/venv/lib/python3.5/site-packages/channels_presence/models.py", line 105, in prune_presences
    last_seen__lt=now() - timedelta(seconds=age_in_seconds)
TypeError: unsupported type for timedelta seconds component: str

Okay. Got it to work.
It was the quotes around the Max Age var in settings:
CHANNELS_PRESENCE_MAX_AGE = "120"
to
CHANNELS_PRESENCE_MAX_AGE = 120
Thanks for the help troubleshooting!
Will give you a heads you if I notice any issues!

Did you set a CHANNELS_PRESENCE_MAX_AGE in settings.py to a string value?


Contributing CI docs tidying

Removes Figure from consortium page and tidies intro page to make it version neutral so we don't have to keep updating it.
N.B. merge job is still waiting on Roger updating the C++ jobs on the release builds page so isn't expected to be made green by this PR.
--no-rebase

:+1: Ready to merge once Travis is green


updateHostsFile.py: add new ipv6 variants

Based on someonewhocares.org hosts schema

@FadeMind I have been looking for justification for adding this.
Today, when Googling ip6-allrouters (and some others) this PR comes up in the top-10 when searching from here in Canada.
Is this in Ubuntu 18.04?

See screenshots from site
https://www.webhosting.uk.com/kb/how-to-update-hosts-file-entry-on-windows-ubuntu-and-mac/

Ok.  Let's do this.
Merging.  Thanks Tomasz @FadeMind.


Update embedded-hal 1.0.0-alpha.6

I updated the embedded-hal to 1.0.0-alpha.6.
This should fix errors in the latest commit.

Well done! The code finished now adapts to embedded-hal traits well.


No wheel

Hi. When a winner is drawn I can see no wheel that spins and shows wich wins. It just picks a winner "in the dark". Is this an error or isnt a wheel included in the code?? :(
Best regards, optiix.

I think its not implemented. Idk for what the sound-file is too.

Aha. Okey =(


Trying to read a huge file

Hi all,
I am trying to read a huge file (2.5 gigabyte) file, but it allways ends up with: "Unhandled Exception: System.IO.IOException: Maximum capacity exceeded" and the Ram is allways around 100% taken.  What I am doing wrong?
           `int blockSize = 10;
            int largeBufferMultiple = 1024 * 1024;
            int maxBufferSize = 16 * largeBufferMultiple;

            var manager = new RecyclableMemoryStreamManager(blockSize,
                                                            largeBufferMultiple,
                                                            maxBufferSize);

            manager.GenerateCallStacks = true;
            manager.AggressiveBufferReturn = true;
            manager.MaximumFreeLargePoolBytes = maxBufferSize * 4;
            manager.MaximumFreeSmallPoolBytes = 100 * blockSize;
            RecyclableMemoryStream memoryStream = new RecyclableMemoryStream(manager);
            using (FileStream fileStream = File.OpenRead(@"C:\Temp\test.bin"))
            {

                // MemoryStream memoryStream = new MemoryStream();
                fileStream.CopyTo((memoryStream);`

What  I am doing wrong?
You are reading huge file into memory.

First of all it's not a case for this library
Secondly, why do you need whole file in memory? Either read in in chunks or use memory-mapped file api.


Incorrect sizing when paper-carousel inside iron-pages

paper-carousel is incorrectly sized when placed inside an iron-pages element. It seems that _setContainerSize() calculates min-width to be 0px during page load. Resizing the page or changing pages results in correct sizing.
See https://nathanandjorja.ca/gallery for an example.

Hi @nloewen,
We let's review it, in the meantime you can use refresh() method after page load for recalculate sizing.

Calling refresh() in the attached callback doesn't change the behaviour. I've worked around this by calling refresh() in the onload callback for the img elements inside the carousel.

Hi @nloewen ,
We just update the component. Could you try again?
If you keep having the same problem, write us again.
Thank you

It's fixed. Thanks!


python3Packages.nunavut: fix build

Motivation for this change
Fix build
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages 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/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

4 packages built:

python38Packages.nunavut
python38Packages.pyuavcan
python39Packages.nunavut
python39Packages.pyuavcan


CSV Export doesn't handle double quotes

Currently if there's a double quote in a string during CSV export the text creates new unwanted cell breaks.  To fix, just need to replace line 45 of packages/react-boostrap-table2-toolkit/src/scv/exporter.js with return "${cellContent}".replace(/"/g, '""');
Thanks!

@CaptainCthulhu sorry for lately reply, thanks for your information and I will fix it by this week

@CaptainCthulhu  we fixed this issue, CHANGELOG
Please upgrade the packages which listed above to get newest patch, thanks


Bitcoin Core 27.0

Blog post, release notes, and RPC docs for 27.0. Also updates the maintenance table.

ACK d5102c587e87da18a8a4a58df5c82cc6363b1748
The RPC doc change amounts to:
diff -durN _doc/en/26.0.0/rpc/blockchain/dumptxoutset.html _doc/en/27.0.0/rpc/blockchain/dumptxoutset.html
--- _doc/en/26.0.0/rpc/blockchain/dumptxoutset.html	2024-04-17 06:31:41.355251702 +0200
+++ _doc/en/27.0.0/rpc/blockchain/dumptxoutset.html	2024-04-17 06:28:00.449564968 +0200
@@ -5,7 +5,7 @@

 dumptxoutset "path"

-Write the serialized UTXO set to disk.
+Write the serialized UTXO set to a file.

 Arguments:
 1. path    (string, required) Path to the output file. If relative, will be prefixed by datadir.
diff -durN _doc/en/26.0.0/rpc/blockchain/loadtxoutset.html _doc/en/27.0.0/rpc/blockchain/loadtxoutset.html
--- _doc/en/26.0.0/rpc/blockchain/loadtxoutset.html	2024-04-17 06:31:41.331251953 +0200
+++ _doc/en/27.0.0/rpc/blockchain/loadtxoutset.html	2024-04-17 06:28:00.417565302 +0200
@@ -5,7 +5,7 @@

 loadtxoutset "path"

-Load the serialized UTXO set from disk.
+Load the serialized UTXO set from a file.
 Once this snapshot is loaded, its contents will be deserialized into a second chainstate data structure, which is then used to sync to the network's tip. Meanwhile, the original chainstate will complete the initial block download process in the background, eventually validating up to the block that the snapshot is based upon.

 The result is a usable bitcoind instance that is current with the network tip in a matter of minutes rather than hours. UTXO snapshot are typically obtained from third-party sources (HTTP, torrent, etc.) which is reasonable since their contents are always checked by hash.
diff -durN _doc/en/26.0.0/rpc/blockchain/scanblocks.html _doc/en/27.0.0/rpc/blockchain/scanblocks.html
--- _doc/en/26.0.0/rpc/blockchain/scanblocks.html	2024-04-17 06:31:41.355251702 +0200
+++ _doc/en/27.0.0/rpc/blockchain/scanblocks.html	2024-04-17 06:28:00.449564968 +0200
@@ -9,27 +9,27 @@
 This call may take several minutes. Make sure to use no RPC timeout (bitcoin-cli -rpcclienttimeout=0)

 Arguments:
-1. action                                 (string, required) The action to execute
-                                          "start" for starting a scan
-                                          "abort" for aborting the current scan (returns true when abort was successful)
-                                          "status" for progress report (in %) of the current scan
-2. scanobjects                            (json array, optional) Array of scan objects. Required for "start" action
-                                          Every scan object is either a string descriptor or an object:
+1. action                        (string, required) The action to execute
+                                 "start" for starting a scan
+                                 "abort" for aborting the current scan (returns true when abort was successful)
+                                 "status" for progress report (in %) of the current scan
+2. scanobjects                   (json array, optional) Array of scan objects. Required for "start" action
+                                 Every scan object is either a string descriptor or an object:
      [
-       "descriptor",                      (string) An output descriptor
-       {                                  (json object) An object with output descriptor and metadata
-         "desc": "str",                   (string, required) An output descriptor
-         "range": n or [n,n],             (numeric or array, optional, default=1000) The range of HD chain indexes to explore (either end or [begin,end])
+       "descriptor",             (string) An output descriptor
+       {                         (json object) An object with output descriptor and metadata
+         "desc": "str",          (string, required) An output descriptor
+         "range": n or [n,n],    (numeric or array, optional, default=1000) The range of HD chain indexes to explore (either end or [begin,end])
        },
        ...
      ]
-3. start_height                           (numeric, optional, default=0) Height to start to scan from
-4. stop_height                            (numeric, optional, default=chain tip) Height to stop to scan
-5. filtertype                             (string, optional, default="basic") The type name of the filter
-6. options                                (json object, optional)
-     {
-       "filter_false_positives": bool,    (boolean, optional, default=false) Filter false positives (slower and may fail on pruned nodes). Otherwise they may occur at a rate of 1/M
-     }
+3. start_height                  (numeric, optional, default=0) Height to start to scan from
+4. stop_height                   (numeric, optional, default=chain tip) Height to stop to scan
+5. filtertype                    (string, optional, default="basic") The type name of the filter
+6. options                       (json object, optional) Options object that can be used to pass named arguments, listed below.
+
+Named Arguments:
+filter_false_positives    (boolean, optional, default=false) Filter false positives (slower and may fail on pruned nodes). Otherwise they may occur at a rate of 1/M

 Result (when action=='status' and no scan is in progress - possibly already completed):
 null    (json null)
diff -durN _doc/en/26.0.0/rpc/control/logging.html _doc/en/27.0.0/rpc/control/logging.html
--- _doc/en/26.0.0/rpc/control/logging.html	2024-04-17 06:31:41.403251199 +0200
+++ _doc/en/27.0.0/rpc/control/logging.html	2024-04-17 06:28:00.465564801 +0200
@@ -10,7 +10,7 @@
 When called with arguments, adds or removes categories from debug logging and return the lists above.
 The arguments are evaluated in order "include", "exclude".
 If an item is both included and excluded, it will thus end up being excluded.
-The valid logging categories are: addrman, bench, blockstorage, cmpctblock, coindb, estimatefee, http, i2p, ipc, leveldb, libevent, mempool, mempoolrej, net, proxy, prune, qt, rand, reindex, rpc, scan, selectcoins, tor, txpackages, txreconciliation, util, validation, walletdb, zmq
+The valid logging categories are: addrman, bench, blockstorage, cmpctblock, coindb, estimatefee, http, i2p, ipc, leveldb, libevent, lock, mempool, mempoolrej, net, proxy, prune, qt, rand, reindex, rpc, scan, selectcoins, tor, txpackages, txreconciliation, util, validation, walletdb, zmq
 In addition, the following are available as category names with special meanings:
   - "all",  "1" : represent all logging categories.
   - "none", "0" : even if other logging categories are specified, ignore all of them.
diff -durN _doc/en/26.0.0/rpc/mining/getnetworkhashps.html _doc/en/27.0.0/rpc/mining/getnetworkhashps.html
--- _doc/en/26.0.0/rpc/mining/getnetworkhashps.html	2024-04-17 06:31:41.331251953 +0200
+++ _doc/en/27.0.0/rpc/mining/getnetworkhashps.html	2024-04-17 06:28:00.417565302 +0200
@@ -10,7 +10,7 @@
 Pass in [height] to estimate the network speed at the time when a certain block was found.

 Arguments:
-1. nblocks    (numeric, optional, default=120) The number of blocks, or -1 for blocks since last difficulty change.
+1. nblocks    (numeric, optional, default=120) The number of previous blocks to calculate estimate from, or -1 for blocks since last difficulty change.
 2. height     (numeric, optional, default=-1) To estimate at the time of the given height.

 Result:
diff -durN _doc/en/26.0.0/rpc/mining/getprioritisedtransactions.html _doc/en/27.0.0/rpc/mining/getprioritisedtransactions.html
--- _doc/en/26.0.0/rpc/mining/getprioritisedtransactions.html	2024-04-17 06:31:41.331251953 +0200
+++ _doc/en/27.0.0/rpc/mining/getprioritisedtransactions.html	2024-04-17 06:28:00.417565302 +0200
@@ -9,9 +9,10 @@

 Result:
 {                                 (json object) prioritisation keyed by txid
-  "txid" : {                      (json object)
+  "<transactionid>" : {           (json object)
     "fee_delta" : n,              (numeric) transaction fee delta in satoshis
-    "in_mempool" : true|false     (boolean) whether this transaction is currently in mempool
+    "in_mempool" : true|false,    (boolean) whether this transaction is currently in mempool
+    "modified_fee" : n            (numeric, optional) modified fee in satoshis. Only returned if in_mempool=true
   },
   ...
 }
diff -durN _doc/en/26.0.0/rpc/network/addnode.html _doc/en/27.0.0/rpc/network/addnode.html
--- _doc/en/26.0.0/rpc/network/addnode.html	2024-04-17 06:31:41.399251240 +0200
+++ _doc/en/27.0.0/rpc/network/addnode.html	2024-04-17 06:28:00.461564842 +0200
@@ -14,7 +14,7 @@
 Arguments:
 1. node           (string, required) The address of the peer to connect to
 2. command        (string, required) 'add' to add a node to the list, 'remove' to remove a node from the list, 'onetry' to try a connection to the node once
-3. v2transport    (boolean, optional, default=false) Attempt to connect using BIP324 v2 transport protocol (ignored for 'remove' command)
+3. v2transport    (boolean, optional, default=set by -v2transport) Attempt to connect using BIP324 v2 transport protocol (ignored for 'remove' command)

 Result:
 null    (json null)
diff -durN _doc/en/26.0.0/rpc/rawtransactions/sendrawtransaction.html _doc/en/27.0.0/rpc/rawtransactions/sendrawtransaction.html
--- _doc/en/26.0.0/rpc/rawtransactions/sendrawtransaction.html	2024-04-17 06:31:41.327251995 +0200
+++ _doc/en/27.0.0/rpc/rawtransactions/sendrawtransaction.html	2024-04-17 06:28:00.417565302 +0200
@@ -18,6 +18,7 @@
 Arguments:
 1. hexstring        (string, required) The hex string of the raw transaction
 2. maxfeerate       (numeric or string, optional, default="0.10") Reject transactions whose fee rate is higher than the specified value, expressed in BTC/kvB.
+                    Fee rates larger than 1BTC/kvB are rejected.
                     Set to 0 to accept any fee rate.
 3. maxburnamount    (numeric or string, optional, default="0.00") Reject transactions with provably unspendable outputs (e.g. 'datacarrier' outputs that use the OP_RETURN opcode) greater than the specified value, expressed in BTC.
                     If burning funds through unspendable outputs is desired, increase this value.
diff -durN _doc/en/26.0.0/rpc/rawtransactions/submitpackage.html _doc/en/27.0.0/rpc/rawtransactions/submitpackage.html
--- _doc/en/26.0.0/rpc/rawtransactions/submitpackage.html	2024-04-17 06:31:41.327251995 +0200
+++ _doc/en/27.0.0/rpc/rawtransactions/submitpackage.html	2024-04-17 06:28:00.413565345 +0200
@@ -7,7 +7,7 @@

 Submit a package of raw transactions (serialized, hex-encoded) to local node.
 The package must consist of a child with its parents, and none of the parents may depend on one another.
-The package will be validated according to consensus and mempool policy rules. If all transactions pass, they will be accepted to mempool.
+The package will be validated according to consensus and mempool policy rules. If any transaction passes, it will be accepted to mempool.
 This RPC is experimental and the interface may be unstable. Refer to doc/policy/packages.md for documentation on package policies.
 Warning: successful submission does not mean the transactions will propagate throughout the network.

@@ -20,19 +20,21 @@

 Result:
 {                                   (json object)
+  "package_msg" : "str",            (string) The transaction package result message. "success" indicates all transactions were accepted into or are already in the mempool.
   "tx-results" : {                  (json object) transaction results keyed by wtxid
     "wtxid" : {                     (json object) transaction wtxid
       "txid" : "hex",               (string) The transaction hash in hex
       "other-wtxid" : "hex",        (string, optional) The wtxid of a different transaction with the same txid but different witness found in the mempool. This means the submitted transaction was ignored.
-      "vsize" : n,                  (numeric) Virtual transaction size as defined in BIP 141.
-      "fees" : {                    (json object) Transaction fees
+      "vsize" : n,                  (numeric, optional) Sigops-adjusted virtual transaction size.
+      "fees" : {                    (json object, optional) Transaction fees
         "base" : n,                 (numeric) transaction fee in BTC
         "effective-feerate" : n,    (numeric, optional) if the transaction was not already in the mempool, the effective feerate in BTC per KvB. For example, the package feerate and/or feerate with modified fees from prioritisetransaction.
         "effective-includes" : [    (json array, optional) if effective-feerate is provided, the wtxids of the transactions whose fees and vsizes are included in effective-feerate.
           "hex",                    (string) transaction wtxid in hex
           ...
         ]
-      }
+      },
+      "error" : "str"               (string, optional) The transaction error string, if it was rejected by the mempool
     },
     ...
   },
diff -durN _doc/en/26.0.0/rpc/rawtransactions/testmempoolaccept.html _doc/en/27.0.0/rpc/rawtransactions/testmempoolaccept.html
--- _doc/en/26.0.0/rpc/rawtransactions/testmempoolaccept.html	2024-04-17 06:31:41.327251995 +0200
+++ _doc/en/27.0.0/rpc/rawtransactions/testmempoolaccept.html	2024-04-17 06:28:00.413565345 +0200
@@ -23,8 +23,9 @@
        "rawtx",    (string)
        ...
      ]
-2. maxfeerate      (numeric or string, optional, default="0.10") Reject transactions whose fee rate is higher than the specified value, expressed in BTC/kvB
-
+2. maxfeerate      (numeric or string, optional, default="0.10") Reject transactions whose fee rate is higher than the specified value, expressed in BTC/kvB.
+                   Fee rates larger than 1BTC/kvB are rejected.
+                   Set to 0 to accept any fee rate.

 Result:
 [                                 (json array) The result of the mempool acceptance test for each raw transaction in the input array.
diff -durN _doc/en/26.0.0/rpc/wallet/encryptwallet.html _doc/en/27.0.0/rpc/wallet/encryptwallet.html
--- _doc/en/26.0.0/rpc/wallet/encryptwallet.html	2024-04-17 06:31:41.395251283 +0200
+++ _doc/en/27.0.0/rpc/wallet/encryptwallet.html	2024-04-17 06:28:00.461564842 +0200
@@ -10,6 +10,10 @@
 will require the passphrase to be set prior the making these calls.
 Use the walletpassphrase call for this, and then walletlock call.
 If the wallet is already encrypted, use the walletpassphrasechange call.
+** IMPORTANT **
+For security reasons, the encryption process will generate a new HD seed, resulting
+in the creation of a fresh set of active descriptors. Therefore, it is crucial to
+securely back up the newly generated wallet file using the backupwallet RPC.

 Arguments:
 1. passphrase    (string, required) The pass phrase to encrypt the wallet with. It must be at least 1 character, but should be long.
diff -durN _doc/en/26.0.0/rpc/wallet/gettransaction.html _doc/en/27.0.0/rpc/wallet/gettransaction.html
--- _doc/en/26.0.0/rpc/wallet/gettransaction.html	2024-04-17 06:31:41.399251240 +0200
+++ _doc/en/27.0.0/rpc/wallet/gettransaction.html	2024-04-17 06:28:00.461564842 +0200
@@ -32,8 +32,8 @@
     "hex",                                 (string) The transaction id.
     ...
   ],
-  "replaced_by_txid" : "hex",              (string, optional) The txid if this tx was replaced.
-  "replaces_txid" : "hex",                 (string, optional) The txid if the tx replaces one.
+  "replaced_by_txid" : "hex",              (string, optional) Only if 'category' is 'send'. The txid if this tx was replaced.
+  "replaces_txid" : "hex",                 (string, optional) Only if 'category' is 'send'. The txid if this tx replaces another.
   "to" : "str",                            (string, optional) If a comment to is associated with the transaction.
   "time" : xxx,                            (numeric) The transaction time expressed in UNIX epoch time.
   "timereceived" : xxx,                    (numeric) The time received expressed in UNIX epoch time.
diff -durN _doc/en/26.0.0/rpc/wallet/getwalletinfo.html _doc/en/27.0.0/rpc/wallet/getwalletinfo.html
--- _doc/en/26.0.0/rpc/wallet/getwalletinfo.html	2024-04-17 06:31:41.359251659 +0200
+++ _doc/en/27.0.0/rpc/wallet/getwalletinfo.html	2024-04-17 06:28:00.453564925 +0200
@@ -31,6 +31,7 @@
   "descriptors" : true|false,             (boolean) whether this wallet uses descriptors for scriptPubKey management
   "external_signer" : true|false,         (boolean) whether this wallet is configured to use an external signer such as a hardware wallet
   "blank" : true|false,                   (boolean) Whether this wallet intentionally does not contain any keys, scripts, or descriptors
+  "birthtime" : xxx,                      (numeric, optional) The start time for blocks scanning. It could be modified by (re)importing any descriptor with an earlier timestamp.
   "lastprocessedblock" : {                (json object) hash and height of the block this information was generated on
     "hash" : "hex",                       (string) hash of the block this information was generated on
     "height" : n                          (numeric) height of the block this information was generated on
diff -durN _doc/en/26.0.0/rpc/wallet/listsinceblock.html _doc/en/27.0.0/rpc/wallet/listsinceblock.html
--- _doc/en/26.0.0/rpc/wallet/listsinceblock.html	2024-04-17 06:31:41.367251576 +0200
+++ _doc/en/27.0.0/rpc/wallet/listsinceblock.html	2024-04-17 06:28:00.457564884 +0200
@@ -52,8 +52,8 @@
         "hex",                             (string) The transaction id.
         ...
       ],
-      "replaced_by_txid" : "hex",          (string, optional) The txid if this tx was replaced.
-      "replaces_txid" : "hex",             (string, optional) The txid if the tx replaces one.
+      "replaced_by_txid" : "hex",          (string, optional) Only if 'category' is 'send'. The txid if this tx was replaced.
+      "replaces_txid" : "hex",             (string, optional) Only if 'category' is 'send'. The txid if this tx replaces another.
       "to" : "str",                        (string, optional) If a comment to is associated with the transaction.
       "time" : xxx,                        (numeric) The transaction time expressed in UNIX epoch time.
       "timereceived" : xxx,                (numeric) The time received expressed in UNIX epoch time.
diff -durN _doc/en/26.0.0/rpc/wallet/listtransactions.html _doc/en/27.0.0/rpc/wallet/listtransactions.html
--- _doc/en/26.0.0/rpc/wallet/listtransactions.html	2024-04-17 06:31:41.391251324 +0200
+++ _doc/en/27.0.0/rpc/wallet/listtransactions.html	2024-04-17 06:28:00.457564884 +0200
@@ -48,8 +48,8 @@
       "hex",                             (string) The transaction id.
       ...
     ],
-    "replaced_by_txid" : "hex",          (string, optional) The txid if this tx was replaced.
-    "replaces_txid" : "hex",             (string, optional) The txid if the tx replaces one.
+    "replaced_by_txid" : "hex",          (string, optional) Only if 'category' is 'send'. The txid if this tx was replaced.
+    "replaces_txid" : "hex",             (string, optional) Only if 'category' is 'send'. The txid if this tx replaces another.
     "to" : "str",                        (string, optional) If a comment to is associated with the transaction.
     "time" : xxx,                        (numeric) The transaction time expressed in UNIX epoch time.
     "timereceived" : xxx,                (numeric) The time received expressed in UNIX epoch time.
diff -durN _doc/en/26.0.0/rpc/wallet/migratewallet.html _doc/en/27.0.0/rpc/wallet/migratewallet.html
--- _doc/en/26.0.0/rpc/wallet/migratewallet.html	2024-04-17 06:31:41.387251367 +0200
+++ _doc/en/27.0.0/rpc/wallet/migratewallet.html	2024-04-17 06:28:00.457564884 +0200
@@ -5,8 +5,6 @@

 migratewallet ( "wallet_name" "passphrase" )

-EXPERIMENTAL warning: This call may not work as expected and may be changed in future releases
-
 Migrate the wallet to a descriptor wallet.
 A new wallet backup will need to be made.

@@ -15,6 +13,8 @@
 for this wallet. In the event of an incorrect migration, the backup can be restored using restorewallet.
 Encrypted wallets must have the passphrase provided as an argument to this call.

+This RPC may take a long time to complete. Increasing the RPC client timeout is recommended.
+
 Arguments:
 1. wallet_name    (string, optional, default=the wallet name from the RPC endpoint) The name of the wallet to migrate. If provided both here and in the RPC endpoint, the two must be identical.
 2. passphrase     (string, optional) The wallet passphrase


Advance throttling policy cannot be added with unit time for seconds via UI

Description:
When adding an advance throttling policy from admin dashboard, user cannot select unit time as second; But this can be done using admin rest api (see attached)
Suggested Labels:
APIM-2.2.0
Type/bug
Priority/highest
Severity/major
Affected Product Version:
2.1.0-update5
Steps to reproduce:

Enable advance throttling in api-manager.xml
Go to admin dashboard and create an advance throttling policy
Select unit time as second => user cannot see "sec" value in the drop down. This is observed in both "default time limit" and unit time under conditional group.
Note that this can be achieved by rest api, therfore this needs to be fixed in UI as well.

PR : https://github.com/wso2/carbon-apimgt/pull/5065


Fixed Piece-Square Tables position evaluation

Reversed the rows of the Piece-Square Tables as explained here.
Also added a small testcast to verify the functionality.

Hi @Varsius!
This looks great.
Two things:

Can you fix the two failing tests? I think it's because the move values changed and the tests need to be updated.
Do you think another test is necessary to cover black's POV? i.e. if black responds to e2e4 with e7e5 then black's positional value should improve.

Oh sorry, that is my bad.. I will be working on a fix soon. And adding another test is no problem.

Tests should be fixed now.

Thanks for the PR! This closes #12


Convert TestValue_Getters to table-driven style

Merge all subtests of TestValue_Getters into a single table-driven test.
Use other table-driven tests in value_test.go as a reference.

Landed


Fail on trailing new lines in disk-encryption keys

draft to see whether with-sudo ci tests fail as expected, currently a bit slow to run locally here ;)

ah, hadn't seen those commits. Thanks!
Was wondering whether just stripping newlines could lead to unexpected situations in setups where the keys don't come from an interactive prompt during boot. But we can probably easily fix those should they arise.


Gradle Plugin for Cloud Foundry?

Hi community,
I want to ask, if somebody can recommend a gradle plugin for cloud foundry?
It shall be able to do this command:
cf push APP_NAME --docker-image [REGISTRY_HOST:PORT/]IMAGE[:TAG] [--docker-username USERNAME]
I would be happy, if you can give me some hints.
Thank you in advance

Please use the Gradle forum for questions. The issue tracker is only for bugs and feature requests for Gradle core.


CHAOS-5946 Add content and reference links to onboard checklist

Describe the permissions required, and add reference links to them.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://668399237dfbc216e06f5342--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66854521756ef1007c219f81--harness-developer.netlify.app


Turtlebot 3 angular velocity commands sign change in real world

ISSUE TEMPLATE ver. 0.2.0

[x] Burger

[ ] Raspberry Pi 3

[ ] Raspbian

[ ] Ubuntu 14.04 LTS

Write down software version and firmware version

Software version: [1.0.0]
Firmware version: [1.2.0]

Write down the commands you used in order
-roslaunch turtlebot3_bringup turtlebot3_robot.launch

I've noticed that I have to change the signs of the angular velocity commands whenever I switch between simulations, and the turtlebot. Is this a bug?

Hi @varunvp :)
Could you tell me more about you said 'switch between simulations and the turtlebot'?

I meant switching between turtlebot simulations on gazebo, and the real life turtlebot.

Could you check your DXL's ID? Letf DXL is 1, right DXL is 2.
Thanks,
Gilbert.

This issue will be closed since there were no actions for a while. You can reopen this issue to show this issue to the users whenever. Thanks.


[Refactoring] Bastion actors and definitions

Checklist

[ ] tests are passing with cargo test.
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added
[ ] commit message is clear

@Relrin I am looking forward to merge this. Looks neat so far.


Fix Login Failure After Manual 8.5.1 Migration

This change addresses the login issues discussed in #7686.  The credit goes to @debaugh for isolating the spot for the fix.

I just tested these changes, and everything LGTM


fix: ERROR: 'CompletionUsage' object has no attribute 'get'

What problem does this PR solve?
Briefly describe what this PR aims to solve. Include background context that will help reviewers understand the purpose of the PR.
Type of change

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

hi @chinamerp . I cannot reporduce this bug ,Do you know how to reproduce this bug?

reporduce this bug：in chat dialog input question，get answer like "xxxxx  ERROR: 'CompletionUsage' object has no attribute 'get'"
openai version:
Name: openai
Version: 1.35.14
Summary: The official Python library for the openai API
Home-page:
Author:
Author-email: OpenAI<EMAIL_ADDRESS>


check GPS enabled state

Since a while I have a phone with Android 2.3.6 which allows enabling/disabling GPS very easily from the status bar. I now have it disabled by default (so Facebook and other apps can not track my position), but always forget to activate it for c:geo and then wonder why the position is not updated.
We really need to have a check in the tool whether or not GPS is enabled (at least when entering the map) and to notify the user or to activate it by ourselfes then.
Not sure if there are duplicates for this, I didn't find one with the quick search.

If you chose to disable the GPS, why should c:geo warn you about it while it can perfectly work without it? Can't you use Tasker or a similar software to enable the GPS while running c:geo?
Would you like it if Facebook and other apps did remind you to turn your GPS on while it can work without it?

We had some time ago already a request to allow to toggle the gps from inside c:geo (#375) that is somewhat related.
If I would use the phones GPS I would see the GPS status in the status bar - is that different for you? Additionally as mentioned in the related entry, c:geo would remind me constantly because my GPS is always turned of (I use an external GPS via bluetooth).

If I want an app to use GPS, I'll enable it. If I don't want it, I'll keep it disabled.

I have also GPS disabled by default. But i'm using EasyProfiles that enables GPS when switching to a "GPS-enabled-profile". And i also don't want any notification to enable GPS.

I'm happy since c:geo notice GPS-enabling during c:geo is open!
"If I would use the phones GPS I would see the GPS status in the status bar " .. same here.

I'm also happy with the current implementation (at least since c:geo detects switch on while the app is running).

Sorry guys, but I reopened the issue because I'm absolutely not satisfied with the answers. I've described a problem that I as a user have with the app and basically everyone tried to convince me that I don't have that problem. To comment on some of the answers:

When I had that issue, my position was around 2 kilometers off. It was shown nearly in the next village! That is not "works without GPS".
I don't consider using a 5 EUR third party software as a solution, if I only need it for this fix.
Yes, I really like that Google Maps tells me that my GPS is not enabled and that the output of the app will improve if I enable it.
If the GPS is switched off then there is no icon on my phone. Technically that might show me it is off, but from the psychological viewpoint the absence of the icon doesn't really indicate anything to me.

As everyone seems to be completely afraid of notifications, what counter arguments do you have for an option to automatically activate GPS?

As everyone seems to be completely afraid of notifications, what counter arguments do you have for an option to automatically activate GPS?

It's not possible. ;) Even Google-apps open the Android-settings so that the user can enable it.

Yes, I really like that Google Maps tells me that my GPS is not enabled and that the output of the app will improve if I enable it.

I don't like it. 6 vs. 1

I choose to disable GPS because I can't control the GPS access on a per application level as a normal Android user.

Per-application-setting is not intended by Google. It's a global privacy setting. The only way is to retract the permission for each app that you don't want to access the GPS (only possible in some custom ROMs).

I normally use c:geo with my GPS off as it runs my battery down too quickly with it on.
Also, c:geo can be used for many things without needing GPS (such as managing lists, exporting field notes, inporting GPX. etc). I do no see a need for this feature (for me).
If you desire to have a prompt about turning GPS on, I request that you add a setting so that I can tell it not to prompt me. I don't want to have to see it every time.

@blafoo
That's a good idea!

In the lower right of the main-screen it says "Network" for me if GPS is disabled...
For me this is the indication that GPS is off or not yet fixed.
Maybe this could be exteneded/used for that purpose ?

Having some extension to the available status lines sounds perfectly fine to me. I'm absolutely not fixed on the idea of a message popping up, I'm mainly trying to solve the problem, that on one day I use Facebook, see the GPS icon coming up and disable it, the next day I use c:geo and wonder why it doesn't get the right caches around me until I remember the GPS setting.

Sounds like missing conditioning for the geocaching-workflow. ;)

It seems my post from yesterday is lost or I did something wrong:
I like the idea from @blafoo:
Maybe a warning could be issues on the lower left or lower right in case GPS is disabled. This could be a black-on-red text stating "GPS disabled".

white on red or red on yellow should be good combinations, maybe in conjunction with a warning triangle.


Webinterface crashes when there are playlists with wrong simbols in name

Hi!
After copying on Musicbox a series of playlists prepared on Windows and after reboot webinterface didn't launch (though mopidy service was working and I even managed to connect to it via AirPlay). Detecting wrong playlists and deleting them (+reboot) solve my problem. So, for me my problem is solved, but I think it's a bug you should fix in next release (however, looking forward for a new version of PiMusicbox).
Good luck!

Could you perhaps provide an extract of the log file (mopidy.log) that shows exactly what type of errors occurred?
It is likely that the symbols are causing Mopidy itself to crash (connecting via Airplay does not prove that Mopidy is up and running - that's a feature that is provided via shairport-sync).
The M3U backend went through a major overhaul in Mopidy 2.0, so you may just be encountering an old issue in Mopidy that's since been fixed.

Maybe I'm looking in a wrong place, but at /var/log/mopidy I can't find a logging for more than 2-3 days from now (this error happend 4-5 days ago and there is no record for this time period).
But if this issue is fixed in new version – it's great!!!

I cannot reproduce this in 0.7.0rc4. If this is not fixed then please reopen.


Change the gson parser to account for changes in the new json output of the orga server

There have been changes in the open event orga json and so the parser has to be changed in order to incorporate these changes.
https://github.com/fossasia/open-event-orga-server/tree/development/samples/ots16
These changes include modifying parser for :

[x] Sponsors
[x] Speakers
[x] Tracks
[x] Sessions
[x] Services Any other objects

Updated the issue to break it into sub modules

@the-dagger
I can help with this. Basically we need to update the parser for v2 right ?
We have already done that on webapp. I'll take some time out to help on it today

Yeah @championswimmer.
Great then, let me know when you're free and we shall work on this.
Cheers.

@mananwason I am able to parse the json files but data isn't getting displayed and stored into the database for some reason.
Let us work on this today.

@the-dagger @mariobehling what are services over here. I'm not able to understand

Changed to "Any other objects".

Closed via #519


Capture and playback touch inputs

What problem does this solve?
Gamepad inputs are not captured.
What solution would you like?
Automatically capture and playback gamepad inputs.

Removing from the milestone; touch support is still immature and I don't have a good way to test this.


Refactor input element

Changes were made to the Input element in combination with Button in order to make both fit easier into the brand identity of the application.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


STORM-2078: enable paging in worker datatable

This can get cherry-picked to 1.x

+1

@revans2 I moved the call to my function that checks for whether the worker components should show or not to a callback that triggers on each render of the datatable. I noticed a bug where filtering would cause odd behavior... this fixes it.

+1, NB

+1


etcd version 3 does not send cfn-signal

<EDITED, this happens also with etcd2>  I tried the new etcd support and specified version: 3.1.5 in the cluster.yaml.  However, etcd starts, but is version 3.0.x and also cfn-signal never fires.  I attempted to debug why it does not fire since etcd3 was able to startup ok and I'm seeing a weird issue.  It does not look like cfn-signal was ever triggered to run and when I manually do systemctl start cfn-signal it hangs forever.  When I look at the processlist for some reason it's showing this systemd-tty-ask-password-agent running...  Using latest master.
root      3710  0.0  0.0  33420  3084 pts/0    S+   18:25   0:00                      \_ systemctl start cfn-signal
root      3711  0.0  0.0  33288  3188 pts/0    S+   18:25   0:00                          \_ /usr/bin/systemd-tty-ask-password-agent --watch

I just tried etcd2 also and it did not receive the signal, however this problem is slightly different since the cfn-signal did startup but cloudformation did not see the signal come in.

I'm still investigating this issue. It's weird because it worked once, 3 ETCD nodes, all sent cfn-signal. Even got a snapshot on a S3 bucket .  Now I don't manage to pass even one "success".Tomorrow  I'm planning to increase the waiting time for the signal and try debugging each failed service on ETCD nodes.

@jeremyd maybe #504 fix this issue, in case you had terminated instances from previous deployments, as @mumoshu pointed this bug in #501.

Thanks to both of you :bow:
#504 is merged and kube-aws v0.9.6-rc.1 which includes the fix is released.
@jeremyd Could you please confirm if the new release work for you now?

This works now, thanks!


There is no 'Print View' option

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Please do not submit support request here, post on Stackoverflow or Gitter

Current behavior
There is no 'Print View' feature.
Expected behavior
Please, add the 'Print View' feature.
What is the motivation / use case for changing the behavior?
Motivation is to print the data table.

Table version: 10.2.3

Angular version: 4

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [all | TypeScript X.X | ES6/7 | ES5]

I have an exact use case for this feature.  Currently, if a user prints the page with the table on it, it doesn't resize properly leading to cut off information, and because of the structure of the markup, it is impossible to create a print style sheet that for instance would re-render the table using display: table.  I'm currently exploring a way to output a hidden html <table> tag that can be toggled to in my print css.

Solution? Anyone?

This is really out of scope for the project. Also this would be very very difficult to do with virtualized dom.

For anyone who does come across this and needs it to happen, I was able to flesh out a way to make my proposed feature work by traversing the rendered grid and building out an HTML <table> that was swapped out in my print css.  I can't share the code because it's for a work project, plus it's doing some dom manipulation keyed off ngOnChanges, so it's kind of gross, though I'd imagine that there's a better, more angular-y way to do it as a plugin or something.  Just sharing my experience from having to "just make it work" for a client.

Does NGX-datatables have support for print-styling today 2021? Example  :host ::ng-deep .datatable-row-odd {
background-color: #eee;
} doesent apply to the print, even if i put it inside a @media print tag  @tstackhouse @amcdnl


Support for kinetic dragging

Hi,
most of the map libs out there now allows for kinetic dragging ie. http://openlayers.org/dev/examples/kinetic.html. Leaflet would gain a lot from it especially for the mobile experience. Have you guys considered it?
Thanks
R.

Yep, planned for this release: https://github.com/CloudMade/Leaflet/issues/17
Closing the issue as duplicate.

The link is broken


How to add 'readOnlyRootFilesystem: true' to Alertmanager security context

I need to make the root filesystem of the Alertmanager pods/containers as read-only per the security guideline.  I added readOnlyRootFilesystem: true to the securityContext of Alertmanager but the change was ignored on deployment.

How do I add the key/value to the Alertmanager securityContext?

alertmanager-alertmanager.yaml looks like:
apiVersion: monitoring.coreos.com/v1
kind: Alertmanager
metadata:
  labels:
    alertmanager: main
  name: main
  namespace: monitoring
spec:
  baseImage: us.icr.io/quay-io/alertmanager
  imagePullSecrets:
  - name: container-registry
  nodeSelector:
    beta.kubernetes.io/os: linux
  replicas: 3
  securityContext:
    fsGroup: 2000
    readOnlyRootFilesystem: true         <-- I ADDED THIS LINE
    runAsNonRoot: true
    runAsUser: 1000
  serviceAccountName: alertmanager-main
  version: v0.18.0

After deployment, I do not see the change in the Alertmanager pods. E.g.
$ kubectl get pod alertmanager-main-0 -n monitoring -o yaml
apiVersion: v1
kind: Pod
metadata:
  creationTimestamp: 2019-12-04T06:20:11Z
  generateName: alertmanager-main-
  labels:
    alertmanager: main
    app: alertmanager
    controller-revision-hash: alertmanager-main-79b5cd6f44
    statefulset.kubernetes.io/pod-name: alertmanager-main-0
  name: alertmanager-main-0
  namespace: monitoring
  ownerReferences:
  - apiVersion: apps/v1
    blockOwnerDeletion: true
    controller: true
    kind: StatefulSet
    name: alertmanager-main
    uid: 1fffe4d8-165e-11ea-911a-fa163e557664
  resourceVersion: "7076529"
  selfLink: /api/v1/namespaces/monitoring/pods/alertmanager-main-0
  uid: 206d38d2-165e-11ea-a973-fa163e999a1f
spec:
  containers:
  - args:
    - --config.file=/etc/alertmanager/config/alertmanager.yaml
    - --cluster.listen-address=[$(POD_IP)]:9094
    - --storage.path=/alertmanager
    - --data.retention=120h
    - --web.listen-address=:9093
    - --web.route-prefix=/
    - --cluster.peer=alertmanager-main-0.alertmanager-operated.monitoring.svc:9094
    - --cluster.peer=alertmanager-main-1.alertmanager-operated.monitoring.svc:9094
    - --cluster.peer=alertmanager-main-2.alertmanager-operated.monitoring.svc:9094
    env:
    - name: POD_IP
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: status.podIP
    image: us.icr.io/quay-io/alertmanager:v0.18.0
    imagePullPolicy: IfNotPresent
    livenessProbe:
      failureThreshold: 10
      httpGet:
        path: /-/healthy
        port: web
        scheme: HTTP
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 3
    name: alertmanager
    ports:
    - containerPort: 9093
      name: web
      protocol: TCP
    - containerPort: 9094
      name: mesh-tcp
      protocol: TCP
    - containerPort: 9094
      name: mesh-udp
      protocol: UDP
    readinessProbe:
      failureThreshold: 10
      httpGet:
        path: /-/ready
        port: web
        scheme: HTTP
      initialDelaySeconds: 3
      periodSeconds: 5
      successThreshold: 1
      timeoutSeconds: 3
    resources:
      requests:
        memory: 200Mi
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /etc/alertmanager/config
      name: config-volume
    - mountPath: /alertmanager
      name: alertmanager-main-db
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: alertmanager-main-token-62mjc
      readOnly: true
  - args:
    - -webhook-url=http://localhost:9093/-/reload
    - -volume-dir=/etc/alertmanager/config
    image: us.icr.io/quay-io/configmap-reload:v0.0.1
    imagePullPolicy: IfNotPresent
    name: config-reloader
    resources:
      limits:
        cpu: 100m
        memory: 25Mi
      requests:
        cpu: 100m
        memory: 25Mi
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /etc/alertmanager/config
      name: config-volume
      readOnly: true
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: alertmanager-main-token-62mjc
      readOnly: true
  dnsPolicy: ClusterFirst
  hostname: alertmanager-main-0
  imagePullSecrets:
  - name: container-registry
  nodeName: sre-k8s-2-node4
  nodeSelector:
    beta.kubernetes.io/os: linux
  restartPolicy: Always
  schedulerName: default-scheduler
  securityContext:
    fsGroup: 2000        <-- MISSING readOnlyRootFilesystem
    runAsNonRoot: true
    runAsUser: 1000
  serviceAccount: alertmanager-main
  serviceAccountName: alertmanager-main
  subdomain: alertmanager-operated
  terminationGracePeriodSeconds: 120
  volumes:
  - name: config-volume
    secret:
      defaultMode: 420
      secretName: alertmanager-main
  - emptyDir: {}
    name: alertmanager-main-db
  - name: alertmanager-main-token-62mjc
    secret:
      defaultMode: 420
      secretName: alertmanager-main-token-62mjc
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: 2019-12-04T06:20:11Z
    status: "True"
    type: Initialized
  - lastProbeTime: null
    lastTransitionTime: 2019-12-04T06:20:16Z
    status: "True"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: 2019-12-04T06:20:11Z
    status: "True"
    type: PodScheduled
  containerStatuses:
  - containerID: docker://8d8d52b58d43bc632f07258fd2b8b23703b9995d9c8abf2f396ed41452df597f
    image: quay.io/prometheus/alertmanager:v0.18.0
    imageID: docker-pullable://quay.io/prometheus/alertmanager@sha256:3d52ab7ef3a2e23e26a73cfd0ce13189e3796fb276b9af3e79664e4f743d8a1d
    lastState: {}
    name: alertmanager
    ready: true
    restartCount: 0
    state:
      running:
        startedAt: 2019-12-04T06:20:12Z
  - containerID: docker://5ff8963a4645b14642e4adbfbb58f65392f8a3a11067a633a67edde2ad6f9903
    image: quay.io/coreos/configmap-reload:v0.0.1
    imageID: docker-pullable://quay.io/coreos/configmap-reload@sha256:e2fd60ff0ae4500a75b80ebaa30e0e7deba9ad107833e8ca53f0047c42c5a057
    lastState: {}
    name: config-reloader
    ready: true
    restartCount: 0
    state:
      running:
        startedAt: 2019-12-04T06:20:12Z
  hostIP: <IP_ADDRESS>
  phase: Running
  podIP: <IP_ADDRESS>
  qosClass: Burstable
  startTime: 2019-12-04T06:20:11Z

Prometheus Operator version: v0.33.0

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:08:12Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.12", GitCommit:"a8b52209ee172232b6db7a6e0ce2adc77458829f", GitTreeState:"clean", BuildDate:"2019-10-15T12:04:30Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
Created via Kubespray

Could you check if the statefulset has the security context the way you defined?

@brancz readOnlyRootFilesystem exists in the statefulset, as can be seen in kubectl.kubernetes.io/last-applied-configuration. But not in the containers' security context.
$ kubectl get statefulset alertmanager-main -n monitoring -o yaml
apiVersion: apps/v1
kind: StatefulSet
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"monitoring.coreos.com/v1","kind":"Alertmanager","metadata":{"annotations":{},"labels":{"alertmanager":"main"},"name":"main","namespace":"monitoring"},"spec":{"baseImage":"us.icr.io/quay-io/alertmanager","imagePullSecrets":[{"name":"container-registry"}],"nodeSelector":{"beta.kubernetes.io/os":"linux"},"replicas":3,"securityContext":{"fsGroup":2000,"readOnlyRootFilesystem":true,"runAsNonRoot":true,"runAsUser":1000},"serviceAccountName":"alertmanager-main","version":"v0.18.0"}}     <-- readOnlyRootFilesystem EXISTS HERE
  creationTimestamp: 2019-12-04T06:49:44Z
  generation: 1
  labels:
    alertmanager: main
  name: alertmanager-main
  namespace: monitoring
  ownerReferences:
  - apiVersion: monitoring.coreos.com/v1
    blockOwnerDeletion: true
    controller: true
    kind: Alertmanager
    name: main
    uid: 1fed86ed-165e-11ea-ade9-fa163e03e917
  resourceVersion: "7080213"
  selfLink: /apis/apps/v1/namespaces/monitoring/statefulsets/alertmanager-main
  uid: 417eac69-1662-11ea-911a-fa163e557664
spec:
  podManagementPolicy: Parallel
  replicas: 3
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      alertmanager: main
      app: alertmanager
  serviceName: alertmanager-operated
  template:
    metadata:
      creationTimestamp: null
      labels:
        alertmanager: main
        app: alertmanager
    spec:
      containers:
      - args:
        - --config.file=/etc/alertmanager/config/alertmanager.yaml
        - --cluster.listen-address=[$(POD_IP)]:9094
        - --storage.path=/alertmanager
        - --data.retention=120h
        - --web.listen-address=:9093
        - --web.route-prefix=/
        - --cluster.peer=alertmanager-main-0.alertmanager-operated.monitoring.svc:9094
        - --cluster.peer=alertmanager-main-1.alertmanager-operated.monitoring.svc:9094
        - --cluster.peer=alertmanager-main-2.alertmanager-operated.monitoring.svc:9094
        env:
        - name: POD_IP
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: status.podIP
        image: us.icr.io/quay-io/alertmanager:v0.18.0
        imagePullPolicy: IfNotPresent
        livenessProbe:
          failureThreshold: 10
          httpGet:
            path: /-/healthy
            port: web
            scheme: HTTP
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 3
        name: alertmanager
        ports:
        - containerPort: 9093
          name: web
          protocol: TCP
        - containerPort: 9094
          name: mesh-tcp
          protocol: TCP
        - containerPort: 9094
          name: mesh-udp
          protocol: UDP
        readinessProbe:
          failureThreshold: 10
          httpGet:
            path: /-/ready
            port: web
            scheme: HTTP
          initialDelaySeconds: 3
          periodSeconds: 5
          successThreshold: 1
          timeoutSeconds: 3
        resources:
          requests:
            memory: 200Mi
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /etc/alertmanager/config
          name: config-volume
        - mountPath: /alertmanager
          name: alertmanager-main-db
      - args:
        - -webhook-url=http://localhost:9093/-/reload
        - -volume-dir=/etc/alertmanager/config
        image: us.icr.io/quay-io/configmap-reload:v0.0.1
        imagePullPolicy: IfNotPresent
        name: config-reloader
        resources:
          limits:
            cpu: 100m
            memory: 25Mi
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /etc/alertmanager/config
          name: config-volume
          readOnly: true
      dnsPolicy: ClusterFirst
      imagePullSecrets:
      - name: container-registry
      nodeSelector:
        beta.kubernetes.io/os: linux
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext:
        fsGroup: 2000               <-- NO readOnlyRootFilesystem
        runAsNonRoot: true
        runAsUser: 1000
      serviceAccount: alertmanager-main
      serviceAccountName: alertmanager-main
      terminationGracePeriodSeconds: 120
      volumes:
      - name: config-volume
        secret:
          defaultMode: 420
          secretName: alertmanager-main
      - emptyDir: {}
        name: alertmanager-main-db
  updateStrategy:
    type: RollingUpdate
status:
  collisionCount: 0
  currentReplicas: 3
  currentRevision: alertmanager-main-79b5cd6f44
  observedGeneration: 1
  readyReplicas: 3
  replicas: 3
  updateRevision: alertmanager-main-79b5cd6f44

Could you try linting your manifests with the linting tool we have available? Install it with:
go get -u -v https://github.com/coreos/prometheus-operator/tree/master/cmd/lint

Then you can lint a manifests simply with:
lint <filename>
echo $?

Only if the exit code is 0 then there are no linting/parsing errors.

@brancz This is what I get on linting the alertmanager-alertmanager.yaml where I made the change
./main alertmanager-alertmanager.yaml
2019/12/10 16:35:07 alertmanager is invalid: json: unknown field "readOnlyRootFilesystem"

I have been told that securityContext: readOnlyRootFilesystem is only available to the containers and not to any other k8s resource. And hence I will need to add it to the container specs of alertmanager's containers.
How are the specs for the alertmanager's container generated? I will need to make the modifications there.

It's generated here: https://github.com/coreos/prometheus-operator/blob/d6d17e6b9653374d7c8e8829b065da9ea3b69aa6/pkg/alertmanager/statefulset.go#L490-L511
I'm curious how the container's securitycontext plays with for example PodSecurityPolicies. If we can in a generally applicable way set read only filesystem to be true, then I'm happy doing so, but I recall us having difficulties with these things in the past, which is why I am tending towards enabling container-merge functionality like we have for the Prometheus object via the containers field:
Containers described here modify an operator generated container if they share the same name and modifications are done via a strategic merge patch. The current container names are: prometheus, prometheus-config-reloader, rules-configmap-reloader, and thanos-sidecar. Overriding containers is entirely outside the scope of what the maintainers will support and by doing so, you accept that this behaviour may break at any time without notice.

If we enable the same thing for the alertmanager, then it would be trivial to set this security context for the container for your setup. Would you like to give this a try? (there is precedence on how to implement this for the Prometheus object here)

Closing due to staleness. Please reopen if you think this is still relevant.


ExpandIcon padding not working properly

I believe there is a bug with the ExpandIcon, I can't set the padding value less than 8 (default padding), if I change it to 0 the icon stays in the same place, only higher values than 8 work.

Thanks for the report!
It would help if you could provide a small self-contained app that demonstrates the problem you've run into.  Screenshots that highlight what's wrong are also useful!


Updated mkdir and find to pass kwargs to async implementations

Fix for #135

@ldacey - Not sure if you saw this discussion at fsspec.  Link to here for any input you may have.


Initial page layout

User Story:

As a developer,
I want to lay out the initial JSX in an organized way,
So that developing components in the future is intuitive and easy

Acceptance Criteria:
Update the JSX in App.js to reflect the sections in the attached screenshot

[x] Use semantic HTML elements whenever possible
[x] Add an element for the navbar
[x] Add an element for the "hero" section
[x] Add an element for the "pitch" section (possible rename this)
[x] Add an element for the halogen app itself
[x] Add an element for the palette section
[x] Add an element for the footer section

Note: This story is just about setting up the containers, no content inside is needed. We will have separate stories for each sections content

I finished writing the sections but I kind of got a little excited and carried away and started thinking about the layout of the webapp. I just created a Google JamBoard to jot down my ideas. Maybe looking at these ideas we can prototype on a better platform like JustinMind, Figma, etc. I just wanted to write down some ideas without getting to fancy so I just did it on Jamboard. Here's the link if y'all want to check it out and maybe leave some suggestions so when we are actually designing we can refer back to these simple notes. https://jamboard.google.com/d/1p8IgGBh6N_K54cxLYsnewVA6HHIDWIng8PsfA3v3gT0/edit?usp=sharing


trunk_address is not being replaced

Hi!
I am finding myself with lots of errors such as the following:
login:673 WebSocket connection to 'wss://{{__trunk_address__}}/_trunk/ws' failed:

I am running on a Chrome browser, macOS. This is our current Trunk configuration (permalink).
I suppose that this variable is meant to be replaced here in your code but for some reason, it is not. Do you have any idea what may cause this to happen?
I do not see any error reported in the log of the Trunk serve.

Which version of trunk are you running? Is there any reproducer that you can share?

Hi @ctron! The version is the latest published, 18.8. I still have to get a minimal reproducible setting, as myself I have no clue as to how this error emerged. I am currently packaging the whole development setup in Dockers, and my current suspects are related to some misconfiguration there. I am now fully rebuilding the Docker and will keep you posted.
That being said, is it correct that I should expect the address __trunk_address__  of the website to be replaced during build time?

That being said, is it correct that I should expect the address trunk_address of the website to be replaced during build time?

Yes. An it might very well be that that's an issue with that code.
I would also encourage you to try out 0.19.0-rc.1, which I just released. I briefly recall some changes in the area.

I have resolved it by making a spartan docker system prune --all to remove all Docker-related stuff, and by rebuilding cleanly the dockers for development (permalink) and deployment (permalink) it is now working.
I am really not sure about how this could cause Trunk serve to start without any error, refresh correctly upon Rust code edits but have the URL not being properly replaced.
Maybe it is an error being ignored or something of this nature in the implementation of Trunk 18.8.
If it happens again in the future, I will try to 19 version and let you know how it does.

I think we can close this issue for the time being, I will reopen if it represents by itself.

Thanks for following up!


See about removing unneeded JSON support from Extensions

Spun out of comments on https://github.com/apple/swift-protobuf/pull/145 -
The Extensions vars created include information for JSON support.  But the spec for JSON doesn't seem to include extensions.  So the extra support for JSON on extensions like should get removed.
Note: a message in a proto3 syntax file can have a field defined in a proto2 syntax file, so JSON support is needed for proto2, it just seems like extensions aren't expected to survive.

@thomasvl:  Is this done?
I see no JSON specifics in the generated code (so at a minimum, I think generator API is no longer relevant).
I don't see any JSON support for Extensions in the library, either, but maybe I missed something?

I honestly don't know.  I opened this purely on your comment on #145 -

I implemented full JSON support for all of proto2 (including extensions, groups, etc) just to see what it would require. Turns out to be pretty straightforward, actually. We should probably rip that back out again to avoid confusion.

But I didn't go dig to see what it actually was.

Okay.  Looks like the last part of this was finished in d1dd91e5, so I'll close it.


Update CI workflow

Description

Fixes #2479 (somewhat). The only bottleneck now is the yarn build command taking forever.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[x] Code quality improvements

How to test

Checklist

[x] I have tested this code
[ ] I have updated the documentation

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 34.828%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4913

Relevant Lines:
13169

💛  - Coveralls

The required CI job will have to be changed in the repository settings immediately before merging this PR:

Note that after this PR is merged and the repository settings are updated, existing PRs will need to pull in the updated workflow file otherwise they will not be able to be merged without bypassing branch protections.

The required CI job will have to be changed in the repository settings immediately before merging this PR:

Seems like I'm unable to select the updated job (perhaps because it's not on master yet?). Thinking of just bypassing requirements for this one, and then update the required CI job for all other PRs once this has been merged.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 34.828%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4913

Relevant Lines:
13169

💛  - Coveralls


feat(Pagination): introduce new component and preset

Add Pagination Components

PR Moved to https://github.com/una-ui/una-ui/pull/210


Fix remove ignored files from import

Hey !
During import from local folder, the script load all files including node_modules, env (stored in cookies) and .gitignored files.
As import MAX_FILES is 1000 it may quickly get stuck.
I've made a quick fix to avoid this, that would allow to upload folder more efficiently, by removing npm/git/ignored files from import.

this is nice but why not use the ignore library to ignore the paths that match the pattern, I am not confident on the glob to regex conversion. I recommend using https://www.npmjs.com/package/ignore

My suggestion would be to maintain your project on GitHub and just pull in the repo with the latest changes. That way best practice is to use .gitignore (by default) and that would resolve this issue. I think the idea behind importing a folder is for prototyping something really quick, not uploading Gigs of data to the Web Container. And while it's not a horrible idea (maybe make bolt use the same .gitignore file when importing), I'm not sure we can support this. I think it's more or a proceedure and maybe provide a warning, than really a thing to fix in code. Just my two cents. Thanks

Ignore is already used here
https://github.com/stackblitz-labs/bolt.diy/blob/1f938fca407aa7fe024fb3d835abb97a285a3621/app/utils/fileUtils.ts#L42
Its imported into
https://github.com/stackblitz-labs/bolt.diy/blob/main/app/components/chat/ImportFolderButton.tsx#L38
I remember testing that it was filtered out.
Need to retest.
But your regex code is not needed, as @aliasfoxkde said ignore library and existing code should be used.

Hi, thanks for your input!
Yes basically the gitignore is taken in account after the files are have
been counted, so I guess it's just a matter of moving that check point so
that's the gitignore is taken in account while counting files right after
file upload.
The issue currently is that uploading a folder with a few files but a
node_modules folder will trigger that max files error, while those ignored
files are then removed and not sent to workbench.
I'll give it another look for a smoother integration, thanks for your
remarks !
Le lun. 23 déc. 2024, 11:07, Eduard Ruzga @.***> a
écrit :

Ignore is already used here
https://github.com/stackblitz-labs/bolt.diy/blob/1f938fca407aa7fe024fb3d835abb97a285a3621/app/utils/fileUtils.ts#L42
Its imported into
https://github.com/stackblitz-labs/bolt.diy/blob/main/app/components/chat/ImportFolderButton.tsx#L38
I remember testing that it was filtered out.
Need to retest.
But your regex code is not needed, as @aliasfoxkde
https://github.com/aliasfoxkde said ignore library and existing code
should be used.
—
Reply to this email directly, view it on GitHub
https://github.com/stackblitz-labs/bolt.diy/pull/783#issuecomment-2559354216,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASV2XSC7V45FZWGDHQEXYH32G7OFDAVCNFSM6AAAAABTXESZUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJZGM2TIMRRGY
.
You are receiving this because you authored the thread.Message ID:
@.***>