Events missing when enabled “SC4S_Use_Name_Cache=Yes”

With the assist from the GitHub team (Host IP can’t be resolved to FQDN on same device on same sourcetype · Issue #1742 · splunk/splunk-connect-for-syslog · GitHub), I have enabled the “SC4S_Use_Name_Cache=Yes” in the env_file that to ensure the device IP (in fallback sourcetype) are converted to FQDN (in VMWare sourcetype). (it was same device but one showed IP another showed FQDN
Issues
• When enabled the “SC4S_Use_Name_Cache=Yes”, Same device will display FQDN in Fallback or VMWare sourcetype. But this caused “packet receive errors” numbers increase when monitoring through “watch -n 1 'netstat -anus'”
• When enabled the “SC4S_Use_Name_Cache=Yes” together with “SC4S_Source_listen_UDP_Socket=1”, the ““packet receive errors” didn’t see any dropped. But when tested with loggen showed that number in Splunk Portal are less than the loggen counter number.
• When disabled the “SC4S_Use_Name_Cache=Yes” and “SC4S_Source_listen_UDP_Socket=1”. The ““packet receive errors” didn’t see any dropped, and loggen test counter showed loggen and portal are matched.
RHEL: 8.5
Podman: 3.0.1
SC4S: version 2.30.0

What could the issues
How to determine the value of “X” on “SC4S_Source_listen_UDP_Socket=x”? As according to the
“Number of kernel sockets per active UDP port, which configures multi-threading of the UDP input buffer in the kernel to prevent packet loss. Total UDP input buffer is the multiple of SOCKETS * SO_RCVBUFF
Where we already have 512 MB set on
OS Kernel

Adjust the buffers related kernel parameters
net.core.rmem_default = 536870912
net.core.rmem_max = 536870912
Env_File
#####UDP Buffer configuration#####
SC4S_SOURCE_UDP_SO_RCVBUFF=536870912
#####UDP Buffer configuration#####
We Provided the documents of SC4S to change the parameters accordingly.
So, you would be required to make 4 changes in the configuration, that is changing the values of:

SC4S_SOURCE_LISTEN_UDP_SOCKETS to 8
SC4S_SOURCE_UDP_SO_RCVBUFF to 67108864
net.core.rmem_default to 17039360
net.core.rmem_max to 67108864

The client is still fine-tuning the buffers for the OS / SC4S end.
Various buffers sizes have been configured, yet On / Offstill received buffers errors.
Can you please help us to resolve the issue?
uploadsvc-85case3018713-07-25-2022-USER-0030b00002DKOreAAH-Catch_Test.docx

@rjha-splunk : Hello Rahul,
Can you please provide some insight on it ?

The issue is right now the rcvbuff is not able to take care of UDP buffers , they can increase :

Number of sockets ( maximum number is 2 X core of cpu)
Increase net.core.rmem_max and SC4S_SOURCE_UDP_SO_RCVBUFF until you see that there is no loss, UDP protocol is lossy protocol so it needs the tuning until we dont see the loss https://www.syslog-ng.com/technical-documents/doc/syslog-ng-premium-edition/7.0.10/collecting-log-messages-from-udp-sources
There could be a problem in communication with dns server and sc4s including overwhelming of cache , there is another  option of using host.csv file  "https://splunk.github.io/splunk-connect-for-syslog/main/configuration/#fixing-overriding-the-host-field"

We have already asked them to increase the values mentioned in points 1 and 2.
For 3, we will ask them to check the host.csv file right now .
But, we would ask you to please advise the values for 1, and 2. As we have already asked them to increase to 8 and 67108864, respectively.

We cant suggest a value, Every env is different they need to check by increasing the parameters.

@dsingala Can you share what kind of loggen test/command are you running?

@rjha-splunk : Sure. I will ask customers and let you what kind of loggen test/command they are running.

@rjha-splunk :
We have the below update from the client for the loggen test.
"Below the sample. We change the rate or number of connections. S with being either 1400 or 800. Issues occur especially with high eps or connections
loggen -i -D --rate=150 --interval=300 -P -F --sdata="[test name="QF Loggen Test -With Filter v2.03"]" -s 1400 --active-connections=100 x.x.x.x.x Port
loggen -i -D --rate=300 --interval=300 -P -F --sdata="[test name="QF Loggen Test -With Filter v2.05"]" -s 1400 --active-connections=100 x.x.x.x.x Port"

@rjha-splunk : Hello Rahul,
If you can provide some insights on this
Thank you in Advance

The qa team is working on it, unfortunately we dont have any update yet.

@rjha-splunk : Thank you for the update.
Can you please explain in detail, what the QA team is checking and working on?
I have to provide the update to the client.
Even I am curious to know more about the SC4S and loggen test as well.

@dsingala
We confirmed in tests when enabling feature SC4S_USE_NAME_CACHE there can be data loss on UDP packets comparing to default settings with the same logs rate.
Unfortunately it cannot be fixed just by changing memory of UDP buffers - but generally increasing it helps in processing higher rates (to some point, setting this too high can make data loss).
If with disabled SC4S_USE_NAME_CACHE there is no data loss - most likely buffer value is set properly. If there is data loss in any case, you can for example double the current buffer and check if this helped.
To have no missing events with enabled SC4S_USE_NAME_CACHE there will be required to use more CPU power by using more SC4S_SOURCE_LISTEN_UDP_SOCKETS. If this is set up already to the maximum recommended value (2xCPU cores), the only way is to upgrade instance and use more sockets with more CPUs.

@rjha-splunk : Thank you so much for the update. We will let you know if client has any further questions


Question

Bro are you creating website for Ghost web editor or response for loading data??
Do you blocked me on telegram OR no longer use telegram?

I am unable to understand your language.

Instead of creating too commits use git commit --amend.

Hello, this data is mandatory for the update. Ninja Coder and I are chatting with the same account because my account was hacked. This is my new ID.
@Injectormain

ok


Windows: Pipline installer build

I think we're ready to go with this finally. Note that since multi executor was activated on the windows release slave, the regular smoke build is broken anyway, so we may as well switch to this sooner as later.
@maxtaco @jzila

The commits d4522f8846ac...f8313eaf3f31 introduce visual changes on linux. :mag_right: 1 changed

Changed: Paper_Key-Normal (before) (after)

The commits d4522f8846ac...9bba133de90d introduce visual changes on linux. :mag_right: 1 changed

Changed: Paper_Key-Normal (before) (after)

The commits d4522f8846ac...225b4d7dde4f introduce visual changes on linux. :mag_right: 1 changed

Changed: Paper_Key-Normal (before) (after)

I added the above helper function, I think we're ready to go.


Client fails to load code

https://github.com/ImagicTheCat/vRP/blob/0d5a18daa041ef4c95c8e808b6534102bd46c25f/vrp/lib/utils.lua#L27-L38
We have found that this seems to fail on the if f then check on the client-side only. We also can't seem to find a reason as to why it fails on that check.

No error ?

Errors weren't consistent. Some came from the same file at different points in the file, and there were no errors in that file. I suspect it has to do with local code = LoadResourceFile(rsc, path..".lua") not loading the code correctly? I know that's a cfx rpc but not sure if you have some insight on it?

There are no actual syntactic errors in the file, as it loads the file fine most of the time.

I don't think I can do much about it, but a good practice is to give the maximum amount of information you can about any issue you open (in this case, to show the actual errors).


Content script matching is very broad

In manifest.json, "matches" includes "https://*/*", meaning the extension runs on every website and not just chromium code source sites - is this necessary?

@psmarshall I did that and added support for ftp:// and file:// URLs, that way the extension could be used on sites other than the Chromium sites. For example, I use the file:// to check out or modify local .icon files I have in my repo.


Refactoring

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
✔

Fixed issues

@samdark  Thanks :+1:

@samdark  Thanks :+1:


Ambari 23362 trunk

What changes were proposed in this pull request?

Add Select All and Select None controls
Items of Levels list should look like entries of service logs table (i.e. with icons and colors)
Add 'filter list' feature.

How was this patch tested?
Manual and unit testing. All unit tests passing.
Please review Ambari Contributing Guide before opening a pull request.
Please review @aBabiichuk

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1475/
Test PASSed.


Detect if job is removed

I was wondering if there is a job event to detect when a job has been removed. My use case:
Sometimes I want to manually stop a job from the web ui, so I click the 'x' which drills down to a job.remove call. The issue is I now need to stop the worker tasks that are still running even after removing the job.

Maybe clicking the "x" could emit and event "deleted" ?

currently kue supports no job dependencies or ... so it is the application responsibility to build needed events and dependencies over Kue :)

@behrad what i meant is, if i click the "x" on kue UI is there a way to be notified on my code that the job was canceled, so i can keep my app up to date in case an "admin" decides to kill a job from within kue UI ?


Broken quote in multi-post content

If content is too long, it is broken into multiple posts in prepare_comment. However, the first line of the next post will not be quoted; and the break location can be not nice. (Example)
A trivial way to solve the first is to allow for the quote character
_current_content = _content[:10000 - len('\n\n--- continued below ---') - len(cfg_file['reddit']['signature'] - 1)]

then prepend it to the continued content:
_content = '>' + _content[len(_current_content):]

but a nicer solution would only use that as a fallback; before going that route, it would be awesome to look for the last index of '\n>' inside _current_content and cut it off there, so that broken paragraphs are also avoided.

Partly already implemeneted in polarbytebot_alpha.py, will aim to implemented your second suggestion.

Implemented cut-off on '\n' in polarbytebot_alpha.py


Property:collectionDescriptionID

Definition
Unique persistent identifier for the CollectionDescription

Existing property

Existing class

Existing property identifier

Format
Text

Required
Yes

Repeatable

Constraints
GUID?

Examples

Notes

This may be similar to a digital specimen identifier (NSId) for specimen, with the difference that there might quite often not be a physical collection identifier as compared to a specimen where there in principle always is one (usually attached as a barcode label) if a preserved specimen exists.

Closing this issue, as we agreed that it's a duplication of the PID property


get rid of restore staging dir by backing up/restoring within volume dir

Signed-off-by: Steve Kriss<EMAIL_ADDRESS>By running restic backup from within the volume's root directory, we can then restic restore directly into the volume root dir.
Also fixed a bug in the PVR controller, in the code that was checking if the restic initcontainer was running.

LGTM


Update to 3.1: Response caching

Don't  duplicate content and use global monikers if there is only one place to change. Apply monikers around the code containing     }).SetCompatibilityVersion(CompatibilityVersion.Version_2_2);

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b6728e59-93ec-891e-0416-94819296ad72
Version Independent ID: 5d581acc-c651-2112-844a-6b85dc5a99a6
Content: Response caching in ASP.NET Core
Content Source: aspnetcore/performance/caching/response.md
Product: aspnet-core
Technology: aspnetcore-performance
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@serpent5  the 3.1 version should probably have MVC and RP, each of them adding
        options.CacheProfiles.Add("Default30",


Validate codes with the latest possible catalogue version

As a user I would like the MiBi-Portal to validate my samples against the latest catalogue version

[ ] The date in column "Datum der Probenahme" defines which catalogue version should be used. Example: The MiBi-Portal contains four versions of AVV319: 01.01.2024, 01.04.2024, 01.07.2024 and 01.09.2024. The sample was taken on 24.07.2024. Thus the AVV319 version from 01.07.2024 needs to be used for validation of this sample. Check for every sample.

This feature was implemented in #21


bug: nvim_buf_get_name must not be called in a lua loop callback

Describe the bug
Error executing luv callback:
...k/.local/share/nvim/lazy/avante.nvim/lua/avante/path.lua:20: E5560: nvim_buf_get_name must not be called in a lua loop callback
stack traceback:
        [C]: in function 'nvim_buf_get_name'
        ...k/.local/share/nvim/lazy/avante.nvim/lua/avante/path.lua:20: in function 'filename'
        ...k/.local/share/nvim/lazy/avante.nvim/lua/avante/path.lua:39: in function 'get'
        ...k/.local/share/nvim/lazy/avante.nvim/lua/avante/path.lua:44: in function 'load'
        ...local/share/nvim/lazy/avante.nvim/lua/avante/sidebar.lua:1030: in function 'update_content'
        ...local/share/nvim/lazy/avante.nvim/lua/avante/sidebar.lua:1376: in function 'on_complete'
        ...ak/.local/share/nvim/lazy/avante.nvim/lua/avante/llm.lua:220: in function '_user_on_exit'
        .../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:241: in function '_shutdown'
        .../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:48: in function <.../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:39>

To reproduce
I had just installed avante for the first time, and ran :AvanteAsk. I was prompted for my API key (which I provided), and then I submitted my first question to the ask window.
You can find my setup/config files here: https://github.com/malakada/dotfiles/blob/main/nvim/init.lua
Expected behavior
That I get to use avante.
Installation method
I used the Lazy loader example from the README.
Environment
$ nvim -v
NVIM v0.10.1
Build type: Release
LuaJIT 2.1.1724232689

$ uname -a
Darwin hecuba.heatsynclabs.org 23.4.0 Darwin Kernel Version 23.4.0: Wed Feb 21 21:44:54 PST 2024; root:xnu-10063.101.15~2/RELEASE_ARM64_T6031 arm64

Additionally, my nvim environment is set up to use Python v3.12.
Repro
-- I don't know what to put here since I have lazy set up to pull from my plugins directory

I'm seeing this as well, just installed today so wasn't sure if it was something with my config

Same issue here.

It happens every time now.  I can't work!


[jest] support nested jest config files

👋 I'm trying to have our Rush monorepo use knip and running into a few things that are probably Rush specific. One of them is that we place our jest configs into a nested directory, config/jest.config.json. It looks like knip then tries to resolve all files relative to that config/* prefix causing something like setupFiles: ['<rootDir>/config/jest.setup.js'] to resolve to /config/config/jest.setup.js.
On the Rush side, they end up setting rootDir to build folder deep in their tooling, which means it isn't available outside of that context.
I think the intention with the knip code is to handle nested directories that have a root level jest config. What would be a good way to handle the Rush nested config folder? Maybe an additional config option, rootDir, that we could set to "../" or "/" to define where we resolve the root directory from?
Happy to submit a fix for this!

Indeed, the <rootDir> is the directory of the config file (config/jest.config.json).
Knip does not support custom options for plugins, so I'm not sure what we can do here at this point. It's also actually more of an issue with Rush, right? One option is to muse jest.config.js and then resolve and set the absolute path to jest.setup.js.

@webpro Thanks for the quick response! Yeah, it's definitely a Rush oddity. It's also a little out of spec for Jest, which also indicated that the config file should be in the root of the package.
I'll take a look at workarounds on our side, I think I might also be able to just declare rootDir in the jest config which will get overwritten by rush but could be used by knip.

Was able to get this working pretty easily with the following function that runs before we run knip,
async function updateJestConfig(packageDir) {
  const jestConfigPath = path.join(packageDir, 'config', 'jest.config.json')
  if (!existsSync(jestConfigPath)) {
    return
  }
  const jestConfig = JSON.parse(await readFile(jestConfigPath))
  jestConfig.rootDir = '..'
  await writeFile(jestConfigPath, JSON.stringify(jestConfig, null, 2))
}


https://unpkg.com/phosphor-icons link is broken

is redirecting to https://rio-unknown-store.productwiz.io/
Unknown Store
Variant Wizard does not know the store you are trying to use the app with
Please try opening up the app again through your Shopify admin. If you are still experiencing any issues, please contact us at<EMAIL_ADDRESS>We will resolve this!
Pro tip: If you have bookmarked the app, please ensure that the ?shop= query is present in your bookmarked URL. An example would be https://app.productwiz.io/?shop=loja.myshopify.com.

seems working fine now

They were hacked. This would probably have affected a large number of hosted packages on the platform. https://twitter.com/DonFeebs/status/1427333203627548674


Add etcd liveness probes

[ ] Investigate what liveness and readiness probes are used by  other etcd operators

Do readiness probes make sense, since etcdclients talk to all nodes anyway.

[ ] Devise a  test to simulate a "stuck" etcd node
[ ] Add liveness probe by calling etcdctl or by using etcd client library

Add documentation explaining our decision to not install liveness and readiness probes for the etcd nodes.


Parsing to an array of a class with PropertyChanged.Fody results in "Unexpected member type"

In my new UWP/UAP app I have the following JSON I want to deserialize. It's coming from a web service, so there's no way to change it.
[
	{
		"id": "108",
		"title": "Felix Breidenstein",
		"tags": "blog",
		"spout": "spouts\\rss\\feed",
		"params": {
			"url": "https:\/\/www.felixbreidenstein.de\/feed.xml"
		},
		"filter": "",
		"error": "2016-01-06 20:30:07error loading feed content: cURL error 35: SSL connect error",
		"lastentry": null,
		"icon": null
	},
	{
		"id": "107",
		"title": "Markus Ritzmann",
		"tags": "blog",
		"spout": "spouts\\rss\\feed",
		"params": {
			"url": "http:\/\/blog.markus-mail.com\/feed\/"
		},
		"filter": "",
		"error": "2016-01-06 20:30:07error loading feed content: cURL error 35: SSL connect error",
		"lastentry": null,
		"icon": null
	},
	...
]

Therefore I'm using the following code to deserialize this object:
 var parsedJson = await Task.Factory.StartNew(() => JsonConvert.DeserializeObject<Class1[]>(jsonstring);

Class1 is looking like this:
[PropertyChanged.ImplementPropertyChanged]
class Class1
    {
        [JsonProperty("id")]
        public string Id { get; set; }

        [JsonProperty("title")]
        public string Title { get; set; }
        …
    }

If I comment out the first line of Class1, it is deserializing perfectly. However, if the line is not commented out, JsonConvert throws an System.Exception with the message: Unexpected member type.
I'm using the newest versions of each NuGet package.

Fixed here - https://github.com/JamesNK/Newtonsoft.Json/issues/771
Use 7.0.1 until it is released.

https://www.nuget.org/packages/Newtonsoft.Json/8.0.2


Issue on page /notebooks/05-Python_I.html

in cfexercises1.py the function foo_3 will not order the three values if the smallest value is in the z position in the function.
def foo_3(x, y, z):
    if x > y:
        tmp = y
        y = x
        x = tmp
    if y > z:
        tmp = z
        z = y
        y = tmp
    return [x, y, z]

foo_3(8,6,1)

returns: (6, 1, 8)

This may be an intentional bug 😄 I would argue though that using the tmp variable is a missed opportunity to show off Python unpacking:
def foo_3(x, y, z):
    if x > y:
         y, x = x, y
    if y > z:
         y, z = z, y
    return [x, y, z]

This does not work for the exceptional case where z is the lowest value. The following code should solve the problem (but sorts it in descending order):
def foo_3(x, y, z):
    if z > y and y > x:
        x, y, z = z, y, x
    if y > x and x > z:
        x, y ,z = y, x, z
    return [x, y, z]

Mine wasn't intended to fix the bug (which may be an intentional feature), but just to point out that the tmp variable can be avoided using Python features.

@hel0122 , do you mind checking and proposing a solution for this?


Cannot create estimations for model order other than 5

Using the estimate command for any other ngram model results in a segfault
./estimate  large_lang.txt  --tmp tmp_hi --ram 0.25 --out index.bin
estimating with 268435456/17179869184 bytes of RAM (1.5625%)
{"dataset":"2021-03-15", "order":4, "RAM":268435456, "threads":12, "counting": {block size = 2236962
sorting took 0.505281 [sec]
block size = 745603
sorting took 0.128015 [sec]
        counting_writer thread stats:
        flushed blocks: 2
        O time: 0.347683
        CPU time: 0.633296
        reader thread stats:
        CPU time: 1.42818 [sec]
        I time: 0.32765 [sec]
"CPU":1.42818, "I":0.32765, "O":0.347683, "total":1.97759}, "adjusting": {vocabulary size: 94357
merging 2 files
        using min. load size of 53687088 because not enough RAM is available
num_ngrams_per_block = 2236962 ngrams
MERGE DONE: 2916244 N-grams
        time waiting for disk = 1.9108e-05 [sec]
        smoothing time: 0.090805 [sec]
        adjusting_writer thread stats:
        flushed blocks: 2
        write time: 0.180041
number of ngrams:
1-grams: 94357
2-grams: 856047
3-grams: 0
4-grams: 5021288
total num. grams: 5971692
total num. tokens: 3360614
Here is the stats
"CPU":0.249942, "I":0.0514812, "O":0.180041, "total":0.410131}, "last": {processing 2 blocks
Segmentation fault: 11```

From what I can see somehow the number of ngrams  for N -1 gram for N another gram is becoming 0

Hi and thanks.
Now fixed by your pull request.


Hope you can give an example of the usage process

install Pinpoint：

git clone https://github.com/pinpoint-apm/pinpoint-docker.git
cd pinpoint-docker
docker-compose pull && docker-compose up -d

Install Collector Agent

docker run -itd -p 9999:9999  --env-file ./env.list ghcr.io/pinpoint-apm/pinpoint-c-agent/collector-agent:latest

Then I want to monitor the c++ program.

$ mkdir build
$ cd build
$ cmake .. && make
$ ./test_pinpoint.cpp

I did not modify test_pinpoint.cpp, but I did not find any application on the 8080 page.
Can you give the complete instructions for using the monitoring C++ program started with docker?

please enable agent into debug mode.  Set agent_info.inter_flag = 1
PPAgentT agent_info = {
    "tcp:<IP_ADDRESS>:9999", 1000, -1, 1700, 1, NULL, NULL, NULL};

then, share the output to me.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

have you check <IP_ADDRESS>:19999, was it open ?
send data error:(Connection reset by peer) fd:(4)

your collect-agent is run by docker run -itd -p 9999:9999 , so try 9999

yes , 19999 is opend.I set the port to 19999. Before the modification, the port was 9999, but it was the same error.
在 2023-09-08 15:47:54，"eeliu" @.***> 写道：
have you check <IP_ADDRESS>:19999, was it open ?
send data error:(Connection reset by peer) fd:(4)
your collect-agent is run by docker run -itd -p 9999:9999 , so try 9999
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

show docker ps | grep collector-agent

ef718fd3ef88   ghcr.io/pinpoint-apm/pinpoint-c-agent/collector-agent:latest   "CollectorAgent"         49 minutes ago   Up 49 minutes   <IP_ADDRESS>:19999->9999/tcp, :::19999->9999/tcp                                                                                vigorous_brattain
I also tested to turn off the original agent, and it didn't work.
docker ps:
ef718fd3ef88   ghcr.io/pinpoint-apm/pinpoint-c-agent/collector-agent:latest   "CollectorAgent"         51 minutes ago   Up 51 minutes   <IP_ADDRESS>:19999->9999/tcp, :::19999->9999/tcp                                                                                vigorous_brattain
301e6430c44d   pinpointdocker/pinpoint-quickstart                             "catalina.sh run"        2 days ago       Up 30 hours     <IP_ADDRESS>:8085->8080/tcp, :::8085->8080/tcp                                                                                pinpoint-quickstart
699e4f117fd6   pinpointdocker/pinpoint-agent:2.5.2                            "/usr/local/bin/conf…"   2 days ago       Up 2 minutes                                                                                pinpoint-agent
06e439817c7a   pinpointdocker/pinpoint-batch:2.5.2                            "sh /pinpoint/script…"   2 days ago       Up 30 hours                                                                                pinpoint-batch
58a28dfa1c8e   pinpointdocker/pinpoint-web:2.5.2                              "sh /pinpoint/script…"   2 days ago       Up 30 hours     <IP_ADDRESS>:8080->8080/tcp, :::8080->8080/tcp, <IP_ADDRESS>:9997->9997/tcp, :::9997->9997/tcp                                                                                pinpoint-web
2cd3372dfeae   pinpointdocker/pinpoint-collector:2.5.2                        "sh /pinpoint/script…"   2 days ago       Up 30 hours     <IP_ADDRESS>:9991-9996->9991-9996/tcp, :::9991-9996->9991-9996/tcp, <IP_ADDRESS>:9995-9996->9995-9996/udp, :::9995-9996->9995-9996/udp                                                                 pinpoint-collector
d86ddc10a385   pinpointdocker/pinpoint-flink:2.5.2                            "/docker-bin/docker-…"   2 days ago       Up 30 hours     6123/tcp, <IP_ADDRESS>:6121-6122->6121-6122/tcp, :::6121-6122->6121-6122/tcp, <IP_ADDRESS>:19994->19994/tcp, :::19994->19994/tcp, 8081/tcp                                                             pinpoint-flink-taskmanager
6fc47e5d6033   pinpointdocker/pinpoint-flink:2.5.2                            "/docker-bin/docker-…"   2 days ago       Up 30 hours     6123/tcp, <IP_ADDRESS>:8081->8081/tcp, :::8081->8081/tcp                                                                                pinpoint-flink-jobmanager
c38715c1ba2b   pinpointdocker/pinpoint-hbase:2.5.2                            "/bin/sh -c '/usr/lo…"   2 days ago       Up 30 hours     <IP_ADDRESS>:16010->16010/tcp, :::16010->16010/tcp, <IP_ADDRESS>:16030->16030/tcp, :::16030->16030/tcp, <IP_ADDRESS>:60000->60000/tcp, :::60000->60000/tcp, <IP_ADDRESS>:60020->60020/tcp, :::60020->60020/tcp   pinpoint-hbase
b8529063bc3a   zookeeper:3.4.13                                               "/docker-entrypoint.…"   2 days ago       Up 30 hours     2888/tcp, 3888/tcp, <IP_ADDRESS>:32774->2181/tcp, :::32774->2181/tcp                                                                                pinpoint-docker-zoo3-1
b745dc25cb49   zookeeper:3.4.13                                               "/docker-entrypoint.…"   2 days ago       Up 30 hours     2888/tcp, 3888/tcp, <IP_ADDRESS>:32775->2181/tcp, :::32775->2181/tcp                                                                                pinpoint-docker-zoo1-1
c06215334500   pinpointdocker/pinpoint-mysql:2.5.2                            "docker-entrypoint.s…"   2 days ago       Up 30 hours     <IP_ADDRESS>:3306->3306/tcp, :::3306->3306/tcp, 33060/tcp                                                                                pinpoint-mysql
738db9d7ffd6   zookeeper:3.4.13                                               "/docker-entrypoint.…"   2 days ago       Up 30 hours     2888/tcp, 3888/tcp, <IP_ADDRESS>:32776->2181/tcp, :::32776->2181/tcp                                                                                pinpoint-docker-zoo2-1
在 2023-09-08 16:07:42，"eeliu" @.***> 写道：
show docker ps | grep collector-agent
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

hmm, please show me the log of collector-agent, it locates into /tjmp

[2023-09-08 07:19:56.457027286]  INFO SocketType:tcp Address:<IP_ADDRESS>:19999  StatAddress:dev-pinpoint:9992 SpanAddress:dev-pinpoint:9993 AgentAddressdev-pinpoint:9991 WebPorts:80  LoggerLevel:DEBUG LoggerDir:/tmp/ AgentChannelSize:1000 SpanStreamParallelismSize:2 AgentReTryTimeout:10ns PingInterval:300 StatInterval:5 SpanTimeWaitSec:10 MetaDataTimeWaitSec:10 Pid:0 StartTime:1694157596 ServerType:1700 Container:false
[2023-09-08 07:19:56.458081963] DEBUG listen: tcp address: <IP_ADDRESS>:19999
在 2023-09-08 16:22:20，"eeliu" @.***> 写道：
hmm, please show me the log of collector-agent, it locates into /tmp
—
Reply to this email directly, view it on GitHub, or unsubscribe.

在 2023-09-08 16:22:20，"eeliu" @.***> 写道：
hmm, please show me the log of collector-agent, it locates into /tmp
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

From your https://github.com/pinpoint-apm/pinpoint-c-agent/issues/522#issuecomment-1711290974, agent to collector-agent container is ok.
Please share the logging of  collector-agent.
docker exec -it collector-agent-container /bin/sh
 # tail /tmp/collector.log

[2023-09-08 09:01:12.938232788]  WARN Dail dev-pinpoint:9992 failed err:context deadline exceeded appid=CPP_APP
[2023-09-08 09:01:17.488914211]  WARN connect:dev-pinpoint:9993 failed. context deadline exceeded
[2023-09-08 09:01:17.488932647]  WARN connect:dev-pinpoint:9993 failed. context deadline exceeded
[2023-09-08 09:01:17.941590707] DEBUG connect StatAddress:dev-pinpoint:9992 appid=CPP_APP
[2023-09-08 09:01:22.945718275]  WARN Dail dev-pinpoint:9992 failed err:context deadline exceeded appid=CPP_APP
[2023-09-08 09:01:27.949675236] DEBUG connect StatAddress:dev-pinpoint:9992 appid=CPP_APP
[2023-09-08 09:01:32.491830988]  WARN connect:dev-pinpoint:9993 failed. context deadline exceeded
[2023-09-08 09:01:32.491841706]  WARN connect:dev-pinpoint:9993 failed. context deadline exceeded
[2023-09-08 09:01:32.953624042]  WARN Dail dev-pinpoint:9992 failed err:context deadline exceeded appid=CPP_APP
[2023-09-08 09:01:37.957679091] DEBUG connect StatAddress:dev-pinpoint:9992 appid=CPP_APP
在 2023-09-08 16:55:44，"eeliu" @.***> 写道：
From your #522 (comment), agent to collector-agent container is ok.
Please share the logging of collector-agent.
docker exec -it collector-agent-container /bin/sh
tail /tmp/collector.log
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

dev-pinpoint should be your pinpointdocker/pinpoint-collector:2.5.2 network address. eg: host ip address (<IP_ADDRESS>).
Then , restart collector-agent:latest

Thanks, it worked！！！
在 2023-09-08 17:16:36，"eeliu" @.***> 写道：
dev-pinpoint should be your pinpointdocker/pinpoint-collector:2.5.2 network address. eg: host ip address (<IP_ADDRESS>).
Then , restart collector-agent:latest
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

close as done


Error with higher level components at depth

import { H, R } from 'dot-dom';

function Page1() {
  return H('div');
}

function Page2() {
  return H(Page1);
}

R(
  H(Page2),
  document.body,
);

Throws this error:
Uncaught DOMException: Failed to execute 'createElement' on 'Document': The tag name provided ('function Page1() {
  return (0, _dotDom.H)('div');
}') is not a valid name.
    at http://localhost:3000/bundle.js:5425:51
    at Array.map (native)
    at render (http://localhost:3000/bundle.js:5374:38)
    at Object.<anonymous> (http://localhost:3000/bundle.js:4177:15)
    at __webpack_require__ (http://localhost:3000/bundle.js:21:30)
    at Object.defineProperty.value (http://localhost:3000/bundle.js:12114:18)
    at __webpack_require__ (http://localhost:3000/bundle.js:21:30)
    at module.exports.ctor.super_ (http://localhost:3000/bundle.js:67:18)
    at http://localhost:3000/bundle.js:70:10

Flagging this line first:
      ? document.createTextNode(vnode) : document.createElement(vnode.E);

It seems that I have to nest them.. but why.
Valid:
import { H, R } from 'dot-dom';

function Page1() {
  return H('div');
}

function Page2() {
  return H('div', H(Page1));
}

R(
  H(Page2),
  document.body,
);

Not Valid:
import { H, R } from 'dot-dom';

function Page1() {
  return H('div');
}

function Page2() {
  return H(Page1);
}

R(
  H(Page2),
  document.body,
);

My hack:
const o = () => (vnode.E && vnode.E.call ?                                    // If the vnode is a functional component, expand
          vnode.E(                                           // it and replace the current vnode variable.

            vnode.P,                                                  // 1. The component properties
            _state[0],                                                // 2. The stateful component state
            (newState) =>                                             // 3. The setState function

              Object.assign(                                          // First we update the state part of the record
                _state[0],                                            // Note: When we defined the variable we kept the
                newState                                              //       reference to the record array
              ) &&

              render(                                                 // We then trigger the same render cycle that will
                vnodes,                                               // update the DOM
                dom,
                _npath
              )

          ) : vnode);

        vnode = o();
        vnode = o();
        vnode = o();

@wavesoft any thoughts on this one? ^^

Oh, blast I didn't read this. Yeah I know what causes this 😞
This is caused by a size-vs-feature tradeoff and must definitely be mentioned in the Caveats. I saw you figured out that the functional component is evaluated only once here: https://github.com/wavesoft/dot-dom/blob/master/src/dotdom.js#L105
Therefore, the library "assumes" that it will receive some VNode as a response and not a nested component. That's why return H('div', H(SubComponent)) works and return H(SubComponent) doesn't.
A recursive approach as the one you suggested seems to be a good idea, but the problem is that a stateful component needs a rendered node on which to store the state record. The bottom line is that your solution works, but the first + child components will share the same state.
Though from the top of my I head I think doing something like _npath + '>' would fix that issue.

@wavesoft something to be considered for sure. Do you have an email I can reach you at? I dont really use linkedin. Yes, adding that to the path would seem to work in this case.

Hey @SilentCicero , I just created a gitter for the project, you can find me there 😄

@wavesoft checkout the PR ;)

This is still not fully addressed so I am adding the bug label

This is now fixed on the latest 0.3.0 release 🎉


Cameras returned by FindObjectsByType are not necessarily in the same order as when compiling the project.

Closed for now until we have bandwidth to resolve the merge conflicts.


CAL ID displayed incorrectly

Similar to #88 .. Examples to be provided by KG.

Version 1.9.4, does not write the DM19 response from all the ECUs. Resulting in an error when tool compares Report Calibrations with Vehicle Calibrations.

The expectation was to receive DM19 responses from multiple modules but there was only one response to DM19. I had reported a similar issue last year on v1.3 and you fixed it in v1.5. ( Details in the attachment)
The adapter used was for testing v1.9.4 is nexiq usb 2. It has been a few weeks since the tool was tested, I am unable to find the requested CAN log in temp folder now. Please let me know If needed, I can try to connect to the tool again and see if it populates the CAN log/.asc file that you requested in the below email.
Regards,
Karthik Govindaraj
From: Joe Batt @.>
Sent: Friday, November 10, 2023 7:51 AM
To: Equipment-and-Tool-Institute/iumpr @.>
Cc: GovindarajKarthik @.>; Comment @.>
Subject: Re: [Equipment-and-Tool-Institute/iumpr] CAL ID displayed incorrectly (Issue #90)
This isn't the first report of this problem, so I'm not arguing that there isn't a problem, but I need more to understand this issue. Your report only includes one response to a global request for DM19 and the response appears to be correctly decoded. Our testing is working with multiple modules, one has multiple DM19 entries and the other is a single.
Were there multiple responses? If the tool is missing responses, then I need a CAN log to understand why. (find the latest .asc file in "%TEMP%") We may need to be more lenient of the TP timeouts. Maybe the tool failed to log TP errors to the report.
What adapter are you using. High latency adapters will have more timing issues resulting in more TP failures.

Reply to this email directly, view it on GitHubhttps://github.com/Equipment-and-Tool-Institute/iumpr/issues/90#issuecomment-1805677128, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJUH22VLFQ3ZTZBX7ZZBPU3YDYPKVAVCNFSM6AAAAAA6TFWBFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBVGY3TOMJSHA.
You are receiving this because you commented.Message ID: @.***>
If you are not the addressee, please inform us immediately that you have received this e-mail by mistake, and delete it. We thank you for your support.

Your github "comment via email" doesn't include an attachment.  That may be a github issue.
Yes, I need a .asc file to diagnose this.  It is probably a TP timing issue.  IUMPR 1.5.0 used the adapter TP.  Starting with 1.9.0 IUMPR implements TP to improve error reporting of bad TP.

I’ve seen emails with confirming complaints.

The J1939 routines copied from the J1939-84 project use 750 ms as the response timeout.  It had been 2500 ms.  Examples provided took 756.225 ms (using a 50 ms interpacket delay).  I recommend switching the timeout back to 2500 ms.

The multiple DM19 responses are on the screen report, but not in the file.  I am able to reproduce this reliably now.

The new J1939 stack was returning responses in the order first response, not the order the the final packet.  The timestamps were then being added to the file out of order, causing an error condition in the logs.  Sorting the responses by final packet timestamp allows them to be added to the file in the correct order avoiding the error.

Still waiting for confirmation of fix.

This issue is still not resolved in version 1.9.5.
Karthik Govindaraj
From: ericthomasswenson @.>
Sent: Friday, December 15, 2023 1:09 PM
To: Equipment-and-Tool-Institute/iumpr @.>
Cc: GovindarajKarthik @.>; Comment @.>
Subject: Re: [Equipment-and-Tool-Institute/iumpr] CAL ID displayed incorrectly (Issue #90)
Still waiting for confirmation of fix.

Reply to this email directly, view it on GitHubhttps://github.com/Equipment-and-Tool-Institute/iumpr/issues/90#issuecomment-1858294498, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJUH22RZG2ICG6HILBHWUFDYJSG2BAVCNFSM6AAAAAA6TFWBFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJYGI4TINBZHA.
You are receiving this because you commented.Message ID: @.***>
If you are not the addressee, please inform us immediately that you have received this e-mail by mistake, and delete it. We thank you for your support.

1.9.5 appears to have corrected this issue.


Update gather-logs script

@jeremiahsnapp Am I correct in assuming that these changes represent the newest version of the script that support has been using and testing on a daily basis with customers?
If so, :+1:.

@stevendanna Yes most of these changes are what we've already been manually sending to customers. There are only three relatively new features.

using rpm/dpkg to gather versions of Chef products
gathering the tail of<EMAIL_ADDRESS>from Chef Server and Analytics Server
gathering rabbitmq list_queues stats from Chef Server and Analytics Server

IMO, these new features have been sufficiently tested.
It would be great if this PR could be merged before a new release of Chef Server.
Thanks!

@jeremiahsnapp Would you mind updating the commit message to include the new features.  perhaps something like:
Multiple updates to the gather-logs script

This includes various improvements and fixes
from support engineers, including:

- using rpm/dpkg to gather versions of Chef Products
- gathering the tail of RabbitMQs logs
- gathering RabbitMQ queues stats

ChangeLog-Entry: New gather-log script with additional rabbitmq debugging
information.
``

@jeremiahsnapp I've added a RABBITMQ_NODENAME variable to the shell script we include and changed the gather-logs script to use it instead of referring directly to rabbitmq@localhost.
This should address the concern that @marcparadise had.
Other than the commit message update I mentioned, I don't see any other blockers to merging this.

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
GitHub Users Who Are Not Authorized To Contribute
The following GitHub users do not appear to have signed a CLA:

@glasschef

Please sign the CLA here.

Hi. Your friendly Curry bot here. Just letting you know that all commit authors have become authorized to contribute. I have added the "Signed CLA" label to this issue so it can easily be found in the future.

I reworked this PR so now it's made up of smaller, more descriptive commits.
@mp @stevendanna thanks for the heads up about rabbit name change. I'm using a glob now to grab those logs.
I added an entry to the CHANGELOG.md too.


🐛 Bug Report: Feature and Plugin issue templates link to Code of Conduct but say Contributor Guidelines

📜 Description
When creating an issue for a Feature of Plugin the section for the Code of Conduct says "I have read the Contributing Guidelines" but links to the Code of Conduct correctly.
👍 Expected behavior
The text should say: "I have read the Conde of Conduct"
👎 Actual Behavior with Screenshots
When creating an issue for a Feature of Plugin the section for the Code of Conduct says "I have read the Contributing Guidelines" but links to the Code of Conduct correctly.
Feature: https://github.com/backstage/backstage/blame/master/.github/ISSUE_TEMPLATE/feature.yaml#L44
Plugin: https://github.com/backstage/backstage/blame/master/.github/ISSUE_TEMPLATE/plugin.yaml#L42
It's not easy to link to these files, it only shows the rendered version so had to use blame to get links 🤔
👟 Reproduction steps

Got to create a Feature or Plugin issue
Scroll down to the Code of Conduct section

Notice: The text says: "I have read the Contributing Guidelines"
📃 Provide the context for the Bug.
No response
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, I don't have time to work on this right now

You have a small type in your Expected Behavior section

"I have read the Conde of Conduct"

I have used the following in my PR

"I have read the Code of Conduct"

Good catch @kurtaking! Thanks for running with this 🚀


Azure OpenAI Api not working - presence_penalty's default should be 0 (instead of null)

For my generation call to Azure OpenAI, I am getting below error, and I can see that in the payload, presence_penalty is set to null, which is a default value set in src\LLMProviders\langchain\azureOpenAIChat.tsx. From what I see, the number should be 0 or it'd be even nicer if we have a slider control in the config page of the Text Generator plugin then use that value.

This should get fixed in the next release (0.6.14)
Thanks for reporting this issue

Thank you for working on this issue!


mwc-button height changes when icon added

I'm submitting a:

[ X] bug report
[ ] feature request

What OS are you using?
Mac OS HighSierra
What browser(s) is this bug affecting:
Chrome Version 78.0.3904.108 (Official Build) (64-bit)
Current behavior:
Have two mwc buttons next to each other.  One has an icon added other does not.  When icon is added then they do not align vertically.  The one with the icon shifts slightly up.
Expected behavior:
Both buttons should have stayed aligned.
Steps to reproduce:
Related code:
        <div class="row">
          <mwc-button outlined id="male" label="Male"  dense icon="clear" @click="${e =>  this._setbutton(e)}" ></mwc-button>
          <mwc-button outlined id="female" label="Male"  dense icon="" @click="${e =>  this._setbutton(e)}" ></mwc-button>
        </div>

Other information:

Fixed in M3


Airflow 1639 Fix Fernet error handling

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
When the encrypted string cannot be decryted using Fernet for some reason, an error will be thrown. In Python 3.6.2 the .message attr is not available. By casting the ValueError to a string, the message will be extracted from the Error.
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-1639

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #2629 into master will increase coverage by 0.09%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #2629      +/-   ##
==========================================
+ Coverage   71.14%   71.23%   +0.09%
==========================================
  Files         150      150
  Lines       11742    11742
==========================================
+ Hits         8354     8365      +11
+ Misses       3388     3377      -11

Impacted Files
Coverage Δ

airflow/models.py
87.15% <0%> (ø)
:arrow_up:

airflow/jobs.py
78.07% <0%> (+0.45%)
:arrow_up:

airflow/utils/helpers.py
56.32% <0%> (+2.87%)
:arrow_up:

airflow/task_runner/bash_task_runner.py
100% <0%> (+6.66%)
:arrow_up:

Continue to review full report at Codecov.

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


Consolidate include and select code

There's currently a lot of duplication, would be nice to reduce it

3493c6c9e6a1f029b37470403a54a6c444cf6bcb


tempConverter.cpp

Created a Basic C++ Program to Convert Temperature from Celsius to Fahrenheit

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


Correct link addresses

Hi,
Some links are pointing to 404 error pages. This PR just corrects their addresses.

Thanks!


rocket-mqtt部置在多台服务器上，如何配置接入实现负载均衡

共用一个rocketmq集群，rocketmq-mqtt部署在多台服务器上，每台rocketmq-mqtt设置相同的first topic, 不同的 notify topic，设备接入不同的rocketmq-mqtt服务器，这样是否行?

If different notification topics are configured, then each rocketmq-mqtt event notification will be independent, and they will appear to be independent clusters. Even if the same first topic is set, there will be problems. It is recommended to use traditional load balancing to implement load balancing of mqtt service.


Add PoissonSolver1DRadial Tests

Pull Request
Description
This pull request addresses #119

[ ] make sure you are pulling from a dev branch on your fork
[ ] check for code linting

Looks like you have a typo in test_computetools.py that is making the tests fail:
E     File "/home/travis/build/NRL-Plasma-Physics-Division/turbopy/tests/test_computetools.py", line 294
E       def test_init_poisson():
E                              ^
E   IndentationError: unindent does not match any outer indentation level


[Epic] Production integration of cuBLAS, cuDNN, and Triton

MS2 Epic level item - to track library integration work.

[ ] P1 cuBLAS integration for GEMMs - needs owner
[ ] P1 Triton integration @burmako
[ ] P2 cuDNN for MHA (flash attention) integration

Design update from @ezhulenev scheduled for tomorrow.

@julianwa @mattwalsh I think we should rewrite this Epic to include:
P1 - Triton integration
P1 - cublas for GEMMs
P2 - cuDNN for MHA (flash attention)
what do you think?

I think we should rewrite this Epic to include: P1 - Triton integration P1 - cublas for GEMMs P2 - cuDNN for MHA (flash attention)
what do you think?

That's fine by me. Production integration of cuBLAS, cuDNN, and Triton.

Updated per today's discussion.
@burmako Please help to add any tasks you are working on to the task list above.
@mattwalsh @julianwa to find an owner for cuBLAS integration work.

Adding @vmurali who is picking up some cublas work.


Add "announcements.pdf"

Announcements.pdf will contain all the announcements for the current version. Announcements.pdf will contain announcements that are also seen here

Finished. Please check the release.

It's good.


#5121: Fixes rescanning of page paths for large sites and makes publi…

…shing pages a lot faster.
Check these before submitting new pull requests

[ ] I read the guidelines for contributing linked above

[ ] PHP-only files follow our coding style; in order to do that use php-cs-fixer - http://cs.sensiolabs.org/ - as follows:
php-cs-fixer fix --config=<webroot>/.php_cs.dist <filename>

If all the above conditions are met, feel free to delete this whole message and to submit your pull request, and... Thank you, your help is really appreciated!

I think there might be an issue with this – it looks like a test is failing.

No - one of the tests failed with this pull request.

PagePathTest::testCustomCanonicalPagePathWithAutoGeneratedChildren
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'/custom-about/contact-us/totally-extreme'
+'/about/contact-us/totally-extreme'
/home/travis/build/concrete5/concrete5/tests/tests/Core/Page/PagePathTest.php:270

Is there any current documentation to how to get the tests run locally? The README.md seems to be outdated.

I've updated the README.md file within the tests/ directory:
https://github.com/concrete5/concrete5/blob/develop/tests/README.md

@aembler @bafrank this fix worked for me. Went from > 30 seconds to 1 second. 👍

Anyone else want to try fixing this so that the tests pass? Can't really let a fix for an issue in that actively breaks the tests that it's specifically related to. It's possible that the fix is just fine and the tests need tweaking.

Thanks for the work here @bafrank. Please get this in working order and reopen this pull request when you have a chance.

FYI I believe this has been taken care of by this:
https://github.com/concrete5/concrete5/pull/5461

Fixed: Update page on large site is always slow
Not fixed: Change page paths on large site is too slow


PLNSRVCE-532: Add new fields to the components in the generated SBOM file

New fields that are being added:

.components[].purl
.components[].properties[]

package:type
package:language

{
    "bomFormat": "CycloneDX",
    "specVersion": "1.4",
    "version": 1,
    "components": [
        {
            "publisher": "central",
            "group": "io.vertx",
            "name": "vertx-bridge-common",
            "version": "4.2.7",
            "type": "library",
            "purl"<EMAIL_ADDRESS>            "properties": [
                {
                    "name": "package:type",
                    "value": "maven"
                },
                {
                    "name": "package:language",
                    "value": "java"
                }
            ]
        }
    ]
}

Quick draft, we still need to figure out how to properly generate the PURLs and how to determine the package type.

/retest

/retest

/retest

This is probably good to go, with @Michkov signing off, but I don't know this area of the code well enough yet to say for certain from my point of view, and given we are still trying to get our footing with now having some form of e2e's in place (though we still have more in flight) and repo stability, I'd like for @stuartwdouglas to sign off on this before we merge.
I've assigned him / asked for his review.

thanks @stuartwdouglas


added fontsizes for JMLR

I just added font sizes for JMLR (which uses the weird 10.95pt font size)

I just added layout for beamer, too. :)


Klipper is unable to upgrade chart with PDB

https://github.com/cockroachdb/helm-charts/issues/270#issuecomment-1490834577
https://github.com/k3s-io/klipper-helm/blob/5e763524fd8cab4790289e7220e04a6d2a016adc/entry#L63
Install logs on k3s 1.26.3
if [[ ${KUBERNETES_SERVICE_HOST} =~ .*:.* ]]; then
	echo "KUBERNETES_SERVICE_HOST is using IPv6"
	CHART="${CHART//%\{KUBERNETES_API\}%/[${KUBERNETES_SERVICE_HOST}]:${KUBERNETES_SERVICE_PORT}}"
else
	CHART="${CHART//%\{KUBERNETES_API\}%/${KUBERNETES_SERVICE_HOST}:${KUBERNETES_SERVICE_PORT}}"
fi

set +v -x
+ [[ '' != \t\r\u\e ]]
+ export HELM_HOST=<IP_ADDRESS>:44134
+ HELM_HOST=<IP_ADDRESS>:44134
+ helm_v2 init --skip-refresh --client-only --stable-repo-url https://charts.helm.sh/stable/
+ tiller --listen=<IP_ADDRESS>:44134 --storage=secret
Creating /home/klipper-helm/.helm
Creating /home/klipper-helm/.helm/repository
Creating /home/klipper-helm/.helm/repository/cache
Creating /home/klipper-helm/.helm/repository/local
Creating /home/klipper-helm/.helm/plugins
Creating /home/klipper-helm/.helm/starters
Creating /home/klipper-helm/.helm/cache/archive
Creating /home/klipper-helm/.helm/repository/repositories.yaml
Adding stable repo with URL: https://charts.helm.sh/stable/
Adding local repo with URL: http://<IP_ADDRESS>:8879/charts
$HELM_HOME has been configured at /home/klipper-helm/.helm.
Not installing Tiller due to 'client-only' flag having been set
++ timeout -s KILL 30 helm_v2 ls --all '^crdb$' --output json++
jq -r '.Releases | length'
[main] 2023/03/30 19:41:24 Starting Tiller v2.17.0 (tls=false)
[main] 2023/03/30 19:41:24 GRPC listening on <IP_ADDRESS>:44134
[main] 2023/03/30 19:41:24 Probes listening on :44135
[main] 2023/03/30 19:41:24 Storage driver is Secret
[main] 2023/03/30 19:41:24 Max history per release is 0
[storage] 2023/03/30 19:41:24 listing all releases with filter
+ V2_CHART_EXISTS=
+ [[ '' == \1 ]]
+ [[ v3 == \v\2 ]]
+ [[ -f /config/ca-file.pem ]]
+ [[ -n '' ]]
+ shopt -s nullglob
+ helm_content_decode
+ set -e
+ ENC_CHART_PATH=/chart/crdb.tgz.base64
+ CHART_PATH=/tmp/crdb.tgz
+ [[ ! -f /chart/crdb.tgz.base64 ]]
+ return
+ [[ template != \d\e\l\e\t\e ]]
+ helm_repo_init
+ grep -q -e 'https\?://'
+ [[ helm_v3 == \h\e\l\m\_\v\3 ]]
+ [[ cockroachdb == stable/* ]]
+ [[ -n https://charts.cockroachdb.com ]]
+ helm_v3 repo add crdb https://charts.cockroachdb.com
"crdb" has been added to your repositories
+ helm_v3 repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "crdb" chart repository
Update Complete. ⎈Happy Helming!⎈
+ helm_update template --namespace crdb --repo https://charts.cockroachdb.com --version 10.0.7 --debug
+ [[ helm_v3 == \h\e\l\m\_\v\3 ]]
++ helm_v3 ls --all -f '^crdb$' --namespace crdb --output json
++ jq -r '"\(.[0].app_version),\(.[0].status)"'
++ tr '[:upper:]' '[:lower:]'
+ LINE=22.1.6,deployed
+ IFS=,
+ read -r INSTALLED_VERSION STATUS _
+ VALUES=
+ for VALUES_FILE in /config/*.yaml
+ VALUES=' --values /config/values-01_HelmChart.yaml'
+ [[ template = \d\e\l\e\t\e ]]
+ [[ 22.1.6 =~ ^(|null)$ ]]
+ [[ deployed =~ ^(pending-install|pending-upgrade|pending-rollback)$ ]]
+ [[ deployed == \d\e\p\l\o\y\e\d ]]
+ echo 'Already installed crdb'
Already installed crdb
+ [[ helm_v3 == \h\e\l\m\_\v\3 ]]
+ helm_v3 mapkubeapis crdb --namespace crdb
2023/03/30 19:41:25 Release 'crdb' will be checked for deprecated or removed Kubernetes APIs and will be updated if necessary to supported API versions.
2023/03/30 19:41:25 Get release 'crdb' latest version.
2023/03/30 19:41:25 Check release 'crdb' for deprecated or removed APIs...
2023/03/30 19:41:25 Finished checking release 'crdb' for deprecated or removed APIs.
2023/03/30 19:41:25 Release 'crdb' has no deprecated or removed APIs.
2023/03/30 19:41:25 Map of release 'crdb' deprecated or removed APIs to supported versions, completed successfully.
+ echo 'Upgrading helm_v3 chart'
+ echo 'Upgrading crdb'
Upgrading crdb
+ shift 1
+ helm_v3 upgrade --namespace crdb --repo https://charts.cockroachdb.com --version 10.0.7 --debug crdb cockroachdb --values /config/values-01_HelmChart.yaml
upgrade.go:142: [debug] preparing upgrade for crdb
upgrade.go:150: [debug] performing update for crdb
Error: UPGRADE FAILED: unable to build kubernetes objects from current release manifest: resource mapping not found for name: "crdb-budget" namespace: "crdb" from "": no matches for kind "PodDisruptionBudget" in version "policy/v1beta1"
ensure CRDs are installed first
helm.go:84: [debug] resource mapping not found for name: "crdb-budget" namespace: "crdb" from "": no matches for kind "PodDisruptionBudget" in version "policy/v1beta1"
ensure CRDs are installed first
unable to build kubernetes objects from current release manifest
helm.sh/helm/v3/pkg/action.(*Upgrade).performUpgrade
	helm.sh/helm/v3/pkg/action/upgrade.go:273
helm.sh/helm/v3/pkg/action.(*Upgrade).RunWithContext
	helm.sh/helm/v3/pkg/action/upgrade.go:151
main.newUpgradeCmd.func2
	helm.sh/helm/v3/cmd/helm/upgrade.go:199
github.com/spf13/cobra.(*Command).execute
	github.com/spf13/cobra@v1.5.0/command.go:872
github.com/spf13/cobra.(*Command).ExecuteC
	github.com/spf13/cobra@v1.5.0/command.go:990
github.com/spf13/cobra.(*Command).Execute
	github.com/spf13/cobra@v1.5.0/command.go:918
main.main
	helm.sh/helm/v3/cmd/helm/helm.go:83
runtime.main
	runtime/proc.go:250
runtime.goexit
	runtime/asm_amd64.s:1571
UPGRADE FAILED
main.newUpgradeCmd.func2
	helm.sh/helm/v3/cmd/helm/upgrade.go:201
github.com/spf13/cobra.(*Command).execute
	github.com/spf13/cobra@v1.5.0/command.go:872
github.com/spf13/cobra.(*Command).ExecuteC
	github.com/spf13/cobra@v1.5.0/command.go:990
github.com/spf13/cobra.(*Command).Execute
	github.com/spf13/cobra@v1.5.0/command.go:918
main.main
	helm.sh/helm/v3/cmd/helm/helm.go:83
runtime.main
	runtime/proc.go:250
runtime.goexit
	runtime/asm_amd64.s:1571

@brandond Does this patch included in 1.27.2+k3s1?
Already installed crdb
2023/05/30 20:31:50 Release 'crdb' will be checked for deprecated or removed Kubernetes APIs and will be updated if necessary to supported API versions.
2023/05/30 20:31:50 Get release 'crdb' latest version.
2023/05/30 20:31:50 Check release 'crdb' for deprecated or removed APIs...
2023/05/30 20:31:50 Finished checking release 'crdb' for deprecated or removed APIs.
2023/05/30 20:31:50 Release 'crdb' has no deprecated or removed APIs.
2023/05/30 20:31:50 Map of release 'crdb' deprecated or removed APIs to supported versions, completed successfully.
+ echo 'Upgrading helm_v3 chart'
+ echo 'Upgrading crdb'
Upgrading crdb
+ shift 1
+ helm_v3 upgrade --namespace crdb --version 11.0.1 crdb crdb/cockroachdb --values /config/values-01_HelmChart.yaml
Error: UPGRADE FAILED: unable to build kubernetes objects from current release manifest: resource mapping not found for name: "crdb-budget" namespace: "crdb" from "": no matches for kind "PodDisruptionBudget" in version "policy/v1beta1"
ensure CRDs are installed first

Yes it is, but note that it only handles migrating existing resources. If the chart is trying to add new resources using the wrong API version, the mapkubeapis plugin won't handle that - you need to update the chart itself. Can you confirm that the chart is using the new version?

@brandond  helm_v3 upgrade --namespace crdb --version 11.0.1 crdb crdb/cockroachdb --values /config/values-01_HelmChart.yaml
8.1.5 -> 11.0.1
chart: cockroachdb
helmVersion: v3
repo: https://charts.cockroachdb.com
targetNamespace: crdb
valuesContent: |
  nameOverride: crdb
  fullnameOverride: crdb

  conf:
    cache: 10%
    max-sql-memory: 30%
    log:
      enabled: true
      config:
        file-defaults:
          format: json
    store:
      enabled: true

  init:
    provisioning:
      enabled: true
      users: []
      databases: []

  statefulset:
    replicas: REDACTED
    podManagementPolicy: OrderedReady

    annotations:
      prometheus.io/scrape: "true"
      prometheus.io/port: "8080"
      prometheus.io/path: _status/vars

    resources:
      limits:
        cpu: REDACTED
        memory: REDACTED
      requests:
        cpu: REDACTED
        memory: REDACTED

    podAntiAffinity:
      topologyKey: kubernetes.io/hostname
      type: hard

    customLivenessProbe:
      httpGet:
        path: /health
        port: http
      initialDelaySeconds: 30
      periodSeconds: 30
      timeoutSeconds: 20
    customReadinessProbe:
      httpGet:
        path: /health
        port: http
      initialDelaySeconds: 30
      periodSeconds: 30
      timeoutSeconds: 20

    env:
      - name: GOMEMLIMIT
        value: REDACTED

  ingress:
    enabled: true
    annotations:
      kubernetes.io/tls-acme: "true"
      nginx.ingress.kubernetes.io/auth-url: https://$host/oauth2/auth
      nginx.ingress.kubernetes.io/auth-signin: https://$host/oauth2/start?rd=$escaped_request_uri
      nginx.ingress.kubernetes.io/service-upstream: "true"
    hosts:
      - REDACTED
    tls:
      - hosts:
          - REDACTED
        secretName: crdb-tls

  storage:
    persistentVolume:
      enabled: true
      size: REDACTED
      storageClass: REDACTED

  tls:
    enabled: false
    certs:
      selfSigner:
        enabled: false
version: 11.0.1

Helm template version is ok
# Source: cockroachdb/templates/poddisruptionbudget.yaml
kind: PodDisruptionBudget
apiVersion: policy/v1
metadata:
  name: crdb-budget
  namespace: "crdb"
  labels:
    helm.sh/chart: cockroachdb-11.0.1
    app.kubernetes.io/name: crdb
    app.kubernetes.io/instance: "crdb"
    app.kubernetes.io/managed-by: "Helm"
spec:
  selector:
    matchLabels:
      app.kubernetes.io/name: crdb
      app.kubernetes.io/instance: "crdb"
      app.kubernetes.io/component: cockroachdb
  maxUnavailable: 1

Did you go directly from K3s 1.24 to 1.27 without stepping through 1.25 and 1.26?

We had k3s 1.24 + crdb 8.1.5
Then bump k3s to 1.25, 1.26, 1.27, but because of broken pdb crdb chart was still 8.1.5 and we redact crdb sts image version manually for a long time
Now we tried to upgrade crdb chart version with fixed pdb, but it is still failing
It is not so important, you can remove requests/limits and set replicas to 3

You'll need to install the helm-mapkubeapis plugin yourself, modify the mapping file at https://github.com/helm/helm-mapkubeapis/blob/main/config/Map.yaml to handle the reversed attribute order, and then execute it to migrate the versions in your existing chart deployment.

@brandond Thank you! This fixed upgrade problem


Code folding won't expand

Issue Type: Bug
Since latest update, when working in larger powershell files (3000+ lines) it seems that some folded blocks won't expand when clicked or using the hotkey combination.  I have to close and re-open the file.
VS Code version: Code 1.37.0 (036a6b1d3ac84e5ca96a17a44e63a87971f8fcc8, 2019-08-08T02:33:50.993Z)
OS version: Windows_NT x64 10.0.18936

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-3687U CPU @ 2.10GHz (4 x 2594)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.86GB (6.35GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (8)

Extension
Author (truncated)
Version

vscode-markdownlint
Dav
0.30.1

xml
Dot
2.5.0

rainbow-csv
mec
1.2.0

powershell
ms-
2019.5.0

team
ms-
1.149.2

code-settings-sync
Sha
3.4.1

markdown-preview-enhanced
shd
0.4.3

vscode-icons
vsc
9.2.0

dup of https://github.com/microsoft/vscode/issues/76596
Sample code would be great


Added Chinese translation in README.md

Hey, Jamie, thank you for this awesome project. I created a Chinese translation for this project.
The project URL: the-super-tiny-compiler-CN
Added Chinese translation.

nubility 👏👏, Had saw the english version  for  all morning ,and then found this 😂

Glad that the translation could help you! :)

However, we already have a Chinese version, see: https://github.com/starkwang/the-super-tiny-compiler-cn


Document Pipeline's use of Pod termination messages

Changes
Prior to this commit we primarily documented use of termination messages
through a lens of Task Results, but the mechanism is used more broadly
than this.
This commit adds notes to our developer docs explaining use of pod termination
messages, giving examples of the data included, how the data is distributed to
other parts of the Pipelines machinery and describing the lack of guarantees
around the message's content.
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Docs included if any changes are user facing
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Release notes block below has been filled in or deleted (only if no user facing changes)

Release Notes
Our developer docs now include more details on how Tekton Pipelines uses Pod termination messages to communicate information between Task pods and the Tekton Pipelines controller.

/lgtm


Add information views to media library

http://www.youtube.com/watch?v=3PX_zpg-sog
Styling has changed a little after video

i have a files mode branch that i think is ready also.. i was thinking of adding it to this pr as the changes in this pr effect the changes in the files branch quite a bit. i can add to this pr or wait untill it this been reviewed to send another pr. your call mrkipling.


Crashes when importing model, animations, or when loading bone maps

Godot version
v4.1.2.stable.official.399c9dc39
System information
Godot v4.1.2.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1650 (NVIDIA; <IP_ADDRESS>99) - AMD Ryzen 7 3750H with Radeon Vega Mobile Gfx (8 Threads)
Issue description
While importing models, animations or setting bonemaps to model and animation skeletons, godot sometimes crashes. It's easy to reproduce, but it is inconsistent.
It can happen at any point when importing models or animations, reimporting models or animations, or when setting bonemaps to models and animation. It most frequently occurs when setting a bonemap for the first time. Restarting Godot and following the steps a second time rarely reproduces the error.
This is the console error message I captured during one of the crashes:
ERROR: Attempt to disconnect a nonexistent connection from '<Object#0>'. Signal: 'property_list_changed', callable: 'EditorInspector::_changed_callback'.
at: (core/object/object.cpp:1351)
Steps to reproduce
Crashing while setting bones example

Create empty scene
double click modular.glb
Click on Skeleton3d
Retarget BoneMap
Quick Load, open synty_bone_map.tres file.
Choose the Humanoid Profile.
Now.....Sometime clicking anywhere else kills godot, sometimes clicking ok, and sometime at Reimport.

Keep in mind this also seems to happen when importing models and animations as well, not just when setting bones. Setting bonemaps however appears to reproduce the crash most frequently.
Minimal reproduction project
Animation Testing.zip

I can also confirm I see this on Godot v4.1.2.stable on a M1 Macbook Pro - Forward+.

Something tells me this is going to get fixed now :)

Ooh why is that? @scotmcp

Ooh why is that? @scotmcp

Cuzz Miguel's Godot session crashed while importing animations last night.

This still happens by the way even in 4.3. I will say it happens much less frequently, but still...it happens...
Interestingly I noticed that the import seems to complete, but control doesn't seem to be handed back to the engine. Something seems to be pegging a CPU core. BUT, when I restart the engine. the import appears to have completed correctly, at least with the times I have actually checked to see if I needed to do it again or not.


Where can I find this paper

I have a more recent version of this model here:
What You Get Is What You See: A Visual Markup Decompiler
Yuntian Deng Anssi Kanervisto, Alexander Rush
https://arxiv.org/pdf/1609.04938.pdf

Note that the model is slightly different.
I also recommend reading this paper:
Robust Scene Text Recognition with Automatic Rectification
Baoguang Shi, Xinggang Wang, Pengyuan Lyu, Cong Yao, Xiang Bai
https://arxiv.org/abs/1603.03915

https://github.com/bgshih/crnn


Jose ocampo

Git WD Project edit added jose-ocampo.txt file

You're good, you should only want one pull request open at a time, and I haven't merged it yet


Updated liquibase to 3.8.8

Until this gets merged, interested parties can overwrite their local image by pulling this branch and running
docker build -t kilna/liquibase .

Is it maintained at all? Maybe someone can push fixed version to the dockerhub?


.NET and AWS SDK Requirements for development

Regarding:

Does plugin development still require installing .NET Core SDK and AWS SDK for .NET? Or is it included in the repository?
Additionally, following the discussion over email, does .NET Core SDK need to be changed to .NET Core Runtime and Hosting Bundle?
Probably best to change these to explicit install instructions instead of noting them as "Requirements".

The SDKs are still needed to build, debug and run the .NET Code. If one only needs to change the maxscripts without building new binaries those are not required.

Thanks for the clarification. Where does .NET Core Runtime and Hosting Bundle fit in? Since I was not able to run the plugin without that.
Can you change the requirements section into full instructions. Its not entirely clear that those need to be installed.


Sign in with email vertical alignment

May want to pin to top to fix screen size overflow issues

Closed by #2693


Has anyone tried the mAP beyond the shufflenet backbone?

The backbone of nanodet supports shufflenet, efficientnet mobilenet resnet. The github only shows the mAP under shufflenet. Has anyone tried other backbones? Could you please share the mAP result?

You can refer to the model zoo in readme.

You can refer to the model zoo in readme.

Thanks very much for the timely reply. I do not see the results of resnet or mobilenet. Do you have the data? Otherwise, I have to train the model by myself.


Unable to filter attachment using file name

Hello there,
I wanted to filter out the attachment using file name, but I am unable top do so.
Any kind of help would be appreciated.

Hello. You are able to filter by the file name, however you still need to provide the attachment entry (AbsEntry). Keep in mind a single attachment entry can be composed by multiple files (attachment lines).
So, if you need to get a specific file by name of a given attachment entry, this is how to do it:
var sl = new SLConnection("https://localhost:50000/b1s/v1", "SBO_COMPANYDB", "manager", "12345");
var attachment = await sl.GetAttachmentAsBytesAsync(120, "myfile.pdf");

In the example above, you obtain a file named "myfile.pdf" for the attachment entry with number 120.

@bgmulinari
I am posting an attachment which throughs an error "A file with this name already exists". I want to overwrite the file if already exists. So to overwrite the file I have to call a patch request, but I do not have the attachment entry of the existing file to call the patch request.

Unfortunately I don't think you'll be able to do that natively. An alternative would be to develop a custom view that returns what you need and then expose it on Service Layer.

Ok Thanks. That was really helpful


Setup notifications when code needs to be released after initial release.

Setup the typical automation here.
Should wait til we've shipped the first initial version.

Added newrelic-node-nextjs to the NR_REPOS env secret.  I also tested locally to verify it'll work
❯ node bin/pending-prs.js --repos newrelic-node-nextjs --dry-run --ignore-labels dev:tests
The latest release for newrelic-node-nextjs is: v0.1.0 published: 2022-03-01T21:06:06Z
Tag: v0.1.0, Target: main
The tag commit sha is:  153c79fbf8557880a1a0bf72422b467a55847ec1
Finding merged pull requests since: 2022-03-01T21:02:16Z
Found 1 PRs not yet released.
Skipping slack but here are the deets

    *newrelic-node-nextjs*

  There have been 1 PRs merged since `v0.1.0` on *2022-03-01T21:06:06Z*.

  :waiting: *PRs not yet released*:

 - https://github.com/newrelic/newrelic-node-nextjs/pull/47

    Do you want to <https://github.com/newrelic/newrelic-node-nextjs/actions/workflows/prepare-release.yml | prepare a release>?

node-newrelic on  main is 🎁 v8.8.0 via 🤖 v16.13.2
❯ node bin/pending-prs.js --repos newrelic-node-nextjs --dry-run --ignore-labels dev:tests,documentation
The latest release for newrelic-node-nextjs is: v0.1.0 published: 2022-03-01T21:06:06Z
Tag: v0.1.0, Target: main
The tag commit sha is:  153c79fbf8557880a1a0bf72422b467a55847ec1
Finding merged pull requests since: 2022-03-01T21:02:16Z
Found 0 PRs not yet released.
Skipping slack but here are the deets
:the-more-you-know: *newrelic-node-nextjs* does not have any new PRs since `v0.1.0` on *2022-03-01T21:06:06Z*.


button-group: Fix btn-group-vertical by using same rules as btn-group

Description
The CSS conditions for vertical button groups was different from the regular button group.
When using the same conditions for the regular groups for the vertical group, the bug is fixed.
Current CSS:
See the .btn-group>:not(.btn-check)+.btn on the right

Modified CSS:

I am assuming the css for the regular button group was improved at some point but not applied to the vertical button group at this point.
The second change is to add > .btn.dropdown-toggle-split:first-child to the Reset rounded corners section which is also copied down from the regular button group. I am not sure what that does but I think the same logic applies to assume that both button groups should behave the same.
I have modified the docs page of the second example on https://getbootstrap.com/docs/5.2/components/button-group/#vertical-variation to have a button group in the first position.
Type of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] ~New feature (non-breaking change which adds functionality)~
[ ] ~Refactoring (non-breaking change)~
[ ] ~Breaking change (fix or feature that would change existing functionality)~

Checklist

[x] I have read the contributing guidelines
[x] My code follows the code style of the project (using npm run lint)
[x] My change introduces changes to the documentation
[ ] ~I have updated the documentation accordingly~
[ ] ~I have added tests to cover my changes~
[x] All new and existing tests passed

Live previews

https://deploy-preview-40488--twbs-bootstrap.netlify.app/docs/5.3/components/button-group

Related issues

Closes https://github.com/twbs/bootstrap/issues/40487

Thanks for catching the issue in the first place and then for submitting a PR @tordans
I have resolved the issue.
https://stackblitz.com/edit/jzsfzg?file=index.html

I haven't checked out the code yet, but there's an issue with the rendering in the deployed version at https://deploy-preview-40488--twbs-bootstrap.netlify.app/docs/5.3/components/button-group/#vertical-variation; the top-right corner from the 2nd item in the vertical variation is rounded, and the left-bottom corner of the last item should be rounded.

This is fixed now. The preview looks right to me, now.


[Diagnostics] Resolves: SR-5324 Improved diagnostic when instance member of outer type is referenced from nested type

The intended behavior is described in JIRA issue.
Resolves SR-5324.
It's my first touch to the Swift compiler and I'm not sure whether it's the right approach. I'm looking for your feedback :)
Could you take a look @xedin ?
Thanks!

It would be great if you could also come up with a couple more similar test-cases so we could add them into the suite.

Of course, I will work on it right away!
Thank you

@Kacper20 Check out this PR -- https://github.com/apple/swift/pull/11640 -- do you think the logic can be combined somehow?

@slavapestov I'm not sure about this, I think I lack the knowledge of how those two relate to each other. Could you please check my last comment to your review? I've asked some questions related to this PR and I believe that answers would allow me to complete this feature(if introducing new diagnostic is not a good idea).
Thanks in advance!

@swift-ci please smoke test

Sorry for the delay! :)
@slavapestov I've managed to preserve the desired message without emitting new kind of diagnostic. Could you please take a look? This required some changes on the other part of code (~5040L, CSDiag.cpp) and it makes code there a bit uglier there.
@xedin I will include tests in next commit.

@swift-ci please smoke test

@swift-ci please smoke test

@Kacper20 Looks like this improve a bunch of other tests, so you'll have to fix that and introduced couple of new crashers which need to be addressed before we merge this, do you know how to run test suite locally?

@xedin Yes, will fix it and let you know. I have some troubles running specific tests(lit.py failing), but will do it with full test suite.

@Kacper20 Thanks!

Should be fixed right now.

@swift-ci please smoke test

@xedin I think that this failure on Linux is unrelated to my changes.

Yeah, I had that happen yesterday too, let's try a clean Linux build.

@swift-ci please clean smoke test Linux platform

@Kacper20 I'm going to squash your changes before merging if you don't mind?

@xedin Of course, thanks!

Merged, thanks for helping out with this, @Kacper20!

Thanks for all of the help in implementing this @xedin, @slavapestov, @CodaFi!


[ISSUE-1261] Finish_backward LocalExchangeSourceOperator because of short-circuit break of HashJoinProbeOperator

Bugfix
In a pipeline, some operators can finish in advance, e.g.

LimitOperator: it finishes after consume sufficient rows.
HashJoinProbeOperator: it finishes if HashJoinBuildOperator build a empty HT and the join type is INNER JOIN, RIGHT JOIN or RIGHT SEMI-JOIN.

when a pipeline is in the form of  ExchangeSourceOperator->Operator(finish in advance) and the pipeline's dop > 1, LocalExchange would get stuck in a corner case if:

There exists a driver, the latter operator(i.e. HashJoinProbeOperator) is finished, then finish function of the former ExchangeSourceOperator ignores the buffered chunks the number of rows of that is taken into consideration when LocalExchanger determines whether it has available room to accept new chunks from LocalExchangeSinkOperators.
LocalExchanger have no available room to accept new chunks from LocalExchangeSinkOperators, so drivers that ends with the LocalExchangeSinkOperator are blocked in OUTPUT_FULL state, and drivers that starts with LocalExchangeSourceOperator are blocked in INTPUT_EMPTY state, in such scenarios, a query is always executed timeout.

The solution to this issue is that finish_backward function which is invoked in the timepoint distinct from the finsh function is added to Operator.  finish_backward function is used to finish preceding operators of the current operator if it finshes in advance, while finish function is used to finish following operators of the current operator.
Most of operators have trivial finish_backward function that just call finsh function. however, ExchangeSourceOperator's finish_backward function will clear the buffered chunks and subtract the number of rows of the buffered chunks from LocalExchanger and make it unblocked.

run starrocks_be_unittest


Update Dora with latest code

So that I do not have to wait for npm install each time I switch branches

Made a mistake in conflict resolution. Will redo.


Adds new API: TSVConnSslSniGet

converts rate_limit to use this API instead of calling OpenSSL APIs,
allowing this plugin to work with BoringSSL

[approve ci autest]

Cherry-picked to v9.2.x


Mag recalibration via rosservice

Hello!
I have a uINS rugged module mounted on my ground vehicle (like so) and I am having trouble getting the absolute orientation from it. When I fuse the yaw output from /ins to my robot_localization node, it causes the robot to rotate on the spot even when it's stationary; and when I use the imu_madgwick_filter package to fuse the /imu and /mag data to get orientation, the orientation output is correct, but when the robot is rotated, the heading immediately returns to the starting position exactly as described here.
I suspect this has a lot to do with the mounting of uINS on the robot - very close to battery cells and the aluminum frame on the bottom. But I am hoping that a mag recalibration can fix this. Also note that the magnetometer readings on /mag seem unreasonably high (like 1.4 Teslas!):
magnetic_field:
  x: -0.695064246655
  y: 1.44425451756
  z: 1.13877093792
magnetic_field_covariance: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]

Is this wierd?
I tried running the rosservice call /single_axis_mag_cal, but it does not inform me if the procedure is completed or if I did it correctly? There is only:
success: True
message: "Successfully initiated mag recalibration."

But how do I know the end of it?
Please let me know your thoughts. Thanks!

I'm also having the same issue.
Is there a fix for this?

The magnetometer is very sensitive as it is trying to sense the relatively weak magnetic field of the earth. From the small image you sent, I don't know the amount of current traveling from those batteries, but current in a wire is going to create a magnetic field. As the current fluctuate, the magnetic field does as well. It will be impossible for the magnetometer to decipher the difference. The fix is to carefully design and evaluate the affects of the difference parts of your system on the magnetic field near the uINS.

Could you send me a PPD log in .dat format and we can investigate this more closely.
https://docs.inertialsense.com/user-manual/logging-plotting/data_logging/#logging-ppd-in-cltool

I'm sorry for the delay. Could you please clarify in what condition of the uINS do you want me to record the log? Do you want me to keep it mounted on my robot, or maybe in mid-air? stationary or performing some motion?

@Srijal97  Send me a log of you trying to recalibrate the magnetometer. I'd like to see it in your intended integration position.


Explicitely set newline and encoding parameters for datalayouts/formats

This will make the resulting artifacts system agnostic. Related to https://github.com/qiime2/qiime2/pull/95

Addressed in https://github.com/qiime2/qiime2/pull/120


Lucas Ho Final Week 1 Review Ticket

[ ] https://github.com/jacksongolding/Nut-Team/issues/19

All this took me five hours. I played around with functions to see what would work. Also, I'm not the best at coding and some stuff is confusing so it took me five hours.

1.8/1.8
Good progress on the calendar done, with its creation and adding to it, also progress on deleting things from the calendar


Fix DQMHarvest spec to create Harvesting job instead of merge one

I started working in the wrong branch, anyways we may need to patch 1.0.5 with this fix.
Creating the master version soon.

This doesn't have to be merged in 1.0.5 version since this only affects reqmgr. But I am merging it anyway.


Add docs for hex package

What exactly has to be done here?

Review current docs, generate & publish edoc, as seen in http://www.rebar3.org/docs/publishing-packages

I can't think of much that needs to be added besides the -triq(eunit) feature. Maybe let's publish the docs as they are, unless you think they're in bad shape, and re-publish after we've revised it. We could change this ticket to track documentation TODO items instead.

@tuncer agreed 👍

See https://github.com/triqng/triq/pull/40

See #42

With #42 merged, I think this can be closed as resolved.

Closing, fixed by #40 and #42.


CI: ClusterFuzzLite integration

As of this writing, the CI correctly reports an expected crash:
INFO: Running with entropic power schedule (0xFF, 100).
INFO: Seed: 1337
INFO: -max_len is not provided; libFuzzer will not generate inputs larger than 4096 bytes
INFO: A corpus is not provided, starting from an empty corpus
#2	INITED cov: 16 ft: 16 corp: 1/1b exec/s: 0 rss: 50Mb
#3	NEW    cov: 16 ft: 17 corp: 2/2b lim: 4 exec/s: 0 rss: 50Mb L: 1/1 MS: 1 ChangeBit-
 === Uncaught Python exception: ===
CalltreeError: Decoding error when reading CFG file
Traceback (most recent call last):
  File "fuzz_cfg_load.py", line 34, in TestOneInput
  File "/tmp/_MEIu963Q8/fuzz_introspector/cfg_load.py", line 111, in data_file_read_calltree
    raise CalltreeError("Decoding error when reading CFG file")

Will push a fix and see if things pass

@jonathanmetzman I'm having some troubles integrating a Python project with ClusterFuzzLite. The problem occurs in the check_build where it seems like ClusterFuzzLite treats it as a c++ project rather than a Python project.
From the CI logs:
 2022-07-22 14:17:27,813 - root - INFO - repo_dir: /github/workspace/storage/fuzz-introspector.
2022-07-22T14:17:27.8198549Z Successfully tagged external-cfl-project-28788aa53f0746e4b6adfe2b8b2060a9:latest
2022-07-22T14:17:27.8462543Z 2022-07-22 14:17:27,845 - root - INFO - Docker container: db2d4fe59c79.
2022-07-22T14:17:27.8475010Z 2022-07-22 14:17:27,845 - root - INFO - Building with address sanitizer.
2022-07-22T14:17:27.8476739Z 2022-07-22 14:17:27,846 - root - INFO - Running: docker run --rm --privileged -e FUZZING_ENGINE=libfuzzer -e CIFUZZ=True -e SANITIZER=address -e ARCHITECTURE=x86_64 -e FUZZING_LANGUAGE=c++ -e OUT=/github/workspace/build-out --volumes-from db2d4fe59c79 external-cfl-project-28788aa53f0746e4b6adfe2b8b2060a9 /bin/bash -c compile.
2022-07-22T14:17:28.1717068Z ---------------------------------------------------------------
2022-07-22T14:17:28.1725688Z Compiling libFuzzer to /usr/lib/libFuzzingEngine.a...  done.
2022-07-22T14:17:28.1817184Z ---------------------------------------------------------------
2022-07-22T14:17:28.1817540Z CC=clang
...
...
...
2022-07-22T14:19:36.9547035Z 2022-07-22 14:19:36,953 - root - ERROR - Request to https://api.github.com/repos/ossf/fuzz-introspector/actions/artifacts?per_page=100&page=1 failed. Code: 401. Response: {'message': 'Bad credentials', 'documentation_url': 'https://docs.github.com/rest'}
2022-07-22T14:19:36.9554093Z 2022-07-22 14:19:36,954 - root - ERROR - Could not get coverage: Github API request failed..
2022-07-22T14:19:36.9554592Z 2022-07-22 14:19:36,954 - root - ERROR - Could not find latest coverage report.
2022-07-22T14:26:56.4222672Z 2022-07-22 14:26:56,421 - root - ERROR - Build check failed.
2022-07-22T14:26:56.4223353Z Build check: stdout: INFO: performing bad build checks for /tmp/not-out/tmpcsnqifqm/fuzz_cfg_load
2022-07-22T14:26:56.4244895Z 2022-07-22 14:26:56,421 - root - ERROR - Error building fuzzers for (commit: 52313a708e6d8f2bec8e768b09385826434a21e2, pr_ref: refs/pull/410/merge).
2022-07-22T14:26:56.4245603Z INFO: performing bad build checks for /tmp/not-out/tmpcsnqifqm/fuzz_report_generation
2022-07-22T14:26:56.4246021Z Retrying failed fuzz targets sequentially 2
2022-07-22T14:26:56.4246533Z INFO: performing bad build checks for /tmp/not-out/tmpcsnqifqm/fuzz_cfg_load
2022-07-22T14:26:56.4247102Z INFO: performing bad build checks for /tmp/not-out/tmpcsnqifqm/fuzz_report_generation
2022-07-22T14:26:56.4247465Z Broken fuzz targets 2
2022-07-22T14:26:56.4249691Z ('/tmp/not-out/tmpcsnqifqm/fuzz_cfg_load', CompletedProcess(args=['bad_build_check', '/tmp/not-out/tmpcsnqifqm/fuzz_cfg_load'], returncode=2, stdout=b'BAD BUILD /tmp/not-out/tmpcsnqifqm/fuzz_cfg_load is not built for architecture: x86_64\nfile command output: /tmp/not-out/tmpcsnqifqm/fuzz_cfg_load: POSIX shell script, ASCII text executable\ncheck_mixed_sanitizers test will fail.\nBAD BUILD: /tmp/not-out/tmpcsnqifqm/fuzz_cfg_load does not seem to be compiled with ASan.\n', stderr=b'objdump: /tmp/not-out/tmpcsnqifqm/fuzz_cfg_load: file format not recognized\nobjdump: /tmp/not-out/tmpcsnqifqm/fuzz_cfg_load: file format not recognized\nobjdump: /tmp/not-out/tmpcsnqifqm/fuzz_cfg_load: file format not recognized\nobjdump: /tmp/not-out/tmpcsnqifqm/fuzz_cfg_load: file format not recognized\n'))
2022-07-22T14:26:56.4251675Z BAD BUILD /tmp/not-out/tmpcsnqifqm/fuzz_cfg_load is not built for architecture: x86_64
2022-07-22T14:26:56.4252320Z file command output: /tmp/not-out/tmpcsnqifqm/fuzz_cfg_load: POSIX shell script, ASCII text executable
2022-07-22T14:26:56.4252772Z check_mixed_sanitizers test will fail.
2022-07-22T14:26:56.4253281Z BAD BUILD: /tmp/not-out/tmpcsnqifqm/fuzz_cfg_load does not seem to be compiled with ASan.
2022-07-22T14:26:56.4253849Z objdump: /tmp/not-out/tmpcsnqifqm/fuzz_cfg_load: file format not recognized
2022-07-22T14:26:56.4254391Z objdump: /tmp/not-out/tmpcsnqifqm/fuzz_cfg_load: file format not recognized

Because FUZZING_LANGUAGE is set to c++ the bad build check does not return here: https://github.com/google/oss-fuzz/blob/f014b858d9f05ac9a8fb50ad6a54b0b3819dcfe8/infra/base-images/base-runner/bad_build_check#L304-L307 but rather continues.
Am struggling to find where I go wrong, could you assist?


[table] save view modal

Summary
As part of #1210 we need to create a modal that lets the user save a view.
Additional context
Add any other context or screenshots about the feature request here.

:tada: This issue has been resolved in version 2.98.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


integral-tests.eo:71-75: This test fails due to incorrect...

The puzzle 93-b28a2be4 from #93 has to be resolved:
https://github.com/objectionary/eo-math/blob/4cceaf5275af9a1b0f1c2755e80daa732df2d486/src/test/eo/org/eolang/math/integral-tests.eo#L71-L75
The puzzle was created by @rultor on 29-Nov-22.
Estimate: 30 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@maxonfjvipon please pay attention to this new issue.

The puzzle 93-b28a2be4 has disappeared from the source code, that's why I closed this issue. //cc @maxonfjvipon


Contributing readme.md file concise readme.md file #193

Hi @iamparas0 ,
I hope this message finds you well. I am reaching out to request your permission to enhance the review section by adding readme.md  file of your  website.
Please assign this issue to me with "hactoberfest" "hactoberfest-accepted" "gssoc-extd" "level-2" labels to make more confident towards open source.
Please let me know if i can proceed this issue. I appreciate your consideration.

Hello @iamparas0
The current readme file does not contain the following sections :
Table of contents for easy access to new contributors
featured in
forkers and stargazers
back to top button for easy navigation
Kindly Assign me this issue with hacktoberfest-accepted and gssoc-extd labels


absl.flags._exceptions.IllegalFlagValueError

I got this exception absl.flags._exceptions.IllegalFlagValueError: flag --bucket_range=[40, 401, 40]: Expect argument to be a string or int, found <class 'list'> at flags.DEFINE_integer("bucket_range", [40, 401, 40], "the range of bucket").
Sorry to say that I'm a beginner. Who can tell me why?

It has been fixed in the latest version

@wzhouad Thank you. It worked after I updated to the latest version. But can I run this model on CPU-only machine?

Change use_cudnn in config.py to False.


Fix: repository base

Also upgraded the deps or it will fail to build :D

LGTM! Thanks @Candinya 🚀


try to follow the manual. this is what i got

❱ kubernaut config backend create --url="https://next.kubernaut.io" --name="v2" --activate $TOKEN
Traceback (most recent call last):
File "kubernaut/cli.py", line 47, in
File "site-packages/click/core.py", line 764, in call
File "site-packages/click/core.py", line 717, in main
File "site-packages/click/core.py", line 1134, in invoke
File "site-packages/click/core.py", line 956, in invoke
File "site-packages/click/core.py", line 555, in invoke
File "site-packages/click/decorators.py", line 17, in new_func
File "kubernaut/cli.py", line 32, in cli
File "kubernaut/config/model.py", line 72, in load
File "pathlib.py", line 1189, in read_text
File "pathlib.py", line 1176, in open
IsADirectoryError: [Errno 21] Is a directory: '/Users/anatoly/Library/Application Support/kubernaut/config'
[16789] Failed to execute script cli

Same here


parseContent doesn't seem to append to new line.

I'm making an embed builder website and when I try to use parseContent or parseTitle, it doesn't seem to go to a new line.
Also markdown isn't properly supported? Could this be a css issue i'm having or not?

Can repro

When I create an embed from the example folder code with your message content, new lines are displaying right, so this is probably a problem with your css.
You should apply this to your embed container:
white-space: pre;


CL2 should fail on Prometheus set-up errors.

As the Prometheus Server is going to become a standard way of measuring SLIs in scale-tests we should make the ClusterLoader2 fail if it's not able to set up the Prometheus stack.
It doesn't make sense to run tests if we're not able to measure SLIs.
Ref. https://github.com/kubernetes/kubernetes/issues/75284

/lgtm
/approve


Support for Cloudflare AI Gateway?

Maybe possible to add support for Cloudflare AI Gateway https://developers.cloudflare.com/ai-gateway/get-started/connecting-applications/ ? and https://developers.cloudflare.com/ai-gateway/tutorials/deploy-aig-worker/

endpoint: the pathname of the provider API you’re trying to reach. For example, on OpenAI it can be chat/completions, and for HuggingFace this might be bigstar/code. See more in the sections that are specific to each provider.

I've just made a PR to add support for OpenAI Cloudflare AI Gateway endpoints. See here: https://github.com/enricoros/big-agi/pull/168

@jontybrook @centminmod - PR merged! Thanks for the contribution. Closed in https://github.com/enricoros/big-agi/commit/05097af27b6b1cc8a30bb2f5bcae15f576a2ea6d
Can you test it and let me know?
You can your CloudFlare OpenAI base URL ("https://gateway.ai.cloudflare.com/v1/ACCOUNT_TAG/GATEWAY/openai") in the "API Host" field in the UI (Models > OpenAI > Advanced).

@enricoros tried to build but ran into an issue https://github.com/enricoros/big-agi/issues/174 :)

@enricoros thanks for the workaround in #174 - managed to build it and test your Cloudflare AI Gateway implementation and so far works. Just one thing the URL isn't https://gateway.ai.cloudflare.com/v1/ACCOUNT_TAG/GATEWAY/openai but https://gateway.ai.cloudflare.com/v1/ACCOUNT_TAG/GATEWAY/YOUR_GATEWAY_NAME/openai where YOUR_GATEWAY_NAME is the name you used to create the AI Gateway


I am adding new Headline in project .

I am adding new Headline in project .

Ok mam
On Sat, 10 Jun 2023, 9:25 am AKSHITA GUPTA, @.***>
wrote:

Closed #740 https://github.com/akshitagupta15june/Moksh/pull/740.
—
Reply to this email directly, view it on GitHub
https://github.com/akshitagupta15june/Moksh/pull/740#event-9489757146,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZX2POY4BJV5OX3KRKRTZL3XKPV4BANCNFSM6AAAAAAZA6KUQA
.
You are receiving this because you authored the thread.Message ID:
@.***>


docker-untar on btrfs_graph extremely slow

Environment:

cf v214
diego 0.1398.0
cf cli v6

Reproducing:
cf docker-push redis altoros/redis
on the cell vm start htop and filter out with docker keyword
time to apply layers onto btrfs_graph is so long and this leads to stopping application by timeout
there are no network delays
i know there is an issue with docker and btrfs and i  wonder can we switch off btrfs for garden-linux or are there any knobs to tune it out?

Hi, @ramelito,
It sounds like this is more of an issue with the operation of garden-linux, rather than with Diego itself, so it would be better to raise this as an issue on the garden-linux repo or its BOSH release. At this point garden-linux is committed strongly to btrfs as the preferred filesystem for its graph layers, although the Garden team can comment more comprehensively on their decision. In our experience on the Diego team, it has been slow in some regards, but generally we haven't seen performance problems with it on that magnitude, so it's possible that something unexpected is going wrong.
Thanks,
Eric, CF Runtime Diego PM

Closing. As stated earlier, if you're still seeing this issue, please raise it with the garden-linux project for better visibility with the CF Garden team. It's also worth noting that we've observed some other issues running btrfs under heavy workloads, and the Garden team is working on alternate approaches for managing container layers that still meet CF's requirements. Please consult their team tracker for the current state of work.
Thanks again,
Eric